Method and system for managing closed access group features for user equipment and networks
By introducing a CAG support indicator between the UE and AMF, it determines whether the UE supports CAG features and processes registration messages based on the support indicator, the problem of UE being unable to register is solved, and 5G service acquisition by UE without supporting CAG features is realized .
Patent Information
- Application Number
- CN202080057642.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2019-08-16
- Filing Date
- 2020-08-13
- Publication Date
- 2024-11-12
- Estimated Expiration
- 2040-08-13
AI Technical Summary
The prior art has failed to effectively deal with the registration problem between a user equipment (UE) that does not support the closed access group (CAG) feature and a network that supports the CAG feature, resulting in the UE being unable to register and attach to the network and unable to obtain 5G services.
By introducing a CAG support indicator between the user equipment (UE) and the access and mobility management function (AMF) of the network, it is determined whether the UE supports the CAG feature and sends corresponding registration messages according to the support indicator, including the CAG information list. Or a registration reject message for 5GMM reason value other than 5GMM reason #76.
The problem of UE being unable to register and attach to the network is solved, allowing UEs to select other cells to obtain 5G service without supporting CAG features, avoiding significant delays and service interruptions.
Smart Images

Figure CN114223261B_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to electronic devices, and more particularly, to methods and systems for managing closed access group (CAG) features for user equipment (UE) and networks. Background Art
[0002] The two types of UEs defined according to the 3rd Generation Partnership Project (3GPP) TS 23.501 are UEs supporting the CAG feature and UEs not supporting the CAG feature. Similarly, the two types of networks defined according to 3GPP TS 23.501 are networks supporting the CAG feature and networks not supporting the CAG feature. The conventional method does not define a behavior of a network supporting the CAG feature for handling a UE not supporting the CAG feature. In addition, the conventional method does not define a behavior of a network sequence diagram not supporting the CAG feature for handling a UE supporting the CAG feature.
[0003] Figure 1 A sequence diagram of signaling between an access and mobility management function (AMF) and a UE for registering a CAG subscription of the UE at a network according to a conventional method is shown. Consider that the AMF of the network supports the CAG feature, while the UE does not support the CAG feature. Consider that a universal integrated circuit card (UICC) is inserted into the UE for the first time, wherein the UICC includes a universal subscriber identity module (USIM) application with a CAG subscription. In step S101, since the CAG feature is not supported, the UE selects (S101) and resides on a non-CAG cell. In step S102, the UE initiates a registration process with the network by sending a registration request message to the AMF. When sending the registration request message, the UE does not indicate to the AMF whether the UE supports the CAG feature. Therefore, the AMF does not know whether the UE supports the CAG feature. In step S103, in response to receiving the registration request message, the AMF assumes that the UE supports the CAG feature based on the CAG subscription of the UICC.
[0004] In step S104, the AMF determines that, for the registration CAG subscription, the UE accesses a non-CAG cell instead of a CAG cell. In addition, the AMF uses 5GMM cause #76 to configure the registration reject message, where 5GMM cause #76 indicates that the UE is not authorized for CAG calls or is authorized to access only CAG cells. In step S105, the AMF sends a registration reject message with 5GMM cause #76 to the UE. In step S106, because 5GMM cause #76 is related to CAG, the UE does not understand 5GMM cause #76 and discards the registration reject message. In step S107, after timer T1 expires, the UE repeats steps S102-S105. In addition, the UE fails to access the 5GS service again. Summary of the invention
[0005] Technical issues
[0006] After the timer T1 expires, steps S102-S105 are repeated and the failure to access the 5GS service is cyclically performed at the UE. Therefore, the UE stays in the same non-CAG cell and cannot register and attach to the network.
[0007] Furthermore, when the UE is in the same location, the UE can never obtain 5G service. Therefore, it is desirable to address the above shortcomings or at least provide a useful alternative.
[0008] Solution to the problem
[0009] The main purpose of the embodiments herein is to provide a method and system for managing CAG features for UE and network.
[0010] Another object of embodiments herein is to determine whether a registration request message from a UE includes a CAG support indicator, wherein the CAG support indicator indicates whether the UE supports or does not support a CAG feature.
[0011] Another object of embodiments herein is to determine whether a UE supports a CAG feature based on a CAG support indicator.
[0012] Another object of an embodiment of the present invention is to send a registration reject message including a 5GMM cause value other than 5GMM cause #76 to the UE in response to determining that the UE (100) does not support the CAG feature and the UE (100) is subscribed to access the network only through a CAG cell.
[0013] Another object of the embodiments of the present invention is to send a registration reject message including one of 5GMM cause #7, 5GMM cause #27 and 5GMM cause #11 to the UE in response to determining that the UE (100) does not support the CAG feature and the UE (100) is subscribed to access the network only through the CAG cell.
[0014] Accordingly, an embodiment of the present invention provides a method for managing CAG features for a UE and a network. The method includes receiving, by an AMF server, a registration request message from a UE for registering a CAG subscription. In addition, the method includes determining, by the AMF, that the UE is subscribed to access the network only through a CAG cell. In addition, the method includes determining, by the AMF, whether the registration request message includes a CAG support indicator, wherein the CAG support indicator indicates whether the UE supports or does not support the CAG feature. In addition, the method includes determining, by the AMF, whether the UE supports the CAG feature based on the CAG support indicator. In addition, the method includes performing, by the AMF, one of the following: in response to determining that the UE supports the CAG feature, sending a registration acceptance message including a CAG information list to the UE, and in response to determining that the UE does not support the CAG feature, sending a registration rejection message to the UE.
[0015] In an embodiment, the registration request message is one of an initial registration request and a mobility registration update request message.
[0016] In an embodiment, the CAG support indicator is a one-bit information provided in the 5GMM capability information element of the registration request message.
[0017] In an embodiment, the registration reject message includes a 5GMM cause value other than 5GMM cause #76.
[0018] In an embodiment, the 5GMM cause value is one of the following: 5GMM cause #3 indicates an illegal UE, 5GMM cause #6 indicates an illegal ME, 5GMM cause #7 indicates that 5GS service is not allowed, 5GMM cause #11 indicates that PLMN is not allowed, 5GMM cause #12 indicates that tracking area is not allowed, 5GMM cause #13 indicates that roaming is not allowed in the tracking area, 5GMM cause #15 indicates that no suitable cell is available in the tracking area, 5GMM cause #22 indicates congestion, 5GMM cause #27 indicates that N1 mode is not allowed, and 5GMM cause #31 indicates that redirection to EPC is required.
[0019] In an embodiment, 5GMM cause #76 indicates that the UE is not authorized for CAG cells or is only authorized for CAG cells.
[0020] In an embodiment, the method includes, in response to receiving a registration reject message from the AMF, determining, by the UE, whether the 5GMM cause value in the registration reject message is one of 5GMM cause #7, 5GMM cause #27, and 5GMM cause #11. In addition, the method includes performing, by the UE, one of the following: in response to determining that the 5GMM cause value received from the AMF is one of 5GMM cause #7 and 5GMM cause #27, disabling the N1 mode and avoiding resending the registration request message through the non-CAG cell; and in response to determining that the 5GMM cause value received from the AMF is 5GMM cause #11, updating the public land mobile network (PLMN) corresponding to the non-CAG cell to the prohibited PLMN list, and selecting another PLMN to obtain service from the network.
[0021] Accordingly, an embodiment of the present invention provides a method for managing CAG features for a UE and a network. The method includes: sending a registration request message by the UE to the AMF of the network to register a CAG subscription and indicating whether the UE supports or does not support the CAG feature. The method includes the UE performing one of the following: when the UE supports the CAG feature and the UE is subscribed to access the network only through a CAG cell, receiving a registration acceptance message including a CAG information list from the AMF; and when the UE does not support the CAG feature and the UE is subscribed to access the network only through a CAG cell, receiving a registration rejection message from the AMF.
[0022] In an embodiment, the registration request message includes a CAG support indicator to indicate whether the UE supports or does not support the CAG feature.
[0023] Accordingly, an embodiment of the present invention provides an AMF for managing CAG features. The AMF includes a CAG message controller, a memory, and a processor, wherein the CAG message controller is coupled to the memory and the processor. The CAG message controller is configured to receive a registration request message from a UE for registering a CAG subscription. The CAG message controller is configured to determine that the UE is subscribed to access the network only through a CAG cell. The CAG message controller is configured to determine whether the registration request message includes a CAG support indicator, wherein the CAG support indicator indicates whether the UE supports or does not support the CAG feature. The CAG message controller is configured to determine whether the UE supports the CAG feature based on the CAG support indicator. The CAG message controller is configured to perform one of the following: in response to determining that the UE supports the CAG feature, sending a registration acceptance message including a CAG information list to the UE; and in response to determining that the UE does not support the CAG feature, sending a registration rejection message to the UE.
[0024] Accordingly, an embodiment of the present invention provides a UE for managing CAG features. The UE includes a CAG message controller, a memory, and a processor, wherein the CAG message controller is coupled to the memory and the processor. The CAG message controller is configured to send a registration request message to the AMF of the network for registering a CAG subscription and indicating whether the UE supports or does not support the CAG feature. The CAG message controller is configured to perform one of the following: when the UE supports the CAG feature and the UE is subscribed to access the network only through a CAG cell, receive a registration acceptance message including a CAG information list from the AMF; and when the UE does not support the CAG feature and the UE is subscribed to access the network only through a CAG cell, receive a registration rejection message from the AMF.
[0025] When considered in conjunction with the following description and the accompanying drawings, these and other aspects of the embodiments herein will be better understood and appreciated. However, it should be understood that the following description, although indicating preferred embodiments and many specific details thereof, 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 its spirit, and the embodiments herein include all such modifications.
[0026] Before proceeding to the following detailed description, it may be helpful to set forth definitions of certain words and phrases used throughout this patent document: the terms "include" and "comprising" and their derivatives mean including but not limited to; the term "or" is inclusive, meaning and / or; the phrases "associated with" and "associated with" and their derivatives may mean including, included, interconnected, containing, contained within, connected to or connected with, coupled to or coupled with, communicable with, cooperating with, interleaved, juxtaposed, proximate to, bound to or bound with, having, having the property of, etc.; and the term "controller" means any device, system, or portion thereof that controls at least one operation, such a device may be implemented as hardware, firmware, or software, or some combination of at least two of the above. It should be noted that the functionality associated with any particular controller may be centralized or distributed, whether locally or remotely.
[0027] 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 embodied 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 adapted to be implemented in a suitable computer-readable program code. 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 disk (CD), a digital video disk (DVD), or any other type of memory. "Non-volatile" computer-readable media do not include wired, wireless, optical, or other communication links that transmit volatile electrical signals or other signals. Non-volatile computer-readable media include media in which data can be permanently stored and media in which data can be stored and rewritten later, such as rewritable optical disks or erasable memory devices.
[0028] Definitions for certain words and phrases are provided throughout this patent document, those of ordinary skill in the art should understand that in many, if not most instances, such definitions apply to prior, as well as future uses of such defined words and phrases.
[0029] Advantageous Effects of the Invention
[0030] The present disclosure provides a method and system for managing CAG features for UE and network.
[0031] The present disclosure provides a method and system for determining whether a registration request message from a UE includes a CAG support indicator, wherein the CAG support indicator indicates whether the UE supports or does not support a CAG feature. BRIEF DESCRIPTION OF THE DRAWINGS
[0032] For a more complete understanding of the present disclosure and its advantages, reference is now made to the following description taken in conjunction with the accompanying drawings, wherein like reference numerals represent like parts:
[0033] Figure 1 A sequence diagram showing signaling between the AMF and the UE for registering the UE's CAG subscription at the network according to the prior art;
[0034] Figure 2 A block diagram of a system for managing CAG features for a UE and a network according to an embodiment disclosed herein is shown;
[0035] Figure 3A flowchart of a method for managing CAG features at a UE according to an embodiment disclosed herein is shown;
[0036] Figure 4 A flowchart of a method for managing CAG features at an AMF according to an embodiment disclosed herein is shown;
[0037] Figure 5 A sequence diagram of signaling between an AMF and a UE for providing a 5GMM cause value other than 5GMM cause #76 to the UE in response to a rejection of a Registration Request message at the AMF according to an embodiment disclosed herein is shown;
[0038] Figure 6 A sequence diagram showing signaling between an AMF and a UE for managing a registration request message from a UE according to an embodiment disclosed herein, wherein the UE does not support the CAG feature; and
[0039] Figure 7 A sequence diagram is shown of signaling between the AMF and the UE for managing a registration request message from the UE according to an embodiment disclosed herein, wherein the UE does not support the CAG feature. DETAILED DESCRIPTION
[0040] Discussed below Figures 1 to 7 The various embodiments used to describe the principles of the present disclosure in this patent document are merely exemplary and should not be interpreted in any way as limiting the scope of the present disclosure. Those skilled in the art will appreciate that the principles of the present disclosure can be implemented in any appropriately arranged system or device.
[0041] With reference to the non-limiting embodiments shown in the accompanying drawings and described in detail in the following description, the embodiments of this article and their various features and advantageous details are explained more comprehensively. The description of known components and processing techniques is omitted so as not to unnecessarily obscure the embodiments of this article. 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 indicated, the term "or" used herein refers to non-exclusive or. The examples used herein are intended only to facilitate understanding of the manner in which the embodiments of this article can be practiced, and further enable those skilled in the art to practice the embodiments of this article. Accordingly, these examples should not be interpreted as limiting the scope of the embodiments of this article.
[0042] As is conventional in the art, embodiments may be described and illustrated in blocks that perform one or more functions described. These blocks, which may be referred to herein as managers, units, modules, hardware components, etc., 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 optionally be driven by firmware and software. The circuit may, for example, be embodied in one or more semiconductor chips or on a substrate support such as a printed circuit board. The circuits constituting the blocks may be implemented by dedicated hardware, or a processor (e.g., one or more programmed microprocessors and associated circuits), or a combination of dedicated hardware that performs some functions of the block and a processor that performs other functions of the block. Without departing from the scope of the present disclosure, each block of the embodiment may be physically separated into two or more interacting 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.
[0043] Accordingly, an embodiment of the present invention provides a method for managing a closed access group (CAG) feature for a user equipment (UE) and a network. The method includes receiving, by an access and mobility management function (AMF) server, a registration request message from a UE for registering a CAG subscription. In addition, the method includes determining, by the AMF, that the UE is subscribed to access the network only through a CAG cell. In addition, the method includes determining, by the AMF, whether the registration request message includes a CAG support indicator, wherein the CAG support indicator indicates whether the UE supports or does not support the CAG feature. In addition, the method includes determining, by the AMF, whether the UE supports the CAG feature based on the CAG support indicator. In addition, the method includes performing one of the following by the AMF: in response to determining that the UE supports the CAG feature, sending a CAG information list to the UE.
[0044] and in response to determining that the UE does not support the CAG feature, sending a registration acceptance message to the UE including
[0045] A registration reject message with a 5GMM cause value other than the fifth generation mobility management 5GMM cause #76 is received.
[0046] Unlike existing methods and systems, in response to determining that the UE does not support the CAG feature, the AMF sends a registration reject message with 5GMM cause #7 or 5GMM cause #11 or 5GMM cause #27 to the UE. The UE understands 5GMM cause #7 or 5GMM cause #11 or 5GMM cause #27. In response to detecting 5GMM cause #7 or 5GMM cause #27, the UE disables N1 mode and will not retry the registration process on the cell used by the UE to send the registration request message. Therefore, the UE can select another cell to obtain 5G system (5GS) services at the earliest without facing significant delays. In response to detecting 5GMM cause #11, the UE puts the public land mobile network (PLMN) used by the UE to send the registration request message into the prohibited PLMN list. Therefore, the UE can select another PLMN to obtain 5GS services at the earliest without facing significant delays.
[0047] Referring now to the drawings, and more particularly to Figures 2 to 7 , showing a preferred embodiment.
[0048] Figure 2 A block diagram of a system (1000) for managing CAG features for a UE (100) and a network according to an embodiment as disclosed herein is shown. In an embodiment, the system (1000) 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 subscriber identity module (USIM) application with a CAG subscription. The AMF (200) is part of the network, and the AMF (200) supports the CAG feature. Examples of the network are a 5G core network (5GC), a next generation radio access network (NG-RAN), and a 5GS. Examples of the UE (100) are, but are not limited to, a smart phone, a tablet computer, a personal digital assistant (PDA), an Internet of Things (IoT), etc. In an embodiment, the UE (100) includes a CAG message controller (110), a memory (120), a processor (130), and a communicator (140). In an embodiment, the AMF (200) includes a CAG message controller (210), a memory (220), a processor (230), and a communicator (240).
[0049] The CAG message controller (110) is configured to select a cell of a PLMN to reside in response to receiving a signal from a base station corresponding to the cell, wherein the base station is connected to the AMF (200). In an embodiment, the UE (100) operates in an automatic network selection mode or a manual network selection mode. In an embodiment, the cell is a CAG cell or a non-CAG cell. In an embodiment, the PLMN is a home PLMN (HPLMN) or a visited PLMN (VPLMN). In addition, the CAG message controller (110) is configured to initiate a non-access stratum (NAS) process (e.g., a registration process) by sending a registration request message to the AMF (200) via the cell to register a CAG subscription with the network. In an embodiment, the registration request message is an initial registration request or a mobility registration update request message. In an embodiment, the registration request message is a NAS message.
[0050] The CAG message controller (110) is configured to indicate to the AMF (200) whether the UE (100) supports or does not support the CAG feature when sending a registration request message. In an embodiment, when the UE (100) supports the CAG feature, the registration request message includes a CAG support indicator. In an embodiment, the CAG support indicator is a one-bit information provided in a 5GMM capability information element (IE) of the registration request message. In addition, when the UE (100) does not support the CAG feature, the registration request message does not include the CAG support indicator. In another embodiment, the registration request message includes a CAG support indicator to indicate whether the UE (100) supports or does not support the CAG feature. In an embodiment, when the UE (100) supports the CAG feature, the CAG message controller (110) is configured to set the value of the CAG support indicator in the registration request message to TRUE.
[0051] When the UE (100) does not support the CAG feature, the CAG message controller (110) is configured to set the value of the CAG support indicator in the registration request message to FALSE. In another embodiment, when the UE (100) supports the CAG feature, the CAG message controller (110) is configured to set the CAG bit in the 5GMM capability IE of the registration request message to "support CAG". When the UE (100) does not support the CAG feature, the CAG message controller (110) is configured to set the CAG bit in the 5GMM capability IE of the registration request message to "not support CAG". The content of the 5GMM capability information element is given in Table 1.
[0052]
[0053] Table 1: 5GMM capability information elements
[0054] When the UE (100) does not support the CAG feature, the entry in the 5GMM capability information element in row: octet 5* and column: bit 1 in the table, namely CAG, is set to 0. In addition, when the UE (100) does not support the CAG feature, the entry CAG is set to 0.
[0055] The CAG message controller (210) is configured to determine, in response to receiving a registration request message from the UE (100), based on the CAG subscription of the UICC (300), that the UE (100) is subscribed to access the network only through the CAG cell.
[0056] In addition, the CAG message controller (210) is configured to determine whether the registration request message includes a CAG support indicator. In addition, the CAG message controller (210) is configured to determine whether the UE (100) supports the CAG feature based on the CAG support indicator. In an embodiment, the CAG message controller (210) is configured to determine that the UE (100) supports the CAG feature in response to detecting the CAG support indicator in the registration request message. The CAG message controller (210) is configured to determine that the UE (100) does not support the CAG feature in response to not detecting the CAG support indicator in the registration request message. In another embodiment, the CAG message controller (210) is configured to determine that the UE (100) supports the CAG feature in response to detecting a set value TRUE from the CAG support indicator in the registration request message. The CAG message controller (210) is configured to determine that the UE (100) does not support the CAG feature in response to not detecting a set value FALSE from the CAG support indicator in the registration request message.
[0057] The CAG message controller (210) is configured to send a registration accept message including a CAG information list to the UE (100) in response to determining that the UE (100) supports the CAG feature, for updating the CAG information list stored at the UE (100). In an embodiment, the CAG message controller (210) is configured to send a registration accept message including a CAG information list to the UE (100) in response to determining that the UE (100) supports the CAG feature and the cell through which the UE (100) sends the registration request message is a CAG cell. In an embodiment, the registration accept message is a NAS message. In an embodiment, the CAG information list includes a list of CAG IDs corresponding to the CAG cells that the UE (100) is allowed to access.
[0058] Furthermore, the CAG message controller (110) is configured to, in response to receiving the registration acceptance message,
[0059] On the CAG cell corresponding to the CAG ID in the list for accessing 5GS services.
[0060] The CAG message controller (210) is configured to send a registration reject message including a 5GMM cause value (i.e., a NAS cause value) other than 5GMM cause #76 to the UE (100) in response to determining that the UE (100) does not support the CAG feature and the UE (100) is allowed to access the 5GS via the CAG cell. In an embodiment, the CAG message controller (210) is configured to send a registration reject message including a 5GMM cause value other than 5GMM cause #76 to the UE (100) in response to determining that the UE (100) does not support the CAG feature and the cell through which the UE (100) sends the registration request message is a non-CAG cell and the UE (100) is allowed to access the 5GS via the CAG cell. In an embodiment, the registration reject message is a NAS message. In an embodiment, 5GMM cause #76 indicates that the UE (100) is not authorized for the CAG cell or is authorized only for the CAG cell. In an embodiment, the 5GMM cause value is one of 5GMM cause #3, 5GMM cause #6, 5GMM cause #7, 5GMM cause #11, 5GMM cause #12, 5GMM cause #13, 5GMM cause #15, 5GMM cause #22, 5GMM cause #27 and 5GMM cause #31 indicating an illegal UE.
[0061] 5GMM Cause #3 indicates that the UE (100) is an illegal UE. 5GMM Cause #6 indicates that the UE (100) is an illegal mobile equipment (ME). 5GMM Cause #7 indicates that 5GS service is not allowed for the UE (100). 5GMM Cause #11 indicates that PLMN is not allowed for the UE (100). 5GMM Cause #12 indicates that tracking area is not allowed for the UE (100). 5GMM Cause #13 indicates that roaming in the tracking area is not allowed for the UE (100). 5GMM Cause #15 indicates that no suitable cell is available in the tracking area for the UE (100). 5GMM Cause #22 indicates congestion to the UE (100). 5GMM Cause #27 indicates that N1 mode is not allowed to the UE (100). 5GMM Cause #31 indicates that redirection to EPC is required.
[0062] In an embodiment, the CAG message controller (210) is configured to receive a registration request message from the UE (100) through a cell of the HPLMN. In addition, the CAG message controller (210) is configured to determine that the UE (100) does not support the CAG feature, the UE (100) has a CAG subscription, and the UE (100) is in the HPLMN. In addition, the CAG message controller (210) is configured to send a registration reject message including 5GMM cause #7 or 5GMM cause #27 to the UE (100).
[0063] In another embodiment, the CAG message controller (210) is configured to receive a registration request message from the UE (100) through a cell of the VPLMN. In addition, the CAG message controller (210) is configured to determine that the UE (100) does not support the CAG feature, the UE (100) has a CAG subscription, and the UE (100) is in the VPLMN. In addition, the CAG message controller (210) is configured to send a registration reject message including 5GMM cause #11 or 5GMM cause #27 to the UE (100).
[0064] In another embodiment, the CAG message controller (110) is configured to determine whether the 5GMM cause value in the registration reject message is one of 5GMM cause #7, 5GMM cause #27 and 5GMM cause #11 in response to receiving the registration reject message from the AMF (200). In an embodiment, the CAG message controller (110) is configured to disable the N1 mode and avoid resending the registration request message through the non-CAG cell in response to determining that the 5GMM cause value received from the AMF (200) is one of 5GMM cause #7 and 5GMM cause #27. In an embodiment, the CAG message controller (110) is configured to update the PLMN corresponding to the non-CAG cell to the prohibited PLMN list in response to determining that the 5GMM cause value received from the AMF (200) is 5GMM cause #11, and select another PLMN to obtain service from the network.
[0065] In response to receiving 5GMM cause #3 or 5GMM cause #6, the UE (100) sets the 5GS update status to 5U3ROAMING NOT ALLOWED and stores the 5G update status. In addition, the UE (100) deletes the 5G globally unique temporary identifier (5G-GUTI), the last visited registration tracking area identifier (TAI), the TAI list and the 5G key set identifier (ngKSI). Before turning off the UE (100) or removing the UICC (300) containing the USIM from the UE (100), the UE (100) considers the USIM invalid for 5GS services. The UE (100) deletes the list of equivalent PLMNs and enters state 5GMM-DEREGISTERED. When the registration reject message has been successfully integrity checked by NAS, the UE (100) sets the counter for "SIM / USIM considered invalid for General Packet Radio Service (GPRS) service" and the counter for "SIM / USIM considered invalid for 5GS service over non-3GPP access" to a UE implementation specific maximum value (e.g. 5).
[0066] In an embodiment, when the UE (100) receives a registration reject message via 3GPP access and the UE (100) is operating in single registration mode, the UE (100) processes the Evolved Packet System Mobility Management (EMM) parameters EMM Status, Evolved Packet System (EPS) Update Status, 4G Globally Unique Temporary Identifier (4G-GUTI), TAI List and EPS Key Set Identifier (eKSI) as specified in 3GPP TS 24.301 for the case when the EPS Attach Request procedure is rejected with an EMM cause of 5GMM cause #3 or 5GMM cause #6. The UE (100) also considers the USIM invalid for non-EPS services before turning off the UE (100) or removing the UICC (300) containing the USIM from the UE (100). In an embodiment, when the Registration Reject message has been successfully integrity checked by the NAS and the UE (100) maintains a counter for "SIM / USIM considered invalid for non-GPRS services", the UE (100) sets the counter to a UE implementation specific maximum value.
[0067] In an embodiment, when the registration reject message has been successfully integrity checked by the NAS and the UE (100) also supports the registration procedure on another access, the UE (100) processes the 5GMM parameters and 5GMM status for that access as described for the 5GMM cause value.
[0068] In response to receiving 5GMM cause #7, the UE (100) sets the 5GS update status to 5U3 ROAMING NOT ALLOWED according to subclause 5.1.3.2.2 and stores the 5GS update status. In addition, the UE (100) deletes the 5G-GUTI, the last visited registered TAI, the TAI list and the ngKSI.
[0069] In the case of a PLMN, the UE (100) considers the USIM to be invalid for 5GS services until the UE (100) is turned off or the UICC (300) containing the USIM is removed from the UE (100).
[0070] In the case of SNPN, the UE (100) considers the entry of the "Subscriber Data List" with the Independent Non-Public Network (SNPN) identity of the current SNPN to be invalid for 5GS services until the UE (100) is turned off or the entry is updated. Additionally, when a primary authentication and key agreement procedure based on the Extensible Authentication Protocol (EAP) using EAP Authentication and Key Agreement (AKA), or a primary authentication and key agreement procedure based on 5G AKA is performed in the current SNPN, the UE (100) considers the USIM to be invalid for the current SNPN until the UE (100) is turned off or the UICC (300) containing the USIM is removed from the UE (100).
[0071] Furthermore, the UE (100) enters state 5GMM-DEREGISTERED. In the case of a PLMN, when the registration reject message has been successfully integrity checked by the NAS, the UE (100) sets a counter for the "SIM / USIM considered invalid for GPRS services" event and a counter for the "SIM / USIM considered invalid for 5GS services on non-3GPP access" event to a UE implementation specific maximum value. In another embodiment, when the registration reject message has been successfully integrity checked by the NAS, in the case of a PLMN, the UE (100) sets a counter for the "entry of current SNPN considered invalid for 3GPP access" event to a UE implementation specific maximum value. In another embodiment, when the registration reject message has been successfully integrity checked by the NAS, the UE (100) deletes the 5GMM parameters stored in the non-volatile memory (120) as specified in 3GPP TS 24.501.
[0072] In an embodiment, when the UE (100) receives a REGISTRATION REJECT message via a 3GPP access and the UE (100) operates in single registration mode, the UE (100) processes the EMM parameters EMM status, EPS update status, 4G-GUTI, TAI list and eKSI as specified in 3GPP TS 24.301 for the case when the EPS ATTACH REQUEST procedure is rejected with an EMM cause with 5GMM cause #7. When the REGISTRATION REJECT message has been successfully integrity checked by NAS and the UE (100) also supports registration procedures on another access, the UE (100) processes the 5GMM parameters and 5GMM status for the other access as described for this 5GMM cause value.
[0073] In response to receiving 5GMM cause #11 through a cell belonging to an SNPN, the UE (100) considers it an abnormal situation and considers the behavior of the UE (100) as specified in 3GPP TS 24.501. In addition, according to subclause 5.1.3.2.2, the UE (100) sets the 5GS update status to 5U3 ROAMING NOT ALLOWED and stores the 5GS update status. In addition, the UE (100) deletes the 5G-GUTI, the last visited registered TAI, the TAI list and the ngKSI. In addition, the UE (100) deletes the list of equivalent PLMNs, resets the registration attempt counter and stores the PLMN identity in the "prohibited PLMN list". In addition, according to 3GPP TS 23.122, the UE (100) enters the state 5GMM-DEREGISTERED.PLMN-SEARCH and performs PLMN selection. When the Registration Reject message has been successfully integrity checked by the NAS, the UE (100) sets the PLMN specific attempt counter and the PLMN specific attempt counter for non-3GPP access for the PLMN to a UE implementation specific maximum value.
[0074] In an embodiment, when the UE (100) receives a registration reject message via 3GPP access and the UE (100) operates in single registration mode, the UE (100) processes the EMM parameters EMM status, EPS update status, 4G-GUTI, TAI list, KSI and attach attempt counter as specified in 3GPP TS 24.301 for the case when the EPS attach request procedure is rejected with an EMM cause with 5GMM cause #11.
[0075] In an embodiment, when the registration reject message has been successfully integrity checked by NAS and the UE (100) also supports the registration procedure for the same PLMN on another access, the UE (100) processes the 5GMM parameters and 5GMM status for that access as described for 5GMM cause #11.
[0076] In response to receiving 5GMM cause #12, the UE (100) sets the 5GS update status to 5U3 ROAMING NOT ALLOWED and stores the 5GS update status according to subclause 5.1.3.2.2. In addition, the UE (100) deletes the 5G-GUTI, the last visited registered TAI, the TAI list and the ngKSI. In addition, the UE (100) resets the registration attempt counter. In addition, the UE (100) stores the current TAI in the list of "5GS prohibited tracking areas for regional provision of services" and enters state 5GMM-DEREGISTERED.LIMITED-SERVICE.
[0077] In an embodiment, when the UE (100) receives a registration reject message via 3GPP access and the UE (100) operates in single registration mode, the UE (100) processes the EMM parameters EMM status, EPS update status, 4G-GUTI, TAI list, eKSI and attach attempt counter as specified in 3GPP TS 24.301 for the case when the EPS attach request procedure is rejected with an EMM cause with 5GMM cause #12.
[0078] In response to receiving 5GMM cause #13, the UE (100) sets the 5GS update status to 5U3 ROAMING NOT ALLOWED and stores the 5GS update status according to subclause 5.1.3.2.2. In addition, the UE (100) deletes the 5G-GUTI, the last visited registered TAI, the TAI list and the ngKSI. In addition, the UE (100) deletes the list of equivalent PLMNs and resets the registration attempt counter. In addition, the UE (100) stores the current TAI in the list of "5GS prohibited tracking areas for roaming" and enters the state 5GMM-DEREGISTERED.LIMITED-SERVICE or optionally enters the state 5GMM-DEREGISTERED.PLMN-SEARCH.
[0079] In an embodiment, when the UE (100) is registered in S1 mode and operates in dual registration mode, the PLMN in which the UE (100) selects to register is as specified in subclause 4.8.3. In another embodiment, the UE (100) performs PLMN selection according to 3GPP TS 23.122.
[0080] In an embodiment, when the UE (100) receives a registration reject message via 3GPP access and the UE (100) operates in single registration mode, the UE (100) processes the EMM parameters EMM status, EPS update status, 4G-GUTI, TAI list, eKSI and attach attempt counter as specified in 3GPP TS 24.301 for the case when the EPS attach request procedure is rejected with an EMM cause with 5GMM cause #13.
[0081] In response to receiving 5GMM cause #15, the UE (100) sets the 5GS update status to 5U3 ROAMING NOT ALLOWED and stores the 5GS update status according to subclause 5.1.3.2.2. In addition, the UE (100) deletes the 5G-GUTI, the last visited registered TAI, the TAI list and the ngKSI. In addition, the UE (100) resets the registration attempt counter. In addition, the UE (100) stores the current TAI in the list of "5GS prohibited tracking areas for roaming" and enters the state 5GMM-DEREGISTERED.LIMITED-SERVICE. In addition, the UE (100) searches for a suitable cell in another tracking area according to 3GPP TS38.304.
[0082] In an embodiment, when the UE (100) receives a registration reject message via 3GPP access and the UE (100) is operating in single registration mode, the UE processes the EMM parameters EMM status, EPS update status, 4G-GUTI, TAI list, eKSI and attach attempt counter as specified in 3GPP TS 24.301 for the case when the EPS attach request procedure is rejected with an EMM cause with 5GMM cause #15.
[0083] In response to receiving 5GMM cause #22, and when the T3346 Value IE is present in the Registration Reject message and the value in the T3346 Value IE indicates that timer T3346 is neither zero nor deactivated, the UE (100) proceeds as described in Method 1, otherwise the UE (100) considers it an abnormal situation and the behavior of the UE (100) for this situation is specified in subclause 5.5.1.2.7.
[0084] Method 1: The UE (100) aborts the initial registration process, sets the 5GS update status to 5U2 NOTUPDATED and enters the state 5GMM-DEREGISTERED.ATTEMPTING-REGISTRATION. In addition, if timer T3346 is running, the UE (100) stops timer T3346. When the registration reject message is integrity protected, the UE (100) uses the value provided in the T3346 value IE to start timer T3346. When the registration reject message is not integrity protected, the UE (100) uses a random value from the default range specified in 3GPP TS 24.008 to start timer T3346. In addition, the UE (100) stays in the current serving cell and applies normal cell reselection processing. In an embodiment, when timer T3346 expires or stops, if still needed, the UE (100) starts the initial registration process.
[0085] In an embodiment, when the UE (100) receives a registration reject message via 3GPP access and the UE (100) is operating in single registration mode, the UE processes the EMM parameters EMM status, EPS update status, 4G-GUTI, TAI list, eKSI and attach attempt counter as specified in 3GPP TS 24.301 for the case when the EPS attach request procedure is rejected with an EMM cause with 5GMM cause #22.
[0086] In response to receiving 5GMM cause #27, the UE (100) sets the 5GS update status to 5U3 ROAMING NOT ALLOWED and stores the 5GS update status according to subclause 5.1.3.2.2. In addition, the UE (100) deletes the 5G-GUTI, the last visited registered TAI, the TAI list and the ngKSI. In addition, the UE (100) resets the registration attempt counter and enters state 5GMM-NULL or state 5GMM-DEREGISTERED.LIMITED-SERVICE.
[0087] In an embodiment, in the case of a PLMN, when the Registration Reject message has been successfully integrity checked by the NAS, the UE (100) sets the PLMN-specific N1 mode attempt counter for 3GPP access and the PLMN-specific N1 mode attempt counter for non-3GPP access to the PLMN to a UE implementation-specific maximum value. In the case of a SNPN, when the Registration Reject message has been successfully integrity checked by the NAS, the UE (100) sets the SNPN-specific attempt counter for 3GPP access of the current SNPN to a UE implementation-specific maximum value.
[0088] In another embodiment, when the REGISTRATION REJECT message has been successfully integrity checked by the NAS, the UE (100) disables N1 mode capabilities for 3GPP access and non-3GPP access (see subclause 4.9). In an embodiment, when the UE (100) receives the REGISTRATION REJECT message via 3GPP access and the UE (100) is operating in single registration mode, the UE sets the EPS update state to EU3ROAMING NOT ALLOWED and deletes the 4G-GUTI, the last visited registered TAI, the TAI list and the eKSI. In addition, the UE (100) resets the attach attempt counter and enters state EMM-DEREGISTERED.
[0089] In response to receiving 5GMM cause #31, the UE (100) sets the 5GS update status to 5U3 ROAMING NOT ALLOWED and stores the 5GS update status according to subclause 5.1.3.2.2. In addition, the UE (100) deletes the 5G-GUTI, the last visited registered TAI, the TAI list and the ngKSI. In addition, the UE (100) resets the registration attempt counter and enters state 5GMM-DEREGISTERED. In addition, if E-UTRA capability is disabled, the UE (100) enables E-UTRA capability and disables N1 mode capability for 3GPP access (see subclause 4.9.2). When the UE (100) operates in single registration mode, the UE (100) handles the EMM parameters EMM status, EPS update status, 4G-GUTI, TAI list, eKSI and attach attempt counter as specified in 3GPP TS 24.301 for the case when the EPS attach procedure is rejected with EMM cause with 5GMM cause #27.
[0090] In an embodiment, for VPLMN 1, the UE (100) is allowed to access the 5GS via a CAG cell or a non-CAG cell; while for VPLMN 2, the UE (100) is allowed to access the 5GS only via a CAG cell. In response to the UE (100) registering with VPLMN 2, the network sends a 5GMM cause #11 to the UE (100). In response to receiving the 5GMM cause #11, the UE (100) puts the VPLMN 2 into a prohibited PLMN list. In addition, the UE (100) never selects VPLMN 2. In addition, when the UE (100) is allowed to access the 5GS service on a non-CAG cell, the UE (100) selects the non-CAG cell of VPLMN 1 and initiates a registration process on the non-CAG cell. In addition, the UE (100) obtains the 5GS service in VPLMN 1.
[0091] The memory (120) and the memory (220) may include a non-volatile memory element. Examples of such non-volatile memory elements may include a magnetic hard disk, an optical disk, a floppy disk, a flash memory, or an electrically programmable memory (EPROM) or an electrically erasable programmable memory (EEPROM).
[0092] Additionally, in some examples, memory (120) and memory (220) may be considered to be non-transitory storage media. The term "non-transitory" may indicate that the storage medium is not embodied in a carrier wave or propagating signal. However, the term "non-transitory" should not be interpreted as memory (120) and memory (220) being non-removable. In some examples, memory (120) and memory (220) may be configured to store a larger amount of information than memory (120) and memory (220), respectively. In certain examples, non-transitory storage media may store data that may change over time (e.g., in random access memory (RAM) or cache).
[0093] The processor (130) is configured to execute instructions stored in the memory (120). The communicator (140) is configured to communicate internally 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.).
[0094] The processor (230) is configured to execute instructions stored in the memory (220). The communicator (240) is configured to communicate internally 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.).
[0095] although Figure 1The hardware components of the system (1000) are shown, but it will be understood that other embodiments are not limited thereto. In other embodiments, the system (1000) 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 to manage CAG features.
[0096] Figure 3 A flowchart S300 of a method for managing a CAG feature at a UE (100) according to an embodiment disclosed herein is shown. In step S301, the method includes sending a registration request message to an AMF (200) of a network for registering a CAG subscription and indicating whether the UE (100) supports or does not support the CAG feature, wherein the UE (100) is subscribed to access the network only through a CAG cell. In an embodiment, the method allows a CAG message controller (110) to send a registration request message to an AMF (200) of a network for registering a CAG subscription and indicating whether the UE (100) supports or does not support the CAG feature, wherein the UE (100) is subscribed to access the network only through a CAG cell. In step S302, the method includes receiving a registration acceptance message including a CAG information list from the AMF (200) when the UE (100) supports the CAG feature. In an embodiment, when the UE (100) supports the CAG feature, the method allows the CAG message controller (110) to receive a registration accept message including a CAG information list from the AMF (200). In step S303, when the UE (100) does not support the CAG feature and the UE (100) is allowed to access the 5GS only via the CAG cell, the method includes receiving a registration reject message including a 5GMM cause value other than 5GMM cause #76 from the AMF (200). In an embodiment, when the UE (100) does not support the CAG feature, the method allows the CAG message controller (110) to receive a registration reject message including a 5GMM cause value other than 5GMM cause #76 from the AMF (200).
[0097] The various behaviors, actions, blocks, steps, etc. in flow chart S300 can be performed in the order presented, in a different order, or simultaneously. In addition, in some embodiments, some behaviors, actions, blocks, steps, etc. can be omitted, added, modified, skipped, etc., without departing from the scope of the present invention.
[0098] Figure 4A flowchart S400 of a method for managing CAG features at an AMF (200) according to an embodiment disclosed herein is shown. In step S401, the method includes receiving a registration request message from a UE (100) for registering a CAG subscription. In an embodiment, the method allows a CAG message controller (210) to receive a registration request message from a UE (100) for registering a CAG subscription. In step S402, the method includes determining that the UE (100) is subscribed to access a network only through a CAG cell. In an embodiment, the method allows a CAG message controller (210) to determine that the UE (100) is subscribed to access a network only through a CAG cell. In step S403, the method includes determining whether the registration request message includes a CAG support indicator, wherein the CAG support indicator indicates whether the UE (100) supports or does not support the CAG feature. In an embodiment, the method allows a CAG message controller (210) to determine whether the registration request message includes a CAG support indicator, wherein the CAG support indicator indicates whether the UE (100) supports or does not support the CAG feature.
[0099] At step S404, the method includes determining whether the UE (100) supports the CAG feature based on the CAG support indicator. In an embodiment, the method allows the CAG message controller (210) to determine whether the UE (100) supports the CAG feature based on the CAG support indicator. If the CAG support indicator is not included, the CAG message controller (210) determines that the UE (100) does not support the CAG feature. At step S405, the method includes sending a registration accept message including a CAG information list to the UE (100) in response to determining that the UE (100) supports the CAG feature. In an embodiment, the method allows the CAG message controller (210) to send a registration accept message including a CAG information list to the UE (100) in response to determining that the UE (100) supports the CAG feature. At step S406, the method includes sending a registration reject message including a 5GMM cause value other than 5GMM cause #76 to the UE (100) in response to determining that the UE (100) does not support the CAG feature. In an embodiment, the method allows the CAG message controller (210) to send a registration reject message including a 5GMM cause value other than 5GMM cause #76 to the UE (100) in response to determining that the UE (100) does not support the CAG feature.
[0100] The various behaviors, actions, blocks, steps, etc. in flow chart S400 can be performed in the order presented, in a different order, or simultaneously. In addition, in some embodiments, some behaviors, actions, blocks, steps, etc. can be omitted, added, modified, skipped, etc., without departing from the scope of the present invention.
[0101] Figure 5A sequence diagram of signaling between an AMF (200) and a UE (100) according to an embodiment disclosed herein is shown, the signaling being used to provide a 5GMM cause value other than 5GMM cause #76 to the UE (100) in response to a rejection of a registration request message at the AMF (200). Consider that the UE (100) does not support the CAG feature and the UE (100) is coupled to a UICC (300) with a CAG subscription. In step S501, the UE (100) selects and resides on a non-CAG cell of the AMF (200), wherein the AMF (200) supports the CAG feature. In step S502, the UE (100) initiates a NAS procedure to the AMF (200) on the non-CAG cell and sends a first NAS message (i.e., a registration request message) without a CAG support indicator to the AMF (200). In step S503, the UE (100) starts a timer T1 after sending the first NAS message.
[0102] In step S504, in response to receiving the first NAS message, the AMF (200) determines that the UE (100) does not support the CAG feature because the CAG support capability (i.e., the CAG support indicator) is not found from the first NAS message. In addition, the AMF (200) determines that the UE (100) has a subscription to access 5GS only via a CAG cell, i.e., the UE (100) is allowed to reside only on the CAG cell according to the subscription. In step S504, when the UE (100) is in the HPLMN, the AMF (200) configures the second NAS message (i.e., the registration reject message) using 5GMM cause #7 or 5GMM cause #27. When the UE (100) is in the VPLMN, the AMF (200) configures the second NAS message (i.e., the registration reject message) using 5GMM cause #11 or 5GMM cause #27. In step S506, the AMF (200) sends the second NAS message to the UE (100) within the expiration of the timer T1. In step S507, when the UE (100) detects 5GMM cause #7 or 5GMM cause #27 from the second NAS message, the UE (100) disables the N1 mode and does not retry the registration process. When the UE (100) detects 5GMM cause #11 from the second NAS message, the UE (100) puts the PLMN into the prohibited PLMN list and selects another PLMN to obtain service.
[0103] Figure 6A sequence diagram of signaling between an AMF (200) and a UE (100) for managing a registration request message from a UE (100) according to an embodiment disclosed herein is shown, wherein the UE (100) does not support the CAG feature. Consider that the UE (100) does not support the CAG feature and the UE (100) is coupled to a UICC (300) with a CAG subscription. In step S601, the UE (100) selects and resides on a non-CAG cell of the AMF (200), wherein the AMF (200) supports the CAG feature. In step S602, the UE (100) initiates a NAS procedure (i.e., an initial registration procedure or a periodic registration update procedure or a registration update procedure or a service request procedure or a deregistration procedure) to the AMF (200) on the non-CAG cell, and sends a first NAS message without a CAG support indicator to the AMF (200).
[0104] In step S603, in response to receiving the first NAS message, the AMF (200) determines that the UE (100) subscribes to the CAG subscription, i.e., according to the subscription, the UE (100) is allowed to access the 5GS only via the CAG cell. In addition, in response to not finding the CAG support indicator in the first NAS message, the AMF (200) determines that the UE (100) does not support the CAG feature. In addition, the AMF (200) completes the NAS procedure. In step S604, the AMF (200) sends a second NAS message including an IE indicating that the UE (100) is allowed to access the 5GS only via the CAG cell.
[0105] In response to receiving the second NAS message, the UE (100) continues to camp on the non-CAG cell, or selects another non-CAG cell to camp on due to not supporting the CAG feature. In step S605, the UE (100) initiates a NAS procedure (i.e., an initial registration procedure or a periodic registration update procedure or a registration update procedure or a service request procedure or a deregistration procedure) to the AMF (200) on the non-CAG cell, and sends a third NAS message without a CAG support indicator to the AMF (200). In step S606, in response to receiving the third NAS message, the AMF (200) determines that the UE (100) does not support the CAG feature, and that the UE (100) has been notified that the UE (100) is a CAG-only UE (i.e., the UE is allowed to access the 5GS through the CAG cell).
[0106] In step S607, in response to receiving the third NAS message, the AMF (200) determines that the UE (100) does not support the CAG feature and that the UE (100) has been notified that the UE (100) is a CAG-only UE (i.e., the UE is allowed to access the 5GS through the CAG cell). In step S607, the AMF (200) rejects the NAS procedure and sends a fourth NAS message (e.g., a NAS message related to rejection of the registration procedure), including one of NAS Cause #3, NAS Cause #6, NAS Cause #7, NAS Cause #11, NAS Cause #12, NAS Cause #13, NAS Cause #15, NAS Cause #22, NAS Cause #27, and NAS Cause #31.
[0107] Figure 7 A sequence diagram of signaling between an AMF (200) and a UE (100) for managing a registration request message from a UE (100) according to an embodiment disclosed herein is shown, wherein the UE (100) does not support a CAG feature. In step S701, the UE (100) initiates a NAS procedure (i.e., an initial registration procedure or a periodic registration update procedure or a registration update procedure or a service request procedure or a deregistration procedure) on a non-CAG cell. In an embodiment, the first NAS message includes at least one of network slice selection assistance information (NSSAI) and a data network name (DNN). In one example, the UE (100) supports the CAG feature. In another example, the UE (100) does not support the CAG feature. In one example, the UE (100) does not receive a CAG-only indication from the AMF (200) indicating that the UE (100) is allowed to access the 5GS only via a CAG cell or that the UE (100) is not configured with an allowed CAG list. The allowed CAG list is a list of CAG IDs corresponding to CAG cells that the UE (100) is allowed to access. In one example, the AMF (200) does not support the CAG feature.
[0108] In step S702, when a single NSSAI (S-NSSAI) in the NSSAI or DNN is used for a non-public network (NPN) integrated with a public network, the AMF (200) determines that the UE (100) has a CAG subscription. When all S-NSSAIs in the NSSAI are used only to access services for the NPN integrated with a public network, the AMF (200) determines that the UE (100) is a CAG-only UE. When the DNN indicates that the DNN is only used for the NPN integrated with a public network, the AMF (200) determines that the UE (100) has a CAG subscription. In one example, when all subscribed S-NSSAIs or DNNs of the UE (100) are used for the NPN integrated with a public network, the AMF (200) determines that the UE (100) has a subscription for the CAG. In an embodiment, the NSSAI includes only the S-NSSAI. In step S703, in response to determining that the UE (100) is a CAG-only UE, the AMF (200) sends a second NAS message (e.g., a NAS message related to rejection of the registration procedure) including one of NAS Cause #3, NAS Cause #6, NAS Cause #7, NAS Cause #11, NAS Cause #12, NAS Cause #13, NAS Cause #15, NAS Cause #22, NAS Cause #27, and NAS Cause #31.
[0109] The embodiments disclosed herein may be implemented using at least one software program running on at least one hardware device and performing network management functions to control the elements.
[0110] Although the present disclosure has been described with various embodiments, various changes and modifications may be suggested to one skilled in the art. The present disclosure is intended to encompass such changes and modifications as fall within the scope of the appended claims.
Claims
1. A method for managing a closed access group (CAG) feature by a user equipment (UE), the method include: sending a first non-access stratum (NAS) message to an access and mobility management function (AMF), the first NAS message including information indicating whether the UE supports the CAG feature; as well as In a case where the UE does not support the CAG feature and the UE is allowed to access a 5GS (5G system) only via a CAG cell, receiving from the AMF a second NAS message including a NAS cause in response to the first NAS message, The NAS reason is one of NAS reason #7, NAS reason #11 and NAS reason #27.
2. The method according to claim 1, in, The UE resides in a non-CAG cell of a network supporting the CAG feature and the AMF supports the CAG feature.
3. The method according to claim 1, in, The NAS reason #7 indicates that 5GS service is not allowed, wherein the NAS cause #11 indicates that a public land mobile network PLMN is not allowed, and Among them, the NAS reason #27 indicates that N1 mode is not allowed.
4. A method for managing a Closed Access Group (CAG) feature by an Access and Mobility Management Function (AMF), the method include: receiving a first non-access stratum (NAS) message from a user equipment (UE), the first NAS message including information indicating whether the UE supports the CAG feature; as well as In a case where the UE does not support the CAG feature and the UE is allowed to access a 5GS (5G system) only via a CAG cell, sending a second NAS message including a NAS cause in response to the first NAS message to the UE, The NAS reason is one of NAS reason #7, NAS reason #11 and NAS reason #27.
5. The method according to claim 4, in, The AMF supports the CAG feature and the UE resides in a non-CAG cell of a network supporting the CAG feature.
6. The method according to claim 4, in, The NAS reason #7 indicates that 5GS service is not allowed, wherein the NAS cause #11 indicates that a public land mobile network PLMN is not allowed, and Among them, the NAS reason #27 indicates that N1 mode is not allowed.
7. A user equipment (UE) for managing a closed access group (CAG) feature, the UE include: Transceiver; and A controller coupled to the transceiver and configured to control: sending a first non-access stratum (NAS) message to an access and mobility management function (AMF), the first NAS message including information indicating whether the UE supports the CAG feature; as well as In a case where the UE does not support the CAG feature and the UE is allowed to access a 5GS (5G system) only via a CAG cell, receiving from the AMF a second NAS message including a NAS cause in response to the first NAS message, The NAS reason is one of NAS reason #7, NAS reason #11 and NAS reason #27.
8. The UE according to claim 7, in, The UE resides in a non-CAG cell of a network supporting the CAG feature and the AMF supports the CAG feature.
9. The UE according to claim 7, in, The NAS reason #7 indicates that 5GS service is not allowed, wherein the NAS cause #11 indicates that a public land mobile network PLMN is not allowed, and Among them, the NAS reason #27 indicates that N1 mode is not allowed.
10. An access and mobility management function (AMF) for managing closed access group (CAG) features, the AMF comprising: Transceiver; A controller coupled to the transceiver and configured to control: receiving a first non-access stratum (NAS) message from a user equipment (UE), the first NAS message including information indicating whether the UE supports the CAG feature; as well as In a case where the UE does not support the CAG feature and the UE is allowed to access a 5GS (5G system) only via a CAG cell, sending a second NAS message including a NAS cause in response to the first NAS message to the UE, The NAS reason is one of NAS reason #7, NAS reason #11 and NAS reason #27.
11. The AMF according to claim 10, in, The AMF supports the CAG feature and the UE resides in a non-CAG cell of a network supporting the CAG feature.
12. The AMF according to claim 10, wherein: in, The NAS reason #7 indicates that 5GS service is not allowed, wherein the NAS cause #11 indicates that a public land mobile network PLMN is not allowed, and Among them, the NAS reason #27 indicates that N1 mode is not allowed.
