KR102657312B1 - Method for managing resources of network slicing in communication system and apparatus for the same - Google Patents

Abstract

A method and apparatus for resource management of network slicing in a communication system are disclosed. A method of operating a first device includes receiving a first message requesting capacity planning of a network slice from a second device; Obtaining information necessary for the capacity planning; transmitting a second message containing the necessary information to a third device supporting the capacity planning function; Receiving a third message including a result of performing the capacity planning from the third device; and performing a reallocation or modification operation of the network slice based on a result of the capacity planning. Therefore, network resources/performance can be optimized in the communication system.

Description

Method and apparatus for resource management of network slicing in a communication system {METHOD FOR MANAGING RESOURCES OF NETWORK SLICING IN COMMUNICATION SYSTEM AND APPARATUS FOR THE SAME}

The present invention relates to network slicing technology, and more specifically, to technology for managing network slicing resources in a communication system.

A communication system may include a core network, a base station (e.g., a macro base station, a small base station, a relay, etc.), and a user equipment (UE). In a communication system that supports 4G communication technology (e.g., long term evolution (LTE) technology), the core network includes a mobility management entity (MME), serving gateway (SGW), and packet data network (PDN) gateway (PGW). It can be included. In a communication system that supports 5G communication technology (e.g., new radio (NR) technology), the core network may include an access and mobility function (AMF), a user plane function (UPF), a session management function (SMF), etc. there is.

Communication between the base station and the UE uses various radio access technologies (RAT) (e.g., 4G communication technology, 5G communication technology, wireless broadband (WiBro) technology, wireless local area network (WLAN) technology, and wireless personal area network (WPAN) technology. etc.). The base station can be connected to the core network via wired backhaul or wireless backhaul. For example, the base station may transmit data and control information received from the terminal to the core network through wired backhaul or wireless backhaul. Additionally, the base station can receive data and control information from the core network through wired backhaul or wireless backhaul.

Meanwhile, network slicing technology may be applied to communication systems. The purpose of network slicing technology is to efficiently and optimally use the resources of the communication system to minimize CAPEX (capital expenditure) and OPEX (operating expenditure). To this end, methods will be needed to optimally manage network slicing resources in communication systems.

The purpose of the present invention to solve the above problems is to provide a method and device for optimally managing resources for network slicing.

A method of operating a first device according to a first embodiment of the present invention for achieving the above object includes receiving a first message requesting capacity planning of a network slice from a second device; Obtaining information necessary for the capacity planning; transmitting a second message containing the necessary information to a third device supporting the capacity planning function; Receiving a third message including a result of performing the capacity planning from the third device; and performing a reallocation or modification operation of the network slice based on a result of the capacity planning.

Here, the method of operating the first device may further include checking the feasibility of the network slice when the first message is received, and the result of checking the feasibility of the network slice is the 2 Can be included in the message.

Here, the operating method of the first device includes updating network capacity availability information based on a result of a reallocation or modification operation of the network slice; And it may further include transmitting a fourth message including updated network capacity availability information to the second device.

Here, the network slice may be NSI or NSSI.

Here, the performance result of the capacity planning is at least one of an indicator requesting reallocation of the NSI, an indicator requesting modification of the NSI, an indicator requesting reallocation of the NSSI, and an indicator requesting modification of the NSSI. It can contain one.

Here, the necessary information may include at least one of topology, capacity information, throughput, packet loss rate, and link delay for the network slice.

Here, the first device may be a device operating as NSMS_P, the second device may be a device operating as NSMS_C, and the third device may be a device operating as MS_P.

Here, when the capacity planning is performed, network resources and functions constituting the network slice can be optimized.

A first device according to a second embodiment of the present invention for achieving the above object includes a first element supporting an NSMS function; a second element supporting the function of capacity planning; and a memory storing at least one command executed by the first element and the second element, wherein the at least one command includes a first message requesting the capacity planning of a network slice by the first element. receive from the second device; the first element obtains information necessary for the capacity planning; the first element transmits a second message containing the necessary information to the second element; the second element performs the capacity planning for the network slice based on the second message; The second element transmits a third message including a result of performing the capacity planning to the first element; And the first element is executed to perform a reallocation or modification operation of the network slice based on the performance result of the capacity planning included in the third message.

Here, the at least one command may be further executed to allow the first element to check the feasibility of the network slice when the first message is received, and the result of checking the feasibility of the network slice is the first element. 2 Can be included in the message.

Here, the at least one command causes the first element to update network capacity availability information based on a result of a reallocation or modification operation of the network slice; And the first element may be further executed to transmit a fourth message including updated network capacity availability information to the second device.

Here, the network slice may be NSI or NSSI.

Here, the performance result of the capacity planning is at least one of an indicator requesting reallocation of the NSI, an indicator requesting modification of the NSI, an indicator requesting reallocation of the NSSI, and an indicator requesting modification of the NSSI. It can contain one.

Here, the necessary information may include at least one of topology, capacity information, throughput, packet loss rate, and link delay for the network slice.

Here, the first device may be a device operating as NSMS_P, and the second device may be a device operating as NSMS_C.

According to the present invention, NSMS_C (network slice management service consumer) can request NSMS_P (NSMS provider) to perform a capacity planning procedure, and NSMS_P works with MS_P (management service provider) at the request of NSMS_C. Capacity planning procedures can be performed. Through the capacity planning procedure, related network resources/functions may be created/removed/changed to optimize utilization of a network slice (e.g., network slice instance (NSI) or network slice subnet instance (NSSI)). Therefore, the efficiency of using network resources/functions in a communication system that supports network slicing can be optimally improved.

1 is a conceptual diagram showing a first embodiment of a communication system supporting network slicing.
Figure 2 is a block diagram showing a first embodiment of a communication node constituting a communication system.
Figure 3 is a conceptual diagram showing a first embodiment of NSI in a communication system.
Figure 4 is a conceptual diagram showing a first embodiment of NSSI in a communication system.
Figure 5 is a flowchart showing a first embodiment of a method for generating NSSI in a communication system.
Figure 6 is a flowchart showing a first embodiment of a network slice capacity planning method in a communication system.
Figure 7 is a flowchart showing a first embodiment of an NSI allocation procedure in a communication system.
Figure 8 is a flowchart showing a first embodiment of an NSSI allocation procedure in a communication system.
9 is a flow chart illustrating a first embodiment of an NSSI modification procedure in a communication system.

Since the present invention can make various changes and have various embodiments, specific embodiments will be illustrated in the drawings and described in detail. However, this is not intended to limit the present invention to specific embodiments, and should be understood to include all changes, equivalents, and substitutes included in the spirit and technical scope of the present invention.

Terms such as first, second, etc. may be used to describe various components, but the components should not be limited by the terms. The above terms are used only for the purpose of distinguishing one component from another. For example, a first component may be named a second component, and similarly, the second component may also be named a first component without departing from the scope of the present invention. The term and/or includes any of a plurality of related stated items or a combination of a plurality of related stated items.

When a component is said to be "connected" or "connected" to another component, it is understood that it may be directly connected to or connected to the other component, but that other components may exist in between. It should be. On the other hand, when it is mentioned that a component is “directly connected” or “directly connected” to another component, it should be understood that there are no other components in between.

The terms used in this application are only used to describe specific embodiments and are not intended to limit the invention. Singular expressions include plural expressions unless the context clearly dictates otherwise. In this application, terms such as “comprise” or “have” are intended to designate the presence of features, numbers, steps, operations, components, parts, or combinations thereof described in the specification, but are not intended to indicate the presence of one or more other features. It should be understood that this does not exclude in advance the possibility of the existence or addition of elements, numbers, steps, operations, components, parts, or combinations thereof.

Unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by a person of ordinary skill in the technical field to which the present invention pertains. Terms defined in commonly used dictionaries should be interpreted as having a meaning consistent with the meaning in the context of the related technology, and should not be interpreted in an ideal or excessively formal sense unless explicitly defined in the present application. No.

Hereinafter, preferred embodiments of the present invention will be described in more detail with reference to the attached drawings. In order to facilitate overall understanding when describing the present invention, the same reference numerals are used for the same components in the drawings, and duplicate descriptions of the same components are omitted.

A communication system to which embodiments according to the present invention are applied will be described. The communication systems to which the embodiments according to the present invention are applied are not limited to those described below, and the embodiments according to the present invention can be applied to various communication systems. Here, communication system may be used in the same sense as communication network.

1 is a conceptual diagram illustrating a first embodiment of a communication system supporting network slicing.

Referring to FIG. 1, the communication system 100 includes a core network 110, an access network (AN) (e.g., radio access network (RAN)) 120, a data network (DN) 130, and a UE ( user equipment) (140). The core network 110 includes an access and mobility management function (AMF) (110-1), a user plane function (UPF) (110-2), a session management function (SMF) (110-3), and an authentication server function (AUSF). (110-4), network exposure function (NEF) (110-5), network repository function (NRF) (110-6), policy control function (PCF) (110-7), user data management (UDM) (110) -8), AF (application function) (110-9), and NSSF (network slice selection function) (110-10). Here, NSSF 110-10 may be used to support selection of network slices. In the embodiments below, a network slice may indicate a network slice instance (NSI) or a network slice subnet instance (NSSI).

Network functions 110-1 to 110-10 constituting the core network 110 may be performed by one or more physical devices. Alternatively, the network functions 110-1 to 110-10 constituting the core network 110 may be implemented as an instance or virtual function running on a physical device.

The core network 110 can be classified into a control plane and a user plane. Control planes can be classified into common control planes and slice specific control planes. AMF 110-1, UPF 110-2, AUSF 110-4, UDM 110-8, and NSSF 110-10 may belong to a common control plane. SMF 110-3, NEF 110-5, NRF 110-6, and PCF 110-7 may belong to a common control plane or a slice-specific control plane. Network functions belonging to a common control plane may be shared by multiple NSIs or multiple NSSIs. Network functions belonging to a slice-specific control plane may be dedicated to a specific NSI or for a specific NSSI.

AMF (110-1) can perform the following functions.

- Termination of the RAN CP (control plane) interface (N2)

- NAS (non access stratum) interface (N1) termination, NAS encryption and integrity protection

- Registration management

- connection management

- Reachability management

- Mobility management

- Lawful intercept of AMF events and L1 system interfaces

- Transparent proxy for SM message routing

- access authentication

- Access Authorization

- SEA (security anchor function)

- Security context management (SCM)

Meanwhile, in the communication system 100, communication between the AMF (110-1) and the NSSF (110-10) can be performed through the Ns interface, and the AMF (110-1) is linked to the NSSF (110-10) to Slicing-related operations can be performed. For example, NSI or NSSI may be selected based on the operation between AMF 110-1 and NSSF 110-10.

When network slicing technology is applied to the communication system 100, network resources/functions can be set as one independent network slice according to the required service. Therefore, the network operator can set network resources/functions specialized for services or users as network slices, and provide the network slices to users who have requested the service. Additionally, software defined networking (SDN)/network function virtualization (NFV) technology may be applied to the communication system 100, and network resources/functions may be virtualized accordingly.

Meanwhile, a communication node (eg, a device performing the network function shown in FIG. 1) included in the communication system 100 shown in FIG. 1 may be configured as follows.

Figure 2 is a block diagram showing a first embodiment of a communication node constituting a communication system.

Referring to FIG. 2, the communication node 200 may include at least one processor 210, a memory 220, and a transmitting and receiving device 230 that is connected to a network and performs communication. Additionally, the communication node 200 may further include an input interface device 240, an output interface device 250, a storage device 260, etc. Each component included in the communication node 200 is connected by a bus 270 and can communicate with each other.

However, each component included in the communication node 200 may be connected through an individual interface or individual bus centered on the processor 210, rather than the common bus 270. For example, the processor 210 may be connected to at least one of the memory 220, the transmission/reception device 230, the input interface device 240, the output interface device 250, and the storage device 260 through a dedicated interface. .

The processor 210 may execute a program command stored in at least one of the memory 220 and the storage device 260. The processor 210 may refer to a central processing unit (CPU), a graphics processing unit (GPU), or a dedicated processor on which methods according to embodiments of the present invention are performed. Each of the memory 220 and the storage device 260 may be comprised of at least one of a volatile storage medium and a non-volatile storage medium. For example, the memory 220 may be comprised of at least one of read only memory (ROM) and random access memory (RAM).

Next, resource management methods for network slicing in communication systems will be described. Even when a method (e.g., transmission or reception of a signal) performed in a first communication node among communication nodes is described, the corresponding second communication node is described as a method (e.g., transmitting or receiving a signal) corresponding to the method performed in the first communication node. For example, reception or transmission of a signal) can be performed. That is, when the operation of the UE is described, the corresponding base station can perform the operation corresponding to the operation of the UE. Conversely, when the operation of the base station is described, the corresponding UE may perform an operation corresponding to the operation of the base station.

Figure 3 is a conceptual diagram showing a first embodiment of NSI in a communication system.

Referring to FIG. 3, a network slice may be a logical network composed of network resources/functions necessary to provide specific network performance/characteristics to users. The network slice may be located in the RAN 320 and the core network (CN) 330. NSI may be a set of network resources/functions that provide the intended network slice service according to a template.

A plurality of NSIs may be assigned to each of the UEs 310-1 and 320-2. For example, NSI #1 to 2 may be assigned to UE #1 (310-1), and NSI #3 to 4 may be assigned to UE #2 (310-2). NSI #1 and #3 may be configured to provide enhanced mobile broadband (eMBB) services, and NSI #2 and #4 may be configured to provide Internet of things (IoT) services. NSI #1 to 4 may be set in the RAN 320 and CN 330, and each of NSI #1 to 4 may include multiple NSSIs.

NSI #1 may be composed of a RAN slice (e.g., a network resource/function constituting the RAN 320) and a CN slice (e.g., a network resource/function constituting the CN 330). A CN slice may include common control network functions (CCNF), slice-specific control network functions (SCNF), user plane functions (UPFs), and other network functions (NFs). Each of NSI #1 to 4 may include instances supporting one or more network functions to provide the required service. An instance that supports network functions may be referred to as a network function instance (NFI).

Each of the UEs 310-1 and 310-2 can access a plurality of NSIs through one RAN 320. In this case, NSI #1~2 may share some functionality of the control plane (e.g., AMF, NSSF), and NSI #3~4 may share some functionality of the control plane (e.g., AMF, NSSF). You can share it. The function of the control plane shared by NSIs assigned to one UE (310-1, 310-2) may be referred to as CCNF. AMF and NSSF included in CCNF can be shared by one or more NSIs according to the network operator's policy.

NSSF may be a network function that has NSI topology information for a public land mobile network (PLMN). For example, the NSSF can check the availability of a set of active NSI(s) corresponding to a registration area and can be an entry point to access a specific NSI. In addition, to select a target NSI based on at least one of a serving mobile virtual network operator (MVNO), an over the top (OTT) provider, the location of the UE, and a time window, the NSSF uses S-NSSAI (single -Slice-level service mapping operation for network slice selection assistance information may be supported.

Here, NSI may be selected from the NSI pool for a specific S-NSSAI for load balancing and redundancy. Slice level control rules can be set by the network operator. Additionally, NSSF can support statistical collection function for slice selection for the management system of the serving PLMN. The following parameters can be considered in the operation between NSSF and AMF.

Input parameters of NSSF may include accepted S-NSSAI. Additionally, the input parameters of the NSSF may include at least one of a past NSI list associated with the UE (310-1, 310-2) and a serving registration area of the UE (310-1, 310-2).

The output parameters of the NSSF may include information (eg, NSI ID (identifier)) of the NSI corresponding to the approved S-NSSAI. Here, the NSI may be a newly selected NSI based on the approved S-NSSAI. Additionally, the output parameters of the NSSF may include at least one of an Internet protocol (IP) address or fully qualified domain name (FQDN) of the new serving AMF, and an IP address or FQDN of the serving NRF selected for NSI.

Additionally, the PLMN may include NSI and NRF provisioned for discovery/selection of network functions. To allow the NRF to support discovery/selection operations of network functions with or without network slicing, the input parameters of the NSSF may include a logical network identifier as well as the type of the network function. The logical network identifier may indicate an NSI ID or a serving PLMN.

Figure 4 is a conceptual diagram showing a first embodiment of NSSI in a communication system.

Referring to FIG. 4, one or more NSIs for providing a service required by the UE may be selected from among the NSIs, and the selected one or more NSIs may be allocated to the UE. For example, multiple NSIs may be configured for a UE in a communication system. There may be one or more NFIs supporting the same network function within an NSI. If there are multiple NFIs supporting the same network function within the NSI, one NFI may be selected from among the multiple NFIs.

One NSI may be configured to provide one or more services and may be assigned to one or more UEs. NSI may be a network operator's service-specific resource/function group. NSI may include multiple NSSIs, and NSSI may be a set of network resources/functions to provide services required by the UE.

Figure 5 is a flowchart showing a first embodiment of a method for generating NSSI in a communication system.

Referring to FIG. 5, a communication node supporting NSSF shown in FIG. 1 may select one or more NSIs to provide the service required by the UE among NSIs predefined in the communication system (S510). For example, a communication node may select an NSI based on NSSAI. Additionally, the communication node may select an NSI based on at least one of the previous NSI assigned to the UE and the UE's serving registration area. When an NSI is selected, the communication node can output the ID of the selected NSI and the addresses of AMF and NRF according to the selected NSI.

The communication node may select one or more NFIs to provide the service required by the UE within the selected NSI (S520). The NFI may be selected based on the logical network identifier (eg, NSI ID or PLMN ID) and type of network function. Additionally, NFI may be selected considering the network operator's policy. The network operator's policies may include load balancing, resource optimization, energy efficiency, traffic optimization, etc. For example, if two SMFs exist in the NSI, the communication node can select the SMF that provides relatively high quality of service (QoS) among the two SMFs. Alternatively, the communication node may select the SMF corresponding to the UE's rate plan or the SMF corresponding to the UE's serving registration area among the two SMFs.

The communication node can generate NSSI consisting of the selected NFI and assign the NSSI to the UE (S530). Steps S510 to S530 described above may be performed by one or more communication nodes.

FIG. 6 is a flowchart illustrating a first embodiment of a capacity planning method of network slices (eg, NSI and NSSI) in a communication system.

Referring to FIG. 6, the communication system may include a network slice management service consumer (NSMS_C) 601, a network slice management service provider (NSMS_P) 602, and a management service provider (MS_P) 603. NSMS_C 601 may refer to a device operating as NSMS_C and may support one or more network functions shown in FIG. 1. NSMS_C 601 may be a consumer of the network slice service. Alternatively, NSMS_C 601 may be a provider of network slice service. For example, NSMS_C 601 may use the network slice (e.g., NSI and NSSI) set by NSMS_P 602 to provide a service corresponding to the network slice to a user (e.g., UE). .

NSMS_P 602 may refer to a device operating as NSMS_P and may support one or more network functions shown in FIG. 1. NSMS_P 602 may support NSI (re)assignment function, NSI modification function, NSSI (re)assignment function, and NSSI modification function. MS_P 603 may refer to a device operating as MS_P and may support one or more network functions shown in FIG. 1. Additionally, MS_P (603) may support a capacity planning function. For example, MS_P 603 may be an NSMS_P that supports a capacity planning function among a plurality of NSMS_Ps. The capacity planning function may refer to a function that optimizes the utilization of NSI or network resources/functions that make up NSSI.

If capacity planning is required for the NSI or NSSI set for NSMS_C (601), NSMS_C (601) may generate a capacity planning request message requesting performance of a capacity planning procedure, The generated capacity planning request message may be transmitted to NSMS_P (602) (S610). That is, the capacity planning request message can be transmitted when optimization of network resource/function utilization of NSMS_C (601) is required.

The capacity planning request message includes an indicator requesting performance of a capacity planning procedure, an identifier of NSMS_C (601), an identifier (e.g., NSI ID, NSSI ID) of the network slice assigned to NSMS_C (601), and NSMS_C ( 601) may include at least one identifier of the target network to which it belongs. The capacity planning request message may be transmitted from NSMS_C (601) to NSMS_P (602) when a predefined event occurs. Alternatively, the capacity planning request message may be transmitted according to a preset period. Here, NSMS_P (602) may be an NSMS_P that has assigned NSI or NSSI to NSMS_C (601).

NSMS_P 602 may receive a capacity planning request message from NSMS_C 601 and confirm that performance of the capacity planning procedure is requested based on the received capacity planning request message. In this case, NSMS_P 602 can check the feasibility of all or all NSSIs of the target network (S620). The target network may be an NSI configured for NSMS_C (601) or a network where the NSSI is located. All NSIs can include enabled NSIs and disabled NSIs, and all NSSIs can include enabled NSIs and disabled NSSIs. For example, NSMS_P 602 can check all NSIs or all NSSIs provisioned within the target network and check the feasibility of the confirmed NSIs or NSSIs. NSMS_P 602 can output a confirmation result of NSI or feasibility of NSSI. The feasibility check result (i.e., the result of step S620) can be used as an input parameter of the capacity planning procedure.

NSMS_P (602) can obtain information necessary for the capacity planning procedure (S630). The necessary information may be information needed for resource optimization calculation in the target network. For example, NSMS_P 602 can obtain information about network resources/functions used in the target network. Here, information about network resources/functions may include the topology of the target network, capacity used and available capacity in the link of the target network, throughput, packet loss rate, link delay, etc. Additionally, NSMS_P 602 can obtain information about all NSIs or network resources/functions for all NSSIs in the target network. Here, information about network resources/functions may include network topology, capacity used and available capacity in the link, throughput, packet loss rate, link delay, etc. in NSI or NSSI. NSMS_P 602 can output the necessary information obtained in step S630. The result of step S630 can be used as an input parameter of the capacity planning procedure.

NSMS_P 602 sends a capacity optimization request message (capacity optimization request message) including the result of step S620 (e.g., feasibility of the network slice) and the result of step S630 (e.g., information required for the capacity planning procedure). request message) can be generated, and a capacity optimization request message can be transmitted to the MS_P (603) (S640). The capacity optimization request message may include an indicator directing performance of the capacity planning procedure. MS_P (603) may be an entity that performs a capacity planning function (eg, network resource optimization function) and may be an entity independent from NSMS_P (602). Alternatively, MS_P (603) may be an entity included within NSMS_P (602).

MS_P (603) can receive a capacity optimization request message from NSMS_P (602) and check the information included in the capacity optimization request message. MS_P (603) may perform a capacity planning procedure using the information included in the capacity optimization request message (S650). The capacity planning procedure may be performed based on a predefined algorithm. If it is determined that relocation of the existing NSI or NSSI is necessary in the capacity planning procedure, MS_P 603 may determine that relocation of the NSI or NSSI is necessary.

Additionally, if it is determined that scale up or scale down of the existing NSI is necessary in the capacity planning procedure, MS_P 603 may determine that modification of the existing NSI is necessary. If it is determined that scaling up or down of the existing NSSI is necessary in the capacity planning procedure, MS_P 603 may determine that modification of the existing NSSI is necessary.

MS_P 603 may generate a capacity optimization response message containing information indicating the result of the capacity planning procedure. Information indicating the results of the capacity planning procedure can be defined as Table 1.

If modification of the existing NSI is required, the capacity optimization response message may further include information indicating that the existing NSI needs to be scaled up or scaled down. If modification of the existing NSSI is required, the capacity optimization response message may further include information indicating that the existing NSSI needs to be scaled up or scaled down.

MS_P (603) may transmit a capacity optimization response message to NSMS_P (602) (S660). NSMS_P 602 may receive a capacity optimization response message from MS_P 603 and perform an allocation/modification procedure (e.g., NSI allocation procedure, NSSI) of a network slice based on the information included in the capacity optimization response message. At least one procedure among an allocation procedure, an NSI modification procedure, and an NSSI modification procedure) may be performed (S670). The network slice allocation/modification procedure may be repeatedly performed until the result indicated by the capacity optimization response message is satisfied. Here, the NSI allocation procedure can be performed as follows.

Figure 7 is a flowchart showing a first embodiment of an NSI allocation procedure in a communication system.

Referring to FIG. 7, the NSI allocation procedure may be performed by the NSMS_P 602 and the network service subnet management service provider (NSSMS_P) 604. NSSMS_P 604 may refer to a device operating as NSSMS_P and may support one or more network functions shown in FIG. 1.

If the capacity optimization response message received from MS_P 603 indicates performance of the NSI allocation procedure, NSMS_P 602 may derive a network slice subnet related to the requirements for NSI allocation ( S670-11). NSMS_P 602 can perform an NSI allocation operation with NSSMS_P 604 using the derived network slice subnet (S670-12). As a result of step S670-12, an NSI may be created, and NSMS_P 602 may set an NSSI associated with the NSI created in step S670-12 (S670-13). Steps S670-11 to S670-13 described above may be repeatedly performed until the result indicated by the capacity optimization response message is satisfied.

Meanwhile, the NSSI allocation procedure can be performed as follows.

Figure 8 is a flowchart showing a first embodiment of an NSSI allocation procedure in a communication system.

Referring to Figure 8, the NSSI allocation procedure may be performed by NSMS_P (602) and NSSMS_P (604). NSSMS_P 604 may refer to a device operating as NSSMS_P and may support one or more network functions shown in FIG. 1.

If the capacity optimization response message received from MS_P 603 indicates performance of the NSSI allocation procedure, NSMS_P 602 may transmit an NSSI allocation request message to NSSMS_P 604 (S670-21). When an NSSI allocation request message is received from NSMS_P 602, NSSMS_P 604 may determine that performance of an NSSI allocation procedure is requested. Therefore, NSSMS_P (604) can derive requirements for NSSI components and transport networks (S670-22). NSSMS_P 604 may perform the steps below based on the derived requirements. For example, if NSSI includes a virtualization part, NSSMS_P 604 may perform a network slice (NS) instance creation operation (S670-23).

Alternatively, according to the requirements of the NSSI component, the NSSMS_P 604 may perform an NSSI allocation operation (S670-24) and a provisioning operation of a network function (S670-25). Afterwards, the NSSMS_P 604 may perform a setting operation of MOI for NSSI (S670-26). Alternatively, according to the requirements of the transport network, the NSSMS_P 604 may perform a coordination operation with a transport network manager (TN_M) (S670-27).

NSSMS_P (604) can generate an NSSI allocation response message containing information of the configured NSSI, and transmit the generated NSSI allocation response message to NSMS_P (602) (S670-28). NSMS_P 602 can receive the NSSI allocation response message from NSSMS_P 604 and check the NSSI information included in the NSSI allocation response message. Steps S670-21 to S670-28 described above may be repeatedly performed until the result indicated by the capacity optimization response message is satisfied.

Meanwhile, if the capacity optimization response message received from MS_P 603 indicates performance of the NSI modification procedure, NSMS_P 602 may perform the NSI modification procedure. The NSI modification procedure may be repeatedly performed until the result indicated by the capacity optimization response message is satisfied.

Meanwhile, the NSSI modification procedure can be performed as follows.

9 is a flow chart illustrating a first embodiment of an NSSI modification procedure in a communication system.

Referring to FIG. 9, the NSSI allocation procedure may be performed by the NSMS_P 602 and the network slice subnet management service provider (NSSM_SP) 605. NSSM_SP 605 may refer to a device operating as NSSM_SP and may support one or more network functions (eg, network slice subnet management function (NSSMF)) shown in FIG. 1.

If the capacity optimization response message received from MS_P 603 indicates performance of an NSSI modification procedure, NSMS_P 602 may transmit an NSSI modification request message to NSSM_SP 605 (S670-31). When an NSSI modification request message is received from NSMS_P 602, NSSM_SP 605 may determine that performance of an NSSI modification procedure is requested. In this case, NSSM_SP 605 can perform the steps below.

If the NSSI includes a component for the NSSI, the NSSM_SP 605 may perform an NSSI modification operation (S670-32). If NSSI includes NFI, NSSM_SP 605 can perform NF provisioning operation (S670-33). If the NSSI includes a virtualization part, the NSSM_SP 605 can perform scaling/update/creation operations of an NS (network slice) instance (S670-34). If NSSI includes a TN part, NSSM_SP (605) can perform coordination operations related to TN (S670-35).

When NSSI modification is completed, NSSM_SP 605 can generate an NSSI modification response message containing information on the modified NSSI, and transmit the generated NSSI modification response message to NSMS_P 602 (S670-36). NSMS_P (602) can receive the NSSI modification response message from NSSM_SP (605) and check the NSSI information included in the NSSI modification response message. Steps S670-31 to S670-36 described above may be repeatedly performed until the result indicated by the capacity optimization response message is satisfied.

Referring again to FIG. 6, NSMS_P 602 may store the result of step S670 when step S670 is completed (S680). For example, NSMS_P (602) may update network capacity availability information, which is the result of performing step S670, and store the updated network capacity availability information in a repository ( repository). Additionally, NSMS_P 602 may generate a capacity planning response message including the result of step S670, and transmit the generated capacity planning response message to NSMS_C 601 (S690). The capacity planning response message may include updated network capacity availability information. Additionally, the capacity planning response message may further include at least one of allocated NSI information, allocated NSSI information, modified NSI information, and modified NSSI information that are the result of performing step S670.

NSMS_C (601) can receive the capacity planning response message from NSMS_P (602) and check the information included in the capacity planning response message. Therefore, NSMS_C 601 can use NSI or NSSI indicated by the capacity planning response message. For example, NSMS_C 601 may provide a network slice service to a user (eg, UE) using the NSI or NSSI indicated by the capacity planning response message.

Methods according to the present invention may be implemented in the form of program instructions that can be executed through various computer means and recorded on a computer-readable medium. Computer-readable media may include program instructions, data files, data structures, etc., singly or in combination. Program instructions recorded on a computer-readable medium may be specially designed and constructed for the present invention or may be known and usable by those skilled in the art of computer software.

Examples of computer-readable media include hardware devices specially configured to store and execute program instructions, such as ROM, RAM, flash memory, etc. Examples of program instructions include machine language code, such as that created by a compiler, as well as high-level language code that can be executed by a computer using an interpreter, etc. The above-described hardware device may be configured to operate with at least one software module to perform the operations of the present invention, and vice versa.

Although the description has been made with reference to the above examples, those skilled in the art will understand that various modifications and changes can be made to the present invention without departing from the spirit and scope of the present invention as set forth in the claims below. You will be able to.

Claims (15)

A method of operating a first device in a communication system supporting network slicing, comprising:
Receiving a first message requesting capacity planning of a network slice from a second device;
Obtaining information necessary for the capacity planning;
transmitting a second message containing the necessary information to a third device supporting the capacity planning function;
Receiving a third message including a result of performing the capacity planning from the third device; and
A step of performing a reallocation or modification operation of the network slice based on a result of the capacity planning,
When the capacity planning is performed, network resources and functions constituting the network slice are optimized. In claim 1,
The method of operating the first device is:
Further comprising checking feasibility for the network slice when the first message is received,
A method of operating a first device, wherein a result of checking the feasibility of the network slice is included in the second message. In claim 1,
The method of operating the first device is:
updating network capacity availability information based on a result of a reallocation or modification operation of the network slice; and
The method of operating a first device further comprising transmitting a fourth message containing updated network capacity availability information to the second device. In claim 1,
The network slice is a network slice instance (NSI) or a network slice subnet instance (NSSI). In claim 4,
The results of the capacity planning are:
Operation of the first device, including at least one of an indicator requesting reallocation of the NSI, an indicator requesting modification of the NSI, an indicator requesting reallocation of the NSSI, and an indicator requesting modification of the NSSI method. In claim 1,
The above necessary information is:
A method of operating a first device, including at least one of topology, capacity information, throughput, packet loss rate, and link delay for the network slice. In claim 1,
The first device is a device operating as a network slice management service provider (NSMS_P), the second device is a device operating as a network slice management service consumer (NSMS_C), and the third device is a device operating as a management service provider (MS_P). A method of operating a first device, which is a device. delete As a first device in a communication system supporting network slicing,
A first element supporting a network slice management slice (NSMS) function;
a second element supporting a capacity planning function; and
It includes a memory storing at least one command executed by the first element and the second element,
The at least one command is:
The first element receives a first message from a second device requesting the capacity planning of a network slice;
the first element obtains information necessary for the capacity planning;
the first element transmits a second message containing the necessary information to the second element;
the second element performs the capacity planning for the network slice based on the second message;
The second element transmits a third message including a result of performing the capacity planning to the first element; and
The first element is executed to perform a reallocation or modification operation of the network slice based on the performance result of the capacity planning included in the third message,
When the capacity planning is performed, network resources and functions constituting the network slice are optimized. In claim 9,
The at least one command is:
When the first message is received, the first element is further executed to check feasibility for the network slice,
A first device, wherein a result of confirming the feasibility of the network slice is included in the second message. In claim 9,
The at least one command is:
Based on the result of the reallocation or modification operation of the network slice, the first element updates network capacity availability information; and
wherein the first element is further configured to transmit a fourth message containing updated network capacity availability information to the second device. In claim 9,
The first device, wherein the network slice is a network slice instance (NSI) or a network slice subnet instance (NSSI). In claim 12,
The results of the capacity planning are:
A first device comprising at least one of an indicator requesting reallocation of the NSI, an indicator requesting modification of the NSI, an indicator requesting reallocation of the NSSI, and an indicator requesting modification of the NSSI. In claim 9,
The above necessary information is:
A first device comprising at least one of topology, capacity information, throughput, packet loss rate, and link delay for the network slice. In claim 9,
The first device is a device operating as a network slice management service provider (NSMS_P), and the second device is a device operating as a network slice management service consumer (NSMS_C).

Images