Communication related to mobile base station

Abstract

Disclosed is a method. The method may comprise the steps of: receiving, from an AMF, a request message related to a PDU session; transmitting a response message to the request message to the AMF; and transmitting a message including N2 information to the AMF.

Description

Communications related to mobile base stations

[0001] This specification relates to mobile communications.

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

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

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

[0005] A method for providing services to UEs based on their connection to a mobile base station is being discussed. However, conventional technology has the problem that services cannot be effectively provided to UEs when the mobile base station is in a roaming state.

[0006] In one aspect, a method is provided. The method may include: receiving a request message related to a PDU session from an AMF; transmitting a response message to the request message to the AMF; and transmitting a message including N2 information to the AMF.

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

[0008] In one aspect, a method is provided, the method comprising: receiving a PDU session establishment request message from a UE served by a mobile base station;

[0009] The method may include a step of transmitting a NAS forwarding message including the PDU session establishment request message to the AMF; and a step of receiving a PDU session resource setup request message including N2 information from the AMF.

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

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

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

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

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

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

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

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

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

[0019] FIGS. 10A to 10C are specific examples of a procedure according to one embodiment of the disclosure of the present specification.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0049] The first wireless device (100) may include at least one transceiver, such as a transceiver (106), at least one processing chip, such as a processing chip (101), and / or one or more antennas (108).

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

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

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

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

[0054] The second wireless device (200) may include at least one transceiver, such as a transceiver (206), at least one processing chip, such as a processing chip (201), and / or one or more antennas (208).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0079] - AUSF (Authentication Server Function)

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

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

[0082] - USDF (Unstructured Data Storage Function)

[0083] - NEF (Network Exposure Function)

[0084] - I-NEF (Intermediate NEF)

[0085] - NRF (Network Repository Function)

[0086] - NSSF (Network Slice Selection Function)

[0087] - PCF (Policy Control Function)

[0088] - SMF (Session Management Function)

[0089] - UDM (Unified Data Management)

[0090] - UDR (Unified Data Repository)

[0091] - UPF (User Plane Function)

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

[0093] - AF (Application Function)

[0094] - UE (User Equipment)

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

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

[0097] - NWDAF (Network Data Analytics Function)

[0098] - CHF (CHarging Function)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0128] Establishing a PDU session may involve:

[0129] - UE-initiated PDU session establishment procedure

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

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

[0132] - Network-triggered PDU session establishment procedure

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0173] - RSN (redundancy sequence number) parameter

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0198] Regarding mobile base stations, the following objectives need to be achieved. However, prior art lacks a method for effectively achieving these objectives.

[0199] Potential architectural and system-level improvements can be discussed to further enhance the functionality of vehicle-mounted base station relays. Specific goals include, for example:

[0200] - Identify gaps to support architectures that onboard full gNB / CU to relay and use PDU sessions for wireless backhauling of N2 / N3 interfaces.

[0201] - Enables mobility for all onboard gNBs / CUs of the relay using PDU sessions for wireless backhauling of N2 / N3 interfaces.

[0202] - Specifies architectural improvements to the options selected to enable relay authorization.

[0203] - Enable QoS support over backhaul by specifying architectural enhancements for the selected options.

[0204] - Enables cell ID / TAC management by specifying architectural enhancements for the selected options.

[0205] - Specifies architectural improvements to the options selected to enable UE location services and emergency services support.

[0206] - Enable NTN backhaul for VMR by specifying architectural enhancements for the selected options.

[0207] - Specifies architectural improvements for onboard services / edge computing access.

[0208] - Extend UAV capabilities to VR by specifying architectural improvements for selected options.

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

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

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

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

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

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

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

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

[0217] 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:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0232] Looking at the architecture of the mobile base station (e.g., vehicle relay) in the example of Fig. 7, the Vehicle Mounted Relay (VMR) is a relay belonging to MNO1. The mobile base station (e.g., VMR) connects to the base station and 5GC of MNO2 to create a PDU session. The mobile base station (e.g., VMR) connects the N2 / N3 interfaces to the 5GC of MNO1 through the created PDU session. The mobile base station (e.g., VMR) can operate as a base station directly connected to the 5GC of MNO1 through the N2 / N3 interfaces to the 5GC of MNO1. In this case, the Vehicle Mounted Relay broadcasts the SIB of MNO1 because the N2 / N3 interfaces are connected to MNO1. Therefore, terminals that receive the SIB transmitted by the mobile base station determine that they are located within the network coverage of MNO1. In other words, even if the terminal is actually located in the VPLMN, the terminal can be determined to be located within the network coverage of MNO1.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0250] Meanwhile, if a mobile base station (e.g., VMR) is in a roaming network, the terminal cannot receive edge computing services by connecting to the mobile base station (e.g., VMR).

[0251] This is because the mobile base station (e.g., VMR) must create N2 / N3 interfaces through the VMR's HPLMN 5GC. In addition, when the mobile base station (e.g., VMR) establishes a PDU session to create the N2 / N3 interface, the mobile base station (e.g., VMR) is likely to create a home-routed PDU session. For example, to prevent the connection between the internet network and the 5GC for the security of the 5GC, the mobile base station (e.g., VMR) can create a home-routed PDU session and connect the created PDU session to a specific DN that can connect to the 5GC. In this case, all traffic of the mobile base station (e.g., VMR) must always be transmitted to the HPLMN. Therefore, there is a problem that edge computing services, which are important for delay, cannot be provided to UEs connected to the mobile base station. For example, when edge computing services are provided, traffic between the UE and the network must be provided based on very short delays. However, according to the prior art, there is a problem that short delay cannot be supported because all traffic of the mobile base station must always be transmitted to the HPLMN.

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

[0253] A mobile base station (e.g., a VMR) may be located in a roaming network. In this case, the mobile base station may be in a roaming state. Conventional techniques have the problem that edge computing services cannot be provided to terminals connected to the mobile base station. This is because the mobile base station cannot establish sessions through the PLMN network. Furthermore, the terminal and the mobile base station establish sessions based on the N2 / N3 interface via the mobile base station's HPLMN 5GC. Sessions created in the HPLMN cannot effectively support edge computing services, which are sensitive to delay.

[0254] The examples of methods proposed in the disclosure of this specification may be composed of a combination of one or more of the following actions / configurations / steps. Furthermore, the examples of methods presented below may be performed or used in combination or complementary manner.

[0255] In this specification, UE (User Equipment) and terminal may be used as terms with the same meaning.

[0256] In this specification, the terms “Subscriber” and “User” may be used interchangeably.

[0257] In this specification, the terms Application Function (AF) and Application Server (AS) may be used interchangeably.

[0258] In the disclosure of this specification, Vehicle Mounted Relay (VMR) / Vehicle Relay / Relay / Mobile Relay, and mobile base station may all be used with the same meaning.

[0259] Mobile base stations (e.g., vehicle relays) can be mounted on various types 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. When mounted on an aerial vehicle, a mobile base station may be referred to as an Aerial Vehicle Relay (AVR). Furthermore, a mobile base station (e.g., vehicle relay) need not necessarily be mobile; it can also function as a base station while stationary.

[0260] Vehicle Relay can serve not only UEs within the vehicle but also UEs in the surrounding area.

[0261] Below, a mobile base station (e.g., a Vehicle Mounted Relay) may include a UE. This may be interpreted as the VMR including the UE part / operation / functionality or the MT (Mobile Terminal) part / operation / functionality.

[0262] A mobile base station (e.g., Vehicle Mounted Relay) can transmit SIB information after performing registration in 5GC.

[0263] According to the disclosure of this specification, when an Edge Computing service is required, the SMF can include information related to the Edge Computing service in N2 information and transmit the N2 information.

[0264] The SMF can provide edge computing to terminals. For example, for edge computing, the SMF helps terminals connect to nearby application servers based on their location. For example, the SMF selects a UPF based on the terminal's location and creates a user plane tunnel between the selected UPF and the base station.

[0265] However, when a terminal connects to the network via a VMR, the SMF cannot accurately determine the actual location of the terminal. This is because the location of the terminal connecting via the VMR varies depending on the location of the VMR.

[0266] According to the disclosure of this specification, when a VMR transmits a terminal's NAS signaling to the core network, the VMR always transmits its User Location Information (ULI) along with it. Upon receiving the VMR's ULI information, the AMF can forward it to the SMF. This allows the SMF to recognize that the terminal has connected via the VMR and determine the terminal's actual location.

[0267] Additionally, the SMF assumes that the PDU session created by the terminal is for edge computing services based on the DNN / S-NSSAI. For example, the terminal may send an NAS message to the SMF to create a PDU session. In this case, the NAS message may include a specific DNN / S-NSSAI associated with the PDU session creation request. Based on the DNN / S-NSSAI requested by the terminal, the SMF may determine that edge computing is necessary.

[0268] Based on this, the SMF can transmit N2 information to the VMR NG-RAN. For example, the N2 information transmitted by the SMF may include information related to the need for Edge Computing (or information indicating the need for access to a local DN, or information indicating the need for N3 user plane setup via an LBO PDU Session, etc.).

[0269] A UE of a mobile base station (e.g., VMR) that has received information from an SMF that Edge Computing is required can perform a procedure for establishing a PDU Session. For example, when establishing a PDU session, the UE of the mobile base station (e.g., VMR) can use a different DNN / S-NSSAI from the DNN / S-NSSAI that the mobile base station (e.g., VMR) used when creating the N2 interface. This is because, if the DNN / S-NSSAI used when creating the N2 interface is used, the mobile base station (e.g., VMR) establishes a home-routed PDU Session. The mobile base station creates an LBO PDU Session based on the different DNN / S-NSSAI. Unlike the conventional technology where the user plane is created up to the HPLMN based on the LBO PDU session, the user plane is created directly from the local network to the local DN, and traffic between the terminal and the network can be transmitted directly from the local network to the local DN.

[0270] Referring to FIGS. 10a to 10c, when an Edge Computing service is required, an example of SMF including information related to the Edge Computing service in N2 information and transmitting the N2 information is described.

[0271] For reference, the procedures illustrated in FIGS. 10A through 10C do not illustrate all steps of the registration procedure, but only some steps. Steps performed in the same manner as in the prior art are omitted from description. Procedures such as basic registration and PDU session establishment, which are not specifically described in FIGS. 10A through 10C, follow the procedures of TS 23.501 V18.3.0 and TS 23.502 V18.3.0.

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

[0273] FIGS. 10A to 10C are specific examples of a procedure according to one embodiment of the disclosure of the present specification.

[0274] According to FIGS. 10a to 10c, when an Edge Computing service is required, the SMF can transmit N2 information including information indicating that an Edge Computing service is required.

[0275] 1. A mobile base station UE (a UE included in a mobile base station) performs a registration procedure through the VPLMN. For example, the mobile base station UE may transmit a Registration Request message containing information indicating that it operates as a mobile base station (e.g., a vehicle-mounted relay).

[0276] 2. The AMF of the VPLMN obtains subscriber information from the UDM of the HPLMN and then performs Nudm_UECM_Registration. During this process, the AMF may include information indicating that the UE operates as a mobile base station (e.g., a vehicle-mounted relay), based on the information received in step 1.

[0277] 3. The AMF may send a Registration Accept message to a mobile base station UE (e.g., a vehicle mounted relay UE). The Registration Accept message may include information allowing the vehicle mounted relay UE to create N2 / N3 interfaces using PDU sessions and / or information allowing the vehicle mounted relay UE to operate as a mobile base station (e.g., a VMR). The Registration Accept message may also include DNN / S-NSSAI information to be used for the PDU sessions to create N2 / N3 interfaces to the HPLMN. Alternatively, the DNN / S-NSSAI information may be configured in the VMR. This DNN / S-NSSAI information may include separate information for LBO PDU sessions and Home Routed PDU sessions.

[0278] 4. A PDU session establishment procedure can be performed. Examples of specific procedures can be found in FIGS. 5 and 6.

[0279] For example, a mobile base station UE (e.g., a Vehicle Mounted Relay UE) may decide to establish a PDU session based on the information received in step 3. For example, the mobile base station UE may create a PDU session based on the DNN / S-NSSAI received in step 3, based on a URSP rule, or based on configured information. Here, the configured information may refer to DNN / S-NSSAI information required for the mobile base station UE to create a PDU session for creating an N2 / N3 interface.

[0280] Here, the PDU session may be a home routed PDU session. In this case, the anchor UPF belongs to the HPLMN. If the anchor UPF is selected based on the DNN / S-NSSAI, the UPF colocated to the AMF of the HPLMN may be selected. In order for the SMF (e.g., H-SMF) to select the anchor UPF colocated to the AMF, the mobile base station UE (e.g., the Vehicle Mounted Relay UE) may perform the following actions. For example, the mobile base station UE (e.g., the Vehicle Mounted Relay UE) may transmit a PDU Session Establishment Request message containing information indicating that the session is for establishing an N2 interface.

[0281] Additionally, the PDU session used to create the N2 interface and the PDU session used to create the N3 interface may be established separately. In this case, the Registration accept in step 3 may include PDU session creation information for the N2 interface (e.g., DNN / S-NSSAI) and PDU session creation information for the N3 interface (e.g., DNN / S-NSSAI). Each PDU session may be established as one local breakout PDU session and the other home routed PDU session. For example, the PDU session for the N2 interface may be established as a home routed PDU session, and the PDU session for the N3 interface may be established as a local breakout PDU session.

[0282] The SMF may send a PDU Session Establishment Accept message to the UE. For example, the SMF may include AMF address information for creating an N2 interface in the PDU Session Establishment Accept message. For example, information related to this N2 interface may be pre-configured in the SMF or included in the subscriber information of the Vehicle Mounted Relay UE. In another example, information related to the N2 interface may be configured in the mobile base station UE (e.g., the Vehicle Mounted Relay UE), and this information may be updated in the HPLMN. Alternatively, the VPLMN may send a registration request message containing information notifying that the mobile base station UE (e.g., the Vehicle Mounted Relay UE) operates as a Vehicle Mounted Relay. In this case, the AMF may send the AMF address for creating an N2 interface to the mobile base station UE (e.g., the Vehicle Mounted Relay UE) based on the local configuration or based on subscriber information obtained from the UDM.

[0283] Alternatively, if the AMF knows that the mobile base station UE is a UE operating as a mobile base station, it can use the preset DNN / S-NSSAI to create a PDU session when the mobile base station UE requests PDU Session Establishment. For example, the AMF may transmit the preset DNN / S-NSSAI to the SMF regardless of the DNN / S-NSSAI transmitted by the mobile base station UE. In this case, the PDU session can be created based on a DNN / S-NSSAI different from the DNN / S-NSSAI provided by the mobile base station UE. Since the SMF always includes the DNN / S-NSSAI information of the session in the PDU Session Establishment Accept message, the mobile base station UE receiving the PDU Session Establishment Accept message can know the DNN / S-NSSAI related to the actually created PDU session.

[0284] 5. The mobile base station (specifically, the mobile NG-RAN) performs the N2 Setup process. For example, the mobile base station (specifically, the mobile NG-RAN) can transmit an N2 Setup Request to the AMF based on the PDU session created in step 4.

[0285] 6. AMF can perform the N2 Setup process. For example, AMF can send an N2 Setup Response.

[0286] 7. A mobile base station (e.g., VMR) can initiate a SIB broadcast. Accordingly, the mobile base station can initiate a service for the UE.

[0287] 8. The UE performs the registration procedure through the NG-RAN of the mobile base station (e.g., VMR).

[0288] 9a. The UE transmits a PDU Session Establishment Request message. For example, the UE transmits an RRC message containing a PDU Session Establishment Request to the NG-RAN of the mobile base station to create a PDU session.

[0289] 9b. The base station of the mobile base station (e.g., NG-RAN) forwards the NAS message sent by the UE to the AMF. The base station of the mobile base station sends the User Location Information (ULI) of the UE (e.g., the cell ID, TAI, used by the VMR) and the ULI of the VMR (e.g., the cell ID, TAI, used by the VPLMN by the VMR) along with the NAS message. The base station of the mobile base station can also send information indicating that the UE is receiving service via the VMR to the AMF along with the NAS message.

[0290] For reference, in various examples disclosed in this specification, the base station of the mobile base station may omit information indicating that the terminal is served via VMR. For example, the AMF and / or SMF may determine that the UE is served by the mobile base station based on the location information of the UE, the location information of the mobile base station, and the DNN and S-NSSAI of the PDU session requested by the UE.

[0291] 9c. AMF can send a request message related to a PDU session (e.g., Nsmf_PDUSession_CreateSMContext Request) to SMF. The request message related to a PDU session can include the ULI of the terminal, the ULI of the VMR, and information indicating that the terminal is receiving service through the VMR. For example, AMF can send the ULI of the terminal, the ULI of the VMR, and information indicating that the terminal is receiving service through the VMR to SMF when sending a request message to SMF for an NAS message sent by the terminal.

[0292] 10. The SMF obtains subscriber information for the DNN / S-NSSAI requested by the UE from the UDM. The SMF can determine whether the PDU session based on the DNN / S-NSSAI requested by the UE should be created through the local DN (or for edge / localized service) based on local configuration, operator policy, and / or PCC rules received during the PCF association setup process. In addition, the subscriber information obtained from the UDM may include information on whether the UE is permitted to create a PDU session based on the local DN through a mobile base station (e.g., VMR). In this case, the SMF may also consider the subscriber information of the UE.

[0293] 11. SMF can send response messages related to the PDU session to AMF. For example, SMF can send a response to AMF's request by sending Nsmf_PDUSession_CreateSMContext Response to AMF.

[0294] 12. The SMF can send a message to the AMF to convey N2 information. For example, the SMF can send Namf_Communication_N1N2MessageTransfer to the AMF to transmit N2 information to the VMR NG-RAN. At this time, the SMF does not send PDU Session Establishment Accept. That is, the SMF sends Namf_Communication_N1N2MessageTransfer that does not include PDU Session Establishment Accept. By not including PDU Session Establishment Accept, after the SMF establishes a PDU session for edge computing in the VPLMN in step 14, the SMF can send the IP address information to be used by the terminal to the terminal in step 17.

[0295] Additionally, N2 information may include information indicating that a session should be created with a local DN (or that an LBO PDU session should be used, or that edge / localized services should be provided). The SMF may also transmit this information only when the VMR is in a roaming state. For example, the SMF may determine that the VMR is roaming based on the VMR's ULI.

[0296] 13. The AMF can forward the N2 information transmitted by the SMF in Step 12 to the VMR NG-RAN. For example, the AMF sends the N2 information to the VMR NG-RAN via the PDU SESSION RESOURCE SETUP REQUEST. The PDU SESSION RESOURCE SETUP REQUEST message may include an LBO indication. The LBO indication may mean, for example, information requesting the mobile base station to establish an LBO PDU session.

[0297] 14. The VMR can decide to establish a PDU session based on the N2 information. For example, the N2 information may include information indicating that the session should be created with a local DN. The VMR can decide to create a PDU session with the VPLMN network based on the information indicating that the session should be created with a local DN.

[0298] For example, the VMR UE can create a PDU session based on a preset DNN / S-NSSAI. Alternatively, the N2 information transmitted by the SMF may include a DNN / S-NSSAI to be used when creating a PDU session with the VPLMN network. In this case, the VMR UE can also create a PDU session based on the DNN / S-NSSAI included in the N2 information. Alternatively, the VMR UE can create a PDU session based on the DNN / S-NSSAI received through Registration Accept in step 3.

[0299] After a PDU session is created, the VMR UE can perform PDU Session Modification based on N2 information, if necessary. In this case, the VMR UE can request the creation of the required QoS flow.

[0300] 15. VMR NG-RAN can send the successfully performed and failed QoS information in step 14 to SMF by sending PDU SESSION RESOURCE SETUP RESPONSE. VMR NG-RAN can also inform SMF of the IP address information generated in step 14.

[0301] 16. AMF transmits the N2 information transmitted by NG-RAN to SMF.

[0302] 17. SMF sends PDU Session Establishment Accept to UE.

[0303] Alternatively, instead of a mobile base station creating an LBO PDU session, the mobile base station can create an HR PDU session. Furthermore, the SMF can utilize conventional HR-SBO (see TS 23.548 V18.0.0 for details). To achieve this, the HPLMN operator can configure the SMF selected when a mobile base station (e.g., VMR) creates a PDU session for the N3 interface to be the same SMF that manages the PDU session that the UE creates for the edge computing service. Based on this, the SMF allows the UE to create a session through the VMR. Furthermore, when edge computing services are required, the SMF can provide a PDU session based on HR SBO for the PDU session that the VMR UE uses for the N3 interface, thereby providing edge computing services.

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

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

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

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

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

[0309] Before step (S1101) is performed, the UE of the mobile base station may perform a registration procedure in the VPLMN, as illustrated in the examples in FIGS. 10a to 10c. In addition, the UE of the mobile base station may also perform a PDU session establishment procedure for performing mobile base station operations.

[0310] For example, a UE included in a mobile base station may send a registration request message to the AMF of the VPLMN that includes information indicating that the mobile base station is operating as a mobile base station.

[0311] For example, a mobile base station may receive a registration acceptance message from an AMF of a VPLMN.

[0312] For example, a registration acceptance message may include information allowing a UE included in a mobile base station to create an N2 interface and an N3 interface based on a PDU session and / or information allowing the mobile base station to operate as a mobile base station.

[0313] For example, a UE included in a mobile base station can perform a PDU session establishment procedure to create an N2 interface and an N3 interface.

[0314] In step (S1101), the UE can transmit a message to the mobile base station.

[0315] The message of step (S1101) may be a PDU session establishment request message.

[0316] For example, a mobile base station may receive a PDU session establishment request message from a UE served by the mobile base station.

[0317] In step (S1102), the mobile base station can transmit a NAS transport message to the AMF.

[0318] For example, a NAS transport message may be an UPLINK NAS Transport message.

[0319] For example, the NAS forwarding message may include location information of the UE and location information of the mobile base station.

[0320] At step (S1103), AMF can send a request message to SMF.

[0321] For example, the request message may be a request message related to a PDU session.

[0322] For example, the request message may be an Nsmf_PDUSession_CreateSMContext Request message.

[0323] For example, the request message may include a PDU session establishment request message transmitted by the UE, location information of the UE, and location information of the mobile base station.

[0324] For example, the SMF can determine that the UE is served by the mobile base station based on the location information of the UE, the location information of the mobile base station, and the DNN and S-NSSAI of the PDU session requested by the UE.

[0325] For example, the PDU session establishment request message may include the DNN and S-NSSAI requested by the UE. For example, the SMF may obtain subscriber information of the UE from the UDM based on the DNN and S-NSSAI.

[0326] For example, subscriber information may include information about whether the mobile base station is permitted to establish PDU sessions based on the local DN.

[0327] At step (S1104), the SMF may send a response message to the AMF.

[0328] The response message may be an Nsmf_PDUSession_CreateSMContext Response message.

[0329] At step (S1105), the SMF can transmit a message to the AMF.

[0330] For example, a message may contain N2 information.

[0331] For example, the SMF can determine that a mobile base station is roaming based on the mobile base station's location information.

[0332] For example, a message containing N2 information may be transmitted based on whether the mobile base station is roaming.

[0333] For example, based on local configuration, operator policy, and / or PCC rules, the SMF may decide whether to request the mobile base station to establish a PDU session based on the local DN.

[0334] For example, the N2 information may include information indicating that the PDU session should be established based on a local DN. For example, the N2 information may include information indicating that the PDU session should be established based on a local DN, information indicating that an LBO PDU session should be used, or information related to edge computing-based services or localized services.

[0335] For example, based on the SMF receiving the request message, the message containing the N2 information may not include a PDU session establishment accept message.

[0336] For example, N2 information can be used to request a mobile base station to establish a PDU session based on the local Data Network (DN).

[0337] The message of step (S1105) may be a Namf_Communication_N1N2 Message Transfer message.

[0338] At step (S1106), the AMF can transmit a message to the mobile base station.

[0339] The message of step (S1106) may be a PDU session resource setup request message.

[0340] For example, a mobile base station may receive a PDU Session Resource Setup Request message containing N2 information from the AMF.

[0341] For example, based on N2 information, a UE included in a mobile base station can perform a PDU session establishment procedure to establish a PDU session in a VPLMN to establish a PDU session based on a local DN.

[0342] According to one embodiment of the disclosure of the present specification, a mobile base station (e.g., a Vehicle Mounted Relay) can create an LBO PDU session in a VPLMN network based on information provided by an SMF.

[0343] This specification may have various effects.

[0344] For example, when a terminal receives services through a mobile base station (e.g., Vehicle Mounted Relay), Edge computing can be effectively supported.

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

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

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

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

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

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

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

[0352] 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 request message related to a Protocol Data Unit (PDU) session from the Access and Mobility management Function (AMF). The above request message includes a PDU session establishment request message transmitted by User Equipment (UE), location information of the UE, and location information of the mobile base station; a step of transmitting a response message to the above request message to the AMF; and Comprising the step of transmitting a message including N2 information to the AMF, Based on the receipt of the above request message, the message including the N2 information does not include a PDU session establishment acceptance message, and A method characterized in that the above N2 information is used to request the mobile base station to establish a PDU session based on a local Data Network (DN).

2. In paragraph 1, A method further comprising a step of determining that the UE is serviced by the mobile base station based on the location information of the UE, the location information of the mobile base station, the DNN of the PDU session requested by the UE, and the S-NSSAI.

3. In paragraph 1 or 2, Further comprising a step of determining whether to request the mobile base station to establish a PDU session based on the local DN based on local settings, operator policies, and / or PCC rules; 4. In any one of paragraphs 1 to 3, A method characterized in that the above N2 information includes information that the PDU session should be established based on a local DN.

5. In any one of paragraphs 1 to 3, A method characterized in that the above N2 information includes information that the PDU session should be established based on a local DN, information that an LBO PDU session should be used, or information related to a service based on edge computing or a localized service.

6. In any one of paragraphs 1 to 5, A method further comprising the step of determining that the mobile base station is roaming based on location information of the mobile base station.

7. In any one of paragraphs 1 to 6, A method characterized in that a message including the N2 information is transmitted based on the fact that the mobile base station is roaming.

8. In any one of paragraphs 1 to 7, The above PDU session establishment request message is characterized in that it includes the DNN and S-NSSAI requested by the UE, Further comprising a step of obtaining subscriber information of the UE from the UDM based on the DNN and the S-NSSAI, A method characterized in that the subscriber information includes information on whether the mobile base station is permitted to establish a PDU session based on the local DN.

9. 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 8.

10. A step of receiving a Protocol Data Unit (PDU) session establishment request message from a User Equipment (UE) served by a mobile base station; A step of transmitting a Non Access Stratum (NAS) forwarding message including the above PDU session establishment request message to the Access and Mobility management Function (AMF); The NAS transmission message includes location information of the UE and location information of the mobile base station; and comprising the step of receiving a PDU session resource setup request message including N2 information from the AMF; The above N2 information is included to request the Session Management Function (SMF) to the mobile base station to establish a PDU session based on the local Data Network (DN), The above N2 information does not include the PDU session establishment acceptance message, and A method characterized in that, based on the above N2 information, a UE included in the mobile base station performs a PDU session establishment procedure for establishing a PDU session in a Visited Public Land Mobile Network (VPLMN) to establish a PDU session based on a local DN.

11. In paragraph 10, A method characterized in that the above N2 information includes information that the PDU session should be established based on a local DN, information that an LBO PDU session should be used, or information related to a service based on edge computing or a localized service.

12. In paragraph 10 or 11, A method characterized in that the N2 information is received based on the mobile base station being roaming in a VPLMN.

13. In any one of paragraphs 10 to 12, A step of transmitting a registration request message including information indicating that the UE included in the mobile base station operates as a mobile base station to the AMF of the VPLMN; and Further comprising the step of receiving a registration acceptance message from the AMF of the VPLMN, A method characterized in that the registration acceptance message includes information allowing a UE included in the mobile base station to create an N2 interface and an N3 interface based on a PDU session and / or information allowing the mobile base station to operate as a mobile base station.

14. In any one of paragraphs 10 to 13, A method further comprising a step of a UE included in the mobile base station performing a PDU session establishment procedure for creating the N2 interface and the N3 interface.

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

16. At least one processor; and At least one memory storing instructions and being operably electrically connected to the at least one processor, An apparatus, wherein the operation performed based on the command being executed by the at least one processor is a method according to any one of claims 10 to 15.

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

Images