Timer setting method

Abstract

One disclosure of the present specification provides a method. The method comprises the steps in which: an NF requests an NWDAF for analytics for a NAS procedure; a UE performs the NAS procedure through a satellite, and the NF receives a first analytics from the NWDAF on the basis of the request; the NF determines a value of a NAS-related timer on the basis of the first analytics; and the NF transmits information about the determined value of the NAS-related timer to the UE.

Description

How to set a timer

[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] The timer is set based on analytics.

[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] Figures 14 and 15 show examples of flowcharts according to the first embodiment of the present specification.

[0018] Figures 16 and 17 show examples of flowcharts according to the first and second embodiments of the present specification.

[0019] Figures 18 and 19 show examples of flowcharts according to embodiment 3-1 of the present specification.

[0020] Figure 20 illustrates the NF procedure for the disclosure of this specification.

[0021] Figure 21 illustrates the UE's procedure for 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, mitigating, curing, or preventing a disease. For example, a medical device may be a device used for the purpose of diagnosing, treating, mitigating, 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), recorder, or 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 6 GHz range," and FR2 can mean the "above 6 GHz 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] For clarity of the point-to-point diagram in Figure 5, 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 (e.g., session management 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 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.

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

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

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

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

[0341] When a UE is served via MWAB, a longer timer value may be applied to the timer for PDU session related procedures.

[0342] For example, regardless of various UE-related circumstances (e.g., the network to which the MWAB is connected / accessed, the location of the MWAB, the location of the UE, the time zone, etc.), a UE receiving service from the MWAB (or the SMF serving the UE) can use a timer with a fixed longer timer value.

[0343] These fixed timer values ​​may have the side effect of unnecessarily delaying PDU session related procedure retries (or domain / network reselection for emergency services).

[0344] For example, when an MWAB connects to PLMN#1 and performs base station operations, the N3 PDU session related procedures (e.g., establishment procedures, modification procedures) of the MWAB-UE may typically take N hours. On the other hand, when an MWAB connects to PLMN#2 and performs base station operations, the N3 PDU session related procedures (e.g., establishment procedures, modification procedures) of the MWAB-UE may typically take 1.5 times N hours.

[0345] As another example, when MWAB performs base station operations by connecting to PLMN#1, N3 PDU session related procedures (e.g., establishment procedure, modification procedure) of MWAB-UE may typically take M hours on Sunday. On the other hand, when MWAB performs base station operations by connecting to PLMN#1, N3 PDU session related procedures (e.g., establishment procedure, modification procedure) of MWAB-UE may typically take twice M hours on Monday.

[0346] Therefore, when setting a timer for a UE (e.g., a timer related to SM (Session management) or a timer related to MM (Mobility Management, NAS), the situation related to the MWAB and the UE receiving service from the MWAB (and / or the situation of the network to which the UE is connected (e.g., a base station, an access network, a RAT, etc.)) needs to be taken into consideration.

[0347] For MM related timers and overall NAS operation, please refer to TS 24.501 v18.7.0.

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

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

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

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

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

[0353] In this specification, the Backhaul (BH) underlay Core Network of MWAB, the underlay Core Network of MWAB and the Core Network to which MWAB connects / registers to connect N2 / N3 interfaces to 5GC, the Core Network of MWAB-UE, the Core Network serving MWAB-UE, and the Core Network to which MWAB-UE connects / registers are used interchangeably for description.

[0354] In this specification, Backhaul (BH) network may be interpreted as including one or more of a Backhaul (BH) base station and a Backhaul (BH) Core Network.

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

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

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

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

[0359] In this specification, 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.

[0360] In this specification, setting / determining / changing / adjusting the timer(s) may mean setting / determining / changing / adjusting the value of the timer(s).

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

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

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

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

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

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

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

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

[0369] In this specification, NAS operation, NAS procedure, NAS message exchange, etc. may be used interchangeably.

[0370] In this specification, NAS operation may be interpreted as including one or more of Mobility Management (MM) related operations and Session Management (SM) related operations.

[0371] In this specification, a NAS timer may be interpreted as including at least one of an MM-related timer and an SM-related timer.

[0372] In this specification, conventional PDU session related operations / procedures / timers / messages, MM 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 addition, conventional NWDAF analytics related operations / procedures / messages, etc. may refer to TS 23.288 v18.6.0. This specification mainly describes the proposed matters.

[0373] I. Embodiment 1: Setting / determining / changing / adjusting SM-related timer values ​​for UEs receiving services via MWAB using NWDAF analytics.

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

[0375] The PDU session related procedure for the UE may be initiated / performed, the N3 PDU session related procedure for the MWAB-UE may be triggered / performed, the N3 PDU session related procedure may be completed / terminated, and the PDU session related procedure for the UE may be completed / terminated in that order.

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

[0377] In this specification, setting / determining / changing / adjusting SM-related timer values ​​for a UE receiving service via MWAB may mean using conventional SM-related timers with different values. In this specification, setting / determining / changing / adjusting SM-related timer values ​​for a UE receiving service via MWAB may also mean separately defining and using the timer(s) themselves for cases where the UE receives service via MWAB.

[0378] When a UE receives services via MWAB, a new analytics model may be defined to determine / set the timer values ​​used when performing PDU session-related procedures for the UE. This analytics model may be called "Session Management Experience via Mobile RAN Analytics." However, this designation is an example, and analytics models may be defined under other names.

[0379] Service consumers (NFs) (e.g., SMF, AMF, PCF, etc.) can request analytics (e.g., Session Management Experience via Mobile RAN Analytics) from NWDAF. A typical reason why a service consumer (NF) might request analytics from NWDAF is because the serving UE receives services from the network via MWAB. However, service consumers can also request analytics from NWDAF for various other reasons / conditions.

[0380] An SMF can determine / recognize that a UE it serves (e.g., a UE of a PDU session it serves) is connected (or serviced) via MWAB in the following cases:

[0381] - When the MWAB informs the Core Network Function (e.g., AMF, SMF, etc.) that it is an MWAB (or a mobile base station, or an MWAB cell, or a mobile base station cell), or

[0382] - If MWAB provides additional ULI information other than the UE's ULI (User Location Information) (e.g., Additional ULI, which may be location-related information of MWAB-UE (e.g., Cell ID, TAI, coordinate information, etc.)), or

[0383] - When SMF receives information from UE that UE has connected (or is receiving service) through MWAB.

[0384] Here, information provided by the MWAB or UE may be provided to the AMF and then forwarded to the SMF via the AMF. Alternatively, information provided by the MWAB or UE may be transparently provided to the SMF via the AMF. This can be applied throughout this specification.

[0385] The method by which the AMF determines / recognizes that the UE it serves has connected (or is receiving service) via MWAB can be referred to the case of the SMF described above (where the SMF determines / recognizes that the UE it serves (e.g., the UE of the PDU session it serves) has connected (or is receiving service) via MWAB). This can be applied throughout this specification.

[0386] The PCF can determine / recognize that a UE it serves (e.g., a UE of a target PDU session that has formed an SM policy association with an SMF, a target UE that has formed a UE policy association with an AMF, or a target UE that has formed an AM policy association with an AMF) is connected or served via MWAB in the following cases:

[0387] - If relevant information is provided by SMF or AMF

[0388] This can be applied throughout this specification.

[0389] A service consumer (NF) can send a message (e.g., a subscription message, a request message) to the NWDAF to request analytics (e.g., Session Management Experience via Mobile RAN Analytics). The message may include at least one of the following information:

[0390] - Analytics ID = "Session Management Experience via Mobile RAN".

[0391] - Target of Analytics Reporting: a single UE (SUPI) or a list of UEs (a list of SUPIs) or group of UEs (ie a list of Internal Group Ids) or any UE.

[0392] - Analytics Filter Information: The following information may be included / provided explicitly, implicitly, implicitly, or in any combination. eg, (Optional) DNN and / or S-NSSAI (DNN and / or S-NSSAI related to the PDU session of the UE receiving service through MWAB), (Optional) area of ​​interest (area of ​​interest information (or location information) related to the location of the UE receiving service through MWAB. For example, it can be expressed as Cell ID(s), TAI(s), RAN node ID(s), coordinate information, etc.), (Optional) area of ​​interest for MWAB (area of ​​interest information (or location information) related to the location of the MWAB (or MWAB-UE). For example, it can be expressed as Cell ID(s), TAI(s), RAN node ID(s), coordinate information, etc.), (Optional) identification information of the network to which the MWAB is connected / accessed (PLMN ID), (Optional) a list of analytics subsets that are requested (indicates the output information desired to be provided from among the information provided as the output of analytics. If this list is not included, it can be interpreted that all output information is desired to be provided.)

[0393] - Analytics target period: the time period over which the statistics or predictions are requested

[0394] In addition to the information described above, the above message may contain various information as defined in section 6.1.3 of TS 23.288 v18.6.0.

[0395] NWDAF, upon receiving such messages, may collect information / data for analytics purposes.

[0396] NWDAF may collect the information / data in Table 3 and / or Table 4. In addition to this information / data, NWDAF may collect various information / data from various entities (e.g., UE, NF, AF, etc.) to obtain analytics (e.g., Session Management Experience via Mobile RAN Analytics). Alternatively, NWDAF may utilize other analytics information to obtain analytics (e.g., Session Management Experience via Mobile RAN Analytics).

[0397] Table 3 provides examples of data collected by NWDAF.

[0398] InformationSourceDescriptionUE IDSMFSUPI (This information may or may not be collected by the NWDAF. For example, if the NWDAF does not collect this information, the NWDAF may be collecting data per DNN and / or S-NSSAI)SM experience for PDU Session via Mobile RAN.> DNNSMFDNN for the PDU Session that SMF collects Data related to SM experience via Mobile RAN.> S-NSSAISMFS-NSSAI for the PDU Session that SMF collects Data related to SM experience via Mobile RAN.> Start time of data collectionSMFStart time of data collection.> End time of data collectionSMFEnd time of data collection.> UE-requested SM operation (1..max)SMFInformation on the UE-requested SM operation for PDU Session during the collection period.> Type of SM operationSMFThe type of SM operation (e.g. PDU Session Establishment, PDU Session Modification, etc.).>> Result of SM operationSMFResult of SM operation, ie success or fail.>> SM NAS Timer valueSMFTimer value used for SM operation (egT3591)>> Elapsed time related information (1..5)SMFElapsed time related information per try (round) for the SM operation>>> Number of try (round) (NOTE 1)SMFNumber of try (round) for the SM operation, i.e. 1, 2, ..., 5>>> Timestamp of received first SM NAS messageSMFA time stamp when SMF receives the first SM NAS message from UE at this try (round) for the SM operation.>>> UE location related to received first SM NAS messageSMF or AMFUE location when SMF receives the first SM NAS message from UE at this try (round) for the SM operation (Cell ID and / or TAI that the UE is accessing / connecting).>>> MWAB location related to received first SM NAS messageSMF or AMFFor MWAB serving the UE, MWAB location or MWAB-UE location when SMF receives the first SM NAS message from UE at this try (round) for the SM operation (Cell ID and / or TAI that the MWAB-UE is accessing / connecting, and / or geographical location information that the MWAB locates).>>> Timestamp of transmitted SM NAS message(NOTE 2)SMFA time stamp when SMF sends the SM NAS message to UE at this try (round) for the SM operation.>>> Timestamp of received second SM NAS message(NOTE 2)SMFA time stamp when SMF receives the second SM NAS message from UE at this try (round) for the SM operation.>>> UE location related to received second SM NAS message(NOTE 3)SMF or AMFUE location when SMF receives the second SM NAS message from UE at this try (round) for the SM operation (Cell ID and / or TAI that the UE is accessing).>>> MWAB location related to received second SM NAS message(NOTE 3)SMF or AMFFor MWAB serving the UE, MWAB location or MWAB-UE location when SMF receives the second SM NAS message from UE at this try (round) for the SM operation (Cell ID and / or TAI that the MWAB-UE is accessing / connecting, and / or geographical location information that the MWAB locates).> SMF-requested SM operation (1..max)SMFInformation on the SMF-requested SM operation for PDU Session during the collection period.>> Type of SM operationSMFThe type of SM operation (e.g. PDU Session Modification, etc.).>> Result of SM operationSMFResult of SM operation, i.e. success or fail.>> Elapsed time related information (1..5)SMFElapsed time related information per try (round) for the SM operation>>> Number of try (round)SMFNumber of try (round) for the SM operation, i.e. 1, 2, ..., 5>>> Timestamp of transmitted SM NAS messageSMFA time stamp when SMF sends the SM NAS message to UE at this try (round) for the SM operation.>>> Timestamp of received SM NAS message(NOTE 2)SMFA time stamp when SMF receives the SM NAS message from UE at this try (round) for the SM operation.>>> UE location related to received SM NAS message(NOTE 3)SMF or AMFUE location when SMF receives the SM NAS message from UE at this try (round) for the SM operation.>>> MWAB location related to received SM NAS message(NOTE 3)SMF or AMFFor MWAB serving the UE, MWAB location or MWAB-UE location when SMF receives the SM NAS message from UE at this try (round) for the SM operation (Cell ID and / or TAI that the MWAB-UE is accessing / connecting, and / or geographical location information that the MWAB locates).> Transmission / Propagation time between SMF and UE(NOTE 4)SMFTime / Delay elapsed for transmission / propagation of SM NAS message between SMF and UENOTE 1: Number of try (round) is counted and incremented from SMF perspective. Number of tries (round) is 1 when the SMF first receives an SM NAS message from the UE for the given SM operation, and may be increased by 1 each time the first SM NAS message is received thereafter. NOTE 2: If there is no SM NAS message transmitted by the SMF to or received from the UE, this information / data may not be provided or may be provided by setting it to a value indicating that it is not present / invalid (e.g., NULL value, 0, etc.). NOTE 3: If there is no SM NAS message received by the SMF from the UE, this information / data may not be provided or may be provided by setting it to a value indicating that it is not present / invalid (e.g., NULL value, 0, etc.). NOTE 4: The time required for transmission of SM NAS messages between the SMF and the UE may be taken into account to calculate the time taken for an SM operation to be completed (successful or failed).The time may be measured, evaluated, or a value set in the SMF.

[0399] Table 4 shows examples of data collected by NWDAF.

[0400] InformationSourceDescriptionTime elapsed performed for establishment of Backhaul PDU SessionOAM or RANTime elapsed performed for establishment of Backhaul PDU Session, per timeslot, per location, per S-NSSAI, and per DNN.(NOTE 1) (NOTE 2) (NOTE 3) (NOTE 4) (NOTE 5) (NOTE 6)Time elapsed performed for modification of Backhaul PDU SessionOAM or RANTime elapsed performed for modification of Backhaul PDU Session, per timeslot, per location, per S-NSSAI, and per DNN.(NOTE 1) (NOTE 2) (NOTE 3) (NOTE 4) (NOTE 5) (NOTE 6)NOTE 1: All of the per may apply, or only some of them may apply.NOTE 2: In per location, the location may be the location of the MWAB or the location of the MWAB-UE. This can be expressed as the serving Cell ID of the MWAB-UE, the serving TAI of the MWAB-UE, the serving RAN node ID of the MWAB-UE, the coordinate information of the MWAB (or MWAB-UE), the serving PLMN ID of the MWAB-UE, etc. NOTE 3: The required time can be measured / inferred by the MWAB and provided to OAM or MWDAF. The required time can also be the time calculated as an average. NOTE 4: The S-NSSAI can be the S-NSSAI related to the BH PDU session of the MWAB, or the S-NSSAI related to the PDU session of the UE served through the MWAB.There may be a mapping between the S-NSSAI associated with the PDU session of the UE and the S-NSSAI associated with the BH PDU session of the MWAB that services it. NOTE 5: The DNN may be a DNN associated with the BH PDU session of the MWAB, or may be a DNN associated with the PDU session of the UE that is serviced through the MWAB. There may be a mapping between the DNN associated with the PDU session of the UE and the DNN associated with the BH PDU session of the MWAB that services it. NOTE 6: The elapsed time may be expressed in various units (e.g., msec, sec, min, etc.).

[0401] Tables 5 and 6 may be analytics that NWDAF can expose (e.g., Session Management Experience via Mobile RAN Analytics).

[0402] Table 5 may be an example of statistics output / information.

[0403] Table 6 may be an example of prediction output / information.

[0404] In addition to this information / data, NWDAF can derive and expose various outputs / information related to analytics.

[0405] InformationDescriptionList of SM Experience via Mobile RAN Analytics (1..max)> DNN(NOTE 1)DNN for PDU Session of UE.> S-NSSAI(NOTE 1)S-NSSAI for PDU Session of UE.> Area of ​​Interest(NOTE 1)Area of ​​interest information (or location information) related to the location of the UE receiving service via MWAB. For example, it can be expressed as Cell ID(s), TAI(s), RAN node ID(s), coordinate information, etc.> Area of ​​Interest for MWAB(NOTE 1)Area of ​​interest information (or location information) related to the location of MWAB or the location of MWAB-UE. This can be expressed as the serving Cell ID of MWAB-UE, serving TAI of MWAB-UE, serving RAN node ID of MWAB-UE, coordinate information of MWAB (or MWAB-UE), serving PLMN ID of MWAB-UE, etc.> Elapsed time for successful SM operation (1..Max)>> Type of SM operationThe type of successfully completed SM operation (eg PDU Session Establishment, UE-requested PDU Session Modification, SMF-requested PDU Session Modification, etc.).>> Time elapsed for SM operationTime elapsed for successfully completed SM operation.> Information on failed SM operation (1..Max)(NOTE 1)>> Type of SM operationThe type of failed SM operation (egPDU Session Establishment, UE-requested PDU Session Modification, SMF-requested PDU Session Modification, etc.).>> Number of failures for the SM operation.> Recommended SM related timer for UE(NOTE 1)Recommended SM related timer value for UE. (NOTE 2)> Recommended SM related timer for SMF(NOTE 1)Recommended SM related timer value for SMF. (NOTE 2)NOTE 1: This information element is an analytics subset available in the 'Requested Analytics Subset List'.NOTE 2: It can be expressed in units of seconds, but is not limited to this and can be expressed in various units.

[0406] InformationDescriptionList of SM Experience via Mobile RAN Analytics (1..max)> DNN(NOTE 1)DNN for PDU Session of UE.> S-NSSAI(NOTE 1)S-NSSAI for PDU Session of UE.> Area of ​​Interest(NOTE 1)Area of ​​interest information (or location information) related to the location of the UE receiving service via MWAB. For example, it can be expressed as Cell ID(s), TAI(s), RAN node ID(s), coordinate information, etc.> Area of ​​Interest for MWAB(NOTE 1)Area of ​​interest information (or location information) related to the location of MWAB or the location of MWAB-UE. This can be expressed as the serving Cell ID of MWAB-UE, serving TAI of MWAB-UE, serving RAN node ID of MWAB-UE, coordinate information of MWAB (or MWAB-UE), serving PLMN ID of MWAB-UE, etc.> Elapsed time for successful SM operation (1..Max)>> Type of SM operationThe type of successfully completed SM operation (eg PDU Session Establishment, UE-requested PDU Session Modification, SMF-requested PDU Session Modification, etc.).>> Time elapsed for SM operationTime elapsed for successfully completed SM operation.> Information on failed SM operation (1..Max)(NOTE 1)>> Type of SM operationThe type of failed SM operation (egPDU Session Establishment, UE-requested PDU Session Modification, SMF-requested PDU Session Modification, etc.).>> Number of failures for the SM operation.> Recommended SM related timer for UE. (NOTE 1) Recommended SM related timer value for UE. (NOTE 2)> Recommended SM related timer for SMF. (NOTE 1) Recommended SM related timer value for SMF. (NOTE 2)> Confidence of the prediction.NOTE 1: This information element is an analytics subset available in the 'Requested Analytics Subset List'.NOTE 2: It can be expressed in units of seconds, but is not limited to this and can be expressed in various units.

[0407] Upon request, a service consumer (NF) (e.g., SMF, AMF, PCF, etc.) can obtain analytics (e.g., Session Management Experience via Mobile RAN Analytics) from the NWDAF. Based on this, steps (A), (B), and (C) described below can be performed. For this purpose, not only analytics (e.g., Session Management Experience via Mobile RAN Analytics) but also other analytics (see TS 23.288 v18.6.0) and various other information can be utilized.

[0408] (A) An SMF may perform one or more of the following actions:

[0409] - The SMF can set / determine / change / adjust the SM-related timer(s) to be used by the UE receiving the service through MWAB. Based on this, the SMF can then start the timer(s) when the relevant procedure is performed.

[0410] - SMF can set / determine / change / adjust SM-related timer(s) to be used by UEs receiving services through MWAB and provide them to UEs.

[0411] (B) AMF may perform one or more of the following actions:

[0412] - AMF can set / determine / change / adjust SM related timer(s) to be used by SMF for UEs served through MWAB and provide them to SMF.

[0413] - AMF can set / determine / change / adjust SM related timer(s) to be used by UE receiving service through MWAB and provide them to UE.

[0414] - AMF sets / determines / changes / adjusts SM related timer(s) to be used by UEs receiving services through MWAB and provides them to SMF, which in turn can provide them to UEs.

[0415] (C) PCF may perform one or more of the following actions:

[0416] - PCF can set / determine / change / adjust SM related timer(s) to be used by SMF for UEs served through MWAB and provide them to SMF.

[0417] - PCF sets / determines / changes / adjusts SM related timer(s) to be used by UEs receiving services through MWAB and provides them to SMF, which then provides them to UEs.

[0418] - PCF sets / determines / changes / adjusts SM related timer(s) to be used by UEs receiving services through MWAB and provides them to AMF, which can then provide them to UEs.

[0419] - PCF can set / determine / change / adjust SM related timer(s) to be used by UE receiving service through MWAB and provide them to UE.

[0420] The setting / determination / change / adjustment of the SM-related timer(s) described above may be applied to one or more of the following units: i to v. If applied to multiple units, it may be applied to combinations of units. However, the setting / determination / change / adjustment of the SM-related timer(s) is not limited to the following units or combinations of units, and may be applied to various units:

[0421] i) UE unit or UE group (group of UEs) unit

[0422] ii) DNN Unit: This may be a DNN related to the PDU session of the UE, a DNN of a BH PDU session to support the PDU session of the UE, or a combination of these two pieces of information.

[0423] iii) S-NSSAI unit: This may be the S-NSSAI related to the PDU session of the UE, the S-NSSAI of the BH PDU session to support the PDU session of the UE, or a combination of these two pieces of information.

[0424] iv) Specific region: This can be expressed as PLMN ID, Cell ID(s), TAI(s), geographical location, etc. This can be region information related to the location of the UE, region information related to the location of the MWAB (or MWAB-UE), or a combination of these two.

[0425] v) SMF unit: SMF unit serving the UE

[0426] When a service consumer (NF) (e.g., SMF, AMF, PCF, etc.) provides the aforementioned SM-related timer(s) to the UE, the service consumer (NF) (e.g., SMF, AMF, PCF, etc.) may also provide information about the units to which they apply. This information about the units may be explicit, implicit, implicit, or in a combinational form.

[0427] When the AMF (or PCF) provides the SM-related timer(s) to the SMF as described above, the AMF (or PCF) may also provide information about the units to which they apply. This information about the units may be explicit, implicit, implicit, or a combination thereof.

[0428] 1. Example 1-1

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

[0430] Figures 14 and 15 show examples of flowcharts according to the first embodiment of the present specification.

[0431] Based on analytics provided by NWDAF (e.g., Session Management Experience via Mobile RAN Analytics), SMF can set / determine / change / adjust values ​​of SM-related timers for UEs receiving services via MWAB.

[0432] For detailed message content and operation details in the steps below, please refer to the above content and TS 23.288 v18.6.0.

[0433] 1) Step 1

[0434] SMF may send a request or subscription message to NWDAF to request analytics (e.g., Session Management Experience via Mobile RAN Analytics).

[0435] For example, the request from the above SMF may be because the SMF needs to serve a UE that is being served via MWAB.

[0436] For example, the above SMF request may be because a UE receiving service through MWAB has requested establishment of a PDU session.

[0437] For example, the request from the SMF may be because the SMF has completed establishing a PDU session for a UE being served via MWAB.

[0438] For example, the request of the above SMF can be performed based on local configuration, operator policy, etc.

[0439] The above SMF request may be performed based on various conditions other than the reasons mentioned above.

[0440] 2) Step 2

[0441] If necessary, to collect analytics-related data (e.g., Session Management Experience via Mobile RAN Analytics), the NWDAF may send a subscription message to the SMF requesting the necessary data.

[0442] 3) Step 3

[0443] SMF may provide collected data to NWDAF.

[0444] 4) Step 4

[0445] If necessary, to collect analytics-related data (e.g., Session Management Experience via Mobile RAN Analytics), the NWDAF may send a subscription message to the AMF requesting the necessary data.

[0446] 5) Step 5

[0447] AMF may provide collected data to NWDAF.

[0448] 6) Step 6

[0449] If required, NWDAF can collect analytics-related data from OAM (e.g., Session Management Experience via Mobile RAN Analytics).

[0450] 7) Step 7

[0451] NWDAF can obtain requested analytics.

[0452] For example, NWDAF can determine (or derive) analytics requested by SMF (e.g., Session Management Experience via Mobile RAN Analytics).

[0453] 8) Step 8

[0454] NWDAF can provide analytics (e.g., Session Management Experience via Mobile RAN Analytics) to SMF.

[0455] 9) Step 9

[0456] The SMF can set / determine / change / adjust the SM-related timer(s) to be used for the UE receiving the service via MWAB. The SMF can then use the SM-related timer(s) when performing PDU session-related procedures. Based on this, the SMF can then start the timer(s) when performing the related procedures.

[0457] The SMF can set / determine / modify / adjust SM-related timer(s) to be used by the UE receiving the service via MWAB. The SMF can provide the timer(s) to the UE. Thereafter, the UE can use the received SM-related timer(s) when performing PDU session-related procedures.

[0458] For example, the aforementioned SM related timer(s) can be provided to the UE by the SMF triggering an SM procedure (e.g., PDU Session Modification procedure, a newly defined procedure).

[0459] For example, if an SM procedure is in progress, the aforementioned SM related timer(s) may be provided to the UE as part of that procedure.

[0460] For example, if a subsequent SM procedure is performed, the aforementioned SM-related timer(s) may be provided to the UE through that procedure.

[0461] 10a) step 10a

[0462] SMF may provide collected data to NWDAF.

[0463] For example, such provisioning may be performed as changes in data occur.

[0464] For example, these offers may be made on a data provision cycle.

[0465] Such provision may be made for other reasons.

[0466] 10b) step 10b

[0467] AMF may provide collected data to NWDAF.

[0468] For example, such provisioning may be performed as changes in data occur.

[0469] For example, these offers may be made on a data provision cycle.

[0470] Such provision may be made for other reasons.

[0471] 10c) step 10c

[0472] OAM may provide the collected data to NWDAF.

[0473] For example, such provisioning may be performed as changes in data occur.

[0474] For example, these offers may be made on a data provision cycle.

[0475] Such provision may be made for other reasons.

[0476] 11) Step 11

[0477] NWDAF can get new analytics.

[0478] For example, NWDAF can determine (or derive) new analytics (e.g., Session Management Experience via Mobile RAN Analytics).

[0479] New analytics may be based on information received by NWDAF in steps 10a through 10c.

[0480] 12) Step 12

[0481] NWDAF can provide SMF with new analytics (e.g., Session Management Experience via Mobile RAN Analytics).

[0482] 13) Step 13

[0483] The contents of step 9 may be applied.

[0484] If the UE is no longer served through MWAB in the future, the UE and SMF may use the conventional SM-related timer values ​​instead of the aforementioned SM-related timer values.

[0485] 2. Example 1-2

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

[0487] Figures 16 and 17 show examples of flowcharts according to the first and second embodiments of the present specification.

[0488] Based on the analytics provided by NWDAF (e.g., Session Management Experience via Mobile RAN Analytics), AMF can set / determine / change / adjust SM related timer values ​​for UEs served via MWAB.

[0489] For detailed message content and operation details in the steps below, please refer to the above content and TS 23.288 v18.6.0.

[0490] 1) Step 1

[0491] AMF may send a request or subscription message to NWDAF to request analytics (e.g., Session Management Experience via Mobile RAN Analytics).

[0492] For example, the request from the above AMF may be due to the need to serve a UE that is serviced via MWAB.

[0493] For example, the above AMF request may be due to a UE receiving service through MWAB requesting registration.

[0494] For example, the above AMF request may be because a UE receiving service through MWAB has completed registration.

[0495] For example, the above AMF request may be because a UE receiving service via MWAB has requested establishment of a PDU session.

[0496] For example, the above AMF request may be because the UE receiving the service via MWAB has completed PDU session establishment.

[0497] For example, the above AMF request can be performed based on local configuration, operator policy, etc.

[0498] The above AMF request may be performed based on various conditions other than the reasons mentioned above.

[0499] 2-7) Step 2 to Step 7

[0500] The contents of steps 2 to 7 of FIGS. 14 and 15 can be applied.

[0501] 8) Step 8

[0502] NWDAF can provide analytics (e.g., Session Management Experience via Mobile RAN Analytics) to AMF.

[0503] 9) Step 9

[0504] The AMF can set / determine / change / adjust SM-related timer(s) to be used by the SMF for UEs served through MWAB. The AMF can provide the timer(s) to the SMF (step 9a). Thereafter, the SMF can use the SM-related timer(s) when performing PDU session-related procedures.

[0505] The AMF can set / determine / modify / adjust SM-related timer(s) to be used by the UE receiving the service via MWAB. The AMF can provide the timer(s) to the UE (step 9b). Thereafter, the UE can use the received SM-related timer(s) when performing PDU session-related procedures.

[0506] For example, the aforementioned SM related timer(s) can be provided to the UE by the AMF triggering an MM procedure (e.g., UE Configuration Update procedure, a newly defined procedure).

[0507] For example, if an MM procedure is in progress, the SM related timer(s) described above may be provided to the UE as part of that procedure.

[0508] For example, if a subsequent MM procedure is performed, the aforementioned SM related timer(s) may be provided to the UE through that procedure.

[0509] The AMF may provide the SM-related timer(s) for the UE to use to the SMF, and the SMF may provide these to the UE. Alternatively, the AMF may directly provide the SM-related timer(s) for the UE to use to the UE.

[0510] Steps 9a and 9b may be performed concurrently. Step 9b may be performed prior to step 9a.

[0511] 10a-10c) Step 10a to Step 10c

[0512] The contents of steps 10a to 10c of FIGS. 14 and 15 can be applied.

[0513] 11) Step 11

[0514] The contents of step 11 of FIG. 14 and FIG. 15 can be applied.

[0515] 12) Step 12

[0516] NWDAF can provide new analytics to AMF (e.g., Session Management Experience via Mobile RAN Analytics).

[0517] 13) Step 13

[0518] The contents of step 9 may be applied.

[0519] If the UE is no longer served through MWAB in the future, the UE and SMF may use the conventional SM-related timer values ​​instead of the aforementioned SM-related timer values.

[0520] II. Second embodiment: Setting / determining / changing / adjusting MM-related timer values ​​for UEs receiving services via MWAB using NWDAF analytics.

[0521] UEs receiving services via MWAB can perform 5G CN and NAS operations via the underlay network. In this case, adjustments to MM-related timers may be required.

[0522] Setting / determining / changing / adjusting the values ​​of MM related timers for a UE receiving service via MWAB may mean using the conventional MM related timer(s) but with different values.

[0523] Alternatively, setting / determining / changing / adjusting the values ​​of MM related timers for a UE served via MWAB may mean defining (newly) the timer(s) separately and using them.

[0524] When a UE receives services via MWAB, a new analytics model may be defined to determine, set, or adjust the values ​​of timers used when performing MM-related procedures for the UE. This analytics model may be called "Mobility Management Experience via Mobile RAN Analytics." However, this designation is merely an example, and analytics models may be defined under other names.

[0525] A service consumer (NF) (e.g., AMF, PCF, etc.) can request analytics (e.g., Mobility Management Experience via Mobile RAN Analytics) from the NWDAF. A typical reason why a service consumer (NF) might request analytics from the NWDAF is because the serving UE receives services from the network via the MWAB. However, a service consumer (NF) may request such analytics from the NWDAF for various other reasons / conditions. In this regard, reference may be made to the contents of the aforementioned first and second embodiments.

[0526] A service consumer (NF) can send a message (e.g., a subscription message, a request message) to NWDAF to request analytics (e.g., Mobility Management Experience via Mobile RAN Analytics). The message may include at least one of the following information:

[0527] - Analytics ID = "Mobility Management Experience via Mobile RAN".

[0528] - Target of Analytics Reporting: a single UE (SUPI) or a list of UEs (a list of SUPIs) or group of UEs (ie a list of Internal Group Ids) or any UE.

[0529] - Analytics Filter Information: The following information may be included / provided explicitly, implicitly, implicitly, or in combination. eg, (Optional) area of ​​interest (this is area of ​​interest information (or location information) related to the location of the UE receiving service through the MWAB. For example, it may be expressed as Cell ID(s), TAI(s), RAN node ID(s), coordinate information, etc.), (Optional) area of ​​interest for MWAB (this is area of ​​interest information (or location information) related to the location of the MWAB (or MWAB-UE). For example, it may be expressed as Cell ID(s), TAI(s), RAN node ID(s), coordinate information, etc.), (Optional) identification information of the network to which the MWAB is connected / accessed (PLMN ID), (Optional) a list of analytics subsets that are requested (this indicates the desired output information among the information provided as the output of Analytics. If this list is not included, it may be interpreted that all output information is desired to be provided.)

[0530] - Analytics target period: the time period over which the statistics or predictions are requested

[0531] In addition to the information described above, the above message may contain various information as defined in section 6.1.3 of TS 23.288 v18.6.0.

[0532] NWDAF, upon receiving such messages, may collect information / data for analytics purposes.

[0533] NWDAF can collect the information / data listed in Table 7. In addition to this information / data, NWDAF can collect various information / data from various entities (e.g., UE, NF, AF, etc.) to obtain analytics (e.g., Mobility Management Experience via Mobile RAN Analytics). Alternatively, NWDAF can utilize other analytics information to obtain analytics (e.g., Mobility Management Experience via Mobile RAN Analytics).

[0534] Table 7 provides examples of data collected by NWDAF.

[0535] InformationSourceDescriptionUE IDAMFSUPI (This information may or may not be collected by NWDAF. For example, if NWDAF does not collect this information, NWDAF may be collecting location-level data.)MM experience via Mobile RANANAMFData related to MM experience via Mobile RAN.> Start time of data collectionAMFStart time of data collection.> End time of data collectionAMFEnd time of data collection.> UE-initiated MM operation (1..max)AMFInformation on the UE-initiated MM operation during the collection period.>> Type of MM operationAMFThe type of MM operation (e.g. Initial Registration, Registration Update, Service Request, etc.).>> Result of MM operationAMFResult of MM operation, i.e. success or fail.>> Elapsed time related information (1..5)AMFElapsed time related information per try (round) for the MM operation>>> Number of try (round) (NOTE 1)AMFNumber of try (round) for the MM operation, ie 1, 2, ..., 5>>> Timestamp of received first MM NAS messageAMFA time stamp when AMF receives the first MM NAS message from UE at this try (round) for the MM operation.>>> UE location related to received first MM NAS messageAMFUE location when AMF receives the first MM NAS message from UE at this try (round) for the MM operation (Cell ID and / or TAI that the UE is accessing / connecting).>>> MWAB location related to received first MM NAS messageAMFFor MWAB serving the UE, MWAB location or MWAB-UE location when AMF receives the first MM NAS message from UE at this try (round) for the MM operation (Cell ID and / or TAI that the MWAB-UE is accessing / connecting, and / or geographical location information that the MWAB locates).>>> Timestamp of transmitted MM NAS message(NOTE 2)AMFA time stamp when AMF sends the MM NAS message to UE at this try (round) for the MM operation.>>> Timestamp of received second MM NAS message(NOTE 2)AMFA time stamp when AMF receives the second MM NAS message from UE at this try (round) for the MM operation.>>> UE location related to received second MM NAS message(NOTE 3)AMFUE location when AMF receives the second MM NAS message from UE at this try (round) for the MM operation (Cell ID and / or TAI that the UE is accessing).>>> MWAB location related to received second MM NAS message(NOTE 3)AMFFor MWAB serving the UE, MWAB location or MWAB-UE location when AMF receives the second MM NAS message from UE at this try (round) for the MM operation (Cell ID and / or TAI that the MWAB-UE is accessing / connecting, and / or geographical location information that the MWAB locates).> AMF-initiated MM operation (1..max)AMFInformation on the AMF-initiated MM operation during the collection period.>> Type of MM operationAMFThe type of MM operation (e.g. UE Configuration Update, etc.).>> Result of MM operationAMFResult of MM operation, i.e.success or fail.>> MM NAS Timer valueAMFTimer value used for MM operation (e.g. T3555)>> Elapsed time related information (1..5)AMFElapsed time related information per try (round) for the MM operation>>> Number of try (round)AMFNumber of try (round) for the MM operation, i.e. 1, 2, ..., 5>>> Timestamp of transmitted MM NAS messageAMFA time stamp when AMF sends the MM NAS message to UE at this try (round) for the MM operation.>>> Timestamp of received MM NAS message(NOTE 2)AMFA time stamp when AMF receives the MM NAS message from UE at this try (round) for the MM operation.>>> UE location related to received MM NAS message(NOTE 3)AMFUE location when AMF receives the MM NAS message from UE at this try (round) for the MM operation.>>> MWAB location related to received MM NAS message(NOTE 3)AMFFor MWAB serving the UE, MWAB location or MWAB-UE location when AMF receives the MM NAS message from UE at this try (round) for the MM operation (Cell ID and / or TAI that the MWAB-UE is accessing / connecting, and / or geographical location information that the MWAB locates).> Transmission / Propagation time between AMF and UE(NOTE 4)AMFTime / Delay elapsed for transmission / propagation of MM NAS message between AMF and UENOTE 1: Number of try (round) is counted and incremented from AMF perspective. Number of tries (round) is 1 when the AMF first receives an MM NAS message from the UE for the MM operation, and may be increased by 1 each time the first MM NAS message is received thereafter. NOTE 2: If there is no MM NAS message transmitted by the AMF to or from the UE, this information / data may not be provided or may be provided by setting it to a value indicating that it is not present / invalid (e.g., NULL value, 0, etc.). NOTE 3: If there is no MM NAS message received by the AMF from the UE, this information / data may not be provided or may be provided by setting it to a value indicating that it is not present / invalid (e.g., NULL value, 0, etc.). NOTE 4: The time required for transmission of MM NAS messages between the AMF and the UE may be taken into account to calculate the time required for the MM operation to be completed (successful or failed).The time may be measured, evaluated or a value set in the AMF.

[0536] Tables 8 and 9 may be analytics that NWDAF can expose (e.g., Mobility Management Experience via Mobile RAN Analytics).

[0537] Table 8 may be an example of statistics output / information.

[0538] Table 9 may be an example of prediction output / information.

[0539] In addition to this information / data, NWDAF can derive and expose various outputs / information related to analytics.

[0540] InformationDescriptionList of MM Experience via Mobile RAN Analytics (1..max) > Area of ​​Interest(NOTE 1) Area of ​​interest information (or location information) related to the location of the UE receiving service via MWAB. For example, it can be expressed as Cell ID(s), TAI(s), RAN node ID(s), coordinate information, etc. > Area of ​​Interest for MWAB(NOTE 1) Area of ​​interest information (or location information) related to the location of MWAB or the location of MWAB-UE. This can be expressed as the serving Cell ID of MWAB-UE, serving TAI of MWAB-UE, serving RAN node ID of MWAB-UE, coordinate information of MWAB (or MWAB-UE), serving PLMN ID of MWAB-UE, etc.> Elapsed time for successful MM operation (1..Max)>> Type of MM operationThe type of successfully completed MM operation (eg Initial Registration, Registration Update, Service Request, UE Configuration Update, etc.).>> Time elapsed for MM operationTime elapsed for successfully completed MM operation.> Information on failed MM operation (1..Max)(NOTE 1)>> Type of MM operationThe type of failed MM operation (eg Initial Registration, Registration Update, Service Request, UE Configuration Update, etc.).>> Number of failures for the MM operation.> Recommended MM related timer for UE(NOTE 1)Recommended MM related timer value for UE. (NOTE 2)> Recommended MM related timer for AMF(NOTE 1)Recommended MM related timer value for SMF. (NOTE 2)NOTE 1: This information element is an analytics subset available in the 'Requested Analytics Subset List'.NOTE 2: It can be expressed in seconds, but is not limited to this and can be expressed in various units.

[0541] InformationDescriptionList of MM Experience via Mobile RAN Analytics (1..max) > Area of ​​Interest(NOTE 1) Area of ​​interest information (or location information) related to the location of the UE receiving service via MWAB. For example, it can be expressed as Cell ID(s), TAI(s), RAN node ID(s), coordinate information, etc. > Area of ​​Interest for MWAB(NOTE 1) Area of ​​interest information (or location information) related to the location of MWAB or the location of MWAB-UE. This can be expressed as the serving Cell ID of MWAB-UE, serving TAI of MWAB-UE, serving RAN node ID of MWAB-UE, coordinate information of MWAB (or MWAB-UE), serving PLMN ID of MWAB-UE, etc.> Elapsed time for successful MM operation (1..Max)>> Type of MM operationThe type of successfully completed MM operation (eg Initial Registration, Registration Update, Service Request, UE Configuration Update, etc.).>> Time elapsed for MM operationTime elapsed for successfully completed MM operation.> Information on failed MM operation (1..Max)(NOTE 1)>> Type of MM operationThe type of failed MM operation (eg Initial Registration, Registration Update, Service Request, UE Configuration Update, etc.).>> Number of failures for the MM operation.> Recommended MM related timer for UE (NOTE 1)Recommended MM related timer value for UE. (NOTE 2)> Recommended MM related timer for AMF (NOTE 1)Recommended MM related timer value for SMF. (NOTE 2)> Confidence of the prediction.NOTE 1: This information element is an analytics subset available in the 'Requested Analytics Subset List'.NOTE 2: It can be expressed in seconds, but is not limited to this and can be expressed in various units.

[0542] Upon request, a service consumer (NF) (e.g., AMF, PCF, etc.) can obtain analytics (e.g., Mobility Management Experience via Mobile RAN Analytics) from the NWDAF. Based on this, steps (a), (b), and (c) described below can be performed. For this purpose, not only analytics (e.g., Mobility Management Experience via Mobile RAN Analytics) but also other analytics (see TS 23.288 v18.6.0) and various other information can be utilized.

[0543] (a) AMF may perform one or more of the following actions:

[0544] - The AMF can set / determine / change / adjust the MM-related timer(s) to be used by the UE receiving the service via MWAB. Based on this, the AMF can then start the timer(s) when the relevant procedure is performed.

[0545] - AMF can set / determine / change / adjust MM related timer(s) to be used by UE receiving service through MWAB and provide them to UE.

[0546] (b) PCF may perform one or more of the following actions:

[0547] - PCF can set / determine / change / adjust MM related timer(s) to be used by AMF for UEs served through MWAB and provide them to AMF.

[0548] - PCF sets / determines / changes / adjusts MM related timer(s) to be used by UEs receiving services through MWAB and provides them to AMF, which then provides them to UE.

[0549] - PCF can set / determine / change / adjust MM related timer(s) to be used by UE receiving service through MWAB and provide them to UE.

[0550] The setting / determination / change / adjustment of the MM-related timer(s) described above may be applied to one or more of the following units i to iii. If applied to multiple units, it may be applied to combinations of units. However, the setting / determination / change / adjustment of the MM-related timer(s) is not limited to the following units or combinations of units, and may be applied to various units:

[0551] i) UE unit or UE group (group of UEs) unit

[0552] ii) Specific area: This can be expressed by PLMN ID, Cell ID(s), TAI(s), geographical location, etc. This can be area information related to the location of the UE, area information related to the location of the MWAB (or MWAB-UE), or a combination of these two.

[0553] iii) AMF unit: AMF unit serving the UE

[0554] When a service consumer (NF) (e.g., AMF, PCF, etc.) provides the UE with the aforementioned MM-related timer(s), the service consumer (NF) (e.g., AMF, PCF, etc.) may also provide information about the units to which they apply. This information about the units may be explicit, implicit, implicit, or in a combinational form.

[0555] When PCF provides the AMF with the aforementioned MM-related timer(s), PCF may also provide information about the units to which they apply. This information about the units may be explicit, implicit, implicit, or a combination thereof.

[0556] III. Third embodiment: Setting / determining / changing / adjusting NAS-related timer values ​​for UE using NWDAF analytics

[0557] The UE can perform NAS procedures via satellite. In this case, the timer value for the NAS procedure needs to be set differently than before. The timer value for the NAS procedure can be set based on NWDAF analytics.

[0558] Depending on the characteristics of the terminal's access network, NAS-related timer values ​​may need to be adjusted. For example, NAS-related timer values ​​may be set differently in the following situations:

[0559] - If the terminal connects via satellite, different NAS-related timer values ​​may need to be set depending on the type of satellite (e.g. LEO, MEO, GEO).

[0560] - When the terminal is connected multi-hop (or directly) via a Relay / mobile base station (e.g., IAB, MBSR, MWAB, Relay UE, etc.), different NAS-related timer values ​​may need to be set depending on the number of hops connected.

[0561] - Even when the terminal is directly connected to the base station, it may be necessary to set values ​​for other NAS-related timers depending on the backhaul network (e.g. satellite) used.

[0562] - When the terminal connects via non-3GPP access, it may be necessary to set the value of the NAS-related timer considering the delay time of non-3GPP access.

[0563] Setting / determining / changing / adjusting the values ​​of NAS-related timers for the UE may mean using the conventional NAS-related timer(s) with different values.

[0564] Alternatively, setting / determining / changing / adjusting the values ​​of NAS-related timers for the UE may mean defining (newly) and using NAS-related timer(s) separately.

[0565] A new analytics model can be defined to determine, set, or adjust the values ​​of timers used when performing NAS-related procedures for a UE (e.g., a UE performing NAS procedures via satellite). This analytics model can be called "NAS Timer Analytics." However, this designation is an example, and analytics models can be defined with other names.

[0566] In this specification, a RAN node may be interpreted as including or corresponding to an AN node (e.g., N3IWF, TNGF, W-IGF, etc.) in non-3GPP access.

[0567] A service consumer (NF) (e.g., AMF, SMF, PCF, etc.) can request analytics (e.g., NAS Timer Analytics) from the NWDAF. A typical reason why a service consumer (NF) might request analytics from the NWDAF is because the serving UE receives services from the network via satellite (or MWAB, etc.). However, the service consumer (NF) may request such analytics from the NWDAF for various other reasons / conditions. In this regard, reference may be made to the contents of the aforementioned embodiments 1-1 and 1-2.

[0568] A service consumer (NF) can send a message (e.g., a subscription message, a request message) to NWDAF to request analytics (e.g., NAS Timer Analytics). The message may include at least one of the following information:

[0569] - Analytics ID = "NAS Timer Analytics".

[0570] - Target of Analytics Reporting: a single UE (SUPI) or a list of UEs (a list of SUPIs) or group of UEs (ie a list of Internal Group Ids) or any UE.

[0571] - Analytics Filter Information: The following information may be included / provided explicitly, implicitly, implicitly, or in combination. eg, (Optional) area of ​​interest (this is area of ​​interest information (or location information) related to the location of the UE. For example, it may be expressed as Cell ID(s), TAI(s), RAN node ID(s), coordinate information, etc.), (Optional) area of ​​interest for RAN node (this is area of ​​interest information (or location information) related to the location of the RAN node to which the UE is connected. For example, it may be expressed as Cell ID(s), TAI(s), RAN node ID(s), coordinate information, etc.), (Optional) identification information (PLMN ID) of the RAN node to which the UE is connected or the network to which the Relay UE is connected / connected, (Optional) a list of analytics subsets that are requested (this indicates the desired output information among the information provided as the output of Analytics. If this list is not included, it may be interpreted that all output information is desired to be provided.)

[0572] - Analytics target period: the time period over which the statistics or predictions are requested

[0573] In addition to the information described above, the above message may contain various information as defined in section 6.1.3 of TS 23.288 v18.6.0.

[0574] NWDAF can collect the information / data listed in Table 10. In addition to this information / data, NWDAF can collect various information / data from various entities (e.g., UE, NF, AF, etc.) to obtain analytics (e.g., NAS Timer Analytics). Alternatively, NWDAF can utilize other analytics information to obtain analytics (e.g., NAS Timer Analytics).

[0575] Table 10 provides examples of data collected by NWDAF.

[0576] InformationSourceDescriptionUE IDAMFSUPI (This information may or may not be collected by NWDAF. For example, if NWDAF does not collect this information, NWDAF may collect location-level data.)MM experienceAMFData related to MM experience. (The sub-information may include all of the information in Table 7. In this case, MWAB in Table 7 can be interpreted as a general RAN replacement.)SM experienceSMF or OAM or RANData related to SM experience. (The sub-information may include all of the information in Tables 3 and 4. In this case, MWAB in Tables 3 and 4 can be interpreted as a general RAN replacement.)Access network typeAMFAccess network type eg 3GPP access, non-3GPP access.RAN node typeAMF or SMF or OAMRAN node type information eg relay node, TN node, NTN node, etc.RAT typeAMF or SMFThe RAT types the UE camps eg NR, NR(LEO), NR(MEO), NR(GEO)Backhaul typeAMF or OAMBackhaul type of the RAN node the UE camps e.g. satellite-LEO, satellite-MEO, satellite-GEO(NOTE 1)NOTE 1: This can be pre-configured in the AMF per RAN node ID or TA. Another way is during the process of creating an interface between the RAN node and the AMF (e.g.NG Setup Request / Response) RAN nodes can provide backhaul type information.

[0577] Tables 11 and 12 may be analytics that NWDAF can expose (e.g., NAS Timer Analytics).

[0578] Table 11 may be an example of statistics output / information.

[0579] Table 12 may be an example of prediction output / information.

[0580] In addition to this information / data, NWDAF can derive and expose various outputs / information related to analytics.

[0581] InformationDescriptionList of MM Experience Analytics (1..max)Data related to MM Experience Analytics (Sub-information can include all of the information in Table 8. In this case, MWAB in Table 8 can be interpreted as a general RAN.)List of SM Experience Analytics (1..max)Data related to SM Experience Analytics (Sub-information can include all of the information in Table 5. In this case, MWAB in Table 5 can be interpreted as a general RAN.)

[0582] InformationDescriptionList of MM Experience Analytics (1..max)Data related to MM Experience Analytics (Sub-information may include all of the information in Table 9. In this case, MWAB in Table 9 may be interpreted as a general RAN.)List of SM Experience Analytics (1..max)Data related to SM Experience Analytics (Sub-information may include all of the information in Table 6. In this case, MWAB in Table 6 may be interpreted as a general RAN.)

[0583] Upon request, a service consumer (NF) (e.g., AMF, SMF, PCF, etc.) can obtain analytics (e.g., NAS Timer statistics) from the NWDAF. Based on this, steps (1), (2), and (3) described below can be performed. For this purpose, not only analytics (e.g., NAS Timer statistics), but also other analytics (see TS 23.288 v18.6.0) and various other information can be utilized.

[0584] (1) AMF may perform one or more of the following actions:

[0585] - The AMF can set / determine / change / adjust the MM-related timer(s) to be used by the UE for the UE. Based on this, the AMF can start the corresponding timer when the relevant procedure (e.g., registration update procedure) is performed. Based on this, the AMF can start the corresponding timer when the relevant procedure is performed. For example, if the AMF expects a registration complete message from the UE based on a registration accept message, the AMF can start the corresponding timer while sending the registration accept message to the UE. When the timer expires, the AMF can resend the registration accept message to the UE.

[0586] - AMF can set / determine / change / adjust MM related timer(s) to be used by UE and provide them to UE.

[0587] - AMF can set / determine / change / adjust SM related timer(s) to be used by SMF for UE and provide them to SMF.

[0588] - AMF can set / determine / change / adjust SM related timer(s) to be used by UE and provide them to UE.

[0589] - AMF sets / determines / changes / adjusts SM related timer(s) to be used by UE and provides them to SMF, which can then provide them to UE.

[0590] (2) SMF can perform one or more of the following actions:

[0591] - The SMF can set / determine / change / adjust the SM-related timer(s) it uses for the UE. Based on this, the SMF can subsequently start the corresponding timer when the related procedure is performed. For example, the SMF can start the SM-related timer when sending the PDU Session Modification command to the UE. When the timer expires, the SMF can retransmit the PDU Session Modification command to the UE.

[0592] - SMF can set / determine / change / adjust SM related timer(s) to be used by UE and provide them to UE.

[0593] (3) PCF can perform one or more of the following actions:

[0594] - PCF can set / determine / change / adjust MM related timer(s) to be used by AMF (or SMF) for UE and provide them to AMF (or SMF).

[0595] - PCF sets / determines / changes / adjusts the timer(s) to be used by UE (e.g., MM related timer(s), SM related timer(s)) and provides them to AMF (or SMF), and then AMF (or SMF) can provide them to UE.

[0596] - PCF can set / determine / change / adjust timer(s) to be used by UE (e.g., MM related timer(s), SM related timer(s)) and provide them to UE.

[0597] The setting / determination / change / adjustment of the above-mentioned timer(s) (e.g., MM-related timer(s), SM-related timer(s)) may be applied to one or more of the following units i to vi. In case of application to multiple units, it may be applied to combinations between the units. However, it is not limited to the following units or combinations between units, and the setting / determination / change / adjustment of the timer(s) (e.g., MM-related timer(s), SM-related timer(s)) may be applied to various units:

[0598] i) UE unit or UE group (group of UEs) unit

[0599] ii) Specific region: This can be expressed by PLMN ID, Cell ID(s), TAI(s), geographical location, etc. This can be region information related to the location of the UE, region information related to the location of the RAN node, or a combination of these two.

[0600] iii) AMF unit: AMF unit serving the UE

[0601] iv) SMF unit: SMF unit serving the UE

[0602] v) DNN Unit: This may be a DNN related to the PDU session of the UE, a DNN of a BH PDU session to support the PDU session of the UE, or a combination of these two pieces of information.

[0603] vi) S-NSSAI unit: This may be the S-NSSAI related to the PDU session of the UE, or the S-NSSAI of the BH PDU session to support the PDU session of the UE, or a combination of these two pieces of information.

[0604] When a service consumer (NF) (e.g., AMF, SMF, PCF, etc.) provides the UE with the aforementioned timer(s) (e.g., MM-related timer(s), SM-related timer(s)), the service consumer (NF) (e.g., AMF, SMF, PCF, etc.) may also provide information about the units to which they are applied. This information about the units may be explicit, implicit, implicit, or in a combined form.

[0605] When the PCF provides the aforementioned timer(s) (e.g., MM-related timer(s), SM-related timer(s)) to the AMF (or SMF), the PCF may also provide information about the units to which they apply. This information about the units may be explicit, implicit, implicit, or a combination thereof.

[0606] 1. Example 3-1

[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, and fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0608] Figures 18 and 19 show examples of flowcharts according to embodiment 3-1 of the present specification.

[0609] Based on the analytics provided by NWDAF (e.g., NAS Timer Analytics), AMF can set / determine / change / adjust NAS-related timer values ​​for UEs connected to the network via satellite.

[0610] For detailed message content and operation details in the steps below, please refer to the above content and TS 23.288 v18.6.0.

[0611] 1) Step 1

[0612] The UE may send a registration request message to the network. The UE may initiate / start a timer configured in connection with the registration request procedure.

[0613] With regard to the registration procedure, the contents of FIGS. 6 and 7 may be applied.

[0614] 2) Step 2

[0615] AMF may send a registration acceptance message to the UE. The UE may stop the timer initiated / started in step 1.

[0616] With regard to the registration procedure, the contents of FIGS. 6 and 7 may be applied.

[0617] 3) Step 3

[0618] AMF may send a request or subscription message to NWDAF to request analytics (e.g., NAS Timer Analytics).

[0619] In this embodiment, the UE may have accessed the network via a satellite. Alternatively, the UE may be in a location where it is likely to access the network via a satellite. Based on this, the AMF may decide to perform the request (or send a join message) to the NWDAF.

[0620] 4) Step 4

[0621] If necessary, to collect analytics-related data (e.g., NAS Timer Analytics), NWDAF may send a subscription message to SMF requesting the necessary data.

[0622] 5) Step 5

[0623] SMF may provide collected data to NWDAF.

[0624] 6) Step 6

[0625] If necessary, to collect analytics-related data (e.g., NAS Timer Analytics), NWDAF may send a subscription message to AMF requesting the necessary data.

[0626] 7) Step 7

[0627] AMF may provide collected data to NWDAF.

[0628] 8) Step 8

[0629] If necessary, NWDAF can collect analytics-related data (e.g., NAS Timer Analytics) from OAM.

[0630] 9) Step 9

[0631] NWDAF can obtain requested analytics.

[0632] For example, NWDAF can determine (or derive) analytics requested by AMF (e.g., NAS Timer Analytics).

[0633] 10) Step 10

[0634] NWDAF can provide analytics (e.g., NAS Timer Analytics) to AMF.

[0635] 11) Step 11

[0636] AMF can set / determine / change / adjust NAS-related timer(s) to be used by UE. AMF can provide the timer(s) to UE. NAS-related timer(s) can be MM-related timer(s) and / or SM-related timer(s).

[0637] For example, the NAS related timer(s) mentioned above can be provided to the UE by the AMF triggering an MM procedure (e.g., UE Configuration Update procedure, a newly defined procedure).

[0638] For example, if an MM procedure is in progress, the NAS related timer(s) described above may be provided to the UE as part of that procedure.

[0639] For example, if a subsequent MM procedure is performed, the aforementioned NAS-related timer(s) may be provided to the UE through that procedure.

[0640] For example, the AMF may provide the SMF with SM-related timer(s) for the UE to use, and the SMF may provide these to the UE.

[0641] If the UE is provided with MM-related timer(s), the UE may use the received MM-related timer(s) when performing MM-related procedures.

[0642] If the UE is provided with SM-related timer(s), the UE may use the received SM-related timer(s) when performing PDU session-related procedures.

[0643] Steps 12 and 13 described below can be performed thereafter for the PDU session establishment procedure.

[0644] Steps 14 and 15 described below can be performed for the registration procedure.

[0645] Steps 16 to 18 described below can be performed thereafter for the PDU session modification procedure.

[0646] 12) Step 12

[0647] With regard to the PDU session establishment procedure, the contents of FIGS. 8 and 9 can be applied.

[0648] A UE can send a PDU Session Establishment Request message to the network to establish a PDU session.

[0649] If the UE has been provided with SM related timer(s) from the AMF in step 11 (e.g., if the UE has been provided with a timer related to a PDU session establishment request / procedure), the UE may initiate / start the corresponding timer.

[0650] If the UE is not provided with a timer related to a PDU session establishment request / procedure, the UE may use / start a timer related to a PDU session establishment request / procedure that has been configured.

[0651] The AMF may transmit a PDU session establishment request message received from the UE to the SMF. At this time, the AMF may set / determine / change / adjust the SM-related timer(s) (timer value) to be used by the SMF for the UE and provide it to the SMF. The AMF may also provide the SM-related timer(s) (timer value) to the SMF using a separate message.

[0652] SMF can use the SM-related timer (timer value) when performing PDU session-related procedures thereafter.

[0653] 13) Step 13

[0654] With regard to the PDU session establishment procedure, the contents of FIGS. 8 and 9 can be applied.

[0655] The SMF may send a PDU Session Establishment Accept message to the UE.

[0656] 14) Step 14

[0657] With regard to the registration procedure, the contents of FIGS. 6 and 7 may be applied.

[0658] The UE can send a registration request message to the network.

[0659] If the UE has been provided with MM related timer(s) from the AMF in step 11 (e.g., specifically, timers related to registration requests / procedures), the UE may initiate / start the corresponding timer(s).

[0660] If the UE is not provided with a timer related to the above registration request / procedure, the UE may use / start the timer related to the registration request / procedure that has been set.

[0661] The registration process for this step may be performed for various reasons.

[0662] For example, the registration procedure of this step may be due to the movement of the UE.

[0663] For example, the registration procedure of this step may be performed periodically.

[0664] For example, the registration procedure of this step may be due to a change in UE capability.

[0665] 15) Step 15

[0666] With regard to the registration procedure, the contents of FIGS. 6 and 7 may be applied.

[0667] The AMF may send a registration acceptance message to the UE. The UE may stop the timer initiated / started in step 14.

[0668] 16) Step 16

[0669] A UE may send a PDU Session Modification Request message to the network to modify a PDU session.

[0670] If the UE has been provided with SM related timer(s) from AMF in step 11 (e.g., if the UE has been provided with a timer related to a PDU session modification request / procedure), the UE may initiate / start the corresponding timer.

[0671] If the UE is not provided with a timer related to a PDU session modification request / procedure, the UE may use / start a timer related to a PDU session modification request / procedure that has been configured.

[0672] 17) Step 17

[0673] The SMF can send a PDU Session Modification Command message to the UE.

[0674] If the SMF has been provided with SM-related timer(s) from the AMF in step 12 above (e.g., if it has been provided with a timer related to a PDU session modification command / procedure), the SMF may initiate / start the timer.

[0675] If the SMF is not provided with a timer related to the above PDU session modification command / procedure, the SMF may use / start a timer related to the configured PDU session modification command / procedure.

[0676] The UE may stop the timer initiated / started in step 16.

[0677] 18) Step 18

[0678] The UE may send a PDU Session Modification Complete message to the network.

[0679] SMF can stop the timer started / initiated in step 17.

[0680] 19) Step 19a

[0681] SMF may provide collected data to NWDAF.

[0682] For example, such provisioning may be performed as changes in data occur.

[0683] For example, these offers may be made on a data provision cycle.

[0684] Such provision may be made for other reasons.

[0685] 19b) step 19b

[0686] AMF may provide collected data to NWDAF.

[0687] For example, such provisioning may be performed as changes in data occur.

[0688] For example, these offers may be made on a data provision cycle.

[0689] Such provision may be made for other reasons.

[0690] 19c) step 19c

[0691] OAM may provide the collected data to NWDAF.

[0692] For example, such provisioning may be performed as changes in data occur.

[0693] For example, these offers may be made on a data provision cycle.

[0694] Such provision may be made for other reasons.

[0695] 20) Step 20

[0696] NWDAF can get new analytics.

[0697] For example, NWDAF can determine (or derive) new analytics.

[0698] The new analytics may be based on information received by NWDAF in steps 19a to 19c.

[0699] 21) Step 21

[0700] NWDAF can provide new analytics to AMF.

[0701] 22) Step 22

[0702] Step 11 may apply.

[0703] 23) Step 23

[0704] The AMF may set / determine / change / adjust the SM-related timer(s) to be used by the SMF for the above UE and provide them to the SMF. The SMF may then use the above SM-related timer values ​​in subsequent PDU session-related procedures.

[0705] According to the disclosure of this specification, when a UE receives service via a mobile base station (or, MWAB, satellite), timers (e.g., MM-related timers, SM-related timers, NAS-related timers) can be set based on NWDAF analytics. This prevents unnecessary retries of certain procedures for the UE (e.g., PDU session-related procedures). Furthermore, a UE seeking emergency services can avoid unnecessary reselection of another domain / network. Therefore, according to the disclosure of this specification, seamless service can be provided to the UE.

[0706] The following actions can be performed:

[0707] - NF (service consumer) (e.g., SMF, AMF, PCF, etc.) can send request / subscription messages to obtain analytics (e.g., Session Management Experience via Mobile RAN Analytics) from NWDAF.

[0708] - NWDAF can collect data to obtain (or derive) analytics (e.g., Session Management Experience via Mobile RAN Analytics). To do this, it can request data from NFs (e.g., SMF, AMF, etc.) and OAMs that provide the necessary data.

[0709] - NWDAF can obtain analytics (e.g., Session Management Experience via Mobile RAN Analytics) and provide them to the NF.

[0710] - NF (service consumer) can use analytics provided from NWDAF to set / determine / change / adjust values ​​of timers (e.g., MM-related timers, SM-related timers, NAS-related timers) for UEs receiving services through MWAB (or UEs accessed via satellite).

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

[0712] Figure 20 illustrates the NF procedure for the disclosure of this specification.

[0713] 1. NF (Network Function) can request analytics for NAS (Non-Access-Stratum) procedures from NWDAF (NetWork Data Analytics Functions).

[0714] UE (User Equipment) can perform the above NAS procedure via satellite.

[0715] 2. Based on the above request, the NF can receive first analytics from the NWDAF.

[0716] 3. Based on the above first analytics, the NF can determine the value of the NAS-related timer.

[0717] 4. The NF can transmit information about the value of the determined NAS-related timer to the UE.

[0718] The above NF can receive second analytics from the NWDAF.

[0719] Based on the second analytics, the NF can determine a new value for the NAS-related timer.

[0720] The above NF can transmit information about the new value of the determined NAS-related timer to the above UE.

[0721] The above NAS-related timer may be for at least one of a UE, a UE group, a region, an Access and Mobility Management Function (AMF), a Session Management Function (SMF), a Data Network Name (DNN), and a Single Network Slice Selection Assistance Information (S-NSSAI).

[0722] The request may include any one of an ID for analytics, target information for analytics, location-related information of the UE, location-related information of a RAN (Radio Access Network) node, Public Land Mobile Network (PLMN) information of a base station node to which the UE has connected, PLNM information of a relay UE to which the UE has connected, and information on an analytics target period.

[0723] The above NF may be an SMF.

[0724] The above NF can determine the value of the SMF timer to be used.

[0725] The above NAS procedure may be a PDU (Protocol Data Unit) session related procedure.

[0726] The above NF can send a PDU session modification command to the UE.

[0727] Based on the NF sending the PDU session modification command to the UE, the NF can start the SMF timer.

[0728] Based on the expiration of the above SMF timer, the NF may retransmit the PDU session modification command to the UE.

[0729] The above NF may be AMF.

[0730] The above NF can determine the value of the SMF timer to be used by the SMF.

[0731] The above NAS procedure may be a PDU session related procedure.

[0732] The above NF can transmit information about the value of the SMF timer to the above SMF.

[0733] The step of the NF transmitting information about the value of the determined NAS-related timer to the UE may include: the step of the NF transmitting information about the value of the determined NAS-related timer to the UE via an SMF.

[0734] The above NAS procedure may be a registration procedure.

[0735] The above NAS-related timer may be a timer that starts when the UE transmits a registration request.

[0736] The above NF can determine the value of the AMF timer to be used.

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

[0738] Figure 21 illustrates the UE's procedure for disclosure of this specification.

[0739] 1. The UE (User Equipment) can receive information about the value of the NAS timer for the NAS procedure from the NF (Network Function).

[0740] The above NAS procedure can be performed via satellite.

[0741] 2. The UE can transmit a NAS message related to the NAS procedure to the network.

[0742] 3. Based on the UE transmitting the NAS message to the network, the UE can start the NAS timer.

[0743] Based on the expiration of the NAS timer, the UE may retransmit the NAS message to the network.

[0744] The above NF may be AMF.

[0745] The above NAS procedure may be a registration procedure.

[0746] The above NAS message may be a registration request message.

[0747] The method may further include: receiving, by the UE, a registration acceptance message from the network; the registration acceptance message may include information about a new value of the NAS timer, and transmitting, by the UE, a new registration request to the network; starting, by the UE, the NAS timer with the new value applied, based on the UE transmitting the new registration request; and retransmitting, by the UE, the new registration request to the network based on the NAS timer expiring.

[0748] The above NF may be an SMF.

[0749] The above NAS procedure may be a PDU session related procedure.

[0750] The above NAS message may be a PDU session establishment request message.

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

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

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

[0754] The operations performed by the processor may include: a step in which a Network Function (NF) requests analytics for a Non-Access-Stratum (NAS) procedure from a NetWork Data Analytics Functions (NWDAF); a User Equipment (UE) performs the NAS procedure via a satellite, and based on the request, the NF receives first analytics from the NWDAF; based on the first analytics, the NF determines a value of a NAS-related timer; and a step in which the NF transmits information about the determined value of the NAS-related timer to the UE.

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

[0756] The operations performed by the processor may include: a step in which a Network Function (NF) requests analytics for a Non-Access-Stratum (NAS) procedure from a NetWork Data Analytics Functions (NWDAF); a User Equipment (UE) performs the NAS procedure via a satellite, and based on the request, the NF receives first analytics from the NWDAF; based on the first analytics, the NF determines a value of a NAS-related timer; and a step in which the NF transmits information about the determined value of the NAS-related timer to the UE.

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

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

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

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

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

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

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

[0764] The one or more stored commands may include: a step in which a Network Function (NF) requests analytics for a Non-Access-Stratum (NAS) procedure from a NetWork Data Analytics Functions (NWDAF); a User Equipment (UE) performs the NAS procedure via a satellite, and based on the request, the NF receives first analytics from the NWDAF; based on the first analytics, the NF determines a value of a NAS-related timer; and a step in which the NF transmits information about the determined value of the NAS-related timer to the UE.

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

[0766] This specification may have various effects.

[0767] For example, an appropriate NAS timer can be set through the procedures disclosed herein.

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

[0769] 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 where NF (Network Function) requests analytics for NAS (Non-Access-Stratum) procedures from NWDAF (NetWork Data Analytics Functions); UE (User Equipment) performs the above NAS procedure via satellite, Based on the above request, the step of the NF receiving first analytics from the NWDAF; A step in which the NF determines the value of the NAS-related timer based on the first analytics; A method comprising the step of the NF transmitting information about the value of the determined NAS-related timer to the UE.

2. In paragraph 1, A step in which the NF receives second analytics from the NWDAF; A step in which the NF determines a new value of the NAS-related timer based on the second analytics; A method further comprising the step of transmitting information about a new value of the determined NAS-related timer to the UE.

3. In paragraph 1 or 2, A method wherein the NAS-related timer is for at least one of a UE, a UE group, a region, an Access and Mobility Management Function (AMF), a Session Management Function (SMF), a Data Network Name (DNN), and a Single Network Slice Selection Assistance Information (S-NSSAI).

4. In any one of the clauses 1 to 3, A method wherein the request includes any one of an ID for analytics, target information for analytics, location-related information of the UE, location-related information of a RAN (Radio Access Network) node, Public Land Mobile Network (PLMN) information of a base station node to which the UE is connected, PLNM information of a relay UE to which the UE is connected, and information on an analytics target period.

5. In any one of paragraphs 1 to 4, The above NF is a method of SMF.

6. In paragraph 5, A step in which the above NF determines the value of the SMF timer to be used; The above NAS procedure is a PDU (Protocol Data Unit) session related procedure, A step in which the NF transmits a PDU session modification command to the UE; A step in which the NF starts the SMF timer based on the NF sending the PDU session modification command to the UE; A method further comprising the step of the NF retransmitting the PDU session modification command to the UE based on the expiration of the SMF timer.

7. In any one of paragraphs 1 to 4, The above NF is an AMF.

8. In paragraph 7, The step of the above NF determining the value of the SMF timer to be used by the SMF; The above NAS procedure is a PDU session related procedure, A method further comprising the step of transmitting information about the value of the SMF timer to the NF.

9. In paragraph 7, The step of the above NF transmitting information about the value of the determined NAS-related timer to the above UE is: A method comprising the step of the NF transmitting information about the value of the determined NAS-related timer to the UE via the SMF.

10. In paragraph 7, The above NAS procedure is a registration procedure, The above NAS related timer is a timer that starts when the UE transmits a registration request.

11. In paragraph 7, A method further comprising the step of the NF determining the value of the AMF timer to be used.

12. As a method, A step in which a UE (User Equipment) receives information about the value of a NAS timer for an NAS procedure from a NF (Network Function); The above NAS procedure is performed via satellite, A step in which the UE transmits a NAS message related to the NAS procedure to the network; A method comprising a step of the UE starting the NAS timer based on the UE transmitting the NAS message to the network.

13. In paragraph 12, A method further comprising the step of the UE retransmitting the NAS message to the network based on the expiration of the NAS timer.

14. In paragraph 12 or 13, The above NF is AMF, The above NAS procedure is a registration procedure, The above NAS message is a registration request message, The above method is: A step in which the UE receives a registration acceptance message from the network; The above registration acceptance message contains information about the new value of the NAS timer, The step of the UE transmitting a new registration request to the network; A step of starting the NAS timer to which the new value is applied based on the UE transmitting the new registration request; A method further comprising the step of the UE retransmitting the new registration request to the network based on the expiration of the NAS timer.

15. In paragraph 12 or 13, The above NF is SMF, The above NAS procedure is a PDU session related procedure. The above NAS message is a PDU session establishment request message.

16. As a Network Function (NF) 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 1 to 11.

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

18. As an apparatus in mobile communication, at least one processor; and At least one memory storing instructions and being operably electrically connected to at least one processor, A device wherein the operation performed based on the command being executed by the at least one processor is a method according to any one of claims 12 to 15.

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 12 to 15.

Images