Mobile base station control

Abstract

One embodiment of the present disclosure provides a method by which an AMF performs communication. The method may comprise the steps of: receiving a registration request message from a UE included in a first mobile base station; receiving, from a UDM, subscriber information related to the first mobile base station; determining, on the basis of the subscriber information, whether to activate or inactivate the first mobile base station operating as a mobile base station; and transmitting, to the UE included in the first mobile base station, a response message of the registration request message.

Description

Mobile base station control

[0001] This specification relates to mobile communications.

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

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

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

[0005] A mobile base station (MBS) can mediate communications between UEs and the network. However, a method for the network to dynamically and effectively control the MBS has not been discussed.

[0006] A mobile base station can be enabled or disabled to operate as a mobile base station.

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

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

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

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

[0011] Figures 5 and 6 illustrate examples of registration procedures to which the implementation of the present specification applies.

[0012] Figures 7 and 8 illustrate examples of a PDU session establishment procedure to which the implementation of the present specification applies.

[0013] Figure 9 shows an example of the overall architecture of NG-RAN to which the implementation of this specification is applied.

[0014] Figure 10 shows an example of the overall architecture for separation of gNB-CU-CP and gNB-CU-UP to which the implementation of this specification applies.

[0015] FIG. 11 is a first example of a procedure according to one embodiment of the disclosure of the present specification.

[0016] FIG. 12 is a second example of a procedure according to one embodiment of the disclosure of the present specification.

[0017] FIG. 13 illustrates an example of operations related to a mobile base station according to one embodiment of the disclosure of the present specification.

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

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

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

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

[0022] 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."

[0023] 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.”

[0024] 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”.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0076] - AUSF (Authentication Server Function)

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

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

[0079] - USDF (Unstructured Data Storage Function)

[0080] - NEF (Network Exposure Function)

[0081] - I-NEF (Intermediate NEF)

[0082] - NRF (Network Repository Function)

[0083] - NSSF (Network Slice Selection Function)

[0084] - PCF (Policy Control Function)

[0085] - SMF (Session Management Function)

[0086] - UDM (Unified Data Management)

[0087] - UDR (Unified Data Repository)

[0088] - UPF (User Plane Function)

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

[0090] - AF (Application Function)

[0091] - UE (User Equipment)

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

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

[0094] - NWDAF (Network Data Analytics Function)

[0095] - CHF (CHarging Function)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0123] Describes the registration procedure. See section 4.2.2.2 of 3GPP TS 23.502 V16.3.0 (2019-12).

[0124] Figures 5 and 6 illustrate examples of registration procedures to which the implementation of the present specification applies.

[0125] A UE must register with the network to receive services, enable mobility tracking, and enable reachability. The UE initiates the registration process using one of the following registration types:

[0126] - Initial registration for 5GS; or

[0127] - mobility registration update; or

[0128] - Periodic registration update; or

[0129] - Emergency registration

[0130] The general registration procedures of Figures 5 and 6 apply to all registration procedures described above, but periodic registration updates do not need to include all parameters used in other registration procedures.

[0131] The general registration procedures of Figures 5 and 6 can also be used to register a UE for a 3GPP connection when it is already registered for a non-3GPP connection, and vice versa. Registering a UE for a 3GPP connection when it is already registered for a non-3GPP connection scenario may require an AMF change.

[0132] First, the procedure of Fig. 5 is described.

[0133] (1) Step 1: The UE transmits a Registration Request message to the (R)AN. The Registration Request message corresponds to an AN message.

[0134] The registration request message may include AN parameters. For NG-RAN, the AN parameters include, for example, the 5G SAE temporary mobile subscriber identity (5G-S-TMSI) or the globally unique AMF ID (GUAMI), the selected public land mobile network (PLMN) ID (or PLMN ID and network identifier (NID)), and the requested network slice selection assistance information (NSSAI). The AN parameters also include an establishment cause. The establishment cause provides the reason for requesting establishment of an RRC connection. Whether and how the UE includes the requested NSSAI as part of the AN parameters depends on the value of the access stratum connection establishment NSSAI inclusion mode parameter.

[0135] A registration request message may include a registration type. The registration type indicates whether the UE wants to perform an initial registration (i.e., the UE is in RM-DEREGISTERED state), or a mobility registration update (i.e., the UE is in RM-REGISTERED state and the registration procedure is initiated because the UE moves, or the UE wants to update its capabilities or protocol parameters, or because the UE requests a change in the set of network slices it is allowed to use), or a periodic registration update (i.e., the UE is in RM-REGISTERED state and the registration procedure is initiated because the periodic registration update timer has expired), or an emergency registration (i.e., the UE is in restricted service state).

[0136] When a UE performs initial registration, the UE indicates its UE ID in the registration request message, listed in decreasing priority order.

[0137] i) If the UE has a valid evolved packet system (EPS) globally unique temporary identifier (GUTI), 5G-GUTI mapped from the EPS GUTI;

[0138] ii) Native 5G-GUTI (if available) allocated by the PLMN in which the UE is attempting to register;

[0139] iii) Native 5G-GUTI allocated by a PLMN equivalent to the PLMN in which the UE is attempting to register;

[0140] iv) Native 5G-GUTI allocated by another PLMN (if available);

[0141] v) Otherwise, the UE includes a subscriber concealed identifier (SUCI) in the registration request message.

[0142] If a UE performing initial registration has both a valid EPS GUTI and a native 5G-GUTI, the UE also indicates the native 5G-GUTI as an additional GUTI. If more than one native 5G-GUTI is available, the UE selects a 5G-GUTI from items (ii)-(iv) in decreasing priority order in the list above.

[0143] When the UE performs initial registration with native 5G-GUTI, the UE indicates the relevant GUAMI information in the AN parameters. When the UE performs initial registration with SUCI, the UE does not indicate the GUAMI information in the AN parameters.

[0144] For emergency registration, if the UE does not have a valid 5G-GUTI, the SUCI is included. If the UE does not have a subscriber permanent identifier (SUPI) and does not have a valid 5G-GUTI, the PEI (Permanent Equipment Identifier) ​​is included. Otherwise, the 5G-GUTI is included, indicating the last serving AMF.

[0145] The registration request message may also include security parameters, PDU session status, etc. Security parameters are used for authentication and integrity protection. The PDU session status indicates a previously established PDU session in the UE. When the UE is connected to two AMFs belonging to different PLMNs via a 3GPP connection and a non-3GPP connection, the PDU session status indicates the PDU session currently established in the PLMN in the UE.

[0146] (2) Step 2: (R)AN selects AMF.

[0147] If 5G-S-TMSI or GUAMI is not included, or if 5G-S-TMSI or GUAMI does not indicate a valid AMF, the (R)AN selects an AMF based on the (R)AT and the requested NSSAI, if available.

[0148] When the UE is in CM-CONNECTED state, (R)AN can forward a registration request message to AMF based on the N2 connection of the UE.

[0149] If the (R)AN cannot select an appropriate AMF, the (R)AN performs AMF selection by forwarding a registration request message to the AMF configured in the (R)AN.

[0150] (3) Step 3: (R)AN sends a registration request message to the new AMF. The registration request message corresponds to the N2 message.

[0151] The registration request message may contain all of the information and / or part of the information contained in the registration request message received from the UE described in step 1.

[0152] The registration request message may include an N2 parameter. When NG-RAN is used, the N2 parameter includes the selected PLMN ID (or PLMN ID and NID), location information and cell ID related to the cell where the UE is camping, and a UE context request indicating that a UE context including security information should be established in the NG-RAN. When NG-RAN is used, the N2 parameter also includes an establishment cause.

[0153] If the registration type indicated by the UE is periodic registration update, steps 4-19 described below may be omitted.

[0154] (4) Step 4: If the UE's 5G-GUTI is included in the registration request message and the serving AMF has changed since the last registration procedure, the new AMF may invoke the Namf_Communication_UEContextTransfer service operation to the previous AMF, including the full registration request non-access stratum (NAS) message to request the UE's SUPI and UE context.

[0155] (5) Step 5: The old AMF can respond to the new AMF for the Namf_Communication_UEContextTransfer call including the UE's SUPI and UE context.

[0156] (6) Step 6: If SUCI is not provided by the UE or not retrieved from the previous AMF, the new AMF may initiate an ID request procedure by sending an Identity Request message to request SUCI from the UE.

[0157] (7) Step 7: The UE may respond with an Identity Response message including the SUCI. The UE derives the SUCI using the provided public key of the home PLMN (HPLMN).

[0158] (8) Step 8: The new AMF may decide to initiate UE authentication by calling the AUSF. In this case, the new AMF selects the AUSF based on SUPI or SUCI.

[0159] (9) Step 9: Authentication / security can be established by UE, new AMF, AUSF and / or UDM.

[0160] (10) Step 10: If the AMF has changed, the new AMF may call the Namf_Communication_RegistrationCompleteNotify service operation to notify the old AMF that the UE registration with the new AMF is complete. If the authentication / security procedure fails, the registration is rejected and the new AMF may call the Namf_Communication_RegistrationCompleteNotify service operation with a reject indication reason code to the old AMF. The old AMF may continue as if the UE context transfer service operation was not received.

[0161] (11) Step 11: If the PEI was not provided by the UE or was not retrieved from the previous AMF, the new AMF may initiate the ID request procedure by sending an Identity Request message to the UE to retrieve the PEI. The PEI is transmitted encrypted, except when the UE performs emergency registration and cannot be authenticated.

[0162] (12) Step 12: Optionally, the new AMF can initiate ME ID checking by calling the N5g-eir_EquipmentIdentityCheck_Get service operation.

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

[0164] (13) Step 13: When step 14 below is performed, the new AMF can select a UDM based on SUPI, and the UDM can select a UDR instance.

[0165] (14) Step 14: New AMFs can be registered with UDM.

[0166] (15) Step 15: New AMF can select PCF.

[0167] (16) Step 16: The new AMF may optionally perform AM policy association establishment / modification.

[0168] (17) Step 17: The new AMF can send update / release SM context messages (e.g., Nsmf_PDUSession_UpdateSMContext and / or Nsmf_PDUSession_ReleaseSMContext) to the SMF.

[0169] (18) Step 18: If the new AMF and the old AMF are in the same PLMN, the new AMF may send a UE context modification request to the N3IWF / TNGF / W-AGF.

[0170] (19) Step 19: N3IWF / TNGF / W-AGF may send a UE context modification response to the new AMF.

[0171] (20) Step 20: After the new AMF receives the response message from N3IWF / TNGF / W-AGF in step 19, the new AMF can register with UDM.

[0172] (21) Step 21: The new AMF sends a Registration Accept message to the UE.

[0173] The new AMF sends the UE a Registration Accept message indicating that the registration request has been accepted. If the new AMF allocates a new 5G-GUTI, it includes the 5G-GUTI. If the UE is already in the RM-REGISTERED state through another connection to the same PLMN, the UE uses the 5G-GUTI received in the Registration Accept message for both registrations. If the Registration Accept message does not include a 5G-GUTI, the UE uses the 5G-GUTI assigned to the existing registration for the new registration. If the new AMF allocates a new registration area, it sends the registration area to the UE in the Registration Accept message. If the Registration Accept message does not include a registration area, the UE considers the previous registration area to be valid. Mobility Restrictions are included if mobility restrictions apply to the UE and the registration type is not emergency registration. The new AMF indicates the PDU sessions established for the UE in the PDU Session State. The UE locally removes internal resources associated with PDU sessions that are not marked as established in the received PDU Session State. When a UE is connected to two AMFs belonging to different PLMNs via a 3GPP connection and a non-3GPP connection, the UE locally removes internal resources associated with PDU sessions in the current PLMN that are not marked as established in the received PDU session status. If PDU session status information is present in the Registration Accept message, the new AMF indicates the PDU session status to the UE.

[0174] The Allowed NSSAI provided in the Registration Accept message is valid for the registration area and applies to all PLMNs that have a tracking area included in the registration area. The Mapping of Allowed NSSAIs maps HPLMN S-NSSAIs to each S-NSSAI of the Allowed NSSAIs. The Mapping of Configured NSSAIs maps HPLMN S-NSSAIs to each S-NSSAI of the Configured NSSAI for the serving PLMN.

[0175] Additionally, optionally, the new AMF performs UE policy association establishment.

[0176] (22) Step 22: If the UE successfully updates itself, it can send a Registration Complete message to the new AMF.

[0177] The UE may send a registration complete message to the new AMF to confirm that a new 5G-GUTI has been allocated.

[0178] (23) Step 23: In case of registration via 3GPP connection, if the new AMF does not release the signaling connection, the new AMF may send RRC Inactive Assistance information to the NG-RAN. In case of registration via non-3GPP connection, if the UE is in CM-CONTENED state on the 3GPP connection, the new AMF may send RRC Inactive Assistance information to the NG-RAN.

[0179] (24) Step 24: AMF can perform information updates on UDM.

[0180] (25) Step 25: The UE may execute a network slice-specific authentication and authorization (NSSAA) procedure.

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

[0182] Figures 7 and 8 illustrate examples of a PDU session establishment procedure to which the implementation of the present specification applies.

[0183] Establishing a PDU session may involve:

[0184] - UE-initiated PDU session establishment procedure

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

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

[0187] - Network-triggered PDU session establishment procedure

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

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

[0190] In the procedures shown in FIGS. 7 and 8, 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.

[0191] First, the procedure of Fig. 7 is explained.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0228] - RSN (redundancy sequence number) parameter

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

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

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

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

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

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

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

[0236] Now, the procedure of Fig. 8 following the procedure of Fig. 7 is described.

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

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

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

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

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

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

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

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

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

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

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

[0248] (21) Step 21: If the PDU session establishment fails after step 4, the SMF may unsubscribe from modifications to the session management subscription data if the SMF no longer processes the UE's PDU session.

[0249] Figure 9 shows an example of the overall architecture of NG-RAN to which the implementation of this specification is applied.

[0250] Referring to FIG. 9, the Next Generation (NG)-RAN (Radio Access Network) consists of a set of gNBs connected to the 5GC via an NG interface. Alternatively, the NG-RAN may consist of a set of ng-eNBs, and the ng-eNBs may consist of an ng-eNB-CU and one or more ng-eNB-DUs. The ng-eNB-CU and ng-eNB-DU are connected via the W1 interface. The general principles for the overall architecture of the NG-RAN described below also apply to the ng-eNB and the W1 interface, unless explicitly stated otherwise.

[0251] gNBs can be interconnected via the Xn interface.

[0252] A gNB can consist of a gNB-CU (Central Unit) and one or more gNB-DUs (Distributed Units). The gNB-CU and gNB-DU are connected via the F1 interface. For convenience of explanation, the gNB-CU may be simply referred to as a CU, and the gNB-DU as a DU.

[0253] A gNB-CU is a logical node that hosts the RRC, SDAP, and PDCP protocols of a gNB or the RRC and PDCP protocols of an en-gNB, which control the operation of one or more gNB-DUs. The gNB-CU terminates the F1 interface connected to the gNB-DU.

[0254] The gNB-DU is a logical node that hosts the RLC, MAC, and PHY layers of a gNB or en-gNB, and its operation is partially controlled by the gNB-CU. A gNB-DU supports one or more cells. A cell is supported only by one gNB-DU. The gNB-DU terminates the F1 interface connected to the gNB-CU.

[0255] A single gNB-DU can be connected to only one gNB-CU. Alternatively, for resiliency, a gNB-DU can be connected to multiple gNB-CUs through appropriate implementation.

[0256] NG, Xn, and F1 are logical interfaces.

[0257] For NG-RAN, the NG and Xn-C interfaces for a gNB consisting of a gNB-CU and a gNB-DU terminate at the gNB-CU. For EN(E-UTRAN-NR)-DC(Dual Connectivity), the S1-U and X2-C interfaces for a gNB consisting of a gNB-CU and a gNB-DU terminate at the gNB-CU. The gNB-CU and the connected gNB-DU appear only as gNBs to other gNBs and the 5GC.

[0258] Figure 10 shows an example of the overall architecture for separation of gNB-CU-CP and gNB-CU-UP to which the implementation of this specification applies.

[0259] Referring to FIG. 10, a gNB may be composed of a gNB-CU-CP (Control Plane), multiple gNB-CU-UPs (User Planes), and multiple gNB-DUs. For convenience of explanation, gNB-CU-CP may be simply referred to as CU-CP, and gNB-CU-UP may be simply referred to as CU-UP.

[0260] The gNB-CU-CP is a logical node that hosts the control plane portion of the RRC and PDCP protocols of the gNB-CU for the en-gNB or gNB. The gNB-CU-CP terminates the E1 interface connected to the gNB-CU-UP and the F1-C interface connected to the gNB-DU.

[0261] The gNB-CU-UP is a logical node that hosts the user plane portion of the PDCP protocol of the gNB-CU for the en-gNB and the user plane portion of the PDCP protocol of the gNB-CU for the gNB and the SDAP protocol. The gNB-CU-UP terminates the E1 interface connected to the gNB-CU-CP and the F1-U interface connected to the gNB-DU.

[0262] The gNB-CU-CP is connected to the gNB-DU via the F1-C interface.

[0263] gNB-CU-UP is connected to gNB-DU via F1-U interface.

[0264] gNB-CU-UP is connected to gNB-CU-CP via E1 interface.

[0265] One gNB-DU is connected to only one gNB-CU-CP.

[0266] A single gNB-CU-UP can be connected to only one gNB-CU-CP. Alternatively, for resiliency, a gNB-DU and / or a gNB-CU-UP can be connected to multiple gNB-CU-CPs through appropriate implementation.

[0267] One gNB-DU can be connected to multiple gNB-CU-UPs under the control of the same gNB-CU-CP.

[0268] One gNB-CU-UP can be connected to multiple DUs under the control of the same gNB-CU-CP.

[0269] The connection between the gNB-CU-UP and the gNB-DU can be established by the gNB-CU-CP using bearer context management functions.

[0270] The gNB-CU-CP can select the appropriate gNB-CU-UP(s) for the requested service for the UE. In the case of multiple gNB-CU-UPs, they belong to the same security domain.

[0271] Data forwarding between gNB-CU-UP during intra-gNB-CU-CP handover within a gNB can be supported by Xn-U.

[0272] Support for mobile base stations (e.g., Mobile Base Station Relay (MBSR)) is being discussed. Note that in various examples disclosed in this specification, MBSR is an example of a mobile base station. The descriptions related to MBSR can be applied to mobile base stations.

[0273] The following example describes MBSR as defined in 3GPP TS 23.501v18.1.0.

[0274] MBSR can be defined as follows. For example, a mobile base station based on MBSR acts as a relay between a UE and a 5G network. Such an MBSR can be installed, for example, in a moving vehicle. The MBSR can serve UEs located inside or outside the vehicle, or as they enter or exit the vehicle. MBSR can be supported in the IAB architecture with mobility, as illustrated in the examples below, and in the 5GS described in TS 38.401 V17.3.0.

[0275] MBSR can be supported as follows:

[0276] MBSR can utilize the Integrated Access and Backhaul (IAB) architecture (e.g., the IAB architecture defined in Section 5.35 of TS 23.501 V18.1.0). When integrated with a serving PLMN, MBSR can operate as a mobile IAB node (e.g., including an IAB-UE and gNB-DU). Furthermore, the following restrictions may apply to MBSR:

[0277] - MBSR can have a single hop to the IAB-donor node.

[0278] - NR Uu can be used for wireless links between MBSR and served UEs and between MBSR and IAB-donor nodes.

[0279] Regulatory requirements (e.g., emergency services, priority services) can be supported when a UE accesses 5GS via MBSR. The LCS framework is used to provide location services to the served UE.

[0280] MBSR roaming is supported, meaning that MBSR can be integrated with IAB-donor nodes in VPLMNs.

[0281] The Closed Access Group (CAG) mechanism can be used to control UE access to MBSR.

[0282] For MBSR nodes, once the RRC connection is established, a mobile IAB-Indication can be provided to the IAB-donor-CU. Upon receiving the mobile IAB-Indication, the IAB-donor-CU can select an AMF that supports IAB-nodes with mobility. The IAB-donor-CU can send an N2 INITIAL UE MESSAGE containing the mobile IAB-Indication to the AMF. The AMF can then perform mobile IAB authorization.

[0283] After the IAB-UE performs the registration procedure in 5GS, it can change the IAB-donor-DU and IAB-donor-CU by performing additional mobility procedures.

[0284] Describes the settings related to MBSR.

[0285] For an MBSR to function as a mobile IAB node, it can receive configuration information from the OAM system of the serving PLMN. An MBSR IAB-UE establishes a secure and reliable connection to the OAM server only if it is authorized to function as an MBSR in the serving PLMN.

[0286] Additionally, for MBSR (IAB-UE) to perform PLMN selection, it is assumed that the HPLMN has a list of preferred PLMNs and forbidden PLMNs set.

[0287] The MBSR can use a PDU session to access an OAM server. In this case, the MBSR can establish a dedicated PDU session for OAM traffic. The serving PLMN provides an allowed NSSAI, and the serving PLMN can establish a PDU session for OAM server access based on the S-NSSAI requested by the MBSR and default values ​​in the DNN and / or subscription data. For the MBSR, the relevant settings can be (pre-)configured based on UE policy. Alternatively, the existing UE policy mechanism can be provided for the MBSR, including OAM access PDU session parameters for the authorized PLMN.

[0288] Describes mobility support for UEs served by MBSR.

[0289] UE mobility between fixed cells and MBSR cells can be supported.

[0290] Inter-gNB-DU mobility procedures defined in TS 38.401 V17.0.0 or handover procedures using Xn / N2 reference points defined in TS 23.502 V17.0.0 may be used.

[0291] For UEs in RRC_IDLE and RRC_INACTIVE states, if MBSR becomes out-of-service, the cell (re)selection procedure for RRC_IDLE and RRC_INACTIVE is used.

[0292] For UEs in RRC_CONNECTED state, if MBSR is out-of-service, or if MBSR moves to an area where relay services cannot be provided, the IAB node release procedure specified in TS 38.401 V17.0.0 is used.

[0293] If MBSR becomes out-of-service, the IAB-donor-CU can trigger a handover procedure when a UE connected to emergency services can receive MBSR service.

[0294] UE mobility between MBSR cells can be supported as follows. For example, the UE handles inter-MBSR cell mobility using existing procedures defined in TS 38.401, TS 23.502 or TS 38.304.

[0295] UE mobility when moving with an MBSR cell can be supported as follows. For example, the TAC broadcast by the mobile MBSR cell can be configured by the OAM or the donor CU. When the MBSR moves to a serving cell with a different TAC, the TAC broadcast by the MBSR may also change. A UE served by an MBSR cell may observe a change in TAC and / or cell ID even if it remains connected to the same MBSR. This behavior may trigger mobility registration if the new TAC is not in the TAI list of the RA.

[0296] MBSR authorization may be supported. For MBSR, it may specify whether the subscription information stored in HPLMN is authorized to operate as MBSR, and for what location and for how long.

[0297] If MBSR roaming is supported, a roaming agreement for MBSR operation exists between the VPLMN and the HPLMN, and the 5GC can utilize this agreement to authorize MBSR in the VPLMN. MBSR (IAB-DU) can integrate into the VPLMN and provide services using the IAB-node integration procedure or the IAB-donor gNB mobility procedure.

[0298] MBSR(IAB-UE) assumes that the HPLMN consists of a list of preferred PLMNs and forbidden PLMNs for MBSR tasks.

[0299] When an MBSR (IAB-UE) performs initial registration with a serving PLMN, it can transmit information requesting MBSR operation. The AMF approves the MBSR based on the subscription information and provides an MBSR approval indication to the NG-RAN. The MBSR uses the configuration information for MBSR operation to establish a connection with the OAM system.

[0300] As part of the registration procedure, the AMF of the MBSR may indicate to the MBSR IAB-UE that it is not capable of acting as an MBSR IAB node, in which case the AMF will not send an MBSR approval indication to the donor-gNB. The AMF may include this indication in the Registration Acceptance message (if the PLMN allows the MBSR IAB-UE to register with the PLMN) or in the Registration Rejection message (if the PLMN does not allow the MBSR IAB-UE to register with the PLMN).

[0301] Describes location service support for UEs served by MBSR.

[0302] When a UE accesses 5GS via MBSR, it can use location services as defined in TS 23.273. However, to provide accurate UE position estimation, the LMF must take into account the MBSR's location.

[0303] A method for providing cell ID / TAC for MBSR for services may be supported. The TAC and cell ID broadcast by the MBSR cell are set as specified in TS 38.470.

[0304] Describes UE access control for MBSR.

[0305] The CAG identifier is used to control UE access to MBSR (i.e., the mobile IAB node). Existing CAG mechanisms can be used to manage UE access to MBSR, with the following additional considerations:

[0306] - If the MBSR is permitted to operate as an IAB node for a PLMN, the MBSR is configured using a CAG identifier unique within the scope of this PLMN during communication with the serving PLMN OAM or a (pre-)configured mechanism. If the MBSR is (pre-)configured with a list of PLMNs permitted to operate as an MBSR, the corresponding CAG identifier for each PLMN is also configured in the MBSR.

[0307] - NG-RAN and 5GC support UE access control based on the CAG identifier associated with the MBSR cell and the allowed CAG identifier for UEs supporting CAG functionality.

[0308] - For UEs that do not support the CAG feature, NG-RAN and 5GC can manage access to MBSR using the CAG mechanism as well as other existing mechanisms (e.g. forbidden tracking regions).

[0309] NOTE 1: If CAG is supported for both MBSR and fixed private networks in a PLMN, the CAG identifier value of the MBSR cell must be different from the CAG identifier of the fixed cell and must be unique within the range of PLMN IDs.

[0310] - Time duration restriction information and location restriction information may be provided along with the CAG identifier for the MBSR to which the UE can access. An enhanced list of allowed CAGs may be provided to the UE and the AMF to prevent the UE from accessing MBSR cells outside the time-restricted or location-restricted area. For example, if the allowed time for a particular CAG for the UE expires or the UE leaves the area, the CAG for the UE is canceled by the network.

[0311] NOTE 2: Control of MBSR access to the serving network is based on general mobility restriction management based on subscription data from MBSR (e.g. IAB-UE).

[0312] Actions are being discussed whereby a VPLMN dynamically controls MBSR without responding to changes in MBSR-related subscriber information or subscriber information. For example, the controlling action is being discussed as enabling MBSR (e.g., enabling can be interpreted as making MBSR authorized or allowing it to operate as MBSR) or disabling MBSR (e.g., disabling can be interpreted as making MBSR unauthorized or not allowing it to operate as MBSR).

[0313] In the disclosure of this specification, the MBSR-related subscriber information may include information regarding whether the subscriber is authorized (or allowed) to operate as MBSR, whether the subscriber is authorized (or allowed) to operate as Mobile IAB (Integrated access and backhaul), or whether the subscriber is authorized (or allowed) to perform mobile operations for IAB. The description of MBSR-related subscriber information may be applied throughout this specification.

[0314] We describe examples of use cases for updating MBSR approval according to prior art.

[0315] After the UE registration process is completed, MBSR authorization may change. For example, subscription information may include location restrictions or authorization time or duration information, or there may be an update to subscription information and the AMF may receive a subscriber data update notification from the UDM.

[0316] AMF can allow MBSR authorization updates to optimize wireless networks. This allows operators to control MBSR operations at any time, regardless of subscription information, whenever necessary.

[0317] For example, this could apply to scenarios where subscription data allows the operation of an MBSR set in a specific area for a specific period of time, but a significant portion of this set operating in that area causes interference. Furthermore, dynamically activating and deactivating MBSR based on the number and distribution of MBSRs and UEs currently in an area (e.g., deactivating an MBSR set when there are no or few UEs in an area) could be useful for optimizing energy consumption, without changing the permitted locations in the subscription data.

[0318] Because operators don't know the future movements of MBSRs and UEs, it's difficult to predict these situations and incorporate them into subscription data. Therefore, operators must be able to dynamically adjust MBSR authorization. Accordingly, operators can control the number of MBSRs operating in a specific area at a given time by temporarily disabling selected MBSR sets, as needed.

[0319] For roaming, the VPLMN must be able to control MBSR permissions to operate on its own network, regardless of the permissions in the HPLMN's subscription data. One use case is a large-scale event that hosts a large number of UEs in an area that typically hosts a very small number of UEs. To support event communications and increase capacity, operators typically add their own IAB nodes to the location. However, allowing MBSR in this area during the event period would only cause interference.

[0320] While it might be argued that operators could proactively update their own MBSR subscription information, this is not possible for roaming MBSRs, which are unknown. Furthermore, it is impractical to update roaming agreements with every operator to authorize MBSRs every time an event of this type is anticipated.

[0321] Therefore, in this use case, the VPLMN operator should be able to disable roaming MBSR when entering the event area during an event to avoid interference.

[0322] A business can dynamically update MBSR permissions to control the number of MBSRs operating in a given area.

[0323] MBSR may be based on the Integrated Access and Backhaul (IAB) architecture, in which case it may be considered a mobile IAB node. MBSR may also be referred to as mobile IAB. Only a single hop may be supported for the connection between the MBSR and the IAB-donor node. The MBSR may perform base station operations after roaming and connecting to the IAB-donor node of the VPLMN. For example, the MBSR may be an IAB-node that includes a UE part (e.g., IAB-UE) and a RAN part (e.g., gNB-DU). The MBSR may connect to the 5GC via the IAB-donor gNB or gNB, for example. The MBSR may connect to other IAB-nodes and / or other UEs. For example, the IAB-donor may act as a base station for the UE part (e.g., IAB-UE) of the MBSR. For example, the UE part of MBSR can send a registration request message to the AMF via a base station (e.g., IAB-donor). The base station part of MBSR (e.g., gNB-DU) can perform base station operations for other UEs.

[0324] The VPLMN needs to dynamically control MBSR based on network conditions (e.g., the number of UEs in the MBSR location, whether the MBSR causes interference, etc.), without having to consider MBSR-related subscriber information or changes thereto. For example, while MBSR operation may be authorized based on subscriber information, the AMF of the VPLMN may not authorize MBSR operation.

[0325] As described in the example above, the HPLMN may not want the VPLMN to control MBSR without the MBSR-related subscriber information managed / configured by the HPLMN. For example, if subscribers roam to the VPLMN, the HPLMN may want them to be served by the MBSR that moved to the VPLMN. In this case, the HPLMN may not want the MBSR to be disabled by the VPLMN. However, prior art solutions have not been able to address this situation.

[0326] In other words, the problem with conventional technology is that it cannot address these issues. Therefore, a solution is needed to address these issues.

[0327] Below, the disclosure of this specification describes various examples supporting MBSR control based on various examples. The method described in the disclosure of this specification may be composed of a combination of one or more of the following actions / configurations / steps.

[0328] In the disclosure of this specification, UE (User Equipment) and terminal may be used as terms having the same meaning.

[0329] In the disclosure of this specification, Mobile Base Station Relay (MBSR), Vehicle Mounted Relay (VMR), mobile IAB, IAB-node, IAB, gNB-DU, mobile base station, mobile gNB, etc. may be used as terms with the same meaning.

[0330] Below, various examples of the disclosure of this specification are described.

[0331] A first example of the disclosure of this specification is described.

[0332] The UDM can transmit subscriber information to an AMF (e.g., the AMF of MBSR). The subscriber information may include one or more of the following:

[0333] 1) Information indicating that VPLMN is allowed to control MBSR.

[0334] 2) Information indicating that dynamic control of MBSR is allowed.

[0335] 3) Information indicating that the Serving PLMN is permitted to control MBSR.

[0336] 4) Information indicating that AMF is allowed to control MBSR.

[0337] 5) Time-related information: This may include time information to indicate that MBSR control is permitted only during certain time periods, in relation to 1) to 4) above. For example, the time information may include information such as time window, time validation, and time restriction.

[0338] 6) Region-related information: This may include location information such as location / spatial validation and location / spatial restriction to indicate that MBSR control is permitted only in a specific region in relation to 1) to 4) above. The location information may take various forms, such as PLMN ID(s), TAI(s), Cell ID(s), and geo-coordinate information.

[0339] 7) Information indicating that NG-RAN (which may mean IAB-donor gNB or IAB-donor-CU) is allowed to control MBSR.

[0340] In the above, "(dynamically) controlling MBSR" can be interpreted in various ways. For example, "(dynamically) controlling MBSR" can mean disabling or enabling MBSR. Alternatively, "(dynamically) controlling MBSR" can mean making MBSR into a non-authorized state or an authorized state. Alternatively, "(dynamically) controlling MBSR" can mean updating the authorization / allowance status / information of MBSR. Alternatively, "(dynamically) controlling MBSR" can mean disallowing or allowing MBSR to operate. Alternatively, "(dynamically) controlling MBSR" can mean disallowing or allowing IAB to perform mobile operations. Various descriptions of "(dynamically) controlling MBSR" can be applied throughout this specification.

[0341] Additionally, MBSR-related subscriber information may include information about whether the subscriber is authorized (or allowed) to operate as MBSR, or whether the subscriber is authorized (or allowed) to operate as Mobile IAB (Integrated access and backhaul), or whether the subscriber is authorized (or allowed) to perform mobile operations on IAB.

[0342] Although an MBSR can be authorized / enabled to operate as a base station, the AMF may not authorize / disable the MBSR. In this case, the reasons for the AMF not authorizing / disabling the MBSR may be as follows. For example, if the number of UEs in the area where the MBSR is located is determined or predicted to be small, the AMF may not authorize / disable the MBSR. If the MBSR causes interference with other base stations (mainly fixed base stations), the AMF may not authorize / disable the MBSR. If there are already sufficient other MBSRs in the area where the MBSR is located, the AMF may not authorize / disable the MBSR.

[0343] As described in the various examples above, while MBSR can be authorized / enabled to operate as a base station, AMF can also authorize / enable MBSR after AMF not_authorizes / disables MBSR. For example, the following are examples of reasons why AMF might authorize / enable MBSR. For example, considering the number of UEs at the location of MBSR, AMF may determine or predict that there are many UEs. In this case, AMF may determine that as MBSR moves, it will no longer cause interference with other base stations (usually fixed base stations). In this case, AMF can authorize / enable MBSR.

[0344] The above subscriber information may be included as part of the IAB-related subscriber information. Alternatively, the subscriber information may be included as part of the MBSR-related subscriber information. Alternatively, the subscriber information may be included as separate subscriber information.

[0345] A second example of the disclosure of this specification is described.

[0346] Based on the subscriber information, AMF can determine whether to dynamically control MBSR. When MBSR performs the registration procedure, AMF can obtain subscriber information from UDM.

[0347] In the following examples, the AMF may decide to dynamically control MBSR. For example, if the subscriber information allows / authorizes the subscriber to operate as MBSR (or allows / authorizes the subscriber to operate as Mobile IAB, or allows / authorizes the subscriber to perform mobile operations on IAB), the AMF may decide to dynamically control MBSR.

[0348] The AMF may be the AMF of the serving PLMN of MBSR (or IAB-UE or IAB-MT). The PLMN may be an HPLMN or a VPLMN. That is, the method for supporting MBSR control proposed in this specification may include an operation in which the AMF dynamically controls MBSR not only in the VPLMN but also in the HPLMN.

[0349] Based on the subscriber information described above, it can be assumed that AMF is permitted to dynamically control MBSR. In this case, AMF can perform MBSR control. Based on various information, such as network conditions (e.g., whether MBSR causes interference), OAM information, local policy, and local configuration, AMF can perform MBSR control.

[0350] The actions by which AMF performs MBSR control may include one or more of the following actions:

[0351] I) If AMF disables MBSR, one or more of actions A) and B) may be performed:

[0352] A) The AMF may provide information to the MBSR (e.g., it may be the IAB-UE or IAB-MT of the MBSR) indicating that it is not authorized / allowed to operate as the MBSR. This may be accomplished using the UE Configuration Update procedure, the Registration procedure, or the Deregistration procedure (which may include Deregistration with re-registration).

[0353] B) The AMF may provide information to the NG-RAN (e.g., it may be the IAB-donor gNB or IAB-donor-CU of the MBSR) indicating that the MBSR (or the IAB or the gNB-DU or the IAB-UE or the IAB-MT) is not authorized / allowed to operate as the MBSR. For this purpose, the AMF may transmit the above information to the NG-RAN when it transmits the NAS message to the MBSR to the NG-RAN. Alternatively, the AMF may transmit the above information to the NG-RAN in a separate action. The information that the AMF provides to the NG-RAN may be provided as part of the IAB-related information, as part of the MBSR-related information, or as separate information.

[0354] II) When MBSR is enabled, one or more of actions a) and b) may be performed:

[0355] a) AMF provides information to MBSR (which may be IAB-UE or IAB-MT of MBSR) indicating that it is authorized / allowed to operate as MBSR. This can be done using the UE Configuration Update procedure, the Registration procedure, or the Deregistration procedure (which includes Deregistration with re-registration).

[0356] b) The AMF may provide information to the NG-RAN (e.g., the IAB-donor gNB or IAB-donor-CU of MBSR) indicating that the MBSR (or IAB, or gNB-DU, or IAB-UE, or IAB-MT) is authorized / allowed to operate as MBSR. For this purpose, the AMF may provide the information to the NG-RAN when transmitting an NAS message to the MBSR. Alternatively, the AMF may provide the information to the NG-RAN in a separate action. The information provided to the NG-RAN may be provided as part of the IAB-related information, as part of the MBSR-related information, or as separate information.

[0357] When determining whether AMF can perform dynamic control of MBSR, AMF may consider not only subscriber information but also local policy / configuration, etc.

[0358] A third example of the disclosure of this specification is described.

[0359] AMF can provide information on whether NG-RAN (which may mean IAB-donor gNB or IAB-donor-CU) can dynamically control MBSR based on subscriber information described in various examples above.

[0360] The action of providing information about whether the AMF can dynamically control the MBSR may include an action of determining that the AMF can dynamically control the MBSR based on the subscriber information. The AMF may obtain subscriber information from the UDM when the MBSR performs the registration procedure.

[0361] The actions that determine whether AMF dynamically controls MBSR and / or provide information related to dynamically controlling MBSR may include the following actions. For example, AMF may determine dynamically controlling MBSR if the subscriber's information allows / authorizes the subscriber to operate with MBSR (or allows / authorizes the subscriber to operate with Mobile IAB, or allows / authorizes the subscriber to perform mobile operations on IAB).

[0362] The AMF may be the AMF of the PLMN serving MBSR (or IAB-UE or IAB-MT). The PLMN may be an HPLMN or a VPLMN. The method for supporting MBSR control described in the disclosure of this specification may include a method for dynamically controlling MBSR in a VPLMN as well as a method for dynamically controlling MBSR in an HPLMN.

[0363] Based on the subscriber information described above, the AMF may deem dynamic MBSR control permitted. In this case, the AMF may provide MBSR control-related information to the NG-RAN. The MBSR control-related information may be identical to the subscriber information described in the first example of the disclosure herein. Alternatively, the MBSR control-related information may be provided in a modified or combined form with the subscriber information described in the first example of the disclosure herein.

[0364] Based on the MBSR dynamic control-related information received from the AMF, the NG-RAN may determine (or deem) that dynamic control of MBSR is permitted. In this case, the NG-RAN may perform MBSR control.

[0365] Based on various information such as network conditions (e.g., MBSR causing interference, etc.), OAM information, local policy, local configuration, etc., NG-RAN can perform MBSR control.

[0366] NG-RAN performing MBSR control may include one or more of the following actions:

[0367] I) If MBSR is disabled, one or more of the actions A) to D may be performed:

[0368] A) If there are UE(s) served by MBSR or UE(s) connected to MBSR, NG-RAN moves (or handovers) these UE(s) to another cell or another RAN.

[0369] B) NG-RAN provides information to MBSR (e.g. corresponding part of IAB-DU) indicating that it is not authorized / allowed to operate as MBSR.

[0370] C) NG-RAN performs actions to remove or hold / suspend MBSR (e.g., the part corresponding to IAB-DU) and F1 interface.

[0371] D) NG-RAN provides information to MBSR (the corresponding part of IAB-UE or IAB-MT) indicating that it is not authorized / allowed to operate as MBSR.

[0372] II) When MBSR is enabled, one or more of actions a) to c) may be performed:

[0373] a) NG-RAN provides information to MBSR (the part corresponding to IAB-DU) indicating that it is authorized / allowed to operate as MBSR.

[0374] b) NG-RAN performs operations to add or resume / restart MBSR (corresponding to IAB-DU) and F1 interface.

[0375] c) NG-RAN provides information to MBSR (corresponding to IAB-UE or IAB-MT) indicating that it is authorized / allowed to operate as MBSR.

[0376] When AMF determines whether MBSR can be dynamically controlled or when AMF provides information to NG-RAN regarding whether MBSR can be dynamically controlled, AMF may consider not only subscriber information but also local policy / configuration, etc.

[0377] When NG-RAN determines whether dynamic control of MBSR is possible, NG-RAN may consider not only MBSR dynamic control related information provided by AMF but also local policy / configuration, etc.

[0378] Hereinafter, procedures based on various examples of the disclosure of the present specification will be described with reference to examples of FIG. 11 and FIG. 12.

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

[0380] For reference, the examples of FIGS. 11 and 12 illustrate a UE, a Mobile gNB, an AMF, an SMF, a UPF, and a UDM. The Mobile gNB may refer to a mobile base station that can move. The Mobile gNB may be a base station that supports MBSR-related operations. The Mobile gNB may include a RAN part and a UE part. The RAN part may refer to a part that operates as a RAN for the UE. The UE part may refer to a part of the Mobile gNB that operates as a UE for the network. The RAN part and the UE part included in the Mobile gNB may be physically separated, or the RAN part and the UE part may not be physically separated.

[0381] FIG. 11 is a first example of a procedure according to one embodiment of the disclosure of the present specification.

[0382] In the example of Figure 11, the mobile gNB may be in a non-roaming state or a roaming state.

[0383] 1. The mobile gNB can send a registration request message to the AMF. For example, the UE part of the mobile gNB can send a Registration Request message to perform the registration procedure with 5GC.

[0384] 2. AMF can send a registration message to UDM. For example, AMF can register with UDM that it is serving AMF.

[0385] 3. AMF can obtain subscriber information from UDM. Subscriber information can include one or more of the information 1) to 7) described in the first example of the disclosure of the present specification. Subscriber information can include information on whether operation as a mobile base station (e.g., MBSR) is authorized / allowed (e.g., information on whether a mobile base station including the UE part that requested the registration is authorized / allowed to perform base station operation). Subscriber information can also include location restriction and / or time restriction information.

[0386] 4. The AMF can determine whether to disable the mobile base station. Based on subscriber information, the AMF can determine whether the mobile gNB is authorized / allowed to operate as a mobile base station. The example in Figure 11 assumes a situation where the mobile gNB is authorized / allowed to operate as a mobile base station. Furthermore, the AMF can determine whether dynamic control of the mobile base station is permitted based on subscriber information. The AMF determines whether to not_authorize / disable the mobile base station.

[0387] 5. AMF can send a Registration Accept message. For example, AMF sends a Registration Accept message to the UE part that includes information indicating that it does not authorize / disable the UE from acting as a mobile base station. Instead of sending a Registration Accept message, AMF can also send a Registration Reject message that includes information indicating that it does not authorize / disable the UE from acting as a mobile base station.

[0388] 6. The AMF may decide to authorize / enable the mobile gNB to operate as a mobile base station. For example, based on subscriber information indicating that the mobile gNB is authorized / allowed to operate as a mobile base station by default (i.e., the mobile base station including the UE requesting registration performs base station operations), the AMF may authorize / enable the mobile gNB to operate as a mobile base station.

[0389] 7. The AMF may transmit NAS messages (e.g., Downlink NAS Transport messages). The AMF transmits NAS messages (e.g., Downlink NAS Transport messages) to the UE, which contain information indicating that the UE is authorized / enabled to operate as a mobile base station. For example, the AMF may perform a procedure to provide the UE part with a change in authorization information related to operating as a mobile base station. For such a procedure, the UE Configuration Update procedure may be used, for example.

[0390] 8. The UE part can establish a PDU session required for the mobile gNB to operate as a base station. For example, the PDU session establishment procedure described in FIGS. 7 and 8 can be performed. The UE part of the mobile gNB can optionally perform the PDU session establishment procedure if PDU session establishment is required.

[0391] 9. The mobile gNB can initiate / perform base station operations. For example, base station operations may include broadcasting system information to UEs, serving UEs (e.g., establishing an RRC connection with the UE, exchanging NAS messages between the UE and 5GC, etc.).

[0392] Below, with reference to the example of Fig. 12, an example is described in which a mobile gNB is not_authorized / disabled while performing base station operations.

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

[0394] FIG. 12 is a second example of a procedure according to one embodiment of the disclosure of the present specification.

[0395] In the example of Figure 12, the mobile gNB may be in a non-roaming state or a roaming state.

[0396] 1. The mobile gNB can send a registration request message to the AMF. For example, the UE part of the mobile gNB can send a Registration Request message to perform the registration procedure with 5GC.

[0397] 2. AMF can send a registration message to UDM. For example, AMF can register with UDM that it is serving AMF.

[0398] 3. AMF can obtain subscriber information from UDM. Subscriber information can include one or more of the information 1) to 7) described in the first example of the disclosure of the present specification. Subscriber information can include information on whether operation as a mobile base station (e.g., MBSR) is authorized / allowed (e.g., information on whether a mobile base station including the UE part that requested the registration is authorized / allowed to perform base station operation). Subscriber information can also include location restriction and / or time restriction information.

[0399] 4. The AMF can send a Registration Accept message. For example, the AMF can determine whether to authorize / allow operation as a mobile base station based on subscriber information. In the example of Figure 12, it is assumed that to authorize / allow operation as a mobile base station. In addition, the AMF can determine whether to dynamically control the mobile base station based on subscriber information. The AMF determines whether to authorize / enable operation as a mobile base station. The AMF sends a Registration Accept message to the UE part containing information indicating that to authorize / enable operation as a mobile base station.

[0400] 5. The UE part can establish a PDU session required for the mobile gNB to operate as a base station. For example, the PDU session establishment procedure described in FIGS. 7 and 8 can be performed. The UE part of the mobile gNB can optionally perform the PDU session establishment procedure if PDU session establishment is required.

[0401] 6. The mobile gNB can initiate / perform base station operations. For example, base station operations may include broadcasting system information to UEs, serving UEs (e.g., establishing an RRC connection with the UE, exchanging NAS messages between the UE and 5GC, etc.).

[0402] 7. Afterwards, AMF may decide not to authorize / disable the Mobile gNB from acting as a mobile base station.

[0403] 8. The AMF may transmit NAS messages (e.g., Downlink NAS Transport messages). For example, the AMF may transmit a NAS message (e.g., Downlink NAS Transport) containing information indicating that the UE part is not authorized / disabled to operate as a mobile base station. For example, the AMF may perform a procedure to provide the UE part with a change in authorization information related to operating as a mobile base station. For such a procedure, the UE Configuration Update procedure may be used, for example.

[0404] Alternatively, the AMF may perform a deregistration procedure on the UE part. In this case, the Deregistration Request message sent by the AMF to the UE may include information indicating that the UE is not authorized / disabled to act as a mobile base station.

[0405] 9. The mobile gNB may perform tasks to clean up the UE(s) it was serving. For example, the mobile gNB may perform actions such as handing over or redirecting the UE(s) to another base station.

[0406] 10. Afterwards, the AMF may decide to authorize / enable the mobile gNB to operate as a mobile base station. For example, based on subscriber information indicating that the mobile gNB is authorized / allowed to operate as a mobile base station by default (i.e., the mobile base station including the UE requesting registration performs base station operations), the AMF may authorize / enable the mobile gNB to operate as a mobile base station.

[0407] 11. The AMF can send NAS messages (e.g., Downlink NAS Transport messages). The AMF sends the UE a NAS message (e.g., Downlink NAS Transport) containing information indicating that the UE is authorized / enabled to operate as a mobile base station. For example, the AMF can perform a procedure to provide the UE part with a change in authorization information related to operating as a mobile base station. For such a procedure, the UE Configuration Update procedure can be used, for example.

[0408] 12. The mobile gNB can initiate / perform base station operations. For example, base station operations may include broadcasting system information to UEs, serving UEs (e.g., establishing an RRC connection with the UE, exchanging NAS messages between the UE and 5GC, etc.).

[0409] For reference, information 1) to 7) described in the first example of the disclosure of this specification may be set in the AMF instead of being provided as subscriber information. Alternatively, the AMF may obtain information 1) to 7) described in the first example of the disclosure of this specification via OAM. The information 1) to 7) described in the first example of the disclosure of this specification that is set or obtained in the above-described examples may be information about a specific MBSR, or information about all MBSRs belonging to / subscribed to a specific PLMN.

[0410] For reference, instead of receiving the information 1) to 7) described in the first example of the disclosure of this specification from the AMF, the information 1) to 7) may be set in the NG-RAN (e.g., IAB-donor gNB or IAB-donor-CU). Alternatively, the NG-RAN may obtain the information 1) to 7) via OAM. The information 1) to 7) described in the first example of the disclosure of this specification that is set or obtained in the above-described example may be information about a specific MBSR, or information about all MBSRs belonging to / subscribed to a specific PLMN.

[0411] For reference, in the disclosure of this specification, the mobile gNB operating as a base station may mean that the mobile gNB operates as a mobile IAB.

[0412] Below, examples of operations related to MBSR described in various examples of the disclosure of this specification are described with reference to the example of FIG. 13.

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

[0414] FIG. 13 illustrates an example of operations related to a mobile base station according to one embodiment of the disclosure of the present specification.

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

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

[0417] For reference, the MBSR described in various examples disclosed herein may be an example of a mobile base station. That is, the term "mobile base station" may be used instead of "MBSR." Alternatively, the mobile base station may be referred to as a "mobile gNB with wireless access backhauling" (MWAB). In other words, the descriptions related to MBSR described in various examples disclosed herein may equally apply to mobile base stations.

[0418] In the example of FIG. 13, the first mobile base station may be the mobile gNB of the examples of FIGS. 11 and 12.

[0419] In step (S1301), the first mobile base station may transmit a registration request message to the AMF. Here, a UE included in the first mobile base station may transmit the registration request message to the AMF.

[0420] The first mobile base station may be an IAB node, a gNB DU, a Vehicle Mounted Relay (VMR), or a mobile gNB.

[0421] For example, a UE included in the first mobile base station can cause the AMF to perform step (S1302) by transmitting a registration request message.

[0422] In step (S1302), the AMF may receive subscriber information related to the first mobile base station from the UDM. The subscriber information may include information regarding whether the first mobile base station is permitted to operate as a mobile base station. The subscriber information may include, for example, one or more of the information 1) to 7) of the first example of the disclosure of this specification.

[0423] Additionally, subscriber information may include information about whether the subscriber is authorized (or allowed) to operate as a mobile base station (e.g., MBSR), or whether the subscriber is authorized (or allowed) to operate as a Mobile Integrated Access and Backhaul (IAB), or whether the subscriber is authorized (or allowed) to perform mobile operations for an IAB.

[0424] The subscriber information may include one or more of the following information: information about whether a VPLMN is allowed to control the mobile base station (e.g., MBSR); information about whether dynamic control of the mobile base station is allowed; information about whether a serving PLMN is allowed to control the mobile base station; information about whether the AMF is allowed to control the mobile base station; time information related to the mobile base station; location information related to the mobile base station; and information indicating that an NG-RAN (which may mean an IAB-donor gNB or an IAB-donor-CU) is allowed to control the mobile base station.

[0425] In step (S1303), the AMF may determine whether to enable the mobile base station. For example, the AMF may determine whether to enable or disable the first mobile base station from operating as a mobile base station based on subscriber information. For example, operating as a mobile base station may mean that the first mobile base station performs base station operations (e.g., RAN operations) for other UEs.

[0426] In step S1304, the AMF may transmit a response message to the registration request message to the first mobile base station. The response message may be a registration acceptance message or a registration rejection message. For example, the AMF may transmit a registration acceptance message to the UE of the first mobile base station. For example, the AMF may transmit a registration rejection message to the UE of the first mobile base station. For example, if it is determined that the first mobile base station is to be activated to operate as the mobile base station, the first mobile base station may transmit a registration acceptance message. The registration acceptance message may include information indicating that the first mobile base station is to be activated to operate as the mobile base station.

[0427] For another example, if it is decided to deactivate the first mobile base station from operating as the mobile base station, the AMF may transmit a registration acceptance message or a registration rejection message to the UE of the first mobile base station.

[0428] When AMF transmits a registration acceptance message, the registration acceptance message may include information that the first mobile base station is deactivated from operating as the mobile base station.

[0429] When AMF sends a registration rejection message, it may not include information that the registration rejection message is disabled.

[0430] According to one embodiment of the disclosure of the present specification, a mobile base station may perform a registration procedure for 5GC. The mobile base station may transmit a registration request message to the AMF. Upon receiving the registration request message, the AMF may receive information related to the IAB and / or MBSR and / or mobile gNB support / capability / operation of the mobile base station from the mobile base station and / or the NG-RAN.

[0431] According to one embodiment of the disclosure of the present specification, the AMF of a mobile base station can obtain subscriber information from the UDM.

[0432] According to one embodiment of the disclosure of this specification, an AMF can determine whether a mobile base station can dynamically control and operate as a mobile base station. This determination can be made based on subscriber information, information obtained in step S1301, etc.

[0433] According to one embodiment of the disclosure of the present specification, the AMF may determine that a subscriber (e.g., a mobile gNB) is capable of operating as a mobile base station.

[0434] According to one embodiment of the disclosure of the present specification, the AMF may notify the mobile base station and the NG-RAN that it may operate as a mobile base station.

[0435] According to one embodiment of the disclosure of the present specification, if the AMF determines that it is capable of dynamic control over a mobile base station, the AMF may also determine that a subscriber (e.g., a mobile gNB) cannot operate as a mobile base station. For example, the AMF may make this determination based on various information, such as subscriber information, network conditions (e.g., whether the mobile base station causes interference, etc.), OAM information, local policy, and local configuration.

[0436] According to one embodiment of the disclosure of the present specification, the AMF may inform the mobile base station and the NG-RAN that the subscriber (e.g., mobile gNB) is unable to operate as a mobile base station.

[0437] This specification may have various effects.

[0438] For example, a VPLMN or a serving PLMN can dynamically control a mobile base station (e.g., MBSR) under the control / permission / authorization of the HPLMN to which the mobile base station is subscribed. Alternatively, subscriber information of the mobile base station (in particular, subscriber information on whether the subscriber can operate as a mobile base station) can be updated daily (changed between being able to operate as a mobile base station and not being able to operate). Accordingly, the serving PLMN / AMF can be authorized to dynamically control the mobile base station without having to inform the serving PLMN / AMF whether it can operate as a mobile base station. Accordingly, the serving PLMN / AMF can control the mobile base station based on the network situation, etc.

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

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

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

[0442] For reference, the operation of a network node (e.g., AMF, SMF, UPF, UDM, etc.) or a base station (e.g., NG-RAN, mobile gNB, mobile base station, IAB node, 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.

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

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

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

[0446] 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. In the method of Access and Mobility Management Function (AMF) performing communication, A step of receiving a registration request message from a User Equipment (UE) included in a first mobile base station; A step of receiving subscription information related to the first mobile base station from Unified Data Management (UDM); A step of determining whether to enable or disable the first mobile base station from operating as a mobile base station based on the subscriber information; and Comprising a step of transmitting a response message to a registration request message to the UE included in the first mobile base station, A method characterized in that the subscriber information includes information on whether the first mobile base station is permitted to operate as the mobile base station.

2. In paragraph 1, A method further comprising a step of determining whether the AMF can dynamically control the first mobile base station based on the subscriber information.

3. In paragraph 1 or 2, The above subscriber information is: Information on whether the VPLMN is permitted to control the above mobile base station; Information on whether dynamic control of the above mobile base station is permitted; Information on whether the serving PLMN is permitted to control the mobile base station; Information on whether the above AMF is permitted to control the above mobile base station; Time information related to the above mobile base station; and Location information related to the above mobile base station; and Information indicating that the NG-RAN (which may mean the IAB-donor gNB or the IAB-donor-CU) is permitted to control the mobile base station; A method characterized by comprising at least one of:

4. In any one of paragraphs 1 to 3, If it is determined that the first mobile base station is activated to operate as the mobile base station, the response message is a registration acceptance message, A method characterized in that the registration acceptance message includes information that the first mobile base station activates operation as the mobile base station.

5. In any one of paragraphs 1 to 3, If it is decided to disable the above first mobile base station from operating as the above mobile base station, the response message is a registration acceptance message or a registration rejection message, and A method characterized in that the registration acceptance message includes information that the first mobile base station is deactivated from operating as the mobile base station.

6. In any one of paragraphs 1 to 5, A method characterized in that the first mobile base station is an Integrated access and backhaul (IAB) node, a gNodeB (gNB) Distributed Unit (DU), a Vehicle Mounted Relay (VMR), or a mobile gNB.

7. In the Access and Mobility Management Function (AMF) that performs communication, the AMF: 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; An operation performed based on the above command being executed by the one or more processors is an AMF method according to any one of claims 1 to 6.

8. In a method for performing communication by a first mobile base station including a User Equipment (UE), A step of transmitting a registration request message to the Access and Mobility management Function (AMF); A step of receiving a response message including information related to a mobile base station from the AMF; The information related to the mobile base station includes information on whether the first mobile base station is enabled or disabled to operate as the mobile base station; and A method comprising the step of operating as a base station for another UE based on information related to the mobile base station.

9. In paragraph 8, A method characterized in that the above registration request message causes the AMF to receive subscriber information related to the first mobile base station from the UDM.

10. In paragraph 9, The above subscriber information is: Information on whether the VPLMN is permitted to control the above mobile base station; Information on whether dynamic control of the above mobile base station is permitted; Information on whether the serving PLMN is permitted to control the mobile base station; Information on whether the above AMF is permitted to control the above mobile base station; Time information related to the above mobile base station; and Location information related to the above mobile base station; and Information indicating that the NG-RAN (which may mean the IAB-donor gNB or the IAB-donor-CU) is permitted to control the mobile base station; A method characterized by comprising at least one of:

11. In any one of paragraphs 8 to 10, A method characterized in that the first mobile base station is an IAB node, a gNB DU, a VMR (Vehicle Mounted Relay), or a mobile gNB.

12. A first mobile base station including a UE (User Equipment) configured to operate in a wireless communication system, wherein the first mobile base station: 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; The actions performed based on the above instructions being executed by the one or more processors are: A first mobile base station according to the method of Articles 8 to 11.

13. As an apparatus in mobile communication, at least one processor; and At least one memory storing instructions and being operably electrically connected to the at least one processor, The operations performed based on the above instruction being executed by the at least one processor are: A device according to the method of Articles 8 to 11.

14. A non-transitory computer-readable storage medium that records commands, The operations performed based on the above instructions being executed by at least one processor are: CRM, a method according to Articles 8 to 11.

Images