Support measures for WLAN usage experience analysis using UE WLAN user data

Abstract

A method for supporting the analysis of WLAN usage experience using UE (user equipment) WLAN (wireless local area network) user data and a device supporting such analysis are provided. A PCF (policy and charging function) operating in a wireless communication system requests analysis information related to the WLAN from a NWDAF (network data analytics function), receives the analysis information related to the WLAN from the NWDAF in response to the request, and updates a policy for WLAN selection based on the analysis information related to the WLAN.

Description

Technology Field

[0001] This specification relates to a method for supporting the analysis of WLAN usage experience using UE (user equipment) WLAN (wireless local area network) user data. Background Technology

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

[0003] Work has begun at the ITU (International Telecommunication Union) and 3GPP to develop requirements and specifications for new radio (NR) systems. 3GPP must identify and develop the technical components necessary to successfully standardize NR in a timely manner, satisfying both urgent market demands and the longer-term requirements presented by the ITU-R (ITU Radio Communication Sector) IMT (International Mobile Telecommunications)-2020 process. Furthermore, NR must be able to utilize any spectrum band up to at least 100 GHz so that it can be used for wireless communication even in the distant future.

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

[0005] User equipment (UE) can select a wireless local area network (WLAN) access network using access network discovery and selection policy. The selected WLAN access network can be used for traffic offloading (i.e., sending traffic to a WLAN outside of a protocol data unit (PDU) session) and registration with the 5GC using non-3GPP access network selection information. The problem to be solved

[0006] It may be necessary to utilize actual WLAN usage data from UEs to support the analysis of WLAN usage experience and to consider this in the selection of access networks and selection policies. means of solving the problem

[0007] In one embodiment, a method is provided that is performed by a policy and charging function (PCF) operating in a wireless communication system. The method includes the steps of requesting analysis information related to a wireless local area network (WLAN) from a network data analytics function (NWDAF), receiving analysis information related to the WLAN from the NWDAF in response to the request, and updating a policy for WLAN selection based on the analysis information related to the WLAN.

[0008] In another embodiment, a method is provided that is performed by user equipment (UE) operating in a wireless communication system. The method comprises the steps of collecting data on wireless local area network (WLAN) usage experience and transmitting the collected data on WLAN usage experience to a policy and charging function (PCF) or a network function (NF).

[0009] In another aspect, a device for implementing the above method is provided. Effects of the invention

[0010] This specification may have various effects.

[0011] For example, PCF can update WLANSP to achieve optimal WLAN performance by utilizing new analytics information related to WLAN usage experience.

[0012] For example, PCF can update WLANSP based on data related to the WLAN usage experience provided by the UE so that the actual UE's WLAN usage experience is continuously reflected.

[0013] For example, other NFs besides PCF can also update WLAN-related settings based on data related to WLAN usage experience provided by the UE.

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

[0015] FIG. 1 shows an example of a communication system to which the implementation of the present specification is applied. FIG. 2 shows an example of a wireless device to which the implementation of the present specification applies. FIG. 3 shows an example of a wireless device to which the implementation of the present specification applies. FIG. 4 shows an example of a UE to which the implementation of the present specification applies. FIG. 5 shows an example of a 5G system architecture to which the implementation of the present specification is applied. FIG. 6 illustrates an example of a method performed by a PCF to which the implementation of the present specification applies. FIG. 7 illustrates an example of a method performed by a UE to which the implementation of the present specification applies. FIG. 8 illustrates an example of a procedure for collecting data on the WLAN usage experience of a UE to which the implementation of the present specification applies. FIG. 9 illustrates an example of a procedure for requesting / transmitting analysis information based on data regarding the WLAN usage experience of a UE to which the implementation of the present specification applies. Specific details for implementing the invention

[0016] The following techniques, devices, and systems may be applied to various wireless multiple access systems. Examples of multiple access systems include code division multiple access (CDMA) systems, frequency division multiple access (FDMA) systems, time division multiple access (TDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and multicarrier frequency division multiple access (MC-FDMA) systems. CDMA may be implemented through wireless technologies such as universal terrestrial radio access (UTRA) or CDMA2000. TDMA may be implemented through wireless technologies such as global system for mobile communications (GSM), general packet radio service (GPRS), or enhanced data rates for GSM evolution (EDGE). OFDMA can be implemented through wireless technologies such as IEEE (Institute of Electrical and Electronics Engineers) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, or E-UTRA (evolved UTRA). UTRA is part of UMTS (universal mobile telecommunications system). 3GPP (3rd generation partnership project) LTE (long-term evolution) is part of E-UMTS (evolved UMTS) using E-UTRA.3GPP LTE uses OFDMA in the downlink (DL) and SC-FDMA in the uplink (UL). Evolutions of 3GPP LTE include LTE-A (advanced), LTE-A Pro, and / or 5G NR (new radio).

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

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

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

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

[0021] In this specification, "at least one of A and B" may mean "only A," "only B," or "both A and B." Additionally, in this specification, the expressions "at least one of A or B" or "at least one of A and / or B" may be interpreted as synonymous with "at least one of A and B."

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

[0023] Additionally, parentheses used in this specification may mean "for example." Specifically, when indicated as "control information (PDCCH)," "PDCCH" may be proposed as an example of "control information." In other words, "control information" in this specification is not limited to "PDCCH," and "PDCCH" may be proposed as an example of "control information." Furthermore, even when indicated as "control information (i.e., PDCCH)," "PDCCH" may be proposed as an example of "control information."

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

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

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

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

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

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

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

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

[0032] Wireless devices (100a to 100f) represent devices that perform communication using radio access technology (RAT) (e.g., 5G NR or LTE) and may also be referred to as communication / wireless / 5G devices. Wireless devices (100a to 100f) may include, but are not limited to, robots (100a), vehicles (100b-1 and 100b-2), extended reality (XR) devices (100c), portable devices (100d), home appliances (100e), IoT devices (100f), and artificial intelligence (AI) devices / servers (400). For example, vehicles may include vehicles with wireless communication capabilities, autonomous vehicles, and vehicles capable of performing communication between vehicles. Vehicles may include unmanned aerial vehicles (UAVs) (e.g., drones). XR devices may include AR / VR / mixed reality (MR) devices and may be implemented in the form of head-mounted devices (HMDs) and head-up displays (HUDs) mounted on vehicles, televisions, smartphones, computers, wearable devices, home appliances, digital signs, vehicles, robots, etc. Portable devices may include smartphones, smart pads, wearable devices (e.g., smartwatches or smart glasses), and computers (e.g., laptops). Home appliances may include TVs, refrigerators, and washing machines. IoT devices may include sensors and smart meters.

[0033] In this specification, wireless devices (100a to 100f) may be referred to as user equipment (UE). The UE may include, for example, a mobile phone, a smartphone, a laptop computer, a digital broadcasting terminal, a PDA (personal digital assistant), a PMP (portable multimedia player), a navigation system, a slate PC, a tablet PC, an ultrabook, a vehicle, a vehicle with autonomous driving capabilities, a connected car, a UAV, an AI module, a robot, an AR device, a VR device, an MR device, a hologram device, a public safety device, an MTC device, an IoT device, a medical device, a fintech device (or financial device), a security device, a weather / environment device, a 5G service-related device, or a device related to the Fourth Industrial Revolution.

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

[0035] For example, a VR device may include a device for implementing objects or backgrounds in a virtual environment. For example, an AR device may include a device that implements objects or backgrounds in a virtual world by connecting them to objects or backgrounds in a real world. For example, an MR device may include a device that implements objects or backgrounds in a virtual world by merging them with objects or backgrounds in a real world. For example, a holographic device may include a device for implementing a 360-degree stereoscopic image by recording and playing back stereoscopic information using the phenomenon of light interference that occurs when two laser lights called holograms meet.

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

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

[0038] For example, a medical device may be a device used for the purpose of diagnosing, treating, alleviating, curing, or preventing a disease. For example, a medical device may be a device used to diagnose, treat, alleviate, or correct an injury or damage. For example, a medical device may be a device used for the purpose of examining, replacing, or modifying a structure or function. For example, a medical device may be a device used for the purpose of regulating pregnancy. For example, a medical device may include a therapeutic device, a driving device, a (in vitro) diagnostic device, a hearing aid, or a surgical device.

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

[0040] For example, a fintech device may be a device capable of providing financial services such as mobile payments. For example, a fintech device may include a payment device or a POS system.

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

[0042] Wireless devices (100a to 100f) can be connected to a network (300) through a base station (200). AI technology may be applied to the wireless devices (100a to 100f), and the wireless devices (100a to 100f) can be connected to an AI server (400) through the network (300). The network (300) can be configured using a 3G network, a 4G (e.g., LTE) network, a 5G (e.g., NR) network, and a network after 5G. The wireless devices (100a to 100f) may communicate with each other through the base station (200) / network (300), but they may also communicate directly (e.g., sidelink communication) without going through the base station (200) / network (300). For example, vehicles (100b-1, 100b-2) can communicate directly (e.g., V2V (vehicle-to-vehicle) / V2X (vehicle-to-everything) communication). Also, IoT devices (e.g., sensors) can communicate directly with other IoT devices (e.g., sensors) or other wireless devices (100a to 100f).

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

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

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

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

[0047] Augmented Reality is a collective term for VR, AR, and MR. VR technology provides real-world objects or backgrounds solely as CG images, AR technology provides virtual CG images superimposed on images of real objects, and MR technology is a CG technology that mixes and combines virtual objects with the real world. MR technology is similar to AR technology in that it displays real-world and virtual objects together. However, there is a difference in that while virtual objects in AR technology are used to complement real-world objects, virtual and real objects in MR technology are used as equal entities.

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

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

[0050] Frequency range definition Frequency range Subcarrier spacing FR1 450MHz - 6000MHz 15, 30, 60kHz FR2 24250MHz - 52600MHz 60, 120, 240kHz

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

[0052] Frequency range definition Frequency range Subcarrier spacing FR1 410MHz - 7125MHz 15, 30, 60kHz FR2 24250MHz - 52600MHz 60, 120, 240kHz

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

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

[0055] Referring to FIG. 2, the first wireless device (100) and the second wireless device (200) can transmit and receive wireless signals to / from an external device via various RATs (e.g., LTE and NR).

[0056] In FIG. 2, {the first wireless device (100) and the second wireless device (200)} may correspond to at least one of the {wireless devices (100a~100f) and base station (200)}, {wireless devices (100a~100f) and wireless devices (100a~100f)} and / or {base station (200) and base station (200)} of FIG. 1.

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

[0058] The processing chip (101) may include at least one processor, such as a processor (102), and at least one memory, such as a memory (104). FIG. 2 is shown as an example in which the memory (104) is included in the processing chip (101). Additionally and / or generally, the memory (104) may be placed outside the processing chip (101).

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

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

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

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

[0063] The processing chip (201) may include at least one processor, such as a processor (202), and at least one memory, such as a memory (204). FIG. 2 is shown as an example in which 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).

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

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

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

[0067] Hereinafter, hardware elements of the wireless device (100, 200) will be described in more detail. Although not limited thereto, one or more protocol layers may be implemented by one or more processors (102, 202). For example, one or more processors (102, 202) may implement one or more layers (e.g., functional layers such as a PHY (physical) layer, a MAC (media access control) layer, a RLC (radio link control) layer, a PDCP (packet data convergence protocol) layer, a RRC (radio resource control) layer, and an SDAP (service data adaptation protocol) layer). One or more processors (102, 202) may generate one or more PDUs (protocol data units) and / or one or more SDUs (service data units) according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification. One or more processors (102, 202) may generate messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification. One or more processors (102, 202) may generate a signal (e.g., baseband signal) containing a PDU, SDU, message, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification and provide it to one or more transceivers (106, 206). One or more processors (102, 202) may receive a signal (e.g., baseband signal) from one or more transceivers (106, 206) and may obtain a PDU, SDU, message, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification.

[0068] One or more processors (102, 202) may be referred to as controllers, microcontrollers, microprocessors, and / or microcomputers. One or more processors (102, 202) may be implemented by hardware, firmware, software, and / or a combination thereof. For example, one or more application-specific integrated circuits (ASICs), one or more digital signal processors (DSPs), one or more digital signal processing devices (DSPDs), one or more programmable logic devices (PLDs), and / or one or more field programmable gate arrays (FPGAs) may be included in one or more processors (102, 202). Descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed herein may be implemented using firmware and / or software, and the firmware and / or software may be implemented to include modules, procedures, and functions. Firmware or software configured to perform the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification may be included in one or more processors (102, 202) or stored in one or more memories (104, 204) and driven by one or more processors (102, 202). The descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification may be implemented using firmware or software in the form of code, instructions, and / or sets of instructions.

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

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

[0071] One or more transceivers (106, 206) may be connected to one or more antennas (108, 208). One or more transceivers (106, 206) may be configured to transmit and receive user data, control information, wireless signals / channels, etc., as described in the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed herein through one or more antennas (108, 208). In this specification, one or more antennas (108, 208) may be a plurality of physical antennas or a plurality of logical antennas (e.g., antenna ports).

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

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

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

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

[0076] Wireless devices can be implemented in various forms depending on the use example / service (see FIG. 1).

[0077] Referring to FIG. 3, the wireless device (100, 200) may correspond to the wireless device (100, 200) of FIG. 2 and may be composed of various components, devices / parts and / or modules. For example, each wireless device (100, 200) may include a communication device (110), a control device (120), a memory device (130), and additional components (140). The communication device (110) may include a communication circuit (112) and a transceiver (114). For example, the communication circuit (112) may include one or more processors (102, 202) of FIG. 2 and / or one or more memories (104, 204) of FIG. 2. For example, the transceiver (114) may include one or more transceivers (106, 206) of FIG. 2 and / or one or more antennas (108, 208) of FIG. 2. The control unit (120) is electrically connected to the communication device (110), the memory device (130), and the additional component (140) and controls the overall operation of each wireless device (100, 200). For example, the control unit (120) may control the electrical / mechanical operation of each wireless device (100, 200) based on a program / code / command / information stored in the memory device (130). The control device (120) can transmit information stored in the memory device (130) to an external (e.g., other communication device) via the communication device (110) through a wireless / wired interface, or store information received from an external (e.g., other communication device) via the communication device (110) through a wireless / wired interface in the memory device (130).

[0078] The additional component (140) can be configured in various ways depending on the type of wireless device (100, 200). For example, the additional component (140) may include at least one of a power device / battery, an input / output (I / O) device (e.g., audio I / O port, video I / O port), a driving device, and a computing device. The wireless device (100, 200) may be implemented in the form of, but is not limited to, a robot (100a in FIG. 1), a vehicle (100b-1 and 100b-2 in FIG. 1), an XR device (100c in FIG. 1), a portable device (100d in FIG. 1), a home appliance (100e in FIG. 1), an IoT device (100f in FIG. 1), a digital broadcasting terminal, a hologram device, a public safety device, an MTC device, a medical device, a fintech device (or financial device), a security device, a climate / environment device, an AI server / device (400 in FIG. 1), a base station (200 in FIG. 1), or a network node. The wireless device (100, 200) may be used in a mobile or fixed location depending on the use example / service.

[0079] In FIG. 3, the entirety of the various components, devices / parts and / or modules of the wireless device (100, 200) may be connected to each other via a wired interface, or at least some of them may be connected wirelessly via a communication device (110). For example, in each wireless device (100, 200), the control device (120) and the communication device (110) may be connected via a wire, and the control device (120) and the first device (e.g., 130 and 140) may be connected wirelessly via the communication device (110). Each component, device / part and / or module within the wireless device (100, 200) may further include one or more elements. For example, the control device (120) may be composed of one or more sets of processors. As an example, the control device (120) may be composed of a set 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 device (130) may be composed of RAM, DRAM, ROM, flash memory, volatile memory, non-volatile memory and / or a combination thereof.

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

[0081] Referring to FIG. 4, the UE (100) may correspond to the first wireless device (100) of FIG. 2 and / or the wireless device (100 or 200) of FIG. 3.

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

[0083] The processor (102) may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed herein. The processor (102) may be configured to control one or more other components of the UE (100) to implement the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed herein. Layers of a wireless interface protocol may be implemented in the processor (102). The processor (102) may include an ASIC, other chipsets, logic circuits, and / or data processing devices. The processor (102) may be an application processor. The processor (102) may include at least one of a digital signal processor (DSP), a central processing unit (CPU), a graphics processing unit (GPU), and a modem (modulator and demodulator). An example of the processor (102) is the SNAPDRAGON manufactured by Qualcomm®. TM Series processor, EXYNOS made by Samsung® TM Series processors, A Series processors made by Apple®, HELIO made by MediaTek® TM Series processors, ATOM made by Intel® TM It can be found in series processors or corresponding next-generation processors.

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

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

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

[0087] The display (114) outputs the result processed by the processor (102). The keypad (116) receives input to be used by the processor (102). The keypad (116) can be displayed on the display (114).

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

[0089] The speaker (120) outputs sound-related results processed by the processor (102). The microphone (122) receives sound-related input to be used by the processor (102).

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

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

[0092] - AUSF (Authentication Server Function)

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

[0094] - DN (Data Network), for example, operator services, internet access, or third-party services

[0095] - USDF (Unstructured Data Storage Function)

[0096] - NEF (Network Exposure Function)

[0097] - I-NEF (Intermediate NEF)

[0098] - NRF (Network Repository Function)

[0099] - NSSF (Network Slice Selection Function)

[0100] - PCF (Policy Control Function)

[0101] - SMF (Session Management Function)

[0102] - UDM (Unified Data Management)

[0103] - UDR (Unified Data Repository)

[0104] - UPF (User Plane Function)

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

[0106] - AF (Application Function)

[0107] - UE (User Equipment)

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

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

[0110] - NWDAF (Network Data Analytics Function)

[0111] - CHF (CHarging Function)

[0112] 또한, 다음과 같은 네트워크 기능이 고려될 수 있다.

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

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

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

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

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

[0118] For clarity, the connection between UDR and other NFs (e.g., PCF) is not shown in FIG. 5. For clarity, the connection between NWDAF and other NFs (e.g., PCF) is not shown in FIG. 5.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0139] NWDAF is described. You may refer to Sections 4 and 5 of 3GPP TS 23.288 V16.3.0.

[0140] NWDAF is part of the 5G system structure exemplarily described in Fig. 5. NWDAF interacts with different entities for the following various purposes.

[0141] - Data collection based on subscriptions to events provided by AMF, SMF, PCF, UDM, AF, and OAM (Operation Administration Maintenance) (directly or via NEF)

[0142] - Retrieval of information from data repositories (e.g., UDR via UDM for subscriber-related information)

[0143] - Retrieval of information regarding NF (e.g., from NRF in the case of NF-related information)

[0144] - Providing analytics to consumers on demand

[0145] A single or multiple NWDAF instances may be deployed in a public land mobile network (PLMN). When multiple NWDAF instances are deployed, the 5G system architecture may deploy the NWDAF as a central NF, a collection of distributed NFs, or a combination of both.

[0146] If multiple NWDAF instances exist, not all NWDAF instances need to provide the same type of analytical information. That is, some NWDAF instances may be specialized in providing specific types of analytical information. The analytical information ID information element (IE) is used to identify the types of supported analytical information that the NWDAF can generate.

[0147] NWDAF instances can be collocated with 5GS NF.

[0148] The 5G system architecture enables an NWDAF to collect data from any 5GC NF. The NWDAF belongs to the same PLMN as the 5GC NF providing the data.

[0149] The Nnf interface is defined as an interface that allows NWDAF to request a subscription for data delivery for a specific context, cancel a subscription for data delivery, and request specific reporting of data for a specific context.

[0150] Through the 5G system structure, NWDAF can call the OAM service and retrieve management data from OAM.

[0151] In addition, the 5G system architecture allows any 5GC NF to request network analysis information from the NWDAF. The NWDAF belongs to the same PLMN as the 5GC NF using the analysis information.

[0152] The Nnwdaf interface is defined as an interface that allows a 5GC NF to request a subscription for network analysis information delivery for a specific context, cancel a subscription for network analysis information delivery, and request a specific report of network analysis information for a specific context.

[0153] NWDAF provides analysis information as 5GC NF and OAM.

[0154] Analysis information is statistical information about past events or predictive information.

[0155] Various NWDAF instances can exist in 5GC and can be specialized by type of analysis information. The functions of NWDAF instances are described in the NWDAF profiles stored in the NRF.

[0156] To support NFs that are consumers of analytical information by searching for NWDAF instances capable of providing a specific type of analytical information, each NWDAF instance provides a list of analytical information IDs that it supports when registering with the NRF, in addition to other NRF registration elements of the NF profile. Other NFs that need to search for NWDAF instances that provide support for a specific type of analytical information can query the NRF and may include analytical information IDs that identify the desired type of analytical information suitable for that purpose.

[0157] Consumers such as 5GC NF and OAM decide how to use the data analysis information provided by NWDAF.

[0158] The interaction between 5GC NF and NWDAF takes place within PLMN.

[0159] NWDAF does not know about NF application logic. NWDAF can use subscription data only for statistical purposes.

[0160] NWDAF service consumers use NWDAF search principles to select an NWDAF that supports the requested analytics information.

[0161] Enhancements to NWDAF are being discussed to enable 5GS to support network automation.

[0162] One of the major issues in the discussion regarding the improvement of NWDAF is UE data as input for generating analytical information. This issue addresses whether and how NWDAF can be improved to support the collection and utilization of data provided by UEs in order to provide input information for generating analytical information (to be consumed by other NFs).

[0163] In relation to this issue, the following may be discussed.

[0164] - What types of information from the UE can be collected as input for the network (e.g., NWDAF) to generate analysis information?

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

[0166] - How often should this data provided by the UE be shared with NWDAF?

[0167] - What is the trigger for the UE to provide data to NWDAF as input for analysis information?

[0168] - How can the integrity of information provided by the UE and operator-level accessibility be ensured to prevent the use of misleading or untrusted information on the network?

[0169] - Should privacy aspects be considered regarding information provided by the UE? If so, what are the methods to ensure privacy regarding the collection and use of UE data?

[0170] - How does NWDAF collect information from UEs? (i.e., data collection method)

[0171] Information regarding access network discovery and selection policy is described. Refer to Section 6.6.1 of 3GPP TS 23.503 V16.4.1.

[0172] The connection network discovery and selection policy is an optional policy that the network can provide to the UE.

[0173] A wireless local area network (WLAN) access network selected by a UE using access network discovery and selection policies can be used for direct traffic offloading (i.e., sending traffic to a WLAN outside the PDU session) and for registration with 5GC using non-3GPP access network selection information.

[0174] If the UE supports non-3GPP access to 5GC, it must support access network discovery and selection policies.

[0175] The access network discovery and selection policy includes one or more WLAN selection policy (WLANSP) rules. A WLANSP (or WLANSP rule) is a set of rules defined by the operator that determine how a UE (re)selects a WLAN access network. According to the WLANSP rule, the UE selects and connects to the highest priority available WLAN. The priority of each WLAN is determined by several attributes (e.g., MinBackhaulThreshold, BSSLoad).

[0176] The access network discovery and selection policy may include information for the UE to select an ePDG (evolved packet data gateway) or N3IWF.

[0177] A UE may be provided with multiple valid WLANSP rules (by the HPLMN (home PLMN), and by the VPLMN (visited PLMN) in the case of roaming). A WLANSP rule is valid if it satisfies the validity conditions included in the WLANSP rule (if provided).

[0178] When the UE is at home, the UE selects an available WLAN using a valid WLANSP rule from the HPLMN. When the UE is roaming and the UE has a valid WLANSP rule received from the HPLMN and the VPLMN, the UE gives priority to the valid WLANSP rule received from the VPLMN.

[0179] The procedure for a UE to select a WLAN access network based on WLANSP rules is as follows.

[0180] If the UE has valid 3GPP subscription credentials (e.g., a valid USIM) and WLANSP rules, the UE performs WLAN selection based on these rules and applicable User Preferences On Non-3GPP Access Selection. User Preferences On Non-3GPP Access Selection takes precedence over WLANSP rules.

[0181] If the UE cannot select a WLAN access network based on user preference for non-3GPP access selection (e.g., there is no user preference for non-3GPP access selection or there are no available WLAN access networks preferred by the user), it uses WLANSP rules to determine the most preferred WLAN access network.

[0182] The UE searches for available WLANs and constructs a priority list of available WLANs by comparing the attributes / capabilities of the discovered WLANs with a group of selection criteria within valid WLANSP rules. If there are multiple valid WLANSP rules, the UE evaluates the valid WLANSP rules in order of priority. The UE first evaluates whether the available WLAN access network meets the selection criteria of the valid WLANSP rule with the highest priority. Then, the UE evaluates whether the available WLAN access network meets the selection criteria of the valid WLANSP rule with the next highest priority.

[0183] Within a valid WLANSP rule, the WLAN matching the highest priority selection criterion group is considered the most preferred WLAN, and the WLAN matching the second highest priority selection criterion group is considered the second most preferred WLAN.

[0184] When the selection criteria group includes the HomeNetwork attribute and is configured, the UE (a) creates a list of available WLANs that are directly interworked with the home operator, and (b) applies the selection criteria group to all WLANs in that list. Otherwise, if the HomeNetwork attribute is not configured or does not exist, the UE applies the selection criteria group to all available WLANs. To discover the attributes / capabilities of available WLANs, the UE may perform the access network query protocol (ANQP) procedure or other procedures.

[0185] When a UE is roaming, the UE may have valid WLANSP rules from both the VPLMN and the HPLMN. In this case, the UE prioritizes the valid WLANSP rules from the VPLMN. The UE constructs a priority list of available WLANs when available WLAN access meets the selection criteria of the valid rules from the VPLMN and the HPLMN. The WLAN access priority based on the WLANSP rules from the HPLMN has a lower priority than the priority list of WLAN access based on the WLANSP rules from the VPLMN.

[0186] As described above, WLANSP rules contain criteria that a UE can consider when selecting a WLAN access network to connect to. WLANSP rules can be generated by the PCF. However, when the PCF generates WLANSP rules, the UE's actual WLAN usage experience may not be reflected. In other words, during the process of generating WLANSP rules, the PCF may not consider which of the various criteria the WLAN selected by the UE satisfies, and / or what performance the selected WLAN has demonstrated. Consequently, the priority of WLANs determined by the UE based on WLANSP rules does not reflect the UE's actual WLAN usage experience, and thus, the WLAN with the highest priority may not provide the best performance to the UE.

[0187] According to the implementation of the present specification, a method for improving the creation / modification of WLANSP rules by utilizing WLAN usage data provided by the UE may be proposed.

[0188] (1) According to an implementation of the present specification, the PCF may provide data collection configuration information to the UE so that the UE can collect data related to the WLAN usage experience. The data collection configuration information may include information regarding the type of data the UE is to collect, the time interval for collecting data and / or the time of transmitting data (e.g., WLAN disconnection, WLAN / SSID (service set ID) change, etc.).

[0189] In addition, the PCF can provide WLANSP to the UE. That is, the data related to the WLAN usage experience collected by the UE may be data related to WLANSP.

[0190] (2) According to the implementation of the present specification, the UE can collect / generate data related to the WLAN usage experience. The UE can collect / generate data related to the WLAN usage experience based on the received data collection configuration information.

[0191] Table 3 shows an example of data related to WLAN usage experience collected / generated by a UE. A UE may collect / generate all or part of the data related to WLAN usage experience disclosed in Table 3. A UE may generate every data slot for every time interval.

[0192] information explanation UE ID Subscription permanent ID (SUPI) SSID SSID of the WLAN AP connected to the UE List of collected UE data slots (1...max) Each slot contains the accumulated or average value measured over a time interval. BSSID SSID of the WLAN connected to the UE UE location Location information where the UE is connected to the WLAN (e.g., cell ID, TAI (tracking area ID), geographic coordinates) Backhaul bandwidth Backhaul bandwidth of the WLAN connected to the UE BSS load Average BSS (basic service set) load of the WLAN connected to the UE WLAN Protocol WLAN MAC and PHY protocols (e.g., 802.11n, 802.11ac) Start time of data collection Data collection start time End time of data collection end time of data collection Packet loss Number of observed packet losses Packet retransmission Observed number of packet retransmissions Latency Average delay Throughput Average throughput RSSI Average received signal strength indicator (RSSI) SNR Average SNR (signal-to-noise ratio)

[0193] The data related to WLAN usage experience disclosed in Table 3 is merely an example. Additionally, the UE may collect / generate data or other forms of information related to WLAN usage experience that are not disclosed in Table 3. For example, additional data may be collected / generated including which WLANSP was applied, what selection criteria were applied to select available WLANs, by what criteria WLANs were deemed unavailable (e.g., MinBackhaulThreshold, MaxBSSLoad, etc.), information on other WLANs that were included in the priority list of available WLANs but were not selected, and / or supported or specified security protocols (e.g., WPA3, WPA2, etc.).

[0194] The UE may transmit all or part of the collected / generated data to a PCF or another NF. The other NF may be an NF responsible for collecting UE data (e.g., NWDAF). The UE may determine when to transmit the collected / generated data based on data collection configuration information (e.g., whenever a specific event occurs). When transmitting the collected / generated data, the UE may transmit it along with a PLMN ID indicating which PLMN to transmit it to. The PLMN ID may be the PLMN ID that created / provided the WLANSP applied when the UE selected the WLAN.

[0195] (3) According to an implementation of the present specification, NWDAF can collect data related to the WLAN usage experience provided by the UE and generate newly defined WLAN usage experience analysis information. The new analysis information related to the WLAN usage experience may include the correlation between the performance of the WLANSP generated by the PCF and the WLAN connected to the UE based thereon.

[0196] Depending on the target period of the analysis information, the WLAN usage experience analysis information may include statistics and / or predictions.

[0197] Table 4 shows an example of statistical information for WLAN usage experience analysis information generated by NWDAF. NWDAF may generate all or part of the statistical information disclosed in Table 4.

[0198] information explanation Area of ​​Interest TAI or Cell ID List Preferred SSID List List of preferred SSIDs for selection List of Analytics per SSID SSID of WLAN AP deployed in area of ​​interest WLAN Protocol WLAN MAC and PHY protocols (e.g., 802.11n, 802.11ac) Backhaul bandwidth Backhaul bandwidth value BSS load Average BSS load Packet loss Number of lost packets Packet retransmission Number of packet retransmissions Latency Average delay Throughput Average throughput RSSI Average RSSI SNR Average SNR Number of UEs Number of UEs observed for SSID

[0199] Table 5 shows an example of predictive information for WLAN usage experience analysis information generated by NWDAF. NWDAF may generate all or part of the predictive information disclosed in Table 5.

[0200] information explanation Area of ​​Interest TAI or Cell ID List Preferred SSID List List of preferred SSIDs for selection List of Analytics per SSID SSID of WLAN AP deployed in area of ​​interest WLAN Protocol WLAN MAC and PHY protocols (e.g., 802.11n, 802.11ac) Backhaul bandwidth Predicted backhaul bandwidth value BSS load Predicted average BSS load Packet loss Predicted number of packet losses Packet retransmission Predicted number of packet retransmissions Latency Predicted average delay Throughput Predicted average throughput RSSI Predicted Average RSSI SNR Predicted average SNR Number of UEs Predicted number of UEs for SSID Confidence Reliability of prediction

[0201] The statistical information for WLAN usage experience analysis disclosed in Table 4 and / or the predictive information for WLAN usage experience analysis disclosed in Table 5 are merely examples. Additionally, NWDAF may generate statistical information and / or predictive information not disclosed in Table 4 and / or Table 5. For example, the frequency with which each WLANSP and / or selection criterion is applied to a UE, WLANSPs and / or selection criterions requiring updates for performance improvement, and the characteristics and values ​​of selection criterions requiring updates (e.g., MaximumBSSLoad = 60, MinimumBackhaulThreshold = 2Mbps on the downlink, etc.).

[0202] (4) According to an implementation of this specification, NWDAF may provide the generated WLAN usage experience analysis information to a PCF or another NF. NWDAF may provide the generated WLAN usage experience analysis information to a PCF or another NF that requested it.

[0203] For example, the NWDAF provides the generated WLAN usage experience analysis information to the PCF, and the PCF can utilize this to update and / or enhance existing WLANSPs so that the UE can select the optimal WLAN. For instance, configuration values ​​and / or locations, effective time conditions, etc., such as MaximumBSSLoad and MinimumBackhaulThreshold, which may be included in the selection criteria of the WLANSP, can be updated and / or modified.

[0204] A consumer of WLAN usage experience analysis information (e.g., PCF) may instruct NWDAF on the following matters when requesting and / or subscribing to WLAN usage experience analysis information.

[0205] - Analytics information ID set to "WLAN Usage Experience"

[0206] - Subjects of analysis information reporting: UE, UE group, or any UE

[0207] - Filter information for analysis: May include at least one of a region of interest (TA list, cell list, PLMN, etc.), SSID, and BSSID.

[0208] - Target period for analysis information: The time period in the past and / or future for which statistical information and / or forecast information is requested.

[0209] The above information is for illustrative purposes only, and various other parameters may be included in the request and / or subscription.

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

[0211] FIG. 6 illustrates an example of a method performed by a PCF to which the implementation of the present specification applies.

[0212] In step S600, the PCF transmits a policy for WLAN selection (e.g., WLANSP) to the UE.

[0213] In step S610, PCF requests analysis information related to the WLAN from NWDAF.

[0214] In some implementations, the PCF may transmit settings for collecting data related to the WLAN to the UE. The settings may include at least one of the type of data the UE is to collect, information regarding the time interval during which the UE collects data, and information regarding the time when the UE transmits the collected data.

[0215] In step S620, the PCF receives analysis information related to the WLAN from the NWDAF in response to the request.

[0216] In some implementations, the analysis information related to the WLAN may include a correlation between the policy for selecting the WLAN and the performance of the WLAN connected to the UE.

[0217] In some implementations, the analysis information may include at least one of statistical information about the past and / or predictive information about the future.

[0218] In some implementations, requesting analysis information related to the WLAN may be subscribing to analysis information related to the WLAN. A request for analysis information related to the WLAN may include at least one of an analysis information ID set to "WLAN Usage Experience" or "WLAN performance," a target for reporting the analysis information, filter information for the analysis information, and / or a target period for the analysis information.

[0219] In step S630, the PCF updates the policy for selecting the WLAN based on the analysis information related to the WLAN.

[0220] FIG. 7 illustrates an example of a method performed by a UE to which the implementation of the present specification applies.

[0221] In step S700, the UE collects data on the WLAN usage experience.

[0222] In some implementations, the data regarding the WLAN usage experience may include data related to a WLAN located in a specific area of ​​interest and / or data related to a specific SSID.

[0223] In step S710, the UE transmits data regarding the collected WLAN usage experience to the PCF or NF.

[0224] In some implementations, the above NF may be NWDAF.

[0225] In some implementations, the UE can determine when to transmit data regarding the collected WLAN usage experience.

[0226] In some implementations, the ID of the PLMN to which the data regarding the collected WLAN usage experience is to be transmitted may be transmitted along with the data regarding the collected WLAN usage experience. The ID of the PLMN may be the ID of the PLMN that provided the policy for WLAN selection applied when the UE selects a WLAN.

[0227] In some implementations, the UE can communicate with at least one of a mobile device, a network, and / or an autonomous vehicle other than the UE.

[0228] Additionally, the method described in Fig. 7 from the perspective of the UE may be performed by the first wireless device (100) shown in Fig. 2, the wireless device (100) shown in Fig. 3, and / or the UE (100) shown in Fig. 4.

[0229] More specifically, the UE includes one or more transceivers, one or more processors, and one or more memories that can be connected to operate with said one or more processors. said one or more memories store instructions that cause the following operations to be performed by said one or more processors.

[0230] The above operation includes collecting data on WLAN usage experience.

[0231] In some implementations, the data regarding the WLAN usage experience may include data related to a WLAN located in a specific area of ​​interest and / or data related to a specific SSID.

[0232] The above operation includes transmitting data regarding the collected WLAN usage experience to the PCF or NF.

[0233] In some implementations, the above NF may be NWDAF.

[0234] In some implementations, the operation may include determining when to transmit data regarding the collected WLAN usage experience.

[0235] In some implementations, the ID of the PLMN to which the data regarding the collected WLAN usage experience is to be transmitted may be transmitted along with the data regarding the collected WLAN usage experience. The ID of the PLMN may be the ID of the PLMN that provided the policy for WLAN selection applied when the UE selects a WLAN.

[0236] Additionally, the method described in the view of the UE in FIG. 7 may be performed by the control of the processor (102) included in the first wireless device (100) shown in FIG. 2, the control of the communication device (110) and / or control device (120) included in the wireless device (100) shown in FIG. 3, and / or the control of the processor (102) included in the UE (100) shown in FIG. 4.

[0237] More specifically, a device operating in a wireless communication system comprises one or more processors and one or more memories that can be connected to operate with said one or more processors. said one or more processors are configured to perform operations including collecting data on WLAN usage experience and controlling said device to transmit said collected data on WLAN usage experience to a PCF or NF.

[0238] Additionally, the method described in Fig. 7 from the perspective of the UE can be performed by software code (105) stored in the memory (104) included in the first wireless device (100) shown in Fig. 2.

[0239] The technical features of this specification may be implemented directly in hardware, in software executed by a processor, or in a combination of both. For example, a method performed by a wireless device in wireless communication may be implemented in hardware, software, firmware, or a combination thereof. For example, software may be in RAM, flash memory, ROM, EPROM, EEPROM, registers, a hard disk, a removable disk, a CD-ROM, or other storage media.

[0240] Some examples of storage media may be coupled to the processor so that the processor can read information from the storage media. Alternatively, the storage media may be integrated into the processor. The processor and storage media may exist in an ASIC. In other examples, the processor and storage media may exist as separate components.

[0241] Computer-readable media may include non-transitory computer-readable storage media of a type.

[0242] For example, non-transient computer-readable media may include RAM such as SDRAM (synchronous dynamic RAM), ROM, non-volatile NVRAM (non-volatile RAM), EEPROM, flash memory, magnetic or optical data storage media, or other media that can be used to store instructions or data structures. Non-transient computer-readable media may include combinations of the above.

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

[0244] According to some implementations of this specification, a non-transient computer-readable medium (CRM) stores multiple commands.

[0245] More specifically, the CRM stores instructions that cause an operation to be performed by one or more processors. The operation includes collecting data on WLAN usage experience and controlling the device to transmit the collected data on WLAN usage experience to a PCF or NF.

[0246] FIG. 8 illustrates an example of a procedure for collecting data on the WLAN usage experience of a UE to which the implementation of the present specification applies.

[0247] The procedure described in Fig. 8 can be applied to both roaming and non-roaming cases.

[0248] In the case of non-roaming, the V-PCF (VPLMN PCF) shown in Fig. 8 is not involved. In the case of roaming, the AMF interacts with the V-PCF, and the H-PCF (HPLMN PCF) interacts with the V-PCF.

[0249] (1) Step S800: The UE performs the registration procedure in 5GC.

[0250] (2) Step S810: H-PCF may provide policy information regarding UE connection selection through a UE policy container. The policy information regarding UE connection selection may include WLANSP and / or data collection configuration information. The data collection configuration information may include information regarding the data slot creation cycle, the type of data to be collected, and the timing of data reporting (e.g., WLAN disconnection, etc.). The details included in the data collection configuration information may be adjusted according to the current UE's situation (e.g., the current UE's location, etc.). Additionally, the details included in the data collection configuration information may be adjusted according to the information included in the subscription request from NWDAF.

[0251] Alternatively, data collection settings may be pre-configured in the UE. Data collection settings pre-configured in the UE may be pre-configured in various forms, such as settings applicable to all PLMNs, settings applicable to HPLMNs and during roaming, and settings applicable to each PLMN.

[0252] (3) Step S812: The UE policy container containing policy information related to UE connection selection is passed to the AMF via the V-PCF.

[0253] (4) Step S814: AMF delivers the UE policy container created by H-PCF to the UE. Accordingly, policy information from HPLMN can be delivered to the UE.

[0254] (5) Step S820: In the case of roaming, V-PCF may provide policy information regarding UE connection selection through a UE policy container. Policy information regarding UE connection selection may include WLANSP and / or data collection configuration information. Data collection configuration information may include information regarding the data slot creation cycle, the type of data to be collected, and the time of data reporting (e.g., WLAN disconnection, etc.). The details included in the data collection configuration information may be adjusted according to the current UE's situation (e.g., current UE's location, etc.). Additionally, the details included in the data collection configuration information may be adjusted according to the information included in the subscription request from NWDAF.

[0255] (6) Step S822: AMF delivers the UE policy container created by V-PCH to the UE. Accordingly, policy information from VPLMN can be delivered to the UE.

[0256] (7) Step S830: In the case of roaming, the UE may have a valid WLAN SP received from the HPLMN and VPLMN. In this case, the WLAN SP of the VPLMN has priority. Depending on the selected WLAN SP, the UE selects an available WLAN and connects to it.

[0257] Then, it begins collecting data related to the WLAN usage experience based on the data collection configuration information. The UE can collect data related to the WLAN usage experience and generate data slots at time intervals specified in the data collection configuration information.

[0258] (8) Step S840 / S842: If the UE selects a WLAN by applying the VPLMN's WLANSP in Step S830, the UE reports data related to the collected WLAN usage experience along with the VPLMN ID. Accordingly, the data related to the collected WLAN usage experience can be transmitted to the V-PCF.

[0259] (9) Step S850 / S852 / S854: If the UE selects a WLAN by applying the HPLMN's WLANSP in Step S830, the UE reports data related to the collected WLAN usage experience along with the HPLMN ID. Accordingly, the data related to the collected WLAN usage experience can be transmitted to the H-PCF.

[0260] For steps S840 and / or S850, existing NAS messages may be extended and used, or new NAS messages may be defined and used.

[0261] Steps S840 / S842 and / or S850 / S852 / S854 may be transmitted via a 3GPP connection or via a non-3GPP connection.

[0262] Data reporting in steps S840 and / or S850 may be triggered whenever an event indicated in the data collection configuration information occurs. Events may include WLAN disconnection, WLAN / SSID change, etc. If data reporting is triggered by WLAN disconnection, data related to the collected WLAN usage experience may be transmitted via a 3GPP connection. In this case, the UE may transmit data related to the collected WLAN usage experience when it is in the CM_CONNECTED state.

[0263] FIG. 9 illustrates an example of a procedure for requesting / transmitting analysis information based on data regarding the WLAN usage experience of a UE to which the implementation of the present specification applies.

[0264] (1) Step S902: NF requests and / or subscribes to analytics information regarding WLAN usage experience from NWDAF using the Nnwdaf_AnalyticsInfo and / or Nnwdaf_AnalyticsSubscription services. At this time, at least one of the following may be indicated.

[0265] - Analytics information ID set to "WLAN Usage Experience"

[0266] - Subjects of analysis information reporting: UE, UE group, or any UE

[0267] - Filter information for analysis: May include at least one of a region of interest (TA list, cell list, PLMN, etc.), SSID, and BSSID.

[0268] - Target period for analysis information: The time period in the past and / or future for which statistical information and / or forecast information is requested.

[0269] The above information is for illustrative purposes only, and various other parameters may be included in the request and / or subscription.

[0270] For example, if a request for and / or subscription for analytics information includes information about a region of interest as filter information, NWDAF can derive analytics information by utilizing data on WLAN usage experience collected within that region of interest.

[0271] For example, if a request for analytics information and / or a subscription includes an SSID as filter information, NWDAF can derive analytics information by utilizing data on WLAN usage experience collected for that SSID.

[0272] For example, if a request for analytics information and / or a subscription includes a UE or a group of UEs as targets for analytics information reporting, NWDAF can derive analytics information targeting the UE or the group of UEs. If a request for analytics information and / or a subscription includes any UE as targets for analytics information reporting, NWDAF can select data to be used for deriving analytics information based on the information included in the filter information.

[0273] (2) Step S904: When the request and / or subscription is approved, NWDAF sends the request and / or subscription to all PCFs to collect UE data related to WLANSP.

[0274] NWDAF can select a serving PCF by utilizing the target and / or filter information of the analysis information reporting included in the request for analysis information and / or subscription.

[0275] NWDAF may include settings related to UE data collection in requests and / or subscriptions. For example, settings related to UE data collection may include the types of data to be collected and collection methods (e.g., time intervals for creating data slots). PCF can adjust data collection settings based on this.

[0276] (3) Step S906: PCF provides data related to the UE's WLAN usage experience that is collected and stored according to the procedure described in FIG. 8.

[0277] (4) Step S908: NWDAF derives the requested analysis information based on the data related to the acquired UE's WLAN usage experience.

[0278] (5) Step S910: NWDAF provides the analytics information derived in NF using the Nnwdaf_AnalyticsInfo and / or Nnwdaf_AnalyticsSubscription services according to the services used in Step S902.

[0279] (6) Step S912 / S914 / S916: If NF subscribes to analysis information in Step S902, NWDAF provides new analysis information to NF whenever a new output result is generated. That is, if NF requests a continuous subscription to analysis information in Step S902, NWADF continuously provides analysis information. At this time, analysis information may be generated and provided at regular intervals, or it may be provided only when the analysis information is updated by obtaining new data from PCF.

[0280] In FIG. 9, NWDAF derived and provided analysis information based on data related to the UE's WLAN usage experience at the request of an NF. However, the implementation of this specification is not limited thereto, and NWDAF may derive said analysis information and provide it to other NFs without a separate request and / or subscription.

[0281] The service operations illustrated in FIG. 8 and / or FIG. 9 may be extended and used, and other service operations (e.g., conventional service operations and / or new service operations) may also be used.

[0282] The NF that receives data related to WLAN usage experience from the UE may be an NF other than a PCF. For example, the NF that receives data related to WLAN usage experience from the UE may be a UPF and / or a new NF defined to collect data related to WLAN usage experience. In this case, the NWDAF can collect data related to WLAN usage experience by requesting it from the NF that collects data related to WLAN usage experience instead of the PCF.

[0283] This specification may have various effects.

[0284] For example, PCF can update WLANSP to achieve optimal WLAN performance by utilizing new analytics information related to WLAN usage experience.

[0285] For example, PCF can update WLANSP based on data related to the WLAN usage experience provided by the UE so that the actual UE's WLAN usage experience is continuously reflected.

[0286] For example, other NFs besides PCF can also update WLAN-related settings based on data related to WLAN usage experience provided by the UE.

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

Claims

Claim 1 A method performed by a policy and charging function (PCF), comprising: transmitting a wireless local area network (WLAN) selection policy to a user equipment (UE); transmitting subscription information related to WLAN analytics to a network data analytics function (NWDAF); wherein the subscription information related to WLAN analytics includes an analytics reporting target, analytics filter information, and an analytics target period, and wherein the analytics filter information includes an area of ​​interest, a service set ID (SSID), and a basic service set ID (BSSID); wherein, in response to the subscription information, the analysis information related to WLAN is received from the NWDAF, wherein the analysis information related to WLAN includes the area of ​​interest and a list of analysis information by SSID, and wherein the list of analysis information by SSID includes a reference signal strength indicator (RSSI) and the number of UEs observed for the SSID; and wherein the method comprises updating the WLAN selection policy based on the analysis information related to WLAN. Claim 2 A method according to claim 1, further comprising the step of transmitting a setting for collecting data related to the WLAN to the UE. Claim 3 A method according to claim 2, wherein the setting comprises at least one of the type of data that the UE must collect, information on the time interval during which the UE collects data, and information on the time of transmission of the collected data by the UE. Claim 4 A method according to claim 1, characterized in that the analysis information related to the WLAN includes a correlation between the WLAN selection policy and the performance of the WLAN connected to the UE. Claim 5 A method according to claim 1, characterized in that the analysis information related to the WLAN includes at least one of statistical information about the past and / or predictive information about the future. Claim 6 A method according to claim 1, characterized in that transmitting information related to the subscription of analysis information related to the WLAN includes subscribing to the analysis information related to the WLAN. Claim 7 A method according to claim 1, characterized in that the subscription-related information of the analysis information related to the WLAN includes an analysis information ID (identifier) ​​set as "WLAN Usage Experience" or "WLAN performance". Claim 8 A method performed by a UE (user equipment), comprising the step of receiving a WLAN (wireless local area network) selection policy from a PCF (policy and charging function); A method comprising the step of receiving an updated WLAN selection policy from the PCF, wherein the updated WLAN selection policy is based on analytics related to the WLAN, wherein the analytics related to the WLAN is known to the PCF from the NWDAF (network data analytics function) in response to subscription information regarding the analytics related to the WLAN, wherein the subscription information regarding the analytics related to the WLAN includes an analytics reporting target, analytics filter information, and an analytics target period, wherein the analytics filter information includes an area of ​​interest, a service set ID (SSID), and a basic service set ID (BSSID), wherein the analytics related to the WLAN includes the area of ​​interest and a list of analytics information by SSID, and wherein the list of analytics information by SSID includes a reference signal strength indicator (RSSI) and the number of UEs observed for the SSID. Claim 9 In claim 8, the method further comprises: a step of collecting data on WLAN usage experience; and a step of transmitting the collected data on WLAN usage experience to the PCF or NF (network function). Claim 10 A method according to claim 8, characterized in that the data regarding the WLAN usage experience includes data related to a WLAN located in a specific area of ​​interest and / or data related to a specific SSID (service set ID). Claim 11 A method according to claim 9, further comprising the step of determining the timing of transmitting data regarding the collected WLAN usage experience. Claim 12 A method according to claim 9, characterized in that the ID of the PLMN (public land mobile network) to which the collected data on WLAN usage experience is to be transmitted is transmitted together with the collected data on WLAN usage experience. Claim 13 A method according to claim 12, wherein the ID of the PLMN is the ID of the PLMN that provided the WLAN selection policy applied when the UE selects a WLAN. Claim 14 A method according to claim 8, wherein the UE communicates with at least one of a mobile device, a network, and / or an autonomous vehicle other than the UE. Claim 15 In the PCF (policy and charging function), one or more processors; The apparatus includes one or more memories capable of storing instructions and being connected to operate with the one or more processors, and the operation performed based on the execution of the instructions by the one or more processors comprises: transmitting a wireless local area network (WLAN) selection policy to a user equipment (UE); transmitting subscription information related to WLAN analytics to a network data analytics function (NWDAF), wherein the subscription information related to WLAN analytics includes an analytics reporting target, analytics filter information, and an analytics target period, and wherein the analytics filter information includes an area of ​​interest, a service set ID (SSID), and a basic service set ID (BSSID); and wherein, in response to the subscription information, the apparatus receives the WLAN analytics information from the NWDAF, wherein the WLAN analytics information includes the area of ​​interest and a list of analytics information by SSID, and wherein the list of analytics information by SSID includes a reference signal strength indicator (RSSI) and the number of UEs observed for the SSID A PCF including; and a step of updating the WLAN selection policy based on analysis information related to the WLAN. Claim 16 delete Claim 17 delete

Images