Communication related to network slices

Abstract

One disclosure of the present specification provides a method for an AMF to communicate, according to which the AMF can receive a registration message including requested NSSAI information, and the AMF can send a response message to the UE in response to the registration request message.

Description

[Technical field]

[0001] This specification relates to mobile communications. [Background technology]

[0002] 3rd generation partnership project (3GPP) long-term evolution (LTE) is a technology that enables high-speed packet communications. Many plans have been proposed for LTE goals, including reducing user and provider costs, improving service quality, and expanding and improving coverage and system capacity. 3GPP LTE requires lower cost per bit, increased service availability, flexible use of frequency bands, simple architecture, open interfaces, and reasonable power consumption of terminals as upper-level requirements.

[0003] A task has been initiated within the International Telecommunication Union (ITU) and 3GPP to develop requirements and specifications for a New Radio (NR) system. 3GPP needs to identify and develop the technical building blocks necessary to timely and successfully standardize a new Radio Access Technology (RAT) that meets all urgent market needs and the long-term requirements set out in the ITU-R (International Mobile Telecommunications) International Mobile Telecommunications (IMT)-2020 process. NR also requires the use of spectrum bands in the minimum and maximum 100 GHz range that can be used for wireless communications into the far future.

[0004] NR targets a single technology framework that addresses all usage scenarios, requirements and deployment scenarios, including enhanced mobile broadband (eMBB), massive machine-type-communications (mMTC), ultra-reliable and low latency communications (URLLC), etc. NR is inherently forward compatible.

[0005] In NR, network slices are introduced.

[0006] When the terminal performs the registration procedure, it sends a Request NSSAI to the AMF. Then, the AMF sends only slices supported by the current terminal in the Allowed NSSAI to the terminal. When sending a Registration accept to the terminal, the AMF also sends the terminal's Registration area. At this time, the AMF must enable the terminal to use all slices included in the Allowed NSSAI in the Registration area assigned to the terminal. At this time, the Registration area is assigned in the form of a TA list including multiple TAs. Therefore, if the terminal cannot use a certain slice in the TA where it is currently located (e.g., the first TA), the AMF cannot include the slice in the Allowed NSSAI even if the slice can be used in all other TAs in the terminal's Registration area (e.g., all other TAs other than the first TA). Therefore, even if the terminal moves to an area where the slice is available in the Registration area (e.g., an area corresponding to one of all other TAs other than the first TA), the terminal cannot use the slice.

[0007] If the AMF sends a Rejected NSSAI to the terminal with the slice in question along with a cause that the slice is not currently allowed in the registration area, a problem will occur in which the terminal will not be able to use the slice until it leaves the registration area, even if the terminal is located in a TA that supports the slice.

[0008] Alternatively, to solve this problem, the AMF can set the registration area to include only the current TA of the terminal so that the UE can use the corresponding slice. However, if this is done, the registration area is set too narrow, and the terminal needs to frequently perform the mobility registration procedure. Summary of the Invention [Problem to be solved by the invention]

[0009] Therefore, one aspect of the present disclosure is to provide a method that can solve the above-mentioned problems. [Means for solving the problem]

[0010] In order to solve the above-mentioned problems, one disclosure of this specification provides a method for AMF communication, which may include the steps of receiving a registration message including requested NSSAI information from a UE; and sending a response message to the UE in response to the registration request message.

[0011] In order to solve the above problems, one disclosure of this specification provides a method for a UE to communicate, which may include: sending a registration message including requested NSSAI information to an AMF; and receiving a response message from the AMF in response to the registration request message. Effect of the Invention

[0012] According to the disclosure of this specification, the problems of the conventional technology can be solved.

[0013] The effects obtained through the specific examples of the present specification are not limited to the effects listed above. For example, there are various technical effects that a person having ordinary skill in the related art can understand or derive through the present specification. Accordingly, the specific effects of the present specification are not limited to those explicitly described in the present specification, but may include various effects that can be understood or derived from the technical features of the present specification. According to this specification, when a node performs an IAB operation, it becomes clear which timing alignment case is used as a reference for the IAB operation, thereby improving the stability and efficiency of wireless communication. [Brief description of the drawings]

[0014] [Figure 1] 1 illustrates an example of a communication system in which implementations of the present disclosure may be applied; [Diagram 2] 1 illustrates an example of a wireless device to which the implementations of this specification may be applied. [Diagram 3] 1 illustrates an example of a wireless device to which the implementations of this specification may be applied. [Figure 4] An example of a 5G system architecture to which the implementation of this specification is applied is shown. [Diagram 5] Another example showing the structure of the Radio Interface Protocol between the UE and the gNB. [Figure 6a-6b] 1 illustrates an example of a registration procedure to which the implementation of this specification can be applied. [Figure 7a-7b] An example of a PDU session establishment procedure to which the implementation of this specification applies is shown. [Figure 8] An example of a slice arrangement is shown. [Figure 9]1 shows an example of a procedure according to the first example of the disclosure of this specification. [Figure 10] 13 shows an example of a procedure according to the sixth example of the present disclosure. [Figure 11] 13 shows an example of a procedure according to the eighth example of the present disclosure. [Fig. 12a-12c] 13 shows an example of a procedure for requesting a UE trigger service. [Figure 13] 1 shows an example of a procedure for requesting a network trigger service. [Figure 14] 1 shows an example of a UE configuration update procedure. [Figure 15] CN-DISCLOSED An example of a selective deactivation procedure for a UP connection of an existing PDU session is shown. [Figure 16] An example of an inter NG-RAN handover procedure is shown. [Figure 17a-17b] An example of an inter NG-RAN handover procedure is shown. [Figure 18] 13 shows an example of a procedure according to the tenth example of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0015] The following techniques, devices, and systems are applied to various wireless multiple access systems. Examples of multiple access systems include code division multiple access (CDMA) systems, frequency division multiple access (FDMA) systems, time division multiple access (TDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and multi carrier frequency division multiple access (MC-FDMA) systems. CDMA is implemented over radio technologies such as universal terrestrial radio access (UTRA) or CDMA2000. TDMA is implemented over radio technologies such as global system for mobile communications (GSM), general packet radio service (GPRS), or enhanced data rates for GSM evolution (EDGE). OFDMA is implemented over radio technologies such as institute of electrical and electronics engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, or evolved UTRA (E-UTRA). UTRA is part of the universal mobile telecommunications system (UMTS). 3GPP (3rd generation partnership project) long-term evolution (LTE) is part of evolved UMTS (E-UMTS) that uses E-UTRA. 3GPP LTE uses OFDMA on the downlink (DL) and SC-FDMA on the uplink (UL).Evolution of 3GPP LTE includes LTE-A (advanced), LTE-A Pro, and / or 5G NR (New Radio).

[0016] For convenience of explanation, the implementation of this specification will be mainly described in relation to a 3GPP-based wireless communication system. However, the technical characteristics of this specification are not limited thereto. For example, the following detailed description is provided based on a mobile communication system corresponding to a 3GPP-based wireless communication system, but aspects of this specification that are not limited to a 3GPP-based wireless communication system can be applied to other mobile communication systems.

[0017] For terms and technologies used in this specification that are not specifically described, reference may be made to wireless communication standard documents published prior to this specification.

[0018] As used herein, "A or B" can mean "only A," "only B," or "both A and B." Also, as used herein, "A or B" can be interpreted as "A and / or B." For example, as used herein, "A, B or C" can mean "only A," "only B," "only C," or "any combination of A, B and C."

[0019] As used herein, a slash ( / ) or a comma can mean "and / or." For example, "A / B" can mean "A and / or B." Thus, "A / B" can mean "only A," "only B," or "both A and B." For example, "A, B, C" can mean "A, B, or C."

[0020] In this specification, "at least one of A and B" can mean "only A," "only B," or "both A and B." In addition, in this specification, the expressions "at least one of A or B" and "at least one of A and / or B" can be interpreted as "at least one of A and B."

[0021] In addition, in this specification, "at least one of A, B and C" can mean "only A," "only B," "only C," or "any combination of A, B and C." In addition, "at least one of A, B or C" or "at least one of A, B and / or C" can mean "at least one of A, B and C."

[0022] In addition, parentheses used in this specification may mean "for example." Specifically, when "control information (PDCCH)" is used, "PDCCH" is proposed as an example of "control information." In addition, "control information" in this specification is not limited to "PDCCH," and "PDDCH" is proposed as an example of "control information." In addition, when "control information (i.e., PDCCH)" is used, "PDCCH" is proposed as an example of "control information."

[0023] In this specification, technical features that are individually described in one drawing may be embodied individually or simultaneously.

[0024] Without being limited thereto, the various descriptions, functions, procedures, suggestions, methods and / or operational flow diagrams disclosed herein may be applied to various fields in which device-to-device wireless communication and / or connectivity (e.g., 5G) is required.

[0025] Hereinafter, the present specification will be described in more detail with reference to the drawings, in which the same reference numbers in the following drawings and / or description may refer to the same or corresponding hardware blocks, software blocks and / or functional blocks, unless otherwise indicated.

[0026] Although UE (User Equipment) is not shown in the attached drawings, the UE shown may be referred to by terms such as terminal, ME (Mobile Equipment), etc. Also, the UE may be a portable device such as a notebook computer, a mobile phone, a PDA, a smartphone, a multimedia device, etc., or a non-portable device such as a PC or a vehicle-mounted device.

[0027] In the following, a UE is used as an example of a wireless communication device (or a radio device, or a radio equipment) capable of wireless communication. The operations performed by the UE are performed by the wireless communication device. The wireless communication device may also be called a radio device, a radio equipment, etc. In the following, AMF may refer to an AMF node, SMF may refer to an SMF node, and UPF may refer to a UPF node.

[0028] The term base station as used hereinafter generally refers to a fixed station that communicates with wireless devices and may be referred to by other terms such as eNode B (evolved-Node B), eNB (evolved-Node B), BTS (Base Transceiver System), Access Point, gNB (Next Generation Node B), etc.

[0029] I. Techniques and Procedures Applicable to the Disclosure herein

[0030] FIG. 1 illustrates an example of a communication system in which the implementation of this specification may be applied.

[0031] The 5G usage scenarios shown in FIG. 1 are merely examples, and the technical features of this specification apply to other 5G usage scenarios not shown in FIG. 1.

[0032] The three main requirement categories for 5G are (1) the enhanced mobile broadband (eMBB) category, (2) the massive machine type communication (mMTC) category, and (3) the ultra-reliable and low latency communications (URLLC) category.

[0033] Some use cases may require multiple categories for optimization, others may focus only on one KPI (key performance indicator), 5G supports such a variety of use cases in a flexible and reliable way.

[0034] eMBB goes far beyond basic mobile Internet connectivity, covering a wealth of interactive tasks and media and entertainment applications in the cloud and augmented reality. Data is one of the core drivers of 5G, and in the 5G era, dedicated voice services may not be available at first. In 5G, voice processing is expected to be simplified as an application that utilizes the data access provided by the communication system. The increase in traffic is mainly due to the increase in content size and the increase in applications that require high data transmission rates. As more devices are connected to the Internet, streaming services (audio and video), conversational video, and mobile Internet connections will become more widely used. Many such applications require an always-on connection to push real-time information and alerts for users. Cloud storage and applications are rapidly increasing on mobile communication platforms and are applied to all aspects of business and entertainment. Cloud storage is a special use case that accelerates the increase in uplink data transmission rates. 5G will also be used for remote tasks in the cloud. When using haptic interfaces, 5G requires much lower end-to-end latency to maintain a good user experience. Entertainment, for example cloud gaming and video streaming, is another key factor driving the demand for mobile broadband capabilities. Smartphones and tablets are a necessity for entertainment everywhere, including in highly mobile environments such as trains, carriages, and airplanes. Another use case is augmented reality for entertainment and information retrieval. In this case, augmented reality requires very low latency and instantaneous data volume.

[0035] One of the most promising use cases of 5G is related to its ability to seamlessly connect embedded sensors in all sectors, i.e. mMTC. Potential number of internet-of-things (IoT) devices is expected to reach 240 million by 2020. Industrial IoT is one of the main roles that will enable smart cities, asset tracking, smart utilities, agriculture, and security infrastructure through 5G.

[0036] URLLC encompasses ultra-reliable, low-latency links for new services that are transforming industries through remote operation of key infrastructure and autonomous vehicles. Reliability and latency are essential for controlling smart grids, automating industries, achieving robotics, and controlling and coordinating drones.

[0037] 5G is a means to deliver gigabits per second of streaming rated at hundreds of megabits per second and can complement fiber-to-the-home (FTTH) and cable-based broadband (or DOCSIS). Such high speeds are necessary to deliver 4K and higher (6K, 8K and higher) resolution TV as well as virtual and augmented reality. Virtual reality (VR) and augmented reality (AR) applications include highly immersive sports games. Certain applications require specialized network configurations. For example, VR games require gaming companies to consolidate their core servers into the network operator's edge network servers to minimize latency.

[0038] Automobiles are expected to be a new important synchronizing force in 5G with many use cases for mobile communication for vehicles. For example, passenger entertainment requires high concurrent capacity and high mobility broadband mobile communication, as users expect continuous high quality connection regardless of location and speed in the future. Another use case in the automotive field is AR dashboards. AR dashboards allow drivers to identify objects in the dark other than those visible in the front window, and overlap the information transfer to the driver to show the distance and movement of the object. In the future, wireless modules will enable communication between vehicles, exchange of information between vehicles and supporting infrastructure, and between vehicles and other connected devices (e.g. devices accompanying pedestrians). Safety systems guide drivers through alternative courses of action to drive more safely and reduce the risk of accidents. The next step will be vehicles that are remotely operated or autonomous. This requires very reliable and very fast communication between each other autonomous vehicles and between vehicles and infrastructure. In the future, autonomous vehicles will perform all driving activities and the driver will only focus on abnormal traffic that the vehicle cannot identify. The technical requirements of autonomous vehicles demand ultra-low latency and ultra-high reliability to enhance road safety to levels unattainable by humans.

[0039] Smart cities and smart homes / buildings, also referred to as smart societies, will be outfitted with high density wireless sensor networks. A distributed network of intelligent sensors will identify the requirements for cost and energy efficient maintenance of the city or house. A similar setup can be implemented for each home. All temperature sensors, window and heating controls, burglar alarms, home appliances will be wirelessly connected. Many of these sensors have low data transmission speeds, power and cost, but real-time HD video is required for monitoring by certain types of devices.

[0040] Higher levels of decentralization of energy consumption and distribution, including heat or gas, require automated control over a distribution sensor network. A smart grid uses digital information and communication technologies to collect information and interconnect sensors to act on the information collected. Because this information can include supplier and consumer actions, a smart grid can improve the distribution of fuels, such as electricity, in ways that are more efficient, reliable, economical, productive, sustainable, and automated. A smart grid may be thought of as a low latency or other sensor network.

[0041] Mission-critical applications (e.g., e-health) are one of the 5G usage scenarios. The health segment includes many applications that benefit from mobile communications. Communication systems can support telemedicine to provide clinical care in remote locations. Telemedicine helps reduce the barrier of distance and improves access to medical services that are not continuously available in remote rural areas. Telemedicine can also be used in emergency situations to perform critical care and save lives. Mobile-based wireless sensor networks can provide remote monitoring and sensing for parameters such as heart rate and blood pressure.

[0042] Wireless and mobile communications are becoming more and more important in industrial applications. Cabling is expensive to install and maintain. The possibility of replacing cables with reconfigurable wireless links is therefore an attractive opportunity in many industrial sectors. However, to achieve such a replacement, wireless access needs to be built with similar latency, reliability and capacity as cables, and the management of wireless access needs to be simplified. Low latency and very low error probability are the new requirements when 5G connections are needed.

[0043] Logistics and cargo tracking are important use cases for mobile communications using location-based information systems to enable inventory and package tracking anywhere. Logistics and cargo use cases typically require low data rates but need location information with wide range and reliability.

[0044] 1, the communication system (1) includes wireless devices 100a to 100f, a base station (BS; 200), and a network 300. FIG. 1 illustrates a 5G network as an example of the network of the communication system (1), but the implementation of this specification is not limited to the 5G system and is applicable to future communication systems beyond the 5G system.

[0045] The base station 200 and network 300 are implemented with wireless devices, and a particular wireless device can act as a base station / network node in conjunction with other wireless devices.

[0046] The wireless devices 100a to 100f are devices that communicate using a radio access technology (RAT) (e.g., 5G NR or LTE), and may be referred to as communication / wireless / 5G devices. The wireless devices 100a to 100f may include, but are not limited to, a robot 100a, vehicles 100b-1 and 100b-2, an extended reality (XR) device 100c, a portable device 100d, a home appliance 100e, an IoT device 100f, and an artificial intelligence (AI) device / server (400). For example, the vehicles may include vehicles with wireless communication capabilities, autonomous vehicles, and vehicles capable of performing inter-vehicle communication. The vehicles may include unmanned aerial vehicles (UAVs) (e.g., drones). XR devices can include AR / VR / mixed reality (MR) devices and are implemented in the form of head-mounted devices (HMDs), head-up displays (HUDs) worn on vehicles, televisions, smartphones, computers, wearable devices, home appliances, digital signs, vehicles, robots, etc. Portable devices include smartphones, smart pads, wearable devices (e.g., smart watches or smart glasses) and computers (e.g., laptops). Home appliances include TVs, refrigerators, and washing machines. IoT devices include sensors and smart meters.

[0047] In this specification, the wireless devices 100a to 100f may be referred to as User Equipment (UE). The UE may include, for example, a mobile phone, a smartphone, a notebook computer, a digital broadcast terminal, a personal digital assistant (PDA), a portable multimedia player (PMP), a navigation system, a slate PC, a tablet PC, an ultrabook, a vehicle, a vehicle with an autonomous driving function, a connected automobile, a UAV, an AI module, a robot, an AR device, a VR device, an MR device, a hologram device, a public safety device, an MTC device, an IoT device, a medical device, a fintech device (or a financial device), a security device, a weather / environment device, a 5G service-related device, or a fourth industrial revolution-related device.

[0048] For example, a UAV is an aircraft without humans on board that navigates using radio control signals.

[0049] For example, a VR device may include a device for implementing an object or background of a virtual environment. For example, an AR device may include a device that implements an object or background of a virtual world by connecting it to an object or background of a real world. For example, an MR device may include a device that implements an object or background of a virtual world by merging it with an object or background of a real world. For example, a hologram device may include a device for implementing a 360-degree stereoscopic image by recording and reproducing stereoscopic information using the interference phenomenon of light that occurs when two laser lights called a hologram come together.

[0050] For example, public safety equipment may include image relay devices or imaging devices that may be worn on the user's body.

[0051] For example, MTC devices and IoT devices are devices that do not require direct human intervention or operation. For example, MTC devices and IoT devices can include smart meters, vending machines, thermometers, smart light bulbs, door locks, or various sensors.

[0052] For example, a medical device is a device used for the purposes of diagnosing, treating, mitigating, curing or preventing disease. For example, a medical device is a device used to diagnose, treat, mitigate or correct an injury or damage. For example, a medical device is a device used for the purposes of examining, replacing or modifying a structure or function. For example, a medical device is a device used for the purposes of fertility control. For example, medical devices may include therapeutic devices, driving devices, (in vitro) diagnostic devices, hearing aids or surgical devices.

[0053] For example, a security device is a device installed to prevent possible danger and maintain safety. For example, a security device can be a camera, a closed circuit TV (CCTV), a recorder, or a black box.

[0054] For example, a PAYG device is a device that can provide financial services such as mobile payments. For example, a PAYG device can include a payment device or a POS system.

[0055] For example, weather / environment devices may include devices that monitor or predict the weather / environment.

[0056] The wireless devices 100a to 100f are connected to a network 300 via a base station 200. AI technology can be applied to the wireless devices 100a to 100f, and the wireless devices 100a to 100f are connected to an AI server (400) via the network 300. The network 300 is configured using a 3G network, a 4G (e.g., LTE) network, a 5G (e.g., NR) network, a network beyond 5G, and the like. The wireless devices 100a to 100f can communicate with each other via the base station 200 / network 300, but can also communicate directly (e.g., sidelink communication) without going through the base station 200 / network 300. For example, vehicles (100b-1, 100b-2) can communicate directly (e.g., vehicle-to-vehicle (V2V) / vehicle-to-everything (V2X) communication). Also, IoT devices (e.g., sensors) can communicate directly with other IoT devices (e.g., sensors) or other wireless devices 100a to 100f.

[0057] Wireless communication / connections 150a, 150b, 150c are established between the wireless devices 100a-100f and / or between the wireless devices 100a-100f and the base station 200 and / or between the base stations 200. Here, the wireless communication / connections are established via various RATs (e.g., 5G NR) such as uplink / downlink communication 150a, sidelink communication 150b (or D2D (device-to-device) communication), inter-base station communication 150c (e.g., relay, IAB (integrated access and backhaul)), etc. Through the wireless communication / connections 150a, 150b, 150c, the wireless devices 100a-100f and the base station 200 can transmit / receive wireless signals to / from each other. For example, the wireless communication / connections 150a, 150b, 150c can transmit / receive signals via various physical channels. To this end, based on various proposals in this specification, at least some of the processes of setting various configuration information for transmitting / receiving wireless signals, various signal processing processes (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), and resource allocation processes are performed.

[0058] AI refers to the field that studies artificial intelligence or the methodology for creating it, while machine learning refers to the field that defines various problems to be dealt with in the field of artificial intelligence and studies the methodology for solving them. Machine learning can also be defined as an algorithm that improves its performance for a certain task through continuous experience with that task.

[0059] A robot can mean a machine that automatically processes or operates a task given to it using its own capabilities. In particular, a robot that has the ability to recognize the environment, make its own decisions, and execute its actions can be called an intelligent robot. Robots can be divided into industrial, medical, household, military, etc., depending on the purpose or field of use. Robots have a driving part including an actuator or a motor and can perform various physical actions such as moving the robot joints. In addition, a mobile robot has a driving part including wheels, brakes, propellers, etc., and can run on the ground or fly in the air using the driving part.

[0060] Autonomous driving refers to a technology that drives itself, and an autonomous vehicle refers to a vehicle that drives without user operation or with minimal user operation. For example, autonomous driving includes all technologies such as maintaining the lane while driving, automatically adjusting the speed like adaptive cruise control, automatically driving along a fixed route, and automatically setting a route and driving when a destination is set. Vehicles include vehicles equipped with only an internal combustion engine, hybrid vehicles equipped with both an internal combustion engine and an electric motor, and electric vehicles equipped with only an electric motor, and can include not only automobiles but also trains and motorcycles. An autonomous vehicle can be seen as a robot with an autonomous driving function.

[0061] Augmented reality is a general term for VR, AR, and MR. VR technology provides real-world objects and backgrounds only as CG images, AR technology provides virtual CG images on top of images of real objects, and MR technology is a CG technology that mixes and combines virtual objects in the real world. MR technology is similar to AR technology in that it displays both real and virtual objects. However, it differs in that while AR technology uses virtual objects to complement real objects, MR technology uses virtual objects and real objects as equals.

[0062] NR supports multiple numerologies or subcarrier spacings (SCS) to support various 5G services. For example, a 15kHz SCS supports wide areas in traditional cellular bands, a 30kHz / 60kHz SCS supports dense urban areas, lower latency and wider carrier bandwidths, and a 60kHz or higher SCS supports bandwidths greater than 24.25GHz to overcome phase noise.

[0063] Here, the wireless communication technology implemented in the wireless device of this specification can include not only LTE, NR, and 6G but also narrowband IoT (NB-IoT, narrowband IoT) for low power communication. For example, NB-IoT technology is an example of LPWAN (low power wide area network) technology, and is implemented in standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the above-mentioned names. Additionally or alternatively, the wireless communication technology implemented in the wireless device of this specification can perform communication based on LTE-M technology. For example, LTE-M technology is an example of LPWAN technology, and can be called various names such as eMTC (enhanced MTC). For example, LTE-M technology is implemented in at least one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-bandwidth limited), 5) LTE-MTC, 6) LTE MTC, and / or 7) LTE M, and is not limited to the above-mentioned names. Additionally or alternatively, the wireless communication technology implemented in the wireless device of this specification may include at least one of ZigBee, Bluetooth (registered trademark), and / or LPWAN, which consider low-power communication, but are not limited to the above names. For example, ZigBee technology can generate personal area networks (PANs) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and may be called by various names.

[0064] FIG. 2 illustrates an example of a wireless device in which the implementation of this specification may be applied.

[0065] Referring to FIG. 2, a first wireless device 100 and a second wireless device 200 can transmit and receive wireless signals to / from an external device via various RATs (e.g., LTE and NR).

[0066] In FIG. 2, {first radio device 100 and second radio device 200} may correspond to at least one of {radio devices 100a-100f and base station 200}, {radio devices 100a-100f and radio devices 100a-100f} and / or {base station 200 and base station 200} in FIG. 1.

[0067] First wireless device 100 may include at least one transceiver, such as transceiver 106 , at least one processing chip, such as processing chip 101 , and / or one or more antennas 108 .

[0068] The processing chip 101 may include at least one processor, such as processor 102, and at least one memory, such as memory 104. In Figure 2, the memory 104 is illustratively shown included in the processing chip 101. Additionally and / or alternatively, the memory 104 may be located external to the processing chip 101.

[0069] The processor 102 may control the memory 104 and / or the transceiver 106 and may be configured to implement the descriptions, functions, procedures, suggestions, methods and / or operational flow diagrams disclosed herein. For example, the processor 102 may process information in the memory 104 to generate a first information / signal and transmit a wireless signal including the first information / signal via the transceiver 106. The processor 102 may receive a wireless signal including a second information / signal via the transceiver 106 and process the second information / signal to store information in the memory 104.

[0070] The memory 104 is operatively connected to the processor 102. The memory 104 may store various types of information and / or instructions. The memory 104 may store software code 105 that, when executed by the processor 102, implements instructions that perform the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed herein. For example, the software code 105, when executed by the processor 102, may implement instructions that perform the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed herein. For example, the software code 105 may control the processor 102 to execute one or more protocols. For example, the software code 105 may control the processor 102 to execute one or more air interface protocol layers.

[0071] Here, the processor 102 and memory 104 are part of a communication modem / circuit / chip designed to implement a RAT (e.g., LTE or NR). A transceiver 106 is connected to the processor 102 and can transmit and / or receive wireless signals via one or more antennas 108. Each transceiver 106 can include a transmitter and / or a receiver. The transceiver 106 is used interchangeably with a radio frequency (RF) unit. In this specification, the first wireless device 100 can refer to a communication modem / circuit / chip.

[0072] The second wireless device 200 may include at least one transceiver, such as transceiver 206, at least one processing chip, such as processing chip 201, and / or one or more antennas 208).

[0073] Processing chip 201 may include at least one processor, such as processor 202, and at least one memory, such as memory 204. Memory 204 is illustratively shown included in processing chip 201. Additionally and / or alternatively, memory 204 may be located external to processing chip 201.

[0074] The processor 202 may control the memory 204 and / or the transceiver 206 and may be configured to implement the descriptions, functions, procedures, suggestions, methods and / or operational flow diagrams disclosed herein. For example, the processor 202 may process information in the memory 204 to generate a third information / signal and transmit a wireless signal including the third information / signal via the transceiver 206. The processor 202 may receive a wireless signal including a fourth information / signal via the transceiver 206 and store information obtained by processing the fourth information / signal in the memory 204.

[0075] The memory 204 is operatively connected to the processor 202. The memory 204 may store various types of information and / or instructions. The memory 204 may store software code 205 that, when executed by the processor 202, implements instructions that perform the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed herein. For example, the software code 205, when executed by the processor 202, may implement instructions that perform the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed herein. For example, the software code 205 may control the processor 202 to execute one or more protocols. For example, the software code 205 may control the processor 202 to execute one or more air interface protocol layers.

[0076] Here, the processor 202 and memory 204 are part of a communication modem / circuit / chip designed to implement a RAT (e.g., LTE or NR). The transceivers 206 are connected to the processor 202 and can transmit and / or receive radio signals via one or more antennas 208). Each transceiver 206 can include a transmitter and / or a receiver. The transceivers 206 are used interchangeably with the RF section. In this specification, the second wireless device 200 can refer to a communication modem / circuit / chip.

[0077] The hardware elements of the wireless device 100, 200 are described in more detail below. One or more protocol layers may be implemented by one or more processors 102, 202, without limitation. For example, one or more processors 102, 202 may implement one or more layers (e.g., functional layers such as a physical (PHY) layer, a media access control (MAC) layer, a radio link control (RLC) layer, a packet data convergence protocol (PDCP) layer, a radio resource control (RRC) layer, and a service data adaptation protocol (SDAP) layer). One or more processors 102, 202 may generate one or more protocol data units (PDUs) and / or one or more service data units (SDUs) according to the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed herein. One or more processors 102, 202 may generate messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed herein. The one or more processors 102, 202 can generate and provide signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data or information to one or more transceivers 106, 206 according to the descriptions, functions, procedures, suggestions, methods and / or operational flow diagrams disclosed herein. The one or more processors 102, 202 can receive signals (e.g., baseband signals) from the one or more transceivers 106, 206 and obtain PDUs, SDUs, messages, control information, data or information according to the descriptions, functions, procedures, suggestions, methods and / or operational flow diagrams disclosed herein.

[0078] The one or more processors 102, 202 may be referred to as controllers, microcontrollers, microprocessors, and / or microcomputers. The one or more processors 102, 202 may be implemented using hardware, firmware, software, and / or a combination thereof. As an example, the one or more processors 102, 202 may include one or more application specific integrated circuits (ASICs), one or more digital signal processors (DSPs), one or more digital signal processing devices (DSPDs), one or more programmable logic devices (PLDs), and / or one or more field programmable gate arrays (FPGAs). The descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed herein may be implemented using firmware and / or software, and the firmware and / or software may be implemented to include modules, procedures, and / or functions. Firmware or software configured to execute the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed herein may be included in the one or more processors 102, 202 or may be stored in one or more memories 104, 204 and executed by the one or more processors 102, 202. The descriptions, functions, procedures, suggestions, methods and / or operational flow diagrams disclosed herein may be implemented using firmware or software in the form of code, instructions and / or collections of instructions.

[0079] The one or more memories 104, 204 may be coupled to the one or more processors 102, 202 and may store various forms of data, signals, messages, information, programs, code, instructions, and / or commands. The one or more memories 104, 204 may be comprised of read-only memory (ROM), random access memory (RAM), erasable programmable ROM (EPROM), flash memory, hard drives, registers, cache memory, computer readable storage media, and / or combinations thereof. The one or more memories 104, 204 may be located internal and / or external to the one or more processors 102, 202. Additionally, the one or more memories 104, 204 may be coupled to the one or more processors 102, 202 via various technologies, such as wired or wireless access.

[0080] One or more transceivers 106, 206 may transmit user data, control information, wireless signals / channels, etc., as referred to in the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed herein to one or more other devices. One or more transceivers 106, 206 may receive user data, control information, wireless signals / channels, etc., as referred to in the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed herein from one or more other devices. For example, one or more transceivers 106, 206 may be coupled to one or more processors 102, 202 to transmit and receive wireless signals. For example, one or more processors 102, 202 may control one or more transceivers 106, 206 to transmit user data, control information, wireless signals, etc., to one or more other devices. Also, one or more processors 102, 202 may control one or more transceivers 106, 206 to receive user data, control information, wireless signals, etc., from one or more other devices.

[0081] The one or more transceivers 106, 206 are coupled to one or more antennas 108, 208. The one or more transceivers 106, 206 are configured to transmit and receive user data, control information, wireless signals / channels, etc., as referred to in the descriptions, functions, procedures, suggestions, methods and / or operational flow diagrams disclosed herein via the one or more antennas 108, 208. As used herein, the one or more antennas 108, 208 may be multiple physical antennas or multiple logical antennas (e.g., antenna ports).

[0082] One or more transceivers 106, 206 can convert received user data, control information, radio signals / channels, etc., in RF band signals to baseband signals for processing by one or more processors 102, 202. One or more transceivers 106, 206 can convert processed user data, control information, radio signals / channels, etc., in baseband signals to RF band signals by one or more processors 102, 202. To this end, one or more transceivers 106, 206 can include an (analog) oscillator and / or a filter. For example, one or more transceivers 106, 206 can up-convert an OFDM baseband signal to an OFDM signal via an (analog) oscillator and / or a filter under the control of one or more processors 102, 202 and transmit the up-converted OFDM signal at a carrier frequency. One or more transceivers 106, 206 can receive OFDM signals at a carrier frequency and down-convert the OFDM signals to OFDM baseband signals via (analog) oscillators and / or filters under the control of one or more processors 102, 202.

[0083] In the implementation of the present specification, a UE can operate from an uplink (UL) to a transmitter and from a downlink (DL) to a receiver. In the implementation of the present specification, a base station can operate from the UL to a receiver and from the DL to a transmitter. In the following, for convenience of explanation, it is mainly assumed that the first wireless device 100 operates as a UE and the second wireless device 200 operates as a base station. For example, a processor 102 connected to, mounted on, or launched in the first wireless device 100 is configured to perform UE operations according to the implementation of the present specification or to control the transceiver 106 to perform UE operations according to the implementation of the present specification. A processor 202 connected to, mounted on, or launched in the second wireless device 200 is configured to perform base station operations according to the implementation of the present specification or to control the transceiver 206 to perform base station operations according to the implementation of the present specification.

[0084] In this specification, a base station may be referred to as a Node B, an eNode B (eNB), or a gNB.

[0085] FIG. 3 illustrates an example of a wireless device to which the implementation of this specification may be applied.

[0086] The wireless device can be implemented in different ways depending on the use case / service (see Figure 1).

[0087] Referring to Fig. 3, the wireless devices 100, 200 may correspond to the wireless devices 100, 200 of Fig. 2 and are composed of various components, devices / portions and / or modules. For example, each wireless device 100, 200 may include a communication device 110, a control device 120, a memory device 130 and additional components 140. The communication device 110 may include a communication circuit 112 and a transceiver 114. For example, the communication circuit 112 may include one or more processors 102, 202 of Fig. 2 and / or one or more memories 104, 204 of Fig. 2. For example, the transceiver 114 may include one or more transceivers 106, 206 of Fig. 2 and / or one or more antennas 108, 208 of Fig. 2. The control device 120 is electrically connected to the communication device 110, the memory device 130 and the additional components 140 and controls the overall operation of each wireless device 100, 200. For example, the controller 120 can control the electrical / mechanical operation of each of the wireless devices 100, 200 based on the programs / codes / instructions / information stored in the memory device 130. The controller 120 can transmit information stored in the memory device 130 to the outside (e.g., other communication devices) through the communication device 110 via the wireless / wired interface, or store information received from the outside (e.g., other communication devices) through the communication device 110 via the wireless / wired interface in the memory device 130.

[0088] The additional component 140 may be configured in various ways depending on the type of the wireless device 100, 200. For example, the additional component 140 may include at least one of a power unit / battery, an input / output (I / O) device (e.g., an audio I / O port, a video I / O port), a drive unit, and a computing device. The wireless device 100, 200 may be implemented in the form of, but is not limited to, a robot (100a in FIG. 1), a vehicle (100b-1 and 100b-2 in FIG. 1), an XR device (100c in FIG. 1), a portable device (100d in FIG. 1), a home appliance (100e in FIG. 1), an IoT device (100f in FIG. 1), a digital broadcasting terminal, a hologram device, a public safety device, an MTC device, a medical device, a fintech device (or a financial device), a security device, a climate / environment device, an AI server / device (400 in FIG. 1), a base station (200 in FIG. 1), or a network node. The wireless devices 100, 200 can be used in mobile or fixed locations depending on the use case / service.

[0089] In FIG. 3, the various components, devices / portions and / or modules of the wireless devices 100, 200 are connected to each other via wired interfaces or at least partially connected wirelessly via the communication device 110. For example, in each of the wireless devices 100, 200, the control device 120 and the communication device 110 are connected via wires, and the control device 120 and the first device (e.g., 130 and 140) are connected wirelessly via the communication device 110. Each of the components, devices / portions and / or modules in the wireless devices 100, 200 may further include one or more elements. For example, the control device 120 may be configured by a set of one or more processors. As an example, the control device 120 may be configured by a set of a communication control processor, an application processor (AP), an electronic control unit (ECU), a graphics processing unit and a memory control processor. As another example, the memory device 130 may be configured by a RAM, a DRAM, a ROM, a flash memory, a volatile memory, a non-volatile memory and / or a combination thereof.

[0090] FIG. 4 shows an example of a 5G system architecture to which the implementation of this specification may be applied.

[0091] The 5G system (5GS) structure consists of the following network functions (NFs):

[0092] -AUSF(Authentication Server Function)

[0093] -AMF(Access and Mobility Management Function)

[0094] -DN (Data Network), e.g., carrier services, Internet connection or other company services

[0095] -USDF(Unstructured Data Storage Function)

[0096] -NEF(Network Exposure Function)

[0097] -I-NEF (Intermediate NEF)

[0098] -NRF(Network Repository Function)

[0099] -NSSF(Network Slice Selection Function)

[0100] -PCF (Policy Control Function)

[0101] -SMF(Session Management Function)

[0102] -UDM (Unified Data Management)

[0103] -UDR (Unified Data Repository)

[0104] - UPF (User Plane Function)

[0105] -UCMF(UE radio Capability Management Function)

[0106] -AF (Application Function)

[0107] -UE (User Equipment)

[0108] -(R)AN ((Radio)Access Network)

[0109] -5G-EIR(5G-Equipment Identity Register)

[0110] -NWDAF(Network Data Analytics Function)

[0111] -CHF (CHarging Function)

[0112] Additionally, the following network functions may be considered:

[0113] -N3IWF (Non-3GPP Inter Working Function)

[0114] -TNGF(Trusted Non-3GPP Gateway Function)

[0115] -W-AGF(Wireline Access Gateway Function)

[0116] Figure 4 shows a 5G system architecture for a non-roaming case using a reference point representation showing how various network functions interact with each other.

[0117] For clarity of the point-to-point diagram in Figure 4, the UDSF, NEF and NRF have not been illustrated, but all of the network functions shown can interact with the UDSF, UDR, NEF and NRF as necessary.

[0118] For clarity, the connections between the UDR and other NFs (e.g., PCFs) are not shown in Figure 4. For clarity, the connections between the NWDAF and other NFs (e.g., PCFs) are not shown in Figure 4.

[0119] The 5G system structure includes the following reference points:

[0120] N1: Reference point between the UE and the AMF.

[0121] -N2: Reference point between (R)AN and AMF.

[0122] -N3: Reference point between (R)AN and UPF.

[0123] - N4: Reference point between SMF and UPF.

[0124] -N6: Reference point between the UPF and the data network.

[0125] - N9: Reference point between two UPFs.

[0126] The following reference points indicate the interactions that exist between NF services in an NF.

[0127] -N5: Reference point between PCF and AF.

[0128] - N7: Reference point between SMF and PCF.

[0129] -N8: Reference point between UDM and AMF.

[0130] - N10: Reference point between UDM and SMF.

[0131] - N11: Reference point between AMF and SMF.

[0132] -N12: Reference point between AMF and AUSF.

[0133] -N13: Reference point between UDM and AUSF.

[0134] - N14: Reference point between two AMFs.

[0135] -N15: Indicates the reference point between the PCF and the AMF in a non-roaming scenario, and the reference point between the AMF and the PCF of the visited network in a roaming scenario.

[0136] -N16: Reference point between two SMFs (in case of roaming, between the SMF of the visited network and the SMF of the home network)

[0137] -N22: Reference point between AMF and NSSF.

[0138] -N30: Reference point between PCF and NEF.

[0139] -N33: Reference point between AF and NEF.

[0140] In some cases, two NFs may be interconnected to serve a UE.

[0141] For reference, in Figure 4, AF by a third party other than the operator can connect to 5GC via NEF.

[0142] FIG. 5 is another exemplary diagram showing the structure of a radio interface protocol between a UE and a gNB.

[0143] The radio interface protocol is based on the 3GPP radio access network standard. The radio interface protocol is horizontally composed of a physical layer, a data link layer, and a network layer, and vertically divided into a user plane for transmitting data information and a control plane for transmitting signaling.

[0144] The protocol layers are divided into L1 (layer 1), L2 (layer 2), and L3 (layer 3) based on the lower three layers of the Open System Interconnection (OSI) reference model, which is widely known in communication systems.

[0145] Each layer of the wireless protocol will now be described.

[0146] The first layer, the physical layer, provides an information transfer service using a physical channel. The physical layer is connected to the higher level medium access control layer via a transport channel, and data is transferred between the medium access control layer and the physical layer via the transport channel. Data is transferred between different physical layers, i.e., between the physical layers of the transmitting side and the receiving side, via the physical channel.

[0147] The second layer includes a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer.

[0148] Layer 3 includes radio resource control (RRC). The RRC layer is defined only in the control plane and is responsible for controlling logical channels, transmission channels, and physical channels in relation to the establishment, re-establishment, and release of radio bearers (RBs). Here, RBs refer to services provided by layer 2 for data transmission between a terminal and E-UTRAN.

[0149] The NAS (Non-Access Stratum) layer performs functions such as session management and mobility management.

[0150] The NAS layer is divided into a NAS entity for Mobility Management (MM) and a NAS entity for session management (SM).

[0151] 1) A NAS entity for MM typically provides the following functions:

[0152] NAS procedures related to AMF include:

[0153] - Registration management and connection management procedures. AMF supports the following functions:

[0154] - Secure NAS signal connection between UE and AMF (integrity protection, encryption)

[0155] 2) The NAS entity for SM performs session management between the UE and the SMF.

[0156] SM signaling messages are processed, i.e. generated and processed, in the NAS-SM layer of the UE and the SMF. The content of SM signaling messages is not interpreted by the AMF.

[0157] - For SM signaling transmission,

[0158] The NAS entity for MM generates a NAS-MM message that guides the method and location of transmitting the SM signaling message via a security header indicating the NAS transmission of the SM signaling and additional information for the receiving NAS-MM.

[0159] Upon receiving SM signaling, the NAS entity for SM performs an integrity check on the NAS-MM message and interprets additional information to guide how and where to derive the SM signaling message.

[0160] On the other hand, the RRC layer, RLC layer, MAC layer, and PHY layer located below the NAS layer in FIG. 5 can be collectively called the Access Stratum (AS).

[0161] A network system (i.e., 5GC) for next-generation mobile communications (i.e., 5G) also supports non-3GPP access. A representative example of the non-3GPP access is WLAN access. The WLAN access may include both trusted WLAN and untrusted WLAN.

[0162] In the 5G system, the AMF performs registration management (RM) and connection management (CM) for not only 3GPP access but also non-3GPP access.

[0163] A Multi-Access (MA) PDU session that utilizes both 3GPP and non-3GPP accesses can be used.

[0164] An MA PDU session is a PDU session that can simultaneously serve 3GPP access and non-3GPP access using one PDU session.

[0165] <Registration Procedure>

[0166] The registration procedure is described below. Please refer to Section 4.2.2.2 of 3GPP TS 23.502 V16.3.0(2019-12).

[0167] 6a and 6b show an example of a registration procedure to which the implementation of this specification can be applied.

[0168] A UE needs to register with the network to receive services, activate mobility tracking, and activate reachability. The UE initiates the registration procedure using one of the following registration types:

[0169] -initial registration for 5GS; or

[0170] -mobility registration update; or

[0171] -periodic registration update; or

[0172] -Emergency registration

[0173] The general registration procedure of Figures 6a and 6b applies to all registration procedures described above, however, periodic registration updates do not necessarily include all parameters used in the other registration procedures.

[0174] The general registration procedure of Figures 6a and 6b may be used to register for a 3GPP connection when the UE is already registered for a non-3GPP connection, or vice versa. When the UE is already registered for a non-3GPP connection scenario, an AMF change may be required to register for a 3GPP connection.

[0175] First, the procedure of FIG. 6a will be described.

[0176] (1) Step 1: The UE sends a Registration Request message to the (R)AN. The Registration Request message corresponds to an AN message.

[0177] The registration request message may include AN parameters. In the case of NG-RAN, the AN parameters include, for example, a 5G SAE temporary mobile subscriber identity (5G-S-TMSI) or globally unique AMF ID (GUAMI), a selected public and mobile network (PLMN) ID (or PLMN ID and network identifier (NID)), and a requested network slice selection assistance information (NSSAI). The AN parameters also include an establishment cause. The establishment cause provides the reason for requesting establishment of an RRC connection. Whether and how the UE includes the requested NSSAI as part of the AN parameters depends on the value of the Access Stratum connection establishment NSSAI inclusion mode parameter.

[0178] The registration request message may include a registration type, which indicates whether the UE wants to perform an initial registration (i.e., the UE is in the RM-DEREGISTERED state), or a mobility registration update (i.e., the UE is in the RM-REGISTERED state and initiates a registration procedure because the UE moves, or the UE wants to update capabilities or protocol parameters, or requests a change in the set of network slices that the UE is authorized to use), or a periodic registration update (i.e., the UE is in the RM-REGISTERED state and initiates a registration procedure due to expiration of a periodic registration update timer), or an emergency registration (i.e., the UE is in a limited service state).

[0179] When the UE performs initial registration, the UE indicates the UE ID in the registration request message as follows:

[0180] i) if the UE has a valid evolved packet system (EPS) globally unique temporary identifier (GUTI), the 5G-GUTI mapped in the EPS GUTI;

[0181] ii) The native 5G-GUTI (if available) assigned by the PLMN to which the UE is attempting to register;

[0182] iii) A native 5G-GUTI assigned by a PLMN equivalent to the PLMN to which the UE is attempting to register;

[0183] iv) Native 5G-GUTI allocated by other PLMNs (if available);

[0184] v) Otherwise, the UE includes a subscriber concealed identifier (SUCI) in the registration request message.

[0185] If the UE performing initial registration has all valid EPS GUTIs and native 5G-GUTIs, the UE shall also indicate the native 5G-GUTI in the additional GUTI. If one or more native 5G-GUTIs are available, the UE shall select a 5G-GUTI from items (ii)-(iv) in the list in the order of decreasing priority.

[0186] When the UE performs initial registration to the native 5G-GUTI, the UE indicates the related GUAMI information in the AN parameters. When the UE performs initial registration to the SUCI, the UE does not indicate the GUAMI information in the AN parameters.

[0187] In case of emergency registration, if the UE does not have a valid 5G-GUTI, the SUCI is included, if the UE does not have a subscriber permanent identifier (SUPI) and does not have a valid 5G-GUTI, the PEI is included. In other cases, the 5G-GUTI is included, which indicates the last serving AMF.

[0188] The registration request message may also include security parameters, PDU session status, etc. The security parameters are used for authentication and integrity protection. The PDU session status indicates a previously established PDU session in the UE. When the UE is connected to two AMFs belonging to different PLMNs through a 3GPP connection and a non-3GPP connection, the PDU session status indicates a currently established PDU session in the PLMN in the UE.

[0189] (2) Step 2: (R)AN selects an AMF.

[0190] If 5G-S-TMSI or GUAMI was not included or if 5G-S-TMSI or GUAMI does not indicate a valid AMF, the (R)AN selects an AMF based on the (R)AT and requested NSSAI, if available.

[0191] If the UE is in the CM-CONNECTED state, the (R)AN can transmit a registration request message to the AMF based on the UE's N2 connection.

[0192] If the (R)AN cannot select an appropriate AMF, the (R)AN transmits a registration request message to an AMF configured in the (R)AN to perform AMF selection.

[0193] (3) Step 3: (R)AN sends a registration request message to the new AMF. The registration request message corresponds to the N2 message.

[0194] The registration request message may include all and / or part of the information included in the registration request message received from the UE described in step 1.

[0195] The registration request message may include an N2 parameter. When NG-RAN is used, the N2 parameter includes the selected PLMN ID (or PLMN ID and NID), location information and cell ID related to the cell on which the UE is camped, and a UE context request indicating that a UE context needs to be established in the NG-RAN, including security information. When NG-RAN is used, the N2 parameter also includes an establishment cause.

[0196] If the registration type indicated by the UE is periodic registration update, steps 4-19 described below can be omitted.

[0197] (4) Step 4: If the UE's 5G-GUTI is included in the registration request message and the serving AMF has changed since the last registration procedure, the new AMF can include a full registration request NAS (non-Access Stratum) message to request the UE's SUPI and UE context to the previous AMF. It can invoke the Namf_Communication_UEContextTransfer service operation.

[0198] (5) Step 5: The previous AMF can respond to the Namf_Communication_UEContextTransfer call to the new AMF, including the UE's SUPI and UE context.

[0199] (6) Step 6: If the SUCI is not provided by the UE or is not retrieved in the previous AMF, the new AMF may initiate an identity request procedure by sending an Identity Request message to the UE to request the SUCI.

[0200] (7) Step 7: The UE may respond with an IdentityResponse message containing the SUCI. The UE derives the SUCI using the provided public key of the Home PLMN (HPLMN).

[0201] (8) Step 8: The new AMF may decide to call the AUSF to initiate UE authentication. In this case, the new AMF selects the AUSF based on the SUPI or SUCI.

[0202] (9) Step 9: Authentication / security is established by the UE, the new AMF, the AUSF and / or the UDM.

[0203] (10) Step 10: If the AMF is changed, the new AMF can call the Namf_Communication_RegistrationCompleteNotify service operation to inform the previous AMF that the UE registration to the new AMF is complete. If the authentication / security procedure fails, the registration is rejected and the new AMF can call the Namf_Communication_RegistrationCompleteNotify service operation with a reject indication reason code to the previous AMF. The previous AMF can continue as if the UE context transfer service operation was not received.

[0204] (11) Step 11: If the PEI has not been provided by the UE or has not been retrieved in the previous AMF, the new AMF may initiate an identity request procedure by sending an Identity Request message to the UE to retrieve the PEI from the UE. The PEI is sent encrypted unless the UE performs emergency registration and cannot be authenticated.

[0205] (12) Step 12: Optionally, the new AMF may initiate a MEID check by calling the N5g-eir_EquipmentIdentityCheck_Get service operation.

[0206] The procedure of FIG. 6b, which follows that of FIG. 6a, will now be described.

[0207] (13) Step 13: When performing the following step 14, the new AMF can select a UDM based on the SUPI, and the UDM can select a UDR instance.

[0208] (14) Step 14: The new AMF can register with the UDM.

[0209] (15) Step 15: The new AMF can select a PCF.

[0210] (16) Step 16: The new AMF can selectively perform AM policy association establishment / modification.

[0211] (17) Step 17: The new AMF may send an update / release SM context message (e.g., Nsmf_PDU session_UpdateSMContext and / or Nsmf_PDU session_ReleaseSMContext) to the SMF.

[0212] (18) Step 18: If the new AMF and the previous AMF are in the same PLMN, the new AMF may send a UE context modification request to the N3IWF / TNGF / W-AGF.

[0213] (19) Step 19: The N3IWF / TNGF / W-AGF may send a UE context modification response to the new AMF.

[0214] (20) Step 20: After the new AMF receives the response message from the N3IWF / TNGF / W-AGF in step 19, the new AMF can register to the UDM.

[0215] (21) Step 21: The new AMF sends a Registration accept message to the UE.

[0216] The new AMF sends a registration accept message to the UE indicating that the registration request has been accepted. If the new AMF assigns a new 5G-GUTI, the 5G-GUTI is included. If the UE is already in RM-REGISTERED state through another connection in the same PLMN, the UE uses the 5G-GUTI received in the registration accept message for both registrations. If the registration accept message does not include the 5G-GUTI, the UE uses the 5G-GUTI assigned to the existing registration for the new registration. If the new AMF assigns a new registration area, it sends the registration area to the UE via the registration accept message. If there is no registration area in the registration accept message, the UE considers the previous registration area to be valid. Mobility Restrictions are included when mobility restrictions are applied to the UE and the registration type is not emergency registration. The new AMF indicates the established PDU sessions to the UE in the PDU session state. The UE locally removes internal resources related to PDU sessions that are not indicated as established in the received PDU session state. If a UE is connected to two AMFs belonging to different PLMNs via a 3GPP connection and a non-3GPP connection, the UE locally removes internal resources associated with PDU sessions of the current PLMN that are not indicated as established in the received PDU session status. If the PDU session status information is in the registration accept message, the new AMF indicates the PDU session status to the UE.

[0217] The Allowed NSSAI provided in the Registration Accept message is valid for the registration area and applies to all PLMNs with tracking areas included in the registration area. Mapping of Allowed NSSAI is mapping of HPLMNS-NSSAI to each Single Network Slice Selection Assistance Information (S-NSSAI) of the Allowed NSSAI. Mapping of Configured NSSAI is mapping of HPLMNS-NSSAI to each S-NSSAI of the Configured NSSAI for the Serving PLMN.

[0218] In addition, the new AMF optionally performs UE policy association establishment.

[0219] (22) Step 22: If the UE successfully updates itself, it can send a Registration Complete message to the new AMF.

[0220] The UE may send a registration completion message to the new AMF to check whether a new 5G-GUTI has been assigned.

[0221] (23) Step 23: In the case of registration via 3GPP connection, if the new AMF does not release the signaling connection, the new AMF can send RRC Inactive Assistance information to the NG-RAN. In the case of registration via non-3GPP connection, if the UE is in CM-CONTENED state on the 3GPP connection, the new AMF can send RRC Inactive Assistance information to the NG-RAN.

[0222] (24) Step 24: The AMF can perform information updates to the UDM.

[0223] (25) Step 25: The UE can perform network slice-specific authentication and authorization (NSSAA) procedures.

[0224] <PDU Session Establishment Procedure>

[0225] The PDU session establishment procedure will be described. Reference can be made to Section 4.3.2 of 3GPP TS23.502 V16.3.0 (2019-12).

[0226] Figures 7a and 7b show examples of PDU session establishment procedures to which the implementation in this specification applies.

[0227] PDU session establishment then applies to the following:

[0228] - The PDU session establishment procedure disclosed by the UE

[0229] - The PDU session handover between 3GPP and non-3GPP disclosed by the UE

[0230] - The PDU session handover from EPS to 5GS in the UE

[0231] - The PDU session establishment procedure triggered by the network

[0232] A PDU session can be associated with (a) a single connection type, i.e., either a 3GPP connection or a non-3GPP connection, at a given time, or (b) multiple connection types simultaneously, i.e., one 3GPP connection and one non-3GPP connection. A PDU session associated with multiple connection types is called a multiaccess (MA) PDU session and can be requested by an access traffic steering, switching, splitting (ATSSS)-supported UE.

[0233] 7a and 7b show procedures for establishing a PDU session associated with a single connection type at a given time.

[0234] In the procedures shown in Figures 7a and 7b, it is assumed that the AMF has already retrieved the user subscription data in the UDM, unless the UE is emergency registered because the UE is already registered to the AMF.

[0235] (1) Step 1: To establish a new PDU session, the UE generates a new PDU session ID.

[0236] The UE initiates the UE requested PDU session establishment procedure by sending a NAS message containing a PDU session establishment request message in an N1SM container. The PDU session establishment request message includes a PDU session ID, a requested PDU session type, a requested session and service continuity (SSC) mode, 5GSM capabilities, Protocol Configuration Options (PCO), an SM PDU DN Request Container, and an UE Integrity protection Maximum Data Rate.

[0237] If the PDU session establishment is a request to establish a new PDU session, the request type indicates "Initial Request". If the request refers to an existing PDU session that is switched between a 3GPP connection and a non-3GPP connection, or a PDU session handover from an existing PDN (packet Data Network) connection in the EPC, the request type indicates "Existing PDU session". If the PDU session establishment is a request to establish a PDU session for an emergency service, the request type indicates "Emergency Request". If the request refers to an existing PDU session for an emergency service that is switched between a 3GPP connection and a non-3GPP connection, or a PDU session handover from an existing PDN connection for emergency services in the EPC, the request type indicates "Existing Emergency PDU session".

[0238] The UE includes the S-NSSAI from the allowed NSSAI of the current connection type. If the Mapping Of Allowed NSSAI is provided to the UE, the UE provides the S-NSSAI of the visited VPLMN (VPLMN) from the allowed NSSAI and the corresponding S-NSSAI of the HPLMN from the mapping of the allowed NSSAI.

[0239] (2) Step 2: The AMF selects an SMF. If the request type indicates "initial request" or the request is for handover from an EPS or a non-3GPP connection provided by another AMF, the AMF stores the S-NSSAI(s) associated with the PDU session, the DNN (Data Network name), the PDU session ID, and the SMF ID, as well as the connection type of the PDU session.

[0240] If the request type is "initial request" and a previous PDU session ID indicating an existing PDU session was also included in the message, the AMF selects an SMF and stores the new PDU session ID, the S-NSAI(s) and the connection for the selected SMF ID.

[0241] If the request type indicates an "existing PDU session", the AMF selects an SMF based on the SMF-ID received in the UDM. The AMF updates the stored connection type for the PDU session.

[0242] If the request type indicates "existing PDU session" referring to an existing PDU session moving between a 3GPP connection and a non-3GPP connection, and if the serving PLMNS-NSSAI of the PDU session is present in the allowed NSSAI of the target connection type, the PDU session establishment procedure may be performed if:

[0243] - if the SMF ID and AMF corresponding to the PDU session ID belong to the same PLMN;

[0244] - if the SMF ID corresponding to the PDU session ID belongs to the HPLMN;

[0245] If not, the AMF rejects the PDU session establishment request with an appropriate rejection cause.

[0246] The AMF shall reject any request from an emergency registered UE whose request type does not indicate "emergency request" or "existing emergency PDU session".

[0247] (3) Step 3: If the AMF is not associated with an SMF for the PDU session ID it provides in the UE (e.g., when the request type indicates "initial request"), the AMF invokes a create SM context request procedure (e.g., Nsmf_PDU session_CreateSMContextRequest). If the AMF is already associated with an SMF for the PDU session ID it provides in the UE (e.g., when the request type indicates "existing PDU session"), the AMF invokes an update SM context request procedure (e.g., Nsmf_PDU session_UpdateSMContextRequest).

[0248] The AMF sends the S-NSSAI of the serving PLMN from the allowed NSSAI to the SMF. For local break out (LBO) roaming scenario, the AMF also sends the corresponding S-NSSAI of the HPLMN from the mapping of the allowed NSSAI to the SMF.

[0249] The AMF ID is the GUAMI of the UE and uniquely identifies the AMF serving the UE. The AMF conveys the PDU session ID together with the N1SM container containing the PDU session establishment request message received from the UE. The GPSI (generic public subscription identifier) ​​is included if available in the AMF.

[0250] If a UE in limited service state does not provide a SUPI and is registered for emergency services, the AMF provides a PEI instead of the SUPI. If a UE in limited service state provides a SUPI and is registered for emergency services but is not authenticated, the AMF indicates that the SUPI is not authenticated. If the SMF does not receive a SUPI from the UE or the AMF indicates that the SUPI is not authenticated, the UE is determined to be not authenticated.

[0251] The AMF may include a PCF ID in the Nsmf_PDU session_CreateSMContext, which identifies the home PCF (H-PCF) in the non-roaming case and the visited PCF (V-PCF) in the LBO roaming case.

[0252] (4) Step 4: If the session management subscription data for the corresponding SUPI, DNN, and S-NSSAI of the HPLMN is not available, the SMF can retrieve the session management subscription data in the UDM and is notified when this subscription data is modified.

[0253] (5) Step 5: The SMF sends a create SM context response message (e.g., Nsmf_PDU session_CreateSMContextResponse) or an update SM context response message (e.g., Nsmf_PDU session_UpdateSMContextResponse) to the AMF depending on the request received in step 3.

[0254] If the SMF receives Nsmf_PDU session_CreateSMContextRequest in step 3 and is able to process the PDU session establishment request, the SMF creates an SM context and responds to the AMF by providing an SM context ID.

[0255] If the SMF decides not to accept the PDU session establishment, it rejects the UE request via a NASSM signal containing the associated SM rejection cause by responding to the AMF with a Nsmf_PDU session_CreateSMContextResponse. The SMF also indicates to the AMF that the PDU session ID is considered released and the PDU session establishment procedure is aborted, with the SMF proceeding to step 20 below.

[0256] (6) Step 6: Selective secondary authentication / authorization is performed.

[0257] (7a) Step 7a: If dynamic policy and charging control (PCC) is used for the PDU session, the SMF may perform PCF selection.

[0258] (7b) Step 7b: The SMF executes the SM policy association establishment procedure to establish an SM policy association with the PCF, and basic PCC rules for the PDU session are obtained.

[0259] (8) Step 8: The SMF selects one or more UPFs.

[0260] (9) Step 9: The SMF may provide information on the policy control request trigger condition that was met by executing the SMF exposed SM policy related remediation procedures.

[0261] (10) Step 10: If the request type indicates an "initial request", the SMF may initiate an N4 Session Establishment procedure with the selected UPF. Otherwise, the SMF may initiate an N4 Session Modification procedure with the selected UPF.

[0262] In step 10a, the SMF can send an N4 session establishment / modification request to the UPF, providing packet sensing, execution and reporting rules to be installed in the UPF for the PDU session. In step 10b, the UPF can send and confirm an N4 session establishment / modification response.

[0263] (11) Step 11: The SMF sends an N1N2 message transfer message (e.g., Namf_Communication_N1N2MessageTransfer) to the AMF.

[0264] The N1N2 message transfer message may contain N2 SM information. The N2 SM information follows the following information transmitted by the AMF to the (R)AN:

[0265] -CN Tunnel Info: Corresponding to the core network address of the N3 tunnel corresponding to the PDU session;

[0266] - one or more QoS (quality of service) profiles and corresponding QoS flow IDs (QFIs);

[0267] -PDU Session ID: indicates to the UE the association between RAN resources and PDU sessions for the UE;

[0268] - S-NSSAI with the value for the serving PLMN (i.e. HPLMNS-NSSAI, or in case of LBO roaming, VPLMNS-NSSAI);

[0269] - User plane security enforcement information determined by the SMF;

[0270] -UE integrity protection maximum data rate received in the PDU session establishment request message: If integrity protection is indicated as "Preferred" or "Required" in the user plane security execution information

[0271] -RSN (redundancy sequence number) parameter

[0272] The N1N2 messaging message may include an N1SM container. The N1SM container includes a PDU session establishment accept message that the AMF provides to the UE. The PDU session establishment accept message includes the S-NSSAI from the authorized NSSAI. In case of an LBO roaming scenario, the PDU session establishment accept message includes the S-NSSAI from the authorized NSSAI for the VPLMN and also includes the corresponding S-NSSAI of the HPLMN from the mapping of the authorized NSSAI received by the SMF in step 3.

[0273] For QoS flows associated with a QoS rule and QoS profile, multiple QoS rules, QoS flow levels, and QoS parameters may be included in the PDU session establishment accept message and N2 SM information in the N1 SM container, if necessary.

[0274] If the PDU Session Establishment fails between step 5 and step 11, the N1N2 Messaging Message contains an N1 SM container with a PDU Session Establishment Reject message and no N2 SM information. The (R)AN sends a NAS message with a PDU Session Establishment Reject message to the UE. In this case, steps 12-17 below are omitted.

[0275] (12) Step 12: The AMF sends a NAS message including the PDU session ID and PDU session establishment accept message towards the UE and the N2 SM information received from the SMF in an N2 PDU session request message to the (R)AN.

[0276] (13) Step 13: The (R)AN may perform AN-specific signaling exchange with the UE related to the information received in the SMF. For example, in case of NG-RAN, the UE may perform an RRC connection reconfiguration with the UE to configure the required NG-RAN resources related to the QoS rules for the PDU session request received in step 12.

[0277] The (R)AN conveys the received NAS message (PDU Session ID, N1 SM container (PDU Session Establishment Accept Message)) to the UE in step 12. The (R)AN provides the NAS message to the UE only if the AN-specific signaling exchange with the UE includes an (R)AN resource addition related to the received N2 command.

[0278] If the N2 SM information is not included in step 11, the following steps 14 to 16b and step 17 are omitted.

[0279] (14) Step 14: The (R)AN sends an N2 PDU session response message to the AMF. The N2 PDU session response message may include a PDU session ID, a cause, N2 SM information (PDU session ID, AN tunnel information, accepted / rejected QFI list, user plane execution policy notification), etc.

[0280] (15) Step 15: The AMF sends an update SM context request message (e.g., Nsmf_PDU session_UpdateSMContextRequest) to the SMF. The AMF conveys the N2 SM information received from the (R)AN to the SMF.

[0281] (16a) Step S16a: The SMF initiates an N4 session modification procedure with the UPF. The SMF provides the AN tunnel information and corresponding transmission rules to the UPF.

[0282] (16b) Step S16b: The UPF provides an N4 session modification response to the SMF.

[0283] After this step, the UPF can deliver to the UE the DL packets that can be buffered for this PDU session.

[0284] (16c) Step 16c: If the SMF is not already registered for this PDU session, the SMF can register with the UDM for the given PDU session.

[0285] (17) Step 17: The SMF sends an update SM context response message (e.g., Nsmf_PDU session_UpdateSMContextResponse) to the AMF.

[0286] After this step, the AMF communicates any relevant events subscribed to by the SMF.

[0287] (18) Step 18: If at any time during the procedure after step 5, the PDU session establishment cannot be successful, the SMF can inform the AMF by calling Nsmf_PDU session_SMContextStatusNotify(release). The SMF can also release the created N4 session, the PDU session address (e.g. IP address) if assigned, and, if possible, the relationship with the PCF. In this case, step 19 below is omitted.

[0288] (19) Step 19: If the PDU session type is IPv6 or IPv4v6, the SMF may generate and send an IPv6 Router Advertisement to the UE.

[0289] (20) Step 20: The SMF may implement the SM policy related modifications disclosed by the SMF.

[0290] (21) Step 21: After step 4, if the PDU session establishment fails, the SMF may unsubscribe from the modification of the session management subscription data if the SMF does not process the PDU session for the UE any more.

[0291] II. Techniques and Procedures Related to the Present Disclosure

[0292] Below, techniques and procedures related to the present disclosure are described. Examples of problems that the present disclosure seeks to solve may also be described below.

[0293] Improvements to network slicing are being discussed.

[0294] There is a scenario in which the S-NSSAI of the Requested NSSAI is rejected because it is not supported in the TA even if the S-NSSAI of the Requested NSSAI can be supported in a neighboring TA. If the AMF determines that it is better to assign a larger Registration Area (RA) to the S-NSSAI of the Allowed NSSAI in consideration of the mobility of the terminal, etc., it is necessary to include the neighboring TAs in the Registration Area. If the AMF performs such an operation and the rejection reason code sent by the AMF to the UE is "not supported in the RA (Registration Area)", the UE cannot attempt to register to the rejected S-NSSAI until the UE moves out of the RA. If this is not desirable, the AMF can configure the RA to include the current TA and a TA in which the rejected S-NSSAI is not supported. Then, when the UE moves to a neighboring TA that supports the rejected S-NSSAI, the UE can request the rejected S-NSSAI again. If a network slice requested by a UE is not available in the current TA but is available in another TA belonging to the UE's RA, a method for improving the functionality so that the UE can use the network slice needs to be discussed. In other words, a method needs to be discussed so that the AMF does not force the RA size to be reduced and the UE can request such a network slice again.

[0295] Additional potential improvements to network slicing need to be investigated.

[0296] The need and potential mechanisms to achieve these goals will be discussed, including, for example:

[0297] For example, it is necessary to discuss whether and how to initiate registration for a rejected S-NSSAI that is rejected in the first TA of the RA but can be used in other TAs of the RA.

[0298] For reference, in the following, slice means network slice.

[0299] According to conventional technology, when a terminal requires a slice, the terminal can request the slice to be used by including the required slice in the Requested NSSAI. There may be cases where the network cannot accept the terminal's request. For example, the slice requested by the terminal may not be available at the current terminal location. In such a case, the AMF can include the slice requested by the terminal in the Rejected NSSAI and transmit the Rejected NSSAI to the terminal to inform the terminal that the corresponding slice cannot be used. In this case, the AMF can also provide the terminal with the cause for the reject. Currently, three cause values ​​are supported as follows:

[0300] The following example in Table 1 shows examples of cause values ​​related to a rejected S-NSSAI (or a rejected NSSAI) according to the prior art.

[0301] [Table 1]

[0302] For example, as shown in the example of Table 1, the cause value for the rejection may include information such as i) the S-NSSAI cannot be used in the current PLMN or SNPN, ii) the S-NSSAI cannot be used in the current registration area, or iii) the S-NSSAI cannot be used due to authentication and authorization failure or cancellation per network slice.

[0303] For example, a network slice may not be supported in the current registration area, i.e., the base station in which the current terminal is located may not support the slice. In this case, the AMF may set the cause value to 0001 to inform the terminal that it is not supported in the current registration area. A terminal that receives this cause value will not request the slice until it leaves the current registration area. This is because the terminal knows that the network slice is not supported in the current registration area.

[0304] The following drawings are created to illustrate a specific example of the present specification. The names of specific devices and names of specific signals / messages / fields described in the drawings are presented for illustrative purposes only, and the technical features of the present specification are not limited to the specific names used in the following drawings.

[0305] FIG. 8 shows an example of a slice arrangement.

[0306] The example of Figure 8 shows a situation where the terminal moves from the base station TA1 to the base station TA2. If the terminal was in the TA1 area, the terminal could request slice X and slice Y in the requested NSSAI. In this case, the AMF can determine the registration area of ​​the terminal as {TA1, TA2} to avoid frequent mobility registrations in consideration of the mobility of the terminal.

[0307] In this case, since only slice X is supported in the TA1 region, the AMF can send an Allowed NSSAI including slice X to the terminal while sending a Rejected NSSAI including slice Y to the terminal to inform the terminal that the cause is currently not available in the registration area.

[0308] If the terminal subsequently moves to the TA2 base station, it will not perform a new registration procedure because it is in the same registration area. In this case, the terminal will only use slice X even if it is in an area where slice Y is available.

[0309] The terminal can optionally request slice Y again in TA2, but unnecessary signaling may occur because the terminal does not know whether the network can accept the slice.

[0310] The disclosure herein proposes a method for effectively solving such problems.

[0311] The disclosure herein below proposes a method for solving such problems.

[0312] III. Disclosure of the Present Specification

[0313] The disclosures described below in this specification can be implemented in one or more combinations (e.g., a combination including at least one of the contents described below). Each drawing shows an embodiment of each disclosure, but the embodiments of the drawings can be implemented in combination with each other.

[0314] The method descriptions proposed in this disclosure may consist of one or more of the acts / structures / steps described below. The following methods described below may be performed or used in combination or complementation.

[0315] The present disclosure proposes the following methods to solve the various problems described above. The following methods may be implemented or used in combination or complementation.

[0316] Hereinafter, the disclosure of the present specification will be described with reference to the first to tenth examples of the disclosure of the present specification. The first to tenth examples of the disclosure of the present specification described below can also be implemented in combination. For reference, the tenth example of the disclosure of the present specification can show a specific embodiment based on a combination of at least one of the first to ninth examples of the disclosure of the present specification.

[0317] 1. First Example of the Disclosure

[0318] The first example of the disclosure of this specification describes an example of a method in which the AMF provides the UE with TA information in which the slice is rejected. For example, according to the first example of the disclosure of this specification, the AMF may include TA information in which the slice is rejected while sending a Rejected NSSAI to the UE.

[0319] If the Rejected NSSAI cannot be used in the current registration area, the AMF may send the Rejected NSSAI to the terminal together with TA information in which the NSSAI cannot be used.

[0320] For example, in the example of Figure 8, in TA1, the terminal can request slice X and slice Y in the requested NSSAI. In this case, according to the first example of the disclosure of this specification, the AMF can send an Allowed NSSAI including slice X to the terminal and a Rejected NSSAI including slice Y to the terminal, while the AMF can send TA information in which slice Y is not available to the terminal.

[0321] In this situation, the AMF of the terminal can decide to set the registration area of ​​the terminal to {TA1, TA2}. In this case, since slice Y is only available in TA1, the AMF can inform the terminal that it is rejected only in TA1.

[0322] Alternatively, if slice Y is rejected, the AMF can send information that enables slice Y to be used, for example, information for TA2, to the terminal because TA2 supports slice Y. The AMF can send such information to the terminal within the registration area, or the AMF can send such information to the terminal based on information held by the network regardless of the registration area.

[0323] For reference, the operation of providing additional information for which a Rejected NSSAI is applied or an AMF is available is optional, and if the network does not provide additional information for a slice, the terminal must process the slice in the same manner as the conventional operation.

[0324] In this method, the registration area may be set to be large or the amount of information provided to the terminal may be large. For example, assuming that slice Y is not supported in TA1 for the terminal, and slice Y is supported in all other areas, RA={TA1, TA2, TA3, TA4, .. TA10} may be used. In this case, the TA information available for the slice must be transmitted as {TA2, TA3, TA4, .. TA10} in order for the AMF to provide additional information for the slice to the terminal. Therefore, the larger the RA, the more information the AMF must transmit to the terminal.

[0325] For reference, the example of Figure 9 below can be applied not only to the first example of the disclosure of this specification, but also to various operations and / or procedures described in the first to tenth examples of the disclosure of this specification.

[0326] The following drawings are created to illustrate a specific example of the present specification. The names of specific devices and names of specific signals / messages / fields described in the drawings are presented for illustrative purposes only, and the technical features of the present specification are not limited to the specific names used in the following drawings.

[0327] FIG. 9 shows an example of a procedure according to the first example of the disclosure of this specification.

[0328] The example of Figure 9 shows a procedure based on the first example of the disclosure of this specification. At this time, it is assumed that NG-RAN1 (egcell1) is set to TA1 and NG-RAN2 (egcell2) is set to TA2. It is also assumed that slice X is supported in NG-RAN1 and slices X and Y are supported in NG-RAN2. NG-RAN1 and NG-RAN2 may be other cells belonging to the same base station.

[0329] Step 1. Assume that the terminal is connected to the base station via NG-RAN1.

[0330] Step 2. The terminal can send a registration request message including slice X and slice Y in the Requested NSSAI to use slice X and slice Y.

[0331] Step 3. The AMF may send a registration acceptance message to the terminal. For example, the registration acceptance message may include Allowed NSSAI information and Rejected NSSAI information. For example, since the terminal is currently connected via NG-RAN1, slice Y is not supported in NG-RAN1, so the AMF may set Allowed NSSAI = {slice X} and set Rejected NSSAI = {slice Y} together with information informing the terminal that slice Y is available in TA2.

[0332] Alternatively, a separate IE other than the Rejected NSSAI may be defined, and the AMF may send such a separate IE to the terminal. In this case, the AMF may also send TA list information available for slice Y to the terminal. For example, the AMF may send information such as Conditional NSSAI={slice Y-Registration required-supported area=[TA2]} to the terminal. Through this, the terminal may be informed that it needs to perform a Registration procedure to use slice Y.

[0333] The AMF can also set the Registration area of ​​the terminal to {TA1, TA2} taking into account the mobility of the terminal and inform the terminal of the registration area. A Conditional NSSAI can have the same meaning as a Partially Allowed NSSAI or a Partially Rejected NSSAI. For example, the AMF can send a Partially Allowed NSSAI to the terminal in the form of partially allowed NSSAI={slice Y-Registration not required-supported area=[TA2]}. For another example, the AMF can send a Partially Rejected NSSAI to the terminal in the form of partially rejected NSSAI={slice Y-Registration required-supported area=[TA2]}.

[0334] Alternatively, the IE name may indicate whether registration is required. For example, a partially allowed NSSAI may include slice information that can be used without performing registration, and a partially rejected NSSAI may include slice information that can be used after performing registration.

[0335] Step 4. The terminal can leave NG-RAN1 and move to NG-RAN2.

[0336] Step 5. Based on the information received from step 3, the terminal recognizes that slice Y is available in NG-RAN2 and can perform a Registration procedure to use slice Y. In this case, the AMF can set Requested NSSAI = {slice X, slice Y} to use both slice X and slice Y.

[0337] Step 6. The AMF can set Allowed NSSAI = {slice X, slice Y} because the terminal is in an area where slice X and slice Y are both supported. In this case, the AMF can set the terminal's Registration area to {TA2} where slice X and slice Y are both supported.

[0338] Step 7. The UE may send a PDU session establishment Request message to generate a PDU session using slice Y. In this case, the UE sets slice Y information and other necessary information such as DNN based on the UE route selection policy (URSP) rule.

[0339] Step 8. The SMF performs an N4 Session establishment procedure with the UPF to create a PDU session. If necessary, it generates a PDU session according to the procedure described in the examples of Figures 7a and 7b.

[0340] Step 9. The SMF can inform the terminal that the PDU session has been successfully established by sending a PDU session establishment Accept message to the terminal.

[0341] In the above example, it was described that the AMF sends a TA list with information on whether slices are supported or not, but this is just an example. If it is necessary to support smaller units, the AMF can send a cell list instead of a TA list. Or, the AMF can send TA + cell list at the same time.

[0342] 2. Second Example of the Disclosure

[0343] According to a second example of the disclosure of this specification, when the terminal enters a new region and becomes able to use a slice, the AMF can inform the terminal by signaling that it can use the slice.

[0344] When the terminal moves within the registration area to an area where the Rejected NSSAI is available, the AMF can send signalling to the terminal based on this. For example, in the example of FIG. 8, if the terminal requests slice X and slice Y in the Requested NSSAI in TA1, the AMF can also send the Allowed NSSAI to the terminal in slice X and the Rejected NSSAI to the terminal in slice Y. In this case, when the AMF recognizes that the terminal has moved to TA2, the AMF can inform the terminal that it can use slice Y via NAS signalling (e.g. UCU procedure). Alternatively, when the AMF recognizes that the terminal has moved to TA2, the AMF can update the Rejected NSSAI of the terminal so that the terminal can request slice Y again.

[0345] In this method, if the terminal moves while in idle mode, the AMF may not be able to recognize that the terminal has moved to the TA2 area. In this case, after the terminal enters connected mode by MO or MT signalling / data, the AMF can inform the terminal that Rejected NSSAI is available.

[0346] 3. Third Example of the Disclosure

[0347] According to a third example of the disclosure of this specification, the AMF may also send a new cause while sending a Rejected NSSAI to the terminal.

[0348] For example, the AMF can transmit a new cause value while transmitting a Rejected NSSAI to the terminal. According to conventional technology, when the slice requested by the terminal cannot be used homogenously in the registration area determined by the AMF, the AMF transmits a Rejected NSSAI and sets the cause to "S-NSSAI not available in the current Registration area." In other words, the AMF transmits a corresponding cause without distinguishing whether or not the slice can be used in the part of the registration area transmitted to the terminal by the AMF.

[0349] According to a fourth example of the disclosure of this specification, when the AMF allocates a cause for the actual Rejected NSSAI, if the entire NSSAI is not available in the Registration Area, the AMF can set the cause to "S-NSSAI not available in the current Registration Area". If a slice is available in some areas of the Registration Area, the AMF can send a new cause (e.g., S-NSSAI not available in the current tracking area).

[0350] For example, if a terminal that has received a new cause moves within a registration area and moves to another TA in the current TA, the terminal is permitted to re-request the rejected slice based on the new cause.

[0351] The operation according to the third example of the disclosure of the present specification accurately distinguishes between slices that can be clearly re-requested and slices that cannot be re-requested and informs the terminal of the same, but does not provide accurate TA information as in the method described in the first example of the disclosure of the present specification. Therefore, even if the terminal is in a TA in which the slice cannot actually be used, the terminal can re-request the slice.

[0352] 4. Fourth Example of the Disclosure of the Present Specification

[0353] According to a fourth example of the disclosure of this specification, the terminal can update the Rejected NSSAI based on SIB information transmitted by the base station.

[0354] Based on the SIB information sent by the base station, the terminal can erase the slice sent by the base station in the Rejected NSSAI.

[0355] The base station can use the SIB to transmit slice information that the base station supports. This is to support cell(re)selection of the terminal and does not affect the NAS protocol. When the terminal receives a Rejected NSSAI from the network, if the slice information sent by the base station to the SIB includes a slice included in the Rejected NSSAI, the terminal can delete the slice from the Rejected NSSAI. If the terminal moves to a new TA through this and there is an available slice in the new TA, the terminal can request this slice again. That is, the terminal can request the S-NSSAI deleted in the Rejected NSSAI again by performing the registration procedure. Subsequent operations follow the conventional operations. For example, the terminal can receive a new Allowed NSSAI and request a PDU session for the slice.

[0356] For this reason, when cell (re)selection occurs in the AS layer of the terminal, it is necessary to inform the NAS layer of the terminal of the slice information to be sent in the SIB. Based on this, the NAS layer of the terminal can compare the Rejected NSSAI with the slice information sent by the base station and determine which slice to remove in the Rejected NSSAI.

[0357] In order to prevent the terminal from updating all Rejected NSSAIs, the terminal may be permitted to update the Rejected NSSAI only for a specific cause based on a specific cause of dropping out of the network. For example, as in the third example of the disclosure of this specification, if a new cause is created and only rejected S-NSSAIs having the corresponding cause are included in the slice information transmitted by the base station, the terminal may update it. Instead of using a new cause, the existing "S-NSSAI not available in the current Registration area" cause may be used.

[0358] At this time, to prevent many terminals from entering TA at the same time and performing registration at the same time, the AMF can perform the following operations. For example, when the AMF gives the terminal an allowed cause to erase in the Rejected NSSAI, it can prevent too many terminals from generating signaling at once by considering the terminal's movement route, the number of terminals / slices to which the corresponding cause is assigned, the load status of the base station, etc. In addition, it can give a general or slice specific MM / SM back-off timer to some terminals to apply the existing NAS level congestion control.

[0359] 5. Fifth Example of the Disclosure of the Present Specification

[0360] According to a fifth example of the disclosure of this specification, a terminal can update the Allowed NSSAI based on SIB information transmitted by a base station.

[0361] The operation according to the fifth example of the disclosure of the present specification operates in a similar manner to the fourth example of the disclosure of the present specification, that is, the terminal can update the Rejected NSSAI based on the SIB information, and further, the terminal can include the slice deleted in the Rejected NSSAI in the Allowed NSSAI without the need to perform registration again.

[0362] If the terminal needs a PDU session for the slice, it can request PDU session establishment. The AMF can provide a special cause as in the third and / or fourth examples of the disclosure of this specification to prevent the terminal from updating all Rejected NSSAIs to Allowed NSSAIs.

[0363] That is, only when the terminal receives a Rejected NSSAI with a specific cause, the terminal can update to an Allowed NSSAI. The AMF can check whether network slice selection assistance information (NSSAI) is required for the slice to determine the cause, whether the slice can be used in the registration area of ​​the terminal, whether NSAC needs to be performed, etc. For example, the AMF can determine the cause so that a slice that needs to perform NSSAA or a slice that needs NSAC does not perform the operation of updating to an Allowed NSSAI. Alternatively, a new cause can be sent to the terminal only if NSSAA / NSAC is successfully performed in advance for a slice that needs to perform NSSAA / a slice that needs NSAC.

[0364] In addition, when the terminal executes PDU session establishment, it may also transmit information informing the AMF that the slice requested has been updated from Rejected NSSAI to Allowed NSSAI. Alternatively, while the terminal executes a Service Request, it may transmit the slice list changed from Rejected NSSAI to Allowed NSSAI and information informing the update.

[0365] Based on this information, or even if the terminal does not send the corresponding information, the AMF can store both the cause and the Rejected NSSAI in the UE context, which indicates that the AMF can update the Allowed NSSAI in the terminal. Further, based on this, the AMF can check again whether the corresponding slice can be used at the terminal's location. If the slice can be used, the AMF can add the corresponding slice to the Allowed NSSAI in the UE context. If the slice cannot be used, the AMF can reject the terminal's PDU session establishment request and send a new Allowed NSSAI / Rejected NSSAI to the terminal via the UCU procedure.

[0366] In order to prevent many terminals from entering TA at the same time and simultaneously performing PDU session establishment, AMF can prevent too many terminals from generating signaling at once by considering the movement route of the terminal, the number of terminals / slices to which the corresponding cause is assigned, the load status of the base station, etc., when giving the terminal an update-allowed cause to the Allowed NSSAI. In addition, a general or slice specific MM / SM back-off timer can be given to some terminals to apply the existing NAS level congestion control.

[0367] 6. Sixth Example of the Disclosure of the Present Specification

[0368] The sixth example of the present disclosure describes a specific example according to the fourth example and / or the fifth example of the present disclosure.

[0369] According to a sixth example of the disclosure of this specification, the UE may remove the rejected S-NSSAI based on cell broadcast information.

[0370] In the method according to the sixth example of the disclosure of this specification, additional signaling between the UE and the network is avoided as much as possible according to the current mechanism. When the UE configures the Requested NSSAI, the UE needs not to include the rejected S-NSSAI in the Requested NSSAI in the current registration area until the UE leaves the current registration area. Therefore, even if the rejected S-NSSAI is available in the current location, the UE cannot use the slice until the UE leaves the registration area.

[0371] Slice information broadcast in the NG-RAN can be utilized. The "slice information" broadcast in a part of the SIB message can be used. The "slice information" generally indicates slice information available for a cell. For example, the "slice information" can be slice group information provided to the UE via NAS signaling. When the UE camps on a cell using the broadcasted slice information, the UE can obtain information related to the available slices of the camped cell. Based on this, if the "slice information" broadcast by the SIB message includes a rejected S-NSSAI, the UE can remove the slice in the rejected S-NSSAI. Then, if necessary, the UE can perform a registration procedure to request a previously rejected slice in the current registration area.

[0372] The same procedure as in the prior art is used, and no additional changes are required for the signaling between objects. All changes are internal UE operations, i.e., if the S-NSSAI is included in the slice information broadcast by the camp cell, the UE can remove the rejected S-NSSAI.

[0373] The example of FIG. 10 shows an example of a procedure according to the sixth example of the disclosure of this specification.

[0374] The following drawings are created to illustrate a specific example of the present specification. The names of specific devices and names of specific signals / messages / fields described in the drawings are presented for illustrative purposes only, and the technical features of the present specification are not limited to the specific names used in the following drawings.

[0375] FIG. 10 shows an example of a procedure according to the sixth example of the disclosure of this specification.

[0376] 1. The UE is camped on a cell of the source NG-RAN and can send a Registration Request message including Requested NSSAI={slice x, slice y}.

[0377] 2. The AMF can determine the registration area (e.g., {TA1, TA2}) of the UE to include the TAs of the source NG-RAN and the target NG-RAN, and can send a registration accept message to the UE including Allowed NSSAI={slice x} and Rejected NSSAI={slice y} because slice Y is not supported in the source NG-RAN.

[0378] 3. The UE can move and camp on a cell of the target NG-RAN. The UE can receive slice information via a SIB message and know that slice Y is currently available in the cell.

[0379] 4. The UE removes slice y in the rejected S-NSSAI. When the UE removes the rejected S-NSSAI, the UE checks the cause of the rejected S-NSSAI. If the cause of the rejected S-NSSAI is rejection for the entire PLMN or due to slice authorization, the rejected S-NSSAI is not removed.

[0380] An example will be described in which the group information of the slice information received by the UE is Group={slice A, slice B, slice C}, and Rejected NSSAI={slice A cause=PLMN, slice B cause=RA}. Here, slice A cause=PLMN may mean that the reason slice A is rejected is that it is currently unavailable in the PLMN. slice B cause=RA may mean that the reason slice B is rejected is that it is currently unavailable in the registration area.

[0381] When the NG-RAN transmits slice information to the UE in the form of a group, multiple slices can be mapped to one group. In this case, the UE can perform the operation in the same manner as described above. For example, the UE can determine whether to delete the rejected S-NSSAI based on the slices mapped to the group. For example, Group X is {slice A, slice B, slice C}, and the NG-RAN can transmit Group X information to the UE. The UE can know that Group X indicates slice A, slice B, and slice C through NAS signaling.

[0382] If Rejected S-NSSAIs = {slice A cause = entire PLMN, slice B cause = Registration area}, if the UE receives Group X information via SIB, the UE can delete slice B in Rejected S-NSSAIs.

[0383] 5. The UE may send a Registration Request message with Requested NSSAI={slice x, slice y}.

[0384] 6. The AMF may provide a new registration area that can support the allowed NSSAI={slice x, slice y} and all slices of the allowed NSSAI. For example, the AMF may send a registration accept message to the UE including the allowed NSSAI={slice x, slice y} and information for the new registration area.

[0385] According to a sixth example of the disclosure of this specification, the UE may remove a rejected S-NSSAI if the slice is available in the serving cell based on slice information broadcast via a SIB message.

[0386] 7. Seventh Example of the Disclosure of the Present Specification

[0387] According to a seventh example of the disclosure of this specification, the AMF may send conditional Allowed NSSAI information to the UE.

[0388] There may be problems similar to those described above (for example, if the UE receives a Rejected NSSAI including a requested slice, the UE cannot request the corresponding slice again until it leaves the registration area). For example, in a situation where the UE's currently connected base station supports the slice requested by the UE, the AMF can determine the registration area taking into account the mobility of the UE. In this case, all base stations in the registration area may not support the slice requested by the UE.

[0389] In this case, in order to provide the slice requested by the terminal, the AMF can configure the registration area with only base stations that support the slice requested by the terminal. This can cause a problem in which the terminal needs to frequently perform the mobility registration procedure. For example, in the example of FIG. 8, the AMF can configure a registration area that includes only TA2. Then, when the UE moves from TA1 to TA1 or TA3, it needs to perform the mobility registration procedure.

[0390] In order to solve this problem, the following method can be used.

[0391] For example, the AMF may transmit a Conditional Allowed NSSAI to the terminal. When the terminal receives the Conditional Allowed NSSAI, the terminal may use the corresponding slice only if the permitted slice included in the Conditional Allowed NSSAI is supported in the currently connected base station based on the SIB information transmitted by the base station.

[0392] For example, if slice X and slice Y are included in the Conditional Allowed NSSAI, if only slice X is permitted in the SIB from the current base station, the terminal can use a PDU session only for slice X. In this case, the terminal can establish a PDU session for slice X and can send and receive data.

[0393] If a UE generates a PDU session for slice X and the UE moves to another base station, but the corresponding base station does not support slice X, the network can deactivate or release the PDU session for slice X. For example, in the process of performing a Handover (HO) procedure in a base station, the AMF can determine whether the base station supports the slice based on information about the base station (e.g., RAN NGAP ID), ULI (User Location Information) information, supported slice information, information that the slice of the PDU session cannot be supported, etc., included in the signaling (e.g., Path Switch Request, Handover Notify, etc.) sent to the AMF, and then the AMF can perform deactivation based on the information.

[0394] For example, when the AMF receives a Handover Notify, it can request the SMF to deactivate / release a PDU session whose slice is not supported in the corresponding base station. The SMF that receives this can perform a deactivation procedure (3GPP TS 23.502 V17.3.0 clause 4.3.7) or a release procedure (3GPP TS 23.502 V17.3.0 clause 4.3.4).

[0395] In addition, when activation occurs for a deactivated PDU session, the AMF can check whether the terminal's base station (the current base station if the terminal is in a connected state, or the base station that sent a Service Request / Registration Request to the AMF if the terminal is in an idle state) supports the slice of the PDU session to be activated. If the base station does not support the slice, the AMF can reject the SMF's request to send N2 information.

[0396] When deciding whether to send a Conditional Allowed NSSAI, the AMF may take into consideration the terminal's capability information, slice information supported by base stations in the terminal's registration area, etc. In addition, a slice included in the Conditional Allowed NSSAI must not be included in the Allowed NSSAI, Rejected NSSAI, or Pending NSSAI.

[0397] For reference, instead of issuing a separate Conditional Allowed NSSAI, the AMF can also send the Allowed NSSAI and add a separate cause to indicate whether or not to use it conditionally.

[0398] The slice information transmitted by the base station to the SIB is transmitted in the form of group slice group, as described in the sixth example of the disclosure of this specification.

[0399] 8. Eighth Example of the Disclosure of the Present Specification

[0400] The eighth example of the present disclosure describes a specific example related to the second example of the present disclosure.

[0401] An eighth example of the disclosure herein describes an example of a network-triggered Rejected NSSAI update.

[0402] According to an eighth example of the disclosure of the present specification, it is possible to improve the support of RA including TA supporting rejected S-NSSAI. According to the eighth example of the disclosure of the present specification, in order to support legacy UE, AMF can determine RA for legacy UE using the same mechanism as that for UE implemented by future standards.

[0403] When the UE requests a slice, the AMF rejects the UE request if the requested slice is not currently supported in the TA. The AMF can then provide the slice to the UE in a Rejected NSSAI with a cause indicating that the slice is not available in the current registration area. The AMF does not need to store the rejected S-NSSAI.

[0404] In an eighth example of the disclosure of this specification, it is proposed that the AMF stores the rejected S-NSSAI provided to the UE. If the AMF detects that the UE moves to an area in which the rejected S-NSSAI is supported within the current registration area, the AMF can trigger a UE Configuration Update procedure to remove the S-NSSAI in the Rejected NSSAI.

[0405] The AMF does not need to store all rejected S-NSSAI with a cause indicating that the slice is not available in the current registration area. The AMF can decide to store the S-NSSAI if the S-NSSAI is available in any TA of the RA. In addition, to reduce the AMF load and signaling for UE Configuration Update, the operator can configure the AMF in a local policy. For example, the operator can also configure the AMF with a candidate list of slices that can be stored when a slice is rejected. The AMF can take into account the UE capabilities. For example, if the UE supports other solutions that affect the UE, the AMF does not need to store the Rejected NSSAI for the UE.

[0406] For example, as in the first example of the disclosure of this specification, only when the terminal cannot support associated TA information for the Rejected NSSAI, the AMF can store the Rejected NSSAI dropped from the terminal. That is, based on the capability information sent by the terminal to the AMF in the registration procedure, the AMF can determine whether to store the Rejected NSSAI.

[0407] Also, if the terminal is in the IDLE state, the AMF does not know the exact location of the terminal. Therefore, in order to inform the terminal that a slice is available as soon as possible, the AMF can keep the terminal in the connected state if a TA where a slice is available is nearby, or set the timer value to a small value when the terminal sends the periodic registration timer. If the periodic timer of the terminal is set to a small value, the terminal needs to perform the periodic registration procedure more frequently, so the AMF can find out the TA information to which the terminal is connected more quickly.

[0408] If the AMF removes the rejected S-NSSAI via the UE Configuration Update procedure, the AMF may include the S-NSSAI in the UE's Allowed NSSAI to reduce additional signaling with the UE based on the operator's local policy.

[0409] The following drawings are created to illustrate a specific example of the present specification. The names of specific devices and names of specific signals / messages / fields described in the drawings are presented for illustrative purposes only, and the technical features of the present specification are not limited to the specific names used in the following drawings.

[0410] FIG. 11 shows an example of a procedure according to the eighth example of the disclosure of this specification.

[0411] The example in Figure 11 shows an example of a procedure associated with a network-triggered Rejected NSSAI update.

[0412] 1. The UE sends a registration request message containing Requested NSSAI={slice x, slice y}. The AMF can determine the registration area of ​​the UE and send a registration accept message to the UE containing Allowed NSSAI={slice x} and Rejected NSSAI={slice y} since slice Y is not supported in the current TA. The AMF can store the rejected S-NSSAI if the operator's local policy is satisfied.

[0413] 2. The AMF can detect that the UE has moved to a TA where the stored rejected S-NSSAI is supported. The AMF can trigger a UE configuration update procedure to remove the rejected S-NSSAI currently available in the TA. Depending on the operator's policy, the rejected S-NSSAI can be included in the Allowed NSSAI to reduce additional signaling with the UE.

[0414] The AMF stores the rejected S-NSSAI for the UE and can remove the rejected S-NSSAI if the UE moves to an area where the rejected S-NSSAI exists according to operator policy.

[0415] 9. Ninth Example of the Disclosure of the Present Specification

[0416] The ninth example of the disclosure of this specification describes an example in which a combination of embodiments including at least one of the first to eighth examples of the disclosure of this specification is applied.

[0417] 9-1.Non-homogenous slice support within a Registration area

[0418] In a ninth example of the present disclosure, a non-homogenous slice support within a Registration area is proposed.

[0419] The UE and AMF can support non-uniform slices within the registration area of ​​the UE. If the UE supports non-uniform slices, the UE can indicate the support in the 5GMM capabilities. If the AMF determines the registration area of ​​the UE and the S-NSSAI of the Reuqested NSSAI is not uniformly supported in the registration area, if the S-NSSAI is supported or not supported in the registration area, the AMF can include the corresponding S-NSSAI in the Rejected NSSAI or Allowed NSSAI together with the Tracking Area information and send it to the UE.

[0420] Note: Whether to provide slices for Rejected NSSAI(s) or Allowed NSSAI is an S-NSSAI specific decision based on AMF policy, e.g., it may take into account whether NSAC applies to the S-NSSAI or not. Both options may be supported in a PLMN and may be applied simultaneously to a UE for different S-NSSAIs.

[0421] The AMF may determine that the UE needs to perform a registration procedure before using an S-NSSAI supported in a subset of the registration area. The AMF may then provide a rejected S-NSSAI containing the corresponding S-NSSAI along with the Tracking Area information in which the S-NSSAI is supported or not supported. If the UE attempts to use the S-NSSAI and the UE moves into a Tracking Area in which the S-NSSAI is supported, the UE may trigger a registration procedure to request the S-NSSAI.

[0422] If the AMF determines that the UE does not need to perform a registration procedure before using the S-NSSAI it supports in a subset of the registration area, the AMF can provide the UE with the S-NSSAI in the Allowed NSSAI along with the Tracking Area information in which the S-NSSAI is supported or not supported. The AMF can provide the S-NSSAI to the (R)AN by including it in the Allowed NSSAI without including the Tracking Area information in which the S-NSSAI is supported. If the UE has a PDU session related to the S-NSSAI and the UE moves outside the Tracking Area in which the S-NSSAI is supported, the AMF can request the SMF to deactivate the related PDU session.

[0423] The UE may perform the following example actions:

[0424] a) If the UE leaves a Tracking Area in which S-NSSAI is supported, the UE shall:

[0425] -Do not use S-NSSAI to request PDU session establishment;

[0426] -Do not establish / modify PDU sessions for S-NSSAI;

[0427] -There is no need to release the existing PDU session for S-NSSAI unless the UE receives an explicit SM PDU session release command message from the network.

[0428] b) When the UE is in a Tracking Area in which S-NSSAI is supported, the UE shall:

[0429] - It is possible to trigger a PDU session setup procedure without triggering a registration procedure;

[0430] -It is possible to request activation of a UP connection of an existing PDU session for S-NSSAI.

[0431] In the above example, it was described that the AMF transmits a TA list with information on whether the slice is supported or not, but this is only an example. If it is necessary to support smaller units, the AMF can transmit a cell list instead of the TA list. Or the AMF can transmit a TA + cell list at the same time. In addition, for PDU sessions that use slices that are not homogeneously supported in the registration area, EPC interworking or handover to non-3GPP access can be prevented. If the UE performs handover to non-3GPP access, the AMF can check the slice of the PDU session and prevent the UE from requesting a handover.

[0432] 9-2. Example of application to registration procedures

[0433] Embodiments including at least one of the first to ninth examples disclosed in this specification may also be applied to the registration procedure described with reference to Figures 6a and 6b.

[0434] For example, the following description can be applied to one step of FIG. 6a and FIG. 6b:

[0435] If the UE supports non-homogeneous slices in the registration area, the UE may indicate the "non-homogeneous slice support" capability in the UE Mobility Management (MM) Core Network Capability. For example, the UE may send a registration request message including UE MM Core Network Capability information, and the UE MM Core Network Capability information may include the "non-homogeneous slice support" capability.

[0436] For example, for the 21 steps of Figures 6a and 6b, the following explanations can be applied:

[0437] If the UE indicates non-homogeneous slice support in the UE 5GMM Core Network Capability, the AMF may include the S-NSSAI(s) supported in a subset of the UE's registration area (e.g., some of the TAs included in the registration area) in the rejected S-NSSAI or allowed NSSAI. In this case, the AMF may provide tracking area information in which the S-NSSAI(s) are supported or not supported. The UE may receive the rejected S-NSSAI including the S-NSSAI together with the tracking area information. If the UE moves in a tracking area in which the S-NSSAI is supported, the UE may trigger a registration procedure to include the corresponding S-NSSAI in the requested NSSAI. If the UE receives the Allowed NSSAI with Tracking Area information including the S-NSSAI and the UE is located in a tracking area in which the corresponding S-NSSAI is supported, the UE may establish a PDU session using the S-NSSAI without performing a registration procedure.

[0438] 9-3.Example of application to service requests

[0439] The embodiments including at least one of the first to ninth examples disclosed in this specification may also be applied to the service request procedures shown in Figures 12a to 12c.

[0440] The following drawings are created to illustrate a specific example of the present specification. The names of specific devices and names of specific signals / messages / fields described in the drawings are presented for illustrative purposes only, and the technical features of the present specification are not limited to the specific names used in the following drawings.

[0441] 12a to 12c show an example of a UE triggered service request procedure.

[0442] Figures 12a to 12c show an example of a service request procedure triggered by a UE. For the specific procedures shown in Figures 12a to 12c, refer to Clause 4.2.3.2 UE Triggered Service Request in 3GPP TS 23.502 V17.3.0. For the remaining operations except for the application examples described below, Clause 4.2.3.2 UE Triggered Service Request in 3GPP TS 23.502 V17.3.0 can be applied as is.

[0443] In the example of Fig. 12a to 12c, the following explanation applies to step 4):

[0444] The AMF can send a message based on Nsmf_PDU session_UpdateSMContextRequest to the SMF. The message based on Nsmf_PDU session_UpdateSMContextRequest can include information such as PDU session ID(s), Operation Type, UE location information, Access Type, RAT Type, UE presence in LADN service area, Indication of Access Type can be changed, and / or [MO Exception Data Counter].

[0445] The Nsmf_PDU session_UpdateSMContextRequest is invoked in the following cases: For example, if the S-NSSAI related to the N2 SM information is not supported in the current UE location, the AMF does not send the N2 SM message provided in step 3a of FIG.

[0446] The embodiments including at least one of the first to ninth examples disclosed in this specification can also be applied to the service request procedure shown in FIG.

[0447] The following drawings are created to illustrate a specific example of the present specification. The names of specific devices and names of specific signals / messages / fields described in the drawings are presented for illustrative purposes only, and the technical features of the present specification are not limited to the specific names used in the following drawings.

[0448] FIG. 13 shows an example of a network trigger service request procedure.

[0449] Figure 13 shows an example of a network-triggered service request procedure. For the specific procedure shown in Figure 13, refer to Clause 4.2.3.3 Network Triggered Service Request in 3GPP TS 23.502 V17.3.0. For the remaining operations except for the application example described below, Clause 4.2.3.3 Network Triggered Service Request in 3GPP TS 23.502 V17.3.0 can be applied as is.

[0450] For step 3b the following comments apply:

[0451] The AMF may respond to the SMF. If the AMF detects that the request from the SMF is related to an S-NSSAI that is not supported in the current UE location, the AMF may reject the SMF request and inform the SMF that the S-NSSAI is not supported in the current UE location.

[0452] 9-4. Example of application to UE Configuration Update procedure

[0453] The embodiments including at least one of the first to ninth examples disclosed in this specification may also be applied to the UE configuration update procedure shown in FIG.

[0454] The following drawings are created to illustrate a specific example of the present specification. The names of specific devices and names of specific signals / messages / fields described in the drawings are presented for illustrative purposes only, and the technical features of the present specification are not limited to the specific names used in the following drawings.

[0455] FIG. 14 shows an example of a UE configuration update procedure.

[0456] Figure 14 shows an example of a UE configuration update procedure for access and mobility management related parameters. For the specific procedure shown in Figure 14, refer to Clause 4.2.4.2 UE Configuration Update procedure for access and Mobility Management related parameters in 3GPP TS 23.502 V17.3.0. For the remaining operations except for the application examples described below, Clause 4.2.4.2 UE Configuration Update procedure for access and Mobility Management related parameters in 3GPP TS 23.502 V17.3.0 can be directly applied.

[0457] For step 1, the following comments apply:

[0458] If the UE indicates non-uniform slice support in the UE 5GMM Core Network Capability, the AMF may include S-NSSAI(s) supported in a subset of the UE's Registration Area in the Allowed NSSAI. In this case, the AMF may provide Tracking Area information in which the corresponding S-NSSAI(s) is supported or not supported.

[0459] 9-5. Example of application for selective deactivation of UP connection of existing PDU session

[0460] Embodiments including at least one of the first to ninth examples disclosed in this specification may also be applied to selective deactivation of a UP connection of an existing PDU session shown in FIG. 15.

[0461] The following drawings are created to illustrate a specific example of the present specification. The names of specific devices and names of specific signals / messages / fields described in the drawings are presented for illustrative purposes only, and the technical features of the present specification are not limited to the specific names used in the following drawings.

[0462] Figure 15 shows an example of a selective deactivation procedure for a CN-initiated existing PDU session UP connection.

[0463] Figure 15 shows an example of a CN-initiated selective deactivation of an UP connection of an existing PDU session. For the specific procedure shown in Figure 15, refer to Clause 4.3.7 CN-initiated selective deactivation of an UP connection of an existing PDU session in 3GPP TS 23.502 V17.3.0. For the remaining operations except for the application examples described below, Clause 4.3.7 CN-initiated selective deactivation of UP connection of an existing PDU session in 3GPP TS 23.502 V17.3.0 can be applied as is.

[0464] For step 1, the following comments apply:

[0465] The AMF may inform the SMF that the UE has moved outside the slice service area in which slices are supported. In this case, the SMF may decide to deactivate the UP connection of the PDU session.

[0466] 9-6.Application example for inter NG-RAN handover

[0467] Embodiments including at least one of the first to ninth examples disclosed in this specification may also be applied to the inter NG-RAN handover shown in FIG. 16.

[0468] The following drawings are created to illustrate a specific example of the present specification. The names of specific devices and names of specific signals / messages / fields described in the drawings are presented for illustrative purposes only, and the technical features of the present specification are not limited to the specific names used in the following drawings.

[0469] Figure 16 shows an example of an inter NG-RAN handover procedure.

[0470] Figure 16 shows an example of Xn based inter NG-RAN handover without User Plane function re-allocation. For the specific procedure shown in Figure 16, refer to Clause 4.9.1.2.2 Xn based inter NG-RAN handover without User Plane function re-allocation in 3GPP TS 23.502 V17.3.0. For the remaining operations except for the application examples described below, Clause 4.9.1.2.2 Xn based inter NG-RAN handover without User Plane function re-allocation in 3GPP TS 23.502 V17.3.0 can be applied as is.

[0471] For step 2, the following comments apply:

[0472] The AMF may send a request message (e.g., a request message based on Nsmf_PDU session_UpdateSMContextRequest) to the SMF. If the AMF determines that the PDU session is associated with an S-NSSAI that is not supported at the current UE location, the AMF may inform the SMF that the S-NSSAI is not supported at the current UE location. The SMF may deactivate the UP connection of the PDU session.

[0473] Embodiments including at least one of the first to ninth examples disclosed in this specification may also be applied to the execution steps of inter NG-RAN handover shown in Figures 17a and 17b.

[0474] The following drawings are created to illustrate a specific example of the present specification. The names of specific devices and names of specific signals / messages / fields described in the drawings are presented for illustrative purposes only, and the technical features of the present specification are not limited to the specific names used in the following drawings.

[0475] 17a and 17b show an example of an inter NG-RAN handover procedure.

[0476] Figures 17a and 17b show an example of an execution phase of inter NG-RAN node Xn based handover. For the specific procedures shown in Figures 17a and 17b, refer to 4.9.1.3.3 Execution phase of 3GPP TS 23.502 V17.3.0. For the remaining operations except for the application examples described below, Clause 4.9.1.3.3 Execution phase of 3GPP TS 23.502 V17.3.0 can be applied as is.

[0477] For step 7, the following comments apply:

[0478] The AMF may send a request message (e.g., a request message based on Nsmf_PDU session_UpdateSMContextRequest) to the SMF. If the AMF determines that the PDU session is associated with an S-NSSAI that is not supported at the current UE location, the AMF may inform the SMF that the S-NSSAI is not supported at the current UE location. The SMF may deactivate the UP connection of the PDU session.

[0479] 10. Tenth Example of the Disclosure of the Present Specification

[0480] The tenth example of the disclosure of this specification may represent a specific embodiment based on a combination of at least one of the first to ninth examples of the disclosure of this specification.

[0481] Below, with reference to FIG. 18, examples of operations performed by various entities, such as UE operations and AMF operations, according to various examples of the disclosure of this specification are described.

[0482] The following drawings are created to illustrate a specific example of the present specification. The names of specific devices and names of specific signals / messages / fields described in the drawings are presented for illustrative purposes only, and the technical features of the present specification are not limited to the specific names used in the following drawings.

[0483] FIG. 18 shows an example of a procedure according to the tenth example of the disclosure of this specification.

[0484] The example of Figure 18 illustrates an example of the operation of a terminal (e.g., UE) and / or a network (e.g., AMF, UPF, SMF, etc.) according to various examples of the disclosure of the present specification described above. For reference, the operation of the terminal and / or the network described in the example of Figure 18 is merely an example, and the scope of the disclosure of the present specification is not limited by the content described in the example of Figure 18. For example, the terminal and / or the network can perform the operations described in the first to ninth examples of the disclosure of the present specification even if they are not described in the example of Figure 18.

[0485] In step S1801, the UE may send a registration request message to the AMF. For example, the registration request message may include a requested NSSAI including information for one or more network slices requested by the UE.

[0486] In step S1802, the AMF may send a response message to the UE. Some of the network slices requested by the UE are supported only in a subset of the registration area (e.g., one or more TAs among a number of TAs included in the registration area). In this case, the AMF may include information on the network slices supported at the current UE location in the Allowed NSSAI, and information on the network slices not supported at the current UE location in the Rejected NSSAI.

[0487] As described in one embodiment of the disclosure of this specification, when a terminal moves to an area where a slice received from a network in Rejected NSSAI can be used, the terminal can be permitted to request the slice again, thereby reducing the delay time for the service. For example, the terminal can be permitted to request the slice even if it does not leave the registration area. In addition, since the AMF is a slice, it is not necessary to set the registration area small, so that the signaling for mobility management can be reduced.

[0488] As described in one embodiment of the disclosure of this specification, the AMF can send the area information (e.g., TA) in which the slice is rejected together with the Rejected NSSAI to the terminal. If the terminal leaves the rejected area even in the same registration area, it can delete the rejected slice in the Rejected NSSAI and perform the registration procedure again.

[0489] As described in one embodiment of the disclosure of this specification, when the AMF sends a Rejected NSSAI to a terminal, the AMF can store the Rejected NSSAI, and if the terminal moves to an area where the Rejected NSSAI is available again, the AMF can update the Rejected NSSAI in the terminal or update the Allowed NSSAI.

[0490] As described in one embodiment of the disclosure of this specification, when the AMF sends a Rejected NSSAI to the terminal, a slice may be available in another TA within the registration area of ​​the current terminal. In this case, if the AMF sends a new cause to the terminal to notify the terminal of this, when the terminal moves to another TA based on the corresponding cause, the slice with the new cause can be deleted in the Rejected NSSAI and the terminal can request the slice again.

[0491] As described in one embodiment of the disclosure of this specification, when a terminal receives a Rejected NSSAI, based on SIB information transmitted by the base station, the terminal can delete the Rejected NSSAI or include slice information in the Allowed NSSAI.

[0492] For reference, the operation of the terminal (e.g., UE) described herein is implemented by the devices of Figs. 1 to 4 described above. For example, the terminal (e.g., UE) may be the first device 100 or the second device 200 of Fig. 2. For example, the operation of the terminal (e.g., UE) described herein may be processed by one or more processors 102 or 202. The operation of the terminal described herein may be stored in one or more memories 104 or 204 in the form of instructions / programs (e.g., executable codes) that can be executed by one or more processors 102 or 202. The one or more processors 102 or 202 may control one or more memories 104 or 204 and one or more transceivers (105 or 206) to execute the instructions / programs stored in the one or more memories 104 or 204 to perform the operation of the terminal (e.g., UE) described in the disclosure of this specification.

[0493] The instructions for performing the operations of the terminal (e.g., UE) described in the disclosure herein may also be stored in a non-volatile computer-readable storage medium, which may be included in one or more of the memories 104 or 204. The instructions stored in the storage medium may then be executed by one or more of the processors 102 or 202 to perform the operations of the terminal (e.g., UE, UE-to-Network Relay) described in the disclosure herein.

[0494] For reference, the operation of a network node (e.g., AMF, UPF, SMF, etc.) or base station (e.g., NG-RAN, gNB, eNB, RAN, E-UTRAN, etc.) described herein is implemented by the devices of FIG. 1 to FIG. 3 described below. For example, the network node or base station may be the first device 100 or the second device 200 of FIG. 2. For example, the operation of a network node or base station described herein may be processed by one or more processors 102 or 202. The operation of a terminal described herein may be stored in one or more memories 104 or 204 in the form of instructions / programs (eginstruction, executable code) executable by one or more processors 102 or 202. The one or more processors 102 or 202 may control one or more memories 104 or 204 and one or more transceivers 106 or 206 to execute the instructions / programs stored in one or more memories 104 or 204 to perform the operation of a network node or base station described in the disclosure of this specification.

[0495] Additionally, instructions for performing the operations of the network node or base station described in this disclosure may be stored on a non-volatile (or non-transitory) computer-readable storage medium, which may be included in one or more of memories 104 or 204, and the instructions stored on the storage medium may be executed by one or more processors 102 or 202 to perform the operations of the network node or base station described in this disclosure.

[0496] Although the above describes preferred embodiments, the disclosure of this specification is not limited to such specific embodiments, and various modifications, changes, or improvements can be made within the spirit and scope of this specification and the claims.

[0497] In the exemplary system described above, the method is described based on a flowchart as a series of steps or blocks, but is not limited to the order of steps described, and a step may occur in other orders or simultaneously with other steps described above. Also, those skilled in the art will understand that the steps shown in the flowchart are not exclusive, and other steps may be included or one or more steps of the flowchart may be deleted without affecting the scope of the scope.

[0498] The claims described herein may be combined in various ways, for example, technical features of the method claims herein may be combined and implemented in an apparatus, technical features of the device claims herein may be combined and implemented in a method, technical features of the method claims herein may be combined with technical features of the device claims herein may be combined and implemented in an apparatus, and technical features of the method claims herein may be combined with technical features of the device claims herein may be combined and implemented in a method.

[0499] [Claims at the time of international application] [Claim 1] A method for performing communication by an Access and Mobility Management Function (AMF), comprising: receiving a registration request message including requested network slice selection assistance information (NSSAI) information from a User Equipment (UE); and sending a response message to the UE in response to the registration request message; The response message includes allowed NSSAI information and rejected NSSAI information, The requested NSSAI includes information related to a first network slice and information related to a second network slice; and The method, characterized in that, based on the rejected NSSAI information including information related to the first network slice, the response message includes information related to a first Tracking Area (TA) list that can be used by the first network slice. [Claim 2] The method according to claim 1, characterized in that the first TA list includes one or more TAs included in a registration area of ​​the UE. [Claim 3] The method of claim 1, further comprising: receiving a registration request message from the UE, the registration request message including a requested NSSAI including information related to the first network slice, based on the UE moving to a TA included in the first TA list. [Claim 4] The method according to claim 1, wherein the response message includes a cause value indicating that the first network slice was rejected for a TA in a registration area that was not included in the first TA list. [Claim 5] The method of claim 1 , further comprising: receiving capability information from the UE that supports non-uniform slices. [Claim 6] An AMF (Access and Mobility Management Function) that performs communication, at least one processor; and at least one memory; the at least one memory storing instructions and operably electrically connected to the at least one processor; The at least one processor performs operations according to the instructions when executed; The operation includes: receiving a registration request message including requested network slice selection assistance information (NSSAI) information from a User Equipment (UE); and sending a response message to the UE in response to the registration request message; The response message includes allowed NSSAI information and rejected NSSAI information, The requested NSSAI includes information related to a first network slice and information related to a second network slice; and Based on the rejected NSSAI information including information related to the first network slice, the response message includes information related to a first Tracking Area (TA) list that can be used by the first network slice. AMF. [Claim 7] A method for performing communication by a UE (User Equipment), comprising: sending a registration request message including requested network slice selection assistance information (NSSAI) information to an Access and Mobility Management Function (AMF); and receiving a response message from the UE in response to the registration request message; The response message includes allowed NSSAI information and rejected NSSAI information, The requested NSSAI includes information related to a first network slice and information related to a second network slice; and The method, characterized in that, based on the rejected NSSAI information including information related to the first network slice, the response message includes information related to a first Tracking Area (TA) list that can be used by the first network slice. [Claim 8] The method according to claim 7, characterized in that the first TA list includes one or more TAs included in a registration area of ​​the UE. [Claim 9] The method of claim 7, further comprising: sending a registration request message to the AMF, the registration request message including a requested NSSAI including information related to the first network slice, based on the UE moving to a TA included in the first TA list. [Claim 10] The method according to claim 7, wherein the response message includes a cause value indicating that the first network slice was rejected for a TA in a registration area that was not included in the first TA list. [Claim 11] The method of claim 7, further comprising: sending capability information that supports non-homogeneous slices to the AMF. [Claim 12] A UE (User Equipment: terminal) that performs communication, at least one processor; and at least one memory; the at least one memory storing instructions and operably electrically connected to the at least one processor; The at least one processor performs operations according to the instructions when executed; The operation includes: sending a registration request message including requested network slice selection assistance information (NSSAI) information to an Access and Mobility Management Function (AMF); and receiving a response message from the UE in response to the registration request message; The response message includes allowed NSSAI information and rejected NSSAI information, The requested NSSAI includes information related to a first network slice and information related to a second network slice; and The UE is characterized in that, based on the rejected NSSAI information including information related to the first network slice, the response message includes information related to a first Tracking Area (TA) list that can be used by the first network slice. [Claim 13] The UE according to claim 12, wherein the UE is an autonomous vehicle that communicates with at least one of a mobile terminal, a network, and an autonomous vehicle other than the UE. [Claim 14] An apparatus in mobile communications, comprising: at least one processor; and at least one memory; the at least one memory storing instructions and operably electrically connected to the at least one processor; The at least one processor performs operations according to the instructions when executed; The operation includes: generating a registration request message including requested network slice selection assistance information (NSSAI) information; and obtaining a response message in response to the registration request message; The response message includes allowed NSSAI information and rejected NSSAI information, The requested NSSAI includes information related to a first network slice and information related to a second network slice; and The apparatus, characterized in that, based on the rejected NSSAI information including information related to the first network slice, the response message includes information related to a first Tracking Area (TA) list that can be used by the first network slice. [Claim 15] A non-transitory computer readable medium (CRM) storing instructions, The at least one processor performs operations according to the instructions when executed; The operation includes: generating a registration request message including requested network slice selection assistance information (NSSAI) information; and obtaining a response message in response to the registration request message; The response message includes allowed NSSAI information and rejected NSSAI information, The requested NSSAI includes information related to a first network slice and information related to a second network slice; and The CRM is characterized in that, based on the rejected NSSAI information including information related to the first network slice, the response message includes information related to a first Tracking Area (TA) list that can be used by the first network slice.

Claims

1. A method for performing communication by an Access and Mobility Management Function (AMF), comprising: receiving a registration request message including requested network slice selection assistance information (NSSAI) information from a UE (User Equipment); and sending a response message to the UE in response to the registration request message; The response message includes allowed NSSAI information and rejected NSSAI information, The requested NSSAI includes information related to a first network slice and information related to a second network slice; and The method, based on the rejected NSSAI information including information related to the first network slice, wherein the response message includes information related to a first tracking area (TA) list that can be used by the first network slice.

2. The method of claim 1, wherein the first TA list includes one or more TAs included in a registration area of ​​the UE.

3. 2. The method of claim 1, further comprising: receiving a registration request message from the UE, the registration request message including a requested NSSAI including information related to the first network slice, based on the UE moving to a TA included in the first TA list.

4. 2. The method of claim 1, wherein the response message includes a cause value indicating that the first network slice was rejected for a TA in a registration area that was not included in the first TA list.

5. The method of claim 1 , further comprising: receiving capability information from the UE that supports non-uniform slices.

6. An AMF (Access and Mobility Management Function) that performs communication, At least one processor; and at least one memory; the at least one memory storing instructions and operably electrically connected to the at least one processor; The at least one processor performs operations according to the instructions when the instructions are executed; The operation includes: receiving a registration request message including requested network slice selection assistance information (NSSAI) information from a UE (User Equipment); and sending a response message to the UE in response to the registration request message; The response message includes allowed NSSAI information and rejected NSSAI information, The requested NSSAI includes information related to a first network slice and information related to a second network slice; and Based on the fact that the rejected NSSAI information includes information related to the first network slice, the response message includes information related to a first tracking area (TA) list that can be used by the first network slice. AMF.

7. A method for performing communication by a UE (User Equipment), comprising: Sending a registration request message including requested network slice selection assistance information (NSSAI) information to an Access and Mobility Management Function (AMF); and receiving a response message from the UE in response to the registration request message; The response message includes allowed NSSAI information and rejected NSSAI information, The requested NSSAI includes information related to a first network slice and information related to a second network slice; and The method, based on the rejected NSSAI information including information related to the first network slice, wherein the response message includes information related to a first tracking area (TA) list that can be used by the first network slice.

8. The method according to claim 7, characterized in that the first TA list includes one or more TAs included in a registration area of ​​the UE.

9. 8. The method of claim 7, further comprising: based on the UE moving to a TA included in the first TA list, sending a registration request message to the AMF, the registration request message including a requested NSSAI including information related to the first network slice.

10. The method according to claim 7, wherein the response message includes a cause value indicating that the first network slice was rejected for a TA in a registration area that was not included in the first TA list.

11. The method of claim 7 , further comprising: sending capability information of supporting non-homogeneous slices to the AMF.

12. A UE (User Equipment) that performs communication, At least one processor; and at least one memory; the at least one memory storing instructions and operably electrically connected to the at least one processor; The at least one processor performs operations according to the instructions when the instructions are executed; The operation includes: Sending a registration request message including requested network slice selection assistance information (NSSAI) information to an Access and Mobility Management Function (AMF); and receiving a response message from the UE in response to the registration request message; The response message includes allowed NSSAI information and rejected NSSAI information, The requested NSSAI includes information related to a first network slice and information related to a second network slice; and Based on the fact that the rejected NSSAI information includes information related to the first network slice, the response message includes information related to a first tracking area (TA) list that can be used by the first network slice. UE.

13. The UE according to claim 12, wherein the UE is an autonomous vehicle that communicates with at least one of a mobile terminal, a network, and an autonomous vehicle other than the UE.

14. An apparatus for mobile communications, comprising: At least one processor; and at least one memory; the at least one memory storing instructions and operably electrically connected to the at least one processor; The at least one processor performs operations according to the instructions when the instructions are executed; The operation includes: generating a registration request message including requested network slice selection assistance information (NSSAI) information; and obtaining a response message in response to the registration request message; The response message includes allowed NSSAI information and rejected NSSAI information, The requested NSSAI includes information related to a first network slice and information related to a second network slice; and The apparatus, based on the rejected NSSAI information including information related to the first network slice, the response message includes information related to a first tracking area (TA) list that can be used by the first network slice.

15. A non-transitory computer readable medium (CRM) storing instructions, comprising: The at least one processor performs operations according to the instructions when the instructions are executed; The operation includes: generating a registration request message including requested network slice selection assistance information (NSSAI) information; and obtaining a response message in response to the registration request message; The response message includes allowed NSSAI information and rejected NSSAI information, The requested NSSAI includes information related to a first network slice and information related to a second network slice; and Based on the fact that the rejected NSSAI information includes information related to the first network slice, the response message includes information related to a first tracking area (TA) list that can be used by the first network slice. CRM.

Images