WO2022111356A1 - 数据迁移方法、系统、服务器和存储介质 - Google Patents

数据迁移方法、系统、服务器和存储介质 Download PDF

Info

Publication number
WO2022111356A1
WO2022111356A1 PCT/CN2021/131162 CN2021131162W WO2022111356A1 WO 2022111356 A1 WO2022111356 A1 WO 2022111356A1 CN 2021131162 W CN2021131162 W CN 2021131162W WO 2022111356 A1 WO2022111356 A1 WO 2022111356A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
migration
data migration
home server
migrated
Prior art date
Application number
PCT/CN2021/131162
Other languages
English (en)
French (fr)
Inventor
成明
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2022111356A1 publication Critical patent/WO2022111356A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/04—Registration at HLR or HSS [Home Subscriber Server]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/20—Transfer of user or subscriber data

Definitions

  • the embodiments of the present application relate to the field of information technology, and in particular, to a data migration method, system, server, and storage medium.
  • the 2G, 3G, and 4G user data of the existing mobile communication network are stored in the Home Location Register (HLR, Home Location Register)/Home Subscriber Server (HSS, Home Subscriber Server), that is, the home server of the stock data, and its associated system includes Operator's business operation support system (BOSS, Business Operation Support System) and signaling gateway equipment: routing agent node (DRA, Diameter Routing Agent)/signaling transfer point (STP, Signalling Transfer Point), etc.
  • HLR/HSS generally It is built according to the principle of large-capacity concentration, and the scale of users ranges from one million to one hundred million.
  • 5G network user data is stored in the unified data management function (UDM, Unified Data Management), 2G, 3G, 4G and 5G user data need to be integrated, and the data is integrated into UDM/HSS, that is, the fusion data home server, and its associated system includes operation Business BOSS, signaling gateway equipment, and other network functions of the 5G core network, etc.
  • UDM Unified Data Management
  • 2G, 3G, 4G and 5G user data need to be integrated
  • the data is integrated into UDM/HSS, that is, the fusion data home server, and its associated system includes operation Business BOSS, signaling gateway equipment, and other network functions of the 5G core network, etc.
  • the cutover method is adopted, that is, the HLR/HSS user data of the existing network is cut over to the UDM of the 5G network as a whole through the data migration tool.
  • Such a method is generally cut over in units of the existing HLR/HSS as a whole, and the cutover process is now
  • the network HLR/HSS needs to stop service, which affects a wide range of users and poses a greater risk.
  • Embodiments of the present application provide a data migration method, comprising the following steps:
  • the data to be migrated is imported into the fusion data home server according to the data migration rule.
  • Embodiments of the present application also provide a data migration method, including:
  • a data migration rule wherein the data migration rule is a data office direction mapping relationship between the fusion data attribution server and the stock data attribution server;
  • the data to be migrated is sent to the converged data home server according to the routing address and the data migration rule.
  • Embodiments of the present application also provide a data migration system, including:
  • an instruction receiving module configured to analyze the business processing instruction sent by the BOSS system, and generate a data migration instruction of a designated user
  • An instruction processing module configured to obtain a routing address and a data migration rule of the data to be migrated in the existing data home server through the data migration service layer in combination with the data migration instruction, wherein the data migration rule is the fusion data the data office direction mapping relationship between the home server and the inventory data home server;
  • a data acquisition module configured to acquire the data to be migrated according to the routing address
  • a data importing module configured to import the data to be migrated into the fusion data home server according to the data migration rule.
  • Embodiments of the present application also provide a data migration system, including:
  • an instruction receiving module configured to analyze the business processing instruction sent by the BOSS system, and generate a data migration instruction of a designated user
  • An instruction processing module configured to obtain a routing address and a data migration rule of the data to be migrated in the fusion data home server by combining the data migration instruction with the data migration service layer, wherein the data migration rule is the fusion data the data office direction mapping relationship between the data home server and the existing data home server;
  • a data exporting module configured to send the data to be migrated to the converged data home server according to the routing address and the data migration rule.
  • Embodiments of the present application also provide a server, including:
  • the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to perform a data migration method.
  • Embodiments of the present application also provide a computer-readable storage medium, comprising:
  • the computer program implements the data migration method when executed by the processor.
  • FIG. 1 is a flowchart 1 of a data migration method provided by a first embodiment of the present application
  • FIG. 2 is a second flowchart of the data migration method provided by the first embodiment of the present application.
  • FIG. 3 is a schematic diagram of the server structure of the data migration method provided by the first embodiment of the present application.
  • FIG. 6 is a schematic structural diagram of a data migration system provided by a fourth embodiment of the present application.
  • FIG. 7 is a schematic structural diagram of a data migration system provided by a fifth embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of a server provided by a sixth embodiment of the present application.
  • the purpose of the embodiments of the present application is to provide a data migration method, system, server and storage medium, so that the existing data can be smoothly migrated to the 5G server without affecting normal services.
  • a data migration service layer is set in the data attribution server, which is used to obtain migration rules according to BOSS instructions, so as to cope with the complex migration logic in the process of data migration between 5G and 4G data attribution servers, such as different number segments. It may correspond to different office directions to make data migration more accurate. At the same time, it is only necessary to add a service layer for data migration to the original server, without adding hardware devices or developing new acceptance services.
  • the data migration instruction sent by the BOSS system is the user data of the designated user, which is generally a user who has signed up for 5G services. Only some users are migrated to avoid the overall cutover affecting the normal use of other user data.
  • the first embodiment of the present application relates to a data migration method.
  • the specific process is shown in Figure 1.
  • Step 101 Analyze the business processing instruction sent by the BOSS system, and generate a data migration instruction for a designated user.
  • the BOSS system accesses the converged data home server, and the converged data home server is UDM/HSS.
  • the BOSS system is a system used by operators to realize functions such as billing, settlement, business, accounting, and customer service.
  • the BOSS system can sign 5G service agreements with users to migrate the user data signed for 5G services.
  • the service processing instruction is that the operator signs a 5G service agreement with the user, and the acceptance of the service requires the migration of user data, that is, the equipment manufacturer is required to complete the migration of the existing user data to the new 5G equipment (fusion data home server when receiving such an instruction).
  • data migration is performed based on service requirements.
  • Different operators have different scenarios and migration rules for triggering data migration, and the data migration process can be started according to different trigger scenarios of operators.
  • the data migration instructions issued by the BOSS system may include data migration rules, or pre-set migration rules corresponding to the data migration instructions, and configure them individually according to different application scenarios and different needs of operators.
  • the fusion data home server After receiving the service processing instruction sent by the operator's BOSS system, the fusion data home server analyzes the service processing instruction, determines that the service processing instruction requires user data migration, and thus generates a user data migration instruction.
  • Non-data migration commands are commands other than data migration commands sent by the BOSS system. For non-migration commands, after the fusion data home server UDM/HSS receives the command, it determines whether there is data to be processed locally (ie UDM/HSS).
  • the data to be processed is processed according to the non-data migration instructions, and the processing result is returned to the BOSS system; if there is no data to be processed locally, it means that the data has not been migrated, and the non-data
  • the migration instruction is converted into the instruction of the stock data home server HLR/HSS according to the migration rules, and processed in the stock office.
  • the stock data home server returns the processing result to the fusion data home server, and the fusion data home server returns the received processing result to the BOSS system.
  • Step 201 Analyze the service processing instruction sent by the BOSS system, and determine that the service processing instruction is a non-data migration instruction.
  • Step 202 Obtain the migration rule and the routing address of the data to be processed in the home server of the existing data through the data migration layer.
  • Step 203 judging whether there is data to be processed in the fusion data home server.
  • Step 204 if there is data to be processed, process the data to be processed according to the instruction.
  • Step 205 returning the processing result to the BOSS system.
  • Step 206 if there is no data to be processed, convert the service processing instruction into an instruction of the existing data home server according to the migration rule.
  • Step 207 Synchronize the converted instruction to the inventory data home server according to the routing address.
  • Step 208 Receive the processing result returned by the inventory data home server.
  • Step 209 returning the received processing result to the BOSS system.
  • This embodiment provides a method for processing non-data migration instructions.
  • Step 102 Obtain the routing address and data migration rule of the data to be migrated in the existing data home server through the data migration service layer in combination with the data migration instruction, wherein the data migration rule is the data mapping relationship between the fusion data home server and the existing data home server .
  • the data migration layer is a new service layer and protocol stack in the data attribution server. It supports editing migration rules based on BOSS instructions to customize the automatic data migration or forwarding acceptance of instructions from different operators.
  • the server structure is shown in FIG. 3 .
  • the data migration layer is set in both the converged UDM/HSS and the stock HLR/HSS.
  • the BOSS system can access the converged UDM/HSS or access the stock HLR/HSS, as the data migration layer in the server on the BOSS access side to control data migration
  • the workflow is based on migration configuration rules; the data migration component on the non-BOSS access side is used to synchronize internal instructions and data. The two work together to complete data migration.
  • the converged UDM/HSS is the BOSS access side
  • the stock HLR/HSS is the non-BOSS access side.
  • the data migration rule is obtained by the data migration layer according to the BOSS instruction, and the data migration rule is the data mapping relationship between the fusion data attribution server and the existing data attribution server.
  • Different server clusters are divided according to regions. Each region also includes different provinces, which can be divided into different office directions.
  • the division rules and office direction rules of 5G integrated UDM/HSS are different from those of the existing network.
  • There is complex conversion logic between data so by setting migration rules to guide the data to be migrated reasonably.
  • the data migration rule can be a conversion rule of "number segment-office direction", or a gateway transfer rule of different templates, wherein the office direction is the direction pointed by the signaling, that is, the address to which the migration data pointed by the migration instruction should be migrated.
  • different migration rules can be defined according to the requirements of different operators.
  • the BOSS system when the BOSS system is connected to the existing HLR/HSS, the data of a set of existing equipment will normally only be migrated to the new 5G equipment according to one rule, and the conversion complexity can be simplified to 1:1; when the BOSS system is integrated with access When UDM/HSS,
  • Data can be converted to new 5G devices with unified rules according to the rules of different office directions, and the conversion complexity is N:1. In this way, the many-to-many migration transformation logic that needs to be considered in the data migration process is decomposed.
  • Step 103 Acquire the data to be migrated according to the routing address.
  • the route/server where the data to be migrated is found through the routing address obtained in step 102, and the data to be migrated is obtained.
  • the integrated UDM/HSS queries the existing HLR/HSS for the data to be migrated. If the existing HLR/HSS returns the data to be migrated, go to step 104; if the existing HLR/HSS does not return the data to be migrated, it means that the data has been previously After the migration is completed, the processing result is returned to the BOSS system.
  • Step 104 import the data to be migrated into the fusion data home server according to the data migration rule.
  • the fusion UDM/HSS After the data to be migrated is imported into the fusion UDM/HSS, the fusion UDM/HSS sends an instruction to delete the user data to the acceptance module of the existing HLR/HSS through the data migration service layer; the existing HLR/HSS returns the deletion result to the fusion UDM/HSS after deleting the data ; After receiving the deletion result, the fusion UDM/HSS returns the command processing result to the BOSS system.
  • acquiring the data to be migrated according to the routing address includes: sending a request for acquiring the data to be migrated to the home server of the existing data through the data migration service layer; and receiving the data to be migrated returned by the home server of the existing data. According to the return result of the acquisition request, it is judged whether the home server of the fusion data includes migration data, so as to confirm whether the data has undergone migration processing and improve the accuracy of migration.
  • the data home server receives a message returned by the stock data home server that the data to be migrated does not exist; sends the instruction processing result to the BOSS system,
  • the command processing result is that data migration has been completed.
  • confirm that the data to be migrated has been migrated and send the processing result to the BOSS system to update the data in the BOSS system, making the migration process more targeted and accurate.
  • the data attribution server sets a data migration service layer, which is used to obtain migration rules according to BOSS instructions, so as to cope with the complex migration logic in the process of data migration between data attribution servers such as 5G and 4G, such as different number segments It may correspond to different office directions to make data migration more accurate.
  • a service layer for data migration it is only necessary to add a service layer for data migration to the original server, without adding hardware devices or developing new acceptance services.
  • the data migration instruction sent by the BOSS system is the user data of the designated user, which is generally a user who has signed up for 5G services. Only some users are migrated to avoid the overall cutover affecting the normal use of other user data.
  • the second embodiment of the present application relates to a data migration method, and the interaction flow between the BOSS system, the fusion data attribution server and the stock data attribution server is shown in FIG. 3 .
  • the BOSS system accesses the converged data home server.
  • Step 401 the BOSS system sends a service processing instruction to the fusion data home server
  • Step 402 the fusion data home server analyzes the service processing instruction, and generates a data migration instruction
  • step 403 is executed according to the migration rules.
  • the specific data migration rules have been discussed in detail in step 102 and will not be repeated here.
  • Step 403 After receiving the data migration instruction, the fusion data home server sends a data query instruction to the stock data home server;
  • Step 404 after receiving the query data instruction, the inventory data home server performs the query processing of the internal data to be migrated;
  • Step 405 the existing data home server returns the data to be migrated to the fusion data home server;
  • the fusion data home server returns the processing result of the completed data migration to the BOSS system.
  • Step 406 after receiving the data to be migrated, the fusion data home server sends an instruction to delete the migrated data to the inventory home server;
  • Step 407 after receiving the instruction to delete the migration data, the inventory data home server deletes the migration data;
  • Step 408 the existing data home server returns the deletion result to the fusion home server.
  • Step 409 the fusion data home server accepts the service processing instruction locally according to the migrated user data.
  • Step 410 the fusion data home server returns the instruction processing result to the BOSS system with the acceptance result.
  • the data that has been migrated in the home server of the existing data is deleted, so that when a subsequent acquisition request is made, a request result in which the data does not exist can be returned.
  • the embodiment of the present application does not require additional hardware equipment, which saves the cost of migration; when the BOSS system accesses the converged data home server (5G new device), the user data can also be transferred from the stock home server (2G/ 3G/4G equipment) is migrated to 5G equipment, making the migration method more diverse and suitable for different application scenarios of operators; at the same time, the data that has been migrated is deleted to save space and avoid repeated migration.
  • the third embodiment of the present application relates to a data migration method.
  • the processing logic of the second embodiment is substantially the same as that of the first embodiment, and this embodiment is applied to the BOSS system accessing the inventory data home server.
  • the interaction process is shown in Figure 5:
  • Step 501 the BOSS system sends a service processing instruction to the inventory data home server
  • Step 502 the inventory data attribution server analyzes the service processing instruction, and generates a data migration instruction
  • Step 503 the inventory data attribution server queries the data to be migrated according to the data migration instruction
  • Step 504 the existing data home server sends the data to be migrated to the fusion data home server;
  • the data migration instruction sent by the BOSS system includes migration rules, that is, the corresponding relationship and conversion method between the data attribution address in the fusion data attribution server and the data attribution address in the stock data attribution server, and the specific migration rules are explained in the It is discussed in the first embodiment and will not be repeated here.
  • the data migration layer in the data home server determines the routing address (that is, the home address) and the migration rule of the data to be migrated in the inventory and fusion home server according to the data migration instruction.
  • the data of the home server sent to the routing address.
  • the fusion data processing server After synchronizing the business processing instructions to the fusion data processing server, the fusion data processing server directly accepts the business processing instructions. .
  • Step 505 After receiving the data to be migrated, the fusion data home server returns the reception result to the existing data home server.
  • Step 506 the existing data home server executes the migration data deletion locally.
  • Step 507 the existing data home server synchronizes the service processing instruction to the fusion data home server
  • Step 508 the fusion data home server accepts the service processing instruction according to the migrated user data
  • Step 509 the fusion data attribution server returns the acceptance result to the stock data attribution server
  • Step 510 the inventory data attribution server returns the acceptance result to the BOSS system.
  • the method of data migration is shown when the BOSS system is connected to the existing HLR/HSS.
  • the operator can choose to access the 5G server for migration according to the needs, or select the 4G server for migration without adding migration hardware.
  • the equipment does not even need to re-plan the network, and the production capacity of the existing equipment can be effectively utilized, which can save the cost and protect the investment for the operator to the greatest extent.
  • the fourth embodiment of the present application relates to a data migration system, as shown in FIG. 6 , including:
  • the instruction receiving module 601 is used to analyze the business processing instruction sent by the BOSS system, and generate the data migration instruction of the designated user;
  • the instruction processing module 602 is used to obtain the routing address and data migration rules of the data to be migrated in the existing data home server through the data migration service layer in combination with the data migration instructions, wherein the data migration rules are the data of the fusion data home server and the existing data home server. Office direction mapping relationship;
  • a data acquisition module 603, configured to acquire the data to be migrated according to the routing address
  • the data import module 604 is configured to import the data to be migrated into the fusion data home server according to the data migration rule.
  • this embodiment is a system example corresponding to the first embodiment, and this embodiment can be implemented in cooperation with the first embodiment.
  • the relevant technical details mentioned in the first embodiment are still valid in this embodiment, and are not repeated here in order to reduce repetition.
  • the related technical details mentioned in this embodiment can also be applied to the first embodiment.
  • the fifth embodiment of the present application relates to a data migration system, as shown in FIG. 7 , including:
  • the instruction receiving module 701 is used to analyze the business processing instruction sent by the BOSS system, and generate the data migration instruction of the designated user;
  • the instruction processing module 702 is used to obtain the routing address and data migration rules of the data to be migrated in the fusion data home server by combining the data migration instructions through the data migration service layer. Data office to mapping relationship;
  • the data export module 703 is configured to send the data to be migrated to the fusion data home server according to the routing address and the data migration rule.
  • the present embodiment can be implemented in cooperation with the second embodiment.
  • the relevant technical details mentioned in the second embodiment are still valid in this embodiment, and the technical effects that can be achieved in the second embodiment can also be achieved in this embodiment, and in order to reduce repetition, they will not be repeated here.
  • the related technical details mentioned in this embodiment can also be applied to the second embodiment.
  • modules involved in the third and fourth embodiments are all logical modules.
  • a logical unit may be a physical unit, a part of a physical unit, or a A composite implementation of multiple physical units.
  • the present embodiment does not introduce units that are not closely related to solving the technical problem raised by the present application, but this does not mean that there are no other units in the present embodiment.
  • the sixth embodiment of the present application relates to a server, as shown in FIG. 8 , including:
  • At least one processor 801 and,
  • a memory 802 in communication with at least one processor 801;
  • the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to perform any of the data migration methods
  • the memory and the processor are connected by a bus, and the bus may include any number of interconnected buses and bridges, and the bus links one or more processors and various circuits of the memory together.
  • the bus may also link together various other circuits such as peripherals, voltage regulators and power management circuits, etc., which are well known in the art and therefore will not be described further herein.
  • the bus interface provides the interface between the bus and the transceiver.
  • a transceiver may be a single element or multiple elements, such as multiple receivers and transmitters, providing a means for communicating with various other devices over a transmission medium.
  • the data processed by the processor is transmitted on the wireless medium through the antenna, and further, the antenna also receives the data and transmits the data to the processor.
  • the processor is responsible for managing the bus and general processing, and can also provide various functions, including timing, peripheral interface, voltage regulation, power management, and other control functions. Instead, memory may be used to store data used by the processor in performing operations.
  • the aforementioned storage medium includes: U disk, mobile hard disk, Read-Only Memory (ROM, Read-Only Memory), Random Access Memory (RAM, Random Access Memory), magnetic disk or optical disk and other media that can store program codes .

Landscapes

  • Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Telephonic Communication Services (AREA)

Abstract

本申请实施例涉及信息技术领域，公开了一种数据迁移方法、系统、服务器和存储介质。本申请中，对所述BOSS系统发送的业务处理指令进行分析，生成指定用户的数据迁移指令；通过所述数据迁移服务层结合所述数据迁移指令获取所述待迁移数据在存量数据归属服务器中路由地址和数据迁移规则，其中，所述数据迁移规则为所述融合数据归属服务器与所述存量数据归属服务器的数据局向映射关系；根据所述路由地址获取所述待迁移数据；根据所述数据迁移规则将所述待迁移数据导入所述融合数据归属服务器。

Description

数据迁移方法、系统、服务器和存储介质
交叉引用
本申请基于申请号为“202011379833.5”、申请日为2020年11月30日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此以引入方式并入本申请。
技术领域
本申请实施例涉及信息技术领域，特别涉及数据迁移方法、系统、服务器和存储介质。
背景技术
随着移动通讯技术和网络的不断发展，移动通讯网络已服务于全球几十亿用户，并在虚拟化、云化、软件定义网络(SDN，Software Defined Network)等技术推动下，全球移动通讯网络即将进入第五代通信技术(5G，5th-Generation)万物互联时代。
现网移动通讯网络的2G、3G、4G用户数据都存储在归属位置寄存器(HLR，Home Location Register)/归属签约用户服务器(HSS，Home Subscriber Server)中，即存量数据归属服务器，其关联系统包括运营商的业务运营支撑系统(BOSS，Business Operation Support System)和信令网关设备：路由代理节点(DRA，Diameter Routing Agent)/信令转接点(STP，Signalling Transfer Point)等，HLR/HSS一般按大容量集中原则建设，用户规模从百万级到亿级别不等。
5G网络用户数据存储到统一数据管理功能(UDM，Unified Data Management)，2G、3G、4G和5G用户数据需要进行融合，将数据融合到UDM/HSS，即融合数据归属服务器，其关联系统包括运营商BOSS、信令网关设备以及5G核心网的其他网络功能等。
为了让用户有更好的体验，提出现网存量用户只需更换5G终端即可享受 5G业务，不换卡不换号，无需对用户重新开户，因此现网存量用户数据如何向5G平滑演进是各大运营商和设备商关注的焦点。
然而，采用割接的方法，即把现网HLR/HSS用户数据，通过数据迁移工具整体割接到5G网络的UDM，这样的方法一般以存量HLR/HSS整体为单位割接，割接过程现网HLR/HSS需停止服务，影响的用户范围广，风险较大。
发明内容
本申请的实施方式提供了一种数据迁移方法，包括以下步骤：
对所述BOSS系统发送的业务处理指令进行分析，生成指定用户的数据迁移指令
通过所述数据迁移服务层结合所述数据迁移指令获取所述待迁移数据在存量数据归属服务器中路由地址和数据迁移规则，其中，所述数据迁移规则为所述融合数据归属服务器与所述存量数据归属服务器的数据局向映射关系；
根据所述路由地址获取所述待迁移数据；
根据所述数据迁移规则将所述待迁移数据导入所述融合数据归属服务器。
本申请的实施方式还提供了一种数据迁移方法，包括：
对所述BOSS系统发送的业务处理指令进行分析，生成指定用户的数据迁移指令；通过所述数据迁移服务层结合所述数据迁移指令获取所述待迁移数据预计在融合数据归属服务器中路由地址和数据迁移规则，其中，所述数据迁移规则为所述融合数据归属服务器与所述存量数据归属服务器的数据局向映射关系；
根据所述路由地址和所述数据迁移规则向所述融合数据归属服务器发送所述待迁移数据。
本申请的实施方式还提供了一种数据迁移系统，包括：
指令接收模块，用于对所述BOSS系统发送的业务处理指令进行分析，生成指定用户的数据迁移指令；
指令处理模块，用于通过所述数据迁移服务层结合所述数据迁移指令获取所述待迁移数据在存量数据归属服务器中路由地址和数据迁移规则，其中，所述数据迁移规则为所述融合数据归属服务器与所述存量数据归属服务器的数据 局向映射关系；
数据获取模块，用于根据所述路由地址获取所述待迁移数据；
数据导入模块，用于根据所述数据迁移规则将所述待迁移数据导入所述融合数据归属服务器。
本申请的实施方式还提供了一种数据迁移系统，包括：
指令接收模块，用于对所述BOSS系统发送的业务处理指令进行分析，生成指定用户的数据迁移指令；
指令处理模块，用于通过所述数据迁移服务层结合所述数据迁移指令获取所述待迁移数据预计在融合数据归属服务器中路由地址和数据迁移规则，其中，所述数据迁移规则为所述融合数据归属服务器与所述存量数据归属服务器的数据局向映射关系；
数据导出模块，用于根据所述路由地址和所述数据迁移规则向所述融合数据归属服务器发送所述待迁移数据。
本申请的实施方式还提供了一种服务器，包括：
至少一个处理器；以及，
与所述至少一个处理器通信连接的存储器；其中，
所述存储器存储有可被所述至少一个处理器执行的指令，所述指令被所述至少一个处理器执行，以使所述至少一个处理器能够执行数据迁移方法。
本申请的实施方式还提供了一种计算机可读存储介质，包括：
所述计算机程序被处理器执行时实现所述的数据迁移方法。
附图说明
一个或多个实施例通过与之对应的附图中的图片进行示例性说明，这些示例性说明并不构成对实施例的限定，附图中具有相同参考数字标号的元件表示为类似的元件，除非有特别申明，附图中的图不构成比例限制。
图1是本申请的第一实施方式提供的数据迁移方法的流程图一；
图2是本申请的第一实施方式提供的数据迁移方法的流程图二；
图3是本申请的第一实施方式提供的数据迁移方法的服务器结构示意图；
图4是本申请的第二实施方式提供的数据迁移方法的交互流程图；
图5是本申请的第三实施方式提供的数据迁移方法的交互流程图；
图6是本申请的第四实施方式提供的数据迁移系统的结构示意图；
图7是本申请的第五实施方式提供的数据迁移系统的结构示意图；
图8是本申请的第六实施方式提供的服务器的结构示意图。
具体实施方式
为使本申请实施例的目的、技术方案和优点更加清楚，下面将结合附图对本申请的各实施方式进行详细的阐述。然而，本领域的普通技术人员可以理解，在本申请各实施方式中，为了使读者更好地理解本申请而提出了许多技术细节。但是，即使没有这些技术细节和基于以下各实施方式的种种变化和修改，也可以实现本申请所要求保护的技术方案。
本申请实施方式的目的在于提供一种数据迁移方法、系统、服务器和存储介质，使存量数据在不影响正常业务的情况下，平滑迁移到5G服务器。
本申请实施方式在数据归属服务器中设置数据迁移服务层，用于根据BOSS指令获取迁移规则，以应对在5G和4G等数据归属服务器之间迁移数据过程中复杂的迁移逻辑，比如不同的号段可能对应不同的局向的情况，使数据的迁移更加的准确，同时，只需要在原有的服务器中加入用于数据迁移的服务层，不需要增加硬件设备，也不需要开发新的受理服务，减少了额外的资源开销，也使数据迁移部署上更为灵活；根据BOSS系统发送的数据迁移指令进行迁移，可以根据不同运营商的不同迁移规则进行迁移，以适用于不同运营商的个性化需求；并且BOSS系统发送的数据迁移指令为指定用户的用户数据，一般为已签约5G服务的用户，仅对部分用户进行数据迁移，避免了因整体割接而影响其他用户数据的正常使用。
以下各个实施例的划分是为了描述方便，不应对本申请的具体实现方式构成任何限定，各个实施例在不矛盾的前提下可以相互结合相互引用。
本申请的第一实施方式涉及一种数据迁移方法。具体流程如图1所示。
步骤101，对所述BOSS系统发送的业务处理指令进行分析，生成指定用户的数据迁移指令。
在本实施方式中，BOSS系统接入融合数据归属服务器，融合数据归属服 务器为UDM/HSS。BOSS系统为运营商用于实现计费、结算、营业、账务和客户服务等功能的系统，BOSS系统可与用户签订5G业务协议，以对该签约5G业务的用户数据进行迁移。
具体地，业务处理指令为运营商与用户签订5G业务协议，受理该业务需要进行用户数据的迁移，即要求设备商收到这样的指令时完成存量用户数据迁移到5G新设备(融合数据归属服务器)中，如开通5G基本数据业务指令等,基于业务需求进行数据迁移。不同运营商具有不同的触发数据迁移的场景及迁移规则，可以根据运营商各自不同的触发场景开启数据迁移流程。BOSS系统发布的数据迁移指令中可以包括数据迁移规则，也可以预先设置与数据迁移指令对应的迁移规则，根据不同的应用场景和运营商的不同的需求，个性化的进行配置。
融合数据归属服务器在接收到运营商的BOSS系统发送的业务处理指令后，对业务处理指令进行分析，确定该业务处理指令需要进行用户数据迁移，因此生成用户数据迁移指令。
需要说明的是，一般对和运营商签订5G业务协议的用户进行用户数据迁移，这样的方式无需割接大批量用户，对现网影响小，初期大部分用户还在现网存量HLR/HSS上，对新建融合UDM/HSS资源占用少，保护和节省投资。
此外，业务处理指令除需要进行数据迁移而生成数据迁移指令外，还包括无需进行数据迁移的指令。非数据迁移指令为BOSS系统发送的除数据迁移指令外的指令，对于非迁移类指令，在融合数据归属服务器UDM/HSS收到指令后，判断本地(即UDM/HSS)中是否存在待处理数据，如果本地存在待处理数据，说明数据已经迁移完成，对待处理数据按照非数据迁移指令进行处理，并将处理结果返回BOSS系统；如果本地不存在待处理数据，说明数据没有进行迁移，将非数据迁移指令根据迁移规则转化为存量数据归属服务器HLR/HSS的指令，在存量局中进行处理，存量数据归属服务器将处理结果返回融合数据归属服务器，融合数据归属服务器将接收的处理结果返回BOSS系统。具体流程如图2所示：
步骤201，对BOSS系统发送的业务处理指令进行分析，确定所述业务处理指令为非数据迁移指令。
步骤202，通过数据迁移层获取迁移规则和待处理数据在存量数据归属服务器的路由地址。
步骤203，判断融合数据归属服务器中是否存在待处理数据。
步骤204，若存在待处理数据，对待处理数据按照指令进行处理。
步骤205，将处理结果返回BOSS系统。
步骤206，若不存在待处理数据，根据迁移规则将业务处理指令转换为存量数据归属服务器的指令。
步骤207，根据路由地址将转化后的指令同步到存量数据归属服务器。
步骤208，接收存量数据归属服务器返回的处理结果。
步骤209，将接收的处理结果返回BOSS系统。
本实施方式提供非数据迁移指令进行处理的方法。
步骤102，通过数据迁移服务层结合数据迁移指令获取待迁移数据在存量数据归属服务器中路由地址和数据迁移规则，其中，数据迁移规则为所述融合数据归属服务器与存量数据归属服务器的数据映射关系。
数据迁移层为数据归属服务器中新增的服务层、协议栈，支持基于BOSS指令编辑迁移规则，以定制完成不同运营商指令的自动数据迁移或转发受理。
具体地，服务器结构如图3所示。在融合UDM/HSS和存量HLR/HSS都设置数据迁移层，BOSS系统可以接入融合UDM/HSS或接入存量HLR/HSS，作为BOSS接入侧的服务器中的数据迁移层用于控制数据迁移的工作流程，基于迁移配置规则工作；而非BOSS接入侧的数据迁移组件用于内部指令、数据的同步。两者配合完成数据迁移。在本实施方式中，融合UDM/HSS为BOSS接入侧，存量HLR/HSS为非BOSS接入侧。
数据迁移规则为数据迁移层根据BOSS指令获得的，数据迁移规则为所述融合数据归属服务器与存量数据归属服务器的数据映射关系，由于现网数据通常存放在不同的HSS中，比如运营商一般会按照大区划分不同的服务器集群，每个大区还包括不同的省份，其中可以被划分成不同的局向，而5G融合UDM/HSS的划分规则和局向规则与现网不同，两者之间具有复杂的转换逻辑，因此通过设置迁移规则来引导数据进行合理的迁移。数据迁移规则可以为“号段-局向”的转换规则，或不同模板的转关规则，其中，局向为信令所指的方向， 即迁移指令所指向的迁移数据应当迁移到的地址。在具体实现中，根据不同运营商的需求可以定义不同的迁移规则。
进一步地，当BOSS系统接入存量HLR/HSS时，一套存量设备的数据正常只会按照一种规则迁移到5G新设备中，转换复杂度可简化为1：1；当BOSS系统接入融合UDM/HSS时，
数据可以按照不同局向的规则，转换到统一规则的5G新设备中，转换复杂度为N:1。通过这样的方式，分解了数据迁移过程中需要考虑的多对多的迁移转换逻辑。
步骤103，根据路由地址获取待迁移数据。
通过步骤102获取的路由地址，找到待迁移数据所在路由/服务器，获取到待迁移数据。
具体地，融合UDM/HSS向存量HLR/HSS查询待迁移数据，若存量HLR/HSS返回了待迁移数据，则执行步骤104；若存量HLR/HSS没有返回待迁移数据，说明该数据在之前已经完成了迁移，向BOSS系统返回处理结果。
步骤104，根据数据迁移规则将待迁移数据导入融合数据归属服务器。
在待迁移数据导入融合UDM/HSS后，融合UDM/HSS通过数据迁移服务层向存量HLR/HSS受理模块发送删除用户数据的指令；存量HLR/HSS在删除数据后向融合UDM/HSS返回删除结果；融合UDM/HSS在接收删除结果后，向BOSS系统返回指令处理结果。
本实施方式中，根据所述路由地址获取所述待迁移数据，包括：通过数据迁移服务层向存量数据归属服务器发送获取待迁移数据请求；接收存量数据归属服务器返回的待迁移数据。根据获取请求的返回结果判断融合数据归属服务器中是否包括迁移数据，用以确认该数据是否已经经过迁移处理，提高迁移的准确性。
在一个实施方式中，通过数据迁移服务层向存量数据归属服务器发送获取待迁移数据请求后，数据归属服务器接收存量数据归属服务器返回的待迁移数据不存在的消息；向BOSS系统发送指令处理结果，指令处理结果为已完成数据迁移。通过指令返回的结果，确认待迁移数据已经迁移完成，并向BOSS系统发送处理结果，以更新BOSS系统中数据，使迁移过程更具有针对性和准确 性。
在本实施方式中，数据归属服务器设置数据迁移服务层，用于根据BOSS指令获取迁移规则，以应对在5G和4G等数据归属服务器之间迁移数据过程中复杂的迁移逻辑，比如不同的号段可能对应不同的局向的情况，使数据的迁移更加的准确，同时，只需要在原有的服务器中加入用于数据迁移的服务层，不需要增加硬件设备，也不需要开发新的受理服务，减少了额外的资源开销，也使数据迁移部署上更为灵活；根据BOSS系统发送的数据迁移指令进行迁移，可以根据不同运营商的不同迁移规则进行迁移，以适用于不同运营商的个性化需求；并且BOSS系统发送的数据迁移指令为指定用户的用户数据，一般为已签约5G服务的用户，仅对部分用户进行数据迁移，避免了因整体割接而影响其他用户数据的正常使用。
本申请的第二实施方式涉及一种数据迁移方法，BOSS系统、融合数据归属服务器和存量数据归属服务器交互流程如图3所示。在本实施方式中，BOSS系统接入融合数据归属服务器。
步骤401，BOSS系统向融合数据归属服务器发送业务处理指令；
步骤402，融合数据归属服务器对业务处理指令进行分析，生成数据迁移指令；
具体地，通过融合数据归属服务器获取数据迁移规则，并根据迁移规则执行步骤403，具体的数据迁移规则已在步骤102中详细论述，此处不再一一赘述。
步骤403，融合数据归属服务器接收到数据迁移指令后向存量数据归属服务器发送查询数据指令；
步骤404，存量数据归属服务器接收到查询数据指令后，进行内部待迁移数据查询处理；
步骤405，存量数据归属服务器向融合数据归属服务器返回待迁移数据；
需要说明的是，当存量归属服务器无法向融合数据归属服务器返回待迁移数据时，即存量归属服务器中不存在待迁移数据时，融合数据归属服务器向BOSS系统返回已完成数据迁移的处理结果。
步骤406，融合数据归属服务器接收到待迁移数据后，向存量归属服务器 发送删除迁移数据的指令；
步骤407，存量数据归属服务器接收到删除迁移数据的指令后，将迁移数据进行删除；
步骤408，存量数据归属服务器将删除结果返回融合归属服务器。
步骤409，融合数据归属服务器根据迁移后的用户数据，在本地受理业务处理指令。
步骤410，融合数据归属服务器将受理结果向BOSS系统返回指令处理结果。
本实施方式将存量数据归属服务器中已迁移完成的数据进行删除处理，方便后续进行获取请求时，可以返回数据不存在的请求结果。
本申请实施方式相对于相关技术而言，无需另外设置硬件设备，节约了迁移成本；在BOSS系统接入融合数据归属服务器(5G新设备)时，也可以实现用户数据从存量归属服务器(2G/3G/4G设备)迁移至5G设备，使迁移方式更加多样，适用于运营商不同的应用场景；同时将已进行迁移的数据进行删除，节约空间，且避免重复迁移。
本申请的第三实施方式涉及一种数据迁移方法。第二实施方式与第一实施方式的处理逻辑大致相同，本实施方式应用于BOSS系统接入存量数据归属服务器。交互流程如图5所示：
步骤501，BOSS系统向存量数据归属服务器发送业务处理指令；
步骤502，存量数据归属服务器对业务处理指令进行分析，生成数据迁移指令；
步骤503，存量数据归属服务器根据数据迁移指令查询待迁移数据；
步骤504，存量数据归属服务器将待迁移数据发送至融合数据归属服务器；
在本实施方式中，BOSS系统发送的数据迁移指令中包括迁移规则，即融合数据归属服务器中数据归属地址与存量数据归属服务器中数据归属地址的对应关系及转换方式，具体的迁移规则说明已在第一实施方式中论述，此处不再一一赘述。
数据归属服务器中的数据迁移层根据数据迁移指令确定待迁移数据在存量和融合归属服务器中的路由地址(即归属地址)及迁移规则，存量数据归属服 务器根据迁移规则将待迁移数据转化成适合融合归属服务器的数据，发送至路由地址。
需要说明的是，存量归属服务器中存在着无待迁数据的情况，这种情况说明该数据已经完成迁移，将业务处理指令同步到融合数据处理服务器后，直接在融合数据处理服务器受理业务处理指令。
步骤505，融合数据归属服务器接收到待迁移数据后，向存量数据归属服务器返回接收结果。
步骤506，存量数据归属服务器在本地执行迁移数据删除。
步骤507，存量数据归属服务器将业务处理指令同步到融合数据归属服务器；
步骤508，融合数据归属服务器根据迁移后的用户数据受理业务处理指令；
步骤509，融合数据归属服务器将受理结果返回存量数据归属服务器；
步骤510，存量数据归属服务器向BOSS系统返回受理结果。
需要说明的是，本实施方式的数据迁移实现方式与第一实施方式具有相同的处理逻辑，第一实施例提供的相关细节及处理方式，在本实施例中依然有效，为减少重复，在本实施方式中便不再一一赘述。
在本实施方式中，展示了在BOSS系统接入存量HLR/HSS时，进行数据迁移的方法，运营商可以根据需求选择接入5G服务器进行迁移，也可以选择4G服务器进行迁移，无需增添迁移硬件设备，甚至不需要重新规划网络，有效发挥已有设备的产能，为运营商最大限度的节省成本、保护投资。
上面各种方法的步骤划分，只是为了描述清楚，实现时可以合并为一个步骤或者对某些步骤进行拆分，分解为多个步骤，只要包括相同的逻辑关系，都在本专利的保护范围内；对算法中或者流程中添加无关紧要的修改或者引入无关紧要的设计，但不改变其算法和流程的核心设计都在该专利的保护范围内。
本申请第四实施方式涉及一种数据迁移系统，如图6所示，包括：
指令接收模块601，用于对BOSS系统发送的业务处理指令进行分析，生成指定用户的数据迁移指令；
指令处理模块602，用于通过数据迁移服务层结合数据迁移指令获取待迁移数据在存量数据归属服务器中路由地址和数据迁移规则，其中，数据迁移规 则为融合数据归属服务器与存量数据归属服务器的数据局向映射关系；
数据获取模块603，用于根据路由地址获取待迁移数据；
数据导入模块604，用于根据数据迁移规则将待迁移数据导入融合数据归属服务器。
不难发现，本实施方式为与第一实施方式相对应的系统实施例，本实施方式可与第一实施方式互相配合实施。第一实施方式中提到的相关技术细节在本实施方式中依然有效，为了减少重复，这里不再赘述。相应地，本实施方式中提到的相关技术细节也可应用在第一实施方式中。
本申请第五实施方式涉及一种数据迁移系统，如图7所示，包括：
指令接收模块701，用于对BOSS系统发送的业务处理指令进行分析，生成指定用户的数据迁移指令；
指令处理模块702，用于通过数据迁移服务层结合数据迁移指令获取待迁移数据预计在融合数据归属服务器中路由地址和数据迁移规则，其中，数据迁移规则为融合数据归属服务器与存量数据归属服务器的数据局向映射关系；
数据导出模块703，用于根据路由地址和数据迁移规则向融合数据归属服务器发送待迁移数据。
由于第二实施方式与本实施方式相互对应，因此本实施方式可与第二实施方式互相配合实施。第二实施方式中提到的相关技术细节在本实施方式中依然有效，在第二实施方式中所能达到的技术效果在本实施方式中也同样可以实现，为了减少重复，这里不再赘述。相应地，本实施方式中提到的相关技术细节也可应用在第二实施方式中。
值得一提的是，第三第四实施方式中所涉及到的各模块均为逻辑模块，在实际应用中，一个逻辑单元可以是一个物理单元，也可以是一个物理单元的一部分，还可以以多个物理单元的组合实现。此外，为了突出本申请的创新部分，本实施方式中并没有将与解决本申请所提出的技术问题关系不太密切的单元引入，但这并不表明本实施方式中不存在其它的单元。
本申请第六实施方式涉及一种服务器，如图8所示，包括：
至少一个处理器801；以及，
与至少一个处理器801通信连接的存储器802；其中，
存储器存储有可被至少一个处理器执行的指令，指令被至少一个处理器执行，以使至少一个处理器能够执行任一的数据迁移方法
其中，存储器和处理器采用总线方式连接，总线可以包括任意数量的互联的总线和桥，总线将一个或多个处理器和存储器的各种电路链接在一起。总线还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口在总线和收发机之间提供接口。收发机可以是一个元件，也可以是多个元件，比如多个接收器和发送器，提供用于在传输介质上与各种其他装置通信的单元。经处理器处理的数据通过天线在无线介质上进行传输，进一步，天线还接收数据并将数据传送给处理器。
处理器负责管理总线和通常的处理，还可以提供各种功能，包括定时，外围接口，电压调节、电源管理以及其他控制功能。而存储器可以被用于存储处理器在执行操作时所使用的数据。
本领域技术人员可以理解实现上述实施例方法中的全部或部分步骤是可以通过程序来指令相关的硬件来完成，该程序存储在一个存储介质中，包括若干指令用以使得一个设备(可以是单片机，芯片等)或处理器(processor)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
本领域的普通技术人员可以理解，上述各实施方式是实现本申请的具体实施例，而在实际应用中，可以在形式上和细节上对其作各种改变，而不偏离本申请的精神和范围。

Claims (13)

  1. 一种数据迁移方法，其特征在于，业务运营支撑BOSS系统接入融合数据归属服务器，其中，所述融合数据归属服务器包括数据迁移服务层，所述方法包括：
    对所述BOSS系统发送的业务处理指令进行分析，生成指定用户的数据迁移指令；
    通过所述数据迁移服务层结合所述数据迁移指令获取待迁移数据在存量数据归属服务器中路由地址和数据迁移规则，其中，所述数据迁移规则为所述融合数据归属服务器与所述存量数据归属服务器的数据映射关系；
    根据所述路由地址获取所述待迁移数据；
    根据所述数据迁移规则将所述待迁移数据导入所述融合数据归属服务器。
  2. 根据权利要求1所述的数据迁移方法，其特征在于，所述对所述BOSS系统发送的业务处理指令进行分析后，还包括：
    确定所述业务处理指令为非数据迁移指令；
    确定所述融合数据归属服务器中存在待处理数据，其中，所述待处理数据为所述存量数据归属服务器迁出数据；
    根据所述非数据迁移指令对所述待处理数据进行受理，并向所述BOSS系统返回受理结果。
  3. 根据权利要求2所述的数据迁移方法，其特征在于，所述确定所述业务处理指令为非数据迁移指令后，还包括：
    确定所述融合数据归属服务器中不存在所述待处理数据；
    将所述非数据迁移指令发送至所述存量数据归属服务器。
  4. 根据权利要求3所述的数据迁移方法，其特征在于，所述将所述非数据迁移指令发送至所述存量数据归属服务器，包括：通过所述数据迁移服务层向所述存量数据归属服务器同步所述非数据迁移指令。
  5. 根据权利要求1至4中任一项所述的数据迁移方法，其特征在于，所述根据所述路由地址获取所述待迁移数据，包括：
    通过所述数据迁移服务层向所述存量数据归属服务器发送获取待迁移数据请求；
    接收所述存量数据归属服务器根据所述获取待迁移数据请求而返回的所述待迁移数据。
  6. 根据权利要求5所述的数据迁移方法，其特征在于，所述通过所述数据迁移服务层向所述存量数据归属服务器发送获取待迁移数据请求后，包括：未接收到所述存量数据归属服务器根据所述获取待迁移数据请求而返回的所述待迁移数据时，向所述BOSS系统发送指令处理结果，所述指令处理结果为已完成所述数据迁移。
  7. 根据权利要求1至6中任一项所述的数据迁移方法，其特征在于，所述根据所述数据迁移规则将所述待迁移数据导入所述融合数据归属服务器后，包括：
    通过所述数据迁移服务层向所述存量数据归属服务器发送删除迁移数据的指令。
  8. 根据权利要求1至7中任一项所述的数据迁移方法，其特征在于，所述根据所述数据迁移规则将所述待迁移数据导入所述融合数据归属服务器后，包括：
    根据迁移完成的数据受理所述业务处理指令；
    将所述业务处理指令受理结果返回所述BOSS系统。
  9. 一种数据迁移方法，其特征在于，业务支撑BOSS系统接入存量数据归属服务器，其中，所述存量数据归属服务器包括数据迁移服务层，所述方法包括：
    对所述BOSS系统发送的业务处理指令进行分析，生成指定用户的数据迁移指令；通过所述数据迁移服务层结合所述数据迁移指令获取待迁移数据预计在融合数据归属服务器中路由地址和数据迁移规则，其中，所述数据迁移规则为所述融合数据归属服务器与所述存量数据归属服务器的数据映射关系；
    根据所述路由地址和所述数据迁移规则向所述融合数据归属服务器发送所述待迁移数据。
  10. 一种数据迁移系统，其特征在于，包括：
    指令接收模块，用于对BOSS系统发送的业务处理指令进行分析，生成指定用户的数据迁移指令；
    指令处理模块，用于通过数据迁移服务层结合所述数据迁移指令获取待迁移数据在存量数据归属服务器中路由地址和数据迁移规则，其中，所述数据迁移规则为融合数据归属服务器与所述存量数据归属服务器的数据局向映射关系；
    数据获取模块，用于根据所述路由地址获取所述待迁移数据；
    数据导入模块，用于根据所述数据迁移规则将所述待迁移数据导入所述融合数据归属服务器。
  11. 一种数据迁移系统，其特征在于，包括：
    指令接收模块，用于对BOSS系统发送的业务处理指令进行分析，生成指定用户的数据迁移指令；
    指令处理模块，用于通过数据迁移服务层结合数据迁移指令获取待迁移数据预计在融合数据归属服务器中路由地址和数据迁移规则，其中，所述数据迁移规则为所述融合数据归属服务器与存量数据归属服务器的数据局向映射关系；
    数据导出模块，用于根据所述路由地址和所述数据迁移规则向所述融合数据归属服务器发送所述待迁移数据。
  12. 一种服务器，其特征在于，包括：
    至少一个处理器；以及，
    与所述至少一个处理器通信连接的存储器；其中，
    所述存储器存储有可被所述至少一个处理器执行的指令，所述指令被所述至少一个处理器执行，以使所述至少一个处理器能够执行如权利要求1至8中任一所述的数据迁移方法，或权利要求9所述的数据迁移方法。
  13. 一种计算机可读存储介质，存储有计算机程序，其特征在于，所述计算机程序被处理器执行时实现权利要求1至8中任一项所述的数据迁移方法，或权利要求9所述的数据迁移方法。
PCT/CN2021/131162 2020-11-30 2021-11-17 数据迁移方法、系统、服务器和存储介质 WO2022111356A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202011379833.5A CN114584962A (zh) 2020-11-30 2020-11-30 数据迁移方法、系统、服务器和存储介质
CN202011379833.5 2020-11-30

Publications (1)

Publication Number Publication Date
WO2022111356A1 true WO2022111356A1 (zh) 2022-06-02

Family

ID=81754012

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/131162 WO2022111356A1 (zh) 2020-11-30 2021-11-17 数据迁移方法、系统、服务器和存储介质

Country Status (2)

Country Link
CN (1) CN114584962A (zh)
WO (1) WO2022111356A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115473815B (zh) * 2022-08-23 2024-01-19 浪潮通信信息系统有限公司 基于设备变更的业务迁移系统及方法

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110536279A (zh) * 2018-10-31 2019-12-03 中兴通讯股份有限公司 一种用户数据迁移的方法、装置和用户数据演进系统
US20190387065A1 (en) * 2018-06-13 2019-12-19 Verizon Patent And Licensing Inc. Systems and methods for wireless service migration
CN111246478A (zh) * 2020-01-20 2020-06-05 广州爱浦路网络技术有限公司 一种基于hss的5g核心网信息处理装置及方法
CN111314899A (zh) * 2018-12-11 2020-06-19 华为技术有限公司 消息处理方法、相关装置及系统
CN111698675A (zh) * 2019-11-13 2020-09-22 中国电信股份有限公司 数据处理方法、装置及计算机可读存储介质

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190387065A1 (en) * 2018-06-13 2019-12-19 Verizon Patent And Licensing Inc. Systems and methods for wireless service migration
CN110536279A (zh) * 2018-10-31 2019-12-03 中兴通讯股份有限公司 一种用户数据迁移的方法、装置和用户数据演进系统
CN111314899A (zh) * 2018-12-11 2020-06-19 华为技术有限公司 消息处理方法、相关装置及系统
CN111698675A (zh) * 2019-11-13 2020-09-22 中国电信股份有限公司 数据处理方法、装置及计算机可读存储介质
CN111246478A (zh) * 2020-01-20 2020-06-05 广州爱浦路网络技术有限公司 一种基于hss的5g核心网信息处理装置及方法

Also Published As

Publication number Publication date
CN114584962A (zh) 2022-06-03

Similar Documents

Publication Publication Date Title
US9251211B2 (en) Generation of a query plan for accessing a database
US8730819B2 (en) Flexible network measurement
CN104539681B (zh) 分布式gis加速系统和gis服务的处理方法
WO2017114327A1 (zh) 网络切片管理装置和网络切片管理方法
WO2021057128A1 (zh) 一种基于nf的通信方法、设备及存储介质
CN101808051B (zh) 应用整合网关及其控制方法
CN113992769B (zh) 一种工业互联网信息交换方法
WO2019174000A1 (zh) 用于业务管理的方法和装置
CN112367211B (zh) 一种设备命令行生成配置模板方法、装置及存储介质
CN109639484B (zh) 基于软件定义的工业融合网络管理方法及其网络管理器
CN101494551A (zh) 业务割接的方法、装置及系统
CN104184663A (zh) 基于软件定义网络和一体化标识网络的通信方法和装置
CN111034238A (zh) 获得关于电信网络中的订户的用户订阅数据的方法
CN102694824B (zh) 一种用户数据存储系统及其数据访问方法
WO2022111356A1 (zh) 数据迁移方法、系统、服务器和存储介质
CN116802628A (zh) 数据管理和查询方法、装置、服务网格系统、计算设备
JP2004519168A (ja) 統合化された通信サーバおよび方法
CN100369440C (zh) 一种业务中间件及利用业务中间件开展业务的方法
CN114301988A (zh) 分布式调用方法、装置、存储介质及电子设备
CN100484014C (zh) 智能网中的分布式集群业务管理系统及业务管理方法
CN110069565A (zh) 一种分布式数据库数据批量处理的方法及装置
CN116827720A (zh) 一种多源异构数据跨系统执行接口网关及方法
US12088459B2 (en) Method and apparatus for edge enabler server lifecycle management
US6411702B1 (en) Intelligent network capable of executing a plurality of service control request messages in a single service control point
WO2022052986A1 (zh) 路径搜索的方法、电子设备及存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21896857

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 24.10.23)

122 Ep: pct application non-entry in european phase

Ref document number: 21896857

Country of ref document: EP

Kind code of ref document: A1