Slice remapping method, apparatus and system
By monitoring load rates in radio access network nodes and remapping PDU sessions to target slices with lower loads, the problem of service interruption caused by resource shortages in radio access network nodes is solved, achieving service continuity and reducing signaling overhead.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- CHINA TELECOM CORP LTD
- Filing Date
- 2021-07-27
- Publication Date
- 2026-06-23
AI Technical Summary
When the load or resource usage of a radio access network node changes, rebuilding the PDU session in the existing technology leads to service interruption, increases signaling overhead, and affects user experience.
By receiving candidate slice identifiers from the core network, monitoring the current slice load rate, selecting a target slice identifier with a lower load, remapping the current PDU session to the target slice, maintaining the connection, and dynamically adjusting slice resource allocation.
Reduce service interruptions, lower signaling overhead, ensure business communication continuity, and improve user experience.
Smart Images
Figure CN115696450B_ABST
Abstract
Description
Technical Field
[0001] This disclosure relates to the field of communication technology, and in particular to slice remapping methods, apparatus and systems, and computer-storable media. Background Technology
[0002] Network slicing, a key technology in 5G networks, was a functional requirement introduced at the outset of the 5G standard. Network slicing allows operators to separate multiple virtual end-to-end networks on a unified infrastructure. Each network slice is logically isolated from the radio access network (RAN) to the bearer network and then to the core network to accommodate various types of applications. However, because the load and resource usage of RAN nodes constantly change, some slices within RAN nodes may not always be available.
[0003] In related technologies, in the absence of mobility, if the slice used by the service experiences resource shortage, it may be necessary to rebuild the PDU (Protocol Data Unit) session and allocate slices to the rebuilt PDU session. Summary of the Invention
[0004] In related technologies, rebuilding a PDU session can lead to service interruption, thus failing to guarantee service continuity. It also introduces more signaling overhead into the mobile network, affecting user experience.
[0005] To address the aforementioned technical issues, this disclosure proposes a solution that can reduce service interruptions, lower signaling overhead, and ensure service communication.
[0006] According to a first aspect of this disclosure, a slice remapping method is provided, comprising: receiving a slice identifier of a candidate slice corresponding to a current Protocol Data Unit (PDU) session with a User Equipment (UE) from a core network; in response to detecting that the load rate of the current slice is greater than the load rate threshold, obtaining stored slice identifiers of candidate slices corresponding to the current PDU session; selecting a slice identifier of a target slice from the slice identifiers of the candidate slices; and, while maintaining the connection of the current PDU session, remapping the current PDU session from the current slice to the target slice according to the slice identifier of the target slice.
[0007] In some embodiments, receiving a slice identifier of a candidate slice corresponding to the current PDU session from the core network includes receiving a slice remapping list of the current PDU session from the core network, the slice remapping list including a slice identifier of at least one candidate slice.
[0008] In some embodiments, receiving a slice remapping list corresponding to the current PDU session from the core network includes receiving an NG Interface Application Protocol (NGAP) message from the core network, the NGAP message including the slice remapping list corresponding to the current PDU session.
[0009] In some embodiments, remapping the current PDU session from the current slice to the target slice includes: allocating slice resources of the target slice to the current PDU session; and sending the slice identifier of the target slice to the core network and the user equipment (UE) corresponding to the current PDU session.
[0010] In some embodiments, sending the slice identifier of the target slice to the core network includes: sending an NG Interface Application Protocol (NGAP) message to the core network, wherein the NGAP message includes the slice identifier of the target slice.
[0011] In some embodiments, the NGAP message includes a PDU session resource establishment request message, an initial context setting request message, a PDU session resource modification request message, or a switch request message.
[0012] In some embodiments, sending the slice identifier of the target slice to the user equipment (UE) includes: sending a Radio Resource Control (RRC) message to the UE, the RRC message including the slice identifier of the target slice.
[0013] In some embodiments, the slice remapping method further includes: sending a PDU session establishment request from the UE to the core network before receiving a slice identifier of a candidate slice corresponding to the current PDU session from the core network; receiving a slice identifier of the current slice from the core network; and allocating slice resources of the current slice to the current PDU session of the UE according to the slice identifier of the current slice.
[0014] In some embodiments, all PDU sessions of the current slice correspond to the same candidate slice or different PDU sessions correspond to different candidate slices.
[0015] In some embodiments, selecting a target slice identifier from the slice identifiers of the candidate slices includes: selecting a target slice identifier from the slice identifiers of the candidate slices based on the load information of the candidate slices.
[0016] In some embodiments, the slice remapping method further includes: after remapping the current PDU session to the target slice, in response to detecting that the load rate of the current slice of the current PDU session is less than or equal to the load rate threshold, remapping the current PDU session from the target slice to the current slice.
[0017] According to a second aspect of this disclosure, a slice remapping apparatus is provided, comprising: a receiving module configured to receive a slice identifier of a candidate slice corresponding to a current Protocol Data Unit (PDU) session with a User Equipment (UE) from a core network; an acquiring module configured to acquire stored slice identifiers of candidate slices corresponding to the current PDU session in response to detecting that the load rate of the current slice is greater than the load rate threshold; a selecting module configured to select a slice identifier of a target slice from the slice identifiers of the candidate slices; and a remapping module configured to remap the current PDU session from the current slice to the target slice based on the slice identifier of the target slice while maintaining the connection of the current PDU session.
[0018] According to a third aspect of this disclosure, a slice remapping apparatus is provided, comprising: a memory; and a processor coupled to the memory, the processor being configured to execute the slice remapping method described in any of the above embodiments based on instructions stored in the memory.
[0019] According to a fourth aspect of this disclosure, a slice remapping system is provided, comprising: a next-generation radio access network (NG-RAN) node configured to: receive slice identifiers of candidate slices corresponding to a current Protocol Data Unit (PDU) session with a user equipment (UE) from a core network; in response to detecting that the load rate of the current slice is greater than the load rate threshold, acquire stored slice identifiers of candidate slices corresponding to the current PDU session; select a slice identifier of a target slice from the slice identifiers of the candidate slices; and, while maintaining the connection of the current PDU session, remap the current PDU session from the current slice to the target slice according to the slice identifier of the target slice.
[0020] In some embodiments, the slice remapping system further includes a core network configured to determine and send a slice identifier of a candidate slice corresponding to the current PDU session to the NG-RAN node.
[0021] In some embodiments, the core network is further configured to determine the slice identifier of the candidate slice corresponding to the current PDU session based on the service information of the current slice currently associated with the current PDU session.
[0022] In some embodiments, the NG-RAN node is further configured to: after remapping the current PDU session to the target slice, in response to detecting that the load rate of the current slice of the current PDU session is less than or equal to the load rate threshold, remap the current PDU session from the target slice to the current slice.
[0023] According to a fifth aspect of this disclosure, a computer-storeable medium is provided having computer program instructions stored thereon that, when executed by a processor, implement the slice remapping method described in any of the above embodiments.
[0024] In the above embodiments, service interruptions can be reduced, signaling overhead can be lowered, and service communication can be guaranteed. Attached Figure Description
[0025] The accompanying drawings, which form part of this specification, illustrate embodiments of this disclosure and, together with the specification, serve to explain the principles of this disclosure.
[0026] This disclosure will become clearer with reference to the accompanying drawings and the following detailed description.
[0027] in:
[0028] Figure 1 This is a flowchart illustrating a slice remapping method according to some embodiments of the present disclosure;
[0029] Figure 2 This is a block diagram illustrating a slice remapping apparatus according to some embodiments of the present disclosure;
[0030] Figure 3 This is a block diagram illustrating a slice remapping apparatus according to other embodiments of the present disclosure;
[0031] Figure 4 This is a block diagram illustrating a slice remapping system according to some embodiments of the present disclosure;
[0032] Figure 5 This is a block diagram illustrating a computer system for implementing some embodiments of the present disclosure. Detailed Implementation
[0033] Various exemplary embodiments of the present disclosure will now be described in detail with reference to the accompanying drawings. It should be noted that, unless otherwise specifically stated, the relative arrangement, numerical expressions, and values of the components and steps set forth in these embodiments do not limit the scope of the present disclosure.
[0034] At the same time, it should be understood that, for ease of description, the dimensions of the various parts shown in the accompanying drawings are not drawn according to actual scale.
[0035] The following description of at least one exemplary embodiment is merely illustrative and is in no way intended to limit this disclosure or its application or use.
[0036] Techniques, methods, and equipment known to those skilled in the art may not be discussed in detail, but where appropriate, such techniques, methods, and equipment should be considered part of the specification.
[0037] In all examples shown and discussed herein, any specific values should be interpreted as merely exemplary and not as limitations. Therefore, other examples of exemplary embodiments may have different values.
[0038] It should be noted that similar labels and letters in the following figures indicate similar items; therefore, once an item is defined in one figure, it does not need to be discussed further in subsequent figures.
[0039] Figure 1 This is a flowchart illustrating a slice remapping method according to some embodiments of the present disclosure.
[0040] like Figure 1 As shown, the slice remapping method includes steps S130-S160. For example, the slice remapping method is performed by a slice remapping device. In some embodiments, the slice remapping device is deployed in an NG-RAN (Next Generation Radio Access Network) node (also called a base station).
[0041] In step S130, a slice identifier for a candidate slice corresponding to the current PDU session of the UE (User Equipment) is received from the core network. In some embodiments, the slice identifier is S-NSSAI (Single Network Slice Selection Assistance Information).
[0042] In some embodiments, the slice identifier of the received candidate slice corresponding to the current PDU session may be stored.
[0043] In some embodiments, all PDU sessions of the current slice correspond to the same candidate slice, or different PDU sessions correspond to different candidate slices. By providing slice remapping strategies with different granularities, diverse remapping schemes are provided.
[0044] In some embodiments, a slice remapping list corresponding to the current PDU session may be received from the core network. The slice remapping list includes slice identifiers of at least one candidate slice. For example, the slice remapping list is an S-NSSAI list.
[0045] In some embodiments, NGAP (NG Application Protocol) messages can be received from the core network. NGAP messages include a list of slice remappings corresponding to the current PDU session.
[0046] For example, the NGAP messages disclosed herein include a PDU Session Resource Setup Request message, an Initial Context Setup Request message, a PDU Session Resource Modify Request message, or a Handover Request message. The Handover Request message is also referred to as an NG Handover Request message.
[0047] Taking the NGAP message including the PDU session resource establishment request message as an example, the message structure is a PDU session resource setup request list, which includes PDU session resource setup request signaling. The number of PDU session resource setup request signaling messages is equal to the number of PDU sessions requested by the UE, and its maximum number does not exceed 256.
[0048] The PDU session resource setup request signaling includes the PDU session identifier, non-access stratum PDU information, single network slice selection assistance information, PDU session slice remapping policy, and PDU session resource setup request transfer. The PDU session identifier is the PDU session ID, with a value ranging from 0 to 255. The non-access stratum PDU information is information about the PDU session configuration directly sent by the core network to the UE. The single network slice selection assistance information indicates the slice associated with the current PDU session, i.e., the original slice. The PDU session slice remapping policy includes a list containing at least one S-NSSAI; this information element is optional, and its absence indicates that the PDU session has no remapping policy. The PDU session resource setup request transfer includes user plane transport network layer information, PDU session type, and a QoS (Quality of Service) flow setting request list.
[0049] The slice remapping strategy for a PDU session includes single-network slice selection auxiliary information. This information indicates the slice used after the current PDU session is remapped. This signaling is optional; its absence indicates that no remapping has been performed.
[0050] Taking the NGAP message including the PDU session resource modification indication message as an example, this message is sent by the NG-RAN node and is used to request the AMF to enable modification of the established PDU session resources of a given UE. Its message structure is a PDU session resource modification indication list, which includes PDU session resource modification indication signaling items. The number of PDU session resource modification indication signaling items is equal to the number of PDU sessions requested for modification, and its maximum number does not exceed 256.
[0051] The PDU session resource modification indication signaling includes the PDU session identifier, single network slice selection auxiliary information, and PDU session resource modification indication transfer. The PDU session identifier is the PDU session ID, with a value ranging from 0 to 255. The single network slice selection auxiliary information indicates the slice used after the current PDU session is remapped; this information element is optional, and its absence indicates that remapping has not been performed. The PDU session resource modification indication transfer mainly contains QoS flow configuration information related to this PDU session.
[0052] In some embodiments, the load rate of the current slice currently associated with the current PDU session can be monitored.
[0053] In step S140, in response to detecting that the load rate of the current slice is greater than the load rate threshold, the slice identifier of the candidate slice corresponding to the current PDU session is obtained.
[0054] In step S150, the slice identifier of the target slice is selected from the slice identifiers of the candidate slices. In some embodiments, the slice identifier of the target slice is selected from the slice identifiers of the candidate slices based on the load information of the candidate slices. For example, the slice identifier of the candidate slice that can handle the current PDU session and has the lowest load rate is selected as the slice identifier of the target slice.
[0055] In step S160, while maintaining the current PDU session connection, the current PDU session is remapped from the current slice to the target slice according to the slice identifier of the target slice.
[0056] In some embodiments, slice resources for a target slice are allocated to the current PDU session, and the slice identifier of the target slice is sent to the core network and the user equipment (UE) corresponding to the current PDU session. For example, an NGAP message including the slice identifier of the target slice can be sent to the core network. Another example is that an RRC (Radio Resource Control) message, including the slice identifier of the target slice, can be sent to the UE.
[0057] In some embodiments, before receiving the slice identifier of the candidate slice corresponding to the current PDU session from the core network, a PDU session establishment request from the UE is sent to the core network; the slice identifier of the current slice is received from the core network; and slice resources of the current slice are allocated to the current PDU session of the UE based on the slice identifier of the current slice. By obtaining the slice identifier of the candidate slice corresponding to the PDU session in advance after each PDU session is established, candidate slices for different PDU sessions can be dynamically determined, improving the accuracy of remapping.
[0058] In some embodiments, after remapping the current PDU session to the target slice, the load rate of the current slice of the current PDU session is monitored; in response to detecting that the load rate of the current slice of the current PDU session is less than or equal to the load rate threshold, the current PDU session is remapped from the target slice to the current slice.
[0059] The slice remapping method of this disclosure will be described below with reference to some embodiments.
[0060] For example, assume that User Equipment 1 (UE1) and User Equipment 2 (UE2) access the network and establish their current PDU sessions using slice 1. UE1's current PDU sessions are PDU session 1 and PDU session 2, and both PDU session 1 and PDU session 2 are currently associated with slice S-NSSAI 1. UE2's current PDU session is PDU session 3, and PDU session 3 is currently associated with slice S-NSSAI 1.
[0061] For example, NG-RAN nodes receive slice remapping policies (including slice identifiers of candidate slices) related to user equipment UE1 and user equipment UE2 in advance from the core network via PDU session resource setting request messages or initial context setting request messages in NGAP messages.
[0062] In some embodiments, the granularity of the slice remapping strategy can be one slice remapping strategy per user equipment (UE).
[0063] For example, the slice remapping policy of User Equipment 1 can be represented as UE1, and the remapping list corresponding to the PDU session on S-NSSAI 1 is (S-NSSAI 2, S-NSSAI 3). The slice remapping policy of User Equipment 2 can be represented as UE2, and the remapping list corresponding to the PDU session on S-NSSAI 1 is (S-NSSAI 6, S-NSSAI 7).
[0064] In some embodiments, the granularity of the slice remapping strategy can also be one slice remapping strategy per PDU session.
[0065] For example, the slice remapping strategy for PDU session 1 can be represented as follows: UE 1, PDU session 1, S-NSSAI 1, the corresponding remapping list is (S-NSSAI 2, S-NSSAI 3). The slice remapping strategy for PDU session 2 can be represented as follows: UE 1, PDU session 2, S-NSSAI 1, the corresponding remapping list is (S-NSSAI 4, S-NSSAI 5). The slice remapping strategy for PDU session 3 can be represented as follows: UE 2, PDU session 3, S-NSSAI 1, the corresponding remapping list is (S-NSSAI 6, S-NSSAI 7).
[0066] UE1 and UE2 are operating normally. When the NG-RAN node detects a resource shortage in slice 1, it remaps the corresponding PDU session to a candidate slice according to the pre-obtained slice remapping policy to reduce service interruptions and informs the core network and UE of the modification of the corresponding PDU session resources.
[0067] If the remapping policy is granular at the per user equipment (UE) level, the remapping results are as follows: UE 1's PDU session 1 is remapped to slice S-NSSAI 2; PDU session 2 is remapped to slice S-NSSAI 2; UE 2's PDU session 3 is remapped to slice S-NSSAI 6.
[0068] If the remapping policy is granular at the per PDU session level, the remapping results are as follows: PDU session 1 of UE 1 is remapped to slice S-NSSAI 2; PDU session 2 is remapped to slice S-NSSAI 5; and PDU session 3 of UE 2 is remapped to slice S-NSSAI 6.
[0069] After a period of time, when slice 1 recovers sufficient resources, the NG-RAN node, according to the previously obtained slice remapping policy, restores UE1's PDU session to continue being served by slice 1, while UE2's PDU session remains unchanged. Specifically, UE1's PDU session 1 is remapped to slice S-NSSAI 1; PDU session 2 is remapped to slice S-NSSAI 1. UE2's PDU session 3 continues to use slice S-NSSAI 6. Finally, the core network and UE1 are notified of the corresponding PDU session resource modifications.
[0070] In the above embodiments, by pre-receiving the slice identifier of the candidate slice for the PDU session, the PDU session can be remapped from the original slice to one of the candidate slices while maintaining the connection of the PDU session, even when the original slice of the PDU session is overloaded. This reduces service interruption, lowers signaling overhead, and ensures service communication. This disclosure solves the problem of interrupting services in use due to resource shortages in slices, effectively improving user experience. Furthermore, it provides slice remapping strategies with different granularities, allowing the network to configure different parameters to adapt to different scenario requirements, enriching the selection methods during slice remapping. In addition, when the resources of the original slice are sufficient, the NG-RAN node supports the ability to restore services to the original slice.
[0071] Slice remapping is particularly suitable for scenarios lacking mobility. In situations lacking mobility, such as when a terminal remains camped in its current cell without handover, it may be necessary to release some ongoing PDU sessions associated with slice 1 due to resource saturation within the base station. Alternatively, even when slice 1 within the base station is saturated, the core network may still allocate resources from slice 1 for new PDU sessions requested by the terminal.
[0072] Figure 2 This is a block diagram illustrating a slice remapping apparatus according to some embodiments of the present disclosure.
[0073] like Figure 2 As shown, the slice remapping device 21 includes a receiving module 213, an acquisition module 214, a selection module 215, and a remapping module 216. For example, the slice remapping device 21 is deployed in an NG-RAN node (base station).
[0074] The receiving module 213 is configured to receive the slice identifier of the candidate slice corresponding to the current Protocol Data Unit (PDU) session with the User Equipment (UE) from the core network, for example, by performing... Figure 1 The step S130 shown.
[0075] The acquisition module 214 is configured to, in response to detecting that the load rate of the current slice is greater than the load rate threshold, acquire the slice identifier of the stored candidate slice corresponding to the current PDU session, for example, by performing the following... Figure 1 The step S140 shown.
[0076] The selection module 215 is configured to select the slice identifier of the target slice from the slice identifiers of the candidate slices, for example, by performing the following: Figure 1 The step S150 shown.
[0077] The remapping module 216 is configured to, while maintaining the current PDU session connection, remap the current PDU session from the current slice to the target slice based on the slice identifier of the target slice, for example, by performing the following... Figure 1 The step S160 shown.
[0078] Figure 3 This is a block diagram illustrating a slice remapping apparatus according to other embodiments of the present disclosure.
[0079] like Figure 3 As shown, the slice remapping apparatus 31 includes a memory 311 and a processor 312 coupled to the memory 311. The memory 311 is used to store instructions for executing embodiments of the slice remapping method. The processor 312 is configured to execute slice remapping methods in any of the embodiments of this disclosure based on the instructions stored in the memory 311. For example, the slice remapping apparatus 31 is deployed in an NG-RAN node (base station).
[0080] Figure 4 This is a block diagram illustrating a slice remapping system according to some embodiments of the present disclosure.
[0081] like Figure 4 As shown, the slice remapping system 4 includes NG-RAN node 41.
[0082] NG-RAN node 41 is configured to: after allocating slice resources of the current slice associated with the current PDU session to the current PDU session, receive the slice identifier of the candidate slice corresponding to the current Protocol Data Unit (PDU) session with the User Equipment (UE) from the core network; in response to detecting that the load rate of the current slice is greater than the load rate threshold, obtain the stored slice identifiers of the candidate slices corresponding to the current PDU session; select the slice identifier of the target slice from the slice identifiers of the candidate slices; and, while maintaining the connection of the current PDU session, remap the current PDU session from the current slice to the target slice according to the slice identifier of the target slice.
[0083] In some embodiments, NG-RAN node 41 is further configured to: allocate slice resources of the target slice for the current PDU session; and send the slice identifier of the target slice to the core network and the UE corresponding to the current PDU session.
[0084] In some embodiments, NG-RAN node 41 is further configured to: after remapping the current PDU session to the target slice, in response to detecting that the load rate of the current slice of the current PDU session is less than or equal to the load rate threshold, remapping the current PDU session from the target slice to the current slice.
[0085] In some embodiments, the slice remapping system 4 further includes a core network 42. The core network 42 is configured to determine and send the slice identifier of the candidate slice corresponding to the current PDU session to the NG-RAN node 41.
[0086] In some embodiments, the core network 42 is further configured to determine the slice identifier of the candidate slice corresponding to the current PDU session based on the service information of the current slice currently associated with the current PDU session.
[0087] In some embodiments, the slice remapping system 4 further includes a UE 40. The UE 40 is configured to send a PDU session establishment request to the NG-RAN node 41. The PDU session establishment request is used to request the establishment of a current PDU session for the UE 40.
[0088] NG-RAN node 41 is also configured to receive PDU session establishment requests from UE 40 and send PDU session establishment requests to core network 42.
[0089] Core network 42 is also configured to establish a current PDU session for UE 40, determine the slice identifier of the current slice used by the current PDU session, and send the determined slice identifier of the current slice to NG-RAN node 41. Core network 42 is also configured to send the determined slice identifier of the current slice to UE 40.
[0090] NG-RAN node 41 is also configured to allocate slice resources for the current PDU session based on the determined slice identifier of the current slice. For example, after allocating slice resources for the current PDU session, NG-RAN node 41 receives the slice identifier of the candidate slice corresponding to the current Protocol Data Unit (PDU) session with the User Equipment (UE) from the core network.
[0091] Figure 5 This is a block diagram illustrating a computer system for implementing some embodiments of the present disclosure.
[0092] like Figure 5As shown, the computer system 50 can be represented in the form of a general computing device. The computer system 50 includes a memory 510, a processor 520, and a bus 500 connecting different system components.
[0093] The memory 510 may include, for example, system memory, non-volatile storage media, etc. The system memory may store, for example, an operating system, application programs, a boot loader, and other programs. The system memory may include volatile storage media, such as random access memory (RAM) and / or cache memory. The non-volatile storage media may store, for example, instructions for performing at least one of the corresponding embodiments of the slice remapping method. Non-volatile storage media include, but are not limited to, disk storage, optical storage, flash memory, etc.
[0094] The processor 520 can be implemented using a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic devices, discrete hardware components such as discrete gates or transistors. Accordingly, each module, such as the decision module and the determination module, can be implemented by executing instructions in the central processing unit (CPU) memory to perform the corresponding steps, or by implementing dedicated circuitry to perform the corresponding steps.
[0095] Bus 500 can use any of the various bus architectures. For example, bus architectures include, but are not limited to, Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, and Peripheral Component Interconnect (PCI) bus.
[0096] The computer system 50 may also include an input / output interface 530, a network interface 540, and a storage interface 550. These interfaces 530, 540, and 550, as well as the memory 510 and processor 520, can be connected via a bus 500. The input / output interface 530 provides a connection interface for input / output devices such as a monitor, mouse, and keyboard. The network interface 540 provides a connection interface for various networked devices. The storage interface 550 provides a connection interface for external storage devices such as floppy disks, USB flash drives, and SD cards.
[0097] Various aspects of this disclosure are described herein with reference to flowchart illustrations and / or block diagrams of methods, apparatus, and computer program products according to embodiments of this disclosure. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations thereof, can be implemented by computer-readable program instructions.
[0098] These computer-readable program instructions are provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable device to produce a machine, such that execution of the instructions by the processor produces means for implementing the functions specified in one or more boxes of the flowchart and / or block diagram.
[0099] These computer-readable program instructions may also be stored in a computer-readable storage medium. These instructions cause a computer to work in a particular manner to produce an article of manufacture, including instructions that implement the functions specified in one or more boxes in a flowchart and / or block diagram.
[0100] This disclosure may take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects.
[0101] The slice remapping method, apparatus, system, and computer-storable medium described in the above embodiments can reduce service interruptions, lower signaling overhead, and ensure service communication.
[0102] This concludes the detailed description of the slice remapping method, apparatus, system, and computer-storable medium according to this disclosure. To avoid obscuring the concept of this disclosure, some details known in the art have not been described. Those skilled in the art will fully understand how to implement the technical solutions disclosed herein based on the above description.
Claims
1. A slice remapping method, applied to a base station, comprising: When a user equipment (UE) lacks mobility, a slice remapping policy corresponding to the current Protocol Data Unit (PDU) session of the UE is received from the core network. The granularity of the slice remapping policy includes one remapping policy for each user equipment or one remapping policy for each PDU session. The slice remapping policy includes the slice identifier of the candidate slice. In response to detecting that the load rate of the current slice is greater than the load rate threshold, obtain the slice identifier of the candidate slice corresponding to the current PDU session; Select the slice identifier of the target slice from the slice identifiers of the candidate slices; While maintaining the current PDU session connection, the current PDU session is remapped from the current slice to the target slice according to the slice identifier of the target slice; In response to detecting that the load rate of the current slice of the current PDU session is less than or equal to the load rate threshold, the current PDU session is remapped from the target slice to the current slice.
2. The slice remapping method according to claim 1, wherein, The slice identifier received from the core network corresponding to the current PDU session includes: Receive a slice remapping list corresponding to the current PDU session from the core network, the slice remapping list including slice identifiers of at least one candidate slice.
3. The slice remapping method according to claim 2, wherein, The slice remapping list received from the core network corresponding to the current PDU session includes: Receive an NGAP message from the core network, the NGAP message including a slice remapping list corresponding to the current PDU session.
4. The slice remapping method according to claim 1, wherein, Remapping the current PDU session from the current slice to the target slice includes: Allocate the slice resources of the target slice to the current PDU session; The slice identifier of the target slice is sent to the core network and the user equipment (UE) corresponding to the current PDU session, respectively.
5. The slice remapping method according to claim 4, wherein, Sending the slice identifier of the target slice to the core network includes: Send an NGAP message to the core network, the NGAP message including the slice identifier of the target slice.
6. The slice remapping method according to claim 3 or 5, wherein, The NGAP messages include PDU session resource establishment request messages, initial context setting request messages, PDU session resource modification request messages, or switchover request messages.
7. The slice remapping method according to claim 4, wherein, Sending the slice identifier of the target slice to the user equipment (UE) includes: A Radio Resource Control (RRC) message is sent to the UE, the RRC message including the slice identifier of the target slice.
8. The slice remapping method according to claim 1, further comprising: Before receiving the slice identifier of the candidate slice corresponding to the current PDU session from the core network, a PDU session establishment request from the UE is sent to the core network; Receive the slice identifier of the current slice from the core network; Based on the slice identifier of the current slice, allocate slice resources of the current slice to the current PDU session of the UE.
9. The slice remapping method according to claim 1, wherein, All PDU sessions in the current slice correspond to the same candidate slice, or different PDU sessions correspond to different candidate slices.
10. The slice remapping method according to claim 1, wherein, The slice identifiers for selecting the target slice from the candidate slice identifiers include: Based on the load information of the candidate slices, the slice identifier of the target slice is selected from the slice identifiers of the candidate slices.
11. A slice remapping device, applied to a base station, comprising: The receiving module is configured to receive a slice remapping policy corresponding to the current Protocol Data Unit (PDU) session of the user equipment (UE) from the core network when the user equipment (UE) lacks mobility. The granularity of the slice remapping policy includes one remapping policy for each user equipment or one remapping policy for each PDU session. The slice remapping policy includes a slice identifier of a candidate slice. The acquisition module is configured to acquire the segment identifier of the candidate segment corresponding to the current PDU session in response to detecting that the load rate of the current segment is greater than the load rate threshold. The selection module is configured to select the slice identifier of the target slice from the slice identifiers of the candidate slices; The remapping module is configured to remap the current PDU session from the current slice to the target slice based on the slice identifier of the target slice, while maintaining the current PDU session connection; In response to detecting that the load rate of the current slice of the current PDU session is less than or equal to the load rate threshold, the current PDU session is remapped from the target slice to the current slice.
12. A slice remapping apparatus, comprising: Memory; as well as A processor coupled to the memory, the processor being configured to execute the slice remapping method as described in any one of claims 1 to 10 based on instructions stored in the memory.
13. A slice remapping system, comprising: Next-generation radio access network (NG-RAN) nodes are configured as follows: When a user equipment (UE) lacks mobility, a slice remapping policy corresponding to the current Protocol Data Unit (PDU) session with the UE is received from the core network. The granularity of the slice remapping policy includes one remapping policy for each UE or one remapping policy for each PDU session. The slice remapping policy includes the slice identifier of the candidate slice. In response to detecting that the load rate of the current slice is greater than the load rate threshold, obtain the slice identifier of the candidate slice corresponding to the current PDU session; Select the slice identifier of the target slice from the slice identifiers of the candidate slices; While maintaining the current PDU session connection, the current PDU session is remapped from the current slice to the target slice according to the slice identifier of the target slice; In response to detecting that the load rate of the current slice of the current PDU session is less than or equal to the load rate threshold, the current PDU session is remapped from the target slice to the current slice.
14. The slice remapping system according to claim 13, further comprising: The core network is configured to determine and send the slice identifier of the candidate slice corresponding to the current PDU session to the NG-RAN node.
15. The slice remapping system according to claim 14, wherein, The core network is also configured to determine the slice identifier of the candidate slice corresponding to the current PDU session based on the service information of the current slice associated with the current PDU session.
16. A computer-storeable medium having stored thereon computer program instructions that, when executed by a processor, implement the slice remapping method as described in any one of claims 1 to 10.