Management of localized services

By using the NEF to subscribe to location reporting events and filtering based on capabilities through AMF and GMLC, the system efficiently manages terminal presence in specific areas, addressing the limitations of current location reporting services and improving service delivery for mobile communication systems.

WO2024228609A1PCT designated stage expired Publication Date: 2024-11-07LG ELECTRONICS INC

Patent Information

Application Number
PCT/KR2024/095730
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-04
Filing Date
2024-04-15
Publication Date
2024-11-07

AI Technical Summary

Technical Problem

Current mobile communication systems face challenges in managing localized services effectively, particularly in identifying and providing services to terminals within specific areas, as existing location reporting services are limited to specific terminals and cannot report the presence of multiple terminals entering or leaving service areas efficiently.

Method used

The proposed solution involves the Network Exposure Function (NEF) subscribing to location reporting events for all terminals in a specific area, filtering based on capabilities, and using the Access and Mobility Management Function (AMF) and Gateway Mobile Location Center (GMLC) to determine and report terminals with the necessary capabilities, enabling efficient management of terminal presence and provision of localized services.

Benefits of technology

This approach allows for accurate reporting of terminals capable of receiving localized services within a specific area, enabling better resource allocation and service provision, and improves the management of terminal presence by reducing repetitive signaling and enhancing service delivery.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure KR2024095730_07112024_PF_FP_ABST
    Figure KR2024095730_07112024_PF_FP_ABST
Patent Text Reader

Abstract

One disclosure of the present disclosure provides a method by which an AF performs communication. The method comprises the steps of: sending a location report request to an NEF of a specific PLMN, wherein the location report request comprises information about a target region, the target region is a region in which an SNPN provides a localized service, and the location report request comprises information indicating that the location report request is for the localized service; receiving a list of UEs from the NEF, wherein a target UE included in the list of UEs is located in the target region; and transmitting a request for an update for the target UE to a network node of an HPLMN of the target UE, wherein the request for an update is a request to enable the target UE to receive a CH control list for the localized service.
Need to check novelty before this filing date? Find Prior Art

Description

Management of localized services

[0001] This specification relates to mobile communications.

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

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

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

[0005] A method is needed to perform the necessary procedures only for terminals located in areas where SNPN's localized service is provided.

[0006] Provides SNPN with information on terminals located in the target area for localized services.

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

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

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

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

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

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

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

[0014] Figure 10 shows an example of reporting a list of aerial UEs in a geographic area.

[0015] Figure 11 illustrates a procedure according to the first embodiment of the present specification.

[0016] Figures 12 and 13 illustrate a procedure according to the disclosure of this specification.

[0017] Figure 14 illustrates the AF procedure for the disclosure of this specification.

[0018] Figure 15 illustrates NEF's procedure for disclosure of this specification.

[0019] Figure 16 illustrates the UE's procedure for disclosure of this specification.

[0020] The following techniques, devices, and systems can be applied to various wireless multiple access systems. Examples of multiple access systems include code division multiple access (CDMA) systems, frequency division multiple access (FDMA) systems, time division multiple access (TDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and multicarrier frequency division multiple access (MC-FDMA) systems. CDMA can be implemented via wireless technologies such as universal terrestrial radio access (UTRA) or CDMA2000. TDMA can be implemented via wireless technologies such as global system for mobile communications (GSM), general packet radio service (GPRS), or enhanced data rates for GSM evolution (EDGE). OFDMA can be implemented using wireless technologies such as IEEE (Institute of Electrical and Electronics Engineers) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, or E-UTRA (evolved UTRA). UTRA is part of UMTS (universal mobile telecommunications system). 3GPP (3rd generation partnership project) LTE (long-term evolution) is part of E-UMTS (evolved UMTS) that uses E-UTRA.3GPP LTE uses OFDMA in the downlink (DL) and SC-FDMA in the uplink (UL). Evolution of 3GPP LTE includes LTE-A (advanced), LTE-A Pro, and / or 5G NR (new radio).

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

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

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

[0024] As used herein, a slash ( / ) or a comma can mean "and / or." For example, "A / B" can mean "A and / or B." Accordingly, "A / B" can mean "only A," "only B," or "both A and B." For example, "A, B, C" can mean "A, B, or C."

[0025] In this specification, “at least one of A and B” may mean “only A,” “only B,” or “both A and B.” Additionally, in this specification, the expressions “at least one of A or B” or “at least one of A and / or B” may be interpreted identically to “at least one of A and B.”

[0026] Additionally, in this specification, “at least one of A, B and C” can mean “only A”, “only B”, “only C”, or “any combination of A, B and C”. Additionally, “at least one of A, B or C” or “at least one of A, B and / or C” can mean “at least one of A, B and C”.

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

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

[0029] Although not limited thereto, the various descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed herein may be applied to various fields requiring wireless communication and / or connectivity between devices (e.g., 5G).

[0030] Hereinafter, the present specification will be described in more detail with reference to the drawings. In the following drawings and / or description, the same reference numbers may refer to the same or corresponding hardware blocks, software blocks, and / or functional blocks, unless otherwise indicated.

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

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

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

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

[0035] The base station (200) and the network (300) may be implemented as wireless devices, and a particular wireless device may operate as a base station / network node in relation to other wireless devices.

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

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

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

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

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

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

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

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

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

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

[0046] Wireless devices (100a to 100f) can be connected to a network (300) via a base station (200). AI technology can be applied to the wireless devices (100a to 100f), and the wireless devices (100a to 100f) can be connected to an AI server (400) via the network (300). The network (300) can be configured using a 3G network, a 4G (e.g., LTE) network, a 5G (e.g., NR) network, and a network after 5G. The wireless devices (100a to 100f) can communicate with each other via the base station (200) / network (300), but can also communicate directly (e.g., sidelink communication) without going through the base station (200) / network (300). For example, vehicles (100b-1, 100b-2) can communicate directly (e.g., vehicle-to-vehicle (V2V) / vehicle-to-everything (V2X) communication). Additionally, IoT devices (e.g., sensors) can communicate directly with other IoT devices (e.g., sensors) or other wireless devices (100a to 100f).

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

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

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

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

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

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

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

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

[0055] As described above, the numerical value of the frequency range of the NR system can be changed. For example, FR1 may include a band from 410 MHz to 7125 MHz, as shown in Table 2 below. That is, FR1 may include frequency bands above 6 GHz (or 5850, 5900, 5925 MHz, etc.). For example, the frequency bands above 6 GHz (or 5850, 5900, 5925 MHz, etc.) included within FR1 may include unlicensed bands. Unlicensed bands may be used for various purposes, such as for communications for vehicles (e.g., autonomous driving).

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

[0057] Here, the wireless communication technology implemented in the wireless device of the present specification may include not only LTE, NR, and 6G, but also narrowband IoT (NB-IoT) for low-power communication. For example, NB-IoT technology may be an example of LPWAN (low power wide area network) technology and may be implemented with standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the above-described names. Additionally or alternatively, the wireless communication technology implemented in the wireless device of the present specification may perform communication based on LTE-M technology. For example, LTE-M technology may be an example of LPWAN technology and may be called by various names such as eMTC (enhanced MTC). For example, LTE-M technology can be implemented by at least one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-bandwidth limited), 5) LTE-MTC, 6) LTE MTC, and / or 7) LTE M, and is not limited to the above-described names. Additionally or alternatively, the wireless communication technology implemented in the wireless device of the present specification can include at least one of ZigBee, Bluetooth, and / or LPWAN considering low-power communication, and is not limited to the above-described names. For example, ZigBee technology can create PAN (personal area networks) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and can be called by various names.

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

[0059] In FIG. 2, the first wireless device (100) and / or the second wireless device (200) may be implemented in various forms depending on the use case / service. For example, {the first wireless device (100) and the second wireless device (200)} may correspond to at least one of {the wireless devices (100a to 100f) and the base station (200)}, {the wireless devices (100a to 100f) and the wireless devices (100a to 100f)}, and / or {the base station (200) and the base station (200)} of FIG. 1. The first wireless device (100) and / or the second wireless device (200) may be configured by various components, devices / parts, and / or modules.

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

[0061] The processing chip (101) may include at least one processor, such as a processor (102), and at least one memory, such as a memory (104). Additionally and / or alternatively, the memory (104) may be located external to the processing chip (101).

[0062] The processor (102) may control the memory (104) and / or the transceiver (106) and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed herein. For example, the processor (102) may process information in the memory (104) to generate first information / signal and transmit a wireless signal including the first information / signal via the transceiver (106). The processor (102) may receive a wireless signal including second information / signal via the transceiver (106) and store information obtained by processing the second information / signal in the memory (104).

[0063] A memory (104) may be operatively connected to the processor (102). The memory (104) may store various types of information and / or instructions. The memory (104) may store firmware and / or software code (105) that implements code, instructions and / or sets of instructions that, when executed by the processor (102), perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein. For example, the firmware and / or software code (105) may implement instructions that, when executed by the processor (102), perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein. For example, the firmware and / or software code (105) may control the processor (102) to perform one or more protocols. For example, the firmware and / or software code (105) may control the processor (102) to perform one or more air interface protocol layers.

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

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

[0066] The processing chip (201) may include at least one processor, such as a processor (202), and at least one memory, such as a memory (204). Additionally and / or alternatively, the memory (204) may be located external to the processing chip (201).

[0067] The processor (202) may control the memory (204) and / or the transceiver (206) and may be configured to implement the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed herein. For example, the processor (202) may process information in the memory (204) to generate third information / signal and transmit a wireless signal including the third information / signal via the transceiver (206). The processor (202) may receive a wireless signal including fourth information / signal via the transceiver (206) and store information obtained by processing the fourth information / signal in the memory (204).

[0068] A memory (204) may be operatively connected to the processor (202). The memory (204) may store various types of information and / or instructions. The memory (204) may store firmware and / or software code (205) that implements instruction codes, commands and / or sets of instructions that, when executed by the processor (202), perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein. For example, the firmware and / or software code (205) may implement instructions that, when executed by the processor (202), perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein. For example, the firmware and / or software code (205) may control the processor (202) to perform one or more protocols. For example, the firmware and / or software code (205) may control the processor (202) to perform one or more air interface protocol layers.

[0069] Here, the processor (202) and memory (204) may be part of a communication modem / circuit / chip designed to implement a RAT (e.g., LTE or NR). A transceiver (206) may be connected to the processor (202) and may transmit and / or receive wireless signals via one or more antennas (208). Each transceiver (206) may include a transmitter and / or a receiver. The transceiver (206) may be used interchangeably with the RF unit. In the present specification, the second wireless device (200) may represent a communication modem / circuit / chip.

[0070] Hereinafter, hardware elements of the wireless device (100, 200) will be described in more detail. Although not limited thereto, one or more protocol layers may be implemented by one or more processors (102, 202). For example, one or more processors (102, 202) may implement one or more layers (e.g., functional layers such as a physical (PHY) layer, a media access control (MAC) layer, a radio link control (RLC) layer, a packet data convergence protocol (PDCP) layer, a radio resource control (RRC) layer, and a service data adaptation protocol (SDAP) layer). One or more processors (102, 202) may generate one or more protocol data units (PDUs), one or more service data units (SDUs), messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed herein. One or more processors (102, 202) can generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data or information according to the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed herein and provide the signals to one or more transceivers (106, 206). One or more processors (102, 202) can receive signals (e.g., baseband signals) from one or more transceivers (106, 206) and obtain PDUs, SDUs, messages, control information, data or information according to the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed herein.

[0071] The one or more processors (102, 202) may be referred to as a controller, a microcontroller, a microprocessor, and / or a microcomputer. The one or more processors (102, 202) may be implemented by hardware, firmware, software, and / or a combination thereof. For example, one or more application specific integrated circuits (ASICs), one or more digital signal processors (DSPs), one or more digital signal processing devices (DSPDs), one or more programmable logic devices (PLDs), and / or one or more field programmable gate arrays (FPGAs) may be included in the one or more processors (102, 202). For example, the one or more processors (102, 202) may be configured by a set of a communication control processor, an application processor (AP), an electronic control unit (ECU), a central processing unit (CPU), a graphic processing unit (GPU), and a memory control processor.

[0072] One or more memories (104, 204) may be coupled to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, codes, instructions, and / or commands. The one or more memories (104, 204) may be configured as random access memory (RAM), dynamic RAM (DRAM), read-only memory (ROM), erasable programmable ROM (EPROM), flash memory, volatile memory, nonvolatile memory, hard drive, register, cache memory, computer-readable storage media, and / or combinations thereof. The one or more memories (104, 204) may be located internally and / or externally to the one or more processors (102, 202). Additionally, the one or more memories (104, 204) may be coupled to the one or more processors (102, 202) via various technologies, such as wired or wireless connections.

[0073] One or more transceivers (106, 206) can transmit user data, control information, wireless signals / channels, etc., referred to in the descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed herein to one or more other devices. One or more transceivers (106, 206) can receive user data, control information, wireless signals / channels, etc., referred to in the descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed herein from one or more other devices. For example, one or more transceivers (106, 206) can be coupled to one or more processors (102, 202) and can transmit and receive wireless signals. For example, one or more processors (102, 202) can control one or more transceivers (106, 206) to transmit user data, control information, wireless signals, etc., to one or more other devices. Additionally, one or more processors (102, 202) may control one or more transceivers (106, 206) to receive user data, control information, wireless signals, etc. from one or more other devices.

[0074] One or more transceivers (106, 206) may be coupled to one or more antennas (108, 208). Additionally and / or alternatively, one or more transceivers (106, 206) may include one or more antennas (108, 208). One or more transceivers (106, 206) may be configured to transmit and receive user data, control information, wireless signals / channels, etc., as described in the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed herein via one or more antennas (108, 208). In the present specification, one or more antennas (108, 208) may be multiple physical antennas or multiple logical antennas (e.g., antenna ports).

[0075] One or more transceivers (106, 206) may convert received user data, control information, wireless signals / channels, etc. from RF band signals to baseband signals in order to process the received user data, control information, wireless signals / channels, etc. using one or more processors (102, 202). One or more transceivers (106, 206) may convert processed user data, control information, wireless signals / channels, etc. from baseband signals to RF band signals using one or more processors (102, 202). For this purpose, one or more transceivers (106, 206) may include an (analog) oscillator and / or a filter. For example, one or more transceivers (106, 206) may up-convert an OFDM baseband signal to an OFDM signal via an (analog) oscillator and / or filter under the control of one or more processors (102, 202) and transmit the up-converted OFDM signal at a carrier frequency. One or more transceivers (106, 206) may receive an OFDM signal at a carrier frequency and down-convert the OFDM signal to an OFDM baseband signal via an (analog) oscillator and / or filter under the control of one or more processors (102, 202).

[0076] Although not illustrated in FIG. 2, the wireless device (100, 200) may further include additional components. The additional components (140) may be configured in various ways depending on the type of the wireless device (100, 200). For example, the additional components (140) may include at least one of a power unit / battery, an input / output (I / O) device (e.g., an audio I / O port, a video I / O port), a driving device, and a computing device. The additional components (140) may be connected to one or more processors (102, 202) via various technologies, such as a wired or wireless connection.

[0077] In the implementation of the present specification, a UE can operate as a transmitter in the uplink (UL) and as a receiver in the downlink (DL). In the implementation of the present specification, a base station can operate as a receiver in the UL and as a transmitter in the DL. For the sake of convenience of description, it is mainly assumed below that the first wireless device (100) operates as a UE and the second wireless device (200) operates as a base station. For example, a processor (102) connected to, mounted on, or released in the first wireless device (100) can be configured to perform UE operations according to the implementation of the present specification or to control a transceiver (106) to perform UE operations according to the implementation of the present specification. A processor (202) connected to, mounted on, or released in the second wireless device (200) can be configured to perform base station operations according to the implementation of the present specification or to control a transceiver (206) to perform base station operations according to the implementation of the present specification.

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

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

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

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

[0082] The UE (100) includes a processor (102), memory (104), a transceiver (106), one or more antennas (108), a power management module (141), a battery (142), a display (143), a keypad (144), a SIM (Subscriber Identification Module) card (145), a speaker (146), and a microphone (147).

[0083] The processor (102) may be configured to implement the descriptions, functions, procedures, proposals, methods and / or flowcharts disclosed herein. The processor (102) may be configured to control one or more other components of the UE (100) to implement the descriptions, functions, procedures, proposals, methods and / or flowcharts disclosed herein. A layer of a radio interface protocol may be implemented in the processor (102). The processor (102) may include an ASIC, other chipsets, logic circuits and / or data processing devices. The processor (102) may be an application processor. The processor (102) may include at least one of a DSP, a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), and a modem (modulator and demodulator). An example of the processor (102) is the SNAPDRAGON manufactured by Qualcomm®. TM Series processors, EXYNOS made by Samsung® TM Series processors, A-series processors made by Apple®, HELIO made by MediaTek® TM ATOM series processors made by Intel® TM It can be found in the series processors or the corresponding next-generation processors.

[0084] Memory (104) is operatively coupled to the processor (102) and stores various information for operating the processor (102). Memory (104) may include ROM, RAM, flash memory, memory cards, storage media, and / or other storage devices. When the implementation is implemented in software, the techniques described herein may be implemented using modules (e.g., procedures, functions, etc.) that perform the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed herein. The modules may be stored in memory (104) and executed by the processor (102). Memory (104) may be implemented within the processor (102) or external to the processor (102), in which case it may be communicatively coupled to the processor (102) via various methods known in the art.

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

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

[0087] The display (143) outputs the results processed by the processor (102). The keypad (144) receives input to be used by the processor (102). The keypad (144) can be displayed on the display (143).

[0088] A SIM card (145) is an integrated circuit that securely stores an International Mobile Subscriber Identity (IMSI) and associated keys, and is used to identify and authenticate subscribers in mobile devices such as mobile phones and computers. Additionally, many SIM cards can store contact information.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0106] - AUSF (Authentication Server Function)

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

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

[0109] - USDF (Unstructured Data Storage Function)

[0110] - NEF (Network Exposure Function)

[0111] - I-NEF (Intermediate NEF)

[0112] - NRF (Network Repository Function)

[0113] - NSSF (Network Slice Selection Function)

[0114] - PCF (Policy Control Function)

[0115] - SMF (Session Management Function)

[0116] - UDM (Unified Data Management)

[0117] - UDR (Unified Data Repository)

[0118] - UPF (User Plane Function)

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

[0120] - AF (Application Function)

[0121] - UE (User Equipment)

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

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

[0124] - NWDAF (Network Data Analytics Function)

[0125] - CHF (CHarging Function)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0153] <Registration Procedure>

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

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

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

[0157] - Initial registration for 5GS; or

[0158] - mobility registration update; or

[0159] - Periodic registration update; or

[0160] - Emergency registration

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0215] Establishing a PDU session may involve:

[0216] - UE-initiated PDU session establishment procedure

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

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

[0219] - Network-triggered PDU session establishment procedure

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

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

[0222] In the procedures shown in Figures 8 and 9, it is assumed that the UE is already registered with the AMF, so unless the UE is emergency registered, the AMF has already retrieved the user subscription data from the UDM.

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

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

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

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

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

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

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

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

[0231] If the request type indicates "Existing PDU Session", which refers to an existing PDU session moving between a 3GPP connection and a non-3GPP connection, and if the serving PLMN S-NSSAI of the PDU session is in the allowed NSSAI of the target connection type, the PDU session establishment procedure may be performed in the following cases:

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

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

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

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

[0236] (3) Step 3: If the AMF is not associated with an SMF for the PDU session ID provided by the UE (e.g., when the request type indicates "Initial Request"), the AMF invokes the Create SM Context request procedure (e.g., Nsmf_PDUSession_CreateSMContext Request). If the AMF is already associated with an SMF for the PDU session ID provided by the UE (e.g., when the request type indicates "Existing PDU Session"), the AMF invokes the Update SM Context request procedure (e.g., Nsmf_PDUSession_UpdateSMContext Request).

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

[0238] The AMF ID is the UE's GUAMI, which uniquely identifies the AMF serving the UE. The AMF passes the PDU session ID along with the N1 SM container containing the PDU session establishment request message received from the UE. The GPSI (generic public subscription identifier) ​​is included if available to the AMF.

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

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

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

[0242] (5) Step 5: SMF sends a create SM context response message (e.g., Nsmf_PDUSession_CreateSMContext Response) or an update SM context response message (e.g., Nsmf_PDUSession_UpdateSMContext Response) to AMF according to the request received in step 3.

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

[0244] If the SMF decides not to accept the PDU session establishment, the SMF rejects the UE request by sending a NAS SM signal including the relevant SM rejection cause by responding to the AMF with an Nsmf_PDUSession_CreateSMContext Response. The SMF also indicates to the AMF that the PDU session ID is considered released and the SMF proceeds to step 20 below, aborting the PDU session establishment procedure.

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

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

[0247] (7b) Step 7b: SMF performs the SM policy association establishment procedure to establish a PCF and SM policy association, and obtains the basic PCC rules for the PDU session.

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

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

[0250] (10) Step 10: If the request type indicates an "Initial Request," the SMF may initiate the N4 Session Establishment procedure with the selected UPF. Otherwise, the SMF may initiate the N4 Session Modification procedure with the selected UPF.

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

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

[0253] The N1N2 Message Forwarding message may contain N2 SM information. The N2 SM information carries the following information that the AMF will forward to the (R)AN:

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

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

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

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

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

[0259] - UE integrity protection maximum data rate received in PDU session establishment request message: if integrity protection is indicated as "Preferred" or "Required" in the user plane security enforcement information.

[0260] - RSN (redundancy sequence number) parameter

[0261] The N1N2 message transfer message may include an N1 SM container. The N1 SM container includes a PDU Session Establishment Accept message that the AMF will provide to the UE. The PDU Session Establishment Accept message includes the S-NSSAI from the allowed NSSAI. For the LBO roaming scenario, the PDU Session Establishment Accept message includes the S-NSSAI from the allowed NSSAI for the VPLMN, and also includes the corresponding S-NSSAI of the HPLMN from the mapping of the allowed NSSAI received by the SMF in step 3.

[0262] Multiple QoS rules, QoS flow levels, and QoS parameters may be included in the PDU session establishment accept message and N2 SM information within the N1 SM container, if required, for QoS flows associated with QoS rules and QoS profiles.

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

[0264] (12) Step 12: AMF sends a NAS message containing the PDU Session ID and PDU Session Establishment Accept message destined for the UE and the N2 SM information received from SMF to (R)AN within an N2 PDU Session Request message.

[0265] (13) Step 13: The (R)AN may perform AN-specific signaling exchanges with the UE related to the information received from the SMF. For example, in the case of the NG-RAN, the UE may perform an RRC connection reconfiguration with the UE to set up the necessary NG-RAN resources related to the QoS rules for the PDU session request received in step 12.

[0266] (R)AN forwards the NAS message (PDU Session ID, N1 SM container (PDU Session Establishment Accept message)) received in step 12 to the UE. (R)AN provides the NAS message to the UE only if the AN-specific signaling exchange with the UE includes (R)AN resource additions related to the received N2 command.

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

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

[0269] (14) Step 14: (R)AN sends an N2 PDU Session Response message to AMF. The N2 PDU Session Response message may include PDU Session ID, cause, N2 SM information (PDU Session ID, AN tunnel information, accepted / rejected QFI list, user plane enforcement policy notification), etc.

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

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

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

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

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

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

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

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

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

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

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

[0281] Location Report Service

[0282] The event monitoring function monitors specific events in 3GPP systems and reports these monitoring event information via the NEF. This function consists of a means for 5GS NFs to configure specific events, detect them, and report them to requested parties.

[0283] To support monitoring capabilities in roaming scenarios, a roaming agreement must be established between the HPLMN and the VPLMN. If the VPLMN's AMF / SMF determines that event reports require normalization, the AMF / SMF normalizes the event reports before transmitting them to the NEF.

[0284] A set of functions required for monitoring must be accessible to the NF of the 5GS through the NEF. The NEF can monitor events through the UDM, AMF, SMF, NSACF, and GMLC. The NEF can configure a given monitor event in the UDM, AMF, SMF, NSACF, or GMLC and report the event through the UDM or the AMF, SMF, NSACF, or GMLC. Based on a specific monitoring event or information, the AMF, GMLC, NSACF, or UDM is responsible for recognizing the monitoring event or information and reporting it through the NEF.

[0285] One of the list of monitoring events may be a location reporting event.

[0286] Location reporting events are detected based on the event reporting information parameters received in the monitoring request (single report, maximum number of reports, maximum report period, cycle, etc.).

[0287] A location report event reports the current or last known location of the UE.

[0288] When AMF is the detecting NF:

[0289] - One-time and continuous location reporting are supported. For continuous location reporting, the serving node sends a notification whenever it detects a location change, with the information refined according to the acceptable location accuracy.

[0290] - For one-time reports with the Immediate Report flag set, AMF reports the last known location immediately.

[0291] When AMF is the detecting NF:

[0292] - If the immediate report flag is not set, the AMF reports the UE's current location (if the AMF does not have the UE's current location at the granularity requested for the location report, the AMF retrieves the information via the NG-RAN location reporting procedure).

[0293] When GMLC is the detecting NF:

[0294] - Immediate and delayed position reporting are supported. For delayed position reporting, the event types UE availability, area, periodic position, and motion are supported.

[0295] Report on UAVs in specific areas

[0296] This procedure can be used by the USS / TPAE to obtain a list of unmanned aerial vehicles (UAVs) in a geographical area and provide them to the PLMN. The USS / TPAE provides the geographical area information to the UAS-NF. Based on the received information, the UAS NF can trigger an AMF / MME monitoring event configuration procedure with the event ID "Number of UEs present in a geographical area" or trigger a GMLC-based position reporting procedure. The AMF / MME can filter the UAV list before sending it to the UAS NF (e.g., if the Aerial UE indication is included as an event filter in the UAS NF's monitoring event configuration request, it can filter only on UEs with an Aerial subscription). The UAS NF performs filtering on the list received from the AMF or MME before responding back to the USS / TPAE. The UAS-NF includes the 3GPP UAV ID and, if available, may include the CAA-level UAV ID for each UAV in its tracking and position response to the USS / TPAE.

[0297] Figure 10 shows an example of reporting a list of aerial UEs in a geographic area.

[0298] 1. From USS to UAS NF: USS / TPAE sends a UAV list request to UAS NF, requesting UAV identities (e.g., 3GPP UAV ID, CAA-level UAV ID). USS / TPAE includes geographic area information, required reliable UE position information indication, and indication for immediate reporting in the request message to UAV-NF.

[0299] 2. From UAS NF to AMF / MME: The UAS NF determines the AMF based on the geographical area information and reuses the "Number of UEs present in a geographical area" event with any UE in the event filter to obtain the list of UEs in the target area from the AMF. The UAS NF may also include the "PDU session established for DNN(s) subject to aerial service" and / or "Aerial UE" indications in the event filter. If the target area cannot be mapped to a 3GPP network area, the UAS NF provides the AMF / MME with a list of TAs larger than the target area for the list of UEs to query. The AMF(s) / MME(s) may identify the UEs corresponding to the geographical area information and may also filter the list of UAVs by checking for UEs with aerial subscriptions if the request from the UAS NF / NEF includes the "Aerial UE" indication in the event filter. Additionally, the AMF may additionally identify UAVs that have successfully established a PDU session to the air service target DNN, if included as an event filter in the request from the UAS NF / NEF.

[0300] 3. [Optional] From UAS NF to GMLC: For UAVs in the target area that are not mapped to a 3GPP network area in the UE list generated in step 2, the UAS-NF queries the GMLC for the location of the UAV.

[0301] 4. [Conditional] If step 3 above has been executed, the UAS NF compares the location of the UAV from the list of locations returned by GMLC with the target area (provided in step 1 above) to identify the UAV to include in the report for the USS.

[0302] 5. For the list of UAVs received from AMF / MME or the list of UAVs identified in step 4, the UAS NF performs filtering by checking whether each reported 3GPP UAV ID matches the corresponding UUAA context.

[0303] 6. UAS NF to USS: The UAS NF responds to the USS / TPAE with a filtered list of UAVs (step 5). If available, the UAS NF may provide the CAA-level UAV ID in the response message to the USS / TPAE. If the USS has performed a UUAA of the UAV or the UAS NF is configured to recognize the USS as authorized to receive that information, the 3GPP UAV ID is also included.

[0304] In order for a terminal to receive localized services from a SNPN, the terminal must be provisioned with "Credentials Holder controlled prioritized lists of preferred SNPNs and GINs for accessing Localized Services" from the home network (HPLMN or subscribed SNPN) and perform SNPN selection based on the lists.

[0305] In order for the home network (HPLMN) to provision the terminal with "Credentials Holder controlled prioritized lists of preferred SNPNs and GINs for accessing Localized Services", the home network must know whether the terminal is subscribed to a localized service.

[0306] To achieve this, a localized service provider (LSP) or a SNPN providing localized services must provide the home network with information for the SNPN (e.g., localized service information, validity conditions, SNPN identity, target UE, etc.). This can be accomplished through OAM procedures.

[0307] For example, a localized service provider (NSP) or a SNPN providing localized services can transmit information about a target UE to the home network. Then, based on the information about the target UE, the home network can determine which terminals are subscribed to the localized service. Based on the information about the target UE, the home network can provision the target UE with "Credentials Holder controlled prioritized lists of preferred SNPNs and GINs for accessing localized services" information.

[0308] Previously, a localized service provider (SNPN) or a localized service provider (LSP) providing localized services had no way of knowing which UEs were present in the area where the localized service was currently provided. Therefore, the SNPN (or localized service provider) may not know which UEs should be provided with the "Credentials Holder controlled prioritized lists of preferred SNPNs and GINs for accessing localized services" information.

[0309] SNPNs (or localized service providers) can typically receive information from UEs that have installed localized service applications. Based on this information, the UEs to which "Credentials Holder controlled prioritized lists of preferred SNPNs and GINs for accessing localized services" information should be provided can be determined.

[0310] Alternatively, generally, when a user subscribes to a localized service via the web or the like, the SNPN (or localized service provider) may receive information. Based on this information, the UE to which the "Credentials Holder controlled prioritized lists of preferred SNPNs and GINs for accessing localized services" information should be provided may be determined.

[0311] An SNPN (or localized service provider) may not be able to determine whether a UE is located within the SNPN's coverage area, which provides localized services. Until a user subscribes to a localized service, the SNPN (or localized service provider) may not have information about the UE. This makes it difficult for the SNPN (or localized service provider) to provide services to any UE in a specific area.

[0312] Conventional "location reporting services" support location reporting via the Network Exposure Function (NEF). These services only support location reporting for specific terminals (those identified by the AMF via IP address or GPSI). In contrast, the method proposed in this specification enables location reporting for all terminals located in a specific area.

[0313] Conventional "location reporting services" can only report the current or periodic location of a terminal. This means that if a terminal enters or leaves a service area (an area where localized services are provided), the SNPN may not be aware of this fact and thus may not be able to provide localized services to that terminal. The method proposed in this specification can address this issue.

[0314] According to the conventional 'Report on UAVs in a Specific Area', information for identifying UAVs (e.g., 3GPP UAV ID, CAA Level UAV ID) may be reported, rather than terminal information. In contrast, according to the method proposed in this specification, multiple terminals with the capability to support localized services can be reported, regardless of whether they subscribe to a UAV. The presence or absence of such capability can be determined by checking the terminal's capability stored in the UDM as subscriber information or by directly checking the terminal's capability in the AMF.

[0315] According to the conventional 'Report on UAVs in a Specific Area', the terminal's UAV identity may be reported. In contrast, according to the method proposed in this specification, the terminal's GPSI may be reported.

[0316] According to the conventional 'Report on UAVs in a Specific Area', the reporting party (USS / TPAE) can receive the report by requesting a one-time report, making it difficult to manage the influx of terminals in the relevant area (repeated reporting requests are required to confirm the influx of terminals in the target area, which may result in repetitive signaling). On the other hand, according to the method proposed in this specification, the reporting party (AF / SNPN) can receive information on the influx of terminals in the relevant area at a specific time, making it possible to efficiently manage the influx of terminals in the relevant area.

[0317] The home network may provide information to the SNPN (e.g., the AF of the SNPN) about terminals located within the SNPN coverage area where localized services are provided.

[0318] Based on the received information, the SNPN (or localized service provider) can determine a candidate UE to provide the localized service. The SNPN (or localized service provider) can send information (e.g., SMS, application-level push message, etc.) to the determined candidate UE to notify it of the availability of the localized service.

[0319] Through the method described above, when a terminal wants to use a localized service, the SNPN can determine the target UE and notify the home network, and based on this, the terminal can select the corresponding SNPN.

[0320] Additionally, based on information about terminals located within the SNPN coverage area where localized services are provided, the SNPN can determine the number of terminals within that coverage area. Based on this, the SNPN can decide whether to launch the localized service. Alternatively, based on this, the SNPN can adjust application server capacity.

[0321] Based on a service agreement between an SNPN (or a localized service provider) and an HPLMN (or a subscribed SNPN acting as a Credentials Holder), the SNPN (or a localized service provider) providing access to the localized service may provide the HPLMN (or the subscribed SNPN acting as a Credentials Holder) with configuration information for SNPN selection, so that the HPLMN or the subscribed SNPN acting as a Credentials Holder may generate and provision SNPN selection information (SNPN selection information for discovering and selecting an SNPN providing localized services) to the UE. The configuration information for SNPN selection may include at least one of the following parameters (a, b, c, d).

[0322] a. An identifier of an SNPN that provides access to one or more localized services;

[0323] b. Identifier of each localized service;

[0324] c. Validity information for each localized service (e.g., validity time information or / and location support information) and / or

[0325] d. A list of UE IDs (e.g. GPSI or external group ID) that identify UEs subscribed to the localized service.

[0326] The operator of the HPLMN (or the subscribed SNPN acting as a Credentials Holder) can use the received information to create or update a Credentials Holder controlled prioritized list of preferred SNPNs / GINs for accessing localized services, and provision them to the UE using the SOR procedure.

[0327] To address the aforementioned issues, the following methods may be proposed. The methods described below may be performed or used in combination or complementary manner.

[0328] In this specification, "Credentials Holder controlled prioritized lists of preferred SNPNs and GINs for accessing localized services" refers to values ​​set by the home network on the terminal, which can be used by the terminal to select an SNPN for localized services. The name for this may vary.

[0329] In this specification, AF may be the AF of SNPN.

[0330] 1. First Example

[0331] An AF (e.g., an AF in SNPN) can subscribe to location reporting events for all terminals via NEF.

[0332] When an AF subscribes to a location reporting event via NEF, the AF can subscribe to the location reporting event by sending the NEF an indication that the request is for any terminal, rather than information about a specific terminal, or by providing information about the area for which the event reporting is desired. The AF can also provide the NEF with information about the time at which the event reporting is desired.

[0333] For example, if a localized service is only available during certain time zones, AF can transmit information about those specific time zones to NEF. This allows event reporting to occur only when a terminal enters that area at a specific time.

[0334] Additionally, the AF can transmit information to the NEF regarding the minimum number of UEs for reporting. The AF can then request that event reporting be performed only when the minimum number of UEs in the area is met (or exceeded).

[0335] Additionally, AF can provide filtering conditions for terminals that can be included in reports. For example, AF can request that location reports be made only for terminals subscribed to networks with which the SNPN has a service level agreement (e.g., PLMN A, PLMN B, etc.).

[0336] Based on the location information received from the AF, the NEF can request an event report using the target AMF or GMLC (Gateway Mobile Location Center). This operation can be performed using conventional techniques. The NEF can receive the event report from the target AMF or GMLC.

[0337] For example, the NEF may request the UDM for a list of terminals attached to AMFs in the target area. The NEF may receive a list of terminals attached to AMFs in the target area.

[0338] If AF subscribes to location reporting events that include time information, NEF can verify, based on the event report received directly from AMF / GMLC, that i) the time at which the terminal(s) included in the event report are located in the area corresponds to ii) the time zone included in the time information received from AF.

[0339] If AF subscribes to a location reporting event by including time information, NEF can perform event subscription (request for event reporting) while transmitting the time information to AMF / GMLC.

[0340] AF can set the aforementioned time information based on the start and end times of the localized service.

[0341] The aforementioned time information may be in the form of a periodic value. For example, the time information may be from 12:00 PM to 1:00 PM every day, every Sunday, or 9:00 AM on the first day of every month.

[0342] If AF subscribes to a location reporting event that includes time information, NEF may report to AF a list of terminals located in the target area during a specific period stipulated by the time information.

[0343] An AF can request location reports for all UEs located in a specific area. Alternatively, an AF can request location reports only for specific UEs located in the target area (e.g., UEs that can access the SNPN).

[0344] For example, if AF requests location reporting only for terminals that can access the SNPN located in the target area, the following actions may be performed:

[0345] - When a terminal registers with a home network, the terminal may transmit 5GMM (5G Mobility Management) capability to the AMF. The 5GMM capability may include information on whether the terminal supports "Credentials Holder controlled prioritized lists of preferred SNPNs and GINs for accessing Localized Services."

[0346] - AMF can transfer the above 5GMM capabilities to UDM.

[0347] - The AF may send a request to the NEF for a location reporting event subscription. At this time, the AF may send the request with an indication that it wishes to report the event only for terminals that have the capability to receive localized services via the SNPN (even if the AF does not include an indication as described above, the NEF will always be able to report only for terminals that have the capability).

[0348] - The NEF can send a request to the UDM for a list of terminals attached to multiple AMFs located in a target area. For example, the NEF can create a list of AMFs managing an area based on the area information requested by the AF through the UDM. Then, based on the list of AMFs created, the NEF can request the UDM for a list of terminals managed by each AMF belonging to the list (the AMF managing the area). The request can include an indication to include in the list only terminals supporting "Credentials Holder controlled prioritized lists of preferred SNPNs and GINs for accessing Localized Services" (even if the request does not include the above-mentioned indication, the UDM can always include in the list only terminals having the capability). In this regard, the following actions (i-iv) can be performed: i. The NEF can receive a terminal list for terminals having the capability from the UDM. ii. Based on the received terminal list, the NEF can request the AMF / GMLC to determine whether terminals with the corresponding capability are located in the target area (or whether they have entered or exited the target area). iii. The NEF can receive information from the AMF / GMLC on whether terminals with the corresponding capability are located in the target area. iv. The NEF can create a list of terminals located in the target area based on the received information and transmit the list to the AF.

[0349] - Instead of the NEF receiving a list of terminals supporting "Credentials Holder controlled prioritized lists of preferred SNPNs and GINs for accessing Localized Services" from the UDM, the NEF may subscribe to an event requesting the AMF / GMLC whether a target terminal is in the target area. The target terminal may be any UE and / or a terminal supporting "Credentials Holder controlled prioritized lists of preferred SNPNs and GINs for accessing Localized Services". In this regard, the following actions (i-iii) may be performed: i. The NEF may request the AMF / GMLC for a list of terminals in the target area (or a list of terminals entering and exiting the area). The request may include an indication to include terminal information only if the terminals have the capability. ii. The AMF / GMLC may create a list of terminals that are in the target area and support the capability. AMF / GMLC can notify NEF of the above-mentioned list and target area entry / exit information (information on terminals entering / exiting the target area and information on the time of entry / exit). AMF can determine whether a terminal has the corresponding capability based on the capability information uploaded by the terminal. GMLC can determine whether the terminal has the corresponding capability information by including the requested information when requesting terminal location information from AMF. iii. NEF can create a list of terminals located in the target area (at a specific time) based on the information received from AMF / GMLC and transmit the created list to AF.

[0350] Alternatively, the following actions can be performed:

[0351] - When a terminal registers with a home network, the terminal may transmit 5GMM (5G Mobility Management) capability to the AMF. The 5GMM capability may include information on whether the terminal supports "Credentials Holder controlled prioritized lists of preferred SNPNs and GINs for accessing Localized Services." The terminal may transmit a registration request including the 5GMM (5G Mobility Management) capability to the AMF. The terminal's support of "Credentials Holder controlled prioritized lists of preferred SNPNs and GINs for accessing Localized Services" may indicate that the terminal has the capability to receive localized services.

[0352] - AMF can transfer the above 5GMM capabilities to UDM.

[0353] - The AF may send a request to the NEF for a location reporting event subscription. At this time, the AF may send the request with an indication that it wishes to report the event only for terminals that have the capability to receive localized services via the SNPN (even if the AF does not include an indication as described above, the NEF will always be able to report only for terminals that have the capability).

[0354] Figure 11 illustrates a procedure according to the first embodiment of the present specification.

[0355] Step 1. The SNPN's AF (or the AF of a localized service provider) can request a location report from the NEF (by subscribing to location report events). The request may include information about the target area.

[0356] AF can send requests to multiple PLMNs / SNPNs.

[0357] The above request may include information about the target area, time condition, and localized service. That is, indications indicating the target area, time condition, and localized service may be included in the request.

[0358] For example, the request may include information that a particular localized service can be provided in a particular area (target area) at a particular time (time condition).

[0359] Information about the target area, time condition, and localized service described above may be set based on the area and / or time provided.

[0360] Step 2-3. NEF can obtain information about terminals located in the target area.

[0361] The NEF can select an AMF based on the target area and request event reports entering and exiting the target area using existing procedures. The NEF can receive reports containing information about terminals located in the target area from the AMF using existing procedures. The NEF can also receive reports containing location information about candidate UEs from the GMLC using existing procedures.

[0362] If the request from AF includes time information, NEF can obtain information about terminals located in the target area during a specific period corresponding to the time information.

[0363] If the request from AF includes time information, NEF can obtain information about terminals entering the target area during a specific period corresponding to the time information and the time of entry.

[0364] If the request from AF includes time information, NEF can obtain information about terminals leaving the target area and the time of departure during a specific period corresponding to the time information.

[0365] Step 4. Based on the reports received from the AMF / GMLC, the NEF can determine a list of terminals currently located in the target area. Based on the information received from the AMF / GMLC, the NEF can determine a list of terminals currently located in the target area.

[0366] If the request from AF includes time information, NEF can determine a list of terminals present in the target area during the specific period based on information about terminals entering the target area and the incoming time information (or information about terminals leaving the target area and the outgoing time information) during the specific period corresponding to the time information.

[0367] Step 5. NEF can filter the terminal list determined above.

[0368] NEF can request subscriber information via UDM. NEF can receive subscriber information from UDM.

[0369] Based on the subscriber information received, NEF can verify whether the terminal included in the determined terminal list has the capability to receive localized services.

[0370] NEF can filter the terminal list by i) maintaining terminals with the above-determined capability and ii) deleting terminals without the above-determined capability.

[0371] Step 6. NEF can send the filtered terminal list to AF.

[0372] Subsequently, when a specific terminal enters or exits the target area, the NEF can receive an event report from the AMF / GMLC regarding this event. The NEF can then notify the AF of this event.

[0373] If the request from the AF includes time information, the NEF can transmit to the AF information about terminals entering the target area and their incoming time information (or information about terminals leaving the target area and their outgoing time information) during a specific period corresponding to the time information.

[0374] Step 7. Based on the information (e.g. GPSI) about the terminal list received by the AF of the SNPN, the SNPN can find (determine) the home networks of the UEs located within the target area.

[0375] If the request from the AF includes time information, the SNPN can determine a list of terminals present in the target area during the specified period based on the information received from the NEF. Based on the determined list of terminals, the SNPN can find (determine) the home networks of the UEs located within the target area.

[0376] Based on the received terminal list, the SNPN can request the home network of the target terminal (a terminal belonging to the terminal list) to transmit (provision or update) a CH control list (Credentials Holder controlled prioritized lists of preferred SNPNs and GINs for accessing Localized Services) for the target terminal.

[0377] Based on the received terminal list, the SNPN may request the home network of the target terminal (a terminal belonging to the terminal list) to provision / update "Credentials Holder controlled prioritized lists of preferred SNPNs and GINs for accessing Localized Services" for the target terminal.

[0378] The home network of the target terminal receiving the above request may be the SoR AF of the home network or the UDM of the home network.

[0379] For example, some UEs in a UE list may belong to PLMN1 and some UEs may belong to PLMN2. In this case, the SNPN can generate a list of UEs belonging to each home network. That is, the SNPN can generate a list of UEs belonging to PLMN1 and a list of UEs belonging to PLMN2. The SNPN can send the list of UEs belonging to PLMN1 to PLMN1. The SNPN can send the list of UEs belonging to PLMN2 to PLMN2. When sending the UE list, the SNPN can request the UEs in the list to provision / update "Credentials Holder controlled prioritized lists of preferred SNPNs and GINs for accessing Localized Services". This request can be forwarded to the OAM, UDM / SoR-AF, or the OAM of the home network, etc.

[0380] Step 8. The home network that received the SNPN request can perform an SoR update procedure to provide the target terminal (a terminal included in the terminal list) with a "Credentials Holder controlled prioritized list of preferred SNPNs and GINs for accessing Localized Services." The details of the SoR update are described later in FIGS. 12 and 13.

[0381] Previously, all terminals (terminals located in the target area and terminals not located in the target area) could receive "Credentials Holder controlled prioritized lists of preferred SNPNs and GINs for accessing Localized Services" from the home network (SOR AF of the home network). According to an embodiment of the present disclosure, terminals located in the target area can receive "Credentials Holder controlled prioritized lists of preferred SNPNs and GINs for accessing Localized Services" from the home network (SOR AF of the home network).

[0382] That is, terminals that are not located in the target area may not receive "Credentials Holder controlled prioritized lists of preferred SNPNs and GINs for accessing Localized Services" from the home network (SOR AF of the home network).

[0383] 2. Second Example

[0384] A PRA can be set up through AF, and based on this, AF can request a location report for the PRA.

[0385] AF can configure PRA information with 5GC using the service parameter provisioning procedure.

[0386] In this case, when requesting a location for any UE (or when AF requests a list of UEs located in the target area), AF can request a location report using the configured PRA ID information. The information about the target area in step 1 of FIG. 11 described above can be replaced with the configured PRA ID information. That is, AF can send a request to NEF including the PRA ID information. Then, AF can receive from NEF a list of UEs located in the area corresponding to the PRA ID.

[0387] For the aforementioned PRA information configuration, AF can provide NEF with PRA ID and location information for the PRA ID. The location information can be in the form of geographical area information, civic address, TA list, cell list, etc.

[0388] If AF has provided location information for a PRA ID to AF in the form of geographical area information or civic address, NEF may transform the received location information into a list of TAs or cells used in the network.

[0389] The NEF can receive information about the PRA (PRA ID and location information for the PRA ID). The NEF can transmit the information about the PRA to other network nodes, such as the AMF / SMF / PCF. Other network nodes, such as the AMF / SMF / PCF, can store the information about the received PRA. Later, when the AF requests the location of any UE (or requests a list of UEs located in the target area), the AF can perform the request based on the information about the PRA.

[0390] Information about PRAs provided by AF (PRA ID and location information for the PRA ID) may not be used directly, but may be mapped to PRA IDs used on the network by NEF. To this end, NEF stores information regarding the mapping between the PRA ID provided by AF and the internal PRA ID assigned by NEF, and NEF may use this mapping information as needed.

[0391] Figures 12 and 13 illustrate a procedure according to the disclosure of this specification.

[0392] Step 1. The SNPN's AF (or the AF of a localized service provider) can request a location report from the NEF (by subscribing to location report events). The request may include information about the target area.

[0393] AF can send requests to multiple PLMNs / SNPNs.

[0394] The above request may include information about the target area, time condition, and localized service. That is, indications indicating the target area, time condition, and localized service may be included in the request.

[0395] For example, the request may include information that a particular localized service can be provided in a particular area (target area) at a particular time (time condition).

[0396] Information about the target area, time condition, and localized service described above may be set based on the area and / or time provided.

[0397] Additionally, AF can provide information about candidate UEs (e.g., GPSI list, External Group Id, etc.). For example, if a terminal has installed an application for a localized service, information about that terminal can be provided.

[0398] The methods by which NEF determines the list of terminals located in the target area may include AMF-based procedures and GMLC-based procedures.

[0399] For the AMF-based procedure, steps 2 to 5 below may be performed. The AMF-based procedure may be performed when the NEF does not receive information about candidate UEs from the AF or when the NEF does not have preset candidate UE information.

[0400] For a GMLC-based procedure, steps 6 to 10 below may be performed. The GMLC-based procedure may be performed when the NEF receives information about a candidate UE from the AF or when the NEF has preset candidate UE information.

[0401] Step 2. NEF can select an AMF based on the target area. Through the existing "Area of ​​Interest event" registration process, NEF can request event reporting from the AMF for terminals entering and exiting the target area. This request can include event reporting for all terminals within the target area.

[0402] The NEF can request the AMF to report events (such as a terminal entering or exiting the target area). Additionally, the NEF can request information about terminals currently in the target area from the AMF.

[0403] If the request in step 1 includes a time condition, the NEF can request information about terminals in the target area at that time from the AMF.

[0404] The above selected AMF may be multiple AMFs.

[0405] Step 3-4. If necessary, the AMF can request a location report from the RAN. The AMF can receive a location report containing location information about the terminal from the RAN.

[0406] For example, if the target area is at the cell level, the AMF can request a position report for the terminal to the RAN to know the exact location of the terminal.

[0407] Step 5. The AMF can inform the NEF whether the terminals are located in the target area (e.g., IN / OUT / UNKNOWN) to inform the NEF of the terminals' location. The AMF can transmit a report containing information about the terminals located in the target area to the NEF.

[0408] In Step 2, the NEF may request the AMF to verify whether terminals in the target area are capable of receiving localized services. In this case, the information about terminals in the target area sent by the AMF to the NEF may not include information about terminals that do not have the capability.

[0409] AMF can send a Namf_EventExposure_Notify to NEF. Namf_EventExposure_Notify can contain SUPI. Namf_EventExposure_Notify can contain information about terminals currently located in the target area.

[0410] If the request in step 1 includes a time condition, Namf_EventExposure_Notify may contain information about terminals located in the target area at that time.

[0411] Step 6. If the AF provides information about the candidate UE to the NEF, the NEF can provide the candidate UE information to the GMLC. Alternatively, even if the AF does not provide information about the candidate UE to the NEF, the NEF can determine the candidate UE based on preset information (information preset by the operator based on the SLA). The NEF can send a request to the GMLC to verify whether the candidate UE has the capability to receive localized services.

[0412] For example, specific candidate UE information may be pre-configured in the NEF based on the AF Id.

[0413] Step 7. Based on the information about the candidate UE, the GMLC can figure out the serving AMF for the candidate UE.

[0414] GMLC can identify the serving AMF for each candidate UE by executing the Nudm_UECM_Get service with UDM. GMLC then executes the Ngmlc_Location_ProvideLocation Request service with the serving AMF to determine the location of each candidate UE.

[0415] Step 8. The AMF can perform a positioning procedure to locate the terminal. This can be performed through the LMF.

[0416] Step 9. AMF can report location information about the terminal to GMLC.

[0417] Step 10. GMLC can report location information about candidate terminals to NEF.

[0418] Step 11. Based on the report received from the AMF / GMLC (either a report from the AMF containing information about terminals located in the target area or a report containing location information about candidate terminals), the NEF can determine a list of terminals currently in the target area.

[0419] If the request in step 1 includes a time condition, NEF can determine a list of terminals located in the target area at that time.

[0420] NEF can retrieve subscriber information from UDM, check whether the terminal is capable of receiving localized services, and include only those terminals in the terminal list (UE list).

[0421] That is, the NEF can filter the determined terminal list. The NEF can request subscriber information via the UDM. The NEF can receive subscriber information from the UDM. Based on the received subscriber information, the NEF can verify whether the terminals included in the determined terminal list have the capability to receive localized services. The NEF can filter the terminal list by i) maintaining terminals with the capability and ii) deleting terminals without the capability from the determined terminal list.

[0422] Step 12. The NEF can send the list of terminals (UEs) located in the target area to the AF (the AF of the SNPN). The NEF can send the list of terminals determined (and filtered) in step 11 to the AF.

[0423] If the terminal subsequently enters (or exits) the target area, the AMF (or GMLC) can notify the NEF of this fact. The NEF can then notify the AF of this fact.

[0424] Step 13. Based on the information (e.g. GPSI) about the terminal list received by the AF of the SNPN, the SNPN can find (determine) the home networks of the UEs located within the target area.

[0425] Based on the received terminal list, the SNPN can request the home network of the target terminal (a terminal belonging to the terminal list) to transmit (provision or update) a CH control list (Credentials Holder controlled prioritized lists of preferred SNPNs and GINs for accessing Localized Services) for the target terminal.

[0426] Based on the received terminal list, the SNPN may request the home network of the target terminal (a terminal belonging to the terminal list) to provision / update "Credentials Holder controlled prioritized lists of preferred SNPNs and GINs for accessing Localized Services" for the target terminal.

[0427] The home network of the target terminal receiving the above request may be the SoR AF of the home network or the UDM of the home network.

[0428] For example, some UEs in a UE list may belong to PLMN1 and some UEs may belong to PLMN2. In this case, the SNPN may generate a list of UEs belonging to each home network. That is, the SNPN may generate a list of UEs belonging to PLMN1 and a list of UEs belonging to PLMN2. The SNPN may send the list of UEs belonging to PLMN1 to PLMN1. The SNPN may send the list of UEs belonging to PLMN2 to PLMN2. When sending the UE list, the SNPN may request the UEs in the list to provision / update "Credentials Holder controlled prioritized lists of preferred SNPNs and GINs for accessing Localized Services". The request may be a request for the UEs to receive the "Credentials Holder controlled prioritized lists of preferred SNPNs and GINs for accessing Localized Services".

[0429] These requests may be forwarded to OAM, UDM / SoR-AF, or OAM in the home network.

[0430] Step 14-15. The home network that received the SNPN request can perform the SoR update procedure to provide the target terminal (terminal located in the target area) with a 'Credentials Holder controlled prioritized list of preferred SNPNs and GINs for accessing Localized Services'.

[0431] When using SoR AF, SoR AF can trigger SoR update by sending 'Nudm_PameterProvision_Update request' to UDM. 'Nudm_SDM_Notification request' can be sent including SoR container. The SOR container of 'Nudm_SDM_Notification request' can include 'Credentials Holder controlled prioritized lists of preferred SNPNs and GINs for accessing Localized Services'.

[0432] For example, when a SNPN requests the SoR AF of a target terminal (SoR AF of HPLMN) to provision / update "Credentials Holder controlled prioritized lists of preferred SNPNs and GINs for accessing Localized Services" for the target terminal, the SoR AF can trigger an SoR update by sending a 'Nudm_PameterProvision_Update request' to the UDM. Then, the UDM can send a 'Nudm_SDM_Notification request' to the AMF to perform an SoR update. The 'Nudm_SDM_Notification request' can be sent with an SoR container included.

[0433] When UDM performs the action directly, it can trigger an SoR update by sending a 'Nudm_SDM_Notification request' to AMF. The 'Nudm_SDM_Notification request' can be sent with an SoR container. The SoR container of the 'Nudm_SDM_Notification request' can include 'Credentials Holder controlled prioritized lists of preferred SNPNs and GINs for accessing Localized Services'.

[0434] For example, when SNPN requests UDM of target terminal (UDM of HPLMN) to provision / update "Credentials Holder controlled prioritized lists of preferred SNPNs and GINs for accessing Localized Services" for target terminal, UDM can trigger SoR update by sending 'Nudm_SDM_Notification request' to AMF. 'Nudm_SDM_Notification request' can be sent including SoR container. SoR container of 'Nudm_SDM_Notification request' can include 'Credentials Holder controlled prioritized lists of preferred SNPNs and GINs for accessing Localized Services'.

[0435] Previously, all terminals (terminals located in the target area and terminals not located in the target area) could receive "Credentials Holder controlled prioritized lists of preferred SNPNs and GINs for accessing Localized Services" from the home network (SOR AF of the home network). According to an embodiment of the present disclosure, terminals located in the target area can receive "Credentials Holder controlled prioritized lists of preferred SNPNs and GINs for accessing Localized Services" from the home network (SOR AF of the home network).

[0436] That is, terminals that are not located in the target area may not receive "Credentials Holder controlled prioritized lists of preferred SNPNs and GINs for accessing Localized Services" from the home network (SOR AF of the home network).

[0437] Step 16. AMF can transmit the SoR container received from the UDM to the terminal. AMF can transmit the SoR container to the terminal via DL NAS Transport. That is, the terminal can receive the 'Credentials Holder controlled prioritized lists of preferred SNPNs and GINs for accessing Localized Services' through the SoR container.

[0438] Step 17. The terminal can send the SoR container to AMF via UL NAS Transport if the network requests a response.

[0439] Step 18. AMF can transmit the SoR container received from the terminal to UDM.

[0440] Step 19. UDM can notify SoR AF that SoR update was successful.

[0441] By providing information about terminals located in areas where localized services are provided to localized service providers / SNPNs that provide localized services, terminals can be enabled to receive localized services. Furthermore, since the number of terminals within the SNPN's coverage area is known, the SNPN can use this information to determine whether to initiate localized services or adjust application server capacity.

[0442] The AF can request a location report for any UE. Based on this, it can request the home network to update the "Credentials Holder controlled prioritized lists of preferred SNPNs and GINs for accessing Localized Services" so that the targeted UEs can access SNPNs.

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

[0444] Figure 14 illustrates the AF procedure for the disclosure of this specification.

[0445] 1. The AF can send a location report request to the Network Exposure Function (NEF) of a specific Public Land Mobile Network (PLMN).

[0446] The above location report request may include information about the target area.

[0447] The above target area may be an area where the above SNPN provides localized service.

[0448] The above location report request may include information indicating that it is for the localized service.

[0449] 2. AF can receive a list of UE (User Equipment) from the above NEF.

[0450] The target UE included in the above UE list may be located in the above target area.

[0451] 3. The AF can send a request for an update for the target UE to the network node of the HPLMN of the target UE.

[0452] The request for the above update may be a request to enable the target UE to receive a CH (Credentials Holder) control list for the localized service.

[0453] The above CH control list may be a 'Credentials Holder controlled prioritized lists of preferred SNPNs and GINs for accessing Localized Services'.

[0454] The above network node may be SoR (Steer of Roaming) AF or UDM (Unified Data Management).

[0455] The above location report request may include a time condition.

[0456] The above localized service may be provided at a specific time corresponding to the above time conditions.

[0457] The above target UE may be located in the target area at the above specific time.

[0458] The above location report request may include information about a candidate UE.

[0459] The above target UE may correspond to the above candidate UE.

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

[0461] Figure 15 illustrates NEF's procedure for disclosure of this specification.

[0462] 1. NEF can receive location report requests from the AF (Application Function) of the SNPN (Standalone Non-Public Network).

[0463] The above location report request may include information about the target area.

[0464] The above target area may be an area where the above SNPN provides localized service.

[0465] The above location report request may include information indicating that it is for the localized service.

[0466] 2. NEF can obtain UE (User Equipment) information located in the target area.

[0467] 3. NEF can determine a UE list based on the UE information obtained above.

[0468] The target UE included in the above UE list may be located in the above target area.

[0469] 4. NEF may transmit the above UE list to the AF.

[0470] NEF can obtain subscriber information from Unified Data Management (UDM).

[0471] The steps for determining the above UE list are:

[0472] A step in which, based on the subscriber information, NEF determines whether the target UE has the capability to receive the localized service;

[0473] A step in which the NEF maintains the target UE in the UE list based on the target UE having the capability;

[0474] The NEF may include a step of deleting the target UE from the UE list based on the target UE not having the capability.

[0475] The above subscriber information may include UE capability information provided by the target UE during the registration process.

[0476] The above UE capability information may be information on whether or not the UE has the capability to receive the localized service.

[0477] The above location report request may include a time condition.

[0478] The above localized service may be provided at a specific time corresponding to the above time conditions.

[0479] The above target UE may be located in the target area at the above specific time.

[0480] The above location report request may include information about a candidate UE.

[0481] The above target UE may correspond to the above candidate UE.

[0482] The steps for obtaining UE information located in the above target area are:

[0483] The above location report request comprises a step of NEF transmitting a UE information request to GMLC (Gateway Mobile Location Center) based on the information about the candidate UE;

[0484] The above UE information request may include information about the candidate UE.

[0485] The UE information request may include a request for the GMLC to verify whether the candidate UE has the capability to receive the localized service.

[0486] The NEF may include a step of receiving location information about the candidate UE from the GMLC.

[0487] The step of determining the above UE list may be performed based on location information for the candidate UE.

[0488] The steps for obtaining UE information located in the above target area are:

[0489] A step in which the NEF transmits a UE information request to the AMF (Access and Mobility management Function) based on the above location report request not including information about the candidate UE;

[0490] The above UE information request may include a request to verify whether the AMF has the capability to receive the localized service.

[0491] The NEF may include a step of receiving the UE information from the AMF.

[0492] The UE included in the above UE information may have the above capabilities.

[0493] The step of determining the above UE list may be performed based on the above UE information.

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

[0495] Figure 16 illustrates the UE's procedure for disclosure of this specification.

[0496] 1. The UE can send a registration request to the Public Land Mobile Network (PLMN).

[0497] 2. The UE may receive approval of the registration from the PLMN.

[0498] 3. The UE can receive a CH (Credentials Holder) control list from the PLMN.

[0499] The above CH control list may be information for the UE to receive localized services from a Standalone Non-Public Network (SNPN) in the target area.

[0500] Based on the fact that the UE is not located in the target area, the UE may skip the step of receiving the CH control list.

[0501] The above CH control list may be a 'Credentials Holder controlled prioritized lists of preferred SNPNs and GINs for accessing Localized Services'.

[0502] The above registration request may include information that the UE has the capability to support the CH control list.

[0503] The above registration request may include information that the UE has the capability to receive the localized service.

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

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

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

[0507] The operations performed by the processor include: transmitting a location report request to an NEF of a specific PLMN; the location report request including information about a target area, the target area being an area in which the SNPN provides a localized service, and including information indicating that the location report request is for the localized service; receiving a list of UEs from the NEF; a target UE included in the list of UEs located in the target area, and transmitting a request for an update for the target UE to a network node of an HPLMN of the target UE, wherein the request for an update may be a request for the target UE to receive a CH control list for the localized service.

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

[0509] The operations performed by the processor include: transmitting a location report request to an NEF of a specific PLMN; the location report request including information about a target area, the target area being an area in which the SNPN provides a localized service, and including information indicating that the location report request is for the localized service; receiving a list of UEs from the NEF; a target UE included in the list of UEs located in the target area, and transmitting a request for an update for the target UE to a network node of an HPLMN of the target UE, wherein the request for an update may be a request for the target UE to receive a CH control list for the localized service.

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

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

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

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

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

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

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

[0517] The stored one or more commands comprise the steps of: transmitting a location report request to an NEF of a specific PLMN; the location report request including information about a target area, the target area being an area in which the SNPN provides a localized service, and including information indicating that the location report request is for the localized service; receiving a list of UEs from the NEF; a target UE included in the list of UEs located in the target area, and transmitting a request for an update for the target UE to a network node of an HPLMN of the target UE, wherein the request for an update may be a request for the target UE to receive a CH control list for the localized service.

[0518] This specification may have various effects.

[0519] For example, through the procedure disclosed in this specification, an efficient localized service can be provided by providing terminal information in the target area of ​​the localized service to the SNPN.

[0520] The effects that can be achieved through specific examples of this specification are not limited to the effects listed above. For example, a person with ordinary skill in the relevant technical field may understand or derive various technical effects from this specification. Accordingly, the specific effects of this specification are not limited to those explicitly described herein, but may include various effects that can be understood or derived from the technical features of this specification.

[0521] The claims set forth in this specification may be combined in various ways. For example, the technical features of the method claims of this specification may be combined to implement a device, and the technical features of the device claims of this specification may be combined to implement a method. Furthermore, the technical features of the method claims and the technical features of the device claims of this specification may be combined to implement a device, and the technical features of the method claims and the technical features of the device claims of this specification may be combined to implement a method. Other implementations are within the scope of the claims.

Claims

1. A method by which AF (Application Function) of SNPN (Standalone Non-Public Network) performs communication. A step of transmitting a location report request to a Network Exposure Function (NEF) of a specific Public Land Mobile Network (PLMN); The above location report request includes information about the target area, The above target area is an area where the above SNPN provides localized service, The above location report request includes information indicating that it is for the localized service; A step of receiving a list of UE (User Equipment) from the above NEF; The target UE included in the above UE list is located in the above target area, A step of transmitting a request for an update for the target UE to a network node of the HPLMN (Home PLMN) of the target UE, A method in which the request for the above update is a request to enable the target UE to receive a CH (Credentials Holder) control list for the localized service.

2. In paragraph 1, The above CH control list is a 'Credentials Holder controlled prioritized lists of preferred SNPNs and GINs for accessing Localized Services'.

3. In paragraph 1 or 2, The above network node is a SoR (Steer of Roaming) AF or UDM (Unified Data Management).

4. In any one of the clauses 1 to 3, The above location report request includes a time condition, The above localized service is provided at a specific time corresponding to the above time conditions, The above target UE is located in the target area at the above specific time.

5. In any one of paragraphs 1 to 4, The above location report request includes information about the candidate UE, The above target UE is a method corresponding to the above candidate UE.

6. As a method for performing communication by the NEF (Network Exposure Function) of PLMN (Public Land Mobile Network), A step of receiving a location report request from an Application Function (AF) of a Standalone Non-Public Network (SNPN); The above location report request includes information about the target area, The above target area is an area where the above SNPN provides localized service, The above location report request includes information indicating that it is for the localized service; A step of acquiring UE (User Equipment) information located in the target area; A step of determining a UE list based on the UE information obtained above; The target UE included in the above UE list is located in the above target area, A method comprising the step of transmitting the UE list to the AF.

7. In paragraph 6, Further comprising the step of obtaining subscriber information from UDM (Unified Data Management), The steps for determining the above UE list are: A step of determining whether the target UE has the capability to receive the localized service based on the subscriber information; a step of maintaining the target UE in the UE list based on the target UE having the capability; and A method comprising the step of deleting the target UE from the UE list based on the target UE not having the capability.

8. In paragraph 7, The above subscriber information includes UE capability information provided by the target UE during the registration process, The above UE capability information is information on whether or not the UE has the capability to receive the localized service.

9. In any one of paragraphs 6 to 8, The above location report request includes a time condition, The above localized service is provided at a specific time corresponding to the above time conditions, The above target UE is located in the target area at the above specific time.

10. In any one of paragraphs 6 to 9, The above location report request includes information about the candidate UE, The above target UE is a method corresponding to the above candidate UE.

11. In paragraph 10, The steps for obtaining UE information located in the above target area are: The step of transmitting a UE information request to a GMLC (Gateway Mobile Location Center) based on the location report request including information about the candidate UE; The above UE information request includes information about the candidate UE, The above UE information request includes a request to the GMLC to verify whether the candidate UE has the capability to receive the localized service, comprising a step of receiving location information about the candidate UE from the GMLC; The step of determining the above UE list is performed based on location information for the candidate UE.

12. In any one of the clauses 6 to 9, The steps for obtaining UE information located in the above target area are: A step of transmitting a UE information request to an AMF (Access and Mobility management Function) based on the above location report request not including information about a candidate UE; The above UE information request includes a request to verify whether the AMF has the capability to receive the localized service, A step of receiving the UE information from the AMF; The UE included in the above UE information has the above capabilities, The step of determining the above UE list is: a method performed based on the above UE information.

13. A method for UE (User Equipment) to perform communication, A step of transmitting a request for registration to a Public Land Mobile Network (PLMN); A step of receiving approval of the registration from the PLMN; comprising a step of receiving a CH (Credentials Holder) control list from the PLMN; The above CH control list is information for the UE to receive localized services from a Standalone Non-Public Network (SNPN) in the target area. A method in which the UE skips the step of receiving the CH control list based on the fact that the UE is not located in the target area.

14. In paragraph 13, The above CH control list is a 'Credentials Holder controlled prioritized lists of preferred SNPNs and GINs for accessing Localized Services'.

15. In paragraph 13 or 14, A method wherein the registration request includes information that the UE has the capability to support the CH control list.

16. In any one of the clauses 13 to 15, A method wherein the registration request includes information that the UE has the capability to receive the localized service.

17. As an AF (Application Function) of SNPN (Standalone Non-Public Network) that performs communication, Transmitter and receiver; Contains a processor, The operation performed by the above processor is an AF method according to any one of claims 1 to 5.

18. As a Network Exposure Function (NEF) of a PLMN (Public Land Mobile Network) that performs communication, Transmitter and receiver; Contains a processor, The operation performed by the above processor is a method according to any one of claims 6 to 12.

19. As a UE (User Equipment) performing communication, Transmitter and receiver; Contains a processor, The operation performed by the above processor is a UE according to any one of claims 13 to 16.

Citation Information

Patent Citations

  • Roaming between public and non-public 5g networks

    WO2022169693A1

Cited By

  • Aerial user equipment positioning

    US20260136219A1