KR20210104511A - Method and apparatus for changing network configuration in wireless communication system - Google Patents

Abstract

The present invention relates to a communication technique that combines a 5G communication system with an IoT technology to support higher data rates after a 4G system and a system thereof. The present invention can be applied to intelligent services (eg, smart home, smart building, smart city, smart car or connected car, healthcare, digital education, retail business, security and safety related services, etc.) based on a 5G communication technology and an IoT-related technology. According to the present invention, disclosed are a method for network slicing and a device thereof.

Description

METHOD AND APPARATUS FOR CHANGING NETWORK CONFIGURATION IN WIRELESS COMMUNICATION SYSTEM

The present disclosure relates to a method of changing the configuration of a network set in a wireless communication system. More particularly, it relates to a method of slicing a network in a next-generation wireless communication system.

Efforts are being made to develop an improved 5th generation (5G) communication system or a pre-5G communication system in order to meet the increasing demand for wireless data traffic after commercialization of the 4G (4th generation) communication system. For this reason, the 5G communication system or the pre-5G communication system is called a 4G network after (Beyond 4G Network) communication system or an LTE (Long Term Evolution) system after (Post LTE) system.

In order to achieve high data rates, 5G communication systems are being considered for implementation in very high frequency (mmWave) bands (eg, 60 gigabytes (60 GHz) bands). In order to alleviate the path loss of radio waves and increase the propagation distance of radio waves in the ultra-high frequency band, in the 5G communication system, beamforming, massive MIMO, and Full Dimensional MIMO (FD-MIMO) are used. ), array antenna, analog beam-forming, and large scale antenna technologies are being discussed.

In addition, for network improvement of the system, in the 5G communication system, an evolved small cell, an advanced small cell, a cloud radio access network (cloud radio access network, cloud RAN), an ultra-dense network (ultra-dense network) ), Device to Device communication (D2D), wireless backhaul, moving network, cooperative communication, Coordinated Multi-Points (CoMP), and reception interference cancellation ) and other technologies are being developed.

In addition, in the 5G system, Hybrid Frequency Shift Keying and Quadrature Amplitude Modulation (FQAM) and Sliding Window Superposition Coding (SWSC), which are advanced coding modulation (Advanced Coding Modulation, ACM) methods, and Filter Bank Multi Carrier (FBMC), an advanced access technology, ), Non Orthogonal Multiple Access (NOMA), and Sparse Code Multiple Access (SCMA) are being developed.

On the other hand, the Internet is evolving from a human-centered connection network where humans create and consume information to an Internet of Things (IoT) network that exchanges and processes information between distributed components such as objects. Internet of Everything (IoE) technology, which combines big data processing technology through connection with cloud servers, etc. with IoT technology, is also emerging. In order to implement IoT, technology elements such as sensing technology, wired and wireless communication and network infrastructure, service interface technology, and security technology are required. , M2M), and MTC (Machine Type Communication) are being studied. In the IoT environment, an intelligent IT (Internet Technology) service that collects and analyzes data generated from connected objects and creates new values in human life can be provided. IoT is a field of smart home, smart building, smart city, smart car or connected car, smart grid, health care, smart home appliance, advanced medical service, etc. can be applied to

Accordingly, various attempts are being made to apply the 5G communication system to the IoT network. For example, in technologies such as sensor network, machine to machine (M2M), and machine type communication (MTC), 5G communication technology is implemented by techniques such as beam forming, MIMO, and array antenna. there will be The application of a cloud radio access network (cloud RAN) as the big data processing technology described above is an example of the convergence of 5G technology and IoT technology.

Due to the development of various information technology (IT) technologies, network equipment can be used interchangeably with 'network elements' in the following virtualized network function (NF) by applying virtualization technology. ), and virtualized NFs are implemented in software form beyond physical limitations and can be installed/operated in various types of clouds or data centers (DCs). In particular, the NF may be freely expanded or reduced according to service requirements, system capacity, or network load, or may be initiated or terminated. Even if these NFs are implemented in the form of software, it should be noted that the physical configuration is not excluded because the NFs have to be basically driven on a physical configuration, for example, a predetermined device. Also, NFs can be implemented with a simple physical configuration, that is, only hardware.

In order to support various services in these various network structures, a network slicing technology has been introduced. Network slicing is a technology that logically configures a network as a set of network functions (NFs) to support a specific service, and separates it from other slices. One terminal may access two or more slices when receiving various services.

The present invention describes a disclosure for effectively managing a network composed of network slices for supporting various services, and preventing signaling load and collision.

In the present invention for solving the above problems, in the network management method of a first network function device for managing a plurality of network function (NF) devices in a wireless communication system, from a base station, information about setting change of the base station Receiving a first update request message comprising a; determining whether to change a network configuration for selecting a network slice based on the received base station update request message; transmitting, to a second network function device managing network state information, a second update request message for servicing the network slice generated based on the first update request message; receiving, from the second network function device, a second update response message corresponding to the second update request message; and transmitting, to the base station, a first update response message generated based on the second update response message.

According to the disclosed embodiment, by managing a network slice in a set unit, radio resources can be efficiently used and various services can be efficiently provided to users.

1 is a diagram illustrating a wireless communication system according to various embodiments of the present disclosure.
2 is a diagram illustrating a method of selecting a network slice when a new base station (RAN) is added or configuration information of a base station is changed in a mobile communication system.
3 is a diagram illustrating a method for more effectively managing NSSAI Availability according to an embodiment of the present disclosure.
4A is a diagram illustrating an overall method of managing slice information in a set unit according to an embodiment of the present disclosure.
FIG. 4B is a diagram illustrating a method by which the Master AMF manages slice information in a set unit according to an embodiment of the present disclosure.
5 is a diagram illustrating a method for managing Profiles in units of NF sets according to an embodiment of the present disclosure.
6 is a diagram illustrating another embodiment of the present disclosure.
7A is a diagram illustrating an AMF selection process using the Master AMF.
7B is a diagram illustrating an NF registration process according to an embodiment of the present invention.
7c is a diagram illustrating an NF registration process according to an embodiment of the present invention.
7D is a diagram illustrating an NF registration process according to an embodiment of the present invention.
7E is a diagram illustrating an NF registration process according to an embodiment of the present invention.
8 is a diagram illustrating a method for an NF to receive information of an SCP through an NRF according to an embodiment of the present invention.
9 is a diagram illustrating a terminal device according to embodiments of the present disclosure.
10 is a diagram illustrating a base station apparatus according to embodiments of the present disclosure.
11 is a diagram illustrating an NF device according to embodiments of the present disclosure.

Terms used in the present disclosure are used only to describe specific embodiments, and may not be intended to limit the scope of other embodiments. The singular expression may include the plural expression unless the context clearly dictates otherwise. Terms used herein, including technical or scientific terms, may have the same meaning as commonly understood by one of ordinary skill in the art described in the present disclosure. Among the terms used in the present disclosure, terms defined in a general dictionary may be interpreted with the same or similar meaning as the meaning in the context of the related art, and unless explicitly defined in the present disclosure, ideal or excessively formal meanings is not interpreted as In some cases, even terms defined in the present disclosure cannot be construed to exclude embodiments of the present disclosure.

In various embodiments of the present disclosure described below, a hardware approach method will be described as an example. However, since various embodiments of the present disclosure include technology using both hardware and software, various embodiments of the present disclosure do not exclude a software-based approach.

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. At this time, it should be noted that in the accompanying drawings, the same components are denoted by the same reference numerals as much as possible. In addition, detailed descriptions of well-known functions and configurations that may obscure the gist of the present invention will be omitted.

In describing embodiments in the present specification, descriptions of technical contents that are well known in the technical field to which the present invention pertains and are not directly related to the present invention will be omitted. This is to more clearly convey the gist of the present invention without obscuring the gist of the present invention by omitting unnecessary description.

For the same reason, some components are exaggerated, omitted, or schematically illustrated in the accompanying drawings. In addition, the size of each component does not fully reflect the actual size. In each figure, the same or corresponding elements are assigned the same reference numerals.

Advantages and features of the present invention, and a method for achieving them will become apparent with reference to the embodiments described below in detail in conjunction with the accompanying drawings. However, the present invention is not limited to the embodiments disclosed below, but may be implemented in various different forms, and only these embodiments allow the disclosure of the present invention to be complete, and common knowledge in the art to which the present invention pertains. It is provided to fully inform the possessor of the scope of the invention, and the present invention is only defined by the scope of the claims. Like reference numerals refer to like elements throughout.

At this time, it will be understood that each block of the flowchart diagrams and combinations of the flowchart diagrams may be performed by computer program instructions. These computer program instructions may be embodied in a processor of a general purpose computer, special purpose computer, or other programmable data processing equipment, such that the instructions performed by the processor of the computer or other programmable data processing equipment are not described in the flowchart block(s). It creates a means to perform functions. These computer program instructions may also be stored in a computer-usable or computer-readable memory that may direct a computer or other programmable data processing equipment to implement a function in a particular manner, and thus the computer-usable or computer-readable memory. It is also possible that the instructions stored in the flow chart block(s) produce an article of manufacture containing instruction means for performing the function described in the flowchart block(s). The computer program instructions may also be mounted on a computer or other programmable data processing equipment, such that a series of operational steps are performed on the computer or other programmable data processing equipment to create a computer-executed process to create a computer or other programmable data processing equipment. It is also possible that instructions for performing the processing equipment provide steps for performing the functions described in the flowchart block(s).

Additionally, each block may represent a module, segment, or portion of code that includes one or more executable instructions for executing specified logical function(s). It should also be noted that in some alternative implementations it is also possible for the functions recited in blocks to occur out of order. For example, two blocks shown one after another may in fact be performed substantially simultaneously, or it is possible that the blocks are sometimes performed in the reverse order according to the corresponding function.

At this time, the term '~ unit' used in this embodiment means software or hardware components such as FPGA or ASIC, and '~ unit' performs certain roles. However, '-part' is not limited to software or hardware. The '~ unit' may be configured to reside on an addressable storage medium or may be configured to refresh one or more processors. Thus, as an example, '~' denotes components such as software components, object-oriented software components, class components, and task components, and processes, functions, properties, and procedures. , subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and variables. The functions provided in the components and '~ units' may be combined into a smaller number of components and '~ units' or further separated into additional components and '~ units'. In addition, components and '~ units' may be implemented to play one or more CPUs in a device or secure multimedia card.

Hereinafter, the present disclosure relates to a method and apparatus for supporting various services in a wireless communication system. Specifically, the present disclosure describes a technique for supporting various services by supporting mobility of a terminal in a wireless communication system.

A term for identifying an access node used in the following description, a term referring to a network entity or NF (network functions), a term referring to messages, a term referring to an interface between network objects, various Terms and the like referring to identification information are exemplified for convenience of description. Accordingly, the present disclosure is not limited to the terms described later, and other terms referring to objects having equivalent technical meanings may be used.

For convenience of description below, the present disclosure uses terms and names defined in 3GPP LTE (3rd generation partnership project long term evolution) and 5G standards. However, the present disclosure is not limited by the terms and names, and may be equally applied to systems conforming to other standards.

Hereinafter, for convenience of description, objects for exchanging information for access control and state management will be collectively described as NF. NF is, for example, an access and mobility management function (Access and Mobility Management Function, hereinafter referred to as AMF) device, a session management function (Session Management Function, hereinafter referred to as SMF) device, a network slice selection function device (Network slice selection function) , hereinafter referred to as NSSF) may be at least one device among devices. However, embodiments of the present disclosure may be equally applied even when NF is actually implemented as an instance (Instance, respectively AMF Instance, SMF Instance, NSSF Instance, etc.).

In the present disclosure, an Instance is a specific NF in the form of a code of software, and a physical computing system, for example, a physical or / and logical from a computing system to perform the function of the NF in a specific computing system existing on the core network. It may mean a state in which resources are allocated and executable. Therefore, all NF instances such as AMF Instance and SMF Instance may mean that physical or/and logical resources are allocated for NF operation from a specific computing system existing on the core network, respectively, and can be used. As a result, when NF devices such as physical AMF and SMF exist, the NF Instance that receives and uses physical and/or logical resources for NF operation from a specific computing system existing on the network can perform the same operation. have.

1 illustrates a wireless communication system according to various embodiments of the present disclosure.

Referring to FIG. 1 , a radio access node (RAN) 110 and a user equipment (UE) 120 are illustrated as some of nodes using a radio channel in a wireless communication system. 1 illustrates only one base station 110 and one terminal 120, other base stations identical to or similar to the base station 110 may be further included. Also, in FIG. 1 , only a case in which only one terminal 120 communicates within one base station 110 is exemplified. However, it is obvious that a plurality of terminals can actually communicate within one base station 110 .

The base station 110 is a network infrastructure that provides a wireless connection to the terminal 120 . The base station 110 has coverage (not shown in FIG. 1 ) defined as a certain geographic area based on a distance capable of transmitting a signal. In addition to the base station, the base station 110 includes an 'access point (AP)', an 'eNodeB (eNodeB)', a '5G node (5th generation node)', a 'wireless point' , may be referred to as a 'transmission/reception point (TRP)' or other terms having an equivalent technical meaning.

The terminal 120 is a device used by a user, and performs communication with the base station 110 through a wireless channel. In some cases, the terminal 120 may be operated without the user's involvement. For example, the terminal 120 is a device that performs machine type communication (MTC) and may not be carried by a user. The terminal 120 illustrated in FIG. 1 may include at least one portable user device and may include at least one MTC. The terminal 120 of FIG. 1 is a 'terminal', 'mobile station', 'subscriber station', 'remote terminal', 'wireless terminal', Alternatively, it may be referred to as a 'user device' or another term having an equivalent technical meaning.

The AMF device 131 may be a network entity that manages wireless network access and mobility for the terminal 120 . The SMF device 132 may be a network entity that manages connection of a packet data network for providing packet data to the terminal 120 . The connection between the terminal 120 and the SMF 132 may be a PDU session (Session).

The user plane function (hereinafter referred to as UPF) device 133 may be a gateway for transmitting packets transmitted and received by the terminal 120 or a network entity serving as a gateway. The UPF 133 may be connected to a data network (DN) 140 connected to the Internet to provide a path for data transmission/reception between the terminal 120 and the DN 140 . Accordingly, the UPF 133 may route data to be transmitted to the Internet among packets transmitted by the terminal 120 to the Internet data network.

The network slice selection function (NSSF) device 134 may be a network entity that performs a network selection operation described in the present disclosure, for example, an operation of selecting a network slice. The operation of the NSSF device 134 will be described in more detail in the drawings to be described later.

The Authentication Server Function (AUSF) device 151 may be an equipment (network entity) that provides a service for processing subscriber authentication.

Network exposure function (NEF) device 152 can access information for managing the terminal 120 in the 5G network, subscription to a mobility management event of the terminal, and session of the terminal A network entity that can transmit a subscription to an event, a request for session-related information, a request for session-related information, a billing information setting for the corresponding terminal, a request to change the PDU session policy for the corresponding terminal, and a small data for the corresponding terminal can be

The Network Repository Function (NRF) device 153 stores state information of NFs, and may be an NF (network entity) having a function of processing a request to find an NF accessible to other NFs.

The policy and charging function (Policy and Charging Function, hereinafter referred to as PCF) device 154 may be a network entity that applies the service policy of the mobile operator to the terminal 120, the charging policy, and the policy for the PDU session. have.

The unified data management (hereinafter referred to as UDM) device 155 may be a network entity that stores information about a subscriber and/or the terminal 120 .

The application function (AF) device 156 may be an NF (network entity) having a function of providing a service to users by interworking with a mobile communication network.

The service communication proxy (Service Communication Proxy, SCP) device 157 is an NF (network entity) that provides functions such as NF discovery for communication between NFs, and message transfer between NFs. SCP (157) may operate in an integrated form with the NRF (153) according to the operator's selection, in this case, the SCP (157) includes the function of the NRF (153), or, conversely, the NRF (153) is the SCP (157) can be included as a function of

Hereinafter, for convenience of description, objects for exchanging information for access control and state management will be collectively described as NF. NF is, for example, an access and mobility management function (Access and Mobility Management Function, hereinafter referred to as AMF) device, a session management function (Session Management Function, hereinafter referred to as SMF) device, a network slice selection function device (Network slice selection function) , NSSF) devices, etc. may be one of the NF devices. However, embodiments of the disclosure of the present disclosure may be equally applied even when the NF is actually implemented as an instance (Instance, respectively, AMF Instance, SMF Instance, NSSF Instance, etc.).

2 is identified by a new base station (RAN) added in a mobile communication system, or configuration information of a base station, that is, a tracking area (TA) supported by the base station, and NW Slice (Single-Network Slice Selection Assistance Information (S-NSSAI)). logical network) is added or changed, this is notified to another NF, and using this, a network slice suitable for the subscriber's service can be selected.

Step 1: A base station is newly added, starts an operation, or a base station setting, that is, a TA (Tracking Area) supported by the base station, NW Slice (a logical network identified by S-NSSAI) is added or changed ( 201).

Step 2: The base station performs the NG Setup procedure when a new relationship and connection with the AMF for network configuration and management is required, or performs the RAN configuration update procedure if there is an existing connection (202). In this case, the request message sent by the base station may include the name of the base station, an identifier, and a list of TAs supported by the base station, and the list of TAs may include one or more S-NSSAI supported by the corresponding TA for each TA.

Step 3: The AMF determines whether network slice and TA information are added or changed according to the information received from the base station to be considered in the slice selection process, and if the network configuration for slice selection is changed, the AMF performs the NSSF (or It can be replaced with NF that manages and finds network status information such as NRF and SCP) and calls the service for NSSAI Availability Update (203). Network Slice Selection Assistance Information (NSSAI) may consist of one or more S-NSSAIs. The service request message may also include a list of TAIs and NSSAIs to be added or changed.

Step 4: The NSSF updates or adds slice and slice-supported area (TA) information when it is necessary to change it according to the request of the AMF (204). At this time, the data stored by the NSSF can be identified using the identifier (ID) of the requested AMF Instance. The NSSF may determine the application time (time) of the updated NSSAI Availability.

Step 5: The NSSF transmits a response to the request of the AMF, and at this time, if the slice information (AuthorizedNssaiAvailability) allowed to be used by the AMF is changed or added, it may be notified including it ( 205 ). At this time, the NSSF may transmit the time information included in the AMF in order to match the availability application time updated in step 5 with other AMFs. Upon receiving the time information, the AMF operates by applying the updated information when the corresponding time condition is satisfied.

Step 6: The AMF transmits a response to the request of the base station, and at this time, configuration information of the AMF may be included (206). If the network configuration (TA, or supported NSSA, PLMN, etc.) supported by the AMF is changed from step 5 (205), the base station is notified through this process.

Another embodiment of the present disclosure proposes a method for more effectively managing a network slice and preventing a signaling load and collision in a network configuration composed of an NF Set.

If two or more AMFs (including instances) are included in one AMF set in the embodiment of FIG. 2, and one set supports the same TA and slice, addition of a base station and change of settings is performed by adding an NF belonging to the set (eg, For example, AMF) should be transmitted, and all NFs receiving this transmit a request to notify other NSSFs (or NRFs, etc.) of the addition/change of their NSSAI Availability. In this case, if the number of base stations is large or the number of AMFs belonging to a set is large, a signaling overload may occur, or a situation of inconsistency or collision of network configuration information may occur due to a difference in signaling transmission and processing time.

3 shows a method for more effectively managing NSSAI Availability according to an embodiment of the present disclosure. In this embodiment, NSSAI Availability management is characterized in that it is performed by the Master AMF (or Default AMF) belonging to the AMF set. The Master AMF may be selected as one of the AMFs belonging to the AMF set, and one designated AMF may be set to perform the Master role, or the AMFs may be alternately selected and performed by a Round-Robin method. At this time, information may be exchanged between AMFs to inform that only one AMF operates as a Master in the AMF set at a specific point in time.

Step 1: A base station is newly added, starts an operation, or a base station setting, that is, a TA (Tracking Area) supported by the base station, NW Slice (a logical network identified by S-NSSAI) is added or changed ( 301).

Steps 2 and 3: The base station performs the NG Setup procedure when a new relationship and connection with the connected AMF and Master AMF is required for network configuration and management, or performs the RAN configuration update procedure if there is an existing connection (302, 303) ). In this case, the request message sent by the base station may include the name of the base station, an identifier, and a list of TAs supported by the base station, and the list of TAs may include one or more S-NSSAI supported by the corresponding TA for each TA.

Step 4: The Master AMF determines whether network slice and TA information are added or changed according to the information received from the base station to be considered in the slice selection process. If the network configuration for slice selection is changed, the Master AMF performs the (or it can be replaced with NF that manages and finds network status information such as NRF and SCP) and calls the service for NSSAI Availability Update (304). Network Slice Selection Assistance Information (NSSAI) may consist of one or more S-NSSAIs. The service request message may also include a list of TAIs and NSSAIs to be added or changed.

Step 5: The NSSF updates or adds slice and slice-supported area (TA) information if it is necessary to change it according to the request of the master AMF (305). At this time, the data stored by the NSSF can be identified using the identifier (ID) of the requested Master AMF Instance. The NSSF may determine the application time (time) of the updated NSSAI Availability.

Step 6: NSSF sends a response to Master AMF's request. At this time, if slice information (eg AuthorizedNssaiAvailability) allowed to be used by AMF is changed or added, it can be notified to Master AMF including this. There is (306). At this time, the NSSF may transmit the time information included in the Master AMF in order to match the availability application time updated in step 5 (305) with other AMFs. After receiving the time information, the Master AMF operates by applying the updated information when the corresponding time condition is satisfied.

Step 7: The NSSF may also update NSSAI Available Information of other AMF instances belonging to the AMF set requested from the Master AMF (307). That is, the NSSF may find the AMF Set for Slice information received from the Master AMF, find the AMF Instances belonging to the corresponding Set, and then update the NSSAI Available Information identified by the Instance ID of the AMF Instance together.

Step 8: If the NSSAI Availability Information is updated for other AMF Instances belonging to the AMF set, and the AuthorizedNssaiAvailability for each AMF Instance is changed or added, the NSSF may transmit a message to notify each AMF Instance (308). ). This can be done using the NSSAI Availability Update Notification service. At this time, the NSSF may transmit the time information included in the AMF in order to match the availability application time updated in step 5 305 with other AMF Instances. Upon receiving the time information, the AMF operates by applying the updated information when the corresponding time condition is satisfied.

Step 9: AMFs transmit a response to the request of the base station, and at this time, configuration information of the AMF may be included (309). If the network configuration (TA, or supported NSSA, PLMN, etc.) supported by the AMF is changed from step 5 (305), the base station is notified through this process.

In another embodiment of the present disclosure, in order to solve the above problem, information shared in the same (common) in a set of specific NFs is separately defined as an NF Set Profile, and a method for improving signaling efficiency and matching state information using this is defined. suggest

The NF Set Profile is stored or managed using an identifier that can identify the NF set (the NF Set ID or the ID of the NF instance that manages the NF set information). The NF set profile may include the information shown in Table 1, and any type of information shared by NF instances in the NF set (eg, Serving Scope: supported area, etc.) may be added.

Similarly, information on available slices (NSSAI Availability) may be shared and managed in units of sets. At this time, the unit for storing/managing slice information in the NF is not the ID of each AMF, but the AMF Set ID or the ID of the NF that manages information for each set. That is, the resource in which the NSSF stores the corresponding information is managed for each set, and is identified by the AMF Set ID or the ID of the NF that manages the information for each set.

NSSAI Availability per Set in a set unit may be composed of the following data as shown in Table 2.

supportedNssaiAvailabilityData may be configured as shown in Table 3 below.

4A and 4B are diagrams illustrating a method of managing slice information in a set unit according to an embodiment of the present disclosure.

First, an overall process of managing slice information in a set unit according to the present disclosure will be described with reference to FIG. 4A .

Step 1: A base station is newly added, starts an operation, or a base station setting, that is, a TA (Tracking Area) supported by the base station, NW Slice (a logical network identified by S-NSSAI) is added or changed ( 401).

Steps 2 and 3: The base station performs the NG Setup procedure when a new relationship and connection for network configuration and management with the connected AMF and Master AMF is required, or performs the RAN configuration update procedure if there is an existing connection (402, 403) ). In this case, the request message sent by the base station may include the name of the base station, an identifier, and a list of TAs supported by the base station, and the list of TAs may include one or more S-NSSAI supported by the corresponding TA for each TA.

Step 4: The Master AMF determines whether network slice and TA information are added or changed to the AMF Set according to the information received from the base station and should be considered in the slice selection process. If the network configuration for slice selection is changed, The Master AMF calls the service for NSSAI Availability Update in a set unit with NSSF (or it can be replaced with NF that manages and finds network status information such as NRF and SCP) (404). The service request may include NSSAI availability information in units of sets described above.

Step 5: The NSSF updates or adds slices to be applied to the set and area (TA) information in which slices are supported when changes are required according to the request of the master AMF (405). In this case, the data stored by the NSSF can be identified using the identifier (ID) of the requested AMF Set. The NSSF may determine the application time (time) of the updated NSSAI Availability per Set.

Step 6: The NSSF transmits a response to the request of the Master AMF, and at this time, if the slice information (AuthorizedNssaiAvailability) allowed to be used for the AMF Set is changed or added, it may be notified including it (406). At this time, the NSSF may transmit the time information including the time information to the Master AMF in order to match the availability application time updated in step 5 with other AMFs. After receiving the time information, the Master AMF operates by applying the updated information when the corresponding time condition is satisfied.

Step 7: The NSSF may also update NSSAI Available Information of other AMF instances belonging to the AMF set requested from the Master AMF (407). That is, the NSSF may find the AMF Set for Slice information received from the Master AMF, find AMF Instances belonging to the corresponding Set, and then update the NSSAI Available Information identified by the Instance ID of the AMF Instance together.

Step 8: NSSF may notify NSSAI Availability Info per Set for other AMF Instances belonging to the AMF set (408). That is, when AuthorizedNssaiAvailability per set is changed or added, a message for notifying this may be transmitted to each AMF Instance. This can be done using the NSSAI Availability Update Notification service. At this time, the NSSF may transmit the time information included in the AMF in order to match the availability application time updated in step 5 with other AMF Instances. Upon receiving the time information, the AMF operates by applying the updated information when the corresponding time condition is satisfied.

Step 9: Each AMF Instance may update the NSSAI Available Information of its own AMF instance unit together using the Authorized Slice information of the set unit received in step 8 (409).

Step 10: The AMFs including the Master AMF transmit a response to the request of the base station, and at this time, the AMF configuration information may be included (410). If the network configuration (TA, supported NSSA, PLMN, etc.) supported by the AMF is changed from step 5, the base station is notified through this process.

FIG. 4B illustrates the operation of the Master AMF according to a time-series flow in relation to the embodiment described with reference to FIG. 4A.

In FIG. 4B , when a new relationship and connection for AMF configuration and management occurs from the base station, the Master AMF may receive a RAN setting change information update request message requesting an NG Setup procedure or RAN configuration update (421). .

Based on the RAN setting change information message received from the base station, the Master AMF may determine whether a network configuration change such as adding or changing network slice and TA information to the AMF set has occurred ( 422 ).

If the network configuration for slice selection is changed, the Master AMF is NSSF (or it can be replaced with NF that manages and finds network status information such as NRF, SCP, etc.) An update request message for NSSAI Availability Update in a set unit to be provided may be transmitted (423).

Thereafter, the NSSF updates or adds network configuration change information using the AMF Set identifier included in the Set unit update request message of the Master AMF, and sends a response to the update request to the Master AMF, and the Master AMF receives it. can (424).

The Master AMF may transmit a response including the AMF configuration information to the base station according to the slice information updated on a set basis (425). Change information of the network configuration (TA, or supported NSSAI, PLMN, etc.) supported by the AMF may be transmitted to the base station through this.

5 is a diagram for Profile management in units of NF sets according to an embodiment of the present disclosure. In this embodiment, the management of the NF set profile is characterized in that it is performed by the Master NF (or Default AMF) belonging to the NF set. The Master NF may be selected as one of the NFs belonging to the NF set, and one designated NF Instance may be set to perform the Master role, or the NF Instances may be alternately selected and performed by a Round-Robin method. At this time, information can be exchanged between NF instances to inform that only one NF instance operates as a Master in the NF set at a specific time.

Step 1: NF set is newly created/added, or setting information of the NF set is changed (501). In this case, the configuration information of the NF set means a set of parameters or attributes that are shared and commonly applied by all NF instances belonging to the NF set.

Step 2: The Master NF performs a process for registering the Profile of the NF set to which it belongs with the NRF (or SCP) (502). At this time, the NF Register or NF set register service can be called, and this service request includes the identifier (ID) of the NF set to be registered and the NF set Profile. The NF set profile may include identifiers of NF instances belonging to the NF set.

Step 3: The NRF stores the profile of the NF set using the received information and creates a resource for it (503). Afterwards, the resource for the NF set profile can be identified by the NF set ID.

Step 4: The NRF transmits a response to the request to the Master NF (504).

Step 5: The NRF may transmit the NF set profile to notify other NF instances belonging to the NF set of the created/updated set profile ( 505 ). In this case, the NRF may use the NF status notify or NF set status notify service.

Step 6: NF instances that have received the notification from the NRF transmit an acknowledgment to the notification to the NRF (506).

6 is a diagram illustrating another embodiment of the present disclosure.

Step 1: NF set is newly created/added, or setting information of the NF set is changed (601). In this case, the configuration information of the NF set means a set of parameters or attributes that are shared and commonly applied by all NF instances belonging to the NF set.

Step 2: The Master NF performs a process for registering the Profile of the NF set to which it belongs with the NRF (or SCP) (602). At this time, the NF Register or NF set register service can be called, and this service request includes the identifier (ID) of the NF set to be registered and the NF set Profile. The NF set profile may include identifiers of NF instances belonging to the NF set.

Step 3: The NRF stores the profile of the NF set using the received information and creates a resource for this (603). Afterwards, the resource for the NF set profile can be identified by the NF set ID.

Step 4: The NRF sends a response to the request to the Master NF (604).

Step 5: When the registration of the NF set profile is successful, the Master NF may transmit the NF set profile to notify other NF instances of the created/updated set profile (605). In this case, the Master NF may use an NF status notify service, an NF set status notify service, or a heartbeat service.

Step 6: NF instances that have received a notification from the Master NF transmit an acknowledgment to the notification to the Master NF (606).

7A is a diagram illustrating an AMF selection process using the Master AMF. The role and selection method of the Master AMF are the same as those disclosed in FIGS. 3 and 4 .

Step 1: The terminal transmits an RRC message including a NAS message for registration to the base station (701). In this case, the terminal may include slice information (NSSAI) to which it is to be accessed as an AS Layer parameter.

Step 2: The base station may determine whether AMF selection can be performed using the identifier (ID) used by the terminal, slice information, and configured information. If the base station cannot perform AMF selection using slice information, or the message sent by the terminal does not include the AS layer slice information (702), the base station selects the Master (or Default) AMF, and the initial transmitted by the terminal The UE message is transferred to the Master AMF (703).

Step 3: The Master AMF may receive subscription information from the UDM if necessary, and at this time, slice information applicable to the subscriber, Subscribed S-NSSAIs, may be received (704). The Master AMF may consider this when the UE includes the slice information (Requested NSSAI) selected in the NAS Layer, and selects the AMF in consideration of the subscription information received from the UDM (705). If it is able to provide a service to the terminal, the rest of the registration process is performed. If another AMF is selected, the Master AMF sends a Reroute NAS message including information that can identify the selected AMF (AMF information, AMF set information, or other Master AMF information) and an Initial UE message (Registration request) transmitted by the terminal. send to the base station (706).

Step 4: The base station again selects the AMF to which the terminal's request is to be delivered using the information received from the Master AMF (707). If one AMF is designated and interworking with the corresponding AMF is possible, the base station selects the corresponding AMF. If AMF set information is received, one AMF may be selected from among the AMF sets. If other Master AMF information is received, the message is transmitted by selecting the corresponding Master AMF.

7B is a diagram illustrating an NF registration process according to an embodiment of the present invention.

Step 1: One NF of the network performs an NF Register process to register its own information with the NRF (7201). In this case, the request message transmitted by the NF includes the profile of the NF, and may also include supported features information indicating the functions supported by the NF. In particular, among the supported functions of the NF, indirect communication, delegated discovery, SM context transfer, binding indication, and whether support for each of the NF sets may be included as enhancements to SBA of the SBA. Supported features may be included in a part of the NF profile, or may be included in the request message in the form of separate data separated from the NF profile.

Step 2: The NRF transmits a response to the NF's request (7202), and the response message may include supported features available in the network in which the NF is currently registered. The contents and message structure that can be included in the supported feature are the same as in step 1. In addition, the NRF response may additionally include information to be applied when the NF uses the SCP in the network. The SCP information may include the address of the SCP, the operation mode of the SCP (one of modes A, B, C, and D), whether to use in-direct communication, and whether to use delegated discovery.

Step 3: The NF stores the information received from the NRF, and then performs an operation using the received information (whether to use SCP, whether to use in-direct communication, whether to use delegated discovery, etc.) when operating thereafter (7203).

7c is a diagram illustrating an NF registration process according to an embodiment of the present invention.

Step 1: One NF in the network performs an NF Register process to register its own information with the NRF (7301). In this case, the request message transmitted by the NF includes the profile of the NF, and may also include supported features information indicating the functions supported by the NF. In particular, among the functions supported by the NF, indirect communication, delegated discovery, SM context transfer, binding indication, and whether support for each of the NF sets may be included as enhancements to SBA of the SBA. Supported features may be included in a part of the NF profile, or may be included in the request message in the form of separate data separated from the NF profile. In this case, the SCP may play a role of transmitting and receiving a message between the NF and the NRF.

Step 2: The NRF transmits a response to the NF's request (7302), and the response message may include supported features available in the network in which the NF is currently registered. The contents and message structure that can be included in the supported feature are the same as in step 1.

Step 3: The response message sent by the NRF is first received by the SCP, and before being delivered, the SCP may include SCP operation information. The SCP information may include the address of the SCP, the operation mode of the SCP (one of modes A, B, C, and D), whether to use in-direct communication, and whether to use delegated discovery (7303). The SCP transmits a response message to the NF by including the information in addition to the information to be transmitted by the NRF.

Step 4. The NF stores information received from the NRF (and SCP), and then performs an operation using the received information (whether or not to use SCP, whether to use in-direct communication, whether to use delegated discovery, etc.) when operating thereafter (7304).

7D is a diagram illustrating an NF registration process according to an embodiment of the present invention.

Step 1: One NF in the network performs a discovery request with the NRF to find, select, or receive information from another NF (7401). In this case, the request message transmitted by the NF may include information related to the target it is looking for. At this time, when the NF finds the NF it is looking for, it is an enhancement to SBA of the SBA. Indirect communication, delegated discovery, SM context transfer, binding indication, support for each NF set may be included as a query parameter. .

Step 2: The NRF searches for a candidate NF whose condition is satisfied for the request of the NF, and transmits a response (7402). The response message may include information on candidate NFs that the requested NF can select and supported features supported by the candidate NF. In addition, the response of the NRF may additionally include information to be applied when using the SCP in the network when the requesting NF communicates with the candidate NFs. The SCP information may include the address of the SCP, the operation mode of the SCP (one of modes A, B, C, and D), whether to use in-direct communication, and whether to use delegated discovery.

Step 3: The NF stores the information received from the NRF, and then performs an operation using the received information (information of candidate NFs, whether or not to use SCP, whether to use in-direct communication, whether to use delegated discovery, etc.) 7403).

7E is a diagram illustrating an NF registration process according to an embodiment of the present invention.

Step 1: One NF (acting as a consumer) in the network sends a request to request a specific service to another NF (acting as a producer). In this case, the request message transmitted by the Consumer NF may include parameters for performing the corresponding service and Supported Features information supported by the Consumer NF. The Supported Feature information may include support for indirect communication, delegated discovery, SM context transfer, binding indication, and each NF set as enhancements to SBA among the consumer NF support functions. The supported features may be included in a part of the service request parameters, or may be separated and included in the request message in the form of separate data (7501).

Step 2: The producer NF processes the service request of the consumer NF and transmits a response message thereto (7502). In this case, the response message transmitted by the Producer NF may include parameters for the corresponding service execution result and Supported Features information supported by the Producer NF. The Supported Feature information is an enhancement to SBA among the supported functions of the Producer NF, and may include indirect communication, delegated discovery, SM context transfer, binding indication, and whether to support each of the NF sets. Supported features may be included in a part of the service result parameters, or may be separated and included in the request message in the form of separate data (7502).

Step 3: The two NFs store the exchanged information, and then perform an operation using the received information (information of the peer NF, whether or not to use SCP, whether to use in-direct communication, whether to use delegated discovery, etc.) when operating afterwards (7503) ).

8 is a diagram illustrating a method for an NF to receive information of an SCP through an NRF according to an embodiment of the present invention.

Step 1: One NF (operable as a consumer or producer) of the network transmits a discovery request to the NRF to receive information for using the SCP according to the configuration of the NW (801). In this case, the request message transmitted by the NF may include a parameter indicating that the target of discovery is an SCP, and Supported Features information supported by the NF. Supported Feature information may include indirect communication, delegated discovery, SM context transfer, binding indication, support for each of the NF set as enhancements to SBA among the supported functions of the NF. Supported features may be included in a part of service request parameters, or may be separated and included in the request message in the form of separate data. Also, when the requesting NF needs to receive SCP information for a specific NW Slice, the request message may include the identifier of the target Slice. The request may be a general NF Discovery request, an SCP Discovery request only for SCP, or a request for receiving message delivery/routing information.

Step 2: The NRF searches for an SCP that satisfies the condition for the NF's request, and transmits a response (802). The response message may include information on the SCP that the requested NF can use (SCP's address, NF ID, identifier of the supported slices of the SCP, connection relationship between the SCP and other SCPs, etc.) and supported features supported by the SCP. In addition, the response of the NRF may additionally include information to be applied when using the SCP in the network when the requesting NF communicates with other NFs. This may include the operation mode of the SCP (one of modes A, B, C, D), whether to use in-direct communication, and whether to use delegated discovery. If no SCP is satisfied for the NF's request, the NRF may explicitly inform the NF of this through a response message. The response is a response to the request generated in step 1, that is, it may be a response to a general NF Discovery or SCP Discovery only for SCP, or a response to a request for receiving message delivery/routing information. If the connection between NF and SCP consists of multiple hops in the network configuration, the Discovery response transmits only the information of the NF (or SCP) of the Next Hop from the point of view of the NF (or SCP) that requested discovery, or includes the order of each hop. All information of NF (or SCP) on the transmission path may be included.

Step 3: NF stores the information received from the NRF, and then performs an operation using the received information (whether or not to use SCP, whether to use the SCP address, NF ID, whether to use in-direct communication, whether to use delegated discovery, etc.) do (803). If the response received in step 2 contains information that there is no SCP or does not contain SCP information, the NF may assume that there is no SCP during subsequent operation.

9 is a diagram illustrating the structure of a terminal according to an embodiment of the present invention.

Referring to FIG. 9 , the terminal may include a transceiver 910 , a terminal controller 920 , and a storage 930 . In the present invention, the terminal control unit 820 may be defined as a circuit or an application-specific integrated circuit or at least one processor.

The transceiver 910 may transmit/receive signals to and from other network entities. The transceiver may receive, for example, system information from a base station, and may receive a synchronization signal or a reference signal.

The terminal control unit 920 may control the overall operation of the terminal according to the embodiment proposed in the present invention. For example, the terminal control unit may control the signal flow between blocks to perform an operation according to the above-described drawings and flowcharts. Specifically, the terminal control unit operates according to a control signal from the base station and may send and receive messages or signals with the terminal and/or network entities.

The storage unit 930 may store at least one of information transmitted/received through the transceiver unit 910 and information generated through the terminal control unit.

10 is a diagram illustrating a structure of a base station according to an embodiment of the present invention.

Referring to FIG. 10 , the base station may include a transceiver 1010 , a base station controller 1020 , and a storage 1030 . In the present invention, the base station controller 1020 may be defined as a circuit or an application-specific integrated circuit or at least one processor.

The transceiver 1010 may transmit/receive signals to and from other network entities. The transceiver may, for example, transmit system information to the terminal, transmit a synchronization signal or a reference signal, and receive information for providing a service to the terminal from the NF.

The base station controller 1020 may control the overall operation of the base station according to the embodiment proposed in the present invention. For example, the base station control unit may control the signal flow between blocks to perform an operation according to the above-described drawings and flowcharts. Specifically, the base station control unit may send and receive messages or signals with the terminal, the base station, and/or the network entity.

The storage unit 1030 may store at least one of information transmitted and received through the transceiver and information generated through the base station control unit.

11 is a diagram illustrating the structure of an NF (including an NF instance) according to an embodiment of the present invention. The NF shown in FIG. 11 may include at least any one of AMF, Master AMF, NSSF, and NRF described above, and is not limited to a specific NF.

Referring to FIG. 11 , the NF may include a transceiver 1110 , an NF control unit 1120 , and a storage unit 1130 .

The transceiver 1110 may transmit/receive a signal to/from another network entity. The transceiver may transmit system information to, for example, a base station (RAN), and may transmit a synchronization signal or a reference signal.

The NF control unit 1120 may control the overall operation of the NF according to the embodiment proposed in the present invention.

The storage unit 1130 may store at least one of information transmitted/received through the transceiver and information generated through the base station controller.

Methods according to the embodiments described in the claims or specifications of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.

When implemented in software, a computer-readable storage medium storing one or more programs (software modules) may be provided. One or more programs stored in the computer-readable storage medium are configured to be executable by one or more processors in an electronic device (device). One or more programs include instructions for causing an electronic device to execute methods according to embodiments described in a claim or specification of the present disclosure.

Such programs (software modules, software) include random access memory, non-volatile memory including flash memory, read only memory (ROM), electrically erasable programmable ROM (electrically erasable programmable read only memory, EEPROM), magnetic disc storage device, compact disc-ROM (CD-ROM), digital versatile discs (DVDs), or other It may be stored in an optical storage device or a magnetic cassette. Alternatively, it may be stored in a memory composed of a combination of some or all thereof. In addition, each configuration memory may be included in plurality.

In addition, the program is transmitted through a communication network consisting of a communication network such as the Internet, an intranet, a local area network (LAN), a wide area network (WAN), or a storage area network (SAN), or a combination thereof. It may be stored on an attachable storage device that can be accessed. Such a storage device may be connected to a device implementing an embodiment of the present disclosure through an external port. In addition, a separate storage device on the communication network may be connected to the device implementing the embodiment of the present disclosure.

In the specific embodiments of the present disclosure described above, components included in the disclosure are expressed in the singular or plural according to the specific embodiments presented. However, the singular or plural expression is appropriately selected for the context presented for convenience of description, and the present disclosure is not limited to the singular or plural element, and even if the element is expressed in plural, it is composed of the singular or singular. Even an expressed component may be composed of a plurality of components.

Meanwhile, although specific embodiments have been described in the detailed description of the present disclosure, various modifications are possible without departing from the scope of the present disclosure. Therefore, the scope of the present disclosure should not be limited to the described embodiments and should be defined by the claims described below as well as the claims and equivalents.

Claims (10)

A network management method of a first network function entity for managing a plurality of network function (NF) entities in a wireless communication system, the method comprising:
Receiving, from a base station, a first update request message including configuration change information of the base station;
determining whether to change a network configuration for selecting a network slice based on the first update request message;
transmitting a second update request message for servicing the network slice generated based on the first update request message to a second network function entity managing state information of a network;
receiving, from the second network function entity, a second update response message corresponding to the second update request message; and
and transmitting, to the base station, a first update response message generated based on the second update response message. According to claim 1,
The first update request message is
Characterized in that it includes at least one of a name of the base station, an identifier, tracking area (TA) information supported by the base station, and single-network slice selection assistance information (S-NSSAI) supported by the TA, the first A method for network management of a network functional entity. According to claim 1,
The second update request message is
and an identifier of the first network functional entity. According to claim 1,
the plurality of network function entities have the same network function set identifier;
and the first network functional entity is selected from the plurality of network functional entities. 5. The method of claim 4,
The second update request message is
and the network function set identifier. In a first network function entity for managing a plurality of network function (NF) entities in a wireless communication system,
a transceiver for transmitting and receiving a signal; and
Including a control unit connected to the transceiver,
The control unit is
Receives a first update request message including configuration change information of the base station from the base station, determines whether to change a network configuration for selecting a network slice based on the first update request message, and manages network state information transmits a second update request message for servicing the network slice generated based on the first update request message to a second network function entity that corresponds to the second update request message from the second network function entity A first network function entity, characterized by receiving a second update response message and transmitting a first update response message generated based on the second update response message to the base station. 7. The method of claim 6,
The first update request message is
Characterized in that it includes at least one of a name of the base station, an identifier, tracking area (TA) information supported by the base station, and single-network slice selection assistance information (S-NSSAI) supported by the TA, the first network function entity. 7. The method of claim 6,
The second update request message is
and an identifier of the first network functional entity. 7. The method of claim 6,
the plurality of network function entities have the same network function set identifier;
and the first network functional entity is selected from the plurality of network functional entities. 10. The method of claim 9,
The second update request message is
and the network function set identifier.

Images