Data migration methods, terminals, cloud, storage media, and application products
By obtaining the scenario authorization information from the terminal token, determining scenario compatibility, generating migration data packets, and performing data migration under certain conditions, the problem of discontinuous cross-device data migration links is solved, achieving seamless continuity and supporting cross-terminal data migration in smart cockpits.
Patent Information
- Application Number
- CN202611460557.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-09-18
- Publication Date
- 2026-11-17
AI Technical Summary
In existing technologies, cross-device data migration links are discontinuous, scene states are lost, and there is a lack of true scene state continuity.
By obtaining the scenario authorization information from the terminal token, the scenario matching is determined, a migration data packet is generated, and data migration is performed under the condition of meeting the scenario matching, achieving seamless connection using near-field or remote communication.
It enables seamless data transfer between different terminals, solves the problem of discontinuous data migration links across devices, and supports cross-terminal data migration in smart cockpits.
Smart Images

Figure CN123123367A_ABST
Abstract
Description
Technical Field
[0001] This disclosure relates to the field of cross-device data migration technology, and more specifically, to a data migration method, terminal, cloud, storage medium, and program product. Background Technology
[0002] With the rapid development of smart cars, smart homes, and mobile terminals, users' need to switch between different devices is increasing. Current research mainly focuses on simple connections and screen mirroring functions between devices, lacking true continuity of scene states.
[0003] While some solutions achieve basic connectivity between devices, they fail to address core pain points such as the loss of context. In other words, they still face the challenge of discontinuous data migration links across devices. Summary of the Invention
[0004] To overcome the problems existing in related technologies, this disclosure provides a data migration method, terminal, cloud, storage medium, and program product.
[0005] According to a first aspect of the present disclosure, a data migration method is provided, comprising: obtaining first scene authorization information of a first terminal token held by a first terminal; determining whether the scene authorized by the first terminal token matches a target scene based on the first scene authorization information of the first terminal token; generating a migration data packet in response to the first terminal token's authorized scene matching the target scene and obtaining a migration trigger event; and sending the migration data packet to the second terminal in response to the second terminal's second terminal's second terminal's second terminal's second terminal's second terminal's second terminal's second scene matching the target scene.
[0006] In some embodiments of this disclosure, obtaining the migration trigger event includes: obtaining the distance between the first terminal and the second terminal; and generating the migration trigger event in response to the distance between the first terminal and the second terminal being less than a first distance.
[0007] In some embodiments of this disclosure, the method further includes: in response to the distance between the first terminal and the second terminal being less than a second distance, sending a first request message to the second terminal, the first request message being used to claim the second terminal token, wherein the second distance is less than the first distance; in response to receiving the second terminal token, obtaining second scene authorization information of the second terminal token; and determining whether the scene authorized by the second terminal token matches the target scene based on the second scene authorization information of the second terminal token.
[0008] In some embodiments of this disclosure, obtaining the migration trigger event includes: determining whether a migration trigger message sent by the cloud has been received; and determining that the migration trigger event has been obtained in response to receiving the migration trigger message.
[0009] In some embodiments of this disclosure, the step of sending the migration data packet to the second terminal in response to the scenario authorized by the second terminal token held by the second terminal matching the target scenario includes: sending the migration data packet to the cloud in response to the scenario authorized by the second terminal token matching the target scenario, so as to send the migration data packet to the second terminal through the cloud.
[0010] In some embodiments of this disclosure, generating the migration data packet includes: obtaining capability information of the second terminal; determining a capability information set of the second terminal based on the capability information of the second terminal; selecting capabilities belonging to the capability information set of the second terminal from the capabilities to be migrated of the first terminal, and adding the selected capabilities to the capability set; and generating the migration data packet based on the capability set.
[0011] In some embodiments of this disclosure, generating the migration data packet based on the capability set includes: combining the application runtime state, the capability set, and the scene context into atomic migration units, wherein the scene context represents the complete environmental semantic information required for a user to complete a business action in a predetermined time and space; performing format conversion processing on the atomic migration units to obtain atomic migration units of a predetermined format; and encrypting the atomic migration units of the predetermined format to obtain the migration data packet.
[0012] In some embodiments of this disclosure, encrypting the atomic migration unit of the predetermined format to obtain the migration data packet includes: sending a second request message to the cloud, the second request message being used to request encrypted information; and in response to receiving the encrypted information, encrypting the atomic migration unit of the predetermined format using the encrypted information to obtain the migration data packet.
[0013] In some embodiments of this disclosure, obtaining the capability information of the second terminal includes: sending a third request message to the cloud, the third request message being used to request the capability information of the second terminal; and receiving the capability information of the second terminal sent by the cloud.
[0014] In some embodiments of this disclosure, obtaining the capability information of the second terminal includes: in response to the establishment of a near-field communication link between the first terminal and the second terminal, sending a fourth request message to the second terminal, the fourth request message being used to request the capability information of the second terminal; and receiving the capability information of the second terminal sent by the second terminal.
[0015] In some embodiments of this disclosure, the method further includes: acquiring environmental features, processing the environmental features to obtain a scene vector; performing confidence prediction based on the scene vector to obtain a predicted confidence level; and warming up the secure transmission channel in response to the predicted confidence level being greater than a confidence level threshold.
[0016] In some embodiments of this disclosure, the method further includes: generating a preheating instruction in response to the prediction confidence level being greater than the confidence level threshold, and sending the preheating instruction to the second terminal.
[0017] According to a second aspect of the present disclosure, a data migration method is provided, comprising: receiving a first biometric feature uploaded by a first terminal and a second biometric feature uploaded by a second terminal; verifying the user identity of the first terminal based on the first biometric feature and verifying the user identity of the second terminal based on the second biometric feature; distributing a first terminal token to the first terminal in response to the successful verification of the user identity of the first terminal; and distributing a second terminal token to the second terminal in response to the successful verification of the user identity of the second terminal, wherein the first terminal token includes first scenario authorization information, the second terminal token includes second scenario authorization information, and the first terminal token and the second terminal token are used for authentication during the data migration process between the first terminal and the second terminal.
[0018] In some embodiments of this disclosure, the method further includes: verifying whether the count value carried by the first terminal token and / or the second terminal token exceeds a preset value, wherein the count value represents the cumulative number of token migrations; and reclaiming the verified first terminal token and / or the second terminal token in response to the count value exceeding the preset value.
[0019] In some embodiments of this disclosure, the method further includes: verifying whether the holding time of the first terminal token and / or the second terminal token exceeds a time threshold; and, in response to the holding time exceeding the time threshold, reclaiming the verified first terminal token or the second terminal token.
[0020] According to a third aspect of the present disclosure, a data migration method is provided, comprising: obtaining second scenario authorization information of a second terminal token held by a second terminal; determining whether the scenario authorized by the second terminal token matches a target scenario based on the second scenario authorization information of the second terminal token; receiving a migration data packet in response to the scenario authorized by the second terminal token matching the target scenario; performing security processing on the migration data packet to obtain migration data; and restoring the running state of an application based on the migration data.
[0021] In some embodiments of this disclosure, obtaining the second scenario authorization information of the second terminal token held by the second terminal includes: in response to the distance between the user and the second terminal being less than a third distance, obtaining the second scenario authorization information of the second terminal token.
[0022] In some embodiments of this disclosure, the method further includes: in response to the scenario authorized by the second terminal token matching the target scenario, sending a notification message to the cloud or the mobile terminal, so that the cloud or the mobile terminal sends the migration data packet in response to the received notification message.
[0023] In some embodiments of this disclosure, the method further includes: launching a corresponding application process in response to receiving a preheating command.
[0024] In some embodiments of this disclosure, the method further includes: after starting the corresponding application process, generating a confirmation prompt message, the confirmation prompt message being used to prompt the user to confirm or cancel the data migration; receiving the migration data packet in response to receiving a confirmation instruction; and refusing to receive the migration data packet in response to receiving a cancellation instruction.
[0025] According to a fourth aspect of the present disclosure, a first terminal is provided, comprising: a first acquisition module, configured to acquire first scene authorization information of a first terminal token held by the first terminal; a first determination module, configured to determine whether the scene authorized by the first terminal token matches a target scene based on the first scene authorization information of the first terminal token; a generation module, configured to generate a migration data packet in response to the scene authorized by the first terminal token matching the target scene and acquiring a migration trigger event; and a sending module, configured to send the migration data packet to the second terminal in response to the scene authorized by a second terminal token held by the second terminal matching the target scene.
[0026] According to a fifth aspect of the present disclosure, a cloud platform is provided, comprising: a first receiving module, configured to receive a first biometric feature uploaded by a first terminal and a second biometric feature uploaded by a second terminal; a verification module, configured to verify the user identity of the first terminal based on the first biometric feature and verify the user identity of the second terminal based on the second biometric feature; and a distribution module, configured to, in response to successful user identity verification, distribute a first terminal token to the first terminal and a second terminal token to the second terminal, wherein the first terminal token includes first scenario authorization information, the second terminal token includes second scenario authorization information, and the first terminal token and the second terminal token are used for authentication during data migration between the first terminal and the second terminal.
[0027] According to a sixth aspect of the present disclosure, a second terminal is provided, comprising: a second acquisition module, configured to acquire second scenario authorization information of a second terminal token held by the second terminal; a second determination module, configured to determine, based on the second scenario authorization information of the second terminal token, whether the scenario authorized by the second terminal token matches a target scenario; a second receiving module, configured to receive a migration data packet in response to the scenario authorized by the second terminal token matching the target scenario; a processing module, configured to perform security processing on the migration data packet to obtain migration data; and a recovery module, configured to restore the running state of an application based on the migration data.
[0028] According to a seventh aspect of the present disclosure, a non-transitory computer-readable storage medium is provided, which, when instructions in the storage medium are executed by a processor of a terminal, enables the terminal to perform any of the data migration methods described herein.
[0029] According to an eighth aspect of the present disclosure, a computer program product is provided, the computer program product including a computer program or computer instructions, the computer program or computer instructions being loaded and executed by a processor to enable a computer to implement any of the data migration methods described herein.
[0030] The data migration method of this disclosure involves: acquiring first scene authorization information of a first terminal token held by a first terminal; determining whether the scene authorized by the first terminal token matches the target scene based on the first scene authorization information; generating a migration data packet in response to the match between the scene authorized by the first terminal token and the target scene, and obtaining a migration trigger event; and then sending the migration data packet to the second terminal in response to the match between the scene authorized by the second terminal token held by the second terminal and the target scene. By binding scenes to the first and second terminal tokens, the data migration process is triggered when the authorized scenes bound to the two tokens match the scene to be migrated, i.e., the target scene. This addresses the technical pain point of discontinuous cross-device data migration links to a certain extent, achieving seamless continuity of scene data between different terminals and supporting cross-terminal data migration in smart cockpits.
[0031] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description
[0032] The accompanying drawings, which are incorporated in and form a part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure.
[0033] Figure 1 This is a schematic diagram of a data migration system according to some embodiments of the present disclosure. Figure 1 ; Figure 2 This is a schematic diagram of a data migration system according to some embodiments of the present disclosure. Figure 2 ; Figure 3 This is a schematic diagram of a data migration system according to some embodiments of the present disclosure. Figure 3 ; Figure 4 This is a flowchart illustrating a data migration method according to some embodiments of the present disclosure. Figure 1 ; Figure 5 This is a flowchart illustrating a data migration method according to some embodiments of the present disclosure. Figure 2 ; Figure 6 This is a flowchart illustrating a data migration method according to some embodiments of the present disclosure. Figure 3 ; Figure 7 This is a flowchart illustrating a data migration method according to some embodiments of the present disclosure. Figure 4 ; Figure 8 This is a flowchart illustrating a data migration method according to some embodiments of the present disclosure. Figure 5 ; Figure 9 This is a flowchart illustrating a data migration method according to some embodiments of the present disclosure. Figure 5 ; Figure 10 This is a schematic diagram illustrating the complete process of commuting to work, based on some embodiments of this disclosure. Figure 11 This is a first-stage timing diagram of a commuting scenario according to some embodiments of the present disclosure; Figure 12 This is a second-stage timing diagram illustrating a commuting scenario to work, based on some embodiments of this disclosure; Figure 13 This is a third-stage timing diagram illustrating a commuting scenario to work, based on some embodiments of this disclosure. Figure 14 This is a fourth-stage timing diagram illustrating a commuting scenario based on some embodiments of the present disclosure; Figure 15 This is a fifth-stage timing diagram illustrating a commuting scenario according to some embodiments of the present disclosure; Figure 16 This is a sixth-stage timing diagram illustrating a commuting scenario according to some embodiments of the present disclosure; Figure 17 This is a schematic diagram illustrating the complete process of returning home after get off work, based on some embodiments of this disclosure. Figure 18 This is a timing diagram of the first stage of a scenario where people return home after get off work, as shown in some embodiments of this disclosure. Figure 19 This is a second-stage timing diagram illustrating a scenario of returning home after get off work, according to some embodiments of this disclosure; Figure 20 This is a timing diagram of the third stage in the scenario of returning home after get off work, as shown in some embodiments of this disclosure; Figure 21 This is a timing diagram of the fourth stage in the scenario of returning home after get off work, as shown in some embodiments of this disclosure; Figure 22 This is a fifth-stage timing diagram illustrating the scenario of returning home after get off work, according to some embodiments of this disclosure; Figure 23 This is a timing diagram of the sixth stage in the scenario of returning home after get off work, as shown in some embodiments of this disclosure; Figure 24 These are schematic diagrams of the architecture shown according to some embodiments of this disclosure; Figure 25 This is a schematic diagram of a first terminal shown according to some embodiments of the present disclosure; Figure 26These are schematic diagrams illustrating operations according to some embodiments of this disclosure; Figure 27 This is a schematic diagram of a second terminal shown according to some embodiments of the present disclosure; Figure 28 This is a block diagram illustrating an electronic device according to some embodiments of the present disclosure. Detailed Implementation
[0034] Exemplary embodiments of this disclosure will be described in detail herein, examples of which are illustrated in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings denote the same or similar elements unless otherwise indicated. Various changes, modifications, and equivalents of the methods, apparatus, and / or systems described herein will become apparent upon understanding this disclosure. For example, the order of operations described herein is merely illustrative and is not limited to those orders set forth herein, but can be changed as will become apparent upon understanding this disclosure, except for operations that must be performed in a particular order. Furthermore, for clarity and brevity, descriptions of features known in the art may be omitted.
[0035] The embodiments described below, which are some of the embodiments of this disclosure, do not represent all embodiments consistent with this disclosure. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this disclosure as detailed in the appended claims.
[0036] The terms "first" and "second," etc., used in this disclosure are only used to distinguish different objects and not to describe a specific order. The terms "comprising" and "having," and any variations thereof, in the embodiments of this disclosure are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device that includes a series of steps or units is not limited to the listed steps or units, but may also include steps or units not listed.
[0037] Throughout this disclosure, the references to "embodiments" do not necessarily refer to the same embodiments, nor are they independent or alternative embodiments mutually exclusive with other embodiments. Those skilled in the art will explicitly and implicitly understand that the embodiments described in this disclosure can be combined with other embodiments.
[0038] The exemplary embodiments in this disclosure may involve user data, data acquisition, and / or use. These aspects all comply with applicable laws, regulations, and relevant provisions. In the exemplary embodiments in this disclosure, all data collection, acquisition, processing, manipulation, forwarding, and use are conducted with the user's knowledge and confirmation. Accordingly, in implementing each example, the type, scope of use, and usage scenarios of any data or information that may be involved should be communicated to the user and their authorization obtained in accordance with applicable laws and regulations through appropriate means. The specific methods of notification and / or authorization can vary depending on the actual situation and application scenario, and the scope of the solution is not limited in this respect.
[0039] The data migration method involved in the embodiments of this disclosure can be used in... Figures 1 to 3 The data migration system shown in the figure is implemented.
[0040] Figure 1 A near-field communication data migration system is shown. The first terminal and the second terminal are connected via near-field communication. The first terminal and the second terminal can communicate with each other through at least one of Bluetooth, NFC, and Wi-Fi Direct, so as to migrate data from the first terminal to the second terminal or vice versa, thereby achieving scene continuity.
[0041] Figure 2 A data migration system for long-distance communication is shown. The first terminal and the second terminal communicate over a long distance. The first terminal communicates with the second terminal through the cloud to migrate data from the first terminal to the second terminal via the cloud, or vice versa, thereby achieving continuity of the scene.
[0042] Figure 3 A data migration system for long-distance communication is illustrated. A first terminal and a second terminal communicate over a long distance. The first terminal communicates with the second terminal via a cloud. The data migration system also includes a mobile terminal, such as a mobile phone or tablet. With cloud involvement, data from the first terminal is migrated to the mobile terminal and then from the mobile terminal to the second terminal; alternatively, with cloud involvement, data from the second terminal is migrated to the mobile terminal and then from the mobile terminal to the first terminal.
[0043] The first terminal and the second terminal include, but are not limited to, in-vehicle terminals, smartphones, smart tablets, desktop computers, laptops, smart speakers, and other terminal devices.
[0044] The specific implementation methods of the embodiments of this disclosure will now be described in detail with reference to the accompanying drawings.
[0045] Figure 4This is a flowchart illustrating a data migration method according to an exemplary embodiment of the present disclosure. The data migration method is executed on a first terminal. Figure 4 As shown, data migration methods include: In step S401, the first scenario authorization information of the first terminal token held by the first terminal is obtained; In step S402, based on the first scene authorization information of the first terminal token, it is determined whether the scene authorized by the first terminal token matches the target scene.
[0046] The first terminal token is the token held by the first terminal, specifically the token issued to the first terminal by the cloud. This token carries an authorized scenario identifier, i.e., the first scenario authorization information, representing the scenario in which the token is permitted to perform data migration operations. For example, commuting to work or returning home from work.
[0047] For example, a first terminal may hold multiple first terminal tokens, and the multiple first terminal tokens correspond to multiple authorized scenarios, with each first terminal token corresponding to an authorized scenario one-to-one.
[0048] The target scenario refers to the business scenario corresponding to the data migration business to be performed this time. For example, the target scenario is a commuting scenario to work or a homecoming scenario.
[0049] Specifically, if the target scenario belongs to the scenario authorized by the first terminal token, then the scenario authorized by the first terminal token is determined to match the target scenario. For example, if the target scenario is a commuting scenario and the scenario authorized by the first terminal token is also a commuting scenario, then it is considered a scenario match.
[0050] In step S403, in response to the matching of the scenario authorized by the first terminal token with the target scenario and the acquisition of the migration trigger event, a migration data packet is generated.
[0051] In step S403, the matching of the scenario authorized by the first terminal token with the target scenario is considered an entry threshold for data migration. Meeting this condition indicates that the permission verification has passed, but it will not directly trigger the migration. A migration trigger event needs to be obtained simultaneously to generate a migration data packet.
[0052] Migration trigger events are events that characterize the need to initiate data migration services. Migration trigger events include: detecting a schedule event reminder (e.g., travel itinerary reminder), detecting that the terminal location leaves the target business scenario (e.g., the user leaves the home UWB range), and detecting that the terminal location enters the target business scenario (e.g., detecting access to in-vehicle Bluetooth, detecting access to home Wi-Fi, or entering the underground parking garage in the scenario of returning home from work).
[0053] In step S404, in response to the scenario authorized by the second terminal token held by the second terminal matching the target scenario, the migration data packet is sent to the second terminal.
[0054] Among them, the second terminal token is the token held by the second terminal, specifically the token issued to the second terminal by the cloud.
[0055] For example, a second terminal may hold multiple first terminal tokens, and the multiple second terminal tokens correspond to multiple authorized scenarios, with each second terminal token corresponding to an authorized scenario.
[0056] Specifically, if the target scenario belongs to the scenario authorized by the second terminal token, then the scenario authorized by the second terminal token is determined to match the target scenario. For example, if the target scenario is a commuting scenario and the scenario authorized by the second terminal token is also a commuting scenario, then it is considered a scenario match.
[0057] In addition to scene authorization information, the information carried in the first terminal token and the second terminal token also includes: user global ID; verification confidence snapshot; and device migration counter.
[0058] A user's global domain ID is a globally unique logical identifier belonging to the same user account. All devices bound to the same user account (including the first terminal and the second terminal) correspond to the same user's global domain ID; different user accounts correspond to different user's global domain IDs. This identifier is independent of the specific device identifier and does not change with the addition, deletion, or replacement of devices. The cloud can use the user's global domain ID to determine whether multiple devices belong to the same user account.
[0059] The confidence score snapshot is generated and stored during the initial authentication process, representing the user's credibility. In subsequent device replacement scenarios, the confidence score is used to determine whether supplementary authentication is required. Specifically, if the confidence score is below a preset threshold, the current device is deemed untrustworthy, triggering and executing supplementary authentication to complete user identity verification; if the confidence score is above or equal to the preset threshold, the device is deemed trustworthy, and supplementary authentication is waived.
[0060] The device migration counter records the number of times a token has been successfully migrated to a new device. Each time a token is successfully migrated across devices, the counter value increments. A higher counter value indicates a lower level of trust in the token. When the device migration counter value exceeds an abnormal threshold, the token is deemed to be at risk of being stolen and is automatically revoked. The number of successful token migrations to new devices refers to the number of times the token has been migrated within the same scenario. For example, in a commuting scenario, a first token is issued to the first device, with a counter value of 1. Then, the second device is verified, and a second token is issued to the second device, with a counter value of 2, and so on.
[0061] Furthermore, the scenarios authorized by the first terminal token and the second terminal token can be categorized into the valid scenario range. The valid scenario range refers to the applicable boundaries of the token configuration, which include: the range of devices allowed to use the token, the validity period of the token, and the available space range of the token; the token is only valid under the condition that these applicable boundaries are met.
[0062] The verification process checks whether the scenario authorized by the first terminal token matches the target scenario. Specifically, it checks whether the target scenario is within the valid scenario range of the first terminal token. If the target scenario is within the valid scenario range of the first terminal token, it is considered a match; if the target scenario is not within the valid scenario range of the first terminal token, it is considered a mismatch.
[0063] The verification process checks whether the scenario authorized by the second terminal token matches the target scenario. Specifically, it checks whether the target scenario is within the valid scenario range of the second terminal token. If the target scenario is within the valid scenario range of the second terminal token, it is considered a match; if the target scenario is not within the valid scenario range of the second terminal token, it is considered a mismatch.
[0064] The data migration method of this disclosure involves obtaining first scene authorization information from a first terminal token held by a first terminal; determining whether the scene authorized by the first terminal token matches the target scene based on the first scene authorization information; generating a migration data packet in response to the match between the scene authorized by the first terminal token and the target scene, and obtaining a migration trigger event; and then sending the migration data packet to the second terminal in response to the match between the scene authorized by the second terminal token held by the second terminal and the target scene. By binding scenes to the first and second terminal tokens, the data migration process is triggered when the authorized scenes bound to the two tokens match the scene to be migrated, i.e., the target scene. This addresses the technical pain point of discontinuous cross-device data migration links to a certain extent, achieving seamless continuity of scene data between different terminals.
[0065] In some embodiments of this disclosure, obtaining a migration trigger event includes: obtaining the distance between a first terminal and a second terminal; and generating a migration trigger event in response to the distance between the first terminal and the second terminal being less than a first distance. See also Figure 1 The first terminal and the second terminal communicate in the near field. When the distance between the first terminal and the second terminal is less than a first distance, it is detected that the first terminal is approaching the second terminal and the distance is small. This is considered as a data migration being triggered, and a migration trigger event is generated.
[0066] For example, the first terminal is a mobile phone and the second terminal is an in-vehicle device. The distance between the two is estimated by the Bluetooth signal strength. The first distance can be set to 3 meters or 5 meters. When the mobile phone Bluetooth establishes a connection with the in-vehicle Bluetooth and the estimated distance between the mobile phone and the in-vehicle device is less than the first distance, it is determined that the mobile phone is close to the in-vehicle device, which is regarded as the data migration being triggered, i.e., a migration trigger event is generated.
[0067] For example, the first terminal is a mobile phone and the second terminal is an in-vehicle device. The distance between the two is directly measured by the UWB ranging module. The first distance can be set to 1.5 meters. When the UWB detects that the distance between the mobile phone and the in-vehicle device is less than 1.5 meters, it is determined that the mobile phone is close to the in-vehicle device, which is regarded as the data migration being triggered, that is, a migration trigger event is generated.
[0068] For example, the first terminal is a mobile phone, and the second terminal is a smart home device (such as a smart speaker). Data from the mobile phone is migrated to the smart home device. The distance between the mobile phone and the smart speaker is estimated using the Wi-Fi Received Signal Strength Index (RSSI). The first distance can be set to 3 meters. When the estimated distance between the two is less than 3 meters, it is determined that the mobile phone is close to the smart speaker, which is considered as the data migration being triggered, i.e., a migration trigger event is generated.
[0069] In some embodiments of this disclosure, the method further includes: in response to the distance between the first terminal and the second terminal being less than a second distance, sending a first request message to the second terminal, the first request message being used to claim a second terminal token, wherein the second distance is less than the first distance, that is, compared to the triggering condition for generating a migration trigger event, the distance between the first terminal and the second terminal is further reduced; in response to receiving the second terminal token, obtaining the second scenario authorization information of the second terminal token; and determining whether the scenario authorized by the second terminal token matches the target scenario based on the second scenario authorization information of the second terminal token. The second terminal token carries an authorized scenario identifier, i.e., the second scenario authorization information, representing the scenario in which the token allows the execution of data migration services. The implementation method for determining whether the scenario authorized by the second terminal token matches the target scenario is equivalent to the implementation method for determining whether the scenario authorized by the first terminal token matches the target scenario.
[0070] See Figure 1 The first terminal and the second terminal communicate via near-field communication. The first terminal is detected as being close to the second terminal when the distance between them is less than a second distance. The first terminal sends a first request message to the second terminal to claim a token from the second terminal and to verify the token. In other words, when the first and second terminals communicate via near-field communication, the verification of the second terminal token is performed on the first terminal. Correspondingly, if scene data from the second terminal is migrated to the first terminal to achieve scene continuity, the verification of the first terminal token is performed on the second terminal.
[0071] For example, the first terminal is a mobile phone and the second terminal is an in-vehicle device. The distance between the two is estimated by the Bluetooth signal strength. The first distance can be set to 3 meters or 5 meters, and the second distance is smaller than the first distance, for example, the second distance is set to 1 meter. When the estimated distance between the mobile phone and the in-vehicle device is further reduced to less than the second distance, a first request message is sent to the second terminal.
[0072] For example, the first terminal is a mobile phone and the second terminal is an in-vehicle device. The distance between the two is directly measured by a UWB ranging module. The first distance can be set to 1.5 meters, and the second distance is less than the first distance, for example, the second distance is set to 0.6 meters. When the UWB detects that the distance between the two has further decreased to less than the second distance, a first request message is sent to the second terminal.
[0073] For example, the first terminal is a mobile phone, and the second terminal is a smart home device (such as a smart speaker). Data from the mobile phone is transferred to the smart home device. The distance between the mobile phone and the smart speaker is estimated using the Wi-Fi Received Signal Strength Index (RSSI). The first distance can be set to 3 meters, and the second distance is less than the first distance, for example, the second distance is set to 1.2 meters. When it is detected that the estimated distance between the two has further decreased to less than the second distance, a first request message is sent to the second terminal.
[0074] In some embodiments of this disclosure, obtaining a migration trigger event includes: a first terminal determining whether it has received a migration trigger message sent by the cloud; and the first terminal determining, in response to receiving the migration trigger message, that it has obtained a migration trigger event. For schemes involving cloud participation, see [link to relevant documentation]. Figure 2 The first and second terminals migrate scene data through the cloud. In this scenario, the cloud determines the migration trigger message based on business conditions and then sends it to the first terminal.
[0075] For example, the first terminal is a home computer and the second terminal is a company computer; a calendar service is deployed on the cloud side, and the cloud continuously monitors meeting schedule events in the calendar service; when the cloud detects an exit reminder event for an upcoming meeting, the cloud generates a migration trigger message and sends it to the home computer, which is the first terminal. After receiving the migration trigger message sent by the cloud, the home computer determines that it has obtained the migration trigger event, and can then trigger the subsequent migration process.
[0076] For example, the first terminal is a mobile phone, and the second terminal is a smart home speaker; the cloud obtains the location information reported by the mobile phone and the home location reported by the smart speaker. When the cloud recognizes that the mobile phone has returned to the home geofence range where the smart speaker is located, the cloud generates a migration trigger message and sends it to the mobile phone; the mobile phone receives the migration trigger message and confirms that it has obtained the migration trigger event.
[0077] For example, the first terminal is a mobile phone and the second terminal is an in-vehicle device; the cloud obtains the location information of the mobile phone and the location information of the in-vehicle device. When the cloud determines that the distance between the location of the mobile phone and the location of the in-vehicle device is less than a preset trigger distance (e.g., 4 meters), the cloud generates a migration trigger message and sends it to the mobile phone; after the mobile phone receives the migration trigger message, it determines that it has obtained the migration trigger event.
[0078] In some embodiments of this disclosure, the step of sending the migration data packet to the second terminal in response to a scenario authorized by a second terminal token held by the second terminal matching the target scenario includes: sending the migration data packet to the cloud in response to a scenario authorized by the second terminal token matching the target scenario, so that the migration data packet is sent to the second terminal via the cloud. See also Figure 2 The first terminal and the second terminal migrate scene data through the cloud. In this scenario, the first terminal and the second terminal communicate over a long distance. To migrate scene data from the first terminal to the second terminal, the first terminal needs to send migration data packets to the cloud, and then the cloud forwards the migration data packets to the second terminal.
[0079] In some embodiments of this disclosure, the method further includes: a first terminal sending a migration data packet to a mobile terminal (including a mobile phone), and then the mobile phone forwarding the migration data packet to a second terminal. Figure 3 The data migration system in China.
[0080] Figure 5 This is a flowchart illustrating another data migration method according to an exemplary embodiment of the present disclosure, applicable to near-field communication between a first terminal and a second terminal. Figure 5 The data migration method shown includes any one or any combination of steps S501, S502, S503, S504, S505, and S506, wherein steps S501, S502, and S506 are respectively related to... Figure 4 The steps S401, S402, and S404 in the data migration method shown correspond to each other and will not be repeated here.
[0081] In step S503, the first terminal detects the distance between the first terminal and the second terminal in response to the matching of the scene authorized by the first terminal token with the target scene; in response to the distance between the first terminal and the second terminal being less than a first distance, a migration data packet is generated.
[0082] In step S504, in response to the fact that the distance between the first terminal and the second terminal is less than the second distance, the first terminal sends a first request message to the second terminal. The first request message is used to claim the token of the second terminal, and the second distance is less than the first distance.
[0083] In step S505, the first terminal responds to obtaining the second terminal token and verifies whether the scenario authorized by the second terminal token matches the target scenario.
[0084] Figure 6 This is a flowchart illustrating another data migration method according to an exemplary embodiment of the present disclosure, applicable to long-distance communication between a first terminal and a second terminal. Figure 6 The data migration method shown includes any one or a combination of any of steps S601, S602, S603, and S604, wherein steps S601, S602, and S604... Figure 4 Steps S401 and S402 in the data migration method shown correspond to each other and will not be repeated here.
[0085] In step S603, in response to the scenario authorized by the first terminal token matching the target scenario and receiving a migration trigger message, a migration data packet is generated; In step S604, in response to the scenario authorized by the second terminal token matching the target scenario, the migration data packet is sent to the cloud so that the migration data packet is sent to the second terminal via the cloud.
[0086] Figure 7 This is a flowchart illustrating another data migration method according to an exemplary embodiment of the present disclosure, applicable to long-distance communication between a first terminal and a second terminal. Figure 7 The data migration method shown includes any one or a combination of any of steps S701, S702, S703, and S704, wherein steps S701, S702, and S703 are combined with... Figure 6 Steps S601, S602, and S603 in the data migration method shown correspond to each other and will not be repeated here.
[0087] In step S704, in response to the scenario authorized by the second terminal token matching the target scenario, the migration data packet is sent to the mobile phone so that the migration data packet is sent to the second terminal via the mobile phone.
[0088] In some embodiments of this disclosure, generating a migration data package includes: obtaining capability information of a second terminal; wherein the capability information can be represented by a capability description registry; the capability description registry is a structured data table used to store and register various capabilities possessed by the second terminal, recording descriptive information such as capability types, capability identifiers, capability parameters, and permission ranges supported by the second terminal; the registry can be maintained locally by the second terminal or registered in the cloud, and the first terminal can obtain complete capability information of the second terminal by reading the registry; determining a capability information set of the second terminal based on the capability information of the second terminal, wherein the capability information set can be represented by a capability list; selecting capabilities belonging to the capability information set of the second terminal from the capabilities to be migrated of the first terminal, and adding the selected capabilities to the capability set; generating the migration data package based on the capability set. That is, capabilities of the first terminal not included in the capability information set of the second terminal are not added to the capability set.
[0089] Capabilities are defined as the functions supported by the terminal, including permissions. For example, the map navigation software on the first terminal has permission to access the user's location, while the map navigation software on the second terminal does not. Similarly, the first terminal may have a music app installed, while the second terminal does not. The first terminal may have an office document application in an editing session, while the second terminal does not have that application installed; even if the document editing session data is migrated, the second terminal cannot restore the editing session. The first terminal may have a video call application with camera and microphone permissions granted, while the same video call application on the second terminal does not have camera permission; after migrating the video call service status, the second terminal cannot properly access the camera for video capture. The first terminal may have NFC near-field communication capabilities and support NFC card swiping; the second terminal lacks an NFC module, so even if the NFC service status data is migrated, the second terminal cannot perform NFC card swiping operations. Finally, the first terminal may have a Bluetooth headset connected and have Bluetooth audio output capabilities; the second terminal may not be paired with the Bluetooth headset, and after migrating the audio playback service status, the second terminal cannot output audio to the Bluetooth headset.
[0090] In terms of terminal capability comparison, there are three scenarios: the first terminal and the second terminal have the same capabilities; the first terminal has more capabilities than the second terminal; and the first terminal has fewer capabilities than the second terminal.
[0091] For example, taking the permission set of the source device (referring to the first terminal) as input, permission adaptation is automatically completed by calculating the semantic similarity of the device capability vectors, and a trusted time window and scene locking conditions are added to achieve fine-grained controlled flow of permissions during the migration process. Through the permission capability graph mapping algorithm, only the permissions corresponding to the actual capabilities of the target device (referring to the second terminal) are migrated, and the permissions corresponding to unavailable capabilities are not migrated.
[0092] When migrating data, if the first terminal supports a certain capability but the second terminal does not, even if the data corresponding to that capability is migrated to the second terminal, the second terminal will not be able to open the corresponding application or restore the corresponding business status. Therefore, it is necessary to build the above-mentioned capability set.
[0093] In some embodiments of this disclosure, the method further includes: the first terminal responding to the reauthorization operation by updating the capability set and generating an updated migration data packet based on the updated capability set. The reauthorization operation is initiated by the user; specifically, the second terminal detects and generates a function restriction notification message, informing the user which permissions have not been migrated and the reasons why. After the user performs reauthorization, the first terminal is notified.
[0094] In some embodiments of this disclosure, the method further includes: multiple first terminals, each containing migration data packets, and transmitting these migration data packets to a second terminal based on priority. The priority includes at least one of the following: device priority and data priority. This solution addresses data transmission conflicts and resource contention in concurrent migration scenarios involving multiple devices, eliminating the need for disordered batch transmission of all migration data packets. Prioritizing the transmission of high-priority data packets allows the second terminal to prioritize the recovery of core sessions and critical services, shortening the perceived availability waiting time for users. Simultaneously, priority strategies can be flexibly configured according to business requirements, accommodating migration needs in different scenarios and improving the scheduling rationality and transmission efficiency of multi-device session migration. Physical output resources (speaker channels, display area) are dynamically sliced and allocated to avoid preemptive conflicts. A fair rotation compensation mechanism is also implemented to prevent low-priority users from being unable to obtain resources for extended periods.
[0095] For example, data priority: multiple first terminals each contain video session data packets and background document data packets. If the priority of the real-time video session is set higher than that of the background document, then the migration data packet corresponding to the video session is transmitted first, allowing the second terminal to quickly resume the video call, while the document data is transmitted later.
[0096] For example, device priority: If a user has two first terminals, a mobile phone and a tablet, the device configured with the mobile phone has higher priority; when multiple devices initiate migration requests at the same time, the migration data packet of the mobile phone is sent to the second terminal first.
[0097] In some embodiments of this disclosure, the method further includes: sensing multiple users simultaneously approaching the device via UWB multi-point positioning, and performing independent token verification on each user in parallel to complete identity confirmation; subsequently, based on a priority scoring matrix, calculating user priority scores by comprehensively considering dimensions such as role, recent usage frequency, task urgency, and fair rotation compensation, allocating primary control permissions (full screen, main speaker channel) to the primary user with the highest score, while secondary users are allocated independent display partitions and independent audio rendering channels; periodically recalculating user priorities to achieve starvation protection and prevent low-priority users from being unable to obtain device resources for extended periods.
[0098] In some embodiments of this disclosure, generating the migration data package based on the capability set includes: combining the application runtime state, capability set, and scene context into atomic migration units, wherein the scene context represents the complete environmental semantic information required for a user to complete a business action in a predetermined time and space; performing format conversion processing on the atomic migration units to obtain atomic migration units of a predetermined format; and encrypting the atomic migration units of the predetermined format to obtain the migration data package. The problem of incomplete functionality after migration is solved by setting atomic migration units.
[0099] The runtime state of an application refers to the transient execution context that is generated during user interaction and changes dynamically over time. It is distinct from storage and can include dimensions such as playback progress (e.g., current playback position of music / video, playlist order), navigation state (e.g., current route, remaining distance, waypoints, real-time traffic conditions), meeting / call state (e.g., ongoing video conference, participant list, screen sharing status), document editing position (e.g., cursor position, unsaved changes, collaborative editing locked state), interactive form data (e.g., filled-out but not submitted form fields), and application process context (e.g., foreground and background application list, session state in each application's memory).
[0100] The scenario context representation is a structured expression of "what the user is currently doing, where they are, and what target they want to switch to." It is the "prediction and matching layer" in the three-element migration (application runtime state - capability set - scenario context). Environmental semantic information includes time features, geographical features, user behavior, device state, and task semantics. After receiving the information, the target device (the second terminal is the target terminal when migrating to the second terminal, and the first terminal is the target terminal when migrating to the first terminal) can combine this environmental semantics to reconstruct an adapted business operating environment under the target device's hardware / system conditions. This not only restores the state of a single application but also restores the entire working scenario, such as restoring the window layout.
[0101] For example, the application's runtime state is represented by editing markers for each document (video playback progress, webpage browsing position), while the scene context is like a description of the office environment (current time, window layout, external device information (e.g., screen brightness)). During migration, both types of information need to be packaged together so that the target device knows to locate each document in its corresponding editing position and restore the adapted office window layout.
[0102] Compared to simply migrating persistent storage data such as files and configurations, this solution incorporates application runtime state, migrating transient dynamic execution contexts such as playback progress, document cursor position, video conference sessions, and unsubmitted forms. Upon recovery of the target device, it can resume previous interaction processes instead of simply opening the original file, achieving seamless continuation of business sessions.
[0103] The atomic migration unit carries a set of capabilities. Before migration, the source device to be migrated (when migrating to the second terminal, the first terminal is the source device; when migrating to the first terminal, the second terminal is the source device) and the target device have been selected to support the capabilities. This avoids directly migrating data corresponding to capabilities that the target terminal does not support, preventing anomalies such as data migration being completed but the application being unable to be opened or the business status being unable to be restored, thus improving the compatibility of cross-device migration.
[0104] Atomic migration units are format-converted to a predetermined format to mask system and version differences between source and target devices, ensuring that different terminals can correctly parse atomic migration units.
[0105] For example, format conversion processing of atomic migration units includes standardized serialization format processing. A user-centric cross-device state snapshot protocol (SceneState) is proposed. Furthermore, the SceneState SDK standard interface is used to obtain application state data, i.e., the application's runtime state, decoupling the application runtime state from the device. Lossless migration and accurate recovery of state across platforms are achieved through standardized serialization formats. This solves the technical problem of complete loss of application runtime state (playback progress, navigation route, meeting status, document editing position) when users switch between different devices, requiring reopening and reconfiguration.
[0106] The migration data packets are encrypted to prevent data leakage or tampering during transmission, thereby improving data security during cross-device migration.
[0107] In some embodiments of this disclosure, the first terminal uses a local state manager to scan applications running in the foreground and background, obtains the runtime state of each application through the SceneState SDK interface (applications not adapted to the SDK are downgraded to UI snapshots), and packages the application runtime state, capability set, and scene context into atomic migration units (SceneStatePackage); the first terminal serializes the atomic migration units into SceneState format (or other compatible formats).
[0108] In some embodiments of this disclosure, atomic migration units of a predetermined format are encrypted to obtain a migration data packet. This includes: a first terminal sending a second request message to the cloud to request encrypted information. The encrypted information is a set of cryptographically related data issued by the cloud to the first terminal, with a core component being an encryption credential, which is the material used by the first terminal to encrypt the atomic migration units. The encryption credential can be understood as a key / encryption ticket used for data migration, uniformly issued by the cloud and not generated locally by the terminal. Upon receiving the encrypted information, the first terminal encrypts the atomic migration units of the predetermined format using the encrypted information to obtain the migration data packet. This method is applicable to scenarios involving remote communication between a first terminal and a second terminal, such as data migration between a home computer and a work computer.
[0109] Encrypted information is distributed by the cloud, and the first terminal requests it through a request message. This avoids the static storage of keys on the local terminal, reduces the risk of key leakage and local theft, and establishes a secure key source for remote cross-terminal migration.
[0110] The atomic migration unit contains the application runtime state, capability set, and scenario context, carrying a large amount of user business, environment, and interaction sensitive data. By encrypting the complete atomic migration unit with encryption information to obtain the migration data packet, the migration data packet can be prevented from being eavesdropped or tampered with during remote transmission between the first terminal and the second terminal, thus avoiding the leakage of user session state and office environment information.
[0111] The encrypted object is an atomic migration unit in a predetermined format that has already undergone format conversion. Encryption will not destroy the internal structured data format. After the target terminal receives the migration data packet, it can decrypt and restore the atomic migration unit in the standard format, without affecting the subsequent state recovery and scene reconstruction process.
[0112] In some embodiments of this disclosure, obtaining capability information of the second terminal includes: the first terminal sending a third request message to the cloud, the third request message being used to request capability information of the second terminal; and the first terminal receiving the capability information of the second terminal sent by the cloud. This is applicable to long-distance communication between the first terminal and the second terminal.
[0113] When the first terminal and the second terminal are isolated at a distance and cannot establish local communication directly, the first terminal does not need to directly probe the second terminal. It can obtain the capability information of the second terminal by sending a request to the cloud, thus solving the problem that the source terminal cannot directly collect the hardware and software capabilities of the second terminal in long-distance cross-device scenarios.
[0114] Once the first terminal obtains the registry, it can know in advance what capabilities the second terminal has and what capabilities it does not support. When constructing atomic migration units locally, it can perform state trimming and capability matching based on the registry, filtering out migration items that the second terminal does not support. This avoids packaging state data that the target device cannot process into the migration data packet, reducing invalid migration data and lowering the probability of subsequent migration failures and abnormal state recovery.
[0115] The second terminal registers its own capability information to the cloud for storage, and the cloud maintains the latest capability information. Even if the second terminal undergoes hardware changes or software version upgrades, the cloud will update the registry synchronously, and the first terminal will obtain the latest capabilities of the second terminal, avoiding migration and adaptation errors caused by using outdated capability information.
[0116] In some embodiments of this disclosure, obtaining capability information of the second terminal includes: a first terminal, in response to establishing a near-field communication link between itself and the second terminal, sending a fourth request message to the second terminal, the fourth request message being used to request capability information of the second terminal; and the first terminal receiving the capability information of the second terminal sent by the second terminal. This is applicable to near-field communication between the first and second terminals. When the first and second terminals are physically close and a near-field communication link (such as Bluetooth, NFC, or a local area network) can be established, access to a cloud server is no longer required. The first terminal directly requests capability information from the second terminal, eliminating cloud dependency, and can still obtain the capabilities of the second terminal even in offline environments without an external network. Furthermore, the near-field link allows for direct end-to-end interaction, resulting in shorter signaling links, faster response times for obtaining the capability registry, and improved migration efficiency.
[0117] In some embodiments of this disclosure, the method further includes: a first terminal acquiring environmental features and processing the environmental features to obtain a scene vector; the first terminal performing confidence prediction based on the scene vector to obtain a predicted confidence level; and the first terminal warming up the secure transmission channel in response to the predicted confidence level being greater than a confidence threshold.
[0118] The environmental characteristics include: time, geofencing, schedule, and UWB distance variation rate. The secure transmission channel is the secure transmission channel between the first terminal and the second terminal.
[0119] By integrating multi-dimensional environmental features such as UWB distance change rate, geofencing, time, and schedule into scene vectors, it goes beyond relying solely on distance for judgment. It can comprehensively determine whether the current environment is trustworthy and whether a scene migration is highly likely to occur. The UWB distance change rate can sense the dynamic trend of two devices moving closer or further apart, while geofencing, time, and schedule help determine user habits and reduce the probability of false triggers.
[0120] Secure channel warm-up is only performed when the prediction confidence exceeds the confidence threshold; warm-up is not initiated when the confidence is insufficient. This prevents the blind establishment of secure channels in low-probability, suspicious scenarios, conserves terminal computing power and wireless resources, and reduces unnecessary overhead.
[0121] In some embodiments of this disclosure, media buffer data is pre-transmitted under WiFi conditions in response to a prediction confidence level greater than a confidence threshold. This solution pre-loads the data in three stages—secure channel warm-up, application process pre-start, and media data pre-buffering—when the prediction confidence level exceeds the threshold. By the time the user arrives at the target device, the migration is essentially complete, requiring only a minimal confirmation, achieving a seamless switching experience with near-zero waiting time.
[0122] In some embodiments of this disclosure, a secure transmission channel warm-up is performed after the migration data packet is generated and before it is sent to the second terminal. The migration data packet has been packaged but not yet sent. At this point, a trustworthy scenario is predicted, and the encrypted channel is prepared in advance. Once transmission is triggered, the data packet can be transmitted directly through the secure channel without waiting for on-site handshake negotiation, significantly reducing handover latency and achieving seamless migration. This parallel warm-up action is based on the judgment of a trustworthy scenario where the prediction confidence exceeds a confidence threshold. Link warm-up and peer application startup are only initiated simultaneously in high-probability migration scenarios; this parallel operation is not triggered in low-confidence scenarios to avoid simultaneously occupying the computing power, memory, and wireless resources of both ends of the device, preventing unnecessary power consumption waste.
[0123] In some embodiments of this disclosure, the method further includes: a first terminal generating a preheating command in response to a prediction confidence level greater than a confidence level threshold, and sending the preheating command to a second terminal so that the second terminal starts the corresponding application process in response to the preheating command.
[0124] When a high-reliability migration scenario is identified, a preheating command is issued in advance to allow the second terminal to start the application process in advance. When the migration data packet is transmitted, the application process is already ready and the session state is loaded directly, which greatly reduces the application waiting time after the migration is completed and achieves seamless session continuation.
[0125] In some embodiments of this disclosure, after the migration data packet is generated and before it is sent to the second terminal, the secure transmission channel is preheated while the second terminal responds to the preheating command and launches the corresponding application process. On the one hand, the first terminal preheats the secure transmission channel between the two ends, completing key negotiation and encrypted link handshake in advance, eliminating the link establishment delay during the transmission phase; on the other hand, the second terminal synchronously responds to the preheating command and launches the target application process, completing application loading and resource initialization in advance, eliminating the application cold start delay. The two operations are executed in parallel, which further shortens the overall preprocessing time compared to processing link preheating and application launch sequentially, achieving faster scene transition.
[0126] In some embodiments of this disclosure, the first terminal generates a preheating command in response to a prediction confidence level greater than a confidence threshold, and sends the preheating command to the second terminal. This includes: the first terminal generating a preheating command in response to a prediction confidence level greater than a confidence threshold; and the first terminal sending the preheating command to the cloud, so that the preheating command can be sent to the second terminal via the cloud. This is applicable to situations where the first and second terminals communicate remotely, and the preheating command is forwarded to the second terminal via the cloud. By using the cloud as a relay node, the first terminal uploads the preheating command to the cloud, which then forwards it to the second terminal. This allows the preheating command to be sent normally and the application preheating of the second terminal to be triggered even in long-distance cross-network scenarios, broadening the applicable scenarios of the migration solution and no longer being limited to near-field local area network device migration. In addition, the cloud, as a relay service, maintains a long connection with both terminals, improving the success rate of preheating command delivery, ensuring that the second terminal can receive the preheating command in a timely manner and start the corresponding application process in remote scenarios, and ensuring the availability of the remote application preheating mechanism.
[0127] In some embodiments of this disclosure, during near-field communication, the first terminal directly sends the preheating command to the second terminal. In near-field scenarios (such as Bluetooth, Wi-Fi Direct, etc.), the two terminals can establish a local direct link, eliminating the need for cloud relay forwarding. This results in a shorter signaling transmission link, allowing the second terminal to receive the preheating command and start the application process for preheating more quickly, further reducing the overall preprocessing time.
[0128] In some embodiments of this disclosure, the method further includes: the first terminal sending a migration data packet to the second terminal in response to the matching of the target scene with the scene authorized by the second terminal token, the second terminal token being in a valid state, and the user's liveness score reaching a preset threshold.
[0129] The second terminal token being in a valid state indicates that it is within its validity period and is therefore usable. A user liveness score reaching a preset threshold constitutes user liveness verification for the second terminal, including verification of the user's heart rate, gait, etc.
[0130] By employing a triple verification mechanism—scenario permission matching, token validity verification, and user liveness verification—the system no longer relies on a single authentication condition. Migration data packets are only allowed to be sent when the token authorization scenario matches the target scenario of this migration, the token has not expired, and the user is verified as a genuine, live user (based on biometric features such as heart rate and gait). This effectively intercepts attacks from counterfeit devices, expired tokens, and static photos / videos, preventing unauthorized data theft or hijacking during migration.
[0131] Of course, the user liveness verification here is a lightweight verification process compared to the initial identity verification, which is a multimodal identity fusion verification. After the initial identity verification is successful, the cloud issues a token to the terminal. That is, the initial identity verification uses multimodal identity fusion verification, relying on multi-dimensional biometric / identity information to complete a complete and highly confident user rights confirmation and establish a trusted identity; subsequent migration processes only perform lightweight liveness verification, without having to repeat the complete multimodal verification. This avoids triggering complex multimodal fusion calculations with each migration, significantly reducing the computing power consumption, data collection overhead, and waiting latency during the migration process, and adapting to the requirements of smooth migration.
[0132] The lightweight verification process avoids the cumbersome operations of repeatedly verifying your identity by scanning your face when getting on a vehicle, entering a house, and unlocking devices in specific applications. After a trusted identity verification is passed once, the identity credential can be reused across multiple associated devices without having to perform a complete biometric comparison for each device. This reduces the computational overhead and waiting latency caused by identity verification and improves the user experience of cross-device continuous identity authentication.
[0133] In some embodiments of this disclosure, the first terminal continues to run while maintaining the application state in response to a network interruption during the migration process.
[0134] In some embodiments of this disclosure, the method further includes: in response to network recovery, the first terminal attempts to continue sending migration data packets, wherein the total number of attempts is less than or equal to a threshold number; in response to the total number of attempts reaching the threshold number and the migration data packets failing to migrate, a user prompt message is generated.
[0135] Network interruption during migration: Anomaly detection is completed through state packet transmission timeout or Merkle root hash verification failure; after an anomaly is triggered, the source device continues to run the current application state uninterruptedly, and the target device discards the incomplete state packets. After the network is restored, the system will perform a maximum of 3 automatic retries. If 3 consecutive retries fail, the user will be prompted to manually initiate a retry; this scenario adopts the consistency guarantee principle of source device priority. During the incomplete migration phase, only the source device is kept in an active state to avoid state fork issues caused by both ends running at the same time.
[0136] In some embodiments of this disclosure, the target device does not support the application to be migrated, and a downgrade processing strategy is adopted to execute in order of priority: the application is installed silently first if pre-authorization is obtained; if silent installation is not possible, the read-only web version is enabled; if the web version is unavailable, the status package is cached locally on the target device, waiting for subsequent application installation; if none of the above strategies can be executed, a prompt notification is sent to the user.
[0137] In some embodiments of this disclosure, if the confidence level of biometric identification is insufficient or identification fails, a tiered degradation verification mechanism is adopted: a maximum of 2 biometric retries are performed first; if the retry fails, the system switches to PIN code or pattern verification; if it still fails, Bluetooth proximity verification of the paired device is enabled; if the verification fails 5 times in a row, the device is locked for 30 seconds and the security event is recorded.
[0138] In some embodiments of this disclosure, if the token expires during migration, the corresponding handling method is as follows: the target device caches the received status packet, and the cache is valid for 24 hours; after the user completes the lightweight PIN verification, the cached status packet can be directly loaded and used without re-collecting biometric features.
[0139] In some embodiments of this disclosure, to address cross-ecosystem compatibility issues, the Device Capability Registry is used as a protocol conversion gateway: a whitelist of state fields supported by various devices is maintained, and only fields supported by the target device's registry declaration are transmitted during the migration process; third-party vendors can complete the access by implementing the SceneState SDK interface without relying on any closed ecosystem private protocols.
[0140] In some embodiments of this disclosure, the method further includes: responding to the existence of a differential data packet between the current migration data packet and the historical migration data packet, sending the differential data packet to the second terminal. This mainly addresses the scenario of migration interruption. If a network interruption, temporary device offline, or other anomaly causes transmission to stop during the migration process, it is not necessary to resend the complete migration data packet; only the current data packet to be migrated is compared with the historical migration data packet that has been successfully sent to the second terminal, the differential data packet between the two is extracted and transmitted, and the second terminal receives the differential data packet and merges it with the locally cached historical data packet to restore the complete migration data.
[0141] Figure 8 This is a flowchart illustrating a data migration method according to an exemplary embodiment of the present disclosure. The data migration method is executed in the cloud. Figure 8 As shown, data migration methods include: In step S801, the first biometric feature uploaded by the first terminal and the second biometric feature uploaded by the second terminal are received. For example, the first and second biometric features are multimodal biometric features, which include one or more of the following: voiceprint, face, palmprint, iris, heart rate, and gait features. Multimodal biometric features support verification by selecting one or more of these features in combination. Terminals with strong hardware capabilities can use high-security combinations such as face and iris recognition; wearable devices can use non-intrusive features such as heart rate and gait; in camera-limited scenarios, voiceprint and palmprint can be used, adapting to heterogeneous terminals such as mobile phones, tablets, and smart wearables, expanding the applicable scenarios of the solution, and balancing flexible configuration of hardware cost and security level.
[0142] This system employs multiple biometric features for joint identity verification, overcoming the limitations of single biometric features being susceptible to environmental interference and forgery. Different modalities are cross-verified, preventing the overall identity verification from failing when a single feature is counterfeited. This effectively resists attacks targeting single biometric methods, such as photo, audio, and video captures, thereby increasing the confidence in user identity verification.
[0143] In step S802, the user identity of the first terminal is verified based on the first biometric feature, and the user identity of the second terminal is verified based on the second biometric feature. In step S803, in response to the successful verification of the user identity of the first terminal, a first terminal token is issued to the first terminal; In step S804, in response to the successful verification of the user identity of the second terminal, a second terminal token is issued to the second terminal. The first terminal token includes authorization information for a first scenario, and the second terminal token includes authorization information for a second scenario. The first terminal token and the second terminal token are used for authentication during the data migration process between the first terminal and the second terminal.
[0144] The cloud verifies user identity based on biometrics; upon successful verification, the cloud issues a first terminal token to the first terminal and a second terminal token to the second terminal. Furthermore, by using the first and second terminal tokens for authentication during data migration between the first and second terminals, seamless data continuity across different terminals is achieved.
[0145] In some embodiments of this disclosure, the method further includes: verifying whether the count value carried by the first terminal token and / or the second terminal token exceeds a preset value, wherein the count value represents the cumulative number of token migrations; and reclaiming the verified first terminal token and / or second terminal token in response to the count value exceeding the preset value. That is, if the count value carried by the first terminal token exceeds the preset value, the first terminal token is reclaimed; if the count value carried by the second terminal token exceeds the preset value, the second terminal token is reclaimed.
[0146] The count value here is the count value of the device migration counter. Preset values are set for different scenarios; for example, a preset value of 3 is set for the commuting scenario, and a preset value of 4 is set for the homecoming scenario.
[0147] Alternatively, segmented processing can be implemented. If the cumulative number of token migrations falls within the first range, the token is issued and used normally. If the cumulative number of token migrations falls within the second range, the frequency of liveness detection verification is increased and / or the number of liveness detection verification items is added, such as one or more of the following: heart rate liveness verification, action command liveness verification, blink dynamic liveness verification, and voiceprint dynamic response verification. If the cumulative number of token migrations falls within the third range, a comprehensive risk assessment is triggered. If it is determined to be high-risk, the token is immediately revoked. The maximum value of the first range is less than the minimum value of the second range, and the maximum value of the second range is less than the minimum value of the third range.
[0148] For example, if the cumulative number of token migrations is 1–5, the tokens are issued and used normally; if the cumulative number of token migrations is 6–9, the verification frequency and / or verification items for liveness detection are increased; if the cumulative number of token migrations is ≥10, and there is a concentrated surge in migration activity within a short period, the tokens are immediately revoked. In other words, a cumulative number of token migrations of 1–5 is considered low security risk, and tokens are issued and authenticated normally according to the original strategy, without increasing additional verification overhead, ensuring smooth migration; a cumulative number of token migrations of 6–9 is considered an increased risk, and the frequency of liveness detection collection and verification is proactively increased, along with the frequency of real-time liveness verification, to prevent token issuance errors; a cumulative number of token migrations ≥10 triggers a comprehensive risk assessment, combining the time concentration of migration activity, abnormal geographical location, and other multi-dimensional contextual information for risk judgment; if it is determined to be a concentrated surge in migration operations within a short period, it is considered high risk, and the tokens are immediately revoked.
[0149] In some embodiments of this disclosure, the method further includes: cloud-based verification of whether the holding duration of the first terminal token and / or the second terminal token exceeds a duration threshold; and cloud-based retrieval of the verified first terminal token and / or second terminal token in response to the holding duration exceeding the duration threshold. That is, the first terminal token is reclaimed if its holding duration exceeds the duration threshold; and the second terminal token is reclaimed if its holding duration exceeds the duration threshold.
[0150] The holding duration refers to the continuous holding time of the token on the terminal side from the moment the token is issued in the cloud to the current verification moment. Different duration thresholds can be configured for different business scenarios. For example, the home-returning scenario belongs to a long-term trusted home environment, and the session migration requirement between terminals lasts longer, so a longer duration threshold is configured; the commuting scenario is mostly a short-term cross-device migration during the day, and the business flow can generally be completed on the same day, so a shorter threshold is set; the temporary visitor scenario only requires a one-time migration, so a short-term threshold is used. As an example, in the commuting scenario, the token duration threshold is set to 24 hours; in the home-returning scenario, the token duration threshold is set to 72 hours; and in the temporary migration scenario, the token duration threshold is set to 2 hours.
[0151] In some embodiments of this disclosure, state recovery is also performed step by step on the target device side according to application priority, and a scheduling strategy of prioritizing the recovery of foreground applications and delaying the recovery of background applications is adopted to ensure that the services that the user is interacting with are quickly ready.
[0152] In some embodiments of this disclosure, after the state is restored, a lightweight confirmation card that can be cancelled is displayed to the user; at the same time, an entry point for undoing the migration operation is retained on the source device to provide the user with an operation channel for reversing the process later.
[0153] In some embodiments of this disclosure, an atomic rollback mechanism is also included when a user initiates a cancellation command: the target device terminates the restored application process, and the source device reverts to a snapshot of the state before the migration, ensuring consistency of the service state.
[0154] Figure 9 This is a flowchart illustrating yet another data migration method according to an exemplary embodiment of the present disclosure. The data migration method is executed on a second terminal. Applied to... Figure 1 The first and second terminals shown are in near-field communication; it is also applied to... Figure 2 The illustration shows long-distance communication between a first terminal and a second terminal in the cloud; it is also applied to... Figure 3 This illustrates long-distance communication between a first terminal and a second terminal, including cloud and mobile terminals.
[0155] like Figure 9 As shown, data migration methods include: In step S901, the second scenario authorization information of the second terminal token held by the second terminal is obtained; In step S902, based on the second scenario authorization information of the second terminal token, it is determined whether the scenario authorized by the second terminal token matches the target scenario; In the case of long-distance communication between the first terminal and the second terminal, the verification step of determining whether the scenario authorized by the token of the second terminal matches the target scenario is executed locally on the second terminal.
[0156] In step S903, in response to the matching of the scenario authorized by the second terminal token with the target scenario, a migration data packet is received; In step S904, the migration data packet is subjected to security processing to obtain migration data; The process of performing security processing on the migration data packets to obtain the migration data includes: the second terminal decrypting the migration data packets to obtain the decrypted data packets, which are the migration data. In step S905, the application's running state is restored based on the migration data.
[0157] The process of restoring the application's running status based on migration data includes: the second terminal restoring the status of each application based on the decrypted data packets.
[0158] The applications include one or more of the following: video playback applications, instant messaging applications, document editing applications, web browser applications, and online conferencing applications. For example, for video playback applications, the playback progress, volume, and playback speed are restored to their pre-migration state, allowing playback to continue directly on the second terminal; for instant messaging applications, the chat window, unread message context, and currently being typed text are restored; for document editing applications, the document cursor position, edited content, and selected area are restored, allowing continued editing; for web browser applications, open tabs, webpage scroll position, and filled-in form content are restored; and for online conferencing applications, the meeting access status, microphone / camera on / off status, and screen sharing status are restored.
[0159] For example, in near-field communication between the first terminal and the second terminal, the second terminal receives migration data packets sent by the first terminal; in long-distance communication between the first terminal and the second terminal, the second terminal receives migration data packets sent by the cloud; in other long-distance communication between the first terminal and the second terminal, the second terminal receives migration data packets sent by the mobile terminal. In this scenario, both the cloud and the mobile terminal only act as data relays and do not decrypt the data.
[0160] By decrypting the received encrypted migration data packets and restoring the application state based on the decrypted data packets, seamless cross-device application migration is achieved. The migration data packets carry a snapshot of the runtime context of each application on the first terminal. After decryption, the second terminal can read the application's page information, session parameters, runtime variables, and other state data, directly restoring the application to its runtime state at the time of migration initiation, without requiring the user to log in again, reopen the page, or manually configure business parameters. Simultaneously, the migration data packets are transmitted with end-to-end encryption, and the decryption operation is performed locally on the second terminal, ensuring data security during the migration process and preventing plaintext leakage.
[0161] In some embodiments of this disclosure, before decrypting the migration data packet to obtain the decrypted data packet, the second terminal verifies the migration data packet, specifically including Merkle root hash integrity verification; the migration data packet is then decrypted after the verification passes.
[0162] In some embodiments of this disclosure, obtaining second scenario authorization information of a second terminal token held by a second terminal includes: the second terminal obtaining the second scenario authorization information of the second terminal token in response to the distance between the user and the second terminal being less than a third distance. That is, the second terminal verifies the second terminal token based on the second scenario authorization information of the second terminal token in response to the distance between the user and the second terminal being less than a third distance.
[0163] For example, the third distance is 0.3m, 0.5m, 0.7m, etc.
[0164] The distance between the user and the second terminal is used as the token verification trigger condition, and token verification is only initiated when the user is close to the second terminal. In long-distance communication scenarios, the token verification model integrated locally on the second terminal is used to complete local token verification, eliminating the need for real-time authentication in the cloud, reducing network latency and signaling interaction overhead. At the same time, it verifies whether the token authorization scenario matches the target scenario, preventing token theft across scenarios and improving the security of long-distance cross-terminal migration.
[0165] In some embodiments of this disclosure, the method further includes: in response to a scenario authorized by the second terminal token matching the target scenario, sending a notification message to the cloud or mobile terminal, so that the cloud or mobile terminal sends the migration data packet in response to the received notification message. This method is applied to long-distance communication between a first terminal and a second terminal. Verification of the second terminal token is performed locally on the second terminal, which has a token verification model integrated locally. Since the first terminal has pre-migrated the migration data packet to the cloud or mobile terminal, the cloud or mobile terminal can send the migration data packet to the second terminal after receiving the notification message.
[0166] In some embodiments of this disclosure, the second terminal, in response to receiving a preheating command, initiates a corresponding application process. This is applied to near-field communication between the first and second terminals, where the second terminal receives a preheating command sent by the first terminal; and to long-distance communication between the first and second terminals, where the second terminal receives a preheating command relayed via the cloud.
[0167] Starting the corresponding application process: This refers to the second terminal, upon receiving the warm-up command, pre-creating a process instance of the target application, loading the application's basic runtime libraries and resources, and completing the initialization of the application's runtime environment. This prepares the application for subsequent restoration of its business state based on the migration data package. This operation only starts the application's basic runtime environment and does not load the application state data from the first terminal.
[0168] Before receiving migration data packets, the corresponding application process is pre-launched and the basic application runtime environment is initialized, avoiding temporary application loading after receiving the migration data packets and eliminating application cold start time. After decrypting the migration data packets, application state data can be directly injected into the ready application process, quickly restoring the application state and significantly reducing the waiting latency for cross-terminal session migration, achieving a near-seamless application continuity experience. At the same time, target applications are pre-warmed on demand rather than all applications, avoiding the memory consumption and power waste caused by indiscriminately pre-launching all applications, balancing migration speed and terminal resource consumption.
[0169] In some embodiments of this disclosure, the method further includes: after the corresponding application process is started, the second terminal generates a confirmation prompt message, which is used to prompt the user to confirm or cancel the data migration; the second terminal receives the migration data packet in response to receiving the confirmation instruction; the second terminal refuses to receive the migration data packet in response to receiving the cancellation instruction.
[0170] When communicating over long distances, a confirmation prompt can be displayed on your mobile phone / watch / wearable device.
[0171] During near-field communication, a confirmation prompt message can be displayed on the first terminal / mobile phone / wearable device.
[0172] After the application process on the second terminal is ready, a confirmation prompt message is displayed to the user, who can choose to confirm or cancel the data migration. The second terminal will only start receiving migration data packets after receiving the user's confirmation instruction; if a cancellation instruction is received, it will refuse to receive migration data packets.
[0173] By using user-initiated authorization, the transmission of migration data is ensured to be user-driven, preventing unauthorized migration and enhancing the security and user-friendliness of cross-device migration solutions.
[0174] In some embodiments of this disclosure, the second terminal further includes: automatically detecting and generating a function-restricted prompt message to inform the user which permissions have not been migrated and the reasons why. The function-restricted prompt message indicates which capabilities of the first terminal have not been migrated to the second terminal. After migration is complete, the second terminal detects and outputs the function-restricted prompt message, informing the user of the unmigrated capabilities and the reasons for their restriction. This method can eliminate the functional expectation deviation caused by differences in cross-terminal hardware and systems, allowing users to clearly understand the boundaries of the migrated capabilities, reducing invalid operations, and improving the transparency and user experience after migration.
[0175] It should be noted that, in this disclosure, the source device refers to the device that sends the migration data packet, and the target device refers to the device that ultimately receives the migration data packet.
[0176] Embodiments of this disclosure also relate to a specific data migration method, including: Step 1: Initial Verification Process: The cloud receives multimodal biometric data uploaded by the terminal, performs fusion comparison (e.g., weighted fusion comparison), and completes user identity verification. After successful identity verification, the cloud issues a token to the terminal. The token carries the following information: user global ID; verification confidence snapshot; valid scenario range; device migration counter.
[0177] By using scene-bound tokens, the results of the first complete biometric verification can be reused across devices within the effective scene range, which can reduce the verification delay of subsequent device switching without sacrificing security; the token carries a confidence snapshot, scene range and migration counter, and combines continuous liveness detection to maintain the trust score.
[0178] Step 2: Assuming both the source and target devices have received their tokens, prepare for the data migration, including verifying whether the tokens of the source and target devices match the target scenario, triggering the migration, and preparing the migration data packets. Step 21: Triggering the migration: There are two scenarios: First remote transmission: The cloud detects a schedule reminder (e.g., detects that the user is about to go out), or the cloud receives a message that the user has left the home UWB range, generates a migration trigger message, and sends the migration trigger message to the source device; Second near-field transmission: The source device detects that the distance between itself and the target device falls within the near-field transmission range and automatically triggers migration.
[0179] The two scenarios also include: mobile phones or wearable devices reminding users whether they are ready to migrate data, and users can choose whether to migrate according to their needs.
[0180] Step 22: Preparation of migration data packets: Once the migration is triggered, preparation of the atomic migration unit begins. The atomic migration unit includes the application's runtime state, permission set (equivalent to capability set), and scenario context. The permission verification operation is performed on the source device: the source device obtains the capability information of the target device; based on the capability information, the source device packages the permissions supported by the target device and removes the permissions not supported by the target device, generating a permission set.
[0181] At the same time, the source device generates a prompt message for permissions that the target device does not support and migrates with the atomic migration unit. The source device queries the target device's capability information to obtain a list of capabilities supported by the target device. For each permission to be migrated, it checks whether the target device has the corresponding capability. If it supports it, it is included in the permission set; otherwise, it is not included. The atomic migration unit only contains the set of supported permissions. When the target device applies the permission migration token, it automatically detects and generates a function restriction prompt message to inform the user which permissions have not been migrated and the reason.
[0182] The source device serializes the atomic migration units into WorkState format (other formats are also possible). The source device uses a local state manager to scan foreground and background applications, obtains the runtime state of each application through the SceneStateSDK interface (applications not adapted to the SDK are downgraded to UI snapshots), and packages them into atomic migration units (SceneState Packages). The source device serializes the atomic migration units into SceneState format (or other compatible formats).
[0183] In addition, permission migration tokens are generated based on the capability set and bound to roaming tokens with scenario binding (e.g., first terminal token, second terminal token) for permission verification and management.
[0184] Step 23: Encrypting the migration data packet: There are two scenarios: First remote transmission: The source device requests an encryption token from the cloud, the cloud returns encryption material to the source device, the source device uses the encryption material to encrypt the serialized data packet to obtain an encrypted data packet; the encrypted data packet is then transmitted to a mobile phone or to the cloud.
[0185] If a mobile phone is involved in the solution, the mobile phone will then transmit the encrypted data packet to the target device. In solutions where no mobile phone is involved, the encrypted data packets will be transmitted from the cloud to the target device.
[0186] Second near-field transmission: The source device encrypts the serialized data packet to obtain an encrypted data packet; the encrypted data packet is then transmitted to the target device.
[0187] Step 3: Preloading Step: Features such as time, geofencing, schedule, and UWB distance change rate are encoded into scene vectors. When the prediction confidence exceeds a threshold, the preheating safety channel and the target device application process are preheated in advance (note...).
[0188] Preloading is performed locally on the source device: the source device continuously collects environmental features, encodes them locally into scene vectors, and predicts the target device; once the prediction confidence exceeds a threshold, the source device sends a preheating command to the target device, and the target device responds by launching the corresponding application process; the source device simultaneously preheats the secure transmission channel. The cloud only acts as a data relay node for far-field transmission and does not participate in the generation of prediction and preheating commands.
[0189] By preloading the source device and warming up the target device, a significant amount of preparatory work is completed without the user's awareness, with lightweight verification only performed in the final stage of migration preparation.
[0190] Step 4: The user is prompted to confirm their migration intention; Remote transmission: The source device initiates the migration, the data is transferred to the target device via the cloud, the target device restores its status, the target device generates a confirmation prompt, a pop-up window appears on the mobile phone / watch / wearable device, and the user confirms or cancels; Near-field transmission: The source device initiates migration, data is directly transmitted to the target device, the target device restores its status, the target device generates a confirmation prompt, a pop-up window appears on the source device / mobile phone / wearable device, and the user confirms or cancels.
[0191] Step 5: Perform authentication, i.e., token lightweight verification.
[0192] Lightweight token verification (performed before migration): Before the source device initiates the migration, lightweight verification is performed on the target device's token. The verification includes: token signature validity, whether the current scenario is within the token authorization range, and whether the liveness score meets the requirements.
[0193] Near-field transfer: The source device directly verifies the target device's SBRT token, and after successful verification, it enters the migration process.
[0194] Remote transmission: The source device sends a migration request to the target device via the network. The target device verifies its own token locally. After successful verification, it returns to a ready state, and the source device begins transmitting data packets via the cloud. The cloud only acts as a data relay and does not participate in token verification.
[0195] In some cases, the order of steps 4 and 5 can be interchanged. In some cases, step 4 can be omitted.
[0196] Step 6: The actual data migration steps; There are two scenarios: First type: Near-field transmission The source device transmits the encrypted data packet directly to the target device via LAN / Bluetooth; upon receiving the packet, the target device verifies the integrity of the Merkle root hash, and if successful, decrypts it and restores the state according to application priority.
[0197] The second method: remote transmission (with mobile phone involved).
[0198] The source device sends encrypted data packets to the mobile phone; the mobile phone acts as a relay node and forwards the encrypted data packets to the target device; the target device verifies the integrity of the Merkle root hash, and decrypts and restores the state after successful verification.
[0199] The third method: remote transmission (without mobile phone involvement)
[0200] The source device sends encrypted data packets to the cloud; the cloud, acting as a relay node, forwards the encrypted data packets to the target device; the target device verifies the integrity of the Merkle root hash, and upon successful verification, decrypts and restores its state. In all three scenarios, both the cloud and the mobile phone only act as data relays and do not decrypt the data.
[0201] Step 7: Loading the environment and restoring the state; The target device decrypts the received encrypted data packets, loads the environment, and restores the state of each application.
[0202] When using the solution disclosed herein, navigation, music, video calls, meetings, and document progress applications remain uninterrupted when switching between mobile phones and in-vehicle systems, in-vehicle systems and smart home systems, in-vehicle systems and office equipment, or home computers and office equipment.
[0203] The following section will illustrate the implementation of continuous data migration in two typical application scenarios.
[0204] The first typical application scenario: commuting to work. (See also...) Figure 10 Specifically, it includes six stages: getting ready to leave home, leaving home, commuting, arriving at the office, entering the office, and starting work.
[0205] The "preparing to leave" phase is primarily responsible for capturing and serializing work status; this includes: the user preparing to work at home, the system detecting schedule reminders, automatically capturing work context such as document editing status, meeting progress, and browser tabs, and preparing for state transition; see [link to implementation details] for more information. Figure 11 .
[0206] The "away from home" phase is primarily responsible for triggering state transitions and encrypted transmission. This includes: when a user leaves the home's UWB range, the system triggers a state transition, encrypting and transmitting work environment data to the mobile phone, including document layout, volume settings, and privacy permissions. For detailed implementation details, please refer to [link to implementation details]. Figure 12 .
[0207] During the commute, the system is primarily responsible for maintaining the user's work status and pre-connecting to the office. This includes: keeping the user's work status synchronized while they are en route, predicting arrival time based on schedule and location, pre-connecting office devices, and preparing to restore the work environment. For detailed implementation details, please refer to [link to implementation details]. Figure 13 .
[0208] The arrival-at-the-office phase is primarily responsible for UWB detection and identity verification; this includes: the user arriving at the office, the UWB base station detecting the user within its effective range, verifying identity through multimodal biometrics, and preparing to load the work environment. For detailed implementation details, please refer to [link to implementation details]. Figure 14 .
[0209] The "Entering the Office" phase primarily handles device activation and permission migration; this includes: upon user entry into the office, automatic activation of office equipment, loading of the user's work environment (document layout, volume settings, privacy permissions), and continued availability of cross-device clipboard and file access permissions. For detailed implementation details, please refer to [link to implementation details]. Figure 15 .
[0210] The initial phase primarily focuses on seamlessly restoring the user's work status; this includes ensuring continuity across all activities such as document editing positions, meeting progress, browser tabs, and IDE status, with real-time synchronization of clipboard content across devices. For detailed implementation details, please refer to [link to implementation details]. Figure 16 .
[0211] See Figure 10 The core technology stack includes document state serialization, continuous meeting progress, cross-device clipboard, continuous permission management, browser state migration, and enterprise-level security.
[0212] Document state serialization includes: accurately capturing document editing position, selection area, scroll position, and formatting settings, supporting a variety of office applications.
[0213] The meeting progress is continuous, including seamless migration of meeting status: participation status, microphone / camera settings, screen sharing, and chat history.
[0214] Cross-device clipboard features include: real-time synchronization of clipboard content, support for multiple formats such as text, images, and files, and end-to-end encrypted transmission.
[0215] Permission management includes: file access permissions, network permissions, and device permissions following the user's identity, automatically and dynamically configuring security for different devices, etc.
[0216] Browser state migration includes migrating browser tabs, login status, form data, and shopping cart content, while maintaining a complete browsing context.
[0217] Enterprise-level security includes: compliance with enterprise security policies, support for zero data loss prevention (DLP), and complete recording of all state migration operations in audit logs.
[0218] The second typical application scenario: going home after get off work. See also... Figure 17Specifically, it includes six stages: approaching the vehicle, entering the vehicle, driving, arriving at the underground parking lot, arriving at the doorstep, and entering the home.
[0219] The "approaching the vehicle" phase is primarily responsible for UWB detection and identity recognition. This includes: the user, wearing a smartwatch, approaches the vehicle; the UWB module detects the user's approach within its effective range; the system automatically identifies the user and pre-starts vehicle settings. For detailed implementation details, please refer to [link to implementation details]. Figure 18 .
[0220] The vehicle entry phase is primarily responsible for biometric authentication and permission granting. This includes: when the user opens the car door, the vehicle's camera, microphone array, and wearable device simultaneously collect biometric data; multimodal fusion is used to verify identity and grant system permissions. For detailed implementation details, please refer to [link to implementation details]. Figure 19 .
[0221] During the driving phase, the system is primarily responsible for status synchronization and pre-connection to home. This includes: the user playing music and using navigation while driving; the system capturing the application status in real time and predicting the return time; and pre-connecting home devices in advance. For detailed implementation details, please refer to [link to implementation details]. Figure 20 .
[0222] The parking garage arrival phase is primarily responsible for triggering state transitions, including: after the user parks and turns off the engine, the system detects the parking status and triggers a state transition, encrypting and transmitting the complete application state, such as music progress and navigation route, to the phone. For detailed implementation details, please refer to [link to implementation details]. Figure 21 .
[0223] The "reaching the doorstep" stage is primarily responsible for secondary verification and permission transfer. This includes: when a user arrives at their doorstep, the home UWB base station detects the user within its effective range, performs lightweight secondary verification via wearable devices, and converts the vehicle's permissions to home permissions. For detailed implementation details, please refer to [link to implementation details]. Figure 22 .
[0224] The home entry phase primarily handles device activation and status restoration. Upon entering the home, smart speakers, TVs, lights, air conditioners, and other devices activate simultaneously, music playback resumes seamlessly, and navigation switches to pedestrian mode. For detailed implementation details, please refer to [link to implementation details]. Figure 23 .
[0225] See Figure 17 The core technology stack includes UWB positioning technology, multimodal biometrics, SceneState protocol, predictive preloading, dynamic permission migration, and zero-trust security architecture.
[0226] UWB positioning technology includes: supporting standard UWB positioning, enabling cell-level device discovery and user tracking, and automatically detecting user approach.
[0227] Multimodal biometrics includes the fusion of multiple biometric features such as face, voiceprint, fingerprint, and behavioral characteristics for secure and reliable identity verification.
[0228] The SceneState protocol includes: standardized field state serialization, support for incremental synchronization, and lightweight and efficient state transmission.
[0229] Predictive preloading includes: establishing connections in advance based on time series analysis and user behavior prediction to achieve seamless migration.
[0230] Dynamic permission migration includes: permissions follow user identity rather than device, and supports a fine-grained migration and automatic revocation mechanism.
[0231] Zero-trust security architecture includes: never trust, always verify, least privilege access, continuous monitoring, and anomaly detection.
[0232] To implement the data migration solution disclosed herein, the following methods may be adopted: Figure 24 The architecture shown includes: user layer, perception layer, middleware layer, and execution layer.
[0233] The user layer includes: smartwatches, smartphones, tablets, laptops, and smart glasses; among them, smartwatches are equipped with heart rate monitoring, motion sensors, and UWB modules; smartphones are equipped with 5G communication modules, biometric recognition modules, and multimedia processing modules; tablets are equipped with WiFi communication modules, Bluetooth communication modules, and touch interaction modules; laptops are equipped with office application modules, document processing modules, and conferencing system modules; and smart glasses are equipped with AR display modules, voice interaction modules, and navigation projection modules.
[0234] The perception layer includes: a UWB positioning module, biometric data acquisition, behavior sensors, and environmental perception. Specifically, the UWB positioning module conforms to the 802.15.4a standard, offering centimeter-level accuracy and a range of 3-8 meters. The biometric data acquisition unit is used for voiceprint recognition, face recognition, palmprint recognition, and heart rate ID acquisition. Behavior sensors are used for door opening detection, seat sensing, and motion recognition. The environmental perception unit is used for temperature detection, light sensing, and sound acquisition.
[0235] The middleware layer includes: identity management, state management, permission management, and prediction management. Identity management implements global identity management, multimodal verification, and token management; state management implements scene serialization, state synchronization, and incremental updates; permission management implements permission arbitration, permission adaptation, and permission revocation; and prediction management implements behavior prediction, resource preloading, and cache management.
[0236] The execution layer includes: vehicle-mounted cockpit, whole-house smart home, mobile office, and wearable devices. Specifically, the vehicle-mounted cockpit controls seats, regulates the air conditioning system, manages the entertainment system, and provides navigation services; the whole-house smart home controls lighting, air conditioning, security systems, and home appliances; the mobile office enables document editing, meeting scheduling, email processing, and collaborative work; and the wearable devices provide health monitoring, notification push notifications, activity tracking, and payment functions.
[0237] To implement the data migration solution disclosed herein, an alternative architecture can be used, including a perception layer, an identity layer, a state layer, a migration control layer, and a device adaptation layer.
[0238] The perception layer is configured with a UWB positioning engine, biometric collector, and behavior sensor to detect user location, collect multimodal biometrics, and perceive user behavioral intent. The identity layer includes a global identity management unit and a token issuer and verifier to generate global identity identifiers and manage the entire lifecycle of tokens. The state layer is configured with a scene serialization engine and a differential synchronization manager to capture and serialize application states, calculate state differences, and perform compressed transmission. The migration control layer includes a dynamic permission arbitration module, a prediction preloading engine, and a conflict arbitrator to complete permission migration adaptation, target device prediction, resource preloading, and handle multi-user conflicts. The device adaptation layer is configured with a protocol conversion gateway and capability information to shield interface differences between different devices and ecosystems and provide a unified description of device capabilities.
[0239] The specific configurations of the global identity management unit include: the identity identifier, i.e., the user's global ID, is generated using a namespace hash based on the user's registration information, possessing global uniqueness and reproducibility; the token's validity period can be dynamically adjusted according to the scenario's risk level; it supports multiple users concurrently online on a single device; complete multimodal identity verification adopts a parallel reasoning mechanism of voiceprint, face, and palmprint, enabling rapid response; token verification is completed based on local signatures, independent of the network; cross-device tokens can achieve rapid synchronization in a local area network environment.
[0240] The specific configuration of the scene serialization engine is as follows: Existing technologies such as Android Activity state saving only support the state restoration of a single device and a single application; this module realizes the atomic packaging of multi-application states across heterogeneous devices, binds the states of multiple parallel running applications, the current set of permissions (i.e., capabilities), and the scene context into an indivisible migration unit SceneState Package, and adopts differential serialization combined with a hash tree verification mechanism to complete the efficient transmission and integrity guarantee of the state.
[0241] The dynamic permission arbitration module is specifically configured as follows: It proposes a permission capability graph mapping algorithm, encoding the source device's permission set and the target device's capability set into capability vectors respectively. Through semantic similarity or cosine similarity calculation, it achieves automatic cross-device permission adaptation, solving the problem that existing cross-device solutions require users to manually re-authorize each item. Permission migration and adaptation are automatically completed through capability vector cosine similarity calculation, supporting "direct migration / downgrade migration / marking as pending authorization." Furthermore, by binding with a token, permissions are automatically revoked when the token expires, preventing permission remnants.
[0242] The specific configuration of the predictive preloading engine includes: scene vectorization and multi-factor fusion prediction mechanism, which jointly encodes time features, geofence events, schedule information and UWB distance change rate into scene feature vectors, and predicts the target migration device through a lightweight classification model; when the prediction confidence exceeds the set threshold, the preloading process is automatically triggered, and a seamless migration control flow with prediction triggering and lazy confirmation characteristics is constructed.
[0243] To implement the data migration scheme of this disclosure, some embodiments of this disclosure also design a security architecture, including a zero-trust security architecture, layered security design, and privacy protection mechanisms.
[0244] Designed based on a zero-trust security architecture, it follows three core principles: First, it adheres to the principle of "never trusting, always verifying." Tokens are only used to reduce the overhead of repeatedly collecting complete biometric features; the verification process is not omitted. Each device switch performs a lightweight verification process involving token signature verification, scene range checking, and liveness scoring, with a verification latency of less than 20ms. Second, it follows the principle of least privilege, relying on a permission capability graph mapping algorithm to migrate only the corresponding permissions supported by the target device's capabilities, without migrating permissions associated with unavailable device capabilities. Third, it adopts a protection approach that assumes the system has been compromised, continuously monitoring the system. Once abnormal behaviors such as token replay attacks, exceeding migration limits, or cross-scene unauthorized access are detected, a token revocation operation is immediately triggered.
[0245] A layered security design is adopted, constructing a complete protection system from the device layer, transport layer, and application layer: At the device layer, a hardware security module protects the biometric template and token signing key, ensuring the key never leaves the hardware security module; a trusted execution environment (TEA) is used for multimodal fusion inference, ensuring the original biometric data does not leave the TEA; and a device fingerprint composed of the International Mobile Equipment Identity (IMEI) and hardware feature hash is used in token signing to prevent cross-device token forgery. At the transport layer, inter-device state packets use SM4 symmetric encryption combined with SM2 asymmetric handshake, generating a one-time session key for each migration based on a forward-secure key negotiation mechanism, ensuring that historical key leaks do not threaten the current session; two-way authentication is performed during token transmission, with the source and target devices mutually verifying each other's certificates. At the application layer, biometric templates are stored locally and not uploaded to the cloud, with only encrypted and anonymized feature vectors used for federated learning; static state packets are stored using SM4-GCM encryption with an integrity authentication tag, and SceneState data is verified using a Merkle hash tree, enabling detection of arbitrary field tampering.
[0246] A privacy protection mechanism is constructed, strictly adhering to the principle of data minimization: the mapping between scene types and transferable application types is configured by the user in the privacy control panel; the system does not preset fixed scene types, supports dynamic expansion, and does not hardcode migration paths; cross-ecosystem migration only transmits application-independent common status fields such as content ID, playback progress, and volume, without carrying platform-private fields; biometric behavior analysis is implemented based on local federated learning, with differential privacy noise added to the model gradient before uploading, and the original behavior data always remaining locally on the device. Simultaneously, complete user control is guaranteed, providing a fine-grained privacy control panel that allows users to independently manage the state transmission range of various applications under different migration paths; users are granted the right to data portability, supporting the export or deletion of locally stored behavior models and state history at any time; all migration events are written to a local anti-tampering audit log for user query and auditing, achieving transparent and traceable operations.
[0247] It should be noted that the above figures are merely illustrative representations of the processes included in methods according to some embodiments of this disclosure, and are not intended to be limiting. It is readily understood that the processes shown in the above figures do not indicate or limit the temporal order of these processes. Furthermore, it is readily understood that these processes may be executed synchronously or asynchronously, for example, in multiple modules.
[0248] The following are terminal embodiments of this disclosure, which can be used to execute the method embodiments of this disclosure. For details not disclosed in the terminal embodiments of this disclosure, please refer to the method embodiments of this disclosure.
[0249] Figure 25This is a block diagram illustrating a first terminal according to some embodiments of the present disclosure. (Refer to...) Figure 25 The first terminal includes: The first acquisition module 2501 is used to acquire the first scenario authorization information of the first terminal token held by the first terminal; The first determining module 2502 is used to determine whether the scene authorized by the first terminal token matches the target scene based on the first scene authorization information of the first terminal token. The generation module 2503 is used to generate a migration data packet in response to the matching of the scenario authorized by the first terminal token with the target scenario and the acquisition of a migration trigger event; The sending module 2504 is used to send the migration data packet to the second terminal in response to the scenario authorized by the second terminal token held by the second terminal matching the target scenario.
[0250] In some embodiments of this disclosure, the generation module is used to obtain the distance between the first terminal and the second terminal; in response to the distance between the first terminal and the second terminal being less than a first distance, the migration trigger event is generated.
[0251] In some embodiments of this disclosure, the first terminal is further configured to send a first request message to the second terminal in response to the first terminal being less than a second distance, the first request message being used to claim a second terminal token, wherein the second distance is less than the first distance; in response to receiving the second terminal token, obtain second scene authorization information of the second terminal token; and determine whether the scene authorized by the second terminal token matches the target scene based on the second scene authorization information of the second terminal token.
[0252] In some embodiments of this disclosure, the generation module is further configured to determine whether a migration trigger message sent from the cloud has been received; and in response to receiving the migration trigger message, to determine that the migration trigger event has been obtained.
[0253] In some embodiments of this disclosure, the sending module is further configured to send the migration data packet to the cloud in response to a match between the scenario authorized by the second terminal token and the target scenario, so as to send the migration data packet to the second terminal through the cloud.
[0254] In some embodiments of this disclosure, the generation module is further configured to obtain capability information of the second terminal; determine the capability information set of the second terminal based on the capability information of the second terminal; select capabilities belonging to the capability information set of the second terminal from the capabilities to be migrated of the first terminal, and add the selected capabilities to the capability set; and generate the migration data packet based on the capability set.
[0255] In some embodiments of this disclosure, the generation module includes a generation submodule, which is used to generate the migration data package based on the capability set. Specifically, the generation submodule is used to combine the application runtime state, the capability set, and the scene context into atomic migration units, wherein the scene context represents the complete environmental semantic information required for the user to complete business behavior in a predetermined time and space; to perform format conversion processing on the atomic migration units to obtain atomic migration units of a predetermined format; and to encrypt the atomic migration units of the predetermined format to obtain the migration data package.
[0256] In some embodiments of this disclosure, the generation submodule includes an encryption submodule, which is used to encrypt the atomic migration units of the predetermined format to obtain the migration data packet. Specifically, the encryption submodule is used to send a second request message to the cloud, the second request message being used to request encryption information; in response to receiving the encryption information, the encryption submodule uses the encryption information to encrypt the atomic migration units of the predetermined format to obtain the migration data packet.
[0257] In some embodiments of this disclosure, the generation module includes an acquisition submodule, which is used to retrieve the capability information of the second terminal. Specifically, the acquisition submodule is used to send a third request message to the cloud, the third request message being used to claim the capability information of the second terminal; and to receive the capability information of the second terminal sent by the cloud.
[0258] In some embodiments of this disclosure, the acquisition submodule is further configured to, in response to the establishment of a near-field communication link between the first terminal and the second terminal, send a fourth request message to the second terminal, the fourth request message being used to request capability information of the second terminal; and receive capability information of the second terminal sent by the second terminal.
[0259] In some embodiments of this disclosure, the first terminal is further configured to acquire environmental features, process the environmental features to obtain a scene vector, perform confidence prediction based on the scene vector to obtain a predicted confidence level, and preheat the secure transmission channel in response to the predicted confidence level being greater than a confidence threshold.
[0260] In some embodiments of this disclosure, the first terminal is further configured to generate a preheating instruction in response to the prediction confidence level being greater than the confidence threshold, and send the preheating instruction to the second terminal.
[0261] Figure 26 This is a block diagram illustrating a cloud-based solution according to some embodiments of this disclosure. (See also...) Figure 26 The cloud includes: The first receiving module 2601 is used to receive the first biometric feature uploaded by the first terminal and the second biometric feature uploaded by the second terminal. Verification module 2602 is used to verify the user identity of the first terminal based on the first biometric feature and to verify the user identity of the second terminal based on the second biometric feature. Distribution module 2603 is used to distribute a first terminal token to the first terminal and a second terminal token to the second terminal in response to successful user identity verification. The first terminal token includes first scenario authorization information, and the second terminal token includes second scenario authorization information. The first terminal token and the second terminal token are used for authentication during data migration between the first terminal and the second terminal.
[0262] In some embodiments of this disclosure, the cloud is also used to verify whether the count value carried by the first terminal token and / or the second terminal token exceeds a preset value, wherein the count value represents the cumulative number of token migrations; in response to the count value exceeding the preset value, the verified first terminal token and / or the second terminal token are reclaimed.
[0263] In some embodiments of this disclosure, the cloud is also used to verify whether the holding time of the first terminal token and / or the second terminal token exceeds a time threshold; in response to the holding time exceeding the time threshold, the verified first terminal token and / or the second terminal token are revoked.
[0264] Figure 27 This is a block diagram illustrating a second terminal according to some embodiments of the present disclosure. (Refer to...) Figure 27 The second terminal includes: The second acquisition module 2701 is used to acquire the second scenario authorization information of the second terminal token held by the second terminal; The second determining module 2702 is used to determine whether the scene authorized by the second terminal token matches the target scene based on the second scene authorization information of the second terminal token; The second receiving module 2703 is used to receive migration data packets in response to the scenario authorized by the second terminal token matching the target scenario; Processing module 2704 is used to perform security processing on the migration data packet to obtain migration data; Recovery module 2705 is used to restore the running state of the application based on the migration data.
[0265] In some embodiments of this disclosure, the second acquisition module is specifically used to acquire the second scenario authorization information of the second terminal token in response to the distance between the user and the second terminal being less than a third distance.
[0266] In some embodiments of this disclosure, the second terminal is further configured to send a notification message to the cloud or mobile terminal in response to the scenario authorized by the second terminal token matching the target scenario, so that the cloud or the mobile terminal sends the migration data packet in response to the received notification message.
[0267] In some embodiments of this disclosure, the second terminal is also used to start the corresponding application process in response to receiving a preheating command.
[0268] In some embodiments of this disclosure, the second terminal is further configured to generate a confirmation prompt message after starting the corresponding application process, the confirmation prompt message being used to prompt the user to confirm or cancel the data migration; receive the migration data packet in response to receiving a confirmation instruction; and refuse to receive the migration data packet in response to receiving a cancellation instruction.
[0269] Figure 28 This is a block diagram illustrating an electronic device according to an exemplary embodiment of the present disclosure. For example, the electronic device 2800 may be a mobile phone, computer, digital broadcasting terminal, messaging device, game console, tablet device, medical device, fitness equipment, personal digital assistant, etc. The electronic device includes a first terminal and a second terminal in embodiments of the present disclosure.
[0270] Reference Figure 28 The electronic device 2800 may include one or more of the following components: a processing component 2802, a memory 2804, a power supply component 2806, a multimedia component 2808, an audio component 2810, an input or output (I or O) interface 2812, a sensor component 2814, and a communication component 2816.
[0271] Processing component 2802 typically controls the overall operation of electronic device 2800, such as operations associated with display, telephone calls, data communication, camera operation, and recording operations. Processing component 2802 may include one or more processors 2820 to execute instructions to perform all or part of the steps of the methods described above. Furthermore, processing component 2802 may include one or more modules to facilitate interaction between processing component 2802 and other components. For example, processing component 2802 may include a multimedia module to facilitate interaction between multimedia component 2808 and processing component 2802.
[0272] Memory 2804 is configured to store various types of data to support the operation of electronic device 2800. Examples of this data include instructions for any application or method operating on electronic device 2800, contact data, phonebook data, messages, pictures, videos, etc. Memory 2804 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.
[0273] Power supply component 2806 provides power to various components of electronic device 2800. Power supply component 2806 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to electronic device 2800.
[0274] Multimedia component 2808 includes a screen that provides an output interface between the electronic device 2800 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touchscreen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensors may sense not only the boundaries of the touch or swipe action but also the duration and pressure associated with the touch or swipe operation. In some embodiments, multimedia component 2808 includes a front-facing camera and / or a rear-facing camera. When the electronic device 2800 is in an operating mode, such as a shooting mode or a video mode, the front-facing camera and / or the rear-facing camera may receive external multimedia data. Each front-facing camera and rear-facing camera may be a fixed optical lens system or have focal length and optical zoom capabilities.
[0275] Audio component 2810 is configured to output and / or input audio signals. For example, audio component 2810 includes a microphone (MIC) configured to receive external audio signals when electronic device 2800 is in an operating mode, such as call mode, recording mode, and voice recognition mode. The received audio signals may be further stored in memory 2804 or transmitted via communication component 2816. In some embodiments, audio component 2810 also includes a speaker for outputting audio signals.
[0276] I / O interface 2812 provides an interface between processing component 2802 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to, home buttons, volume buttons, power buttons, and lock buttons.
[0277] Sensor assembly 2814 includes one or more sensors for providing state assessments of various aspects of electronic device 2800. For example, sensor assembly 2814 can detect the on or off state of electronic device 2800, the relative positioning of components such as the display and keypad of electronic device 2800, changes in position of electronic device 2800 or a component of electronic device 2800, the presence or absence of user contact with electronic device 2800, the orientation, acceleration or deceleration of electronic device 2800, and temperature changes of electronic device 2800. Sensor assembly 2814 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. Sensor assembly 2814 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, sensor assembly 2814 may also include an accelerometer, gyroscope, magnetometer, pressure sensor, or temperature sensor.
[0278] Communication component 2816 is configured to facilitate wired or wireless communication between electronic device 2800 and other devices. Electronic device 2800 can access wireless networks based on communication standards, such as WiFi, 3G, 4G, 8G, other communication standards, or combinations thereof. In some embodiments of this disclosure, communication component 2816 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In some embodiments of this disclosure, communication component 2816 further includes a near-field communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented based on radio frequency identification (RFID) technology, Infrared Data Association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.
[0279] In some embodiments of this disclosure, the electronic device 2800 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the methods described above.
[0280] In some embodiments of this disclosure, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 2804 including instructions, which can be executed by a processor 2820 of an electronic device 2800 to perform the above-described method. For example, the non-transitory computer-readable storage medium may be a ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage device, etc.
[0281] In some embodiments of this disclosure, a non-transitory computer-readable storage medium is provided, which, when the instructions in the storage medium are executed by the processor of a mobile terminal, enables the mobile terminal to perform the data migration method of the embodiments of this disclosure.
[0282] In some embodiments of this disclosure, a computer program product is also provided, including a computer program or instructions that, when executed by a processor, implement the data migration method of the embodiments of this disclosure.
[0283] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this disclosure are indicated by the following claims.
[0284] It should be understood that this disclosure is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this disclosure is limited only by the appended claims.
Claims
1. A data migration method, characterized in that, include: Obtain the first scenario authorization information of the first terminal token held by the first terminal; Based on the first scenario authorization information of the first terminal token, determine whether the scenario authorized by the first terminal token matches the target scenario; In response to the scenario authorized by the first terminal token matching the target scenario and obtaining a migration trigger event, a migration data packet is generated; In response to the scenario authorized by the second terminal token held by the second terminal matching the target scenario, the migration data packet is sent to the second terminal.
2. The method according to claim 1, characterized in that, The acquisition of the migration trigger event includes: Obtain the distance between the first terminal and the second terminal; The migration trigger event is generated in response to the distance between the first terminal and the second terminal being less than a first distance.
3. The method according to claim 2, characterized in that, Also includes: In response to the fact that the distance between the first terminal and the second terminal is less than the second distance, a first request message is sent to the second terminal. The first request message is used to claim a token for the second terminal, wherein the second distance is less than the first distance. In response to receiving the second terminal token, obtain the second scenario authorization information of the second terminal token; Based on the second scenario authorization information of the second terminal token, determine whether the scenario authorized by the second terminal token matches the target scenario.
4. The method according to claim 1, characterized in that, The acquisition of the migration trigger event includes: Determine whether a migration trigger message has been received from the cloud; In response to receiving the migration trigger message, it is determined that the migration trigger event has been obtained.
5. The method according to claim 1, characterized in that, The step of responding to a scenario authorized by a second terminal token held by the second terminal matching the target scenario and sending the migration data packet to the second terminal includes: In response to the scenario authorized by the second terminal token matching the target scenario, the migration data packet is sent to the cloud so that the migration data packet can be sent to the second terminal through the cloud.
6. The method according to claim 1, characterized in that, The generation of the migration data packet includes: Obtain the capability information of the second terminal; Based on the capability information of the second terminal, determine the capability information set of the second terminal; Among the capabilities to be migrated in the first terminal, the capabilities belonging to the capability information set of the second terminal are selected, and the selected capabilities are added to the capability set; The migration data package is generated based on the set of capabilities.
7. The method according to claim 6, characterized in that, The process of generating the migration data packet based on the capability set includes: The application runtime state, the capability set, and the scene context are combined into an atomic migration unit, wherein the scene context represents the complete environmental semantic information required for the user to complete business behavior in a predetermined time and space. The atomic migration units are subjected to format conversion processing to obtain atomic migration units of a predetermined format; The atomic migration units of the predetermined format are encrypted to obtain the migration data packet.
8. The method according to claim 7, characterized in that, The atomic migration unit of the predetermined format is encrypted to obtain the migration data packet, which includes: Send a second request message to the cloud, the second request message being used to request encrypted information; In response to receiving the encrypted information, the atomic migration unit of the predetermined format is encrypted using the encrypted information to obtain the migration data packet.
9. The method according to claim 6, characterized in that, Obtaining the capability information of the second terminal includes: Send a third request message to the cloud, the third request message being used to request the capability information of the second terminal; Receive capability information of the second terminal sent by the cloud.
10. The method according to claim 6, characterized in that, Obtaining the capability information of the second terminal includes: In response to the establishment of a near-field communication link between the first terminal and the second terminal, a fourth request message is sent to the second terminal, the fourth request message being used to request the capability information of the second terminal; Receive capability information of the second terminal sent by the second terminal.
11. The method according to claim 1, characterized in that, Also includes: Obtain environmental features, and process the environmental features to obtain a scene vector; Based on the scene vector, a confidence score is predicted to obtain the predicted confidence score. In response to the prediction confidence level being greater than the confidence threshold, the secure transmission channel is preheated.
12. The method according to claim 11, characterized in that, Also includes: In response to the prediction confidence level being greater than the confidence threshold, a preheating instruction is generated and sent to the second terminal.
13. A data migration method, characterized in that, include: Receive a first biometric feature uploaded by a first terminal and a second biometric feature uploaded by a second terminal; The user identity of the first terminal is verified based on the first biometric feature, and the user identity of the second terminal is verified based on the second biometric feature. In response to the successful user identity verification of the first terminal, a first terminal token is issued to the first terminal. In response to the successful user identity verification of the second terminal, a second terminal token is issued to the second terminal. The first terminal token includes first scenario authorization information, and the second terminal token includes second scenario authorization information. The first terminal token and the second terminal token are used for authentication during data migration between the first terminal and the second terminal.
14. The method according to claim 13, characterized in that, Also includes: Verify whether the count value carried by the first terminal token and / or the second terminal token exceeds a preset value, wherein the count value represents the cumulative number of token migrations; In response to the count value exceeding the preset value, the verified first terminal token and / or second terminal token are revoked.
15. The method according to claim 13, characterized in that, Also includes: Verify whether the holding time of the first terminal token and / or the second terminal token exceeds the time threshold; In response to the holding time exceeding the time threshold, the verified first terminal token and / or second terminal token are revoked.
16. A data migration method, characterized in that, include: Obtain the second scenario authorization information of the second terminal token held by the second terminal; Based on the second scenario authorization information of the second terminal token, determine whether the scenario authorized by the second terminal token matches the target scenario; In response to the scenario authorized by the second terminal token matching the target scenario, a migration data packet is received; The migration data packet is subjected to security processing to obtain migration data; The application's running status is restored based on the migration data.
17. The method according to claim 16, characterized in that, The second scenario authorization information for obtaining the second terminal token held by the second terminal includes: In response to the user's distance from the second terminal being less than the third distance, the second scenario authorization information of the second terminal token is obtained.
18. The method according to claim 16, characterized in that, Also includes: In response to the scenario authorized by the second terminal token matching the target scenario, a notification message is sent to the cloud or mobile terminal, so that the cloud or mobile terminal sends the migration data packet in response to the received notification message.
19. The method according to claim 17, characterized in that, Also includes: Upon receiving a preheating command, the corresponding application process is launched.
20. The method according to claim 19, characterized in that, Also includes: After the corresponding application process is launched, a confirmation prompt message is generated, which is used to prompt the user to confirm or cancel the data migration. In response to receiving a confirmation command, the migration data packet is received; In response to receiving a cancellation command, the migration data packet is refused to be received.
21. A first terminal, characterized in that, include: The first acquisition module is used to acquire the first scenario authorization information of the first terminal token held by the first terminal; The first determining module is used to determine whether the scenario authorized by the first terminal token matches the target scenario based on the first scenario authorization information of the first terminal token. The generation module is used to generate a migration data packet in response to the matching of the scenario authorized by the first terminal token with the target scenario and the acquisition of the migration trigger event; The sending module is used to send the migration data packet to the second terminal in response to a scenario authorized by the second terminal token held by the second terminal matching the target scenario.
22. A cloud computing platform, characterized in that, include: The first receiving module is used to receive a first biometric feature uploaded by a first terminal and a second biometric feature uploaded by a second terminal. The verification module is used to verify the user identity of the first terminal based on the first biometric feature and to verify the user identity of the second terminal based on the second biometric feature. The distribution module is used to distribute a first terminal token to the first terminal and a second terminal token to the second terminal in response to successful user identity verification. The first terminal token includes first scenario authorization information, and the second terminal token includes second scenario authorization information. The first terminal token and the second terminal token are used for authentication during data migration between the first terminal and the second terminal.
23. A second terminal, characterized in that, include: The second acquisition module is used to acquire the second scenario authorization information of the second terminal token held by the second terminal. The second determining module is used to determine whether the scenario authorized by the second terminal token matches the target scenario based on the second scenario authorization information of the second terminal token. The second receiving module is used to receive migration data packets in response to the scenario authorized by the second terminal token matching the target scenario; The processing module is used to perform security processing on the migration data packet to obtain migration data; The recovery module is used to restore the application's running state based on the migration data.
24. A non-transitory computer-readable storage medium, characterized in that, When the instructions in the storage medium are executed by the processor of the terminal, the terminal is able to perform a data migration method according to any one of claims 1 to 12, 13 to 15, or 16 to 20.
25. A computer program product, said computer program product comprising a computer program or computer instructions, characterized in that, The computer program or the computer instructions are loaded and executed by a processor to enable the computer to implement the data migration method as described in any one of claims 1 to 12, 13 to 15, or 16 to 20.
