Method and apparatus for managing closed access group information

Abstract

Embodiments of the present invention provide a method for managing CAG information. The method includes receiving, by an access and mobility management function (AMF) (200), a registration request message for registering to a network from a user equipment (UE) (100) through a cell. In addition, the method includes determining, by the AMF (200), that the UE (100) is one of the following: when the cell is a CAG cell, the UE is not authorized to the cell, and when the cell is a non-CAG cell, the UE is authorized to access the network only through the CAG cell. In addition, the method includes sending, by the AMF (200), a registration rejection message to the UE (100), wherein the registration rejection message includes a CAG information list.

Description

Technical Field

[0001] The present disclosure relates to electronic devices, and more particularly, to methods and devices for managing Closed Access Group (CAG) information. Background Art

[0002] In order to meet the demand for wireless data services that has increased since the deployment of the fourth generation (4G) communication system, efforts have been made to develop an improved fifth generation (5G) or pre-5G communication system. 5G or pre-5G communication systems are also referred to as "beyond 4G networks" or "post-Long Term Evolution (LTE) systems". 5G communication systems are considered to be implemented in higher frequency (mmWave) bands, such as the 60 GHz band, in order to achieve higher data rates. In order to reduce the propagation loss of radio waves and increase the transmission distance, beamforming, massive multiple input multiple output (MIMO), full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive antenna technology are discussed with respect to 5G communication systems. In addition, in 5G communication systems, development of system network improvements is being carried out based on advanced small cells, cloud radio access networks (RAN), ultra-dense networks, device-to-device (D2D) communications, wireless backhaul, mobile networks, cooperative communications, coordinated multi-point (CoMP), receiving-end interference elimination, etc. In 5G systems, hybrid frequency shift keying (FSK) and Firth quadrature amplitude modulation (FQAM) and sliding window superposition coding (SWSC) as advanced coded modulation (ACM), and filter bank multi-carrier (FBMC), non-orthogonal multiple access (NOMA) and sparse code multiple access (SCMA) as advanced access technologies have been developed.

[0003] The Internet is a human-centered connected network where humans generate and consume information, and is now developing into the Internet of Things (IoT), where distributed entities such as things exchange and process information without human intervention. The Internet of Everything (IoE) is a combination of IoT technology and big data processing technology through connection with cloud servers. As a technical element, connected network technology such as humans generating and consuming information is now developing into the Internet of Things (IoT), where ud servers have realized emeIoT, sensor networks, machine-to-machine (M2M) communication, machine type communication (MTC), etc. are already under development. This IoT environment can provide intelligent Internet technology services that create new value for human life by collecting and analyzing data generated between connected things. Through the integration and combination between existing information technology (IT) and various industrial applications, IT can be applied to various fields, including smart homes, smart buildings, smart cities, smart cars or connected cars, smart grids, healthcare, smart devices, and advanced medical services.

[0004] In line with this, various attempts have been made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, MTC, and M2M communications can be implemented through beamforming, MIMO, and array antennas. The application of cloud RAN, which is the above-mentioned big data processing technology, can also be considered an example of the fusion between 5G technology and IoT technology.

[0005] As described above, various services can be provided according to the development of wireless communication systems, and thus a method for easily providing such services is required. Summary of the invention

[0006] [Technical solution]

[0007] The main purpose of the embodiments of this document is to provide a method and system for managing CAG information.

[0008] Another object of embodiments herein is to determine that a user equipment (UE) is not authorized to a CAG cell in response to receiving a registration request message for registering to a network from the user equipment (UE) through the CAG cell.

[0009] Another object of embodiments herein is to determine that the UE is authorized to access the network only through the CAG cell in response to receiving a registration request message for registering to the network from the UE through a non-CAG cell.

[0010] Another object of an embodiment of the present invention is to send a registration rejection message to a UE, the registration rejection message including a CAG information list, wherein the CAG information list includes zero entries or at least one of the following: a public land mobile network identifier PLMN ID, an authorized CAG list including zero or more CAG IDs, and an indication that the UE is only allowed to access the network through the CAG cell. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] The method and device are illustrated in the accompanying drawings, in which the same reference numerals represent corresponding parts in the various drawings. The embodiments herein will be better understood from the following description with reference to the accompanying drawings, in which:

[0012] Figure 1 is a block diagram of a system for managing CAG information according to embodiments disclosed herein;

[0013] Figure 2A is a flowchart illustrating a method for obtaining a CAG information list from an AMF by a UE according to an embodiment disclosed herein;

[0014] Figure 2B is a flowchart illustrating a method for providing a CAG information list to a UE by an AMF according to an embodiment disclosed herein; and

[0015] Figure 3 is a sequence diagram illustrating signaling between an AMF and a UE for managing CAG information to register the UE to a network according to embodiments disclosed herein;

[0016] Figure 4 Schematically illustrates an access and mobility management function (AMF) according to an embodiment of the present disclosure; and

[0017] Figure 5 A user equipment (UE) according to an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0018] [Best Mode]

[0019] Therefore, an embodiment of the present invention provides a method for managing CAG information. The method includes receiving, by an access and mobility management function (AMF), a registration request message for registering to a network from a user equipment (UE) through a cell. In addition, the method includes determining, by the AMF, that the UE is one of the following: when the cell is a CAG cell, the UE is not authorized to the cell, and when the cell is a non-CAG cell, the UE is authorized to access the network only through the CAG cell. In addition, the method includes sending, by the AMF, a registration rejection message to the UE, wherein the registration rejection message includes a CAG information list.

[0020] In one embodiment, the registration request message is one of an initial registration request and a mobility and periodic registration update request message.

[0021] In one embodiment, the CAG information list includes zero entries or at least one of the following: a public land mobile network identifier (PLMN ID), an allowed CAG list including zero or more CAG IDs, and an indication indicating that the UE is only allowed to access the network through a CAG cell.

[0022] Accordingly, an embodiment of the present invention provides a method for managing CAG information. The method includes sending, by the UE, a registration request message for registering to the network to the AMF through a cell. In addition, the method includes receiving, by the UE, a registration rejection message including a CAG information list from the AMF in response to the AMF determining that the UE is one of the following: when the cell is a CAG cell, the UE is not authorized to the cell, and when the cell is a non-CAG cell, the UE is authorized to access the network only through the CAG cell.

[0023] In one embodiment, the UE operates in one of an automatic network selection mode and a manual network selection mode.

[0024] In one embodiment, the method includes storing, by the UE, the CAG information in a memory of the UE or a universal integrated circuit card (UICC) coupled to the UE.

[0025] In one embodiment, the method includes selecting, by the UE, a CAG cell based on a CAG information list received in a registration rejection message. In addition, the method includes sending, by the UE, a registration request message to the AMF via the CAG cell. In addition, the method includes receiving, by the UE, a registration acceptance message from the AMF.

[0026] Accordingly, an embodiment of the present invention provides an AMF for managing CAG information. The AMF includes a CAG information controller, a memory, and a processor, wherein the CAG information controller is coupled to the memory and the processor. The CAG information controller is configured to receive a registration request message for registering to a network from a UE through a cell. The CAG information controller is configured to determine whether the UE is one of the following: when the cell is a CAG cell, the UE is not authorized to the cell, and when the cell is a non-CAG cell, the UE is authorized to access the network only through the CAG cell. The CAG information controller is configured to send a registration rejection message to the UE, wherein the registration rejection message includes a CAG information list.

[0027] In one embodiment, the registration request message is one of an initial registration request and a mobility and periodic registration update request message.

[0028] In one embodiment, the CAG information list includes zero entries or at least one of the following: a public land mobile network identifier (PLMN ID), an allowed CAG list including zero or more CAG IDs, and an indication indicating that the UE is only allowed to access the network through a CAG cell.

[0029] Accordingly, an embodiment of the present invention provides a UE for managing CAG information. The UE includes a CAG information controller, a memory, and a processor, wherein the CAG information controller is coupled to the memory and the processor. The CAG information controller is configured to send a registration request message for registering to a network to the AMF through a cell. The CAG information controller is configured to receive a registration rejection message including a CAG information list from the AMF in response to the AMF determining that the UE is one of the following: when the cell is a CAG cell, the UE is not authorized to the cell, and when the cell is a non-CAG cell, the UE is authorized to access the network only through the CAG cell.

[0030] In one embodiment, the registration request message is one of an initial registration request and a mobility and periodic registration update request message.

[0031] In one embodiment, the UE operates in one of an automatic network selection mode and a manual network selection mode.

[0032] In one embodiment, the CAG information list includes zero entries or at least one of the following: a public land mobile network identifier (PLMN ID), an allowed CAG list including zero or more CAG IDs, and an indication indicating that the UE is only allowed to access the network through a CAG cell.

[0033] In one embodiment, the CAG information controller is configured to store the CAG information to a memory of the UE or to a Universal Integrated Circuit Card (UICC) coupled to the UE.

[0034] In one embodiment, the CAG information controller is configured to: select a CAG cell based on a CAG information list received in a registration reject message, send a registration request message to the AMF through the CAG cell, and receive a registration accept message from the AMF.

[0035] These and other aspects of the embodiments herein will be better understood and appreciated when considered in conjunction with the following description and accompanying drawings. However, it should be understood that the following description, although indicating preferred embodiments and many of their specific details, is provided by way of illustration and not limitation. Many changes and modifications may be made within the scope of the embodiments herein without departing from the spirit of the present invention, and the embodiments herein include all such modifications.

[0036] [Invention Mode]

[0037] The embodiments herein and their various features and advantageous details will be explained more fully with reference to the non-limiting embodiments shown in the accompanying drawings and described in detail in the following description. The description of well-known components and processing techniques is omitted so as not to unnecessarily obscure the embodiments herein. In addition, the various embodiments described herein are not necessarily mutually exclusive, because some embodiments can be combined with one or more other embodiments to form new embodiments. Unless otherwise stated, the term "or" used herein refers to a non-exclusive or. The examples used herein are intended only to help understand the way in which the embodiments herein can be practiced, and further enable those skilled in the art to practice the embodiments herein. Therefore, the embodiments should not be interpreted as limiting the scope of the embodiments herein.

[0038] The term "coupling" and its derivatives refer to any direct or indirect communication between two or more elements, whether or not these elements are in physical contact with each other. The terms "send", "receive" and "communication" and their derivatives include direct and indirect communication. The terms "include" and "comprise" and their derivatives are meant to include without limitation. The term "or" is inclusive, meaning and / or. The phrase "associated with..." and its derivatives mean to include, be included in, interconnect with, include, be included in, be connected to or connected with, be coupled to or coupled with, communicate with, collaborate with, interweave, parallel, approach, be bound to or bound with, have, have the characteristics of, have a relationship with, etc. The term "controller" refers to any device, system or part thereof that controls at least one operation. Such a controller can be implemented with hardware or a combination of hardware and software and / or firmware. The functions associated with any particular controller can be centralized or distributed, whether local or remote. The phrase "at least one of," when used with a list of items, means that different combinations of one or more of the listed items may be used, and only one of the items in the list may be required. For example, "at least one of A, B, and C" includes any of the following combinations: A, B, C, A and B, A and C, B and C, and A and B and C.

[0039] In addition, the various functions described below can be implemented or supported by one or more computer programs, each of which is formed by a computer-readable program code and is contained in a computer-readable medium. The terms "application" and "program" refer to one or more computer programs, software components, instruction sets, processes, functions, objects, classes, instances, related data, or parts thereof suitable for implementation in appropriate computer-readable program codes. The phrase "computer-readable program code" includes any type of computer code, including source code, object code, and executable code. The phrase "computer-readable medium" includes any type of medium that can be accessed by a computer, such as a read-only memory (ROM), a random access memory (RAM), a hard drive, a compact disc (CD), a digital video disc (DVD), or any other type of memory. "Non-transitory" computer-readable media excludes wired, wireless, optical, or other communication links that transmit temporary electrical signals or other signals. A non-transitory computer-readable medium includes a medium that can permanently store data, and a medium that can store data and then rewrite data, such as a rewritable optical disc or an erasable storage device.

[0040] Definitions for certain other words and phrases are provided throughout this patent document. Those skilled in the art should understand that in many, if not most, instances, such definitions apply to both past and future tenses of such defined words and phrases.

[0041] As is conventional in the art, embodiments may be described and illustrated in terms of blocks that perform one or more functions described. These blocks may be referred to herein as managers, units, modules, hardware components, etc., which are physically implemented by analog and / or digital circuits, such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hard-wired circuits, etc., and may be optionally driven by firmware and software. For example, the circuit may be embodied in one or more semiconductor chips, or on a substrate support such as a printed circuit board. The circuits that constitute the blocks may be implemented by dedicated hardware, or by a processor (e.g., one or more programmed microprocessors and associated circuits), or by a combination of dedicated hardware to perform some functions of the blocks, and by a processor to perform other functions of the blocks. Without departing from the scope of the present disclosure, each block of the embodiment may be physically divided into two or more interactive and discrete blocks. Similarly, without departing from the scope of the present disclosure, the blocks of the embodiment may be physically combined into more complex blocks.

[0042] CAG is a group of users who are approved to access the network through one or more licensed CAG cells that are allowed to connect. Typically, the user equipment (UE) of the CAG user is pre-configured with CAG information, which includes a list of licensed CAGs and optionally an indication. The licensed CAG list includes a list ID of licensed CAG cells. The indication indicates that the UE is allowed to access the network only through the CAG cell. In another method, the network sends CAG information in a registration accept message during a NAS process (e.g., a registration process or a UE configuration update process) for registering the UE through the CAG cell. In addition, the UE can access the CAG service from the network through the licensed CAG cell in the licensed CAG cell list.

[0043] In an example scenario, a universal integrated circuit card (UICC) is inserted into the UE for the first time, wherein the UICC includes a universal user identity module (USIM) application with a CAG subscription universal integrated circuit card (UICC). Considering that CAG information is not available at the UE, allowed CAG cells and non-CAG cells (i.e., normal cells) of a public land mobile network (PLMN) are available at the UE's geographical location. Since the UE does not have CAG information (i.e., indication), the UE accesses the non-CAG cell to send a registration request message to the access and mobility management function AMF of the network.

[0044] When the AMF receives a Registration Request message through a non-CAG cell, the AMF rejects the UE's request and sends a Registration Reject message because the UE should not access the non-CAG cell according to the CAG subscription. In addition, the UE never registers for the CAG subscription and camps on the CAG cell. Therefore, the UE loses the opportunity to access all CAG services.

[0045] In another example scenario, the UE accesses CAG services (i.e., PDU sessions) through a licensed CAG cell, where a list of CAG IDs is available at the UE. Consider that the UE arrives at a geographical location where coverage of the CAG cell is unavailable. In addition, the UE initiates a mobility registration request to the AMF through a non-CAG cell and receives an indication in a registration reject message from the AMF. Upon receiving the indication, the UE initiates EU3: Roaming Unlicensed State and deletes all PDU sessions related to the CAG. In addition, the CAG service is interrupted at the UE. It is therefore desirable to address the above-mentioned shortcomings or at least provide a useful alternative.

[0046] Therefore, an embodiment of the present invention provides a method for managing CAG information. The method includes receiving, by an access and mobility management function (AMF), a registration request message for registering to a network from a user equipment (UE) through a cell. In addition, the method includes determining, by the AMF, that the UE is one of the following: when the cell is a CAG cell, the UE is not authorized to the cell, and when the cell is a non-CAG cell, the UE is authorized to access the network only through the CAG cell. In addition, the method includes sending, by the AMF, a registration rejection message to the UE, wherein the registration rejection message includes a CAG information list.

[0047] Unlike existing methods and systems, the proposed method allows the UE to obtain CAG information, including the permitted CAG list and the CAG-only indication, as part of the registration reject message from the AMF. The UE uses the CAG information to immediately select and camp on the CAG cell corresponding to the CAG ID in the permitted CAG list and access the CAG service as quickly as possible.

[0048] In addition, the proposed method allows the UE to immediately know that the UE is only allowed to access the network through the CAG cell by providing a CAG-only indication in a Registration Reject message or a Registration Accept message to the UE 100. Therefore, the UE 100 does not reselect or select a non-CAG cell and does not lose the CAG service.

[0049] Referring now to the drawings and more particularly to Figures 1 to 3 , which shows a preferred embodiment.

[0050] Figure 1is a block diagram of a system for managing CAG information according to an embodiment disclosed herein. In one embodiment, the system includes a UE (100), an AMF (200), and a universal integrated circuit card (UICC) (300), wherein the UICC (300) is coupled to the UE (100). The UICC (300) includes a universal user identity module (USIM) application with a CAG subscription. The AMF (200) is part of a network. Examples of networks are a 5G core network (5GC), a next generation radio access network (NG-RAN), and a 5G system (5G).

[0051] Examples of UE (100) are, but are not limited to, smart phones, tablet computers, personal digital assistants (PDAs), Internet of Things (IoT), etc. In one embodiment, UE (100) includes a CAG information controller (110), a memory (120), a processor (130), and a communicator (140). In one embodiment, the CAG information controller (110) includes a registration controller (111) and a cell detector (112). In one embodiment, AMF (200) includes a CAG information controller (210), a memory (220), a processor (230), and a communicator (240). In one embodiment, CAG information controller (210) includes a registration controller (211) and an authorization controller (212). In one embodiment, AMF (200) includes a CAG information controller (210), a memory (220), a processor (230), and a communicator (240). In one embodiment, CAG information controller (210) includes a registration controller (211) and an authorization controller (212).

[0052] The CAG information controller (110) is configured to select a cell of the PLMN to camp on in response to receiving a signal corresponding to the cell from a base station, wherein the base station is connected to the AMF (200). In one embodiment, the UE (100) operates in an automatic network selection mode or a manual network selection mode. In one embodiment, the cell is a CAG cell or a non-CAG cell.

[0053] In one embodiment, the cell detector (112) selects a cell of the PLMN to camp on in response to receiving a signal corresponding to the cell from a base station. In addition, the CAG information controller (110) is configured to initiate a non-access stratum (NAS) procedure (e.g., a registration procedure) by sending a registration request message for registering to the network to the AMF (200) via the cell. In one embodiment, the registration request message is an initial registration request or a mobility and periodic registration update request message. In one embodiment, the registration controller (111) sends a registration request message for registering to the network to the AMF (200) via the cell.

[0054] In another embodiment, even if the UE (100) does not have a CAG ID, the registration controller (111) selects and camps on a CAG cell of the PLMN to initiate a NAS process (e.g., a registration process) to the network. In one embodiment, while camping on the CAG cell, the CAG cell broadcasts the CAG ID to the UE (100). In addition, the registration controller (111) selects a CAG ID from the broadcasted CAG IDs. In addition, the registration controller (111) sends a registration request message including the selected CAG ID to the network for registration.

[0055] The CAG information controller (210) is configured to receive a registration request message from the UE (100) via a cell. In one embodiment, the registration controller (211) receives a registration request message from the UE (100) via a cell. The CAG information controller (210) is configured to determine that the UE (100) is unauthorized for the cell when the cell is a CAG cell. In one embodiment, the authorization controller (212) determines that the UE (100) is unauthorized for the cell when the cell is a CAG cell. In an example scenario, the UE (100) resides on a CAG cell, where the UE (100) is not allowed to access the CAG cell according to the current CAG subscription of the UE (100) in the network, i.e., one or more CAG identifiers broadcast by the CAG cell are in a list of permitted CAG IDs in the network. This occurs when the CAG information lists stored in the UE (100) and the network are not synchronized or the user inserts the UICC (300) into a UE (100) that does not have the CAG information list of the USIM (e.g., a brand new UE or the user removes the UICC (300) from one UE and inserts it into another UE). In addition, the UE (100) sends a registration request message to the AMF (200) through the CAG cell. In addition, the AMF (200) recognizes based on the CAG subscription of the UE (100) that the UE (100) sends the registration request message through a CAG cell that the UE (100) is not allowed to access, that is, one or more CAG identities broadcast by the CAG cell are in the list of authorized CAG IDs in the network. Therefore, the AMF (200) determines that the UE (100) is not authorized to access the CAG cell because the registration request message is received through a CAG cell that the UE (100) is not allowed to access.

[0056] In another embodiment, the CAG information controller (210) is configured to determine that the UE (100) is authorized to access the network only through the CAG cell when the UE (100) is a non-CAG cell. In one embodiment, the authorization controller (212) determines that the UE (100) is authorized to access the network only through the CAG cell when the cell is a non-CAG cell. In an example scenario, the UE (100) resides on a non-CAG cell according to a CAG subscription, wherein the UE (100) is a CAG-only UE (i.e., the UE (100) is only allowed to access the network through the CAG cell). When the CAG information list stored in the UE (100) and the network is not synchronized (i.e., according to the CAG information list stored in the UE (100), the UE (100) is allowed to access 5G through the CAG cell as well as the non-CAG cell, but on the network side, the UE (100) is allowed to access 5G only through the non-CAG cell according to the updated CAG subscription. The updated CAG subscription has not yet been updated to the UE (100)). In addition, the UE (100) sends a registration request message to the AMF (200) through a non-CAG cell. In addition, the AMF (200) recognizes that the UE (100) should send the registration request message through a CAG cell based on the CAG subscription of the UE (100), and therefore the AMF (200) determines that the UE (100) is authorized to access the network through the CAG cell.

[0057] The registration controller (211) sets the 5GMM cause value to #76 to indicate that the UE (100) is not authorized for CAG calls or is only authorized for CAG cells. The CAG information controller (210) is configured to send a registration rejection message including a CAG information list to the UE (100). In one embodiment, the CAG information list is a list of CAG information. The CAG information list includes zero entries or at least one of the following: a public land mobile network identifier (PLMN ID), a permitted CAG list including zero or more CAG IDs, and an indication that the UE (100) is only allowed to access the network through the CAG cell. The CAG-only indication is an example of the indication. In one embodiment, the registration rejection message is a NAS message or an access stratum (AS) message. In one embodiment, the registration controller (211) sends a registration rejection message to the UE (100).

[0058] In one embodiment, the CAG information list is included in the CAG information list information element in the registration reject message. The content in the registration reject message is given in Table 1.

[0059] [Table 1]

[0060]

[0061]

[0062] Table 1: Contents of the registration rejection message

[0063] The CAG information controller (110) is configured to receive a registration rejection message from the AMF (200) via a cell. In one embodiment, the registration controller (111) receives a registration rejection message from the AMF (200) via a cell.

[0064] In an embodiment, when the UE (100) is a CAG-only UE and the UE (100) does not have a CAG subscription, the AMF (200) provides a registration reject message with zero entries in the allowed CAG list to the UE (100).

[0065] In one embodiment, the registration controller (111) indicates to the AMF (200) that the permitted CAG list is empty or the permitted CAG list is not available at the UE (100). In addition, the registration controller (211) sends the permitted CAG list or only the CAG indication to the UE (100) in a NAS message or an AS message.

[0066] The CAG information controller (110) is configured to store a CAG information list in a registration rejection message to a UICC (300) or a memory (120). In one embodiment, the registration controller (111) stores the CAG information list in a registration rejection message to a UICC (300) or a memory (120). In one embodiment, the CAG information list is stored in a basic file (300) in the UICC. In one embodiment, when the basic file is available at the UICC (300), the registration controller (111) stores the CAG information list to the UICC (300). When the basic file is not available at the UICC (300), the registration controller (111) stores the CAG information list in the memory (120). The CAG information controller (110) is configured to select and reside on a CAG cell based on the CAG information list in the registration rejection message. In one embodiment, the cell detector (112) selects and resides on a CAG cell based on the CAG information list. The CAG information controller (110) is configured to send a registration request message for registering to the network to the AMF (200) through the selected CAG cell. In one embodiment, the registration controller (111) sends the registration request message to the AMF (200) through the selected CAG cell to register to the network.

[0067] The CAG information controller (210) is configured to determine that the UE (100) is authorized to the CAG cell in response to receiving a registration request message from the UE (100) via the CAG cell. In one embodiment, the authorization controller (212) determines that the UE is authorized to the CAG cell in response to receiving the registration request message from the UE (100) via the CAG cell. The CAG information controller (210) is configured to register the CAG subscription of the UE (100) in response to determining that the UE (100) is authorized to the CAG cell. In one embodiment, the registration controller (211) registers the CAG subscription of the UE (100) in response to determining that the UE (100) is authorized to the CAG cell. The CAG information controller (210) is configured to send a registration accept message to the UE (100) in response to registering the UE (100) to access the CAG service. In one embodiment, the registration controller (211) sends the registration accept message to the UE (100). In one embodiment, the registration accept message includes only a CAG indication. The CAG information controller (110) is configured to allow the UE (100) to access the CAG service in response to receiving a registration acceptance message from the AMF (200). In one embodiment, the registration controller (111) allows the UE (100) to access the CAG service in response to receiving a registration acceptance message from the AMF (200).

[0068] In an embodiment, when the UE (100) is a CAG-only UE and the UE (100) does not have a CAG subscription, the AMF (200) provides a registration accept message with zero entries in the allowed CAG list to the UE (100).

[0069] In another embodiment, when the permitted CAG list is empty or the permitted CAG list is empty,

[0070] When unavailable at the UE (100), the Registration Controller (111) sends a

[0071] In one embodiment, the registration controller sends a registration request message to re-initiate the NAS process.

[0072] (111) Restart the NAS process after a specified number of durations or indefinitely.

[0073] In one embodiment, the AMF (200) indicates in a NAS message (e.g., a Registration Reject message)

[0074] The duration and / or the specific number of times may be preconfigured in the UE (100) based on the UE implementation. In one embodiment, the registration controller (111) stops sending the registration request message in response to not receiving any subscription related to the CAG from the AMF (200) after sending the registration request message for a specific number of times.

[0075] In one embodiment, in response to receiving the CAG information list, the registration controller (111) does not find a suitable CAG cell corresponding to the CAG ID in the permitted CAG list for the UE (100) to register with the network. In addition, the registration controller (111) locally cancels the CAG subscription or sends a deregistration request on a cell of the PLMN for deregistration.

[0076] In another embodiment, when the AMF (200) receives the registration request message through the first CAG cell and determines that the UE (100) does not have any CAG subscription in the first CAG cell for at least one second CAG cell, the AMF (200) accepts the registration request message. In addition, the AMF (200) sends a registration accept message including an allowed CAG list and / or a CAG-only indication.

[0077] In another embodiment, when the AMF (200) receives the registration request message through a non-CAG cell and the AMF (200) determines that the UE (100) is a CAG-only UE, the AMF (200) accepts the registration request message. In addition, the AMF (200) sends a registration accept message including an allowed CAG list and / or a CAG-only indication.

[0078] In another embodiment, when the UE (100) is camped on a non-CAG cell or a non-standalone non-public network (non-SNPN) cell and the UE (100) supports CAG-related features or SNPN-related features, the UE (100) includes capability information of the UE (100) supporting CAG-related features or SNPN-related features in an AS message during an exit radio resource control (RRC) connection procedure (e.g., RRC connection establishment, RRC recovery procedure, or RRC reestablishment) or in a NAS message (e.g., a registration request or a service request). In response to determining from the capability information that the UE (100) supports CAG-related features, the AMF (200) sends a CAG information list to the UE (100) in a NAS message (e.g., a registration accept). In response to determining from the capability information that the UE (100) supports SNPN-related features, the AMF (200) sends SNPN-related information to the UE (100) in a NAS message or an Open Mobile Alliance Device Management (OMA-DM) message or other UE configuration update process, such as UE-related SNPN subscription, user identifiers and credentials of the identified one or more SNPNs, etc.

[0079] The memory (120, 220) may include a non-volatile storage element. Examples of such non-volatile storage elements may include a magnetic hard disk, an optical disk, a floppy disk, a flash memory, or a form of an electrically programmable memory (EPROM) or an electrically erasable programmable memory (EEPROM).

[0080] Additionally, in some examples, the memory (120, 220) may be considered a non-transitory storage medium. The term "non-transitory" may indicate that the storage medium is not contained in a carrier wave or propagating signal. However, the term "non-transitory" should not be interpreted as the memory (120, 220) being non-removable. In some instances, the memory (120, 220) may be configured to store a larger amount of information than the memory (120, 220). In certain instances, the non-transitory storage medium may store data that may change over time (e.g., in a random access memory (RAM) or a cache memory).

[0081] The processor (130) is configured to execute instructions stored in the memory (120). The communicator (140) is configured to perform internal communication between hardware components in the UE (100). In addition, the communicator (140) is configured to facilitate communication between the UE (100) and other devices (e.g., base stations, UICC (300), etc.).

[0082] The processor (230) is configured to execute instructions stored in the memory (220). The communicator (240) is configured to perform internal communication between hardware components in the AMF (200). In addition, the communicator (240) is configured to facilitate communication between the AMF (200) and other devices (e.g., base stations, etc.).

[0083] although Figure 1 The hardware components of the system are shown, but it should be understood that other embodiments are not limited thereto. In other embodiments, the system may include fewer or greater numbers of components. In addition, the labels or names of the components are for illustrative purposes only and do not limit the scope of the invention. One or more components may be combined together to perform the same or substantially similar functions for managing CAG information.

[0084] Figure 2A200 is a flowchart illustrating a method for obtaining a CAG information list from an AMF (200) by a UE (100) according to an embodiment disclosed herein. In step A201, the method includes sending a registration request message for registering to a network to the AMF (200) via a cell. In one embodiment, the method allows a registration controller (111) to send a registration request message to the AMF (200) via a cell in order to register to the network. In step A202, the method includes receiving a registration rejection message (200) including a CAG information list from the AMF. In one embodiment, the method allows a registration controller (111) to receive a registration rejection message including a CAG information list from the AMF (200). In step A203, the method includes storing the CAG information list.

[0085] In one embodiment, the method allows the registration controller (111) to store the CAG information list to the memory (120) of the UE (100). In another embodiment, the method allows the registration controller (111) to store the CAG information list to the UICC (300). In step A204, the method includes selecting a CAG cell based on the CAG information list received in the registration reject message. In one embodiment, the method allows the cell detector (112) to select a CAG cell based on the CAG information list received in the registration reject message. In step A205, the method includes sending a registration request message to the AMF (200) via the CAG cell. In one embodiment, the method allows the registration controller (111) to send a registration request message to the AMF (200) via the CAG cell. In step A206, the method includes receiving a registration accept message (200) from the AMF. In one embodiment, the method allows the registration controller (111) to receive a registration accept message from the AMF (200).

[0086] The various operations, actions, blocks, steps, etc. in flow chart A200 can be performed in the order presented, in a different order, or simultaneously. In addition, in some embodiments, some operations, actions, blocks, steps, etc. can be omitted, added, modified, or skipped without departing from the scope of the present invention.

[0087] Figure 2BThe invention is a flowchart B200 showing a method for providing a CAG information list to a UE (100) by an AMF (200) according to an embodiment disclosed herein. In step B201, the method includes receiving a registration request message for registering to a network from a UE (100) through a cell. In one embodiment, the method allows a registration controller (211) to receive a registration request message from a UE (100) through a cell in order to register to a network. In step B202, the method includes determining that the UE (100) is one of the following: when the cell is a CAG cell, the UE is not authorized to the cell, and when the cell is a non-CAG cell, the UE is authorized to access the network only through the CAG cell. In one embodiment, the method allows an authorization controller (212) to determine that the UE (100) is one of the following: when the cell is a CAG cell, the UE is not authorized to the cell, and when the cell is a non-CAG cell, the UE is authorized to access the network only through the CAG cell. In step B203, the method includes sending a registration rejection message (100) including a CAG information list to the UE. In one embodiment, the method allows the registration controller (211) to send a registration reject message including a CAG information list to the UE (100).

[0088] The various operations, actions, blocks, steps, etc. in flowchart B200 may be performed in the order presented, in a different order, or simultaneously. In addition, in some embodiments, some operations, actions, blocks, steps, etc. may be omitted, added, modified, or skipped without departing from the scope of the present invention.

[0089] Figure 3 is a sequence diagram showing signaling between an AMF (200) and a UE (100) for managing CAG information to register the UE (100) with a network according to an embodiment disclosed herein. In response to coupling a UICC (300) with a CAG subscription with the UE (100) for the first time, the UE (100) selects a non-CAG cell and camps on the non-CAG cell. In step S301, the UE (100) sends a registration request message for registering with the network to the AMF (200) via the non-CAG cell. In step S302, the AMF (200) determines that the UE (100) is authorized to access the network only via the CAG cell. In step S303, the AMF (200) rejects the request from the UE (100) by sending a registration reject message including a list of permitted CAGs and an optional CAG-only indication to the UE (100). In step S304, in response to receiving the registration reject message, the UE (100) stores the permitted CAG list in the UICC (300) or the memory (120). In one embodiment, when there is a CAG-only indication in the registration reject message, the UE (100) determines that the UE (100) is only allowed to access the network through the CAG cell.

[0090] In step S305, the UE selects and resides on a CAG cell corresponding to a CAG ID in the permitted CAG list. In step S306, the UE (100) sends a registration request message for registering to the network to the AMF (200) through the CAG cell. In step S307, the AMF (200) determines that the UE (100) is authorized to the CAG cell through which the UE (100) sends the registration request. In step S308, the AMF (200) registers the UE (100) for accessing the CAG service, and in response to determining that the UE (100) is authorized to the CAG cell, sends a registration accept message. In one embodiment, the registration accept message includes a CAG-only indication to the UE (100). In response to receiving the registration accept message, the UE (100) initiates access to the CAG service.

[0091] Unlike existing methods and systems, the proposed method allows the UE (100) to obtain CAG information including an allowed CAG list and a CAG-only indication as part of a registration reject message from the AMF (200). The UE (100) uses the CAG information to immediately select and camp on a CAG cell corresponding to a CAG ID in the allowed CAG list and use CAG services as quickly as possible.

[0092] In addition, the proposed method allows the UE (100) to immediately know that the UE (100) is allowed to access the network through the CAG cell by providing the UE (100) with a CAG-only indication in a registration reject message or a registration accept message. Therefore, the UE (100) does not reselect or select a non-CAG cell and does not lose the CAG service.

[0093] Figure 4 An Access and Mobility Management Function (AMF) according to an embodiment of the present disclosure is schematically illustrated.

[0094] Reference Figure 4 , AMF 400 may include a processor 410, a transceiver 420, and a memory 430. However, all the components shown are not required. AMF 400 may be composed of Figure 4 The components shown may be implemented with more or fewer components. In addition, according to another embodiment, the processor 410 and the transceiver 420 and the memory 430 may be implemented as a single chip.

[0095] The AMF 400 may correspond to the above-mentioned AMF 200. For example, the AMF 400 may correspond to Figure 1 and Figure 3 AMF200 shown.

[0096] The above-mentioned components will now be described in detail.

[0097] The processor 410 may include one or more processors or other processing devices that control the proposed functions, processes and / or methods. The operations of the AMF 400 may be implemented by the processor 410.

[0098] The transceiver 420 may include an RF transmitter for up-converting and amplifying a transmission signal, and an RF receiver for down-converting the frequency of a reception signal. However, according to another embodiment, the transceiver 420 may be implemented by more or fewer components than those shown in the components.

[0099] The transceiver 420 may be connected to the processor 410 and transmit and / or receive signals. The signals may include control information and data. In addition, the transceiver 420 may receive signals through wired and wireless networks and output the signals to the processor 410. The transceiver 420 may transmit signals output from the processor 410 through a wireless channel.

[0100] The memory 430 may store control information or data included in the signal obtained by the AMF 400. The memory 430 may be connected to the processor 410 and store at least one instruction or protocol or parameter for the proposed function, process and / or method. The memory 430 may include a read-only memory (ROM) and / or a random access memory (RAM) and / or a hard disk and / or a CD-ROM and / or a DVD and / or other storage devices.

[0101] The embodiments disclosed herein may be implemented using at least one software program that runs on at least one hardware device and performs network management functions to control the elements.

[0102] Figure 5 A user equipment (UE) according to an embodiment of the present disclosure is shown.

[0103] refer to Figure 5 UE 2200 may include a processor 510, a transceiver 520, and a memory 530. However, not all of the components shown are required. UE 2200 may include a processor 510, a transceiver 520, and a memory 530. Figure 5 The components shown may be implemented with more or fewer components. In addition, according to another embodiment, the processor 510 and the transceiver 520 and the memory 530 may be implemented as a single chip.

[0104] UE 500 may correspond to the above-mentioned UE. For example, UE 500 may correspond to Figure 1 and Figure 3 UE 100 shown in .

[0105] The above-mentioned components will now be described in detail.

[0106] The processor 510 may include one or more processors or other processing devices that control the proposed functions, processes and / or methods. The operations of the UE 500 may be implemented by the processor 510.

[0107] The transceiver 520 may include an RF transmitter for up-converting and amplifying a transmission signal, and an RF receiver for down-converting the frequency of a reception signal. However, according to another embodiment, the transceiver 520 may be implemented by more or less components than those shown in the components.

[0108] The transceiver 520 may be connected to the processor 510 and transmit and / or receive a signal. The signal may include control information and data. In addition, the transceiver 520 may receive a signal through a wireless channel and output the signal to the processor 510. The transceiver 520 may transmit a signal output from the processor 510 through a wireless channel.

[0109] The memory 530 may store control information or data included in a signal obtained by the UE 500. The memory 530 may be connected to the processor 510 and store at least one instruction or protocol or parameter for the proposed function, process and / or method. The memory 530 may include a read-only memory (ROM) and / or a random access memory (RAM) and / or a hard disk and / or a CD-ROM and / or a DVD and / or other storage devices.

[0110] The embodiments disclosed herein may be implemented using at least one software program that runs on at least one hardware device and performs network management functions to control the elements.

[0111] The foregoing description of specific embodiments will fully reveal the general nature of the embodiments herein, so that other embodiments can be easily modified and / or adapted to various applications by applying current knowledge, such specific embodiments do not depart from the general concept, and therefore, such adaptations and modifications should and are intended to be understood within the meaning and scope of the equivalent representations of the disclosed embodiments. It should be understood that the wording or terminology used herein is for descriptive purposes rather than for limiting purposes. Therefore, although the embodiments herein have been described according to preferred embodiments, those skilled in the art will recognize that the embodiments herein can be practiced by modification within the scope of the embodiments described herein.

Claims

1. A method for managing a closed access group (CAG), performed by a user equipment (UE), comprising: Sending a registration request message to the access and mobility management function AMF for registering with the network; as well as Based on identifying that the UE is allowed to access the network through only the CAG cell, receiving a registration reject message from the AMF, wherein the registration reject message includes a CAG information list; The CAG information list includes an allowed CAG list and an indication that the UE is allowed to access the network through only CAG cells, and the allowed CAG list includes zero or more CAG IDs.

2. The method according to claim 1, wherein: The method further includes reselecting a cell to register with a network based on the CAG information list.

3. A method for managing a closed access group (CAG), performed by an access and mobility management function (AMF), the method comprising: receiving, from a user equipment UE, a registration request message for registering with a network; identifying that the UE is allowed to access the network through only a CAG cell; as well as Based on identifying that the UE is allowed to access the network through only the CAG cell, sending a registration rejection message to the UE, wherein the registration rejection message includes a CAG information list, The CAG information list includes an allowed CAG list and an indication that the UE is allowed to access the network through only CAG cells, and the allowed CAG list includes zero or more CAG IDs.

4. A user equipment UE for managing a closed access group CAG, the UE comprising: Transceiver; Memory; and at least one processor coupled to the transceiver and the memory and configured to: Sending a registration request message to the access and mobility management function AMF for registering with the network; as well as Based on the UE being allowed to access the network through only the CAG cell, receiving a registration reject message from the AMF, wherein the registration reject message includes a CAG information list; The CAG information list includes an allowed CAG list and an indication that the UE is allowed to access the network through only CAG cells, and the allowed CAG list includes zero or more CAG IDs.

5. The UE according to claim 4, wherein: The at least one processor is further configured to reselect a cell to register with a network based on the CAG information list.

6. An access and mobility management function AMF for managing a closed access group CAG, the AMF comprising: Transceiver; Memory; and at least one processor coupled to the transceiver and the memory and configured to: receiving, from a user equipment UE, a registration request message for registering with a network; identifying that the UE is allowed to access the network through only a CAG cell; as well as Based on identifying that the UE is allowed to access the network through only the CAG cell, sending a registration rejection message to the UE, wherein the registration rejection message includes a CAG information list, The CAG information list includes an allowed CAG list and an indication that the UE is allowed to access the network through only CAG cells, and the allowed CAG list includes zero or more CAG IDs.

Images