Session management timer according to mwab

Abstract

The present disclosure provides a method. The method comprises the steps of: transmitting, by a UE, a session message for a protocol data unit (PDU) session to a base station; and starting, by the UE, a session management timer on the basis of transmitting, by the UE, the session message, wherein, on the basis that the base station is a mobile gNB with wireless access backhauling (MWAB), the session management timer is a timer for access through the MWAB.

Description

Session management timer according to MWAB

[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 in a timely manner, meeting both urgent market needs and the longer-term requirements outlined by the ITU-R (ITU radio communication sector) 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] When a terminal receives service through MWAB, the timer related to session-related procedures is set to a value that takes MWAB into account.

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

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

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

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

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

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

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

[0013] Figure 10 shows an example of the architecture of MWAB.

[0014] Figure 11 shows an example of the architecture in a non-roaming scenario of MWAB.

[0015] Figure 12 shows an example of the architecture in a roaming scenario of MWAB.

[0016] Figure 13 shows an example of MWAB's handling of PDU session establishment or modification of UE.

[0017] Figure 14 shows a flowchart of a first example of the first embodiment of the present specification.

[0018] Figure 15 shows a flowchart of a second example of the first embodiment of the present specification.

[0019] Figure 16 shows a flowchart of the third embodiment of the present specification.

[0020] Figure 17 illustrates the UE's procedure for disclosure of this specification.

[0021] Figure 18 illustrates the SMF procedure for the disclosure of this specification.

[0022] 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 multicarrier frequency division multiple access (MC-FDMA) systems. CDMA can be implemented via wireless technologies such as universal terrestrial radio access (UTRA) or CDMA2000. TDMA can be implemented via 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 E-UTRA (evolved UTRA). UTRA is part of UMTS (universal mobile telecommunications system). 3GPP (3rd generation partnership project) LTE (long-term evolution) is part of E-UMTS (evolved UMTS) that uses 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).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0038] Wireless devices (100a to 100f) refer to devices that perform communication using radio access technology (RAT) (e.g., 5G NR or LTE) and may also be referred to as communication / wireless / 5G devices. Wireless devices (100a to 100f) may include, but are not limited to, robots (100a), vehicles (100b-1 and 100b-2), extended reality (XR) devices (100c), portable devices (100d), home appliances (100e), IoT devices (100f), and artificial intelligence (AI) devices / servers (400). For example, vehicles may include vehicles having wireless communication capabilities, autonomous vehicles, and vehicles capable of performing vehicle-to-vehicle communication. Vehicles may include unmanned aerial vehicles (UAVs) (e.g., drones). XR devices may include AR / VR / mixed reality (MR) devices, and may be implemented in the form of head-mounted devices (HMDs) and heads-up displays (HUDs) mounted on vehicles, televisions, smartphones, computers, wearable devices, home appliances, digital signs, vehicles, robots, etc. Portable devices may include smartphones, smart pads, wearable devices (e.g., 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.

[0039] 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 functions, a connected car, a UAV, an AI module, a robot, an AR device, a VR device, an MR device, a holographic 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.

[0040] For example, a UAV may be an aircraft that is unmanned and navigated by radio control signals.

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

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

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

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

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

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

[0047] For example, a weather / environment device may include a device that monitors or predicts the weather / environment.

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

[0049] 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, device-to-device (D2D) communication), and base station-to-base station communication (150c) (e.g., relay, integrated access and backhaul (IAB)). 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.

[0050] AI is the study of artificial intelligence or the methodologies for creating it, while machine learning (ML) defines various problems in the field of AI and studies the methodologies for solving them. Machine learning is also defined as an algorithm that improves performance on a task through consistent experience.

[0051] A robot can be defined as a machine that automatically processes or operates a given task based on its own capabilities. Specifically, a robot capable of perceiving its environment, making decisions, and performing actions on its own can be called an intelligent robot. Robots can be categorized into industrial, medical, household, and military applications based on their intended use or field. Robots are equipped with a drive unit, including an actuator or motor, enabling them to perform various physical actions, such as moving robot joints. Furthermore, mobile robots include wheels, brakes, and propellers in their drive unit, enabling them to drive on the ground or fly in the air.

[0052] Autonomous driving refers to the technology of driving on one's own, while autonomous vehicles refer to vehicles that drive without, or with minimal, user intervention. For example, autonomous driving can include technologies such as lane keeping, automatic speed control like adaptive cruise control, autonomous driving along a set route, and autonomous driving based on a set destination. Vehicles encompass all types of vehicles: those with internal combustion engines, hybrid vehicles with both internal combustion engines and electric motors, and electric vehicles with only electric motors. These vehicles can include not only cars but also trains and motorcycles. Autonomous vehicles can be viewed as robots with autonomous driving capabilities.

[0053] Extended reality is a general term for VR, AR, and MR. VR technology provides real-world objects and backgrounds as CG images only, AR technology provides virtual CG images over images of real objects, and MR technology is a CG technology that mixes and combines virtual objects with the real world. MR technology is similar to AR in that it displays real and virtual objects together. However, there is a difference: while AR uses virtual objects to complement real objects, MR uses virtual and real objects equally.

[0054] NR supports multiple numerologies, or subcarrier spacing (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.

[0055] 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 NR systems, FR1 can mean the "sub-6GHz range," and FR2 can mean the "above 6GHz range," which can be referred to as millimeter wave (mmW).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0070] 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 instruction codes, commands 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.

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

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

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

[0074] 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. The one or more memories (104, 204) may be located internally and / or externally to the one or more processors (102, 202). Additionally, the one or more memories (104, 204) may be coupled to the one or more processors (102, 202) via various technologies, such as wired or wireless connections.

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

[0076] 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 specification, one or more antennas (108, 208) may be multiple physical antennas or multiple logical antennas (e.g., antenna ports).

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

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

[0079] In the implementation of the present specification, a UE can operate as a transmitter in the uplink (UL) and as a receiver in the downlink (DL). In the implementation of the present 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 the present specification or to control a transceiver (106) to perform UE operations according to the implementation of the present 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 the present specification or to control a transceiver (206) to perform base station operations according to the implementation of the present specification.

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

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

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

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

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

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

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

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

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

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

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

[0091] Figure 4 is a structural diagram of a next-generation mobile communications network.

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

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

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

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

[0096] The illustrated AMF (410) can manage access and mobility in a 5G system. The AMF (410) can perform functions to manage Non-Access Stratum (NAS) security. The AMF (410) can perform functions to handle mobility in the idle state.

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

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

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

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

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

[0102] The illustrated SMF (420) can perform the function of allocating an IP (Internet Protocol) address of the UE. In addition, the SMF (420) can control a PDU (protocol data unit) session.

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

[0104] 5G mobile communications support multiple numerologies, or subcarrier spacing (SCS), to support diverse 5G services. For example, a 15 kHz SCS supports wide areas in traditional cellular bands. A 30 kHz / 60 kHz SCS supports dense urban environments, lower latency, and wider carrier bandwidth. An SCS of 60 kHz or higher supports bandwidths greater than 24.25 GHz to overcome phase noise.

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

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

[0107] - AUSF (Authentication Server Function)

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

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

[0110] - USDF (Unstructured Data Storage Function)

[0111] - NEF (Network Exposure Function)

[0112] - I-NEF (Intermediate NEF)

[0113] - NRF (Network Repository Function)

[0114] - NSSF (Network Slice Selection Function)

[0115] - PCF (Policy Control Function)

[0116] - SMF (Session Management Function)

[0117] - UDM (Unified Data Management)

[0118] - UDR (Unified Data Repository)

[0119] - UPF (User Plane Function)

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

[0121] - AF (Application Function)

[0122] - UE (User Equipment)

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

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

[0125] - NWDAF (Network Data Analytics Function)

[0126] - CHF (CHarging Function)

[0127] Additionally, the following network features may be considered:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0154] <Registration Procedure>

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

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

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

[0158] - Initial registration for 5GS; or

[0159] - mobility registration update; or

[0160] - Periodic registration update; or

[0161] - Emergency registration

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

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

[0164] First, the procedure of Fig. 6 is described.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0195] Now, the procedure of Fig. 7 following the procedure of Fig. 6 is described.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0216] Establishing a PDU session may involve:

[0217] - UE-initiated PDU session establishment procedure

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

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

[0220] - Network-triggered PDU session establishment procedure

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

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

[0223] In the procedures shown in Figures 8 and 9, 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.

[0224] First, the procedure of Fig. 8 is explained.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0261] - RSN (redundancy sequence number) parameter

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

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

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

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

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

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

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

[0269] Now, the procedure of Fig. 9 following the procedure of Fig. 8 is described.

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

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

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

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

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

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

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

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

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

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

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

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

[0282] <MWAB (Mobile gNB with wireless access backhauling)>

[0283] Figure 10 shows an example of the architecture of MWAB.

[0284] MNO2 (mobile network operator2) can provide wireless access and transmission between MWAB (vehicle relay in Fig. 10) and MNO1.

[0285] MNO1 may decide to tunnel MNO1 traffic to MWAB, leveraging the 5G wireless (and transport) connectivity provided by MNO2.

[0286] The MNO2 connection between MWAB and MNO1 can be used to carry relay traffic between MWAB and MNO1 5GC.

[0287] (1) Service Flow

[0288] Step 1. MWAB can be provisioned and configured to register with MNO2 and establish the required PDU sessions using specific quality of service and policies (as negotiated for MNO1 traffic and subscribers).

[0289] Step 2. MWAB can be provisioned and configured to connect to the MNO1 network for communication between users of MNO1 and the MNO1 network.

[0290] Step 3. MN01 subscribers / UEs can camp on the MWAB broadcasting the MNO1 PLMN ID. MN01 subscribers / UEs can then register and connect to the MNO1 network.

[0291] Step 4. All traffic generated by MNO1 UE through MWAB can be tunneled through MNO2 5G connection of configured relay.

[0292] (2) Architecture

[0293] In the MWAB architecture, the MWAB (Mobile gNB with wireless access backhauling) (or VMR, mobile base station) can be a relay belonging to MNO1. The MWAB connects to the base station and 5GC of MNO2 to create a PDU session, and connects the N2 / N3 interface to the 5GC of MNO1 through the created PDU session, so that the MWAB can directly operate as a base station.

[0294] MWAB can also operate as a base station by connecting to MNO1's base station and 5GC to create a PDU session and connecting the N2 / N3 interface to MNO1's 5GC through the created PDU session. In this specification, the base station that MWAB connects to connect the N2 / N3 interface to the 5GC can be referred to as an underlay base station.

[0295] Looking at the MWAB (Vehicle Relay) architecture, MWAB (Vehicle Relay) is a relay belonging to MNO1. In a roaming situation, it connects to the base station and 5GC of MNO2 to create a PDU session, and connects the N2 / N3 interface to the 5GC of MNO1 through the created PDU session, so that MWAB (Vehicle Relay) can operate directly as a base station.

[0296] The MWAB belonging to the above MNO1 can connect to the base station and 5GC of MNO2 to create a PDU session, and connect the N2 / N3 interface to the 5GC of MNO2 through the created PDU session, so that the MWAB can operate directly as a base station. In addition, when the MWAB (Vehicle Relay) is non-roaming, it can connect to the base station and 5GC of MNO1 to create a PDU session, and connect the N2 / N3 interface to the 5GC of MNO1 through the created PDU session, so that it can operate as a base station. In this specification, the base station that the MWAB (Vehicle Relay) connects to connect the N2 / N3 interface to the 5GC is referred to as an underlay base station.

[0297] Figure 11 shows an example of the architecture in a non-roaming scenario of MWAB.

[0298] MWAB can establish PDU sessions by connecting to base stations and 5GCs in the home network.

[0299] Through the established PDU session, MWAB can operate as a base station by connecting the N2 / N3 interface to the 5GC of the home network.

[0300] Both the MWAB's BH (Backhaul) network and the UE's serving network can be the MWAB's Home network.

[0301] Figure 11 illustrates 5G core network functions for MWAB-UE (e.g., BH AMF, BH SMF, BH UPF, UDM (MWAB-UE)) and 5G core network functions for UE served by MWAB-gNB (e.g., AMF, SMF, UPF, UDM) as different NFs. However, some or all of these may be the same NF. For example, BH AMF and AMF may be the same AMF. Or UDM (MWAB-UE) and UDM may be the same UDM.

[0302] Figure 12 shows an example of the architecture in a roaming scenario of MWAB.

[0303] MWAB can establish PDU sessions by connecting to base stations and 5GCs of the visited network.

[0304] Through the established PDU session, MWAB can operate as a base station by connecting the N2 / N3 interface to the 5GC of the home network.

[0305] The BH (Backhaul) network of MWAB is a visited network (e.g., roaming network) and the serving network of the UE can be the Home network of MWAB.

[0306] Figure 12 illustrates UDM for MWAB-UE (e.g., UDM (MWAB-UE)) and UDM for UE served by MWAB-gNB with different NFs. However, they may be the same UDM.

[0307] In FIGS. 11 and 12, a backhaul base station gNB (i.e., an NR base station) is depicted, but it may be a base station / RAN supporting another RAT.

[0308] MWAB can serve terminals using N3 PDU sessions.

[0309] When a PDU session needs to be established or modified, an N3 PDU session of the MWAB-UE can be established or an existing N3 PDU session can be modified. The relevant procedures / sequences can be as follows:

[0310] - Step 1) UE's PDU session establishment or modification procedure is initiated.

[0311] - Step 2) MWAB-gNB provides relevant information (e.g. N3 PDU session establishment request, N3 PDU session modification request, etc.) to MWAB-UE.

[0312] - Step 3) MWAB-UE establishes or modifies N3 PDU session based on information provided by MWAB-gNB.

[0313] - Step 4) MWAB-UE notifies MWAB-gNB that N3 PDU session establishment or modification has been completed / terminated.

[0314] - Step 5) MWAB-gNB initiates the UE's PDU session establishment or modification procedure. This completes / ends the UE's PDU session establishment or modification procedure.

[0315] Figure 13 shows an example of MWAB's handling of PDU session establishment or modification of UE.

[0316] 1) Step 1

[0317] The procedure for establishing / modifying a PDU session for the UE can be initiated.

[0318] Based on this, the MWAB-gNB can receive a new SM context for a PDU session containing at least one QoS flow from the SMF.

[0319] 2) Step 2

[0320] For each QoS flow, the MWAB-gNB can determine the TNL to use to inform the BH SMF of the SDF for the 5QI / ARP and other QoS parameters required in the BH PDU session, and the DL QoS rules associated with that SDF. For UL, the QoS rules are also determined in the MWAB, and the TNL information determined in the MWAB-gNB can be used for UL classification.

[0321] 3) Step 3

[0322] MWAB-UE can modify BH PDU sessions as directed.

[0323] 4) Step 4

[0324] The UPF of the BH PDU session is ready to properly process DL traffic transmitted from the UE UPF.

[0325] 5) Step 5

[0326] MWAB-UE can verify correct modification of BH PDU session.

[0327] 6) Step 6

[0328] MWAB-gNB can complete PDU session setup.

[0329] 7) Step 7

[0330] Data in a UE PDU session can be transmitted and received with the correct QoS.

[0331] <PDU 세션 절차 관련 타이머>

[0332] A timer may be used in connection with PDU session related procedures.

[0333] For example, a terminal may start a timer (e.g., T3580) by transmitting a PDU session establishment request message. When the timer expires, the terminal may retransmit the PDU session establishment request message and reset the timer. Other actions may be performed. For example, if the PDU session is for emergency services, when the timer expires, the terminal may select a different domain for emergency services or perform initial registration.

[0334] For example, a terminal may start a timer (e.g., T3581) by transmitting a PDU Session Modification Request message. When the timer expires, the terminal may retransmit a PDU Session Modification Request message and reset the timer. Other actions may also be performed.

[0335] For example, an SMF can start a timer (e.g., T3591) by sending a PDU Session Modification Command message. When the timer expires, the SMF can resend the PDU Session Modification Command message and reset the timer. Other actions can be performed.

[0336] When the extended timer proposed in this specification expires, the aforementioned actions (e.g., resending the relevant message, selecting a different domain, performing an initial registration) may be performed.

[0337] When a PDU session related procedure (e.g., establishment procedure, modification procedure) for a terminal (UE) via MWAB is initiated, the PDU session related procedure for the terminal can be completed after the N3 PDU session related procedure (e.g., establishment procedure, modification procedure) of the MWAB-UE is completed to support this.

[0338] For example, initiation of a PDU session related procedure for a terminal, completion of an N3 PDU session related procedure of an MWAB-UE, and completion of a PDU session related procedure for a terminal may be performed sequentially.

[0339] Therefore, compared to PDU session related procedures through a normal base station (not through MWAB), PDU session related procedures through MWAB may take longer.

[0340] This may cause the timer started upon initiation of a PDU session-related procedure for the terminal to expire during the procedure. In this case, the PDU session-related procedure for the terminal may be retried (e.g., the terminal retransmits a PDU session establishment request message).

[0341] This may cause the timer started upon initiating a PDU session-related procedure for the terminal to expire during the procedure. If the PDU session is for emergency services, the terminal may select another domain for emergency services or perform initial registration upon expiration.

[0342] Actions such as retrying PDU session related procedures or reselecting a different domain / network to receive emergency services may result in unnecessary signaling and additional time.

[0343] Therefore, timers in PDU session related procedures should be considered considering MWAB.

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

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

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

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

[0348] In this specification, the Backhaul (BH) base station of MWAB, the underlay base station of MWAB, the base station that MWAB connects to connect the N2 / N3 interface to 5GC, the base station of MWAB-UE, the base station that serves MWAB-UE, and the base station that MWAB-UE connects to are described interchangeably.

[0349] In this specification, the MWAB's backhaul (BH) underlay core network, the MWAB's underlay core network and the core network to which the MWAB connects / registers to connect the N2 / N3 interface to 5GC, the MWAB-UE's core network, the core network serving the MWAB-UE, and the core network to which the MWAB-UE connects / registers are used interchangeably to describe the same.

[0350] In this specification, a backhaul (BH) network may be interpreted as including one or more of a backhaul (BH) base station and a backhaul (BH) core network.

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

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

[0353] In this specification, the N2 interface is described interchangeably with the NG-C interface, the NGAP (NG Application Protocol) interface, the N2 tunnel, and the interface for the control plane between the base station and the core network, and the N3 interface is described interchangeably with the NG-U interface, the N3 tunnel, and the interface for the user plane between the base station and the core network.

[0354] In this specification, PDU session for N2 interface, PDU session for N2 interface, N2 PDU session, backhaul (BH) N2 PDU session, N2 backhaul (BH) PDU session, backhaul (BH) PDU session, etc. are used interchangeably to describe.

[0355] In this specification, the terms PDU session for N3 interface, PDU session for N3 interface, N3 PDU session, backhaul (BH) N3 PDU session, N3 backhaul (BH) PDU session, backhaul (BH) PDU session, etc. are used interchangeably to describe the same.

[0356] In this specification, the expansion / reduction timer may be a session management timer. The expansion / reduction timer may be a timer for a PDU session.

[0357] MWABs can be mounted on a variety of vehicles, including ground vehicles (e.g., cars, trains), sea or river vehicles (e.g., ships, boats), aerial vehicles (e.g., airplanes, helicopters, drones), and satellites. When mounted on an aerial vehicle, they may be referred to as Aerial MWABs or Aerial Vehicle Relays (AVRs). Furthermore, MWABs do not necessarily need to be mobile; they can also function as base stations while stationary.

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

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

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

[0361] The method proposed in this specification may be composed of a combination of one or more of the operations / configurations / steps described below, and the proposed methods may be performed or used in combination or complementary manner.

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

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

[0364] In this specification, PDU session related operations / procedures / timers / messages and SM (Session Management) related operations / procedures / timers / messages may be used interchangeably.

[0365] In this specification, conventional PDU session related operations / procedures / timers / messages, etc. may refer to TS 23.501 v18.6.0, TS 23.502 v18.6.0, TS 24.501 v18.6.0, TS 38.413 v18.2.0, etc. In this specification, the proposed items are mainly described.

[0366] I. Embodiment 1: Use of an extended timer in PDU session-related procedures for a terminal

[0367] As the PDU session-related procedure for the terminal is initiated / performed, the N3 PDU session-related procedure for the MWAB-UE may be triggered / performed. When the N3 PDU session-related procedure is completed / terminated, the PDU session-related procedure for the terminal may be completed / terminated.

[0368] When a terminal receives service via MWAB, a timer with a larger value than the conventional timer value may be used for PDU session-related procedures for the terminal. For example, when a terminal receives service via MWAB, a timer with a larger value than the conventional timer value may be used when a PDU session-related procedure for the terminal is initiated.

[0369] An "extended timer" (or SM-related extended timer) in this specification may refer to a timer with a value greater than that of the aforementioned conventional timer. In this regard, the following may apply:

[0370] - 1) When the terminal performs a PDU session establishment procedure (e.g., when the terminal requests PDU session establishment), the terminal can use an extended timer with a larger value than the conventional T3580 value. The extended timer may be used by changing the value of T3580, or a new timer may be defined and used (e.g., extended T3580, extended timer T3580, T3580', long T3580, longer T3580, etc.).

[0371] - 2) When the terminal performs a PDU session modification procedure (e.g., when the terminal requests a PDU session modification procedure, UE-requested PDU Session Modification procedure), the terminal may use an extended timer with a larger value than the conventional T3581 value. The extended timer may be a value of T3581 that is changed and used, or a new timer may be defined and used (e.g., extended T3581, extended timer T3581, T3581', long T3581, longer T3581, etc.).

[0372] - 3) When SMF performs PDU session modification procedure (e.g., Network-requested PDU Session Modification procedure), SMF may use extended timer with a larger value than conventional T3591 value. Extended timer may be used by changing the value of T3591, or a new timer may be defined and used (e.g., extended T3591, extended timer T3591, T3591', long T3591, longer T3591, etc.).

[0373] A PDU session for a terminal may refer to a PDU session for the terminal to receive a service, a PDU session for providing a service to the terminal, a PDU session established by the terminal, or a PDU session for the terminal. This can be applied throughout this specification.

[0374] A terminal can determine / recognize that it is connected or receiving services via MWAB by:

[0375] - A specific MWAB can notify the UE that it is an MWAB (or MWAB cell, mobile base station, or mobile base station cell). For example, a specific MWAB can notify the UE that it is an MWAB (or MWAB cell, mobile base station, or mobile base station cell) through a SIB (or dedicated signal).

[0376] - Alternatively, the core network (e.g., AMF, SMF, etc.) can provide the terminal with the relevant information (e.g., information that the terminal is receiving service through MWAB).

[0377] An SMF (or AMF) can determine / recognize that a terminal it serves (e.g., a terminal of a PDU session it serves) is connected or serviced via MWAB by:

[0378] - A particular MWAB can advertise to the core network (e.g., AMF, SMF, etc.) that it is an MWAB (or MWAB cell, mobile base station, mobile base station cell).

[0379] - Alternatively, a specific MWAB may provide the core network (e.g., AMF, SMF, etc.) with additional ULI information (e.g., Additional ULI, which may be location-related information of the MWAB-UE) in addition to the ULI (User Location Information) of the terminal.

[0380] - Alternatively, SMF (or AMF) can receive information from the terminal about its access or service through MWAB.

[0381] Here, information provided by the MWAB or terminal may be provided to the AMF and then transmitted to the SMF via the AMF. Alternatively, information provided by the MWAB or terminal may be transparently transmitted to the SMF via the AMF.

[0382] Based on the above, the AMF can determine / recognize that the terminal it serves (e.g., the terminal of the PDU session it serves) is connected or serviced via MWAB. Based on this, the AMF can provide the terminal (or SMF) with an SM-related extended timer. The terminal (or SMF) can use the SM-related extended timer provided by the AMF.

[0383] The SM-related extended timer may be a timer for access via the terminal's MWAB.

[0384] The SM-related extended timer (or the value of the SM-related extended timer) can be determined by one or more of the methods a to g described below.

[0385] The SM-related extended timer (or the value of the SM-related extended timer) may be determined in other ways. Alternatively, the SM-related extended timer (or the value of the SM-related extended timer) may be determined based on information provided by various entities.

[0386] Some or all of the SM-related extended timers (or values ​​of the SM-related extended timers) may be determined differently depending on the serving network of the terminal, the serving network of the MWAB-UE, or a combination of the serving network of the terminal and the serving network of the MWAB-UE.

[0387] SM-related extended timers (or values ​​of SM-related extended timers) may be determined / exist / defined for a specific DNN / S-NSSAI, or may be determined / exist / defined independently of the DNN / S-NSSAI (e.g., equally for all DNNs / S-NSSAIs).

[0388] The SM-related extended timer (or the value of the SM-related extended timer) can be determined by one or more of the following methods a to g.

[0389] a) An extended timer related to SM is set on the terminal.

[0390] b) SM related extended timer is set in SMF.

[0391] c) SMF obtains SM-related extended timer from subscriber information (subscriber information stored in UDM).

[0392] d) The SMF obtains the SM-related extended timer from the PCF. The PCF can obtain the SM-related extended timer from the UDR. Alternatively, the SM-related extended timer may be set in the PCF.

[0393] e) The terminal (or SMF) receives the SM-related extended timer (or the value of the SM-related extended timer) from the counterpart entity of the SM-related procedure (e.g., the counterpart entity of the terminal is the SMF, and the counterpart entity of the SMF is the terminal) via an SM NAS message.

[0394] For example, when a terminal transmits a PDU session establishment request message, it can provide an SM-related extended timer (or a value of an SM-related extended timer) to the SMF. Based on this, the SMF can store the provided SM-related extended timer (or the value of the SM-related extended timer). Thereafter, when the SMF performs a PDU session-related procedure (e.g., a network-requested PDU session modification procedure) for the terminal, the SMF can use the stored SM-related extended timer (or the value of the SM-related extended timer).

[0395] For example, when the SMF transmits a PDU session establishment acknowledgement message, the SMF may provide the UE with an SM-related extended timer (or a value of the SM-related extended timer). Based on this, the UE may store the provided SM-related extended timer (or the value of the SM-related extended timer). Thereafter, when the UE performs a PDU session-related procedure for the UE (e.g., a UE-requested PDU Session modification procedure, a PDU Session establishment procedure (a procedure for forming a PDU session other than an established PDU session)), the UE may use the stored SM-related extended timer (or the value of the SM-related extended timer).

[0396] The SMF may obtain the SM-related extended timer (or the value of the SM-related extended timer) from the subscriber information. Alternatively, the SM-related extended timer (or the value of the SM-related extended timer) may be set in the SMF.

[0397] f) AMF provides SM-related extended timers to the terminal.

[0398] For example, when the AMF transmits a registration approval message to the UE, it can provide an SM-related extended timer (or a value of the SM-related extended timer). Based on this, the UE can store the provided SM-related extended timer (or the value of the SM-related extended timer). Thereafter, when the UE performs a PDU session-related procedure for the UE (e.g., UE-requested PDU Session modification procedure, PDU Session establishment procedure), the UE can use the stored SM-related extended timer (or the value of the SM-related extended timer).

[0399] AMF may obtain the SM-related extended timer (or the value of the SM-related extended timer) from subscriber information. Alternatively, the SM-related extended timer (or the value of the SM-related extended timer) may be set in AMF.

[0400] g) AMF provides SM-related extended timers to SMF.

[0401] For example, when the AMF forwards an SM NAS message (e.g., a PDU Session Establishment Request message) transmitted by a terminal to the SMF, the AMF may provide an SM-related extended timer (or a value of the SM-related extended timer). The SMF may store the provided SM-related extended timer (or the value of the SM-related extended timer). Thereafter, when the SMF performs a PDU session-related procedure (e.g., a Network-requested PDU Session modification procedure) for the terminal, the SMF may use the stored SM-related extended timer (or the value of the SM-related extended timer).

[0402] AMF may obtain the SM-related extended timer (or the value of the SM-related extended timer) from subscriber information. Alternatively, the SM-related extended timer (or the value of the SM-related extended timer) may be set in AMF. Alternatively, AMF may obtain the SM-related extended timer (or the value of the SM-related extended timer) from the terminal.

[0403] In PDU session-related procedures for terminals, an extended timer may be used. In addition (or instead), the number of PDU session-related procedure retries may be increased compared to the previous case.

[0404] For example, conventionally, a terminal retransmits a PDU session establishment request message up to n times when a timer expires. According to the first embodiment of the present specification, a terminal can retransmit a PDU session establishment request message up to m (where m is greater than n) times when a timer (or an extended timer) expires.

[0405] 1. First example of the first embodiment

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

[0407] Figure 14 shows a flowchart of a first example of the first embodiment of the present specification.

[0408] MWAB can be in non-roaming or roaming state.

[0409] This description is based on PLMNs. However, PLMNs (HPLMNs and / or VPLMNs) may also be NPNs. This can be applied throughout this specification.

[0410] MWAB-UE is registered to a network (e.g., backhaul network).

[0411] The procedure described below can be applied to the contents described in FIGS. 6 to 9.

[0412] 1) Step 1

[0413] MWAB-UE can establish N3 PDU sessions.

[0414] 2) Step 2

[0415] A UE can perform registration with a network (e.g., the UE's serving network) via MWAB.

[0416] 3) Step 3

[0417] The UE may send a PDU Session Establishment Request message to the MWAB to establish a PDU session. At this time, the UE may initiate / start an extended timer (extended T3580) (the SM extended timer of the first embodiment described above).

[0418] 4) Step 4

[0419] AMF can send a PDU session establishment request message (e.g., a message for establishing a PDU session) to SMF.

[0420] AMF can send SMF an update SM context request message for UE's PDU session (e.g., a message for establishing a PDU session).

[0421] 5) Step 5

[0422] SMF can send a response to AMF.

[0423] 6) Step 6

[0424] The SMF may send a message to the AMF containing a PDU session establishment acknowledgement message and N2 SM information (based on which the base station creates PDU session related resources) (and / or requesting the base station to create PDU session related resources).

[0425] 7) Step 7

[0426] The AMF may send an N2 message to the MWAB-gNB containing messages and information received from the SMF (and / or a request to the base station to create PDU session related resources).

[0427] 8) Step 8

[0428] The MWAB-gNB can send a PDU session related request to the MWAB-UE.

[0429] For example, a PDU session related request may be a request related to an N3 PDU session required to support (or mapped to or associated with) a PDU session of the UE.

[0430] PDU session related requests may also include QoS related information (e.g., specific 5QI / ARP and other QoS parameters).

[0431] Based on the PDU session related request, the MWAB-UE can perform N3 PDU session related procedures (e.g., procedure for establishing a new N3 PDU session, procedure for modifying an existing N3 PDU session).

[0432] In the first example of the first embodiment, the PDU session related request may be for the MWAB-UE to modify an existing N3 PDU session.

[0433] 9) Step 9

[0434] MWAB-UE can modify existing N3 PDU sessions based on requests / information provided by MWAB-gNB.

[0435] 10) Step 10

[0436] The MWAB-UE can send a response to a PDU session related request to the MWAB-gNB.

[0437] The response may contain information indicating that the N3 PDU session related procedure has been completed / terminated.

[0438] Information indicating that an N3 PDU session related procedure has been completed / terminated may indicate or imply that the N3 PDU session related procedure was successful.

[0439] Alternatively, the information indicating that an N3 PDU session related procedure has been completed / terminated may include information such as whether the N3 PDU session related procedure succeeded, failed, or partially succeeded or failed (e.g., multiple QoS Flows need to be added or modified, but only some QoS Flows are added or modified).

[0440] This information may be explicit, implicit or implicit.

[0441] Information indicating that an N3 PDU session related procedure has been completed / terminated may be information that notifies the MWAB-gNB of one or more of the following information:

[0442] - Which QoS Flows can be supported during the UE's PDU sessions,

[0443] - Which QoS Flows cannot be supported?

[0444] - Which QoS Flow can be supported at which level of QoS, etc.

[0445] 11) Step 11

[0446] The MWAB-gNB can send a response to step 3 to the UE.

[0447] The MWAB-gNB can perform resource setup related to the PDU session established by the UE through AN-specific signaling exchange with the UE and transmit a PDU session establishment approval message to the UE.

[0448] For example, the MWAB-gNB can set up resources related to a PDU session established by a UE. Then, the MWAB-gNB can send a PDU session establishment acknowledgement message to the UE.

[0449] When the UE receives a PDU Session Establishment Acknowledgement message, it can stop the extended timer (extended T3580).

[0450] 12) Step 12

[0451] The PDU session establishment procedure for the UE may be completed / terminated.

[0452] If the MWAB-gNB receives from the MWAB-UE that the N3 PDU session related procedure failed in step 10, the MWAB-gNB may, instead of performing step 11, transmit N2 SM information (which may be as described in section 4.3.2 of TS 23.502 v18.6.0 or may include newly defined or modified information) informing the SMF that the PDU session related resource creation request was not successful (or failed or rejected).

[0453] The SMF may then send a PDU Session Establishment Reject message to the UE. When the UE receives the PDU Session Establishment Reject message, the extended timer (extended T3580) may be stopped.

[0454] 2. Second example of the first embodiment

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

[0456] Figure 15 shows a flowchart of a second example of the first embodiment of the present specification.

[0457] MWAB can be in non-roaming or roaming state.

[0458] This description is based on PLMNs. However, PLMNs (HPLMNs and / or VPLMNs) may also be NPNs. This can be applied throughout this specification.

[0459] The second example of the first embodiment can be combined with the first example of the first embodiment described above. For example, after a PDU session is established through the first example of the first embodiment, a procedure for modifying the PDU session established through the second example of the first embodiment can be performed.

[0460] There may be a PDU session established by the UE, and there may be an N3 PDU session mapped (or associated) to the PDU session.

[0461] 1) Step 1

[0462] The SMF may send a message containing a PDU Session Modification Command to the AMF to modify an existing PDU session. At this time, the SMF may initiate / start an extended timer (extended T3591) (the SM extended timer of the first embodiment described above).

[0463] For SMF using extended T3591 instead of T3591, please refer to the SM extended timer content of the first embodiment described above.

[0464] The message sent by the SMF to the AMF may include N2 SM information for modifying PDU session related resources (and / or a request to the base station to modify PDU session related resources).

[0465] 2) Step 2

[0466] The AMF may send an N2 message containing messages and / or information received from the SMF (and / or a request to the base station to modify PDU session related resources) to the MWAB-gNB.

[0467] 3) Step 3

[0468] The MWAB-gNB can send a PDU session related request to the MWAB-UE.

[0469] For example, a PDU session related request may be a request related to an N3 PDU session required to support (or mapped to or associated with) a PDU session of the UE.

[0470] PDU session related requests may also include QoS related information (e.g., specific 5QI / ARP and other QoS parameters).

[0471] Based on the PDU session related request, the MWAB-UE can perform N3 PDU session related procedures (e.g., procedure for establishing a new N3 PDU session, procedure for modifying an existing N3 PDU session).

[0472] In the second example of the first embodiment, the PDU session related request may be for the MWAB-UE to modify an existing N3 PDU session.

[0473] 4) Step 4

[0474] MWAB-UE can modify existing N3 PDU sessions based on requests / information provided by MWAB-gNB.

[0475] 5) Step 5

[0476] The MWAB-UE can send a response to a PDU session related request to the MWAB-gNB.

[0477] The response may contain information indicating that the N3 PDU session related procedure has been completed / terminated.

[0478] Information indicating that an N3 PDU session related procedure has been completed / terminated may indicate or imply that the N3 PDU session related procedure was successful.

[0479] Alternatively, the information indicating that an N3 PDU session related procedure has been completed / terminated may include information such as whether the N3 PDU session related procedure succeeded, failed, or partially succeeded or failed (e.g., multiple QoS Flows need to be added or modified, but only some QoS Flows are added or modified).

[0480] This information may be explicit, implicit or implicit.

[0481] Information indicating that an N3 PDU session related procedure has been completed / terminated may be information that notifies the MWAB-gNB of one or more of the following information:

[0482] - Which QoS Flows can be supported during the UE's PDU sessions,

[0483] - Which QoS Flows cannot be supported?

[0484] - Which QoS Flow can be supported at which level of QoS, etc.

[0485] 6) Step 6

[0486] The MWAB-gNB can perform resource modification related to the PDU session established by the UE through AN-specific signaling exchange with the UE and transmit a PDU session modification command message to the UE.

[0487] For example, the MWAB-gNB may modify resources associated with a PDU session established by the UE. Furthermore, the MWAB-gNB may send a PDU session modification command message to the UE.

[0488] 7) Step 7

[0489] The UE may send a PDU Session Modification Complete message (e.g., in response to a Modify Command message) to the SMF. The PDU Session Modification Complete message may be a PDU Session Modification Ack message.

[0490] When the SMF receives the above PDU session modification complete message, it can stop the extended timer (extended T3591).

[0491] 8) Step 8

[0492] The PDU session modification procedure for the UE may be completed / terminated.

[0493] If the MWAB-gNB receives from the MWAB-UE that the N3 PDU session related procedure failed in step 5, the MWAB-gNB may, instead of performing step 6, transmit N2 SM information (which may be as described in section 4.3.2 of TS 23.502 v18.6.0 or may include newly defined or modified information) informing the SMF that the PDU session related resource modification request was not successful (or failed or rejected).

[0494] Then, SMF can abort the PDU session modification procedure.

[0495] Alternatively, the SMF may generate N2 SM information that includes another QoS Flow (or a QoS Flow with different QoS characteristics). The SMF may transmit a PDU Session Modification Command message to the UE, reflecting the contents of the N2 SM information. Upon receiving this, the UE may transmit a PDU Session Modification Complete message to the SMF. The PDU Session Modification Complete message may be a PDU Session Modification Ack message.

[0496] When the SMF receives a PDU Session Modification Complete message, the SMF can stop the extended timer (extended T3591).

[0497] II. Second embodiment: Use of shortened timer in PDU session related procedures for MWAB-UE

[0498] As the PDU session-related procedure for the terminal is initiated / performed, the N3 PDU session-related procedure for the MWAB-UE may be triggered / performed. When the N3 PDU session-related procedure is completed / terminated, the PDU session-related procedure for the terminal may be completed / terminated.

[0499] The proposed method of the second embodiment can be applied to step 9 of FIG. 14 or step 4 of FIG. 15.

[0500] A timer with a smaller value than the conventional timer value may be used for N3 PDU session-related procedures for MWAB-UEs. For example, when performing N3 PDU session-related procedures for MWAB-UEs, a timer with a smaller value than the conventional timer value may be used.

[0501] The shortened timer (or SM-related shortened timer) in this specification may refer to a timer with a value smaller than that of the conventional timer described above. In this regard, the following may apply:

[0502] - 1) When the MWAB-UE performs a PDU session establishment procedure (e.g., when the MWAB-UE requests PDU session establishment), the MWAB-UE can use a shortened timer with a smaller value than the conventional T3580 value. The shortened timer may be used by changing the value of T3580, or a new timer may be defined and used (e.g., shortened T3580, shortened timer T3580, T3580'', short T3580, shorter T3580, etc.).

[0503] - 2) When the MWAB-UE performs a PDU session modification procedure (e.g., when the MWAB-UE requests a PDU session modification procedure, UE-requested PDU Session Modification procedure), the MWAB-UE may use a shortened timer with a smaller value than the conventional T3581 value. The shortened timer may be used by changing the value of T3581, or a new timer may be defined and used (e.g., shortened T3581, shortened timer T3581, T3581'', short T3581, shorter T3581, etc.).

[0504] - 3) When SMF performs PDU session modification procedure (e.g., Network-requested PDU Session Modification procedure), SMF may use a shortened timer with a smaller value than the conventional T3591 value. The shortened timer may be used by changing the value of T3591, or a new timer may be defined and used (e.g., shortened T3591, shortened timer T3591, T3591'', short T3591, shorter T3591, etc.).

[0505] Since the DNN, or S-NSSAI, or combination of DNN / S-NSSAI is for the N3 interface, the MWAB-UE (or SMF) can determine / recognize that the PDU session is for the N3 interface.

[0506] N3 PDU sessions may also be used for N2 interfaces and / or OAM (or OAM server connections, configuration from OAM).

[0507] AMF can provide SM-related shortened timers to MWAB-UE (or SMF). Based on this, MWAB-UE (or SMF) can use SM-related shortened timers.

[0508] An AMF can determine / recognize that the UE it is serving is an MWAB-UE by:

[0509] - MWAB-UE has provided that it is MWAB-UE, and / or

[0510] - MWAB-UE can use DNN / S-NSSAI for MWAB operation (this corresponds to one or more of N2 interface connection, N3 interface connection, and OAM server connection).

[0511] The SM-related short timer (or the value of the SM-related short timer) can be determined by one or more of the methods A to G described below.

[0512] The SM-related short timer (or the value of the SM-related short timer) may be determined in other ways. Alternatively, the SM-related short timer (or the value of the SM-related short timer) may be determined based on information provided by various entities.

[0513] Some or all of the SM-related shortened timers (or values ​​of the SM-related shortened timers) may be determined differently depending on the serving network of the terminal, the serving network of the MWAB-UE, or the combination of the serving network of the terminal and the serving network of the MWAB-UE.

[0514] SM-related short timers (or values ​​of SM-related short timers) may be determined / exist / defined for a specific DNN / S-NSSAI, or may be determined / exist / defined independently of the DNN / S-NSSAI (e.g., identically for all DNNs / S-NSSAIs).

[0515] The SM-related short timer (or the value of the SM-related short timer) can be determined by one or more of the following methods A to G.

[0516] A) SM related short timer is set in MWAB-UE.

[0517] B) SM related short timer is set in SMF.

[0518] C) SMF obtains SM-related short timer from subscriber information (subscriber information stored in UDM).

[0519] D) The SMF obtains the SM-related shortened timer from the PCF. The PCF can obtain the SM-related shortened timer from the UDR. Alternatively, the SM-related extended timer may be set in the PCF.

[0520] E) MWAB-UE (or SMF) receives SM-related shortened timer (or value of SM-related shortened timer) from counterpart entity of SM-related procedure (e.g., counterpart entity of MWAB-UE is SMF, counterpart entity of SMF is MWAB-UE) via SM NAS message.

[0521] For example, when an MWAB-UE transmits a PDU session establishment request message, it can provide an SM-related shortened timer (or a value of an SM-related shortened timer) to the SMF. Based on this, the SMF can store the provided SM-related shortened timer (or a value of an SM-related shortened timer). Thereafter, when the SMF performs a PDU session-related procedure (e.g., a network-requested PDU session modification procedure) for the MWAB-UE, the SMF can use the stored SM-related shortened timer (or a value of an SM-related shortened timer).

[0522] For example, when the SMF transmits a PDU session establishment acknowledgement message, the SMF may provide the SM-related shortened timer (or the value of the SM-related shortened timer) to the MWAB-UE. Based on this, the MWAB-UE may store the provided SM-related shortened timer (or the value of the SM-related shortened timer). Thereafter, when the MWAB-UE performs an N3 PDU session-related procedure (e.g., a UE-requested PDU Session modification procedure, a PDU Session establishment procedure (a procedure for establishing a PDU Session different from the N3 PDU Session established above)), the MWAB-UE may use the stored SM-related shortened timer (or the value of the SM-related shortened timer).

[0523] The SMF may obtain the SM-related shortened timer (or the value of the SM-related shortened timer) from subscriber information. Alternatively, the SM-related shortened timer (or the value of the SM-related shortened timer) may be set in the SMF.

[0524] F) AMF provides SM-related shortened timers to MWAB-UE.

[0525] For example, when the AMF sends a registration acknowledgement message to the MWAB-UE, it can provide the SM-related shortened timer (or the value of the SM-related shortened timer). Based on this, the MWAB-UE can store the provided SM-related shortened timer (or the value of the SM-related shortened timer). Thereafter, when the MWAB-UE performs an N3 PDU session-related procedure (e.g., UE-requested PDU Session modification procedure, PDU Session establishment procedure), the MWAB-UE can use the stored SM-related shortened timer (or the value of the SM-related shortened timer).

[0526] AMF may obtain the SM-related shortened timer (or the value of the SM-related shortened timer) from subscriber information. Alternatively, the SM-related shortened timer (or the value of the SM-related shortened timer) may be set in AMF.

[0527] G) AMF provides SM-related short timers to SMF.

[0528] For example, the AMF may provide the SM-related shortened timer (or the value of the SM-related shortened timer) to the SMF when forwarding the SM NAS message (e.g., PDU Session Establishment Request message) transmitted by the MWAB-UE. The SMF may store the provided SM-related shortened timer (or the value of the SM-related shortened timer). Thereafter, when the SMF performs an N3 PDU session-related procedure (e.g., Network-requested PDU Session modification procedure), the SMF may use the stored SM-related shortened timer (or the value of the SM-related shortened timer).

[0529] The AMF may obtain the SM-related shortened timer (or the value of the SM-related shortened timer) from subscriber information. Alternatively, the SM-related shortened timer (or the value of the SM-related shortened timer) may be configured in the AMF. Alternatively, the AMF may obtain the SM-related shortened timer (or the value of the SM-related shortened timer) from the MWAB-UE.

[0530] In N3 PDU session-related procedures for MWAB-UEs, a shortened timer may be used. This reduces the time required to determine the final failure of a PDU session-related procedure based on timer expiration and subsequent retry, compared to the conventional time. This also reduces the time it takes for the MWAB-UE to transmit a PDU session-related response to the MWAB-gNB.

[0531] In N3 PDU session-related procedures for MWAB-UEs, a shortened timer may be used. In addition (or instead), the number of PDU session-related procedure retries may be reduced compared to the previous case.

[0532] For example, conventionally, an MWAB-UE retransmits a PDU session modification request message up to n times when a timer expires. According to the second embodiment of the present specification, the UE can retransmit a PDU session modification request message up to m (m is less than n) times when a timer (or shortened timer) expires.

[0533] III. Third embodiment: When the N3 PDU session related procedure is performed after the PDU session related procedure for the UE is completed.

[0534] The extended timer of the first embodiment or the shortened timer of the second embodiment may not be used.

[0535] Unlike the first and second embodiments, after the PDU session related procedures for the UE are completed / terminated, the N3 PDU session related procedures required (or mapped or associated) to service the PDU session for the UE can be performed.

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

[0537] Figure 16 shows a flowchart of the third embodiment of the present specification.

[0538] MWAB can be in non-roaming or roaming state.

[0539] This description is based on PLMNs. However, PLMNs (HPLMNs and / or VPLMNs) may also be NPNs. This can be applied throughout this specification.

[0540] MWAB-UE is registered to a network (e.g., backhaul network).

[0541] MWAB-UE can also establish N3 PDU sessions.

[0542] 1) Step 1

[0543] A UE can perform registration with the network via MWAB.

[0544] 2) Step 2

[0545] A UE can establish a PDU session. A PDU session establishment procedure for the UE can be performed.

[0546] Alternatively, the UE may modify a previously established PDU session. A PDU session modification procedure may be performed for the UE.

[0547] 3) Step 3

[0548] As the UE establishes / modifies a PDU session, the SMF may transmit N2 SM information to the MWAB-gNB in ​​step 2. Based on this, the MWAB-gNB may transmit a PDU session-related request to the MWAB-UE to support the PDU session. For the request, refer to the first and second examples of Embodiment 1.

[0549] 4) Step 4

[0550] The MWAB-UE may perform a procedure to establish an N3 PDU session or a procedure to modify a previously established N3 PDU session.

[0551] In the third embodiment, it is assumed that the N3 PDU session related procedure has failed, or partially succeeded or failed (e.g., multiple QoS Flows need to be added or modified, but only some of the QoS Flows are added or modified).

[0552] 5) Step 5

[0553] The MWAB-UE can send a PDU session related response to the MWAB-gNB.

[0554] The response may contain information indicating that the N3 PDU session related procedure failed, or was partially successful or failed (e.g., multiple QoS Flows were to be added or modified, but only some QoS Flows were added or modified).

[0555] This information may be explicit, implicit or implicit.

[0556] The information described above (indicating that an N3 PDU session related procedure failed, or was partially successful or failed (e.g., multiple QoS Flows were to be added or modified, but only some QoS Flows were added or modified)) may inform the MWAB-gNB of one or more of the following information:

[0557] - Which QoS Flows can be supported during the UE's PDU session?

[0558] - Which QoS Flows cannot be supported?

[0559] - Which QoS Flow can be supported at which level of QoS, etc.

[0560] If there is a QoS Flow of a UE that cannot be supported, the MWAB-gNB can map the QoS Flow to another QoS Flow of the N3 PDU session.

[0561] 6) Step 6

[0562] The MWAB-gNB may inform the SMF of at least one of the following information using the N2 SM information:

[0563] - Which QoS Flows can be supported during the UE's PDU sessions,

[0564] - Which QoS Flows cannot be supported?

[0565] - Which QoS Flow can be supported at which level of QoS, etc.

[0566] Alternatively, the MWAB-gNB can only inform the SMF about the QoS Flows that it cannot support (or the QoS Flows that it can support but cannot support at the level requested by the SMF).

[0567] If the PDU session establishment procedure is performed in Step 2, the MWAB-gNB may release the corresponding PDU session (e.g., PDU session related resources / context) and notify the SMF that the PDU session (e.g., PDU session related resources / context) has been released. Based on this, the SMF may perform the procedure to release the PDU session to the UE instead of Step 7. This PDU session release procedure of the SMF may be performed especially when the N3 PDU session related procedure fails.

[0568] 7) Step 7

[0569] Based on the information provided by the MWAB-gNB, the SMF can perform procedures to modify the PDU session with the UE. For example, the SMF can send a PDU Session Modification Command message to the AMF.

[0570] 8) Step 8

[0571] AMF can send a PDU Session Modification Command message to the UE.

[0572] After step 5, the MWAB-gNB may send a PDU session-related request to the MWAB-UE for a QoS Flow that it cannot support at all (or cannot support at the desired level). Based on this, the MWAB-UE can perform the N3 PDU session-related procedure to support the corresponding QoS Flow (or support it at the desired level).

[0573] Alternatively, after step 5, the MWAB-UE may perform N3 PDU session related procedures to enable it to support (or support to a desired level) a QoS Flow that it cannot support at all (or cannot support to a desired level).

[0574] If such QoS Flow can be supported, the MWAB-UE can notify the MWAB-gNB of this fact. Based on this, the MWAB-gNB can notify the SMF of this fact. Then, the SMF can perform a procedure to modify the PDU session with the UE. For example, the SMF can send a PDU Session Modification Command message to the AMF. The AMF can send a PDU Session Modification Command message to the UE.

[0575] According to the disclosure of this specification, when a UE receives service through a MWAB (e.g., a mobile base station), PDU session-related procedures for the UE may not be unnecessarily retried. Furthermore, a UE seeking emergency services may not needlessly reselect another domain / network. This allows the UE to receive seamless service.

[0576] According to the disclosure of this specification, for example, the following actions may be performed:

[0577] - PDU session-related procedures for UEs receiving services through MWAB can be initiated / performed. If the UE initiates a PDU session-related procedure, the UE can initiate / start an SM-related extended timer. If the SMF initiates a PDU session-related procedure, the SMF can initiate / start an SM-related extended timer.

[0578] - MWAB-gNB can send PDU session related requests to MWAB-UE.

[0579] - MWAB-UE can perform N3 PDU session related procedures.

[0580] - MWAB-UE can send PDU session related responses to MWAB-gNB.

[0581] - MWAB-gNB can continue PDU session related procedures for the UE.

[0582] - PDU session related procedures for UE can be completed / terminated.

[0583] An entity (e.g., UE, SMF) that initiates a PDU session-related procedure can receive an SM NAS message from the counterpart entity. Based on this, the entity that initiated the PDU session-related procedure can stop the previously started SM-related extension timer.

[0584] If the entity initiating the PDU session related procedure is a UE, the counterpart entity may be an SMF.

[0585] If the entity initiating the PDU session related procedure is SMF, the counterpart entity may be UE.

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

[0587] Figure 17 illustrates the UE's procedure for disclosure of this specification.

[0588] 1. The UE (User Equipment) can send a session message for a PDU (Protocol Data Unit) session to the base station.

[0589] 2. Based on the UE transmitting the session message, the UE can start a session management timer.

[0590] Based on the above base station being MWAB (Mobile gNB with wireless access backhauling), the session management timer may be a timer for access via MWAB.

[0591] Based on the above base station being MWAB, the value of the session management timer may be greater than the value of the timer for the case where the above base station is not MWAB.

[0592] The UE can receive a System Information Block (SIB) from the base station.

[0593] The above SIB may include information that the base station is an MWAB.

[0594] The step of the UE starting the session management timer may be performed based on the SIB.

[0595] The UE may receive information about the session management timer from an Access and Mobility management Function (AMF).

[0596] The value of the above session management timer can be determined based on information about the above session management timer.

[0597] The above UE may send an establishment request message for a previous PDU session to the SMF (Session Management Function).

[0598] The UE may further include a step of receiving an acknowledgement message for the previous PDU session from the SMF.

[0599] The step of the UE transmitting the session message may be performed after the step of the UE receiving an acknowledgment message for the previous PDU session.

[0600] The acknowledgement message for the previous PDU session may include information about a timer associated with the session.

[0601] The above session message may be a modification request message for the previous PDU session or an establishment request message for the PDU session.

[0602] The value of the above session management timer can be determined based on information about the above session management timer.

[0603] The UE may receive a response to the session message from the base station.

[0604] Based on the above response, the UE may stop the session management timer.

[0605] Based on the expiration of the session management timer, the UE may retransmit the session message to the base station.

[0606] The above session message may be an establishment request message for the PDU session or a modification request message for the PDU session.

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

[0608] Figure 18 illustrates the SMF procedure for the disclosure of this specification.

[0609] 1. The SMF (Session Management Function) can send a modification command for a PDU session for the UE (User Equipment) to the AMF (Access and Mobility management Function).

[0610] 2. Based on the above SMF sending the above modification command, the above SMF can start the session management timer.

[0611] Based on the fact that the serving base station of the UE is MWAB (Mobile gNB with wireless access backhauling), the session management timer may be a timer for access through the MWAB of the UE.

[0612] Based on the serving base station being MWAB, the value of the session management timer may be greater than the value of the timer for cases where the serving base station is not MWAB.

[0613] The above SMF can receive MWAB information from the AMF that the serving base station is an MWAB.

[0614] The step of the above SMF starting the session management timer may be performed based on the above MWAB information.

[0615] The above SMF can receive information about the session management timer from the above AMF.

[0616] The value of the above session management timer can be determined based on information about the above session management timer.

[0617] The above SMF can receive a message for establishing the PDU session from the above AMF.

[0618] Based on the message for establishing the above PDU session, the SMF can send an establishment approval message for the PDU session to the AMF.

[0619] The step of the SMF transmitting the modification command may be performed after the step of the SMF transmitting the establishment approval message.

[0620] The message for establishing the above PDU session may include information about the session management timer.

[0621] The value of the above session management timer can be determined based on information about the above session management timer.

[0622] The above SMF can receive a completion message for the above modification command from the above AMF.

[0623] Based on the above completion message, the SMF may stop the session management timer.

[0624] Based on the expiration of the above session management timer, the SMF may resend the above modification command to the AMF.

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

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

[0627] For example, a processor may be configured to be operatively coupled with memory and a processor.

[0628] The operations performed by the processor include: a step of the UE transmitting a session message for a Protocol Data Unit (PDU) session to the base station; a step of the UE starting a session management timer based on the UE transmitting the session message, and based on the base station being an MWAB (Mobile gNB with wireless access backhauling), the session management timer may be a timer for access via MWAB.

[0629] Below, a processor of a device for providing communication according to some embodiments of the present specification is described.

[0630] The operations performed by the processor include: a step of the UE transmitting a session message for a Protocol Data Unit (PDU) session to the base station; a step of the UE starting a session management timer based on the UE transmitting the session message, and based on the base station being an MWAB (Mobile gNB with wireless access backhauling), the session management timer may be a timer for access via MWAB.

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

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

[0633] Some examples of storage media are coupled to the processor, allowing the processor to read information from the storage media. Alternatively, the storage media may be integrated into the processor. The processor and storage media may reside in an ASIC. In other examples, the processor and storage media may reside as separate components.

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

[0635] For example, nonvolatile computer-readable media may include random access memory (RAM), such as synchronized dynamic random access memory (SDRAM), read-only memory (ROM), non-volatile random access memory (NVRAM), read-only memory (EEPROM), flash memory, magnetic or optical data storage media, or any other media that can be used to store instructions or data structures. Nonvolatile computer-readable media may also include combinations of the above.

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

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

[0638] The one or more stored commands include: a step of the UE transmitting a session message for a Protocol Data Unit (PDU) session to the base station; and a step of the UE starting a session management timer based on the UE transmitting the session message, wherein the session management timer may be a timer for access via MWAB (Mobile gNB with wireless access backhauling) based on the base station being an MWAB.

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

[0640] This specification may have various effects.

[0641] For example, a timer taking MWAB into account can be set through the procedures disclosed herein.

[0642] The effects that can be achieved through 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.

[0643] 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. As a method, A step in which a UE (User Equipment) transmits a session message for a PDU (Protocol Data Unit) session to a base station; A step of the UE starting a session management timer based on the UE transmitting the session message, A method in which the above-mentioned base station is a MWAB (Mobile gNB with wireless access backhauling), and the above-mentioned session management timer is a timer for access via MWAB.

2. In paragraph 1, Based on the above base station being MWAB, the value of the session management timer is greater than the value of the timer for the case where the above base station is not MWAB.

3. In paragraph 1 or 2, The UE further includes a step of receiving a SIB (System Information Block) from the base station, The above SIB includes information that the base station is MWAB, The step of the UE starting the session management timer is: a method performed based on the SIB.

4. In any one of the clauses 1 to 3, The UE further comprises a step of receiving information about the session management timer from an Access and Mobility management Function (AMF), A method in which the value of the above session management timer is determined based on information about the above session management timer.

5. In any one of paragraphs 1 to 3, A step in which the UE transmits an establishment request message for a previous PDU session to the SMF (Session Management Function); The UE further comprises a step of receiving an acknowledgment message for the previous PDU session from the SMF, The step of the UE transmitting the session message is performed after the step of the UE receiving an acknowledgment message for the previous PDU session, The acknowledgement message for the above previous PDU session contains information about the timer associated with the above session, The above session message is a modification request message for the previous PDU session or an establishment request message for the PDU session, A method in which the value of the above session management timer is determined based on information about the above session management timer.

6. In any one of paragraphs 1 to 5, A step in which the UE receives a response to the session message from the base station; and A method further comprising the step of the UE stopping the session management timer based on the response.

7. In any one of paragraphs 1 to 5, A method further comprising the step of the UE retransmitting the session message to the base station based on the expiration of the session management timer.

8. In any one of paragraphs 1 to 7, The above session message is a method in which an establishment request message for the PDU session or a modification request message for the PDU session.

9. As a method, A step in which the SMF (Session Management Function) sends a modification command for a PDU session for the UE (User Equipment) to the AMF (Access and Mobility management Function); A step of the SMF starting a session management timer based on the SMF sending the modification command, A method in which the session management timer is a timer for access through the MWAB of the UE, based on the serving base station of the UE being MWAB (Mobile gNB with wireless access backhauling).

10. In paragraph 9, A method in which the value of the session management timer is greater than the value of the timer for the case in which the serving base station is not MWAB, based on the serving base station being MWAB.

11. In paragraph 9 or 10, The SMF further includes a step of receiving MWAB information from the AMF, wherein the serving base station is MWAB, The step of the above SMF starting the session management timer is: a method performed based on the above MWAB information.

12. In any one of the clauses 9 to 11, The SMF further comprises a step of receiving information about the session management timer from the AMF, A method in which the value of the above session management timer is determined based on information about the above session management timer.

13. In any one of the clauses 9 to 11, A step in which the SMF receives a message for establishing the PDU session from the AMF; Based on the message for establishing the PDU session, the SMF further includes a step of transmitting an establishment approval message for the PDU session to the AMF, The step of the SMF transmitting the modification command is performed after the step of the SMF transmitting the establishment approval message, The message for establishing the above PDU session includes information about the session management timer, A method in which the value of the above session management timer is determined based on information about the above session management timer.

14. In any one of the clauses 9 to 13, a step in which the SMF receives a completion message for the modification command from the AMF; and A method further comprising the step of the SMF stopping the session management timer based on the completion message.

15. In any one of the clauses 9 to 13, A method further comprising the step of the SMF resending the modify command to the AMF based on the expiration of the session management timer.

16. As a UE (User Equipment) performing communication, At least one transmitter and receiver; Contains at least one processor, A specific UE wherein the operation performed by at least one processor is a method according to any one of claims 1 to 8.

17. As a SMF (Session Management Function) that performs communication, At least one transmitter and receiver; Contains at least one processor, The operation performed by said at least one processor is a method according to any one of claims 9 to 15. SMF.

18. 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, A device wherein the operation performed based on the command being executed by at least one processor is a method according to any one of claims 1 to 8.

19. A non-volatile computer-readable storage medium that records commands, A non-volatile computer-readable storage medium, wherein the instructions, when executed by one or more processors, cause the one or more processors to perform a method according to any one of claims 1 to 8.

Images