Management node in wireless communication system with network slicing environment and method of operation thereof

Abstract

A management node in a wireless communication system having a network slicing environment and a method of operation thereof are disclosed. The management node may receive an activation request for the shared lower-level entity according to activation of one or more of the plurality of higher-level entities sharing the lower-level entity, and activate the shared lower-level entity for the activated one or more higher-level entities in response to the received activation request.

Description

TECHNICAL FIELD

[0001] The disclosure relates to a management node in a wireless communication system and an operation method thereof, for example, to a management node for managing network entities in a wireless communication system with a network slicing environment and an operation method thereof. BACKGROUND

[0002] The fifth generation (5G) mobile communication technology defines wide frequency bands in order to allow high transmission rates and new services, and can be implemented not only in frequency bands below 6 GHz, such as 3.5 GHz, but also in extremely high frequency bands (above 6 GHz), such as 28 GHz and 39 GHz, which are referred to as millimeter wave (mmWave). In addition, the sixth generation (6G) mobile communication technology, which is referred to as a beyond 5G (B5G) system, is considering the implementation in terahertz (THz) bands (e.g., in 95 GHz to 3 THz bands) to achieve transmission rates fifty times faster than those of 5G mobile communication technology and ultra-low latency reduced to one-tenth.

[0003] In the initial stage of 5G mobile communication technology, in order to support services and to meet the performance requirements of enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), and massive machine-type communication (mMTC), the following have been standardized: beamforming and massive multiple input multiple output (MIMO) for mitigating radio wave path loss and increasing radio wave transmission distance in an extremely high frequency band; support for various parameter sets (operating multiple subcarrier intervals, etc.) for efficiently utilizing an extremely high frequency resource and time slot format dynamic operation; initial access techniques for supporting multi-beam transmission and wideband; definition and operation of bandwidth parts (BWPs); new channel coding methods such as low-density parity check (LDPC) codes for large-capacity data transmission and polar codes for more reliable transmission of control information; L2 pre-processing; and network slicing for providing a dedicated network customized for a specific service.

[0004] Currently, discussions are underway regarding improvements and performance enhancements to the initial 5G mobile communication technology performance by considering services supported by 5G mobile communication technology, and physical layer standardization is being conducted on technologies such as V2X (vehicle-to-everything) for assisting in driving determination of autonomous vehicles based on location and status information transmitted by vehicles and enhancing user convenience; NR-U (new radio-unlicensed) aiming to meet various regulatory requirements for system operation in unlicensed bands; NR user equipment (UE) power saving; non-terrestrial networks (NTN) as UE-satellite direct communication for guaranteeing coverage in areas where communication with terrestrial networks is not feasible; and positioning.

[0005] There is also standardization in the field of radio interface architecture / protocol for technologies such as Industrial Internet of Things (IoT) for supporting new services through interworking and convergence with other industries, Integrated Access and Backhaul (IAB) for providing a node that expands a network service area by supporting a wireless backhaul link and an access link in an integrated manner, mobility enhancement including conditional handover and Dual Active Protocol Stack (DAPS) handover, and two-step random access (2-step RACH for NR) for simplifying a random access procedure, and also in the field of system architecture / service for a 5G baseline architecture (e.g., service-based architecture, service-based interface) for combining Network Function Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) for receiving services based on UE location.

[0006] If such a 5G mobile communication system is commercialized, connected devices that are increasing exponentially will be connected to a communication network, and thus it is expected that there will be a need for enhancement of functions and performance enhancement of the 5G mobile communication system and integrated operation of connected devices. For this purpose, new research will be conducted for Extended Reality (XR) for efficiently supporting Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR); 5G performance improvement and complexity reduction by utilizing Artificial Intelligence (AI) and Machine Learning (ML); AI service support; metaverse service support; and drone communication.

[0007] In addition, such development of the 5G mobile communication system will serve as a basis for not only developing new waveforms for securing coverage in a terahertz band of 6G mobile communication technology, Full Dimensional MIMO (FD-MIMO), multiple antenna transmission technologies such as array antennas and massive antennas, metamaterial-based lenses and antennas for improving terahertz band signal coverage, higher dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM), and Reconfigurable Intelligent Surface (RIS), but also developing Full Duplex technology for improving frequency efficiency and mobile communication systems of 6G mobile communication technology, AI-based communication technology for implementing system optimization by utilizing satellites and AI from the design stage and embedding end-to-end AI support functions, and next-generation distributed computing technology for implementing complex services that exceed the limits of UE processing capacity by utilizing super-high-performance communication and computing resources.

[0008] In a wireless communication system such as a 5G mobile communication system, a network slice can be a network architecture capable of multiplexing virtualized logical networks and independent logical networks on the same physical network infrastructure. Each network slice (or subnet) can represent an isolated end-to-end network customized to meet various requirements requested by a specific application. Through network slicing technology, multiple virtualized logical networks can exist on one physical network. SUMMARY

[0009] SOLUTION TO PROBLEM Embodiments of the disclosure can provide an operation method of a management node. The method according to an embodiment can be a method of operating a management node in a wireless communication system having a network slicing environment. The method can include receiving an activation request of a lower-level entity shared as one or more higher-level entities of a plurality of higher-level entities sharing the lower-level entity managed by the management node are activated; and in response to the activation request, activating the lower-level entity shared for the activated one or more higher-level entities.

[0010] Embodiments of the disclosure can provide a management node. The management node according to an embodiment can be a management node in a wireless communication system having a network slicing environment. The management node can include a transceiver; and at least one processor connected to the transceiver. The at least one processor can be configured to receive an activation request of a lower-level entity shared as one or more higher-level entities of a plurality of higher-level entities sharing the lower-level entity managed by the management node are activated; and in response to the activation request, activate the lower-level entity shared for the activated one or more higher-level entities. BRIEF DESCRIPTION OF DRAWINGS

[0011] The above and other aspects, features, and advantages of certain embodiments of the disclosure will be more apparent from the following detailed description taken in conjunction with the accompanying drawings, in which:

[0012] Figure 1 A communication network including a network entity in a wireless communication system according to various embodiments is illustrated.

[0013] Figure 2a FIG. 1 is a diagram illustrating a sharing of a network slice instance (NSI) and a network slice subnet instance (NSSI) in a wireless communication system according to an embodiment.

[0014] Figure 2b A configuration of a management node in a wireless communication system according to an embodiment is illustrated.

[0015] Figure 3 FIG. 4 is a flowchart illustrating an operation method of a management node in a wireless communication system according to an embodiment.

[0016] Figure 4a and Figure 4b is a diagram for illustrating a selective activation operation of a shared entity in a wireless communication system according to an embodiment.

[0017] Figure 5a and Figure 5b is a diagram for illustrating a selective deactivation operation of a shared entity in a wireless communication system according to an embodiment.

[0018] Figure 6a and Figure 6b is a flowchart illustrating a selective activation operation of one NSSI shared by a plurality of NSIs in a wireless communication system according to an embodiment.

[0019] Figure 7a is a flowchart illustrating a selective activation operation of a shared entity in a wireless communication system according to an embodiment, in a case where higher-level entities are managed by different management systems.

[0020] Figure 7b is a flowchart illustrating a selective activation operation of a shared entity in a wireless communication system according to an embodiment, in a case where multi-level entities are managed by a single management system.

[0021] Figure 8a is a flowchart illustrating a selective activation operation of a managed function (MF) by a handover scheme supported by an element management system (EMS) in a wireless communication system according to an embodiment.

[0022] Figure 8b is a flowchart illustrating a selective deactivation operation of a managed function (MF) by a handover scheme supported by an element management system (EMS) in a wireless communication system according to an embodiment.

[0023] Figure 9a is a flowchart illustrating a selective activation operation of a managed function (MF) by a completing configuration scheme in a wireless communication system according to an embodiment.

[0024] Figure 9b is a flowchart illustrating a selective deactivation operation of a managed function (MF) by a completing configuration scheme in a wireless communication system according to an embodiment.

[0025] Figure 10ais a flowchart illustrating a selective activation operation of NSSI or MF by a network communication blocking or unblocking scheme in a wireless communication system according to an embodiment.

[0026] Figure 10b is a flowchart illustrating a selective deactivation operation of NSSI or MF by a network communication blocking or unblocking scheme in a wireless communication system according to an embodiment.

[0027] Figure 11a and Figure 11b is a diagram for illustrating a selective deactivation operation of NSSI by a consensus scheme of a network slice management function (NSMF) in a wireless communication system according to an embodiment. DETAILED DESCRIPTION

[0028] It should be understood that various embodiments of the present disclosure and the terms used herein are not intended to limit the technical features disclosed in the present disclosure to particular embodiments, but include various modifications, equivalents, or alternatives of the corresponding embodiments.

[0029] The method according to various embodiments of the present disclosure can be implemented in software, hardware, or a combination of hardware and software. In a software implementation, a computer-readable storage medium storing one or more programs (software modules) can be provided. The one or more programs stored in the computer-readable storage medium are configured to be executed by one or more processors of an electronic device. The one or more programs include instructions for controlling the electronic device to execute the methods according to the embodiments described in the claims or the specification of the present disclosure.

[0030] Such a program (software module, software) can be stored to a random access memory, a non-volatile memory (including a flash memory), a read only memory (ROM), an electrically erasable programmable ROM (EEPROM), a magnetic disc storage device, a compact disc (CD)-ROM, a digital versatile disc (DVD), or other optical storage devices, and a magnetic cassette. Alternatively, it can be stored to a memory that partially or wholly combines them. In addition, a plurality of memories can be included.

[0031] In addition, the program can be stored in an attachable storage device accessible via a communication network such as the Internet, an intranet, a local area network (LAN), a wide area network (WAN), or a storage area network (SAN), or a communication network combining them. Such a storage device can access a device performing embodiments of the present disclosure through an external port. In addition, a separate storage device on the communication network can access a device performing embodiments of the present disclosure.

[0032] In various embodiments of the disclosure, components are expressed in singular or plural forms. However, the singular or plural expression is appropriately selected according to the situation presented for convenience of explanation, and the disclosure is not limited to a single component or multiple components, and a component expressed in plural form can be configured as a single component, and a component expressed in singular form can be configured as multiple components.

[0033] The terms indicating a signal, a term indicating a channel, a term indicating control information, a term indicating a network entity, and a term indicating a component of a device used in the following description are for the purpose of explanation. Accordingly, the disclosure is not limited to the terms to be described, and other terms having technically identical or similar meanings can be used.

[0034] In addition, the disclosure describes various embodiments by using terms used in some communication standards (for example, the third generation partnership project (3GPP)) only as examples for explanation. The various embodiments of the disclosure can be easily modified and applied to other communication systems.

[0035] Hereinafter, embodiments of the disclosure will be described in detail so that those skilled in the art can easily practice them in the technical field of the disclosure with reference to the accompanying drawings. However, the disclosure can be implemented in many different forms and is not limited to the embodiments described herein. With regard to the description of the drawings, the same or similar reference numerals can be used for the same or similar components. In addition, in the drawings and the related description, descriptions of well-known functions and configurations can be omitted for clarity and conciseness.

[0036] Figure 1 A communication network including a network entity in a wireless communication system according to various embodiments is illustrated.

[0037] Reference Figure 1 The 5G mobile communication network of the wireless communication system 100 can include a user equipment (UE) 110, a radio access network (RAN) 120, and a core network (CN).

[0038] The CN is a network that manages the entire system and can control the RAN 120 and process data and control signals transmitted and received by the UE 110 through the RAN 120. The CN can perform various functions such as user plane and control plane control, mobility handling, subscriber information management, charging, and interworking with other systems (for example, a long term evolution (LTE) system). To perform the various functions described above, the CN can include a plurality of entities having different network functions (NFs) that are functionally separated.

[0039] The CN can include network functions such as an Access and Mobility Management Function (AMF) 150 that provides mobility management functions for UEs, a Session Management Function (SMF) 160 that provides session management functions, a User Plane Function (UPF) 170 that communicates data, a Policy Control Function (PCF) 180 that provides policy and control functions, a Unified Data Management (UDM) 153 that provides data management functions such as subscriber data or policy control data, a Network Slice Selection Function (NSSF) 190 that operates and / or manages network slices, or a Unified Data Repository (UDR) that stores data for various network functions. Although not depicted in FIG. 1, the CN can also include a Communication Service Management Function (CSMF), a Network Slice Management Function (NSMF), and a Network Slice Subnet Management Function (NSSMF) for creating network slices and identifying user services. Figure 1

[0040] Referring to Figure 1 , the UE 110 can perform communication through a wireless channel constructed with a base station (e.g., an evolved Node B (eNB), a next-generation Node B (gNB)) (i.e., through an access network). In some embodiments, the UE 110 is a device used by a user and can be configured to provide a user interface (UI). For example, the UE 110 can be a terminal installed in a vehicle for driving. In some other embodiments, the UE 110 can be a device performing machine type communication (MTC) that operates without user involvement or an autonomous vehicle. In addition to electronic devices, a UE can also be referred to as a "terminal," a "vehicle terminal," a "UE," a "mobile station," a "subscriber station," a "remote terminal," a "wireless terminal," a "user equipment," or other terms having equivalent technical meanings. As a terminal, a customer premises equipment (CPE) or a dongle type terminal can be used in addition to a UE. The CPE is connected to an NG-RAN node like a UE and can provide a network for other communication devices (e.g., a laptop computer).

[0041] Referring to Figure 1 , the AMF 150 provides functions for access and mobility management based on the UE 110, and one UE 110 can be basically connected to one AMF 150. Specifically, the AMF 150 can perform at least one function of signaling between core network nodes for mobility of the 3GPP access network, an interface (N2 interface) between wireless access networks (e.g., the RAN 120), non-access stratum (NAS) signaling with the UE 110, identifying the SMF 160, and transferring session management (SM) messages between the UE 110 and the SMF 160. Some or all of the functions of the AMF 150 can be supported in a single instance of one AMF 150. ​

[0042] Reference Figure 1 The SMF 160 provides session management functionality, and if the UE 110 has multiple sessions, these can be managed by different SMFs 160 respectively. Specifically, the SMF 160 can perform at least one of session management (e.g., session establishment, modification, and release, including tunnel maintenance between UPF 170 and access network node), user plane (UP) function selection and control, traffic steering configuration to route traffic flow from a UPF 170 to the proper destination, termination of SM parts of NAS messages, downlink data notification (DDN), and initiator of AN specific SM information (e.g., delivered by AMF 150 to access network over N2 interface). Some or all of the functions of the SMF 160 can be supported in a single instance of the SMF 160.

[0043] In 3GPP systems, a concept link that interconnects network functions (NFs) within a 5G system can be referred to as a reference point. A reference point can be referred to as an interface. The following shows the reference points included in the 5G system architecture represented in Figures 1 to 11b - N1: Reference point between UE 110 and AMF 150 - N2: Reference point between (R)AN 120 and AMF 150 - N3: Reference point between (R)AN 120 and UPF 170 - N4: Reference point between SMF 160 and UPF 170 - N5: Reference point between PCF 180 and AF 130 - N6: Reference point between UPF 170 and DN 140 - N7: Reference point between SMF 160 and PCF 180 - N8: Reference point between UDM 153 and AMF 150 - N9: Reference point between two core UPFs 170 - N10: Reference point between UDM 153 and SMF 160 - N11: Reference point between AMF 150 and SMF 160 - N12: Reference point between AMF 150 and authentication server function (AUSF) 151 - N13: Reference point between UDM 153 and AUSF 151 - N14: Reference point between two AMFs 150​ - N15: Reference point between PCF 180 and AMF 150 in a non-roaming scenario; reference point between PCF 180 and AMF 150 within a visited network in a roaming scenario - N22: Reference point between NSSF 190 and AMF 150.

[0044] Figure 2a FIG. 1 is a diagram illustrating a network slice instance (NSI) and network slice subnet instance (NSSI) sharing in a wireless communication system according to an embodiment.

[0045] According to various embodiments, by applying a network slicing technology to a wireless communication system (e.g., a 5G mobile communication network) including a RAN 120 and a CN 200, Figure 1 multiple logical networks can be spawned on one shared infrastructure, and each logical network can be endowed with unique characteristics for specific service requirements. In a network slicing environment, slice entities, which are constituent elements of a network slice, can be shared with each other. Instead of allocating dedicated managed entities for each new network, a single instance of a managed entity can be used simultaneously by multiple logical networks that are network slices.

[0046] According to various embodiments, in a wireless communication system having a network slicing environment, slice entities or managed entities (e.g., NSSIs, NSIs, or managed functions (MFs)) can have sharing. For example, one NSSI (e.g., any one of NSSI 1, NSSI 2, and NSSI 3 shown in FIG. 1) can be shared among multiple NSIs (e.g., at least a part of NSI A, NSI B, and NSI C shown in FIG. 1) or other nested NSSIs. Figure 2a Figure 2a One NSI can be shared among multiple communication service instances (CSIs). One MF can be shared among multiple NSSIs.

[0047] According to an embodiment, an MF can represent a logical application that is executed inside a virtual network function (VNF) / physical network function (PNF) / container network function (CNF). An MF can perform a predefined set of functions and communicate with each other through a standard interface called a reference point. Creating a network slice can mean spawning a new instance of a slice-specific MF and reusing an MF that can be shared among multiple slices. For example, a dedicated MF can correspond to an SMF 160 or a UPF 170 shown in FIG. 1. For example, a shared MF can correspond to an AMF 150 shown in FIG. 1. Figure 1 Figure 1 ​​Any of the UDM 153, AMF 150, NSSF 190, or network repository function (NRF) (not depicted).

[0048] Figure 2b A configuration of a management node in a wireless communication system according to an embodiment is illustrated.

[0049] According to an embodiment, the management node 201 can be a device or function for managing one or more slice entities. The management node 201 can be referred to as a management entity, a management system, or a management function. In an embodiment, the management node 201 can include a device or function for managing lower-level entities among multi-level entities (higher-level entities and lower-level entities) included in a wireless communication system. For example, the management node 201 can include a function or device corresponding to at least one of a CSMF, an NSMF, and a NSSMF. Hereinafter, a term such as "... unit" or "... er" indicates a unit for processing at least one function or operation, and can be implemented using hardware, software, or a combination of hardware and software.

[0050] Reference Figure 2b According to an embodiment, the management node 201 can include a communication unit (e.g., including a communication circuit) 210 and a control unit (e.g., including a processing / control circuit) 220. In an embodiment, the management node 201 can further include a storage unit 230.

[0051] In an embodiment, the communication unit 210 can provide an interface for communication with other devices in a network. That is, the communication unit 210 can convert a bit string transmitted from the management node 210 to other devices (or external electronic devices) into a physical signal, and convert a physical signal received from other devices into a bit string. In an embodiment, the communication unit 210 can transmit and receive a signal. Accordingly, the communication unit 210 can be referred to as a modem, a transmitter, a receiver, or a transceiver. The communication unit 210 can support the management node 210 to communicate with other devices or systems via a backhaul connection (e.g., a wired backhaul or a wireless backhaul) or through a network.

[0052] In an embodiment, the storage unit 230 can store data such as basic programs, application programs, and setting information for the operation of the management node 201. The storage unit 230 can include a volatile memory, a non-volatile memory, or a combination of a volatile memory and a non-volatile memory. The storage unit 230 can provide stored data according to a request of the control unit 220.

[0053] In an embodiment, the control unit 220 can include at least one processor electrically and / or operatively coupled with the communication unit 210. The processor(s) according to an embodiment of the present disclosure can include various processing circuitries. For example, as used herein (including the claims), the term “processor,” “control unit,” or the like can include various processing circuitries including at least one processor, in which one or more of the at least one processor can be configured to perform various functions described herein. Also, the at least one processor can include a combination of processors that perform various recited / disclosed functions. The at least one processor can execute program instructions to implement or perform various functions. The control unit 220 can control overall operations of the management node 201. For example, the control unit 220 can transmit and receive signals through the communication unit 210. Also, the control unit 220 can record and read data in / from the storage unit 230. The control unit 220 can perform a designated function by executing instructions (or programs) stored in the storage unit 203.

[0054] According to an embodiment, as one or more of the plurality of higher-level entities (e.g., the first entity among the first and second entities) sharing a lower-level entity (e.g., the third entity) managed by the management node 201 is activated, the control unit 220 can be configured to receive, through the communication unit 210 (e.g., a transceiver), an activation request of the activated lower-level entity (e.g., the third entity) that is shared.

[0055] In an embodiment, if the higher-level entities (e.g., the first and second entities) are managed by different second management nodes, the control unit 220 can receive the activation request from a management node among the second management nodes that manages one or more activated higher-level entities (e.g., the first entity).

[0056] In an embodiment, if the multi-level entities including the higher-level entities (e.g., the first and second entities) and the lower-level entity (e.g., the third entity) are managed by the management node 201 alone, the control unit 220 can internally detect that the activation request occurs.

[0057] According to an embodiment, the control unit 220 of the management node 201 can be configured to, in response to the activation request, activate, for one or more activated higher-level entities (e.g., the first entity), the lower-level entity (e.g., the third entity) that is shared.

[0058] According to an embodiment, the management node 201 can comprise a NSSMF for managing NSSIs that are lower level entities. The NSSMF can receive an activation request for a NSSI of a particular NSI from a NSMF that manages the NSI as a higher level entity. The NSSMF can activate the NSSI shared by the NSI partially only for the particular NSI.

[0059] In an embodiment, the NSSMF can send a MF activation request for the particular NSI to a network element management system (EMS) that manages the MFs, thus enabling the EMS to configure the MFs as activated MFs for the particular NSI in response to the MF activation request.

[0060] In an embodiment, the NSSMF can send a MF configuration request for the particular NSI to the EMS that manages the MFs, thus enabling the EMS to configure the MFs for the particular NSI by omitting some MFs in response to the MF configuration request.

[0061] In an embodiment, the NSSMF can send a network reconfiguration request for enabling network communication related to the particular NSI to a network controller, thus enabling the network controller to reconfigure the network in response to the network reconfiguration request.

[0062] In an embodiment, the NSSMF can activate a lower level entity (e.g., NSSI) shared by a higher level entity (e.g., NSI 1, NSI 2) only for an activated set of entities (e.g., NSI 1) of the higher level entities (e.g., NSI 1, NSI 2). The NSSMF can deactivate the lower level entity (e.g., NSSI) shared by the higher level entity (e.g., NSI 1, NSI 2) for a de-activated set of entities (e.g., NSI 2) of the higher level entities (e.g., NSI 1, NSI 2).

[0063] According to an embodiment, the control unit 220 of the management node 201 can be configured to receive a deactivation request for a shared lower level entity (e.g., third entity) as one or more (e.g., first entity) of the higher level entities (e.g., first entity and second entity) are deactivated. The control unit 220 can be configured to deactivate the shared lower level entity (e.g., third entity) for the one or more deactivated higher level entities (e.g., first entity) in response to the deactivation request.

[0064] In an embodiment, the management node 201 can include an NSSMF for managing an NSSI that is a shared lower-level entity. In an embodiment, the NSSMF can identify whether NSIs that are higher-level entities sharing one NSSI are all deactivated. The NSSMF can deactivate the NSSI in a case where the NSIs that are higher-level entities sharing one NSSI, which is a shared lower-level entity, are all deactivated, and can maintain the NSSI in an activated state in a case where the NSIs sharing the NSSI are not all deactivated.

[0065] Figure 3 is a flowchart illustrating an operation method of a management node in a wireless communication system according to an embodiment.

[0066] Figure 3 The operations of the method illustrated can be performed by Figure 2b the management node 201 (for example, the management node 201 to be described below Figure 4b the N-level management system 401, Figure 6b the NSSMF 601, Figure 7a the NSSMF 701, Figure 7b the MF 705, Figure 8a the NSSMF 801, Figure 10a the NSSMF 1001, and Figure 11b the NSSMF 1101. However, this is not limited thereto. For example, Figure 3 The operations of the method illustrated can be performed by one or more devices or a combination of functions. The device(s) performing the operations of the method Figure 3 The entity performing the method illustrated is not limited to a hardware component. This can be implemented by hardware, software, or a combination of hardware and software. For example, in some embodiments, the method can be performed by an application installed in the management node 201.

[0067] Referring to Figure 3 , the operation method of a management node in a wireless communication system can include operation 310 and operation 320.

[0068] According to an embodiment, a CN of a wireless communication system can include various multi-level entities, for example, entity_1, entity_2, and entity_3. The entity_1, entity_2, or entity_3 can correspond to a slice entity operating in a network slice environment. At least a part of the entity_1, entity_2, and entity_3 can be entities of different levels. For example, the entity_1 and entity_2 can be higher-level or higher-layer (for example, N+1 level) entities compared to the entity_3. The entity_3 can be a lower-level or lower-layer (for example, N level) entity compared to the entity_1.

[0069] According to an embodiment, the CN of the wireless communication system can include the management node 201. In an embodiment, the management node 201 can be a first management node for managing the entity_3 which is a lower level entity. For example, the first management node can include at least one of the N-level management system 401 of Figure 4b or the NSMF 601 of Figure 6b .

[0070] Operation 310 can include receiving an activation request of the shared lower level entity (e.g., entity_3). In operation 310, as one or more (e.g., entity_1) of the multiple higher level entities (e.g., entity_1, entity_2) sharing the lower level entity (e.g., entity_3) managed by the management node 201 is activated, the management node (e.g., the control unit 220 of Figure 2b ) can receive the activation request of the shared lower level entity (e.g., entity_3).

[0071] According to an embodiment, if the higher level entities (e.g., entity_1 and entity_2 or NSI 1 and NSI 2) are managed by different second management nodes, the management node 201 can receive the activation request from the management node (e.g., any one of the N+1-level management system 402 of Figure 4b or the NSMF 602 of Figure 6b managing one or more of the activated higher level entities (e.g., entity_1, NSI 1) among the second management nodes.

[0072] According to an embodiment, if the multi-level entities including the higher level entities and the lower level entity are managed by one management node 201, the management node 201 can detect the occurrence of the activation request inside the management node 201.

[0073] Operation 320 can include selectively activating the shared lower level entity (e.g., entity_3). In operation 320, the management node 201 (e.g., the control unit 220 of Figure 2b ) can activate the shared lower level entity (e.g., entity_3) in response to the activation request received in operation 310.

[0074] In an embodiment, the management node 201 can selectively (or partially) activate the lower level entity only for a specific entity (e.g., entity_1) among the higher level entities sharing one lower level entity (e.g., entity_3). For example, selective (or partial) activation and / or deactivation of entity_3 for a specific higher level entity (e.g., entity_1) can be implemented, instead of binary activation of the entire entity_3 shared by multiple higher level entities (e.g., entity_1, entity_2).

[0075] According to an embodiment, the management node 201 can enable a slice entity (e.g., a lower level entity) to perform selective activation and / or deactivation. As a result, activation and / or deactivation of a lower level entity can be performed only for a specific higher level entity among higher level entities, not for all higher level entities sharing one lower level entity.

[0076] According to an embodiment, the management node 201 can directly control activation and / or deactivation of a slice entity (e.g., a lower level entity), or can induce activation and / or deactivation of a slice entity through selective activation and / or deactivation of a network function (or MF).

[0077] According to an embodiment, a method for performing deactivation of a shared lower level entity managed by the management node 201 can be provided. For example, a lower level entity can be deactivated only in the case where all higher level entities sharing one lower level entity are expected to be deactivated. In this method, the NSSI is presented as an example of a shared lower level entity.

[0078] According to an embodiment, a higher level entity (e.g., entity_1, entity_2) can be managed by a plurality of different second management nodes (e.g., Figure 7a If the higher level entity (e.g., entity_1, entity_2) is managed by a plurality of different second management nodes, the operation 310 for receiving an activation request can include receiving an activation request for a shared lower level entity (e.g., entity_3) from a management node among the second management nodes managing one or more activated higher level entities (e.g., entity_1).

[0079] According to an embodiment, a multi-level entity including a higher level entity (e.g., entity_1, entity_2) and a lower level entity (e.g., entity_3) can be managed by one same management node 201 (e.g., Figure 7b If the multi-level entity is managed by only one management node 201, the operation 310 for receiving an activation request can detect occurrence of an activation request inside the management node 201.

[0080] According to an embodiment, the management node 201 can include an NSSMF for managing an NSSI as a shared lower level entity (e.g., entity_3). The selective activation operation 320 of the shared lower level entity can include receiving an activation request for the NSSI for a specific NSI (e.g., NSI 1) among NSIs from an NSMF for managing the NSI as a higher level entity (e.g., Figure 6a and Figure 6bIn an embodiment, the selective activation operation 320 of the shared lower-level entity (e.g., entity_3) can include a selective activation operation of the MF by a handover scheme of the EMS (e.g., the selective activation operation 320 of the entity_3 of FIG. 10).

[0081] In an embodiment, the selective activation operation 320 of the shared lower-level entity (e.g., entity_3) can include a selective activation operation of the MF by a handover scheme of the EMS (e.g., the selective activation operation 320 of the entity_3 of FIG. 10). Figure 8a In an embodiment, the selective activation operation 320 of the shared lower-level entity (e.g., entity_3) can include a selective activation operation of the MF by a handover scheme of the EMS (e.g., the selective activation operation 320 of the entity_3 of FIG. 10).

[0082] In an embodiment, the selective activation operation 320 of the shared lower-level entity (e.g., entity_3) can include a selective activation operation of the MF by a handover scheme of the EMS (e.g., the selective activation operation 320 of the entity_3 of FIG. 10). Figure 9a In an embodiment, the selective activation operation 320 of the shared lower-level entity (e.g., entity_3) can include a selective activation operation of the MF by a handover scheme of the EMS (e.g., the selective activation operation 320 of the entity_3 of FIG. 10).

[0083] In an embodiment, the selective activation operation 320 of the shared lower-level entity (e.g., entity_3) can include a selective activation operation of the MF by a handover scheme of the EMS (e.g., the selective activation operation 320 of the entity_3 of FIG. 10). Figure 10a In an embodiment, the selective activation operation 320 of the shared lower-level entity (e.g., entity_3) can include a selective activation operation of the MF by a handover scheme of the EMS (e.g., the selective activation operation 320 of the entity_3 of FIG. 10).

[0084] In an embodiment, the selective activation operation 320 of the shared lower-level entity (e.g., entity_3) can include a selective activation operation of the MF by a handover scheme of the EMS (e.g., the selective activation operation 320 of the entity_3 of FIG. 10).

[0085] According to embodiments, the operation method of a management node in a wireless communication system can include receiving a deactivation request of a lower level entity (e.g., entity_3) that is shared, and deactivating the shared lower level entity (e.g., entity_3) in response to the deactivation request. As one or more (e.g., the first entity) of the higher level entities (e.g., the first and second entities) are deactivated, the management node 201 can receive a deactivation request of a lower level entity (e.g., entity_3) that is shared by the higher level entities. The management node 201 can be configured to selectively (or partially) deactivate the shared lower level entity (e.g., entity_3) in response to the deactivation request, with respect to one or more deactivated higher level entities (e.g., the first entity).

[0086] In embodiments, the management node 201 can include an NSSMF for managing an NSSI that is a shared lower level entity. In embodiments, the NSSMF can identify whether NSIs that are higher level entities sharing one NSSI are all deactivated. The NSSMF can deactivate the NSSI in case that the NSIs that are higher level entities sharing one NSSI (the one NSSI being a shared lower level entity) are all deactivated, and can maintain the NSSI in an activated state in case that the NSIs sharing the NSSI are not all deactivated (e.g., Figure 11a and Figure 11b embodiments).

[0087] Thereafter, operations for selectively activating and / or deactivating different level entities in a network slicing environment of a wireless communication system are described by referring to the accompanying drawings according to various embodiments. The illustrated operations can be sequentially performed, but not necessarily so. For example, the order of the operations can be changed, and at least two operations can be performed in parallel.

[0088] At least some of the operations for selectively activating and / or deactivating different level entities to be explained according to various embodiments can correspond to each other or can be performed in combination. In some embodiments, at least one of the illustrated operations can be omitted, the order of some operations can be changed, or other operations can be added.

[0089] Figure 4a and Figure 4b are diagrams for illustrating selective activation operations of a shared entity in a wireless communication system according to embodiments.

[0090] Reference will now be made to Figure 4aThe CN of the wireless communication system may include entity_1 411, entity_2 412, and entity_3 413. Entity_1 411 and entity_2 412 may be N+1 level entities, and entity_3 413 may be an N level entity. For entity_3 413, entity_1 411 and entity_2 412 may be shared. Entity_3 413 may be an entity shared by entity_1 411 and entity_2 412. Entity_3 413 may include two or more constituent elements 414. For example, each constituent element 414 of entity_3 413 indicates a unit for processing at least one function or operation, and may be implemented using hardware, software, or a combination of hardware and software.

[0091] Figure 4a In the first state 405, all of entities _1 411, _2 412, and the shared entity _3 413 can be deactivated. If entity _1 411 is switched to active, selective activation of entity _3 413 may be required. Therefore, it can switch from the first state 405 to the second state 406. In the second state 406, entity _1 411 can be switched to active, and entity _2 412 can be kept inactive. In the second state 406, the shared entity _3 413 can be selectively (or partially) activated, thus activating only entity _1 411 and keeping entity _2 412 deactivated.

[0092] According to the embodiment, each entity 411, 412, and 413 can be managed by a corresponding level of management system. For example, entities _1 411 and _2 412, which are N+1 level entities, can be managed by... Figure 4b The N+1 level management system 402 shown is used for management. Entity _3, which is an N-level entity and is shared by N+1 level entities, can be managed by... Figure 4b The N-level management system 401 shown is used for management.

[0093] refer to Figure 4b The selective activation operation of entity_3 413, which is the shared entity, may include operation 410, operation 420 and operation 430.

[0094] According to an embodiment, Figure 2b The management node 201 may include Figure 4b The N-level management system 401. The N-level management system 401 can perform selective activation operations on the shared entity _3 by communicating with the N+1-level management system 402.

[0095] According to the embodiment, entities_1 411, 412, and 413 can be deactivated (e.g., Figure 4a(e.g., the first state 405 of FIG. 4). For example, entity_1 411, entity_2 412, and entity_3 413 can have been instantiated and provisioned, but can not be serving users (inactive state).

[0096] For example, a user's UE 110 can be simultaneously connected to one or more network slice instances according to the provided services via the RAN 120. If the UE 110 sends the user service requirement information requested by the UE 110 to the CN 200 to obtain services from a specific network slice instance, the CN 200 can select an appropriate network slice instance based on the received information. With the network slice instance being selected, the management systems 401 and 402 of the CN 200 can be prepared for immediate use by instantiating and provisioning corresponding entities and allocating, arranging, or distributing resources for the user service requirement information. Even though the entities are instantiated and provisioned, they cannot serve users before being activated (e.g., link blocked). With the entities being instantiated and provisioned and then activated, they can serve users (e.g., link connected).

[0097] In operation 410, the N+1 level management system 402 can send an activation request for entity_3 413 of entity_1 411 to the N level management system 401.

[0098] In operation 420, the N level management system 401 can selectively activate entity_3 413 in response to the activation request received in operation 410. By activating entity_3 413 for entity_1 411, the N level management system 401 can selectively (or partially) activate only some of the constituent elements of entity_3 constituent elements 414 related to entity_1 411 and maintain other constituent elements in an inactive state.

[0099] In operation 430, the N level management system 401 can send an OK response for the activation request of operation 410 to the N+1 level management system 402.

[0100] By activating entity_3 413 for entity_1 411 in operation 430, entity_3 413 shared by entity_1 411 and entity_2 412 can be selectively activated for entity_1 411 only (e.g., the second state 406 of FIG. 4). Thus, entity_1 411 can be switched to an active state and entity_2 412 can be maintained in an inactive state (e.g., the first state 405 of FIG. 4). Figure 4a the second state 406 of FIG. 4). Thus, entity_1 411 can be switched to an active state and entity_2 412 can be maintained in an inactive state (e.g., the first state 405 of FIG. 4). Figure 4a the second state 406 of FIG. 4). Thus, entity_1 411 can be switched to an active state and entity_2 412 can be maintained in an inactive state (e.g., the first state 405 of FIG. 4).

[0101] Figure 5a and Figure 5bis a diagram for illustrating a selective deactivation operation of a shared entity in a wireless communication system according to an embodiment.

[0102] In an initial state 505 of Figure 5a , the entity_1 411, the entity_2 412, and the entity_3 413 which is a shared entity can be activated. If the entity_1 411 is switched to an inactive state, a selective deactivation of the entity_3 413 can be required. Accordingly, it can be switched from the first state 505 to a second state 506. In the second state 506, the entity_1 411 can be switched to an inactive state, and the entity_2 412 can be maintained in an active state. In the second state 506, the shared entity_3 413 can be selectively (or partially) deactivated, thus being deactivated only for the entity_1 411 and still being activated for the entity_2 413.

[0103] According to an embodiment, the management node 201 can include an N-level management system 401 of Figure 5b . The N-level management system 401 can perform a selective deactivation operation of the shared entity_3 413 by interworking with an N+1-level management system 402.

[0104] Referring to Figure 5b , the selective deactivation operation of the entity_3 413 which is a shared entity can include an operation 510, an operation 520, and an operation 530.

[0105] According to an embodiment, the entity_1 411 and the entity_2 412 can be activated, and the shared entity_3 413 can be activated as a whole for both the entity_1 411 and the entity_2 412 (e.g., a first state 505 of Figure 5a ). For example, the entity_1 411, the entity_2 412, and the entity_3 413 can have been instantiated and configured, and can be serving a user.

[0106] In operation 510, the N+1-level management system 402 can transmit, to the N-level management system 401, a deactivation request of the entity_3 413 for the entity_1 411.

[0107] In operation 520, the N-level management system 401 can selectively deactivate the entity_3 413 in response to the deactivation request received in operation 510. By deactivating the entity_3 413 for the entity_1 411, the N-level management system 401 can selectively (or partially) deactivate only some of the constituent elements of the entity_3 413 which are related to the entity_1 411, and maintain other constituent elements in an active state.

[0108] In operation 530, the N-level management system 401 can send an OK response to the deactivation request in operation 510 to the N+1-level management system 402.

[0109] By deactivating entity_3 413 for entity_1 411 in operation 530, entity_3 413, which is shared by entities_1 411 and entity_2 412, can be selectively deactivated only for entity_1 411 (e.g., Figure 5a The second state 506). Therefore, entity_1 411 can be switched to the inactive state, and entity_2 413 can be maintained in the active state (e.g., Figure 5a The second state (506).

[0110] Figure 6a and Figure 6b This is a flowchart illustrating the selective activation operation of an NSSI shared by multiple NSIs in a wireless communication system according to an embodiment.

[0111] Figure 6a and Figure 6b The embodiments can Figure 4a and Figure 4b The embodiments are applied to specific entities. For example, Figure 6a NSI 1 611, NSI 2 612, the shared NSSI 613, and NSSI constituent element 614 can correspond to Figure 4a The entities are: Entity 1411 (higher level entity), Entity 2 412 (higher level entity), Shared Entity 3 413 (lower level entity), and Entity 3 constituent element 414 (constituent element of lower level entity). Figure 6b The NSMF shown is used to manage the more advanced NSI 1 611 and NSI 2 612 devices, and can correspond to... Figure 4a The N+1 level management system 402. Figure 6b The NSMF 601 shown is a device used to manage the lower-level shared NSMF 602, and can correspond to Figure 4a The N-level management system 401. Figure 6b Operations 610, 620, and 630 shown can respectively correspond to Figure 4a Operations 410, 420 and 430.

[0112] exist Figure 6aIn the first state 605, the NSI 1 611, the NSI 2 612 and the shared NSSI 613 can be deactivated. If the NSI 1 611 is switched to the active state, the selective activation of the shared NSSI 613 can be required. Thus, it can be switched from the first state 605 to the second state 606. In the second state 606, the NSI 1 611 can be switched to the active state and the NSI 2 612 can be maintained in the inactive state. In the second state 606, the shared NSSI 613 can be selectively (or partially) activated, thus activated only for the NSI 1 611 and deactivated for the NSI 2 613.

[0113] Reference Figure 6b The selective activation operation of the shared NSSI 613 can include an operation 610, an operation 620 and an operation 630.

[0114] In an embodiment, the NSI 1 611, the NSI 2 612 and the shared NSSI 613 can be deactivated (e.g., Figure 6a the first state 605). For example, the NSI 1 611, the NSI 2 612 and the shared NSSI 613 can have been instantiated and configured, but can not serve users (inactive state).

[0115] In operation 610, the NSMF 602 for managing the NSI 1 611 and the NSI 2 612 can transmit an activation request for the NSSI 613 of the NSI 1 611 to the NSSMF 601 managing the shared NSSI 613 to the NSSMF 601.

[0116] In operation 620, the NSSMF 601 can selectively activate the NSSI 613 in response to the activation request received in operation 610. By activating the NSSI 613 for the NSI 1 611, the NSSMF 601 can selectively (or partially) activate only some of the NSSI constituent elements 614 related to the NSI 1 611 among the NSSI constituent elements 614 and maintain the other constituent elements in the inactive state.

[0117] In operation 630, the NSSMF 601 can transmit an OK response for the activation request of operation 610 to the NSMF 602.

[0118] By activating the NSSI 613 for the NSI 1 611 in operation 630, the NSSI 613 shared by the NSI 1 611 and the NSI 2 612 can be selectively activated only for the NSI 1 611 (e.g., Figure 6ato the second state 606). Thus, the NSI 1 611 can be switched to the active state, and the NSI 2 612 can be maintained in the non-active state (e.g., Figure 6a to the second state 606).

[0119] Figure 7a is a flowchart illustrating a selective activation operation of a shared entity in a case where higher-level entities are managed by different management systems, in a wireless communication system according to an embodiment.

[0120] According to an embodiment, a CN of a wireless communication system can include a plurality of management systems. Higher-level (e.g., N+1 level) entities sharing a lower-level (e.g., N level) entity can be managed by different management systems. In this case, a selective activation operation performed on a higher-level entity managed by one management system can not affect other higher-level entities managed by other management systems.

[0121] Referring to Figure 7a , a plurality of N+1 level entities (e.g., entity_1 to entity_N) can be managed by the NSMF 702 as a different management system and the NSMF(s) 703. The shared entity_X of the N level can be managed by the NSSMF 701. The NSSMF 701 can perform a selective activation operation of the shared entity_X by interworking with the NSMF 702 and / or the NSMF(s) 703.

[0122] Referring to Figure 7a , if higher-level entities are managed by different management systems, the selective activation operation of the shared entity_X can include operation 710, operation 720, and operation 730.

[0123] In an embodiment, the entity_1 to entity_N of the N+1 level and the entity_X of the N level can have been instantiated and configured, but can not serve users (non-active state).

[0124] In operation 710, the NSMF 702 managing the entity_1 can transmit an entity_X activation request for the entity_1 to the NSSMF 701 managing the entity_X.

[0125] In operation 720, the NSSMF 701 can selectively activate the entity_X in response to the activation request received in operation 710. By activating the entity_X for the entity_1, the NSSMF 701 can selectively (or partially) activate only some constituent elements of the entity_X constituent elements related to the entity_1, and maintain other constituent elements in a non-active state.

[0126] In operation 730, the NSSMF 701 can transmit an OK response for the activation request of operation 710 to the NSMF 702.

[0127] By activating the entity_X for the entity_1 in operation 730, the entity_X shared by the entity_1 to the entity_N can be selectively activated only for the entity_1. Accordingly, the entity_1 can be activated to provide a service, and the entity_2 to the entity_N can be maintained in an inactive state.

[0128] Accordingly, the NSSMF 701 can selectively (or partially) activate the entity_X shared by all of the entity_1 to the entity_N only for the entity_1, according to a request of the NSMF 701 managing the entity_1. Such a selective activation operation of the N-level entity_X can be performed only for the entity_1 of the N+1 level managed by the NSMF 701 as one management system, and can not affect the entity_2 to the entity_N as other N+1 level entities managed by the NSMF(s) 703 as other management systems.

[0129] Figure 7b is a flowchart illustrating a selective activation operation of a shared entity in a case where multiple level entities are managed by one management system in a wireless communication system according to an embodiment.

[0130] According to an embodiment, in a CN hierarchy of a wireless communication system, a plurality of slice entities can be managed by a single management system.

[0131] Referring to Figure 7b , a plurality of slice entities (e.g., entity_1, entity_2, and entity_3) having different levels can be managed by one management function 705. The entity_3 of the N level can be an entity shared by the entity_1 of the N+1 level and the entity_2 of the N+1 level.

[0132] Referring to Figure 7b , if the multiple level entities are managed by a single management system, a selective activation operation of the shared entity_3 can include operations 711, 721, and 731.

[0133] In an embodiment, the entity_1, the entity_2, and the entity_3 can have been instantiated and configured, but can not serve a user (inactive state).

[0134] In operation 711, the management function 705 managing the entity_1, the entity_2, and the shared entity_3 can detect that an entity_3 activation request for the entity_1 occurs.

[0135] In operation 721, the management function 705 can selectively activate entity_3 in response to the activation request detected in operation 711. By activating entity_3 for entity_1, the management function 705 can selectively (or partially) activate some of the constituent elements among the entity_3 constituent elements related to entity_1, and maintain other constituent elements in an inactive state.

[0136] In operation 731, the management function 705 can feedback an OK response for the activation request occurred in operation 711. By activating entity 3 for entity 1 in operation 731, entity 3 shared by entity 1 and entity 2 can be selectively activated only for entity 1. Accordingly, entity 1 can be activated to provide a service, and entity 2 can be maintained in an inactive state.

[0137] Figure 8a is a flowchart illustrating a selective activation operation of an MF by a handover scheme supported by an EMS in a wireless communication system according to an embodiment.

[0138] According to an embodiment, in order for selective activation of a shared entity (e.g., NSSI) in a network slice environment, support of a lower-level (or lower-layer) management system (e.g., EMS 803 of Figure 8a ) can be required.

[0139] According to an embodiment, an NSSI can group constituent elements MF (or managed function instance (MFI)) which are configurable entities. In order for overall activation of the NSSI, it can be necessary to configure all configurable MFs which are lower-level entities. A selective (or partial) activation of the NSSI can be implemented with a scheme of configuring only some of the configurable MFs. In an embodiment, selective activation of the NSSI lower-level can be supported.

[0140] Referring to Figure 8a , a CN of a wireless communication system can include an NSMF 802 for managing NSI 1 and NSI 2, an NSSMF 801 for managing a shared NSSI, an EMS 803 for managing MF 805, and MF 805. The NSI 1 and NSI 2 can be higher-level (e.g., N+1 level) entities compared to the NSSI. The NSSI can be a lower-level (e.g., N level) entity compared to the NSI 1 and NSI 2. The NSSI can include MF 805 which is a lower-level (e.g., N-1 level) entity of the NSSI. The EMS 803 can support a selective handover scheme for each MF 805 which is a lower-level entity of a shared entity.

[0141] Referring to Figure 8aThe selective activation operation on the shared entities by the selective activation handover scheme supported by the EMS 803 can include operation 811, operation 812, operation 813, operation 814, operation 815, and operation 816.

[0142] In an embodiment, NSI 1 and NSI 2, which are N+1 level entities, can have been instantiated and configured, but can not be serving users (inactive state).

[0143] In operation 811, the NSMF 802 managing NSI 1 and NSI 2 can transmit an NSSI activation request for NSI 1 to the NSSMF 801 managing the NSSI.

[0144] In an embodiment, the NSSMF 801 can perform a selective NSSI activation operation in response to the activation request received in operation 811. The selective NSSI activation operation can include operation 812, operation 813, operation 814, operation 815, and operation 816.

[0145] In operation 812, the NSSMF 801 can transmit an MF activation request for NSI 1 to the EMS 803 managing the MF 805. In operation 813, the EMS 803 can configure MFs to be activated for NSI 1 with a scheme for selectively switching only some of the MFs 805. In operation 814 and operation 815, the EMS 803 can receive OK signals notifying of completion of MF configuration for activation of NSI 1 from the MFs 805 and forward the same to the NSSMF 801. In operation 816, upon receipt of the OK signals from the EMS 803, the NSSMF 801 can activate the NSSI for NSI 1.

[0146] In operation 817, the NSSMF 801 can transmit an OK response for the activation request of operation 812 to the NSMF 802.

[0147] Through the above procedure, the MFs 805, which are lower level entities of the NSSI, can be selectively activated only for NSI 1. Accordingly, the NSSI, which is a higher level entity of the MFs 805, can also be selectively activated only for NSI 1. According to the selective activation of the NSSI, NSI 1 can be activated to be switched to provide a service, and NSI 2 can be maintained in an inactive state.

[0148] Figure 8b is a flowchart illustrating a selective deactivation operation on MFs by a handover scheme supported by an EMS in a wireless communication system according to an embodiment.

[0149] Reference Figure 8bThe selective deactivation operation of the shared entities by the selective activation handover scheme supported by the EMS 803 can include operation 821, operation 822, operation 823, operation 824, operation 825, operation 826, and operation 827.

[0150] In an embodiment, the NSI 1, the NSI 2, the NSSI, and the MF can have been instantiated and configured to serve users (an activated state).

[0151] In operation 821, the NSMF 802 managing the NSI 1 and the NSI 2 can transmit an NSSI deactivation request for the NSI 1 to the NSSMF 801 managing the NSSI.

[0152] In an embodiment, the NSSMF 801 can perform a selective NSSI deactivation operation in response to the deactivation request received in operation 811. The selective NSSI deactivation operation can include operation 822, operation 823, operation 824, operation 825, and operation 826.

[0153] In operation 822, the NSSMF 801 can transmit an MF activation request for the NSSI 1 to the EMS 803 managing the MF 805. In operation 823, the EMS 803 can configure the MF to be activated for the NSI 1 with a scheme for selectively switching only some of the MF 805. In operation 824 and operation 825, the EMS 803 can receive OK signals notifying of completion of the MF configuration for the NSI 1 activation from the MF 805 and forward the same to the NSSMF 801. In operation 826, upon receipt of the OK signals from the EMS 803, the NSSMF 801 can activate the NSSI for the NSI 1.

[0154] In operation 827, the NSSMF 801 can transmit an OK response for the activation request of operation 812 to the NSMF 802.

[0155] Through the above procedure, the MF 805, which is a lower-level entity of the NSSI, can be selectively activated only for the NSI 1. Accordingly, the NSSI, which is a higher-level entity of the MF 805, can also be selectively activated only for the NSI 1. According to the selective activation of the NSSI, the NSI 1 can be activated to provide a service, and the NSI 2 can be maintained in a non-activated state.

[0156] Figure 9a is a flowchart illustrating a selective activation operation of an MF by a completion configuration or a missing configuration scheme in a wireless communication system according to an embodiment.

[0157] Some communication standards can limit selective handover schemes by lower level entity managed systems (e.g., EMS). In such cases, selective activation of shared entities can be achieved by completing configuration.

[0158] According to embodiments, to achieve selective activation of shared entities, as part of instantiation and configuration operations, only some of the MFs can be configured. In embodiments, NSSI level selective activation can be supported. For example, only some of the configurable MFs (N-1 level) of a lower level entity, NSSI (N level), can be partially configured, and other MFs can be missing configuration. As a result of missing configuration, the corresponding MFs can not serve users.

[0159] Referring to Figure 9a The CN of the wireless communication system can include an EMS 903. The EMS 903 can be a lower level management system for managing MFs 805, which are lower level entities that are shared entities.

[0160] Referring to Figure 9a The selective activation operation of shared entities by completing configuration can include operation 911, operation 912, operation 913, operation 914, operation 915, operation 916, and operation 917.

[0161] In embodiments, NSI 1 and NSI 2, which are N+1 level entities, can have been instantiated and configured. The MFs have been instantiated and configured, but can be missing the part of the configuration that enables service, and can not serve users (inactive state).

[0162] In operation 911, the NSMF 802 that manages NSI 1 and NSI 2 can transmit an NSSI activation request for NSI 1 to the NSSMF 801 that manages NSSI.

[0163] In embodiments, the NSSMF 801 can perform a selective NSSI activation operation in response to the activation request received in operation 911. The selective NSSI activation operation can include operation 912, operation 913, operation 914, operation 915, and operation 916.

[0164] In operation 912, the NSSMF 801 can transmit an MF configuration request to the EMS 903 managing the MF 805. The request can request to complete missing configuration. In operation 913, the EMS 903 can configure the MFs with a scheme of adding only some MFs 805 to the configuration and missing others. In operations 914 and 915, the EMS 903 can receive OK signals notifying completion of missing configuration from the MFs 805 and forward them to the NSSMF 801. In operation 916, upon receiving the OK signals from the EMS 903, the NSSMF 801 can activate the NSSI for the NSI 1.

[0165] In operation 917, the NSSMF 801 can transmit an OK response for the activation request of operation 911 to the NSMF 802.

[0166] Through the above procedure, the MFs 805 that are lower-level entities of the NSSI can be selectively activated only for the NSI 1. Accordingly, the NSSI that is a higher-level entity of the MFs 805 can also be selectively activated only for the NSI 1. Through the selective activation of the NSSI, the NSI 1 can be activated to provide a service, and the NSI 2 can be maintained in an inactive state.

[0167] Figure 9b is a flowchart illustrating a selective deactivation operation of an MF through completion of configuration (or missing configuration) in a wireless communication system according to an embodiment.

[0168] According to an embodiment, in order to implement selective deactivation of the NSSI that is a shared entity, removal of some configurations of the MFs constituting the NSSI can be included. The corresponding operation can make the MFs unable to serve users with respect to the NSSI that is a higher-level entity.

[0169] Reference Figure 9b The selective deactivation operation of the shared entity through completion of configuration can include operations 921, 922, 923, 924, 925, 926, and 927.

[0170] In an embodiment, the NSI 1, the NSI 2, the NSSI, and the MFs can have been instantiated and configured to serve users (active state).

[0171] In operation 921, the NSMF 802 managing the NSI 1 and the NSI 2 can transmit an NSSI deactivation request for the NSI 1 to the NSSMF 801 managing the NSSI.

[0172] In an embodiment, the NSSMF 801 can perform a selective NSSI deactivation operation in response to the deactivation request received in operation 811. The selective NSSI deactivation operation can include operation 922, operation 923, operation 924, operation 925, and operation 926.

[0173] In operation 922, the NSSMF 801 can transmit an MF reconfiguration request (or a request for partial configuration removal) to the EMS 803 managing the MF 805. In operation 923, the EMS 903 can reconfigure the MF by removing some of the MF 805 in the configuration. In operations 924 and 925, the EMS 903 can receive an OK signal notifying that the MF reconfiguration is complete (or the partial configuration removal is complete) from the MF 805 and forward the same to the NSSMF 801. In operation 926, upon receiving the OK signal from the EMS 903, the NSSMF 801 can deactivate the NSSI for the NSI 1. In operation 927, the NSSMF 801 can transmit an OK response for the deactivation request of operation 921 to the NSMF 802.

[0174] Through the above procedure, the MF 805, which is a lower-level entity of the NSSI, can be selectively deactivated only for the NSI 1. Accordingly, the NSSI, which is a higher-level entity of the MF 805, can also be selectively deactivated only for the NSI 1. According to the selective deactivation of the NSSI, the NSI 1 can be deactivated not to provide a service, and the NSI 2 can be maintained in an activated state.

[0175] Figure 10a is a flowchart illustrating a selective activation operation of an NSSI or an MF by a network communication blocking or unblocking scheme according to an embodiment.

[0176] Some communication standards can limit a selective handover scheme by a lower-level entity management system (e.g., an EMS). In this case, selective activation of an NSSI or a shared entity can be implemented by blocking or unblocking network communication.

[0177] According to embodiments, to implement the selective activation of the shared entity, as part of the instantiation and configuration operations, operations to block or unblock network communications can be included. In embodiments, NSSI level selective activation can be supported. For example, for NSSI level selective activation, the network connectivity portion of the NSSI or MF can be modified. The NSSI or MF instantiation and configuration can make the corresponding entity fully operational, but can be missing or alter the configured network portion. Such network configuration can interrupt communications with other constituent elements of the service to not serve the user. An activation operation can complete the missing configuration or modify the missing configuration. Such activation operation can activate nominal connectivity for the particular higher level entity and thus enable the NSSI or MF to fully serve the user.

[0178] Referring to Figure 10a The CN of the wireless communication system can include the NSMF 1002 for managing the NSI 1 and the NSI 2, the NSSMF 1001 for managing the shared NSSI, the network controller 1003, the network 1004, the EMS 1005, and the MF 1006. The NSI 1 and the NSI 2 can be higher level (e.g., N+1 level) entities compared to the NSSI. The NSSI can be a lower level (e.g., N level) entity compared to the NSI 1 and the NSI 2.

[0179] Referring to Figure 10a The selective activation operation of the shared entity by blocking or unblocking network communications can include operation 1011, operation 1012, operation 1013, operation 1014, operation 1015, operation 1016, and operation 1017.

[0180] In embodiments, the NSI 1, the NSI 2, the NSSI, and the MF can have been instantiated and configured, but can not be serving a user (non-activated state). The network 1004 (e.g., a particular network slice or subnetwork) can be configured to block each service traffic (or communication) for the NSI 1 and the NSI 2.

[0181] In operation 1011, the NSMF 1002 managing the NSI 1 and the NSI 2 can transmit an NSSI activation request for the NSI 1 to the NSSMF 1001 managing the NSSI.

[0182] In embodiments, the NSSMF 1001 can perform a selective NSSI activation operation in response to the activation request received in operation 1011. The selective NSSI activation operation can include operation 1012, operation 1013, operation 1014, operation 1015, and operation 1016.

[0183] In operation 1012, the NSSMF 1001 can transmit a network reconfiguration request to the network controller 1003 to enable service traffic (or communication) for the NSI 1. In operation 1013, the network controller 1003 can reconfigure the network 1004 to unlock the service traffic for the NSI 1. In operations 1014 and 1015, the network controller 1003 can receive an OK signal from the reconfigured network 1004 and forward it to the NSSMF 1001. In operation 1016, upon receiving the OK signal from the network controller 1003, the NSSMF 1001 can activate the NSSI for the NSI 1.

[0184] In operation 1017, the NSSMF 1001 can transmit an OK response for the activation request of operation 1011 to the NSMF 1002.

[0185] Through the above procedure, the NSI 1 can be activated, and the NSI 2 can not be activated. The shared NSSI can be selectively (or partially) activated only for the NSI 1. The reconfiguration of the network 1004 can enable communication only for the service related to the NSI 1.

[0186] Figure 10b is a flowchart illustrating a selective deactivation operation of an NSSI or an MF by blocking or unblocking network communication in a wireless communication system according to an embodiment.

[0187] Reference Figure 10b The selective deactivation operation of the shared entity by blocking or unblocking network communication can include operations 1021, 1022, 1023, 1024, 1025, 1026, and 1027.

[0188] In an embodiment, the NSI 1, the NSI 2, the NSSI, and the MF can all be instantiated and configured to serve users (an activated state).

[0189] In operation 1021, the NSMF 1002 managing the NSI 1 and the NSI 2 can transmit an NSSI deactivation request for the NSI 1 to the NSSMF 1001 managing the NSSI.

[0190] In an embodiment, the NSSMF 1001 can perform a selective NSSI deactivation operation in response to the deactivation request received in operation 1021. The selective NSSI deactivation operation can include operations 1022, 1023, 1024, 1025, and 1026.

[0191] In operation 1022, the NSSMF 1001 can transmit an MF reconfiguration request to the network controller 1003 to disable service traffic (or communication) for the NSI 1. In operation 1023, the network controller 1003 can reconfigure the network 1004 to block service traffic for the NSI 1. In operations 1024 and 1025, the network controller 1003 can receive an OK signal from the reconfigured network 1004 and forward it to the NSSMF 1001. In operation 1026, upon receiving the OK signal from the network controller 1003, the NSSMF 1001 can deactivate the NSSI for the NSI 1.

[0192] In operation 1027, the NSSMF 1001 can transmit an OK response for the deactivation request of operation 1021 to the NSMF 1002.

[0193] Through the above procedure, the NSI 1 can be deactivated, and the NSI 2 can be maintained in an activated state. The shared NSSI can be selectively (or partially) deactivated only for the NSI 1. The reconfiguration of the network 1004 can disable communication only for the service related to the NSI 1.

[0194] According to an embodiment, a network communication blocking (or service traffic blocking) scheme can be implemented as follows: - configuring a hardware or software firewall to block specific network traffic - disabling an interface of a hardware or software switch and router - configuring a routing protocol, routing policy, or static route on a hardware or software switch or router to block or blackhole route specific traffic - configuring an internal firewall on a virtual machine constituting an MF to block specific network traffic - disabling an interface on a virtual machine constituting an MF - configuring a routing protocol, routing policy, or static route on a virtual machine constituting an MF to block or blackhole route specific traffic.

[0195] According to an embodiment, a network communication unblocking (or service traffic unblocking) scheme can be implemented as follows: - configuring a hardware or software firewall to unblock specific network traffic - enabling an interface on a hardware or software switch and router - configuring a routing protocol, routing policy, or static route on a hardware or software switch or router to allow and route specific traffic - configuring an internal firewall on a virtual machine constituting an MF to allow specific network traffic - enabling an interface on the virtual machine that constitutes the MF, which configures a routing protocol, a routing policy, or a static route on the virtual machine that constitutes the MF to allow and route specific traffic.

[0196] Figure 11a and Figure 11b is a diagram for showing a selective deactivation operation of a NSSI by a consensus scheme of an NSMF in a wireless communication system according to an embodiment.

[0197] If some communication standards do not support a selective activation and deactivation scheme per NSI, a consensus scheme can be used to improve the control of deactivation by an NSMF request. A higher-level management node (e.g., NSMF) can not be aware of other higher-level management nodes (e.g., another NSMF) that share a lower-level entity (e.g., NSSI). In this case, each higher-level management node can request deactivation to a lower-level management node (e.g., NSSMF) based only on a predetermined state of an entity (e.g., NSI) it manages. A lower-level management node (e.g., NSSMF) that manages a shared entity (e.g., NSSI) can prevent the entity (e.g., NSSI) it manages from being deactivated while some higher-level entities are still activated.

[0198] Referring to Figure 11a , NSI 1 1111 is an N+1 level entity and can be an entity managed by NSMF 1 1102. NSI2 1112 is an N+1 level entity and can be an entity managed by NSMF 2 1103. NSSI 1113 can be an N level entity shared by NSI 1 and NSI 2. NSSI 1113 can include NSSI constituent elements 1115.

[0199] In a first state 1106 of Figure 11a , NSI 1 1111, NSI 2 1112, and shared NSSI 1113 can all be activated. By performing NSI 1 deactivation with NSMF request tracking, the first state 1106 can be switched to a second state 1107. In the second state 1107, only NSI 1 can be deactivated, and NSI 2 can be maintained in an activated state.

[0200] Referring to Figure 11b , a CN of a wireless communication system can include NSMF 1 1102 for managing NSI 1 1111, NSMF 2 1103 for managing NSI 2, NSSMF 1101 for managing shared NSSI 1113, EMS 1104 for managing MF of the NSSI, and MF 1105 managed by the EMS 1104.

[0201] Referring toFigure 11b An activation operation with NSMF requesting tracking can include NSI 1 activation operation 1131 and / or NSI2 activation operation 1132.

[0202] NSI 1 activation operation 1131 can include operation 1121 and operation 1122.

[0203] In operation 1121, NSMF 1 1102 managing NSI 1 1111 can send an activation request of NSSI 1113 to NSSMF 1101 managing NSSI 1113 as a shared lower level entity. Upon receiving the activation request, NSSMF 1101 for managing NSSI 1113 as a shared lower level entity can store information of NSMF 1 1102 (e.g., system ID of NSMF 1 1102 and / or entity ID of NSI 1) that sends the request for activating NSSI 1113 in place of NSI 1. If the managed NSSI 1113 is already deactivated, NSSMF 1101 can perform NSSI activation in response to the request. In operation 1122, NSSMF 1101 can send an OK response to the activation request of operation 1121 to NSMF 1 1102.

[0204] NSI 2 activation operation 1132 can include operation 1123 and operation 1124.

[0205] In operation 1123, NSMF 2 1103 managing NSI 2 1112 can send an activation request of NSSI 1113 to NSSMF 1101 managing the shared NSSI 1113. Upon receiving the activation request, NSSMF 1101 can store information of NSMF 2 1103 (e.g., system ID of NSMF 2 1103 and / or entity ID of NSI 2) that sends the request for activating the managed NSSI 1113 in place of NSI 2. In operation 1124, NSSMF 1101 can send an OK response to the activation request of operation 1123 to NSMF 2 1103.

[0206] Reference Figure 11b A deactivation operation with NSMF requesting tracking can include NSI 1 deactivation operation and / or NSI2 deactivation operation.

[0207] NSI 1 deactivation operation 1133 can include operation 1125 and operation 1126.

[0208] In operation 1125, the NSMF 1 1102 can transmit a deactivation request for the NSSI 1113 to the NSSMF 1101. Upon receiving the deactivation request, the NSSMF 1101, which is a lower-level management node, can store information of the NSMF 1 1102 (e.g., a system ID of the NSMF 1 1102 and / or an entity ID of the NSI 1 1111) that transmitted the request for activating the NSSI 1113 on behalf of the NSI 1. In operation 1126, the NSSMF 1101 can transmit an OK response for the deactivation request of operation 1125 to the NSMF 1 1102.

[0209] The NSI 2 deactivation operation 1134 can include operation 1127 and operation 1128.

[0210] In operation 1127, the NSMF 1 1102 can transmit a deactivation request for the NSSI 1113 to the NSSMF 1101. If the deactivation request is received from the NSMF 1 1102, the NSSMF 1101 can delete the stored information of the NSMF 1 1102 (e.g., a system ID of the NSMF 1 1102 and / or an entity ID of the NSI 1 1111) for activation. If the corresponding information is all deleted and there is no longer an intention to activate the NSMF 1 1102 and the NSMF 2 1103 for management, the NSSMF 1101 can perform deactivation of the NSSI 1113 shared by the NSMF 1 1102 and the NSMF 2 1103. In operation 1128, the NSSMF 1101 can transmit an OK response for the deactivation request of operation 1127 to the NSMF 1 1102.

[0211] The operation method of a management node according to various embodiments can be an operation method of a management node in a wireless communication system having a network slice environment. The method can include receiving an activation request for a shared lower-level entity as one or more higher-level entities of a plurality of higher-level entities sharing the lower-level entity managed by the management node are activated, and in response to the activation request, activating the shared lower-level entity with respect to the activated one or more higher-level entities.

[0212] According to various embodiments, receiving the activation request can include receiving the activation request from a management node that manages the activated one or more higher-level entities among second management nodes if the higher-level entity is managed by the different second management nodes.

[0213] According to various embodiments, receiving the activation request can include detecting an occurrence of the activation request inside the management node if a multi-level entity including the higher-level entity and the lower-level entity is managed by the management node.

[0214] According to various embodiments, the management node can include an NSSMF for managing the NSSIs that are lower-level entities. Receiving the activation request can include receiving, at the NSSMF, an activation request for the NSSIs in a particular NSI from an NSMF that manages the NSI that is a higher-level entity. The activating can include activating, at the NSSMF, the NSSIs shared by the NSI only partially for the particular NSI.

[0215] According to various embodiments, the activating the NSSIs shared by the NSI only partially at the NSSMF for the particular NSI can include sending, at the NSSMF, a MF activation request for the particular NSI to an EMS that manages the MFs to enable the EMS to configure the MFs in response to the MF activation request to activate the MFs for the particular NSI.

[0216] According to various embodiments, the activating the NSSIs shared by the NSI only partially at the NSSMF for the particular NSI can include sending, at the NSSMF, a MF configuration request for the particular NSI to an EMS that manages the MFs to enable the EMS to configure the MFs in response to the MF configuration request by missing some of the MFs for the particular NSI.

[0217] According to various embodiments, the activating the NSSIs shared by the NSI only partially at the NSSMF for the particular NSI can include sending, at the NSSMF, a network reconfiguration request to a network controller for enabling network communication related to the particular NSI to enable the network controller to reconfigure the network in response to the network reconfiguration request.

[0218] According to various embodiments, the activating can include activating the shared lower-level entities only for a set of activated entities among the higher-level entities and deactivating the shared lower-level entities for a set of deactivated entities among the higher-level entities.

[0219] According to various embodiments, the method can include receiving a deactivation request for the shared lower-level entities as one or more higher-level entities are deactivated, and deactivating the shared lower-level entities for the deactivated one or more higher-level entities in response to the deactivation request.

[0220] According to various embodiments, the management node can include an NSSMF for managing the NSSIs that are lower-level entities. The deactivating can include identifying, at the NSSMF, whether the NSIs sharing one NSSI are all deactivated, deactivating the NSSI if the NSIs are all deactivated, and maintaining the NSSI in an activated state if the NSIs are not all deactivated.

[0221] A management node according to various embodiments can be a management node in a wireless communication system having a network slice environment. The management node can include a transceiver; and at least one processor connected to the transceiver. The at least one processor can be configured to receive an activation request for a shared lower-level entity as one or more higher-level entities of a plurality of higher-level entities sharing the lower-level entity managed by the management node are activated; and in response to the activation request, activate the shared lower-level entity for the activated one or more higher-level entities.

[0222] According to various embodiments, the at least one processor can be configured to receive the activation request from a management node among second management nodes managing the activated one or more higher-level entities, if the higher-level entity is managed by the different second management node.

[0223] According to various embodiments, the at least one processor can be configured to detect an occurrence of the activation request internally in the management node, if a multi-level entity including the higher-level entity and the lower-level entity is managed by the management node.

[0224] According to various embodiments, the management node can include an NSSMF for managing an NSSI as a lower-level entity. The at least one processor can be configured to receive an activation request for the NSSI for a specific NSI of NSIs from an NSMF managing the NSI as a higher-level entity, and activate the NSSI shared by the NSI only partially for the specific NSI.

[0225] According to various embodiments, the at least one processor can be configured to transmit an MF activation request for the specific NSI to an EMS managing the MFs, to enable the EMS to configure some MFs as MFs to be activated for the specific NSI in response to the MF activation request.

[0226] According to various embodiments, the at least one processor can be configured to transmit an MF configuration request for the specific NSI to an EMS managing the MFs, to enable the EMS to configure the MFs for the specific NSI by missing some MFs in response to the MF configuration request.

[0227] According to various embodiments, the at least one processor can be configured to transmit a network reconfiguration request for enabling network communication related to the specific NSI to a network controller, to enable the network controller to reconfigure a network in response to the network reconfiguration request.

[0228] According to various embodiments, the at least one processor can be configured to activate the shared lower-level entity only for an activated set of entities among the higher-level entities, and deactivate the shared lower-level entity for a deactivated set of other entities among the higher-level entities.

[0229] According to various embodiments, the at least one processor can be configured to: receive a deactivation request of the shared lower-level entity as the one or more higher-level entities are deactivated; and in response to the deactivation request, deactivate the shared lower-level entity for the deactivated one or more higher-level entities.

[0230] According to various embodiments, the management node can include an NSSMF for managing an NSSI as a lower-level entity. The at least one processor can be configured to: identify whether NSIs of higher-level entities sharing one NSSI are all deactivated; deactivate the NSSI if the NSIs are all deactivated; and maintain the NSSI in an activated state if the NSIs are not all deactivated.

[0231] According to various embodiments of the disclosure, selective activation and / or deactivation can be implemented in an appropriate manner for a slice entity (or a shared entity) required for a service in a network slice environment of a wireless communication system. Accordingly, time taken to configure necessary slice entities for each network slice can be reduced, and quality of service can be improved, as compared to activating and / or deactivating slice entities as a whole.

[0232] While the disclosure has been shown and described with reference to various example embodiments, it will be understood that the various example embodiments are intended to be illustrative, not limiting. It will be further understood that various changes in form and detail can be made without departing from the true spirit and full scope of the disclosure, including the appended claims and their equivalents. It will also be understood that any one of the embodiments described herein can be used in combination with any other embodiment described herein.

Claims

1. An operation method for a management node in a wireless communication system with a network slicing environment, the method comprising: As one or more of the higher-level entities that share the lower-level entities managed by the management node are activated, the activation request of the shared lower-level entity is received. as well as In response to the activation request, for the one or more higher-level entities that are activated, the shared lower-level entities are activated.

2. The method according to claim 1, wherein, Receiving the activation request includes: Based on the fact that the higher-level entities are managed by different second management nodes, the management node of the one or more higher-level entities that are activated by the management of the second management nodes receives the activation request.

3. The method according to claim 1, wherein, Receiving the activation request includes: The management node manages a multi-level entity system that includes the higher-level entity and the lower-level entity, and detects the occurrence of the activation request within the management node.

4. The method according to claim 1, wherein, The management node includes a Network Slice Subnet Management Function (NSSMF), which is configured to manage Network Slice Subnet Instances (NSSIs), and the NSSIs include the lower-level entities. Receiving the activation request includes: At the NSSMF, the Network Slice Management Function (NSMF), which manages the Network Slice Instance (NSI) as the higher-level entity, receives an activation request for the NSSI of a specific NSI within the NSI. The activation includes: At the NSSMF, for the specific NSI, the NSSI shared by the NSI is partially activated.

5. The method according to claim 4, wherein, At the NSSMF, for the specific NSI, partially activating the NSSI shared by the NSI includes: At the NSSMF, an MF activation request for the specific NSI is sent to the Element Management System (EMS) that manages the managed functions (MFs), so that the EMS can configure some of the MFs as the MFs to be activated for the specific NSI in response to the MF activation request.

6. The method according to claim 4, wherein, At the NSSMF, for the specific NSI, partially activating the NSSI shared by the NSI includes: At the NSSMF, an MF configuration request for the specific NSI is sent to the EMS that manages the MF, so that the EMS can configure the MF for the specific NSI in response to the MF configuration request by missing some of the MFs.

7. The method according to claim 4, wherein, At the NSSMF, for the specific NSI, partially activating the NSSI shared by the NSI includes: At the NSMF, a network reconfiguration request is sent to the network controller to enable network communication associated with the specific NSI, so that the network controller can reconfigure the network in response to the network reconfiguration request.

8. The method according to claim 1, wherein, The activation includes: For the set of activated entities within the higher-level entities, activate the shared lower-level entities; and For other deactivated entity sets among the higher-level entities, the shared lower-level entities are deactivated.

9. The method according to claim 1, further comprising: As one or more of the higher-level entities are deactivated, a deactivation request is received from the shared lower-level entities. as well as In response to the deactivation request, for the one or more higher-level entities that are deactivated, the shared lower-level entities are deactivated.

10. The method according to claim 9, wherein, The management node includes an NSSMF, which manages the NSSI including the lower-level entity. The deactivation includes: At the NSSMF, it is determined whether all NSIs sharing a single NSSI are deactivated. Based on the fact that all NSIs are deactivated, the NSIs are deactivated; and Since not all NSIs are deactivated, the NSIs are kept in an active state.

11. A management node in a wireless communication system with a network slicing environment, the management node comprising: transceiver; as well as At least one processor, the at least one processor including processing circuitry and connected to the transceiver, Wherein, the at least one processor is configured to: As one or more of the higher-level entities that share the lower-level entities managed by the management node are activated, the activation request of the shared lower-level entity is received. and In response to the activation request, for the one or more higher-level entities that are activated, the shared lower-level entities are activated.

12. The management node according to claim 11, wherein, The at least one processor is configured to: Based on the fact that the higher-level entities are managed by different second management nodes, the activation request is received from the management node of the one or more higher-level entities that are activated by the management of the second management nodes.

13. The management node according to claim 11, wherein, The at least one processor is configured to: The management node manages a multi-level entity system that includes the higher-level entity and the lower-level entity, and detects the occurrence of the activation request within the management node.

14. The management node according to claim 11, wherein, The management node includes a Network Slice Subnet Management Function (NSSMF), which is configured to manage Network Slice Subnet Instances (NSSIs), including the lower-level entity. Wherein, the at least one processor is configured to: The Network Slice Management Function (NSMF), which manages the Network Slice Instance (NSI) as the higher-level entity, receives an activation request for the NSSI for a specific NSI within the NSI; and For the specific NSI, the NSSI shared by the NSI is partially activated.

15. The management node according to claim 14, wherein, The at least one processor is configured to: Send an MF activation request for the specific NSI to the Element Management System (EMS) that manages the managed functions (MFs), so that the EMS can configure some of the MFs as the MFs to be activated for the specific NSI in response to the MF activation request.

Images