Communication based on mobile base station

Abstract

One disclosure of the present specification provides a method. The method comprises the steps of: receiving a registration request message from a UE; transmitting a registration acceptance message to the UE; receiving a UL NAS Trasport message from a base station of a mobile base station; and transmitting a PDU session establishment request message and information related to a first network entity to a second network entity related to a session.

Description

Communication based on 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] Methods for providing services to terminals through mobile base stations are being discussed. However, conventional technology has the problem of not being able to effectively provide services to terminals when mobile base stations are located in roaming networks.

[0006] In one aspect, a method is provided. The method may include: receiving a registration request message from a UE; transmitting a registration acceptance message to the UE; receiving a UL NAS Transport message from a base station of the mobile base station; and transmitting a PDU session establishment request message and information related to the first network entity to a second network entity associated with the session.

[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 first NAS message from a UE, the first NAS message including a registration request message; transmitting the first NAS message to an AMF; receiving a second NAS message from the AMF, the second NAS message including a registration acceptance message; transmitting the second NAS message to the UE; receiving a PDU session establishment request message from the UE; and transmitting a UL NAS Transport message to a second network entity associated with mobility.

[0009] In another aspect, a device for 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 a third example of an architecture related to a mobile base station according to the disclosure of this specification.

[0019] FIG. 11 is a fourth example of an architecture related to a mobile base station according to the disclosure of this specification.

[0020] FIG. 12 illustrates a first example of a procedure according to one embodiment of the disclosure of the present specification.

[0021] FIG. 13 illustrates a second 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 may 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., MWABs). 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., MWAB). For example, a relay node includes all gNBs and co-located UEs. 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 to specific deployment scenarios for vehicle-mounted relays, such as those using MWAB where IAB is not widely supported, or those where the relay handles local traffic on 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, and fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[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 through 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 sufficient 5G spectrum or RAN / network infrastructure, they can use MNO2's mobile network to connect 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] 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).

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

[0237] A mobile base station (e.g., MWAB or vehicle relay) belonging to MNO1 can access the base station and 5GC of MNO2, create a PDU session, and connect the N2 / N3 interfaces to the 5GC of MNO2 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 MNO2.

[0238] Additionally, when the mobile base station is in a non-roaming state, the mobile base station can connect to the base station and 5GC of MNO1 to create a PDU session. Through the created PDU session, the mobile base station can also operate as a base station by connecting the N2 / N3 interfaces 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] Various scenarios related to mobile base stations are described with reference to examples of FIGS. 8 to 10.

[0241] In the examples of FIGS. 8 to 10, the Vehicle Relay is referred to as MWAB (Mobile gNB with wireless access backhauling).

[0242] In the examples of FIGS. 8 to 10, the bold line between the MWAB-UE and the 5GC represents PDU Session(s) for tunneling N2 / N3 interfaces of the MWAB-gNB. "PDU Session(s) for tunneling N2 / N3 interfaces of the MWAB-gNB" may refer to a PDU session for the MWAB-UE to create the N2 / N3 interfaces of the MWAB-gNB in ​​order to perform the MWAB operation. The dotted line between the MWAB-gNB and the 5GC represents N2 / N3 interfaces of the MWAB-gNB tunneled through PDU Session(s). "N2 / N3 interfaces of the MWAB-gNB tunneled through PDU Session(s)" may refer to the N2 / N3 interfaces established by the MWAB-gNB through the PDU session of the MWAB-UE.

[0243] Additionally, an MWAB may connect its Xn interface to other base stations. The base station to which an MWAB connects its Xn interface may be an MWAB or a non-MWAB base station (e.g., a conventional base station, typically a stationary base station or a fixed base station).

[0244] A method is needed to manage / support the Xn interface connection of MWAB with mobility compared to the Xn interface connection between existing base stations.

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

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

[0247] The example in Fig. 8 illustrates an example of a scenario in which the MWAB is in a non-roaming state. The MWAB-UE establishes a PDU session via 5GC, and the MWAB-gNB can create an N2 / N3 interface based on the PDU session. The MWAB-gNB can be connected to other MWABs or gNBs via the Xn interface.

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

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

[0250] The example in Figure 9 shows an example of a scenario where the MWAB is in a roaming state.

[0251] The MWAB-UE establishes a PDU session through the 5GC of the visited network, and the MWAB-gNB can create the 5GC and N2 / N3 interfaces of the home network based on the PDU session of the MWAB-UE.

[0252] MWAB-gNB can be connected to other MWABs or gNBs via the Xn interface.

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

[0254] FIG. 10 is a third example of an architecture related to a mobile base station according to the disclosure of this specification.

[0255] The example in Figure 10 shows an example of a scenario where the MWAB is in a roaming state.

[0256] The MWAB-UE establishes a PDU session through the 5GC of the visited network, and the MWAB-gNB can create the 5GC and N2 / N3 interfaces of the visited network based on the PDU session of the MWAB-UE.

[0257] MWAB-gNB can be connected to other MWABs or gNBs via the Xn interface.

[0258] Additionally, an architecture such as the example in Fig. 11 may need to be supported to support edge computing using MWAB.

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

[0260] FIG. 11 is a fourth example of an architecture related to a mobile base station according to the disclosure of this specification.

[0261] The example in Fig. 11 is an example of an architecture for MWAB onboard MEC support. Referring to the example in Fig. 11, the MWAB may include a UPF.

[0262] To support this architecture, the 5GC must be aware of UPF information in the MWAB. Furthermore, an N4 interface must be created for UPF selection and configuration in the MWAB. However, prior art cannot support this architecture.

[0263] For example, when a MWAB is roaming, the PLMN of the mobile base station is not the serving PLMN of the terminal, making it difficult to provide edge computing services. One way for a mobile base station to support edge computing for terminals is to include a UPF within the mobile base station. However, conventional technology has the problem of not being able to support this architecture.

[0264] The disclosure of this specification describes an example of a method for supporting a structure such as the example of FIG. 11.

[0265] For reference, we describe an example of a method for using co-located UPFs in PDU Sessions in W-AGF. For example, the W-AGF can use UL NAS Transport to inform the SMF of UPF information so that the SMF can be aware of co-located UPFs in the W-AGF.

[0266] The disclosure of this specification describes various examples of methods for supporting onboard UPF included in MWAB.

[0267] Describes an example of Fixed Wireless Access.

[0268] For 5G-RGs connected to 5GC via NG-RAN, the following applies:

[0269] - UE corresponds to 5G-RG (5G Residential Gateway).

[0270] - 5G-RG can support LTE access and EPC interworking connected to EPC as defined in TS 23.501 V18.0.0, section 5.17. This can be controlled by SMF selection subscription data as defined in Table 5.2.3.3.1-1 of TS 23.502 V18.0.0.

[0271] - 5G-RG settings are applied through the ACS server.

[0272] - Home routing roaming is supported for 5G-RG connected via NG RAN.

[0273] - 5G Multi-Operator Core Network (5G MOCN) is supported for 5G-RG connected via NG RAN.

[0274] - The LADN service defined in section 5.6.5 of TS 23.501 V18.0.0 applies to 5G-RGs connected to 5GCs via 3GPP access. The specifications in section 5.6.5 of TS 23.501 V18.0.0 apply to 5G-RGs with the following differences:

[0275] - For UE settings update procedure, refer to the procedure in TS 23.316 V18.0.0 section 7.2.3.1.

[0276] - 5G-RG is registered via both 3GPP access and W-5GAN, and AMF can receive W-AGF ID from AGF. In this case, AMF can also provide W-AGF ID to SMF when forwarding N1 SM container transmitted by 5G-RG via 3GPP access.

[0277] Note that when 5G-RG transmits a PDU session establishment request message via 3GPP access, the SMF may receive W-AGF information. In this case, depending on the operator's configuration, the SMF may select a UPF deployed with the W-AGF based on the W-AGF information.

[0278] For example, an NG-RAN node may transmit an uplink NAS transport message to the AMF, which carries NAS information. Here, the uplink NAS transport message may include a message type, an AMF UE NGAP ID, a RAN UE NGAP ID, NAS-PDU, user location information, and W-AGF identifier information. The W-AGF identifier information may include a WAgfInfo IE. The WAgfInfo IE may include at least one of the address parameters ipv4EndpointAddresses, ipv6EndpointAddresses, and endpointFqdn.

[0279] In this specification, UE (User Equipment) and terminal are used interchangeably.

[0280] In this specification, the terms Subscriber and User are used interchangeably.

[0281] In this specification, NG-RAN, RAN, base station, NR base station, LTE base station, gNB, eNB, ng-eNB, etc. are used interchangeably to describe.

[0282] In this specification, Mobile gNB with wireless access backhauling (MWAB or mWAB or MgWAB) and Vehicle Relay, Vehicle-Mounted Relay (VMR), Relay, Mobile Relay, MBSR (Mobile Base Station Relay), eMBSR (enhanced MBSR), mobile base station, etc. are used interchangeably to describe them.

[0283] In this specification, the underlay base station of MWAB, the base station that MWAB connects to connect N2 / N3 interfaces to 5GC, the base station of MWAB-UE, the base station that serves MWAB-UE, and the base station that MWAB-UE connects to are used interchangeably to describe.

[0284] In this specification, the underlay Core Network of MWAB, the Core Network to which MWAB connects / registers to connect N2 / N3 interfaces to 5GC, the Core Network of MWAB-UE, the Core Network serving MWAB-UE, and the Core Network to which MWAB-UE connects / registers are used interchangeably.

[0285] In this specification, an underlay network may be interpreted as including one or more of an underlay base station and an underlay core network.

[0286] In this specification, the terms MWAB base station, MWAB base station part, MWAB-gNB, MWAB base station, MWAB base station part, MWAB RAN, MWAB NG-RAN, etc. are used interchangeably to describe.

[0287] In this specification, the N2 interface is described interchangeably with the NG-C interface, NGAP (NG Application Protocol) interface, and N2 tunnel, and the N3 interface is described interchangeably with the NG-U interface and N3 tunnel.

[0288] In this specification, the Xn interface is described interchangeably with the connection between base stations.

[0289] In this specification, Xn setup, Xn interface connection, connection (setup) with other base stations, connection (setup) between base stations, etc. are used interchangeably.

[0290] MWABs can be mounted on a variety of 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. MWABs mounted on aerial vehicles may be referred to as Aerial MWABs or Aerial Vehicle Relays (AVRs). Furthermore, MWABs do not necessarily need to be mobile; they can also function as base stations while stationary.

[0291] MWAB can serve not only UEs within the vehicle / MWAB but also surrounding UEs.

[0292] MWAB can use various RATs to serve UEs (e.g., NR, LTE, 6G RAT, etc.).

[0293] A MWAB may include a UE or MT (Mobile Terminal) part. This may be interpreted as the MWAB including either a UE part / operation / functionality or a MT (Mobile Terminal) part / operation / functionality. This may be referred to as MWAB-UE or MWAB-MT.

[0294] 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, and the proposed methods may be performed or used in combination or complementary manner.

[0295] The various examples proposed in this specification can be applied to both cases where an MWAB is connected to a PLMN and provides services, and cases where it is connected to an NPN and provides services. When an MWAB is connected to an NPN and provides services, the PLMN ID can be interpreted by replacing it with NPN identification information. Specifically, when an MWAB is connected to an SNPN and provides services, the PLMN ID can be interpreted by replacing it with SNPN identification information (PLMN ID and NID identifying an SNPN).

[0296] The operations and contents described herein as being performed by the MWAB-UE or MWAB base station may be interpreted as operations and contents performed by the MWAB. Alternatively, the operations and contents performed by the MWAB may be specifically performed by the MWAB-UE or MWAB base station.

[0297] In this specification, the definition / operation of conventional IAB-based VMR (MBSR), registration procedure, PDU Session related procedure, UE Configuration Update (UCU) procedure, etc. refer to TS 23.501 V18.0.0, TS 23.502 V18.0.0, etc., and Xn related operation / procedure / message, including Xn setup procedure, can refer to TS 38.423 V18.0.0. In addition, N4 association can be PFCP association, and the related procedure can refer to TS 29.244 V18.0.0.

[0298] In this specification, detailed descriptions of the same content as the prior art are omitted, and the description will focus on matters proposed in the disclosure of this specification.

[0299] Hereinafter, a first example of the disclosure of the present specification will be described with reference to the example of FIG. 12.

[0300] According to a first example of the disclosure of this specification, the MWAB can notify onboard UPF information to the network.

[0301] For reference, in the disclosure of this specification, onboard UPF may mean a UPF that is in (or included in, or mounted on) the MWAB.

[0302] If the MWAB has an onboard UPF, the MWAB can advertise information related to the onboard UPF to the network.

[0303] For example, when a UE transmits a PDU Session Establishment Request, the MWAB-gNB can transmit information related to the UPF in the MWAB to the AMF using the UL NAS Transport. For example, when the MWAB-gNB receives a PDU Session Establishment Request message from the UE, the MWAB gNB can transmit a UL NAS Transport message containing the PDU Session Establishment Request and information related to the UPF in the MWAB to the AMF.

[0304] For example, when an AMF receives information related to a UPF in an MWAB, it can transmit the information related to the UPF to the SMF together with the PDU Session Establishment Request.

[0305] For example, the SMF can perform UPF selection while processing a PDU Session Establishment Request. In this case, the SMF can perform UPF selection by considering the UPF-related information in the MWAB.

[0306] For example, before the SMF selects a UPF in the MWAB and creates a PDU Session, the SMF may need to create an N4 association with the UPF in the MWAB. To support this, the MWAB can create a PDU Session for the SMF and UPF to create the N4 association. Regarding this PDU Session, the MWAB can create the same PDU Session as the PDU Session for the N2 / N3 interface or create a new PDU Session.

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

[0308] FIG. 12 illustrates a first example of a procedure according to one embodiment of the disclosure of the present specification.

[0309] Figure 12 shows an example in which UPF information included in MWAB is provided based on an N2 message.

[0310] For reference, in the examples of FIG. 12 and FIG. 13, MWAB may include MWAB-gNB, MWAB-UE, and MWAB-UPF.

[0311] MWAB can be non-roaming or roaming.

[0312] Although FIG. 12 illustrates a PLMN, the HPLMN and / or VPLMN in the example of FIG. 12 may also be NPNs. This can be applied throughout this specification.

[0313] 1. MWAB-UE can send a Registration Request message to AMF to perform registration.

[0314] For example, an MWAB-UE may include information related to MWAB operation (e.g., information indicating that it wishes to perform an MWAB operation) in an RRC message and / or a Registration Request message. The base station may receive the RRC message and / or the Registration Request message from the MWAB-UE. Based on the information related to MWAB operation (e.g., information indicating that it wishes to perform an MWAB operation), the base station may select an AMF that supports MWAB.

[0315] Additionally, the MWAB-UE may transmit a message including information related to the onboard UPF (e.g., information indicating that the MWAB has an onboard UPF), capabilities, etc., in the RRC message and / or Registration Request message.

[0316] The AMF can obtain subscriber information for MWAB-UEs from the UDM. For example, the subscriber information may include information regarding whether edge computing is permitted for MWAB. For example, the subscriber information may include information indicating that edge computing is permitted based on the DNN / S-NSSAI combination, or information indicating that edge computing is permitted separately, regardless of the DNN / S-NSSAI.

[0317] For example, subscriber information may also include information (e.g., DNN, S-NSSAI, etc.) for MWAB to form (or establish) a PDU Session for use in an N4 association (or PFCP association).

[0318] For example, the information for forming a PDU Session for use in an N4 association may be different from, or may be the same as, or partially the same as, the information for forming a PDU Session for use in an MWAB NG setup.

[0319] 2. AMF can send a Registration Accept message to MWAB-UE.

[0320] At this time, the AMF may provide the MWAB-UE with information (e.g., DNN, S-NSSAI, SMF address, etc.) for the MWAB to form a PDU Session for use in the N4 association and / or information related to whether the MWAB can create an N4 association and whether edge computing services are allowed (or whether the settings are allowed / instructed) (the information described in step 1 may be provided as is or in a modified form).

[0321] For example, the registration accept message may contain information for forming a PDU Session for use in an N4 association (e.g., DNN, S-NSSAI, SMF address, etc.) and / or information regarding whether the MWAB can create an N4 association and whether edge computing services are allowed (or allowed / instructed to be set up).

[0322] During the MWAB-UE registration process, the AMF may perform authorization to allow edge computing services via the MWAB based on subscriber information, local configuration, operator policy, and messages / information received in step 1. If edge computing services via the MWAB are allowed / authorized, the AMF may provide the MWAB with information to establish a PDU Session for use in the N4 association.

[0323] 3. MWAB-UE can form a PDU Session to be used for N4 association.

[0324] For example, an MWAB-UE may send a PDU Session Establishment Request message to establish a PDU Session to be used for N4 association.

[0325] For the parameters used in the PDU Session Establishment Request message, the MWAB-UE can use the values ​​received from the AMF. Alternatively, the MWAB-UE can determine the parameters used in the PDU Session Establishment Request message based on the URSP rules, local configuration, etc. that the MWAB-UE has.

[0326] These actions may be performed if the MWAB is permitted (i.e. authorized) to perform the actions. Alternatively, these actions may be performed if the MWAB is permitted / instructed to establish an N4 association connection (e.g., the AMF may have provided information regarding the establishment of an N4 association connection, or the MWAB may have been instructed to establish an N4 association connection).

[0327] Additionally, these actions may be performed after MWAB has successfully performed / completed configuration setup / update with the OAM server.

[0328] The MWAB can receive the configuration required for MWAB operation through the OAM server. For example, it can receive TA information and cell information that the MWAB should use. Furthermore, the MWAB can receive PDU session-related information (e.g., DNN, S-NSSAI) required for the MWAB to connect to the N4 association through the OAM server. To receive this information, the MWAB can send the OAM server information indicating that it has an onboard UPF, capabilities, etc.

[0329] The PDU Session established in step 3 may be a Local Breakout PDU Session as shown in Fig. 12, or a Home Routed PDU Session.

[0330] A PDU Session for an N4 association may also be used for NG interfaces (N2 and / or N3). Alternatively, a PDU Session for an NG interface (N2 and / or N3) may also be used for an N4 association. This can be applied throughout this specification.

[0331] 4. MWAB-UPF can perform procedures for creating an N4 Association (N4 Session Establishment, PFCP Association Setup) for the SMF. At this time, MWAB-UPF can select an SMF based on the information received in step 2 or through the OAM server. If there is no information about the SMF, step 4 can be performed in step 8.

[0332] 5. The UE can perform registration through MWAB-gNB.

[0333] For example, the UE may send a registration request message to the AMF via the MWAB-gNB. The AMF may send a registration accept message to the UE via the MWAB-gNB.

[0334] 6. The UE can transmit a PDU Session Establishment Request including values ​​such as DNN and S-NSSAI to create a PDU Session.

[0335] An MWAB-gNB that receives a PDU Session Establishment Request can transmit a NAS message (e.g., a UL NAS Transport message) containing the PDU Session Establishment Request to the AMF.

[0336] At this time, the MWAB-gNB can transmit information related to the onboard UPF in the MWAB-gNB to the AMF. For example, information related to the onboard UPF can be transmitted in various forms, such as the onboard UPF's IP address information and FQDN information.

[0337] For example, the MWAB-gNB may send a NAS message (e.g., a UL NAS Transport message) containing information related to the PDU Session Establishment Request and onboard UPF to the AMF.

[0338] The MWAB-gNB may transmit information related to the onboard UPF to the AMF based on the MWAB-UE receiving information during the registration process indicating that it can create an N4 association (or information indicating that edge computing is allowed).

[0339] 7. AMF can trigger a service (e.g., Nsmf_PDUSession_CreateSMContext service) to create an SM context related to the PDU session in order to send a PDU Session Establishment Request to the SMF.

[0340] At this time, if there is information related to UPF received from MWAB-gNB, AMF can transmit the information related to UPF to SMF together.

[0341] For example, the AMF may transmit information related to UPF received from the MWAB-gNB to the SMF based on whether onboard UPF use is permitted based on subscriber information or local configuration. The UPF-related information may be information at the MWAB level or at the DNN / S-NSSAI level.

[0342] 8. The SMF can perform UPF selection and N4 Session Establishment procedures. The SMF can select the onboard UPF in the MWAB-gNB.

[0343] For example, the SMF's selection of an onboard UPF in the MWAB-gNB may be performed based on subscriber information, local configuration, PCC rules, etc., which allow onboard UPF for a specific DNN / S-NSSAI. If the N4 Association does not yet exist (e.g., step 4 has not yet been performed), the SMF may perform the N4 Association Setup procedure with the MWAB-UPF and then perform the N4 Session Establishment procedure.

[0344] 9. SMF can trigger Namf_Communication_N1N2MessageTransfer to send a PDU Session Establishment Accept message. For example, SMF can send a PDU Session Establishment Accept message to AMF.

[0345] 10. AMF can send PDU Session Establishment Accept to UE. For example, AMF can send PDU Session Establishment Accept to UE via MWAB-gNB.

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

[0347] According to the second example of the disclosure of this specification, the MWAB can register information related to the onboard UPF with the NRF.

[0348] For example, if an MWAB has an onboard UPF, the MWAB can register the onboard UPF with the NRF. When registering information related to the UPF with the NRF, the MWAB can additionally add information indicating that the UPF is an MWAB onboard UPF.

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

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

[0351] According to the example of Fig. 13, information related to the UE included in the MWAB can be provided to the NRF.

[0352] 1~3. It can be performed in the same manner as steps 1 to 3 of Fig. 12.

[0353] 4a. The MWAB UPF can register UPF-related information with the NRF. This information may include the DNN and S-NSSAI information supported by the UPF. Additionally, this information may include information indicating that the UPF is connected to the MWAB, information indicating that edge computing is supported through the MWAB, the ID information of the MWAB gNB, and TA / TAI information of the MWAB-gNB.

[0354] The PDU session used when the MWAB UPF transmits information to the NRF may be the PDU Session created for the N4 interface in step 3 or a separate PDU Session. If a separate PDU Session needs to be created, the information required to create the PDU Session can be obtained in the same way as the PDU Session parameters for the N4 interface described in steps 1 to 3.

[0355] 4b. SMF can receive information related to MWAB UPF from NRF through Nnrf_NFManagement_NFStatusNotify.

[0356] For example, before step 4b is performed, it is assumed that the SMF has subscribed to a service that receives notifications when a UPF for a specific DNN, S-NSSAI is registered by performing Nnrf_NFManagement_NFStatusSubscribe with NRF. This procedure can also be performed when the SMF is created, regardless of the procedure above. When the MWAB UPF is registered with NRF in step 4a, the corresponding information (e.g., information related to the UPF) can be delivered to the SMF via Nnrf_NFManagement_NFStatusNotify.

[0357] 4c. The SMF can perform the N4 Association Setup procedure for the UPF. This procedure can be performed immediately after the SMF receives the notification from the NRF in step 4b, or before step 8, after the terminal requests a PDU Session via MWAB.

[0358] 5. The UE can perform registration through the MWAB-gNB. During this process, the MWAB-gNB transmits information indicating that it is an MWAB and MWAB-gNB information (e.g., MWAB-gNB ID) to the AMF, and the AMF may store this information.

[0359] 6. The UE can transmit a PDU Session Establishment Request containing values ​​such as DNN and S-NSSAI to create a PDU Session. The MWAB-gNB that receives the PDU Session Establishment Request can transmit a NAS message (e.g., a UL NAS Transport message) containing the PDU Session Establishment Request to the AMF.

[0360] At this time, the MWAB-gNB can include information indicating that it is an MWAB-gNB and MWAB-gNB information (e.g. MWAB-gNB ID) in a UL NAS Transport message and transmit it to the AMF.

[0361] 7. AMF can trigger the Nsmf_PDUSession_CreateSMContext service to send a PDU Session Establishment Request to the SMF. At this time, AMF can send the SMF an Nsmf_PDUSession_CreateSMContext related message containing information indicating that the terminal is receiving service through the MWAB-gNB.

[0362] The operation of step 7 may be performed based on information stored in the terminal's context in step 5, or based on information provided by the MWAB-gNB in ​​step 6.

[0363] 8. The SMF performs UPF selection and N4 Session Establishment procedure. Based on subscriber information, local configuration, PCC rule, etc. that allows onboard UPF for a specific DNN / S-NSSAI, the SMF can select an onboard UPF in the MWAB-gNB. If the N4 Association does not yet exist (e.g., step 4 has not been performed), the SMF can perform the N4 Association Setup procedure for the MWAB-UPF and then perform the N4 Session Establishment procedure. The SMF can select a UPF through the NRF. At this time, when the SMF performs the UPF discovery procedure through the NRF, it may recognize that the UE is served through MWAB based on the information received in step 7, and request the SMF to select a UPF in the MWAB. To this end, the SMF may also input information about the MWAB-gNB (e.g., MWAB-gNB ID) or transmit TA / TAI information used by the MWAB-gNB to the NRF.

[0364] 9~10. It can be performed in the same manner as steps 9 and 10 of Fig. 12.

[0365] In the disclosure of this specification, the onboard UPF may create one or more SMFs and N4 Associations. For example, if there are multiple SMFs responsible for a specific DNN / S-NSSAI, the onboard UPF may create an N4 Association with each SMF.

[0366] After the MWAB onboard UPF creates the SMF and N4 Association, the liveness of each node can be checked by periodically performing the Heartbeat Procedure as described in TS 29.244 V18.0.0.

[0367] If no terminals are serviced through MWAB and the N4 Association is maintained continuously, the MWAB onboard UPF may have to exchange unnecessary messages with the SMF due to the hearbeat procedure. To solve this problem, the MWAB onboard UPF can run an inactivity timer for PDU sessions serviced through the UPF. Alternatively, the MWAB onboard UPF can run a UPF level timer instead of a PDU session level timer to monitor whether there are terminals serviced through the MWAB onboard UPF. The MWAB onboard UPF may run the PDU session level timer or UPF level timer based on the SMF's settings, or the UPF may run it based on the operator's settings or local configuration. Based on the inactivity timer, if it determines that no terminals are serviced through the MWAB onboard UPF, the MWAB onboard UPF can run a PFCP Association Release to release the N4 association with the SMF. If necessary later (e.g., when a new terminal starts a service through MWAB or when existing terminals are RRC connected to MWAB), the MWAB onboard UPF can create an N4 association again.

[0368] When the MWAB onboard UPF is registered with the NRF, the MWAB onboard UPF can periodically send an update message to the NRF to notify its liveness. Therefore, even in this case, if it is determined that there is no terminal receiving service through the MWAB onboard UPF through the method described in the paragraph above, the MWAB onboard UPF can perform Nnrf_NFManagement_NFDeregister to the NRF to deregister the MWAB onboard UPF. Afterwards, if necessary (e.g., when a new terminal starts a service through the MWAB or existing terminals are RRC connected to the MWAB, etc.), the MWAB onboard UPF can register the MWAB onboard UPF with the NRF again.

[0369] When an MWAB is deauthorized, the MWAB onboard UPF can suspend the N4 Association or notify the NRF of the suspension, thereby aborting unnecessary liveness checks. If necessary (e.g., when a new terminal starts service via the MWAB or existing terminals establish RRC connections with the MWAB), the MWAB onboard UPF can resume the N4 Association or notify the NRF of the resume.

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

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

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

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

[0374] In the example of FIG. 14, the UE and base station included in the mobile base station may be referred to as MWAB-UE and MWAB-gNB, respectively.

[0375] In the example of FIG. 14, the first network entity may be a network entity that manages mobility. For example, the first network entity may be an AMF.

[0376] In the example of Figure 14, the second network entity may be a network entity that manages the session. For example, the second network entity may be an SMF.

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

[0378] For reference, before performing step (S1401), the UE of the mobile base station may perform a registration procedure.

[0379] For example, a UE of a mobile base station may transmit a registration request message to a first network entity. For example, the registration request message may include information related to the operation of the mobile base station and information that the mobile base station includes a network entity of the mobile base station.

[0380] For example, when a registration request message is received from a UE of a mobile base station, the first network entity can obtain subscriber information of the UE of the mobile base station.

[0381] For example, subscriber information may include information regarding whether a mobile base station is permitted to perform operations related to edge computing.

[0382] For example, the subscriber information may include information related to the creation of an N4 association between a network entity of the mobile base station (e.g., a network entity associated with the user plane) and the second network entity.

[0383] For example, the first network entity may perform authentication related to whether edge computing services through the mobile base station are allowed based on at least one of subscriber information of the UE of the mobile base station, local settings, operator policy, and the registration request message.

[0384] For example, a first network entity may send a registration accept message to a UE of a mobile base station.

[0385] For example, the registration acceptance message may further include information related to the creation of an N4 association.

[0386] In step (S1401), a UE receiving service through a mobile base station can transmit a registration request message to a first network entity.

[0387] For example, a UE receiving service through a mobile base station may transmit a registration request message to the base station of the mobile base station, and the base station of the mobile base station may transmit the registration request message to the first network entity.

[0388] In step (S1402), the first network entity can transmit a registration acceptance message to the UE receiving the service through the mobile base station.

[0389] For example, the first network entity may transmit a registration acceptance message to the base station of the mobile base station, and the base station of the mobile base station may transmit the registration acceptance message to the UE receiving service through the mobile base station.

[0390] In step (S1403), the base station of the mobile base station can transmit a NAS message to the first network entity.

[0391] For example, a UE receiving service through a mobile base station may transmit a PDU session establishment request message to the base station of the mobile base station. The base station of the mobile base station may transmit an NAS message (e.g., an UL NAS Transport message) containing the PDU session establishment request message and information related to a network entity related to the user plane of the mobile base station (e.g., information related to a network entity of the mobile base station) to a first network entity.

[0392] For example, information related to a network entity of a mobile base station may include IP address information for the network entity of the mobile base station, and / or Fully Qualified Domain Name (FQDN) information for the network entity of the mobile base station.

[0393] For example, prior to step (S1403), the UE of the mobile base station may have received information from the first network entity indicating that the mobile base station is permitted to perform operations related to edge computing. Based on this, the base station of the mobile base station may transmit information related to the network entity of the mobile base station to the first network entity.

[0394] At step (S1404), the first network entity can transmit a message to the second network entity.

[0395] For example, a first network entity may transmit a PDU session establishment request message and a message containing information related to the network entity of the mobile base station to a second network entity.

[0396] Based on information related to the network entity of the mobile base station, the network entity of the mobile base station may be selected as the network entity related to the user plane of the PDU session associated with the PDU session establishment request message. For example, based on information related to the network entity of the mobile base station, a second network entity may select the network entity of the mobile base station as the network entity related to the user plane of the PDU session.

[0397] Based on subscriber information or local settings of the UE of the mobile base station, use of the network entity of the mobile base station may be permitted. Based on the permission to use the network entity of the mobile base station, the first network entity may transmit information related to the network entity of the mobile base station to the second network entity.

[0398] According to one embodiment of the disclosure of this specification, the MWAB-UE may transmit information indicating the availability of onboard UPF and edge computing services during the registration process. The AMF may transmit information indicating the availability of onboard UPF and edge computing services to the MWAB-UE based on subscriber information.

[0399] According to one embodiment of the disclosure of the present specification, an MWAB-UE can create a PDU Session for an N4 interface based on information indicating that an onboard UPF, edge computing service is available, configuration, etc.

[0400] According to one embodiment of the disclosure of the present specification, when the MWAB-UE includes onboard UPF information in a UL NAS Transport message, the AMF can transmit the onboard UPF information to the SMF.

[0401] According to one embodiment of the disclosure of the present specification, the SMF can perform UPF selection based on onboard UPF information transmitted by the AMF. For example, the SMF can select the MWAB onboard UPF and create a PDU Session.

[0402] This specification may have various effects.

[0403] For example, a mobile base station can provide edge computing services to UEs.

[0404] For example, edge computing services can be supported using MWAB. For example, the network can provide edge computing services through the onboard UPF included in MWAB.

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

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

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

[0408] For reference, the operation of a network node (e.g., AMF, SMF, UPF, PCF, V-UPF, UDM, NRF, NWAB-UPF, etc.) or a base station (e.g., mobile base station, VMR, MWAB, MWAB-gNB, 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 base station may be the first device (100) or the second device (200) of FIG. 2. For example, the operation of a network node or base station described in this specification may be processed by one or more processors (102 or 202). The operation of a 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.

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

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

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

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

Claims

1. A step of receiving a registration request message from User Equipment (UE); A step of transmitting a registration acceptance message to the UE; A step of receiving an Uplink (UL) Non Access Stratum (NAS) Transport message including a PDU session establishment request message and information related to a first network entity included in the mobile base station from the base station of the mobile base station; The above first network entity is a network entity related to the user plane; and Comprising the step of transmitting a PDU session establishment request message and information related to the first network entity to a second network entity related to the session, A method wherein, based on information related to the first network entity, the first network entity is selected as the network entity related to the user plane of the PDU session related to the PDU session establishment request message.

2. In paragraph 1, A method wherein the information related to the first network entity includes IP address information of the first network entity or Fully Qualified Domain Name (FQDN) information of the first network entity.

3. In paragraph 1 or 2, A method in which information related to the first network entity is transmitted based on whether the first network entity is permitted to be used based on subscriber information or local settings of the UE of the mobile base station.

4. In any one of paragraphs 1 to 3, A step of receiving a registration request message from a UE of the mobile base station; and A method further comprising the step of transmitting a registration acceptance message to the UE of the mobile base station.

5. In any one of the 4 paragraphs, Further comprising a step of obtaining subscriber information of the UE of the above mobile base station, The above subscriber information includes information related to whether the mobile base station is permitted to perform operations related to edge computing.

6. In any one of paragraphs 1 to 5, A method further comprising a step of performing authentication related to whether edge computing service through the mobile base station is permitted based on at least one of subscriber information, local settings, operator policy, and the registration request message of the UE of the mobile base station.

7. One or more transmitters and receivers; one or more processors; and comprising one or more memories capable of storing instructions and being operable to the one or more processors; A device 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 6.

8. A step of receiving a first NAS message including a registration request message from the UE; A step of transmitting the first NAS message to AMF; Receiving a second NAS message including a registration acceptance message from the AMF; A step of transmitting the second NAS message to the UE; A step of receiving a PDU session establishment request message from a UE; and Comprising the step of transmitting an Uplink (UL) Non Access Stratum (NAS) Transport message including a PDU session establishment request message and information related to a first network entity included in the mobile base station to a second network entity related to mobility, Information related to the first network entity is transmitted to the third network entity involved in the session by the second network entity, A method wherein, based on information related to the first network entity, the first network entity is selected as the network entity related to the user plane of the PDU session related to the PDU session establishment request message.

9. In paragraph 8, A method wherein the information related to the first network entity includes IP address information of the first network entity or Fully Qualified Domain Name (FQDN) information of the first network entity.

10. In paragraph 8 or 9, A method in which information related to the first network entity is transmitted based on the UE of the mobile base station receiving information from the second network entity that the mobile base station is permitted to perform operations related to edge computing.

11. One or more transmitters and receivers; one or more processors; and comprising one or more memories capable of storing instructions and being operable to the one or more processors; A device 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 8 to 10.

Images