Patent Application
20240356802
The present disclosure relates to a management node and its operating method in a wireless communication system, and for example, to the management node for managing a network entity and its operating method in the wireless communication system with a network slicing environment.
A fifth generation (5G) mobile communication technology defines a broad frequency band to allow a high transmission rate and a new service, and may be implemented not only in a frequency (‘Sub 6 gigahertz (GHz)’) band below 6 GHz such as 3.5 GHz but also in an extremely high frequency band (‘Above 6 GHz’) referred to as a millimeter wave (mmWave) such as 28 GHz and 39 GHz. In addition, a sixth generation (6G) mobile communication technology referred to as a beyond 5G system is considering its implementation in a terahertz (THz) band (e.g., in a band from 95 GHz to 3 THz) to achieve the transmission rate fifty times faster than the 5G mobile communication technology and ultra low latency reduced to one-tenth.
At the initial stage of the 5G mobile communication technology, to support services and to satisfy performance requirements for enhanced mobile broadband, (eMBB), ultra-reliable low-latency communications (URLLC), and massive machine-type communications (mMTC), standardization has been conducted on beamforming and massive multiple input multiple output (MIMO) for alleviating a radio wave path loss and increasing a radio wave transmission distance in the extremely high frequency band, support of various numerologies (operating multiple subcarrier spacings and so on) for efficiently utilizing extremely high frequency resources and slot format dynamic operation, an initial access technology for supporting multi-beam transmission and the broadband, definition and operation of a band-width part (BWP), a new channel coding method such as a low density parity check (LDPC) code for large-capacity data transmission and a polar code for higher-reliability transmission of control information, L2 pre-processing, and network slicing for providing a dedicated network customized to a specific service.
Currently, there is ongoing discussion regarding improvement and performance enhancement of the initial 5G mobile communication technology by considering the services to be supported by the 5G mobile communication technology, and physical layer standardization is conducted on technologies such as vehicle-to-everything (V2X) for aiding driving determination of an autonomous vehicle based on location and state information transmitted by the vehicle and enhancing user convenience, new radio unlicensed (NR-U) aimed at system operations conforming to various regulation-related requirements in an unlicensed band, NR user equipment (UE) power saving, a non-terrestrial network (NTN) which is UE-satellite direct communication for securing coverage in an area where communication with a terrestrial network is impossible, and positioning.
There has also been ongoing standardization in wireless interface architecture/protocol fields for technologies such as industrial internet of things (IOT) for supporting a new service through interworking and converging with other industries, integrated access and backhaul (IAB) for providing a node for network service area expansion by supporting a wireless backhaul link and an access link in an integrated manner, mobility enhancement including conditional handover and dual active protocol stack (DAPS) handover, and two-step random access for simplifying a random access procedure (2-step RACH for NR), and standardization is also conducted in system architecture/service fields for a 5G baseline architecture (e.g., service based architecture, service based interface) for combining network functions virtualization (NFV) and software-defined networking (SDN) technologies, and mobile edge computing (MEC) for receiving a service based on a UE location.
If such a 5G mobile communication system is commercialized, connected devices which are exponentially increasing will be connected to the communication network, and accordingly it is expected that function and performance enhancement of the 5G mobile communication system and integrated operation of the connected devices are needed. To this end, new research is scheduled on extended reality (XR) for efficiently supporting augmented reality (AR), virtual reality (VR), and mixed reality (MR), 5G performance improvement and complexity reduction by utilizing artificial intelligence (AI) and machine learning (ML), AI service support, metaverse service support, and drone communication.
In addition, such development of the 5G mobile communication system will serve as a basis for developing not only new waveform for securing coverage in the terahertz band of the 6G mobile communication technology, full dimensional MIMO (FD-MIMO), multi-antenna transmission technology such as an array antenna and a large scale antenna, metamaterial-based lens and antenna for improving terahertz band signal coverage, higher-dimensional space multiplexing technology using orbital angular momentum (OAM), and reconfigurable intelligent surface (RIS), but also full duplex technology for increasing frequency efficiency and improving a system network of the 6G mobile communication technology, AI based communication technology for implementing system optimization by utilizing a satellite and an AI from the design stage and embedding an end-to-end AI support function, and next-generation distributed computing technology for implementing services of complexity exceeding UE processing capability limits by utilizing ultra high performance communication and computing resources.
Network slicing may refer to a network architecture which enables multiplexing of virtualized and independent logical networks on the same physical network infrastructure in the wireless communication system such as the 5G mobile communication system. Each network slice (or subnet) may represent an isolated end-to-end network, tailored to fulfill various requirements requested by a particular application. Through the network slicing technique, multiple virtualized logical networks may exist on one physical network.
Embodiments of the disclosure may provide an operating method of a management node. The method of operating a management node according to an example embodiment may be in a wireless communication system with a network slicing environment. The method may include, based on one or more of multiple higher-level entities sharing a lower-level entity managed by the management node being activated, receiving an activation request of the shared lower-level entity, and activating the shared lower-level entity for the one or more activated higher-level entities, in response to the activation request.
Embodiments of the disclosure may provide a management node. The management node according to an example embodiment may be in a wireless communication system with a network slicing environment. The management node may include: a transceiver and at least one processor comprising processing circuitry connected to the transceiver. At least one processor may be configured to, based on one or more of multiple higher-level entities sharing a lower-level entity managed by the management node being activated: receive an activation request of the shared lower-level entity, and activate the shared lower-level entity for the one or more activated higher-level entities, in response to the activation request.
The above and other aspects, features and advantages of certain embodiments of the present disclosure will be more apparent from the following detailed description, taken in conjunction with the accompanying drawings, in which:
It should be understood that various example embodiments of the present disclosure and terms used herein do not intend to limit technical features disclosed in the present disclosure to specific embodiments, but embrace various modifications, equivalents, or alternatives of corresponding embodiments.
Methods according to various example embodiments of the present disclosure may be implemented in software, hardware, or a combination of hardware and software. In the software implementation, a computer-readable storage medium storing one or more programs (software modules) may be provided. One or more programs stored in the computer-readable storage medium is configured for execution by one or more processors of an electronic device. One or more programs include instructions for controlling the electronic device to execute the methods according to the embodiments described in the claims or the present disclosure.
Such a program (software module, software) may be stored to a random access memory, a non-volatile memory including a flash memory, a read only memory (ROM), an electrically erasable programmable ROM (EEPROM), a magnetic disc storage device, a compact disc (CD)-ROM, digital versatile discs (DVDs) or other optical storage devices, and a magnetic cassette. Alternatively, it may be stored to a memory combining part or all of them. In addition, a plurality of memories may be included.
The program may be stored in an attachable storage device accessible via a communication network such as internet, intranet, local area network (LAN), wide LAN (WLAN), or storage area network (SAN), or a communication network by combining them. Such a storage device may access a device which executes an embodiment of the present disclosure through an external port. In addition, a separate storage device on the communication network may access a device which executes an embodiment of the present disclosure.
In various example embodiments of the present disclosure, components are expressed in a singular or plural form. However, the singular or plural expression is appropriately selected for convenience of explanation, the present disclosure is not limited to a single component or a plurality of components, the components expressed in the plural form may be configured as a single component, and the components expressed in the singular form may be configured as a plurality of components.
Terms indicating signals, terms indicating channels, terms indicating control information, terms indicating network entities, terms indicating components of a device, which are used in the following descriptions, are for the sake of explanations. Accordingly, the present disclosure is not limited to the terms to be described, and other terms having technically identical or similar meaning may be used.
In addition, the present disclosure describes various embodiments using terms used in various communication standards (e.g., 3rd generation partnership project (3GPP)), which are merely examples used for explanation. Various embodiments of the present disclosure may be easily modified and applied to other communication systems.
Hereafter, various example embodiments of the present disclosure will be described in greater detail. However, the present disclosure may be implemented in many different forms and is not limited to the embodiments described herein. In relation to the description of the drawings, identical or similar reference numerals may be used for identical or similar components. Additionally, in the drawings and related descriptions, descriptions on well-known functions and configurations may be omitted for clarity and brevity.
Referring to
The CN is a network which manages the entire system, and may control the RAN 120, and process data and control signals of the UE 110 transmitted and received over the RAN 120. The CN may perform various functions such as user plane and control plane controlling, mobility processing, subscriber information management, charging, and interworking with other system (e.g., a long term evolution (LTE) system). To perform the various functions described above, the CN may include a plurality of functionally separated entities with different network functions (NFs).
The CN may include network functions such as an access and mobility management function (AMF) 150 which provides a mobility management function of the UE, a session management function (SMF) 160 which provides a session management function, a user plane function (UPF) 170 which delivers data, a policy control function (PCF) 180 which provides a policy and charging function, a unified data management (UDM) 153 which provides a data management function such as subscriber data or policy control data, a network slice selection function (NSSF) 190 which operates and/or manages network slices, or a unified data repository (UDR) which stores data of various network functions. Although not depicted in
Referring to
Referring to
Referring to
In the 3GPP system, conceptual links interconnecting network functions (NFs) within the 5G system may be referred to as reference points. The reference point may be referred to as an interface. The following illustrates reference points included in the 5G system architecture represented in
According to various embodiments, by applying the network slicing technique to the wireless communication system (e.g., the 5G mobile communication network of
According to various embodiments, in the wireless communication system with the network slicing environment, a slicing entity or a managed entity (e.g., an NSSI, an NSI, or a managed function (MF)) may have sharability. For example, one NSSI (e.g., any one of an NSSI 1, an NSSI 2, and an NSSI 3 of
According to an embodiment, MFs may represent logical applications executed inside virtual network functions (VNFs)/physical network functions (PNFs)/container network functions (CNFs). The MFs may execute a predefined function set, and communicate with each other through standard interfaces called reference points. Creating a network slice may indicate spawning new instances of slice-dedicated MFs, and reusing MFs which may be shared among multiple slices. For example, the dedicated MFs may correspond to the SMF 160 or the UPF 170 shown in
According to an embodiment, a management node 201 may be a device or a function for managing one or more slice entities. The management node 201 may be referred to as a management entity, a management system, or a management function. In an embodiment, the management node 201 may include a device or a function for managing a lower-level entity among multi-level entities (a higher-level entity and a lower-level entity) included in the wireless communication system. For example, the management node 201 may include a function or a device corresponding to at least one of the CSMF, the NSMF and the NSSMF. A term such as ‘ . . . unit’ or ‘ . . . er’ used hereafter indicates a unit for processing at least one function or operation, and may be implemented using hardware, software, or a combination of hardware and software.
Referring to
In an embodiment, the communication unit 210 may include various communication circuitry and provide an interface for communicating with other devices in the network. For example, the communication unit 210 may convert a bit string transmitted from the management node 210 to other device (or an external electronic device) into a physical signal, and convert a physical signal received from other device into a bit string. In an 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, a transceiver, or the like. The communication unit 210 may support the management node 210 to communicate with other devices or systems via a backhaul connection (e.g., wired backhaul or wireless backhaul) or over the network.
In an embodiment, the storage unit 230 may store data such as a basic program, an application program, and setting information for the operations of the management node 201. The storage unit 230 may include a volatile memory, a nonvolatile memory or a combination of a volatile memory and a nonvolatile memory. The storage unit 230 may provide the stored data according to a request of the control unit 220.
In an embodiment, the control unit 220 may include at least one processor electrically and/or operatively coupled with the communication unit 210. The processor according to an embodiment of the disclosure may include various processing circuitry. For example, as used herein, including the claims, the term “processor”, “control unit”, etc., may include various processing circuitry, including at least one processor, wherein one or more of at least one processor may be configured to perform various functions described herein. Additionally, the at least one processor may include a combination of processors performing various of the recited/disclosed functions. At least one processor may execute program instructions to achieve or perform various functions. The control unit 220 may control general operations of the management node 201. For example, the control unit 220 may transmit and receive signals through the communication unit 210. In addition, the control unit 220 may record and read data in and from the storage unit 230. The control unit 220 may perform a designated function by executing instructions (or programs) stored in the storage unit 203.
According to an embodiment, as one or more (e.g., a first entity among the first entity and a second entity) of multiple higher-level entities sharing a lower-level entity (e.g., a third entity) managed by the management node 201 is activated, the control unit 220 may be configured to receive an activation request of the shared lower-level entity (e.g., the third entity), through the communication unit 210 (e.g., a transceiver).
In an embodiment, if the higher-level entities (e.g., the first entity and the second entity) are managed by different second management nodes, the control unit 220 may receive an activation request from a management node which manages one or more activated higher-level entities (e.g., the first entity) among the second management nodes.
In an embodiment, if multi-level entities including the higher-level entities (e.g., the first entity and the second entity) and the lower-level entity (e.g., the third entity) are managed by the management node 201 alone, the control unit 220 may internally detect activation request occurrence.
According to an embodiment, the control unit 220 of the management node 201 may be configured to activate the shared lower-level entity (e.g., the third entity) with respect to one or more activated higher-level entities (e.g., the first entity), in response to the activation request.
According to an embodiment, the management node 201 may include the NSSMF for managing the NSSI which is the lower-level entity. The NSSMF may receive an activation request of the NSSI for a specific NSI of the NSIs from the NSMF which manages NSIs which are higher-level entities. The NSSMF may partially activate the shared NSSI only for the specific NSI by the NSIs.
In an embodiment, the NSSMF may transmit an MF activation request of the specific NSF to an element management system (EMS) which manages the MFs, to thus enable the EMS to configure some of the MFs as the MF to be activated for the specific NSI in response to the MF activation request.
In an embodiment, the NSSMF may transmit an MF configuration request for the specific NSF to the EMS which manages the MFs, to thus enable the EMS to configure the MF for the specific NSI by leaving some of the MFs in response to the MF configuration request.
In an embodiment, the NSSMF may transmit a network reconfiguration request for enabling network communication related to the specific NSF to a network controller, to thus enable the network controller to reconfigure the network in response to the network reconfiguration request.
In an embodiment, the NSSMF may activate a lower-level entity (e.g., the NSSI) shared by the higher-level entities only for an activated entity set (e.g., the NSI 1) of the higher-level entities (e.g., the NSI 1, the NSI2). The NSSMF may deactivate a lower-level entity (e.g., the NSSI) shared by the higher-level entities with respect to the other deactivated entity set (e.g., the NSI 2) of the higher-level entities (e.g., the NSI 1, the NSI2).
According to an embodiment, the control unit 220 of the management node 201 may be configured to receive a deactivation request of the shared lower-level entity (e.g., a third entity), as one or more of higher-level entities (e.g., a first entity and a second entity) are deactivated (e.g., the first entity). The control unit 220 may be configured to deactivate the shared lower-level entity (e.g., a third entity) for one or more deactivated higher-level entities (e.g., the first entity), in response to the deactivation request.
In an embodiment, the management node 201 may include the NSSMF for managing the NSSI which is the shared lower-level entity. In an embodiment, the NSSMF may identify whether the NSIs which are the higher-level entities sharing one NSSI are all deactivated. The NSSMF may deactivate the NSSI if the NSIs which are the higher-level entities sharing one NSSI being the shared lower-level entity are all deactivated, and may maintain the NSSI in the active state if all of the NSIs which share the NSSI are not deactivated.
Operations of the method illustrated in
Referring to
According to an embodiment, a CN of the wireless communication system may include various multi-level entities, for example, an entity_1, an entity_2 and an entity_3. The entity_1, the entity_2 or the entity_3 may correspond to slicing entities operating in the network slicing environment. At least a part of the entity_1, the entity_2 and the entity_3 may be entities of different levels. For example, the entity_1 and the entity_2 may be entities of a higher level or a higher layer (e.g., an N+1 level) than the entity_3. The entity_3 may be an entity of a lower level or a lower layer (e.g., an N level) than the entity_1.
According to an embodiment, the CN of the wireless communication system may include the management node 201. In an embodiment, the management node 201 may be a first management node for managing the entity_3 which is the lower-level entity. For example, the first management node may include at least one of the N-level management system 401 of
Operation 310 may include receiving an activation request of a shared lower-level entity (e.g., the entity_3). In operation 310, the management node (e.g., the control unit 220 of
According to an embodiment, if higher-level entities (e.g., the entity_1 and the entity_2, or the NSI 1 and the NSI 2) are managed by different second management nodes, the management node 201 may receive an activation request from the management node (e.g., any one of an N+1 level management system 402 of
According to an embodiment, if multi-level entities including higher-level entities and lower-level entities are managed by one management node 201, the management node 201 may detect activation request occurrence inside the management node 201.
Operation 320 may include selectively activating the shared lower-level entity (e.g., the entity_3). In operation 320, the management node 201 (e.g., the control unit 220 of
In an embodiment, the management node 201 may selectively (or partially) activate the lower-level entity only for a specific entity (e.g., the entity_1) among the higher-level entities sharing one lower-level entity (e.g., the entity_3). For example, the selective (or partial) activation and/or deactivation of the entity_3 for the specific higher-level entity (e.g., the entity_1) may be implemented, rather than binary activation of the whole entity_3 shared by multiple higher-level entities (e.g., the entity_1, the entity_2).
According to an embodiment, the management node 201 may allow a slicing entity (e.g., a lower-level entity) to perform the selective activation and/or deactivation. As a result, activation and/or deactivation of the lower-level entity may be performed only for a specific higher-level entity of the higher-level entities, not for all the higher-level entities sharing one lower-level entity.
According to an embodiment, the management node 201 may directly control the activation and/or deactivation of the slicing entity (e.g., a lower-level entity), or may induce the activation and/or deactivation of the slicing entity through the selective activation and/or deactivation of the network function (or the MF).
According to an embodiment, a method for performing deactivation of a shared lower-level entity, managed by the management node 201, may be provided. For example, the lower-level entity may be deactivated only if it is expected that all the higher-level entities sharing one lower-level entity are to be deactivated. In this method, the NSSI is presented as an example of the shared lower-level entity.
According to an embodiment, higher-level entities (e.g., the entity_1, the entity 2) may be managed by a plurality of different second management nodes (e.g., an embodiment of
According to an embodiment, multi-level entities including higher-level entities (e.g., the entity_1, the entity 2) and lower-level entities (e.g., the entity_3) may be managed by one identical management node 201 (e.g., an embodiment of
According to an embodiment, the management node 201 may include the NSSMF for managing the NSSI which is the shared lower-level entity (e.g., the entity_3). The selective activation operation 320 of the shared lower-level entity may include receiving an activation request of the NSSI for a specific NSI (e.g., the NSI 1) among the NSIs from the NSMF for managing NSIs which are the higher-level entities (e.g., an embodiment of
In an embodiment, the selective activation operation 320 of the shared lower-level entity (e.g., the entity_3) may include a selective activation operation of MFs by a switching scheme of the EMS (e.g., an embodiment of
In an embodiment, the selective activation operation 320 of the shared lower-level entity (e.g., the entity_3) may include a selective activation operation of NFs by a configuration complete scheme (e.g., an embodiment of
In an embodiment, the selective activation operation 320 of the shared lower-level entity (e.g., the entity_3) may include a selective activation operation of an NSSI or NFs by a network communication blocking or unblocking scheme (e.g., an embodiment of
According to an embodiment, the selective activation operation 320 of the shared lower-level entity (e.g., the entity_3) may include activating a shared lower-level entity (e.g., the entity_3) only for an activated entity set (e.g., the first entity) of higher-level entities sharing the lower-level entity, and deactivating the shared lower-level entity (e.g., the entity_3) for the other deactivated entity set (e.g., the entity_2) of the higher-level entities.
According to an embodiment, the method of operating the management node in the wireless communication system may include receiving a deactivation request of a shared lower-level entity (e.g., the entity_3), and deactivating the shared lower-level entity (e.g., the entity_3) in response to the deactivation request. As one or more of the higher-level entities (e.g., the first entity and the second entity) are deactivated (e.g., the first entity), the management node 201 may receive the deactivation request of the lower-level entity (e.g., the entity_3) shared by the higher-level entities. The management node 201 may be configured to selectively (or partially) deactivating the shared lower-level entity (e.g., the entity_3) for the one or more deactivated higher-level entities (e.g., the first entity), in response to the deactivation request.
In an embodiment, the management node 201 may include the NSSMF for managing the NSSI which is the shared lower-level entity. In an embodiment, the NSSMF may identify whether the NSIs which are the higher-level entities sharing one NSSI are all deactivated. The NSSMF may deactivate the NSSI if the NSIs which are the higher-level entities sharing one NSSI being the shared lower-level entity are all deactivated, and may maintain the NSSI in the active state if all of the NSIs sharing the NSSI are not deactivated (e.g., an embodiment of
Hereafter, according to various embodiments, operations for selectively activating and/or deactivating entities of different levels in the network slicing environment of the wireless communication system are described in greater detail with reference to the drawings. The illustrated operations may be performed in sequence, but not necessarily. For example, the order of the operations may be altered, and at least two operations may be performed in parallel.
At least some of the operations for selectively activating and/or deactivating entities of different levels to be explained according to various embodiments may correspond to each other or may be performed in combination. In various embodiments, at least one of the illustrated operations may be omitted, the order of some operations may be altered, or other operation may be added.
Referring to
A first state 405 of
According to an embodiment, each entity 411, 412, and 413 may be managed by a management system of a corresponding level. For example, the entity_1 411 and the entity_2 412 which are the N+1-level entities may be managed by the N+1-level management system 402 shown in
Referring to
According to an embodiment, the management node 201 of
According to an embodiment, the entity_1 411, the entity_2 412 and the entity_3 413 may be deactivated (e.g., the first state 402 of
For example, the UE 110 of the user may concurrently connect to one or more network slice instances via the RAN 120 according to the provided service. If the UE 110 transmits user's service requirement information requested by the UE 110 to the CN 200 to be served from a specific network slice instance, the CN 200 may select an adequate network slice instance based on the received information. As the network slice instance is selected, the management systems 401 and 402 of the CN 200 may prepare in advance for immediate use by instantiating and provision corresponding entities, and allocating, placing, or distributing resources for the user's service requirement information. Even though the entities are instantiated and provisioned, the user may not be served (e.g., link blocking) before the activation. As the entities are instantiated and provisioned and then activated, the user may be served (e.g., link connection).
In operation 410, the N+1-level management system 402 may transmit an activation request of the entity_3 413 for the entity_1 411 to the N-level management system 401.
In operation 420, the N-level management system 401 may selectively activate the entity_3 413 in response to the activation request received in operation 410. By activating the entity_3 413 for the entity_1 411, the N-level management system 401 may selectively (or partially) activate only some constituent related to the entity_1 411 among the entity_3 constituents 414, and maintain other constituents in the inactive state.
In operation 430, the N-level management system 401 may transmit an OK response for the activation request of operation 410 to the N+1-level management system 402.
By activating the entity_3413 for the entity_1 411 in operation 430, the entity_3 413 shared by the entity_1 411 and the entity_2 412 may be selectively activated only for the entity_1 411 (e.g., the second state 406 of
In a first state 505 of
According to an embodiment, the management node 201 may include the N-level management system 401 of
Referring to
According to an embodiment, the entity_1 411 and the entity_2 412 may be activated, and the shared entity_3 413 may be activated as a whole for both of the entity_1 411 and the entity_2 412 (e.g., the first state 505 of
In operation 510, the N+1-level management system 402 may transmit a deactivation request of the entity_3 413 for the entity_1 411 to the N-level management system 401.
In operation 520, the N-level management system 401 may selectively deactivate the entity_3 413 in response to the deactivation request received in operation 510. By deactivating the entity_3 413 for the entity_1 411, the N-level management system 401 may selectively (or partially) deactivate only some constituent(s) related to the entity_1 411 among the constituents of the entity_3 413, and maintain other constituents in the active state.
In operation 530, the N-level management system 401 may transmit an OK response for the deactivation request of operation 510 to the N+1-level management system 402.
By deactivating the entity_3 413 for the entity_1 411 in operation 530, the entity_3 413 shared by the entity_1 411 and the entity_2 412 may be selectively deactivated only for the entity_1 411 (e.g., the second state 506 of
The embodiment of
In a first state 605 of
Referring to
In an embodiment, the NSI 1 611, the NSI 2 612 and the shared NSSI 613 may be deactivated (e.g., the first state 605 of
In operation 610, the NSMF 602 for managing the NSI 1 611 and the NSI 2 612 may transmit an activation request of the NSSI 613 for the NSI 1 611 to the NSSMF 601 managing the shared NSI 3 613.
In operation 620, the NSSMF 601 may selectively activate the NSSI 613 in response to the activation request received in operation 610. By activating the NSSI 613 for the NSI 1 611, the NSSMF 601 may selectively (or partially) activate only some constituent related to the NSI 1 611 among the NSSI constituents 614, and maintain other constituents in the inactive state.
In operation 630, the NSSMF 601 may transmit an OK response for the activation request of operation 610 to the NSMF 602.
By activating the NSSI 613 for the NSI 1 611 in operation 630, the NSSI 613 shared by the NSI 1 611 and the NSI 2 612 may be selectively activated only for the NSI 1 611 (e.g., the second state 606 of
According to an embodiment, the CN of the wireless communication system may include a plurality of management systems. Higher-level (e.g., N+1-level) entities sharing a lower-level (e.g., N-level) entity may be managed by different management systems. In this case, the selective activation performed on the higher-level entity managed by one management system may not affect other higher-level entity managed by other management system.
Referring to
Referring to
In an embodiment, the entity_1 through the entity_N of the N+1 level, and the entity_X of the N level may be already instantiated and provisioned but may not serve users (the inactive state).
In operation 710, the NSMF 702 managing the entity_1 may transmit an entity_X activation request for the entity_1 to the NSSMF 701 managing the entity_X.
In operation 720, the NSSMF 701 may selectively activate the entity_X in response to the activation request received in operation 710. By activating the entity_X for the entity_1, the NSSMF 701 may selectively (or partially) activate only some constituent related to the entity_1 among entity_X constituents, and maintain other constituents in the inactive state.
In operation 730, the NSSMF 701 may transmit an OK response for the activation request of operation 710 to the NSMF 702.
By activating the entity_X for the entity_1 in operation 730, the entity_X shared by the entity_1 and the entity_N may be selectively activated only for the entity_1. Thus, the entity_1 may be activated to provide the service, and the entity_2 through the entity_N may be maintained in the inactive state.
As such, at the request of the NSMF 701 managing the entity_1, the NSSMF 701 may selectively (or partially) activate the entity_X shared by all of the entity_1 through the entity_N only for the entity_1. This selective activation operation of the N-level entity_X may be performed only on the N+1-level entity_1 managed by the NSMF(s) 703 which is one management system, and may not affect the entity_2 through the entity_N which are other N+1-level entities managed by the NSMF(s) 703 which is another management system.
According to an embodiment, multiple slicing entities may be managed by a single management system in a CN hierarchy of the wireless communication system.
Referring to
Referring to
In an embodiment, the entity_1, the entity_2, and the entity_3 may be already instantiated and provisioned, but may not serve users (the inactive state).
In operation 711, the management function 705 managing the entity_1, the entity_2, and the shared entity_3 may detect entity_3 activation request occurrence for the entity_1.
In operation 721, the management function 705 may selectively activate the entity_3 in response to the activation request detected in operation 711. By activating the entity_3 for the entity_1, the management function 705 may selectively (or partially) activate only some constituent related to the entity_1 among the entity_3 constituents, and maintain other constituents in the inactive state.
In operation 731, the management function 705 may feed an OK response back for the activation request occurred operation 711. By activating the entity_3 for the entity_1 in operation 731, the entity_3 shared by the entity_1 and the entity_2 may be selectively activated only for the entity_1. Hence, the entity_1 may be activated to provide the service, and the entity_2 may be maintained in the inactive state.
According to an embodiment, support of a lower-level (or lower-layer) management system (e.g., an EMS 803 of
According to an embodiment, the NSSI may group constituent MFs (or managed function instances (MFIs)) which are configurable entities. For the whole activation of the NSSI, it may be necessary to configure all the configurable MFs which are the lower-level entities. The selective (or partial) activation of the NSSI may be implemented with a scheme which configures only some of the configurable MFs. In an embodiment, the selective activation of the NSSI lower level may be supported.
Referring to
Referring to
In an embodiment, the NSI 1 and the NSI 2 which are the N+1-level entities may be already instantiated and provisioned but may not serve users (the inactive state).
In operation 811, the NSMF 802 managing the NSI 1 and an NSI 2 may transmit an NSSI activation request for the NSI 1 to the NSSMF 801 managing the NSSI.
In an embodiment, the NSSMF 801 may perform the selective NSSI activation operation in response to the activation request received in operation 811. The selective NSSI activation operation may include operation 812, operation 813, operation 814, operation 815 and operation 816.
In operation 812, the NSSMF 801 may transmit an MF activation request for the NSSI 1 to the EMS 803 which manages the MFs 805. In operation 813, the EMS 803 may configure an MF to be activated for the NSI 1 with the scheme for selectively switching some of the MFs 805. In operation 814 and operation 815, the EMS 803 may receive an OK signal notifying MF configuration complete to be activated for the NSI 1 from the MFs 805 and forward it to the NSSMF 801. In operation 816, upon receiving the OK signal from the EMS 803, the NSSMF 801 may activate the NSSI for the NSI 1.
In operation 817, the NSSMF 801 may transmit an OK response for the activation request of operation 812 to the NSMF 802.
Through the above process, the MFs 805 which are the lower-level entities of the NSSI may be selectively activated only for the NSI 1. Hence, the NSSI which is the higher-level entity of the MFs 805 may be also selectively activated only for the NSI 1. According to the selective activation of the NSSI, the NSI 1 may be activated to switch to provide the service, and the NSI 2 may be maintained in the inactive state.
Referring to
In an embodiment, the NSI 1, the NSI 2, the NSSI and the MFs may be already instantiated and provisioned to serve the users (the active state).
In operation 821, the NSMF 802 managing the NSI 1 and an NSI 2 may transmit an NSSI deactivation request for the NSI 1 to the NSSMF 801 which manages the NSSI.
In an embodiment, the NSSMF 801 may perform the selective NSSI deactivation operation in response to the deactivation request received in operation 811. The selective NSSI deactivation operation may include operation 822, operation 823, operation 824, operation 825 and operation 826.
In operation 822, the NSSMF 801 may transmit an MF activation request for the NSSI 1 to the EMS 803 which manages the MFs 805. In operation 823, the EMS 803 may configure an MF to be activated for the NSI 1 with the scheme for selectively switching some of the MFs 805. In operation 824 and operation 825, the EMS 803 may receive an OK signal notifying MF configuration complete to be activated for the NSI 1 from the MFs 805 and forward it to the NSSMF 801. In operation 826, the NSSMF 801, upon receiving the OK signal from the EMS 803, may activate the NSSI for the NSI 1.
In operation 827, the NSSMF 801 may transmit an OK response for the activation request of operation 812 to the NSMF 802.
Through the above process, the MFs 805 which is the lower-level entity of the NSSI may be selectively activated only for the NSI 1. Hence, the NSSI which is the higher-level entity of the MFs 805 may be also selectively activated only for the NSI 1. According to the selective activation of the NSSI, the NSI 1 may be activated to provide the service, and the NSI 2 may be maintained in the inactive state.
Some communication standards may limit the selective switch scheme by the lower-level entity management system (e.g., the EMS). In this case, the selective activation of the shared entity may be implemented by completing configuration.
According to an embodiment, to implement the selective activation of the shared entity, only partially configuring the MFs may be included, as part of the instantiation and provisioning operations. In an embodiment, the selective activation of the NSSI level may be supported. For example, only some of the configurable MFs (N−1 level) which are the lower-level entities of the NSSI (N level) may be partially configured, and others may miss configuration. Due to the missing configuration, corresponding MFs may not serve users.
Referring to
Referring to
In an embodiment, the NSI 1 and the NSI 2 which are the N+1-level entities may be already instantiated and provisioned. The MFs are already instantiated and provisioned, but may miss a portion which enables the service in the configuration and may not serve the users (the inactive state).
In operation 911, the NSMF 802 managing the NSI 1 and an NSI 2 may transmit an NSSI activation request for the NSI 1 to the NSSMF 801 which manages the NSSI.
In an embodiment, the NSSMF 801 may perform the selective NSSI activation operation in response to the activation request received in operation 911. The selective NSSI activation operation may include operation 912, operation 913, operation 914, operation 915 and operation 916.
In operation 912, the NSSMF 801 may transmit an MF configuration request to the EMS 803 which manages the MFs 805. Th request may request to complete missing configuration. In operation 913, the EMS 903 may configure an MF with the scheme for adding some of the MFs 805 to the configuration and missing others. In operation 914 and operation 915, the EMS 903 may receive an OK signal notifying the missing configuration complete from the MFs 805 and forward it to the NSSMF 801. In operation 916, upon receiving the OK signal from the EMS 903, the NSSMF 801 may activate the NSSI for the NSI 1.
In operation 917, the NSSMF 801 may transmit an OK response for the activation request of operation 911 to the NSMF 802.
Through the above process, the MFs 805 which is the lower-level entity of the NSSI may be selectively activated only for the NSI 1. Hence, the NSSI which is the higher-level entity of the MFs 805 may be also selectively activated only for the NSI 1. By the selective activation of the NSSI, the NSI 1 may be activated to provide the service, and the NSI 2 may be maintained in the inactive state.
According to an embodiment, to implement the selective deactivation of the NSSI which is the shared entity, removing some configuration of the MFs constituting the NSSI may be included. The corresponding operation may prevent the MFs from serving users with respect to the NSSI which is the higher-level entity.
Referring to
In an embodiment, the NSI 1, the NSI 2, the NSSI and the MFs may be already instantiated and provisioned to serve the users (the active state).
In operation 921, the NSMF 802 managing the NSI 1 and the NSI 2 may transmit an NSSI deactivation request for the NSI 1 to the NSSMF 801 which manages the NSSI.
In an embodiment, the NSSMF 801 may perform the selective NSSI deactivation operation in response to the deactivation request received in operation 811. The selective NSSI deactivation operation may include operation 922, operation 923, operation 924, operation 925 and operation 926.
In operation 922, the NSSMF 801 may transmit an MF reconfiguration request (or a request for removing partial configuration) to the EMS 803 which manages the MFs 805. In operation 923, the EMS 803 may reconfigure the MF by removing some of the MFs 805 in the configuration. In operation 924 and operation 925, the EMS 903 may receive an OK signal notifying MF reconfiguration complete (or partial configuration removing complete) from the MFs 805 and forward it to the NSSMF 801. In operation 926, the NSSMF 801, upon receiving the OK signal from the EMS 903, may deactivate the NSSI for the NSI 1. In operation 927, the NSSMF 801 may transmit an OK response for the deactivation request of operation 912 to the NSMF 802.
Through the above process, the MFs 805 which are the lower-level entities of the NSSI may be selectively deactivated only for the NSI 1. Hence, the NSSI which is the higher-level entity of the MFs 805 may be also selectively deactivated only for the NSI 1. According to the selective deactivation of the NSSI, the NSI 1 may be deactivated not to provide the service, and the NSI 2 may be maintained in the active state.
Some communication standards may limit the selective switch scheme by the lower-level entity management system (e.g., the EMS). In this case, the selective activation of the NSSI or the shared entity may be implemented by blocking or unblocking the network communication.
According to an embodiment, to implement the selective activation of the shared entity, an operation for blocking or unblocking the network communication may be included, as part of the instantiation and provisioning operations. In an embodiment, the selective activation of the NSSI level may be supported. For example, a network connectivity part of the NSSI or the MF may be modified, for the selective activation of the NSSI level. The NSSI or MF instantiation and provisioning may leave corresponding entities fully operable, but the network part of the configuration may be missed or altered. Such network configuration may interrupt communication with other constituents of the service not to serve the users. The activation operation may complete missing configuration or modify missing configuration. This activation operation may activate nominal connectivity for a specific higher-level entity, and thus allow the NSSI or the MF to fully serve the user.
Referring to
Referring to
In an embodiment, the NSI 1, the NSI 2, the NSSI, and the MFs may be all instantiated and provisioned but may not serve users (the inactive state). The network 1004 (e.g., a specific network slice or subnet) may be configured to block every service traffic (or communication) for the NSI 1 and the NSI 2.
In operation 1011, the NSMF 1002 managing the NSI 1 and the NSI 2 may transmit an NSSI activation request for the NSI 1 to the NSSMF 1001 which manages the NSSI.
In an embodiment, the NSSMF 1001 may perform the selective NSSI activation operation in response to the activation request received in operation 1011. The selective NSSI activation operation may include operation 1012, operation 1013, operation 1014, operation 1015 and operation 1016.
In operation 1012, the NSSMF 1001 may transmit a network reconfiguration request to the network controller 1003, to enable the service traffic (or communication) for the NSI 1. In operation 1013, the network controller 1003 may reconfigure the network 1004 to unlock the service traffic for the NSI 1. In operation 1014 and operation 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, upon receiving the OK signal from the network controller 1003, the NSSMF 1001 may activate the NSSI for the NSI 1.
In operation 1017, the NSSMF 1001 may transmit an OK response for the activation request of operation 1011 to the NSMF 1002.
Through the above process, the NSI 1 may be activated, and the NSI 2 may not be activated. The shared NSSI may be selectively (or partially) activated only for the NSI 1. The reconfiguration of the network 1004 may enable the communication only for the service related to the NSI 1.
Referring to
In an embodiment, the NSI 1, the NSI 2, the NSSI and the MFs may be all instantiated and provisioned to serve the users (the active state).
In operation 1021, the NSMF 1002 managing the NSI 1 and an NSI 2 may transmit an NSSI deactivation request for the NSI 1 to the NSSMF 1001 which manages the NSSI.
In an embodiment, the NSSMF 801 may perform the selective NSSI deactivation operation in response to the deactivation request received in operation 1021. The selective NSSI deactivation operation may include operation 1022, operation 1023, operation 1024, operation 1025 and operation 1026.
In operation 1022, the NSSMF 1001 may transmit an MF reconfiguration request to the network controller 1003, to disable the service traffic (or communication) for the NSI 1. In operation 1023, the network controller 1003 may reconfigure the MF to block the service traffic for the NSI 1. In operation 1024 and operation 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 upon receiving the OK signal from the network controller 1003 may deactivate the NSSI for the NSI 1.
In operation 1027, the NSSMF 1001 may transmit an OK response for the deactivation request of operation 1021 to the NSMF 1002.
Through the above process, the NSI 1 may be deactivated, and the NSI 2 may be maintained in the active state. The shared NSSI may be selectively (or partially) deactivated only for the NSI 1. The reconfiguration of the network 1004 may disable the communication only for the service related to the NSI 1.
According to an embodiment, the network communication blocking (or service traffic blocking) scheme may, for example, be implemented as follows.
According to an embodiment, the network communication unblocking (or service traffic unblocking) scheme may, for example, be implemented as follows.
Control on the deactivation may be improved using the NSMF request consensus scheme if some communication standards do not support the selective per-NSI activation and deactivation schemes. A higher-level management node (e.g., an NSMF) may not know about other higher-level management node (e.g., another NSMF) which shares a lower-level entity (e.g., an NSSI). In this case, each higher-level management node may request the deactivation from the lower-level management node (e.g., the NSSMF) only based on an intended state of its managed entity (e.g., the NSI). The lower-level management node (e.g., the NSSMF) managing the shared entity (e.g., an NSSMF) may prevent its managed entity (e.g., the NSSI) from deactivating while some of higher-level entities are still activated.
Referring to
In a first state 1106 of
Referring to
Referring to
The NSI 1 activation operation 1131 may include operation 1121 and operation 1122.
In operation 1121, the NSMF 1 1102 managing the NSI 1 1111 may transmit an activation request of the NSSI 1113 to the NSSMF 1101 which manages the NSSI 1113 which is the shared lower-level entity. Upon receiving the activation request, the NSSMF 1101 for managing the NSSI 1113 which is the shared lower-level entity may store information (e.g., a system ID of the NSMF 1 1102 and/or an entity ID of the NSI 1) of the NSMF 1 1102 transmitting the request to activate the NSSI 1113 instead of the NSI 1. If the managed NSSI 1113 is already deactivated, the NSSMF 1101 may perform the NSSI activation in response to the request. In operation 1122, the NSSMF 1101 may transmit an OK response for the activation request of operation 1121 to the NSMF 1 1102.
The NSI 2 activation operation 1132 may include operation 1123 and operation 1124.
In operation 1123, the NSMF 2 1103 managing the NSI 2 1112 may transmit an activation request of the NSSI 1113 to the NSSMF 1101 which manages the shared NSSI 1113. Upon receiving the activation request, the NSSMF 110 may store information (e.g., a system ID of the NSMF 2 1103 and/or an entity ID of the NSI 2) of the NSMF 2 1103 transmitting the request to activate the managed NSSI 1113 instead of the NSI 2. In operation 1124, the NSSMF 1101 may transmit an OK response for the activation request of operation 1123 to the NSMF 2 1103.
Referring to
The NSI 1 deactivation operation 1133 may include operation 1125 and operation 1126.
In operation 1125, the NSMF 1 1102 may transmit a deactivation request of the NSSI 1113 to the NSSMF 1101. Upon receiving the deactivation request, the NSSMF 1101 which is the lower-level management node may store information (e.g., a system ID of the NSMF 1 1102 and/or an entity ID of the NSI 1 1111) of the NSMF 1 1102 transmitting the request to activate the NSSI 1113 instead of the NSI 1. In operation 1126, the NSSMF 1101 may transmit an OK response for the deactivation request of operation 1125 to the NSMF 1 1102.
The NSI 2 deactivation operation 1134 may include operation 1127 and operation 1128.
In operation 1127, the NSMF 1 1102 may transmit a deactivation request of the NSSI 1113 to the NSSMF 1101. If receiving the deactivation request from the NSMF 1 1102, the NSSMF 1101 may delete the information (e.g., the system ID of the NSMF 1 1102 and/or the NSI 1 1111) of the NSMF 1 1102 stored for the activation. If the corresponding information is deleted all and there is no more intention to activate the NSMF 1 1102 and the NSMF 2 1103 for the management, the NSSMF 1101 may perform the deactivation of the NSSI 1113 shared by the NSMF 1 1102 and the NSMF 2 1103. In operation 1128, the NSSMF 1101 may transmit an OK response for the deactivation request of operation 1127 to the NSMF 1102.
A method of operating a management node according to various example embodiments may include a method of operating a management node in a wireless communication system with a network slicing environment. The method may include, as one or more of multiple higher-level entities sharing a lower-level entity managed by the management node are activated: receiving an activation request of the shared lower-level entity, and activating the shared lower-level entity for the one or more activated higher-level entities, in response to the activation request.
According to various example embodiments, receiving the activation request may include, based on the higher-level entities being managed by different second management nodes, receiving the activation request from a management node which manages the one or more activated higher-level entities among the second management nodes.
According to various example embodiments, receiving the activation request may include, based on multi-level entities including the higher-level entities and the lower-level entities being managed by the management node, detecting occurrence of the activation request inside the management node.
According to various example embodiments, the management node may include a network slice subnet management function (NSSMF) for managing a network slice subnet instance (NSSI) including the lower-level entity. Receiving the activation request may include receiving, at the NSSMF, from a network slice management function (NSMF) which manages network slice instances (NSIs) which are the higher-level entities, an activation request of the NSSI for a specific NSI of the NSIs. Activating may include partially activating, at the NSSMF, the NSSI shared by the NSIs only for the specific NSI.
According to various example embodiments, partially activating, at the NSSMF, the NSSI shared by the NSIs for the specific NSI may include transmitting, at the NSSMF, an MF activation request for the specific NSI to an EMS which managed MFs, to allow the EMS to configure some of the MFs as an MF to activate for the specific NSI in response to the MF activation request.
According to various example embodiments, partially activating, at the NSSMF, the NSSI shared by the NSIs for the specific NSI may include transmitting, at the NSSMF, an MF configuration request for the specific NSI to the EMS which manages the MFs, to allow the EMS to configure an MF for the specific NSI by missing some of the MFs in response to the MF configuration request.
According to various example embodiments, partially activating, at the NSSMF, the NSSI shared by the NSIs for the specific NSI may include transmitting, at the NSSMF, a network reconfiguration request for enabling network communication related to the specific NSI to a network controller, to allow the network controller to reconfigure a network in response to the network reconfiguration request.
According to various example embodiments, activating may include activating the shared lower-level entity only for an activated entity set among the higher-level entities, and deactivating the shared lower-level entity for other deactivated entity set among the higher-level entities.
According to various example embodiments, the method may include, as one or more of the higher-level entities are deactivated, receiving a deactivation request of the shared lower-level entity, and in response to the deactivation request, deactivating the shard lower-level entity for the one or more deactivated higher-level entities.
According to various example embodiments, the management node may include the NSSMF for managing the NSSI which is the lower-level entity. Deactivating may include identifying at the NSSMF whether NSIs sharing one NSSI are all deactivated, deactivating the NSSI if the NSIs are all deactivated, and maintaining the NSSI in an active state if the NSIs are not all deactivated.
A management node according to various example embodiments may include a management node in a wireless communication system with a network slicing environment. The management node may include: a transceiver and at least one processor, comprising processing circuitry, connected to the transceiver. At least one processor may be configured to, as one or more of multiple higher-level entities sharing a lower-level entity managed by the management node are activated: receive an activation request of the shared lower-level entity, and in response to the activation request, activate the shared lower-level entity for the one or more activated higher-level entities.
According to various example embodiments, at least one processor may be configured to, based on the higher-level entities being managed by different second management nodes, receive the activation request from a management node configured to manage the one or more activated higher-level entities among the second management nodes.
According to various example embodiments, at least one processor may be configured to, based on multi-level entities including the higher-level entities and the lower-level entities being managed by the management node, detect occurrence of the activation request inside the management node.
According to various example embodiments, the management node may include an NSSMF configured to manage an NSSI. At least one processor may be configured to: receive from an NSMF configured to manage NSIs including the higher-level entities, an activation request of the NSSI for a specific NSI of the NSIs, and partially activate the NSSI shared by the NSIs for the specific NSI.
According to various example embodiments, at least one processor may be configured to: control the management node to transmit an MF activation request for the specific NSI to an EMS which managed MFs, to thus allow the EMS to configure some of the MFs as an MF to activate for the specific NSI in response to the MF activation request.
According to various example embodiments, at least one processor may be configured to: control the management node to transmit an MF configuration request for the specific NSI to the EMS which manages the MFs, to thus allow the EMS to configure an MF for the specific NSI by missing some of the MFs in response to the MF configuration request.
According to various example embodiments, at least one processor may be configured to: control the management node to transmit a network reconfiguration request for enabling network communication related to the specific NSI to a network controller, to thus allow the network controller to reconfigure a network in response to the network reconfiguration request.
According to various example embodiments, at least one processor may be configured to: activate the shared lower-level entity for an activated entity set among the higher-level entities, and deactivate the shared lower-level entity for other deactivated entity set among the higher-level entities.
According to various example embodiments, at least one processor may be configured to, as one or more of the higher-level entities are deactivated: receive a deactivation request of the shared lower-level entity, and in response to the deactivation request, deactivate the shard lower-level entity for one or more deactivated higher-level entities.
According to various example embodiments, the management node may include: an NSSMF configured to manage the NSSI which is the lower-level entity. At least one processor may be configured to: identify whether NSIs which are the higher-level entities sharing one NSSI are all deactivated, deactivate the NSSI based on the NSIs all being deactivated, and maintain the NSSI in an active state based on the NSIs not all being deactivated.
According to various example embodiments of the present disclosure, the selective activation and/or deactivation may be implemented in an appropriate manner for the slicing entity (or the shared entity) required for the service under the network slicing environment of the wireless communication system. Hence, compared to activating and/or deactivating the slicing entities as a whole, it is possible to reduce a time taken to configure necessary slicing entities for each network slice, and to improve service quality.
While the disclosure has been illustrated and described with reference to various example embodiments, it will be understood that the various example embodiments are intended to be illustrative, not limiting. It will be further understood by those skilled in the art that various changes in form and detail may be made without departing from the true spirit and full scope of the disclosure, including the appended claims and their equivalents. It will also be understood that any of the embodiment(s) described herein may be used in conjunction with any other embodiment(s) described herein.
| Number | Date | Country | Kind |
|---|---|---|---|
| 10-2023-0053647 | Apr 2023 | KR | national |
| 10-2023-0059371 | May 2023 | KR | national |
This application is a continuation of International Application No. PCT/KR2024/003670 designating the United States, filed on Mar. 25, 2024, in the Korean Intellectual Property Receiving Office and claiming priority to Korean Patent Application Nos. 10-2023-0053647, filed on Apr. 24, 2023, and 10-2023-0059371, filed on May 8, 2023, in the Korean Intellectual Property Office, the disclosures of each of which are incorporated by reference herein in their entireties.
| Number | Date | Country | |
|---|---|---|---|
| Parent | PCT/KR2024/003670 | Mar 2024 | WO |
| Child | 18677044 | US |
