Local area data network service

Abstract

One embodiment of the present disclosure provides a method. The method may comprise the steps of: receiving, from a UE, a registration request message including S-NSSAI; acquiring, from a UDM, subscriber information of the UE; and transmitting a registration acceptance message.

Description

Local Area Data Network Service

[0001] This specification relates to mobile communications.

[0002] 3GPP (3rd Generation Partnership Project) LTE (Long-Term Evolution) is a technology designed to enable high-speed packet communications. Numerous approaches have been proposed to achieve LTE's goals of reducing costs for users and operators, improving service quality, expanding coverage, and increasing system capacity. 3GPP LTE's high-level requirements include reduced cost per bit, improved service availability, flexible use of frequency bands, a simple architecture, open interfaces, and adequate power consumption for terminals.

[0003] The International Telecommunication Union (ITU) and 3GPP have begun work on developing requirements and specifications for New Radio (NR) systems. 3GPP must identify and develop the technical components necessary to successfully standardize NR, meeting both urgent market needs and the longer-term requirements outlined by the ITU Radio communication sector (ITU-R) International Mobile Telecommunications (IMT)-2020 process. NR must also be able to utilize any spectrum band up to at least 100 GHz, ensuring that it remains available for wireless communications well into the future.

[0004] NR aims to be a single technology framework that addresses all deployment scenarios, usage scenarios, and requirements, including enhanced Mobile Broadband (eMBB), massive Machine Type Communications (mMTC), and Ultra-Reliable and Low Latency Communications (URLLC). NR must be inherently forward-compatible.

[0005] Previously, there was a problem in that Local Area Data Network (LADN) services were not effectively supported. For example, cell-level UE locations were not considered.

[0006] According to one embodiment of the present disclosure, a method is provided. The method may include the steps of: receiving a registration request message including an S-NSSAI from a UE; obtaining subscriber information of the UE from a UDM; and transmitting a registration acceptance message.

[0007] According to one embodiment, a device implementing the method is provided.

[0008] According to one embodiment of the present disclosure, a method is provided. The method may include the steps of transmitting a registration request message including an S-NSSAI to an AMF; and receiving a registration acceptance message from the AMF.

[0009] According to one embodiment, a device implementing the method is provided.

[0010] Figure 1 illustrates an example of a communication system to which the implementation of this specification is applied.

[0011] Figure 2 illustrates an example of a wireless device to which the implementation of the present specification is applied.

[0012] Figure 3 shows an example of a UE to which the implementation of this specification is applied.

[0013] Figure 4 shows an example of a 5G system structure to which the implementation of this specification is applied.

[0014] Figures 5 and 6 illustrate examples of registration procedures to which the implementation of the present specification applies.

[0015] Figure 7 is an example diagram showing an example of an architecture for implementing the concept of network slicing.

[0016] Figure 8 is an exemplary diagram showing another example of an architecture for implementing the concept of network slicing.

[0017] FIG. 9 illustrates a first example of a procedure according to one embodiment of the disclosure of the present specification.

[0018] FIG. 10 illustrates a second example of a procedure according to one embodiment of the disclosure of the present specification.

[0019] FIG. 11 illustrates an example of operations according to one embodiment of the disclosure of the present specification.

[0020] The following techniques, devices, and systems can be 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 can be implemented using wireless technologies such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA can be implemented using wireless technologies such as Global System for Mobile communications (GSM), General Packet Radio Service (GPRS), or Enhanced Data rates for GSM Evolution (EDGE). OFDMA can be implemented using wireless technologies such as IEEE (Institute of Electrical and Electronics Engineers) 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 E-UMTS (Evolved UMTS) that utilizes E-UTRA.3GPP LTE uses OFDMA in the downlink (DL) and SC-FDMA in the uplink (UL). Evolution of 3GPP LTE includes LTE-A (Advanced), LTE-A Pro, and / or 5G NR (New Radio).

[0021] For convenience of explanation, the implementation of this specification is primarily described in relation to a 3GPP-based wireless communication system. However, the technical features 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.

[0022] 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.

[0023] As used herein, "A or B" can mean "only A," "only B," or "both A and B." Alternatively, 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."

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

[0025] In this specification, “at least one of A and B” may mean “only A,” “only B,” or “both A and B.” Additionally, in this specification, the expressions “at least one of A or B” or “at least one of A and / or B” may be interpreted identically to “at least one of A and B.”

[0026] Additionally, 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”. Additionally, “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”.

[0027] Additionally, parentheses used herein may mean "for example." Specifically, when indicated as "control information (PDCCH)", "PDCCH" may be proposed as an example of "control information." In other words, "control information" in this specification is not limited to "PDCCH," and "PDCCH" may be proposed as an example of "control information." Furthermore, even when indicated as "control information (i.e., PDCCH)", "PDCCH" may be proposed as an example of "control information."

[0028] Technical features individually described in a single drawing in this specification may be implemented individually or simultaneously.

[0029] Although not limited thereto, the various descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed herein may be applied to various fields requiring wireless communication and / or connectivity between devices (e.g., 5G).

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

[0031] Figure 1 illustrates an example of a communication system to which the implementation of this specification is applied.

[0032] The 5G usage scenario shown in FIG. 1 is only an example, and the technical features of this specification can be applied to other 5G usage scenarios not shown in FIG. 1.

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

[0034] Referring to FIG. 1, a 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 a network of the communication system (1), but the implementation of the present disclosure is not limited to a 5G system and can be applied to future communication systems beyond the 5G system.

[0035] The base station (200) and the network (300) may be implemented as wireless devices, and a particular wireless device may operate as a base station / network node in relation to other wireless devices.

[0036] The wireless devices (100a to 100f) represent devices that perform communication using Radio Access Technology (RAT) (e.g., 5G NR or LTE) and may also be referred to as communication / wireless / 5G devices. The wireless devices (100a to 100f) may include, but are not limited to, a robot (100a), a vehicle (100b-1 and 100b-2), an extended reality (XR) device (100c), a portable device (100d), a home appliance (100e), an Internet-of-Things (IoT) device (100f), and an artificial intelligence (AI) device / server (400). For example, the vehicles may include vehicles having wireless communication capabilities, autonomous vehicles, and vehicles capable of performing vehicle-to-vehicle communication. The vehicles may include unmanned aerial vehicles (UAVs) (e.g., drones). XR devices may include AR (Augmented Reality) / VR (Virtual Reality) / MR (Mixed Reality) devices, and may be implemented in the form of HMD (Head-Mounted Device) and HUD (Head-Up Display) mounted on vehicles, televisions, smartphones, computers, wearable devices, home appliances, digital signs, vehicles, robots, etc. Portable devices may include smartphones, smart pads, wearable devices (e.g., smart watches or smart glasses), and computers (e.g., laptops). Home appliances may include TVs, refrigerators, and washing machines. IoT devices may include sensors and smart meters.

[0037] In this specification, 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 laptop computer, a digital broadcasting 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 autonomous driving function, a connected car, 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 / environmental device, a 5G service-related device, or a 4th industrial revolution-related device.

[0038] Wireless devices (100a to 100f) can be 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) can be connected to an AI server (400) via the network (300). The network (300) can be configured using a 3G network, a 4G (e.g., LTE) network, a 5G (e.g., NR) network, and a network after 5G. 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). Additionally, IoT devices (e.g., sensors) can communicate directly with other IoT devices (e.g., sensors) or other wireless devices (100a to 100f).

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

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

[0041] The NR frequency band can be defined by two types of frequency ranges (FR1 and FR2). The numerical values ​​of the frequency ranges can be changed. For example, the two types of frequency ranges (FR1 and FR2) can be as shown in Table 1 below. For convenience of explanation, among the frequency ranges used in the NR system, FR1 can mean the "sub 6 GHz range," and FR2 can mean the "above 6 GHz range," which can be called millimeter wave (mmW).

[0042] Frequency Range DefinitionFrequency RangeSubcarrier SpacingFR1450MHz - 6000MHz15, 30, 60kHzFR224250MHz - 52600MHz60, 120, 240kHz

[0043] As described above, the numerical value of the frequency range of the NR system can be changed. For example, FR1 may include a band from 410 MHz to 7125 MHz, as shown in Table 2 below. That is, FR1 may include frequency bands above 6 GHz (or 5850, 5900, 5925 MHz, etc.). For example, the frequency bands above 6 GHz (or 5850, 5900, 5925 MHz, etc.) included within FR1 may include unlicensed bands. Unlicensed bands can be used for various purposes, such as for communications for vehicles (e.g., autonomous driving).

[0044] Frequency Range DefinitionFrequency RangeSubcarrier SpacingFR1410MHz - 7125MHz15, 30, 60kHzFR224250MHz - 52600MHz60, 120, 240kHz

[0045] Here, the wireless communication technology implemented in the wireless device of the present specification may include not only LTE, NR, and 6G, but also Narrowband IoT (NB-IoT) for low-power communication. For example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology and may be implemented with standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the above-described names. Additionally or alternatively, the wireless communication technology implemented in the wireless device of the present specification may perform communication based on LTE-M technology. For example, LTE-M technology may be an example of LPWAN technology and may be called by various names such as eMTC (enhanced MTC). For example, LTE-M technology can be implemented by 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-described names. Additionally or alternatively, the wireless communication technology implemented in the wireless device of the present specification can include at least one of ZigBee, Bluetooth, and / or LPWAN considering low-power communication, and is not limited to the above-described names. For example, ZigBee technology can create PANs (Personal Area Networks) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and can be called by various names.

[0046] Figure 2 illustrates an example of a wireless device to which the implementation of the present specification is applied.

[0047] In FIG. 2, the first wireless device (100) and / or the second wireless device (200) may be implemented in various forms depending on the use case / service. For example, {the first wireless device (100) and the second wireless device (200)} may correspond to at least one of {the wireless devices (100a to 100f) and the base station (200)}, {the wireless devices (100a to 100f) and the wireless devices (100a to 100f)}, and / or {the base station (200) and the base station (200)} of FIG. 1. The first wireless device (100) and / or the second wireless device (200) may be configured by various components, devices / parts, and / or modules.

[0048] The first wireless device (100) may include at least one transceiver, such as a transceiver (106), at least one processing chip, such as a processing chip (101), and / or one or more antennas (108).

[0049] The processing chip (101) may include at least one processor, such as a processor (102), and at least one memory, such as a memory (104). Additionally and / or alternatively, the memory (104) may be located external to the processing chip (101).

[0050] The processor (102) may control the memory (104) and / or the transceiver (106) and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed herein. For example, the processor (102) may process information in the memory (104) to generate 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 second information / signal via the transceiver (106) and store information obtained by processing the second information / signal in the memory (104).

[0051] A memory (104) may be operatively connected to the processor (102). The memory (104) may store various types of information and / or instructions. The memory (104) may store firmware and / or software code (105) that implements code, instructions and / or sets of instructions that, when executed by the processor (102), perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein. For example, the firmware and / or software code (105) may implement instructions that, when executed by the processor (102), perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein. For example, the firmware and / or software code (105) may control the processor (102) to perform one or more protocols. For example, the firmware and / or software code (105) may control the processor (102) to perform one or more air interface protocol layers.

[0052] Here, the processor (102) and memory (104) may be part of a communication modem / circuit / chip designed to implement a RAT (e.g., LTE or NR). A transceiver (106) may be connected to the processor (102) and may transmit and / or receive wireless signals via one or more antennas (108). Each transceiver (106) may include a transmitter and / or a receiver. The transceiver (106) may be used interchangeably with an RF (Radio Frequency) unit. In the present specification, the first wireless device (100) may represent a communication modem / circuit / chip.

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

[0054] The processing chip (201) may include at least one processor, such as a processor (202), and at least one memory, such as a memory (204). Additionally and / or alternatively, the memory (204) may be located external to the processing chip (201).

[0055] The processor (202) may control the memory (204) and / or the transceiver (206) and may be configured to implement the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed herein. For example, the processor (202) may process information in the memory (204) to generate 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 fourth information / signal via the transceiver (206) and store information obtained by processing the fourth information / signal in the memory (204).

[0056] A memory (204) may be operatively connected to the processor (202). The memory (204) may store various types of information and / or instructions. The memory (204) may store firmware and / or software code (205) that implements code, instructions and / or sets of instructions that, when executed by the processor (202), perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein. For example, the firmware and / or software code (205) may implement instructions that, when executed by the processor (202), perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein. For example, the firmware and / or software code (205) may control the processor (202) to perform one or more protocols. For example, the firmware and / or software code (205) may control the processor (202) to perform one or more air interface protocol layers.

[0057] Here, the processor (202) and memory (204) may be part of a communication modem / circuit / chip designed to implement a RAT (e.g., LTE or NR). A transceiver (206) may be connected to the processor (202) and may transmit and / or receive wireless signals via one or more antennas (208). Each transceiver (206) may include a transmitter and / or a receiver. The transceiver (206) may be used interchangeably with the RF unit. In the present specification, the second wireless device (200) may represent a communication modem / circuit / chip.

[0058] Hereinafter, hardware elements of the wireless device (100, 200) will be described in more detail. Although not limited thereto, one or more protocol layers may be implemented by one or more processors (102, 202). 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), one or more Service Data Units (SDUs), messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed herein. One or more processors (102, 202) can generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data or information according to the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed herein and provide the signals to one or more transceivers (106, 206). One or more processors (102, 202) can receive signals (e.g., baseband signals) from one or more transceivers (106, 206) and obtain PDUs, SDUs, messages, control information, data or information according to the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed herein.

[0059] The one or more processors (102, 202) may be referred to as a controller, a microcontroller, a microprocessor, and / or a microcomputer. The one or more processors (102, 202) may be implemented by hardware, firmware, software, and / or a combination thereof. For example, 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) may be included in the one or more processors (102, 202). For example, the one or more processors (102, 202) may be configured by a set of a communication control processor, an Application Processor (AP), an Electronic Control Unit (ECU), a Central Processing Unit (CPU), a Graphic Processing Unit (GPU), and a Memory Control Processor. One or more memories (104, 204) may be coupled to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, codes, instructions and / or commands. The one or more memories (104, 204) may be configured as random access memory (RAM), dynamic RAM (DRAM), read-only memory (ROM), erasable programmable ROM (EPROM), flash memory, volatile memory, nonvolatile memory, hard drive, register, cache memory, computer readable storage media and / or combinations thereof.One or more memories (104, 204) may be located internally and / or externally to one or more processors (102, 202). Additionally, one or more memories (104, 204) may be connected to one or more processors (102, 202) via various technologies, such as wired or wireless connections.

[0060] One or more transceivers (106, 206) can transmit user data, control information, wireless signals / channels, etc., referred to in the descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed herein to one or more other devices. One or more transceivers (106, 206) can receive user data, control information, wireless signals / channels, etc., referred to in the descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed herein from one or more other devices. For example, one or more transceivers (106, 206) can be coupled to one or more processors (102, 202) and can transmit and receive wireless signals. For example, one or more processors (102, 202) can control one or more transceivers (106, 206) to transmit user data, control information, wireless signals, etc., to one or more other devices. Additionally, 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.

[0061] One or more transceivers (106, 206) may be coupled to one or more antennas (108, 208). Additionally and / or alternatively, one or more transceivers (106, 206) may include one or more antennas (108, 208). One or more transceivers (106, 206) may be configured to transmit and receive user data, control information, wireless signals / channels, etc., as described in the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed herein via one or more antennas (108, 208). In the present disclosure, one or more antennas (108, 208) may be multiple physical antennas or multiple logical antennas (e.g., antenna ports).

[0062] One or more transceivers (106, 206) may convert received user data, control information, wireless signals / channels, etc. from RF band signals to baseband signals in order to process the received user data, control information, wireless signals / channels, etc. using one or more processors (102, 202). One or more transceivers (106, 206) may convert processed user data, control information, wireless signals / channels, etc. from baseband signals to RF band signals using one or more processors (102, 202). For this purpose, one or more transceivers (106, 206) may include an (analog) oscillator and / or a filter. For example, one or more transceivers (106, 206) may up-convert an OFDM baseband signal to an OFDM signal via an (analog) oscillator and / or 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) may receive an OFDM signal at a carrier frequency and down-convert the OFDM signal to an OFDM baseband signal via an (analog) oscillator and / or filter under the control of one or more processors (102, 202).

[0063] Although not illustrated in FIG. 2, the wireless device (100, 200) may further include additional components. The additional components (140) may be configured in various ways depending on the type of the wireless device (100, 200). For example, the additional components (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 driving device, and a computing device. The additional components (140) may be connected to one or more processors (102, 202) via various technologies, such as a wired or wireless connection.

[0064] In the implementation of this specification, a UE can operate as a transmitter in the uplink and as a receiver in the downlink. In the implementation of this specification, a base station can operate as a receiver in the UL and as a transmitter in the DL. For the sake of convenience of description, it is mainly assumed below 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 released in the first wireless device (100) can be configured to perform UE operations according to the implementation of this specification or to control a transceiver (106) to perform UE operations according to the implementation of this specification. A processor (202) connected to, mounted on, or released in the second wireless device (200) can be configured to perform base station operations according to the implementation of this specification or to control a transceiver (206) to perform base station operations according to the implementation of this specification.

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

[0066] Figure 3 shows an example of a UE to which the implementation of this specification is applied.

[0067] Referring to FIG. 3, the UE (100) can correspond to the first wireless device (100) of FIG. 2.

[0068] The UE (100) includes a processor (102), memory (104), a transceiver (106), one or more antennas (108), a power management module (141), a battery (142), a display (143), a keypad (144), a SIM (Subscriber Identification Module) card (145), a speaker (146), and a microphone (147).

[0069] The processor (102) may be configured to implement the descriptions, functions, procedures, proposals, methods and / or flowcharts disclosed herein. The processor (102) may be configured to control one or more other components of the UE (100) to implement the descriptions, functions, procedures, proposals, methods and / or flowcharts disclosed herein. A layer of a radio interface protocol may be implemented in the processor (102). The processor (102) may include an ASIC, other chipsets, logic circuits and / or data processing devices. The processor (102) may be an application processor. The processor (102) may include at least one of a DSP, a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), and a modem (modulator and demodulator). An example of the processor (102) is the SNAPDRAGON manufactured by Qualcomm®. TM Series processors, EXYNOS made by Samsung® TM Series processors, A-series processors made by Apple®, HELIO made by MediaTek® TM ATOM series processors made by Intel® TM It can be found in the series processors or the corresponding next-generation processors.

[0070] Memory (104) is operatively coupled to the processor (102) and stores various information for operating the processor (102). Memory (104) may include ROM, RAM, flash memory, memory cards, storage media, and / or other storage devices. When the implementation is implemented in software, the techniques described herein may be implemented using modules (e.g., procedures, functions, etc.) that perform the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed herein. The modules may be stored in memory (104) and executed by the processor (102). Memory (104) may be implemented within the processor (102) or external to the processor (102), in which case it may be communicatively coupled to the processor (102) via various methods known in the art.

[0071] A transceiver (106) is operably coupled to the processor (102) and transmits and / or receives a radio signal. The transceiver (106) includes a transmitter and a receiver. The transceiver (106) may include a baseband circuit for processing a radio frequency signal. The transceiver (106) controls one or more antennas (108) to transmit and / or receive a radio signal.

[0072] The power management module (141) manages the power of the processor (102) and / or the transceiver (106). The battery (142) supplies power to the power management module (141).

[0073] The display (143) outputs the results processed by the processor (102). The keypad (144) receives input to be used by the processor (102). The keypad (144) can be displayed on the display (143).

[0074] A SIM card (145) is an integrated circuit that securely stores an International Mobile Subscriber Identity (IMSI) and associated keys, and is used to identify and authenticate subscribers in mobile devices such as mobile phones and computers. Additionally, many SIM cards can store contact information.

[0075] The speaker (146) outputs sound-related results processed by the processor (102). The microphone (147) receives sound-related input to be used by the processor (102).

[0076] Figure 4 shows an example of a 5G system structure to which the implementation of this specification is applied.

[0077] The 5G system (5GS; 5G system) structure consists of the following network functions (NF; Network Function).

[0078] - AUSF (Authentication Server Function)

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

[0080] - DN (Data Network), for example, operator services, Internet access, or third-party services.

[0081] - USDF (Unstructured Data Storage Function)

[0082] - NEF (Network Exposure Function)

[0083] - I-NEF (Intermediate NEF)

[0084] - NRF (Network Repository Function)

[0085] - NSSF (Network Slice Selection Function)

[0086] - PCF (Policy Control Function)

[0087] - SMF (Session Management Function)

[0088] - UDM (Unified Data Management)

[0089] - UDR (Unified Data Repository)

[0090] - UPF (User Plane Function)

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

[0092] - AF (Application Function)

[0093] - UE (User Equipment)

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

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

[0096] - NWDAF (Network Data Analytics Function)

[0097] - CHF (CHarging Function)

[0098] 또한, 다음과 같은 네트워크 기능이 고려될 수 있다.

[0099] - N3IWF (Non-3GPP InterWorking Function)

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

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

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

[0103] For clarity of the point-to-point diagram in Figure 4, UDSF, NEF, and NRF are not illustrated. However, all network functions shown can interact with UDSF, UDR, NEF, and NRF as needed.

[0104] For clarity, the connection between UDR and other NFs (e.g., PCF) is not shown in Fig. 4. For clarity, the connection between NWDAF and other NFs (e.g., PCF) is not shown in Fig. 4.

[0105] The 5G system architecture includes the following benchmarks:

[0106] - N1: Reference point between UE and AMF.

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

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

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

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

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

[0112] The following benchmarks illustrate the interactions that exist between NF services in NF.

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

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

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

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

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

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

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

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

[0121] - N15: Reference point between PCF and AMF for non-roaming scenarios, and reference point between PCF and AMF of visited network for roaming scenarios.

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

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

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

[0125] Describes the registration procedure. See section 4.2.2.2 of 3GPP TS 23.502 V16.3.0 (2019-12).

[0126] Figures 5 and 6 illustrate examples of registration procedures to which the implementation of the present specification applies.

[0127] A UE must register with the network to receive services, enable mobility tracking, and enable reachability. The UE initiates the registration process using one of the following registration types:

[0128] - Initial registration for 5GS; or

[0129] - mobility registration update; or

[0130] - Periodic registration update; or

[0131] - Emergency registration

[0132] The general registration procedures of Figures 5 and 6 apply to all registration procedures described above, but periodic registration updates do not need to include all parameters used in other registration procedures.

[0133] The general registration procedures of Figures 5 and 6 can also be used to register a UE for a 3GPP connection when it is already registered for a non-3GPP connection, and vice versa. Registering a UE for a 3GPP connection when it is already registered for a non-3GPP connection scenario may require an AMF change.

[0134] First, the procedure of Fig. 5 is described.

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

[0136] The registration request message may include AN parameters. For NG-RAN, the AN parameters include, for example, the 5G SAE temporary mobile subscriber identity (5G-S-TMSI) or globally unique AMF ID (GUAMI), the selected public land mobile network (PLMN) ID (or PLMN ID and network identifier (NID)), and the 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.

[0137] A registration request message may include a registration type. The registration type indicates whether the UE wants to perform an initial registration (i.e., the UE is in RM-DEREGISTERED state), or a mobility registration update (i.e., the UE is in RM-REGISTERED state and the registration procedure is initiated because the UE moves, or the UE wants to update its capabilities or protocol parameters, or because the UE requests a change in the set of network slices it is allowed to use), or a periodic registration update (i.e., the UE is in RM-REGISTERED state and the registration procedure is initiated because of expiration of the periodic registration update timer), or an emergency registration (i.e., the UE is in restricted service state).

[0138] When a UE performs initial registration, the UE indicates its UE ID in the registration request message, listed in decreasing priority order.

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

[0140] ii) Native 5G-GUTI (if available) allocated by the PLMN in which the UE is attempting to register;

[0141] iii) Native 5G-GUTI allocated by a PLMN equivalent to the PLMN in which the UE is attempting to register;

[0142] iv) Native 5G-GUTI allocated by another PLMN (if available);

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

[0144] If a UE performing initial registration has both a valid EPS GUTI and a native 5G-GUTI, the UE also indicates the native 5G-GUTI as an additional GUTI. If more than one native 5G-GUTI is available, the UE selects a 5G-GUTI from items (ii)-(iv) in decreasing priority order in the list above.

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

[0146] For 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 (Permanent Equipment Identifier) ​​is included. Otherwise, the 5G-GUTI is included, indicating the last serving AMF.

[0147] The registration request message may also include security parameters, PDU session status, etc. 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 via a 3GPP connection and a non-3GPP connection, the PDU session status indicates the PDU session currently established in the PLMN in the UE.

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

[0149] If 5G-S-TMSI or GUAMI is 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 the requested NSSAI, if available.

[0150] When the UE is in CM-CONNECTED state, (R)AN can forward a registration request message to AMF based on the N2 connection of the UE.

[0151] If the (R)AN cannot select an appropriate AMF, the (R)AN performs AMF selection by forwarding a registration request message to the AMF configured in the (R)AN.

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

[0153] The registration request message may contain all of the information and / or part of the information contained in the registration request message received from the UE described in step 1.

[0154] 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 where the UE is camping, and a UE context request indicating that a UE context including security information should be established in the NG-RAN. When NG-RAN is used, the N2 parameter also includes an establishment cause.

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

[0156] (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 may invoke the Namf_Communication_UEContextTransfer service operation to the previous AMF, including the full registration request non-access stratum (NAS) message to request the UE's SUPI and UE context.

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

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

[0159] (7) Step 7: The UE may respond with an Identity Response message including the SUCI. The UE derives the SUCI using the provided public key of the home PLMN (HPLMN).

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

[0161] (9) Step 9: Authentication / security can be established by UE, new AMF, AUSF and / or UDM.

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

[0163] (11) Step 11: If the PEI was not provided by the UE or was not retrieved from the previous AMF, the new AMF may initiate the ID request procedure by sending an Identity Request message to the UE to retrieve the PEI. The PEI is transmitted encrypted, except when the UE performs emergency registration and cannot be authenticated.

[0164] (12) Step 12: Optionally, the new AMF can initiate ME ID checking by calling the N5g-eir_EquipmentIdentityCheck_Get service operation.

[0165] Now, the procedure of Fig. 6 following the procedure of Fig. 5 is described.

[0166] (13) Step 13: When step 14 below is performed, the new AMF can select a UDM based on SUPI, and the UDM can select a UDR instance.

[0167] (14) Step 14: New AMFs can be registered with UDM.

[0168] (15) Step 15: New AMF can select PCF.

[0169] (16) Step 16: The new AMF may optionally perform AM policy association establishment / modification.

[0170] (17) Step 17: The new AMF can send update / release SM context messages (e.g., Nsmf_PDUSession_UpdateSMContext and / or Nsmf_PDUSession_ReleaseSMContext) to the SMF.

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

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

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

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

[0175] The new AMF sends the UE a Registration Accept message indicating that the registration request has been accepted. If the new AMF allocates a new 5G-GUTI, it includes the 5G-GUTI. If the UE is already in the RM-REGISTERED state through another connection to 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 a 5G-GUTI, the UE uses the 5G-GUTI assigned to the existing registration for the new registration. If the new AMF allocates a new registration area, it sends the registration area to the UE in the Registration Accept message. If the Registration Accept message does not include a registration area, the UE considers the previous registration area to be valid. Mobility Restrictions are included if mobility restrictions apply to the UE and the registration type is not emergency registration. The new AMF indicates the PDU sessions established for the UE in the PDU Session State. The UE locally removes internal resources associated with PDU sessions that are not marked as established in the received PDU Session State. When 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 in the current PLMN that are not marked as established in the received PDU session status. If PDU session status information is present in the Registration Accept message, the new AMF indicates the PDU session status to the UE.

[0176] The Allowed NSSAI provided in the Registration Accept message is valid for the registration area and applies to all PLMNs that have a tracking area included in the registration area. The Mapping of Allowed NSSAIs maps HPLMN S-NSSAIs to each S-NSSAI of the Allowed NSSAIs. The Mapping of Configured NSSAIs maps HPLMN S-NSSAIs to each S-NSSAI of the Configured NSSAI for the serving PLMN.

[0177] Additionally, optionally, the new AMF performs UE policy association establishment.

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

[0179] The UE may send a registration complete message to the new AMF to confirm that a new 5G-GUTI has been allocated.

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

[0181] (24) Step 24: AMF can perform information updates on UDM.

[0182] (25) Step 25: The UE may execute a network slice-specific authentication and authorization (NSSAA) procedure.

[0183] Network Slice

[0184] Below, we explain network slicing to be introduced in next-generation mobile communications.

[0185] Next-generation mobile communications introduce the concept of network slicing to provide diverse services through a single network. Here, a network slicing refers to a combination of network nodes with the functions necessary to provide a specific service. The network nodes that make up a slice instance can be either hardware-independent or logically independent.

[0186] Each slice instance can be composed of any combination of nodes required to form the entire network. In this case, a single slice instance can provide services to a UE independently.

[0187] Alternatively, a slice instance may be composed of a combination of nodes within the network. In this case, the slice instance may not provide services to the UE independently, but may instead collaborate with other existing network nodes to provide services to the UE. Furthermore, multiple slice instances may collaborate to provide services to the UE.

[0188] Slice instances differ from dedicated core networks in that the entire network, including the core network (CN) nodes and the RAN, can be separated. Furthermore, slice instances differ from dedicated core networks in that network nodes can be logically separated.

[0189] Note that for network slices, quotas can be used.

[0190] For example, a quota associated with a network slice may include a quota for a maximum number of UEs. The quota for the maximum number of UEs may refer to the maximum number of terminals that can simultaneously use the network slice. For example, each network slice information may include quota information for a maximum number of UEs (e.g., 10, 1,000,000, etc.).

[0191] For example, a quota associated with a network slice may include a quota for the maximum number of PDU sessions. The quota for the maximum number of PDU sessions may refer to the maximum number of concurrent PDU sessions supported by the network slice. For example, the maximum number of concurrent PDU sessions supported by the network slice may refer to the maximum number of PDU sessions that can be simultaneously established within a network slice associated with a Data Network Name (DNN) defined by the S-NSSAI.

[0192] In 5G mobile communications, network slice quota event notifications may be supported within a network slice. For example, event notifications regarding quotas related to a network slice may be supported. For example, an AF may request an event notification regarding quotas related to a network slice from 5GS. Then, the AF may receive quota notifications for attributes related to the network slice from 5GS. For example, the 5GS may notify the AF whether the quota for a specific attribute has reached a specified threshold. Then, the AF may influence 5GS routing decisions.

[0193] Figure 7 is an example diagram showing an example of an architecture for implementing the concept of network slicing.

[0194] As can be seen from Figure 7, a core network (CN) can be divided into multiple slice instances. Each slice instance can include one or more CP functional nodes and UP functional nodes.

[0195] Each UE can use a network slice instance suitable for its service through the RAN.

[0196] Unlike the example shown in FIG. 7, each slice instance may share one or more of the CP function nodes and UP function nodes with other slice instances. This is described below with reference to FIG. 8.

[0197] Figure 8 is an exemplary diagram showing another example of an architecture for implementing the concept of network slicing.

[0198] Referring to FIG. 8, multiple UP function nodes are clustered, and similarly multiple CP function nodes are clustered.

[0199] And, referring to FIG. 8, slice instance #1 (or referred to as instance #1) within the core network includes a first cluster of UP functional nodes. And, the slice instance #1 shares a cluster of CP functional nodes with slice #2 (or referred to as instance #2). The slice instance #2 includes a second cluster of UP functional nodes.

[0200] The illustrated NSSF selects a slice (or instance) that can accommodate the UE's service.

[0201] The illustrated UE can use service #1 through slice instance #1 selected by the NSSF, and can also use service #2 through slice instance #2 selected by the N.

[0202] LADN service, which provides services based on LADN service area, was introduced.

[0203] According to the prior art, the LADN service area is defined in Tracking Area (TA) units.

[0204] For example, if multiple cells exist within a TA, S-NSSAI may or may not be allowed in a specific cell. In this case, conventional LADN services could not support conditions related to S-NSSAI.

[0205] GMEC (Generic Group Management, Exposure, and Communication enhancements) is being discussed. For example, methods for effectively performing general group management are being discussed. To this end, Extended LADN information has been newly defined.

[0206] For example, Extended LADN information may include a LADN Data Network Name (DNN), an S-NSSAI associated with the LADN DNN, and a LADN service area associated with the LADN DNN. Here, the LADN service area may be configured as a Tracking Area list existing in a Registration Area to which the UE can connect. For example, the LADN service area may include a Tracking Area list. A higher-level application or SMF, etc., allows the UE to perform a specific service (e.g., LADN service) only within the LADN service area. For example, an application, a network entity (e.g., AMF, SMF), and the UE may be configured so that only a specific DNN can provide a service at a specific location. In addition, the higher-level application or SMF, etc., may allow data transmission to the UE only to the corresponding location and DNN.

[0207] For reference, in the disclosure of this specification, UE and terminal may be used as terms having the same meaning.

[0208] To provide LADN service to a UE, the UE and the NW (e.g., SMF, AMF, etc.) can determine whether the UE exists within or outside the LADN service area. If the NW determines that the UE does not exist within the LADN service area, the NW does not perform data transmission for the Protocol Data Unit (PDU) (or Packet Data Unit) session related to the LADN service. Among the NW entities, the SMF manages data transmission for the PDU session. The AMF manages mobility management. Therefore, when a UE moves, the AMF can inform the SMF of information regarding whether the UE exists within the LADN service area. The SMF can determine whether to perform transmission for the PDU session or to stop transmission based on the information received from the AMF.

[0209] According to the prior art, AMF uses the LADN service area based on the Tracking area list included in the registration area. AMF determines whether a terminal is located within the LADN service area based on the LADN service area based on the Tracking area list.

[0210] Meanwhile, several methods for handling S-NSSAI, such as partially allowed NSSAI, S-NSSAI time validity information, and S-NSSAI location validity information, are being discussed.

[0211] For example, a temporarily available network slice can be used. For example, S-NSSAI time validity information can be used to process an S-NSSAI that is only available during a specific time period. Based on the S-NSSAI time validity information, the UE and the NW can temporarily use the S-NSSAI only during a specific time period. For example, the NW provides the UE with the start time, end time, recurrence pattern, and recurrence end time of the temporarily available network slice. Based on this, the S-NSSAI can only be used during the available time period.

[0212] According to the prior art, if there is no S-NSSAI or if the S-NSSAI is not associated with the LADN, the AMF can determine the UE presence in the LADN service area as out of the LADN service area.

[0213] However, the prior art could not support LADN service for S-NSSAI related to a temporarily available network slice.

[0214] For example, if there is an S-NSSAI related to a temporarily available network slice, the network slice may not be available at a certain time or under certain conditions. In this case, even though the terminal and the network are in a situation where they cannot perform LADN service, the prior art does not determine this situation as being out of the LADN service area. In other words, the prior art cannot consider that the temporarily available network slice is unavailable. Therefore, in a situation where the temporarily available network slice is unavailable, the terminal and / or the network can transmit data based on the PDU session.

[0215] Specifically, according to the prior art, AMF determines that a UE in a LADN service area is out of the LADN service area in the following cases:

[0216] - When the DNN used for LADN is included in the LADN information and the UE is outside the LADN service area indicated in the LADN information;

[0217] - When the DNN and S-NSSAI used for LADN are included in the extended LADN information and the UE is located outside the LADN service area indicated in the extended LADN information;

[0218] - If the DNN used for LADN is included in the extended LADN information and there is no S-NSSAI provided by the UE to establish a PDU session for LADN; or

[0219] - When the DNN used for the LADN is included in the extended LADN information and the S-NSSAI provided by the UE to establish a PDU session for the LADN is not associated with that LADN.

[0220] Additionally, the service area for a network slice may not match the deployed tracking area. In this case, the AMF can inform the UE of the S-NSSAI location validity information and the list of cells where the S-NSSAI is available. In addition, the UE can receive the ID of the connected current serving cell from the lower layer. In this case, the UE can check whether the UE is in an available cell and whether the network slice is within the area of ​​service. For example, the UE can check whether the network slice is available within the area of ​​service. In other words, the UE or the AMF can perform a LADN service area check through S-NSSAI handling. For example, the AMF can determine whether S-NASSAI is available on a tracking area basis. If the AMF informs the SMF that the UE is outside the LADN service area, the SMF can release the corresponding PDU session.

[0221] However, according to the prior art, whether a terminal exists within the LADN service area is checked by the terminal or AMF in units of tracking areas of the LADN service area. Therefore, when Extended LADN information and S-NSSAI location validity information are configured together, the AMF must also check whether the terminal's S-NSSAI exists within the NS-AoS.

[0222] Additionally, the current extended LADN information may include an allowed NSSAI. Based on the allowed NSSAI, an S-NSSAI carrying a PDU session transmitting a LADN DNN mapped to the LADN service area may be determined.

[0223] However, the current network slice may not be allowed in all TAs in the current registration area, and may be rejected in some TAs. In addition, the TAs available in the partially allowed NSSAI may not be aligned with the TAs in the LADN service area. Therefore, the AMF must determine the S-NSSAI of the extended LADN information based on the allowed NSSAI or the partially allowed NSSAI. For example, the AMF can transmit the extended LADN information that includes the partially allowed NSSAI and the allowed NSSAI. When the AMF announces the partially allowed NSSAI, it is equivalent to allocating the LADN for the S-NSSAI that satisfies the NS-AoS.

[0224] Unlike the prior art, when AMF sets Extended LADN information, it must consider partially allowed NSSAI, S-NSSAI time validity information, and S-NSSAI location validity information due to the definition and procedure of newly defined S-NSSAI-related information (e.g., partially allowed NSSAI, S-NSSAI time validity information, S-NSSAI location validity information). In addition, when AMF notifies SMF of information related to whether a UE exists within the LADN service area, it is necessary to consider the characteristics of S-NSSAI (e.g., partially allowed NSSAI, S-NSSAI time validity information, S-NSSAI location validity information).

[0225] However, prior art does not consider the characteristics of S-NSSAI (e.g., partially allowed NSSAI, S-NSSAI time validity information, S-NSSAI location validity information) at all. Therefore, an additional handling method related to Extended LADN information is required.

[0226] In various examples of the disclosure of this specification, additional handling methods related to Extended LADN information are specifically described.

[0227] A terminal can inform the network whether data services are available in a specific area.

[0228] For example, when a terminal informs the network of the availability of data services in a specific area (e.g., a LADN area or service area), the terminal may additionally consider the availability of network slices connected to the data services used in the specific area. Accordingly, the terminal can inform the network of the availability of data services in the specific area.

[0229] For example, when a network slice connected to a data service used in a specific area is available, the terminal can notify the network whether the data service is available in the specific area.

[0230] For example, a terminal can inform the network whether data services are available in a specific area when the network slice connected to the data services used in that area is valid.

[0231] A first network entity (e.g., AMF) may inform a second network entity (e.g., SMF) of the availability of data services in a specific area for a terminal connected to the first network entity. For example, the first network entity (e.g., AMF) may additionally consider the availability of a network slice connected to the data service used in the specific area and inform the second network entity of the availability of data services for the terminal in the specific area.

[0232] A first network entity (e.g., AMF) may inform a second network entity (e.g., SMF) of the availability of data services in a specific area of ​​a terminal connected to it. For example, when a network slice connected to a data service used by a terminal in a specific area is available, the first network entity (e.g., AMF) may inform the second network entity of the availability of data services in the specific area of ​​the terminal connected to it.

[0233] A first network entity (e.g., AMF) can determine whether a network slice connected to a data service used by a terminal in a specific area is available. If a partially allowed NSSAI can be configured in the Extended LADN configuration. In this case, if an S-NSSAI that the terminal is trying to transmit exists in the configured NSSAI but does not belong to the partially allowed NSSAI, the terminal determines that the S-NSSAI is outside the NS-AoS, and the terminal can release the PDU session for the LADN. The first network entity (e.g., AMF) can inform a second network entity that a data service is available in a specific area for the terminal connected to the first network entity.

[0234] A partially allowed network slice (NSSAI) may be a network slice that falls within a registration area (an area to which a terminal can connect). For example, a partially allowed network slice may be a network slice that falls within a specific area (e.g., a LADN area or an allowed area) to which a terminal can transmit.

[0235] A first network entity (e.g., AMF) can determine whether a network slice connected to a data service used in a specific area of ​​a terminal is available as follows. For example, if a terminal can use the network slice only during a specific time period, the first network entity (e.g., AMF) can inform a second network entity that the terminal connected to the first network entity can use the data service in the specific area only during the time period in which the network slice is available.

[0236] For example, a first network entity (e.g., AMF) may determine whether a corresponding network slice is available to a terminal during a specific time interval as follows. For example, based on the S-NSSAI time availability information notified to the terminal, the first network entity (e.g., AMF) may determine that a corresponding network slice is available only during the time interval in which S-NSSAI is available.

[0237] For example, S-NSSAI time validity information may include time information indicating the start and end of valid time information, valid day of the week information, the number of repetitions of the valid time information, and / or whether it is repeated.

[0238] A first network entity (e.g., AMF) can inform a second network entity (e.g., SMF) whether a terminal connected to it can use data services in a specific area. For example, when a network slice connected to a data service used by a terminal in a specific area is valid, the first network entity (e.g., AMF) can inform a second network entity (e.g., SMF) whether the terminal can use data services in the specific area.

[0239] A first network entity (e.g., AMF) can determine the validity of a network slice connected to a data service used by a terminal in a specific area. For example, the first network entity (e.g., AMF) may determine that the terminal can use the network slice only in a specific cell or a specific cell group within a specific area (e.g., LADN service area). In this case, only when the first network entity (e.g., AMF) determines that the network slice is only available in the specific cell or the specific cell group, the first network entity (e.g., AMF) can notify a second network entity that the terminal connected to the first network entity can use the data service in the specific area.

[0240] A first network entity (e.g., AMF) can inform the terminal of an available cell ID or cell group ID. In this case, the terminal can check the cell ID of the base station to which it has connected to determine whether the cell ID or cell group ID transmitted by the first network entity (e.g., AMF) relates to a cell to which the terminal can connect. For example, when a lower layer (e.g., RRC layer) of the terminal transmits the cell ID or cell group ID transmitted by the base station to the terminal, the terminal can determine the validity of the received information. For example, information that determines that a network slice is available only in a specific cell or a specific cell group is received from a lower layer of the terminal, such as the cell ID to which the terminal has connected. If the received cell ID exists as a cell identity available in a specific cell or a specific cell group, the terminal determines that the network slice is valid for the cell or cell group.

[0241] Below, examples to which the disclosure of this specification applies are described.

[0242] For example, based on S-NSSAI handling, Extended LADN information can be set.

[0243] To support Generic group Management, Exposure and Communication enhancements (GMEC) functionality, extended LADN information may include a LADN DNN and an associated S-NSSAI mapped to the LADN service area.

[0244] Connected S-NSSAI may be a new parameter of GMEC function.

[0245] To handle S-NSSAI, newly introduced partially allowed NSSAI, S-NSSAI time validity information, and S-NSSAI location validity information may be introduced.

[0246] Since the GMEC feature does not exclude the above S-NSSAI processing, when determining whether a terminal is located inside or outside the LADN service area, the corresponding S-NSSAI conditions must satisfy the requirements for the relevant S-NSSAI mapped to the LADN service area.

[0247] 1. AMF may set the associated S-NSSAI mapped to the LADN service area within the extended LADN information. In this case, AMF may set the S-NSSAI within the allowed NSSAI, the partially allowed NSSAI (if any), the S-NSSAI location validity information (if any), and the S-NSSAI time validity information (if any).

[0248] 2. The AMF can determine whether the UE is inside or outside the LADN service area. In this case, the AMF can check whether the S-NSSAI is in an allowed NSSAI or a partially allowed NSSAI, and whether the S-NSSAI is valid or usable based on the S-NSSAI location validity information and the S-NSSAI time validity information. Based on this, the AMF can determine whether the UE is inside or outside the LADN service area.

[0249] On the other hand, in the prior art, it was not defined at all how to handle S-NSSAI when extended LADN information is set.

[0250] If initial registration is accepted by the network, the following examples of applications to which the disclosure of this specification applies may apply:

[0251] A UE may set the LADN-DS bit in the 5GMM Capabilities IE of the REGISTRATION REQUEST message to "LADN per DNN and S-NSSAI is supported", and extended LADN information may be available to the UE. For example, LADN per DNN and S-NSSAI may mean LADN based on a combination of DNN and S-NSSAI. In this case, the AMF may include the extended LADN information in the Extended LADN Information IE of the Registration Acceptance Type 6 IE Container IE of the REGISTRATION ACCEPT message. For example, the extended LADN information may include the determined LADN DNN for the UE, the S-NSSAI associated with the determined LADN DNN for the UE included in the allowed NSSAI or partially allowed NSSAI (if any), and the LADN service areas available in the current registration area.

[0252] For Local Area Data Network (LADN), the disclosure of this specification may be applied as follows.

[0253] If conditions a through d below are satisfied, AMF may request SMF to release the PDU session:

[0254] a) The UE supports LADN per DNN and S-NSSAI;

[0255] b) The UE has a PDU session established based on a DNN and S-NSSAI that is not associated with the LAND service area indicated in the extended LADN information;

[0256] c) The LADN service area is set within the extended LADN information associated with the DNN and S-NSSAI of the PDU session; and

[0257] d) AMF determines that “UE exists within LADN service area” as it is outside the LADN service area set in the extended LADN information.

[0258] If the following conditions a through c are satisfied, the AMF may request the SMF to release the PDU session:

[0259] a) The UE supports LADN per DNN and S-NSSAI;

[0260] b) The UE has established a PDU session for LADN; and

[0261] c) AMF determines that the LADN service area associated with the DNN and S-NSSAI of the PDU session for LADN is removed from the extended LADN information.

[0262] Additionally, the AMF may include Extended LADN information in a UCU message or a registration acceptance message. According to one embodiment of the disclosure of the present specification, the S-NSSAI included in the Extended LADN information may be an S-NSSAI of an allowed NSSAI or a partially allowed NSSAI.

[0263] AMF may independently allocate a list of LADN service areas and TAIs associated with S-NSSAIs within a partially permitted NSSAI, if applicable.

[0264] A UE may receive Local Area Data Network (LADN) information consisting of LADN DNN and LADN service area information (a set of tracking areas belonging to the current registration area) during a registration procedure or a generic UE configuration update procedure.

[0265] The UE may support LADN per DNN and S-NSSAI. In this case, the UE may additionally receive extended LADN (Local Area Data Network) information, including LADN DNN, S-NSSAI, and LADN service area information (a set of tracking areas belonging to the current registration area), during the registration procedure or the general UE configuration update procedure.

[0266] Based on LADN service area information, the UE may consider itself to be located within the LADN service area. If the UE does not have LADN service area information for the LADN DNN, the UE may consider itself to be located outside the LADN service area.

[0267] The UE may support LADN per DNN and S-NSSAI and may receive extended LADN information. In this case, based on the LADN service area information and the availability or validity of the S-NSSAI, the UE may consider itself to be located within the LADN service area.

[0268] If the UE is in a LADN service area and the UE is in the alternate 5GMM-REGISTERED.NORMAL-SERVICE, the UE may initiate the following actions:

[0269] - To establish a PDU session for LADN, the UE may perform a UE-requested PDU session establishment procedure via the LADN DNN;

[0270] - If extended LADN information is available in the UE, the UE may perform a UE-requested PDU session setup procedure using the LADN DNN and the S-NSSAI associated with the LADN to establish a PDU session for the LADN;

[0271] - To modify a PDU session for LADN, the UE may perform the UE Request PDU Session Modification procedure;

[0272] - To re-establish user plane resources for a PDU session for LADN, the UE may perform a service request procedure; or

[0273] - To transmit CIoT user data over the control plane of a PDU session for LADN, the UE may perform a service request procedure or a UE-initiated NAS transfer procedure.

[0274] NOTE 1: If the UE receives one or more of the LADN Information IE or the Extended LADN Information IE and the Service Area List IE, the UE may evaluate the Service Area List IE first.

[0275] When the UE is outside the LADN service area, the UE is allowed to perform the following actions:

[0276] - To release a PDU session for LADN, the UE may initiate a UE-Request PDU Session Release procedure; or

[0277] - To indicate a change in the 3GPP PS data off UE state, the UE may initiate a UE-Request PDU Session Modification procedure.

[0278] AMF may determine that a UE is outside the LADN service area in the following cases. For example, AMF may determine that a UE is within the LADN service area and that it is outside the LADN service area in the following cases:

[0279] - When the DNN used for LADN is included in the LADN information and the UE is outside the LADN service area indicated in the LADN information;

[0280] - When the DNN and S-NSSAI used for LADN are included in the extended LADN information and the UE is located outside the LADN service area indicated in the extended LADN information;

[0281] - If the DNN used for LADN is included in the extended LADN information and there is no S-NSSAI provided by the UE to establish a PDU session for LADN;

[0282] - If the DNN used for the LADN is included in the extended LADN information and the S-NSSAI provided by the UE to establish a PDU session for the LADN is not associated with that LADN;

[0283] - If the DNN and S-NSSAI used for LADN are included in the extended LADN information and the AMF determines that the S-NSSAI provided by the UE to establish a PDU session for LADN is not within the NS-AoS; or

[0284] - When the DNN and S-NSSAI used for LADN are included in the extended LADN information and the S-NSSAI provided by the UE to establish a PDU session for LADN cannot be used.

[0285] If the UE is outside the LADN service area, the following actions may be taken:

[0286] a) SMF can perform the following actions:

[0287] 1) SMF may release the PDU session for LADN; or

[0288] 2) SMF can release user plane resources for PDU sessions for LADN and maintain PDU sessions for LADN. Depending on the operator's policy, whether user plane resources are released may vary.

[0289] b) SMF shall not transmit CIoT user data to the UE over the control plane for PDU sessions for LADN.

[0290] For a2) and b):

[0291] - When the UE returns within the LADN service area and downlink user data is pending in the network, the network re-establishes user plane resources for the PDU session for LADN;

[0292] - When the UE returns to the LADN service area and the network has pending downlink CIoT user data, the SMF can transmit the CIoT user data to the UE via control plane transmission; and

[0293] - If the UE does not return to the LADN service area after a certain period of time according to the carrier's policy, the SMF may release the PDU session for the LADN.

[0294] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals / messages / fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0295] FIG. 9 illustrates a first example of a procedure according to one embodiment of the disclosure of the present specification.

[0296] The procedure according to the example of Fig. 9 may be a procedure based on the registration procedure of Figs. 5 and 6. Descriptions of operations that overlap with the examples of Figs. 5 and 6 are omitted.

[0297] The UDM can manage UE subscriber information. For example, UE subscriber information may include information related to the LADN service area. This information may include the DNN and S-NSSAI.

[0298] 1. The UE can send a registration request message.

[0299] For example, a registration request message may include capability information. The registration request message may include the Requested NSSAI, LADN DNN, and 5GMM capabilities. For example, the registration request message may include one or more of the capabilities listed below:

[0300] - LADN-DS (LADN per DNN and S-NSSAI support): LADN-DS can include capability information on whether LADN per DNN and S-NSSAI is supported.

[0301] - PNS: PNS may contain capability information about whether it supports partial network slicing.

[0302] - SLVI: SLVI may include capability information on whether it supports S-NSSAI location validation.

[0303] - TempNS: TempNS may contain capability information on whether it supports S-NSSAI time validity.

[0304] 2. AMF can obtain UE subscriber information from UDM.

[0305] For example, upon receiving a registration request message, the AMF may perform the Uudm_SDM get service operation. For example, the AMF may send a message requesting subscriber information to the UDM. The UDM may send a message containing information related to the LADN service area to the AMF.

[0306] 3. AMF may send a registration acceptance message to the UE.

[0307] For example, a registration acceptance message may include LADN information. The LADN information may be extended LADN information.

[0308] For example, LADN information may include DNN and LADN service areas.

[0309] AMF can set LADN information (e.g., extended LADN information) based on the values ​​contained in the partially allowed NSSAI. For example, the extended LADN information can include the partially allowed NSSAI.

[0310] Even within a single tracking area, S-NSSAIs that allow LADN services and S-NSSAIs that do not allow LADN services may be included. Furthermore, a partially allowed S-NSSAI may include tracking areas that allow and areas that do not allow LADN services.

[0311] For example, AMF can set extended LADN information based on the tracking area allowed in S-NSSAI.

[0312] The area of ​​an S-NSSAI may not exactly match the deployed Tracking area. In this case, the AMF can configure LADN information so that LADN services can be effectively provided in a specific cell or cell group. For example, the AMF can configure LADN information that includes per S-NSSAI location validity information. The AMF can configure per S-NSSAI location validity information with the NS-AoS information included in each S-NSSAI. The AMF can inform the UE of the per S-NSSAI location validity information as NS-AoS information for each S-NSSAI.

[0313] AMF can send S-NSSAI location validity information to UE.

[0314] The purpose of the S-NSSAI Location Validity Information Information Element (IE) is to provide S-NSSAI location validity information to the UE.

[0315] S-NSSAI location validation information may include S-NSSAI, NS-AoS, and NR Cell ID.

[0316] For example, the S-NSSAI value can be coded into the length and value portions of the S-NSSAI information element.

[0317] For example, the NS-AoS value may include the number of NR cell ID fields and at least two NR CGIs. The NR CGI number may indicate the number of NR CGIs. An NR CGI can globally identify an NR cell. An NR CGI may include an NR cell ID and the PLMN ID of the corresponding cell.

[0318] S-NSSAI location validity information includes NS-AoS information. NS-AoS information indicates the cell ID applicable to the S-NSSAI. The AMF can inform the UE of the cell ID applicable to the S-NSSAI. Even if the cell ID is included in the tracking area, if it does not belong to the cell ID of the base station that the UE can actually access, the UE cannot transmit the S-NSSAI.

[0319] 4. OAM can send information to AMF and / or SMF. For example, OAM can send RRM policies to AMF and / or SMF.

[0320] For example, cell ID information applicable to S-NSSAI can be determined as an RRM policy in OAM and transmitted to the terminal.

[0321] 5. AMF can transmit information to gNB. gNB can transmit information to AMF.

[0322] 6a. 5G-AN can recognize S-NSSAI supported by AMF by PLMN ID.

[0323] 6b. AMF can recognize S-NSSAI supported by 5G-AN on a per TA basis.

[0324] A UE and an AMF according to one embodiment of the disclosure of this specification may perform a registration procedure based on the examples of FIGS. 5 and 6.

[0325] In step 1 of FIGS. 5 and 6, the registration request message transmitted by the UE may include an indicator of the Requested NSSAI, UE MM core network capabilities, LADN DNN(s), or requested LADN information. The same description may also apply to step 1 of FIG. 9.

[0326] In step 14 of FIGS. 5 and 6, the AMF may apply LADN per DNN and S-NSSAI. For example, the AMF may receive information from the UE in step 1 that the UE supports LADN per DNN and S-NSSAI. If the AMF has a LADN service area and the UE indicates that it supports LADN per DNN and S-NSSAI, the AMF may apply LADN per DNN and S-NSSAI. The same description may apply to step 2 of FIG. 9.

[0327] In step 16 of FIGS. 5 and 6, the PCF may provide the AMF with updated mobility restrictions. For example, if the AMF notifies the PCF of mobility restrictions (e.g., UE location) for adjustment, or if the PCF updates mobility restrictions on its own due to certain conditions (e.g., application in use, time, and date), the PCF may provide the updated mobility restrictions to the AMF. If the subscriber information includes tracing requirements, the AMF may provide the tracing requirements to the PCF.

[0328] If the AMF supports DNN replacement, the AMF may provide the PCF with allowed NSSAIs and partially allowed NSSAIs. If possible, the AMF provides the PCF with allowed NSSAI mappings and partially allowed NSSAI mappings.

[0329] In step 21 of FIGS. 5 and 6, the registration acceptance message may include at least one of mobility restrictions, a TAI list for S-NSSAIs within partially allowed NSSAIs, a TAI list for S-NSSAIs within partially rejected NSSAIs within RA, and LDAN information. The same description may also apply to step 3 of FIG. 9.

[0330] In step 21 of FIG. 5 and FIG. 6, the AMF may send a Registration Accept message. For example, if the UE indicated that it supports partial network slice support in the registration area of ​​the UE MM core network function of the Registration Request message, the AMF may include in the Registration Accept message a list of associated TAIs for the partially allowed NSSAI and the S-NSSAI of the partially allowed NSSAI. Alternatively, if the UE indicated that it supports partial network slice support in the registration area of ​​the UE MM core network function of the Registration Request message, the AMF may include in the N2 message conveying the Registration Accept message a list of associated TAIs for the S-NSSAI of the partially allowed NSSAI.

[0331] In step 21 of FIGS. 5 and 6, the AMF may send a Registration Acceptance message. For example, if the UE indicated in the Registration Request that it supports partial network slice support in the Registration Area of ​​the UE MM Core Network Function, the AMF may include the S-NSSAI that was partially rejected in the Registration Acceptance message along with a corresponding TAI list for the S-NSSAI that was partially rejected in the RA. The same description may apply to step 3 of FIG. 9.

[0332] In step 21 of FIGS. 5 and 6, the AMF may send a Registration Accept message. For example, the AMF may include in the Registration Accept message LADN information for a list of available LADNs within the registration area determined by the AMF for the UE. If the UE indicates that it supports LADN per DNN and S-NSSAI in the UE MM core network function, the AMF may include LADN information per DNN and S-NSSAI in the Registration Accept message. The same description may apply to step 3 of FIG. 9.

[0333] In step 21 of FIGS. 5 and 6 , the AMF may send a registration acceptance message. For example, if the UE indicates that it supports S-NSSAI location availability information, the AMF may include S-NSSAI location availability information in the registration acceptance message. The same description may apply to step 3 of FIG. 9 .

[0334] Referring to FIG. 10, the second part of the procedure according to the example of the disclosure of the present specification is described.

[0335] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals / messages / fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0336] FIG. 10 illustrates a second example of a procedure according to one embodiment of the disclosure of the present specification.

[0337] The procedure according to the example of Fig. 10 may be based on the registration procedure of Figs. 5 and 6. Operations that overlap with the examples of Figs. 5 and 6 will not be described. Furthermore, operations that overlap with the example of Fig. 9 will also not be described.

[0338] UDM can manage UE subscriber information, as shown in the example of Fig. 9.

[0339] Additionally, subscriber information may include information regarding the extent of area covered by each S-NSSAI.

[0340] 1. The UE can send a registration request message.

[0341] For example, a registration request message may include capability information. The registration request message may include the Requested NSSAI, LADN DNN, and 5GMM capabilities. For example, the registration request message may include one or more of the capabilities listed below:

[0342] - LADN-DS: LADN-DS can include capability information on whether the DNN and S-NSSAI support LADN.

[0343] - PNS: PNS may contain capability information about whether it supports partial network slicing.

[0344] - SLVI: SLVI may include capability information on whether it supports S-NSSAI location validation.

[0345] - TempNS: TempNS may contain capability information on whether it supports S-NSSAI time validity.

[0346] - SLVI2: SLVI2 may include capability information on whether it supports GNSS-based S-NSSAI position validation.

[0347] For example, the terminal may transmit a registration request message to the NW that includes whether GNSS-based S-NSSAI location validity support is provided.

[0348] 2. AMF can obtain UE subscriber information from UDM.

[0349] For example, upon receiving a registration request message, the AMF may perform the Uudm_SDM get service operation. For example, the AMF may send a message requesting subscriber information to the UDM. The UDM may send a message containing information related to the LADN service area to the AMF.

[0350] For example, AMF may receive geo location type information from UDM.

[0351] 3. AMF can obtain location information from LMF / LCS.

[0352] For reference, LMF can be Location Management Function. LCS can be Location Services.

[0353] For example, AMF can send a Namf_Location_ProvidePositioningInfo request message to LMF / LCS. LMF / LCS can send a Namf_Location_ProvidePositioningInfo response message to AMF. For example, the response message can include geographic location information (e.g., GeoLocation).

[0354] For example, the geographic location information may include location information related to S-NSSAI based on the Global Navigation Satellite System (GNSS).

[0355] 4. AMF may send a registration acceptance message to the UE.

[0356] For example, a registration acceptance message may include LADN information. The LADN information may be extended LADN information.

[0357] For example, LADN information may include DNN and LADN service areas.

[0358] AMF can set LADN information (e.g., extended LADN information) based on the values ​​contained in the partially allowed NSSAI. For example, the extended LADN information can include the partially allowed NSSAI.

[0359] Even within a single tracking area, S-NSSAIs that allow LADN services and S-NSSAIs that do not allow LADN services may be included. Furthermore, a partially allowed S-NSSAI may include tracking areas that allow and areas that do not allow LADN services.

[0360] For example, AMF can set extended LADN information based on the tracking area allowed in S-NSSAI.

[0361] The area of ​​an S-NSSAI may not exactly match the deployed Tracking area. In this case, the AMF can configure LADN information so that LADN services can be effectively provided in a specific cell or cell group. For example, the AMF can configure LADN information that includes per S-NSSAI location validity information. The AMF can configure per S-NSSAI location validity information with the NS-AoS information included in each S-NSSAI. The AMF can inform the UE of the per S-NSSAI location validity information as NS-AoS information for each S-NSSAI.

[0362] The S-NSSAI may not exactly match the deployed tracking area. In such cases, the AMF can configure per-S-NSSAI location validity information to ensure that LADN services can be effectively provided in a specific cell or group of cells. For example, the AMF can configure per-S-NSSAI location validity information that includes location information based on the GNSS information available to the actual S-NSSAI.

[0363] AMF can send S-NSSAI location validity information to UE.

[0364] The AMF can provide GNSS-based S-NSSAI location information to the UE. GNSS-based S-NSSAI location information can include geographic location information specific to each S-NSSAI. In this case, the AMF can also provide the UE with the distance or angle at which the S-NSSAI is available.

[0365] For example, the location coordinates of the registration request message containing the terminal's S-NSSAI may be (44, 33, 66) (e.g., latitude, longitude, height). In this case, the location at which the S-NSSAI is available may be indicated at a distance from the corresponding location. The locations at which the S-NSSAI is available may be stored in the subscriber information. For example, information related to the area covered by each S-NSSAI may be stored in the subscriber information.

[0366] The AMF manages the area of ​​a terminal's S-NSSAI and can determine its validity. Additionally, the SMF can also manage the validity of this area. The SMF can provide terminals with area information related to LADN services.

[0367] The description of step 3 of FIG. 9 can also be applied to step 4 of FIG. 10.

[0368] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals / messages / fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0369] FIG. 11 illustrates an example of operations according to one embodiment of the disclosure of the present specification.

[0370] For reference, the procedure illustrated in FIG. 11 is merely an example, and the scope of the disclosure of this specification is not limited by the example in FIG. 11.

[0371] For example, with respect to the example of FIG. 11, the operations described in the examples of FIGS. 1 to 10 may also be applied. For example, even if operations, contents, etc. are not directly described in the example of FIG. 11, operations, contents, etc. described in various examples of the disclosure of this specification may be applied.

[0372] In step (S1101), the UE may transmit a registration request message to the AMF.

[0373] For example, a registration request message may include capability information. For example, the capability information may include information that LADN is supported for each S-NSSAI.

[0374] In step (S1102), AMF can receive subscriber information from UDM.

[0375] For example, subscriber information may include Local Area Data Network (LADN) service area information related to S-NSSAI.

[0376] For example, AMF can determine location information related to the S-NSSAI based on LADN service area information.

[0377] In step (S1103), AMF may send a registration acceptance message to the UE.

[0378] For example, the registration acceptance message may include LADN information and location information related to the S-NSSAI. For example, the LADN information may include LADN service area information.

[0379] For example, location information related to S-NSSAI may be location validity information including Network Slice-Area of ​​Service (NS-AOS) information in which service area information for supporting LADN service is set on a cell-by-cell or cell-group basis.

[0380] Before performing step (S1103), the AMF may receive geographic location information related to the S-NSSAI from the Location Management Function (LMF). For example, the AMF may determine location information related to the S-NSSAI based on the geographic location information. For example, the location information related to the S-NSSAI may be GNSS-based S-NSSAI location information that includes possible geographic location information for each S-NSSAI.

[0381] For example, the AMF can determine UE presence information within the LADN service area based on the location information related to the S-NSSAI. The AMF can transmit the UE presence information within the LADN service area to the SMF.

[0382] The UE may determine whether a LADN service based on S-NSSAI is available based on location information related to S-NSSAI and the LADN service area information.

[0383] According to one embodiment of the disclosure of the present specification, a first network entity (e.g., AMF) may inform a second network entity (e.g., SMF) whether a terminal connected to the first network entity is available for data services in a specific area. For example, the first network entity (e.g., AMF) may additionally consider the availability or validity of a network slice connected to a data service used in the specific area.

[0384] According to one embodiment of the disclosure of the present specification, a first network entity (e.g., AMF) can determine whether a network slice connected to a data service used in a specific area of ​​a terminal is available. For example, if a network slice connected to a data service used in a specific area of ​​a terminal is a partially allowed network slice (Partially allowed NSSAI), the first network entity (e.g., AMF) can notify a second network entity that the terminal connected to it can use the data service in the specific area.

[0385] According to one embodiment of the disclosure of the present specification, a first network entity (e.g., AMF) can determine whether a network slice connected to a data service used by a terminal in a specific area is available. For example, if the terminal can use the network slice only during a specific time period, the first network entity (e.g., AMF) can notify a second network entity that the terminal connected to the first network entity can use the data service in the specific area only during the time period in which the network slice is available.

[0386] According to one embodiment of the disclosure of the present specification, a first network entity (e.g., AMF) may determine the validity of a network slice connected to a data service used by a terminal in a specific area. For example, the terminal may be available only in a specific cell or a specific cell group within a specific area (e.g., LADN service area). In this case, only when the first network entity (e.g., AMF) determines that the network slice is available only in the specific cell or the specific cell group, the first network entity (e.g., AMF) may notify a second network entity that the terminal connected to it can use the data service in the specific area.

[0387] This specification may have various effects.

[0388] For example, LADN services can be effectively provided. For example, LADN service areas associated with S-NSSAIs within partially allowed NSSAIs can be effectively handled. For example, LADN information can be configured to more accurately consider location information available in S-NSSAIs.

[0389] The effects that can be achieved through the specific examples of this specification are not limited to the effects listed above. For example, a person with ordinary skill in the relevant technical field may understand or derive various technical effects from this specification. Accordingly, the specific effects of this specification are not limited to those explicitly described herein, but may include various effects that can be understood or derived from the technical features of this specification.

[0390] For reference, the operation of the terminal (e.g., UE) described in this specification may be implemented by the devices of FIGS. 1 to 3 described above. For example, the terminal may be the first device (100) or the second device (200) of FIG. 2. For example, the operation of the terminal described in this specification may be processed by one or more processors (102 or 202). The operation of the terminal described in this specification may be stored in one or more memories (104 or 204) in the form of instructions / programs (e.g., instructions, executable codes) 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 (105 or 206), and execute the instructions / programs stored in one or more memories (104 or 204) to perform the operation of the terminal (e.g., UE) described in the disclosure of this specification.

[0391] Additionally, the commands for performing the operations of the terminal described in the disclosure of this specification may be stored in a non-volatile computer-readable storage medium. The storage medium may be included in one or more memories (104 or 204). In addition, the commands recorded in the storage medium may be executed by one or more processors (102 or 202) to perform the operations of the terminal described in the disclosure of this specification.

[0392] For reference, the operation of a network node (e.g., AMF, SMF, PCF, UDM, LMF, etc.) or a base station (e.g., NG-RAN, gNB, RAN, (R)AN, etc.) described in this specification may be implemented by the devices of FIGS. 1 to 3 described below. For example, the network node or the base station may be the first device (100) or the second device (200) of FIG. 2. For example, the operation of the network node or the base station described in this specification may be processed by one or more processors (102 or 202). The operation of the terminal described in this specification may be stored in one or more memories (104 or 204) in the form of instructions / programs (e.g., instructions, executable codes) executable by one or more processors (102 or 202). One or more processors (102 or 202) may control one or more memories (104 or 204) and one or more transceivers (106 or 206), and execute instructions / programs stored in one or more memories (104 or 204) to perform operations of a network node or base station as described in the disclosure of this specification.

[0393] Additionally, the instructions for performing the operations of the network node or base station described in the disclosure of this specification may be stored in a non-volatile (or non-transitory) computer-readable storage medium having the instructions recorded thereon. The storage medium may be included in one or more memories (104 or 204). In addition, the instructions recorded in 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 the disclosure of this specification.

[0394] Although the preferred embodiments have been described above by way of example, the disclosure of this specification is not limited to such specific embodiments, and may be modified, changed, or improved in various forms within the scope described in the spirit and claims of this specification.

[0395] In the exemplary system described above, the methods are described based on a flowchart as a series of steps or blocks. However, the order of the steps described is not limited, and some steps may occur in a different order or simultaneously with other steps described above. Furthermore, those skilled in the art will understand that the steps depicted in the flowchart are not exclusive, and other steps may be included, or one or more steps in the flowchart may be deleted without affecting the scope of the invention.

[0396] The claims set forth in this specification may be combined in various ways. For example, the technical features of the method claims of this specification may be combined to implement a device, and the technical features of the device claims of this specification may be combined to implement a method. Furthermore, the technical features of the method claims and the technical features of the device claims of this specification may be combined to implement a device, and the technical features of the method claims and the technical features of the device claims of this specification may be combined to implement a method. Other implementations are within the scope of the claims.

Claims

1. A step of receiving a registration request message including Single Network Slice Selection Assistance Information (S-NSSAI) from User Equipment (UE); A step of obtaining subscriber information of the above UE from Unified Data Management (UDM), The above subscriber information includes Local Area Data Network (LADN) service area information related to the S-NSSAI; and comprising the step of sending a registration acceptance message; The above registration acceptance message includes LADN information and location information related to the S-NSSAI, The above LADN information includes the above LADN service area information, A method characterized in that the location information related to the above S-NSSAI is location validity information including Network Slice-Area of ​​Service (NS-AOS) information in which service area information for supporting LADN service is set by cell unit or cell group unit.

2. In paragraph 1, A method further comprising a step of determining location information related to the S-NSSAI based on the LADN service area information.

3. In paragraph 1 or 2, A step of receiving geographic location information related to the S-NSSAI from a Location Management Function (LMF); A method characterized in that the location information related to the S-NSSAI is S-NSSAI location information based on GNSS including possible geographical location information for each S-NSSAI.

4. In paragraph 3, A method further comprising a step of determining location information related to the S-NSSAI based on the geographic location information.

5. In any one of paragraphs 1 to 4, The above registration request message includes capability information, A method characterized in that the above capability information includes information that supports LADN by S-NSSAI.

6. In any one of paragraphs 1 to 5, A method further comprising the step of transmitting UE presence information within a LADN service area to a Session Management Function (SMF) based on location information related to the S-NSSAI.

7. One or more transmitters and receivers; one or more processors; and comprising one or more memories capable of storing instructions and being operable to the one or more processors; A device wherein the operation performed based on the above command being executed by the one or more processors is a method according to any one of claims 1 to 6.

8. A step of transmitting a registration request message including Single Network Slice Selection Assistance Information (S-NSSAI) to the AMF; and comprising the step of receiving a registration acceptance message from the AMF; The above registration acceptance message includes Local Area Data Network (LADN) information and location information related to the S-NSSAI, The above LADN information includes LADN service area information, A method characterized in that the location information related to the above S-NSSAI is location validity information including Network Slice-Area of ​​Service (NS-AOS) information in which service area information for supporting LADN service is set by cell unit or cell group unit.

9. In paragraph 8, A method characterized in that the location information related to the S-NSSAI is S-NSSAI location information based on GNSS including possible geographical location information for each S-NSSAI.

10. In paragraph 8 or 9, The above registration request message includes capability information, A method characterized in that the above capability information includes information that supports LADN by S-NSSAI.

11. In any one of paragraphs 8 to 10, A method further comprising a step of determining whether a LADN service based on the S-NSSAI is possible based on location information related to the S-NSSAI and the LADN service area information.

12. One or more transmitters and receivers; one or more processors; and comprising one or more memories capable of storing instructions and being operable to the one or more processors; The actions performed based on the above instructions being executed by the one or more processors are: A device according to any one of claims 8 to 11.

13. In an apparatus of a communication system, the apparatus: One or more transmitters and receivers; one or more processors; and comprising one or more memories capable of storing instructions and being operable to the one or more processors; A device wherein the operation performed based on the command being executed by the one or more processors is a method according to any one of claims 8 to 11.

14. A non-transitory computer readable medium (CRM) storing instructions, wherein an operation performed based on the instructions being executed by one or more processors is a method according to any one of claims 8 to 11.

Images