Management node in wireless communication system having network slicing environment, and operating method therefor

Abstract

A management node in a wireless communication system having a network slicing environment, and an operating method therefor are disclosed. The management node can: receive an activation request of a shared lower level entity according to the activation of one or more from among a plurality of upper level entities sharing the lower level entity; and activate the shared lower level entity with respect to the one or more activated upper level entities in response to the received activation request.

Description

Management node and its operation method in a wireless communication system having a network slicing environment

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

[0002] 5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in the sub-6GHz frequency band such as 3.5 gigahertz (3.5GHz), but also in the ultra-high frequency band called millimeter wave (mmWave) such as 28GHz and 39GHz ('Above 6GHz'). In addition, for 6G mobile communication technology, which is called the system after 5G communication (Beyond 5G), implementation in the terahertz band (for example, the 3 terahertz (3THz) band at 95GHz) is being considered to achieve a transmission speed that is 50 times faster than 5G mobile communication technology and an ultra-low latency time that is reduced to one-tenth.

[0003] In the early stages of 5G mobile communication technology, the goal is to support services and meet performance requirements for enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC). These include beamforming and massive MIMO to mitigate path loss of radio waves in ultra-high frequency bands and increase the transmission distance of radio waves, support for various numerologies (such as operation of multiple subcarrier intervals) and dynamic operation of slot formats for efficient use of ultra-high frequency resources, initial access technology to support multi-beam transmission and wideband, definition and operation of BWP (Bidth Part), new channel coding methods such as LDPC (Low Density Parity Check) codes for large-capacity data transmission and Polar Code for reliable transmission of control information, and L2 pre-processing (L2). Standardization has been made for network slicing, which provides dedicated networks specialized for specific services, and pre-processing.

[0004] Currently, discussions are underway to improve and enhance the initial 5G mobile communication technology in consideration of the services that 5G mobile communication technology was intended to support, and physical layer standardization is in progress for technologies such as V2X (Vehicle-to-Everything) to help autonomous vehicles make driving decisions and increase user convenience based on their own location and status information transmitted by vehicles, NR-U (New Radio Unlicensed) for the purpose of system operation that complies with various regulatory requirements in unlicensed bands, NR terminal low power consumption technology (UE Power Saving), Non-Terrestrial Network (NTN), which is direct terminal-satellite communication to secure coverage in areas where communication with terrestrial networks is impossible, and Positioning.

[0005] In addition, standardization of wireless interface architecture / protocols is in progress for technologies such as intelligent factories (Industrial Internet of Things, IIoT) to support new services through linkage and convergence with other industries, Integrated Access and Backhaul (IAB) that provides nodes for expanding network service areas by integrating wireless backhaul links and access links, Mobility Enhancement technology including Conditional Handover and Dual Active Protocol Stack (DAPS) handover, and 2-step random access (2-step RACH for NR) that simplifies random access procedures. Standardization is also in progress for system architecture / services such as 5G baseline architecture (e.g., Service-based Architecture, Service-based Interface) for grafting Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) that provides services based on the location of the terminal.

[0006] Once these 5G mobile communication systems are commercialized, an explosive increase in connected devices will be connected to the communication network, necessitating enhanced functionality and performance of 5G mobile communication systems and integrated operation of these connected devices. To this end, new research will be conducted on improving 5G performance and reducing complexity, supporting AI services, supporting metaverse services, and drone communications by utilizing eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).

[0007] In addition, the development of these 5G mobile communication systems includes new waveforms to ensure coverage in the terahertz band of 6G mobile communication technology, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), Array Antenna, and Large Scale Antenna, metamaterial-based lenses and antennas to improve the coverage of terahertz band signals, high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM), Reconfigurable Intelligent Surface (RIS) technology, as well as full duplex technology to improve the frequency efficiency and system network of 6G mobile communication technology, satellite, AI (Artificial Intelligence) from the design stage and AI-based communication technology that realizes system optimization by internalizing end-to-end AI support functions, and ultra-high-performance communication and computing resources to provide services with complexity that exceeds the limits of terminal computing capabilities. It can serve as a basis for the development of next-generation distributed computing technologies that can be realized by utilizing them.

[0008] In wireless communication systems, such as 5G mobile communication systems, network slicing can be a network architecture that enables multiple virtualized, independent logical networks within the same physical network infrastructure. Each network slice (or subnet) can represent an isolated, end-to-end network tailored to meet the diverse requirements of specific applications. Network slicing technology allows multiple virtualized logical networks to exist within a single physical network.

[0009] Various embodiments of the present disclosure may provide a method of operating a management node. In one embodiment, the method may be a method of operating a management node in a wireless communication system having a network slicing environment. The method may include receiving an activation request for a shared lower-level entity among a plurality of higher-level entities that share a lower-level entity managed by the management node, when one or more of the shared lower-level entities are activated, and activating the shared lower-level entity for the one or more activated higher-level entities in response to the activation request.

[0010] Various embodiments of the present disclosure may provide a management node. According to one embodiment, the management node may be a management node in a wireless communication system having a network slicing environment. The management node may include a transceiver and at least one processor connected to the transceiver. The at least one processor may be configured to receive an activation request for a shared lower-level entity among a plurality of higher-level entities that share the lower-level entity managed by the management node when one or more of the shared higher-level entities are activated, and in response to the activation request, activate the shared lower-level entity for the one or more activated higher-level entities.

[0011] Aspects, features and advantages of embodiments of the present disclosure will become more apparent from the following detailed description taken in conjunction with the accompanying drawings.

[0012] FIG. 1 illustrates a communication network including network entities in a wireless communication system according to various embodiments.

[0013] FIG. 2a is a diagram illustrating the sharing of network slice instances (NSIs) and network slice subnet instances (NSSIs) in a wireless communication system according to one embodiment.

[0014] FIG. 2b illustrates the configuration of a management node in a wireless communication system according to one embodiment.

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

[0016] FIGS. 4A and 4B are diagrams for explaining a selective activation operation of a shared entity in a wireless communication system according to one embodiment.

[0017] FIGS. 5A and 5B are diagrams illustrating a selective deactivation operation of a shared entity in a wireless communication system according to one embodiment.

[0018] FIGS. 6A and 6B are flowcharts illustrating selective activation operations of a network slice subnet instance (NSSI) shared by multiple network slice instances (NSIs) in a wireless communication system according to one embodiment.

[0019] FIG. 7A is a flowchart illustrating an operation of selectively activating a shared entity when upper-level entities are managed by different management systems in a wireless communication system according to one embodiment.

[0020] FIG. 7b is a flowchart illustrating an operation of selectively activating a shared entity when multiple level entities are managed by a single management system in a wireless communication system according to one embodiment.

[0021] FIG. 8a is a flowchart illustrating a selective activation operation of MFs (managed functions) by a switching technique supported by an EMS (element management system) in a wireless communication system according to one embodiment.

[0022] FIG. 8b is a flowchart illustrating a selective deactivation operation of MFs by a switching technique supported by an EMS in a wireless communication system according to one embodiment.

[0023] FIG. 9a is a flowchart illustrating a selective activation operation of MFs by a completing configuration technique in a wireless communication system according to one embodiment.

[0024] FIG. 9b is a flowchart illustrating a selective deactivation operation of MFs by a configuration completion technique in a wireless communication system according to one embodiment.

[0025] FIG. 10a is a flowchart illustrating a selective activation operation of NSSI or MFs by a network communication blocking and unblocking technique in a wireless communication system according to one embodiment.

[0026] FIG. 10b is a flowchart illustrating a selective deactivation operation of NSSI or MFs by a network communication blocking and unblocking technique in a wireless communication system according to one embodiment.

[0027] FIG. 11a and FIG. 11b are drawings for explaining a selective deactivation operation of a network slice subnet instance (NSSI) by a consensus technique of a network slice management function (NSMF) in a wireless communication system according to one embodiment.

[0028] It should be understood that the various embodiments of the present disclosure and the terminology used therein are not intended to limit the technical features described in the present disclosure to specific embodiments, but include various modifications, equivalents, or alternatives of the embodiments.

[0029] Methods according to various embodiments of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software. If implemented in software, a computer-readable storage medium storing one or more programs (software modules) may be provided. The one or more programs stored in the computer-readable storage medium are configured for execution by one or more processors within an electronic device. The one or more programs include instructions that cause the electronic device to execute methods according to embodiments described in the claims or specification of the present disclosure.

[0030] These programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, read only memory (ROM), electrically erasable programmable read only memory (EEPROM), magnetic disc storage devices, compact disc-ROMs (CD-ROMs), digital versatile discs (DVDs) or other forms of optical storage devices, magnetic cassettes, or may be stored in memories formed by a combination of some or all of these. In addition, each configuration memory may include multiple copies.

[0031] Additionally, the program may be stored on an attachable storage device that is accessible via a communication network, such as the Internet, an intranet, a local area network (LAN), a wide area network (WAN), a storage area network (SAN), or a combination thereof. Such a storage device may be connected to a device implementing an embodiment of the present disclosure via an external port. Additionally, a separate storage device on the communication network may be connected to a device implementing an embodiment of the present disclosure.

[0032] In various embodiments of the present disclosure, components are expressed singularly or plurally, depending on the specific embodiments presented. However, the singular or plural expressions are selected to suit the presented situation for convenience of explanation, and the present disclosure is not limited to singular or plural components. Components expressed plurally may be composed of singular elements, or components expressed singularly may be composed of plural elements.

[0033] The terms used in the following description, including terms referring to signals, channels, control information, network entities, and device components, are provided for convenience of explanation. Therefore, the present disclosure is not limited to the terms described below, and other terms with equivalent technical meanings may be used.

[0034] Additionally, while this disclosure describes various embodiments using terminology used in certain communication standards (e.g., 3rd generation partnership project (3GPP)), these are merely illustrative examples. The various embodiments of this disclosure can be easily modified and applied to other communication systems.

[0035] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings so that those skilled in the art can easily implement the present disclosure. However, the present disclosure may be implemented in various different forms and is not limited to the embodiments described herein. In connection with the description of the drawings, the same or similar reference numerals may be used for identical or similar components. Furthermore, in the drawings and related descriptions, descriptions of well-known functions and configurations may be omitted for clarity and conciseness.

[0036] FIG. 1 illustrates a communication network including network entities in a wireless communication system according to various embodiments.

[0037] Referring to FIG. 1, a 5G mobile communication network of a wireless communication system (100) may include a user equipment (UE) (e.g., including a terminal) (110), a radio access network (RAN) (120), and a core network (CN).

[0038] The core network is a network that manages the entire system, controls the RAN (120), and can process data and control signals for the UE (110) transmitted and received through the RAN (120). The core network can perform various functions, such as controlling the user plane and the control plane, processing mobility, managing subscriber information, billing, and interworking with other types of systems (e.g., long term evolution (LTE) systems). In order to perform the various functions described above, the core network can include multiple functionally separated entities having different network functions (NFs).

[0039] The core network may be configured to include network functions such as an access and mobility management function (AMF) (150) that provides a mobility management function of a UE, a session management function (SMF) (160) that provides a session management function, a user plane function (UPF) (170) that performs a data transfer role, a policy control function (PCF) (180) that provides a policy control function, a unified data management (UDM) (153) that provides a data management function such as subscriber data and 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 of various network functions. Although not illustrated in FIG. 1, the core network may further include a communication service management function (CSMF), a network slice management function (NSMF), and a network slice subnet management function (NSSMF) for creating a network slice and verifying a user service.

[0040] Referring to FIG. 1, a user equipment (UE) (110) may communicate with a base station (e.g., an eNB, a gNB) via a wireless channel, i.e., an access network. In some embodiments, the UE (110) may be a device used by a user and configured to provide a user interface (UI). As an example, the UE (110) may be a terminal mounted (equipment) on a vehicle for driving. In some other embodiments, the UE (110) may be a device that performs machine type communication (MTC) that operates without user intervention, or may be an autonomous vehicle. UE may be referred to as a 'terminal', 'vehicle terminal', 'user equipment (UE)', 'mobile station', 'subscriber station', 'remote terminal', 'wireless terminal', or 'user device' or other terms having equivalent technical meanings, other than electronic devices. As the terminal, in addition to the UE, a customer-premises equipment (CPE) or a dongle-type terminal may be used. The CPE, while connected to the NG-RAN node like the UE, may also provide a network to other communication devices (e.g., a laptop).

[0041] Referring to FIG. 1, the AMF (150) provides a function for connection and mobility management per terminal (110), and basically, one AMF (150) can be connected to one terminal (110). Specifically, the AMF (150) can perform at least one of signaling between core network nodes for mobility between 3GPP access networks, an interface (N2 interface) between wireless access networks (e.g., RAN (120)), NAS signaling with the terminal (110), identification of the SMF (160), and provision of transmission of session management (SM) messages between the terminal (110) and the SMF (160). Some or all of the functions of the AMF (150) can be supported within a single instance of one AMF (150).

[0042] Referring to FIG. 1, the SMF (160) provides a session management function, and when the terminal (110) has multiple sessions, each session may be managed by a different SMF (160). Specifically, the SMF (160) may perform at least one of the following functions: session management (e.g., session establishment, modification, and release, including tunnel maintenance between the UPF (170) and the access network node), selection and control of UP (user plane) functions, traffic steering setup for routing traffic to an appropriate destination in the UPF (170), termination of the SM portion of NAS messages, downlink data notification (DDN), and initiation of AN-specific SM information (e.g., delivery to the access network via the N2 interface via the AMF (150)). Some or all of the functions of the SMF (160) may be supported within a single instance of one SMF (160).

[0043] In the 3GPP system, the conceptual links connecting network functions (NFs) within a 5G system can be referred to as reference points. Reference points can also be referred to as interfaces. The following illustrates reference points included in the 5G system architecture depicted in Figures 1 through 11b.

[0044] - N1: Reference point between UE (110) and AMF (150)

[0045] - N2: Reference point between (R)AN(120) and AMF(150)

[0046] - N3: Reference point between (R)AN(120) and UPF(170)

[0047] - N4: Reference point between SMF (160) and UPF (170)

[0048] - N5: Reference point between PCF (180) and AF (130)

[0049] - N6: Reference point between UPF (170) and DN (140)

[0050] - N7: Reference point between SMF (160) and PCF (180)

[0051] - N8: Reference point between UDM (153) and AMF (150)

[0052] - N9: Reference point between two core UPFs (170)

[0053] - N10: Reference point between UDM (153) and SMF (160)

[0054] - N11: Reference point between AMF (150) and SMF (160)

[0055] - N12: Reference point between AMF (150) and authentication server function (AUSF) (151)

[0056] - N13: Reference point between UDM (153) and authentication server function (151)

[0057] - N14: Reference point between two AMFs (150)

[0058] - N15: For non-roaming scenarios, reference point between PCF (180) and AMF (150), for roaming scenarios, reference point between PCF (180) and AMF (150) within the visited network.

[0059] - N22: Reference point between NSSF (190) and AMF (150)

[0060] FIG. 2a is a diagram illustrating the sharing of network slice instances (NSIs) and network slice subnet instances (NSSIs) in a wireless communication system according to one embodiment.

[0061] According to various embodiments, by applying network slicing technology to a wireless communication system (e.g., a 5G mobile communication network of FIG. 1) including a radio access network (RAN) (120) and a core network (CN) (200), multiple logical networks can be spawned on a single shared infrastructure, and each logical network can be given unique characteristics tailored to specific service requirements. In a network slicing environment, slicing entities, which are components of a network slice, can be shared with each other. Instead of deploying dedicated managed entities for each new network, a single instance of a managed entity can be used simultaneously across multiple logical networks, called a network slice.

[0062] According to various embodiments, in a wireless communication system having a network slicing environment, a slicing entity or a managed entity (e.g., a network slice subnet instance (NSSI), a network slice instance (NSI), or a managed function (MF)) may have shareability. For example, one NSSI (e.g., any one of NSSI 1, NSSI 2, and NSSI 3 in FIG. 2A) may be shared among multiple NSIs (e.g., at least some of NSI A, NSI B, and NSI C in FIG. 2A) or other nested NSSIs. One NSI may also be shared among multiple CSIs (communication service instances). One MF may also be shared among multiple NSSIs.

[0063] According to one embodiment, managed functions (MFs) may represent logical applications running within virtual network functions (VNFs) / physical network functions (PNFs) / container network functions (CNFs). MFs may perform a predefined set of functions and communicate with each other through standard interfaces called reference points. Creating a network slice may mean spawning new instances of slice-dedicated MFs and reusing MFs that may be shared between multiple slices. For example, dedicated MFs may correspond to SMFs (160) or UPFs (170) illustrated in FIG. 1. For example, shared MFs may correspond to any one of UDMs (153), AMFs (150), NSSFs (190), or NRFs (not illustrated, network repository function) illustrated in FIG. 1.

[0064] FIG. 2b illustrates the configuration of a management node in a wireless communication system according to one embodiment.

[0065] According to one embodiment, the management node (201) may be a device or function that manages one or more slicing entities. The management node (201) may also be referred to as a management entity, a management system, or a management function. In one embodiment, the management node (201) may include a device or function that manages a lower-level entity among multi-level entities (higher-level entities and lower-level entities) included in a wireless communication system. For example, the management node (201) may include a function or device corresponding to at least one of a communication service management function (CSMF), a network slice management function (NSMF), and a network slice subnet management function (NSSMF). Terms such as '... unit', '... device', etc. used hereinafter mean a unit that processes at least one function or operation, and this may be implemented by hardware, software, or a combination of hardware and software.

[0066] Referring to FIG. 2b, a management node (201) according to one embodiment may include a communication unit (e.g., including communication circuitry) (210) and a control unit (e.g., including processing / control circuitry) (220). In one embodiment, the management node (201) may further include a storage unit (230).

[0067] In one embodiment, the communication unit (210) may provide an interface for communicating with other devices within the network. For example, the communication unit (210) may convert a bit string transmitted from the management node (201) to another device (or an external electronic device) into a physical signal, and may convert a physical signal received from another device into a bit string. In one embodiment, the communication unit (210) may transmit and receive signals. Accordingly, the communication unit (210) may be referred to as a modem, a transmitter, a receiver, or a transceiver. The communication unit (210) may support the management node (201) to communicate with other devices or systems via a backhaul connection (e.g., a wired backhaul or a wireless backhaul) or via a network.

[0068] In one embodiment, the storage unit (230) may store data such as basic programs, application programs, and setting information for the operation of the management node (201). The storage unit (230) may be configured as volatile memory, non-volatile memory, or a combination of volatile memory and non-volatile memory. The storage unit (230) may provide stored data upon request from the control unit (220).

[0069] In one embodiment, the control unit (220) may include at least one processor electrically and / or operatively connected to the communication unit (210). A processor according to one embodiment of the present disclosure may include various processing circuits. For example, terms such as "processor," "control unit," etc., used in this disclosure, including the claims, may include various processing circuits including at least one processor, wherein at least one of the at least one processor may be configured to perform various functions described in the present disclosure. Furthermore, the at least one processor may include a combination of processors that perform various functions cited / disclosed. The at least one processor may execute program instructions to achieve or perform various functions. The control unit (220) may control the overall operations of the management node (201). For example, the control unit (220) may transmit and receive signals via the communication unit (210). Furthermore, the control unit (220) may write data to or read data 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).

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

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

[0072] In one embodiment, when multi-level entities including upper-level entities (e.g., first entity and second entity) and lower-level entities (e.g., third entity) are solely managed by the management node (201), the control unit (220) can internally detect the occurrence of an activation request.

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

[0074] According to one embodiment, the management node (201) may include a network slice subnet management function (NSSMF) that manages a network slice subnet instance (NSSI), which is a lower-level entity. The NSSMF may receive an activation request for a specific NSI among the network slice instances (NSIs) from the network slice management function (NSMF) that manages the network slice instances (NSIs), which are higher-level entities. The NSSMF may partially activate the NSSI shared by the NSIs only for the specific NSI.

[0075] In one embodiment, the NSSMF may transmit an MF activation request for the particular NSI to an element management system (EMS) node that manages managed functions (MFs), such that the EMS may, in response to the MF activation request, configure some of the MFs as MFs to be activated for the particular NSI.

[0076] In one embodiment, the NSSMF may send an MF configuration request for the particular NSI to an EMS that manages MFs, such that the EMS may configure the MF for the particular NSI by omitting some of the MFs in response to the MF configuration request.

[0077] In one embodiment, the NSSMF may transmit a network reconfiguration request to the network controller to enable network communications associated with the particular NSI, such that the network controller may reconfigure the network in response to the network reconfiguration request.

[0078] In one embodiment, NSSMF may enable lower-level entities (e.g., NSSI) shared by upper-level entities only for a set of enabled entities (e.g., NSI 1) among the upper-level entities (e.g., NSI 1, NSI2). NSSMF may disable lower-level entities (e.g., NSSI) shared by the upper-level entities for a set of disabled entities (e.g., NSI 2) among the upper-level entities (e.g., NSI 1, NSI2).

[0079] According to one embodiment, the control unit (220) of the management node (201) may be configured to receive a deactivation request of a shared lower-level entity (e.g., a third entity) when one or more of the upper-level entities (e.g., a first entity and a second entity) are deactivated (e.g., the first entity). In response to the deactivation request, the control unit (220) may be configured to deactivate the shared lower-level entity (e.g., the third entity) for the one or more upper-level entities (e.g., the first entity) that are deactivated.

[0080] In one embodiment, the management node (201) may include an NSSMF that manages an NSSI, which is a shared lower-level entity. In one embodiment, the NSSMF may identify whether all NSIs, which are upper-level entities sharing an NSSI, are inactive. If all NSIs, which are upper-level entities sharing an NSSI, which is a shared lower-level entity, are inactive, the NSSMF may deactivate the NSSI, and if not all NSIs sharing the NSSI are inactive, the NSSMF may keep the NSSI in an active state.

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

[0082] The operations of the method illustrated in FIG. 3 may be performed by any one of the management node (201) of FIG. 2b, for example, the N-level management system (401) of FIG. 4b, which will be described later, the NSSMF (601) of FIG. 6b, the NSSMF (701) of FIG. 7a, the management function (705) of FIG. 7b, the NSSMF (801) of FIG. 8a, the NSSMF (1001) of FIG. 10a, and the NSSMF (1101) of FIG. 11b. However, the present invention is not limited thereto. For example, the operations of the method illustrated in FIG. 3 may be performed by a combination of one or more devices or functions. The performing entity of the method illustrated in FIG. 3 is not limited to hardware components. It may be implemented by hardware, software, or a combination of hardware and software. For example, in some embodiments, the method may be performed by an application installed on the management node (201).

[0083] Referring to FIG. 3, the operating method of the management node in the wireless communication system may include operations 310 and 320.

[0084] According to one embodiment, a core network of a wireless communication system may include various multi-level entities, for example, entity_1, entity_2, and entity_3. Entity_1, entity_2, or entity_3 may correspond to slicing entities operating in a network slicing environment. At least some of entity_1, entity_2, and entity_3 may be entities of different levels. For example, entity_1 and entity_2 may be higher level (or higher layer, e.g., level N+1) entities compared to entity_3. Entity_3 may be lower level (or lower layer, e.g., level N) entities compared to entity_1.

[0085] According to one embodiment, the core network of a wireless communication system may include a management node (201). In one embodiment, the management node (201) may be a first management node that manages a lower-level entity, Entity_3. For example, the first management node may include at least one of the N-level management system (401) of FIG. 4b or the NSSMF (601) of FIG. 6b.

[0086] Operation 310 may include receiving an activation request of a shared lower-level entity (e.g., entity_3). In operation 310, the management node (201) (e.g., the control unit (220) of FIG. 2B ) may receive an activation request of the shared lower-level entity (e.g., entity_3) when one or more (e.g., entity_1) of a plurality of upper-level entities (e.g., entity_1, entity_2) that share the lower-level entity (e.g., entity_3) managed by the management node (201) is activated.

[0087] In one embodiment, when upper 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) may receive an activation request from a management node (e.g., one of the N+1 level management system (402) of FIG. 4b or the NSMF (602) of FIG. 6b) that manages one or more activated upper level entities (e.g., Entity_1, NSI 1) among the second management nodes.

[0088] In one embodiment, when multi-level entities including upper-level entities and lower-level entities are managed by one management node (201), the management node (201) can internally detect the occurrence of an activation request in the management node (201).

[0089] Action 320 may include an action of selectively activating a shared lower-level entity (e.g., entity_3). In action 320, the management node (201) (e.g., the control unit (220) of FIG. 2B ) may activate the shared lower-level entity (e.g., entity_3) in response to the activation request received via action 310.

[0090] In one embodiment, the management node (201) may selectively (or partially) activate only a specific entity (e.g., Entity_1) among the higher-level entities that share a lower-level entity (e.g., Entity_3). For example, rather than binary activation of the entire Entity_3 shared by multiple higher-level entities (e.g., Entity_1, Entity_2), selective (or partial) activation and / or deactivation of Entity_3 for a specific higher-level entity (e.g., Entity_1) may be implemented.

[0091] In one embodiment, the management node (201) may allow a slicing 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 may be performed only for a specific upper-level entity among the upper-level entities, rather than for all upper-level entities that share the lower-level entity.

[0092] According to one embodiment, the management node (201) may directly control the activation and / or deactivation of a slicing entity (e.g., a lower-level entity), or may induce the activation and / or deactivation of a slicing entity through selective activation and / or deactivation of a network function (or a management function).

[0093] According to one embodiment, a method may be provided for performing deactivation of a shared lower-level entity managed by a management node (201). For example, a lower-level entity may be deactivated only if all higher-level entities sharing the lower-level entity are expected to be deactivated. In this method, NSSI is presented as an example of a shared lower-level entity.

[0094] In one embodiment, upper-level entities (e.g., Entity_1, Entity_2) may be managed by a plurality of different second management nodes (e.g., the embodiment of FIG. 7A). When upper-level entities (e.g., Entity_1, Entity_2) are managed by a plurality of different second management nodes, the activation request receiving operation 310 may include receiving an activation request of a shared lower-level entity (e.g., Entity_3) from a management node that manages one or more of the activated upper-level entities (e.g., Entity_1) among the second management nodes.

[0095] In one embodiment, multi-level entities including upper-level entities (e.g., Entity_1, Entity_2) and lower-level entities (e.g., Entity_3) may be managed by the same single management node (201) (e.g., the embodiment of FIG. 7b). In the case where multi-level entities are solely managed by a single management node (201), the activation request receiving operation 310 may internally detect the occurrence of the activation request in the management node (201).

[0096] According to one embodiment, the management node (201) may include an NSSMF that manages an NSSI, which is a shared lower-level entity (e.g., entity_3). The selective activation operation 320 of the shared lower-level entity may include an operation in which the NSSMF receives an activation request for a specific NSI (e.g., NSI 1) among the NSIs from an NSMF that manages the NSIs, which are higher-level entities (e.g., the embodiments of FIGS. 6A and 6B ). In addition, the selective activation operation 320 of the shared lower-level entity may include an NSSI selective activation operation. The NSSI selective activation operation may be an operation in which the NSSMF selectively (or partially) activates the NSSI shared by the NSIs only for a specific NSI (e.g., NSI 1 corresponding to entity 1).

[0097] In one embodiment, the selective activation operation 320 of a shared lower-level entity (e.g., entity_3) may include a selective activation operation of MFs by a switching technique of an EMS (e.g., the embodiment of FIG. 8A). An NSSMF corresponding to a management node (201) may transmit an MF activation request for a specific NSI to an EMS (element management system) node that manages MFs (managed functions), so that the EMS may, in response to the MF activation request, configure some of the MFs as MFs to be activated for the specific NSI.

[0098] In one embodiment, the selective activation operation 320 of a shared lower-level entity (e.g., entity_3) may include a selective activation operation of MFs by a configuration completion technique (e.g., the embodiment of FIG. 9a). The NSSMF corresponding to the management node (201) may transmit an MF configuration request for a specific NSI to the EMS managing the MFs, so that the EMS may configure an MF for the specific NSI by omitting some of the MFs in response to the MF configuration request.

[0099] In one embodiment, the selective activation operation 320 of a shared lower-level entity (e.g., entity_3) may include a selective activation operation of NSSI or MFs by a network communication blocking or unblocking technique (e.g., the embodiment of FIG. 10a). The NSSMF corresponding to the management node (201) may transmit a network reconfiguration request to the network controller to enable network communication related to a specific NSI, thereby causing the network controller to reconfigure the network in response to the network reconfiguration request.

[0100] According to one embodiment, the selective activation operation 320 of a shared lower-level entity (e.g., entity_3) may include an operation of activating the shared lower-level entity (e.g., entity_3) only for a set of activated entities (e.g., first entity) among higher-level entities sharing the lower-level entity, and an operation of deactivating the shared lower-level entity (e.g., entity_3) for a set of deactivated entities (e.g., entity_2) among the higher-level entities.

[0101] According to one embodiment, a method of operating a management node in a wireless communication system may include receiving a deactivation request of a shared lower-level entity (e.g., entity_3), and deactivating the shared lower-level entity (e.g., entity_3) in response to the deactivation request. The management node (201) may receive a deactivation request of a lower-level entity (e.g., a third entity) shared by the higher-level entities when one or more of the higher-level entities (e.g., a first entity and a second entity) are deactivated (e.g., the first entity). The management node (201) may be configured to selectively (or partially) deactivate the shared lower-level entity (e.g., the third entity) for one or more of the deactivated higher-level entities (e.g., the first entity), in response to the deactivation request.

[0102] In one embodiment, the management node (201) may include an NSSMF that manages an NSSI, which is a shared lower-level entity. In one embodiment, the NSSMF may identify whether all NSIs, which are upper-level entities sharing an NSSI, are inactive. If all NSIs, which are upper-level entities sharing an NSSI, which is a shared lower-level entity, are inactive, the NSSMF may deactivate the NSSI, and if not all NSIs sharing the NSSI are inactive, the NSSMF may keep the NSSI in an active state (e.g., the embodiments of FIGS. 11A and 11B ).

[0103]

[0104] Hereinafter, with reference to the drawings, operations for selectively activating and / or deactivating entities at different levels in a network slicing environment of a wireless communication system according to various embodiments are described. The illustrated operations may be performed sequentially, but are not necessarily sequential. For example, the order of the operations may be changed, and at least two operations may be performed in parallel.

[0105] At least some of the operations for selectively activating and / or deactivating entities at different levels according to the various embodiments described below may be performed in correspondence with or in combination with each other. In some embodiments, at least one of the illustrated operations may be omitted, the order of some operations may be changed, or other operations may be added.

[0106] FIGS. 4A and 4B are diagrams for explaining a selective activation operation of a shared entity in a wireless communication system according to one embodiment.

[0107] Referring to FIG. 4A, a core network of a 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 N level entity. Entity_1 (411) and entity_2 (412) may have sharing rights to entity_3 (413). Entity_3 (413) may be an entity shared by entity_1 (411) and entity_2 (412). Entity_3 (413) may include two or more constituents (414). For example, each component (414) of entity_3 (413) means a unit that processes at least one function or operation, and can be implemented by hardware, software, or a combination of hardware and software.

[0108] The first state (405) of Fig. 4a may be a state in which entity_1 (411), entity_2 (412), and the shared entity entity_3 (413) are all inactive. When entity_1 (411) is switched to active, selective activation of entity_3 (413) may be entailed. Accordingly, the first state (405) may be switched to a second state (406). In the second state (406), entity_1 (411) may be switched to an active state, and entity_2 (412) may remain in an inactive state. In the second state (406), the shared entity_3 (413) may be selectively (or partially) activated, such that it may be activated only for entity_1 (411) and continue to be inactive for entity_2 (412).

[0109] According to one embodiment, each entity (411, 412, 413) can be managed by a management system of the corresponding level. For example, entity_1 (411) and entity_2 (412), which are N+1 level entities, can be managed by the N+1 level management system (402) illustrated in FIG. 4b. Entity_3, which is an N level entity shared by N+1 level entities, can be managed by the N level management system (401) illustrated in FIG. 4b.

[0110] Referring to FIG. 4b, the selective activation operation of the shared entity, entity_3 (413), may include operation 410, operation 420, and operation 430.

[0111] According to one embodiment, the management node (201) of FIG. 2b may include an N-level management system (401) of FIG. 4b. The N-level management system (401) may interact with an N+1-level management system (402) to perform a selective activation operation of the shared entity_3.

[0112] In one embodiment, entity_1 (411), entity_2 (412), and entity_3 (413) may be in a deactivated state (e.g., the first state (405) of FIG. 4A). For example, entity_1 (411), entity_2 (412), and entity_3 (413) may have already been instantiated and provisioned, but may be in a state (deactivated state) in which they cannot serve users.

[0113] For example, a user's UE (110) may be simultaneously connected to one or more network slice instances via a radio access network (RAN) (120) depending on the service being provided. When the UE (110) transmits the user's service requirement information requested by the UE (110) to the core network (CN) (200) in order to receive a service from a specific network slice instance, the core network (200) may select an appropriate network slice instance based on the transmitted information. As the network slice instance is selected, the management system (401, 402) of the core network (200) may perform instantiation and provisioning of the corresponding entities, and allocate, arrange, or distribute resources according to the user's service requirement information to prepare them for immediate use. Even if the entities are instantiated and provisioned, they may be in a state where service provision to the user is impossible (e.g., link blocking state) before activation. After entities are instantiated and provisioned, they can be activated and brought into a state where they can provide services to users (e.g., a linked state).

[0114] In operation 410, the N+1 level management system (402) may transmit an activation request of entity_3 (413) for entity_1 (411) to the N level management system (401).

[0115] In operation 420, the N-level management system (401) may perform selective activation of entity_3 (413) in response to the activation request received through operation 410. By performing activation of entity_3 (413) for entity_1 (411), the N-level management system (401) may selectively (or partially) activate only some components related to entity_1 (411) among entity_3 components (414), and keep the remaining components in a deactivated state.

[0116] In operation 430, the N level management system (401) may transmit an OK response to the activation request of operation 410 to the N+1 level management system (402).

[0117] By performing the activation of entity_3(413) for entity_1(411) through operation 430, entity_3(413) shared by entity_1(411) and entity_2(412) can be selectively activated only for entity_1(411) (e.g., the second state (406) of FIG. 4a). Accordingly, entity_1(411) can be switched to the activated state, and entity_2(413) can be maintained in the deactivated state (e.g., the second state (406) of FIG. 4a).

[0118] FIGS. 5A and 5B are diagrams illustrating a selective deactivation operation of a shared entity in a wireless communication system according to one embodiment.

[0119] In the first state (505) of FIG. 5A, entity_1 (411), entity_2 (412), and a shared entity entity_3 (413) may be activated. When entity_1 (411) is transitioned to inactive, selective deactivation of entity_3 (413) may follow. Accordingly, the first state (505) may transition to a second state (506). In the second state (506), entity_1 (411) may transition to a inactive state, and entity_2 (412) may remain activated. In the second state (506), the shared entity_3 (413) may be selectively (or partially) deactivated, such that it may be deactivated only for entity_1 (411) and continue to be activated for entity_2 (413).

[0120] According to one embodiment, the management node (201) may include an N-level management system (401) of FIG. 5B. The N-level management system (401) may interact with an N+1-level management system (402) to perform a selective deactivation operation of the shared entity_3 (413).

[0121] Referring to FIG. 5b, the selective deactivation operation of the shared entity, entity_3 (413), may include operation 510, operation 520, and operation 530.

[0122] In one embodiment, Entity_1 (411) and Entity_2 (412) may be activated, and the shared Entity_3 (413) may be globally activated for both Entity_1 (411) and Entity_2 (412) (e.g., the first state (505) of FIG. 5A). For example, Entity_1 (411), Entity_2 (412), and Entity_3 (413) may all already be instantiated and provisioned, and are providing services to users.

[0123] In operation 510, the N+1 level management system (402) may transmit a deactivation request of entity_3 (413) to entity_1 (411) to the N level management system (401).

[0124] In operation 520, the N-level management system (401) may perform selective deactivation of entity_3 (413) in response to the deactivation request received through operation 510. By performing deactivation of entity_3 (413) for entity_1 (411), the N-level management system (401) may selectively (or partially) deactivate only some components related to entity_1 (411) among the components of entity_3 (413), and maintain the remaining components in an activated state.

[0125] In operation 530, the N level management system (401) may transmit an OK response to the deactivation request of operation 510 to the N+1 level management system (402).

[0126] By performing deactivation of entity_3(413) for entity_1(411) through operation 530, entity_3(413) shared by entity_1(411) and entity_2(412) can be selectively deactivated only for entity_1(411) (e.g., second state (506) of Fig. 5a). Accordingly, entity_1(411) can be switched to a deactivated state, and entity_2(413) can be maintained in an activated state (e.g., second state (506) of Fig. 5a).

[0127] FIGS. 6A and 6B are flowcharts illustrating selective activation operations of a network slice subnet instance (NSSI) shared by multiple network slice instances (NSIs) in a wireless communication system according to one embodiment.

[0128] The embodiments of FIGS. 6A and 6B may be applications of the embodiments of FIGS. 4A and 4B to concretized entities. For example, NSI 1 (611), NSI 2 (612), shared NSSI (613), and NSSI component (614) of FIG. 6A may correspond to Entity_1 (411) (upper level entity), Entity_2 (412) (upper level entity), shared Entity_3 (413) (lower level entity), and Entity_3 component (414) (component of lower level entity) of FIG. 4A, respectively. The network slice management function (NSMF) (602) illustrated in FIG. 6b is a device that manages upper-level NSI 1 (611) and NSI 2 (612), and may correspond to the N+1 level management system (402) of FIG. 4a. The network slice subnet management function (NSSMF) (601) illustrated in FIG. 6b is a device that manages lower-level shared NSSMF (602), and may correspond to the N level management system (401) of FIG. 4a. Operations 610, 620, and 630 illustrated in FIG. 6b may correspond to operations 410, 420, and 430 of FIG. 4a, respectively.

[0129] In the first state (605) of FIG. 6A, NSI 1 (611), NSI 2 (612), and the shared NSSI (613) may be deactivated. When NSI 1 (611) transitions to activation, selective activation of the shared NSSI (613) may be accompanied. Accordingly, the first state (605) may transition to the second state (606). In the second state (606), NSI 1 (611) may transition to the activated state, and NSI 2 (612) may remain in the deactivated state. In the second state (606), the shared NSSI (613) may be selectively (or partially) activated, such that it may be activated only for NSI 1 (611) and remain deactivated for NSI 2 (613).

[0130] Referring to FIG. 6b, the selective activation operation of the shared NSSI (613) may include operation 610, operation 620, and operation 630.

[0131] In one embodiment, NSI 1 (611), NSI 2 (612), and NSSI (613) may be in a disabled state (e.g., the first state (605) of FIG. 6A). For example, NSI 1 (611), NSI 2 (612), and NSSI (613) may have already been instantiated and provisioned, but may be in a state (disabled state) in which they cannot provide services to users.

[0132] In operation 610, the NSMF (602) managing NSI 1 (611) and NSI 2 (612) may send an activation request of NSSI (613) for NSI 1 (611) to the NSSMF (601) managing the shared NSI 3 (613).

[0133] In operation 620, the NSSMF (601) may perform selective activation of the NSSI (613) in response to the activation request received through operation 610. By performing activation of the NSSI (613) for NSI 1 (611), the NSSMF (601) may selectively (or partially) activate only some components related to NSI 1 (611) among the NSSI components (614), and keep the remaining components in a deactivated state.

[0134] At operation 630, NSSMF (601) may send an OK response to the activation request of operation 610 to NSMF (602).

[0135] By performing the activation of NSSI (613) for NSI 1 (611) through operation 630, NSSI (613) shared by NSI 1 (611) and NSI 2 (612) can be selectively activated only for NSI 1 (611) (e.g., the second state (606) of FIG. 6a). Accordingly, NSI 1 (611) can be switched to an activated state, and NSI 2 (612) can be maintained in a deactivated state (e.g., the second state (606) of FIG. 6a).

[0136] FIG. 7A is a flowchart illustrating an operation of selectively activating a shared entity when upper-level entities are managed by different management systems in a wireless communication system according to one embodiment.

[0137] In one embodiment, the core network of a wireless communication system may include multiple management systems. Higher-level (e.g., N+1) entities that share lower-level (e.g., N-level) entities may be managed by different management systems. In this case, selective activation performed on a higher-level entity managed by one management system may not affect other higher-level entities managed by other management systems.

[0138] Referring to FIG. 7A, a plurality of N+1 level entities, for example, entity_1 to entity_N, can be managed by different management systems, such as a network slice management function (NSMF) (702) and NSMF(s) (703). A shared entity_X of level N can be managed by a network slice subnet management function (NSSMF) (701). The NSSMF (701) can interact with the NSMF (702) and / or NSMF(s) (703) to perform a selective activation operation of the shared entity_X.

[0139] Referring to FIG. 7a, when upper level entities are managed by different management systems, the optional activation operations of the shared entity_X may include operations 710, 720, and 730.

[0140] In one embodiment, Entity_1 to Entity_N of level N+1, and Entity_X of level N may all be already instantiated and provisioned, but may be in a state where they cannot provide services to users (inactive state).

[0141] In operation 710, the NSMF (702) managing the entity_1 may send an entity_X activation request for the entity_1 to the NSSMF (701) managing the entity_X.

[0142] In operation 720, NSSMF (701) may perform selective activation of Entity_X in response to the activation request received through operation 710. By performing activation of Entity_X for Entity_1, NSSMF (701) may selectively (or partially) activate only some components related to Entity_1 among Entity_X components, and keep the remaining components in a deactivated state.

[0143] At operation 730, NSSMF (701) may send an OK response to the activation request of operation 710 to NSMF (702).

[0144] By performing the activation of entity_X for entity_1 through operation 730, entity_X shared by entities_1 to_N can be selectively activated only for entity_1. Accordingly, entity_1 can be activated and transitioned to a state where it can provide services, and entities_2 to_N can be maintained in a deactivated state.

[0145] In this way, NSSMF (701) can selectively (or partially) activate Entity_X, which is shared by all Entities_1 to Entities_N, only for Entity_1, at the request of NSMF (701) managing Entity_1. This selective activation operation of N-level Entity_X can be performed only for N+1-level Entity_1 managed by one management system, NSMF (701), and may not affect other N+1 entities, Entity_2 to Entity_N, managed by other management systems, NSMF(s) (703).

[0146] FIG. 7b is a flowchart illustrating an operation of selectively activating a shared entity when multiple level entities are managed by a single management system in a wireless communication system according to one embodiment.

[0147] In one embodiment, multiple slicing entities in a core network hierarchy of a wireless communication system may be managed by a single management system.

[0148] Referring to FIG. 7b, multiple slicing entities of different levels, for example, entity_1, entity_2, and entity_3, can be managed by a single management function (705). Entity_3 of level N can be an entity shared by entity_1 of level N+1 and entity_2 of level N+1.

[0149] Referring to FIG. 7b, when multi-level entities are managed by a single management system, the optional activation operations of the shared entity_3 may include operations 711, 721, and 731.

[0150] In one embodiment, Entity_1, Entity_2, and Entity_3 may all have already been instantiated and provisioned, but may be in a state where they cannot provide services to users (inactive state).

[0151] In operation 711, a management function (705) managing entity_1, entity_2 and shared entity_3 can detect the occurrence of an entity_3 activation request for entity_1.

[0152] In operation 721, the management function (705) may perform selective activation of entity_3 in response to the activation request detected through operation 711. By performing activation of entity_3 for entity_1, the management function (705) may selectively (or partially) activate only some components of entity_3 related to entity_1, and keep the remaining components in a deactivated state.

[0153] In operation 731, the management function (705) may feed back an OK response to the activation request generated in operation 711. By performing activation of entity_3 for entity_1 through operation 731, entity_3 shared by entity_1 and entity_2 may be selectively activated only for entity_1. Accordingly, entity_1 may be activated and transitioned to a state where it can provide services, and entity_2 may be maintained in a deactivated state.

[0154] FIG. 8a is a flowchart illustrating a selective activation operation of MFs (managed functions) by a switching technique supported by an EMS (element management system) in a wireless communication system according to one embodiment.

[0155] In one embodiment, support from a lower-level (or lower-layer) management system (e.g., an element management system (EMS) (803) of FIG. 8A) may be required for selective activation of shared entities (e.g., NSSI) in a network slicing environment.

[0156] In one embodiment, the NSSI may be a grouping of constituent managed functions (MFs) (or managed function instances (MFIs)), which are configurable entities. Full activation of the NSSI may require configuring all of the constituent MFs, which are lower-level entities of the NSSI. Selective (or partial) activation of the NSSI may be implemented by a scheme that configures only some of the configurable MFs. In one embodiment, selective activation at the lower level of the NSSI may be supported.

[0157] Referring to FIG. 8A, a core network of a wireless communication system may include an NSMF (802) managing NSI 1 and NSI 2, an NSSMF (801) managing a shared NSSI, an EMS (803) managing MFs (805), and MFs (805). NSI 1 and NSI 2 may be higher-level (e.g., N+1 level) entities compared to NSSI. NSSI may be a lower-level (e.g., N level) entity compared to NSI 1 and NSI 2. NSSI may be composed of MFs (805), which are lower-level (e.g., N-1 level) entities of NSSI. EMS (803) may support a selective switching technique for each of MFs (805), which are lower-level entities of the shared entity.

[0158] Referring to FIG. 8a, the selective activation operation of the shared entity by the selective activation switch technique supported by the EMS (803) may include operation 811, operation 812, operation 813, operation 814, operation 815, and operation 816.

[0159] In one embodiment, both N+1 level entities NSI 1 and NSI 2 may already be instantiated and provisioned, but may be in a state where they cannot provide services to users (deactivated state).

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

[0161] In one embodiment, NSSMF (801) may perform an optional NSSI activation operation in response to an activation request received via operation 811. The optional NSSI activation operation may include operations 812, 813, 814, 815, and 816.

[0162] At operation 812, the NSSMF (801) may transmit an MF activation request for NSSI 1 to the EMS (803) managing the MFs (805). At operation 813, the EMS (803) may configure a managed function (MF) to be activated for NSI 1 by a technique of selectively switching only some of the MFs (805). At operations 814 and 815, the EMS (803) may receive an OK signal from the MFs (805) indicating completion of MF configuration to be activated for NSI 1 and transmit the OK signal to the NSSMF (801). At operation 816, the NSSMF (801) may activate the NSSI for NSI 1 upon receiving the OK signal from the EMS (803).

[0163] At operation 817, NSSMF (801) may send an OK response to the activation request of operation 812 to NSMF (802).

[0164] Through the aforementioned process, MFs (805), which is a lower-level entity of NSSI, can be selectively activated only for NSI 1. Accordingly, NSSI, which is a higher-level entity of MFs (805), can also be selectively activated only for NSI 1. By selectively activating NSSI, NSI 1 can be activated and switched to a state where it can provide services, and NSI 2 can be maintained in a deactivated state.

[0165] FIG. 8b is a flowchart illustrating a selective deactivation operation of MFs by a switching technique supported by an EMS in a wireless communication system according to one embodiment.

[0166] Referring to FIG. 8b, the selective deactivation operation of the shared entity by the selective activation switch technique supported by the EMS (803) may include operation 821, operation 822, operation 823, operation 824, operation 825, operation 826, and operation 827.

[0167] In one embodiment, NSI 1, NSI 2, NSSI and MFs may all be already instantiated and provisioned and ready to provide services to users (activated).

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

[0169] In one embodiment, NSSMF (801) may perform an optional NSSI deactivation operation in response to a deactivation request received via operation 811. The optional NSSI deactivation operation may include operations 822, 823, 824, 825, and 826.

[0170] At operation 822, the NSSMF (801) may transmit an MF activation request for NSSI 1 to the EMS (803) managing the MFs (805). At operation 823, the EMS (803) may configure a managed function (MF) to be activated for NSI 1 by a technique of selectively switching only some of the MFs (805). At operations 824 and 825, the EMS (803) may receive an OK signal from the MFs (805) indicating completion of MF configuration to be activated for NSI 1 and transmit the OK signal to the NSSMF (801). At operation 826, the NSSMF (801) may activate the NSSI for NSI 1 upon receiving the OK signal from the EMS (803).

[0171] At operation 827, NSSMF (801) may send an OK response to the activation request of operation 821 to NSMF (802).

[0172] Through the aforementioned process, MFs (805), which is a lower-level entity of NSSI, can be selectively activated only for NSI 1. Accordingly, NSSI, which is a higher-level entity of MFs (805), can also be selectively activated only for NSI 1. By selectively activating NSSI, NSI 1 can be activated and switched to a state where it can provide services, and NSI 2 can be maintained in a deactivated state.

[0173] FIG. 9a is a flowchart illustrating an operation of selectively activating MFs by a completing configuration (or missing configuration) technique in a wireless communication system according to one embodiment.

[0174] Some communication standards may restrict selective switching techniques by lower-level management systems (e.g., EMS). In these cases, selective activation of shared entities can be implemented upon configuration completion.

[0175] In one embodiment, to implement selective activation of shared entities, as part of the instantiation and provisioning operations, an operation of only partially configuring MFs may be included. In one embodiment, selective activation at the NSSI level may be supported. For example, only some of the configurable MFs (N-1 levels), which are lower-level entities of the NSSI (N levels), may be partially configured, while the rest may be missing configurations. Missing configurations may prevent the MFs from providing services to users.

[0176] Referring to FIG. 9A, the core network of the wireless communication system may include an EMS (903). The EMS (903) may be a lower-level management system that manages MFs (805), which are lower-level entities of a shared entity.

[0177] Referring to FIG. 9a, the optional activation operations of a shared entity upon completion of configuration may include operations 911, 912, 913, 914, 915, 916, and 917.

[0178] In one embodiment, N+1 level entities NSI 1 and NSI 2 may already be instantiated and provisioned. MFs may already be instantiated and provisioned, but may be in a state where they cannot provide services to users (i.e., in a disabled state) due to a service-enabling part missing from their configuration.

[0179] In operation 911, the NSMF (802) managing NSI 1 and NSI 2 may send an NSSI activation request for NSI 1 to the NSSMF (801) managing NSSI.

[0180] In one embodiment, NSSMF (801) may perform an optional NSSI activation operation in response to an activation request received via operation 911. The optional NSSI activation operation may include operations 912, 913, 914, 915, and 916.

[0181] At operation 912, the NSSMF (801) may transmit an MF configuration request to the EMS (903) managing the MFs (805). The request may be for requesting a complete missing configuration. At operation 913, the EMS (903) may configure the MF by adding only some of the MFs (805) to the configuration and omitting the rest. At operations 914 and 915, the EMS (903) may receive an OK signal from the MFs (805) indicating the completion of the missing configuration and forward it to the NSSMF (801). At operation 916, the NSSMF (801) may activate the NSSI for NSI 1 upon receiving the OK signal from the EMS (903).

[0182] At operation 917, NSSMF (801) may send an OK response to the activation request of operation 911 to NSMF (802).

[0183] Through the aforementioned process, MFs (805), which is a lower-level entity of NSSI, can be selectively activated only for NSI 1. Accordingly, NSSI, which is a higher-level entity of MFs (805), can also be selectively activated only for NSI 1. By selectively activating NSSI, NSI 1 can be activated and switched to a state where it can provide services, and NSI 2 can be maintained in a deactivated state.

[0184] FIG. 9b is a flowchart illustrating an operation of selectively disabling MFs by a configuration completion (or missing configuration) technique in a wireless communication system according to one embodiment.

[0185] In one embodiment, selective deactivation of a shared entity, NSSI, may include removing some of the components of the MFs that comprise the NSSI. This action may prevent the MFs from providing services to users for the higher-level entity, NSSI.

[0186] Referring to FIG. 9b, the optional deactivation operation of a shared entity upon completion of configuration may include operation 921, operation 922, operation 923, operation 924, operation 925, operation 926, and operation 927.

[0187] In one embodiment, NSI 1, NSI 2, NSSI and MFs may all be already instantiated and provisioned and ready to provide services to users (activated).

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

[0189] In one embodiment, NSSMF (801) may perform an optional NSSI deactivation operation in response to a deactivation request received via operation 811. The optional NSSI deactivation operation may include operations 922, 923, 924, 925, and 926.

[0190] At operation 922, the NSSMF (801) may transmit an MF reconfiguration request (or a request for partial configuration removal) to the EMS (803) managing the MFs (805). At operation 923, the EMS (903) may reconfigure the MF by deleting some of the MFs (805) from the configuration. At operations 924 and 925, the EMS (903) may receive an OK signal from the MFs (805) indicating completion of the MF reconfiguration (or completion of the partial configuration removal) and transmit the OK signal to the NSSMF (801). At operation 926, the NSSMF (801) may deactivate the NSSI for NSI 1 upon receiving the OK signal from the EMS (903). At operation 927, the NSSMF (801) may transmit an OK response to the deactivation request of operation 921 to the NSMF (802).

[0191] Through the aforementioned process, MFs (805), which is a lower-level entity of NSSI, can be selectively deactivated only for NSI 1. Accordingly, NSSI, which is a higher-level entity of MFs (805), can also be selectively deactivated only for NSI 1. By selectively deactivating NSSI, NSI 1 can be deactivated and converted to a state where service provision is impossible, and NSI 2 can be maintained in an activated state.

[0192] FIG. 10a is a flowchart illustrating a selective activation operation of NSSI or MFs by a network communication blocking and unblocking technique in a wireless communication system according to one embodiment.

[0193] Some communication standards may restrict selective switching techniques by lower-level management systems (e.g., EMS). In these cases, selective activation of NSSI or shared entities can be implemented by blocking or unblocking network communication.

[0194] In one embodiment, to implement selective activation of shared entities, network communication blocking or unblocking operations may be included as part of the instantiation and provisioning operations. In one embodiment, selective activation at the NSSI level may be supported. For example, for selective activation at the NSSI level, the network connectivity part of the NSSI or MF may be modified. While the instantiation and provisioning of the NSSI or MF ensures that the entities remain fully operable, the network portion of the configuration may be missing or modified. Such network configuration may interfere with communication with other constituents of the service, preventing the service from being provided to the user. The activation operation may be an operation that completes or modifies the missing configuration. Such an activation operation enables nominal connectivity to a specific higher-level entity, allowing the NSSI or MF to fully provide the service to the user.

[0195] Referring to FIG. 10A, the core network of the wireless communication system may include an NSMF (1002) managing NSI 1 and NSI 2, an NSSMF (1001) managing a shared NSSI, a network controller (1003), a network (1004), an EMS (1005), and MFs (1006). NSI 1 and NSI 2 may be higher-level entities (e.g., N+1 level) compared to NSSI. NSSI may be a lower-level entity (e.g., N level) compared to NSI 1 and NSI 2.

[0196] Referring to FIG. 10a, the selective activation operations of shared entities by blocking and unblocking network communication may include operations 1011, 1012, 1013, 1014, 1015, 1016, and 1017.

[0197] In one embodiment, NSI 1, NSI 2, NSSI, and MFs may all be instantiated and provisioned, but may be in a state where they are unable to provide services to users (i.e., are in a disabled state). The network (1004) (e.g., a specific network slice or subnet) may be configured to block all service traffic (or communication) for NSI 1 and NSI 2.

[0198] In operation 1011, the NSMF (1002) managing NSI 1 and NSI 2 may send an NSSI activation request for NSI 1 to the NSSMF (1001) managing NSSI.

[0199] In one embodiment, NSSMF (1001) may perform an optional NSSI activation operation in response to an activation request received via operation 1011. The optional NSSI activation operation may include operations 1012, 1013, 1014, 1015, and 1016.

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

[0201] At operation 1017, NSSMF (1001) may send an OK response to the activation request of operation 1011 to NSMF (1002).

[0202] Through the aforementioned process, NSI 1 may be activated, while NSI 2 may not be activated. The shared NSSI may be selectively (or partially) activated only for NSI 1. Reconfiguration of the network (1004) may enable communication only for services associated with NSI 1.

[0203] FIG. 10b is a flowchart illustrating a selective deactivation operation of NSSI or MFs by a network communication blocking and unblocking technique in a wireless communication system according to one embodiment.

[0204] Referring to FIG. 10b, the selective disabling of shared entities by blocking and unblocking network communication may include operations 1021, 1022, 1023, 1024, 1025, 1026, and 1027.

[0205] In one embodiment, NSI 1, NSI 2, NSSI and MFs may all be already instantiated and provisioned and ready to provide services to users (activated).

[0206] In operation 1021, the NSMF (1002) managing NSI 1 and NSI 2 may send an NSSI deactivation request for NSI 1 to the NSSMF (1001) managing NSSI.

[0207] In one embodiment, NSSMF (1001) may perform an optional NSSI deactivation operation in response to a deactivation request received via operation 1021. The optional NSSI deactivation operation may include operations 1022, 1023, 1024, 1025, and 1026.

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

[0209] At operation 1027, NSSMF (1001) may send an OK response to the deactivation request of operation 1021 to NSMF (1002).

[0210] Through the aforementioned process, NSI 1 may be deactivated, while NSI 2 may remain activated. The shared NSSI may be selectively (or partially) deactivated only for NSI 1. Communication may be disabled only for services associated with NSI 1 through reconfiguration of the network (1004).

[0211] According to one embodiment, a network communication blocking (or service traffic blocking) technique may be implemented as follows.

[0212] - Configure a hardware or software firewall to block specific network traffic.

[0213] - Disable interfaces on hardware or software switches and routers.

[0214] - Configure routing protocols, routing policies, or static routing to block or blackhole specific traffic on hardware or software switches or routers.

[0215] - Configure an internal firewall on the Virtual Machine that configures MF to block specific network traffic.

[0216] - Disable the interface of the virtual machine that makes up the MF.

[0217] - Configure routing protocols, routing policies, or static routing to block or blackhole specific traffic on the virtual machines that make up the MF.

[0218] According to one embodiment, a network communication unblocking (or service traffic unblocking) technique may be implemented as follows.

[0219] - Configure a hardware or software firewall to unblock specific network traffic.

[0220] - Activate interfaces on hardware or software switches and routers

[0221] - Configuring routing protocols, routing policies, or static routing on hardware or software switches or routers to allow and route specific traffic.

[0222] - Configure an internal firewall on the Virtual Machine that configures MF to allow specific network traffic.

[0223] - Allow and route specific traffic from the virtual machines that configure the MF by activating interfaces on the virtual machines that configure the MF, which configure routing protocols, routing policies, or static routing.

[0224] FIG. 11a and FIG. 11b are drawings for explaining a selective deactivation operation of a network slice subnet instance (NSSI) by a consensus technique of a network slice management function (NSMF) in a wireless communication system according to one embodiment.

[0225] In cases where some communication standards do not support selective per-NSI activation and deactivation, NSMF request tracking techniques can be used to improve control over deactivation. A higher-level management node (e.g., NSMF) may not be aware of other higher-level management nodes (e.g., other NSMFs) that share a lower-level entity (e.g., NSSI). In this case, each higher-level management node can request deactivation from a lower-level management node (e.g., NSSMF) based solely on the intended state of the entity (e.g., NSI) it manages. A lower-level management node (e.g., NSSMF) that manages a shared entity (e.g., NSSI) can ensure that the entity (e.g., NSSI) it manages is not deactivated while any of the higher-level entities are activated.

[0226] Referring to FIG. 11A, NSI 1 (1111) may be an N+1 level entity managed by NSMF 1 (1102). NSI 2 (1112) may be an N+1 level entity managed by NSMF 2 (1103). NSSI (1113) may be an N level entity shared by NSI 1 and NSI 2. NSSI (1113) may be composed of NSSI constituents (1115).

[0227] In the first state (1106) of FIG. 11a, NSI 1 (1111), NSI 2 (1112), and shared NSSI (1113) may all be activated. By performing NSI 1 deactivation with NSMF request tracking, the first state (1106) may transition to the second state (1107). In the second state (1107), only NSI 1 may be deactivated, and NSI 2 may remain activated.

[0228] Referring to FIG. 11b, the core network of the wireless communication system may include NSMF 1 (1102) managing NSI 1 (1111), NSMF 2 (1103) managing NSI 2, NSSMF (1101) managing shared NSSI (1113), EMS (1104) managing MFs of NSSI, and MFs (1105) managed by EMS (1104).

[0229] Referring to FIG. 11b, the activation operation through request tracing of NSMF may include NSI 1 activation operation 1131 and / or NSI 2 activation operation 1132.

[0230] NSI 1 activation action 1131 may include actions 1121 and 1122.

[0231] In operation 1121, NSMF 1 (1102) managing NSI 1 (1111) may transmit an activation request of NSSI (1113) to NSSMF (1101) managing NSSI (1113), which is a shared lower-level entity. Upon receiving the activation request, NSSMF (1101) managing NSSI (1113), which is a shared lower-level entity, may store information about NSMF 1 (1102) that transmitted the request with the intention of activating NSSI (1113) on behalf of NSI 1 (e.g., system ID of NSMF 1 (1102) and / or entity ID of NSI 1). NSSMF (1101) may perform activation of NSSI in response to the request if NSSI (1113) that it manages is already deactivated. At operation 1122, NSSMF (1101) may send an OK response to the activation request of operation 1121 to NSMF 1 (1102).

[0232] NSI 2 activation action 1132 may include actions 1123 and 1124.

[0233] In operation 1123, NSMF 2 (1103) managing NSI 2 (1112) may transmit an activation request of NSSI (1113) to NSSMF (1101) managing shared NSSI (1113). Upon receiving the activation request, NSSMF (1101) may store information about NSMF 2 (1103) that transmitted the request with the intention of activating NSSI (1113) managed by NSSMF (1101) on behalf of NSI 2 (e.g., system ID of NSMF 2 (1103) and / or entity ID of NSI 2). In operation 1124, NSSMF (1101) may transmit an OK response to the activation request of operation 1123 to NSMF 2 (1103).

[0234] Referring to FIG. 11b, the deactivation operation through request tracing of NSMF may include an NSI 1 deactivation operation and / or an NSI 2 deactivation operation.

[0235] NSI 1 Disable Action 1133 may include Action 1125 and Action 1126.

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

[0237] NSI 2 Disable Action 1134 may include Actions 1127 and 1128.

[0238] In operation 1127, NSMF 1 (1102) may transmit a deactivation request of NSSI (1113) to NSSMF (1101). Upon receiving the deactivation request from NSMF 1 (1102), NSSMF (1101) may delete information about NSMF 1 (1102) stored as an activation intent (e.g., system ID of NSMF 1 (1102) and / or NSI 1 (1111)). When all of the information is deleted and there is no longer an activation intent of NSMF 1 (1102) and NSMF 2 (1103) as managed entities, NSSMF (1101) may deactivate NSSI (1113) shared by NSMF 1 (1102) and NSMF 2 (1103). At operation 1128, NSSMF (1101) may send an OK response to the deactivation request of operation 1127 to NSMF (1002).

[0239] A method of operating a management node according to various embodiments may be a method of operating a management node in a wireless communication system having a network slicing environment. The method may include receiving an activation request for a shared lower-level entity among a plurality of higher-level entities that share a lower-level entity managed by the management node, when one or more of the shared lower-level entities are activated, and activating the shared lower-level entity for the one or more activated higher-level entities in response to the activation request.

[0240] According to various embodiments, the act of receiving the activation request may include receiving the activation request from a management node that manages one or more of the activated higher-level entities among the second management nodes, if the higher-level entities are managed by different second management nodes.

[0241] According to various embodiments, the act of receiving the activation request may include an act of internally detecting the occurrence of the activation request in the management node when multi-level entities including the upper-level entities and the lower-level entities are managed by the management node.

[0242] According to various embodiments, the operation of receiving the activation request may include the operation of the management node including a network slice subnet management function (NSSMF) that manages the network slice subnet instance (NSSI), which is the lower-level entity. The operation of receiving the activation request may include the operation of the NSSMF receiving an activation request for a specific NSI among the network slice instances (NSIs), which are the upper-level entities, from a network slice management function (NSMF) that manages the NSIs. The operation of activating may include the operation of the NSSMF partially activating the NSSI shared by the NSIs only for the specific NSI.

[0243] According to various embodiments, the operation of the NSSMF to partially activate the NSSI shared by the NSIs only for the specific NSI may include an operation of the NSSMF sending an MF activation request for the specific NSI to an element management system (EMS) that manages MFs (managed functions), such that the EMS, in response to the MF activation request, configures some of the MFs as MFs to be activated for the specific NSI.

[0244] According to various embodiments, the operation of the NSSMF partially activating the NSSI shared by the NSIs only for the specific NSI may include an operation of the NSSMF sending an MF configuration request for the specific NSI to an EMS managing MFs, such that the EMS configures an MF for the specific NSI by omitting some of the MFs in response to the MF configuration request.

[0245] According to various embodiments, the operation of the NSSMF partially activating the NSSI shared by the NSIs only for the specific NSI may include the operation of the NSSMF transmitting a network reconfiguration request to the network controller to enable network communication related to the specific NSI, thereby causing the network controller to reconfigure the network in response to the network reconfiguration request.

[0246] According to various embodiments, the activating operation may include activating the shared lower-level entity only for a set of activated entities among the upper-level entities, and deactivating the shared lower-level entity for a set of deactivated entities among the upper-level entities.

[0247] According to various embodiments, the method may further include receiving a deactivation request of the shared lower-level entity when one or more of the upper-level entities are deactivated, and, in response to the deactivation request, deactivating the shared lower-level entity for the one or more deactivated upper-level entities.

[0248] According to various embodiments, the management node may include an NSSMF that manages the NSSI, which is the lower-level entity. The deactivating operation of the method may include an operation in which the NSSMF identifies whether all NSIs sharing one NSSI are in a deactivated state, an operation in which the NSSI is deactivated if all NSIs are in a deactivated state, and an operation in which the NSSI is maintained in an activated state if not all NSIs are in a deactivated state.

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

[0250] According to various embodiments, the at least one processor may be configured to receive the activation request from a management node that manages the activated one or more higher-level entities among the second management nodes, when the higher-level entities are managed by different second management nodes.

[0251] According to various embodiments, the at least one processor may be configured to internally detect the occurrence of the activation request in the management node when multi-level entities including the upper-level entities and the lower-level entities are managed by the management node.

[0252] According to various embodiments, the management node may include a network slice subnet management function (NSSMF) that manages the network slice subnet instance (NSSI), which is the lower-level entity. The at least one processor may be configured to receive an activation request for a specific NSI among the network slice instances (NSIs) from the network slice management function (NSMF) that manages the network slice instances (NSIs), which are the upper-level entities, and to partially activate the NSSI shared by the NSIs only for the specific NSI.

[0253] According to various embodiments, the at least one processor may transmit an MF activation request for the specific NSI to an element management system (EMS) that manages managed functions (MFs), thereby causing the EMS to configure some of the MFs as MFs to be activated for the specific NSI in response to the MF activation request.

[0254] According to various embodiments, the at least one processor may transmit an MF configuration request for the specific NSI to an EMS managing MFs, thereby causing the EMS to configure an MF for the specific NSI by omitting some of the MFs in response to the MF configuration request.

[0255] According to various embodiments, the at least one processor may cause the network controller to reconfigure the network in response to the network reconfiguration request by transmitting a network reconfiguration request to the network controller to enable network communication associated with the particular NSI.

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

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

[0258] According to various embodiments, the management node may include an NSSMF that manages the NSSI, which is the lower-level entity. The at least one processor may be configured to identify whether all of the NSIs, which are the upper-level entities sharing the NSSI, are inactive, and to deactivate the NSSI if all of the NSIs are inactive, and to maintain the NSSI in an active state if not all of the NSIs are inactive.

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

[0260] While this disclosure has been illustrated and described with reference to various embodiments, it is to be understood that the various embodiments are illustrative and not restrictive. It will be understood by those skilled in the art that various changes in form and detail may be made without departing from the full scope of the disclosure, including the appended claims and their equivalents. Furthermore, it will be understood that any embodiment(s) of the present disclosure may be used in conjunction with any other embodiment(s) of the present disclosure.

Claims

1. In a method of operating a management node in a wireless communication system having a network slicing environment, An operation of receiving an activation request of a shared lower-level entity, when one or more of a plurality of higher-level entities sharing a lower-level entity managed by the management node are activated; and A method comprising, in response to said activation request, an action of activating said shared lower-level entity for said one or more activated higher-level entities.

2. In claim 1, The action of receiving the above activation request is: A method comprising receiving an activation request from a management node that manages one or more of the activated higher level entities among the second management nodes, based on the above upper level entities being managed by different second management nodes.

3. In claim 1, The action of receiving the above activation request is: A method including an operation of internally detecting the occurrence of the activation request in the management node based on the multi-level entities including the above upper-level entities and the above lower-level entities being managed by the management node.

4. In claim 1, The above management node includes a network slice subnet management function (NSSMF) configured to manage a network slice subnet instance (NSSI) including the above lower level entity, The action of receiving the above activation request is: The NSSMF comprises an operation of receiving an activation request of the NSSI for a specific NSI among the NSIs from the NSMF (network slice management function) that manages the NSIs (network slice instances) including the upper level entities, The above activating action is, A method comprising the NSSMF partially activating the NSSI shared by the NSIs for the specific NSI.

5. In claim 4, The operation of the above NSSMF partially activating the NSSI shared by the above NSIs for the specific NSI is, By the above NSSMF sending an MF activation request for the specific NSI to the EMS (element management system) that manages the MFs (managed functions), A method comprising the action of causing said EMS to configure some of said MFs as MFs to be activated for said particular NSI in response to said MF activation request.

6. In claim 4, The operation of the above NSSMF partially activating the NSSI shared by the above NSIs for the specific NSI is, By the above NSSMF sending a MF configuration request for the above specific NSI to the EMS that manages the MFs, A method comprising the action of causing said EMS to configure an MF for said specific NSI by omitting some of said MFs in response to said MF configuration request.

7. In claim 4, The operation of the above NSSMF partially activating the NSSI shared by the above NSIs for the specific NSI is, By the above NSSMF sending a network reconfiguration request to the network controller to enable network communication related to the specific NSI, A method comprising causing the network controller to reconfigure the network in response to the network reconfiguration request.

8. In claim 1, The above activating action is, An operation of activating the shared lower level entity for the set of activated entities among the upper level entities; and A method comprising the action of deactivating the shared lower level entities for the remaining set of deactivated entities among the above upper level entities.

9. In claim 1, An operation of receiving a deactivation request of said shared lower level entity when one or more of said upper level entities are deactivated; and A method further comprising, in response to said deactivation request, deactivating said shared lower-level entity for said one or more deactivated higher-level entities.

10. In claim 9, The above management node includes an NSSMF configured to manage the NSSI including the above lower level entities, The above disabling action is: An action for identifying whether all NSIs sharing a single NSSI are inactive; An action to disable the NSSI based on the above NSIs being all disabled; and A method comprising the action of maintaining said NSSI in an activated state based on not all of said NSIs being in an inactive state.

11. In a management node in a wireless communication system having a network slicing environment, transceiver; and At least one processor coupled to said transceiver and comprising a processing circuit; At least one processor of the above: When one or more of a plurality of higher-level entities sharing a lower-level entity managed by the above management node are activated, a request for activation of the shared lower-level entity is received, A management node configured to activate the shared lower-level entity for the one or more activated higher-level entities in response to the activation request.

12. In claim 11, At least one processor of the above, A management node configured to receive the activation request from a management node that manages one or more of the activated higher level entities among the second management nodes, based on which the above upper level entities are managed by different second management nodes.

13. In claim 11, At least one processor of the above, A management node configured to internally detect the occurrence of the activation request based on the multi-level entities including the above upper-level entities and the above lower-level entities being managed by the management node.

14. In claim 11, The above management node, Includes a network slice subnet management function (NSSMF) configured to manage a network slice subnet instance (NSSI) that includes the above lower-level entities, At least one processor of the above, Receive an activation request for a specific NSI among the NSIs from the NSMF (network slice management function) that manages the NSIs (network slice instances), which are the upper level entities, and A management node configured to partially activate said NSSI shared by said NSIs for said specific NSI.

15. In claim 14, At least one processor of the above, By sending an MF activation request for the specific NSI to the EMS (element management system) that manages MFs (managed functions), A management node that causes the EMS to configure some of the MFs as MFs to be activated for the specific NSI in response to the MF activation request.

Images