Minimal SI structure

Abstract

The UE may receive an indication of a first assignment of a first PDSCH from a network entity via a PBCH. The first PDSCH may include at least a first portion of the SIB. The UE may receive the first portion of the SIB from the network entity via the first PDSCH based on the first assignment of the first PDSCH. The first portion of the SIB may include access control information for the network entity and an assignment for a second portion of the SIB. The UE may identify whether the UE is permitted to access the network entity based on the access control information for the network entity.

Description

[0001] Cross - Reference to Related Applications

[0002] This application claims the benefit of U.S. Non - Provisional Patent Application Serial No. 18 / 052,565, filed on November 3, 2022, entitled "STRUCTURE OF MINIMUM SI (Structure of Minimum SI)", which is hereby incorporated by reference in its entirety. Field of the Invention

[0003] The present disclosure relates generally to communication systems, and more particularly to the communication of system information in a wireless communication system. Background Art

[0004] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasting. A typical wireless communication system may employ a multiple access technology that is capable of supporting communication with multiple users by sharing the available system resources. Examples of such multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single - Carrier Frequency Division Multiple Access (SC - FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD - SCDMA) systems.

[0005] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at the city, national, regional, and even global levels. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the ongoing evolution of mobile broadband promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., related to the Internet of Things (IoT)), and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine - type communication (mMTC), and ultra - reliable low - latency communication (URLLC). Certain aspects of 5G NR may be based on the 4G Long - Term Evolution (LTE) standard. Further improvements to 5G NR technology are needed. In addition, these improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the Invention

[0006] A simplified summary of one or more aspects is presented below in order to provide a basic understanding of these aspects. This summary is not an extensive overview of all contemplated aspects. This summary neither identifies key or critical elements of all aspects nor describes the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.

[0007] In one aspect of the present disclosure, a method, a computer-readable medium, and a device are provided. The device may be a user equipment (UE). The device may receive an indication of a first assignment of a first physical downlink shared channel (PDSCH) from a network entity via a physical broadcast channel (PBCH). The first PDSCH may include at least a first part of a system information block (SIB). The device may receive the first part of the SIB from the network entity via the first PDSCH based on the first assignment of the first PDSCH.

[0008] In one aspect of the present disclosure, a method, a computer-readable medium, and a device are provided. The device may be a user equipment (UE). The device may receive the first part of the SIB from a network entity. The first part of the SIB may include access control information for the network entity and may indicate an assignment of a second PDSCH when the access control information indicates that the UE is permitted to access the network entity. The device may identify whether the UE is permitted to access the network entity based on the access control information for the network entity.

[0009] In one aspect of the present disclosure, a method, a computer-readable medium, and a device are provided. The device may be a network entity. The device may send an indication of a first assignment of a first PDSCH for a UE via the PBCH. The first PDSCH may include at least a first part of the SIB. The device may send the first part of the SIB for the UE via the first PDSCH based on the first assignment of the first PDSCH.

[0010] In one aspect of the present disclosure, a method, a computer-readable medium, and a device are provided. The device may be a network entity. The device may send the first part of the SIB for a UE. The first part of the SIB may include access control information for the network entity. Based on the access control information for the network entity, the UE may or may not be permitted to access the network entity. The device may send a second part of the SIB for the UE via a second PDSCH based on a second assignment of the second PDSCH when the UE is permitted to access the network entity. When the UE is permitted to access the network entity, the second assignment of the second PDSCH may be based on the first part of the SIB.

[0011] To achieve the foregoing and related purposes, one or more aspects include the features described comprehensively below and particularly pointed out in the claims. The following description and the drawings set forth in detail some illustrative features of one or more aspects. However, these features indicate only some of the various ways in which the principles of the various aspects may be employed. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Figure 1 is a diagram illustrating an example of a wireless communication system and an access network.

[0013] Figure 2A Is a diagram illustrating an example of a first frame according to various aspects of the present disclosure.

[0014] Figure 2B Is a diagram illustrating an example of a downlink (DL) channel within a subframe according to various aspects of the present disclosure.

[0015] Figure 2C Is a diagram illustrating an example of a second frame according to various aspects of the present disclosure.

[0016] Figure 2D Is a diagram illustrating an example of an uplink (UL) channel within a subframe according to various aspects of the present disclosure.

[0017] Figure 3 Is a diagram illustrating an example of a base station and a user equipment (UE) in an access network.

[0018] Figure 4 Is a diagram illustrating various example minimum system information (MSI) structures.

[0019] Figure 5 Is a diagram illustrating an MSI structure according to one or more aspects.

[0020] Figure 6 Is a diagram illustrating various fields in an example enhanced physical broadcast channel (ePBCH) according to one or more aspects.

[0021] Figure 7 Is a diagram illustrating various fields of an example SIB1-a according to one or more aspects.

[0022] Figure 8 Is a diagram of a communication flow of a method for wireless communication.

[0023] Figure 9 Is a flowchart of a method for wireless communication.

[0024] Figure 10 Is a flowchart of a method for wireless communication.

[0025] Figure 11 Is a flowchart of a method for wireless communication.

[0026] Figure 12 Is a flowchart of a method for wireless communication.

[0027] Figure 13 Is a flowchart of a method for wireless communication.

[0028] Figure 14 Is a flowchart of a method for wireless communication.

[0029] Figure 15It is a flowchart of a method for wireless communication.

[0030] Figure 16 It is a flowchart of a method for wireless communication.

[0031] Figure 17 It is a diagram illustrating an example of a hardware implementation for exemplifying a device and / or a network entity.

[0032] Figure 18 It is a diagram illustrating an example of a hardware implementation for exemplifying a network entity. Detailed Description

[0033] In some configurations, to obtain SIB1, the UE may monitor a Type0-Common Search Space (CSS) set and may perform blind decoding on the scheduling Physical Downlink Control Channel (PDCCH) for SIB1 (e.g., Control Resource Set (CORESET) #0). To enable the UE to identify whether the UE is authorized to access the network entity, the UE may decode a large Transport Block (TB) (e.g., more than 300 bytes), even though the access / barring control information may occupy much less space. It may be desirable to improve the efficiency of Minimum System Information (MSI) delivery or decoding.

[0034] According to one or more aspects, the UE may receive an indication of a first assignment of a first PDSCH from the network entity via the PBCH. The first PDSCH may include at least a first part of the SIB. The UE may receive the first part of the SIB from the network entity via the first PDSCH based on the first assignment of the first PDSCH. The first part of the SIB may include access control information for the network entity. The UE may identify whether the UE is permitted to access the network entity based on the access control information for the network entity. Thus, the UE may be able to identify whether the UE may camp on the network entity (e.g., whether the UE is authorized) without decoding the large SIB1. In addition, the UE may be able to decode System Information (SI) without performing blind decoding on the PDCCH or performing less blind decoding on the PDCCH.

[0035] The detailed description set forth below in connection with the accompanying drawings is a description of various configurations and does not represent the only configurations in which the concepts described herein may be practiced. To provide a thorough understanding of the various concepts, the detailed description includes specific details. However, the concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0036] Certain aspects of a telecommunications system are presented with reference to various apparatus and methods. These apparatus and methods are described in the following detailed description, and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). The elements can be implemented using electronic hardware, computer software, or any combination thereof. Whether an element is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

[0037] By way of example, an element, or any portion of an element, or any combination of elements can be implemented as a "processing system" that includes one or more processors. Examples of processors include a microprocessor, a microcontroller, a graphics processing unit (GPU), a central processing unit (CPU), an application processor, a digital signal processor (DSP), a reduced instruction set computing (RISC) processor, a system on a chip (SoC), a baseband processor, a field programmable gate array (FPGA), a programmable logic device (PLD), a state machine, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functions described throughout this disclosure. One or more processors in the processing system can execute software. Software should be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, or any combination thereof, regardless of whether it is referred to as software, firmware, middleware, microcode, hardware description language, or other terms.

[0038] Thus, in one or more example aspects, embodiments, and / or use cases, the described functionality can be implemented in hardware, software, or any combination thereof. If implemented in software, the functionality can be stored or encoded on a computer-readable medium as one or more instructions or code. Computer-readable media includes computer storage media. Storage media can be any available media that can be accessed by a computer. By way of example, such computer-readable media can include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of these types of computer-readable media, or any other medium that can be used to store computer-executable code in the form of instructions or data structures that can be accessed by a computer.

[0039] Although aspects, embodiments, and / or use cases are described by way of some examples in this application, additional or different aspects, embodiments, and / or use cases may arise in many different arrangements and scenarios. The aspects, embodiments, and / or use cases described herein may be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, aspects, embodiments, and / or use cases may be embodied via integrated chips and other devices based on non-module components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchase devices, medical devices, artificial intelligence (AI)-enabled devices, etc.). Although some examples may or may not be specifically targeted at use cases or applications, the examples described may have broad applicability. Aspects, embodiments, and / or use cases may range from chip-level or modular components to non-modular, non-chip-level embodiments, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more of the technologies herein. In some actual settings, devices incorporating the aspects and features described may also include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily includes multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The technologies described herein may be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated components, or disaggregated components, end-user devices, etc., of various sizes, shapes, and configurations.

[0040] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or constituent parts in multiple ways. In a 5G NR system or network, network nodes, network entities, mobility elements of the network, radio access network (RAN) nodes, core network nodes, network elements, or network equipment (such as a base station (BS)) or one or more units (or one or more components) performing base station functions may be implemented in an aggregated or disaggregated architecture. For example, a BS (such as a Node B (NB), evolved NB (eNB), NR BS, 5G NB, access point (AP), transmit receive point (TRP), or cell, etc.) may be implemented as an aggregated base station (also referred to as a stand-alone BS or monolithic BS) or a disaggregated base station.

[0041] A centralized base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A split base station may be configured to utilize a protocol stack that is physically or logically distributed across two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0042] Base station operation or network design may consider the aggregation characteristics of base station functionality. For example, a split base station may be used in an integrated access backhaul (IAB) network, an open radio access network (O-RAN, such as a network configuration advocated by the O-RAN Alliance), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Splitting may include distributing functions across two or more units at various physical locations, as well as virtually distributing the functions of at least one unit, which may achieve flexibility in network design. The various units of a split base station or a split RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0043] Figure 1 FIG. 100 is a diagram illustrating an example of a wireless communication system and an access network. The illustrated wireless communication system includes a split base station architecture. The split base station architecture may include one or more CUs 110, which may communicate directly with the core network 120 via a backhaul link, or indirectly with the core network 120 through one or more split base station units, such as a near real-time (near RT) RAN intelligent controller (RIC) 125 via an E2 link, or a non-real-time (non RT) RIC 115 associated with a service management and orchestration (SMO) framework 105, or both. The CU 110 may communicate with one or more DUs 130 via a respective midhaul link, such as an F1 interface. The DU 130 may communicate with one or more RUs 140 via a respective fronthaul link. The RU 140 may communicate with a respective UE 104 via one or more radio frequency (RF) access links. In some embodiments, the UE 104 may be served simultaneously by multiple RUs 140.

[0044] Each unit (i.e., CU 110, DU 130, RU 140, and the near RT RIC 125, non-RT RIC 115, and SMO framework 105) may include one or more interfaces or be coupled to one or more interfaces, which are configured to receive or transmit signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interfaces of these units may be configured to communicate with one or more of the other units via the transmission medium. For example, the units may include a wired interface that is configured to receive signals or transmit signals to one or more of the other units via a wired transmission medium. Additionally, the units may include a wireless interface, which may include a receiver, transmitter, or transceiver (such as an RF transceiver) that is configured to receive and / or transmit signals to one or more of the other units via a wireless transmission medium.

[0045] In some aspects, CU 110 may host one or more higher layer control functions. Such control functions may include Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Service Data Adaptation Protocol (SDAP), etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by CU 110. CU 110 may be configured to handle user plane functionality (i.e., Central Unit - User Plane (CU-UP)), control plane functionality (i.e., Central Unit - Control Plane (CU-CP)), or a combination thereof. In some specific implementations, CU 110 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units may communicate bidirectionally with the CU-CP units via an interface (such as an E1 interface). As needed, CU 110 may be implemented to communicate with DU 130 for network control and signaling.

[0046] DU 130 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 140. In some aspects, DU 130 may host one or more of the Radio Link Control (RLC) layer, Media Access Control (MAC) layer, and one or more high Physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation, and demodulation, etc.) at least partially according to a functional split (such as those defined by 3GPP). In some aspects, DU 130 may also host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 130 or with the control functions hosted by CU 110.

[0047] Lower layer functionality may be implemented by one or more RUs 140. In some deployments, the RUs 140 controlled by the DU 130 may correspond to logical nodes that host RF processing functions or low PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.) or both, at least in part based on function splitting (such as lower layer function splitting). In such an architecture, the RU 140 may be implemented to handle over-the-air (OTA) communication with one or more UEs 104. In some embodiments, the real-time and non-real-time aspects of control and user plane communication with the RU 140 may be controlled by the corresponding DU 130. In some scenarios, this configuration may enable the implementation of the DU 130 and the CU 110 in a cloud-based RAN architecture (such as a vRAN architecture).

[0048] The SMO framework 105 may be configured to support the deployment and orchestration of RANs with non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 105 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as the O1 interface). For virtualized network elements, the SMO framework 105 may be configured to interact with a cloud computing platform (such as the Open Cloud (O-Cloud) 190) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as the O2 interface). Such virtualized network elements may include, but are not limited to, the CU 110, the DU 130, the RU 140, and the near RT RIC 125. In some embodiments, the SMO framework 105 may communicate with the hardware aspects of the 4G RAN (such as the Open eNB (O-eNB) 111) via the O1 interface. Additionally, in some embodiments, the SMO framework 105 may communicate directly with one or more RUs 140 via the O1 interface. The SMO framework 105 may also include a non-RT RIC 115 configured to support the functionality of the SMO framework 105.

[0049] The non-RT RIC 115 can be configured to include logic functions that can implement non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) / machine learning (ML) (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 125. The non-RT RIC 115 can be coupled to or communicate with the near-RT RIC 125 (such as via the A1 interface). The near-RT RIC 125 can be configured to include logic functions that can implement near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via the E2 interface), which connects one or more CUs 110, one or more DUs 130, or both, and the O-eNB to the near-RT RIC 125.

[0050] In some specific implementations, to generate the AI / ML models to be deployed in the near-RT RIC 125, the non-RT RIC 115 can receive parameters or external enrichment information from an external server. Such information can be utilized by the near-RT RIC 125 and can be received from non-network data sources or from network functions at the SMO framework 105 or the non-RT RIC 115. In some examples, the non-RT RIC 115 or the near-RT RIC 125 can be configured to tune RAN behavior or performance. For example, the non-RT RIC 115 can monitor long-term trends and patterns of performance and employ an AI / ML model to perform corrective actions through the SMO framework 105 (such as reconfiguration via O1) or via creating RAN management policies (such as A1 policies).

[0051] At least one of CU 110, DU 130, and RU 140 may be referred to as base station 102. Thus, base station 102 may include one or more of CU 110, DU 130, and RU 140 (each component is indicated by a dashed line to indicate that each component may or may not be included in base station 102). Base station 102 provides an access point to core network 120 for UE 104. Base station 102 may include macro cells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Small cells include femto cells, pico cells, and micro cells. A network including both small cells and macro cells may be referred to as a heterogeneous network. The heterogeneous network may also include a home evolved Node B (eNB) (HeNB) that may provide services to a restricted group referred to as a closed subscriber group (CSG). The communication link between RU 140 and UE 104 may include an uplink (UL) (also referred to as a reverse link) transmission from UE 104 to RU 140 and / or a downlink (DL) (also referred to as a forward link) transmission from RU 140 to UE 104. The communication link may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may be through one or more carriers. For each carrier allocated in carrier aggregation with a total of up to Yx MHz (x component carriers) for transmission in each direction, base station 102 / UE 104 may use a spectrum with a bandwidth of up to Y MHz (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, etc.). These carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric for DL and UL (e.g., more or fewer carriers may be allocated for DL compared to UL). Component carriers may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell) and the secondary component carriers may be referred to as secondary cells (SCells).

[0052] Some UEs 104 may use a device-to-device (D2D) communication link 158 to communicate with each other. D2D communication link 158 may use DL / UL wireless wide area network (WWAN) spectrum. D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). D2D communication may be through various wireless D2D communication systems, such as, for example, Bluetooth, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

[0053] The wireless communication system may further include a Wi-Fi AP 150 that communicates with the UE 104 (also referred to as a Wi-Fi station (STA)) via a communication link 154, e.g., in an unlicensed spectrum such as the 5 GHz unlicensed spectrum. When communicating in an unlicensed spectrum, the UE 104 / AP 150 may perform a Clear Channel Assessment (CCA) before communication to determine whether the channel is available.

[0054] The electromagnetic spectrum is generally subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as Frequency Range Designation FR1 (410 MHz - 7.125 GHz) and FR2 (24.25 GHz - 52.6 GHz). Although a part of FR1 is greater than 6 GHz, in various documents and articles, FR1 is generally referred to (interchangeably) as the "sub-6 GHz" band. Regarding FR2, a similar naming issue sometimes occurs, which is generally (interchangeably) referred to as the "millimeter wave" band in documents and articles, although it is different from the Extremely High Frequency (EHF) band (30 GHz - 300 GHz) identified by the International Telecommunication Union (ITU) as the "millimeter wave" band.

[0055] The frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified operating bands for these mid-band frequencies as Frequency Range Designation FR3 (7.125 GHz - 24.25 GHz). The bands falling within FR3 may inherit FR1 characteristics and / or FR2 characteristics, and thus can effectively extend the features of FR1 and / or FR2 to the mid-band frequencies. In addition, higher bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as Frequency Range Designation FR2-2 (52.6 GHz - 71 GHz), FR4 (71 GHz - 114.25 GHz), and FR5 (114.25 GHz - 300 GHz). Each of these higher bands falls within the EHF band.

[0056] Considering the above aspects, unless otherwise specifically stated, if the term "sub-6 GHz" etc. is used in this article, it may broadly represent frequencies that can be less than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise specifically stated, if the term "millimeter wave" etc. is used in this article, it may broadly represent frequencies that can include mid-band frequencies, can be within FR2, FR4, FR2-2, and / or FR5, or can be within the EHF band.

[0057] Base station 102 and UE 104 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming. Base station 102 may transmit beamformed signal 182 to UE 104 in one or more transmission directions. UE 104 may receive the beamformed signal from base station 102 in one or more reception directions. UE 104 may also transmit beamformed signal 184 to base station 102 in one or more transmission directions. Base station 102 may receive the beamformed signal from UE 104 in one or more reception directions. Base station 102 / UE 104 may perform beam training to determine the optimal reception direction and transmission direction for each of base station 102 / UE 104. The transmission direction and reception direction of base station 102 may be the same or may not be the same. The transmission direction and reception direction of UE 104 may be the same or may not be the same.

[0058] Base station 102 may include and / or be referred to as gNB, Node B, eNB, access point, base station transceiver, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), transmit receive point (TRP), network node, network entity, network equipment, or some other suitable term. Base station 102 may be implemented as an integrated access and backhaul (IAB) node, a relay node, a sidelink node, an aggregated (monolithic) base station with a baseband unit (BBU) (including CU and DU) and RU, or as a disaggregated base station including one or more of CU, DU, and / or RU. A set of base stations including disaggregated base stations and / or aggregated base stations may be referred to as a next generation (NG) RAN (NG-RAN).

[0059] The core network 120 may include an Access and Mobility Management Function (AMF) 161, a Session Management Function (SMF) 162, a User Plane Function (UPF) 163, a Unified Data Management (UDM) 164, one or more Location Servers 168, and other functional entities. The AMF 161 is a control node that processes signaling between the UE 104 and the core network 120. The AMF 161 supports registration management, connection management, mobility management, and other functions. The SMF 162 supports session management and other functions. The UPF 163 supports packet routing, packet forwarding, and other functions. The UDM 164 supports the generation of Authentication and Key Agreement (AKA) credentials, user identity handling, access authorization, and subscription management. One or more Location Servers 168 are illustrated as including a Gateway Mobile Location Center (GMLC) 165 and a Location Management Function (LMF) 166. However, in general, one or more Location Servers 168 may include one or more location / locationing servers, which may include one or more of GMLC 165, LMF 166, a Position Determination Entity (PDE), a Serving Mobile Location Center (SMLC), a Mobile Positioning Center (MPC), etc. The GMLC 165 and the LMF 166 support UE location services. The GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE location information. The LMF 166 receives measurement and assistance information from the NG-RAN and the UE 104 via the AMF 161 to calculate the location of the UE 104. The NG-RAN may utilize one or more positioning methods to determine the location of the UE 104. Positioning the UE 104 may involve signal measurements, location estimation, and optional speed calculations based on these measurements. The signal measurements may be performed by the UE 104 and / or the serving base station 102. The measured signals may be based on a Satellite Positioning System (SPS) 170 (e.g., a Global Navigation Satellite System (GNSS), a Global Positioning System (GPS), a Non-Terrestrial Network (NTN), or one or more of other satellite positioning / locationing systems), an LTE signal, a Wireless Local Area Network (WLAN) signal, a Bluetooth signal, a terrestrial beacon system, sensor-based information (e.g., an atmospheric pressure sensor, a motion sensor), an NR Enhanced Cell ID (NR E-CID) method, an NR signal (e.g., multi-round-trip time (multi-RTT), DL Departure Angle (DL-AoD), DL Time Difference of Arrival (DL-TDOA), UL Time Difference of Arrival (UL-TDOA), and UL Arrival Angle (UL-AoA) positioning), and / or one or more of other systems / signals / sensors.

[0060] Examples of the UE 104 include cellular phones, smart phones, Session Initiation Protocol (SIP) phones, laptop computers, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet computers, smart devices, wearable devices, vehicles, electricity meters, air pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other device with similar functions. Some of the UEs in the UE 104 may be referred to as IoT devices (e.g., parking meters, air pumps, toasters, vehicles, heart monitors, etc.). The UE 104 may also be referred to as a station, mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, cell phone, user agent, mobile client, client, or some other suitable term. In some scenarios, the term UE may also apply to one or more companion devices, such as in a device constellation. One or more of these devices may access the network jointly and / or access the network individually.

[0061] Referring again to Figure 1 , in some aspects, the UE 104 may include an SIB component 198, which may be configured to receive an indication of a first assignment of a first PDSCH from a network entity via the PBCH. The first PDSCH may include at least a first portion of the SIB. The SIB component 198 may be configured to receive the first portion of the SIB from the network entity via the first PDSCH based on the first assignment of the first PDSCH. In some aspects, the base station 102 may include an SIB component 199, which may be configured to send an indication of a first assignment of a first PDSCH for the UE via the PBCH. The first PDSCH may include at least a first portion of the SIB. The SIB component 199 may be configured to send the first portion of the SIB for the UE via the first PDSCH based on the first assignment of the first PDSCH.

[0062] In some aspects, the UE 104 may include a SIB component 198 that may be configured to receive a first portion of the SIB from a network entity. The first portion of the SIB may include access control information for the network entity and may indicate an assignment of a second PDSCH in the case where the access control information indicates that the UE is granted access to the network entity. The SIB component 198 may be configured to identify whether the UE is granted access to the network entity based on the access control information for the network entity. In some aspects, the base station 102 may include a SIB component 199 that may be configured to transmit the first portion of the SIB for the UE. The first portion of the SIB may include access control information for the network entity. Based on the access control information for the network entity, the UE may or may not be granted access to the network entity. The SIB component 199 may be configured to transmit a second portion of the SIB for the UE via the second PDSCH based on a second assignment of the second PDSCH in the case where the UE is granted access to the network entity. In the case where the UE is granted access to the network entity, the second assignment of the second PDSCH may be based on the first portion of the SIB. Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar domains, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0063] Figure 2A FIG. 200 is a diagram illustrating an example of a first subframe within a 5G NR frame structure. Figure 2B FIG. 230 is a diagram illustrating an example of a DL channel within a 5G NR subframe. Figure 2C FIG. 250 is a diagram illustrating an example of a second subframe within a 5G NR frame structure. Figure 2D FIG. 280 is a diagram illustrating an example of a UL channel within a 5G NR subframe. The 5G NR frame structure may be frequency division duplex (FDD) (wherein for a particular set of subcarriers (carrier system bandwidth), the subframes within the set of subcarriers are dedicated to either DL or UL), or may be time division duplex (TDD) (wherein for a particular set of subcarriers (carrier system bandwidth), the subframes within the set of subcarriers are dedicated to both DL and UL). In Figure 2A 、 Figure 2CIn the provided example, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (where most are DL), where D is DL, U is UL, and F is flexibly usable between DL / UL, and subframe 3 is configured with slot format 1 (where all are UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28 respectively, any particular subframe can be configured with any of the various available slot formats 0 - 61. Slot formats 0 and 1 are all - DL and all - UL respectively. The other slot formats 2 - 61 include a mixture of DL, UL, and flexible symbols. The UE is configured with the slot format by the received slot format indicator (SFI) (configured dynamically via downlink control information (DCI) or semi - statically / statically via radio resource control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.

[0064] Figures 2A to 2D The frame structure is illustrated, and aspects of the present disclosure can be applied to other wireless communication technologies that may have different frame structures and / or different channels. One frame (10 ms) can be divided into 10 equal - sized subframes (1 ms). Each subframe can include one or more slots. A subframe can also include mini - slots, which can include 7, 4, or 2 symbols. Each slot can include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For normal CP, each slot can include 14 symbols, and for extended CP, each slot can include 12 symbols. The symbols on the DL can be cyclic - prefix orthogonal frequency - division multiplexing (CP - OFDM) symbols. The symbols on the UL can be CP - OFDM symbols (for high - throughput scenarios) or discrete Fourier transform (DFT) - spread OFDM (DFT - s - OFDM) symbols (for power - limited scenarios; limited to single - stream transmission). The number of slots within a subframe is based on the CP and the parameter set. The parameter set defines the sub - carrier spacing (SCS) (see Table 1). The symbol length / duration can be scaled with 1 / SCS.

[0065]

[0066] Table 1: Parameter Sets, SCS, and CP

[0067] For normal CP (14 symbols / slot), the different parameter sets μ0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe respectively. For extended CP, parameter set 2 allows 4 slots per subframe. Thus, for normal CP and parameter set μ, there are 14 symbols / slot and 2 μ slots / subframe. The sub - carrier spacing can be equal to 2 μ*15 kHz, where μ is a parameter set from 0 to 4. Thus, the subcarrier spacing for parameter set μ = 0 is 15 kHz, and the subcarrier spacing for parameter set μ = 4 is 240 kHz. The symbol length / duration is negatively correlated with the subcarrier spacing. Figures 2A to 2D An example for parameter set μ = 2 with normal CP having 14 symbols per time slot and 4 time slots per subframe is provided. The time slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within a frame set, there may be one or more different bandwidth parts (BWPs) that are frequency division multiplexed (see Figure 2B ). Each BWP may have a specific parameter set and CP (normal or extended).

[0068] A resource grid can be used to represent the frame structure. Each time slot includes a resource block (RB) (also referred to as a physical RB (PRB)) that extends over 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0069] As Figure 2A illustrated, some of the REs carry reference (pilot) signals (RSs) for the UE. The RSs can include demodulation RSs (DM-RSs) (indicated as R for a particular configuration, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RSs) for channel estimation at the UE. The RSs can also include beam measurement RSs (BRSs), beam refinement RSs (BRRSs), and phase tracking RSs (PT-RSs).

[0070] Figure 2BExamples of various DL channels within a subframe of a frame are illustrated. The Physical Downlink Control Channel (PDCCH) carries DCI within one or more Control Channel Elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), where each CCE includes six Resource Element Groups (REGs), and each REG includes 12 consecutive Resource Elements (REs) in the OFDM symbols of a Resource Block (RB). The PDCCH within a Bandwidth Part (BWP) can be referred to as a Control Resource Set (CORESET). The UE is configured to monitor PDCCH candidates in the PDCCH search space (e.g., Common Search Space (CSS), UE-specific Search Space (USS)) during the PDCCH monitoring occasion on the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs can be located at higher and / or lower frequencies on the channel bandwidth. The Primary Synchronization Signal (PSS) can be in symbol 2 of a specific subframe of the frame. The PSS is used by the UE 104 to determine subframe / symbol timing and the physical layer identity. The Secondary Synchronization Signal (SSS) can be in symbol 4 of a specific subframe of the frame. The SSS is used by the UE to determine the physical layer cell identity group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine the Physical Cell Identifier (PCI). Based on the PCI, the UE can determine the location of the Demodulation Reference Signal (DM-RS). The Physical Broadcast Channel (PBCH) carrying the Master Information Block (MIB) can be logically grouped with the PSS and SSS to form a Synchronization Signal (SS) / PBCH block (also referred to as an SS block (SSB)). The MIB provides the System Frame Number (SFN) and the number of RBs in the system bandwidth. The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information not transmitted via the PBCH (such as System Information Blocks (SIBs)), and paging messages.

[0071] As Figure 2C illustrated, some of the REs carry DM-RS (indicated as R for a specific configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE can transmit DM-RS for the Physical Uplink Control Channel (PUCCH) and the Physical Uplink Shared Channel (PUSCH). The PUSCH DM-RS can be transmitted in the previous one or two symbols of the PUSCH. Depending on whether a short PUCCH or a long PUCCH is transmitted and depending on the specific PUCCH format used, the PUCCH DM-RS can be transmitted in different configurations. The UE can transmit a Sounding Reference Signal (SRS). The SRS can be transmitted in the last symbol of the subframe. The SRS can have a comb structure, and the UE can transmit the SRS on one of the teeth of the comb. The SRS can be used by the base station for channel quality estimation to enable frequency-dependent scheduling of the UL.

[0072] Figure 2DIllustrates an example of various UL channels within a subframe of a frame. The PUCCH may be located at the position indicated in one configuration. The PUCCH carries uplink control information (UCI), such as a scheduling request, a channel quality indicator (CQI), a precoding matrix indicator (PMI), a rank indicator (RI), and a hybrid automatic repeat request (HARQ) acknowledgement (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUSCH carries data and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0073] Figure 3 Is a block diagram of a base station 310 in an access network communicating with a UE 350. In the DL, Internet Protocol (IP) packets may be provided to a controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a media access control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with the broadcast of system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), radio access technology (RAT) - to - RAT mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with the transfer of upper layer packet data units (PDUs), error correction via ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), re - segmentation of RLC data PDUs, and re - ordering of RLC data PDUs; and MAC layer functionality associated with the mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel prioritization.

[0074] The transmit (TX) processor 316 and the receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1, which includes the physical (PHY) layer, may include error detection on the transport channel, forward error correction (FEC) encoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 handles the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase phase shift keying (M-PSK), M-order quadrature amplitude modulation (M-QAM)). The encoded and modulated symbols may then be split into parallel streams. Subsequently, each stream may be mapped to OFDM subcarriers, multiplexed with reference signals (e.g., pilots) in the time domain and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to generate a physical channel carrying a stream of time-domain OFDM symbols. The OFDM stream is precoded in space to generate multiple spatial streams. Channel estimates from the channel estimator 374 may be used to determine the encoding and modulation schemes, as well as for spatial processing. The channel estimates may be derived from reference signals transmitted by the UE 350 and / or channel state feedback. Then, each spatial stream may be provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx may modulate a radio frequency (RF) carrier using the corresponding spatial stream for transmission.

[0075] At the UE 350, each receiver 354Rx receives signals via its corresponding antenna 352. Each receiver 354Rx recovers the information modulated onto the RF carrier and provides the information to the receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 may perform spatial processing on the information to recover any spatial streams destined for the UE 350. If multiple spatial streams are destined for the UE 350, they may be combined by the RX processor 356 into a single OFDM symbol stream. The RX processor 356 then uses a fast Fourier transform (FFT) to convert the OFDM symbol stream from the time domain to the frequency domain. The frequency-domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, as well as the reference signals, are recovered and demodulated by determining the most likely signal constellation points transmitted by the base station 310. These soft decisions may be based on the channel estimates computed by the channel estimator 358. Then, the soft decisions are decoded and deinterleaved to recover the data and control signals originally transmitted by the base station 310 on the physical channel. The data and control signals are then provided to the controller / processor 359, which implements layer 3 and layer 2 functionality.

[0076] The controller / processor 359 may be associated with a memory 360 that stores program code and data. The memory 360 may be referred to as a computer-readable medium. In the UL, the controller / processor 359 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets. The controller / processor 359 is also responsible for error detection using the ACK and / or NACK protocols to support HARQ operations.

[0077] Similar to the functionality described in connection with DL transmission performed by the base station 310, the controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with the transfer of upper layer PDUs, error correction via ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with the mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel prioritization.

[0078] Channel estimates derived by the channel estimator 358 based on reference signals or feedback transmitted by the base station 310 may be used by the TX processor 368 to select appropriate decoding and modulation schemes and facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via a separate transmitter 354Tx. Each transmitter 354Tx modulates an RF carrier with the corresponding spatial stream for transmission.

[0079] UL transmission is processed at the base station 310 in a manner similar to that described in connection with the receiver functionality at the UE 350. Each receiver 318Rx receives signals via its corresponding antenna 320. Each receiver 318Rx recovers the information modulated onto the RF carrier and provides the information to the RX processor 370.

[0080] The controller / processor 375 may be associated with a memory 376 that stores program code and data. The memory 376 may be referred to as a computer-readable medium. In the UL, the controller / processor 375 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover IP packets. The controller / processor 375 is also responsible for error detection using the ACK and / or NACK protocols to support HARQ operations.

[0081] At least one of TX processor 368, RX processor 356, and controller / processor 359 may be configured to perform aspects associated with Figure 1 SIB component 198 of

[0082] At least one of TX processor 316, RX processor 370, and controller / processor 375 may be configured to perform aspects associated with Figure 1 SIB component 199 of

[0083] In some aspects, SI may include a MIB and multiple SIBs. SI may be partitioned into MSI and other SI (OSI). MSI may include basic information for initial access and information for obtaining any OSI. In one configuration, MSI may include the MIB and SIB1. Specifically, the MIB may contain network entity barred status information and basic physical layer information of the network entity for receiving additional SI, such as CORESET#0 configuration. In some configurations, the MIB may be broadcast periodically on the broadcast channel (BCH). Additionally, SIB1 may define the scheduling of OSI blocks and may contain information for initial access. SIB1 may also be referred to as remaining MSI (RMSI) and may be broadcast periodically on the DL shared channel (DL-SCH) or transmitted to a UE in the RRC_CONNECTED state in a dedicated manner on the DL-SCH. Additionally, OSI may cover all SIBs not broadcast in MSI (e.g., SIB2 and above).

[0084] As new UE features or types are introduced, the payload size of SIB1 may keep increasing and may soon reach the capacity limit of SIB1. In some configurations, to obtain SIB1, a UE may monitor a Type0-CSS set and may perform blind decoding on the scheduling PDCCH of SIB1 (e.g., CORESET#0). To enable the UE to identify whether the UE is authorized to access the network entity, the UE may decode a large TB (e.g., more than 300 bytes), even though the access / barring control information may occupy much less space.

[0085] Figure 4FIG. 400 is a diagram illustrating various example MSI structures. As shown, FIGS. 420, 430, 440 may each illustrate an example time-frequency resource reuse pattern associated with a channel or block used to obtain MSI. Generally, a UE may perform blind decoding of CORESET #0 404 based on an indication in the MIB received with SSB 402 (which may be received via PBCH). CORESET #0 404 may include a DL assignment of a PDSCH that may carry SIB1 406. As shown in FIG. 420, SIB1 406 may include an indication of another PDCCH 408, where PDCCH 408 may include a DL assignment of another PDSCH that may carry SIB2 410. Thus, to obtain SIB1 406, the UE may first perform blind decoding of CORESET #0 404.

[0086] A scalable network (e.g., based on future technologies such as 6G) may ensure the coexistence of UEs of different UE types and UEs belonging to different access categories or access identities. The framework of unified access control (UAC) may be reused or extended to achieve UE coexistence. The prohibited control information associated with different access categories and / or access identities may be broadcast by the RAN.

[0087] It may be desirable to improve the efficiency of MSI delivery or decoding. Specifically, based on an improved method according to one or more aspects, a UE may be able to identify whether the UE can camp on a network entity (e.g., whether the UE is authorized) without decoding a large SIB1. Additionally, the UE may be able to decode SI without performing blind decoding of the PDCCH or with less blind decoding of the PDCCH.

[0088] In some configurations, the network may be backward compatible. Specifically, the access control information for legacy and new UE types may be indicated (e.g., explicitly) in a lightweight SIB.

[0089] One or more aspects may relate to an improved structure of MSI that may be carried in the PBCH and SIB. Thus, the efficiency of SI scheduling may be improved (e.g., the overhead of always-on MSI may be reduced and energy may be saved since the network energy consumption associated with SI broadcast may be reduced). Additionally, the complexity associated with MSI acquisition at the UE may be reduced.

[0090] Figure 5FIG. 500 illustrates an MSI structure according to one or more aspects. As shown, an enhanced PBCH (ePBCH) 502 may indicate a DL assignment 510 for SIB1-a 504 (e.g., the first part of SIB1). SIB1-a 504 may indicate a DL assignment 512 for SIB1-b 506 (e.g., the second part of SIB1). The ePBCH 502, SIB1-a 504, and SIB1-b 506 may be described in further detail below. In addition, SIB1-b 506 may carry a DL assignment and / or additional scheduling information 514 for the OSI 508.

[0091] In one or more configurations, the ePBCH may carry the master system information (e.g., MIB) of the serving network entity. In some configurations, the ePBCH may have a small payload size (e.g., 24 bits, 32 bits, 36 bits, 40 bits, 48 bits, etc.). In one configuration, the ePBCH payload size may be constant. In another configuration, the ePBCH payload size may be configurable (e.g., within a specified / limited range).

[0092] Figure 6 FIG. 600 illustrates various fields in an example ePBCH according to one or more aspects. As shown, the example ePBCH 600 may include a plurality of fields for indicating various system information. For example, a first field 602 having a size of L1 bits may be used to indicate timing (e.g., SFN). A second field 604 having a size of L2 bits may be used to indicate a DL assignment for SIB1-a (e.g., the "pdsch-ConfigSIB1a" field). In addition, a third field 606 having a size of L3 bits may be used to indicate whether inter / intra-frequency reselection is allowed / permitted. In addition, a fourth field 608 having a size of L4 bits may be used to indicate additional SI or may include spare bits.

[0093] In one configuration, the indication of the DL assignment for SIB1-a may include an index of a selected entry in a preconfigured lookup table, where each entry in the lookup table may correspond to a potential DL assignment for SIB1-a. The DL assignment for SIB1-a may correspond to the PDSCH. In one or more configurations, the DL assignment for SIB1-a may include, for example, one or more of the following: time-frequency resource allocation, spatial relation indication, waveform indication, modulation and coding scheme (MCS) indication, payload size indication (e.g., actual transport block size (TBS), scaling factor, aggregation factor, etc.), additional information for coverage enhancement of the SIB, etc. In one configuration, a plurality of lookup tables may be preconfigured, and the indication of the DL assignment for SIB1-a may further include an index of the selected lookup table among the plurality of lookup tables.

[0094] In some configurations, the transmission of SIB1-a can be configured with a low MCS and / or a low peak-to-average power ratio (PAPR) waveform.

[0095] In one configuration, to obtain SIB1-a, the UE may not blindly decode any PDCCH first.

[0096] In some configurations, the message type of the ePBCH can be indicated (explicitly or implicitly) based on one of the following: DM-RS resource configuration, cyclic redundancy check (CRC) attachment scheme, radio resource mapping, or the payload structure of the ePBCH. For example, the message type of the ePBCH can indicate that the ePBCH may not carry a DL assignment for SIB1-a (e.g., non-cell definition enhanced SSB (NCD-eSSB)). In another example, the message type of the ePBCH can indicate that the DL assignment for SIB1-a may depend on one or more of the following: UE capabilities, the duplex mode of the network (e.g., sub-band full duplex (SBFD)), or the network topology (e.g., intelligent repeater, reconfigurable intelligent surface (RIS), etc.).

[0097] As described above, in some configurations, to obtain SIB1-a, since the DL assignment for SIB1-a can be provided in the ePBCH, the UE may not blindly decode the PDCCH first.

[0098] In some configurations, SIB1-a can be a lightweight (e.g., small payload size) SIB that includes the basic SI for the unified access control of the UE. In some configurations, SIB1-a can indicate a DL assignment for SIB1-b (e.g., the second part of SIB1).

[0099] In some configurations, the payload size of SIB1-a can be configurable (e.g., within a specified / limited range).

[0100] Figure 7FIG. is an illustration showing various fields of an exemplary SIB1-a 700 according to one or more aspects. As shown, the exemplary SIB1-a 700 may include a first field 702 (i.e., the "Information Element (IE) #1" field), which may be used to indicate access / barring control information for one or more access categories (the access categories may be related to conditions associated with the UE and types of access attempts). The exemplary SIB1-a 700 may include a second field 704 (i.e., the "IE #2" field), which may be used to indicate access / barring control information for one or more access identifiers (the access identifiers may be related to UE configurations for, e.g., Multimedia Priority Service (MPS), mission-critical services, disaster conditions, or access categories). Additionally, the exemplary SIB1-a 700 may include a third field 706 (i.e., the "IE #3" field), which may be used to indicate access / barring control information for one or more UE types.

[0101] In one configuration, the exemplary SIB1-a 700 may include a fourth field 708 (i.e., the "IE #4" field), which may be used to indicate the DL assignment for SIB1-b. Specifically, in one configuration, the indication of the DL assignment for SIB1-b may include an index of a selected entry in a pre-configured lookup table, where each entry in the lookup table may correspond to a potential DL assignment for SIB1-b. The DL assignment for SIB1-b may correspond to the PDSCH. In one or more configurations, the DL assignment for SIB1-b may include, for example, one or more of the following: time-frequency resource allocation, spatial relation indication, waveform indication, MCS indication, payload size indication (e.g., actual TBS, scaling factor, aggregation factor, etc.), additional information for coverage enhancement of the SIB, etc. In one configuration, multiple lookup tables may be pre-configured, and the indication of the DL assignment for SIB1-b may also include an index of the selected lookup table among the multiple lookup tables.

[0102] In one configuration, one or more lookup tables associated with the DL assignment for SIB1-a and one or more lookup tables associated with the DL assignment for SIB1-b may be the same one or more lookup tables. In another configuration, one or more lookup tables associated with the DL assignment for SIB1-a and one or more lookup tables associated with the DL assignment for SIB1-b may be different lookup tables.

[0103] In one configuration, if the UE is not barred from a network entity (e.g., based on the access / barring control information in SIB1-a), the UE may continue with SIB1-b decoding.

[0104] In one configuration, if the UE is prohibited from accessing a network entity (e.g., based on the access / barring control information in SIB1-a), the UE may abort the decoding of SIB1-b. In one configuration, after or concurrently with aborting the decoding of SIB1-b, the UE may continue with the network entity selection / reselection operation based on the indication in the ePBCH.

[0105] In some configurations, in order to obtain SIB1-b, since the DL assignment for SIB1-b is provided in SIB1-a, the UE may not perform blind decoding of the PDCCH.

[0106] In order for the UE to be allowed to access a network entity (e.g., as indicated in SIB1-a), in one configuration, the random access resource allocation (e.g., PRACH preamble, CSS set for random access, PUCCH resource set for HARQ-ACK to contention resolution message) may be indicated and broadcast in SIB1-b. In another configuration, the UE that is allowed to access the network entity may request the random access resource allocation from the network entity (e.g., based on a beacon as indicated in SIB1-b, where the beacon may be a signal dedicated to the on-demand random access resource allocation procedure). The process of requesting and granting the random access resource allocation may be referred to as the on-demand allocation of random access resources.

[0107] Therefore, in one configuration, if a UE of a specific UE type or access identifier is allowed to access a network entity (e.g., as indicated in SIB1-a) but is not provided with the resource allocation for initial access, the UE may send a beacon to the network entity to request the on-demand allocation of random access resources. The beacon may be associated with an identifier (ID).

[0108] In one configuration, the beacon may reuse the waveform of the PRACH preamble. In another configuration, the beacon may be configured with a waveform / bandwidth / radio resource different from that of the PRACH preamble.

[0110] In one or more configurations, after the UE uses the beacon to send a request for on-demand random access resource allocation, the network entity (e.g., the network) may respond to the UE (e.g., within a time window). In one configuration, the response from the network entity may include the ID of the beacon (e.g., as indicated in the beacon sent by the UE) and an indication of the random access resources allocated to the UE. In one configuration, the response from the network entity may not include the timing advance (TA) information or the contention resolution information. In other words, the response from the network entity may be different from the random access response in the 2-step or 4-step random access channel (RACH) procedure.

[0111] In one or more configurations, the on-demand allocation of random access resources can be network entity-specific or beam-specific. In additional configurations, the on-demand allocation of random access resources can be adapted to (based on) system load (e.g., across different beams), the coverage area of network entities, random access priority, UE type, access category, and / or access identifier. In other words, the on-demand allocation of random access resources can be associated with one or more of the following: network entity, beam, system load, random access priority, UE type, access category, or access identifier.

[0112] Figure 8 FIG. 800 is a diagram of a communication flow of a method of wireless communication. UE 802 can implement aspects of UE 104 / 350. Additionally, network entity 804 can implement aspects of base station 102 / 310. At 806, network entity 804 can send an indication of a first assignment of a first PDSCH for UE 802 via a PBCH (e.g., ePBCH). The first PDSCH can include at least a first part of the SIB (e.g., SIB1-a).

[0113] In one configuration, network entity 804 can provide an indication of the message type of the PBCH to UE 802.

[0114] In one configuration, the indication of the first assignment of the first PDSCH can be associated with a first look-up table. The indication of the first assignment of the first PDSCH can include an index of an entry in the first look-up table for the first assignment.

[0115] In one configuration, the first assignment of the first PDSCH can correspond to one or more of the following: time-frequency resource allocation, spatial relation, waveform, MCS, time slot aggregation factor, TBS scaling factor, number of repetitions, DM-RS binding scheme, TBS, or information for coverage enhancement of the SIB.

[0116] At 808, network entity 804 can send the first part of the SIB for UE 802 via the first PDSCH based on the first assignment of the first PDSCH. The first part of the SIB can include access control information for network entity 804.

[0117] In one or more configurations, the access control information for network entity 804 can include access / barring control information for one or more access categories, one or more access identifiers, and / or one or more UE types.

[0118] At 810, UE 802 can identify whether UE 802 is permitted to access network entity 804 based on the access control information for network entity 804.

[0119] In one configuration, at 812, in the case where the UE 802 is not permitted to access the network entity 804, the UE 802 may perform network entity selection or reselection operations.

[0120] In another configuration, at 814, in the case where the UE 802 is permitted to access the network entity 804, the UE 802 may identify a second assignment of a second PDSCH based at least on a received first portion of the SIB. The second PDSCH may include a second portion of the SIB (e.g., SIB1-b).

[0121] In one configuration, the second assignment of the second PDSCH may correspond to one or more of the following: time-frequency resource allocation, spatial relation, waveform, MCS, slot aggregation factor, TBS scaling factor, number of repetitions, DM-RS binding scheme, TBS, or information for coverage enhancement of the SIB.

[0122] In one configuration, the first portion of the SIB may include an indication of the second assignment of the second PDSCH. The indication of the second assignment may be associated with a second lookup table. The indication of the second assignment may include an index of an entry in the second lookup table for the second assignment.

[0123] At 816, in the case where the UE 802 is permitted to access the network entity 804, the network entity 804 may send the second portion of the SIB for the UE 802 via the second PDSCH based on the second assignment of the second PDSCH.

[0124] In one configuration, the second portion of the SIB may include at least an indication of random access resource allocation for the network entity 804 and for the UE 802 or an indication of an assignment for subsequent SIB transmission from the network entity 804.

[0125] At 818, the UE 802 may identify random access resource allocation for the network entity 804 based at least on the received second portion of the SIB.

[0127] In one configuration, the second portion of the SIB may include information associated with on-demand random access resource allocation. At 818a, the UE 802 may send a request for random access resource allocation for the network entity 804 based on a beacon and the information associated with on-demand random access resource allocation.

[0128] At 818b, the network entity 804 may send a response indicating random access resource allocation for the network entity 804 and for the UE 802 based on the received request for random access resource allocation for the UE 802.

[0129] In one configuration, on-demand allocation of random access resources may be associated with one or more of the following: network entity, beam, system load, random access priority, UE type, access category, or access identifier.

[0130] Figure 9 is a flowchart 900 of a method for wireless communication. The method may be performed by a UE (e.g., UE 104 / 350 / 802; device 1704). At 902, the UE may receive an indication of a first assignment of a first PDSCH from a network entity via the PBCH. The first PDSCH may include at least a first portion of the SIB. For example, 902 may be performed by Figure 17 component 198 in. Refer to Figure 8 , at 806, UE 802 may receive an indication of a first assignment of a first PDSCH from network entity 804 via the PBCH.

[0131] At 904, the UE may receive the first portion of the SIB from the network entity via the first PDSCH based on the first assignment of the first PDSCH. For example, 904 may be performed by Figure 17 component 198 in. Refer to Figure 8 , at 808, UE 802 may receive the first portion of the SIB from network entity 804 via the first PDSCH based on the first assignment of the first PDSCH.

[0132] Figure 10 is a flowchart 1000 of a method for wireless communication. The method may be performed by a UE (e.g., UE 104 / 350 / 802; device 1704). At 1002, the UE may receive an indication of a first assignment of a first PDSCH from a network entity via the PBCH. The first PDSCH may include at least a first portion of the SIB. For example, 1002 may be performed by Figure 17 component 198 in. Refer to Figure 8 , at 806, UE 802 may receive an indication of a first assignment of a first PDSCH from network entity 804 via the PBCH.

[0133] At 1004, the UE may receive the first portion of the SIB from the network entity via the first PDSCH based on the first assignment of the first PDSCH. For example, 1004 may be performed by Figure 17 component 198 in. Refer to Figure 8 , at 808, UE 802 may receive the first portion of the SIB from network entity 804 via the first PDSCH based on the first assignment of the first PDSCH.

[0134] In one configuration, refer to Figure 8, at 806, an indication of a first assignment of a first PDSCH may be associated with a first lookup table. At 806, the indication of the first assignment of the first PDSCH may include an index of an entry in the first lookup table for the first assignment.

[0135] In one configuration, the first assignment of the first PDSCH may correspond to one or more of the following: time-frequency resource allocation, spatial relation, waveform, MCS, slot aggregation factor, TBS scaling factor, number of repetitions, DM-RS binding scheme, TBS, or information for coverage enhancement of SIB.

[0136] In one configuration, referring Figure 8 , a first part of the SIB may include access control information for the network entity 804. At 1006, the UE may identify whether the UE is permitted to access the network entity based on the access control information for the network entity. For example, 1006 may be performed by Figure 17 component 198 in. Referring Figure 8 , at 810, the UE 802 may identify whether the UE 802 is permitted to access the network entity 804 based on the access control information for the network entity 804.

[0137] In one configuration, at 1008, in a case where the UE is not permitted to access the network entity, the UE may perform a network entity selection or reselection operation. For example, 1008 may be performed by Figure 17 component 198 in. Referring Figure 8 , at 812, in a case where the UE802 is not permitted to access the network entity 804, the UE 802 may perform a network entity selection or reselection operation.

[0138] In one configuration, at 1010, in a case where the UE is permitted to access the network entity, the UE may identify a second assignment of a second PDSCH based at least on the received first part of the SIB. The second PDSCH may include a second part of the SIB. For example, 1010 may be performed by Figure 17 component 198 in. Referring Figure 8 , at 814, in a case where the UE 802 is permitted to access the network entity 804, the UE 802 may identify a second assignment of a second PDSCH based at least on the received first part of the SIB.

[0139] At 1012, the UE may receive the second part of the SIB from the network entity via the second PDSCH. For example, 1012 may be performed by Figure 17 component 198 in. Referring Figure 8 , at 816, the UE 802 may receive the second part of the SIB from the network entity 804 via the second PDSCH.

[0140] At 1014, the UE can identify the random access resource allocation for the network entity based at least on the received second part of the SIB. For example, 1014 can be performed by Figure 17 component 198 in Figure 8 . Referring to

[0141] In one configuration, referring to Figure 8 , at 816, the second part of the SIB can include at least an indication of the random access resource allocation for the network entity 804 and for the UE 802 and / or an indication of an assignment for a subsequent SIB transmission from the network entity 804.

[0142] In one configuration, referring to Figure 8 , at 816, the second part of the SIB can include information associated with on-demand random access resource allocation. To identify the random access resource allocation for the network entity, at 1014a, the UE can send a request for the random access resource allocation for the network entity based on the beacon and the information associated with on-demand random access resource allocation. For example, 1014a can be performed by Figure 17 component 198 in Figure 8 . Referring to

[0143] At 1014b, the UE can receive, from the network entity, a response indicating the random access resource allocation for the network entity and for the UE based on the sent request for the random access resource allocation. For example, 1014b can be performed by Figure 17 component 198 in Figure 8 . Referring to

[0144] In one configuration, referring to Figure 8, at 808, the first part of the SIB may include an indication of a second assignment of a second PDSCH. The indication of the second assignment may be associated with a second look-up table. The indication of the second assignment may include an index of an entry in the second look-up table for the second assignment. In one configuration, the second assignment of the second PDSCH may correspond to one or more of the following: time-frequency resource allocation, spatial relation, waveform, MCS, time slot aggregation factor, TBS scaling factor, number of repetitions, DM-RS binding scheme, TBS, or information for coverage enhancement of the SIB.

[0145] Figure 11 is a flowchart 1100 of a method for wireless communication. The method may be performed by a UE (e.g., UE 104 / 350 / 802; apparatus 1704). At 1102, the UE may receive a first part of an SIB from a network entity. The first part of the SIB may include access control information for the network entity and may indicate an assignment of a second PDSCH in the case where the access control information indicates that the UE is permitted to access the network entity. For example, 1102 may be performed by Figure 17 component 198 in. Refer to Figure 8 , at 808, UE 802 may receive a first part of an SIB from network entity 804.

[0146] At 1104, the UE may identify whether the UE is permitted to access the network entity based on the access control information for the network entity. For example, 1104 may be performed by Figure 17 component 198 in. Refer to Figure 8 , at 810, UE 802 may identify whether UE 802 is permitted to access network entity 804 based on the access control information for network entity 804.

[0147] Figure 12 is a flowchart 1200 of a method for wireless communication. The method may be performed by a UE (e.g., UE 104 / 350 / 802; apparatus 1704). At 1202, the UE may receive a first part of an SIB from a network entity. The first part of the SIB may include access control information for the network entity and may indicate an assignment of a second PDSCH in the case where the access control information indicates that the UE is permitted to access the network entity. For example, 1202 may be performed by Figure 17 component 198 in. Refer to Figure 8 , at 808, UE 802 may receive a first part of an SIB from network entity 804.

[0148] At 1204, the UE may identify whether the UE is permitted to access the network entity based on the access control information for the network entity. For example, 1204 may be performed by Figure 17 component 198 in. Refer toFigure 8 At 810, the UE 802 may identify whether the UE 802 is permitted to access the network entity 804 based on the access control information for the network entity 804.

[0149] In one configuration, at 1206, in the case where the UE is not permitted to access the network entity, the UE may perform network entity selection or reselection operations. For example, 1206 may be performed by Figure 17 component 198 in Figure 8 . Referring to

[0150] In one configuration, at 1208, in the case where the UE is permitted to access the network entity, the UE may identify a second assignment of a second PDSCH based at least on a first received portion of the SIB. The second PDSCH may include a second portion of the SIB. For example, 1208 may be performed by Figure 17 component 198 in Figure 8 . Referring to

[0151] At 1210, the UE may receive a second portion of the SIB from the network entity via the second PDSCH. For example, 1210 may be performed by Figure 17 component 198 in Figure 8 . Referring to

[0153] At 1212, the UE may identify a random access resource allocation for the network entity based at least on the second received portion of the SIB. For example, 1212 may be performed by Figure 17 component 198 in Figure 8 . Referring to

[0154] In one configuration, referring to Figure 8 at 816, the second portion of the SIB may include at least an indication of a random access resource allocation for the network entity 804 and for the UE 802 and / or an indication of an assignment for a subsequent SIB transmission from the network entity 804.

[0155] In one configuration, referring to Figure 8, at 816, the second part of the SIB may include information associated with on-demand random access resource allocation. To identify the random access resource allocation for a network entity, at 1212a, the UE may send a request for the random access resource allocation for the network entity based on the beacon and the information associated with the on-demand random access resource allocation. For example, 1212a may be performed by Figure 17 Component 198 in. Refer to Figure 8 , at 818a, UE 802 may send a request for the random access resource allocation for the network entity 804 based on the beacon and the information associated with the on-demand random access resource allocation.

[0156] At 1212b, the UE may receive a response indicating the random access resource allocation for the network entity and for the UE based on the sent request for the random access resource allocation. For example, 1212b may be performed by Figure 17 Component 198 in. Refer to Figure 8 , at 818b, UE 802 may receive a response indicating the random access resource allocation for the network entity 804 and for UE 802 based on the sent request for the random access resource allocation.

[0157] In one configuration, refer to Figure 8 , at 808, the first part of the SIB may include an indication of a second assignment of a second PDSCH. The indication of the second assignment may be associated with a second lookup table. The indication of the second assignment may include an index of an entry in the second lookup table for the second assignment. In one configuration, the second assignment of the second PDSCH may correspond to one or more of the following: time-frequency resource allocation, spatial relationship, waveform, MCS, slot aggregation factor, TBS scaling factor, number of repetitions, DM-RS binding scheme, TBS, or information for coverage enhancement of the SIB.

[0158] Figure 13 Is a flowchart 1300 of a method of wireless communication. The method may be performed by a network entity (e.g., base station 102 / 310; network entity 804 / 1702 / 1802). At 1302, the network entity may send an indication of a first assignment of a first PDSCH for the UE via the PBCH. The first PDSCH may include at least the first part of the SIB. For example, 1302 may be performed by Figure 18 Component 199 in. Refer to Figure 8 , at 806, network entity 804 may send an indication of a first assignment of a first PDSCH for UE 802 via the PBCH.

[0159] At 1304, a network entity may transmit, via a first PDSCH, a first portion of a SIB for a UE based on a first assignment of the first PDSCH. For example, 1304 may be performed by component 199 in Figure 18 . Referring to Figure 8 , at 808, network entity 804 may transmit, via a first PDSCH, a first portion of a SIB for UE 802 based on a first assignment of the first PDSCH.

[0160] Figure 14 FIG. 1400 is a flowchart of a method of wireless communication. The method may be performed by a network entity (e.g., base station 102 / 310; network entity 804 / 1702 / 1802). At 1402, the network entity may transmit, via a PBCH, an indication of a first assignment of a first PDSCH for the UE. The first PDSCH may include at least a first portion of a SIB. For example, 1402 may be performed by component 199 in Figure 18 . Referring to Figure 8 , at 806, network entity 804 may transmit, via a PBCH, an indication of a first assignment of a first PDSCH for UE 802.

[0161] At 1404, the network entity may transmit, via a first PDSCH, a first portion of a SIB for the UE based on a first assignment of the first PDSCH. For example, 1404 may be performed by component 199 in Figure 18 . Referring to Figure 8 , at 808, network entity 804 may transmit, via a first PDSCH, a first portion of a SIB for UE 802 based on a first assignment of the first PDSCH.

[0162] In one configuration, referring to Figure 8 , at 806, an indication of a first assignment of a first PDSCH may be associated with a first look-up table. The indication of the first assignment of the first PDSCH may include an index of an entry in the first look-up table for the first assignment.

[0163] In one configuration, the first assignment of the first PDSCH may correspond to one or more of the following: time-frequency resource allocation, spatial relation, waveform, MCS, slot aggregation factor, TBS scaling factor, number of repetitions, DM-RS binding scheme, TBS, or information for coverage enhancement of the SIB.

[0164] In one configuration, referring to Figure 8 , at 808, the first portion of the SIB may include access control information for network entity 804. Based on the access control information for network entity 804, UE 802 may or may not be granted access to network entity 804.

[0165] In one configuration, at 1406, a network entity may transmit a second part of the SIB for a UE via a second PDSCH based on a second assignment of the second PDSCH when the UE is granted access to the network entity. The second assignment of the second PDSCH may be based on a first part of the SIB. For example, 1406 may be performed by Figure 18 component 199 in. Refer to Figure 8 , at 816, when UE 802 is granted access to network entity 804, network entity 804 may transmit a second part of the SIB for UE 802 via a second PDSCH based on a second assignment of the second PDSCH.

[0166] In one configuration, refer to Figure 8 , at 816, the second part of the SIB may include at least an indication of a random access resource allocation for network entity 804 and for UE 802 and / or an indication of an assignment for a subsequent SIB transmission from network entity 804.

[0167] In one configuration, refer to Figure 8 , at 816, the second part of the SIB may include information associated with on-demand random access resource allocation. At 1408, the network entity may receive a request for random access resource allocation from the UE based on a beacon and the information associated with on-demand random access resource allocation. For example, 1408 may be performed by Figure 18 component 199 in. Refer to Figure 8 , at 818a, network entity 804 may receive a request for random access resource allocation from UE802 based on a beacon and the information associated with on-demand random access resource allocation.

[0168] At 1410, the network entity may transmit a response indicating a random access resource allocation for the network entity and for the UE based on the received request for random access resource allocation. For example, 1410 may be performed by Figure 18 component 199 in. Refer to Figure 8 , at 818b, network entity 804 may transmit a response indicating a random access resource allocation for network entity 804 and for UE 802 based on the received request for random access resource allocation.

[0169] In one configuration, refer to Figure 8, at 808, the first part of the SIB may include an indication of a second assignment of a second PDSCH. The indication of the second assignment may be associated with a second look-up table. The indication of the second assignment may include an index of an entry in the second look-up table for the second assignment. In one configuration, the second assignment of the second PDSCH may correspond to one or more of the following: time-frequency resource allocation, spatial relation, waveform, MCS, slot aggregation factor, TBS scaling factor, number of repetitions, DM-RS bundling scheme, TBS, or information for coverage enhancement of the SIB.

[0170] Figure 15 is a flowchart 1500 of a method of wireless communication. The method may be performed by a network entity (e.g., base station 102 / 310; network entity 804 / 1702 / 1802). At 1502, the network entity may transmit a first part of an SIB for a UE. The first part of the SIB may include access control information for the network entity. Based on the access control information for the network entity, the UE may or may not be granted access to the network entity. For example, 1502 may be performed by Figure 18 component 199 in. Refer to Figure 8 , at 808, network entity 804 may transmit a first part of an SIB for UE 802.

[0171] At 1504, the network entity may transmit a second part of the SIB for the UE via a second PDSCH based on a second assignment of the second PDSCH if the UE is granted access to the network entity. If the UE is granted access to the network entity, the second assignment of the second PDSCH may be based on the first part of the SIB. For example, 1504 may be performed by Figure 18 component 199 in. Refer to Figure 8 , at 816, if UE 802 is granted access to network entity 804, network entity 804 may transmit a second part of the SIB for UE 802 via a second PDSCH based on a second assignment of the second PDSCH.

[0172] Figure 16 is a flowchart 1600 of a method of wireless communication. The method may be performed by a network entity (e.g., base station 102 / 310; network entity 804 / 1702 / 1802). At 1602, the network entity may transmit a first part of an SIB for a UE. The first part of the SIB may include access control information for the network entity. Based on the access control information for the network entity, the UE may or may not be granted access to the network entity. For example, 1602 may be performed by Figure 18 component 199 in. Refer to Figure 8 , at 808, network entity 804 may transmit a first part of an SIB for UE 802.

[0173] At 1604, the network entity may transmit, for the UE, a second part of the SIB via a second PDSCH based on a second assignment of the second PDSCH if the UE is granted access to the network entity. If the UE is granted access to the network entity, the second assignment of the second PDSCH may be based on the first part of the SIB. For example, 1604 may be performed by Figure 18 component 199 in Figure 8 . Referring to

[0174] In one configuration, referring to Figure 8 , at 816, the second part of the SIB may at least include an indication of a random access resource allocation for the network entity 804 and for the UE 802 and / or an indication of an assignment for a subsequent SIB transmission from the network entity 804.

[0175] In one configuration, referring to Figure 8 , at 816, the second part of the SIB may include information associated with on-demand random access resource allocation. At 1606, the network entity may receive, from the UE, a request for random access resource allocation based on a beacon and the information associated with on-demand random access resource allocation. For example, 1606 may be performed by Figure 18 component 199 in Figure 8 . Referring to

[0176] At 1608, the network entity may transmit, for the UE, a response indicating a random access resource allocation for the network entity and for the UE based on the received request for random access resource allocation. For example, 1608 may be performed by Figure 18 component 199 in Figure 8 . Referring to

[0177] In one configuration, referring to Figure 8, at 808, the first part of the SIB may include an indication of a second assignment of a second PDSCH. The indication of the second assignment may be associated with a second look-up table. The indication of the second assignment may include an index of an entry in the second look-up table for the second assignment. In one configuration, the second assignment of the second PDSCH may correspond to one or more of the following: time-frequency resource allocation, spatial relation, waveform, MCS, slot aggregation factor, TBS scaling factor, number of repetitions, DM-RS binding scheme, TBS, or information for coverage enhancement of the SIB.

[0178] Figure 17FIG. 1700 is a diagram illustrating an example of a hardware implementation for apparatus 1704. Apparatus 1704 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, apparatus 1704 may include a cellular baseband processor 1724 (also referred to as a modem) coupled to one or more transceivers 1722 (e.g., cellular RF transceivers). The cellular baseband processor 1724 may include on-chip memory 1724'. In some aspects, apparatus 1704 may also include one or more subscriber identity module (SIM) cards 1720 and an application processor 1706 coupled to a secure digital (SD) card 1708 and a screen 1710. The application processor 1706 may include on-chip memory 1706'. In some aspects, apparatus 1704 may also include a Bluetooth module 1712, a WLAN module 1714, an SPS module 1716 (e.g., a GNSS module), one or more sensor modules 1718 (e.g., an atmospheric pressure sensor / altimeter; motion sensors such as an inertial measurement unit (IMU), a gyroscope, and / or an accelerometer; light detection and ranging (LIDAR), radio assisted detection and ranging (RADAR), sound navigation and ranging (SONAR), a magnetometer, audio, and / or other technologies for positioning), an additional memory module 1726, a power source 1730, and / or a camera 1732. The Bluetooth module 1712, the WLAN module 1714, and the SPS module 1716 may include on-chip transceivers (TRX) (or in some cases, only receivers (RX)). The Bluetooth module 1712, the WLAN module 1714, and the SPS module 1716 may include their own dedicated antennas and / or communicate using antenna 1780. The cellular baseband processor 1724 communicates with UE 104 and / or with the RU associated with network entity 1702 via one or more antennas 1780 through transceiver 1722. The cellular baseband processor 1724 and the application processor 1706 may each separately include computer-readable media / memory 1724', 1706'. The additional memory module 1726 may also be considered computer-readable media / memory. Each computer-readable media / memory 1724', 1706', 1726 may be non-transitory. The cellular baseband processor 1724 and the application processor 1706 are each responsible for general processing, including executing software stored on the computer-readable media / memory. The software, when executed by the cellular baseband processor 1724 / application processor 1706, causes the cellular baseband processor 1724 / application processor 1706 to perform the various functions described above. The computer-readable media / memory may also be used to store data manipulated by the cellular baseband processor 1724 / application processor 1706 when executing the software.The cellular baseband processor 1724 / application processor 1706 can be a component of the UE 350 and can include at least one of the memory 360 and / or the TX processor 368, the RX processor 356, and the controller / processor 359. In one configuration, the device 1704 can be a processor chip (modem and / or application) and include only the cellular baseband processor 1724 and / or the application processor 1706, and in another configuration, the device 1704 can be the entire UE (e.g., see. Figure 3 of 350) and include additional modules of the device 1704.

[0179] As discussed above, component 198 is configured to receive an indication of a first assignment of a first PDSCH from a network entity via the PBCH. The first PDSCH may include at least a first portion of the SIB. Component 198 is configured to receive the first portion of the SIB from the network entity via the first PDSCH based on the first assignment of the first PDSCH. Component 198 is configured to receive the first portion of the SIB from the network entity. The first portion of the SIB may include access control information for the network entity and may indicate an assignment of a second PDSCH in the case where the access control information indicates that the UE is permitted to access the network entity. Component 198 is configured to identify whether the UE is permitted to access the network entity based on the access control information for the network entity. Component 198 may be within the cellular baseband processor 1724, the application processor 1706, or both the cellular baseband processor 1724 and the application processor 1706. Component 198 may be one or more hardware components specifically configured to perform the stated processes / algorithms, implemented by one or more processors configured to perform the stated processes / algorithms, stored in a computer-readable medium for implementation by one or more processors, or some combination of the above. As shown, device 1704 may include various components configured for various functions. In one configuration, device 1704 (and specifically, the cellular baseband processor 1724 and / or the application processor 1706) includes means for receiving an indication of a first assignment of a first PDSCH from a network entity via the PBCH. The first PDSCH may include at least a first portion of the SIB. Device 1704 (and specifically, the cellular baseband processor 1724 and / or the application processor 1706) includes means for receiving the first portion of the SIB from the network entity via the first PDSCH based on the first assignment of the first PDSCH. Device 1704 (and specifically, the cellular baseband processor 1724 and / or the application processor 1706) includes means for receiving the first portion of the SIB from the network entity. The first portion of the SIB may include access control information for the network entity and may indicate an assignment of a second PDSCH in the case where the access control information indicates that the UE is permitted to access the network entity. Device 1704 (and specifically, the cellular baseband processor 1724 and / or the application processor 1706) includes means for identifying whether the UE is permitted to access the network entity based on the access control information for the network entity.

[0180] In one configuration, an indication of a first assignment of a first PDSCH may be associated with a first lookup table. The indication of the first assignment of the first PDSCH may include an index of an entry in the first lookup table for the first assignment. In one configuration, the first assignment of the first PDSCH may correspond to one or more of the following: time-frequency resource allocation, spatial relation, waveform, MCS, slot aggregation factor, TBS scaling factor, number of repetitions, DM-RS binding scheme, TBS, or information for coverage enhancement of SIB. In one configuration, a first part of the SIB may include access control information for a network entity. The apparatus 1704 (and specifically, the cellular baseband processor 1724 and / or the application processor 1706) includes components for identifying whether the UE is permitted to access the network entity based on the access control information for the network entity. In one configuration, the apparatus 1704 (and specifically, the cellular baseband processor 1724 and / or the application processor 1706) includes components for performing network entity selection or reselection operations in case the UE is not permitted to access the network entity. In one configuration, the apparatus 1704 (and specifically, the cellular baseband processor 1724 and / or the application processor 1706) includes components for identifying a second assignment of a second PDSCH based at least on the received first part of the SIB in case the UE is permitted to access the network entity, where the second PDSCH includes a second part of the SIB. The apparatus 1704 (and specifically, the cellular baseband processor 1724 and / or the application processor 1706) includes components for receiving the second part of the SIB from the network entity via the second PDSCH. The apparatus 1704 (and specifically, the cellular baseband processor 1724 and / or the application processor 1706) includes components for identifying a random access resource allocation for the network entity based at least on the received second part of the SIB. In one configuration, the second part of the SIB may include at least an indication of the random access resource allocation for the network entity and for the UE or an indication of an assignment for a subsequent SIB transmission from the network entity. In one configuration, the second part of the SIB may include information associated with on-demand random access resource allocation. The components for identifying the random access resource allocation for the network entity may also be configured to: send a request for the random access resource allocation for the network entity based on a beacon and the information associated with on-demand random access resource allocation; and receive, from the network entity, a response indicating the random access resource allocation for the network entity and for the UE based on the sent request for the random access resource allocation. In one configuration, the first part of the SIB may include an indication of the second assignment of the second PDSCH. The indication of the second assignment may be associated with a second lookup table. The indication of the second assignment may include an index of an entry in the second lookup table for the second assignment.The second assignment of the second PDSCH may correspond to one or more of the following: time-frequency resource allocation, spatial relation, waveform, MCS, slot aggregation factor, TBS scaling factor, number of repetitions, DM-RS bundling scheme, TBS, or information for coverage enhancement for SIB.

[0181] A component can be a component 198 of apparatus 1704 configured to perform the functions recited by the component. As described above, apparatus 1704 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Thus, in one configuration, a component can be the TX processor 368, the RX processor 356, and / or the controller / processor 359 configured to perform the functions recited by the component.

[0182] Figure 18FIG. 1800 is a diagram illustrating an example of a hardware implementation for network entity 1802. Network entity 1802 may be a BS, a component of a BS, or may implement BS functionality. Network entity 1802 may include at least one of CU 1810, DU 1830, or RU 1840. For example, depending on the layer functionality handled by component 199, network entity 1802 may include CU 1810; both CU 1810 and DU 1830; each of CU 1810, DU 1830, and RU 1840; DU 1830; both DU 1830 and RU 1840; or RU 1840. CU 1810 may include CU processor 1812. CU processor 1812 may include on-chip memory 1812'. In some aspects, CU 1810 may also include additional memory module 1814 and communication interface 1818. CU 1810 communicates with DU 1830 via an intermediate link (such as the F1 interface). DU 1830 may include DU processor 1832. DU processor 1832 may include on-chip memory 1832'. In some aspects, DU 1830 may also include additional memory module 1834 and communication interface 1838. DU 1830 communicates with RU 1840 via a fronthaul link. RU 1840 may include RU processor 1842. RU processor 1842 may include on-chip memory 1842'. In some aspects, RU 1840 may also include additional memory module 1844, one or more transceivers 1846, antenna 1880, and communication interface 1848. RU 1840 communicates with UE 104. On-chip memories 1812', 1832', 1842' and additional memory modules 1814, 1834, 1844 may each be considered a computer-readable medium / memory. Each computer-readable medium / memory may be non-transitory. Each of processors 1812, 1832, 1842 is responsible for general processing, including executing software stored on the computer-readable medium / memory. The software, when executed by the corresponding processor, causes the processor to perform the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by the processor when executing the software.

[0183] As discussed above, component 199 is configured to send an indication of a first assignment of a first PDSCH for a UE via PBCH. The first PDSCH may include at least a first part of the SIB. Component 199 is configured to send the first part of the SIB for the UE via the first PDSCH based on the first assignment of the first PDSCH. Component 199 is configured to send the first part of the SIB for the UE. The first part of the SIB may include access control information for a network entity. Based on the access control information for the network entity, the UE may or may not be granted access to the network entity. Component 199 is configured to send a second part of the SIB for the UE via a second PDSCH based on a second assignment of the second PDSCH in the case where the UE is granted access to the network entity. In the case where the UE is granted access to the network entity, the second assignment of the second PDSCH may be based on the first part of the SIB. Component 199 may be within one or more processors of one or more of CU 1810, DU 1830, and RU 1840. Component 199 may be one or more hardware components specifically configured to perform the stated processes / algorithms, implemented by one or more processors configured to perform the stated processes / algorithms, stored in a computer-readable medium for implementation by one or more processors, or some combination of the above. Network entity 1802 may include a variety of components configured for various functions. In one configuration, network entity 1802 includes means for sending an indication of a first assignment of a first PDSCH for a UE via PBCH. The first PDSCH may include at least a first part of the SIB. Network entity 1802 includes means for sending the first part of the SIB for the UE via the first PDSCH based on the first assignment of the first PDSCH. Network entity 1802 includes means for sending the first part of the SIB for the UE. The first part of the SIB may include access control information for a network entity. Based on the access control information for the network entity, the UE may or may not be granted access to the network entity. Network entity 1802 includes means for sending a second part of the SIB for the UE via a second PDSCH based on a second assignment of the second PDSCH in the case where the UE is granted access to the network entity. In the case where the UE is granted access to the network entity, the second assignment of the second PDSCH may be based on the first part of the SIB.

[0184] In one configuration, an indication of a first assignment of a first PDSCH may be associated with a first look-up table. The indication of the first assignment of the first PDSCH may include an index of an entry in the first look-up table for the first assignment. In one configuration, the first assignment of the first PDSCH may correspond to one or more of the following: time-frequency resource allocation, spatial relation, waveform, MCS, slot aggregation factor, TBS scaling factor, number of repetitions, DM-RS binding scheme, TBS, or information for coverage enhancement of SIB. In one configuration, a first portion of the SIB may include access control information for a network entity. Based on the access control information for the network entity, the UE may or may not be granted access to the network entity. In one configuration, network entity 1802 includes components for transmitting, via a second PDSCH, a second portion of the SIB for the UE based on a second assignment of the second PDSCH in the case where the UE is granted access to the network entity. The second assignment of the second PDSCH may be based on the first portion of the SIB. In one configuration, the second portion of the SIB may at least include an indication of random access resource allocation for the network entity and for the UE or an indication of an assignment for subsequent SIB transmission from the network entity. In one configuration, the second portion of the SIB may include information associated with on-demand random access resource allocation. Network entity 1802 includes components for receiving, from the UE, a request for random access resource allocation based on a beacon and the information associated with on-demand random access resource allocation. Network entity 1802 includes components for transmitting, for the UE, a response indicating random access resource allocation for the network entity and for the UE based on the received request for random access resource allocation. In one configuration, the first portion of the SIB may include an indication of the second assignment of the second PDSCH. The indication of the second assignment may be associated with a second look-up table. The indication of the second assignment may include an index of an entry in the second look-up table for the second assignment. The second assignment of the second PDSCH may correspond to one or more of the following: time-frequency resource allocation, spatial relation, waveform, MCS, slot aggregation factor, TBS scaling factor, number of repetitions, DM-RS binding scheme, TBS, or information for coverage enhancement of SIB.

[0185] A component may be a component 199 of network entity 1802 configured to perform the functions recited by the component. As described above, network entity 1802 may include TX processor 316, RX processor 370, and controller / processor 375. Thus, in one configuration, the component may be TX processor 316, RX processor 370, and / or controller / processor 375 configured to perform the functions recited by the component.

[0186] Return reference Figures 4 to 18, the UE can receive an indication of the first assignment of the first PDSCH from a network entity via the PBCH. The first PDSCH can include at least a first part of the SIB. The UE can receive the first part of the SIB from the network entity via the first PDSCH based on the first assignment of the first PDSCH. The first part of the SIB can include access control information for the network entity. The UE can identify whether the UE is permitted to access the network entity based on the access control information for the network entity. Therefore, the UE can identify whether the UE can camp on the network entity (e.g., whether the UE is authorized) without decoding the large SIB1. In addition, the UE can decode the SI without performing blind decoding of the PDCCH or performing less blind decoding of the PDCCH.

[0187] It should be understood that the specific order or hierarchy of the boxes in the disclosed process / flowchart is merely illustrative of an example method. It should be understood that based on design preferences, the specific order or hierarchy of the boxes in the process / flowchart can be rearranged. Further, some boxes can be combined or omitted. The appended method claims present the elements of the various boxes in a sample order, but are not limited to the specific order or hierarchy presented.

[0188] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Thus, the claims are not limited to the aspects described herein, but are to be accorded the full scope consistent with the language of the claims, and the singular forms of elements are not intended to mean "one and only one" but "one or more" unless specifically stated otherwise. Terms such as "if," "when," and "while" do not denote a direct temporal relationship or reaction. That is, these phrases, such as "when...," do not mean an immediate action in response to or during the occurrence of an action, but simply imply that the action will occur if the condition is met, without requiring a specific or immediate time limit for the occurrence of the action. The word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any aspect described herein as "exemplary" is not necessarily to be construed as preferred or having an advantage over other aspects. Unless specifically stated otherwise, the term "some" refers to one or more. Combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B, and C," "one or more of A, B, and C," and "any combination of A, B, C, or any of them," including any combination of A, B, and / or C, may include multiple As, multiple Bs, or multiple Cs. Specifically, combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B, and C," "one or more of A, B, and C," and "any combination of A, B, C, or any of them" can be only A, only B, only C, A and B, A and C, B and C, or A and B and C, where any such combination may contain one or more members of A, B, or C. A set should be construed as a collection of elements, where the number of elements is one or more. Thus, for a set of X, X will include one or more elements. If a first device receives data from or sends data to a second device, the data may be received / sent directly between the first and second devices, or indirectly between the first and second devices through a collection of devices. All structural and functional equivalents of the elements of the aspects described throughout this disclosure that are known or later will be known to those of ordinary skill in the art are expressly incorporated herein by reference and are covered by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public, whether or not such disclosure is expressly recited in the claims. The words "module," "mechanism," "element," "device," etc. do not substitute for the word "component." Thus, no claim element shall be construed as a means-plus-function unless the element is expressly recited using the phrase "means for..."

[0189] As used herein, the phrase "based on" should not be construed to refer to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase "based on A" (where "A" can be information, a condition, a factor, etc.) should be construed as "at least based on A", unless stated otherwise specifically.

[0190] The following aspects are merely illustrative and can be combined with other aspects or teachings described herein without limitation.

[0191] Aspect 1 is a method for wireless communication at a UE, the method comprising: receiving, via a PBCH, an indication of a first assignment of a first PDSCH from a network entity, the first PDSCH including at least a first part of a SIB; and receiving, via the first PDSCH from the network entity, the first part of the SIB based on the first assignment of the first PDSCH.

[0192] Aspect 2 is the method according to aspect 1, wherein the indication of the first assignment of the first PDSCH is associated with a first look-up table, and the indication of the first assignment of the first PDSCH includes an index of an entry in the first look-up table for the first assignment.

[0194] Aspect 3 is the method according to any one of aspects 1 and 2, wherein the first assignment of the first PDSCH corresponds to one or more of the following: time-frequency resource allocation, spatial relation, waveform, MCS, slot aggregation factor, TBS scaling factor, number of repetitions, DM-RS binding scheme, TBS, or information for coverage enhancement of the SIB.

[0195] Aspect 4 is the method according to any one of aspects 1 to 3, wherein the first part of the SIB includes access control information for the network entity, and the method further comprises: identifying whether the UE is permitted to access the network entity based on the access control information for the network entity.

[0196] Aspect 5 is the method according to aspect 4, the method further comprising: performing a network entity selection or reselection operation in the case where the UE is not permitted to access the network entity.

[0197] Aspect 6 is the method according to aspect 4, the method further comprising: identifying a second assignment of a second PDSCH based at least on the received first part of the SIB in the case where the UE is granted access to the network entity, the second PDSCH comprising a second part of the SIB; receiving the second part of the SIB from the network entity via the second PDSCH; and identifying a random access resource allocation for the network entity based at least on the received second part of the SIB.

[0198] Aspect 7 is the method according to aspect 6, wherein the second part of the SIB comprises at least an indication of the random access resource allocation for the network entity and for the UE or an indication of an assignment for a subsequent SIB transmission from the network entity.

[0199] Aspect 8 is the method according to aspect 6, wherein the second part of the SIB comprises information associated with on-demand random access resource allocation, and identifying the random access resource allocation for the network entity further comprises: sending a request for the random access resource allocation for the network entity based on a beacon and the information associated with the on-demand random access resource allocation; and receiving, from the network entity, a response indicating the random access resource allocation for the network entity and for the UE based on the sent request for the random access resource allocation.

[0200] Aspect 9 is the method according to any one of aspects 6 to 8, wherein the first part of the SIB comprises an indication of the second assignment of the second PDSCH, the indication of the second assignment being associated with a second look-up table, the indication of the second assignment comprising an index of an entry in the second look-up table for the second assignment, and the second assignment of the second PDSCH corresponds to one or more of the following: time-frequency resource allocation, spatial relation, waveform, MCS, time slot aggregation factor, TBS scaling factor, number of repetitions, DM-RS binding scheme, TBS, or information for coverage enhancement of the SIB, or any combination thereof.

[0201] Aspect 10 is a method for wireless communication at a UE, the method comprising: receiving a first part of an SIB from a network entity, the first part of the SIB comprising access control information for the network entity and indicating an assignment of a second PDSCH in the case where the access control information indicates that the UE is granted access to the network entity; and identifying whether the UE is granted access to the network entity based on the access control information for the network entity.

[0202] Aspect 11 is the method according to aspect 10, the method further comprising: performing a network entity selection or reselection operation in case the access control information indicates that the UE is not permitted to access the network entity.

[0203] Aspect 12 is the method according to aspect 10, wherein the second PDSCH comprises a second part of the SIB, and the method further comprises: receiving, via the second PDSCH, the second part of the SIB from the network entity; and identifying a random access resource allocation for the network entity based at least on the received second part of the SIB.

[0204] Aspect 13 is the method according to aspect 12, wherein the second part of the SIB comprises at least an indication of the random access resource allocation for the network entity and for the UE or an indication of an assignment for a subsequent SIB transmission from the network entity.

[0205] Aspect 14 is the method according to aspect 12, wherein the second part of the SIB comprises information associated with on-demand random access resource allocation, and identifying the random access resource allocation for the network entity further comprises: sending, for the network entity, a request for the random access resource allocation based on a beacon and the information associated with the on-demand random access resource allocation; and receiving, from the network entity, a response indicating the random access resource allocation for the network entity and for the UE based on the sent request for the random access resource allocation.

[0206] Aspect 15 is the method according to any one of aspects 12 to 14, wherein the indication of the second assignment is associated with a second lookup table and comprises an index of an entry in the second lookup table for the second assignment, and the second assignment of the second PDSCH corresponds to one or more of the following: time-frequency resource allocation, spatial relation, waveform, MCS, time slot aggregation factor, TBS scaling factor, number of repetitions, DM-RS binding scheme, TBS, or information for coverage enhancement of the SIB, or any combination thereof.

[0207] Aspect 16 is a method for wireless communication at a network entity, the method comprising: sending, via a PBCH, an indication of a first assignment of a first PDSCH for a UE, the first PDSCH comprising at least a first part of an SIB; and sending, via the first PDSCH, the first part of the SIB for the UE based on the first assignment of the first PDSCH.

[0208] Aspect 17 is the method according to aspect 16, wherein the indication of the first assignment of the first PDSCH is associated with a first look-up table, and the indication of the first assignment of the first PDSCH includes an index of an entry in the first look-up table for the first assignment.

[0209] Aspect 18 is the method according to any one of aspects 16 and 17, wherein the first assignment of the first PDSCH corresponds to one or more of the following: time-frequency resource allocation, spatial relation, waveform, MCS, time slot aggregation factor, TBS scaling factor, number of repetitions, DM-RS binding scheme, TBS, or information for coverage enhancement of the SIB.

[0210] Aspect 19 is the method according to any one of aspects 16 to 18, wherein the first part of the SIB includes access control information for the network entity, and the UE is permitted or not permitted to access the network entity based on the access control information for the network entity.

[0211] Aspect 20 is the method according to aspect 19, the method further comprising: transmitting, for the UE, a second part of the SIB via a second PDSCH based on a second assignment of the second PDSCH in the case where the UE is permitted to access the network entity, the second assignment of the second PDSCH being based on the first part of the SIB.

[0212] Aspect 21 is the method according to aspect 20, wherein the second part of the SIB includes at least an indication of random access resource allocation for the network entity and for the UE or an indication of an assignment for subsequent SIB transmission from the network entity.

[0213] Aspect 22 is the method according to aspect 20, wherein the second part of the SIB includes information associated with on-demand random access resource allocation, and the method further comprising: receiving, from the UE, a request for random access resource allocation based on a beacon and the information associated with the on-demand random access resource allocation; and transmitting, for the UE, a response indicating the random access resource allocation for the network entity and for the UE based on the received request for the random access resource allocation.

[0214] Aspect 23 is the method according to any one of Aspects 20 to 22, wherein the first part of the SIB includes an indication of the second assignment of the second PDSCH, the indication of the second assignment is associated with a second look-up table, the indication of the second assignment includes an index of an entry in the second look-up table for the second assignment, and the second assignment of the second PDSCH corresponds to one or more of the following: time-frequency resource allocation, spatial relation, waveform, MCS, slot aggregation factor, TBS scaling factor, number of repetitions, DM-RS binding scheme, TBS, or information for coverage enhancement of the SIB, or any combination thereof.

[0215] Aspect 24 is a method for wireless communication at a network entity, the method comprising: transmitting, for a UE, a first part of an SIB, the first part of the SIB including access control information for the network entity, wherein the UE is permitted or not permitted to access the network entity based on the access control information for the network entity; and transmitting, via the second PDSCH, a second part of the SIB for the UE based on a second assignment of the second PDSCH when the UE is permitted to access the network entity, wherein the second assignment of the second PDSCH is based on the first part of the SIB when the UE is permitted to access the network entity.

[0216] Aspect 25 is the method according to Aspect 24, wherein the second part of the SIB at least includes an indication of random access resource allocation for the network entity and for the UE or an indication of an assignment for subsequent SIB transmission from the network entity.

[0217] Aspect 26 is the method according to Aspect 24, wherein the second part of the SIB includes information associated with on-demand random access resource allocation, and the method further comprises: receiving, from the UE, a request for random access resource allocation based on a beacon and the information associated with the on-demand random access resource allocation; and transmitting, for the UE, a response indicating the random access resource allocation for the network entity and for the UE based on the received request for the random access resource allocation.

[0218] Aspect 27 is the method according to any one of aspects 24 to 26, wherein the first part of the SIB includes an indication of the second assignment of the second PDSCH, the indication of the second assignment is associated with a second look-up table and includes an index of an entry in the second look-up table for the second assignment, and the second assignment of the second PDSCH corresponds to one or more of the following: time-frequency resource allocation, spatial relationship, waveform, MCS, time slot aggregation factor, TBS scaling factor, number of repetitions, DM-RS binding scheme, TBS, or information for coverage enhancement of the SIB, or any combination thereof.

[0219] Aspect 28 is a device for wireless communication, the device comprising: at least one processor, the at least one processor being coupled to a memory, and at least partially based on information stored in the memory, the at least one processor being configured to implement the method according to any one of aspects 1 to 27.

[0220] Aspect 29 can be combined with aspect 28 and further comprises: a transceiver, the transceiver being coupled to the at least one processor.

[0221] Aspect 30 is a device for wireless communication, the device comprising components for implementing any one of aspects 1 to 27.

[0222] Aspect 31 is a non-transitory computer-readable storage medium storing computer-executable code, wherein the code, when executed by a processor, causes the processor to implement any one of aspects 1 to 27.

[0223] Aspects have been described herein. These aspects and other aspects are within the scope of the following claims.

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: a memory; a transceiver; and at least one processor coupled to the memory and the transceiver, and at least partially based on information stored in the memory, the at least one processor is configured to: receive, via the transceiver, an indication of a first assignment of a first physical downlink shared channel (PDSCH) from a network entity via a physical broadcast channel (PBCH), the first PDSCH including at least a first part of a system information block (SIB); and receive, based on the first assignment of the first PDSCH, the first part of the SIB from the network entity via the first PDSCH via the transceiver.

2. The apparatus according to claim 1, wherein the indication of the first assignment of the first PDSCH is associated with a first lookup table, and the indication of the first assignment of the first PDSCH includes an index of an entry in the first lookup table for the first assignment.

3. The apparatus according to claim 1, wherein the first assignment of the first PDSCH corresponds to one or more of the following: time-frequency resource allocation, spatial relation, waveform, modulation and coding scheme (MCS), time slot aggregation factor, transport block size (TBS) scaling factor, number of repetitions, demodulation reference signal (DM-RS) binding scheme, TBS, or information for coverage enhancement of the SIB.

4. The apparatus according to claim 1, wherein the first part of the SIB includes access control information for the network entity, and the at least one processor is further configured to: identify whether the UE is permitted to access the network entity based on the access control information for the network entity.

5. The apparatus according to claim 4, the at least one processor is further configured to: perform a network entity selection or reselection operation when the UE is not permitted to access the network entity.

6. The apparatus according to claim 4, the at least one processor is further configured to: identify a second assignment of a second PDSCH including a second part of the SIB based at least on the received first part of the SIB when the UE is permitted to access the network entity; receive, via the transceiver, the second part of the SIB from the network entity via the second PDSCH; and identify a random access resource allocation for the network entity based at least on the received second part of the SIB.

7. The apparatus according to claim 6, wherein the second part of the SIB includes at least an indication of the random access resource allocation for the network entity and for the UE or an indication of an assignment for a subsequent SIB transmission from the network entity.

8. The apparatus according to claim 6, wherein the second part of the SIB includes information associated with on-demand random access resource allocation, and in order to identify the random access resource allocation for the network entity, the at least one processor is further configured to: Send a request for the random access resource allocation for the network entity based on a beacon and the information associated with the on-demand random access resource allocation; and Receive, from the network entity, a response indicating the random access resource allocation for the network entity and for the UE based on the sent request for the random access resource allocation.

9. The apparatus according to claim 6, wherein the first part of the SIB includes an indication of the second assignment of the second PDSCH, the indication of the second assignment is associated with a second look-up table, the indication of the second assignment includes an index of an entry in the second look-up table for the second assignment, and the second assignment of the second PDSCH corresponds to one or more of the following: Time-frequency resource allocation, Spatial relation, Waveform, Modulation and coding scheme (MCS), Slot aggregation factor, Transport block size (TBS) scaling factor, Number of repetitions, Demodulation reference signal (DM-RS) bundling scheme, TBS, or Information for coverage enhancement of the SIB, or Any combination thereof.

10. A method for wireless communication at a user equipment (UE), the method comprises: Receiving, via a physical broadcast channel (PBCH), an indication of a first assignment of a first physical downlink shared channel (PDSCH) from a network entity, the first PDSCH including at least a first part of a system information block (SIB); And Receiving, via the first PDSCH, the first part of the SIB from the network entity based on the first assignment of the first PDSCH.

11. The method according to claim 10, wherein the indication of the first assignment of the first PDSCH is associated with a first look-up table, and the indication of the first assignment of the first PDSCH includes an index of an entry in the first look-up table for the first assignment.

12. The method according to claim 10, wherein the first assignment of the first PDSCH corresponds to one or more of the following: time-frequency resource allocation, spatial relation, waveform, modulation and coding scheme (MCS), slot aggregation factor, transport block size (TBS) scaling factor, number of repetitions, demodulation reference signal (DM-RS) bundling scheme, TBS, or information for coverage enhancement of the SIB.

13. The method according to claim 10, wherein the first part of the SIB includes access control information for the network entity, and the method further comprises: Identifying whether the UE is permitted to access the network entity based on the access control information for the network entity.

14. The method according to claim 13, the method further comprises: Perform a network entity selection or reselection operation in case the UE is not permitted to access the network entity.

15. The method according to claim 13, the method further comprises: In case the UE is permitted to access the network entity, identify a second assignment of a second PDSCH based at least on a received first part of the SIB, the second PDSCH comprising a second part of the SIB; Receive the second part of the SIB from the network entity via the second PDSCH; and Identify a random access resource allocation for the network entity based at least on the received second part of the SIB.

16. The method according to claim 15, wherein the second part of the SIB comprises at least an indication of the random access resource allocation for the network entity and for the UE or an indication of an assignment for a subsequent SIB transmission from the network entity.

17. The method according to claim 15, wherein the second part of the SIB comprises information associated with on-demand random access resource allocation, and identifying the random access resource allocation for the network entity further comprises: Send a request for the random access resource allocation for the network entity based on a beacon and the information associated with the on-demand random access resource allocation; and Receive from the network entity a response indicating the random access resource allocation for the network entity and for the UE based on the sent request for the random access resource allocation.

18. The method according to claim 15, wherein the first part of the SIB comprises an indication of the second assignment of the second PDSCH, the indication of the second assignment being associated with a second look-up table, the indication of the second assignment comprising an index of an entry in the second look-up table for the second assignment, and the second assignment of the second PDSCH corresponds to one or more of the following: Time-frequency resource allocation, Spatial relation, Waveform, Modulation and coding scheme (MCS), Slot aggregation factor, Transport block size (TBS) scaling factor, Number of repetitions, Demodulation reference signal (DM-RS) bundling scheme, TBS, or Information for coverage enhancement of the SIB, or Any combination thereof.

19. An apparatus for wireless communication at a user equipment (UE), the apparatus comprises: A memory; A transceiver; and At least one processor, the at least one processor being coupled to the memory and the transceiver and being configured, at least in part based on information stored in the memory, to: Receive, via the transceiver, a first part of a system information block (SIB) from a network entity, the first part of the SIB comprising access control information for the network entity and indicating an assignment of a second PDSCH in case the access control information indicates that the UE is permitted to access the network entity; and Identify whether the UE is permitted to access the network entity based on the access control information for the network entity.

20. The apparatus according to claim 19, wherein the at least one processor is further configured to: Perform a network entity selection or reselection operation when the access control information indicates that the UE is not permitted to access the network entity.

21. The apparatus according to claim 19, wherein the second PDSCH comprises a second part of the SIB, and the at least one processor is further configured to: Receive, via the transceiver, the second part of the SIB from the network entity via the second PDSCH; and Identify the random access resource allocation for the network entity based at least on the received second part of the SIB.

22. The apparatus according to claim 21, wherein the second part of the SIB comprises at least an indication of the random access resource allocation for the network entity and for the UE or an indication of an assignment for a subsequent SIB transmission from the network entity.

23. The apparatus according to claim 21, wherein the second part of the SIB comprises information associated with on-demand random access resource allocation, and in order to identify the random access resource allocation for the network entity, the at least one processor is further configured to: Send, via the transceiver, a request for the random access resource allocation for the network entity based on a beacon and the information associated with the on-demand random access resource allocation; and Receive, from the network entity, a response indicating the random access resource allocation for the network entity and for the UE based on the sent request for the random access resource allocation.

24. The apparatus according to claim 21, wherein the indication of the second assignment is associated with a second lookup table and comprises an index of an entry in the second lookup table for the second assignment, and the second assignment of the second PDSCH corresponds to one or more of the following: Time-frequency resource allocation, Spatial relation, Waveform, Modulation and coding scheme (MCS), Time slot aggregation factor, Transport block size (TBS) scaling factor, Number of repetitions, Demodulation reference signal (DM-RS) bundling scheme, TBS, or Information for coverage enhancement of the SIB, or Any combination thereof.

25. A method for wireless communication at a user equipment (UE), the method comprises: Receive, from a network entity, a first part of a system information block (SIB), the first part of the SIB comprising access control information for the network entity and indicating an assignment of a second PDSCH when the access control information indicates that the UE is permitted to access the network entity; and Identify whether the UE is permitted to access the network entity based on the access control information for the network entity.

26. The method according to claim 25, the method further comprises: Perform a network entity selection or reselection operation in case the access control information indicates that the UE is not permitted to access the network entity.

27. The method according to claim 25, wherein the second PDSCH comprises a second part of the SIB, and the method further comprises: Receiving, via the second PDSCH, the second part of the SIB from the network entity; and Identifying a random access resource allocation for the network entity based at least on the received second part of the SIB.

28. The method according to claim 27, wherein the second part of the SIB comprises at least an indication of the random access resource allocation for the network entity and for the UE or an indication of an assignment for a subsequent SIB transmission from the network entity.

29. The method according to claim 27, wherein the second part of the SIB comprises information associated with on-demand random access resource allocation, and identifying the random access resource allocation for the network entity further comprises: Sending, based on a beacon and the information associated with the on-demand random access resource allocation, a request for the random access resource allocation for the network entity; and Receiving, based on the sent request for the random access resource allocation, a response from the network entity indicating the random access resource allocation for the network entity and for the UE.

30. The method according to claim 27, wherein the indication of the second assignment is associated with a second lookup table and comprises an index of an entry in the second lookup table for the second assignment, and the second assignment of the second PDSCH corresponds to one or more of the following: Time-frequency resource allocation, Spatial relation, waveform, Modulation and coding scheme (MCS), Slot aggregation factor, Transport block size (TBS) scaling factor, Number of repetitions, Demodulation reference signal (DM-RS) binding scheme, TBS, or Information for coverage enhancement of the SIB, or Any combination thereof.

31. An apparatus for wireless communication at a network entity, the apparatus comprises: A memory; and At least one processor coupled to the memory and configured, at least in part based on information stored in the memory, to: Send, via a physical broadcast channel (PBCH), an indication of a first assignment of a first physical downlink shared channel (PDSCH) for a user equipment (UE), the first PDSCH comprising at least a first part of a system information block (SIB); and Send, based on the first assignment of the first PDSCH, the first part of the SIB for the UE via the first PDSCH.

32. The apparatus according to claim 31, wherein the indication of the first assignment of the first PDSCH is associated with a first lookup table, and the indication of the first assignment of the first PDSCH comprises an index of an entry in the first lookup table for the first assignment.

33. The apparatus according to claim 31, wherein the first assignment of the first PDSCH corresponds to one or more of the following: time-frequency resource allocation, spatial relation, waveform, time slot aggregation factor, transport block size (TBS) scaling factor, number of repetitions, demodulation reference signal (DM-RS) binding scheme, modulation and coding scheme (MCS), TBS, or information for coverage enhancement of the SIB.

34. The apparatus according to claim 31, wherein the first part of the SIB includes access control information for the network entity, and the UE is permitted or not permitted to access the network entity based on the access control information for the network entity.

35. The apparatus according to claim 34, wherein the at least one processor is further configured to: transmit, via the second PDSCH, the second part of the SIB for the UE based on a second assignment of the second PDSCH when the UE is permitted to access the network entity, the second assignment of the second PDSCH being based on the first part of the SIB.

36. The apparatus according to claim 35, wherein the second part of the SIB includes at least an indication of random access resource allocation for the network entity and for the UE or an indication of an assignment for subsequent SIB transmission from the network entity.

37. The apparatus according to claim 35, wherein the second part of the SIB includes information associated with on-demand random access resource allocation, and the at least one processor is further configured to: receive, from the UE, a request for random access resource allocation based on a beacon and the information associated with the on-demand random access resource allocation; and transmit, for the UE, a response indicating the random access resource allocation for the network entity and for the UE based on the received request for the random access resource allocation.

38. The apparatus according to claim 35, wherein the first part of the SIB includes an indication of the second assignment of the second PDSCH, the indication of the second assignment being associated with a second look-up table, the indication of the second assignment including an index of an entry in the second look-up table for the second assignment, and the second assignment of the second PDSCH corresponds to one or more of the following: time-frequency resource allocation, spatial relation, waveform, modulation and coding scheme (MCS), time slot aggregation factor, transport block size (TBS) scaling factor, number of repetitions, demodulation reference signal (DM-RS) binding scheme, TBS, or information for coverage enhancement of the SIB, or any combination thereof.

39. The apparatus according to claim 31, the apparatus further includes a transceiver coupled to the at least one processor, the transceiver being configured to transmit the indication of the assignment of the first PDSCH and the first part of the SIB.

40. A method for wireless communication at a network entity, the method comprises: Indicating a first assignment of a first physical downlink shared channel (PDSCH) for a user equipment (UE) via a physical broadcast channel (PBCH), the first PDSCH including at least a first part of a system information block (SIB); and Transmitting, via the first PDSCH, the first part of the SIB for the UE based on the first assignment of the first PDSCH.

41. The method according to claim 40, wherein the indication of the first assignment of the first PDSCH is associated with a first look-up table, and the indication of the first assignment of the first PDSCH includes an index of an entry in the first look-up table for the first assignment.

42. The method according to claim 40, wherein the first assignment of the first PDSCH corresponds to one or more of the following: time-frequency resource allocation, spatial relationship, waveform, time slot aggregation factor, transport block size (TBS) scaling factor, number of repetitions, demodulation reference signal (DM-RS) bundling scheme, modulation and coding scheme (MCS), TBS, or information for coverage enhancement of the SIB.

43. The method according to claim 40, wherein the first part of the SIB includes access control information for the network entity, and the UE is granted or not granted access to the network entity based on the access control information for the network entity.

44. The method according to claim 43, the method further comprises: Transmitting, via a second PDSCH, a second part of the SIB for the UE based on a second assignment of the second PDSCH when the UE is granted access to the network entity, the second assignment of the second PDSCH being based on the first part of the SIB.

45. The method according to claim 44, wherein the second part of the SIB includes at least an indication of random access resource allocation for the network entity and for the UE or an indication of an assignment for subsequent SIB transmission from the network entity.

46. The method according to claim 44, wherein the second part of the SIB includes information associated with on-demand random access resource allocation, and the method further comprises: Receiving, from the UE, a request for random access resource allocation based on a beacon and the information associated with the on-demand random access resource allocation; and Transmitting, in response to the received request for random access resource allocation, an indication of the random access resource allocation for the network entity and for the UE for the UE.

47. The method according to claim 44, wherein the first part of the SIB includes an indication of the second assignment of the second PDSCH, the indication of the second assignment being associated with a second look-up table, the indication of the second assignment including an index of an entry in the second look-up table for the second assignment, and the second assignment of the second PDSCH corresponds to one or more of the following: Time-frequency resource allocation, Spatial relationship, Waveform, Modulation and coding scheme (MCS), Slot aggregation factor, Transport block size (TBS) scaling factor, Number of repetitions, Demodulation reference signal (DM-RS) bundling scheme, TBS, or Information for coverage enhancement of the SIB, or Any combination thereof.

48. An apparatus for wireless communication at a network entity, the apparatus comprising: a memory; and at least one processor coupled to the memory and configured at least in part based on information stored in the memory to: transmit a first portion of a system information block (SIB) for a user equipment (UE), the first portion of the SIB including access control information for the network entity, wherein the UE is granted or not granted access to the network entity based on the access control information for the network entity; and transmit a second portion of the SIB for the UE via a second physical downlink shared channel (PDSCH) based on a second assignment of the second PDSCH in the case where the UE is granted access to the network entity, the second assignment of the second PDSCH being based on the first portion of the SIB in the case where the UE is granted access to the network entity.

49. The apparatus according to claim 48, wherein the second portion of the SIB includes at least an indication of random access resource allocation for the network entity and for the UE or an indication of an assignment for transmission of a subsequent SIB from the network entity.

50. The apparatus according to claim 48, wherein the second portion of the SIB includes information associated with on-demand random access resource allocation, and the at least one processor is further configured to: receive a request for random access resource allocation from the UE based on a beacon and the information associated with the on-demand random access resource allocation; and transmit, based on the received request for the random access resource allocation, a response indicating the random access resource allocation for the network entity and for the UE for the UE.

51. The apparatus according to claim 48, wherein the first portion of the SIB includes an indication of the second assignment of the second PDSCH, the indication of the second assignment being associated with a second look-up table and including an index of an entry in the second look-up table for the second assignment, and the second assignment of the second PDSCH corresponds to one or more of the following: Time-frequency resource allocation, Spatial relationship, Waveform, Modulation and coding scheme (MCS), Slot aggregation factor, Transport block size (TBS) scaling factor, Number of repetitions, Demodulation reference signal (DM-RS) bundling scheme, TBS, or Information for coverage enhancement of the SIB, or Any combination thereof.

52. The apparatus according to claim 48, the apparatus further comprising a transceiver coupled to the at least one processor, the transceiver being configured to transmit the first portion of the SIB.

53. A method for wireless communication at a network entity, the method comprises: transmitting, for a user equipment (UE), a first part of a system information block (SIB), the first part of the SIB including access control information for the network entity, wherein the UE is permitted or not permitted to access the network entity based on the access control information for the network entity; and transmitting, via a second physical downlink shared channel (PDSCH) for the UE, a second part of the SIB based on a second assignment of the second PDSCH when the UE is permitted to access the network entity, wherein the second assignment of the second PDSCH is based on the first part of the SIB when the UE is permitted to access the network entity.

54. The method according to claim 53, wherein the second part of the SIB comprises at least an indication of random access resource allocation for the network entity and for the UE or an indication of an assignment for subsequent SIB transmission from the network entity.

55. The method according to claim 53, wherein the second part of the SIB comprises information associated with on-demand random access resource allocation, and the method further comprises: receiving, from the UE, a request for random access resource allocation based on a beacon and the information associated with the on-demand random access resource allocation; and transmitting, for the UE, a response indicating the random access resource allocation for the network entity and for the UE based on the received request for the random access resource allocation.

56. The method according to claim 53, wherein the first part of the SIB comprises an indication of the second assignment of the second PDSCH, the indication of the second assignment being associated with a second lookup table and including an index of an entry in the second lookup table for the second assignment, and the second assignment of the second PDSCH corresponds to one or more of the following: time-frequency resource allocation, spatial relation, waveform, modulation and coding scheme (MCS), time slot aggregation factor, transport block size (TBS) scaling factor, number of repetitions, demodulation reference signal (DM-RS) binding scheme, TBS, or information for coverage enhancement of the SIB, or any combination thereof.

Images