Communications related to congestion control

Abstract

A disclosure of the specification provides a method for performing communication related to congestion control through an SMF. The method may include the following steps: sending a request message requesting SMCCE analysis to an NWDAF; and receiving a response message including SMCCE analysis information from the NWDAF in response to the request message.

Description

Technical Field

[0001] The present disclosure relates to mobile communications. Background Art

[0002] 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) is a technology for achieving high-speed packet communications. Many schemes have been proposed for LTE goals, including schemes aimed at reducing user and provider costs, improving service quality, and expanding and improving coverage and system capacity. 3GPP LTE requires reduced cost per bit, increased service availability, flexible use of frequency bands, simple structure, open interfaces, and sufficient power consumption of terminals as upper layer requirements.

[0003] Work has already begun in the International Telecommunications Association (ITU) and 3GPP to develop requirements and specifications for the development of new radio (NR) systems. 3GPP must identify and develop the technical components required to successfully standardize new RATs in a timely manner to meet both the immediate market needs and the longer-term requirements of the ITU Radiocommunication Sector (ITU-R) International Mobile Telecommunications (IMT)-2020 process. In addition, NR should be able to use any spectrum band in the range of at least up to 100 GHz that can be used for wireless communications even in the more distant future.

[0004] NR aims at a single technology framework to address all use cases, requirements and deployment scenarios including enhanced mobile broadband (eMBB), massive machine type communications (mMTC), ultra-reliable and low-latency communications (URLLC), etc. NR should be inherently forward compatible.

[0005] Meanwhile, congestion control can be applied to the communication between the terminal and the network. For example, a network node (e.g., SMF, AMF, etc.) can apply congestion control when the communication is congested. In this case, the network node can provide a backoff timer to the terminal to which congestion control is applied. On the other hand, the network node does not store information about the backoff timer provided by the network node. Therefore, fairness issues may arise for the terminal to which congestion control is applied. For example, a network node can continuously provide a backoff timer with a long time value to a specific terminal, and can provide a backoff timer with a short time value to other terminals. In a case such as this example, fairness issues between terminals may occur. When congestion control is applied, a method for solving fairness issues between terminals is needed. Summary of the invention

[0006] Technical issues

[0007] Therefore, the disclosure of this specification has been made in order to solve the above-mentioned problems.

[0008] Technical Solution

[0009] In order to solve the above problem, a disclosure of this specification provides a method for SMF to perform congestion control related communication. The method includes: sending a request message for requesting SMCCE analysis to NWDAF; and receiving a response message including SMCCE analysis information from NWDAF in response to the request message.

[0010] In order to solve the above problems, a disclosure of the present specification provides an SMF for performing communications related to congestion control. The SMF includes: at least one processor; and at least one memory, the at least one memory storing instructions and being operably connected to the at least one processor, wherein the operations performed based on the instructions executed by the at least one processor include: sending a request message requesting SMCCE analysis to NWDAF; and receiving a response message including SMCCE analysis information from the NWDAF in response to the request message.

[0011] In order to solve the above problems, a disclosure of this specification provides a method for NWDAF to perform congestion control related communication. The method includes: receiving a request message for requesting analysis of session management congestion control experience from the SMF; and sending a response message including SMCCE analysis information to the SMF in response to the request message.

[0012] In order to solve the above problem, a disclosure of the present specification provides a NWDAF for performing communications related to congestion control. The NWDAF includes: at least one processor; and at least one memory, the at least one memory storing instructions and being operably connected to the at least one processor, wherein the operations performed based on the instructions executed by the at least one processor include: receiving a request message from the SMF requesting analysis of the session management congestion control experience; and in response to the request message, sending a response message including SMCCE analysis information to the SMF.

[0013] Beneficial Effects

[0014] According to the disclosure of this specification, the problems of the related art can be solved.

[0015] The effects that can be obtained through the specific examples of this specification are not limited to the above-mentioned effects. For example, there may be various technical effects that can be understood by ordinary technicians in the relevant field or obtained from this specification. Therefore, the specific effects of this specification are not limited to those effects explicitly described herein, and may include various effects that can be understood or derived from the technical features of this specification. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] Figure 1 An example of a communication system to which an embodiment of the present disclosure is applied is shown.

[0017] Figure 2 An example of a wireless device to which an embodiment of the present disclosure is applied is shown.

[0018] Figure 3 An example of a wireless device to which an embodiment of the present disclosure is applied is shown.

[0019] Figure 4 It is a structural diagram of the next generation mobile communication network.

[0020] Figure 5 is an example diagram showing the predicted structure of the next generation of mobile communications from the perspective of nodes.

[0021] Figure 6 is an exemplary diagram showing an architecture that allows a UE to access two data networks simultaneously using one PDU session.

[0022] Figure 7 An example of UE data according to an embodiment disclosed in this specification is shown.

[0023] Figure 8 A first example of SMCCE analysis according to an embodiment disclosed in this specification is shown.

[0024] Fig. 9 A second example of SMCCE analysis according to an embodiment disclosed in this specification is shown.

[0025] Fig.10 An example of a process according to an embodiment disclosed in this specification is shown.

[0026] Fig.11 An example of the operation of a network according to an embodiment disclosed in this specification is shown.

[0027] Fig.12 An example of operations of a terminal and a network according to an embodiment disclosed in this specification is shown. DETAILED DESCRIPTION

[0028] The following techniques, devices and systems can be applied to various wireless multiple access systems. Examples of multiple access systems include code division multiple access (CDMA) systems, frequency division multiple access (FDMA) systems, time division multiple access (TDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and multi-carrier frequency division multiple access (MC-FDMA) systems. CDMA can be implemented by radio technologies such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA can be implemented by radio technologies such as Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), or Enhanced Data Rate for GSM Evolution (EDGE). OFDMA can be implemented by radio technologies such as Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE802.16 (WiMAX), IEEE 802.20, or Evolved UTRA (E-UTRA). UTRA is part of Universal Mobile Telecommunications System (UMTS). 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) is a part of Evolved UMTS (E-UMTS) using E-UTRA. 3GPP LTE adopts OFDMA in DL and SC-FDMA in UL. The evolution of 3GPP LTE includes LTE-A (Advanced), LTE-A Pro and / or 5G NR (New Radio).

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

[0030] For terms and techniques not specifically described among the terms and techniques used in the present disclosure, reference may be made to wireless communication standard documents published prior to the present disclosure.

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

[0032] In the present disclosure, a slash ( / ) or a comma (,) may mean "and / or". For example, "A / B" may mean "A and / or B". Thus, "A / B" may mean "only A", "only B", or "both A and B". For example, "A, B, C" may mean "A, B, or C".

[0033] In the present disclosure, "at least one of A and B" may mean "only A", "only B", or "both A and B". In addition, the expression "at least one of A or B" or "at least one of A and / or B" in the present disclosure may be interpreted as being the same as "at least one of A and B".

[0034] In addition, in the present disclosure, "at least one of A, B, and C" may mean "only A", "only B", "only C", or "any combination of A, B, and C". In addition, "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".

[0035] In addition, the brackets used in the present disclosure may mean "for example". Specifically, when it is shown as "control information (PDCCH)", "PDCCH" may be proposed as an example of "control information". In other words, the "control information" in the present disclosure is not limited to "PDCCH", and "PDCCH" may be proposed as an example of "control information". In addition, even when it is shown as "control information (ie, PDCCH)", "PDCCH" may be proposed as an example of "control information".

[0036] The technical features described separately in one drawing of the present disclosure may be implemented separately or simultaneously.

[0037] Although not limited thereto, the various descriptions, functions, processes, suggestions, methods and / or operational flowcharts of the present disclosure disclosed herein may be applied to various fields requiring wireless communication and / or connection between devices (e.g., 5G).

[0038] Hereinafter, the present disclosure will be described in more detail with reference to the accompanying drawings. Unless otherwise specified, the same reference numerals in the following drawings and / or descriptions may refer to the same and / or corresponding hardware blocks, software blocks and / or functional blocks.

[0039] In the accompanying drawings, for example, a user equipment (UE) is shown. UE can also be represented as a terminal or a mobile equipment (ME). In addition, UE can be a laptop computer, a mobile phone, a PDA, a smart phone, a multimedia device or other portable device, or can be a fixed device such as a PC or a vehicle-mounted device.

[0040] In the following, UE is used as an example of a wireless communication device (or wireless device or wireless equipment) capable of wireless communication. The operation performed by the UE may be performed by the wireless communication device. The wireless communication device may also be referred to as a wireless device, a wireless device, etc. In the following, AMF may mean an AMF node, SMF may mean an SMF node, and UPF may mean a UPF node.

[0041] The term "base station" used below generally refers to a fixed station that communicates with wireless devices, and may be represented by other terms such as evolved Node B (e Node B), evolved Node B (eNB), base transceiver system (BTS), access point or next generation Node B (gNB).

[0042] I. Disclosed Techniques and Processes Applicable to This Specification

[0043] Figure 1 An example of a communication system to which an embodiment of the present disclosure is applied is shown.

[0044] Figure 1 The 5G usage scenarios shown in are only exemplary, and the technical features of the present disclosure can be applied to Figure 1 Other 5G usage scenarios not shown.

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

[0046] Some use cases may require multiple categories for optimization, and others may focus only on key performance indicators (KPIs). 5G supports these various use cases with a flexible and reliable approach.

[0047] eMBB goes far beyond basic mobile Internet access and covers a large number of two-way work in the cloud and augmented reality as well as media and entertainment applications. Data is one of the core driving forces of 5G, and in the 5G era, dedicated voice services may not be provided for the first time. In 5G, it is expected that the data connection provided by the communication system will be used as an application to simply process voice. The main reason for the increase in traffic is due to the increase in content size and the increase in the number of applications that require high data transmission rates. As more devices are connected to the Internet, streaming services (audio and video), conversational video, and mobile Internet access will be more widely used. These many applications require connectivity in an always-on state to push real-time information and alerts to users. Cloud storage and applications are rapidly increasing in mobile communication platforms and can be applied to both work and entertainment. Cloud storage is a special use case that accelerates the growth of uplink data transmission rates. 5G is also used for remote cloud work. When using a tactile interface, 5G requires lower end-to-end latency to maintain a good experience for users. Entertainment (e.g., cloud games and video streaming) is another core element that increases the demand for mobile broadband capabilities. Entertainment is essential for smartphones and tablets anywhere, including in high mobility environments such as trains, vehicles and airplanes. Other use cases are augmented reality for entertainment and information search. In this case, augmented reality requires very low latency and instantaneous data volume.

[0048] Additionally, one of the most anticipated 5G use cases involves the ability to smoothly connect embedded sensors in all fields (i.e., mMTC). The number of potential Internet of Things (IoT) devices is expected to reach 20.4 billion by 2020. Industrial IoT is one of the categories that plays a major role in enabling smart cities, asset tracking, smart utilities, agriculture, and security infrastructure through 5G.

[0049] URLLC includes new services that will transform industries (e.g., autonomous vehicles) through remote control of key infrastructure and ultra-reliable / available low-latency links. To control smart grids, automate industry, enable robotics, and control and regulate drones, the level of reliability and latency is critical.

[0050] 5G is a means of providing streaming services estimated at a few hundred megabits per second to a gigabit per second, and can complement fiber to the home (FTTH) and cable-based broadband (or DOCSIS). Such fast speeds are needed to deliver 4K or higher (6K, 8K and higher) resolution TV as well as virtual reality and augmented reality. Virtual reality (VR) and augmented reality (AR) applications include virtually immersive sports games. Specific applications may require special network configurations. For example, for VR games, gaming companies need to merge core servers into network operators' edge network servers to minimize latency.

[0051] Along with many use cases for mobile communications for vehicles, it is expected that cars will become a new important driving force in 5G. For example, the entertainment of passengers requires high simultaneous capacity and mobile broadband with high mobility. This is because future users continue to expect high-quality connections regardless of their location and speed. Another use case in the automotive field is the AR dashboard. The AR dashboard allows the driver to identify objects in the dark in addition to the objects seen from the front window, and displays the distance to the object and the movement of the object by overlapping the information told to the driver. In the future, wireless modules allow communication between vehicles, information exchange between vehicles and supporting infrastructure, and information exchange between vehicles and other connected devices (e.g., devices accompanying pedestrians). The safety system guides alternative behavior processes so that drivers can drive more safely, thereby reducing the risk of accidents. The next stage will be remote control or autonomous vehicles. This requires very high reliability and very fast communication between different autonomous vehicles and between vehicles and infrastructure. In the future, autonomous vehicles will perform all driving activities, and drivers will only focus on abnormal traffic that cannot be recognized by the vehicle. The technical requirements of autonomous vehicles require ultra-low latency and ultra-high reliability to increase traffic safety to a level that humans cannot reach.

[0052] Smart cities and smart homes / buildings, known as smart societies, will be embedded in high-density wireless sensor networks. Distributed networks of smart sensors will identify conditions for cost and energy-saving maintenance in cities or homes. Similar configurations can be performed for individual homes. Temperature sensors, window and heating controllers, burglar alarms, and home appliances are all wirelessly connected. Many of these sensors typically have low data transfer rates, power, and costs. However, certain types of devices may require real-time HD video to perform monitoring.

[0053] The consumption and distribution of energy, including heat or gas, is distributed at a higher level, requiring automatic control of a distributed sensor network. Smart grids collect information and use digital information and communication technologies to connect sensors to each other to act according to the collected information. Since this information can include the behavior of power supply companies and consumers, smart grids can improve the distribution of fuels such as electricity by methods with efficiency, reliability, economic viability, production sustainability and automation. Smart grids can also be considered as another sensor network with low latency.

[0054] Mission-critical applications (e.g., e-health) are one of the 5G use cases. The health segment contains many applications that can enjoy the benefits of mobile communications. The communication system can support telemedicine that provides clinical treatment in distant places. Telemedicine can help reduce distance barriers and improve access to medical services that are not continuously available in remote rural areas. Telemedicine is also used to perform important treatments and save lives in emergency situations. Wireless sensor networks based on mobile communications can provide remote monitoring and sensors for parameters such as heart rate and blood pressure.

[0055] Wireless and mobile communications are becoming increasingly important in the field of industrial applications. Cabling is expensive to install and maintain. Therefore, the possibility of replacing cables with reconfigurable wireless links is an attractive opportunity in many industrial fields. However, in order to achieve this replacement, wireless connections need to be established with latency, reliability and capacity similar to cables, and the management of wireless connections needs to be simplified. When it comes to connecting to 5G, low latency and very low error probability are new requirements.

[0056] Logistics and freight tracking are important use cases for mobile communications, which allow inventory and packages to be tracked anywhere using location-based information systems. Logistics and freight use cases typically require low data rates, but require location information with wide range and reliability.

[0057] Reference Figure 1 , the communication system 1 includes wireless devices 100a to 100f, a base station (BS) 200, and a network 300. Figure 1A 5G network is shown as an example of a network of the communication system 1 , but embodiments of the present disclosure are not limited to the 5G system and may be applied to future communication systems other than the 5G system.

[0058] The BS 200 and the network 300 may be implemented as wireless devices, and a specific wireless device may operate as a BS / network node relative to other wireless devices.

[0059] The wireless devices 100a to 100f represent devices that perform communication using a radio access technology (RAT) (e.g., 5G new RAT (NR) or LTE), and may be referred to as communication / radio / 5G devices. The wireless devices may include, but are not limited to, a robot 100a, vehicles 100b-1 and 100b-2, an extended reality (XR) device 100c, a handheld device 100d, a home appliance 100e, an IoT device 100f, and an artificial intelligence (AI) device / server 400. For example, a vehicle may include a vehicle with a wireless communication function, an autonomous vehicle, and a vehicle capable of performing communication between vehicles. A vehicle may include an unmanned aerial vehicle (UAV) (e.g., a drone). The XR device may include an AR / VR / mixed reality (MR) device, and may be implemented in the form of a head-mounted device (HMD), a head-up display (HUD) installed in a vehicle, a television, a smart phone, a computer, a wearable device, a home appliance device, a digital signage, a vehicle, a robot, and the like. Handheld devices may include smart phones, smart tablets, wearable devices (e.g., smart watches or smart glasses), and computers (e.g., notebook computers). Home appliances may include TVs, refrigerators, and washing machines. IoT devices may include sensors and smart meters.

[0060] In the present disclosure, the wireless devices 100a to 100f may be referred to as user equipment (UE). The UE may include, for example, a cellular phone, a smart phone, a laptop computer, a digital broadcast terminal, a personal digital assistant (PDA), a portable multimedia player (PMP), a navigation system, a tablet personal computer (PC), a tablet PC, an ultrabook, a vehicle, a vehicle with an autonomous driving function, a connected car, a UAV, an AI module, a robot, an AR device, a VR device, an MR device, a holographic device, a public safety device, an MTC device, an IoT device, a medical device, a FinTech device (or a financial device), a security device, a weather / environmental device, a device related to 5G services, or a device related to the field of the fourth industrial revolution.

[0061] A UAV may be, for example, an aircraft that is flown by wireless control signals without humans on board.

[0062] VR devices may include, for example, devices for realizing objects or backgrounds of a virtual world. AR devices may include, for example, devices realized by connecting objects or backgrounds of a virtual world to objects or backgrounds of a real world. MR devices may include, for example, devices realized by merging objects or backgrounds of a virtual world into objects or backgrounds of a real world. Holographic devices may include, for example, devices for realizing 360-degree stereoscopic images by recording and reproducing stereoscopic information using an interference phenomenon of light generated when two lasers meet, called holography.

[0063] Public safety devices may include, for example, image relay devices or image devices wearable on a user's body.

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

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

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

[0067] For example, a FinTech device may be a device that can provide financial services such as mobile payment. For example, a FinTech device may include a payment device or a point of sale (POS) system.

[0068] Weather / environmental devices may include, for example, devices for monitoring or predicting weather / environmental conditions.

[0069] The wireless devices 100a to 100f may be connected to the network 300 via the BS 200. The AI ​​technology may be applied to the wireless devices 100a to 100f, and the wireless devices 100a to 100f may be connected to the AI ​​server 400 via the network 300. The network 300 may be configured using a 3G network, a 4G (e.g., LTE) network, a 5G (e.g., NR) network, and a super 5G network. Although the wireless devices 100a to 100f may communicate with each other via the BS 200 / network 300, the wireless devices 100a to 100f may perform direct communication (e.g., side link communication) with each other without passing through the BS 200 / network 300. For example, the vehicles 100b-1 and 100b-2 may perform direct communication (e.g., vehicle-to-vehicle (V2V) / vehicle-to-everything (V2X) communication). An IoT device (e.g., a sensor) may perform direct communication with other IoT devices (e.g., a sensor) or other wireless devices 100a to 100f.

[0070] Wireless communication / connection 150a, 150b, and 150c may be established between wireless devices 100a to 100f and / or between wireless devices 100a to 100f and BS200 and / or between BS200. In this document, wireless communication / connection may be established through 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 BS200 / wireless devices 100a to 100f may send / receive radio signals to each other through wireless communication / connection 150a, 150b, and 150c. For example, wireless communication / connection 150a, 150b, and 150c may send / receive signals through various physical channels. To this end, various configuration information configuration processes for sending / receiving radio signals, various signal processing processes (e.g., channel coding / decoding, modulation / demodulation, and resource mapping / demapping), and at least a portion of a resource allocation process may be performed based on various proposals of the present disclosure.

[0071] AI means the field that studies artificial intelligence or methods that can create it, and machine learning refers to the field that defines the various problems addressed in the field of AI and methods to solve them. Machine learning is also defined as an algorithm that improves the performance of a task through steady experience with the task.

[0072] A robot means a machine that automatically processes or operates a given task by its own ability. Specifically, a robot that has the ability to recognize the environment and make self-determination to perform actions can be called an intelligent robot. According to the purpose or field of use, robots can be classified into industrial, medical, household, military, etc. The robot can perform various physical operations such as moving the robot joints using actuators or motors. The movable robot also includes wheels, brakes, propellers, etc. on the drive, allowing it to drive on the ground or fly in the air.

[0073] Autonomous driving means the technology of self-driving, and autonomous vehicles mean vehicles that are driven without user control or with minimal user control. For example, autonomous driving may include keeping lane movement, automatically adjusting speed (e.g., adaptive cruise control), automatically driving along a set route, and automatically setting a route when a destination is set. Vehicles include vehicles equipped with internal combustion engines, hybrid vehicles equipped with internal combustion engines and electric motors, and electric vehicles equipped with electric motors, and may include trains, motorcycles, etc. as well as cars. Autonomous vehicles can be regarded as robots with autonomous driving capabilities.

[0074] Extended reality is collectively referred to as VR, AR, and MR. VR technology only provides objects and backgrounds of the real world through computer graphics (CG) images. AR technology provides virtual CG images on top of real object images. MR technology is a CG technology that combines virtual objects into the real world. MR technology is similar to AR technology in that they show real objects and virtual objects together. However, the difference is that in AR technology, virtual objects are used as a complementary form of real objects, while in MR technology, virtual objects and real objects are used as the same characteristics.

[0075] NR supports multiple parameter sets (and / or multiple subcarrier spacing (SCS)) to support various 5G services. For example, if the SCS is 15kHz, wide areas can be supported in traditional cellular bands, and if the SCS is 30kHz / 60kHz, dense cities, lower latency, and wider carrier bandwidths can be supported. If the SCS is 60kHz or higher, bandwidths greater than 24.25GHz can be supported to overcome phase noise.

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

[0077] [Table 1]

[0078]

[0079] As described above, the numerical value of the frequency range of the NR system can be changed. For example, FR1 may include a frequency 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 MHz, 5900 MHz, 5925 MHz, etc.) or higher. For example, a frequency band of 6 GHz (or 5850 MHz, 5900 MHz, 5925 MHz, etc.) or higher included in FR1 may include an unlicensed frequency band. The unlicensed frequency band may be used for various purposes (e.g., for communication of vehicles (e.g., autonomous driving)).

[0080] [Table 2]

[0081]

[0082] Here, the radio communication technology implemented in the wireless device in the present disclosure may include narrowband Internet of Things (NB-IoT) technology for low-power communication as well as LTE, NR and 6G. For example, NB-IoT technology may be an example of a low-power wide area network (LPWAN) technology, which may be implemented in specifications such as LTE Cat NB1 and / or LTE Cat NB2, and may not be limited to the above names. Additionally and / or alternatively, the radio communication technology implemented in the wireless device in the present disclosure may communicate based on LTE-M technology. For example, LTE-M technology may be an example of LPWAN technology, and may be referred to as 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 may not be limited to the above names. Additionally and / or alternatively, the radio communication technology implemented in the wireless device in the present disclosure may include at least one of ZigBee, Bluetooth, and / or LPWAN considering low-power communication, and may not be limited to the above names. For example, ZigBee technology may generate a personal area network (PAN) associated with low-power / low-power digital communication based on various specifications such as IEEE 802.15.4, and may be referred to as various names.

[0083] Figure 2 An example of a wireless device to which an embodiment of the present disclosure is applied is shown.

[0084] Reference Figure 2, the first wireless device 100 and the second wireless device 200 may transmit / receive radio signals to / from an external device through various RATs (eg, LTE and NR).

[0085] exist Figure 2 In the embodiment, the first wireless device 100 and the second wireless device 200 may correspond to Figure 1 At least one of the wireless devices 100a to 100f and the BS200, the wireless devices 100a to 100f and the wireless devices 100a to 100f and / or the BS200 and the BS200.

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

[0087] The processing chip 101 may include at least one processor (eg, processor 102 ) and at least one memory (eg, memory 104 ). Figure 2 It is exemplarily shown that the memory 104 is included in the processing chip 101. Additionally and / or alternatively, the memory 104 may be placed outside the processing chip 101.

[0088] The processor 102 may control the memory 104 and / or the transceiver 106, and may be configured to implement the descriptions, functions, processes, suggestions, methods, and / or operational flow charts described in the present disclosure. For example, the processor 102 may process the information in the memory 104 to generate first information / signals, and then send a radio signal including the first information / signals through the transceiver 106. The processor 102 may receive a radio signal including second information / signals through the transceiver 106, and then store information obtained by processing the second information / signals in the memory 104.

[0089] The memory 104 may be operatively connected to the processor 102. The memory 104 may store various types of information and / or instructions. The memory 104 may store software code 105 implementing instructions that, when executed by the processor 102, perform the descriptions, functions, processes, suggestions, methods, and / or operational flow charts disclosed in the present disclosure. For example, the software code 105 may implement instructions that, when executed by the processor 102, perform the descriptions, functions, processes, suggestions, methods, and / or operational flow charts disclosed in the present disclosure. For example, the software code 105 may control the processor 102 to execute one or more protocols. For example, the software code 105 may control the processor 102 to execute one or more layers of a wireless interface protocol.

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

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

[0092] The processing chip 201 may include at least one processor (eg, processor 202 ) and at least one memory (eg, memory 204 ). Figure 2 It is exemplarily shown that the memory 204 is included in the processing chip 201. Additionally and / or alternatively, the memory 204 may be placed outside the processing chip 201.

[0093] The processor 202 may control the memory 204 and / or the transceiver 206, and may be configured to implement the descriptions, functions, processes, suggestions, methods, and / or operational flow charts described in the present disclosure. For example, the processor 202 may process the information in the memory 204 to generate third information / signals, and then send a radio signal including the third information / signals through the transceiver 206. The processor 202 may receive a radio signal including fourth information / signals through the transceiver 106, and then store information obtained by processing the fourth information / signals in the memory 204.

[0094] The memory 204 may be operatively connected to the processor 202. The memory 204 may store various types of information and / or instructions. The memory 204 may store software code 205 implementing instructions that, when executed by the processor 202, perform the descriptions, functions, processes, suggestions, methods, and / or operational flow charts disclosed in the present disclosure. For example, the software code 205 may implement instructions that, when executed by the processor 202, perform the descriptions, functions, processes, suggestions, methods, and / or operational flow charts disclosed in the present disclosure. For example, the software code 205 may control the processor 202 to execute one or more protocols. For example, the software code 205 may control the processor 202 to execute one or more layers of a wireless interface protocol.

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

[0096] Hereinafter, the hardware elements of the wireless devices 100 and 200 will be described in more detail. One or more protocol layers may be implemented by (but not limited to) one or more processors 102 and 202. For example, one or more processors 102 and 202 may implement one or more layers (e.g., functional layers such as a physical (PHY) layer, a medium access control (MAC) layer, a radio link control (RLC) layer, a packet data convergence protocol (PDCP) layer, a radio resource control (RRC) layer, and a service data adaptation protocol (SDAP) layer). One or more processors 102 and 202 may generate one or more protocol data units (PDUs) and / or one or more service data units (SDUs) according to the description, function, process, suggestion, method, and / or operation flowchart disclosed in the present disclosure. One or more processors 102 and 202 may generate messages, control information, data, or information according to the description, function, process, suggestion, method, and / or operation flowchart disclosed in the present disclosure. One or more processors 102 and 202 may generate a signal (e.g., a baseband signal) including a PDU, SDU, message, control information, data, or information according to the description, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed in the present disclosure, and provide the generated signal to one or more transceivers 106 and 206. One or more processors 102 and 202 may receive a signal (e.g., a baseband signal) from one or more transceivers 106 and 206 according to the description, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed in the present disclosure, and obtain the PDU, SDU, message, control information, data, or information.

[0097] One or more processors 102 and 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. 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 one or more processors 102 and 202. The descriptions, functions, processes, suggestions, methods, and / or operational flow charts disclosed in the present 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 operational flow charts disclosed in the present disclosure may be included in one or more processors 102 and 202 or stored in one or more memories 104 and 204 so as to be driven by one or more processors 102 and 202. The descriptions, functions, processes, suggestions, methods and / or operational flow charts disclosed in this disclosure may be implemented using software or firmware in the form of codes, commands and / or command sets.

[0098] One or more memories 104 and 204 may be connected to one or more processors 102 and 202 and store various types of data, signals, messages, information, programs, codes, instructions, and / or commands. One or more memories 104 and 204 may be configured by read-only memory (ROM), random access memory (RAM), electrically erasable programmable read-only memory (EPROM), flash memory, hard drive, register, flash memory, computer-readable storage medium, and / or a combination thereof. One or more memories 104 and 204 may be located inside and / or outside of one or more processors 102 and 202. One or more memories 104 and 204 may be connected to one or more processors 102 and 202 by various technologies such as wired or wireless connections.

[0099] One or more transceivers 106 and 206 can send user data, control information and / or radio signals / channels mentioned in the description, function, process, suggestion, method and / or operation flow chart disclosed in the present disclosure to one or more other devices. One or more transceivers 106 and 206 can receive user data, control information and / or radio signals / channels mentioned in the description, function, process, suggestion, method and / or operation flow chart disclosed in the present disclosure from one or more other devices. For example, one or more transceivers 106 and 206 can be connected to one or more processors 102 and 202 and send and receive radio signals. For example, one or more processors 102 and 202 can perform control so that one or more transceivers 106 and 206 can send user data, control information or radio signals to one or more other devices. One or more processors 102 and 202 can perform control so that one or more transceivers 106 and 206 can receive user data, control information or radio signals from one or more other devices.

[0100] One or more transceivers 106 and 206 may be connected to one or more antennas 108 and 208, and 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 flow charts disclosed in the present disclosure through one or more antennas 108 and 208. In the present disclosure, one or more antennas 108 and 208 may be multiple physical antennas or multiple logical antennas (e.g., antenna ports).

[0101] One or more transceivers 106 and 206 may convert received user data, control information, radio signals / channels, etc. from RF band signals into baseband signals so as to process the received user data, control information, radio signals / channels, etc. using one or more processors 102 and 202. One or more transceivers 106 and 206 may convert user data, control information, radio signals / channels, etc. processed using one or more processors 102 and 202 from baseband signals into RF band signals. To this end, one or more transceivers 106 and 206 may include (analog) oscillators and / or filters. For example, one or more transceivers 106 and 206 may up-convert OFDM baseband signals into OFDM signals through their (analog) oscillators and / or filters under the control of one or more processors 102 and 202, and transmit the up-converted OFDM signals at a carrier frequency. One or more transceivers 106 and 206 may receive the OFDM signal at a carrier frequency and down-convert the OFDM signal to an OFDM baseband signal through its (analog) oscillator and / or filter under the control of one or more processors 102 and 202 .

[0102] In an implementation of the present disclosure, a UE may operate as a transmitting device in an uplink (UL) and as a receiving device in a downlink (DL). In an implementation of the present disclosure, a BS may operate as a receiving device in the UL and as a transmitting device in the DL. Hereinafter, for the convenience of description, it is mainly assumed that the first wireless device 100 acts as a UE and the second wireless device 200 acts as a BS. For example, a processor 102 connected to, installed on, or started in the first wireless device 100 may be configured to perform UE behavior according to an implementation of the present disclosure, or to control a transceiver 106 to perform UE behavior according to an implementation of the present disclosure. A processor 202 connected to, installed on, or started in the second wireless device 200 may be configured to perform BS behavior according to an implementation of the present disclosure, or to control a transceiver 206 to perform BS behavior according to an implementation of the present disclosure.

[0103] In this disclosure, a BS is also referred to as a Node B (NB), an eNodeB (eNB), or a gNB.

[0104] Figure 3 An example of a wireless device to which an embodiment of the present disclosure is applied is shown.

[0105] Can be based on use cases / services (see Figure 1 ) Wireless devices are implemented in various forms.

[0106] Reference Figure 3, the wireless devices 100 and 200 may correspond to Figure 2 The wireless devices 100 and 200 of the present invention may be configured by 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, the transceiver 114 may include Figure 2 One or more transceivers 106 and 206 and / or Figure 2 The control unit 120 is electrically connected to the communication unit 110, the memory unit 130, and the additional components 140, and controls the overall operation of each of the wireless devices 100 and 200. For example, the control unit 120 may control the electrical / mechanical operation of each of the wireless devices 100 and 200 based on the program / code / command / information stored in the memory unit 130. The control unit 120 may transmit information stored in the memory unit 130 to the outside (e.g., other communication devices) through a wireless / wired interface via the communication unit 110, or store information received from the outside (e.g., other communication devices) through a wireless / wired interface via the communication unit 110 in the memory unit 130.

[0107] The additional component 140 may be variously configured according to the type of the 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 driving unit, and a computing unit. The wireless devices 100 and 200 may be in the form of (but not limited to) a robot ( Figure 1 100a), vehicles ( Figure 1 100b-1 and 100b-2), XR devices ( Figure 1 100c), handheld device ( Figure 1 100d), household appliances ( Figure 1 100e), IoT devices ( Figure 1 100f), digital broadcasting terminal, holographic device, public safety device, MTC device, medical device, FinTech device (or financial device), security device, climate / environmental device, AI server / device ( Figure 1 400), BS( Figure 1The wireless devices 100 and 200 may be implemented in the form of a wireless device 200 , a network node, etc. The wireless devices 100 and 200 may be used in a mobile or fixed location depending on the usage example / service.

[0108] exist Figure 3 In the wireless devices 100 and 200, the entirety of the various elements, components, units / parts and / or modules in the wireless devices 100 and 200 may be connected to each other through a wired interface, or at least a portion thereof may be wirelessly connected through the communication unit 110. For example, in each of the wireless devices 100 and 200, the control unit 120 and the communication unit 110 may be wired, and the control unit 120 and the first unit (e.g., 130 and 140) may be wirelessly connected through the communication unit 110. Each element, component, unit / part and / or module within the wireless devices 100 and 200 may also include one or more elements. For example, the control unit 120 may be configured by a collection of one or more processors. As an example, the control unit 120 may be configured by a collection of a communication control processor, an application processor (AP), an electronic control unit (ECU), a graphics processing unit, and a memory control processor. As another example, the memory unit 130 may be configured by a RAM, a DRAM, a ROM, a flash memory, a volatile memory, a non-volatile memory, and / or a combination thereof.

[0109] Figure 4 It is a structural diagram of the next generation mobile communication network.

[0110] 5GC (5G Core) may include various components including access and mobility management function (AMF) 410, session management function (SMF) 420, policy control function (PCF) 430, user plane function (UPF) 44, application function (AF) 450, unified data management (UDM) data network 460 and non-3GPP (3rd Generation Partnership Project) interworking function (N3IWF) 490, some of which are described in Figure 4 Shown in.

[0111] UE 100 is connected to a data network via UPF 440 through a next generation radio access network (NG-RAN) including gNB 20.

[0112] Even through untrusted non-3GPP accesses, such as wireless local area networks (WLANs), data services may be provided to the UE 100. In order to connect the non-3GPP accesses to the core network, the N3IWF 490 may be deployed.

[0113] The N3IWF 490 shown performs the function of managing the interworking between the non-3GPP access and the 5G system. When the UE 100 is connected to the non-3GPP access (e.g., WiFi known 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 through the N3 interface for data transmission.

[0114] The AMF 410 shown can manage access and mobility in the 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.

[0115] The UPF 440 shown is a gateway through which user data is sent / received. The UPF 440 may perform all or part of the user plane functions of a serving gateway (S-GW) and a packet data network gateway (P-GW) of 4G mobile communication.

[0116] UPF 440 serves as a boundary point between the next generation radio access network (NG-RAN) and the core network, and maintains the data path between gNB20 and SMF 420. In addition, when UE 100 moves over the area served by gNB 20, UPF 440 serves as a mobility anchor point. UPF 440 can perform the function of handling PDUs. For mobility within NG-RAN (which is defined after 3GPP Release 15), UPF 440 can route packets. In addition, UPF 440 can also serve as an anchor point for mobility with another 3GPP network (RAN defined before 3GPP Release 15, for example, Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN), Evolved (E)-UTRAN, or Global System for Mobile Communications (GERAN) / Enhanced Data Rates for Global Evolution (EDGE) RAN). UPF 440 may correspond to an endpoint of a data interface toward a data network.

[0117] The PCF 430 shown is a node that controls the operator's policy.

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

[0119] The illustrated UDM 460 is a server that manages subscriber information (eg, a Home Subscriber Server (HSS) of 4G mobile communication). The UDM 460 stores and manages subscriber information in a unified data repository (UDR).

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

[0121] For reference, in the following, the figure markings of AMF (410), SMF (420), PCF (430), UPF (440), AF (450), UDM (460), N3IWF (490), gNB (20) or UE (100) may be omitted.

[0122] The fifth generation of mobile communications supports multiple parameter sets (e.g., multiple values ​​of subcarrier spacing (SCS)) to support various services. For example, when the SCS is 15kHz, a wide area in the traditional cellular band is supported. When the SCS is 30kHz / 60kHz, dense cities, lower latency, and wider carrier bandwidth are supported. When the SCS is 60kHz or greater, a bandwidth greater than 24.25GHz is supported to overcome phase noise.

[0123] Figure 5 is an example diagram showing the predicted structure of the next generation of mobile communications from the perspective of nodes.

[0124] Reference Figure 5 , the UE is connected to the data network (DN) through the next generation RAN (Radio Access Network).

[0125] Figure 5 The control plane function (CPF) node shown can perform all or part of the mobility management entity (MME) functions of the fourth generation mobile communication and all or part of the control plane functions of the serving gateway (S-GW) and PDN (packet data network)-gateway (P-GW) of the fourth generation mobile communication. The CPF node includes an access and mobility management function (AMF) node and a session management function (SMF) node.

[0126] The user plane function (UPF) node shown in the figure is a gateway through which user data is sent and received. The UPF node can perform all or part of the user plane functions of the S-GW and P-GW of the fourth generation mobile communication.

[0127] Figure 5 The illustrated Policy Control Function (PCF) node is configured to control policies of a service provider.

[0128] The shown application function (AF) node refers to a server that provides various services to UE.

[0129] The Unified Data Management (UDM) node as shown refers to a server that manages subscriber information, such as a Home Subscriber Server (HSS) of 4th generation mobile communications. The UDM node stores and manages subscriber information in a Unified Data Repository (UDR).

[0130] The Authentication Server Function (AUSF) node as shown authenticates and manages the UE.

[0131] The Network Slice Selection Function (NSSF) node as shown refers to the node that performs network slicing as described below.

[0132] The Network Exposure Function (NEF) shown is a node for providing a mechanism to securely expose services and functions of the 5G core. For example, the NEF exposes functions and events, securely provides information from external applications to the 3GPP network, converts internal / external information, provides control plane parameters, and manages packet flow descriptions (PFDs).

[0133] exist Figure 6 In , the UE can use multiple PDU sessions to access two data networks simultaneously.

[0134] Figure 6 is an exemplary diagram showing an architecture that allows a UE to access two data networks simultaneously using one PDU session.

[0135] Figure 6 An architecture is shown that allows a UE to access two data networks simultaneously using one PDU session.

[0136] For reference, Figure 2 and Figure 3 A description of the reference points shown follows.

[0137] N1 represents the reference point between UE and AMF.

[0138] N2 represents the reference point between NG-RAN and AMF.

[0139] N3 represents the reference point between NG-RAN and UPF.

[0140] N4 represents the reference point between SMF and UPF.

[0141] N5 represents the reference point between PCF and AF.

[0142] N6 represents the reference point between UPF and DN.

[0143] N7 represents the reference point between SMF and PCF.

[0144] N8 represents the reference point between UDM and AMF.

[0145] N9 represents the reference point between UPFs.

[0146] N10 represents the reference point between UDM and SMF.

[0147] N11 represents the reference point between AMF and SMF.

[0148] N12 represents the reference point between AMF and AUSF.

[0149] N13 represents the reference point between UDM and AUSF.

[0150] N14 represents the reference point between AMFs.

[0151] N15 represents the reference point between the PCF and AMF in a non-roaming scenario and the reference point between the AMF and PCF of the access network in a roaming scenario.

[0152] N16 represents the reference point between SMFs.

[0153] N22 represents the reference point between AMF and NSSF.

[0154] N30 represents the reference point between PCF and NEF.

[0155] N33 indicates the reference point between AF and NEF.

[0156] exist Figure 5 and Figure 6 In the 5GC, AFs of third parties other than operators can be connected to 5GC through the network open function (NEF).

[0157] <Network Data Analysis>

[0158] To support enablers of network automation, methods to improve the performance of 5GS systems are being discussed.

[0159] For example, for 5GS system enhancement, it may be necessary to further study the system enhancement of the network data analysis function (NWDAF). Through the system enhancement of NWDAF, 5GS can support network automation.

[0160] Here, NWDAF may be a network node that provides network analysis information based on a request from another network node (another NF). For example, NWDAF may generate analysis information based on communication related information (e.g., information related to the load level of a specific network slice). NWDAF may provide analysis information such as statistical information or prediction information to other network nodes (other NFs) in order to utilize data provided by UE or other network nodes.

[0161] Research related to network data analysis may focus on data analysis of 5GC NF (network function) (e.g., data analysis to support 5GC NF decision making). Alternatively, research related to network data analysis may focus on supporting application-related analysis, UE-related analysis, and session-related analysis. In terms of network data analysis, research may be conducted on the input to NWDAF and the output of NWDAF. Potential improvements and new scenarios for network data analysis may be studied.

[0162] As input for NWDAF to generate data analysis, data from UE or data from network nodes (e.g., SMF) can be used. In order for 5GS to support NWDAF that collects and utilizes data provided from UE (or network node), ways to enhance 5GS can be discussed. 5GS can be enhanced to provide input information for generating analysis information to NWDAF. This analysis information can be used by other NFs (e.g., non-NWDAF network nodes).

[0163] When envisioning network enhancements based on data provided to the UE (or network node) of the NWDAF, questions such as the following examples may be investigated:

[0164] - What type of information can the network (eg NWDAF) collect from the UE as input for analytics generation?

[0165] - What types of analysis information can the NWDAF provide to other NFs to exploit the data provided by the UE?

[0166] - How often is such data provided by the UE shared with the NWDAF?

[0167] -What are the triggers for the UE to provide data to the NWDAF as input for analysis?

[0168] - How to ensure the integrity and carrier-grade accessibility of information provided by the UE to avoid the use of misleading or untrusted information in the network?

[0169] - Are there any privacy aspects that need to be considered, i.e. related to the information provided by the UE? If so, how can the privacy of the collection and use of UE data be ensured?

[0170] -How does NWDAF collect UE information (data collection method)?

[0171] The network can guarantee the privacy, integrity and operator-grade accessibility of the data provided by the UE.

[0172] The NWDAF may provide statistical or prediction information to the UE or other NFs to utilize the data provided by them.

[0173] There may not be a direct interface between the UE and the NWDAF.

[0174] <Congestion Control>

[0175] In 5G communication, congestion control may be used. For example, congestion control related to session management (SM) used in 5GS is defined as the following example. Hereinafter, an example of congestion control based on a data network name (DNN) and single network slice selection auxiliary information (S-NSSAI) based on congestion control will be described.

[0176] First, DNN-based congestion control will be described.

[0177] Regardless of the presence of S-NSSAI, DNN-based congestion control is designed to prevent and handle NAS SM signaling congestion for UEs with backoff timers associated with DNNs (or UEs without backoff timers associated with DNNs). Both UE and 5GC must support the functionality to enable DNN-based congestion control.

[0178] The SMF may apply DNN-based congestion control to the UE by rejecting a PDU Session Establishment Request message or a PDU Session Modification Request message. Exceptionally, the SMF may not reject a message sent to report a 3GPP Packet Switched (PS) Data Off state change for a specific DNN running a backoff timer.

[0179] The SMF may release a PDU Session belonging to a congested DNN by sending a PDU SESSION RELEASE COMMAND message to the UE along with the DNN BACKOFF TIMER. If the DNN BACKOFF TIMER is set in the PDU SESSION RELEASE COMMAND message, the Cause value is not set to "Reactivation Request".

[0180] When DNN-based congestion control is activated in the AMF (e.g., DNN-based congestion control is set by OAM), the AMF may provide a NAS transport error message for a NAS transport message carrying a session management (SM) message, and may include a DNN backoff timer in the NAS transport error message.

[0181] The UE may associate the received backoff timer value with a DNN (eg, no DNN, only DNN) included in an uplink NAS Mobility Management (MM) message for delivering a corresponding NAS SM request message.

[0182] If the DNN associated with the back-off timer is not a local access data network (LADN) DNN, the UE may associate the received back-off timer value with DNNs in all PLMNs (i.e., no DNNs, only DNNs). In this case, the UE associates the received back-off timer value only with the PLMN in which the back-off timer value was received.

[0183] When the DNN backoff timer is being executed (or running), the UE may operate as in the following example:

[0184] -If a DNN is associated with a backoff timer, the UE may not initiate any session management procedures for the congested DNN. The UE may initiate session management procedures for other DNNs. When the UE moves to the EPS, the UE shall not initiate any session management procedures for the corresponding APN. When the UE moves to the EPS, the UE may initiate session management procedures for other APNs;

[0185] - If no DNN is associated with the backoff timer, the UE may initiate session management requests for any PDU session type only for a specific DNN;

[0186] - The UE does not stop the back-off timer when the cell / tracking area (TA) / PLMN / radio access technology (RAT) changes, the untrusted non-3GPP access network changes, or the access type changes;

[0187] -The UE may initiate session management procedures for high priority access and emergency services;

[0188] -UE can initiate the session management process and report the data closing status change to the network;

[0189] -The UE may initiate a PDU session release procedure. That is, the UE may send a PDU session release request message. When the associated PDU session is released, the UE may not stop the backoff timer;

[0190] - If the UE receives a network initiated session management message other than a PDU Session Release Command for a congested DNN associated with a running backoff timer, the UE shall stop the backoff timer and respond to the 5GC;

[0191] - If the UE receives a PDU Session Release Command message from a congested DNN, it shall stop the backoff timer unless it receives a new backoff time from the SMF;

[0192] - Allow the UE to initiate the PDU session release procedure (i.e. send a PDU session release request message). The UE shall not stop the backoff timer when releasing the related PDU session;

[0193] If the UE initiates one of the session management procedures that exempts NAS congestion control, the UE indicates in the UL NAS transport message that the carried NAS SM message is exempt from NAS congestion control. When DNN-based congestion control is activated at the AMF, if the UE indicates that the NAS SM message in the UL NAS transport message is exempt from NAS congestion control, the AMF does not apply DNN-based congestion control to the UL NAS transport message. And, in this case, the AMF may forward a NAS SM message with an indication of the received message with an exemption indication to the corresponding SMF. The SMF may evaluate whether the NAS SM message is allowed to be exempt from DNN-based congestion control. If not, the SMF rejects the message, for example, (if it is not a data closing status report, the SMF should reject the received PDU session modification).

[0194] The UE may maintain a separate backoff timer for each DNN that the UE may use.

[0195] To avoid a large number of UEs initiating delay requests (almost) simultaneously, the 5GC should select the backoff timer value such that the delay requests are not synchronized.

[0196] If the UE needs to report a 5GSM core network capability change, or an always-on PDU session request indication, when DNN-based congestion control is running and SM signaling cannot be initiated, the UE postpones the related SM signaling until the DNN-based congestion control timer expires. And the UE can initiate the necessary SM signaling after the timer expires.

[0197] DNN-based session management congestion control applies to NAS SM signaling initiated from the UE in the control plane. Session management congestion control does not prevent the UE from sending and receiving data to the DNN under session management congestion control or initiating a service request procedure for activating a user plane connection.

[0198] Hereinafter, congestion control based on S-NSSAI will be described.

[0199] The purpose of S-NSSAI based congestion control design is to avoid and handle NAS signaling congestion for UEs with backoff timers associated with or not associated with S-NSSAI, regardless of the presence of DNN.

[0200] The UE may associate the received backoff time with the S-NSSAI and DNN included in the uplink NAS MM message (i.e., no S-NSSAI and DNN, no S-NSSAI, only S-NSSAI, S-NSSAI and DNN). Here, the uplink NAS MM message may be a NAS MM message carrying a corresponding NAS SM request message for a PLMN in congestion.

[0201] S-NSSAI based congestion control can be applied as in the following example:

[0202] - If the S-NSSAI is determined to be congested, the SMF may apply S-NSSAI based congestion control to the UE for SM requests, except for those requests sent to report a 3GPP PS Data Off state change for a specific S-NSSAI, and provide a back-off time and an indication of HPLMN congestion;

[0203] - If the UE receives an S-NSSAI based backoff time without an HPLMN congestion indication, the UE shall apply the S-NSSAI backoff timer only in the PLMN where the backoff time was received. If the UE receives an S-NSSAI based backoff time with an HPLMN congestion indication, the UE shall apply the S-NSSAI based backoff timer in the PLMN where the backoff time was received and any other PLMNs;

[0204] - The SMF may release the PDU Session belonging to the congested S-NSSAI by sending a PDU Session Release Request message to the UE with a backoff time associated with the S-NSSAI only (i.e. without a specific DNN) or with a combination of the S-NSSAI and a specific DNN;

[0205] - If S-NSSAI based congestion control is activated at the AMF, e.g. configured by OAM, and the S-NSSAI is determined to be congested, the AMF applies S-NSSAI based congestion control to the UE for the session management request initiated by the UE. In this case, the AMF provides a NAS transport error message for the NAS transport message carrying the SM message, and includes a backoff timer in the NAS transport error message;

[0206] The UE may behave as follows in a PLMN where S-NSSAI based congestion control is applied when the back-off timer is running:

[0207] - If the backoff timer is associated with the S-NSSAI only (i.e. not associated with the S-NSSAI and DNN), the UE may not initiate any session management procedures for the congested S-NSSAI;

[0208] - If a backoff timer is associated with S-NSSAI and DNN, the UE may not initiate any session management procedure for the combination of S-NSSAI and DNN;

[0209] - If the UE receives a network initiated session management message other than a PDU session release command for a congested S-NSSAI, the UE may stop the backoff timer and respond to the 5GC;

[0210] - If the UE receives a PDU Session Release Command message for a congested S-NSSAI, it shall stop the backoff timer unless it receives a new backoff time from the SMF;

[0211] - The UE shall not stop the backoff timer for any S-NSSAI or any combination of S-NSSAI and DNN when the cell / TA / PLMN / RAT changes, the untrusted non-3GPP access network changes or the access type changes;

[0212] - Allows the UE to initiate the session management procedure for high priority access and emergency services of S-NSSAI;

[0213] - Allows the UE to initiate a session management procedure for reporting a data off state change for S-NSSAI or a combination of S-NSSAI and DNN.

[0214] - If the back-off timer is not associated with any S-NSSAI, the UE may initiate session management procedures only for a specific S-NSSAI;

[0215] - If the back-off timer is not associated with any S-NSSAI and DNN, the UE may initiate session management procedures only for specific S-NSSAI and DNN;

[0216] - The UE is allowed to initiate a PDU Session release procedure (e.g. sending a PDU Session Release Request message). The UE shall not stop the backoff timer when releasing the associated PDU Session.

[0217] The UE shall maintain a separate backoff timer for each S-NSSAI and each combination of S-NSSAI and DNN that the UE may use.

[0218] If the UE initiates one of the session management procedures that exempts NAS congestion control, the UE may indicate in the UL NAS transport message that the carried NAS SM message is exempt from NAS congestion control. When S-NSSAI based congestion control is activated at the AMF, if the UE indicates that the NAS SM message in the UL NAS transport message is exempt from NAS congestion control, the AMF shall not apply S-NSSAI based congestion control to the UL NAS transport message and forward the NAS SM message to the corresponding SMF indicating that a message with an exemption indication was received. The SMF may evaluate whether the NAS SM message is allowed to be exempt from S-NSSAI based congestion control. If not, the SMF rejects the message, for example, if it is not a data closed status report, the SMF may reject the received PDU session modification.

[0219] When the UE is in 5GS, the backoff timer associated with S-NSSAI or a combination of S-NSSAI and DNN may be applied only for congestion control of session management procedures.

[0220] To avoid that a large number of UEs initiate delay requests (almost) simultaneously, the 5GC may select the value of the backoff timer used for S-NSSAI based congestion control such that the delay requests are not synchronized.

[0221] If the UE needs to report a change in 5GSM core network capabilities, or always-on PDU session request indication, when the S-NSSAI-based congestion control timer is running and SM signaling cannot be initiated, the UE may postpone the relevant SM signaling until the S-NSSAI-based congestion control timer expires and initiate the necessary SM signaling after the timer expires.

[0222] S-NSSAI based congestion control does not prevent the UE from sending and receiving data or initiating a service request procedure for activating a user plane connection for a PDU session associated with the S-NSSAI under congestion control.

[0223] II. Disclosure of this Specification

[0224] The disclosure described below in this specification may be implemented in one or more combinations (for example, a combination including at least one of the contents described below). Each drawing shows an embodiment of each disclosure, but the embodiments of the drawings may be implemented in combination with each other.

[0225] The description of the method proposed in the disclosure of 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.

[0226] For specific examples of SM-related congestion control schemes and backoff timers related to the congestion control schemes (e.g., T3396 for DNN-based congestion control, T3584 for S-NSSAI-based congestion control), reference may be made to conventional technologies (e.g., TS24.501V15.0.0).

[0227] According to the SM-related congestion control mechanism (e.g., DNN-based congestion control and / or S-NSSAI-based congestion control), the SMF does not store information and / or history about the UE for which the SMF provides a backoff timer. Here, the SMF may apply the SM-related congestion control mechanism, or may have already applied the SM-related congestion control mechanism.

[0228] Therefore, the fairness of the application of SM-related congestion control is not considered and cannot be guaranteed. For example, among UEs using a PDU session associated with S-NSSAI #1, some UEs may experience congestion control based on a high S-NSSAI (e.g., some UEs may receive a NAS SM reject message including a long backoff timer value from the SMF). On the other hand, some other UEs may experience congestion control based on a low S-NSSAI during a specific period of time (e.g., the UE may receive a NAS SM reject message including a short backoff timer value from the SMF). Since the timer value of the backoff timer received by the UE can be as high as 70 hours, the backoff timer provided to each UE may be different.

[0229] As in the above-described example, when SM-related congestion control is applied, fairness issues may occur. In the disclosure of this specification, examples of methods for solving fairness issues are described.

[0230] For example, the disclosure herein may describe an example of how to use data analysis to solve fairness issues. As an example, the disclosure of this specification describes an example of solving fairness issues by using UE data provided by the UE. As another example, the disclosure of this specification describes an example of solving fairness issues by using data provided by a network node (e.g., SMF).

[0231] For example, the disclosure of this specification proposes a method of using data (eg, data analysis, UE data, and / or data provided by a network node) to support SM congestion control.

[0232] The method for supporting SM congestion control proposed in the disclosure of this specification may be configured by a combination of one or more operations / configurations / steps in various examples described below.

[0233] For descriptions of NWDAF operations, 5GS network automation enabler, network data analysis services, etc., see TS23.288V16.1.0.

[0234] Various examples are described in the disclosure of this specification.For example, the following describes analysis of SM Congestion Control Experience (SMCCE) utilizing data (eg, data analysis, UE data, and / or data provided by a network node).

[0235] According to the SM-related congestion control mechanism (e.g., DNN-based congestion control and / or S-NSSAI-based congestion control), the SMF does not store information and / or history about the UE for which the SMF provides a backoff timer. Here, the SMF may apply the SM-related congestion control mechanism, or may have already applied the SM-related congestion control mechanism.

[0236] Therefore, the fairness of the application of SM-related congestion control is not considered and cannot be guaranteed. For example, among UEs using a PDU session associated with S-NSSAI #1, some UEs may experience congestion control based on a high S-NSSAI (e.g., some UEs may receive a NAS SM reject message including a long backoff timer value from the SMF). On the other hand, some other UEs may experience congestion control based on a low S-NSSAI during a specific period of time (e.g., the UE may receive a NAS SM reject message including a short backoff timer value from the SMF). Since the timer value of the backoff timer received by the UE can be as high as 70 hours, the backoff timer provided to each UE may be different.

[0237] In order to solve the same problem as the above example, in the disclosed embodiment of this specification, a new analysis ID (Analysis ID) "Session Management Congestion Control Experience (SMCCE)" is proposed. NWDAF can use this data to analyze SMCCE. For example, NWDAF can provide observed (or analyzed) SMCCE analysis to service consumers for specific DNNs and / or S-NSSAI. For example, NWDAF can provide SMCCE analysis to service consumers in the form of statistics or predictions.

[0238] For example, the service consumer may be an SMF. Alternatively, other NFs and operations, management and maintenance (OAM) may also be service consumers. The observed (or analyzed) SMCCE analysis may provide one or more of the following outputs to the service consumer:

[0239] a) A list of UEs with higher experience levels for session management congestion control for a specific DNN and / or S-NSSAI;

[0240] b) a list of UEs with medium experience level for session management congestion control for a specific DNN and / or S-NSSAI;

[0241] c) A list of UEs with low or zero experience level for session management congestion control for a specific DNN and / or S-NSSAI.

[0242] In other words, the NWDAF may provide the service consumer (eg, SMF) with SMCCE analysis information including information about one or more of a) to c) above.

[0243] Additionally, if the service consumer is an SMF, the observed (or analyzed) SMCCE analysis may provide output to the SMF, such as the following example:

[0244] 1) A list of UEs recommended for reallocation by the serving SMF. (This list may be the same as a) or include UEs that do not belong to any of a), b) and c). ); and

[0245] 2) A list of candidate SMFs that can be used as target SMFs for SMF reallocation.

[0246] In other words, the NWDAF may additionally provide the service consumer (eg, SMF) with SMCCE analysis information, including the information regarding 1) and 2) described above.

[0247] For reference, NWDAF may derive the above 2) using NF load analysis according to the prior art. For example, here, the NF load analysis may be an analysis in which the target NF type is set to SMF and a specific S-NSSAI is performed.

[0248] The NWDAF may receive a request message for requesting SMCCE analysis from a service consumer. The NWDAF may then use the data to generate (or determine) SMCCE analysis information. In addition, the NWDAF may provide the SMCCE analysis information to the service consumer.

[0249] The request of the service consumer may include parameters such as the following examples. For example, the request message sent by the service consumer to the NWDAF may include the parameters in the following examples:

[0250] -Analysis ID = "Session Management Congestion Control Experience".

[0251] - Target of the analytical report: one or more SUPIs.

[0252] -Analysis filter information. For example, the analysis filter information may include DNN and / or S-NSSAI.

[0253] -Analysis target time period: the time period in the past or future for which statistics or forecasts are required.

[0254] In other words, the same parameters as in the example can be used as input parameters for SMCCE analysis. In addition, in addition to the parameters in the above example, other conventional input parameters can also be used for the request of the service consumer. In addition to the parameters included in the request of the service consumer, various parameters can be included in the request.

[0255] The NWDAF may collect UE data in order to calculate statistics and predictions about the observed session management congestion control experience and provide them to the consumer NF. For example, the NWDAF may collect UE data related to the session management congestion control experience from the UE via the AMF and / or from the UE data store (e.g., UDR, NWDAF acting as a data store function). For example, the NWDAF may collect UE data related to the SMCCE from the SMF.

[0256] NWDAF can collect data (e.g., UE data) to analyze SMCCE. For example, for the purpose of SMCCE analysis, NWDAF can collect data such as the following: Figure 7 Example UE data.

[0257] The following figures are created to explain specific examples of this specification. Since the names of specific devices or the names of specific signals / messages / fields described in the figures are presented by way of example, the technical features of this specification are not limited to the specific names used in the following figures.

[0258] Figure 7 An example of UE data according to an embodiment disclosed in this specification is shown.

[0259] Figure 7 The example of FIG. 4 shows an example of UE data collected by NWDAF for SMCCE analysis.

[0260] UE data collected by NWDAF may include Figure 7 In other words, Figure 7 The information shown in the example can be the input data for SMCCE analysis.

[0261] The UE data collected by the NWDAF may include the UE ID information of the PDU session and the SMCC (SM Congestion Control) experience (SMCC experience of the PDU session) information. Here, the UE ID information may include SUPI. The SMCC experience of the PDU session information may be UE data related to the SMCC experience of each PDU session.

[0262] UE data related to the SMCC experience for each PDU session may include Figure 7 For example, UE data related to the SMCC experience for each PDU session may include one or more of DNN, S-NSSAI, start time of data collection, end time of data collection, sent SM NAS requests (1..max), and received SM NAS rejections / commands (1,...,max) with backoff timers.

[0263] exist Figure 7 In the example of , the DNN may refer to the DNN of the PDU session in which the UE collects UE data related to the SMCCE. The S-NSSAI may refer to the S-NSSAI of the PDU session in which the UE collects UE data related to the SMCCE.

[0264] The start time of data collection may refer to the start time of data collection. The end time of data collection may refer to the end time of data collection.

[0265] The SM NAS request (1..max) sent may represent information related to the SM NAS message sent by the UE to the SMF. For example, the UE may send an SM NAS message for a PDU session to the SMF. Here, "(1..max)" may refer to the number of SM NAS request information sent. For example, the maximum number of SM NAS request information sent may be collected / stored, and the number of SM NAS requests sent collected / stored may refer to the number of times the UE sends an SM NAS message during a data collection period.

[0266] Each SM NAS request message sent may include the type and timestamp of the SM NAS request.

[0267] The type of SM NAS request may refer to the type of SM NAS message sent by the UE. For example, the type of SM NAS message may be a PDU session establishment request, a PDU session modification request, etc. The timestamp may refer to the timestamp when the UE sends the SM NAS message to the SMF.

[0268] Received SM NAS rejection / command with backoff timer (1,...,max) may represent information related to the SMCC applied to the UE. For example, received SM NAS rejection / command with timing timer information may represent information related to the SMCC applied to the PDU session of the UE. Here, "(1..max)" may refer to the number of received SM NAS rejections / commands with timing timer information. Up to a maximum number of received SM NAS rejections / commands with backoff timer information may be collected / stored, and the number collected / stored may refer to the number of times the SMCC is applied to the UE during a data collection period. For example, the number of received SM NAS rejections / commands collected / stored with backoff timer information may refer to the number of times the UE receives a SM NAS rejection or a SM NAS command together with a backoff timer during a data collection period.

[0269] The received SM NAS reject / command with backoff timer information may include the type of SM NAS reject / command, a timestamp, the received backoff timer, and the type of SMCC applied.

[0270] The type of SM NAS rejection / command may refer to the type of SM NAS message received by the UE. For example, the type of SM NAS message may be PDU session establishment rejection, PDU session modification rejection, PDU session release command, etc. The timestamp may indicate the timestamp when the UE receives the SM NAS message from the SMF. The received backoff timer may refer to the value of the received backoff timer. The Type of SMCC applied refers to the type of SMCC applied. For example, the type of SMCC applied may be DNN-based congestion control or S-NSSAI-based congestion control.

[0271] UE can collect Figure 7 . For example, the UE may collect UE data related to the SMCC experience for each PDU session. And, the UE may provide the collected UE data to the AMF. For example, the UE may periodically provide the collected UE data to the AMF. Alternatively, when the AMF requests the UE data, the UE may provide the collected UE data to the AMF. Alternatively, when the data collected by the UE reaches a maximum amount, the UE may provide the UE data to the AMF.

[0272] UE can provide Figure 7 In addition, Figure 7 The UE data shown in the example is only an example, and the disclosure scope of this specification is not limited thereto. For example, the UE may provide Figure 7 Information not shown in the examples or with Figure 7 For example, the UE may provide information such as access type information (3GPP access or non-3GPP access) associated with a sent SM NAS request, received SM NAS rejection / command (3GPP access or non-3GPP access) with back-off timer related access type information, public land mobile network (PLMN) information associated with a sent SM NAS request, PLMN information associated with a received SM NAS rejection / command with back-off timer, sent SM NAS request count / number, received SM NAS rejection / command with back-off timer count / number.

[0273] For reference, although in Figure 7 In the example of FIG. 1 , a description of UE collecting UE data is written, but this is only an example and the scope of the present disclosure is not limited thereto. Figure 7 For example, the scope disclosed herein may also include a network node (eg, SMF) that collects UE data.

[0274] As an example, SMF can collect Figure 7 The SMF may provide the collected UE data to the NWDAF. Specifically, the SMF may collect / store data collected by the UE from the perspective of the SMF (e.g., Figure 7 For example, in Figure 7In the case of the SM NAS request information sent in the example of , the SMF may collect / store the SM NAS request related information in the form of information about the SM NAS request received from the UE. Therefore, the type of the SM NAS request may refer to the type of the SM NAS message received by the SMF from the UE. For example, the type of the SM NAS message may be a PDU session establishment request, a PDU session modification request, etc. And, the timestamp may indicate the timestamp when the SMF receives the SM NAS message from the UE. In addition, the received SM NAS rejection / command with backoff timer information may be collected / stored in the form of a SM NAS rejection / command with backoff timer information applied / provided to the UE by the SMF. Therefore, the type of the SM NAS rejection / command may refer to the type of the SM NAS message applied / provided to the UE. For example, the type of the SM NAS message may be a PDU session establishment rejection, a PDU session modification rejection, a PDU session release command, etc. The timestamp may refer to the timestamp when the SMF sends the SM NAS message to the UE. The received backoff timer may be interpreted by replacing the value of the backoff timer applied / provided to the UE by the SMF. The Type of the applied SMCC refers to the type of the applied SMCC. For example, the type of SMCC applied may be DNN-based congestion control or S-NSSAI-based congestion control.

[0275] When a service consumer (e.g., SMF) requests analysis (e.g., SMCCE) related to SM congestion control from NWDAF, NWDAF may perform analysis (e.g., SMCCE) related to SM congestion control. For example, NWDAF may Figure 7 The NWDAF may collect UE data as in the example of , and may perform SM congestion control related analysis (e.g., SMCCE) based on the collected data. The NWDAF may provide (or send) analysis (e.g., SMCCE) information related to SM congestion control to the service consumer (e.g., SMF), such as the following: Figure 8 Examples of and / or Fig. 9 .

[0276] For example, the NWDAF may output an SMCCE analysis. For example, as a result of performing the SMCCE analysis, the NWDAF may output SMCCE statistics or SMCCE predictions. As an example, the output of the NWDAF may be configured as SMCCE statistics (e.g., Figure 8 ) or SMCCE prediction (e.g. Fig. 9 for example).

[0277] Will refer to Figure 8 The SMCCE statistics of the example and Fig. 9A specific example of the information provided by NWDAF is described in more detail in FIG. 1 .

[0278] The following figures are created to explain specific examples of this specification. Since the names of specific devices or the names of specific signals / messages / fields described in the figures are presented by way of example, the technical features of this specification are not limited to the specific names used in the following figures.

[0279] Figure 8 A first example of SMCCE analysis according to an embodiment disclosed in this specification is shown.

[0280] Figure 8 The example of FIG. 4 shows a first example of SMCCE analysis performed by NWDAF. The first example of SMCCE analysis may be SMCCE statistics. Figure 8 The example shows a specific example of SMCCE statistics. Figure 8 An example of may be the analysis information output by NWDAF.

[0281] according to Figure 8 The example SMCCE statistics information may include an SMCCE analysis list (1..max). Here, "(1..max)" may refer to the number of SMCCE analysis information lists. The SMCCE analysis list is an SMCCE statistics information list derived by NWDAF and may provide the maximum number of SMCCE statistics information.

[0282] The list of SMCCE analysis information may include Figure 8 One or more information shown in the example of . For example, the SMCCE analysis information list may include one or more information in the DNN, S-NSSAI and UE list classified based on the experience level of the SMCC. Alternatively, the SMCCE analysis information list may also include information about SMF reallocation.

[0283] exist Figure 8 In the example, DNN may refer to a DNN to which SMCCE is applied. S-NSSAI may refer to an S-NSSAI to which SMCCE is applied.

[0284] The UE list classified based on the experience level of SMCC may refer to a UE list classified based on the experience level of SMCC (eg, the level of SMCC that the UE has experienced). Figure 8 As shown, the UE list classified by experience level based on SMCC may include one or more lists of high experience UE list, medium experience UE list and low experience UE list. In the UE list classified by experience level based on SMCC, SUPI may be used to identify UE.

[0285] exist Figure 8 In the example of , the high experience UE list may refer to a list of UEs with a high experience level of SMCC for a specific DNN and / or a specific S-NSSAI. The medium experience UE list may refer to a list of UEs with a medium experience level SMCC for a specific DNN and / or a specific S-NSSAI. The low experience UE list may refer to a list of UEs with a low experience level of SMCC for a specific DNN and / or a specific S-NSSAI or a list of UEs with an SMCC experience level 0 (e.g., UEs that do not experience SMCC). When classifying UEs according to the experience level of SMCC, the experience level applied by the NWDAF may be based on various values. For example, the NWDAF may classify the UEs based on the number of SMCCs experienced by the UE, or the NWDAF may classify the UEs based on the ratio of the experienced SMCC to the number of SM NAS messages sent by the UE, or the NWDAF may classify the UEs based on the sum of the backoff timer values ​​experienced by the UE.

[0286] exist Figure 8 In the example of , the information about SMF reallocation may represent information about SMF reallocation. The information about SMF reallocation may include a UE list and a candidate SMF list. The UE list may be a UE list for which the service SMF is recommended for reallocation. In the UE list, SUPI may be used to identify the UE. The candidate SMF list may represent a candidate SMF list, which may be a target SMF for SMF reallocation. In the candidate SMF list, the SMF ID may be used to identify the SMF.

[0287] according to Figure 8 NOTE for the example Figure 8 Each list of example SMCCE analyses may include DNN or S-NSSAI. Alternatively, Figure 8 Each list of example SMCCE analysis may include a DNN and an S-NSSAI.

[0288] The following figures are created to explain specific examples of this specification. Since the names of specific devices or the names of specific signals / messages / fields described in the figures are presented by way of example, the technical features of this specification are not limited to the specific names used in the following figures.

[0289] Fig. 9 A second example of SMCCE analysis according to an embodiment disclosed in this specification is shown.

[0290] Fig. 9 The example of FIG. 1 shows a specific example of SMCCE prediction.

[0291] Fig. 9The example of FIG. 4 shows a second example of SMCCE analysis performed by NWDAF. The second example of SMCCE analysis may be SMCCE prediction. Fig. 9 The example of FIG. 1 shows a specific example of SMCCE prediction. Fig. 9 An example of may be the analysis information output by NWDAF.

[0292] according to Fig. 9 The example SMCCE prediction information may include an SMCCE analysis list (1..max). Here, "(1..max)" may refer to the number of SMCCE analysis information lists. The SMCCE analysis list is an SMCCE prediction information list derived by NWDAF and may provide the maximum number of SMCCE prediction information.

[0293] The list of SMCCE analysis information may include Fig. 9 One or more information shown in the example of . For example, the SMCCE analysis information list may include one or more information in the DNN, S-NSSAI and UE list classified based on the experience level of the SMCC. And, the SMCCE analysis information list may include confidence information. Alternatively, the SMCCE analysis information list may also include information about SMF reallocation.

[0294] exist Fig. 9 In the example, DNN may refer to a DNN to which SMCCE is applied. S-NSSAI may refer to an S-NSSAI to which SMCCE is applied.

[0295] The UE list classified based on the experience level of SMCC may refer to a UE list classified based on the experience level of SMCC (eg, the level of SMCC that the UE has experienced). Fig. 9 As shown, the UE list classified by experience level based on SMCC may include one or more lists of high experience UE list, medium experience UE list and low experience UE list. In the UE list classified by experience level based on SMCC, SUPI may be used to identify UE.

[0296] exist Fig. 9In the example of , the high experience UE list may refer to a list of UEs with a high experience level of SMCC for a specific DNN and / or a specific S-NSSAI. The medium experience UE list may refer to a list of UEs with a medium experience level SMCC for a specific DNN and / or a specific S-NSSAI. The low experience UE list may refer to a list of UEs with a low experience level of SMCC for a specific DNN and / or a specific S-NSSAI or a list of UEs with an SMCC experience level 0 (e.g., UEs that do not experience SMCC). When classifying UEs according to the experience level of SMCC, the experience level applied by the NWDAF may be based on various values. For example, the NWDAF may classify the UEs based on the number of SMCCs experienced by the UE, or the NWDAF may classify the UEs based on the ratio of the experienced SMCC to the number of SM NAS messages sent by the UE, or the NWDAF may classify the UEs based on the sum of the backoff timer values ​​experienced by the UE.

[0297] exist Fig. 9 In the example of , the information about SMF reallocation may represent information about SMF reallocation. The information about SMF reallocation may include a UE list and a candidate SMF list. The UE list may be a UE list for which the service SMF is recommended for reallocation. In the UE list, SUPI may be used to identify the UE. The candidate SMF list may represent a candidate SMF list, which may be a target SMF for SMF reallocation. In the candidate SMF list, the SMF ID may be used to identify the SMF.

[0298] according to Fig. 9 NOTE for the example Fig. 9 Each list of example SMCCE analyses may include DNN or S-NSSAI. Alternatively, Figure 8 Each list of example SMCCE analysis may include a DNN and an S-NSSAI.

[0299] exist Fig. 9 In the example of , confidence can refer to the confidence of the prediction.

[0300] For reference, in Figure 8 Examples and Fig. 9 In the example of the example in which the list of low-experience UEs includes UEs that have never experienced SMCC, this is merely an example, and the scope of disclosure of this specification is not limited thereto. For example, the scope of disclosure of this specification may also include an example of providing a separate list for UEs that have never experienced SMCC.

[0301] NWDAF can provide Figure 8 Examples of and / or Fig. 9For example, NWDAF can provide service consumers (such as SMF) with some or all of the information shown in the example. Figure 8 Examples of and / or Fig. 9 Some or all of the information shown in the examples.

[0302] in addition, Figure 8 Examples of and / or Fig. 9 The information shown in the example is only an example, and the scope of disclosure of this specification is not limited thereto. For example, NWDAF can provide a service consumer (e.g., SMF) with Figure 8 Examples of and / or Fig. 9 Information not shown in the examples or with Figure 8 Examples of and / or Fig. 9 The information in the examples is in different forms of information.

[0303] For example, the NWDAF may provide a backoff timer value that should be provided to the UE on average, or a backoff timer value that can be provided to the UE on average, to a service consumer (e.g., SMF). Here, the backoff timer value provided on average or the backoff timer value that can be provided on average may be set to a different value for each of the high experience UE, the medium experience UE, and the low experience UE.

[0304] For example, NWDAF may provide information about how many UE SMCCs should be applied to a service consumer (e.g., SMF) or information about how many UE SMCCs may be applied to a service consumer (e.g., SMF). Here, for each of high experience UE, medium experience UE, and low experience UE, information about how many UE SMCCs should be applied or information about how many UE SMCCs may be applied may be set to different values.

[0305] For example, the NWDAF may provide a list of UEs to which SMCC should be applied at a high level, a list of UEs to which SMCC should be applied at a normal level, and / or a list of UEs to which SMCC should be applied at a low level, and a list of UEs to which SMCC should not be applied at a low level to a service consumer (e.g., SMF). Here, the NWDAF may provide the service consumer (e.g., SMF) with information on the average backoff timer value applicable to each list and a list of UEs for each level of applying SMCC.

[0306] In the following, reference is made to Fig.10 Examples of processes related to the above-mentioned SMCCE analysis will be described through various examples.

[0307] The following figures are created to explain specific examples of this specification. Since the names of specific devices or the names of specific signals / messages / fields described in the figures are presented by way of example, the technical features of this specification are not limited to the specific names used in the following figures.

[0308] Fig.10 An example of a process according to an embodiment disclosed in this specification is shown.

[0309] Fig.10 The example of FIG. 1 shows an example of a process related to SMCCE analysis. For example, Fig.10 The example describes the process of SMCCE analysis using UE data.

[0310] For reference, in Fig.10 In the example, the operation of NWDAF receiving UE data from UE through AMF is included, but this is only an example. For example, in the disclosure of this article, NWDAF can receive UE data from a service consumer (e.g., SMF) and an SMF different from the service consumer.

[0311] 1) SMF may request NWDAF for analysis information about the "session management congestion control experience" provided by NWDAF. For example, SMF may send a request message to NWDAF requesting analysis information about the "session management congestion control experience".

[0312] The request message sent by the SMF to the NWDAF may include the above parameters. For example, the request message may include parameters such as analysis ID, analysis report target, analysis filter information, and analysis target time period.

[0313] For reference, the SMF may not include UE information (e.g., one or more SUPIs) in the request message. In this case, in step 2) described later, the NWDAF may collect UE data for DNN and / or S-NSSAI from the UE data storage. The UE data storage may be, for example, a network node storing data related to the UE, such as a unified data repository (UDR) or the NWDAF. In addition, in step 3) described later, the NWDAF may provide the SMF ID to the AMF. By providing the SMF ID to the AMF, the NWDAF may determine the UE served by the SMF corresponding to the SMF ID.

[0314] In addition to the request message, the SMF may also include information about the serving AMF. Here, the information about the serving AMF may be in the form of information about the serving AMF of each UE. Alternatively, the information about the serving AMF may be information in the form of a serving AMF list. When the SMF additionally includes information about the serving AMF in the request message, some operations of performing step 3 performed by the NWDAF may be omitted. For example, the operation of the NWDAF querying the network storage function (NRF) for the serving AMF of the UE and obtaining information about the serving AMF from the NRF may be omitted.

[0315] The SMF may also include congestion level (e.g., high / medium / low, or high / medium / low, or level 1, 2, 3, etc.) information in the request message. The NWDAF may utilize the congestion level information for SMCCE analysis. For example, when the NWDAF derives (or performs) SMCCE analysis and / or when the NWDAF collects data for SMCCE analysis, the NWDAF may utilize the congestion level information.

[0316] For reference, in Fig.10 In the example, the SMF that performs step 1 may be an SMF that anticipates congestion, an SMF in which congestion has already begun, an SMF that attempts to initiate SM congestion control, or an SMF that initiates SM congestion control.

[0317] NWDAF may optionally perform the following steps 2) and / or 3). For reference, when step 3) is performed, steps 4) to 7) may be performed.

[0318] 2) NWDAF may collect data related to SM congestion control experience from a UE data storage (eg, UDR used as a data storage function, NWDAF, etc.).

[0319] The NWDAF may acquire necessary UE data from the UE data storage based on the information provided in step 1).

[0320] For example, in step 1), the SMF may have requested SMCCE analysis of DNN#1 and S-NSSAI#2 from the NWDAF. In this case, the NWDAF may request the UE's SMCC (SM congestion control) experience information / data for the PDU session associated with DNN#1 and S-NSSAI#2 from the UE data memory. Then, the NWDAF may obtain the UE's SMCC (SM congestion control) experience information / data for the PDU session associated with DNN#1 and S-NSSAI#2 from the UE data memory.

[0321] 3) In order to collect UE data related to SM congestion control experience, NWDAF can send a subscription request to all serving AMFs. For example, NWDAF receives UE data related to SMCCE from UE via AMF, and NWDAF can send a request message (e.g., Namf_EventExposure_Subscribe message) to AMF for subscribing to AMF's service, which provides AMF with UE data related to SMCCE. For reference, step 3) can be performed only when NWDAF has not subscribed to the service for collecting UE data related to SMCCE.

[0322] Here, NWDAF can configure (or set) the subscription request based on the information provided in step 1). For example, in step 1), SMF may have requested SMCCE analysis of DNN#1 and S-NSSAI#2 from NWDAF. In this case, NWDAF requests AMF for SMCC (SM congestion control) experience information / data of UE for PDU session associated with DNN#1 and S-NSSAI#2, and NWDAF can obtain SMCC (SM congestion control) experience information / data of UE for PDU session associated with DNN#1 and S-NSSAI#2 from AMF.

[0323] If the NWDAF has already obtained necessary UE data for some UEs in step 2), the NWDAF may not perform step 3) for these UEs.

[0324] 4) AMF may request UE to provide UE data related to SM congestion control experience. For example, AMF may send a request message to UE to request UE data related to SM congestion control experience (e.g., requesting UE data related to SMCC experience).

[0325] When NWDAF requests UE data collection for a specific UE, AMF may perform step 4 for the UE). For example, when AMF receives a subscription request message for collecting UE data for a specific UE from NWDAF in step 3), AMF may perform step 4 for the UE). Alternatively, instead of NWDAF providing UE information to AMF in step 3), DNN and / or S-NSSAI information may be provided to AMF. In this case, AMF may request UE data collection from a UE that has a corresponding DNN and / or S-NSSAI in a UE served by AMF as subscription information (e.g., UE context information).

[0326] The AMF may also request UE data collection from UEs for which a PDU session related to the DNN and / or S-NSSAI in the UE has not been created.

[0327] 5) For example, the UE may provide the AMF with UE data collected by the SMCCE.

[0328] For reference, for step 4) and step 5), a conventional NAS message may be extended and used, or a new NAS message may be defined and used.

[0329] For reference, the messages sent in step 4) and step 5) may be sent via 3GPP access, or may be sent via non-3GPP access. In order for the AMF to perform step 4), it may have to page the UE.

[0330] 6) AMF may provide the collected UE data to NWDAF. For example, AMF may send a Namf_EventExposure_Notify message including the collected UE data to NWDAF.

[0331] 7)AMF may store the collected UE data in the UE data storage.

[0332] For reference, step 7 may be performed optionally). For example, instead of storing the UE data in the UE data storage, the AMF may store the UE data provided from the UE in the UE context stored by itself (AMF).

[0333] 8) NWDAF may decide to include information related to SMF reallocation in the SMCCE analysis. For example, in the case where the SMF requests information related to SMF reallocation based on the number of UEs served by the SMF in step 1), etc., NWDAF may decide to include information related to SMF reallocation in the analysis. If NWDAF decides to include information related to SMF reallocation in its analysis, NWDAF may derive (or perform) SMF load analysis by leveraging traditional NF load analysis. Here, the target NF type of the SMF load analysis is set to SMF, and the SMF load analysis may be performed for a specific S-NSSAI.

[0334] For reference, step 8) may be performed optionally. For example, step 8) may be performed only if the NWDAF wishes to include information related to SMF reallocation in the SMCCE analysis.

[0335] 9) NWDAF may derive (or perform) SMF requested analysis (e.g., SMCCE analysis). For example, based on the data received in step 2) and / or the data received in step 6), optionally, based on the SMF load analysis derived in step 8), NWDAF may derive (or perform) SMCCE analysis.

[0336] NWDAF can collect various necessary information from other NFs and / or OAMs to derive (or perform) SMCCE analysis. For example, NWDAF can collect information about the total number of PDU sessions associated with DNNs and / or S-NSSAIs, information about the number of UEs that have created (or established) / existing PDU sessions associated with DNNs and / or S-NSSAIs, etc. from other NFs and / or OAMs. Here, the corresponding DNNs and / or S-NSSAIs can represent the DNNs and / or S-NSSAIs for the SMCCE analysis requested by the SMF in step 1) above.

[0337] In order to derive (or perform) SMCCE analysis, NWDAF may additionally use various analyses defined in the prior art (eg, UE communication analysis, UE mobility analysis, etc.).

[0338] 10) NWDAF may provide SMF with analysis information about SMCCE. For example, NWDAF may send a Nnwdaf_Anlayticsinfo_Request response message including SMCCE analysis information to SMF.

[0339] 11) The SMF may initiate SM congestion control (e.g., DNN-based congestion control and / or S-NSSAI-based congestion control). When applying SM congestion control, the SMF may consider fairness (e.g., fairness between UEs). For example, based on SMCCE analysis information (e.g., referring to Figure 8 Examples and Fig. 9 (See the SMCCE analysis information described in the example above) and considering fairness, SMF can apply SM congestion control.

[0340] As an example, the SMF may set the value of the backoff timer provided to the UE based on the SMCCE analysis information. For example, the SMF may send a NAS SM reject message with a short backoff timer value to the UE included in the high experience UE list, and the SMF may send a NAS SM reject message with a long backoff timer value to the UE included in the low experience UE list.

[0341] As another example, the SMF may not apply SM congestion control to UEs included in the high experience UE list, and the SMF may apply SM congestion control to UEs included in the medium experience UE list and UEs included in the low experience UE list.

[0342] As another example, for each list (e.g., a list of high experience UEs, a list of medium experience UEs, a list of low experience UEs), an applicable backoff timer or a range of backoff timers (example: minimum and maximum values ​​of backoff timer values) may be set in the SMF. Alternatively, the NWDAF may provide a backoff timer or a range of backoff timers (example: minimum and maximum values ​​of backoff timer values) that may be applied to each list (e.g., a list of high experience UEs, a list of medium experience UEs, a list of low experience UEs) of the SMF by including it in the SMCCE analysis. Then, based on the backoff timer or the range of backoff timers (example: minimum and maximum values ​​of backoff timer values) that may be applied to each list (i.e., a list of high experience UEs, a list of medium experience UEs, a list of low experience UEs), the SMF may provide a backoff timer value to the UEs included in each list.

[0343] As another example, for each list (i.e., list of high experience UEs, list of medium experience UEs, list of low experience UEs), the number of UEs to which SMCC should be applied may be set in the SMF. Alternatively, the NWDAF may provide the SMF by including the number of UEs to which SMCC should be applied for each list (i.e., list of high experience UEs, list of medium experience UEs, list of low experience UEs) in the SMCCE analysis. The SMF may then apply SMCC based on the number of UEs to which SMCC should be applied for each list (i.e., list of high experience UEs, list of medium experience UEs, list of low experience UEs).

[0344] As another example, NWDAF may provide information about the UEs to which SMCC should be applied for each list (i.e., list of high experience UEs, list of medium experience UEs, list of low experience UEs) by including the information in the SMCCE analysis. Then, SMF may apply SMCC for these UEs.

[0345] As another example, the various examples described above (various examples in which SMF applies SMCC) may be used by SMF in combination.

[0346] The backoff timer or the range (i.e., min and max) of the backoff timer that can be applied and the number of UEs to which SMCC should be applied for each list (i.e., list of high experience UEs, list of medium experience UEs, list of low experience UEs) may be set in the SMF. Alternatively, the NWDAF may provide the backoff timer or the range (i.e., min and max) of the backoff timer that can be applied and the number of UEs to which SMCC should be applied for each list (i.e., list of high experience UEs, list of medium experience UEs, list of low experience UEs) to the SMF by including it in the SMCCE analysis. Then, based on the backoff timer or the range (i.e., min and max) of the backoff timer that can be applied and the number of UEs to which SMCC should be applied for each list (i.e., list of high experience UEs, list of medium experience UEs, list of low experience UEs), the SMF may apply the backoff timer to as many UEs as the number of UEs corresponding to each list.

[0347] If the SMF has started SM congestion control before executing step 11), the SMF can apply SM congestion control based on the SMCCE analysis provided from the NWDAF.

[0348] 12) In the above step 10), if the information about SMF reallocation is included in the SMCCE analysis, the SMF can request SMF reallocation from the serving AMF for all UEs included in the "UE list for which the serving SMF reallocation is recommended". For example, the SMF can send an SMF reallocation request message to the AMF.

[0349] When the NWDAF sends the SMCCE analysis including information related to SMF reallocation to the SMF in step 10), the NWDAF may not include "a list of candidate SMFs that can be target SMFs for SMF reallocation" in the SMCCE analysis. In this case, the SMF may send an SMF reallocation request message (e.g., "a list of candidate SMFs that can be target SMFs for SMF reallocation") to the AMF without this information. The AMF may then perform an operation of selecting / determining a target SMF for SMF reallocation.

[0350] To request SMS reallocation, the SMF may use the Namf_Communication_N1N2MessageTransfer service operation and an SMF reallocation request indication (eg, SMF Reallocation Request Indication). Information about the candidate SMF may be introduced as a new parameter of the service operation (eg, Namf_Communication_N1N2MessageTransfer).

[0351] For reference, although in Fig.10 In the example shown in FIG. 1 , step 12) is performed after step 11), but this is only an example. Step 12) may be performed before step 11).

[0352] For reference, even if the above example and the information about SMF reallocation are not included in the SMCCE analysis, the SMF may perform SMF reallocation. That is, even if the information about SMF reallocation is not included in the SMCCE analysis, the SMF may perform SMF reallocation. For example, the SMF may perform SMF reallocation based on the setting of the SMF. Here, the SMF setting may be, for example, a setting for performing SMF reallocation for a list of high-experience UEs when the number of UEs included in the list is several or more. For another example, the SMF configuration may be a configuration for performing SMF reallocation on all UEs included in the high-experience UE list.

[0353] Can be expanded and used Fig.10 The various service operations shown in the example (e.g., the operations described in step 1) to step 12)). In addition, different Fig.10 Other service operations (eg, traditional service operations or newly defined service operations) of the various service operations shown in the examples.

[0354] For reference, in Fig.10 In the example, a request-response model related to Nnwdaf service operation is shown (for example, when SMF requests SMCCE analysis from NWDAF, NWDAF provides SMCCE analysis to SMF), but this is only an example. The method proposed in this specification can also be applied by extending to a subscription notification model (for example, when SMF requests a subscription related to SMCCE analysis from NWDAF, when an event related to SMCCE analysis occurs, NWDAF sends SMCCE analysis to SMF).

[0355] The NF provided with the UE data from the UE may be different from Fig.10 In this case, the NWDAF may request and collect UE data from the NF that collects UE data instead of the AMF. For example, in step 3), the NWDAF may request and collect UE data from the SMF instead of the AMF.

[0356] For reference, in the above various examples, NWDAF provides SMCCE analysis to SMF at the request of SMF. However, this is just an example, and NWDAF can derive (or perform) SMCCE analysis without SMF request and provide SMCCE analysis to SMF.

[0357] For reference, the various examples described above may be modified / extended and applied to mobility management congestion control (MMCC). For example, the UE may collect MMCC experience information / data and provide the collected MMCC experience information / data to the network. The NWDAF may then provide the AMF with an analysis of the MMCC experience using the collected MMCC experience information / data. The AMF may apply MMCC considering fairness by receiving an analysis of the MMCC experience from the NWDAF. In this case, the items / information / parameters described in the various examples above regarding session management and SMCC may be interpreted / applied based on mobility management and MMCC. For example, in the various examples related to the above SMCC, the SM NAS message may be understood as an MM NAS message.

[0358] In the following, reference will be made to Fig.11 Examples and Fig.12 The example of the operation of the network (e.g., SMF, NWDAF, AMF, UE data storage, etc.) described in the disclosure of this specification and the example of the operation of the terminal are described in detail. For reference, the following Fig.11 Examples and Fig.12 The operations described in the example are only examples, and the network and the terminal can not only perform Fig.11 Examples and Fig.12 In addition to the operations described in the examples, the operations described in various examples disclosed in this specification can also be performed.

[0359] The following figures are created to explain specific examples of this specification. Since the names of specific devices or the names of specific signals / messages / fields described in the figures are presented by way of example, the technical features of this specification are not limited to the specific names used in the following figures.

[0360] Fig.11 An example of the operation of a network according to an embodiment disclosed in this specification is shown.

[0361] Fig.11 The operation of the service consumer (e.g., SMF) described in various examples disclosed in this specification can be represented. Among the various network nodes that can be service consumers, the focus will be on the SMF execution Fig.11 An example of the operation is described Fig.11 .

[0362] In step S1101, the SMF may send a request message. For example, the SMF may send a request message to the NWDAF requesting SMCCE analysis. The request message may include, for example, at least one of an analysis ID (analysis ID), a target of an analysis report, analysis filter information (analysis filter information), or an analysis target time period. For example, step S1101 may be in the form of Fig.10 The same method as described in step 1) is performed.

[0363] In step S1102, the SMF may receive a response message. For example, the NWDAF may send a response message including SMCCE analysis information to the SMF in response to the request message. The SMF may receive a response message including SMCCE analysis information. The SMCCE analysis information may include, for example, one or more lists of high experience user equipment lists, medium experience user equipment lists, or low experience user equipment lists. For example, step S1102 may be performed in the same manner as Fig.10 The same method as described in step 10) is performed.

[0364] When NWDAF receives the request message from SMF, it can collect data to analyze SMCCE. For example, NWDAF can request data related to SMCCE from UE or SMF. NWDAF can receive data related to SMCCE from UE or SMF. NWDAF can perform (or derive) SMCCE analysis based on the received data. NWDAF can send a response message to SMF by including SMCCE analysis information in the response message of step S1102.

[0365] The following figures are created to explain specific examples of this specification. Since the names of specific devices or the names of specific signals / messages / fields described in the figures are presented by way of example, the technical features of this specification are not limited to the specific names used in the following figures.

[0366] Fig.12 An example of operations of a terminal and a network according to an embodiment disclosed in this specification is shown.

[0367] Fig.12 UE, a first SMF (first SMF), NWDAF, and a second SMF (second SMF) are shown. Here, the first SMF may be an SMF that requests SMCCE analysis from NWDAF. The second SMF may be an SMF that provides data related to SMCCE to NWDAF. Fig.12 A second SMF is shown in FIG. 1 , but this is only an example, and the NWDAF may receive data related to the SMCCE from one or more second SMFs.

[0368] In step S1201, the first SMF may send an analysis request message to the NWDAF. Here, the analysis request message may be a request message for requesting SMCCE analysis. For example, step S1201 may be in the same manner as Fig.11 Step S1101 and / or Fig.10 When the first SMF intends to apply SM congestion control using SMCCE analysis, the first SMF may send an analysis request message to the NWDAF.

[0369] For reference, in order for the SMF to utilize the SMCCE analysis information, the SMF may need to request the SMCCE analysis information from the NWDAF before applying congestion control due to the formation of potential congestion conditions.

[0370] In step S1202, the NWDAF may send a data request message to the second SMF. For example, step S1202 may be performed in the same manner as Fig.10 The data request message may be Nsmf_EventExposure_Subscribe.

[0371] For example, in step S1202, Fig.10 In step 3), the NWDAF may send a request message to the second SMF, the request message being used to subscribe the data related to the SMCCE to the service provided by the SMF. For reference, if the NWDAF has sent a data request message to the second SMF before executing step S1202, step S1202 may be omitted. The NWDAF may send a data request message to all SMFs serving the DNN and / or S-NSSAI included in the analysis filter information received in step S1201.

[0372] In step S1203, the second SMF may send data to the NWDAF. Here, the data sent by the second SMF may be data related to the SMCCE. The second SMF may provide the NWDAF with the following information: Figure 7 For example, when applying SM congestion control to a UE served by an SMF, the second SMF may collect data related to SMCCE. In addition, the second SMF may provide the collected data related to SMCCE to the NWDAF. For reference, the first SMF may also provide data to the NWDAF like the second SMF.

[0373] In step S1204, the NWDAF may send an analysis response message to the first SMF. Before executing step S1204, the NWDAF may perform (or derive) SMCCE analysis based on the data received from the second SMF. For example, the NWDAF may Fig.10 The NWDAF may then send an analysis response message including the SMCCE analysis information to the first SMF. For example, the NWDAF may send an analysis response message including the SMCCE analysis information to the first SMF in the same manner as step 9). Fig.11 Step S1102 and / or Fig.10 The analysis response message is sent to the first SMF in the same manner as step 10.

[0374] In step S1205, the first SMF may send a message related to congestion control to the UE. For example, the first SMF may send a NAS reject message or a NAS command message. The NAS reject message or the NAS command message may be, for example, a message including information related to congestion control applied by the first SMF. The first SMF may determine the value of the backoff timer applied to the UE for SM congestion control based on the SMCCE analysis information. The NAS reject message sent to the UE may include the value of the backoff timer. The NAS reject message may be, for example, a PDU session creation reject message or a PDU session modification reject message. The NAS command message may be, for example, a PDU session release command message. The NAS reject message may be a message sent in response to a NAS request message sent by the UE to the SMF.

[0375] As described in the disclosure of this specification, the SMF may perform SM congestion control considering the fairness of the UE. For example, the SMF may perform SM congestion control considering fairness based on the experience information / data related to SM congestion control provided by the UE (or an NF such as an SMF). For example, the NWDAF may perform SMCCE analysis based on the SM congestion control related experience information / data from the UE (or an NF such as an SMF). The SMF may perform SM congestion control based on the SMCCE analysis provided from the NWDAF. Therefore, the fairness of the UE related to SM congestion control may be improved. Improving the fairness of the UE may lead to an improvement in the user's service experience. For example, assume that a new PDU session must be created, and when the service is terminated (or when the application execution is terminated), the PDU session is released so that UE#1 receives a specific service (or executes an application). In this case, as in the following example of two UEs, the fairness of the UE is not considered, so that the user's service experience may be poor. As a first example, in this case, UE#1 may receive a PDU session creation rejection message from the SMF, the message mainly including a long backoff timer value for the PDU session creation request message. For a second example, UE#2 may receive a PDU session creation rejection message from the SMF, the message mainly including a short backoff timer value for the PDU session creation request message under the same circumstances, or UE#2 may receive a PDU session creation permission message from the SMF. In this case, the user of UE#1 may have a worse service experience than the user of UE#2. According to the disclosure of this specification, since the fairness of UEs related to SM congestion control is improved, the service experience of users can be improved.

[0376] As described in the disclosure of this specification, the NWDAF may collect data (e.g., UE data) related to the SM congestion control experience. For example, the NWDAF may collect data (e.g., UE data) from the UE via the AMF. As another example, the NWDAF may collect data (e.g., UE data) from the SMF. The data (e.g., UE data) related to the SM congestion control experience may be information associated with a PDU session of a specific DNN and / or a specific S-NSSAI.

[0377] As described in the disclosure of this specification, the SMF may request SMCCE analysis from the NWDAF. Then, the SMF may receive SMCCE analysis information from the NWDAF. The SMF may apply SM congestion control to the UE based on the SMCCE analysis information. Since the SMF applies SMC congestion control in consideration of the SMCCE analysis information, the fairness problem between UEs to which SM congestion control is applied may be solved.

[0378] As described in the disclosure of this specification, the NWDAF may perform (or derive) SMCCE analysis based on SMCCE related data (e.g., UE data) collected by the NWDAF. The NWDAF may provide SMCCE analysis information to a service consumer (e.g., SMF). For example, when a service consumer (e.g., SMF) requests SMCCE analysis from the NWDAF, the SMCCE analysis information may be provided to the service consumer (e.g., SMF). The service consumer (e.g., SMF) may then apply SM congestion control based on the SMCCE analysis information.

[0379] For reference, the operation of the terminal (eg, UE) described in this specification may be performed by Figures 1 to 3 For example, a terminal (eg, UE) may be Figure 1 The first device 100 or the second device 200 of the present invention may be a first device 100 or a second device 200. For example, the operation of the terminal (e.g., UE) described herein may be processed by one or more processors 102 or 202. The operation of the terminal described herein may be stored in one or more memories 104 or 204 in the form of instructions / programs (e.g., instructions, executable codes) that may be executed by one or more processors 102 or 202. The one or more processors 102 or 202 control the one or more memories 104 or 204 and the one or more transceivers 106 or 206, and may perform the operation of the terminal (e.g., UE) described herein by executing the instructions / programs stored in the one or more memories 104 or 204.

[0380] In addition, instructions for executing the operation of the terminal (e.g., UE) described in the disclosure of this specification may be stored in a non-volatile computer-readable storage medium recording the instructions. The storage medium may be included in one or more memories 104 or 204. And, the instructions recorded in the storage medium may be executed by one or more processors 102 or 202 to perform the operation of the terminal (e.g., UE) described in the disclosure of this specification.

[0381] For reference, the operations of the network nodes (e.g., AMF, SMF, NWDAF, UE data storage, etc.) or base stations (e.g., NG-RAN, gNB, gNB (NB-IoT), gNB (NR) eNB, RAN, etc.) described herein may be described below. Figures 1 to 3 For example, a network node or base station may be Figure 1 The first device 100a or Figure 1The second device 100b of the present invention. For example, the operation of the network node or base station described herein may be processed by one or more processors 102 or 202. The operation of the terminal described herein may be stored in one or more memories 104 or 204 in the form of instructions / programs (e.g., instructions, executable codes) that may be executed by one or more processors 102 or 202. The one or more processors 102 or 202 may perform the operation of the network node or base station described herein by controlling one or more memories 104 or 204 and one or more transceivers 106 or 206 and executing the instructions / programs stored in one or more memories 104 or 204.

[0382] In addition, instructions for executing the operations of the network node or base station described in the disclosure of this specification may be stored in a non-volatile (or non-transitory) computer-readable storage medium. The storage medium may be included in one or more memories 104 or 204. And, the instructions recorded in the storage medium are executed by one or more processors 102 or 202, thereby executing the operations of the network node or base station.

[0383] In the above, the preferred embodiment has been exemplarily described, but the disclosure of the present specification is not limited to this specific embodiment, and thus, improvements, modifications, and changes are possible.

[0384] In the above exemplary system, these methods are described as a series of steps or blocks based on the flowchart, but are not limited to the order of the steps described, and some steps may occur in a different order or occur simultaneously with other steps as described above. In addition, those skilled in the art will understand that the steps shown in the flowchart are not exclusive, and other steps may be included, or one or more steps of the flowchart may be deleted without affecting the scope of rights.

[0385] The claims described herein can be combined in various ways. For example, the technical features of the method claims of this specification can be combined and implemented as a device, and the technical features of the device claims of this specification can be combined and implemented as a method. In addition, the technical features of the method claims of this specification and the technical features of the device claims can be combined to be implemented as a device, and the technical features of the method claims of this specification and the technical features of the device claims can be combined and implemented as a method.

Claims

1. A method for performing communications related to congestion control, the method being performed by a session management function (SMF) and comprising the following steps: Send a request message for session management congestion control experience SMCCE analysis to the network data analysis function NWDAF, The request message includes a data network name DNN for a protocol data unit PDU session associated with a session management congestion control SMCC and / or single network slice selection auxiliary information S-NSSAI for the PDU session associated with the SMCC; and In response to the request message from the NWDAF, receiving a response message including SMCCE analysis information, the SMCCE analysis information including a list of user equipments UE classified based on the experience level of the SMCC, Among them, the list of UEs classified based on the experience level of the SMCC includes one or more of a list of high-experience UEs, a list of medium-experience UEs, or a list of low-experience UEs, the high-experience UE has a higher experience level for the SMCC of the DNN and / or the S-NSSAI, the medium-experience UE has a medium experience level for the SMCC of the DNN and / or the S-NSSAI, and the low-experience UE has a lower experience level for the SMCC of the DNN and / or the S-NSSAI.

2. The method according to claim 1, further comprising: Session management congestion control is applied based on the SMCCE analysis information.

3. The method according to claim 2, wherein: The step of applying the session management congestion control also includes: Based on the SMCCE analysis information, a backoff timer value to be provided to one or more UEs to which the session management congestion control is to be applied is determined.

4. The method according to claim 3, in, The backoff timer value to be provided to one or more UEs is determined according to which list of the high experience UE list, the medium experience UE list, or the low experience UE list the one or more UEs are respectively included in.

5. The method according to claim 1, in, The SMCCE analysis information is information determined by the NWDAF based on input data collected by the NWDAF.

6. The method according to claim 1, in, The request message also includes one or more information of an analysis ID set to “session management congestion control experience”, an analysis report target including one or more SUPIs, or an analysis target time period.

7. A session management function (SMF) for performing communications related to congestion control, wherein: The SMF includes: at least one processor; and at least one memory for storing instructions and operatively connected to the at least one processor; The operations performed by the at least one processor based on the execution of the instruction include: Send a request message for session management congestion control experience SMCCE analysis to the network data analysis function NWDAF, The request message includes a data network name DNN for a protocol data unit PDU session associated with a session management congestion control SMCC and / or single network slice selection auxiliary information S-NSSAI for the PDU session associated with the SMCC; and In response to the request message from the NWDAF, receiving a response message including SMCCE analysis information, the SMCCE analysis information including a list of user equipments UE classified based on the experience level of the SMCC, Among them, the list of UEs classified based on the experience level of the SMCC includes one or more of a list of high-experience UEs, a list of medium-experience UEs, or a list of low-experience UEs, the high-experience UE has a higher experience level for the SMCC of the DNN and / or the S-NSSAI, the medium-experience UE has a medium experience level for the SMCC of the DNN and / or the S-NSSAI, and the low-experience UE has a lower experience level for the SMCC of the DNN and / or the S-NSSAI.

8. A method for performing communications related to congestion control, the method being performed by a network data analysis function (NWDAF) and comprising the steps of: Receive a request message from the session management function SMF requesting session management congestion control experience SMCCE analysis, The request message includes a data network name DNN for a protocol data unit PDU session associated with a session management congestion control SMCC and / or single network slice selection auxiliary information S-NSSAI for the PDU session associated with the SMCC; and In response to the request message, sending a response message including SMCCE analysis information to the SMF, wherein the SMCCE analysis information includes a list of user equipments UE classified based on the experience level of the SMCC, Among them, the list of UEs classified based on the experience level of the SMCC includes one or more of a list of high-experience UEs, a list of medium-experience UEs, or a list of low-experience UEs, the high-experience UE has a higher experience level for the SMCC of the DNN and / or the S-NSSAI, the medium-experience UE has a medium experience level for the SMCC of the DNN and / or the S-NSSAI, and the low-experience UE has a lower experience level for the SMCC of the DNN and / or the S-NSSAI.

9. The method according to claim 8, in, The SMCCE analysis information is used for application session management congestion control.

10. The method according to claim 8, further comprising the steps of: Collect data related to the SMCCE analysis for use in the SMCCE analysis information.

11. The method according to claim 10, further comprising the steps of: The SMCCE analysis information is determined based on the collected data.

12. The method according to claim 8, in, The request message also includes one or more information of an analysis ID set to “session management congestion control experience”, an analysis report target including one or more SUPIs, or an analysis target time period.

Images