CELL RESELECTION METHOD IN A NON-PUBLIC NETWORK AND RELATED DEVICE

Abstract

The present invention relates to a method for reselecting a cell in a non-public network (NPN) for a user equipment (UE). The method includes receiving, from a first cell via a first System Information Block 1 (SIB1), a first network identity associated with a first indication; receiving, from a second cell via a second SIB1, a second network identity associated with a second indication; selecting one of the first network identity and the second network identity; determining whether the first indication is present and whether the first network identity is selected by the UE; determining the first cell as prohibited from cell reselection when the first indication is present but the first network identity is not selected by the UE; and determining the first cell as a candidate cell for cell reselection when the first indication is present and the first network identity is selected by the UE.

Description

CELL RESELECTION METHOD IN A NON-PUBLIC NETWORK AND RELATED DEVICE Field of Invention In general, this description relates to wireless communications and, more specifically, to a cell reselection method in a non-public network (NPN) and a related device. Background of the Invention With the tremendous growth in the number of connected devices and the rapid increase in user / network traffic volume, several efforts have been made to improve different aspects of wireless communication for the next generation wireless communication system, such as fifth generation (5G) New Radio (NR), by improving data rate, latency, reliability, and mobility. The 5G NR system is designed to provide flexibility and configurability to optimize network types and services and adapt to various use cases, such as enhanced mobile broadband (eMBB), massive machine-type communication (MMTC), and ultra-reliable and ultra-reliable low-latency communication (URLLC). However, as demand continues to increase Ref. 338050 of radio access, there is a need for additional improvements in wireless communication for the next generation wireless communication system. Brief Description of the Invention This description provides a method for reselecting cells in a non-public network (NPN) and a related device. According to one aspect of the present description, a cell reselection method is provided for a user equipment (UE) on an NPN. The method includes receiving, from a first cell via a first System Information Block 1 (SIB1), a first information element that includes a first network identity associated with a first indication; receiving, from a second cell via a second SIB1, a second information element that includes a second network identity associated with a second indication; selecting one of the first network identity and the second network identity; determining whether the first indication is present in the first information element and whether the first network identity is selected by the UE; and determining the first cell as prohibited from cell reselection when the first indication is present.but the first network identity is not selected by the UE, and determine the first cell as a candidate cell for cell reselection when the first indication is present and the first network identity is selected by the UE, wherein the first indication is used to indicate whether the first cell supports Integrated Access and Return Network (IAB) functionality, and the first network identity is different from the second network identity. According to another aspect of the present description, a UE is provided for performing cell reselection on an NPN. The UE includes a processor configured to execute a computer executable program, and memory coupled to the processor and configured to store the computer executable program, wherein the computer executable program instructs the processor to perform the method described above of executing cell reselection on an NPN. Brief Description of the Figures The aspects of this description are best understood from the following detailed description when read in conjunction with the accompanying figures. Several features are not drawn to scale. The dimensions of several features may be arbitrarily enlarged or reduced for clarity. Figure 1A is a schematic diagram illustrating an integrated access and backhaul (IAB) architecture that includes IAB nodes with an independent mode (SA), according to an implementation of the present description. Figure IB is a schematic diagram illustrating an IAB architecture that includes IAB nodes with a dual E-UTRA-NR (EN-DC) connectivity mode, according to an implementation of the present description. Figure 2 is a schematic diagram illustrating an IAB architecture with a 5G System (5GS), according to an implementation of the present description. Figure 3 is a flowchart illustrating a cell reselection method performed by a UE in a non-public network (NPN), according to an implementation of the present description. Figure 4 is a block diagram illustrating a node for wireless communication, according to an implementation of the present description. Detailed Description of the Invention The following description contains specific information related to exemplary implementations in this description. The figures and their accompanying detailed descriptions are directed toward exemplary implementations. However, this description is not limited to these exemplary implementations. Other variations and implementations of this description will be presented for those skilled in the art. Unless otherwise indicated, similar or corresponding elements in the figures may be indicated by the same or corresponding reference numbers. Furthermore, the figures and illustrations are generally not to scale and are not intended to correspond to actual relative dimensions. For consistency and ease of understanding, similar features are identified (although not shown in some examples) by reference designators in the example figures. However, features in different implementations may differ in other aspects and are therefore not strictly limited to what is shown in the figures. The phrases "in one implementation" and "in some implementations" may each refer to one or more identical or different implementations. The term "coupled" is defined as connected, either directly or indirectly through intermediate components, and is not necessarily limited to physical connections. The term "comprising" may mean that it includes, but is not necessarily limited to, and specifically indicates an open inclusion or membership in the combination, group, series, and equivalents described. The term "and / or" herein is simply an associative relation used to describe associated objects and represents three possible relationships. For example, A and / or B can represent that: A exists alone, A and B exist simultaneously, and B exists alone. A and / or B and / or C can represent that at least one of A, B, and C exists; A and B exist simultaneously; A and C exist simultaneously; B and C exist simultaneously; and A, B, and C exist simultaneously. Furthermore, the / character used herein generally represents that the preceding and following associated objects are in an "or" relationship. Furthermore, two or more of the following paragraphs, (sub)bullets, points, actions, behaviors, terms, alternatives, examples, or claims in this description may be logically, reasonably, and appropriately combined to form a specific method. Any sentence, paragraph, (sub)bullet, point, action, behavior, term, or claim in this description may be implemented independently and separately to form a specific method. Dependence, for example, on, more specifically, preferably, on a modality, on an implementation, on an alternative, in this description may refer to only one possible example that would not restrict the specific method. For a non-limiting explanation, specific details, such as functional entities, techniques, protocols, standards, and the like, are presented to provide an understanding of the described technology. In other examples, detailed descriptions of well-known methods, technologies, systems, and architectures are omitted to avoid obscuring the present description with unnecessary detail. Those experienced in the field will recognize that any described network function or algorithm can be implemented using physical elements (hardware), programming elements (software), or a combination of both. The described functions may correspond to modules, which can be programming elements, physical elements, physical programs (firmware), or any combination thereof. The implementation of programming elements may comprise computer-executable instructions stored on a computer-readable medium, such as memory or other types of storage devices. For example, one or more microprocessors or general-purpose computers with communications processing capabilities can be programmed with the corresponding executable instructions and perform the described network functions or algorithms.Microprocessors or general-purpose computers may consist of application-specific integrated circuits (ASICs), programmable logic arrays, and / or use one or more digital signal processors (DSPs). Although some of the implementations described are directed at programming elements and / or elements installed and running on physical computer components, alternative implementations such as physical programs or physical components, or a combination of physical and programming elements, are nonetheless within the scope of this description. Computer-readable media may include, but are not limited to, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, compact disc (CD), read-only memory (CD-ROM), magnetic cassettes, magnetic tape, magnetic disk storage, or any other equivalent medium capable of storing computer-readable instructions. A radio communication network architecture (for example, a Long-Term Evolution (LTE) system, an LTE-Advanced (LTE-A) system, an LTE-Advanced Pro system, or a New Radio (NR) system) typically includes at least one base station (BS), at least one unit (UE), and one or more optional network elements that provide connectivity to a network. The UE can communicate with the network (for example, a core network (CN), an evolved packet core (EPC), an evolved universal terrestrial radio access network (E-UTRAN), a next-generation core (NGC), a 5G core (5GC), or the Internet) via a radio access network (RAN) established by one or more BSs. A UE, as defined herein, may include, but is not limited to, a mobile station, a mobile terminal or device, or a user communication radio terminal. For example, a UE may be portable radio equipment, including, but not limited to, a mobile phone, tablet, handheld device, sensor, or personal digital assistant (PDA) with wireless communication capabilities. The UE may be configured to receive and transmit signals over an air interface to one or more cells in a RAN. A BS may include, but is not limited to, a Node B (NB) as in the Universal Mobile Telecommunications System (UMTS), an evolved Node B (eNB) as in LTE-A, a Radio Network Controller (RNC) as in UMTS, a Base Station Controller (BSC) as in the Global System for Mobile Communications (GSM) / Enhanced GSM Data Rates for GSM Evolution (EDGE) RAN (GERAN), a next-generation eNB (ng-eNB) as in an evolved universal terrestrial radio access (E-UTRA) BS in conjunction with 5GC, a last-generation Node B (gNB) as in 5G-RAN (or in the 5G access network (5G-AN)), and any other apparatus capable of controlling communication over radio and manage radio resources within a cell.The BS can connect to serve one or more UEs via a radio interface to the network. A base station (BS) can be configured to provide communication services in accordance with at least one of the following Radio Access Technologies (RATs): Worldwide Interoperability for Microwave Access (WiMAX), GSM (often referred to as 2G), GERAN, General Packet Radio Service (GRPS), UMTS (often referred to as 3G) in accordance with Wideband Code Division Multiple Access (W-CDMA), High-Speed ​​Packet Access (HSPA), LTE, LTE-A, Enhanced LTE (eLTE), NR (often referred to as 5G), and / or LTE-A Pro. However, the scope of this description is not limited to these protocols. The base station (BS) can function to provide radio coverage to a specific geographic area using a plurality of cells that form the regional area network (RAN). The BS can support cell operations. Each cell can function to provide services to at least one user unit (UE) within its radio coverage. More specifically, each cell (often referred to as a service cell) can provide services to one or more UEs within its radio coverage (for example, each cell schedules downlink (DL) and, optionally, uplink (UL) resources to at least one UE within its radio coverage for DL ​​and optionally UL packet transmissions). The BS can communicate with one or more UEs in the radio communication system through the plurality of cells. A cell can allocate Sidelink (SL) resources to support Proximity Service (ProSe), LTE SL services, and LTE / NR Vehicle-to-Everything (V2X) services. Each cell can have overlapping coverage areas with other cells. In multi-RAT dual connectivity (MR-DC) scenarios, the primary cell of a Master Cell Group (MCG) or a Secondary Cell Group (SCG) can be called a Special Cell (SpCell). A Primary Cell (PCell) can refer to a SpCell of an MCG. A Primary Cell of an SCG (PSCell) can refer to a SpCell of an SCG. An MCG can refer to a group of service cells associated with the Master Node (MN), comprising a SpCell and, optionally, one or more Secondary Cells (SCells).An SCG can refer to a group of service cells associated with the Secondary Node (SN), comprising SpCell and, optionally, one or more SCells. As described above, the NR framework structure supports flexible configurations to accommodate various next-generation communication requirements (e.g., 5G), such as eMBB, mMTC, and URLLC, while meeting high reliability, high data rate, and low latency requirements. Orthogonal frequency-division multiplexing (OFDM) technology, as agreed upon in the Third Generation Partnership Project (3GPP), can serve as the baseline for an NR waveform. Scalable OFDM numerology, such as adaptive subcarrier spacing, channel bandwidth, and cyclic prefix (CP), can also be used. Furthermore, two coding schemes are applicable for NR: (1) Low-Density Parity Check (LDPC) code and (2) polar code. The coding scheme can be configured based on channel conditions and / or service applications. Furthermore, within a single NR frame transmission time interval, at least DL transmission data, a guard period, and UL transmission data must be included. The respective portions of the DL transmission data, the guard period, and the UL transmission data should also be configurable, for example, based on the NR network dynamics. An out-of-box (OO / O) SL resource can also be provided through an NR frame to support ProSe or V2X services. In order to meet the low latency and high reliability requirements for the vertical industry and support 5G Local Area Network (LAN) type service, a dedicated wireless network (e.g., a private network) is being considered for inclusion in the next generation cellular network. A private network (e.g., a non-public network (NPN)) can support vertical industry and LAN services. Private networks can be classified as either a standalone non-public network (SNPN) or a non-public network integrated into a public network (PNI-NPN). The 5G system is enhanced to support NPNs. Two network identifiers are used for NPNs: Network Identifier (NID) and Closed Access Group (CAG) ID. The 5G Radio Access Network (RAN) can also implement NPNs by enhancing features such as NPN identification, discovery, selection / reselection, access control, and mobility restrictions. One of the potential technologies intended to enable future cellular network deployment scenarios and applications is support for wireless backhaul and relay links. This allows for the flexible and very dense deployment of cells (e.g., NR cells) without the need to proportionally densify the transport network. The wireless backhaul and relay can utilize massive Multi-Input Multi-Output (MIMO) or multi-beam systems. The benefits of integrated access and backhaul (IAB) are crucial during network deployment and the initial network growth phase. To leverage these benefits, IAB must be available when NR deployment occurs. Enabling IAB functionality in NPN deployments is considered a possible scenario for future cellular networks. In an NPN scenario, a UE can be configured as an SNPN access mode UE or a non-SNPN access mode UE (for example, a UE that is not in SNPN access mode) by the UE's NAS layer, by the camped / server cell, or by preconfiguration. A cell can be configured as an SNPN cell, a CAG cell, a public land mobile network (PLMN) cell, a cell that supports at least SNPN deployments, a cell that supports at least PNI-NPN deployments, a cell that supports at least PLMN deployments, a cell that supports at least SNPN and PNI-NPN deployments, a cell that supports at least SNPN and PLMN deployments, a cell that supports at least PNI-NPN and PLMN deployments, or a cell that supports SNPN, PNI-NPN, and PLMN deployments. In an IAB scenario, a UE can be configured as a UE with IAB functionality and a UE without IAB functionality. A cell can be configured as a cell with IAB functionality and a cell without IAB functionality. Multiple PLMNs can operate on unlicensed spectrum. Multiple PLMNs can share the same unlicensed operator. PLMNs can be public or private. Public PLMNs can be (but are not limited to) carriers or virtual operators that provide radio services to public subscribers. Public PLMNs can own licensed spectrum and also support RAT on that licensed spectrum. Private PLMNs can be (but are not limited to) micro-operators, factories, or businesses that provide radio services to their private users (e.g., employees or machines).Public PLMNs can support more deployment scenarios (e.g., carrier aggregation (CA) between the licensed NR band (e.g., PCell) and NR-U (e.g., SCell), dual connectivity (DC) between the licensed LTE band (e.g., PCell) and NR-U (e.g., PSCell), standalone NR-U, an NR cell with DL in the unlicensed band and UL in the licensed band, dual connectivity between the licensed NR band (e.g., PCell) and NR-U (e.g., PSCell)). On the other hand, private PLMNs primarily support (but are not limited to) standalone unlicensed RATs (e.g., standalone NR-U). This description describes a mechanism for a UE that supports IAB and / or NPN perform a cell (re)selection to select / camp in a cell that supports the corresponding IAB and / or NPN. IAB Technology IAB can enable wireless relaying within a RAN (e.g., a next-generation RAN (NG-RAN)). The relay node, called the IAB node, can support both access and backhaul via a RAT (e.g., NR, LTE connected to a 5G Core (5GC), LTE connected to an EPC). In this description, the term NR is used for illustrative purposes. However, the RAT required for IAB is not limited to NR. The NR backhaul termination node on the network side can be called the IAB-donor, representing a base station (e.g., gNB if the RAT is NR, eNB if the RAT is LTE connected to an EPC, ngeNB if the RAT is LTE connected to a 5GC) with additional functionality to support IAB. The backhaul can be presented across one or multiple hops. The IAB architecture is illustrated in Figure 1A and Figure 1B. Figure 1A is a schematic diagram illustrating an IAB architecture that includes IAB nodes with an independent mode (SA), according to an implementation of the present description. In NR SA mode, the IAB donor 10 can be a gNB that supports IAB functionality. A network node (for example, a UE, IAB node 12, or IAB node 14) can connect to 5GC (for example, Access and Mobility Management (AMF) / User Plane Function (UPF)) through the IAB donor 10. Figure IB is a schematic diagram illustrating an IAB architecture that includes IAB nodes with a dual E-UTRA-NR (EN-DC) connectivity mode, according to one implementation of the present description. In one example, in EN-DC mode, donor IAB 100 can be a secondary gNB (SgNB) with IAB functionality. Alternatively, donor IAB 100 can be a master eNB (MeNB) that supports IAB functionality. A network node (for example, a UE, IAB node 102, or IAB node 104) can connect to an EPC (for example, a Mobility Management Entity (MME) / Services Packet Network Gateway (S-PGW)) through donor IAB 100.Alternatively, a network node (e.g., a UE, IABnode 102 or IABnode 104) can connect to 5GC (e.g., AMF / UPF) via IAB-donor 100 (e.g., in NG RAN E-UTRA-NR Dual Connectivity Mode (NGEN-DC)). In another example, in NR-NR dual connectivity mode (NR-DC), the IAB donor can be a gNB master (MgNB) that supports IAB functionality. Alternatively, the IAB donor can be an SgNB that supports IAB functionality. A network node (e.g., a UE or an IAB node) can connect to 5GC (e.g., AMF / UPF) through the IAB donor. In other examples, in NR-EUTRA (NE-DC) dual connectivity mode, the IAB donor can be an MgNB that supports IAB functionality. Alternatively, the IAB donor can be a SeNB that supports IAB functionality. A network node (e.g., a UE or an IAB node) can connect to 5GC (e.g., AMF / UPF) via the IAB donor. Figure 2 is a schematic diagram illustrating an IAB architecture with a 5G System (5GS), according to an implementation of the present description. The IAB nodes (e.g., gNB donor IAB 20 and IAB nodes 22 and 24) can support gNB Distributed Unit (gNB-DU) functionality (e.g., IAB donor-DU 204, gNB-DU 222, and gNB-DU 242) to terminate the NR access interface to UE 25-27 and the next-hop IAB nodes (e.g., IAB nodes 22 and 24), and to terminate the EL protocol to gNB Central Unit (gNB-CU) functionality (e.g., gNB donor IAB donor-CU 202). The IAB-donor-DU 204, gNB-DU 222 and gNB-DU 242 are also referred to as IAB-DU. As illustrated in Figure 2, the IAB architecture is described with two return network hops when connected to 5GC. For example, the gNB-DU 222 and 242 of the nodes IAB 22 and 24 are responsible for providing NR Uu access to UE 26 and 27 and to secondary IAB nodes (e.g., IAB node 24 is a secondary IAB node for IAB node 22). gNB-CU functionality (e.g., IAB-donor-CU 202) can be implemented on the IAB-donor gNB 20, which controls the gNBDU 222 and 242 of IAB nodes 22 and 24 via the El interface. IAB nodes 22 and 24 can be considered normal gNB nodes for UE 26-27, and other IAB nodes (e.g., IAB donor gNB 20) can enable UE 25-27 to connect to the 5GC (or EPC). In addition to the gNB-DU functionality, IAB nodes 22 and 24 can support a subset of the UE functionality (e.g., IAB-UE 224 and 244), which may be termed IAB Mobile Termination (IAB-MT) and each includes a physical layer, a layer-2, a Radio Resource Control (RRC) and a Non-Access Stratum Functionality (NAS) to connect to the gNB-DU (e.g., IAB-donor-DU 204, gNB-DU 222 and gNB-DU 242) of another IAB node (e.g., IAB nodes 22 and 24) or the IAB donor (e.g., IAB donor gNB 20), to connect to the gNB-CU (e.g., IAB-donor-CU 202) of the IAB donor (e.g., IAB donor gNB 20), and to the core network. All the functions of a UE can be used as an IABMT. For example, the IAB-MT can access the network using one network node or using two different network nodes with ENDC and NR-DC modes. In (NG)EN-DC mode, return network traffic through the E-UTRA radio interface may or may not be supported. The IAB node can access the network using SA mode or EN-DC mode, but is not limited to these. For example, the IAB node can access the network using (NG)EN-DC, NR-DC, or NE-DC modes. In EN-DC mode, the IAB node can connect via E-UTRA to a MeNB (or SgNB), and the donor IAB terminates as an X2-C SgNB. In EN-DC mode, a secondary node (SN) can transmit system information to allow IAB-MT to access the SN. As illustrated in Figure 2, the IAB node can enable in-band and out-of-band wireless retransmission of NR Uu access traffic over NR Uu backlinks. These Uu backlinks can exist between the IAB node and a gNB called the IAB donor, or between the IAB node and another IAB node. The portion of the IAB node that supports the (Uu) interface to the IAB donor or another primary IAB node (to manage backlink connectivity with the PLMN or SNPN with which the IAB node is registered) is called the IAB-UE.The IAB-UE function behaves like a UE and reuses UE procedures to connect to: (1) the gNB-DU on a parent IAB node or IAB donor for access and backhaul, (2) the gNB-CU on the IAB-donor via RRC for access and backhaul link control, (3) 5GC (e.g., AME) via NAS, and (4) the operations, administration, and maintenance (OAM) system via a packet data unit (PDU) session or packet data network (PDN) connection. The IAB-UE can connect to a 5GC over NR (using SA mode, NR-DC mode, or NGEN-DC mode). Alternatively, the IAB-UE can connect to an EPC (using EN-DC mode) (for example, via the SgNB network). The UE served by the IAB node can operate in the same or different modes as the IAB node. For example, the IAB donor can be a gNB with IAB functionality if the IAB-UE connects to the 5GC over NR (using SA mode). Alternatively, the IAB donor can be an SgNB with IAB functionality in EN-DC mode if the IAB-UE connects to the EPC via EN-DC mode. On the other hand, a UE can operate in PLMN access mode (for example, not in SNPN access mode) or in SNPN access mode. The UE can determine whether it is in PLMN access mode or SNPN access mode based on at least one of the following conditions: Condition 1: The UE (e.g., the UE's NAS entity) can determine based on the NAS's (pre)configuration; Condition 2: The UE may be (pre)configured to be in PLMN access mode (e.g., not in SNPN access mode) or in SNPN access mode; Condition 3: The UE can switch from PLMN access mode (e.g., not in SNPN access mode) to access mode SNPN by the EU (e.g., the EU's NAS entity) or by the duty / camping cell; and Condition 4: The UE can switch from SNPN access mode to PLMN access mode (e.g., non-SNPN access mode) by the UE (e.g., the UE's ÑAS entity) or by the duty / camping cell. If a UE is in PLMN access mode (or if a UE is not in SNPN access mode), the UE can perform PLMN selection. For UEs not operating in SNPN access mode (or for UEs operating in PLMN access mode), the UE (e.g., the UE's NAS entity) can maintain a list of PLMNs in priority order. For each PLMN (selected / registered), the UE (e.g., the UE's NAS entity) can set the associated RAT(s). The UE (e.g., the UE's AS entity) can perform cell measurement for PLMN selection. The UE (e.g., the UE's AS entity) can synchronize with a broadcast channel to identify PLMNs. The UE (e.g., the UE's AS entity) can search for available PLMNs. The UE's AS entity can report available PLMNs to the UE's NAS entity.The EU AS entity may report on available PLMNs and / or any CAG IDs associated with RAT(s) linked to the EU ÑAS entity, either upon request from the EU ÑAS entity or independently. The EU ÑAS entity may evaluate reports of available PLMNs and any associated CAG IDs from the entity. The UE AS for PLMN selection. The UE NAS entity may maintain a list of equivalent PLMN identities. The UE NAS entity may select a PLMN automatically (e.g., the UE may select automatically) or manually (e.g., the UE may not be authorized to select automatically but may select under certain predefined or preconfigured requirements / conditions) based on the reported available PLMN(s) and / or reported CAG ID(s) and request the UE AS entity to select a (suitable / acceptable) cell belonging to this PLMN. In one example, the UE's ÑAS entity can indicate the selected PLMN (or a PLMN ID that identifies the selected PLMN) to the UE's AS entity (for example, without considering the available PLMNs). Therefore, the UE's AS entity can perform a cell (re)selection procedure and select a suitable / acceptable cell that belongs to the selected PLMN. If the UE is in PLMN access mode (or if the UE is not in SNPN access mode), the UE can perform PLMN selection and CAG selection. For UEs that do not operate in SNPN access mode (or for UEs that operate in PLMN access mode) and support manual CAG selection (for example, the UE can (re)select a CAG cell using the manual CAG selection method, whereby it is able to manually control the UE by selecting an NPN hosted by this PLMN that the UE may not be authorized to select automatically), the UE's NAS entity can provide a request to the UE's AS entity to search for available CAG(s). The UE's AS entity can search for cells broadcasting CAG ID(s) in the System Information Block (SIB) (for example, in SIB1). The UE's AS entity can read the Human Readable Network Name (HRNN) for each CAG ID if a cell broadcasting a CAG ID is found.The UE AS entity can report the CAG ID(s) of the found cell by transmitting the CAG ID along with the associated HRNN and PLMN to the UE ÑAS entity. The UE ÑAS entity can evaluate available CAG reports from the UE AS entity for CAG selection. The UE ÑAS entity can select the CAG ID based on the available CAG reports. The UE ÑAS entity can report the selected / registered CAG ID to the UE AS entity. A selected CAG is identified by the selected CAG ID, and a registered CAG is identified by the registered CAG ID. The UE AS entity can select any acceptable or suitable cell belonging to the selected CAG and transmit an indication (for example, indicating that access for the registration procedure is possible) to the UE ÑAS entity. In one example, the UE's ÑAS entity can indicate a selected PLMN (or a PLMN ID that identifies the selected PLMN) and / or selected CAG (or a CAG ID that identifies the selected CAG) to the UE's AS entity (for example, without considering the available PLMNs / CAGs). The UE's AS entity can then perform a cell (re)selection procedure and select a suitable / acceptable cell belonging to the selected PLMN and / or the selected CAG. If the UE is in SNPN access mode, it can select SNPNs. For UEs operating in SNPN access mode, the UE (e.g., the UE's NAS entity) can maintain a list of SNPNs. The UE's NAS entity can automatically or manually select an SNPN and request the UE's AS entity to select a cell belonging to that SNPN. The UE's NAS entity can evaluate available SNPN reports from the UE's AS entity for SNPN selection. The UE (e.g., the UE's NAS entity) can establish associated RAT(s) for the corresponding SNPN. The UE (e.g., the UE's AS entity) can search for available SNPNs by considering the cells corresponding to the associated RAT(s). Alternatively, the UE (e.g., the UE's NAS entity) can consider the associated RAT for the corresponding SNPN to be NR (Not Relevant). The UE (e.g., the UE's AS entity) can search for available SNPNs by considering the NR cells.The UE (e.g., the UE's AS entity) can perform a cell measurement to support SNPN selection. The UE (e.g., the UE's AS entity) can synchronize with a broadcast channel to identify SNPNs. The UE's AS entity can automatically report available SNPNs to the UE's NAS entity. The UE's AS entity can report available SNPNs, along with the associated HRNN (if available), to the UE's NAS entity based on a request from the UE's NAS entity. The UE (e.g., the UE's NAS entity) can select (or register) an SNPN. The UE's NAS entity can report the selected (or registered) SNPN ID to the UE's AS entity. The selected SNPN ID can identify the selected SNPN, and the registered SNPN ID can identify the registered SNPN. In one example, the UE's NAS entity can indicate a selected or registered SNPN (for example, an SNPN ID that identifies the selected SNPN or a registered SNPN ID that identifies the registered SNPN) to the UE's AS entity (for example, without considering available SNPNs). The UE's AS entity can then perform a cell (re)selection procedure and select a suitable / acceptable cell belonging to the selected SNPN. After the UE's AS entity receives the selected / registered SNPN ID, the UE's AS entity can perform a cell (re)selection procedure. Therefore, the UE in the RRC_IDLE / RRC_INACTIVE state can be assigned to a suitable cell as a result of the cell (re)selection procedure. During the cell (re)selection procedure, the UE in the RRC_IDLE / RRC_INACTIVE state can receive and read system information (e.g., MIB, SIB1) emitted by a candidate cell. Based on the system information emitted by the candidate cell, the UE in the RRC_IDLE / RRC_INACTIVE state can determine whether the UE is excluded from the corresponding candidate cell. The system information can indicate whether the cell supports IAB functionality for a corresponding PLMN / SNPN and / or whether the cell supports NPN functionality.Different UEs in RRC_IDLE / RRC_INACTIVE state (e.g., if the UE supports NPN functionality, if the UE supports IAB functionality) can perform different actions according to system information. In this description, system information (e.g., information implicitly or explicitly stated in the system information) may include (but is not limited to) a first indication and / or a second indication. The UE may determine whether the cell is prohibited for the UE or whether the cell is a candidate cell for the cell (re)selection procedure based on the first indication and / or the second indication. The UE may determine whether the cell is prohibited for the UE or whether the cell is a candidate cell for the cell (re)selection procedure based on the two indications sequentially or in parallel. In this description, a UE may refer to (but is not limited to) a normal UE, an IAB-UE, an IAB-MT, an NPN-capable UE, and / or a non-NPN-capable UE. A cell may refer to (but is not limited to) a normal cell, a normal BS, an IAB node, a gNB-DU, a gNB-CU, an IAB donor, a cell with IAB functionality enabled to perform IAB-related functionality, a cell with IAB functionality that is not enabled to perform IAB-related functionality, a cell without IAB functionality, an SNPN-compliant cell, a PNI-NPN-compliant cell, and / or a cell that is compatible with at least one of SNPN, PNI-NPN, and PLMN. IAB support on NPN The UE can determine whether it is excluded from a cell after the UE receives a first indication (for example, a support information element (IE) iab) from the cell. The format of the first indication can be a Boolean indicator, ENUMERATED {true}, or ENUMERATED {true, false}. The UE can read the SIB1 received from the cell and receive the cell's first indication via SIB1. The first indication may be associated with an identity and the identity may identify a network (e.g., a first network identity). In one example, the first indication may be associated with a PLMN ID. The PLMN ID may identify a PLMN or a PNI-NPN and / or an SNPN. For example, the first indication may be included in an IE, where the IE includes information associated with the PLMN ID. For example, the first indication can be included in an IE (e.g., NPN-IdentityInfo IE), where the IE includes information associated with an NPN (e.g., PNI-NPN, SNPN) and includes at least one NPN identity (e.g., a PNI-NPN ID, an SNPN ID). The PNI-NPN ID can include a PLMN ID and at least one CAG ID. The SNPN identity can include a PLMN ID and at least one NID. At least one NPN identity can identify the NPN. The first indication can also be included in an IE, where the IE includes information associated with a PLMN ID that identifies a PNI-NPN. Alternatively, the first indication can also be included in an IE, where the IE includes information associated with a PLMN ID that identifies an SNPN. In one example, the first indication might be associated with an SNPN ID. The SNPN ID can identify an SNPN. For example, the first indication can be included in an IE (e.g., NPN-IdentityInfo IE), where the IE includes information associated with an NPN (e.g., PNI-NPN, SNPN) and includes at least one NPN identity (e.g., a PNI-NPN ID, an SNPN ID). The PNI-NPN ID can include a PLMN ID and at least one CAG ID. The SNPN identity can include a PLMN ID and at least one NID. At least one NPN identity can identify the NPN. In this case, the NPN identity can be the SNPN identity. In one example, the first indication may be associated with a NID. The NID may identify an SNPN. For example, the first indication may be included in an IE in which the IE includes information associated with the NID. In one example, the first indication may be associated with a PNI-NPN ID. The PNI-NPN ID can identify a PNI-NPN and / or CAG cell. For example, the first indication can be included in an IE (e.g., NPN-IdentityInfo IE), where the IE includes information associated with an NPN (e.g., PNI-NPN, SNPN) and includes at least one NPN identity (e.g., a PNI-NPN ID, an SNPN ID). The PNI-NPN ID can include a PLMN ID and at least one CAG ID. The SNPN identity can include a PLMN ID and at least one NID. At least one NPN identity can identify the NPN. In this case, the NPN identity can be the PNI-NPN ID. In one example, the first indication may be associated with a CAG ID. The CAG ID can identify a PNI-NPN and / or CAG cell. For example, the first indication may be included in an IE, where the IE includes information associated with the CAG ID. The first indicator can show whether the cell supports IAB functionality (for example, IAB node support from the cell's perspective) and / or the cell's status with respect to IAB functionality. If the indicator is present (either 1 or {true}) in the IE, the cell supports IAB functionality and can be considered a candidate cell for a cell (re)selection procedure from the UE's perspective. If the indicator is absent (either 0 or {false}) in the IE, the cell may not support IAB functionality and / or can be considered a prohibited cell for IAB (or IAB-MT) nodes (for example, a UE that supports IAB) for the cell (re)selection procedure from the UE's perspective. The first indicator can show whether the cell supports IAB functionality (e.g., IAB node support from the cell's perspective) and NPN functionality (e.g., NPN support from the cell's perspective) and / or the cell's status for IAB and NPN functionality. If the first indicator is present (either 1 or {true}), the cell supports both IAB and NPN functionality and can be considered a candidate cell for a cell (re)selection procedure from the UE's perspective. That is, the cell can be identified as a candidate cell for IAB nodes that support NPN functionality (e.g., a UE with the capability to...). NPN that supports IAB). If the first indication is absent (or 0 or {false}), the cell may not support IAB or NPN functionality and / or the cell may be considered a prohibited cell for the UE perspective cell (re)selection procedure. That is, the cell may be determined as a prohibited cell for IAB nodes that support NPN functionality (for example, an NPN-capable UE that supports IAB) (or IAB-MT). If the UE receives the first indication through system information (e.g., SIB1), the UE can verify if the first indication is associated with the registered (or selected) identity (e.g., PLMN ID, SNPN ID, PNI-NPN ID, NID, CAG ID) that identifies the corresponding network (e.g., PLMN, SNPN, PNI-NPN, CAG cell). If the first indication is not provided (not present or absent) in the IE for the selected PLMN, nor the registered PLMN, nor the PLMN from the equivalent PLMN list, nor the selected SNPN, nor the registered SNPN, nor the SNPN from the equivalent SNPN list, the UE may consider the cell as prohibited (e.g., prohibited for a UE that supports IAB functionality and / or NPN functionality, prohibited for a UE that supports IAB functionality and with a registered / selected SNPN). If the first indication is not provided (not present or absent) in the IE for the selected (or registered) PNI-NPN (or CAG cell), the UE may consider the cell as prohibited (e.g., prohibited for a UE that supports IAB functionality and NPN functionality, except for a UE that supports IAB functionality and CAG functionality). If the first indication is provided (present or included) in the IE for the selected (or registered) SNPN, the UE can consider the cell as a candidate cell for a cell (re)selection procedure. The UE can support IAB functionality and NPN functionality with the SNPN registered (or selected) for the corresponding SNPN. If the indication is provided (present or included) in the IE for the selected (or registered) PLMN / PNI-NPN / CAG, the UE can consider the cell as a candidate cell for a cell (re)selection procedure. The UE can support IAB functionality and NPN functionality with PLMN / PNI-NPN / CAGs registered (or selected) for the corresponding PNINPN / CAG. If the UE considers itself excluded from a cell, the UE may not consider the cell as a candidate cell for the cell (re)selection procedure. If the UE considers itself not excluded from a cell, the UE may consider the cell as a candidate cell for a cell (re)selection procedure. If the first indication is unrelated to the UE, the UE can ignore it when it receives the first indication. For example, if the UE does not function as an IAB node, and / or if the UE does not support IAB functionality, and / or if the UE does not support NPN functionality, the UE can ignore the first indication. A UE that supports IAB and NPN functionality with SNPN registered (or selected) cannot ignore a second indication (e.g., cellReservedforOtherUse) transmitted by a cell through system information (e.g., SIB1) during a cell re-selection procedure. A UE that supports IAB and NPN functionality with PLMN / PNI-NPN / CAG registered (or selected) for PNINPN / CAG cannot ignore a second indication (e.g., cellReservedforOtherUse) transmitted by a cell in system information (e.g., SIB1) during a cell re-selection procedure. The format of the second indication can be a Boolean indicator, ENUMERATED {true}, or ENUMERATED {true, false}. The second indication can be associated with all PLMNs whose PLMN IDs are transmitted in the same system information (e.g., SIB1).The second indication and associated PLMN IDs are broadcast by the cell in the same IE (e.g., IE cellAccessRelatedlnfo). The UE can receive the second indication and associated PLMN IDs via the SIB1 transmission from the cell. A UE that supports IAB functionality and NPN functionality with SNPN registered (or selected) can check the second indication issued by a cell and determine whether the cell is forbidden to the UE or whether the cell may be a candidate cell for a cell (re)selection procedure. If the UE receives the second indication indicating true (or 1), and if the cell does not transmit any CAG ID or NID, the UE can determine that the cell is prohibited. If the UE receives the second indication indicating true (or 1), and if the cell transmits any CAG ID or NID, the UE can determine whether the UE is excluded from the cell based on the first indication. For example, the UE can determine whether the cell is prohibited for the UE or whether the cell might be a candidate cell for a cell (re)selection procedure based on the first indication. If the UE receives the second indication indicating that it is not true (or indicates 0 or indicates false), or if the second indication is absent in the IE (e.g., the UE does not receive the second indication, the UE does not receive the IE that includes the second indication), the UE can determine the cell since the cell's state is forbidden. If the UE receives a second indication that is not true (or indicates 0 or false), or if the second indication is absent in the IE (for example, the UE does not receive the second indication, or the UE does not receive the IE that includes the second indication), the UE can determine whether it is excluded from the cell based on the first indication. For example, the UE can determine whether the cell is prohibited for the UE or whether the cell might be a candidate cell for a cell (re)selection procedure based on the first indication. A UE that supports IAB functionality and NPN functionality with registered (or selected) PLMN / PNI-NPN / CAG can check the second indication issued by a cell and determine whether the cell is prohibited for the UE or whether the cell may be a candidate cell for a cell (re)selection procedure. If the UE receives the second indication indicating true (or 1), and if the cell does not transmit any CAG ID or NID, the UE can determine that the cell is prohibited. If the UE receives the second indication indicating true (or 1), and if the cell transmits any CAG ID or NID, the UE can determine whether the UE is excluded from the cell based on the first indication. For example, the UE can determine whether the cell is prohibited for the UE or whether the cell might be a candidate cell for a cell (re)selection procedure based on the first indication. If the UE receives the second indication indicating that it is not true (or indicates 0 or indicates false), or if the second indication is absent in the IE (e.g., the UE does not receive the second indication, the UE does not receive the IE that includes the second indication), the UE can determine the cell since the cell's state is forbidden. If the UE receives the second prompt indicating that it is not true (either it indicates 0 or indicates false), or if the second prompt is absent in the IE (for example, the UE does not receive the second prompt), the UE can determine whether it is excluded from the cell based on the first prompt. For example, the UE can determine whether the cell is prohibited for the UE or whether the cell might be a candidate cell for a cell (re)selection procedure based on the first prompt. EU operating as an IAB node A UE that supports IAB functionality can refer to a UE that operates as an IAB node. Alternatively, a UE that supports IAB functionality can determine on its own (or be determined by the network (NW)) that it is a UE that operates as an IAB node. A UE that supports IAB functionality can also determine on its own (or be determined by the NW) that it is not a UE that operates as an IAB node. For example, the examples mentioned above (e.g., the first indication, the second indication, the cell (re)selection procedure) can be applied to the IAB node. The UE's NAS entity that supports IAB functionality can send a third indication to the UE's AS entity. If the UE's AS entity receives the third indication, it can determine itself as a UE operating as an IAB node based on (receiving) the third indication. The UE's NAS entity that supports IAB functionality can send a third indication to the UE's AS entity. If the third indication is 1, the UE's AS entity can determine itself as a UE operating as an IAB node based on (the content of) the third indication after receiving the third indication. The UE's NAS entity that supports IAB functionality can send a third indication to the UE's AS entity. If the third indication is 0, the UE's AS entity can determine that it is not a UE operating as an IAB node based on (the content of) the third indication after receiving the third indication. The network can transmit a third indication to the UE (the AS entity of the UE). If the UE (the AS entity of the UE) receives the third indication, the UE that supports IAB functionality can determine itself as a UE operating as an IAB node based on the receipt of the third indication. The network can transmit a third indication in downlink control information (DCI) / media access control element (MAC) / RRC message to ML / a / ZUZZ / UI Do / □ (the AS entity of) the UE. If (the AS entity of) the UE receives the third prompt and the third prompt is 1, the UE that supports IAB functionality can determine itself as a UE that operates as an IAB node based on (the content of) the third prompt. The network can transmit a third indication in a DCI / MAC CE / RRC message to the UE's AS entity. If the UE's AS entity receives the third indication and the third indication is 0, the UE that supports IAB functionality can determine that it is not a UE operating as an IAB node based on the content of the third indication. The third indication may be associated with a PLMN / SNPN / PNI-NPN / CAG and / or a RAT (e.g., NR, E-UTRA). The UE can determine for itself whether it is a UE operating as an IAB node based on the third indication (e.g., receipt of the third indication, content of the third indication) and / or based on the PLMN / SNPN / PNI-NPN / CAG (registered / selected) and / or based on the RAT that the UE operates / selects. The third indication may be associated with a PLMN / SNPN / PNI-NPN / CAG. The associated PLMN / SNPN / PNI-NPN / CAG may be predefined (or preconfigured) in the Universal Subscriber Identity Module (USIM) or by the network. For example, the UE's ÑAS entity that supports IAB functionality can send a third associated indication oo / o with at least one PLMN / SNPN / PNI-NPN / CAG to the UE's AS entity. For example, the UE may act as an IAB node (for the associated PLMN / SNPN / PNI-NPN / CAG) (1) after the UE's AS entity receives the third indication, (2) if the third received indication is associated with a PLMN / SNPN / PNI-NPN / CAG that is the UE's registered / selected PLMN / SNPN / PNI-NPN / CAG, and / or (3) if the content of the third indication is 1. The third indication may be associated with a RAT. The associated RAT may be predefined (or preconfigured) in the USIM or by the network. For example, the UE's ÑAS entity that supports IAB functionality can send a third indication associated with at least one RAT to the UE's AS entity. For example, the UE can function as an IAB node (for the associated RAT) (1) after the UE's AS entity receives the third indication, (2) if the third indication received is associated with a RAT that is the RAT selected / instructed by the UE's ÑAS entity to perform PLMN selection and / or cell (re)selection, and / or (3) if the content of the third indication is 1. Terms such as NW, RAN, cell, camped cell, service cell, BS, gNB, eNB, and ng-eNB are used interchangeably. Some of these terms may refer to the same network entity. A service cell can represent, for an RRC_CONNECTED UE not configured with carrier aggregation (CA) or dual connectivity (DC), the main cell. For an RRC CONNECTED UE configured with CA / DC, the term service cells is used to indicate a set of cells comprising the special cell(s) and all secondary cells. The term Special Cell may refer to the PCell of the MCG or the PSCell of the SCG, for DC operation. Otherwise, the term Special Cell may refer to the PCell. The examples mentioned above can be applied to any RAT. The RAT can be (but is not limited to) NR, NRU (NR-unlicensed, NR-based access to unlicensed spectrum), LTE, E-UTRA connected to 5GC, LTE connected to 5GC, E-UTRA connected to EPC, and LTE connected to EPC. The examples mentioned above can be applied to UEs in public networks or in private networks (e.g., non-public network (NPN), standalone NPN (SNPN), or NPN integrated into a public network (PNI-NPN)). The examples mentioned above can be used for licensed frequency and / or unlicensed frequency. System information (SI) may refer to MIB, SIB1, and other SIs. The minimum SI may include MIB and SIB1. Other SIs may refer to SIB3, SIB4, SIB5, and other SIBs (e.g., SNPN-specific SIB or PNI-NPN-specific SIB). Dedicated signaling may refer to (but is not limited to) RRC message(s). For example, an RRC message may include an RRC Configuration Request (Connection) message, an RRC Configuration (Connection) message, an RRC Full Configuration (Connection) message, an RRC Reconfiguration (Connection) message, an RRC Connection Reconfiguration message that includes mobility control information, an RRC Connection Reconfiguration message without mobility control information, an RRC Reconfiguration message that includes synchronized configuration, an RRC Reconfiguration message without synchronized configuration, an RRC Full Reconfiguration (Connection) message, an RRC Resume (Connection) request message, an RRC Resume (Connection) message, a Full Resume (Connection) message, or an RRC Reset (Connection) request message.RRC Reset Message (Connection), RRC Full Reset Message (Connection), RRC Reject Message (Connection), RRC Release Message (Connection), RRC System Information Request Message, UE Support Information Message, UE Capacity Query Message, and UE Capacity Information Message. The RRC message can be a type of dedicated signaling. The UE can receive the RRC message from the network via unicast / broadcast / group broadcast. The UE RRC_CONNECTED, UE RRC_INACTIVE, and UE RRC_IDLE can apply the examples mentioned above. A UE RRC_CONNECTED can be configured with an active BWP with a common search space configured to monitor system information or paging. In general, the examples mentioned above can be applied to both the PCell and the UE. The examples mentioned above can be applied to both the PSCell and the UE. The PSCell (or a child node) can transmit a short message and / or paging downlink control information (DCI) to the UE. The UE can monitor the Physical Downlink Control Channel (PDCCH) monitoring events for paging configured by the PSCell (or a child node). A list of allowed CAGs can represent a list per PLMN of CAG identifiers that the UE can access. A CAG cell can refer to the cell that transmits at least one CAG identifier. A CAG can represent CAG(s) that operate nearby cells, and the CAG(s) can be identified by the CAG ID(s) broadcast by nearby cells. A CAG member cell can represent, for a UE, the cell that transmits an identity of the selected PLMN, the registered PLMN, or equivalent PLMN, and for that PLMN, a CAG identifier belonging to the UE's list of permitted CAGs for that PLMN. A CAG identifier can be used to identify a CAG within a PLMN. A network identifier can be used to identify an SNPN in combination with a PLMN ID. An NPN can refer to a network deployed for non-public use. An NPN-only cell can refer to a cell that is only available for normal services to NPN subscribers. An NPN-capable UE determines that a cell is an NPN-only cell by detecting that the IE cellReservedForOtherUse is set to true while the IE npn-IdentitylnfoList is present in the IE CellAccessRelatedlnfo. A PNI-NPN ID can represent the identifier of a PNI-NPN that comprises a combination of PLMN ID and CAG ID. A registered SNPN may refer to the SNPN in which certain location logging results have occurred. A selected SNPN can refer to the SNPN that has been selected by the NAS (e.g., the UE NAS layer, or the CN NAS layer), either manually or automatically. oo / o An SNPN access mode can represent the mode of operation where the UE only selects SNPN. An SNPN identity can represent the identifier of an SNPN that comprises a combination of PLMN ID and NID. An SNPN-only cell can refer to a cell that is only available for normal services to SNPN subscribers. A UE with NPN capability can refer to the UE that supports CAG (or NPN). A child node can represent the next hop neighbor node of the IAB-DU node, where the child node is also an IAB node. A parent node can represent the next hop neighbor node of the IAB-node-MT, where the parent node can be an IAB node or the IAB-donor-DU. Downstream can represent the direction towards the child node or the UE in the IAB topology. Upstream can represent the direction towards the parent node in the IAB topology. An IAB donor can represent the gNB that provides network access to UEs through a backhaul network and access links. An IAB-DU can represent the gNB-DU functionality supported by the IAB node to terminate the NR access interface to UEs and next-hop IAB nodes, and to terminate 6 the F1 protocol to the gNB-CU functionality, as defined in 3GPP TS 38.401 V16.1.0, of the IAB-donor. An IAB-MT can represent the IAB node function that terminates the Uu interface with the parent node by applying the procedures and behaviors specified for UEs. The IAB-MT function used in the 3GPP Specifications 38 series corresponds to the IAB-UE function defined in 3GPP TS 23.501 vl6.4.0. An IAB node can represent the RAN node that supports NR access links to UE and NR backhaul links to parent and child nodes. The IAB node may or may not support the backhaul over LTE. The multi-hop backhaul network can use an NR (and / or LTE) backhaul link chain between an IAB node and a donor IAB gNB. An NR return network link can represent the NR link used for the return network between an IAB node and an IAB donor gNB, and between IAB nodes in the case of a multi-hop return network. An LTE backhaul link can represent the LTE link used for the backhaul between an IAB node and an IAB donor gNB, and between IAB nodes in the case of a multi-hop backhaul network. Multi-radio dual connectivity (MR-DC) can represent dual connectivity between E-UTRA and NR nodes, or between two NR nodes. MR-DC can include EN-DC, NEDC, NGEN-DC, and NR-DC modes. In MR-DC, a master cell group can represent the group of service cells associated with the Master Node (MN) comprising the SpCell (PCell) and, optionally, one or more SCells. In MR-DC, a master node can represent the radio access node that provides the connection from the control plane to the core network. It can be an eNB Master (in EN-DC mode), an ng-eNB Master (in NGEN-DC mode), or a gNB Master (in NR-DC and NE-DC modes). A group of secondary cells can represent, in MRDC, the group of service cells associated with the secondary node (SN) comprising the SpCell (PSCell) and, optionally, one or more SCells. In MR-DC, a secondary node can represent the radio access node, without a control plane connection to the core network, providing additional resources to the UE. It can be an en-gNB (in EN-DC mode), a secondary ng-eNB (in NEDC mode), or a secondary gNB (in NR-DC and NGEN-DC modes). A MeNB can refer to the master eNB which is an eNB as a master node associated with an MCG in MR-DC mode. An SgNB can refer to the secondary gNB, which is a gNB as a secondary node associated with an SCG in MR-DC mode. The first indication may be associated with NR, LTE connected to EPC, and / or LTE connected to 5GC. The second indication may be associated with NR, LTE connected to EPC, and / or LTE connected to 5GC. The first and second indications may be associated with the same RAT (e.g., NR, LTE connected to EPC, LTE connected to 5GC) or different RATs. The UE that supports a RAT (e.g., IAB functionality via NR and / or NPN functionality via NR, if the RAT is NR) may apply the first indication associated with NR and / or the second indication associated with NR. The UE that supports a RAT may apply or ignore the first indication that is not associated with NR and / or the second indication that is not associated with NR. In the examples mentioned above, if the UE is considered blocked by a cell, or if the UE blocks a cell, the UE can block the cell for a period of time (e.g., 300 s). In other words, the UE may not consider the cell as a candidate cell for cell (re)selection for a period of time (e.g., 300 s). In the examples mentioned above, if the UE changes from SNPN access mode to PLMN access mode (i.e., the UE leaves SNPN access mode and does not operate in SNPN access mode), the UE's (NAS entity) can publish (or delete or discard) the (stored or maintained) list of SNPN ID(s). In the examples mentioned above, if the UE switches from PLMN access mode to SNPN access mode (i.e., the UE enters SNPN access mode from a state in which the UE does not operate in SNPN access mode), (the UE's ÑAS entity may release (or delete or discard) the (stored or maintained) list of PLMN ID(s). DCI can refer to a PDCCH resource with Cyclic Redundancy Check (CRC) encoded by a Radio Network Temporal Identifier (RNTI). The RNTI can be related to IAB. Alternatively, the examples related to DCI can be applied to a physical signal. A MAC CE is a string of bits that is aligned in bits (i.e., a multiple of 8 bits) of length. In the examples mentioned above, if the UE that supports IAB functionality determines itself as an IAB node or operates as an IAB node, and / or if the UE acts as the IAB node, and / or if the UE operates the IAB functions, the UE can transmit an indication to inform the network via dedicated signaling. Figure 3 is a flowchart illustrating a 300 method for a UE to perform a cell reselection on an NPN. In action 302, the UE receives a first information element (for example, NPN-IdentityInfo IE) that includes a first network identity (for example, an SNPN ID or a PNI-NPN ID) associated with a first indication (for example, iab-Support IE) via a SIB1, from a first cell. In action 304, the UE receives a second information element that includes a second network (for example, a PLMN ID) associated with a second indication via a SIB1, from a second cell. In action 306, the UE selects one of the first network identity and one of the second network identity. In action 308, the UE determines whether the first indication is present in the first information element and whether the UE selects the first network identity.In action 310, the UE determines that the first cell is prohibited from cell reselection when the first indication is present, but the UE does not select the first network identity. In action 312, the UE determines the first cell as a candidate cell for cell reselection when the first indication is present, and the UE selects the first network identity. In one example, the first indication is used to indicate whether the first cell supports IAB functionality. In one example, the first network identity is an NPN identity, which can be either an SNPN ID or a PNI-NPN ID. The second network identity is a PLMN ID. Note that the first network identity is different from the second network identity. In one example, the UE determines that the first cell is prohibited for cell reselection when the first indication is absent (or not present) in the first information item. In one example, the UE determines that the first cell is prohibited for cell reselection when the UE selects the first network identity, but the first indication is absent (or not present) in the first information item. In one example, the UE supports IAB functionality. In one example, the UE's ÑAS layer transmits the third indication mentioned above, indicating that the UE supports IAB functionality, to the UE's AS layer, and therefore the UE's AS layer determines that the UE supports IAB functionality when the UE's AS layer receives the third indication from the UE's ÑAS layer. In one example, the third indication is associated with a third network identity which may be a PLMN ID, an SNPN ID, a PNI-NPN ID, a CAG ID, or a NID. In one example, the first indication indicates that the first cell supports IAB functionality when the first indication is present in the first information item. In one example, the UE ignores the first indication associated with the first network identity when the UE does not support IAB functionality. In one example, the UE ignores the second prompt associated with the second network identity when the UE does not select the second network identity. In one example, the first indication indicates that the first cell supports IAB functionality when the first indication is present in the first information item and is set with a first value (e.g., 1 or {true}). Figure 4 is a block diagram illustrating a node 400 for wireless communication, according to an implementation of the present description. As illustrated in Figure 4, node 400 may include a transceiver 420, a processor 426, a memory 428, one or more presentation components 434, and at least one antenna 436. Node 400 may also include a radio frequency (RF) spectrum band module, a BS communications module, a network communications module, a system communications management module, input / output (I / O) ports, I / O components, and a power supply (not illustrated in Figure 4). Each of these components can be in communication with each other, directly or indirectly, through one or more information transfer pathways 440. The node 400 can be a UE or a BS that performs various functions described and illustrated in Figure 3 and examples in this description. The 420 transceiver may include a 422 transmitter (with transmit circuitry) and a 424 receiver (with receive circuitry) and may be configured to transmit and / or receive time and / or frequency resource partitioning information. The 420 transceiver may be configured to transmit in different types of sub-frames and slots, including, but not limited to, usable, unusable, and flexibly usable sub-frames and slot formats. The 420 transceiver may be configured to receive data and control channels. Node 400 can include a variety of computer-readable media. Computer-readable media can be any medium that Node 400 can access and includes both volatile (and non-volatile) and removable (and non-removable) media. Computer-readable media can include computer storage media and communication media. Computer storage media can include volatile (and / or non-volatile) media, as well as removable (and / or non-removable) media, implemented according to any method or technology for information storage, such as computer-readable media. Computer storage media can include RAM, ROM, EPROM, EEPROM, flash memory (or other memory technology), CD-ROM, Digital Versatile Disc (DVD) (or other optical disc storage), magnetic cassettes, magnetic tapes, disk storage (or other magnetic storage devices), etc. Computer storage media do not include a propagated data signal. Communication media can typically include computer-readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave or other transport mechanism, and include any means of information delivery. The term modulated data signal can mean a signal that has one or more of its characteristics configured or modified in such a way as to encode information in the signal. Communication media can include wired media, such as a wired network or a direct cable connection, and wireless media, such as acoustic, infrared, and other wireless means. Combinations of any of the media described should be included within the scope of computer-readable media. Memory 428 may include computer storage media in the form of volatile and / or non-volatile memory. Memory 428 may be removable, non-removable, or a combination thereof. For example, memory 428 may include solid-state memory, hard disks, optical disk drives, etc. As illustrated in Figure 4, memory 428 may store computer-readable and / or computer-executable instructions 432 (e.g., programming element codes) that are configured to, when executed, cause the processor 426 (e.g., processing circuits) to perform various described functions. Alternatively, the instructions 432 may not be directly executable by the processor 426 but may be configured to cause the node 400 (e.g., when compiled and executed) to perform various described functions. The processor 426 may include an intelligent hardware device, a central processing unit (CPU), a microcontroller, an ASIC, etc. The processor 426 may include memory. The processor 426 can process data 430 and instructions 432 received from memory 428, and information received through transceiver 420, the baseband communications module, and / or the network communications module. The processor 426 can also process information to be sent to transceiver 420 for transmission through antenna 436, and / or to the network communications module for transmission to a CN. One or more 434 presentation components can present data to a person or other devices. 434 presentation components can include a display device, a speaker, a printing component, a vibration component, etc. From the present description, it is evident that various techniques can be used to implement the described concepts without deviating from their scope. Furthermore, although the concepts have been described with specific reference to particular implementations, a person with ordinary technical experience would recognize that changes can be made to the form and details without departing from the scope of those concepts. As such, the present description should be considered in all respects as illustrative and not restrictive. It should also be understood that the present description is not limited to the specific implementations described, but that many rearrangements, modifications, and substitutions are possible without departing from the scope of the present description. It is hereby stated that, as of this date, the best method known to the applicant for putting the aforementioned invention into practice is the one that is clear from the present description of the invention.

Claims

1. A cell reselection method in a non-public network (NPN) for a user equipment (UE), characterized in that it comprises: receiving, from a first cell via a first System Information Block 1 (SIB1), a first information element comprising a first network identity associated with a first indication; receiving, from a second cell via a second SIB1, a second information element including a second network identity associated with a second indication; selecting one of the first network identity and the second network identity; determining whether the first indication is present in the first information element and whether the UE selects the first network identity; determining the first cell as prohibited for cell reselection when the first indication is present, but the UE does not select the first network identity;and determine the first cell as a candidate cell for cell reselection when the first indication is present and the first network identity is selected by the UE, wherein: the first indication is used to indicate whether the first cell supports Integrated Access and Return Network (IAB) functionality, and the first network identity is different from the second network identity.; 2. The method according to claim 1, characterized in that it further comprises: determining the first cell as prohibited for cell reselection when the first indication is absent in the first information element.

3. The method according to claim 1, characterized in that: the first network identity is an NPN identity comprising a unique non-public network identity (SNPN) and a public network integrated non-public network identity (PNI-NPN), and the second network identity is a public land mobile network (PLMN) identity.

4. The method according to claim 1, characterized in that the UE supports IAB functionality.

5. The method according to claim 1, characterized in that it further comprises: transmitting, by a non-access stratum layer (NAS) of the UE, to an access stratum layer (AS) of the UE, a third indication indicating that the UE supports IAB functionality; and determining, by the AS layer of the UE, that the UE supports IAB functionality when it receives the third indication from the NAS layer of the UE.

6. The method according to claim 5, characterized in that the third indication is associated with a third network identity comprising a public land mobile network (PLMN) identity, a unique non-public network identity (SNPN), a public network integrated non-public network (PNINPN), a closed access group (CAG) identity, and a network identifier (NID).

7. The method according to claim 1, characterized in that the first indication indicates that the first cell supports IAB functionality when the first indication is present.

8. The method according to claim 1, characterized in that it further comprises: ignoring the first indication when the UE does not support IAB functionality.

9. The method according to claim 1, characterized in that it further comprises: ignoring the second indication when the identity of the second network is not selected by the EU.

10. The method according to claim 1, characterized in that the first indication indicates that the first cell supports IAB functionality when the first indication is present and is set with a first value.

11. User Equipment (UE) for performing cell reselection in a non-public network (NPN), characterized in that it comprises: a processor for executing a computer-executable program; and a memory coupled to the processor for storing the computer-executable program, wherein the computer-executable program instructs the processor to: receive, from a first cell via a first System Information Block 1 (SIB1), a first information element including a first network identity associated with a first indication; receive, from a second cell via a second SIB1, a second information element including a second network identity associated with a second indication; select one of the first network identity and the second network identity; determine whether the first indication is present in the first information element and whether the UE selects the first network identity;to determine the first cell as prohibited for cell reselection when the first indication is present, but the UE does not select the first network identity; and to determine the first cell as a candidate cell for cell reselection when the first indication is present and the first network identity is selected by the UE, wherein: the first indication is used to indicate whether the first cell supports Integrated Access and Return Network (IAB) functionality, and the first network identity is different from the second network identity.

12. The UE according to claim 11, characterized in that the computer executable program further instructs the processor to: determine the first cell as prohibited for cell reselection when the first indication is absent in the first information element.

13. The UE according to claim 11, characterized in that the first network identity is an NPN identity comprising a unique non-public network identity (SNPN) and an integrated non-public network identity of public or non-public network (PNI-NPN), and the second network identity is a public land mobile network identity (PLMN), wherein: the first network identity is an NPN identity comprising a unique non-public network identity (SNPN) and an integrated non-public network identity of public or non-public network (PNI-NPN), and the second network identity is a public land mobile network identity (PLMN).

14. The UE according to claim 11, characterized in that the UE supports IAB functionality.

15. The UE according to claim 11, characterized in that the computer executable program further instructs the processor to: transmit, by means of a non-access stratum layer (NAS) of the UE, to an access stratum layer (AS) of the UE, a third indication indicating that the UE supports IAB functionality; and determine, by means of the AS layer of the UE, that the UE supports IAB functionality when it receives the third indication from the NAS layer of the UE.

16. The UE according to claim 15, characterized in that the third indication is associated with a third network identity that includes a public land mobile network (PLMN) identity, a unique non-public network identity (SNPN), a public network integrated non-public network (PNI- ινΐΛ / a / zuzz / ui dd NRN), a closed access group (CAG) identity, and a network identifier (NID).

17. The UE according to claim 11, characterized in that the first indication indicates that the first cell supports IAB functionality when the first indication is present.

18. The UE according to claim 11, characterized in that the computer executable program further instructs the processor to: ignore the first indication when the UE does not support IAB functionality.

19. The UE according to claim 11, characterized in that the computer executable program further instructs the processor to: ignore the second indication when the identity of the second network is not selected by the UE.

20. The UE according to claim 11, characterized in that the first indication indicates that the first cell supports IAB functionality when the first indication is present and is set with a first value.