CN114600509B

CN114600509B - Method and apparatus for cell reservation and access restriction

Info

Publication number: CN114600509B
Application number: CN202080075110.8A
Authority: CN
Inventors: 施美如; 曾勇岚; 陈宏镇
Original assignee: FG Innovation Co Ltd
Current assignee: FG Innovation Co Ltd
Priority date: 2019-10-29
Filing date: 2020-10-29
Publication date: 2024-06-07
Anticipated expiration: 2040-10-29
Also published as: CN114600509A; EP4035431A4; WO2021083289A1; US20210127325A1; JP2022553221A; US11589294B2; KR20220083794A; EP4035431A1; TW202126079A

Abstract

A method performed by a User Equipment (UE) for wireless communication is provided. The method comprises the following steps: receiving a Master Information Block (MIB) from a cell, the MIB including a cell barring Information Element (IE); receiving a system information block type 1 (SIB 1) from a cell, the SIB1 including a first non-public network (NPN) Identity (ID), a first cell reservation for an operator use IE associated with the first NPN ID, and a cell reservation for other use IEs; and determining that the cell is considered as a candidate cell for a cell selection or cell reselection procedure when the cell barring IE is "not barred", the cell reservation is not true, the first cell reservation is the operator use IE is "reserved", the first NPN ID matches with the registered independent non-public network (SNPN) ID of the UE, and the access ID of the UE is 11 or 15.

Description

Method and apparatus for cell reservation and access restriction

Cross Reference to Related Applications

The present disclosure requests the benefit and priority of provisional U.S. patent application Ser. No. 62/927,479, entitled "Method and Apparatus for Cell Reservations AND ACCESS Restrictions in Non-Public Network(s)" ("the' 479 provisional"), filed on 10/29 2019. The' 479 provisional disclosure is incorporated herein by reference in its entirety for all purposes.

Technical Field

The present disclosure relates to wireless communications, and in particular, to a method and apparatus for cell reservation and access restriction in a cellular wireless communication network.

Background

Various efforts have been made to improve different aspects of wireless communication of cellular wireless communication systems, such as improving fifth generation (5G) New Radios (NRs) by increasing data rates, delays, reliability and mobility.

The 5G NR system is intended to provide flexibility and configurability to optimize network services and types to accommodate various use cases, such as enhanced mobile broadband (eMBB), large-scale machine type communications (mMTC), and ultra-reliable low-latency communications (URLLC).

However, as the demand for radio access continues to increase, further improvements in the art are needed.

Disclosure of Invention

The present disclosure relates to a method and apparatus for cell reservation and access restriction in a cellular wireless communication network.

According to one aspect of the present disclosure, there is provided a UE comprising one or more non-transitory computer-readable media having computer-executable instructions embodied thereon; and at least one processor coupled to the one or more non-transitory computer-readable media. The at least one processor is configured to execute computer-executable instructions to: receiving a master information block (Master Information Block, MIB) from a cell, the MIB including a cell barring Information Element (IE); receiving a system information block type 1 (System Information Block Type, sib1) from a cell, the SIB1 including a first Non-Public Network (NPN) Identity (ID), a first cell reservation associated with the first NPN ID for an operator use IE and a cell reservation for other use IEs; and determining whether to consider the cell as a candidate cell for a cell selection or cell reselection procedure based on the cell barring IE, the first cell reservation as an operator use IE, and the cell reservation as another use IE, wherein when the cell barring IE is "not barred", the cell reservation as another use IE is not "true", the first cell reservation as an operator use IE is "reserved", the first NPN ID matches the registered SNPN ID of the UE, and the access ID of the UE is 11 or 15, the UE considers the cell as the candidate cell for a cell selection or cell reselection procedure.

According to another aspect of the present disclosure, a method performed by a UE for wireless communication is provided. The method comprises the following steps: receiving a MIB from a cell, the MIB including a cell barring IE; receiving SIB1 from a cell, the SIB1 including a first NPN ID, a first cell reservation for an operator use IE and a cell reservation for other use IEs associated with the first NPN ID; and determining whether to consider the cell as a candidate cell for a cell selection or cell reselection procedure based on a cell barring IE, a first cell reservation as an operator use IE, and a cell reservation as another use IE, wherein when the cell barring IE is "not barred", the cell reservation as another use IE is not "true", the first cell reservation as an operator use IE is "reserved", the first NPN ID matches with the registered SNPN ID of the UE, and the access ID of the UE is 11 or 15, the UE regards the cell as the candidate cell for the cell selection or cell reselection procedure.

Drawings

Aspects of the disclosure are best understood from the following detailed disclosure when read with the accompanying drawing figures. The various features are not drawn to scale. The dimensions of the various features may be arbitrarily increased or decreased for clarity of discussion.

Fig. 1 is a flowchart illustrating a method performed by a UE for cell reservation and access restriction according to an example embodiment of the present disclosure.

Fig. 2 is a flowchart illustrating a method performed by a UE for determining whether to consider a cell as a candidate cell or a forbidden cell according to an example embodiment of the present disclosure.

Fig. 3 is a flowchart illustrating a method performed by a UE for determining whether to consider a cell as a candidate cell or a forbidden cell according to another example embodiment of the present disclosure.

Fig. 4 is a block diagram illustrating a node for wireless communication in accordance with various aspects of the disclosure.

Detailed Description

In order to meet the requirements of the vertical industry for low latency, high reliability, support for 5G local area network (Local Area Network, LAN) type services, private wireless networks (e.g., private networks) have attracted attention to be introduced into the next generation cellular networks.

A private network (e.g., NPN) may support both vertical services and LAN services. The private Network may be divided into a Stand-Alone Non-Public Network (SNPN) and a Public Network integrated Non-Public Network (Public Network Integrated Non-Public Network, PNI-NPN). Operators may focus on PNI-NPN solutions applicable to a wide range of use cases, such as at home office (Small Office Home Office, SOHO) and residential, private network coverage deployments, etc.

The 5G system may be enhanced to support NPN. Two network Identifications (IDs) are introduced for NPN: network ID (NID) and closed access group (Closed Access Group, CAG) ID. The 5G radio access network (Radio Access Network, RAN) may also implement NPN by enhancing features such as non-public network identification, discovery, selection/reselection, access control, and mobility restrictions.

For RAN sharing, the network deployment may be different. The cell may be operated by public network(s) (e.g., public land mobile network(s) (Public Land Mobile Network, PLMN) owned by a legacy operator) and private network(s) (e.g., SNPN and PNI-NPN(s) owned by an operator or enterprise). The UE may be a legacy UE that does not support NPN features, an advanced UE that supports NPN features, or an advanced UE that does not support NPN features. Thus, mechanisms for cell reservation and access restriction performed by a UE are disclosed to treat the correct cell as a candidate cell for a cell (re) selection procedure.

The following contains specific information pertaining to embodiments in the present disclosure. The drawings and their accompanying detailed description are directed to merely embodiments. However, the disclosure is not limited to such embodiments. Other variations and implementations of the present disclosure will be apparent to those skilled in the art.

Similar or corresponding elements in the drawings may be denoted by similar or corresponding reference numerals unless otherwise specified. Moreover, the drawings and illustrations in the present disclosure are generally not drawn to scale and are not intended to correspond to actual relative dimensions.

For consistency and ease of understanding, similar features (although not shown in some examples) may be identified by the same numerals in the drawings. However, the features in the different embodiments may be different in other respects, and should not be narrowly limited to the features shown in the drawings.

The phrase "in one embodiment" or "in certain embodiments" may refer to one or more of the same or different embodiments, respectively. The term "coupled" is defined as directly or indirectly connected through intervening components, not necessarily limited to physical connections. The term "comprising" means "including but not limited to," and specifically means open ended or members of the disclosed combinations, groups, families, and equivalents. "A, B and C" or "at least one of: A. b and C "means" A alone, or B alone, or C alone, or any combination of A, B and C ".

The terms "system" and "network" may be used interchangeably. The term "and/or" is used merely to reveal an association of associated objects and to indicate that three relationships may exist, such that a and/or B may indicate that a exists alone, that a and B exist together, or that B exists alone. "A and/or B and/or C" may mean that at least one of A, B and C is present. The character "/" generally indicates that the associated object is in an "or" relationship.

For purposes of non-limiting explanation, specific details are set forth such as functional entities, techniques, protocols, standards, etc. to provide an understanding of the disclosed techniques. In other instances, detailed disclosure of well-known methods, techniques, systems, architectures, and equivalents have been omitted so as not to obscure the disclosure with unnecessary detail.

Those of skill in the art will immediately recognize that any network function(s) or algorithm(s) can be implemented by hardware, software, or a combination of software and hardware. The disclosed functions may correspond to modules, which may be software, hardware, firmware, or any combination thereof.

The software implementation may include computer-executable instructions stored on a computer-readable medium such as memory or other type of storage device. One or more microprocessors or general purpose computers with communication processing capabilities may be programmed with corresponding executable instructions and perform the disclosed network function(s) or algorithm(s).

The microprocessor or general purpose computer may be comprised of application specific integrated circuits (ASICs SPECIFIC INTEGRATED Circuitry), programmable logic arrays, and/or using one or more digital signal processors (DIGITAL SIGNAL processors, DSPs). While some of the disclosed example embodiments are directed to software installed and executed on computer hardware, alternative example embodiments implemented as firmware or as hardware or a combination of hardware and software are within the scope of the disclosure. Computer-readable media includes, but is not limited to, random access Memory (Random Access Memory, RAM), read-Only Memory (ROM), erasable programmable Read-Only Memory (Erasable Programmable Read-Only Memory, EPROM), electrically erasable programmable Read-Only Memory (ELECTRICALLY ERASABLE PROGRAMMABLE READ-Only Memory, EEPROM), flash Memory, compact disc Read-Only Memory (Compact Disc 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, such as a long term evolution (Long Term Evolution, LTE) system, an LTE-Advanced (LTE-a) system, an LTE-Advanced Pro system, or a 5G NR RAN, typically includes at least one Base Station (BS), at least one UE, and one or more optional network elements that provide connectivity within the network. The UE communicates with a Network, such as a Core Network (CN), evolved packet Core (Evolved Packet Core, EPC) Network, evolved universal terrestrial RAN (Evolved Universal TERRESTRIAL RAN, E-UTRAN), next-Generation Core (NGC), 5G Core (5G Core,5 gc), or the internet, via a RAN established by one or more BSs.

The UE may include, but is not limited to, a mobile station, a mobile terminal or device, a user communication radio terminal. For example, the UE may be a portable radio, including but not limited to a mobile phone, tablet, wearable device, sensor, or Personal digital assistant (Personal DIGITAL ASSISTANT, PDA) with wireless communication capabilities. The UE may be configured to receive signals over an air interface and to transmit signals to one or more cells in the RAN.

The BS may be configured to provide communication services according to at least one of the following radio access technologies (Radio Access Technology, RAT): global microwave access interoperability (Worldwide Interoperability for Microwave Access, wiMAX), global system for mobile communications (Global System for Mobile communication, GSM), commonly referred to as 2G, GSM enhanced data rates for GSM evolution (GSM ENHANCED DATA RATES for GSM Evolution RAN, GERAN), general packet Radio Service (GENERAL PACKET Radio Service, GPRS), universal mobile communications system, commonly referred to as 3G, based on Wideband-Code Division Multiple Access, W-CDMA (Universal Mobile Telecommunication System, UMTS), high-speed packet access (High-SPEED PACKET ACCESS, HSPA), LTE-A, LTE, evolved/enhanced LTE (ENHANCED LTE, ELTE) for 5GC, NR (commonly referred to as 5G) and/or LTE-a Pro. However, the scope of the present disclosure should not be limited to the above protocols.

The BSs may include, but are not limited to, node BS (NB) in UMTS, evolved Node BS (eNB) in LTE or LTE-a, radio network controllers (Radio Network Controller, RNC) in UMTS, base station controllers (Base Station Controller, BSC) in GSM/GERAN, evolved universal terrestrial radio access (Evolved Universal Terrestrial Radio Access, E-UTRA) in BS with 5GC connection, next generation enbs (ng-enbs), next generation Node BS (next-generation Node B, gNB) in 5G-RAN (or 5G access network, 5G-AN), and any other device capable of controlling radio communications and managing radio resources within a cell. The BS may serve one or more UEs over a radio interface.

The BS may be operable to provide radio coverage to a particular geographic area using a plurality of cells included within the RAN. The BS may support operation of the cell. Each cell may be operable to provide service to at least one UE within its radio coverage area.

Each cell (commonly referred to as a serving cell) may provide services to serve one or more UEs within its radio coverage area such that each cell schedules Downlink (DL) resources and optional Uplink (UL) resources to at least one UE within its radio coverage area for DL and optional UL packet transmissions. The BS may communicate with one or more UEs in a radio communication system via a plurality of cells.

The cells may allocate side link (Sidelink, SL) resources to support proximity services (Proximity Service, proSe), LTE SL services, and/or LTE/NR internet of vehicles (V2X) services. Each cell may have a coverage area overlapping with other cells. In the case of Multi-RAT dual connectivity (Multi-RAT Dual Connectivity, MR-DC), the primary cell of the primary cell Group (MASTER CELL Group, MCG) or the secondary cell Group (Secondary Cell Group, SCG) may be referred to as a specific cell (SPECIAL CELL, SPCELL). The primary cell (PRIMARY CELL, PCELL) may refer to the SpCell of the MCG. The primary SCG cell (PRIMARY SCG CELL, PSCELL) may refer to the SpCell of the SCG. MCG may refer to a set of serving cells associated with a Master Node (MN), including a SpCell and optionally one or more Secondary cells (scells). SCG may refer to a set of serving cells associated with a Secondary Node (SN), including a SpCell and optionally one or more scells.

As previously disclosed, the frame structure of NR supports flexible configuration to accommodate various next generation (e.g., 5G) communication requirements, such as eMBB, emtc, and URLLC, while meeting high reliability, high data rate, and low latency requirements. Orthogonal frequency division multiplexing (Orthogonal Frequency-Division Multiplexing, OFDM) techniques agreed in the third generation partnership project (3 GPP) may be used as a baseline for the NR waveforms. An extensible OFDM parameter set such as adaptive subcarrier spacing, channel bandwidth and Cyclic Prefix (CP) may also be used.

Two code schemes are applied to the NR: low density parity Check codes (Low-DENSITY PARITY-Check, LDPC) and polarization codes. Coding scheme adaptation may be configured based on channel conditions and/or service applications.

At least DL Transmission data, a guard period, and UL Transmission data should be included in a Transmission time interval (Transmission TIME INTERVAL, TTI) of a single NR frame. The various parts of DL transmission data, guard period and UL transmission data should also be configured based on network dynamics such as NR. SL resources may also be provided in NR frames to support ProSe services or V2X services.

Multiple PLMNs may operate on unlicensed spectrum. Multiple PLMNs may share the same unlicensed carrier. PLMNs may be public or private. The public PLMN may be, but is not limited to, an operator or virtual operator providing radio services to public subscribers. The public PLMN may possess licensed spectrum and may also support radio access technologies on the licensed spectrum. The private PLMN may be, but is not limited to, a mini-operator, factory, or enterprise that provides radio services to its private users (e.g., employees or machines). In some embodiments, the public PLMN may support more deployment scenarios (e.g., carrier aggregation (Carrier Aggregation, CA) between licensed band NR (PCell) and NR unlicensed (NR-U) (SCell), dual connectivity (Dual Connectivity, DC) between licensed band LTE (PCell) and NR-U (PSCell), independent NR-U, NR cells with DL in unlicensed band and UL in licensed band, DC between licensed band NR (PCell) and NR-U (PSCell). In some embodiments, the private PLMN primarily supports, but is not limited to, independent unlicensed radio access technologies (e.g., independent NR-us).

NPN scene

The NPN scenario may be SNPN, which may be operated by the NPN operator and is independent of the network functions provided by the PLMN. The NPN scenario may be PNI-NPN, which may be NPN deployed under support of PLMN. SNPN(s) may be identified by one SNPN ID, where SNPN ID may include PLMN IDs and/or Network IDs (NIDs) and be broadcast in SIB1 of SNPN enabled cells. The PNI-NPN may be identified by a PNI-NPN ID, which may include a PLMN ID and/or a closed access group (Closed Access Group, CAG) ID, and broadcast in SIB1 of a cell supporting the PNI-NPN feature. The NPN ID may be SNPN ID or PNI-NPN ID. In one embodiment, the cell may broadcast PLMN ID(s) and/or NID(s) in a first list in a first IE, may broadcast PLMN ID(s) in a second list in a second IE, and may broadcast PLMN ID(s) and/or CAG ID(s) in a third list in a third IE, where the first IE, second IE, and third IE may be located in SIB 1. In one embodiment, the cell may broadcast the PLMN ID(s), PLMN ID(s) and/or NID(s), and PLMN ID(s) and/or CAG ID(s) in SIB1 in a first list in the first IE. In one embodiment, the cell may broadcast the PLMN ID(s) in a first list in a first IE and broadcast the PLMN ID(s) and/or NID(s) and PLMN ID(s) and/or CAG ID(s) in a second list in a second IE, wherein the first IE and the second IE may be located in SIB 1.

Considering that RAN sharing may be supported in the next generation cellular network, RAN sharing between PLMNs and NPN may include the following "cell type" variants:

case 1-1: a cell may be shared (operated) by multiple PLMNs. The maximum number of PLMNs for the shared cell may be, but is not limited to, 12.

Cases 1-2: the cell may be shared (operated) by a plurality SNPN. In one embodiment, these SNPN may share a common PLMN ID, but are identified by different NIDs. In one embodiment, these SNPN may be identified by different PLMN IDs and by the same (or different) NIDs. In one embodiment, these SNPN may be identified by different NIDs, but no PLMN ID is used for identification. In one embodiment, these SNPN may be identified by different PLMN IDs and no NID is used for identification. The maximum number of SNPN shared cells may be, but is not limited to, 12. In one embodiment, the combination of PLMN ID and/or NID may uniquely identify SNPN.

In one embodiment, the cell supporting the NPN feature (or SNPN only) may not broadcast the NID(s). A cell supporting the NPN feature (or SNPN only) may broadcast an indicator that supports NPN (or SNPN only) to indicate that the cell supports NPN functions (or SNPN only). The NPN function (or SNPN function only) may be applicable to the PLMN identified by the PLMN ID(s) broadcast by the cell. A UE with a registered PLMN ID and/or NID (or with a PLMN ID and/or CAG ID) may consider a cell with an NPN-enabled indicator (or an indicator of SNPN only) as a candidate cell for cell (re) selection. A UE with a registered PLMN ID and/or NID (or with a PLMN ID and/or CAG ID) may consider the following cells as candidate cells for cell (re) selection: the cell broadcasts an indicator supporting NPN (or an indicator supporting SNPN only) and a PLMN ID matching the registered PLMN ID of the UE. In one embodiment, a UE with a registered PLMN ID and/or a registered NID may consider the following cells as candidate cells for cell (re) selection: the cell broadcasts an indicator supporting NPN (or an indicator supporting SNPN only) and PLMN IDs and/or NIDs that match the registered PLMN IDs and/or registered NIDs of the UE. In one embodiment, a UE with a registered PLMN ID and/or a registered CAG ID may consider the following cells as candidate cells for cell (re) selection: the cell broadcasts an indicator supporting NPN (or an indicator supporting SNPN only) and PLMN IDs and/or CAG IDs that match the registered PLMN IDs and/or registered CAG IDs of the UE. Registered SNPN ID may refer to a registered PLMN ID and/or a registered NID. The registered PNI-NPN ID may refer to a registered PLMN ID and/or a registered CAG ID.

Cases 1-3: a cell may be shared (operated) by multiple PNI-NPN. In one embodiment, these PNI-NPN may share a common PLMN ID, but are identified by different CAG IDs. In one embodiment, these PNI-NPN may be identified by different PLMN IDs and the same (or different) CAG IDs. In one embodiment, these PNI-NPN may be identified by different CAG IDs, but no PLMN ID is used for identification. In one embodiment, these PNI-NPN may be identified by different PLMN IDs, but no CAG IDs are used for identification. The maximum number of PNI-NPN sharing a cell may be, but is not limited to, 12. In one embodiment, the combination of PLMN IDs and/or CAG IDs may uniquely identify the PNI-NPN.

In one embodiment, the cells supporting NPN features (or CAGs only) may not broadcast the CAG ID(s). A cell supporting the NPN feature (or CAG only) may broadcast an indicator supporting NPN (or CAG only) to indicate that the cell supports NPN functionality (or CAG only). The NPN function (or CAG-only function) may be applicable to the PLMN identified by the PLMN ID(s) broadcast by the cell. A UE with a registered PLMN ID and/or CAG ID (or with a PLMN ID and/or NID) may consider a cell with an NPN-enabled indicator (or a CAG-only indicator) as a candidate cell for cell (re-) selection. A UE with registered PLMN IDs and/or CAG IDs (or with PLMN IDs and/or NIDs) may consider the following cells as candidate cells for cell (re) selection: the cell broadcasts an indicator supporting NPN (or an indicator supporting CAG only) and a PLMN ID matching the registered PLMN ID of the UE. In one embodiment, a UE with a registered PLMN ID and/or a registered NID may consider the following cells as candidate cells for cell (re) selection: the cell broadcasts an indicator that supports NPN (or an indicator that supports CAG only) and a PLMN ID and/or NID that matches the registered PLMN ID and/or registered NID of the UE. In one embodiment, a UE with a registered PLMN ID and/or a registered CAG ID may consider the following cells as candidate cells for cell (re) selection: the cell broadcasts an indicator that supports NPN (or an indicator that supports CAG only) and a PLMN ID and/or CAG ID that matches the registered PLMN ID and/or registered CAG ID of the UE.

Cases 1-4: the cells may be shared (operated) by at least one PLMN and at least one SNPN. The maximum number of PLMNs and SNPN for the shared cell may be, but is not limited to, 12.

Cases 1-5: a cell may be shared (operated) by at least one PLMN and at least one PNI-NPN. The maximum number of PLMNs and PNI-NPN sharing a cell may be, but is not limited to, 12.

Cases 1-6: a cell may be shared (operated) by at least one PLMN and at least one SNPN and at least one PNI-NPN. The maximum number of PLMNs, SNPNs, and PNI-NPN of the shared cell may be (but is not limited to) 12.

Although RAN sharing is not supported, different network types may include the following "cell type" variants:

Cases 1-7: a cell may only be operated by the PLMN(s).

Cases 1-8: the cell may be operable only by SNPN(s).

Cases 1-9: a cell may be operable only by PNI-NPN(s).

In one embodiment, the cells supporting (at least) SNPN may be cells operated only by SNPN(s), cells shared by at least one PLMN and at least one SNPN, cells shared by at least one PLMN and at least one SNPN and at least one PNI-NPN, or cells shared by at least one SNPN and at least one PNI-NPN. In one embodiment, the cell supporting (at least) PNI-NPN may be a cell operated only by PNI-NPN(s), a cell shared by at least one PLMN and at least one PNI-NPN, a cell shared by at least one PLMN and at least one SNPN and at least one PNI-NPN, or a cell shared by at least one SNPN and at least one PNI-NPN. In one embodiment, the cells supporting (at least) the PLMN may be cells operated only by the PLMN(s), cells shared by at least one PLMN and at least one PNI-NPN, cells shared by at least one PLMN and at least one SNPN and at least one PNI-NPN, or cells shared by at least one SNPN and at least one PLMN.

From the perspective of the UE, with the advent of NPN network(s), the "UE type" may include the following variants:

Case 2-1: the UE may support only legacy networks (without NPN features) (e.g., 3GPP Rel-15 UE supports Rel-15 features). The Rel-15 feature may not include NPN network(s). Such a UE may not have SNPN functions. The UE may not have CAG functionality.

Case 2-2: the UE may support only the PLMN feature in a network supporting the NPN feature or in a network supporting both the NPN feature and the PLMN feature. For example, even though 3GPP Rel-16 supports NPN features, 3GPP Rel-16 UE may not support NPN features. The UE may camp on and/or access cells supporting at least the PLMN. The UE may not have SNPN functions. The UE may not have CAG functionality.

Cases 2-3: the UE may support only SNPN networks. For example, the UE may support SNPN access modes only. The UE may camp on and/or access cells supporting at least SNPN. The UE may support SNPN functions.

Cases 2-4: the UE may support only PNI-NPN networks. For example, the UE may support only PNI-NPN access mode. The UE may camp on and/or access cells supporting at least PNI-NPN. The UE may support CAG functions.

Cases 2-5: the UE may support both PLMN and SNPN networks. For example, the UE may support PLMN network access mode and SNPN access mode. The UE may camp on and/or access cells supporting at least SNPN or cells supporting at least PLMNs. The UE may support SNPN functions

Cases 2-6: the UE may support a PLMN network and a PNI-NPN network. For example, the UE may support PLMN network access mode and PNI-NPN access mode. The UE may camp on and/or access cells supporting at least PLMNs or cells supporting at least PNI-NPN. The UE may support CAG functions.

Cases 2-7: the UE may support both SNPN and PNI-NPN networks. For example, the UE may support SNPN access modes and PNI-NPN access modes. The UE may camp on and/or access cells supporting at least SNPN or cells supporting at least PNI-NPN. The UE may support SNPN functions. The UE may support CAG functions.

Cases 2-8: the UE may support a PLMN network, SNPN network, and PNI-NPN network. For example, the UE may support PLMN access mode, SNPN access mode, and PNI-NPN access mode. The UE may camp on and/or access cells supporting at least PLMNs, cells supporting at least SNPN, or cells supporting at least PNI-NPN. The UE may support SNPN functions. The UE may support CAG functions.

In one embodiment, the UE supporting (at least) SNPN features (or the UE with registered (or selected) SNPN features) may be a UE supporting only SNPN features, a UE supporting both SNPN features and PNI-NPN features, a UE supporting both SNPN features and PLMN features, or a UE supporting PLMN features, SNPN features and PNI-NPN features. A UE supporting (at least) SNPN features may operate in a cell supporting (at least) SNPN features. A UE supporting (at least) PNI-NPN features may operate in a cell supporting (at least) PNI-NPN features. A UE supporting (at least) PLMN features may operate in a cell supporting (at least) PLMN features. A UE with registered SNPN may mean that the UE has registered SNPN ID (stored in the non-access stratum (NAS) of the UE) and/or that the UE has registered SNPN ID with the network. A UE with a selected SNPN may mean that the UE (e.g., by the NAS of the UE) has selected SNPN identified by the selected SNPN ID and/or that the UE has stored the selected SNPN ID in the NAS of the UE. In one embodiment, a UE supporting (at least) PNI-NPN features (or a UE with registered (or selected) PNI-NPN features) may be a UE supporting only PNI-NPN features, a UE supporting both SNPN features and PNI-NPN features, a UE supporting both PNI-NPN features and PLMN features, or a UE supporting PLMN features, SNPN features and PNI-NPN features. A UE with a registered PNI-NPN may mean that the UE has a registered PNI-NPN ID (stored in the NAS of the UE) and/or that the UE has registered a registered PNI-NPN ID with the network. A UE having a selected PNI-NPN may mean that the UE (e.g., by the NAS of the UE) has selected a PNI-NPN identified by the selected PNI-NPN ID and/or that the UE has stored the selected PNI-NPN ID in the NAS of the UE. In one embodiment, the UE supporting (at least) PLMN features (or the UE with registered (or selected) PLMNs) may be a UE supporting legacy networks (e.g., networks without NPN features), a UE supporting only PLMN features in a network supporting NPN features, a UE supporting both PLMN features and SNPN features, a UE supporting both PLMN features and PNI-NPN features, or a UE supporting PLMN features, SNPN features and PNI-NPN features. A UE with a registered PLMN may mean that the UE has a registered PLMN ID (stored in the NAS of the UE) and/or that the UE has registered a registered PLMN ID with the network. A UE having a selected PLMN may mean that the UE (e.g., by the NAS of the UE) has selected a PLMN identified by the selected PLMN ID and/or that the UE has stored the selected PLMN ID in the NAS of the UE.

Cell barring information

In one embodiment, the cell may broadcast cell barring information, which may be a cell barring IE in the MIB message. In one implementation, the cell barring IE may be in an enumerated (ENUMERATED) { "barred", "not barred" } format.

In one embodiment, the value "forbidden" may mean that for a UE without NPN characteristics, the cell is forbidden for all PLMN(s) supported by the cell. In one embodiment, the value "forbidden" may mean that for a UE with NPN characteristics, a cell is forbidden for all NPN(s) supported by the cell. In one embodiment, the value "forbidden" may mean that for a UE with NPN characteristics, a cell is forbidden for all PLMN(s) supported by the cell.

In one embodiment, the value "forbidden" may mean that for a UE with/without NPN features, a cell is forbidden for all PLMN(s) supported by the cell. In one embodiment, the value "forbidden" may not mean that for a UE with NPN characteristics, a cell is forbidden for all NPN(s) supported by the cell. In one embodiment, a UE with a registered (or selected) SNPN/PNI-NPN may ignore cell barring information.

In one embodiment, the value "forbidden" may mean that for a UE with/without NPN features, a cell is forbidden for all PLMN(s) supported by the cell. In one embodiment, the value "forbidden" may not mean that for a UE with NPN characteristics, a cell is forbidden for all NPN(s) supported by the cell. In one embodiment, a UE with a registered (or selected) SNPN/PNI-NPN may read SIB1 to further check if the UE is barred from accessing the cell. For example, the UE may consider the cell barring information in combination with PLMN IDs and/or CAG IDs broadcast by the cell to determine whether the UE is barred from accessing the cell. For example, the UE may consider the cell barring information in combination with the PLMN ID and/or NID broadcast by the cell to determine whether the UE is barred from accessing the cell.

In one embodiment, when the UE prohibits itself from accessing the cell, the UE may not consider the cell as a candidate cell during the cell (re) selection procedure, and the UE may neither (re) select nor camp on the cell. When the UE does not prohibit itself from accessing the cell, the UE may treat the cell as a candidate cell in a cell (re) selection procedure, and the UE may (re) select or camp on the cell.

In one embodiment, when the UE ignores the cell barring information (or cell reservation for other use IEs, or cell reservation for operator use IEs), the UE may prohibit itself from accessing the cell, (re) select the cell or camp on the cell, irrespective of the cell barring information (or cell reservation for other use IEs, or cell reservation for operator use IEs). In one embodiment, when the UE ignores the cell barring information (or cell reservation for other use IEs, or cell reservation for operator use IEs), the UE may act without based on the cell barring information (or cell reservation for other use IEs, or cell reservation for operator use IEs).

Case 3-1: cell broadcast cell barring information supporting (at least) PLMN

In one embodiment, if the cell supports (at least) PLMN features, the cell barring information may be common to all PLMNs, SNPNs, and/or PNI-NPN operating the cell. The cell may broadcast in system information (e.g., SIB1, other SI) PLMN ID(s) identifying supported PLMN(s), PLMN ID(s) and/or NID(s) identifying supported SNPN(s), and/or PLMN ID(s) and/or CAG ID(s) identifying supported PNI-NPN(s).

In some implementations, if the cell barring information broadcast by the cell (e.g., in the MIB) is "barred", a UE supporting SNPN features (or a UE with registered (or selected) SNPN) may receive SIB1. For example, a UE supporting SNPN features (or a UE with registered (or selected) SNPN) may need PLMN information and/or NID(s) in SIB1 broadcast by the cell to determine whether SNPN features in the cell are barred or whether the cell is barred for the UE.

In some implementations, a PNI-NPN enabled UE (or a UE with a registered (or selected) PNI-NPN) may receive SIB1 if the cell barring information broadcast by the cell (e.g., in the MIB) is "barred". For example, a PNI-NPN enabled UE (or a UE with registered (or selected) PNI-NPN) may need PLMN information and/or CAG ID(s) in SIB1 broadcast by the cell to determine whether PNI-NPN features in the cell are barred or whether the cell is barred for the UE.

In some embodiments, if the cell barring information broadcast by a cell (e.g., in MIB) is "barred", UEs that do not support SNPN features and/or that do not support PNI-NPN features may exclude the cell as a candidate cell for cell selection/reselection without receiving SIB 1.

In one embodiment, if the cell barring information (e.g., in MIB) broadcast by a cell is barred, a UE having a registered (or selected) specific ID that matches a corresponding specific ID indicated in system information (e.g., SIB1, other SI) may barre itself from accessing the cell. The UE may neither (re) select nor camp on the cell. On the other hand, a UE with a registered (or selected) specific ID that does not match the corresponding specific ID indicated in the system information (e.g., SIB1, other SI) may not prohibit itself from accessing the cell. The UE may consider this cell as a candidate cell for cell (re-) selection. The UE may (re) select or camp on the cell. In another embodiment, a UE having a registered (or selected) specific ID that does not match a corresponding specific ID indicated in system information (e.g., SIB1, other SI) may ignore cell barring information. The UE may prohibit itself from accessing the cell, reselect the cell or camp on the cell, irrespective of the cell prohibit information. The term "specific ID" in the present disclosure may include at least one of a PLMN ID, a combination of at least one of a PLMN ID and a NID, and a combination of at least one of a PLMN ID and a CAG ID. For example, the "specific IDs" may be one or more PLMN IDs, one or more NIDs, one or more CAGs, one or more pairs of PLMN IDs and NIDs, one or more pairs of PLMN IDs and CAGs, and any combination thereof.

In one embodiment, if the cell barring information (e.g., in MIB) broadcast by the cell is "not barred", a UE having a registered (or selected) specific ID that matches a corresponding specific ID indicated in the system information (e.g., SIB1, other SI) may not barre itself from accessing the cell. The UE may consider this cell as a candidate cell for cell (re-) selection. The UE may (re) select or camp on the cell. On the other hand, a UE with a registered (or selected) specific ID that does not match the corresponding specific ID indicated in the system information (e.g., SIB1, other SI) may prohibit itself from accessing the cell. The UE may neither (re) select nor camp on the cell. In another embodiment, a UE having a registered (or selected) specific ID that does not match a corresponding specific ID indicated in system information (e.g., SIB1, other SI) may ignore cell barring information. The UE may prohibit itself from accessing the cell, reselect the cell or camp on the cell, irrespective of the cell prohibit information.

In one embodiment, if the cell barring information broadcast by the cell (e.g., in the MIB) is "barred", UEs that support only legacy networks (without NPN features) (e.g., UEs that do not support NPN features, UEs that support only legacy features that do not include NPN features (e.g., prior to Rel-16)) may barre themselves from accessing the cell. The UE may neither (re) select nor camp on the cell. For other UEs supporting features other than legacy networks (e.g., NPN features), these UEs may prohibit themselves from accessing the cell if they determine that their registered (or selected) specific ID(s) match the corresponding specific ID(s) indicated in the system information. They may not be (re) selected or camp on the cell. For other UEs supporting features other than legacy networks (e.g., NPN features), these UEs may not prohibit themselves from accessing the cell if they determine that their registered (or selected) specific ID(s) does not match the corresponding specific ID(s) indicated in the system information. They may consider the cell as a candidate cell for cell (re-) selection. They may be (re) selected or camp on the cell. For other UEs supporting features other than legacy networks (e.g., NPN features), these UEs may ignore the cell barring information if they determine that their registered (or selected) specific ID(s) do not match the corresponding specific ID(s) indicated in the system information. They may prohibit themselves from accessing the cell, (re) selecting or camping on the cell.

In one embodiment, if the cell barring information broadcast by the cell (e.g., in the MIB) is "not barred," UEs that support only legacy networks (without NPN features) (e.g., UEs that do not support NPN features, UEs that support only legacy features that do not include NPN features (e.g., prior to Rel-16)) may not barre themselves from accessing the cell. The UE may consider this cell as a candidate cell for cell (re-) selection. The UE may (re) select or camp on the cell. For other UEs supporting features other than legacy networks (e.g., NPN features), these UEs may not prohibit themselves from accessing the cell if they determine that their registered (or selected) specific ID(s) match the corresponding specific ID(s) indicated in the system information. The UE may consider this cell as a candidate cell for cell (re-) selection. They may be (re) selected or camp on the cell. For other UEs supporting features other than legacy networks (e.g., NPN features), these UEs may prohibit themselves from accessing the cell if they determine that their registered (or selected) specific ID(s) do not match the corresponding specific ID(s) indicated in the system information. They may neither (re) select nor camp on the cell. For other UEs supporting features other than legacy networks (e.g., NPN features), these UEs may ignore the cell barring information if they determine that their registered (or selected) specific ID(s) do not match the corresponding specific ID(s) indicated in the system information. They may prohibit themselves from accessing the cell, (re) selecting or camping on the cell.

In one embodiment, if the cell barring information broadcast by a cell is "barred", a UE supporting (at least) PLMN features, a UE supporting (at least) SNPN features, or a UE supporting (at least) PNI-NPN features may barre itself from accessing the cell. The UE may neither (re) select nor camp on the cell.

In one embodiment, if the cell barring information broadcast by a cell is "not barred", a UE supporting (at least) PLMN features, a UE supporting (at least) SNPN features, or a UE supporting (at least) PNI-NPN features may not barre itself from accessing the cell. The UE may (re) select or camp on the cell.

In one embodiment, if the cell barring information broadcast by a cell is "barred," a UE that supports only legacy networks (e.g., a UE that does not support NPN features, a UE that supports only legacy features that do not include NPN features (e.g., prior to Rel-16)) may prohibit itself from accessing the cell. The UE may neither (re) select nor camp on the cell. For other UEs (e.g., UEs supporting features other than legacy networks (e.g., NPN features), the UE may prohibit itself from accessing the cell if the UE supports (at least) the PLMN, supports (at least) SNPN, or supports (at least) PNI-NPN. The UE may neither (re) select nor camp on the cell. In another embodiment, for other UEs (e.g., UEs supporting features other than legacy networks (e.g., NPN features), the UE may ignore the cell barring information if the UE supports (at least) PLMN features, supports (at least) SNPN features, or supports (at least) PNI-NPN features. The UE may prohibit itself from accessing the cell, (re) selecting or camping on the cell.

In one embodiment, if the cell barring information broadcast by the cell is "not barred", UEs supporting only legacy networks (without NPN features) (e.g., UEs not supporting NPN features, UEs supporting only legacy features not including NPN features (e.g., prior to Rel-16)) may not barre themselves from accessing the cell. The UE may (re) select or camp on the cell. For other UEs (e.g., UEs supporting features other than legacy networks (e.g., NPN features), the UE may not prohibit itself from accessing the cell if the UE supports (at least) PLMN features, supports (at least) SNPN features, or supports (at least) PNI-NPN features. The UE may (re) select or camp on the cell. In another embodiment, for other UEs (e.g., UEs supporting features other than legacy networks (e.g., NPN features), the UE may ignore the cell barring information if the UE supports (at least) PLMN features, supports (at least) SNPN features, or supports (at least) PNI-NPN features. The UE may prohibit itself from accessing the cell, (re) selecting or camping on the cell.

In one embodiment, if the cell barring information broadcast by the cell is "barred", a UE that supports only legacy networks (without NPN features) (e.g., a UE that does not support NPN features, a UE that supports only legacy features that do not include NPN features (e.g., prior to Rel-16)), or a UE that has a registered (or selected) PLMN and supports a network that includes NPN features may barre itself from accessing the cell. The UE may neither (re) select nor camp on the cell. In another embodiment, if the cell barring information broadcast by a cell is "barred," a UE with registered (or selected) SNPN/PNI-NPN or a UE supporting SNPN features and/or PNI-NPN features may barre itself from accessing the cell. The UE may neither (re) select nor camp on the cell. In another embodiment, if the cell barring information broadcast by the cell is "barred", a UE with registered (or selected) SNPN/PNI-NPN or a UE supporting SNPN features and/or PNI-NPN features may ignore the cell barring information. The UE may prohibit itself from accessing the cell, (re) selecting or camping on the cell.

In one embodiment, if the cell barring information broadcast by the cell is "not barred", a UE that supports only legacy networks (without NPN features) (e.g., a UE that does not support NPN features, a UE that supports only legacy features that do not include NPN features (e.g., prior to Rel-16)), or a UE that has a registered (or selected) PLMN and supports a network that includes NPN features may not barre itself from accessing the cell. The UE may consider this cell as a candidate cell for cell (re-) selection. The UE may (re) select or camp on the cell. In another embodiment, if the cell barring information broadcast by the cell is "not barred," a UE with registered (or selected) SNPN/PNI-NPN or a UE supporting SNPN features and/or PNI-NPN features may not barre itself from accessing the cell. The UE may (re) select or camp on the cell. In another embodiment, if the cell barring information broadcast by the cell is "not barred," a UE with registered (or selected) SNPN/PNI-NPN or a UE supporting SNPN features and/or PNI-NPN features may ignore the cell barring information. The UE may prohibit itself from accessing the cell, (re) selecting or camping on the cell.

Case 3-2: cell broadcast cell barring information supporting only NPN features

In one embodiment, if a cell supports only NPN features (e.g., a cell operated by only SNPN(s), a cell operated by only PNI-NPN(s), a cell shared by SNPN(s) and PNI-NPN (s)), then the cell barring information may be common to all SNPN and/or PNI-NPN(s) operating the cell. The cell may broadcast in system information (e.g., SIB1, other SI) PLMN ID(s) and/or NID(s) identifying SNPN supported, and/or broadcast PLMN ID(s) and/or CAG ID(s) supporting PNI-NPN.

In one embodiment, if the cell barring information broadcast by the cell is "barred", a UE that supports only legacy networks (without NPN features) (e.g., a UE that does not support NPN features, a UE that supports only legacy features that do not include NPN features (e.g., prior to Rel-16)), or a UE that has a registered (or selected) PLMN and supports a network that includes NPN features may barre itself from accessing the cell. The UE may neither (re) select nor camp on the cell. In another embodiment, if the cell barring information broadcast by the cell is "barred", a UE with registered (or selected) SNPN/PNI-NPN or a UE supporting SNPN features and/or PNI-NPN features may barre itself from accessing the cell. The UE may neither (re) select nor camp on the cell. In another embodiment, if the cell barring information broadcast by the cell is "barred", a UE with registered (or selected) SNPN/PNI-NPN or a UE supporting SNPN features and/or PNI-NPN features may ignore the cell barring information. The UE may prohibit itself from accessing the cell, (re) selecting or camping on the cell. In yet another embodiment, for a UE with registered (or selected) SNPN/PNI-NPN or a UE supporting SNPN features and/or PNI-NPN features, if the cell barring information broadcast by the cell is "barred" and if the registered (or selected) SNPN/PNI-NPN matches the corresponding NPN ID (e.g., PLMN ID(s) and/or NID(s), PLMN ID(s) and/or CAG ID (s)) broadcast by the cell in the system information (e.g., SIB1, other SI), the UE may prohibit itself from accessing the cell. In yet another embodiment, for a UE with registered (or selected) SNPN/PNI-NPN or a UE supporting SNPN features and/or PNI-NPN features, if the cell barring information broadcast by the cell is "barred" and if the registered (or selected) SNPN/PNI-NPN does not match the corresponding NPN ID (e.g., PLMN ID(s) and/or NID(s), PLMN ID(s) and/or CAG ID (s)) broadcast by the cell in the system information (e.g., SIB1, other SI), the UE may prohibit itself from accessing the cell. In yet another embodiment, for a UE with registered (or selected) SNPN/PNI-NPN or a UE supporting SNPN features and/or PNI-NPN features, if the cell barring information broadcast by the cell is "barred" and if the registered (or selected) SNPN/PNI-NPN does not match the corresponding NPN ID (e.g., PLMN ID(s) and/or NID(s), PLMN ID(s) and/or CAG ID (s)) broadcast by the cell in the system information (e.g., SIB1, other SI), the UE may ignore the cell barring information. The UE may prohibit itself from accessing the cell, (re) selecting or camping on the cell.

In one embodiment, if the cell barring information broadcast by the cell is "not barred," a UE supporting only legacy networks (e.g., a UE not supporting NPN features, a UE supporting only legacy features not including NPN features (e.g., prior to Rel-16)) or a UE having a registered (or selected) PLMN and supporting a network including NPN features may barre itself from accessing the cell. The UE may neither (re) select nor camp on the cell. In another embodiment, if the cell barring information broadcast by the cell is "not barred," a UE with registered (or selected) SNPN/PNI-NPN or a UE supporting SNPN features and/or PNI-NPN features may not barre itself from accessing the cell. The UE may (re) select or camp on the cell. In another embodiment, if the cell barring information broadcast by the cell is "not barred," a UE with registered (or selected) SNPN/PNI-NPN or a UE supporting SNPN features and/or PNI-NPN features may ignore the cell barring information. The UE may prohibit itself from accessing the cell, (re) selecting or camping on the cell. In yet another embodiment, for a UE with registered (or selected) SNPN/PNI-NPN or a UE supporting SNPN features and/or PNI-NPN features, if the cell barring information broadcast by the cell is "not barred" and if the registered (or selected) SNPN/PNI-NPN matches the corresponding NPN ID (e.g., PLMN ID(s) and/or NID(s), PLMN ID(s) and/or CAG ID (s)) broadcast by the cell in the system information (e.g., SIB1, other SI), the UE may not prohibit itself from accessing the cell. In yet another embodiment, for a UE with registered (or selected) SNPN/PNI-NPN or a UE supporting SNPN features and/or PNI-NPN features, if the cell barring information broadcast by the cell is "not barred" and if the registered (or selected) SNPN/PNI-NPN does not match the corresponding NPN ID (e.g., PLMN ID(s) and/or NID(s), PLMN ID(s) and/or CAG ID (s)) broadcast by the cell in the system information (e.g., SIB1, other SI), the UE may prohibit itself from accessing the cell. In yet another embodiment, for a UE with registered (or selected) SNPN/PNI-NPN or a UE supporting SNPN features and/or PNI-NPN features, if the cell barring information broadcast by the cell is "not barred" and if the registered (or selected) SNPN/PNI-NPN does not match the corresponding NPN ID (e.g., PLMN ID(s) and/or NID(s), PLMN ID(s) and/or CAG ID (s)) broadcast by the cell in the system information (e.g., SIB1, other SI), the UE may ignore the cell barring information. The UE may prohibit itself from accessing the cell, (re) selecting or camping on the cell.

Cell reservation for other usage IEs

In one embodiment, a cell may broadcast cell reservation as other usage information, which may be a cell reservation in system information (e.g., SIB1, other SI) as other usage IEs. In one embodiment, cell reservation for other usage IEs may be in an enumerated { "true", "not true" } format. In one embodiment, cell reservation for other usage IEs may be in the enumerated { "true" } format, where the absence of cell reservation for other usage IEs may be equivalent to a value of "not true".

Case 4-1: one cell associated with PLMN(s) and NPN(s) is reserved for other usage IEs

In one embodiment, the cell reservation for other usage IEs may be associated with PLMN ID(s) identifying PLMN(s) operating the cell, PLMN ID(s) and/or NID(s) identifying SNPN(s) operating the cell, and PLMN ID(s) and/or CAG ID(s) identifying PNI-NPN(s) operating the cell. For example, cells operated (or shared) by (at least one) PLMN, (at least one) SNPN, and (at least one) PNI-NPN may broadcast a cell reservation as other usage IEs. For example, cells operated (or shared) by the PLMN(s) and SNPN (or shared) may broadcast a cell reservation with empty (or non-existing) PLMN ID(s) and/or CAG ID(s) for other usage IEs. For example, cells operated (or shared) by the PLMN(s) and PNI-NPN(s) may broadcast a cell reservation with empty (or non-existing) PLMN ID(s) and/or NID(s) for other usage IEs. For example, cells operated (or shared) by the PNI-NPN(s) and the SNPN(s) may broadcast a cell reservation with an empty (or non-existing) PLMN ID(s) as other usage IEs. For example, cells operated (or shared) by the PLMN(s) may broadcast cell reservations with empty (or non-existing) PLMN ID(s) and/or NID(s) and empty (or non-existing) PLMN ID(s) and/or CAG ID(s) for other usage IEs. For example, a cell operated (or shared) by the PNI-NPN(s) may broadcast a cell with an empty (or non-existing) PLMN ID(s) and/or NID(s) reserved for other usage IEs. For example, a cell operated (or shared) by (at least one) SNPN may broadcast a cell with an empty (or non-existing) PLMN ID(s) and/or CAG ID(s) reserved for other usage IEs.

In one embodiment, the cell reservation for other usage IEs and corresponding PLMN ID(s), PLMN ID(s) and/or NID(s), and/or PLMN ID(s) and/or CAG ID(s) may be included in an IE (e.g., a cell-specific cell access related IE) that may be broadcast by the cell in the system information.

In one embodiment, if a cell reservation is "true" for other usage IEs, a UE that supports only legacy networks (without NPN features) (e.g., a UE that does not support NPN features, a UE that supports only legacy features that do not include NPN features (e.g., prior to Rel-16)) may prohibit itself from accessing the cell or ignore the cell reservation for other usage IEs. A UE having a registered (or selected) PLMN and supporting a network including NPN features may prohibit itself from accessing the cell. A UE with registered (or selected) SNPN/PNI-NPN may prohibit itself from accessing the cell.

In one embodiment, if the cell reservation is that the other usage IE is "not true" or not present, then UEs that support only legacy networks (without NPN features) (e.g., UEs that do not support NPN features, UEs that support only legacy features that do not include NPN features (e.g., prior to Rel-16)) may not prohibit themselves from accessing the cell or may ignore the cell reservation as other usage IEs. A UE having a registered (or selected) PLMN and supporting a network including NPN features may not prohibit itself from accessing the cell. A UE with registered (or selected) SNPN/PNI-NPN may not prohibit itself from accessing the cell.

In one embodiment, a cell may broadcast a first cell reservation as other usage IEs for UEs supporting legacy networks (without NPN features) and a second cell reservation as other usage IEs for UEs having registered (or selected) PLMNs and supporting networks including NPN features and for UEs having registered SNPN/PNI-NPN. A UE supporting only legacy networks (without NPN features) may ignore the second cell reservation as other usage IEs. If the first cell is reserved for other uses IE is "true", then a UE supporting only legacy networks (without NPN features) may prohibit itself from accessing the cell. If the first cell is reserved for other uses IE as "not true" or not present, a UE supporting only legacy networks (without NPN features) may not prohibit itself from accessing the cell. A UE supporting only legacy networks (without NPN features) may consider this cell as a candidate cell for cell (re-) selection. A UE supporting only legacy networks (without NPN features) may camp on the cell or (re-) select the cell. In one embodiment, the reservation of the first cell for other usage IEs may be associated with only the PLMN ID(s) identifying the PLMN(s) operating the cell.

In one embodiment, the UE may receive an (optional) first cell reservation for other use IEs and a second cell reservation for other use IEs. The first cell reservation for other UEs using IEs may be used to support legacy networks (without NPN features). The second cell reservation for other usage IEs may be associated with PLMN ID(s), PLMN ID(s) and/or NID(s), and/or PLMN ID(s) and/or CAG ID(s). A UE having a registered (or selected) PLMN ID and supporting a network with NPN features, a UE having a registered (or selected) PLMN ID and/or NID, or a UE having a registered (or selected) PLMN ID and/or CAG ID may ignore the first cell reservation as other usage IEs (if received). The UE having a registered (or selected) PLMN ID and supporting a network with NPN features, the UE having a registered (or selected) PLMN ID and/or NID, and the UE having a registered (or selected) PLMN ID and/or CAG ID may act for other usage IEs based on the second cell reservation.

Case 4-2: one cell is reserved for other uses IE associated with PLMN(s) and SNPN(s), while another cell is reserved for other uses IE associated with PNI-NPN(s)

In one embodiment, the other usage IE reserved for one cell (which may be referred to as the first cell reservation as the other usage IE in case 4-2) may be associated with PLMN ID(s) identifying PLMN(s) operating the cell and PLMN ID(s) and/or NID(s) identifying SNPN(s) operating the cell. For example, cells operated (or shared) by (at least one) PLMN and (at least one) SNPN may broadcast that the first cell is reserved for other usage IEs. For example, a cell operated (or shared) by the PLMN(s) may broadcast a first cell with an empty (or non-existing) PLMN ID(s) and/or NID(s) reserved for other usage IEs. For example, a cell operated (or shared) by (at least one) SNPN may broadcast a PLMN ID first cell(s) reserved for other usage IEs with null (or non-existing). For example, a cell operated (or shared) by (at least one) PNI-NPN may not broadcast the first cell reservation as other usage IEs.

In one embodiment, another cell reserved for other uses IE (which may be referred to as a second cell reserved for other uses IE in case 4-2) may be associated with PLMN ID(s) and/or CAG ID(s) identifying PNI-NPN(s) operating the cell. For example, a cell operated (or shared) by (at least one) PNI-NPN may broadcast a second cell reservation as other usage IE. For example, a cell operated (or shared) by (at least one) SNPN may not broadcast a second cell reservation for other use IEs. For example, a cell operated (or shared) by the (at least one) PLMN may not broadcast a second cell reservation for other usage IEs.

In one embodiment, the first cell reservation for other usage IEs and corresponding PLMN ID(s) and/or NID(s) may be included in an IE (e.g., a non-PNI-NPN specific cell access related IE) that may be broadcast by the cell in the system information. In one embodiment, the second cell reservation for other usage IEs and the corresponding PLMN ID(s) and/or CAG ID(s) may be included in another IE (e.g., PNI-NPN specific cell access related IE), which may be broadcast by the cell in the system information. In another embodiment, the first cell reservation for other use IEs and the second cell reservation for other use IEs may be included in an IE (e.g., a cell-specific cell access related IE) that may be broadcast by the cell in the system information.

In one embodiment, if the first cell reservation is true for other usage IEs, UEs that support only legacy networks (without NPN features) (e.g., UEs that do not support NPN features, UEs that support only legacy features that do not include NPN features (e.g., prior to Rel-16)) may prohibit themselves from accessing the cell or may ignore the first cell reservation as other usage IEs. A UE having a registered (or selected) PLMN and supporting a network including NPN features or a UE having a registered (or selected) SNPN may prohibit itself from accessing the cell. A UE with a registered (or selected) PNI-NPN may not prohibit itself from accessing the cell or the UE may ignore the first cell reservation as other usage IEs.

In one embodiment, if the first cell is reserved as other usage IEs being "not true" or not present, UEs that support only legacy networks (without NPN features) (e.g., UEs that do not support NPN features, UEs that support only legacy features that do not include NPN features (e.g., prior to Rel-16)) may not prohibit themselves from accessing the cell, or may ignore the first cell reservation as other usage IEs. A UE having a registered (or selected) PLMN and supporting a network including NPN features or a UE having a registered (or selected) SNPN may not prohibit itself from accessing a cell. A UE with a registered (or selected) PNI-NPN may prohibit itself from accessing the cell or ignore the first cell reservation as other usage IEs. If the UE does not prohibit the cell, the UE may consider the cell as a candidate cell for cell (re-) selection. The UE may (re) select or camp on the cell.

In one embodiment, if the second cell reservation is "true" for other usage IEs, UEs that support only legacy networks (without NPN features) (e.g., UEs that do not support NPN features, UEs that support only legacy features that do not include NPN features (e.g., prior to Rel-16)) may not prohibit themselves from accessing the cell or may ignore the second cell reservation as other usage IEs. A UE with a registered (or selected) PLMN and supporting a network including NPN features or a UE with a registered (or selected) SNPN may not prohibit itself from accessing a cell or ignore the second cell reservation as other usage IEs. A UE with a registered (or selected) PNI-NPN may prohibit itself from accessing the cell.

In one embodiment, if the second cell is reserved as other usage IEs being "not true" or not present, UEs that support only legacy networks (without NPN features) (e.g., UEs that do not support NPN features, UEs that support only legacy features that do not include NPN features (e.g., prior to Rel-16)) may prohibit themselves from accessing the cell or may ignore the second cell reservation as other usage IEs. A UE having a registered (or selected) PLMN and supporting a network including NPN features or a UE having a registered (or selected) SNPN may prohibit itself from accessing a cell or ignore the second cell reservation as other usage IEs. A UE with a registered (or selected) PNI-NPN may not prohibit itself from accessing the cell.

In one embodiment, in addition to the first cell reserving as other usage IEs (for UEs with registered (or selected) PLMNs and supporting networks including NPN features and for UEs with registered SNPN) and the second cell reserving as other usage IEs (for UEs with registered PNI-NPN), the cell may also broadcast a third cell reserving as other usage IEs for UEs supporting legacy networks (without NPN features). A UE supporting only legacy networks (without NPN features) may ignore the first cell reservation for other usage IEs and the second cell reservation for other usage IEs. If the third cell is reserved for other uses IE is "true", then a UE supporting only legacy networks (without NPN features) may prohibit itself from accessing that cell. If the third cell is reserved for other uses IE as "not true" or not present, a UE supporting only legacy networks (without NPN features) may not prohibit itself from accessing the cell. A UE supporting only legacy networks (without NPN features) may camp on the cell or (re-) select the cell. In one embodiment, the third cell reservation for other usage IEs may be associated with only PLMN ID(s) identifying the PLMN(s) operating the cell.

In one embodiment, the UE may receive a first cell reservation associated with PLMN ID(s), and/or NID(s) as other usage IEs, (optionally) receive a second cell reservation associated with PLMN ID(s) and/or CAG ID(s) as other usage IEs, and (optionally) receive a third cell reservation as other usage IEs for the UE supporting legacy networks (without NPN features). A UE having a registered (or selected) PLMN ID and supporting a network with NPN features or a UE having a registered (or selected) PLMN ID and/or NID may ignore the second cell reservation as other usage IEs (if received) and the third cell reservation as other usage IEs (if received). A UE having a registered (or selected) PLMN ID and supporting a network with NPN features or a UE having a registered (or selected) PLMN ID and/or NID may act for other usage IEs based on the first cell reservation.

In one embodiment, the UE may receive a first cell associated with PLMN ID(s), and/or NID(s) reserved for other usage IEs, a second cell associated with PLMN ID(s) and/or CAG ID(s) reserved for other usage IEs, and a third cell reserved for other usage IEs for UEs supporting legacy networks (without NPN features). The UE with the registered (or selected) PLMN ID and/or CAG ID may ignore the first cell reservation for other usage IEs (if received) and the third cell reservation for other usage IEs (if received). The UE with the registered (or selected) PLMN ID and/or CAG ID may act for other usage IEs based on the second cell reservation.

Case 4-3: one cell is reserved for other uses IE associated with PLMN(s) and PNI-NPN(s), while another cell is reserved for other uses IE associated with SNPN(s)

In one embodiment, the other usage IE reserved for one cell (which may be referred to as the first cell reservation as the other usage IE in case 4-3) may be associated with PLMN ID(s) identifying the PLMN(s) operating the cell and PLMN ID(s) and/or CAG ID(s) identifying the PNI-NPN(s) operating the cell. For example, a cell operated (or shared) by the (at least one) PLMN and the (at least one) PNI-NPN may broadcast that the first cell is reserved for other usage IEs. For example, a cell operated (or shared) by the PLMN(s) may broadcast a first cell with empty (or non-existing) PLMN ID(s) and/or CAG ID(s) reserved for other usage IEs. For example, a cell operated (or shared) by (at least one) PNI-NPN may broadcast a first cell reservation with empty (or non-existing) PLMN ID(s) for other usage IEs. For example, a cell operated (or shared) by (at least one) SNPN may broadcast a first cell reservation with an empty (or non-existing) PLMN ID(s) for other usage IEs. For example, a cell operated (or shared) by (at least one) SNPN may not broadcast the first cell reservation as other usage IEs.

In one embodiment, another cell reserved for other uses IE (which may be referred to as a second cell reserved for other uses IE in case 4-3) may be associated with PLMN ID(s) and/or NID(s) identifying SNPN operating the cell. For example, a cell operated (or shared) by (at least one) SNPN may broadcast a second cell reservation as other usage IEs. For example, a cell operated (or shared) by (at least one) PNI-NPN may not broadcast a reservation of the second cell for other usage IEs. For example, a cell operated (or shared) by the (at least one) PLMN may not broadcast a second cell reservation for other usage IEs.

In one embodiment, the first cell reservation for other usage IEs and corresponding PLMN ID(s) and/or CAG ID(s) may be included in an IE (e.g., a non-SNPN specific cell access related IE) that may be broadcast by the cell in the system information. In one embodiment, the second cell reservation for other usage IEs and the corresponding PLMN ID(s) and/or NID(s) may be included in another IE (e.g., SNPN-specific cell access related IE), which may be broadcast by the cell in the system information. In another embodiment, the first cell reservation for other use IEs and the second cell reservation for other use IEs may be included in an IE (e.g., a cell-specific cell access related IE) that may be broadcast by the cell in the system information.

In one embodiment, if the first cell reservation is true for other usage IEs, UEs that support only legacy networks (without NPN features) (e.g., UEs that do not support NPN features, UEs that support only legacy features that do not include NPN features (e.g., prior to Rel-16)) may prohibit themselves from accessing the cell or may ignore the first cell reservation as other usage IEs. A UE having a registered (or selected) PLMN and supporting a network including NPN features or a UE having a registered (or selected) PNI-NPN may prohibit itself from accessing a cell. A UE with registered (or selected) SNPN may not prohibit itself from accessing the cell or the UE may ignore the first cell reservation as other use IEs.

In one embodiment, if the first cell is reserved as other usage IEs being "not true" or not present, UEs that support only legacy networks (without NPN features) (e.g., UEs that do not support NPN features, UEs that support only legacy features that do not include NPN features (e.g., prior to Rel-16)) may not prohibit themselves from accessing the cell, or may ignore the first cell reservation as other usage IEs. A UE having a registered (or selected) PLMN and supporting a network including NPN features or a UE having a registered (or selected) PNI-NPN may not prohibit itself from accessing a cell. A UE with registered (or selected) SNPN may prohibit itself from accessing the cell or the UE may ignore the first cell reservation as other use IEs.

In one embodiment, if the second cell reservation is "true" for other usage IEs, UEs that support only legacy networks (without NPN features) (e.g., UEs that do not support NPN features, UEs that support only legacy features that do not include NPN features (e.g., prior to Rel-16)) may not prohibit themselves from accessing the cell or may ignore the second cell reservation as other usage IEs. A UE having a registered (or selected) PLMN and supporting a network including NPN features or a UE having a registered (or selected) PNI-NPN may not prohibit itself from accessing a cell or may ignore the second cell reservation as other usage IEs. A UE with registered (or selected) SNPN may prohibit itself from accessing the cell.

In one embodiment, if the second cell is reserved as other usage IEs being "not true" or not present, UEs that support only legacy networks (without NPN features) (e.g., UEs that do not support NPN features, UEs that support only legacy features that do not include NPN features (e.g., prior to Rel-16)) may prohibit themselves from accessing the cell or may ignore the second cell reservation as other usage IEs. A UE having a registered (or selected) PLMN and supporting a network including NPN features or a UE having a registered (or selected) PNI-NPN may prohibit itself from accessing a cell or may ignore the second cell reservation as other usage IEs. A UE with registered (or selected) SNPN may not prohibit itself from accessing the cell.

In one embodiment, in addition to the first cell reserving as other usage IEs (for UEs with registered (or selected) PLMN(s) and supporting a network including NPN features) and for UEs with registered PNI-NPN(s) and the second cell reserving as other usage IEs (for UEs with registered SNPN (s)), the cell may also broadcast a third cell reserving as other usage IEs for UEs supporting legacy networks (without NPN features). A UE supporting only legacy networks (without NPN features) may ignore the first cell reservation for other usage IEs and the second cell reservation for other usage IEs. If the third cell is reserved for other uses IE is "true", then a UE supporting only legacy networks (without NPN features) may prohibit itself from accessing that cell. If the third cell is reserved for other uses IE as "not true" or not present, a UE supporting only legacy networks (without NPN features) may not prohibit itself from accessing the cell. A UE supporting only legacy networks (without NPN features) may camp on the cell or (re-) select the cell. In one embodiment, the third cell reservation for other usage IEs may be associated with only PLMN ID(s) identifying the PLMN(s) operating the cell.

In one embodiment, the UE may receive a first cell reservation associated with PLMN ID(s), and/or CAG ID(s) as other usage IEs, (optionally) receive a second cell reservation associated with PLMN ID(s) and/or NID(s) as other usage IEs, and (optionally) receive a third cell reservation as other usage IEs, the third cell being for supporting UEs of legacy networks (without NPN features). A UE having a registered (or selected) PLMN ID and supporting a network with NPN features or a UE having a registered (or selected) PLMN ID and/or CAG ID may ignore the second cell reservation as other usage IEs (if received) and the third cell reservation as other usage IEs (if received). A UE having a registered (or selected) PLMN ID and supporting a network with NPN features or a UE having a registered (or selected) PLMN ID and/or CAG ID may act for other usage IEs based on the first cell reservation.

In one embodiment, the UE may receive a first cell associated with PLMN ID(s), PLMN ID(s) and/or CAG ID(s) reserved for other use IEs, a second cell associated with PLMN ID(s) and/or NID(s) reserved for other use IEs, and a third cell reserved for other use IEs for UEs supporting legacy networks (without NPN features). A UE with a registered (or selected) PLMN ID and/or NID may ignore the first cell reservation for other usage IEs (if received) and the third cell reservation for other usage IEs (if received). A UE with a registered (or selected) PLMN ID and/or NID may act for other usage IEs based on the second cell reservation.

Cases 4-4: one cell is reserved for other uses IE associated with NPN(s), while another cell is reserved for other uses IE associated with PLMN(s)

In one embodiment, the other usage IE reserved for one cell (which may be referred to as the first cell reservation as the other usage IE in case 4-4) may be associated with PLMN ID(s) and/or NID(s) identifying SNPN operating the cell and PLMN ID(s) and/or CAG ID(s) identifying PNI-NPN(s) operating the cell. For example, a cell operated (or shared) by (at least one) SNPN and (at least one) PNI-NPN may broadcast a first cell reservation as other usage IEs. For example, a cell operated (or shared) by (at least one) SNPN may broadcast a first cell with empty (or non-existing) PLMN ID(s) and/or CAG ID(s) reserved for other usage IEs. For example, a cell operated (or shared) by the PNI-NPN(s) may broadcast a first cell with empty (or non-existing) PLMN ID(s) and/or NID(s) reserved for other usage IEs. For example, a cell operated (or shared) by the (at least one) PLMN may not broadcast the first cell reservation as other usage IEs.

In one embodiment, other usage IEs reserved for another cell (which may be referred to as a second cell reservation as other usage IEs in cases 4-4) may be associated with PLMN ID(s) identifying PLMN(s) operating the cell. For example, a cell operated (or shared) by the (at least one) PLMN may broadcast a second cell reservation for other usage IEs. For example, a cell operated (or shared) by (at least one) SNPN may not broadcast a second cell reservation for other use IEs. For example, a cell operated (or shared) by (at least one) PNI-NPN may not broadcast a reservation of the second cell for other usage IEs.

In one embodiment, the first cell reservation for other usage IEs and corresponding PLMN IDs and/or NIDs and corresponding PLMN IDs and/or CAG IDs may be included in an IE (e.g., NPN-specific cell access related IE) that may be broadcast by the cell in the system information. In one embodiment, the second cell reservation for other usage IEs and corresponding PLMN ID(s) may be included in another IE (e.g., a non-NPN specific cell access related IE), which may be broadcast by the cell in the system information. In another embodiment, the first cell reservation for other use IEs and the second cell reservation for other use IEs may be included in an IE (e.g., a cell-specific cell access related IE) that may be broadcast by the cell in the system information.

In one embodiment, if the first cell reservation is "true" for other usage IEs, UEs that support only legacy networks (without NPN features) (e.g., UEs that do not support NPN features, UEs that support only legacy features that do not include NPN features (e.g., prior to Rel-16)) may not prohibit themselves from accessing the cell or may ignore the first cell reservation as other usage IEs. A UE having a registered (or selected) PLMN and supporting a network including NPN features may not prohibit itself from accessing a cell or may ignore the first cell reservation as other usage IEs. A UE with registered (or selected) SNPN or a UE with registered (or selected) PNI-NPN may prohibit itself from accessing the cell.

In one embodiment, if the first cell reservation is "not true" or not present for other usage IEs, UEs that support only legacy networks (without NPN features) (e.g., UEs that do not support NPN features, UEs that support only legacy features that do not include NPN features (e.g., prior to Rel-16)) may prohibit themselves from accessing the cell or may ignore the first cell reservation as other usage IEs. A UE having a registered (or selected) PLMN and supporting a network including NPN features may prohibit itself from accessing a cell or may ignore the first cell reservation as other usage IEs. A UE with registered (or selected) SNPN or a UE with registered (or selected) PNI-NPN may not be barred from accessing the cell itself.

In one embodiment, if the second cell reservation is true for other usage IEs, UEs that support only legacy networks (without NPN features) (e.g., UEs that do not support NPN features, UEs that support only legacy features that do not include NPN features (e.g., prior to Rel-16)) may prohibit themselves from accessing the cell or may ignore the second cell reservation as other usage IEs. A UE having a registered (or selected) PLMN and supporting a network including NPN features may prohibit itself from accessing the cell. A UE with registered (or selected) SNPN or a UE with registered (or selected) PNI-NPN may not prohibit itself from accessing the cell or may ignore the reservation of the second cell for other use IEs.

In one embodiment, if the second cell reservation is "not true" or not present for other usage IEs, UEs that support only legacy networks (e.g., UEs that do not support NPN features, UEs that support only legacy features that do not include NPN features (e.g., prior to Rel-16)) may not prohibit themselves from accessing the cell or may ignore the second cell reservation as other usage IEs. A UE having a registered (or selected) PLMN and supporting a network including NPN features may not prohibit itself from accessing the cell. A UE with registered (or selected) SNPN or a UE with registered (or selected) PNI-NPN may prohibit itself from accessing the cell or may ignore the reservation of the second cell for other use IEs.

In one embodiment, in addition to the first cell reserving as other usage IEs (for UEs with registered SNPN(s) and for UEs with registered PNI-NPN (s)) and the second cell reserving as other usage IEs (for UEs with registered (or selected) PNI-NPN (s)), the cell may also broadcast a third cell reserving as other usage IEs for UEs supporting legacy networks (without NPN features). A UE supporting only legacy networks (without NPN features) may ignore the first cell reservation for other usage IEs and the second cell reservation for other usage IEs. If the third cell is reserved for other uses IE is "true", then a UE supporting only legacy networks (without NPN features) may prohibit itself from accessing that cell. If the third cell is reserved for other uses IE as "not true" or not present, a UE supporting only legacy networks (without NPN features) may not prohibit itself from accessing the cell. A UE supporting only legacy networks (without NPN features) may camp on the cell or (re-) select the cell. In one embodiment, the third cell reservation for other usage IEs may be associated with only PLMN ID(s) identifying the PLMN(s) operating the cell.

In one embodiment, the UE may receive a first cell associated with PLMN ID(s) and/or NID(s) and PLMN ID(s) and/or CAG ID(s) reserved for other use IEs, a second cell associated with PLMN ID(s) reserved for other use IEs, and a third cell reserved for other use IEs for UEs supporting legacy networks (without NPN features). A UE having a registered (or selected) PLMN ID and supporting a network with NPN features may ignore the first cell reservation as the other usage IE (if received) and the third cell reservation as the other usage IE (if received). A UE with a registered (or selected) PLMN ID and supporting a network with NPN features may act for other usage IEs based on the second cell reservation

In one embodiment, the UE may receive a first cell reservation associated with PLMN ID(s) and/or NID(s) and PLMN ID(s) and/or CAG ID(s) as other usage IEs, a second cell reservation associated with PLMN ID(s) (optional) as other usage IEs, and a third cell reservation as other usage IEs, the third cell being for supporting UEs of legacy networks (without NPN features). A UE with a registered (or selected) PLMN ID and/or NID or a UE with a registered (or selected) PLMN ID and/or CAG ID may ignore the second cell reservation for other usage IEs (if received) and the third cell reservation for other usage IEs (if received). A UE with a registered (or selected) PLMN ID and/or NID or a UE with a registered (or selected) PLMN ID and/or CAG ID may act for other usage IEs based on the first cell reservation.

Cases 4-5: one cell is reserved for other uses IE associated with SNPN(s), another cell is reserved for other uses IE associated with PLMN(s), yet another cell is reserved for other uses IE associated with PNI-NPN(s)

In one embodiment, the PLMN ID(s) and/or NID(s) identifying SNPN that operate the cell may be associated with a cell reservation as other usage IE (which may be referred to as the first cell reservation as other usage IE in cases 4-5). For example, a cell operated (or shared) by (at least one) SNPN may broadcast a first cell reservation as other usage IEs. For example, a cell operated (or shared) by the (at least one) PLMN may not broadcast the first cell reservation as other usage IEs. For example, a cell operated (or shared) by (at least one) PNI-NPN may not broadcast the first cell reservation as other usage IEs. For example, cells that are not operated (or shared) by SNPN (or are shared) may not broadcast the first cell reservation for other use IEs.

In one embodiment, other usage IEs reserved for another cell (which may be referred to as a second cell reservation as other usage IEs in cases 4-5) may be associated with PLMN ID(s) identifying PLMN(s) operating the cell. For example, a cell operated (or shared) by the (at least one) PLMN may broadcast a second cell reservation for other usage IEs. For example, a cell operated (or shared) by (at least one) SNPN may not broadcast a second cell reservation for other use IEs. For example, a cell operated (or shared) by (at least one) PNI-NPN may not broadcast a reservation of the second cell for other usage IEs. For example, cells that are not operated (or shared) by the PLMN(s) may not broadcast the second cell reservation for other usage IEs.

In one embodiment, a further cell reservation as other usage IE (which may be referred to as a third cell reservation as other usage IE in cases 4-5) may be associated with PLMN ID(s) and/or CAG ID(s) identifying PNI-NPN(s) operating the cell. For example, a cell operated (or shared) by (at least one) PNI-NPN may broadcast a third cell reservation as other usage IEs. For example, a cell operated (or shared) by the (at least one) PLMN may not broadcast a third cell reservation for other usage IEs. For example, a cell operated (or shared) by (at least one) SNPN may not broadcast a third cell reservation for other use IEs. For example, a cell that is not operated (or shared) by PNI-PLMN(s) may not broadcast a third cell reservation for other usage IEs.

In one embodiment, the first cell reservation for other usage IEs and the corresponding PLMN ID(s) and/or NID(s) may be included in an IE (e.g., SNPN a cell access related IE specific) that may be broadcast by the cell in the system information. In one embodiment, the second cell reservation for other usage IEs and corresponding PLMN ID(s) may be included in another IE (e.g., a PLMN-specific cell access related IE), which may be broadcast by the cell in the system information. In one embodiment, the third cell reservation for other usage IEs and the corresponding PLMN ID(s) and/or CAG ID(s) may be included in yet another IE (e.g., PNI-NPN specific cell access related IE) that may be broadcast by the cell in the system information. In another embodiment, the first cell reservation for other use IEs, the second cell reservation for other use IEs, and the third cell reservation for other use IEs may be included in an IE (e.g., a cell-specific cell access related IE) that may be broadcast by the cell in the system information.

In one embodiment, if the second cell associated with the PLMN ID(s) is reserved as other usage IEs being "true", UEs that support only legacy networks (without NPN features) (e.g., UEs that do not support NPN features, UEs that support only legacy features that do not include NPN features (e.g., prior to Rel-16)) may prohibit themselves from accessing the cell or may ignore the second cell reservation as other usage IEs. A UE having a registered (or selected) PLMN and supporting a network including NPN features may prohibit itself from accessing the cell. A UE with registered (or selected) SNPN may not prohibit itself from accessing the cell or may ignore the second cell reservation as other usage IEs. A UE with a registered (or selected) PNI-NPN may not prohibit itself from accessing the cell or may ignore the reservation of the second cell for other usage IEs.

In one embodiment, if the second cell associated with the PLMN ID(s) is reserved as other usage IEs being "non-true" or not present, UEs supporting only legacy networks (without NPN features) (e.g., UEs supporting no NPN features, UEs supporting only legacy features that do not include NPN features (e.g., prior to Rel-16)) may not prohibit themselves from accessing the cell or may ignore the second cell reservation as other usage IEs. A UE having a registered (or selected) PLMN and supporting a network including NPN features may not prohibit itself from accessing the cell. A UE with registered (or selected) SNPN may prohibit itself from accessing the cell or may ignore the second cell reservation as other use IEs. A UE with a registered (or selected) PNI-NPN may prohibit itself from accessing the cell or may ignore the reservation of the second cell for other usage IEs.

In one embodiment, if the first cell associated with the PLMN ID(s) and/or NID(s) is reserved as other usage IEs being "true", UEs that support only legacy networks (without NPN features) (e.g., UEs that do not support NPN features, UEs that support only legacy features that do not include NPN features (e.g., prior to Rel-16)) may not be barred from accessing the cell themselves or the first cell reservation as other usage IEs may be ignored. A UE having a registered (or selected) PLMN and supporting a network including NPN features may not prohibit itself from accessing a cell or may ignore the first cell reservation as other usage IEs. A UE with registered (or selected) SNPN may prohibit itself from accessing the cell. A UE with registered (or selected) PNI-NPN may not prohibit itself from accessing the cell, or may ignore the reservation of the first cell for other usage IEs

In one embodiment, if the first cell associated with PLMN ID(s) and/or NID(s) is reserved as being "non-genuine" or absent from other usage IEs, UEs that support only legacy networks (without NPN features) (e.g., UEs that do not support NPN features, UEs that support only legacy features that do not include NPN features (e.g., prior to Rel-16)) may prohibit themselves from accessing the cell or may ignore the first cell reservation as other usage IEs. A UE having a registered (or selected) PLMN and supporting a network including NPN features may prohibit itself from accessing a cell or may ignore the first cell reservation as other usage IEs. A UE with registered (or selected) SNPN may not prohibit itself from accessing the cell. A UE with a registered (or selected) PNI-NPN may prohibit itself from accessing the cell or may ignore the reservation of the first cell for other usage IEs.

In one embodiment, if the third cell associated with PLMN ID(s) and/or CAG ID(s) is reserved as other usage IEs being "true", UEs that support only legacy networks (without NPN features) (e.g., UEs that do not support NPN features, UEs that support only legacy features that do not include NPN features (e.g., prior to Rel-16)) may not prohibit themselves from accessing the cell or may ignore the third cell reservation as other usage IEs. A UE having a registered (or selected) PLMN and supporting a network including NPN features may not prohibit itself from accessing a cell or may ignore a third cell reservation as other usage IEs. A UE with registered (or selected) SNPN may not prohibit itself from accessing the cell or may ignore the third cell reservation as other usage IEs. A UE with a registered (or selected) PNI-NPN may prohibit itself from accessing the cell.

In one embodiment, if the third cell associated with PLMN ID(s) and/or CAG ID(s) is reserved as being "non-true" or absent from other usage IEs, UEs that support only legacy networks (without NPN features) (e.g., UEs that do not support NPN features, UEs that support only legacy features that do not include NPN features (e.g., prior to Rel-16)) may prohibit themselves from accessing the cell or may ignore the third cell reservation as being other usage IEs. A UE having a registered (or selected) PLMN and supporting a network including NPN features may prohibit itself from accessing a cell or may ignore a third cell reservation as other usage IEs. A UE with registered (or selected) SNPN may prohibit itself from accessing the cell or may ignore the third cell reservation as other use IEs. A UE with a registered (or selected) PNI-NPN may not prohibit itself from accessing the cell.

In one embodiment, the cell may broadcast a fourth cell reservation as other usage IEs for UEs supporting legacy features (without NPN features) in addition to the (optional) first cell reservation as other usage IEs for UEs with registered SNPN(s), the second cell reservation as other usage IEs for UEs with registered (or selected) PLMN(s) and supporting network including NPN features, and the (optional) third cell reservation as other usage IEs for UEs with registered PNI-NPN(s). A UE supporting only legacy networks (without NPN features) may ignore the second cell reservation for other usage IEs, the first cell reservation for other usage IEs (if received), and the third cell reservation for other usage IEs (if received). If the fourth cell is reserved with other usage IEs being "true", a UE supporting only legacy networks (without NPN features) may prohibit itself from accessing the cell. If the fourth cell is reserved for other uses IE as "not true" or not present, a UE supporting only legacy networks (without NPN features) may not prohibit itself from accessing the cell. A UE supporting only legacy networks (without NPN features) may camp on the cell or (re-) select the cell. In one embodiment, the fourth cell reservation for other usage IEs may be associated with only PLMN ID(s) identifying the PLMN(s) operating the cell.

In one embodiment, the UE may receive a first cell reservation associated with PLMN ID(s) and/or NID(s) as other usage IEs, a second cell reservation associated with PLMN ID(s) as other usage IEs, a third cell reservation associated with PLMN ID(s) and/or CAG ID(s) as other usage IEs, and a fourth cell reservation as other usage IEs for supporting UEs of legacy networks (without NPN features). A UE having a registered (or selected) PLMN ID and supporting a network with NPN features may ignore the first cell reservation as the other use IE (if received), the third cell reservation as the other use IE (if received), and the fourth cell reservation as the other use IE (if received). A UE having a registered (or selected) PLMN ID and supporting a network with NPN features may act for other usage IEs based on the second cell reservation.

In one embodiment, the UE may receive a first cell reservation associated with PLMN ID(s) and/or CAG ID(s) as other usage IEs, a second cell reservation associated with PLMN ID(s) as other usage IEs, a third cell reservation associated with PLMN ID(s) and/or CAG ID(s) as other usage IEs, and a fourth cell reservation as other usage IEs, the fourth cell being for supporting UEs of the legacy network (without NPN features). The UE with the registered (or selected) PLMN ID and/or NID may ignore the second cell reservation as the other use IE (if received), the third cell reservation as the other use IE (if received), and the fourth cell reservation as the other use IE (if received). A UE with a registered (or selected) PLMN ID and/or NID may act for other usage IEs based on the first cell reservation.

In one embodiment, the UE may receive a first cell associated with the PLMN ID(s) and/or NID(s) reserved for other usage IEs, a second cell associated with the PLMN ID(s) reserved for other usage IEs, a third cell associated with the PLMN ID(s) and/or CAG ID(s) reserved for other usage IEs, and a fourth cell (optional) reserved for other usage IEs for UEs supporting legacy networks (without NPN features). The UE with the registered (or selected) PLMN ID and/or CAG ID may ignore the first cell reservation as the other use IE (if received), the second cell reservation as the other use IE (if received), and the fourth cell reservation as the other use IE (if received). A UE with a registered (or selected) PLMN ID and/or CAG ID may act for other usage IEs based on the third cell reservation.

Cell reservation for use of IEs for operators

In one embodiment, a cell may broadcast cell reservation as operator use information, which may be a cell reservation as operator use IE in system information (e.g., SIB1, in other SIs). In one embodiment, cell reservation for operator use IEs may be in an enumerated { "reserved", "unreserved" } format. In one embodiment, a cell reservation for operator use IE may be in the format of enumerated { "reserved" }, where the absence of a cell reservation for operator use IE may be equivalent to a value of "unreserved".

In one embodiment, the cell reservation may be indicated/configured for the operator to use the IE according to PLMN, according to SNPN, and according to PNI-NPN (or according to CAG). For example, a cell supporting (at least) PLMN features may use IEs for operators based on PLMN broadcast cell reservations operating the cell. For example, a cell supporting (at least) SNPN features may use an IE for the operator according to SNPN broadcast cell reservation operating the cell. For example, a cell supporting (at least) PNI-NPN features may be reserved for operator use IEs according to the PNI-NPN (or CAG) broadcast cell operating the cell.

Case 5-1: reserving usage IEs for operators for each SNPN cell

In one embodiment, the cell reservation for the operator use IE and associated SNPN ID (e.g., PLMN ID and/or NID) may be included in a first IE (e.g., SNPN ID related IE) that may be broadcast by the cell in system information (e.g., SIB1, other SI). In one embodiment, the list of first IEs may be included in a first list information structure, which may be included in a cell access related IE, which may be broadcast by the cell in system information (e.g., SIB1, other SI).

Case 5-2: reserving usage IEs for operators for each PNI-NPN cell

In one embodiment, the cell reservation for the operator use IE and associated PNI-NPN ID (e.g., PLMN ID and/or CAG ID) may be included in a second IE (e.g., PNI-NPN ID related IE) that may be broadcast by the cell in system information (e.g., SIB1, other SI). In one embodiment, the list of second IEs may be included in a second list information structure, which may be included in a cell access related IE, which may be broadcast by the cell in system information (e.g., SIB1, other SI).

Case 5-3: cell reservation for operator use IE for each PLMN

In one embodiment, the cell reservation for operator use IE and associated PLMN ID may be included in a third IE (e.g., PLMID related IE) that may be broadcast by the cell in system information (e.g., SIB1, other SI). In one embodiment, the list of third IEs may be included in a third list information structure, which may be included in a cell access related IE, which may be broadcast by the cell in system information (e.g., SIB1, other SI).

Cases 5-4: mixed in list information structure

In one embodiment, the first list information structure may include a list of the second IEs and/or a list of the third IEs. In one embodiment, the second list information structure may include a list of the first IEs and/or a list of the third IEs. In one embodiment, the third list information structure may include a list of the second IEs and/or a list of the first IEs.

Case 6-1: reserving usage IEs for operators for each SNPN cell

In one embodiment, if a cell reservation associated with SNPN ID (e.g., PLMN ID and/or NID) is "reserved" for operator use IEs, a UE with registered (or selected) SNPN ID matching the received cell reservation SNPN ID associated with the operator use IEs may prohibit itself from accessing the cell. Other UEs such as a registered (or selected) SNPN ID UE having a SNPN ID mismatch associated with a received cell reservation as an operator use IE, a UE having a registered (or selected) PNI-NPN ID (e.g., PLMN ID and/or CAG ID), a UE having a registered (or selected) PLMN ID supporting a network including NPN features, or a UE supporting only legacy networks (without NPN features) may ignore the cell reservation associated with SNPN ID as an operator use IE.

In one embodiment, if the cell reservation associated with SNPN ID (e.g., PLMN ID and/or NID) is "reserved" for operator use IE, then the UE may prohibit itself from accessing the cell (a) the UE is assigned an access ID that can be used in the home country (e.g., access ID 12, 13 or 14) or an access ID that is used when the UE is configured with a particular service (e.g., multimedia Priority Service (MPS), mission Critical Service (MCS)) such as access ID 1 or 2 or when the UE is configured with access ID 0 (e.g., the UE is not configured with a particular access ID such as access IDs 1 through 15) and (b) has registered (or selected) SNPN ID that matches SNPN ID associated with the received cell reservation for operator use IE. On the other hand, if the UE (e.g., a UE with an access ID of 11 or 15) is (a) not assigned with an access ID usable in the home country nor with an access ID used when the UE is configured with a specific service (e.g., MPS, MCS), and (b) has a registered (or selected) SNPN ID matching SNPN ID associated with a received cell reservation for an operator use IE, the UE may not prohibit itself from accessing the cell.

It should be noted that access IDs 11 and 15 may be used only in the Home PLMN (HPLMN) or Equivalent Home PLMN (EHPLMN), while access IDs 12, 13 and 14 may be used only in the Home country (e.g., in the Home HPLMN and visited PLMNs).

In some implementations, if a cell reservation associated with SNPN ID (e.g., PLMN ID and/or NID) is "unreserved" or absent from the operator use IE, a UE with registered (or selected) SNPN ID matching the received cell reservation SNPN ID associated with the operator use IE may not prohibit itself from accessing the cell. Other UEs, such as a registered (or selected) SNPN ID UE having a SNPN ID mismatch associated with a received cell reservation for operator use IE, a UE having a registered (or selected) PNI-NPN ID (e.g., PLMN ID and/or CAG ID), a UE having a registered (or selected) PLMN ID supporting a network including NPN features, a UE supporting only legacy networks (without NPN features), may ignore the cell reservation associated with SNPN ID as an operator use IE.

Case 6-2: reserving for an operator to use an IE for a cell per PNI-NPN or per CAG

In some implementations, if a cell reservation associated with a PNI-NPN ID (e.g., PLMN ID and/or CAG ID) is "reserved" for an operator use IE, a UE having a registered (or selected) PNI-NPN ID that matches the PNI-NPN ID associated with the received cell reservation for the operator use IE may prohibit itself from accessing the cell. Other UEs, such as UEs with registered (or selected) PNI-NPN IDs that do not match PNI-NPN IDs associated with the received cell reservation as operator use IE, UEs with registered (or selected) SNPN ID (e.g., PLMN IDs and/or NIDs), UEs with registered (or selected) PLMN IDs that support networks that include NPN features, or UEs that support legacy networks only (without NPN features), may ignore the cell reservation associated with PNI-NPN IDs as operator use IE.

In one embodiment, if the cell associated with the PNI-NPN ID (e.g., PLMN ID and/or CAG ID) is reserved as "reserved" for operator use IE, then the UE may prohibit itself from accessing the cell (a) is assigned an access ID that can be used in the home country (e.g., access ID 12, 13 or 14) or an access ID that is used when the UE is configured with a specific service (e.g., MPS, MCS) (e.g., access ID 1 or 2) or when the UE is configured with access ID 0 (e.g., the UE is not configured with a specific access ID such as access IDs 1 through 15) and (b) has a registered (or selected) PNI-NPN ID that matches the PNI-NPN ID that is received with which the cell reservation is associated as operator use IE. On the other hand, if a UE (e.g., a UE with an access ID of 11 or 15) is (a) not assigned with an access ID usable in the home country nor with an access ID used when the UE is configured with a specific service (e.g., MPS, MCS), and (b) has a registered (or selected) PNI-NPN ID that matches the received PNI-NPN ID with which the cell is reserved for operator use IE, the UE may not prohibit itself from accessing the cell.

In some implementations, if a cell associated with a PNI-NPN ID (e.g., PLMN ID and/or CAG ID) is reserved as "unreserved" or not present by the operator use IE, a UE having a registered (or selected) PNI-NPN ID that matches the PNI-NPN ID associated with the received cell reservation as the operator use IE may not prohibit itself from accessing the cell. Other UEs, such as UEs with registered (or selected) PNI-NPN IDs that do not match PNI-NPN IDs associated with the received cell reservation as operator use IE, UEs with registered (or selected) SNPN ID (e.g., PLMN IDs and/or NIDs), UEs with registered (or selected) PLMN IDs that support networks that include NPN features, or UEs that support legacy networks only (without NPN features), may ignore the cell reservation associated with PNI-NPN IDs as operator use IE.

Case 6-3: cell reservation for operator use IE for each PLMN

In one embodiment, if the cell reservation associated with the PLMN ID is set to "reserved" for the operator use IE, a UE having a registered (or selected) PLMN ID that matches the PLMN ID associated with the received cell reservation for the operator use IE may disable itself from accessing the cell, wherein the UE supports a network that includes NPN features. Other UEs, such as UEs with registered (or selected) PLMN IDs that do not match the PLMN IDs associated with the received cell reservation as an operator use IE (where the UE supports an IE of the network that includes NPN features), UEs with registered (or selected) SNPN ID (e.g., PLMN IDs and/or NIDs), UEs with registered (or selected) PNI-NPN IDs (e.g., PLMN IDs and/or CAG IDs), UEs that support only legacy networks (without NPN features), may ignore the cell reservation associated with the PLMN IDs as an operator use IE.

In one embodiment, if the cell reservation associated with the PLMN ID is "reserved" for the operator use IE, the following UE may prohibit itself from accessing the cell: the UE is (a) assigned an access ID that can be used in the home (e.g., access ID 12, 13 or 14) or assigned an access ID that is used when the UE is configured with a particular service (e.g., MPS, MCS) (e.g., access ID 1 or 2) or when the UE is configured with access ID 0 (e.g., the UE is not configured with a particular access ID such as access IDs 1 through 15) and (b) has a registered (or selected) PLMN ID that matches the received PLMN ID associated with the cell reservation for operator use IE. On the other hand, if the UE (e.g., a UE with an access ID of 11 or 15) is (a) not assigned with an access ID usable in the home country nor with an access ID used when the UE is configured with a specific service (e.g., MPS, MCS), and (b) has a registered (or selected) PLMN ID matching the received PLMN ID with which the cell is reserved for operator use IE, the UE may not prohibit itself from accessing the cell.

In some embodiments, if the cell reservation associated with the PLMN ID is "unreserved" or absent from the operator use IE, a UE having a registered (or selected) PLMN ID that matches the received cell reservation as a PLMN ID associated with the operator use IE may not prohibit itself from accessing the cell, wherein the UE supports a network that includes NPN features. Other UEs, such as UEs with registered (or selected) PLMN IDs that do not match the PLMN IDs associated with the received cell reservation as an operator use IE (where the UE supports a network including NPN features), UEs with registered (or selected) SNPN ID (e.g., PLMN IDs and/or NIDs), UEs with registered (or selected) PNI-NPN IDs (e.g., PLMN IDs and/or CAG IDs), or UEs that support only legacy networks (without NPN features), may ignore the cell reservation associated with the PLMN IDs as an operator use IE.

UE behavior jointly considering multiple IEs

In one embodiment, if a UE (e.g., a UE supporting only legacy networks (without NPN features), a UE having a registered (or selected) PLMN ID and supporting networks including NPN features, a UE having a registered (or selected) PLMN ID and/or NID, a UE having a registered (or selected) PLMN ID and/or CAG ID) does not prohibit itself from accessing the cell based on a cell barring IE received by a cell broadcast, a cell reservation for other use IEs, and/or a cell reservation for an operator use IE, the UE may treat the cell as a candidate cell during a cell (re) selection procedure. The UE may camp on the cell or (re) select the cell.

In one embodiment, if a UE (e.g., a UE supporting only legacy networks (without NPN features), a UE having a registered (or selected) PLMN ID and supporting networks including NPN features, a UE having a registered (or selected) PLMN ID and/or NID, a UE having a registered (or selected) PLMN ID and/or CAG ID) disables itself based on a received cell barring IE, then either the received cell is reserved for operator use IE or the received cell is reserved for other use IE, the UE may not be allowed to (re) select the cell, or even be unable to (re) select the cell for limited service and/or emergency calls. In one embodiment, if the UE disables itself based on the received cell disable IE and if the cell supports (at least) PNI-NPN (e.g., CAG cells) (e.g., the UE receives at least one PLMN ID and/or CAG ID from the cell in the system information), the UE may camp on that cell as an acceptable cell for emergency services (or limited services). In one embodiment, if the UE disables itself based on the received cell disable IE and if the cell supports (at least) PNI-NPN (e.g., CAG cell) (e.g., the UE receives at least one PLMN ID and/or CAG ID from the cell in the system information) and if the cell supports emergency services/calls (or limited services) (e.g., the UE may receive an indicator broadcast by the cell supporting PNI-NPN features, wherein the indicator may be associated with the PNI-NPN information broadcast by the cell, wherein the indicator may indicate whether the cell supports emergency services/calls (or limited services)), the UE may camp on the cell as an acceptable cell for emergency services (or limited services).

In one embodiment, if a UE (e.g., a UE supporting only legacy networks (without NPN features), a UE having a registered (or selected) PLMN ID and supporting networks including NPN features, a UE having a registered (or selected) PLMN ID and/or NID, a UE having a registered (or selected) PLMN ID and/or CAG ID) disables itself based on a received cell reservation as an operator use IE, the UE may not be allowed to (re) select the cell, or even be able to (re) select the cell for limited service and/or emergency calls, regardless of the received cell prohibition IE and the received cell reservation as other use IEs. In one embodiment, if the UE disables itself for the operator based on the received cell reservation using the IE, and if the cell supports (at least) PNI-NPN (e.g., CAG cells) (e.g., the UE receives at least one PLMN ID and/or CAG ID from the cell in the system information), the UE may camp on the cell as an acceptable cell for emergency services/calls (or limited services). In one embodiment, if the UE disables itself based on the received cell reservation as an operator use IE, and if the cell supports (at least) PNI-NPN (e.g., CAG cell) (e.g., the UE receives at least one PLMN ID and/or CAG ID from the cell in the system information), and if the cell supports emergency services/calls (or limited services) (e.g., the UE may receive an indicator broadcast by the cell supporting PNI-NPN features, wherein the indicator may be associated with the PNI-NPN information broadcast by the cell, wherein the indicator may indicate whether the cell supports emergency services/calls (or limited services)), the UE may camp on the cell that is an acceptable cell for emergency services/calls (or limited services).

In one embodiment, if a UE (e.g., a UE supporting only legacy networks (without NPN features), a UE having a registered (or selected) PLMN ID and supporting networks including NPN features, a UE having a registered (or selected) PLMN ID and/or NID, a UE having a registered (or selected) PLMN ID and/or CAG ID) disables itself based on a received cell reservation as other usage IEs, the UE may not be allowed to (re) select the cell, or even be unable to (re) select the cell for limited service and/or emergency calls, regardless of the received cell reservation as operator usage IE and the received cell disabling IE. In one embodiment, if the UE disables itself based on the received cell reservation for other usage IEs and if the cell supports (at least) PNI-NPN features (e.g., CAG cells) (e.g., the UE receives at least one PLMN ID and/or CAG ID broadcast by the cell in system information), the UE may camp on the cell that is an acceptable cell for emergency services/calls (or limited services). In one embodiment, if the UE disables itself based on the received cell reservation for other usage IEs and if the cell supports (at least) a PNI-NPN feature (e.g., CAG cell) (e.g., the UE receives at least one PLMN ID and/or CAG ID broadcast by the cell in system information) and if the cell supports emergency services/calls (or limited services) (e.g., the UE may receive an indicator broadcast by the cell supporting the PNI-NPN feature, wherein the indicator may be associated with the PNI-NPN information broadcast by the cell, wherein the indicator may indicate whether the cell supports emergency services/calls (or limited services)), the UE may camp on the cell that is an acceptable cell for emergency services (or limited services).

Processing of Tracking Area Codes (TACs)

In some implementations, the cell may broadcast a particular TAC value associated with the corresponding PLMN ID and/or CAG ID. If the UE (e.g., a UE supporting only legacy networks (without NPN feature), a UE having a registered (or selected) PLMN ID and supporting networks including NPN feature, a UE having a registered (or selected) PLMN ID and/or NID, a UE having a registered (or selected) PLMN ID and/or CAG ID) receives a PLMN ID and/or CAG ID from the cell with the corresponding TAC field being null, the UE may still apply limited services to the cell (e.g., a cell supporting only CAG feature, a cell supporting only CAG). Thus, the cell may support limited services (e.g., emergency services/calls, earthquake and Tsunami Warning System (ETWS), commercial mobile warning system (CMAS) notifications, public Safety (PS) related side link communications (Tx/Rx), V2X side link communications (Tx/Rx), and PS related side link discovery (Tx/Rx)). The UE may consider the cell as a candidate for an acceptable cell. The UE may camp on the cell or (re) select the cell.

In some implementations, the cell may not broadcast a particular TAC value associated with the corresponding PLMN ID and/or CAG ID. That is, TAC values corresponding to PLMN IDs and/or CAG IDs may not exist. If the UE (e.g., a UE supporting only legacy networks (without NPN feature), a UE having a registered (or selected) PLMN ID and supporting networks including NPN feature, a UE having a registered (or selected) PLMN ID and/or NID, a UE having a registered (or selected) PLMN ID and/or CAG ID) receives a PLMN ID and/or CAG ID from the cell with the corresponding TAC field being null, the UE may still apply limited services to the cell (e.g., a cell supporting only CAG feature, a cell supporting only CAG). Thus, limited services are allowed. The UE may consider the cell as a candidate for an acceptable cell. The UE may camp on the cell or (re) select the cell.

In some implementations, the cell may broadcast a particular TAC value associated with the corresponding PLMN ID and/or NID. If a UE (e.g., a UE supporting only a legacy network (without NPN feature), a UE having a registered (or selected) PLMN ID and supporting a network including NPN feature, a UE having a registered (or selected) PLMN ID and/or NID, a UE having a registered (or selected) PLMN ID and/or CAG ID) receives a PLMN ID and/or NID from a cell while the corresponding TAC field is null, the UE may prohibit the cell (e.g., a cell supporting only SNPN feature, a cell supporting only SNPN). The UE may not consider the cell as a candidate cell for the cell (re) selection procedure.

In some implementations, the cell may not broadcast a particular TAC value associated with the corresponding PLMN ID and/or NID. For example, a cell supporting only SNPN features may not broadcast a particular TAC value associated with a corresponding PLMN ID and/or NID.

In some embodiments, the UE may not prohibit itself from accessing the cell may indicate that the UE may consider the cell as a candidate cell for cell (re) selection. The UE may further camp on the cell or (re) select the cell.

In the present disclosure, network (NW), cell, camping cell, serving cell, base station, gNB, eNB, and ng-eNB may be used interchangeably. In some implementations, some of these items may refer to the same network entity.

The disclosed mechanisms may be applied to any RAT. RATs may include, but are not limited to, NR-U, LTE, E-UTRA connected to 5GC, LTE connected to 5GC, E-UTRA connected to EPC, and LTE connected to EPC.

The disclosed mechanisms may be used for licensed frequencies and/or unlicensed frequencies.

System Information (SI) may include MIB, SIB1, and other SI. The minimum SI may include MIB and SIB1. Other SIs may refer to SIB2, SIB3, SIB4, SIB5, and other SIB(s).

Dedicated signaling may refer to, but is not limited to, RRC message(s), such as RRC (connection) setup request message, RRC (connection) setup complete message, RRC (connection) reconfiguration message, RRC reconfiguration message with information including synchronous configuration reconfiguration, RRC reconfiguration message without information of synchronous configuration reconfiguration, information of synchronous configuration reconfiguration included in RRC reconfiguration message, RRC (connection) reconfiguration complete message, RRC (connection) restoration request message, RRC (connection) restoration complete message, RRC (connection) reestablishment request message, RRC (connection) reestablishment complete message, RRC (connection) rejection message, RRC (connection) release message, RRC system information request message, UE assistance information message, UE capability query message, and UE capability information message. The UE may monitor a UE-specific search space (USS) to derive time/frequency resources (e.g., physical Downlink Shared Channel (PDSCH) resources) for receiving dedicated signaling.

The rrc_idle/rrc_inactive UE may camp on a cell (e.g., camping cell). The rrc_connected UE may be served by a (serving) cell. Embodiments in the present disclosure may be applicable to rrc_idle/rrc_inactive/rrc_connected UE(s).

The UE may be served by a cell (e.g., a serving cell). The serving cell may serve (but is not limited to) the rrc_connected UE. The serving cell may be, but is not limited to, a suitable cell.

The UE may camp on a cell (e.g., camping on a cell). The camping cell may be a suitable cell or an acceptable cell.

A suitable cell is a cell on which the UE may camp. The UE (e.g., especially not in SNPN access mode) may consider the cell suitable if the following conditions are met: (1) The cell is part of a selected PLMN or a registered PLMN or PLMN equivalent list, and (2) cell selection criteria (e.g., S criteria) of the cell are met. Furthermore, the appropriate cell is not barred according to the latest information provided by the NAS of the UE. The suitable cell is part of at least one Tracking Area (TA) which is not part of the "forbidden tracking area" list, which belongs to a PLMN which fulfils condition (1).

An acceptable cell is one on which the UE may camp to obtain limited services (initiate an emergency call and receive ETWS and CMAS notifications). Such a cell may fulfill the following requirements, which is the minimum set of requirements for initiating emergency calls and receiving ETWS and CMAS notifications in the NR network: (1) The cell is not barred and/or (2) cell selection criteria are met.

Restricted services may include, but are not limited to, initiating emergency calls by the UE and/or receiving ETWS and CMAS notifications.

The disclosed mechanism(s) may be applied to a UE to access (but is not limited to) a PCell.

Primary cell (PCell): MCG cells operating on the primary frequency, wherein the UE performs an initial connection setup procedure or initiates a connection re-establishment procedure.

Primary SCG cell (PSCell): for dual connectivity operation, it refers to an SCG cell where the UE performs random access when performing a synchronization reconfiguration procedure.

The serving cell: there is only one serving cell including the primary cell for a UE in the rrc_connected state that is not CA/DC configured. For a UE in rrc_connected state configured with CA/DC, the term serving cell is used to denote a set of cells including the specific cell(s) and all secondary cells.

Secondary cell (SCell): for a UE configured with CA, it refers to a cell that provides additional radio resources over a particular cell.

Specific cell (SpCell): for dual connectivity operation, the term specific cell refers to the PCell of the MCG, and may also refer to the PSCell of the SCG, otherwise the term specific cell refers to the PCell.

Master Cell Group (MCG): in MR-DC, is a set of serving cells associated with a Master Node (Master Node), including a SpCell (e.g., PCell) and optionally one or more scells.

And (3) a master node: in MR-DC is a radio access node providing control plane connectivity to the core network. It may be a master eNB (in E-UTRA NR-Dual connectivity (EN-DC)), a master ng-eNB (in the next generation E-UTRA NR-Dual connectivity (NGEN-DC)) or a master gNB (in NR-Dual connectivity (NR-DC) and NR E-UTRA-Dual connectivity (NE-DC)).

Secondary Cell Group (SCG): in MR-DC, there is a set of serving cells associated with the secondary node, including a SpCell (e.g., PSCell) and optionally one or more scells.

Secondary node: in MR-DC, which is a radio access node, there is no control plane connection to the core network, providing additional resources for the UE. It may be a gNB (in EN-DC), a secondary ng-eNB (in NE-DC) or a secondary gNB (in NR-DC and NGEN-DC).

Fig. 1 is a flowchart illustrating a method 100 performed by a UE for cell reservation and access restriction according to an example embodiment of the present disclosure. In act 102, the UE may receive a MIB from the cell, the MIB including a cell barring IE. In one implementation, the cell barring IE may be in an enumerated { "barred", "non-barred" } format. In act 104, the UE may receive SIB1 from the cell, the SIB1 including a first NPN ID, a first cell reservation for an operator use IE associated with the first NPN ID, and a cell reservation for other use IEs. In one implementation, cell reservation for other usage IEs may be in an enumerated { "true", "not true" } format or an enumerated { "true" } format. In one implementation, the cell reservation for the operator use IE may be in an enumerated { "reserved", "unreserved" } format or an enumerated { "reserved" } format.

In one embodiment, the first NPN ID may be one of SNPN ID and PNI-NPN ID. In one embodiment SNPN ID may include a PLMN ID and NID. In one embodiment, the PNI-NPN ID may include a PLMN ID and a CAG ID. In one embodiment, SIB1 may include multiple NPN IDs, each of which is associated with an information element reserved for operator use IE by the cell. That is, the cell may be instructed to reserve an IE for the operator according to NPN. For example, SIB1 may further include a second NPN ID and a second cell reservation associated with the second NPN ID for an operator usage IE. In one embodiment, the cell barring IE may be common to all PLMNs/NPN supported by the cell or indicated in SIB 1. For example, the cell barring IE may be common to the first NPN indicated by the first NPN ID and the second NPN indicated by the second NPN ID. In one embodiment, SIB1 may further include a first TAC associated with the first NPN ID. SIB1 may further include a second TAC associated with the second NPN ID. In one embodiment, SIB1 may further include a list of PLMN IDs. The cell barring IE may be common to all PLMNs indicated by the PLMN ID list. In one embodiment, the cell reservation for other usage IEs may also be common to all PLMNs indicated by the PLMN ID list.

In act 106, the UE may determine whether to consider the cell as a forbidden cell or a candidate cell for a cell selection or cell reselection procedure based on the cell forbidden IE, the cell reserved for operator use IE, and the cell reserved for other use IE. In one embodiment, the UE may determine the cell as a barred cell if the cell barred IE is "barred". In one embodiment, the UE may further determine whether to consider the cell as a forbidden cell or a candidate cell for a cell selection or cell reselection procedure based on the access ID of the UE. As specified in 3GPP TS24.501V16.2.0, the access ID may range from 0 to 15.

In act 108, when the cell barring IE is "not barred", the cell reservation is other use IE is not "true", the cell reservation is the operator use IE is "reserved", the first NPN ID matches the registered SNPN ID of the UE, and the access ID of the UE is 11 or 15, the UE may determine to consider the cell as a candidate cell for the cell selection or cell reselection procedure.

In one embodiment, when the cell barring IE is "not barred", the cell reservation is that the other use IEs are not "true", the first cell reservation is that the operator use IE is "reserved", the first NPN ID matches the registered SNPN ID of the UE, and the access ID of the UE is 0, 1,2, 12, 13, or 14, the UE may determine to consider the cell as a barred cell.

Fig. 2 is a flowchart illustrating a method 200 performed by a UE for determining whether to consider a cell as a candidate cell or a forbidden cell according to example embodiments of the present disclosure. Method 200 may be an embodiment of act 106 shown in fig. 1. In act 202, the UE may check a cell barring IE, which may be broadcast from the cell via the MIB. If the cell barring IE is "barred," the UE may perform act 212 to treat the cell as a barred cell. If the cell barring IE is not "barred," the UE may perform act 204 to check that the cell reservation is other usage IEs. If the cell reservation is that the other usage IE is "true," the UE may perform act 212 to treat the cell as a forbidden cell. If the cell reservation is not true for the other usage IE, the UE may perform act 206 to check that the cell reservation is for the operator usage IE.

In act 206, the UE may check that the cell reservation is an operator use IE that is associated with the UE's registered (or selected) NPN. For example, the UE may receive SIB1, the SIB1 including a first NPN ID, a first cell reservation associated with the first NPN ID for an operator use IE, a second NPN ID, a second cell reservation associated with the second NPN ID for an operator use IE. If the registered (or selected) NPN of the UE corresponds to the first NPN ID, the UE may check that the first cell is reserved for operator use IE (and ignore the second cell is reserved for operator use IE). If the registered (or selected) NPN of the UE corresponds to the second NPN ID, the UE may check that the second cell is reserved for operator use IE (and ignore the first cell is reserved for operator use IE). If the cell reservation is "reserved" for operator use IE in act 206, the UE may perform act 212 to treat the cell as a forbidden cell. If the cell reservation is "reserved" for operator use IE in act 206, the UE may perform act 208.

When the first cell reservation is used as the carrier usage IE in act 206, the UE may check whether the first NPN ID matches the registered SNPN ID of the UE in act 208. If the first NPN ID does not match the registration SNPN ID of the UE, the UE may perform act 212 to treat the cell as a forbidden cell. If the first NPN ID matches the registration SNPN ID of the UE, the UE may perform act 210 to check the access ID of the UE. If the access ID of the UE is 0,1, 2, 12, 13, or 14, the UE may perform act 212 to treat the cell as a forbidden cell. If the access ID of the UE is 11 or 15, the UE may perform act 214 to treat the cell as a candidate cell.

The acts illustrated in fig. 2 should not be construed as necessarily order dependent. The order in which the processes are described is not intended to be construed as a limitation. Acts 202, 204, 206, 208, and 210 may be performed in a different order than shown in fig. 2. For example, in one embodiment, act 206 may be performed prior to act 204, in one embodiment act 210 may be performed prior to act 208, and so on.

Fig. 3 is a flowchart illustrating a method 300 performed by a UE for determining whether to consider a cell as a candidate cell or a forbidden cell according to another example embodiment of the disclosure. Method 300 may be another embodiment of act 106 shown in fig. 1. Blocks having the same reference numerals as in fig. 2 may be referred to as a description with respect to fig. 2. For example, descriptions regarding acts 202, 204, 206, 208, 210, 212, and 214 in FIG. 3 may refer to acts 202, 204, 206, 208, 210, 212, and 214, respectively, in FIG. 2. In act 204, the UE may check that the cell reservation is other usage IEs. If the cell reservation is "not true" for the other usage IEs, the UE may perform act 206. If the cell reservation is "true" for the other usage IEs, the UE may perform act 306 to check that the cell reservation is for the operator usage IEs. If the cell reservation is "reserved" for the operator use IE, the UE may perform act 212 to treat the cell as a forbidden cell. If the cell reservation for operator use IE is not "reserved," the UE may perform act 308 to check if the UE is NPN capable. If the UE is not NPN capable, the UE may perform act 212 to treat the cell as a forbidden cell. If the UE is NPN capable, the UE may perform act 214 to treat the cell as a candidate cell. The acts illustrated in fig. 3 should not be construed as necessarily order dependent. The order in which the processes are described is not intended to be construed as a limitation. For example, in one embodiment, act 308 may be performed prior to act 306.

In one embodiment, the UE is not NPN-capable if the UE supports only legacy networks (no NPN features), the UE does not support NPN features, or the UE supports only legacy features that do not include NPN features (e.g., prior to Rel-16). In one embodiment, the UE is not NPN-capable if the UE has a registered (or selected) PLMN and supports a network that includes NPN features. In one embodiment, the UE is NPN-capable if the UE has registered (or selected) SNPN or registered (or selected) PNI-NPN.

Fig. 4 illustrates a block diagram of a node 400 for wireless communication in accordance with various aspects of the disclosure. As shown in fig. 4, node 400 may include a transceiver 420, a processor 428, a memory 434, one or more presentation components 438, and at least one antenna 436. Node 400 may also include a Radio Frequency (RF) spectrum band module, a BS communication module, a network communication module, and a system communication management module, input/output (I/O) ports, I/O components, and a power supply (not explicitly shown in fig. 4).

Each of these components may communicate with each other directly or indirectly through one or more buses 440. In one embodiment, the node 400 may be a UE or BS that performs various functions such as those described herein with reference to fig. 1-3.

Transceiver 420 has a transmitter 422 (e.g., transmission/reception) circuit and a receiver 424 (e.g., reception/reception) circuit) and may be configured to transmit and/or receive time and/or frequency resource partition information. Transceiver 420 may be configured to transmit in different types of subframes and slots including, but not limited to, usable, unusable, and flexibly usable subframe and slot formats. Transceiver 420 may be configured to receive data and control channels.

Node 400 may include a variety of computer-readable media. Computer readable media can be any available media that can be accessed by node 400 and includes both volatile (and nonvolatile) media and removable (and non-removable) media.

Computer-readable media include computer storage media and communication media. Computer storage media may include volatile (and/or nonvolatile) and removable (and/or non-removable) media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules, or data.

Computer storage media may include RAM, ROM, EPROM, EEPROM, flash memory (or other storage technology), CD-ROM, digital versatile disk (DIGITAL VERSATILE DISK, DVD) (or other optical storage), magnetic tape, magnetic disk storage (or other magnetic storage device), and the like. The computer storage medium may not include a propagated data signal. Communication media typically embodies 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 includes any information delivery media.

The term "modulated data signal" means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. Communication media may include 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 any of the above should also be included within the scope of computer readable media.

Memory 434 may include computer storage media in the form of volatile and/or nonvolatile memory. The memory 434 may be removable, non-removable or a combination thereof. For example, the memory may include solid state memory, a hard disk drive, an optical disk drive, and the like. As shown in fig. 4, the memory 434 may store computer-readable and/or computer-executable instructions 432 (e.g., software code) that, when executed, are configured to cause the processor 428 to perform the various functions described herein, e.g., with reference to fig. 1-3. Alternatively, the instructions 432 may not be directly executed by the processor 428, but may be configured to cause the node 400 (e.g., when compiled and executed) to perform the various functions described herein.

The processor 428 (e.g., with processing circuitry) may include intelligent hardware devices, a central processing unit (Central Processing Unit, CPU), a microcontroller, an ASIC, and the like. The processor 428 may include a memory. Processor 428 may process data 430 and instructions 432 received from memory 434, as well as information via transceiver 420, a baseband communication module, and/or a network communication module. Processor 428 may also process information to be sent to transceiver 420 for transmission to a network communication module for transmission to a CN via antenna 436.

One or more presentation components 438 can present data indications to a person or other device. Examples of presentation component 438 can include a display device, a speaker, a printing component, a vibrating component, and so forth.

From the present disclosure, it will be seen that the concepts described in this disclosure may be implemented using a variety of techniques without departing from the scope of these concepts. Furthermore, while these concepts have been described with specific reference to certain implementations, those of ordinary skill in the art will recognize that changes may be made in form and detail without departing from the scope of the concepts. The described implementations are, therefore, to be considered in all respects as illustrative and not restrictive. It should also be understood that the present disclosure is not limited to the particular embodiments described above. However, many rearrangements, modifications, and substitutions are possible without departing from the scope of the disclosure.

Claims

1. A user equipment, UE, characterized in that the UE comprises:

One or more non-transitory computer-readable media having computer-executable instructions embodied thereon; and

At least one processor coupled to the one or more non-transitory computer-readable media, the at least one processor configured to execute the computer-executable instructions to:

receiving a master information block, MIB, from a cell, the MIB including a cell barring information element, IE;

receiving a system information block type 1, SIB1, from the cell, the SIB1 including a first non-public network, NPN, identity, an operator use IE reserved for a first cell associated with the first NPNID and other use IEs reserved for the cell; and

Determining whether to consider the cell as a forbidden cell or a candidate cell for a cell selection or cell reselection procedure based on the cell forbidden IE, the first cell reserved for operator use IE, and the cell reserved for other use IE,

Wherein when the cell barring IE is "not barred", the cell reservation is that the other use IEs are not "true", the first cell reservation is that the operator use IE is "reserved", the first NPN ID matches with the registered independent non-public network SNPN ID of the UE, and the access ID of the UE is 11 or 15, the UE regards the cell as the candidate cell for the cell selection or cell reselection procedure.

2. The UE of claim 1, wherein the first NPN ID is one of SNPNID and public network integrated non-public network PNI-NPNID.

3. The UE of claim 2, wherein SNPN ID comprises a public land mobile network PLMNID and a network identification NID.

4. The UE of claim 2, wherein the PNI-NPN ID comprises a public land mobile network PLMNID and a closed access group CAGID.

5. The UE of claim 1, wherein the SIB1 further comprises a second NPNID and a second cell reservation associated with the second NPNID for operator use IE.

6. The UE of claim 5, wherein the cell barring IE is common to a first NPN indicated by the first NPN ID and a second NPN indicated by the second NPN ID.

7. The UE of claim 1, wherein the SIB1 further includes a first tracking area code TAC associated with the first NPN ID.

8. The UE of claim 1, wherein the SIB1 further comprises a list of public land mobile network PLMNIDs.

9. The UE of claim 8, wherein the cell barring IE and the cell reservation are common to all PLMNs indicated by the PLMNID list for other usage IEs.

10. The UE of claim 1, wherein the UE treats the cell as the barred cell when the cell barred IE is "not barred", the cell reserved for other uses IE is not "true", the first cell reserved for operator uses IE is "reserved", the first NPNID matches the registered SNPN ID of the UE, and the access ID of the UE is 0,1,2, 12, 13, or 14.

11. A method performed by a user equipment, UE, for wireless communication, the method comprising:

Determining whether to consider the cell as a forbidden cell or a candidate cell for a cell selection or cell reselection procedure based on the cell forbidden IE, the first cell reserved for operator use IE and the cell reserved for other use IE,

12. The method of claim 11, wherein the first NPN ID is one of SNPNID and public network integrated non-public network PNI-NPNID.

13. The method of claim 12, wherein SNPN ID comprises a public land mobile network PLMNID and a network identification NID.

14. The method of claim 12, wherein the PNI-NPN ID comprises a public land mobile network PLMNID and a closed access group CAGID.

15. The method of claim 11, wherein the SIB1 further comprises a second NPNID and a second cell reservation associated with the second NPNID for operator use IE.

16. The method of claim 15, wherein the cell barring IE is common to a first NPN indicated by the first NPN ID and a second NPN indicated by the second NPN ID.

17. The method of claim 11, wherein the SIB1 further includes a first tracking area code TAC associated with the first NPN ID.

18. The method of claim 11, wherein the SIB1 further comprises a list of public land mobile networks, PLMNIDs.

19. The method of claim 18, wherein the cell barring IE and the cell reservation are common to all PLMNs indicated by the PLMN ID list for other usage IEs.

20. The method of claim 11, wherein the UE treats the cell as the barred cell when the cell barred IE is "not barred", the cell reserved for other uses IE is not "true", the first cell reserved for operator uses IE is "reserved", the first NPNID matches the registered SNPN ID of the UE, and the access ID of the UE is 0, 1,2, 12, 13, or 14.