Method, apparatus, and computer program product for managing device network capability in private network

Abstract

To provide an approach for managing network capabilities for user equipment (UE).SOLUTION: UE can maintain subscriber data that comprises an entry index of networks for which various access modes are enabled / disabled, and a counter for each network / access mode combination. After requesting access to a network, the UE may receive a non-integrity protected rejection message that indicates the network does not allow a particular access mode. Based on the cause of access rejection, the UE can disallow the particular access mode for the network, start a timer, and increment a counter associated with the network / access mode combination. Once the timer expires, if the counter value is below a threshold, the UE re-enables the particular access mode for the network, or if the counter value is at or above the threshold, the UE removes the respective entry index for the particular access mode for the network.SELECTED DRAWING: Figure 6

Description

[Technical Field]

[0001] One exemplary embodiment relates generally to managing communications in a communication system, and more particularly to managing device network capabilities in a private network. [Background technology]

[0002] A communication system can be considered a facility that facilitates communication sessions between two or more entities, such as user terminals, base stations / access points, and / or other nodes, by providing carriers between the various entities involved in the communication path. A communication system can be provided, for example, by a communication network and one or more compatible communication devices. A communication session can include communication of data to convey information, such as voice, electronic mail (email), text messages, multimedia, and / or content data. Non-limiting examples of services provided include two-way or multi-way calls, data communication or multimedia services, and access to a data network system such as the Internet. In a wireless communication system, at least a portion of a communication session between at least two stations occurs over a wireless link.

[0003] A user can access a communication system by means of an appropriate communication device or terminal. A user's communication device is often referred to as user equipment (UE) or user device. A communication device is provided with appropriate signal transmission and reception equipment to enable communication (e.g., access to a communication network or direct communication with other users). A communication device may access a carrier provided by a station or access point to transmit and / or receive information on the carrier.

[0004] Communication systems and associated devices typically operate according to a given standard or specification that defines what the various entities associated with the system are allowed to do and how to achieve it. The communication protocols and / or parameters used for the connections are also typically specified. Summary of the Invention

[0005] When a conventional user equipment (UE) is accessing or requesting access to a network and is denied access by the network, it may determine that a particular network access method or interface has been denied by the network. In such a case, the conventional UE typically needs to disable the particular network access method or interface for all networks and / or disable all network access methods or interfaces for the particular network. The systems, apparatuses, methods, and computer program products described herein, according to some embodiments, are provided to solve at least some of the technical challenges faced in conventional and emerging networks. For example, improved UEs of some embodiments can be provided by physically, structurally, operationally, and / or functionally modifying conventional UEs, such as smartphones, so that network capability information can be stored in the UE in an embodiment in a much more granular and organized manner. This refinement of the granularity of network access capabilities is achieved, for example, by creating a hierarchical data storage structure in which subscriber information stores indexes of entries specific to networks, network access methods, and / or interfaces. In some embodiments, such a structure and the inclusion of such information in the UE's subscriber information may also reduce the number of instances in which an embodiment UE is erroneously disabled for a particular network, a particular network access method or interface, and / or a particular network access method or interface to a particular network. In other words, an embodiment apparatus (and / or embodiment method or embodiment computer program product), when implemented in managing network access capabilities for a UE, may reduce computational complexity and messaging between the UE and a network or network entity, because the UE does not need to continue to request access from a network that has denied the UE access.Similarly, a UE may have greater network availability and / or a larger set of network access methods or interfaces through which the UE may access a network, thereby improving UE performance, e.g., with respect to the speed and availability of messaging between different users' UEs, requesting service from the network, providing service by the network, handling emergency services, downlink / uplink speeds and bandwidth (capacity), etc. Some described embodiments provide substantial technical improvements to a UE, such as a smartphone or another mobile device, during access to or requesting access to a network, for example, because the UE may be able to scan a list of available networks and determine particular networks or a subset of the list of available networks that the UE knows are accessible via a particular network access method or interface, or for which the UE does not have information that the network does not allow a particular network access method or interface. This allows a UE to register or request service by sending messages, such as an initial registration request, to a specific network or a subset of the list of available networks, without using traditional trial-and-error techniques and / or requiring extra messaging between the UE and each available network to request information about the network's capabilities and / or the access methods / interfaces allowed / denied by the network. This may also allow the UE to receive registration acceptance messages from the requested networks more quickly, because the networks to which the UE requests access are less likely to deny access. The UE may continue to update and refine its index of network entries, including network capability information, over time, thereby reducing the time it takes to access the network, receive offered services, send messages, upload / download packets, etc.

[0006] Thus, described herein is an approach for managing network capabilities for a UE. According to exemplary embodiments, a UE may maintain subscriber data including entry indexes for networks for which various access modes are enabled / disabled, and a counter for each network / access mode combination. After requesting access to a network, the UE may receive a non-integrity protected rejection message indicating that the network does not allow the particular access mode. Based on the cause of the access rejection, the UE may disable the particular access mode for the network, start a timer, and increment a counter associated with the network / access mode combination. When the timer expires, the UE re-enables the particular access mode for the network if the counter value is below a threshold, or removes each entry index for the particular access mode for the network if the counter value is equal to or greater than the threshold. Thus, provided herein are methods, apparatuses, and computer program products according to exemplary embodiments for managing device network capabilities in a private network.

[0007] In some embodiments, the method comprises maintaining, for a user equipment, a list of subscriber data for one or more networks, the list of subscriber data being identified by an entry index or network identification. maintaining a list of one or more entry indexes of entries used to send requests to specific networks that do not allow the specific network access mode, or a list of one or more network identities of specific networks that do not allow the specific network access mode; disabling the entry used to send the request or the specific network access mode for the specific network when a non-integrity protection rejection message for the request is received from the specific network indicating that the specific network does not allow the specific network access mode, starting a timer, and incrementing one of the one or more counters associated with the entry; re-enabling the entry used to send the request or the specific network access mode for the specific network when the timer expires and a counter value of the one of the one or more counters is below a predetermined threshold; and including an index of the entry or an identification of the specific network used to send the request in the list of one or more entry indexes or the list of one or more network identities when the timer expires and a counter value of the one of the one or more counters meets the predetermined threshold. In some embodiments, the particular network access mode includes one of a trusted network access mode, an untrusted network access mode, or a non-access stratum interface or protocol.In some embodiments, the one or more networks include at least one of a non-public network (NPN), a private network, a standalone non-public network (SNPN), an NPN deployed with a public network, an NPN deployed with a public land mobile network (PLMN), an NPN deployed with a public network using a shared radio access network, an NPN deployed with a shared radio access network and a public network using a shared control plane, an NPN deployed in a public network, or an NPN deployed in a PLMN. In some embodiments, the non-integrity protection rejection message includes an indication that N1 mode is not allowed for the particular network or an indication that untrusted network access mode is not allowed for the particular network. In some embodiments, the one or more networks include an NPN deployed with a PLMN, the user equipment is deployed in PLMN access mode, and the list of subscriber data includes a list of PLMNs. In some embodiments, the predetermined threshold for one of the one or more counters is implementation dependent and specific to the particular network access mode and the indicator received in the non-integrity protection rejection message.

[0008] In some embodiments, an apparatus comprises at least one processor and at least one memory containing computer program code, the at least one memory and the computer program code causing the at least one processor to: maintain, with respect to the user equipment, a list of subscriber data for one or more networks, the list of subscriber data including one or more entries each including an entry index or network identification information used to send a request to a particular network; maintain, for each of the one or more entries, one or more counters; maintain a list of one or more entry indexes of entries used to send a request to a particular network that does not allow a particular network access mode, or a list of one or more network identification information of a particular network that does not allow a particular network access mode; The device may be configured to at least: when a non-integrity protection rejection message for the request is received from a specific network indicating denial, disable the entry or the specific network access mode for the specific network used to transmit the request, start a timer, and increment one of one or more counters associated with the entry; when the timer expires, if the counter value of the one of the one or more counters is below a predetermined threshold, re-enable the entry or the specific network access mode for the specific network used to transmit the request; and when the timer expires, if the counter value of the one of the one or more counters meets the predetermined threshold, include an index of the entry or identification information of the specific network used to transmit the request in a list of one or more entry indexes or a list of one or more network identification information.In some embodiments, the particular network access mode includes one of a trusted network access mode, an untrusted network access mode, or an unaccess stratum interface or protocol. In some embodiments, the one or more networks include at least one of a non-public network (NPN), a private network, a standalone non-public network (SNPN), an NPN deployed with a public network, an NPN deployed with a public land mobile network (PLMN), an NPN deployed with a public network using a shared radio access network, an NPN deployed with a public network using a shared radio access network and a shared control plane, an NPN deployed in a public network, or an NPN deployed in a PLMN. In some embodiments, the non-integrity protection rejection message includes an indication that N1 mode is not allowed for the particular network or an indication that untrusted network access mode is not allowed for the particular network. In some embodiments, the one or more networks include an NPN deployed with a PLMN, the user equipment is deployed in PLMN access mode, and the list of subscriber data includes a list of PLMNs. In some embodiments, the predetermined threshold for one of the one or more counters is implementation dependent and specific to the particular network access mode and the indicator received in the non-integrity protection rejection message.

[0009] In some embodiments, the apparatus includes, for user equipment, a processor or processing circuit, such as a memory having stored thereon computer program code, means for maintaining a list of subscriber data for one or more networks, the list of subscriber data including one or more entries each including an entry index or network identification information, used to send requests to a particular network; means for maintaining one or more counters for each of the one or more entries; means for maintaining a list of one or more entry indexes of entries used to send requests to a particular network that does not allow a particular network access mode, or a list of one or more network identification information of a particular network that does not allow a particular network access mode; and means for maintaining a counter for a request indicating that a particular network does not allow a particular network access mode. The method may include: means for disabling the entry or the specific network access mode for the specific network used to transmit the request when a non-integrity protection rejection message is received from the specific network, starting a timer, and incrementing one of one or more counters associated with the entry; means for re-enabling the entry or the specific network access mode for the specific network used to transmit the request when the counter value of the one of the one or more counters is below a predetermined threshold when the timer expires; and means for including an index of the entry or an identification of the specific network used to transmit the request in the list of one or more entry indexes or the list of one or more network identifications when the counter value of the one of the one or more counters meets the predetermined threshold when the timer expires. In some embodiments, the specific network access mode includes one of a trusted network access mode, an untrusted network access mode, or a non-access stratum interface or protocol.In some embodiments, the one or more networks include at least one of a non-public network (NPN), a private network, a standalone non-public network (SNPN), an NPN deployed with a public network, an NPN deployed with a public land mobile network (PLMN), an NPN deployed with a public network using a shared radio access network, an NPN deployed with a public network using a shared radio access network and a shared control plane, an NPN deployed in a public network, or an NPN deployed in a PLMN. In some embodiments, the non-integrity protection rejection message includes an indication that N1 mode is not allowed for the particular network or an indication that untrusted network access mode is not allowed for the particular network. In some embodiments, the one or more networks include an NPN deployed with a PLMN, the user equipment is deployed in PLMN access mode, and the list of subscriber data includes a list of PLMNs. In some embodiments, the predetermined threshold for one of the one or more counters is implementation-dependent and specific to the particular network access mode and the indicator received in the non-integrity protection rejection message.

[0010] In some embodiments, the computer program product comprises, for a user equipment, maintaining a list of subscriber data for one or more networks, the list of subscriber data including one or more entries each including an entry index or network identification information used to send requests to the particular network; maintaining one or more counters for each of the one or more entries; maintaining a list of one or more entry indexes of entries used to send requests to the particular network that does not allow the particular network access mode, or a list of one or more network identification information of the particular network that does not allow the particular network access mode; and if a non-integrity protection rejection message in response to the request is received from the particular network indicating that the particular network does not allow the particular network access mode, The present invention may include a non-transitory computer-readable medium having stored thereon computer instructions that perform at least the following: disable a specific network access mode for an entry or a specific network used to transmit the request, start a timer, and increment one of one or more counters associated with the entry; when the timer expires, if the counter value of the one of the one or more counters is below a predetermined threshold; and when the timer expires, if the counter value of the one of the one or more counters meets the predetermined threshold, include an index of the entry or an identification of the specific network used to transmit the request in a list of one or more entry indexes or a list of one or more network identifications. In some embodiments, the specific network access mode includes one of a trusted network access mode, an untrusted network access mode, or a non-access stratum interface or protocol.In some embodiments, the one or more networks include at least one of a non-public network (NPN), a private network, a standalone non-public network (SNPN), an NPN deployed with a public network, an NPN deployed with a public land mobile network (PLMN), an NPN deployed with a public network using a shared radio access network, an NPN deployed with a public network using a shared radio access network and a shared control plane, an NPN deployed in a public network, or an NPN deployed in a PLMN. In some embodiments, the non-integrity protection rejection message includes an indication that N1 mode is not allowed for the particular network or an indication that untrusted network access mode is not allowed for the particular network. In some embodiments, the one or more networks include an NPN deployed with a PLMN, the user equipment is deployed in PLMN access mode, and the list of subscriber data includes a list of PLMNs. In some embodiments, the predetermined threshold for one of the one or more counters is implementation-dependent and specific to the particular network access mode and the indicator received in the non-integrity protection rejection message.

[0011] In some embodiments, a method may include, for user equipment, maintaining a list of subscriber data for one or more networks, the list of subscriber data including one or more entries each including an entry index or network identification information, used to transmit a request to the particular network; maintaining a list of one or more entry indexes of entries used to transmit a request to the particular network that does not allow the particular network access mode, or a list of one or more network identification information for the particular network that does not allow the particular network access mode; disabling the entry used to transmit the request or the particular network access mode for the particular network when an integrity protection rejection message for the request is received from the particular network indicating that the particular network does not allow the particular network access mode; and including the index of the entry used to transmit the request or the identification information of the particular network in the list of one or more entry indexes or including the identification information of the particular network in the list of one or more network identities.

[0012] In some embodiments, an apparatus may comprise at least one processor and at least one memory containing computer program code, wherein the at least one memory and computer program code may be configured to cause, by the at least one processor, the apparatus to at least perform the following: maintain, for user equipment, a list of subscriber data for one or more networks, the list of subscriber data including one or more entries each including an entry index or network identification information, used to send a request to a particular network; maintain a list of one or more entry indexes of entries used to send a request to a particular network that does not allow the particular network access mode, or a list of one or more network identification information for the particular network that does not allow the particular network access mode; invalidate the entry used to send the request or the particular network access mode for the particular network when an integrity protection rejection message in response to the request is received from the particular network indicating that the particular network does not allow the particular network access mode; and, when a timer expires, include the index of the entry used to send the request or the identification information of the particular network in the list of one or more entry indexes or the list of one or more network identification information.

[0013] In some embodiments, the apparatus may comprise: means for maintaining, for user equipment, a list of subscriber data for one or more networks, such as a processor or processing circuitry and a memory having computer program code stored therein, the list of subscriber data including one or more entries, each including an entry index or network identification, used to send a request to a particular network; means for maintaining a list of one or more entry indexes of entries used to send a request to a particular network that does not allow the particular network access mode, or a list of one or more network identifications of particular networks that do not allow the particular network access mode; means for invalidating the entry used to send the request or the particular network access mode for the particular network when an integrity protection rejection message for the request is received from the particular network indicating that the particular network does not allow the particular network access mode; and means for including, when a timer expires, the index of the entry used to send the request or the identification of the particular network in the list of one or more entry indexes or the list of one or more network identifications.

[0014] In some embodiments, a computer program product may include a non-transitory computer-readable medium having stored thereon computer instructions that perform at least the following: for a user equipment, maintaining a list of subscriber data for one or more networks, the list of subscriber data including one or more entries each including an entry index or network identification information and used to send a request to a particular network; maintaining a list of one or more entry indexes of entries used to send a request to a particular network that does not allow the particular network access mode, or a list of one or more network identification information for the particular network that does not allow the particular network access mode; invalidating the entry used to send the request or the particular network access mode for the particular network when an integrity protection rejection message for the request is received from the particular network indicating that the particular network does not allow the particular network access mode; and when a timer expires, including the index of the entry used to send the request or the identification information of the particular network in the list of one or more entry indexes or the list of one or more network identification information.

[0015] In some embodiments, a method may include, for a user equipment, maintaining a list of subscriber data for one or more networks, the list of subscriber data including an entry index containing a list of networks for which one or more network access modes are disabled; maintaining, for each of the one or more networks, one or more counters of access attempts via the one or more network access modes; disabling the particular network access mode for the particular network and starting a timer and incrementing one of the one or more counters associated with the particular network when a non-integrity protection rejection message is received indicating that the particular network of the one or more networks is not configured for the particular network access mode of the one or more network access modes; re-enabling the particular network access mode for the particular network if a counter value of the one of the one or more counters is below a predetermined threshold when the timer expires; and removing each entry index of the particular access mode for the particular network from the list of subscriber data if a counter value of the one of the one or more counters meets the predetermined threshold when the timer expires.

[0016] In some embodiments, an apparatus may comprise at least one processor and at least one memory containing computer program code, wherein the at least one memory and the computer program code may be configured to cause, by the at least one processor, the apparatus to perform at least the following: maintain, for user equipment, a list of subscriber data for one or more networks, the list of subscriber data including an entry index containing a list of networks for which one or more network access modes are disabled; maintain, for each of the one or more networks, one or more counters of access attempts via the one or more network access modes; disable the particular network access mode for the particular network, if a non-integrity protection rejection message is received indicating that the particular network of the one or more networks is not configured for the particular network access mode of the one or more network access modes, start a timer, and increment one of the one or more counters associated with the particular network; re-enable the particular network access mode for the particular network if a counter value of the one of the one or more counters is below a predetermined threshold when the timer expires; and remove each entry index of the particular access mode for the particular network from the list of subscriber data if the counter value of the one of the one or more counters meets the predetermined threshold when the timer expires.

[0017] In some embodiments, the apparatus may comprise, for user equipment, means for maintaining a list of subscriber data for one or more networks, such as a processor or processing circuitry and a memory having computer program code stored thereon, the list of subscriber data including an entry index containing a list of networks for which one or more network access modes are disabled; means for maintaining, for each of the one or more networks, one or more counters of access attempts via the one or more network access modes; means for disabling the particular network access mode for the particular network, starting a timer, and incrementing one of the one or more counters associated with the particular network, when a non-integrity protection rejection message is received indicating that the particular network of the one or more networks is not configured for the particular network access mode of the one or more network access modes; means for re-enabling the particular network access mode for the particular network if the counter value of the one of the one or more counters is below a predetermined threshold when the timer expires; and means for removing each entry index of the particular access mode for the particular network from the list of subscriber data if the counter value of the one of the one or more counters meets the predetermined threshold when the timer expires.

[0018] In some embodiments, a computer program product may include a non-transitory computer-readable medium having stored thereon computer instructions that perform at least the following: maintain, for a user equipment, a list of subscriber data for one or more networks, the list of subscriber data including an entry index containing a list of networks for which one or more network access modes are disabled; maintain, for each of the one or more networks, one or more counters of access attempts via the one or more network access modes; disable the particular network access mode for the particular network and start a timer and increment one of the one or more counters associated with the particular network when a non-integrity protection rejection message is received indicating that the particular network of the one or more networks is not configured for the particular network access mode of the one or more network access modes; re-enable the particular network access mode for the particular network if the counter value of the one of the one or more counters is below a predetermined threshold when the timer expires; and remove each entry index of the particular access mode for the particular network from the list of subscriber data if the counter value of the one of the one or more counters meets the predetermined threshold when the timer expires.

[0019] In some embodiments, the method may include compiling a list of networks for which one or more access modes or one or more access types are disabled in a user equipment; sending from the user equipment to a network entity of the network an initial registration request message or a service request message for a particular access type via the particular access mode; receiving from the network entity a rejection message in response to the initial registration request message or the service request message, the rejection message including an indication of a reason for rejection of the initial registration request message or the service request message; determining a number of times a rejection message is received from the network entity when the reason is that the particular access mode is an N1 access mode and the network entity is not configured for N1 access, and adding an entry for the network to the list of networks if the number of times meets a threshold; and determining a number of times a rejection message is received from the network entity when the reason is that the particular access type is an untrusted access type and the network is not configured for untrusted access, and adding an entry for the particular access type associated with the network to the list of networks if the number of times meets a threshold.

[0020] In some embodiments, an apparatus comprises at least one processor and at least one memory containing computer program code, the at least one memory and the computer program code comprising: compiling, by the at least one processor, a list of networks for which one or more access modes or one or more access types are disabled in the user equipment; sending an initial registration request message or a service request message from the user equipment to a network entity of the network for a particular access type with a particular access mode; and receiving an initial registration request message or a service request message from the network entity in response to the initial registration request message or the service request message. The network entity may be configured to at least receive a rejection message including an indication of a reason for rejection of the page; determine a number of times a rejection message has been received from a network entity where the reason is that the particular access mode is an N1 access mode and the network entity is not configured for N1 access, and add an entry for the network to the list of networks if the number of times meets a threshold; and determine a number of times a rejection message has been received from a network entity where the reason is that the particular access type is an untrusted access type and the network is not configured for untrusted access, and add an entry for the particular access type associated with the network to the list of networks if the number of times meets a threshold.

[0021] In some embodiments, the apparatus may comprise: means for compiling a list of networks for which one or more access modes or one or more access types are disabled in user equipment, such as a processor or processing circuitry and a memory having computer program code stored thereon; means for transmitting an initial registration request message or a service request message from the user equipment to a network entity of the network for a particular access type via a particular access mode; means for receiving from the network entity, in response to the initial registration request message or the service request message, a rejection message including an indication of a reason for rejection of the initial registration request message or the service request message; means for determining a number of times a rejection message is received from a network entity when the reason is that the particular access mode is an N1 access mode and the network entity is not configured for N1 access, and adding an entry for the network to the list of networks if the number of times meets a threshold; and means for determining a number of times a rejection message is received from a network entity when the reason is that the particular access type is an untrusted access type and the network is not configured for untrusted access, and adding an entry for the particular access type associated with the network to the list of networks if the number of times meets a threshold.

[0022] In some embodiments, a computer program product may include a non-transitory computer-readable medium having stored thereon computer instructions to perform at least the following: compile a list of networks for which one or more access modes or one or more access types are disabled in user equipment; send from the user equipment to a network entity of the network an initial registration request message or a service request message for a particular access type via a particular access mode; receive from the network entity, in response to the initial registration request message or the service request message, a rejection message including an indication of a reason for rejection of the initial registration request message or the service request message; determine a number of times a rejection message is received from the network entity for a reason where the particular access mode is an N1 access mode and the network entity is not configured for N1 access, and add an entry for the network to the list of networks if the number of times meets a threshold; and determine a number of times a rejection message is received from the network entity for a reason where the particular access type is an untrusted access type and the network is not configured for untrusted access, and add an entry for the particular access type associated with the network to the list of networks if the number of times meets a threshold.

[0023] In some embodiments, the method includes retrieving a list of subscriber data for user equipment associated with one or more networks, the list of subscriber data including one or more entries, each including an entry index or network identification information, operable to track transmission of requests to a particular network or track denials received by a particular network; providing one or more counters for each of the one or more entries; retrieving a list of one or more entry indexes of entries operable to be used to transmit requests to a particular network that does not allow a particular network access mode, or a list of one or more network identification information of a particular network that does not allow a particular network access mode; and transmitting the request to the particular network by using the particular entry associated with the particular network and the particular network access mode. the entry includes one of an initial registration request or a service request; if, in response to transmitting the request to the specific network, a non-integrity protection rejection message is received from the specific network indicating that the specific network does not allow the specific network access mode, disable the specific network access mode for the specific entry or the specific network used to transmit the request, start a timer, and increment a corresponding counter of one or more counters associated with the specific entry that is associated with a reason value indicated in the non-integrity protection rejection message; when the timer expires, if the counter value of the corresponding counter of the one or more counters is below a predetermined threshold, re-enable the specific network access mode for the specific entry or the specific network used to transmit the request; when the timer expires, if the counter value of the corresponding counter of the one or more counters is equal to or greater than the predetermined threshold,and including in the list of one or more entry indexes or list of one or more network identities an index of a particular entry or an identification of a particular network to be used in transmitting the request.

[0024] In some embodiments, an apparatus comprises at least one processor and at least one memory containing computer program code, the at least one memory and computer program code comprising: retrieving, by the at least one processor, a list of subscriber data for user equipment associated with one or more networks, the list of subscriber data including one or more entries, each including an entry index or network identification information, operable to track transmission of requests to a particular network or track denials received by a particular network; providing one or more counters for each of the one or more entries; retrieving a list of one or more entry indexes of entries operable to be used to transmit requests to a particular network that does not allow a particular network access mode, or a list of one or more network identification information of a particular network that does not allow a particular network access mode; and transmitting a request to the specific network by using a specific entry associated with the specific network access mode, the request including one of an initial registration request or a service request; if, in response to transmitting the request to the specific network, a non-integrity protection rejection message is received from the specific network indicating that the specific network does not allow the specific network access mode, disabling the specific entry or the specific network access mode for the specific network used to transmit the request, starting a timer, and incrementing a corresponding counter, among one or more counters associated with the specific entry, that is associated with the reason value indicated in the non-integrity protection rejection message; when the timer expires, if the counter value of the corresponding counter, among the one or more counters, is below a predetermined threshold, re-enabling the specific entry or the specific network access mode for the specific network used to transmit the request; when the timer expires,If a counter value of a corresponding counter among the one or more counters is equal to or greater than a predetermined threshold, include an index of a particular entry or an identification of a particular network used to transmit the request in the list of one or more entry indexes or the list of one or more network identifications.

[0025] In some embodiments, the apparatus includes a processor or processing circuitry and a memory having stored thereon computer program code, and includes: means for retrieving a list of subscriber data for user equipment associated with one or more networks, the list of subscriber data including one or more entries each including an entry index or network identification information, operable to track transmission of requests to a particular network or to track denials received by a particular network; means for providing one or more counters for each of the one or more entries; means for retrieving a list of one or more entry indexes of entries operable to be used to transmit requests to a particular network that does not allow a particular network access mode, or a list of one or more network identifications of a particular network that does not allow a particular network access mode; and means for identifying a request by using a particular entry associated with a particular network and a particular network access mode. means for transmitting a request to a specific network, the request including one of an initial registration request or a service request; means for, when in response to transmitting the request to the specific network, a non-integrity protection rejection message is received from the specific network indicating that the specific network does not allow the specific network access mode, disabling the specific network access mode for the specific entry or the specific network used to transmit the request, starting a timer, and incrementing a corresponding counter associated with the reason value indicated in the non-integrity protection rejection message among one or more counters associated with the specific entry; means for, when the timer expires, if the counter value of the corresponding counter of the one or more counters is below a predetermined threshold, re-enabling the specific network access mode for the specific entry or the specific network used to transmit the request; and means for, when the timer expires, if the counter value of the corresponding counter of the one or more counters is equal to or greater than the predetermined threshold,and means for including in one or more lists of entry indexes or one or more lists of network identities an index of a particular entry or an identification of a particular network to be used in transmitting the request.

[0026] In some embodiments, the computer program product includes: retrieving a list of subscriber data for user equipment associated with one or more networks, the list of subscriber data including one or more entries, each including an entry index or network identification information, operable to track transmission of requests to a particular network or track denials received by a particular network; providing one or more counters for each of the one or more entries; retrieving a list of one or more entry indexes of the entries operable to be used to transmit requests to a particular network that does not allow a particular network access mode, or a list of one or more network identification information of a particular network that does not allow a particular network access mode; and transmitting the request to the particular network by using the particular entry associated with the particular network and the particular network access mode. the request includes one of an initial registration request or a service request; and when, in response to transmitting the request to the specific network, a non-integrity protection rejection message is received from the specific network indicating that the specific network does not allow the specific network access mode, disable the specific network access mode for the specific entry or the specific network used to transmit the request, start a timer, and increment a corresponding counter of one or more counters associated with the specific entry that is associated with a reason value indicated in the non-integrity protection rejection message; when the timer expires, if the counter value of the corresponding counter of the one or more counters is below a predetermined threshold, re-enable the specific network access mode for the specific entry or the specific network used to transmit the request; and when the timer expires, if the counter value of the corresponding counter of the one or more counters is equal to or greater than the predetermined threshold,and including in the list of one or more entry indexes or the list of one or more network identities an index of a particular entry or an identification of a particular network to be used in sending the request.

[0027] Various other aspects are set forth in the following detailed description and appended claims.

[0028] Having generally described embodiments of the present disclosure above, reference will now be made to the accompanying drawings, which are not necessarily drawn to scale. [Brief explanation of the drawings]

[0029] [Figure 1] FIG. 1 illustrates an exemplary architecture of a communication network, according to some embodiments. [Figure 2] FIG. 1 illustrates an exemplary architecture of a communication network, according to some embodiments. [Figure 3] FIG. 1 illustrates an exemplary architecture of a communication network, according to some embodiments. [Figure 4] FIG. 1 illustrates an exemplary computing device for managing device capabilities in a private network, according to some embodiments. [Figure 5] FIG. 1 illustrates an exemplary computing device for managing user equipment capabilities for a private network, according to some embodiments. [Figure 6] FIG. 1 illustrates an exemplary approach for user equipment to request initial registration with a network, according to some embodiments. [Figure 7] FIG. 1 illustrates an exemplary technique for user equipment to request the provision of a service from a network, according to some embodiments. [Figure 8]6 is a flowchart illustrating operations performed to manage user equipment capabilities for a private network, such as by the apparatus of FIG. 4 or 5, according to one embodiment. [Figure 9] 6 is a flowchart illustrating operations performed to manage user equipment capabilities for a private network, such as by the apparatus of FIG. 4 or 5, according to another embodiment. [Figure 10] 6 is a flowchart illustrating operations performed to manage user equipment capabilities for a private network, such as by the apparatus of FIG. 4 or 5, according to yet another embodiment. [Figure 11] 6 is a flowchart illustrating operations performed to manage user equipment capabilities for a private network, such as by the apparatus of FIG. 4 or 5, according to yet another embodiment. [Figure 12] 6 is a flowchart illustrating operations performed to manage user equipment capabilities for a private network, such as by the apparatus of FIG. 4 or 5, according to yet another embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0030] Certain embodiments of the present invention will now be described in more detail with reference to the accompanying drawings, in which some, but not all, embodiments of the invention are shown. Indeed, various embodiments of the present invention may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will satisfy applicable legal requirements. As used herein, the term "or" is used in both its alternative and in conjunction, unless otherwise specified. The terms "illustrative" and "exemplary" are used as examples without designation of level of quality. Like reference numerals refer to like elements throughout. As used herein, the terms "data," "content," "information," and similar terms may be used interchangeably to refer to data that may be transmitted, received, and / or stored in accordance with embodiments of the present invention. Therefore, use of any such terms should not be taken to limit the spirit or scope of embodiments of the present invention.

[0031] Also, as used herein, the term “circuitry” refers to (a) a hardware-only circuit implementation (e.g., an implementation in analog and / or digital circuitry), (b) a combination of a circuit and a computer program product in which software and / or firmware instructions stored in one or more computer-readable memories cooperate to cause a device to perform one or more functions described herein, and (c) a circuit such as, for example, a microprocessor or portion of a microprocessor that is not physically present but requires software or firmware for operation. This definition of “circuitry” applies to all uses of the term herein, including any claims. As another example, as used herein, the term “circuitry” includes implementations that include one or more processors and / or portions thereof and associated software and / or firmware. As another example, as used herein, the term “circuitry” includes, for example, baseband or application processor integrated circuits for mobile phones or similar integrated circuits in servers, cellular network devices, other network devices, and / or other computing devices.

[0032] As defined herein, a "computer-readable storage medium," which refers to a non-transitory physical storage medium (e.g., a volatile or non-volatile memory device), is distinguishable from a "computer-readable transmission medium," which refers to an electromagnetic signal. Such media can take many forms, including, but not limited to, non-transitory computer-readable storage media (e.g., a non-volatile medium, a volatile medium) and transmission media. Transmission media include, for example, coaxial cable, copper wire, fiber optic cable, and carrier waves that travel through space without wires or cables, such as acoustic waves and electromagnetic waves (including radio waves, light waves, and infrared waves). Signals include artificially induced transient variations in amplitude, frequency, phase, polarization, or other physical characteristics that are transmitted through a transmission medium. Examples of non-transitory computer-readable media include magnetic computer-readable media (e.g., floppy disks, hard disks, magnetic tape, or any other magnetic media), optical computer-readable media (e.g., compact disk read-only memory (CD-ROM), digital versatile disk (DVD), Blu-ray disk, etc.), random access memory (RAM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), flash EPROM, or any other non-transitory medium readable by a computer. In this specification, the term computer-readable storage medium is used to refer to any computer-readable medium excluding transmission media. However, it will be appreciated that where an embodiment is described as employing a computer-readable storage medium, in alternative embodiments, other types of computer-readable media may be used in place of or in addition to the computer-readable storage medium.

[0033] While various embodiments of the present invention have been described and illustrated herein, those skilled in the art will readily envision numerous other means and / or structures for performing the functions and / or results and / or obtaining one or more of the advantages described herein, and each such variation and / or improvement is deemed to be within the scope of the embodiments of the present invention described herein. More generally, those skilled in the art will understand that all parameters, dimensions, materials, and configurations described herein are intended to be exemplary, and that the actual parameters, dimensions, materials, and / or configurations will depend on the specific application or applications in which the teachings of the present invention are used. Those skilled in the art will recognize, or be able to ascertain with no more than routine experimentation, many equivalents to the specific embodiments of the present invention described herein. Accordingly, it will be understood that the above-described embodiments are presented by way of example only, and that, within the scope of the appended claims and equivalents thereof, embodiments of the present invention may be practiced otherwise than as specifically described and claimed. The inventive embodiments of the present disclosure are directed to each individual feature, system, article, material, kit, and / or method described herein. Also, any combination of two or more such features, systems, articles, materials, kits, and / or methods, if such features, systems, articles, materials, kits, and / or methods are not mutually inconsistent, is included within the inventive scope of the present disclosure.

[0034]

[0013] Specific embodiments will now be described with reference to a mobile communication device capable of communicating via a wireless cellular system and a mobile communication system serving such a mobile communication device. Prior to a detailed description of exemplary embodiments, certain general principles of a wireless communication system, its access system, and a mobile communication device will be briefly described with reference to Figures 1-3 to aid in understanding the technology underlying the described examples.

[0035] According to some embodiments, a communications device or terminal is provided that allows wireless access via a cell, base station, or similar wireless transmitter and / or receiver node that provides an access point of a wireless access system.

[0036] An access point, and thus communications through it, is typically controlled by at least one suitable controller to enable management of its operation and the mobile communications devices communicating therewith. In some embodiments, a node controller may be integrated with, coupled to, and / or provided for control of the access point. In some embodiments, the controller is configurable to enable communications between user equipment and the core network or a network entity of the core network. To this end, the controller may comprise at least one memory, at least one data processing unit such as a processor, and an input / output interface. The controller may be coupled to other relevant components of the access point via interfaces. The controller may be configured to provide control functionality by executing appropriate software code. Of course, similar components may be provided in controllers located elsewhere in the network system (e.g., in core network entities). The controller may be interconnected with other control entities. The controller and functions may be distributed among multiple control units. In some embodiments, each base station may comprise a controller. In alternative embodiments, two or more base stations may share a controller.

[0037] The access points and associated controllers may be adapted to communicate with each other via wired and / or wireless interfaces. The logical connection between the base station nodes may be provided by an interface such as X2. This interface may be used, for example, to coordinate base station operations and to perform reselection or handover operations.

[0038] A communication device or user equipment may comprise any suitable device capable of receiving at least wireless communication data. For example, the device may be a handheld data processing device equipped with a wireless receiver, data processing, and user interface devices. Non-limiting examples include a mobile station (MS) such as a mobile phone or what is known as a "smartphone," a portable computer such as a laptop or tablet computer equipped with a wireless interface mechanism such as a wireless interface card, a personal data assistant (PDA) equipped with wireless communication capabilities, or any combination thereof. Other examples include a wearable wireless device integrated into a watch or smartwatch, eyewear, a helmet, a hat, clothing, an earpiece with wireless connectivity, jewelry, or the like, a universal serial bus (USB) stick with wireless capabilities, a modem data card, a mechanical device, or any combination thereof.

[0039] In some embodiments, a communications device configured to communicate with, for example, a wireless network or core network entity may be exemplified by a handheld or other mobile communications device (e.g., user equipment (UE)). The mobile communications device may be provided with wireless communications capabilities and appropriate electronic controllers to enable its operation. To this end, the communications device may be provided with at least one data processing entity (e.g., a central processing unit and / or core processor), at least one memory, and other possible components such as additional processors and memories used for software and hardware-assisted execution of the tasks it is designed to perform. Data processing, storage, and other related controllers may be provided on an appropriate circuit board and / or in a chipset. The data processing and memory functions provided by the communications device controller are configured to effect control and signaling operations according to certain embodiments, as described below in this specification. A user may control the operation of the communications device by a suitable user interface, such as a touch-sensitive display screen or pad and / or keypad, one or more actuator buttons, voice commands, or a combination thereof. A speaker and microphone are also typically provided. Additionally, the mobile communication device may be equipped with suitable connectors (wired or wireless) to other devices and / or for connecting external accessories (eg, hands-free devices).

[0040] In some embodiments, the communications device may be adapted to communicate wirelessly via a suitable device for transmitting and receiving signals. In some embodiments, a radio unit may be connected to the device's controller. The radio unit may comprise a radio section and an associated antenna arrangement. The antenna arrangement may be located internally or externally to the communications device.

[0041] 1-3 illustrate various example architectures of a communications network 100 in which various methods, apparatus, and computer program products may be implemented and / or used. In some embodiments, the communications network 100 may comprise any suitable configuration, number, orientation, location, and / or dimensions of components and specialized equipment configured to provide air interface (e.g., New Radio (NR)) communications or connectivity between a user equipment 102 (UE 102) and a data network 116 (DN 116) via a core network 101 (CN 101) of the communications network 100. As shown in FIG. 1 , the communications network 100 may include a transmission tower, base station, network node, etc., that places the UE 102 in operative communication with an AN 104. In some embodiments, the AN 104 may be in communication with the CN 101 or a component or entity thereof. In some embodiments, the CN 101 may facilitate communications between the UE 102 and the DN 116, such as transmission of data, messages, requests, etc. In some embodiments, the DN 116 or CN 101 can be in communication with an application server or application function 112 (AS / AF 112).

[0042] In the context of a fifth-generation (5G) network such as those shown in FIGS. 2 and 3 , a communications network 100 may include a set of connectivity network devices and dedicated hardware distributed throughout a service region or country, and one or more network entities that may be stored and / or hosted by one or more of the connectivity network devices or dedicated hardware. In some embodiments, a UE 102 may be connected to an AN 104, which may relay information between the UE 102 and a CN 101 connected to a DN 116, which may be in communication with one or more AS / AFs 112. In some embodiments, the UE 102 may be in communication with a radio access network 104 (RAN 104 or (R)AN 104), which may act as a relay between the UE 102 and other components or services of the CN 101. For example, in some embodiments, the UE 102 may be in communication with the RAN 104, which may be in communication with an Access and Mobility Management Function 108 (AMF 108). In other examples or embodiments, the UE 102 may be in direct communication with the AMF 108. In some embodiments, the AMF 108 may be in communication with one or more Network Functions (NFs), such as an Authentication Server Function (AUSF 120), a Network Slice Selection Function (NSSF 122), a Network Repository Function (NRF 124), a Policy Charging Function (PCF 114), a Network Data Analytics Function (NWDAF 126), a Unified Data Management Function (UDM 118), an AS / AF 112, a Session Management Function (SMF 110), and / or the like.

[0043] In some embodiments, the SMF 110 may be in communication with one or more User Plane Functions 106 (UPFs 106, UPFs 106a, UPFs 106b (collectively "UPFs 106"). In some embodiments, the UPFs 106 may be in communication with the RAN 104 and the DNs 116, but this is by way of example only. In other embodiments, the DNs 116 may be in communication with the first UPF 106a, and the RAN 104 may be in communication with the second UPF 106b. Alternatively, the SMF 110 may be in communication with both the first and second UPFs 106a, 106b, and the first and second UPFs 106a, 106b may be in communication with each other.

[0044] In some embodiments, the UE 102 may comprise a single-mode or dual-mode device such that it can connect to one or more RANs 104. In some embodiments, the RAN 104 may be configured to implement one or more radio access technologies (RATs) that can be used to connect the UE 102 to the CN 101, such as Bluetooth, Wi-Fi, and GSM, UMTS, LTE, or 5G NR, among others. In some embodiments, the RAN 104 may comprise or be implemented using a chip in the UE 102, such as a silicon chip, that can pair with or be recognized by a similar chip in the CN 101, such that the chip in the UE 102 and the chip in the CN 101 can be identified and paired to establish a communications connection or link between the UE 102 and the CN 101. In some embodiments, the RAN 104 may be implemented using one or more base stations, towers, etc., to communicate between the UE 102 and the AMF 108 of the CN 101.

[0045] In some embodiments, the communications network 100 or components thereof (e.g., base stations, towers, etc.) can be configured to communicate with communications devices (e.g., UEs 102), such as mobile phones, over multiple different frequency bands (e.g., FR1 (sub-6 GHz), FR2 (mmWave), other suitable frequency bands, sub-bands thereof, and / or the like). In some embodiments, the communications network 100 can also include or employ massive multiple-input multiple-output (massive MIMO) antennas. In some embodiments, the communications network 100 can include multi-user MIMO (MU-MIMO) antennas. In some embodiments, the communications network 100 can employ edge computing, in which computer servers are communicatively, physically, computationally, and / or temporally closer to the communications devices (e.g., UEs 102) to reduce latency and data traffic congestion. In some embodiments, the communications network 100 can employ other technologies, devices, or techniques, such as small cells, low-power RANs, radio beamforming, Wi-Fi-cellular convergence, non-orthogonal multiple access (NOMA), channel coding, etc.

[0046] As shown in FIG. 3 , the UE 102 may be configured to communicate with the RAN 104 over an N1 interface (e.g., according to a non-access stratum (NAS) protocol). In some embodiments, the RAN 104 is configurable to communicate with the CN 101 or components thereof (e.g., the AMF 108) over an N2 interface (e.g., a control plane between a base station of the RAN 104 and the AMF 108). In some embodiments, the RAN 104 is configurable to communicate with the UPF 106 over an N3 interface (e.g., a user plane). In some embodiments, the AMF 108 and / or the SMF 110 are configurable to communicate with other service or network entities in the CN 101 over different interfaces and / or different protocols. For example, in some embodiments, the AMF 108 and / or the SMF 110 are configurable to communicate with the AUSF 120 over a Nausf interface or an N12 interface. In some embodiments, the AMF 108 and / or the SMF 110 are configurable to communicate with the NSSF 122 over a Nnssf interface. In some embodiments, the AMF 108 and / or SMF 110 are configurable to communicate with the NRF 124 over an Nnrf interface. In some embodiments, the AMF 108 and / or SMF 110 are configurable to communicate with the PCF 114 over an Npcf interface or an N7 interface. In some embodiments, the AMF 108 and / or SMF 110 are configurable to communicate with the NWDAF 126 over an Nnwdaf interface. In some embodiments, the AMF 108 and / or SMF 110 are configurable to communicate with the UDM 118 over an Nudm interface, an N8 interface, or an N10 interface. In some embodiments, the AMF 108 and / or SMF 110 are configurable to communicate with the AS / AF 112 over a Naf interface.In some embodiments, the SMF 110 can be configured to communicate with the UPF 106 over the N4 interface, which can act as a bridge between the control plane and the user plane, for example, acting as a conduit for protocol data unit (PDU) sessions through which information is transported between the UE 102 and the CN 101 or its components / services.

[0047] It should be understood that the exemplary embodiments of the present invention disclosed and / or described herein occur in the context of telecommunications networks, including, but not limited to, telecommunications networks conforming to and / or incorporating aspects of a fifth generation (5G) architecture. While Figures 1-3 illustrate various configurations and / or components of an exemplary architecture for communications network 100, many other systems, system configurations, networks, network entities, and paths / protocols for communication therebetween are contemplated and considered within the scope of the present disclosure.

[0048] The methods, devices, and computer program products described herein are described in the context of fifth generation (5G) core networks and systems as shown in Figures 1-3 and described above, but are nevertheless applicable to any suitable telecommunications system, network, standard, or protocol in a broader context.

[0049] In the context of a communication system (e.g., a fifth-generation (5G) network), a user equipment (UE) may request access to a network or request a service from the network. A non-standalone non-public network is a non-public network (NPN) deployed with support of a public PLMN using a CAG and / or network slicing. When an NPN is made available by the PLMN, the UE 102 has a subscription to the PLMN to access the network and obtain services provided by the network. A CAG identifies a set of subscribers authorized to access one or more CAG cells. When a UE 102 requests access to or service provision by a network, the network must verify, among other considerations, whether the UE 102 is authorized to access the network, whether the network is configured to communicate via a requested access mode, and whether the requested access is via a trusted or untrusted connection.

[0050] In some embodiments, the network may need to know the UE's 102 Subscription Permanent Identifier (SUPI) to verify the UE's 102 access. The UE 102 may send the Subscription Concealed Identifier (SUCI) to the network during the initial Non-Access Stratum (NAS) procedure (registration procedure) in accordance with TS 33.501. The serving network receives the UE's 102 SUPI from the Authentication Server Function (AUSF) only after a successful primary authentication. Therefore, if the serving network needs to perform an access control procedure as described herein for the UE during the initial registration procedure, the AMF 108 may or may need to wait until the primary authentication procedure is successfully completed.

[0051] In some embodiments, when a UE 102 seeks to access a system or network (e.g., 5GS), it may first perform an access control check to determine whether it is authorized to access the network. In some embodiments, the access control check may be performed for access attempts defined by the following list of events:

[0052] a) The UE 102 is in idle mode (e.g., 5G Mobility Management [5GMM]-IDLE mode) on a 3GPP access and an event occurs that requires a transition to connected mode (e.g., 5GMM-CONNECTED mode).

[0053] b) The UE 102 is in a connected mode (e.g., 5GMM-CONNECTED mode) on a 3GPP access or a connected mode (e.g., 5GMM-CONNECTED mode) with a radio resource control (RRC) inactivity indicator, and one of the following events occurs:

[0054] 1) The 5GMM receives a Managed Object-Multimedia Telephone (MO-MMTEL)-Voice Call Start Indication, a MO-MMTEL-Video Call Start Indication, or a MO-SMS-over-IP (SMSoIP)-Attempt Start Indication from upper layers.

[0055] 2) The 5GMM receives a request from higher layers to send a mobile-originated SMS-over-NAS if the request has not triggered a service request procedure that transitions the UE 102 from 5GMM-IDLE mode to 5GMM-CONNECTED mode.

[0056] 3) The 5GMM receives a request from upper layers to send a UL NAS TRANSPORT message for the purpose of PDU session establishment, if the request does not trigger a service request procedure that transitions the UE 102 from 5GMM-IDLE mode to 5GMM-CONNECTED mode.

[0057] 4) The 5GMM receives a request from upper layers to send a UL NAS TRANSPORT message for PDU session modification if the request has not triggered a service request procedure to transition the UE 102 from 5GMM-IDLE mode to 5GMM-CONNECTED mode.

[0058] 5) The 5GMM receives a request to re-establish user plane resources for an existing PDU session.

[0059] In some embodiments, 5GMM-specific procedures initiated by the NAS in 5GMM-CONNECTED mode may not be subject to access control. For example, a registration procedure after a PS handover is not blocked by access control. In some embodiments, when the NAS detects one of the above events, it must map the request type to one or more access identities and an access category. Lower layers will perform an access barring check on the request based on the determined access identities and access categories. In some embodiments, the NAS can recognize the above events based on an indication provided by higher layers and / or a determination that a 5GMM procedure needs to be initiated according to normal NAS behavior.

[0060] In some embodiments, to determine the access identity and access category of the request, the NAS checks the profile of the UE 102, including the reason for access, the type of service requested, and the UE configuration, against a set of access identities and access categories specified in 3GPP TS 22.261, i.e., a) a set of standardized access identities, b) a set of standardized access categories, and, if available, c) a set of operator-defined access categories. To determine the applicable access identity from the set of standardized access identities specified in 3GPP TS 22.261, the NAS may or shall follow the requirements, rules, actions, etc. described herein and / or in 3GPP TS 22.261.

[0061] In some embodiments, the applicable access category is determined from a set of standardized and operator-defined access categories specified in 3GPP TS 22.261.

[0062] Turning now to FIG. 4 , an example core network device (CNA) (including core network services: UPF 106, AMF 108, SMF 110, PCF 114, and / or another NF and / or NRF) configured in accordance with an example embodiment of the present disclosure may be embodied as a core network device 200. As described below in conjunction with the flowcharts of FIGS. 8-12 , the CNA 200 of an example embodiment may be configured to perform the functions described herein. In any example, the CNA 200 may be more generally embodied by a computing device such as a server, personal computer, computer workstation, or other type of computing device, including those that function as user equipment and / or a wireless local area network. Regardless of how the CNA 200 is embodied, the device of an example embodiment may include, be associated with, or be configured to communicate with, processing circuitry 208, including, for example, a processor 202 and a memory device 204, and / or, in some embodiments, a communication interface 206, as shown in FIG. 4 . In some embodiments, the UE 102 or other elements of the system 100 may be embodied by a device such as the CNA 200 of FIG.

[0063] In the processing circuitry 208, the processor 202 (and / or any coprocessor or other circuitry supporting or associated with the processor) may be in communication with the memory device 204 via a bus that passes information between components of the CNA 200. The memory device may include, for example, one or more volatile and / or non-volatile memories. In other words, the memory device may be, for example, an electronic storage device (e.g., a computer-readable storage medium) with gates configured to store data (e.g., bits) readable by a machine (e.g., a computing device such as a processor). The memory device may be configured to store information, data, content, applications, instructions, etc. that enable an apparatus to perform various functions in accordance with an exemplary embodiment of the present invention. For example, the memory device may be configured to buffer input data for processing by the processor. Additionally or alternatively, the memory device may be configured to store instructions for execution by the processor.

[0064] In some embodiments, CNA 200 may be embodied in various computing devices, as described above. However, in some embodiments, the apparatus may be embodied as a chip or chipset. In other words, the apparatus may include one or more physical packages (e.g., chips) containing materials, components, and / or wires on a structural assembly (e.g., baseboard). The structural assembly may provide physical strength, size conservation, and / or limited electrical interaction of the component circuits contained thereon. Thus, the apparatus may, in some cases, be configured to implement an embodiment of the present invention on a single chip or as a single "system-on-chip." Thus, in some cases, the chip or chipset may comprise means for performing one or more operations that provide the functionality described herein.

[0065] The processor 202 may be embodied in many different ways. For example, the processor may be embodied as one or more of various hardware processing means, such as a coprocessor, a microprocessor, a controller, a digital signal processor (DSP), a processing element with or without a DSP, or various other circuits including integrated circuits such as an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), a microcontroller unit (MCU), a hardware accelerator, a dedicated computer chip, etc. Thus, in some embodiments, the processor may include one or more processing cores configured to execute independently. A multi-core processor may enable multi-processing within a single physical package. Additionally or alternatively, the processor may include one or more processors in a tandem configuration via a bus to enable independent execution of instructions, pipelining, and / or multithreading.

[0066] In an exemplary embodiment, the processor 202 may be configured to execute instructions stored on or accessible to the memory device 204. Alternatively or additionally, the processor may be configured to execute hard-coded functions. Thus, whether configured in a hardware or software manner, or a combination thereof, a processor may represent an entity (e.g., physically embodied in circuitry) capable of performing operations according to an embodiment of the present disclosure. Thus, a processor may be specially configured hardware to perform the operations described herein, for example, when embodied as an ASIC, FPGA, etc. Alternatively, as another example, when a processor is embodied as an instruction executor, the instructions may specifically configure the processor to perform the algorithms and / or operations described herein upon execution of the instructions. However, in some cases, the processor may be the processor of a particular device (e.g., an encoder and / or decoder) configured to employ an embodiment of the present invention by further configuring the processor to perform the algorithms and / or operations described herein. A processor may include, among other things, a clock, an arithmetic processing unit (ALU), and logic gates configured to facilitate the operation of the processor.

[0067] In embodiments including a communications interface 206, the communications interface may be any device or circuitry embodied in hardware or a combination of hardware and software configured to receive and / or transmit data to or from a network and / or any other device or module in communication with the CNA 200, such as an NF, NRF, UE 102, a radio access network, a core network service, an application server / function, a database or other storage device, or the like. In this regard, the communications interface may include, for example, an antenna (or multiple antennas) and supporting hardware and / or software to enable communication with a wireless communications network. Additionally or alternatively, the communications interface may include circuitry that interacts with the antenna to process the transmission of signals via the antenna or the reception of signals received via the antenna. In some environments, the communications interface may alternatively or additionally support wired communications. Thus, for example, the communications interface may include a communications modem and / or other hardware / software to support communications via cable, digital subscriber line (DSL), universal serial bus (USB), or other mechanisms. In some embodiments, the session management function may include a 5GC session management function for any suitable CUPS architecture, such as a Gateway GPRS Support Node (GGSN-C), TWAG-C, BNG-CUPS, N4, Sxa, Sxb, Sxc, Evolved Packet Core (EPC) SWG-C, EPC PGW-C, EPC TDF-C, and / or the like.

[0068] In some embodiments, CNA 200 may represent user equipment configured to connect to other core network entities or network equipment, such as a mobile telephone.

[0069] As shown, CNA 200 may include a processor 202 in communication with memory 204 and configured to provide signals to and receive signals from communication interface 206. In some embodiments, communication interface 206 may include a transmitter and a receiver. In some embodiments, processor 202 is configurable to control at least a portion of the functionality of CNA 200. In some embodiments, processor 202 may be configured to control the functionality of the transmitter and receiver by performing control signal transmission over conductors to the transmitter and receiver. Similarly, processor 202 may be configured to control other elements of CNA 200 by performing control signal transmission over conductors connecting processor 202 to other elements, such as a display or memory 204. Processor 202 may be embodied in a variety of ways, including, for example, as a circuit, at least one processing core, one or more microprocessors with digital signal processors, one or more processors without digital signal processors, one or more coprocessors, one or more multi-core processors, one or more controllers, processing circuits, one or more computers, various other processing elements including integrated circuits (e.g., application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), and / or the like), or any combination thereof. Thus, although shown as a single processor in FIG. 4, in some exemplary embodiments, processor 202 may include multiple processors or processing cores.

[0070] CNA 200 may be operable with one or more air interface standards, communication protocols, modulation types, access types, and / or the like. Signals transmitted and received by processor 202 may include signaling information according to applicable cellular system air interface standards and / or any number of different wired or wireless networking technologies, including, but not limited to, Wi-Fi, wireless local access network (WLAN) technologies such as Institute of Electrical and Electronics Engineers (IEEE) 802.11, 802.16, 802.3, ADSL, DOCSIS, and / or the like. These signals may also include speech data, user-generated data, user-requested data, and / or the like.

[0071] For example, CNA 200 and / or the cellular modem therein may be capable of operating according to various first-generation (1G), second-generation (2G or 2.5G), third-generation (3G), fourth-generation (4G), fifth-generation (5G), Internet Protocol Multimedia Subsystem (IMS) communication protocols (e.g., Session Initiation Protocol (SIP)), and / or the like. For example, device 10 may be capable of operating according to 2G wireless communication protocols IS-136 (Time Division Multiple Access TDMA), Global System for Mobile Communications (GSM), IS-95 (Code Division Multiple Access CDMA), and / or the like. Also, for example, device 10 may be capable of operating according to 2.5G wireless communication protocols General Packet Radio Service (GPRS), Enhanced Data GSM Environment (EDGE), and / or the like. Further, for example, CNA 200 may be capable of operating according to 3G wireless communication protocols, such as Universal Mobile Telecommunications System (UMTS), Code Division Multiple Access 2000 (CDMA2000), Wideband Code Division Multiple Access (WCDMA), Time Division Synchronous Code Division Multiple Access (TD-SCDMA), and / or the like. CNA 200 may also be capable of operating according to 3.9G wireless communication protocols, such as Long Term Evolution (LTE), Evolved Universal Terrestrial Radio Access Network (E-UTRAN), and / or the like. CNA 200 may also be capable of operating according to 4G wireless communication protocols, such as LTE-Advanced, 5G, and / or the like, as well as similar wireless communication protocols that may be developed in the future.In some embodiments, CNA 200 may conform to or be operable within the framework of any suitable Control-User Plane Separation (CUPS) architecture, such as a Gateway GPRS Support Node (GGSN-C), Trusted Radio Access Gateway (TWAG-C), Broadband Network Gateway (BNG), N4, Sxa, Sxb, Sxc, Evolved Packet Core (EPC) SWG-C, EPC PGW-C, EPC TDF-C, and / or the like.

[0072] It will be appreciated that processor 202 may include circuitry for implementing the audio / video and logic functions of CNA 200. For example, processor 202 may include a digital signal processor device, a microprocessor device, an analog-to-digital converter, a digital-to-analog converter, and / or the like. The control and signal processing functions of CNA 200 may be distributed among these devices according to their respective capabilities. Processor 202 may also include an internal voice coder (VC), an internal data modem (DM), and / or the like. Processor 202 may also include functionality for operating one or more software programs, which may be stored in memory 204. Generally, the software instructions stored in processor 202 and memory 206 may be configured to cause CNA 200 to perform operations. For example, processor 202 may be capable of operating a connectivity program, such as a web browser. The connectivity program may enable CNA 200 to send and receive web content, such as location-based content, according to protocols such as Wireless Application Protocol (WAP), Hypertext Transfer Protocol (HTTP), and / or the like.

[0073] In some embodiments, the CNA 200 may also include a user interface, including, for example, an earphone or speaker, a ringer, a microphone, a display, a user input interface, and / or the like, which may be operatively coupled to the processor 202. The display may include a touch-sensitive display, as described above, and a user may make selections, input values, and / or the like by touch and / or gestures. The processor 202 may also include user interface circuitry configured to control at least some functionality of one or more elements of the user interface, such as the speaker, ringer, microphone, display, and / or the like. The processor 202 and / or the user interface circuitry comprising the processor 202 may be configured to control one or more functions of one or more elements of the user interface through computer program instructions (e.g., software and / or firmware) stored in a memory 204 accessible by the processor 202 (e.g., a volatile memory, a non-volatile memory, a device including these, and / or the like). CNA 200 may include a battery that powers various circuits associated with the mobile terminal (e.g., circuitry that provides mechanical vibration as a detectable output). A user input interface may include devices that allow data to be accepted by CNA 200, such as a keypad (e.g., a virtual keyboard presented on a display or an externally connected keyboard) and / or the like.

[0074] 4, the CNA 200 may also include one or more mechanisms for sharing and / or obtaining data, shown as a communication interface 206. For example, the communication interface 206 of the CNA 200 may include a short-range radio frequency (RF) transceiver and / or interrogator, so that data can be shared with and / or obtained from electronic devices according to RF technology. The CNA 200 may also include other short-range transceivers, such as an infrared (IR) transceiver, a Bluetooth™ (BT) transceiver operating using Bluetooth™ wireless technology, a wireless universal serial bus (USB) transceiver, a Bluetooth™ low power transceiver, a ZigBee transceiver, an ANT transceiver, a cellular device-to-device transceiver, a wireless local area link transceiver, and / or any other short-range wireless technology. In some embodiments, the CNA 200, and in particular the short-range transceiver, may be capable of transmitting data to and / or receiving data from electronic devices in close proximity to the device, e.g., within approximately 10 meters. Additionally, the CNA 200 equipped with a Wi-Fi or wireless local area networking modem may be capable of transmitting data to and / or receiving data from electronic devices according to various wireless networking technologies, including WLAN technologies such as 6LoWpan, Wi-Fi, low power Wi-Fi, IEEE 802.11 technology, IEEE 802.15 technology, IEEE 802.16 technology, and the like.

[0075] CNA 200 may include other memory, such as a subscriber identity module (SIM), a removable user identity module (R-UIM), an eUICC, a UICC, and / or the like, that may store information elements associated with a mobile subscriber. In addition to a SIM, CNA 200 may include other removable and / or fixed memory. CNA 200 may include volatile and / or nonvolatile memory, which may include some or all of memory 204 or may be separate memory within or connected to CNA 200. For example, volatile memory may include random access memory (RAM), including dynamic and / or static RAM, on-chip or off-chip cache memory, and / or the like. The embedded and / or removable non-volatile memory may include, for example, read-only memory, flash memory, magnetic storage devices (e.g., hard disks, floppy disk drives, magnetic tape), optical disk drives and / or media, non-volatile random access memory (NVRAM), and / or the like. Like volatile memory, non-volatile memory may include a cache area for temporarily storing data. At least a portion of the volatile and / or non-volatile memory may be embedded in the processor 202. The memory may store one or more software programs, instructions, information, data, and / or the like usable by the device to perform the operations disclosed herein. Alternatively or additionally, the CNA 200 may be configured to provide the operations disclosed herein to a base station, a WLAN access point, a network node, one or more UEs 102, and / or the like.

[0076] The memory may include an identifier, such as an International Mobile Equipment Identity (IMEI) code, that can uniquely identify the CNA 200. The memory may include an identifier, such as an International Mobile Equipment Identity (IMEI) code, that can uniquely identify the CNA 200. In this exemplary embodiment, the processor 202 may be configured to use computer code stored in the memory to provide the operations disclosed herein to a base station, a WLAN access point, a network node, one or more UEs 102, and / or the like. Similarly, the CNA 200 may be configurable to be other components or network equipment of a core network.

[0077] Some of the embodiments disclosed herein may be implemented in software, hardware, application logic, or a combination of software, hardware, and application logic. The software, application logic, and / or hardware may reside, for example, in memory 204, controller 202, or electronic components. In some exemplary embodiments, the application logic, software, or instruction set is maintained on any one of a variety of conventional computer-readable media. In the context of this specification, a "computer-readable medium" may be any non-transitory medium capable of containing, storing, transmitting, propagating, or transporting instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer or data processor circuitry. In the example shown in FIG. 4, the computer-readable medium may include a non-transitory computer-readable storage medium, which may be any medium capable of containing or storing instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer.

[0078] 5 illustrates another example of an apparatus 300 configurable in accordance with an example embodiment of the present disclosure (e.g., containing or embodying a core network entity, such as the CAN 200, the UE 102, and / or participating in or communicating with core network services (e.g., the UPF 106, the AMF 108, the SMF 110, the PCF 114, another Network Function (NF), and / or a Network Resource Function (NRF)). As described below in conjunction with the flowcharts of FIGS. 8-12, the apparatus 300 of an example embodiment may be configured to perform the functions, processes, and methods, combinations thereof, variations thereof, or portions thereof, described herein.

[0079] In some embodiments, device 300 is or comprises exemplary dedicated hardware specifically dimensioned and configured to perform any of the methods, processes, and techniques described herein. In some embodiments, device 300 can be part of system 100 or can be in communication with components thereof. It should be understood that device 300 is provided as an example of one embodiment and should not be construed as limiting the scope or spirit of the invention. In this regard, the scope of the present disclosure includes many potential embodiments in addition to the embodiments shown and described herein. Thus, while FIG. 5 illustrates one example configuration of an apparatus for processing emergency services in a private network or other wireless communication system, such as a 5G system, other configurations may be used to implement certain embodiments of the present disclosure.

[0080] Device 300 may be embodied as a desktop computer, a laptop computer, a mobile terminal, a mobile computer, a mobile telephone, a mobile communication device, a gaming device, a digital camera / camcorder, an audio / video player, a television device, a wireless receiver, a digital video recorder, a positioning device, a chipset, a computing device with a chipset, any combination thereof, and / or the like. In some exemplary embodiments, device 300 is embodied as a mobile computing device, such as a mobile telephone, a mobile computer, a personal digital assistant (PDA), a pager, a laptop computer, a desktop computer, a gaming device, a television, electronic paper, and other types of electronic systems that can employ various embodiments of the present invention.

[0081] Apparatus 300 may include a computing device 302 that includes a processor 304 and storage, such as non-volatile memory 306 and / or volatile memory 308. In some embodiments, processor 304 may be embodied as a variety of means, including, for example, a circuit, one or more microprocessors with digital signal processors, one or more processors without digital signal processors, one or more coprocessors, one or more multi-core processors, one or more controllers, processing circuitry, one or more computers, various other processing elements including integrated circuits (e.g., ASICs (application-specific integrated circuits) or FPGAs (field-programmable gate arrays)), or some combination thereof. Thus, although shown as a single processor in FIG. 5, in some embodiments, processor 304 includes multiple processors. These signals transmitted and received by the processor 304 may include signaling information according to an applicable cellular system air interface standard and / or any number of different wired or wireless networking technologies, including, but not limited to, Wi-Fi, Wireless Local Access Network (WLAN) technologies such as Institute of Electrical and Electronics Engineers (IEEE) 802.11, 802.16, and the like. These signals may also include speech data, user-generated data, user-requested data, and / or the like. In this regard, a mobile terminal may be capable of operating according to one or more air interface standards, communication protocols, modulation types, access types, and / or the like. More particularly, the mobile terminal may be capable of operating according to various first generation (1G), second generation (2G), 2.5G, third generation (3G) communication protocols, fourth generation (4G) communication protocols, fifth generation (5G), any band, frequency, or protocol thereof, Internet Protocol Multimedia Subsystem (IMS) communication protocols (e.g., Session Initiation Protocol (SIP)), and / or the like.For example, the mobile terminal may be capable of operating according to 2G wireless communication protocols IS-136 (Time Division Multiple Access (TDMA)), Global System for Mobile Communications (GSM), IS-95 (Code Division Multiple Access (CDMA)), and / or the like. Also, for example, the mobile terminal may be capable of operating according to 2.5G wireless communication protocols General Packet Radio Service (GPRS), Enhanced Data GSM Environment (EDGE), and / or the like. Furthermore, for example, the mobile terminal may be capable of operating according to 3G wireless communication protocols such as Universal Mobile Telecommunications System (UMTS), Code Division Multiple Access 2000 (CDMA2000), Wideband Code Division Multiple Access (WCDMA), Time Division Synchronous Code Division Multiple Access (TD-SCDMA), and / or the like. Also, the mobile terminal may be capable of operating according to 3.9G wireless communication protocols such as Long Term Evolution (LTE), Evolved Universal Terrestrial Radio Access Network (E-UTRAN), and / or the like. Also, for example, the mobile terminal may be capable of operating according to fourth generation (4G) wireless communication protocols and / or the like, as well as any similar wireless communication protocols that may be developed in the future.

[0082] In addition to broadband systems, some Narrowband Advanced Mobile Phone Systems (NAMPS) and Total Access Communication Systems (TACS) mobile terminals may also benefit from embodiments of the present invention, as may dual-mode or high-mode phones (e.g., digital / analog or TDMA / CDMA / analog phones). Additionally, device 300 or components thereof may be capable of operating according to Wi-Fi or WiMAX (Worldwide Interoperability for Microwave Access) protocols.

[0083] It will be appreciated that the processor 304 may include circuitry for implementing the audio / video and logic functions of the device 300. For example, the processor 304 may include a digital signal processor device, a microprocessor device, an analog-to-digital converter, a digital-to-analog converter, and / or the like. The control and signal processing functions of the mobile terminal may be distributed among these devices according to their respective capabilities. The processor may also include an internal voice coder (VC), an internal data modem (DM), and / or the like. The processor may also include functionality for operating one or more software programs that may be stored in memory. For example, the processor 304 may be capable of operating a connectivity program such as a web browser. The connectivity program may enable the device 300 to transmit and receive web content, such as location-based content, according to protocols such as the Wireless Application Protocol (WAP), Hypertext Transfer Protocol (HTTP), and / or the like. The device 300 may also be capable of transmitting and receiving web content over a network, such as the Internet, using the Transmission Control Protocol / Internet Protocol (TCP / IP).

[0084] The device 300 may also include a user interface 312, including, for example, an earphone or speaker, a ringer, a microphone, a user display, a user input interface, and / or the like, which may be operatively coupled to the processor 304. In this regard, the processor 304 may include user interface circuitry configured to control at least some functionality of one or more elements of the user interface, such as, for example, a speaker, a ringer, a microphone, a display, and / or the like. The processor 304 and / or the user interface circuitry comprising the processor 304 may be configured to control one or more functions of one or more elements of the user interface through computer program instructions (e.g., software and / or firmware) stored in memory accessible to the processor 304 (e.g., non-volatile memory 306, volatile memory 308, and / or the like). Although not shown, the device 300 may include a battery to power various circuits associated with the device 300 (e.g., circuitry that provides mechanical vibration as a detectable output). The device 300 may further include a display 314. In some embodiments, display 314 may be of any type suitable for the electronic device, some examples including a plasma display panel (PDP), a liquid crystal display (LCD), a light emitting diode (LED), an organic light emitting diode display (OLED), a projector, a holographic display, etc. User interface 312 may include devices that enable data to be accepted by device 300, such as a keypad, a touch display (e.g., in some exemplary embodiments, display 314 is configured as a touch display), a joystick (not shown), and / or other input devices. In some embodiments that include a keypad, the keypad may include numbers (0-9) and associated keys (#, *), and / or other keys to operate device 300.

[0085] The device 300 may include memory, such as non-volatile memory 306 and / or volatile memory 308 (e.g., RAM, read-only memory (ROM), non-volatile RAM (NVRAM)), a subscriber identity module (SIM), a removable user identity module (R-UIM), and / or the like. In addition to memory, the device 300 may include other removable and / or fixed memory. In some embodiments, the volatile memory 308 may include random access memory (RAM), including dynamic and / or static RAM, on-chip or off-chip cache memory, and / or the like. In some embodiments, the embedded and / or removable non-volatile memory 306 may include, for example, read-only memory, flash memory, magnetic storage devices (e.g., hard disks, floppy disk drives, magnetic tapes, etc.), optical disk drives and / or media, non-volatile random access memory (NVRAM), and / or the like. Like the volatile memory 308, the non-volatile memory 306 may include a cache area for temporarily storing data. The memory may store one or more software programs, instructions, information, data, and / or the like that can be used by the mobile terminal to perform the functions of the mobile terminal. For example, the memory may include an identifier, such as an International Mobile Equipment Identity (IMEI) code, that can uniquely identify device 300.

[0086] In some exemplary embodiments, apparatus 300 comprises various means for performing various functions described herein, which may include one or more of processor 304, non-volatile memory 306, volatile memory 308, user interface 312, or display 314. The means of apparatus 300 as described herein may be embodied, for example, as circuitry, hardware elements (e.g., a suitably programmed processor, combinational logic, and / or the like), a computer program product (e.g., software or firmware) containing computer-readable program instructions stored on a computer-readable medium (e.g., storage 306 or 308) and executable by a suitably configured processing device (e.g., processor 304), or some combination thereof.

[0087] In some exemplary embodiments, one or more of the means shown in FIG. 5 may be embodied as a chip or chipset. In other words, device 300 may include one or more physical packages (e.g., chips) that include materials, components, and / or wires on a structural assembly (e.g., a baseboard). The structural assembly may provide physical strength, size conservation, and / or limited electrical interaction of component circuits contained thereon. In this regard, processor 304, memory 306 and / or 308, user interface 312, and / or display 314 may be embodied as a chip or chipset. Thus, device 300 may, in some cases, be configured to implement embodiments of the present invention on a single chip or as a single “system-on-chip,” or may include components configured to implement embodiments of the present invention. Thus, in some cases, a chip or chipset may comprise means for performing one or more operations that provide the functionality described herein.

[0088] Processor 304 may be embodied as a variety of means, including, for example, one or more microprocessors with digital signal processors, one or more processors without digital signal processors, one or more coprocessors, one or more multi-core processors, one or more controllers, processing circuits, one or more computers, various other processing elements including integrated circuits (e.g., ASICs (Application Specific Integrated Circuits) or FPGAs (Field Programmable Gate Arrays)), one or more other types of hardware processors, or some combination thereof. Thus, although shown as a single processor in FIG. 5 , in some embodiments, processor 304 includes multiple processors. The multiple processors may be in operative communication with each other and may be collectively configured to perform one or more functions of apparatus 100 as described herein. The multiple processors may be embodied on a single computing device collectively configured to function as apparatus 300 or may be distributed across multiple computing devices. For example, in some embodiments in which the apparatus is embodied as apparatus 300, processor 304 may be embodied as or include processor 304 (shown in FIG. 5 ). In some exemplary embodiments, processor 304 is configured to execute instructions stored in or accessible to memory 306 and / or 308. These instructions, when executed by processor 304, may cause device 300 to perform one or more of the functions of device 300 as described herein. Thus, whether implemented in a hardware or software manner, or a combination thereof, processor 304 may comprise an entity that is accordingly configured to perform operations according to embodiments of the present invention. Thus, processor 304 may comprise specially configured hardware to perform one or more of the operations described herein, for example, when embodied as an ASIC, FPGA, etc.Alternatively, as another example, if processor 304 is embodied as an executor of instructions that may be stored in memory 306 and / or 308, etc., processor 304 may be specifically configured, by the instructions, to perform one or more of the algorithms and operations described herein.

[0089] Memory 306 and / or 308 may include, for example, volatile memory, nonvolatile memory, or some combination thereof. In this regard, memory 306 and / or 308 may include a non-transitory computer-readable storage medium. Although shown as a single memory in FIG. 5, memory 306 and / or 308 may include multiple memories. The multiple memories may be embodied on a single computing device configured as a whole to function as apparatus 300, or may be distributed across multiple computing devices. In various exemplary embodiments, memory 306 and / or 308 may include a hard disk, random access memory, cache memory, flash memory, a compact disc read-only memory (CD-ROM), a digital versatile disc read-only memory (DVD-ROM), an optical disk, circuitry configured to store information, or some combination thereof. In some embodiments, memory 306 and / or 308 may include volatile memory 308 (shown in FIG. 5) and / or nonvolatile memory 306. Memory 306 and / or 308 may be configured to store information, data, applications, instructions, etc. that enable device 300 to perform various functions in accordance with various exemplary embodiments. For example, in some exemplary embodiments, memory 306 and / or 308 is configured to buffer input data for processing by processor 304. Additionally or alternatively, memory 306 and / or 308 may be configured to store program instructions for execution by processor 304. Memory 306 and / or 308 may store information in the form of static and / or dynamic information. Stored information may include, for example, images, content, media content, user data, application data, and / or the like. This stored information may be stored in and / or used by processor 304 during the execution of functions.

[0090] In some embodiments, apparatus 300 may further comprise a communications interface (not shown), which may be embodied as circuitry, hardware, a computer program product including computer-readable program instructions stored on a computer-readable medium (e.g., memory 306 and / or 308) and executed by a processing device (e.g., processor 304), or any device or means embodied in a combination of the above configured to receive and / or transmit data from another computing device. In some exemplary embodiments, the communications interface is embodied at least in part as or controlled by processor 304. In this regard, the communications interface may be in communication with processor 304 via a bus or the like. The communications interface may comprise, for example, an antenna, a transmitter, a receiver, a transceiver, and / or supporting hardware or software that enables communication with one or more remote computing devices. For example, in some embodiments in which an apparatus is embodied as apparatus 300, the communications interface may be embodied as or comprise a transmitter and a receiver. The communications interface may be configured to receive and / or transmit data using any protocol available for communication between computing devices. In this regard, the communications interface may be configured to receive and / or transmit data using any protocol available for transmitting data over a wireless network, a wired network, any combination thereof, or any link through which apparatus 300 and one or more computing devices can communicate. As an example, the communications interface may be configured to receive and / or access content (e.g., web page content, streaming media content, and / or the like) from a content source, such as a server, over a network. The communications interface may also be in communication with memory 306 and / or 308, user interface 312, and / or processor 304 via a bus or the like.

[0091] User interface 312 may be configured to communicate with processor 304 and accept user input instructions and / or provide audio, visual, mechanical, or other output to a user. To this end, user interface 312 may include, for example, a keyboard, a mouse, a joystick, a display, a touchscreen display, a microphone, a speaker, and / or other input / output mechanisms. For example, in an embodiment in which device 300 is embodied as device 300, user interface 312 may be embodied as or include a user input interface, such as display 314 (shown in FIG. 5 ) and other components such as a keypad, a mouse, etc. User interface 312 may be in communication with memory 306 and / or 308, a communication interface, a sensor, a speaker, and / or processor 304 via a bus or the like. In some exemplary embodiments, user interface 312 may include a single input / output mechanism. In other embodiments, user interface 312 may include a content-presenting touch display, such as display 314. In some embodiments, the user interface 312 may include a touch display user interface with a content display portion and a dedicated user input portion, such as a virtual keyboard, a virtual piano, or an application with designated keys for user input.

[0092] The processor 304 may be embodied in various ways, such as circuitry, hardware, a computer program product including computer-readable program instructions stored on a computer-readable medium (e.g., memory 306 and / or 308) and executed by a processing device (e.g., processor 304), or some combination thereof, and in some embodiments is embodied as or controlled by the processor 304. The processor 304 may further be in communication with one or more of the memories 306 and / or 308 or the user interface 312 via a bus or the like.

[0093] The processor 304 may be configured to receive user input from a user interface 312, such as a touch display. The user input or signal may carry position information indicative of the user input. In this regard, position includes the location of the user input in two-dimensional space, which may be relative to the surface of the touch display user interface. For example, the position may include a coordinate position relative to a two-dimensional coordinate system (e.g., X and Y axes) such that the location may be determined. The processor 304 may thus determine an element / instruction / command corresponding to a key or image displayed on the touch display user interface at or within a predetermined vicinity (e.g., within a predetermined tolerance) of the determined location. The processor 304 may further be configured to perform a function or operation associated with the key corresponding to the element / instruction / command determined by the processor 304 based on the location of the user input, such as a touch.

[0094] Without limiting the scope, interpretation, or application of the following claims in any way, the technical effect of one or more of the exemplary embodiments disclosed herein may be an improvement in the configuration of user equipment or network equipment. Thus, any embodiment of a method, system, technique, device, apparatus, or computer program described or illustrated herein is understood to include any or all of the components, functions, elements, or steps of any other embodiment, such that any method may be performed by CNA 200, apparatus 300, or any other suitable system or device, as well as may be performed in accordance with computer program code contemplated within the scope of the present disclosure.

[0095] 6 and 7, in the context of a communication system (e.g., system 100), a UE 102 or the like may request network access or the provision of a service from the network by sending a registration request, an access request message, a service request, a session request message, or the like to an AMF 108.

[0096] Generally, an initial registration procedure may be performed by the UE 102 for initial registration with a particular network entity (e.g., the AMF 108) for 5GS services. In some embodiments, the UE 102 may or shall indicate "initial registration" in the 5GS registration type IE when initiating the registration procedure for initial registration. In some embodiments, the UE 102 may or shall indicate "emergency registration" in the 5GS registration type IE when initiating the registration procedure for emergency services.

[0097] In some embodiments, a UE 102 in state "5GMM-DEREGISTERED" may or shall initiate a registration procedure for initial registration by sending a REGISTRATION REQUEST message to the AMF 108 when:

[0098] a) When the UE 102 performs initial registration for the 5GS service

[0099] b) When the UE 102 performs an initial registration for emergency services

[0100] c) When the UE 102 performs an initial registration for SMS-over-NAS

[0101] d) When the UE 102 moves from GERAN to NG-RAN coverage or from UTRAN to NG-RAN coverage

[0102] In some embodiments, the UE 102 may initiate the registration procedure for initial registration by sending a REGISTRATION REQUEST message to the AMF 108 and may start timer T3510. If timer T3502 is currently running, the UE 102 may or shall stop timer T3502. If timer T3511 is currently running, the UE 102 may or shall stop timer T3511.

[0103] In some embodiments, if the UE 102 has a valid 5G-GUTI, it may or shall indicate the 5G-GUTI in the 5GS Mobile Identity IE. Otherwise, if the SUCI is available, the UE 102 may or shall include the SUCI in the 5GS Mobile Identity IE. If the UE 102 has initiated an emergency services registration procedure but does not have a valid 5G-GUTI or SUCI, the PEI may or shall be included in the 5GS Mobile Identity IE.

[0104] In some embodiments, when the UE 102 operates in dual registration mode and is in the EMM state EMM-REGISTERED, the UE 102 may or shall include a UE 102 status IE with EMM registration status set to "UE in EMM-REGISTERED state."

[0105] In some embodiments, including the UE Status IE in this configuration corresponds to indicating that the UE 102 has "moved out of EPC," as specified in 3GPP TS 23.502.

[0106] In some embodiments, if a last visit registration TAI is available, the UE 102 may or shall include this last visit registration TAI in the REGISTRATION REQUEST message.

[0107] In some embodiments, if the UE 102 requests the use of SMS-over-NAS, the UE 102 may or shall include an SMS Request IE in the REGISTRATION REQUEST message and set the SMS Request bit in the SMS Request IE to "SMS-over-NAS supported."

[0108] In some embodiments, the UE 102 may or shall include a MICO indicator IE in the REGISTRATION REQUEST message if it supports MICO mode and requests the use of MICO mode.

[0109] In some embodiments, the UE 102 may or shall include a Request DRX Parameters IE in the REGISTRATION REQUEST message if it wishes to use UE-specific DRX parameters.

[0110] In some embodiments, the UE 102 may or shall include in the REGISTRATION REQUEST message a Request NSSAI that includes an S-NSSAI corresponding to the slice for which the UE 102 wishes to register, and a mapping of each S-NSSAI of the Request NSSAI to an S-NSSAI of the NSSAI configured for the HPLMN, if available. If the UE 102 has authorized an NSSAI or an NSSAI configured for the current PLMN, the Request NSSAI may or shall be one of the following:

[0111] a) If the UE 102 does not have an allowed NSSAI for the current PLMN, then the configured NSSAI for the current PLMN or a subset thereof, as described below.

[0112] b) If the UE 102 has an allowed NSSAI for the current PLMN, then the allowed NSSAI for the current PLMN or a subset thereof, as described below.

[0113] c) The allowed NSSAIs or a subset thereof for the current PLMN, as described below, plus one or more S-NSSAIs from the configured NSSAIs whose corresponding S-NSSAIs are not present in the allowed NSSAIs and are not present in either the rejected NSSAIs for the current PLMN or the rejected NSSAIs for the combination of the current PLMN and registration area.

[0114] In some embodiments, if the UE 102 has neither an authorized NSSAI for the current PLMN nor a configured NSSAI for the current PLMN, and has a configured NSSAI that is not associated with a PLMN, the UE 102 may or shall include an S-NSSAI in the Requested-NSSAI IE of the REGISTRATION REQUEST message with the configured NSSAI that is not associated with a PLMN. If the UE 102 has neither an authorized NSSAI for the current PLMN nor a configured NSSAI for the current PLMN, and has a configured NSSAI that is not associated with a PLMN, the UE 102 may or shall not include a Requested-NSSAI in the REGISTRATION message.

[0115] The subset of configured NSSAIs provided in the request NSSAI consists of one or more S-NSSAIs in the configured NSSAIs applicable to the current PLMN if those S-NSSAIs are not present in the rejected NSSAIs for the current PLMN or the rejected NSSAIs for the combination of the current PLMN and registration area.

[0116] The subset of allowed NSSAIs provided in the Requested NSSAI consists of one or more S-NSSAIs among the allowed NSSAIs for the current PLMN, if a rejected S-NSSAI is added by the configuration update procedure and is not present in the rejected NSSAIs for the current PLMN or the rejected NSSAIs for the combination of the current PLMN and registration area.

[0117] In some embodiments, the method by which UE 102 selects the subset of configured or authorized NSSAIs provided in the Request NSSAI is considered an "implementation." In some embodiments, the number of S-NSSAIs included in the Request NSSAI may not or may not exceed a certain number, such as 20, 10, 8, etc.

[0118] The UE 102 may or shall set the "follow-on request pending" indicator to 1 when it initiates initial registration for emergency services or when it needs to extend the established NAS signaling connection after completion of the initial registration procedure (e.g., by pending uplink signaling).

[0119] If the UE 102 supports the S1 mode, it may or shall do the following:

[0120] In the 5GMM Capabilities IE of the REGISTRATION REQUEST message, the S1 Mode bit shall be set to "S1 Mode Supported".

[0121] Including the S1 UE Network Capabilities IE in the REGISTRATION REQUEST message

[0122] If the UE 102 supports sending an ATTACH REQUEST message containing a PDN CONNECTIVITY REQUEST message with the request type set to "HANDOVER" to transfer a PDU session from N1 mode to S1 mode, then in the 5GMM Capabilities IE of the REGISTRATION REQUEST message, set the H0 Attach bit to "Attach a request message containing a PDN CONNECTIVITY REQUEST message with the request type set to HANDOVER to transfer a PDU session from N1 mode to S1 mode support".

[0123] The UE 102 may or shall include a UPSI LIST TRANSPORT message in the payload container IE of the REGISTRATION REQUEST message if one or more UE policy sections are stored therein.

[0124] Generally, if the initial registration request is accepted by the network, the AMF 108 may or shall send a REGISTRATION ACCEPT message to the UE 102. The AMF 108 may or shall assign and include in the REGISTRATION ACCEPT message a TAI list as the registration area in which the UE 102 is registered. Upon receiving the REGISTRATION ACCEPT message, the UE 102 may or shall clear its old TAI list and store the received TAI list. If the REGISTRATION REQUEST message is received via non-3GPP access, the AMF 108 may or shall include only N3GPP TAIs in the TAI list.

[0125] In some embodiments, a request from the UE 102 (e.g., an initial registration request) may not be accepted by the network. In such a case, the network (e.g., the AMF 108) may send a rejection message (e.g., a registration rejection message) containing an appropriate 5GMM cause value back to the UE 102. If the initial registration request is rejected due to general NAS-level mobility management congestion control, the network may or shall set the 5GMM cause value to #22 "Congestion" and assign a back-off timer T3346. The other two cause values, "Reason #27" and "Reason #72," represent "N1 mode not allowed" and "Non-3GPP access to 5GCN not allowed," respectively.

[0126] In some embodiments, in response to receiving a Request Reject message containing cause value #27 (e.g., "N1 Mode Not Allowed"), the UE 102 may or shall set (and may store in accordance with section 5.1.3.2.2 of 3GPP TS 24.501) the 5GS Update Status to "5U3 ROAMING NOT ALLOWED" and may or shall clear any 5G-GUTI, last visit registration TAI, TAI list, and / or ngKSI. The UE 102 may also reset (and may reset) a registration attempt counter and may or shall enter state "5GMM-DEREGISTERED.LIMITED-SERVICE". In some embodiments, if the message integrity check by the NAS is successful, the UE 102:

[0127] 1) for a PLMN, a PLMN-specific N1 mode attempt counter for 3GPP access and a PLMN-specific N1 mode attempt counter for non-3GPP access of the PLMN, or

[0128] 2) In case of an SNPN, an SNPN-specific attempt counter for 3GPP access of the current SNPN;

[0129] may or shall be set to a UE implementation specific maximum value (also known herein as a "threshold" or "predetermined threshold").

[0130] Thereafter, in some embodiments, the UE 102 may or may not disable N1 mode capability for the particular access type for which the message was received.

[0131] If the message integrity check by the NAS is successful, the UE 102 may or shall disable N1 mode capability for other access types as well.

[0132] If the message is received via 3GPP access and the UE 102 is operating in single registration mode, the UE 102 may or shall set the EPS update status to "EU3 ROAMING NOT ALLOWED" and may or shall clear any 4G-GUTI, last visited registration TAI, TAI list, and / or eKSI. The UE 102 may also reset the attachment attempt counter and may or shall enter state "EMM-DEREGISTERED".

[0133] In some embodiments, in response to receiving (e.g., via non-3GPP access) a request reject message with cause value #72 (e.g., "Non-3GPP access to 5GCN not allowed"), the UE 102 may or shall set (and may store in accordance with section 5.1.3.2.2 of 3GPP TS 24.501) the 5GS update status to "5U3 ROAMING NOT ALLOWED" and may or shall clear the 5G-GUTI, last visit registration TAI, TAI list, and / or ngKSI. The UE 102 may also reset a registration attempt counter and enter state "5GMM-DEREGISTERED". If the message integrity check by the NAS is successful, the UE 102 may or shall set a PLMN-specific N1 mode attempt counter for non-3GPP access of that PLMN to a UE implementation-specific maximum value.

[0134] In some embodiments, the 5GMM sublayer state, 5GMM parameters, and registration status can be managed independently for each access type (eg, 3GPP access or non-3GPP access).

[0135] In some embodiments, the UE 102 may or shall disable N1 mode capability for non-3GPP access.

[0136] As an implementation option, the UE 102 may enter the state "5GMM-DEREGISTERED.PLMN-SEARCH" to perform PLMN selection according to 3GPP TS 23.122.

[0137] In some embodiments, in the case of reception via 3GPP access, the reason may or may be considered an abnormal case, and the behavior of the UE 102 in that case is specified in section 5.5.1.2.7 of 3GPP TS 24.501.

[0138] In some embodiments, the UE 102 may request a network mobility update and / or periodic registration update, for example, by the AMF 108. If such a mobility update or periodic registration update is not permitted by the network, the network or the AMF 108 may respond to the UE 102's request with a rejection message. In some embodiments, the rejection message may be similar to those described above with respect to a rejection message received in response to the UE 102 sending an initial registration request to an incapable / unconfigured or rejected network.

[0139] If such a rejection message is received from the AMF 108 in response to a mobility update and / or periodic registration update request from the UE 102 and includes cause value #27 ("N1 mode not allowed"), the UE 102 may or shall set (and may or shall store in accordance with clause 5.1.3.2.2 of 3GPP TS 24.501) the 5GS update status to "5U3 ROAMING NOT ALLOWED". The UE 102 may or shall reset the registration attempt counter and may or shall enter the state "5GMM-REGISTERED.LIMITED-SERVICE". If the message integrity check by the NAS is successful, the UE 102:

[0140] 1) for a PLMN, a PLMN-specific N1 mode attempt counter for 3GPP access and a PLMN-specific N1 mode attempt counter for non-3GPP access of the PLMN, or

[0141] 2) In case of an SNPN, an SNPN-specific attempt counter for 3GPP access of the current SNPN;

[0142] may or shall be set to a UE implementation specific maximum value.

[0143] In some embodiments, the UE 102 may or may not disable N1 mode capability for the particular access type for which the message was received.

[0144] In some embodiments, if the integrity check of the rejection message by the NAS is successful, the UE 102 may or shall disable N1 mode capability for other access types as well.

[0145] In some embodiments, if the message is received via 3GPP access and the UE 102 is operating in single registration mode, the UE 102 may or shall additionally set the EPS update status to "EU3 ROAMING NOT ALLOWED", and the UE 102 may or shall reset the tracking area update attempt counter and enter the state "EMM-REGISTERED".

[0146] In some embodiments, if a rejection message is received from the AMF 108 in response to a mobility update and / or periodic registration update request from the UE 102 and includes cause value #72 ("Non-3GPP access not allowed to 5GCN"), the UE 102 may change the setting regarding the access type (trusted vs. untrusted, 3GPP access vs. non-3GPP access) for the particular network from which the rejection message was received.

[0147] In some embodiments, if a rejection message is received over non-3GPP access, the UE 102 may or shall set the 5GS update status to "5U3 ROAMING NOT ALLOWED" (and may or shall store it in accordance with section 5.1.3.2.2 of 3GPP TS 24.501) and may or shall clear the 5G-GUTI, last visit registration TAI, TAI list, and / or ngKSI. The UE 102 may also reset a registration attempt counter and enter state "5GMM-DEREGISTERED". If the message integrity check by the NAS is successful, the UE 102 may or shall set a PLMN-specific N1 mode attempt counter for non-3GPP access of that PLMN to a UE implementation-specific maximum value.

[0148] In some embodiments, the 5GMM sublayer state, 5GMM parameters, and registration status can be managed independently for each access type (eg, 3GPP access or non-3GPP access).

[0149] In some embodiments, the UE 102 may or shall disable N1 mode capability for non-3GPP access, and in some embodiments, the UE 102 may or shall disable N1 mode capability for the particular access type for which the reject message was received.

[0150] As an implementation option, the UE 102 may enter the state "5GMM-DEREGISTERED.PLMN-SEARCH" to perform PLMN selection according to 3GPP TS 23.122.

[0151] In the case of reception via 3GPP access, the reason may or shall be considered an abnormal case, and the behavior of the UE 102 in that case is specified in clause 5.5.1.2.7 of 3GPP TS 24.501.

[0152] In some embodiments, a service request from the network, for example by the AMF 108, may be requested by the UE 102. If such a service request or provision of the requested service is not permitted by the network, the network or the AMF 108 may respond to the UE 102's request with a rejection message. In some embodiments, the rejection message may be similar to those described above with respect to a rejection message received in response to the UE 102 sending an initial registration request to an incapable / unconfigured or rejected network.

[0153] In some embodiments, a rejection message received from AMF 108 in response to a request for service provision (e.g., a service request) from UE 102 as described above may include cause value #27 ("N1 mode not allowed").

[0154] In some embodiments, the UE 102 may or shall set the 5GS update status to "5U3 ROAMING NOT ALLOWED" (and may or shall store it in accordance with section 5.1.3.2.2 of 3GPP TS 24.501) and may or shall enter the state "5GMM-REGISTERED.LIMITED-SERVICE". If the message integrity check by the NAS is successful, the UE 102:

[0155] 1) for a PLMN, a PLMN-specific N1 mode attempt counter for 3GPP access and a PLMN-specific N1 mode attempt counter for non-3GPP access of the PLMN, or

[0156] 2) In case of an SNPN, an SNPN-specific attempt counter for 3GPP access of the current SNPN;

[0157] may or shall be set to a UE implementation specific maximum value.

[0158] In some embodiments, the UE 102 may or may not disable N1 mode capability for the particular access type for which the message was received.

[0159] In some embodiments, if the integrity check of the rejection message by the NAS is successful, the UE 102 may or shall disable N1 mode capability for other access types as well.

[0160] In some embodiments, if the message is received via 3GPP access and the UE 102 is operating in single registration mode, the UE 102 may or shall additionally set the EPS update status to "EU3 ROAMING NOT ALLOWED" and enter the state "EMM-REGISTERED".

[0161] In some embodiments, a rejection message received from the AMF 108 in response to a request for service provision (e.g., a service request) from the UE 102 as described above may include cause value #72 ("Non-3GPP access to 5GCN not allowed").

[0162] In some embodiments, if the UE 102 initiates a service request procedure over non-3GPP access, the UE 102 may or shall set the 5GS update status to "5U3 ROAMING NOT ALLOWED" (and may or shall store it in accordance with section 5.1.3.2.2 of 3GPP TS 24.501) and may or shall clear the 5G-GUTI, last visit registration TAI, TAI list, and / or ngKSI for the non-3GPP access. The UE 102 may or shall enter the state "5GMM-DEREGISTERED" for the non-3GPP access. If the message integrity check by the NAS is successful, the UE 102 may or shall set a PLMN-specific N1 mode attempt counter for that PLMN's non-3GPP access to a UE implementation-specific maximum value.

[0163] In some embodiments, the UE 102 may or may not disable N1 mode capability for the particular access type for which the message was received.

[0164] In some embodiments, if the integrity check of the rejection message by the NAS is successful, the UE 102 may or shall disable N1 mode capability for other access types as well.

[0165] As an implementation option, the UE 102 may enter state "5GMM-DEREGISTERED.PLMN-SEARCH" if it is not currently registered via 3GPP access to perform PLMN selection according to 3GPP TS 23.122.

[0166] In some embodiments, in the case of reception via 3GPP access, the reason may or may be considered an abnormal case, and the behavior of the UE 102 in that case is specified in section 5.5.1.2.7 of 3GPP TS 24.501.

[0167] In some embodiments, the purpose of the service request procedure may be to change the 5GMM mode from 5GMM-IDLE to 5GMM-CONNECTED mode and / or to request the establishment of user plane resources for a PDU session that was activated without user plane resources. In the latter case, when the UE 102 requests the activation of user plane resources for a PDU session, the 5GMM mode can be either 5GMM-IDLE or 5GMM-CONNECTED. This procedure:

[0168] If the network has downlink signaling pending on the 3GPP access and the UE 102 is in 5GMM-IDLE mode on the 3GPP access,

[0169] If the network has downlink signaling pending on the non-3GPP access and the UE 102 is in 5GMM-IDLE mode on the non-3GPP access and in 5GMM-IDLE or 5GMM-CONNECTED mode on the 3GPP access,

[0170] If the UE 102 has uplink signaling pending on the 3GPP access and is in 5GMM-IDLE mode on the 3GPP access,

[0171] If the network has downlink user data pending on the 3GPP access and the UE 102 is in 5GMM-IDLE mode on the 3GPP access,

[0172] If the network has downlink user data pending on a non-3GPP access and the UE 102 is in 5GMM-IDLE mode on the non-3GPP access and in 5GMM-IDLE or 5GMM-CONNECTED mode on the 3GPP access,

[0173] If the UE 102 has user data pending on the 3GPP access and is in 5GMM-IDLE or 5GMM-CONNECTED mode on the 3GPP access,

[0174] If the UE 102 has user data pending on a non-3GPP access and is in 5GMM-CONNECTED mode on the non-3GPP access,

[0175] a UE 102 in 5GMM-IDLE mode on a non-3GPP access receives an indication from a lower layer of the non-3GPP access that an access stratum connection has been established between the UE 102 and the network; or

[0176] Used when a UE 102 in 5GMM-IDLE or 5GMM-CONNECTED mode on a 3GPP access receives a request for emergency services from higher layers and performs emergency service fallback as specified in clause 4.13.4.2 of 3GPP TS 23.502.

[0177] In some embodiments, this procedure may not be used, may be used rarely, or may be used occasionally to initiate user data transfer or PDU session-related signaling associated with a PDU session for the LADN when the UE 102 is located outside the LADN service area.

[0178] The service request procedure is initiated by the UE 102, but can also be triggered by the network by:

[0179] Paging procedures (see section 5.6.2) for transfer of downlink signaling or user data reservation on the 3GPP access for a UE 102 in 5GMM-IDLE mode on the 3GPP access

[0180] Paging procedures (see section 5.6.2) for transfer of downlink signaling or user data reservation on non-3GPP accesses for UEs 102 in 5GMM-IDLE mode on 3GPP accesses and 5GMM-IDLE mode on non-3GPP accesses

[0181] Notification procedures for forwarding downlink signaling (see clause 5.6.3) or user data reservation on non-3GPP accesses for UEs 102 in 5GMM-CONNECTED mode on 3GPP accesses and 5GMM-IDLE mode on non-3GPP accesses

[0182] Notification procedures for forwarding downlink signaling (see clause 5.6.3) or user data reservation on 3GPP access for UEs 102 in 5GMM-IDLE mode on 3GPP access and in 5GMM-CONNECTED mode on non-3GPP access

[0183] In some embodiments, in instances where the UE 102 is in 5GMM-IDLE mode on a 3GPP access and 5GMM-CONNECTED mode on a non-3GPP access and transfer of downlink signaling or pending user data on the 3GPP access is required, the AMF 108 can trigger a notification procedure or a paging procedure based on the implementation.

[0184] The UE 102 may or shall invoke the service request procedure when:

[0185] a) When a UE 102 in 5GMM-IDLE mode on a 3GPP access receives a paging request from the network.

[0186] b) When the UE 102 in 5GMM-CONNECTED mode on 3GPP access receives a notification from the network indicating that the access type is non-3GPP access.

[0187] c) When a UE 102 in 5GMM-IDLE mode on a 3GPP access has uplink signaling pending

[0188] d) When a UE 102 in 5GMM-IDLE mode on a 3GPP access has uplink user data pending

[0189] e) When a UE 102 in 5GMM-CONNECTED mode has user data pending because user plane resources have not been established for the PDU session used for user data transport.

[0190] f) A UE 102 in 5GMM-IDLE mode on a non-3GPP access receives an indication from a lower layer of the non-3GPP access that an access stratum connection has been established between the UE 102 and the network.

[0191] g) the UE 102 in 5GMM-IDLE mode on a 3GPP access receives a notification from the network indicating that the access type is 3GPP access when the UE 102 is in 5GMM-CONNECTED mode on a non-3GPP access; or

[0192] h) When a UE 102 in 5GMM-IDLE or 5GMM-CONNECTED mode on a 3GPP access receives a request for emergency services from higher layers and performs emergency service fallback as specified in clause 4.13.4.2 of 3GPP TS 23.502.

[0193] The UE 102 may not or shall not invoke the service request procedure when in the state "5GMM-SERVICE-REQUESTINITIATED".

[0194] In some embodiments, the service request procedure may not be accepted by the network for various reasons. If the service request is not accepted, the network may or shall return a SERVICE REJECT message to the UE 102 containing an appropriate 5GMM cause value and a stop timer T3517.

[0195] If the AMF 108 needs to initiate PDU session status synchronization or if the PDU session status IE was included in the SERVICE REQUEST message, the AMF 108 may or shall include in the SERVICE REJECT message a PDU session status IE indicating which PDU sessions associated with the access type for which the SERVICE REJECT message was sent are active at the AMF 108. If the PDU session status IE is included in the SERVICE REJECT message, the UE 102 may or shall locally (without peer-to-peer signaling between the network and the UE 102) release all PDU sessions associated with the access type for which the SERVICE REJECT message was sent that are active at the UE 102 but indicated as inactive by the AMF 108.

[0196] Upon receipt of the SERVICE REJECT message, if the message is integrity protected, the UE 102 may or shall stop timer T3517 if it is running.

[0197] If a service request for a mobile-originated service is rejected due to general NAS-level mobility management congestion control, the network may or shall set the 5GMM cause value to #22 "Congestion" and assign a value for the back-off timer T3346.

[0198] If the AMF 108 determines that the UE 102 is in a non-authorized area or is not in an authorized area:

[0199] a) If the Service Type IE in the SERVICE REQUEST message is set to "Signaling" or "Data", the AMF 108 may or shall send a SERVICE REJECT message with the 5GMM Cause value set to #28 "Service Area Restriction".

[0200] b) Otherwise, if the Service Type IE in the SERVICE REQUEST message is set to "Mobile Terminated Service", "Emergency Service", "Emergency Service Fallback", or "High Priority Access", the AMF 108 may or shall continue the process unless the service request is not accepted for other reasons.

[0201] The UE 102 may or shall take the following actions depending on the 5GMM cause value received in the SERVICE REJECT message:

[0202] #3(Illegal UE)

[0203] #6 (Illegal ME), or

[0204] #7 (5GS Service Not Allowed): In such an example, the UE 102 may or shall set the 5GS Update Status to "5U3 ROAMING NOT ALLOWED" (and may or shall store it in accordance with section 5.1.3.2.2 of 3GPP TS 24.501) and may or shall erase any 5G-GUTI, Last Visit Registration TAI, TAI List, and ngKSI. The UE 102 may or shall consider the USIM invalid for 5GS service until it is switched off or the UICC containing the USIM is removed.

[0205] The UE 102 may or shall enter the state "5GMM-DEREGISTERED".

[0206] If the UE 102 supports S1 mode, it may or shall process the EMM parameters, EMM state, GUTI, last visit registration TAI, TAI list, and eKSI as specified in 3GPP TS 24.301 for the case where a service request procedure is rejected with an EMM reason of the same value. The USIM may or shall be considered invalid even for non-EPS services until it is switched off or the UICC containing the USIM is removed.

[0207] #9 (UE identity cannot be derived by the network)

[0208] The UE 102 may or shall set the 5GS update status to "5U2 NOT UPDATED" (and may or shall store it in accordance with section 5.1.3.2.2) and may or shall clear any 5G-GUTI, last visit registration TAI, TAI list, and ngKSI. The UE 102 may or shall enter state "5GMM-DEREGISTERED".

[0209] If a service request is initiated for emergency service fallback, the UE 102 may, or shall, attempt to select an E-UTRA cell connected to the EPC or 5GCN according to the emergency service support indicator. If the UE 102 finds a suitable E-UTRA cell, it proceeds with the appropriate EMM or 5GMM procedure.

[0210] If a service request is initiated for reasons other than emergency service fallback or initiation of an emergency service PDU session, the UE 102 may or shall perform a new initial registration procedure.

[0211] In some embodiments, if the UE 102 is unable to automatically reactivate the PDU session, intervention by the user of the UE 102 may be required.

[0212] When the UE 102 is operating in single registration mode, it may or shall process the EMM parameters, EMM state, GUTI, last visit registration TAI, TAI list, and eKSI as specified in 3GPP TS 24.301 for the case where a service request procedure is rejected with an EMM reason of the same value.

[0213] #10 (Implicit unregistration)

[0214] The UE 102 may or shall enter the state "5GMM-DEREGISTERED.NORMAL-SERVICE". The UE 102 may or shall clear the mapped 5G NAS security context or some native 5G NAS security context.

[0215] If the rejected request is not for the initiation of an emergency services PDU session, the UE 102 may or shall perform a new initial registration procedure.

[0216] If the UE 102 supports S1 mode, it may or shall handle the EMM condition as specified in 3GPP TS 24.301 for the case where a service request procedure is rejected with an EMM reason of the same value.

[0217] #22 (Congestion)

[0218] If the T3346 value IE is present in the SERVICE REJECT message and indicates that this timer is neither zero nor inactive, the UE 102 may or shall proceed as described below, otherwise it may or shall consider this an abnormal case. The behavior of the UE 102 in this case is specified in clause 5.6.1.6 of 3GPP TS 24.501.

[0219] If the rejected request is not for the initiation of an emergency services PDU session, the UE 102 aborts the service request procedure and enters state "5GMM-REGISTERED" and may or shall stop timer T3517 if it is still running.

[0220] The UE 102 may or shall stop timer T3346 if it is running.

[0221] If the SERVICE REJECT message is integrity protected, the UE 102 may or shall start timer T3346 with the value given in the T3346 Value IE.

[0222] If the SERVICE REJECT message is not integrity protected, the UE 102 may or shall start timer T3346 with a random value from the default range specified in 3GPP TS 24.008.

[0223] In all other cases, the UE 102 remains in the current serving cell and the normal cell reselection process applies. When timer T3346 expires or stops, a service request procedure is initiated, if still required.

[0224] #27 (N1 mode not allowed)

[0225] An S1 mode capable UE may or shall disable N1 mode capability for both 3GPP and non-3GPP accesses (see section 4.9).

[0226] #28 (Service area restrictions)

[0227] The UE 102 may or shall perform registration procedures for mobility and periodic registration updates (see section 5.5.1.3).

[0228] In some embodiments, N1 mode capability may represent the ability of the UE 102 to access a network. If N1 mode capability is disabled for a particular network (e.g., a 5G system (5GS)), the UE 102 generally cannot access 5GS. If N1 mode capability is enabled and 5GS is available, the UE 102 generally can access 5GS. N1 mode capability is also access-specific. For example, currently, there are two types of N1 mode capability: N1 mode capability for 3GPP access and N1 mode capability for non-3GPP access. For example, if N1 mode capability for non-3GPP access is disabled and N1 mode capability for 3GPP access is enabled, the UE 102 can access 5GS only via 3GPP access.

[0229] If the 5GS sends 5GMM cause value #27 "N1 mode not allowed" or #72 "Non-3GPP access to 5GCN not allowed", the N1 mode capability of the UE 102 is affected. For example, in a service request procedure, if the UE 102 service request is rejected with 5GMM cause value #27 "N1 mode not allowed" or #72 "Non-3GPP access to 5GCN not allowed", the UE 102 behaves as follows (see 3GPP TS 24.501):

[0230] #27 (N1 mode not allowed)

[0231] The UE 102 may or shall set the 5GS update status to "5U3 ROAMING NOT ALLOWED" (and may or shall store it according to clause 5.1.3.2.2) and may or shall enter the state "5GMM-REGISTERED.LIMITED-SERVICE". If the message integrity check by the NAS is successful, the UE 102:

[0232] For a PLMN, a PLMN-specific N1 mode attempt counter for 3GPP access and a PLMN-specific N1 mode attempt counter for non-3GPP access of the PLMN; or

[0233] For an SNPN, an SNPN-specific attempt counter for 3GPP access of the current SNPN;

[0234] may or shall be set to a UE implementation specific maximum value.

[0235] If the message integrity check by the NAS is successful, the UE 102 may or shall disable N1 mode capability for both 3GPP and non-3GPP access (see section 4.9).

[0236] If the message is received via 3GPP access and the UE 102 is operating in single registration mode, the UE 102 may or shall additionally set the EPS update status to "EU3 ROAMING NOT ALLOWED" and enter the state "EMM-REGISTERED".

[0237] #72 (Non-3GPP access to 5GCN not permitted)

[0238] If the UE 102 initiates a service request procedure over non-3GPP access, it may or shall set the 5GS update status to "5U3 ROAMING NOT ALLOWED" (and may or shall store it in accordance with 3GPP TS 24.501, clause 5.1.3.2.2) and may or shall clear the 5G-GUTI, last visit registration TAI, TAI list, and ngKSI for non-3GPP access. The UE 102 may or shall enter state "5GMM-DEREGISTERED" for non-3GPP access. If the message integrity check by the NAS is successful, the UE 102 may or shall set a PLMN-specific N1 mode attempt counter for non-3GPP access of that PLMN to a UE implementation-specific maximum value.

[0239] In some embodiments, the 5GMM sublayer state, 5GMM parameters, and registration status are managed independently for each access type (e.g., 3GPP access or non-3GPP access). In some embodiments, the UE 102 may or shall disable N1 mode capability for non-3GPP access. In some embodiments, the UE 102 may or shall disable a particular network's N1 mode capability for non-3GPP access in response to receiving a rejection message from the particular network indicating that N1 mode is not allowed or that the UE 102 can only access the network via 3GPP (trusted) access.

[0240] As an implementation option, the UE 102 may enter state "5GMM-DEREGISTERED.PLMN-SEARCH" if it is not currently registered via 3GPP access to perform PLMN selection according to 3GPP TS 23.122.

[0241] In the case of reception via 3GPP access, the reason may or shall be considered an abnormal case, and the behavior of the UE 102 in that case is specified in clause 5.5.1.2.7 of 3GPP TS 24.501.

[0242] In some embodiments, the UE 102 shall store the identities of PLMNs for which N1 mode capability has been disabled for 3GPP access and shall use the stored information in subsequent PLMN selection. More specifically, according to 3GPP TS 23.122, the UE 102 shall maintain a list of PLMNs for which N1 mode capability has been disabled due to receipt of a rejection from the network with 5GMM cause #27 "N1 mode not allowed." If the UE 102 disables N1 mode capability due to receipt of a rejection from the network with 5GMM cause #27 "N1 mode not allowed,"

[0243] The UE 102 shall add the identity of the PLMN to the list of PLMNs for which N1 mode is not allowed and start timer TG if it is not already running. The number of PLMNs for which N1 mode is not allowed that the MS can store is implementation specific but may or shall be at least one. In some embodiments, the value of timer TG is MS implementation specific but may not, cannot, or shall not exceed the maximum possible value of a background scanning timer, T.

[0244] During automatic PLMN selection, the MS may not, cannot or shall not consider PLMNs for which N1 mode is not allowed as PLMN selection candidates for the NG-RAN access technology, unless no other PLMNs are available. If such PLMNs are available in another RAT, this does not prevent PLMN selection.

[0245] The MS may or shall erase stored information on PLMNs where N1 mode is not allowed when switched off, when the USIM is removed or when the timer TG expires.

[0246] According to conventional techniques and protocols, the UE 102 may disable N1 mode capability for all networks if it receives a 5GMM cause value of #27 from an SNPN. This is problematic because the UE 102 may have multiple sets of subscriber data for multiple SNPNs, and if one SNPN sends a 5GMM cause value of #27, the UE 102 may be unable to access other SNPNs because it has disabled its N1 mode capability.

[0247] To this end, the embodiments described herein provide methods, systems, devices, and computer program products for managing the network capabilities of a UE 102 with respect to a private network (e.g., SNPN) selection process following receipt of a rejection message including a 5GMM cause value (e.g., #27 or #72, etc.), for example, in response to an initial registration request, a mobility update request, a term registration update request, a service request, etc.

[0248] According to some embodiments, the UE 102 may manage the disabling and re-enabling of N1 mode to the network using entries in the "List of Subscriber Data." In some embodiments, the UE 102 may maintain a list of entries for which N1 mode capability for 3GPP access is disabled. In some embodiments, an entry in the "List of Subscriber Data" may have an "Entry Index" parameter. In some embodiments, in PLMN access mode, the UE 102 may maintain a list of PLMNs (e.g., PLMN IDs).

[0249] In some embodiments, the UE 102 may maintain one SNPN-specific N1 mode attempt counter for 3GPP access for each entry in the "list of subscriber data." The maximum possible number of entries in the list is implementation dependent. This list is applicable only to access attempts via 3GPP access (and one SNPN-specific N1 mode attempt counter for non-3GPP access). In some embodiments, the maximum possible number of entries in the list may be implementation dependent. In some embodiments, the network can be accessed by reference to, implementation of, or use of the list when requesting registration or mobility updates, when requesting services (e.g., when requesting SNPN services via PLMNs only), etc.

[0250] In some embodiments (eg, for a PLMN), the UE 102 may maintain one list of PLMN-specific N1 mode attempt counters for 3GPP access and one list of PLMN-specific N1 mode attempt counters for non-3GPP access.

[0251] In some embodiments, if the UE 102 receives a rejection message containing a non-integrity protected 5GMM cause value #27 (or #72), it disables N1 mode capability for the entry (for each access type (or non-3GPP access)) and initiates T3247. Also, if the value of an SNPN-specific N1 mode attempt counter for each access type (or non-3GPP access) and the current SNPN is less than a UE implementation-specific maximum value, the UE 102 may or shall increment this counter for that entry.

[0252] When timer T3247 expires, the UE 102 re-enables N1 mode capability for 3GPP access / non-3GPP access for that entry and removes from the list of entries each entry index for which N1 mode is not allowed for 3GPP access / non-3GPP access if the value of the SNPN-specific N1 mode attempt counter for 3GPP access is greater than zero and less than a UE implementation-specific maximum value.

[0253] In some embodiments, a "list of subscriber data" containing zero or more entries is configured in the ME in the UE 102. Each entry in the "list of subscriber data" consists of:

[0254] a) Entry Index

[0255] b) Other parameters available in TS 23.122 (e.g. subscriber ID, authentication information, SNPN identification information)

[0256] In some embodiments, the "list of subscriber data" is information configured in the ME of the UE 102 that contains zero or more entries. Each entry in the "list of subscriber data" consists of the following (the following list is in accordance with the current version of TS 23.122 and is subject to change):

[0257] a) (Optional) Subscriber Identifier

[0258] b) (Optional) Credentials

[0259] c)SNPN identification information

[0260] d) (Optional) Unified Access Control Settings

[0261] The UE 102 shall maintain a list of entries for which N1 mode capability has been disabled due to receipt of a rejection from the network with 5GMM cause #27 "N1 mode not allowed". If the UE 102 has disabled N1 mode capability for an entry due to receipt of a rejection from the network with 5GMM cause #27 "N1 mode not allowed", then:

[0262] The UE 102 shall add to the list of entries for which N1 mode is disabled the index of the entry used to access the SNPN that sent the rejection with 5GMM reason #27 "N1 mode not allowed" (or add to the list of SNPNs for which N1 mode is disabled the SNPN identity of the SNPN that sent the rejection with 5GMM reason #27 "N1 mode not allowed") and start timer TG if it is not already running. The number of entries (or SNPNs) for which N1 mode is not allowed that the MS can store is implementation specific, but may be or shall be at least one. The value of timer TG is UE implementation specific,

[0263] In automatic SNPN selection, the UE 102 cannot or shall not use an entry (or SNPN) for which N1 mode is not allowed as an SNPN selection candidate for the NG-RAN access technology unless no other SNPN is available.

[0264] The UE 102 may or shall erase stored information on entries (or SNPNs) for which N1 mode is not allowed when it is switched off, when the USIM is removed, or when the timer TG expires.

[0265] When the UE 102 is operating in SNPN access mode, it may or shall maintain, for each entry in the List of Subscriber Data:

[0266] One SNPN-specific N1 mode attempt counter for 3GPP access (the maximum possible number of entries in the list is implementation-dependent. This list is only applicable to access attempts via 3GPP access)

[0267] One SNPN-specific N1 mode attempt counter for non-3GPP access (the maximum possible number of entries in the list is implementation-dependent. This list is only applicable when accessing SNPN services via a PLMN)

[0268] If UE 102 receives a REGISTRATION REJECT or SERVICE REJECT message that is not integrity protected with 5GMM cause value #27 or #72 before the network has established a secure exchange of NAS messages for the N1 NAS signaling connection, UE 102 shall stop timer T3510 or T3517 if it is running, or start timer T3247 with a random value drawn uniformly from the range 30 to 60 minutes if it is not running, and may or shall take the following actions:

[0269] a) If the received 5GMM cause value is #27, the UE 102 may or shall proceed as specified in clauses 5.5.1 and 5.6.1 of 3GPP TS 24.501, and if the value of the SNPN-specific N1 mode attempt counter for each access type and current SNPN is less than a UE implementation-specific maximum value, the UE 102 may or shall increment this counter for that entry (or that SNPN).

[0270] b) If the received 5GMM cause value is #72, the UE 102 may or shall proceed as specified in clauses 5.5.1 and 5.6.1 of 3GPP TS 24.501, and if the value of the SNPN-specific N1 mode attempt counter for the non-3GPP access and current SNPN is less than a UE implementation-specific maximum value, the UE 102 may or shall increment this counter for that entry (or that SNPN).

[0271] When timer T3247 expires, the UE 102:

[0272] If N1 mode capability for 3GPP access is re-enabled for that entry and the value of the SNPN-specific N1 mode attempt counter for 3GPP access is greater than zero and less than a UE implementation-specific maximum, then each entry index for which N1 mode is not allowed for 3GPP access may or shall be removed from the list of entries (or SNPN identities for which N1 mode is not allowed for 3GPP access may or shall be removed from the list of SNPNs).

[0273] Also, if N1 mode capability for non-3GPP access is re-enabled and the value of the SNPN-specific N1 mode attempt counter for non-3GPP access is greater than zero and less than a UE implementation-specific maximum, then each entry index for which N1 mode is not allowed for non-3GPP access may or shall be removed from the list of entries (or SNPN identities for which N1 mode is not allowed for non-3GPP access may or shall be removed from the list of SNPNs).

[0274] In some embodiments, registration on the selected SNPN and LR is only necessary if only services requiring registration are available on the MS; otherwise, the SNPN selection procedure is performed without registration.

[0275] The ME is configured with a "list of subscriber data" which contains zero or more entries. Each entry in the "list of subscriber data" consists of:

[0276] aa) Entry index

[0277] a) a subscriber identifier in the form of a SUPI containing a network unique identifier;

[0278] b) Credentials (excluding use of SNPN)

[0279] 1) EAP-based primary authentication and key exchange procedure using EAP-AKA

[0280] 2) 5G AKA-based primary authentication and key exchange procedure

[0281] In some embodiments, authentication information for an EAP-based primary authentication and key exchange procedure using EAP-AKA' and a 5G AKA-based primary authentication and key exchange procedure is available in the USIM.

[0282] c)SNPN identification information

[0283] d) (Optional) Integrated Access Control Configuration indicating the access identity (see 3GPP TS 24.501) configured by the ME in the SNPN.

[0284] In some embodiments, multiple entries may contain the same subscriber identifier and authentication information. In some embodiments, the handling of two or more entries with the same SNPN identification information may depend on the MS implementation.

[0285] The MS may or shall maintain in the ME a list of "temporarily banned SNPNs" and a list of "permanently banned SNPNs". Each entry in these lists consists of an SNPN identity.

[0286] If a message containing cause value 74 "Temporary disapproval for this SNPN" (see 3GPP TS 24.501) is received by the MS in response to an LR request from an SNPN, the MS may or shall add the SNPN to its list of "Temporarily Forbidden SNPNs" and start an MS implementation-specific timer of at least 60 minutes.

[0287] This message is integrity protected.

[0288] Alternatively, the message is not integrity protected and the value of the SNPN-specific attempt counter for that SNPN is equal to an MS implementation-specific maximum value as specified in 3GPP TS 24.501.

[0289] An MS may or shall remove an SNPN from the list of "Temporarily Prohibited SNPNs" if:

[0290] a) Successful LR after subsequent manual selection of SNPN

[0291] b) When an MS implementation-specific timer of 60 minutes or more expires.

[0292] c) The MS is switched off, or

[0293] d) When an entry in the "List of subscriber data" with the SNPN identification information of an SNPN is updated or when a USIM is removed,

[0294] EAP-based primary authentication and key exchange procedure using EAP-AKA, or

[0295] 5G AKA-based primary authentication and key exchange procedure

[0296] When executed in the selected SNPN

[0297] The MS may or shall add an SNPN to the list of "permanently banned SNPNs" if a message containing cause value 75 "Permanent disapproval of this SNPN" (see 3GPP TS 24.501) is received by the MS in response to an LR request from the SNPN.

[0298] This message is integrity protected.

[0299] Alternatively, the message is not integrity protected and the value of the SNPN-specific attempt counter for that SNPN is equal to an MS implementation-specific maximum value as specified in 3GPP TS 24.501.

[0300] An MS may or shall remove an SNPN from the list of "permanently banned SNPNs" if:

[0301] a) Successful LR after subsequent manual selection of SNPN

[0302] b) When an entry in the "List of subscriber data" with the SNPN identification information of an SNPN is updated or when a USIM is removed,

[0303] EAP-based primary authentication and key exchange procedure using EAP-AKA, or

[0304] 5G AKA-based primary authentication and key exchange procedure

[0305] When executed in the selected SNPN

[0306] If the MS reselects a cell in a shared network and this cell is a suitable cell for multiple SNPN identities received in broadcast information as specified in 3GPP TS 36.331 and 3GPP TS 38.331, the AS 112 (or AS / AF 112) specifies these multiple SNPN identities to the NAS in accordance with 3GPP TS 36.304 and 3GPP TS 38.304. The MS may or shall select one of these SNPNs. If a registration SNPN is available among these SNPNs, the MS may not or shall not select a different SNPN. In some embodiments, the preferred cell among the SNPNs must be specified by RAN2. In some embodiments, an MS operating in SNPN access mode may or shall maintain one or more lists of "5GS Forbidden Tracking Areas for Roaming," each associated with an SNPN. The MS may or shall use the list of "5GS Forbidden Tracking Areas for Roaming" associated with the selected SNPN. When an MS selects a new SNPN, it may or shall maintain a list of "5GS Forbidden Tracking Areas for Roaming" associated with the previously selected SNPN. If the number of lists to maintain exceeds the support, the MS may or shall delete the oldest stored list of "5GS Forbidden Tracking Areas for Roaming". The MS may or shall delete all lists of "5GS Forbidden Tracking Areas for Roaming" when it is periodically switched off (with a period ranging from 12 to 24 hours). The MS may or shall delete the list of "5GS Forbidden Tracking Areas for Roaming" associated with an SNPN when: the SNPN's entry in the "List of Subscriber Data" is updated or the USIM is removed.

[0307] EAP-based primary authentication and key exchange procedure using EAP-AKA, or

[0308] 5G AKA-based primary authentication and key exchange procedure

[0309] When executed in the selected SNPN

[0310] In some embodiments, the number of lists of "5GS Prohibited Tracking Areas for Roaming" that an MS supports is MS implementation specific.

[0311] If a message with cause value #15 (see 3GPP TS 24.501) is received by an MS operating in SNPN access mode, the TA is added to the list of "5GS Forbidden Tracking Areas for Roaming" of the selected SNPN. The MS may or shall then search for a suitable cell belonging to the same SNPN but a TA that is not in the list of "5GS Forbidden Tracking Areas for Roaming" of the selected SNPN.

[0312] The MS shall maintain a list of entries for which N1 mode capability has been disabled due to receipt of a rejection from the network with 5GMM cause #27 "N1 mode not allowed". If the MS has disabled N1 mode capability for an entry due to receipt of a rejection from the network with 5GMM cause #27 "N1 mode not allowed", then:

[0313] The MS shall add to the list of entries the index of the entry used to access the SNPN that sent the rejection with 5GMM reason #27 "N1 mode not allowed" and shall start timer TG if it is not already running. The number of entries for which N1 mode is not allowed that the MS can store is implementation specific but may or shall be at least one. The value of timer TG is MS implementation specific.

[0314] In automatic SNPN selection, the MS cannot or shall not use an entry that does not allow N1 mode as an SNPN selection candidate for the NG-RAN access technology unless no other SNPN is available.

[0315] The MS may or shall erase stored information on entries for which N1 mode is not allowed when switched off, when the USIM is removed or when timer TG expires.

[0316] In some embodiments, for a UE 102 to disable and / or re-enable N1 mode capability for 3GPP access, the UE 102 may or shall disable N1 mode capability for 3GPP access only when in 5GMM-IDLE mode.

[0317] If the UE 102 has disabled N1 mode capability for 3GPP access, it shall proceed as follows.

[0318] a) If the UE 102 supports S1 mode and the UE 102 has not disabled E-UTRA capability as specified in 3GPP TS 24.301, select an E-UTRA cell connected to the EPC of the registered PLMN or a PLMN in the equivalent PLMN list.

[0319] b) If an E-UTRA cell connected to the EPC of the registered PLMN or a PLMN in the equivalent PLMN list is not found, if the UE 102 does not support S1 mode, or if the UE 102 has disabled E-UTRA capability as specified in 3GPP TS 24.301, the UE 102 may select another RAT of the registered PLMN or a PLMN in the equivalent PLMN list that it supports.

[0320] c) In the case of a PLMN, if the UE 102 cannot find another RAT for the registered PLMN or a PLMN in the equivalent PLMN list, or if the UE 102 does not have a registered PLMN, it enters state "5GMM-DEREGISTERED.PLMN-SEARCH" and performs PLMN selection as specified in 3GPP TS 23.122. If the N1 mode capability for the 3GPP access was not disabled by a switch-off or a UE-initiated deregistration procedure for 5GS services over the 3GPP access, the UE 102 may re-enable N1 capability for this PLMN selection. As an implementation option, if the UE 102 does not have a registered PLMN, instead of performing PLMN selection, the UE 102 may select another RAT for the selected PLMN if it has selected a PLMN and supports the RAT.

[0321] In the case of an SNPN, the state "5GMM-DEREGISTERED.PLMN-SEARCH" is entered to perform the SNPN selection as specified in 3GPP TS 23.122. If the deactivation of N1 mode capability for the 3GPP access was not due to a switch-off or a UE initiated deregistration procedure for 5GS services over the 3GPP access, the UE 102 may re-enable the N1 capability of a previously used entry in the "list of subscriber data" for this SNPN selection, or

[0322] d) If the other allowed PLMN and RAT combination is unavailable or if the other SNPN is unavailable, the UE 102 may re-enable N1 mode capability for 3GPP access, instruct lower layers to remain in the NG-RAN of the registered PLMN or SNPN, and (if the UE 102 supports EPS or non-EPS services) periodically scan for other PLMN and RAT combinations that may provide EPS or non-EPS services. How this periodic scanning is performed is up to the implementation of the UE 102.

[0323] If the UE 102 has disabled N1 mode capability upon receipt of rejection cause #31 "Redirection to EPC required" as specified in sections 5.5.1.2.5 and 5.5.1.3.5, the UE 102 shall proceed as follows:

[0324] a) If the UE 102 is in NB-N1 mode,

[0325] 1) If the lower layers do not provide an indication that the current E-UTRA cell is connected to the EPC or that the current E-UTRA cell supports the CIoT EPS optimizations that the UE 102 supports, search for a suitable NB-IoT cell connected to the EPC according to 3GPP TS 36.304.

[0326] 2) If lower layers provide an indication that the current E-UTRA cell is connected to an EPC and that the current E-UTRA cell supports CIoT EPS optimizations that the UE 102 supports, select the EPC by performing a core network selection as specified in section 4.8.4A.1; or

[0327] 3) If the lower layers are unable to find a suitable NB-IoT cell connected to the EPC or there is no suitable NB-IoT cell connected to the EPC that supports CIoT EPS optimization supported by the UE 102, the UE 102 may re-enable N1 mode capability for 3GPP access and instruct the lower layers to remain on E-UTRA connected to the 5GCN of the previously registered PLMN and proceed with the appropriate 5GMM procedures.

[0328] b) When the UE 102 is in WB-N1 mode,

[0329] 1) If the lower layers do not provide an indication that the current E-UTRA cell is connected to the EPC or that the current E-UTRA cell supports the CIoT EPS optimization that the UE 102 supports, search for a suitable E-UTRA cell connected to the EPC according to 3GPP TS 36.304.

[0330] 2) If lower layers provide an indication that the current E-UTRA cell is connected to an EPC and that the current E-UTRA cell supports CIoT EPS optimizations that the UE (102) supports, select the EPC by performing a core network selection as specified in clause 4.8.4A.1.

[0331] 3) If the lower layers are unable to find a suitable E-UTRA cell connected to the EPC or there is no suitable E-UTRA cell connected to the EPC that supports CIoT EPS optimization supported by the UE 102, the UE 102 may re-enable N1 mode capability for 3GPP access, instruct the lower layers to remain on the E-UTRA connected 5GCN of the previously registered PLMN, and proceed with the appropriate 5GMM procedures.

[0332] If a UE 102 that supports both N1 mode and S1 mode needs to remain in an E-UTRA connected to an EPC (e.g., due to domain selection of a UE 102-originated session as specified in section 4.3.2), the UE 102 operating in single registration mode may or shall disable N1 mode capability for 3GPP access to prevent unintended handover or cell reselection from an E-UTRA connected to an EPC to an NG-RAN connected to a 5GCN;

[0333] a) In the UE 102 Network Capability IE (see 3GPP TS 24.301) of the ATTACH REQUEST and TRACKING AREA UPDATE REQUEST messages of the EPC, the N1mode bit may or shall be set to "N1 mode not supported".

[0334] b) The UE NAS layer may or shall instruct the access stratum layer to disable N1 mode capability for 3GPP access.

[0335] If the UE 102 needs to disable N1 mode capability for 3GPP access and select E-UTRA or another RAT, and the UE 102 is in 5GMM-CONNECTED mode,

[0336] If the UE 102 has a persistent PDU session, the UE 102 waits until the radio bearer associated with the persistent PDU session is released.

[0337] Alternatively, the UE 102 may or shall locally release the established NAS signaling connection.

[0338] Also, 5GMM-IDLE mode is entered prior to selection of E-UTRA or another RAT.

[0339] If the UE 102 has disabled N1 mode capability for 3GPP access prior to selecting E-UTRA or another RAT, the UE 102 may not, cannot, or shall not perform the UE-initiated deregistration procedure of section 5.5.2.2.

[0340] The UE 102 may or shall re-enable N1 mode capability for the 3GPP access when performing PLMN or SNPN selection over the 3GPP access, except in the following cases:

[0341] The deactivation of the N1 mode capability for the 3GPP access was not due to a switch-off but due to a UE-initiated deregistration procedure for 5GS services on the 3GPP access, or

[0342] If the UE 102 has re-enabled E-UTRA capability when performing item c) or d) above.

[0343] If the disabling of N1 mode capability for 3GPP access was due to IMS voice not being available over the 3GPP access and the UE usage configuration being "voice-centric", the UE 102 may or shall re-enable N1 mode capability for 3GPP access if the UE usage configuration is changed from "voice-centric" to "data-centric" as specified in section 4.3.3.

[0344] The UE 102 shall remember, record, store, etc., the identity of the PLMN or the index of the entry in the "List of Subscriber Data" used to access the SNPN for which N1 mode capability for 3GPP access has been disabled, and shall use the stored information in subsequent PLMN or SNPN selection as specified in 3GPP TS 23.122.

[0345] If the disabling of N1 mode capability for 3GPP access was due to successful completion of emergency services fallback, the criteria for re-enabling N1 mode capability is again UE 102 implementation specific.

[0346] As an implementation option, the UE 102 may start a timer to enable N1 mode capability for 3GPP access when the UE's registration attempt counter reaches 5, and disable N1 mode capability for 3GPP access for the cases described in clauses 5.5.1.2.7 and 5.5.1.3.7. The UE 102 shall record, remember, or store the identity of the PLMN for which N1 mode capability for 3GPP access has been disabled. When this timer expires:

[0347] The UE 102 shall enable N1 mode capability for 3GPP access if in Iu mode or A / Gb mode and in idle mode as specified in 3GPP TS 24.008 upon expiration of the timer.

[0348] If the UE 102 is in Iu mode or A / Gb mode and an RR connection exists, the UE 102 may or shall delay enabling N1 mode capability for 3GPP access until the RR connection is released.

[0349] If the UE 102 is in Iu mode and a PS signaling connection exists but an RR connection does not exist, the UE 102 may discontinue the PS signaling connection prior to enabling N1 mode capability for 3GPP access.

[0350] The UE 102 shall enable N1 mode capability for 3GPP access if it is in S1 mode and in EMM-IDLE mode as specified in 3GPP TS 24.301 upon expiration of the timer.

[0351] If the UE 102 is in S1 mode and in EMM-CONNECTED mode as specified in 3GPP TS 24.301 upon expiration of the timer, the UE 102 may or shall delay enabling N1 mode capabilities for 3GPP access until the NAS signaling connection in S1 mode is released.

[0352] If the UE 102 attempts to establish an emergency PDU session in a PLMN for which N1 mode capability has been disabled because the UE's registration attempt counter has reached 5, the UE 102 may enable the N1 mode capability stored by the UE 102 for that PLMN.

[0353] In some embodiments, if N1 mode capability is disabled because the UE's registration attempt counter has reached 5, it is recommended that the value of the timer for re-enabling N1 mode capability be the same as the value of T3502 following the procedure specified in clause 5.3.8.

[0354] In the case of SNPN, for example, if the UE 102 is not SNPN-capable, the UE 102 is always considered not to be operating in SNPN access mode. If the UE 102 is SNPN-capable, the UE 102 may operate in SNPN access mode. The details of activating and deactivating the SNPN access mode in an SNPN-capable UE 102 are up to the implementation of the UE 102.

[0355] The NAS functions and procedures described in this patent specification are applicable, unless otherwise specified, to SNPN and SNPN-enabled UEs 102. The main differences that SNPN brings to the NAS layer are as follows:

[0356] a) Instead of a PLMN selection process, an SNPN selection process is performed by the UE 102 operating in SNPN access mode (see 3GPP TS 23.122 for additional details regarding SNPN selection).

[0357] b) Instead of a forbidden PLMN list, a "permanently forbidden SNPN" list and a "temporarily forbidden SNPN" list are managed by the UE 102 operating in SNPN access mode.

[0358] c) Inter-system switching for S1 mode is not supported.

[0359] d) Emergency services are not supported in SNPN access mode.

[0360] e) CAG is not supported in SNPN access mode.

[0361] f) Regarding 5GMM reason values,

[0362] 1) While 5GMM cause values ​​#74 "Temporary disapproval of this SNPN" and #75 "Permanent disapproval of this SNPN" are supported, these 5GMM cause values ​​cannot be used in the PLMN.

[0363] 2) While 5GMM cause values ​​#11 "PLMN Not Admitted" and #73 "Serving Network Not Admitted" are not supported, these 5GMM cause values ​​can be used in PLMNs.

[0364] 3) While 5GMM cause value #76 "Not admitted to this CAG or admitted to CAG cells only" is not supported, this 5GMM cause value can be used in PLMNs.

[0365] In some embodiments, 5GMM cause values ​​#31 "Redirection to EPC required" and #72 "Non-3GPP access to 5GCN not allowed" are supported in the SNPN.

[0366] g) A list of "5GS Forbidden Tracking Areas for Roaming" and a list of "5GS Forbidden Tracking Areas for Regional Service Provision" are managed per SNPN (see 3GPP TS 23.122).

[0367] h) When accessing an SNPN service via a PLMN, access to the 5GCN of the SNPN is performed using 5GMM procedures and 5GMM parameters for non-3GPP access. When accessing a PLMN service via an SNPN, access to the 5GCN of the PLMN is performed using 5GMM procedures and 5GMM parameters for non-3GPP access.

[0368] i) When registered with an SNPN, the UE 102 may or shall only use UE 102 policies provided by the registered SNPN.

[0369] j) Equivalent SNPN is not supported.

[0370] x) N1 mode capability for an access type is disabled and re-enabled for each entry in the "List of Subscriber Data".

[0371] Additionally, there may be specific requirements for the UE 102 to access, register with, and / or receive services from an SNPN. In some embodiments, when operating in SNPN access mode, the UE 102 may or shall maintain, for each entry in the "List of Subscriber Data," the following:

[0372] One SNPN-specific attempt counter for 3GPP access (this counter is only applicable to access attempts via 3GPP access)

[0373] One SNPN-specific attempt counter for non-3GPP access (this counter is only applicable when accessing SNPN services via a PLMN)

[0374] One SNPN-specific N1 mode attempt counter for 3GPP access (the maximum possible number of entries in the list is implementation-dependent. This list is only applicable to access attempts via 3GPP access)

[0375] One SNPN-specific N1 mode attempt counter for non-3GPP access (the maximum possible number of entries in the list is implementation-dependent. This list is only applicable when accessing SNPN services via a PLMN)

[0376] One counter for the event "Current SNPN entry considered invalid for 3GPP access"

[0377] One counter for the event "Current SNPN entry considered invalid for non-3GPP access" (this counter is only applicable when accessing SNPN services via a PLMN)

[0378] In some embodiments, the term "non-3GPP access" may be used in the counter for the "current SNPN entry considered invalid for 3GPP access" event and the counter for the "current SNPN entry considered invalid for non-3GPP access" event, and can be used to refer to access to SNPN services via a PLMN.

[0379] The UE 102 may or shall store the counters in non-volatile memory. The UE 102 may or shall clear the attempt counter and reset the event counter to zero when an entry in the "List of Subscriber Data" with the corresponding SNPN identity is updated. The counter values ​​may not, cannot, or shall not be affected by the activation or deactivation of MICO mode or power saving mode (see 3GPP TS 24.301).

[0380] The UE 102 implementation-specific maximum value for any of the above counters may not, cannot, or shall not be greater than or equal to 1, 2, 3, 4, 5, 6, 7, 8, 9, 10. In some embodiments, the UE 102 implementation-specific maximum values ​​used by different counters may be different.

[0381] If the UE 102 receives a REGISTRATION REJECT or SERVICE REJECT message that is not integrity protected with 5GMM cause value #3, #6, #7, #12, #13, #15, #27, #72, #74, or #75 before the network has established a secure exchange of NAS messages for the N1 NAS signaling connection, the UE 102 shall stop timer T3510 or T3517 if it is running, and may or shall start timer T3247 if it is not running with a random value drawn uniformly from the following range (see 3GPP TS 24.008):

[0382] a) 15 to 30 minutes for 5GMM reason value #74, or

[0383] b) 30 to 60 minutes for the other 5 GMM reason values

[0384] The following operations may or shall be performed:

[0385] a) If the received 5GMM cause value is #3, #6, or #7,

[0386] 1) If a 5GMM cause value is received via 3GPP access,

[0387] i) If the UE 102 is already registered via another access, the UE 102 may or shall:

[0388] A) Store the current TAI in the list of "5GS Forbidden Tracking Areas for Roaming" and for a non-integrity protected NAS reject message, remember that the current TAI has been stored in the list of "5GS Forbidden Tracking Areas for Roaming" and enter state "5GMM-DEREGISTERED.LIMITED-SERVICE".

[0389] B) Search for a suitable cell in another tracking area according to 3GPP TS 38.304 or 3GPP TS 36.304.

[0390] ii) Otherwise, if the value of the counter for the "Current SNPN entry considered invalid for 3GPP access" event is less than a UE implementation specific maximum value, the UE 102 may or shall:

[0391] A) Set the 5GS update status to "5U3 ROAMING NOT ALLOWED" (and may or shall store it in accordance with clause 5.1.3.2.2) and may or shall erase the 5G-GUTI, last visit registration TAI, TAI list, and ngKSI for 3GPP access.

[0392] B) Increment the counter of the event "entry of current SNPN considered invalid for 3GPP access".

[0393] C) In the case of a REGISTRATION REJECT message, the registration attempt counter is reset, and in the case of a SERVICE REJECT message, the service request attempt counter is reset.

[0394] D) Store the current TAI in the list of "5GS Forbidden Tracking Areas for Roaming" for the current SNPN, and for a non-integrity protected NAS reject message, remember that the current TAI has been stored in the list of "5GS Forbidden Tracking Areas for Roaming" for the current SNPN, and enter state "5GMM-DEREGISTERED.LIMITED-SERVICE".

[0395] E) Search for a suitable cell in another tracking area according to 3GPP TS 38.304 or 3GPP TS 36.304. As a UE 102 implementation option, if access to SNPN services via a PLMN is available and the entry in the "List of Subscriber Data" with the SNPN identity of the current SNPN is not considered invalid for non-3GPP access, the UE 102 may attempt to access SNPN services via a PLMN.

[0396] iii) Otherwise, the UE 102 may or shall proceed as specified in Sections 5.5.1 and 5.6.1 if:

[0397] 2) If the 5GMM reason value is received via non-3GPP access

[0398] In some embodiments, the 5GMM cause value "Received via non-3GPP access" may represent a 5GMM cause value received via a PLMN when the UE 102 attempts to access an SNPN service via the PLMN.

[0399] i) If the UE 102 is already registered via another access, the UE 102 may or shall enter the state "5GMM-DEREGISTERED.LIMITED-SERVICE", or

[0400] ii) Otherwise, if the value of the counter for the "Current SNPN entry considered invalid for non-3GPP access" event is less than a UE implementation-specific maximum value, the UE 102 may or shall:

[0401] A) Set the 5GS update status to "5U3 ROAMING NOT ALLOWED" (and may or shall store it in accordance with clause 5.1.3.2.2) and may or shall erase the 5G-GUTI, last visit registration TAI, TAI list, and ngKSI for non-3GPP access.

[0402] B) Enter state "5GMM-DEREGISTERED.LIMITED-SERVICE".

[0403] C) Increment a counter of "entry of current SNPN considered invalid for non-3GPP access" events. As a UE implementation option, the UE 102 may attempt to register via 3GPP access if 3GPP access is available and the entry in the "list of subscriber data" with the SNPN identity of the current SNPN is not considered invalid for 3GPP access.

[0404] iii) Otherwise, the UE 102 may or shall proceed as specified in Sections 5.5.1 and 5.6.1 if:

[0405] b) If the received 5GMM cause value is #12, #13, or #15, the UE 102 may or shall proceed as specified in clauses 5.5.1 and 5.6.1; and

[0406] 1) If the 5GMM cause value is received via 3GPP access, access to the SNPN service via the PLMN is available, the UE 102 is not already accessing the SNPN service via the PLMN, and the entry in the "List of Subscriber Data" with the SNPN identity of the current SNPN is not considered invalid for non-3GPP access, the UE 102 may attempt to access the SNPN service via the PLMN.

[0407] 2) If the 5GMM cause value is received via non-3GPP access, 3GPP access is available, the UE 102 is not yet registered to the current SNPN via 3GPP access, and the entry in the "List of Subscriber Data" with the SNPN identity of the current SNPN is not considered invalid for 3GPP access, the UE 102 may attempt to register via 3GPP access.

[0408] c) If the received 5GMM cause value is #27, the UE 102 may or shall proceed as specified in clauses 5.5.1 and 5.6.1, and if the value of the SNPN-specific N1 mode attempt counter for each access type (3GPP access) and current SNPN is less than a UE implementation-specific maximum value, the UE 102 may or shall increment this counter for the entry SNPN.

[0409] c1) If the received 5GMM cause value is #72, the UE 102 may or shall proceed as specified in clauses 5.5.1 and 5.6.1, and if the value of the SNPN-specific N1 mode attempt counter for the non-3GPP access and current SNPN is less than a UE implementation-specific maximum, the UE 102 may or shall increment this counter for that entry.

[0410] d) If the received 5GMM cause value is #74 or #75, the UE 102 may or shall do the following:

[0411] 1) If a 5GMM cause value is received over 3GPP access, the UE 102 may or shall:

[0412] i) Set the 5GS update status to "5U3 ROAMING NOT ALLOWED" (and may or shall store it in accordance with clause 5.1.3.2.2) and may or shall erase the 5G-GUTI, last visit registration TAI, TAI list, and ngKSI for 3GPP access.

[0413] ii) In case of a REGISTRATION REJECT message, the registration attempt counter is reset, and in case of a SERVICE REJECT message, the service request attempt counter is reset.

[0414] iii) Store the current TAI in the list of "5GS Forbidden Tracking Areas for Roaming" for the current SNPN and for a non-integrity protected NAS reject message, remember that the current TAI has been stored in the list of "5GS Forbidden Tracking Areas for Roaming" for the current SNPN and enter state "5GMM-DEREGISTERED.LIMITED-SERVICE".

[0415] iv) Search for a suitable cell in another tracking area according to 3GPP TS 38.304 or 3GPP TS 36.304. As a UE 102 implementation option, if access to the SNPN service via a PLMN is available, the UE 102 is not already accessing the SNPN service via a PLMN, and the entry in the "List of Subscriber Data" with the SNPN identity of the current SNPN is not considered invalid for non-3GPP access, the UE 102 may attempt to access the SNPN service via a PLMN.

[0416] 2) If the 5GMM cause value is received via non-3GPP access, the UE 102 may or shall:

[0417] i) Set the 5GS update status to "5U3 ROAMING NOT ALLOWED" (and may or shall store it in accordance with clause 5.1.3.2.2) and may or shall erase the 5G-GUTI, last visit registration TAI, TAI list, and ngKSI for non-3GPP access.

[0418] ii) In case of a REGISTRATION REJECT message, the registration attempt counter is reset, and in case of a SERVICE REJECT message, the service request attempt counter is reset.

[0419] iii) Enter state "5GMM-DEREGISTERED.LIMITED-SERVICE". As a UE 102 implementation option, the UE 102 may attempt to register via 3GPP access if 3GPP access is available, the UE 102 is not already registered with the current SNPN via 3GPP access, and the entry in the "List of Subscriber Data" with the SNPN identity of the current SNPN is not considered invalid for 3GPP access.

[0420] When timer T3247 expires, the UE 102:

[0421] For the current SNPN, MAY or SHALL remove from the list of "5GS Forbidden Tracking Areas for Regional Service Provision" and the list of "5GS Forbidden Tracking Areas for Roaming" all tracking areas stored in these lists for non-integrity protected NAS reject messages.

[0422] If the value of the counter for the event "Entry of current SNPN considered invalid for 3GPP access" is less than a UE implementation specific maximum value, the entry in the "List of subscriber data" with the SNPN identity of the current SNPN may or shall be set valid for 3GPP access.

[0423] If the value of the counter for the event "Entry of current SNPN invalid for non-3GPP access" is less than a UE implementation specific maximum value, the entry in the "List of subscriber data" with the SNPN identity of the current SNPN may or shall be set to valid for non-3GPP access.

[0424] If, for the current SNPN, the value of the SNPN-specific attempt counter for 3GPP access is greater than zero and less than a UE implementation-specific maximum value, and if the SNPN identity of the current SNPN is included in either the "permanently banned SNPN" list or the "temporarily banned SNPN" list, then the SNPN identity of the current SNPN may or shall be removed from the "permanently banned SNPN" list or the "temporarily banned SNPN" list.

[0425] If the value of the SNPN-specific attempt counter for non-3GPP access is greater than zero and less than a UE implementation specific maximum value, and if the SNPN identity of the current SNPN is included in either the "permanently banned SNPN" list for non-3GPP access or the "temporarily banned SNPN" list for non-3GPP access, then the SNPN identity of the current SNPN may or shall be removed from the "permanently banned SNPN" list for non-3GPP access or the "temporarily banned SNPN" list for non-3GPP access.

[0426] The entry index for which N1 mode is not allowed for 3GPP access may or shall be removed from the list of entries if N1 mode capability for 3GPP access is re-enabled for that entry and the value of the SNPN specific N1 mode attempt counter for 3GPP access is greater than zero and less than a UE implementation specific maximum value (see 3GPP TS 23.122).

[0427] If N1 mode capability for non-3GPP access is re-enabled and the value of the SNPN specific N1 mode attempt counter for non-3GPP access is greater than zero and less than a UE implementation specific maximum, then each entry index for which N1 mode for non-3GPP access is not allowed may or shall be removed from the list of entries.

[0428] Depending on the 5GMM state and 5GS update status, it may / shall initiate a registration procedure if still necessary, or it may / shall perform SNPN selection according to 3GPP TS 23.122.

[0429] When the UE 102 is switched off,

[0430] For each SNPN-specific attempt counter for 3GPP access that has a value greater than zero and less than a UE implementation-specific maximum, the UE 102 may or shall remove the respective SNPN identity from the "permanently banned SNPN" list or the "temporarily banned SNPN" list (if available).

[0431] For each SNPN-specific attempt counter for non-3GPP access that has a value greater than zero and less than a UE implementation-specific maximum, the UE 102 may or shall remove the respective SNPN identity from the "permanently banned SNPN" list for non-3GPP access or the "temporarily banned SNPN" list for non-3GPP access (if available).

[0432] When an entry in the "List of Subscriber Data" is updated,

[0433] If the value of the SNPN-specific attempt counter for 3GPP access for the SNPN corresponding to the entry is greater than zero and less than a UE implementation-specific maximum value, the UE 102 may or shall remove the SNPN identity corresponding to the entry from the "permanently banned SNPN" list or the "temporarily banned SNPN" list (if available).

[0434] If, for the SNPN corresponding to the entry, the value of the SNPN-specific attempt counter for non-3GPP access is greater than zero and less than a UE implementation-specific maximum value, the UE 102 may or shall remove the SNPN identification corresponding to the entry from the "permanently banned SNPNs" list for non-3GPP access or the "temporarily banned SNPNs" list for non-3GPP access (if available).

[0435] For example, if an initial registration with the network is requested by the UE 102 and the network returns a rejection message with reason code #27 ("N1 mode not allowed");

[0436] The UE 102 may or shall set the 5GS update status to "5U3 ROAMING NOT ALLOWED" (and may or shall store it according to section 5.1.3.2.2), and may or shall clear any 5G-GUTI, last visit registration TAI, TAI list, and ngKSI. The UE 102 may or shall reset the registration attempt counter, and may or shall enter state "5GMM-DEREGISTERED.LIMITED-SERVICE". If the message integrity check by the NAS is successful, the UE 102:

[0437] 1) for a PLMN, a PLMN-specific N1 mode attempt counter for 3GPP access and a PLMN-specific N1 mode attempt counter for non-3GPP access of the PLMN, or

[0438] 2) In case of an SNPN, an SNPN-specific attempt counter for 3GPP access of the current SNPN;

[0439] may or shall be set to a UE implementation specific maximum value.

[0440] The UE 102 may or shall disable N1 mode capability for the particular access type for which the message was received (see section 4.9.3).

[0441] If the message integrity check by the NAS is successful, the UE 102 may or shall also disable N1 mode capabilities for the other access type, for both 3GPP and non-3GPP access (see section 4.9).

[0442] If the message is received via 3GPP access and the UE 102 is operating in single registration mode, the UE 102 may or shall set the EPS update status to "EU3 ROAMING NOT ALLOWED", may or shall clear any 4G-GUTI, last visited registration TAI, TAI list, and eKSI, and may or shall reset the attachment attempt counter and enter state "EMM-DEREGISTERED".

[0443] For example, if an initial registration to the network is requested by the UE 102 and the network returns a rejection message with reason code #72 ("Non-3GPP access to 5GCN not allowed");

[0444] In case of reception via non-3GPP access, the UE 102 may or shall set the 5GS update status to "5U3 ROAMING NOT ALLOWED" (and may or shall store it according to section 5.1.3.2.2) and may or shall clear the 5G-GUTI, last visit registration TAI, TAI list, and ngKSI. The UE 102 may or shall reset the registration attempt counter and enter state "5GMM-DEREGISTERED". If the message integrity check by the NAS is successful, the UE 102 may or shall set a PLMN-specific N1 mode attempt counter for non-3GPP access of that PLMN to a UE implementation-specific maximum value.

[0445] In some embodiments, the 5GMM sublayer state, 5GMM parameters, and registration status are managed independently for each access type (eg, 3GPP access or non-3GPP access).

[0446] In some embodiments, the UE 102 may or shall disable N1 mode capability for non-3GPP access (see section 4.9.3).

[0447] As an implementation option, the UE 102 may enter the state "5GMM-DEREGISTERED.PLMN-SEARCH" to perform PLMN selection according to 3GPP TS 23.122.

[0448] In the case of reception via 3GPP access, the reason may or shall be considered an abnormal case, and the behavior of the UE 102 in that case is specified in clause 5.5.1.2.7 of 3GPP TS 24.501.

[0449] 8 , a method 10 for managing network capabilities of a device (e.g., UE 102) in a private network (e.g., SNPN, etc.) (e.g., for a 5G network) may be provided. In some embodiments, method 10 may be executable by an apparatus (e.g., CNA 200 and / or apparatus 300) that may include means such as a processor, a memory having computer program code stored thereon, and / or a communications interface, and may maintain, at 11, for at least the user equipment, a list of subscriber data for one or more networks, the list of subscriber data including one or more entries each including an entry index or network identification information used to send requests to the particular network. In some embodiments, method 10 may further include, at 12, maintaining one or more counters for each of the one or more entries. In some embodiments, method 10 may further include, at 13, maintaining a list of one or more entry indexes of entries used to send requests to particular networks that do not allow a particular network access mode, or a list of one or more network identification information for particular networks that do not allow a particular network access mode. In some embodiments, the method 10 may further include, at 14, when a non-integrity protection rejection message for the request is received from the particular network indicating that the particular network does not allow the particular network access mode, and a counter value of one of the one or more counters is below a predetermined threshold, invalidating the entry used to transmit the request or the particular network access mode, starting a timer, and incrementing one of the one or more counters associated with the entry.In some embodiments, method 10 may further include, at 15, re-enabling a particular network access mode for an entry or a particular network used to transmit the request if a counter value of one of the one or more counters is below a predetermined threshold when the timer expires. In some embodiments, method 10 may further include including an index of the entry or an identification of the particular network used to transmit the request in the list of one or more entry indexes or the list of one or more network identifications if a counter value of one of the one or more counters meets a predetermined threshold when the timer expires. In some embodiments, the particular network access mode includes one of a trusted network access mode, an untrusted network access mode, or a non-access stratum interface or protocol. In some embodiments, the one or more networks include at least one of a non-public network (NPN), a private network, a standalone non-public network (SNPN), an NPN deployed with a public network, an NPN deployed with a public land mobile network (PLMN), an NPN deployed with a public network using a shared radio access network, an NPN deployed with a public network using a shared radio access network and a shared control plane, an NPN deployed in a public network, or an NPN deployed in a PLMN. In some embodiments, the non-integrity protection rejection message includes an indication that N1 mode is not allowed for the particular network or an indication that untrusted network access mode is not allowed for the particular network. In some embodiments, the one or more networks include an NPN deployed with a PLMN, the user equipment is deployed in PLMN access mode, and the list of subscriber data includes a list of PLMNs.In some embodiments, the predetermined threshold for one of the one or more counters is implementation dependent and specific to the particular network access mode and the indicator received in the non-integrity protection rejection message.

[0450] 9 , a method 20 for managing network capabilities of a device (e.g., UE 102) in a private network (e.g., SNPN, etc.) (e.g., for a 5G network) may be provided. In some embodiments, method 20 may be executable by an apparatus (e.g., CNA 200 and / or apparatus 300) that may include means such as a processor, a memory having computer program code stored thereon, and / or a communications interface, and may maintain, at 21, for at least the user equipment, a list of subscriber data for one or more networks, the list of subscriber data including one or more entries each including an entry index or network identification information, to be used for sending requests to the particular network. In some embodiments, method 20 may further include, at 22, maintaining a list of one or more entry indexes of entries to be used for sending requests to particular networks that do not allow a particular network access mode, or a list of one or more network identification information for particular networks that do not allow a particular network access mode. In some embodiments, method 20 may further include, at 23, invalidating the entry or the particular network access mode for the particular network used to transmit the request if an integrity protection rejection message for the request is received from the particular network indicating that the particular network does not allow the particular network access mode. In some embodiments, method 20 may further include, at 24, including an index of the entry or an identification of the particular network used to transmit the request in one or more lists of entry indexes, or including an identification of the particular network in one or more lists of network identifications.

[0451] 10 , a method 30 for managing network capabilities of a device (e.g., UE 102) in a private network (e.g., SNPN, etc.) (e.g., for a 5G network) may be provided. In some embodiments, method 30 is executable by an apparatus (e.g., CNA 200 and / or apparatus 300) that may include means such as a processor, a memory having computer program code stored thereon, and / or a communications interface, and may maintain, at 31, for at least the user equipment, a list of subscriber data for one or more networks, the list of subscriber data including an entry index containing a list of networks for which one or more network access modes are disabled. In some embodiments, method 30 may further include, at 32, maintaining, for each of the one or more networks, one or more counters of access attempts via one or more network access modes. In some embodiments, method 20 may further include, at 33, disabling the particular network access mode for the particular network, starting a timer, and incrementing one of the one or more counters associated with the particular network if a non-integrity protection rejection message is received indicating that the particular network of the one or more networks is not configured for the particular network access mode of the one or more network access modes. In some embodiments, method 30 may further include, at 34, re-enabling the particular network access mode for the particular network if a counter value of the one of the one or more counters is below a predetermined threshold when the timer expires. In some embodiments, method 30 may further include, at 35, removing each entry index for the particular access mode for the particular network from the list of subscriber data if a counter value of the one of the one or more counters meets a predetermined threshold when the timer expires.

[0452] 11 , a method 40 for managing network capabilities of a device (e.g., UE 102) in a private network (e.g., SNPN, etc.) (e.g., for a 5G network) may be provided. In some embodiments, method 40 is executable by an apparatus (e.g., CNA 200 and / or apparatus 300) that may include means such as a processor, a memory having computer program code stored thereon, and / or a communications interface, and is operable to compile, at 41, a list of networks for which one or more access modes or one or more access types are disabled for the user equipment. In some embodiments, method 40 may further include, at 42, sending an initial registration request message or a service request message from the user equipment to a network entity of the network for a particular access type with a particular access mode. In some embodiments, method 40 may further include, at 43, receiving from the network entity a rejection message in response to the initial registration request message or the service request message, the rejection message including an indication of a reason for rejection of the initial registration request message or the service request message. In some embodiments, method 40 may further include, at 44, determining a number of times a reject message is received from a network entity when the reason is that the particular access mode is an N1 access mode and the network entity is not configured for N1 access, and adding an entry for the network to the list of networks if the number of times meets a threshold. In some embodiments, method 40 may further include, at 45, determining a number of times a reject message is received from a network entity when the reason is that the particular access type is an untrusted access type and the network is not configured for untrusted access, and adding an entry for the particular access type associated with the network to the list of networks if the number of times meets a threshold.

[0453] 12 , a method 50 for managing network capabilities of a device (e.g., UE 102) in a private network (e.g., SNPN, etc.) (e.g., for a 5G network) may be provided. In some embodiments, method 50 is executable by an apparatus (e.g., CNA 200 and / or apparatus 300) that may include means such as a processor, a memory having computer program code stored thereon, and / or a communications interface, and optionally includes, at 51, retrieving a list of subscriber data for user equipment associated with one or more networks, the list of subscriber data including one or more entries, each including an entry index or network identification information, and operable to track transmission of requests to a particular network or track rejections received by a particular network. In some embodiments, method 50 may further include, at 52, optionally providing one or more counters for each of the one or more entries. In some embodiments, method 50 may further include, at 53, optionally retrieving a list of one or more entry indexes of entries operable to be used to send the request to the particular network that does not allow the particular network access mode, or a list of one or more network identities of the particular network that does not allow the particular network access mode. In some embodiments, method 50 may further include, at 54, sending the request to the particular network by using the particular entry associated with the particular network and the particular network access mode, wherein the request comprises one of an initial registration request or a service request.In some embodiments, method 50 may further include, at 55, disabling the particular entry or the particular network access mode for the particular network used to transmit the request if a non-integrity protection rejection message is received from the particular network in response to transmitting the request, indicating that the particular network does not allow the particular network access mode, starting a timer, and incrementing a corresponding counter of one or more counters associated with the particular entry that is associated with the reason value indicated in the non-integrity protection rejection message. In some embodiments, method 50 may further include, at 56, re-enabling the particular entry or the particular network access mode for the particular network used to transmit the request if, when the timer expires, the counter value of the corresponding counter of the one or more counters is below a predetermined threshold. In some embodiments, method 50 may further include, at 57, e.g., as an alternative to method element 56, including an index of the particular entry or an identification of the particular network used to transmit the request in the list of one or more entry indexes or the list of one or more network identifications if, when the timer expires, the counter value of the corresponding counter of the one or more counters is equal to or greater than a predetermined threshold.

[0454] As noted above, FIGS. 8-12 are flowcharts of methods executable by an apparatus in accordance with an associated computer program product containing computer program code. It will be understood that each block of the flowchart, and combinations of blocks in the flowchart, may be implemented by various means, such as hardware, firmware, processors, circuits, and / or other devices associated with the execution of software containing one or more computer program instructions. For example, one or more of the procedures described above may be embodied by computer program instructions. In this regard, computer program instructions embodying the procedures described above may be stored by a memory device (e.g., 204) of an apparatus (e.g., 200) and, employing an embodiment of the present invention, may be executable by a processing circuit (e.g., 202) of the apparatus. It will be appreciated that any such computer program instructions may be loaded into a programmable apparatus (e.g., hardware), such as a computer, to configure the machine so that the resulting programmable apparatus (e.g., computer) can implement the functions set forth in the flowchart blocks. These computer program instructions can also be stored in a computer-readable memory that can cause a programmable device, such as a computer, to function in a specific manner, thereby constituting an article of manufacture that can implement the functions specified in the flowchart blocks when the instructions stored in the computer-readable memory are executed. Furthermore, the computer program instructions can be loaded into a programmable device, such as a computer, and can cause the programmable device, such as a computer, to execute a series of operations that, when executed on a programmable device, provide operations that implement the functions specified in the flowchart blocks, thereby constituting a computer-implemented process.

[0455] Thus, a computer program product is defined in examples where computer program instructions, such as computer readable program code portions, are stored on at least one non-transitory computer readable storage medium, and where the computer program instructions, such as computer readable program code portions, when executed are configured to perform the functions described above, such as with respect to the flowcharts of Figures 8-12. In other embodiments, computer program instructions, such as computer readable program code portions, need not be stored or embodied on a non-transitory computer readable storage medium, but instead may be embodied on a transitory medium, where the computer program instructions, such as computer readable program code portions, when executed are still configured to perform the functions described above.

[0456] Thus, the blocks of the flowcharts support combinations of means for performing the specified functions and combinations of acts for performing the specified functions, and it will be understood that one or more blocks of the flowcharts, and combinations of blocks in the flowcharts, can be implemented by a dedicated hardware-based computer system that performs the specified functions, or a combination of dedicated hardware and computer instructions.

[0457] In some embodiments, certain of the above operations may be refined or further extended. Furthermore, in some embodiments, additional optional operations may be included. Refinement, addition, or extension to the above operations may be performed in any order and in any combination.

[0458] When a conventional user equipment (UE) is accessing or requesting access to a network and is denied access by the network, it may determine that a particular network access method or interface has been denied by the network. In such a case, the conventional UE typically needs to disable the particular network access method or interface for all networks and / or disable all network access methods or interfaces for the particular network. The systems, apparatuses, methods, and computer program products described herein, according to some embodiments, are provided to solve at least some of the technical challenges faced in conventional and emerging networks. For example, an improved UE of some embodiments can be provided by physically, structurally, operationally, and / or functionally modifying a conventional UE, such as a smartphone, so that network capability information can be stored in the UE in a much more granular and organized manner. This refinement of the granularity of network access capabilities is achieved, for example, by creating a hierarchical data storage structure in which subscriber information stores indexes of entries specific to networks, network access methods, and / or interfaces. In some embodiments, such a structure and the inclusion of such information in the UE's subscriber information may also reduce the number of instances in which an embodiment UE is erroneously disabled for a particular network, a particular network access method or interface, and / or a particular network access method or interface to a particular network. In other words, an embodiment apparatus (and / or embodiment method or embodiment computer program product), when implemented in managing network access capabilities for a UE, may reduce computational complexity and messaging between the UE and a network or network entity, because the UE does not need to continue to request access from a network that has denied the UE access.Similarly, a UE may have greater network availability and / or a larger set of network access methods or interfaces through which the UE may access a network, thereby improving UE performance, e.g., with respect to the speed and availability of messaging between different users' UEs, requesting service from the network, providing service by the network, handling emergency services, downlink / uplink speeds and bandwidth (capacity), etc. Some described embodiments provide substantial technical improvements to a UE, such as a smartphone or another mobile device, during access to or requesting access to a network, for example, because the UE may be able to scan a list of available networks and determine particular networks or a subset of the list of available networks that the UE knows are accessible via a particular network access method or interface, or for which the UE does not have information that the network does not allow a particular network access method or interface. This allows a UE to register or request service by sending messages, such as an initial registration request, to a specific network or a subset of the list of available networks, without using traditional trial-and-error techniques and / or requiring extra messaging between the UE and each available network to request information about the network's capabilities and / or the access methods / interfaces allowed / denied by the network. This may also allow the UE to receive registration acknowledgement messages from the requested networks more quickly, because the networks to which the UE requests access are less likely to deny access. The UE may continue to update and refine its index of network entries, including network capability information, over time, thereby reducing the time it takes to access the network, receive offered services, send messages, upload / download packets, etc.

[0459] Therefore, techniques for managing network capabilities for a UE are described herein. According to exemplary embodiments, a UE may maintain subscriber data including entry indexes for networks for which various access modes are enabled / disabled, and a counter for each network / access mode combination. After requesting access to a network, the UE may receive a non-integrity protection rejection message indicating that the network does not allow the particular access mode. Based on the cause of the access rejection, the UE may disable the particular access mode for the network, start a timer, and increment a counter associated with the network / access mode combination. When the timer expires, the UE re-enables the particular access mode for the network if the counter value is below a threshold, or removes each entry index for the particular access mode for the network if the counter value is equal to or greater than the threshold. According to exemplary embodiments, methods, apparatuses, and computer program products are provided herein for managing device network capabilities in a private network.

[0460] In some embodiments, the method includes, for a user equipment, maintaining a list of subscriber data for one or more networks, the list of subscriber data including one or more entries each including an entry index or network identification information used to send requests to the particular network; maintaining one or more counters for each of the one or more entries; maintaining a list of one or more entry indexes of entries used to send requests to the particular network that does not allow the particular network access mode, or a list of one or more network identification information of the particular network that does not allow the particular network access mode; and detecting a non-integrity protection rejection message in response to a request indicating that the particular network does not allow the particular network access mode. When received from the network, disabling a particular network access mode for the entry or particular network used to transmit the request, starting a timer, and incrementing one of one or more counters associated with the entry, when the timer expires if the counter value of the one of the one or more counters is below a predetermined threshold, re-enabling the particular network access mode for the entry or particular network used to transmit the request, when the timer expires if the counter value of the one of the one or more counters meets the predetermined threshold, when the timer expires if the counter value of the one of the one or more counters meets the predetermined threshold, including an index of the entry or an identification of the particular network used to transmit the request in the list of one or more entry indexes or the list of one or more network identifications. In some embodiments, the particular network access mode includes one of a trusted network access mode, an untrusted network access mode, or a non-access stratum interface or protocol.In some embodiments, the one or more networks include at least one of a non-public network (NPN), a private network, a standalone non-public network (SNPN), an NPN deployed with a public network, an NPN deployed with a public land mobile network (PLMN), an NPN deployed with a public network using a shared radio access network, an NPN deployed with a public network using a shared radio access network and a shared control plane, an NPN deployed in a public network, or an NPN deployed in a PLMN. In some embodiments, the non-integrity protection rejection message includes an indication that N1 mode is not allowed for the particular network or an indication that untrusted network access mode is not allowed for the particular network. In some embodiments, the one or more networks include an NPN deployed with a PLMN, the user equipment is deployed in PLMN access mode, and the list of subscriber data includes a list of PLMNs. In some embodiments, the predetermined threshold for one of the one or more counters is implementation-dependent and specific to the particular network access mode and the indicator received in the non-integrity protection rejection message.

[0461] In some embodiments, an apparatus comprises at least one processor and at least one memory containing computer program code, the at least one memory and the computer program code causing the at least one processor to: maintain, with respect to the user equipment, a list of subscriber data for one or more networks, the list of subscriber data including one or more entries each including an entry index or network identification information used to send a request to a particular network; maintain, for each of the one or more entries, one or more counters; maintain a list of one or more entry indexes of entries used to send a request to a particular network that does not allow a particular network access mode, or a list of one or more network identification information of a particular network that does not allow a particular network access mode; The device may be configured to at least: when a non-integrity protection rejection message for the request is received from a specific network indicating denial, disable the entry or the specific network access mode for the specific network used to transmit the request, start a timer, and increment one of one or more counters associated with the entry; when the timer expires, if the counter value of the one of the one or more counters is below a predetermined threshold, re-enable the entry or the specific network access mode for the specific network used to transmit the request; and when the timer expires, if the counter value of the one of the one or more counters meets the predetermined threshold, include an index of the entry or identification information of the specific network used to transmit the request in a list of one or more entry indexes or a list of one or more network identification information.In some embodiments, the particular network access mode includes one of a trusted network access mode, an untrusted network access mode, or an unaccess stratum interface or protocol. In some embodiments, the one or more networks include at least one of a non-public network (NPN), a private network, a standalone non-public network (SNPN), an NPN deployed with a public network, an NPN deployed with a public land mobile network (PLMN), an NPN deployed with a public network using a shared radio access network, an NPN deployed with a public network using a shared radio access network and a shared control plane, an NPN deployed in a public network, or an NPN deployed in a PLMN. In some embodiments, the non-integrity protection rejection message includes an indication that N1 mode is not allowed for the particular network or an indication that untrusted network access mode is not allowed for the particular network. In some embodiments, the one or more networks include an NPN deployed with a PLMN, the user equipment is deployed in PLMN access mode, and the list of subscriber data includes a list of PLMNs. In some embodiments, the predetermined threshold for one of the one or more counters is implementation dependent and specific to the particular network access mode and the indicator received in the non-integrity protection rejection message.

[0462] In some embodiments, the apparatus includes, for user equipment, a processor or processing circuit, such as a memory having stored thereon computer program code, means for maintaining a list of subscriber data for one or more networks, the list of subscriber data including one or more entries each including an entry index or network identification information, used to send requests to a particular network; means for maintaining one or more counters for each of the one or more entries; means for maintaining a list of one or more entry indexes of entries used to send requests to a particular network that does not allow a particular network access mode, or a list of one or more network identification information of a particular network that does not allow a particular network access mode; and means for maintaining a counter for a request indicating that a particular network does not allow a particular network access mode. The method may include: means for disabling the entry or the specific network access mode for the specific network used to transmit the request when a non-integrity protection rejection message is received from the specific network, starting a timer, and incrementing one of one or more counters associated with the entry; means for re-enabling the entry or the specific network access mode for the specific network used to transmit the request when the counter value of the one of the one or more counters is below a predetermined threshold when the timer expires; and means for including an index of the entry or an identification of the specific network used to transmit the request in the list of one or more entry indexes or the list of one or more network identifications when the counter value of the one of the one or more counters meets the predetermined threshold when the timer expires. In some embodiments, the specific network access mode includes one of a trusted network access mode, an untrusted network access mode, or a non-access stratum interface or protocol.In some embodiments, the one or more networks include at least one of a non-public network (NPN), a private network, a standalone non-public network (SNPN), an NPN deployed with a public network, an NPN deployed with a public land mobile network (PLMN), an NPN deployed with a public network using a shared radio access network, an NPN deployed with a public network using a shared radio access network and a shared control plane, an NPN deployed in a public network, or an NPN deployed in a PLMN. In some embodiments, the non-integrity protection rejection message includes an indication that N1 mode is not allowed for the particular network or an indication that untrusted network access mode is not allowed for the particular network. In some embodiments, the one or more networks include an NPN deployed with a PLMN, the user equipment is deployed in PLMN access mode, and the list of subscriber data includes a list of PLMNs. In some embodiments, the predetermined threshold for one of the one or more counters is implementation-dependent and specific to the particular network access mode and the indicator received in the non-integrity protection rejection message.

[0463] In some embodiments, the computer program product comprises, for a user equipment, maintaining a list of subscriber data for one or more networks, the list of subscriber data including one or more entries each including an entry index or network identification information used to send requests to the particular network; maintaining one or more counters for each of the one or more entries; maintaining a list of one or more entry indexes of entries used to send requests to the particular network that does not allow the particular network access mode, or a list of one or more network identification information of the particular network that does not allow the particular network access mode; and if a non-integrity protection rejection message in response to the request is received from the particular network indicating that the particular network does not allow the particular network access mode, The present invention may include a non-transitory computer-readable medium having stored thereon computer instructions that perform at least the following: disable a specific network access mode for an entry or a specific network used to transmit the request, start a timer, and increment one of one or more counters associated with the entry; when the timer expires, if the counter value of the one of the one or more counters is below a predetermined threshold; and when the timer expires, if the counter value of the one of the one or more counters meets the predetermined threshold, include an index of the entry or an identification of the specific network used to transmit the request in a list of one or more entry indexes or a list of one or more network identifications. In some embodiments, the specific network access mode includes one of a trusted network access mode, an untrusted network access mode, or a non-access stratum interface or protocol.In some embodiments, the one or more networks include at least one of a non-public network (NPN), a private network, a standalone non-public network (SNPN), an NPN deployed with a public network, an NPN deployed with a public land mobile network (PLMN), an NPN deployed with a public network using a shared radio access network, an NPN deployed with a public network using a shared radio access network and a shared control plane, an NPN deployed in a public network, or an NPN deployed in a PLMN. In some embodiments, the non-integrity protection rejection message includes an indication that N1 mode is not allowed for the particular network or an indication that untrusted network access mode is not allowed for the particular network. In some embodiments, the one or more networks include an NPN deployed with a PLMN, the user equipment is deployed in PLMN access mode, and the list of subscriber data includes a list of PLMNs. In some embodiments, the predetermined threshold for one of the one or more counters is implementation-dependent and specific to the particular network access mode and the indicator received in the non-integrity protection rejection message.

[0464] In some embodiments, a method may include, for user equipment, maintaining a list of subscriber data for one or more networks, the list of subscriber data including one or more entries each including an entry index or network identification information, used to transmit a request to the particular network; maintaining a list of one or more entry indexes of entries used to transmit a request to the particular network that does not allow the particular network access mode, or a list of one or more network identification information for the particular network that does not allow the particular network access mode; disabling the entry used to transmit the request or the particular network access mode for the particular network when an integrity protection rejection message for the request is received from the particular network indicating that the particular network does not allow the particular network access mode; and including the index of the entry used to transmit the request or the identification information of the particular network in the list of one or more entry indexes or including the identification information of the particular network in the list of one or more network identities.

[0465] In some embodiments, an apparatus may comprise at least one processor and at least one memory containing computer program code, wherein the at least one memory and computer program code may be configured to cause, by the at least one processor, the apparatus to at least perform the following: maintain, for user equipment, a list of subscriber data for one or more networks, the list of subscriber data including one or more entries each including an entry index or network identification information, used to send a request to a particular network; maintain a list of one or more entry indexes of entries used to send a request to a particular network that does not allow the particular network access mode, or a list of one or more network identification information for the particular network that does not allow the particular network access mode; invalidate the entry used to send the request or the particular network access mode for the particular network when an integrity protection rejection message in response to the request is received from the particular network indicating that the particular network does not allow the particular network access mode; and, when a timer expires, include the index of the entry used to send the request or the identification information of the particular network in the list of one or more entry indexes or the list of one or more network identification information.

[0466] In some embodiments, the apparatus may comprise: means for maintaining, for user equipment, a list of subscriber data for one or more networks, such as a processor or processing circuitry and a memory having computer program code stored therein, the list of subscriber data including one or more entries, each including an entry index or network identification, used to send a request to a particular network; means for maintaining a list of one or more entry indexes of entries used to send a request to a particular network that does not allow the particular network access mode, or a list of one or more network identifications of particular networks that do not allow the particular network access mode; means for invalidating the entry used to send the request or the particular network access mode for the particular network when an integrity protection rejection message for the request is received from the particular network indicating that the particular network does not allow the particular network access mode; and means for including, when a timer expires, the index of the entry used to send the request or the identification of the particular network in the list of one or more entry indexes or the list of one or more network identifications.

[0467] In some embodiments, a computer program product may include a non-transitory computer-readable medium having stored thereon computer instructions that perform at least the following: for a user equipment, maintaining a list of subscriber data for one or more networks, the list of subscriber data including one or more entries each including an entry index or network identification information and used to send a request to a particular network; maintaining a list of one or more entry indexes of entries used to send a request to a particular network that does not allow the particular network access mode, or a list of one or more network identification information for the particular network that does not allow the particular network access mode; invalidating the entry used to send the request or the particular network access mode for the particular network when an integrity protection rejection message for the request is received from the particular network indicating that the particular network does not allow the particular network access mode; and when a timer expires, including the index of the entry used to send the request or the identification information of the particular network in the list of one or more entry indexes or the list of one or more network identification information.

[0468] In some embodiments, a method may include, for a user equipment, maintaining a list of subscriber data for one or more networks, the list of subscriber data including an entry index containing a list of networks for which one or more network access modes are disabled; maintaining, for each of the one or more networks, one or more counters of access attempts via the one or more network access modes; disabling the particular network access mode for the particular network and starting a timer and incrementing one of the one or more counters associated with the particular network when a non-integrity protection rejection message is received indicating that the particular network of the one or more networks is not configured for the particular network access mode of the one or more network access modes; re-enabling the particular network access mode for the particular network if a counter value of the one of the one or more counters is below a predetermined threshold when the timer expires; and removing each entry index of the particular access mode for the particular network from the list of subscriber data if a counter value of the one of the one or more counters meets the predetermined threshold when the timer expires.

[0469] In some embodiments, an apparatus may comprise at least one processor and at least one memory containing computer program code, wherein the at least one memory and the computer program code may be configured to cause, by the at least one processor, the apparatus to perform at least the following: maintain, for user equipment, a list of subscriber data for one or more networks, the list of subscriber data including an entry index containing a list of networks for which one or more network access modes are disabled; maintain, for each of the one or more networks, one or more counters of access attempts via the one or more network access modes; disable the particular network access mode for the particular network, if a non-integrity protection rejection message is received indicating that the particular network of the one or more networks is not configured for the particular network access mode of the one or more network access modes, start a timer, and increment one of the one or more counters associated with the particular network; re-enable the particular network access mode for the particular network if a counter value of the one of the one or more counters is below a predetermined threshold when the timer expires; and remove each entry index of the particular access mode for the particular network from the list of subscriber data if the counter value of the one of the one or more counters meets the predetermined threshold when the timer expires.

[0470] In some embodiments, the apparatus may comprise, for user equipment, means for maintaining a list of subscriber data for one or more networks, such as a processor or processing circuitry and a memory having computer program code stored thereon, the list of subscriber data including an entry index containing a list of networks for which one or more network access modes are disabled; means for maintaining, for each of the one or more networks, one or more counters of access attempts via the one or more network access modes; means for disabling the particular network access mode for the particular network, starting a timer, and incrementing one of the one or more counters associated with the particular network, when a non-integrity protection rejection message is received indicating that the particular network of the one or more networks is not configured for the particular network access mode of the one or more network access modes; means for re-enabling the particular network access mode for the particular network if the counter value of the one of the one or more counters is below a predetermined threshold when the timer expires; and means for removing each entry index of the particular access mode for the particular network from the list of subscriber data if the counter value of the one of the one or more counters meets the predetermined threshold when the timer expires.

[0471] In some embodiments, a computer program product may include a non-transitory computer-readable medium having stored thereon computer instructions that perform at least the following: maintain, for a user equipment, a list of subscriber data for one or more networks, the list of subscriber data including an entry index containing a list of networks for which one or more network access modes are disabled; maintain, for each of the one or more networks, one or more counters of access attempts via the one or more network access modes; disable the particular network access mode for the particular network and start a timer and increment one of the one or more counters associated with the particular network when a non-integrity protection rejection message is received indicating that the particular network of the one or more networks is not configured for the particular network access mode of the one or more network access modes; re-enable the particular network access mode for the particular network if the counter value of the one of the one or more counters is below a predetermined threshold when the timer expires; and remove each entry index of the particular access mode for the particular network from the list of subscriber data if the counter value of the one of the one or more counters meets the predetermined threshold when the timer expires.

[0472] In some embodiments, the method may include compiling a list of networks for which one or more access modes or one or more access types are disabled in a user equipment; sending from the user equipment to a network entity of the network an initial registration request message or a service request message for a particular access type via a particular access mode; receiving from the network entity a rejection message in response to the initial registration request message or the service request message, the rejection message including an indication of a reason for rejection of the initial registration request message or the service request message; determining a number of times a rejection message is received from the network entity when the reason is that the particular access mode is an N1 access mode and the network entity is not configured for N1 access, and adding an entry for the network to the list of networks if the number of times meets a threshold; and determining a number of times a rejection message is received from the network entity when the reason is that the particular access type is an untrusted access type and the network is not configured for untrusted access, and adding an entry for the particular access type associated with the network to the list of networks if the number of times meets a threshold.

[0473] In some embodiments, an apparatus comprises at least one processor and at least one memory containing computer program code, the at least one memory and the computer program code comprising: compiling, by the at least one processor, a list of networks for which one or more access modes or one or more access types are disabled in the user equipment; sending an initial registration request message or a service request message from the user equipment to a network entity of the network for a particular access type with a particular access mode; and receiving an initial registration request message or a service request message from the network entity in response to the initial registration request message or the service request message. The network entity may be configured to at least receive a rejection message including an indication of a reason for rejection of the page; determine a number of times a rejection message has been received from a network entity where the reason is that the particular access mode is an N1 access mode and the network entity is not configured for N1 access, and add an entry for the network to the list of networks if the number of times meets a threshold; and determine a number of times a rejection message has been received from a network entity where the reason is that the particular access type is an untrusted access type and the network is not configured for untrusted access, and add an entry for the particular access type associated with the network to the list of networks if the number of times meets a threshold.

[0474] In some embodiments, the apparatus may comprise: means for compiling a list of networks for which one or more access modes or one or more access types are disabled in user equipment, such as a processor or processing circuitry and a memory having computer program code stored thereon; means for transmitting an initial registration request message or a service request message from the user equipment to a network entity of the network for a particular access type via a particular access mode; means for receiving from the network entity, in response to the initial registration request message or the service request message, a rejection message including an indication of a reason for rejection of the initial registration request message or the service request message; means for determining a number of times a rejection message is received from a network entity when the reason is that the particular access mode is an N1 access mode and the network entity is not configured for N1 access, and adding an entry for the network to the list of networks if the number of times meets a threshold; and means for determining a number of times a rejection message is received from a network entity when the reason is that the particular access type is an untrusted access type and the network is not configured for untrusted access, and adding an entry for the particular access type associated with the network to the list of networks if the number of times meets a threshold.

[0475] In some embodiments, a computer program product may include a non-transitory computer-readable medium having stored thereon computer instructions to perform at least the following: compile, in a user equipment, a list of networks for which one or more access modes or one or more access types are disabled; send from the user equipment to a network entity of the network an initial registration request message or a service request message for a particular access type via a particular access mode; receive from the network entity, in response to the initial registration request message or the service request message, a rejection message including an indication of a reason for rejection of the initial registration request message or the service request message; determine a number of times a rejection message is received from the network entity for a reason where the particular access mode is an N1 access mode and the network entity is not configured for N1 access, and add an entry for the network to the list of networks if the number of times meets a threshold; and determine a number of times a rejection message is received from the network entity for a reason where the particular access type is an untrusted access type and the network is not configured for untrusted access, and add an entry for the particular access type associated with the network to the list of networks if the number of times meets a threshold.

[0476] In some embodiments, the method includes retrieving a list of subscriber data for user equipment associated with one or more networks, the list of subscriber data including one or more entries, each including an entry index or network identification information, operable to track transmission of requests to a particular network or track denials received by a particular network; providing one or more counters for each of the one or more entries; retrieving a list of one or more entry indexes of entries operable to be used to transmit requests to a particular network that does not allow a particular network access mode, or a list of one or more network identification information of a particular network that does not allow a particular network access mode; and transmitting the request to the particular network by using the particular entry associated with the particular network and the particular network access mode. the entry includes one of an initial registration request or a service request; if, in response to transmitting the request to the specific network, a non-integrity protection rejection message is received from the specific network indicating that the specific network does not allow the specific network access mode, disable the specific network access mode for the specific entry or the specific network used to transmit the request, start a timer, and increment a corresponding counter of one or more counters associated with the specific entry that is associated with a reason value indicated in the non-integrity protection rejection message; when the timer expires, if the counter value of the corresponding counter of the one or more counters is below a predetermined threshold, re-enable the specific network access mode for the specific entry or the specific network used to transmit the request; when the timer expires, if the counter value of the corresponding counter of the one or more counters is equal to or greater than the predetermined threshold,and including in the list of one or more entry indexes or list of one or more network identities an index of a particular entry or an identification of a particular network to be used in transmitting the request.

[0477] In some embodiments, an apparatus comprises at least one processor and at least one memory containing computer program code, the at least one memory and computer program code comprising: retrieving, by the at least one processor, a list of subscriber data for user equipment associated with one or more networks, the list of subscriber data including one or more entries, each including an entry index or network identification information, operable to track transmission of requests to a particular network or track denials received by a particular network; providing one or more counters for each of the one or more entries; retrieving a list of one or more entry indexes of entries operable to be used to transmit requests to a particular network that does not allow a particular network access mode, or a list of one or more network identification information of a particular network that does not allow a particular network access mode; and transmitting a request to the specific network by using a specific entry associated with the specific network access mode, the request including one of an initial registration request or a service request; if, in response to transmitting the request to the specific network, a non-integrity protection rejection message is received from the specific network indicating that the specific network does not allow the specific network access mode, disabling the specific entry or the specific network access mode for the specific network used to transmit the request, starting a timer, and incrementing a corresponding counter, among one or more counters associated with the specific entry, that is associated with the reason value indicated in the non-integrity protection rejection message; when the timer expires, if the counter value of the corresponding counter, among the one or more counters, is below a predetermined threshold, re-enabling the specific entry or the specific network access mode for the specific network used to transmit the request; when the timer expires,If a counter value of a corresponding counter among the one or more counters is equal to or greater than a predetermined threshold, include an index of a particular entry or an identification of a particular network used to transmit the request in the list of one or more entry indexes or the list of one or more network identifications.

[0478] In some embodiments, the apparatus includes a processor or processing circuitry and a memory having stored thereon computer program code, and includes: means for retrieving a list of subscriber data for user equipment associated with one or more networks, the list of subscriber data including one or more entries each including an entry index or network identification information, operable to track transmission of requests to a particular network or to track denials received by a particular network; means for providing one or more counters for each of the one or more entries; means for retrieving a list of one or more entry indexes of entries operable to be used to transmit requests to a particular network that does not allow a particular network access mode, or a list of one or more network identifications of a particular network that does not allow a particular network access mode; and means for identifying a request by using a particular entry associated with a particular network and a particular network access mode. means for transmitting a request to a specific network, the request including one of an initial registration request or a service request; means for, when in response to transmitting the request to the specific network, a non-integrity protection rejection message is received from the specific network indicating that the specific network does not allow the specific network access mode, disabling the specific network access mode for the specific entry or the specific network used to transmit the request, starting a timer, and incrementing a corresponding counter associated with the reason value indicated in the non-integrity protection rejection message among one or more counters associated with the specific entry; means for, when the timer expires, if the counter value of the corresponding counter of the one or more counters is below a predetermined threshold, re-enabling the specific network access mode for the specific entry or the specific network used to transmit the request; and means for, when the timer expires, if the counter value of the corresponding counter of the one or more counters is equal to or greater than the predetermined threshold,and means for including in one or more lists of entry indexes or one or more lists of network identities an index of a particular entry or an identification of a particular network to be used in transmitting the request.

[0479] In some embodiments, the computer program product includes: retrieving a list of subscriber data for user equipment associated with one or more networks, the list of subscriber data including one or more entries, each including an entry index or network identification information, operable to track transmission of requests to a particular network or track denials received by a particular network; providing one or more counters for each of the one or more entries; retrieving a list of one or more entry indexes of the entries operable to be used to transmit requests to a particular network that does not allow a particular network access mode, or a list of one or more network identification information of a particular network that does not allow a particular network access mode; and transmitting the request to the particular network by using the particular entry associated with the particular network and the particular network access mode. the request includes one of an initial registration request or a service request; and when, in response to transmitting the request to the specific network, a non-integrity protection rejection message is received from the specific network indicating that the specific network does not allow the specific network access mode, disable the specific network access mode for the specific entry or the specific network used to transmit the request, start a timer, and increment a corresponding counter of one or more counters associated with the specific entry that is associated with a reason value indicated in the non-integrity protection rejection message; when the timer expires, if the counter value of the corresponding counter of the one or more counters is below a predetermined threshold, re-enable the specific network access mode for the specific entry or the specific network used to transmit the request; and when the timer expires, if the counter value of the corresponding counter of the one or more counters is equal to or greater than the predetermined threshold,and including in the list of one or more entry indexes or the list of one or more network identities an index of a particular entry or an identification of a particular network to be used in sending the request.

[0480] Many modifications and other embodiments of the inventions described herein will occur to those skilled in the art to which these inventions pertain having the benefit of the teachings presented in the foregoing description and its associated drawings. Accordingly, the invention is not limited to the particular embodiments disclosed, and modifications and other embodiments are to be understood as falling within the scope of the appended claims. Furthermore, while the foregoing description and its associated drawings describe exemplary embodiments in the context of particular exemplary combinations of elements and / or functions, it will be understood that different combinations of elements and / or functions may be provided in alternative embodiments without departing from the scope of the appended claims. In this regard, for example, different combinations of elements and / or functions than those expressly set forth above may be contemplated as part of the appended claims. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation. The entire contents of any applications, publications, technical documents, etc. cited in this disclosure are incorporated herein by reference.

[0481] While the embodiments set forth herein have been illustrated and described in detail, it will be understood that various changes in form and detail are possible. Unless otherwise specified, the illustrated embodiments can be understood as providing exemplary features of various details of particular embodiments, and, unless otherwise specified, the illustrated features, components, modules, and / or aspects can be otherwise combined, separated, interchanged, and / or rearranged without departing from the disclosed systems or methods. The shapes and sizes of components are also illustrative and, unless otherwise specified, can be changed without affecting the scope of the exemplary systems, devices, or methods of the present disclosure.

[0482] As used herein, the terms "about" and "approximately" generally mean ±10% of the stated value. For example, approximately 250 μm would include 225 μm to 275 μm, and about 1,000 μm would include 900 μm to 1,100 μm.

[0483] Conventional terminology from the fields of telecommunications, network engineering, electrical engineering, computer science, and software engineering is used herein. These terms are known in the art and are provided for convenience only as non-limiting examples. Accordingly, interpretation of corresponding terms in the claims is not limited to any particular definition unless otherwise specified. For this reason, the terms used in the claims should be given their broadest reasonable interpretation.

[0484] Although specific embodiments have been shown and described herein, it will be apparent to those skilled in the art that any adapted structure for achieving the same purpose may be substituted for the specific embodiments shown. Many adaptations will be apparent to those skilled in the art. Accordingly, this application is intended to cover any adaptations or modifications.

[0485] The above detailed description includes references to the accompanying drawings, which form a part of this detailed description. The drawings show, by way of illustration, specific embodiments which may be practiced. These embodiments are also referred to herein as "examples." Such examples may include additional elements other than those shown or described. However, the inventors also contemplate examples in which only the elements shown or described are provided. Furthermore, the inventors also contemplate examples (or one or more aspects thereof) using any combination or permutation of the elements shown or described, relative to the particular example (or one or more aspects thereof) shown or described herein or to other examples (or one or more aspects thereof).

[0486] All publications, technical documents, patents, and patent documents mentioned herein are incorporated herein in their entirety as if individually incorporated by reference. In the event of a conflict between the usage of this specification and any incorporated document, the usage of the incorporated document shall be deemed to supplement the usage of this specification, and in the event of an irreconcilable conflict, the usage of this specification shall prevail.

[0487] As used herein, the terms "a" or "an," as is common in patent documents, are used to include one or more, regardless of any other instance or usage of "at least one" or "one or more." As used herein, the term "or" denotes non-exclusion; i.e., "A or B" includes "A but not B," "B but not A," and "A and B," unless otherwise specified. As used herein, the terms "including" and "in which" are used as plain English equivalents of the terms "comprising" and "wherein," respectively. Also, in the following claims, the terms "including" and "comprising" are open-ended; i.e., systems, devices, articles, or processes that include elements other than those listed after such terms in a claim are still considered to be within the scope of that claim. Furthermore, in the following claims, the terms "first," "second," "third," etc. are used as labels only and are not intended to impose numerical requirements on their respective objects.

[0488] The above description is intended to be illustrative and not limiting. For example, the above examples (or one or more aspects thereof) may be used in combination with each other. Other embodiments may be used by those skilled in the art upon review of the above description. The Abstract complies with 37 CFR §1.72(b) to enable the reader to quickly grasp the nature of the technical disclosure. It has been submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims.

[0489] In the above Detailed Description, various features may be grouped together to simplify the disclosure. This should not be interpreted as intending that an unclaimed feature of the disclosure is essential to any claim. Rather, inventive subject matter may lie in fewer than all features of a particular disclosed embodiment. Accordingly, the following claims are hereby incorporated by reference into the Detailed Description, with each claim standing on its own as a separate embodiment. Such embodiments may be construed as being combinable with each other in various combinations or permutations. The scope of the embodiments should be determined with reference to the appended claims, along with the full range of equivalents to which such claims are entitled.

Claims

1. 1. A user equipment method, comprising: maintaining a list of subscriber data for one or more standalone non-public networks (SNPNs), the list of subscriber data including one or more entries, each of the one or more entries including a respective SNPN identification to be used by the user equipment when sending a request to a particular SNPN of one or more SNPNs associated with the respective SNPN identification; maintaining one or more counters for each entry of said one or more entries; maintaining a list of one or more SNPN identities of SNPNs that do not allow N1 mode; If a non-integrity protection rejection message is received in response to a request sent to a particular SNPN, and the non-integrity protection rejection message includes an indication that the particular SNPN does not allow N1 mode, Disabling N1 mode for the entry or the particular SNPN network used to send the request; causing the user equipment to enter a PLMN SEARCH state; including a SNPN identification of the particular SNPN in the list of one or more entries containing one or more identifications of SNPNs that do not allow N1 mode; Start the timer, and incrementing a particular one of the one or more counters associated with an entry used by the user equipment to send the request to the particular SNPN; When the timer expires, re-enabling the N1 mode for the entry or the particular network used to send the request; and deleting the SNPN identification information of the particular SNPN from a list of one or more entries containing one or more SNPN identification information of SNPNs that do not allow N1 mode when the counter value of the particular counter among the one or more counters has a value greater than zero and is below a predetermined threshold.

2. the predetermined threshold for the particular counter of the one or more counters is implementation dependent; The method of claim 1.

3. The predetermined threshold for the particular counter of the one or more counters maintained in the user equipment is specific to the N1 mode and the indication received in the non-integrity protection rejection message. The method of claim 1.

4. A user equipment, means for maintaining a list of subscriber data for one or more standalone non-public networks (SNPNs), the list of subscriber data including one or more entries, each of the one or more entries including a respective SNPN identification to be used by the user equipment when sending a request to a particular SNPN of one or more SNPNs associated with the respective SNPN identification; means for maintaining one or more counters for each entry of said one or more entries; means for maintaining a list of one or more SNPN identities of SNPNs that do not allow N1 mode; If a non-integrity protection rejection message is received in response to a request sent to a particular SNPN, and the non-integrity protection rejection message includes an indication that the particular SNPN does not allow N1 mode, Disabling N1 mode for the entry or the particular SNPN network used to send the request; causing the user equipment to enter a PLMN SEARCH state; including a SNPN identification of the particular SNPN in the list of one or more entries containing one or more identifications of SNPNs that do not allow N1 mode; Start the timer, and means for incrementing a particular one of the one or more counters associated with an entry used by the user equipment to send the request to the particular SNPN; means for re-enabling the N1 mode for the entry or the particular network used to send the request when the timer expires; and means for deleting the SNPN identification information of the particular SNPN from a list of one or more entries containing one or more SNPN identification information of SNPNs that do not allow N1 mode when the counter value of the particular counter among the one or more counters has a value greater than zero and is below a predetermined threshold.

5. 5. The user equipment of claim 4, wherein the predetermined threshold for the particular counter of the one or more counters is specific to an N1 mode and the indication received in the non-integrity protection rejection message.

6. 1. A computer program product comprising a non-transitory computer readable medium having stored thereon computer instructions, the computer instructions comprising at least: maintaining a list of subscriber data for one or more standalone non-public networks (SNPNs), the list of subscriber data including one or more entries, each of the one or more entries including a respective SNPN identification to be used by the user equipment when sending a request to a particular SNPN of one or more SNPNs associated with the respective SNPN identification; maintaining one or more counters for each entry of said one or more entries; maintaining a list of one or more SNPN identities of SNPNs that do not allow N1 mode; If a non-integrity protection rejection message is received in response to a request sent to a particular SNPN, and the non-integrity protection rejection message includes an indication that the particular SNPN does not allow N1 mode, Disabling N1 mode for the entry or the particular SNPN network used to send the request; causing the user equipment to enter a PLMN SEARCH state; including a SNPN identification of the particular SNPN in the list of one or more entries containing one or more identifications of SNPNs that do not allow N1 mode; Start the timer, and incrementing a particular one of the one or more counters associated with an entry used by the user equipment to send the request to the particular SNPN; When the timer expires, re-enabling the N1 mode for the entry or the particular network used to send the request; and, when the counter value of the particular counter among the one or more counters has a value greater than zero and is below a predetermined threshold, deleting the SNPN identification information of the particular SNPN from a list of one or more entries containing one or more SNPN identification information of SNPNs that do not allow N1 mode.

Images