Method for subscribing to events in response to change in terminal state

Abstract

One disclosure of the present specification provides a method. The method comprises steps in which a mobility-related NF: receives, from a base station, information related to event subscription for a UE, and a storage request for the information; stores the information related to the event subscription on the basis of the storage request; receives a service request from the UE; and transmits, to the base station, the information related to the event subscription on the basis of the service request.

Description

Method for subscribing to events based on terminal state changes

[0001] This specification relates to mobile communication.

[0002] 3GPP (3rd generation partnership project) LTE (long-term evolution) is a technology designed to enable high-speed packet communication. Many methods have been proposed to achieve LTE goals, such as reducing costs for users and operators, improving service quality, expanding coverage, and increasing system capacity. As high-level requirements, 3GPP LTE demands reduced cost per bit, improved service availability, flexible use of frequency bands, a simple structure, open interfaces, and appropriate power consumption of terminals.

[0003] Work has begun at the ITU (International Telecommunication Union) and 3GPP to develop 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, satisfying both urgent market demands and the longer-term requirements presented by the ITU-R (ITU Radio Communication Sector) IMT (International Mobile Telecommunications)-2020 process. Furthermore, NR must be able to utilize any spectrum band up to at least 100 GHz so that it can be used for wireless communication even in the distant future.

[0004] NR targets a single technical framework that covers all deployment scenarios, usage scenarios, and requirements, including eMBB (enhanced mobile broadband), mMTC (massive machine type communications), and URLLC (ultra-reliable and low latency communications). NR must inherently be forward compatible.

[0005] The base station transmits information related to event subscriptions and a request to store that information to the network.

[0006] FIG. 1 shows an example of a communication system to which the implementation of the present specification is applied.

[0007] FIG. 2 shows an example of a wireless device to which the implementation of the present specification applies.

[0008] FIG. 3 shows an example of a UE to which the implementation of the present specification applies.

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

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

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

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

[0013] Figure 10 shows an example of an O-RAN logical architecture.

[0014] FIGS. 11 and FIGS. 12 show examples of flowcharts of a first embodiment according to the disclosure of the present specification.

[0015] FIGS. 13 and FIGS. 14 show examples of flowcharts of a second embodiment according to the disclosure of the present specification.

[0016] FIG. 15 illustrates the procedure of the mobility NF for the disclosure of the present specification.

[0017] FIG. 16 illustrates the procedure of a base station for the disclosure of the present specification.

[0018] The following techniques, devices, and systems may 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 may be implemented through wireless technologies such as universal terrestrial radio access (UTRA) or CDMA2000. TDMA may be implemented through 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 through 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) using E-UTRA.3GPP LTE uses OFDMA in the downlink (DL) and SC-FDMA in the uplink (UL). Evolutions of 3GPP LTE include LTE-A (advanced), LTE-A Pro, and / or 5G NR (new radio).

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

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

[0021] In this specification, "A or B" may mean "only A," "only B," or "both A and B." Alternatively, in this specification, "A or B" may be interpreted as "A and / or B." For example, in this specification, "A, B or C" may mean "only A," "only B," "only C," or "any combination of A, B and C."

[0022] A slash ( / ) or a comma used in this specification may mean "and / or." For example, "A / B" may mean "A and / or B." Accordingly, "A / B" may mean "only A," "only B," or "both A and B." For example, "A, B, C" may mean "A, B or C."

[0023] In this specification, "at least one of A and B" may mean "only A," "only B," or "both A and B." Additionally, in this specification, the expressions "at least one of A or B" or "at least one of A and / or B" may be interpreted as synonymous with "at least one of A and B."

[0024] Additionally, in this specification, "at least one of A, B and C" may mean "only A," "only B," "only C," or "any combination of A, B and C." Furthermore, "at least one of A, B or C" or "at least one of A, B and / or C" may mean "at least one of A, B and C."

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

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

[0027] Although not limited thereto, the various descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification may be applied to various fields where wireless communication and / or connectivity between devices (e.g., 5G) is required.

[0028] The present specification will be described in more detail below with reference to the drawings. In the following drawings and / or description, the same reference numerals may refer to the same or corresponding hardware blocks, software blocks, and / or function blocks unless otherwise indicated.

[0029] FIG. 1 shows an example of a communication system to which the implementation of the present specification is applied.

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

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

[0032] Referring to FIG. 1, the 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 the network of the communication system (1), but the implementation of the present specification is not limited to a 5G system and may be applied to future communication systems beyond a 5G system.

[0033] The base station (200) and the network (300) can be implemented as wireless devices, and a specific wireless device can operate as a base station / network node in relation to another wireless device.

[0034] Wireless devices (100a to 100f) represent devices that perform communication using radio access technology (RAT) (e.g., 5G NR or LTE) and may also be referred to as communication / wireless / 5G devices. 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 with wireless communication capabilities, autonomous vehicles, and vehicles capable of performing communication between vehicles. 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 head-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., smartwatches or smart glasses), and computers (e.g., laptops). Home appliances may include TVs, refrigerators, and washing machines. IoT devices may include sensors and smart meters.

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

[0036] For example, a UAV can be an aircraft that is not on board and is navigated by radio control signals.

[0037] 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 a 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 a real world. For example, a holographic device may include a device for implementing a 360-degree stereoscopic image by recording and playing back stereoscopic information using the phenomenon of light interference that occurs when two laser lights called holograms meet.

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

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

[0040] For example, a medical device may be a device used for the purpose of diagnosing, treating, alleviating, curing, or preventing a disease. For example, a medical device may be a device used to diagnose, treat, alleviate, or correct 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, a (in vitro) diagnostic device, a hearing aid, or a surgical device.

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

[0042] 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 POS system.

[0043] For example, a weather / environment device may include a device for monitoring or predicting the weather / environment.

[0044] Wireless devices (100a to 100f) can be connected to a network (300) through a base station (200). AI technology may be applied to the wireless devices (100a to 100f), and the wireless devices (100a to 100f) can be connected to an AI server (400) through 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) may communicate with each other through the base station (200) / network (300), but they may 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., V2V (vehicle-to-vehicle) / V2X (vehicle-to-everything) communication). Also, IoT devices (e.g., sensors) can communicate directly with other IoT devices (e.g., sensors) or other wireless devices (100a to 100f).

[0045] Wireless communication / connections (150a, 150b, 150c) can be established between wireless devices (100a to 100f) and / or between wireless devices (100a to 100f) and base station (200) and / or between base station (200). Here, the wireless communication / connections can be established through various RATs (e.g., 5G NR), such as uplink / downlink communication (150a), sidelink communication (150b) (or D2D (device-to-device) communication), and communication between base stations (150c) (e.g., relay, IAB (integrated access and backhaul)). Through the wireless communication / connections (150a, 150b, 150c), wireless devices (100a to 100f) and base station (200) can transmit / receive wireless signals to / from each other. For example, wireless communication / connection (150a, 150b, 150c) may transmit / receive signals through various physical channels. To this end, based on various proposals in this specification, at least some of the following may be performed: a process for setting various configuration information for transmitting / receiving wireless signals, a process for various signal processing (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), and a resource allocation process.

[0046] AI refers to the field of researching artificial intelligence or the methodologies to create it, while machine learning refers to the field of researching methodologies to define and solve various problems within the realm of artificial intelligence. Machine learning is also defined as an algorithm that improves performance on a task through continuous experience.

[0047] A robot can refer to a machine that automatically processes or operates given tasks based on its own capabilities. In particular, a robot equipped with the ability to perceive its environment, make independent judgments, and perform actions can be called an intelligent robot. Robots can be classified into industrial, medical, domestic, and military types depending on their purpose or field of use. Robots are equipped with drive units, including actuators or motors, to perform various physical movements, such as moving robot joints. Additionally, mobile robots include wheels, brakes, propellers, etc., in their drive units, enabling them to drive on the ground or fly in the air.

[0048] Autonomous driving refers to technology that drives itself, and an autonomous vehicle refers to a vehicle that drives without user intervention or with minimal user intervention. For example, autonomous driving can include technologies such as maintaining the driving lane, automatically adjusting speed like adaptive cruise control, driving automatically along a predetermined route, and automatically setting a route and driving once a destination is set. The term "vehicle" encompasses vehicles equipped solely with internal combustion engines, hybrid vehicles equipped with both internal combustion engines and electric motors, and electric vehicles equipped solely with electric motors; it can include not only automobiles but also trains and motorcycles. An autonomous vehicle can be viewed as a robot equipped with autonomous driving capabilities.

[0049] Augmented Reality is a collective term for VR, AR, and MR. VR technology provides real-world objects or backgrounds solely as CG images, AR technology provides virtual CG images superimposed on 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 technology in that it displays real-world and virtual objects together. However, there is a difference in that while virtual objects in AR technology are used to complement real-world objects, virtual and real objects in MR technology are used as equal entities.

[0050] NR supports multiple numerologies or subcarrier spacings (SCS) to support various 5G services. For example, when the SCS is 15 kHz, it supports a wide area in traditional cellular bands; when the SCS is 30 kHz / 60 kHz, it supports dense-urban areas, lower latency, and wider carrier bandwidth; and when the SCS is 60 kHz or higher, it supports a bandwidth greater than 24.25 GHz to overcome phase noise.

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

[0052] Frequency Range Definition Frequency Range Subcarrier Spacing FR1 450 MHz - 6000 MHz 15, 30, 60 kHz FR2 24 250 MHz - 52600 MHz 60, 120, 240 kHz

[0053] As described above, the numerical values ​​of the frequency range of the NR system may change. For example, FR1 may include a band of 410 MHz to 7125 MHz as shown in Table 2 below. That is, FR1 may include a frequency band of 6 GHz (or 5850, 5900, 5925 MHz, etc.) or higher. For example, the frequency band of 6 GHz (or 5850, 5900, 5925 MHz, etc.) or higher included within FR1 may include an unlicensed band. The unlicensed band may be used for various purposes, for example, for communication for vehicles (e.g., autonomous driving).

[0054] Frequency Range Definition Frequency Range Subcarrier Spacing FR1 4 10 MHz - 7 125 MHz 15, 30, 60 kHz FR2 24 250 MHz - 5 2600 MHz 60, 120, 240 kHz

[0055] Here, the wireless communication technology implemented in the wireless device of this specification may include LTE, NR, and 6G, as well as narrowband IoT (NB-IoT) for low-power communication. For example, NB-IoT technology may be an example of low-power wide-area network (LPWAN) technology and may be implemented according to standards such as LTE Cat NB1 and / or LTE Cat NB2, but is not limited to the names mentioned above. Additionally, or generally, the wireless communication technology implemented in the wireless device of this specification may perform communication based on LTE-M technology. For example, LTE-M technology may be an example of LPWAN technology and may be referred to by various names such as enhanced MTC (eMTC). For example, LTE-M technology may be implemented in 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 names mentioned above. Additionally or generally, wireless communication technology implemented in the wireless device of this specification may include at least one of ZigBee, Bluetooth, and / or LPWAN for low-power communication, and is not limited to the names mentioned above. For example, ZigBee technology may create personal area networks (PANs) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and may be referred to by various names.

[0056] FIG. 2 shows an example of a wireless device to which the implementation of the present specification applies.

[0057] 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 example / service. For example, {the first wireless device (100) and the second wireless device (200)} may correspond to at least one of {wireless devices (100a–100f) and base station (200)}, {wireless devices (100a–100f) and wireless devices (100a–100f)} and / or {base station (200) and base station (200)} of FIG. 1. The first wireless device (100) and / or the second wireless device (200) may be composed of various components, devices / parts and / or modules.

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

[0059] 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 generally, the memory (104) may be placed outside the processing chip (101).

[0060] The processor (102) can control the memory (104) and / or the transceiver (106) and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed herein. For example, the processor (102) may process information within the memory (104) to generate a first information / signal and transmit a wireless signal containing the first information / signal through the transceiver (106). The processor (102) may receive a wireless signal containing a second information / signal through the transceiver (106) and process the second information / signal to store the obtained information in the memory (104).

[0061] Memory (104) may be connected to the processor (102) so as to be operable. Memory (104) may store various types of information and / or instructions. Memory (104) may store firmware and / or software code (105) that implements code, instructions, and / or sets of instructions that perform descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed in this specification when executed by the processor (102). For example, firmware and / or software code (105) may implement instructions that perform descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed in this specification when executed by the processor (102). For example, firmware and / or software code (105) may control the processor (102) to perform one or more protocols. For example, firmware and / or software code (105) may control the processor (102) to perform one or more wireless interface protocol layers.

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

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

[0064] 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 placed outside the processing chip (201).

[0065] The processor (202) can control the memory (204) and / or the transceiver (206) and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed herein. For example, the processor (202) may process information within the memory (204) to generate a third information / signal and transmit a wireless signal containing the third information / signal through the transceiver (206). The processor (202) may receive a wireless signal containing a fourth information / signal through the transceiver (206) and process the fourth information / signal to store the obtained information in the memory (204).

[0066] Memory (204) may be connected to the processor (202) so as to be operable. Memory (204) may store various types of information and / or instructions. Memory (204) may store firmware and / or software code (205) that implements instruction code, instructions, and / or sets of instructions that perform descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification when executed by the processor (202). For example, firmware and / or software code (205) may implement instructions that perform descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification when executed by the processor (202). For example, firmware and / or software code (205) may control the processor (202) to perform one or more protocols. For example, firmware and / or software code (205) may control the processor (202) to perform one or more wireless interface protocol layers.

[0067] 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 a wireless signal through one or more antennas (208). Each transceiver (206) may include a transmitter and / or receiver. The transceiver (206) may be interchangeably used with an RF unit. In this specification, the second wireless device (200) may represent a communication modem / circuit / chip.

[0068] 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 PHY (physical) layer, a MAC (media access control) layer, a RLC (radio link control) layer, a PDCP (packet data convergence protocol) layer, a RRC (radio resource control) layer, and an SDAP (service data adaptation protocol) layer). One or more processors (102, 202) may generate one or more PDUs (protocol data units), one or more SDUs (service data units), messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification. One or more processors (102, 202) may generate a signal (e.g., baseband signal) including a PDU, SDU, message, control information, data, or information according to the description, function, procedure, proposal, method, and / or operation flowchart disclosed in this specification and provide it to one or more transceivers (106, 206). One or more processors (102, 202) may receive a signal (e.g., baseband signal) from one or more transceivers (106, 206) and may obtain a PDU, SDU, message, control information, data, or information according to the description, function, procedure, proposal, method, and / or operation flowchart disclosed in this specification.

[0069] One or more processors (102, 202) may be referred to as a controller, a microcontroller, a microprocessor, and / or a microcomputer. 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 one or more processors (102, 202). For example, one or more processors (102, 202) may be composed of a set of communication control processors, application processors (APs), electronic control units (ECUs), central processing units (CPUs), graphic processing units (GPUs), and memory control processors.

[0070] One or more memories (104, 204) may be connected to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, codes, instructions, and / or commands. One or more memories (104, 204) may consist of random access memory (RAM), dynamic RAM (DRAM), read-only memory (ROM), erasable programmable ROM (EPROM), flash memory, volatile memory, non-volatile memory, hard drives, registers, cache memory, computer read storage media, and / or combinations thereof. One or more memories (104, 204) may be located inside and / or outside of one or more processors (102, 202). Additionally, one or more memories (104, 204) may be connected to one or more processors (102, 202) through various technologies such as wired or wireless connections.

[0071] One or more transceivers (106, 206) may transmit user data, control information, wireless signals / channels, etc., as described in the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification to one or more other devices. One or more transceivers (106, 206) may receive user data, control information, wireless signals / channels, etc., as described in the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification from one or more other devices. For example, one or more transceivers (106, 206) may be connected to one or more processors (102, 202) and may transmit and receive wireless signals. For example, one or more processors (102, 202) may 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) can control one or more transceivers (106, 206) to receive user data, control information, wireless signals, etc. from one or more other devices.

[0072] One or more transceivers (106, 206) may be connected to one or more antennas (108, 208). Additionally and / or generally, 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 operation flowcharts disclosed herein through one or more antennas (108, 208). In this specification, one or more antennas (108, 208) may be a plurality of physical antennas or a plurality of logical antennas (e.g., antenna ports).

[0073] One or more transceivers (106, 206) can convert received user data, control information, wireless signals / channels, etc. from RF band signals to baseband signals in order to process received user data, control information, wireless signals / channels, etc. using one or more processors (102, 202). One or more transceivers (106, 206) can convert processed user data, control information, wireless signals / channels, etc. from baseband signals to RF band signals using one or more processors (102, 202). To this end, one or more transceivers (106, 206) may include (analog) oscillators and / or filters. For example, one or more transceivers (106, 206) can up-convert an OFDM baseband signal into an OFDM signal through 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) can receive an OFDM signal at a carrier frequency and down-convert the OFDM signal into an OFDM baseband signal through an (analog) oscillator and / or filter under the control of one or more processors (102, 202).

[0074] Although not illustrated in FIG. 2, the wireless device (100, 200) may 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., audio I / O port, video I / O port), a driving unit, and a computing unit. The additional components (140) may be connected to one or more processors (102, 202) through various technologies, such as wired or wireless connections.

[0075] In an implementation of this specification, the UE may operate as a transmitting device in the uplink (UL; uplink) and as a receiving device in the downlink (DL; downlink). In an implementation of this specification, the base station may operate as a receiving device in the UL and as a transmitting device in the DL. For technical convenience, it is generally assumed 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 to the first wireless device (100) may be configured to perform UE operations according to an implementation of this specification or to control a transceiver (106) to perform UE operations according to an implementation of this specification. A processor (202) connected to, mounted on, or released to the second wireless device (200) may be configured to perform base station operations according to an implementation of this specification or to control a transceiver (206) to perform base station operations according to an implementation of this specification.

[0076] In this specification, the base station may be referred to as Node B, eNode B, or gNB.

[0077] FIG. 3 shows an example of a UE to which the implementation of the present specification applies.

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

[0079] The UE (100) includes a processor (102), memory (104), 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).

[0080] The processor (102) may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operation 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 operation flowcharts disclosed herein. Layers of a wireless 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 processor, EXYNOS made by Samsung® TM Series processors, A Series processors made by Apple®, HELIO made by MediaTek® TM Series processors, ATOM made by Intel® TM It can be found in series processors or corresponding next-generation processors.

[0081] Memory (104) is coupled to the processor (102) so as to be operable and stores various information for operating the processor (102). Memory (104) may include ROM, RAM, flash memory, memory card, storage medium and / or other storage device. When the implementation is implemented in software, the technology described herein may be implemented using modules (e.g., procedures, functions, etc.) that perform the descriptions, functions, procedures, proposals, methods and / or operation flowcharts disclosed herein. Modules may be stored in memory (104) and executed by the processor (102). Memory (104) may be implemented within the processor (102) or outside the processor (102), in which case it may be communicatively coupled to the processor (102) through various methods known in the technology.

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

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

[0084] The display (143) outputs the result 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).

[0085] A SIM card (145) is an integrated circuit for securely storing an International Mobile Subscriber Identity (IMSI) and associated keys, and is used to identify and authenticate a subscriber in a mobile device such as a mobile phone or computer. Additionally, contact information can be stored on many SIM cards.

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

[0087] Figure 4 is a structural diagram of a next-generation mobile communication network.

[0088] 5GC (5G Core) may include various components, and FIG. 5 includes some of them, such as 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).

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

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

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

[0092] The illustrated AMF (410) can manage access and mobility in a 5G system. The AMF (410) can perform the function of managing Non-Access Stratum (NAS) security. The AMF (410) can perform the function of handling mobility in an idle state.

[0093] 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 communication.

[0094] 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 the data path between the gNB (20) and the SMF (420). Additionally, 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 the function of handling PDUs. For mobility within the NG-RAN (Next Generation Radio Access Network defined in 3GPP Release-15 or later), packets can be routed through the UPF. Additionally, the UPF (440) may also function as an anchor point for mobility with other 3GPP networks (RANs defined prior to 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.

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

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

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

[0098] The illustrated SMF (420) can perform the function of assigning the IP (Internet Protocol) address of the UE. Also, the SMF (420) can control the PDU (protocol data unit) session.

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

[0100] Fifth-generation mobile communication supports multiple numerologies or subcarrier spacings (SCS) to support various 5G services. For example, when the SCS is 15 kHz, it supports a wide area in traditional cellular bands; when the SCS is 30 kHz / 60 kHz, it supports dense-urban environments, lower latency, and wider carrier bandwidth; and when the SCS is 60 kHz or higher, it supports a bandwidth greater than 24.25 GHz to overcome phase noise.

[0101] FIG. 5 shows an example of a 5G system structure to which the implementation of the present specification is applied.

[0102] The 5G system (5GS) structure consists of the following network functions (NF).

[0103] - AUSF (Authentication Server Function)

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

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

[0106] - USDF (Unstructured Data Storage Function)

[0107] - NEF (Network Exposure Function)

[0108] - I-NEF (Intermediate NEF)

[0109] - NRF (Network Repository Function)

[0110] - NSSF (Network Slice Selection Function)

[0111] - PCF (Policy Control Function)

[0112] - SMF (Session Management Function)

[0113] - UDM (Unified Data Management)

[0114] - UDR (Unified Data Repository)

[0115] - UPF (User Plane Function)

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

[0117] - AF (Application Function)

[0118] - UE (User Equipment)

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

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

[0121] - NWDAF (Network Data Analytics Function)

[0122] - CHF (CHarging Function)

[0123] In addition, the following network functions may be considered.

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

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

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

[0127] Figure 5 shows the 5G system structure in a non-roaming case using a reference point representation that shows how various network functions interact with each other.

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

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

[0130] The 5G system structure includes the following reference points.

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

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

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

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

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

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

[0137] The following reference points show the interactions that exist between the NF services of NF.

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

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

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

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

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

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

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

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

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

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

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

[0149] In some cases, two NFs may need to be connected to each other to service the UE.

[0150] <Registration Procedure>

[0151] The registration procedure is described. Refer to Section 4.2.2.2 of 3GPP TS 23.502 V16.3.0 (2019-12).

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

[0153] The 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.

[0154] - Initial registration for the 5GS; or

[0155] - Mobility registration update; or

[0156] - Periodic registration update; or

[0157] - Emergency registration

[0158] The general registration procedure of Figures 6 and 7 applies to all registration procedures described above, but the periodic registration update does not need to include all parameters used in other registration procedures.

[0159] The general registration procedure of Figures 6 and 7 is used when a UE is registered to a 3GPP connection when it is already registered to a non-3GPP connection, and vice versa. To register a UE to a 3GPP connection when it is already registered to a non-3GPP connection scenario, an AMF change may be required.

[0160] First, the procedure of Fig. 6 is explained.

[0161] (1) Step 1: The UE sends a Registration Request message to the (R)AN. The Registration Request message corresponds to the AN message.

[0162] A registration request message may include AN parameters. For NG-RAN, AN parameters include, for example, 5G-S-TMSI (5G SAE temporary mobile subscriber identity) or GUAMI (globally unique AMF ID), a selected PLMN (public land mobile network) ID (or PLMN ID and NID (network identifier)), and requested NSSAI (Requested network slice selection assistance information). AN parameters also include an establishment cause. The establishment cause provides the reason for requesting the 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.

[0163] The 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 the RM-DEREGISTERED state), or a mobility registration update (i.e., the UE is in the RM-REGISTERED state and initiates the registration process because the UE moves, or the UE wants to update capabilities or protocol parameters, or requests a change to the set of network slices allowed for the UE to use), or a periodic registration update (i.e., the UE is in the RM-REGISTERED state and initiates the registration process due to the expiration of the periodic registration update timer), or an urgent registration (i.e., the UE is in the restricted service state).

[0164] When a UE performs initial registration, the UE specifies the UE ID in the registration request message as follows, listed in order of decreasing priority.

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

[0166] ii) Native 5G-GUTI assigned by the PLMN for which the UE is attempting to register (if available);

[0167] iii) Native 5G-GUTI assigned by a PLMN equivalent to the PLMN for which the UE is attempting to register;

[0168] iv) Native 5G-GUTI assigned by other PLMNs (if available);

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

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

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

[0172] In the case of emergency registration, SUCI is included if the UE does not have a valid 5G-GUTI, and PEI is included if the UE does not have a SUPI (subscriber permanent identifier) ​​and does not have a valid 5G-GUTI. In other cases, a 5G-GUTI is included, which indicates the last serving AMF.

[0173] 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 established PDU session of the current PLMN in the UE.

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

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

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

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

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

[0179] The registration request message may include all information and / or part of the information contained in the registration request message received from the UE described in Step 1.

[0180] The registration request message may include N2 parameters. When NG-RAN is used, the N2 parameters include the selected PLMN ID (or PLMN ID and NID), location information and cell ID associated with the cell where the UE is camping, and a UE context request indicating that a UE context including security information in NG-RAN must be established. When NG-RAN is used, the N2 parameters also include the cause for establishment.

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

[0182] (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 call the Namf_Communication_UEContextTransfer service operation on the previous AMF, including the full registration request NAS (non-access stratum) message to request the UE's SUPI and UE context.

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

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

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

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

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

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

[0189] (11) Step 11: If the PEI is not provided by the UE or has not been retrieved from the previous AMF, the new AMF may initiate an Identity Request procedure by sending an Identity Request message to the UE to retrieve the PEI. The PEI is transmitted in encryption, except in cases where the UE cannot perform emergency registration and be authenticated.

[0190] (12) Step 12: Optionally, the new AMF can call the N5g-eir_EquipmentIdentityCheck_Get service operation to start ME ID checking.

[0191] Now, the procedure of Fig. 7 following the procedure of Fig. 6 is explained.

[0192] (13) Step 13: If you perform Step 14 below, the new AMF can select a UDM based on SUPI, and the UDM can select a UDR instance.

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

[0194] (15) Step 15: The new AMF can select PCF.

[0195] (16) Step 16: The new AMF may optionally establish / modify AM policy associations.

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

[0197] (18) Step 18: If the new AMF and the previous AMF are in the same PLMN, the new AMF can send a request to modify the UE context to N3IWF / TNGF / W-AGF.

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

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

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

[0201] The new AMF sends a registration acceptance message to the UE indicating that the registration request has been accepted. If the new AMF assigns a new 5G-GUTI, the 5G-GUTI is included. If the UE is already in the RM-REGISTERED state via another connection on the same PLMN, the UE uses the 5G-GUTI received in the registration acceptance message for both registrations. If the registration acceptance message does not include a 5G-GUTI, the UE uses the 5G-GUTI assigned to the existing registration for the new registration as well. If the new AMF assigns a new registration area, it transmits the registration area to the UE via the registration acceptance message. If the registration acceptance message does not contain a registration area, the UE considers the previous registration area to be valid. Mobility Restrictions are included when mobility restrictions apply to the UE and the registration type is not an urgent registration. The new AMF indicates the PDU session 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 connects to two AMFs belonging to different PLMNs via a 3GPP connection and a non-3GPP connection, the UE locally removes internal resources associated with the PDU session of the current PLMN that are not indicated as established in the received PDU session state. If PDU session state information is present in the registration acceptance message, the new AMF instructs the UE on the PDU session state.

[0202] The Allowed NSSAI provided in the registration acceptance message is valid in the registration area and applies to all PLMNs having a tracking area included in the registration area. The Mapping of Allowed NSSAI is to map the HPLMN S-NSSAI to each S-NSSAI of the Allowed NSSAI. The Mapping of Configured NSSAI is to map the HPLMN S-NSSAI to each S-NSSAI of the Configured NSSAI for the serving PLMN.

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

[0204] (22) Step 22: If the UE succeeds in updating itself, it can send a Registration Complete message to the new AMF.

[0205] The UE can send a registration completion message to the new AMF to check if a new 5G-GUTI has been assigned.

[0206] (23) Step 23: In the case of registration via a 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 the case of registration via a non-3GPP connection, if the UE is in a CM-CONTENED state on the 3GPP connection, the new AMF may send RRC Inactive Assistance information to the NG-RAN.

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

[0208] (25) Step 25: The UE can execute network slice-specific authentication and authorization (NSSAA) procedures.

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

[0210] The procedure for establishing a PDU session is described. Refer to Section 4.3.2 of 3GPP TS 23.502 V16.3.0 (2019-12).

[0211] FIGS. 8 and 9 illustrate examples of PDU session establishment procedures to which the implementation of the present specification applies.

[0212] PDU session establishment may fall under the following:

[0213] - Procedure for establishing a PDU session initiated by the UE

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

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

[0216] - Procedure for establishing a PDU session triggered by the network

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

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

[0219] In the procedure shown in Figures 8 and 9, since the UE is already registered with the AMF, it is assumed that the AMF has already retrieved user subscription data from the UDM unless the UE is urgently registered.

[0220] First, the procedure of Fig. 8 will be explained.

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

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

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

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

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

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

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

[0228] If the request type indicates an "existing PDU session" that refers to an existing PDU session moving between a 3GPP connection and a non-3GPP connection, and the serving PLMN S-NSSAI of the PDU session exists in the allowed NSSAI of the target connection type, the PDU session establishment procedure may be performed in the following cases.

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

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

[0231] Otherwise, the AMF rejects the request to establish a PDU session with an appropriate reason for rejection.

[0232] AMF rejects requests from urgently registered UEs where the request type does not indicate "Urgent Request" or "Existing Urgent PDU Session".

[0233] (3) Step 3: If the AMF is not associated with an SMF for a PDU session ID provided by the UE (e.g., when the request type indicates "initial request"), the AMF calls the Create SMContext request procedure (e.g., Nsmf_PDUSession_CreateSMContext Request). If the AMF is already associated with an SMF for a PDU session ID provided by the UE (e.g., when the request type indicates "existing PDU session"), the AMF calls the Update SMContext request procedure (e.g., Nsmf_PDUSession_UpdateSMContext Request).

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

[0235] The AMF ID is the UE's GUAMI and uniquely identifies the AMF serving the UE. The AMF transmits the PDU Session ID along with an N1 SM container containing the PDU session establishment request message received from the UE. The generic public subscription identifier (GPSI) is included if available in the AMF.

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

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

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

[0239] (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 in accordance with the request received in Step 3.

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

[0241] If the SMF decides not to accept the establishment of a PDU session, the SMF rejects the UE request via a NAS SM signal containing 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 that the SMF proceeds to step 20 below and the PDU session establishment procedure is stopped.

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

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

[0244] (7b) Step 7b: SMF can establish an SM policy association with PCF and obtain a basic PCC rule for the PDU session by performing the SM policy association establishment procedure.

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

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

[0247] (10) Step 10: If the request type indicates an “initial request,” the SMF may initiate an N4 Session Establishment procedure with the selected UPF. Otherwise, the SMF may initiate an N4 Session Modification procedure with the selected UPF.

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

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

[0250] The N1N2 message delivery message may include N2 SM information. The N2 SM information carries the following information that the AMF will transmit to the (R)AN.

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

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

[0253] - PDU Session ID: Indicates to the UE the association between the RAN resource and the PDU session for the UE;

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

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

[0256] - Maximum data rate for UE integrity protection received in PDU session establishment request message: When integrity protection is indicated as "Preferred" or "Required" in user plane security enforcement information

[0257] - RSN (redundancy sequence number) parameter

[0258] The N1N2 message delivery message may include an N1 SM container. The N1 SM container includes a PDU session establishment acceptance message that the AMF will provide to the UE. The PDU session establishment acceptance message includes an S-NSSAI from an allowed NSASI. In the case of an LBO roaming scenario, the PDU session establishment acceptance message includes an S-NSSAI from an allowed NSSAI for the VPLMN, and also includes the corresponding S-NSSAI for the HPLMN from the mapping of the allowed NSSAI received by the SMF in step 3.

[0259] If necessary for QoS flows related to QoS rules and QoS profiles, multiple QoS rules, QoS flow levels, and QoS parameters may be included in the PDU session establishment acceptance message and N2 SM information within the N1 SM container.

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

[0261] (12) Step 12: The AMF sends a NAS message containing a PDU session ID destined for the UE, a message accepting the establishment of a PDU session, and N2 SM information received from the SMF to (R)AN within the N2 PDU session request message.

[0262] (13) Step 13: (R)AN can perform AN-specific signal exchanges with the UE regarding information received from the SMF. For example, in the case of NG-RAN, it can perform RRC connection reconfiguration with the UE to set up necessary NG-RAN resources in relation to the QoS rules for the PDU session request received by the UE in Step 12.

[0263] (R)AN forwards the NAS message (PDU session ID, N1 SM container (PDU session establishment acceptance message)) received in step 12 to the UE. (R)AN provides the NAS message to the UE only if the AN-specific signal exchange with the UE includes the addition of (R)AN resources related to the received N2 command.

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

[0265] Now, the procedure of Fig. 9 following the procedure of Fig. 8 is explained.

[0266] (14) Step 14: (R)AN sends an N2 PDU session response message to AMF. The N2 PDU session response message may include a PDU session ID, cause, N2 SM information (PDU session ID, AN tunnel information, list of accepted / rejected QFIs, user plane enforcement policy notifications), etc.

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

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

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

[0270] After this step, UPF can deliver the DL packet that may have been buffered for this PDU session to the UE.

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

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

[0273] After this step, AMF delivers the relevant events subscribed to by SMF.

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

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

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

[0277] (21) Step 21: If the establishment of a PDU session fails after Step 4, and the SMF no longer processes the UE's PDU session, the SMF may unsubscribe from the modification of the session management subscription data.

[0278] <O-RAN (open RAN)>

[0279] Figure 10 shows an example of an O-RAN logical architecture.

[0280] In 5G networks, the Service Based Interface (SBI) was defined within the 5G core network, and standardization was carried out to make it suitable for providing 5GC services in a cloud environment.

[0281] However, SBI between the base station and 5GC was not introduced, and the conventional point-to-point NG-AP protocol was defined.

[0282] Meanwhile, as standardization for NG-RAN progressed at 3GPP, the base station was subdivided into CU-CP / CU-UP / DU. In O-RAN, aiming for a cloud-based RAN, even interfaces not defined in 3GPP standards (e.g., A1, E2) are being defined.

[0283] Considering these circumstances, there is a possibility that SBI will be used between the base station and the core network in 6G networks.

[0284] Meanwhile, in the case of the existing SBI, a consumer NF can perform a subscription to an event from a producer NF. Here, the performance of the subscription can be carried out not only in the form of a simple request / response but also in the form of a subscribe / notify. In this case, there is an action in which the producer NF notifies the consumer NF regarding the occurrence of an event.

[0285] When a base station sends a terminal to an idle state, the base station can delete all context for the terminal.

[0286] If the NF of the base station and the core network perform a subscription to an event and use a service (a subscription / notification type service), when the terminal enters an idle state, all contexts for the terminal of the base station are deleted. Consequently, the above service (a subscription / notification type service) is interrupted.

[0287] Afterwards, when the terminal becomes connected again, signaling transmission and reception of the core network's NF (and / or base station) is required again for event subscription.

[0288] When a base station performs subscription / notification with multiple core networks' NFs, there is a problem of a large amount of signaling occurring because signaling for event subscription with each core network's NF is required whenever a terminal becomes connected.

[0289] A method for solving the aforementioned problem may be proposed in this specification.

[0290] The proposed method may consist of a combination of one or more of the actions / configurations / steps described below.

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

[0292] I. Method for a base station to request the core network to store event subscription information

[0293] When a core NF performs an event subscription for a terminal to a base station, the base station may store information about the event subscription in the terminal context. If conditions are met, the base station may perform an event notification to the core NF.

[0294] Conversely, if the base station performs an event subscription for the terminal with the core NF, the base station may have information about the event subscription.

[0295] In this way, when event subscription is performed between a base station and a core network, the base station may have information about the event subscription.

[0296] In the following cases, the base station may request the core network node to store information related to event subscriptions:

[0297] - If the base station has information related to event subscription and

[0298] - Cases where the base station sends (or transitions) the terminal to an idle state (e.g., when the base station sends the terminal to an idle state because there is no traffic transmission from the terminal, or when the core network (e.g., AMF) sends the terminal to an idle state)

[0299] The base station can transmit information related to the above event subscription while making a request to the core network node.

[0300] The above event subscription information may include at least one of the following:

[0301] - Event type,

[0302] - Information about the NF that performed the event subscription,

[0303] - URI information for event notification,

[0304] - Event reporting method (e.g., reporting cycle, reporting conditions, reporting time),

[0305] - Last reported information,

[0306] - Various other information

[0307] In this specification, event subscription information (or information regarding event subscription) may refer to the aforementioned event subscription-related information.

[0308] Based on the save request, the core network node (e.g., AMF) can store information about the event subscription.

[0309] Subsequently, when the terminal becomes connected again (e.g., when the AMF transmits the initial context setup for the terminal to the base station), the core network node (e.g., AMF) can transmit information regarding the aforementioned event subscription for the terminal to the base station.

[0310] The above-described method was explained using an AMF connected to a base station to manage the core network access, registration, mobility, etc., of a terminal as an example. The method disclosed in this specification may also be applied to NFs other than AMFs (e.g., various NFs that perform event subscriptions to a base station, various NFs that receive event subscriptions from a base station).

[0311] I-1. First Embodiment: Method for MM NF (e.g., 6G AMF) to store event subscription information in a base station

[0312] The following drawings are made to illustrate a specific example of the present specification. The names of specific devices or specific signals / messages / fields described in the drawings are presented as examples, and therefore the technical features of the present specification are not limited to the specific names used in the following drawings.

[0313] FIGS. 11 and FIGS. 12 show examples of flowcharts of a first embodiment according to the disclosure of the present specification.

[0314] In the first embodiment, the MM NF (e.g., 6G AMF) can store information related to event subscriptions at the base station.

[0315] 1) Step 1

[0316] The terminal can register with the network.

[0317] Assume that the terminal has successfully completed the network registration process.

[0318] 2) Step 2

[0319] The terminal can establish a PDU session with the network.

[0320] Assume that the terminal establishes a PDU session with the network and is receiving services.

[0321] 3) Step 3

[0322] In order to obtain information about a terminal from a base station, an SM (Session Management) NF (e.g., 6G SMF) that manages PDU sessions can perform event subscription to the base station.

[0323] For example, SM (Session Management) NF (e.g., 6G SMF) can perform event subscriptions to be notified when the QoS provided to the terminal is not satisfied.

[0324] 4) Step 4

[0325] The base station can detect / determine that it has not exchanged data with the terminal for a certain period of time or longer. Based on this, (to put the terminal into an idle state), the base station can send a notification message to the Mobility Management (MM) NF (e.g., 6G AMF) that manages the terminal's mobility, informing it that the terminal's connection release is required.

[0326] For example, the transmission of the above notification message may be based on the fact that, in step 1, the MM NF (e.g., 6G AMF) performs (explicitly or implicitly) an event subscription to notify the inactivity of the terminal while transmitting a message to the base station to create the context of the terminal.

[0327] For example, the transmission of the above notification message may be based on the fact that, after the context of the terminal is created, the MM NF (e.g., 6G AMF) performs an event subscription to notify the base station of the terminal's inactivity.

[0328] When the base station transmits the above notification message, if there is information regarding event subscription for the terminal, the base station may transmit the information regarding event subscription and a request to store said information to the MM NF (e.g., 6G AMF).

[0329] This process may also be performed in step 9.

[0330] 5) Step 5

[0331] The MM NF (e.g., 6G AMF) can notify the SM NF (e.g., 6G SMF) that the user plane resource of the PDU session must be released. If there are multiple PDU sessions, this process can be performed by the SM NF (e.g., 6G SMF) managing each PDU session.

[0332] 6) Step 6

[0333] To release user plane resources, the SM NF (e.g., SMF) may request the UP (User Plane) NF (e.g., 6G UPF) to release the user plane resources.

[0334] Afterwards, SM NF (e.g., 6G SMF) can transmit the response of step 5 to MM NF (e.g., 6G AMF).

[0335] 7) Step 7

[0336] MM NF (e.g., 6G AMF) can send a message to the base station to clear the UE context.

[0337] For example, MM NF (e.g. 6G AMF) can send a request to the base station to delete the UE context.

[0338] 8) Step 8

[0339] The base station can disconnect the AN connection with the terminal.

[0340] 9) Step 9

[0341] The base station can transmit the response to step 7 to the MM NF (e.g., 6G AMF).

[0342] At this time, if there is information regarding event subscription for the terminal, the base station may request storage of said information while transmitting the event subscription information to the MM NF (e.g., 6G AMF). This process may also be performed in step 4.

[0343] Based on the message of step 7, after the AN connection (e.g., RRC connection) with the terminal is disconnected, the base station can delete information related to event subscription and UE context.

[0344] 10) Step 10

[0345] In order to transmit data and for the terminal to enter a connected state, the terminal may send a service request message to the MM NF (e.g., 6G AMF).

[0346] At this time, the terminal may include information requesting user plane activation for a PDU session for transmitting data in the service request message.

[0347] 11) step 11

[0348] Based on information provided by the terminal, the MM NF (e.g., 6G AMF) can notify the SM NF (e.g., 6G SMF) managing the PDU session for which the terminal requested activation that PDU session activation is required.

[0349] 12) Step 12

[0350] For activation of a PDU session, the SM NF (e.g., 6G SMF) may request the UP (User Plane) NF (e.g., 6G UPF) to set up a user plane resource.

[0351] Afterwards, the SM NF (e.g., 6G SMF) can transmit the response of step 11 to the MM NF (e.g., 6G AMF). At this time, the SM NF (e.g., 6G SMF) can also transmit information that needs to be sent to the base station for user plane resource setup.

[0352] 13) Step 13

[0353] Based on Step 10 and / or Step 12, the MM NF (e.g., 6G AMF) may send a request to the base station to create a UE context.

[0354] At this time, the MM NF (e.g., 6G AMF) can transmit information transmitted by the SM NF (e.g., 6G SMF) (e.g., N2 information (a message requesting resource allocation for a PDU session)) and UE context information for the terminal to the base station. In this process, if there is event subscription-related information stored in the MM NF (e.g., 6G AMF) due to a request from the base station through step 9 (or step 4), the MM NF (e.g., 6G AMF) can transmit the event subscription-related information to the base station together.

[0355] 14) Step 14

[0356] The base station can set up user plane resources for the PDU session requested by the terminal through signaling with the terminal.

[0357] 15) Step 15

[0358] The base station can transmit the response of step 13 in MM NF (e.g., 6G AMF). In this process, the base station can also transmit information about the assigned user plane (information to be transmitted in SM NF (e.g., 6G SMF)). This information can be transmitted in SM NF (e.g., 6G SMF).

[0359] 16) Step 16

[0360] The MM NF (e.g., 6G AMF) can transmit the information transmitted by the base station in step 15 to the SM NF (e.g., 6G SMF).

[0361] For example, the MM NF (e.g., 6G AMF) can transmit information about the user plane assigned by the base station to the SM NF (e.g., 6G SMF).

[0362] 17) step 17

[0363] SM NF (e.g., 6G SMF) can transmit the response of step 16 to MM NF (e.g., 6G AMF).

[0364] 18) Step 18

[0365] In step 3, if the SM NF (e.g., 6G SMF) has subscribed to an event from the base station, when the corresponding condition is satisfied (e.g., the QoS that must be provided to the terminal is not satisfied due to a change in the wireless environment), the base station may provide an event notification to the SM NF (e.g., 6G SMF).

[0366] II. How to Use Indirect Communication

[0367] According to the prior art, when using SBI between NFs, the NFs can perform direct communication.

[0368] Alternatively, according to the prior art, when using SBI among NFs, the NFs can perform indirect communication through an NF called SCP (Service Communication Proxy).

[0369] Similar to conventional indirect communication methods, when base stations and core NFs perform communication using SBI (e.g., event subscription), indirect communication can be performed through an NF that performs a proxy function similar to SCP.

[0370] For example, a core NF (e.g., AMF) that manages the mobility of a terminal can perform the function of a proxy NF. Or, an NF that performs the function of a proxy may be defined.

[0371] When a core NF (consumer NF) performs an event subscription to a base station, the following actions may be performed:

[0372] - The core NF transmits signaling to the proxy NF, and the proxy NF transmits signaling back to the base station.

[0373] - Subsequently, the proxy NF receives a response from the base station, and the proxy NF can send the response back to the core NF (consumer NF).

[0374] - Subsequently, when the base station transmits an event notification (e.g., when the condition is satisfied and the base station transmits an event notification), the base station transmits the event notification to the proxy NF, and the proxy NF can then transmit the event notification to the core NF (consumer NF).

[0375] - When the terminal enters an idle state, the base station may notify the proxy NF that it cannot perform the service for the proxy NF's event subscription requested by the core NF (e.g., event notification service). For example, the base station may notify the proxy NF of the event subscription termination while sending an event notification. At this time, the base station may also send information indicating that the terminal has entered an idle state.

[0376] - When a proxy NF receives information indicating that it cannot perform a service for event subscription (e.g., a notification service for an event), the proxy NF may continue to maintain the event without notifying the core NF of event subscription termination. Subsequently, when the terminal becomes connected (e.g., when the proxy NF performs an event subscription for the terminal's state from the mobility-managing NF and receives a notification (a notification for the terminal's connected state), or when the proxy NF is the same as or co-located with the mobility-managing NF and recognizes the terminal's connected state), the proxy NF may perform an event subscription again with the base station.

[0377] Instead of providing information (e.g., termination of event subscription) indicating that the base station cannot perform the service for the event subscription (e.g., notification service for the event), the proxy NF can perform an event subscription regarding the terminal's state (e.g., a subscription requesting a notification when the terminal becomes idle) to the base station / NF (core NF managing terminal mobility). Subsequently, the proxy NF can receive a notification that the terminal has become idle. Based on this, the proxy NF can recognize that the base station cannot perform the event notification. Subsequently, when the terminal becomes connected, the proxy NF can perform the event subscription again with the base station.

[0378] Conversely, if the base station performs event subscription with the core NF, the following actions may be performed:

[0379] - The base station transmits signaling to the proxy NF, and the proxy NF can transmit signaling back to the core NF.

[0380] - Afterwards, the proxy NF receives a response from the core NF, and the proxy NF can send the response back to the base station.

[0381] - Subsequently, when the core NF sends an event notification (e.g., when the core NF sends an event notification because a condition is satisfied), the core NF sends the event notification to the proxy NF, and the proxy NF can then send the event notification to the base station.

[0382] - When the terminal is in an idle state, the core NF can send event notifications to the proxy NF. If the proxy NF detects the terminal's idle state, the proxy NF may store the event notifications sent by the core NF.

[0383] - Afterwards, when the terminal becomes connected, the proxy NF can transmit the stored event notification to the base station.

[0384] As in I, the Mobility Management NF may receive and store event subscription information from the base station. When the terminal becomes connected, the Mobility Management NF may transmit the event subscription information to the base station. Based on this, the base station can understand the event notification transmitted from the proxy NF.

[0385] If a proxy NF receives the same event subscription from the same terminal from multiple NFs, the proxy NF can merge them and perform an event subscription to the base station.

[0386] II-1. Second Embodiment: Method in which an MM NF (e.g., 6G AMF) operates as a proxy NF

[0387] The following drawings are made to illustrate a specific example of the present specification. The names of specific devices or specific signals / messages / fields described in the drawings are presented as examples, and therefore the technical features of the present specification are not limited to the specific names used in the following drawings.

[0388] FIGS. 13 and FIGS. 14 show examples of flowcharts of a second embodiment according to the disclosure of the present specification.

[0389] In the second embodiment, the MM NF (e.g., 6G AMF) can operate as a proxy NF (or MM NF + proxy NF).

[0390] 1) Step 1

[0391] The terminal can register with the network.

[0392] Assume that the terminal has successfully completed the network registration process.

[0393] 2) Step 2

[0394] The terminal can establish a PDU session with the network.

[0395] Assume that the terminal establishes a PDU session with the network and is receiving services.

[0396] 3) Step 3

[0397] To obtain information from a PM NF (Policy Management NF) (e.g., PCF), the base station can subscribe to events from the PM NF (Policy Management NF) (e.g., PCF).

[0398] For example, the above event subscription may be intended to obtain updated information regarding RFSP indexes, sidelink operation-related parameters (e.g., PC5 QoS parameters), etc.

[0399] 4) Step 4

[0400] The base station can detect / determine that it has not exchanged data with the terminal for a certain period of time or longer. Based on this, (to put the terminal into an idle state), the base station can send a notification message to the Mobility Management (MM) NF (e.g., 6G AMF) that manages the terminal's mobility, informing it that the terminal's connection release is required.

[0401] For example, the transmission of the above notification message may be based on the fact that, in step 1, the MM NF (e.g., 6G AMF) performs (explicitly or implicitly) an event subscription to notify the inactivity of the terminal while transmitting a message to the base station to create the context of the terminal.

[0402] For example, the transmission of the above notification message may be based on the fact that, after the context of the terminal is created, the MM NF (e.g., 6G AMF) performs an event subscription to notify the base station of the terminal's inactivity.

[0403] When the base station transmits the above notification message, if there is information regarding event subscription for the terminal, the base station may transmit the information regarding event subscription and a request to store said information to the MM NF (e.g., 6G AMF).

[0404] This process may also be performed in step 9.

[0405] 5-9) Step 5 to Step 9

[0406] Steps 5 to 9 can be performed as steps 5 to 9 of the first embodiment (Figs. 11 and 12).

[0407] The MM NF in steps 5 to 9 of the first embodiment (Figs. 11 and 12) can be replaced with a proxy NF (or MM NF + proxy NF).

[0408] 10) Step 10

[0409] While the terminal is in an idle state, the PM NF (Policy Management NF) (e.g., PCF) may decide to transmit the terminal's updated RFSP index.

[0410] The above decision may be made based on various information, such as changes in the terminal's subscription, network load information, and analytics-based information.

[0411] A PM NF (Policy Management NF) (e.g., PCF) can transmit an updated RFSP index to a proxy NF. At this time, the PM NF (Policy Management NF) (e.g., PCF) can send an event notification regarding the event subscription of step 3 to the proxy NF (if the conditions for the event regarding the event subscription are satisfied). For example, the updated RFSP index can be transmitted through the event notification.

[0412] Proxy NF may store received information (e.g., event notification).

[0413] 11) step 11

[0414] In order to transmit data and for the terminal to enter a connected state, the terminal may send a service request message to an MM NF (or proxy NF) (e.g., 6G AMF).

[0415] At this time, the terminal may include information requesting user plane activation for a PDU session for transmitting data in the service request message.

[0416] 12-18) Steps 11 to 18

[0417] Steps 12 to 18 can be performed as steps 11 to 17 of the first embodiment (Figs. 11 and 12).

[0418] The MM NF in steps 11 to 17 of the first embodiment (Figs. 11 and 12) can be replaced with a proxy NF (or MM NF + proxy NF).

[0419] 19) step 19

[0420] Proxy NF can recognize that the terminal has become connected. For example, based on receiving the message of step 18, proxy NF can recognize that the terminal has become connected.

[0421] Based on this, the proxy NF can transmit the event notification sent by the PM NF (Policy Management NF) (e.g., PCF) in step 10 to the base station.

[0422] Instead of Step 19 being performed, when the MM NF (or proxy NF) (e.g., 6G AMF) transmits the UE context to the base station in Step 14, it may also transmit an updated RFSP index (including event notifications for events).

[0423] Through the disclosure of this specification, event subscription / notify between the base station and the core network NF can be efficiently supported without signaling overhead even when the idle / connected state / mode of the terminal changes.

[0424] In accordance with the disclosure of the present specification, the following operations may be performed:

[0425] - If the base station needs to send the terminal to an idle state while it has information about event subscriptions, the base station may request the core network node to save the event subscription information. Based on this, the core network node can store the saved information in the terminal context and then transmit the event subscription information back to the base station when the terminal becomes connected.

[0426] - If a base station needs to receive event notifications about a terminal from the core network, the base station can subscribe to the events through a proxy NF. When the terminal is in an idle state, the core network can send event notifications to the proxy NF. The proxy NF can store the event notifications and send them to the base station when the terminal becomes connected.

[0427] The following drawings are made to illustrate a specific example of the present specification. The names of specific devices or specific signals / messages / fields described in the drawings are presented as examples, and therefore the technical features of the present specification are not limited to the specific names used in the following drawings.

[0428] FIG. 15 illustrates the procedure of the mobility NF for the disclosure of the present specification.

[0429] 1. A mobility-related Network Function (NF) can receive information related to an event subscription for a User Equipment (UE) from a base station and a request to store said information.

[0430] 2. Based on the above storage request, the mobility-related NF can store information related to the event subscription.

[0431] 3. The above mobility-related NF can receive a service request from the above UE.

[0432] 4. Based on the above service request, the mobility-related NF may transmit information related to the event subscription to the base station.

[0433] The above mobility-related NF can receive event notifications regarding the event subscription from other NFs.

[0434] Based on the above service request, the above mobility-related NF can transmit the above event notification to the base station.

[0435] The step of transmitting information related to the above event subscription may include: based on the above service request, the mobility-related NF transmitting a request to the base station to create a context for the UE.

[0436] The above mobility-related NF can receive a notification message from the base station.

[0437] The above notification message may include information that the UE needs to be released.

[0438] The above mobility-related NF may be an AMF (Access and Mobility management Function).

[0439] The following drawings are made to illustrate a specific example of the present specification. The names of specific devices or specific signals / messages / fields described in the drawings are presented as examples, and therefore the technical features of the present specification are not limited to the specific names used in the following drawings.

[0440] FIG. 16 illustrates the procedure of a base station for the disclosure of the present specification.

[0441] 1. The base station can perform event subscriptions for the UE to the network.

[0442] 2. The base station may receive a request to delete the context for the UE from a mobility-related NF of the network.

[0443] 3. The base station may disconnect the AN (Access Network) connection with the UE.

[0444] 4. The base station may transmit information related to the event subscription and a request to store the information to the mobility-related NF.

[0445] 5. Based on the above deletion request, the base station may delete information related to the event subscription and the context of the UE.

[0446] 6. The base station may receive a request to create the context of the UE from the mobility-related NF.

[0447] The above creation request may include information related to the above event subscription.

[0448] The base station can receive an event notification regarding the event subscription from the mobility-related NF.

[0449] The above event notification may have occurred after the above AN connection was disconnected.

[0450] The base station can determine that there is no data from the UE for a specific period of time.

[0451] Based on the above decision, the base station may send a notification message to the mobility-related NF.

[0452] The above notification message may include information that the UE needs to be disconnected.

[0453] The above mobility-related NF may be an AMF.

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

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

[0456] For example, the processor can be configured to be operablely coupled with memory and the processor.

[0457] The operation performed by the above processor may include: a step in which a mobility-related NF (Network Function) receives information related to an event subscription for a UE (User Equipment) and a request to store said information from a base station; a step in which, based on said storage request, the mobility-related NF stores the information related to said event subscription; a step in which the mobility-related NF receives a service request from said UE; and a step in which, based on said service request, the mobility-related NF transmits the information related to said event subscription to the base station.

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

[0459] The operation performed by the above processor may include: a step in which a mobility-related NF (Network Function) receives information related to an event subscription for a UE (User Equipment) and a request to store said information from a base station; a step in which, based on said storage request, the mobility-related NF stores the information related to said event subscription; a step in which the mobility-related NF receives a service request from said UE; and a step in which, based on said service request, the mobility-related NF transmits the information related to said event subscription to the base station.

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

[0461] According to some embodiments of the present disclosure, the technical features of the present disclosure may be directly implemented in hardware, software executed by a processor, or a combination of both. 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, 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.

[0462] In some examples, storage media are coupled to the processor so that the processor can read information from the storage media. Alternatively, the storage media can be integrated into the processor. The processor and storage media can reside in an ASIC. In other examples, the processor and storage media can reside as separate components.

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

[0464] For example, non-volatile computer-readable media may include RAM (Random Access Memory) such as SDRAM (Synchronization Dynamic Random Access Memory), ROM (Read-Only Memory), and NVRAM (Non-Volatile Random Access Memory); read-only memory (EEPROM); flash memory; magnetic or optical data storage media; or other media that can be used to store instructions or data structures. Non-volatile computer-readable media may also include combinations of the above.

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

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

[0467] One or more stored commands may include the steps of: a mobility-related Network Function (NF) receiving from a base station information related to an event subscription for a User Equipment (UE) and a request to store said information; based on said storage request, the mobility-related NF storing said information related to the event subscription; the mobility-related NF receiving a service request from said UE; and based on said service request, the mobility-related NF transmitting said information related to the event subscription to the base station.

[0468] This specification may have various effects.

[0469] For example, through the procedure disclosed in this specification, if the terminal becomes idle after an event subscription is performed, the problem of the event subscription being performed again after the terminal becomes connected is resolved.

[0470] The effects obtainable through the specific examples of this specification are not limited to those listed above. For example, there may be various technical effects that a person with ordinary skill in the related art can understand or derive 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.

[0471] The claims described in this specification may be combined in various ways. For example, the technical features of the method claims in this specification may be combined to be implemented as a device, and the technical features of the device claims in this specification may be combined to be implemented as a method. Furthermore, the technical features of the method claims and the technical features of the device claims in this specification may be combined to be implemented as a device, and the technical features of the method claims and the technical features of the device claims in this specification may be combined to be implemented as a method. Other implementations are within the scope of the following claims.

Claims

1. As a method, A step in which a mobility-related NF (Network Function) receives information related to an event subscription for a UE (User Equipment) and a request to store said information from a base station; Based on the above storage request, the step of the mobility-related NF storing information related to the event subscription; The step of the above mobility-related NF receiving a service request from the UE; and A method comprising the step of, based on the above service request, transmitting information related to the event subscription to the base station by the mobility-related NF.

2. In Paragraph 1, The step of the above mobility-related NF receiving an event notification regarding the event subscription from another NF; and A method further comprising the step of the mobility-related NF transmitting the event notification to the base station based on the above service request.

3. In Paragraph 1 or 2, A method comprising the step of transmitting information related to the above event subscription, wherein, based on the above service request, the mobility-related NF transmits a request to the base station to create a context for the UE.

4. In any one of paragraphs 1 through 3, The above mobility-related NF further includes the step of receiving a notification message from the base station, and A method in which the above notification message includes information that the above UE needs to be released.

5. In any one of paragraphs 1 through 4, The above mobility-related NF is a method in which it is an AMF (Access and Mobility management Function).

6. As a method, Step of the base station performing event subscription for the UE to the network; The step of the base station receiving a request to delete the context for the UE from a mobility-related NF of the network; A step in which the base station disconnects the AN (Access Network) connection with the UE; The step of the base station transmitting information related to the event subscription and a request to store the information to the mobility-related NF; Based on the above deletion request, the base station deletes information related to the event subscription and the context of the UE; and The step of the base station receiving a request to create the context of the UE from the mobility-related NF; The above creation request is a method that includes information related to the above event subscription.

7. In Paragraph 8, The above base station further includes the step of receiving an event notification for the event subscription from the above mobility-related NF, and A method in which the above event notification occurs after the above AN connection is disconnected.

8. In Paragraph 6 or 7, A step in which the base station determines that there is no data from the UE for a specific period of time; Based on the above decision, the method further includes the step of the base station transmitting a notification message to the mobility-related NF. A method comprising the above notification message including information that the above UE needs to be disconnected.

9. In any one of paragraphs 6 through 8, The above mobility-related NF is a method that is an AMF.

10. As a mobility-related NF that performs communication, At least one transmitter / receiver; It includes at least one processor, The operation performed by the above at least one processor is a mobility-related NF that is a method according to any one of claims 1 to 5.

11. As a base station performing communication, At least one transmitter / receiver; It includes at least one processor, The operation performed by the above-mentioned at least one processor is a base station that is a method according to any one of claims 6 to 9.

12. As an apparatus in mobile communication, At least one processor; and It includes at least one memory that stores instructions and is operablely electrically connected to at least one processor, and A device in which the operation performed based on the execution of the above instruction by the at least one processor is a method according to any one of claims 1 to 5.

13. A non-volatile computer-readable storage medium that records instructions, A non-volatile computer-readable storage medium that, when the above instructions are executed by one or more processors, causes the one or more processors to perform a method according to any one of claims 1 to 5.

Images