A data migration method, device, apparatus and storage medium

Abstract

The application provides a data migration method, device, equipment and storage medium. The method comprises the following steps: receiving user information of a user to be migrated sent by a second operator system; determining product subscription information of the user to be migrated according to the user information of the user to be migrated; sending a data query request to the second operator system according to the product subscription information of the user to be migrated, so that the second operator system sends customer information and account information of the user to be migrated to a first operator system according to the data query request; receiving the customer information and the account information of the user to be migrated; generating instance information of the user to be migrated according to the user information, the customer information and the account information of the user to be migrated; and distributing the instance information of the user to be migrated to an accounting system and a charging system. The method of the application improves operation efficiency and system uniformity, eliminates data redundancy, and solves the problem of inconsistent information between multiple systems.

Description

Technical Field

[0001] This application relates to the field of data migration technology, and in particular to a data migration method, apparatus, device and storage medium. Background Technology

[0002] Data migration, also known as data synchronization, refers to the process of selecting, preparing, retrieving, and transforming data, and transferring the data from one computer storage system to another.

[0003] Existing technologies, when migrating data between systems, determine the data to be migrated and the migration destination by sending multiple requests, determine the migration destination information and migration source information, change the path information after legality judgment, extract and store the migration data, and thus realize data migration.

[0004] However, existing technologies are not effective when applied to operator systems, and the operating costs are high. Summary of the Invention

[0005] This application provides a data migration method, apparatus, device, and storage medium to solve the problems of poor performance and high operating costs of existing technologies when applied to operator systems.

[0006] Firstly, this application provides a data migration method, including:

[0007] Receive user information of users to be migrated from the second operator system;

[0008] Based on the user information of the users to be migrated, determine the product order information of the users to be migrated;

[0009] Based on the product order information of the user to be migrated, a data query request is sent to the second operator system, so that the second operator system can send the customer information and account information of the user to be migrated to the first operator system in accordance with the data query request.

[0010] Receive customer and account information of users to be migrated;

[0011] Generate instance information for the users to be migrated based on their user data, customer data, and account data.

[0012] Distribute the instance information of users to be migrated to the accounting and billing systems.

[0013] In this application, the first operator system and the second operator system have a hierarchical relationship, with the first operator system being the superior operator system of the second operator system.

[0014] In this application, before receiving the user information of the user to be migrated sent by the second operator system, the method further includes:

[0015] Identify the initial users, who are the users from the second operator who will be migrated.

[0016] Based on the initial user, a legitimacy verification request is sent to the second operator system so that the second operator system can determine the legitimacy information of the initial user according to the legitimacy verification request;

[0017] Receive the legitimacy information of the initial user;

[0018] If the initial user's legitimacy information indicates that the initial user is legitimate, then the initial user is determined to be a user to be migrated, and a user information query request for the migrated user is sent to the second operator system.

[0019] In this application, after receiving the legitimacy information of the initial user, the method further includes:

[0020] If the initial user's legitimacy information indicates that the initial user is illegitimate, then the initial user will be stored in the first target table;

[0021] The first target table is sent to the second operator system so that the second operator system can change the migration status of the initial user to the pending migration status based on the first target table.

[0022] In this application, based on the user information, customer information, and account information of the user to be migrated, instance information of the user to be migrated is generated, including:

[0023] Based on the user information, customer information, and account information of the user to be migrated, generate initial instance information, wherein the status of the initial instance information is activated.

[0024] Obtain the settlement information of the users to be migrated sent by the second operator system;

[0025] The target instance information is determined based on the initial instance information and settlement information.

[0026] In this application, after generating instance information of the user to be migrated based on the user information, customer information, and account information of the user to be migrated, the method further includes:

[0027] Store the user IDs of the users to be migrated into the second target table;

[0028] The second target table containing the user ID is sent to the second operator system so that the second operator system changes the migration status of the user to be migrated from in progress to completed.

[0029] In this application, the method also includes:

[0030] Obtain user information of users to be removed from the second operator system. The users to be removed are those who have been migrated to the first operator system through the second operator system and are in the target status. The target status includes abnormal user account status and user change plan status.

[0031] Based on the user information of the users to be removed from the second operator's system, delete the routing data of the users to be removed from the system.

[0032] Secondly, this application provides a data migration apparatus, applied to a first operator system, comprising:

[0033] The receiving module is used to receive user information of users to be migrated sent by the second operator system;

[0034] The determination module is used to determine the product ordering information of the users to be migrated based on their user data.

[0035] The query module is used to send a data query request to the second operator system based on the product order information of the user to be migrated, so that the second operator system can send the customer information and account information of the user to be migrated to the first operator system according to the data query request.

[0036] The receiving module is used to receive customer information and account information of users to be migrated;

[0037] The execution module is used to generate instance information for the users to be migrated based on their user data, customer data, and account data.

[0038] The synchronization module is used to distribute the instance information of users to be migrated to the accounting and billing systems.

[0039] Thirdly, this application provides an electronic device, including: a processor and a memory communicatively connected to the processor;

[0040] The memory stores instructions that the computer executes;

[0041] The processor executes computer execution instructions stored in memory to implement the method of this application.

[0042] Fourthly, this application provides a computer-readable storage medium, comprising: computer-executable instructions stored in the computer-readable storage medium, which, when executed by a processor, are used to implement the method of this application.

[0043] This application provides a data migration method, apparatus, device, and storage medium that receives user information of the user to be migrated from a second operator system; determines the product order information of the user to be migrated based on the user information; sends a data query request to the second operator system based on the product order information of the user to be migrated, so that the second operator system sends the customer information and account information of the user to be migrated to a first operator system according to the data query request; receives the customer information and account information of the user to be migrated; generates instance information of the user to be migrated based on the user information, customer information, and account information of the user to be migrated; and distributes the instance information of the user to be migrated to the billing system and the accounting system by sending a query request to the second operator system to query the user information, customer information, and account information, generating instance information, and synchronizing the instance information to the billing system and the accounting system, thereby completing the user data migration, realizing data sharing and interaction, improving operational efficiency, and solving the problem of information inconsistency between different systems. Attached Figure Description

[0044] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0045] Figure 1 A schematic diagram illustrating a data migration method provided in an embodiment of this application;

[0046] Figure 2 A flowchart illustrating a data migration method provided in an embodiment of this application;

[0047] Figure 3 A flowchart illustrating another data migration method provided in an embodiment of this application;

[0048] Figure 4 This is a schematic diagram of the structure of a data migration device provided in an embodiment of this application;

[0049] Figure 5 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application.

[0050] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0051] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0052] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use and processing of the relevant data must comply with relevant laws, regulations and standards, and corresponding operation entry points are provided for users to choose to authorize or refuse.

[0053] Telecom operator operating systems typically consist of multiple independent subsystems, including business support systems, billing systems, and user management systems. These systems may suffer from data redundancy, inconsistencies, and complex interfaces, posing challenges to maintenance and operation for operators. Current technologies for data migration between systems involve sending multiple requests to determine the data to be migrated, its destination, and the source and destination information. After a validity check, the path information is changed, the migration data is extracted and stored, and the data migration is completed. However, because current technologies cannot generate instance information for each user, they cannot be applied to telecom operator operating systems. Furthermore, the multiple requests involved in current technologies result in cumbersome interfaces and tedious operational processes.

[0054] To address the issues of existing technologies being unapplicable to operator systems, having cumbersome interfaces and complex operating procedures, and the data redundancy and inconsistencies among operator systems, this application queries user information, customer information, and account information by calling the interfaces of operator subsystems, generates instance information, synchronizes the instance information to the accounting and billing systems, completes user data migration, achieves data sharing and interaction, improves operational efficiency, and eliminates data redundancy by rejecting users who meet the bill of lading rules, thus resolving the information inconsistency problem between multiple systems.

[0055] This application provides a data migration method aimed at solving the aforementioned technical problems of the prior art.

[0056] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0057] Figure 1 This is a schematic diagram illustrating a data migration method provided in an embodiment of this application. Figure 1 As shown, the execution entity of this method can be a data migration system, which includes: a verification unit, a query unit, and an execution unit.

[0058] The verification unit refers to a unit that checks the correctness of data transmission, storage, and processing. It can be used to detect errors or anomalies that may occur during data transmission, storage, and processing. A verification unit typically includes a checksum, a verification algorithm, and check bits. In this application, the verification unit is mainly used to receive a list of users to be migrated sent by the second operator, perform legality verification on the users to be migrated based on the list, and select users who pass the verification for migration.

[0059] The query unit refers to a unit used for database queries, which includes a query language and a query engine. The query unit is used to perform operations such as retrieving, filtering, and sorting data in the database to obtain the required data. The query unit typically provides query statements or query interfaces, through which users can submit query requests to the database. The query engine will then retrieve and process the data according to the request and return the results to the user. In this application, the first operator system sends query requests to the second operator system through the user query interface and the product ordering information query interface. The second operator system then returns the search results to the first operator system.

[0060] The execution unit refers to the unit responsible for executing the operation requests submitted by the query unit. An execution unit typically consists of a set of storage modules and an execution engine, used to efficiently process operation requests. The main responsibility of the execution unit is to receive and parse the operation requests, and then generate an execution plan based on the parsing results. The execution plan is a logical sequence of operations used to guide the execution engine on how to execute the requests. In this application, the execution unit generates preliminary instance information based on the query unit's results. After the settlement is completed in the sub-business system and the settlement file is uploaded to the main business system, target instance information is generated and synchronized to the accounting and billing systems. Furthermore, the execution unit can also receive users whose orders have been cancelled from the second operator system, tag these users, and delete their routing data.

[0061] The verification unit receives a list of users to be migrated from the second operator. Based on the list, it verifies the legitimacy of the users to be migrated, and determines that users who pass the verification are indeed to be migrated. The query unit sends query requests to the second operator's system through the user query interface and the product order information query interface. The second operator's system returns the search results to the first operator's system. The execution unit generates preliminary instance information based on the query unit's results. After the settlement is completed in the sub-business system and the settlement file is uploaded to the main business system, the target instance information is generated and synchronized to the accounting system and the billing system. In addition, the execution unit can also receive users whose orders have been cancelled from the second operator's system, tag the cancelled users, and delete their routing data.

[0062] The execution entity of the data migration method provided in this application embodiment can also be a server. The server can be a computer, tablet, or other device. This embodiment does not impose any particular limitation on the implementation method of the execution entity, as long as the execution entity can receive user information of the user to be migrated sent by the second operator system; determine the product order information of the user to be migrated based on the user information; send a data query request to the second operator system based on the product order information of the user to be migrated, so that the second operator system sends the customer information and account information of the user to be migrated to the first operator system according to the data query request; receive the customer information and account information of the user to be migrated; generate instance information of the user to be migrated based on the user information, customer information, and account information of the user to be migrated; and distribute the instance information of the user to be migrated to the billing system and the accounting system.

[0063] Data migration refers to the process of moving data from one system, platform, or format to another. Data migration comprises four stages: Data integration, the first stage, primarily involves consolidating disparate data sources into a unified data warehouse; Data cleaning, the second stage, mainly involves cleaning and validating the data, removing duplicates and inaccurate data; Data transformation, the third stage, primarily involves transforming the data from the source system to the target system; and Data loading, the final stage, primarily involves loading the data into the target system.

[0064] Figure 2 This is a flowchart illustrating a data migration method provided in an embodiment of this application. The executing entity of this method can be a server or other servers; this embodiment does not impose any particular limitations. Figure 2 As shown, the method may include:

[0065] S201, Receive user information of users to be migrated sent by the second operator system.

[0066] The second operator system can refer to a comprehensive system in which operators perform operations such as service acceptance, billing, and settlement.

[0067] Among them, users to be migrated can refer to users who have decided to migrate but have not yet completed the migration process or are in the process of migration. In this application, users to be migrated need to migrate from the second operator system to the first operator system.

[0068] User data can refer to service information describing a user's use of a mobile operator's services. This user data contains service-related information, including mobile phone number, account opening date, account opening location, selected service plan, user status, user type, user level, user suspension time, user account cancellation time, and other information related to the use of mobile operator services. In this application, user data only exists when a user uses mobile operator services.

[0069] In some embodiments, before the first operator system receives user data, the second operator system needs to first establish the mapping relationship between the data in the second operator system and the data in the first operator system, and then send this mapping relationship to the first operator system. During the migration process, it is necessary to ensure that the data mapping relationship between the source system and the destination system is correct to ensure data integrity and accuracy.

[0070] In this process, the second operator system identifies the initial users that need to be migrated and enters them into an intermediate table. The users in the table are tagged as being in the process of migration. The first operator system obtains the list of initial users by scanning the intermediate table of the second operator system, verifies the legality of the initial users, and thus determines the users to be migrated. The first operator system then queries the user information of the users to be migrated by calling the user query interface of the second operator system.

[0071] In this embodiment of the application, the first operator system and the second operator system have a hierarchical relationship, with the first operator system being the superior operator system of the second operator system.

[0072] In this context, the hierarchical relationship can refer to the relationship between different levels of systems, where the superior system is responsible for managing and guiding the work of its subordinates, while the subordinate system is responsible for executing the instructions and decisions of the superior system.

[0073] In some embodiments, the source system is the parent system and the destination system is the child system. For example, when data is migrated from a municipal operator system to a provincial operator system, the provincial operator's business system is the first operator system and the municipal sub-business system is the second operator system.

[0074] In this embodiment of the application, before receiving the user information of the user to be migrated sent by the second operator system, the method further includes:

[0075] Identify the initial users, who are the users from the second operator who will be migrated.

[0076] Based on the initial user, a legitimacy verification request is sent to the second operator system so that the second operator system can determine the legitimacy information of the initial user according to the legitimacy verification request;

[0077] Receive the legitimacy information of the initial user;

[0078] If the initial user's legitimacy information indicates that the initial user is legitimate, then the initial user is determined to be a user to be migrated, and a user information query request for the migrated user is sent to the second operator system.

[0079] The first operator's system obtains the validity verification result of the user to be migrated by calling the validity verification interface of the second operator's system. If the verification result is valid, the first operator's system calls the user query interface of the second operator's system to obtain the user information of the user to be migrated.

[0080] In this embodiment of the application, after receiving the legitimacy information of the initial user, the method further includes:

[0081] If the initial user's legitimacy information indicates that the initial user is illegitimate, then the initial user will be stored in the first target table;

[0082] The first target table is sent to the second operator system so that the second operator system can change the migration status of the initial user to the pending migration status based on the first target table.

[0083] The first target table can refer to a historical table, which is a table used to store historical data, typically recording the state changes of an entity. Each historical table usually has a timestamp column to identify the time of the record and an identifier column to identify the entity corresponding to the record. Through the historical table, it is easy to query the state and changes of an entity at different points in time.

[0084] If the verification result indicates that the user is illegitimate, the initial user is stored in the first target table. The first operator system sends the first target table to the second operator system, and the second operator system cancels the order based on the first target table.

[0085] Specifically, when a user's account status is abnormal, user data is abnormal, or lost, the user's verification result indicates that the user is illegitimate.

[0086] In this context, "removal" refers to the process of removing non-compliant or invalid data from the migration list during the migration process. This is typically due to issues such as missing, duplicate, incorrect, or invalid data. Removal ensures the accuracy and completeness of the migrated data, preventing errors and problems caused by invalid data.

[0087] S202. Based on the user information of the user to be migrated, determine the product order information of the user to be migrated.

[0088] Product ordering information can refer to information related to the user's purchase of a package, such as package type, price, order date, and validity period.

[0089] S203. Based on the product order information of the user to be migrated, send a data query request to the second operator system, so that the second operator system can send the customer information and account information of the user to be migrated to the first operator system according to the data query request.

[0090] Customer data describes a customer's natural attributes. A customer can be associated with a user one-to-one or with many users. Even if someone doesn't use the carrier's services, they may still have customers, as customers exist naturally. Customer data includes information such as customer name, address, postal code, gender, age, occupation, and identification number—information that naturally exists.

[0091] Account information can refer to the account information opened by the customer in the operator's system, including account number, account type, account opening date, account balance, etc.

[0092] Among them, user information, customer information, and account information satisfy China Unicom's three-user model relationship. The relationship between these three can be imagined as a tree, with the customer at the root, the account in the middle, and the user as the third-level leaf node. A customer has multiple accounts, and an account can have multiple users. The user is the finest unit.

[0093] After the first operator system determines the product order information in the user's data, it queries the user's three account information in the second operator system through the product order information query interface, and then sends the relevant data to the first operator system.

[0094] S204. Receive customer information and account information of users to be migrated.

[0095] S205. Generate instance information for the user to be migrated based on the user information, customer information, and account information of the user to be migrated.

[0096] The process involves the first operator system organizing data and generating initial instance information based on the user, customer, and account information of the users to be migrated. The second operator system then uploads information such as the post-settlement balance, outstanding fees, and six-month data packages of the migrated users to the first operator system in file format. After processing, the first operator system activates the credit control mechanism. The second operator system then uploads the post-settlement user's points information and user rating information. The first operator system then generates target instance information for the users to be migrated, stores successfully migrated users in the second target table, and changes the migration status of successfully migrated users to "completed."

[0097] Among these, the information control mechanism can be used to ensure the reliability and stability of the system. The information control mechanism typically includes information collection, information transmission, information processing, and information feedback. These links cooperate with each other to control and regulate the system, thereby ensuring its efficient, stable, and secure operation.

[0098] In this embodiment of the application, the generation of instance information for the user to be migrated, based on the user information, customer information, and account information of the user to be migrated, includes:

[0099] Based on the user information, customer information, and account information of the user to be migrated, generate initial instance information, wherein the status of the initial instance information is activated.

[0100] Obtain the settlement information of the users to be migrated sent by the second operator system;

[0101] The target instance information is determined based on the initial instance information and settlement information.

[0102] The process involves the first operator system organizing user data, customer data, and account data of the users to be migrated, generating initial instance information. When the second operator system stops billing the users to be migrated and invalidates their data, the first operator system activates the user instance of the users to be migrated. The second operator system uploads information such as the user's post-settlement balance, outstanding fees, and six-month data package to the first operator system in file format. After the first operator system completes its processing, it activates the credit control mechanism. The second operator system then uploads the post-settlement user's points information, user rating information, etc., and the first operator system generates the target instance information of the users to be migrated.

[0103] In this embodiment of the application, after generating instance information of the user to be migrated based on the user information, customer information, and account information of the user to be migrated, the method further includes:

[0104] Store the user IDs of the users to be migrated into the second target table;

[0105] The second target table containing the user ID is sent to the second operator system so that the second operator system changes the migration status of the user to be migrated from in progress to completed.

[0106] S206. Distribute the instance information of users to be migrated to the accounting system and billing system.

[0107] An accounting system can refer to a system based on accounting principles, primarily responsible for recording and tracking a company's transaction activities, including revenue, expenses, receivables and payables, and the integration of accounting procedures. An accounting system helps companies record and monitor all transaction activities, providing accurate financial data support to assist managers in decision-making. Furthermore, an accounting system can help companies achieve financial management and compliance with relevant laws and regulations.

[0108] A billing system can refer to a system used to manage orders, payments, accounts, invoices, and other related functions. Its main function is to ensure operational order and effectively protect customer rights. A billing system can implement order management, payment management, invoice management, and account management functions, allowing customers to enjoy more convenient and efficient services. Furthermore, billing systems can be custom-developed according to the needs of enterprises, reducing costs, improving efficiency, and employing secure and reliable payment methods to protect the security of both enterprise and customer accounts.

[0109] In this embodiment of the application, the method further includes:

[0110] Obtain user information of users to be removed from the second operator system. The users to be removed are those who have been migrated to the first operator system through the second operator system and are in the target status. The target status includes abnormal user account status and user change plan status.

[0111] Based on the user information of the users to be removed from the second operator's system, delete the routing data of the users to be removed from the system.

[0112] Users whose orders are pending removal refer to those removed from transactions or settlements by the system or administrators for various reasons during the transaction or settlement process. These reasons may include issues with the user's account, abnormal or irregular transactions, system malfunctions, or administrator errors. Transactions or settlements of users whose orders are pending removal will be canceled or reprocessed to ensure the accuracy and security of the transactions or settlements.

[0113] The second operator system determines the users to be removed from the order list according to the pre-set removal rules, initializes the migration status of the users to be removed from the order list, and sends the users to be removed from the order list to the first operator system and the billing system. The first operator system changes the status of the user information of the users to be removed from the order list to "removed" and deletes the routing data of the users to be removed from the order list. The billing system changes the status of the user information of the users to be removed from the order list to "removed".

[0114] The data migration method provided in this application has a minimal impact on user experience and requires relatively less work on the second operator system, simplifying the operation process and reducing the operating costs of the second operator system.

[0115] Figure 3 This is a flowchart illustrating another data migration method provided in an embodiment of this application. Figure 3 As shown, the method includes:

[0116] S301. Determine the initial user list.

[0117] S302. Perform a legality check on the users in the initial user list, and determine the legal users to be migrated based on the check results.

[0118] The verification results indicate that illegitimate users are stored in the history table and sent to the second operator system. The second operator system initializes the migration status of illegitimate users to the pending migration status based on the history table.

[0119] S303. Query the user information, customer information, and account information of the user to be migrated in the second operator system.

[0120] S304. Generate instance information for the user to be migrated based on the user information, customer information, and account information of the user to be migrated.

[0121] When the second operator's system stops billing the migrated user and invalidates their data, the first operator's system reactivates the user's data. The second operator's system uploads the migrated user's post-cancellation balance, outstanding fees, and six-month data package information in file format, and the first operator's system processes this data. After the balance and outstanding fees are processed, the first operator's system's credit control mechanism is activated.

[0122] After the bill is issued, the second operator's system uploads the user's points information, user rating information, etc., and the first operator's system processes the data into the database to complete the migration.

[0123] S305. Store the user ID of the user to be migrated into the target table.

[0124] S306. Synchronize the instance information of the users to be migrated to the accounting system and billing system.

[0125] After the instance information is synchronized, the second operator system, i.e. the sub-business system, determines the users who need to be removed from the order list according to the preset removal rules. The first operator system, i.e. the main business system, marks the user information of the users to be removed from the order list as removed from the order list and deletes the routing data of the users to be removed from the order list.

[0126] Figure 4 This is a schematic diagram of the structure of a data migration device provided in an embodiment of this application, as shown below. Figure 4 As shown, the data migration device 40 includes: a receiving module 401, a determining module 402, a querying module 403, a receiving module 404, an execution module 405, and a synchronization module 406. Wherein:

[0127] The receiving module 401 is used to receive user information of the user to be migrated sent by the second operator system;

[0128] The determination module 402 is used to determine the product ordering information of the user to be migrated based on the user information of the user to be migrated.

[0129] The query module 403 is used to send a data query request to the second operator system based on the product order information of the user to be migrated, so that the second operator system can send the customer information and account information of the user to be migrated to the first operator system based on the data query request.

[0130] Receiver module 404 is used to receive customer information and account information of the user to be migrated;

[0131] Execution module 405 is used to generate instance information of the user to be migrated based on the user information, customer information and account information of the user to be migrated;

[0132] Synchronization module 406 is used to distribute the instance information of users to be migrated to the accounting system and billing system.

[0133] In this embodiment of the application, the receiving module 401 may also be specifically used for:

[0134] Identify the initial users, who are the users from the second operator who will be migrated.

[0135] Based on the initial user, a legitimacy verification request is sent to the second operator system so that the second operator system can determine the legitimacy information of the initial user according to the legitimacy verification request;

[0136] Receive the legitimacy information of the initial user;

[0137] If the initial user's legitimacy information indicates that the initial user is legitimate, then the initial user is determined to be a user to be migrated, and a user information query request for the migrated user is sent to the second operator system.

[0138] In this embodiment of the application, the receiving module 401 may also be specifically used for:

[0139] If the initial user's legitimacy information indicates that the initial user is illegitimate, then the initial user will be stored in the first target table;

[0140] The first target table is sent to the second operator system so that the second operator system changes the migration status of the initial user to an inactive state based on the first target table.

[0141] In this embodiment of the application, the execution module 405 may also be specifically used for:

[0142] Based on the user information, customer information, and account information of the user to be migrated, generate initial instance information, wherein the status of the initial instance information is activated.

[0143] Obtain the settlement information of the users to be migrated sent by the second operator system;

[0144] The target instance information is determined based on the initial instance information and settlement information.

[0145] In this embodiment of the application, the execution module 405 may also be specifically used for:

[0146] Store the user IDs of the users to be migrated into the second target table;

[0147] The second target table containing the user ID is sent to the second operator system so that the second operator system changes the migration status of the user to be migrated from in progress to completed.

[0148] In this embodiment of the application, the execution module 405 may also be specifically used for:

[0149] Obtain user information of users to be removed from the second operator system. The users to be removed are those who have been migrated to the first operator system through the second operator system and are in the target status. The target status includes abnormal user account status and user change plan status.

[0150] Based on the user information of the users to be removed from the second operator's system, delete the routing data of the users to be removed from the system.

[0151] Figure 5 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Figure 5 As shown, the electronic device 50 includes:

[0152] The electronic device 50 may include a processor 501 with one or more processing cores, a memory 502 with one or more computer-readable storage media, a communication component 503, and other components. The processor 501, memory 502, and communication component 503 are connected via a bus 504.

[0153] In the specific implementation process, at least one processor 501 executes computer execution instructions stored in memory 502, causing at least one processor 501 to execute the data migration method described above.

[0154] The specific implementation process of processor 501 can be found in the above method embodiments, and its implementation principle and technical effect are similar. It will not be repeated here.

[0155] In the above Figure 5 In the illustrated embodiments, it should be understood that the processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this invention can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules within the processor.

[0156] The memory may include random access memory (RAM) and may also include non-volatile memory (NVM), such as at least one disk storage device.

[0157] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, the buses shown in the accompanying drawings are not limited to a single bus or a single type of bus.

[0158] In some embodiments, a computer program product is also provided, comprising a computer program or instructions that, when executed by a processor, implement the steps in any of the above-described data migration methods.

[0159] For details on the implementation of each of the above operations, please refer to the previous examples, which will not be repeated here.

[0160] Those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be performed by instructions, or by instructions controlling related hardware. These instructions can be stored in a computer-readable storage medium and loaded and executed by a processor.

[0161] Therefore, embodiments of this application provide a computer-readable storage medium storing a plurality of instructions that can be loaded by a processor to execute steps in any of the data migration methods provided in embodiments of this application.

[0162] The storage medium may include: read-only memory (ROM), random access memory (RAM), disk or optical disk, etc.

[0163] According to one aspect of this application, a computer program product or computer program is provided, the computer program product or computer program including computer instructions stored in a computer-readable storage medium.

[0164] Since the instructions stored in the storage medium can execute the steps of any of the data migration methods provided in the embodiments of this application, the beneficial effects that any of the data migration methods provided in the embodiments of this application can achieve can be realized. For details, please refer to the previous embodiments, which will not be repeated here.

[0165] Other embodiments of this application 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 application that follow the general principles of this application 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 application are indicated by the following claims.

[0166] It should be understood that this application is not limited to the precise structure 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 application is limited only by the appended claims.

Claims

1. A data migration method, characterized in that, Applied to the first operator system, including: Receive user information of users to be migrated from the second operator system; Based on the user information of the user to be migrated, determine the product order information of the user to be migrated; Based on the product order information of the user to be migrated, a data query request is sent to the second operator system, so that the second operator system sends the customer information and account information of the user to be migrated to the first operator system according to the data query request; Receive the customer information and account information of the user to be migrated; Based on the user information, customer information, and account information of the user to be migrated, generate instance information of the user to be migrated; The instance information of the users to be migrated is distributed to the accounting system and the billing system.

2. The method according to claim 1, characterized in that, The first operator system and the second operator system have a hierarchical relationship, with the first operator system being the superior operator system of the second operator system.

3. The method according to claim 1, characterized in that, Before receiving the user information of the user to be migrated sent by the second operator system, the method further includes: Determine the initial users, who are the users from the second operator who will be migrated; Based on the initial user, a legitimacy verification request is sent to the second operator system, so that the second operator system can determine the legitimacy information of the initial user based on the legitimacy verification request; Receive the legitimacy information of the initial user; If the initial user's legitimacy information indicates that the initial user is legitimate, then the initial user is determined to be a user to be migrated, and a user information query request for the migrated user is sent to the second operator system.

4. The method according to claim 3, characterized in that, After receiving the legitimacy information of the initial user, the method further includes: If the legitimacy information of the initial user indicates that the initial user is illegitimate, then the initial user is stored in the first target table; The first target table is sent to the second operator system so that the second operator system changes the migration status of the initial user to a pending migration status based on the first target table.

5. The method according to claim 1, characterized in that, The step of generating instance information for the user to be migrated based on the user data, customer data, and account data of the user to be migrated includes: Based on the user information, customer information, and account information of the user to be migrated, initial instance information is generated, wherein the status of the initial instance information is activated. Obtain the settlement information of the user to be migrated sent by the second operator system; The target instance information is determined based on the initial instance information and the settlement information.

6. The method according to claim 1, characterized in that, After generating instance information of the user to be migrated based on the user information, customer information, and account information of the user to be migrated, the method further includes: Store the user ID of the user to be migrated into the second target table; The second target table containing the user ID is sent to the second operator system so that the second operator system changes the migration status of the user to be migrated from in progress to completed.

7. The method according to claim 1, characterized in that, The method further includes: Obtain user information of users to be canceled sent by the second operator system, wherein the users to be canceled are users who have been migrated to the first operator system through the second operator system and are in the target state, and the target state includes user account abnormal state and user change plan state. Based on the user information of the users to be removed from the second operator system, the routing data of the users to be removed from the system is deleted.

8. A data migration device, characterized in that, Applied to the first operator system, including: The receiving module is used to receive user information of users to be migrated sent by the second operator system; The determination module is used to determine the product ordering information of the user to be migrated based on the user information of the user to be migrated; The query module is used to send a data query request to the second operator system based on the product order information of the user to be migrated, so that the second operator system can send the customer information and account information of the user to be migrated to the first operator system based on the data query request; The receiving module is used to receive the customer information and account information of the user to be migrated; The execution module is used to generate instance information of the user to be migrated based on the user information, customer information and account information of the user to be migrated; The synchronization module is used to distribute the instance information of the users to be migrated to the accounting system and the billing system.

9. An electronic device, characterized in that, include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory to implement the method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any one of claims 1 to 7.

Images