Communication related to mobile base station

Abstract

The present disclosure provides a method. The method comprises the steps of: transmitting a PDU session establishment request message to a network node related to a session; receiving a PDU session establishment accept message from the network node; transmitting, to the network node, a request message related to a PDU session; receiving, from the network node, a response message related to the PDU session; and receiving, from the network node, an NAS message including information related to QoS.

Description

Communications related to mobile base stations

[0001] This specification relates to mobile communications.

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

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

[0004] NR aims to be a single technology framework that addresses all deployment scenarios, usage scenarios, and requirements, including enhanced Mobile Broadband (eMBB), massive Machine Type Communications (mMTC), and Ultra-Reliable and Low Latency Communications (URLLC). NR must be inherently forward-compatible.

[0005] Discussions are underway to provide services to UEs based on their connection to mobile base stations. However, conventional technology has the problem of not effectively providing Quality of Service (QoS) to UEs connected to mobile base stations.

[0006] In one aspect, a method is provided. The method may include: transmitting a PDU session establishment request message to a network node associated with a session; receiving a PDU session establishment acceptance message from the network node; transmitting a request message associated with the PDU session to the network node; receiving a response message associated with the PDU session from the network node; and receiving an NAS message including information associated with QoS from the network node.

[0007] In another aspect, a device implementing the above method is provided.

[0008] In one aspect, a method is provided. The method may include: receiving a PDU session establishment request message from a mobile base station including a first UE; transmitting a PDU session establishment acceptance message to the mobile base station; receiving a request message related to the PDU session from the mobile base station; transmitting a response message related to the PDU session to the mobile base station via a base station serving the first UE; receiving a notification related to the QoS from the base station; and transmitting an NAS message including information related to the QoS to the mobile base station.

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

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

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

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

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

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

[0015] FIG. 7 is an example of an architecture for communication based on a mobile base station according to one embodiment of the disclosure of the present specification.

[0016] FIG. 8 is a first example of an architecture related to a mobile base station according to the disclosure of this specification.

[0017] FIG. 9 is a second example of an architecture related to a mobile base station according to the disclosure of this specification.

[0018] FIG. 10 is an example of PDU session resource setup according to the disclosure of this specification.

[0019] FIG. 11 is an example of PDU session resource modification according to the disclosure of this specification.

[0020] FIG. 12 is an example of a PDU session resource notification according to the disclosure of this specification.

[0021] FIG. 13 is a specific example of a procedure according to one embodiment of the disclosure of the present specification.

[0022] FIG. 14 illustrates an example of a procedure performed according to one embodiment of the disclosure of the present specification.

[0023] The following techniques, devices, and systems can be applied to various wireless multiple access systems. Examples of multiple access systems include Code Division Multiple Access (CDMA) systems, Frequency Division Multiple Access (FDMA) systems, Time Division Multiple Access (TDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Multi-Carrier Frequency Division Multiple Access (MC-FDMA) systems. CDMA can be implemented using wireless technologies such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA can be implemented using wireless technologies such as Global System for Mobile communications (GSM), General Packet Radio Service (GPRS), or Enhanced Data rates for GSM Evolution (EDGE). OFDMA can be implemented using wireless technologies such as IEEE (Institute of Electrical and Electronics Engineers) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, or Evolved UTRA (E-UTRA). UTRA is part of the Universal Mobile Telecommunications System (UMTS). 3GPP (3rd Generation Partnership Project) Long-Term Evolution (LTE) is part of E-UMTS (Evolved UMTS) that utilizes E-UTRA.3GPP LTE uses OFDMA in the downlink (DL) and SC-FDMA in the uplink (UL). Evolution of 3GPP LTE includes LTE-A (Advanced), LTE-A Pro, and / or 5G NR (New Radio).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0039] The wireless devices (100a to 100f) represent devices that perform communication using Radio Access Technology (RAT) (e.g., 5G NR or LTE) and may also be referred to as communication / wireless / 5G devices. The wireless devices (100a to 100f) may include, but are not limited to, a robot (100a), a vehicle (100b-1 and 100b-2), an extended reality (XR) device (100c), a portable device (100d), a home appliance (100e), an Internet-of-Things (IoT) device (100f), and an artificial intelligence (AI) device / server (400). For example, the vehicles may include vehicles having wireless communication capabilities, autonomous vehicles, and vehicles capable of performing vehicle-to-vehicle communication. The vehicles may include unmanned aerial vehicles (UAVs) (e.g., drones). XR devices may include AR (Augmented Reality) / VR (Virtual Reality) / MR (Mixed Reality) devices, and may be implemented in the form of HMD (Head-Mounted Device) and HUD (Head-Up Display) mounted on vehicles, televisions, smartphones, computers, wearable devices, home appliances, digital signs, vehicles, robots, etc. Portable devices may include smartphones, smart pads, wearable devices (e.g., smart watches or smart glasses), and computers (e.g., laptops). Home appliances may include TVs, refrigerators, and washing machines. IoT devices may include sensors and smart meters.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0053] The processor (102) may control the memory (104) and / or the transceiver (106) and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed herein. For example, the processor (102) may process information in the memory (104) to generate first information / signal and transmit a wireless signal including the first information / signal via the transceiver (106). The processor (102) may receive a wireless signal including second information / signal via the transceiver (106) and store information obtained by processing the second information / signal in the memory (104).

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

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

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

[0057] The processing chip (201) may include at least one processor, such as a processor (202), and at least one memory, such as a memory (204). Additionally and / or alternatively, the memory (204) may be located external to the processing chip (201).

[0058] The processor (202) may control the memory (204) and / or the transceiver (206) and may be configured to implement the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed herein. For example, the processor (202) may process information in the memory (204) to generate third information / signal and transmit a wireless signal including the third information / signal via the transceiver (206). The processor (202) may receive a wireless signal including fourth information / signal via the transceiver (206) and store information obtained by processing the fourth information / signal in the memory (204).

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

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

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

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

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

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

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

[0066] Although not illustrated in FIG. 2, the wireless device (100, 200) may further include additional components. The additional components (140) may be configured in various ways depending on the type of the wireless device (100, 200). For example, the additional components (140) may include at least one of a power unit / battery, an input / output (I / O) device (e.g., an audio I / O port, a video I / O port), a driving device, and a computing device. The additional components (140) may be connected to one or more processors (102, 202) via various technologies, such as a wired or wireless connection.

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

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

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

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

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

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

[0073] Memory (104) is operatively coupled to the processor (102) and stores various information for operating the processor (102). Memory (104) may include ROM, RAM, flash memory, memory cards, storage media, and / or other storage devices. When the implementation is implemented in software, the techniques described herein may be implemented using modules (e.g., procedures, functions, etc.) that perform the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed herein. The modules may be stored in memory (104) and executed by the processor (102). Memory (104) may be implemented within the processor (102) or external to the processor (102), in which case it may be communicatively coupled to the processor (102) via various methods known in the art.

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

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

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

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

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

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

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

[0081] - AUSF (Authentication Server Function)

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

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

[0084] - USDF (Unstructured Data Storage Function)

[0085] - NEF (Network Exposure Function)

[0086] - I-NEF (Intermediate NEF)

[0087] - NRF (Network Repository Function)

[0088] - NSSF (Network Slice Selection Function)

[0089] - PCF (Policy Control Function)

[0090] - SMF (Session Management Function)

[0091] - UDM (Unified Data Management)

[0092] - UDR (Unified Data Repository)

[0093] - UPF (User Plane Function)

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

[0095] - AF (Application Function)

[0096] - UE (User Equipment)

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

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

[0099] - NWDAF (Network Data Analytics Function)

[0100] - CHF (CHarging Function)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0130] Establishing a PDU session may involve:

[0131] - UE-initiated PDU session establishment procedure

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

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

[0134] - Network-triggered PDU session establishment procedure

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0151] (3) Step 3: If the AMF is not associated with an SMF for the PDU session ID provided by the UE (e.g., when the request type indicates "Initial Request"), the AMF invokes the Create SM Context request procedure (e.g., Nsmf_PDUSession_CreateSMContext Request). If the AMF is already associated with an SMF for the PDU session ID provided by the UE (e.g., when the request type indicates "Existing PDU Session"), the AMF invokes the Update SM Context request procedure (e.g., Nsmf_PDUSession_UpdateSMContext Request).

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

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

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

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

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

[0157] (5) Step 5: SMF sends a create SM context response message (e.g., Nsmf_PDUSession_CreateSMContext Response) or an update SM context response message (e.g., Nsmf_PDUSession_UpdateSMContext Response) to AMF according to the request received in step 3.

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

[0159] If the SMF decides not to accept the PDU session establishment, the SMF rejects the UE request by sending a NAS SM signal including the relevant SM rejection cause by responding to the AMF with an Nsmf_PDUSession_CreateSMContext Response. The SMF also indicates to the AMF that the PDU session ID is considered released and the SMF proceeds to step 20 below, aborting the PDU session establishment procedure.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0174] - UE integrity protection maximum data rate received in PDU Session Establishment Request message: if integrity protection is indicated as "Preferred" or "Required" in the user plane security enforcement information.

[0175] - RSN (redundancy sequence number) parameter

[0176] The N1N2 message transfer message may include an N1 SM container. The N1 SM container includes a PDU Session Establishment Accept message that the AMF will provide to the UE. The PDU Session Establishment Accept message includes the S-NSSAI from the allowed NSSAI. For the LBO roaming scenario, the PDU Session Establishment Accept message includes the S-NSSAI from the allowed NSSAI for the VPLMN, and also includes the corresponding S-NSSAI of the HPLMN from the mapping of the allowed NSSAI received by the SMF in step 3.

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

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

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

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

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

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

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

[0184] (14) Step 14: (R)AN sends an N2 PDU Session Response message to AMF. The N2 PDU Session Response message may include PDU Session ID, cause, N2 SM information (PDU Session ID, AN tunnel information, accepted / rejected QFI list, user plane enforcement policy notification), etc.

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

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

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

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

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

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

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

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

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

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

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

[0196] Architectural improvements for vehicle-mounted relays (VMRs) are being discussed. Note that VMRs are an example of mobile base stations. The descriptions of VMRs in this disclosure can be applied to mobile base stations.

[0197] For reference, in the disclosure of this specification, mobile base stations, VMRs, vehicle relays, etc. may mean MWAB (Mobile gNB with wireless access backhauling or Mobile RAN with wireless access backhauling).

[0198] Research is underway on mobile base stations (e.g., VMRs). The scope of the work can be applied to the Integrated Access and Backhaul (IAB) architecture. The IAB node consists of the IAB-MT and the IAB-DU, and the IAB-DU establishes an F1 interface with the donor CU via a wireless link.

[0199] Meanwhile, there are other architectural options for achieving the functionality of a mobile base station (e.g., a VMR). For example, a relay node includes a UE co-located with the entire gNB. Furthermore, there is a so-called "Velcro" solution, where the relay gNB establishes N2 and N3 interfaces to the AMF residing in the 5GC via PDU sessions.

[0200] These architectural options, which have not yet been explored, may be better suited for specific deployment scenarios of vehicle-mounted relays, such as those using VMRs where IAB is not widely supported, or where the relay handles local traffic in the vehicle to provide onboard services with low latency.

[0201] Additionally, other features not previously discussed include:

[0202] NTN backhauling to provide coverage to ships, aircraft and other areas without TN coverage;

[0203] A different scenario for backhaul (midhaul) MNOs than for VMR providers.

[0204] Therefore, further research on the above-mentioned items is suggested.

[0205] In relation to mobile base stations, the following objectives can be discussed:

[0206] For example, the goal might be to investigate and identify potential architectural and system-level improvements to further enhance the functionality of a vehicle-mounted base station relay. Specific objectives include:

[0207] - Identify gaps to support architectures that onboard gNBs to relay and use PDU sessions for wireless backhauling of N2 / N3 interfaces (e.g. including UE access control).

[0208] - Study whether and how to enable mobility for the onboard gNB of the relay using PDU sessions for wireless backhauling of the N2 / N3 interface.

[0209] - Determine whether and how to improve the architecture to enable relay authorization and configuration.

[0210] - Determine whether and how to improve the architecture to support QoS over backhaul.

[0211] - Determine whether and how to improve the architecture to enable cell ID / TAC management.

[0212] - Identify ways to improve the architecture to support UE location services and emergency services.

[0213] For reference, for wireless backhauling of N2 / N3, existing TN and NTN can be used.

[0214] Additionally, the following use cases were discussed:

[0215] For example, transporting vehicle relay traffic using a partner 5G network was discussed as an example use case.

[0216] This use case addresses a specific deployment scenario. For example, traffic exchanged via a vehicle relay station for users of one Mobile Network Operator (MNO) or service provider could be delivered via a 5G transport network managed by a second MNO.

[0217] Such a use case is illustrated in Figure 7. Figure 7 illustrates an example where MNO2 provides wireless access and transmission between a vehicle relay and the MNO1 5G network, providing End to End (E2E) connectivity to MNO1 users.

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

[0219] FIG. 7 is an example of an architecture for communication based on a mobile base station according to one embodiment of the disclosure of the present specification.

[0220] According to an example of FIG. 7, mobile relay traffic of MNO1 can be transmitted through the network of MNO2. The example of FIG. 7 is an example of the Velcro structure described above.

[0221] For example, the leftmost UE is the UE of the MNO1 user. The mobile base station includes a base station (e.g., gNB) and a UE. The UE of the MNO1 user is connected to the mobile base station. The UE of the mobile base station can establish a PDU session with the CN of MNO2. Through the PDU session of the UE of the mobile base station, the base station of the mobile base station connects the CN of MNO1 and the N2 / N3 interface, and the base station of the mobile base station can operate as the base station of MNO1. The base station of the mobile base station transmits the System Information Block (SIB) of MNO1 to the UE.

[0222] These scenarios may be based on business agreements between the two parties, specific network deployment / operational constraints, coverage requirements, and more. For example, they may be used for:

[0223] A 5G mobile operator (MNO1) with limited macro-RAN deployment and coverage space wants to leverage its spectrum to provide 5G access and services to subscribers (those traveling in vehicles or located in specific hotspot areas). MNO1 may decide to tunnel MNO1 traffic to and from mobile base stations (e.g., vehicle repeaters) by leveraging the better / ubiquitous 5G wireless (and transport) connectivity provided by a second operator (MNO2).

[0224] Public safety providers or other service / vehicle operators can manage specific vehicles via onboard relays. They can offer temporary 5G subscription and connectivity services for specific user categories, such as emergency responders, delivery workers, and general passengers. Since these providers may not own 5G spectrum or RAN / network infrastructure, they can use MNO2's mobile network to connect to relays (and users).

[0225] The prerequisites for the example in Figure 7 are as follows. This use case assumes the following options:

[0226] - The access link between the MNO1 UE and the mobile base station (e.g., a vehicle repeater) uses the MNO1 spectrum, and the repeater can be connected to the MNO2 RAN using the MNO2 spectrum.

[0227] - The MNO2 transport connection between the mobile base station (e.g., vehicle relay station) and the MNO1 network is used to carry relay traffic between the mobile base station (e.g., vehicle relay station) and the MNO1 5GC.

[0228] The service flow related to the example in Fig. 7 is as follows.

[0229] 1. A mobile base station (e.g., a vehicle relay) is provisioned and configured to register with the MNO2 network and establish the required PDU sessions with specific quality of service and policies (as negotiated for MNO1 traffic and subscribers).

[0230] 2. Mobile base stations (e.g., vehicle relays) are provisioned and configured to connect to the donor MNO1 network for communication between MNO1 users and the MNO1 network.

[0231] 3. The MNO1 subscriber / UE inside the vehicle camps on a mobile base station (e.g., a mobile repeater). The mobile base station broadcasts the MNO1 PLMN ID, and the MNO1 subscriber / UE inside the vehicle can register and connect to the MNO1 network.

[0232] 4. All traffic generated by MNO1 UE through the vehicle repeater is tunneled through the MNO2 5G connection of the existing repeater.

[0233] The postconditions according to the example in Fig. 7 are as follows.

[0234] MNO1 users will have full transparency into the superior in-vehicle 5G coverage / connectivity provided by 5G services and vehicle repeaters.

[0235] Examples of existing features that encompass some or all of the use case capabilities include: TS 23.501 V18.0.0 (Annex D) describes the concept of an overlay network connection over an underlay network connection. This does not fully address the target use case and requirements and is limited to mobile BS relays. For reference, examples of underlay and overlay network connections can be illustrated in the examples in Figures 8 and 9 below.

[0236] Potential new requirements needed to support this use case include: 5G systems must be able to support communications with users of one mobile network operator (MNO-A) via mobile base station relays, where relayed traffic is then transported to the MNO-A network using 5G connectivity (RAN and 5GC) provided by another mobile network operator (MNO-B).

[0237] Looking at the architecture of the mobile base station (e.g., vehicle relay) of the example in Fig. 7, the Vehicle Mounted Relay (VMR) is a relay belonging to MNO1. The mobile base station (e.g., VMR) connects to the base station and 5GC of MNO2 and creates a PDU session. The mobile base station (e.g., VMR) connects the N2 / N3 interfaces to the 5GC of MNO1 through the created PDU session. The mobile base station (e.g., VMR) can operate as a base station directly connected to the 5GC of MNO1 through the N2 / N3 interfaces.

[0238] Of course, a mobile base station (e.g., a vehicle relay) can access the base station and 5GC of MNO1, create a PDU session, and connect the N2 / N3 interfaces to the 5GC of MNO1 through the created PDU session. The mobile base station can also operate as a base station based on the N2 / N3 interfaces connected to the 5GC of MNO1.

[0239] In this specification, a base station that a mobile base station (e.g., vehicle relay) connects to connect N2 / N3 interfaces to 5GC is referred to as an underlay base station.

[0240] In this case, the Vehicle Mounted Relay broadcasts MNO1's SIB because the N2 / N3 interfaces are connected to MNO1. Therefore, terminals receiving the SIB transmitted by the mobile base station are assumed to be within MNO1's network coverage. In other words, even if the terminal is actually located in a VPLMN, it can be assumed to be within MNO1's network coverage.

[0241] For reference, the vehicle relay architecture of FIG. 7 illustrates a scenario in which the Vehicle Relay connects to the MNO1 network via the MNO2 network. However, this is merely an example, and the disclosure of this specification is not limited by the example of FIG. 7. For example, the Vehicle Relay may connect to the base station and 5GC of MNO1 to create a PDU session, and connect the N2 / N3 interfaces to the 5GC of MNO1 through the created PDU session, thereby operating as a base station.

[0242] Below, examples of architectures related to mobile base stations are described with reference to examples of FIGS. 8 and 9.

[0243] Figure 8 is a first example of an architecture related to a mobile base station.

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

[0245] FIG. 8 is a first example of an architecture related to a mobile base station according to the disclosure of this specification.

[0246] The example in Figure 8 illustrates an architecture in which both the underlay network and the overlay network of a mobile base station (e.g., vehicle relay) are Home networks.

[0247] For reference, in the disclosure of this specification, the underlay network refers to the network to which the UE of the mobile base station (e.g., the VMR-UE in FIG. 8) is connected. The underlay network provides wireless backhaul connectivity via PDU sessions. The overlay network refers to the network to which the base station of the mobile base station (e.g., the VMR-RAN) is connected. The overlay network refers to the network to which the UE receiving service through the mobile base station (e.g., the UE located at the far left of FIG. 8) connects.

[0248] According to the example of Fig. 8, a UE (i.e., VMR-UE) of a mobile base station (e.g., Vehicle Relay or VMR) connects to a base station and 5GC of a home network to create a PDU session. The RAN of the mobile base station (i.e., VMR-RAN) connects N2 / N3 interfaces to a 5GC of the home network through the created PDU session and operates as a base station.

[0249] In the example of FIG. 8, the 5G Core Network Functions for the VMR-UE (i.e., AMF1, SMF1, UPF1, UDM1) and the 5G Core Network Functions for the UE served by the VMR-RAN (i.e., AMF2, SMF2, UPF2, UDM2) are depicted as different NFs. However, this is merely an example, and the scope of the present specification is not limited thereto. For example, some or all of these may be the same NF. For example, AMF1 and AMF2 may be the same AMF. Or, UDM1 and UDM2 may be the same UDM.

[0250] Figure 9 is a second example of an architecture related to a mobile base station.

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

[0252] FIG. 9 is a second example of an architecture related to a mobile base station according to the disclosure of this specification.

[0253] The example in Figure 9 illustrates an example architecture in which the underlay network of a mobile base station (e.g., a vehicle relay) is the Visited network and the overlay network is the Home network.

[0254] According to the example of Fig. 9, a UE (i.e., VMR-UE) of a mobile base station (e.g., Vehicle Relay or VMR) connects to a base station and 5GC of a visited network and creates a PDU session. The base station (i.e., VMR-RAN) of the mobile base station connects N2 / N3 interfaces to 5GC of the home network through the created PDU session and operates as a base station.

[0255] In the example of Figure 9, the UDM for the VMR-UE (i.e., UDM1) and the UDM for the UE served by the VMR-RAN (i.e., UDM2) are depicted as different NFs. However, this is merely an example, and the scope of this specification is not limited thereto. For example, UDM1 and UDM2 may be the same UDM.

[0256] Referring to the architecture of FIG. 7 described above, the architecture of the mobile base station of FIG. 7 in a roaming state may correspond to FIG. 9. For example, MNO1 and MNO2 of FIG. 7 may be considered to correspond to the Home network and the Visited network of FIG. 9, respectively.

[0257] Although examples of FIG. 8 and FIG. 9 illustrate a gNB (i.e., an NR base station) as an underlay base station, this is merely an example and the scope of the disclosure of this specification is not limited thereto. For example, the underlay base station may be a base station / RAN supporting a different RAT than 5G.

[0258] Meanwhile, 5GS defined notification control (or QNC: QoS Notification Control) as a mechanism / feature for providing QoS. An example of the content defined in TS 23.501 V18.3.0 is described.

[0259] For example, let's explain Notification control.

[0260] QoS parameter notification control indicates whether to request notification to the NG-RAN when "GFBR can no longer be guaranteed (or can be guaranteed again)" during the lifetime of the QoS flow. Notification control can be used for GBR QoS flows if application traffic can adapt to changes in QoS (e.g., AF can trigger rate adaptation).

[0261] SMF activates notification control only if the QoS notification control parameters are set in the PCC rule (received from the PCF) bound to the QoS flow. The notification control parameters are signaled to the NG-RAN as part of the QoS profile.

[0262] Describes notification control without an alternative QoS profile.

[0263] When notification control is enabled for a particular Guaranteed Bit Rate (GBR) QoS flow and the NG-RAN determines that it cannot meet the Guaranteed Flow Bit Rate (GFBR), Packet Delay Budget (PDB) or Packet Error Rate (PER) of the QoS profile, the NG-RAN sends a notification to the SMF stating that "GFBR cannot be guaranteed any more". Furthermore, the NG-RAN maintains this GBR QoS flow (i.e. while not fulfilling the requested QoS profile for this QoS flow), unless NG-RAN specific conditions, such as radio link failure or internal RAN congestion, require it to release NG-RAN resources for this GBR QoS flow. The NG-RAN shall attempt to meet the GFBR, PDB and PER of the QoS profile again.

[0264] Upon receiving a notification from NG-RAN that “GFBR can no longer be guaranteed,” the SMF can forward the notification to the PCF.

[0265] The NG-RAN may determine that it can once again meet the GFBR, PDB, and PER requirements of the QoS profile for the QoS flow for which it has been notified that "GFBR can no longer be guaranteed." In this case, the NG-RAN may send a "GFBR can be guaranteed again" notification to the SMF, which may then forward the notification to the PCF. The NG-RAN must send subsequent "GFBR can no longer be guaranteed" notifications whenever necessary.

[0266] During a handover, the source NG-RAN does not inform the target NG-RAN whether the source NG-RAN has sent a "GFBR can no longer be guaranteed" notification for the QoS flow. The target NG-RAN performs admission control to reject any QoS flow for which it cannot permanently allocate resources. The accepted QoS flow is included in the N2 Path Switch Request or N2 Handover Request Accept message sent by the NG-RAN to the AMF. Unless the SMF also receives a reference to an alternate QoS profile for the QoS flow, the SMF interprets the fact that the QoS flow is listed as a transferred QoS Flow in the Nsmf_PDUSession_UpdateSMContext request received from the AMF as a "GFBR can be guaranteed again" notification for this QoS flow. After a successful handover, the target NG-RAN must send a follow-up notification indicating "GFBR can no longer be guaranteed" for the corresponding QoS flow whenever necessary. The SMF may have previously notified the PCF that "GFBR can no longer be guaranteed" and the SMF may not have received an explicit notification from the target NG-RAN indicating "GFBR can no longer be guaranteed" for the corresponding QoS flow within a configured time period. In this case, the SMF notifies the PCF that "GFBR can be guaranteed again."

[0267] Describes notification control based on alternative QoS profiles.

[0268] If notification control is enabled for a given GBR QoS flow and the NG-RAN receives a list of alternate QoS profiles for this QoS flow and supports handling of alternate QoS profiles, the following applies:

[0269] 1) If the NG-RAN determines that it cannot meet the GFBR, PDB or PER of a QoS profile, the NG-RAN shall send a notification to the SMF stating that "GFBR can no longer be guaranteed". Before sending the notification that "GFBR can no longer be guaranteed" to the SMF, the NG-RAN shall check whether the GFBR, PDB and PER currently being implemented by the NG-RAN matches with an alternate QoS profile in the given priority order. If there is a match, the NG-RAN shall indicate to the SMF a reference to the matching alternate QoS profile with the highest priority together with the notification.

[0270] If no match is found, the NG-RAN sends a "GFBR can no longer be guaranteed" notification to the SMF, indicating that the lowest fallback QoS profile cannot be met (unless NG-RAN specific conditions, such as radio link failure or internal RAN congestion, require NG-RAN resources to be released for this GBR QoS flow).

[0271] 2) A notification "GFBR can no longer be guaranteed" is sent to the SMF and the NG-RAN may determine that the currently satisfied GFBR, PDB or PER is different from the situation indicated in the last notification. In this case, the NG-RAN sends a notification ("GFBR can no longer be guaranteed" or "GFBR can be guaranteed again") to the SMF and indicates the current situation (unless there are specific conditions in the NG-RAN such as radio link failure or internal RAN congestion that require the NG-RAN to release NG-RAN resources for this GBR QoS flow).

[0272] 3) NG-RAN should always attempt to fulfill the QoS profile, and if this is not possible, it should use an alternate QoS profile with higher priority.

[0273] 4) Upon receiving notification from the NG-RAN, the SMF may notify the PCF. In doing so, the SMF informs the PCF of the current fulfillment status.

[0274] 5) Unless otherwise indicated by the PCF, the SMF uses NAS signaling (transmitted transparently through the RAN) to inform the UE of changes in QoS parameters (e.g. 5QI, GFBR, MFBR) that the NG-RAN is currently implementing for the QoS flow after notification control has occurred.

[0275] Describes the use of notification control based on alternate QoS profiles during handover.

[0276] During a handover, a prioritized list of alternative QoS profiles (if available) is provided to the target NG-RAN for each QoS flow, along with the QoS profiles. If the target NG-RAN cannot guarantee the GFBR, PDB, and PER included in the QoS profiles, an alternative QoS profile is provided to the target NG-RAN, and the target NG-RAN can support the alternative QoS profile. In this case, the target NG-RAN checks whether the GFBR, PDB, and PER values ​​that can be implemented match those of the alternative QoS profiles, taking into account the priorities. If one of the alternative QoS profiles matches the GFBR, PDB, and PER values ​​that the target NG-RAN can implement, the target NG-RAN shall accept the QoS flow and indicate a reference to that alternative QoS profile to the source NG-RAN.

[0277] For delay-critical GBR QoS flows, the target NG-RAN also considers whether it can accommodate MDBV if included in an alternative QoS profile.

[0278] If no match is found for the alternative QoS profile, the Target NG-RAN rejects QoS flows that cannot guarantee GFBR, PDB, PER and, if available, the associated MDBV included in the QoS profile.

[0279] After the handover is completed and the target NG-RAN accepts the QoS flow based on the alternate QoS profile, the target NG-RAN processes this QoS flow in the same way as if it had sent a notification to the SMF that "GFBR can no longer be guaranteed" with reference to the alternate QoS profile.

[0280] If the target NG-RAN accepts the QoS flow based on an alternate QoS profile, during the Xn and N2 based handover procedure, a reference to the matching alternate QoS profile is provided by the target NG-RAN to the AMF (which forwards the message to the SMF) and this reference is forwarded to the SMF. After the handover is successfully completed, the SMF receives the reference to the alternate QoS profile and if this reference indicates that the state of this previously notified QoS flow has changed, it notifies the PCF that "GFBR can no longer be guaranteed" for the QoS flow. Unless the PCF indicates otherwise, the SMF shall use NAS signaling (transmitted transparently through the RAN) to inform the UE of the QoS parameters (e.g. 5QI, GFBR, MFBR) corresponding to the new state of the QoS flow.

[0281] If the target NG-RAN has accepted the QoS flow according to the QoS profile, the SMF interprets the fact that the QoS flow is indicated as a forwarded QoS flow in the message received from the AMF as an indication that "GFBR can be guaranteed again" for that QoS flow. Upon successful completion of the handover, the target NG-RAN performs the actions described in "Notification Control Based on Alternative QoS Profiles". If the SMF has previously notified the PCF that "GFBR can no longer be guaranteed" and has not received an explicit notification from the target NG-RAN that "GFBR can no longer be guaranteed" for that QoS flow within a configured timeframe, the SMF shall notify the PCF that "GFBR can be guaranteed again".

[0282] If the QoS flow is accepted by the target NG-RAN and the SMF has not received a reference to an alternate QoS profile from the target NG-RAN and the SMF previously informed the UE of the QoS parameters corresponding to the alternate QoS profile, the SMF shall use NAS signaling to inform the UE of the QoS parameters corresponding to the corresponding QoS profile.

[0283] Describes the use of notification control based on alternate QoS profiles when setting up and modifying QoS flows.

[0284] When establishing or modifying a QoS flow, a list of prioritized alternative QoS profiles for the QoS flow may be provided to the NG-RAN along with the QoS profiles. If the NG-RAN cannot guarantee the GFBR, PDB and PER included in the QoS profiles, and if an alternative QoS profile is provided to the NG-RAN and the NG-RAN supports the alternative QoS profiles, the NG-RAN shall ensure that the implementable GFBR, PDB and PER values ​​match at least one of the alternative QoS profiles, taking into account the priorities. If one of the alternative QoS profiles matches the GFBR, PDB and, if available, the associated MDBV and the PER values ​​that the NG-RAN can implement, the NG-RAN shall accept the QoS flow and indicate a reference to that alternative QoS profile in the SMF. If no match is found for an alternative QoS profile, the NG-RAN shall reject the QoS flow establishment or modification.

[0285] After the NG-RAN has successfully established or modified a QoS flow indicating that the currently satisfied QoS matches one of the alternate QoS profiles, the NG-RAN shall treat this QoS flow in the same manner as if it had notified the SMF that "GFBR can no longer be guaranteed" with reference to that alternate QoS profile.

[0286] If SMF receives a reference to an alternate QoS profile during QoS flow setup or modification, SMF can notify PCF about it.

[0287] Unless otherwise indicated by the PCF, the SMF shall inform the UE of the QoS parameters (e.g. 5QI, GFBR, MFBR) corresponding to the referenced alternative QoS profile using NAS signaling (transmitted transparently over the RAN).

[0288] Below, examples of the content defined in TS 38.413 V17.6.0 are described. For example, the procedure for SMF to provide QNC-related requests to NG-RAN as part of QoS parameters for a QoS Flow, and examples of message / parameter formats are shown. This is described with reference to FIGS. 10 to 12.

[0289] Describes an example of PDU session resource setup.

[0290] The purpose of the PDU Session Resource Setup procedure is to allocate resources to Uu and NG-U for one or more PDU sessions and their corresponding QoS flows, and to establish the corresponding DRB for a given UE. This procedure uses UE-specific signaling.

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

[0292] FIG. 10 is an example of PDU session resource setup according to the disclosure of this specification.

[0293] The example in Figure 10 is an example of a successful operation.

[0294] According to the example of FIG. 10, the AMF may send a PDU Session Resource Setup Request message to the NG-RAN node.

[0295] NG-RAN may send a PDU Session Resource Setup Response message to AMF.

[0296] AMF initiates the procedure by sending a PDU Session Resource Setup Request message to the NG-RAN node.

[0297] The PDU Session Resource Setup Request message must contain the information required for the NG-RAN node to configure the NG-RAN configuration related to a PDU session consisting of one or more PDU session resources. In addition, the PDU Session Resource Setup Request message may include each PDU session resource to be configured in the PDU Session Resource Setup Request List IE.

[0298] For each PDU session in a PDU Session Resource Setup Request message, an Alternative QoS Parameter Setting List IE may be included in the GBR QoS Flow Information IE within the PDU Session Resource Setup Request Transmission IE of the PDU Session Resource Setup Request message. In this case, if notification control is enabled, the NG-RAN node may accept the setup of the QoS flow when at least one of the requested QoS parameters or the alternative QoS parameter sets can be satisfied at the time of setup. The NG-RAN node may accept the setup that satisfies one of the alternative QoS parameters. In this case, the NG-RAN node indicates the currently satisfied alternative QoS parameter set in the Current QoS Parameter Set Index IE within the PDU Session Resource Setup Response Transmission IE of the PDU Session Resource Setup Response message.

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

[0300] FIG. 11 is an example of PDU session resource modification according to the disclosure of this specification.

[0301] The example in Figure 11 is an example of a successful operation.

[0302] According to the example of FIG. 11, the AMF can send a PDU session resource modify request message to the NG-RAN node.

[0303] NG-RAN may send a PDU Session Resource Modification Response message to AMF.

[0304] AMF initiates the procedure by sending a PDU Session Resource Modification Request message to the NG-RAN node.

[0305] The purpose of the PDU Session Resource Modification procedure is to enable configuration modification of a PDU session already established for a specific UE. It also enables the establishment, modification, and release of QoS flows for an already established PDU session. This procedure uses UE-specific signaling.

[0306] AMF initiates the procedure by sending a PDU Session Resource Modification Request message to the NG-RAN node.

[0307] For each PDU session in a PDU Session Resource Modification Request message, an Alternative QoS Parameter Setting List IE may be included in the GBR QoS Flow Information IE within the PDU Session Resource Modification Request Transmission IE of the PDU Session Resource Modification Request message. In this case, if notification control is enabled, the NG-RAN node may accept the setup of the QoS flow when at least one of the requested QoS parameters or the alternative QoS parameter sets can be satisfied at the time of setup. The NG-RAN node may accept the setup that satisfies one of the alternative QoS parameters. In this case, the NG-RAN node indicates the currently satisfied alternative QoS parameter set in the Current QoS Parameter Set Index IE within the PDU Session Resource Setup Response Transmission IE of the PDU Session Resource Modification Response message.

[0308] Referring to the example in Table 3, an example of GBR QoS flow information is described.

[0309] IE / Group Name Scope IE Type and Reference Semantics Description Importance Assigned Importance Maximum Flow Bit Rate Downlink M bit rate. See TS 38.413 V17.6.0, Section 9.3.1.4 Maximum bit rate in DL See TS 23.501 V18.3.0 for details. - Maximum Flow Bit Rate Uplink M bit rate. See TS 38.413 V17.6.0, Section 9.3.1.4 Maximum bit rate in UL See TS 23.501 V18.3.0 for details. - Guaranteed Flow Bit Rate Downlink M bit rate. See TS 38.413 V17.6.0, Section 9.3.1.4 Guaranteed bit rate in DL (if there is data to transmit). See TS 23.501 V18.3.0 for details. See TS 38.413 V17.6.0, clause 9.3.1.4. Guaranteed flow bit rate uplink M bit rate. See TS 38.413 V17.6.0, clause 9.3.1.4. Guaranteed bit rate in UL (if there is data to transmit). See TS 23.501 V18.3.0 for details. - Notification control OENUMERATED (notification requested, ...) See TS 23.501 V18.3.0 for details. - Maximum packet loss rate downlink O packet loss rate See TS 38.413 V17.6.0, clause 9.3.1.79. Indicates the maximum packet loss rate that can be tolerated in the downlink direction. See TS 23.501 V18.3.0 for details. - Maximum packet loss rate uplink O packet loss rate See TS 38.413 V17.6.0, clause 9.3.1.79. Indicates the maximum packet loss rate that can be tolerated in the uplink direction. Indicates the maximum packet loss rate. See TS 23.501 V18.3.0 for details. - List of alternative QoS parameter sets. See section 9.3.1.151 of OTS 38.413 V17.6.0. Indicates an alternative QoS parameter set for the QoS flow. YESignore

[0310] The IE according to the example in Table 3 represents the QoS parameters of the GBR QoS flow for downlink and uplink.

[0311] Below, a list of alternative QoS parameter sets is described with reference to Table 4.

[0312] IE / Group Name Scope IE Type and Reference Semantics Description Alternative QoS Parameter Set Item 1.. <maxnoofqosparasets>> Alternative QoS Parameter Set Index See 9.3.1.152 of MTS 38.413 V17.6.0 > Guaranteed Flow Bit Rate Downlink Bit Rate See 9.3.1.4 of TS 38.413 V17.6.0 > Guaranteed Flow Bit Rate Uplink Bit Rate See 9.3.1.4 of TS 38.413 V17.6.0 > Packet Delay Budget See 9.3.1.80 of OTS 38.413 V17.6.0 > Packet Error Rate See 9.3.1.81 of OTS 38.413 V17.6.0

[0313] For reference, in the example in Table 4, the range bound maxnoofQoSparaSets represents the maximum number of alternative QoS parameter sets allowed for a QoS profile. The value is 8.

[0314] The IE according to the example in Table 4 includes a set of alternative QoS parameters that the NG-RAN node can indicate to satisfy if notification control is enabled and the requested list of QoS parameters cannot be satisfied.

[0315] Table 5 shows examples of alternative QoS parameter set indices.

[0316] IE / Group Name Scope IE Type and Reference Semantics Description Alternative QoS Parameter Set Index MINTEGER (1..8, ...) Indicates the index of the entry in the list of alternative QoS parameter sets, i.e., the index of the entry corresponding to the currently satisfied alternative QoS parameter set.

[0317] The IE according to the example in Table 5 represents the set of QoS parameters that can currently be satisfied.

[0318] Below, we provide examples of what is defined in TS 38.413 V17.6.0. For example, we show the procedure by which the NG-RAN provides QNC-related notifications to the SMF, and examples of message / parameter formats.

[0319] Describes an example of a PDU session resource notification.

[0320] The purpose of the PDU Session Resource Notification procedure is to notify the NG-RAN node that a QoS flow or PDU session that has already been established for a specific UE has been released, is no longer satisfied, or has been re-established. The PDU Session Resource Notification procedure is also used to notify the NG-RAN node that updated QoS parameters during a path switching request procedure were not successfully accepted. This procedure uses UE-specific signaling.

[0321] Describes an example of a PDU session resource notification.

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

[0323] FIG. 12 is an example of a PDU session resource notification according to the disclosure of this specification.

[0324] The example in Figure 12 is an example of a successful operation.

[0325] For example, an NG-RAN node may send a PDU Session Resource Notification message to the AMF.

[0326] The NG-RAN node initiates the procedure by sending a PDU Session Resource Notification message.

[0327] The PDU Session Resource Notification message contains information about PDU session resources or resources released by the NG-RAN node (or QoS flows, or QoS flows that are no longer fulfilled, or QoS flows that are being fulfilled again).

[0328] - If some QoS flows are released by the NG-RAN node, or some QoS flows are no longer carried by the NG-RAN node, or some QoS flows are carried again by the NG-RAN node, for each PDU session, a PDU Session Resource Notification Transmission IE containing the following shall be included in the PDU Session Resource Notification message:

[0329] 1. QoS Flow Release List IE containing the QoS flow list (if any) released by the NG-RAN node.

[0330] 2. QoS Flow Notification List IE containing the list of GBR QoS flows (if any) that are no longer fulfilled or will not be fulfilled again by the NG-RAN node and the Notification Cause IE. For QoS flows that are marked as no longer fulfilled, the NG-RAN node may also indicate in the Current QoS Parameter Set Index IE the alternative QoS parameter set that it can now fulfill.

[0331] 3. QoS Flow Feedback List IE containing the list of QoS flows (if any) for which QoS parameters were updated during the path switching request procedure but could not be successfully accepted by the NG-RAN node. The QoS Flow Feedback List IE may be associated with a value that can be provided.

[0332] - The PDU Session Resource Notification message contains a PDU Session Resource Notification Release Transmission IE for each PDU session resource released by the NG-RAN node. The PDU Session Resource Notification Release Transmission IE contains a Cause IE containing the release reason.

[0333] The NG-RAN node reports location information in the User Location Information IE within the UE's PDU Session Resource Notification message, if supported.

[0334] Upon receiving a PDU Session Resource Notification message, the AMF shall transparently forward a PDU Session Resource Notification Transmission IE or a PDU Session Resource Notification Release Transmission IE for each PDU Session indicated in the PDU Session ID IE to the SMF associated with that PDU Session. Upon receiving a PDU Session Resource Notification Transmission IE, the SMF will typically initiate appropriate release or modification procedures for the PDU Session or QoS flow that has been determined to be no longer satisfied by the core network side.

[0335] An example of a PDU session resource notification message is described below with reference to Table 6.

[0336] IE / Group Name Scope IE Type and Reference Semantics Description Importance Assigned Importance Message Type See 9.3.1.1 of MTS 38.413 V17.6.0 YESignoreAMF UE NGAP IDMTS See 9.3.3.1 of TS 38.413 V17.6.0 YESrejectRAN UE NGAP IDMTS See 9.3.3.2 of TS 38.413 V17.6.0 YESrejectPDU Session Resource Notification List 0..1 YESreject>PDU Session Resource Notification Item 1.. <maxnoofpdusessions>->>PDU Session IDM See 9.3.1.50 of TS 38.413 V17.6.0 ->>PDU Session Resource Notify Transfer MOCTET STRINGContaining the PDU Session Resource Notify Transfer IE This IE is described in subclause 9.3.4.5 of TS 38.413 V17.6.0 - PDU Session Resource Released List0..1YESignore>PDU Session Resource Released Item1.. <maxnoofpdusessions>->>PDU Session IDM See 9.3.1.50 of TS 38.413 V17.6.0 ->>PDU Session Resource Notification Released Transport MOCTET STRING Contains PDU Session Resource Notification Released Transport IE. This IE is described in subclause 9.3.4.13 of TS 38.413 V17.6.0 - User Location Information See 9.3.1.16 of OTS 38.413 V17.6.0 YESignore

[0337] The NG-RAN node sends this message according to the example in Table 6. For example, this message is sent to indicate that the QoS requirements of an already established GBR QoS flow for which notification control has been requested are no longer met or have been met again by the NG-RAN node. This message may also be sent by the NG-RAN node to indicate that PDU session resources for a specific UE have been released.

[0338] PDU Session Resource Notification messages are sent from NR-RAN nodes to AMF.

[0339] For reference, in the example in Table 6, the range bound maxnoofPDUSessions represents the maximum number of PDU sessions allowed for a single UE. The value is 256.

[0340] Referring to the example in Table 7, an example of a PDU session resource notification transfer message is described.

[0341] IE / Group Name Scope IE Type and Reference Semantics Description Importance Assigned Importance QoS Flow Notification List 0..1 -> QoS Flow Notification Item 1.. <maxnoofqosflows>->>QoS Flow Identifier See 9.3.1.51 of MTS 38.413 V17.6.0 ->>Notification Reason MENUMERATED (fullfilled, not fulfilled, 쪋) ->>Current QoS Parameter Set Index OAlternative QoS Parameter Set Notification Index See 9.3.1.153 of MTS 38.413 V17.6.0 The index to the currently fulfilled alternative QoS parameter set. A value of 0 indicates that the NG-RAN cannot satisfy even the lowest alternative parameter set. YESIgnoreQoS Flow Dismissed ListOFlow List with Reason See 9.3.1.13 of TS 38.413 V17.6.0 - Secondary RAT Usage Information See 9.3.1.114 of OTS 38.413 V17.6.0 YESignoreQoS Flow Feedback List0..1 YESignore >QoS Flow Feedback Item1.. <maxnoofqosflows>->>QoS Flow Identifier See 9.3.1.51 of MTS 38.413 V17.6.0 ->>Update Feedback OBIT STRING {CN PDB DL(0),CN PDB UL(1)}(SIZE(8, 쪋)) Each position in the bitmap represents a QoS parameter. If the bit is set to "1", the corresponding parameter has not been updated. If the bit is set to "0", the corresponding parameter has been successfully updated. Bits 2-7 are reserved for future use. ->>CN Packet Delay Budget Downlink OExtended Packet Delay Budget See 9.3.1.135 of MTS 38.413 V17.6.0 Indicates that the NG-RAN can provide this value if the packet delay budget downlink has not been updated at the path switch. ->>CN Packet Delay Budget Uplink OExtended Packet Delay Budget 9.3.1.135 Indicates that the NG-RAN can provide this value if the reference packet delay budget uplink has not been updated at the path switch.

[0342] The PDU session resource notification transfer message according to the example in Table 7 can be transparent to AMF.

[0343] For reference, in the example in Table 7, the range bound maxnoofQoSFlows represents the maximum number of QoS flows allowed within a single PDU session. The value is 64.

[0344] Below, the alternative QoS parameter set notification index is described with reference to Table 8.

[0345] IE / Group Name Scope IE Type and Reference Semantics Description Alternative QoS Parameter Set Notification Index MINTEGER (0..8, ...) Indicates the index of the entry in the list of alternative QoS parameter sets, i.e., the index of the entry corresponding to the currently satisfied alternative QoS parameter set. A value of 0 indicates that the NG-RAN cannot satisfy even the lowest alternative parameter set.

[0346] The IE according to the example in Table 8 represents the set of QoS parameters that can currently be satisfied.

[0347] For Notification control (or QNC: QoS Notification Control), please refer to TS 23.501 V18.0.0, TS 23.502 V18.0.0, TS 23.503 V18.0.0, TS 38.413 V17.6.0, etc.

[0348] According to the QoS Notification Control (QNC) mechanism described above, if the NG-RAN cannot satisfy the QoS required by the QoS Flow (e.g., due to congestion), the NG-RAN can notify the SMF of this. In particular, in the case of QNC to which the Alternative QoS Profile is applied, the NG-RAN can also notify the SMF of the QoS that it can satisfy. Then, the SMF can notify this to the PCF, and the PCF can notify this to the AF. If the NG-RAN can satisfy the QoS required by the QoS Flow again, or can provide a better QoS based on the AQP, it can notify this to the SMF. Then, the SMF can also notify this to the AF through the PCF.

[0349] The QoS requirements of the QoS Flow or PDU Session of the UE served by the Vehicle Relay may not be met. The QoS requirements of the QoS Flow or PDU Session of the UE served by the Vehicle Relay may not be met due to one or more of the following reasons. Note that reasons why the base station may not be able to meet the QoS requirements include, but are not limited to, congestion:

[0350] 1) When the base station part of the Vehicle Relay cannot satisfy the QoS required by the QoS Flow or PDU Session of the above UE.

[0351] 2) When the underlay base station of the Vehicle Relay (e.g., the base station of MNO2 in Fig. 7) cannot satisfy the QoS required by the QoS Flow or PDU Session of the UE.

[0352] 3) When the underlay base station of the Vehicle Relay (e.g., the base station of MNO2 in Fig. 7) cannot satisfy the QoS required by the QoS Flow or PDU Session of the UE part of the Vehicle Relay (i.e., VMR UE).

[0353] According to the prior art, if a mobile base station fails to satisfy the QoS flow or QoS requirements in cases 2) and 3), a QoS notification is not provided. This causes the mobile base station to serve the UE without considering the cases where the QoS requirements are not satisfied in cases 2) and 3). This causes the mobile base station to be unable to effectively and / or accurately provide services to the UE. Therefore, a method is needed that enables the QNC mechanism to cover cases 2) and 3).

[0354] This specification proposes a method to solve these problems.

[0355] In the disclosure of this specification, UE (User Equipment) and terminal are used interchangeably.

[0356] In the disclosure of this specification, the terms Subscriber and User are used interchangeably.

[0357] In the disclosure of this specification, Application Function (AF) and Application Server (AS) are used interchangeably.

[0358] In the disclosure of this specification, the terms Vehicle Relay, Vehicle-Mounted Relay (VMR), Relay, Mobile Relay, MBSR (Mobile Base Station Relay), eMBSR (enhanced MBSR), mobile base station, MWAB (Mobile gNB with wireless access backhauling or Mobile RAN with wireless access backhauling) and the like are used interchangeably.

[0359] In the disclosure of this specification, the underlay base station of a mobile base station (e.g., Vehicle Relay), the base station to which the mobile base station (e.g., Vehicle Relay) connects to connect N2 / N3 interfaces to 5GC, the base station of a VMR UE, the base station serving the VMR UE, the base station to which the VMR UE connects, the backhaul (BH) base station of the VMR, etc. are used interchangeably to describe.

[0360] In the disclosure of this specification, the terms VMR base station, VMR base station part, VMR gNB, Vehicle Relay base station, and Vehicle Relay base station part are used interchangeably to describe the same.

[0361] In the disclosure of this specification, the N2 interface is described interchangeably with the N2 tunnel and N2, and the N3 interface is described interchangeably with the N3 tunnel and N3.

[0362] Vehicle relays can be mounted on various vehicles, including ground vehicles (e.g., cars, trains), sea or river vehicles (e.g., ships, boats), aerial vehicles (e.g., airplanes, helicopters, drones), and satellites. When mounted on an aerial vehicle, they are referred to as Aerial Vehicle Relays (AVRs). Furthermore, vehicle relays do not necessarily have to be mobile; they can function as base stations while stationary. As previously explained, "vehicle relay" can be used synonymously with terms such as "mobile base station" and "MWAB."

[0363] Vehicle Relay can serve not only UEs within the vehicle but also UEs around the vehicle.

[0364] VMR can use various RATs to serve UE (e.g., NR, LTE, 6G RAT, etc.).

[0365] A Vehicle Relay may contain a UE or a Mobile Terminal (MT) part. This may be interpreted as the VMR containing either a UE part / operation / functionality or a Mobile Terminal (MT) part / operation / functionality.

[0366] The method proposed in the disclosure of this specification may be composed of a combination of one or more of the following operations / configurations / steps. Furthermore, the proposed methods may be performed or used in combination or complementary manner.

[0367] The method proposed in this specification can be applied to both cases where the Vehicle Relay is connected to the Home network to provide services and cases where it is connected to the Visited / Roaming network to provide services.

[0368] The operations and contents described herein as being performed by a UE (e.g., a VMR UE) included in a VMR or a base station (e.g., a VMR base station) included in a VMR may be interpreted as operations and contents performed by a VMR.

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

[0370] A first example of the disclosure of this specification includes an operation in which a base station (i.e., an underlay base station) of a VMR UE performs QoS-related notification (or alert).

[0371] According to a first example of the disclosure of the present specification, a base station of a VMR UE (i.e., an underlay base station) may directly and / or indirectly transmit a notification (or alert) related to QoS to the VMR UE in the following cases. For example, if i) the base station of the VMR UE (i.e., the underlay base station) cannot satisfy the QoS for the VMR UE or the QoS of the UE served by the VMR, or ii) the base station of the VMR UE (i.e., the underlay base station) becomes able to satisfy the QoS again, or iii) the QoS that the base station of the VMR UE (i.e., the underlay base station) can satisfy changes (the QoS level / levels that can be satisfied are changed), the base station of the VMR UE (i.e., the underlay base station) may perform the following actions. For example, the base station (i.e., the underlay base station) of the VMR UE can notify the VMR UE of QoS-related information directly (e.g., an RRC message can be used) and / or indirectly (e.g., the base station (i.e., the underlay base station) of the VMR UE can notify the SMF, and the SMF can notify the VMR UE). In addition, the QoS-related notification can be based on one or more of the following conditions:

[0372] a) The base station of the VMR UE can perform the above QoS-related notification because it knows that it is serving the VMR UE.

[0373] For example, if a VMR UE notifies the underlay base station that it is a VMR through an RRC message when connecting to the underlay base station, the base station of the VMR UE can know that it is serving the VMR UE. And / or, if the AMF provides the base station of the VMR UE with authorized / allowed information about whether the VMR UE (i.e., the UE that wants to operate as a VMR) can operate as a VMR, the base station of the VMR UE can know that it is serving the VMR UE.

[0374] The above underlay base station can perform QoS-related notifications based on local configuration, operator policy, etc.

[0375] b) Based on the VMR UE requesting the above QoS-related notification to the VMR UE's base station, the VMR UE's base station can perform the above QoS-related notification.

[0376] The VMR UE can request the above QoS-related notification from the underlay base station using an RRC message.

[0377] c) The SMF serving the VMR UE may request the underlay base station to provide the above QoS-related notification to the VMR UE.

[0378] d) The SMF serving the VMR UE may request the underlay base station to provide the above QoS-related notification to the SMF. The base station of the VMR UE may provide the above QoS-related notification to the SMF. When the SMF receives the above QoS-related notification, the SMF may provide / forward QoS-related information to the VMR UE via a SM (Session Management) NAS message. At this time, the SMF may provide / forward the same information, modified information, or part of the information notified from the underlay base station to the VMR UE. Alternatively, when the SMF receives a QoS-related notification request from an AF (e.g., when the VMR (or VMR UE or VMR RAN) acts as an AF), when the SMF receives the above QoS-related notification, the SMF may forward the QoS-related notification to the PCF, and the PCF may notify the AF.

[0379] In cases c) and d) described above, the SMF's request to the underlay base station (e.g., the SMF requests the underlay base station to provide the above QoS-related notification to the VMR UE or the SMF) may be based on one or more of the following being satisfied:

[0380] - SMF knows that it is serving the VMR UE.

[0381] - A UE (i.e., a VMR UE) can inform the SMF / PCF that it is a VMR.

[0382] - A UE (i.e., a VMR UE) requests and / or provides information about the request to the SMF / PCF. The request and / or information about the request that the VMR UE provides to the SMF / PCF may be provided / requested from the VMR's base station. The VMR's base station may generate information to be provided to the VMR UE based on QNC-related information or QoS Profile / parameter-related information provided from the SMF serving the UE it serves, or may generate information to be provided to the VMR UE based on a policy / configuration set for itself.

[0383] - The PDU Session of a UE (i.e., a VMR UE) may be based on the DNN and / or S-NSSAI for the VMR UE.

[0384] - The PDU Session of a UE (i.e., a VMR UE) may be based on the DNN and / or S-NSSAI (or NSSAI) for the N3 interface and / or N2 interface of the VMR.

[0385] - The AMF of a UE (i.e., a VMR UE) may provide information to the SMF / PCF that the UE is a VMR UE (e.g., this information may be authorized / allowed information about whether the UE can operate as a VMR).

[0386] - SMF can check VMR UE related information included in subscriber information of UE (i.e. VMR UE).

[0387] - SMF may be an SMF to support VMR UEs.

[0388] - SMF can perform the above request to the underlay base station based on the PCC rule instructed / provided by the PCF.

[0389] - Based on local configuration / policy or operator policy, the above request can be made to the underlay base station.

[0390] - VMR (or VMR UE or VMR RAN) can directly request SMF based on QoS notification method by using service such as Nnef_AFsessionWithQoS_Create to NEF of underlay network through application layer (e.g. acting as AF). This request can be forwarded to PCF through NEF. PCF can provide PCC rule including QNC to SMF based on conventional QNC method. And SMF can enable QNC to underlay base station. Based on this, SMF can receive QoS related notification from underlay base station.

[0391] In the examples described above, when a UE (i.e., a VMR UE) provides a request / information to an SMF / PCF, it can be interpreted that the UE provides information to the SMF, which then forwards it to the PCF.

[0392] For reference, the QoS-related notification requests and / or targets of QoS-related notifications described above can be based on various units, as follows:

[0393] - Some or all PDU Session(s) of the VMR UE: If some PDU Session(s) are present, for example, these may be PDU Session(s) for the N3 interface.

[0394] - PDU Session(s) corresponding to some or all DNNs of the VMR UE: In the case of some PDU Session(s), for example, this may be the PDU Session(s) corresponding to the DNN for the N3 interface.

[0395] - PDU Session(s) corresponding to some or all S-NSSAI (or NSSAI) of the VMR UE: In case of some PDU Session(s), for example, this may be PDU Session(s) corresponding to S-NSSAI (or NSSAI) for N3 interface.

[0396] - PDU Session(s) corresponding to some or all DNN / S-NSSAI combinations of the VMR UE: For some PDU Session(s), for example, this may be PDU Session(s) corresponding to DNN / S-NSSAI (or NSSAI) combinations for the N3 interface.

[0397] - QoS Flow(s) corresponding to some / specific or all 5QIs of the VMR UE

[0398] - QoS Flow(s) corresponding to the GBR type of the VMR UE (which may or may not include the Delay Critical GBR type).

[0399] The PDU Session and QoS Flow of the VMR UE may be interpreted as supporting / serving the PDU Session and QoS Flow of the UE served by the VMR. Alternatively, the PDU Session and QoS Flow of the VMR UE may be interpreted as supporting / serving the UE served by the VMR. Alternatively, the PDU Session and QoS Flow of the VMR UE may be interpreted as supporting / connecting the N3 interface of the VMR. Alternatively, the PDU Session and QoS Flow of the VMR UE may be interpreted as supporting / connecting the N2 interface of the VMR.

[0400] When a VMR UE or SMF requests QoS-related notification to an underlay base station, the VMR UE or SMF may explicitly or implicitly / implicitly express the target to which it wants to notify.

[0401] When a VMR UE or SMF requests QoS-related notification to an underlay BS, the VMR UE or SMF may request as follows. For example, the VMR UE or SMF may request only information about whether QoS is satisfied (i.e., QoS not satisfied, QoS satisfied again) to the underlay BS, like a QNC to which the conventional Alternative QoS Profile (AQP) is not applied. Alternatively, the VMR UE or SMF may request the underlay BS to also inform the level / index at which QoS is satisfied by providing Alternative QoS Profile information (e.g., this information may be the same as, extended from, or modified from the conventional information) to the QNC to which the conventional Alternative QoS Profile is applied.

[0402] The above QoS-related notifications may also be interpreted as conveying or providing QoS-related information. This may be applied throughout this specification.

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

[0404] A second example of the disclosure of this specification may include an operation in which a VMR UE forwards / provides QoS related notifications for an underlay base station to a base station (or a base station portion of the VMR) of the VMR.

[0405] According to the second example of the disclosure of this specification, when a VMR UE receives a QoS-related notification for an underlay base station from the underlay base station or an SMF, the VMR UE may forward the QoS-related notification to the base station portion of the VMR.

[0406] At this time, the VMR UE may provide / transmit to the VMR base station the same information as the QoS-related notification information received / acquired for the underlay base station, or modified information, or part of the information. The QoS-related notification information for the underlay base station that the VMR UE provides / transmits to the VMR base station may include one or more of the following information. Information such as the examples below may be provided / transmitted explicitly, implicitly, or implicitly. Including or separately from the information below, information that allows the VMR base station to know which UE the VMR base station serves, which PDU Session of which UE, or which QoS Flow of which UE is the QoS-related notification may also be included in the QoS-related notification information:

[0407] i) Information on which PDU Session for which QoS-related notification information is associated or applicable to which N3 interface (e.g., PDU Session identification information, PDU Session-related DNN information, PDU Session-related slice information, etc.)

[0408] ii) Information on which QoS-related notification information is associated with or corresponds to which QoS Flow(s) (e.g., QoS Flow identification information, QoS / QoS flow characteristics (e.g., delay / latency budget, error rate, throughput, etc.), QoS / Service requirements (e.g., delay / latency requirement, reliability requirement, throughput requirement, etc.))

[0409] iii) Information indicating that QoS cannot be satisfied

[0410] iv) Information on what level / level of QoS can be satisfied.

[0411] v) Information indicating that QoS can be satisfied again.

[0412] Additionally, the VMR UE may provide a QoS-related notification to the VMR base station, either explicitly or implicitly, indicating the subject of the QoS-related notification. The subject of the QoS-related notification may be related to various levels, as shown in the following examples:

[0413] A) VMR's underlay base station

[0414] B) VMR's N3 interface

[0415] C) VMR's N2 interface

[0416] D) A specific UE(s) or group of UEs served by the VMR.

[0417] E) Specific PDU Session(s) of a specific UE served by the VMR. If for multiple UEs, this may be in the form of a list.

[0418] F) Specific DNN(s) of a specific UE served by the VMR. This may be in the form of a list if it serves multiple UEs.

[0419] G) Specific S-NSSAI(s) of a specific UE served by the VMR. This may be in the form of a list if it is for multiple UEs.

[0420] H) A combination(s) of a specific DNN / S-NSSAI for a specific UE served by the VMR. This may be in the form of a list if it is for multiple UEs.

[0421] I) Specific 5QI(s) of all UEs served by VMR.

[0422] J) Specific 5QI(s) of a specific UE served by the VMR. If it is for multiple UEs, it may be in the form of a list.

[0423] K) Specific QoS Flow(s) for a specific UE served by the VMR. This may be in the form of a list if it is for multiple UEs.

[0424] A VMR base station can receive a QoS-related notification for an underlay base station from a VMR UE or through an application layer (e.g., the VMR application layer receives a notification when the underlay network notifies the AF). A VMR base station that receives a QoS-related notification for an underlay base station can make one of the following decisions based on the notification information (e.g., information related to the QoS-related notification). For example, a VMR base station can make one of the following decisions for a UE served by the VMR, for a PDU Session of a UE served by the VMR, or for a QoS Flow of a PDU Session of a UE served by the VMR. There may be multiple UEs involved in the decision made by the VMR base station, multiple PDU Sessions for a UE, or multiple QoS Flows for a PDU Session:

[0425] - Whether QoS cannot be satisfied

[0426] - At what level / levels can QoS be satisfied?

[0427] - Can QoS be satisfied again?

[0428] Alternatively, the VMR UE can directly monitor the QoS of the underlay network and determine whether the QoS required by the VMR RAN is supported, without receiving QoS-related notifications from the underlay network. If the VMR UE determines that QoS is not supported, it can notify the VMR RAN that QoS is not supported.

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

[0430] A third example of the disclosure of this specification may include actions that a VMR (e.g., a base station portion of the VMR) performs when it receives a QoS-related notification for an underlay base station.

[0431] When a VMR (e.g., the base station portion of the VMR) receives a QoS-related notification for an underlay base station, it may perform one or more of the following actions:

[0432] i) The VMR may decide to no longer serve additional UEs. This may be interpreted as the mobile base station not providing service to new UEs.

[0433] ii) The VMR can perform QoS-related notification to the SMF (i.e., the SMF serving the PDU Session of the UE) serving the UE related to the QoS-related notification (i.e., the UE corresponding to the QoS-related notification among the UEs served by the VMR itself). If there are multiple UEs and / or PDU Sessions related to the QoS-related notification, the base station part of the mobile base station can perform the notification to all related serving SMFs. The notification may be a conventional QNC operation or an extension / modification of the conventional QNC operation. Basically, the base station part of the mobile base station can notify the SMF that the QoS cannot be satisfied (which may also include information about an (Alternative) QoS level that can be satisfied, and which may also include information about a change in the (Alternative) QoS level that can be satisfied), and / or that the QoS can be satisfied again.

[0434] The VMR may reflect, consider, or incorporate information about its own QoS satisfaction and (alternative) QoS levels into QoS-related notification information / content for underlay base stations. For example, the VMR may transmit QoS-related notifications to the SMF based on such QoS-related notification information / content for underlay base stations.

[0435] For example, a VMR may be unable to satisfy the QoS for a QoS Flow of a UE it serves but may provide QoS at level / index 1, and an underlay base station may also be unable to satisfy the QoS for it but may provide QoS at level / index 2. In this case, the VMR may notify the SMF that it is unable to satisfy the QoS but may provide QoS at level / index 2. Alternatively, the VMR may notify the SMF that it is unable to satisfy the QoS but may provide QoS at level / index 3. Here, it is assumed that the larger the level / index number, the lower the QoS level provided.

[0436] As described above, the SMF, upon receiving a QoS-related notification from the VMR, can provide / forward this information (e.g., QoS-related notification) to the UE via an SM (Session Management) NAS message. At this time, the SMF can provide / forward the same information, modified information, or part of the information notified from the VMR to the UE.

[0437] iii) The VMR (e.g., the base station part of the VMR) can request the underlay network to create another PDU Session / QoS Flow for the N3 tunnel. To do this, the VMR (e.g., the base station part of the VMR) can request a PDU Session with different values ​​for DNN / S-NSSAI than the existing PDU Session for the N3 tunnel, or can request a change in values ​​such as 5QI / data rate of the QoS Flow. Of course, the VMR (e.g., the base station part of the VMR) can use the same DNN / S-NSSAI, or the same values ​​such as 5QI / data rate.

[0438] iv) The VMR (e.g., the base station portion of the VMR) can cause the VMR UE to perform PLMN selection to select a different underlay network.

[0439] v) The VMR (e.g., the base station portion of the VMR) can perform QoS-related notifications to the UEs corresponding to the QoS-related notifications (i.e., UEs related to the QoS-related notifications among the UEs served by the VMR itself). If there are multiple UEs related to the QoS-related notifications, the VMR (e.g., the base station portion of the VMR) can perform the notifications to all of the corresponding UEs. For the QoS-related notification information / contents, reference may be made to the example in ii) above.

[0440] The operations of the above iii) and iv) may be performed when the overlay network (e.g., MNO1 in FIG. 7) does not support QoS Notification Control and the underlay network (e.g., MNO2 in FIG. 7) supports QoS Notification Control (QNC), or may be performed when both networks support QNC.

[0441] 4. Fourth example of disclosure of this specification

[0442] A fourth example of the disclosure of this specification may include a procedure combining at least one of the examples of the first to third examples of the disclosure of this specification.

[0443] The description in Example 4 of the disclosure of this specification is merely exemplary, and the scope of the disclosure of this specification is not limited to Example 4 of the disclosure of this specification. For example, even if not described in Example 4 of the disclosure of this specification, operations described in various examples of the disclosure of this specification may be performed.

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

[0445] FIG. 13 is a specific example of a procedure according to one embodiment of the disclosure of the present specification.

[0446] Referring to the example of FIG. 13, the mobile base station may include a base station of the mobile base station (e.g., a VMR RAN) and a UE of the mobile base station (e.g., a VMR UE). The mobile base station may serve the UE shown on the left.

[0447] The underlay network for a mobile base station may include the RAN, AMF, SMF, and UPF. A mobile base station UE (e.g., a VMR UE) may perform registration procedures and PDU session establishment procedures with the underlay network.

[0448] The serving network of the UE may refer to the network serving the UE shown on the left side of the mobile base station.

[0449] In Fig. 13, a mobile base station (e.g., VMR), specifically a UE portion of the mobile base station (e.g., VMR UE), may be connected to a Home network or a Visited network.

[0450] 1. It is assumed that the VMR UE has registered with the 5G Core Network (e.g., the underlay network). Thereafter, the VMR UE can establish a PDU Session for the N2 interface (i.e., N2 PDU Session) and a PDU Session for the N3 interface (i.e., N3 PDU Session). The PDU Session for the N3 interface may be established when the base station part of the mobile base station (VMR RAN) serves the UE, or may be established when the serving UE establishes a PDU Session.

[0451] 2. A UE served by a VMR RAN can perform registration with a 5G Core Network (e.g., the UE's serving network).

[0452] 3. A UE served by VMR RAN can establish a PDU Session.

[0453] 4. The VMR UE may request the serving SMF to provide QoS-related information for the PDU Session for the N3 interface. For example, in Figure 13, the PDU Session Modification procedure may be used by the VMR UE to the SMF for this request. For example, the VMR UE may send a PDU Session Modification Request message to the SMF.

[0454] However, the disclosure of this specification is not limited to the PDU session modification procedure. For example, various SM NAS messages / procedures other than the PDU session modification procedure may be used. For details on requesting QoS-related information from the serving SMF, refer to the first example of the disclosure of this specification.

[0455] Alternatively, the VMR (or VMR-UE or VMR NG-RAN) can request specific QoS from the SMF through the NEF of the underlay network via the application layer (e.g., if the VMR acts as an AF). In this case, the actions according to steps 4-6 and steps 8-9 can be replaced by message exchanges between VMR <-> NEF of the underlay network <-> PCF of the underlay network <-> SMF of the underlay network. For this, the VMR can create a separate PDU Session, or use the PDU Session for the N2 / N3 interface, or use the PDU Session for OAM.

[0456] Between Steps 3 and 4, the PDU Session established by the UE served by the VMR RAN may be modified. For example, if the PDU Session was established without a GBR QoS Flow, this may be performed to add a GBR QoS Flow to the PDU Session through PDU Session modification.

[0457] 5. The serving SMF of the VMR UE may send a response message to the request to the VMR UE. For example, the SMF may send a PDU Session Modification Command message to the VMR UE.

[0458] The serving SMF may, while transmitting these SM NAS messages, request / instruct the serving base station of the VMR UE to provide QoS-related notifications. For example, the message transmitted in step 5 may include information indicating that the VMR UE will be provided with QoS-related information and information requesting the base station of the VMR UE to provide QoS-related notifications. For details on the operation of the SMF requesting / instructing the serving base station of the VMR UE, reference may be made to the contents of the first example of the disclosure of this specification.

[0459] 6. The VMR UE may send an acknowledgment message (e.g., a PDU Session Modification Command ack message) to the serving SMF.

[0460] 7. A change in the QoS satisfaction / level for the VMR UE may occur at the serving base station of the VMR UE (e.g., the QoS cannot be satisfied). Then, the serving base station of the VMR UE may transmit a QoS-related notification to the SMF of the VMR UE. For details on the QoS-related notification, refer to the first example of the disclosure of this specification.

[0461] 8. When the serving SMF of the VMR UE receives the QoS-related notification, it can provide / forward it to the VMR UE. For example, the serving SMF can transmit a PDU session modification command message containing information related to the QoS-related notification to the VMR UE. Although FIG. 13 illustrates that the SMF uses the PDU Session Modification procedure to the VMR UE for such provision / forwarding, this is merely an example. However, the scope of the disclosure of the present specification is not limited by the PDU session modification command message. For example, other than the PDU session modification command message, various SM NAS messages / procedures can be used. For details on the provision / forwarding of the QoS-related information, refer to the contents of the first example of the disclosure of the present specification.

[0462] 9. The VMR UE may send an acknowledgment message (e.g., a PDU Session Modification Command ack message) to the serving SMF.

[0463] 10. A VMR UE that has received QoS-related information from the serving SMF can provide QoS-related information for a PDU session for the N3 interface to the VMR RAN. For details on the provision of the QoS-related information, refer to the second example of the disclosure of this specification.

[0464] 11. The VMR RAN may perform QoS-related notifications to the SMF serving the UE related to the QoS-related information. For example, the VMR RAN may perform QoS-related notifications to the SMF serving the UE corresponding to the QoS-related information / notification (i.e., the UE corresponding to the QoS-related notification among the UEs served by the VMR itself) (i.e., the SMF serving the PDU Session of the UE). For further details, please refer to the third example of the disclosure of this specification.

[0465] 12. When the serving SMF of the UE receives the above QoS-related notification, it can provide / forward it to the UE. For example, the serving SMF of the UE can transmit a PDU Session Modification Command message containing QoS-related information to the UE. Although Fig. 13 illustrates that the SMF uses the PDU Session Modification procedure to the UE for such provision / forwarding, this is merely an example. The scope of the disclosure of the present specification is not limited by the PDU Session Modification Command message. For example, other than the PDU Session Modification Command message, various SM NAS messages / procedures can be used. For details on the provision / forwarding of the above QoS-related information, refer to the contents of the third example of the disclosure of the present specification.

[0466] Afterwards, a change related to the QoS satisfaction / level for the VMR UE may occur at the serving base station of the VMR UE (e.g., the QoS may be satisfied again). Then, the serving base station of the VMR UE may perform a QoS-related notification to the SMF of the VMR UE regarding this QoS-related change. In this case, step 8 of FIG. 13 and subsequent operations may be performed.

[0467] The method proposed in this specification may be interpreted as including an operation of aligning or synchronizing QoS notification control between a VMR base station and an underlay base station.

[0468] When a VMR UE or SMF requests QoS-related notifications to an underlay base station, existing procedures, messages / parameters, etc. that the SMF uses to perform QNC-related requests to the NG-RAN may be utilized, extended, or modified. Alternatively, new procedures, messages / parameters, etc. may be defined. In particular, for a VMR UE to request QoS-related notifications to an underlay base station, existing RRC messages may be extended and used, or new RRC messages may be defined.

[0469] When an underlay base station provides QoS-related notifications to a VMR UE or SMF, the procedures, messages, and parameters used by existing NG-RANs to notify the SMF of QNC-related information can be utilized, extended, or modified. New procedures, messages, and parameters can also be defined. In particular, existing RRC messages can be extended and used to notify VMR UEs of QoS-related information from the underlay base station, or new RRC messages can be defined.

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

[0471] FIG. 14 illustrates an example of a procedure performed according to one embodiment of the disclosure of the present specification.

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

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

[0474] According to the example of Fig. 14, a mobile base station may include a UE and a base station. The UE included in the mobile base station of Fig. 14 may also perform a relay role, allowing the mobile base station to provide services as a mobile base station to the UE it serves.

[0475] Before step (S1401) is performed, the UE of the mobile base station may perform a registration procedure, as illustrated in the example in FIG. 13. In addition, the base station of the mobile base station may also perform a registration procedure and a PDU session establishment procedure with the UE served by the mobile base station.

[0476] In step (S1401), the mobile base station can transmit a session establishment request message to the SMF.

[0477] For example, a UE in a mobile base station may transmit a session establishment request message to an SMF. For example, a UE in a mobile base station may transmit a PDU session establishment request message to a network node (e.g., an SMF) involved in the session to establish a PDU session.

[0478] In step (S1402), the SMF may transmit a session establishment acceptance message to the mobile base station.

[0479] For example, the SMF may transmit a Session Establishment Accept message to a UE in a mobile base station. A PDU session is established by the UE in the mobile base station, and the PDU session may be used by a base station in the mobile base station to serve the UE.

[0480] In step (S1403), the mobile base station can transmit a request message.

[0481] For example, a UE in a mobile base station may transmit a request message related to a PDU session to the SMF. For example, the request message may be a PDU Session Modification Request message.

[0482] At step (S1404), the SMF can transmit a response message.

[0483] For example, the SMF may transmit a response message related to a PDU session to the mobile base station via the base station serving the UE of the mobile base station. For example, the SMF may transmit a response message related to a PDU session to the UE of the mobile base station. For example, the response message may be a PDU session modification command message.

[0484] For example, the response message may include information requesting a notification related to the QoS from the base station serving the mobile base station.

[0485] At step (S1405), the base station serving the UE of the mobile base station may transmit a QoS notification (or notice) to the SMF.

[0486] In step (S1406), the SMF may transmit a NAS message containing information related to QoS to the mobile base station.

[0487] For example, the SMF may transmit an NAS message containing QoS-related information to the UE of the mobile base station.

[0488] For example, a UE of a mobile base station can transmit information related to QoS to the base station of the mobile base station.

[0489] For example, a message transmitted by a UE of a mobile base station to a base station of the mobile base station may include information related to QoS and information for identifying a target of QoS.

[0490] For example, information for identifying a target of QoS may include at least one of information about some or all of the PDU sessions related to a UE of a mobile base station (e.g., a first UE), information about PDU sessions related to some or all of the Data Network Names (DNNs) related to the first UE, information about PDU sessions related to some or all of the network slices related to the first UE, information about PDU sessions related to some or all of the combinations of network slices and DNNs related to the first UE, QoS flow information related to some or all of the 5G QoS Identifiers (5QIs) related to the first UE, and / or QoS flow information related to a Guaranteed Bit Rate (GBR) type of the first UE.

[0491] For example, the QoS-related information provided to the base station of the mobile base station may include at least one of information about a PDU session related to the QoS-related information, information about a QoS flow related to the QoS-related information, information about whether the QoS cannot be satisfied, information about what level of QoS can be satisfied, and information about whether the QoS can be satisfied again.

[0492] According to one embodiment of the disclosure of the present specification, an SMF or VMR UE (e.g., a UE of a mobile base station) may request QoS-related notifications from a base station of the VMR UE (i.e., an underlay base station).

[0493] According to one embodiment of the disclosure of the present specification, a base station (i.e., an underlay base station) of a VMR UE can perform QoS-related notification.

[0494] According to one embodiment of the disclosure of the present specification, when a VMR UE receives a QoS-related notification for the underlay base station, the VMR UE may forward the QoS-related notification to the VMR base station.

[0495] According to one embodiment of the disclosure of the present specification, a VMR base station can transmit a QoS-related notification to an SMF of a UE served by the VMR.

[0496] This specification may have various effects.

[0497] A mobile base station can effectively and / or accurately provide services to a UE. For example, a mobile base station can serve a UE by considering not only its own QoS satisfaction but also the QoS satisfaction of the underlay base station.

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

[0499] For reference, the operation of the terminal (e.g., UE) described in this specification may be implemented by the devices of FIGS. 1 to 3 described above. For example, the terminal (e.g., UE) may be the first device (100) or the second device (200) of FIG. 2. For example, the operation of the terminal (e.g., UE) described in this specification may be processed by one or more processors (102 or 202). The operation of the terminal described in this specification may be stored in one or more memories (104 or 204) in the form of instructions / programs (e.g., instructions, executable codes) executable by one or more processors (102 or 202). One or more processors (102 or 202) may control one or more memories (104 or 204) and one or more transceivers (105 or 206), and execute instructions / programs stored in one or more memories (104 or 204) to perform operations of a terminal (e.g., UE) described in the disclosure of this specification.

[0500] In addition, commands for performing operations of a terminal (e.g., UE, relay UE, vehicle relay UE) described in the disclosure of this specification may be stored in a non-volatile computer-readable storage medium. The storage medium may be included in one or more memories (104 or 204). In addition, the commands recorded in the storage medium may be executed by one or more processors (102 or 202) to perform operations of a terminal (e.g., UE) described in the disclosure of this specification.

[0501] For reference, the operation of a network node (e.g., AMF, SMF, UPF, PCF, V-UPF, etc.) or a base station (e.g., a mobile base station, VMR, NG-RAN, gNB, etc.) described in this specification may be implemented by the devices of FIGS. 1 to 3 described below. For example, the network node or the base station may be the first device (100) or the second device (200) of FIG. 2. For example, the operation of the network node or the base station described in this specification may be processed by one or more processors (102 or 202). The operation of the terminal described in this specification may be stored in one or more memories (104 or 204) in the form of instructions / programs (e.g., instructions, executable codes) executable by one or more processors (102 or 202). One or more processors (102 or 202) may control one or more memories (104 or 204) and one or more transceivers (106 or 206), and execute instructions / programs stored in one or more memories (104 or 204) to perform operations of a network node or base station as described in the disclosure of this specification.

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

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

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

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

Claims

1. A step of transmitting a PDU session establishment request message to establish a Protocol Data Unit (PDU) session to a network node involved in the session; A step of receiving a PDU session establishment acceptance message from the network node; A step of transmitting a request message related to the above PDU session to the above network node; The above request message includes information requesting notification related to Quality of Service (QoS) related to the PDU session; A step of receiving a response message related to the PDU session from the network node; and comprising a step of receiving a Non Access Stratum (NAS) message containing information related to QoS from the network node; A method characterized in that information related to the above QoS is provided to a base station included in the mobile base station by a first User Equipment (UE) included in the mobile base station.

2. In paragraph 1, The above PDU session is established by the first UE included in the mobile base station, and A method characterized in that the above PDU session is used by a base station included in the mobile base station to serve a second UE.

3. In paragraph 1 or 2, A method characterized in that a message transmitted by a first UE included in the mobile base station to a base station included in the mobile base station includes information related to the QoS and information for identifying a target of the QoS.

4. In paragraph 3, Information for identifying the target of the above QoS is: A method characterized in that it includes at least one of information about some or all of the PDU sessions related to the first UE, information about the PDU sessions related to some or all of the Data Network Names (DNNs) related to the first UE, information about the PDU sessions related to some or all of the network slices related to the first UE, information about the PDU sessions related to some or all of the combinations of the network slices and DNNs related to the first UE, QoS flow information related to some or all of the 5G QoS Identifiers (5QIs) related to the first UE, and / or QoS flow information related to the Guaranteed Bit Rate (GBR) type of the first UE.

5. In any one of paragraphs 1 to 4, The information related to the QoS provided to the base station included in the above mobile base station is: A method characterized in that it includes at least one of information about a PDU session related to the information related to the QoS, information about a QoS flow related to the information related to the QoS, information about whether the QoS cannot be satisfied, information about what level of QoS can be satisfied, and information about whether the QoS can be satisfied again.

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

7. At least one processor; and At least one memory storing instructions and being operably electrically connected to the at least one processor, An apparatus, wherein the operation performed based on the above instruction being executed by the at least one processor is a method according to any one of claims 1 to 5.

8. A non-transitory computer-readable storage medium that records commands, The above instructions, when executed by one or more processors, cause the one or more processors to: A CRM that performs a method according to any one of claims 1 to 5.

9. A step of receiving a PDU session establishment request message for establishing a Protocol Data Unit (PDU) session from a mobile base station including a first User Equipment (UE); A step of transmitting a PDU session establishment acceptance message to the mobile base station; A step of receiving a request message related to the above PDU session from the mobile base station; The above request message includes information requesting notification related to Quality of Service (QoS) related to the PDU session; A step of transmitting a response message related to the PDU session to the mobile base station via the base station serving the first UE; The above response message includes information requesting the base station to provide notification related to the QoS; A step of receiving a notification related to the QoS from the base station; and Comprising a step of transmitting a Non Access Stratum (NAS) message containing information related to QoS to the mobile base station, A method characterized in that information related to the above QoS is provided to a base station included in the mobile base station by a first User Equipment (UE) included in the mobile base station.

10. In paragraph 9, The above PDU session is established by the first UE included in the mobile base station, and A method characterized in that the above PDU session is used by a base station included in the mobile base station to serve a second UE.

11. In paragraph 9 or 10, A method characterized in that a message transmitted by a first UE included in the mobile base station to a base station included in the mobile base station includes information related to the QoS and information for identifying a target of the QoS.

12. In paragraph 11, Information for identifying the target of the above QoS is: A method characterized in that it includes at least one of information about some or all of the PDU sessions related to the first UE, information about the PDU sessions related to some or all of the Data Network Names (DNNs) related to the first UE, information about the PDU sessions related to some or all of the network slices related to the first UE, information about the PDU sessions related to some or all of the combinations of the network slices and DNNs related to the first UE, QoS flow information related to some or all of the 5G QoS Identifiers (5QIs) related to the first UE, and / or QoS flow information related to the Guaranteed Bit Rate (GBR) type of the first UE.

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

Images