Method for managing specific traffic

A unified framework for wireless communication systems addresses diverse traffic types and future spectrum challenges, enhancing service quality and capacity in 5G and beyond by supporting multiple access technologies and advanced signal processing.

WO2026235493A1PCT designated stage Publication Date: 2026-11-12LG ELECTRONICS INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/KR2026/096671
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-08
Filing Date
2026-05-07
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

Existing wireless communication technologies face challenges in efficiently managing diverse traffic types and scenarios, such as eMBB, mMTC, and URLLC, while ensuring compatibility with future spectrum bands up to 100 GHz and meeting the requirements of 5G and beyond.

Method used

Implementing a unified framework for wireless communication systems that supports multiple access technologies, including CDMA, FDMA, TDMA, OFDMA, and SC-FDMA, with advanced signal processing and resource allocation methods to manage traffic segmentation and control across various deployment scenarios.

Benefits of technology

Enables efficient management of diverse traffic types and scenarios, ensuring compatibility with future spectrum bands, and enhancing service quality, availability, and system capacity in 5G and beyond.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure KR2026096671_12112026_PF_FP_ABST
    Figure KR2026096671_12112026_PF_FP_ABST
Patent Text Reader

Abstract

A disclosure of the present specification provides a method. In the method: management and control of subdivided traffic are performed on the basis of information capable of distinguishing traffic; a system function and procedure in which AI-related data transmitted through a user plane can be distinguished / recognized and controlled from user service data are proposed; and an operation of subdividing, managing, and controlling traffic related to a specific operation (AI operation, model training) is performed.
Need to check novelty before this filing date? Find Prior Art

Description

Methods for managing specific traffic

[0001] This specification relates to mobile communication.

[0002] 3GPP (3rd generation partnership project) LTE (long-term evolution) is a technology designed to enable high-speed packet communication. Many methods have been proposed to achieve LTE goals, such as reducing costs for users and operators, improving service quality, expanding coverage, and increasing system capacity. As high-level requirements, 3GPP LTE demands reduced cost per bit, improved service availability, flexible use of frequency bands, a simple structure, open interfaces, and appropriate power consumption of terminals.

[0003] Work has begun at the ITU (International Telecommunication Union) and 3GPP to develop 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, satisfying both urgent market demands and the longer-term requirements presented by the ITU-R (ITU Radio Communication Sector) IMT (International Mobile Telecommunications)-2020 process. Furthermore, NR must be able to utilize any spectrum band up to at least 100 GHz so that it can be used for wireless communication even in the distant future.

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

[0005] Based on information that can distinguish traffic, segmented traffic management and control are performed.

[0006] FIG. 1 shows an example of a communication system to which the implementation of the present specification is applied.

[0007] FIG. 2 shows an example of a wireless device to which the implementation of the present specification applies.

[0008] FIG. 3 shows an example of a UE to which the implementation of the present specification applies.

[0009] Figure 4 is a structural diagram of a next-generation mobile communication network.

[0010] FIG. 5 shows an example of a 5G system structure to which the implementation of the present specification is applied.

[0011] FIGS. 6 and FIGS. 7 illustrate examples of PDU session establishment procedures to which the implementation of the present specification applies.

[0012] FIG. 8 illustrates an example of the procedure for the disclosure of the present specification.

[0013] FIG. 9 illustrates the procedure of a session-related NF for the disclosure of the present specification.

[0014] FIG. 10 illustrates the procedure of the UE for the disclosure of the present specification.

[0015] The following techniques, devices, and systems may 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 may be implemented through wireless technologies such as universal terrestrial radio access (UTRA) or CDMA2000. TDMA may be implemented through 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 through 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) using E-UTRA.3GPP LTE uses OFDMA in the downlink (DL) and SC-FDMA in the uplink (UL). Evolutions of 3GPP LTE include LTE-A (advanced), LTE-A Pro, and / or 5G NR (new radio).

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

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

[0018] In this specification, "A or B" may mean "only A," "only B," or "both A and B." Alternatively, in this specification, "A or B" may be interpreted as "A and / or B." For example, in this specification, "A, B or C" may mean "only A," "only B," "only C," or "any combination of A, B and C."

[0019] A slash ( / ) or a comma used in this specification may mean "and / or." For example, "A / B" may mean "A and / or B." Accordingly, "A / B" may mean "only A," "only B," or "both A and B." For example, "A, B, C" may mean "A, B or C."

[0020] 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 as synonymous with "at least one of A and B."

[0021] Additionally, in this specification, "at least one of A, B and C" may mean "only A," "only B," "only C," or "any combination of A, B and C." Furthermore, "at least one of A, B or C" or "at least one of A, B and / or C" may mean "at least one of A, B and C."

[0022] Additionally, parentheses used in this specification 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."

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

[0024] Although not limited thereto, the various descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification may be applied to various fields where wireless communication and / or connectivity between devices (e.g., 5G) is required.

[0025] The present specification will be described in more detail below with reference to the drawings. In the following drawings and / or description, the same reference numerals may refer to the same or corresponding hardware blocks, software blocks, and / or function blocks unless otherwise indicated.

[0026] FIG. 1 shows an example of a communication system to which the implementation of the present specification is applied.

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

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

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

[0030] The base station (200) and the network (300) can be implemented as wireless devices, and a specific wireless device can operate as a base station / network node in relation to another wireless device.

[0031] Wireless devices (100a to 100f) represent devices that perform communication using radio access technology (RAT) (e.g., 5G NR or LTE) and may also be referred to as communication / wireless / 5G devices. 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 with wireless communication capabilities, autonomous vehicles, and vehicles capable of performing communication between vehicles. 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 head-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., smartwatches 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.

[0032] 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 PDA (personal digital assistant), a PMP (portable multimedia player), a navigation system, a slate PC, a tablet PC, an ultrabook, a vehicle, a vehicle with autonomous driving capabilities, a connected car, a UAV, an AI module, a robot, an AR device, a VR device, an MR device, a hologram device, a public safety device, an MTC device, an IoT device, a medical device, a fintech device (or financial device), a security device, a weather / environment device, a 5G service-related device, or a device related to the Fourth Industrial Revolution.

[0033] For example, a UAV can be an aircraft that is not on board and is navigated by radio control signals.

[0034] 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 a 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 a real world. For example, a holographic device may include a device for implementing a 360-degree stereoscopic image by recording and playing back stereoscopic information using the phenomenon of light interference that occurs when two laser lights called holograms meet.

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

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

[0037] 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 to diagnose, treat, alleviate, or correct 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, a (in vitro) diagnostic device, a hearing aid, or a surgical device.

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

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

[0040] For example, a weather / environment device may include a device for monitoring or predicting the weather / environment.

[0041] Wireless devices (100a to 100f) can be connected to a network (300) through a base station (200). AI technology may be applied to the wireless devices (100a to 100f), and the wireless devices (100a to 100f) can be connected to an AI server (400) through 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) may communicate with each other through the base station (200) / network (300), but they may 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., V2V (vehicle-to-vehicle) / V2X (vehicle-to-everything) communication). Also, IoT devices (e.g., sensors) can communicate directly with other IoT devices (e.g., sensors) or other wireless devices (100a to 100f).

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

[0043] AI refers to the field of researching artificial intelligence or the methodologies to create it, while machine learning refers to the field of researching methodologies to define and solve various problems within the realm of artificial intelligence. Machine learning is also defined as an algorithm that improves performance on a task through continuous experience.

[0044] A robot can refer to a machine that automatically processes or operates given tasks based on its own capabilities. In particular, a robot equipped with the ability to perceive its environment, make independent judgments, and perform actions can be called an intelligent robot. Robots can be classified into industrial, medical, domestic, and military types depending on their purpose or field of use. Robots are equipped with drive units, including actuators or motors, to perform various physical movements, such as moving robot joints. Additionally, mobile robots include wheels, brakes, propellers, etc., in their drive units, enabling them to drive on the ground or fly in the air.

[0045] Autonomous driving refers to technology that drives itself, and an autonomous vehicle refers to a vehicle that drives without user intervention or with minimal user intervention. For example, autonomous driving can include technologies such as maintaining the driving lane, automatically adjusting speed like adaptive cruise control, driving automatically along a predetermined route, and automatically setting a route and driving once a destination is set. The term "vehicle" encompasses vehicles equipped solely with internal combustion engines, hybrid vehicles equipped with both internal combustion engines and electric motors, and electric vehicles equipped solely with electric motors; it can include not only automobiles but also trains and motorcycles. An autonomous vehicle can be viewed as a robot equipped with autonomous driving capabilities.

[0046] Augmented Reality is a collective term for VR, AR, and MR. VR technology provides real-world objects or backgrounds solely as CG images, AR technology provides virtual CG images superimposed on 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 technology in that it displays real-world and virtual objects together. However, there is a difference in that while virtual objects in AR technology are used to complement real-world objects, virtual and real objects in MR technology are used as equal entities.

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

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

[0049] Frequency Range Definition Frequency Range Subcarrier Spacing FR1 450 MHz - 6000 MHz 15, 30, 60 kHz FR2 24 250 MHz - 52600 MHz 60, 120, 240 kHz

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

[0051] Frequency Range Definition Frequency Range Subcarrier Spacing FR1 4 10 MHz - 7 125 MHz 15, 30, 60 kHz FR2 24 250 MHz - 5 2600 MHz 60, 120, 240 kHz

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

[0053] FIG. 2 shows an example of a wireless device to which the implementation of the present specification applies.

[0054] 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 example / service. For example, {the first wireless device (100) and the second wireless device (200)} may correspond to at least one of {wireless devices (100a–100f) and base station (200)}, {wireless devices (100a–100f) and wireless devices (100a–100f)} and / or {base station (200) and base station (200)} of FIG. 1. The first wireless device (100) and / or the second wireless device (200) may be composed of various components, devices / parts and / or modules.

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

[0056] 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 generally, the memory (104) may be placed outside the processing chip (101).

[0057] The processor (102) can control the memory (104) and / or the transceiver (106) and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed herein. For example, the processor (102) may process information within the memory (104) to generate a first information / signal and transmit a wireless signal containing the first information / signal through the transceiver (106). The processor (102) may receive a wireless signal containing a second information / signal through the transceiver (106) and process the second information / signal to store the obtained information in the memory (104).

[0058] Memory (104) may be connected to the processor (102) so as to be operable. Memory (104) may store various types of information and / or instructions. Memory (104) may store firmware and / or software code (105) that implements code, instructions, and / or a set of instructions that perform the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification when executed by the processor (102). For example, firmware and / or software code (105) may implement instructions that perform the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification when executed by the processor (102). For example, firmware and / or software code (105) may control the processor (102) to perform one or more protocols. For example, firmware and / or software code (105) may control the processor (102) to perform one or more wireless interface protocol layers.

[0059] 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 a wireless signal through one or more antennas (108). Each transceiver (106) may include a transmitter and / or receiver. The transceiver (106) may be interchangeably used with an RF (radio frequency) unit. In this specification, the first wireless device (100) may represent a communication modem / circuit / chip.

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

[0061] 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 placed outside the processing chip (201).

[0062] The processor (202) can control the memory (204) and / or the transceiver (206) and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed herein. For example, the processor (202) may process information within the memory (204) to generate a third information / signal and transmit a wireless signal containing the third information / signal through the transceiver (206). The processor (202) may receive a wireless signal containing a fourth information / signal through the transceiver (206) and process the fourth information / signal to store the obtained information in the memory (204).

[0063] Memory (204) may be connected to the processor (202) so as to be operable. Memory (204) may store various types of information and / or instructions. Memory (204) may store firmware and / or software code (205) that implements instruction code, instructions, and / or sets of instructions that perform descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification when executed by the processor (202). For example, firmware and / or software code (205) may implement instructions that perform descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification when executed by the processor (202). For example, firmware and / or software code (205) may control the processor (202) to perform one or more protocols. For example, firmware and / or software code (205) may control the processor (202) to perform one or more wireless interface protocol layers.

[0064] 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 transmit and / or receive a wireless signal through one or more antennas (208). Each transceiver (206) may include a transmitter and / or receiver. The transceiver (206) may be interchangeably used with an RF unit. In this specification, the second wireless device (200) may represent a communication modem / circuit / chip.

[0065] 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 PHY (physical) layer, a MAC (media access control) layer, a RLC (radio link control) layer, a PDCP (packet data convergence protocol) layer, a RRC (radio resource control) layer, and an SDAP (service data adaptation protocol) layer). One or more processors (102, 202) may generate one or more PDUs (protocol data units), one or more SDUs (service data units), messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification. One or more processors (102, 202) may generate a signal (e.g., baseband signal) including a PDU, SDU, message, control information, data, or information according to the description, function, procedure, proposal, method, and / or operation flowchart disclosed in this specification and provide it to one or more transceivers (106, 206). One or more processors (102, 202) may receive a signal (e.g., baseband signal) from one or more transceivers (106, 206) and may obtain a PDU, SDU, message, control information, data, or information according to the description, function, procedure, proposal, method, and / or operation flowchart disclosed in this specification.

[0066] One or more processors (102, 202) may be referred to as a controller, a microcontroller, a microprocessor, and / or a microcomputer. 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 one or more processors (102, 202). For example, one or more processors (102, 202) may be composed of a set of communication control processors, application processors (APs), electronic control units (ECUs), central processing units (CPUs), graphic processing units (GPUs), and memory control processors.

[0067] One or more memories (104, 204) may be connected to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, codes, instructions, and / or commands. One or more memories (104, 204) may consist of random access memory (RAM), dynamic RAM (DRAM), read-only memory (ROM), erasable programmable ROM (EPROM), flash memory, volatile memory, non-volatile memory, hard drives, registers, cache memory, computer read storage media, and / or combinations thereof. One or more memories (104, 204) may be located inside and / or outside of one or more processors (102, 202). Additionally, one or more memories (104, 204) may be connected to one or more processors (102, 202) through various technologies such as wired or wireless connections.

[0068] One or more transceivers (106, 206) may transmit user data, control information, wireless signals / channels, etc., as described in the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification to one or more other devices. One or more transceivers (106, 206) may receive user data, control information, wireless signals / channels, etc., as described in the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification from one or more other devices. For example, one or more transceivers (106, 206) may be connected to one or more processors (102, 202) and may transmit and receive wireless signals. For example, one or more processors (102, 202) may control one or more transceivers (106, 206) to transmit user data, control information, wireless signals, etc., to one or more other devices. Additionally, one or more processors (102, 202) can control one or more transceivers (106, 206) to receive user data, control information, wireless signals, etc. from one or more other devices.

[0069] One or more transceivers (106, 206) may be connected to one or more antennas (108, 208). Additionally and / or generally, 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 operation flowcharts disclosed herein through one or more antennas (108, 208). In this specification, one or more antennas (108, 208) may be a plurality of physical antennas or a plurality of logical antennas (e.g., antenna ports).

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

[0071] Although not illustrated in FIG. 2, the wireless device (100, 200) may 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., audio I / O port, video I / O port), a driving unit, and a computing unit. The additional components (140) may be connected to one or more processors (102, 202) through various technologies, such as wired or wireless connections.

[0072] In an implementation of this specification, the UE may operate as a transmitting device in the uplink (UL; uplink) and as a receiving device in the downlink (DL; downlink). In an implementation of this specification, the base station may operate as a receiving device in the UL and as a transmitting device in the DL. For technical convenience, it is generally assumed that the first wireless device (100) operates as a UE and the second wireless device (200) operates as a base station. For example, a processor (102) connected to, mounted on, or released to the first wireless device (100) may be configured to perform UE operations according to an implementation of this specification or to control a transceiver (106) to perform UE operations according to an implementation of this specification. A processor (202) connected to, mounted on, or released to the second wireless device (200) may be configured to perform base station operations according to an implementation of this specification or to control a transceiver (206) to perform base station operations according to an implementation of this specification.

[0073] In this specification, the base station may be referred to as Node B, eNode B, or gNB.

[0074] FIG. 3 shows an example of a UE to which the implementation of the present specification applies.

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

[0076] The UE (100) includes a processor (102), memory (104), 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).

[0077] The processor (102) may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operation 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 operation flowcharts disclosed herein. Layers of a wireless 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 processor, EXYNOS made by Samsung® TM Series processors, A Series processors made by Apple®, HELIO made by MediaTek® TM Series processors, ATOM made by Intel® TM It can be found in series processors or corresponding next-generation processors.

[0078] Memory (104) is coupled to the processor (102) so as to be operable and stores various information for operating the processor (102). Memory (104) may include ROM, RAM, flash memory, memory card, storage medium and / or other storage device. When the implementation is implemented in software, the technology described herein may be implemented using modules (e.g., procedures, functions, etc.) that perform the descriptions, functions, procedures, proposals, methods and / or operation flowcharts disclosed herein. Modules may be stored in memory (104) and executed by the processor (102). Memory (104) may be implemented within the processor (102) or outside the processor (102), in which case it may be communicatively coupled to the processor (102) through various methods known in the technology.

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

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

[0081] The display (143) outputs the result 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).

[0082] A SIM card (145) is an integrated circuit for securely storing an International Mobile Subscriber Identity (IMSI) and associated keys, and is used to identify and authenticate a subscriber in a mobile device such as a mobile phone or computer. Additionally, contact information can be stored on many SIM cards.

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

[0084] Figure 4 is a structural diagram of a next-generation mobile communication network.

[0085] 5GC (5G Core) may include various components, and FIG. 5 includes some of them, such as 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).

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

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

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

[0089] The illustrated AMF (410) can manage access and mobility in a 5G system. The AMF (410) can perform the function of managing Non-Access Stratum (NAS) security. The AMF (410) can perform the function of handling mobility in an idle state.

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

[0091] 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 the data path between the gNB (20) and the SMF (420). Additionally, 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 the function of handling PDUs. For mobility within the NG-RAN (Next Generation Radio Access Network defined in 3GPP Release-15 or later), packets can be routed through the UPF. Additionally, the UPF (440) may also function as an anchor point for mobility with other 3GPP networks (RANs defined prior to 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.

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

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

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

[0095] The illustrated SMF (420) can perform the function of assigning the IP (Internet Protocol) address of the UE. Also, the SMF (420) can control the PDU (protocol data unit) session.

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

[0097] Fifth-generation mobile communication supports multiple numerologies or subcarrier spacings (SCS) to support various 5G services. For example, when the SCS is 15 kHz, it supports a wide area in traditional cellular bands; when the SCS is 30 kHz / 60 kHz, it supports dense-urban environments, lower latency, and wider carrier bandwidth; and when the SCS is 60 kHz or higher, it supports a bandwidth greater than 24.25 GHz to overcome phase noise.

[0098] FIG. 5 shows an example of a 5G system structure to which the implementation of the present specification is applied.

[0099] The 5G system (5GS) structure consists of the following network functions (NF).

[0100] - AUSF (Authentication Server Function)

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

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

[0103] - USDF (Unstructured Data Storage Function)

[0104] - NEF (Network Exposure Function)

[0105] - I-NEF (Intermediate NEF)

[0106] - NRF (Network Repository Function)

[0107] - NSSF (Network Slice Selection Function)

[0108] - PCF (Policy Control Function)

[0109] - SMF (Session Management Function)

[0110] - UDM (Unified Data Management)

[0111] - UDR (Unified Data Repository)

[0112] - UPF (User Plane Function)

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

[0114] - AF (Application Function)

[0115] - UE (User Equipment)

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

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

[0118] - NWDAF (Network Data Analytics Function)

[0119] - CHF (CHarging Function)

[0120] In addition, the following network functions may be considered.

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

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

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

[0124] Figure 5 shows the 5G system structure in a non-roaming case using a reference point representation showing how various network functions interact with each other.

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

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

[0127] The 5G system structure includes the following reference points.

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

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

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

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

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

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

[0134] The following reference points show the interactions that exist between the NF services of NF.

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

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

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

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

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

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

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

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

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

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

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

[0146] In some cases, two NFs may need to be connected to each other to service the UE.

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

[0148] The procedure for establishing a PDU session is described. Refer to Section 4.3.2 of 3GPP TS 23.502 V16.3.0 (2019-12).

[0149] FIGS. 6 and FIGS. 7 illustrate examples of PDU session establishment procedures to which the implementation of the present specification applies.

[0150] PDU session establishment may fall under the following:

[0151] - Procedure for establishing a PDU session initiated by the UE

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

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

[0154] - Procedure for establishing a PDU session triggered by the network

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

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

[0157] In the procedure shown in Figures 6 and 7, it is assumed that the AMF has already retrieved user subscription data from the UDM, unless the UE is urgently registered, since the UE is already registered with the AMF.

[0158] First, the procedure of Fig. 6 will be explained.

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

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

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

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

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

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

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

[0166] If the request type indicates an "existing PDU session" that refers to an existing PDU session moving between a 3GPP connection and a non-3GPP connection, and the serving PLMN S-NSSAI of the PDU session exists in the allowed NSSAI of the target connection type, the PDU session establishment procedure may be performed in the following cases.

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

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

[0169] Otherwise, the AMF rejects the request to establish a PDU session with an appropriate reason for rejection.

[0170] AMF rejects requests from urgently registered UEs where the request type does not indicate "urgent request" or "existing urgent PDU session".

[0171] (3) Step 3: If the AMF is not associated with an SMF for a PDU session ID provided by the UE (e.g., when the request type indicates "initial request"), the AMF calls the Create SMContext request procedure (e.g., Nsmf_PDUSession_CreateSMContext Request). If the AMF is already associated with an SMF for a PDU session ID provided by the UE (e.g., when the request type indicates "existing PDU session"), the AMF calls the Update SMContext request procedure (e.g., Nsmf_PDUSession_UpdateSMContext Request).

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

[0173] The AMF ID is the UE's GUAMI and uniquely identifies the AMF serving the UE. The AMF transmits the PDU Session ID along with an N1 SM container containing the PDU session establishment request message received from the UE. The generic public subscription identifier (GPSI) is included if available in the AMF.

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

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

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

[0177] (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 in accordance with the request received in Step 3.

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

[0179] If the SMF decides not to accept the establishment of a PDU session, the SMF rejects the UE request via a NAS SM signal containing 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 that the SMF proceeds to step 20 below and the PDU session establishment procedure is stopped.

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

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

[0182] (7b) Step 7b: SMF can establish an SM policy association with PCF and obtain a basic PCC rule for the PDU session by performing the SM policy association establishment procedure.

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

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

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

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

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

[0188] The N1N2 message delivery message may include N2 SM information. The N2 SM information carries the following information that the AMF will transmit to the (R)AN.

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

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

[0191] - PDU Session ID: Indicates to the UE the association between the RAN resource and the PDU session for the UE;

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

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

[0194] - Maximum data rate for UE integrity protection received in PDU session establishment request message: When integrity protection is indicated as "Preferred" or "Required" in user plane security enforcement information

[0195] - RSN (redundancy sequence number) parameter

[0196] The N1N2 message delivery message may include an N1 SM container. The N1 SM container includes a PDU session establishment acceptance message that the AMF will provide to the UE. The PDU session establishment acceptance message includes an S-NSSAI from an allowed NSASI. In the case of an LBO roaming scenario, the PDU session establishment acceptance message includes an S-NSSAI from an allowed NSSAI for the VPLMN, and also includes the corresponding S-NSSAI for the HPLMN from the mapping of the allowed NSSAI received by the SMF in step 3.

[0197] If necessary for QoS flows related to QoS rules and QoS profiles, multiple QoS rules, QoS flow levels, and QoS parameters may be included in the PDU session establishment acceptance message and N2 SM information within the N1 SM container.

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

[0199] (12) Step 12: The AMF sends a NAS message containing a PDU session ID destined for the UE, a message accepting the establishment of a PDU session, and N2 SM information received from the SMF to (R)AN within the N2 PDU session request message.

[0200] (13) Step 13: (R)AN can perform AN-specific signal exchanges with the UE regarding information received from the SMF. For example, in the case of NG-RAN, it can perform RRC connection reconfiguration with the UE to set up necessary NG-RAN resources in relation to the QoS rules for the PDU session request received by the UE in Step 12.

[0201] (R)AN forwards the NAS message (PDU session ID, N1 SM container (PDU session establishment acceptance message)) received in step 12 to the UE. (R)AN provides the NAS message to the UE only if the AN-specific signal exchange with the UE includes the addition of (R)AN resources related to the received N2 command.

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

[0203] Now, the procedure of Fig. 7 following the procedure of Fig. 6 is explained.

[0204] (14) Step 14: (R)AN sends an N2 PDU session response message to AMF. The N2 PDU session response message may include a PDU session ID, cause, N2 SM information (PDU session ID, AN tunnel information, list of accepted / rejected QFIs, user plane enforcement policy notifications), etc.

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

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

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

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

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

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

[0211] After this step, AMF delivers the relevant events subscribed to by SMF.

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

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

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

[0215] (21) Step 21: If the establishment of a PDU session fails after Step 4, and the SMF no longer processes the UE's PDU session, the SMF may unsubscribe from the modification of the session management subscription data.

[0216] The amount of data required for AI (Artificial Intelligence) / ML (Machine Learning) operations and services can be vast. Therefore, there has traditionally been discussion about exchanging necessary information between terminal networks via the user plane.

[0217] Similar to sensing services and XR services, traffic characteristics can change dynamically. Therefore, there is a need to manage this effectively.

[0218] Targeting zero-touch configuration / operation environments where network automation is extended, this document addresses the fact that the volume of data traffic collected by UEs and networks to perform AI-related operations, such as AIML model training, model performance monitoring, and model transfer in mobile communication systems, can be very large. Furthermore, when such traffic is transmitted through the user plane, it is indistinguishable from or recognized as user service traffic data in the prior art.

[0219] In this specification, system functions and procedures may be proposed that allow AI-related data transmitted through the user plane to be distinguished / recognized and controlled from user service data.

[0220] Through this, effective wired and wireless network resource allocation and system control are possible, and it can be utilized for applying billing policies, etc.

[0221] In this specification, methods for solving the aforementioned problems may be proposed.

[0222] The contents / methods described below may be performed / used selectively, in combination, or complementarily. One or more of the contents / methods described below may be implemented in combination.

[0223] The method proposed in this specification is described based on the structure, procedures, messages, etc. of a 5G mobile communication system. However, the method proposed in this specification is not limited to a 5G mobile communication system and can be extended to an evolved form of a 6G mobile communication system.

[0224] In this specification, information capable of distinguishing traffic (or information used to distinguish traffic) may be information representing specific traffic (e.g., traffic segmented from AI / sensing / XR-related operations).

[0225] In this specification, a method for managing and controlling traffic related to specific operations (e.g., AI operations, model training) by segmenting it may be proposed.

[0226] Although AI data traffic is described as an example in this specification, it can be extended to specific data required for various types of data (e.g., sensing data and XR / immersive services, etc.) that can be transmitted between a terminal and a network.

[0227] I. User consent check process

[0228] According to conventional technology, in order to collect AI-related data from a UE, verification of user consent stored in subscriber information is required. The said subscriber information may be information about the UE's user.

[0229] NWDAF may subscribe to or unsubscribe from NF in order to receive data collection notifications regarding relevant events. In this regard, user consent may be required for the collection of UE-related data and the use of collected data, subject to local regulations. User consent may be defined according to specific purposes, such as analytics or model training. NWDAF may determine whether user consent has been obtained based on the purpose of data collection and use.

[0230] Regarding the granularity of user consent, Table 3 is defined in the current standard.

[0231] -Enumeration value-Description"ANALYTICS"User consent for analytics."MODEL_TRAINING"User consent for model training."NW_CAP_EXPOSURE"User consent for network capability exposure."EDGEAPP_UE_LOCATION"User consent for the manipulation of UE information for the purpose of UE Location retrieval by the EDGEAPP EAS entity.

[0232] User consent for model training is stipulated.

[0233] There is a need for user consent to be granularized so that AI-related data can be recognized, managed, and controlled.

[0234] For example, traffic related to specific actions (e.g., AI actions, model training) can be segmented. User consent for each segmented traffic related to specific actions (e.g., AI actions, model training) can be included in the subscriber information. For example, user consent for the first segmented traffic may exist in the subscriber information, but user consent for the second segmented traffic may not exist.

[0235] In addition to model training, user consent for various purposes can be defined and used.

[0236] For example, the granularity / unit of user consent may be used in combination of one or more of the following options:

[0237] - For analytics (conventional technology)

[0238] - For Model training (conventional technology)

[0239] - For model performance monitoring: For example, whether there is user consent for the collection / use of data to monitor model performance related to AI behavior.

[0240] - For Exposure (to Access Network or 3rd party): For example, whether there is user consent for exposure to the access network / third party regarding data collected / generated by AI operations.

[0241] - For Sensing contextual information generation: For example, whether there is user consent to the collection / use of data for the generation of sensing contextual information related to AI behavior.

[0242] - For Sensing performance monitoring: For example, whether there is user consent for the collection / use of data for monitoring sensing performance related to AI operations

[0243] - Etc.

[0244] For the collection and analysis of simple AI data / sensing data, the conventional "for analytics" may be used.

[0245] According to the prior art, when subscriber information of a UDM / UDR is updated, said subscriber information can be provisioned to other network nodes (e.g., AMF, SMF, NWDAF, etc.).

[0246] In this specification, a method may be proposed for transmitting subscriber information regarding user consent, segmented for various purposes, to network nodes and base stations.

[0247] In this regard, at least one of the following options may be used:

[0248] - A separate procedure for user consent provision may be defined between the UDM / UDR and network nodes. Alternatively, the conventional provisioning procedure for subscriber information may be applied.

[0249] - A separate procedure for user consent provisioning may be defined between the core network and the base station. Alternatively, the content of user consent may be transmitted to the base station during the initial setup process or update process (e.g., the process of updating information regarding the association and configuration) between the core network and the base station.

[0250] - Network nodes (e.g., AMF, SMF, NWDAF, etc.) may define and use service operations for user consent exposure. Based on this, network nodes may receive subscriber information containing user consent (or the user consent information itself) from UDM / UDR. The service operation may be an extension of conventional service operations. The service operation may be a separate service operation for specific user consent. Alternatively, the service operation may be a service operation that transmits all subscriber information.

[0251] - The base station may directly or indirectly transmit a subscription message (or a request message, if necessary) regarding a service operation (e.g., a service operation to receive subscriber information including user consent) to a network node (e.g., UDM / UDR) holding user consent information. Based on this, the base station may directly or indirectly receive update notifications (and / or updated information).

[0252] - The UDM / UDR may define and use service actions regarding the exposure of user consent directly. The base station may send a subscription message (or a request message if necessary) regarding the service action (e.g., a service action for receiving subscriber information containing user consent) to the UDM / UDR.

[0253] - If user consent is stored in the subscriber information, the base station may transmit a subscriber message (or a request message if necessary) regarding a service operation (service operation of the prior art) to the UDM / UDR.

[0254] - If user consent is stored separately, the base station may send a subscription message (or a request message if necessary) for a service operation (a newly defined service operation) to the UDM / UDR (or the network node where the user consent is stored).

[0255] II. Process of receiving information necessary for classifying AI-related traffic from AF

[0256] The AF can send a request message (e.g., AF request) to the core network.

[0257] The above request message may include information necessary to establish a session in the user plane.

[0258] The above request message may include information necessary to distinguish traffic for specific actions related to AI operations. The information necessary to distinguish traffic for specific actions related to AI operations is utilized as a filter factor, and traffic can be distinguished based thereon. The information (parameter) necessary to distinguish traffic for specific actions related to AI operations (hereinafter referred to as the traffic information of Section II) may include, for example, at least one of the following:

[0259] - DNN(s) and / or S-NSSAI(s)

[0260] - DNAI(s)

[0261] - Traffic description information

[0262] - QoS parameters for the purpose of data collection

[0263] QoS parameters for the purpose of model training

[0264] QoS parameter for the purpose of model performance monitoring

[0265] - IP address

[0266] - Port number

[0267] - Session number

[0268] - QFI number

[0269] - Others (etc.)

[0270] Through the traffic information of Section II described above, traffic related to AI operation (or model training) can be segmented. Therefore, based on the traffic information of Section II described above, the network / base station / terminal can control / manage the segmented traffic.

[0271] For example, the above request message may include information that traffic for a specific action related to AI operations (e.g., data collection, model training, model performance monitoring) uses a specific parameter (one of the traffic information in Section II).

[0272] For example, the above request message may include information that S-NSSAI#1 is used for AI-related traffic.

[0273] For example, the above request message may include traffic description information that 'IP address xx.xx.xx.xx' is used for traffic for AI model training purposes and / or QoS parameter information for model training purposes that must be satisfied.

[0274] For example, if a specific DNN and S-NSSAI are used when establishing a PDU session, data collected by the UE for AI-related operations can be transmitted through the said PDU session. Based on this, information regarding data transmission and reception per PDU session can be collected by UPF, etc. The collected information can be used for billing.

[0275] For example, if information is received to satisfy the user consent for granular purposes in Section I, and if information (parameters) necessary to distinguish AI-related traffic is received from the AF, the core network control node (e.g., SMF) may allocate a separate QFI at the time of PDU session establishment (or QoS flow allocation) to manage specific traffic (e.g., AI operation-related model training, AI operation-related model performance monitoring, etc.) as a separate QoS. Based on this, information regarding data transmission and reception by QoS may be collected by the UPF, etc. The collected information may be used for billing.

[0276] SMF can assign a QFI (QoS Flow ID) using at least one of the following:

[0277] - A specific range to distinguish from User service data traffic: The above specific range may represent one or more available QFI values. For example, QFI values ​​from 1 to 3 are used for User service data traffic, and QFI values ​​of 5 or higher are used for AI behavior-related model training traffic.

[0278] - Pre-configured range values: Pre-configured values ​​may be pre-set on network nodes. The said pre-configured values ​​may be used for traffic related to AI operations. For example, the pre-configured range values ​​may be one or more available QFI values. For example, QFI values ​​from 1 to 5 are used for specific AI operations (e.g., data collection, model training, model performance monitoring).

[0279] - Values ​​within a standardized range: For example, a specific value (e.g., QFI 5) may be defined in the standard as being used for specific AI-related actions (e.g., data collection, model training, model performance monitoring).

[0280] Based on information received from AF, PCF may generate and transmit a PCC (Policy and Charging Control) rule to SMF so that SMF can allocate QFI. For example, the PCC rule may include information necessary to distinguish the aforementioned traffic (e.g., information that a specific parameter is used for traffic related to AI operations), an allocable QFI range, and / or QoS requirements to be satisfied. For example, the PCC rule may include information that a QFI value between 10 and 15 is used for a specific AI operation-related operation (e.g., data collection, model training, model performance monitoring).

[0281] The above QFI ranges (e.g., QFI 10–15) may be used differentially by network nodes for controlling packet scheduling (and / or priority, etc.). Additionally, the above QFI ranges (e.g., QFI 10–15) may be used for billing records and control.

[0282] PCC rules may include charging rules intended for use in the user's billing policy. For example, PCC rules may limit the usage of traffic for specific AI-related operations (e.g., data collection, model training, model performance monitoring) to a maximum value. For example, PCC rules may include information that usage for traffic for specific AI-related operations (e.g., data collection, model training, model performance monitoring) is excluded from user billing.

[0283] The SMF can transmit the assigned QFI to the UPF. Based on this, the UPF can control and manage the transmission and reception information of the relevant data. For example, the UPF can perform the following actions:

[0284] - QoS parameter control

[0285] - Generate billing records for each PDU session

[0286] - Create billing records for each QFI

[0287] The SMF can transmit the assigned QFI to the terminal / base station. Based on this, the terminal / base station can control and manage the transmission and reception information of the relevant data. For example, the terminal / base station can perform the following actions:

[0288] - QoS parameter control

[0289] - Generate billing records for each PDU session

[0290] - Create billing records for each QFI

[0291] The contents of Section I and Section II can be combined and implemented.

[0292] For example, if there is user consent for specific traffic in Section I, the method of Section II for said specific traffic may be performed.

[0293] The following drawings are made to illustrate a specific example of the present specification. The names of specific devices or specific signals / messages / fields described in the drawings are presented as examples, and therefore the technical features of the present specification are not limited to the specific names used in the following drawings.

[0294] FIG. 8 illustrates an example of the procedure for the disclosure of the present specification.

[0295] The contents of Figs. 6 and 7 can be applied to the contents related to session establishment in Fig. 8.

[0296] 1) Step 1

[0297] The AF can send request messages (control requests based on segmented traffic classification) to the core network.

[0298] If the AF is located outside the operator network, the above request message may be transmitted via the NEF.

[0299] The above request message may include at least one of the following:

[0300] - i. Information capable of distinguishing granular traffic: Traffic information from Section II mentioned above (e.g., traffic for training AI behavior-related models: QFI 2

[0301] - ii. Information on QoS parameters for controlling the relevant traffic

[0302] For example, information capable of distinguishing the above-mentioned segmented traffic may include the following:

[0303] - Traffic for AI motion-related model training: QFI 2

[0304] - Traffic for AI operation-related model performance monitoring: QFI 3

[0305] For example, information regarding QoS parameters for controlling the above-mentioned traffic may include the following:

[0306] - Types of QoS parameters (e.g., transmission rate, latency) required for traffic for AI behavior-related model training and their corresponding values.

[0307] - Types of QoS parameters (e.g., transmission rate, latency) required for traffic to monitor the performance of AI operation-related models, and their corresponding values

[0308] The core network node receiving the above request message may be a PCF, UDM / UDR, or NEF.

[0309] 2) Step 2

[0310] Option 1 or Option 2 may be performed.

[0311] According to Option 1, the following actions can be performed:

[0312] - A request message from AF can be delivered to PCF. In this case, PCF can generate a PCC rule based on the request message. The PCC rule may be a policy intended to perform QoS control and monitoring for each granular traffic segment.

[0313] - According to the prior art procedure, the PCF can transmit PCC rules to the SMF. Based on this, the SMF can generate N4 rules and transmit them to the UPF. The N4 rules may include policies for controlling / monitoring granular traffic based on AF requests.

[0314] - According to the prior art procedure, the PCF can transmit PCC rules to the SMF. Based on this, the SMF can generate a QoS profile and transmit it to the base station. The QoS profile may include policies for controlling / monitoring granular traffic based on AF requests.

[0315] - According to the prior art procedure, the PCF can transmit PCC rules to the SMF. Based on this, the SMF can generate QoS rules and transmit them to the terminal. The QoS rules may include policies for controlling / monitoring granular traffic based on AF requests.

[0316] According to Option 2, the following actions can be performed:

[0317] - The AF's request message can be delivered to the UDM / UDR. In this case, based on the request message, the UDM / UDR can update / store subscriber information:

[0318] - By means of a conventional technology procedure, a UDM / UDR can transmit updated subscriber information to one or more network nodes (e.g., AMF, SMF, etc.).

[0319] - The above updated subscriber information may include information necessary for granular traffic control.

[0320] - The above-mentioned updated subscriber information may be transmitted to the base station and UPF. For example, network nodes (e.g., AMF, SMF, etc.) may transmit subscriber information to the base station and / or UPF.

[0321] Alternatively, a network node (e.g., AMF, SMF, etc.) may extract and process only the user consent-related matters from the updated subscriber information to determine specific information (e.g., allow traffic for PDU session number xx, allow traffic assigned to QFI xx, etc.). The network node (e.g., AMF, SMF, etc.) may transmit the specific information to the base station and / or UPF.

[0322] 3) Step 3

[0323] Apart from the transmission of subscriber information in option 2 of step 2, if necessary, the SMF may request subscriber information from the UDM / UDR and receive the information.

[0324] 4) Step 4

[0325] The terminal can send a request to establish a PDU session to the SMF.

[0326] The contents of Figures 6 and 7 can be applied to step 4.

[0327] 5) Step 5

[0328] Based on the terminal's request, subscriber information, PCC rules, etc., the SMF can determine whether to establish a PDU session.

[0329] At this time, the SMF can verify user consent information regarding subscriber information. According to an embodiment of the present specification, unlike the prior art, the SMF can perform a verification process for granular user consent (e.g., user consent for specific traffic).

[0330] For example, the SMF can verify subscriber information (through interaction with the UDM / UDR). Based on the subscriber information, the SMF can determine whether user consent exists for specific traffic (e.g., AI-related traffic). If user consent exists, the subsequent step can be performed.

[0331] If user consent is obtained, SMF may decide to perform management of specific traffic (e.g., AI-related traffic). Based on the above decision, SMF may perform management of said specific traffic (e.g., AI-related traffic). The management of said specific traffic may be, for example, as follows:

[0332] - QFI allocation in step 6

[0333] - Transmission of the N4 rule containing QoS parameters for the specific traffic in step 7 to the UPF

[0334] - Transmission to the terminal of the QoS rule including QoS parameters for the specific traffic mentioned above in step 9-1

[0335] - Transmission to the base station of the QoS profile including QoS parameters for the specific traffic mentioned above in step 9-2

[0336] - Generating a billing record for the specific traffic mentioned above in step 9-3)

[0337] 6) Step 6

[0338] SMF can decide to establish a PDU session.

[0339] In addition, the SMF can allocate QFIs for granular traffic and set QoS parameters for granular traffic (e.g., Parameter A is the type and value required for traffic for data collection of AI operations, and Parameter B is the type and value required for traffic for model performance monitoring of AI operations). This operation can be performed based on information based on an AF request. The allocation of QFIs for granular traffic and the setting of QoS parameters for granular traffic can be performed based on the confirmation in step 5 that there is user consent from the terminal for the traffic.

[0340] For example, the SMF can allocate a QFI for traffic related to AI operations and set QoS parameters. The corresponding QFI can be used to manage traffic related to AI operations.

[0341] For example, the assigned QFI and QoS parameters may be as follows:

[0342] - Traffic for AI operation data collection: QFI 1, maximum transmission speed 10Mbps~15Mbps, maximum latency 10msec

[0343] - Traffic for AI behavior model training: QFI 2, transmission speed 12Mbps~16Mbps

[0344] - Traffic for AI operation model performance monitoring: QFI 3, transmission speed 11Mbps~15Mbps

[0345] 7) Step 7

[0346] SMF can generate N4 rules and send them to UPF.

[0347] N4 rules can include policies for controlling / monitoring granular traffic based on AF requests.

[0348] N4 rules may include QFI and / or granular traffic-specific QoS parameters assigned in step 6.

[0349] 8) Step 8

[0350] The SMF can send a PDU session establishment approval message to the terminal.

[0351] The contents of Figures 6 and 7 can be applied to step 8.

[0352] 9) Step 9

[0353] 9-1) step 9-1

[0354] The terminal can receive UE policies and QoS rules from the network. The UE policy may be transmitted to the terminal from the PCF via the AMF. The QoS rule may be transmitted to the terminal from the SMF during the session establishment process. The QoS rule may be transmitted to the terminal along with a session establishment acknowledgment message.

[0355] A UE policy or QoS rule may include information capable of distinguishing granular traffic (e.g., traffic information of Section II described above capable of distinguishing traffic related to AI operations (or traffic of specific operations related to AI operations)). The information capable of distinguishing granular traffic may be the traffic information of Section II described above.

[0356] The above QoS rule may include information (e.g., QoS parameter values) regarding the required QoS conditions per traffic for specific operations related to AI operations. For example, the above QoS rule may include information regarding the maximum transmission speed of traffic for data collection related to AI operations and the maximum transmission speed of traffic for monitoring model performance related to AI operations.

[0357] Based on the information received by the terminal, the terminal can perform granular traffic-specific management.

[0358] For example, the terminal can adjust QoS parameter values ​​(e.g., maximum transmission speed, latency, etc.) for uplink data related to specific AI operations (e.g., data collection, model training, model performance monitoring). Through this, traffic related to AI operations transmitted by the terminal can be controlled differentially on a per-traffic basis. Then, the terminal can transmit uplink data for specific AI operations (e.g., data collection, model training, model performance monitoring) based on the adjusted QoS parameters.

[0359] For example, the following traffic can each be controlled by different QoS parameters (e.g., maximum transmission rate, latency, etc.):

[0360] - Terminal uplink data for AI operation data collection

[0361] - Terminal uplink data for AI behavior model training

[0362] - Terminal uplink data for monitoring model performance of AI operations

[0363] For example, the terminal can generate records related to billing by the aforementioned granular traffic.

[0364] 9-2) step 9-2

[0365] The base station can receive subscriber information and a QoS profile from the network (e.g., SMF). The QoS profile can be transmitted to the terminal along with a session establishment acknowledgment message.

[0366] The subscriber information or QoS profile may include information capable of distinguishing granular traffic (e.g., traffic information of Section II described above capable of distinguishing traffic related to AI operations (or traffic of specific operations related to AI operations)). The information capable of distinguishing granular traffic may be the traffic information of Section II described above.

[0367] Subscriber information or QoS profiles may include information (e.g., QoS parameter values) regarding required QoS conditions per traffic for specific operations related to AI operations. For example, said subscriber information or QoS profiles may include information regarding the maximum transmission speed of traffic for collecting data related to AI operations and the maximum transmission speed of traffic for monitoring model performance related to AI operations.

[0368] Based on subscriber information or QoS profiles, base stations can perform granular traffic-specific management.

[0369] For example, the base station can adjust QoS parameter values ​​for uplink / downlink data (e.g., maximum transmission speed, latency, etc. of traffic for AI behavior-related model training). Through this, AI behavior-related traffic transmitted and received by the base station can be controlled differentially on a traffic-by-traffic basis.

[0370] For example, the following traffic can each be controlled by different QoS parameters (e.g., maximum transmission rate, latency, etc.):

[0371] - Base station uplink / downlink data for AI operation data collection

[0372] - Base station uplink / downlink data for AI behavior model training

[0373] - Base station uplink / downlink data for monitoring AI operation model performance

[0374] For example, the base station can generate the aforementioned granular traffic-specific billing records.

[0375] 9-3) step 9-3

[0376] SMF can receive PCC rules and subscriber information from PCF. Based on this, SMF can perform granular traffic-based management.

[0377] SMF can receive monitoring information from network nodes (e.g., UPF, NWDAF, etc.).

[0378] PCC rules, subscriber information, and monitoring information may include information capable of distinguishing granular traffic (e.g., traffic information of Section II described above capable of distinguishing traffic related to AI operations (or traffic of specific operations related to AI operations)). The information capable of distinguishing granular traffic may be the traffic information of Section II described above.

[0379] For example, based on information capable of distinguishing granular traffic from monitoring data, a network node can check whether the transmission of traffic for specific AI-related operations (e.g., data collection, model training, model performance monitoring) satisfies configured QoS parameters (e.g., maximum transmission speed, latency, etc.).

[0380] Based on monitoring information, the SMF can transmit information for adjusting QoS parameter values ​​to the terminal, base station, and / or UPF.

[0381] 9-4) step 9-4

[0382] UPF may receive N4 rules and subscriber information from SMF. The N4 rules or subscriber information may include information capable of distinguishing granular traffic (e.g., traffic information of Section II described above capable of distinguishing traffic related to AI operations (or traffic of specific operations related to AI operations)). The information capable of distinguishing granular traffic may be the traffic information of Section II described above.

[0383] Based on this, UPF can perform granular traffic-specific management.

[0384] For example, UPF can adjust QoS parameter values ​​(e.g., maximum transmission rate, latency, etc.) for traffic related to AI operations downlink data. Through this, traffic related to AI operations downlink data can be controlled differentially on a per-traffic basis.

[0385] For example, the following traffic can each be controlled by different QoS parameters (e.g., maximum transmission rate, latency, etc.):

[0386] - Data for collecting AI operation data

[0387] - Data for training AI behavior models

[0388] - Data for monitoring model performance of AI operations

[0389] For example, UPF can generate the aforementioned granular traffic-specific billing records.

[0390] According to the disclosure of the present specification, the following operations may be performed:

[0391] - The network control node (e.g., SMF) can receive information from the AF that can be used to distinguish traffic.

[0392] - The network control node (e.g., SMF) can receive subscriber information from the UDM / UDR.

[0393] - When performing the session establishment procedure, the network control node (e.g., SMF) can establish a PDU session (a PDU session associated with a specific DNN, specific S-NSSAI, etc.) based on information received from the AF.

[0394] - When configuring a QoS flow, the network control node (e.g., SMF) may assign a specific (range) QFI associated with a specific QoS parameter based on information received from the AF. Alternatively, when performing the session establishment procedure, the network control node (e.g., SMF) may assign a specific (range) QFI associated with a specific QoS parameter based on a policy received from the PCF.

[0395] - The network control node (e.g., SMF) can send the relevant information to the UPF. Based on this, the transmission and reception information of related data can be controlled and managed.

[0396] - The network control node (e.g., SMF) can send the relevant information to the terminal and base station. Based on this, the transmission and reception information of related data can be controlled and managed.

[0397] The following drawings are made to illustrate a specific example of the present specification. The names of specific devices or specific signals / messages / fields described in the drawings are presented as examples, and therefore the technical features of the present specification are not limited to the specific names used in the following drawings.

[0398] FIG. 9 illustrates the procedure of a session-related NF for the disclosure of the present specification.

[0399] 1. Session-related NF (Network Function) can receive traffic information.

[0400] The above traffic information may include information that the first traffic for the first operation uses the first parameter.

[0401] 2. The above session-related NF may receive a request to establish a PDU (Protocol Data Unit) session for the UE (User Equipment).

[0402] 3. The above session-related NF can determine that there is user consent of the UE for the above first traffic.

[0403] 4. Based on the above decision and the above traffic information, the session-related NF may allocate a QFI (Quality of Service flow Indication) for the first traffic.

[0404] 5. The above session-related NF can transmit the above QFI to the UPF (User Plane Function).

[0405] 6. Based on the above decision, the session-related NF may transmit approval for the establishment of the PDU session.

[0406] The above PDU session may be a session for traffic related to the above first operation.

[0407] The above first operation may be related to AI (Artificial Intelligence).

[0408] The above traffic information may be information based on a request from an AF (Application Function).

[0409] The step of the session-related NF receiving the traffic information may include: the session-related NF receiving a PCC (Policy and Charging Control) rule containing the traffic information from a PCF (Policy Control Function).

[0410] The above PCC rule may include at least one of i) a charge rule for the first traffic, ii) a maximum value that limits the usage of the first traffic, or iii) a QoS (QoS of Service) parameter required for the first traffic.

[0411] The above QoS parameter may include at least one of transmission speed or delay time.

[0412] The first parameter above may include at least one of DNN (Data Network Name), S-NSSAI (Single Network Slice Selection Assistance Information), DNAI (Data Network Access Identifier), traffic description information, IP (Internet Protocol) address, port number, session number, and QFI (QoS Flow Identifier) ​​number.

[0413] The step of determining that the above session-related NF has user consent of the UE for the above first traffic is:

[0414] The step of the above session-related NF obtaining user subscriber information from UDM (Unified Data Management) or UDR (Unified Data Repository); and

[0415] The above session-related NF may include a step of determining that the user has consent to the first action in the subscriber information.

[0416] The above subscriber information may include the user's consent to at least one of i) monitoring model performance related to AI operation, ii) exposure of data by AI operation to an access network, iii) generation of sensing contextual information related to AI operation, iv) monitoring of sensing performance related to AI operation, or v) collection of data related to AI operation.

[0417] Based on the above decision and the above traffic information, the session-related NF can generate a billing record for the first traffic.

[0418] Based on the above decision and the above traffic information, the session-related NF can transmit QoS parameters for the first traffic to the base station.

[0419] The above session-related NF may be an SMF (Session Management Function).

[0420] The first operation above may be at least one of data collection, model training, or model performance monitoring.

[0421] The above traffic information may include QoS information required for the first traffic.

[0422] The above session-related NF can generate an N4 rule that includes the above assigned QFI and the above QoS information.

[0423] The step of the session-related NF transmitting the QFI to the UPF is: the session-related NF may transmit the generated N4 rule to the UPF.

[0424] The above session-related NF can transmit the above traffic information to the UE.

[0425] The following drawings are made to illustrate a specific example of the present specification. The names of specific devices or specific signals / messages / fields described in the drawings are presented as examples, and therefore the technical features of the present specification are not limited to the specific names used in the following drawings.

[0426] FIG. 10 illustrates the procedure of the UE for the disclosure of the present specification.

[0427] 1. A UE (User Equipment) can send a request to the network to establish a PDU (Protocol Data Unit) session.

[0428] 2. The above UE can receive traffic information from the network.

[0429] The above traffic information may include information that the first traffic for a first operation related to AI (Artificial Intelligence) uses a first parameter.

[0430] The above PDU session may be a session for traffic related to the above first operation.

[0431] The above traffic information may be information based on a request from an AF (Application Function).

[0432] The above traffic information may include information regarding the QoS (Quality of Service) conditions required for the first traffic.

[0433] The first parameter above may include at least one of DNN (Data Network Name), S-NSSAI (Single Network Slice Selection Assistance Information), DNAI (Data Network Access Identifier), traffic description information, IP (Internet Protocol) address, port number, session number, and QFI (QoS Flow Identifier) ​​number.

[0434] The first operation above may be at least one of data collection, model training, or model performance monitoring.

[0435] Based on the above traffic information, the UE can adjust the QoS parameters for the uplink data for the first operation.

[0436] Based on the above-mentioned adjusted QoS parameters, the UE can transmit uplink data for the first operation to the network.

[0437] The above QoS parameter may include at least one of transmission speed or delay time.

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

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

[0440] For example, the processor can be configured to be operablely coupled with memory and the processor.

[0441] The operation performed by the processor comprises: a step in which a session-related NF (Network Function) receives traffic information; the traffic information includes information that a first traffic for a first operation uses a first parameter, and the session-related NF receives a request to establish a PDU (Protocol Data Unit) session for a UE (User Equipment); the session-related NF determines that there is user consent of the UE for the first traffic; the session-related NF transmits approval to establish the PDU session based on the determination; the session-related NF assigns a QFI (Quality of Service flow Indication) for the first traffic based on the determination and the traffic information; and the session-related NF transmits the QFI to a UPF (User Plane Function), and the PDU session may be a session for traffic related to the first operation.

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

[0443] The operation performed by the processor comprises: a step in which a session-related NF (Network Function) receives traffic information; the traffic information includes information that a first traffic for a first operation uses a first parameter, and the session-related NF receives a request to establish a PDU (Protocol Data Unit) session for a UE (User Equipment); the session-related NF determines that there is user consent of the UE for the first traffic; the session-related NF transmits approval to establish the PDU session based on the determination; the session-related NF assigns a QFI (Quality of Service flow Indication) for the first traffic based on the determination and the traffic information; and the session-related NF transmits the QFI to a UPF (User Plane Function), and the PDU session may be a session for traffic related to the first operation.

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

[0445] According to some embodiments of the present disclosure, the technical features of the present disclosure may be directly implemented in hardware, software executed by a processor, or a combination of both. 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, 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.

[0446] In some examples, storage media are coupled to the processor so that the processor can read information from the storage media. Alternatively, the storage media can be integrated into the processor. The processor and storage media can reside in an ASIC. In other examples, the processor and storage media can reside as separate components.

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

[0448] For example, non-volatile computer-readable media may include RAM (Random Access Memory) such as SDRAM (Synchronization Dynamic Random Access Memory), ROM (Read-Only Memory), and NVRAM (Non-Volatile Random Access Memory); read-only memory (EEPROM); flash memory; magnetic or optical data storage media; or other media that can be used to store instructions or data structures. Non-volatile computer-readable media may also include combinations of the above.

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

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

[0451] One or more stored commands include the steps of: a session-related Network Function (NF) receiving traffic information; the traffic information including information that a first traffic for a first operation uses a first parameter; the session-related NF receiving a request to establish a Protocol Data Unit (PDU) session for a User Equipment (UE); the session-related NF determining that there is user consent of the UE for the first traffic; based on the determination, the session-related NF transmitting approval to establish the PDU session; based on the determination and the traffic information, the session-related NF assigning a Quality of Service Flow Indication (QFI) for the first traffic; and the session-related NF transmitting the QFI to a User Plane Function (UPF), wherein the PDU session may be a session for traffic related to the first operation.

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

[0453] This specification may have various effects.

[0454] For example, AI-related traffic can be segmented and managed and controlled through the procedures disclosed in this specification.

[0455] The effects obtainable through the specific examples of this specification are not limited to those listed above. For example, there may be various technical effects that a person with ordinary skill in the related art can understand or derive 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.

[0456] The claims described in this specification may be combined in various ways. For example, the technical features of the method claims in this specification may be combined to be implemented as a device, and the technical features of the device claims in this specification may be combined to be implemented as a method. Furthermore, the technical features of the method claims and the technical features of the device claims in this specification may be combined to be implemented as a device, and the technical features of the method claims and the technical features of the device claims in this specification may be combined to be implemented as a method. Other implementations are within the scope of the following claims.

Claims

As a method, A step in which a session-related NF (Network Function) receives traffic information; The above traffic information includes information that the first traffic for the first operation uses a first parameter, and A step in which the above session-related NF receives a request to establish a PDU (Protocol Data Unit) session for the UE (User Equipment); A step of determining that the session-related NF has user consent of the UE for the first traffic; Based on the above decision and the above traffic information, the step of the session-related NF allocating a QFI (Quality of Service flow Indication) for the first traffic; The step of the above session-related NF transmitting the above QFI to the UPF (User Plane Function); and Based on the above decision, the step of the session-related NF transmitting approval for the establishment of the PDU session is included, and A method in which the above PDU session is a session for traffic related to the above first operation. In paragraph 1, The above first operation is a method related to AI (Artificial Intelligence). In paragraph 1 or 2, A method in which the above traffic information is information based on a request from an AF (Application Function). In any one of paragraphs 1 through 3, A method in which the above session-related NF receives the traffic information, comprising the step of the above session-related NF receiving a PCC (Policy and Charging Control) rule containing the traffic information from a PCF (Policy Control Function). In paragraph 4, The above PCC rule is a method comprising at least one of i) a charge rule for the first traffic, ii) a maximum value limiting the usage for the first traffic, or iii) a QoS (QoS of Service) parameter required for the first traffic. In paragraph 5, The above QoS parameter is a method that includes at least one of transmission speed or delay time. In any one of paragraphs 1 through 6, A method in which the first parameter above includes at least one of DNN (Data Network Name), S-NSSAI (Single Network Slice Selection Assistance Information), DNAI (Data Network Access Identifier), traffic description information, IP (Internet Protocol) address, port number, session number, and QFI (QoS Flow Identifier) ​​number. In any one of paragraphs 1 through 7, The step of determining that the above session-related NF has user consent of the UE for the above first traffic is: The step of the above session-related NF obtaining user subscriber information from UDM (Unified Data Management) or UDR (Unified Data Repository); and A method comprising the step of determining that the session-related NF determines that the user has consent to the first action in the subscriber information. In paragraph 8, A method comprising the user's consent to at least one of the above subscriber information, i) monitoring of model performance related to AI operation, ii) exposure of data by AI operation to an access network, iii) generation of sensing contextual information related to AI operation, iv) monitoring of sensing performance related to AI operation, or v) collection of data related to AI operation. In any one of paragraphs 1 through 9, A method further comprising the step of, based on the above decision and the above traffic information, the session-related NF generating a billing record for the first traffic. In any one of paragraphs 1 through 9, A method further comprising the step of transmitting QoS parameters for the first traffic to a base station by the session-related NF based on the above decision and the above traffic information. In any one of paragraphs 1 through 11, The above session-related NF is a method that is an SMF (Session Management Function). In any one of paragraphs 1 through 12, The above first operation is a method that is at least one of data collection, model training, or model performance monitoring. In any one of paragraphs 1 through 13, The above traffic information includes QoS information required for the first traffic, and The step of generating an N4 rule including the assigned QFI and the QoS information using the session-related NF; and The step of the session-related NF transmitting the QFI to the UPF further comprises the step of the session-related NF transmitting the generated N4 rule to the UPF. In any one of paragraphs 1 through 14, A method further comprising the step of the above session-related NF transmitting the above traffic information to the UE. As a method, A step in which the UE (User Equipment) transmits a request to the network to establish a PDU (Protocol Data Unit) session; and The above UE includes the step of receiving traffic information from the network, The above traffic information includes information that the first traffic for a first operation related to AI (Artificial Intelligence) uses a first parameter, and A method in which the above PDU session is a session for traffic related to the above first operation. In Paragraph 16, A method in which the above traffic information is information based on a request from an AF (Application Function). In paragraph 16 or 17, A method in which the above traffic information includes information on QoS (Quality of Service) conditions required for the first traffic. In any one of paragraphs 16 through 18, A method in which the first parameter above includes at least one of DNN (Data Network Name), S-NSSAI (Single Network Slice Selection Assistance Information), DNAI (Data Network Access Identifier), traffic description information, IP (Internet Protocol) address, port number, session number, and QFI (QoS Flow Identifier) ​​number. In any one of paragraphs 16 through 19, The above first operation is a method that is at least one of data collection, model training, or model performance monitoring. In any one of paragraphs 16 through 20, Based on the above traffic information, the UE adjusts QoS parameters for uplink data for the first operation; and A method further comprising the step of the UE transmitting uplink data for the first operation to the network based on the above-mentioned adjusted QoS parameters. In paragraph 21, The above QoS parameter is a method that includes at least one of transmission speed or delay time. As a session-related NF (Network Function) that performs communication, At least one transmitter / receiver; It includes at least one processor, The operation performed by the above at least one processor is a session-related NF that is a method according to any one of claims 1 to 15. As a UE (User Equipment) performing communication, At least one transmitter / receiver; It includes at least one processor, The operation performed by the above-mentioned at least one processor is a method according to any one of claims 16 to 22, UE. As an apparatus in mobile communication, At least one processor; and It includes at least one memory that stores instructions and is operablely electrically connected to at least one processor, and A device in which the operation performed based on the execution of the above instruction by the at least one processor is a method according to any one of claims 1 to 15. As a non-volatile computer-readable storage medium that records instructions, A non-volatile computer-readable storage medium in which the above instructions, when executed by one or more processors, cause the one or more processors to perform a method according to any one of claims 1 to 15.