WO2022071674A1 - Procédé et appareil permettant de prendre en charge des informations de filtre d'état d'application dans une collecte de données d'ue utilisant une fonction d'application fournie par une porteuse de communication - Google Patents

Procédé et appareil permettant de prendre en charge des informations de filtre d'état d'application dans une collecte de données d'ue utilisant une fonction d'application fournie par une porteuse de communication Download PDF

Info

Publication number
WO2022071674A1
WO2022071674A1 PCT/KR2021/012181 KR2021012181W WO2022071674A1 WO 2022071674 A1 WO2022071674 A1 WO 2022071674A1 KR 2021012181 W KR2021012181 W KR 2021012181W WO 2022071674 A1 WO2022071674 A1 WO 2022071674A1
Authority
WO
WIPO (PCT)
Prior art keywords
application
data
information
data collection
nwdaf
Prior art date
Application number
PCT/KR2021/012181
Other languages
English (en)
Korean (ko)
Inventor
김재휴
김래영
윤명준
Original Assignee
엘지전자 주식회사
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 엘지전자 주식회사 filed Critical 엘지전자 주식회사
Publication of WO2022071674A1 publication Critical patent/WO2022071674A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/18—Service support devices; Network management devices

Definitions

  • the present specification relates to a method and apparatus for supporting application state filter information in UE data collection utilizing an application function provided by a carrier.
  • 3rd Generation Partnership Project (3GPP) Long-Term Evolution (LTE) is a technology for enabling high-speed packet communication. Many methods have been proposed to reduce costs for users and operators, which are LTE goals, to improve service quality, to expand coverage, and to increase system capacity. 3GPP LTE requires lower cost per bit, improved service availability, flexible use of frequency bands, simple structure, open interface, and proper power consumption of terminals as high-level requirements.
  • NR New Radio
  • ITU-R ITU Radio Communication Sector
  • IMT International Mobile Telecommunications
  • NR targets a single technology framework that covers all deployment scenarios, usage scenarios, and requirements, including enhanced Mobile BroadBand (eMBB), massive Machine Type-Communications (mMTC), Ultra-Reliable and Low Latency Communications (URLLC), and more. do. NR must be forward compatible in nature.
  • eMBB enhanced Mobile BroadBand
  • mMTC massive Machine Type-Communications
  • URLLC Ultra-Reliable and Low Latency Communications
  • NWDAF Network Data Analytics Function
  • a consumer NF Network Function
  • ASP Application Service Provider
  • UE User Equipment
  • a method performed by a Network Data Analytics Function (NWDAF) operating in a wireless communication system includes receiving analysis filter information related to user equipment (UE) data collection from a consumer network function (NF).
  • the analysis filter information includes application state information, and the application state information indicates either a foreground or a background.
  • the method includes the steps of determining a data collection AF to use for collecting UE data for the application, determining a list of UEs from which to collect UE data based on state information of the application, and filtering an event with the data collection AF transmitting information.
  • an apparatus implementing the method is provided.
  • the present specification may have various effects.
  • a consumer NF may obtain analysis results based on UE data collected in a specific application state (eg foreground or background).
  • a specific application state eg foreground or background.
  • NWDAF requests UE data collection only for UEs in CM-CONNECTED state when application state information indicates foreground, resource waste due to UE data collection can be reduced.
  • the ASP application client may apply it to UE data collection.
  • FIG. 1 shows an example of a communication system to which an implementation of the present specification is applied.
  • FIG. 2 shows an example of a wireless device to which the implementation of the present specification is applied.
  • FIG 3 shows an example of a wireless device to which the implementation of the present specification is applied.
  • FIG. 4 shows an example of a UE to which the implementation of the present specification is applied.
  • 5 shows an example of a 5G system architecture to which the implementation of the present specification is applied.
  • FIG. 6 shows an example of a setup of a method of collecting UE data based on AF for UE data to which the implementation of the present specification is applied.
  • FIG. 7 shows an example in which the UE ASP application client to which the implementation of the present specification is applied connects to the MNO AF for data collection.
  • Figure 8 schematically shows the exchange from NF to NWDAF, starting with delivering notifications and subscribing to analysis in NWDAF.
  • FIG 10 shows an example of a method performed by the NWDAF to which the implementation of the present specification is applied.
  • CDMA Code Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • TDMA Time Division Multiple Access
  • OFDMA Orthogonal Frequency Division Multiple Access
  • SC-FDMA Single Frequency Division Multiple Access
  • Carrier Frequency Division Multiple Access and MC-FDMA (Multi-Carrier Frequency Division Multiple Access) systems.
  • CDMA may be implemented through a radio technology such as Universal Terrestrial Radio Access (UTRA) or CDMA2000.
  • TDMA may be implemented through a radio technology such as Global System for Mobile communications (GSM), General Packet Radio Service (GPRS), or Enhanced Data rates for GSM Evolution (EDGE).
  • OFDMA may be implemented through a wireless technology such as Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, or Evolved UTRA (E-UTRA).
  • UTRA is part of the Universal Mobile Telecommunications System (UMTS).
  • 3rd Generation Partnership Project (3GPP) Long-Term Evolution (LTE) is a part of Evolved UMTS (E-UMTS) using E-UTRA.
  • 3GPP LTE uses OFDMA in downlink (DL) and SC-FDMA in uplink (UL).
  • Evolution of 3GPP LTE includes LTE-A (Advanced), LTE-A Pro, and/or 5G New Radio (NR).
  • the implementation of the present specification is mainly described in relation to a 3GPP-based wireless communication system.
  • the technical characteristics of the present specification are not limited thereto.
  • the following detailed description is provided based on a mobile communication system corresponding to the 3GPP-based wireless communication system, but aspects of the present specification that are not limited to the 3GPP-based wireless communication system may be applied to other mobile communication systems.
  • a or B (A or B) may mean “only A”, “only B”, or “both A and B”.
  • a or B (A or B) may be interpreted as “A and/or B (A and/or B)”.
  • A, B or C(A, B or C) herein means “only A”, “only B”, “only C”, or “any and any combination of A, B and C ( any combination of A, B and C)”.
  • a slash (/) or a comma (comma) may mean “and/or”.
  • A/B may mean “A and/or B”. Accordingly, “A/B” may mean “only A”, “only B”, or “both A and B”.
  • A, B, C may mean “A, B, or C”.
  • At least one of A and B may mean “only A”, “only B”, or “both A and B”.
  • the expression “at least one of A or B” or “at least one of A and/or B” means “A and It may be construed the same as “at least one of A and B”.
  • At least one of A, B and C means “only A”, “only B”, “only C”, or “A, B and C” any combination of A, B and C”.
  • at least one of A, B or C or “at least one of A, B and/or C” means can mean “at least one of A, B and C”.
  • parentheses used herein may mean “for example”.
  • PDCCH control information
  • PDCCH control information
  • parentheses used herein may mean “for example”.
  • PDCCH control information
  • PDCCH control information
  • FIG. 1 shows an example of a communication system to which an implementation of the present specification is applied.
  • the 5G usage scenario shown in FIG. 1 is only an example, and the technical features of the present specification may be applied to other 5G usage scenarios not shown in FIG. 1 .
  • the three main requirements categories for 5G are (1) enhanced Mobile BroadBand (eMBB) category, (2) massive Machine Type Communication (mMTC) category, and (3) ultra-reliable, low-latency communication. (URLLC; Ultra-Reliable and Low Latency Communications) category.
  • eMBB enhanced Mobile BroadBand
  • mMTC massive Machine Type Communication
  • URLLC Ultra-Reliable and Low Latency Communications
  • a communication system 1 includes wireless devices 100a to 100f , a base station (BS) 200 , and a network 300 .
  • BS base station
  • 1 illustrates a 5G network as an example of a network of the communication system 1, the implementation of the present specification is not limited to the 5G system, and may be applied to future communication systems beyond the 5G system.
  • Base station 200 and network 300 may be implemented as wireless devices, and certain wireless devices may act as base station/network nodes in relation to other wireless devices.
  • the wireless devices 100a to 100f represent devices that perform communication using a radio access technology (RAT) (eg, 5G NR or LTE), and may also be referred to as a communication/wireless/5G device.
  • RAT radio access technology
  • the wireless devices 100a to 100f include, but are not limited to, a robot 100a, a vehicle 100b-1 and 100b-2, an extended reality (XR) device 100c, a portable device 100d, and a home appliance.
  • the product 100e may include an Internet-Of-Things (IoT) device 100f and an Artificial Intelligence (AI) device/server 400 .
  • a vehicle may include a vehicle with a wireless communication function, an autonomous vehicle, and a vehicle capable of performing vehicle-to-vehicle communication.
  • Vehicles may include Unmanned Aerial Vehicles (UAVs) (eg drones).
  • UAVs Unmanned Aerial Vehicles
  • XR devices may include Augmented Reality (AR)/Virtual Reality (VR)/Mixed Reality (MR) devices, and are mounted on vehicles, televisions, smartphones, computers, wearable devices, home appliances, digital signs, vehicles, robots, etc. It may be implemented in the form of a head-mounted device (HMD) or a head-up display (HUD).
  • Portable devices may include smartphones, smart pads, wearable devices (eg, smart watches or smart glasses), and computers (eg, laptops).
  • Home appliances may include TVs, refrigerators, and washing machines.
  • IoT devices may include sensors and smart meters.
  • the wireless devices 100a to 100f may be referred to as user equipment (UE).
  • a UE may be, for example, a mobile phone, a smartphone, a notebook computer, a digital broadcasting terminal, a Personal Digital Assistant (PDA), a Portable Multimedia Player (PMP), a navigation system, a slate PC, a tablet PC, an ultrabook, a vehicle, an autonomous driving function.
  • the UAV may be an aircraft that does not have a person on board and is navigated by a radio control signal.
  • the VR device may include a device for realizing an object or a background of a virtual environment.
  • the AR device may include a device implemented by connecting an object or background in a virtual world to an object or background in the real world.
  • the MR apparatus may include a device implemented by merging the background of an object or virtual world with the background of the object or the real world.
  • the hologram device may include a device for realizing a 360-degree stereoscopic image by recording and reproducing stereoscopic information using an interference phenomenon of light generated when two laser lights called a hologram meet.
  • the public safety device may include an image relay device or an image device that can be worn on a user's body.
  • MTC devices and IoT devices may be devices that do not require direct human intervention or manipulation.
  • MTC devices and IoT devices may include smart meters, vending machines, thermometers, smart light bulbs, door locks, or various sensors.
  • a medical device may be a device used for the purpose of diagnosing, treating, alleviating, treating, or preventing a disease.
  • a medical device may be a device used to diagnose, treat, alleviate, or correct an injury or injury.
  • a medical device may be a device used for the purpose of examining, replacing, or modifying structure or function.
  • the medical device may be a device used for pregnancy control purposes.
  • a medical device may include a device for treatment, a device for driving, an (ex vivo) diagnostic device, a hearing aid, or a device for a procedure.
  • a security device may be a device installed to prevent a risk that may occur and to maintain safety.
  • the security device may be a camera, closed circuit television (CCTV), recorder or black box.
  • the fintech device may be a device capable of providing financial services such as mobile payment.
  • a fintech device may include a payment device or a POS system.
  • the weather/environment device may include a device for monitoring or predicting the weather/environment.
  • the wireless devices 100a to 100f may be connected to the network 300 through the base station 200 .
  • AI technology may be applied to the wireless devices 100a to 100f , and the wireless devices 100a to 100f may be connected to the AI server 400 through the network 300 .
  • the network 300 may be configured using a 3G network, a 4G (eg, LTE) network, a 5G (eg, NR) network, and a 5G or later network.
  • the wireless devices 100a to 100f may communicate with each other through the base station 200/network 300, but communicate directly without going through the base station 200/network 300 (eg, sidelink communication) You may.
  • the vehicles 100b-1 and 100b-2 may perform direct communication (eg, Vehicle-to-Vehicle (V2V)/Vehicle-to-everything (V2X) communication).
  • the IoT device eg, a sensor
  • the IoT device may communicate directly with another IoT device (eg, a sensor) or other wireless devices 100a to 100f.
  • Wireless communications/connections 150a , 150b , 150c may be established between the wireless devices 100a - 100f and/or between the wireless devices 100a - 100f and the base station 200 and/or between the base station 200 .
  • wireless communication/connection includes uplink/downlink communication 150a, sidelink communication 150b (or D2D (Device-To-Device) communication), and inter-base station communication 150c (eg, relay, IAB (Integrated) communication).
  • Access and Backhaul can be established through various RATs (eg, 5G NR).
  • the wireless devices 100a to 100f and the base station 200 may transmit/receive wireless signals to/from each other through the wireless communication/connections 150a, 150b, and 150c.
  • the wireless communication/connection 150a , 150b , 150c may transmit/receive signals through various physical channels.
  • various configuration information setting processes for transmission/reception of radio signals various signal processing processes (eg, channel encoding/decoding, modulation/demodulation, resource mapping/demapping, etc.), and at least a part of a resource allocation process and the like may be performed.
  • AI refers to a field that studies artificial intelligence or a methodology that can create it
  • machine learning refers to a field that defines various problems dealt with in the field of artificial intelligence and studies methodologies to solve them.
  • Machine learning is also defined as an algorithm that improves the performance of a certain task through constant experience.
  • a robot can mean a machine that automatically handles or operates a task given by its own capabilities.
  • a robot having a function of recognizing an environment and performing an operation by self-judgment may be referred to as an intelligent robot.
  • Robots can be classified into industrial, medical, home, military, etc. depending on the purpose or field of use.
  • the robot may be provided with a driving unit including an actuator or a motor to perform various physical operations such as moving the robot joints.
  • the movable robot includes a wheel, a brake, a propeller, and the like in the driving unit, and may travel on the ground or fly in the air through the driving unit.
  • Autonomous driving refers to a technology that drives itself, and an autonomous driving vehicle refers to a vehicle that runs without or with minimal user manipulation.
  • autonomous driving includes technology that maintains a driving lane, technology that automatically adjusts speed such as adaptive cruise control, technology that automatically drives along a set route, and technology that automatically sets a route when a destination is set. Technology, etc. may all be included.
  • the vehicle includes a vehicle having only an internal combustion engine, a hybrid vehicle having both an internal combustion engine and an electric motor, and an electric vehicle having only an electric motor, and may include not only automobiles, but also trains, motorcycles, and the like.
  • Autonomous vehicles can be viewed as robots with autonomous driving capabilities.
  • Augmented reality refers to VR, AR, and MR.
  • VR technology provides only CG images of objects or backgrounds in the real world
  • AR technology provides virtual CG images on top of images of real objects
  • MR technology provides CG by mixing and combining virtual objects with the real world.
  • MR technology is similar to AR technology in that it shows both real and virtual objects.
  • AR technology a virtual object is used in a form that complements a real object
  • MR technology a virtual object and a real object are used with equal characteristics.
  • NR supports multiple numerology or subcarrier spacing (SCS) to support various 5G services. For example, when SCS is 15 kHz, it supports wide area in traditional cellular band, and when SCS is 30 kHz/60 kHz, dense-urban, lower latency and wider area are supported. It supports a wider carrier bandwidth, and when the SCS is 60 kHz or higher, it supports a bandwidth greater than 24.25 GHz to overcome the phase noise.
  • SCS subcarrier spacing
  • the NR frequency band may be defined as two types of frequency ranges (FR1, FR2).
  • the numerical value of the frequency range may change.
  • the frequency ranges of the two types (FR1, FR2) may be as shown in Table 1 below.
  • FR1 may mean "sub 6GHz range”
  • FR2 may mean “above 6GHz range”
  • mmW millimeter wave
  • 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, a frequency band of 6GHz (or 5850, 5900, 5925 MHz, etc.) or higher included in FR1 may include an unlicensed band.
  • the unlicensed band can be used for a variety of purposes, for example, for communication for vehicles (eg, autonomous driving).
  • the wireless communication technology implemented in the wireless device of the present specification may include narrowband IoT (NB-IoT, NarrowBand IoT) for low-power communication as well as LTE, NR, and 6G.
  • NB-IoT technology may be an example of a Low Power Wide Area Network (LPWAN) technology, and may be implemented in standards such as LTE Cat NB1 and/or LTE Cat NB2, and is not limited to the above-mentioned name.
  • LPWAN Low Power Wide Area Network
  • the wireless communication technology implemented in the wireless device of the present specification may perform communication based on LTE-M technology.
  • the LTE-M technology may be an example of an LPWAN technology, and may be called by various names such as enhanced MTC (eMTC).
  • eMTC enhanced MTC
  • LTE-M technology is 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) may be implemented in at least one of various standards such as LTE M, and is not limited to the above-described name.
  • the wireless communication technology implemented in the wireless device of the present specification may include at least one of ZigBee, Bluetooth, and/or LPWAN in consideration of low-power communication, and limited to the above-mentioned names it is not
  • the ZigBee technology may create PANs (Personal Area Networks) related to small/low-power digital communication based on various standards such as IEEE 802.15.4, and may be called by various names.
  • FIG. 2 shows an example of a wireless device to which the implementation of the present specification is applied.
  • the first wireless device 100 and the second wireless device 200 may transmit/receive radio signals to/from an external device through various RATs (eg, LTE and NR).
  • various RATs eg, LTE and NR.
  • ⁇ first wireless device 100 and second wireless device 200 ⁇ are ⁇ radio devices 100a to 100f and base station 200 ⁇ in FIG. 1, ⁇ wireless device 100a to 100f ) and wireless devices 100a to 100f ⁇ and/or ⁇ base station 200 and base station 200 ⁇ .
  • 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 .
  • Processing chip 101 may include at least one processor, such as processor 102 , and at least one memory, such as memory 104 .
  • the memory 104 is exemplarily shown to be included in the processing chip 101 . Additionally and/or alternatively, the memory 104 may be located external to the processing chip 101 .
  • the processor 102 may control the memory 104 and/or the transceiver 106 and may be configured to implement the descriptions, functions, procedures, suggestions, methods, and/or operational flow diagrams disclosed herein. For example, the processor 102 may process information in the memory 104 to generate first information/signal, and transmit a wireless signal including the first information/signal through the transceiver 106 . The processor 102 may receive a radio signal including the second information/signal through the transceiver 106 , and store information obtained by processing the second information/signal in the memory 104 .
  • Memory 104 may be operatively coupled to processor 102 .
  • Memory 104 may store various types of information and/or instructions.
  • the memory 104 may store software code 105 that, when executed by the processor 102 , implements instructions that perform the descriptions, functions, procedures, suggestions, methods, and/or operational flow diagrams disclosed herein.
  • the software code 105 may implement instructions that, when executed by the processor 102 , perform the descriptions, functions, procedures, suggestions, methods, and/or operational flow diagrams disclosed herein.
  • software code 105 may control processor 102 to perform one or more protocols.
  • software code 105 may control processor 102 to perform one or more air interface protocol layers.
  • the processor 102 and memory 104 may be part of a communication modem/circuit/chip designed to implement a RAT (eg, LTE or NR).
  • the transceiver 106 may be coupled to the processor 102 to transmit and/or receive wireless signals via one or more antennas 108 .
  • Each transceiver 106 may include a transmitter and/or a receiver.
  • the transceiver 106 may be used interchangeably with a radio frequency (RF) unit.
  • the first wireless device 100 may represent a communication modem/circuit/chip.
  • 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 .
  • 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 .
  • the memory 204 is exemplarily shown included in the processing chip 201 . Additionally and/or alternatively, the memory 204 may be located external to the processing chip 201 .
  • the processor 202 may control the memory 204 and/or the transceiver 206 and may be configured to implement the descriptions, functions, procedures, suggestions, methods, and/or operational flow diagrams disclosed herein. For example, the processor 202 may process the information in the memory 204 to generate third information/signal, and transmit a wireless signal including the third information/signal through the transceiver 206 . The processor 202 may receive a radio signal including the fourth information/signal through the transceiver 206 , and store information obtained by processing the fourth information/signal in the memory 204 .
  • Memory 204 may be operatively coupled to processor 202 .
  • Memory 204 may store various types of information and/or instructions.
  • the memory 204 may store software code 205 that, when executed by the processor 202 , implements instructions that perform the descriptions, functions, procedures, suggestions, methods, and/or operational flow diagrams disclosed herein.
  • software code 205 may implement instructions that, when executed by processor 202 , perform the descriptions, functions, procedures, suggestions, methods, and/or operational flow diagrams disclosed herein.
  • software code 205 may control processor 202 to perform one or more protocols.
  • software code 205 may control processor 202 to perform one or more air interface protocol layers.
  • the processor 202 and the memory 204 may be part of a communication modem/circuit/chip designed to implement a RAT (eg, LTE or NR).
  • the transceiver 206 may be coupled to the processor 202 to transmit and/or receive wireless signals via one or more antennas 208 .
  • Each transceiver 206 may include a transmitter and/or a receiver.
  • the transceiver 206 may be used interchangeably with the RF unit.
  • the second wireless device 200 may represent a communication modem/circuit/chip.
  • one or more protocol layers may be implemented by one or more processors 102 , 202 .
  • the one or more processors 102, 202 may include one or more layers (eg, a physical (PHY) layer, a Media Access Control (MAC) layer, a Radio Link Control (RLC) layer, a Packet Data Convergence Protocol (PDCP) layer, A functional layer such as a Radio Resource Control (RRC) layer or a Service Data Adaptation Protocol (SDAP) layer) may be implemented.
  • layers eg, a physical (PHY) layer, a Media Access Control (MAC) layer, a Radio Link Control (RLC) layer, a Packet Data Convergence Protocol (PDCP) layer, A functional layer such as a Radio Resource Control (RRC) layer or a Service Data Adaptation Protocol (SDAP) layer
  • the one or more processors 102, 202 generate one or more Protocol Data Units (PDUs) and/or one or more Service Data Units (SDUs) according to the descriptions, functions, procedures, proposals, methods, and/or operational flow diagrams disclosed herein. can do.
  • One or more processors 102 , 202 may generate messages, control information, data, or information in accordance with the descriptions, functions, procedures, proposals, methods, and/or operational flow diagrams disclosed herein.
  • the one or more processors 102, 202 may configure a signal including a PDU, SDU, message, control information, data or information (eg, a baseband signal) and provide it to one or more transceivers 106 , 206 .
  • the one or more processors 102 , 202 may receive signals (eg, baseband signals) from one or more transceivers 106 , 206 , and may be described, functions, procedures, proposals, methods, and/or operational flow diagrams disclosed herein.
  • PDU, SDU, message, control information, data or information may be acquired according to
  • 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.
  • ASICs Application Specific Integrated Circuits
  • DSPs Digital Signal Processors
  • DSPDs Digital Signal Processing Devices
  • PLDs Programmable Logic Devices
  • FPGAs Field Programmable Gates
  • the descriptions, functions, procedures, suggestions, methods, and/or flow diagrams disclosed herein may be implemented using firmware and/or software, and the firmware and/or software may be implemented to include modules, procedures, functions. .
  • Firmware or software configured to perform the descriptions, functions, procedures, proposals, methods, and/or operational flow diagrams disclosed herein may be included in one or more processors 102 , 202 , or stored in one or more memories 104 , 204 . It may be driven by the above processors 102 and 202 .
  • the descriptions, functions, procedures, proposals, methods, and/or flow diagrams disclosed herein may be implemented using firmware or software in the form of code, instructions, and/or sets of instructions.
  • One or more memories 104 , 204 may be coupled with one or more processors 102 , 202 , and may store various forms of data, signals, messages, information, programs, code, instructions, and/or instructions.
  • the one or more memories 104 and 204 may include read-only memory (ROM), random access memory (RAM), erasable programmable ROM (EPROM), flash memory, hard drives, registers, cache memory, computer readable storage media and/or these may be composed of a combination of One or more memories 104 , 204 may be located inside and/or external to one or more processors 102 , 202 . Additionally, one or more memories 104 , 204 may be coupled to one or more processors 102 , 202 through various technologies, such as wired or wireless connections.
  • the one or more transceivers 106, 206 may transmit user data, control information, wireless signals/channels, etc. referred to in the descriptions, functions, procedures, suggestions, methods, and/or flow charts disclosed herein to one or more other devices. .
  • the one or more transceivers 106, 206 may receive user data, control information, radio signals/channels, etc. referred to in the descriptions, functions, procedures, suggestions, methods, and/or flow charts disclosed herein, from one or more other devices. there is.
  • one or more transceivers 106 , 206 may be coupled to one or more processors 102 , 202 and may transmit and receive wireless signals.
  • 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.
  • one or more processors 102 , 202 may control one or more transceivers 106 , 206 to receive user data, control information, wireless signals, etc. from one or more other devices.
  • One or more transceivers 106 , 206 may be coupled to one or more antennas 108 , 208 .
  • One or more transceivers 106, 206 may be connected via one or more antennas 108, 208 to user data, control information, radio signals/channels referred to in the descriptions, functions, procedures, proposals, methods, and/or operational flow diagrams disclosed herein. It may be set to transmit and receive, etc.
  • the one or more antennas 108 and 208 may be a plurality of physical antennas or a plurality of logical antennas (eg, antenna ports).
  • One or more transceivers are configured to process received user data, control information, radio signals/channels, etc., using one or more processors (102, 202), such as received user data, control information, radio signals/channels, and the like. etc. can be converted from an RF band signal to a baseband signal.
  • One or more transceivers 106 , 206 may convert user data, control information, radio signals/channels, etc. processed using one or more processors 102 , 202 from baseband signals to RF band signals.
  • one or more transceivers 106 , 206 may include (analog) oscillators and/or filters.
  • one or more transceivers 106, 206 up-convert OFDM baseband signals to OFDM signals via (analog) oscillators and/or filters under the control of one or more processors 102, 202; , an up-converted OFDM signal may be transmitted at a carrier frequency.
  • One or more transceivers 106, 206 receive the OFDM signal at the carrier frequency and down-convert the OFDM signal to an OFDM baseband signal through an (analog) oscillator and/or filter under the control of one or more processors 102, 202. can be down-converted.
  • the UE may operate as a transmitting device in uplink and as a receiving device in downlink.
  • the base station may operate as a receiving device in the UL and a transmitting device in the DL.
  • a processor 102 coupled to, mounted on, or shipped with the first wireless device 100 may perform UE operations in accordance with implementations of the present disclosure or may configure the transceiver 106 to perform UE operations in accordance with implementations of the present disclosure.
  • a processor 202 coupled to, mounted on, or shipped to the second wireless device 200 is configured to perform a base station operation according to an implementation of the present specification or to control the transceiver 206 to perform a base station operation according to an implementation of the present specification. can be
  • a base station may be referred to as a Node B (Node B), an eNode B (eNB), or a gNB.
  • Node B Node B
  • eNB eNode B
  • gNB gNode B
  • FIG 3 shows an example of a wireless device to which the implementation of the present specification is applied.
  • the wireless device may be implemented in various forms according to usage examples/services (refer to FIG. 1 ).
  • the wireless devices 100 and 200 may correspond to the wireless devices 100 and 200 of FIG. 2 , and may be configured by various components, devices/parts and/or modules.
  • each wireless device 100 , 200 may include a communication device 110 , a control device 120 , a memory device 130 , and an additional component 140 .
  • the communication device 110 may include communication circuitry 112 and a transceiver 114 .
  • communication circuitry 112 may include one or more processors 102 , 202 of FIG. 2 and/or one or more memories 104 , 204 of FIG. 2 .
  • transceiver 114 may include one or more transceivers 106 , 206 of FIG.
  • the control device 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 .
  • the control device 120 may control the electrical/mechanical operation of each of the wireless devices 100 and 200 based on the program/code/command/information stored in the memory device 130 .
  • the control device 120 transmits information stored in the memory device 130 to the outside (eg, other communication devices) via the communication device 110 through a wireless/wired interface, or a communication device ( 110), information received from an external (eg, other communication device) may be stored in the memory device 130 .
  • the additional component 140 may be variously configured according to the type of the wireless device 100 or 200 .
  • the additional components 140 may include at least one of a power unit/battery, input/output (I/O) devices (eg, audio I/O ports, video I/O ports), drive units, and computing devices.
  • I/O input/output
  • Wireless devices 100 and 200 include, but are not limited to, robots (100a in FIG. 1 ), vehicles ( 100b-1 and 100b-2 in FIG. 1 ), XR devices ( 100c in FIG. 1 ), and portable devices ( FIG. 1 ). 100d), home appliances (100e in FIG. 1), IoT devices (100f in FIG.
  • the wireless devices 100 and 200 may be used in a moving or fixed location according to usage examples/services.
  • all of the various components, devices/parts and/or modules of the wireless devices 100 and 200 may be connected to each other via a wired interface, or at least some of them may be wirelessly connected via the communication device 110 .
  • the control device 120 and the communication device 110 are connected by wire, and the control device 120 and the first device (eg, 130 and 140 ) are communication devices. It may be connected wirelessly through 110 .
  • Each component, device/portion, and/or module within the wireless device 100, 200 may further include one or more elements.
  • the control device 120 may be configured by one or more processor sets.
  • control device 120 may be configured by a set of a communication control processor, an application processor (AP), an electronic control unit (ECU), a graphic processing unit, and a memory control processor.
  • AP application processor
  • ECU electronice control unit
  • the memory device 130 may be configured by RAM, dynamic RAM (DRAM), ROM, flash memory, volatile memory, non-volatile memory, and/or a combination thereof.
  • FIG. 4 shows an example of a UE to which the implementation of the present specification is applied.
  • 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 .
  • UE 100 includes processor 102 , memory 104 , transceiver 106 , one or more antennas 108 , power management module 141 , battery 142 , display 143 , keypad 144 , SIM (Subscriber Identification Module) includes a card 145 , a speaker 146 , and a microphone 147 .
  • SIM Subscriber Identification Module
  • the processor 102 may be configured to implement the descriptions, functions, procedures, suggestions, methods, and/or operational flow diagrams 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, suggestions, methods, and/or operational flow diagrams disclosed herein.
  • a layer of air interface protocol may be implemented in the processor 102 .
  • Processor 102 may include an ASIC, other chipset, logic circuitry, and/or data processing device.
  • the processor 102 may be an application processor.
  • the processor 102 may include at least one of a DSP, a central processing unit (CPU), a graphics processing unit (GPU), and a modem (modulator and demodulator).
  • Examples of the processor 102 include SNAPDRAGON TM series processors made by Qualcomm®, EXYNOS TM series processors made by Samsung®, A series processors made by Apple®, HELIO TM series processors made by MediaTek®, ATOM TM series processors made by Intel®. or in the corresponding next-generation processor.
  • the memory 104 is operatively coupled to the processor 102 , and stores various information for operating the processor 102 .
  • Memory 104 may include ROM, RAM, flash memory, memory cards, storage media, and/or other storage devices.
  • modules eg, procedures, functions, etc.
  • Modules may be stored in memory 104 and executed by processor 102 .
  • the memory 104 may be implemented within the processor 102 or external to the processor 102 , in which case it may be communicatively coupled with the processor 102 through various methods known in the art.
  • the transceiver 106 is operatively coupled with the processor 102 and transmits and/or receives wireless signals.
  • the transceiver 106 includes a transmitter and a receiver.
  • the transceiver 106 may include baseband circuitry for processing radio frequency signals.
  • the transceiver 106 controls one or more antennas 108 to transmit and/or receive wireless signals.
  • the power management module 141 manages power of the processor 102 and/or the transceiver 106 .
  • the battery 142 supplies power to the power management module 141 .
  • the display 143 outputs the result processed by the processor 102 .
  • Keypad 144 receives input for use by processor 102 .
  • the keypad 144 may be displayed on the display 143 .
  • the SIM card 145 is an integrated circuit for securely storing an International Mobile Subscriber Identity (IMSI) and related keys, and is used to identify and authenticate a subscriber in a mobile phone device such as a mobile phone or computer. You can also store contact information on many SIM cards.
  • IMSI International Mobile Subscriber Identity
  • the speaker 146 outputs sound related results processed by the processor 102 .
  • Microphone 147 receives sound related input for use by processor 102 .
  • 5 shows an example of a 5G system architecture to which the implementation of the present specification is applied.
  • the 5G system (5GS; 5G System) structure consists of the following network functions (NF; Network Functions).
  • Data Network e.g. operator services, Internet access or third-party services
  • 5 shows the 5G system structure of a non-roaming case using a reference point representation that shows how various network functions interact with each other.
  • UDSF, NEF and NRF are not described for clarity of the point-to-point diagram. However, all network functions shown can interact with UDSF, UDR, NEF and NRF as needed.
  • connection between UDRs and other NFs is not shown in FIG. 5 .
  • connection between NWDAF and other NFs is not shown in FIG. 5 .
  • the 5G system architecture includes the following reference points.
  • - N1 the reference point between the UE and the AMF.
  • NWDAF is a part of the 5G system architecture exemplarily described in FIG. 5 .
  • NWDAF interacts with different entities for a variety of purposes:
  • a single or multiple NWDAF instances may be deployed in a Public Land Mobile Network (PLMN).
  • PLMN Public Land Mobile Network
  • the 5G system structure may be deployed as a collection of NWDAF central NF, distributed NF, or a combination of both.
  • NWDAF instances When multiple NWDAF instances exist, not all NWDAF instances need to provide the same type of analysis information. That is, some instances of NWDAF may specialize in providing certain types of analytics information.
  • An Analytics ID Information Element IE is used to identify the types of supported analytics information that NWDAF can generate.
  • NWDAF instance may be collocated with 5GS NF.
  • the 5G system architecture allows NWDAF to collect data from any 5GC NF.
  • NWDAF belongs to the same PLMN as 5GC NF that provides data.
  • the Nnf interface is defined as an interface through which NWDAF can request a subscription for data delivery for a specific context, cancel a subscription for data delivery, and request a specific report of data for a specific context.
  • 5G system architecture allows NWDAF to call OAM service to retrieve management data from OAM.
  • the 5G system structure allows any 5GC NF to request network analysis information from NWDAF.
  • NWDAF belongs to the same PLMN as 5GC NF using analysis information.
  • the Nnwdaf interface is defined as an interface through which 5GC NF can 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. .
  • NWDAF provides analysis information with 5GC NF and OAM.
  • the analysis information is statistical information or predictive information about past events.
  • NWDAF instances can exist in 5GC, and specialization is possible for each type of analysis information.
  • the functionality of the NWDAF instance is described in the NWDAF profile stored in the NRF.
  • each NWDAF instance provides a list of supported analytics IDs when registering with the NRF, in addition to other NRF registration elements in the NF profile. to provide.
  • Other NFs that need to retrieve an NWDAF instance that provide support for a particular type of analytics may query the NRF and include an analytics ID that identifies the desired type of analytics for that purpose. .
  • 5GC NF The interaction between 5GC NF and NWDAF takes place within the PLMN.
  • NWDAF does not know about NF application logic. NWDAF may use subscription data for statistical purposes only.
  • NWDAF enhancements are under discussion to enable 5GS to support network automation.
  • NWDAF One of the main issues in the discussion on the improvement of NWDAF is UE data as input for generating analysis information. This issue addresses whether and how NWDAF can be improved to support the collection and utilization of data provided by UEs to provide input information for generating analysis information (which other NFs will consume).
  • NWDAF What types of analysis information can NWDAF provide to other NFs to utilize the data provided by the UE?
  • NWDAF collect information from UE? i.e. data collection method
  • a method of collecting UE data based on AF for UE data provided by a Mobile Network Operator may be proposed as follows. there is.
  • AF for UE application layer data collection is introduced.
  • This AF is provided and controlled by the MNO and communicates with the UE's Application Service Provider (ASP) application client via the HyperText Transfer Protocol Secure (HTTPS) protocol in the user plane.
  • HTTPS HyperText Transfer Protocol Secure
  • AF for UE data collection in turn refines and enriches the input data provided by the UE's application client and exposes the resulting analysis information to NWDAF through the generic Naf_EventExposure mechanism.
  • NWDAF generic Naf_EventExposure mechanism.
  • SLA Service Level Agreement
  • MNO AF to which the UE application client of the ASP will connect (eg via Fully Qualified Domain Name (FQDN))
  • the information shared by the UE application clients of the ASP with the MNO AF i.e. service experience data, UE communication data and exception information / These information may be extended to other data that the UE may provide within the scope of Rel-17) has exist
  • Authentication information for MNO AF the method and data used by the UE application client of the ASP to verify that the object to send data to is actually the MNO AF
  • Authentication information for the ASP's UE application client the method and data used by the MNO AF to verify that the entity from which the data is being received is actually the ASP's UE application client.
  • the MNO AF connected by the ASP also registers with the NRF by providing the internal application ID (register the internal application ID used for event exposure). MNO AF also maps the external application ID (provided by the UE application client) to the internal application ID used for event exposure.
  • FIG. 6 shows an example of a setup of a method of collecting UE data based on AF for UE data to which the implementation of the present specification is applied.
  • a typical ASP application server provides services such as content to the ASP application client, but also provides the FQDN and authorization and authentication details (this information may be provided in advance to the application client) to communicate with the AF for UE data collection.
  • Authorization and authentication details may include:
  • the ASP application client is designed to establish user plane communication with the AF for UE data collection, using the FQDN and the authorization and authentication details provided by the ASP to the application client, only if the privacy settings allow sharing application data with the MNO. .
  • This communication channel is established through the user plane using the existing PDU session.
  • FIG. 7 shows an example in which the UE ASP application client to which the implementation of the present specification is applied connects to the MNO AF for data collection.
  • each ASP application client is set up to establish a connection with the MNO AF for UE data collection through the user plane when running.
  • a connection is established through an existing PDU session used by the ASP application client.
  • the user starts or interacts with the application client on the UE.
  • the application client contacts the application server.
  • the application client may receive the data (FQDN) required for the user plane connection to the MNO AF for UE data collection. This data may be provided in advance to the application client.
  • the application client initiates the user plane connection setup to the MNO AF for data collection through the existing PDU session.
  • the application client provides the application ID and UE IP address to be stored in the MNO AF to request input data from the UE application client.
  • FIG. 8 shows an example of providing UE ASP application client data to NWDAF to which the implementation of the present specification is applied.
  • MNO AF for UE data collection When the MNO AF for UE data collection receives the data subscription from the NWDAF, it instructs it to communicate with the ASP application client through the user plane connection described in FIG. 7 and deliver the data. MNO AF for UE data collection processes the data (eg enrichment, aggregation or normalization) in the UE application client of the ASP and provides the results to the NWDAF using Naf_EventExpoure_Notify.
  • Figure 8 schematically shows the exchange from NF to NWDAF, starting with delivering notifications and subscribing to analysis in NWDAF.
  • NWDAF may begin collecting data prior to this subscription.
  • the NWDAF uses the Nnrf_NFDiscovery request containing the application ID provided by the NWDAF to determine which AF to use for UE data collection provided by the MNO.
  • NWDAF uses a Naf_EventExposure subscription that includes the event reporting target (i.e. Subscription Permanent Identifier (SUPI) or any UE), event ID, event filter, and application ID for which input data is requested, to AF for UE data collection. Subscribe to input data for analysis.
  • event reporting target i.e. Subscription Permanent Identifier (SUPI) or any UE
  • event ID i.e. Event ID
  • event filter i.e. Subscription Permanent Identifier (SUPI) or any UE
  • application ID for which input data is requested
  • AF for UE data collection determines which ASP application clients are in data collection scope. If the NWDAF has provided an internal group ID as the target for event reporting, the AF for UE data collection must find the SUPI list within that internal group ID. If the NWDAF has provided all UEs, the NWDAF will check the Analytics Filter and contact the AMF to find a list of SUPIs in the Area of Interest (AoI). NWDAF contacts all ASP application clients that support that application ID. If the NWDAF provides a region of interest or network slice as an event reporting target, the AF for UE data collection must find a list of SUPIs within range. AF for UE data collection requests the ASP's UE application client to start reporting input data as requested by the SLA.
  • AoI Area of Interest
  • the AF for UE data collection communicates with the ASP application client within range via the connection setup described in FIG. 7 and requests and receives data. This procedure can be used to collect data for both 3GPP defined services and non-3GPP defined services.
  • AF for UE data collection receives input data from the UE, processes it (e.g., enriches, aggregates and normalizes), applies event IDs and event filters, and then sends it to NWDAF for data collected according to the NWDAF subscription. inform
  • NWDAF provides analysis to consumer NFs.
  • ASPs are responsible for ensuring that user privacy is not compromised as ASPs ultimately decide what data is shared with MNOs through AF for UE data collection to NWDAF. That is, the user agrees with the ASP to allow or deny the possibility of sharing the ASP's UE application client data with the MNO.
  • the ASP's UE application client is instructed by the ASP to establish a connection with the MNO AF only if its agreement allows it to share data with the MNO.
  • the method and data the MNO AF will use to authenticate are all negotiated as part of the SLA between the MNO and the ASP.
  • the method and data that the ASP application client of the UE will use to authenticate is both negotiated as part of the SLA between the MNO and the ASP.
  • the ASP sends the method and data used to authenticate the MNO AF to the UE application client as described in FIG. 6 .
  • the UE application client In order to associate the UE application client data with the input data requested by the NWDAF, the UE application client provides the UE IP address/prefix and an external application ID, and the NWDAF request includes the SUPI and the internal application ID. MNO AF must relate both.
  • the MNO AF registers with the NRF as supporting both applications that are part of the NF profile.
  • the MNO AF obtains an active PDU session for SUPI, Data Network Name (DNN) and Single Network Slice Selection Assistance Information (S-NSSAI) if provided by NWDAF, followed by an event Subscribe to IP address assignment and release to SMF.
  • DNN Data Network Name
  • S-NSSAI Single Network Slice Selection Assistance Information
  • the MNO AF will submit a Nudm_SDM_Subscribe with the datatype set to the UE context in the target SUPI, S-NSSASI if available, and SMF data. to connect to UDM.
  • the MNO AF requests the UDM to provide a list of SUPIs using the Nudm_SMF_Get service containing the internal group ID and datatype set to group data.
  • UDM provides UE context data including SMF serving SUPI. This step may be required multiple times, one per SUPI.
  • MNO AF uses Nsmf_EventExposure, event ID for UE IP address/prefix assignment change to contact each SMF in the list of SMFs serving SUPI.
  • the SMF provides the UE IP address/prefix assigned to the SUPI.
  • MNO AF saves it for later use and updates it according to SMF's notification.
  • One of the event filters is a region of interest.
  • the UE application ID reports the event with the associated timestamp and at the same time the MNO AF makes a request to the AMF with which the SUPI is registered to provide the UE location.
  • AF for UE data collection In order to utilize the AF for UE data collection provided by the MNO as described above, first establish a connection between the ASP application client and the AF for UE data collection through communication between the ASP application server and the ASP application client installed in the UE. can be Afterwards, when UE data collection is required, AF for UE data collection may be received by requesting UE data collection from an ASP application client of the UE.
  • an application status may be an important element of UE data collection.
  • the application state may indicate whether the current application is operating in the foreground/foreground or in the background/background. For example, a consumer NF requesting/subscribing analysis from NWDAF may only request/subscribe UE data for applications in foreground state. However, UE data collection considering the application state is not currently supported.
  • the present specification describes a method of supporting the application state as filter information in UE data collection.
  • the methods described herein may consist of a combination of one or more operations/configurations/steps described below.
  • the NWDAF may include the application state as an event filter.
  • the application state may be provided by the consumer NF of the NWDAF through an analysis filter.
  • the application state may be generated by the NWDAF itself based on a local configuration.
  • the NWDAF may include the UE list including the UE in the CM-CONNECTED state in Naf_EventExposure and transmit it to the AF.
  • the NWDAF may include information related to the UE's connection type (eg, 3GPP connection, non-3GPP connection (eg, WLAN)) as an event filter.
  • Information related to the connection type of the UE may be provided by the consumer NF of the NWDAF through an analysis filter.
  • the information related to the connection type of the UE may be generated by the NWDAF itself based on local settings.
  • the AF for UE data collection provided by the MNO may transmit filter information to the ASP application client.
  • the filter information may include information related to AoI.
  • the filter information may include information related to an application state.
  • the filter information may include information related to the connection type of the UE.
  • information related to the connection type of the UE may include a service set ID (SSID) and/or a basic service set ID (BSSID).
  • SSID service set ID
  • BSSID basic service set ID
  • the filter information may be obtained from NWDAF.
  • the filter information may be generated by the NWDAF itself based on information obtained by the NWDAF from the consumer NF.
  • the filter information may be generated by NWDAF itself based on local settings.
  • the ASP application client may collect UE data by applying filter information.
  • FIG 10 shows an example of a method performed by the NWDAF to which the implementation of the present specification is applied.
  • the method includes receiving analysis filter information related to UE data collection from the consumer NF.
  • the analysis filter information includes application status information.
  • the status information of the application indicates either the foreground or the background.
  • the status information of the application may be set for each application and/or set identically for all applications.
  • step S1010 the method includes determining a data collection AF to use for UE data collection for the application.
  • step S1020 the method includes determining a UE list for collecting UE data based on the state information of the application.
  • the UE list may include only UEs in a CM_CONNECTED state.
  • the method may further include the step of notifying whether a function of displaying the UE list including only the UEs in the CM_CONNECTED state is supported based on the status information of the application indicating the foreground.
  • step S1030 the method includes transmitting event filter information to the data collection AF.
  • the event filter information may include state information of the application.
  • the event filter information may include information related to a connection type of the UE. Based on that the connection type of the UE is a non-3GPP connection, the information related to the connection type of the UE may include an SSID and/or a BSSID.
  • step S1040 the method includes receiving, from the data collection AF, UE data collected from one or more UEs included in the UE list.
  • step S1050 the method includes generating analysis data based on the collected UE data.
  • step S1060 the method includes transmitting the generated analysis data to the consumer NF.
  • the method may include obtaining information of the UE in the CM_CONNECTED state from the AMF.
  • the one or more UEs may communicate with at least one of a mobile device, a network, and/or an autonomous vehicle other than the one or more UEs.
  • the method described in terms of NWDAF in FIG. 10 may be performed by an apparatus implementing NWDAF.
  • a device implementing NWDAF receives analysis filter information related to UE data collection from a consumer NF.
  • the analysis filter information includes application status information.
  • the status information of the application indicates either the foreground or the background.
  • the status information of the application may be set for each application and/or set identically for all applications.
  • a device implementing NWDAF determines the data collection AF to use for UE data collection for the application.
  • a device implementing NWDAF determines a list of UEs from which to collect UE data based on the state information of the application.
  • the UE list may include only UEs in a CM_CONNECTED state.
  • the device implementing NWDAF may indicate whether or not the function of displaying the UE list including only the UEs in the CM_CONNECTED state is supported based on the status information of the application indicating the foreground.
  • a device implementing NWDAF sends event filter information to the data collection AF.
  • the event filter information may include state information of the application.
  • the event filter information may include information related to a connection type of the UE. Based on that the connection type of the UE is a non-3GPP connection, the information related to the connection type of the UE may include an SSID and/or a BSSID.
  • An apparatus implementing NWDAF receives, from the data collection AF, UE data collected from one or more UEs included in the UE list.
  • a device implementing NWDAF generates analysis data based on the collected UE data.
  • a device implementing NWDAF transmits the generated analysis data to the consumer NF.
  • the device implementing NWDAF may obtain the information of the UE in the CM_CONNECTED state from the AMF.
  • NWDAF may begin collecting data prior to this subscription.
  • analysis filter information related to UE data collection may be included.
  • the analysis filter information may include AoI, application ID, as well as application state information.
  • the application state information may indicate a foreground and/or a background.
  • the foreground is merely a name and/or an example, and may be replaced with another term having a similar meaning to the foreground.
  • the foreground may be interpreted as that the corresponding application is running, being executed, is in operation, and/or that the corresponding application is in a running, on-going, or active state.
  • the background is merely a name and/or an example, and may be replaced with other terms having a meaning similar to the background.
  • the background may be interpreted that the corresponding application is not running, not running, not running, and/or that the corresponding application is in a not running, not on-going, inactive state.
  • the application state information may be provided/set for each application ID.
  • the application state information may indicate a foreground for a specific application ID and a background for another specific application ID.
  • the application state information may be provided/set equally for all application IDs.
  • the application state information may indicate foreground and/or background for all application IDs.
  • the NWDAF uses the Nnrf_NFDiscovery request containing the application ID provided by the NWDAF to determine which AF to use for UE data collection provided by the MNO.
  • NWDAF uses a Naf_EventExposure subscription that includes the event report target (i.e. SUPI or all UEs), event ID, event filter, and application ID for which input data is requested, to AF for UE data collection input data for analysis. subscribe to the event report target (i.e. SUPI or all UEs), event ID, event filter, and application ID for which input data is requested, to AF for UE data collection input data for analysis. subscribe to
  • the analysis filter information obtained in step 1 may be applied to the event filter. Accordingly, the analysis filter information transmitted by the consumer NF in step 1 may be included in the event filter of Naf_EventExposure transmitted by the NWDAF to the AF for data collection. Based on the analysis filter information including the application state information, the NWDAF may provide the application state to the AF for data collection as an event filter.
  • the NWDAF determines the application state Event filters can be provided to AF for data collection.
  • the NWDAF may include in Naf_EventExposure a UE list including only UEs in CM-CONNECTED state among target UEs as an event filter.
  • the NWDAF may obtain information about the UE in the CM-CONNECTED state from the AMF.
  • NWDAF uses a UE list including only UEs in CM-CONNECTED state as an event filter. to include it in Naf_EventExposure.
  • the NWDAF may inform other NFs of whether or not it supports the function of displaying a UE list including only UEs in CM-CONNECTED state when application state information is in the foreground. If the NWDAF does not support the corresponding function, the AF for data collection may directly acquire the UE's status information through the AMF.
  • the NWDAF receives the requested information.
  • application state information required for the corresponding application can be known. For example, if the consumer NF requests UE data related to service experience, if separate application state information is not provided/set/indicated, it is implicitly that the application in the foreground state is the target of UE data collection. may be indicated/assumed. As another example, when the consumer NF requests location information, if separate application state information is not provided/set/indicated, it may be implicitly indicated/assumed that both the foreground and background applications are the target of UE data collection. .
  • the event filter may include various parameters in addition to the parameters included in the analysis filter information obtained in step 1 above.
  • the connection type of the UE may be applied as an event filter. That is, when the UE accesses through either a 3GPP connection or a non-3GPP connection (eg, WLAN), collection of UE data may be requested only for the corresponding UE.
  • a 3GPP connection or a non-3GPP connection (eg, WLAN)
  • collection of UE data may be requested only for the corresponding UE.
  • the collection of UE data may be requested for the UE connected through a specific SSID/BSSID.
  • AF for UE data collection determines which ASP application clients are in data collection scope. If the NWDAF has provided an internal group ID as the target for event reporting, the AF for UE data collection must find the SUPI list within that internal group ID. If the NWDAF has covered all UEs, the NWDAF will check the analysis filter and contact the AMF to find a list of SUPIs for that area of interest. NWDAF contacts all ASP application clients that support that application ID. If the NWDAF provides a region of interest or network slice as an event reporting target, the AF for UE data collection must find a list of SUPIs within range. AF for UE data collection requests the ASP's UE application client to start reporting input data as requested by the SLA.
  • the AF for UE data collection communicates with the ASP application client within range via the connection setup described in FIG. 7 and requests and receives data. This procedure can be used to collect data for both 3GPP defined services and non-3GPP defined services.
  • AF for UE data collection receives a Naf_EventExposure containing event filters related to UE data collection described in step 3 (eg AoI, application ID, application state), AF for UE data collection returns the filter information to ASP application can be sent to the client.
  • the filter information may be to deliver the event filter as it is.
  • the filter information may be generated by the AF for collecting UE data based on the event filter.
  • ASP application clients can apply filter information to collect UE data.
  • the ASP application client can only collect UE data within the AoI.
  • the ASP application client can collect UE data only when the application is in the specified application state. For example, if the application state is set to foreground, the ASP application client can collect UE data only when that application is in the foreground state.
  • UE data collection may be determined according to the UE's connection type (eg, 3GPP connection or non-3GPP connection). That is, the ASP application client can collect UE data only for the UE connected through a specific connection. In addition, when the ASP application client collects UE data only for a UE accessed through a non-3GPP connection, if a specific SSID/BSSID is specified, UE data may be collected only from the corresponding SSID/BSSID.
  • the connection type eg, 3GPP connection or non-3GPP connection. That is, the ASP application client can collect UE data only for the UE connected through a specific connection.
  • a specific SSID/BSSID if a specific SSID/BSSID is specified, UE data may be collected only from the corresponding SSID/BSSID.
  • AF for UE data collection receives input data from the UE, processes it (e.g., enriches, aggregates and normalizes), applies event IDs and event filters, and then sends it to NWDAF for data collected according to the NWDAF subscription. inform
  • NWDAF provides analysis to consumer NFs.
  • the present specification may have various effects.
  • a consumer NF may obtain analysis results based on UE data collected in a specific application state (eg foreground or background).
  • a specific application state eg foreground or background.
  • NWDAF requests UE data collection only for UEs in CM-CONNECTED state when application state information indicates foreground, resource waste due to UE data collection can be reduced.
  • the ASP application client may apply it to UE data collection.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un procédé et un appareil permettant de prendre en charge des informations de filtre d'état d'application dans une collecte de données d'UE à l'aide d'une fonction d'application fournie par une porteuse de communication. Une fonction d'analyse de données de réseau (NWDAF) reçoit, d'une fonction de réseau (NF) de consommateur, des informations de filtre d'analyse relatives à la collecte de données d'équipement utilisateur (UE). Les informations de filtre d'analyse comprennent les informations d'état d'une application, les informations d'état de l'application indiquant soit un premier plan soit un arrière-plan. La NWDAF : détermine une AF de collecte de données destinée à être utilisée pour la collecte de données d'UE pour l'application ; détermine, d'après les informations d'état de l'application, une liste d'UE pour collecter des données d'UE ; et transmet les informations de filtre d'événement à l'AF de collecte de données.
PCT/KR2021/012181 2020-09-29 2021-09-08 Procédé et appareil permettant de prendre en charge des informations de filtre d'état d'application dans une collecte de données d'ue utilisant une fonction d'application fournie par une porteuse de communication WO2022071674A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR10-2020-0126867 2020-09-29
KR20200126867 2020-09-29

Publications (1)

Publication Number Publication Date
WO2022071674A1 true WO2022071674A1 (fr) 2022-04-07

Family

ID=80950723

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2021/012181 WO2022071674A1 (fr) 2020-09-29 2021-09-08 Procédé et appareil permettant de prendre en charge des informations de filtre d'état d'application dans une collecte de données d'ue utilisant une fonction d'application fournie par une porteuse de communication

Country Status (1)

Country Link
WO (1) WO2022071674A1 (fr)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020070118A1 (fr) * 2018-10-05 2020-04-09 Telefonaktiebolaget Lm Ericsson (Publ) Procédés et appareil de découverte de fonctions analytiques

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020070118A1 (fr) * 2018-10-05 2020-04-09 Telefonaktiebolaget Lm Ericsson (Publ) Procédés et appareil de découverte de fonctions analytiques

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Architecture enhancements for 5G System (5GS) to support network data analytics services (Release 16)", 3GPP STANDARD; 3GPP TS 23.288, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, no. V16.5.0, 24 September 2020 (2020-09-24), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , pages 1 - 66, XP051960887 *
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on enablers for network automation for the 5G System (5GS); Phase 2 (Release 17)", 3GPP STANDARD; TECHNICAL REPORT; 3GPP TR 23.700-91, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, no. V1.0.0, 11 September 2020 (2020-09-11), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , pages 1 - 304, XP051926020 *
CATT: "KI #13, New Sol: Trigger configuration for data collection and analytics", 3GPP DRAFT; S2-2005438, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Elbonia ;20200819 - 20200901, 13 August 2020 (2020-08-13), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051920265 *
HUAWEI, HISILICON: "KI#8, Sol#29: Update to add an Application Status for the application data from UE", 3GPP DRAFT; S2-2006255, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. e-meeting; 20200819 - 20200901, 2 September 2020 (2020-09-02), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051928789 *

Similar Documents

Publication Publication Date Title
WO2022059987A1 (fr) Procédé et dispositif pour obtenir, gérer, et vérifier un consentement d'utilisateur pour la fourniture externe d'informations d'analyse de données d'utilisateur
WO2021241905A1 (fr) Sélection efficace de plmn lors d'une défaillance d'authentification pour chaque tranche de réseau dans un réseau d'itinérance
WO2021187913A1 (fr) Communication associée à un calcul de bordure
WO2021242060A1 (fr) Procédé et dispositif de prise en charge d'une génération d'une session de pdu dédiée pour un trafic d'utilisateur particulier
WO2021187829A1 (fr) Communication relative à une tranche de réseau
WO2021225317A1 (fr) Communication associée à une commande d'encombrement
WO2021187936A1 (fr) Procédé de communication utilisant une tranche de réseau
WO2022019537A1 (fr) Accès à un snpn en utilisant un justificatif d'identité appartenant à une entité séparée du snpn, et prise en charge d'interface f1 pour cela
WO2022014960A1 (fr) Procédé de commande de congestion provoquée par un utilisateur itinérant en cas de catastrophe, et dispositif prenant en charge ledit procédé
WO2021187881A1 (fr) Indication de prise en charge de réseau pour des informations d'appariement de session de pdu fournies par un ue
WO2022055078A1 (fr) Procédé d'acceptation d'une politique d'application de sécurité entre une liaison pc5 et une liaison uu dans une communication de relais prose, et dispositif prenant en charge ledit procédé
WO2022014973A1 (fr) Procédé permettant de gérer une liste de réseaux plmn interdits pendant une itinérance en cas de catastrophe, et appareil le prenant en charge
WO2022035204A1 (fr) Communication associée à une tranche de réseau
WO2021235779A1 (fr) Communication liée à une multidiffusion
WO2022035259A1 (fr) Procédé de gestion de session
WO2021194214A1 (fr) Indicateur de support d'interface n14 pour la continuité de service
WO2021187828A1 (fr) Communication associée à une tranche de réseau
WO2022035230A1 (fr) Procédé de gestion de session
WO2021162498A1 (fr) Procédé de service de système d'avertissement public dans un réseau non public
WO2021206322A1 (fr) Procédé de traitement d'exceptions au contrôle de la congestion pour une opération d'un terminal à multi-usim se déplaçant entre des usim
WO2022014963A1 (fr) Procédé de notification d'une situation de catastrophe par un nœud de réseau ran, et dispositif le prenant en charge
WO2022071673A1 (fr) Support de continuité de service pour une session pdu à routage domestique lorsqu'il n'y a pas d'interface n14 entre un réseau source et un réseau cible
WO2022071674A1 (fr) Procédé et appareil permettant de prendre en charge des informations de filtre d'état d'application dans une collecte de données d'ue utilisant une fonction d'application fournie par une porteuse de communication
WO2022014962A1 (fr) Procédé d'affichage d'ui/ux en fonction d'une notification de situation de catastrophe d'un noeud ran, et dispositif prenant en charge celui-ci
WO2022005207A1 (fr) Procédé de communication par multidiffusion

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21875949

Country of ref document: EP

Kind code of ref document: A1