Management node in wireless communication system having network slicing environment and operation method thereof
The management node in the wireless communication system addresses the challenge of adapting network slices by reallocating slicing entities to maintain service quality and stability, ensuring continuous and sustainable service through autonomous reallocation and self-healing capabilities.
Patent Information
- Application Number
- PCT/KR2024/005839
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-31
- Filing Date
- 2024-04-30
- Publication Date
- 2024-11-14
AI Technical Summary
In wireless communication systems, especially in network slicing environments, there is a need for efficient management of slicing entities to ensure that network slices meet specific requirements and adapt to reallocation events, such as failures or performance degradation, without disrupting service.
A management node is implemented that can allocate and reallocate slicing entities in response to allocation requests and reallocation events, using existing or newly created entities to maintain service quality, with the ability to detect and manage reallocation triggering conditions autonomously.
This solution ensures continuous service quality and stability by enabling autonomous reallocation of slicing entities, maintaining service level agreements, and providing self-healing capabilities within the network slice, thus ensuring uninterrupted and sustainable service.
Smart Images

Figure KR2024005839_14112024_PF_FP_ABST
Abstract
Description
Management node and its operation method in a wireless communication system having a network slicing environment
[0001] The present disclosure relates to a management node and its operating method in a wireless communication system. More particularly, the present disclosure relates to a management node and its operating method for managing network entities in a wireless communication system having a network slicing environment.
[0002] 5G (fifth generation) mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in the sub-6GHz frequency band such as 3.5 gigahertz (3.5GHz), but also in the ultra-high frequency band called millimeter wave (mmWave) such as 28GHz and 39GHz ('Above 6GHz'). In addition, 6G mobile communication technology, which is called the system after 5G communication (Beyond 5G), is being considered for implementation in the terahertz band (for example, the 3 terahertz (3THz) band at 95GHz) to achieve a transmission speed that is 50 times faster than 5G mobile communication technology and an ultra-low latency time that is reduced to one-tenth.
[0003] In the early stages of 5G mobile communication technology, the goal is to support services and meet performance requirements for enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC). These include beamforming and massive MIMO to mitigate path loss and increase the transmission distance of radio waves in ultra-high frequency bands, support for various numerologies (such as operation of multiple subcarrier intervals) and dynamic operation of slot formats for efficient use of ultra-high frequency resources, initial access technology to support multi-beam transmission and wideband, definition and operation of BWP (Bidth Part), new channel coding methods such as LDPC (Low Density Parity Check) codes for large-capacity data transmission and Polar Code for reliable transmission of control information, and L2 pre-processing (L2). Standardization has been made for network slicing, which provides dedicated networks specialized for specific services, and pre-processing.
[0004] Currently, discussions are underway to improve and enhance the initial 5G mobile communication technology in consideration of the services that 5G mobile communication technology was intended to support, and physical layer standardization is in progress for technologies such as V2X (Vehicle-to-Everything) to help autonomous vehicles make driving decisions and increase user convenience based on their own location and status information transmitted by vehicles, NR-U (New Radio Unlicensed) for the purpose of system operation that complies with various regulatory requirements in unlicensed bands, NR terminal low power consumption technology (UE Power Saving), Non-Terrestrial Network (NTN), which is direct terminal-satellite communication to secure coverage in areas where communication with terrestrial networks is impossible, and Positioning.
[0005] In addition, standardization of radio interface architecture / protocols for technologies such as intelligent factories (Industrial Internet of Things, IoT) to support new services through linkage and convergence with other industries, Integrated Access and Backhaul (IAB) that provides nodes for expanding network service areas by integrating wireless backhaul links and access links, Mobility Enhancement technology including Conditional Handover and Dual Active Protocol Stack (DAPS) handover, and 2-step random access (2-step RACH for NR) to simplify random access procedures is also in progress, and standardization of system architecture / services for 5G baseline architecture (e.g., Service-based Architecture, Service-based Interface) for grafting Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) that provides services based on the location of the terminal is also in progress.
[0006] Once these 5G mobile communication systems are commercialized, an explosive increase in connected devices will be connected to the communication network, necessitating enhanced functionality and performance of 5G mobile communication systems and integrated operation of these connected devices. To this end, new research will be conducted on improving 5G performance and reducing complexity, supporting AI services, supporting metaverse services, and drone communications by utilizing eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).
[0007] In addition, the development of these 5G mobile communication systems includes new waveforms for coverage guarantee in the terahertz band of 6G mobile communication technology, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), Array Antenna, and Large Scale Antenna, metamaterial-based lenses and antennas to improve the coverage of terahertz band signals, high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM), Reconfigurable Intelligent Surface (RIS) technology, as well as full duplex technology for improving the frequency efficiency and system network of 6G mobile communication technology, satellite, AI (Artificial Intelligence) from the design stage and internalizing end-to-end AI support functions to realize system optimization, and ultra-high-performance communication and computing resources for services with complexity that exceeds the limits of terminal computing capabilities. It can serve as a basis for the development of next-generation distributed computing technologies that can be realized by utilizing them.
[0008] Meanwhile, in wireless communication systems such as 5G mobile communication systems, network slicing can be a network architecture that enables multiple virtualized, independent logical networks within the same physical network infrastructure. Each network slice (or subnet) can represent an isolated, end-to-end network tailored to meet the diverse requirements of specific applications. Network slicing technology allows multiple virtualized logical networks to exist within a single physical network.
[0009] The above information is provided solely as background information to aid in understanding the contents of this disclosure. It cannot be determined whether any of the above information constitutes prior art related to the present disclosure, and no claims are made.
[0010] According to one aspect of the present disclosure, a method of operating a management node in a wireless communication system having a network slicing environment is provided. The method includes an operation of allocating a first slicing entity that satisfies specified requirements for a network slice to a lower-level management node in response to an allocation request from a higher-level management node, an operation of detecting an occurrence of a reassignment event, and an operation of reallocating a second slicing entity, among slicing entities managed by the management node, that satisfies the specified requirements, to the lower-level management node in response to the occurrence of the reassignment event.
[0011] According to another aspect of the present disclosure, a management node is provided. The management node may include a transceiver, a memory storing one or more computer programs, and one or more processors communicatively connected to the transceiver and the memory. The one or more computer programs include computer-executable instructions that, when executed by the one or more processors, cause the management node, in response to an allocation request from a higher-level management node, to allocate a first slicing entity that satisfies specified requirements for a network slice to a lower-level management node, detect the occurrence of a reassignment event, and in response to the occurrence of the reassignment event, to allocate a second slicing entity that satisfies the specified requirements among slicing entities managed by the management node to the lower-level management node.
[0012] According to another aspect of the present disclosure, one or more non-transitory computer-readable storage media are provided. The non-transitory storage media stores one or more computer programs comprising computer-executable instructions that, when executed by one or more processors of a management node, cause the management node to perform the following operations: in response to an allocation request from a higher-level management node, allocate a first slicing entity that satisfies specified requirements for a network slice to a lower-level management node; detect an occurrence of a reassignment event; and in response to the occurrence of the reassignment event, reallocate a second slicing entity among slicing entities managed by the management node that satisfies the specified requirements to the lower-level management node.
[0013] Other embodiments, advantages and features of the present disclosure will become apparent to those skilled in the art from the following detailed description of various embodiments taken in conjunction with the accompanying drawings.
[0014] FIG. 1 illustrates a communication network including network entities in a wireless communication system according to various embodiments.
[0015] FIG. 2a is a diagram exemplarily showing the structure of network slices in a wireless communication system according to one embodiment.
[0016] FIG. 2b illustrates the configuration of a management node in a wireless communication system according to one embodiment.
[0017] FIG. 3 is a flowchart illustrating an operation method of a management node in a wireless communication system according to one embodiment.
[0018] FIG. 4 is a flowchart illustrating a method for reallocating slicing entities by a break before make technique in a wireless communication system according to one embodiment.
[0019] FIG. 5A and FIG. 5B are flowcharts illustrating operations prior to reallocation execution when reallocating a slicing entity by a pre-generation stop technique in a wireless communication system according to one embodiment.
[0020] FIGS. 6A and 6B are diagrams for explaining reassignment triggering conditions in a wireless communication system according to one embodiment.
[0021] FIG. 7A and FIG. 7B are flowcharts illustrating reallocation execution operations when reallocating a slicing entity by a pre-generation interrupt technique in a wireless communication system according to one embodiment.
[0022] FIG. 8 is a flowchart illustrating a method of reallocating slicing entities by a pre-allocation technique in a wireless communication system according to one embodiment.
[0023] FIG. 9 is a flowchart illustrating a method for reallocating a slicing entity by a late deprovisioning technique in a wireless communication system according to one embodiment.
[0024] It should be understood that the various embodiments of the present disclosure and the terminology used therein are not intended to limit the technical features described in the present disclosure to specific embodiments, but include various modifications, equivalents, or alternatives of the embodiments.
[0025] Methods according to various embodiments of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software. If implemented in software, a computer-readable storage medium storing one or more programs (software modules) may be provided. The one or more programs stored in the computer-readable storage medium are configured for execution by one or more processors within an electronic device. The one or more programs include instructions that cause the electronic device to execute methods according to embodiments described in the claims or specification of the present disclosure.
[0026] These programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, read only memory (ROM), electrically erasable programmable read only memory (EEPROM), magnetic disc storage devices, compact disc-ROMs (CD-ROMs), digital versatile discs (DVDs) or other forms of optical storage devices, magnetic cassettes, or may be stored in memories formed by a combination of some or all of these. In addition, each configuration memory may include multiple copies.
[0027] Additionally, the program may be stored on an attachable storage device that is accessible via a communication network, such as the Internet, an intranet, a local area network (LAN), a wide area network (WAN), a storage area network (SAN), or a combination thereof. Such a storage device may be connected to a device implementing an embodiment of the present disclosure via an external port. Additionally, a separate storage device on the communication network may be connected to a device implementing an embodiment of the present disclosure.
[0028] In various embodiments of the present disclosure, components are expressed singularly or plurally, depending on the specific embodiments presented. However, the singular or plural expressions are selected to suit the presented situation for convenience of explanation, and the present disclosure is not limited to singular or plural components. Components expressed plurally may be composed of singular elements, or components expressed singularly may be composed of plural elements.
[0029] The terms used in the following description, including terms referring to signals, channels, control information, network entities, and device components, are provided for convenience of explanation. Therefore, the present disclosure is not limited to the terms described below, and other terms with equivalent technical meanings may be used.
[0030] Additionally, while this disclosure describes various embodiments using terminology used in certain communication standards (e.g., 3rd generation partnership project (3GPP)), these are merely illustrative examples. The various embodiments of this disclosure can be easily modified and applied to other communication systems.
[0031] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings so that those skilled in the art can easily implement the present disclosure. However, the present disclosure may be implemented in various different forms and is not limited to the embodiments described herein. In connection with the description of the drawings, the same or similar reference numerals may be used for identical or similar components. Furthermore, in the drawings and related descriptions, descriptions of well-known functions and configurations may be omitted for clarity and conciseness.
[0032] The combinations between blocks within each flowchart and between flowcharts can be performed by one or more computer programs containing instructions. One or more computer programs may be stored entirely in a single memory device, or one or more computer programs may be divided into different parts and stored in multiple memory devices.
[0033] The functions or operations described in this document may be processed by a single processor or a combination of processors. A single processor or a combination of processors is a circuit that performs processing and includes circuits such as an application processor (AP, e.g., a central processing unit (CPU)), a communication processor (CP, e.g., a modem), a graphics processing unit (GPU), a neural processing unit (NPU) (e.g., an artificial intelligence (AI) chip), a Wi-Fi chip, a Bluetooth® chip, a global positioning system (GPS) chip, a near-field communication (NFC) chip, a connection chip, a sensor controller, a touch controller, a fingerprint sensor controller, a display driver integrated circuit (IC), an audio codec chip, a universal serial bus (USB) controller, a camera controller, an image processing IC, a microprocessor unit (MPU), a system on a chip (SoC), an integrated circuit (IC), and the like.
[0034] FIG. 1 illustrates a communication network including network entities in a wireless communication system according to various embodiments.
[0035] Referring to FIG. 1, a 5G mobile communication network of a wireless communication system (100) may include a user equipment (UE) (110), a radio access network (RAN) (120), and a core network (CN).
[0036] The core network is a network that manages the entire system, controls the RAN (120), and can process data and control signals for the UE (110) transmitted and received through the RAN (120). The core network can perform various functions, such as controlling the user plane and the control plane, processing mobility, managing subscriber information, billing, and interworking with other types of systems (e.g., long term evolution (LTE) systems). In order to perform the various functions described above, the core network can include multiple functionally separated entities having different network functions (NFs).
[0037] The core network may be configured to include network functions such as an access and mobility management function (AMF) (150) that provides a mobility management function of UE, a session management function (SMF) (160) that provides a session management function, a user plane function (UPF) (170) that performs a data transfer role, a policy control function (PCF) (180) that provides a policy control function, a network slice selection function (NSSF) (190) that provides a network slice selection function, a unified data management (UDM) (153) that provides a data management function such as subscriber data and policy control data, or a unified data repository (UDR) that stores data of various network functions. Although not illustrated in FIG. 1, the core network may further include a communication service management function (CSMF), a network slice management function (NSMF), and a network slice subnet management function (NSSMF) for creating a network slice and verifying a user service.
[0038] Referring to FIG. 1, a user equipment (UE) (110) may communicate with a base station (e.g., an eNB, a gNB) via a wireless channel, i.e., an access network. In some embodiments, the UE (110) may be a device used by a user and configured to provide a user interface (UI). As an example, the UE (110) may be a terminal mounted (equipment) on a vehicle for driving. In some other embodiments, the UE (110) may be a device that performs machine type communication (MTC) that operates without user intervention, or may be an autonomous vehicle. UE may be referred to as a 'terminal', 'vehicle terminal', 'user equipment (UE)', 'mobile station', 'subscriber station', 'remote terminal', 'wireless terminal', or 'user device' or other terms having equivalent technical meanings, other than electronic devices. As the terminal, in addition to the UE, a customer-premises equipment (CPE) or a dongle-type terminal may be used. The CPE, while connected to the NG-RAN node like the UE, may also provide a network to other communication devices (e.g., a laptop).
[0039] Referring to FIG. 1, the AMF (150) provides a function for connection and mobility management per terminal (110), and basically, one AMF (150) can be connected to one terminal (110). Specifically, the AMF (150) can perform at least one of signaling between core network nodes for mobility between 3GPP access networks, an interface (N2 interface) between wireless access networks (e.g., RAN (120)), NAS signaling with the terminal (110), identification of the SMF (160), and provision of transmission of session management (SM) messages between the terminal (110) and the SMF (160). Some or all of the functions of the AMF (150) can be supported within a single instance of one AMF (150).
[0040] Referring to FIG. 1, the SMF (160) provides a session management function, and when the terminal (110) has multiple sessions, each session may be managed by a different SMF (160). Specifically, the SMF (160) may perform at least one of the following functions: session management (e.g., session establishment, modification, and release, including tunnel maintenance between the UPF (170) and the access network node), selection and control of UP (user plane) functions, traffic steering setup for routing traffic to an appropriate destination in the UPF (170), termination of the SM portion of NAS messages, downlink data notification (DDN), and initiation of AN-specific SM information (e.g., delivery to the access network via the N2 interface via the AMF (150)). Some or all of the functions of the SMF (160) may be supported within a single instance of one SMF (160).
[0041] In 3GPP systems, conceptual links connecting network functions (NFs) within a 5G system may be referred to as reference points. Reference points may also be referred to as interfaces. The following illustrates reference points included in the 5G system architecture represented across Figures 1, 2a, 2b, 3, 4, 5a, 5b, 6a, 6b, 7a, 7b, 8, and 9.
[0042] - N1: Reference point between UE (110) and AMF (150)
[0043] - N2: Reference point between (R)AN(120) and AMF(150)
[0044] - N3: Reference point between (R)AN(120) and UPF(170)
[0045] - N4: Reference point between SMF (160) and UPF (170)
[0046] - N5: Reference point between PCF (180) and AF (130)
[0047] - N6: Reference point between UPF (170) and DN (140)
[0048] - N7: Reference point between SMF (160) and PCF (180)
[0049] - N8: Reference point between UDM (153) and AMF (150)
[0050] - N9: Reference point between two core UPFs (170)
[0051] - N10: Reference point between UDM (153) and SMF (160)
[0052] - N11: Reference point between AMF (150) and SMF (160)
[0053] - N12: Reference point between AMF (150) and authentication server function (AUSF) (151)
[0054] - N13: Reference point between UDM (153) and authentication server function (151)
[0055] - N14: Reference point between two AMFs (150)
[0056] - N15: For non-roaming scenarios, reference point between PCF (180) and AMF (150), for roaming scenarios, reference point between PCF (180) and AMF (150) within the visited network.
[0057] FIG. 2a is a diagram exemplarily showing the structure of network slices in a wireless communication system according to one embodiment.
[0058] According to various embodiments, by applying network slicing technology to a wireless communication system (e.g., a 5G mobile communication network of FIG. 1) including an access network (AN) (120) and a core network (CN) (200), multiple logical networks can be spawned on a single physical network infrastructure, and each logical network can be given unique characteristics suited to specific service requirements. A wireless communication system having a network slicing environment can include slicing entities, which are components of each network slice (or subnet).
[0059] In one embodiment, network slicing may be implemented based on a hierarchical structure of slicing entities (or network entities). Because network slices are complex and must encompass different management domains, each network slice must be composed of independent, lower-level building blocks that may contain lower-level blocks within them.
[0060] In one embodiment, a slicing entity may mean an entity that is subject to management (e.g., allocation, deallocation, or reallocation) or a managed entity.
[0061] In one embodiment, a slicing entity constituting a network slice may be any one of a communication service instance (CSI), a network slice instance (NSI), a network slice subnet instance (NSSI), a managed function instance (MFI), or a combination thereof. The slicing entities may be managed by dedicated management systems. The dedicated management systems may perform network slicing management and / or coordination (e.g., allocation, deallocation, reallocation, etc. of slicing entities). For example, the dedicated management systems may be any one of a communication service management function(s) (CSMF) for managing CSIs, a network slice management function(s) (NSMF) for managing NSIs, a network slice subnet management function(s) (NSSMF) for managing NSSIs, a network function management function(s) (NFMF) for managing MFIs, or a combination thereof.
[0062] FIG. 2b illustrates the configuration of a management node in a wireless communication system according to one embodiment.
[0063] According to one embodiment, the management node (20) may be a device or function that manages one or more slicing entities. The management node (20) may also be referred to as a management entity, a management system, or a management function. In one embodiment, the management node (20) may correspond to a device or function that manages a lower-level entity among multi-level entities (higher-level entities and lower-level entities) included in a wireless communication system. For example, the management node (20) may correspond to a function or device corresponding to at least one of CSMF, NSMF, NSSMF, or NFMF. Terms such as '... unit', '... device', etc. used hereinafter mean a unit that processes at least one function or operation, and this may be implemented by hardware, software, or a combination of hardware and software.
[0064] Referring to FIG. 2b, a management node (20) according to one embodiment may include a communication unit (210) and a control unit (220). In one embodiment, the management node (20) may further include a storage unit (230).
[0065] In one embodiment, the communication unit (210) may provide an interface for communicating with other devices within the network. For example, the communication unit (210) may convert a bit string transmitted from the management node (20) to another device (or an external electronic device) into a physical signal, and may convert a physical signal received from another device into a bit string. In one embodiment, the communication unit (210) may transmit and / or receive signals. Accordingly, the communication unit (210) may be referred to as a modem, a transmitter, a receiver, or a transceiver. The communication unit (210) may support the management node (20) to communicate with other devices or systems via a backhaul connection (e.g., a wired backhaul or a wireless backhaul) or via a network.
[0066] In one embodiment, the storage unit (230) may store data such as basic programs, application programs, and setting information for the operation of the management node (20). The storage unit (230) may be composed of volatile memory, non-volatile memory, or a combination of volatile and non-volatile memory. The storage unit (230) may provide stored data upon request from the control unit (220).
[0067] In one embodiment, the control unit (220) may include at least one processor communicatively and / or operatively connected to the communication unit (210). The control unit (220) may control the overall operations of the management node (20). For example, the control unit (220) may transmit and receive signals via the communication unit (210). In addition, the control unit (220) may write data to the storage unit (230) or read data from the storage unit (230). The control unit (220) may execute instructions (or programs) stored in the storage unit (203) to perform a designated function.
[0068] According to one embodiment, a control unit (220) of a management node (20) (e.g., a lower-level management system (21) of FIG. 4) may, in response to an allocation request from a higher-level management node (e.g., a higher-level management system (22) of FIG. 4), allocate a first slicing entity (or an original slicing entity) that satisfies specified requirements for a network slice to a lower-level management node (e.g., an external lower-level management system (23) of FIG. 4). The control unit (220) may detect the occurrence of a reassignment event.
[0069] In one embodiment, the reassignment event may correspond to a reassignment triggering condition associated with the first slicing entity or a lower-level management node. For example, the reassignment triggering condition may include at least one of a failure of the first slicing entity, a failure of the lower-level management node, non-fulfillment of requirements attached (or stored) to the first slicing entity, occurrence of a reassignment trigger request, and degradation of the performance of the first slicing entity below a pre-specified threshold.
[0070] In response to the occurrence of the reassignment event, the control unit (220) can reassign a second slicing entity that satisfies the specified requirements among the slicing entities managed by the management node to the lower level management node.
[0071] According to one embodiment, the control unit (220) can reuse an existing slicing entity among the slicing entities managed by the management node (20) as a second slicing entity (or an alternative slicing entity).
[0072] According to one embodiment, the control unit (220) may create a new slicing entity to be used as a second slicing entity (or alternative slicing entity) among the slicing entities managed by the management node (20).
[0073] According to one embodiment, the control unit (220) may determine that a reassignment event has occurred when a reassignment triggering condition associated with the first slicing entity or a lower-level management node to which the first slicing entity is assigned is satisfied.
[0074] According to one embodiment, the control unit (220) may transition the first slicing entity to an inoperable state prior to the reassignment of the second slicing entity if a specified reassignment triggering condition is met.
[0075] According to one embodiment, the control unit (220) may determine that a reassignment event has occurred when a reassignment triggering condition associated with the first slicing entity or a lower-level management node to which the first slicing entity is assigned is expected to be satisfied.
[0076] According to one embodiment, the control unit (220) may maintain both the first slicing entity and the second slicing entity in an operational state for a specified period of time when a specified reallocation triggering condition is expected to be met.
[0077] According to one embodiment, the control unit (220) may transmit a notification to the upper-level management node at any one of the stages of starting, proceeding, or completing the slicing entity reallocation procedure. For example, the control unit (220) may perform one or more of the following operations: transmitting a notification to the upper-level management node notifying the intention to reallocate a first slicing entity, transmitting a notification to the upper-level management node notifying the progress of the reallocation of a second slicing entity, and transmitting a notification to the upper-level management node notifying the completion of the reallocation of the second slicing entity. Accordingly, the upper-level management node may perform procedures (e.g., update procedures for operating inventory, databases, configurations, etc.) necessary to maintain integrity between the upper-level management node and the management node (20) based on the notification from the management node (20).
[0078] According to one embodiment, the management node (20) may include at least one of a communication service management function (CSMF), a network slice management function (NSMF), a network slice subnet management function (NSSMF), or a network function management function (NFMF).
[0079] According to one embodiment, the first slicing entity (or original slicing entity) and the second slicing entity (or alternative slicing entity) may each include at least one of a communication service instance (CSI), a network slice instance (NSI), a network slice subnet instance (NSSI), or a managed function instance (MFI).
[0080] FIG. 3 is a flowchart illustrating an operation method of a management node in a wireless communication system according to one embodiment.
[0081] According to one embodiment, a communication network of a wireless communication system may include various multi-level slicing entities (or network entities) and one or more management nodes that manage the slicing entities. In one embodiment, the operations of the method illustrated in FIG. 3 may be performed by the management node (20) of FIG. 2b. However, the present invention is not limited thereto. For example, the operations of the method illustrated in FIG. 3 may be performed by a combination of one or more devices or functions. The performing entity of the method illustrated in FIG. 3 is not limited to hardware components. It may be implemented by hardware, software, or a combination of hardware and software. For example, in some embodiments, the method may be performed by an application installed on the management node (20).
[0082] Referring to FIG. 3, the operation method of a management node in a wireless communication system may include operations 310, 320, and 330.
[0083] In operation 310, a management node (20) (e.g., any one of CSMF, NSMF, NSSMF, NFMF, or a combination thereof) may, in response to an allocation request from an upper-level management node, allocate a first slicing entity (or a first slicing entity) that satisfies specified requirements (e.g., ServiceProfile requirements, or SliceProfile requirements) for a network slice (or subnet) to a lower-level management node.
[0084] For example, the management node (20) may correspond to the lower level management system (21) of FIG. 4. The upper level management node that assigns the slicing entity to the management node (20) may correspond to the upper level management system (22) of FIG. 4. The lower level management node that is assigned the slicing entity from the management node (20) may correspond to a lower level management node or a constituent of the management node (20) compared to the management node (20).
[0085] At operation 320, the management node (20) can detect the occurrence of a reassignment event.
[0086] In one embodiment, the reassignment event may correspond to a reassignment triggering condition. For example, the reassignment triggering condition may include at least one of a failure of the first slicing entity, a failure of the lower-level management node, non-fulfillment of requirements attached (or stored) to the first slicing entity, occurrence of a reassignment trigger request, and degradation of the performance of the first slicing entity below a pre-specified threshold.
[0087] In one embodiment, the management node (20) may determine that a reassignment event has occurred if a reassignment triggering condition associated with the first slicing entity or a lower-level management node is met. If the reassignment triggering condition is met, the management node (20) may place the first slicing entity in an inoperable state prior to the reassignment of the second slicing entity.
[0088] In one embodiment, the management node (20) may determine that a reassignment event has occurred if a reassignment triggering condition associated with the first slicing entity or a lower-level management node is expected to be met. If the reassignment triggering condition is expected to be met, the management node (20) may maintain both the first slicing entity and the second slicing entity in an operational state for a specified period of time.
[0089] In operation 330, the management node (20) may, in response to the occurrence of a reassignment event detected through operation 320, reassign a second slicing entity (or an alternative slicing entity) that satisfies the specified requirements among the slicing entities (e.g., any one of CSIs, NSIs, NSSIs, MFIs, or a combination thereof) managed by the management node (20) to the lower level management node.
[0090] In one embodiment, the management node (20) may provide a procedure for reallocation of a slicing entity already assigned to the management node (20). The reallocation procedure may be a procedure for replacing, exchanging, or switching a first slicing entity (or original slicing entity) with a second slicing entity (or alternative slicing entity) that can satisfy the requirements raised for the first slicing entity. The reallocation procedure may be performed autonomously (or internally) by the management node (20).
[0091] According to one embodiment, the management node (20) can perform a reallocation procedure using a second slicing entity already assigned to it without having to separately request the upper-level management node to deallocate the first slicing entity and newly allocate another slicing entity for reallocation. In the case where the management node (20) autonomously (or internally) performs the reallocation procedure, additional support operations on the upper-level management node side, such as operations of the upper-level management node for deallocation and new allocation, may be unnecessary. In this case, the second slicing entity (or alternative slicing entity) to be reallocated and the existing first slicing entity (or original slicing entity) are both slicing entities belonging to the same management domain or of the same category managed by one management node (20), and can reliably satisfy the specified requirements for one network slice (or subnet).
[0092] According to one embodiment, the second slicing entity (or alternative slicing entity) to be reallocated by the management node (20) may be one of the slicing entities already allocated to the management node (20), which may correspond to an existing slicing entity already existing in the management node (20) or a new slicing entity newly created by the management node (20).
[0093] In one embodiment, the management node (20) can reuse an existing slicing entity among the slicing entities it manages as a second slicing entity (or an alternative slicing entity).
[0094] In one embodiment, the management node (20) may create a new slicing entity to be used as a second slicing entity (or alternative slicing entity) among the slicing entities it manages.
[0095] According to one embodiment, the slicing entity reallocation procedure of operation 330 may be autonomously (or internally) executed by a management node (20) (e.g., a lower-level management system (21) of FIG. 4) that manages a first slicing entity (or original slicing entity) given from a higher-level management node (e.g., a higher-level management system (22) of FIG. 4). In such a case, it may be unnecessary for the higher-level management node to support the reallocation procedure or for the higher-level management node to be aware that the reallocation procedure is being executed by a lower-level management node (20).
[0096] According to one embodiment, the slicing entity reallocation procedure of operation 330 may be performed using a utility operation triggered from an upper level management node via an exposed northbound interface (NBI) of the management node (20) (e.g., the lower level management system (21) of FIG. 4).
[0097] According to one embodiment, the slicing entity reassignment procedure of operation 330 may be explicitly invoked by a higher-level management node (or any other actor). For example, the reassignment procedure may be implemented to be exposed to the NBI of the management node (20) so that it can be explicitly invoked from the higher-level management node, or may be implemented to be available in internal APIs (application programming interfaces, not exposed as NBIs) that can be explicitly invoked by an administrator of the management node (20).
[0098] In one embodiment, the slicing entity reallocation method may correspond to at least one of a break-before-make technique for reallocating slicing entities, a pre-allocation technique for reallocating slicing entities, a late deprovisioning technique for reallocating slicing entities, or a combination thereof.
[0099] Hereinafter, with reference to FIGS. 4, 5a, 5b, 6a, 6b, 7a, 7b, 8, and 9, a slicing entity reallocation method using each technique will be exemplarily described. FIGS. 4, 5a, 5b, 6a, 6b, 7a, and 7b are examples of a slicing entity reallocation method using a pre-generation stop technique according to one embodiment. FIG. 8 is an example of a slicing entity reallocation method using a pre-allocation technique according to one embodiment. FIG. 9 is an example of a slicing entity reallocation method using a provisioning release delay technique according to one embodiment. At least some of the slicing entity reallocation operations according to the various embodiments described below may be performed in correspondence with each other or in combination with each other. In some embodiments, at least one of the illustrated operations may be omitted, the order of some operations may be changed, or other operations may be added. For example, operations marked as optional in the drawings described below may be omitted depending on the embodiment.
[0100] FIG. 4 is a flowchart illustrating a method for reallocating slicing entities by a break before make technique in a wireless communication system according to one embodiment.
[0101] In one embodiment, the pre-creation slicing interruption technique may mean a reassignment procedure in which a reassignment triggering condition is met before reassigning an alternative slicing entity (SE_alternative), thereby discontinuing the use of the original slicing entity (SE_original).
[0102] Referring to FIG. 4, a communication network of a wireless communication system may include multi-level management systems (21, 22, 23). A higher-level management system (22) (e.g., level N+1) may be a higher-level management node than a lower-level management system (21) (e.g., level N). A lower-level management system (21) (e.g., level N) may be a higher-level management node than an external lower-level management system (23) (e.g., level N-1, or a component of the lower-level management system (21)).
[0103] In one embodiment, a pre-create abort technique may be used to reallocate a slicing entity when the currently allocated slicing entity is no longer available due to an unexpected event (or a reallocation triggering event, e.g., as a result of a fault affecting the slicing entity).
[0104] For example, the external lower-level management system (23) may function as a fault management system, collecting data on the status of the slicing entities managed by the lower-level management system (21) and notifying the lower-level management system (21) of potential failures (e.g., based on predictions from current situation analysis) or failures that have already occurred. The fault management system may decide to trigger a reallocation to preserve the operational status of the affected slicing entities for various reasons. Accordingly, the external lower-level management system (23) may generate a reallocation event to trigger the reallocation of the slicing entities by the lower-level management system (21).
[0105] Referring to FIG. 4, an operation of reallocating a slicing entity by a pre-generation suspend technique according to one embodiment may include operations 401 and 402.
[0106] Operation 401 exemplifies operations prior to the execution of slicing entity reallocation, and may correspond to preconditions for the execution of said reallocation. Operation 401 may be for the allocation of the original slicing entity (SE_original). In some embodiments, operation 401 may be omitted or performed in a different manner.
[0107] Action 402 illustrates a slicing entity reallocation procedure using the pre-create interrupt technique. Action 402 may be for reallocating an alternative slicing entity (SE_alternative).
[0108] In one embodiment, when a specified reassignment triggering condition is detected to trigger a reassignment, the lower-level management system (21) may need to notify the upper-level management system (22) of its intent to perform a reassignment of the original slicing entity. The upper-level management system (22) may utilize this notification to potentially influence the execution of the reassignment procedure by the lower-level management system (21). For example, the upper-level management system (22) may approve or disapprove the execution of the reassignment procedure (potentially within a limited timeframe).
[0109] In one embodiment, the lower-level management system (21) may create a new slicing entity and designate it as an alternative slicing entity for the original slicing entity, or select another existing slicing entity and designate it as an alternative slicing entity for the original slicing entity. The alternative slicing entity designated by the lower-level management system (21) may satisfy the requirements assigned to the originally assigned original slicing entity (e.g., expressed as a SliceProfile for NSSI or as a ServiceProfile for NSI).
[0110] In one embodiment, as the reassignment procedure is performed, requirements (e.g., requirements specifications according to SliceProfile, ServiceProfile, or other representations) may be detached from the original slicing entity to which they were originally assigned and attached to an alternative slicing entity.
[0111] In one embodiment, the lower level management system (21) may, upon completion of the reassignment procedure, transmit a notification containing details of the reassignment procedure performed to the upper level management system (22) so that the inventory is updated.
[0112] The method of reallocating slicing entities by the pre-generation interruption technique and the detailed operations of operations 401 and 402 are described in more detail with reference to FIGS. 5a, 5b, 6a, 6b, 7a, and 7b.
[0113] FIG. 5A and FIG. 5B are flowcharts illustrating operations prior to reallocation execution when reallocating a slicing entity by a pre-generation stop technique in a wireless communication system according to one embodiment.
[0114] Referring to FIG. 5A, operation 401 illustrates operations prior to executing a slicing entity reallocation, and may be a prerequisite for executing the reallocation. Operation 401 may be for allocating a raw slicing entity.
[0115] Action 401 may include actions 510, 520, and 530.
[0116] At operation 510, the upper-level management system (22) may transmit a slicing entity allocation request to the lower-level management system (21) to satisfy specific requirements. The allocation request may include input requirements that the slicing entity to be allocated must satisfy.
[0117] In operation 520, the lower level management system (21) can execute the allocation procedure of the original slicing entity (SE_original).
[0118] Action 520 may include actions 521, 522, and 523.
[0119] At operation 521, the lower level management system (21) may determine whether to reuse an existing slicing entity or create a new slicing entity based on input requirements, monitored network environment, and / or operational policies.
[0120] Action 522 may include either an action of reusing an existing slicing entity or an action of creating a new slicing entity. The lower level management system (21) may selectively execute either an action of reusing an existing slicing entity that satisfies the input requirements as an original slicing entity (SE_original) or an action of creating a new slicing entity that satisfies the input requirements as an original slicing entity (SE_original) based on the determination of action 521.
[0121] In operation 523, the lower-level management system (21) may provide provisioning requirements for the original slicing entity (SE_original) to an external lower-level management system (23). Provisioning may mean allocating, arranging, and distributing system resources according to specific requirements for a service and preparing the system in advance for immediate use when needed. It may be necessary for both the lower-level management system (21) and the external lower-level management system (23) that serves as the basis for the lower-level management system (21) to perform management and configuration procedures for the allocation of the original slicing entity (SE_original).
[0122] Operation 530 may be an operation that returns a handle to the original slicing entity (SE_original). In operation 530, the lower-level management system (21) may send a notification to the upper-level management system (22) that requested the slicing entity allocation through operation 510, indicating the original slicing entity ID (SE_original ID). Single or multiple notifications may be sent. The notifications may be sent synchronously or asynchronously.
[0123] Referring to FIG. 5b, operation 402 may be an operation for detecting the occurrence of a slicing entity reallocation event.
[0124] Action 402 may include actions 540 and 550.
[0125] At operation 540, the lower-level management system (21) may detect the occurrence of a slicing entity reassignment event. For example, the lower-level management system (21) may determine that a reassignment event has occurred when the original slicing entity (SE_original) is rendered unusable and / or a reassignment triggering condition is met. Upon detecting the occurrence of the event, a slicing entity reassignment operation may be triggered.
[0126] Examples of reallocation triggering conditions that trigger slicing entity reallocation are described in more detail in FIGS. 6a and 6b below.
[0127] At step 550, the lower level management system (21) may transmit a notification to the upper level management system (22) informing of the intent to reassign the original slicing entity (SE_original) and details of the fulfilled reassignment triggering conditions (e.g., defects, non-fulfillment of requirements). In some embodiments, step 550 may be omitted.
[0128] FIGS. 6A and 6B are diagrams for explaining reassignment triggering conditions in a wireless communication system according to one embodiment.
[0129] Figure 6a illustrates exemplary operations of management systems (21, 22, 23) in a steady state when a reallocation triggering condition is not met (or when a reallocation event does not occur). The upper-level management system (22) can request the lower-level management system (21) to allocate a slicing entity that satisfies a specific requirement (external requirement) (operation 610). In response to the allocation request, the lower-level management system (21) can provide the original slicing entity (SE_original) (24) with the corresponding requirement (internal requirement) (operation 620), thereby enabling the necessary components (24_m, 24_n) to be configured. The lower level management system (21) can enable the resources of the external lower level management system (23_x, 23_z) to be used in response to the allocation request (operation 630), thereby allowing the corresponding components (24_m, 24_n) to be managed by the resources.
[0130] Figure 6b illustrates potential reallocation triggering conditions that trigger a slicing entity reallocation. If one or more of the reallocation triggering conditions are met (or a reallocation event occurs), a slicing entity reallocation operation may be triggered.
[0131] According to one embodiment, the reassignment triggering condition for triggering the slicing entity reassignment may be one or a combination of the conditions listed in a) to f) below, but is not limited thereto.
[0132] a) Complete or partial failure (drawing symbol 651) of the original slicing entity (SE_original) (24) or one of its components (24_m, 24_n);
[0133] b) Complete or partial failure of one of the lower level management systems (21) or the external lower level management systems (23_x, 23_z) (drawing symbol 652)
[0134] c) Result of not meeting the requirements attached to the original slicing entity (SE_original) (24) (drawing symbol 653): The above requirements may be those specified by the upper level slicing management system (22) in the allocation request or may be requirements modified later.
[0135] d) Result of not meeting the requirement attached to the original slicing entity (SE_original) (24) (drawing symbol 654): The requirement may be an internally defined requirement by a lower level management system (21) (e.g., system administrator or operator).
[0136] e) Explicit triggering of reassignment via APIs of a lower-level management system (21) (e.g., system administrator or operator) (reference numeral 655): said APIs may or may not be exposed for external use.
[0137] f) Periodic checks (reference numeral 656) indicating a performance degradation of the original slicing entity (SE_original) (24) or its components (24_m, 24_n): when a periodic load balancing check is performed to distribute (load balance) a set of requirements among a pool of managed slicing entities, when the amount of a set of requirements already attached (or connected) to a given original slicing entity (SE_original) reaches a threshold, when a new set of requirements has a higher priority than a set of requirements already attached (or connected) to the original slicing entity (SE_original) (24), requiring reassignment of a particular set of requirements to an alternative slicing entity, or when other conditions are met as a result of the check.
[0138] FIG. 7A and FIG. 7B are flowcharts illustrating reallocation execution operations when reallocating a slicing entity by a pre-generation interrupt technique in a wireless communication system according to one embodiment.
[0139] Referring to FIG. 7a, operation 402 may be an allocation procedure of an alternative slicing entity.
[0140] At operation 402, the lower level management system (21) may reallocate an alternative slicing entity (SE_alternative) that can replace the original slicing entity (SE_original) in satisfying the assigned requirement.
[0141] The logic for reassignment may involve either creating a new slicing entity or selecting an existing slicing entity. Creating a new slicing entity may be more advantageous than selecting an existing slicing entity in customizing specific requirements for the service. Selecting an existing slicing entity may reduce the reassignment time and improve resource utilization compared to creating a new slicing entity. The alternative slicing entity (SE_alternative) may satisfy the specific requirements originally assigned to the original slicing entity (SE_original). In some embodiments, the alternative slicing entity (SE_alternative) may satisfy more than the specific requirements originally assigned to the original slicing entity (SE_original) (e.g., in the case of intentional overbooking). In some embodiments, the original slicing entity (SE_original) may have multiple sets of requirements assigned to it. In such cases, the reassignment procedure may consider multiple sets of requirements assigned to the original slicing entity (SE_original) or all sets of requirements to be reassigned from the original slicing entity (SE_original) to the alternative slicing entity (SE_alternative).
[0142] Action 402 may include action 760. Action 760 may include actions 761, 762, 763, and 764.
[0143] At operation 761, the lower level management system (21) may determine whether to reuse an existing slicing entity or create a new slicing entity based on input requirements, monitored network environment, and / or operational policies.
[0144] In operation 762, the lower level management system (21) can optionally execute one of the following operations: reusing an existing slicing entity that satisfies the input requirements as an original slicing entity (SE_original) based on the decision of operation 761, or creating a new slicing entity that satisfies the input requirements as an original slicing entity (SE_original).
[0145] In operations 763 and 764, the lower level management system (21) may notify the upper level management system (22) of information regarding the progress of the reallocation of the alternative slicing entity (SE_alternative). For example, the information regarding the progress may include at least some of information regarding the reallocation of the alternative slicing entity (SE_alternative) with respect to the input requirements included in the original allocation request from the upper level management system (22), details regarding the creation of a new slicing entity or the reuse of an existing slicing entity for use as the alternative slicing entity (SE_alternative), information regarding one or more of the current status, current functionality, and current configuration of the alternative slicing entity (SE_alternative), other information regarding the alternative slicing entity (SE_alternative), or detailed procedure information regarding the reallocation being performed as part of the reallocation involving the alternative slicing entity (SE_alternative). In some embodiments, operations 763 and / or 764 may be omitted.
[0146] In operation 765, the lower level management system (21) may provide provisioning requirements for the original slicing entity (SE_original) to an external lower level management system (23). It may be necessary for both the lower level management system (21) and the external lower level management system (23) that serves as the basis for the lower level management system (21) to perform management and configuration procedures for the allocation of the original slicing entity (SE_original).
[0147] Referring to FIG. 7b, operation 402 of reallocating an alternative slicing entity (SE_alternative) may include operations 770, 780, and 790.
[0148] Operation 770 may be performed subsequent to operation 760 of FIG. 7A. In operation 770, the lower-level management system (21) may request deprovisioning from the original slicing entity (SE_original) to detach the requirements attached to the original slicing entity (SE_original). In some embodiments, operation 770 may be omitted or replaced with another operation. For example, the lower-level management system (21) may decide to continue attaching the previously attached requirements or their copies to the original slicing entity (SE_original) without deprovisioning.
[0149] At operation 780, the lower-level management system (21) may shut down (or terminate) the original slicing entity (SE_original). In some embodiments, operation 780 may be omitted or replaced with another operation. For example, the lower-level management system (21) may maintain (or preserve) the original slicing entity (SE_original) in an operational state. The original slicing entity (SE_original) may be kept operational by a reallocation operation policy so that it can be used for future reallocation. For example, if a reallocation is not triggered due to an error in the original slicing entity (SE_original), the original slicing entity (SE_original) may still be fully operational. If the reallocation is the result of a partial failure of the original slicing entity (SE_original), the original slicing entity (SE_original) may be partially operational. Termination of the original slicing entity (SE_original) may not be planned if the reallocation does not meet the specified requirements or is the result of an implicit user trigger.
[0150] At step 790, the lower-level management system (21) may transmit a notification to the upper-level management system (22) notifying that the slicing entity reallocation has been completed. For example, the notification may include at least some of the following: identification information of the original allocation request, identification information of the requirement, identification and details of the original slicing entity (SE_original), identification and details of the alternative slicing entity (SE_alternative), procedure status information, or information regarding potential changes to the requirement. Based on the notification, the upper-level management system (22) may perform necessary procedures (e.g., update procedures for operating inventory, databases, configurations, etc.) to maintain integrity between the upper-level management system (22) and the lower-level management system (21). In some embodiments, step 790 may be omitted.
[0151] FIG. 8 is a flowchart illustrating a method of reallocating slicing entities by a pre-allocation technique in a wireless communication system according to one embodiment.
[0152] The slicing entity reallocation method of FIG. 8 can be used when the need for reallocation is anticipated and / or when prior preparation is possible.
[0153] Referring to FIG. 8, an operation of reallocating a slicing entity by a pre-allocation technique according to one embodiment may include operations 801 and 802.
[0154] Operation 801 exemplifies operations prior to executing slicing entity reallocation, and may correspond to a prerequisite for executing the reallocation. Operation 801 may correspond to operation 401 of FIGS. 4 and 5A. Operation 801 may include operation 810 of allocating an original slicing entity (SE_original). In operation 810, the lower level management system (21) may allocate the original slicing entity (SE_original) by performing operations corresponding to operations 510, 520, and 530 of FIG. 5A.
[0155] Operation 802 illustrates a procedure for reallocating a slicing entity using a pre-allocation technique. Operation 802 may be for reallocating an alternative slicing entity (SE_alternative). Operation 802 may include operations 840 and 850.
[0156] At operation 840, the lower-level management system (21) may anticipate whether a reallocation triggering condition will be met (or whether a slicing entity reallocation event will occur). For example, the lower-level management system (21) may anticipate whether a reallocation triggering condition will be met when maintenance or termination of the infrastructure hosting the slicing entity is expected, when an expected key performance indicator (KPI) degrades due to an expected cause, when a non-total failure of the current slicing entity is detected, when a pre-created backup slicing entity pool is ready to be used as a target for reallocation, or when a combination thereof occurs.
[0157] If a reassignment triggering condition is expected to be met (or a slicing entity reassignment event is expected to occur), the lower level management system (21) may proceed to operation 850 to reassign the slicing entity. In operation 850, the lower level management system (21) may reassign the alternative slicing entity (SE_alternative) by performing operations corresponding to operation 550 of FIG. 5b, operation 760 of FIG. 7a, operation 770, operation 780, and operation 790 of FIG. 7b.
[0158] FIG. 9 is a flowchart illustrating a method for reallocating a slicing entity by a late deprovisioning technique in a wireless communication system according to one embodiment.
[0159] Referring to FIG. 9, an operation of reallocating a slicing entity by a provisioning de-provisioning delay technique according to one embodiment may include operations 901 and 902.
[0160] Action 901 exemplifies actions prior to executing slicing entity reallocation, and may be a prerequisite for executing the reallocation. Action 901 may correspond to action 401 of FIGS. 4 and 5a.
[0161] Operation 901 may include operation 910 of allocating an original slicing entity (SE_original). In operation 910, the lower level management system (21) may allocate the original slicing entity (SE_original) by performing operations corresponding to operations 510, 520, and 530 of FIG. 5A.
[0162] Operation 902 illustrates a procedure for reassigning a slicing entity using a provisioning delay technique. Operation 902 may be for reassigning an alternative slicing entity (SE_alternative). Operation 902 may include operations 940, 950, 980, 990, and 1010.
[0163] At operation 940, the lower-level management system (21) may anticipate whether a reallocation triggering condition will be met (or whether a slicing entity reallocation event will occur). For example, the lower-level management system (21) may anticipate whether a reallocation triggering condition will be met when maintenance or termination of the infrastructure hosting the slicing entity is expected, when an expected key performance indicator (KPI) degrades due to an expected cause, when a non-total failure of the current slicing entity is detected, when a pre-created backup slicing entity pool is ready to be used as a target for reallocation, or when a combination thereof occurs.
[0164] If the reallocation triggering condition is expected to be met, the lower level management system (21) may proceed to operation 950 to reallocate the slicing entity.
[0165] Action 950 may include actions 951 and 952.
[0166] At operation 951, the lower level management system (21) can reallocate the alternative slicing entity (SE_alternative) by performing operations corresponding to operation 550 of FIG. 5b, operation 760 of FIG. 7a, operation 770, operation 780 and operation 790 of FIG. 7b.
[0167] In operation 952, the lower level management system (21) may maintain both the original slicing entity (SE_original) and the alternative slicing entity (SE_alternative) in an operational state for a designated (or given) period of time. In some embodiments, the lower level management system (21) may also perform load balancing between the original slicing entity (SE_original) and the alternative slicing entity (SE_alternative).
[0168] At operation 960, the lower level management system (21) may request deprovisioning from the original slicing entity (SE_original) to detach requirements attached to the original slicing entity (SE_original). At operation 970, the lower level management system (21) may shut down (or terminate) the original slicing entity (SE_original). At operation 980, the lower level management system (21) may send a notification to the upper level management system (22) informing that the slicing entity reallocation is complete. Operations 960, 970, and 980 may correspond to operations 770, 780, and 790 of FIG. 7B, respectively. In some embodiments, one or more of operations 960, 970, or 980 may be omitted or replaced with other operations.
[0169] When reallocating slicing entities using a provisioning delay technique, as illustrated in the embodiment of FIG. 9, specific requirements required for servicing a network slice can be allocated to both the original slicing entity (SE_original) and the alternative slicing entity (SE_alternative) for a certain period of time. This eliminates or reduces downtime while the slicing entity is being changed through the reallocation procedure.
[0170] A method of operating a management node according to various embodiments may be a method of operating a management node in a wireless communication system having a network slicing environment. The method may include, in response to an allocation request from a higher-level management node, allocating a first slicing entity that satisfies specified requirements for a network slice to a lower-level management node, detecting an occurrence of a reassignment event, and in response to the occurrence of the reassignment event, reallocating a second slicing entity, among slicing entities managed by the management node, that satisfies the specified requirements to the lower-level management node.
[0171] According to various embodiments, the act of reallocating the second slicing entity may include an act of reusing an existing slicing entity among the slicing entities managed by the management node as the second slicing entity.
[0172] According to various embodiments, the act of reallocating the second slicing entity may include an act of creating a new slicing entity to be used as the second slicing entity among the slicing entities managed by the management node.
[0173] According to various embodiments, the operation of detecting the occurrence of the reassignment event may include an operation of determining that the reassignment event has occurred when a reassignment triggering condition associated with the first slicing entity or the lower-level management node is satisfied.
[0174] According to various embodiments, the method may further include an operation of transitioning the first slicing entity to an inoperable state prior to the reallocation of the second slicing entity if the reallocation triggering condition is met.
[0175] According to various embodiments, the operation of detecting the occurrence of the reassignment event may include an operation of determining that the reassignment event has occurred when a reassignment triggering condition associated with the first slicing entity or the lower-level management node is expected to be satisfied.
[0176] According to various embodiments, the method may further include maintaining both the first slicing entity and the second slicing entity in an operational state for a specified period of time when the reallocation triggering condition is expected to be met.
[0177] According to various embodiments, the method may further include one or more of the following operations: transmitting a notification to the upper level management node notifying an intention to reassign the first slicing entity, transmitting a notification to the upper level management node notifying a progress status of reassignment of the second slicing entity, and transmitting a notification to the upper level management node notifying completion of reassignment of the second slicing entity.
[0178] According to various embodiments, the management node may include at least one of a communication service management function (CSMF), a network slice management function (NSMF), a network slice subnet management function (NSSMF), or a network function management function (NFMF).
[0179] According to various embodiments, the first slicing entity and the second slicing entity may each include at least one of a communication service instance (CSI), a network slice instance (NSI), a network slice subnet instance (NSSI), or a managed function instance (MFI).
[0180] A management node according to various embodiments (e.g., a management node (20) of FIG. 2b or a lower-level management system (21) of FIG. 4) may include a transceiver (e.g., a communication unit (210) of FIG. 2b), a memory storing one or more computer programs (e.g., a storage unit (230) of FIG. 2b), and one or more processors (e.g., a control unit (220) of FIG. 2b) communicatively connected to the transceiver and the memory. The one or more computer programs may include computer-executable instructions that, when executed by the one or more processors, cause the management node, in response to an allocation request from a higher-level management node, to allocate a first slicing entity that satisfies specified requirements for a network slice to a lower-level management node, to detect an occurrence of a reassignment event, and in response to an occurrence of the reassignment event, to reallocate a second slicing entity among the slicing entities managed by the management node that satisfies the specified requirements to the lower-level management node.
[0181] According to various embodiments, the one or more computer programs may include computer-executable instructions that, when executed by the one or more processors, cause the management node to reuse an existing slicing entity among the slicing entities managed by the management node as the second slicing entity.
[0182] According to various embodiments, the one or more computer programs may include computer-executable instructions that, when executed by the one or more processors, cause the management node to create a new slicing entity to be used as the second slicing entity among the slicing entities managed by the management node.
[0183] According to various embodiments, the one or more computer programs may include computer-executable instructions that, when executed by the one or more processors, cause the management node to determine that the reassignment event has occurred when a reassignment triggering condition associated with the first slicing entity or the lower-level management node is met.
[0184] According to various embodiments, the one or more computer programs may include computer-executable instructions that, when executed by the one or more processors, cause the management node to place the first slicing entity into an inoperable state prior to the reallocation of the second slicing entity if the reallocation triggering condition is met.
[0185] According to various embodiments, the one or more computer programs may include computer-executable instructions that, when executed by the one or more processors, cause the management node to determine that the reassignment event has occurred when a reassignment triggering condition associated with the first slicing entity or the lower-level management node is expected to be satisfied.
[0186] According to various embodiments, the one or more computer programs may include computer-executable instructions that, when executed by the one or more processors, cause the management node to maintain both the first slicing entity and the second slicing entity in an operational state for a specified period of time when the specified reallocation triggering condition is expected to be met.
[0187] According to various embodiments, the one or more computer programs may include computer-executable instructions that, when executed by the one or more processors, cause the management node to perform one or more of the following operations: transmitting a notification to the upper level management node notifying an intention to reassign the first slicing entity, transmitting a notification to the upper level management node notifying a progress status of the reassignment of the second slicing entity, and transmitting a notification to the upper level management node notifying the completion of the reassignment of the second slicing entity.
[0188] According to various embodiments, the management node may include at least one of a communication service management function (CSMF), a network slice management function (NSMF), a network slice subnet management function (NSSMF), or a network function management function (NFMF).
[0189] According to various embodiments, the first slicing entity and the second slicing entity may each include at least one of a communication service instance (CSI), a network slice instance (NSI), a network slice subnet instance (NSSI), or a managed function instance (MFI).
[0190] According to various embodiments, the reassignment event may correspond to a reassignment triggering condition associated with the first slicing entity or the lower-level management node. The reassignment triggering condition may include at least one of a failure of the first slicing entity, a failure of the lower-level management node, non-fulfillment of requirements attached (or stored) to the first slicing entity, occurrence of a reassignment trigger request, and degradation of the performance of the first slicing entity below a pre-specified threshold.
[0191] According to various embodiments, one or more non-transitory computer-readable storage media may be provided. The non-transitory storage medium may store one or more computer programs including computer-executable instructions that, when executed by one or more processors of a management node (e.g., a management node (20) of FIG. 2b or a lower-level management system (21) of FIG. 4), cause the management node to perform, in response to an allocation request from a higher-level management node, an operation of allocating a first slicing entity that satisfies specified requirements for a network slice to a lower-level management node, an operation of detecting an occurrence of a reassignment event, and an operation of reallocating a second slicing entity among slicing entities managed by the management node that satisfies the specified requirements to the lower-level management node in response to an occurrence of the reassignment event.
[0192] According to various embodiments, the non-transitory storage medium may store one or more computer programs including computer-executable instructions that, when executed by the one or more processors of the management node, cause the management node to perform one or more of the following operations: transmitting a notification to the upper level management node notifying an intention to reassign the first slicing entity, transmitting a notification to the upper level management node notifying a progress status of the reassignment of the second slicing entity, and transmitting a notification to the upper level management node notifying the completion of the reassignment of the second slicing entity.
[0193] According to various embodiments of the present disclosure, even if a problem situation requiring reallocation occurs in a network slice, the quality of service (QoS) and quality of experience (QoE) expectations of users for services (e.g., business applications) provided through the network slice can be met by performing an autonomous reallocation procedure.
[0194] According to various embodiments of the present disclosure, management functions can be enhanced to provide greater reliability in maintaining service level agreement (SLA) requirements and service level specification (SLS) requirements.
[0195] According to various embodiments of the present disclosure, by providing self-healing capabilities through a reassignment procedure to lower-level management nodes of a network slice, continuous service can be guaranteed without interruption to users of the network slice.
Claims
1. In a method of operating a management node in a wireless communication system having a network slicing environment, In response to an allocation request from a higher-level management node, the act of allocating a first slicing entity that satisfies specified requirements for a network slice to a lower-level management node; Action to detect the occurrence of a reassignment event; and A method comprising, in response to the occurrence of the above reassignment event, an action of reassigning, to the lower level management node, a second slicing entity among the slicing entities managed by the management node that satisfies the specified requirement.
2. In claim 1, The action of reallocating the above second slicing entity is: A method comprising an action of reusing an existing slicing entity among the slicing entities managed by the management node as the second slicing entity.
3. In claim 1, The action of reallocating the above second slicing entity is: A method comprising an action of creating a new slicing entity to be used as the second slicing entity among the slicing entities managed by the management node.
4. In claim 1, The action to detect the occurrence of the above reassignment event is: A method comprising an action for determining that a reassignment event has occurred when a reassignment triggering condition associated with the first slicing entity or the lower level management node is satisfied.
5. In claim 4, A method further comprising an action of putting the first slicing entity into an inoperable state before the reassignment of the second slicing entity if the reassignment triggering condition is met.
6. In claim 1, The action to detect the occurrence of the above reassignment event is: A method comprising an action for determining that a reassignment event has occurred when a reassignment triggering condition associated with the first slicing entity or the lower level management node is expected to be satisfied.
7. In claim 6, A method further comprising: maintaining both the first slicing entity and the second slicing entity in an operational state for a specified period of time if the reassignment triggering condition is expected to be satisfied.
8. In claim 1, An action of sending a notification to the upper level management node notifying the intention to reassign the first slicing entity; An action of sending a notification to the upper level management node informing the progress of the reallocation of the second slicing entity; and A method further comprising one or more of the actions of sending a notification to the upper level management node notifying completion of the reallocation of the second slicing entity.
9. In claim 1, The above management node, A method including at least one of a communication service management function (CSMF), a network slice management function (NSMF), a network slice subnet management function (NSSMF), or a network function management function (NFMF).
10. In claim 1, The first slicing entity and the second slicing entity are, respectively, A method comprising at least one of a communication service instance (CSI), a network slice instance (NSI), a network slice subnet instance (NSSI), or a managed function instance (MFI).
11. In a management node in a wireless communication system having a network slicing environment, transceiver; a memory storing one or more computer programs; and comprising one or more processors communicatively connected to the transceiver and memory; The one or more computer programs, when executed by the one or more processors, cause the management node to: In response to an allocation request from a higher-level management node, allocates a first slicing entity that satisfies the specified requirements for a network slice to a lower-level management node, Detect the occurrence of a reassignment event, A management node comprising computer-executable instructions that, in response to the occurrence of the above reassignment event, cause the lower-level management node to reassign a second slicing entity among the slicing entities managed by the management node that satisfies the above specified requirements.
12. In claim 11, The one or more computer programs, when executed by the one or more processors, cause the management node to: A management node comprising computer-readable instructions for causing an existing slicing entity among the slicing entities managed by the management node to be reused as the second slicing entity.
13. In claim 11, The one or more computer programs, when executed by the one or more processors, cause the management node to: A management node comprising computer-readable instructions that cause the management node to create a new slicing entity to be used as the second slicing entity among the slicing entities managed by the management node.
14. In claim 11, The one or more computer programs, when executed by the one or more processors, cause the management node to: A management node comprising computer-readable instructions that cause a reassignment event to be determined to have occurred when a reassignment triggering condition associated with said first slicing entity or said lower-level management node is met.
15. In claim 14, The one or more computer programs, when executed by the one or more processors, cause the management node to: A management node comprising computer-readable instructions that cause the first slicing entity to be placed in an inoperable state prior to the reassignment of the second slicing entity if the reassignment triggering condition is met.
Citation Information
Patent Citations
Surface protecting adhesive film for semiconductor wafer
KR1020220107592A
Partial replaceable road reflector
KR102178280B1
Lifecycle management for NSI and csi
US20190052579A1
Network slice provisioning and operation
US20190223055A1
Policy driven network slice orchestration
WO2022269045A1
