IP address allocation method for ethernet

Abstract

An embodiment of the present disclosure provides a method. The method comprises the steps of: an SMF receiving, from a UPF, MPQUIC-E-related information including at least one of an IPv4 address and an IPv6 address; and on the basis of the MPQUIC-E-related information, transmitting, to a base station, type information of a PDU session for Ethernet, wherein the type information includes at least one of IPv4, IPv6, and IPv4v6, and MPQUIC-E is activated for the PDU session.

Description

IP address allocation method for Ethernet

[0001] This specification relates to mobile communication.

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

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

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

[0005] When MPQUIC-E is enabled for an Ethernet type PDU session, UPF allocates the IPv4 and / or IPv6 addresses required to use MPQUIC-E.

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

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

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

[0009] Figure 4 is a structural diagram of a next-generation mobile communication network.

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

[0011] FIGS. 6 and 7 illustrate examples of PDU session establishment procedures to which the implementation of the present specification applies.

[0012] FIG. 8 illustrates an example of a configuration-based MPQUIC-E proxy address allocation procedure according to the disclosure of the present specification.

[0013] FIG. 9 illustrates the procedure of SMF for the disclosure of the present specification.

[0014] FIG. 10 illustrates the procedure of the UE for the disclosure of the present specification.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0049] Frequency Range Definition Frequency Range Subcarrier Spacing FR1 450 MHz - 6000 MHz 15, 30, 60 kHz FR2 24 250 MHz - 52600 MHz 60, 120, 240 kHz

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

[0051] Frequency Range Definition Frequency Range Subcarrier Spacing FR1 4 10 MHz - 7 125 MHz 15, 30, 60 kHz FR2 24 250 MHz - 5 2600 MHz 60, 120, 240 kHz

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

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

[0054] 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 example / service. For example, {the first wireless device (100) and the second wireless device (200)} may correspond to at least one of {wireless devices (100a–100f) and base station (200)}, {wireless devices (100a–100f) and wireless devices (100a–100f)} and / or {base station (200) and base station (200)} of FIG. 1. The first wireless device (100) and / or the second wireless device (200) may be composed of various components, devices / parts and / or modules.

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

[0056] 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 generally, the memory (104) may be placed outside the processing chip (101).

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

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

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

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

[0061] 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 placed outside the processing chip (201).

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

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

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

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

[0066] One or more processors (102, 202) may be referred to as a controller, a microcontroller, a microprocessor, and / or a microcomputer. One or more processors (102, 202) may be implemented by hardware, firmware, software, and / or a combination thereof. For example, one or more application-specific integrated circuits (ASICs), one or more digital signal processors (DSPs), one or more digital signal processing devices (DSPDs), one or more programmable logic devices (PLDs), and / or one or more field programmable gate arrays (FPGAs) may be included in one or more processors (102, 202). For example, one or more processors (102, 202) may be composed of a set of communication control processors, application processors (APs), electronic control units (ECUs), central processing units (CPUs), graphic processing units (GPUs), and memory control processors.

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

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

[0069] One or more transceivers (106, 206) may be connected to one or more antennas (108, 208). Additionally and / or generally, 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 operation flowcharts disclosed herein through one or more antennas (108, 208). In this specification, one or more antennas (108, 208) may be a plurality of physical antennas or a plurality of logical antennas (e.g., antenna ports).

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

[0071] Although not illustrated in FIG. 2, the wireless device (100, 200) may 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., audio I / O port, video I / O port), a driving unit, and a computing unit. The additional components (140) may be connected to one or more processors (102, 202) through various technologies, such as wired or wireless connections.

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

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

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

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

[0076] The UE (100) includes a processor (102), memory (104), 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).

[0077] The processor (102) may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed herein. The processor (102) may be configured to control one or more other components of the UE (100) to implement the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed herein. Layers of a wireless interface protocol may be implemented in the processor (102). The processor (102) may include an ASIC, other chipsets, logic circuits, and / or data processing devices. The processor (102) may be an application processor. The processor (102) may include at least one of a 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 processor, EXYNOS made by Samsung® TM Series processors, A Series processors made by Apple®, HELIO made by MediaTek® TM Series processors, ATOM made by Intel® TM It can be found in series processors or corresponding next-generation processors.

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

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

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

[0081] The display (143) outputs the result 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).

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

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

[0084] Figure 4 is a structural diagram of a next-generation mobile communication network.

[0085] 5GC (5G Core) may include various components, and FIG. 5 includes some of them, such as AMF (Access and Mobility Management Function) (410), SMF (Session Management Function) (420), PCF (Policy Control Function) (430), UPF (User Plane Function) (440), AF (Application Function) (450), UDM (Unified Data Management) (460), and N3IWF (Non-3GPP (3rd Generation Partnership Project) Inter Working Function) (490).

[0086] The UE (100) is connected to the data network via the UPF (440) through the NG-RAN (Next Generation Radio Access Network) including the gNB (20).

[0087] The UE (100) can also receive data services through untrusted non-3GPP access, such as a WLAN (Wireless Local Area Network). To connect the non-3GPP access to the core network, an N3IWF (490) may be deployed.

[0088] The illustrated N3IWF (490) performs the function of managing interworking between non-3GPP access and 5G systems. When the UE (100) is connected to non-3GPP access (e.g., WiFi referred to as IEEE 801.11), the UE (100) can be connected to the 5G system through the N3IWF (490). The N3IWF (490) performs control signing with the AMF (410) and connects to the UPF (440) via the N3 interface for data transmission.

[0089] The illustrated AMF (410) can manage access and mobility in a 5G system. The AMF (410) can perform the function of managing Non-Access Stratum (NAS) security. The AMF (410) can perform the function of handling mobility in an idle state.

[0090] The illustrated UPF (440) is a type of gateway through which user data is transmitted and received. The UPF node (440) can perform all or part of the user plane functions of the S-GW (Serving Gateway) and P-GW (Packet Data Network Gateway) of 4th generation mobile communication.

[0091] The UPF (440) acts as a boundary point between the next generation radio access network (NG-RAN) and the core network, and is an element that maintains the data path between the gNB (20) and the SMF (420). Additionally, when the UE (100) moves across the area served by the gNB (20), the UPF (440) acts as a mobility anchor point. The UPF (440) can perform the function of handling PDUs. For mobility within the NG-RAN (Next Generation Radio Access Network defined in 3GPP Release-15 or later), packets can be routed through the UPF. Additionally, the UPF (440) may also function as an anchor point for mobility with other 3GPP networks (RANs defined prior to 3GPP Release-15, e.g., UTRAN, E-UTRAN (Evolved-UMTS (Universal Mobile Telecommunications System) Terrestrial Radio Access Network)) or GERAN (GSM (Global System for Mobile Communication) / EDGE (Enhanced Data rates for Global Evolution) Radio Access Network). The UPF (440) may correspond to a termination point of a data interface toward a data network.

[0092] The illustrated PCF (430) is a node that controls the operator's policy.

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

[0094] The illustrated UDM (460) is a type of server that manages subscriber information, such as the HSS (Home subscriber Server) of 4th generation mobile communication. The UDM (460) stores and manages the subscriber information in a Unified Data Repository (UDR).

[0095] The illustrated SMF (420) can perform the function of assigning the IP (Internet Protocol) address of the UE. Also, the SMF (420) can control the PDU (protocol data unit) session.

[0096] For reference, the reference numerals for AMF (410), SMF (420), PCF (430), UPF (440), AF (450), UDM (460), N3IWF (490), gNB (20), or UE (100) may be omitted below.

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

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

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

[0100] - AUSF (Authentication Server Function)

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

[0102] - DN (Data Network), 예를 들어 운영자 서비스, 인터넷 접속 또는 타사 서비스

[0103] - USDF (Unstructured Data Storage Function)

[0104] - NEF (Network Exposure Function)

[0105] - I-NEF (Intermediate NEF)

[0106] - NRF (Network Repository Function)

[0107] - NSSF (Network Slice Selection Function)

[0108] - PCF (Policy Control Function)

[0109] - SMF (Session Management Function)

[0110] - UDM (Unified Data Management)

[0111] - UDR (Unified Data Repository)

[0112] - UPF (User Plane Function)

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

[0114] - AF (Application Function)

[0115] - UE (User Equipment)

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

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

[0118] - NWDAF (Network Data Analytics Function)

[0119] - CHF (CHarging Function)

[0120] In addition, the following network functions may be considered.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0147] <PDU 세션 수립 절차>

[0148] The procedure for establishing a PDU session is described. Refer to Section 4.3.2 of 3GPP TS 23.502 V16.3.0 (2019-12).

[0149] FIGS. 6 and 7 illustrate examples of PDU session establishment procedures to which the implementation of the present specification applies.

[0150] PDU session establishment may fall under the following:

[0151] - Procedure for establishing a PDU session initiated by the UE

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

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

[0154] - Procedure for establishing a PDU session triggered by the network

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

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

[0157] In the procedure shown in Figures 6 and 7, it is assumed that the AMF has already retrieved user subscription data from the UDM unless the UE is urgently registered, since the UE is already registered with the AMF.

[0158] First, the procedure of Fig. 6 will be explained.

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

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

[0161] If the PDU session establishment is a request to establish a new PDU session, the request type indicates "Initial Request". If the request refers to an existing PDU session transitioning between a 3GPP connection and a non-3GPP connection, or a PDU session handover from an existing PDN (packet data network) connection in the EPC, the request type indicates "Existing PDU Session". If the PDU session establishment is a request to establish a PDU session for an emergency service, the request type indicates "Emergency Request". If the request refers to an existing PDU session for an emergency service transitioning between a 3GPP connection and a non-3GPP connection, or a PDU session handover from an existing PDN connection for an emergency service in the EPC, the request type indicates "Existing Emergency PDU Session".

[0162] The UE includes S-NSSAI (Single Network Slice Selection Assistance Information) from the allowed NSSAI of the current connection type. If a mapping of the allowed NSSAI is provided to the UE, the UE provides both the S-NSSAI of the visited VPLMN from the allowed NSSAI and the corresponding S-NSSAI of the HPLMN from the mapping of the allowed NSSAI.

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

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

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

[0166] If the request type indicates an "existing PDU session" that refers to an existing PDU session moving between a 3GPP connection and a non-3GPP connection, and the serving PLMN S-NSSAI of the PDU session exists in the allowed NSSAI of the target connection type, the PDU session establishment procedure may be performed in the following cases.

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

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

[0169] Otherwise, the AMF rejects the request to establish a PDU session with an appropriate reason for rejection.

[0170] AMF rejects requests from urgently registered UEs where the request type does not indicate "Urgent Request" or "Existing Urgent PDU Session".

[0171] (3) Step 3: If the AMF is not associated with an SMF for a PDU session ID provided by the UE (e.g., when the request type indicates "initial request"), the AMF calls the Create SMContext request procedure (e.g., Nsmf_PDUSession_CreateSMContext Request). If the AMF is already associated with an SMF for a PDU session ID provided by the UE (e.g., when the request type indicates "existing PDU session"), the AMF calls the Update SMContext request procedure (e.g., Nsmf_PDUSession_UpdateSMContext Request).

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

[0173] The AMF ID is the UE's GUAMI and uniquely identifies the AMF serving the UE. The AMF transmits the PDU Session ID along with an N1 SM container containing the PDU session establishment request message received from the UE. The generic public subscription identifier (GPSI) is included if available in the AMF.

[0174] If a UE in a restricted service state is registered for emergency services without providing a SUPI, the AMF provides a PEI instead of a SUPI. If a UE in a restricted service state is registered for emergency services while providing a SUPI but is not authenticated, the AMF indicates that the SUPI is not authenticated. If the SMF does not receive a SUPI from a UE or if the AMF indicates that the SUPI is not authenticated, the UE is determined to be unauthenticated.

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

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

[0177] (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 in accordance with the request received in Step 3.

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

[0179] If the SMF decides not to accept the establishment of a PDU session, the SMF rejects the UE request via a NAS SM signal containing 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 that the SMF proceeds to step 20 below and the PDU session establishment procedure is stopped.

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

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

[0182] (7b) Step 7b: SMF can establish an SM policy association with PCF and obtain a basic PCC rule for the PDU session by performing the SM policy association establishment procedure.

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

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

[0185] (10) Step 10: If the request type indicates an “initial request,” the SMF may initiate an N4 Session Establishment procedure with the selected UPF. Otherwise, the SMF may initiate an N4 Session Modification procedure with the selected UPF.

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

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

[0188] The N1N2 message delivery message may include N2 SM information. The N2 SM information carries the following information that the AMF will transmit to the (R)AN.

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

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

[0191] - PDU Session ID: Indicates to the UE the association between the RAN resource and the PDU session for the UE;

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

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

[0194] - Maximum data rate for UE integrity protection received in PDU session establishment request message: When integrity protection is indicated as "Preferred" or "Required" in user plane security enforcement information

[0195] - RSN (redundancy sequence number) parameter

[0196] The N1N2 message delivery message may include an N1 SM container. The N1 SM container includes a PDU session establishment acceptance message that the AMF will provide to the UE. The PDU session establishment acceptance message includes an S-NSSAI from an allowed NSASI. In the case of an LBO roaming scenario, the PDU session establishment acceptance message includes an S-NSSAI from an allowed NSSAI for the VPLMN, and also includes the corresponding S-NSSAI for the HPLMN from the mapping of the allowed NSSAI received by the SMF in step 3.

[0197] If necessary for QoS flows related to QoS rules and QoS profiles, multiple QoS rules, QoS flow levels, and QoS parameters may be included in the PDU session establishment acceptance message and N2 SM information within the N1 SM container.

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

[0199] (12) Step 12: The AMF sends a NAS message containing a PDU session ID destined for the UE, a message accepting the establishment of a PDU session, and N2 SM information received from the SMF to (R)AN within the N2 PDU session request message.

[0200] (13) Step 13: (R)AN can perform AN-specific signal exchanges with the UE regarding information received from the SMF. For example, in the case of NG-RAN, it can perform RRC connection reconfiguration with the UE to set up necessary NG-RAN resources in relation to the QoS rules for the PDU session request received by the UE in Step 12.

[0201] (R)AN forwards the NAS message (PDU session ID, N1 SM container (PDU session establishment acceptance message)) received in step 12 to the UE. (R)AN provides the NAS message to the UE only if the AN-specific signal exchange with the UE includes the addition of (R)AN resources related to the received N2 command.

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

[0203] Now, the procedure of Fig. 7 following the procedure of Fig. 6 is explained.

[0204] (14) Step 14: (R)AN sends an N2 PDU session response message to AMF. The N2 PDU session response message may include a PDU session ID, cause, N2 SM information (PDU session ID, AN tunnel information, list of accepted / rejected QFIs, user plane enforcement policy notifications), etc.

[0205] (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.

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

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

[0208] After this step, UPF can deliver the DL packet that may have been buffered for this PDU session to the UE.

[0209] (16c) Step 16c: If the SMF is not yet registered for this PDU session, the SMF can register with the UDM for the given PDU session.

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

[0211] After this step, AMF delivers the relevant events subscribed to by SMF.

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

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

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

[0215] (21) Step 21: If the establishment of a PDU session fails after Step 4, and the SMF no longer processes the UE's PDU session, the SMF may unsubscribe from the modification of the session management subscription data.

[0216] 3GPP conducted a study to further extend ATSSS's MPQUIC with a study called Multi-Access (DualSteer and ATSSS_Ph4) in Rel-19.

[0217] Currently, the MPQUIC steering function supports steering, switching, and splitting for IETF protocol-based UDP traffic using UDP proxying over HTTP. For TCP traffic, ATSSS has relied on the "MPTCP steering function" specified in Rel-16. The related proxy functions (MPQUIC and MPTCP) add complexity to operator deployments. To alleviate this deployment burden, we need to investigate ways to enable the MPQUIC steering function to support steering, switching, and splitting for non-UDP traffic (i.e., TCP, IP, and Ethernet traffic), while making the MPTCP steering function for TCP traffic optional in ATSSS.

[0218] To implement MPQUIC steering functions that support steering, switching, and splitting of non-UDP traffic (e.g., TCP, IP, Ethernet traffic), the following matters must be studied.

[0219] - What is required to improve the existing Rel-18 MPQUIC steering functionality to support proxying of TCP traffic using MPQUIC?

[0220] - What is required to improve the existing Rel-18 MPQUIC steering functionality to support proxying of general IP traffic using MPQUIC?

[0221] - What is required to improve the existing Rel-18 MPQUIC steering function to support proxying of Ethernet traffic using MPQUIC?

[0222] The solution must be based on IETF protocols.

[0223] The new ATSSS features specified for UE may be applied to ATSSS-supported 5G-RGs upon approval by BBF and / or CableLabs.

[0224] In this regard, a new MPQUIC steering function can be defined.

[0225] - CONNECT-IP-based multipath QUIC-IP (MPQUIC-IP) steering function that tunnels IP packets between a client (UE) and a proxy (UPF) using HTTP / 3 over MPQUIC

[0226] - CONNECT-Ethernet-based MPQUIC-E (Multipath QUIC-IP) steering function that proxies Ethernet frames between a client (UE) and a proxy (UPF) using HTTP / 3 over MPQUIC

[0227] The operation of the MPQUIC-E function is based on the IETF draft-ietf-masque-connect-ethernet "Ethernet proxying over HTTP," which specifies how to transmit Ethernet traffic between a client (UE) and a proxy (UPF) using the RFC 9114 HTTP / 3 protocol.

[0228] The MPQUIC-E function can be enabled when the MA PDU session type is Ethernet. When the MPQUIC-E function is enabled for an Ethernet type PDU session, the SMF can indicate the PDU session type as IP in the N2 information to the NG-RAN.

[0229] If the PDU session type is "Ethernet":

[0230] - If the steering function parameter in the MA PDU session control information of the received PCC rule is set to only MPQUIC-E, the SMF may provide the NG-RAN with the PDU session type as "IP" in the N2 SM information. When only the MPQUIC-E function is enabled for the MA PDU session, the packets exchanged between the UE and the UPF are IP packets using "MPQUIC link-by-link multipath" addresses / prefixes (e.g., the (R)AN transmits IP packets between the UE and the UPF). The PDU session type IP may be provided to the (R)AN so that the NG-RAN can apply ROHC.

[0231] - If the steering function parameter in the MA PDU session control information of the received PCC rule is set only to ATSSS-LL, the PDU session type "Ethernet" may be provided in the N2 SM information.

[0232] Only one of the ATSSS-LL or MPQUIC-E functions can be enabled for the same Ethernet MA PDU session.

[0233] When using MPQUIC-E, Ethernet packets can be encapsulated into IP packets and transmitted via the QUIC protocol. Then, even though the session type associated with the packet is Ethernet, the base station receives an IP (Internet Protocol) packet.

[0234] Problems may occur when a base station performs Ethernet header compression based on the PDU session type. To prevent this, the network can indicate (transmit / configure) the PDU session type to the base station as an IP type. Then, the base station can support ROHC (header compression).

[0235] According to the above, when using MPQUIC-E, SMF can set the PDU Session Type to IP in NG-RAN.

[0236] Generally, to establish a PDU session, the terminal may request the establishment of a PDU session for a supported IP version (e.g., IPv4 (Internet Protocol version 4), IPv6 (Internet Protocol version 6), IPv4v6). During the PDU session establishment process, the network may indicate the type of PDU session to the base station (NG-RAN).

[0237] For example, a terminal requesting the establishment of a PDU session for IPv4v6 may mean that the terminal supports both IPv4 and IPv6.

[0238] For example, a terminal that supports only IPv4 requests the establishment of a PDU session for IPv4 and does not request the establishment of a PDU session for IPv6.

[0239] However, in the case of a PDU session for Ethernet, the terminal can indicate the PDU session type as Ethernet in the PDU session establishment request. In this case, the network cannot know the IP versions supported by the terminal (e.g., IPv4, IPv6, IPv4v6). Therefore, the network cannot accurately determine the type of PDU session to display to the base station (NG-RAN) during the PDU session establishment process.

[0240] When the MPQUIC-E function is enabled for an Ethernet type PDU session, the SMF indicates the PDU session type in the N2 information to the NG-RAN as an IP (e.g., IPv4, IPv6, IPv4v6). However, as mentioned above, this is problematic because the SMF cannot determine the IP version (e.g., IPv4, IPv6, IPv4v6) supported by the terminal.

[0241] In this regard, when allocating MPQUIC proxy addresses for MPQUIC-E, the question arises as to which IP version (e.g., IPv4, IPv6, IPv4v6 (meaning that both IPv4 and IPv6 addresses must be allocated)) address should be used.

[0242] In this specification, a method for supporting header compression when using MPQUIC-E for Ethernet type PDU sessions may be proposed.

[0243] The method proposed in this specification may be composed of a combination of one or more of the operations / configurations / steps described below.

[0244] In this specification, the terms User Equipment (UE) and terminal are used interchangeably. Either of these expressions may be replaced with the other.

[0245] In this specification, base station, RAN, and NG-RAN are used interchangeably. Any of these expressions may be replaced with another.

[0246] In this specification, IPv4v6 may mean both IPv4 and IPv6.

[0247] I. Method based on network configuration

[0248] This method allocates IP addresses for MPQUIC-E based on information pre-configured in the network.

[0249] In relation to this method, it can be assumed that a terminal supporting MPQUIC-E can support both IPv4 and IPv6.

[0250] For example, since the terminal supports all IP versions, the network can select the desired IP version and assign MPQUIC-related information (e.g., MPQUIC proxy address, MPQUIC link-specific multipath address / prefix).

[0251] For example, an address may be assigned based on the IP version set by the operator.

[0252] When using MPQUIC-E with SMF or UPF, the IP version to be used can be pre-configured.

[0253] If the above information (which IP version should be used when using MPQUIC-E) is configured in the SMF, the SMF can inform the UPF which IP version should be used when requesting the MPQUIC-E usage setting for a specific PDU session.

[0254] If the above information (which IP version should be used when using MPQUIC-E) is configured in the UPF, and the UPF receives a request from the SMF to configure MPQUIC-E usage for a specific PDU session, the UPF can assign MPQUIC-related information (e.g., MPQUIC proxy address, MPQUIC link-specific multipath address / prefix) based on this.

[0255] The information set by the operator in SMF / UPF may also be set according to a combination of DNN and / or S-NSSAI.

[0256] I-1. First Embodiment: Configuration-based MPQUIC-E Proxy Address Assignment

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

[0258] FIG. 8 illustrates an example of a configuration-based MPQUIC-E proxy address allocation procedure according to the disclosure of the present specification.

[0259] 1) Step 1

[0260] The terminal can perform the registration procedure.

[0261] In relation to the relevant procedure, the procedure in TS 23.502 v19.1.0 clause 4.2.2.2.2 may be applied.

[0262] 2) Step 2

[0263] The terminal may decide to use an MA PDU session. This decision may be based on a URSP rule set on the terminal.

[0264] The terminal can transmit a PDU Session Establishment Request message. In this case, the terminal can include the PDU Session Establishment Request message in a UL NAS Transport message and transmit it. In this case, the terminal can set the request type of the UL NAS Transport message to "MA PDU Request" and transmit the DNN and / or S-NSSAI together.

[0265] In addition, the terminal can set the PDU session type of the PDU session establishment request message to "Ethernet" and transmit it.

[0266] 3) Step 3

[0267] The AMF can transmit the PDU session establishment request message sent by the terminal to the SMF.

[0268] 4) Step 4

[0269] SMF can establish the SM Policy Association with PCF.

[0270] In this process, SMF can decide to generate an MA PDU session using MPQUIC-E based on the PCC rule received from PCF.

[0271] 5) Step 5

[0272] SMF can perform the N4 Session Establishment process with UPF.

[0273] At this time, SMF can send an N4 Session Establishment Request to UPF, set the PDU session type to Ethernet, and indicate that MPQUIC-E must be used.

[0274] For example, SMF can include MPQUIC Control Information indicating that CONNECT-Ethernet should be used in the 'Provide ATSSS Control Information' of the N4 session establishment request.

[0275] - i. (When configured in SMF) If the operator has configured in the SMF which IP type address to use, the SMF can also inform the UPF which IP type to use. Based on this, the UPF can allocate MPQUIC-related information for MPQUIC-E (e.g., MPQUIC proxy address, MPQUIC link-specific multipath address / prefix). The UPF can inform the SMF of the allocated MPQUIC-related information (e.g., MPQUIC proxy address, MPQUIC link-specific multipath address / prefix).

[0276] - ii. (When configured in UPF) If the operator configures in UPF which IP type address to use, UPF can determine which IP type address (e.g., IPv4 address, IPv6 address, or both IPv4 and IPv6 addresses) to use based on the local configuration. Based on this, UPF can allocate MPQUIC-related information for MPQUIC-E (e.g., MPQUIC proxy address, MPQUIC link-specific multipath address / prefix). UPF can notify SMF of the allocated MPQUIC-related information (e.g., MPQUIC proxy address, MPQUIC link-specific multipath address / prefix).

[0277] If MPQUIC-E is enabled for a PDU session (Ethernet type PDU session), UPF can assign MPQUIC-related information (e.g., MPQUIC proxy address, MPQUIC link-specific multipath address / prefix) including IP version addresses (IPv4 address and / or IPv6 address).

[0278] If MPQUIC-E is enabled for a PDU session (Ethernet type PDU session, session for Ethernet), the UPF can send MPQUIC-related information (e.g., MPQUIC proxy address, MPQUIC link-specific multipath address / prefix) including the IP version address (IPv4 address and / or IPv6 address) to the SMF.

[0279] 6) Step 6

[0280] To notify the terminal of MPQUIC-related information (e.g., MPQUIC proxy address, MPQUIC link-specific multipath address / prefix) received from the UPF, the SMF may include the information received from the UPF in the PDU session establishment acknowledgment message.

[0281] In addition, to support ROHC for MPQUIC-E packets, based on the MPQUIC IP information assigned by the UPF, the SMF can determine the PDU session type to be included in the N2 SM information and include it in the N2 SM information and transmit it to the (R)AN.

[0282] For example, if the MPQUIC-related information received from the UPF (e.g., MPQUIC proxy address, MPQUIC link-specific multipath address / prefix) is IPv4, the SMF can set the PDU session type to IPv4 and transmit it to the base station (e.g., NG-RAN).

[0283] For example, if the MPQUIC-related information received from the UPF (e.g., MPQUIC proxy address, MPQUIC link-specific multipath address / prefix) is IPv6, the SMF can set the PDU session type to IPv6 and transmit it to the base station (e.g., NG-RAN).

[0284] For example, if the MPQUIC-related information received from the UPF (e.g., MPQUIC proxy address, MPQUIC link-specific multipath address / prefix) is IPv4 and / or IPv6, the SMF can set the PDU session type to IPv4, IPv6, or IPv4v6 and transmit it to the base station (e.g., NG-RAN).

[0285] For example, based on the IP version of the assigned MPQUIC-related information (e.g., MPQUIC proxy address, MPQUIC link-specific multipath address / prefix), the SMF can set the PDU session type to IPv4, IPv6, or IPv4v6 and transmit it to the base station (e.g., NG-RAN).

[0286] The SMF can transmit N2 SM information (and / or PDU session acknowledgment message) including the aforementioned information to the AMF.

[0287] 7) Step 7

[0288] The AMF can transmit the PDU session establishment acknowledgment message and N2 SM information transmitted by the SMF to the base station.

[0289] 8) Step 8

[0290] The base station can transmit the PDU session establishment approval message received from the AMF to the terminal.

[0291] The base station can create a PDU session context and allocate related resources based on N2 SM information.

[0292] The PDU session establishment acknowledgment message received by the terminal may include MPQUIC-related information (e.g., MPQUIC proxy address, MPQUIC link-specific multipath address / prefix).

[0293] The terminal can receive MPQUIC-related information (e.g., MPQUIC proxy address, MPQUIC link-specific multipath address / prefix) regarding (or including) an IP version (e.g., IPv4, IPv6, IPv4v6) from the network. Based on this, the terminal can select an IP address version based on its capability.

[0294] Based on the selected IP address version, the terminal can perform a procedure to establish a QUIC connection with an MPQUIC proxy server. In this case, if both 3GPP access and non-3GPP access are available, the terminal can establish a QUIC connection for both 3GPP access and non-3GPP access by using an 'MPQUIC link-specific multipath address / prefix' suitable for each access.

[0295] 9) Step 9

[0296] The base station can transmit a response to the N2 SM information to the AMF.

[0297] 10) Step 10

[0298] The AMF can transmit messages related to N2 SM information received from the base station to the SMF.

[0299] AMF can send a request to update the SM context for the PDU session to SMF.

[0300] 11) Step 11

[0301] The SMF can update GTP-U tunneling information between the base station and the UPF by performing a modification procedure with the UPF and N4.

[0302] 12) Step 12

[0303] SMF can send a response to AMF.

[0304] Subsequently, based on MPQUIC-related information (e.g., MPQUIC proxy address, MPQUIC link-specific multipath address / prefix) in the PDU Session Establishment Accept message, the terminal can establish a QUIC connection with an MPQUIC proxy in the UPF and transmit data.

[0305] Since all Ethernet packets are transmitted via QUIC, they can be encapsulated into IP packets and transmitted. The base station can perform ROHC because the PDU session type is set to IPv4, IPv6, or IPv4v6 by the SMF.

[0306] II. Method by which a terminal transmits information on the IP capabilities it supports

[0307] This method involves transmitting capability information regarding the IP versions supported by the terminal along with the creation of an MA PDU session for Ethernet if the terminal supports MPQUIC-E.

[0308] The capability information above may differ from the actual IP capabilities supported by the terminal. For example, even if the terminal has the capability to create PDU sessions that support IPv4, IPv6, and IPv4v6 (both IPv4 and IPv6), the IP capabilities supported by MPQUIC-E may be only IPv4 and / or IPv6. For example, even if the terminal has the capability to create PDU sessions that support IPv4v6 (both IPv4 and IPv6), the terminal may support only IPv4 or IPv6 in MPQUIC-E.

[0309] The terminal can include its IP capability information in a PDU session establishment request message and send it to the SMF.

[0310] The above IP capability information may be information regarding the IP version supported by the terminal, independent of MPQUIC-E. Alternatively, the above IP capability information may be for MPQUIC-E.

[0311] Based on the capability information, SMF may send a message to UPF containing at least one of the following:

[0312] - Instruct to use MPQUIC-E

[0313] - Request allocation of MPQUIC-related information for MPQUIC-E (e.g., MPQUIC proxy address, MPQUIC link-specific multipath address / prefix)

[0314] - Request the assignment of MPQUIC proxy information (MPQUIC proxy address / ports)

[0315] - IP capability information for MPQUIC-E supported by the terminal

[0316] Based on this, UPF can assign an address / prefix of the IP version supported by the terminal.

[0317] UPF can assign MPQUIC-related information (e.g., MPQUIC proxy address, MPQUIC link-specific multipath address / prefix) and MPQUIC proxy information (MPQUIC proxy address / ports).

[0318] UPF can transmit the allocated information to SMF.

[0319] Based on MPQUIC-related information (e.g., MPQUIC proxy address, MPQUIC link-specific multipath address / prefix) and MPQUIC proxy information (MPQUIC proxy address / ports) assigned by the UPF, the SMF can identify which IP version is used by MPQUIC-E. Based on this, when sending N2 information to the NG-RAN, the SMF can set the PDU session type to the IP version used by MPQUIC-E and transmit it. Through this, the NG-RAN can perform ROHC for MPQUIC-E.

[0320] II-1. Second Embodiment: MPQUIC-E Proxy Address Allocation Based on UE Capability Reporting

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

[0322] The procedure for assigning proxy addresses based on UE capability reporting MPQUIC-E will be described later with reference to Fig. 8.

[0323] 1) Step 1

[0324] The terminal can perform the registration procedure.

[0325] In relation to the relevant procedure, the procedure in TS 23.502 v19.1.0 clause 4.2.2.2.2 may be applied.

[0326] 2) Step 2

[0327] The terminal may decide to use an MA PDU session. This decision may be based on a URSP rule set on the terminal.

[0328] The terminal can transmit a PDU Session Establishment Request message. In this case, the terminal can include the PDU Session Establishment Request message in a UL NAS Transport message and transmit it. In this case, the terminal can set the request type of the UL NAS Transport message to "MA PDU Request" and transmit the DNN and / or S-NSSAI together.

[0329] In addition, the terminal can transmit the PDU session type of the PDU session establishment request message by setting it to "Ethernet".

[0330] A PDU Session Establishment Request message transmitted by a terminal may include IP version capability information that the terminal can use (support).

[0331] 3) Step 3

[0332] The AMF can transmit the PDU session establishment request message sent by the terminal to the SMF.

[0333] 4) Step 4

[0334] SMF can establish the SM Policy Association with PCF.

[0335] In this process, SMF can decide to generate an MA PDU session using MPQUIC-E based on the PCC rule received from PCF.

[0336] 5) Step 5

[0337] SMF can perform the N4 Session Establishment process with UPF.

[0338] At this time, SMF can send an N4 Session Establishment Request to UPF, set the PDU session type to Ethernet, and indicate that MPQUIC-E must be used.

[0339] For example, SMF can include MPQUIC Control Information indicating that CONNECT-Ethernet should be used in the 'Provide ATSSS Control Information' of the N4 session establishment request.

[0340] In this case, the SMF can transmit the capabilities transmitted by the terminal to the UPF. Alternatively, the SMF can determine which IP version to use based on the terminal's capabilities and transmit it to the UPF.

[0341] Based on this, the UPF can allocate MPQUIC-related information for MPQUIC-E (e.g., MPQUIC proxy address, MPQUIC link-specific multipath address / prefix). The UPF can notify the SMF of the allocated MPQUIC-related information (e.g., MPQUIC proxy address, MPQUIC link-specific multipath address / prefix).

[0342] If MPQUIC-E is enabled for a PDU session (Ethernet type PDU session, session for Ethernet), the UPF can send MPQUIC-related information (e.g., MPQUIC proxy address, MPQUIC link-specific multipath address / prefix) including the IP version address (IPv4 address and / or IPv6 address) to the SMF.

[0343] 6-12) Steps 6 through 12

[0344] Steps 6 to 12 of FIGS. 8 and FIGS. 9 of the first embodiment described above may be applied.

[0345] III. Examples to which the disclosure of this specification applies

[0346] III-1. MPQUIC-based functions

[0347] MPQUIC-based steering functions can be supported as follows.

[0348] (1)

[0349] The MPQUIC-E function can be enabled when the MA PDU session type is Ethernet. In this case, the UE can transmit the IP capability for MPQUIC-E when sending the PDU session setup request message.

[0350] SMF can provide the UE's capabilities to UPF, enabling UPF to allocate "MPQUIC link-specific multipath" addresses / prefixes and MPQUIC proxy information by taking the UE's capabilities into account.

[0351] When MPQUIC-E functionality is enabled for an Ethernet type PDU session, based on the assigned IP type (e.g., IPv4, IPv6, both IPv4 and IPv6) of the “MPQUIC link-specific multipath” address / prefix and MPQUIC proxy information, the SMF can indicate to the NG-RAN in the N2 information that the PDU session type is IPv4, IPv6, or IPv4v6.

[0352] For example, SMF can indicate the PDU session type as IPv4, IPv6, or IPv4v6 in the N2 information transmitted to NG-RAN.

[0353] (2)

[0354] The MPQUIC-E function can be enabled when the MA PDU session type is Ethernet. In this case, the UPF can assign "MPQUIC link-specific multipath" addresses / prefixes and MPQUIC proxy information based on the local configuration.

[0355] When MPQUIC-E functionality is enabled for an Ethernet type PDU session, based on the assigned IP type (e.g., IPv4, IPv6, both IPv4 and IPv6) of the “MPQUIC link-specific multipath” address / prefix and MPQUIC proxy information, the SMF can indicate to the NG-RAN in the N2 information that the PDU session type is IPv4, IPv6, or IPv4v6.

[0356] For example, SMF can indicate the PDU session type as IPv4, IPv6, or IPv4v6 in the N2 information transmitted to NG-RAN.

[0357] In the case of MPQUIE-E, since it is assumed that the UE supports all IP types (IPv4, IPv6, IPv4v6 (both IPv4 and IPv6)), UPF can select any IP address version based on the local configuration.

[0358] III-2. Roaming and Non-Roaming Using Local Breakouts

[0359] When the UE is not roaming, or when the UE is roaming and the PDU Session Anchor (PSA) is located in the VPLMN, the MA PDU session setup signal flow is based on the signal flow of TS23.502 v19.1.0 Figure 4.3.2.2.1-1. The differences will be described later. This will be explained with reference to Figures 6 and 7.

[0360] In step 1 of FIG. 6, if the terminal supports MPQUIC-E, the terminal may include IP version capability information for MPQUIC-E in the PDU session establishment request message. The IP version capability information of the terminal may be transmitted to the SMF via the AMF.

[0361] SMF can establish user plane resources through access (e.g., 3GPP access) to which a PDU session setup request is transmitted.

[0362] In step 10 of Fig. 6, if the MPQUIC-E function is supported for an MA PDU session of the Ethernet PDU session type, the SMF instructs the UPF to enable the MPQUIC-E function for the corresponding MA PDU session and can also provide the IP version information of the UE received from the UE.

[0363] In step 10a of Fig. 6, if a message sent from the SMF instructs the UPF to enable MPQUIC-UDP and / or MPQUIC-IP or MPQUIC-E steering functions, the UPF may assign an "MPQUIC link-specific multipath" address / prefix to the UE. In the case of MPQUIC-E, the UPF may consider the UE's IP version capability when assigning the "MPQUIC link-specific multipath" address / prefix and MPQUIC proxy information. In step 10b, the UPF may send the "MPQUIC link-specific multipath" address / prefix and MPQUIC proxy information corresponding to the enabled MPQUIC steering function to the SMF.

[0364] In step 11 of Fig. 6, if the PDU session type is "Ethernet":

[0365] - Based on the IP version of the '"MPQUIC link-specific multipath" address / prefix and MPQUIC proxy information' assigned to the UPF, if the steering function parameter in the MA PDU session control information of the received PCC rule is set only to MPQUIC-E, the SMF may provide the NG-RAN with the PDU session type as IPv4, IPv6, or IPv4v6 in the N2 SM information. For example, the SMF may indicate the PDU session type as IPv4, IPv6, or IPv4v6 in the N2 SM information transmitted to the NG-RAN. To enable the NG-RAN to apply ROHX, the PDU session type IPv4, IPv6, or IPv4v6 may be provided to the (R)AN.

[0366] According to the disclosure of this specification, a network can identify the IP version used in MPQUIC-E and transmit it to NG-RAN. Through this, NG-RAN can support ROHC for MPQUIC-E packets.

[0367] In accordance with the disclosure of the present specification, the following operations may be performed:

[0368] - The terminal can provide information on the IP version capabilities it supports for MPQUIC-E in the PDU session establishment request message.

[0369] - The SMF informs the UPF of the IP version capability information uploaded by the UE, allowing the UPF to allocate 'MPQUIC link-specific IP addresses / prefixes, MPQUIC proxy information' considering the IP versions supported by the UE.

[0370] Based on the 'MPQUIC link-specific IP addresses / prefixes, MPQUIC proxy information' assigned by the UPF, the SMF can determine the PDU session type to be transmitted to the base station and transmit it to the base station.

[0371] IV. Method for assigning based on network settings without supporting all terminal IP versions

[0372] This method is similar to the aforementioned method I, but it assigns MPQUIC proxy addresses and 'MPQUIC link-specific multipath' addresses / prefixes based on network settings even if the terminal does not support all IP versions.

[0373] For example, if a terminal supports only IPv4, the network may assign an MPQUIC proxy address, or 'MPQUIC link-specific multipath' address / prefix, that includes IPv4 and / or IPv6 based on the configuration. Based on this, the terminal can establish connections only to IPv4 MPQUIC proxies due to its capability.

[0374] If a terminal does not establish a connection until the timer preset in the UPF (or the timer set by the SMF) expires, the UPF may release resources for MPQUIC proxy addresses assigned to IPv6 addresses, and 'MPQUIC link-specific multipath' addresses / prefixes. The UPF may also notify the SMF of this.

[0375] As another example, the terminal may support only IPv4 while the network supports only IPv6. In this case, the network can only assign MPQUIC proxy addresses and 'MPQUIC link-specific multipath' addresses / prefixes assigned to IPv6 addresses to the terminal. Consequently, since the terminal supports only IPv4, it becomes unable to establish an MPQUIC connection. Based on a timer, the UPF can release resources for the MPQUIC proxy addresses and 'MPQUIC link-specific multipath' addresses / prefixes assigned to IPv6 addresses and notify the SMF that the terminal did not establish a connection. Based on this, the SMF can determine that MPQUIC cannot be used due to the terminal's IP capability. Based on this, the SMF can perform the release of the MA PDU session. During this process, the SMF can notify the terminal that the MA PDU session cannot be used due to a capability mismatch. For example, the SMF can transmit a specific cause to the terminal. In contrast, the SMF may simply notify the terminal that the MA PDU session is unavailable (instead of notifying it that the MA PDU session is unavailable due to a capability mismatch) or, more specifically, that only specific IP versions are supported.

[0376] To prevent such mismatches (e.g., capability mismatch), the network can always assign IPv4 and / or MPQUIC proxy addresses, and 'MPQUIC link-specific multipath' addresses / prefixes. Based on this, the terminal can establish a connection according to its capability. In this case, the terminal may establish connections for both IPv4 and IPv6, or establish a QUIC connection only for the specific IP version required, depending on its capability.

[0377] V. Examples to which the disclosure of this specification applies

[0378] V-1. MPQUIC-based functions

[0379] The MPQUIC-E function can be enabled when the MA PDU session type is Ethernet. In this case, based on the local configuration, the UPF can assign the same IP type to the "MPQUIC link-specific multipath" address / prefix and the MPQUIC proxy information.

[0380] When MPQUIC-E functionality is enabled for an Ethernet type PDU session, based on the assigned IP type (e.g., IPv4, IPv6, both IPv4 and IPv6) of the “MPQUIC link-specific multipath” address / prefix and MPQUIC proxy information, the SMF can indicate to the NG-RAN in the N2 information that the PDU session type is IPv4, IPv6, or IPv4v6.

[0381] For example, SMF can indicate the PDU session type as IPv4, IPv6, or IPv4v6 in the N2 information transmitted to NG-RAN.

[0382] In the case of MPQUIE-E, since it is assumed that the UE supports all IP types (IPv4, IPv6, IPv4v6 (both IPv4 and IPv6)), UPF can select any IP address version based on the local configuration.

[0383] If the terminal receives an MPQUIC link-specific multipath address / prefix and MPQUIC proxy information, the terminal may initiate the establishment of an MPQUIC connection based on its IP capabilities. Based on a preset timer, the UPF may detect that the terminal has not established an MPQUIC connection. Then, the UPF may report to the SMF that the MPQUIC connection was not established. Based on this report, the SMF may trigger the PDU session release procedure.

[0384] V-2. Roaming and Non-Roaming Using Local Breakouts

[0385] When the UE is not roaming, or when the UE is roaming and the PDU Session Anchor (PSA) is located in the VPLMN, the MA PDU session setup signal flow is based on the signal flow of TS23.502 v19.1.0 Figure 4.3.2.2.1-1. The differences will be described later. This will be explained with reference to Figures 6 and 7.

[0386] In step 10a of FIG. 6, if the UPF has enabled the MPQUIC-E steering function, the UPF may start a locally configured timer to detect whether the terminal establishes an MPQUIC connection. If the terminal does not establish an MPQUIC connection, the UPF may report to the SMF that the MPQUIC connection was not established. Based on this report, the SMF may release the PDU session.

[0387] If UPF has assigned MPQUIC proxies for IPv4 and IPv6 respectively, UPF can start a timer for each proxy. Based on this, for a specific IP type, UPF can determine that the terminal is not establishing a connection and report this to SMF. Based on this, SMF can recognize that there is no QUIC connection only for the said specific IP type. Based on this, SMF can change the PDU session type and send (notify) it to NG-RAN.

[0388] For example, the terminal may have established a QUIC connection only for IPv4 and not for IPv6. In this case, the SMF can update the PDU session type to IPv4 instead of the IPv4v6 previously sent to the NG-RAN. For example, the SMF can change the PDU session type to IPv4 and send it to the NG-RAN.

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

[0390] FIG. 9 illustrates the procedure of SMF for the disclosure of the present specification.

[0391] 1. An SMF (Session Management Function) can receive MPQUIC-E (Multipath QUIC-Ethernet) related information from a UPF (User Plane Function) that includes at least one of an IPv4 (Internet Protocol version 4) address or an IPv6 address.

[0392] 2. Based on the above MPQUIC-E related information, the above SMF can transmit type information of a PDU (Protocol Data Unit) session for Ethernet to the base station.

[0393] The above type information may be at least one of IPv4, IPv6, or IPv4v6.

[0394] MPQUIC-E can be enabled for the above PDU session.

[0395] The above MPQUIC-E related information may include: MPQUIC proxy information; and the address and / or prefix of an 'MPQUIC link-specific multipath'.

[0396] The above SMF can send a command to the above UPF to enable the MPQUIC-E function for the above PDU session.

[0397] The above SMF can receive capability information of the UE (User Equipment) from the UE (User Equipment) AMF (Access and Mobility management Function).

[0398] The above capability information may include information related to the IP version supported by the UE.

[0399] The step of transmitting the above activation instruction may include the step of the SMF transmitting information related to the IP version to the UPF.

[0400] The above MPQUIC-E related information may be based on information related to the above IP version.

[0401] The step of transmitting the above activation instruction may include: the step of the SMF transmitting information about the IP version based on the local configuration.

[0402] The above MPQUIC-E related information may be information assigned by the UPF based on the local settings configured in the UPF.

[0403] The above base station may be NG-RAN (New Generation Radio Access Network) or 5G-AN.

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

[0405] FIG. 10 illustrates the procedure of the UE for the disclosure of the present specification.

[0406] 1. A step in which the UE receives MPQUIC-E related information for at least one of an IPv4 address or an IPv6 address from a network; and

[0407] 2. Based on the above MPQUIC-E related information, the UE may select the version of the IP address as i) IPv4, ii) IPv6, or iii) both IPv4 and IPv6.

[0408] The above MPQUIC-E related information may include: MPQUIC proxy information; and the address and / or prefix of an 'MPQUIC link-specific multipath'.

[0409] The above UE can send a message requesting the establishment of a PDU session to the above network.

[0410] The above PDU session may be a session for Ethernet.

[0411] MPQUIC-E can be enabled for the above PDU session.

[0412] The above establishment request message may include capability information of the UE.

[0413] The above capability information may include information related to the IP version supported by the UE.

[0414] The step of receiving the above MPQUIC-E related information can be performed based on the capability information.

[0415] The step of receiving the above MPQUIC-E related information can be received by the UE through an establishment approval message for the above PDU session.

[0416] Hereinafter, a device for performing communication according to some embodiments of the present specification will be described.

[0417] For example, the device may include a processor, a transceiver, and memory.

[0418] For example, the processor can be configured to be operablely coupled with memory and the processor.

[0419] The operation performed by the above processor includes: a step in which a Session Management Function (SMF) receives MPQUIC-E (Multipath QUIC-Ethernet) related information from a User Plane Function (UPF) that includes at least one of an IPv4 (Internet Protocol version 4) address or an IPv6 address; and a step in which, based on the MPQUIC-E related information, the SMF transmits type information of a PDU (Protocol Data Unit) session for Ethernet to a base station, wherein the type information is at least one of IPv4, IPv6, or IPv4v6, and MPQUIC-E can be enabled for the PDU session.

[0420] Hereinafter, a processor of a device for providing communication according to some embodiments of the present specification will be described.

[0421] The operation performed by the processor includes the step of the SMF (Session Management Function) receiving MPQUIC-E (Multipath QUIC-Ethernet) related information from the UPF (User Plane Function) that includes at least one of an IPv4 (Internet Protocol version 4) address or an IPv6 address; and the step of the SMF transmitting type information of a PDU (Protocol Data Unit) session for Ethernet to a base station based on the MPQUIC-E related information, wherein the type information is at least one of IPv4, IPv6, or IPv4v6, and MPQUIC-E can be enabled for the PDU session.

[0422] Hereinafter, a non-volatile computer-readable medium storing one or more instructions for providing mobile communication according to some embodiments of the present specification will be described.

[0423] According to some embodiments of the present disclosure, the technical features of the present disclosure may be directly implemented in hardware, software executed by a processor, or a combination of both. For example, a method performed by a wireless device in wireless communication may be implemented in hardware, software, firmware, or any combination thereof. For example, software may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or other storage media.

[0424] In some examples, storage media are coupled to the processor so that the processor can read information from the storage media. Alternatively, the storage media can be integrated into the processor. The processor and storage media can reside in an ASIC. In other examples, the processor and storage media can reside as separate components.

[0425] Computer-readable media may include tangible and non-volatile computer-readable storage media.

[0426] For example, non-volatile computer-readable media may include RAM (Random Access Memory) such as SDRAM (Synchronization Dynamic Random Access Memory), ROM (Read-Only Memory), and NVRAM (Non-Volatile Random Access Memory); read-only memory (EEPROM); flash memory; magnetic or optical data storage media; or other media that can be used to store instructions or data structures. Non-volatile computer-readable media may also include combinations of the above.

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

[0428] According to some embodiments of the present disclosure, a non-transient computer-readable medium stores one or more instructions thereon. The stored one or more instructions can be executed by a processor of a base station.

[0429] One or more stored commands include the step of the SMF (Session Management Function) receiving MPQUIC-E (Multipath QUIC-Ethernet) related information from the UPF (User Plane Function) that includes at least one of an IPv4 (Internet Protocol version 4) address or an IPv6 address; and the step of the SMF transmitting type information of a PDU (Protocol Data Unit) session for Ethernet to a base station based on the MPQUIC-E related information, wherein the type information is at least one of IPv4, IPv6, or IPv4v6, and MPQUIC-E can be enabled for the PDU session.

[0430] Hereinafter, a non-volatile computer-readable medium storing one or more instructions for providing mobile communication according to some embodiments of the present specification will be described.

[0431] This specification may have various effects.

[0432] For example, I-SMF can be reused through the procedure disclosed in this specification.

[0433] The effects obtainable through the specific examples of this specification are not limited to those listed above. For example, there may be various technical effects that a person with ordinary skill in the related art can understand or derive 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.

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

Claims

1. As a method, A step in which an SMF (Session Management Function) receives MPQUIC-E (Multipath QUIC-Ethernet) related information from a UPF (User Plane Function) that includes at least one of an IPv4 (Internet Protocol version 4) address or an IPv6 address; and Based on the above MPQUIC-E related information, the above SMF includes the step of transmitting type information of a PDU (Protocol Data Unit) session for Ethernet to a base station. The above type information is at least one of IPv4, IPv6, or IPv4v6, and A method in which MPQUIC-E is enabled for the above PDU session.

2. In Paragraph 1, The above MPQUIC-E related information is: MPQUIC proxy information; and A method including the address and / or prefix of 'MPQUIC link-specific multipath'.

3. In Paragraph 1 or 2, A method further comprising the step of the above SMF transmitting a command to the above UPF to enable the MPQUIC-E function for the above PDU session.

4. In Paragraph 3, The above SMF further includes the step of receiving capability information of the UE from the UE (User Equipment), and The above capability information includes information related to the IP version supported by the UE, and The step of transmitting the above activation instruction includes: the step of the SMF transmitting information related to the IP version to the UPF, and The above MPQUIC-E related information is a method based on the information related to the above IP version.

5. In Paragraph 3, The step of transmitting the above activation instruction includes: the step of the SMF transmitting information about the IP version based on the local configuration.

6. In any one of paragraphs 1 through 5, A method in which the above MPQUIC-E related information is information assigned by the UPF based on local settings set in the UPF.

7. In any one of paragraphs 1 through 6, The above base station is a method in which it is an NG-RAN (New Generation Radio Access Network) or 5G-AN.

8. As a method, A step in which a UE receives MPQUIC-E related information for at least one of an IPv4 address or an IPv6 address from a network; and A method comprising the step of the UE selecting, based on the above MPQUIC-E related information, a version of an IP address as i) IPv4, ii) IPv6, or iii) both IPv4 and IPv6.

9. In Paragraph 8, The above MPQUIC-E related information is: MPQUIC proxy information; and A method including the address and / or prefix of 'MPQUIC link-specific multipath'.

10. In Paragraph 8 or 9, The above UE further includes the step of sending a request message to establish a PDU session to the network, and The above PDU session is a session for Ethernet, and A method in which MPQUIC-E is enabled for the above PDU session.

11. In Paragraph 10, The above establishment request message includes capability information of the above UE, and The above capability information includes information related to the IP version supported by the UE, and The step of receiving the above MPQUIC-E related information is a method performed based on the above capability information.

12. In Paragraph 10, The step of receiving the above MPQUIC-E related information is: a method received by the UE through an establishment approval message for the above PDU session.

13. In any one of paragraphs 8 through 12, A method further comprising the step of the UE establishing a QUIC connection with an MPQUIC proxy server based on the version of the selected IP address.

14. As an SMF, At least one transmitter / receiver; It includes at least one processor, The operation performed by the above at least one processor is an SMF that is a method according to any one of claims 1 to 7. 15.UE, At least one transmitter / receiver; It includes at least one processor, The operation performed by the above-mentioned at least one processor is a method according to any one of claims 8 to 13, UE.

16. As an apparatus in mobile communication, At least one processor; and It includes at least one memory that stores instructions and is operablely electrically connected to at least one processor, and A device in which the operation performed based on the execution of the above instruction by the at least one processor is a method according to any one of claims 1 to 7.

17. A non-volatile computer-readable storage medium that records instructions, A non-volatile computer-readable storage medium in which, when the above instructions are executed by one or more processors, the operation that causes the one or more processors to perform is a method according to any one of claims 1 to 7.

Images