Method for managing CAG configuration

Abstract

The present disclosure provides a method. The method comprises the steps in which: an AMF receives an NG setup request from a specific femto; the AMF transmits information about the specific femto to an NRF on the basis of the NG setup request; the AMF receives, from an NEF, an update request message for a CAG configuration of a target femto, wherein the update request message includes information about the target femto and the requested CAG configuration; and the AMF transmits an update message to the specific femto on the basis of the target femto being the specific femto, wherein the update message includes a request for updating the CAG configuration of the specific femto with the requested CAG configuration.

Description

How to manage CAG settings

[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] In relation to Femto, a method is required for updating CAG settings requested by operators.

[0006] When an update of the CAG settings of the target femto is requested by the operator, the CAG settings can be updated through the serving AMF of the target femto.

[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 a procedure according to the disclosure of this specification.

[0013] Figure 8 illustrates the procedure of AMF according to the disclosure of this specification.

[0014] Figure 9 illustrates the NEF procedure according to the disclosure of this specification.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0100] - AUSF (Authentication Server Function)

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

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

[0103] - USDF (Unstructured Data Storage Function)

[0104] - NEF (Network Exposure Function)

[0105] - I-NEF (Intermediate NEF)

[0106] - NRF (Network Repository Function)

[0107] - NSSF (Network Slice Selection Function)

[0108] - PCF (Policy Control Function)

[0109] - SMF (Session Management Function)

[0110] - UDM (Unified Data Management)

[0111] - UDR (Unified Data Repository)

[0112] - UPF (User Plane Function)

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

[0114] - AF (Application Function)

[0115] - UE (User Equipment)

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

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

[0118] - NWDAF (Network Data Analytics Function)

[0119] - CHF (CHarging Function)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0147] <femto>

[0148] In telecommunications, a femtocell can be a small, low-power cellular base station typically designed for use in homes or small businesses. A broader term used in the industry is small cells, which are a subset of femtocells. Femtocells allow service providers to extend coverage indoors or at the cell edge. Specifically, they can extend coverage in areas with limited or unavailable access.

[0149] Femtocells can provide network coverage even in areas where the signal from the main network cell may be too weak. Femtocells can also reduce competition for the main network cell by connecting end users to the operator's private network infrastructure located elsewhere via the Internet.

[0150] Consumers and small businesses can benefit from significantly improved coverage and signal strength, as the base station is virtually located within the building. Because the cell tower is relatively close to the femtocell, the mobile phone (user equipment) consumes significantly less power communicating with the femtocell, potentially extending battery life. Furthermore, depending on various factors, including carrier / network support, customer contract / rate plan, and mobile phone and operating system support, better voice quality (via HD Voice) may be achieved. Some carriers may even offer more attractive rates, such as discounts on home calls.

[0151] Femtocells can be an alternative approach to delivering the benefits of fixed mobile convergence (FMC). While most FMC architectures require new dual-mode handsets that operate on existing unlicensed spectrum residential / enterprise wireless access points, femtocell-based deployments require the installation of new access points that operate on existing handsets but use licensed spectrum.

[0152] In 3GPP terminology, a Home Node B (HNB) can be a 3G femtocell. A Home eNode B (HeNB) can be an LTE 4G femtocell.

[0153] UE access control in 5G femto can be supported by utilizing CAG (Closed Access Group) functionality.

[0154] This may be to satisfy the following SA1 requirements:

[0155] - Depending on operator policy, the 5G system should allow authorized administrators to provision PRAS with UE access considerations (allow all UEs or only specific UEs).

[0156] Looking at the above SA1 requirement, for a 5G femto that can only be accessed through a specific CAG, the CAG operator can change / update / manage the CAG configuration of the 5G femto to allow access to the 5G femto through a new CAG or to allow all UEs to access the network through the 5G femto for a certain period of time.

[0157] When a 5G femto is installed in an indoor environment and connected to a network, the 5G femto can notify the UE of its (pre-)configured supported CAG list via SIB. Then, only UEs with a matching allowed CAG list can access the network via the 5G femto.

[0158] However, to satisfy the above SA1 requirement (e.g., to allow all UEs to connect to 5G Femto, to allow UEs to connect to 5G Femto through a new CAG, or to allow 5G Femto connection to only specific UEs after allowing all UEs to connect to 5G Femto, etc.), the CAG list (supported CAG list) may not be included in the SIB information sent to the UE after 5G Femto is installed, or a new CAG ID may be included in the CAG list (supported CAG list), or the CAG list (supported CAG list) may be included again.

[0159] To this end, a method is needed that allows CAG operators to dynamically set / change / update / manage CAG configuration information of currently installed 5G femtos.

[0160] In this specification, a method may be proposed for a CAG operator to request the following from a Target 5G Femto through an AF:

[0161] - Request to stop SIB broadcasting for a specific CAG, or

[0162] - Request to add a new CAG ID in SIB, or

[0163] - Request for resumption of SIB broadcasting to CAG

[0164] To this end, during the NG setup process with 5G Femto, AMF can store information related to the 5G Femto in the NRF (Network Repository Function).

[0165] The AF can receive a CAG configuration provisioning / update request related to the target 5G femto from the CAG operator. Based on this, the AF can obtain information stored in the NRF via the NEF. Based on this, the AF (or NEF) can find the serving AMF connected to the target 5G femto.

[0166] The AF (or NEF) can transmit the CAG configuration information requested by the CAG operator to the 5G Femto via the serving AMF. In other words, the target 5G Femto can be updated / configured with the CAG configuration information requested by the CAG operator.

[0167] Based on the CAG configuration information updated / configured in 5G Femto, 5G Femto (or serving AMF) can perform access control for UE(s) currently in CM_CONNECTED state.

[0168] The method for dynamically changing / updating / managing CAG configuration information of 5G femto proposed in this specification may be composed of a combination of one or more operations / configurations / steps described in this specification.

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

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

[0171] In this specification, the terms network, CN (Core Network), 5G CN, 3GPP network, and 3GPP system are used interchangeably.

[0172] In this specification, the network may include a PLMN and a Non-Public Network (NPN).

[0173] In this specification, NPN may include both PNI-NPN (Public Network Integrated Non-Public Network) and SNPN (Stand-alone Non-Public Network), or may include only SNPN.

[0174] In this specification, PLMN may be interpreted to include PNI-NPN.

[0175] In this specification, the network identifier (or network identification information) may be a PLMN ID, PLMN ID, or NID (which is an SNPN ID).

[0176] In this specification, (5G) femto may be used interchangeably with (5G) femto cell(s), (5G) femto RAN, (5G) femto NG-RAN, (5G) femto gNB, CAG cell(s), femto base station, closed cell(s), etc.

[0177] In this specification, CAG operator may be used interchangeably with femto operator, CAG owner, femto provider, femto owner, authorized administrator, 3rd party administrator, etc.

[0178] Additionally, in this specification, the CAG operator may be the same entity as the person / entity that actually purchases and installs the femto (i.e., the femto installer) or may be a different entity.

[0179] By having the Femto installer perform the role / action of a 3rd party administrator, the CAG configuration information of the 5G Femto proposed in this specification can be dynamically configured / changed / updated / managed.

[0180] Some of the service operations between the core NFs (network functions) described below may be defined and used as new service operations.

[0181] Some of the NG message(s) between AMF and NG-RAN described below may be defined and used as new NG messages.

[0182] Some of the RRC message(s) between the NG-RAN and the terminal described below may be defined and used as new RRC messages.

[0183] The multiple steps described below may be performed simultaneously / in parallel, or may be performed in a reversed order.

[0184] The indications and names of parameter information suggested below are examples and may be called by different names for the proposed procedure / purpose / method.

[0185] Figures 6 and 7 illustrate a procedure according to the disclosure of this specification.

[0186] 1) Step 1

[0187] After the 5G Femto is installed / operated, the 5G Femto can initiate the setup process for the NG interface by sending an NG SETUP REQUEST message to the AMF.

[0188] A 5G Femto may also explicitly inform the AMF that it is a 5G Femto by including an additional 5G Femto indication in the NG setup request message.

[0189] Alternatively, a 5G Femto may implicitly indicate to the AMF that it is a 5G Femto by including the following in the NG Setup Request message:

[0190] - Information such as TAI, Global RAN Node ID, RAN Node Name, etc., and / or

[0191] - Information such as the IP address used by 5G Femto to establish an AMF and TNL connection, and / or

[0192] - Information set (configuration) in AMF, etc.

[0193] Alternatively, the 5G Femto may inform the AMF that it is a 5G Femto by including a list of CAGs supported by the 5G Femto in the NG setup request message.

[0194] Alternatively, the 5G Femto may inform the AMF that it is a 5G Femto by including the 5G Femto's CAG operator information, the Femto installer information (such as the installer's user ID, user number, etc.) and / or the 5G Femto's serial / manufacturing number (which may consist of one or more of numbers, strings, and special characters) in the NG setup request message.

[0195] If 5G Femto does not yet have a CAG list at the time of NG setup, 5G Femto may provide the CAG list to AMF when it is set up / provided later.

[0196] 2) Step 2

[0197] AMF can store information related to newly connected 5G femtos in NRF using the Nnrf_NFManagement_NFRegister procedure.

[0198] For existing input parameters that AMF stores in NRF, the contents of TS 23.502 v18.4.0 can be applied.

[0199] Additionally, information related to 5G femto that AMF stores in NRF may include some or all of the following information:

[0200] - Global RAN Node ID(s)

[0201] - RAN Node Name(s)

[0202] - Service area (e.g., TAI list)

[0203] - Serving AMF ID(s)

[0204] - Location information (e.g., geographical area)

[0205] - IP address(es)

[0206] - CAG business information

[0207] - Femto-spreader information

[0208] - 5G Femto serial / manufacturing number

[0209] - Can support 5G Femto.

[0210] 3) Step 3

[0211] AMF can complete the NG Setup process by sending an NG SETUP RESPONSE message to 5G Femto.

[0212] 5G Femto can broadcast (transmit to UE) SIB1 containing a supported CAG list that is (pre-)configured.

[0213] The terminal can compare the allowed CAG list with the CAG list included in SIB1 from the 5G femto to determine whether it can connect to the 5G femto.

[0214] That is, if some of the CAG list included in SIB1 from 5G Femto matches some of the allowed CAG list (pre-)stored in the terminal, the terminal can be determined to be able to connect to the 5G Femto.

[0215] If the 5G Femto does not yet have a CAG list when NG is set up, the 5G Femto can include the CAG list in SIB1 and broadcast it (transmit it to the terminal) when it is set up / provided with the CAG list later.

[0216] 4) Step 4

[0217] A CAG operator can request to set / change / update / manage CAG configuration for a specific 5G femto by sending a Nnef_FemtoManagement_Request message to NEF via AF.

[0218] A CAG operator can request the AF to configure / change / update / manage the CAG configuration for a specific 5G femto. Based on this, the AF can send the Nnef_FemtoManagement_Request message to the NEF. The Nnef_FemtoManagement_Request message can include information about the target 5G femto and / or CAG configuration information.

[0219] The Nnef_FemtoManagement_Request message may contain some or all of the following information. Additionally, the Nnef_FemtoManagement_Request message may explicitly, implicitly, or implicitly contain the following information:

[0220] - Information for target 5G Femto

[0221] - CAG configuration

[0222] The information for the target 5G Femto may include some or all of the following information:

[0223] - Global RAN Node ID(s)

[0224] - RAN Node Name(s)

[0225] - Area of ​​interest (e.g. TAI list and / or geographic area)

[0226] - IP address(es)

[0227] - CAG business information

[0228] - Femto-spreader information

[0229] - 5G Femto serial / manufacturing number

[0230] If a network operator assigns a different TAI to each 5G femto, AMF, SMF, NRF, NEF, etc. within 5GC may identify the 5G femto based on the TAI.

[0231] The above CAG configuration may include some or all of the following information:

[0232] - Target CAG ID(s)

[0233] - Indication on enabling or disabling broadcasting of CAG information in SIB

[0234] - Supported CAG list in Target 5G Femto(s)

[0235] - All access indication (This may indicate that access via the 5G femto is allowed to all terminals)

[0236] - Indication on enabling or disabling CAG-based access control

[0237] A CAG operator can change whether to transmit to the terminal a list of CAGs (pre-)configured in the target 5G femto by including them in the SIB using the information included in the CAG configuration.

[0238] Alternatively, the CAG operator may manage / change the settings of the target 5G femto, such as requesting the target 5G femto to transmit additional CAG ID(s) that are not (pre-)configured in the SIB or providing a list of CAGs, using the information included in the CAG settings.

[0239] 5) Step 5

[0240] NEF can request AMF ID information currently serving the target 5G femto by sending Nnrf_NFDiscovery_Request message to NRF.

[0241] The contents of TS 23.502 v18.4.0 may be applied to existing input parameters included in the Nnrf_NFDiscovery_Request message.

[0242] Additionally, the Nnrf_NFDiscovery_Request message may contain some or all of the following information:

[0243] - Information for target 5G Femto

[0244] - The above NEF can support 5G Femto.

[0245] The information for the target 5G Femto may include some or all of the following information:

[0246] - Global RAN Node ID(s)

[0247] - RAN Node Name(s)

[0248] - Area of ​​interest (e.g. TAI list and / or geographical area)

[0249] - IP address(es)

[0250] - CAG business information

[0251] - Femto-spreader information

[0252] - 5G Femto serial / manufacturing number

[0253] 6) Step 6

[0254] Based on the information received from the AMF in Step 2 and the information received from the NEF in Step 5 (information about the target 5G femto), the NRF can determine the AMF serving the target 5G femto. Based on this, the NRF can include the ID of the AMF serving the target 5G femto in the Nnrf_NFDiscovery_Response message and send it to the NEF.

[0255] If the target 5G femto performs multiple AMF and NG settings, the NRF may transmit multiple AMF ID information to the NEF.

[0256] Alternatively, if the target 5G femto performs multiple AMF and NG configurations, the NRF may transmit the ID information of only one AMF among the multiple AMFs to the NEF.

[0257] If in Step 5, NRF receives an Area of ​​Interest consisting of a geographical area, NRF may convert the geographical area into a TAI list format and transmit it to NEF by referring to the 5G Femto information provided by AMF in Step 2 (and / or information configured in NRF, etc.).

[0258] If in Step 5, NRF receives information about a target 5G femto, which consists of RAN node name(s), region of interest and / or IP address(es), NRF may also find the global RAN node ID(s) for the target 5G femto based on the 5G femto information provided by AMF in Step 2 and transmit it to NEF.

[0259] 7) Step 7

[0260] Based on the information received from NRF, NEF may request the AMF currently serving the target 5G Femto to set / change / update / manage the CAG configuration for the target 5G Femto by sending a Namf_FemtoCAGManagement_Request message.

[0261] If NEF is provided with information on multiple AMFs, NEF may select one of them and transmit the request message to it.

[0262] Based on the information received in Steps 4 and 6, NEF may include some or all of the following information in the Namf_FemtoCAGManagement_Request message:

[0263] - Information for target 5G Femto

[0264] - CAG configuration

[0265] The information for the target 5G Femto may include some or all of the following information:

[0266] - Global RAN Node ID(s)

[0267] - RAN Node Name(s)

[0268] - Target TAI list

[0269] - IP address(es)

[0270] - CAG business information

[0271] - Femto-spreader information

[0272] - 5G Femto serial / manufacturing number

[0273] The above CAG configuration may include some or all of the following information:

[0274] - Target CAG ID(s)

[0275] - Indication on enabling or disabling broadcasting of CAG information in SIB

[0276] - Supported CAG list in Target 5G Femto(s)

[0277] - All access indication (This may indicate that access via the 5G femto is allowed to all terminals)

[0278] - Indication on enabling or disabling CAG-based access control

[0279] 8) Step 8

[0280] Based on the information about the target 5G femto received in Step 7, the AMF can send an AMF CONFIGURATION UPDATE message to the target 5G femto to request configuration / change / update of a specific CAG.

[0281] The AMF CONFIGURATION UPDATE message may contain CAG configuration provisioning / update information.

[0282] The above CAG configuration provisioning / update information may include some or all of the following information: The above CAG configuration provisioning / update information may explicitly, implicitly, or implicitly include the following information:

[0283] - Target CAG ID(s)

[0284] - Enabling or disabling broadcasting of CAG information in SIB

[0285] - All access indication (This may indicate that access via the 5G femto is allowed to all terminals)

[0286] - Indication on enabling or disabling CAG-based access control

[0287] - Target TAI list

[0288] 9) Step 9

[0289] Based on the CAG configuration provisioning / update information received in Step 8, the 5G Femto can update and broadcast (transmit to the terminal) SIB1 information.

[0290] The above SIB1 information may include an updated / changed Supported CAG list based on the information received in step 8. For example, based on the target TAI list of the received information, the 5G Femto may update the Supported CAG list. The 5G Femto may broadcast the updated Supported CAG list by including it in SIB1.

[0291] When 5G Femto is separated into CU and DU, the CU of 5G Femto can transmit the information received in Step 8 to the DU, and the DU can update and broadcast (transmit to the terminal) SIB information based on the information received from the CU.

[0292] If the AMF CONFIGURATION UPDATE message received in Step 8 is a request to stop SIB broadcasting for specific CAG ID(s), the 5G Femto may broadcast (transmit to the UE) SIB1 without including the CAG ID(s).

[0293] Alternatively, if the AMF CONFIGURATION UPDATE message received in Step 8 is a request to stop broadcasting SIBs for specific CAG ID(s), the 5G Femto may also broadcast a separate indication in the SIB to ignore the specific CAG ID(s) (or to indicate that access is allowed regardless of CAG, or to indicate that access is allowed to all terminals).

[0294] 5G Femto can additionally perform the following access control operations for terminal(s) in RRC_CONNECTED state:

[0295] - If 5G Femto needs to exclude some CAG ID(s) from the supported CAG list transmitted as SIB (if the CAG list is updated with some CAG IDs excluded from the existing CAG list), 5G Femto may handover or RRC release UE(s) in RRC_CONNECTED state whose Allowed CAG list consists only of some of the excluded CAG ID(s) (or UEs whose Allowed CAG list does not include any CAG ID(s) in the updated Supported CAG list) to the neighboring NG-RAN.

[0296] - If 5G Femto needs to transmit SIB without any CAG ID(s) information or with an indication to ignore all CAG ID(s), 5G Femto may maintain the connection with the terminal(s) in RRC_CONNECTED state.

[0297] If the AMF CONFIGURATION UPDATE message requests SIB broadcasting for specific CAG ID(s), 5G Femto may transmit SIB1 with the CAG ID(s) added.

[0298] 5G Femto can additionally perform the following access control operations for terminal(s) in RRC_CONNECTED state:

[0299] - If 5G Femto needs to add some CAG ID(s) to the supported CAG list being transmitted as SIB (if the CAG list is updated with some CAG IDs added to the existing CAG list), 5G Femto may maintain the connection with the terminal(s) in RRC_CONNECTED state.

[0300] - In case 5G Femto needs to transmit some CAG ID(s) by adding them to the supported CAG list while SIB does not include any CAG ID(s) information, 5G Femto may handover or RRC release the terminal(s) in RRC_CONNECTED state that is composed only of the Allowed CAG list that does not include some of the added CAG ID(s) (or the terminal(s) in RRC_CONNECTED state that does not have the Allowed CAG list that includes some of the added CAG ID(s)) to the surrounding NG-RAN.

[0301] The terminal can determine / decide whether it can access the 5G femto based on the SIB transmitted from the 5G femto. If access is possible, the terminal can transmit a registration request message to the 5G femto. Then, the base station can forward the received registration request message to the AMF via the INITIAL UE MESSAGE. At this time, the base station can include the 'supported CAG list' broadcast by the base station in the cell currently accessed by the terminal in the Cell CAG List IE information and transmit it to the AMF.

[0302] 10) Step 10

[0303] 5G Femto can notify the AMF of the results of configuration / update for the CAG configuration by sending an AMF CONFIGURATION UPDATE ACKNOWLEDGE message.

[0304] AMF can receive information on the list of supported CAGs for 5G Femto during the NG setup process and the NG-RAN configuration update process.

[0305] Alternatively, AMF can receive the list of supported CAGs for 5G Femto from AF via Step 7 (and Step 4).

[0306] Alternatively, if the 5G Femto has only one serving cell, the AMF may also know the supported CAG list information through the Cell CAG List IE information included in the initial UE message (INITIAL UE MESSAGE) transmitted by the 5G Femto during the terminal registration process.

[0307] The AMF can receive an All Access Indication from the AF via Step 7 (and Step 4). Through the received All Access Indication, the AMF can explicitly inform all terminals that they can access the 5G Femto.

[0308] Alternatively, based on the supported CAG list information of 5G Femto and the CAG configuration received by AF, AMF can implicitly be informed that all terminals can access via that 5G Femto.

[0309] If the 5G femto performs NG setup with multiple AMFs, the NEF may transmit the message of Step 7 to all of the multiple AMFs. At this time, the NEF may instruct only one AMF among the multiple AMFs to transmit the CAG setup provisioning / update information to the target 5G femto, and instruct the other AMF(s) not to transmit the CAG setup provisioning / update information to the target 5G femto. This may be to ensure that only the single AMF references / utilizes the information (CAG setup provisioning / update information).

[0310] Alternatively, if the 5G femto performs NG setup with multiple AMFs, the NEF may instruct only one of the multiple AMFs to transmit CAG configuration provisioning / update information to the target 5G femto. Thereafter, the target 5G femto may notify the other AMF(s) of the updated CAG configuration information through a RAN Configuration Update procedure.

[0311] AMF can perform the following access control actions on terminal(s) in CM_CONNECTED state:

[0312] - If 5G Femto needs to exclude some CAG ID(s) from the supported CAG list transmitted in SIB, AMF may initiate AN release procedure for UE(s) in RRC_CONNECTED state whose Allowed CAG list consists only of some of the excluded CAG ID(s) (or UEs whose Allowed CAG list does not include any of the CAG ID(s) in the updated Supported CAG list) or request 5G Femto to perform handover for the UE(s).

[0313] - If 5G Femto needs to transmit SIB without any CAG ID(s) information or with an indication to ignore all CAG ID(s), 5G Femto may maintain the connection with the terminal(s) in RRC_CONNECTED state.

[0314] - If 5G Femto needs to add some CAG ID(s) to the list of supported CAGs transmitted as SIB, AMF may keep the connection with the terminal(s) in CM_CONNECTED state.

[0315] - If 5G Femto needs to transmit some CAG ID(s) by adding them to the supported CAG list while the SIB does not contain any CAG ID(s) information, AMF may initiate an AN release procedure for the UE(s) in RRC_CONNECTED state that consists only of the Allowed CAG list that does not include some of the added CAG ID(s) or request 5G Femto to perform a handover for the UE(s).

[0316] The above operation can be performed based on the AMF CONFIGURATION UPDATE ACKNOWLEDGE message (result of configuration / update for CAG configuration) received from the 5G Femto.

[0317] Alternatively, the above operation can be performed based on the CAG list received from the 5G Femto in step 1 (if the CAG list was delivered in step 1) and the CAG list received from the NEF in step 7.

[0318] 11) Step 11

[0319] AMF can notify NEF of the results of configuration / update of the above CAG configuration by sending Namf_FemtoCAGManagement_Response message.

[0320] 12) Step 12

[0321] NEF can notify AF of the results of configuration / update for the above CAG configuration by sending the Nnef_FemtoManagement_Response message.

[0322] When a CAG operator requests CAG configuration settings / changes / updates / management for a specific 5G femto device via AF, the specific 5G femto device may not yet be installed / operated. That is, Steps 1 through 3 may not have been performed before Step 4. In this case, the following actions may be performed:

[0323] - The NRF that received Step 5 may fail to find an AMF serving the target 5G Femto and may notify this to the NEF through Step 6.

[0324] - NEF can request NRF to notify it when an NG interface is created between the target 5G Femto and AMF by sending the Nnrf_NFManagement_NFStatusSubscribe message.

[0325] - When the above target 5G femto is installed and the NG setup process is in progress, AMF can store information about the target 5G femto to NRF through Step 2.

[0326] - Based on this, NRF can send NEF an Nnrf_NFManagement_NFStatusNotify message including AMF ID information serving the target 5G femto to notify that an NG interface between the target 5G femto and the serving AMF has been created.

[0327] - Based on this, NEF can perform Step 7.

[0328] When CAG configuration information is set / updated / changed, the 5G Femto (NG-RAN) may transmit the set / updated / changed CAG configuration information to the surrounding 5G Femto (NG-RAN)(s) via the Xn interface. This action may be at the request of the AMF.

[0329] In this specification, CAG ID(s) (or supported CAG list) are described as being transmitted via SIB1 by 5G Femto, but may also be transmitted via other SIBs.

[0330] In this specification, CAG operators can dynamically change / manage CAG configurations for individually installed 5G femtos, thereby controlling access of terminal(s) based on specific times (and / or locations, etc.).

[0331] The following actions can be performed:

[0332] - AF can transmit to 5G Femto a list of CAGs to be included in the SIB.

[0333] - AF may request NEF to provision / update / change CAG settings for a specific 5G femto.

[0334] - After NEF obtains the ID information of the AMF serving the 5G femto through NRF, NEF can request CAG setting provisioning / update / change to the 5G femto through the AMF.

[0335] - 5G Femto can configure / update SIB contents and notify the terminal based on the request for CAG configuration provisioning / update / change received through AMF.

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

[0337] Figure 8 illustrates the procedure of AMF according to the disclosure of this specification.

[0338] 1. AMF (Access Mobility Function) can receive NG setup requests from specific Femto.

[0339] 2. Based on the above NG setting request, the AMF can transmit information about the specific femto to the NRF (Network Repository Function).

[0340] 3. The above AMF can receive an update request message for the CAG (Closed Access Group) configuration of the target femto from the NEF (Network Exposure Function).

[0341] The above update request message may include information about the target femto and the requested CAG settings.

[0342] 4. Based on the target femto being the specific femto, the AMF can transmit an update message to the specific femto.

[0343] The above update message may include a request to update the CAG settings of the specific femto to the requested CAG settings.

[0344] The information about the specific femto and the information about the target femto may include at least one of the ID, name, TAI (Tracking Area Identity), installer information, and serial number of the specific femto.

[0345] The above requested CAG configuration may include a target CAG ID.

[0346] The requested CAG configuration may include a Supported CAG list in Target 5G Femto.

[0347] The above update message may be an AMF CONFIGURATION UPDATE message.

[0348] The requested CAG configuration may include an indication that the target femto allows access to all UEs.

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

[0350] Figure 9 illustrates the NEF procedure according to the disclosure of this specification.

[0351] 1. The Network Exposure Function (NEF) can receive a first update request message for the CAG (Closed Access Group) configuration of the target Femto from the Application Function (AF).

[0352] The first update request message may include information about the target femto and the requested CAG settings.

[0353] 2. Based on the first update request message, the NEF can send a discovery request message to the NRF (Network Repository Function).

[0354] The above discovery request message may include information about the target femto.

[0355] 3. Based on the discovery request message, the NEF can receive the ID of the serving AMF (Access Mobility Function) for the target femto from the NRF.

[0356] 4. The NEF may send a second update request message for the CAG settings of the target femto to the serving AMF.

[0357] The second update message may include information about the target femto and the requested CAG settings.

[0358] The information about the target femto may include at least one of the ID, name, TAI (Tracking Area Identity), installer information, and serial number of the specific femto.

[0359] The above requested CAG configuration may include a target CAG ID.

[0360] The requested CAG configuration may include a Supported CAG list in Target 5G Femto.

[0361] The requested CAG configuration may include an indication that the target femto allows access to all UEs.

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

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

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

[0365] The operations performed by the processor include: receiving, by an Access Mobility Function (AMF), a Next-Generation (NG) configuration request from a specific Femto; transmitting, by the AMF, information about the specific Femto to a Network Repository Function (NRF) based on the NG configuration request; receiving, by the AMF, an update request message for a Closed Access Group (CAG) configuration of a target Femto from a Network Exposure Function (NEF); transmitting, by the AMF, an update message to the specific Femto, the update request message including information about the target Femto and a requested CAG configuration, and based on the target Femto being the specific Femto, the update message may include a request for updating the CAG configuration of the specific Femto to the requested CAG configuration.

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

[0367] The operations performed by the processor include: an AMF (Access Mobility Function) receiving a NG (Next-Generation) configuration request from a specific femto; a AMF transmitting information about the specific femto to an NRF (Network Repository Function) based on the NG configuration request; a AMF receiving an update request message for a CAG (Closed Access Group) configuration of a target femto from an NEF (Network Exposure Function); the update request message including information about the target femto and a requested CAG configuration, and a AMF transmitting an update message to the specific femto based on the target femto being the specific femto, wherein the update message may include a request for updating the CAG configuration of the specific femto to the requested CAG configuration.

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

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

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

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

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

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

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

[0375] The one or more stored commands include: an Access Mobility Function (AMF) receiving a Next-Generation (NG) configuration request from a specific Femto; a step in which the AMF transmits information about the specific Femto to a Network Repository Function (NRF) based on the NG configuration request; a step in which the AMF receives an update request message for a Closed Access Group (CAG) configuration of a target Femto from a Network Exposure Function (NEF); the update request message includes information about the target Femto and a requested CAG configuration, and a step in which the AMF transmits an update message to the specific Femto based on the target Femto being the specific Femto, wherein the update message may include a request for updating the CAG configuration of the specific Femto to the requested CAG configuration.

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

[0377] This specification may have various effects.

[0378] For example, CAG settings can be dynamically managed through the procedures disclosed herein.

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

[0380] 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.< / femto>

Claims

1. As a method, A step in which AMF (Access Mobility Function) receives an NG setup request from a specific Femto; A step in which the AMF transmits information about the specific femto to the NRF (Network Repository Function) based on the above NG setting request; A step in which the above AMF receives an update request message for the CAG (Closed Access Group) configuration of the target femto from the NEF (Network Exposure Function); The above update request message includes information about the target femto and the requested CAG settings, A step of the AMF transmitting an update message to the specific femto based on the target femto being the specific femto, A method wherein said update message includes a request to update the CAG settings of said particular femto to the requested CAG settings.

2. In paragraph 1, A method wherein the information about the specific femto and the information about the target femto include at least one of an ID, a name, a Tracking Area Identity (TAI), information about the installer, and a serial number of the specific femto.

3. In paragraph 1 or 2, The above requested CAG setting comprises a target CAG ID.

4. In any one of the clauses 1 to 3, The above requested CAG configuration method includes a Supported CAG list in Target 5G Femto.

5. In any one of paragraphs 1 to 4, The above update message is an AMF CONFIGURATION UPDATE message.

6. In any one of paragraphs 1 to 5, A method wherein the requested CAG setup includes an indication that the target femto allows access to all UEs.

7. As a method, A step in which the Network Exposure Function (NEF) receives a first update request message for the CAG (Closed Access Group) configuration of the target Femto from the Application Function (AF); The above first update request message includes information about the target femto and the requested CAG settings, A step of the NEF transmitting a discovery request message to the NRF (Network Repository Function) based on the first update request message; The above discovery request message includes information about the target femto, Based on the discovery request message, the NEF receives an ID of a serving AMF (Access Mobility Function) for the target femto from the NRF; The step of the NEF sending a second update request message for the CAG settings of the target femto to the serving AMF, A method wherein the second update message includes information about the target femto and the requested CAG settings.

8. In paragraph 7, The information about the target femto comprises at least one of the ID, name, TAI (Tracking Area Identity), installer information, and serial number of the specific femto.

9. In paragraph 7 or 8, The above requested CAG setting comprises a target CAG ID.

10. In any one of paragraphs 7 to 9, The above requested CAG configuration method includes a Supported CAG list in Target 5G Femto.

11. In any one of the clauses 7 to 10, A method wherein the requested CAG setup includes an indication that the target femto allows access to all UEs.

12. As an AMF (Access Mobility Function) that performs communication, At least one transmitter and receiver; comprising at least one processor, The operation performed by said at least one processor is an AMF method according to any one of claims 1 to 6.

13. As a Network Exposure Function (NEF) that performs communication, At least one transmitter and receiver; comprising at least one processor, The operation performed by said at least one processor is a NEF method according to any one of claims 7 to 11.

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

15. A non-volatile computer-readable storage medium that records commands, A nonvolatile computer-readable storage medium which, when executed by one or more processors, causes the one or more processors to perform a method according to any one of claims 1 to 6.

Images