UPF load management for specific traffic

Abstract

One aspect of the present disclosure provides a method. The method comprises the steps of: transmitting, by an SMF, a first message including a request for information related to a load of a specific UPF to an NF; receiving, by the SMF, a second message including information related to a load of specific traffic of the specific UPF from the NF; determining, by the SMF, an overload of the load of the specific UPF on the basis of the information related to the load of the UPF; and performing, by the SMF, UPF reselection on the basis of the determination.

Description

UPF Load Management for 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] Manages the load of UPF for specific traffic.

[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] FIG. 6 shows an example of a flowchart of a first embodiment according to the disclosure of the present specification.

[0012] FIG. 7 shows an example of a flowchart of a second embodiment according to the disclosure of the present specification.

[0013] FIG. 8 illustrates the procedure of the SMF for the disclosure of the present specification.

[0014] FIG. 9 illustrates the PCF procedure for the disclosure of the present specification.

[0015] FIG. 10 illustrates the procedure of UPF for the disclosure of the present specification.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0043] 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) may transmit / receive signals through various physical channels. To this end, based on various proposals in this 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.

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

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

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

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

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

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

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

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

[0052] 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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0089] 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 signaling with the AMF (410) and is connected to the UPF (440) via the N3 interface for data transmission.

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

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

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

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

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

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

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

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

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

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

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

[0101] - AUSF (Authentication Server Function)

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

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

[0104] - USDF (Unstructured Data Storage Function)

[0105] - NEF (Network Exposure Function)

[0106] - I-NEF (Intermediate NEF)

[0107] - NRF (Network Repository Function)

[0108] - NSSF (Network Slice Selection Function)

[0109] - PCF (Policy Control Function)

[0110] - SMF (Session Management Function)

[0111] - UDM (Unified Data Management)

[0112] - UDR (Unified Data Repository)

[0113] - UPF (User Plane Function)

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

[0115] - AF (Application Function)

[0116] - UE (User Equipment)

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

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

[0119] - NWDAF (Network Data Analytics Function)

[0120] - CHF (CHarging Function)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0145] - 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)

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

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

[0148] < UPF Management >

[0149] 1. The Importance of UPF Management Due to AIML

[0150] Research is required on the improvement of AI / ML in UPF.

[0151] - The development of AI / ML technology is required to improve the robustness and resilience of 5G networks.

[0152] For example, if errors occur during transmission and reception with the RAN or DN for unknown reasons, or if incorrectly formatted UP packets are generated, it can ultimately lead to UPF performance degradation and system failure. To prevent these problems, it is essential to extend the scope of AIML_CN research to the user plane (UP). It is also important for UPF to perform high-speed packet processing in conjunction with AI / ML.

[0153] A method is required to prevent 5G system performance from degrading due to UPF traffic.

[0154] 2. Conventional UPF Event Management and Additional Considerations in the AIML Environment Proposed in This Document

[0155] The following was proposed as a measure to prevent UPF performance degradation caused by “UPF data reporting to NWDAF”:

[0156] - Combines individual requests from multiple nodes in UPF

[0157] - Delays reporting

[0158] - Technology to reduce event notifications

[0159] For example, if event notifications can be delayed (delay acceptable), report suggestion information may be included. Report suggestion information may include report urgency and report time information. Report urgency information may indicate whether the event report is delay acceptable (whether the report can be delayed). If the report urgency information is marked as "delay acceptable," a report time defining the last valid report time may also be provided. The UPF must report events detected before the last valid time.

[0160] For services where reporting becomes meaningless after a certain period, for example, for services where maintaining UPF performance is more important from the operator's perspective (e.g., traffic information for real-time reference rather than creating cumulative statistics for specific traffic)

[0161] - UPF measures performance internally and may start comparing it to the UPF threshold. If the UPF threshold is exceeded, UPF may stop reporting the service subscribed to by NF in order to avoid further impacting UPF's performance.

[0162] - UPF continues to measure performance and can compare it to the UPF threshold. Once the UPF threshold is not exceeded, UPF can resume reporting, which is the service subscribed to by NF.

[0163] For AIML operations, model (re)training data, model test data, monitoring data (model performance and / or accuracy, etc.), inference data, and model transmission / distribution traffic may be processed on core network nodes such as UPFs. In this case, the volume of traffic passing through UPFs can increase excessively. Furthermore, event reporting by UPFs, which must monitor and report this traffic, is expected to become even more critical.

[0164] In this specification, signaling / processing / computing loads for processing traffic for specific purposes, such as AIML operations, and signaling / processing / computing loads for event reporting that must monitor and report such traffic are considered.

[0165] Beyond the efficiency achieved by managing the temporal concept of urgent reporting / delay-tolerant reporting or by suspending reporting, the method proposed herein is:

[0166] - 1) Loads for specific purposes of traffic can be separated / managed at network nodes.

[0167] - 2) To this end, a separate load / computing burden for reporting important events that the network must handle can be considered.

[0168] Traditionally, the primary function of UPF was user data processing; however, to handle special traffic distinct from user data, such as AIML operations, the load of UPF can be separated or segmented. As a result, network resources can be utilized effectively.

[0169] Network management measures regarding UPF loads that process traffic for specific purposes can be proposed.

[0170] The function of reporting specific events requested by other network nodes after traffic monitoring was considered an additional feature of UPF. Therefore, if the focus was on technologies that perform event reporting without degrading UPF's performance, UPF would have to monitor a relatively large volume of specific types of traffic that need to be processed in the network due to AIML, etc. Consequently, event reporting regarding this could also be considered a very important function.

[0171] Therefore, when event reporting is critical, policies and management measures are required to ensure event reporting. For example, network management measures can be proposed to ensure event reporting for traffic intended for specific purposes, such as AIML operations (e.g., model (re)training data, model test data, monitoring data (model performance and / or accuracy, etc.), inference data, model transmission / distribution traffic, etc.).

[0172] This specification proposes methods to solve these problems. The proposed methods may be performed or used optionally, in combination, or complementarily.

[0173] In this specification, specific traffic may be traffic related to UPF.

[0174] In this specification, embodiments are described based on the structure, procedures, messages, etc. of a 5G mobile communication system, but are not limited thereto and can be extended to an evolved form of a 6G mobile communication system.

[0175] Although this specification specifies embodiments regarding event reporting of UPF, it is not limited thereto and can be generalized and applied to event reporting of other network nodes.

[0176] According to an embodiment of the present specification, based on requests and local configurations of a terminal, a third-party application server / AF, or other network nodes, etc., a UPF can recognize traffic for a specific purpose (e.g., AIML operation, model (re-)training data, model testing data, monitoring data (model performance and / or accuracy, etc.), inference data, model transfer / delivery traffic, etc.) and perform QoS and various event reporting in relation thereto.

[0177] The aforementioned request from the third-party application server / AF may implicitly or directly include a request to manage / guarantee processing for specific traffic (or a request to manage / guarantee load) or a request to manage / guarantee event reporting for specific traffic, such as AIML operations (or a request to manage / guarantee load related thereto).

[0178] In particular, follow-up measures may be taken considering UPF performance degradation or computation load resulting from the processing of specific traffic and event monitoring / reporting.

[0179] The above follow-up action may be the reselection / relocation of the core network's UPF for resetting / re-establishing a UP path for traffic of a specific purpose. Alternatively, the above follow-up action may be a procedure for establishing a UP path to connect to another edge data network / edge server.

[0180] I. First Embodiment: Utilization of NWDAF Analytic

[0181] A service consumer of NWDAF analytics can be a network node that intends to use network management by utilizing NF (e.g., SMF, PCF, AF) and UPF load / UPF event reporting information.

[0182] Consumers of NWDAF Analytics can send requests containing the following:

[0183] - Analytics ID = "NF load experience" or "Event reporting experience".

[0184] A consumer can send a relevant request (e.g., a request related to specific traffic) to NWDAF. Based on this, NWDAF can collect input data. Based on the collected input data, NWDAF can determine output data (output analytics). NWDAF can send the output data (output analytics) to the said consumer.

[0185] Representative inputs and outputs are described below. Inputs and outputs are not limited to the information described below and may consist of combinations of such information. It is assumed that information is collected based on groups and combinations of individual granularities, as well as per UE, PDU session, slice, and NF node. Furthermore, it is assumed that statistical and predicted values ​​can be calculated.

[0186] 1. Analytics

[0187] (1) Input Data

[0188] (from UPF) When providing input to NWDAF directly from UPF, the input data may be at least one of the following:

[0189] - UPF's total signaling / processing / computing load in use / operation over time, available buffered load capability / status at a specific point in time, etc.

[0190] - Signaling / processing / computing loads being used / operated for traffic for specific purposes over time, buffered load capability / status available at a specific point in time, etc.

[0191] For example, the traffic for the aforementioned specific purpose may be AIML operations. More specifically, it may be load information separated by each operation (model (re)training data, model test data, monitoring data (model performance and / or accuracy, etc.), inference data, model transmission / distribution traffic, etc.).

[0192] - Signaling / processing / computing loads in use / operation, buffered load capability / status available at a specific point in time, etc., for management purposes of event reporting regarding specific traffic.

[0193] - Information regarding event reporting for specific traffic management purposes: event reporting time, cloud or location / region information where the event reporting node is hosted, etc.

[0194] - The ratio of the active load / available load for specific traffic relative to the total signaling / processing / computing load of UPF, etc.

[0195] - Operating load ratio / available load ratio, etc., for management-purpose event reporting on specific traffic relative to the total signaling / processing / computing load of UPF

[0196] (from SMF) Input data from SMF may be at least one of the following:

[0197] - When UPF provides input to NWDAF via SMF, information identical to the information provided as input by the UPF, or information aggregated / processed with a different granularity, etc.

[0198] - Information related to PDU sessions, for example, information regarding the activation / deactivation of PDU sessions, etc.

[0199] (from AMF) Input data from AMF may be at least one of the following:

[0200] - Various information related to the UE, for example, the UE's location information, etc.

[0201] - UE location / region information while performing specific event reporting, etc.

[0202] (from AF) Input data from AF may be at least one of the following:

[0203] - UE location and data network / session-related information that the application can provide, etc.

[0204] - Information on the types of specific traffic that the application can provide (e.g., AIML operation, model (re-)training data, model testing data, monitoring data (model performance and / or accuracy, etc.), inference data, model transfer / delivery traffic, etc.)

[0205] (from OAM) Input data from OAM may be at least one of the following:

[0206] - Load-related information of UPF that can be collected from OAM, etc.

[0207] - Terminal information that can be collected by OAM, etc.

[0208] (2) Output Analytics

[0209] 1) Statistical value (Statistic)

[0210] Output analytics may include load-related statistical information for traffic intended for a specific purpose. For example, output analytics may include all statistical values ​​of the data collected as input. For example, output analytics may include at least one of the following:

[0211] - Load change / change trends over a certain period of time

[0212] - The ratio of the active load / available load for specific traffic relative to the total signaling / processing / computing load of UPF, etc.

[0213] Output analytics may include statistical information regarding event reporting for the management purposes of specific traffic. For example, output analytics may include all statistical values ​​of the data collected as input. For example, output analytics may include at least one of the following:

[0214] - Event reporting frequency / cycle / time,

[0215] - Signaling / processing / computing load for event reporting (based on time / region),

[0216] - For event reporting purposes regarding specific traffic relative to the total signaling / processing / computing load of UPF, it can include all statistical values ​​of the data collected as input, such as the ratio of the operating load / the ratio of the available load.

[0217] 2) Prediction

[0218] Output analytics may include predictive information regarding specific traffic and / or predictive information regarding event reporting for management purposes. For example, output analytics may include future predicted values ​​for data collected as input.

[0219] 2. Procedure

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

[0221] FIG. 6 shows an example of a flowchart of a first embodiment according to the disclosure of the present specification.

[0222] 1) Step 1

[0223] A registration procedure for the terminal to connect to the network can be performed.

[0224] 2) Step 2

[0225] AF can send AF requests to the core network.

[0226] A network node (e.g., PCF, NEF) can receive an AF request from an AF. Based on the AF request, the network node can send a message related to the AF request to an SMF. Based on the message related to the AF request, the SMF can perform the operations described below.

[0227] The above AF request may include a request for specific traffic load management and / or a request for event reporting guarantees.

[0228] The above AF request may be a request for information related to the load on specific traffic in UPF and / or the load on event reporting related to said specific traffic.

[0229] The aforementioned specific traffic may be traffic related to UPF.

[0230] 3) Step 3

[0231] Network nodes (consumers) (e.g., SMF, PCF, NEF) can send analytics requests to NWDAF.

[0232] 4) Step 4

[0233] NWDAF can collect input data from each node, base station, or terminal.

[0234] Based on input data, NWDAF can generate / determine output analytics.

[0235] 5) Step 5

[0236] NWDAF can transmit output analytics to SMF, PCF, NEF, or AF (via NEF).

[0237] 6) Step 6

[0238] Subsequent actions utilizing output analytics are described in the following section.

[0239] 3. Subsequent action

[0240] (1) SMF

[0241] Based on output analytics, SMF can recognize, anticipate, and determine overload caused by specific traffic or event reporting. Alternatively, based on output analytics, SMF can recognize, anticipate, and determine when UPF performance will degrade.

[0242] Based on this, in order to resolve / prevent UPF performance degradation and ensure specific traffic processing and event reporting, the SMF can decide on UPF reselection / UPF relocation. Through this, the SMF can decide to reset the UP path and perform the corresponding procedure.

[0243] (2) PCF

[0244] 1) When PCF receives output analytics from NWDAF

[0245] Based on output analytics, PCF can recognize, anticipate, or determine overload caused by specific traffic or event reporting. Alternatively, based on output analytics, PCF can recognize or anticipate when UPF performance will degrade.

[0246] Based on this, to ensure specific traffic or event reporting, the PCF can determine policy updates and provision new policies to the network and base stations / terminals.

[0247] For example, the PCF can update policies and provide them to the network / base station / terminal.

[0248] 2) When PCF receives a policy control request trigger from SMF

[0249] Based on output analytics, SMF can recognize, anticipate, or determine overload caused by specific traffic or event reporting. Alternatively, based on output analytics, SMF can recognize or anticipate when UPF performance will degrade.

[0250] Based on this, to ensure the reporting of specific traffic or events, the SMF can send Policy Control Request Triggers to the PCF.

[0251] Based on this, the PCF determines policy updates and can provision new policies to the network and base stations / terminals. For example, the PCF can provide and configure the updated policies to the SMF, base stations, or terminals.

[0252] For example, the PCF can update policies and provide them to the network / base station / terminal.

[0253] Examples of definitions for the above Policy Control Request Triggers may be as shown in Table 3. For example, the contents of Table 3 may be information (or conditions of the trigger) included in the above Policy Control Request Triggers.

[0254] Table 3 shows access independent Policy Control Request Triggers relevant for SMF.

[0255] Policy Control Request TriggerDescriptionNF load changeNF node-level load threshold is exceeded or not exceeded (e.g., change in total UPF load)NF specific traffic load changeNF specific traffic load threshold is exceeded or not exceeded (e.g., change in load for specific traffic processing)NF event reporting load changeNF event reporting load threshold is exceeded or not exceeded (e.g., change in load for event reporting processing) It is assumed that the above threshold values ​​were included in the AF request and transmitted to the core network, or were pre-configured in advance by the SLA between the operator and the third-party AS / AF.

[0256] Based on output analytics, the SMF can detect / determine that the NF node-level load has exceeded a threshold. The SMF can send a policy control request trigger containing 'NF load change' to the PCF. Based on this, the PCF can update the policy to change the UPF overall load.

[0257] Based on output analytics, the SMF can detect / determine that the NF-specific traffic load has exceeded a threshold. The SMF can send a policy control request trigger containing 'NF-specific traffic load change' to the PCF. Based on this, the PCF can update the policy to change the load for processing the specific traffic.

[0258] Based on output analytics, the SMF can detect / determine that the NF event reporting load has exceeded a threshold. The SMF can send a policy control request trigger to the PCF that includes 'NF event reporting load change'. Based on this, the PCF can update the policy to change the load for event reporting processing.

[0259] (3) AF

[0260] Based on output analytics, AF can detect / predict overload caused by specific traffic processing or event reporting. Alternatively, based on output analytics, AF can detect / predict when UPF performance will degrade.

[0261] Based on this, if AF has previously requested event reporting from UPF, AF can modify the request for event reporting. For example, AF can change the reporting cycle or the events to be reported for the event report.

[0262] Alternatively, based on this, AF can change the behavior of the application layer. For example, AF can perform AIML-specific behaviors at the application layer, change the timing of ML model transfers / downloads, etc.

[0263] II. Second Embodiment: Adding a New Parameter Flag to Service Operation

[0264] According to the second embodiment, a new parameter flag may be added to the service operation. The parameter flag may be for requesting an event report (notification) to consider UPF performance.

[0265] Network nodes receive event reports (notifications) from UPF and can utilize this information to manage the network. To this end, network nodes can subscribe to UPF event exposure. For example, a network node can send an Event Exposure Subscribe request message to UPF. This message can be delivered to UPF directly or indirectly (e.g., via SMF).

[0266] The event exposure subscription service (Nupf_EventExposure_Subscribe) provided by the User Plane Function (UPF) of the core network will be described below.

[0267] This service is used when a specific NF (Network Function, e.g., NWDAF) sets up or modifies a subscription to receive traffic data or specific events from UPF.

[0268] This service operation can be used for a specific NF to subscribe to UPF event exposure notifications or to modify existing subscriptions. For example, the service operation may be intended to collect UPF data for a specific PDU session, all PDU sessions of a single terminal (UE), or all terminals (any UE).

[0269] A network node can perform a subscription through a message containing inputs from an event exposure subscription service. When the subscription is approved, an event report (notification) containing outputs can be sent to the network node.

[0270] The required input for the event exposure subscription service may be at least one of the following:

[0271] - NF ID (Network Function Identifier requesting the service)

[0272] - Event reporting targets (e.g., "any UE")

[0273] - Event ID(s)

[0274] - Notification Target Address (and Notification Correlation ID)

[0275] - Event Reporting Information (Table 4)

[0276] The optional input of the event exposure subscription service may be at least one of the following:

[0277] - Subscription Correlation ID (Required for subscription modification)

[0278] - Expiry time

[0279] - DNN (Data Network Name)

[0280] - S-NSSAI (Slice Identifier)

[0281] - Application ID(s) or traffic filtering information

[0282] - Measurement Type and Unit of Measurement (Granularity)

[0283] - Report proposal information

[0284] - Instructions to report subscription termination

[0285] - Remaining data reporting instructions

[0286] - Terminal (UE)'s (private) IP address

[0287] - IP domain

[0288] - IP address of the remote end

[0289] - Port number of the remote end

[0290] If the subscription is approved, the required output of the event exposure subscription service may be at least one of the following:

[0291] - Subscription correlation identifier (required for managing this subscription)

[0292] - Expiration time (required if expiration is set according to operator policy)

[0293] The optional output of the event exposure subscription service may be at least one of the following. Where possible, it may be included in the first event report:

[0294] - Notification Target Address (and Notification Correlation ID): This is used to match (correlate) the notifications sent by UPF with this subscription information.

[0295] Among the inputs of the event exposure subscription service, the event reporting information may include the contents of Table 4.

[0296] Event Reporting Information Parameter Description Presence requirement Event reporting mode Mode of reporting - e.g., reporting up to a maximum number of reports, periodic reporting along with periodicity, variable reporting periodicity, reporting up to a maximum duration, reporting when threshold is reached. mandatory Reporting Threshold Threshold values ​​indicate conditions on the level to be reached for the reporting Optional "Consideration on NF (e.g., UPF) load for specific traffic processing" flag Indicates to the Event provider NF if the threshold of NF load for specific traffic processing is exceeded.Optionally, may imply to the Event provider NF to send the notification to the Event consumer NF if the threshold of NF load for specific traffic processing is not exceeded. When subscribing to events for reporting, if this flag is set, an event regarding the NF load is reported if the accompanying or pre-configured threshold is exceeded. Optional "Consideration on NF (e.g., UPF) load for event report" flag (Flag for considering the load for event reporting processing) Indicates to the Event provider NF if the threshold of NF load for event reporting is exceeded. Optionally, may imply to the Event provider NF to send a notification to the Event consumer NF if the threshold of NF load for event reporting is not exceeded. the notification to the Event consumer NF if the threshold of NF load for event report is not exceeded).When subscribing to events for reporting, if this flag is set, events regarding the NF load are reported when the provided or pre-configured threshold is exceeded. OptionalLoadThreshold The threshold value indicates conditions on the level to be reached for the consideration on NF (e.g., UPF) load. When requesting reporting for UPF performance consideration, reference values / levels may be provided. If this value is not provided separately, it may be assumed to be pre-configured. Alternatively, instead of defining a new threshold, a Reporting Threshold defined in the prior art may be utilized. Optional (see NOTE X) NOTE 5: This parameter is included only if the event reporting mode indicates reporting upon reaching the threshold. NOTE 7: If the requester includes "variable reporting periodicity," the reporting period changes based on the load of the NF service producer, etc. Otherwise, the reporting cycle is fixed. NOTE X: This parameter is included only with the "Consideration on NF (eg. UPF) load for event report" flag or the "Consideration on NF (eg. UPF) load for specific traffic processing" flag.

[0297] Based on an event notification (or event report) resulting from the aforementioned service operation, the network node may perform the network operation described in the first embodiment. For example, the network node may receive an event report (or notification) from the UPF. Based on this, the network may perform Section 3 (subsequent operation) of the first embodiment.

[0298] If the load exceeds a threshold and then returns to within the threshold range, the PCF may change the policy based on that status. For example, if the load exceeds the threshold and then returns to within the threshold range, the UPF can notify the SMF (or PCF). Based on this, the PCF can update the policy based on that status.

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

[0300] FIG. 7 shows an example of a flowchart of a second embodiment according to the disclosure of the present specification.

[0301] AF can request NF (or NEF) to subscribe to event exposures.

[0302] An NF (e.g., SMF) (or NEF) may request an event exposure subscription from the UPF. Such a request may include inputs from the aforementioned event exposure subscription service. For example, such a request may be a notification request for the load on the UPF for specific traffic (e.g., traffic related to the UPF) and / or the load on the UPF for event reporting.

[0303] UPF can start UPF's load check.

[0304] UPF can determine that its load (load for specific traffic) exceeds a threshold.

[0305] If the load of the UPF exceeds a threshold, the UPF may send an event report (notification) to the NF (e.g., SMF) (or NEF). The event report (notification) may include the output of the aforementioned event exposure subscription service.

[0306] The subsequent operation of NF (e.g., SMF) (or NEF) may be subject to Section 3 (subsequent operation) of the first embodiment.

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

[0308] - The first network node (e.g., AF) sends a request message to the core network node that directly or implicitly includes a request regarding specific traffic load management and event reporting guarantees. Based on the response corresponding to the request, the operation at the application service layer is modified.

[0309] - The second network control node (e.g., a network node such as SMF, AF, or PCF that intends to use UPF load or UPF event reporting information for network management) requests analytics information regarding load and event reporting for specific traffic from the NWDAF based on requests from other network nodes and third-party AS / AFs.

[0310] - A third network node (e.g., UPF) measures and reports the load regarding specific traffic and event reporting based on requests from other network nodes.

[0311] - The 4th network node (e.g., SMF) triggers the UPF reselection / relocation procedure based on analytics information received from NWDAF.

[0312] - Based on the request message received from the network through the above procedure, the terminal performs a PDU session management (modification, release / re-establishment, etc.) procedure for UP path setup.

[0313] - The 5th network node (e.g., PCF) updates the policy based on analytics information received from the NWDAF and sends the new policy to other network nodes and base stations / terminals.

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

[0315] FIG. 8 illustrates the procedure of the SMF for the disclosure of the present specification.

[0316] 1. An SMF (Session Management Function) may send a first message to an NF (Network Function) containing a request for information related to the load of specific traffic of a specific UPF (User Plane Function).

[0317] 2. The above SMF may receive a second message from the above NF containing information related to the load of the specific traffic.

[0318] 3. Based on information related to the load of the above UPF, the above SMF can determine the overload of the load of the specific traffic.

[0319] 4. Based on the above decision, the SMF can perform UPF reselection.

[0320] The information related to the load of the specific traffic may be information related to the load of the specific UPF for processing the specific traffic, or information related to the load of the specific UPF for processing event reporting related to the specific traffic.

[0321] The above SMF can receive messages related to an AF (Application Function) request.

[0322] The step of the above SMF transmitting the first message can be performed based on the message related to the AF request.

[0323] The above NF may be the above specific UPF.

[0324] The above first message can be transmitted to the specific UPF through an event exposure subscription request message.

[0325] The above second message can be received from the specific UPF through an event notification message.

[0326] The step of the SMF receiving the second message can be performed based on the load of the specific UPF exceeding a threshold.

[0327] The first message above may include information related to the threshold value.

[0328] The above NF may be NWDAF (Network Data Analytics Function).

[0329] The first message above can be transmitted to the NWDAF via an analytics request message.

[0330] The above second message can be received from the NWDAF through an analytics response message.

[0331] The above analytics response message may include statistical information on the load of the specific UPF for processing the specific traffic or statistical information on the load of the specific UPF for processing event reporting related to the specific traffic.

[0332] The above analytics response message may include predicted load information of the specific UPF for processing the specific traffic or predicted load information of the specific UPF for processing event reporting related to the specific traffic.

[0333] Based on the above decision, the SMF can send a policy control request trigger to the PCF (Policy Control Function).

[0334] The aforementioned specific traffic may be traffic related to AI (Artificial Intelligence) / ML (Machine Learning).

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

[0336] FIG. 9 illustrates the PCF procedure for the disclosure of the present specification.

[0337] 1. PCF can receive a first message from NF containing information related to the load of specific traffic for a specific UPF.

[0338] 2. The above PCF can update the policy related to the processing of the above specific traffic of the above specific UPF.

[0339] 3. The above PCF can provide the above updated policy.

[0340] Information related to the load of the specific traffic may be information related to the load of the specific UPF for processing the specific traffic, or information related to the load of the specific UPF for processing event reporting related to the specific traffic.

[0341] The above PCF can send an analytics request for the above specific traffic to NWDAF.

[0342] The above NF may be the above NWDAF.

[0343] Based on the above analytics request, the first message may include an analytics response message.

[0344] The step of updating the above policy can be performed based on the above analytics response message.

[0345] The above analytics response message may include statistical information on the load of the specific UPF for processing the specific traffic or statistical information on the load of the specific UPF for processing event reporting related to the specific traffic.

[0346] The above analytics response message may include predicted load information of the specific UPF for processing the specific traffic or predicted load information of the specific UPF for processing event reporting related to the specific traffic.

[0347] The above PCF can send an event exposure subscription request message to the above specific UPF.

[0348] The above NF may be the above specific UPF.

[0349] The step of receiving the first message above may be performed based on the fact that the load of the specific UPF exceeds a threshold.

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

[0351] FIG. 10 illustrates the procedure of UPF for the disclosure of the present specification.

[0352] 1. UPF can receive an event exposure subscription request message from NF.

[0353] The above event exposure subscription request message may include information related to the load of specific traffic of the above UPF.

[0354] 2. The above UPF can determine that the load of its specific traffic exceeds a threshold.

[0355] 3. Based on the above decision, the UPF may send an event notification message to the NF.

[0356] Information related to the load of the specific traffic may be information related to the load of the specific UPF for processing the specific traffic, or information related to the load of the specific UPF for processing event reporting related to the specific traffic.

[0357] The above event exposure subscription request message may include information related to the commercial threshold.

[0358] The above NF may be SMF, NEF (Network Exposure Function), or PCF.

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

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

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

[0362] The operation performed by the processor may include: a step in which a Session Management Function (SMF) transmits a first message to a Network Function (NF) containing a request for information regarding the load of specific traffic of a specific User Plane Function (UPF); a step in which the SMF receives a second message from the NF containing information regarding the load of the specific traffic; a step in which the SMF determines the overload of the load of the specific traffic based on the information regarding the load of the UPF; and a step in which the SMF performs UPF reselection based on the determination.

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

[0364] The operation performed by the processor may include: a step in which a Session Management Function (SMF) transmits a first message to a Network Function (NF) containing a request for information regarding the load of specific traffic of a specific User Plane Function (UPF); a step in which the SMF receives a second message from the NF containing information regarding the load of the specific traffic; a step in which the SMF determines the overload of the load of the specific traffic based on the information regarding the load of the UPF; and a step in which the SMF performs UPF reselection based on the determination.

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

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

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

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

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

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

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

[0372] One or more stored commands may include the steps of: a Session Management Function (SMF) transmitting a first message to a Network Function (NF) containing a request for information regarding the load of specific traffic of a User Plane Function (UPF); the SMF receiving a second message from the NF containing information regarding the load of specific traffic; and, based on the information regarding the load of the UPF, the SMF determining the overload of the load of specific traffic; and, based on the determination, the SMF performing UPF reselection.

[0373] This specification may have various effects.

[0374] For example, the UPF load can be appropriately adjusted through the procedure disclosed in this specification.

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

[0376] 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

1. As a method, A step in which an SMF (Session Management Function) transmits a first message to an NF (Network Function) containing a request for information related to the load of specific traffic of a specific UPF (User Plane Function); The step of the SMF receiving a second message from the NF containing information related to the load of the specific traffic; and A step in which the SMF determines the overload of the load of the specific traffic based on information related to the load of the UPF; A method comprising the step of the SMF performing UPF reselection based on the above decision.

2. In Paragraph 1, A method in which information related to the load of the specific traffic is information related to the load of the specific UPF for processing the specific traffic, or information related to the load of the specific UPF for processing event reporting related to the specific traffic.

3. In Paragraph 1 or 2, The above SMF further includes the step of receiving a message related to an AF (Application Function) request, and The step of the above SMF transmitting the above first message is performed based on the message related to the above AF request.

4. In any one of paragraphs 1 through 3, The above NF is the above specific UPF, and The above first message is transmitted to the specific UPF via an event exposure subscription request message, and The above second message is received from the above specific UPF through an event notification message.

5. In Paragraph 4, The step of the above SMF receiving the above second message is performed based on the load of the above specific UPF exceeding a threshold.

6. In Paragraph 5, The above first message is a method that includes information related to the threshold value.

7. In any one of paragraphs 1 through 3, The above NF is NWDAF (Network Data Analytics Function), and The first message above is transmitted to the NWDAF via an analytics request message, and The above second message is received from the above NWDAF via an analytics response message.

8. In Paragraph 7, A method in which the above analytics response message includes statistical information on the load of the specific UPF for processing the specific traffic or statistical information on the load of the specific UPF for processing event reporting related to the specific traffic.

9. In Paragraph 7, A method in which the above analytics response message includes predicted load information of the specific UPF for processing the specific traffic or predicted load information of the specific UPF for processing event reporting related to the specific traffic.

10. In any one of paragraphs 1 through 9, A method further comprising the step of the SMF transmitting a policy control request trigger to the PCF (Policy Control Function) based on the above decision.

11. In any one of paragraphs 1 through 10, A method in which the above specific traffic is traffic related to AI (Artificial Intelligence) / ML (Machine Learning).

12. As a method, A step in which the PCF receives a first message from the NF containing information related to the load for specific traffic of a specific UPF; The step of the PCF updating a policy related to the processing of the specific traffic of the specific UPF; and A method comprising the step of the above PCF providing the above updated policy.

13. In Paragraph 12, A method in which information related to the load of the specific traffic is information related to the load of the specific UPF for processing the specific traffic, or information related to the load of the specific UPF for processing event reporting related to the specific traffic.

14. In Paragraph 12 or 13, The above PCF further includes the step of sending an analytics request for the specific traffic to the NWDAF, and The above NF is the above NWDAF, and Based on the above analytics request, the first message includes an analytics response message, and The step of updating the above policy is: a method performed based on the above analytics response message.

15. In Paragraph 14, A method in which the above analytics response message includes statistical information on the load of the specific UPF for processing the specific traffic or statistical information on the load of the specific UPF for processing event reporting related to the specific traffic.

16. In Paragraph 14, A method in which the above analytics response message includes predicted load information of the specific UPF for processing the specific traffic or predicted load information of the specific UPF for processing event reporting related to the specific traffic.

17. In Paragraph 12 or 13, The above PCF further includes the step of sending an event exposure subscription request message to the above specific UPF, and The above NF is the above specific UPF, and The step of receiving the first message is performed based on the load of the specific UPF exceeding a threshold.

18. As a method, A step in which UPF receives an event exposure subscription request message from NF; The above event exposure subscription request message includes information related to the load of specific traffic of the above UPF, and The step of the above UPF determining that the load of its above-mentioned specific traffic exceeds a threshold; and A method comprising the step of the UPF sending an event notification message to the NF based on the above decision.

19. In Paragraph 18, A method in which information related to the load of the specific traffic is information related to the load of the specific UPF for processing the specific traffic, or information related to the load of the specific UPF for processing event reporting related to the specific traffic.

20. In Paragraph 18 or 19, A method in which the above event exposure subscription request message includes information related to the commercial threshold.

21. In any one of paragraphs 18 through 20, The above NF is a method in which it is an SMF, NEF (Network Exposure Function), or PCF.

22. As an SMF 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 an SMF that is a method according to any one of claims 1 to 11.

23. As a PCF 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 PCF which is a method according to any one of claims 12 to 17.

24. As a UPF performing communication, At least one transmitter / receiver; It includes at least one processor, The operation performed by the above at least one processor is a UPF, which is a method according to any one of claims 18 to 21.

Images