Packet discard

Abstract

One disclosure of the present specification provides a method. The method may comprise the steps of: receiving a random access preamble message from a UE; transmitting a response message related to random access to the UE; receiving an N2 message from a first network entity related to mobility; and transmitting notification information related to an event related to an active discard to the first network entity or a second network entity related to a user plane.

Description

Packet discard

[0001] This specification relates to mobile communications.

[0002] 3GPP (3rd Generation Partnership Project) LTE (Long-Term Evolution) is a technology designed to enable high-speed packet communications. Numerous approaches have been proposed to achieve LTE's goals of reducing costs for users and operators, improving service quality, expanding coverage, and increasing system capacity. 3GPP LTE's high-level requirements include reduced cost per bit, improved service availability, flexible use of frequency bands, a simple architecture, open interfaces, and adequate power consumption for terminals.

[0003] The International Telecommunication Union (ITU) and 3GPP have begun work on developing requirements and specifications for New Radio (NR) systems. 3GPP must identify and develop the technical components necessary to successfully standardize NR, meeting both urgent market needs and the longer-term requirements outlined by the ITU Radio communication sector (ITU-R) International Mobile Telecommunications (IMT)-2020 process. NR must also be able to utilize any spectrum band up to at least 100 GHz, ensuring that it remains available for wireless communications well into the future.

[0004] NR aims to be 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). NR must be inherently forward-compatible.

[0005] Base stations can perform active packet discarding depending on congestion conditions. However, conventional technology has the problem that entities other than the base station (e.g., terminals, application servers, etc.) cannot detect whether active packet discarding is occurring, resulting in inefficient communication.

[0006] According to one embodiment of the present disclosure, a method is provided. The method may include: receiving a random access preamble message from a UE; transmitting a response message related to random access to the UE; receiving an N2 message from a first network entity related to mobility; and transmitting notification information related to an event related to the active abandonment to the first network entity or a second network entity related to a user plane.

[0007] According to one embodiment, a device implementing the method is provided.

[0008] According to one embodiment of the present disclosure, a method is provided. The method may include the steps of: receiving a PDU session establishment request message from a UE; transmitting a PDU session establishment acceptance message to the UE; receiving a notification message related to policy control including a PCC rule from a first network node related to the policy; and transmitting QoS monitoring settings related to the active discard to a second network node related to a user plane and / or to a base station via a third network node related to mobility.

[0009] According to one embodiment, a device implementing the method is provided.

[0010] According to one embodiment of the present disclosure, a method is provided. The method may include: receiving a request message from a first network node involved in network exposure; and transmitting a notification message related to policy control, including a PCC rule configured based on the request message, to a second network node involved in the session.

[0011] According to one embodiment, a device implementing the method is provided.

[0012] Figure 1 illustrates an example of a communication system to which the implementation of this specification is applied.

[0013] Figure 2 illustrates an example of a wireless device to which the implementation of the present specification is applied.

[0014] Figure 3 shows an example of a UE to which the implementation of this specification is applied.

[0015] Figure 4 shows an example of a 5G system structure to which the implementation of this specification is applied.

[0016] Figures 5 and 6 illustrate examples of a PDU session establishment procedure to which the implementation of the present specification applies.

[0017] FIG. 7a and FIG. 7b illustrate a first example of a procedure according to one embodiment of the disclosure of the present specification.

[0018] FIG. 8 illustrates a second example of a procedure according to one embodiment of the disclosure of the present specification.

[0019] FIG. 9 illustrates a third example of a procedure according to one embodiment of the disclosure of the present specification.

[0020] FIG. 10 illustrates an example of operations according to one embodiment of the disclosure of the present specification.

[0021] The following techniques, devices, and systems can be applied to various wireless multiple access systems. Examples of multiple access systems include Code Division Multiple Access (CDMA) systems, Frequency Division Multiple Access (FDMA) systems, Time Division Multiple Access (TDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Multi-Carrier Frequency Division Multiple Access (MC-FDMA) systems. CDMA can be implemented using wireless technologies such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA can be implemented using 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 using wireless technologies such as IEEE (Institute of Electrical and Electronics Engineers) 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). 3GPP (3rd Generation Partnership Project) Long-Term Evolution (LTE) is part of E-UMTS (Evolved UMTS) that utilizes E-UTRA.3GPP LTE uses OFDMA in the downlink (DL) and SC-FDMA in the uplink (UL). Evolution of 3GPP LTE includes LTE-A (Advanced), LTE-A Pro, and / or 5G NR (New Radio).

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

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

[0024] As used herein, "A or B" can mean "only A," "only B," or "both A and B." Alternatively, as used herein, "A or B" can be interpreted as "A and / or B." For example, as used herein, "A, B or C" can mean "only A," "only B," "only C," or "any combination of A, B and C."

[0025] As used herein, a slash ( / ) or a comma can mean "and / or." For example, "A / B" can mean "A and / or B." Accordingly, "A / B" can mean "only A," "only B," or "both A and B." For example, "A, B, C" can mean "A, B, or C."

[0026] In this specification, “at least one of A and B” may mean “only A,” “only B,” or “both A and B.” Additionally, in this specification, the expressions “at least one of A or B” or “at least one of A and / or B” may be interpreted identically to “at least one of A and B.”

[0027] Additionally, in this specification, “at least one of A, B and C” can mean “only A”, “only B”, “only C”, or “any combination of A, B and C”. Additionally, “at least one of A, B or C” or “at least one of A, B and / or C” can mean “at least one of A, B and C”.

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

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

[0030] Although not limited thereto, the various descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed herein may be applied to various fields requiring wireless communication and / or connectivity between devices (e.g., 5G).

[0031] Hereinafter, the present specification will be described in more detail with reference to the drawings. In the following drawings and / or description, the same reference numbers may refer to the same or corresponding hardware blocks, software blocks, and / or functional blocks, unless otherwise indicated.

[0032] Figure 1 illustrates an example of a communication system to which the implementation of this specification is applied.

[0033] 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.

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

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

[0036] The base station (200) and the network (300) may be implemented as wireless devices, and a particular wireless device may operate as a base station / network node in relation to other wireless devices.

[0037] The 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. The wireless devices (100a to 100f) may 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), a home appliance (100e), an Internet-of-Things (IoT) device (100f), and an artificial intelligence (AI) device / server (400). For example, the vehicles may include vehicles having wireless communication capabilities, autonomous vehicles, and vehicles capable of performing vehicle-to-vehicle communication. The vehicles may include unmanned aerial vehicles (UAVs) (e.g., drones). XR devices may include AR (Augmented Reality) / VR (Virtual Reality) / MR (Mixed Reality) devices, and may be implemented in the form of HMD (Head-Mounted Device) and HUD (Head-Up Display) mounted on vehicles, televisions, smartphones, computers, wearable devices, home appliances, digital signs, vehicles, robots, etc. Portable devices may include smartphones, smart pads, wearable devices (e.g., smart watches or smart glasses), and computers (e.g., laptops). Home appliances may include TVs, refrigerators, and washing machines. IoT devices may include sensors and smart meters.

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

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

[0040] Wireless communication / connection (150a, 150b, 150c) can be established between wireless devices (100a to 100f) and / or between wireless devices (100a to 100f) and a base station (200) and / or between base stations (200). Here, the wireless communication / connection can be established through various RATs (e.g., 5G NR), such as uplink / downlink communication (150a), sidelink communication (150b) (or, D2D (Device-To-Device) communication), and base station-to-base station communication (150c) (e.g., relay, IAB (Integrated Access and Backhaul)). Through the wireless communication / connection (150a, 150b, 150c), the wireless devices (100a to 100f) and the base station (200) can transmit / receive wireless signals to / from each other. For example, wireless communication / connection (150a, 150b, 150c) can transmit / receive signals through various physical channels. To this end, based on various proposals of this specification, at least some of 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 resource allocation processes can be performed.

[0041] NR supports multiple numerologies, or subcarrier spacings (SCS), to support diverse 5G services. For example, an SCS of 15 kHz supports wide areas in traditional cellular bands; an SCS of 30 kHz / 60 kHz supports dense urban areas, lower latency, and wider carrier bandwidth; and an SCS of 60 kHz or higher supports bandwidths greater than 24.25 GHz to overcome phase noise.

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

[0043] Frequency Range DefinitionFrequency RangeSubcarrier SpacingFR1450MHz - 6000MHz15, 30, 60kHzFR224250MHz - 52600MHz60, 120, 240kHz

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

[0045] Frequency Range DefinitionFrequency RangeSubcarrier SpacingFR1410MHz - 7125MHz15, 30, 60kHzFR224250MHz - 52600MHz60, 120, 240kHz

[0046] Here, the wireless communication technology implemented in the wireless device of the present specification may include not only LTE, NR, and 6G, but also Narrowband IoT (NB-IoT) for low-power communication. For example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology and may be implemented with standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the above-described names. Additionally or alternatively, the wireless communication technology implemented in the wireless device of the present specification may perform communication based on LTE-M technology. For example, LTE-M technology may be an example of LPWAN technology and may be called by various names such as eMTC (enhanced MTC). For example, LTE-M technology can be implemented by at least one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (Non-Bandwidth Limited), 5) LTE-MTC, 6) LTE MTC, and / or 7) LTE M, and is not limited to the above-described names. Additionally or alternatively, the wireless communication technology implemented in the wireless device of the present specification can include at least one of ZigBee, Bluetooth, and / or LPWAN considering low-power communication, and is not limited to the above-described names. For example, ZigBee technology can create PANs (Personal Area Networks) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and can be called by various names.

[0047] Figure 2 illustrates an example of a wireless device to which the implementation of the present specification is applied.

[0048] In FIG. 2, the first wireless device (100) and / or the second wireless device (200) may be implemented in various forms depending on the use case / service. For example, {the first wireless device (100) and the second wireless device (200)} may correspond to at least one of {the wireless devices (100a to 100f) and the base station (200)}, {the wireless devices (100a to 100f) and the wireless devices (100a to 100f)}, and / or {the base station (200) and the base station (200)} of FIG. 1. The first wireless device (100) and / or the second wireless device (200) may be configured by various components, devices / parts, and / or modules.

[0049] 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).

[0050] The processing chip (101) may include at least one processor, such as a processor (102), and at least one memory, such as a memory (104). Additionally and / or alternatively, the memory (104) may be located external to the processing chip (101).

[0051] The processor (102) may control the memory (104) and / or the transceiver (106) and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts 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 via the transceiver (106). The processor (102) may receive a wireless signal including second information / signal via the transceiver (106) and store information obtained by processing the second information / signal in the memory (104).

[0052] A memory (104) may be operatively connected to the processor (102). The memory (104) may store various types of information and / or instructions. The memory (104) may store firmware and / or software code (105) that implements code, instructions and / or sets of instructions that, when executed by the processor (102), perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein. For example, the firmware and / or software code (105) may implement instructions that, when executed by the processor (102), perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein. For example, the firmware and / or software code (105) may control the processor (102) to perform one or more protocols. For example, the firmware and / or software code (105) may control the processor (102) to perform one or more air interface protocol layers.

[0053] Here, the processor (102) and memory (104) may be part of a communication modem / circuit / chip designed to implement a RAT (e.g., LTE or NR). A transceiver (106) may be connected to the processor (102) and may transmit and / or receive 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 an RF (Radio Frequency) unit. In the present specification, the first wireless device (100) may represent a communication modem / circuit / chip.

[0054] 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).

[0055] 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). Additionally and / or alternatively, the memory (204) may be located external to the processing chip (201).

[0056] The processor (202) may control the memory (204) and / or the transceiver (206) and may be configured to implement the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed herein. For example, 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 via the transceiver (206). The processor (202) may receive a wireless signal including fourth information / signal via the transceiver (206) and store information obtained by processing the fourth information / signal in the memory (204).

[0057] A memory (204) may be operatively connected to the processor (202). The memory (204) may store various types of information and / or instructions. The memory (204) may store firmware and / or software code (205) that implements code, instructions and / or sets of instructions that, when executed by the processor (202), perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein. For example, the firmware and / or software code (205) may implement instructions that, when executed by the processor (202), perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein. For example, the firmware and / or software code (205) may control the processor (202) to perform one or more protocols. For example, the firmware and / or software code (205) may control the processor (202) to perform one or more air interface protocol layers.

[0058] Here, the processor (202) and memory (204) may be part of a communication modem / circuit / chip designed to implement a RAT (e.g., LTE or NR). A transceiver (206) may be connected to the processor (202) and may 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. In the present specification, the second wireless device (200) may represent a communication modem / circuit / chip.

[0059] Hereinafter, hardware elements of the wireless device (100, 200) will be described in more detail. Although not limited thereto, one or more protocol layers may be implemented by one or more processors (102, 202). For example, one or more processors (102, 202) may implement one or more layers (e.g., functional layers such as a physical (PHY) layer, a Media Access Control (MAC) layer, a Radio Link Control (RLC) layer, a Packet Data Convergence Protocol (PDCP) layer, a Radio Resource Control (RRC) layer, and a Service Data Adaptation Protocol (SDAP) layer). One or more processors (102, 202) may generate one or more Protocol Data Units (PDUs), one or more Service Data Units (SDUs), messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed herein. One or more processors (102, 202) can generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data or information according to the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed herein and provide the signals to one or more transceivers (106, 206). One or more processors (102, 202) can receive signals (e.g., baseband signals) from one or more transceivers (106, 206) and obtain PDUs, SDUs, messages, control information, data or information according to the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed herein.

[0060] The one or more processors (102, 202) may be referred to as a controller, a microcontroller, a microprocessor, and / or a microcomputer. The one or more processors (102, 202) may be implemented by hardware, firmware, software, and / or a combination thereof. For example, one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), one or more Digital Signal Processing Devices (DSPDs), one or more Programmable Logic Devices (PLDs), and / or one or more Field Programmable Gate Arrays (FPGAs) may be included in the one or more processors (102, 202). For example, the one or more processors (102, 202) may be configured by a set of a communication control processor, an Application Processor (AP), an Electronic Control Unit (ECU), a Central Processing Unit (CPU), a Graphic Processing Unit (GPU), and a Memory Control Processor. One or more memories (104, 204) may be coupled to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, codes, instructions and / or commands. The one or more memories (104, 204) may be configured as random access memory (RAM), dynamic RAM (DRAM), read-only memory (ROM), erasable programmable ROM (EPROM), flash memory, volatile memory, nonvolatile memory, hard drive, register, cache memory, computer readable storage media and / or combinations thereof.One or more memories (104, 204) may be located internally and / or externally to one or more processors (102, 202). Additionally, one or more memories (104, 204) may be connected to one or more processors (102, 202) via various technologies, such as wired or wireless connections.

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

[0062] One or more transceivers (106, 206) may be coupled 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) may be configured to transmit and receive user data, control information, wireless signals / channels, etc., as described in the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed herein via one or more antennas (108, 208). In the present disclosure, one or more antennas (108, 208) may be multiple physical antennas or multiple logical antennas (e.g., antenna ports).

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

[0064] Although not illustrated in FIG. 2, the wireless device (100, 200) may further include additional components. The additional components (140) may be configured in various ways depending on the type of the wireless device (100, 200). For example, the 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 driving device, and a computing device. The additional components (140) may be connected to one or more processors (102, 202) via various technologies, such as a wired or wireless connection.

[0065] In the implementation of this specification, a UE can operate as a transmitter in the uplink and as a receiver in the downlink. In the implementation of this specification, a base station can operate as a receiver in the UL and as a transmitter in the DL. For the sake of convenience of description, it is mainly assumed below that the first wireless device (100) operates as a UE and the second wireless device (200) operates as a base station. For example, a processor (102) connected to, mounted on, or released in the first wireless device (100) can be configured to perform UE operations according to the implementation of this specification or to control a transceiver (106) to perform UE operations according to the implementation of this specification. A processor (202) connected to, mounted on, or released in the second wireless device (200) can be configured to perform base station operations according to the implementation of this specification or to control a transceiver (206) to perform base station operations according to the implementation of this specification.

[0066] In this specification, a base station may be referred to as a Node B, an eNode B (eNB), or a gNB.

[0067] Figure 3 shows an example of a UE to which the implementation of this specification is applied.

[0068] Referring to FIG. 3, the UE (100) can correspond to the first wireless device (100) of FIG. 2.

[0069] The UE (100) includes a processor (102), memory (104), a transceiver (106), one or more antennas (108), a power management module (141), a battery (142), a display (143), a keypad (144), a SIM (Subscriber Identification Module) card (145), a speaker (146), and a microphone (147).

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

[0071] 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. When the implementation is implemented in software, the techniques described herein may be implemented using modules (e.g., procedures, functions, etc.) that perform the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed herein. The modules may be stored in memory (104) and executed by the processor (102). Memory (104) may be implemented within the processor (102) or external to the processor (102), in which case it may be communicatively coupled to the processor (102) via various methods known in the art.

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

[0073] The power management module (141) manages the power of the processor (102) and / or the transceiver (106). The battery (142) supplies power to the power management module (141).

[0074] The display (143) outputs the results processed by the processor (102). The keypad (144) receives input to be used by the processor (102). The keypad (144) can be displayed on the display (143).

[0075] A SIM card (145) is an integrated circuit that securely stores an International Mobile Subscriber Identity (IMSI) and associated keys, and is used to identify and authenticate subscribers in mobile devices such as mobile phones and computers. Additionally, many SIM cards can store contact information.

[0076] The speaker (146) outputs sound-related results processed by the processor (102). The microphone (147) receives sound-related input to be used by the processor (102).

[0077] Figure 4 shows an example of a 5G system structure to which the implementation of this specification is applied.

[0078] The 5G system (5GS; 5G system) structure consists of the following network functions (NF; Network Function).

[0079] - AUSF (Authentication Server Function)

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

[0081] - DN (Data Network), for example, operator services, Internet access, or third-party services.

[0082] - USDF (Unstructured Data Storage Function)

[0083] - NEF (Network Exposure Function)

[0084] - I-NEF (Intermediate NEF)

[0085] - NRF (Network Repository Function)

[0086] - NSSF (Network Slice Selection Function)

[0087] - PCF (Policy Control Function)

[0088] - SMF (Session Management Function)

[0089] - UDM (Unified Data Management)

[0090] - UDR (Unified Data Repository)

[0091] - UPF (User Plane Function)

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

[0093] - AF (Application Function)

[0094] - UE (User Equipment)

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

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

[0097] - NWDAF (Network Data Analytics Function)

[0098] - CHF (CHarging Function)

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

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

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

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

[0103] Figure 4 illustrates the 5G system architecture for a non-roaming case using a reference point representation showing how various network functions interact with each other.

[0104] For clarity of the point-to-point diagram in Figure 4, UDSF, NEF, and NRF are not illustrated. However, all network functions shown can interact with UDSF, UDR, NEF, and NRF as needed.

[0105] For clarity, the connection between UDR and other NFs (e.g., PCF) is not shown in Fig. 4. For clarity, the connection between NWDAF and other NFs (e.g., PCF) is not shown in Fig. 4.

[0106] The 5G system architecture includes the following benchmarks:

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

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

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

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

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

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

[0113] The following benchmarks illustrate the interactions that exist between NF services in NF.

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

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

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

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

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

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

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

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

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

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

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

[0125] In some cases, two NFs may need to be interconnected to serve a UE.

[0126] Describes the PDU session establishment procedure. See Section 4.3.2 of 3GPP TS 23.502 V16.3.0 (2019-12).

[0127] Figures 5 and 6 illustrate examples of a PDU session establishment procedure to which the implementation of the present specification applies.

[0128] Establishing a PDU session may involve:

[0129] - UE-initiated PDU session establishment procedure

[0130] - PDU session handover between 3GPP and non-3GPP initiated by UE

[0131] - PDU session handover from UE-initiated EPS to 5GS.

[0132] - Network-triggered PDU session establishment procedure

[0133] A PDU session may be associated with either (a) a single connection type at a given time, i.e., either a 3GPP connection or a non-3GPP connection, or (b) multiple connection types simultaneously, i.e., one 3GPP connection and one non-3GPP connection. A PDU session associated with multiple connection types is called a multi-access (MA) PDU session and may be requested by an access traffic steering, switching, splitting (ATSS) capable UE.

[0134] Figures 5 and 6 specify a procedure for establishing a PDU session associated with a single connection type at a given time.

[0135] In the procedures shown in Figures 5 and 6, it is assumed that the UE is already registered with the AMF, so unless the UE is emergency registered, the AMF has already retrieved the user subscription data from the UDM.

[0136] First, the procedure of Fig. 5 is explained.

[0137] (1) Step 1: To establish a new PDU session, the UE generates a new PDU session ID.

[0138] The UE initiates the PDU session establishment procedure requested by the UE by sending an NAS message containing a PDU session establishment request message within the N1 SM container. The PDU session establishment request message includes the PDU session ID, the requested PDU session type, the requested session and service continuity (SSC) mode, 5G SM capabilities, Protocol Configuration Options (PCO), the SM PDU DN Request Container, and the UE Integrity Protection Maximum Data Rate.

[0139] If the PDU session establishment is a request to establish a new PDU session, the request type is "Initial Request." If the request refers to an existing PDU session switching 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." If the PDU session establishment is a request to establish a PDU session for emergency services, the request type is "Emergency Request." If the request refers to an existing PDU session for emergency services switching 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."

[0140] The UE includes the S-NSSAI from the allowed NSSAI of the current connection type. If a mapping of allowed NSSAIs (Mapping of Allowed NSSAIs) is provided to the UE, the UE provides both the S-NSSAI of the VPLMN (visited VPLMN) from the allowed NSSAIs and the corresponding S-NSSAI of the HPLMN from the mapping of allowed NSSAIs.

[0141] (2) Step 2: AMF selects an SMF. If the request type indicates "Initial Request" or the request is due to a handover from an EPS or other non-3GPP connection provided by an AMF, AMF stores the connection type of the PDU session as well as the association of S-NSSAI(s), data network name (DNN), PDU session ID, and SMF ID.

[0142] If the request type is "Initial Request" and the message also contains a previous PDU session ID representing an existing PDU session, AMF selects an SMF and stores the association of the new PDU session ID, S-NSAI(s), and the selected SMF ID.

[0143] If the request type indicates "Existing PDU Session," AMF selects an SMF based on the SMF-ID received from the UDM. AMF updates the stored connection type for the PDU session.

[0144] If the request type indicates "Existing PDU Session", which refers to an existing PDU session moving between a 3GPP connection and a non-3GPP connection, and if the serving PLMN S-NSSAI of the PDU session is in the allowed NSSAI of the target connection type, the PDU session establishment procedure may be performed in the following cases:

[0145] - When the SMF ID and AMF corresponding to the PDU session ID belong to the same PLMN;

[0146] - If the SMF ID corresponding to the PDU session ID belongs to HPLMN;

[0147] Otherwise, AMF rejects the PDU session establishment request with an appropriate rejection cause.

[0148] AMF rejects requests from emergency-registered UEs whose request type does not indicate "Emergency Request" or "Existing Emergency PDU Session".

[0149] (3) 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 invokes the Create SM Context request procedure (e.g., Nsmf_PDUSession_CreateSMContext Request). If the AMF is already associated with an SMF for the PDU session ID provided by the UE (e.g., when the request type indicates "Existing PDU Session"), the AMF invokes the Update SM Context request procedure (e.g., Nsmf_PDUSession_UpdateSMContext Request).

[0150] The AMF transmits the S-NSSAI of the serving PLMN to the SMF from the allowed NSSAI. For a roaming scenario of local breakout (LBO), the AMF also transmits the corresponding S-NSSAI of the HPLMN to the SMF from the mapping of the allowed NSSAI.

[0151] The AMF ID is the UE's GUAMI, which uniquely identifies the AMF serving the UE. The AMF passes the PDU session ID along with the N1 SM container containing the PDU session establishment request message received from the UE. The GPSI (generic public subscription identifier) ​​is included if available to the AMF.

[0152] If a UE in limited service state is registered for emergency services without providing SUPI, the 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 the SUPI is not authenticated. If the SMF does not receive a SUPI for the UE or if the AMF indicates that the SUPI is not authenticated, the UE is considered unauthenticated.

[0153] AMF can include a PCF ID in Nsmf_PDUSession_CreateSMContext. This PCFID identifies the home PCF (H-PCF) in non-roaming cases and the visited PCF (V-PCF) in LBO roaming cases.

[0154] (4) Step 4: If the session management subscription data for the S-NSSAI of the corresponding SUPI, DNN, or HPLMN is not available, the SMF can retrieve the session management subscription data from the UDM and be notified when the subscription data is modified.

[0155] (5) Step 5: 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 AMF according to the request received in step 3.

[0156] If SMF receives the Nsmf_PDUSession_CreateSMContext Request in step 3 and can process the PDU session establishment request, SMF creates an SM context and responds to AMF by providing the SM context ID.

[0157] If the SMF decides not to accept the PDU session establishment, the SMF rejects the UE request by sending a NAS SM signal including the relevant SM rejection cause 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, aborting the PDU session establishment procedure.

[0158] (6) Step 6: Optional secondary authentication / authorization may be performed.

[0159] (7a) Step 7a: When dynamic policy and charging control (PCC) is used in a PDU session, the SMF can perform PCF selection.

[0160] (7b) Step 7b: SMF performs the SM policy association establishment procedure to establish a PCF and SM policy association, and obtains the basic PCC rules for the PDU session.

[0161] (8) Step 8: SMF selects one or more UPFs.

[0162] (9) Step 9: The SMF may provide information about the satisfied policy control request trigger conditions by performing the SM policy association modification procedure initiated by the SMF.

[0163] (10) Step 10: If the request type indicates an "Initial Request," the SMF may initiate the N4 Session Establishment procedure with the selected UPF. Otherwise, the SMF may initiate the N4 Session Modification procedure with the selected UPF.

[0164] In step 10a, the SMF can send an N4 session establishment / modification request to the UPF, providing packet detection, enforcement, and reporting rules to be installed in the UPF for the PDU session. In step 10b, the UPF can confirm by sending an N4 session establishment / modification response.

[0165] (11) Step 11: SMF sends an N1N2 message transfer message (e.g. Namf_Communication_N1N2 Message Transfer) to AMF.

[0166] The N1N2 Message Forwarding message may contain N2 SM information. The N2 SM information carries the following information that the AMF will forward to the (R)AN:

[0167] - CN Tunnel Info: Corresponds to the core network address of the N3 tunnel corresponding to the PDU session;

[0168] - QFI (QoS flow ID) corresponding to one or more QoS (quality of service) profiles;

[0169] - PDU Session ID: Indicates to the UE the association between RAN resources and a PDU session for the UE;

[0170] - S-NSSAI with value for serving PLMN (i.e. HPLMN S-NSSAI, or VPLMN S-NSSAI in case of LBO roaming);

[0171] - User plane security enforcement information determined by SMF;

[0172] - UE integrity protection maximum data rate received in PDU session establishment request message: if integrity protection is indicated as "Preferred" or "Required" in the user plane security enforcement information.

[0173] - RSN (redundancy sequence number) parameter

[0174] The N1N2 message transfer message may include an N1 SM container. The N1 SM container includes a PDU Session Establishment Accept message that the AMF will provide to the UE. The PDU Session Establishment Accept message includes the S-NSSAI from the allowed NSSAI. For the LBO roaming scenario, 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.

[0175] Multiple QoS rules, QoS flow levels, and QoS parameters may be included in the PDU session establishment accept message and N2 SM information within the N1 SM container, if required, for QoS flows associated with QoS rules and QoS profiles.

[0176] If the PDU session establishment fails between steps 5 and 11, the N1N2 message forwarding message contains an N1 SM container containing a PDU session establishment rejection message, but does not contain N2 SM information. The (R)AN sends an NAS message containing a PDU session establishment rejection message to the UE. In this case, steps 12-17 below are omitted.

[0177] (12) Step 12: AMF sends a NAS message containing the PDU Session ID and PDU Session Establishment Accept message destined for the UE and the N2 SM information received from SMF to (R)AN within an N2 PDU Session Request message.

[0178] (13) Step 13: The (R)AN may perform AN-specific signaling exchanges with the UE related to the information received from the SMF. For example, in the case of the NG-RAN, the UE may perform an RRC connection reconfiguration with the UE to set up the necessary NG-RAN resources related to the QoS rules for the PDU session request received in step 12.

[0179] (R)AN forwards the NAS message (PDU Session ID, N1 SM container (PDU Session Establishment Accept message)) received in step 12 to the UE. (R)AN provides the NAS message to the UE only if the AN-specific signaling exchange with the UE includes (R)AN resource additions related to the received N2 command.

[0180] If N2 SM information is not included in step 11, steps 14-16b and 17 below are omitted.

[0181] Now, the procedure of Fig. 6 following the procedure of Fig. 5 is described.

[0182] (14) Step 14: (R)AN sends 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.

[0183] (15) Step 15: AMF sends an update SM context request message (e.g., Nsmf_PDUSession_UpdateSMContext Request) to SMF. AMF forwards the N2 SM information received from (R)AN to SMF.

[0184] (16a) Step S16a: SMF initiates the N4 session modification procedure with UPF. SMF provides AN tunnel information and corresponding forwarding rules to UPF.

[0185] (16b) Step S16b: UPF provides an N4 session modification response to SMF.

[0186] After this step, the UPF can forward any DL packets that may have been buffered for this PDU session to the UE.

[0187] (16c) 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.

[0188] (17) Step 17: SMF sends an update SM context response message (e.g., Nsmf_PDUSession_UpdateSMContext Response) to AMF.

[0189] After this step, AMF forwards the relevant events to which SMF subscribes.

[0190] (18) Step 18: At any time during the procedure after Step 5, if the PDU session establishment is not successful, the SMF can notify the AMF by calling Nsmf_PDUSession_SMContextStatusNotify (release). The SMF can also release the created N4 session, the PDU session address (e.g., IP address) if assigned, and possibly the association with the PCF. In this case, Step 19 below is omitted.

[0191] (19) Step 19: For PDU session type IPv6 or IPv4v6, SMF may generate and send an IPv6 Router Advertisement to the UE.

[0192] (20) Step 20: SMF can perform SM policy association modification initiated by SMF.

[0193] (21) Step 21: If the PDU session establishment fails after step 4, the SMF may unsubscribe for modification of session management subscription data if the SMF no longer processes the UE's PDU session.

[0194] Describes eXtended Reality (XR) and interactive media services.

[0195] High data rate low latency services, eXtended Reality (XR), and interactive media services can be supported.

[0196] This document outlines examples of 5GS capabilities to support XR services (AR / VR applications) and interactive media services that require high data rates and low latency, such as cloud gaming and tactile / multimodal communication services, according to the service requirements documented in 3GPP TS 22.261 V 19.5.0. Additional enhancements for these interactive media services include:

[0197] - 5GS can support QoS policy control for multimodal traffic.

[0198] - 5GS can support network information exposure based on ECN marking for L4S (see 5GS Exposure API).

[0199] - 5GS can support PDU set-based QoS processing, including PDU set identification and marking.

[0200] - 5GS can verify that UL and DL packets together meet the requested round-trip delay, and update the delay for UL and DL considering the QoS monitoring results.

[0201] - 5GS can perform per-flow Packet Delay Variation (PDV) monitoring and policy control according to AF provisioning requirements.

[0202] - 5GC can provide traffic assistance information to NG-RAN to enable connected mode DRX power saving.

[0203] Describes examples of policy control improvements to support multimodal services.

[0204] A multimodal service is a communication service composed of multiple data flows that are interrelated and subject to application coordination. Data flows can carry various types of data (e.g., audio, video, location, haptic data) and can originate from different sources (e.g., a single UE, a single device, multiple devices connected to a single UE, or multiple UEs).

[0205] For a single UE, these data flows are closely related and require strong application coordination for proper execution of multimodal applications, so all data flows can be transmitted in a single PDU session.

[0206] The Nnef_AFsessionWithQoS service allows AF to simultaneously provide multi-modal service IDs, service requirements, and QoS monitoring requirements for each data flow belonging to a multi-modal service:

[0207] - A multimodal service ID can explicitly indicate that a data flow is associated with a multimodal service. PCF can use this information to derive the appropriate PCC rules and apply appropriate QoS policies to data flows that are part of a specific multimodal application.

[0208] - AF can provide PCF with QoS monitoring requirements for data flows associated with multimodal services. PCF can then create an approved QoS monitoring policy for each data flow.

[0209] In addition to the features provided when a data flow is associated with a single UE, the features provided when a data flow is associated with more than one UE are as follows:

[0210] - Each UE involved can select the same DNN / S-NSSAI combination for a multimodal service. The URSP rule evaluation framework can be used to ensure that the same DNN / S-NSSAI is selected.

[0211] - The AF can use the same multimodal service ID for all associated UEs in its interactions with the PCF for a multimodal service. The PCF can consider this information when independently processing each AF request (e.g., applying specific QoS policies). Data flows contribute to the service experience, but are still valid independently because they are transmitted through separate PDU sessions with the associated UEs.

[0212] - When multiple PCFs are involved, a PCF can make policy decisions based on input provided by the AF. Policy decisions can be made individually by each PCF on a per-PDU session basis.

[0213] For XR and interactive media services, ECN marking for L4S to expose congestion information may be supported.

[0214] L4S (Low Latency, Low Loss and Scalable Throughput) is described in IETF RFC 9330, IETF RFC 9331, and IETF RFC 9332. L4S exposes congestion information by marking the ECN bit in the IP header of user IP packets between the UE and the application server to trigger application layer rate adaptation.

[0215] For XR and interactive media services, 5G systems may support ECN marking for L4S. ECN marking for L4S is enabled per QoS flow in the uplink and / or downlink directions and can be used for GBR and non-GBR QoS flows.

[0216] For ECN marking for L4S by PSA UPF, NG-RAN is instructed to perform congestion information monitoring and report congestion information (i.e., the percentage of packets that UPF uses for ECN marking for L4S) to PSA UPF via GTP-U header extension. Accordingly, PSA UPF can mark UL and / or DL ​​direction packets of QoS flows.

[0217] For example, if the PSA UPF or NG-RAN services are changed due to a NG-RAN-to-RAN handover or a PSA UPF relocation, the target NG-RAN and the target PSA UPF will continue to perform ECN marking for L4S for QoS flows if supported. However, if it is not available (i.e., if ECN marking for L4S is not supported by both the target NG-RAN and the target PSA UPF), the AF may inform the AF that it can no longer perform ECN marking for L4S if it had previously enabled ECN marking for L4S for QoS flows as requested by the AF. If ECN marking for L4S becomes supported again on the target NG-RAN or the target PSA UPF, the AF may inform the AF that it can perform ECN marking for L4S again if it had previously enabled ECN marking for L4S for QoS flows as requested by the AF.

[0218] For XR and interactive media services, PDU set-based handling may be supported.

[0219] A PDU set may consist of one or more PDUs carrying an application layer payload, such as a video frame or a video slice. PDU set-based QoS processing by the NG-RAN may be determined by the PDU set QoS parameters in the QoS profile of the QoS flow and the PDU set information provided by the PSA UPF via the N3 / N9 interface. PDU set-based processing may be applied to GBR and non-GBR QoS flows. The AF may provide PDU set-related support information for dynamic PCC control.

[0220] For XR and interactive media services, 5GS packet delay variation monitoring and reporting may be supported.

[0221] 5GS packet delay variation can be the variation in packet delay measured between the UE and the PSA UPF. The AF can transmit packet delay variation monitoring requirements along with packet delay measurement requirements to 5GS.

[0222] When there is an AF request for packet delay variation monitoring along with packet delay monitoring, the PCF can trigger a QoS monitoring procedure and obtain UL, DL, or RT QoS monitoring results from the SMF. After receiving the QoS monitoring results, the PCF can derive the 5GS packet delay variation based on the QoS monitoring results, and then report both the packet delay measurement value and the packet delay variation to the AF / NEF.

[0223] QoS monitoring is used to obtain QoS parameter measurements for individual QoS flows. The PCF determines the required measurements based on input from the AF and can activate measurements by generating an approved QoS monitoring policy for the PCC rules.

[0224] For XR and interactive media services, UE power saving management may be supported.

[0225] To configure the UE power saving management scheme for connected mode DRX, the CN can provide the following traffic assistance information to the NG-RAN:

[0226] - UL and / or DL ​​periodicity;

[0227] - N6 jitter information related to DL periodicity;

[0228] - Data burst end indication.

[0229] UL and / or DL ​​periodicity and N6 jitter information associated with DL periodicity may be provided from CN to NG RAN via TSCAI.

[0230] In relation to XR and interactive media services, exposure of network information may be supported.

[0231] To support real-time media codec / traffic adaptation to network conditions, AF can request 5GS network information exposure.

[0232] The AF may provide subscriptions to the following information: UL and / or DL ​​congestion level information, UL and / or DL ​​packet delay, round trip delay for one or two service data flows, UL and / or DL ​​data rates of the target service data flows, or QNC of GBR QoS flows in AF sessions using the required QoS.

[0233] PCF can create PCC rules that include QoS monitoring for the above network information.

[0234] AF can also provide averaging window values ​​using AF sessions with required QoS.

[0235] For XR and interactive media services, UL / DL policy control based on round-trip latency requirements may be supported.

[0236] The AF can provide a round-trip (RT) delay indication along with the one-way delay requirement between the UE and the PSA UPF, expressed as a QoS reference or individual QoS parameter. The RT delay indication indicates that the RT delay requirement of the service data flow, i.e., twice the one-way delay requirement between the UE and the PSA UPF, must be met.

[0237] Based on the RT latency requirement received from the AF or configured locally in the PCF, the PCF approves the AF request and splits the RT latency requirement into two PDBs, each consisting of two PCC rules, for use by the UL QoS flow and the DL QoS flow, respectively, used to carry the UL and DL traffic of the service. The two PDBs can be different, but their sum must not exceed the RT latency requirement.

[0238] Depending on the RT latency requirements, the PCF can create UL and DL QoS monitoring policies in the PCC rules, each associated with two interrelated QoS flows, to enable RT latency tracking. The uplink and downlink delays of the two QoS flows can be tracked independently by the PCF.

[0239] Once QoS monitoring results are reported to the PCF, the PCF can derive and track RT latency by combining QoS monitoring reports for UL and DL packet delays. Based on the QoS monitoring results, the PCF can adjust the PDB of one or two PCC rules to better suit the new situation, taking into account RT latency requirements using the SM policy association modification procedure.

[0240] If the UL and DL traffic of a service have different QoS requirements (e.g., different one-way delays), the AF can provide the QoS requirements via RT latency indications to the AF session, along with the QoS requests required for UL and DL flow descriptions. The PCF can then use the RT latency indicators to identify the UL and DL service data flows for RT latency control. In this case, the RT latency requirement of the service can be described as the sum of the UL and DL latency requirements.

[0241] In relation to XR and interactive media services, multimodal service provision may be supported.

[0242] Enablers can be applied to support interactive media services that require high data rates and low-latency communication, such as cloud gaming, AR / VR / XR services, and tactile / multimodal communication services.

[0243] To provide multimodal services, the AF may request multiple data flows for a single UE or multiple UEs via multiple PDU sessions and separate requests per PDU session to the NEF to establish specific QoS requirements. If the AF provides specific information about the multimodal service, the following additional attributes may be supported:

[0244] - Multimodal Service ID: An identifier representing a multimodal communication service. Data flows belonging to the same multimodal service can share the same multimodal service ID.

[0245] To provide specific information about the data flow of a multimodal service, AF supports the following multimodal service requirements, which consist of existing properties that AF can provide multiple times, once per data flow:

[0246] - QoS monitoring requirements for each data flow.

[0247] - QoS information and service requirements for each data flow are structured as follows: Flow description information and QoS parameters / QoS reference for the data flow.

[0248] A request to the PCF may include a multimodal service ID and service requirements for each data flow belonging to the multimodal service. The PCF determines whether the request from the NEF or AF is authorized, derives the required QoS parameters based on the provided information, and provides the SMF with a PCC rule containing updated policy control information for the affected PDU session.

[0249] AF can provide QoS monitoring requirements for each data flow associated with the same multimodal service ID. When PCF receives QoS monitoring requirements from AF, PCF can create a QoS monitoring policy for the PCC rule corresponding to the data flow.

[0250] If PCF receives an additional AF request with the same multimodal service ID and PCF approval fails, PCF can reject the AF. Applications can decide how to handle data flows that already have approved AF requests with the same multimodal service ID (e.g., stop or adjust the AF request).

[0251] For XR and interactive media services, PDU set QoS handling may be supported.

[0252] The PCF can generate PDU set control information based on local configuration or information received from the AF. The PCF can include the UL and / or DL ​​protocol descriptions received from the AF and the PDU set control information in the PCC rules. The PDU set control information can include PDU set QoS parameters. Based on the received PCC rules or pre-configured PCC rules, the SMF can provide the PDU set QoS parameters to the NG-RAN. If the PCC rules include a protocol description, this protocol description can be used to identify the PDU set.

[0253] When an AF requests that a data session for a UE be set to a specific QoS, the AF can describe its requirements for PDU set QoS handling and protocol description by providing individual QoS parameters: Requested PDU set delay budget (UL and / or DL), Requested PDU set error rate (UL and / or DL), and Requested PDU set aggregate handling information (UL and / or DL).

[0254] For XR and interactive media services, data burst-based handling may be supported.

[0255] Based on the DL protocol description provided by AF and / or local settings, PCF may generate a data burst end indication and provide it to SMF along with the DL protocol description of PCC rules.

[0256] In relation to XR and interactive media services, traffic parameter information and traffic parameter measurement may be supported.

[0257] Traffic parameter information and traffic parameter measurements can be applied to power saving.

[0258] PCF can generate PCC rules that include traffic parameter information and traffic parameter measurements based on periodicity information provided by AF.

[0259] Traffic parameter information may include UL and / or DL ​​periodicity, and traffic parameter measurement may indicate traffic parameters to be measured and reporting conditions.

[0260] Discussions are underway to improve Quality of Service (QoS) management based on Protocol Data Unit (PDU) sets. For example, QoS management could be applied to eXtended Reality and Media services (XRM). XRM includes eXtended Reality (XR) services.

[0261] This paper discusses issues related to QoS management based on PDU sets. Issues to improve PDU set-based QoS handling, considering both the control plane and user plane perspectives, can be discussed. This issue covers the following:

[0262] - Whether, what, and how to improve PDU set-based processing provided by AF / AS (e.g., new standardized 5QI, alternative QoS profile enhancements, Forward Error Correction (FEC), etc.) and PDU set information (e.g., including control plane and / or user plane information).

[0263] Conventional base stations can determine and perform packet discarding based on PDU sets depending on congestion conditions. In relation to the above issue, solutions that additionally support active packet discarding for FEC packets / streams based on PDU set content ratios are being discussed. However, a method is needed to distinguish between packet discarding based on PDU sets due to RAN internal congestion in conventional technology and packet discarding due to active discarding support in 5GS.

[0264] For example, a base station can perform active packet discarding depending on congestion conditions. However, according to conventional technology, entities other than the base station (e.g., terminals, application servers, etc.) cannot detect whether active packet discarding is taking place, resulting in inefficient communication.

[0265] For FEC data discarded by 5GS based on active discarding, the terminal perceives packet loss as data loss. This causes the terminal to request more FEC data from the application server.

[0266] According to various examples of the disclosure of this specification, by informing the application layer of information related to active discarding intentionally performed by 5GS / RAN, the network can effectively support the following controls:

[0267] - It can prevent the FEC request rate from the terminal application from increasing and the bandwidth from increasing.

[0268] - It can prevent additional delay caused by increased FEC data.

[0269] - It can prevent incorrect measurements of packet loss rate and network capacity at the application layer.

[0270] Hereinafter, regarding the procedures and / or messages described in the various examples of the disclosure of this specification, conventional procedures / messages may be used, conventional procedures / messages may be extended and used, or new procedures / messages may be defined and used. Depending on the purpose and needs of the disclosure of this specification, the procedures or operations described in the first to fourth examples of the disclosure of this specification below may be performed or used in combination or complementary manner.

[0271] In this specification, the event name / ID or report / notification called "FEC Active Discarding" or "Active Discarding" may be defined by various names such as Intentional Drop, Non-congestion based Drop, etc.

[0272] Describes an example where content ratio awareness of a PDU set is supported in RAN.

[0273] For example, the principles underpinning the use of Application Layer Forward Error Correction (AL-FEC) by XR applications are discussed:

[0274] - Applications transmit Application Data Units (ADUs), which consist of source symbols containing, for example, video frames, and recovery symbols.

[0275] - If the code used is maximum distance separable (MDS) (e.g. RaptorQ or Reed-Solomon codes), the source and recovery symbols are distributed across N packets so that the receiver receives K (K) of the N packets. <N)를 수신할 경우 실제 콘텐츠(예: 비디오 프레임)를 재구성할 수 있도록 한다.

[0276] In other words, from the receiver's perspective, receiving K packets of an ADU is sufficient to reconstruct the actual content. This also means that once the receiver successfully receives K of the N packets that make up an ADU, it is of no use transmitting the remaining NK ADU packets to the receiver, as the receiver can already reconstruct the original content based on the first K packets.

[0277] For example, the overhead of AL-FEC schemes ranges from 10% to 50%, with a typical value of 30%. For AL-FEC-based XR content over 5G, this presents a significant optimization opportunity: if the NG-RAN successfully delivers the first K PDUs of a PDU set to the UE, the remaining PDUs can be discarded by the NG-RAN as they do not provide additional value to the UE. (Hereinafter, these PDUs are referred to as discarded PDUs.) Given that the typical overhead of AL-FEC schemes is 30%, this can result in significant air interface resource savings.

[0278] Therefore, the NG-RAN can recognize the PDU ratio of the PDU set required by the UE to reconstruct the original content, and the NG-RAN can discard the remaining useless PDUs.

[0279] This approach can work regardless of whether AL-FEC encoded traffic is encrypted.

[0280] Another important aspect is the application's perspective. If the NG-RAN discards obsolete PDUs, the application can observe that the UE continues to receive only enough PDUs to reconstruct the original content.

[0281] It is important to ensure that applications do not increase the amount of AL-FEC information based on these observations. If the network supports active discarding of obsolete PDUs, it can notify the network of data discarding. For example, the AF can subscribe to events related to the discarding of obsolete PDUs at the application layer. In this case, if the RAN distinguishes between dropped FEC packets and packets dropped due to congestion, it can notify the application server. Based on this, the application can avoid erroneous packet loss rate measurements without increasing the AL-FEC information rate, as long as sufficient PDUs are received to reconstruct the original content.

[0282] For reference, in the disclosure of this specification, the content ratio may be the PDU ratio of a set of PDUs required by the UE to reconstruct the original content.

[0283] For reference, in the disclosure of this specification, a discarded PDU may be any PDU in a set of PDUs that has not yet been transmitted to the UE, in a situation where sufficient PDUs have already been successfully transmitted to the UE according to the content ratio.

[0284] When requesting or updating QoS for a QoS flow, the AF may provide the PCF / NEF with the content ratio for the flow along with the PDU set QoS parameters. The AF may provide either the PSIHI or the content ratio for the flow. The AF may also subscribe to the PCF to receive additional indications of support / non-support for PDU set content ratio awareness and discard information for obsolete PDUs.

[0285] When PCF receives content rate and subscription information from AF, PCF may include the content rate and subscription information in the PCC rules provided to SMF. Note that in the disclosure of this specification, the terms "subscription" and "subscription" may be used interchangeably.

[0286] SMF can provide content rate and subscription information to NG-RAN when setting / modifying QoS flows.

[0287] If the NG-RAN supports PDU setup content rate awareness and receives content rate information along with subscription information related to discarding unnecessary PDUs for a QoS flow, the NG-RAN can discard unnecessary PDUs of this flow in case of congestion and send a notification to the AF.

[0288] Describes examples of handling supported / unsupported NG-RAN nodes.

[0289] If the NG-RAN node supports PDU Set Content Rate Awareness, the following explanation may apply. For example, if the NG-RAN node receives content rate information from the SMF, the NG-RAN node may respond by informing the SMF that it supports PDU Set Content Rate Awareness. As part of Xn and N2 handovers, the target NG-RAN node may inform the SMF that the NG-RAN supports PDU Set Content Rate Awareness.

[0290] When a UE moves from a RAN node that does not support PDU set content rate awareness (e.g., an NG-RAN or E-UTRAN node) to an NG-RAN node that does support PDU set content rate awareness (hereinafter referred to as a non-supporting node), the SMF may provide content rate information (if available) to the NG-RAN.

[0291] When the SMF receives content rate information from the PCF and the NG-RAN indicates that it supports PDU set content rate awareness, the SMF notifies the PCF, which then notifies the AF that PDU set content rate awareness is supported by the NG-RAN. The AF can then subscribe to events related to discarding unnecessary PDUs.

[0292] When a UE moves from a supported node to an unsupported node, the SMF notifies the PCF, which then notifies the AF that PDU set content ratio awareness is not supported in the NG-RAN.

[0293] For reference, the procedure according to the prior art may be reused or extended to apply content ratio information and information related to PDU set content ratio recognition.

[0294] AF provides content ratios and can subscribe to PCF for events related to disposal.

[0295] The AF can receive support / non-support indications for PDU set content ratio recognition from the SMF and can receive notifications from the NG-RAN to discard obsolete PDUs.

[0296] PCF may receive content rate and subscription requests from AF and provide content rate and subscription information to SMF as part of PCC rules.

[0297] PCF can receive support / non-support indication for PDU set content ratio recognition from SMF and inform AF accordingly.

[0298] The SMF can receive content rate and subscription information from the PCF and provide the content rate and subscription information to the RAN.

[0299] SMF can provide PCF with an indication of support / non-support for PDU set content ratio awareness.

[0300] - NG-RAN can support receiving content ratio information for QoS flows and, based on notifications about content ratio and AF, can support discarding unnecessary PDUs for QoS flows.

[0301] - NG-RAN may transmit information to SMF related to support of PDU set content ratio awareness during QoS flow establishment and during Xn and N2 handover.

[0302] 1. First example of disclosure of this specification

[0303] Referring to FIGS. 7a and 7b, a first example of the disclosure of the present specification is described.

[0304] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals, messages, and fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0305] FIG. 7a and FIG. 7b illustrate a first example of a procedure according to one embodiment of the disclosure of the present specification.

[0306] The examples in Figures 7a and 7b illustrate an example of a procedure for subscribing to events related to active discarding for FEC. For example, an Application Function (AF) can subscribe to events related to active discarding performed by the NG-RAN.

[0307] (1) AF can send a subscription request message to NEF. For example, AF can subscribe to notification of active discarding events.

[0308] For example, an AF can subscribe to 5GS for Active Discarding event notifications for FEC data from a base station. Subscription to such events can be requested during the AF session creation process between the AF and PCF, or through a separate subscription service process after the AF session is created. The AF can also subscribe to direct notifications for such requests, bypassing the network control node (e.g., SMF, PCF, etc.).

[0309] Additionally, AF can transmit conditional information for event notifications from NG-RAN. For example, it can subscribe to notifications only when a certain drop rate is exceeded.

[0310] As another way for AF to subscribe to active discarding event notifications for FEC data, the existing AF session with required QoS service procedure can be extended. For example, AF can request event notification subscriptions with information related to active discarding requirements via the Nnef_AFsessionWithQoS_Create / Update service.

[0311] For example, the FEC active discarding event may be applied to the List of events for monitoring capability in TS 23.502 V18.1.0 Table 4.15.3.1-1. For example, the event name may be FEC active discarding. The detection criteria may be that this event indicates the status of active discarding of FEC data performed by the RAN. The NF that detects the event may be SMF, UPF, etc.

[0312] (2) (2-1) NEF can perform an authentication procedure. (2-2) NEF can send a subscription request message to PCF. The subscription request message includes an Event ID, and the Event ID can be actively discarded.

[0313] For example, according to the conventional procedure, after the NEF performs the authentication procedure for the AF request, the subscription information, indication of direct event notification, reporting threshold, etc. in the AF request can be transmitted to the PCF.

[0314] (3) (3-1) PCF can configure Policy and Charging Control (PCC) rules. (3-2) PCF can send Policy Control Update Notification Request / Response messages to SMF. Messages sent to SMF can include QoS monitoring policies for active discarding and target information for reporting.

[0315] For example, a network policy control node (e.g., PCF) can create / update a PCC rule based on request information from AF and local configuration information or operator policy of PCF.

[0316] For example, a message sent by the PCF to the SMF may include QoS monitoring parameters. These QoS monitoring parameters may include subscription information related to active discarding and target information for reporting. Subscription information related to active discarding may include indications of direct event notification, reporting thresholds, etc.

[0317] For example, FEC Active Discarding information may be added to the description of QoS monitoring in TS 23.501 V18.1.0. For example,

[0318] Note that QoS monitoring consists of measuring QoS monitoring parameters and reporting the measurement results for QoS flows, and can be enabled based on third-party application requests and / or operator policies configured in PCF.

[0319] An AF may request measurements for one or more of the following QoS monitoring parameters, which may trigger QoS monitoring for service data flows:

[0320] - Crowded

[0321] - Data rate

[0322] - FEC Active Discarding Information

[0323] The PCF may generate approved QoS monitoring policies for service data flows based on QoS monitoring requests received from the AF, or for PCF local policy or configuration reasons, such as PCF awareness of dynamic satellite backhaul connections. The PCF may include the approved QoS monitoring policies in the PCC rules and provide them to the SMF.

[0324] The QoS monitoring parameters that can be measured through QoS monitoring are as follows. The QoS monitoring policy of a PCC rule can include the following:

[0325] - Crowded.

[0326] - Data rate.

[0327] - FEC Active Discarding Information

[0328] The SMF performs QoS monitoring on QoS flows and configures the UPF to report monitoring results using parameters determined by the SMF based on the approved QoS monitoring policy received from the PCF or local configuration or both.

[0329] Additionally, the SMF may configure the RAN to measure QoS monitoring parameters by sending QoS monitoring requests based on the approved QoS monitoring policy and / or local configuration received from the PCF.

[0330] (4) (4-1) The SMF can configure QoS monitoring settings for subscription to active discarding events. (4-2) Optionally, the SMF can also send an N4 session modification request message to the UPF. The N4 session modification request message can include information related to QoS monitoring settings for active discarding and targets of reporting. (4-3) The SMF can send the QoS monitoring settings for active discarding to the AMF. In this case, the AMF can send an N2 message containing QoS monitoring request information for active discarding to the RAN in step (5).

[0331] For example, the SMF can process the PCC rules received from the PCF according to conventional techniques. Furthermore, the SMF can transmit relevant information for QoS handling to the terminal, NG-RAN, and related NFs.

[0332] For example, according to the disclosure of this specification, QoS monitoring parameters for detecting and requesting notification of active discarding events may be included in the PCC rule transmitted by the PCF. In this case, based on the information included in the PCC rule and the direct notification request information from the AF, the SMF may transmit QoS monitoring configuration information to the UPF and the NG-RAN. That is, based on the request information for event notification transmitted by the AF in step (1), information such as the event notification method and conditions are transmitted to the NG-RAN.

[0333] For example, an Active Discarding Reporting request Information Element (IE) may be defined. This IE represents a request to an NG-RAN node to report the Active Discarding status for a QoS flow.

[0334] IE / Group Name Scope IE Type and Reference Semantics Description Event Reporting Type MENUMERATED (CP-based reporting, UP-based reporting, 쪋) Event Reporting Threshold OINTEGER (0..100) When the drop rate exceeds this threshold, Active Discarding Reporting is activated.

[0335] For reference, in the example in Table 3, CP-based reporting may mean Control Plane (CP) based reporting, and UP-based reporting may mean User Plane (UP) based reporting.

[0336] (5) The AMF may transmit an N2 message to the RAN. For example, the N2 message may include QoS monitoring request information for active discarding. The base station may transmit a response message to the N2 message to the AMF. For reference, the QoS monitoring request information for active discarding may be the same information as the QoS monitoring settings for active discarding in steps 4-1 to 4-3.

[0337] For example, the AMF can send an N2 message requesting QoS monitoring to the NG-RAN. For example, the N2 message can include Active Discarding subscription information and QoS monitoring configuration information received from the SMF.

[0338] For example, QoS monitoring configuration information may be configuration information that enables Active Discarding performance information from the RAN to be exposed to the AF under specific conditions (Threshold basis) or sent to the AF on demand. Active discarding subscription information may include destination information (Target of reporting) for the corresponding reporting (e.g., RAN event notification, event report, etc.) to be transmitted directly from the RAN to the AF or indirectly to the AF via 5GC NF.

[0339] Based on the N2 message, the NG-RAN can notify event information about Active Discarding for FEC by including the event information in the NGAP PDU Session Resource Notify message based on the control plane or by including the event information in the Uplink data based on the user plane.

[0340] (6) The SMF may send a request message related to the SM context update of the PDU session to the AMF. The AMF may send a response message related to the SM context update of the PDU session to the SMF.

[0341] (7) SMF can send a policy control update notification response message to PCF.

[0342] (8) PCF can send a policy authentication subscription response message to NEF.

[0343] (9) NEF may send a response message related to event subscription to AF.

[0344] For reference, steps 6 to 9 may be steps that notify that the message containing the subscription information transmitted by AF has been successfully delivered to RAN via 5GC.

[0345] TS 38.413 V18.1.0 S9.3.4.1 The PDU Session Resource Setup Request Transfer may include an Active Discarding Reporting Request. For example, the example in Table 4 below may be applied.

[0346] For reference, the example in Table 4 is an example of a PDU Session Resource Setup Request Transfer IE. This IE may indicate that information will be requested from the NG-RAN node.

[0347] IE / Group Name Scope IE Type and Reference Semantics Description Importance Assigned Importance QoS Flow Setup Request List 1 YES Reject > QoS Flow Setup Request Item 1.. <maxnoofqosflows>->>QoS Flow Identifier See S9.3.1.51 of MTS 38.413 V18.1.0->>QoS Flow Level QoS Parameters See 9.3.1.12 of MTS 38.413 V18.1.0->>Active Discarding Report Request O See the description related to Active Discarding Report Request This IE may be present if you are subscribed to Active discarding events. YES Ignore

[0348] For example, according to the example in Table 4, the N2 message may include a PDU Session Resource Setup Request Transmission IE. The PDU Session Resource Setup Request Transmission IE may include a QoS Flow Setup Request List, the QoS Flow Setup Request List may include a QoS Flow Setup Request Item, and the QoS Flow Setup Request Item may include an Active Discarding Report Request.

[0349] 2. Second example of disclosure of this specification

[0350] Referring to FIG. 8, a second example of the disclosure of the present specification is described.

[0351] For reference, the first example of the disclosure of this specification may be combined with the second example of the disclosure of this specification. For example, the procedure according to the example of FIG. 8 may be performed after the procedure according to the examples of FIGS. 7A and 7B are performed.

[0352] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals, messages, and fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0353] FIG. 8 illustrates a second example of a procedure according to one embodiment of the disclosure of the present specification.

[0354] Referring to the example of FIG. 8, an example of an active discarding event notification procedure for FEC is described. Note that in the example of FIG. 8, the RAN may also be referred to as a base station or NG-RAN.

[0355] Based on the AF request, the NG-RAN can perform active discarding on traffic containing FEC data between the application server and the terminal.

[0356] (1) The base station can perform active discarding on FEC data. Events related to active discarding may occur.

[0357] For example, as described in the first disclosure of this specification, an AF may subscribe to an event for Active Discarding. In this case, a base station (e.g., NG-RAN) may receive Active Discarding Reporting Request information (e.g., see the example in Table 3) from the SMF regarding the event. Based on the Active Discarding Reporting Request information, the base station may transmit a notification message when an event occurs. The notification message may include event notification information.

[0358] For example, in the examples of FIGS. 7A and 7B , the base station may receive an Active Discarding Report Request IE. The Active Discarding Report Request IE may include an event report type and an event report threshold. The base station may perform Active Discarding and transmit a notification message if the drop rate exceeds the event report threshold.

[0359] The NG-RAN can transmit event notification information via the control plane or the user plane. For example, in the first example of the disclosure of this specification, based on the Event Reporting Type (information included in the Active Discarding Report Request) set according to whether the AF request includes a Direct Reporting Request (or direct event notification information), the NG-RAN can transmit event notification information via the control plane or the user plane.

[0360] For example, in the first example of the disclosure of the present specification, a request message transmitted by the AF may include direct event notification information. Accordingly, the SMF transmits QoS monitoring configuration information for active discarding, including information such as an event notification method and conditions, to the AMF. The AMF may transmit QoS monitoring request information for active discarding to the base station based on the QoS monitoring configuration information for active discarding. The base station may transmit the event notification information through the control plane or the user plane, depending on whether the AF transmitted a direct reporting request (or direct event notification information).

[0361] Based on the Event Reporting Type, event notifications can be transmitted from the NG-RAN via the control plane (Event notification via control plane in the example of Figure 8). In this case, the base station can transmit an N2 message containing the event notification to the SMF via the AMF.

[0362] Alternatively, based on the Event Reporting Type, a direct notification may be sent via the user plane (Direct notification via user plane in the example of FIG. 8). In this case, the base station may transmit uplink user data containing notification information to the UPF. For example, information related to an active discarding event may be included in the header of uplink data according to a conventional QoS monitoring mechanism. Alternatively, if the base station does not have uplink data to transmit, the base station may transmit a direct notification using a dummy packet.

[0363] If an Event Reporting Threshold is included in the Active Discarding Reporting Request received from the SMF, the base station can decide whether to report the Event based on the Drop rate calculated by performing Active Discarding.

[0364] For example, as shown in the example in Table 5, the PDU Session Resource Notification Transmission IE may include FEC Active Discarding status information.

[0365] IE / Group Name Scope IE Type and Reference Semantics Description Importance Assigned Importance QoS Flow Notification List 0..1 > QoS Flow Notification Item 1.. <maxnoofqosflows>>>QoS Flow Identifier See 9.3.1.51 of MTS 38.413 V18.1.0>> Notification Reason MENUMERATED (fullfilled, not fulfilled, 쪋)>> FEC Active discarding Status OENUMERATED (activate, inactive, 쪋) YES Ignore

[0366] (2) and (3). (2a) In case of event notification via the control plane, the base station can transmit a PDU session resource notification message to the AMF. For example, in case of event notification via the control plane (NG-RAN->AMF->SMF->PCF->NEF->AF), the notification information for the active discarding event transmitted by the NG-RAN can be transparently transmitted to the SMF via the AMF according to Steps (3a-1) to (3a-4). In addition, the notification information for the active discarding event can be transmitted to the AF via the PCF and NEF.

[0367] (2b) Alternatively, in the case of direct notification via the user plane, the base station may transmit uplink data containing active discarding event notification information to the UPF. For example, in the case of direct notification via the user plane (RAN->UPF->AF), the base station may transmit user data containing the notification information. In this case, according to Step (3b), the UPF may detect active discarding event notification information and directly transmit the active discarding event notification information to the AF.

[0368] (4) Based on the active discarding event notification information, the AF can perform application layer rate adaptation. For example, the active discarding event notification information for FEC received in Step 3 can be referenced in determining application layer rate adaptation between the AF / AS and the terminal. For example, the AF can perform actions related to application layer means based on the event information. For example, the AF can perform actions to prevent inefficiencies (e.g., increased FEC request rate from the terminal, additional delay, and packet loss rate mismeasurement) caused by FEC data intentionally discarded by the NG-RAN. Alternatively, the AF can make decisions such as adjusting the FEC data transmission rate for the corresponding application traffic or no longer sending FEC data based on the active discarding event notification information.

[0369] 3. Third example of disclosure of this specification

[0370] Hereinafter, a third example of the disclosure of the present specification will be described with reference to FIG. 9. Note that the third example of the disclosure of the present specification may be combined with the first and / or second examples of the disclosure of the present specification.

[0371] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals, messages, and fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0372] FIG. 9 illustrates a third example of a procedure according to one embodiment of the disclosure of the present specification.

[0373] According to the example of Fig. 9, NG-RAN can control application rate adaptation.

[0374] (1)~(2) The AF can send a request message (e.g., Nnef_AFsessionWithQoS_Create Request message) to the NEF. The request message can also include information on whether to allow Rate Adaptation suspend, a UE address, flow description information, or an external application identifier. After authenticating the AF, the NEF can send a request message containing information on whether to allow Rate Adaptation suspend to the PCF.

[0375] For example, the AF can transmit information that allows the UE to control the rate adaptation delay (suspend) in 5GS. For example, the AF can transmit information that allows the UE to control the rate adaptation delay (suspend) in 5GS for packet discarding based on PDU Set (e.g., active discarding for FEC of NG-RAN or packet discarding according to congestion situation) (i.e., information on whether rate adaptation suspension is permitted).

[0376] In the disclosure of this specification, it is assumed that the AF knows the capabilities of the terminal in order to transmit information on whether or not to permit Rate Adaptation Suspension. For example, the AF can transmit Rate Adaptation Delay Control permission information for a terminal capable of FEC rate adaptation for application traffic. The Rate Adaptation Suspension permission information can be transmitted through the NEF or directly to the PCF together with information that can identify the target, such as the conventional UE address, Flow description, or External Application ID.

[0377] In step (1), the Nnef_AFsessionWithQoS_Create service operation may be used. For example, the following description may be applied to the Nnef_AFsessionWithQoS_Create service operation.

[0378] The Nnef_AFsessionWithQoS_Create service operation allows a consumer to request the network to provide specific QoS for an AF session for a UE or a list of UEs.

[0379] Inputs, Required: AF identifier, UE address (i.e., IP address or MAC address, for single UE AF sessions only), UE address list (for multimember AF sessions only), flow description information or application identifier, QoS reference or individual QoS parameters.

[0380] Inputs, Optional: Time period, traffic volume, alternate service requirements (including one or more QoS reference parameters or a requested set of alternate QoS parameters, in order of priority), QoS monitoring parameters, reporting frequency, reporting target, and optionally local event notification indication, DNN if available, S-NSSAI if available, Rate adaptation suspend allowed indication.

[0381] Output, required: Transaction Reference ID, Result

[0382] Output (optional): None

[0383] (3) The PCF can create / update a PCC rule including rate adaptation delay control permission information (e.g., information on whether to allow rate adaptation suspend) in the AF request. The PCF transmits the created / updated PCC rule to the SMF, and the SMF can adjust QoS-related information to be sent to the terminal, NG-RAN, and UPF according to conventional procedures. The PCF can configure a QoS profile to be sent to the NG-RAN. For example, the PCF can transmit a QoS profile including rate adaptation delay control information to the base station through the AMF. For example, if the AF allows rate adaptation delay control to the 5GC through the rate adaptation suspend permission information, the PCF can transmit rate adaptation delay control information. For reference, the rate adaptation suspend permission information transmitted by the AF and the rate adaptation delay control information transmitted by the PCF, AMF, and RAN can include information related to whether rate adaptation delay control for the terminal is permitted. For reference, in the example of Fig. 9, “Rate Adaptation control information” may be the same information as the Rate adaptation delay control information.

[0384] AMF can send an N2 message containing Rate Adaptation control information to RAN.

[0385] (4) NG-RAN can perform active discarding of FEC data based on AF request or packet discarding based on PDU Set in case of RAN internal congestion.

[0386] (5) In step (4), an RRC reconfiguration message including Rate adaptation control information may be transmitted to the terminal based on the packet discarding performed by the NG-RAN. The Rate adaptation control information may be updated based on a subsequent procedure message transmitted by the base station. Based on local configuration information or operator policy, the base station may transmit Rate adaptation control information. For example, based on local configuration information or operator policy, the Rate adaptation control information may optionally include i) whether control for Rate adaptation delay is enabled or disabled, and ii) a Rate adaptation suspend timer based on the Expected congestion period depending on the NG-RAN internal congestion status.

[0387] The terminal can receive the Rate Adaptation Delay Control enable / disable status and the suspend timer value. In this case, the terminal can determine whether to delay / resume application layer rate adaptation based on this information. Accordingly, an increase in the FEC request rate in the delay control state can be prevented, and packet loss rate mismeasurement can be prevented.

[0388] For example, a terminal may receive control information regarding Application rate adaptation disabled from 5GS. In this case, the terminal may not increase the FEC request rate, lower the FEC request rate, or suspend further FEC requests until the state is updated to Application rate adaptation enabled according to a subsequent procedure message. If the terminal also receives a suspend timer value, the terminal may not increase the FEC request rate within that time, lower the FEC request rate, or suspend further FEC requests.

[0389] 3. Fourth example of disclosure of this specification

[0390] The fourth example of the disclosure of this specification describes an example of a procedure based on the various examples of the disclosure of this specification described above.

[0391] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals, messages, and fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0392] FIG. 10 illustrates an example of operations according to one embodiment of the disclosure of the present specification.

[0393] For reference, the procedure illustrated in FIG. 10 is merely an example, and the scope of the disclosure of this specification is not limited by the example in FIG. 10.

[0394] For example, with respect to the example of FIG. 10, the operations described in the examples of FIGS. 1 to 9 may also be applied. For example, even if operations, contents, etc. are not directly described in the example of FIG. 10, operations, contents, etc. described in various examples of the disclosure of this specification may be applied.

[0395] The operations illustrated in FIG. 10 are merely examples, and the scope of the disclosure of this specification is not limited to the operations illustrated in FIG. 10.

[0396] For example, the first network entity may be a network entity that manages mobility. For example, the first network entity may be an AMF. For example, the second network entity may be a network entity that manages the user plane. For example, the second network entity may be a UPF.

[0397] Although the example of FIG. 10 illustrates two network entities, this is merely an example. Various network entities, such as a network entity involved in a session (e.g., an SMF), a network entity involved in a policy (e.g., a PCF), and a network entity involved in an application (e.g., an AF), may perform operations in accordance with the disclosure herein.

[0398] For reference, before step (S1001) is performed, the following actions may also be performed.

[0399] For example, a UE may perform a random access procedure with a base station. The UE may transmit a random access preamble to the base station. The base station may transmit a response message to the UE.

[0400] For example, a UE, a base station, a first network entity, a second network entity, and an SMF may perform a PDU session establishment procedure according to the examples of FIGS. 5 and 6.

[0401] In step (S1001), the UE may transmit a random access preamble to the base station.

[0402] In step (S1002), the base station can transmit a response message to the UE.

[0403] At step (S1003), the first network entity can transmit an N2 message to the base station.

[0404] For example, an N2 message may contain Quality of Service (QoS) monitoring request information related to active discarding.

[0405] QoS monitoring request information may include active discard report request information. The active discard request information may include an event report type and an event report threshold.

[0406] Based on the QoS monitoring request information, the base station can perform active discarding on traffic containing FEC data between the UE and the network entity associated with the application.

[0407] In step (S1004), the base station can transmit a message related to the notification to the first network entity or the second network entity.

[0408] For example, based on the QoS monitoring request information, the base station may transmit notification information related to the event related to the active discard to the first network entity or a second network entity related to the user plane.

[0409] For example, if the QoS monitoring request information includes an event report type set to Control Plane (CP)-based reporting, the base station may transmit a PDU session resource notification message including notification information related to an event related to active discard to the first network node.

[0410] For example, if the QoS monitoring request information includes an event report type set to User Plane (UP)-based reporting, the base station may transmit uplink data including notification information related to an event related to active discard to the second network entity.

[0411] The first network entity may receive QoS monitoring settings from a network entity associated with the session. Based on the QoS monitoring settings, the first network entity may transmit an N2 message including QoS monitoring request information to the base station.

[0412] For example, a network entity (e.g., an SMF) associated with a session may perform the following actions. The network entity associated with the session may receive a PDU Session Establishment Request message from a UE. The network entity associated with the session may send a PDU Session Establishment Accept message to the UE. The network entity associated with the session may receive a notification message related to policy control including a Policy and Charging Control (PCC) rule from a network node associated with the policy. The PCC rule may include a Quality of Service monitoring policy for active discarding. The network entity associated with the session may transmit QoS monitoring settings related to the active discarding to a second network node based on the QoS monitoring policy, and / or to a base station via the first network node.

[0413] For example, QoS monitoring settings may include active discard report request information. The active discard request information may include an event report type and an event report threshold. The event report type may include a Control Plane (CP)-based report or a User Plane (UP)-based report. The event report threshold may be used to activate active discard reporting when the drop rate is greater than or equal to the event report threshold.

[0414] For example, a network entity (e.g., PCF) involved in a policy may perform the following actions: The request message may include an event ID related to active discarding, information related to direct event notification, and a reporting threshold. The network entity involved in the policy may then send a notification message related to policy control, including Policy and Charging Control (PCC) rules configured based on the request message, to the network nodes involved in the session.

[0415] For reference, in the various examples of the disclosure of this specification, the operations performed by the base station, SMF, PCF, UE, AF, etc. may be operations related to data (or services, or information) related to XR and interactive media services.

[0416] For reference, in the disclosure of this specification, network entity and network node may be used as terms with the same meaning.

[0417] According to one embodiment of the disclosure of the present specification, a network node (e.g., AF) associated with an application may subscribe to be notified of an active discarding event for FEC performed by the NG-RAN. Furthermore, the network node (e.g., AF) associated with the application may optionally provide information on whether application rate adaptation control is authorized by the NG-RAN.

[0418] According to one embodiment of the disclosure of the present specification, a network node (e.g., PCF) associated with a policy can receive information on whether FEC active discarding event subscription information or application rate adaptation control is permitted from an AF. The network node (e.g., PCF) associated with the policy can generate / update a PCC rule by including the information on whether FEC active discarding event subscription information or application rate adaptation control is permitted in a QoS monitoring parameter. The network node (e.g., PCF) associated with the policy can transmit the generated / updated PCC rule to other network nodes.

[0419] According to one embodiment of the disclosure of the present specification, a network node (e.g., SMF) associated with a session can receive a PCC rule generated / updated from a network node (e.g., PCF) associated with a policy. The generated / updated PCC rule can include information on whether FEC active discarding subscription information or application rate adaptation control is permitted. In this case, the network node (e.g., SMF) associated with the session can include information on whether FEC active discarding subscription information or application rate adaptation control is permitted in a QoS monitoring configuration. The network node (e.g., SMF) associated with the session can transmit the QoS monitoring configuration to the NG-RAN via a network node (e.g., AMF) associated with mobility. If a direct reporting indication exists in the PCC rule, the network node (e.g., SMF) associated with the session can set an N4 rule to the UPF including the QoS monitoring configuration.

[0420] According to one embodiment of the disclosure of the present specification, a base station (e.g., NG-RAN) can receive an active discarding event subscription from a network node (e.g., AF) associated with an application. Based on the reporting type and reporting threshold included in the active discarding event subscription, the base station (e.g., NG-RAN) can transmit a notification. For example, based on the reporting type and reporting threshold included in the active discarding event subscription, the base station (e.g., NG-RAN) can transmit a notification including discarding information for FEC traffic to an SMF or UPF via the control plane or user plane.

[0421] According to one embodiment of the disclosure of the present specification, a network node (e.g., AF) associated with an application can receive a notification from an NG-RAN regarding an FEC Active Discarding event. The network node (e.g., AF) associated with the application can determine whether to delay / resume application layer rate adaptation based on the notification. That is, the AF can perform actions such as preventing an increase in the FEC request rate of a terminal due to discarding FEC data, preventing additional delay, and preventing packet loss rate mismeasurement. For example, the network node (e.g., AF) associated with the application can determine, based on the notification, to adjust the FEC data transmission rate for the corresponding application traffic or to no longer transmit FEC data.

[0422] According to one embodiment of the disclosure of the present specification, a base station (e.g., NG-RAN) can receive information on whether application rate adaptation control is permitted from a network node (e.g., AF) related to an application. In this case, in a situation of active discarding for FEC traffic or RAN internal congestion, the base station (e.g., NG-RAN) can perform discarding on a PDU set, and the base station (e.g., NG-RAN) can transmit application rate adaptation control information to a terminal. The application rate adaptation control information may be updated to application rate adaptation enabled / disabled information by a subsequent procedure message. Additionally, the application rate adaptation control information may optionally include timer information corresponding to an expected congestion period value.

[0423] According to one embodiment of the disclosure of the present specification, a terminal (e.g., UE) can receive application rate adaptation control information from an NG-RAN. In this case, the terminal can determine application layer rate adaptation delay / resume based on the application rate adaptation control information. Furthermore, the terminal can determine an FEC request rate and a packet loss rate based on the application rate adaptation control information. For example, if the terminal receives application rate adaptation control information from a 5GS, the terminal cannot increase the FEC request rate accordingly, and may lower the FEC request rate or stop making any further FEC requests.

[0424] This specification may have various effects.

[0425] For example, the terminal and application layers can detect intentional active discarding by 5GS / RAN. This prevents increases in FEC request rates and bandwidth. Furthermore, additional delays due to increased FEC data can be prevented. Furthermore, the application layer can accurately and effectively measure packet loss rates and network capacity.

[0426] The effects that can be achieved through the specific examples of this specification are not limited to the effects listed above. For example, a person with ordinary skill in the relevant technical field may understand or derive various technical effects from this specification. Accordingly, the specific effects of this specification are not limited to those explicitly described herein, but may include various effects that can be understood or derived from the technical features of this specification.

[0427] For reference, the operation of the terminal (e.g., UE, terminal) described in this specification can be implemented by the devices of FIGS. 1 to 3 described above. For example, the terminal can be the first device (100) or the second device (200) of FIG. 2. For example, the operation of the terminal described in this specification can be processed by one or more processors (102 or 202). The operation of the terminal described in this specification can be stored in one or more memories (104 or 204) in the form of instructions / programs (e.g., instructions, executable codes) executable by one or more processors (102 or 202). The 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 the instructions / programs stored in one or more memories (104 or 204) to perform the operation of the terminal (e.g., UE) described in the disclosure of this specification.

[0428] Additionally, the commands for performing the operations of the terminal 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). In addition, the commands recorded in the storage medium may be executed by one or more processors (102 or 202) to perform the operations of the terminal described in the disclosure of this specification.

[0429] For reference, the operations of a network entity (e.g., AMF, PCF, SMF, UPF, UDM, DN, AF, NEF, etc.) or a base station (e.g., NG-RAN, gNB, RAN, (R)AN, etc.) described in this specification may be implemented by the devices of FIGS. 1 to 3 described below. For example, the network entity (or network node) or the base station may be the first device (100) or the second device (200) of FIG. 2. For example, the operations of the network entity or the base station described in this specification 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 codes) executable by one or more processors (102 or 202). One or more processors (102 or 202) may 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) to perform operations of a network entity or base station as described in the disclosure of this specification.

[0430] Additionally, the instructions for performing the operations of the network entity or base station described in the disclosure of this specification may be stored in a non-volatile (or non-transitory) computer-readable storage medium having the instructions recorded thereon. The storage medium may be included in one or more memories (104 or 204). In addition, the instructions recorded in the storage medium may be executed by one or more processors (102 or 202) to perform the operations of the network entity or base station described in the disclosure of this specification.

[0431] Although the preferred embodiments have been described above by way of example, the disclosure of this specification is not limited to such specific embodiments, and may be modified, changed, or improved in various forms within the scope described in the spirit and claims of this specification.

[0432] In the exemplary system described above, the methods are described based on a flowchart as a series of steps or blocks. However, the order of the steps described is not limited, and some steps may occur in a different order or simultaneously with other steps described above. Furthermore, those skilled in the art will understand that the steps depicted in the flowchart are not exclusive, and other steps may be included, or one or more steps in the flowchart may be deleted without affecting the scope of the invention.

[0433] The claims set forth in this specification may be combined in various ways. For example, the technical features of the method claims of this specification may be combined to implement a device, and the technical features of the device claims of this specification may be combined to implement a method. Furthermore, the technical features of the method claims and the technical features of the device claims of this specification may be combined to implement a device, and the technical features of the method claims and the technical features of the device claims of this specification may be combined to implement a method. Other implementations are within the scope of the claims.< / maxnoofqosflows> < / maxnoofqosflows>

Claims

1. A step of receiving a random access preamble message from a User Equipment (UE); A step of transmitting a response message related to random access to the UE; A step of receiving an N2 message from a first network entity related to mobility, The above N2 message includes Quality of Service (QoS) monitoring request information related to active discarding; and A method comprising the step of transmitting notification information related to an event related to the active discard to the first network entity or a second network entity related to the user plane based on the QoS monitoring request information.

2. In paragraph 1, The above QoS monitoring request information includes active discard report request information, A method characterized in that the above active discard request information includes an event report type and an event report threshold.

3. In paragraph 1 or 2, A method further comprising the step of performing active discarding on traffic containing Forward Error Correction (FEC) data between the UE and a network entity associated with the application.

4. In any one of paragraphs 1 to 3, A method characterized in that the notification information is transmitted when the drop rate due to active discarding exceeds the event reporting threshold included in the QoS monitoring request information.

5. In any one of paragraphs 1 to 4, A method characterized in that, when the QoS monitoring request information includes an event report type set to a Control Plane (CP)-based report, a PDU session resource notification message including notification information related to an event related to the active discard is transmitted to the first network node.

6. In any one of paragraphs 1 to 5, A method characterized in that, when the QoS monitoring request information includes an event report type set to User Plane (UP)-based reporting, uplink data including notification information related to an event related to the active discard is transmitted to the second network entity.

7. One or more transmitters and receivers; one or more processors; and comprising one or more memories capable of storing instructions and being operable to the one or more processors; A device wherein the operation performed based on the above command being executed by the one or more processors is a method according to any one of claims 1 to 6.

8. A step of receiving a Protocol Data Unit (PDU) session establishment request message from a User Equipment (UE); A step of transmitting a PDU session establishment acceptance message to the UE; A step of receiving a notification message related to policy control including a Policy and Charging Control (PCC) rule from a first network node related to the policy; The above PCC rule includes a Quality of Service monitoring policy for active discarding; and A method comprising the step of transmitting, based on the above QoS monitoring policy, QoS monitoring settings related to the active discard to a second network node related to the user plane, and / or transmitting them to the base station via a third network node related to mobility.

9. In paragraph 8, The above QoS monitoring settings include active discard report request information, A method characterized in that the above active discard request information includes an event report type and an event report threshold.

10. In paragraph 8 or 9, The above event reporting types include Control Plane (CP) based reporting or User Plane (UP) based reporting, A method characterized in that the above event reporting threshold is used to activate active discard reporting when the drop rate is greater than or equal to the above event reporting threshold.

11. One or more transmitters and receivers; one or more processors; and comprising one or more memories capable of storing instructions and being operable to the one or more processors; A device wherein the operation performed based on the command being executed by the one or more processors is a method according to any one of claims 8 to 10.

12. A step of receiving a request message from a first network node related to network exposure; The above request message includes an event ID related to active discarding, information related to direct event notification, and a reporting threshold; and A method comprising the step of transmitting a notification message related to policy control including a Policy and Charging Control (PCC) rule configured based on the above request message to a second network node involved in the session.

13. In paragraph 12, A method characterized in that the above PCC rule includes a Quality of Service monitoring policy for active discarding.

14. One or more transmitters and receivers; one or more processors; and comprising one or more memories capable of storing instructions and being operable to the one or more processors; A device wherein the operation performed based on the command being executed by the one or more processors is a method according to any one of claims 12 to 13.

Images