WO2024005396A1 - Communication relative à un rapport d'événement d'upf - Google Patents

Communication relative à un rapport d'événement d'upf Download PDF

Info

Publication number
WO2024005396A1
WO2024005396A1 PCT/KR2023/007742 KR2023007742W WO2024005396A1 WO 2024005396 A1 WO2024005396 A1 WO 2024005396A1 KR 2023007742 W KR2023007742 W KR 2023007742W WO 2024005396 A1 WO2024005396 A1 WO 2024005396A1
Authority
WO
WIPO (PCT)
Prior art keywords
upf
event
performance
reporting
consumer
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/KR2023/007742
Other languages
English (en)
Korean (ko)
Inventor
김현숙
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
LG Electronics Inc
Original Assignee
LG Electronics Inc
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 LG Electronics Inc filed Critical LG Electronics Inc
Publication of WO2024005396A1 publication Critical patent/WO2024005396A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/20—Traffic policing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/08—Testing, supervising or monitoring using real traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports

Definitions

  • This specification relates to mobile communications.
  • 3GPP (3rd Generation Partnership Project) LTE Long-Term Evolution is a technology to enable high-speed packet communication. Many methods have been proposed to achieve the LTE goals of reducing costs for users and operators, improving service quality, expanding coverage, and increasing system capacity. 3GPP LTE requires lower cost per bit, improved service usability, flexible use of frequency bands, simple structure, open interface, and appropriate power consumption of the terminal as high-level requirements.
  • NR New Radio
  • 3GPP identifies the technology components needed to successfully standardize NR that meets both urgent market needs and the longer-term requirements presented by the ITU Radio communication sector (ITU-R) International Mobile Telecommunications (IMT)-2020 process in a timely manner. and must be developed. Additionally, NR should be able to use any spectrum band up to at least 100 GHz, which can be used for wireless communications even in the distant future.
  • ITU-R ITU Radio communication sector
  • IMT International Mobile Telecommunications
  • NR targets a single technology framework that addresses all deployment scenarios, usage scenarios, and requirements, including enhanced Mobile Broadband (eMBB), massive Machine Type-Communications (mMTC), and Ultra-Reliable and Low Latency Communications (URLLC). do. NR must be inherently forward compatible.
  • eMBB enhanced Mobile Broadband
  • mMTC massive Machine Type-Communications
  • URLLC Ultra-Reliable and Low Latency Communications
  • a User Plane Function can send a reporting message to another Network Function (NF).
  • NF Network Function
  • UPF provides a method for conducting communications. The method includes receiving a PDU session establishment request message from a UE; Transmitting a PDU session establishment acceptance message to the UE; Receiving an event subscription request message from the consumer NF; checking whether the performance of the UPF exceeds a UPF performance threshold; and determining whether to stop event reporting for the consumer NF.
  • an apparatus implementing the method is provided.
  • UPF provides a method for conducting communications.
  • the method includes transmitting a PDU session establishment request message to the UPF; And it may include receiving a PDU session establishment acceptance message from the UPF.
  • an apparatus implementing the method is provided.
  • a method for a consumer NF to conduct communication.
  • the method includes sending an event subscription request message to a User Plane Function (UPF); And it may include receiving an event subscription response message from the UPF.
  • UPF User Plane Function
  • an apparatus implementing the method is provided.
  • FIG. 1 shows an example of a communication system to which implementations of the present disclosure are applied.
  • FIG. 2 shows an example of a wireless device to which implementations of the present disclosure are applied.
  • Figure 3 shows an example of a UE to which the implementation of the present specification is applied.
  • Figure 4 shows an example of a 5G system structure to which the implementation of the present specification is applied.
  • Figures 5 and 6 show an example of a PDU session establishment procedure to which the implementation of the present specification is applied.
  • Figure 8 shows an example of the operation of a UE, UPF, and consumer NF according to an embodiment of the disclosure herein.
  • 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, and Single Access (SC-FDMA) systems. It includes a Carrier Frequency Division Multiple Access (MC-FDMA) system and a Multi-Carrier Frequency Division Multiple Access (MC-FDMA) system.
  • CDMA can be implemented through wireless technologies such as Universal Terrestrial Radio Access (UTRA) or CDMA2000.
  • TDMA can be implemented over 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 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 part of Evolved UMTS (E-UMTS) using E-UTRA.
  • 3GPP LTE uses OFDMA in the downlink (DL) and SC-FDMA in the uplink (UL).
  • the evolution of 3GPP LTE includes LTE-A (Advanced), LTE-A Pro, and/or 5G NR (New Radio).
  • implementations herein are primarily described in relation to a 3GPP based wireless communication system.
  • the technical features of this specification are not limited to this.
  • the following detailed description is provided based on a mobile communication system corresponding to a 3GPP-based wireless communication system, but aspects of the present specification that are not limited to a 3GPP-based wireless communication system can be applied to other mobile communication systems.
  • a or B may mean “only A,” “only B,” or “both A and B.” In other words, as used herein, “A or B” may be interpreted as “A and/or B.”
  • A, B or C refers to “only A,” “only B,” “only C,” or “any and all combinations of A, B, and C ( It can mean “any combination of A, B and C)”.
  • the slash (/) or comma used in this specification may mean “and/or.”
  • A/B can mean “A and/or B.”
  • A/B can mean “only A,” “only B,” or “both A and B.”
  • A, B, C can 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 can be interpreted 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”. It may mean “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 It may mean “at least one of A, B and C.”
  • control information may be proposed as an example of “control information.”
  • control information in this specification is not limited to “PDCCH,” and “PDCCH” may be proposed as an example of “control information.”
  • PDCCH control information
  • FIG. 1 shows an example of a communication system to which implementations of the present disclosure are applied.
  • the 5G usage scenario shown in FIG. 1 is only an example, and the technical features of this specification can 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
  • the communication system 1 includes wireless devices 100a to 100f, a base station (BS) 200, and a network 300.
  • Figure 1 illustrates a 5G network as an example of a network of the communication system 1, but the implementation of this specification is not limited to the 5G system and can 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 operate as base stations/network nodes in relation to other wireless devices.
  • 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 include, but are not limited to, robots 100a, vehicles 100b-1 and 100b-2, extended reality (XR; eXtended Reality) devices 100c, portable devices 100d, and home appliances. It may include a product 100e, an Internet-Of-Things (IoT) device 100f, and an Artificial Intelligence (AI) device/server 400.
  • vehicles may include vehicles with wireless communication capabilities, autonomous vehicles, and vehicles capable of vehicle-to-vehicle communication.
  • Vehicles may include unmanned aerial vehicles (UAVs) (e.g., drones).
  • UAVs unmanned aerial vehicles
  • XR devices may include Augmented Reality (AR)/Virtual Reality (VR)/Mixed Realty (MR) devices and may be mounted on vehicles, televisions, smartphones, computers, wearable devices, home appliances, digital signs, vehicles, robots, etc. It can be implemented in the form of a Head-Mounted Device (HMD) or Head-Up Display (HUD).
  • Portable devices may include smartphones, smart pads, wearable devices (e.g. smart watches or smart glasses), and computers (e.g. laptops).
  • Home appliances may include TVs, refrigerators, and washing machines.
  • IoT devices can include sensors and smart meters.
  • the wireless devices 100a to 100f may be referred to as user equipment (UE).
  • UE includes, for example, mobile phones, smartphones, laptop computers, digital broadcasting terminals, PDA (Personal Digital Assistant), PMP (Portable Multimedia Player), navigation systems, slate PCs, tablet PCs, ultrabooks, vehicles, and autonomous driving functions.
  • vehicles connected cars, UAVs, AI modules, robots, AR devices, VR devices, MR devices, holographic devices, public safety devices, MTC devices, IoT devices, medical devices, fintech devices (or financial devices), security devices , weather/environment devices, 5G service-related devices, or 4th Industrial Revolution-related devices.
  • 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 post-5G network.
  • Wireless devices 100a - 100f may communicate with each other via base station 200/network 300, but communicate directly (e.g., sidelink communication) rather than via base station 200/network 300. You may.
  • vehicles 100b-1 and 100b-2 may perform direct communication (e.g., vehicle-to-vehicle (V2V)/vehicle-to-everything (V2X) communication).
  • an IoT device e.g., sensor
  • another IoT device e.g., sensor
  • another wireless device e.g., 100f
  • Wireless communication/connections 150a, 150b, 150c may be established between wireless devices 100a - 100f and/or between wireless devices 100a - 100f and base station 200 and/or between base station 200.
  • wireless communication/connection includes uplink/downlink communication (150a), sidelink communication (150b) (or D2D (Device-To-Device) communication), communication between base stations (150c) (e.g. relay, IAB (Integrated Access and Backhaul) can be established through various RATs (e.g. 5G NR).
  • RATs e.g. 5G NR
  • wireless communication/connection 150a, 150b, and 150c may transmit/receive signals through various physical channels.
  • various configuration information setting processes for transmitting/receiving wireless signals various signal processing processes (e.g. channel encoding/decoding, modulation/demodulation, resource mapping/demapping, etc.), and a resource allocation process, etc. may be performed.
  • NR supports multiple numerologies or subcarrier spacing (SCS) to support various 5G services. For example, if SCS is 15kHz, it supports a wide area in traditional cellular bands, and if SCS is 30kHz/60kHz, it supports dense-urban, lower latency, and wider areas. It supports a wider carrier bandwidth, and when SCS is 60kHz or higher, it supports a bandwidth greater than 24.25GHz to overcome phase noise.
  • SCS subcarrier spacing
  • the NR frequency band can be defined as two types of frequency ranges (FR1, FR2).
  • the values of the frequency range may vary.
  • 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” and may be referred to as MilliMeter Wave (mmW). there is.
  • mmW MilliMeter Wave
  • Frequency range definition frequency range Subcarrier spacing FR1 450MHz - 6000MHz 15, 30, 60kHz FR2 24250MHz - 52600MHz 60, 120, 240kHz
  • FR1 may include a band of 410MHz to 7125MHz as shown in Table 2 below. That is, FR1 may include a frequency band of 6GHz (or 5850, 5900, 5925 MHz, etc.). For example, the frequency band above 6 GHz (or 5850, 5900, 5925 MHz, etc.) included within FR1 may include an unlicensed band. Unlicensed bands can be used for a variety of purposes, for example for communications for vehicles (e.g. autonomous driving).
  • Frequency range definition frequency range Subcarrier spacing FR1 410MHz - 7125MHz 15, 30, 60kHz FR2 24250MHz - 52600MHz 60, 120, 240 kHz
  • wireless communication technologies implemented in the wireless device of the present specification may include NarrowBand IoT (NB-IoT) for low-power communication as well as LTE, NR, and 6G.
  • NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) 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 names.
  • the wireless communication technology implemented in the wireless device of the present specification may perform communication based on LTE-M technology.
  • LTE-M technology may be an example of LPWAN technology and may be called various names such as enhanced MTC (eMTC).
  • eMTC enhanced MTC
  • LTE-M technologies include 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, etc. may be implemented in at least one of various standards, and are not limited to the above-mentioned names.
  • the wireless communication technology implemented in the wireless device of the present specification may include at least one of ZigBee, Bluetooth, and/or LPWAN considering low-power communication, and is limited to the above-mentioned names. That is not the case.
  • ZigBee technology can create PANs (Personal Area Networks) related to small/low-power digital communications based on various standards such as IEEE 802.15.4, and can be called by various names.
  • FIG. 2 shows an example of a wireless device to which implementations of the present disclosure are applied.
  • the first wireless device 100 and/or the second wireless device 200 may be implemented in various forms depending on usage examples/services.
  • ⁇ first wireless device 100 and second wireless device 200 ⁇ are ⁇ wireless devices 100a to 100f and base station 200 ⁇ of FIG. 1, ⁇ wireless devices 100a to 100f ) and wireless devices (100a to 100f) ⁇ and/or ⁇ base station 200 and base station 200 ⁇ .
  • the first wireless device 100 and/or the second wireless device 200 may be composed of various components, devices/parts and/or modules.
  • First wireless device 100 may include at least one transceiver, such as transceiver 106, at least one processing chip, such as processing chip 101, and/or one or more antennas 108.
  • transceiver 106 such as transceiver 106
  • processing chip 101 such as processing chip 101
  • antennas 108 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. Additionally and/or alternatively, memory 104 may include processing chip 101. ) can be placed externally.
  • Processor 102 may control memory 104 and/or transceiver 106 and may be configured to implement the descriptions, functions, procedures, suggestions, methods and/or operational flow diagrams disclosed herein.
  • 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 wireless 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. Memory 104 may include firmware and/or code, instructions, and/or sets of instructions that, when executed by processor 102, perform the descriptions, functions, procedures, suggestions, methods, and/or operational flow diagrams disclosed herein.
  • Software code 105 may be stored. For example, firmware and/or software code 105 may, when executed by processor 102, implement instructions that perform the descriptions, functions, procedures, suggestions, methods and/or operational flow diagrams disclosed herein. For example, firmware and/or software code 105 may control processor 102 to perform one or more protocols. For example, firmware and/or 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 RAT (eg, LTE or NR).
  • Transceiver 106 may be coupled to processor 102 to transmit and/or receive wireless signals via one or more antennas 108.
  • Each transceiver 106 may include a transmitter and/or receiver.
  • the transceiver 106 can be used interchangeably with the RF (Radio Frequency) 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 transceiver 206, at least one processing chip, such as processing chip 201, and/or one or more antennas 208.
  • Processing chip 201 may include at least one processor, such as processor 202, and at least one memory, such as memory 204. Additionally and/or alternatively, memory 204 may include processing chip 201. ) can be placed externally.
  • Processor 202 may control memory 204 and/or transceiver 206 and may be configured to implement the descriptions, functions, procedures, suggestions, methods and/or operational flow diagrams disclosed herein.
  • the processor 202 may process 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 wireless 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.
  • Memory 204 may include firmware and/or code, instructions, and/or sets of 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 be stored.
  • firmware and/or software code 205 may, when executed by processor 202, implement instructions that perform the descriptions, functions, procedures, suggestions, methods and/or operational flow diagrams disclosed herein.
  • firmware and/or software code 205 may control processor 202 to perform one or more protocols.
  • firmware and/or software code 205 may control processor 202 to perform one or more air interface protocol layers.
  • the processor 202 and memory 204 may be part of a communication modem/circuit/chip designed to implement RAT (eg, LTE or NR).
  • Transceiver 206 may be coupled to processor 202 to transmit and/or receive wireless signals via one or more antennas 208.
  • Each transceiver 206 may include a transmitter and/or receiver.
  • the transceiver 206 can 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.
  • one or more processors 102, 202 may support one or more layers (e.g., a physical (PHY) layer, a Media Access Control (MAC) layer, a Radio Link Control (RLC) layer, a Packet Data Convergence Protocol (PDCP) layer, Functional layers such as RRC (Radio Resource Control) layer and SDAP (Service Data Adaptation Protocol) layer) can be implemented.
  • layers e.g., a physical (PHY) layer, a Media Access Control (MAC) layer, a Radio Link Control (RLC) layer, a Packet Data Convergence Protocol (PDCP) layer, Functional layers such as RRC (Radio Resource Control) layer and SDAP (Service Data Adaptation Protocol) layer
  • PHY physical
  • MAC Media Access Control
  • RLC Radio Link Control
  • PDCP Packet Data Convergence Protocol
  • Functional layers such as RRC (Radio Resource Control) layer and SDAP (Service Data
  • One or more processors 102, 202 may process one or more Protocol Data Units (PDUs), one or more Service Data Units (SDUs), messages, and controls according to the descriptions, functions, procedures, suggestions, methods, and/or operational flow diagrams disclosed herein. It can generate information, data or information.
  • One or more processors 102, 202 may process signals (e.g., baseband) containing PDUs, SDUs, messages, control information, data, or information in accordance with the descriptions, functions, procedures, suggestions, methods, and/or operational flow diagrams disclosed herein. signal) can be generated and provided to one or more transceivers (106, 206).
  • One or more processors 102, 202 may receive signals (e.g., baseband signals) from one or more transceivers 106, 206, and the descriptions, functions, procedures, suggestions, methods, and/or operational flow diagrams disclosed herein. Depending on the PDU, SDU, message, control information, data or information can be obtained.
  • signals e.g., baseband signals
  • One or more processors 102, 202 may be referred to as a controller, microcontroller, microprocessor, and/or microcomputer.
  • 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
  • one or more processors 102, 202 may include a communication control processor, an application processor (AP), an electronic control unit (ECU), a central processing unit (CPU), and a graphics processing unit. It can be configured by a set of (GPU; Graphic Processing Unit) and a memory control processor.
  • One or more memories 104, 204 may be connected to one or more processors 102, 202 and may store various types of data, signals, messages, information, programs, codes, instructions, and/or instructions.
  • One or more memories 104 and 204 include random access memory (RAM), dynamic RAM (DRAM), read-only memory (ROM), erasable programmable ROM (EPROM), flash memory, volatile memory, non-volatile memory, hard drive, It may consist of registers, cache memory, computer-readable storage media, and/or combinations thereof.
  • RAM random access memory
  • DRAM dynamic RAM
  • ROM read-only memory
  • EPROM erasable programmable ROM
  • flash memory volatile memory
  • non-volatile memory hard drive
  • It may consist of registers, cache memory, computer-readable storage media, and/or combinations thereof.
  • One or more memories 104, 204 may be located internal to and/or external to 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.
  • 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 operational flow diagrams disclosed herein to one or more other devices. .
  • One or more transceivers 106, 206 may receive user data, control information, wireless signals/channels, etc. referred to in the descriptions, functions, procedures, suggestions, methods and/or operational flow diagrams disclosed herein from one or more other devices. there is.
  • one or more transceivers 106 and 206 may be connected to one or more processors 102 and 202 and may transmit and receive wireless signals.
  • one or more processors 102 and 202 may control one or more transceivers 106 and 206 to transmit user data, control information, wireless signals, etc. to one or more other devices. Additionally, one or more processors 102 and 202 may control one or more transceivers 106 and 206 to receive user data, control information, wireless signals, etc. from one or more other devices.
  • One or more transceivers (106, 206) may be connected to one or more antennas (108, 208). Additionally and/or alternatively, one or more transceivers (106, 206) may include one or more antennas (108, 208). One or more transceivers (106, 206) transmit, through one or more antennas (108, 208), user data, control information, and wireless signals/channels referred to in the descriptions, functions, procedures, proposals, methods, and/or operational flow diagrams disclosed herein. It may be configured to transmit and receive, etc.
  • 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 (106, 206) process the received user data, control information, wireless signals/channels, etc. using one or more processors (102, 202). 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, wireless 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 an (analog) oscillator and/or filter.
  • one or more transceivers (106, 206) up-convert an OFDM baseband signal to an OFDM signal through an (analog) oscillator and/or filter under the control of one or more processors (102, 202). , the up-converted OFDM signal can be transmitted at the carrier frequency.
  • One or more transceivers (106, 206) receive an OFDM signal at a carrier frequency and, under the control of one or more processors (102, 202), down-convert the OFDM signal to an OFDM baseband signal via an (analog) oscillator and/or filter ( down-convert).
  • wireless devices 100 and 200 may further include additional components.
  • Additional components 140 may be configured in various ways depending on the type of wireless device 100 or 200.
  • additional components 140 may include at least one of a power unit/battery, an input/output (I/O) device (e.g., an audio I/O port, a video I/O port), a drive device, and a computing device. You can.
  • Additional components 140 may be connected to one or more processors 102, 202 through various technologies, such as wired or wireless connections.
  • the UE may operate as a transmitting device in the uplink and as a receiving device in the downlink.
  • the base station may operate as a receiving device in the UL and as a transmitting device in the DL.
  • the first wireless device 100 operates as a UE and the second wireless device 200 operates as a base station.
  • a processor 102 connected to, mounted on, or released from the first wireless device 100 may perform UE operations according to implementations herein or may use transceiver 106 to perform UE operations according to implementations herein. It can be configured to control.
  • the processor 202 connected to, mounted on, or released from 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 the implementation of the present specification. It can be.
  • the base station may be referred to as Node B, eNode B (eNB), or gNB.
  • Node B Node B
  • eNode B eNode B
  • gNB gNode B
  • Figure 3 shows an example of a UE to which the implementation of the present specification is applied.
  • UE 100 may correspond to the first wireless device 100 of FIG. 2.
  • UE 100 includes a processor 102, memory 104, transceiver 106, one or more antennas 108, power management module 141, battery 142, display 143, keypad 144, and SIM.
  • SIM Subscriber Identification Module
  • Processor 102 may be configured to implement the descriptions, functions, procedures, suggestions, methods and/or operational flow diagrams disclosed herein. Processor 102 may be configured to control one or more other components of UE 100 to implement the descriptions, functions, procedures, suggestions, methods and/or operational flow diagrams disclosed herein.
  • a layer of air interface protocols may be implemented in processor 102.
  • Processor 102 may include an ASIC, other chipset, logic circuitry, and/or data processing devices.
  • 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).
  • processors 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®, and ATOM TM series processors made by Intel®. Alternatively, it can be found 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 e.g., procedures, functions, etc.
  • Modules may be stored in memory 104 and executed by processor 102.
  • Memory 104 may be implemented within processor 102 or external to processor 102, in which case it may be communicatively coupled to processor 102 through various methods known in the art.
  • Transceiver 106 is operatively coupled to processor 102 and transmits and/or receives wireless signals.
  • Transceiver 106 includes a transmitter and a receiver.
  • 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 results 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 associated keys, and is used to identify and authenticate subscribers in mobile phone devices such as mobile phones and computers. 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.
  • Figure 4 shows an example of a 5G system structure to which the implementation of the present specification is applied.
  • the 5G system (5GS; 5G system) structure consists of the following network functions (NF).
  • Data Network e.g. operator services, Internet access or third-party services
  • Figure 4 shows the 5G system architecture for the non-roaming case using a reference point representation that shows how the various network functions interact with each other.
  • the 5G system architecture includes the following reference points:
  • the following baseline shows the interactions that exist between NF services in NF.
  • two NFs may need to be connected to each other to serve the UE.
  • the PDU session establishment procedure is described. Please refer to section 4.3.2 of 3GPP TS 23.502 V16.3.0 (2019-12).
  • Figures 5 and 6 show an example of a PDU session establishment procedure to which the implementation of the present specification is applied.
  • Establishing a PDU session may involve:
  • a PDU session may be (a) associated with a single connection type at any given time, either a 3GPP connection or a non-3GPP connection, or (b) associated with multiple connection types simultaneously, i.e., one 3GPP connection and one non-3GPP connection. It can be related.
  • a PDU session associated with multiple access types is called a multi access (MA) PDU session and may be requested by a UE that supports access traffic steering, switching, splitting (ATSSS).
  • MA multi access
  • Figures 5 and 6 specify procedures for establishing a PDU session associated with a single connection type at a given time.
  • Step 1 To establish a new PDU session, the UE creates a new PDU session ID.
  • the UE transmits a NAS message including a PDU session establishment request message in the N1 SM container to initiate the PDU session establishment procedure requested by the UE.
  • the PDU session establishment request message includes PDU session ID, Requested PDU Session Type, requested session and service continuity (SSC) mode, 5G SM capability, Protocol Configuration Options (PCO), and SM. Includes PDU DN Request Container (SM PDU DN Request Container), UE Integrity Protection Maximum Data Rate, etc.
  • PDU session establishment is a request to establish a new PDU session
  • the request type indicates "Initial Request.” If the request refers to an existing PDU session being switched between a 3GPP connection and a non-3GPP connection, or a PDU session handover from an existing packet data network (PDN) connection in the EPC, the request type is "Existing PDU Session”. ".
  • the request type indicates "Emergency Request.” If the request refers to an existing PDU session for emergency services being switched between a 3GPP connection and a non-3GPP connection, or a PDU session handover from an existing PDN connection for emergency services in the EPC, the request type is "Existing emergency PDU session ( Existing Emergency PDU Session)”.
  • the UE includes the S-NSSAI from the allowed NSSAI of the current connection type. If a Mapping Of Allowed NSSAI is provided to the UE, the UE provides both the S-NSSAI of the visited VPLMN (VPLMN) from the allowed NSSAI and the corresponding S-NSSAI of the HPLMN from the mapping of the allowed NSSAI. .
  • VPLMN visited VPLMN
  • Step 2 AMF selects SMF. If the request type indicates "initial request", or if the request is due to a handover from an EPS or another AMF-provided non-3GPP connection, the AMF will determine the connection type of the PDU session as well as the association of S-NSSAI(s), DNN ( data network name), PDU session ID, and SMF ID are saved.
  • the AMF selects the SMF and stores the new PDU session ID, S-NSAI(s), and the association of the selected SMF ID. .
  • the AMF selects an SMF based on the SMF-ID received from the UDM. AMF updates the stored connection type for the PDU session.
  • the PDU session establishment procedure can be performed in the following cases.
  • AMF rejects the PDU session establishment request with an appropriate rejection reason.
  • AMF rejects requests from emergency registered UEs where the request type does not indicate "emergency request” or "existing emergency PDU session".
  • Step 3 If the AMF is not associated with an SMF for the PDU session ID provided by the UE (e.g. when the request type indicates "initial request"), the AMF sends the Create SM Context request procedure (e.g. Nsmf_PDUSession_CreateSMContext Request). If the AMF is already associated with the SMF for the PDU session ID provided by the UE (e.g. when the request type indicates "existing PDU session"), the AMF calls the Update SM Context Request procedure (e.g. Nsmf_PDUSession_UpdateSMContext Request) do.
  • the Create SM Context request procedure e.g. Nsmf_PDUSession_CreateSMContext Request
  • the AMF calls the Update SM Context Request procedure (e.g. Nsmf_PDUSession_UpdateSMContext Request) do.
  • AMF transmits the S-NSSAI of the serving PLMN from the allowed NSSAI to the SMF.
  • the AMF also transmits the corresponding S-NSSAI of the HPLMN from the mapping of allowed NSSAIs to the SMF.
  • the AMF ID is the UE's GUAMI and uniquely identifies the AMF serving the UE.
  • AMF delivers the PDU session ID along with the N1 SM container containing the PDU session establishment request message received from the UE.
  • GPSI generator public subscription identifier
  • AMF provides PEI instead of SUPI. If a UE in limited service state is registered for emergency services while providing SUPI but is not authenticated, the AMF indicates that SUPI is not authenticated. If the SMF does not receive SUPI for the UE or the AMF indicates that the SUPI is not authenticated, it determines that the UE is not authenticated.
  • AMF can include the PCF ID in Nsmf_PDUSession_CreateSMContext. This PCFID identifies the home PCF (H-PCF) in the non-roaming case and the visited PCF (V-PCF) in the LBO roaming case.
  • Step 4 If the session management subscription data for the S-NSSAI of the corresponding SUPI, DNN, or HPLMN is not available, the SMF may retrieve the session management subscription data from the UDM, and this subscription You can be notified when your data is modified.
  • Step 5 The SMF sends a create SM context response message (e.g., Nsmf_PDUSession_CreateSMContext Response) or an update SM context response message (e.g., Nsmf_PDUSession_UpdateSMContext Response) to the AMF, depending on the request received in step 3.
  • a create SM context response message e.g., Nsmf_PDUSession_CreateSMContext Response
  • an update SM context response message e.g., Nsmf_PDUSession_UpdateSMContext Response
  • the SMF If the SMF received the Nsmf_PDUSession_CreateSMContext Request in step 3 and can process the PDU session establishment request, the SMF creates an SM context and responds to the AMF by providing the SM context ID.
  • the SMF rejects the UE request via a NAS SM signal including the relevant SM rejection reason by responding to the AMF with an Nsmf_PDUSession_CreateSMContext Response.
  • the SMF also indicates to the AMF that the PDU session ID is considered released and the SMF proceeds to step 20 below and the PDU session establishment procedure is stopped.
  • Step 6 Optional secondary authentication/authorization may be performed.
  • Step 7a When dynamic policy and charging control (PCC) is used for the PDU session, the SMF may perform PCF selection.
  • PCC dynamic policy and charging control
  • Step 7b The SMF performs the SM policy association establishment procedure to establish the SM policy association with the PCF and obtain the basic PCC rules for the PDU session.
  • Step 8 SMF selects one or more UPFs.
  • Step 9 The SMF may perform the SM policy association modification procedure initiated by the SMF to provide information about the satisfied policy control request trigger conditions.
  • Step 10 If the request type indicates "initial request", the SMF may initiate an N4 Session Establishment procedure with the selected UPF. Otherwise, the SMF may initiate an N4 Session Modification procedure with the selected UPF.
  • the SMF may send an N4 session establishment/modification request to the UPF and provide packet detection, enforcement and reporting rules to be installed in the UPF for the PDU session.
  • UPF can confirm by sending an N4 session establishment/modification response.
  • Step 11 SMF sends an N1N2 message transfer message (e.g. Namf_Communication_N1N2 Message Transfer) to AMF.
  • N1N2 message transfer message e.g. Namf_Communication_N1N2 Message Transfer
  • the N1N2 message delivery message may include N2 SM information.
  • N2 SM information carries the following information to be delivered by AMF to (R)AN.
  • QFI QoS flow ID
  • - PDU Session ID Indicates to the UE the association between the RAN resource and the PDU session for the UE;
  • - S-NSSAI with value for the serving PLMN (i.e. HPLMN S-NSSAI, or VPLMN S-NSSAI for LBO roaming);
  • the N1N2 message delivery message may include the N1 SM container.
  • the N1 SM container includes a PDU session establishment acceptance message to be provided by AMF to the UE.
  • the PDU Session Establishment Accept message includes the S-NSSAI from the permitted NSASI.
  • the PDU Session Establishment Accept message includes the S-NSSAI from the allowed NSSAI for the VPLMN and also includes the corresponding S-NSSAI of the HPLMN from the mapping of the allowed NSSAI received by the SMF in step 3. .
  • multiple QoS rules, QoS flow levels, and QoS parameters may be included in the PDU Session Establishment Accept message and N2 SM information in the N1 SM container.
  • the N1N2 message delivery message includes an N1 SM container including a PDU session establishment rejection message and does not include N2 SM information.
  • (R)AN transmits a NAS message including a PDU session establishment rejection message to the UE. In this case, steps 12-17 below are omitted.
  • Step 12 AMF transmits a NAS message containing the PDU session ID and PDU session establishment acceptance message destined for the UE and the N2 SM information received from the SMF to (R)AN within the N2 PDU session request message.
  • Step 13 (R)AN may perform AN-specific signal exchange with the UE related to information received from the SMF.
  • the UE may perform RRC connection reconfiguration with the UE to set the necessary NG-RAN resources in relation to the QoS rules for the PDU session request received in step 12.
  • (R)AN delivers the NAS message (PDU session ID, N1 SM container (PDU session establishment acceptance message)) received in step 12 to the UE.
  • (R)AN provides NAS messages to the UE only if the AN-specific signaling exchange with the UE includes adding (R)AN resources related to the received N2 command.
  • steps 14 to 16b and 17 below are omitted.
  • Step 14 (R)AN transmits an N2 PDU session response message to AMF.
  • the N2 PDU session response message may include PDU session ID, cause, N2 SM information (PDU session ID, AN tunnel information, accepted/rejected QFI list, user plane enforcement policy notification), etc.
  • Step 15 AMF sends an update SM context request message (e.g. Nsmf_PDUSession_UpdateSMContext Request) to SMF.
  • AMF transmits the N2 SM information received from (R)AN to SMF.
  • Step S16a SMF initiates the N4 session modification procedure with UPF.
  • SMF provides AN tunnel information and corresponding forwarding rules to UPF.
  • Step S16b UPF provides an N4 session modification response to SMF.
  • the UPF can forward any DL packets that may have been buffered for this PDU session to the UE.
  • Step 16c If the SMF is not yet registered for this PDU session, the SMF may register with the UDM for the given PDU session.
  • Step 17 SMF transmits an update SM context response message (e.g. Nsmf_PDUSession_UpdateSMContext Response) to AMF.
  • an update SM context response message e.g. Nsmf_PDUSession_UpdateSMContext Response
  • AMF delivers relevant events to which SMF has subscribed.
  • Step 18 If the PDU session establishment is not successful during the procedure at any time after step 5, the SMF may call Nsmf_PDUSession_SMContextStatusNotify (release) to notify the AMF. The SMF may also release the N4 session that was created, the PDU session address (e.g. IP address) if assigned, and possibly its association with the PCF. In this case, step 19 below is omitted.
  • Nsmf_PDUSession_SMContextStatusNotify release
  • the SMF may also release the N4 session that was created, the PDU session address (e.g. IP address) if assigned, and possibly its association with the PCF.
  • step 19 is omitted.
  • Step 19 For PDU session type IPv6 or IPv4v6, SMF may generate an IPv6 Router Advertisement and transmit it to the UE.
  • Step 20 The SMF may perform SM policy association modifications initiated by the SMF.
  • Step 21 If PDU session establishment fails after step 4, and the SMF no longer processes the UE's PDU session, the SMF may unsubscribe upon modification of session management subscription data.
  • UPF exposure information for other NFs may be supported.
  • various examples of the disclosure herein describe how to reduce the UPF performance impact due to reporting UPF data to a NF consumer, such as a Network Data Analytics Function (NWDAF).
  • NWDAAF Network Data Analytics Function
  • UPF user plane traffic processing performance is not degraded.
  • the scope of UPF data collection by NWDAF could be AoI-specific or S-NSSAI-specific (e.g., Service Experience and Abnormal Behavior Analysis), and UPF would report the data to NWDAF.
  • the UPF data collection range per AoI or S-NSSAI refers to UE-level UPF data of UPF, which may be for all UEs connected to the indicated AoI or S-NSSAI. If the number of UEs is quite large, the reporting impact on UPF performance cannot be ignored.
  • UPF data for data analysis is not always time-sensitive (especially for training dataset collection). Although an event is detected, it is recommended not to immediately send notification of that event to NWDAF when UPF is at peak times. So you can improve event subscription like this:
  • Reporting proposal information includes reporting urgency and reporting window two information.
  • the reporting urgency information indicates whether this event reporting is delay tolerant, that is, whether the event reporting can be delayed.
  • the reporting window defines the last reporting valid time. For example, if an event can be reported within 2 hours of being detected, the reporting window is 2 hours.
  • the granularity of event subscription and reporting is at the UE level. That is, each UE may have separate event subscriptions and event reporting. To reduce the number of event notifications, when a UE-level UPF event is subscribed to, subscription and notification can be performed at each node level.
  • event subscription is performed at the node level.
  • UPF can aggregate event notifications.
  • a UE ID or other identifier may be added within the event notification to distinguish between other UE-related UPF events. Therefore, event notifications sent to NF consumers can be reduced.
  • the above mechanism can be applied generally to all NF consumers of UPF event exposure services.
  • New IEs e.g. reporting proposal information
  • This may include reporting urgency and reporting period information.
  • the NF consumer may support aggregating other UPF event subscriptions/notifications at the UE level according to the node level.
  • UPF may delay event reporting depending on the reporting proposal information received from the event subscription.
  • UPF can support aggregating different UPF event subscriptions/notifications by node level depending on the node level.
  • UPF can expose network information to NFs through the UPF event exposure service.
  • 5G evolution/6G system implementation in a zero-touch configuration/operation environment with expanded network automation can be carried out efficiently.
  • zero-touch configuration/operation may mean, for example, a set of technologies and processes that automate the setup and management of a network with little or no human intervention.
  • the goal of zero-touch configuration/operation can be to reduce the time, effort, and cost associated with network deployment and management while improving the overall efficiency and performance of the network.
  • Zero-touch configuration/operation can be achieved using advanced automation technologies such as AI/ML, robotics, and software-defined networking (SDN).
  • a network node may perform functions and/or operations such as the examples below.
  • the network node may be an NF consumer (e.g., AF, NWDAF, NEF, etc.) that uses the event exposure service of UPF. Additionally, in the examples disclosed herein, the network node may be a UPF.
  • NF consumers of UPF event exposure services may perform the following functions and/or operations:
  • - NF consumers can request event reports with considerations for NF performance.
  • Event reporting information may be used.
  • NF consumers can use event reporting information.
  • Report request information may be added to event report information. That is, event report information may include report request information.
  • UPF may perform the following functions and/or operations:
  • UPF can pause (or mute) and/or resume event reporting.
  • UPF event exposure considering UPF performance is explained.
  • UPF user plane traffic processing performance should not be degraded due to the mechanisms defined below.
  • the example described below may be an example to solve problems related to supporting exposure of UPF information to other NFs.
  • a consumer NF e.g. NEF, AF
  • NEF EventExposure Service
  • Table 3 is an example of event reporting information used by consumer NF and UPF.
  • Event reporting mode Mode of reporting For example, reporting up to a maximum number of reports, reporting periodically based on a cycle, reporting up to a maximum period of time, reporting when a threshold is reached, etc.
  • mandatory Maximum number of reports Maximum number of reports at which event subscription will end (see NOTE 1)
  • Maximum duration of reporting Maximum period of time after which the existence of an event subscription ends (see NOTE 1)
  • Immediate reporting flag The event provider NF immediately informs the consumer NF of the current status (if possible) of the subscribed event.
  • Sampling ratio Sampling percentage of affected UEs (1%..100%).
  • Group Reporting Guard Time This is a parameter for setting up group-based monitoring and indicates the time during which monitoring event reporting related to UEs in the group can be aggregated before being transmitted to the consumer NF.
  • Deactivate notification flag A parameter that instructs the event provider NF to pause (or mute) notifications for available events until the event consumer NF provides a retrieval notification flag to retrieve the stored event.
  • Retrieval notification flag A parameter that instructs the event provider NF to notify the event consumer NF with stored events and again pause (or mute) future event notifications.
  • Granularity of dynamics The maximum dynamic amount of events over which event notifications can be skipped.
  • Reporting type Event Provider NF only reports if an event is different from a previously notified event.
  • Reporting Thresholds represent conditions for the level that must be reached for reporting.
  • “Consideration on NF (e.g. UPF) performance” flag (“Consideration on NF (e.g. UPF) performance” flag) If a threshold of NF performance is exceeded, it notifies the event provider NF that notification of available events should be paused (or muted). Optionally, the event provider NF can be hinted to send a notification to the event consumer NF if the event performance threshold is not exceeded. This is a flag for the purpose of requesting reporting considering UPF performance. When subscribing to an event for reporting, this flag can be set.
  • the consumer NF can transmit event reporting information including this flag to the UPF. If the NF performance threshold value provided with this flag is exceeded, UPF stops reporting. (In addition, if the performance of the UPF measured by the UPF no longer exceeds the NF performance threshold value at some point, it may imply that the UPF will resume reporting.)
  • Optional NF Performance Threshold The threshold represents the condition of the level that must be reached when considering NF (e.g. UPF) performance. When requesting reporting considering UPF performance, the values/levels that serve as the standard for reporting deactivation/mute can also be provided. If this value is not given separately, it can be assumed that it has been pre-configured. Optional (see NOTE 6)
  • the requester must include one or both of the following: 1) depending on the event reporting mode, 2) the maximum number of reports or 3) the maximum reporting period.
  • the granularity of dynamics includes 1) range of scalar values, 2) event identification list, or 3) previous notification.
  • the range of scalar values applies only to events expressed as numbers (e.g. number of UEs), while others apply to events expressed as identifications (e.g. UE location, UE identification).
  • Table 4 below shows examples of UPF services and UPF service operations.
  • This service can expose relevant information related to UPF to other NFs.
  • This service has one operation (or action):
  • the following events can be notified to the NF consumer:
  • Event notifications may include QoS monitoring reports.
  • an event notification may include the following information:
  • the Nupf_EventExposure_Notify service task may refer to the Notify task (or action) in the Nupf_EventExposure service, according to the example in Table 4.
  • Event ID Event ID
  • UE address e.g. IP address or MAC address
  • Event reporting information for UPF specific as described in the example in Table 3.
  • Event-specific parameters described previously. Event reporting information (for UPF specific) described in Table 3.
  • NWDAF may perform the same operation.
  • NEF may perform the same operation.
  • only either NWDAF or NEF may be used.
  • AF may send an event subscription request message (e.g., Nnef_EventExposureSubscribe Request) to NWDAF and/or NEF.
  • Nnef_EventExposureSubscribe Request e.g., Nnef_EventExposureSubscribe Request
  • the event subscription request message may include event reporting information.
  • Event reporting information may include new flags (e.g., Consideration on NF (e.g UPF) performance" flag in Table 3) and thresholds (e.g., NF Performance Threshold in Table 3).
  • NWDAF and/or NEF may transmit an event subscription request message (e.g., Nnef_EventExposureSubscribe Request) to UPF.
  • AF is the consumer NF for UPF reporting
  • NWDAF and/or NEF may be responsible for delivering AF's subscription request message to UPF.
  • NWDAF and/or NEF may be the consumer NF for UPF reporting, in which case step 1 may be omitted.
  • the event subscription request message may include event reporting information. Event reporting information may include new flags (e.g., Consideration on NF (e.g UPF) performance" flag in Table 3) and thresholds (e.g., NF Performance Threshold in Table 3).
  • UPF may send a response message to the subscription request (e.g., Nupf_EventExposureSubscribe Response) to NWDAF and/or NEF. If the AF sends a subscription request message, NWDAF and/or NEF may send a response message (e.g., Nnef_eventExposureSubscribe Response) to the AF.
  • a response message e.g., Nnef_eventExposureSubscribe Response
  • Steps 1 to 3 are summarized as the following example.
  • a consumer NF e.g., AF, NWDAF, or NEF
  • a consumer NF e.g., AF, NWDAF, or NEF
  • a service After a certain period of time has passed after subscribing to a service, there may be services in which reporting is meaningless, and for which maintaining UPF performance is more important for the operator.
  • a service may be a service that reports traffic information for real-time reference without creating cumulative statistics on specific traffic.
  • the consumer NF may transmit event reporting information (e.g., see the example in Table 3) to the UPF.
  • event reporting information e.g., see the example in Table 3
  • a “Consideration on NF (e.g UPF) performance” flag and NF Performance Threshold may be added to the event reporting information.
  • UPF can check the UPF threshold.
  • UPF can measure the performance of UPF and compare the performance of UPF with UPF threshold.
  • the UPF threshold may be included in event reporting information or may be a preset value.
  • UPF can notify the consumer NF of the event. For example, as shown in the example in Table 4, UPF can notify NF consumers of events such as QoS monitoring results. UPF may send an event notification message (e.g. Nupf_EventExposureNotify) to NWDAF and/or NEF. If AF is also a consumer NF, NWDAF and/or NEF may send a notification message (e.g. Nnef_EventExposureNotify) to AF. In addition, NWDAF and/or NEF may calculate statistical values or predicted values and transmit them to AF, rather than transmitting the information received from UPF as is to AF. Alternatively, NEF can transmit the information received from UPF to AF as is, and NWDAF can collect information received from UPF for a certain period of time and transmit analytics values (statistics and forecast values) to AF.
  • an event notification message e.g. Nupf_EventExposureNotify
  • NWDAF and/or NEF may calculate statistical values or predicted
  • the performance of UPF may exceed the UPF threshold.
  • the UPF may determine that the performance of the UPF has exceeded the UPF's threshold.
  • UPF may stop reporting events.
  • Steps 4 to 7 can be summarized as the following example.
  • UPF can measure performance internally.
  • UPF can measure the performance of UPF.
  • performance can refer to the ability to process data (e.g. computing power).
  • the UPF can start an operation comparing the performance with the UPF threshold value.
  • UPF performance may exceed the UPF threshold value.
  • UPF may discontinue the service (i.e. reporting) to which the consumer NF subscribes. This is because, unlike the prior art, it is more effective to stop reporting rather than delaying it.
  • UPF can continuously check the UPF threshold.
  • the performance of UPF may not exceed the UPF threshold. For example, UPF performance may fall below the UPF threshold.
  • the UPF may decide to resume event reporting when it confirms that the performance of the UPF is below the UPF threshold. In this case, UPF can resume event reporting.
  • UPF can notify the consumer NF of the event. For example, as shown in the example in Table 4, UPF can notify NF consumers of events such as QoS monitoring results. UPF may send an event notification message (e.g. Nupf_EventExposureNotify) to NWDAF and/or NEF. If AF is also a consumer NF, NWDAF and/or NEF may send a notification message (e.g. Nnef_EventExposureNotify) to AF.
  • an event notification message e.g. Nupf_EventExposureNotify
  • NWDAF and/or NEF may send a notification message (e.g. Nnef_EventExposureNotify) to AF.
  • AF can unsubscribe to events.
  • NWDAF and/or NEF may unsubscribe to the event.
  • AF may send an event unsubscription message (e.g., Nnef_EventExposureUnsubscribe) to NWDAF and/or NEF.
  • NWDAF and/or NEF may send an event unsubscription message (e.g., Nupf_EventExposureUnsubscribe) to UPF.
  • UPF may stop checking the UPF threshold.
  • Steps 8 to 11 are summarized as the following example.
  • UPF can continuously measure the performance of UPF. And, UPF can compare the performance of UPF with the UPF threshold. If the performance of the UPF does not exceed the UPF threshold, the UPF can resume the service (i.e. reporting) to which the consumer NF has subscribed.
  • the 5G evolution/6G system in a zero-touch configuration/operation environment can be effectively implemented.
  • the disclosure of this specification may include UPF event exposure considering UPF performance.
  • UPF reporting may be paused (or muted) and then resumed according to a UPF performance threshold set by an operator policy. Then, UPF event exposure can be managed efficiently and can help provide operators with flexibility in network deployment and management.
  • consumer NFs e.g. NEF, AF
  • subscribe to the Event Exposure Service When performing subscriptions, a request can be made to consider UPF performance.
  • UPF is assumed to be monitoring performance itself, and this may vary depending on the implementation.
  • the consumer NF's request is:
  • Thresholds for NF performance can be preset in UPF.
  • the threshold value of NF performance may be transmitted along with a request to consider UPF performance transmitted by the consumer NF.
  • the NF consumer of the UPF event exposure service can request event reporting considering NF performance.
  • UPF can pause/resume event reporting.
  • Figure 8 shows an example of the operation of a UE, UPF, and consumer NF according to an embodiment of the disclosure herein.
  • the operation described in the example of FIG. 7 may also be applied.
  • the operations, contents, etc. are not directly explained in the example of FIG. 8, the operations, contents, etc. described in various examples disclosed in the present specification may be applied.
  • the consumer NF may be NEF and/or NWDAF.
  • the consumer NF may be AF.
  • the operations performed by the consumer NF in FIG. 8 may include all the operations performed by AF, NEF, and/or NWDAF in the example of FIG. 7.
  • steps S901 and S902 may be omitted.
  • step S901 the UE may transmit a PDU session establishment request message to the UPF.
  • the UPF may transmit a PDU session establishment accept message to the UE.
  • the consumer NF may transmit an event subscription request message to the UPF.
  • UPF can send an event notification message to the consumer NF.
  • the event subscription request message may include flag information related to UPF performance.
  • the flag information may be the “Consideration on NF (e.g UPF) performance” flag.
  • the event subscription request message may include event reporting information.
  • the event reporting information may be “Consideration on”, as shown in the example in Table 3.
  • NF (e.g UPF) performance” flag and NF Performance Threshold may be included.
  • the UPF can check the performance of the UPF.
  • UPF can check the UPF threshold.
  • UPF can compare the performance of UPF and UPF threshold. If the performance of the UPF exceeds the UPF threshold, the UPF may stop reporting events to the consumer NF. After stopping event reporting, if the performance of the UPF falls below the UPF threshold, the UPF may resume event reporting.
  • the UPF threshold may be a preset threshold.
  • the first network node e.g., consumer NF of UPF service such as NWDAF, AF, NEF
  • a second network node may measure the performance of the UPF based on a request from the first network node. If the value measured by the UPF exceeds the threshold provided with the request or a pre-configuration threshold, the UPF may stop event reporting.
  • a second network node may measure the performance (eg, performance) of the UPF based on the request. If the measured value is within the threshold provided with the request or a pre-configuration threshold, UPF can resume event reporting that was stopped.
  • a network node may perform functions and/or operations such as the examples below.
  • the network node may be an NF consumer (e.g., AF, NWDAF, NEF, etc.) that uses the event exposure service of UPF. Additionally, in the examples disclosed herein, the network node may be a UPF.
  • NF consumers of UPF event exposure services may perform the following functions and/or actions:
  • - NF consumers can request event reports with considerations for NF performance.
  • Event reporting information may be used.
  • NF consumers can use event reporting information.
  • Report request information may be added to event report information. That is, event report information may include report request information.
  • UPF may perform the following functions and/or operations:
  • UPF can pause (or mute) and/or resume event reporting.
  • UPF can perform UPF threshold checking. For example, UPF can measure the performance of the UPF and determine whether the measured performance is above or below a threshold.
  • UPF exposure information for other NFs may be supported.
  • various examples of the disclosure herein describe ways to reduce UPF performance impact due to UPF data reporting to NF consumers, such as NWDAF.
  • UPF user plane traffic processing performance is not degraded.
  • the scope of UPF data collection by NWDAF could be AoI-specific or S-NSSAI-specific (e.g., Service Experience and Abnormal Behavior Analysis), and UPF would report the data to NWDAF.
  • the UPF data collection range per AoI or S-NSSAI refers to UE-level UPF data of UPF, which may be for all UEs connected to the indicated AoI or S-NSSAI. If the number of UEs is quite large, the reporting impact on UPF performance cannot be ignored.
  • DCCF Data Collection Coordination Function
  • UPF data for data analysis is not always time-sensitive (especially for training dataset collection). Although an event is detected, it is recommended not to immediately send notification of that event to NWDAF when UPF is at peak times. So you can improve event subscription like this:
  • Reporting proposal information includes reporting urgency and reporting window two information.
  • Report urgency information indicates whether this event report is delay tolerant, that is, whether the event report can be delayed.
  • the reporting window defines the last reporting valid time. For example, if an event can be reported within 2 hours of being detected, the reporting window is 2 hours.
  • Report request information may include:
  • An indication may be included that notification of available events will be paused (or muted) (disabled) when the NF performance threshold is exceeded. For example: For example, this could also tell the event provider NF to send a notification to the event consumer NF if the event performance threshold is not exceeded.
  • NF performance threshold Indicates the condition of the level that must be reached for consideration of NF (e.g. UPF) performance.
  • the granularity of event subscription and reporting is at the UE level. That is, each UE may have separate event subscriptions and event reporting. To reduce the number of event notifications, when a UE-level UPF event is subscribed to, subscription and notification can be performed at each node level.
  • event subscription is performed at the node level.
  • UPF can aggregate event notifications.
  • a UE ID or other identifier may be added within the event notification to distinguish between other UE-related UPF events. Therefore, event notifications sent to NF consumers can be reduced.
  • the above mechanism can be applied generally to all NF consumers of UPF event exposure services.
  • NF consumers e.g. AF, NEF, NWDAF
  • UPF event exposure service e.g. AF, NEF, NWDAF
  • event reporting information can be used.
  • the NF consumer can transmit event reporting information to the UPF.
  • event reporting information may be used:
  • New IEs may be added to event reporting information. This may include reporting urgency and reporting period information.
  • the NF consumer may support aggregating different UPF event subscriptions/notifications at the UE level according to the node level; or
  • a new IE that is, reporting request information, may be added to the event reporting information.
  • the NF consumer can support aggregating other UPF event subscriptions/notifications at the UE level according to the node level.
  • UPF may delay event reporting.
  • UPF can pause (or mute)/resume event reporting.
  • UPF can support aggregating different UPF event subscriptions/notifications by node level depending on the node level.
  • network automation can effectively support 5G evolution/6G systems in an expanded zero-touch configuration/operation environment.
  • considering the individual performance of the UPF it may be determined whether to use a mechanism to prevent performance degradation of the UPF. For example, if a certain period of time passes after UPF starts reporting, there may be cases where reporting becomes meaningless. In this case, if there is a service where maintaining UPF performance is more important, the efficiency of the entire system can be increased by stopping rather than delaying reporting performed by UPF.
  • it is possible to determine whether to use a mechanism to prevent performance degradation considering the individual performance of the UPF. By considering the performance of UPF, the efficiency of the overall system can be improved.
  • the operations of the terminal may be implemented by the devices of FIGS. 1 to 3 described above.
  • the terminal e.g., UE
  • the terminal may be the first device 100 or the second device 200 of FIG. 2.
  • operations of a terminal (eg, UE) described herein may be processed by one or more processors 102 or 202.
  • the operations of the terminal described in this specification may be stored in one or more memories 104 or 204 in the form of instructions/programs (e.g. instructions, executable code) executable by one or more processors 102 or 202.
  • One or more processors (102 or 202) control one or more memories (104 or 204) and one or more transceivers (105 or 206) and execute instructions/programs stored in one or more memories (104 or 204) as disclosed herein.
  • the operations of the terminal (e.g., UE) described above can be performed.
  • instructions for performing operations of a terminal (eg, UE) described in the disclosure of this specification may be stored in a non-volatile computer-readable storage medium.
  • the storage medium may be included in one or more memories 104 or 204.
  • the instructions recorded in the storage medium may be executed by one or more processors 102 or 202 to perform operations of the terminal (eg, UE) described in the disclosure of this specification.
  • network nodes e.g., network nodes, consumer NF, UPF, NEF, NWDAF, AF, AMF, SMF, PCF, UDM, DN, etc.
  • base stations e.g., NG-RAN, (R)AN, etc.
  • the network node or base station may be the first device 100 or the second device 200 of FIG. 2 .
  • operations of a network node or base station described herein may be handled by one or more processors 102 or 202.
  • the operations of the terminal described in this specification may be stored in one or more memories 104 or 204 in the form of instructions/programs (e.g. instructions, executable code) executable by one or more processors 102 or 202.
  • One or more processors (102 or 202) control one or more memories (104 or 204) and one or more transceivers (106 or 206) and execute instructions/programs stored in one or more memories (104 or 204) as disclosed herein.
  • the operation of the network node or base station described above can be performed.
  • instructions for performing operations of a network node or base station described in the disclosure of this specification may be stored in a non-volatile (or non-transitory) computer-readable storage medium.
  • the storage medium may be included in one or more memories 104 or 204.
  • instructions recorded in the storage medium may be executed by one or more processors 102 or 202 to perform operations of the network node or base station described in the disclosure of this specification.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

La présente invention concerne un procédé pour effectuer une communication par une UPF. Le procédé peut comprendre les étapes consistant à : recevoir un message de demande d'établissement de session PDU ; transmettre un message d'acceptation d'établissement de session PDU à un UE ; recevoir un message de demande d'abonnement aux événements provenant d'une NF consommatrice ; identifier si la performance de l'UPF dépasse une valeur seuil de performance d'UPF ; et déterminer s'il faut arrêter de rapporter un événement pour la NF consommatrice.
PCT/KR2023/007742 2022-06-30 2023-06-07 Communication relative à un rapport d'événement d'upf Ceased WO2024005396A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US202263357008P 2022-06-30 2022-06-30
US63/357,008 2022-06-30
US202263396629P 2022-08-10 2022-08-10
US63/396,629 2022-08-10

Publications (1)

Publication Number Publication Date
WO2024005396A1 true WO2024005396A1 (fr) 2024-01-04

Family

ID=89380989

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2023/007742 Ceased WO2024005396A1 (fr) 2022-06-30 2023-06-07 Communication relative à un rapport d'événement d'upf

Country Status (1)

Country Link
WO (1) WO2024005396A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20240414794A1 (en) * 2021-11-04 2024-12-12 Telefonaktiebolaget Lm Ericsson (Publ) Methods and apparatuses for same event subscription for multi sessions of one ue
WO2025209096A1 (fr) * 2024-04-03 2025-10-09 华为技术有限公司 Procédé de communication et dispositif de communication
GB2643248A (en) * 2024-08-08 2026-02-11 Nokia Technologies Oy Data collection based on user or packet data unit session markers
WO2026032877A1 (fr) * 2024-08-05 2026-02-12 Telefonaktiebolaget Lm Ericsson (Publ) Optimisation de collecte de données dans un réseau de communication

Non-Patent Citations (5)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Management and orchestration; Performance assurance (Release 17)", 3GPP STANDARD; TECHNICAL SPECIFICATION; 3GPP TS 28.550, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG5, no. V17.1.0, 16 June 2022 (2022-06-16), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, pages 1 - 85, XP052182928 *
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System (5GS); Stage 2 (Release 17)", 3GPP STANDARD; 3GPP TS 23.502, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. V17.5.0, 15 June 2022 (2022-06-15), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, pages 1 - 744, XP052182883 *
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on UPF enhancement for Exposure and SBA (Release 18)", 3GPP STANDARD; TECHNICAL REPORT; 3GPP TR 23.700-62, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, no. V0.3.0, 27 May 2022 (2022-05-27), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, pages 1 - 70, XP052182980 *
CATT: "KI#16, New solution for KI#16: NWDAF assisted UP optimization for EC", 3GPP DRAFT; S2-2003899, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Elbonia; 20200601 - 20200612, 22 May 2020 (2020-05-22), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051889907 *
NOKIA, NOKIA SHANGHAI BELL: "Access Network Performance Measurements", 3GPP DRAFT; S2-1901538_CR23501R16 ATSSS ACCESS NETWORK PERFORMANCE MEASUREMENTS_V3, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Santa Cruz - Tenerife, Spain; 20190225 - 20190301, 19 February 2019 (2019-02-19), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051610149 *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20240414794A1 (en) * 2021-11-04 2024-12-12 Telefonaktiebolaget Lm Ericsson (Publ) Methods and apparatuses for same event subscription for multi sessions of one ue
WO2025209096A1 (fr) * 2024-04-03 2025-10-09 华为技术有限公司 Procédé de communication et dispositif de communication
WO2026032877A1 (fr) * 2024-08-05 2026-02-12 Telefonaktiebolaget Lm Ericsson (Publ) Optimisation de collecte de données dans un réseau de communication
GB2643248A (en) * 2024-08-08 2026-02-11 Nokia Technologies Oy Data collection based on user or packet data unit session markers

Similar Documents

Publication Publication Date Title
WO2021091314A1 (fr) Procédé et appareil de gestion de tranches de réseau dans un système de communication sans fil
WO2024005396A1 (fr) Communication relative à un rapport d'événement d'upf
WO2021167233A1 (fr) Communication relative à une tranche de réseau
WO2023172094A1 (fr) Communication associée à des informations d'analyse
WO2024010230A1 (fr) Apprentissage fédéré
WO2023182874A1 (fr) Communication associée à un état de communication
WO2024005429A1 (fr) Communication relative à un intervalle de recherche de plmn
WO2023182728A1 (fr) Procédé d'enregistrement de réseau pour transmission de trafic et dispositif prenant en charge celui-ci
WO2023101391A1 (fr) Procédé de mesure d'utilisation de trafic
WO2023146253A1 (fr) Procédé destiné à favoriser efficacement la qs de services ia et aa
WO2024147621A1 (fr) Communication basée sur un calcul de périphérie
WO2025033836A1 (fr) Communication associée à une demande d'af
WO2024025276A1 (fr) Communication relative à une session d'unité de données de protocole (pdu) redondante
WO2024029821A1 (fr) Session pdu en mode lbo
WO2025053506A1 (fr) Procédé et appareil pour des opérations tenant compte de la consommation d'énergie dans un système de communication sans fil
WO2025028818A1 (fr) Communication basée sur une zone de service de tranche de réseau
WO2025206791A1 (fr) Communication basée sur une session multi-accès
WO2026034938A1 (fr) Communication basée sur ntz
WO2026089434A1 (fr) Communication associée à un dns
WO2025063616A1 (fr) Communication associée à une station de base mobile
WO2025071197A1 (fr) Communication basée sur des trajets multiples
WO2025211552A1 (fr) Rejet de paquets
WO2024186077A1 (fr) Tranche de réseau
WO2024162818A1 (fr) Commutation de trajet
WO2025075357A1 (fr) Service de réseau de données de zone locale

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23831756

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 23831756

Country of ref document: EP

Kind code of ref document: A1