Method and related devices for cell reselection in non-public networks

Abstract

A method for a user equipment (UE) to perform cell reselection in a non-public network (NPN) is provided. The method includes receiving a first network identity from a first cell through a first system information block 1 (SIB1), the first network identity being associated with a first indication, receiving a second network identity from a second cell through a second SIB1, the second network identity being 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 the first network identity is selected by the UE, determining the first cell as barred for the 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

[0001] Cross Reference to Related Applications

[0002] This disclosure claims the benefit of and priority to Provisional U.S. Patent Application Serial No. 63 / 041,775, entitled “METHOD AND APPARATUS FOR THE SUPPORT OF INTEGRATED ACCESS AND BACKHAUL IN NON-PUBLIC NETWORK,” filed on June 19, 2020 (hereinafter “‘775 Provisional Application”). The disclosure of the ‘775 Provisional Application is hereby fully incorporated by reference into the present disclosure. TECHNICAL FIELD

[0003] The present disclosure relates generally to wireless communication, and more specifically to methods and related apparatus for cell reselection in a non-public network (NPN). BACKGROUND

[0004] As the number of connected devices grows exponentially and user / network traffic increases rapidly, various efforts have been made to improve different aspects of wireless communication by increasing data rates, latency, reliability, and mobility for next-generation wireless communication systems, such as the fifth generation (5G) New Radio (NR).

[0005] 5G NR systems are designed to provide flexibility and configurability to optimize network services and types, and to accommodate different use cases, such as enhanced mobile broadband (eMBB), massive machine-type communication (mMTC), and ultra-reliable and low-latency communication (URLLC).

[0006] However, as the demand for radio access continues to increase, there is a need for further improvements in wireless communication for next-generation wireless communication systems. SUMMARY

[0007] The present disclosure provides a method and related apparatus for cell reselection in a non-public network (NPN).

[0008] According to a first aspect of the disclosure, a method for a user equipment (UE) to perform cell reselection in a non-public network (NPN) is provided. The method comprises: receiving, from a first cell, a first information element through a first system information block 1 (SIB1), the first information element comprising a first network identity associated with a first indication; receiving, from a second cell, a second information element through a second SIB1, the second information element comprising 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 exists in the first information element and whether the first network identity is selected by the UE; determining the first cell as barred for the cell reselection when the first indication exists but the first network identity is not selected by the UE; and determining the first cell as a candidate cell for the cell reselection when the first indication exists and the first network identity is selected by the UE, characterized in that the first indication is used to indicate whether the first cell supports integrated access and backhaul (IAB) function, and the first network identity is different from the second network identity.

[0009] According to another aspect of the disclosure, a UE for performing cell reselection in a NPN is provided. The UE comprises a processor configured to execute a computer executable program; and a memory coupled to the processor configured to store the computer executable program, wherein the computer executable program instructs the processor to perform the above-mentioned method for performing cell reselection in a NPN. BRIEF DESCRIPTION OF DRAWINGS

[0010] Aspects of the disclosure are best understood from the following detailed description when read in conjunction with the accompanying drawings. Various features are not drawn to scale. The size of various features can be arbitrarily increased or decreased for the sake of discussion.

[0011] Figure 1A FIG. 1 is a schematic diagram illustrating an integrated access and backhaul (IAB) architecture comprising an IAB-node in standalone (SA) mode, according to an embodiment of the disclosure.

[0012] Figure 1B FIG. 2 is a schematic diagram illustrating an IAB architecture comprising an IAB-node in E-UTRA-NR dual connectivity (EN-DC) mode, according to an embodiment of the disclosure.

[0013] Figure 2 FIG. 3 is a schematic diagram illustrating an IAB architecture with 5G system (5GS), according to an embodiment of the disclosure.

[0014] Figure 3is a flowchart illustrating a method of a UE performing cell reselection in a non-public network (NPN) according to an embodiment of the disclosure.

[0015] Figure 4 is a block diagram illustrating a node for wireless communication according to an embodiment of the disclosure. DETAILED DESCRIPTION

[0016] The following disclosure contains specific information relating to exemplary embodiments in the present disclosure. The drawings in the present disclosure and their accompanying detailed disclosure are directed to exemplary embodiments. However, the present disclosure is not limited to these exemplary embodiments. Other variations and embodiments of the present disclosure will occur to those skilled in the art. Unless otherwise stated, identical or corresponding elements in the drawings can be denoted by identical or corresponding reference numerals. In addition, the drawings and the description are generally not to scale and are not intended to correspond to actual relative sizes.

[0017] For the purpose of consistency and ease of understanding, similar features are identified by reference indicators in the exemplary drawings (but are not shown in some examples). However, features in different embodiments can differ in other respects and should therefore not be narrowly limited to what is shown in the drawings.

[0018] The phrases "in one embodiment" and "in some embodiments" can each refer to one or more of the same or different embodiments. The term "coupled" is defined as connected, whether directly or indirectly through intervening components, and is not necessarily limited to a physical connection. The term "includes" can mean "comprises but not necessarily limited to"; it specifically indicates open-ended inclusion of the disclosed combinations, groups, series, and equivalents.

[0019] The term "and / or" in this document merely describes an association relationship of associated objects, which means that there can be three relationships, for example, A and / or B can represent: A exists alone, A and B exist at the same time, 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 at the same time, A and C exist at the same time, B and C exist at the same time, and A, B and C exist at the same time. In addition, the character " / " used here generally represents that the previous associated object and the latter associated object are in an "or" relationship.

[0020] Additionally, any two or more of the following in this disclosure: paragraphs, (sub-)item numbers, points, actions, acts, terms, alternatives, examples, or claims can be combined logically, reasonably, and appropriately to form a particular method. Any sentence, paragraph, (sub-)item number, point, action, act, term, or claim in this disclosure can be implemented independently and separately to form a particular method. Dependencies in this disclosure, such as “based on,” “more specifically,” “preferably,” “in one embodiment,” “in one embodiment,” “in one alternative,” can refer to only one possible example of a particular method that is not limiting.

[0021] For the purposes of explanation and non-limitation, specific details are set forth, such as functional entities, techniques, protocols, standards, etc., to provide an understanding of the described technology. In other examples, detailed disclosure of well-known methods, techniques, systems, and architectures is omitted so as not to obscure the disclosure with unnecessary detail.

[0022] Those skilled in the art will recognize that any disclosed network function or algorithm can be implemented by hardware, software, or a combination of software and hardware. The described functions can correspond to modules, which can be software, hardware, firmware, or any combination thereof. Software implementations can include computer-executable instructions stored on a computer-readable medium such as a memory or other type of storage device. For example, one or more microprocessors or general purpose computers with communication processing capabilities can be programmed using corresponding executable instructions to perform the described network functions or algorithms. These microprocessors or general purpose computers can be formed by application-specific integrated circuits (ASICs), programmable logic arrays, and / or using one or more digital signal processors (DSPs). While several embodiments are directed to software installed and executed on computer hardware, alternative embodiments of the same are fully within the scope of the disclosure as firmware or hardware or a combination of hardware and software.

[0023] The computer readable medium includes, but is 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 read only memory (CD-ROM), digital versatile disc (DVD), a box of magnetic tape, a magnetic tape, a magnetic disk, or any other medium that can be used to store computer readable instructions.

[0024] A radio communication network architecture (e.g., a Long Term Evolution (LTE) system, an LTE-Advanced (LTE-A) system, an LTE-Advanced Pro system, or a New Radio (NR) system) generally includes at least one base station (BS), at least one UE, and one or more optional network elements providing connectivity with a network (e.g., a Core Network (CN), an Evolved Packet Core (EPC) network, an Evolved Universal Terrestrial Radio Access Network (E-UTRAN), a Next-Generation Core (NGC), a 5G Core (5GC), or the Internet ) communicate.

[0025] A UE according to the present disclosure can include, but is not limited to, a mobile station, a mobile terminal, or a device, or a user communication radio terminal. For example, the UE can be a portable radio device including, but not limited to, a mobile phone, a tablet, a wearable device, a sensor, or a personal digital assistant (PDA) having a wireless communication capability. The UE can be configured to receive a signal through an air interface and to transmit a signal to one or more cells in a RAN. The BS can include, but is not limited to, a Node B (NB) in a Universal Mobile Telecommunication System (UMTS), an evolved Node B (eNB) in LTE-A, a radio network controller (RNC) in a UMTS, a base station controller (BSC) in a Global System for Mobile communication (GSM) / Enhanced Data rates for GSM Evolution (EDGE) RAN (GERAN), a next-generation eNB (ng-eNB) in an Evolved Universal Terrestrial Radio Access (E-UTRA) BS connected with a 5GC, a next-generation Node B (gNB) in a 5G-RAN (or 5G access network (5G-AN)), and any other device capable of controlling radio communication and managing radio resources within a cell. The BS can be connected through a radio interface to serve one or more UEs.

[0026] The BS can be configured to provide a communication service according to at least one of the following radio access technologies (RATs): Worldwide Interoperability for Microwave Access (WiMAX), GSM (commonly referred to as 2G), GERAN, General Packet Radio Service (GPRS), Enhanced Data rates for GSM Evolution (EDGE) RAN (GERAN), Universal Mobile Telecommunication System (UMTS), High Speed Packet Access (HSPA), Long Term Evolution (LTE), LTE-Advanced (LTE-A), Code Division Multiple Access (CDMA), Wideband CDMA (WCDMA), Institute of Electrical and Electronics Engineers (IEEE) 802.16m, IEEE 802.11, Bluetooth®, and / or ZigBee®. GPRSUMTS (commonly referred to as 3G), High-Speed Packet Access (HSPA), LTE, LTE-A, evolved LTE (eLTE), New Radio (NR, commonly referred to as 5G), and / or LTE-A Pro access may be employed. However, the scope of the disclosure is not limited to these protocols.

[0027] A BS can operate to provide wireless radio coverage to a particular geographic area using a plurality of cells forming the RAN. The BS can support operation of the cells. Each cell can operate to serve at least one UE within its radio coverage. More specifically, each cell (commonly referred to as a serving cell) can provide service to serve one or more UEs within its radio coverage (e.g., each cell schedules downlink (DL) and optional UL resources to at least one UE within its radio coverage for downlink and optional uplink packet transmissions). The BS can communicate with one or more UEs in the wireless communication system through a plurality of cells.

[0028] A cell can allocate sidelink resources for supporting Proximity Service (ProSe), LTE sidelink services, and LTE / NR Vehicle to Everything (V2X) services. Each cell can have an overlapping coverage area with other cells. In a Multi-RAT Dual Connectivity (MR-DC) case, a master cell group (MCG) or a secondary cell group (SCG) primary cell can be referred to as a special cell (SpCell). A primary cell (PCell) can refer to the SpCell of the MCG. A primary SCG cell (PSCell) can refer to the SpCell of the SCG. The MCG can refer to a serving cell group associated with a master node (MN), including the SpCell and optionally one or more secondary cells (SCells). The SCG can refer to a serving cell group associated with a secondary node (SN), including the SpCell and optionally one or more SCells.

[0029] As previously described, the frame structure for NR supports flexible configurations for accommodating various next generation (e.g., 5G) communication requirements, 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 in the Third Generation Partnership Project (3GPP), can be used as a baseline for the NR waveform. Scalable OFDM numerologies, such as adaptive subcarrier spacing, channel bandwidth, and Cyclic Prefix (CP), can also be used. In addition, two coding schemes are applied for NR: (1) Low Density Parity Check (LDPC) code and (2) polar code. Coding scheme adaptation can be configured based on channel conditions and / or service applications.

[0030] In addition, in a transmission time interval of a single NR frame, DL transmission data, a guard period, and UL transmission data should be included at least. Each portion of the DL transmission data, the guard period, and the UL transmission data should also be configurable, for example, based on NR network dynamics. SL resources can also be provided via the NR frame to support ProSe services or V2X services.

[0031] To meet the low latency and high reliability requirements of vertical industries and support 5G local area network (LAN) type services, a dedicated wireless network (e.g., a private network) has attracted attention and will be incorporated into the next generation cellular network.

[0032] The dedicated network (e.g., a non-public network (NPN)) can support vertical industries and LAN services. The dedicated network can be divided into a standalone non-public network (SNPN) and a public network integrated non-public network (PNI-NPN).

[0033] The 5G system is enhanced to support the NPN. Two network identities are applied to the NPN: a network identifier (NID) for identifying the NPN and a closed access group (CAG) identity. The 5G radio access network (RAN) can also implement the NPN by enhancing functions such as NPN identification, discovery, selection / reselection, access control, and mobility restriction.

[0034] One of the potential technologies aimed at enabling future cellular network deployment scenarios and applications is the support of wireless backhaul and relay links to enable flexible and very dense cell deployments (e.g. NR cells) without the need to scale the transport network density proportionally. The wireless backhaul and relay can utilize massive multiple-input multiple-output (MIMO) or multi-beam systems. The benefits of integrated access and backhaul (IAB) are crucial in the network rollout and initial network growth phase. To leverage these benefits, IAB needs to be available when rolling out NR. Enabling IAB functionality in NPN deployments is considered as one possible case for future cellular networks.

[0035] In NPN scenarios, a UE can be configured as "UE in SNPN access mode" or "UE in non-SNPN access mode (e.g. UE not in SNPN access mode)" by the UE's NAS layer, by the camped / serving cell or through pre-configuration. A cell can be configured as "SNPN cell", "CAG cell", "Public Land Mobile Network (PLMN) cell", "cell supporting at least SNPN deployment", "cell supporting at least PNI-NPN deployment", "cell supporting at least PLMN deployment". "cell supporting at least SNPN and PNI-NPN deployment", "cell supporting at least SNPN and PLMN deployment", "cell supporting at least PNI-NPN and PLMN deployment", or "cell supporting SNPN, PNI-NPN and PLMN deployment".

[0036] In IAB scenarios, a UE can be configured as "IAB capable UE" and "non-IAB capable UE". A cell can be configured as "IAB capable cell" and "non-IAB capable cell".

[0037] Multiple PLMNs can operate on unlicensed spectrum. Multiple PLMNs can share the same unlicensed carrier. A PLMN can be public or private. A public PLMN can be (but can not be limited to) an operator or a virtual operator that provides radio services to public users. A public PLMN can own licensed spectrum and support RATs on licensed spectrum. A private PLMN can be (but not limited to) a micro-operator, a factory or an enterprise that provides radio services to its private users (e.g. employees or machines). A public PLMN can support more deployment scenarios (e.g. carrier aggregation (CA) between licensed band NR (e.g. PCell) and NR-U (e.g. SCell), dual connectivity (DC) between licensed band LTE (e.g. PCell) and NR-U (e.g. PSCell), standalone NR-U, NR cell with DL in unlicensed band and UL in licensed band, dual connectivity between licensed band NR (e.g. PCell) and NR-U (e.g. PSCell)). On the other hand, a private PLMN mainly supports (but can not be limited to) standalone unlicensed RAT (e.g. standalone NR-U).

[0038] In the present disclosure, mechanisms are disclosed for a UE supporting IAB and / or NPN to perform cell (re)selection in order to select / camp on a cell supporting the corresponding IAB and / or NPN.

[0039] IAB technology

[0040] IAB can enable wireless relaying in RAN (e.g. next generation RAN (NG-RAN)). Relay nodes, referred to as IAB nodes, can support access and backhaul over a RAT (e.g. NR, LTE connected to 5G core (5GC), LTE connected to EPC). In the present disclosure, the term "NR" is used as an example for illustration. However, the RAT applied to IAB can not be limited to NR. The terminal node of the NR backhaul on the network side can be referred to as IAB-donor, which represents a base station with additional functionalities to support IAB (e.g. gNB if the RAT is NR, eNB if the RAT is LTE connected to EPC, ng-eNB if the RAT is LTE connected to 5GC). Backhauling can occur through single-hop or multi-hop. Figure 1A and Figure 1B IAB architecture is illustrated.

[0041] Figure 1Ais a schematic diagram illustrating an IAB architecture including IAB-nodes with standalone (SA) mode, according to embodiments of the present disclosure. In NR SA mode, the IAB-donor 10 can be a gNB supporting IAB functionality. Network nodes (e.g., UEs, IAB-nodes 12, or IAB-nodes 14) can be connected to a 5GC (e.g., access and mobility management function (AMF) / user plane function (UPF)) through the IAB-donor 10.

[0042] Figure 1B is a schematic diagram illustrating an IAB architecture including IAB-nodes with E-UTRA-NR dual connectivity (EN-DC) mode, according to embodiments of the present disclosure. In one example, in EN-DC mode, the IAB-donor 100 can be a secondary gNB (SgNB) with IAB functionality. Alternatively, the IAB-donor 100 can be a master eNB (MeNB) supporting IAB functionality. Network nodes (e.g., UEs, IAB-nodes 102, or IAB-nodes 104) can be connected to an EPC (e.g., mobility management entity (MME) / serving and packet data network gateway (S-PGW)) through the IAB-donor 100. Alternatively, network nodes (e.g., UEs, IAB-nodes 102, or IAB-nodes 104) can be connected to a 5GC (e.g., AMF / UPF) through the IAB-donor 100 (e.g., in NG-RAN E-UTRA-NR dual connectivity (NGEN-DC) mode).

[0043] In another example, in NR-NR dual connectivity (NR-DC) mode, the IAB-donor can be a master gNB (MgNB) supporting IAB functionality. Alternatively, the IAB-donor can be a SgNB supporting IAB functionality. Network nodes (e.g., UEs or IAB-nodes) can be connected to a 5GC (e.g., AMF / UPF) through the IAB-donor.

[0044] In other examples, in NR-E-UTRA dual connectivity (NE-DC) mode, the IAB-donor can be a MgNB supporting IAB functionality. Alternatively, the IAB-donor can be a SeNB supporting IAB functionality. Network nodes (e.g., UEs or IAB-nodes) can be connected to a 5GC (e.g., AMF / UPF) through the IAB-donor.

[0045] Figure 2is a diagram illustrating an IAB architecture with a 5G system (5GS) according to an embodiment of the disclosure. IAB nodes (e.g., IAB-donor gNB 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 UEs 25-27 and next-hop IAB nodes (e.g., IAB-nodes 22 and 24) and the Fl protocol to gNB-central unit (gNB-CU) functionality (e.g., IAB-donor-CU 202 of IAB-donor gNB 20). IAB-donor-DU 204, gNB-DU 222, and gNB-DU 242 are also referred to as IAB-DUs.

[0046] As shown in Figure 2 , an IAB architecture with two backhaul hops when connected to 5GC is disclosed. For example, gNB-DUs 222 and 242 of IAB-nodes 22 and 24 are responsible for providing NR Uu access to UEs 26 and 27 and child IAB-nodes (e.g., IAB-node 24 is a child IAB-node of IAB-node 22). A gNB-CU functionality (e.g., IAB-donor-CU 202) can be deployed on IAB-donor gNB 20, which controls gNB-DUs 222 and 242 of IAB-nodes 22 and 24 over the Fl interface. IAB-nodes 22 and 24 can be considered as normal gNBs for UEs 26-27, while other IAB-nodes (e.g., IAB-donor gNB 20) can allow UEs 25-27 to connect to 5GC (or EPC).

[0047] In addition to gNB-DU functionality, IAB-nodes 22 and 24 can support a subset of UE functionality (e.g., IAB-UEs 224 and 244), which can be referred to as IAB-mobile- terminals (IAB-MTs), and each include physical layer, second layer, radio resource control (RRC), and non-access stratum (NAS) functionality to connect to another IAB-node (e.g., IAB-nodes 22 and 24) or gNB-DU (e.g., IAB-donor-DU 204, gNB-DU 222, and gNB-DU 242) of an IAB-donor (e.g., IAB-donor gNB 20), to a gNB-CU (e.g., IAB-donor-CU 202) of an IAB-donor (e.g., IAB-donor gNB 20), and to a core network.

[0048] All the functionalities of a UE can be used as an IAB-MT. For example, an IAB-MT can access the network using one network node or using two different network nodes in EN-DC and NR-DC mode. In (NG)EN-DC mode, backhaul traffic over E-UTRA radio interface can or can not be supported.

[0049] An IAB-node can access the network by using SA-mode or EN-DC mode, but can not be limited thereto. For example, an IAB-node can access the network by using (NG)EN-DC, NR-DC or NE-DC mode. In EN-DC mode, an IAB-node can be connected to a MeNB (or SgNB) through E-UTRA, while an IAB-donor terminates X2-C as a SgNB.

[0050] In EN-DC mode, a secondary node (SN) can broadcast system information to allow an IAB-MT to access the SN.

[0051] It is noted that, as shown in Figure 2 An IAB-node can implement wireless in-band and out-of-band relaying of NR Uu access traffic over a NR Uu backhaul link. The Uu backhaul link can exist between an IAB-node and a gNB called an IAB-donor, or between an IAB-node and another IAB-node. The part of an IAB-node that supports the (Uu) interface towards an IAB-donor or another parent IAB-node (for managing the backhaul connection to the PLMN or SNPN that the IAB-node is registered with) is called an IAB-UE. The functions of the IAB-UE are equivalent to a UE and reuse UE procedures to connect to: (1) a gNB-DU of a parent IAB-node or IAB-donor for access and backhaul; (2) a gNB-CU of an IAB-donor for control of access and backhaul links through RRC; (3) a 5GC (e.g., AMF) through NAS; and (4) an operation, administration, and maintenance (OAM) system through a packet data unit (PDU) session or packet data network (PDN) connection.

[0052] An IAB-UE can connect to a 5GC through NR (with SA mode, NR-DC or NGEN-DC mode). Alternatively, an IAB-UE can connect to an EPC (with EN-DC mode) network (e.g., through a SgNB). A UE served by an IAB-node can operate in the same or different mode as the IAB-node. For example, if an IAB-UE connects to a 5GC through NR (with SA mode), the IAB-donor can be an IAB-capable gNB. For another example, if an IAB-UE connects to an EPC through EN-DC mode, the IAB-donor can be an IAB-capable SgNB in EN-DC mode.

[0053] On the other hand, the UE can operate in a PLMN access mode (e.g., not in a SNPN access mode) or a SNPN access mode. The UE can determine whether it is in a PLMN access mode or in a SNPN access mode according to at least one of the following conditions:

[0054] Condition 1: The UE (e.g., a NAS entity of the UE) can determine according to NAS (pre-)configuration;

[0055] Condition 2: The UE can be (pre-)configured to be in a PLMN access mode (e.g., not in a SNPN access mode) or in a SNPN access mode;

[0056] Condition 3: The UE can be changed from a PLMN access mode (e.g., not in a SNPN access mode) to a SNPN access mode by the UE (e.g., a NAS entity of the UE) or by a serving / camping cell; and

[0057] Condition 4: The UE can be changed from a SNPN access mode to a PLMN access mode (e.g., not in a SNPN access mode) by the UE (e.g., a NAS entity of the UE) or by a serving / camping cell.

[0058] If the UE is in PLMN access mode (or if the UE is not in SNPN access mode), the UE can perform PLMN selection. For a UE operating not in SNPN access mode (or for a UE operating in PLMN access mode), the UE (e.g., a NAS entity of the UE) can maintain a list of PLMNs in a priority order. For each (selected / registered) PLMN, the UE (e.g., the NAS entity of the UE) can set an associated RAT. The UE (e.g., an AS entity of the UE) can perform cell measurements for selection of a PLMN. The UE (e.g., the AS entity of the UE) can synchronize with a broadcast channel to identify a PLMN. The UE (e.g., the AS entity of the UE) can search for available PLMNs. The AS entity of the UE can report available PLMNs to the NAS entity of the UE. The AS entity of the UE can report available PLMNs and / or any associated CAG IDs with the associated RAT to the NAS entity of the UE according to a request by the NAS entity of the UE or autonomously. The NAS entity of the UE can evaluate the report of available PLMNs and any associated CAG IDs from the AS entity of the UE for selection of a PLMN. The NAS entity of the UE can maintain a list of equivalent PLMN identities. The NAS entity of the UE can select a PLMN according to the reported available PLMNs and / or the reported CAG IDs in an automatic manner (e.g., allowing the UE to automatically select) or in a manual manner (e.g., the UE is not authorized to automatically select, but is allowed to select under certain required / default or pre-configured conditions) and request the AS entity of the UE to select a (suitable / acceptable) cell belonging to the PLMN.

[0059] In one example, the NAS entity of the UE can indicate a selected PLMN (or a PLMN ID identifying the selected PLMN) (e.g., without involving available PLMNs) to the AS entity of the UE. Accordingly, the AS entity of the UE can perform a cell (re)selection procedure and select a suitable / acceptable cell belonging to the selected PLMN.

[0060] 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 a UE not operating in SNPN access mode (or for a UE operating in PLMN access mode) and a UE supporting manual CAG selection (e.g., the UE can (re)select a CAG cell according to a manual CAG selection method by which a PLMN can control the UE to manually select an NPN hosted by the PLMN for which the UE can not be authorized to automatically select), the NAS entity of the UE can provide a request to the AS entity of the UE to search for available CAGs. The AS entity of the UE can search for cells that broadcast CAG IDs in a system information block (SIB) (e.g., in SIB1). If a cell that broadcasts a CAG ID is found, the AS entity of the UE can read a human-readable network name (HRNN) for each CAG ID. The AS entity of the UE can report the CAG IDs of the found cells that broadcast CAG IDs, and the associated HRNNs and PLMNs, to the NAS entity of the UE. The NAS entity of the UE can evaluate the report of available CAGs from the AS entity of the UE in order to select a CAG. The NAS entity of the UE can select a CAG ID from the report of available CAGs. The NAS entity of the UE can inform the AS entity of the UE of the selected CAG ID. The selected CAG is identified by the selected CAG ID, while the registered CAG is identified by the registered CAG ID. The AS entity of the UE can select any acceptable or suitable cell that belongs to the selected CAG and transmit an indication to the NAS entity of the UE (e.g., indicating that access for a registration procedure is possible).

[0061] In one example, the NAS entity of the UE can indicate to the AS entity of the UE the selected PLMN (or a PLMN ID identifying the selected PLMN) and / or the selected CAG (or a CAG ID identifying the selected CAG) (e.g., without involving available PLMNs / CAGs). The AS entity of the UE can perform a cell (re)selection procedure and select a suitable / acceptable cell that belongs to the selected PLMN and / or the selected CAG.

[0062] If the UE is in the SNPN access mode, the UE can perform SNPN selection. For a UE operating in the SNPN access mode, the UE (e.g., a NAS entity of the UE) can maintain a list of SNPNs. The NAS entity of the UE can select a SNPN in an automatic or manual manner and request the AS entity of the UE to select a cell belonging to the SNPN. The NAS entity of the UE can evaluate the available SNPN report from the AS entity of the UE in order to select a SNPN. The UE (e.g., the NAS entity of the UE) can set the associated RAT for the respective SNPN. The UE (e.g., the AS entity of the UE) can search for available SNPNs by considering cells corresponding to the relevant RAT. Alternatively, the UE (e.g., the NAS entity of the UE) can consider that the relevant RAT for the respective SNPN is NR. The UE (e.g., the AS entity of the UE) can search for available SNPNs by considering NR cells. The UE (e.g., the AS entity of the UE) can perform cell measurements to support SNPN selection. The UE (e.g., the AS entity of the UE) can synchronize with a broadcast channel to identify SNPNs. The AS entity of the UE can automatically report available SNPNs to the NAS entity of the UE. The AS entity of the UE can report available SNPNs and associated HRNNs (if available) to the NAS entity of the UE upon request by the NAS entity of the UE. The UE (e.g., the NAS entity of the UE) can select (or register) a SNPN. The NAS entity of the UE can inform the AS entity of the UE of the selected (or registered) SNPN ID. The selected SNPN ID can identify the selected SNPN, while the registered SNPN ID can identify the registered SNPN.

[0063] In one example, the NAS entity of the UE can indicate to the AS entity of the UE the selected or registered SNPN (e.g., the SNPN ID identifying the selected SNPN or the registered SNPN ID identifying the registered SNPN) (e.g., without involving available SNPNs). The AS entity of the UE can perform a cell (re)selection procedure and select a suitable / acceptable cell belonging to the selected SNPN.

[0064] After the AS entity of the UE receives the selected / registered SNPN ID, the AS entity of the UE can perform a cell (re)selection procedure. Thus, the UE in RRC_IDLE / RRC_INACTIVE state can camp on a suitable cell as a result of the cell (re)selection procedure. In the cell (re)selection procedure, the UE in RRC_IDLE / RRC_INACTIVE state can receive and read the system information (e.g., MIB, SIB1) broadcasted by the candidate cell. According to the system information broadcasted by the candidate cell, the UE in RRC_IDLE / RRC_INACTIVE state can determine whether the UE is barred from entering the corresponding candidate cell. The system information can indicate whether the cell supports IAB function for the corresponding PLMN / SNPN, and / or whether the cell supports NPN function. Different UEs in RRC_IDLE / RRC_INACTIVE state (e.g., whether the UE supports NPN function, whether the UE supports IAB function) can perform different actions according to the system information.

[0065] In the present disclosure, the information of the system information (e.g., the information is implicitly or explicitly indicated in the system information) can include (but can not be limited to) the first indication and / or the second indication. The UE can determine whether the cell is barred for the UE or whether the cell is a candidate cell for the cell (re)selection procedure according to the first indication and / or the second indication. The UE can determine whether the cell is barred for the UE or whether the cell is a candidate cell for the cell (re)selection procedure according to the two indications sequentially or in parallel.

[0066] In the present disclosure, the UE can refer to (but can not be limited to) a normal UE, an IAB-UE, an IAB-MT, a NPN capable UE, and / or a NPN incapable UE. The cell can refer to (but can not be limited to) a normal cell, a normal BS, an IAB node, a gNB-DU, a gNB-CU, an IAB-donor, a cell with IAB function and activated to perform IAB related functions, a cell with IAB function but not activated to perform IAB related functions, a cell without IAB function, a cell supporting SNPN, a cell supporting PNI-NPN, and / or a cell supporting at least one of SNPN, PNI-NPN, and PLMN.

[0067] IAB support in NPN

[0068] The UE can determine whether it is barred from entering the cell after the UE receives the first indication (e.g., iab-Support information element (IE)) 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 first indication from the cell through the SIB1.

[0069] The first indication can be associated with an identity, and the identity can identify a network (e.g., a first network identity).

[0070] In one example, the first indication can be associated with a PLMN ID. The PLMN ID can identify a PLMN and / or a PNI-NPN and / or a SNPN.

[0071] For example, the first indication can be included in an IE, where the IE includes information associated with a PLMN ID.

[0072] For example, the first indication can be included in an IE (e.g., NPN-Identitylnfo IE), where the IE includes information associated with a NPN (e.g., PNI-NPN, SNPN) and includes at least one NPN identity (e.g., PNI-NPN ID, SNPN ID). The PNI-NPN identity can include one PLMN identity and at least one CAG identity. The SNPN identity can include one PLMN ID and at least one NID. The at least one NPN identity can identify a NPN. The first indication can be further included in an IE, where the IE includes information associated with a PLMN ID that identifies a PNI-NPN. Or, the first indication can be further included in an IE, where the IE includes information associated with a PLMN ID that identifies a SNPN.

[0073] In one example, the first indication can be associated with a SNPN ID. The SNPN ID can identify a SNPN.

[0074] For example, the first indication can be included in an IE (e.g., NPN-Identitylnfo IE), where the IE includes information associated with a NPN (e.g., PNI-NPN, SNPN) and includes at least one NPN identity (e.g., PNI-NPN ID, SNPN ID). The PNI-NPN identity can include one PLMN identity and at least one CAG identity. The SNPN identity can include one PLMN ID and at least one NID. The at least one NPN identity can identify a NPN. In this case, the NPN identity can be a SNPN identity.

[0075] In one example, the first indication can be associated with a NID. The NID can identify a SNPN.

[0076] For example, the first indication can be included in an IE, wherein the IE includes information associated with a NID.

[0077] In one example, the first indication can be associated with a PNI-NPN ID. The PNI-NPN ID can identify a PNI-NPN and / or a CAG cell.

[0078] For example, the first indication can be included in an IE (e.g., NPN-Identitylnfo IE), wherein the IE includes information associated with a NPN (e.g., PNI-NPN, SNPN) and includes at least one NPN identity (e.g., PNI-NPN ID, SNPN ID). The PNI-NPN identity can include one PLMN identity and at least one CAG identity. The SNPN identity can include one PLMN ID and at least one NID. The at least one NPN identity can identify a NPN. In this case, the NPN identity can be a PNI-NPN ID.

[0079] In one example, the first indication can be associated with a CAG ID. The CAG ID can identify a PNI-NPN and / or a CAG cell.

[0080] For example, the first indication can be included in an IE, wherein the IE includes information associated with a CAG ID.

[0081] The first indication can indicate whether the cell supports IAB functionality (e.g., support for IAB-node from the perspective of the cell) and / or a cell status of IAB functionality. If the indication is present (or '1' or {true}) in an IE, the cell can support IAB functionality and the cell can be considered as a candidate cell for cell (re)selection procedure from the perspective of a UE. If the indication is not present (or '0' or {false}) in the IE, the cell can not support IAB functionality from the perspective of a UE and / or the cell can be considered as a barred cell for IAB-node (or IAB-MT) (e.g., IAB-enabled UE) for cell (re)selection procedure.

[0082] The first indication can indicate whether the cell supports IAB functionality (e.g., supports IAB-node from the perspective of the cell) and NPN functionality (e.g., supports NPN from the perspective of the cell) and / or cell status for IAB functionality and NPN functionality. If the first indication is present (or '1' or {true}), the cell can support IAB functionality and NPN functionality and the cell can be considered as a candidate cell for cell (re)selection procedure from the perspective of a UE. That is, the cell can be determined as a candidate cell for IAB-node supporting NPN functionality (e.g., IAB-enabled NPN-capable UE). If the first indication is not present (or '0' or {false}), the cell can not support IAB functionality or NPN functionality from the perspective of a UE and / or the cell can be considered as a barred cell for cell (re)selection procedure. That is, the cell can be determined as a barred cell for IAB-node supporting NPN functionality (e.g., IAB-enabled NPN-capable UE) (or IAB-MT).

[0083] If the UE receives the first indication through system information (e.g., SIB1), the UE can check whether the first indication is associated with a registration (or selection) identity (e.g., PLMN ID, SNPN ID, PNI-NPN ID, NID, CAG ID) identifying a corresponding network (e.g., PLMN, SNPN, PNI-NPN, CAG cell).

[0084] If the first indication is not provided (not present or absent) in the IE for the selected PLMN, the registered PLMN, or the PLMNs of the equivalent PLMN list, the selected SNPN, the registered SNPN, or the SNPNs of the equivalent SNPN list, the UE can consider the cell as barred (e.g., barred for the UE supporting IAB functionality and / or NPN functionality, barred for the UE supporting IAB functionality and having a registered / selected SNPN).

[0085] 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 can consider the cell as barred (e.g., barred for the UE supporting IAB functionality and NPN functionality, barred for the UE supporting IAB functionality and CAG functionality).

[0086] 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 cell (re)selection procedure. The UE can support IAB functionality and NPN functionality having a registered (or selected) SNPN for a corresponding SNPN.

[0087] If the indication is provided (present or included) in the selected (or registered) PLMN / PNI-NPN / CAG IE, the UE can consider the cell as a candidate cell for cell (re)selection procedure. The UE can support IAB function and NPN function with the registered (or selected) PLMN / PNI-NPN / CAG for the corresponding PNI-NPN / CAG.

[0088] If the UE considers itself prohibited from entering a certain cell, the UE can not consider the cell as a candidate cell for cell (re)selection procedure. If the UE considers itself not prohibited from entering a certain cell, the UE can consider the cell as a candidate cell for cell (re)selection procedure.

[0089] If the first indication is irrelevant to the UE, the UE can ignore the first indication when the UE receives the first indication. For example, if the UE does not operate as an IAB node, and / or if the UE does not support IAB function, and / or if the UE does not support NPN function, the UE can ignore the first indication.

[0090] A UE supporting IAB function and NPN function with a registered (or selected) SNPN shall not ignore a second indication (e.g., cellReservedforOtherUse IE) broadcast by a cell in system information (e.g., SIB1) during cell (re)selection procedure. A UE supporting IAB function and NPN function with a registered (or selected) PLMN / PNI-NPN / CAG for the corresponding PNI-NPN / CAG shall not ignore a second indication (e.g., cellReservedforOtherUse IE) broadcast by a cell in system information (e.g., SIB1) during 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 broadcast in the same system information (e.g., SIB1). The second indication and associated PLMN IDs are broadcast by a cell in the same IE (e.g., cellAccessRelatedInfo IE). The UE can receive the second indication and associated PLMN IDs through SIB1 broadcast by the cell.

[0091] A UE supporting IAB function and NPN function with a registered (or selected) SNPN can check the second indication broadcast by a cell and determine whether the cell is prohibited for the UE or the cell can be a candidate cell for cell (re)selection procedure.

[0092] If the UE receives the second indication indicating "true" (or "1") and if the cell does not broadcast any CAG ID or NID, the UE can determine the cell as cell status "barred".

[0093] If the UE receives the second indication indicating "true" (or "1") and if the cell broadcasts any CAG ID or NID, the UE can determine whether the UE is barred from entering the cell according to the first indication. For example, the UE can determine whether the cell is barred for the UE or the cell can be a candidate cell for a cell (re)selection procedure according to the first indication.

[0094] If the UE receives the second indication indicating not "true" (or indicating "0", or indicating "false"), or if the second indication is not present in the IE (e.g., the UE does not receive the second indication, the UE does not receive the IE including the second indication), the UE can determine the cell as cell status "barred".

[0095] If the UE receives the second indication indicating not "true" (or indicating "0", or indicating "false"), or if the second indication is not present in the IE (e.g., the UE does not receive the second indication, the UE does not receive the IE including the second indication), the UE can determine whether the UE is barred from entering the cell according to the first indication. For example, the UE can determine whether the cell is barred for the UE or the cell can be a candidate cell for a cell (re)selection procedure according to the first indication.

[0096] A UE supporting IAB functionality and having NPN functionality of registering (or selecting) a PLMN / PNI-NPN / CAG can check the second indication broadcast by the cell and determine whether the cell is barred for the UE or the cell can be a candidate cell for a cell (re)selection procedure.

[0097] If the UE receives the second indication indicating "true" (or "1") and if the cell does not broadcast any CAG ID or NID, the UE can determine the cell as cell status "barred".

[0098] If the UE receives the second indication indicating "true" (or "1") and if the cell broadcasts any CAG ID or NID, the UE can determine whether the UE is barred from entering the cell according to the first indication. For example, the UE can determine whether the cell is barred for the UE or the cell can be a candidate cell for a cell (re)selection procedure according to the first indication.

[0099] If the UE receives the second indication indicating not "true" (or indicating "0", or indicating "false"), or if the second indication is not present in the IE (e.g., the UE does not receive the second indication, the UE does not receive the IE including the second indication), the UE can determine the cell as the cell status being "barred".

[0100] If the UE receives the second indication indicating not "true" (or indicating "0", or indicating "false"), or if the second indication is not present in the IE (e.g., the UE does not receive the second indication), the UE can determine whether the UE is barred from entering the cell according to the first indication. For example, the UE can determine whether the cell is barred for the UE, or the cell can be a candidate cell for a cell (re)selection procedure, according to the first indication.

[0101] UE operating as an IAB node

[0102] The UE supporting IAB functionality can refer to a UE operating as an IAB node. Or, the UE supporting IAB functionality can determine itself (or be determined by a network (NW)) as a UE operating as an IAB node. The UE supporting IAB functionality can determine itself (or be determined by a network) not to be a UE operating as an IAB node. For example, the aforementioned examples (e.g., the first indication, the second indication, the cell (re)selection procedure) can be applicable to an IAB node.

[0103] The NAS entity of the UE supporting IAB functionality can transmit the third indication to the AS entity of the UE. If the AS entity of the UE receives the third indication, the AS entity of the UE can determine itself as a UE operating as an IAB node according to the (received) third indication.

[0104] The NAS entity of the UE supporting IAB functionality can transmit the third indication to the AS entity of the UE. If the third indication is '1', the AS entity of the UE can determine itself as a UE operating as an IAB node according to the (content) of the third indication after receiving the third indication.

[0105] The NAS entity of the UE supporting IAB functionality can transmit the third indication to the AS entity of the UE. If the third indication is '0', the AS entity of the UE can determine itself as not a UE operating as an IAB node according to the (content) of the third indication after receiving the third indication.

[0106] The network can transmit the third indication to the AS entity of the UE. If the AS entity of the UE receives the third indication, the UE supporting IAB functionality can determine itself as a UE operating as an IAB node according to the (received) third indication.

[0107] The network can transmit a third indication in a downlink control information (DCI) / medium access control (MAC) control element (CE) / RRC message to the UE (of the AS entity). If the UE (of the AS entity) receives the third indication and the third indication is '1', the IAB-capable UE can determine itself as a UE operating as an IAB node according to (the content of) the third indication.

[0108] The network can transmit a third indication in a DCI / MAC CE / RRC message to the UE (of the AS entity). If the UE (of the AS entity) receives the third indication and the third indication is '0', the IAB-capable UE can determine itself as not a UE operating as an IAB node according to (the content of) the third indication.

[0109] The third indication can be associated with a PLMN / SNPN / PNI-NPN / CAG and / or a RAT (e.g., NR, E-UTRA). The UE can determine itself as a UE operating as an IAB node according to the third indication (e.g., reception of the third indication, content of the third indication) and / or according to the (registered / selected) PLMN / SNPN / PNI-NPN / CAG and / or according to the RAT the UE operates / selects.

[0110] The third indication can be associated with a PLMN / SNPN / PNI-NPN / CAG. The associated PLMN / SNPN / PNI-NPN / CAG can be in a universal subscriber identity module (USIM) or predefined (or pre-configured) by the network.

[0111] For example, the NAS entity of the IAB-capable UE can send the third indication associated with at least a PLMN / SNPN / PNI-NPN / CAG to the AS entity of the UE.

[0112] For example, (1) after the AS entity of the UE receives the third indication, (2) if the received third indication associated with a PLMN / SNPN / PNI-NPN / CAG is the registered / selected PLMN / SNPN / PNI-NPN / CAG of the UE, and / or (3) if the content of the third indication is '1', the UE can perform as an IAB node (for the associated PLMN / SNPN / PNI-NPN / CAG).

[0113] The third indication can be associated with a RAT. The associated RAT can be in a USIM or predefined (or pre-configured) by the network.

[0114] For example, the NAS entity of the IAB-capable UE can send the third indication associated with at least one RAT to the AS entity of the UE.

[0115] For example, (1) after the AS entity of the UE receives the third indication, (2) if the received third indication is related to a RAT, which is selected / indicated by the NAS entity of the UE to perform PLMN selection and / or cell (re)selection, and / or (3) if the content of the third indication is '1', the UE can perform as an IAB node (for the associated RAT).

[0116] The terms, e.g., NW, RAN, cell, camped cell, serving cell, BS, gNB, eNB, and ng-eNB, can be used interchangeably. Some of these terms can refer to the same network entity.

[0117] For a UE in RRC CONNECTED state without configured Carrier Aggregation (CA) or Dual Connectivity (DC), a serving cell can mean a primary cell. For a UE in RRC CONNECTED state with configured CA / DC, the term "serving cell" is used to mean a cell group comprising a special cell and all secondary cells.

[0118] The term "special cell" can refer to a PCell of a MCG or a PSCell of a SCG when used for DC operation. Otherwise, the term "special cell" can refer to a PCell.

[0119] The aforementioned examples can apply to any RAT. The RAT can be (but can not be limited to) NR, NR-U (Unlicensed NR, unlicensed spectrum access according to NR), LTE, E-UTRA connected to 5GC, LTE connected to 5GC, E-UTRA connected to EPC, and LTE connected to EPC.

[0120] The aforementioned examples can apply to a UE in a public network or a private network (e.g., a Non-Public Network (NPN), a Standalone NPN (SNPN), or a Public Network Integrated NPN (PNI-NPN)).

[0121] The aforementioned examples can apply to licensed frequencies and / or unlicensed frequencies.

[0122] System information (SI) can refer to MIB, SIB1, and other SI. Minimum SI can include MIB and SIB1. Other SI can refer to SIB3, SIB4, SIB5, and other SIBs (e.g., SNPN-specific SIB or PNI-NPN-specific SIB).

[0123] Dedicated signaling can refer to, but can not be limited to, RRC messages. For example, the RRC messages can include RRC (connection) setup request message, RRC (connection) setup message, RRC (connection) setup complete message, RRC (connection) reconfiguration message, RRC connection reconfiguration message including mobility control information, RRC connection reconfiguration message not including mobility control information, RRC reconfiguration message including synchronization configuration, RRC reconfiguration message not including synchronization configuration, RRC (connection) reconfiguration complete message, RRC (connection) resume request message, RRC (connection) resume message, RRC (connection) resume complete message, RRC (connection) reestablishment request message, RRC (connection) reestablishment message, RRC (connection) reestablishment complete message, RRC (connection) reject message, RRC (connection) release message, RRC system information request message, UE assistance information message, UE capability enquiry message, and UE capability information message. The RRC message can be a kind of dedicated signaling. The UE can receive the RRC message from the network through unicast / broadcast / groupcast.

[0124] The aforementioned examples can be applied to RRC_CONNECTED UEs, RRC_INACTIVE UEs, and RRC_IDLE UEs.

[0125] The RRC_CONNECTED UE can be configured to have an active BWP with a common search space configured to monitor system information or paging.

[0126] In general, the aforementioned examples can be applied to PCell and UE. The aforementioned examples can be applied to PSCell and UE. Short message and / or paging downlink control information (DCI) can be transmitted by the PSCell (or secondary node) to the UE. The UE can monitor the physical downlink control channel (PDCCH) monitoring occasion to obtain the paging configured by the PSCell (or secondary node).

[0127] The allowed CAG list can represent a list of CAG identifiers per PLMN that the UE is allowed to access.

[0128] The CAG cell can refer to a cell that plays at least one CAG identifier.

[0129] The CAG can represent the CAG operating nearby cells, and the CAG can be identified by the CAG ID broadcast by the nearby cells.

[0130] A CAG member cell can mean a cell that broadcasts a selected PLMN, a registered PLMN, or an equivalent PLMN identity for a UE, and for the PLMN, a CAG identifier that belongs to the allowed CAG list of the UE.

[0131] A CAG identifier can be used to identify a CAG within a PLMN.

[0132] A network identifier can be used to identify a SNPN in combination with a PLMN ID.

[0133] An NPN can refer to a network deployed for non-public use.

[0134] A cell for NPN only can refer to a cell that can be used for normal service of NPN users only. An NPN capable UE determines that the cell is a cell for NPN only by detecting that the cellReservedForOtherUse IE is set to true and the npn-IdentityInfoList IE is present in the CellAccessRelatedInfo IE.

[0135] A PNI-NPN ID can mean an identifier of a PNI-NPN composed of a combination of a PLMN ID and a CAG ID.

[0136] A registered SNPN can mean an SNPN that has some location registration result.

[0137] A selected SNPN can mean an SNPN that is manually or automatically selected by a NAS (e.g., a NAS layer of a UE, or a NAS layer of a CN).

[0138] An SNPN access mode can mean an operation mode in which a UE selects only an SNPN.

[0139] An SNPN identity can mean an identifier of an SNPN composed of a combination of a PLMN ID and an NID.

[0140] A cell for SNPN only can refer to a cell that can be used for normal service of SNPN users only.

[0141] An NPN capable UE can mean a UE that supports CAG (or NPN).

[0142] A child node can mean a next hop neighbor node of an IAB-node-DU, wherein the child node is also an IAB-node.

[0143] A parent node can mean a next hop neighbor node of an IAB-node-MT, wherein the parent node can be an IAB-node or an IAB-donor-DU.

[0144] Downstream can mean the direction towards a child node or a UE in an IAB-topology.

[0145] Upstream can mean the direction towards a parent node in an IAB-topology.

[0146] IAB-donor can mean a gNB that provides network access to UEs over backhaul and access links.

[0147] IAB-DU can mean a gNB-DU functionality supported by an IAB-node to terminate NR access interfaces to UEs and next hop IAB-nodes and F1 protocol to gNB-CU functionality defined in 3GPP TS 38.401 v16.1.0.

[0148] IAB-MT can mean an IAB-node functionality that applies procedures and behaviors specified for a UE to terminate Uu interface to a parent node. The IAB-MT functionality used in 38 series of 3GPP specifications corresponds to IAB-UE functionality defined in 3GPP TS 23.501 v16.4.0.

[0149] IAB-node can mean a RAN node that supports NR access links to UEs and NR backhaul links to parent and child nodes. The IAB-node can or can not support backhauling over LTE.

[0150] Multi-hop backhauling can use NR (and / or LTE) backhaul links chains between IAB-nodes and IAB-donor-gNBs.

[0151] NR backhaul link can mean a NR link used for backhauling between IAB-nodes and IAB-donor-gNBs and between IAB-nodes in case of multi-hop backhauling.

[0152] LTE backhaul link can mean a LTE link used for backhauling between IAB-nodes and IAB-donor-gNBs and between IAB-nodes in case of multi-hop backhauling.

[0153] Multi-Radio Dual Connectivity (MR-DC) can mean dual connectivity between E-UTRA and NR nodes or between two NR nodes. MR-DC can include EN-DC, NE-DC, NGEN-DC and NR-DC modes.

[0154] Master Cell Group in MR-DC can mean a group of serving cells associated with a master node (MN) that includes a SpCell (PCell) and optionally one or more SCells.

[0155] A master node can represent in MR-DC a radio access node providing a control plane connection to a core network. The master node can be a master eNB (in EN-DC mode), a master ng-eNB (in NGEN-DC mode) or a master gNB (in NR-DC and NE-DC mode).

[0156] A secondary cell group can represent in MR-DC a group of serving cells associated with a secondary node (SN) comprising a SpCell (PSCell) and optionally one or more SCells.

[0157] A secondary node can represent in MR-DC a radio access node which is not connected to a core network over a control plane and provides additional resources to a UE. The secondary node can be an en-gNB (in EN-DC mode), a secondary ng-eNB (in NE-DC mode) or a secondary gNB (in NR-DC and NGEN-DC mode).

[0158] MeNB can refer to a master eNB, i.e. an eNB acting as a master node associated with a MCG in MR-DC mode.

[0159] SgNB can refer to a secondary gNB, i.e. a gNB acting as a secondary node associated with a SCG in MR-DC mode.

[0160] The first indication can be associated with NR, LTE connected to EPC and / or LTE connected to 5GC. The second indication can be associated with NR, LTE connected to EPC and / or LTE connected to 5GC. The first indication and the second indication can both be associated with the same RAT (e.g. NR, LTE connected to EPC, LTE connected to 5GC) or different RATs. A UE supporting one RAT (e.g. IAB functionality over NR and / or NPN functionality over NR if one RAT is NR) can apply the first indication associated with NR and / or the second indication associated with NR. A UE supporting one RAT can apply or ignore the first indication not associated with NR and / or the second indication not associated with NR.

[0161] In the example mentioned above, the UE can bar the cell for a period of time (e.g. 300s) if the UE considers itself barred by the cell or if the UE bars the cell. In other words, the UE can not consider the cell as a candidate cell for cell (re)selection for a period of time (e.g. 300s).

[0162] In the aforementioned examples, if the UE changes from the SNPN access mode to the PLMN access mode (i.e., the UE leaves the SNPN access mode and does not operate in the SNPN access mode), the UE (of the NAS entity) can release (or delete or discard) the (stored or maintained) list of SNPN IDs.

[0163] In the aforementioned examples, if the UE changes from the PLMN access mode to the SNPN access mode (i.e., the UE enters the SNPN access mode from a state in which the UE does not operate in the SNPN access mode), the UE (of the NAS entity) can release (or delete or discard) the (stored or maintained) list of PLMN IDs.

[0164] DCI can refer to a PDCCH resource with a cyclic redundancy check (CRC) scrambled by a radio network temporary identifier (RNTI). The RNTI can be related to IAB. Additionally, examples regarding DCI can apply to physical signals.

[0165] A MAC CE is a bit string of a length that is byte-aligned (i.e., a multiple of 8 bits).

[0166] In the aforementioned examples, if the UE supporting IAB functionality determines that it is an IAB node or operates as an IAB node, and / or if the UE performs as an IAB node, and / or if the UE operates IAB functionality, the UE can transmit an indication through dedicated signaling to inform the network.

[0167] Figure 3 is a flowchart illustrating a method 300 of performing cell reselection by a UE in an NPN. In act 302, the UE receives, from a first cell, a first information element (e.g., NPN-IdentityInfo IE) including a first network identity (e.g., SNPN ID or PNI-NPN ID) associated with a first indication (e.g., iab-Support IE) through SIB1. In act 304, the UE receives, from a second cell, a second information element including a second network (e.g., PLMN ID) associated with a second indication through SIB1. In act 306, the UE selects one of the first network identity and the second network identity. In act 308, the UE determines whether the first indication is present in the first information element and whether the first network identity is selected by the UE. In act 310, when the first indication is present but the first network identity is not selected by the UE, the UE determines the first cell as barred for cell reselection. In act 312, when the first indication is present and the first network identity is selected by the UE, the UE determines the first cell as a candidate cell for cell reselection.

[0168] In one example, the first indication is used to indicate whether the first cell supports IAB functionality.

[0169] In one example, the first network identity is a NPN identity, which can be a 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.

[0170] In one example, when the first indication is missing (or absent) in the first information element, the UE determines the first cell as prohibited for cell reselection.

[0171] In one example, when the UE selects the first network identity but the first indication is missing (or absent) in the first information element, the UE determines the first cell as prohibited for cell reselection.

[0172] In one example, the UE supports IAB functionality.

[0173] In one example, the NAS layer of the UE transmits the aforementioned third indication to the AS layer of the UE, the third indication indicating that the UE supports IAB functionality, and thus the AS layer of the UE determines that the UE supports IAB functionality when the AS layer of the UE receives the third indication from the NAS layer of the UE.

[0174] In one example, the third indication is associated with a third network identity, which can be a PLMN ID, a SNPN ID, a PNI-NPN ID, a CAG ID, or a NID.

[0175] In one example, when the first indication is present in the first information element, the first indication indicates that the first cell supports IAB functionality.

[0176] In one example, when the UE does not support IAB functionality, the UE ignores the first indication associated with the first network identity.

[0177] In one example, when the UE does not select the second network identity, the UE ignores the second indication associated with the second network identity.

[0178] In one example, when the first indication is present in the first information element and is configured to a first value (e.g., '1' or {true}), the first indication indicates that the first cell supports IAB functionality.

[0179] Figure 4 is a block diagram illustrating a node 400 for wireless communication according to an embodiment of the disclosure.

[0180] As Figure 4As shown, node 400 can include a transceiver 420, a processor 426, a memory 428, one or more presentation components 434, and at least one antenna 436. Node 400 can also include a radio frequency (RF) spectrum band module, a base station communication module, a network communication module, a system communication management module, an input / output (I / O) port, an I / O component, or a power source (not shown in Figure 4

[0181] Each of these components can communicate with one another directly or indirectly, over one or more buses 440. Node 400 can be a UE or a BS that performs various disclosed functions as well as examples of the present disclosure, shown in Figure 3

[0182] Transceiver 420 can have a transmitter 422 (with transmitting circuitry) and a receiver 424 (with receiving circuitry) and can be configured to transmit and / or receive time and / or frequency resource partitioning information. Transceiver 420 can be configured to transmit in different types of subframes and slots, including but not limited to, usable, unusable, and flexible usable subframe and slot formats. Transceiver 420 can be configured to receive data and control channels.

[0183] Node 400 can include a variety of computer-readable media. Computer-readable media can be any media that can be accessed by node 400 and includes both volatile and nonvolatile media, and removable and non-removable media. Computer-readable media can include computer storage media and communication media. Computer storage media includes both volatile and nonvolatile, and removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions.

[0184] Computer storage media includes RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, Digital Versatile Disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices. Computer storage media does not include a propagated data signal.

[0185] ​​Communication media can typically be embodied in a modulated data signal, such as a carrier wave or other transport mechanism, and includes any information delivery media. The term "modulated data signal" can describe a signal that has one or more characteristics set or changed in such a manner as to encode information in the signal. Communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared, and other wireless media. Combinations of the any of the above can also be included within the scope of computer readable media.

[0186] Memory 428 can include computer- storage media in the form of volatile and / or nonvolatile memory. The memory 428 can be removable, non-removable, or a combination thereof. For example, the memory 428 can include solid-state memory, hard drives, optical drives, etc. As shown, the memory 428 can store computer-readable and / or computer- executable instructions 432 (e.g., software code) configured to, when executed, cause the processor 426 (e.g., processing circuitry) to perform various disclosed functions. Alternatively, the instructions 432 can not be directly executable by the processor 426 but be configured to cause the node 400 (e.g., when compiled and executed) to perform various disclosed functions. Figure 4

[0187] The processor 426 can include an intelligent hardware device, a central processing unit (CPU), a microcontroller, an ASIC, etc. The processor 426 can include memory. The processor 426 can process data 430 and instructions 432 received from the memory 428, as well as information received by the transceiver 420, baseband communication module, and / or network communication module. The processor 426 can also process information to be sent to the transceiver 420 for transmission via the antenna 436, and / or information to be sent to a CN for transmission via the network communication module.

[0188] The one or more presentation components 434 can present data in a visual, audible, or tactile format. The presentation components 434 can include a display device, a speaker, a printing component, a vibrating component, etc.

[0189] In accordance with the present disclosure, it is expressly intended that the concepts of the disclosure can be utilized in various ways, including use of any suitable programming or programming technologies for implementing the concepts of the disclosure. In addition, it should be appreciated that the concepts of the disclosure can be practiced in an electrical circuit comprising discrete electronic components, a hybrid circuit that includes both analog and digital components, a digital circuit that includes one or more processors programmed to perform one or more designated functions, or a combination of one or more such electrical circuits. In addition, although the concepts of the disclosure have been disclosed in the context of certain embodiments, it should be recognized that numerous modifications, rearrangements, and substitutions can readily be practiced without departing from the scope of the disclosure.​

Claims

1. A method for a user equipment (UE) to perform cell reselection in a non-public network (NPN), the method comprising: receiving, from a first cell, a first information element through a first system information block 1 (SIB1), the first information element comprising a first network identity associated with a first indication; receiving, from a second cell, a second information element through a second SIB1, the second information element comprising 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; determining the first cell as barred for the cell reselection when the first indication is present in the first information element but the first network identity is not selected by the UE; and determining the first cell as a candidate cell for the cell reselection when the first indication is present in the first information element and the first network identity is selected by the UE, characterized in that the first indication is used to indicate whether the first cell supports integrated access and backhaul (IAB) function, wherein when the first indication is present in the first information element, the first indication indicates that the first cell supports the IAB function; when the first indication is not present in the first information element, the first cell is determined as barred for an IAB node, and the first network identity is a NPN identity, the NPN identity comprising a standalone non-public network (SNPN) identity and a public network integrated non-public network (PNI-NPN) identity, and the second network identity is a public land mobile network (PLMN) identity. 2.The method of claim 1, characterized in that the UE supports the IAB function. the method further comprises:

3. The method of claim 1, wherein, transmitting, by a non-access stratum (NAS) layer of the UE, a third indication to an access stratum (AS) layer of the UE, the third indication indicates that the UE supports the IAB function; and determining, by the AS layer of the UE, that the UE supports the IAB function upon receiving the third indication from the NAS layer of the UE. 4.The method of claim 3, characterized in that the third indication is associated with a third network identity, the third network identity comprising a public land mobile network (PLMN) identity, a standalone non-public network (SNPN) identity, a public network integrated non-public network (PNI-NPN) identity, a closed access group (CAG) identity, and a network identifier (NID). the method further comprises:

5. The method of claim 1, wherein, ignoring the first indication when the UE does not support the IAB function. the method further comprises:

6. The method of claim 1, wherein, ignoring the second indication when the second network identity is not selected by the UE. 7.The method of claim 1, characterized in that when the first indication is present in the first information element and is configured with a first value, the first indication indicates that the first cell supports the IAB function. 8.A user equipment (UE) for performing cell reselection in a non-public network (NPN), the UE comprising: ​ a processor configured to execute a computer-executable program; and a memory coupled to the processor configured to store a computer-executable program, wherein the computer-executable program instructs the processor to: receive, from a first cell, a first information element via a first system information block 1 (SIB1), the first information element comprising a first network identity associated with a first indication; receive, from a second cell, a second information element via a second SIB1, the second information element comprising 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 first network identity is selected by the UE; determine the first cell as barred for the cell reselection when the first indication is present in the first information element but the first network identity is not selected by the UE; and determine the first cell as a candidate cell for the cell reselection when the first indication is present in the first information element 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 backhaul (IAB) functionality, wherein when the first indication is present in the first information element, the first indication indicates that the first cell supports the IAB functionality, and the first network identity is a non-public network (NPN) identity comprising a standalone NPN (SNPN) identity and a public network integrated NPN (PNI-NPN) identity, and the second network identity is a public land mobile network (PLMN) identity.

9. The UE of claim 8, wherein the UE supports the IAB functionality. the computer-executable program further instructs the processor to: transmit, by a non-access stratum (NAS) layer of the UE, a third indication to an access stratum (AS) layer of the UE, the third indication indicating that the UE supports the IAB functionality; and 10. The UE of claim 8, wherein, determine, by the AS layer of the UE, that the UE supports the IAB functionality upon receiving the third indication from the NAS layer of the UE.

11. The UE of claim 10, wherein the third indication is associated with a third network identity comprising a PLMN identity, a SNPN identity, a PNI-NPN identity, a closed access group (CAG) identity, and a network identifier (NID). the computer-executable program further instructs the processor to: ignore the first indication when the UE does not support the IAB functionality.

12. The UE of claim 8, wherein, 13. The UE of claim 8, wherein the computer-executable program further instructs the processor to: ignore the second indication when the second network identity is not selected by the UE. ​ ​ 14. The UE of claim 8, wherein, the first indication indicates that the first cell supports the IAB function when the first indication is present in the first information element and is configured with a first value.

Images