KR102666016B1 - Method and apparatus for network slicing in mobile communication system - Google Patents

Abstract

A network slicing method and device for a mobile communication system are provided. When a mobile communication system receives a service request, it determines the service type based on the service characteristics and requirements of the service request, and according to the service type, an independent network for each node for a plurality of nodes included in the mobile communication system. Depending on slicing, it is determined whether the service can be processed. If a service can be processed according to independent network slicing for each node, the service is processed through at least one slice instance implemented according to the network slicing of the corresponding node. On the other hand, if service processing is not possible according to independent network slicing for each node, the service is processed through the combination of at least two or more nodes and at least one slice instance implemented according to the network slicing of each node.

Description

Method and apparatus for network slicing in mobile communication system}

The present invention relates to a network slicing method and device for a mobile communication system.

Until now, customers (individual customers, corporate customers, and equipment) have had no choice but to use the services provided by mobile communication networks, and all mobile communication networks have provided similar services. In particular, the 4G system focused on technology to increase traffic capacity, and since the dedicated network is structured to handle all services equally, the efficiency of system resource utilization was low and it was not easy to change the network configuration, so we actively responded to various services and requirements. It is not efficient to respond.

Therefore, in the 5G next-generation communication environment, requirements are segmented and diverse, and various services centered on low latency or high reliability are expected to become mainstream, so network slicing is needed to provide various requirements and services. A network structure such as technology is required. In particular, 5G network slicing technology is a new concept of 5G network that has not been used in existing mobile communication network technology. It is a technology that bundles and provides network resources and network functions required for services requested by mobile terminals into one independent slice. Through this, network operators can independently allocate network resources specialized for each service and user and secure network flexibility through resource virtualization, providing scalability and reliability of service and network resource operation.

To date, global standardization efforts for network slicing are still in their early stages and are mostly focused on vertical slicing. Industry-wide research on vertical network slicing is ongoing, including work by NGMN, 3GPP, 5GPPP Co-Funded Frameworks, and WWRF. In particular, in 3GPP, vertical network slicing has been identified as one of the key technologies to be developed in 5G standardization, and research on core network slicing is in progress. Current discussions in the industry include the concept and requirements of vertical network slicing, how and at what granularity to perform slicing, the impact of network slicing on the core network (CN), random access network (RAN), and devices, and how network slicing can be implemented. The focus is on the potential system architecture based on it. Vertical network slicing is primarily a technology such as Network Functional Virtualization (NFV) and Software Defined Networking (SDN) that focuses on active core network nodes.

Meanwhile, in addition to vertical network slicing, horizontal slicing, that is, horizontal network slicing, is also being studied. Horizontal network slicing supports each slice to have its own physical resources or share resources from adjacent network slices. Horizontal network slicing can provide the optimal solution in an environment where network virtualization can be fully performed. In addition, it is a new technology that can efficiently respond to the diverse services and non-uniform traffic environment of the 5G system by configuring slicing with essential functions, excluding unnecessary functions customized to service and user requirements.

If full virtualization of the network is realized in the future, one device can operate in multiple slices in an environment where vertical slicing and horizontal slicing can be used simultaneously. For example, smartphones can operate in vertical slicing for Mobile Broadband (MBB) services, vertical slicing for health care services, and horizontal slicing supporting wearable devices.

The problem to be solved by the present invention is to provide a method and device for efficiently performing network slicing based on horizontal slicing in a mobile communication system.

A method according to a feature of the present invention is a network slicing method in a mobile communication system, comprising: when the mobile communication system receives a service request, determining a service type based on service characteristics and requirements of the service request; determining whether a plurality of nodes included in the mobile communication system according to the service type can process the service according to independent network slicing for each node; If a service can be processed according to independent network slicing for each node, processing the service through at least one slice instance implemented according to the network slicing of the corresponding node; And if service processing is not possible according to independent network slicing for each node, the service is processed through at least one slice instance implemented according to the network slicing of each node through the combination of at least two or more nodes. do.

According to an embodiment of the present invention, network horizontal slicing is effectively operated in a next-generation mobile communication system to provide user-requested services with optimal efficiency, thereby improving traffic service quality and improving system performance.

Figure 1 is a diagram showing the concept of vertical network slicing.
Figure 2 is a diagram showing the concept of horizontal network slicing.
Figure 3 is a conceptual diagram of network slicing according to an embodiment of the present invention.
Figure 4 is a flowchart of a processing procedure according to a network slicing method according to an embodiment of the present invention.
Figure 5 is a structural diagram of a network slicing device according to an embodiment of the present invention.

Below, with reference to the attached drawings, embodiments of the present invention will be described in detail so that those skilled in the art can easily implement the present invention. However, the present invention may be implemented in many different forms and is not limited to the embodiments described herein. In order to clearly explain the present invention in the drawings, parts unrelated to the description are omitted, and similar parts are given similar reference numerals throughout the specification.

Throughout the specification, when a part “includes” a certain element, this means that it may further include other elements rather than excluding other elements, unless specifically stated to the contrary.

In this specification, expressions described as singular may be interpreted as singular or plural, unless explicit expressions such as “one” or “single” are used.

The mobile communication system according to an embodiment of the present invention can be applied to various mobile communication networks. For example, the mobile communication system can be applied to current radio access technology (RAT)-based mobile communication networks or 5G and later mobile communication networks. 3GPP is developing a new RAT-based 5G standard specification that satisfies IMT-2020 requirements, and this new RAT can be called NR (New Radio). The embodiment of the present invention is described using NR, that is, a next-generation based mobile communication system as an example, but the embodiment of the present invention is not limited to this and can be applied to various mobile communication systems.

Hereinafter, a network slicing method and device according to an embodiment of the present invention will be described with reference to the drawings.

Figure 1 is a diagram showing the concept of vertical network slicing.

Network slicing is a virtualization technology that physically makes one network operate like multiple networks. It is based on technologies called SDN (Software Defined Network) and NFV (Network Function Virtualization). These technologies are used to enhance the operational efficiency of wired networks. This is a concept that emerged. Until now, providing a dedicated network to a specific industry or company requires a lot of resources to provide the service as it must reflect the complex needs of users. Network slicing is a method of 'slicing' the network into pieces, which does not actually divide the bandwidth, but rather uses multiple logical networks on top of the physical network infrastructure. Physical resources and functions are separated from the network and then bundled and provided separately as needed. Each of these bundles is called a slice, and each slice can be customized. Some slices can be optimized for HD (High Definition) video streaming, some for security, and still others for connecting many devices. For example, since HD-level video is the mainstream service for smartphones, the service is provided by setting up a structure such as slice 1 in Figure 1, and real-time performance and low latency are provided. For automotive devices that need it, services are provided by setting up a slice 2-type structure, and for Massive IoT devices that only need low-power connectivity, slice 2 is provided. The service will be provided by setting up a structure like 3 (slice 3).

Network slicing is a situation in which various types of terminals are provided services through different virtual network resources. Different wireless connection technologies (RAT, It can be connected through Radio Access Technology. Different terminals can receive end-to-end services of different quality suitable for the characteristics of the terminal through each network slice. At this time, each network vertical slicing can be a virtualized network composed of mutually mapped slices among the components (Access Node/Cloud Node/Networking Node) of one physical network. In addition, the components that process CP (Control Plane) and UP (User Plane) may be different for each network slice. Currently, industry-wide research on vertical network slicing is ongoing, including work by NGMN, 3GPP, 5GPPP Co-Funded Framework and WWRF, and especially in 3GPP, vertical network slicing is one of the key technologies to be developed in 5G standardization and core network Research on slicing is ongoing

In an embodiment of the present invention, customized network services are provided in the core network and RAN (Random Access Network) through the application of network slicing. Accordingly, network functions or traffic unnecessary for the service are separated to ensure service independence, stability, and resource use efficiency, thereby ensuring flexibility in the network structure. In addition, for services that must be provided in the network, detailed service classification such as priorities such as bandwidth, response time, reliability, urgency, priority, and security is provided. Efficient processing is performed using the network slicing method.

More specifically, an embodiment of the present invention is a network slicing based on horizontal slicing that allows services and user requirements to be completely processed by independently or organically combining local slicing functions rather than the existing vertical slicing concept. provides.

In the post-5G phase, it is expected that network capacity and user environment will need to be further improved. However, increasing capacity does not require end-to-end unification. Capacity expansion factors can be higher closer to users and lower deeper into the infrastructure network. It provides 10,000x capacity scaling at the leading edge of the network and 10x scaling at the network core. This uneven capacity expansion is driven by new types of user traffic and services and determined by the fundamental principles of communications technology. We expect an ever-increasing number of devices, which will result in large amounts of user traffic at the network edge. Because service functions and device detection are local, it is desirable to keep detected data processing and corresponding decisions and actions local to reduce latency and improve privacy and security. As a result, the amount of data entering deeper networks will decrease and traffic steering will become more non-uniform. Non-uniform traffic scaling requires uneven network capacity expansion, and the feasibility of non-uniform capacity scaling has been well proven in communication theory. Non-uniform capacity scaling is used to aid communication, and edge computing and processing are used as infrastructure networks. This can be seen as reducing traffic. For example, a base station (e.g., RAN) may be utilized to provide a user experience, such as slicing up some of its computing resources to help compute on portable devices, and portable devices slicing up some of its computing resources to help with computations in wearable devices. You can.

Therefore, in an embodiment of the present invention, in order to efficiently cope with non-uniform capacity, a network based on horizontal slicing is used to completely handle service and user requirements by independently or organically combining local slicing functions. Slicing is provided.

Figure 2 is a diagram showing the concept of horizontal network slicing.

In horizontal network slicing, as shown in Figure 2, in a horizontal area, physical resources (computation devices, storage devices, etc. from a wireless perspective) in adjacent layers of the network layer are sliced to form a horizontal partition. . Horizontal network slicing supports each slice to have its own physical resources or share resources from adjacent network slices, and can provide an optimal solution in an environment where virtualization can be fully performed.

In addition, horizontal network slicing can configure slicing with essential functions, excluding unnecessary functions tailored to service and user requirements. For example, when processing services that can be processed locally, existing vertical network slicing must consist of 1:1 or 1:n slicing from the terminal to the core network, but horizontal network slicing can be processed in the minimum number of units. Since the concept was defined so that slicing from the terminal to the core network does not necessarily have a mapping relationship. Accordingly, it is possible to dynamically provide services that require user experience, services that require low latency, and user requirements, thereby improving system performance and service quality.

This horizontal network slicing is an advanced technology over vertical network slicing and is designed to accommodate new non-uniform capacity scaling trends and support edge cloud computing and compute offloading for local processing. As the previous example, the computing resources of base stations and portable devices (or high-performance devices) are sliced horizontally, and this slice and the computing resource slices of wearable devices (or low-performance devices) are combined to form a virtual computing platform through the new 5G air interface design. , which will greatly enhance the computing capabilities of future portable and wearable devices and perform local traffic processing. With horizontal slicing, the end-to-end traffic flow in horizontal slicing is typically localized and horizontal, because the traffic flow ends within a horizontal slicing created between devices that have directional communication links (potentially in close proximity). Enemy slicing occurs at two ends, for example between a wearable device and a portable device, or between a wearable device and a small cell (RAN) access point.

However, in vertical network slicing, each network node usually implements similar functions between slices, and the dynamic implementation of the network node is mostly to dynamically allocate resources to each slice, so the various services and non-uniformity of the 5G system As for slicing to process traffic, horizontal network slicing can be absolutely advantageous in terms of efficiency. And in horizontal network slicing, when supporting slices according to service and user requirements, optimized slicing can be created by excluding unnecessary functions from the network node and creating essential functions at any time.

An embodiment of the present invention provides network slicing based on such horizontal slicing.

Figure 3 is a conceptual diagram of network slicing according to an embodiment of the present invention.

As shown in the attached FIG. 3, in the embodiment of the present invention, the mobile communication system largely includes a portable domain 10, a random access domain (RAN) domain 20, and a core domain 30. And, each domain is sliced and includes at least one slice instance. Here, each domain can be named a node, horizontal slicing is performed for each node, and the horizontal slicing of each node can be defined to perform services independently according to the service type.

There is an orchestration part that manages slicing at the system level, that is, a slice management and orchestration (40). When a service request comes in from a user or device, the slicing management unit 40 configures a service instance according to the service type and characteristics and determines the slicing processing method and type accordingly. If independent processing is possible in the portable domain 10, RAN domain 20, and core domain 30, independent processing is performed, and if cooperation of adjacent domains is required, these domains can be organically combined and processed. make it possible This kind of horizontal slicing can provide the optimal solution in an environment where network virtualization can be fully performed, and slicing can be configured with essential functions while excluding unnecessary functions tailored to service and user requirements, enabling various 5G systems. It is a technology that can respond efficiently in service and non-uniform traffic environments.

In an embodiment of the present invention, the portable domain 10, RAN domain 20, and core domain 30 may be composed of various types of slicing instances depending on the service. Each slicing instance may operate independently or organically with the slicing instances of the portable domain 10, RAN domain 20, and core domain 30.

Meanwhile, the embodiment of the present invention may also include a function to distinguish and process CP and UP, which are the basic technologies of vertical slicing, and regarding the operation method, all instances can process CP/UP simultaneously depending on the service and requirements. Alternatively, only part of CP or UP functions may be processed. Additionally, CP can be processed in one instance, and UP can be processed separately in multiple instances. This means that when applying the network slicing method according to an embodiment of the present invention, the advanced vertical slicing technology can be accepted as is. From a vertical slicing service-oriented network perspective, network slicing requires support for end-to-end network slices. Therefore, in addition to supporting network slicing in the core network, which is currently being intensively discussed, a solution is needed on how to support end-to-end network slicing in conjunction with the core network in the radio access network (RAN). However, from a horizontal slicing service perspective, new end-to-end service definition and support that are different from existing ones are needed, but this will not be discussed here.

Next-generation communications are expected to see an ever-increasing number of devices, resulting in large amounts of user traffic at the network edge. Since service functions and device detection are local, it is desirable to keep detected data processing and corresponding decisions and actions local to reduce latency and improve privacy and security. As a result, the amount of data entering the deeper network will decrease and the non-uniformity of traffic steering will increase, so non-uniform traffic scaling requires uneven network capacity expansion and a communication method is applied to handle non-uniform capacity scaling. For this purpose, a portable domain (10) is used.

Meanwhile, the portable domain 10, RAN domain 20, and core domain 30 function to configure and process slicing considering physical resources. In other words, optimized slicing is processed by categorizing slicing processing types, including system resource allocation, according to the requested service traffic type. Each domain can process services independently, and if cooperation from adjacent domains is required, they can be organically combined to process services.

The portable domain 10 is a service slicing domain that can be provided when a local service is required, such as vehicle communication, MTC (machine type communication), or DTD (Device To Device) communication. Portable domain 10 is expected to be the most frequent and numerous type of communication in next-generation communication such as 5G, and horizontal slicing technology is expected to be the most efficient for such communication.

The RAN domain 20 includes MEC (Mobile Edge Computing) functions for processing real-time services that can be processed within the base station, and for this purpose, the CP/UP function in the core network is also structured in a structure that can be processed in the RAN domain 20. Configure a service slicing domain.

The core domain 30 configures a service slicing domain with a structure that requires less real-time than the RAN domain 20 and can process services with hyper-connectivity characteristics.

Mobile communication services can be classified in various ways according to service characteristics and requirements. In order to subdivide each service and process services according to characteristics, the service is divided into portable domain 10, RAN domain 20, and The core domain 30 is divided into nodes and slicing is configured and processed for each service instance.

In other words, autonomous driving, vehicle, MTC, and DTD types of services that place the highest importance on ultra-low latency performance that require real-time performance based on service requirements and user requirements are, if possible, provided. By processing in the portable domain 10, slicing in the RAN domain 20 and core domain 30 can be configured to a minimum, and slicing can be mainly configured in the portable domain 10.

MEC type-based services, which place the highest importance on low-latency performance that requires real-time, should be processed in the RAN domain (20) if possible, so that slicing of the portable domain (10) and core domain (30) is kept to a minimum. It can be configured and processed mainly by configuring slicing in the RAN domain 10.

Massive IoT services that value reliability should be processed in the core domain (30) if possible, and slicing can be processed to minimize slicing in the portable domain (10) and RAN domain (30) and divide roles. there is.

And if processing cannot be done in one single domain or if a better service can be provided through mutual cooperation between domains, the service can be provided through organic combination between different domains. For example, MBB (Mobile Broad Band) service, which requires high-quality transmission capacity, can be handled by dividing roles between the RAN domain 20 and the core domain 30.

In this way, in the next-generation mobile communication system according to the embodiment of the present invention, such as 5G, slicing can be classified according to the characteristics and requirements of each service, and the main performance criteria are transmission reliability (Reliability), required transmission capacity (Bandwidth), It includes latency, etc., and additionally includes criteria such as urgency, priority, security, etc. to distinguish service types, thereby providing efficiency in service provision.

Network slicing is in the process of standardizing vertical slicing centered on the core domain, but it is still about vertical slicing technology and is in the stage of defining slicing by separating CP and UP with the main purpose of efficiently utilizing resource management, and RAN For the domain, this is the step of defining slicing by separating CP and UP as well as CU (Control Unit) and DU (Digital Unit), and is a technology for applying the vertical slicing function based on the current system structure.

In general, in order to fully support network slicing, service instances must be sliced according to the system's services and requirements, and horizontal slicing of the portable domain, RAN domain, and core domain must be supported, respectively, to maximize system efficiency. In other words, horizontal slicing can maximize efficiency when applied to an environment where all networks have virtualization functions. Of course, if wearable communication is activated in the future, the slicing domain can be expanded by adding a wearable domain. In an embodiment of the present invention, a horizontal slicing technique is proposed limited to the portable domain, RAN domain, and core domain, but it is not necessarily limited thereto.

Next, a network slicing method according to an embodiment of the present invention will be described.

Figure 4 is a flowchart of a processing procedure according to a network slicing method according to an embodiment of the present invention.

As shown in the attached FIG. 4, upon receiving a service request (S100), the network slicing device 100 classifies the service type according to the characteristics and requirements for each service (S110). Service types are classified based on transmission reliability, bandwidth, and latency, but are further divided into additional services such as emergency, priority, and security. Type distinction is possible.

As shown in FIG. 3 mentioned above, the portable domain 10, the RAN domain 20, and the core domain 30 are each processed by horizontal slicing to include a plurality of slice instances, and are distinguishable according to an embodiment of the present invention. Service types can be prioritized as a horizontal slicing unit.

The network slicing device 100 determines whether the service type according to the received request is a portable domain-based service (S120). In an embodiment of the present invention, based on the service type and horizontal slicing, it is determined whether the service is a portable domain-based service in order to give priority to ultra-low latency and high reliability services such as vehicle communication, MTC, and DTD communication.

In particular, in step S120, in the case of a portable domain-based service, since it is a service that requires minimal time delay and high reliability, the portable domain can be serviced without necessarily utilizing slicing of the RAN domain 20 and the core domain 30. Only in (10) is it determined whether slicing is possible. If slicing can be processed only in the portable domain 10, the service is processed using the necessary resources in the portable domain 10. That is, the service is processed using the slice instance of the portable domain 10 (S130).

On the other hand, if it is determined that the service cannot be processed by slicing only in the portable domain, it is determined whether the service can be processed by organically combining with the RAN domain 20, even though the service requires ultra-low delay and high reliability ( S140). If a service can be processed by organically combining with the RAN domain 20, the service is processed by utilizing the necessary resources in the portable domain 10 and the RAN domain 20. That is, the service is processed using the slice instance of the portable domain 10 and the slice instance of the RAN domain 20 (S150).

In step S140, if it is determined that the service cannot be sliced even when the portable domain 10 and the RAN domain 20 are organically combined, although it is a service that requires ultra-low delay and high reliability, the portable domain 10 ), the RAN domain 20, and the core domain 30, it is determined that the service can be processed through organic combination, and the service is processed (S160, S170). That is, the service is processed using the slice instance of the portable domain 10, the slice instance of the RAN domain 20, and the slice instance of the core domain 30.

Meanwhile, in step 110, if the service type is a RAN domain-based service, the corresponding processing is performed. In an embodiment of the present invention, in order to prioritize services suitable for processing in the RAN domain 20, such as MEC, it is determined whether the service type is a RAN domain-based service and the corresponding processing is performed. Specifically, in the case of a RAN domain-based service, it is determined whether slicing processing is possible only in the RAN domain 10 without utilizing slicing in the core domain 30 (S180). If slicing can be processed only in the RAN domain 20, the service is processed using the necessary resources in the RAN domain 20. That is, the service is processed using the slice instance of the RAN domain 20 (S190).

In step S180, if it is determined that the service cannot be processed by slicing only in the RAN domain 20, it is determined whether the service can be processed by organically combining with the core domain 30 (S200).

If a service can be processed by organically combining with the core domain 30, the service is processed by utilizing the necessary resources in the RAN domain 20 and the core domain 30. That is, the service is processed using the slice instance of the RAN domain 20 and the slice instance of the core domain 30 (S210).

Meanwhile, in step S200, if it is determined that the service cannot be sliced even when the RAN domain 20 and the core domain 30 are organically combined, the portable domain 10, the RAN domain 20, and the core domain It is determined that the service can be processed through organic combination with (30), and the service is processed (S160, S170). That is, the service is processed using the slice instance of the portable domain 10, the slice instance of the RAN domain 20, and the slice instance of the core domain 30.

Meanwhile, in step 110, if the service type is a core domain-based service, the corresponding processing is performed. In an embodiment of the present invention, if the service type is a core domain-based service such as a massive IoT service that values reliability, it is determined whether slicing processing is possible in the core domain (S220). In addition, since the service type may have redundancy not only in latency but also in performance requirements, such as a hyper-connectivity-based service, there is no problem at all even if it is processed in the core domain (30) rather than in the portable domain (10) or RAN domain (20). Since there is no such service type, it is possible to first determine whether slicing processing is possible in the core domain.

In step S220, if slicing processing is possible only in the core domain, the service is processed using the necessary resources in the core domain 30. That is, the service is processed using the slice instance of the core domain 30 (S230). However, in step S220, if slicing processing is not possible only in the core domain, the hyper-connectivity-based service can inevitably be sliced by organically combining with the RAN domain 20 (S200, S210).

In this way, by applying horizontal slicing according to the characteristics of each service request, it is possible to efficiently handle the ultra-low delay and high reliability characteristics of the service as well as distribute the non-uniform traffic load of the next-generation communication system where non-uniform traffic will increase. In addition to improving quality, it can ultimately improve system performance.

Figure 5 is a structural diagram of a network slicing device according to an embodiment of the present invention.

As shown in the attached FIG. 5, the network slicing device 100 according to an embodiment of the present invention includes a processor 110, a memory 120, an input interface device 130, an output interface device 140, and a network interface ( 150) and a storage device 160, which may communicate via bus 170.

The processor 110 may be configured to implement the methods described based on FIGS. 3 and 4 above. For example, the processor 110 determines the service type based on the received service request, determines whether service processing is possible through independent network slicing for each node (portable domain, RAN domain, core domain) depending on the service type, and , or through network slicing of organic combination between nodes, it is determined whether service processing is possible, and service processing is performed through each node according to the judgment result. The processor 110 may be a central processing unit (CPU) or a semiconductor device that executes instructions stored in the memory 120 or the storage device 160.

The memory 120 is connected to the processor 110 and stores various information related to the operation of the processor 110. The memory 120 may store instructions to be executed by the processor 110 or may load instructions from the storage device 160 and temporarily store them. The processor 110 may execute instructions stored or loaded in the memory 120. Memory may include ROM 121 and RAM 122.

In an embodiment of the present invention, the memory 120 may be located inside or outside the processor 110, and the memory 120 may be connected to the processor 110 through various known means.

The network interface device 150 is connected to a network and is configured to transmit and receive signals. The network interface device 150 may be configured to receive a service request and provide it to the processor 110, or may be configured to transmit a determination result according to the service type from the processor 110 to each node.

The network slicing device 100 having this structure may be implemented as included in the slicing management unit of FIG. 3.

The embodiments of the present invention are not implemented only through the devices and/or methods described above, but can be implemented through programs for realizing functions corresponding to the configuration of the embodiments of the present invention, recording media on which the programs are recorded, etc. This implementation can be easily implemented by an expert in the technical field to which the present invention belongs based on the description of the embodiments described above.

Although the embodiments of the present invention have been described in detail above, the scope of the present invention is not limited thereto, and various modifications and improvements can be made by those skilled in the art using the basic concept of the present invention defined in the following claims. It falls within the scope of rights.

Claims (10)

A network slicing method in a mobile communication system, comprising:
When the mobile communication system receives a service request, determining a service type based on service characteristics and requirements of the service request;
determining whether a plurality of nodes included in the mobile communication system according to the service type can process the service according to independent network slicing for each node;
If a service can be processed according to independent network slicing for each node, processing the service through at least one slice instance implemented according to the network slicing of the corresponding node; and
If service processing is not possible according to independent network slicing for each node, the service is processed through at least one slice instance implemented according to the network slicing of each node through the combination of at least two or more nodes.
Including,
If service processing is not possible according to the independent network slicing for each node, the step of processing the service through at least one slice instance implemented according to the network slicing of each node through the combination of at least two or more nodes is the step of processing the service. If the service type is the first service type considering ultra-low latency performance that requires real-time, but cannot be processed only by the first node, it is implemented according to the network slicing of each node through the combination of the first node and the second node. Processing the service through at least one slice instance,
The plurality of nodes include the first node corresponding to a portable domain, the second node corresponding to a RAN domain, and a third node corresponding to a core domain. According to paragraph 1,
The service type is network slicing, which is determined based on at least one of transmission reliability, requested transmission capacity (Bandwidth), latency, urgency, priority, and security. method. delete According to paragraph 1,
If a service can be processed according to independent network slicing for each node, the step of processing the service through at least one slice instance implemented according to the network slicing of the corresponding node is:
If the service type is a first service type considering ultra-low latency performance that requires real-time, processing the service through at least one slice instance implemented according to network slicing of the first node;
If the service type is a second service type considering low-latency performance that requires real-time, processing the service through at least one slice instance implemented according to network slicing of the second node; and
If the service type is a third service type considering reliability, processing the service through at least one slice instance implemented according to network slicing of the third node.
Network slicing method including. According to paragraph 1,
If service processing is not possible according to the independent network slicing for each node, the service is processed through at least one slice instance implemented according to the network slicing of each node through the combination of at least two or more nodes, including:
If the service type is a second service type considering low-latency performance that requires real-time, but cannot be processed only by the second node, network slicing of each node is performed by combining the second node and the third node. Processing the service through at least one slice instance implemented according to; and
If the service type is a third service type considering reliability, but cannot be processed only by the third node, at least one service implemented according to network slicing of each node through a combination of the third node and the second node Steps to handle the service through slice instances
Network slicing method including. According to clause 5,
If service processing is not possible according to the independent network slicing for each node, the service is processed through at least one slice instance implemented according to the network slicing of each node through the combination of at least two or more nodes, including:
If the first service type cannot be processed even through a combination of the first node and the second node, and if the second service type cannot be processed even through a combination of the second node and the third node, Or, if the third service type cannot be processed even through the combination of the third node and the second node, network slicing of each node through the combination of the first node, the second node, and the third node Processing the service through at least one slice instance implemented according to
A network slicing method further comprising: As a mobile communication system,
A first node corresponding to a portable domain and configured to create at least one service instance by performing network slicing considering physical resources;
a second node corresponding to the RAN domain and configured to create at least one service instance by performing network slicing considering physical resources;
a third node corresponding to the core domain and configured to create at least one service instance by performing network slicing considering physical resources; and
Determine the service type based on the service characteristics and requirements of the received service request, and process the service by at least one of the first node, the second node, and the third node according to the service type, A slicing management unit that makes a request to at least one of the first node, the second node, and the third node.
Including,
If the service type is a first service type considering ultra-low latency performance that requires real-time, but cannot be processed only by the first node, the first node and the second node are combined to perform network slicing of each node. A mobile communication system that processes the service through at least one slice instance implemented according to. In clause 7,
The service type is determined based on at least one of transmission reliability, bandwidth, latency, urgency, priority, and security,
A mobile communication system in which each service instance of the first node, the second node, and the third node operates independently or organically with the service instance of another node. In clause 7,
If the service type is a first service type considering ultra-low latency performance that requires real-time, the first node processes the service through at least one slice instance implemented according to network slicing,
If the service type is a second service type considering low-latency performance that requires real-time, the second node processes the service through at least one slice instance implemented according to network slicing, and
When the service type is a third service type considering reliability, a mobile communication system that processes the service through at least one slice instance implemented according to network slicing of the third node. In clause 7,
If the service type is a second service type considering low-latency performance that requires real-time, but cannot be processed only by the second node, network slicing of each node is performed by combining the second node and the third node. Process the service through at least one slice instance implemented according to;
If the service type is a third service type considering reliability, but cannot be processed only by the third node, at least one service implemented according to network slicing of each node through a combination of the third node and the second node A mobile communication system that processes its services through slice instances.

Images