Method and apparatus for handling equivalent independent non-public network for localized services
By setting up UE registration request messages and managing the equivalent independent non-public network list, the problem of equivalent independent non-public networks being prohibited in localized services is solved, enabling reasonable network selection and management, and improving the efficiency and accuracy of mobile communication.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-01
- Publication Date
- 2026-04-03
AI Technical Summary
In mobile communications, existing technologies have failed to effectively address the prohibition and selection issues of equivalent independent non-public networks (SNPNs) in localized services, resulting in the potential use of SNPNs that are prohibited during Public Land Mobile Network (PLMN) selection or cell reselection processes.
The User Equipment (UE) receives and manages the Equivalent Independent Non-Public Network (SNPN) list by setting the encoding symbol identifier bit of the 5G Mobility Management Capability Information element in the Registration Request message to 'Support Equivalent Independent Non-Public Network', and removes prohibited SNPN identifiers from the list based on conditions, including SNPNs in the 'Permanently Prohibited' and 'Temporarily Prohibited' lists.
This solves the problem of the equivalent SNPN being prohibited in localized services, ensuring that UEs can reasonably select and manage SNPNs in mobile communications, and improving the efficiency and accuracy of network selection.
Smart Images
Figure CN121795008A_ABST
Abstract
Description
[0001] Cross-references
[0002] This disclosure claims priority to Indian Patent Application No. 202321059941, filed on September 6, 2023, the contents of which are incorporated herein by reference in their entirety. Technical Field
[0003] This disclosure generally relates to mobile communications, and more specifically, to the processing of equivalent standalone non-public networks (SNPNs) for localized services in mobile communications. Background Technology
[0004] In the current 3rd generation partnership program (3 rd In wireless communications (such as mobile communications) under the Generation Partnership Project (3GPP) specification, if the registration request message is in the 5th generation mobility management (5GM) specification... th If the encoding symbol identifier (ESI) bit of the Generation Partnership Project (5GMM) information element (IE) is set to "Support standalone non-public network (SNPN)," then the SNPN's Access & Mobility Management Function (AMF) can include an equivalent SNPN list in the corresponding registration acceptance message. Each entry in this list contains an SNPN identifier, which the User Equipment (UE) should store according to the list provided by the network. If the initial registration process is not for emergency services and is not an initial registration in an SNPN for network access, the UE should remove any SNPN identifiers already in the "Permanently Prohibited Standalone Non-Public Networks" and "Temporarily Prohibited Standalone Non-Public Networks" lists from the list. Furthermore, the UE should add the SNPN identifiers of the registered SNPNs that sent this list to the stored list. The UE should also replace the stored list each time a registration acceptance message is received. If the registration acceptance message does not contain a list, the UE should delete the stored list. The SNPN's AMF should not include a list of equivalent public land mobile networks (PLMNs).
[0005] However, when registration is for accessing localized services, and / or when the UE receives an equivalent SNPN list and the SNPN belongs to either the "Temporarily Prohibited Independent Non-Public Networks for Access to Localized Services in Independent Non-Public Networks" list or the "Permanently Prohibited Independent Non-Public Networks for Access to Localized Services in Independent Non-Public Networks" list, the prohibited SNPN may be used during Public Land Mobile Network (PLMN) selection or cell reselection processes. Therefore, it is necessary to address the issue of handling equivalent SNPNs used for localized services in mobile communications. Summary of the Invention
[0006] The following summary is for illustrative purposes only and is not intended to be limiting in any way. That is, the following summary aims to introduce the concepts, highlights, benefits, and advantages of the novel and non-obvious techniques described herein. Selected embodiments will be further described in the detailed description below. Therefore, the following summary is not intended to identify the essential features of the claimed subject matter, nor is it intended to determine the scope of the claimed subject matter.
[0007] The objective of this disclosure is to propose solutions or schemes to address the problems described herein. More specifically, the various schemes proposed in this disclosure are intended to provide solutions related to processing equivalent independent non-public networks for localized services in mobile communications. It is believed that implementation of one or more of the schemes proposed herein can solve or mitigate the aforementioned problems.
[0008] In one aspect, a method may involve a user equipment sending a registration request message to a first independent non-public network (ISN) having a first ISN identifier. The encoded symbol identifier bit of the fifth-generation mobility management capability information element of the registration request message may be set to "support equivalent ISNs". The method may also involve the user equipment receiving a registration acceptance message from the first ISN containing a list of equivalent ISNs, which includes a second ISN identifier. The method may further involve the user equipment removing the second ISN identifier from the list of equivalent ISNs when certain conditions are met.
[0009] In another aspect, an apparatus may include a transceiver configured for wireless communication and a processor coupled to the transceiver. The processor may send a registration request message to a first independent non-public network (ISN) having a first ISN identifier. The encoded symbol identifier bit of the fifth-generation mobility management capability information element in the registration request message may be set to "support equivalent ISNs". The processor may also receive from the first ISN a registration acceptance message containing a list of equivalent ISNs, which includes a second ISN identifier. The processor may also remove the second ISN identifier from the list of equivalent ISNs when certain conditions are met.
[0010] It is worth noting that although the descriptions provided herein may be made in the context of certain wireless access technologies, networks, and network topologies (such as fifth-generation (5G) / new radio (NR) / beyond fifth-generation (B5G) mobile communications), the proposed concepts, schemes, and any variations / derivatives thereof can be implemented, for, and through other types of wireless access technologies, networks, and network topologies, such as, but not limited to, fourth-generation (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. Therefore, the scope of this disclosure is not limited to the examples described herein. Attached Figure Description
[0011] The accompanying drawings are included to provide a further understanding of the present disclosure and form part of this disclosure. The drawings illustrate embodiments of the present disclosure and, together with the description, serve to explain the principles of the present disclosure. It will be understood that the drawings are not necessarily drawn to scale, as some components may be shown out of proportion to their actual dimensions in order to clearly illustrate the concepts of the present disclosure.
[0012] Figure 1 This is a schematic diagram of an example network environment that can implement various solutions and schemes according to this disclosure.
[0013] Figure 2 This is a block diagram of an example communication system conforming to one embodiment of the present disclosure.
[0014] Figure 3 This is a flowchart of a second example process conforming to an embodiment of the present disclosure. Detailed Implementation
[0015] This document discloses detailed embodiments and implementations of the claimed subject matter. However, it should be understood that the disclosed embodiments and implementations are merely illustrative of the claimed subject matter, which can be embodied in various forms. This disclosure can be embodied in many different forms and should not be construed as being limited to the exemplary embodiments and implementations listed herein. Rather, these exemplary embodiments and implementations are provided to make the description of this disclosure comprehensive and complete, and to fully convey the scope of this disclosure to those skilled in the art. Details of well-known features and techniques may be omitted in the following description to avoid unnecessarily obscuring the presented embodiments and implementations.
[0016] Overview
[0017] Embodiments of this disclosure relate to various techniques, methods, schemes, and / or solutions for processing equivalent independent non-public networks for localized services in mobile communications. According to this disclosure, many possible solutions can be implemented individually or in combination. That is, although these possible solutions may be described separately below, two or more of these possible solutions can be implemented in one or another combination.
[0018] Figure 1 An example network environment 100 is shown, in which various solutions and schemes according to this disclosure can be implemented. Figures 2 to 3 Examples of implementations of various proposed schemes in network environment 100 according to this disclosure are shown. The following descriptions of the various proposed schemes are for reference only. Figures 1 to 3 Provided.
[0019] See Figure 1 Network environment 100 may involve a user equipment 110, such as a mobile device or smartphone, wirelessly communicating with a wireless network 120 as part of a communication network. Wireless network 120 may be a public land mobile network (PLMN) encompassing 5G / NR and 4G / LTE domains. User equipment 110 may initially communicate wirelessly with wireless network 120 via a base station or network node 125 (e.g., eNB, gNB, or transmit-receive point (TRP)). In network environment 100, user equipment 110 and wireless network 120 can implement an equivalent independent non-public network for handling localized services in mobile communications according to various schemes of this disclosure, as described herein.
[0020] It is worth noting that while various proposed schemes may be described individually or separately below, in actual implementation, some or all of the proposed schemes may be used in combination or implemented in other ways. Of course, each proposed scheme may be used individually or separately or implemented in other ways. Furthermore, as used herein, "lower layer" can refer to layers in the 5GMM protocol stack below the radio resource control (RRC) layer, such as the packet data convergence protocol (PDCP) layer, radio control link (RLC) layer, medium access control (MAC) layer, physical (PHY) layer, etc.
[0021] According to the proposed scheme of this disclosure, when user equipment 110 receives an equivalent list of independent non-public networks from the first independent non-public network, user equipment 110 can remove any independent non-public network from the list of "temporarily prohibited independent non-public networks for access to localized services in independent non-public networks" from the equivalent list of independent non-public networks. Alternatively, when user equipment 110 receives an equivalent list of independent non-public networks from the first independent non-public network, user equipment 110 can remove any independent non-public network identifier from the list of "permanently prohibited independent non-public networks for access to localized services in independent non-public networks". The above can be achieved when one or more of the following conditions are met: (1) the first independent non-public network is selected for access to localized services in independent non-public networks (e.g., the first independent non-public network is selected according to clause a0 of sub-clause 4.9.3.1.1 of 3GPP Technical Specification (TS) 23.122); and / or (2) if the registration is not for emergency services; and / or (3) if the registration is not for network access services in independent non-public networks.
[0022] As an example implementation of the proposed scheme, when network 120 accepts initial registration, if the encoded symbol identifier bit of the fifth-generation mobility management capability information element in the registration request message is set to "Support Equivalent Independent Non-Public Networks," then the Access and Mobility Management Function (AMF) of the independent non-public network can include a list of equivalent independent non-public networks in the registration acceptance message. Each entry in the list can contain an independent non-public network identifier. User equipment 110 can store this list in a manner provided by the network. If the initial registration process is not for emergency services and is not for initial registration for network access services in an independent non-public network, user equipment 110 can remove any independent non-public network identifiers already in the "Permanently Prohibited Independent Non-Public Networks" list and the "Temporarily Prohibited Independent Non-Public Networks" list (optionally, if the independent non-public network was not selected according to item a0 of sub-clause 4.9.3.1.1 of 3GPP TS 23.122). Alternatively, user equipment 110 may remove any independent non-public network identifiers already in the "Temporarily Prohibited Independent Non-Public Networks for Localized Service Access in Independent Non-Public Networks" list (optionally, if the independent non-public network was selected pursuant to sub-clause 4.9.3.1.1a0 of 3GPP TS 23.122). Alternatively, user equipment 110 may remove any independent non-public network identifiers already in the "Permanently Prohibited Independent Non-Public Networks for Localized Service Access in Independent Non-Public Networks" list (optionally, if the independent non-public network was selected pursuant to sub-clause 4.9.3.1.1a0 of 3GPP TS 23.122).
[0023] According to the proposed scheme, User Equipment 110 can add the identifier of the Independent Non-Public Network (INN) registered in the sending list to a stored list. User Equipment 110 can also replace the stored list each time a registration acceptance message is received. If the registration acceptance message does not contain a list, User Equipment 110 can delete the stored list. The Access and Mobility Management Function (AMF) of an INN may not include a list of equivalent Public Land Mobile Networks (PLMNs).
[0024] In light of the above, the key points of the proposed solution are summarized below.
[0025] In the proposed scheme, User Equipment (UE) 110 can select a first independent non-public network (ISN) with a first ISN identifier according to item (a0) of sub-clause 4.9.3.1.1 of 3GPP TS 23.122. UE 110 can then send a registration request message to the first ISN, setting the Encoded Symbol Identifier (ESI) bit of the 5GMM Capability Information Element (IE) to "Support Equivalent ISN". In response, UE 110 can receive a registration acceptance message containing a list of equivalent ISNs from the first ISN. If the received list of equivalent ISNs contains a second ISN identifier, and that second ISN identifier is already in the "Permanently Prohibited ISN" list, then UE 110 can remove the second ISN identifier from the list of equivalent ISNs. Alternatively, if the received equivalent independent non-public network list contains a second independent non-public network identifier, and that second independent non-public network identifier is already in the "Temporarily Prohibited Independent Non-Public Networks" list, then UE 110 can remove the second independent non-public network identifier from the equivalent independent non-public network list. Alternatively, if the received equivalent independent non-public network list contains a second independent non-public network identifier, and that second independent non-public network identifier is already in the "Temporarily Prohibited Independent Non-Public Networks for Localized Service Access in Independent Non-Public Networks" list, then UE 110 can remove the second independent non-public network identifier from the equivalent independent non-public network list. Alternatively, if the received equivalent independent non-public network list contains a second independent non-public network identifier, and that second independent non-public network identifier is already in the "Permanently Prohibited Independent Non-Public Networks for Localized Service Access in Independent Non-Public Networks" list, then UE 110 can remove the second independent non-public network identifier from the equivalent independent non-public network list.
[0026] Exemplary Implementation
[0027] Figure 2 An example communication system 200 is shown, comprising at least one example device 210 and one example device 220, conforming to an implementation of this disclosure. Each of devices 210 and 220 can perform various functions to implement the schemes, techniques, processes, and methods described herein, relating to processing equivalent independent non-public networks for localized services in mobile communications, including the various schemes described above regarding various proposed designs, concepts, schemes, systems, and methods, including network environment 100, and the processes described below.
[0028] Each of devices 210 and 220 may be part of an electronic device, which may be a network device or user equipment (e.g., UE 110), such as a portable or mobile device, a wearable device, an in-vehicle device or vehicle, a wireless communication device, or a computing device. For example, each of devices 210 and 220 may be implemented in a smartphone, smartwatch, personal digital assistant, electronic control unit (ECU) in a vehicle, digital camera, or computing device such as a tablet, laptop, or notebook computer. Each of devices 210 and 220 may also be part of a machine-type device, which may be an Internet of Things (IoT) device, such as a fixed or stationary device, a home device, a roadside unit (RSU), a wired communication device, or a computing device. For example, each of devices 210 and 220 may be implemented in a smart thermostat, a smart refrigerator, a smart door lock, a wireless speaker, or a home control center. When implemented in or as a network device, device 210 and / or device 220 may be implemented in an eNodeB in an LTE, LTE-Advanced, or LTE-Advanced Pro network, or in a gNB or TRP in a 5G, NR, or IoT network.
[0029] In some implementations, each of devices 210 and 220 may be implemented as one or more integrated circuit (IC) chips, such as, but not limited to, 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 all the above-described embodiments, each of devices 210 and 220 may be implemented as a network device or a user equipment. Each of devices 210 and 220 may include... Figure 2 At least some of the components shown, such as processor 212 and processor 222. Each of devices 210 and 220 may also include one or more other components unrelated to the proposed solutions of this disclosure (e.g., internal power supply, display device, and / or user interface device), therefore, for simplicity and brevity, Figure 2 These components are not shown in the document, nor are they described below.
[0030] In one aspect, each of processors 212 and 222 may be implemented as one or more single-core processors, one or more multi-core processors, or one or more CISC or RISC processors. That is, although the singular term "processor" is used herein to refer to processors 212 and 222, in some implementations each of processors 212 and 222 may include multiple processors, while in other implementations it is a single processor, consistent with this disclosure. In another aspect, each of processors 212 and 222 may be implemented in hardware (and optionally firmware) comprising, for example, but not limited to, 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 varactor diodes, these electronic components being configured and arranged to achieve a specific purpose consistent with this disclosure. In other words, in at least some implementations, each of processors 212 and 222 is a dedicated machine specifically designed, arranged, and configured to perform specific tasks, including those involving processing equivalent independent non-public networks for localized services in mobile communications, consistent with various implementations of this disclosure.
[0031] In some implementations, device 210 may further include a transceiver 216 coupled to processor 212. Transceiver 216 can wirelessly transmit and receive data. In some implementations, transceiver 216 can wirelessly communicate with different types of wireless networks using different radio access technologies (RATs). In some implementations, transceiver 216 may be equipped with multiple antenna ports (not shown), 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 communication. In some implementations, device 220 may further 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 can wirelessly communicate with different types of user equipment / wireless networks using different RATs. In some implementations, transceiver 226 may be equipped with multiple antenna ports (not shown), for example, four antenna ports. In other words, transceiver 226 can be equipped with multiple transmit antennas and multiple receive antennas for MIMO wireless communication.
[0032] In some implementations, device 210 may further include a memory 214 coupled to and accessible by processor 212, wherein data is stored. In some implementations, device 220 may further include a memory 224 coupled to and accessible by processor 222, wherein data is stored. Each of memory 214 and memory 224 may include a 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 read-only memory (ROM), such as a mask ROM, programmable ROM (PROM), erasable programmable ROM (EPROM), and / or electrically erasable programmable ROM (EEPROM). Alternatively, each of memories 214 and 224 may include a non-volatile random access memory (NVRAM), such as flash memory, solid-state memory, ferroelectric RAM (FeRAM), magnetoresistive RAM (MRAM), and / or phase-change memory.
[0033] Each of devices 210 and 220 may be a communication entity capable of communicating with each other using various proposed schemes of this disclosure. For illustrative purposes and without limitation, the following description, within the context of example procedure 300, provides the capabilities of device 210 as a user equipment (e.g., user equipment 110) and device 220 as a network node (e.g., network node 125) of a network (e.g., a wireless network 120 as a 5G / NR mobile network).
[0034] Example process
[0035] Figure 3An example process 300 according to an implementation of this disclosure is shown. Process 300 may represent one aspect of implementing the various proposed designs, concepts, schemes, systems, and methods described above. More specifically, process 300 may represent one aspect of proposed concepts and schemes related to processing an equivalent independent non-public network for localized services in mobile communications according to this disclosure. Process 300 may include one or more operations, actions, or functions illustrated by one or more blocks 310, 320, and 330. Although shown as discrete blocks, the individual blocks of process 300 may be divided into more blocks, merged into fewer blocks, or omitted, depending on the desired implementation. Furthermore, the blocks / sub-blocks of process 300 may be arranged according to... Figure 3 The execution may proceed in the order shown, or in a different order. Furthermore, one or more blocks / subblocks of process 300 may be executed repeatedly or iteratively. Process 300 may be implemented by or in devices 210 and 220, and any variations thereof. For illustrative purposes only and without limitation, process 300 is described below in the context of device 210 as a user equipment (e.g., user equipment 110) and device 220 as a communication entity (e.g., a network node or base station, such as network node 125). Process 300 may begin with block 310.
[0036] In block 310, process 300 may involve the processor 212 of device 210 sending a registration request message via transceiver 216 to a first independent non-public network (e.g., device 220 as network node 125 of wireless network 120 as the first independent non-public network) having a first independent non-public network identifier. The encoded symbol identifier bit of the fifth-generation mobility management capability information element of the registration request message may be set to "support equivalent independent non-public network". Process 300 may proceed from 310 to 320.
[0037] In block 320, process 300 may involve processor 212 receiving, via transceiver 216, a registration acceptance message containing a list of equivalent independent non-public networks, which includes identifiers of a second independent non-public network. Process 300 may proceed from 320 to 330.
[0038] In block 330, process 300 may involve processor 212 removing a second independent non-public network identifier from the equivalent independent non-public network list when certain conditions are met.
[0039] In some implementations, this condition may involve a second independent non-public network identifier already being listed in the "Permanently Prohibited Independent Non-Public Networks" list.
[0040] In some implementations, this condition may involve a second independent non-public network identifier already being listed in the "Temporarily Prohibited Independent Non-Public Networks" list.
[0041] In some implementations, this condition may involve a second independent non-public network identifier being on the "Temporarily Prohibited Independent Non-Public Networks for Access to Localized Services in Independent Non-Public Networks" list.
[0042] In some implementations, this condition may involve a second independent non-public network identifier being on the "Permanently Prohibited Independent Non-Public Networks for Access to Localized Services in Independent Non-Public Networks" list.
[0043] Additional notes
[0044] The described topics may sometimes demonstrate different components contained within or connected to different other components. It should be understood that the architectures depicted are merely examples, and many other architectures can actually be implemented to achieve the same functionality. Conceptually, any arrangement of components to achieve the same functionality is effectively “associated” to achieve the desired function. Therefore, any two components combined in this document to achieve a particular function can be considered “interrelated” to achieve the desired function, regardless of the architecture or intermediate components. Similarly, any two components so associated can also be considered “operably connected” or “operably coupled” to each other to achieve the desired function, and any two components that can be so associated can also be considered “operably coupled” to each other to achieve the desired function. Specific examples of operably coupled include, but are not limited to, physically matable and / or physically interactive components and / or wirelessly interactive and / or logically interactive components.
[0045] Furthermore, regarding the use of virtually any plural and / or singular terms in this document, those with technical skills may appropriately translate from plural to singular and / or from singular to plural depending on the context and / or application. For clarity, various singular / plural arrangements may be explicitly listed.
[0046] Furthermore, those skilled in the art will understand that, generally, the terms used herein, especially in appended claims, such as the body of an appended claim, are generally interpreted as “open” terms; for example, the term “comprising” should be interpreted as “comprising but not limited to,” the term “having” should be interpreted as “having at least,” and the term “including” should be interpreted as “including but not limited to,” etc. Those skilled in the art will also understand that if a particular number of claim statements is intentional, such intention will be explicitly stated in the claims, and without such a statement, such intention does not exist. For example, to aid understanding, the following appended claims may contain the use of introductory phrases “at least one” and “one or more” to introduce claim statements. However, the use of these phrases should not be construed as implying that claim statements introduced by the indefinite article “a” or “an” limit any particular claim containing such introductory claim statements to containing only one such statement, even if the same claim includes the introductory phrase “one or more” or “at least one” and indefinite articles such as “a” or “an,” for example, “a” and / or “an” should be interpreted as “at least one” or “one or more”; the same applies to definite articles used to introduce claim statements. Furthermore, even if a specific number of claims is explicitly stated, those skilled in the art will recognize that such a statement should be interpreted as at least the number stated. For example, the simple statement "two statements," without any other modifiers, means at least two statements, or two or more statements. Additionally, in cases where conventions such as "at least one A, B, and C, etc." are used, this structure is generally used in the conventional sense understood by those skilled in the art. For example, "a system having at least one A, B, and C" includes, but is not limited to, systems having only A, only B, only C, A and B together, A and C together, B and C together, and / or A, B, and C together, etc. Similarly, in cases where conventions such as "at least one A, B, or C, etc." are used, this structure is generally used in the conventional sense understood by those skilled in the art. For example, "a system having at least one A, B, or C" includes, but is not limited to, systems having only A, only B, only C, A and B together, A and C together, B and C together, and / or A, B, and C together, etc. Those skilled in the art will also understand that virtually any extractive term and / or phrase presenting two or more alternative terms, whether in the description, claims, or drawings, should be understood to include the possibility of containing one, any, or both terms. For example, the phrase “A or B” will be understood to include the possibility of “A” or “B” or “A and B”.
[0047] As can be seen from the foregoing, the various implementations of this disclosure described herein are for illustrative purposes, and various modifications can be made without departing from the scope and spirit of this disclosure. Therefore, the various implementations disclosed herein are not intended to be limiting, and their true scope and spirit are indicated by the following claims.
Claims
1. A method comprising: A processor of a user equipment sends a registration request message to a first independent non-public network having a first independent non-public network identifier; The processor receives a registration acceptance message from the first independent non-public network containing an equivalent list of independent non-public networks, the equivalent list of independent non-public networks including a second independent non-public network identifier; and The processor removes the second independent non-public network identifier from the equivalent independent non-public network list when a certain condition is met. In this registration request message, a coded symbol identifier bit of a fifth-generation mobility management capability information element is set to support an equivalent independent non-public network.
2. The method of claim 1, wherein the condition includes the second independent non-public network identifier being in a permanently banned independent non-public network list.
3. The method of claim 1, wherein the condition includes the second independent non-public network identifier being in a temporary list of prohibited independent non-public networks.
4. The method of claim 1, wherein the condition includes the second independent non-public network identifier being in a temporary list of prohibited independent non-public networks for access to localized services in independent non-public networks.
5. The method of claim 1, wherein the condition includes the second independent non-public network identifier being in a permanently banned independent non-public network list for access to localized services in independent non-public networks.
6. An apparatus that can be implemented in a user equipment, comprising: A transceiver configured for wireless communication; as well as A processor, coupled to the transceiver and configured to perform operations, including: The transceiver sends a registration request message to a first independent non-public network having a first independent non-public network identifier. The transceiver receives a registration acceptance message from the first independent non-public network containing an equivalent list of independent non-public networks, the equivalent list of independent non-public networks including a second independent non-public network identifier; and The second independent non-public network identifier is removed from the equivalent independent non-public network list when a certain condition is met. In this registration request message, a coded symbol identifier bit of a fifth-generation mobility management capability information element is set to support an equivalent independent non-public network.
7. The apparatus of claim 6, wherein the condition includes the second independent non-public network identifier being in a permanently banned independent non-public network list.
8. The apparatus of claim 6, wherein the condition includes the second independent non-public network identifier being in a temporary list of prohibited independent non-public networks.
9. The apparatus of claim 6, wherein the condition includes the second independent non-public network identifier being in a temporary list of prohibited independent non-public networks for access to localized services in an independent non-public network.
10. The apparatus of claim 6, wherein the condition includes the second independent non-public network identifier being in a permanently banned independent non-public network list for access to localized services in independent non-public networks.