Local offloading management based on service area

Abstract

A method and an apparatus related to service area-based local offloading management are provided. An access and mobility management node generates local offloading management service area information for each user equipment (UE). The local offloading management service area information includes, on a tracking area (TA) basis, an allowed area in which local offloading management is allowed and a non-allowed area in which local offloading management is not allowed. The access and mobility management node determines whether the local offloading management is supported for a UE on the basis of the generated local offloading management service area information, and on the basis that the local offloading management is determined to be supported, selects an intermediate session management node for a session of the UE.

Description

Service Area-Based Local Offloading Management

[0001] The present disclosure relates to service area-based local offloading management.

[0002] 3GPP (3rd Generation Partnership Project) New Radio (NR) targets a single technical framework that addresses all deployment, use, and requirements, including enhanced Mobile Broadband (eMBB), massive Machine Type Communications (mmTC), and Ultra-Reliable and Low Latency Communications (URLLC). Additionally, NR must be able to utilize any spectrum band up to at least 100 GHz that can be used for wireless communication in the distant future. NR must be inherently forward compatible.

[0003] In a 5G network environment, edge computing is attracting attention as a technology for minimizing service latency and efficiently processing network traffic by deploying computing resources in locations physically close to User Equipment (UEs) or users. To support this, 3GPP standards define mechanisms such as Local Area Data Network (LADN), Uplink Classifier (ULCL), and Branching Point (BP), and Session Management Function (SMF), which manages Protocol Data Unit (PDU) sessions of UEs within the network, plays a key role in managing sessions related to edge computing.

[0004] 6G is the successor to 5G cellular technology. 6G networks can utilize higher frequencies than 5G networks and will provide significantly higher capacity and much lower latency. The 6G technology market is expected to drive massive improvements in imaging, presence technology, and location awareness. Working in conjunction with Artificial Intelligence (AI), 6G computing infrastructure will be able to identify the best places for computing to occur. This includes decisions regarding data storage, processing, and sharing.

[0005] The introduction of Local Offloading Management (LOM) functionality was discussed for the purpose of making edge computing support more efficient. The LOM function aims to distribute the processing load related to edge computing, which was previously concentrated on the Anchor SMF (A-SMF), by selecting and / or adding an Intermediate SMF (I-SMF), a separate SMF dedicated to edge computing support, to the UE's PDU session.

[0006] Specifically, the selection and addition of I-SMFs based on LOM functions may be determined within the UE PDU session establishment and / or handover procedures received from the Access and Mobility Management Function (AMF), based on subscriber information (e.g., LOM allowance information by DNN (Data Network Name) / S-NSSAI (Single Network Slice Selection Assistance Information)) and / or whether the UE's location is included within a pre-configured LOM Service Area (SA) within each AMF and / or SMF.

[0007] However, the same SMF may be selected to operate as an A-SMF for a specific UE's PDU session and as an I-SMF for another UE's PDU session, depending on network operation and deployment scenarios. In such an environment where a single SMF simultaneously performs both A-SMF and I-SMF roles for multiple UEs, signaling for processing management data, making decisions, and providing notifications for edge computing support may become concentrated on a specific SMF depending on the UE's mobility. In other words, even though the LOM function introduced an I-SMF to balance the load of the A-SMF, a problem may arise where the load is re-concentrated on a specific I-SMF.

[0008] Furthermore, if decisions regarding the selection, addition, and / or modification of I-SMFs are based solely on statically configured information—such as the UE's current location, LOM SA information pre-configured or fixed in each SMF, and / or SMF-related information cached within the AMF—they may fail to reflect dynamic changes in network conditions, such as real-time UE movement patterns, changes in UE density within a specific region, and the current processing load status of each SMF. Consequently, decisions regarding the selection, addition, and / or modification of I-SMFs may not be optimized, leading to a problem where the load associated with edge computing support across SMFs is not efficiently distributed.

[0009] In addition, if the load is concentrated on a specific SMF, the processing performance of that SMF may be degraded, and the Quality of Service (QoS) of edge computing services may not be guaranteed, and furthermore, it may affect the service stability of the entire 5G network.

[0010] Therefore, a method and device are required to more efficiently determine the selection, addition, and / or change of I-SMFs for LOM functions by reflecting the real-time load status of each SMF within the network and dynamically changing network conditions.

[0011] In one embodiment, a method is provided that is performed by a connection and mobility management node. The method includes the step of generating local offloading management service area information for each user equipment (UE). The local offloading management service area information includes an allowed area and a non-allowed area for local offloading management on a tracking area basis. The method includes the step of determining whether local offloading management is supported for a UE based on the generated local offloading management service area information, and the step of selecting an intermediate session management node for a session of the UE based on the determination that local offloading management is supported.

[0012] In one embodiment, a connectivity and mobility management node is provided. The connectivity and mobility management node includes at least one processor and at least one memory that can be operably connected to the at least one processor and stores instructions that cause the connectivity and mobility management node to perform an operation based on execution by the at least one processor. The operation includes the step of generating local offloading management service area information for each UE. The local offloading management service area information includes areas where local offloading management is allowed and areas where it is not allowed on a tracking area basis. The operation includes the step of determining whether local offloading management is supported for a UE based on the generated local offloading management service area information, and the step of selecting an intermediate session management node for the UE's session based on the determination that local offloading management is supported.

[0013] The present disclosure may have various effects.

[0014] For example, even if an LOM SA is not pre-configured in the network, the AMF can efficiently support LOM. In other words, by configuring and / or managing LOM SAs by dynamically reflecting UE mobility patterns and the real-time load conditions of each SMF, rather than relying on statically fixed LOM SA settings, the LOM function can be flexibly applied across various network operating environments and deployment scenarios.

[0015] For example, the load resulting from edge computing support of each SMF can be efficiently distributed from an overall network perspective. That is, the load among SMFs can be balanced through decisions regarding the selection, addition, and / or modification of I-SMFs that reflect dynamically changing network conditions. This prevents QoS degradation caused by overloading of specific SMFs and improves the stability and reliability of the 5G network as a whole.

[0016] For example, network resources can be utilized efficiently by minimizing unnecessary signaling and procedures related to LOM support. In other words, network resource consumption can be reduced by decreasing unnecessary procedures and signaling through optimized LOM SA configuration / management and / or LOM support decisions based thereon.

[0017] The effects obtainable through the specific examples of the present disclosure are not limited to those listed above. For example, there may be various technical effects that a person having ordinary skill in the related art can understand or derive from the present disclosure. Accordingly, the specific effects of the present disclosure are not limited to those explicitly described in the present disclosure, but may include various effects that can be understood or derived from the technical features of the present disclosure.

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

[0019] FIG. 2 shows an example of a wireless device to which an implementation of the present disclosure is applied.

[0020] FIG. 3 shows an example of a UE to which an implementation of the present disclosure is applied.

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

[0022] FIGS. 5 and FIGS. 6 illustrate examples of registration procedures to which an implementation of the present disclosure applies.

[0023] FIGS. 7 and FIGS. 8 illustrate examples of PDU session establishment procedures to which an implementation of the present disclosure is applied.

[0024] FIG. 9 shows an example of a 5G system structure that simultaneously uses an SMF and an I-SMF to which an implementation of the present disclosure is applied.

[0025] FIG. 10 illustrates an example of a method to which an implementation of the present disclosure is applied.

[0026] FIG. 11 shows an example of a PDU session establishment procedure that supports an LOM to which the first implementation of the present disclosure applies.

[0027] FIG. 12 illustrates an example of a procedure for managing an analysis information-based LOM service area to which the first implementation of the present disclosure is applied.

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

[0029] For convenience of explanation, the implementation of the present disclosure is described primarily in relation to 3GPP-based wireless communication systems. However, the technical characteristics of the present disclosure 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 the present disclosure that are not limited to 3GPP-based wireless communication systems may be applied to other mobile communication systems.

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

[0031] In the present disclosure, "A or B" may mean "only A," "only B," or "both A and B." Alternatively, in the present disclosure, "A or B" may be interpreted as "A and / or B." For example, in the present disclosure, "A, B or C" may mean "only A," "only B," "only C," or "any combination of A, B and C."

[0032] A slash ( / ) or a comma used in the present disclosure 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."

[0033] In the present disclosure, "at least one of A and B" may mean "only A," "only B," or "both A and B." Additionally, in the present disclosure, 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."

[0034] Additionally, in the present disclosure, "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."

[0035] Additionally, parentheses used in the present disclosure may mean "for example." Specifically, when indicated as "control information (PDCCH)," "PDCCH" may be proposed as an example of "control information." In other words, the "control information" of the present disclosure 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."

[0036] Technical features described individually within one drawing in this disclosure may be implemented individually or simultaneously.

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

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

[0039] The present disclosure describes embodiments based on the structure, procedures, messages, etc. of a 5G mobile communication system. However, this is merely an example, and the embodiments of the present disclosure are not limited thereto. For example, the embodiments of the present disclosure can be extended to apply to an evolved form of a 6G mobile communication system. For example, the 5G-based messages described in the embodiments of the present disclosure may be defined as other existing messages, new messages, or parameters.

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

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

[0042] The three main requirement 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.

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

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

[0045] 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), Internet-Of-Things (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 (Augmented Reality) / VR (Virtual Reality) / MR (Mixed Reality) devices and may be implemented in the form of HMDs (Head-Mounted Devices) and HUDs (Head-Up Displays) 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.

[0046] In the present disclosure, 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.

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

[0048] 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 of the present disclosure, 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.

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

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

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

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

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

[0054] Here, the wireless communication technology implemented in the wireless device of the present disclosure 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 the present disclosure 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 eMTC (enhanced MTC). 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 the present disclosure 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.

[0055] FIG. 2 shows an example of a wireless device to which an implementation of the present disclosure is applied.

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

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

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

[0059] The processor (102) can control the memory (104) and / or the transceiver (106) and may be configured to implement the description, function, procedure, proposal, method and / or operation flowchart disclosed in this disclosure. 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).

[0060] 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 a set of instructions that perform the descriptions, functions, procedures, suggestions, methods, and / or operation flowcharts disclosed in this disclosure when executed by the processor (102). For example, the firmware and / or software code (105) may implement instructions that perform the descriptions, functions, procedures, suggestions, methods, and / or operation flowcharts disclosed in this disclosure when executed by the processor (102). For example, the firmware and / or software code (105) may control the processor (102) to perform one or more protocols. For example, the firmware and / or software code (105) may control the processor (102) to perform one or more wireless interface protocol layers.

[0061] 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 disclosure, the first wireless device (100) may represent a communication modem / circuit / chip.

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

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

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

[0065] 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 code, instructions, and / or a set of instructions that perform the descriptions, functions, procedures, suggestions, methods, and / or operation flowcharts disclosed in this disclosure when executed by the processor (202). For example, the firmware and / or software code (205) may implement instructions that perform the descriptions, functions, procedures, suggestions, methods, and / or operation flowcharts disclosed in this disclosure when executed by the processor (202). For example, the firmware and / or software code (205) may control the processor (202) to perform one or more protocols. For example, the firmware and / or software code (205) may control the processor (202) to perform one or more wireless interface protocol layers.

[0066] 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 disclosure, the second wireless device (200) may represent a communication modem / circuit / chip.

[0067] 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, an RLC (Radio Link Control) layer, a PDCP (Packet Data Convergence Protocol) layer, an 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 disclosure. 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 the present disclosure 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 the present disclosure.

[0068] 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. 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 be composed of Random Access Memory (RAM), Dynamic RAM (DRAM), Read-Only Memory (ROM), Erasable Programmable ROM (EPROM), flash memory, volatile memory, non-volatile memory, hard drive, register, 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.

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

[0070] 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., mentioned in the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this disclosure through one or more antennas (108, 208). In this disclosure, one or more antennas (108, 208) may be a plurality of physical antennas or a plurality of logical antennas (e.g., antenna ports).

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

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

[0073] In an embodiment of the present disclosure, the UE may operate as a transmitting device in the uplink and as a receiving device in the downlink. In an embodiment of the present disclosure, 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 embodiment of the present disclosure or to control a transceiver (106) to perform UE operations according to an embodiment of the present disclosure. 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 embodiment of the present disclosure or to control a transceiver (206) to perform base station operations according to an embodiment of the present disclosure.

[0074] In the present disclosure, the base station may be referred to as Node B, eNode B, or gNB.

[0075] FIG. 3 shows an example of a UE to which an implementation of the present disclosure is applied.

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

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

[0078] The processor (102) may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this disclosure. 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 in this disclosure. 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.

[0079] 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 in this disclosure. 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.

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

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

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

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

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

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

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

[0087] - AUSF (Authentication Server Function)

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

[0089] - DN (Data Network), for example, operator services, internet access, or third-party services

[0090] - USDF (Unstructured Data Storage Function)

[0091] - NEF (Network Exposure Function)

[0092] - I-NEF (Intermediate NEF)

[0093] - NRF (Network Repository Function)

[0094] - NSSF (Network Slice Selection Function)

[0095] - PCF (Policy Control Function)

[0096] - SMF (Session Management Function)

[0097] - UDM (Unified Data Management)

[0098] - UDR (Unified Data Repository)

[0099] - UPF (User Plane Function)

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

[0101] - AF (Application Function)

[0102] - UE (User Equipment)

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

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

[0105] - NWDAF (Network Data Analytics Function)

[0106] - CHF (CHarging Function)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0131] - 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)

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

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

[0134] Explain the registration procedure.

[0135] FIGS. 5 and FIGS. 6 illustrate examples of registration procedures to which an implementation of the present disclosure applies.

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

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

[0138] - Mobility registration update; or

[0139] - Periodic registration update; or

[0140] - Emergency registration

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

[0142] The general registration procedure of Figures 5 and 6 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0158] 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, where available.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0174] Now, the procedure of Fig. 6 following the procedure of Fig. 5 is explained.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0192] This explains the procedure for establishing a PDU session.

[0193] FIGS. 7 and FIGS. 8 illustrate examples of PDU session establishment procedures to which an implementation of the present disclosure is applied.

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

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

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

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

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

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

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

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

[0202] First, the procedure of Fig. 7 will be explained.

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

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

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

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

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

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

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

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

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

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

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

[0214] AMF rejects requests from urgently registered UEs where the request type does not indicate "urgent request" or "existing urgent PDU session".

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0239] - RSN (redundancy sequence number) parameter

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

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

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

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

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

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

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

[0247] The procedure of Fig. 8 following the procedure of Fig. 7 is described.

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

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

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

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

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

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

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

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

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

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

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

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

[0260] Edge computing enables efficient service delivery by hosting operator and third-party services at locations close to the UE's access point, thereby reducing end-to-end latency and transmission network load.

[0261] The 5G core network can select a UPF located close to the UE and forward traffic according to traffic steering rules provided to the UPF to enable local access to the Data Network (DN) through the N6 interface. This may be based on the UE's subscriber data, UE location, information from the AF, EAS information reported from the Edge Application Server Discovery Function (EASDF), policies, or other relevant traffic rules.

[0262] Due to the mobility of the user or AF, service or session continuity may be required depending on the requirements of the service or 5G network.

[0263] The 5G core network can expose network information and functions to edge computing AF.

[0264] Edge computing can be supported by one or a combination of the following functional elements.

[0265] - User Plane (Re)selection: The 5G core network (re)selects a UPF to route user traffic to the local area of ​​the DN.

[0266] - Local Routing and Traffic Steering: The 5G core network selects traffic to be routed to applications within the local area of ​​the DN. This may include the use of a single PDU session containing multiple PDU session anchors (UL CL (Classifier) ​​ / IPv6 multi-homing) and the utilization of PDU sessions using distributed anchor points with SSC mode 2 / 3;

[0267] - Session and service continuity to support UE and application mobility;

[0268] - Affects AF's UPF (re)selection and traffic routing via PCF or NEF;

[0269] - Network Function Exposure: The 5G core network and AF provide mutual information via the NEF, directly, or from the UPF;

[0270] - QoS and Billing: PCF provides QoS control and billing rules for traffic routed to the DN's local zone;

[0271] - LADN (Local Area Data Network) Support: The 5G core network provides support for accessing LADN within a specific area where applications are deployed;

[0272] - Discovery and re-discovery of edge application servers;

[0273] - Support for cases involving edge relocation and AF changes, and support for edge relocation triggered by 5GC within the Edge Hosting Environment (EHE) of the same hosting PLMN;

[0274] - Support for DNAI (Data Network Access Identifier)-based (I-)SMF (re)selection;

[0275] - Support for granular UE sets;

[0276] - Support for common EAS exploration and common DNAI determination for UE sets;

[0277] - Support for mapping information between EAS IP / IP ranges and DNAI;

[0278] - Support for AF requests for DNAI.

[0279] To support edge computing more efficiently, the introduction of Local Offloading Management (LOM) functionality is being discussed. Since the load may be concentrated on the anchor SMF (A-SMF) due to increased signaling for management data and / or processing / decision / notification within the 5G core network for edge computing support, an intermediate SMF (I-SMF), which is a separate dedicated SMF responsible for edge computing support functions, is selected / configured to resolve / prevent these problems, and edge computing-related functions can be delegated to the I-SMF.

[0280] Depending on the LOM function, an I-SMF may be selected and / or added to a UE's PDU session related to edge computing. The selection and / or addition of a separate I-SMF for LOM support to a UE's PDU session may be determined within the procedure for establishing the UE's PDU session from the AMF and / or the handover procedure, based on subscriber information (e.g., LOM permission information by DNN / S-NSSAI), whether the UE's location is included within a pre-configured LOM Service Area (SA) within each AMF and / or SMF, etc.

[0281] More specifically, in an edge computing deployment environment, 5GS can support LOM to reduce the load impact caused by a centrally deployed SMF managing edge computing-related information.

[0282] In distributed anchor point and multiple PDU session connection models, LOM can be supported by utilizing means such as URSP (UE Route Selection Policy) and SSC mode.

[0283] In the session breakout connection model, LOM may be applied only to non-roaming PDU sessions. In the session breakout connection model, if the AMF determines that the UE is located within the LOM service area and that LOM is allowed in the SMF selected subscriber data, the AMF may select / re-select an I-SMF to support LOM. This may also include cases where the UE is located within the SMF service area. For LOM, the I-SMF is responsible for edge computing processing and can support the following functions.

[0284] - EASDF configuration and DNS (Domain Name System) message processing instead of SMF.

[0285] - I-SMF performs EASDF search and selection instead of SMF.

[0286] - Management and retrieval of EDI (Edge Data Information) from NEF

[0287] - Receive local offloading information via SMF indicating IP ranges and / or Fully Qualified Domain Names (FQDNs) allowed to be routed from PCF to the local area of ​​the DN.

[0288] If an I-SMF is inserted for the LOM, that is, if the inserted I-SMF provides an indication to the SMF to allow local offloading, the SMF may not perform EASDF discovery, selection, and / or configuration and DNS message processing for local offloading traffic toward the local DN.

[0289] The UE may not be aware of whether LOM has been applied to its PDU session.

[0290] If a UE is located within a LOM service area, support for the LOM function may be determined, and for this purpose, information related to the LOM service area may be pre-configured in the AMF and / or SMF. Information related to the LOM service area may be configured manually and / or statically. More specifically, when an AMF selects an SMF that supports a LOM service area including the UE's location for the selection of an I-SMF for LOM support, specific LOM service area information including the region may be pre-configured in each SMF, taking into account the service area supported by the SMF, so that it is registered in the NF profile.

[0291] More specifically, if LOM is allowed based on SMF selected subscriber data and the UE is located within the LOM service area, an I-SMF supporting LOM can be inserted between the SMF and the AMF, even if the UE is within the SMF service area. The LOM service area can be locally configured within the AMF by S-NSSAI and DNN, or can be created within the AMF based on the I-SMF profile received from the NRF.

[0292] An I-SMF profile may include LOM service areas supported by the I-SMF.

[0293] When an I-SMF supporting LOM is inserted to manage edge computing information locally, EAS deployment information management, EASDF selection, configuration, and DNS message processing can be performed by the I-SMF.

[0294] A local offloading policy can represent IP ranges and / or FQDNs that are allowed to be routed to the local area of ​​the DN.

[0295] UL CL and UPF can be inserted, changed, or removed by I-SMF for traffic offloaded for LOM.

[0296] In the SMF search and selection procedure to find an I-SMF that supports LOM functionality, the AMF can perform a query procedure to the NRF based on the UE's location and / or, if pre-configured, the LOM service area within the AMF. The AMF can obtain information about candidate SMFs that support the UE's location and / or LOM service area. Additionally, to reduce the number of queries to the NRF for the SMF selection procedure whenever the UE moves to or connects to a new Tracking Area (TA), the AMF can cache and refer to the results of the NRF query.

[0297] More specifically, if LOM is allowed for the requested DNN / S-NSSAI, the AMF can search for SMF(s) that support LOM. The AMF can use the UE's current location as a query parameter during the search. For the discovered SMF(s), the AMF can perform the following:

[0298] - If the UE is not located within the LOM service area of ​​any of the candidate SMF(s), an I-SMF for the LOM may not be required.

[0299] - If the UE is located within the LOM service area of ​​one or more of the candidate SMF(s), the AMF can select an I-SMF for LOM that supports the corresponding LOM service area.

[0300] When AMF utilizes the SMF's NF profile to determine whether LOM applies to a UE's location, AMF can cache the results of the NRF query. This minimizes the need for AMF to perform a query every time a UE enters a new TA, which can be particularly useful when LOM was not applied in the previous TA.

[0301] AMF can have a configured LOM service area.

[0302] FIG. 9 shows an example of a 5G system structure that simultaneously uses an SMF and an I-SMF to which an implementation of the present disclosure is applied.

[0303] Referring to FIG. 9, an I-SMF can be inserted between the AMF and the SMF. The conventional SMF can be represented as an A-SMF. The I-SMF and the (A-)SMF can manage a single PDU session of the UE. The service area managed by the conventional (A-)SMF can be represented simply as a service area, and the service area managed by the I-SMF can be represented as a LOM service area.

[0304] Based on the insertion of I-SMF, the following reference points show the interactions that exist between the NF services of the NF.

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

[0306] - N16a: Reference point between I-SMF and SMF

[0307] - N38: Reference point between two I-SMFs

[0308] As described above, two SMFs, A-SMF and I-SMF, can be selected for a UE's PDU session. In the SMF selection procedure, the operation supported by a specific SMF (i.e., whether to operate as A-SMF or I-SMF) can be determined based on the UE's location and / or the SMF search and selection procedure described above.

[0309] Depending on 5G network operation and deployment scenarios, a single SMF may be selected to operate as an A-SMF for a specific UE's PDU session and as an I-SMF for another UE's PDU session. In other words, the same SMF can handle multiple PDU sessions from multiple UEs and operate as either an A-SMF or an I-SMF. In this case, although the original purpose of LOM support is to distribute the load of a centralized A-SMF, signaling overhead for managing data and processing / decisions / notifications for edge computing support may increase in a specific SMF depending on the UE's mobility.

[0310] More specifically, as described above, if the selection, addition, or modification of I-SMFs is determined based solely on static information, such as the UE's current location and / or pre-configured / fixed LOM service areas for each SMF and / or cached SMF-related information within the AMF, the load associated with SMF edge computing support may not be efficiently distributed. For example, when selecting and / or adding I-SMFs for LOM support, the dynamically changing load conditions of A-SMFs and candidate SMFs may not be considered. Consequently, frequent insertion, modification, or removal of I-SMFs may occur depending on UE mobility, and signaling overhead may increase due to unnecessary selection / removal of I-SMFs, UPFs, and EASDFs, as well as / or DNS context setup / unset procedures.

[0311] To solve the aforementioned problems, according to an implementation of the present disclosure, a method may be proposed to efficiently utilize SMF resources and reduce unnecessary signaling and procedures by preventing the load from being concentrated on a specific SMF in advance. For example, according to an implementation of the present disclosure, a method for setting and managing LOM service areas considering UE mobility patterns, dynamically changing SMF load conditions, etc., and / or a method for determining whether to support LOM based thereon may be proposed. The method proposed in the present disclosure may be applied even when an LOM service area within a 5G network is not pre-configured.

[0312] According to a first embodiment of the present disclosure, a method for setting and managing a LOM service area within an AMF may be proposed for determining an I-SMF that supports LOM functions in a UE based on the LOM service area and / or a PDU session.

[0313] For example, according to the first embodiment of the present disclosure, an AMF may create, store, and manage separate LOM service areas per UE for LOM support. An AMF may create, store, and manage separate LOM service areas per UE as a subset of the entire available LOM service area pre-configured within the network. Alternatively, even if there is no pre-configured LOM service area information within the network, an AMF may create, store, and manage separate LOM service areas per UE independently by selectively considering the service areas of the SMF(s) that support LOM. An AMF may create, store, and manage separate LOM service areas per UE according to the procedure of an NRF inquiry, taking into account the mobility of the UE.

[0314] For example, according to a first embodiment of the present disclosure, an AMF may determine whether to support LOM and / or to add / change / remove I-SMFs that support LOM functions based on the LOM service area for a UE connecting to the said AMF.

[0315] For example, according to a first embodiment of the present disclosure, an AMF may set / configure an LOM allowed area and a LOM non-allowed area within LOM service area information. The LOM allowed area information and the LOM non-allowed area information may be mutually exclusive. An AMF may sort TAI lists in order of priority for each of the LOM allowed area and the LOM non-allowed area.

[0316] For example, according to a first embodiment of the present disclosure, an AMF can dynamically manage / update LOM allowed area and / or LOM non-allowed area information within a LOM service area based on at least one NWDAF analysis information, such as UE mobility analytics and / or NF load analytics for an SMF.

[0317] According to a second embodiment of the present disclosure, a method for determining and controlling LOM support based on LOM allowed areas and LOM non-allowed areas may be proposed for determining LOM support of a UE based on LOM service areas and / or an I-SMF supporting LOM functions in a PDU session.

[0318] For example, according to a second embodiment of the present disclosure, the AMF may determine whether to support LOM for a UE's PDU session based on the LOM allowed area and LOM non-allowed area that can be established by the first embodiment of the present disclosure, rather than a LOM service area pre-established in a conventional network, and the UE's current location.

[0319] For example, according to a second embodiment of the present disclosure, the AMF may determine not to support LOM for UEs located in the area by setting the service area and / or LOM service area of ​​the A-SMF, which has a low load according to the NF load analysis information of the A-SMF, as a LOM non-allowed area. For example, when the load of the A-SMF is high, the AMF may determine to support LOM for UEs located in the area by setting and / or updating the service area and / or LOM service area of ​​the A-SMF as a LOM allowed area.

[0320] For example, according to a second embodiment of the present disclosure, an AMF may transmit LOM allowed area and LOM non-allowed area information that is dynamically updated / managed according to UE mobility analysis information, so that a target AMF can refer to it as initial LOM service area information during a handover procedure.

[0321] According to an implementation of the present disclosure, LOM can be supported more efficiently than conventional LOM support scenarios, including cases where the LOM service area is not pre-configured in the network. Additionally, according to an implementation of the present disclosure, the load resulting from edge computing support for each SMF can be distributed across the entire network.

[0322] The I-SMF responsible for the LOM described in this disclosure is an SMF controlled to support different functions / roles in conjunction with the A-SMF, and can be described / defined as an I-SMF that performs functions other than the operation of the I-SMF defined in the conventional ETSUN (Enhancing Topology of SMF and UPF in 5G Networks) technology. For example, the I-SMF described in this disclosure may be an SMF that performs functions / operations to provide edge computing to the UE.

[0323] In the present disclosure, SMF may be a 5G SMF or a network function / entity responsible for session management functions in 6G (e.g., 6G SMF, SM NF, 6G SM NF). In the present disclosure, I-SMF may be a 5G I-SMF or a network function / entity responsible for session management functions related to edge computing in 6G (e.g., 6G I-SMF, I-SM NF, 6G I-SM NF). In the present disclosure, AMF may be a 5G AMF or a network function / entity responsible for access and mobility management in 6G (e.g., 6G AMF, AM NF, 6G AM NF). In the present disclosure, UPF may be a 5G UPF or a network function / entity responsible for the user plane in 6G (e.g., 6G UPF, UP NF, 6G UP NF). In the present disclosure, NWDAF may be a network function / entity responsible for network data analysis in 5G NWDAF or 6G (e.g., 6G NWDAF, NWDA NF, 6G NWDA NF).

[0324] In the present disclosure, procedures and / or messages may use conventional procedures and / or messages, or may use an extension of conventional procedures and / or messages, or may use new procedures and / or messages defined therein. For example, in the present disclosure, service operations between core network NFs may be at least one of service operations that existed in conventional 5G and / or service operations that will be newly defined in 6G.

[0325] In the methods and / or procedures described in this disclosure, multiple steps may be performed simultaneously and / or in parallel. In the methods and / or procedures described in this disclosure, multiple steps may be performed in a different order than that described in the drawings. In the methods and / or procedures described in this disclosure, some steps may be omitted without loss of generality. The methods and / or procedures described in this disclosure may be performed or used in combination or complementarily.

[0326] The names of information, indications, and / or parameters described in this disclosure are merely illustrative. The names of information, indications, and / or parameters described in this disclosure may be replaced with other names or interpreted as such for the procedures, purposes, and methods proposed in this disclosure.

[0327] The following drawings are made to illustrate a specific example of the present disclosure. 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 disclosure are not limited to the specific names used in the following drawings.

[0328] FIG. 10 illustrates an example of a method to which an implementation of the present disclosure is applied.

[0329] FIG. 10 can be performed by an access and mobility management node. The access and mobility management node may be a network function / entity responsible for access and mobility management in 5G AMF or 6G (e.g., 6G AMF, AM NF, 6G AM NF).

[0330] In step S1000, the method includes the step of generating local offloading management service area information for each UE. The local offloading management service area information includes an allowed area and a non-allowed area for local offloading management on a tracking area basis.

[0331] In some implementations, the local offloading management service area information may be generated based on a subset of all available local offloading service areas pre-configured within the network.

[0332] In some implementations, the local offloading management service area information may be generated based on the service area of ​​at least one session management node supporting the local offloading management if there is no pre-configured local offloading management service area information within the network.

[0333] In some implementations, the local offloading management service area information may be generated based on at least one of the current location of the UE or the mobility pattern of the UE in a list of TAs.

[0334] In some implementations, the method may further include the step of updating the local offloading management service area information.

[0335] In some implementations, the local offloading management service area information may be generated or updated based on analysis information obtained from a network data analysis node. The analysis information may include at least one of UE mobility analysis information or NF load analysis information.

[0336] In some implementations, based on the high load of the anchor session management node, the service area of ​​the anchor session management node may be included in the allowed area.

[0337] In some implementations, based on the fact that the load of the anchor session management node is not high, the service area of ​​the anchor session management node may be included in the aforementioned unallowed area.

[0338] In some implementations, the allowed area and the prohibited area may be mutually exclusive.

[0339] In some implementations, the allowed area and the prohibited area may each include a list of TAs according to priority.

[0340] In step S1010, the method includes the step of determining whether the local offloading management is supported for the UE based on the generated local offloading management service area information.

[0341] In some implementations, the local offloading management may be supported based on the UE being located in the allowed area.

[0342] In some implementations, it may be determined that local offloading management is not supported based on the fact that the UE is located in the aforementioned unallowed area.

[0343] In step S1020, the method includes the step of selecting an intermediate session management node for the UE's session based on the determination that the local offloading management is supported.

[0344] In some implementations, the local offloading management service area information may be transmitted to the target access and mobility management node of the handover.

[0345] Additionally, the method described in Fig. 10 in terms of the connection and mobility management node can be performed by the second wireless device (200) shown in Fig. 2.

[0346] A connectivity and mobility management node includes one or more processors and one or more memories that store instructions for the connectivity and mobility management node to perform the method described in FIG. 10 based on being connected to the one or more processors to be operable and executed by the at least one processor.

[0347] More specifically, the Access and Mobility Management node generates local offloading management service area information for each UE. The local offloading management service area information includes areas where local offloading management is allowed and areas where it is not allowed, on a tracking area basis.

[0348] In some implementations, the local offloading management service area information may be generated based on a subset of all available local offloading service areas pre-configured within the network.

[0349] In some implementations, the local offloading management service area information may be generated based on the service area of ​​at least one session management node supporting the local offloading management if there is no pre-configured local offloading management service area information within the network.

[0350] In some implementations, the local offloading management service area information may be generated based on at least one of the current location of the UE or the mobility pattern of the UE in a list of TAs.

[0351] In some implementations, the method may further include the step of updating the local offloading management service area information.

[0352] In some implementations, the local offloading management service area information may be generated or updated based on analysis information obtained from a network data analysis node. The analysis information may include at least one of UE mobility analysis information or NF load analysis information.

[0353] In some implementations, based on the high load of the anchor session management node, the service area of ​​the anchor session management node may be included in the allowed area.

[0354] In some implementations, based on the fact that the load of the anchor session management node is not high, the service area of ​​the anchor session management node may be included in the aforementioned unallowed area.

[0355] In some implementations, the allowed area and the prohibited area may be mutually exclusive.

[0356] In some implementations, the allowed area and the prohibited area may each include a list of TAs according to priority.

[0357] The connectivity and mobility management node determines whether to support the local offloading management for the UE based on the generated local offloading management service area information.

[0358] In some implementations, the local offloading management may be supported based on the UE being located in the allowed area.

[0359] In some implementations, it may be determined that local offloading management is not supported based on the fact that the UE is located in the aforementioned unallowed area.

[0360] Based on the determination that the above local offloading management is supported, the connectivity and mobility management node selects an intermediate session management node for the UE's session.

[0361] In some implementations, the local offloading management service area information may be transmitted to the target access and mobility management node of the handover.

[0362] The first and second embodiments of the present disclosure will be described in detail.

[0363] 1. First Implementation: Configuration and / or management of LOM service areas within AMF

[0364] According to a first embodiment of the present disclosure, an AMF may generate, store, and manage separate LOM service area information and utilize it to select an I-SMF for LOM support of a UE. The initial LOM service area information may be based on results obtained by querying an NRF according to a LOM service area pre-configured for the AMF and / or each SMF supporting LOM.

[0365] If there is no pre-configured LOM service area information within the network, the AMF can generate LOM service area information independently by selectively considering the service areas of specific SMFs. For example, the AMF can acquire / generate LOM service area information based on the service areas of each SMF that support the UE's movement path regions, taking into account the UE's mobility patterns. Additionally, even if there is no pre-configured LOM service area information for each SMF, if LOM capability is present as a result of an NRF query (i.e., if an SMF supporting LOM exists), the AMF can generate initial LOM service area information using a combination of the service areas of that SMF.

[0366] That is, the AMF can configure / create separate LOM service area information as a subset of the entire pre-configured available LOM service area within the network, or configure / create a separate LOM service area based on the service area of ​​at least one SMF that supports LOM. The configured / created separate LOM service area can be used in the same way to determine whether LOM is supported for UEs registered with the corresponding AMF.

[0367] FIG. 11 shows an example of a PDU session establishment procedure that supports an LOM to which the first implementation of the present disclosure applies.

[0368] In step S1100, a registration procedure may be performed. The registration procedure may follow the registration procedure described in FIGS. 5 and FIGS. During the registration procedure, the AMF may receive a DNN / S-NSSAI-specific LOM allowed indication from the UDM as part of the SMF selected subscriber data.

[0369] If LOM is allowed for the requested DNN / S-NSSAI, the AMF can search for SMF(s) that support LOM. The AMF may use the UE's current location as a query parameter during the search. To create and / or update LOM service areas within the AMF, the AMF may use a list of TAIs that consider the UE's current location and / or the UE's mobility patterns as a query parameter during the search. For the discovered SMF(s), the AMF can perform the following:

[0370] - If the UE is not located within the LOM service area of ​​any of the candidate SMF(s), an I-SMF for the LOM is not required, and step S1110 can be performed.

[0371] - If the UE is located within the LOM service area of ​​one or more of the candidate SMF(s), the AMF may select an I-SMF for LOM that supports the LOM service area, and step S1120 may be performed.

[0372] - If the LOM service area of ​​a candidate SMF is not configured, the AMF may consider the service area of ​​a candidate SMF that supports LOM as the LOM service area.

[0373] When AMF utilizes the SMF's NF profile to determine whether LOM applies to a UE's location, AMF can cache the results of the NRF query. This minimizes the need for AMF to perform a query every time a UE enters a new TA, which can be particularly useful when LOM was not applied in the previous TA.

[0374] AMF can have a configured LOM service area.

[0375] In step S1110, the SMF can select an EASDF and instruct the EASDF to create a DNS context for the PDU session.

[0376] In step S1120, the AMF services the UE location and the LOM service area and can select an I-SMF that supports LOM. If the I-SMF receives a LOM allow instruction from the AMF, the I-SMF can perform the following:

[0377] - Based on UE location information, UL CL / BP UPF and L-PSA (Local PDU Session Anchor) UPF can be selected.

[0378] - You can select EASDF.

[0379] - You can obtain an EASDF IP address based on local settings, or by calling a Neasdf_DNSContext_Create Request that includes a UE IP address configured with a DNN, S-NSSAI, and an unspecified or mapped address.

[0380] - EASDF DNS security information can be obtained based on local settings or through interaction with EASDF.

[0381] - Can transmit Nsmf_PDUSession_Create Request (LOM allow instruction, offload ID) (if available, e.g., by configuration), EASDF IP address and DNS security information (if present), and DNAI supported by I-SMF).

[0382] If the SMF receives a LOM allow instruction and allows the I-SMF to perform LOM based on SM subscriber data, the SMF may perform the following:

[0383] - EASDF search and selection procedures and DNS message processing can be omitted.

[0384] - During the SM Policy Association Establishment process, an instruction to allow LOMs may be provided to the PCF, and accordingly, the PCF may provide an LOM policy (i.e., an FQDN / IP range that allows routing to the local area of ​​a DN) or an offload ID to the SMF. Each LOM policy may be provided with an offload ID assigned by the PCF.

[0385] - Received LOM policies and / or offload IDs can be transmitted to I-SMF. SMF can transmit the offload ID alone or together with LOM information.

[0386] - Can provide DNS server addresses to be used for DNS requests related to traffic that is not a target of the LOM.

[0387] - To configure the EDNS (Extension DNS) client subnet option for the target FQDN(s) of a DNS query that is not a target of the LOM, I-SMF can provide PSA UPF address information to be used in the selected EASDF (e.g., PSA UPF IP address on N6).

[0388] - The IP address of the EASDF received from the I-SMF and optionally DNS security information can be transmitted to the UE via Protocol Configuration Options (PCO).

[0389] - Can send LOM allow instructions to I-SMF.

[0390] In step S1130, I-SMF can set DNS message processing rules in EASDF using LOM information received from SMF.

[0391] If I-SMF obtains an EASDF IP address in step S1110 or S1120, I-SMF may call Neasdf_DNSContext_Create Request to configure EASDF.

[0392] I-SMF can configure the UL CL UPF in the direction of the local PSA UPF to forward IP packets (including forwarding IP packets to EASDF) based on LOM information or offload ID.

[0393] In step S1140, an EAS discovery procedure using EASDF can be performed.

[0394] Additionally, according to the first embodiment of the present disclosure, LOM service area information generated by the AMF may include allowed areas and non-allowed areas in units of TAI lists. The TAI lists included in the allowed areas and non-allowed areas may be mutually exclusive. For example, the non-allowed area may take precedence over the allowed area. Each TA within the TAI lists included in the allowed areas and non-allowed areas may be sorted according to priority.

[0395] AMF can dynamically manage and / or update allowed and disallowed zones within the LOM service area, and can determine whether LOM is supported and the I-SMF for LOM functions based on the UE's location and the allowed / disallowed zones.

[0396] Additionally, according to the first embodiment of the present disclosure, LOM service areas managed by an AMF may be managed / updated based on analysis information obtained from an NWDAF. For example, based on UE mobility analysis information, the AMF may configure the service areas / LOM service areas of an SMF supporting LOM as allowed areas by considering the mobility patterns of the UE. Additionally, for example, based on NF load analysis information for the SMF, the service areas / LOM service areas of a specific SMF may be configured as allowed areas and / or disallowed areas.

[0397] The LOM service area updated by the AMF can be applied or referenced at the time of determining whether a UE supports the new LOM. In other words, there is no impact on existing PDU sessions of UEs that support or do not support LOM based on the LOM service area prior to the update.

[0398] For example, according to a first embodiment of the present disclosure, an AMF may manage / update a LOM service area composed of allowed or disallowed areas based on the area where a LOM service area exists in the result of an NRF query, or based on the service area of ​​a candidate SMF that supports LOM. The AMF may utilize analysis information from an NWDAF (e.g., UE mobility analysis, NF load analysis, etc.) to determine and update the allowed and disallowed areas for LOM.

[0399] FIG. 12 illustrates an example of a procedure for managing an analysis information-based LOM service area to which the first implementation of the present disclosure is applied.

[0400] In step S1200, a subscription procedure for UE mobility analytics information may be performed. The AMF may send a subscription request to the NWDAF to obtain UE mobility analytics information for a specific UE. For example, the AMF may call the Nnwdaf_AnalyticsSubscription_Subscribe operation to send a subscription request message to the NWDAF to obtain UE mobility analytics information. The NWDAF may generate analytics information by subscribing to and obtaining statistics and / or prediction information regarding UE location changes, etc., from the target UE's serving AMF, AF, or OAM, and send the generated UE mobility analytics information back to the AMF. For example, the NWDAF may call the Nnwdaf_AnalyticsSubscription_Notify operation to send a notification message containing UE mobility analytics information to the AMF.

[0401] In step S1210, a subscription procedure for NF load analysis information may be performed. The AMF may send a subscription request to the NWDAF to obtain NF load analysis information for the SMF. For example, the AMF may call the Nnwdaf_AnalyticsSubscription_Subscribe operation to send a subscription request message to the NWDAF to obtain NF load analysis information. The NWDAF may generate analysis information by subscribing to and obtaining statistical and forecast information regarding the SMF's NF status, NF resource usage, NF load, etc., through data collection from the NRF, OAM, and AF, and may send the generated NF load analysis information back to the AMF. For example, the NWDAF may call the Nnwdaf_AnalyticsSubscription_Notify operation to send a notification message containing NF load analysis information to the AMF.

[0402] In step S1220, the AMF may create an initial LOM service area (allowed area and / or unallowed area) based on the UE mobility analysis information and / or NF load analysis information obtained through step S1200 and / or step S1210. Alternatively, the AMF may update the preset LOM service area information based on the UE mobility analysis information and / or NF load analysis information obtained through step S1200 and / or step S1210.

[0403] For example, the AMF can configure an LOM service area that includes the UE's expected movement path or a range of locations where UE movement is frequent as an allowed area. For example, the AMF can configure an SMF service area / LOM service area that supports LOMs exceeding a specific threshold as an unallowed area, or configure an allowed area that consists only of an SMF service area / LOM service area that supports LOMs not exceeding a specific threshold. The AMF can select the optimal LOM I-SMF that supports the configured allowed area.

[0404] In step S1230, NWDAF may send an analytics subscription notification message containing updated UE mobility analytics information. For example, NWDAF may call the Nnwdaf_AnalyticsSubscription_Notify operation to send a notification message containing updated UE mobility analytics information to AMF.

[0405] In step S1240, NWDAF may send an analytics information subscription notification message containing updated NF load analysis information. For example, NWDAF may call the Nnwdaf_AnalyticsSubscription_Notify operation to send a notification message containing updated NF load analysis information to AMF.

[0406] In step S1250, the AMF can update / manage allowed areas and / or disallowed areas based on the updated analysis information received in steps S1230 and / or S1240.

[0407] 2. Second Implementation: Determining LOM Support Based on Allowed and Disallowed Zones

[0408] According to a second embodiment of the present disclosure, the AMF may determine whether to support LOM for a UE's PDU session based on allowed and disallowed areas that the AMF stores, manages, and updates. In particular, the AMF may determine whether to support LOM for a UE's PDU session based on a LOM service area configured and updated based on analysis information obtained from the NWDAF according to the first embodiment of the present disclosure, rather than whether the UE location is included within a LOM service area based on conventional static / passive configuration.

[0409] That is, in the prior art, the AMF determines whether to support LOM based only on the UE location and a preset LOM service area regardless of the load of the A-SMF, and selects / adds an I-SMF that supports the LOM service area, whereas according to the second implementation of the present disclosure, the SMF determines whether to support LOM for the UE's PDU session based on allowed and unallowed areas created / updated based on NF load analysis information and / or mobility analysis information of the UE, and can determine whether to select / add a LOM I-SMF.

[0410] For example, based on the NF load analysis information of A-SMF, AMF can set the service area / LOM service area of ​​A-SMF with low load as an unallowed area. AMF can decide not to support LOM for PDU sessions of UEs located in the unallowed area.

[0411] For example, based on the NF load analysis information of A-SMF, AMF can set the service area / LOM service area as an allowed area if the load of A-SMF is high. AMF can select / add I-SMF for LOM support for UEs located in the allowed area.

[0412] This can also be applied to other UEs. For example, as the service area / LOM service area of ​​a high-load A-SMF is set to a disallowed area, that A-SMF may not be selected as the LOM I-SMF for another UE. Accordingly, the load resulting from each SMF's edge computing support can be distributed across the entire network.

[0413] Information on allowed and disallowed zones may be information stored, managed, or updated by the AMF at the network level. Information on allowed and disallowed zones may be transferred or provided between AMFs during the handover procedure depending on UE mobility.

[0414] An example according to the implementation of the present specification may be as follows.

[0415] For example, assume that the pre-configured LOM service zones within the network include TAs 1 through 30. The pre-configured LOM service zone information for each SMF may be as follows.

[0416] - SMF#1's LOM Service Areas: TA 1~10

[0417] - SMF#2 LOM Service Area: TA 11~20

[0418] - SMF#3 LOM Service Area: TA 21~30

[0419] The expected movement paths based on the mobility patterns of UE#1 and UE#2 serviced by AMF may be as follows.

[0420] - UE#1: TA 5~10

[0421] - UE#2: TA 11~15

[0422] AMF can determine LOM support for the PDU sessions of UE#1 and UE#2 by setting the allowed zones within the LOM service zones it manages / updates / references to TA 5~15.

[0423] Meanwhile, assuming that the service area / LOM service area of ​​the A-SMF of UE#1 and UE#2 is TA 9~11, if the A-SMF load is not high, the allowed area can be set to TA 5~15 as above. On the other hand, if the A-SMF load is high, the allowed and disallowed areas can be set as follows.

[0424] - Allowed areas: TA 5~8, 12~15

[0425] - Unallowed areas: TA 9~11

[0426] That is, if the load of the A-SMF is high, the service area / LOM service area TA 9~11 of the A-SMF is set as an unallowed area, so that other UEs can be prevented from selecting the A-SMF as the LOM I-SMF.

[0427] Subsequently, for example, in a situation where the load of SMF#2 increases, the AMF can change the TA that supported LOM through the SMF from the existing allowed area to the disallowed area, allowing it to refer to whether existing / new UEs will support LOM in the future. For example, the allowed and disallowed areas can be configured as follows.

[0428] - Allowed areas: TA 5~8

[0429] - Unallowed areas: TA 9~15

[0430] Additionally, if, via AMF, the location and expected movement path of a new UE#3 are not included in the existing allowed / unallowed areas, AMF can add / update LOM service area information through an NRF inquiry.

[0431] The present disclosure may have various effects.

[0432] For example, even if an LOM SA is not pre-configured in the network, the AMF can efficiently support LOM. In other words, by configuring and / or managing LOM SAs by dynamically reflecting UE mobility patterns and the real-time load conditions of each SMF, rather than relying on statically fixed LOM SA settings, the LOM function can be flexibly applied across various network operating environments and deployment scenarios.

[0433] For example, the load resulting from edge computing support of each SMF can be efficiently distributed from an overall network perspective. That is, the load among SMFs can be balanced through decisions regarding the selection, addition, and / or modification of I-SMFs that reflect dynamically changing network conditions. This prevents QoS degradation caused by overloading of specific SMFs and improves the stability and reliability of the 5G network as a whole.

[0434] For example, network resources can be utilized efficiently by minimizing unnecessary signaling and procedures related to LOM support. In other words, network resource consumption can be reduced by decreasing unnecessary procedures and signaling through optimized LOM SA configuration / management and / or LOM support decisions based thereon.

[0435] The effects obtainable through the specific examples of the present disclosure are not limited to those listed above. For example, there may be various technical effects that a person having ordinary skill in the related art can understand or derive from the present disclosure. Accordingly, the specific effects of the present disclosure are not limited to those explicitly described in the present disclosure, but may include various effects that can be understood or derived from the technical features of the present disclosure.

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

Claims

1. In a method performed by a connection and mobility management node, Step of generating local offloading management service area information for each UE (user equipment), The above local offloading management service area information includes an allowed area and a non-allowed area for local offloading management on a tracking area (TA) basis; A step of determining whether the local offloading management is supported for the UE based on the local offloading management service area information generated above; and A method comprising the step of selecting an intermediate session management node for the session of the UE based on the determination that the above local offloading management is supported.

2. In Paragraph 1, A method for generating the above local offloading management service area information based on a subset of all available local offloading service areas pre-configured within a network.

3. In Paragraph 1, A method in which the above local offloading management service area information is generated based on the service area of ​​at least one session management node supporting the above local offloading management when there is no pre-configured local offloading management service area information within the network.

4. In Paragraph 1, A method for generating the above local offloading management service area information based on at least one of a TA list considering the current location of the UE or the mobility pattern of the UE.

5. In Paragraph 1, The above method further includes the step of updating the local offloading management service area information.

6. In Paragraph 1, A method in which the above-mentioned local offloading management service area information is generated or updated based on analysis information obtained from a network data analysis node.

7. In Paragraph 6, A method comprising at least one of UE mobility analysis information or NF (network function) load analysis information.

8. In Paragraph 1, A method for determining that local offloading management is supported based on the above UE being located in the above allowed area.

9. In Paragraph 1, A method in which it is determined that the local offloading management is not supported based on the fact that the above UE is located in the above-mentioned unallowed area.

10. In Paragraph 1, A method in which the service area of ​​the anchor session management node is included in the allowed area based on the high load of the anchor session management node.

11. In Paragraph 1, A method in which the service area of ​​the anchor session management node is included in the aforementioned unallowed area based on the fact that the load of the anchor session management node is not high.

12. In Paragraph 1, The above allowed area and the above prohibited area are mutually exclusive methods.

13. In Paragraph 1, A method including a list of TAs according to priority for each of the above allowed area and the above unallowed area.

14. In Paragraph 1, A method for transmitting the above local offloading management service area information to the target connection and mobility management node of the handover.

15. In the connection and mobility management node, At least one processor; and It includes at least one memory that can be operably connected to the at least one processor and stores instructions that cause the connection and mobility management node to perform operations based on execution by the at least one processor. The above operation is: Step of generating local offloading management service area information for each UE (user equipment), The above local offloading management service area information includes an allowed area and a non-allowed area for local offloading management on a tracking area (TA) basis; A step of determining whether the local offloading management is supported for the UE based on the local offloading management service area information generated above; and A step of selecting an intermediate session management node for the session of the UE based on the determination that the above local offloading management is supported; Connection and mobility management nodes including

Images