Method for non-3GPP device connected to terminal

Abstract

One disclosure of the present specification provides a method. The method comprises steps in which a UE: receives a non-3GPP (N3D) policy from a policy control function (PCF), the N3D policy including device identifier information; transmits, to a session management function (SMF), an establishment request message for a specific packet data unit (PDU) session; receives, from the SMF, an establishment approval message for the specific PDU session; determines a specific device identifier for a specific non-3GPP device on the basis of a connection of the specific non-3GPP device to the UE, and the device identifier information, the specific PDU session being a PDU session for the specific non-3GPP device; and, on the basis of the connection of the specific non-3GPP device to the UE, transmits, to the SMF, a first message including the specific device identifier.

Description

Method for a NON-3GPP device connected to a terminal

[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 in a timely manner, meeting both urgent market needs and the longer-term requirements outlined by the ITU-R (ITU radio communication sector) 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] The problem lies in the method for non-3GPP devices connected to the terminal.

[0006] The terminal receives a policy for a non-3GPP device and, based on this, informs the network of an identifier for a specific non-3GPP device.

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

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

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

[0010] Figure 4 is a structural diagram of a next-generation mobile communications network.

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

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

[0013] Figures 8 and 9 illustrate examples of a PDU session establishment procedure to which the implementation of the present specification applies.

[0014] FIG. 10 illustrates an example of a device ID profile provisioning procedure according to the first disclosure of the present specification.

[0015] FIG. 11 illustrates an example of a UE / 5G-RG approval procedure according to the first disclosure of this specification.

[0016] Figure 12 illustrates an example of a procedure for providing a service to a non-3GPP device according to the first disclosure of this specification.

[0017] Figure 13 illustrates an example of a procedure for providing a service to a non-3GPP device according to the second disclosure of this specification.

[0018] Figures 14a and 14b illustrate examples of procedures according to the disclosure of the present specification.

[0019] Figure 15 illustrates the UE's procedure for disclosure of this specification.

[0020] Figure 16 illustrates the SMF procedure for the disclosure of this specification.

[0021] 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 multicarrier frequency division multiple access (MC-FDMA) systems. CDMA can be implemented via wireless technologies such as universal terrestrial radio access (UTRA) or CDMA2000. TDMA can be implemented via 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 E-UTRA (evolved UTRA). UTRA is part of UMTS (universal mobile telecommunications system). 3GPP (3rd generation partnership project) LTE (long-term evolution) is part of E-UMTS (evolved UMTS) that uses 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).

[0022] 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. However, aspects of this specification that are not limited to a 3GPP-based wireless communication system can be applied to other mobile communication systems.

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

[0024] 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."

[0025] 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."

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

[0027] 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”.

[0028] 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."

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

[0030] 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).

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

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

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

[0034] 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).

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

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

[0037] Wireless devices (100a to 100f) refer to 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. Wireless devices (100a to 100f) may include, but are not limited to, robots (100a), vehicles (100b-1 and 100b-2), extended reality (XR) devices (100c), portable devices (100d), home appliances (100e), IoT devices (100f), and artificial intelligence (AI) devices / servers (400). For example, vehicles may include vehicles having wireless communication capabilities, autonomous vehicles, and vehicles capable of performing vehicle-to-vehicle communication. Vehicles may include unmanned aerial vehicles (UAVs) (e.g., drones). XR devices may include AR / VR / mixed reality (MR) devices, and may be implemented in the form of head-mounted devices (HMDs) and heads-up displays (HUDs) 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.

[0038] 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 functions, a connected car, a UAV, an AI module, a robot, an AR device, a VR device, an MR device, a holographic 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.

[0039] For example, a UAV may be an aircraft that is unmanned and navigated by radio control signals.

[0040] For example, a VR device may include a device for implementing objects or backgrounds in a virtual environment. For example, an AR device may include a device that implements objects or backgrounds in a virtual world by connecting them to objects or backgrounds in the real world. For example, an MR device may include a device that implements objects or backgrounds in a virtual world by merging them with objects or backgrounds in the real world. For example, a holographic device may include a device that implements 360-degree stereoscopic images by recording and reproducing three-dimensional information using the light interference phenomenon that occurs when two laser lights, called holograms, meet.

[0041] For example, a public safety device may include an image relay device or imaging device that can be worn on the user's body.

[0042] For example, MTC devices and IoT devices may be devices that do not require direct human intervention or manipulation. Examples include smart meters, vending machines, thermometers, smart light bulbs, door locks, or various sensors.

[0043] For example, a medical device may be a device used for the purpose of diagnosing, treating, alleviating, curing, or preventing a disease. For example, a medical device may be a device used for diagnosing, treating, alleviating, or correcting an injury or damage. For example, a medical device may be a device used for the purpose of examining, replacing, or modifying a structure or function. For example, a medical device may be a device used for the purpose of regulating pregnancy. For example, a medical device may include a therapeutic device, a driving device, an (in vitro) diagnostic device, a hearing aid, or a surgical device.

[0044] For example, a security device may be a device installed to prevent potential hazards and maintain safety. For example, a security device may be a camera, closed-circuit television (CCTV), recorder, or black box.

[0045] For example, a fintech device may be a device capable of providing financial services, such as mobile payments. For example, a fintech device may include a payment device or a point-of-sale system.

[0046] For example, a weather / environment device may include a device that monitors or predicts the weather / environment.

[0047] 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).

[0048] 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, device-to-device (D2D) communication), and base station-to-base station communication (150c) (e.g., relay, integrated access and backhaul (IAB)). 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, at least some of the 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 based on various proposals of the present specification.

[0049] AI is the study of artificial intelligence or the methodologies for creating it, while machine learning (ML) defines various problems in the field of AI and studies the methodologies for solving them. Machine learning is also defined as an algorithm that improves performance on a task through consistent experience.

[0050] A robot can be defined as a machine that automatically processes or operates a given task based on its own capabilities. Specifically, a robot capable of perceiving its environment, making decisions, and performing actions on its own can be called an intelligent robot. Robots can be categorized into industrial, medical, household, and military applications based on their intended use or field. Robots are equipped with a drive unit, including an actuator or motor, enabling them to perform various physical actions, such as moving robot joints. Furthermore, mobile robots include wheels, brakes, and propellers in their drive unit, enabling them to drive on the ground or fly in the air.

[0051] Autonomous driving refers to the technology of driving on one's own, while autonomous vehicles refer to vehicles that drive without, or with minimal, user intervention. For example, autonomous driving can include technologies such as lane keeping, automatic speed control like adaptive cruise control, autonomous driving along a set route, and autonomous driving based on a set destination. Vehicles encompass all types of vehicles: those with internal combustion engines, hybrid vehicles with both internal combustion engines and electric motors, and electric vehicles with only electric motors. These vehicles can include not only cars but also trains and motorcycles. Autonomous vehicles can be viewed as robots with autonomous driving capabilities.

[0052] Extended reality is a general term for VR, AR, and MR. VR technology provides real-world objects and backgrounds as CG images only, AR technology provides virtual CG images over images of real objects, and MR technology is a CG technology that mixes and combines virtual objects with the real world. MR technology is similar to AR in that it displays real and virtual objects together. However, there is a difference: while AR uses virtual objects to complement real objects, MR uses virtual and real objects equally.

[0053] NR supports multiple numerologies, or subcarrier spacing (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.

[0054] 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 NR systems, FR1 can mean the "sub-6GHz range," and FR2 can mean the "above 6GHz range," which can be referred to as millimeter wave (mmW).

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

[0056] 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 may be used for various purposes, such as for communications for vehicles (e.g., autonomous driving).

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

[0058] 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 PAN (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.

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

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

[0061] 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).

[0062] 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).

[0063] 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).

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

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

[0066] 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).

[0067] 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).

[0068] 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).

[0069] 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 instruction codes, commands 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.

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

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

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

[0073] 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. The one or more memories (104, 204) may be located internally and / or externally to the one or more processors (102, 202). Additionally, the one or more memories (104, 204) may be coupled to the one or more processors (102, 202) via various technologies, such as wired or wireless connections.

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

[0075] 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 specification, one or more antennas (108, 208) may be multiple physical antennas or multiple logical antennas (e.g., antenna ports).

[0076] 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).

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

[0078] In the implementation of the present specification, a UE can operate as a transmitter in the uplink (UL) and as a receiver in the downlink (DL). In the implementation of the present 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 the present specification or to control a transceiver (106) to perform UE operations according to the implementation of the present 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 the present specification or to control a transceiver (206) to perform base station operations according to the implementation of the present specification.

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

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

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

[0082] 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).

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

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

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

[0086] 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).

[0087] 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).

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

[0089] 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).

[0090] Figure 4 is a structural diagram of a next-generation mobile communications network.

[0091] 5GC (5G Core) may include various components, and in FIG. 5, some of them include AMF (Access and Mobility Management Function) (410), SMF (Session Management Function) (420), PCF (Policy Control Function) (430), UPF (User Plane Function) (440), AF (Application Function) (450), UDM (Unified Data Management) (460), and N3IWF (Non-3GPP (3rd Generation Partnership Project) Inter Working Function) (490).

[0092] The UE (100) is connected to a data network via UPF (440) through a Next Generation Radio Access Network (NG-RAN) including a gNB (20).

[0093] The UE (100) can also receive data services via untrusted non-3GPP access, such as a Wireless Local Area Network (WLAN). To connect the non-3GPP access to the core network, an N3IWF (490) may be deployed.

[0094] The illustrated N3IWF (490) performs the function of managing interworking between non-3GPP access and 5G system. When UE (100) is connected to non-3GPP access (e.g., WiFi, referred to as IEEE 801.11), UE (100) can be connected to 5G system through N3IWF (490). N3IWF (490) performs control signaling with AMF (410) and is connected to UPF (440) through N3 interface for data transmission.

[0095] The illustrated AMF (410) can manage access and mobility in a 5G system. The AMF (410) can perform functions to manage Non-Access Stratum (NAS) security. The AMF (410) can perform functions to handle mobility in the idle state.

[0096] The illustrated UPF (440) is a type of gateway through which user data is transmitted and received. The UPF node (440) can perform all or part of the user plane functions of the S-GW (Serving Gateway) and P-GW (Packet Data Network Gateway) of 4th generation mobile communications.

[0097] The UPF (440) acts as a boundary point between the next generation radio access network (NG-RAN) and the core network, and is an element that maintains a data path between the gNB (20) and the SMF (420). In addition, when the UE (100) moves across the area served by the gNB (20), the UPF (440) acts as a mobility anchor point. The UPF (440) can perform a function of handling PDUs. For mobility within the NG-RAN (Next Generation-Radio Access Network defined after 3GPP Release-15), the UPF can route packets. Additionally, the UPF (440) may also function as an anchor point for mobility with other 3GPP networks (RANs defined before 3GPP Release-15, e.g., UTRAN, E-UTRAN (Evolved-UMTS (Universal Mobile Telecommunications System) Terrestrial Radio Access Network)) or GERAN (GSM (Global System for Mobile Communication) / EDGE (Enhanced Data rates for Global Evolution) Radio Access Network). The UPF (440) may correspond to a termination point of a data interface toward a data network.

[0098] The illustrated PCF (430) is a node that controls the business operator's policy.

[0099] The illustrated AF (450) is a server for providing various services to the UE (100).

[0100] The illustrated UDM (460) is a type of server that manages subscriber information, such as the HSS (Home Subscriber Server) of 4th generation mobile communications. The UDM (460) stores and manages the subscriber information in a Unified Data Repository (UDR).

[0101] The illustrated SMF (420) can perform the function of allocating an IP (Internet Protocol) address of the UE. In addition, the SMF (420) can control a PDU (protocol data unit) session.

[0102] For reference, the drawing symbols for AMF (410), SMF (420), PCF (430), UPF (440), AF (450), UDM (460), N3IWF (490), gNB (20), or UE (100) may be omitted below.

[0103] 5G mobile communications support multiple numerologies, or subcarrier spacing (SCS), to support diverse 5G services. For example, a 15 kHz SCS supports wide areas in traditional cellular bands. A 30 kHz / 60 kHz SCS supports dense urban environments, lower latency, and wider carrier bandwidth. An SCS of 60 kHz or higher supports bandwidths greater than 24.25 GHz to overcome phase noise.

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

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

[0106] - AUSF (Authentication Server Function)

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

[0108] - DN (Data Network), 예를 들어 운영자 서비스, 인터넷 접속 또는 타사 서비스

[0109] - USDF (Unstructured Data Storage Function)

[0110] - NEF (Network Exposure Function)

[0111] - I-NEF (Intermediate NEF)

[0112] - NRF (Network Repository Function)

[0113] - NSSF (Network Slice Selection Function)

[0114] - PCF (Policy Control Function)

[0115] - SMF (Session Management Function)

[0116] - UDM (Unified Data Management)

[0117] - UDR (Unified Data Repository)

[0118] - UPF (User Plane Function)

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

[0120] - AF (Application Function)

[0121] - UE (User Equipment)

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

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

[0124] - NWDAF (Network Data Analytics Function)

[0125] - CHF (CHarging Function)

[0126] Additionally, the following network features may be considered:

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

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

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

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

[0131] In Figure 5, for clarity of the point-to-point diagram, UDSF, NEF, and NRF are not illustrated. However, all network functions shown can interact with UDSF, UDR, NEF, and NRF as needed.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0153] <Registration Procedure>

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

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

[0156] 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:

[0157] - Initial registration for 5GS; or

[0158] - mobility registration update; or

[0159] - Periodic registration update; or

[0160] - Emergency registration

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

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

[0163] First, the procedure of Fig. 6 is described.

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

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

[0166] 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 the periodic registration update timer has expired), or an emergency registration (i.e., the UE is in restricted service state).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0185] (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.

[0186] (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.

[0187] (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.

[0188] (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).

[0189] (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.

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

[0191] (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.

[0192] (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.

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

[0194] Now, the procedure of Fig. 7 following the procedure of Fig. 6 is described.

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

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

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

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

[0199] (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.

[0200] (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.

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

[0202] (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.

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

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

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

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

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

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

[0209] (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.

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

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

[0212] <PDU 세션 수립 절차>

[0213] Describes the PDU session establishment procedure. See Section 4.3.2 of 3GPP TS 23.502 V16.3.0 (2019-12).

[0214] Figures 8 and 9 illustrate examples of a PDU session establishment procedure to which the implementation of the present specification applies.

[0215] Establishing a PDU session may involve:

[0216] - UE-initiated PDU session establishment procedure

[0217] - PDU session handover between 3GPP and non-3GPP initiated by UE

[0218] - PDU session handover from UE-initiated EPS to 5GS.

[0219] - Network-triggered PDU session establishment procedure

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

[0221] Figures 8 and 9 specify the procedure for establishing a PDU session associated with a single connection type at a given time.

[0222] In the procedures shown in Figures 8 and 9, it is assumed that the UE is already registered with the AMF, so unless the UE is emergency registered, the AMF has already retrieved the user subscription data from the UDM.

[0223] First, the procedure of Fig. 8 is explained.

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

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

[0226] If the PDU session establishment is a request to establish a new PDU session, the request type is "Initial Request." If the request refers to an existing PDU session switching between a 3GPP connection and a non-3GPP connection, or a PDU session handover from an existing packet data network (PDN) connection in the EPC, the request type is "Existing PDU Session." If the PDU session establishment is a request to establish a PDU session for emergency services, the request type is "Emergency Request." If the request refers to an existing PDU session for emergency services switching between a 3GPP connection and a non-3GPP connection, or a PDU session handover from an existing PDN connection for emergency services in the EPC, the request type is "Existing Emergency PDU Session."

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

[0228] (2) Step 2: AMF selects an SMF. If the request type indicates "Initial Request" or the request is due to a handover from an EPS or other non-3GPP connection provided by an AMF, AMF stores the connection type of the PDU session as well as the association of S-NSSAI(s), data network name (DNN), PDU session ID, and SMF ID.

[0229] If the request type is "Initial Request" and the message also contains a previous PDU Session ID representing an existing PDU Session, AMF selects an SMF and stores the association of the new PDU Session ID, S-NSAI(s), and the selected SMF ID.

[0230] If the request type indicates "Existing PDU Session," AMF selects an SMF based on the SMF-ID received from the UDM. AMF updates the stored connection type for the PDU session.

[0231] If the request type indicates "Existing PDU Session", which refers to an existing PDU session moving between a 3GPP connection and a non-3GPP connection, and if the serving PLMN S-NSSAI of the PDU session is in the allowed NSSAI of the target connection type, the PDU session establishment procedure may be performed in the following cases:

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

[0233] - If the SMF ID corresponding to the PDU session ID belongs to HPLMN;

[0234] Otherwise, AMF rejects the PDU session establishment request with an appropriate rejection cause.

[0235] AMF rejects requests from emergency-registered UEs whose request type does not indicate "Emergency Request" or "Existing Emergency PDU Session".

[0236] (3) Step 3: If the AMF is not associated with an SMF for the PDU session ID provided by the UE (e.g., when the request type indicates "Initial Request"), the AMF invokes the Create SM Context request procedure (e.g., Nsmf_PDUSession_CreateSMContext Request). If the AMF is already associated with an SMF for the PDU session ID provided by the UE (e.g., when the request type indicates "Existing PDU Session"), the AMF invokes the Update SM Context request procedure (e.g., Nsmf_PDUSession_UpdateSMContext Request).

[0237] The AMF transmits the S-NSSAI of the serving PLMN to the SMF from the allowed NSSAI. For a roaming scenario of local breakout (LBO), the AMF also transmits the corresponding S-NSSAI of the HPLMN to the SMF from the mapping of the allowed NSSAI.

[0238] The AMF ID is the UE's GUAMI, which uniquely identifies the AMF serving the UE. The AMF passes the PDU session ID along with the N1 SM container containing the PDU session establishment request message received from the UE. The GPSI (generic public subscription identifier) ​​is included if available to the AMF.

[0239] If a UE in limited service state is registered for emergency services without providing SUPI, the AMF provides PEI instead of SUPI. If a UE in limited service state is registered for emergency services while providing SUPI but is not authenticated, the AMF indicates that the SUPI is not authenticated. If the SMF does not receive a SUPI for the UE or if the AMF indicates that the SUPI is not authenticated, the UE is considered unauthenticated.

[0240] AMF can include a PCF ID in Nsmf_PDUSession_CreateSMContext. This PCFID identifies the home PCF (H-PCF) in non-roaming cases and the visited PCF (V-PCF) in LBO roaming cases.

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

[0242] (5) Step 5: SMF sends a create SM context response message (e.g., Nsmf_PDUSession_CreateSMContext Response) or an update SM context response message (e.g., Nsmf_PDUSession_UpdateSMContext Response) to AMF according to the request received in step 3.

[0243] If SMF receives the Nsmf_PDUSession_CreateSMContext Request in step 3 and can process the PDU session establishment request, SMF creates an SM context and responds to AMF by providing the SM context ID.

[0244] If the SMF decides not to accept the PDU session establishment, the SMF rejects the UE request by sending a NAS SM signal including the relevant SM rejection cause by responding to the AMF with an Nsmf_PDUSession_CreateSMContext Response. The SMF also indicates to the AMF that the PDU session ID is considered released and the SMF proceeds to step 20 below, aborting the PDU session establishment procedure.

[0245] (6) Step 6: Optional secondary authentication / authorization may be performed.

[0246] (7a) Step 7a: When dynamic policy and charging control (PCC) is used in a PDU session, the SMF can perform PCF selection.

[0247] (7b) Step 7b: SMF performs the SM policy association establishment procedure to establish a PCF and SM policy association, and obtains the basic PCC rules for the PDU session.

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

[0249] (9) Step 9: The SMF may provide information about the satisfied policy control request trigger conditions by performing the SM policy association modification procedure initiated by the SMF.

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

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

[0252] (11) Step 11: SMF sends an N1N2 message transfer message (e.g. Namf_Communication_N1N2 Message Transfer) to AMF.

[0253] The N1N2 Message Forwarding message may contain N2 SM information. The N2 SM information carries the following information that the AMF will forward to the (R)AN:

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

[0255] - QFI (QoS flow ID) corresponding to one or more QoS (quality of service) profiles;

[0256] - PDU Session ID: Indicates to the UE the association between RAN resources and a PDU session for the UE;

[0257] - S-NSSAI with value for serving PLMN (i.e. HPLMN S-NSSAI, or VPLMN S-NSSAI in case of LBO roaming);

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

[0259] - UE integrity protection maximum data rate received in PDU Session Establishment Request message: if integrity protection is indicated as "Preferred" or "Required" in the user plane security enforcement information.

[0260] - RSN (redundancy sequence number) parameter

[0261] The N1N2 message transfer message may include an N1 SM container. The N1 SM container includes a PDU Session Establishment Accept message that the AMF will provide to the UE. The PDU Session Establishment Accept message includes the S-NSSAI from the allowed NSSAI. For the LBO roaming scenario, the PDU Session Establishment Accept message includes the S-NSSAI from the allowed NSSAI for the VPLMN, and also includes the corresponding S-NSSAI of the HPLMN from the mapping of the allowed NSSAI received by the SMF in step 3.

[0262] Multiple QoS rules, QoS flow levels, and QoS parameters may be included in the PDU session establishment accept message and N2 SM information within the N1 SM container, if required, for QoS flows associated with QoS rules and QoS profiles.

[0263] If the PDU session establishment fails between steps 5 and 11, the N1N2 message forwarding message contains an N1 SM container containing a PDU session establishment rejection message, but does not contain N2 SM information. The (R)AN sends an NAS message containing a PDU session establishment rejection message to the UE. In this case, steps 12-17 below are omitted.

[0264] (12) Step 12: AMF sends a NAS message containing the PDU Session ID and PDU Session Establishment Accept message destined for the UE and the N2 SM information received from SMF to (R)AN within an N2 PDU Session Request message.

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

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

[0267] If N2 SM information is not included in step 11, steps 14-16b and 17 below are omitted.

[0268] Now, the procedure of Fig. 9 following the procedure of Fig. 8 is described.

[0269] (14) Step 14: (R)AN sends an N2 PDU Session Response message to AMF. The N2 PDU Session Response message may include PDU Session ID, cause, N2 SM information (PDU Session ID, AN tunnel information, accepted / rejected QFI list, user plane enforcement policy notification), etc.

[0270] (15) Step 15: AMF sends an update SM context request message (e.g., Nsmf_PDUSession_UpdateSMContext Request) to SMF. AMF forwards the N2 SM information received from (R)AN to SMF.

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

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

[0273] After this step, the UPF can forward any DL packets that may have been buffered for this PDU session to the UE.

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

[0275] (17) Step 17: SMF sends an update SM context response message (e.g., Nsmf_PDUSession_UpdateSMContext Response) to AMF.

[0276] After this step, AMF forwards the relevant events to which SMF subscribes.

[0277] (18) Step 18: At any time during the procedure after Step 5, if the PDU session establishment is not successful, the SMF can notify the AMF by calling Nsmf_PDUSession_SMContextStatusNotify (release). The SMF can also release the created N4 session, the PDU session address (e.g., IP address) if assigned, and possibly the association with the PCF. In this case, Step 19 below is omitted.

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

[0279] (20) Step 20: SMF can perform SM policy association modification initiated by SMF.

[0280] (21) Step 21: If the PDU session establishment fails after step 4, the SMF may unsubscribe from modifications to the session management subscription data if the SMF no longer processes the UE's PDU session.

[0281] The proposed method may consist of a combination of one or more of the operations / configurations / steps described herein.

[0282] In this specification, UE (User Equipment), terminal, and 5G-RG are used interchangeably.

[0283] In this specification, a 5G-RG may be an RG capable of connecting to a 5GC, which acts as a UE in relation to the 5G core. It supports a security element and can exchange N1 signals with the 5GC. The 5G-RG may be a 5G-BRG or a 5G-CRG. The 5G-RG may be a special UE supporting a service called Fixed Wireless Access (FWA). The 5G-RG may be used to provide Internet services via a 5G wireless connection in environments where it is difficult to install a wired network.

[0284] The operations / compositions / steps / methods described in this specification may be performed or used in combination or complementary manner.

[0285] Non-3GPP devices can receive services from the network through terminals.

[0286] The first and second disclosures described below can be performed in combination.

[0287] I. First Disclosure

[0288] Based on the information received from the network, the terminal can report a device identifier for the non-3GPP device to the network.

[0289] Device identifiers of non-3GPP devices can be unique within an operator network.

[0290] A Device Identity Profile may contain the following information:

[0291] - Connected 3GPP subscription (SUPI).

[0292] - List of device identifiers.

[0293] - Information that can identify non-3GPP devices (e.g. host name, MAC address, port, SSID, etc.)

[0294] - Specific service settings and parameters.

[0295] A device ID profile can be provided to the 5GC using the External Parameter Provisioning procedure. When the AF provides the device ID profile information, the AF may include the GPSI of the associated 3GPP subscription along with the device identifier, allowing the 5GC to recognize the link between the 3GPP subscription and the device identifier. Additionally, the AF may include information that can identify non-3GPP devices, basic QoS parameters for the device identifier (e.g., 5QI and ARP, MBR), and specific service settings and parameters including application-specific QoS requirements.

[0296] The UE / 5G-RG can receive policies / parameters (called N3D policies) to support non-3GPP devices behind the UE / 5G-RG from the PCF. The N3D policies can include authorization policies supporting non-3GPP devices and parameters supporting non-3GPP devices.

[0297] 1) Authorization policy supporting non-3GPP devices

[0298] The authentication policy supporting non-3GPP devices may include PLMNs / locations where the UE is authorized to relay traffic for non-3GPP devices.

[0299] Location information can be transmitted to the terminal in the form of a TA / cell / GLI (Global Line Identifier) / GCI (Global Cable Identifier) ​​list. Additionally, location information can also be transmitted in the form of a geographical area (e.g., coordinate information, address information, etc.).

[0300] An authorization policy supporting non-3GPP devices may include information about where services to non-3GPP devices are permitted through the terminal. Alternatively, an authorization policy supporting non-3GPP devices may simply include information about whether services to specific non-3GPP devices are permitted.

[0301] 2) Parameters supporting non-3GPP devices

[0302] Parameters supporting non-3GPP devices may include the device identifier of the non-3GPP device.

[0303] Parameters supporting non-3GPP devices may include priority information for each device identifier. For example, for non-3GPP devices, device identifiers with higher priorities may be matched first.

[0304] Parameters supporting non-3GPP devices may include information that can identify the non-3GPP device (e.g. host name, MAC address, port, SSID, etc.).

[0305] Information that can identify (distinguish) non-3GPP devices may include information that can be matched to all non-3GPP devices (e.g., host name =*). Information that can be matched to all such non-3GPP devices may be set to the lowest priority.

[0306] Parameters supporting non-3GPP devices may include PDU session parameters for non-3GPP devices (e.g. DNN, S-NSSAI, PDU Session type, etc.).

[0307] Instead of the PCF transmitting PDU session parameters to the terminal, the terminal can determine PDU session parameters based on its own URSP rules. To this end, PIN ID and connection group ID information matching each device identifier can be transmitted to the terminal. Based on this, the terminal can determine PDU session parameters.

[0308] PCF can generate N3D policies based on the Device Identity Profile of UDR and subscription data of UE / 5G-RG.

[0309] Based on the N3D policy received from the PCF, when a non-3GPP device is connected to the terminal (UE / 5G-RG), the terminal can decide whether to establish a new PDU session or use an existing PDU session based on the information contained in the parameters supporting the non-3GPP device.

[0310] The terminal (UE / 5G-RG) may transmit a non-3GPP device report message to report the non-3GPP device to the SMF of the selected PDU session (new PDU session or existing PDU session).

[0311] The non-3GPP device report message may include the identified device identifier and address information allocated for the non-3GPP device.

[0312] When a non-3GPP device is separated from a terminal (UE / 5G-RG), the terminal (UE / 5G-RG) can report separated non-3GPP device information to the SMF.

[0313] SMF can trigger the Nudm_UECM_Update service to notify the connection (or disconnection) of a non-3GPP device.

[0314] SMF can report non-3GPP device information to PCF whenever a non-3GPP device is connected or disconnected.

[0315] PCF can retrieve specific service settings and parameters from the device ID profile in the UDR using the terminal's SUPI and device identifier. Based on the retrieved specific service settings and parameters, PCF can update PCC rules to provide specific QoS for non-3GPP devices.

[0316] 1. Device ID Profile Provisioning Procedure

[0317] 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, and 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.

[0318] FIG. 10 illustrates an example of a device ID profile provisioning procedure according to the first disclosure of the present specification.

[0319] 1) Step 1

[0320] AF can trigger Nnef_PrameterProvision_Create / Update / Delete service actions by sending Nnef_PrameterProvision_Create / Update / Delete requests.

[0321] When AF wants to create / update / delete a Device Identity Profile, AF can trigger Nnef_PrameterProvision_Create / Update / Delete service action to provide Device Identity Profile information including GPSI of connected 3GPP subscription, device identifier(s), information that can identify non-3GPP devices, specific service settings and parameters.

[0322] 2) Step 2

[0323] If the AF is approved by the NEF, the NEF can select the UDM using the GPSI of the connected 3GPP subscription.

[0324] NEF can trigger Nudm_PrameterProvision_Create / Update / Delete service actions by sending Nudm_PrameterProvision_Create / Update / Delete requests.

[0325] 3) Step 3

[0326] When AF is authorized to provision subscriber parameters (expressed as GPSI of the connected 3GPP subscription) by UDM, UDM can request UDR to create, update, or delete device identification profiles via Nudr_DM_Create / Update / Delete requests. The stored information can be used by PCF to apply device identification specific policies.

[0327] 4) Step 4

[0328] UDR can respond to the request in step 3 with a Nudr_DM_Create / Update / Delete response.

[0329] 5) Step 5

[0330] UDM can respond to the request in step 2 with a Nudm_ParameterProvision_Create / Update / Delete response.

[0331] 6) Step 6

[0332] NEF can respond to the request in step 1 with a Nnef_ParameterProvision_Create / Update / Delete response.

[0333] 2. UE / 5G-RG approval procedure supporting non-3GPP devices and non-3GPP device policy provisioning.

[0334] 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, and 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.

[0335] FIG. 11 illustrates an example of a UE / 5G-RG approval procedure according to the first disclosure of this specification.

[0336] 1) Step 1

[0337] A terminal may send a registration request message containing capability information to AMF.

[0338] If the UE supports non-3GPP devices connected behind the UE / 5G-RG, the UE may indicate that capability in the registration request message.

[0339] A terminal may include capability information indicating that the terminal supports the N3D policy in the policy container of the registration request message.

[0340] 2) Step 2

[0341] AMF can retrieve subscription data (subscriber information) of UE / 5G-RG from UDM.

[0342] Subscription data (subscriber information) of the UE / 5G-RG may include information on whether the UE / 5G-RG is authorized to support non-3GPP devices connected behind the UE / 5G-RG.

[0343] Subscription data (subscriber information) may include location / PLMN information where the terminal can use non-3GPP devices (non-3GPP devices connecting behind a UE / 5G-RG).

[0344] Subscription data (subscriber information) may include location / PLMN information of terminals capable of relaying communication between non-3GPP devices and networks.

[0345] In this case, AMF can check the terminal's location, PLMN information, etc. and inform PCF whether it is authorized.

[0346] If the serving PLMN of the terminal does not allow non-3GPP devices (non-3GPP devices connecting behind a UE / 5G-RG), the UDM can send the subscriber information to the AMF including information that non-3GPP devices (non-3GPP devices connecting behind a UE / 5G-RG) are not allowed.

[0347] 3) Step 3

[0348] AMF can send a registration approval message to the terminal.

[0349] AMF can decide whether non-3GPP devices connecting behind a UE / 5G-RG are allowed based on the information received in step 2.

[0350] AMF can inform the UE via registration approval message whether non-3GPP devices (non-3GPP devices connecting behind a UE / 5G-RG) are allowed.

[0351] The registration approval message may include information on whether non-3GPP devices connecting behind a UE / 5G-RG are allowed.

[0352] 4) Step 4

[0353] If the terminal is authorized to support non-3GPP devices (e.g., non-3GPP devices are allowed / authorized for the terminal), the AMF can select a PCF that supports N3D policy provisioning and establish a UE policy association.

[0354] While the UE policy connection is being established, the AMF can report the approved non-3GPP device support capabilities to the PCF. The PCF can then trigger N3D policy provisioning.

[0355] 5) Step 5

[0356] UE policies may be updated.

[0357] PCF can provide the aforementioned N3D policy to the terminal. In this regard, the procedure described in Section 4.2.4.3 of TS 23.502 v18.4.0 can be used.

[0358] During this process, the PCF can verify whether the terminal supports the N3D policy. If the terminal supports the N3D policy, the PCF can provide the aforementioned N3D policy to the terminal.

[0359] PCF can provide the aforementioned N3D policy to the terminal based on the capability information in step 1.

[0360] 3. Procedure for providing services to non-3GPP devices

[0361] 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, and 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.

[0362] Figure 12 illustrates an example of a procedure for providing a service to a non-3GPP device according to the first disclosure of this specification.

[0363] The procedure of Fig. 11 may be performed first.

[0364] 1) Step 1

[0365] Non-3GPP devices can connect to UE / 5G-RG.

[0366] 2) Step 2

[0367] UE / 5G-RG can receive N3D policy from the network (e.g., PCF) through step 5 of FIG. 11.

[0368] Based on the N3D policy, UE / 5G-RG can identify non-3GPP devices.

[0369] Based on the N3D policy, the UE / 5G-RG can determine the device identifier for the connected non-3GPP device. For example, the UE / 5G-RG can determine the device identifier corresponding to the connected non-3GPP device in the N3D policy.

[0370] Based on the N3D policy, the UE / 5G-RG can determine the parameters of the PDU session for the connected non-3GPP device. For example, the UE / 5G-RG can determine the parameters of the PDU session corresponding to the connected non-3GPP device based on the N3D policy.

[0371] Based on the N3D policy (e.g. parameters of the PDU session), the UE / 5G-RG can establish a PDU session for a non-3GPP device or select an existing PDU session.

[0372] For example, an N3D policy may include device identifiers that map to non-3GPP devices.

[0373] If there is no device identifier mapped to a non-3GPP device in the N3D policy, the UE / 5G-RG may disconnect from the non-3GPP device and not provide service.

[0374] To receive an updated N3D policy, the terminal may include information requesting the N3D policy in the policy container while performing registration.

[0375] For example, a terminal can include information requesting an N3D policy in the policy container of a registration request message and transmit it to the network. Based on this, the terminal can receive an updated N3D policy.

[0376] 3) Step 3

[0377] UE / 5G-RG can assign IP addresses to non-3GPP devices.

[0378] UE / 5G-RG can allocate IP addresses for non-3GPP devices and transmit them to non-3GPP devices.

[0379] 4) Step 4

[0380] The UE / 5G-RG may send a message to the SMF containing device identifier and / or address information (e.g. IP address / port range or MAC address) for the non-3GPP device.

[0381] For example, the message may be a non-3GPP device report message or a PDU session modification message. The message may be an N1 SM NAS message transmitted to the AMF along with a PDU session ID. The message may then be forwarded to the SMF.

[0382] Address information for non-3GPP devices may include not only address information but also various information such as host name, port, SSID, etc.

[0383] When multiple non-3GPP devices are connected to the UE / 5G-RG, the message (e.g., non-3GPP device report message, PDU session modification message) may include information about the multiple non-3GPP devices.

[0384] If a single device identifier can be used by multiple non-3GPP devices, the UE / 5G-RG may not send the above message (e.g., non-3GPP device report message, PDU session modification message) every time the non-3GPP device connects (or disconnects). In this case, the UE / 5G-RG may only send the message to the network when a new device identifier is used.

[0385] 5) Step 5

[0386] SMF can send Nudm_UECM_Update to UDM.

[0387] SMF can trigger Nudm_UECM_Update to notify UDM of non-3GPP devices (non-3GPP devices connected to the terminal, non-3GPP devices corresponding to device identifiers). For example, SMF can send UDM information about device identifiers.

[0388] The UDM can determine the number of non-3GPP devices behind the UE / 5G-RG. Based on this, the UDM can decide whether to approve the non-3GPP device.

[0389] Nudm_UECM_Update may contain device identifier, non-3GPP information (e.g. IP address / MAC address, host name, port, SSID, etc.).

[0390] The maximum number of non-3GPP devices allowed in a UE / 5G-RG or the maximum number of allowed device identifiers may be set in the UDM. Based on this, the UDM can limit the number of non-3GPP devices / device identifiers.

[0391] For example, based on the received device identifier, the UDM can determine the number of non-3GPP devices / device identifiers allowed for the UE / 5G-RG. Based on this, the UDM can decide whether to grant permission for the non-3GPP device (device identifier).

[0392] UDM can send approval status for the non-3GPP device (device identifier) ​​to SMF.

[0393] 6) Step 6

[0394] The SMF can determine whether a non-3GPP device can receive services through the UE.

[0395] SMF can send a response message for step 4 (e.g., non-3GPP device report response message) to UE / 5G-RG.

[0396] The above response message may include information on whether a non-3GPP device can receive services via UE / 5G-RG (whether or not the non-3GPP device is authorized).

[0397] 7) Step 7

[0398] The SMF may transmit device identifiers and / or associated address information to the PCF.

[0399] This behavior may be based on previously setting Policy Control Request Triggers (PCRTs) that cause PCF to notify SMF.

[0400] 8) Step 8

[0401] PCF can retrieve specific service settings and parameters of device identifiers from UDR in the device identification profile using SUPI of UE / 5G-RG and device identifiers of non-3GPP devices.

[0402] For example, the PCF can send a message to the UDR that includes the SUPI of the UE / 5G-RG and the device identifier of the non-3GPP device. Based on this, the UDR can find specific service settings and parameters of the device identifier in the device identification profile. Then, the UDR can send the device identification profile (or specific service settings and parameters of the device identifier in the device identification profile) to the PCF.

[0403] 9) Step 9

[0404] Based on the device identification profile (or specific service settings and parameters of the device identifier in the device identification profile), the PCF can update the PCC rules and trigger the PDU Session Modification procedure. Based on the updated PCC rules, appropriate QoS can be provided for non-3GPP devices.

[0405] After this, the network can provide appropriate QoS for non-3GPP devices.

[0406] 10) Step 10

[0407] Non-3GPP devices can disconnect from the UE / 5G-RG.

[0408] 11) Step 11

[0409] To notify a non-3GPP device that has been released, steps 4 through 7 described above may be performed.

[0410] 4. Impact on services, entities, and interfaces

[0411] N3D policies can be provisioned to UE / 5G-RG.

[0412] The UE / 5G-RG can identify non-3GPP devices connected to the UE / 5G-RG and send NAS SM messages (e.g., non-3GPP device reporting messages).

[0413] AMF can select a PCF that supports N3D policy provisioning and establish a UE policy association with the PCF.

[0414] SMF can support non-3GPP device reporting messages.

[0415] SMF can register device identifiers of non-3GPP devices (non-3GPP devices behind the UE / 5G-RG) in UDM.

[0416] PCF can support receiving device identifiers of non-3GPP devices (non-3GPP devices behind the UE / 5G-RG) from SMF.

[0417] PCF can retrieve specific service settings and parameters of the device identification profile from the UDR.

[0418] UDR can support provisioning of Device Identity Profiles.

[0419] AF can support provisioning of Device Identity Profiles.

[0420] II. Second Disclosure

[0421] If charging for non-3GPP devices is required, the 5GC may want to authenticate the non-3GPP devices. Furthermore, even if charging is not required, the 5GC may want to support services or QoS only for authenticated terminals.

[0422] Therefore, authentication for non-3GPP devices may be supported depending on operator policy.

[0423] Device identifiers of non-3GPP devices can be unique at least within the operator's network.

[0424] A device ID profile can contain the following information:

[0425] - Connected 3GPP subscription (SUPI).

[0426] - Device identifier list: Information that can identify non-3GPP devices (e.g., host name, MAC address, port, SSID, etc.), as well as specific service settings and parameters. Authentication required.

[0427] Device identifiers in a PLMN can be unique. For example, if there are duplicate device identifiers, AF requests may be rejected. Alternatively, the device identifier may include an AF-specific ID.

[0428] Random MAC addresses may not be supported if only MAC addresses are used to identify non-3GPP devices.

[0429] Device ID profiles can be provided to 5GC using the external parameter provisioning procedure described in section 4.15.6.2 of TS 23.502 v18.4.0.

[0430] When AF provides device ID profile information, AF may include the GPSI of the connected 3GPP subscription along with the device identifier so that 5GC can recognize the link between the 3GPP subscription and the device identifier.

[0431] Additionally, the AF may contain information that can identify non-3GPP devices, basic QoS parameters for device identifiers (e.g., 5QI and ARP, MBR), and specific service settings and parameters including application-specific QoS requirements.

[0432] The UE / 5G-RG can receive policies / parameters (called N3D policies) from the PCF to support non-3GPP devices behind the UE / 5G-RG. This may include the following information:

[0433] 1) Authorization policy to support non-3GPP devices

[0434] - Whether the UE can support non-3GPP devices

[0435] 2) Parameters to support non-3GPP devices

[0436] - For each device identifier of a non-3GPP device

[0437] -- Information that can identify non-3GPP devices (e.g., host name, MAC address, port, SSID, etc.)

[0438] -- PDU session parameters for non-3GPP devices (e.g. DNN, S-NSSAI, PDU session type, etc.)

[0439] -- Whether authentication is required

[0440] PCF can generate N3D policies based on the device ID profile of UDR and subscription data of UE / 5G-RG.

[0441] When a non-3GPP device is connected to the UE / 5G-RG based on the N3D policy received from the PCF, the UE / 5G-RG can decide whether to establish a new PDU session or use an existing PDU session based on the information in "2) Parameters for supporting non-3GPP devices". The UE / 5G-RG can report the information of the non-3GPP 3GPP device connected to the SMF of the selected PDU session (new PDU session or existing PDU session) by sending a NAS SM message (e.g., Modify PDU Session). This may include the identified device identifier and the assigned address information of the non-3GPP device.

[0442] When a non-3GPP device is disconnected from the UE / 5G-RG, the UE / 5G-RG may also report the disconnected non-3GPP device information to the SMF.

[0443] The N3D policy can also indicate whether the identified non-3GPP device requires authentication. If authentication is required, the UE / 5G-RG can perform authentication before reporting the non-3GPP device information to the SMF.

[0444] The NAS SM message sent from UE / 5G-RG may be similar to the Remote UE Report (Remote User ID, Remote UE info) message sent from 5G ProSe Layer-3 UE-to-Network Relay to SMF for PDU sessions related to the relay.

[0445] The SMF can report non-3GPP device information to the PCF whenever a non-3GPP device is connected or disconnected. The PCF can use the UE's SUPI and device identifier to retrieve specific service settings and parameters from the device identifier in the device ID profile in the UDR. Based on the retrieved specific service settings and parameters, the PCF can update the PCC rules to provide specific QoS for the non-3GPP device.

[0446] In this specification, non-3GPP devices can be distinguished based on N3D policies generated in PCF.

[0447] In this specification, based on the N3D policy, the terminal can determine PDU session parameters.

[0448] 1. Device ID Profile Provisioning Procedure

[0449] The contents of Fig. 10 can be applied.

[0450] UDM may not store device identification profiles.

[0451] Only UDR can store device identification profiles.

[0452] 2. UE / 5G-RG approval procedure supporting non-3GPP devices and non-3GPP device policy provisioning.

[0453] This will be described later with reference to Figure 11.

[0454] 1) Step 1

[0455] A terminal may send a registration request message containing capability information to AMF.

[0456] If the UE supports non-3GPP devices connected behind the UE / 5G-RG, the UE may indicate that capability in the '5GMM capability' field of the registration request message.

[0457] 2) Step 2

[0458] AMF can retrieve subscription data (subscriber information) of UE / 5G-RG from UDM.

[0459] Subscription data (subscriber information) of the UE / 5G-RG may include information on whether the UE / 5G-RG is authorized to support non-3GPP devices connected behind the UE / 5G-RG.

[0460] 3) Step 3

[0461] AMF can send a registration approval message to the terminal.

[0462] 4) step

[0463] If the terminal is authorized to support non-3GPP devices (e.g., non-3GPP devices are allowed / authorized for the terminal), the AMF can select a PCF that supports N3D policy provisioning and establish a UE policy association.

[0464] While the UE policy connection is being established, the AMF can report the approved non-3GPP device support capabilities to the PCF. The PCF can then trigger N3D policy provisioning.

[0465] 5) Step 5

[0466] UE policies may be updated.

[0467] PCF can provide the aforementioned N3D policy to the terminal. In this regard, the procedure described in Section 4.2.4.3 of TS 23.502 v18.4.0 can be used.

[0468] 3. Procedure for providing services to non-3GPP devices

[0469] 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, and 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.

[0470] Figure 13 illustrates an example of a procedure for providing a service to a non-3GPP device according to the second disclosure of this specification.

[0471] The procedure of Fig. 11 may be performed first.

[0472] 1) Step 1

[0473] Non-3GPP devices can connect to UE / 5G-RG (step 1a).

[0474] Based on information that can identify non-3GPP devices in the N3D policy (e.g., host name, MAC address, port, SSID, etc.), UE / 5G-RG can identify non-3GPP devices.

[0475] The N3D policy may include device identifiers corresponding to connected non-3GPP devices.

[0476] The N3D policy may include information about whether authentication is required per device identifier.

[0477] If the N3D policy indicates that authentication is required for the detected device identifier (the device identifier corresponding to the connected non-3GPP device), the UE / 5G-RG may send a NAS MM message (e.g., non-3GPP device authentication request) containing the detected device identifier to the AMF (step 1b).

[0478] AMF can trigger authentication of non-3GPP devices. Based on this, authentication of non-3GPP devices can be performed (step 1c).

[0479] Once authentication is complete, AMF can send a notification to the terminal indicating whether authentication was successful (step 1d).

[0480] If authentication is successful, the next step can be performed.

[0481] Alternatively, the UE / 5G-RG can always perform step 1b and the AMF can perform step 1c as needed, without informing the UE / 5G-RG via the N3D policy whether authentication is required.

[0482] Alternatively, the N3D policy can be used to indicate to the UE / 5G-RG that authentication is not required, and the UE / 5G-RG can always perform step 1b, and the AMF can skip step 1c and go straight to step 1d, indicating that authentication is not required.

[0483] AMF may trigger authentication of a non-3GPP device based on various information. For example, AMF may retrieve User Identity Profile (UIP) information from the UDM to determine whether authentication is required.

[0484] Alternatively, the operator policy / local configuration may be set in the AMF to always perform non-3GPP device authentication for a specific DNN / S-NSSAI.

[0485] Alternatively, the operator policy / local configuration may be set in AMF to force AMF to always perform non-3GPP device authentication.

[0486] Alternatively, the subscriber information of the UE may include information that authentication must be performed for non-3GPP devices connected to the UE.

[0487] 2) Step 2

[0488] Based on the PDU session parameters of the N3D policy, the terminal can establish a PDU session. Or

[0489] Alternatively, based on the PDU session parameters of the N3D policy, the terminal can select an existing PDU session.

[0490] A single PDU session can be shared by multiple non-3GPP devices.

[0491] A terminal may not use URSP rules to establish a PDU session or select an existing PDU session for a non-3GPP device.

[0492] 3) Step 3

[0493] UE / 5G-RG can assign IP addresses to non-3GPP devices.

[0494] For example, based on the IP address of the established PDU session or the selected PDU session, the UE / 5G-RG can allocate an IP address to a non-3GPP device using 'IP prefix delegation' or NAT.

[0495] UE / 5G-RG can allocate IP addresses for non-3GPP devices and transmit them to non-3GPP devices.

[0496] 4) Step 4

[0497] UE / 5G-RG can send NAS SM messages (e.g. PDU Session Modification) to SMF.

[0498] NAS SM messages (e.g. PDU Session Modification) may contain device identifiers and address information (e.g. IP address / port range or MAC address) of non-3GPP devices.

[0499] Alternatively, without performing steps 1b to 1d, the UE / 5G-RG can include the device identifier in the UL NAS Transport message so that the AMF can see the device identifier when sending the NAS SM message in step 4. Based on this, the AMF can, if necessary, send a rejection message to the UE for the UL NAS Transport message to indicate that authentication is required. Furthermore, after sending the rejection message, the AMF can perform the authentication procedure. For this purpose, the AMF can obtain the User Identity Profile information from the UDM and determine whether authentication is required. Alternatively, the AMF may be configured to always perform non-3GPP device authentication for specific DNNs / S-NSSAIs by operator policy.

[0500] Alternatively, based on the device identifier that the UE / 5G-RG sends to the SMF, the SMF can determine whether authentication is required for a non-3GPP device. This determination can be made based on information about whether authentication is required for a specific device identifier included in a PCC rule generated by the PCF based on the device identifier profile. Alternatively, the SMF can be configured to always perform non-3GPP device authentication for a specific DNN / S-NSSAI. Alternatively, the SMF can directly retrieve the device identifier profile for the device identifier from the UDM and determine whether authentication is required based on this. Furthermore, the device identifier profile information can include DN-AAA information that must perform authentication. In this case, a procedure similar to conventional secondary authentication can be used. In this case, the SMF can include the device identifier in the NAS message for authentication (e.g., PDU session authentication command, PDU session authentication complete, PDU session authentication result) and transmit it to indicate that authentication is for a specific device identifier.

[0501] When NAT is used in UE / 5G-RG, when UE / 5G-RG transmits non-3GPP device address information, UE may transmit IP address and port range used by non-3GPP devices.

[0502] 5) Step 5

[0503] SMF may send a NAS SM message (e.g. PDU Session Modification) to UE / 5G-RG containing whether non-3GPP devices are allowed to receive services.

[0504] 6) Step 6

[0505] SMF can provide device identifiers and associated address information to PCF.

[0506] 7) Step 7

[0507] Using the SUPI of the terminal and the device identifier of the non-3GPP device, the PCF can retrieve specific service settings and parameters of the device identifier from the device identification profile from the UDR.

[0508] 8) Step 8

[0509] PCF can update PCC rules based on device identification profile.

[0510] A PDU session modification procedure to provide QoS to non-3GPP devices by UE / 5G-RG can be triggered by PCF.

[0511] After this, the network can provide appropriate QoS for non-3GPP devices.

[0512] 9) Step 9

[0513] Non-3GPP devices can disconnect from the UE / 5G-RG.

[0514] 10) Step 10

[0515] Steps 4 to 8 may be performed. This allows the UE / 5G-RG to notify the network of the disconnection of a non-3GPP device.

[0516] 4. Impact on services, entities, and interfaces

[0517] N3D policies can be provisioned to UE / 5G-RG.

[0518] UE / 5G-RG can identify non-3GPP devices connected to UE / 5G-RG and send NAS SM messages.

[0519] UE / 5G-RG can support authentication of non-3GPP devices.

[0520] AMF can select a PCF that supports N3D policy provisioning. AMF can establish a UE policy association with the PCF.

[0521] AMF can support authentication of non-3GPP devices upon request from UE / 5G-RG.

[0522] SMF can support receiving NAS SM messages containing non-3GPP device information.

[0523] SMF can register device identifiers of non-3GPP devices (non-3GPP devices behind the UE / 5G-RG) in UDM.

[0524] PCF can support receiving device identifiers of non-3GPP devices (non-3GPP devices behind the UE / 5G-RG) from SMF.

[0525] PCF can retrieve specific service settings and parameters of the device identification profile from the UDR.

[0526] UDM can support storing device identifiers and limit the maximum number of device identifiers for non-3GPP devices.

[0527] UDM can support provisioning of Device Identity Profiles.

[0528] UDR can support provisioning of Device Identity Profiles.

[0529] AF can support provisioning of Device Identity Profiles.

[0530] Non-3GPP devices can support authentication of non-3GPP devices.

[0531] In this specification, a method for distinguishing a terminal from a non-3GPP device based on information provided by the network may be proposed.

[0532] 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, and 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.

[0533] Figures 14a and 14b illustrate examples of procedures according to the disclosure of the present specification.

[0534] 1) Step 1

[0535] If the terminal (UE / 5G-RG) supports non-3GPP devices (non-3GPP devices connecting behind the UE / 5G-RG), the terminal can include the terminal's capability information in a registration request message and transmit it to the network.

[0536] A terminal may include capability information indicating that the terminal supports the N3D policy in the policy container of the registration request message.

[0537] 2) Step 2

[0538] AMF can send a registration approval message to the terminal.

[0539] AMF can inform the UE via registration approval message whether non-3GPP devices (non-3GPP devices connecting behind a UE / 5G-RG) are allowed.

[0540] 3) Step 3

[0541] If the terminal is authorized to support non-3GPP devices (e.g., non-3GPP devices are allowed / authorized for the terminal), the AMF can select a PCF that supports N3D policy provisioning and establish a UE policy association.

[0542] While the UE policy connection is being established, the AMF can report the approved non-3GPP device support capabilities to the PCF. The PCF can then trigger N3D policy provisioning.

[0543] 4) step

[0544] UE policies may be updated.

[0545] PCF can provide the aforementioned N3D policy to the terminal. In this regard, the procedure described in Section 4.2.4.3 of TS 23.502 v18.4.0 can be used.

[0546] During this process, the PCF can verify whether the terminal supports the N3D policy. If the terminal supports the N3D policy, the PCF can provide the aforementioned N3D policy to the terminal.

[0547] 5) Step 5

[0548] Non-3GPP devices can connect to UE / 5G-RG.

[0549] 6) Step 6

[0550] In Step 4, the UE / 5G-RG can receive N3D policy from the network (e.g., PCF).

[0551] Based on the N3D policy, UE / 5G-RG can identify non-3GPP devices.

[0552] Based on the N3D policy, the UE / 5G-RG can determine the device identifier for the connected non-3GPP device. For example, the UE / 5G-RG can determine the device identifier corresponding to the connected non-3GPP device in the N3D policy.

[0553] Based on the N3D policy, the UE / 5G-RG can determine the parameters of the PDU session for the connected non-3GPP device. For example, the UE / 5G-RG can determine the parameters of the PDU session corresponding to the connected non-3GPP device based on the N3D policy.

[0554] Based on the N3D policy (e.g. parameters of the PDU session), the UE / 5G-RG can establish a PDU session for a non-3GPP device or select an existing PDU session.

[0555] For example, an N3D policy may include device identifiers that map to non-3GPP devices.

[0556] If there is no device identifier mapped to a non-3GPP device in the N3D policy, the UE / 5G-RG may disconnect from the non-3GPP device and not provide service.

[0557] To receive an updated N3D policy, the terminal may include information requesting the N3D policy in the policy container while performing registration.

[0558] For example, a terminal can include information requesting an N3D policy in the policy container of a registration request message and transmit it to the network. Based on this, the terminal can receive an updated N3D policy.

[0559] The N3D policy may include a Non-3GPP Device Identifier for non-3GPP devices.

[0560] For example, the Non-3GPP Device Identifier for a non-3GPP device in the N3D policy may be 'My Notebook'. The N3D policy may include address information (e.g., MAC Address = "AA:BB:CC:DD:EE:00") and PDU session parameters (e.g., DNN#A, S-NSSAI#X) of the device identifier (My Notebook).

[0561] For example, the Non-3GPP Device Identifier for a non-3GPP device in the N3D policy may be 'My wearable watch'. The N3D policy may include address information (e.g., MAC Address = "QQ:RR:YY:NN:MM:SS") and PDU session parameters (e.g., DNN#B, S-NSSAI#Y) of the device identifier (My wearable watch).

[0562] 7) Step 7

[0563] The contents of step 3 of Fig. 12 can be applied.

[0564] 8) Step 8

[0565] The contents of step 4 of Fig. 12 can be applied.

[0566] 9) Step 9

[0567] The contents of step 7 of Figure 12 can be applied.

[0568] 10) Step 10

[0569] SMF can send a PDU Session Modification Command message to UE / 5G-RG.

[0570] The PDU Session Modification Command message may contain information on whether a non-3GPP device can receive services through the UE / 5G-RG.

[0571] 11) Step 11

[0572] The UE / 5G-RG may send a PDU Session Modification Complete message to the SMF.

[0573] 12) Step 12

[0574] The contents of step 8 of Fig. 12 can be applied.

[0575] 13) Step 13

[0576] Based on the device identification profile (or specific service settings and parameters of the device identifier in the device identification profile), the PCF can update the PCC rules to provide QoS for non-3GPP devices to the UE / 5G-RG.

[0577] PCF can send updated PCC rules to SMF.

[0578] 14) Step 14

[0579] Based on the PCC rules received from the PCF, the SMF can trigger the PDU Session Modification procedure to provide QoS for non-3GPP devices to the UE / 5G-RG.

[0580] In this procedure, QoS for non-3GPP devices can be provided.

[0581] After this, the network can provide appropriate QoS for non-3GPP devices.

[0582] Based on the information set by the network, the terminal can distinguish non-3GPP devices and thereby provide differentiated QoS support for non-3GPP devices (non-3GPP devices connecting behind a UE / 5G-RG).

[0583] The following actions can be performed:

[0584] - The network can transmit information that can distinguish non-3GPP devices, device identifier information mapped to it, and PDU session parameter information to the UE / 5G-RG.

[0585] - When a non-3GPP device is connected or disconnected, the UE / 5G-RG can send non-3GPP device information (e.g. device identifier information mapped to the non-3GPP device, address information assigned to the non-3GPP device, non-3GPP device name, etc.) to the SMF based on information provided by the network.

[0586] - SMF can notify PCF based on information received from UE / 5G-RG.

[0587] - Based on the device identifier provided by SMF, PCF can obtain the QoS information required for non-3GPP devices using the device identifier from UDR and update the PCC rules.

[0588] 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, and 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.

[0589] Figure 15 illustrates the UE's procedure for disclosure of this specification.

[0590] 1. The UE (User Equipment) can send a registration request message to the AMF (Access Mobility Function).

[0591] The above registration request message may include capability information indicating that the UE supports a non-3GPP device connected to the UE.

[0592] 2. The UE can receive a registration approval message from the AMF.

[0593] 3. Based on the above capability information, the UE can receive an N3D (non-3GPP) policy from a PCF (Policy Control Function).

[0594] The above N3D policy may include device identifier information.

[0595] 4. The UE can send a request message to establish a specific PDU (Packet Data Unit) session to the SMF (Session Management Function).

[0596] 5. The UE can receive an establishment approval message for the specific PDU session from the SMF.

[0597] 6. Based on the specific non-3GPP device being connected to the UE and the device identifier information, the UE can determine a specific device identifier for the specific non-3GPP device.

[0598] The above specific PDU session may be a PDU session for the above specific non-3GPP device.

[0599] 7. Based on the specific non-3GPP device being connected to the UE, the UE may transmit a first message including the specific device identifier to the SMF.

[0600] Based on the first message, the UE can receive a response message from the SMF.

[0601] The above response message may include information on whether the specific non-3GPP device can receive service through the UE.

[0602] The above N3D policy may include parameter information for a PDU session.

[0603] Based on the particular non-3GPP device being connected to the UE and the parameter information, the UE can determine a particular parameter corresponding to the particular PDU session.

[0604] The above registration approval message may include information that non-3GPP devices connected to the UE are allowed.

[0605] The UE may allocate an IP address for the specific non-3GPP device.

[0606] The first message may include the assigned IP address.

[0607] The above allocated IP address may include at least one of a host name, a port, and a service set identifier (SSID).

[0608] The above N3D policy may include authentication information on whether authentication of non-3GPP devices is required.

[0609] Based on the particular non-3GPP device being connected to the UE and the authentication information, the UE can determine whether the particular non-3GPP device requires authentication.

[0610] Based on the specific non-3GPP device requiring authentication, the UE may send an authentication request message to the AMF.

[0611] Based on the above authentication request message, the UE can receive an authentication response message from the AMF.

[0612] The above authentication response message may include information on whether authentication for the specific non-3GPP device was successful.

[0613] 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, and 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.

[0614] Figure 16 illustrates the SMF procedure for the disclosure of this specification.

[0615] 1. The SMF (Session Management Function) can receive a request message from the UE (User Equipment) to establish a specific PDU session for a specific non-3GPP device.

[0616] The above specific non-3GPP device may be a device connected to the UE via non-3GPP.

[0617] 2. The SMF may send an establishment approval message for the specific PDU session to the UE.

[0618] 3. The SMF can receive a first message from the UE.

[0619] The first message may include a device identifier corresponding to the specific non-3GPP device.

[0620] 4. Based on the first message, the SMF can determine whether the specific non-3GPP device can receive service through the UE.

[0621] Based on the first message, the step may include the SMF transmitting a first response message to the UE.

[0622] The above first response message may include the result of the above decision.

[0623] The above SMF can send a second message to UDM (Unified Data Management).

[0624] The second message may include information about the device identifier.

[0625] Based on the second message, the SMF can receive a second response message from the UDM.

[0626] The second response message may include specific information about whether the specific non-3GPP can receive service through the UE.

[0627] The step of determining whether the specific non-3GPP device can receive service through the UE may be performed based on the specific information.

[0628] The second message may include at least one of address information, host name, port, and SSID for the specific non-3GPP.

[0629] The above SMF can transmit information about the device identifier to the PCF (Policy Control Function).

[0630] The first message may include an IP address for the specific non-3GPP device allocated by the UE.

[0631] Hereinafter, a device for performing communication according to some embodiments of the present specification will be described.

[0632] For example, a device may include a processor, a transceiver, and memory.

[0633] For example, a processor may be configured to be operatively coupled with memory and a processor.

[0634] The operations performed by the processor include: a step for a UE (User Equipment) to transmit a registration request message to an AMF (Access Mobility Function); the registration request message includes capability information indicating that the UE supports a non-3GPP device connected to the UE, and the UE receives a registration approval message from the AMF; a step for the UE to receive an N3D (non-3GPP) policy from a PCF (Policy Control Function) based on the capability information; the N3D policy includes device identifier information, and the UE transmits a request message for establishing a specific PDU (Packet Data Unit) session to an SMF (Session Management Function); a step for the UE to receive an establishment approval message for the specific PDU session from the SMF; a step for the UE to determine a specific device identifier for the specific non-3GPP device based on the fact that the specific non-3GPP device is connected to the UE and the device identifier information; The specific PDU session may be a PDU session for the specific non-3GPP device, and may include a step of the UE transmitting a first message including the specific device identifier to the SMF based on the specific non-3GPP device being connected to the UE.

[0635] Below, a processor of a device for providing communication according to some embodiments of the present specification is described.

[0636] The operations performed by the processor include: a step for a UE (User Equipment) to transmit a registration request message to an AMF (Access Mobility Function); the registration request message includes capability information indicating that the UE supports a non-3GPP device connected to the UE, and the UE receives a registration approval message from the AMF; a step for the UE to receive an N3D (non-3GPP) policy from a PCF (Policy Control Function) based on the capability information; the N3D policy includes device identifier information, and the UE transmits a request message for establishing a specific PDU (Packet Data Unit) session to an SMF (Session Management Function); a step for the UE to receive an establishment approval message for the specific PDU session from the SMF; a step for the UE to determine a specific device identifier for the specific non-3GPP device based on the fact that the specific non-3GPP device is connected to the UE and the device identifier information; The specific PDU session may be a PDU session for the specific non-3GPP device, and may include a step of the UE transmitting a first message including the specific device identifier to the SMF based on the specific non-3GPP device being connected to the UE.

[0637] Hereinafter, a non-volatile computer-readable medium storing one or more commands for providing mobile communication according to some embodiments of the present specification is described.

[0638] According to some embodiments of the present disclosure, the technical features of the present disclosure may be implemented directly in hardware, software executed by a processor, or a combination of the two. For example, a method performed by a wireless device in wireless communication may be implemented in hardware, software, firmware, or any combination thereof. For example, the software may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or other storage media.

[0639] Some examples of storage media are coupled to the processor, allowing the processor to read information from the storage media. Alternatively, the storage media may be integrated into the processor. The processor and storage media may reside in an ASIC. In other examples, the processor and storage media may reside as separate components.

[0640] Computer-readable media may include tangible and non-volatile computer-readable storage media.

[0641] For example, nonvolatile computer-readable media may include random access memory (RAM), such as synchronized dynamic random access memory (SDRAM), read-only memory (ROM), non-volatile random access memory (NVRAM), read-only memory (EEPROM), flash memory, magnetic or optical data storage media, or any other media that can be used to store instructions or data structures. Nonvolatile computer-readable media may also include combinations of the above.

[0642] Additionally, the methods described herein can be realized at least in part by a computer-readable communication medium that carries or transmits code in the form of instructions or data structures and that can be accessed, read, and / or executed by a computer.

[0643] According to some embodiments of the present disclosure, a non-transitory computer-readable medium has one or more instructions stored thereon. The one or more stored instructions can be executed by a processor of a base station.

[0644] One or more stored commands include: a step for a UE (User Equipment) to transmit a registration request message to an AMF (Access Mobility Function); the registration request message includes capability information indicating that the UE supports a non-3GPP device connected to the UE; and a step for the UE to receive a registration approval message from the AMF; a step for the UE to receive an N3D (non-3GPP) policy from a PCF (Policy Control Function) based on the capability information; the N3D policy includes device identifier information; and a step for the UE to transmit a request message for establishing a specific PDU (Packet Data Unit) session to an SMF (Session Management Function); a step for the UE to receive an establishment approval message for the specific PDU session from the SMF; a step for the UE to determine a specific device identifier for the specific non-3GPP device based on the fact that the specific non-3GPP device is connected to the UE and the device identifier information; The specific PDU session may be a PDU session for the specific non-3GPP device, and may include a step of the UE transmitting a first message including the specific device identifier to the SMF based on the specific non-3GPP device being connected to the UE.

[0645] Hereinafter, a non-volatile computer-readable medium storing one or more commands for providing mobile communication according to some embodiments of the present specification is described.

[0646] This specification may have various effects.

[0647] For example, through the procedures disclosed herein, a QoS policy suitable for a non-3GPP device connected to a terminal can be applied.

[0648] The effects that can be achieved through 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.

[0649] 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. As a method, A step in which a UE (User Equipment) transmits a registration request message to an AMF (Access Mobility Function); The above registration request message includes capability information that the UE supports a non-3GPP device connected to the UE, A step in which the UE receives a registration approval message from the AMF; A step in which the UE receives an N3D (non-3GPP) policy from a PCF (Policy Control Function) based on the above capability information; The above N3D policy includes device identifier information, A step in which the UE transmits a request message for establishing a specific PDU (Packet Data Unit) session to the SMF (Session Management Function); A step in which the UE receives an establishment approval message of the specific PDU session from the SMF; A step in which the UE determines a specific device identifier for the specific non-3GPP device based on the specific non-3GPP device being connected to the UE and the device identifier information; The above specific PDU session is a PDU session for the above specific non-3GPP device, A method comprising the step of the UE transmitting a first message including the specific device identifier to the SMF based on the specific non-3GPP device being connected to the UE.

2. In paragraph 1, Based on the first message, the UE further includes a step of receiving a response message from the SMF, A method wherein the response message includes information on whether the specific non-3GPP device can receive service through the UE.

3. In paragraph 1 or 2, The above N3D policy contains parameter information for the PDU session, A method further comprising the step of the UE determining a specific parameter corresponding to the specific PDU session based on the specific non-3GPP device being connected to the UE and the parameter information.

4. In any one of the clauses 1 to 3, A method wherein the registration approval message includes information that a non-3GPP device connected to the UE is permitted.

5. In any one of paragraphs 1 to 4, The UE further comprises a step of allocating an IP address for the specific non-3GPP device, A method wherein the first message includes the assigned IP address.

6. In paragraph 5, A method wherein the above allocated IP address includes at least one of a host name, a port, and an SSID (service set identifier).

7. In any one of paragraphs 1 to 6, The above N3D policy contains authentication information on whether authentication of non-3GPP devices is required, A step in which the UE determines whether the specific non-3GPP device requires authentication based on the specific non-3GPP device being connected to the UE and the authentication information; A step in which the UE transmits an authentication request message to the AMF based on the specific non-3GPP device requiring authentication; Based on the above authentication request message, the UE further includes a step of receiving an authentication response message from the AMF, A method wherein the authentication response message includes information on whether authentication for the specific non-3GPP device is successful.

8. As a method, A step in which the SMF (Session Management Function) receives a request message for establishing a specific PDU session for a specific non-3GPP device from a UE (User Equipment); The above specific non-3GPP device is a device connected to the UE via non-3GPP, A step in which the SMF transmits an establishment approval message of the specific PDU session to the UE; A step in which the SMF receives a first message from the UE; The first message includes a device identifier corresponding to the specific non-3GPP device, Based on the first message, the SMF determines whether the specific non-3GPP device can receive service through the UE; Based on the first message, the SMF comprises a step of transmitting a first response message to the UE, A method wherein the first response message includes the result of the decision.

9. In paragraph 8, A step in which the above SMF transmits a second message to UDM (Unified Data Management); The second message contains information about the device identifier, A step in which the SMF receives a second response message from the UDM based on the second message; The second response message includes specific information about whether the specific non-3GPP can receive service through the UE, The step of determining whether the specific non-3GPP device can receive service through the UE by the SMF is: a method performed based on the specific information.

10. In paragraph 9, A method wherein the second message includes at least one of address information, host name, port, and SSID for the specific non-3GPP.

11. In any one of the clauses 8 to 10, A method further comprising the step of the SMF transmitting information about the device identifier to a PCF (Policy Control Function).

12. In any one of the clauses 8 to 11, A method wherein the first message includes an IP address for the specific non-3GPP device allocated by the UE.

13. As a UE (User Equipment) performing communication, At least one transmitter and receiver; Contains at least one processor, A UE wherein the operation performed by at least one processor is a method according to any one of claims 1 to 7.

14. As a SMF (Session Management Function) that performs communication, At least one transmitter and receiver; Contains at least one processor, The operation performed by the at least one processor is an SMF method according to any one of claims 8 to 12.

15. As an apparatus in mobile communication, at least one processor; and At least one memory storing instructions and being operably electrically connected to the at least one processor, A device wherein the operation performed based on the command being executed by the at least one processor is a method according to any one of claims 1 to 7.

16. A non-volatile computer-readable storage medium that records commands, A non-volatile computer-readable storage medium, wherein the instructions, when executed by one or more processors, cause the one or more processors to perform an operation according to any one of claims 1 to 7.

Images