Tethering service method

Abstract

The present disclosure provides a method. The method comprises the steps of: an SMF receiving, from a UE, a NAS message related to a PDU session for the UE; on the basis that the UE has a support capability for a tethering service using a tethered device, the SMF stores first state information indicating an enable state of the support capability of the UE before the SMF receives the NAS message, the NAS message includes second state information indicating the enable state of the support capability of the UE, and the first state information is different from the second state information, the SMF determining that the enable state of the UE has been changed; on the basis of the determination, the SMF requesting an update on a PCC rule from a PCF, the request including the second state information regarding the enable state; and on the basis of the request, the SMF receiving the updated PCC rule from the PCF.

Description

Tethering Service Method

[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] In relation to tethering services, there is a need for a method by which policies and / or rules are provided to terminals and nodes of the network.

[0006] Based on the change in the activation status of the terminal's tethered device support function, the SMF requests a new rule from the PCF.

[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 a PDU session establishment procedure to which the implementation of the present specification applies.

[0013] Figure 8 shows an example of a flowchart according to the first embodiment of the present specification.

[0014] Figure 9 shows an example of a flowchart according to the second embodiment of the present specification.

[0015] Figures 10 and 11 illustrate examples of flowcharts according to the third embodiment of the present specification.

[0016] Figure 12 illustrates the SMF procedure for the disclosure of this specification.

[0017] Figure 13 illustrates the UE's procedure for disclosure of this specification.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0103] - AUSF (Authentication Server Function)

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

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

[0106] - USDF (Unstructured Data Storage Function)

[0107] - NEF (Network Exposure Function)

[0108] - I-NEF (Intermediate NEF)

[0109] - NRF (Network Repository Function)

[0110] - NSSF (Network Slice Selection Function)

[0111] - PCF (Policy Control Function)

[0112] - SMF (Session Management Function)

[0113] - UDM (Unified Data Management)

[0114] - UDR (Unified Data Repository)

[0115] - UPF (User Plane Function)

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

[0117] - AF (Application Function)

[0118] - UE (User Equipment)

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

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

[0121] - NWDAF (Network Data Analytics Function)

[0122] - CHF (CHarging Function)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0152] Figures 6 and 7 illustrate examples of a PDU session establishment procedure to which the implementation of the present specification applies.

[0153] Establishing a PDU session may involve:

[0154] - UE-initiated PDU session establishment procedure

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

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

[0157] - Network-triggered PDU session establishment procedure

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

[0159] Figures 6 and 7 specify the procedure for establishing a PDU session associated with a single connection type at a given time.

[0160] In the procedures shown in Figures 6 and 7, 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.

[0161] First, the procedure of Fig. 6 is explained.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0198] - RSN (redundancy sequence number) parameter

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0219] In this specification, a mechanism related technology for QoS handling may be described.

[0220] The UE / user can decide whether to use a tethered device.

[0221] According to the implementation of this specification, the network (5GC) can determine whether a tethered device is in use. The network can then effectively perform the following controls:

[0222] - Permit provision of the relevant service to the relevant UE based on subscriber information

[0223] - QoS handling depending on whether a tethered device is used

[0224] The methods proposed in this specification are described below. The methods described below may be performed or used in combination or complementary manner.

[0225] The method proposed in this specification may refer to the architecture, framework and QoS model specified in TS 23.501 v18.3.0, TS 23.502 v18.3.0 and TS 23.503 v18.3.0.

[0226] It may be an issue whether and / or how the 5GC should identify that the UE is using a tethered device for XR traffic.

[0227] It may be an issue whether and / or how 5GC should authorize UEs to use tethered devices for XR traffic.

[0228] In this specification, a tethered PDU session / PDU session for tethering service may be: an independent PDU session for the purpose of transmitting tethered user data and control signals, or a PDU session created for another purpose but intended to perform transmission of tethered user data and control signals through a modification procedure (change of the properties of the PDU session).

[0229] The embodiments described herein may be performed in combination with each other.

[0230] 1. First Example

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

[0232] Figure 8 shows an example of a flowchart according to the first embodiment of the present specification.

[0233] (1) Step 1

[0234] A terminal can send a PDU session establishment request to a network control node (SMF).

[0235] A PDU session establishment request may include whether tethered devices are supported.

[0236] The PDU session establishment request may include whether the tethered device support function is enabled. In other words, the PDU session establishment request may include whether the terminal is currently capable of using the tethered device.

[0237] The PDU session establishment request may include whether the UL PDU set QoS enforcement / handling capability, the QoS enforcement / handling capability (if a tethered device is used) and / or the tethered device support capability are enabled / disabled. That is, the terminal may notify the network control node (SMF) of the aforementioned information.

[0238] QoS enhancement / handling capabilities may be required to support tethering services. Tethering services may refer to services in which a terminal uses a tethered device.

[0239] When creating a tethered PDU session (or when the session is associated with a tethering service) (i.e., creating an independent PDU session for the purpose of transmitting tethered user data and control signals, or changing the properties of a PDU session via a PDU session modification procedure to enable transmission of tethered user data and control signals in a PDU session created for another purpose), the PDU session establishment request may include whether the tethered device support capability is enabled / disabled.

[0240] The terminal can recognize that the PDU session is for tethering (a session related to a tethering service) based on pre-configured local policies or pre-provisioned URSP rules, QoS rules, etc.

[0241] For example, based on the connection capabilities of the traffic descriptor of the URSP rule, the terminal can determine that the session is for tethering (a session related to a tethering service).

[0242] When a terminal first sends a PDU session establishment request for tethering, the terminal may only include tethered device support capability information for XR in the establishment request. After this, when a tethered device is attached (or connected) to the terminal, the terminal may notify the SMF that it serves the tethered device (or that the session is used for the tethered device) through a PDU session modification procedure. This information may be notified to the SMF through a PDU session modification request.

[0243] Based on the pre-configured local policy of the terminal or the pre-provisioned URSP rules, QoS rules (received from SMF), etc., the terminal can determine whether the device connected to it is a device for tethering service (or a tethering device of a specific address / type is connected to it via Bluetooth / Wi-Fi).

[0244] For example, if the tethered device is an XR (Extended Reality) device, the tethered device can transmit its IP information, etc. to the server through application layer signaling. Then, the server can request QoS to the AF with 5GC (refer to procedures such as TS 23.502 v18.3.0 clause 4.15.6.6 (Setting up an AF session with required QoS procedure)). Based on this, when the SMF transmits a QoS rule to the terminal, the terminal can determine that the device connected to it is a device for the tethering service based on the traffic filter information in the QoS rule.

[0245] For example, based on information such as source IP address / port in traffic filter information, the terminal can determine that the device connected to it is a device for tethering service.

[0246] Alternatively, for example, based on the device name, hardware / software information, QoS information requested by the device, etc. of the device connected to the terminal, the terminal can determine that the device connected to the terminal is a device for tethering service.

[0247] A PDU session establishment / modification request may include UE 5GSM Core Network Capability.

[0248] The UE 5GSM Core Network Capability may include information on whether the UE supports the following capabilities. That is, the UE may indicate in the UE 5GSM Core Network Capability whether it supports the following capabilities:

[0249] - "Ethernet" PDU Session Type is supported in EPC as PDN Type "Ethernet";

[0250] - Reflective QoS;

[0251] - Multi-homed IPv6 PDU sessions (only when the Requested PDU Type is set to "IPv6" or "IPv4v6");

[0252] - ATSSS capability;

[0253] - Transfer of Port Management Information containers

[0254] - UL PDU Set QoS enforcement based on the RTP Header Extension for PDU Set Marking as defined in TS 26.522 v17.6.0 (UL PDU Set QoS enforcement based on the RTP Header Extension for PDU Set Marking as defined in TS 26.522

[0179] )

[0255] - Tethered device support features (specialized features for tethered devices, the ability to change the QoS rules applied to detect / enforce uplink traffic based on the QoS rules the network provides to apply when a tethered device is present, etc.)

[0256] - Information on enabling / disabling tethered device support capability (tethered device support capability enabled / disabled)

[0257] The information for enabling / disabling the aforementioned tethered device support feature may also be conveyed through parameter fields of other NAS than the UE 5GSM core network function.

[0258] Enabling tethered device support may indicate that a tethered device is already physically connected to the terminal. Alternatively, enabling tethered device support may indicate the possibility of a tethered device connecting to the terminal.

[0259] Enabling tethered device support may indicate that the current device is capable of using tethered devices. Disabling tethered device support may indicate that the current device is unable to use tethered devices.

[0260] The aforementioned UL PDU Set QoS enhancements and tethered device support features can each be transmitted to the network.

[0261] Alternatively, the aforementioned UL PDU Set QoS enhancements and tethered device support features can be combined and transmitted to the network as a single capability.

[0262] 5GSM core network functions can be transferred from V-SMF to H-SMF during PDU session establishment / modification procedures, if required.

[0263] After the first inter-system change from EPS to 5GS is performed for a PDU session established in EPS, 5GSM core network functions may also be included in the PDU session modification if there are reflective QoS and / or multi-homed IPv6 PDU sessions.

[0264] (2) Step 2

[0265] The network control node (SMF) can obtain subscriber information related to the session.

[0266] The network control node (SMF) can obtain subscriber information related to a session from the UDM.

[0267] Subscriber information may include information about whether the session allows tethered XR services.

[0268] Subscriber information may include a Tethered XR service indication.

[0269] A Tethered XR service indication may indicate whether a DNN and / or S-NSSAI is used for a tethered XR service.

[0270] That is, a Tethered XR service indication may indicate whether the DNN and / or S-NSSAI that includes the session is used (or allowed) for the tethered XR service.

[0271] Subscriber information may include UE authorization for Tethered XR service.

[0272] UE authorization for Tethered XR service may indicate whether the UE is authorized to use a 5GC supported tethered XR service.

[0273] (3) Step 3

[0274] Based on information received from the terminal, subscriber information, local configuration information of the SMF, operator policy, etc., the SMF can decide whether to grant service to the terminal and the tethered device of the corresponding PDU session.

[0275] The SMF determines whether to grant permission for specialized QoS enhancements / handling for terminals using tethered devices. QoS enhancements / handling may refer to services for tethered devices.

[0276] (4) Step 4

[0277] SMF can interact with PCF to obtain policies for providing appropriate QoS.

[0278] At this time, F can include tethered device support capability enabled / disabled information received from the terminal in the message sent to PCF.

[0279] Based on this, PCF can generate PCC rules.

[0280] PCF can transmit the generated PCC rules to SMF.

[0281] (5) Step 5

[0282] SMF can process the received PCC rules.

[0283] SMF can transmit information processed from PCC rules to terminals, NG-RAN, and UPF.

[0284] For example, information processed from PCC rules may be relevant information for QoS handling.

[0285] For example, information processed from the PCC rule may be a PDU Set QoS parameter. The SMF may transmit the PDU Set QoS parameter to the base station (RAN).

[0286] For example, information processed from a PCC rule may be a QoS profile. The SMF may transmit the QoS profile to the base station (RAN).

[0287] For example, information processed from a PCC rule may be a QoS rule. The SMF may transmit the QoS rule to the terminal.

[0288] The terminal can recognize whether it can receive tethering service based on the received QoS rules.

[0289] If tethering service is permitted, the terminal can receive tethering service.

[0290] 2. Second Example

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

[0292] Figure 9 shows an example of a flowchart according to the second embodiment of the present specification.

[0293] A new Policy Control Request Trigger (PCRT) can be defined.

[0294] If PCRT conditions are met, SMF can request a new policy from PCF using the conventional 'SMF initiated SM Policy Association Modification'.

[0295] (1) Step 1

[0296] 1) Step 1-1

[0297] The terminal may support tethered devices.

[0298] The terminal can transmit tethered device support capability enabled / disabled information to the network control node (SMF).

[0299] The information may be transmitted in a PDU session-related NAS message. The PDU session-related NAS message may be a PDU session modification request message. The PDU session-related NAS message may be a PDU session establishment request message.

[0300] Based on the change in information about the tethered device support capability of the terminal, the terminal can transmit tethered device support capability enabled / disabled information.

[0301] 2) Step 1-2

[0302] SMF can recognize (or determine) changes in the tethered device support capability enabled / disabled information.

[0303] The SMF may already have stored information about the activation / deactivation of the tethered device support function of the terminal. Thereafter, the SMF may receive information about the activation / deactivation of the tethered device support function from the terminal. If the received information about the activation / deactivation of the tethered device support function differs from the previously stored information about the activation / deactivation of the tethered device support function, the SMF may recognize the change in the information about the activation / deactivation of the tethered device support function.

[0304] For example, the SMF may receive information from the terminal that the tethered device support feature is activated. The SMF may store information about the activation of the feature on the terminal. Subsequently, the SMF may receive information from the terminal that the tethered device support feature is deactivated. Because the feature has been changed from activated to deactivated, the SMF can recognize the change in the tethered device support feature activation / deactivation information.

[0305] For example, the SMF may receive information from the terminal that the tethered device support feature is disabled. The SMF may store information about the deactivation of the feature on the terminal. Subsequently, the SMF may receive information from the terminal that the tethered device support feature is enabled. Because the feature has been changed from disabled to enabled, the SMF may recognize the change in the tethered device support feature enable / disable information.

[0306] Here, changing the information on enabling / disabling the tethered device support function may be a PCRT condition.

[0307] (2) Step 2

[0308] 1) Step 2-1

[0309] When the SMF recognizes (or determines) that a PCRT condition has been met (change in tethered device support feature enable / disable information), the SMF may perform a conventional 'SMF initiated SM Policy Association Modification'.

[0310] When the SMF recognizes (or determines) that a PCRT condition is met (change in tethered device support feature enable / disable information), the SMF may request an update of the PCC rules by sending the PCF an Npcf_SMPolicyControl_Update. The Npcf_SMPolicyControl_Update may contain the tethered device support feature enable / disable information received by the SMF from the terminal.

[0311] 2) Step 2-2

[0312] Based on information received from SMF (e.g., received tethered device support feature enable / disable information), PCF can update PCC rules.

[0313] 3) Step 2-3

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

[0315] Updated PCC rules may include information about changes in tethered device support availability.

[0316] Information about changes in tethered device support availability may include information that the tethered device support function of the terminal is activated (or deactivated) for tethered XR services.

[0317] (3) Step 3

[0318] SMF can process the received PCC rules.

[0319] SMF can transmit information processed from PCC rules to terminals, NG-RAN, and UPF.

[0320] For example, information processed from PCC rules may be relevant information for QoS handling.

[0321] For example, information processed from the PCC rule may be a PDU Set QoS parameter. The SMF may transmit the PDU Set QoS parameter to the base station (RAN).

[0322] For example, information processed from a PCC rule may be a QoS profile. The SMF may transmit the QoS profile to the base station (RAN).

[0323] For example, information processed from a PCC rule may be a QoS rule. The SMF may transmit the QoS rule to the terminal.

[0324] The first embodiment may be performed and the second embodiment may be performed thereafter.

[0325] For example, according to the first embodiment, the terminal may initiate a session establishment procedure by transmitting tethered device support function activation / deactivation information to the SMF. Furthermore, according to the first embodiment, tethered device services may be permitted for the terminal for the session. If the terminal subsequently transmits different tethered device support function activation / deactivation information to the SMF than before, the second embodiment may be performed.

[0326] 3. Third Example

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

[0328] Figures 10 and 11 illustrate examples of flowcharts according to the third embodiment of the present specification.

[0329] PCF can send policy information (i.e., both policy for activation and policy for deactivation) to SMF for each tethered device support feature activation / deactivation.

[0330] Based on this, SMF can optionally use PCC rules.

[0331] (1) Step 1 - Step 4

[0332] Step 1-step 4 described in Example 1 can be performed.

[0333] However, the information that PCF transmits to SMF in step 4-3 may include all of the following information:

[0334] - Policy on enabling tethered device support features

[0335] - Policy on disabling tethered device support

[0336] (5) Step 5

[0337] Based on the tethered device support feature activation / deactivation information sent by the terminal, the SMF can optionally apply PCC rules. In other words, the SMF can adjust the QOS-related information sent to the UE, NG-RAN, and UPF.

[0338] For example, if the terminal transmits information indicating that the tethered device support feature is enabled in step 1, the SMF can select and apply a policy for tethered device support feature activation from the information received from the PCF. Accordingly, the SMF can process a policy for tethered device support feature activation.

[0339] For example, if the terminal transmits information in step 1 indicating that the tethered device support function is disabled, the SMF can select and apply a policy for disabling the tethered device support function from the information received from the PCF. Accordingly, the SMF can process a policy for disabling the tethered device support function.

[0340] (6) Step 6

[0341] SMF can transmit processed information to terminals, NG-RAN, and UPF.

[0342] For example, the processed information may be relevant information for QoS handling.

[0343] For example, the processed information may be a PDU Set QoS parameter. The SMF may transmit the PDU Set QoS parameter to the base station (RAN).

[0344] For example, the processed information may be a QoS profile. The SMF may transmit the QoS profile to the base station (RAN).

[0345] For example, the processed information may be a QoS rule. The SMF may transmit the QoS rule to the terminal.

[0346] The QoS rule transmitted to the terminal may be a QoS rule for the tethered device support function activation / deactivation information transmitted by the terminal in step 1.

[0347] For example, if in step 1 the terminal transmits information that the tethered device support function is activated, the QoS rule transmitted to the terminal may be a QoS rule for activating the tethered device support function.

[0348] Alternatively, the QoS rules transmitted to the terminal may include both QoS rules for enabling tethered device support and QoS rules for disabling tethered device support. Step 7 described below assumes this case.

[0349] (7) Step 7

[0350] The terminal can apply the corresponding QoS rules depending on the tethered device support function activation / deactivation status.

[0351] Additionally, the terminal may include the following in subsequent procedure messages sent to the network:

[0352] - Information on enabling / disabling tethered device support

[0353] - Information indicating that the terminal has both a QoS rule for activating the tethered device support function and a QoS rule for deactivating the tethered device support function, and that the rules can be applied.

[0354] In accordance with the disclosure of this specification, the following operations may be performed:

[0355] - The first network node (e.g. SMF) can determine whether to use the service for the terminal based on the capability and enable / disable information of the terminal using the tethered device for the XR service and subscriber information, and send the result to the terminal.

[0356] - A second network node (e.g. PCF) can generate PCC rules based on the terminal's function and function activation / deactivation information using a tethered device for XR service and forward them to other network nodes.

[0357] - The first network node (e.g. SMF) can be aware of whether the tethered device support function is enabled / disabled and, if the PCRT condition is met, can request a policy update to the second network node (e.g. PCF) to receive updated PCC rules.

[0358] - The first network node (e.g. SMF) receives each PCC rule according to the tethered device support function activation / deactivation status from the second network node (e.g. PCF), and can selectively use the PCC rule according to the status.

[0359] - The terminal receives QoS rules based on the activation / deactivation status of the tethered device support function received from the network, and can selectively use PCC rules based on the status. Additionally, in a subsequent procedure message sent to the network, in addition to information on the activation / deactivation of the tethered device support function, the terminal can also send information to the network indicating that it already has the relevant QoS rules and can apply them.

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

[0361] Figure 12 illustrates the SMF procedure for the disclosure of this specification.

[0362] 1. The SMF (Session Management Function) can receive a NAS (Non-Access-Stratum) message related to a PDU (Protocol Data Unit) session for the UE from the UE (User Equipment).

[0363] The above UE may have the capability to support tethering services using tethered devices.

[0364] Before the SMF receives the NAS message, first status information indicating the activation status of the support function of the UE may be stored in the SMF.

[0365] The above NAS message may include second status information indicating an activation status of the above support function of the UE.

[0366] 2. The first state information and the second state information

[0367] Based on other factors, the SMF may determine that the activation state of the UE has changed.

[0368] 3. Based on the above decision, the SMF may request the Policy Control Function (PCF) to update the Policy and Charging Control (PCC) rule.

[0369] The above request may include the second activation status information.

[0370] 4. Based on the above request, the SMF can receive updated PCC rules from the PCF.

[0371] Based on the above updated PCC rules, the SMF can generate changed QoS (Quality of Service) rules.

[0372] The above SMF can transmit the changed QoS rule to the UE.

[0373] Before the SMF receives the NAS message, the SMF may receive an establishment request for the PDU session from the UE.

[0374] The above establishment request may include information about the above support capabilities of the UE.

[0375] The above establishment request may include the first state information.

[0376] Based on the above establishment request, the SMF can obtain subscriber information from UDM (Unified Data Management).

[0377] Based on the above subscriber information, the SMF may decide to allow the tethering service to the UE.

[0378] Based on the above SMF's decision to allow the above tethering service, the SMF can receive a PCC rule from the PCF.

[0379] Based on the above PCC rules, SMF can determine QoS rules.

[0380] The above SMF may send an establishment acknowledgment for the PDU session to the above UE.

[0381] The above establishment approval may include the above QoS rules.

[0382] The above subscriber information may include information that allows the tethering service for the DNN (Data Network Name) or S-NSSAI (Single-Network Slice Selection Assistance Information) related to the PDU session.

[0383] The above subscriber information may include information that allows the tethering service for the UE.

[0384] The above NAS message may be a modification request message for the above PDU session.

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

[0386] Figure 13 illustrates the UE's procedure for disclosure of this specification.

[0387] 1. A UE (User Equipment) can send a request to a SMF (Session Management Function) to establish a PDU (Protocol Data Unit) session for the UE.

[0388] The above UE may have the capability to support tethering services using tethered devices.

[0389] The above establishment request may include the first state information.

[0390] 2. Based on the establishment request, the UE can receive establishment approval for the PDU session from the SMF.

[0391] The above establishment approval may include Quality of Service (QoS) rules.

[0392] 3. Based on the change of the activation status of the UE from the first state information to the second state information, the UE can transmit a NAS (Non-Access-Stratum) message related to the PDU session to the SMF.

[0393] The above NAS message may include second status information indicating an activation status of the above support function of the UE.

[0394] 4. Based on the difference between the first state information and the second state information, the UE can receive a changed QoS rule from the SMF.

[0395] The above establishment request may include information about the above support capabilities of the UE.

[0396] The above NAS message may be a modification request message for the above PDU session.

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

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

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

[0400] The operations performed by the processor may include: receiving, by the SMF, a NAS message related to a PDU session for the UE from the UE; wherein the UE has a support function for a tethering service using a tethered device, and before the SMF receives the NAS message, first state information indicating an activation state of the support function of the UE is stored in the SMF, the NAS message includes second state information indicating an activation state of the support function of the UE, and based on a difference between the first state information and the second state information, the SMF determines that the activation state of the UE has changed; based on the determination, the SMF requests the PCF to update a PCC rule; the request includes the second activation state information, and based on the request, the SMF receives an updated PCC rule from the PCF.

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

[0402] The operations performed by the processor may include: receiving, by the SMF, a NAS message related to a PDU session for the UE from the UE; wherein the UE has a support function for a tethering service using a tethered device, and before the SMF receives the NAS message, first state information indicating an activation state of the support function of the UE is stored in the SMF, the NAS message includes second state information indicating an activation state of the support function of the UE, and based on a difference between the first state information and the second state information, the SMF determines that the activation state of the UE has changed; based on the determination, the SMF requests the PCF to update a PCC rule; the request includes the second activation state information, and based on the request, the SMF receives an updated PCC rule from the PCF.

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

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

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

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

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

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

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

[0410] The one or more stored commands may include: receiving, by an SMF, an NAS message from a UE related to a PDU session for the UE; wherein the UE has a support function for a tethering service using a tethered device, and before the SMF receives the NAS message, first state information indicating an activation state of the support function of the UE is stored in the SMF, the NAS message including second state information indicating an activation state of the support function of the UE, and based on a difference between the first state information and the second state information, determining, by the SMF, that an activation state of the UE has changed; based on the determination, requesting, by the SMF, a PCF for an update of a PCC rule; the request including the second activation state information, and based on the request, receiving, by the SMF, an updated PCC rule from the PCF.

[0411] This specification may have various effects.

[0412] For example, depending on whether the tethered device support function is enabled, appropriate QoS rules can be effectively provided to the terminal.

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

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

Claims

1. A step in which SMF (Session Management Function) receives a NAS (Non-Access-Stratum) message related to a PDU (Protocol Data Unit) session for the UE from UE (User Equipment); The above UE has the capability to support tethering services using tethered devices, Before the SMF receives the NAS message, first status information indicating the activation status of the support function of the UE is stored in the SMF, The NAS message includes second status information indicating the activation status of the support function of the UE, A step in which the SMF determines that the activation state of the UE has changed based on the difference between the first state information and the second state information; Based on the above decision, the SMF requests the PCF (Policy Control Function) to update the PCC (Policy and Charging Control) rule; The above request includes the second activation status information, A method comprising a step of the SMF receiving updated PCC rules from the PCF based on the request.

2. In paragraph 1, A step of generating a changed QoS (Quality of Service) rule based on the above updated PCC rule; A method further comprising the step of the SMF transmitting the changed QoS rule to the UE.

3. In paragraph 1 or 2, The SMF further comprises a step of receiving an establishment request for the PDU session from the UE before the SMF receives the NAS message, The above establishment request includes information about the above support function of the UE, A method wherein the above establishment request includes the first state information.

4. In paragraph 3, Based on the above establishment request, the step of the SMF obtaining subscriber information from UDM (Unified Data Management); A step in which the SMF determines to allow the tethering service to the UE based on the subscriber information; A step in which the SMF receives a PCC rule from the PCF based on the SMF's decision to allow the tethering service; A step in which the SMF determines QoS rules based on the above PCC rules; The SMF further comprises a step of transmitting an establishment acknowledgment for the PDU session to the UE, The above establishment approval method includes the above QoS rules.

5. In paragraph 4, A method in which the subscriber information includes information that allows the tethering service for the DNN (Data Network Name) or S-NSSAI (Single-Network Slice Selection Assistance Information) related to the PDU session.

6. In paragraph 4, A method wherein the subscriber information includes information that allows the tethering service for the UE.

7. In any one of paragraphs 1 to 6, The above NAS message is a modification request message for the above PDU session.

8. As a method, A step in which a UE (User Equipment) transmits a request for establishing a PDU (Protocol Data Unit) session for the UE to a SMF (Session Management Function); The above UE has the capability to support tethering services using tethered devices, The above establishment request includes the first state information, Based on the establishment request, the UE receives an establishment approval for the PDU session from the SMF; The above establishment approval includes QoS (Quality of Service) rules, A step of transmitting a NAS (Non-Access-Stratum) message related to the PDU session to the SMF by the UE based on the activation status of the UE being changed from the first state information to the second state information; The NAS message includes second status information indicating the activation status of the support function of the UE, A method comprising a step of the UE receiving a changed QoS rule from the SMF based on the difference between the first state information and the second state information.

9. In paragraph 8, A method wherein the above establishment request includes information about the above support function of the UE.

10. In paragraph 8 or 9, The above NAS message is a modification request message for the above PDU session.

11. As a SMF (Network Function), At least one transmitter and receiver; Contains at least one processor, The operation performed by the at least one processor is an SMF according to any one of claims 1 to 7.

12. As a UE (User Equipment), 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 8 to 10.

13. 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 at least one processor is a method according to any one of claims 8 to 10.

14. 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 a method according to any one of claims 8 to 10.

Images