Network slice migration method, apparatus and device
By employing an automatic lookup and path adjustment method for network slice migration, the problems of incorrect resource object ownership and long migration times in SPN networks are solved, achieving fast and accurate network slice migration.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- FIBERHOME TELECOMMUNICATION TECHNOLOGIES CO LTD
- Filing Date
- 2025-11-21
- Publication Date
- 2026-07-24
AI Technical Summary
In the existing SPN network, resource objects are often misattributed, and the migration process is prone to errors and time-consuming, making it inconvenient to create and manage network slice services.
By automatically finding the starting and extended objects that meet the preset migration rules, a set to be migrated is formed, and the path of the target tunnel is adjusted to ensure that the migration is completed to the target network slice and avoid resource conflicts.
It enables fast and accurate migration of network slices, avoiding operational errors and extra time consumption caused by manual selection, and improving migration efficiency.
Smart Images
Figure CN121509243B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of communication network technology, specifically to a network slice migration method, apparatus, and device. Background Technology
[0002] SPN (Slicing Packet Network) networks support the virtualization and resource isolation of the transport plane and physical interfaces, providing virtual device nodes (vNodes) and virtual connections (vLinks) for logical slice networks (vNets).
[0003] However, due to various reasons, some resource objects (including vLinks, tunnels, and services) in existing SPN networks that should belong to ordinary leased line network slices, high-value leased line network slices, or other slices are still relegated to the default network slice. When creating services in these slices, resource restrictions need to be manually imposed by selecting the vLink method, which is detrimental to the creation and management of slice services. Therefore, it is necessary to migrate these resource objects to their proper slices.
[0004] Current technologies require manual selection of the objects to be migrated, and some tunnels may also require path adjustments, which is prone to errors and very time-consuming. Therefore, there is an urgent need for an efficient and accurate network slice migration method. Summary of the Invention
[0005] This application provides a network slice migration method, apparatus, and device, which can solve the technical problems of network slice migration being prone to operational errors and taking a very long time in the prior art.
[0006] In a first aspect, embodiments of this application provide a network slice migration method, the network slice migration method comprising: Find the extended object corresponding to the starting object, and add the starting object and the extended object to the migration set. The starting object and the extended object both conform to the preset migration rules. Each extended object is an associated object of the starting object or other extended objects. The service layer and the client layer it carries are associated objects of each other. If a target vLink exists in the set to be migrated, the target vLink is removed from the set to be migrated, and the target tunnel is searched in the set to be migrated. The target vLink is the exclusive vLink that needs to be retained in the current network slice, and the target tunnel is the associated object of the target vLink. Adjust the path of the target tunnel so that the adjusted target tunnel only passes through the set to be migrated and the vLink in the target network slice; Migrate objects from the set to be migrated to the target network slice.
[0007] Further, in one embodiment, the step of finding the extended object corresponding to the starting object and adding the starting object and the extended object to the migration set includes: Add the starting object to the target queue and the set to be migrated; If the target queue is not empty, pop the earliest object in the target queue and record it as the first object; If a second object exists among the associated objects of the first object, then the second object is added to the target queue and the set to be migrated, wherein the second object meets the preset migration rules and is not in the set to be migrated; If the target queue is empty, then the search for extended objects is complete.
[0008] Further, in one embodiment, the step of finding the extended object corresponding to the starting object and adding the starting object and the extended object to the migration set includes: Add the starting object to the target queue; If the target queue is not empty, pop the earliest object in the target queue, record it as the first object, and add the first object to the set to be migrated; If a second object exists among the associated objects of the first object, then the second object is added to the target queue, wherein the second object meets the preset migration rules and is not in the set to be migrated; If the target queue is empty, then the search for extended objects is complete.
[0009] Further, in one embodiment, the step of adjusting the path of the target tunnel so that the adjusted target tunnel only passes through the set to be migrated and the vLink in the target network slice includes: For each target tunnel, vLinks that are not in the set to be migrated and the target network slice are used as exclusion links, and the target tunnel is re-routed to achieve path adjustment.
[0010] Furthermore, in one embodiment, the object types include vLink, MPLS-TP tunnel, SR-TP tunnel, FGU tunnel, VPN service, and CBR service; The client layer corresponding to vLink includes MPLS-TP tunnel, SR-TP tunnel and FGU tunnel; The client layer corresponding to MPLS-TP tunnels includes VPN services, and the corresponding service layer includes vLink and FGU tunnels. The SR-TP tunnel's customer layer includes VPN services, and its service layer includes vLink and FGU tunnels; The customer layer corresponding to FGU tunnels includes MPLS-TP tunnels, SR-TP tunnels, VPN services, and CBR services, while the corresponding service layer includes vLink. The service layer corresponding to VPN services includes MPLS-TP tunnels, SR-TP tunnels, and FGU tunnels; The service layer corresponding to CBR services includes the FGU tunnel.
[0011] Furthermore, in one embodiment, when an MPLS-TP tunnel or an SR-TP tunnel serves as the service layer for VPN services, it is distinguished as a primary service layer or a backup service layer. The default migration rules include: If the current object is a third object, then the current object cannot be used as the starting object or the extension object. The third object is an SR-TP tunnel, and there is a VPN service with the MPLS-TP tunnel as the primary service layer and the SR-TP tunnel as the backup service layer. The service layer of the MPLS-TP tunnel is the FGU tunnel.
[0012] Furthermore, in one embodiment, the preset migration rule further includes: If the current object is a dedicated vLink and there is a third object among the associated objects of the current object, then the current object cannot be used as the starting object.
[0013] Furthermore, in one embodiment, the preset migration rules include: If the current object is a shared vLink, then the current object cannot be used as the starting object; If the current object is a shared vLink and the current object is an extended object, then other associated objects of the current object cannot be used as new extended objects.
[0014] Secondly, embodiments of this application also provide a network slice migration apparatus, the network slice migration apparatus comprising: The object extension module is used to find the extension object corresponding to the starting object, and add the starting object and the extension object to the migration set. The starting object and the extension object both conform to the preset migration rules. Each extension object is an associated object of the starting object or other extension objects. The service layer and the client layer it carries are associated objects with each other. The object removal module is used to remove the target vLink from the migration set if the target vLink exists in the migration set, and to search for the target tunnel in the migration set. The target vLink is the exclusive vLink that needs to be retained in the current network slice, and the target tunnel is the associated object of the target vLink. The path adjustment module is used to adjust the path of the target tunnel so that the adjusted target tunnel only passes through the vLink in the set to be migrated and the target network slice; The object migration module is used to migrate objects from a set to be migrated to a target network slice.
[0015] Thirdly, this application also provides a network slice migration device, which includes a processor, a memory, and a network slice migration program stored in the memory and executable by the processor, wherein when the network slice migration program is executed by the processor, it implements the steps of the above-described network slice migration method.
[0016] In this application, after specifying the starting object to be migrated to the target network slice, based on a predefined network model and migration rules, the application automatically identifies the extended objects that need to be migrated to the target network slice, forming an initial set to be migrated. Then, it automatically identifies target vLinks that conflict with resource planning and removes them from the set to be migrated. Finally, it adjusts the paths of target tunnels carried by target vLinks in the set to be migrated, forming the final set to be migrated. Finally, the objects in the set to be migrated are migrated to the target network slice. This application enables fast and accurate automatic migration of network slices, avoiding operational errors and additional time consumption caused by manually selecting objects to be migrated. Attached Figure Description
[0017] Figure 1 A diagram illustrating the creation of multiple logical networks from a physical network; Figure 2 This is a schematic diagram illustrating a scenario requiring network slice migration. Figure 3 This is a flowchart illustrating a network slice migration method in one embodiment of this application; Figure 4 This refers to the resource objects and their relationships included in the default network slice before migration in Example 1; Figure 5 This refers to the resource objects and their relationships included in the target network slice after migration, as described in Example 1. Figure 6 This refers to the resource objects and their relationships included in the migrated default network slice in Example 1; Figure 7 This refers to the resource objects and their relationships included in the default network slice before migration in Example 2; Figure 8 This refers to the resource objects and their relationships included in the target network slice after migration, as described in Example 2. Figure 9 This refers to the resource objects and their relationships included in the migrated default network slice in Example 2; Figure 10 This is a schematic diagram of the functional modules of a network slice migration device in one embodiment of this application; Figure 11 This is a schematic diagram of the hardware structure of the network slice migration device involved in the embodiments of this application. Detailed Implementation
[0018] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of the present application.
[0019] First, the background technology involved in this application will be described in more detail so that those skilled in the art can understand this application.
[0020] Figure 1 This diagram illustrates how a physical network can be used to create multiple logical networks.
[0021] Reference Figure 1 In SPN networks, network slicing allows operators to build multiple dedicated, virtualized, and isolated vNets on top of a common physical network to meet the diverse network capability requirements of different customers. Generally, default network slices are used to carry 4G / 5G ToC personal services, ordinary leased line network slices are used to carry ordinary corporate customer services, high-value leased line network slices are used to carry high-value customer services such as financial services, and other slices are used to carry other services. When establishing a network service, the vNet to which the service belongs can be specified; if not specified, the service is created in the default network slice.
[0022] The normal procedure is as follows: First, establish a regular leased line network slice, a high-value leased line network slice, or another slice. During the establishment process, select the bandwidth resources of the physical links to be used and generate vLinks within the slice. The default network slice does not need to be explicitly created; all vLink resources not in other network slices belong to the default network slice. Second, when creating tunnels or services, specify the associated vNet. Tunnel routing will only search within the set of vLink links contained in that vNet.
[0023] Figure 2 This diagram illustrates a scenario where network slice migration is required.
[0024] Reference Figure 2vLink1, vLink2, and vLink3 should belong to the leased network slice, but they are still in the default network slice. When creating a leased service, it is necessary to manually select exclusion conditions: avoid network element B and vLink6, ensuring that the leased service only uses the link resources of vLink1, vLink2, and vLink3. Therefore, these vLinks and their carried tunnels and services need to be migrated to the corresponding leased network slices.
[0025] The technical terms used in this application are explained below.
[0026] vLink: A logical link generated by partitioning resources from a physical link. A physical link can be divided into one or more logical links.
[0027] vNode: A logical node generated by virtualizing physical network elements.
[0028] vNet: A logical network composed of vNodes and vLinks.
[0029] Shared vLink: A vLink may be contained in multiple vNets simultaneously. For example, in a hybrid network scenario of SPN and PTN (Packet Transport Network), PTN does not support hard isolation, so a link of a PTN needs to be divided into multiple vNets.
[0030] Exclusive vLink: A vLink can only be contained in one vNet.
[0031] MPLS-TP (Multiprotocol Label Switching - Transport Profile) tunneling: A packet transport network (PTN) technology standardized by the International Telecommunication Union (ITU-T). It borrows from MPLS technology, and data is forwarded based on MPLS-TP labels, making it a connection-oriented technology.
[0032] SR-TP (Segment Routing Transport Profile) tunnel: A new tunneling technology that combines SR (Source Routing Protocol) in IP networks and MPLS-TP in PTN networks in SPN networks.
[0033] FGU (Fine Granularity Unit) tunnel: SPN small-granularity technology reduces the SPN hard slice granularity from 5Gbps to 10Mbps, providing n*10Mbps hard slices to build an end-to-end efficient, lossless, flexible, and reliable channel and bearer.
[0034] VPN (Virtual Private Network) service: This involves establishing a private network over a public network for encrypted communication. A VPN gateway enables remote access by encrypting data packets and translating their destination addresses. VPNs can be categorized into Layer 2 and Layer 3 VPNs. Layer 2 VPNs can be further divided into Eline, ETree, and ELan types.
[0035] CBR (Constant Bit Rate) service: Transmits information at a fixed bit rate, used for real-time services that require fixed bandwidth, low latency, and minimal latency variation.
[0036] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.
[0037] In a first aspect, embodiments of this application provide a network slice migration method.
[0038] Figure 3 A flowchart illustrating a network slice migration method according to an embodiment of this application is shown.
[0039] Reference Figure 3 In one embodiment, the network slice migration method includes the following steps: S1. Locate the extended object corresponding to the starting object, and add the starting object and the extended object to the migration set. The starting object and the extended object both conform to the preset migration rules. Each extended object is an associated object of the starting object or other extended objects. The service layer and the client layer it carries are associated objects of each other.
[0040] Specifically, related objects have a host or being hosted relationship; if one object hosts another, the former is defined as the service layer, and the latter as the client layer. A service layer can have multiple client layers, and a client layer can have multiple service layers. The basic migration rule is that if an object needs to be migrated, its related objects also need to be migrated unless there are special circumstances. In different scenarios, other migration rules may exist; in this embodiment, these are defined as preset migration rules.
[0041] In this embodiment, a starting object is first specified and added to the set to be migrated. Then, objects that meet the preset migration rules are searched among the associated objects of the starting object and added to the set to be migrated as extended objects. For each extended object, objects that meet the preset migration rules are searched among the associated objects of the extended object and added as new extended objects to be migrated, until no new extended objects can be found, thus forming a preliminary set to be migrated.
[0042] S2. If a target vLink exists in the set to be migrated, remove the target vLink from the set to be migrated and search for the target tunnel in the set to be migrated. The target vLink is the exclusive vLink that needs to be retained in the current network slice, and the target tunnel is the associated object of the target vLink.
[0043] In this embodiment, considering that manually constraining vLink to create services may require the tunnel to be migrated to the target network slice to pass through a dedicated vLink that needs to be retained in the current network slice, resulting in resource conflicts, in step S1, when selecting the extension object, there is no requirement as to whether the vLink is a dedicated vLink that needs to be retained in the current network slice, thereby avoiding the omission of tunnels and services that need to be migrated.
[0044] In this step, the intersection of the set to be migrated and the dedicated vLinks that need to be retained in the current network slice is detected to determine if a target vLink exists. The target vLink is then removed from the set to be migrated to resolve resource conflicts. Furthermore, SPN networks stipulate that vLinks traversed by a tunnel must be within the same network slice. Therefore, it is also necessary to identify the target tunnels in the set to be migrated that pass through the target vLink. In subsequent steps, the paths of these target tunnels are adjusted to ensure that the migrated target tunnel only passes through vLinks within the target network slice.
[0045] S3. Adjust the path of the target tunnel so that the adjusted target tunnel only passes through the set to be migrated and the vLink in the target network slice.
[0046] It is understandable that after the target vLink is removed, the vLinks in the set to be migrated will be migrated to the target network slice in subsequent steps. These vLinks, along with the vLinks that originally belonged to the target network slice, can be used as new path selections for the target tunnel.
[0047] S4. Migrate the objects in the set to be migrated to the target network slice.
[0048] Specifically, resource objects record their associated network slice through the vNet ID attribute. The specific operation for migrating objects in the set to be migrated to the target network slice is as follows: For dedicated vLinks, tunnels, and services, modify the vNet ID from its current value to the vNet ID of the target network slice. For shared vLinks, add the vNet ID of the target network slice to the vNet ID list.
[0049] Therefore, in this embodiment, after specifying the starting object to be migrated to the target network slice, based on predefined resource object relationships and migration rules, the system automatically identifies the extended objects that need to be migrated to the target network slice together, forming a preliminary set to be migrated. Then, it automatically identifies target vLinks that conflict with resource planning and removes them from the set to be migrated. Finally, it adjusts the paths of target tunnels carried by target vLinks in the set to be migrated, forming the final set to be migrated. Finally, the objects in the set to be migrated are migrated to the target network slice. This embodiment enables fast and accurate automatic migration of network slices, avoiding operational errors and additional time consumption caused by manually selecting objects to be migrated.
[0050] It should be noted that the network slice migration method described in this embodiment is applicable not only to migrating resource objects from the default network slice to the target network slice, but also to migrating resource objects from other network slices to the target network slice (including the default network slice).
[0051] Further, in one embodiment, the step of finding the extended object corresponding to the starting object and adding the starting object and the extended object to the migration set includes: Add the starting object to the target queue and the set to be migrated; If the target queue is not empty, pop the earliest object in the target queue and record it as the first object; If a second object exists among the associated objects of the first object, then the second object is added to the target queue and the set to be migrated, wherein the second object meets the preset migration rules and is not in the set to be migrated; If the target queue is empty, then the search for extended objects is complete.
[0052] In this embodiment, the expansion object is found by iterating through the target queue. The target queue is used to store objects that have not undergone expansion detection (detecting whether there is a second object). The migration set is used to store historical objects in the target queue. When expansion detection is performed, the object is popped from the target queue. The starting object and the expansion object are added to the target queue and the migration set simultaneously.
[0053] Further, in one embodiment, the step of finding the extended object corresponding to the starting object and adding the starting object and the extended object to the migration set includes: Add the starting object to the target queue; If the target queue is not empty, pop the earliest object in the target queue, record it as the first object, and add the first object to the set to be migrated; If a second object exists among the associated objects of the first object, then the second object is added to the target queue, wherein the second object meets the preset migration rules and is not in the set to be migrated; If the target queue is empty, then the search for extended objects is complete.
[0054] In this embodiment, the target queue is used to iterate to find the extended object. The target queue is used to store objects that have not been extended and the set to be migrated is used to store objects that have been extended and migrated. When performing the extended and migrated detection, the object is popped from the target queue and added to the set to be migrated.
[0055] Optionally, the object can be added to the tail of the target queue or popped from the head of the target queue.
[0056] Optionally, the object is added to the head of the target queue and popped from the tail of the target queue.
[0057] Furthermore, in one embodiment, the step of adjusting the path of the target tunnel so that the adjusted target tunnel only passes through the set to be migrated and the vLink in the target network slice includes: For each target tunnel, vLinks that are not in the set to be migrated and the target network slice are used as exclusion links, and the target tunnel is re-routed to achieve path adjustment.
[0058] In this embodiment, automatic rerouting is performed by setting exclusion link conditions to ensure that the adjusted target tunnel only passes through vLinks in the set to be migrated and the target network slice, without the need for manual operation.
[0059] Common SPN network models are as follows: Object types include vLink, MPLS-TP tunnel, SR-TP tunnel, FGU tunnel, VPN service, and CBR service; The client layer corresponding to vLink includes MPLS-TP tunnel, SR-TP tunnel and FGU tunnel; The client layer corresponding to MPLS-TP tunnels includes VPN services, and the corresponding service layer includes vLink and FGU tunnels. The SR-TP tunnel's customer layer includes VPN services, and its service layer includes vLink and FGU tunnels; The customer layer corresponding to FGU tunnels includes MPLS-TP tunnels, SR-TP tunnels, VPN services, and CBR services, while the corresponding service layer includes vLink. The service layer corresponding to VPN services includes MPLS-TP tunnels, SR-TP tunnels, and FGU tunnels; The service layer corresponding to CBR services includes the FGU tunnel.
[0060] Furthermore, in one embodiment, when an MPLS-TP tunnel or an SR-TP tunnel serves as the service layer for VPN services, it is distinguished as a primary service layer or a backup service layer. The default migration rules include: If the current object is a third object, then the current object cannot be used as the starting object or the extension object. The third object is an SR-TP tunnel, the service layer of which is vLink. There is a VPN service with MPLS-TP tunnel as the primary service layer and SR-TP tunnel as the backup service layer. The service layer of MPLS-TP tunnel is FGU tunnel.
[0061] This embodiment applies to an SPN network model with small-granularity leased line services. These services are VPN services, with the MPLS-TP tunnel carried on the FGU tunnel as the primary service layer and the SR-TP tunnel carried on the vLink as the backup service layer. The backup service layer SR-TP tunnel (defined as a third object) for the small-granularity leased line service is not migrated; that is, it cannot be used as a starting object or an extension object.
[0062] Furthermore, in one embodiment, the preset migration rule further includes: If the current object is a dedicated vLink and there is a third object among the associated objects of the current object, then the current object cannot be used as the starting object.
[0063] In this embodiment, the backup service layer for the small-granularity leased line service is an SR-TP tunnel with rerouting capabilities (automatically rerouting after a path is interrupted), serving to enhance protection. Under the small-granularity leased line service model, the FGU service layer tunnel of the primary service layer's MPLS-TP tunnel is configured with protection. However, to prevent service interruption if both the working path and protection path of the FGU service layer tunnel are interrupted, protection is superimposed. The backup service layer SR-TP tunnel and its traversed vLinks are retained in the current network slice (usually the default network slice) to share the link resources of the current network slice, avoiding excessive resource consumption in the target network slice.
[0064] Furthermore, in one embodiment, the preset migration rules include: If the current object is a shared vLink, then the current object cannot be used as the starting object; If the current object is a shared vLink and the current object is an extended object, then other associated objects of the current object cannot be used as new extended objects.
[0065] This embodiment applies to a hybrid PTN and SPN networking scenario. Since PTN does not support virtualization and resource isolation of physical interfaces, it is necessary to support the same link belonging to multiple network slices simultaneously. In this scenario, a shared vLink cannot be used as a starting object, and when a shared vLink is used as an extension object, its associated other objects cannot be migrated as new extension objects.
[0066] For example, the resource object relationships of the SPN network are shown in Table 1.
[0067] The relationship types between objects include C_S, S_C, C_Main_S, and C_Backup_S. C_S represents a client-service layer relationship between the current object and its associated objects; S_C represents a service layer-client layer relationship; C_Main_S represents a client layer-primary service layer relationship; and C_Backup_S represents a client layer-backup service layer relationship.
[0068] Table 1
[0069] Figure 4 The example illustrates the resource objects and their relationships included in the default network slice before migration in Example 1.
[0070] Reference Figure 4 Before network slice migration, the resource objects in the default network slice include vLink1-vLink11, MPLS-TP tunnels 1 and 2, SR-TP tunnels 3, 4 and 5, and Eline services 1, 2, 3 and 4. Figure 4 The resource object relationships are shown in Table 2.
[0071] Table 2
[0072] The exclusive vLinks that need to be retained in the default network slice include vLink2, 3, 5, 8, 9, 10, and 11. Specify vLink1 as the starting object.
[0073] Example 1 executes step S1 in the first target queue iteration method described above to form the set to be migrated, as shown in Table 3. It should be noted that in the third iteration, since vLink10 is a shared vLink, its other associated object, MPLS-TP2, cannot be added as a new extended object to the target queue and the set to be migrated.
[0074] Table 3
[0075] Figure 5 The diagram illustrates the resource objects and their relationships included in the migrated target network slice in Example 1. Figure 6 The diagram illustrates the resource objects and their relationships included in the migrated default network slice in Example 1.
[0076] In Example 1, in step S2, it is found that the target vLink is vLink3 in the migration set. vLink3 is removed from the migration set, and the target tunnel is SR-TP4. In step S3, the path of SR-TP4 is adjusted, and the new path is vLink7-vLink6-vLink4. The situation after migration is as follows. Figure 5 and Figure 6 .
[0077] Figure 7 The example illustrates the resource objects and their relationships included in the default network slice before migration in Example 2.
[0078] Reference Figure 7 Before network slice migration, the resource objects in the default network slice include vLink1-vLink6, FGU tunnel 1, MPLS-TP tunnel 2, SR-TP tunnel 3, and Eline service 1. Figure 7 The resource object relationships are shown in Table 4.
[0079] Table 4
[0080] Dedicated vLinks that need to be retained in the default network slice include vLink5 and 6. Specify vLink1 as the starting object.
[0081] Example 2 executes step S1 in the second target queue iteration method described above to form the set to be migrated, as shown in Table 5. It should be noted that in the 6th iteration, since ELine1 is a small-granularity leased line service, SR-TP3, as its backup service layer, cannot be added to the target queue as a new extension object.
[0082] Table 5
[0083] Figure 8 The diagram illustrates the resource objects and their relationships included in the migrated target network slice in Example 2. Figure 9 The diagram illustrates the resource objects and their relationships included in the migrated default network slice in Example 2.
[0084] In Example 2, step S2 reveals that the target vLink is not present in the set to be migrated, therefore step S3 is not required. The post-migration situation is as follows. Figure 8 and Figure 9 .
[0085] Secondly, embodiments of this application also provide a network slice migration device.
[0086] Figure 10A schematic diagram of the functional modules of a network slice migration device in one embodiment of this application is shown.
[0087] Reference Figure 10 In one embodiment, the network slice migration apparatus includes: The object extension module 10 is used to find the extension object corresponding to the starting object and add the starting object and the extension object to the migration set. The starting object and the extension object both conform to the preset migration rules. Each extension object is an associated object of the starting object or other extension objects. The service layer and the client layer it carries are associated objects of each other. The object removal module 20 is used to remove the target vLink from the migration set if the target vLink exists in the migration set, and to search for the target tunnel in the migration set. The target vLink is the exclusive vLink that needs to be retained in the current network slice, and the target tunnel is the associated object of the target vLink. The path adjustment module 30 is used to adjust the path of the target tunnel so that the adjusted target tunnel only passes through the vLink in the set to be migrated and the target network slice. The object migration module 40 is used to migrate objects in the set to be migrated to the target network slice.
[0088] Furthermore, in one embodiment, the object expansion module 10 is used for: Add the starting object to the target queue and the set to be migrated; If the target queue is not empty, pop the earliest object in the target queue and record it as the first object; If a second object exists among the associated objects of the first object, then the second object is added to the target queue and the set to be migrated, wherein the second object meets the preset migration rules and is not in the set to be migrated; If the target queue is empty, then the search for extended objects is complete.
[0089] Furthermore, in one embodiment, the object expansion module 10 is used for: Add the starting object to the target queue; If the target queue is not empty, pop the earliest object in the target queue, record it as the first object, and add the first object to the set to be migrated; If a second object exists among the associated objects of the first object, then the second object is added to the target queue, wherein the second object meets the preset migration rules and is not in the set to be migrated; If the target queue is empty, then the search for extended objects is complete.
[0090] Furthermore, in one embodiment, the path adjustment module 30 is used for: For each target tunnel, vLinks that are not in the set to be migrated and the target network slice are used as exclusion links, and the target tunnel is re-routed to achieve path adjustment.
[0091] Furthermore, in one embodiment, the object types include vLink, MPLS-TP tunnel, SR-TP tunnel, FGU tunnel, VPN service, and CBR service; The client layer corresponding to vLink includes MPLS-TP tunnel, SR-TP tunnel and FGU tunnel; The client layer corresponding to MPLS-TP tunnels includes VPN services, and the corresponding service layer includes vLink and FGU tunnels. The SR-TP tunnel's customer layer includes VPN services, and its service layer includes vLink and FGU tunnels; The customer layer corresponding to FGU tunnels includes MPLS-TP tunnels, SR-TP tunnels, VPN services, and CBR services, while the corresponding service layer includes vLink. The service layer corresponding to VPN services includes MPLS-TP tunnels, SR-TP tunnels, and FGU tunnels; The service layer corresponding to CBR services includes the FGU tunnel.
[0092] Furthermore, in one embodiment, when an MPLS-TP tunnel or an SR-TP tunnel serves as the service layer for VPN services, it is distinguished as a primary service layer or a backup service layer. The default migration rules include: If the current object is a third object, then the current object cannot be used as the starting object or the extension object. The third object is an SR-TP tunnel, and there is a VPN service with the MPLS-TP tunnel as the primary service layer and the SR-TP tunnel as the backup service layer. The service layer of the MPLS-TP tunnel is the FGU tunnel.
[0093] Furthermore, in one embodiment, the preset migration rule further includes: If the current object is a dedicated vLink and there is a third object among the associated objects of the current object, then the current object cannot be used as the starting object.
[0094] Furthermore, in one embodiment, the preset migration rules include: If the current object is a shared vLink, then the current object cannot be used as the starting object; If the current object is a shared vLink and the current object is an extended object, then other associated objects of the current object cannot be used as new extended objects.
[0095] The functions of each module in the above-mentioned network slice migration device correspond to the steps in the above-mentioned network slice migration method embodiment, and their functions and implementation processes will not be described in detail here.
[0096] Thirdly, embodiments of this application provide a network slice migration device, which can be a personal computer (PC), laptop computer, server, or other device with data processing capabilities.
[0097] Figure 11 A schematic diagram of the hardware structure of the network slice migration device involved in the embodiment of this application is shown.
[0098] Reference Figure 11 In this embodiment of the application, the network slice migration device may include a processor, a memory, a communication interface, and a communication bus.
[0099] The communication bus can be of any type and is used to interconnect the processor, memory, and communication interface.
[0100] Communication interfaces include input / output (I / O) interfaces, physical interfaces, and logical interfaces used for interconnecting devices within the network slicing migration device, as well as interfaces used for interconnecting the network slicing migration device with other devices (such as other computing devices or user equipment). Physical interfaces can be Ethernet interfaces, fiber optic interfaces, ATM interfaces, etc.; user equipment can be displays, keyboards, etc.
[0101] Memory can be various types of storage media, such as random access memory (RAM), read-only memory (ROM), non-volatile RAM (NVRAM), flash memory, optical storage, hard disk, programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), etc.
[0102] The processor can be a general-purpose processor, which can call the network slice migration program stored in memory and execute the network slice migration method provided in the embodiments of this application. For example, the general-purpose processor can be a central processing unit (CPU). The method executed when the network slice migration program is called can be referred to in the various embodiments of the network slice migration method of this application, and will not be repeated here.
[0103] Those skilled in the art will understand that Figure 11 The hardware structure shown does not constitute a limitation of this application and may include more or fewer components than shown, or combine certain components, or have different component arrangements.
[0104] It should be noted that the sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.
[0105] The terms "comprising" and "having," and any variations thereof, in the specification, claims, and accompanying drawings of this application are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to such process, method, product, or apparatus. The terms "first," "second," and "third," etc., are used to distinguish different objects, etc., and do not indicate a sequence, nor do they limit "first," "second," and "third" to different types.
[0106] In the description of the embodiments of this application, terms such as "exemplary," "for example," or "for instance" are used to indicate examples, illustrations, or explanations. Any embodiment or design described as "exemplary," "for example," or "for instance" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of terms such as "exemplary," "for example," or "for instance" is intended to present the relevant concepts in a concrete manner.
[0107] In the description of the embodiments of this application, unless otherwise stated, " / " means "or". For example, A / B can mean A or B. The "and / or" in the text is merely a description of the relationship between related objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, and B exists alone. In addition, in the description of the embodiments of this application, "multiple" means two or more.
[0108] In some processes described in the embodiments of this application, multiple operations or steps are included in a specific order. However, it should be understood that these operations or steps may not be executed in the order they appear in the embodiments of this application, or they may be executed in parallel. The sequence number of the operation is only used to distinguish different operations, and the sequence number itself does not represent any execution order. In addition, these processes may include more or fewer operations, and these operations or steps may be executed sequentially or in parallel, and these operations or steps may be combined.
[0109] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) as described above, and includes several instructions to cause a terminal device to execute the methods described in the various embodiments of this application.
[0110] The above are merely preferred embodiments of this application and do not limit the patent scope of this application. Any equivalent structural or procedural transformations made using the content of this application's specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the patent protection scope of this application.
Claims
1. A network slice migration method, characterized in that, The network slice migration method includes: Find the extended object corresponding to the starting object, and add the starting object and the extended object to the migration set. The starting object and the extended object both conform to the preset migration rules. Each extended object is an associated object of the starting object or other extended objects. The service layer and the client layer it carries are associated objects of each other. If a target vLink exists in the set to be migrated, the target vLink is removed from the set to be migrated, and the target tunnel is searched in the set to be migrated. The target vLink is the exclusive vLink that needs to be retained in the current network slice, and the target tunnel is the associated object of the target vLink. Adjust the path of the target tunnel so that the adjusted target tunnel only passes through the set to be migrated and the vLink in the target network slice; Migrate objects from the set to be migrated to the target network slice.
2. The network slice migration method as described in claim 1, characterized in that, The steps of finding the extended object corresponding to the starting object and adding the starting object and the extended object to the migration set include: Add the starting object to the target queue and the set to be migrated; If the target queue is not empty, pop the earliest object in the target queue and record it as the first object; If a second object exists among the associated objects of the first object, then the second object is added to the target queue and the set to be migrated, wherein the second object meets the preset migration rules and is not in the set to be migrated; If the target queue is empty, then the search for extended objects is complete.
3. The network slice migration method as described in claim 1, characterized in that, The steps of finding the extended object corresponding to the starting object and adding the starting object and the extended object to the migration set include: Add the starting object to the target queue; If the target queue is not empty, pop the earliest object in the target queue, record it as the first object, and add the first object to the set to be migrated; If a second object exists among the associated objects of the first object, then the second object is added to the target queue, wherein the second object meets the preset migration rules and is not in the set to be migrated; If the target queue is empty, then the search for extended objects is complete.
4. The network slice migration method as described in claim 1, characterized in that, The step of adjusting the path of the target tunnel so that the adjusted target tunnel only passes through the vLink in the set to be migrated and the target network slice includes: For each target tunnel, vLinks that are not in the set to be migrated and the target network slice are used as exclusion links, and the target tunnel is re-routed to achieve path adjustment.
5. The network slice migration method as described in claim 1, characterized in that, Object types include vLink, MPLS-TP tunnel, SR-TP tunnel, FGU tunnel, VPN service, and CBR service; The client layer corresponding to vLink includes MPLS-TP tunnel, SR-TP tunnel and FGU tunnel; The client layer corresponding to MPLS-TP tunnels includes VPN services, and the corresponding service layer includes vLink and FGU tunnels. The SR-TP tunnel's customer layer includes VPN services, and its service layer includes vLink and FGU tunnels; The customer layer corresponding to FGU tunnels includes MPLS-TP tunnels, SR-TP tunnels, VPN services, and CBR services, while the corresponding service layer includes vLink. The service layer corresponding to VPN services includes MPLS-TP tunnels, SR-TP tunnels, and FGU tunnels; The service layer corresponding to CBR services includes the FGU tunnel.
6. The network slice migration method as described in claim 5, characterized in that, When an MPLS-TP tunnel or SR-TP tunnel is used as the service layer for VPN services, it is distinguished as the primary service layer or the backup service layer. The default migration rules include: If the current object is a third object, then the current object cannot be used as the starting object or the extension object. The third object is an SR-TP tunnel, and there is a VPN service with the MPLS-TP tunnel as the primary service layer and the SR-TP tunnel as the backup service layer. The service layer of the MPLS-TP tunnel is the FGU tunnel.
7. The network slice migration method as described in claim 6, characterized in that, The default migration rules also include: If the current object is a dedicated vLink and there is a third object among the associated objects of the current object, then the current object cannot be used as the starting object.
8. The network slice migration method as described in claim 1, characterized in that, The default migration rules include: If the current object is a shared vLink, then the current object cannot be used as the starting object; If the current object is a shared vLink and the current object is an extended object, then other associated objects of the current object cannot be used as new extended objects.
9. A network slice migration device, characterized in that, The network slice migration device includes: The object extension module is used to find the extension object corresponding to the starting object, and add the starting object and the extension object to the migration set. The starting object and the extension object both conform to the preset migration rules. Each extension object is an associated object of the starting object or other extension objects. The service layer and the client layer it carries are associated objects with each other. The object removal module is used to remove the target vLink from the migration set if the target vLink exists in the migration set, and to search for the target tunnel in the migration set. The target vLink is the exclusive vLink that needs to be retained in the current network slice, and the target tunnel is the associated object of the target vLink. The path adjustment module is used to adjust the path of the target tunnel so that the adjusted target tunnel only passes through the vLink in the set to be migrated and the target network slice; The object migration module is used to migrate objects from a set to be migrated to a target network slice.
10. A network slice migration device, characterized in that, The network slice migration device includes a processor, a memory, and a network slice migration program stored in the memory and executable by the processor, wherein when the network slice migration program is executed by the processor, it implements the steps of the network slice migration method as described in any one of claims 1 to 8.