Method for managing a session

Abstract

One disclosure of the specification provides a method of a session management function (SMF) performing communication. The method includes the steps of: sending an analytics request message to a network data analytics function (NWDAF), the request message including a data network name (DNN) and single-network slice selection assistance information (S-NSSAI); receiving analytics from the NWDAF; determining a deactivation timer value based on the analytics; and sending the deactivation timer value to a user plane function (UPF).

Description

Technical Field

[0001] This manual relates to mobile communications. Background Technology

[0002] The 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) is a technology designed to enable high-speed packet communication. Numerous proposals have been put forward for LTE objectives, including those aimed at reducing costs for users and providers, improving quality of service, and expanding and improving coverage and system capacity. As upper-layer requirements, 3GPP LTE needs to reduce cost per bit, increase service availability, allow flexible use of frequency bands, have a simple architecture, open interfaces, and sufficient power consumption for terminals.

[0003] Requirements and specifications for New Radio (NR) systems have begun to be developed within the International Telecommunication Union (ITU) and 3GPP. 3GPP must identify and develop technical components that will be successfully standardized under the new RAT to meet both pressing market demands and the longer-term requirements outlined in the ITU Radiocommunication Sector (ITU-R) International Mobile Telecommunications (IMT)-2020 process. Furthermore, NR should be able to utilize any spectrum band, at least up to 100 GHz, that can be used for wireless communication even in the more distant future.

[0004] The goal of NR is to address all use cases, requirements, and deployment scenarios with a single technology framework, including enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable and low-latency communications (URLLC). NR should be inherently backward compatible. Summary of the Invention

[0005] Technical issues

[0006] If no data transmission occurs within a specific time period in a session (PDU session), the SMF can terminate the corresponding session. That is, the user plane connection for the corresponding session can be disabled. In this case, efficient communication requires correctly setting specific time periods for each session.

[0007] Technical solution

[0008] SMF can receive analysis from NWDAF and, based on this, determine the appropriate deactivation timer value suitable for the session.

[0009] Technical effect

[0010] This specification can have a variety of effects.

[0011] For example, through the procedures disclosed herein, SMF can determine appropriate inactivity timers for PDU sessions to efficiently manage user plane resources for optimized uptime.

[0012] The effects achievable through the specific examples in this specification are not limited to those listed above. For example, various technical effects may exist that can be understood or derived from this specification by one of ordinary skill in the art. Therefore, 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. Attached Figure Description

[0013] Figure 1 An example of a communication system that applies the implementation of this disclosure is shown.

[0014] Figure 2 An example of a wireless device that applies an implementation of the present disclosure is shown.

[0015] Figure 3 An example of a wireless device that applies an implementation of the present disclosure is shown.

[0016] Figure 4 An example of a UE that applies the implementation of this disclosure is shown.

[0017] Figure 5 An example of a 5G system architecture that applies the implementation of this specification is shown.

[0018] Figure 6 This indicates that the UP connection used for the PDU session is disabled.

[0019] Figure 7 This indicates that the UP timer is disabled.

[0020] Figure 8 This specification discloses the information presented herein.

[0021] Figure 9 The procedure of SMF as disclosed in this specification is shown.

[0022] Figure 10 The procedure for NWDAF as disclosed in this specification is shown. Detailed Implementation

[0023] The following technologies, devices, and systems can be applied to a variety of wireless multiple access systems. Examples of multiple access systems include Code Division Multiple Access (CDMA) systems, Frequency Division Multiple Access (FDMA) systems, Time Division Multiple Access (TDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single-Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Multi-Carrier Frequency Division Multiple Access (MC-FDMA) systems. CDMA can be implemented using radio technologies such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA can be implemented using radio technologies such as Global System for Mobile Communications (GSM), Universal Packet Radio Service (GPRS), or Enhanced Data Rate Evolution of GSM (EDGE). OFDMA can be implemented using radio technologies such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, or Evolved UTRA (E-UTRA). UTRA is part of the Universal Mobile Telecommunications System (UMTS). The 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) is part of the Evolved UMTS (E-UMTS) using E-UTRA. 3GPP LTE employs OFDMA in DL and SC-FDMA in UL. The evolution of 3GPP LTE includes LTE-A (Advanced), LTE-APro, and / or 5G NR (New Radio).

[0024] For ease of description, the implementation of this disclosure is primarily described with respect to 3GPP-based wireless communication systems. However, the technical features of this disclosure are not limited thereto. For example, although the following detailed description is given based on mobile communication systems corresponding to 3GPP-based wireless communication systems, the aspects of this disclosure, which are not limited to 3GPP-based wireless communication systems, are applicable to other mobile communication systems.

[0025] For any terms and techniques used in this disclosure that are not specifically described in this disclosure, please refer to previously published wireless communication standards documents.

[0026] In this disclosure, "A or B" may mean "A only", "B only", or "both A and B". In other words, "A or B" in this disclosure may be interpreted as "A and / or B". For example, "A, B or C" in this disclosure may mean "A only", "B only", "C only", or "any combination of A, B and C".

[0027] In this disclosure, a forward slash ( / ) or a comma can mean "and / or". For example, "A / B" can mean "A and / or B". Therefore, "A / B" can mean "A only", "B only", or "both A and B". For example, "A, B, C" can mean "A, B, or C".

[0028] In this disclosure, "at least one of A and B" may mean "only A", "only B" or "both A and B". Furthermore, the expressions "at least one of A or B" or "at least one of A and / or B" in this disclosure may be interpreted as the same as "at least one of A and B".

[0029] Additionally, in the disclosure, "at least one of A, B, and C" may mean "A only", "B only", "C only" 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".

[0030] Furthermore, the brackets used in this disclosure may mean "for example". Specifically, when shown as "Control Information (PDCCH)", "PDCCH" can be cited as an example of "Control Information". In other words, "Control Information" in this disclosure is not limited to "PDCCH", and "PDCCH" can be cited as an example of "Control Information". Additionally, even when shown as "Control Information (i.e., PDCCH)", "PDCCH" can be cited as an example of "Control Information".

[0031] The technical features described individually in one of the accompanying drawings of this disclosure may be implemented individually or simultaneously.

[0032] Not limited thereto, the various descriptions, functions, processes, suggestions, methods and / or operation flowcharts disclosed herein can be applied to various fields requiring wireless communication and / or connectivity between devices (e.g., 5G).

[0033] In the following description, this disclosure will be described in more detail with reference to the accompanying drawings. Unless otherwise indicated, the same reference numerals in the following drawings and / or description may denote the same and / or corresponding hardware blocks, software blocks and / or functional blocks.

[0034] Figure 1 An example of a communication system that applies the implementation of this disclosure is shown.

[0035] Figure 1 The 5G use cases shown are merely illustrative, and the technical features of this disclosure can be applied to... Figure 1 Other 5G use cases not shown.

[0036] The three main requirement categories for 5G include (1) Enhanced Mobile Broadband (eMBB), (2) Massive Machine-Type Communications (mMTC), and (3) Ultra-Reliable and Low-Latency Communications (URLLC).

[0037] Reference Figure 1 The communication system 1 includes wireless devices 100a to 100f, a base station (BS) 200, and a network 300. Although Figure 1 An example of a 5G network as a network of communication system 1 is shown, but the implementation of this disclosure is not limited to 5G systems and can be applied to future communication systems other than 5G systems.

[0038] BS 200 and network 300 can be implemented as wireless devices, and a particular wireless device can operate as a BS / network node relative to other wireless devices.

[0039] Wireless devices 100a to 100f represent devices that perform communication using radio access technology (RAT) (e.g., 5G New RAT (NR) or LTE) and may be referred to as communication / radio / 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, handheld 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 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 displays (HMDs), head-up displays (HUDs) installed in vehicles, televisions, smartphones, computers, wearable devices, home appliances, digital signage, vehicles, robots, etc. Handheld devices may include smartphones, smart tablets, wearable devices (e.g., smartwatches or smart glasses), and computers (e.g., laptops). Home appliances may include televisions, refrigerators, and washing machines. IoT devices may include sensors and smart meters.

[0040] In this disclosure, wireless devices 100a to 100f may be referred to as user equipment (UE). For example, a UE may include a cellular phone, smartphone, laptop computer, digital broadcasting terminal, personal digital assistant (PDA), portable multimedia player (PMP), navigation system, Slate PC, tablet PC, ultrabook, vehicle, vehicle with autonomous driving capability, connected car, UAV, AI module, robot, AR device, VR device, MR device, holographic device, public safety device, MTC device, IoT device, medical device, fintech device (or financial device), security device, weather / environment device, device related to 5G services, or device related to the Fourth Industrial Revolution.

[0041] For example, a UAV can be an aircraft that flies wirelessly via control signals without a crew.

[0042] For example, a VR device may include means for realizing objects or backgrounds in a virtual world. For example, an AR device may include means for connecting objects or backgrounds in a virtual world to objects or backgrounds in a real world. For example, a MR device may include means for incorporating objects or backgrounds in a virtual world into objects or backgrounds in a real world. For example, a holographic device may include means for recording and reproducing stereoscopic information using the light interference phenomenon produced when two lasers meet, known as holography, to create a 360-degree stereoscopic image.

[0043] For example, public safety devices may include image relay devices or image devices that can be worn on the user's body.

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

[0045] For example, a medical device can be a device for the purpose of diagnosing, treating, alleviating, treating, or preventing a disease. For example, a medical device can be a device for the purpose of diagnosing, treating, alleviating, or correcting an injury or trauma. For example, a medical device can be a device for the purpose of examining, replacing, or modifying a structure or function. For example, a medical device can be a device for regulating pregnancy. For example, a medical device may include a device for treatment, a device for operation, a device for (in vitro) diagnosis, a hearing aid, or a device for surgery.

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

[0047] For example, a fintech device can be a device capable of providing financial services such as mobile payments. For instance, a fintech device may include a payment device or a point-of-sale (POS) system.

[0048] For example, weather / environment devices may include devices for monitoring or predicting weather / environment.

[0049] Wireless devices 100a to 100f can connect to network 300 via BS 200. AI technology can be applied to wireless devices 100a to 100f, and wireless devices 100a to 100f can connect to AI server 400 via network 300. Network 300 can be configured using 3G, 4G (e.g., LTE), 5G (e.g., NR), and super 5G networks. Although wireless devices 100a to 100f can communicate with each other via BS 200 / network 300, wireless devices 100a to 100f can also perform direct communication with each other without going through BS 200 / network 300 (e.g., sidelink communication). For example, vehicles 100b-1 and 100b-2 can perform direct communication (e.g., vehicle-to-vehicle (V2V) / vehicle-to-everything (V2X) communication). IoT devices (e.g., sensors) can perform direct communication with other IoT devices (e.g., sensors) or other wireless devices 100a to 100f.

[0050] Wireless communication / connections 150a, 150b, and 150c can be established between wireless devices 100a to 100f and / or between wireless devices 100a to 100f and BS 200 and / or between BS 200. In this document, wireless communication / connections can be established via various RATs (e.g., 5G NR), such as uplink / downlink communication 150a, sidelink communication or device-to-device (D2D) communication 150b, inter-base station communication 150c (e.g., relay, integrated access and backhaul (IAB)), etc. Wireless devices 100a to 100f and BS 200 / wireless devices 100a to 100f can send / receive radio signals to each other via wireless communication / connections 150a, 150b, and 150c. For example, wireless communication / connections 150a, 150b, and 150c can send / receive signals via various physical channels. Therefore, at least a portion of the various configuration information configuration processes, various signal processing processes (e.g., channel coding / decoding, modulation / demodulation, and resource mapping / demapping), and resource allocation processes used for transmitting / receiving radio signals can be performed based on various proposals of this disclosure.

[0051] AI refers to the field of studying artificial intelligence or the methods that can create it, while machine learning refers to the field that defines the various problems solved within AI and the methods for solving them. Machine learning is also defined as algorithms that improve the performance of a task through stable experience with that task.

[0052] A robot is a machine that automatically processes or operates a given task through its own capabilities. In particular, robots capable of recognizing their environment and autonomously determining the actions they must perform can be called intelligent robots. Depending on their purpose or field of use, robots can be classified as industrial, medical, domestic, military, etc. Robots can perform various physical operations, such as moving their joints using actuators or motors. Mobile robots also include driven wheels, brakes, propellers, etc., allowing them to move on the ground or fly in the air.

[0053] Autonomous driving refers to the technology of driving itself, and autonomous vehicles refer to vehicles driven without user control or with minimal user control. For example, autonomous driving can include maintaining a lane while in motion, automatically adjusting speed (e.g., adaptive cruise control), driving automatically along a set route, and automatically setting a route when a destination is set. Vehicles encompass vehicles equipped with internal combustion engines, hybrid vehicles equipped with both internal combustion engines and electric motors, and electric vehicles equipped with electric motors, and can include trains, motorcycles, and automobiles. Autonomous vehicles can be considered as robots with autonomous driving capabilities.

[0054] Extended reality is collectively referred to as VR, AR, and MR. VR technology provides real-world objects and backgrounds solely through computer graphics (CG) images. AR technology provides virtual CG images on top of real-world object images. MR technology is a CG technique that combines virtual objects into the real world. MR technology is similar to AR technology in that it displays real and virtual objects together. However, the difference lies in that in AR technology, virtual objects serve as a supplementary form to real objects, while in MR technology, virtual and real objects are treated as equal entities.

[0055] NR supports multiple parameter sets (and / or multiple subcarrier spacings (SCS)) to support a variety of 5G services. For example, a 15kHz SCS can support wide areas in traditional cellular bands, while a 30kHz / 60kHz SCS can support dense urban areas, lower latency, and wider carrier bandwidth. A 60kHz or higher SCS can support bandwidths greater than 24.25GHz to overcome phase noise.

[0056] NR bands can be defined as two types of frequency ranges, namely FR1 and FR2. The numerical values ​​of the frequency ranges can vary. For example, the two types of frequency ranges (FR1 and FR2) can be shown in Table 1 below. For ease of explanation, in the frequency ranges used in NR systems, FR1 can mean "the range below 6 GHz" and FR2 can mean "the range above 6 GHz" and can be referred to as millimeter wave (mmW).

[0057] [Table 1]

[0058] FR1 450MHz-6000MHz 15, 30, 60kHz FR2 24250MHz-52600MHz 60, 120, 240kHz

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

[0060] [Table 2]

[0061] FR1 410MHz-7125MHz 15, 30, 60kHz FR2 24250MHz-52600MHz 60, 120, 240kHz

[0062] Here, the radio communication technologies implemented in the wireless devices of this disclosure may include narrowband Internet of Things (NB-IoT) technologies for low-power communication, as well as LTE, NR, and 6G. For example, NB-IoT technology may be an example of low-power wide-area network (LPWAN) technology, implemented in specifications such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the names mentioned above. Additionally and / or alternatively, the radio communication technologies implemented in the wireless devices of this disclosure may be based on LTE-M technology. For example, LTE-M technology may be an example of LPWAN technology and referred to by various names such as enhanced machine-type communication (eMTC). For example, LTE-M technology may be implemented in at least one of various specifications such as 1) LTE Cat 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-bandwidth limited (non-BL), 5) LTE-MTC, 6) LTE machine-type communication, and / or 7) LTE M, and is not limited to the names mentioned above. Additionally and / or alternatively, the radio communication technologies implemented in the wireless devices of this disclosure may include at least one of ZigBee, Bluetooth, and / or LPWAN, which take into account low-power communication, and may not be limited to the names mentioned above. For example, ZigBee technology may generate personal area networks (PANs) associated with small / low-power digital communication based on various specifications such as IEEE 802.15.4, and may be referred to by various names.

[0063] Figure 2 An example of a wireless device that applies an implementation of the present disclosure is shown.

[0064] Reference Figure 2 The first wireless device 100 and the second wireless device 200 can send / receive radio signals to / from external devices via various RATs (e.g., LTE and NR).

[0065] exist Figure 2 In this context, {first wireless device 100 and second wireless device 200} can correspond to Figure 1 At least one of {wireless devices 100a to 100f and BS 200}, {wireless devices 100a to 100f and wireless devices 100a to 100f} and / or {BS 200 and BS 200}.

[0066] The first wireless device 100 may include at least one transceiver (e.g., transceiver 106), at least one processing chip (e.g., processing chip 101), and / or one or more antennas 108.

[0067] The processing chip 101 may include at least one processor (e.g., processor 102) and at least one memory (e.g., memory 104). Figure 2 The image exemplarily illustrates that memory 104 is included within processing chip 101. Alternatively and / or alternatively, memory 104 may be located external to processing chip 101.

[0068] Processor 102 can control memory 104 and / or transceiver 106, and can be configured to implement the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts described in this disclosure. For example, processor 102 can process information in memory 104 to generate first information / signal, and then transmit a radio signal including the first information / signal via transceiver 106. Processor 102 can receive a radio signal including a second information / signal via transceiver 106, and then store the information obtained by processing the second information / signal in memory 104.

[0069] Memory 104 may be operatively connected to processor 102. Memory 104 may store various types of information and / or instructions. Memory 104 may store software code 105 that implements instructions that, when executed by processor 102, perform the descriptions, functions, procedures, suggestions, methods, and / or operation flowcharts disclosed in this disclosure. For example, software code 105 may implement instructions that, when executed by processor 102, perform the descriptions, functions, procedures, suggestions, methods, and / or operation flowcharts disclosed in this disclosure. For example, software code 105 may control processor 102 to execute one or more protocols. For example, software code 105 may control processor 102 to execute one or more layers of a radio interface protocol.

[0070] In this document, processor 102 and memory 104 may be part of a communication modem / circuit / chip designed to implement RAT (e.g., LTE or NR). Transceiver 106 may be connected to processor 102 and transmit and / or receive radio signals via one or more antennas 108. Each transceiver 106 may include a transmitter and / or a receiver. Transceiver 106 may be used interchangeably with a radio frequency (RF) unit. In this disclosure, first wireless device 100 may represent a communication modem / circuit / chip.

[0071] The second wireless device 200 may include at least one transceiver (e.g., transceiver 206), at least one processing chip (e.g., processing chip 201), and / or one or more antennas 208.

[0072] The processing chip 201 may include at least one processor (e.g., processor 202) and at least one memory (e.g., memory 204). Figure 2 The image exemplarily illustrates that memory 204 is included within processing chip 201. Alternatively and / or alternatively, memory 204 may be located external to processing chip 201.

[0073] Processor 202 can control memory 204 and / or transceiver 206, and can be configured to implement the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts described in this disclosure. For example, processor 202 can process information in memory 204 to generate third information / signal, and then transmit a radio signal including the third information / signal via transceiver 206. Processor 202 can receive a radio signal including a fourth information / signal via transceiver 106, and then store the information obtained by processing the fourth information / signal in memory 204.

[0074] Memory 204 may be operatively connected to processor 202. Memory 204 may store various types of information and / or instructions. Memory 204 may store software code 205 that implements instructions, which, when executed by processor 202, perform the descriptions, functions, procedures, suggestions, methods, and / or operation flowcharts disclosed in this disclosure. For example, software code 205 may implement instructions that, when executed by processor 202, perform the descriptions, functions, procedures, suggestions, methods, and / or operation flowcharts disclosed in this disclosure. For example, software code 205 may control processor 202 to execute one or more protocols. For example, software code 205 may control processor 202 to execute one or more layers of a radio interface protocol.

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

[0076] The hardware elements of wireless devices 100 and 200 will be described in more detail below. One or more protocol layers may be implemented by one or more processors 102 and 202, but are not limited thereto. For example, these one or more processors 102 and 202 may implement one or more layers (e.g., functional layers such as the Physical (PHY) layer, Media Access Control (MAC) layer, Radio Link Control (RLC) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Resource Control (RRC) layer, and Service Data Adaptation Protocol (SDAP) layer). These one or more processors 102 and 202 may generate one or more Protocol Data Units (PDUs) and / or one or more Service Data Units (SDUs) according to the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed in this disclosure. These one or more processors 102 and 202 may generate messages, control information, data, or information according to the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed in this disclosure. The one or more processors 102 and 202 may generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information, according to the descriptions, functions, procedures, suggestions, methods, and / or operation flowcharts disclosed in this disclosure, and provide the generated signals to the one or more transceivers 106 and 206. The one or more processors 102 and 202 may receive signals (e.g., baseband signals) from the one or more transceivers 106 and 206, and acquire PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods, and / or operation flowcharts disclosed in this disclosure.

[0077] The one or more processors 102 and 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. The one or more processors 102 and 202 may be implemented by hardware, firmware, software, or a combination thereof. As an 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), or one or more field-programmable gate arrays (FPGAs) may be included in the one or more processors 102 and 202. The descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed in this disclosure may be implemented using firmware or software, and the firmware or software may be configured to include modules, processes, or functions. Firmware or software configured to execute the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed in this disclosure may be included in the one or more processors 102 and 202 or stored in the one or more memories 104 and 204 to be driven by the one or more processors 102 and 202. The descriptions, functions, processes, suggestions, methods and / or operation flowcharts disclosed in this disclosure may be implemented using firmware or software in the form of code, commands and / or command sets.

[0078] The one or more memories 104 and 204 may be connected to the one or more processors 102 and 202 and store various types of data, signals, messages, information, programs, code, instructions, and / or commands. The one or more memories 104 and 204 may be configured with read-only memory (ROM), random access memory (RAM), electrically erasable programmable read-only memory (EPROM), flash memory, hard disk drive, registers, cache memory, computer-readable storage media, and / or combinations thereof. The one or more memories 104 and 204 may be located internally and / or externally to the one or more processors 102 and 202. The one or more memories 104 and 204 may be connected to the one or more processors 102 and 202 via various technologies such as wired or wireless connections.

[0079] The one or more transceivers 106 and 206 may transmit user data, control information, and / or radio signals / channels mentioned in the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed in this disclosure to one or more other devices. The one or more transceivers 106 and 206 may receive user data, control information, and / or radio signals / channels mentioned in the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed in this disclosure from one or more other devices. For example, the one or more transceivers 106 and 206 may be connected to the one or more processors 102 and 202 and transmit and receive radio signals. For example, the one or more processors 102 and 202 may perform control to enable the one or more transceivers 106 and 206 to transmit user data, control information, or radio signals to one or more other devices. The one or more processors 102 and 202 can perform control to enable the one or more transceivers 106 and 206 to receive user data, control information or radio signals from one or more other devices.

[0080] The one or more transceivers 106 and 206 may be connected to the one or more antennas 108 and 208, and the one or more transceivers 106 and 206 may be configured to transmit and receive user data, control information, and / or radio signals / channels mentioned in the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed in this disclosure through the one or more antennas 108 and 208. In this disclosure, the one or more antennas 108 and 208 may be multiple physical antennas or multiple logical antennas (e.g., antenna ports).

[0081] One or more transceivers 106 and 206 can convert received user data, control information, radio signals / channels, etc., from RF band signals to baseband signals so that the received user data, control information, radio signals / channels, etc., can be processed by one or more processors 102 and 202. One or more transceivers 106 and 206 can also convert user data, control information, radio signals / channels, etc., processed by one or more processors 102 and 202 from baseband signals to RF band signals. For this purpose, one or more transceivers 106 and 206 may include (analog) oscillators and / or filters. For example, one or more transceivers 106 and 206, under the control of one or more processors 102 and 202, can upconvert OFDM baseband signals to OFDM signals via their (analog) oscillators and / or filters, and transmit the upconverted OFDM signals at a carrier frequency. One or more transceivers 106 and 206 can receive OFDM signals at a carrier frequency and, under the control of one or more processors 102 and 202, down-convert the OFDM signals to OFDM baseband signals via their (analog) oscillators and / or filters.

[0082] In the implementation of this disclosure, the UE can operate as a transmitting device in the uplink (UL) and as a receiving device in the downlink (DL). In the implementation of this disclosure, the BS can operate as a receiving device in the UL and as a transmitting device in the DL. For ease of description, it is primarily assumed below that the first radio device 100 acts as the UE and the second radio device 200 acts as the BS. For example, a processor 102 connected to, installed on, or started in the first radio device 100 can be configured to perform UE behavior according to the implementation of this disclosure or control the transceiver 106 to perform UE behavior according to the implementation of this disclosure. A processor 202 connected to, installed on, or started in the second radio device 200 can be configured to perform BS behavior according to the implementation of this disclosure or control the transceiver 206 to perform BS behavior according to the implementation of this disclosure.

[0083] In this disclosure, BS is also referred to as Node B (NB), eNode B (eNB), or gNB.

[0084] Figure 3 An example of a wireless device that applies an implementation of the present disclosure is shown.

[0085] Wireless devices can be implemented in various forms depending on the usage / service (see reference) Figure 1 ).

[0086] Reference Figure 3Wireless devices 100 and 200 can correspond to Figure 2 The wireless devices 100 and 200 are configured with various elements, components, units / parts, and / or modules. For example, each of the wireless devices 100 and 200 may include a communication unit 110, a control unit 120, a memory unit 130, and an additional component 140. The communication unit 110 may include a communication circuit 112 and a transceiver 114. For example, the communication circuit 112 may include... Figure 2 One or more processors 102 and 202 and / or Figure 2 One or more memories 104 and 204. For example, transceiver 114 may include Figure 2 One or more transceivers 106 and 206 and / or Figure 2 One or more antennas 108 and 208. Control unit 120 is electrically connected to communication unit 110, memory unit 130, and add-on components 140 and controls the overall operation of each of the wireless devices 100 and 200. For example, control unit 120 may control the electromechanical operation of each of the wireless devices 100 and 200 based on programs / code / commands / information stored in memory unit 130. Control unit 120 may transmit information stored in memory unit 130 to an external source (e.g., other communication device) via communication unit 110 through a wireless / wired interface, or store information received from an external source (e.g., other communication device) via wireless / wired interface in memory unit 130 via communication unit 110.

[0087] The additional component 140 may be configured differently depending on the type of wireless devices 100 and 200. For example, the additional component 140 may include at least one of a power supply unit / battery, an input / output (I / O) unit (e.g., an audio I / O port, a video I / O port), a drive unit, and a computing unit. Wireless devices 100 and 200 may be configured according to the type of robot (…). Figure 1 100a), vehicles ( Figure 1 100b-1 and 100b-2), XR device ( Figure 1 100c), handheld device ( Figure 1 100d), home appliances ( Figure 1 100e), IoT devices ( Figure 1 100f), digital broadcasting terminals, holographic devices, public safety devices, MTC devices, medical devices, fintech devices (or financial devices), security devices, climate / environmental devices, AI servers / devices ( Figure 1 400), BS ( Figure 1 Wireless devices 100 and 200 can be implemented in the form of network nodes, etc., but are not limited to this. Depending on the use case / service, wireless devices 100 and 200 can be used in mobile or fixed locations.

[0088] exist Figure 3 In both wireless devices 100 and 200, all elements, components, units / parts, and / or modules can be connected to each other via wired interfaces, or at least some of them can be wirelessly connected via communication unit 110. For example, in each of wireless devices 100 and 200, control unit 120 and communication unit 110 can be wired connected, and control unit 120 and first units (e.g., 130 and 140) can be wirelessly connected via communication unit 110. The various elements, components, units / parts, and / or modules within wireless devices 100 and 200 may also include one or more elements. For example, control unit 120 may be configured as a collection of one or more processors. As an example, control unit 120 may be configured as a collection of communication control processors, application processors (APs), electronic control units (ECUs), graphics processing units, and memory control processors. As another example, memory unit 130 may be configured as RAM, DRAM, ROM, flash memory, volatile memory, non-volatile memory, and / or combinations thereof.

[0089] Figure 4 An example of a UE that applies the implementation of this disclosure is shown.

[0090] Reference Figure 4 UE 100 can correspond to Figure 2 The first wireless device 100 and / or Figure 3 Wireless devices 100 or 200.

[0091] UE 100 includes a processor 102, a memory 104, a transceiver 106, one or more antennas 108, a power management module 110, a battery 112, a display 114, a keypad 116, a subscriber identification module (SIM) card 118, a speaker 120, and a microphone 122.

[0092] Processor 102 may be configured to implement the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed in this disclosure. Processor 102 may be configured to control one or more other components of UE 100 to implement the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed in this disclosure. A layer of the radio interface protocol may be implemented in processor 102. Processor 102 may include an ASIC, other chipsets, logic circuits, and / or data processing means. Processor 102 may be an application processor. Processor 102 may include at least one of a digital signal processor (DSP), a central processing unit (CPU), a graphics processing unit (GPU), and a modem (modulator and demodulator). Examples of processor 102 can be found in […]. Manufacturing SNAPDRAGON TM Series processors EXYNOS manufactured TM Series processors A series of processors manufactured HELIO manufactured TM Series processors Manufactured ATOM TM This series of processors or the corresponding next-generation processors.

[0093] Memory 104 is operatively coupled to processor 102 and stores various information to operate processor 102. Memory 104 may include ROM, RAM, flash memory, memory card, storage medium, and / or other storage devices. When the implementation is software-based, the techniques described herein may be implemented using modules (e.g., procedures, functions, etc.) that execute the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed herein. Modules may be stored in memory 104 and executed by processor 102. Memory 104 may be implemented within or outside processor 102, in which case it may be communicatively coupled to processor 102 via various means known in the art.

[0094] Transceiver 106 is operatively coupled to processor 102 and transmits and / or receives radio signals. Transceiver 106 includes a transmitter and a receiver. Transceiver 106 may include baseband circuitry for processing radio frequency signals. Transceiver 106 controls one or more antennas 108 to transmit and / or receive radio signals.

[0095] The power management module 110 manages the power of the processor 102 and / or transceiver 106. The battery 112 supplies power to the power management module 110.

[0096] Display 114 outputs the results processed by processor 102. Keypad 116 receives inputs to be used by processor 102. Keypad 116 can be displayed on display 114.

[0097] The SIM card 118 is an integrated circuit designed to securely store the International Mobile Subscriber Identity (IMSI) number and its associated key used for identifying and authenticating subscribers on mobile devices such as mobile phones and computers. Contact information can also be stored on many SIM cards.

[0098] Speaker 120 outputs the sound-related results processed by processor 102. Microphone 122 receives sound-related inputs to be used by processor 102.

[0099] Figure 5 An example of a 5G system architecture that applies the implementation of this specification is shown.

[0100] The architecture of a 5G system (5GS; 5G system) consists of the following network functions (NFs).

[0101] -AUSF (Authentication Server Functionality)

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

[0103] -DN (Data Network), such as carrier services, internet access, or third-party services.

[0104] -USDF (Unstructured Data Storage Function)

[0105] -NEF (Network Exposure Feature)

[0106] -I-NEF (middle NEF)

[0107] -NRF (Network Repository Functionality)

[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 Device Identifier Register)

[0119] -NWDAF (Network Data Analysis Function)

[0120] -CHF (Billing Function)

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

[0122] -N3IWF (Non-3GPP interoperability function)

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

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

[0125] Figure 5 The diagram illustrates the architecture of a 5G system in a non-roaming scenario, represented using reference points, and shows how various network functions interact with each other.

[0126] exist Figure 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, Figure 5 The connections between the UDR and other NFs (e.g., PCFs) are not shown. For clarity, Figure 5 The connection between NWDAF and other NFs (e.g., PCF) is not shown.

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

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

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

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

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

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

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

[0135] The following reference points illustrate the interactions between NF services in 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 the two AMFs.

[0144] -N15: The reference point between the PCF and AMF in non-roaming scenarios, and the reference point between the PCF and AMF of the surveyed network in 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, it may be necessary to connect two NFs to each other to serve the UE.

[0148] <Disabling the UP connection used to establish the PDU session>

[0149] It can selectively enable and disable UP connections for existing PDU sessions.

[0150] A UE can establish multiple PDU sessions. Enabling the UP connection of an existing PDU session enables UE-CN user plane connectivity (i.e., data radio bearer and N3 tunnel).

[0151] For UEs in CM idle state within 3GPP access, the UE or network-triggered service request procedure can support the independent activation of UP connections for existing PDU sessions. For UEs in CM idle state within non-3GPP access, the UE-triggered service request procedure allows the reactivation of UP connections for existing PDU sessions and can support the independent activation of UP connections for existing PDU sessions.

[0152] A UE in CM connection state invokes a service request procedure to request the independent activation of the UP connection of an existing PDU session.

[0153] The network triggering of the UP connection of the existing PDU session will be re-enabled as follows.

[0154] - If the UE CM state in the AMF has already been CM connected on the access (3GPP, non-3GPP) of the PDU session associated with the SMF, the network can use the network-initiated service request procedure to re-enable the UP connection of the PDU session.

[0155] otherwise:

[0156] - If the UE is registered in both 3GPP access and non-3GPP access and the UE CM state in the AMF is CM idle in the non-3GPP access, then the PDU session associated (i.e., last routed) to the non-3GPP access in the SMF can be paged or notified to the UE via the 3GPP access.

[0157] - If the UE's CM state in the AMF is CM Idle in the 3GPP access, the paging message may include the access type associated with the PDU session in the SMF. Upon receiving a paging message containing the access type, the UE should reply to the 5GC via the 3GPP access using a NAS service request message. This NAS service request message should contain a list of PDU sessions associated with the received access type whose UP connection can be reactivated via 3GPP (i.e., based on the UE policy and whether the S-NSSAI of these PDU sessions is within the allowed NSSAI of the 3GPP access, this list does not include PDU sessions whose UP connection cannot be reactivated on 3GPP). If the PDU session that the UE has paged is in the list of PDU sessions provided in the NAS service request and the paging is triggered by pending DL data, the 5GC should reactivate the PDU session UP connection via the 3GPP access. If the paging is triggered by pending DL signaling, the service request succeeds without reactivating the PDU session UP connection via the 3GPP access, and pending DL signaling is transmitted to the UE via the 3GPP access.

[0158] - If the UE's CM state in the AMF is a CM connection in 3GPP access, the notification message should include a non-3GPP access type. Upon receiving the notification message, the UE should reply to the 5GC via 3GPP access using a NAS service request message. This NAS service request message should contain a list of allowed PDU sessions that can be re-enabled via 3GPP, or, if re-enabled PDU sessions via 3GPP access is not allowed, an empty list of allowed PDU sessions.

[0159] Note: Assume that a UE is within the coverage area of ​​a non-3GPP access and has a PDU session associated (i.e., last routed) to a non-3GPP access in the UE attempts to connect to it without paging.

[0160] - If a UE is registered in both a 3GPP access and a non-3GPP access served by the same AMF, and the UE's CM state in the AMF is CM idle in the 3GPP access and CM connected in the non-3GPP access, then the PDU session associated (i.e., last routed) to the 3GPP access in the SMF can be notified to the UE via the non-3GPP access. The notification message should include the 3GPP access type. Upon receiving the notification message, if the 3GPP access is available, the UE should reply to the 5GC via the 3GPP access using a NAS service request message.

[0161] In addition to the above, PDU sessions can be established as always-on PDU sessions.

[0162] Disabling the UP connection of an existing PDU session results in the deactivation of the corresponding data radio bearer and N3 tunnel. When the UE is in a CM connection state in 3GPP access or non-3GPP access, the UP connections of different PDU sessions can be deactivated independently. When the UP connection of a PDU session using an N9 tunnel controlled by the I-SMF is deactivated, the N9 tunnel is retained. If the PDU session is a normally open PDU session, the SMF should not deactivate the UP connection of that PDU session due to inactivity.

[0163] Figure 6 This indicates that the UP connection used for the PDU session is disabled.

[0164] The UP connection (i.e., data radio bearer and N3 tunnel) of the PDU session established by a UE in CM connection state can be disabled.

[0165] 1. The SMF can determine that the UP connection of a PDU session can be disabled under the following conditions.

[0166] - During the handover process, if all QoS flows of the PDU session are rejected by the target NG-RAN, or if the PDU session fails to be configured as indicated by the AMF, the SMF continues with steps 2 and 3, and steps 5 through 9 can be skipped;

[0167] -UPF can detect when a PDU session has not transmitted data during a specified inactivity period;

[0168] - For LADN PDU sessions, the AMF can notify the SMF that the UE has moved out of the LADN service area; or

[0169] -AMF can notify SMF that the UE has moved out of the permitted area.

[0170] The SMF may decide to release the UPF at the N3 termination point. In this case, the SMF continues with steps 2 and 3. Otherwise, if the SMF decides to keep the UPF at the N3 termination point, the SMF continues with step 4.

[0171] 2. The SMF can initiate an N4 session release procedure to release the intermediate UPF at the N3 endpoint. If multiple intermediate UPFs exist, this step can be performed for each UPF to be released. The SMF needs to initiate an N4 session modification procedure in step 3 to the UPF connected to the released UPF (i.e., the N9 endpoint or PDU session anchor).

[0172] 3. If the intermediate UPF at the N3 termination point is released in step 2, the SMF may initiate an N4 session modification procedure towards the UPF (PDU session anchor or another intermediate UPF) connected to the released UPF, indicating that the CN tunnel information of the N9 tunnel corresponding to the PDU session needs to be removed. In this case, based on the buffering instructions provided by the SMF, the UPF connected to the released UPF buffers the DL packets of the PDU session, discards the DL packets of the PDU session, or forwards the DL packets of the PDU session to the SMF. If the PDU session corresponds to an LADN and the UE moves out of the LADN service area, the SMF may notify the UPF connected to the released UPF to discard the downlink data of the PDU session and / or not provide further data notification messages.

[0173] Otherwise, the N4 session modification process can proceed toward the N3 termination point.

[0174] 4. If the UPF at the N3 termination point is not released in step 2, the SMF may initiate an N4 session modification procedure, indicating that the AN tunnel information of the N3 tunnel for the corresponding PDU session needs to be removed. In this case, based on the buffering instructions provided by the SMF, the UPF may buffer the DL packets of the PDU session, discard the DL packets of the PDU session, or forward the DL packets of the PDU session to the SMF. If the PDU session corresponds to an LADN and the UE moves out of the LADN service area, the SMF may instruct the UPF to discard the downlink data of the PDU session and / or not provide further data notification messages.

[0175] 5. The SMF calls the Namf_Communication_N1N2MessageTransfer service operation (PDU session ID, N2SM information (N2 resource release request (PDU session ID))) to release the NG-RAN resources associated with the PDU session.

[0176] 6. The AMF can send an N2 PDU session resource release command to the NG-RAN via N2, which includes the N2 SM information (N2 resource release request (PDU session ID)) received from the SMF.

[0177] 7. NG-RAN may issue NG-RAN-specific signaling exchanges with the UE (e.g., RRC connection reconfiguration) to release NG-RAN resources associated with the PDU session received from the AMF in step 5. When the user plane connection of the PDU session is released, the AS layer in the UE indicates it to the NAS layer.

[0178] If the UE is in an RRC inactive state, this step is skipped. When the UE changes from an RRC inactive state to an RRC connected state, the NG-RAN and the UE can synchronize the release of radio resources for the PDU sessions that have been deactivated.

[0179] 8. NG-RAN can confirm the N2 PDU session resource release command to AMF, including N2 SM resource release confirmation (user location information, auxiliary RAT usage data).

[0180] 9. The AMF can call the Nsmf_PDUSession_UpdateSMContext service operation (N2 SM information (auxiliary RAT usage data)) to confirm the Namf service received in step 5.

[0181] <Inactive Timer>

[0182] SMF can configure UPF to report inactivity by providing UPF with an inactivity timer for the PDU session during the N4 session establishment / modification process associated with the PDU session.

[0183] The value of the inactivity timer is related to the inactivity detection time, which defines the time at which time measurement stops when no packets are received. The inactivity timer associated with the inactivity detection time is restarted at the end of each transmitted packet.

[0184] Figure 7 This indicates that the UP timer is disabled.

[0185] The UP inactivity timer can include the number of seconds of inactivity monitored by the UP function (i.e., UPE).

[0186] The user plane inactivity timer IE contains the number of seconds of inactivity monitored by the UP function.

[0187] The user plane inactivity timer field should be encoded as an Unsigned32 binary integer value. A timer value of "0" should be interpreted as an indication that user plane inactivity detection and reporting has stopped.

[0188] <Problems to be solved in the disclosure of this specification>

[0189] If the inactivity timer provided by the SMF is not suitable for the PDU session—for example, if the UPF takes too long to detect PDU session inactivity relative to the communication pattern of the PDU session—the PDU session may become inactive, and UP resources (i.e., data radio bearers and N3 tunnels) may be unnecessarily allocated even if there is no data transmission for a period of time. Additionally, because enabled PDU sessions must be handled during handover scenarios, UPF reallocation may be necessary. This handover process for the PDU session may not be required when there is no data transmission for a period of time due to PDU session inactivity.

[0190] <Disclosure of this specification>

[0191] The disclosures described later in this specification can be implemented in one or more combinations (e.g., combinations including at least one of those described below). The various figures illustrate embodiments of the respective disclosures, but the embodiments in the figures can be combined with each other.

[0192] The description of the methods disclosed in this specification may include a combination of one or more operations / configurations / steps described below. The methods described below may be performed or used in combination or complementarily.

[0193] The following figures are used to illustrate specific examples of this specification. Since the names of specific devices or signals / messages / fields described in the figures are provided as examples, the technical features of this specification are not limited to the specific names used in the figures below.

[0194] It can be argued that SMF's determination of appropriate inactivity timers for PDU sessions will help efficiently manage user plane resources, thereby leading to UP optimization.

[0195] In the proposed solution, the SMF can use the UE communication analysis output of the NWDAF to selectively disable the CN-initiated UP connection of the existing PDU session.

[0196] That is, the SMF can determine i) whether the inactivity of the PDU session established by the UPF using the output report of the UE communication analysis is configured, and ii) if a report is required, the inactivity timer of the PDU session provided to the UPF.

[0197] Figure 8 This illustrates the disclosure in this specification.

[0198] 1. The SMF can request or subscribe to UE communication analysis provided by NWDAF. The `Nnwdaf_AnalyticsInfo_Request` can be used for this request, and the `Nnwdaf_AnalyticsSubscription_Subscribe` can be used for this subscription.

[0199] Messages sent for requests or subscriptions may include analytics filtering information and analytics report target information. DNN and S-NSSAI information may be included in the message as analytics filtering information. A UE information (i.e., SUPI) or UE group information (i.e., internal group identifier) ​​may be included in the message as analytics report target information. Messages sent for the above requests or subscriptions may include region of interest information.

[0200] The messages sent for the above requests or subscriptions may include requests for predictions or statistics as output of the analysis.

[0201] 2a-b. To provide the requested analysis, the NWDAF may subscribe to a service from the SMF that provides information related to UE communications. The Nsmf_EventExposure_Subscribe service can be used for subscription. The information provided from the SMF may include the information in Table 3.

[0202] [Table 3]

[0203] UE ID SUPI Group ID Internal group ID S-NSSAI Information identifying network slices DNN Data network name providing PDU connectivity services Application ID Identify the application that provides this information. UE communication (1..max) Communication description for each application Communication begins The timestamp of when the communication started >Communication stopped The timestamp of when the communication stopped UL data rate The UL data rate of this communication DL data rate The DL data rate of this communication Business volume The traffic volume of this communication

[0204] 2c-d. To provide the requested analysis, NWDAF can subscribe to a service that provides information related to Type Assignment Codes (TACs) from the AMF. Namf_EventExposure_Subscribe can be used for this subscription.

[0205] TAC information may include terminal model and terminal manufacturer information. The reason for providing TAC information from the AMF is that UEs with the same TAC information may have similar communication types.

[0206] 3. NWDAF can calculate the requested analysis. In step 1, if the SMF requests statistical output, the UE communication analysis calculated above is statistical information. If the SMF requests predictive output in step 1, the UE communication analysis calculated above is predictive information.

[0207] 4. The NWDAF can provide UE communication analysis to the SMF. If an Nnwdaf_AnalyticsInfo_Request is received from the SMF in step 1, the NWDAF can provide analysis information to the SMF via Nnwdaf_AnalyticsInfo_Response. If an Nnwdaf_AnalyticsSubscription_Subscribe is received from the SMF in step 1, the NWDAF can provide analysis information to the SMF via Nnwdaf_AnalyticsSubscription_Notify.

[0208] If the UE communication analysis output / information provided by NWDAF to SMF is statistical information, it may include the information in Table 4.

[0209] [Table 4]

[0210]

[0211]

[0212] If the UE communication analysis output / information provided by NWDAF to SMF is predictive information, it may include the information in Table 5.

[0213] [Table 5]

[0214]

[0215] 5. The SMF can determine the inactivity timer value to be provided to the UPF for a PDU session based on the UE communication analysis output / information received from the NWDAF. This decision may include whether to configure the UPF to report inactivity of the PDU session or whether to stop the UPF from reporting inactivity of the PDU session. By setting the inactivity timer value to 0, the SMF can configure the UPF not to report inactivity or to stop it.

[0216] SMF can determine whether to designate a PDU session as a normally open PDU session based on the UE communication analysis output / information received from NWDAF.

[0217] A PDU session is a DNN / S-NSSAI PDU session included in the NWDAF output.

[0218] PDU sessions can be targeted at a specific UE or a specific group of UEs.

[0219] PDU sessions can be enabled in specific areas (cells, TAs, UPF service areas, etc.).

[0220] For example, if UE communication related to S-NSSAI / DNN (i.e., the communication characteristics / patterns of PDU sessions related to S-NSSAI / DNN) is periodic and has a long period, the inactivity timer for the corresponding PDU session is determined to be a smaller value. By providing this to the UPF, the UPF can detect inactivity shortly after communication terminates and report it to the SMF. As another example, if UE communication related to S-NSSAI / DNN is not periodic, the inactivity timer for the corresponding PDU session can be determined to be a larger value and provided to the UPF. This is to prevent premature deactivation of the PDU session's user plane due to the UPF reporting inactivity when the inactivity timer is set to a smaller value and provided to the UPF. As another example, if the period of UE communication related to S-NSSAI / DNN is very short, the UPF can be configured not to report inactivity or to stop.

[0221] 6-8. If NWDAF receives Nnwdaf_AnalyticsSubscription_Subscribe from SMF in step 1, NWDAF can calculate a new analysis based on information provided from SMF and / or AMF (the information described in step 2). Furthermore, the newly calculated analysis information can be provided to SMF via Nnwdaf_AnalyticsSubscription_Notify.

[0222] 9. Same as the above 5 steps.

[0223] When the SMF determines the inactivity timer value for a PDU session, the SMT can provide it to the UPF. This provision can be performed during the PDU session establishment or modification process.

[0224] As described above, when SMF performs UP (User Plane) optimization using NWDAF analysis, it can extend and use UE communication analysis, and can use other analyses (e.g., UE mobility analysis, user data congestion analysis) in conjunction with or in addition to UE communication analysis.

[0225] When SMF subscribes to or requests NWDAF analysis for UP optimization, it can always do so, or it can be done based on various conditions / reasons as shown below. However, subscriptions / requests can be performed based on a variety of situations and are not limited to this.

[0226] - RAN congestion information (e.g., notification information received from NG-RAN according to QNC (QoS Notification Control))

[0227] - Handover results (e.g., PDU session / QoS flow accepted and PDU session / QoS flow rejected during handover).

[0228] - When SMF determines that the number of PDU sessions created or released has reached a threshold for a specific DNN / S-NSSAI and / or in a specific region.

[0229] Figure 9 The procedure of SMF as disclosed in this specification is shown.

[0230] 1. SMF can send a message requesting analysis to NWDAF.

[0231] The requested analysis could be UE communication analysis.

[0232] The message may include DNN and S-NSSAI. DNN and S-NSSAI may be associated with a specific session (PDU session).

[0233] Analysis request messages may include Subscription Permanent Identifier (SUPI) information, internal group identifier information, and region of interest information.

[0234] 2. SMF can be received and analyzed from NWDAF.

[0235] This analysis can be related to the specific session described in step 1 above.

[0236] 3. SMF can determine the value of the timer that is not enabled based on analysis.

[0237] Inactive timer values ​​can be session-specific. Appropriate inactive timer values ​​can be set to suit the characteristics of the session.

[0238] The timer value can be zero if it is not enabled.

[0239] 4. The SMF can send a disabled timer value to the UPF.

[0240] When there is no data transmission for a specific session within the time corresponding to the inactivity timer value, the UPF can detect this and notify the SMF.

[0241] When the SMF detects that there is no data transmission for a specific session within the time period corresponding to the inactive timer value, the SMF can terminate that specific session (i.e., disable the UP connection).

[0242] SMF can receive new analyses from NWDAF.

[0243] New disabled timer values ​​can be determined based on the new analysis.

[0244] New disabled timer values ​​can be sent via UPF.

[0245] Figure 10 The procedure for NWDAF as disclosed in this specification is shown.

[0246] 1. NWDAF can receive messages requesting analysis from SMF.

[0247] The requested analysis could be UE communication analysis.

[0248] Analysis request messages may include DNN and S-NSSAI. DNN and S-NSSAI may be associated with a specific session (PDU session).

[0249] Analysis request messages may include Subscription Permanent Identifier (SUPI) information, internal group identifier information, and region of interest information.

[0250] 2. The NWDAF can receive information for analysis from at least one SMF.

[0251] The NWDAF can request information for analysis from at least one SMF and receive it as a response. The SMF in step 1 can correspond to one of at least one SMF.

[0252] 3. NWDAF can receive TAC information from AMF.

[0253] 4. NWDAF can generate analyses based on the information used for analysis and TAC information.

[0254] 5. NWDAF can send the generated analysis to the SMF that requested the analysis.

[0255] NWDAF can receive information for new analysis from at least one SMF.

[0256] NWDAF can receive new TAC information from AMF.

[0257] NWDAF can create new analyses based on information used for new analyses and new TAC information.

[0258] NWDAF can send new analyses to SMF.

[0259] This instruction manual can have various effects.

[0260] For example, through the procedures disclosed herein, SMF can determine appropriate inactivity timers for PDU sessions to efficiently manage user plane resources and provide optimized UP.

[0261] The effects achievable through the specific examples in this specification are not limited to those listed above. For example, various technical effects may exist that can be understood or derived from this specification by one of ordinary skill in the art. Therefore, 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.

[0262] The claims set forth herein can be combined in various ways. For example, the technical features of the method claims in this specification can be combined to implement an apparatus, and the technical features of the apparatus claims in this specification can be combined to implement a method. Furthermore, the technical features of the method claims and the apparatus claims in this specification can be combined to implement an apparatus, and the technical features of the method claims and the apparatus claims in this specification can be combined to implement a method. Other implementations are within the scope of the following claims.

Claims

1. A method for analyzing communications targeting a user equipment (UE), the method comprising the following steps: The Session Management Function (SMF) sends an analysis request for the UE's communications to the Network Data Analysis Function (NWDAF). The analysis request includes the data network name DNN and single network slice selection assistance information S-NSSAI. The analysis request includes requests for statistics or prediction regarding the UE's communications. The SMF receives and analyzes communications for the UE from the NWDAF based on the request; The analysis request includes the request for statistics, and the received analysis includes statistics on the communications of the UE. Wherein, the analysis request includes the request for prediction, and the received analysis includes predictions of the UE's communications. The analysis request includes the request for statistics or prediction, and the received analysis includes information indicating whether the UE communicates periodically. The SMF determines the value of the inactivity timer for the Packet Data Unit (PDU) session based on the received analysis; and The inactivity timer value is sent by the SMF to the User Plane Function (UPF).

2. The method according to claim 1, in, The communication of the UE is periodic, and the received analysis includes the interval between periodic communications.

3. The method according to claim 1, in, The analysis request includes subscribing to permanent identifier SUPI information or internal group identifier information.

4. The method according to claim 1, in, The analysis request includes information about the region of interest.

5. The method according to claim 1, in, The steps to determine the value of the inactive timer are as follows: The SMF sets the value of the inactivity timer to 0 to either i) configure the UPF not to report inactivity or ii) cause the UPF to stop reporting inactivity.

6. The method according to claim 1, further comprising the following step: Based on the fact that no data transmission occurred in the PDU session corresponding to the DNN and the S-NSSAI within the time period of the inactivity timer, the SMF receives a message from the UPF indicating that no data transmission occurred in the PDU session within the time period of the inactivity timer. as well as The SMF disables the PDU session.

7. The method according to claim 1, further comprising the following step: The SMF receives new analysis from the NWDAF; The SMF determines a new value for the inactive timer based on the received new analysis; as well as The SMF sends a new value for the inactive timer to the UPF.

8. A method for analyzing communications of a user equipment (UE), the method comprising the following steps: The Network Data Analysis Function (NWDAF) receives an analysis request for the UE's communications from the Session Management Function (SMF). The analysis request includes the data network name DNN and single network slice selection assistance information S-NSSAI. The analysis request includes requests for statistics or prediction regarding the UE's communications. The NWDAF receives, based on the request, information for analysis of communications to the UE from at least one SMF; The NWDAF receives information about the Type Assignment Code (TAC) from the Access and Mobility Management Function (AMF). The NWDAF generates an analysis for the inactive timer based on the information used for analysis and the information about the TAC; and The analysis is sent from the NWDAF to the SMF. The analysis request includes the request for statistics, and the analysis includes statistics on the communications of the UE. The analysis request includes the request for prediction, and the analysis includes prediction of the UE's communications. The analysis request includes the request for statistics or prediction, and the analysis sent includes information indicating whether the UE communicates periodically.

9. The method according to claim 8, in, The analysis includes the intervals between periodic communications, since the UE's communication is periodic.

10. The method according to claim 8, in, The analysis request includes subscribing to permanent identifier SUPI information or internal group identifier information.

11. The method according to claim 8, in, The analysis request includes information about the region of interest.

12. The method according to claim 8, in, The value of the inactivity timer will be 0 to either i) configure the User Plane Function (UPF) not to report inactivity or ii) cause the UPF to stop reporting inactivity.

13. The method of claim 8, further comprising the step of: The NWDAF receives information for new analysis from the at least one SMF; The NWDAF receives information about the new TAC from the AMF; The NWDAF generates a new analysis for the inactive timer based on information for the new analysis and information about the new TAC; as well as The new analysis is sent from the NWDAF to the SMF.

Images