Apparatus and method for supporting communication service continuity in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. A method of a terminal in a wireless communication system according to the present disclosure includes transmitting, by a base station, a first registration request message to an access and mobility management function (AMF), receiving, by the base station, a registration rejection message from the AMF as a response to the first registration request message, and transmitting, by the base station, a second registration request message to the AMF based on the registration rejection message.

Description

Technical Field

[0001] The present disclosure relates to wireless communication systems, and more particularly, to an apparatus and method for supporting communication service continuity. Background Art

[0002] The 5th generation (5G) mobile communication technology defines a wide frequency band so that high transmission rates and new services are possible, and can be realized not only in the "below 6 GHz" frequency band such as 3.5 GHz, but also in the "above 6 GHz" frequency band called millimeter wave including 28 GHz and 39 GHz. In addition, the implementation of the 6th generation (6G) mobile communication technology (called super 5G system) in the terahertz frequency band (for example, the 95 GHz to 3 THz frequency band) has been considered in order to achieve a transmission rate fifty times faster than that of the 5G mobile communication technology and an ultra-low latency of one tenth of that of the 5G mobile communication technology.

[0003] At the beginning of the development of 5G mobile communication technology, in order to support services and meet performance requirements related to enhanced mobile broadband (eMBB), ultra-reliable low latency communication (URLLC), and massive machine type communication (mMTC), there has been ongoing standardization on beamforming and massive multiple-input multiple-output (MIMO) for mitigating radio wave path loss in mmWave and increasing radio wave transmission distance, dynamic operation of parameter sets (e.g., operating multiple subcarrier spacings) and time slot formats to support efficient utilization of mmWave resources, initial access technology to support multi-beam transmission and broadband, definition and operation of bandwidth part (BWP), new channel coding methods such as low-density parity check (LDPC) codes for large-volume data transmission and polar codes for highly reliable transmission of control information, layer 2 (L2) pre-processing, and network slicing for providing dedicated networks tailored for specific services.

[0004] Currently, there are ongoing discussions on the improvement and performance enhancement of initial 5G mobile communication technologies in view of the services to be supported by 5G mobile communication technologies, and there has been physical layer standardization on technologies such as: vehicle-to-everything (V2X) for assisting driving decisions of autonomous vehicles based on information about the position and status of a vehicle transmitted by the vehicle and for enhancing user convenience, unlicensed new radio (NR-U) for system operation intended to comply with various regulatory-related requirements within unlicensed frequency bands, new radio user equipment (NR UE) energy saving, non-terrestrial network (NTN) as UE-satellite direct communication for providing coverage in areas where communication with terrestrial networks is not possible, and positioning.

[0005] In addition, in the air interface architecture / protocol, there is already ongoing standardization on technologies such as the Industrial Internet of Things (IIoT) that supports new services through interworking and integration with other industries, Integrated Access and Backhaul (IAB) that provides nodes for network service area expansion by supporting wireless backhaul links and access links in an integrated manner, mobility enhancements including conditional handover and dual active protocol stack (DAPS) handover, and two-step random access (two-step RACH for NR) for simplifying the random access procedure. In terms of system architecture / services, standardization is also ongoing on the following items: 5G baseline architecture (e.g., service-based architecture or service-based interface) for combining network function virtualization (NFV) and software defined network (SDN) technologies, and mobile edge computing (MEC) for receiving UE location-based services.

[0006] As 5G mobile communication systems are commercialized, the number of connected devices, which has been growing exponentially, will be connected to the communication network, and it is accordingly expected that enhanced functions and performance of the 5G mobile communication systems and integrated operations of the connected devices will be necessary. To this end, new research is scheduled on extended reality (XR) for effectively supporting augmented reality (AR), virtual reality (VR), mixed reality (MR), etc., 5G performance improvement and complexity reduction by utilizing artificial intelligence (AI) and machine learning (ML), AI service support, metaverse service support, and drone communication.

[0007] Furthermore, such development of 5G mobile communication systems will serve as the basis for developing not only new waveforms for providing terahertz band coverage for 6G mobile communication technology, multi-antenna transmission technologies such as full-dimensional MIMO (FD-MIMO), array antennas, and massive antennas, metamaterial-based lenses and antennas for improving terahertz band signal coverage, high-dimensional spatial multiplexing technology using orbital angular momentum (OAM), and reconfigurable smart surfaces (RIS), but also full-duplex technology for improving frequency efficiency of 6G mobile communication technology and improving system networks, AI-based communication technology for leveraging satellites and AI from the design stage to achieve system optimization and internalize end-to-end AI support functions, and next-generation distributed computing technology for implementing services at a complexity level that exceeds the limits of UE operating capabilities by utilizing ultra-high-performance communication and computing resources.

[0008] The above information is presented as background information only to assist with an understanding of the present disclosure. No determination has been made, and no assertion is made, as to whether any of the above might be applicable as prior art with respect to the present disclosure. Summary of the invention

[0009] Technical issues

[0010] The present disclosure relates to an apparatus and method for providing network slicing to a terminal moving in a wireless communication system.

[0011] Technical Solution

[0012] According to the present disclosure, an operation method of a terminal in a wireless communication system includes: sending a first registration request message to an access and mobility management function (AMF) through a base station, receiving a registration rejection message from the AMF through the base station as a response to the first registration request message, and based on the registration rejection message, sending a second registration request message to the AMF through the base station.

[0013] According to the present disclosure, a terminal in a wireless communication system includes a transceiver and a processor coupled to the transceiver. The processor is configured to send a first registration request message to an AMF through a base station, receive a registration rejection message from the AMF through the base station as a response to the first registration request message, and send a second registration request message to the AMF through the base station based on the registration rejection message.

[0014] The first registration request message may include an indication requesting authentication of a network slice of the terminal in the tracking area unit, an indication indicating that the terminal is capable of authenticating the network slice of the terminal in the tracking area unit, an indication indicating that the terminal is capable of receiving and using authentication information of the network slice of the terminal, and an indication indicating that the terminal is capable of performing communication using the authentication information.

[0015] The first registration request message may include information about the tracking area associated with the network slice for the service request desired by the terminal, and information about the network slice.

[0016] The registration reject message may include a list of tracking areas determined based on the first registration message, information about network slices available in the tracking areas, and at least one of authentication information for the network slices.

[0017] The registration rejection message may include a list of tracking areas determined based on the first registration message, information about network slices that are unavailable in the tracking area, authentication information for the network slices, and information about network slices that failed authentication in the tracking area.

[0018] The registration rejection message may include a list of tracking areas determined based on the first registration message, information about network slices that are unavailable in the tracking area, information about network slices that have been attempted to be authenticated but failed in the tracking area, and authentication information for the network slices.

[0019] The registration rejection message may be generated based on a first authentication response message sent from a session management function (SMF) to the AMF. The first authentication response message may include a tracking area list determined based on the first registration request message, information about network slices available in the tracking area, and authentication information about the network slices.

[0020] The first authentication response message may be generated based on a second authentication response message sent from an authentication, authorization, and accounting (AAA) to the SMF.

[0021] The second authentication response message may include an indication that the wireless communication system has the ability to support and configure the network slice in the tracking area unit determined based on the first registration request message, and an indication that establishment, management or authentication of the network slice in the tracking area unit is allowed.

[0022] The second authentication response message may be generated based on the authentication request message sent from the SMF to the AAA.

[0023] The authentication request message may include a tracking area code (TAC) and a granularity indication that instructs the terminal to use a network slice in a tracking area unit determined based on the first registration request message.

[0024] The authorization request message can be generated based on the network slice configuration information determined according to the first registration request message.

[0025] The network slice configuration information may include at least one of an indication of the granularity of mobility or authentication associated with a network slice for a terminal configured in a tracking area unit, and an indication of a mutual mapping relationship between information about the tracking area and authentication information about the tracking area.

[0026] Beneficial Effects

[0027] The present disclosure can effectively support network slicing and network slicing services for terminals moving in a wireless communication system. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] The above and other aspects, features and advantages of certain embodiments of the present disclosure will become more apparent through the following description in conjunction with the accompanying drawings, in which:

[0029] FIG. 1 illustrates a conceptual diagram of a terminal and a network environment for providing communication to a user equipment (UE) moving in a 5G network environment by considering slices according to an embodiment of the present disclosure;

[0030] FIG2 illustrates a flow chart of a process for providing communication to a UE moving in a 5G network environment by considering slices according to an embodiment of the present disclosure;

[0031] FIG3 illustrates a flowchart of a process for providing communication to a UE moving in a 5G network environment by considering slices according to another embodiment of the present disclosure;

[0032] FIG4 illustrates a flowchart of a process for providing communication to a UE moving in a 5G network environment by considering slices according to another embodiment of the present disclosure;

[0033] FIG5 illustrates a flowchart of a process for providing communication to a UE moving in a 5G network environment by considering slices according to another embodiment of the present disclosure;

[0034] FIG6 illustrates a flowchart of a process for providing communication to a UE moving in a 5G network environment by considering slices according to another embodiment of the present disclosure;

[0035] FIG7 shows a block diagram of a UE according to an embodiment of the present disclosure; and

[0036] FIG8 shows a block diagram of a network entity according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0037] Before proceeding to the following detailed description, it may be helpful to set forth definitions of certain words and phrases used throughout this patent document: the terms "include" and "comprising" and their derivatives mean including but not limited to; the term "or" is inclusive, meaning and / or; the phrases "associated with" and "associated with" and their derivatives may mean including, included within, interconnected with, containing, contained within, connected to or connected with, coupled to or coupled with, communicable with, cooperating with, interleaved, juxtaposed, proximate to, bound to or bound with, having, having the property of, etc.; and the term "controller" means any device, system, or portion thereof that controls at least one operation, such device may be implemented in hardware, firmware, or software, or some combination of at least two thereof. It should be noted that the functionality associated with any particular controller may be centralized or distributed, whether locally or remotely.

[0038] In addition, the various functions described below may be implemented or supported by one or more computer programs, each of which is formed by a computer-readable program code and embodied in a computer-readable medium. The terms "application" and "program" refer to one or more computer programs, software components, instruction sets, processes, functions, objects, classes, instances, related data, or a portion thereof, suitable for implementation in a suitable computer-readable program code. The phrase "computer-readable program code" includes any type of computer code, including source code, object code, and executable code. The phrase "computer-readable medium" includes any type of medium that can be accessed by a computer, such as a read-only memory (ROM), a random access memory (RAM), a hard drive, a compact disk (CD), a digital video disk (DVD), or any other type of memory. "Non-transitory" computer-readable media excludes wired, wireless, optical, or other communication links that transmit temporary electrical or other signals. Non-transitory computer-readable media include media in which data can be permanently stored and media in which data can be stored and later rewritten, such as rewritable optical disks or erasable memory devices.

[0039] Definitions for certain words and phrases are provided throughout this patent document, those of ordinary skill in the art should understand that in many, if not most instances, such definitions apply to prior, as well as future uses of such defined words and phrases.

[0040] FIG. 1 to FIG. 8 discussed below and the various embodiments used to describe the principles of the present disclosure in this patent document are illustrative only and should not be interpreted in any way as limiting the scope of the present disclosure. Those skilled in the art will appreciate that the principles of the present disclosure can be implemented in any suitably arranged system or device.

[0041] Hereinafter, embodiments are described in detail with reference to the accompanying drawings. In the accompanying drawings, the same reference numerals represent the same elements. Well-known functions or structures may not be described or shown in detail to avoid obscuring the subject matter of the present disclosure.

[0042] In the accompanying drawings, some components may be exaggerated, omitted or schematically shown. In addition, the size of each component does not fully reflect the actual size. In the accompanying drawings, the same or corresponding components may be provided with the same or similar reference numerals.

[0043] By referring to the embodiments described below in conjunction with the accompanying drawings, various advantages and features of the present disclosure and the modes for achieving them will be apparent. However, the present disclosure is not limited to the embodiments set forth below, but can be implemented in various different forms. The following embodiments are provided only to inform those skilled in the art of the scope of the present disclosure, and the present disclosure is limited by the appended claims.

[0044] Each block of the flowchart and the combination of blocks in the flowchart can be implemented by computer program instructions, which can be installed on a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that the instructions executed by the processor of the computer or other programmable data processing device create a device for performing the functions specified in the flowchart block. These computer program instructions can also be stored in a computer-usable or computer-readable memory, which can instruct the computer or other programmable data processing device to act in a specific manner, so that the instructions stored in the computer-usable or computer-readable memory produce an article of manufacture including an instruction device that implements the functions specified in the flowchart. The computer program instructions can also be loaded on a computer or other programmable data processing device so that a series of operating steps are performed on the computer or other programmable device to produce a computer-implemented process, so that the instructions of the executing computer or other programmable device provide steps for performing the functions described in the flowchart.

[0045] In addition, each box can represent a module, segment or part of a code, which includes one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative embodiments, the functions marked in the box may not occur in order. For example, two boxes shown in succession can actually be executed substantially simultaneously, or these boxes can sometimes be executed in reverse order, depending on the functions involved.

[0046] The term unit represents a software or hardware component, such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC), and the unit performs a specific task. However, the unit does not always have a meaning limited to software or hardware. The unit can be advantageously configured to reside on an addressable storage medium and to operate on one or more processors. Therefore, a unit can include, for example, components (such as software components, object-oriented software components, class components, and task components), processes, functions, attributes, procedures, subroutines, program code segments, drivers, firmware, microcodes, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided in components and units can be combined into fewer components and units, or can be further separated into additional components and units.

[0047] In addition, the components and units may be implemented to operate on one or more central processing units (CPUs) within the device or secure multimedia card. In the following, a base station is a subject that allocates resources to a terminal and may be at least one of an eNode B (eNB), a Node B (NB), a base station (BS), a radio access network (RAN), an access network (AN), a RAN node, a new radio (NR) NB, a gNB, a wireless access unit, a base station controller, and a node in a network. In addition, a base station may be a network entity including at least one of an integrated access and backhaul donor (backhaul-donor, IAB donor) and an IAB node, the IAB donor being a gNB that provides network access to a user equipment (UE) through a network of backhaul and access links in an NR system, and the IAB node being a RAN node that supports an NR backhaul link to an IAB donor or another IAB node and supports an NR access link to a UE. The UE is wirelessly connected through the IAB node and may send / receive data to and from the IAB donor connected to at least one IAB node through a backhaul link. The UE may include a terminal, a mobile station (MS), a cellular phone, a smart phone, a computer, or a multimedia system capable of performing a communication function.

[0048] In the present disclosure, downlink (DL) means a radio transmission path of a signal sent from a BS to a UE, and uplink (UL) means a radio transmission path of a signal sent from a UE to a BS. In addition, although a system based on LTE or LTE-A is described in conjunction with the embodiments, as an example, the embodiments may also be applied to other communication systems with similar technical backgrounds or channel forms. In addition, the embodiments may be modified within the scope of the present disclosure without significantly departing from the scope of the present disclosure as determined by a person of ordinary skill in the art, and such modifications may be applicable to other communication systems.

[0049] The description of the embodiments of the present disclosure is mainly based on a new radio access network (new RAN) and a packet core (fifth generation (5G) system, 5G core network or next generation (NG) core), which is a core network on the 5G mobile communication standard specified by the Third Generation Partnership Project (3GPP) as a mobile communication standardization group, but the main subject matter of the present disclosure can be applied to other communication systems with similar technical backgrounds by slight modifications without departing from the scope of the present disclosure, which can be determined by those skilled in the art.

[0050] FIG. 1 shows a conceptual diagram of a UE 101 and a network environment for performing communication with improved communication performance in a 5G network according to an embodiment of the present disclosure.

[0051] 1 , a 5G network or NR core network may include network functions (NFs) such as a user plane function (UPF) 131, a session management function (SMF) 121, an access and mobility management function (AMF) 111, a 5G radio access network (RAN) 103, a user data management (UDM) 151, and a policy control function (PCF) 161. In addition, the 5G network or NR core network may also include entities such as an authentication server function (AUSF) 141, and an authentication, authorization, and accounting (AAA) 181 to authenticate the above entities. UE (or terminal) 101 may be connected to the 5G network or NR core network through a BS (or 5G RAN) 103. The 5G network or NR core network may also include an N3 interworking function (N3IWF) for UE 101 to communicate via non-3GPP access. For example, when UE 101 performs communication via non-3GPP access, session management may be controlled by UE 101, non-3GPP access, N3IWF, and SMF 121. For example, mobility management may be controlled by UE 101, non-3GPP access, N3IWF, and AMF 111.

[0052] In a 5G or NR system, AMF 111 may perform mobility management. SMF 121 may perform session management. On the other hand, a 5G or NR system may include an independent deployment architecture in which only a 5G or NR entity is used to perform communication, and a non-independent deployment architecture in which both a 4G entity and a 5G or NR entity are used to perform communication.

[0053] For example, when UE 101 performs communication with the network, deployment of a 5G entity using a core network while control is performed by the eNB is possible. For example, mobility management between UE 101 and AMF 111 and session management between UE 101 and SMF 121 may be performed on the non-access stratum (NAS) layer of layer 3.

[0054] According to the present disclosure, the communication network assumes 5G, 4G LTE networks, but is not limited thereto, and the present disclosure can be applied when the same concept is applied to other networks or systems within the scope understood by those skilled in the art.

[0055] When managing the mobility of UE 101 in the 5G network, multiple cells may be managed as one tracking area, and multiple tracking areas may be managed as one registration area, so as to reduce the frequent occurrence of signal and message communications due to the movement of UE 101. For example, in the 5G network, network slices may be managed in registration area units, and in the case where network slices are not allowed in smaller units of tracking areas configuring the registration area, UE 101 cannot receive services related to the network slices in the corresponding registration area.

[0056] The present disclosure relates to a method and apparatus for supporting a network slicing service in a case where there is at least one tracking area supporting a service for network slicing in a wireless communication system. The present disclosure can solve the problem that a network slice or a network slice-related service cannot be provided due to determination that even when one tracking area in a plurality of tracking areas does not support a service for network slicing and a service related to network slicing is unavailable in the entire registration area.

[0057] For example, in the case where there is at least one tracking area supporting services for network slicing when UE 101 moves, the present disclosure can provide network slicing services in the tracking area.

[0058] FIG2 shows a flowchart of a process for providing communication to a UE 101 moving in a 5G network environment by considering network slicing according to an embodiment of the present disclosure.

[0059] 2 , in operation 211, UE 101 may send a registration request message to AMF 111. For example, the registration request message may include at least one of the following information.

[0060] 1) An indication (or information) for requesting the network to allow mobility tracking of UE 101 in a tracking area unit, to register the location of UE 101, and to allow UE 101 to use and authenticate a network slice.

[0061] 2) An indication for notifying the network that UE 101 has the capability to use and authenticate slices in the tracking area unit. The information includes information such as a bit or an indication that notifies UE 101 that it has the capability to receive authentication of network slices in the tracking area unit or to perform communication using corresponding authentication information.

[0062] 3) Network slice information (e.g., Network Slice Selection Assistance Information (NSSAI)) used by UE 101 to request services in tracking area units. NSSAI may include (a) a slice / service type (SST) requested by the user terminal or (b) a slice differentiator (SD) corresponding to the user terminal and the slice / service type. For example, network slice #1 (NSSAI #1), network slice #2 (NSSAI #2), etc.

[0063] 4) UE 101 desires to request tracking area information, such as a tracking area code (TAC), for services related to the slice. For example, when requesting to use and authenticate a network slice in a tracking area unit from network slice #1, UE 101 may send the TAC information to the network (e.g., AMF 111).

[0064] In operation 213, AMF 111 may configure the granularity of mobility or authentication associated with the network slice to be used by UE 101 in the tracking area unit based on the registration request message received from UE 101.

[0065] For example, in an embodiment (Case 1), AMF 111 may configure the network slice to be used by UE 101 and the granularity of mobility or authentication associated with the slice in a tracking area unit, and may store a mapping relationship between information about the tracking area and authentication information about the tracking area. The information about the tracking area may include a TAC. For example, AMF 111 may map NSSAI#1, which is network slice information, to TAC#1, which is tracking area information, and map NSSAI#2, NSSAI#3, etc. to TAC#2, and may also store information about whether UE 101 is allowed to use the corresponding network slice (network slice identified by NSSAI) in each TAC.

[0066] In another embodiment (Case 2), the AMF 111 may configure the granularity of mobility and authentication associated with the network slice to be used by the UE 101 in registration area units.

[0067] The AMF 111 may send at least one of an indication for notifying the UE 101 that the UE 101 will use the mobility granularity of the network slice in the tracking area unit, an indication (or bit or information) indicating that the UE 101 is using the network slice in the tracking area unit, and information related to the TAC to the SMF 121 or to the AAA 181 via the SMF. For example, at least one of the SMF 121 and the AAA 181 may receive from the AMF 111 an indication for notifying the UE 101 that the UE 101 will use the mobility granularity of the network slice in the tracking area unit, an indication (or bit or information) indicating that the UE 101 is using the network slice in the tracking area unit, or information related to the TAC.

[0068] In operation 215, UE 101 may send a PDU session establishment request message to SMF 121. SMF 121 may receive the PDU session establishment request message from UE 101.

[0069] In operation 217, the SMF 121 may send a PDU session establishment response message to the UE 101 as a response to the PDU session establishment request message. The UE 101 may receive the PDU session establishment response message from the SMF 121.

[0070] In operation 221:

[0071] Example 1)

[0072] This embodiment includes the case where SMF 121 has configured the granularity of network slice related authentication, mobility and sessions as tracking areas (Embodiment 1-A) or registration areas (Embodiment 1-B).

[0073] (Example 1-A-1)

[0074] For example, SMF 121 may configure the granularity of authentication, mobility, or sessions related to the network slice to be used by UE 101 in tracking area units.

[0075] (Example 1-A-2)

[0076] For example, the SMF 121 may configure the granularity of authentication, mobility, or session associated with a network slice used by the UE 101 in tracking area units, and may store information about the tracking area and authentication information about the tracking area. The information about the tracking area may include a TAC. For example, the SMF 121 may map NSSAI#1 to TAC#1, TAC#2, etc., and store them together to identify which network slice (e.g., NSSAI#1) is provided from which tracking area (e.g., TAC#1, TAC#2, etc.).

[0077] (Example 1-B)

[0078] For example, SMF 121 may configure the granularity of authentication, mobility, or sessions associated with a network slice used by UE 101 in registration area units.

[0079] Example 2)

[0080] This embodiment may correspond to a situation where AMF 111 configures or configures and stores the granularity of authentication, mobility or session associated with a network slice as a tracking area or a registration area, and SMF 121 also configures the granularity of authentication, mobility or session associated with the network slice as a tracking area or a registration area based on the configuration information configured by AMF 111.

[0081] (Example 2-A-1)

[0082] For example, in a case where AMF 111 configures the granularity of at least one of mobility and authentication associated with a network slice used by UE 101 in a tracking area unit, SMF 121 may configure the granularity of sessions or authentication associated with the network slice used by UE 101 in the tracking area unit based on the configuration information configured by AMF 111.

[0083] (Example 2-A-2)

[0084] For example, in a case where the AMF 111 configures the granularity of mobility or authentication associated with a network slice used by the UE 101 in a tracking area unit, and stores and manages a mutual mapping relationship between information about the tracking area and authentication information about the tracking area, the SMF 121 may configure the granularity of authentication or session associated with the network slice used by the UE 101 in a tracking area unit based on the information configured and stored by the AMF. The information about the tracking area may include a TAC.

[0085] (Example 2-B)

[0086] For example, in a case where AMF 111 configures the granularity of mobility or authentication associated with a network slice used by UE 101 in a registration area unit, SMF 121 may configure the granularity of sessions or authentication associated with a network slice used by UE 101 in a registration area unit by considering the configuration of AMF 111.

[0087] In operation 223, the SMF 121 may send an authentication request message to the AAA 181. The AAA 181 may receive the authentication request message from the SMF 121.

[0088] For example, the authentication request message may include an indication of the granularity of network slices to be used in the tracking area unit (e.g., T if managed in the tracking area unit, R if managed in the registration area unit, etc.) to notify UE 101, an indication of network slices being used in the tracking area unit (e.g., configuring the corresponding bit to 1 to indicate that the network slices are managed in the tracking area unit), and at least one of the associated tracking area information (e.g., TAC#1, TAC#2, TAC#3, etc.).

[0089] In operation 225, AAA 181 may configure the granularity of the network slice used by UE 101 in the tracking area unit. For example, AAA 181 may map the TAC and information about the network slice used by UE 101, or may bind, map, or store information about the network slice used by UE 101, network slice authentication information, TAC, or location information of UE 101.

[0090] In operation 227, AAA 181 may send an authentication response message to SMF 121 as a response to the authentication request message. The authentication response message may include an indication notifying that the network accessed by UE 101 has the capability to configure support network slicing in the tracking area unit. The authentication response message may include an indication notifying that establishment, management, or authentication of network slicing is allowed in the tracking area unit, or an indication (bit) for allowing the indication.

[0091] In operation 231, SMF 121 may send an authentication response message to AMF 111.

[0092] For example, the authentication response message may include at least one of a tracking area list, information about network slices available in the tracking area, and authentication information about whether the network slice is available in the tracking area.

[0093] In operation 241, AMF 111 may send an authentication request message to UE 101.

[0094] For example, the authentication request message may include at least one of a list of tracking areas, information about network slices available in the tracking area, and authentication information about whether the network slice is available in the tracking area.

[0095] In operation 251, UE 101 may store at least one of a tracking area list included in the authentication request message, information about network slices available in the tracking area, and authentication information about the network slice.

[0096] The stored information may include a list of TACs associated with available network slices. For example, the stored information may include a list of available TACs that are certified or capable of providing network slice services, network slices, and information about the network slice certification of each TAC.

[0097] UE 101 may attempt to access the network based on the stored information during registration. For example, UE 101 may attempt to establish and modify a PDU session based on the stored information.

[0098] For example, UE 101 may generate and transmit a mobility management message of the UE, such as a service request or registration request message for mobility or session management of UE 101, or a session management message of the UE, such as a PDU session establishment request message or a PDU session modification request, by using / including the stored tracking area list, information about the network slices available in the tracking area, and authentication information for the network slices.

[0099] For example, UE 101 can identify a network slice that is authenticated and allowed to access in units of TAC based on the stored information in order to attempt to access, or can send at least one of a registration request message, a service request message, a PDU session establishment request message, and a PDU session modification request message to a network or network slice that can provide network slice authentication in units of TAC.

[0100] FIG3 shows a flowchart of a process for providing communication to a UE 101 moving in a 5G network environment by considering network slicing according to an embodiment of the present disclosure.

[0101] 3 , in operation 311, UE 101 may send a registration request message to AMF 111. For example, the registration request message may include at least one of the following information.

[0102] 1) An indication (or information) for requesting the network to allow mobility tracking of UE 101 in a tracking area unit, to register the location of UE 101, and to allow UE 101 to use and authenticate a network slice.

[0103] 2) An indication for notifying the network that UE 101 has the capability to use and authenticate slices in the tracking area unit. The information includes information such as a bit or an indication that notifies UE 101 that it has the capability to receive authentication of network slices in the tracking area unit or to perform communication using corresponding authentication information.

[0104] 3) Network slice information (e.g., Network Slice Selection Assistance Information (NSSAI)) used by UE 101 to request services in tracking area units: NSSAI may include (a) a slice / service type (SST) requested by the user terminal or (b) a slice differentiator (SD) corresponding to the user terminal and the slice / service type. For example, network slice #1 (NSSAI #1), network slice #2 (NSSAI #2), etc.

[0105] 4) UE 101 desires to request tracking area information, such as a tracking area code (TAC), for services related to the slice. For example, when requesting to use and authenticate a network slice in a tracking area unit from network slice #1, UE 101 may send the TAC information to the network (e.g., AMF 111).

[0106] In operation 313, AMF 111 may configure the granularity of mobility or authentication associated with the network slice to be used by UE 101 in the tracking area unit based on the registration request message received from UE 101.

[0107] For example, in an embodiment (Case 1), AMF 111 may configure the network slice to be used by UE 101 and the granularity of mobility or authentication associated with the slice in a tracking area unit, and may store a mapping relationship between information about the tracking area and authentication information about the tracking area. The information about the tracking area may include a TAC. For example, AMF 111 may map NSSAI#1, which is network slice information, to TAC#1, which is tracking area information, and map NSSAI#2, NSSAI#3, etc. to TAC#2, and may also store information about whether UE 101 is allowed to use the corresponding network slice (network slice identified by NSSAI) in each TAC.

[0108] In another embodiment (Case 2), the AMF 111 may configure the granularity of mobility and authentication associated with the network slice to be used by the UE 101 in registration area units.

[0109] The AMF 111 may send at least one of an indication for notifying the UE 101 that the UE 101 will use the mobility granularity of the network slice in the tracking area unit, an indication (or bit or information) indicating that the UE 101 is using the network slice in the tracking area unit, and information related to the TAC to the SMF 121 or to the AAA 181 via the SMF. For example, at least one of the SMF 121 and the AAA 181 may receive from the AMF 111 an indication for notifying the UE 101 that the UE 101 will use the mobility granularity of the network slice in the tracking area unit, an indication (or bit or information) indicating that the UE 101 is using the network slice in the tracking area unit, or information related to the TAC.

[0110] In operation 315, UE 101 may send a PDU session establishment request message to SMF 121. SMF 121 may receive the PDU session establishment request message from UE 101.

[0111] In operation 317, the SMF 121 may send a PDU session establishment response message to the UE 101 as a response to the PDU session establishment request message. The UE 101 may receive the PDU session establishment response message from the SMF 121.

[0112] In operation 321:

[0113] Example 1)

[0114] This embodiment includes the case where the SMF has configured the granularity of network slice-related authentication, mobility and sessions as a tracking area (Embodiment 1-A) or a registration area (Embodiment 1-B).

[0115] (Example 1-A-1)

[0116] For example, SMF 121 may configure the granularity of authentication, mobility, or sessions related to the network slice to be used by UE 101 in tracking area units.

[0117] (Example 1-A-2)

[0118] For example, the SMF 121 may configure the granularity of authentication, mobility, or session associated with a network slice used by the UE 101 in tracking area units, and may store information about the tracking area and authentication information about the tracking area. The information about the tracking area may include a TAC. For example, the SMF 121 may map NSSAI#1 to TAC#1, TAC#2, etc., and store them together to identify which network slice (e.g., NSSAI#1) is provided from which tracking area (e.g., TAC#1, TAC#2, etc.).

[0119] (Example 1-B)

[0120] For example, SMF 121 may configure the granularity of authentication, mobility, or sessions associated with a network slice used by UE 101 in registration area units.

[0121] Example 2)

[0122] This embodiment includes a situation where AMF 111 configures or configures and stores the granularity of authentication, mobility, or sessions associated with a network slice in units of tracking areas or registration areas, and SMF 121 also configures the granularity of authentication, mobility, or sessions associated with the network slice as tracking areas or registration areas based on the configuration information configured by AMF 111.

[0123] (Example 2-A-1)

[0124] For example, in a case where AMF 111 configures the granularity of at least one of mobility and authentication associated with a network slice used by UE 101 in a tracking area unit, SMF 121 may configure the granularity of sessions or authentication associated with the network slice used by UE 101 in the tracking area unit based on the configuration information configured by AMF 111.

[0125] (Example 2-A-2)

[0126] For example, in a case where the AMF 111 configures the granularity of mobility or authentication associated with a network slice used by the UE 101 in a tracking area unit, and stores and manages a mutual mapping relationship between information about the tracking area and authentication information about the tracking area, the SMF 121 may configure the granularity of authentication or session associated with the network slice used by the UE 101 in a tracking area unit based on the information configured and stored by the AMF. The information about the tracking area may include a TAC.

[0127] (Example 2-B)

[0128] For example, in a case where AMF 111 configures the granularity of mobility or authentication associated with a network slice used by UE 101 in a registration area unit, SMF 121 may configure the granularity of sessions or authentication associated with a network slice used by UE 101 in a registration area unit by considering the configuration of AMF 111.

[0129] In operation 323, the SMF 121 may send an authentication request message to the AAA 181. The AAA 181 may receive the authentication request message from the SMF 121.

[0130] For example, the authentication request message may include an indication of the granularity of network slices to be used in the tracking area unit (e.g., T if managed in the tracking area unit, R if managed in the registration area unit, etc.) to notify UE 101, an indication of network slices being used in the tracking area unit (e.g., configuring the corresponding bit to 1 to indicate that the network slices are managed in the tracking area unit), and at least one of the associated tracking area information (e.g., TAC#1, TAC#2, TAC#3, etc.).

[0131] In operation 325, AAA 181 may configure the granularity of the network slice used by UE 101 in the tracking area unit. For example, AAA 181 may map the TAC and information about the network slice used by UE 101, or may bind, map, or store information about the network slice used by UE 101, network slice authentication information, TAC, or location information of UE 101.

[0132] At operation 327, AAA 181 may send an authentication response message to SMF 121 as a response to the authentication request message. The authentication response message may include an indication notifying that the network accessed by UE 101 has the capability to configure support for network slicing in the tracking area unit. The authentication response message may include an indication notifying that establishment, management, or authentication of network slicing is allowed in the tracking area unit, or an indication (bit) for allowing the indication.

[0133] In operation 331, SMF 121 may send a configuration trigger message to AMF 111 to trigger configuration settings.

[0134] For example, a configuration trigger message that triggers a configuration setting may include a list of tracking areas, information about network slices available in the tracking areas, and at least one of authentication information about whether the network slice is available in the tracking areas.

[0135] In operation 341, AMF 111 may send a configuration command message to UE 101.

[0136] For example, the configuration command message may include a list of tracking areas, information about network slices available in the tracking area, and at least one of authentication information about whether the network slice is available in the tracking area.

[0137] In operation 351, UE 101 may store at least one of a tracking area list included in the authentication request message, information about network slices available in the tracking area, and authentication information about the network slice.

[0138] The stored information may include a list of TACs associated with available network slices. For example, the stored information may include a list of available TACs that are certified or capable of providing network slice services, network slices, and information about the network slice certification of each TAC.

[0139] UE 101 may attempt to access the network based on the stored information during registration. For example, UE 101 may attempt to establish and modify a PDU session based on the stored information.

[0140] For example, UE 101 may generate and transmit a mobility management message of the UE, such as a service request or registration request message for mobility or session management of UE 101, or a session management message of the UE, such as a PDU session establishment request message or a PDU session modification request, by using / including the stored tracking area list, information about the network slices available in the tracking area, and authentication information for the network slices.

[0141] For example, UE 101 can identify the network slice that is authenticated and allowed to access in units of TAC based on the stored information in order to attempt to access, or can send at least one of a registration request message, a service request message, a PDU session establishment request message, and a PDU session modification request message to a network or network slice that can provide network slice authentication in units of TAC.

[0142] FIG4 shows a flowchart of a process for providing communication to a UE 101 moving in a 5G network environment by considering network slicing according to an embodiment of the present disclosure.

[0143] 4 , in operation 411, UE 101 may send a registration request message to AMF 111. For example, the registration request message may include at least one of the following information.

[0144] 1) An indication (or information) for requesting the network to allow mobility tracking of UE 101 in a tracking area unit, to register the location of UE 101, and to allow UE 101 to use and authenticate a network slice.

[0145] 2) An indication for notifying the network that UE 101 has the capability to use and authenticate slices in the tracking area unit. The information includes information such as a bit or an indication that notifies UE 101 that it has the capability to receive authentication of network slices in the tracking area unit or to perform communication using corresponding authentication information.

[0146] 3) Network slice information (e.g., Network Slice Selection Assistance Information (NSSAI)) used by UE 101 to request services in tracking area units. NSSAI may include (a) a slice / service type (SST) requested by the user terminal or (b) a slice differentiator (SD) corresponding to the user terminal and the slice / service type. For example, network slice #1 (NSSAI #1), network slice #2 (NSSAI #2), etc.

[0147] 4) UE 101 desires to request tracking area information, such as a tracking area code (TAC), for services related to the slice. For example, when requesting to use and authenticate a network slice in a tracking area unit from network slice #1, UE 101 may send the TAC information to the network (e.g., AMF 111).

[0148] In operation 413, AMF 111 may configure the granularity of mobility or authentication associated with the network slice to be used by UE 101 in the tracking area unit based on the registration request message received from UE 101.

[0149] For example, in an embodiment (Case 1), AMF 111 may configure the network slice to be used by UE 101 and the granularity of mobility or authentication associated with the slice in a tracking area unit, and may store a mapping relationship between information about the tracking area and authentication information about the tracking area. The information about the tracking area may include a TAC. For example, AMF 111 may map NSSAI#1, which is network slice information, to TAC#1, which is tracking area information, and map NSSAI#2, NSSAI#3, etc. to TAC#2, and may also store information about whether UE 101 is allowed to use the corresponding network slice (network slice identified by NSSAI) in each TAC.

[0150] In another embodiment (Case 2), the AMF 111 may configure the granularity of mobility and authentication associated with the network slice to be used by the UE 101 in registration area units.

[0151] The AMF 111 may send at least one of an indication for notifying the UE 101 that the UE 101 will use the mobility granularity of the network slice in the tracking area unit, an indication (or bit or information) indicating that the UE 101 is using the network slice in the tracking area unit, and information related to the TAC to the SMF 121 or to the AAA 181 via the SMF. For example, at least one of the SMF 121 and the AAA 181 may receive from the AMF 111 an indication for notifying the UE 101 that the UE 101 will use the mobility granularity of the network slice in the tracking area unit, an indication (or bit or information) indicating that the UE 101 is using the network slice in the tracking area unit, or information related to the TAC.

[0152] In operation 415, UE 101 may send a PDU session establishment request message to SMF 121. SMF 121 may receive the PDU session establishment request message from UE 101.

[0153] In another embodiment, a PDU session establishment request message may be sent from UE 101 to SMF 121 in operation 431.

[0154] For example, the PDU session establishment request message may include the following information.

[0155] 1) An indication (or information) for requesting the network to allow mobility tracking of UE 101 in a tracking area unit, to register the location of UE 101, and to allow UE 101 to use and authenticate a network slice.

[0156] 2) An indication for notifying the network that the UE 101 has the capability to use and authenticate the slice in the tracking area unit. The information includes information such as a bit or an indication that notifies the UE 101 that it has the capability to receive authentication of the network slice in the tracking area unit or to perform communication using the corresponding authentication information.

[0157] 3) Network slice information (e.g., Network Slice Selection Assistance Information (NSSAI)) used by UE 101 to request services in tracking area units. NSSAI may include (a) a slice / service type (SST) requested by the user terminal or (b) a slice differentiator (SD) corresponding to the user terminal and the slice / service type. Examples: Network Slice #1 (NSSAI #1), Network Slice #2 (NSSAI #2), etc.

[0158] 4) UE 101 desires to request tracking area information, such as a tracking area code (TAC), for services related to the slice. For example, when requesting to use and authenticate a network slice in a tracking area unit from network slice #1, UE 101 may send the TAC information to the network (e.g., AMF 111).

[0159] In operation 417, the SMF 121 may send a PDU session establishment response message to the UE 101 as a response to the PDU session establishment request message. The UE 101 may receive the PDU session establishment response message from the SMF 121.

[0160] In operation 421:

[0161] Example 1)

[0162] This embodiment includes the case where SMF 121 has configured the granularity of network slice related authentication, mobility and sessions as tracking areas (Embodiment 1-A) or registration areas (Embodiment 1-B).

[0163] (Example 1-A-1)

[0164] For example, SMF 121 may configure the granularity of authentication, mobility, or sessions related to the network slice to be used by UE 101 in tracking area units.

[0165] (Example 1-A-2)

[0166] For example, the SMF 121 may configure the granularity of authentication, mobility, or session associated with a network slice used by the UE 101 in tracking area units, and may store information about the tracking area and authentication information about the tracking area. The information about the tracking area may include a TAC. For example, the SMF 121 may map NSSAI#1 to TAC#1, TAC#2, etc., and store them together to identify which network slice (e.g., NSSAI#1) is provided from which tracking area (e.g., TAC#1, TAC#2, etc.).

[0167] (Example 1-B)

[0168] For example, SMF 121 may configure the granularity of authentication, mobility, or sessions associated with a network slice used by UE 101 in registration area units.

[0169] Example 2)

[0170] This embodiment includes a situation where AMF 111 configures or configures and stores the granularity of authentication, mobility, or sessions associated with a network slice in units of tracking areas or registration areas, and SMF 121 also configures the granularity of authentication, mobility, or sessions associated with the network slice as tracking areas or registration areas based on the configuration information configured by AMF 111.

[0171] (Example 2-A-1)

[0172] For example, in a case where AMF 111 configures the granularity of at least one of mobility and authentication associated with a network slice used by UE 101 in a tracking area unit, SMF 121 may configure the granularity of sessions or authentication associated with the network slice used by UE 101 in the tracking area unit based on the configuration information configured by AMF 111.

[0173] (Example 2-A-2)

[0174] For example, in a case where the AMF 111 configures the granularity of mobility or authentication associated with a network slice used by the UE 101 in a tracking area unit, and stores and manages a mutual mapping relationship between information about the tracking area and authentication information about the tracking area, the SMF 121 may configure the granularity of authentication or session associated with the network slice used by the UE 101 in a tracking area unit based on the information configured and stored by the AMF. The information about the tracking area may include a TAC.

[0175] (Example 2-B)

[0176] For example, in a case where AMF 111 configures the granularity of mobility or authentication associated with a network slice used by UE 101 in a registration area unit, SMF 121 may configure the granularity of sessions or authentication associated with a network slice used by UE 101 in a registration area unit by considering the configuration of AMF 111.

[0177] In operation 423, the SMF 121 may send an authentication request message to the AAA 181. The AAA 181 may receive the authentication request message from the SMF 121.

[0178] For example, the authentication request message may include an indication of the granularity of network slices to be used in the tracking area unit (e.g., T if managed in the tracking area unit, R if managed in the registration area unit, etc.) to notify UE 101, an indication of network slices being used in the tracking area unit (e.g., configuring the corresponding bit to 1 to indicate that the network slices are managed in the tracking area unit), and at least one of the associated tracking area information (e.g., TAC#1, TAC#2, TAC#3, etc.).

[0179] In operation 425, AAA 181 may configure the granularity of the network slice used by UE 101 in the tracking area unit. For example, AAA 181 may map the TAC and information about the network slice used by UE 101, or may bind, map, or store information about the network slice used by UE 101, network slice authentication information, TAC, or location information of UE 101.

[0180] In operation 427, AAA 181 may send an authentication response message to SMF 121 as a response to the authentication request message. The authentication response message may include an indication notifying that the network accessed by UE 101 has the capability to configure support for network slicing in the tracking area unit. The authentication response message may include an indication notifying that establishment, management, or authentication of network slicing is allowed in the tracking area unit, or an indication (bit) for allowing the indication.

[0181] In operation 433, SMF 121 may send a PDU session establishment accept message to UE 101.

[0182] For example, the PDU session establishment accept message may include a tracking area list, information about network slices available in the tracking area, and at least one of authentication information about whether the network slice is available in the tracking area.

[0183] In operation 451, UE 101 may store at least one of a tracking area list included in the PDU session establishment accept, information about network slices available in the tracking area, and authentication information about the network slice.

[0184] The stored information may include a list of TACs associated with available network slices. For example, the stored information may include a list of available TACs that are certified or capable of providing network slice services, network slices, and information about the network slice certification of each TAC.

[0185] UE 101 may attempt to access the network based on the stored information during registration. For example, UE 101 may attempt to establish and modify a PDU session based on the stored information.

[0186] For example, UE 101 may generate and transmit a mobility management message of the UE, such as a service request or registration request message for mobility or session management of UE 101, or a session management message of the UE, such as a PDU session establishment request message or a PDU session modification request, by using / including the stored tracking area list, information about the network slices available in the tracking area, and authentication information for the network slices.

[0187] For example, UE 101 can identify the network slice that is authenticated and allowed to access in units of TAC based on the stored information in order to attempt to access, or can send at least one of a registration request message, a service request message, a PDU session establishment request message, and a PDU session modification request message to a network or network slice that can provide network slice authentication in units of TAC.

[0188] FIG5 shows a flowchart of a process for providing communication to a UE 101 moving in a 5G network environment by considering network slicing according to an embodiment of the present disclosure.

[0189] 5 , in operation 511, UE 101 may send a registration request message to AMF 111. For example, the registration request message may include at least one of the following information.

[0190] 1) An indication (or information) for requesting the network to allow mobility tracking of UE 101 in a tracking area unit, to register the location of UE 101, and to allow UE 101 to use and authenticate a network slice.

[0191] 2) An indication for notifying the network that UE 101 has the capability to use and authenticate slices in the tracking area unit. The information includes information such as a bit or an indication that notifies UE 101 that it has the capability to receive authentication of network slices in the tracking area unit or to perform communication using corresponding authentication information.

[0192] 3) Network slice information (e.g., Network Slice Selection Assistance Information (NSSAI)) used by UE 101 to request services in tracking area units. NSSAI may include (a) a slice / service type (SST) requested by the user terminal or (b) a slice differentiator (SD) corresponding to the user terminal and the slice / service type. For example, network slice #1 (NSSAI #1), network slice #2 (NSSAI #2), etc.

[0193] 4) UE 101 desires to request tracking area information, such as a tracking area code (TAC), for services related to the slice. For example, when requesting to use and authenticate a network slice in a tracking area unit from network slice #1, UE 101 may send the TAC information to the network (e.g., AMF 111).

[0194] In operation 513, AMF 111 may configure the granularity of mobility or authentication associated with the network slice to be used by UE 101 in the tracking area unit based on the registration request message received from UE 101.

[0195] For example, in an embodiment (Case 1), AMF 111 may configure the network slice to be used by UE 101 and the granularity of mobility or authentication associated with the slice in a tracking area unit, and may store a mapping relationship between information about the tracking area and authentication information about the tracking area. The information about the tracking area may include a TAC. For example, AMF 111 may map NSSAI#1, which is network slice information, to TAC#1, which is tracking area information, and map NSSAI#2, NSSAI#3, etc. to TAC#2, and may also store information about whether UE 101 is allowed to use the corresponding network slice (network slice identified by NSSAI) in each TAC.

[0196] In another embodiment (Case 2), the AMF 111 may configure the granularity of mobility and authentication associated with the network slice to be used by the UE 101 in registration area units.

[0197] The AMF 111 may send at least one of an indication for notifying the UE 101 that the UE 101 will use the mobility granularity of the network slice in the tracking area unit, an indication (or bit or information) indicating that the UE 101 is using the network slice in the tracking area unit, and information related to the TAC to the SMF 121 or to the AAA 181 via the SMF. For example, at least one of the SMF 121 and the AAA 181 may receive from the AMF 111 an indication for notifying the UE 101 that the UE 101 will use the mobility granularity of the network slice in the tracking area unit, an indication (or bit or information) indicating that the UE 101 is using the network slice in the tracking area unit, or information related to the TAC.

[0198] In operation 515, UE 101 may send a PDU session establishment request message to SMF 121. SMF 121 may receive the PDU session establishment request message from UE 101.

[0199] In operation 517, the SMF 121 may send a PDU session establishment response message to the UE 101 as a response to the PDU session establishment request message. The UE 101 may receive the PDU session establishment response message from the SMF 121.

[0200] In operation 521:

[0201] Example 1)

[0202] This embodiment includes the case where SMF 121 has configured the granularity of network slice related authentication, mobility and sessions as tracking areas (Embodiment 1-A) or registration areas (Embodiment 1-B).

[0203] (Example 1-A-1)

[0204] For example, SMF 121 may configure the granularity of authentication, mobility, or sessions related to the network slice to be used by UE 101 in tracking area units.

[0205] (Example 1-A-2)

[0206] For example, the SMF 121 may configure the granularity of authentication, mobility, or session associated with a network slice used by the UE 101 in tracking area units, and may store information about the tracking area and authentication information about the tracking area. The information about the tracking area may include a TAC. For example, the SMF 121 may map NSSAI#1 to TAC#1, TAC#2, etc., and store them together to identify which network slice (e.g., NSSAI#1) is provided from which tracking area (e.g., TAC#1, TAC#2, etc.).

[0207] (Example 1-B)

[0208] For example, SMF 121 may configure the granularity of authentication, mobility, or sessions associated with a network slice used by UE 101 in registration area units.

[0209] Example 2)

[0210] This embodiment includes a situation where AMF 111 configures or configures and stores the granularity of authentication, mobility, or sessions associated with a network slice in units of tracking areas or registration areas, and SMF 121 also configures the granularity of authentication, mobility, or sessions associated with the network slice as tracking areas or registration areas based on the configuration information configured by AMF 111.

[0211] (Example 2-A-1)

[0212] For example, in a case where AMF 111 configures the granularity of at least one of mobility and authentication associated with a network slice used by UE 101 in a tracking area unit, SMF 121 may configure the granularity of sessions or authentication associated with the network slice used by UE 101 in the tracking area unit based on the configuration information configured by AMF 111.

[0213] (Example 2-A-2)

[0214] For example, in a case where the AMF 111 configures the granularity of mobility or authentication associated with a network slice used by the UE 101 in a tracking area unit, and stores and manages a mutual mapping relationship between information about the tracking area and authentication information about the tracking area, the SMF 121 may configure the granularity of authentication or session associated with the network slice used by the UE 101 in a tracking area unit based on the information configured and stored by the AMF. The information about the tracking area may include a TAC.

[0215] (Example 2-B)

[0216] For example, in a case where AMF 111 configures the granularity of mobility or authentication associated with a network slice used by UE 101 in a registration area unit, SMF 121 may configure the granularity of sessions or authentication associated with a network slice used by UE 101 in a registration area unit by considering the configuration of AMF 111.

[0217] In operation 523, the SMF 121 may send an authentication request message to the AAA 181. The AAA 181 may receive the authentication request message from the SMF 121.

[0218] For example, the authentication request message may include an indication of the granularity of network slices to be used in the tracking area unit (e.g., T if managed in the tracking area unit, R if managed in the registration area unit, etc.) to notify UE 101, an indication of network slices being used in the tracking area unit (e.g., configuring the corresponding bit to 1 to indicate that the network slices are managed in the tracking area unit), and at least one of the associated tracking area information (e.g., TAC#1, TAC#2, TAC#3, etc.).

[0219] In operation 525, AAA 181 may configure the granularity of the network slice used by UE 101 in the tracking area unit. For example, AAA 181 may map the TAC and information about the network slice used by UE 101, or may bind, map, or store information about the network slice used by UE 101, network slice authentication information, TAC, or location information of UE 101.

[0220] In operation 527, AAA 181 may send an authentication response message to SMF 121 as a response to the authentication request message. The authentication response message may include an indication notifying that the network accessed by UE 101 has the capability to configure support for network slicing in the tracking area unit. The authentication response message may include an indication notifying that establishment, management, or authentication of network slicing is allowed in the tracking area unit, or an indication (bit) for allowing the indication.

[0221] In operation 531, SMF 121 may send an authentication response message to AMF 111.

[0222] For example, the authentication response message may include at least one of a tracking area list, information about network slices available in the tracking area, and authentication information about whether the network slice is available in the tracking area.

[0223] In operation 541, AMF 111 may send a registration accept message to UE 101.

[0224] For example, the registration acceptance message may include a list of tracking areas, information about network slices available in the tracking area, and at least one of authentication information about whether the network slice is available in the tracking area.

[0225] In operation 551, UE 101 may store at least one of a tracking area list included in the authentication request message, information about network slices available in the tracking area, and authentication information about the network slice.

[0226] The stored information may include a list of TACs associated with available network slices. For example, the stored information may include a list of available TACs that are certified or capable of providing network slice services, network slices, and information about the network slice certification of each TAC.

[0227] UE 101 may attempt to access the network based on the stored information during registration. For example, UE 101 may attempt to establish and modify a PDU session based on the stored information.

[0228] For example, UE 101 may generate and transmit a mobility management message of the UE, such as a service request or registration request message for mobility or session management of UE 101, or a session management message of the UE, such as a PDU session establishment request message or a PDU session modification request, by using / including the stored tracking area list, information about the network slices available in the tracking area, and authentication information for the network slices.

[0229] For example, UE 101 can identify the network slice that is authenticated and allowed to access in units of TAC based on the stored information in order to attempt to access, or can send at least one of a registration request message, a service request message, a PDU session establishment request message, and a PDU session modification request message to a network or network slice that can provide network slice authentication in units of TAC.

[0230] FIG6 shows a flowchart of a process for providing communication to a UE 101 moving in a 5G network environment by considering network slicing according to an embodiment of the present disclosure.

[0231] 6 , in operation 611, UE 101 may send a registration request message to AMF 111. For example, the registration request message may include at least one of the following information.

[0232] 1) An indication (or information) for requesting the network to allow mobility tracking of UE 101, register the location of UE 101, and allow UE 101 to use and authenticate the network slice in the tracking area unit.

[0233] 2) An indication for notifying the network that UE 101 has the capability to use and authenticate slices in the tracking area unit. The information includes information such as a bit or an indication that notifies UE 101 that it has the capability to receive authentication of network slices in the tracking area unit or to perform communication using corresponding authentication information.

[0234] 3) Network slice information (e.g., Network Slice Selection Assistance Information (NSSAI)) used by UE 101 to request services in tracking area units. NSSAI may include (a) a slice / service type (SST) requested by the user terminal or (b) a slice differentiator (SD) corresponding to the user terminal and the slice / service type. For example, network slice #1 (NSSAI #1), network slice #2 (NSSAI #2), etc.

[0235] 4) UE 101 desires to request tracking area information, such as a tracking area code (TAC), for services related to the slice. For example, when requesting to use and authenticate a network slice in a tracking area unit from network slice #1, UE 101 may send the TAC information to the network (e.g., AMF 111).

[0236] In operation 613, AMF 111 may configure the granularity of mobility or authentication associated with the network slice to be used by UE 101 in the tracking area unit based on the registration request message received from UE 101.

[0237] For example, in an embodiment (Case 1), AMF 111 may configure the network slice to be used by UE 101 and the granularity of mobility or authentication associated with the slice in a tracking area unit, and may store a mapping relationship between information about the tracking area and authentication information about the tracking area. The information about the tracking area may include a TAC. For example, AMF 111 may map NSSAI#1, which is network slice information, to TAC#1, which is tracking area information, and map NSSAI#2, NSSAI#3, etc. to TAC#2, and may also store information about whether UE 101 is allowed to use the corresponding network slice (network slice identified by NSSAI) in each TAC.

[0238] In another embodiment (Case 2), the AMF 111 may configure the granularity of mobility and authentication associated with the network slice to be used by the UE 101 in registration area units.

[0239] The AMF 111 may send at least one of an indication for notifying the UE 101 that the UE 101 will use the mobility granularity of the network slice in the tracking area unit, an indication (or bit or information) indicating that the UE 101 is using the network slice in the tracking area unit, and information related to the TAC to the SMF 121 or to the AAA 181 via the SMF. For example, at least one of the SMF 121 and the AAA 181 may receive from the AMF 111 an indication for notifying the UE 101 that the UE 101 will use the mobility granularity of the network slice in the tracking area unit, an indication (or bit or information) indicating that the UE 101 is using the network slice in the tracking area unit, or information related to the TAC.

[0240] In operation 615, UE 101 may send a PDU session establishment request message to SMF 121. SMF 121 may receive the PDU session establishment request message from UE 101.

[0241] In operation 617, the SMF 121 may send a PDU session establishment response message to the UE 101 as a response to the PDU session establishment request message. The UE 101 may receive the PDU session establishment response message from the SMF 121.

[0242] In operation 621:

[0243] Example 1)

[0244] This embodiment includes the case where SMF 121 has configured the granularity of network slice related authentication, mobility and sessions as tracking areas (Embodiment 1-A) or registration areas (Embodiment 1-B).

[0245] (Example 1-A-1)

[0246] For example, SMF 121 may configure the granularity of authentication, mobility, or sessions related to the network slice to be used by UE 101 in tracking area units.

[0247] (Example 1-A-2)

[0248] For example, the SMF 121 may configure the granularity of authentication, mobility, or session associated with a network slice used by the UE 101 in tracking area units, and may store information about the tracking area and authentication information about the tracking area. The information about the tracking area may include a TAC. For example, the SMF 121 may map NSSAI#1 to TAC#1, TAC#2, etc., and store them together to identify which network slice (e.g., NSSAI#1) is provided from which tracking area (e.g., TAC#1, TAC#2, etc.).

[0249] (Example 1-B)

[0250] For example, SMF 121 may configure the granularity of authentication, mobility, or sessions associated with a network slice used by UE 101 in registration area units.

[0251] Example 2)

[0252] This embodiment includes a situation where AMF 111 configures or configures and stores the granularity of authentication, mobility, or sessions associated with a network slice in units of tracking areas or registration areas, and SMF 121 also configures the granularity of authentication, mobility, or sessions associated with the network slice as tracking areas or registration areas based on the configuration information configured by AMF 111.

[0253] (Example 2-A-1)

[0254] For example, in a case where AMF 111 configures the granularity of at least one of mobility and authentication associated with a network slice used by UE 101 in a tracking area unit, SMF 121 may configure the granularity of sessions or authentication associated with the network slice used by UE 101 in the tracking area unit based on the configuration information configured by AMF 111.

[0255] (Example 2-A-2)

[0256] For example, in a case where the AMF 111 configures the granularity of mobility or authentication associated with a network slice used by the UE 101 in a tracking area unit, and stores and manages a mutual mapping relationship between information about the tracking area and authentication information about the tracking area, the SMF 121 may configure the granularity of authentication or session associated with the network slice used by the UE 101 in a tracking area unit based on the information configured and stored by the AMF. The information about the tracking area may include a TAC.

[0257] (Example 2-B)

[0258] For example, in a case where AMF 111 configures the granularity of mobility or authentication associated with a network slice used by UE 101 in a registration area unit, SMF 121 may configure the granularity of sessions or authentication associated with a network slice used by UE 101 in a registration area unit by considering the configuration of AMF 111.

[0259] In operation 623, the SMF 121 may send an authentication request message to the AAA 181. The AAA 181 may receive the authentication request message from the SMF 121.

[0260] For example, the authentication request message may include an indication of the granularity of network slices to be used in the tracking area unit (e.g., T if managed in the tracking area unit, R if managed in the registration area unit, etc.) to notify UE 101, an indication of network slices being used in the tracking area unit (e.g., configuring the corresponding bit to 1 to indicate that the network slices are managed in the tracking area unit), and at least one of the associated tracking area information (e.g., TAC#1, TAC#2, TAC#3, etc.).

[0261] In operation 625, AAA 181 may configure the granularity of the network slice used by UE 101 in the tracking area unit. For example, AAA 181 may map the TAC and information about the network slice used by UE 101, or may bind, map, or store information about the network slice used by UE 101, network slice authentication information, TAC, or location information of UE 101.

[0262] In operation 627, AAA 181 may send an authentication response message to SMF 121 as a response to the authentication request message. The authentication response message may include an indication notifying that the network accessed by UE 101 has the capability to configure support network slicing in the tracking area unit. The authentication response message may include an indication notifying that establishment, management, or authentication of network slicing is allowed in the tracking area unit, or an indication (bit) for allowing the indication.

[0263] In operation 631, SMF 121 may send an authentication response message to AMF 111.

[0264] For example, the authentication response message may include at least one of a tracking area list, information about network slices available in the tracking area, and authentication information about whether the network slice is available in the tracking area.

[0265] In operation 641, AMF 111 may send a registration reject message to UE 101.

[0266] Example 6-A)

[0267] Network slice information that can be authenticated / available in the tracking area unit (TAC available network slice information).

[0268] For example, the registration reject message may include information of network slices that UE 101 can authenticate / use in the tracking area unit (TAC available network slices).

[0269] The TAC available network slice information that UE 101 is able to authenticate / use in the tracking area unit may include at least one of the following information.

[0270] 1) Information about network slices that are authenticated or allowed to be used in the tracking area unit (e.g., information about network slices that are authenticated or allowed to be used in the corresponding TAC, NSSAI, etc.).

[0271] 2) A list of relevant Tracking Area Codes (TACs), Tracking Area Information, or Tracking Area List.

[0272] 3) Authentication information about whether the corresponding network slice is available in the tracking area.

[0273] Thereafter, UE 101 may attempt to access the network in a subsequent registration attempt by using the network slice information that may be accessed / authenticated in the TAC. Alternatively, UE 101 may attempt to establish or modify a session in a subsequent PDU session establishment / modification attempt by using the network slice information that may be accessed / authenticated in the TAC.

[0274] In an embodiment, in the case where the UE 101 receives network slice information (TAC available network slice) that can be authenticated / available in the tracking area unit through a registration reject / or registration accept message after attempting registration,

[0275] 1) UE 101 may add the corresponding TAC or the corresponding network slice to the authenticatable / available network slice (TAC available network slice) information and store it in the SIM / non-volatile / volatile memory.

[0276] 2) UE 101 may then attempt to subsequently access the TAC or network slice stored in the authenticatable / available network slice (TAC available network slice) information.

[0277] 3) In addition, in the event that a subsequent registration process of the UE 101 for the TAC or network slice included or stored in the authenticatable / available network slices (TAC available network slices) fails, the TAC or network slice may be removed from the list of authenticated / available network slices (TAC available network slices) information.

[0278] 4) Furthermore, the list may be stored until the UE is switched off or the SIM is removed. Alternatively, the list may be deleted when the UE is switched off or the SIM is removed. Alternatively, the list may be updated after a predetermined period of time.

[0279] Example 6-B)

[0280] Network slice (TAC prohibited network slice) information, which cannot be authenticated / available in the tracking area unit, or is not allowed.

[0281] For example, the registration reject message may include information about network slices that UE 101 cannot authenticate / use in the tracking area unit (network slices prohibited by the TAC), or information about network slices that are not allowed.

[0282] Alternatively, although UE 101 attempts to use and authenticate network slice information in the tracking area unit and is not allowed to do so, UE 101 may store the corresponding information in network slice information that cannot be authenticated / available or is not allowed (TAC prohibited network slice).

[0283] The TAC-prohibited network slice information that the UE 101 cannot authenticate / use in the tracking area unit or the TAC-prohibited network slice information that is not allowed may include at least one of the following information.

[0284] 1) Tracking Area Code (TAC) list, tracking area information, or tracking area list.

[0285] 2) Information about network slices that are not available in the tracking area unit (e.g., network slice information, NSSAI, etc. that are not allowed to be used in the corresponding TAC).

[0286] 3) Information about network slices that are not authenticated, cannot be authenticated, or attempt to be authenticated but fail in the tracking area unit (e.g., information about network slices that failed to be authenticated in the corresponding TAC, NSSAI, etc.).

[0287] 4) Authentication information related to whether the network slice is available in the tracking area.

[0288] 5) Information about the reasons for the rejection.

[0289] Example 1 related to rejection reason: Reason #xx)

[0290] For example, the information about the rejection cause may be "information / cause value / or indication indicating that authentication of the network slice is not supported in the tracking area unit". For example, the information about the rejection cause may include a cause value xx. For example, the cause value xx may indicate that authentication of the network slice cannot be supported in the tracking area unit. For example, UE 101 may determine that the network cannot support authentication of the network slice in the tracking area unit based on the registration rejection message including the information about the rejection cause.

[0291] Example 2 related to rejection reason: Reason #yy)

[0292] The information about the rejection cause may be "information / cause value / or indication related to a situation where authentication of the network slice has been attempted in the tracking area unit but failed". For example, the information about the rejection cause may include a cause value yy. For example, the cause value yy may indicate that authentication of the network slice has been attempted in the tracking area unit but failed. For example, UE 101 may determine, based on the registration rejection message including the information about the rejection cause, that the network attempted to authenticate the network slice in the tracking area unit, but did not successfully authenticate the network slice in the corresponding tracking area.

[0293] In an embodiment, in the case where UE 101 receives "information / cause value / or indication indicating that authentication of network slice cannot be supported in tracking area unit" (cause #xx) through a registration reject / or registration accept message, as a registration / access result, after the registration attempt, UE 101 may add network slice information, TAC information, etc. to a list of network slices that cannot be authenticated / used or are not allowed in the tracking area unit (TAC prohibited network slices), and store it in a SIM / non-volatile / volatile memory.

[0294] UE 101 may subsequently not attempt to register / access the list of network slices that cannot be authenticated / used or are not allowed (TAC prohibited network slices) in the stored tracking area unit.

[0295] In addition, in the event that UE 101 subsequently successfully completes a registration process for a TAC and a network slice in a list of network slices that cannot be authenticated / used or are not allowed (TAC-prohibited network slices) stored in the tracking area unit, the TAC and the network slice may be removed from the TAC-prohibited network slice list in the tracking area unit.

[0296] Furthermore, the list may be stored until the UE 101 is turned off or the SIM is removed. Alternatively, the list may be deleted when the UE 101 is turned off or the SIM is removed. Alternatively, the list may be updated after a predetermined period of time.

[0297] In an embodiment, in the case where the UE 101 receives "information / cause value / indication indicating that authentication to the network slice in the tracking area unit failed (cause #yy)" in the REGISTRATION REJECT / or REGISTRATION ACCEPT message,

[0298] 1) The PLMN may be stored in a list of network slices that cannot be authenticated / used in the cell of the tracking area for the network slice service or are not allowed (TAC prohibited network slices).

[0299] 2) In addition, UE 101 may not subsequently attempt to register / access a network slice that cannot be authenticated / used or is not allowed in the tracking area unit (TAC prohibited network slice).

[0300] 3) After the registration process is successfully performed, the corresponding network slice information and TAC information can be deleted from the list of network slices that cannot be authenticated / used or are not allowed in the tracking area unit (TAC-prohibited network slices).

[0301] 4) The list is deleted when the UE 101 is switched off or the SIM is removed. Alternatively, the list may be updated after a predetermined period of time.

[0302] Thereafter, UE 101 may attempt to register / access the network during the registration phase, excluding the network slice indicated by the information included in the registration reject message, or excluding a TAC that does not support network slicing. For example, UE 101 may perform an operation of establishing a PDU session or modifying a PDU session, excluding the network slice indicated by the registration reject message, or excluding a TAC that does not support network slicing.

[0303] In operation 651, UE 101 may store at least one of a tracking area list included in the authentication request message, information about network slices available in the tracking area, and authentication information about the network slice.

[0304] The stored information may include a list of TACs associated with available network slices. For example, the stored information may include a list of available TACs that are certified or capable of providing network slice services, network slices, and information about the network slice certification of each TAC.

[0305] UE 101 may attempt to access the network based on the stored information during registration. For example, UE 101 may attempt to establish and modify a PDU session based on the stored information.

[0306] For example, UE 101 may generate and transmit a mobility management message of the UE, such as a service request or registration request message for mobility or session management of UE 101, or a session management message of the UE, such as a PDU session establishment request message or a PDU session modification request, by using / including the stored tracking area list, information about the network slices available in the tracking area, and authentication information for the network slices.

[0307] For example, UE 101 can identify the network slice that is authenticated and allowed to access in units of TAC based on the stored information in order to attempt to access, or can send at least one of a registration request message, a service request message, a PDU session establishment request message, and a PDU session modification request message to a network or network slice that can provide network slice authentication in units of TAC.

[0308] In operation 661, UE 101 may send a second registration request message to AMF 111 through RAN 103.

[0309] For example, the registration request message may include at least one of the following information.

[0310] 1) An indication (or information) for requesting the network to allow mobility tracking of UE 101 in a tracking area unit, to register the location of UE 101, and to allow UE 101 to use and authenticate a network slice.

[0311] 2) An indication for notifying the network that UE 101 has the capability to use and authenticate slices in the tracking area unit. The information includes information such as a bit or an indication that notifies UE 101 that it has the capability to receive authentication of network slices in the tracking area unit or to perform communication using corresponding authentication information.

[0312] 3) Network slice information (e.g., Network Slice Selection Assistance Information (NSSAI)) used by UE 101 to request services in tracking area units. NSSAI may include (a) a slice / service type (SST) requested by the user terminal or (b) a slice differentiator (SD) corresponding to the user terminal and the slice / service type. For example, network slice #1 (NSSAI #1), network slice #2 (NSSAI #2), etc.

[0313] 4) UE 101 desires to request tracking area information, such as a tracking area code (TAC), for services related to the slice. For example, when requesting to use and authenticate a network slice in a tracking area unit from network slice #1, UE 101 may send the TAC information to the network (e.g., AMF 111).

[0314] FIG. 7 is a block diagram showing a configuration of a UE 101 according to the present disclosure.

[0315] As shown in FIG. 7 , the UE 101 of the present disclosure may include a transceiver 710, a memory 720, and a processor 730. The processor 730, the transceiver 710, and the memory 720 of the UE 101 may operate according to the communication method of the UE 101 described above. However, the elements of the UE 101 are not limited to the above examples. For example, the UE 101 may include more elements or fewer elements than the above elements. In addition, the processor 730, the transceiver 710, and the memory 720 may be implemented in the form of a single chip.

[0316] The transceiver 710, which is collectively referred to as a receiver of the UE 101 and a transmitter of the UE 101, can transmit or receive signals to or from the base station 103 or the network entities 111, 121, 131, 151, and 181. The signals transmitted to or received from the base station 103 may include control information and data. To this end, the transceiver 710 may include an RF transmitter configured to up-convert and amplify the frequency of the transmitted signal, and an RF receiver configured to low-noise amplify and down-convert the frequency of the received signal. However, this is only an embodiment of the transceiver 710, and the elements of the transceiver 710 are not limited to the RF transmitter and the RF receiver.

[0317] In addition, the transceiver 710 may include a wired or wireless transceiver, and may include various configurations for transmitting and receiving signals.

[0318] In addition, the transceiver 710 may receive a signal through a wireless channel and output the signal to the processor 730 , and transmit a signal output from the processor 730 through a wireless channel.

[0319] In addition, the transceiver 710 may receive a communication signal and output the communication signal to the processor, and transmit the signal output from the processor to a network entity via a wired or wireless network.

[0320] The memory 720 may store programs and data required for the operation of the UE 101. In addition, the memory 720 may store control information or data included in a signal acquired by the terminal. The memory 720 may include a storage medium such as a ROM, RAM, hard disk, CD-ROM, and DVD, or a combination of storage media.

[0321] The processor 730 may control a series of processes so that the UE 101 can operate according to the above-mentioned embodiments of the present disclosure. The processor 730 may include at least one processor. For example, the processor 730 may include a communication processor (CP) configured to perform control for communication and an application processor (AP) configured to control a high layer such as an application.

[0322] FIG8 shows a configuration of network entities 103 , 111 , 121 , 131 , 151 , and 181 according to the present disclosure.

[0323] As shown in FIG8, the network entities 103, 111, 121, 131, 151, and 181 of the present disclosure may include a transceiver 810, a memory 820, and a processor 830. The processor 830, the transceiver 810, and the memory 820 of the network entities 103, 111, 121, 131, 151, and 181 may operate according to the communication methods of the above-mentioned network entities 103, 111, 121, 131, 151, and 181. However, the elements of the network entities 103, 111, 121, 131, 151, and 181 are not limited to the aforementioned examples. For example, the network entities 103, 111, 121, 131, 151, and 181 may include more elements or fewer elements than those described above. In addition, the processor 830, the transceiver 810, and the memory 820 may be implemented in the form of a single chip. The network entities 103, 111, 121, 131, 151, 181 may include network functions (NFs), such as the aforementioned access and mobility management function (AMF) 111, session management function (SMF) 121, policy and charging function (PCF) 161, network exposure function (NEF), unified data management (UDM) 151, and user plane function (UPF). The network entity may also include a base station 131.

[0324] The transceiver 810, which is collectively referred to as a receiver including network entities 103, 111, 121, 131, 151 and 181 and a transmitter of network entities 103, 111, 121, 131, 151 and 181, can send signals to UE 101 or other network entities and receive signals from UE 101 or other network entities. The signals sent and received may include control information and data. To this end, the transceiver 810 may include an RF transmitter configured to up-convert and amplify the frequency of the transmitted signal, and an RF receiver configured to perform low noise amplification and down-conversion on the frequency of the received signal. However, this is only an embodiment of the transceiver 810, and the elements of the transceiver 810 are not limited to RF transmitters and RF receivers. The transceiver 810 may include a wired or wireless transceiver, and may include various configurations for sending and receiving signals.

[0325] In addition, the transceiver 810 may receive a signal through a communication channel (eg, a wireless channel) and output the signal to the processor 830 , and transmit a signal output from the processor 830 through the communication channel.

[0326] In addition, the transceiver 810 may receive a communication signal and output the communication signal to the processor, and transmit the signal output from the processor to the UE 101 or the network entities 103 , 111 , 121 , 131 , 151 , and 181 via a wired or wireless network.

[0327] The memory 820 may store programs and data required for the operation of the network entities 103, 111, 121, 131, 151, and 181. In addition, the memory 820 may store control information or data contained in signals obtained from the network entities 103, 111, 121, 131, 151, and 181. The memory 820 may include a storage medium such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD, or a combination of storage media.

[0328] The processor 830 may control a series of processes to enable the network entities 103, 111, 121, 131, 151, and 181 to operate according to the above-mentioned embodiments of the present disclosure. The processor 830 may include at least one processor. The method according to the claims of the present disclosure or the embodiments described herein may be implemented in the form of hardware, software, or a combination of hardware and software.

[0329] It should be noted that the above-mentioned structure diagram, the exemplary diagram of the method for sending control / data signals, the exemplary diagram of the operation process and the structure diagram are not intended to limit the scope of the present disclosure. That is, all components, network entities or operation steps described in the embodiments of the present disclosure should not be interpreted as necessary components for implementing the present disclosure, and the present disclosure can be implemented within the scope of not damaging the essence of the present disclosure by only including some components. In addition, the various embodiments of the present disclosure can be combined with each other as needed. For example, parts according to the method of the present disclosure can be combined with each other to enable network entities and terminals to operate.

[0330] In the above-mentioned specific embodiment of the present disclosure, according to the specific embodiment of the present disclosure, the components included in the present disclosure are expressed in singular or plural form. However, for the convenience of explanation, the singular or plural form is appropriately selected, and the present disclosure is not limited thereto. Therefore, the components expressed in plural form may also be configured as a single component, and the components expressed in singular form may also be configured as multiple components.

[0331] 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 determined by the claims described below and the claims and equivalents.

[0332] Although the present disclosure has been described with various embodiments, various changes and modifications may be suggested to one skilled in the art. The present disclosure is intended to encompass such changes and modifications as fall within the scope of the appended claims.

Claims

1. A method for operating a terminal in a wireless communication system, the method comprising: Sending a first registration request message to an access and mobility management function (AMF) through a base station; receiving, by the base station from the AMF, a registration reject message as a response to the first registration request message; as well as Based on the registration rejection message, a second registration request message is sent to the AMF through the base station.

2. The method according to claim 1, wherein: The first registration request message includes: A first indication requests authentication of a network slice of a terminal in a tracking area unit, The second indication indicates that the terminal can authenticate the network slice of the terminal in the tracking area unit, a third indication, indicating that the terminal is capable of receiving and using authentication information of the network slice of the terminal, and A fourth indication indicates that the terminal can perform communication using the authentication information.

3. The method according to claim 1, wherein: The first registration request message includes: information about the tracking area associated with the network slice for the service request desired by the terminal, and Information about network slicing.

4. The method according to claim 1, wherein: The registration rejection message includes at least one of the following: A tracking area list determined based on the first registration request message, Information about the network slices available in the tracking area, and Authentication information used for network slicing.

5. The method according to claim 1, wherein: Registration rejection messages include: A tracking area list determined based on the first registration request message, Information about network slices that are not available in the tracking area, Authentication information for network slicing, and Information about network slices that failed authentication in the tracking area.

6. The method according to claim 1, wherein: Registration rejection messages include: A tracking area list determined based on the first registration request message, Information about network slices that are not available in the tracking area, Information about network slices for which authentication has been attempted but has failed in the tracking area, and Authentication information used for network slicing.

7. The method according to claim 1, wherein: The Registration Reject message is generated based on the First Authentication Response message sent from the Session Management Function (SMF) to the AMF, and The first authentication response message includes a tracking area list determined based on the first registration request message, information about network slices available in the tracking area, and authentication information about the network slices.

8. The method according to claim 7, wherein: The first authentication response message is generated based on a second authentication response message sent from Authentication, Authorization, and Accounting (AAA) to the SMF, and The second authentication response message includes a first indication and a second indication, wherein the first indication indicates that the wireless communication system has the ability to support and configure network slices in the tracking area unit determined based on the first registration request message, and the second indication indicates that the establishment, management or authentication of network slices in the tracking area unit is allowed.

9. The method according to claim 8, wherein: The second authentication response message is generated based on the authentication request message sent from the SMF to the AAA, and The authentication request message includes a tracking area code (TAC) and a granularity indication, wherein the granularity indication instructs the terminal to use a network slice in a tracking area unit determined based on the first registration request message.

10. The method according to claim 9, wherein: The authorization request message is generated based on the network slice configuration information determined according to the first registration request message, and The network slice configuration information includes at least one of an indication indicating that the granularity of mobility or authentication associated with the network slice for the terminal is configured in a tracking area unit, and an indication indicating a mutual mapping relationship between information about the tracking area and authentication information about the tracking area.

11. A terminal in a wireless communication system, the terminal comprising: Transceiver; and a processor coupled to the transceiver, wherein the processor is configured to: Sending a first registration request message to an access and mobility management function (AMF) through a base station; receiving, by the base station, from the AMF a registration reject message as a response to the first registration request message; and Based on the registration rejection message, a second registration request message is sent to the AMF through the base station.

12. The terminal according to claim 11, wherein: The first registration request message includes: A first indication requests authentication of a network slice of a terminal in a tracking area unit, The second indication indicates that the terminal can authenticate the network slice of the terminal in the tracking area unit, a third indication, indicating that the terminal is capable of receiving and using authentication information of the network slice of the terminal, and A fourth indication indicates that the terminal can perform communication using the authentication information.

13. The terminal according to claim 11, wherein: The first registration request message includes: information about the tracking area associated with the network slice for the service request desired by the terminal, and Information about network slicing.

14. The terminal according to claim 11, wherein: The registration rejection message includes at least one of the following: a list of tracking areas determined based on the first registration message, information about network slices available in the tracking areas, and Authentication information used for network slicing.

15. The terminal according to claim 11, wherein: Registration rejection messages include: A tracking area list determined based on the first registration message, Information about network slices that are not available in the tracking area, Authentication information for network slicing, and Information about network slices that failed authentication in the tracking area.

Images