KR102327021B1 - Method and apparatus for providing service through network slice - Google Patents

Abstract

Receiving a PDU session establishment request message including information on a network slice corresponding to the service from the terminal, determining the SMF and UPF included in the network slice, capable of processing the service, the determined SMF and UPF Transmitting a network slice instance request message including information of to the NSSF, receiving information on a network slice instance including SMF and UPF from the NSSF, and in response to the PDU session establishment request message, a PDU session establishment acceptance message to the terminal A method and a network apparatus for providing a network slice comprising the step of transmitting are provided.

Description

Service provision method and apparatus through network slice

The present disclosure relates to a method and apparatus for providing a service to a terminal through a network slice.

Although the 4G network is optimized for smartphones, the 5G network needs to provide services to various terminals with different properties. Mobile Broadband, Massive IoT, and Ultra Reliable Low Latency Communication, which are representative use-cases of 5G systems, include mobility and charging ), security, policy control, latency, and reliability have different properties and network requirements.

For example, hyper-connected IoT services in which fixed sensors that measure temperature, humidity, and rainfall are connected to a network do not require functions such as mobility. In addition, ultra-low latency communication services such as autonomous driving and remote industrial robot control require low latency of several milliseconds, unlike mobile broadband services. In addition, mobile broadband service requires up to 1 gigabyte of bandwidth.

A network slicing technology may provide a plurality of logical networks (network slices) created within one physical network and including specific network functions in order to satisfy the above different performance requirements of each service. . That is, each logical network can provide various services having different characteristics and reduce network construction costs.

One embodiment provides a method of providing a service over a network slice.

Another embodiment provides a network device that provides a service through a network slice.

Another embodiment provides a method for creating a network slice instance.

According to one embodiment, a method for an AMF of a communication network to provide a service through a network slice is provided. The service providing method includes the steps of: receiving, from a terminal, a packet data unit (PDU) session establishment request message including information on a network slice corresponding to the service; Determining possible SMF and UPF, sending a network slice instance request message including information of the determined SMF and UPF to the NSSF, receiving information of a network slice instance including the SMF and UPF from the NSSF, and and transmitting a PDU session establishment acceptance message to the terminal in response to the PDU session establishment request message.

The service providing method may further include providing a service to a terminal or another terminal based on information on a network slice instance when a network slice is requested again from a terminal or a terminal different from the terminal.

The determining of the SMF and the UPF in the service providing method may include selecting an SMF capable of processing a service, and receiving information about the UPF determined by the selected SMF from the selected SMF.

Selecting an SMF capable of processing a service in the service providing method may include receiving information necessary for selecting an SMF from an NRF if information necessary for selecting an SMF is not stored in the AMF.

Selecting the SMF capable of processing the service in the service providing method may include requesting the NRF to select the SMF if information necessary for selecting the SMF is not stored in the AMF.

In the service providing method, the information on the network slice instance may include a number of the network slice instance, and the network slice providing method may further include managing the number of the network slice instance.

According to another embodiment, a network device of a communication network is provided. The network device includes a processor, a memory, and a network interface, and the processor executes a program stored in the memory, and receives a PDU session establishment request message including information of a network slice corresponding to the service from the terminal, the network Determining the SMF and UPF that can process the service included in the slice, transmitting a network slice instance request message including information of the determined SMF and UPF to the NSSF, Network slice instance including SMF and UPF receiving the information of from the NSSF, and transmitting a PDU session establishment acceptance message to the terminal in response to the PDU session establishment request message.

In the network device, the processor executes a program, and when a network slice is requested again from a terminal or a terminal different from the terminal, the step of providing a service to the terminal or another terminal based on the information on the network slice instance may be further performed. .

When the processor in the network device performs the step of determining the SMF and the UPF, selecting an SMF capable of processing a service, and receiving information about the UPF determined by the selected SMF from the selected SMF may be performed. .

In the network device, when the processor selects an SMF capable of processing a service, if the information necessary for selecting the SMF is not stored in the network device, in order to select the SMF from the Network Repository Function (NRF) It may include receiving necessary information.

In the network device, when the processor selects an SMF capable of processing a service, if information necessary for selecting the SMF is not stored in the network device, a network storage function (NRF) is requested to select the SMF. may include doing

In the network device, the information of the network slice instance may include the number of the network slice instance, and the processor may further perform the step of executing a program to manage the number of the network slice instance.

According to another embodiment, a method is provided for an NSSF of a communication network to create a network slice instance. The method for generating a network slice instance includes receiving, from an AMF, a network slice instance request message for providing a service to a terminal, and a network slice including SMF and UPF capable of processing a service based on the network slice instance request message creating an instance, and sending a network slice instance accept message to the AMF in response to the network slice instance request message.

The step of creating a network slice instance in the method for creating a network slice instance includes comparing information of SMF and UPF with information of a network slice managed by NSSF, and SMF and UPF in a network slice managed by NSSF If the existing network slice instance is not included, creating a new network slice instance may be included.

In the network slice instance creation method, the network slice instance acceptance message may include the number of a new network slice instance.

In the network slice instance creation method, the step of transmitting the network slice instance acceptance message to the AMF includes, if the existing network slice instance including SMF and UPF is included in the network slice managed by the NSSF, the number of the existing network slice instance It may include sending to the AMF through a network slice instance accept message.

According to an embodiment, a combined network function can be efficiently provided to immediately create a network slice instance based on a request from a terminal and provide a service through the created network slice instance.

1 is a conceptual diagram illustrating a functional configuration diagram of a 5G system according to an embodiment.
2 is a conceptual diagram illustrating a network slice according to an embodiment.
3 is a conceptual diagram illustrating a relationship between a network slice and a network function according to an embodiment.
4 is a flowchart illustrating a method of registering a network slice according to an embodiment.
5 is a flowchart illustrating a method of providing a network slice instance according to an embodiment.
6 is a conceptual diagram illustrating a network slice instance provided according to an embodiment.
7 is a block diagram illustrating a wireless communication system according to an embodiment.

Hereinafter, with reference to the accompanying drawings, it will be described in detail for those of ordinary skill in the art to which the present invention pertains to easily implement the embodiments of the present disclosure. However, the present description may be embodied in various different forms and is not limited to the embodiments described herein. And in order to clearly explain the present description in the drawings, parts irrelevant to the description are omitted, and similar reference numerals are attached to similar parts throughout the specification.

Throughout the specification, a terminal is a mobile station (mobile station, MS), a mobile terminal (MT), an advanced mobile station (AMS), a high reliability mobile station (HR-MS) ), subscriber station (SS), portable subscriber station (PSS), access terminal (AT), user equipment (UE), machine type communication device (machine type communication device, MTC device) and the like, and may include all or some functions of MT, MS, AMS, HR-MS, SS, PSS, AT, UE, and the like.

In addition, the base station (base station, BS) is an advanced base station (advanced base station, ABS), a high reliability base station (high reliability base station, HR-BS), a Node B (node B), an advanced node B (evolved node B, eNodeB), an access point (AP), a radio access station (RAS), a base transceiver station (BTS), a mobile multihop relay (MMR)-BS, a relay serving as a base station station, RS), a relay node (RN) serving as a base station, an advanced relay station (ARS) serving as a base station, and a high reliability relay station (HR) serving as a base station -RS), small base station [femto base station (femto BS), home node B (home node B, HNB), home eNodeB (HeNB), pico base station (pico BS), macro base station (macro BS), micro base station (micro BS) ), etc.], etc., may include all or part of the functions of ABS, NodeB, eNodeB, AP, RAS, BTS, MMR-BS, RS, RN, ARS, HR-RS, small base station, etc. have.

1 is a conceptual diagram illustrating a functional configuration diagram of a 5G system according to an embodiment, and FIG. 2 is a conceptual diagram illustrating a network slice according to an embodiment.

In the present description, a network function may be used in the meaning of a network function instance (virtual machine), and a network slice instance may be used in the meaning of an instance included in a network slice. Virtualized resources and virtualized network resources in the server are allocated to each network slice of the 5G system. Since each network slice is isolated from each other, each network slice can operate irrespective of errors or failures occurring in other slices.

In a 5G system, a network slice is created for each service with different requirements, and a network function (Network Function, NF) also exists in different locations (eg, edge or core cloud) for each network slice. The network functions that each network slice contains are also different. That is, a network function included in one arbitrary network slice may not be included in another network slice (eg, charging, policy control, etc.). Each network slice can create only as many network functions as necessary, cost-effectively. For example, many network resources may be allocated to a network slice during a period in which traffic is concentrated, and network functions of other network slices may be flexibly used when service traffic increases rapidly. In addition, network automation maximizes network value and operational efficiency by simultaneously implementing various services.

The network function includes a slice-shared network function commonly used by a plurality of network slice instances and a slice-specific network function using only a predetermined network slice instance. For example, a slice sharing NF has an Access and Mobility management function (AMF) and a network slice selection function (NSSF), and a slice-specific NF has a session management function (SMF). ) and User Plane Function (UPF).

Referring to FIG. 1 , a 5G system is designed in logical functional units in consideration of virtualization and the like, and a control plane (CP) and a user plane (UP) are divided for each function. The design principle of the 5G architecture is to minimize the dependence of the access network (AN) and the core network (CN).

The network function of the 5G system is defined as follows. AMF supports registration management, connection management, and mobility management functions so that the terminal can receive services from the network. The Authentication Server Function (AUSF) supports the authentication server function. The Network Exposure Function (NEF) supports the function of opening the network function to the outside. The Network Repository Function (NRF) supports the NF instance search function and the NF instance profile management function. NSSF supports the selection function of the network slice instance, the determination function of the AMF, and the like. The Policy Control Function (PCF) supports functions such as an integrated policy framework and policy rule provision. SMF supports functions such as session management, IP address assignment, and UPF selection and control. Unified Data Management (UDM) supports functions such as user identification processing and subscription information management. UPF supports functions such as packet data unit (PDU) session connection to data network (DN), packet routing and forwarding, and QoS processing. Application Function (AF) supports functions such as traffic routing coordination and NEF access. The data network refers to a network to which a terminal accesses. (R)AN stands for Wireless and Wired Access Networks. The PDU means data exchanged between the terminal and the data network.

Referring to FIG. 2 , three network slices are shown. That is, three network slices corresponding to eMBB, URLLC, and mIoT are predefined, and in FIG. 2 , each network slice includes three network slice instances. Each network slice instance contains network functions such as SMF and UPF. The UE may select a network slice according to a service and use a network function in the network slice instance through AMF.

Referring to FIG. 2 , network slices corresponding to eMBB, URLLC, and mIoT are predefined, respectively. Each network slice contains one or more network slice instances. Each network slice instance is configured with a network function necessary to provide a service requested by the UE to the UE, is separated from other network slice instances, and may operate to provide different services.

In the terminal registration step for registering the terminal in the network, the terminal requests a network slice to be used for the service from the network. Thereafter, the network determines whether it can provide the terminal with the network slice requested by the terminal, and notifies the terminal of the request result of the network slice. That is, information of available network slices is transmitted to the terminal by the network.

In the step of establishing a PDU session for a service, the UE notifies the network of a network slice to be used by requesting the network to establish a PDU session. In this case, the network slice instance is divided into early binding (EB) and late binding (LB) according to the timing when the network selects the network slice instance. According to the pre-binding, one network slice instance is selected in the terminal registration step. According to the post binding, a plurality of candidate network slice instances are selected in the terminal registration step, and one network slice instance is determined in the PDU session establishment step. AMF provides terminal registration for the service requested by the terminal and mobility management of the terminal. AMF is a network function shared between network slices, and one AMF is selected for each terminal.

As such, the network of FIG. 2 creates a plurality of network slice instances before receiving the PDU session setup from the terminal. In addition, the AMF selects an SMF to control the PDU session requested by the terminal from among a plurality of SMFs in the selected network slice instance. In addition, the selected SMF selects a UPF for packet delivery and processing, and then, when the SMF and UPF are selected in the network slice instance, it is possible to provide a service to the terminal. That is, in the network shown in FIG. 2 , a plurality of network slice instances are previously generated for each predefined network slice before a PDU session establishment request from the UE. Network functions are assigned per network slice instance. Accordingly, the network of FIG. 2 selects a specific network slice instance in order to provide a service to the terminal, and selects SMF and UPF from among a plurality of selected network functions, so that the selection is performed twice.

3 is a conceptual diagram illustrating a relationship between a network slice and a network function according to an embodiment.

Referring to FIG. 3 , each network slice has different performance requirements and includes network functions related to the performance requirements. In this case, the network slice instance is not created before the service is started. In this description, the network slice corresponds to three types of eMBB, URLLC, and mIoT according to the performance requirements of the service, and the network function included in each network slice may satisfy the performance requirements of the network slice. In FIG. 3 , the first network slice 11 corresponds to the eMBB scheme, the second network slice 12 corresponds to the URLLC scheme, and the third network slice 13 corresponds to the mIoT scheme.

4 is a flowchart illustrating a method of registering a network slice according to an embodiment.

First, the terminal requests the registration of the terminal through a registration request message to the AMF of the network (S110). In this case, the registration request message includes information indicating a service (ie, a network slice) that the terminal can request. Thereafter, the AMF of the network acquires service subscription information of the terminal (S120). To this end, the AMF requests the UDM for service subscription information of the terminal, and the UDM provides the service subscription information of the terminal to the AMF.

The AMF of the network determines a network slice that the terminal can use based on the registration request message of the terminal and the service subscription information of the terminal (S130). If it is determined that the AMF can directly support the determined network slice, the AMF transmits information about the accepted network slice that the terminal can use to the terminal through a Registration Accept message, and the terminal's network registration procedure is successfully completed. It ends (S140). When it is determined that the network slice determined by the AMF cannot be directly supported, the AMF is information about the network slice requested by the terminal through a network slice request (NS Request) message to the NSSF in order to determine a network slice that can be used in the terminal. to convey NSSF verifies whether the network slice requested by the terminal is available according to the network slice supported by the network, and if the network slice requested by the terminal is available, it delivers a network slice accept message to the AMF. When the AMF delivers information about the accepted network slice that the terminal can use to the terminal through a Registration Accept message, the terminal's network registration procedure is successfully terminated (S140).

5 is a flowchart illustrating a method of providing a network slice instance according to an embodiment.

First, the terminal 100 transmits a PDU Session Establishment Request message to the AMF 200 in order to connect to the data network (S210). The AMF 200 that receives the PDU session establishment request message is selected by a RAN (Radio Access Network). The RAN determines the AMF to receive the PDU session establishment request message of the terminal 100 according to the priorities of 1) known AMF information, 2) NS information, and 3) default AMF information. The AMF 200 may manage a network slice allocated to a terminal, a network slice instance, information about a network function, a service band requested by the terminal, etc., and process functions such as generation, update, and deletion of quality of service information. .

The PDU session establishment request message includes information of the network slice requested by the terminal. In addition, the network slice requested by the terminal is a network slice approved to be usable by the terminal in the registration step of the terminal (refer to FIG. 4 ). For example, referring to FIG. 3 , the terminal can use the first network slice, the second network slice, and the third network slice in the terminal registration step. A PDU session establishment request message including information on a network slice indicating the network slice 11 may be transmitted to the AMF 200 . The PDU session establishment request message may further include data network name (Data Network Name, DNN) (same as access point name in LTE system) information along with the information of the network slice requested by the terminal. .

The AMF 200 determines the SMF and the UPF capable of processing the service requested by the terminal based on the information of the network slice and the DNN information (S220). The AMF 200 may select an SMF in consideration of a load among a plurality of SMFs included in the network slice. If the PDU session establishment request message does not include network slice information and DNN information, the AMF 200 may select a default SMF. After the SMF is selected by the AMF 200, the AMF 200 transmits an SMF request message to the selected SMF, so that the SMF receiving the SMF request message selects the UPF for processing the service requested by the terminal. can do. That is, the SMF may be selected by the AMF 200 , and the UPF may be selected by the SMF. The SMF inquires whether the request can be processed by sending a UPF Request message to the selected UPF. If the UPF can handle the SMF's request, it sends a UPF Accept message to the SMF. And the SMF transmits an SMF Accept message to the AMF 200 . At this time, if the AMF 200 does not have the information necessary to select the SMF (that is, the information for selecting the SMF is not stored in the AMF 200), the AMF 200 selects the SMF from the NRF. It may receive information necessary for this or request the NRF to select an SMF. In addition, if the SMF does not have the information necessary for selecting the UPF, the SMF may also receive information necessary for selecting the UPF from the NRF or may request the NRF to select the UPF. In this description, one network slice instance may include one SMF and one UPF.

Thereafter, the AMF 200 transmits a network slice instance request (NSI Request) message to the NSSF 300 to request allocation of a network slice instance (S230). Here, the network slice instance request message includes the determined SMF and UPF information. The NSSF 300 manages network slice information such as a network function included in a network slice and a network function allocated to a network slice instance.

The NSSF 300 creates a network slice instance including the determined SMF and UPF (S240). The NSSF 300 compares the SMF and UPF information received from the AMF 200 with network slice information managed by the NSSF 300 to determine whether to create a new network slice instance. That is, if the network slice managed by the NSSF 300 does not include the determined network slice instance including the SMF and the UPF, a new network slice instance is generated. Thereafter, the NSSF 300 transmits a network slice instance acceptance (NSI Accept) message including information on the generated network slice instance to the AMF 200 (S250). Accordingly, a network slice instance may be allocated. In this case, the information of the network slice instance includes the number of the generated network slice instance. On the other hand, if a network slice instance including the determined SMF and UPF exists in the network slice managed by the NSSF 300, the NSSF 300 transmits the information of the corresponding network slice instance to the AMF 200 through the network slice instance acceptance message. transmit In this case, the information of the network slice instance includes the number of the network slice instance, and the number of the network slice instance is managed by the AMF 200 and the NSSF 300 .

The AMF 200 transmits a PDU Session Establishment Accept message to the terminal to notify the terminal that the preparation to provide the requested service is complete (S260).

6 is a flowchart illustrating a method of providing a network slice instance according to another embodiment.

The terminal 100 transmits a PDU Session Establishment Request message for connecting to the data network to the AMF 200 (S310). The PDU session establishment request message includes network slice information and DNN information. The terminal 100 may be a terminal that has already requested the same network slice (ie, the terminal of FIG. 5 ), or may be another terminal requesting the same network slice as the terminal of FIG. 5 . For example, the terminal 100 of FIG. 6 is an arbitrary terminal requesting a first network slice in which a network slice instance has already been created.

The AMF 200 determines whether a network slice instance is created in the network slice indicated through the PDU session establishment request message. If the same information as the network slice information and DNN information used when creating the created network slice instance is included in the PDU session establishment request message, the AMF 200 selects the corresponding network slice instance. Thereafter, the AMF 200 transmits a network slice instance use request message for using the network slice instance to the SMF 400 (S320). The network slice instance use request message may include network slice information and DNN information. The SMF 400 transmits network slice information and DNN information to the UPF (not shown), and when the network slice instance is available for use, transmits a network slice instance use acceptance message to the AMF 200 ( S330 ). Thereafter, the AMF 200 may transmit a PDU session establishment acceptance message to the terminal 100 (S340).

7 is a conceptual diagram illustrating a network slice instance provided according to an embodiment.

Referring to FIG. 7 , each network slice 11 , 12 , and 13 includes a network slice instance 20 , and each network slice instance 20 includes an SMF and a UPF. In FIG. 7 , some SMFs and UPFs in the network slice may not be included in the network slice instance 20 . That is, the network slice instance 20 may include the optimal SMF and UPF for providing a service, and when the network slice instance 20 is created (or selected) to provide a service to the terminal, it is created (or selected) ) SMF and UPF in the network slice instance 20 operates for a service provided to the terminal.

8 is a block diagram illustrating a network device according to an embodiment.

A network device according to an embodiment may be implemented in a computer system, for example, a computer-readable medium. Referring to FIG. 8 , a computer system 800 includes a processor 810 , a memory 830 , a user interface input device 880 , a user interface output device 870 , and a storage device that communicate via a bus 820 . It may include at least one of (880). Computer system 800 may also include a network interface 890 coupled to a network. The processor 810 may be a central processing unit (CPU) or a semiconductor device that executes instructions stored in the memory 830 or the storage device 880 . The memory 830 and the storage device 880 may include various types of volatile or nonvolatile storage media. For example, the memory may include read only memory (ROM) 831 and random access memory (RAM).

In the embodiment of the present disclosure, the memory may be located inside or outside the processor, and the memory may be connected to the processor through various known means. The memory is a volatile or non-volatile storage medium of various types. For example, the memory may include a read-only memory (ROM) or a random access memory (RAM).

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 improved forms of the present invention are also provided by those skilled in the art using the basic concept of the present invention as defined in the following claims. is within the scope of the right.

Claims (16)

A method for providing a service through a network slice by an Access and Mobility management function (AMF) of a communication network, comprising:
Receiving, from the terminal, a packet data unit (PDU) session establishment request message including information on a network slice corresponding to the service;
Determining an SMF and UPF capable of processing the service from among a plurality of session management functions (SMF) and a plurality of user plane functions (UPF) included in the network slice;
Transmitting a network slice instance request message including information of the determined SMF and UPF to a network slice selection function (NSSF);
Receiving information of a network slice instance including the SMF and the UPF from the NSSF, and
Transmitting a PDU session establishment acceptance message to the terminal in response to the PDU session establishment request message
A method of providing services, including In claim 1,
If the network slice is requested again from the terminal or a terminal different from the terminal, providing the service to the terminal or the other terminal based on information about the network slice instance
A method of providing a service comprising further. In claim 1,
The step of determining the SMF and the UPF,
Selecting an SMF capable of processing the service, and receiving information about the UPF determined by the selected SMF from the selected SMF
A method of providing services, including. In claim 3,
Selecting an SMF that can process the service is,
If the information necessary for selecting the SMF is not stored in the AMF, receiving information necessary for selecting the SMF from a Network Repository Function (NRF). In claim 3,
Selecting an SMF that can process the service is,
If the information necessary for selecting the SMF is not stored in the AMF, requesting a network storage function (NRF) to select the SMF. In claim 1,
The information of the network slice instance includes the number of the network slice instance,
managing the number of the network slice instance
A method of providing a service comprising further. A network device in a communication network, comprising:
including a processor, memory, and a network interface;
The processor executes the program stored in the memory,
Receiving a packet data unit (PDU) session establishment request message including information on a network slice corresponding to a service to be provided to the terminal from the terminal;
Determining an SMF and UPF capable of processing the service from among a plurality of session management functions (SMF) and a plurality of user plane functions (UPF) included in the network slice;
Transmitting a network slice instance request message including information of the determined SMF and UPF to a network slice selection function (NSSF);
Receiving information of a network slice instance including the SMF and the UPF from the NSSF, and
Transmitting a PDU session establishment acceptance message to the terminal in response to the PDU session establishment request message
A network device that does In claim 7,
The processor executes the program,
If the network slice is requested again from the terminal or a terminal different from the terminal, providing the service to the terminal or the other terminal based on information about the network slice instance
Network devices that do more. In claim 7,
When the processor performs the step of determining the SMF and UPF,
Selecting an SMF capable of processing the service, and receiving information about the UPF determined by the selected SMF from the selected SMF
A network device that does In claim 9,
The processor selects an SMF that can process the service,
and if the information necessary for selecting the SMF is not stored in the network device, receiving information necessary for selecting the SMF from a Network Repository Function (NRF). In claim 9,
The processor selects an SMF that can process the service,
and if the information necessary for selecting the SMF is not stored in the network device, requesting a Network Repository Function (NRF) to select the SMF. In claim 7,
The information of the network slice instance includes the number of the network slice instance,
The processor executes the program,
managing the number of the network slice instance
Network devices that do more. A method for a network slice selection function (NSSF) of a communication network to create a network slice instance, comprising:
Receiving a network slice instance request message for providing a service to a terminal from an access and mobility management function (AMF);
Creating a network slice instance including a session management function (SMF) and a user plane function (UPF) capable of processing the service based on the network slice instance request message, and
transmitting a network slice instance accept message to the AMF in response to the network slice instance request message
including,
The network slice instance request message includes information about the SMF and the UPF. In claim 13,
The step of creating the network slice instance comprises:
comparing the information of the SMF and the UPF with information of a network slice managed by the NSSF; and
If the network slice managed by the NSSF does not include the existing network slice instance including the SMF and the UPF, creating a new network slice instance
A method of creating a network slice instance, comprising: 15. In claim 14,
The network slice instance acceptance message includes the number of the new network slice instance. 15. In claim 14,
Transmitting the network slice instance accept message to the AMF comprises:
If the network slice managed by the NSSF includes the existing network slice instance including the SMF and the UPF, transmitting the number of the existing network slice instance to the AMF through the network slice instance accept message.
A method of creating a network slice instance, comprising:

Images