Migration Method, Device, Equipment and Storage Medium for Line App Data
By constructing Post requests and data storage requests in Google Drive storage space, the problem of Line App data being unable to be migrated across systems is solved, and data migration from iOS to Android system and recovery of chat records is realized.
Patent Information
- Application Number
- CN202111619100.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2021-12-27
- Publication Date
- 2025-07-22
- Estimated Expiration
- 2041-12-27
AI Technical Summary
Line App data cannot be moved from iOS system to Android system, causing iOS users' chat backup data to be unable to be used in Android system.
By constructing access to Google Drive storage space, generate Post requests and data storage requests, transfer Line data from iOS to Google Drive backup, and log in to Google Drive storage space in the Android system to restore chat content.
It realizes the migration of Line App data from iOS system to Android system, and users can access and recover chat records on Android devices.
Smart Images

Figure CN114356845B_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of data migration, and in particular to a method, device, equipment and storage medium for migrating Line App data. Background Art
[0002] Line app is a free instant messaging software with a large user group in Taiwan, China, Japan and Thailand.
[0003] Due to the different storage methods of backup data of iOS and Android Line chat records, the Line backup data of iOS users and Android users cannot be directly migrated. And Line does not provide a cross-terminal transmission tool between iOS and Android. Currently, the chat backup data of Line users are saved on third-party Google Drive or Apple iCloud cloud storage services.
[0004] In the official website help of Line, it is clearly introduced that chat records cannot be restored between devices of different operating systems (Android to iPhone, iPhone to Android). The methods of backing up and restoring chat records are only for iOS users to use iCloud backup restoration, and Android users to use Google Drive to back up chat records.
[0005] Therefore, iOS data cannot be used in the Android system, resulting in the problem that the data format of Line App cannot be migrated from the iOS system to the Android system. Therefore, a new technology is needed to solve the technical problem that Line App data cannot be migrated from the iOS system to the Android system. Summary of the Invention
[0006] The main purpose of the present invention is to solve the technical problem that Line App data cannot be migrated from the iOS system to the Android system.
[0007] The first aspect of the present invention provides a method for migrating Line App data, including the steps of:
[0008] Obtain a migration instruction for Line data from iOS to Android;
[0009] According to the migration instruction, send a data storage request to a preset Google Drive storage address to obtain a response permission value feedback by the Google Drive storage cloud, wherein the network address of the Google Drive storage cloud is the Google Drive storage address;
[0010] According to the preset first request generation algorithm, combine and process the file name data of the Line data, the response permission value, and the Google Drive storage address to generate a Post request;
[0011] Send the Post request to the Google Drive storage address and receive the response data transmitted by the Google Drive storage address;
[0012] According to the preset second request generation algorithm, parse and pack the file entity data of the Line data and the response data to generate a data storage request;
[0013] Send the data storage request to the Google Drive storage address so that the Android device can log in to the Google Drive storage cloud to download the Line data.
[0014] Optionally, in the first implementation manner of the first aspect of the present invention, the step of combining and processing the file name data of the Line data, the response permission value, and the Google Drive storage address according to the preset first request generation algorithm to generate a Post request includes:
[0015] Based on the response permission value and the Google Drive storage address, construct a Post request header;
[0016] Analyze the tree structure of the Line data, and according to the tree structure, read the file node names of the Line data to obtain a set of file node names;
[0017] Based on the tree structure, sort the set of file node names to obtain file name data;
[0018] Determine the file name data as the Post entity data, and splice the Post request header and the Post entity data to generate a Post request.
[0019] Optionally, in the second implementation manner of the first aspect of the present invention, the step of sorting the set of file node names based on the tree structure to obtain file name data includes:
[0020] Analyze the parent-child relationship of the tree structure;
[0021] Based on the parent-child relationship, perform data association processing on the set of file node names to obtain file name data.
[0022] Optionally, in the third implementation manner of the first aspect of the present invention, constructing the Post request header based on the response permission value and the Google Drive storage address includes:
[0023] Obtain a preset Post request framework;
[0024] Set the user service address in the Post request framework to the Google Drive storage address, and set the authorization letter in the Post request framework to the response permission value to construct the Post request header.
[0025] Optionally, in the fourth implementation manner of the first aspect of the present invention, parsing and packing the file entity data and the response data of the Line data according to a preset second request generation algorithm to generate a data storage request includes:
[0026] Read the response header of the response data to obtain the URL storage path;
[0027] Obtain a preset storage request framework, set the upload path in the storage request framework to the URL storage path, and set the authorization letter in the storage request framework to the response permission value to obtain the storage request header;
[0028] Set the file entity data of the Line data as the entity data to obtain the storage request entity data;
[0029] Perform splicing processing on the storage request header and the storage request entity data to generate a data storage request.
[0030] Optionally, in the fifth implementation manner of the first aspect of the present invention, after sending the data storage request to the Google Drive storage address, it further includes:
[0031] The Android device logs in to the Google Drive storage address;
[0032] The Line data in the Google Drive storage address is copied to the attachment folder of the Line App in the Android system through the adb component.
[0033] Optionally, in the sixth implementation manner of the first aspect of the present invention, the Line data includes:
[0034] Chat data displayed by the Line App during operation.
[0035] The second aspect of the present invention provides a migration device for Line App data, and the migration device for Line App data includes:
[0036] An acquisition module, configured to acquire a migration instruction for Line data from iOS to Android;
[0037] A first response module, configured to send a data migration request to a preset Google Drive storage address according to the migration instruction, and obtain a response approval value fed back by the Google Drive storage cloud, where the network address of the Google Drive storage cloud is the Google Drive storage address;
[0038] A combination module, configured to perform combination processing on the file name data of the Line data, the response approval value, and the Google Drive storage address according to a preset first request generation algorithm, and generate a Post request;
[0039] A second response module, configured to send the Post request to the Google Drive storage address and receive response data transmitted by the Google Drive storage address;
[0040] A parsing and packaging module, configured to perform parsing and packaging processing on the file entity data of the Line data and the response data according to a preset second request generation algorithm, and generate a data storage request;
[0041] A request sending module, configured to send the data storage request to the Google Drive storage address, so that an Android device logs in to the Google Drive storage cloud to download the Line data.
[0042] A third aspect of the present invention provides a Line App data migration device, including: a memory and at least one processor, where instructions are stored in the memory, and the memory and the at least one processor are interconnected by a line; the at least one processor calls the instructions in the memory, so that the Line App data migration device executes the above-mentioned Line App data migration method.
[0043] A fourth aspect of the present invention provides a computer-readable storage medium, where instructions are stored in the computer-readable storage medium, and when the instructions run on a computer, the computer is made to execute the above-mentioned Line App data migration method.
[0044] In an embodiment of the present invention, after creating the storage space of the Line App by constructing access to the Google Drive storage space, the chat record is written into the chat database, and the Line data on the iOS side is transmitted to the Google Drive for backup. In the Android system, the App can be logged in to access the Google Drive storage space to restore the chat content, realizing the transmission of the Line App data from the iOS system to the Android system. BRIEF DESCRIPTION OF THE DRAWINGS
[0045] Figure 1 FIG. is a schematic diagram of an embodiment of the method for migrating Line App data in an embodiment of the present invention;
[0046] Figure 2 FIG. is a schematic diagram of an embodiment of the device for migrating Line App data in an embodiment of the present invention;
[0047] Figure 3 FIG. is another schematic diagram of an embodiment of the device for migrating Line App data in an embodiment of the present invention;
[0048] Figure 4 FIG. is a schematic diagram of an embodiment of the device for migrating Line App data in an embodiment of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS
[0049] The embodiments of the present invention provide a method, device, equipment and storage medium for migrating Line App data.
[0050] The terms "first", "second", "third", "fourth", etc. (if any) in the specification, claims and drawings of the present invention are used to distinguish similar objects, and do not have to be used to describe a specific order or sequence. It should be understood that such data can be interchanged under appropriate circumstances so that the embodiments described here can be implemented in an order different from that shown or described here. In addition, the terms "comprising" or "having" and any variation thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product or equipment comprising a series of steps or units does not have to be limited to those steps or units clearly listed, but may include other steps or units not clearly listed or inherent to these processes, methods, products or equipment.
[0051] For ease of understanding, the following describes the specific process of the embodiments of the present invention. Please refer to Figure 1 , an embodiment of the method for migrating Line App data in an embodiment of the present invention, includes the steps of:
[0052] 101. Obtain a migration instruction for Line data from iOS to Android;
[0053] 102. Send a data migration request to the pre-set Google Drive storage address according to the migration instruction, and obtain a response approval value feedback from the Google Drive storage cloud. Among them, the network address of the Google Drive storage cloud is the Google Drive storage address;
[0054] In the embodiments of 101 and 102, a migration instruction to migrate the chat data displayed by the Line App running from iOS to Android is received. Send a data packet to the URL address of the Google Drive storage cloud. The URL address can be https: / / www.googleapis.com / upload / drive / v3 / files?fields=id,%20name,%20size,%20createdTime&uploadType=resumable. The Google Drive storage address returns a response approval value, also known as the Auth value.
[0055] 103. According to the pre-set first request generation algorithm, perform combined processing on the file name data, response approval value, and Google Drive storage address of the Line data to generate a Post request;
[0056] In this embodiment, construct a request header with the Auth value and the service address carried in the Google Drive storage address. Use the various file names of the chat data displayed by the Line App running as the entity data of the request data packet, and based on the request header and the entity data as the Post request.
[0057] Furthermore, 103 can perform the following steps:
[0058] 1031. Based on the response approval value and the Google Drive storage address, construct a Post request header;
[0059] 1032. Analyze the tree structure of the Line data. According to the tree structure, read the file node names of the Line data to obtain a set of file node names;
[0060] 1034. Based on the tree structure, perform sorting processing on the set of file node names to obtain the file name data;
[0061] 1035. Determine the file name data as the Post entity data, and splice the Post request header and the Post entity data to generate a Post request.
[0062] In steps 1031 - 1035, the Google Drive storage address user Agent is LINE Google-API-Java-Client Google-HTTP-Java-Client / 1.28.0 (gzip). This LINE Google-API-Java-Client Google-HTTP-Java-Client / 1.28.0 (gzip) is determined as the request header service address, and the Authorization in the request header is set to the obtained Auth value.
[0063] The Line data folder name has a tree structure like Group A - Subgroup B - Person C. First, analyze the Line folder name, and then arrange the folder names in a tree structure to obtain the file name data.
[0064] Concatenate the obtained header file and file name data into a Post request data.
[0065] Furthermore, step 1032 can perform the following steps:
[0066] 10321. Analyze the parent - child relationship of the tree structure;
[0067] 10322. Based on the parent - child relationship, perform an associated processing on the file node name set data to obtain the file name data.
[0068] In steps 10321 - 10322, construct the file name data to include name and parents. Set name to the file name to be written, here set to chat - backup.sqlite, and set parents to App Data Folder. AppData Folder represents the parent - child folding relationship or tree relationship between data names.
[0069] Furthermore, in step 1031, the following steps can be performed:
[0070] 10311. Obtain the preset Post request framework;
[0071] 10312. Set the user service address in the Post request framework to the Google Drive storage address, and set the authorization letter in the Post request framework to the response permission value to construct the Post request header.
[0072] In steps 10311 - 10312, within the Post request framework, settings data in the request header framework is set. The Google Drive storage address user Agent is set to LINE Google-API-Java-ClientGoogle-HTTP-Java-Client / 1.28.0 (gzip). This LINE Google-API-Java-Client Google-HTTP-Java-Client / 1.28.0 (gzip) is determined as the request header service address, and the Authorization in the request header is set to the obtained Auth value.
[0073] 104. Send the Post request to the Google Drive storage address and receive the response data transmitted by the Google Drive storage address;
[0074] In this embodiment, after the Post request is sent, the Google Drive storage address feeds back response data. In the data header of the response data, there is location data, and the location data is the URL path where we will upload and write.
[0075] 105. According to the preset second request generation algorithm, parse and package the file entity data and response data of the Line data to generate a data storage request;
[0076] In this embodiment, write the URL path in the response data into the request header, and write the chat data corresponding to each chat file name in the Line data into the entity data. The resulting data storage request can also be considered a Put request, and a Put request is a write request.
[0077] Further, the following steps can be executed in 105:
[0078] 1051. Read the response header of the response data to obtain the URL storage path;
[0079] 1052. Obtain the preset storage request framework, set the upload path in the storage request framework to the URL storage path, and set the authorization letter in the storage request framework to the response permission value to obtain the storage request header;
[0080] 1053. Set the file entity data of the Line data as the entity data to obtain the storage request entity data;
[0081] 1054. Concatenate and process the storage request header and the storage request entity data to generate a data storage request.
[0082] In steps 1051 - 1054, obtain the location data in the response header of the response data. The location data is determined as the URL storage path, and a Put request is sent to the URL storage path. The request header is constructed by setting the header Authorization (letter of authorization) to the previously obtained Auth value, setting x - upload - content - type to application / octet - stream, setting x - goog - api - client() to java / 0.0.0http - google - a / 1.26.0linux / 3.18.48. The Body data sent is the file entity data of the Line data we want to upload, which is also the actual data in the chat database. In this way, a data storage request is formed.
[0083] 106. Send the data storage request to the Google Drive storage address so that the Android device can log in to the Google Drive storage cloud to download the Line data.
[0084] In this embodiment, after the Put request is successfully sent, the database is written into the Google Drive storage space. After the Android device logs in to the Google Drive storage cloud, it can download and inject the chat data of Line into the folder of the Line App on the Android device.
[0085] Further, after 106, the following steps can be executed:
[0086] 107. The Android system logs in to the Google Drive storage address;
[0087] 108. The Line data in the Google Drive storage address is copied to the attachment folder of the Line App in the Android system through the adb component.
[0088] In steps 107 and 108, if a device has dual - system opening, and the iOS system has uploaded the chat data of the Line App, and then the Android system is turned on and logged in to the Google Drive storage address, the chat data of the Line App will be copied to the attachment folder of the Line App in the Android system through the adb component, that is, the migration of the chat data of the Line App from the iOS system to the Android system of a device can be achieved.
[0089] In an embodiment of the present invention, after creating the storage space of the Line App by constructing an access to the Google Drive storage space, the chat record chat database is written, and the Line data on the iOS side is transmitted to the Google Drive for backup. In the Android system, the App can be logged in to access the Google Drive storage space to restore the chat content, realizing the transmission of the Line App iOS system data to the Android system.
[0090] The method for migrating the Line App data in the embodiment of the present invention is described above. Next, the device for migrating the Line App data in the embodiment of the present invention will be described. Please refer to Figure 2 An embodiment of the device for migrating the Line App data in the embodiment of the present invention includes:
[0091] An acquisition module 201, configured to acquire a migration instruction for the Line data from iOS to Android;
[0092] A first response module 202, configured to send a data migration request to a preset Google Drive storage address according to the migration instruction, and obtain a response permission value fed back by the Google Drive storage cloud, where the network address of the Google Drive storage cloud is the Google Drive storage address;
[0093] A combination module 203, configured to perform a combination process on the file name data of the Line data, the response permission value, and the Google Drive storage address according to a preset first request generation algorithm to generate a Post request;
[0094] A second response module 204, configured to send the Post request to the Google Drive storage address and receive the response data transmitted by the Google Drive storage address;
[0095] A parsing and packaging module 205, configured to perform a parsing and packaging process on the file entity data of the Line data and the response data according to a preset second request generation algorithm to generate a data storage request;
[0096] A request sending module 206, configured to send the data storage request to the Google Drive storage address so that the Android device logs in to the Google Drive storage cloud to download the Line data.
[0097] In an embodiment of the present invention, after creating the storage space of the Line App by constructing an access to the Google Drive storage space, the chat record is written into the chat database, and the Line data on the iOS side is transmitted to the Google Drive for backup. In the Android system, the App can be logged in to access the Google Drive storage space to restore the chat content, realizing the transmission of the Line App iOS system data to the Android system.
[0098] Please refer to Figure 3 , another embodiment of the Line App data migration device in the embodiment of the present invention includes:
[0099] An acquisition module 201, configured to acquire a migration instruction for Line data from iOS to Android;
[0100] A first response module 202, configured to send a data migration request to a preset Google Drive storage address according to the migration instruction, and obtain a response permission value fed back by the Google Drive storage cloud, where the network address of the Google Drive storage cloud is the Google Drive storage address;
[0101] A combination module 203, configured to perform a combination process on the file name data of the Line data, the response permission value, and the Google Drive storage address according to a preset first request generation algorithm to generate a Post request;
[0102] A second response module 204, configured to send the Post request to the Google Drive storage address and receive the response data transmitted by the Google Drive storage address;
[0103] A parsing and packaging module 205, configured to perform a parsing and packaging process on the file entity data of the Line data and the response data according to a preset second request generation algorithm to generate a data storage request;
[0104] A request sending module 206, configured to send the data storage request to the Google Drive storage address so that an Android device logs in to the Google Drive storage cloud to download the Line data.
[0105] Wherein, the combination module 203 is specifically configured to:
[0106] Based on the response permission value and the Google Drive storage address, construct a Post request header;
[0107] Analyze the tree structure of the Line data. According to the tree structure, read the file node names of the Line data to obtain a set of file node names;
[0108] Based on the tree structure, sort the set of file node names to obtain file name data;
[0109] Determine the file name data as Post entity data, and splice the Post request header and the Post entity data to generate a Post request.
[0110] Among them, the combination module 203 is further specifically configured to:
[0111] Analyze the parent-child relationship of the tree structure;
[0112] Based on the parent-child relationship, perform data association processing on the set of file node names to obtain file name data.
[0113] Among them, the combination module 203 is further specifically configured to:
[0114] Obtain a preset Post request framework;
[0115] Set the user service address in the Post request framework to the Google Drive storage address, and set the authorization letter in the Post request framework to the response approval value to construct a Post request header.
[0116] Among them, the parsing and packaging module 205 is specifically configured to:
[0117] Read the response header of the response data to obtain the URL storage path;
[0118] Obtain a preset storage request framework, set the upload path in the storage request framework to the URL storage path, and set the authorization letter in the storage request framework to the response approval value to obtain a storage request header;
[0119] Set the file entity data of the Line data as entity data to obtain storage request entity data;
[0120] Splice the storage request header and the storage request entity data to generate a data storage request.
[0121] Among them, the migration device of the Line App data further includes a replication module 207, and the replication module 207 is specifically configured to:
[0122] Log in to the Google Drive storage address on the Android system;
[0123] The Line data in the Google Drive storage address is copied to the attachment folder of the Line App in the Android system through the adb component.
[0124] In the embodiment of the present invention, after creating the storage space of the Line App by constructing access to the Google Drive storage space, the chat record chat database is written, the Line data on the iOS side is transmitted to the Google Drive for backup, and the chat content can be restored by logging in to the App to access the Google Drive storage space in the Android system, realizing the transmission of the Line App iOS system data to the Android system.
[0125] Above Figure 2 And Figure 3 The migration device of the Line App data in the embodiment of the present invention is described in detail from the perspective of modular functional entities. Next, the migration device of the Line App data in the embodiment of the present invention is described in detail from the perspective of hardware processing.
[0126] Figure 4 FIG. is a schematic structural diagram of a migration device of Line App data provided by an embodiment of the present invention. The migration device 400 of the LineApp data may vary greatly due to configuration or performance, and may include one or more processors (central processing units, CPU) 410 (for example, one or more processors) and a memory 420, and one or more storage media 430 (for example, one or more mass storage devices) storing application programs 433 or data 432. Among them, the memory 420 and the storage media 430 may be transient storage or persistent storage. The program stored in the storage media 430 may include one or more modules (not shown in the figure), and each module may include a series of instruction operations on the migration device 400 of the Line App data. Further, the processor 410 may be configured to communicate with the storage media 430 and execute a series of instruction operations in the storage media 430 on the migration device 400 of the Line App data.
[0127] Based on the migration device 400 of the Line App data may further include one or more power supplies 440, one or more wired or wireless network interfaces 450, one or more input / output interfaces 460, and / or one or more operating systems 431, such as Windows Serve, Mac OS X, Unix, Linux, FreeBSD, etc. Those skilled in the art can understand, Figure 4The migration device structure of the Line App data shown does not limit the migration device based on Line App data, and may include more or fewer components than shown, or combine certain components, or have different component arrangements.
[0128] The present invention also provides a computer-readable storage medium. The computer-readable storage medium can be a non-volatile computer-readable storage medium, or can also be a volatile computer-readable storage medium. Instructions are stored in the computer-readable storage medium. When the instructions run on a computer, the computer is caused to execute the steps of the method for migrating Line App data.
[0129] Those skilled in the art can clearly understand that for the convenience and brevity of description, the specific working processes of the above-described system, device, or unit can refer to the corresponding processes in the foregoing method embodiments and will not be elaborated herein.
[0130] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of this technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions to cause a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of the present invention. The foregoing storage medium includes: various media such as USB flash drives, mobile hard disks, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical discs that can store program codes.
[0131] As described above, the above embodiments are only used to illustrate the technical solutions of the present invention and are not intended to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that they can still modify the technical solutions recorded in the foregoing embodiments, or perform equivalent replacements for some of the technical features; and these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of various embodiments of the present invention.
Claims
1. A method for migrating Line App data, characterized in that, Including steps: Obtain the migration instructions for Line data from iOS to Android; According to the migration instructions, send a data migration request to the preset Google Drive storage address, and obtain the response approval value feedback by the Google Drive storage cloud. Among them, the network address of the Google Drive storage cloud is the Google Drive storage address; According to the preset first request generation algorithm, perform combined processing on the file name data of the Line data, the response approval value, and the Google Drive storage address to generate a Post request; Send the Post request to the Google Drive storage address, and receive the response data transmitted by the Google Drive storage address; According to the preset second request generation algorithm, perform parsing and packaging processing on the file entity data of the Line data and the response data to generate a data storage request; Send the data storage request to the Google Drive storage address so that the Android device logs in to the Google Drive storage cloud to download the Line data.
2. The method for migrating Line App data according to claim 1, wherein The performing combined processing on the file name data of the Line data, the response approval value, and the Google Drive storage address according to the preset first request generation algorithm to generate a Post request includes: Based on the response approval value and the Google Drive storage address, construct a Post request header; Analyze the tree structure of the Line data. According to the tree structure, read the file node names of the Line data to obtain a set of file node names; Based on the tree structure, perform sorting processing on the set of file node names to obtain file name data; Determine the file name data as the Post entity data, and splice the Post request header and the Post entity data to generate a Post request.
3. The method for migrating Line App data according to claim 2, wherein The performing sorting processing on the set of file node names based on the tree structure to obtain file name data includes: Analyze the parent-child relationship of the tree structure; Based on the parent-child relationship, perform data association processing on the set of file node names to obtain file name data.
4. The method for migrating Line App data according to claim 2, wherein The constructing a Post request header based on the response approval value and the Google Drive storage address includes: Obtain the preset Post request framework; Set the user service address in the Post request framework to the Google Drive storage address, and set the authorization letter in the Post request framework to the response approval value to construct a Post request header.
5. The method for migrating Line App data according to claim 1, wherein The performing parsing and packaging processing on the file entity data of the Line data and the response data according to the preset second request generation algorithm to generate a data storage request includes: Read the response header of the response data to obtain the URL storage path; Obtain a preset storage request framework, set the upload path in the storage request framework to a URL storage path, and set the authorization letter in the storage request framework to a response approval value to obtain a storage request header; Set the file entity data of the Line data as the entity data to obtain storage request entity data; Perform splicing processing on the storage request header and the storage request entity data to generate a data storage request.
6. The method for migrating Line App data according to claim 1, wherein After sending the data storage request to the Google Drive storage address, it further includes: The Android system logs in to the Google Drive storage address; The Line data in the Google Drive storage address is copied to the attachment folder of the Line App in the Android system through the adb component.
7. The method for migrating Line App data according to claim 1, wherein The Line data includes: Chat data displayed during the operation of the Line App.
8. A migration device for Line App data, characterized in that, The migration device for Line App data includes: An acquisition module for acquiring a migration instruction for Line data from iOS to Android; A first response module for sending a data migration request to a preset Google Drive storage address according to the migration instruction to obtain a response approval value feedback by the Google Drive storage cloud, where the network address of the Google Drive storage cloud is the Google Drive storage address; A combination module for performing combination processing on the file name data of the Line data, the response approval value, and the Google Drive storage address according to a preset first request generation algorithm to generate a Post request; A second response module for sending the Post request to the Google Drive storage address and receiving response data transmitted by the Google Drive storage address; A parsing and packaging module for performing parsing and packaging processing on the file entity data of the Line data and the response data according to a preset second request generation algorithm to generate a data storage request; A request sending module for sending the data storage request to the Google Drive storage address so that the Android device logs in to the Google Drive storage cloud to download the Line data.
9. A migration device for Line App data, characterized in that The migration device for Line App data includes a memory and at least one processor, instructions are stored in the memory, and the memory and the at least one processor are interconnected by a line; The at least one processor calls the instructions in the memory so that the migration device for Line App data executes the migration method for Line App data as described in any one of claims 1-7.
10. A computer-readable storage medium, on which a computer program is stored, characterized in that, The computer program, when executed by a processor, implements the migration method for Line App data as described in any one of claims 1-7.
Citation Information
Patent Citations
Redis data migration system, migration method, device and terminal
CN111190551A
Inter-cloud migration method and device for cloud storage system
CN112347036A