Combined random access response and remaining minimum system information

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may transmit physical random access channel (PRACH) communications to a network node. The UE may receive a random access response (RAR) communication and a system information block 1 (SIB1) communication including remaining minimum system information (RMSI) from the network node and based at least in part on the PRACH communication. Numerous other aspects are described.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. Patent Application No. 17 / 809,972, filed on June 30, 2022, entitled “COMBINED RANDOMACCESS RESPONSE AND REMAINING MINIMUM SYSTEMINFORMATION” and assigned to the assignee of this patent application. The disclosure of the prior application is considered a part of and incorporated by reference into this patent application. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communications and to techniques and apparatus for combined random access responses and remaining minimum system information. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). 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, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0005] A wireless network may include one or more network nodes that support communications for wireless communication devices, such as user equipment (UE) or multiple UEs. A UE may communicate with a network node via downlink communications and uplink communications. A "downlink" (or "DL") refers to a communication link from a network node to a UE, and an "uplink" (or "UL") refers to a communication link from a UE to a network node. Some wireless networks may support device-to-device communications, such as via a local link (e.g., a side link (SL), a wireless local area network (WLAN) link, and / or a wireless personal area network (WPAN) link, among other examples).

[0006] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region and / or global level. New Radio (NR) (which may be referred to as 5G) is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better integrate with other open standards by improving spectrum efficiency, reducing costs, improving services, utilizing new spectrum, and using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with cyclic prefix (CP) on the downlink, using CP-OFDM and / or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink, and supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation, so as to better support mobile broadband Internet access. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR and other radio access technologies remain useful. Summary of the invention

[0007] Some aspects described herein relate to a method of wireless communication performed by a user equipment (UE). The method may include sending a physical random access channel (PRACH) communication to a network node. The method may include receiving a random access response (RAR) communication and a system information block 1 (SIB1) communication including remaining minimum system information (RMSI) from the network node and based at least in part on the PRACH communication.

[0008] Some aspects described herein relate to a method of wireless communication performed by a network node. The method may include receiving a PRACH communication from a UE. The method may include sending a RAR communication and a SIB1 communication including an RMSI to the UE and based at least in part on the PRACH communication.

[0009] Some aspects described herein relate to a UE for wireless communication. The UE may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to send a PRACH communication to a network node. The one or more processors may be configured to receive a RAR communication and a SIB1 communication including an RMSI from the network node and based at least in part on the PRACH communication.

[0010] Some aspects described herein relate to a network node for wireless communication. The network node may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive a PRACH communication from a UE. The one or more processors may be configured to send a RAR communication and a SIB1 communication including an RMSI to the UE and based at least in part on the PRACH communication.

[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a UE. The instruction set, when executed by one or more processors of the UE, may cause the UE to send a PRACH communication to a network node. The instruction set, when executed by one or more processors of the UE, may cause the UE to receive a RAR communication and a SIB1 communication including an RMSI from the network node and based at least in part on the PRACH communication.

[0012] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a network node. The instruction set, when executed by one or more processors of the network node, may cause the network node to receive a PRACH communication from a UE. The instruction set, when executed by one or more processors of the network node, may cause the network node to send a RAR communication and a SIB1 communication including an RMSI to the UE and based at least in part on the PRACH communication.

[0013] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for sending a PRACH communication to a network node. The apparatus may include means for receiving a RAR communication and a SIB1 communication including an RMSI from the network node and based at least in part on the PRACH communication.

[0014] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for receiving a PRACH communication from a UE. The apparatus may include components for sending a RAR communication and a SIB1 communication including an RMSI to the UE and based at least in part on the PRACH communication.

[0015] The various aspects generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network entities, network nodes, wireless communication devices and / or processing systems as fully described herein with reference to the drawings and description and as illustrated in the drawings and description.

[0016] The features and technical advantages of examples according to the present disclosure have been outlined quite broadly above so that the following specific embodiments may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description and not as a definition of limitations to the claims.

[0017] Although various aspects are described in the present disclosure by illustrating some examples, it will be understood by those skilled in the art that such aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment, and / or artificial intelligence devices). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components and / or system-level components. The equipment incorporating the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include one or more components (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers) for analog and digital purposes. The various aspects described herein are intended to be practiced in various devices, components, systems, distributed arrangements, and / or end-user devices of various sizes, shapes and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to fully understand the above-mentioned features of the present disclosure, a more specific description of the invention briefly summarized above can be obtained by referring to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings only illustrate certain typical aspects of the present disclosure and are therefore not to be considered as limiting the scope thereof, as the specification may admit of other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0019] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

[0020] Figure 2 is a diagram illustrating an example of communication between a network node and a UE in a wireless network according to the present disclosure.

[0021] Figure 3 is a diagram illustrating an example decomposed base station architecture according to the present disclosure.

[0022] Figure 4 is a diagram illustrating an example of an initial access procedure according to the present disclosure.

[0023] Figure 5 is a diagram illustrating an example associated with a combined random access response (RAR) and remaining minimum system information (RMSI) according to the present disclosure.

[0024] Figure 6 is a diagram illustrating an example process performed, for example, by a UE according to the present disclosure.

[0025] Figure 7 is a diagram illustrating an example process, for example, performed by a network node, according to the present disclosure.

[0026] Figure 8 is a diagram of an example apparatus for wireless communications according to the present disclosure.

[0027] Fig. 9 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

[0028] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms, and should not be construed as being limited to any specific structure or function presented throughout the present disclosure. On the contrary, these aspects are provided so that the present disclosure will be thorough and complete, and the scope of the present disclosure will be fully conveyed to those skilled in the art. It should be understood by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether it is implemented independently or in combination with any other aspect of the present disclosure. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods that are practiced using other structures, functions, or structures and functions in addition to or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the claims.

[0029] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0030] Although various aspects may be described herein using terms generally associated with 5G or new radio (NR) radio access technology (RAT), various aspects of the present disclosure may be applied to other RATs, such as 3G RAT, 4G RAT and / or RATs beyond 5G (e.g., 6G).

[0031] Figure 11 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network and / or elements of a 4G (e.g., Long Term Evolution (LTE)) network, as well as other examples. The wireless network 100 may include one or more network nodes 110 (shown as network node 110a, network node 110b, network node 110c, and network node 110d), user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other entities. The network node 110 is a network node that communicates with the UE 120. As shown in the figure, the network node 110 may include one or more network nodes. For example, the network node 110 may be a converged network node, which means that the converged network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node (e.g., within a single device or unit). As another example, the network node 110 may be a decomposed network node (sometimes referred to as a decomposed base station), which means that the network node 110 is configured to utilize a protocol stack that is physically or logically distributed between two or more nodes (such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)).

[0032] In some examples, the network node 110 is or includes a network node that communicates with the UE 120 via a radio access link, such as an RU. In some examples, the network node 110 is or includes a network node that communicates with other network nodes 110 via a fronthaul link or a midhaul link, such as a DU. In some examples, the network node 110 is or includes a network node that communicates with other network nodes 110 via a midhaul link or communicates with the core network via a backhaul link, such as a CU. In some examples, the network node 110 (such as an aggregated network node 110 or a decomposed network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. The network node 110 may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, a transmit receive point (TRP), a DU, a RU, a CU, a mobility element of a network, a core network node, a network element, a network equipment, a RAN node, or a combination thereof. In some examples, network nodes 110 may be interconnected to each other or to one or more other network nodes 110 in wireless network 100 via various types of fronthaul, midhaul, and / or backhaul interfaces, such as direct physical connections, air interfaces, or virtual networks, using any suitable transport network.

[0033] In some examples, the network node 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" may refer to the coverage area of ​​the network node 110 and / or the network node subsystem serving the coverage area, depending on the context in which the term is used. The network node 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by a UE 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by a UE 120 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by a UE 120 associated with a femto cell (e.g., a UE 120 in a closed subscriber group (CSG)). A network node 110 for a macro cell may be referred to as a macro network node. A network node 110 for a pico cell may be referred to as a pico network node. The network node 110 for a femto cell may be referred to as a femto network node or a home network node. Figure 1 In the example shown in , network node 110a may be a macro network node for macro cell 102a, network node 110b may be a pico network node for pico cell 102b, and network node 110c may be a femto network node for femto cell 102c. A network node may support one or more (e.g., three) cells. In some examples, a cell may not necessarily be stationary, and the geographic area of ​​a cell may move depending on the location of a mobile network node 110 (e.g., a mobile network node).

[0034] In some aspects, the term "base station" or "network node" may refer to an aggregated base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, a "base station" or "network node" may refer to a CU, a DU, a RU, a near real-time (near RT) RAN intelligent controller (RIC) or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network node" may refer to a device configured to perform one or more functions (such as those described herein in conjunction with network node 110). In some aspects, the term "base station" or "network node" may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of a number of different devices (which may be located in the same geographic location or in different geographic locations) may be configured to perform at least a portion of a function, or to repeat the execution of at least a portion of the function, and the term "base station" or "network node" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network node" may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term "base station" or "network node" may refer to one of the base station functions but not the other. In this way, a single device may include more than one base station.

[0035] The wireless network 100 may include one or more relay stations. A relay station is a network node that can receive transmissions of data from an upstream node (e.g., a network node 110 or a UE 120) and transmit transmissions of data to a downstream node (e.g., a UE 120 or a network node 110). A relay station may be a UE 120 that is capable of relaying transmissions for other UEs 120. Figure 1 In the example shown in , a network node 110d (e.g., a relay network node) may communicate with a network node 110a (e.g., a macro network node) and a UE 120d to facilitate communications between the network node 110a and the UE 120d. A network node 110 that relays communications may be referred to as a relay station, a relay base station, a relay network node, a relay node, a relay, etc.

[0036] The wireless network 100 may be a heterogeneous network that includes different types of network nodes 110, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, etc. These different types of network nodes 110 may have different transmit power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, a macro network node may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico network node, a femto network node, and a relay network node may have a lower transmit power level (e.g., 0.1 watt to 2 watts).

[0037] The network controller 130 may be coupled to or in communication with a set of network nodes 110 and may provide coordination and control for the network nodes 110. The network controller 130 may communicate with the network nodes 110 via a backhaul communication link or a midhaul communication link. The network nodes 110 may also communicate directly with each other or indirectly via a wireless backhaul communication link or a wired backhaul communication link. In some aspects, the network controller 130 may be or may include a CU or a core network device.

[0038] UE 120 can be distributed throughout the wireless network 100, and each UE 120 can be stationary or mobile. UE 120 can include, for example, an access terminal, a terminal, a mobile station and / or a subscriber unit. UE 120 can be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet device, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, an industrial manufacturing equipment, a global positioning system device, a UE function of a network node and / or any other suitable device configured to communicate via a wireless or wired medium.

[0039] Some UE 120 may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UE. MTC UE and / or eMTC UE may include, for example, a robot, a drone, a remote device, a sensor, a meter, a monitor and / or a location tag, which may communicate with a network node, another device (e.g., a remote device) or some other entity. Some UE 120 may be considered as an Internet of Things (IoT) device and / or may be implemented as a NB-IoT (narrowband IoT) device. Some UE 120 may be considered as customer premises equipment. UE 120 may be included in a housing that houses components of UE 120, such as a processor component and / or a memory component. In some examples, the processor component and the memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operationally coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0040] In general, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a specific RAT and may operate on one or more frequencies. RAT may be referred to as a radio technology, an air interface, etc. Frequency may be referred to as a carrier, a frequency channel, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0041] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly (e.g., without using network node 110 as an intermediary to communicate with each other) using one or more side link channels. For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or mesh networks. In such examples, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by network node 110.

[0042] The devices of the wireless network 100 may communicate using an electromagnetic spectrum, which may be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, the devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency ranges designated FR1 (410 MHz–7.125 GHz) and FR2 (24.25 GHz–52.6 GHz). It should be understood that, although portions of FR1 are greater than 6 GHz, FR1 is often (interchangeably) referred to as the “below 6 GHz” band in various documents and articles. Similar naming issues sometimes occur with respect to FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz–300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU).

[0043] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz–24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and therefore the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6GHz–71GHz), FR4 (52.6GHz–114.25GHz), and FR5 (114.25GHz–300GHz). Each of these higher frequency bands falls within the EHF band.

[0044] In view of the above examples, unless otherwise explicitly stated, it should be understood that if the term "below 6 GHz" or the like is used herein, the term can be broadly referred to as a frequency that can be lower than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise explicitly stated, it should be understood that if the term "millimeter wave" or the like is used herein, the term can be broadly referred to as a frequency that can include mid-band frequencies, can be within FR2, FR4, FR4-a or FR4-1 and / or FR5, or can be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) can be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0045] In some aspects, UE 120 may include a communication manager 140. As described in greater detail elsewhere herein, the communication manager 140 may send a physical random access channel (PRACH) communication to a network node; and receive a random access response (RAR) communication and a system information block 1 (SIB1) communication including remaining minimum system information (RMSI) from the network node and based at least in part on the PRACH communication. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0046] In some aspects, the network node 110 may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may receive a PRACH communication from a UE; and send a RAR communication and a SIB1 communication including a RMSI to the UE and based at least in part on the PRACH communication. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0047] As indicated above, Figure 1 are provided as examples. Other examples can be found in the Figure 1 The examples described are different.

[0048] Figure 2 2 is a diagram illustrating an example 200 of a network node 110 communicating with a UE 120 in a wireless network 100 according to the present disclosure. The network node 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). The UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1). The network node 110 of example 200 includes one or more radio frequency components, such as an antenna 234 and a modem 254. In some examples, the network node 110 may include an interface, a communication component, or another component that facilitates communication with the UE 120 or another network node. Some network nodes 110 may not include a radio frequency component that facilitates direct communication with the UE 120, such as one or more CUs or one or more DUs.

[0049] At the network node 110, a transmit processor 220 may receive data intended for a UE 120 (or a set of UEs 120) from a data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCS) for the UE 120 based at least in part on one or more channel quality indicators (CQIs) received from the UE 120. The network node 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS selected for the UE 120, and may provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling), and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., pre-coding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modulators) (shown as modems 232a to 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may further process (e.g., convert to analog, amplify, filter, and / or upconvert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a through 232t may transmit a set of downlink signals (eg, T downlink signals) via a corresponding set of antennas 234 (eg, T antennas) (shown as antennas 234a through 234t).

[0050] At the UE 120, a set of antennas 252 (shown as antennas 252a to 252r) may receive downlink signals from the network node 110 and / or other network nodes 110 and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a to 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain input samples. Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modem 254, may perform MIMO detection on the received symbols where applicable, and may provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to the data sink 260, and may provide decoded control information and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter, among other things. In some examples, one or more components of the UE 120 may be included in the housing 284.

[0051] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the network node 110 via the communication unit 294.

[0052] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (within a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and / or coupled to one or more transmit and / or receive components (such as, Figure 2 One or more antenna elements of one or more components in.

[0053] On the uplink, at the UE 120, the transmit processor 264 may receive and process data from the data source 262 and control information from the controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266, where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and sent to the network node 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to perform operations described herein (eg, with reference to Figures 4 to 9 ) or any aspect of any of the methods described herein.

[0054] At the network node 110, uplink signals from the UE 120 and / or other UEs may be received by the antenna 234, processed by the modem 232 (e.g., a demodulator component (shown as DEMOD) of the modem 232), detected by the MIMO detector 236 (where applicable), and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and the decoded control information to the controller / processor 240. The network node 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink communication and / or uplink communication. In some examples, the modem 232 of the network node 110 may include a modulator and a demodulator. In some examples, the network node 110 includes a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform operations described herein (e.g., with reference to Figures 4 to 9 ) or any aspect of any of the methods described herein.

[0055] The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other components of the UE 120 may perform one or more techniques associated with combined RAR and RMSI, as described in more detail elsewhere herein. For example, the controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of may perform or direct e.g. Figure 6 The process of 600 Figure 7 700 and / or operations of other processes as described herein. Memory 242 and memory 282 may store data and program codes for network node 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed by one or more processors of network node 110 and / or UE 120 (e.g., directly, or after compilation, conversion and / or interpretation), may cause the one or more processors, UE 120 and / or network node 110 to perform or direct, for example Figure 6 The process of 600 Figure 7 The process 700 of and / or operations of other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.

[0056] In some aspects, a UE (e.g., UE 120) includes a component for sending a PRACH communication to a network node; and / or a component for receiving a RAR communication and a SIB1 communication including a RMSI from a network node and based at least in part on the PRACH communication. The components for the UE to perform the operations described herein may include, for example, one or more of the following: a communication manager 140, an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, or a memory 282.

[0057] In some aspects, a network node (e.g., network node 110) includes a component for receiving a PRACH communication from a UE; and / or a component for sending a RAR communication and a SIB1 communication including a RMSI to a UE and based at least in part on the PRACH communication. In some aspects, the components for the network node to perform the operations described herein may include, for example, one or more of the communication manager 150, the transmit processor 220, the TX MIMO processor 230, the modem 232, the antenna 234, the MIMO detector 236, the receive processor 238, the controller / processor 240, the memory 242, or the scheduler 246.

[0058] Although Figure 2 The blocks in the 200 and 210 are illustrated as distinct components, but the functionality described above with respect to these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described with respect to the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0059] As indicated above, Figure 2 are provided as examples. Other examples can be found in the Figure 2 The examples described are different.

[0060] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or components in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element, a base station or network equipment can be implemented in an aggregated or decomposed architecture. For example, a base station (such as a node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a TRP or a cell, etc.) or one or more units (or one or more components) that perform base station functionality can be implemented as an aggregated base station (also referred to as an independent base station or a monolithic base station) or a decomposed base station. "Network entity" or "network node" may refer to a decomposed base station or one or more units of a decomposed base station (such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof).

[0061] An aggregated base station (e.g., an aggregated network node) may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node (e.g., within a single device or unit). A decomposed base station (e.g., a decomposed network node) may be configured to utilize a protocol stack physically or logically distributed between two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, a CU may be implemented within a network 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 network nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may also be implemented as a virtual unit, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), and the like.

[0062] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a decomposed base station may be utilized in an IAB network, an open radio access network (O-RAN (such as a network configuration initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)) to facilitate the scaling of a communication system by separating base station functionality into one or more units that can be deployed separately. A decomposed base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented virtually for at least one unit, which may enable flexibility in network design. Various units of a decomposed base station may be configured for wired or wireless communication with at least one other unit of the decomposed base station.

[0063] Figure 3 3 is a diagram illustrating an example disaggregated base station architecture 300 according to the present disclosure. The disaggregated base station architecture 300 may include a CU 310 that may communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more disaggregated control units, such as a near-RT RIC 325 via an E2 link, or a non-RT RIC 315 associated with a service management and orchestration (SMO) framework 305, or both. The CU 310 may communicate with one or more DUs 330 via respective midhaul links, such as via an F1 interface. Each of the DUs 330 may communicate with one or more RUs 340 via respective fronthaul links. Each of the RUs 340 may communicate with one or more UEs 120 via respective radio frequency (RF) access links. In some implementations, a UE 120 may be served by multiple RUs 340 simultaneously.

[0064] Each of the units (including CU 310, DU 330, RU 340) and the near-RT RIC 325, non-RT RIC 315, and SMO framework 305 may include or be coupled to one or more interfaces, the one or more interfaces being configured to receive or send 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 one or more communication interfaces of the corresponding unit may be configured to communicate with one or more of the other units via a transmission medium. In some examples, each of the units may include a wired interface and a wireless interface, the wired interface being configured to receive signals or send signals to one or more of the other units via a wired transmission medium, the wireless interface being configured to receive signals or send signals to one or more of the other units via a wired transmission medium, or both.

[0065] In some aspects, CU 310 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC) functions, packet data convergence protocol (PDCP) functions, or service data adaptation protocol (SDAP) functions, etc. Each control function can be implemented using an interface that is configured to communicate signals with other control functions hosted by CU 310. CU 310 may be configured to handle user plane functionality (e.g., central unit-user plane (CU-UP) functionality), control plane functionality (e.g., central unit-control plane (CU-CP) functionality), or a combination thereof. In some specific implementations, CU 310 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 unit may communicate bidirectionally with the CU-CP unit via an interface such as an E1 interface. As needed, CU 310 may be implemented to communicate with DU 330 for network control and signaling.

[0066] Each DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 340. In some aspects, the DU 330 may host one or more of a radio link control (RLC) layer, a MAC layer, and one or more high physical (PHY) layers, at least in part, according to a functional partition such as that defined by 3GPP. In some aspects, one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc. In some aspects, the DU 330 may also host one or more low PHY layers, such as one or more modules for fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming or physical random access channel (PRACH) extraction and filtering, etc. Each layer (which may also be referred to as a module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0067] Each RU 340 may implement lower layer functionality. In some deployments, the RU 340 controlled by the DU 330 may correspond to a logical node that hosts RF processing functions or low PHY layer functions such as performing FFT, performing iFFT, digital beamforming, or PRACH extraction and filtering based on functional splitting (e.g., functional splitting defined by 3GPP) (such as lower layer functional splitting). In this architecture, each RU 340 may be operated to handle over-the-air (OTA) communications with one or more UEs 120. In some specific implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture such as a vRAN architecture.

[0068] The SMO framework 305 may be configured to support RAN deployment and configuration of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 305 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 an O1 interface). For virtualized network elements, the SMO framework 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) platform 390) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 315, and near-RTRIC 325. In some specific implementations, the SMO framework 305 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 311) via an O1 interface. Additionally, in some implementations, the SMO framework 305 can communicate directly with each of the one or more RUs 340 via a corresponding O1 interface. The SMO framework 305 can also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305.

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

[0070] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 325, the non-RT RIC 315 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 325 and may be received from a non-network data source or from a network function at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or the near-RT RIC 325 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective measures through the SMO framework 305 (such as via reconfiguration of the O1 interface) or via the creation of RAN management policies (such as A1 interface policies).

[0071] As indicated above, Figure 3 are provided as examples. Other examples can be found in the Figure 3 The examples described are different.

[0072] Figure 4 is a diagram illustrating an example 400 of an initial access procedure according to the present disclosure.

[0073] like Figure 4 As shown, in a 5G NR system, during initial access, a network entity may transmit to up to 64 synchronization signal block (SSB) beams. The network entity may transmit the SSB beam using time division multiplexing (TDM). The network entity may transmit the SSB beam based at least in part on beam scanning. During cell search, the UE may detect one of the SSB beams. In other words, the UE may detect the SSB from a specific beam. The master information block (MIB) associated with the SSB may configure control resource set (CORESET) 0 and search space set type 0. The network entity may transmit downlink control information (DCI) (e.g., DCI format 1_0) based at least in part on CORESET 0 and search space set type 0, wherein the DCI may be a cyclic redundancy check (CRC) scrambled by a system information radio network temporary identifier (SI-RNTI). The network entity may transmit the DCI via physical downlink shared channel (PDSCH) communication. The UE may detect the DCI. The DCI may schedule the RMSI, which may include SIB1 (e.g., SIB1 PDSCH). SIB1 may configure a random access channel (RACH). The UE may send a RACH message to a network entity at a RACH opportunity based at least in part on SIB1, wherein the RACH opportunity may be configured by the network entity. The RACH message may be message 1 (Msg1) or message A (MsgA) of a RACH procedure. The UE may access the network entity based at least in part on a RACH procedure.

[0074] The 5G NR system may support up to 64 SSBs, up to 64 CORESET 0s, up to 64 SIB1 PDSCHs, and up to 64 RACHs. In other words, SSBs, CORESET 0s, SIB1 PDSCHs, and RACHs may be per-beam, and resources may be per-beam reserved. In other words, multiple initial access channels and messages (e.g., all initial access channels or messages) may be repeated per-beam (with up to 64 separate beams), which may contribute to initial access overhead.

[0075] As an example, the 5G NR system may be a 400 MHz system with a subcarrier spacing (SCS) of 120 kHz. The 5G NR system may employ 64 wide beams. The 5G NR system may provide CORESET 0, which may be associated with one OFDM symbol and 48 resource blocks (RBs). The 5G NR system may provide SIB1 PDSCH, which may be associated with 7 OFDM symbols and 48 RBs. The 5G NR system may employ RACH, where there may be 6 OFDM symbols per RACH opportunity, two RACH opportunities per slot, and one-to-one SSB to resource opportunity mapping may occur. In the 5G NR system, the periodicity for SSB, CORESET 0, SIB1 PDSCH, and RACH may be 20 milliseconds (ms). The 5G NR system may employ a time division duplex (TDD) configuration of "DDDSU", where "D" represents a downlink slot, "S" represents a special slot, and "U" indicates an uplink slot. In this example, SSB may consume approximately 1.1% of the available downlink resources, CORESET 0 may consume approximately 1.3% of the available downlink resources, and SIB1 PDSCH may consume approximately 4.6% of the available downlink resources. RACH may consume approximately 3.7% of the available uplink resources. Initial access (e.g., SSB, CORESET 0, SIB1 PDSCH, and RACH) may consume approximately 7% of the total available downlink resources, and initial access may consume approximately 6.2% of the total available downlink and uplink resources. SIB1 PDSCH may consume approximately 66% of the downlink resources for initial access, and SIB1 PDSCH may consume approximately 56% of the downlink resources and uplink resources for initial access. Therefore, initial access and, in particular, SIB1 PDSCH may generate a considerable amount of overhead for 5G NR systems.

[0076] In some examples, to address this overhead issue, during the initial access procedure, the network entity may send a dedicated CORESET 0 or a dedicated SIB1 PDSCH. The network entity may send the dedicated CORESET 0 or the dedicated SIB1 PDSCH based at least in part on a request received from the UE. The network entity may send the dedicated CORESET 0 or the dedicated SIB1 PDSCH on an on-demand basis. For example, the network entity may send multiple SSB beams. The UE may detect one of the SSB beams. In other words, the UE may detect the SSB from a specific beam. The UE may send a RACH message to the network entity using the beam, and the RACH message may indicate the request. The network entity may send a dedicated SIB1 PDSCH based at least in part on the request indicated in the RACH message. The network may send the SIB1 PDSCH only on the beam used by the UE. By sending SIB1 PDSCH only on the beam used by the UE (as compared to repeating SIB1 on all beams in the beam), the SIB1 PDSCH overhead can be reduced from consuming 4.6% of the available downlink resources to consuming 0.1% of the available downlink resources. In addition, the initial access overhead can be reduced from consuming 7% of the total available downlink resources to consuming 2.5% of the total available downlink resources.

[0077] In initial access supporting dedicated SIBs, some resources may be preconfigured or specified. For example, RACH resources that are usually indicated by SIB1 PDSCH may be preconfigured or specified because the RACH message may indicate a request for SIB1 PDSCH. In other words, the RACH message may appear before SIB1 PDSCH in time, so SIB1 may not indicate RACH resources, and instead, RACH resources may be preconfigured or specified.

[0078] As indicated above, Figure 4 are provided as examples. Other examples can be found in the Figure 4 The examples described are different.

[0079] Some techniques and apparatus described herein enable RAR to be provided together with RMSI in response to PRACH communication (e.g., in SIB1 PDSCH). For example, a UE may send a PRACH communication to a network node, which may trigger the network node to send both RAR and SIB1 PDSCH. RAR and SIB1 may be included in a single PDSCH communication or separate PDSCH communications, and in either case may be scheduled by a single DCI communication. Therefore, initial access overhead may be further reduced relative to RAR and SIB1 communications that are separately scheduled and communicated. The reduction in overhead may help save resources, including processing, networking, and power resources associated with a wireless network. In addition, initial access may be completed more quickly, resulting in less delay than may otherwise occur with separate RAR and SIB1 communications.

[0080] Figure 5 is a diagram illustrating an example 500 associated with a combined RAR and RMSI according to the present disclosure. Figure 5 As shown, SSB can be used to trigger PRACH and dedicated SIB1 including RMSI.

[0081] As shown by reference numeral 510, the network node may send and the UE may receive the SSB. For example, the SSB may be received during cell search, cell acquisition, beam management, and / or beam selection (e.g., as part of an initial network access procedure). The SSB may be sent periodically by a wireless node (e.g., the network node 110). In some aspects, the SSB may include resources carrying a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and / or a physical broadcast channel (PBCH).

[0082] As shown by reference numeral 520, the UE may send and the network node may receive PRACH communications. The PRACH communications may be sent based at least in part on the SSB, and the SSB may also serve as a dedicated SIB1 trigger. For example, the PRACH communications may include information indicating to the network node that a dedicated SIB1 and RAR are requested based at least in part on the PRACH communications. In some aspects, the resources used for the PRACH communications may be preconfigured and / or based at least in part on information included in the SSB.

[0083] In some aspects, a PRACH communication may be associated with an identifier such as a random access (RA) radio network temporary identifier (RA-RNTI), a system information (SI) RNTI (SI-RNTI), or a dedicated RNTI. For example, the identifier may be used to send and receive DCI associated with scheduling one or more PDSCH communications (e.g., SIB1 and / or RAR PDSCH communications) based on the PRACH communication. In this case, the network node receiving the PRACH communication may use the identifier to scramble the cyclic redundancy check bits of the DCI.

[0084] In some aspects, the UE may monitor downlink communications within a time window after sending a PRACH communication. For example, the UE may monitor DCI for scheduling SIB1 and / or RAR PDSCH communications within the time window. In some aspects, the time window may be based at least in part on information available to the UE and / or communicated with the UE. For example, the time window may be based at least in part on an SSB received from a network node (e.g., included in a master information block (MIB), RMSI, etc.), system information associated with a cell separate from the network node (e.g., associated with cell reselection), dedicated signaling from a cell separate from the network node, and / or a preconfigured time period, etc.

[0085] As indicated by reference numerals 530, 540, 550, and 560, the network node may send, and the UE may receive, RAR communications and SIB1 communications including the RMSI. As indicated, the RAR and SIB1 communications may be communicated in a variety of ways.

[0086] As indicated by reference numeral 530, the network node may send, and the UE may receive, a DCI that schedules a single PDSCH communication that includes both RAR information and SIB1 information. In this way, a PRACH communication may trigger a single DCI communication that may be used to specify resources for a single PDSCH to deliver both RAR information and SIB1 information.

[0087] As shown by reference numeral 540, the network node may send, and the UE may receive, a DCI that schedules a first PDSCH communication that includes a RAR communication and schedules a second PDSCH communication that includes a SIB1 communication (e.g., RMSI). In this way, a PRACH communication may trigger a single DCI communication that may be used to specify separate resources for a PDSCH communication that includes RAR information and SIB1 information.

[0088] As shown by reference numeral 550, the network node may transmit and the UE may receive a single PDSCH communication including both RAR information and SIB1 information. In this way, the PRACH communication may trigger the transmission of a single PDSCH to deliver both RAR information and SIB1 information. In some aspects, the resources used for the PDSCH may be pre-configured and / or indicated by the SSB.

[0089] As shown by reference numeral 560, the network node may send and the UE may receive a first PDSCH communication including a RAR communication and a second PDSCH communication including a SIB1 communication (e.g., RMSI). In this way, the PRACH communication may trigger the transmission of two PDSCH communications to deliver the RAR information and the SIB1 information. In some aspects, the resources used for the PDSCH may be pre-configured and / or indicated by the SSB.

[0090] In some aspects, the RAR (e.g., included in the RAR PDSCH communication and / or the combined SIB1 and RAR PDSCH communication) may indicate that the random access channel (RACH) contention resolution procedure was unsuccessful. In this case, the UE may resend the PRACH communication, but may assume that the dedicated SIB1 will or will not be resent. For example, the UE may resend the PRACH communication to the network node and reuse the information included in the SIB1 communication for subsequent communications with the network node. As another example, the UE may resend the PRACH communication and receive a new SIB1 communication including an updated RMSI for subsequent communications with the network node.

[0091] As indicated above, Figure 5 are provided as examples. Other examples can be found in the Figure 5 The examples described are different.

[0092] Figure 6 is a diagram illustrating an example process 600 performed, for example, by a UE in accordance with the present disclosure. Example process 600 is an example in which a UE (eg, UE 120) performs operations associated with combined RAR and RMSI.

[0093] like Figure 6 As shown, in some aspects, process 600 may include sending a PRACH communication to a network node (block 610). For example, a UE (e.g., using Figure 8 The communication manager 140 and / or the sending component 804 depicted in FIG. 8 may send a PRACH communication to a network node, as described above.

[0094] like Figure 6As further shown in FIG. 6 , in some aspects, process 600 may include receiving, from a network node and at least in part based on a PRACH communication, a RAR communication and a SIB1 communication including a RMSI (block 620). For example, a UE (e.g., using communication manager 140 and / or Figure 8 The receiving component 802 depicted in FIG. 8 may receive a RAR communication and a SIB1 communication including a RMSI from a network node and based at least in part on a PRACH communication, as described above.

[0095] Process 600 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0096] In a first aspect, process 600 includes receiving, from a network node and based at least in part on a PRACH communication, a DCI that schedules RAR communications in a first PDSCH communication and schedules SIB1 communications in a second PDSCH communication.

[0097] In a second aspect, alone or in combination with the first aspect, process 600 includes receiving, from a network node and based at least in part on a PRACH communication, a DCI that schedules RAR communication and SIB1 communication in a single PDSCH communication.

[0098] In a third aspect, alone or in combination with one or more of the first and second aspects, receiving the RAR communication and the SIB1 communication includes receiving the RAR communication in a first PDSCH communication and receiving the SIB1 communication in a second PDSCH communication.

[0099] In a fourth aspect, alone or in combination with one or more of the first to third aspects, receiving the RAR communication and the SIB1 communication includes receiving the RAR communication and the SIB1 communication in a single PDSCH communication.

[0100] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the PRACH communication is associated with one of a RA-RNTI, a SI-RNTI or a dedicated RNTI.

[0101] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the RAR indicates that RACH contention resolution is unsuccessful, and the process 600 includes sending a PRACH communication to a network node, and using information included in the SIB1 communication for subsequent communication with the network node.

[0102] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the RAR indicates that RACH contention resolution is unsuccessful, and the process 600 includes sending a PRACH communication to the network node, and receiving a new SIB1 communication from the network node including an updated RMSI for subsequent communications with the network node.

[0103] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, process 600 includes monitoring downlink control information within a time window after transmitting a PRACH communication.

[0104] In a ninth aspect, either alone or in combination with one or more of aspects 1 to 8, the time window is based at least in part on an SSB received from the network node, information associated with cell reselection and associated with a cell separate from the network node, dedicated signaling from a cell separate from the network node, or a preconfigured time period.

[0105] although Figure 6 An example block diagram of process 600 is shown, but in some aspects, process 600 may include Figure 6 The blocks depicted in the process 600 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 600. Additionally or alternatively, two or more blocks in the blocks of the process 600 may be performed in parallel.

[0106] Figure 7 is a diagram illustrating an example process 700 performed, for example, by a network node in accordance with the present disclosure. The example process 700 is an example in which a network node (eg, network node 110) performs operations associated with combined RAR and RMSI.

[0107] like Figure 7 As shown, in some aspects, process 700 may include receiving a PRACH communication from a UE (block 710). For example, a network node (e.g., using Fig. 9 The communication manager 150 and / or receiving component 902 depicted in FIG. 1 may receive PRACH communications from a UE, as described above.

[0108] like Figure 7 As further shown in FIG. 7 , in some aspects, process 700 may include sending a RAR communication and a SIB1 communication including a RMSI to a UE and based at least in part on a PRACH communication (block 720). For example, a network node (e.g., using Fig. 9 The communication manager 150 and / or the transmitting component 904 depicted in FIG. 1 may transmit the RAR communication and the SIB1 communication including the RMSI to the UE and based at least in part on the PRACH communication, as described above.

[0109] Process 700 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0110] In a first aspect, process 700 includes sending, to a UE and based at least in part on a PRACH communication, a DCI that schedules RAR communications in a first PDSCH communication and schedules SIB1 communications in a second PDSCH communication.

[0111] In a second aspect, alone or in combination with the first aspect, process 700 includes sending, to a UE and based at least in part on the PRACH communication, a DCI that schedules RAR communication and SIB1 communication in a single PDSCH communication.

[0112] In a third aspect, alone or in combination with one or more of the first and second aspects, transmitting the RAR communication and the SIB1 communication includes transmitting the RAR communication in a first PDSCH communication and transmitting the SIB1 communication in a second PDSCH communication.

[0113] In a fourth aspect, alone or in combination with one or more of the first to third aspects, transmitting the RAR communication and the SIB1 communication includes transmitting the RAR communication and the SIB1 communication in a single PDSCH communication.

[0114] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the PRACH communication is associated with one of a RA-RNTI, a SI-RNTI or a dedicated RNTI.

[0115] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the RAR indicates that RACH contention resolution is unsuccessful, and the process 700 includes sending a SIB1 communication to the UE.

[0116] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the RAR indicates that RACH contention resolution is unsuccessful, and the process 700 includes sending a new SIB1 communication including an updated RMSI for subsequent communications with the network node to the UE.

[0117] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, process 700 includes sending data to the UE and after sending the PRACH communication indicating a time window for the UE to monitor downlink control information.

[0118] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, sending data indicating the time window includes sending an SSB indicating the time window to the UE.

[0119] although Figure 7 An example block diagram of process 700 is shown, but in some aspects, process 700 may include Figure 7 The blocks depicted in the process 700 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 700. Additionally or alternatively, two or more blocks in the blocks of the process 700 may be performed in parallel.

[0120] In this way, initial access overhead can be further reduced relative to separately scheduled and communicated RAR and SIB1 communications. The reduction in overhead can help save resources, including processing, networking, and power resources associated with the wireless network. In addition, initial access can be completed faster, resulting in less delay that may otherwise occur with separate RAR and SIB1 communications.

[0121] Figure 8 800 is a diagram of an example apparatus 800 for wireless communication according to the present disclosure. Apparatus 800 may be a UE, or a UE may include apparatus 800. In some aspects, apparatus 800 includes a receiving component 802 and a transmitting component 804 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 800 may use receiving component 802 and transmitting component 804 to communicate with another apparatus 806 (such as a UE, a base station, or another wireless communication device). As further shown, apparatus 800 may include a communication manager 140. Communication manager 140 may include monitoring component 808, etc.

[0122] In some aspects, the apparatus 800 may be configured to perform the Figures 4 to 5 Additionally or alternatively, the apparatus 800 may be configured to perform one or more processes described herein, such as Figure 6 In some aspects, the apparatus 800 and / or Figure 8 One or more components shown may include a combination of Figure 2 Additionally or alternatively, Figure 8 One or more of the components shown in the figure may be combined with Figure 2 Additionally or alternatively, one or more components in the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and may be executed by a controller or processor to perform the function or operation of the component.

[0123] The receiving component 802 may receive communications from the apparatus 806, such as reference signals, control information, data communications, or a combination thereof. The receiving component 802 may provide the received communications to one or more other components of the apparatus 800. In some aspects, the receiving component 802 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding) on ​​the received communications and may provide the processed signals to one or more other components of the apparatus 800. In some aspects, the receiving component 802 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of a described UE.

[0124] The transmitting component 804 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 806. In some aspects, one or more other components of the device 800 may generate communications and may provide the generated communications to the transmitting component 804 for transmission to the device 806. In some aspects, the transmitting component 804 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 806. In some aspects, the transmitting component 804 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described UE. In some aspects, the transmit component 804 can be co-located with the receive component 802 in a transceiver.

[0125] Transmitting component 804 can transmit the PRACH communication to the network node.Receiving component 802 can receive the RAR communication and the SIB1 communication including the RMSI from the network node and based at least in part on the PRACH communication.

[0126] Receiving component 802 can receive, from a network node and based at least in part on the PRACH communication, a DCI that schedules RAR communication in a first PDSCH communication and schedules SIB1 communication in a second PDSCH communication.

[0127] Receiving component 802 can receive, from a network node and based at least in part on the PRACH communication, a DCI that schedules RAR communication and SIB1 communication in a single PDSCH communication.

[0128] Monitoring component 808 can monitor downlink control information within a time window after transmitting the PRACH communication.

[0129] Figure 8 The number and arrangement of components shown in the figure are provided as examples. In practice, there may be Figure 8 The components shown in the figure may include additional components, fewer components, different components, or components arranged in a different manner. Figure 8 Two or more components shown in the figure may be implemented in a single component, or Figure 8 The single component shown in can be implemented as multiple distributed components. Additionally or alternatively, Figure 8 The assembly of (one or more) components shown in the figure may perform the operations described as being performed by Figure 8 Another set of components shown in the figure performs one or more functions.

[0130] Fig. 9 900 is a diagram of an example apparatus 900 for wireless communication according to the present disclosure. Apparatus 900 may be a network node, or a network node may include apparatus 900. In some aspects, apparatus 900 includes a receiving component 902 and a transmitting component 904 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 900 may use receiving component 902 and transmitting component 904 to communicate with another apparatus 906 (such as a UE, a base station, or another wireless communication device). As further shown, apparatus 900 may include a communication manager 150. Communication manager 150 may include one or more other components for performing the operations described herein.

[0131] In some aspects, the apparatus 900 may be configured to perform the Figures 4 to 5 Additionally or alternatively, the apparatus 900 may be configured to perform one or more processes described herein, such as Figure 7 The process 700. In some aspects, Fig. 9 The apparatus 900 and / or one or more components shown in FIG. 1 may include a combination of Figure 2 Additionally or alternatively, Fig. 9 One or more of the components shown in the figure may be combined with Figure 2 Additionally or alternatively, one or more components in the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and may be executed by a controller or processor to perform the function or operation of the component.

[0132] The receiving component 902 may receive communications from the device 906, such as reference signals, control information, data communications, or a combination thereof. The receiving component 902 may provide the received communications to one or more other components of the device 900. In some aspects, the receiving component 902 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding) on ​​the received communications and may provide the processed signals to one or more other components of the device 900. In some aspects, the receiving component 902 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof, of the described network nodes.

[0133] Transmit component 904 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 906. In some aspects, one or more other components of device 900 may generate communications and may provide the generated communications to transmit component 904 for transmission to device 906. In some aspects, transmit component 904 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding) on ​​the generated communications and may transmit the processed signals to device 906. In some aspects, transmit component 904 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described network nodes. In some aspects, the transmit component 904 can be co-located with the receive component 902 in a transceiver.

[0134] Receiving component 902 can receive a PRACH communication from a UE. Transmitting component 904 can transmit a RAR communication and a SIB1 communication including the RMSI to the UE and based at least in part on the PRACH communication.

[0135] Transmitting component 904 can transmit, to the UE and based at least in part on the PRACH communication, a DCI that schedules RAR communication in the first PDSCH communication and schedules SIB1 communication in the second PDSCH communication.

[0136] Transmitting component 904 can transmit, to the UE and based at least in part on the PRACH communication, a DCI that schedules RAR communication and SIB1 communication in a single PDSCH communication.

[0137] Transmitting component 904 can transmit, to the UE and after transmitting the PRACH communication, data indicating a time window for the UE to monitor downlink control information.

[0138] Fig. 9 The number and arrangement of components shown in the figure are provided as examples. In practice, there may be Fig. 9 The components shown in the figure may include additional components, fewer components, different components, or components arranged in a different manner. Fig. 9 Two or more components shown in the figure may be implemented in a single component, or Fig. 9 The single component shown in can be implemented as multiple distributed components. Additionally or alternatively, Fig. 9 The assembly of (one or more) components shown in the figure may perform the operations described as being performed by Fig. 9 One or more functions performed by another collection of components shown in the figure.

[0139] The following provides an overview of some aspects of the disclosure:

[0140] Aspect 1: A method of wireless communication performed by a UE, comprising: sending a PRACH communication to a network node; and receiving a RAR communication and a SIB1 communication including a RMSI from the network node and based at least in part on the PRACH communication.

[0141] Aspect 2: The method according to aspect 1 further comprises: receiving DCI from the network node and based at least in part on the PRACH communication, the DCI scheduling the RAR communication in the first PDSCH communication and scheduling the SIB1 communication in the second PDSCH communication.

[0142] Aspect 3: The method according to aspect 1 further comprises: receiving DCI from the network node and based at least in part on the PRACH communication, the DCI scheduling the RAR communication and the SIB1 communication in a single PDSCH communication.

[0143] Aspect 4: The method according to aspect 1, wherein receiving the RAR communication and the SIB1 communication comprises: receiving the RAR communication in a first PDSCH communication; and receiving the SIB1 communication in a second PDSCH communication.

[0144] Aspect 5: The method according to aspect 1, wherein receiving the RAR communication and the SIB1 communication comprises: receiving the RAR communication and the SIB1 communication in a single PDSCH communication.

[0145] Aspect 6: The method according to aspect 1, wherein the PRACH communication is associated with one of the following: RA-RNTI, SI-RNTI or dedicated RNTI.

[0146] Aspect 7: A method according to aspect 1, wherein the RAR indicates that RACH contention resolution is unsuccessful; and wherein the method further comprises: resending the PRACH communication to the network node; and reusing information included in the SIB1 communication for subsequent communication with the network node.

[0147] Aspect 8: A method according to aspect 1, wherein the RAR indicates that RACH contention resolution is unsuccessful; and wherein the method further comprises: resending the PRACH communication to the network node; and receiving a new SIB1 communication from the network node including an updated RMSI for subsequent communication with the network node.

[0148] Aspect 9: The method according to aspect 1 further includes: monitoring downlink control information within a time window after sending the PRACH communication.

[0149] Aspect 10: A method according to Aspect 9, wherein the time window is based at least in part on: an SSB received from the network node, system information associated with cell reselection and associated with a cell separate from the network node, dedicated signaling from a cell separate from the network node, or a preconfigured time period.

[0150] Aspect 11: A method of wireless communication performed by a network node, comprising: receiving a PRACH communication from a UE; and sending a RAR communication and a SIB1 communication including a RMSI to the UE and based at least in part on the PRACH communication.

[0151] Aspect 12: The method according to aspect 11 further comprises: sending DCI to the UE and based at least in part on the PRACH communication, the DCI scheduling the RAR communication in the first PDSCH communication and scheduling the SIB1 communication in the second PDSCH communication.

[0152] Aspect 13: The method according to aspect 11 further comprises: sending DCI to the UE and based at least in part on the PRACH communication, the DCI scheduling the RAR communication and the SIB1 communication in a single PDSCH communication.

[0153] Aspect 14: The method according to aspect 11, wherein sending the RAR communication and the SIB1 communication comprises: sending the RAR communication in a first PDSCH communication; and sending the SIB1 communication in a second PDSCH communication.

[0154] Aspect 15: The method according to aspect 11, wherein sending the RAR communication and the SIB1 communication comprises: sending the RAR communication and the SIB1 communication in a single PDSCH communication.

[0155] Aspect 16: The method according to aspect 11, wherein the PRACH communication is associated with one of the following: a RA-RNTI, a SI-RNTI, or a dedicated RNTI.

[0156] Aspect 17: The method according to aspect 11, wherein the RAR indicates that RACH contention resolution is unsuccessful; and wherein the method further comprises: resending the SIB1 communication to the UE.

[0157] Aspect 18: The method according to aspect 11, wherein the RAR indicates that RACH contention resolution is unsuccessful; and wherein the method further comprises: sending a new SIB1 communication including an updated RMSI for subsequent communications with the network node to the UE.

[0158] Aspect 19: The method according to aspect 11 further comprises: sending data indicating a time window for the UE to monitor downlink control information after sending the PRACH communication.

[0159] Aspect 20: The method according to aspect 19, wherein sending the data indicating the time window includes: sending a synchronization signal block (SSB) indicating the time window to the UE.

[0160] Aspect 21: An apparatus for performing wireless communications at a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 1 to 10.

[0161] Aspect 22: An apparatus for wireless communication at a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 11 to 20.

[0162] Aspect 23: A device for wireless communication, comprising: a memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more of aspects 1 to 10.

[0163] Aspect 24: A device for wireless communication, comprising: a memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more of aspects 11 to 20.

[0164] Aspect 25: An apparatus for wireless communication, comprising: at least one component for performing the method according to one or more of aspects 1 to 10.

[0165] Aspect 26: An apparatus for wireless communication, comprising: at least one component for performing the method according to one or more of aspects 11 to 20.

[0166] Aspect 27: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 10.

[0167] Aspect 28: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 11 to 20.

[0168] Aspect 29: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising: one or more instructions, which, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 1 to 10.

[0169] Aspect 30: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising: one or more instructions, which, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 11 to 20.

[0170] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the various aspects.

[0171] As used herein, the term "component" is intended to be broadly interpreted as hardware, and / or a combination of hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures and / or functions, etc. As used herein, "processor" is implemented by a combination of hardware and / or hardware and software. It will be apparent that the system and / or method described herein can be implemented by a combination of hardware and / or hardware and software in different forms. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, the operation and behavior of the system and / or method are not described herein with reference to specific software codes, because it will be understood by those skilled in the art that software and hardware can be designed to implement the system and / or method based at least in part on the description herein.

[0172] As used herein, "satisfying a threshold" may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0173] Although the specific combination of features is set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner that is not specifically listed in the claims and / or is not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one of" the list of items refers to any combination of these items (which includes a single member). As an example, "at least one of a, b or c" is intended to cover a, b, c, a+b, a+c, b+c and a+b+c, and any combination with multiple identical elements (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c and c+c+c, or any other ordering of a, b and c).

[0174] Any element, action or instruction used herein should not be interpreted as key or necessary, unless clearly described as such. In addition, as used herein, the article "one" is intended to include one or more items, and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more items connected to the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items, and can be used interchangeably with "one or more". If only want to refer to a project, the phrase "only one" or similar terms will be used. In addition, as used herein, the terms "have", "have" etc. are intended to be open terms, which do not limit the elements they modify (for example, "elements with" A can also have B). In addition, the phrase "based on" is intended to represent "based at least in part", unless otherwise explicitly stated. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and may be used interchangeably with "and / or" unless expressly stated otherwise (eg, if used in conjunction with "either" or "only one of").

Claims

1. A user equipment (UE) for wireless communication, comprising: Memory; and one or more processors coupled to the memory and configured to: sending a physical random access channel (PRACH) communication to a network node; as well as A random access response (RAR) communication and a system information block 1 (SIB1) communication including remaining minimum system information (RMSI) are received from the network node and based at least in part on the PRACH communication.

2. The UE of claim 1, wherein the one or more processors are further configured to: Downlink control information (DCI) is received from the network node and based at least in part on the PRACH communication, the downlink control information (DCI) scheduling the RAR communication in a first physical downlink shared channel (PDSCH) communication and scheduling the SIB1 communication in a second PDSCH communication.

3. The UE of claim 1 , wherein the one or more processors are further configured to: Downlink control information (DCI) is received from the network node and based at least in part on the PRACH communication, the downlink control information (DCI) scheduling the RAR communication and the SIB1 communication in a single physical downlink shared channel (PDSCH) communication.

4. The UE of claim 1 , wherein to receive the RAR communication and the SIB1 communication, the one or more processors are configured to: receiving the RAR communication in a first physical downlink shared channel (PDSCH) communication; and The SIB1 communication is received in a second PDSCH communication.

5. The UE of claim 1 , wherein to receive the RAR communication and the SIB1 communication, the one or more processors are configured to: The RAR communication and the SIB1 communication are received in a single physical downlink shared channel (PDSCH) communication.

6. The UE of claim 1 , wherein the PRACH communication is associated with one of: Random Access (RA) Radio Network Temporary Identifier (RA-RNTI), System Information (SI) Radio Network Temporary Identifier (SI-RNTI), or Dedicated RNTI.

7. The UE of claim 1, wherein the RAR indicates that random access channel (RACH) contention resolution is unsuccessful; and wherein the one or more processors are further configured to: sending the PRACH communication to the network node; and The information included in the SIB1 communication is used for subsequent communications with the network node.

8. The UE of claim 1, wherein the RAR indicates that random access channel (RACH) contention resolution is unsuccessful; and wherein the one or more processors are further configured to: sending the PRACH communication to the network node; and A new SIB1 communication is received from the network node including an updated RMSI for subsequent communications with the network node.

9. The UE of claim 1, wherein the one or more processors are further configured to: Downlink control information is monitored within a time window after transmitting the PRACH communication.

10. The UE of claim 9, wherein the time window is based at least in part on: a synchronization signal block (SSB) received from said network node, system information associated with a cell separated from the network node and associated with cell reselection, dedicated signalling from a cell separate from the network node, or Preconfigured time period.

11. A network node for wireless communication, comprising: Memory; and one or more processors coupled to the memory and configured to: receiving a physical random access channel (PRACH) communication from a user equipment (UE); as well as A random access response (RAR) communication and a system information block 1 (SIB1) communication including remaining minimum system information (RMSI) are sent to the UE and based at least in part on the PRACH communication.

12. The network node of claim 11, wherein the one or more processors are further configured to: Downlink control information (DCI) is sent to the UE and based at least in part on the PRACH communication, the downlink control information (DCI) scheduling the RAR communication in a first physical downlink shared channel (PDSCH) communication and scheduling the SIB1 communication in a second PDSCH communication.

13. The network node of claim 11, wherein the one or more processors are further configured to: Downlink control information (DCI) is transmitted to the UE and based at least in part on the PRACH communication, the downlink control information (DCI) scheduling the RAR communication and the SIB1 communication in a single physical downlink shared channel (PDSCH) communication.

14. The network node of claim 11, wherein to send the RAR communication and the SIB1 communication, the one or more processors are configured to: transmitting the RAR communication in a first physical downlink shared channel (PDSCH) communication; and The SIB1 communication is sent in a second PDSCH communication.

15. The network node of claim 11, wherein to send the RAR communication and the SIB1 communication, the one or more processors are configured to: The RAR communication and the SIB1 communication are transmitted in a single physical downlink shared channel (PDSCH) communication.

16. The network node of claim 11, wherein the PRACH communication is associated with one of: Random Access (RA) Radio Network Temporary Identifier (RA-RNTI), System Information (SI) Radio Network Temporary Identifier (SI-RNTI), or Dedicated RNTI.

17. The network node of claim 11, wherein the RAR indicates that random access channel (RACH) contention resolution was unsuccessful; and wherein the one or more processors are further configured to: The SIB1 communication is sent to the UE.

18. The network node of claim 11, wherein the RAR indicates that random access channel (RACH) contention resolution was unsuccessful; and wherein the one or more processors are further configured to: A new SIB1 communication including the updated RMSI for subsequent communications with the network node is sent to the UE.

19. The network node of claim 11, wherein the one or more processors are further configured to: Data indicating a time window for the UE to monitor downlink control information is sent to the UE and after sending the PRACH communication.

20. The network node of claim 19, wherein to send the data indicative of the time window, the one or more processors are configured to: A synchronization signal block (SSB) indicating the time window is sent to the UE.

21. A method of wireless communication performed by a user equipment (UE), comprising: sending a physical random access channel (PRACH) communication to a network node; as well as A random access response (RAR) communication and a system information block 1 (SIB1) communication including remaining minimum system information (RMSI) are received from the network node and based at least in part on the PRACH communication.

22. The method according to claim 21, further comprising: Downlink control information (DCI) is received from the network node and based at least in part on the PRACH communication, the downlink control information (DCI) scheduling the RAR communication in a first physical downlink shared channel (PDSCH) communication and scheduling the SIB1 communication in a second PDSCH communication.

23. The method according to claim 21, further comprising: Downlink control information (DCI) is received from the network node and based at least in part on the PRACH communication, the downlink control information (DCI) scheduling the RAR communication and the SIB1 communication in a single physical downlink shared channel (PDSCH) communication.

24. The method of claim 21 , wherein receiving the RAR communication and the SIB1 communication comprises: receiving the RAR communication in a first physical downlink shared channel (PDSCH) communication; as well as The SIB1 communication is received in a second PDSCH communication.

25. The method of claim 21, wherein receiving the RAR communication and the SIB1 communication comprises: The RAR communication and the SIB1 communication are received in a single physical downlink shared channel (PDSCH) communication.

26. A method of wireless communication performed by a network node, comprising: receiving a physical random access channel (PRACH) communication from a user equipment (UE); as well as A random access response (RAR) communication and a system information block 1 (SIB1) communication including remaining minimum system information (RMSI) are sent to the UE and based at least in part on the PRACH communication.

27. The method according to claim 26, further comprising: Downlink control information (DCI) is sent to the UE and based at least in part on the PRACH communication, the downlink control information (DCI) scheduling the RAR communication in a first physical downlink shared channel (PDSCH) communication and scheduling the SIB1 communication in a second PDSCH communication.

28. The method of claim 26, further comprising: Downlink control information (DCI) is transmitted to the UE and based at least in part on the PRACH communication, the downlink control information (DCI) scheduling the RAR communication and the SIB1 communication in a single physical downlink shared channel (PDSCH) communication.

29. The method of claim 26, wherein sending the RAR communication and the SIB1 communication comprises: sending the RAR communication in a first physical downlink shared channel (PDSCH) communication; as well as The SIB1 communication is sent in a second PDSCH communication.

30. The method of claim 26, wherein sending the RAR communication and the SIB1 communication comprises: The RAR communication and the SIB1 communication are transmitted in a single physical downlink shared channel (PDSCH) communication.

Images