WO2025237173A1

WO2025237173A1 - Methods and apparatus for handling emergency services and forbidden list in mobile communications

Info

Publication number: WO2025237173A1
Application number: PCT/CN2025/093694
Authority: WO
Inventors: Puneet PUNEET; Marko NIEMI
Original assignee: MediaTek Inc
Current assignee: MediaTek Inc
Priority date: 2024-05-13
Filing date: 2025-05-09
Publication date: 2025-11-20
Anticipated expiration: 2026-11-13

Abstract

Techniques pertaining to handling emergency services and forbidden list in mobile communications are described. An apparatus (e.g., a UE) determines that one or more standalone non-public networks (SNPNs) are in a list of forbidden SNPNs. In response to the determining, the apparatus accesses the one or more SNPNs in the list of forbidden SNPNs. Alternatively, or additionally, the apparatus does not remove an entry from that list of forbidden SNPNs.

Description

METHODS AND APPARATUS FOR HANDLING EMERGENCY SERVICES AND FORBIDDEN LIST IN MOBILE COMMUNICATIONS

CROSS REFERENCE TO RELATED PATENT APPLICATION (S)

The present disclosure claims the priority benefit of Indian Patent Application Nos. 202421037560 and 202421041051, filed 13 May 2024 and 27 May 2024, respectively, the contents of which herein being incorporated by reference in their entirety.

TECHNICAL FIELD

The present disclosure is generally related to mobile communications and, more particularly, to handling emergency services and forbidden list in mobile communications.

BACKGROUND

In wireless communications such as mobile communications under the current 3^rd Generation Partnership Project (3GPP) specification, a mobile station (MS) , or user equipment (UE) , is required to add a standalone non-public network (SNPN) to a list of "temporarily forbidden SNPNs" under certain conditions as follows: (a) for access for localized services in SNPN, if the SNPN is an SNPN selected for localized services in SNPN; (b) for onboarding services, if the MS/UE is registered for onboarding services in SNPN or performing initial registration for onboarding services in SNPN) which is, if the MS/UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both associated with the selected entry of the "list of subscriber data" or the selected public land mobile network (PLMN) subscription, if a message with a cause value #74 "Temporarily not authorized for this SNPN" (see 3GPP Technical Specification (TS) 24.501 [64] ) is received by the MS/UE in response to a location request (LR) from the SNPN.

The MS/UE is also required to add an SNPN to a list of "permanently forbidden SNPNs" under certain conditions as follows: (a) for access for localized services in SNPN, if the SNPN is an SNPN selected for localized services in SNPN; and (b) for onboarding services, if the MS/UE is registered for onboarding services in SNPN or performing initial registration for onboarding services in SNPN) which is, if the MS/UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if a message with a cause value #75 "Permanently not authorized for this SNPN" , #3 "Illegal UE" (applicable in an onboarding SNPN only) , #6 "Illegal ME" (applicable in an onboarding SNPN only) , or #7 "5GS services not allowed" (applicable in an onboarding SNPN only) (see 3GPP TS 24.501 [64] ) is received by the MS/UE in response to an LR request from the SNPN.

Also, under the 3GPP specification, a 5^th Generation Mobility Management (5GMM) cause #36 ( “IAB-node operation not authorized” ) is sent to a UE if the UE, operating as an Integrated Access Backhaul (IAB) -node, requests for a service, or if the network initiates a deregistration procedure, in a PLMN or SNPN where the UE by subscription is not authorized for IAB operations.

However, at the time of the present disclosure, UE behavior is undefined for a number of situations, such as: (a) when the UE is establishing a protocol data unit (PDU) session with the network for an emergency service; (b) when the UE has a PDU session for emergency services; (c) when the UE is being registered for emergency services and a tracking area identity (TAI) is in a forbidden TAI list of a selected SNPN or fully standalone non-public network (FSNPN) list. Moreover, when a visited PLMN (VPLMN) is added to a forbidden list due to a cause value (e.g., #36) indicating IAB-node operation not authorized, UE behavior is undefined.

Therefore, there is a need for a solution of handling emergency services and forbidden list in mobile communications.

SUMMARY

The following summary is illustrative only and is not intended to be limiting in any way. That is, the following summary is provided to introduce concepts, highlights, benefits, and advantages of the novel and non-obvious techniques described herein. Select implementations are further described below in the detailed description. Thus, the following summary is not intended to identify essential features of the claimed subject matter, nor is it intended for use in determining the scope of the claimed subject matter.

An objective of the present disclosure is to propose solutions or schemes that address the issue (s) described herein. More specifically, various schemes proposed in the present disclosure are believed to provide solutions pertaining to handling emergency services and forbidden list in mobile communications. It is believed that implementations of one or more of the schemes proposed herein may address or otherwise alleviate the issues described above.

In one aspect, a method may involve a UE determining that one or more SNPNs are in a list of forbidden SNPNs, while at least one condition exists. The list of forbidden SNPNs may include a list of “temporarily forbidden SNPNs” , a list of “permanently forbidden SNPNs” , a list of “temporarily forbidden SNPNs for access for localized services in SNPN” , a list of “permanently forbidden SNPNs for access for localized services in SNPN” , a list of “permanently forbidden SNPNs” for onboarding services, or a list of “temporarily forbidden SNPNs” for onboarding services. The method may also involve the UE, in response to the determining, performing either or both of the following: (a) accessing the one or more SNPNs in the list of forbidden SNPNs; or (b) not removing an entry from the list of forbidden SNPNs,

In another aspect, a method may involve a UE determining that a VPLMN is added to a forbidden PLMNs list due to a cause value in a message received by the UE indicating an IAB-node operation not authorized, while a precondition is satisfied. The method may also involve the UE, in response to the determining, performing either or both of the following: (a) removing the VPLMN from the forbidden PLMNs list which was added due to the IAB-node operation not authorized after a successful registration due to: (i) a manual selection of the VPLMN; or (ii) expiry of a timer T3245; or (iii) expiry of a timer T3247; and (b) storing the VPLMN in an extension of the forbidden PLMNs list.

It is noteworthy that, although the description provided herein may be in the context of certain radio access technologies, networks, and network topologies such as 5G NR/Beyond Fifth-Generation (B5G) mobile communications, the proposed concepts, schemes and any variation (s) /derivative (s) thereof may be implemented in, for and by other types of radio access technologies, networks and network topologies such as, for example and without limitation, 4G/Long-Term Evolution (LTE) , LTE-Advanced, LTE-Advanced Pro, Internet-of-Things (IoT) , Narrow Band Internet of Things (NB-IoT) , Industrial Internet of Things (IIoT) , vehicle-to-everything (V2X) , and non-terrestrial network (NTN) communications. Thus, the scope of the present disclosure is not limited to the examples described herein.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of the present disclosure. The drawings illustrate implementations of the disclosure and, together with the description, serve to explain the principles of the disclosure. It is appreciable that the drawings are not necessarily in scale as some components may be shown to be out of proportion than the size in actual implementation in order to clearly illustrate the concept of the present disclosure.

FIG. 1 is a diagram of an example network environment in which various solutions and schemes in accordance with the present disclosure may be implemented.

FIG. 2 is a block diagram of an example communication system under a proposed scheme in accordance with the present disclosure.

FIG. 3 is a flowchart of a second example process under a proposed scheme in accordance with the present disclosure.

FIG. 4 is a flowchart of a second example process under a proposed scheme in accordance with the present disclosure.
DETAILED DESCRIPTION OF PREFERRED IMPLEMENTATIONS

Detailed embodiments and implementations of the claimed subject matters are disclosed herein. However, it shall be understood that the disclosed embodiments and implementations are merely illustrative of the claimed subject matters which may be embodied in various forms. The present disclosure may, however, be embodied in many different forms and should not be construed as limited to the exemplary embodiments and implementations set forth herein. Rather, these exemplary embodiments and implementations are provided so that description of the present disclosure is thorough and complete and will fully convey the scope of the present disclosure to those skilled in the art. In the description below, details of well-known features and techniques may be omitted to avoid unnecessarily obscuring the presented embodiments and implementations.
Overview

Implementations in accordance with the present disclosure relate to various techniques, methods, schemes and/or solutions pertaining to handling emergency services and forbidden list in mobile communications. According to the present disclosure, a number of possible solutions may be implemented separately or jointly. That is, although these possible solutions may be described below separately, two or more of these possible solutions may be implemented in one combination or another.

FIG. 1 illustrates an example network environment 100 in which various solutions and schemes in accordance with the present disclosure may be implemented. FIG. 2 ～ FIG. 4 illustrate examples of implementation of various proposed schemes in network environment 100 in accordance with the present disclosure. The following description of various proposed schemes is provided with reference to FIG. 1 ～ FIG. 4.

Referring to FIG. 1, network environment 100 may involve a UE 110, such as a mobile device or smartphone, in wireless communication with a wireless network 120 as part of a communication network. The wireless network 120 may be one or more public land mobile networks (PLMNs) including 5G/NR domain, 4G/LTE domain, and 2^nd Generation/3^rd Generation (2G/3G) domain. UE 110 may initially be in wireless communication with wireless network 120 via a base station or network node 125 (e.g., an eNB, gNB or transmit-receive point (TRP)) . In network environment 100, UE 110 and the wireless network 120 may implement various schemes pertaining to handling emergency services and forbidden list in mobile communications in accordance with the present disclosure, as described herein.

It is noteworthy that, while the various proposed schemes may be individually or separately described below, in actual implementations some or all of the proposed schemes may be utilized or otherwise implemented jointly. Of course, each of the proposed schemes may be utilized or otherwise implemented individually or separately. Moreover, as used herein, a lower layer may refer to a layer in the 5GMM protocol stack that is lower than the radio resource control (RRC) layer, such as a packet data convergence protocol (PDCP) layer, a radio control link (RLC) layer, a medium access control (MAC) layer, a physical (PHY) layer, or so forth.

Under a first proposed scheme in accordance with the present disclosure, in case that UE 110 has one or more SNPNs in a list of “temporarily forbidden SNPNs” , a list of “permanently forbidden SNPNs” , a list of “temporarily forbidden SNPNs for access for localized services in SNPN” , a list of “permanently forbidden SNPNs for access for localized services in SNPN” , a list of “permanently forbidden SNPNs” for onboarding services, or a list of “temporarily forbidden SNPNs” for onboarding services, while at least one conditions exists, UE 110 may access SNPN (s) on one or more of aforementioned lists. UE 110 may, alternatively or additionally, not remove an entry from one or more of aforementioned lists. The at least one condition may include, for example, one or more of the following: (a) UE 110 is establishing a PDU session with wireless network 120 for one or more emergency services; (b) UE 110 has a PDU session with wireless network 120 for one or more emergency services; and (c) UE 110 is being registered for one or more emergency services.

Under a second proposed scheme in accordance with the present disclosure, when a VPLMN is added to a “forbidden PLMNs” list due to a cause value in a message received by UE 110 indicating IAB-node operation not authorized while any of one or more preconditions is satisfied, UE 110 may remove the VPLMN from the “forbidden PLMNs” list which was added due to IAB-node operation not authorized after a successful registration due to manual selection of that VPLMN or expiry of a timer T3245 or expiry of a timer T3247. UE 110 may, alternatively or additionally, store the VPLMN in an extension of the "forbidden PLMNs" list. The one or more preconditions may include one or more of the following: (a) UE 110 is configured to use timer T3245; (b) UE 110 is not configured to use timer T3245 and the message is integrity-protected; (c) UE 110 is not configured to use timer T3245, the message is not integrity-protected, and UE 110 does not maintain a list of PLMN-specific attempt counters; and (d) UE 110 is not configured to use timer T3245, the message is not integrity-protected, UE 110 maintains a list of PLMN-specific attempt counters, and the value of the PLMN-specific attempt counter for that VPLMN is equal to a UE 110 implementation-specific maximum value.

As a first implementation example, an MS (e.g., UE 110) that is establishing or has established a PDU session for emergency services, or is being registered or is registering for emergency services, may access SNPNs in the list "temporarily forbidden SNPNs" , "permanently forbidden SNPNs" , "temporarily forbidden SNPNs for access for localized services in SNPN" , permanently forbidden SNPNs for access for localized services in SNPN" , "permanently forbidden SNPNs" list for onboarding services or "temporarily forbidden SNPNs" list for onboarding services. The MS may not remove any entry from the list of "temporarily forbidden SNPNs" , "permanently forbidden SNPNs" , "temporarily forbidden SNPNs for access for localized services in SNPN" , permanently forbidden SNPNs for access for localized services in SNPN" , "permanently forbidden SNPNs" list for onboarding services or "temporarily forbidden SNPNs" list for onboarding services as a result of such accesses.

As a second implementation example, in a manual or automatic mode, a VPLMN may be added by an MS (e.g., UE 110) to a list of "forbidden PLMNs" in the subscriber identify module (SIM) of the MS if a message with cause value "PLMN not allowed" or "Requested service option not authorized in this PLMN" or "Serving network not authorized" or "IAB-node operation not authorized" is received by the MS in response to an LR request from that VPLMN and any of one or more preconditions is satisfied. The one or more preconditions may include: (a) the MS is configured to use timer T3245 as defined in 3GPP Technical Specification (TS) 24.008 [23] , 3GPP TS 24.301 [23A] , and 3GPP TS 24.501 [64] ; (b) the MS is not configured to use timer T3245 and the message is integrity-protected; (c) the MS is not configured to use timer T3245, the message is not integrity-protected and the MS does not maintain a list of PLMN-specific attempt counters; and (d) the MS is not configured to use timer T3245, the message is not integrity-protected, the MS maintains a list of PLMN-specific attempt counters and the value of the PLMN-specific attempt counter for that VPLMN is equal to the MS implementation specific maximum value as defined in 3GPP TS 24.008 [23] , 3GPP TS 24.301 [23A] and 3GPP TS 24.501 [64] . Moreover, a VPLMN may be stored by the MS in the extension of the "forbidden PLMNs" list if a message with cause value "PLMN not allowed" or "Requested service option not authorized in this PLMN" or "Serving network not authorized" or "IAB-node operation not authorized" is received by an MS in response to an LR request from that VPLMN, while a condition is valid. Such condition may be that the MS is not configured to use timer T3245, the message is not integrity-protected, the MS maintains a list of PLMN-specific attempt counters and the value of the PLMN-specific attempt counter for that VPLMN is less than an MS implementation specific maximum value as defined in 3GPP TS 24.008 [23] , 3GPP TS 24.301 [23A] and 3GPP TS 24.501 [64] .
Illustrative Implementations

FIG. 2 illustrates an example communication system 200 having at least an example apparatus 210 and an example apparatus 220 in accordance with an implementation of the present disclosure. Each of apparatus 210 and apparatus 220 may perform various functions to implement schemes, techniques, processes and methods described herein pertaining to handling emergency services and forbidden list in mobile communications, including the various schemes described above with respect to various proposed designs, concepts, schemes, systems and methods described above, including network environment 100, as well as processes described below.

Each of apparatus 210 and apparatus 220 may be a part of an electronic apparatus, which may be a network apparatus or a UE (e.g., UE 110) , such as a portable or mobile apparatus, a wearable apparatus, a vehicular device or a vehicle, a wireless communication apparatus or a computing apparatus. For instance, each of apparatus 210 and apparatus 220 may be implemented in a smartphone, a smart watch, a personal digital assistant, an electronic control unit (ECU) in a vehicle, a digital camera, or a computing equipment such as a tablet computer, a laptop computer or a notebook computer. Each of apparatus 210 and apparatus 220 may also be a part of a machine type apparatus, which may be an IoT apparatus such as an immobile or a stationary apparatus, a home apparatus, a roadside unit (RSU) , a wire communication apparatus or a computing apparatus. For instance, each of apparatus 210 and apparatus 220 may be implemented in a smart thermostat, a smart fridge, a smart door lock, a wireless speaker or a home control center. When implemented in or as a network apparatus, apparatus 210 and/or apparatus 220 may be implemented in an eNB in an LTE, LTE-Advanced or LTE-Advanced Pro network or in a gNB or TRP in a 5G network, an NR network, or an IoT network.

In some implementations, each of apparatus 210 and apparatus 220 may be implemented in the form of one or more integrated-circuit (IC) chips such as, for example and without limitation, one or more single-core processors, one or more multi-core processors, one or more complex-instruction-set-computing (CISC) processors, or one or more reduced-instruction-set-computing (RISC) processors. In the various schemes described above, each of apparatus 210 and apparatus 220 may be implemented in or as a network apparatus or a UE. Each of apparatus 210 and apparatus 220 may include at least some of those components shown in FIG. 2 such as a processor 212 and a processor 222, respectively, for example. Each of apparatus 210 and apparatus 220 may further include one or more other components not pertinent to the proposed scheme of the present disclosure (e.g., internal power supply, display device and/or user interface device) , and, thus, such component (s) of apparatus 210 and apparatus 220 are neither shown in FIG. 2 nor described below in the interest of simplicity and brevity.

In one aspect, each of processor 212 and processor 222 may be implemented in the form of one or more single-core processors, one or more multi-core processors, or one or more CISC or RISC processors. That is, even though a singular term “aprocessor” is used herein to refer to processor 212 and processor 222, each of processor 212 and processor 222 may include multiple processors in some implementations and a single processor in other implementations in accordance with the present disclosure. In another aspect, each of processor 212 and processor 222 may be implemented in the form of hardware (and, optionally, firmware) with electronic components including, for example and without limitation, one or more transistors, one or more diodes, one or more capacitors, one or more resistors, one or more inductors, one or more memristors and/or one or more varactors that are configured and arranged to achieve specific purposes in accordance with the present disclosure. In other words, in at least some implementations, each of processor 212 and processor 222 is a special-purpose machine specifically designed, arranged, and configured to perform specific tasks including those pertaining to handling emergency services and forbidden list in mobile communications in accordance with various implementations of the present disclosure.

In some implementations, apparatus 210 may also include a transceiver 216 coupled to processor 212. Transceiver 216 may be capable of wirelessly transmitting and receiving data. In some implementations, transceiver 216 may be capable of wirelessly communicating with different types of wireless networks of different radio access technologies (RATs) . In some implementations, transceiver 216 may be equipped with a plurality of antenna ports (not shown) such as, for example, four antenna ports. That is, transceiver 216 may be equipped with multiple transmit antennas and multiple receive antennas for multiple-input multiple-output (MIMO) wireless communications. In some implementations, apparatus 220 may also include a transceiver 226 coupled to processor 222. Transceiver 226 may include a transceiver capable of wirelessly transmitting and receiving data. In some implementations, transceiver 226 may be capable of wirelessly communicating with different types of UEs/wireless networks of different RATs. In some implementations, transceiver 226 may be equipped with a plurality of antenna ports (not shown) such as, for example, four antenna ports. That is, transceiver 226 may be equipped with multiple transmit antennas and multiple receive antennas for MIMO wireless communications.

In some implementations, apparatus 210 may further include a memory 214 coupled to processor 212 and capable of being accessed by processor 212 and storing data therein. In some implementations, apparatus 220 may further include a memory 224 coupled to processor 222 and capable of being accessed by processor 222 and storing data therein. Each of memory 214 and memory 224 may include a type of random-access memory (RAM) such as dynamic RAM (DRAM) , static RAM (SRAM) , thyristor RAM (T-RAM) and/or zero-capacitor RAM (Z-RAM) . Alternatively, or additionally, each of memory 214 and memory 224 may include a type of read-only memory (ROM) such as mask ROM, programmable ROM (PROM) , erasable programmable ROM (EPROM) and/or electrically erasable programmable ROM (EEPROM) . Alternatively, or additionally, each of memory 214 and memory 224 may include a type of non-volatile random-access memory (NVRAM) such as flash memory, solid-state memory, ferroelectric RAM (FeRAM) , magnetoresistive RAM (MRAM) and/or phase-change memory.

Each of apparatus 210 and apparatus 220 may be a communication entity capable of communicating with each other using various proposed schemes in accordance with the present disclosure. For illustrative purposes and without limitation, a description of capabilities of apparatus 210, as a UE (e.g., UE 110) , and apparatus 220, as a network node (e.g., network node 125) of a network (e.g., wireless network 120 as a 5G/NR mobile network) , is provided below in the context of example processes 300 and 400.
Illustrative Processes

FIG. 3 illustrates an example process 300 in accordance with an implementation of the present disclosure. Process 300 may represent an aspect of implementing various proposed designs, concepts, schemes, systems and methods described above. More specifically, process 300 may represent an aspect of the proposed concepts and schemes pertaining to handling emergency services and forbidden list in mobile communications in accordance with the present disclosure. Process 300 may include one or more operations, actions, or functions as illustrated by one or more of blocks 310 and 320. Although illustrated as discrete blocks, various blocks of process 300 may be divided into additional blocks, combined into fewer blocks, or eliminated, depending on the desired implementation. Moreover, the blocks/sub-blocks of process 300 may be executed in the order shown in FIG. 3 or, alternatively, in a different order. Furthermore, one or more of the blocks/sub-blocks of process 300 may be executed repeatedly or iteratively. Process 300 may be implemented by or in apparatus 210 and apparatus 220 as well as any variations thereof. Solely for illustrative purposes and without limiting the scope, process 300 is described below in the context of apparatus 210 as a UE (e.g., UE 110) and apparatus 220 as a communication entity such as a network node or base station (e.g., network node 125) of a network (e.g., wireless network 120) . Process 300 may begin at block 310.

At 310, process 300 may involve processor 212 of apparatus 210, as UE 110, determining that one or more standalone non-public networks (SNPNs) are in a list of forbidden SNPNs, while at least one condition exists. The list of forbidden SNPNs may include a list of “temporarily forbidden SNPNs” , a list of “permanently forbidden SNPNs” , a list of “temporarily forbidden SNPNs for access for localized services in SNPN” , a list of “permanently forbidden SNPNs for access for localized services in SNPN” , a list of “permanently forbidden SNPNs” for onboarding services, or a list of “temporarily forbidden SNPNs” for onboarding services. Process 300 may proceed from 310 to 320.

At 320, process 300 may involve processor 212, in response to the determining, performing either or both of the following: (a) accessing the one or more SNPNs in the list of forbidden SNPNs; or (b) not removing an entry from the list of forbidden SNPNs.

In some implementations, the at least one condition may involve apparatus 210 establishing a PDU session for one or more emergency services.

In some implementations, the at least one condition may involve apparatus 210 having a PDU session for one or more emergency services.

In some implementations, the at least one condition may involve apparatus 210 being registered for one or more emergency services.

In some implementations, the at least one condition may involve one or more of the following: (a) apparatus 210 establishing a PDU session for one or more emergency services; (b) apparatus 210 having the PDU session for the one or more emergency services; or (c) apparatus 210 being registered for the one or more emergency services.

FIG. 4 illustrates an example process 400 in accordance with an implementation of the present disclosure. Process 400 may represent an aspect of implementing various proposed designs, concepts, schemes, systems and methods described above. More specifically, process 400 may represent an aspect of the proposed concepts and schemes pertaining to handling emergency services and forbidden list in mobile communications in accordance with the present disclosure. Process 400 may include one or more operations, actions, or functions as illustrated by one or more of blocks 410 and 420. Although illustrated as discrete blocks, various blocks of process 400 may be divided into additional blocks, combined into fewer blocks, or eliminated, depending on the desired implementation. Moreover, the blocks/sub-blocks of process 400 may be executed in the order shown in FIG. 4 or, alternatively, in a different order. Furthermore, one or more of the blocks/sub-blocks of process 400 may be executed repeatedly or iteratively. Process 400 may be implemented by or in apparatus 210 and apparatus 220 as well as any variations thereof. Solely for illustrative purposes and without limiting the scope, process 400 is described below in the context of apparatus 210 as a UE (e.g., UE 110) and apparatus 220 as a communication entity such as a network node or base station (e.g., network node 125) of a network (e.g., wireless network 120) . Process 400 may begin at block 410.

At 410, process 400 may involve processor 212 of apparatus 210, as UE 110, determining that a VPLMN is added to a forbidden PLMNs list due to a cause value in a message received by apparatus 210 from a network (e.g., wireless network 120 via apparatus 220 as network node 125) indicating an IAB-node operation not authorized, while a precondition is satisfied. Process 400 may proceed from 410 to 420.

At 420, process 400 may involve processor 212, in response to the determining, performing either or both of the following: (a) removing the VPLMN from the forbidden PLMNs list which was added due to the IAB-node operation not authorized after a successful registration due to: (i) a manual selection of the VPLMN; or (ii) expiry of a timer T3245; or (iii) expiry of a timer T3247; and (b) storing the VPLMN in an extension of the forbidden PLMNs list.

In some implementations, the precondition may involve apparatus 210 being configured to use the timer T3245.

In some implementations, the precondition may involve apparatus 210 not being configured to use the timer T3245 and the message being integrity-protected.

In some implementations, the precondition may involve apparatus 210 not being configured to use the timer T3245, the message not being integrity-protected, and apparatus 210 not maintaining a list of PLMN-specific attempt counters.

In some implementations, the precondition may involve apparatus 210 not being configured to use the timer T3245, the message not being integrity-protected, apparatus 210 maintaining a list of PLMN-specific attempt counters, and a value of the list of PLMN-specific attempt counters for the VPLMN being equal to a UE implementation-specific maximum value.
Additional Notes

The herein-described subject matter sometimes illustrates different components contained within, or connected with, different other components. It is to be understood that such depicted architectures are merely examples, and that in fact many other architectures can be implemented which achieve the same functionality. In a conceptual sense, any arrangement of components to achieve the same functionality is effectively "associated" such that the desired functionality is achieved. Hence, any two components herein combined to achieve a particular functionality can be seen as "associated with" each other such that the desired functionality is achieved, irrespective of architectures or intermedial components. Likewise, any two components so associated can also be viewed as being "operably connected" , or "operably coupled" , to each other to achieve the desired functionality, and any two components capable of being so associated can also be viewed as being "operably couplable" , to each other to achieve the desired functionality. Specific examples of operably couplable include but are not limited to physically mateable and/or physically interacting components and/or wirelessly interactable and/or wirelessly interacting components and/or logically interacting and/or logically interactable components.

Further, with respect to the use of substantially any plural and/or singular terms herein, those having skill in the art can translate from the plural to the singular and/or from the singular to the plural as is appropriate to the context and/or application. The various singular/plural permutations may be expressly set forth herein for sake of clarity.

Moreover, it will be understood by those skilled in the art that, in general, terms used herein, and especially in the appended claims, e.g., bodies of the appended claims, are generally intended as “open” terms, e.g., the term “including” should be interpreted as “including but not limited to, ” the term “having” should be interpreted as “having at least, ” the term “includes” should be interpreted as “includes but is not limited to, ” etc. It will be further understood by those within the art that if a specific number of an introduced claim recitation is intended, such an intent will be explicitly recited in the claim, and in the absence of such recitation no such intent is present. For example, as an aid to understanding, the following appended claims may contain usage of the introductory phrases "at least one" and "one or more" to introduce claim recitations. However, the use of such phrases should not be construed to imply that the introduction of a claim recitation by the indefinite articles "a" or "an" limits any particular claim containing such introduced claim recitation to implementations containing only one such recitation, even when the same claim includes the introductory phrases "one or more" or "at least one" and indefinite articles such as "a" or "an, " e.g., “a” and/or “an” should be interpreted to mean “at least one” or “one or more; ” the same holds true for the use of definite articles used to introduce claim recitations. In addition, even if a specific number of an introduced claim recitation is explicitly recited, those skilled in the art will recognize that such recitation should be interpreted to mean at least the recited number, e.g., the bare recitation of "two recitations, " without other modifiers, means at least two recitations, or two or more recitations. Furthermore, in those instances where a convention analogous to “at least one of A, B, and C, etc. ” is used, in general such a construction is intended in the sense one having skill in the art would understand the convention, e.g., “asystem having at least one of A, B, and C” would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C together, etc. In those instances where a convention analogous to “at least one of A, B, or C, etc. ” is used, in general such a construction is intended in the sense one having skill in the art would understand the convention, e.g., “a system having at least one of A, B, or C” would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C together, etc. It will be further understood by those within the art that virtually any disjunctive word and/or phrase presenting two or more alternative terms, whether in the description, claims, or drawings, should be understood to contemplate the possibilities of including one of the terms, either of the terms, or both terms. For example, the phrase “A or B” will be understood to include the possibilities of “A” or “B” or “A and B. ”

From the foregoing, it will be appreciated that various implementations of the present disclosure have been described herein for purposes of illustration, and that various modifications may be made without departing from the scope and spirit of the present disclosure. Accordingly, the various implementations disclosed herein are not intended to be limiting, with the true scope and spirit being indicated by the following claims.

Claims

A method, comprising:

determining, by a processor of a user equipment (UE) , that one or more standalone non-public networks (SNPNs) are in a list of forbidden SNPNs, while at least one condition exists; and

responsive to the determining, performing, by the processor, either or both of:

accessing the one or more SNPNs in the list of forbidden SNPNs; or

not removing an entry from the list of forbidden SNPNs,

wherein the list of forbidden SNPNs comprises a list of “temporarily forbidden SNPNs” , a list of “permanently forbidden SNPNs” , a list of “temporarily forbidden SNPNs for access for localized services in SNPN” , a list of “permanently forbidden SNPNs for access for localized services in SNPN” , a list of “permanently forbidden SNPNs” for onboarding services, or a list of “temporarily forbidden SNPNs” for onboarding services.
The method of Claim 1, wherein the at least one condition comprises the UE establishing a protocol data unit (PDU) session for one or more emergency services.
The method of Claim 1, wherein the at least one condition comprises the UE having a protocol data unit (PDU) session for one or more emergency services.
The method of Claim 1, wherein the at least one condition comprises the UE being registered for one or more emergency services.
The method of Claim 1, wherein the at least one condition comprises one or more of:

the UE establishing a protocol data unit (PDU) session for one or more emergency services;

the UE having the PDU session for the one or more emergency services; or

the UE being registered for the one or more emergency services.
A method, comprising:

determining, by a processor of a user equipment (UE) , that a visited public land mobile network (VPLMN) is added to a forbidden public land mobile networks (PLMNs) list due to a cause value in a message received by the UE indicating an integrated access backhaul (IAB) -node operation not authorized, while a precondition is satisfied; and

responsive to the determining, performing, by the processor, either or both of:

removing the VPLMN from the forbidden PLMNs list which was added due to the IAB-node operation not authorized after a successful registration due to:

a manual selection of the VPLMN; or

expiry of a timer T3245; or

expiry of a timer T3247; and

storing the VPLMN in an extension of the forbidden PLMNs list.
The method of Claim 6, wherein the precondition comprises the UE being configured to use the timer T3245.
The method of Claim 6, wherein the precondition comprises the UE not being configured to use the timer T3245 and the message being integrity-protected.
The method of Claim 6, wherein the precondition comprises the UE not being configured to use the timer T3245, the message not being integrity-protected, and the UE not maintaining a list of PLMN-specific attempt counters.
The method of Claim 6, wherein the precondition comprises the UE not being configured to use the timer T3245, the message not being integrity-protected, the UE maintaining a list of PLMN-specific attempt counters, and a value of the list of PLMN-specific attempt counters for the VPLMN being equal to a UE implementation-specific maximum value.
An apparatus implementable in a user equipment (UE) , comprising:

a transceiver configured to communicate wirelessly; and

a processor coupled to the transceiver and configured to perform operations comprising:

determining that one or more standalone non-public networks (SNPNs) are in a list of forbidden SNPNs, while at least one condition exists; and

responsive to the determining, performing either or both of:

accessing the one or more SNPNs in the list of forbidden SNPNs; or

not removing an entry from the list of forbidden SNPNs,

wherein the list of forbidden SNPNs comprises a list of “temporarily forbidden SNPNs” , a list of “permanently forbidden SNPNs” , a list of “temporarily forbidden SNPNs for access for localized services in SNPN” , a list of “permanently forbidden SNPNs for access for localized services in SNPN” , a list of “permanently forbidden SNPNs” for onboarding services, or a list of “temporarily forbidden SNPNs” for onboarding services.
The apparatus of Claim 11, wherein the at least one condition comprises the UE establishing a protocol data unit (PDU) session for one or more emergency services.
The apparatus of Claim 11, wherein the at least one condition comprises the UE having a protocol data unit (PDU) session for one or more emergency services.
The apparatus of Claim 11, wherein the at least one condition comprises the UE being registered for one or more emergency services.
The apparatus of Claim 11, wherein the at least one condition comprises one or more of:

the UE establishing a protocol data unit (PDU) session for one or more emergency services;

the UE having the PDU session for the one or more emergency services; or

the UE being registered for the one or more emergency services.
An apparatus implementable in a user equipment (UE) , comprising:

a transceiver configured to communicate wirelessly; and

a processor coupled to the transceiver and configured to perform operations comprising:

determining, by a processor of a user equipment (UE) , that a visited public land mobile network (VPLMN) is added to a forbidden public land mobile networks (PLMNs) list due to a cause value in a message received by the UE indicating an integrated access backhaul (IAB) -node operation not authorized, while a precondition is satisfied; and

responsive to the determining, performing, by the processor, either or both of:

removing the VPLMN from the forbidden PLMNs list which was added due to the IAB-node operation not authorized after a successful registration due to:

a manual selection of the VPLMN; or

expiry of a timer T3245; or

expiry of a timer T3247; and

storing the VPLMN in an extension of the forbidden PLMNs list.
The apparatus of Claim 16, wherein the precondition comprises the UE being configured to use the timer T3245.
The apparatus of Claim 16, wherein the precondition comprises the UE not being configured to use the timer T3245 and the message being integrity-protected.
The apparatus of Claim 16, wherein the precondition comprises the UE not being configured to use the timer T3245, the message not being integrity-protected, and the UE not maintaining a list of PLMN-specific attempt counters.
The apparatus of Claim 16, wherein the precondition comprises the UE not being configured to use the timer T3245, the message not being integrity-protected, the UE maintaining a list of PLMN-specific attempt counters, and a value of the list of PLMN-specific attempt counters for the VPLMN being equal to a UE implementation-specific maximum value.