Message 2 or Message B with PDCCH inside PDSCH resources

By mapping PDCCH to PDSCH resources during the RACH process, the problem of insufficient PDCCH coverage in the 5G NR system is solved, the communication support capability of the base station to user equipment is improved, and the access performance is enhanced.

CN115316037BActive Publication Date: 2024-11-01QUALCOMM INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202180023960.8
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2021-03-29
Filing Date
2021-03-30
Publication Date
2024-11-01
Estimated Expiration
2041-03-30

AI Technical Summary

Technical Problem

In the existing 5G NR system, the PDCCH coverage of Message2 or MessageB is limited, resulting in insufficient coverage of PDCCH by the base station during the RACH process, which affects the communication quality and the access performance of user equipment.

Method used

During the RACH process, the base station configures the RAR message so that it includes the PDCCH on the PDSCH resource to increase the coverage range and transmission energy of the PDCCH, thereby improving the coverage effect of the PDCCH.

Benefits of technology

By mapping the PDCCH resources to the PDSCH resources, the time for the base station to send PDCCH during the RACH process is extended, the coverage range and access performance of the PDCCH are improved, and the communication support capability for user equipment is enhanced.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115316037B_ABST
    Figure CN115316037B_ABST
Patent Text Reader

Abstract

A configuration that allows a base station to improve coverage for a PDCCH during a RACH process. An apparatus receives a preamble from a UE to initiate a RACH process. The apparatus sends a RAR to the UE in response to receiving the preamble. The RAR includes a PDCCH on a PDSCH resource.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. Provisional Application No. 63 / 005,033, filed on April 3, 2020, entitled “Message2 or MessageB withPDCCH Inside PDSCH Resources,” and U.S. Patent Application No. 17 / 215,693, filed on March 29, 2021, entitled “Message2 or MessageB with PDCCH Inside PDSCH Resources,” the entire contents of which are incorporated herein by reference. Technical Field

[0003] The present disclosure relates generally to communication systems and, more particularly, to random access channel (RACH) procedures. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcast. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.

[0005] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at a city, country, region, and even global level. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continuous mobile broadband evolution released by the Third Generation Partnership (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., together with the Internet of Things (IoT)) and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable low latency communication (URLLC). Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. There is a need for further improvement of 5GNR technology. These improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the invention

[0006] A brief summary of one or more aspects is given below to provide a basic understanding of such aspects. This summary is not an extensive overview of all expected aspects, and is neither intended to identify the key or important elements of all aspects, nor to delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to a more detailed description that will be given later.

[0007] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be a device at a base station. The apparatus may be a processor and / or a modem at a base station or the base station itself. The apparatus receives a preamble from a user equipment (UE) to initiate a random access channel (RACH) procedure. The apparatus, in response to receiving the preamble, sends a random access response (RAR) to the UE, wherein the RAR includes a physical downlink control channel (PDCCH) on a physical downlink shared channel (PDSCH) resource.

[0008] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be a device at a UE. The apparatus may be a processor and / or a modem at the UE or the UE itself. The apparatus sends a preamble to a base station to initiate a random access channel (RACH) procedure. The apparatus receives a random access response (RAR) from the base station in response to the sent preamble, wherein the RAR includes a physical downlink control channel (PDCCH) on a physical downlink shared channel (PDSCH) resource.

[0009] To accomplish the foregoing and related purposes, one or more aspects include the features fully described below and particularly pointed out in the claims. The following description and drawings set forth in detail certain illustrative features of one or more aspects. However, these features are indicative of only some of the various ways in which the principles of the various aspects may be employed, and this specification is intended to include all such aspects and their equivalents. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

[0012] Figure 2B is a diagram illustrating an example of DL channels within a subframe according to various aspects of the present disclosure.

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

[0014] Figure 2D is a diagram illustrating an example of UL channels within a subframe according to various aspects of the present disclosure.

[0015] Figure 3 is a schematic diagram showing an example of a base station and a user equipment (UE) in an access network.

[0016] Figure 4 is a call flow diagram showing signaling between a UE and a base station.

[0017] Figure 5 is a flow chart of a method of wireless communication.

[0018] Figure 6 is a schematic diagram showing an example of a hardware implementation for an exemplary apparatus.

[0019] Figure 7 is a flow chart of a method of wireless communication.

[0020] Figure 8 is a schematic diagram showing an example of a hardware implementation for an exemplary apparatus. DETAILED DESCRIPTION

[0021] The detailed description set forth below in conjunction with the accompanying drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for providing a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts may be implemented without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0022] Several aspects of telecommunication systems will now be presented with reference to various devices and methods. These devices and methods will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using electronic hardware, computer software, or any 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.

[0023] By way of example, an element, or any part of an element, or any combination of elements can be implemented as a "processing system" including one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gating logic, discrete hardware circuits, and other suitable hardware configured to perform various functions described throughout the present disclosure. One or more processors in a processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other, software should be broadly interpreted as instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, processes, functions, etc.

[0024] Therefore, in one or more exemplary embodiments, the functions described can be implemented in hardware, software, or any combination thereof. If implemented in software, the functions can be stored or encoded as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media. Storage media can be any available media that can be accessed by a computer. By way of example and not limitation, such computer-readable media can include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, or a combination of computer-readable media of the above type, or can be used to store any other medium with executable code in the form of instructions or data structures that can be accessed by a computer.

[0025] Figure 1 1 is a schematic diagram showing an example of a wireless communication system and access network 100. The wireless communication system (also referred to as a wireless wide area network (WWAN)) includes a base station 102, a UE 104, an evolved packet core (EPC) 160, and another core network 190 (e.g., a 5G core (5GC)). The base station 102 may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). A macro cell includes a base station. A small cell includes a femto cell, a pico cell, and a micro cell.

[0026] The base station 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can interface with the EPC 160 via a first backhaul link 132 (e.g., S1 interface). The base station 102 configured for 5G NR (collectively referred to as Next Generation RAN (NG-RAN)) can interface with the core network 190 via a second backhaul link 184. Among other functions, the base station 102 can perform one or more of the following functions: transmission of user data, wireless channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection setup and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), user and device tracking, RAN information management (RIM), paging, positioning, and delivery of warning messages. The base stations 102 may communicate with each other directly or indirectly (eg, through the EPC 160 or the core network 190) over a third backhaul link 134 (eg, an X2 interface). The first backhaul link 132, the second backhaul link 184, and the third backhaul link 134 may be wired or wireless.

[0027] Base station 102 can communicate wirelessly with UE 104. Each base station 102 can provide communication coverage for a respective geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, a small cell 102' may have a coverage area 110' that overlaps with the coverage area 110 of one or more macro base stations 102. A network including small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a home evolved Node B (eNB) (HeNB), which may provide services to a restricted group referred to as a closed subscriber group (CSG). The communication link 120 between base station 102 and UE 104 may include an uplink (UL) (also referred to as a reverse link) transmission from UE 104 to base station 102 and / or a downlink (DL) (also referred to as a forward link) transmission from base station 102 to UE 104. The communication link 120 may use multiple input multiple output (MIMO) antenna technology, including spatial multiplexing, beamforming and / or transmit diversity. The communication link may be through one or more carriers. In each carrier allocated in the carrier aggregation, the base station 102 / UE 104 can use up to Y MHz (e.g., 5, 10, 15, 20, 100, 400, etc. MHz) of spectrum bandwidth, and up to a total of Yx MHZ (x component carriers) of carrier aggregation for transmission in each direction. The carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL ​​compared to UL). The component carrier may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell), and the secondary component carrier may be referred to as a secondary cell (SCell).

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

[0029] The wireless communication system may also include a Wi-Fi access point (AP) 150 that communicates with a Wi-Fi station (STA) 152 via a communication link 154, for example, in a 5 GHz unlicensed spectrum. When communicating in an unlicensed spectrum, the STA 152 / AP 150 may perform a clear channel assessment (CCA) prior to communication to determine whether a channel is available.

[0030] The small cell 102' may operate in a licensed and / or unlicensed spectrum. When operating in an unlicensed spectrum, the small cell 102' may employ NR and use the same unlicensed spectrum (e.g., 5 GHz, etc.) as used by the Wi-Fi AP 150. The small cell 102' employing NR in the unlicensed spectrum may improve the coverage of the access network and / or increase the capacity of the access network.

[0031] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency ranges referred to as FR1 (410 MHz–7.125 GHz) and FR2 (24.25 GHz–52.6 GHz). Frequencies between FR1 and FR2 are typically referred to as mid-band frequencies. Although a portion of FR1 is greater than 6 GHz, FR1 is typically referred to (interchangeably) as a “sub-6 GHz” band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is typically referred to (interchangeably) as a “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as a “millimeter wave” band by the International Telecommunication Union (ITU).

[0032] In view of the above, unless otherwise explicitly stated, it should be understood that if the term "sub-6 GHz" or the like is used herein, the term can broadly refer to frequencies that may be lower than 6 GHz, may be within FR1, or may include mid-band frequencies. Similarly, unless otherwise explicitly stated, it should be understood that if the term "millimeter wave" or the like is used herein, the term can broadly refer to frequencies that may include mid-band frequencies, may be within FR2, or may be within the EHF band.

[0033] The base station 102 (whether a small cell 102' or a large cell (e.g., a macro base station)) may include and / or be referred to as an eNB, a gNodeB (gNB), or another type of base station. Some base stations (e.g., gNB 180) may operate in traditional sub-6 GHz spectrum, millimeter wave frequencies, and / or near millimeter wave frequencies to communicate with UE 104. When the gNB 180 operates in millimeter wave or near millimeter wave frequencies, the gNB 180 may be referred to as a millimeter wave base station. The millimeter wave base station 180 may utilize beamforming 182 with the UE 104 to compensate for path loss and short range. The base station 180 and the UE 104 may each include multiple antennas, such as antenna elements, antenna panels, and / or antenna arrays, to facilitate beamforming.

[0034] The base station 180 may send beamformed signals in one or more transmit directions 182' to the UE 104. The UE 104 may receive beamformed signals from the base station 180 in one or more receive directions 182". The UE 104 may also send beamformed signals to the base station 180 in one or more transmit directions. The base station 180 may receive beamformed signals from the UE 104 in one or more receive directions. The base station 180 / UE 104 may perform beam training to determine the best receive and transmit directions for each of the base station 180 / UE 104. The transmit and receive directions for the base station 180 may be the same, or may not be the same. The transmit and receive directions for the UE 104 may be the same, or may not be the same.

[0035] The EPC 160 may include a mobility management entity (MME) 162, other MMEs 164, a serving gateway 166, a multimedia broadcast multicast service (MBMS) gateway 168, a broadcast multicast service center (BM-SC) 170, and a packet data network (PDN) gateway 172. The MME 162 may communicate with a home subscriber server (HSS) 174. The MME 162 is a control node that handles signaling between the UE 104 and the EPC 160. Typically, the MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are transmitted through the serving gateway 166, which itself is connected to the PDN gateway 172. The PDN gateway 172 provides UE IP address allocation and other functions. The PDN gateway 172 and the BM-SC 170 are connected to IP services 176. The IP services 176 may include the Internet, an intranet, an IP multimedia subsystem (IMS), a PS streaming service, and / or other IP services. The BM-SC 170 may provide functionality for MBMS user service provisioning and delivery. The BM-SC 170 may serve as an entry point for content provider MBMS transmissions, may be used to authorize and initiate MBMS bearer services within a public land mobile network (PLMN), and may be used to schedule MBMS transmissions. The MBMS Gateway 168 may be used to distribute MBMS services to base stations 102 belonging to a multicast broadcast single frequency network (MBSFN) area that broadcasts specific services, and may be responsible for session management (start / stop) and collecting eMBMS-related billing information.

[0036] The core network 190 may include an access and mobility management function (AMF) 192, other AMFs 193, a session management function (SMF) 194, and a user plane function (UPF) 195. The AMF 192 may communicate with a unified data management (HSS) 196. The AMF 192 is a control node that handles signaling between the UE 104 and the core network 190. Typically, the AMF 192 provides QoS flow and session management. All user Internet Protocol (IP) packets are transmitted through the UPF 195. The UPF 195 provides UE IP address allocation and other functions. The UPF 195 is connected to an IP service 197. The IP service 197 may include the Internet, an intranet, an IP multimedia subsystem (IMS), a packet switched (PS) streaming (PSS) service, and / or other IP services.

[0037] A base station may include and / or be referred to as a gNB, a Node B, an eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmit receive point (TRP), or some other suitable term. Base station 102 provides an access point to EPC 160 or core network 190 for UE 104. Examples of UE 104 include a cellular phone, a smart phone, a Session Initiation Protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., an MP3 player), a camera, a game console, a tablet computer, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor / actuator, a display, or any other similar functional device. Some of UE 104 may be referred to as IoT devices (e.g., a parking meter, a gas pump, a toaster, a vehicle, a heart monitor, etc.). UE 104 may also be referred to as a station, a mobile station, a user station, a mobile unit, a user unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile user station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology.

[0038] Reference again Figure 1 In some aspects, the UE 104 may be configured to receive a RAR message including a PDCCH on a PDSCH resource. For example, the UE 104 may include a RAR component 198 configured to receive a RAR message including a PDCCH on a PDSCH resource. The UE 104 sends a preamble to the base station 180 to initiate a RACH procedure. The UE 104 receives a RAR from the base station 180 in response to the sent preamble. The RAR includes a PDCCH on a PHSCH resource.

[0039] Reference again Figure 1 In certain aspects, the base station 180 may be configured to send a RAR message to the UE 104 in response to receiving a preamble, wherein the RAR message includes a PDCCH on a PDSCH resource. For example, the base station 180 may include a RAR component 199 configured to send a RAR message to the UE 104 in response to receiving a preamble, wherein the RAR message includes a PDCCH on a PDSCH resource. The base station 180 receives a preamble from the UE 104 to initiate a RACH procedure. The base station 180 sends a RAR to the UE 104 in response to receiving the preamble, wherein the RAR includes a PDCCH on a PDSCH resource.

[0040] Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar areas, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

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

[0042] Other wireless communication technologies may have different frame structures and / or different channels. A frame (10ms) may be divided into 10 equally sized subframes (1ms). Each subframe may include one or more time slots. A subframe may also include microslots that may include 7, 4, or 2 symbols. Depending on the slot configuration, each time slot may include 7 or 14 symbols. For slot configuration 0, each time slot may include 14 symbols, and for slot configuration 1, each time slot may include 7 symbols. The symbols on the DL may be cyclic prefix (CP) orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbols. The symbols on the UL may be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbols (also known as single carrier frequency division multiple access (SC-FDMA) symbols) (for power-limited scenarios; limited to single stream transmission). The number of time slots within a subframe is based on the slot configuration and the digital scheme. For slot configuration 0, different digital schemes μ0 to 4 allow 1, 2, 4, 8 and 16 slots per subframe, respectively. For slot configuration 1, different digital schemes 0 to 2 allow 2, 4 and 8 slots per subframe, respectively. Therefore, for slot configuration 0 and digital scheme μ, there are 14 symbols / slot and 2μ slots / subframe. The subcarrier spacing and symbol length / duration are functions of the digital scheme. The subcarrier spacing can be equal to 2^μ*15kHz, where μ is digital scheme 0 to 4. Thus, digital scheme μ=0 has a subcarrier spacing of 15kHz, and digital scheme μ=4 has a subcarrier spacing of 240kHz. The symbol length / duration is inversely related to the subcarrier spacing. Figures 2A-2D An example of a slot configuration 0 with 14 symbols per slot and a digital scheme μ=2 with 4 slots per subframe is provided. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within a set of frames, there may be one or more different bandwidth parts (BWPs) frequency-division multiplexed (see Figure 2B ). Each BWP can have a specific numbering scheme.

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

[0044] like Figure 2AAs shown, some REs carry reference (pilot) signals (RS) for the UE. RSs may include demodulation RSs (DM-RSs) for channel estimation at the UE (indicated as R for one specific configuration, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RSs). RSs may also include beam measurement RSs (BRSs), beam refinement RSs (BRRSs), and phase tracking RSs (PT-RSs).

[0045] Figure 2B Examples of various DL channels within a subframe of a frame are shown. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE including six RE groups (REGs), each REG including 12 consecutive REs in an OFDM symbol of an RB. The PDCCH within a BWP may be referred to as a control resource set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., a common search space, a UE-specific search space) during a PDCCH monitoring opportunity on the CORESET, wherein the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at higher and / or lower frequencies across the channel bandwidth. The primary synchronization signal (PSS) may be within symbol 2 of a particular subframe of a frame. The PSS is used by UE 104 to determine subframe / symbol timing and physical layer identity. The secondary synchronization signal (SSS) may be within symbol 4 of a particular subframe of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and the radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the aforementioned DM-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also referred to as an SS block (SSB)). The MIB provides the number of RBs in the system bandwidth and the system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information that is not sent through the PBCH (e.g., the system information block (SIB)), and paging messages.

[0046] like Figure 2CAs shown in , some of the REs carry DM-RS for channel estimation at the base station (indicated as R for one specific configuration, but other DM-RS configurations are possible). The UE can send DM-RS for the physical uplink control channel (PUCCH) and DM-RS for the physical uplink shared channel (PUSCH). The PUSCH DM-RS can be sent in the first one or two symbols of the PUSCH. Depending on whether a short PUCCH or a long PUCCH is sent, and depending on the specific PUCCH format used, the PUCCH DM-RS can be sent in different configurations. The UE can send a sounding reference signal (SRS). The SRS can be sent in the last symbol of the subframe. The SRS can have a comb structure, and the UE can send the SRS on one of the comb structures. The SRS can be used by the base station for channel quality estimation to achieve frequency-dependent scheduling on the UL.

[0047] Figure 2D Examples of various UL channels within a subframe of a frame are shown. The PUCCH may be located as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicator (CQI), precoding matrix indicator (PMI), rank indicator (RI), and hybrid automatic repeat request (HARQ) acknowledgement (ACK) (HARQ-ACK) information (ACK / negative ACK (NACK)) feedback. The PUSCH carries data and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

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

[0049] The transmit (TX) processor 316 and the receive (RX) processor 370 implement layer 1 functions associated with various signal processing functions. Layer 1 including the physical (PHY) layer may include error detection on the transmission channel, forward error correction (FEC) encoding / decoding of the transmission channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 processes the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols can then be divided into parallel streams. Each stream can then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time domain and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to generate a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to generate multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine coding and modulation schemes and for spatial processing. Channel estimates may be derived from reference signals and / or channel condition feedback sent by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318TX. Each transmitter 318TX may modulate an RF carrier with a respective spatial stream for transmission.

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

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

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

[0053] Channel estimates derived by the channel estimator 358 from a reference signal or feedback transmitted by the base station 310 may be used by the TX processor 368 to select the appropriate coding and modulation schemes and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via separate transmitters 354TX. Each transmitter 354TX may modulate an RF carrier with a respective spatial stream for transmission.

[0054] UL transmissions are processed at the base station 310 in a manner similar to that described in conjunction with the receiver functionality at the UE 350. Each receiver 318RX receives a signal through its respective antenna 320. Each receiver 318RX recovers information modulated onto an RF carrier and provides the information to a RX processor 370.

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

[0056] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to perform Figure 1 198 related aspects.

[0057] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to perform Figure 1 199 related aspects.

[0058] Message 2 (Msg2) PDCCH may be a bottleneck for coverage of millimeter wave (mmW) 5G systems. The same coverage limitations may also be an issue for message B (msgB). The limited coverage of msg2 PDCCH may be due to the fact that msg2 PDCCH is sent in a control resource set (CORESET) and cannot be more than 3 symbols, and typically no more than 2 symbols. The limited coverage of msg2PDCCH may be due to the fact that the broadcast beam is wide and based on SSB beams, and may not have sufficient gain and / or coverage. The amount of energy that can be transmitted may be limited, and as a result of the limitation, the base station has a limited time to send msg2PDCCH, which may lead to coverage limitations. As such, there is a need to improve the coverage of msg2 or msgB.

[0059] Aspects provided herein provide a configuration that allows a base station to improve coverage for a PDCCH during a RACH process. For example, a base station may be configured to configure a RAR message (e.g., msg2 or msgB) such that the RAR message includes a PDCCH on a PDSCH resource. For example, a base station may configure a RAR message in response to receiving a preamble from a UE to initiate a RACH process. At least one advantage of the present disclosure is that coverage of a msg2 PDCCH may be increased by configuring msg2 to include a PDCCH on a PDSCH resource.

[0060] Figure 44 is a call flow chart 400 of signaling between UE 402 and base station 404. Base station 404 may be configured to provide at least one cell. UE 402 may be configured to communicate with base station 404. For example, in Figure 1 In the context of , base station 404 may correspond to base station 102 / 180, and accordingly, a cell may include a geographic coverage area 110 in which communication coverage is provided and / or a small cell 102' having a coverage area 110'. In addition, UE 402 may correspond to at least UE 104. In another example, in Figure 3 In the context of , base station 404 may correspond to base station 310, and UE 402 may correspond to UE 350. Optional aspects are shown with dashed lines.

[0061] like Figure 4 As shown in , UE 402 may send a preamble to initiate a RACH procedure. The UE may send a preamble to a base station 404 to initiate a RACH procedure. The base station 404 may receive a preamble from the UE 402 to initiate a RACH procedure. The RACH procedure may include a 2-step RACH procedure or a 4-step RACH procedure. In a 2-step RACH procedure, the preamble 406 may include MsgA. In a 4-step RACH procedure, the preamble 406 may include Msg1. In some aspects, for example, as shown at 408, the UE 402 may monitor a response from the base station 404. The UE 402 may monitor at least one RAR from the base station 404 during the RAR window.

[0062] In some aspects, the base station 404 may configure a RAR message in response to receiving a preamble from the UE 402, e.g., as shown at 409. The base station may configure the RAR message as Msg2 for a 4-step RACH procedure or MsgB for a 2-step RACH procedure. The RAR message may be configured to improve PDCCH coverage during the RACH procedure.

[0063] As shown at 410, the base station 404 may send a RAR (e.g., Msg2 or MsgB) in response to the reception of the preamble. The base station 404 may send the RAR to the UE 402 in response to receiving the preamble. The base station 404 may configure the RAR to include a PDCCH on a PDSCH resource. The base station 404 configures the RAR to include a PDCCH on a PDSCH resource, which helps improve PDCCH coverage during a RACH process. For example, configuring the RAR to include a PDCCH on a PDSCH resource may improve PDCCH coverage due to an increase in the amount of energy that can be sent by the base station during the RACH process. Including the RAR PDCCH as well as the PDSCH resource removes the RAR PDCCH sent in the CORESET, which increases the time that the base station can send the RAR PDCCH, thereby increasing the coverage of the RAR PDCCH. In some aspects, the PDCCH may at least partially schedule the PDSCH. In some aspects, the PDCCH may be encoded using low-density parity check (LDPC) coding. In some aspects, the cyclic redundancy check (CRC) of the RAR may follow the design or may be similar to the CRC and its size for the PDSCH. In some aspects, the content of the PDCCH and / or the content of the DCI may indicate RB allocation, modulation and coding scheme (MCS) and / or other parameters for the Msg2 PDSCH. In some aspects, the frequency domain resources or time domain resources for the RAR may be allocated based on the random access radio network temporary identifier (RA-RNTI) or the residual system information (RMSI). In this way, due to the RA-RNTI, the UE may know where to find the PDCCH. Based on the content of the DCI or PDCCH, the UE may know the RB allocation for the PDSCH. The time domain resource allocation for PDCCH and PDSCH may be the same. The time domain resource allocation for PDCCH may include a subset of the time domain resource allocation for PDSCH. In some aspects, the frequency domain resource allocation for PDCCH may be a subset of the frequency domain resource allocation for PDSCH. In some aspects, the frequency domain resource allocation for PDSCH may be based on at least one of DCI or frequency domain resource allocation for PDCCH. For example, both the base station and the UE may know the frequency domain resource allocation for Msg2 PDCCH, and may have some information of the frequency domain resource allocation for PDSCH, so that the UE may obtain supplementary information based on the content of DCI. In some aspects, the time domain resource allocation for PDSCH may be based on at least one of DCI or time domain resource allocation for PDCCH.

[0064] In some aspects, the UE may have multiple candidates for the msg2 PDCCH. In these aspects, based on the RA-RNTI, the UE may know that it has multiple candidates for the msg2 PDCCH. For example, the time domain resource allocation may be the same, but the multiple candidates may be in different frequencies and / or frequency bands. In some aspects, the multiple candidates may have different aggregation levels, and the RB allocations may also be different. The UE may perform blind detection and check the CRC to determine if the candidate is a valid PDCCH for the UE. The multiple candidates may also depend on the RACH timing and / or RA-RNTI.

[0065] In some aspects, for example, in a 4-step RACH procedure, the UE 402 may send an RRC connection request at 412 to the base station 404. The UE 402 may send an RRC connection request (e.g., Msg3) 412 in response to receiving an RAR (e.g., Msg2) 410 from the base station 404. Additionally, in a 4-step RACH procedure, the base station 404 may send an RRC connection reply (e.g., Msg4) at 414 in response to receiving an RRC connection request (e.g., Msg3) 412 from the UE 402.

[0066] Figure 5 5 is a flow chart of a method of wireless communication. The method may be performed by a base station or a component of a base station (e.g., base station 102 / 180, 404; apparatus 602; baseband unit 604, which may include memory 376 and may be the entire base station 310 or a component of base station 310, such as TX processor 316, RX processor 370 and / or controller / processor 375). One or more of the operations shown may be omitted, swapped, or performed simultaneously. Optional aspects are shown in dashed lines. The method may allow a base station to improve coverage of a PDCCH during a RACH process.

[0067] At 502, the base station may receive a preamble to initiate a RACH procedure. For example, 502 may be performed by the preamble component 640 of the apparatus 602. The base station may receive a preamble from the UE to initiate a RACH procedure. For example, referring to Figure 4 , the base station 404 receives a preamble 406 (eg, Msg1 or MsgA) from the UE 402 to initiate a RACH process.

[0068] In some aspects, the base station may configure the RAR message in response to receiving the preamble from the UE. For example, in response to receiving the preamble from the UE, configuring the RAR message may be performed by the RAR component 642 of the apparatus 602. The RAR message may be Msg2 of a 4-step RACH procedure or MsgB of a 2-step RACH procedure. For example, referring to Figure 4, the base station 404 may configure a RAR at 409 in response to receiving the preamble 406 from the UE 402. The RAR message may be configured to improve PDCCH coverage during a RACH procedure.

[0069] At 504, the base station may send a RAR in response to receiving the preamble. For example, 504 may be performed by the RAR component 642 of the apparatus 602. The base station may send a RAR to the UE in response to receiving the preamble. The base station may configure the RAR to include the PDCCH on the PDSCH resource. For example, referring to Figure 4 , the base station may send RAR 410 to UE 402 in response to receiving preamble 406. In some aspects, PDCCH at least partially schedules PDSCH. In some aspects, PDCCH may be encoded using low density parity check (LDPC) coding. In some aspects, the cyclic redundancy check (CRC) of RAR may be similar to the CRC for PDSCH. In some aspects, frequency domain resources or time domain resources for RAR may be allocated based on random access radio network temporary identifier (RA-RNTI). Time domain resource allocation for PDCCH and PDSCH may be the same. Time domain resource allocation for PDCCH may include a subset of time domain resource allocation for PDSCH. In some aspects, frequency domain resource allocation for PDCCH may be a subset of frequency domain resource allocation for PDSCH. In some aspects, frequency domain resource allocation for PDSCH may be based on at least one of DCI or frequency domain resource allocation for PDCCH. In some aspects, time domain resource allocation for PDSCH may be based on at least one of DCI or time domain resource allocation for PDCCH.

[0070] Figure 6600 is a schematic diagram showing an example of a hardware implementation for an apparatus 602. The apparatus 602 is a BS and includes a baseband unit 604. The baseband unit 604 can communicate with the UE 104 via a cellular RF transceiver 622. The baseband unit 604 may include a computer-readable medium / memory. The baseband unit 604 is responsible for general processing, including the execution of software stored on the computer-readable medium / memory. When executed by the baseband unit 604, the software causes the baseband unit 604 to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by the baseband unit 604 when executing the software. The baseband unit 604 also includes a receiving component 630, a communication manager 632, and a sending component 634. The communication manager 632 includes one or more of the components shown. The components within the communication manager 632 may be stored in a computer-readable medium / memory and / or configured as hardware within the baseband unit 604. The baseband unit 604 may be a component of the BS 310 and may include the memory 376 and / or at least one of the TX processor 316 , the RX processor 370 , and the controller / processor 375 .

[0071] The communication manager 632 includes a preamble component 640 that can receive a preamble to initiate a RACH procedure, for example, as described in conjunction with Figure 5 The communication manager 632 also includes a RAR component 642, which can send a RAR in response to receiving the preamble, for example, as described in conjunction with Figure 5 The 504 is described.

[0072] The device may include an additional component that performs the aforementioned Figure 5 Each block in the algorithm of the flowchart. Figure 5 Each block in the flowchart of can be performed by a component, and the device may include one or more of these components. The component can be one or more hardware components specifically configured to implement the process / algorithm, one or more hardware components implemented by a processor configured to execute the process / algorithm, one or more hardware components stored in a computer-readable medium for processor implementation, or some combination thereof.

[0073] In one configuration, the device 602 (and, specifically, the baseband unit 604) includes a unit for receiving a preamble from a UE to initiate a RACH process. The device includes a unit for configuring a RAR message in response to receiving a preamble from the UE. The device includes a unit for sending a RAR to the UE in response to receiving a preamble. The RAR includes a PDCCH on a PDSCH resource. The aforementioned unit may be one or more of the aforementioned components of the device 602 configured to perform the functions recited by the aforementioned units. As described above, the device 602 may include a TX processor 316, an RX processor 370, and a controller / processor 375. As such, in one configuration, the aforementioned unit may be a TX processor 316, an RX processor 370, and a controller / processor 375 configured to perform the functions recited by the aforementioned units.

[0074] Figure 7 700 is a flow chart of a method of wireless communication. The method may be performed by a UE or a component of a UE (e.g., UE 104, 402; apparatus 802; cellular baseband processor 804, which may include memory 360 and may be the entire UE 350 or a component of UE 350, such as TX processor 368, RX processor 356 and / or controller / processor 359). One or more of the operations shown may be omitted, swapped, or performed simultaneously. Optional aspects are shown with dashed lines. The method may allow a UE to receive a RAR message with improved coverage during a RACH procedure.

[0075] At 702, the UE may send a preamble to initiate a RACH procedure. For example, 702 may be performed by the preamble component 840 of the apparatus 802. The UE may send a preamble to a base station to initiate a RACH procedure. For example, referring to Figure 4 , UE 402 sends a preamble code 406 to base station 404.

[0076] In some aspects, the UE may monitor at least one RAR during the RAR window. For example, the monitoring of at least one RAR during the RAR window may be performed by the RAR component 842 of the apparatus 802. The UE may monitor at least one RAR from the base station during the RAR window. For example, referring to Figure 4 At 408, UE 402 may monitor at least one RAR from base station 404 during the RAR window.

[0077] At 704, the UE may receive a RAR in response to the transmitted preamble. For example, 704 may be performed by the RAR component 842 of the apparatus 802. The UE may receive a RAR from the base station in response to the transmitted preamble. The RAR may include a PDCCH on a PDSCH resource. For example, referring to Figure 4, UE 402 may receive RAR 410 with PDCCH resources on PDSCH from base station 404. In some aspects, PDCCH at least partially schedules PDSCH. In some aspects, LDPC coding may be used to encode PDCCH. In some aspects, the CRC of RAR may be similar to the CRC for PDSCH. In some aspects, frequency domain resources or time domain resources for RAR may be allocated based on RA-RNTI. Time domain resource allocation for PDCCH and PDSCH may be the same. Time domain resource allocation for PDCCH may include a subset of time domain resource allocation for PDSCH. In some aspects, frequency domain resource allocation for PDCCH may be a subset of frequency domain resource allocation for PDSCH. In some aspects, frequency domain resource allocation for PDSCH may be based on at least one of DCI or frequency domain resource allocation for PDCCH. In some aspects, time domain resource allocation for PDSCH may be based on at least one of DCI or time domain resource allocation for PDCCH.

[0078] Figure 88 is a schematic diagram 800 showing an example of a hardware implementation for an apparatus 802. The apparatus 802 is a UE and includes a cellular baseband processor 804 (also referred to as a modem) coupled to a cellular RF transceiver 822 and one or more subscriber identity modules (SIM) cards 820, an application processor 806 coupled to a secure digital (SD) card 808 and a screen 810, a Bluetooth module 812, a wireless local area network (WLAN) module 814, a global positioning system (GPS) module 816, and a power supply 818. The cellular baseband processor 804 communicates with the UE 104 and / or the BS 102 / 180 through the cellular RF transceiver 822. The cellular baseband processor 804 may include a computer-readable medium / memory. The computer-readable medium / memory may be non-transitory. The cellular baseband processor 804 is responsible for general processing, including the execution of software stored on the computer-readable medium / memory. When executed by the cellular baseband processor 804, the software causes the cellular baseband processor 804 to perform the various functions described above. The computer-readable medium / memory may also be used to store data that is manipulated by the cellular baseband processor 804 when executing software. The cellular baseband processor 804 also includes a receiving component 830, a communication manager 832, and a transmitting component 834. The communication manager 832 includes one or more of the components shown. The components within the communication manager 832 may be stored in a computer-readable medium / memory and / or configured as hardware within the cellular baseband processor 804. The cellular baseband processor 804 may be a component of the UE 350 and may include a memory 360 and / or at least one of a TX processor 368, an RX processor 356, and a controller / processor 359. In one configuration, the device 802 may be a modem chip and include only the cellular baseband processor 804, while in another configuration, the device 802 may be the entire UE (e.g., see Figure 3 350), and includes the above-mentioned additional modules of device 802.

[0079] The communication manager 832 includes a preamble component 840 configured to send a preamble to initiate a RACH procedure, for example, as described in conjunction with Figure 7 The communication manager 832 also includes a RAR component 842, which is configured to receive a RAR in response to the transmitted preamble, for example, as described in conjunction with Figure 7 704. The RAR component 842 may be configured to monitor at least one RAR during a RAR window, for example, as described in conjunction with Figure 7 as described.

[0080] The device may include additional components that perform the aforementioned Figure 7 The process Figure 7Each box in the algorithm in the box. So, the above Figure 7 The process Figure 7 Each block in the process / algorithm may be performed by a component, and the device may include one or more of these components. The component may be one or more hardware components specifically configured to implement the process / algorithm, one or more hardware components implemented by a processor configured to execute the process / algorithm, one or more hardware components stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0081] In one configuration, the device 802 (and, in particular, the cellular baseband processor 804) includes a unit for sending a preamble to a base station to initiate a RACH process. The device includes a unit for receiving a RAR from a base station in response to the sent preamble, wherein the RAR includes a PDCCH on a PDSCH resource. The device also includes a unit for monitoring at least one RAR during a RAR window. The aforementioned unit may be one or more of the aforementioned components of the device 802 configured to perform the functions recited by the aforementioned units. As described above, the device 802 may include a TX processor 368, an RX processor 356, and a controller / processor 359. As such, in one configuration, the aforementioned unit may be a TX processor 368, an RX processor 356, and a controller / processor 359 configured to perform the functions recited by the aforementioned units.

[0082] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is an illustration of an exemplary method. Based on design preferences, it is understood that the specific order or hierarchy of the blocks in the process / flowchart can be rearranged. In addition, some blocks can be combined or omitted. The attached method claims present the elements of each block in a sample order and are not intended to be limited to the specific order or hierarchy presented.

[0083] The following examples are merely illustrative and may be combined with other embodiments or aspects of the teachings described herein without limitation.

[0084] Aspect 1 is a method of wireless communication at a base station, comprising: receiving a preamble from a UE to initiate a RACH process; and sending a RAR to the UE in response to receiving the preamble, wherein the RAR includes a PDCCH on a PDSCH resource.

[0085] In aspect 2, the method according to aspect 1 further includes the PDCCH at least partially scheduling the PDSCH.

[0086] In aspect 3, the method according to aspect 1 or 2 further includes that the PDCCH is encoded using LDPC coding.

[0087] In aspect 4, the method according to any one of aspects 1-3 further includes: the CRC of the RAR is similar to the CRC for the PDSCH.

[0088] In aspect 5, the method according to any one of aspects 1-4 further includes that the frequency domain resources or time domain resources used for the RAR are allocated based on RA-RNTI.

[0089] In aspect 6, the method according to any one of aspects 1-5 further includes that time domain resource allocation for the PDCCH and PDSCH is the same.

[0090] In aspect 7, the method according to any one of aspects 1-6 further includes that the time domain resource allocation for the PDCCH includes a subset of the time domain resource allocation for the PDSCH.

[0091] In aspect 8, the method according to any one of aspects 1-7 further includes that the frequency domain resource allocation for the PDCCH is a subset of the frequency domain resource allocation for the PDSCH.

[0092] In aspect 9, the method according to any one of aspects 1-8 further includes that the frequency domain resource allocation for the PDSCH is based on at least one of DCI or the frequency domain resource allocation for the PDCCH.

[0093] In aspect 10, the method according to any one of aspects 1-9 further includes that the time domain resource allocation for the PDSCH is based on at least one of downlink control information (DCI) or the time domain resource allocation for the PDCCH.

[0094] Aspect 11 is a device, comprising: one or more processors; and one or more memories, the one or more memories being in electronic communication with the one or more processors and storing instructions, the instructions being executable by the one or more processors to enable the device to implement a method according to any one of Aspects 1-10.

[0095] Aspect 12 is a system or an apparatus, comprising a unit for implementing the method according to any one of aspects 1-10 or implementing the apparatus according to any one of aspects 1-10.

[0096] Aspect 13 is a non-transitory computer-readable storage medium storing instructions executable by one or more processors to cause the one or more processors to implement the method according to any one of aspects 1-10.

[0097] Aspect 14 is a method of wireless communication at a UE, comprising: sending a preamble to a base station to initiate a RACH process; and receiving a RAR from the base station in response to the sent preamble, wherein the RAR includes a PDCCH on a PDSCH resource.

[0098] In aspect 15, the method according to aspect 14 further includes the PDCCH at least partially scheduling the PDSCH.

[0099] In aspect 16, the method according to aspect 14 or 15 further includes that the PDCCH is encoded using LDPC coding.

[0100] In aspect 17, the method according to any one of aspects 14-16 further includes that the CRC of the RAR is similar to the CRC for the PDSCH.

[0101] In aspect 18, the method according to any one of aspects 14-17 further includes that the frequency domain resources or time domain resources for the RAR are allocated based on RA-RNTI.

[0102] In aspect 19, the method according to any one of aspects 14-18 further includes that the time domain resource allocation for the PDCCH and PDSCH is the same.

[0103] In aspect 20, the method according to any one of aspects 14-19 further includes the time domain resource allocation for the PDCCH comprising a subset of the time domain resource allocation for the PDSCH.

[0104] In aspect 21, the method according to any one of aspects 14-20 further includes that the frequency domain resource allocation for the PDCCH is a subset of the frequency domain resource allocation for the PDSCH.

[0105] In aspect 22, the method according to any one of aspects 14-21 further includes that the frequency domain resource allocation for the PDSCH is based on at least one of DCI or the frequency domain resource allocation for the PDCCH.

[0106] In aspect 23, the method according to any one of aspects 14-22 further includes that the time domain resource allocation for the PDSCH is based on at least one of DCI or the time domain resource allocation for the PDCCH.

[0107] Aspect 24 is a device, comprising: one or more processors; and one or more memories, the one or more memories being in electronic communication with the one or more processors and storing instructions, the instructions being executable by the one or more processors to enable the device to implement a method according to any one of Aspects 14-23.

[0108] Aspect 25 is a system or an apparatus, comprising a unit for implementing the method according to any one of aspects 14-23 or implementing the apparatus according to any one of aspects 14-23.

[0109] Aspect 26 is a non-transitory computer-readable storage medium storing instructions executable by one or more processors to cause the one or more processors to implement the method according to any one of aspects 14-23.

[0110] The above description is provided so that any person skilled in the art can implement the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but should be given the full scope consistent with the language claims, wherein, unless specifically stated otherwise, reference to elements in the singular form is not intended to mean "one and only one", but "one or more". Terms such as "if", "when" and "while" should be interpreted as meaning "under ... conditions", rather than implying a direct temporal relationship or reaction. That is, these phrases (such as "when") do not mean immediate action in response to the occurrence of an action or during the occurrence of an action, but simply mean that if the condition is met, the action will occur, but no specific or immediate time limit is required for the occurrence of the action. The word "exemplary" is used herein to mean "used as an example, instance or illustration". Any aspect described as "exemplary" herein is not necessarily interpreted as being more preferred or more advantageous than other aspects. Unless otherwise expressly stated, the term "some" refers to one or more. Combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof” include any combination of A, B, and / or C, and may include multiples of A, multiples of B, or multiples of C. Specifically, combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof” may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, wherein any such combination may include one or more members of A, B, or C. All structural and functional equivalents to the elements of the various aspects described throughout the disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be covered by the claims. In addition, nothing disclosed herein is dedicated to the public, regardless of whether such disclosure is explicitly stated in the claims. The words "module," "mechanism," "element," "device," etc. may not be a substitute for the word "unit." Thus, no claim element is to be interpreted as a unit-plus-function unless the element is explicitly stated using the phrase "unit for..."

Claims

1. A method of wireless communication at a base station, comprising: receiving a preamble from a user equipment (UE) to initiate a random access channel (RACH) procedure; as well as In response to receiving the preamble, a random access response (RAR) is sent to the UE, wherein the RAR includes a physical downlink control channel (PDCCH) on a physical downlink shared channel (PDSCH) resource, and wherein a cyclic redundancy check (CRC) of the RAR includes a configuration based on a configuration and size of a CRC for the PDSCH.

2. The method according to claim 1, wherein: The PDCCH at least partially schedules the PDSCH.

3. The method according to claim 1, wherein: The PDCCH is encoded using low-density parity check (LDPC) coding.

4. The method according to claim 1, wherein: The frequency domain resources or time domain resources used for the RAR are allocated based on a random access radio network temporary identifier (RA-RNTI).

5. The method according to claim 4, wherein: The time domain resource allocation for the PDCCH and PDSCH is the same.

6. The method according to claim 4, wherein: The time domain resource allocation for the PDCCH includes a subset of the time domain resource allocation for the PDSCH.

7. The method according to claim 4, wherein: The frequency domain resource allocation for the PDCCH is a subset of the frequency domain resource allocation for the PDSCH.

8. The method according to claim 4, wherein: The frequency domain resource allocation for the PDSCH is based on at least one of downlink control information (DCI) or the frequency domain resource allocation for the PDCCH.

9. The method according to claim 4, wherein: The time domain resource allocation for the PDSCH is based on at least one of downlink control information (DCI) or the time domain resource allocation for the PDCCH.

10. An apparatus for wireless communication at a base station, comprising: Memory; as well as at least one processor coupled to the memory and configured to: receiving a preamble from a user equipment (UE) to initiate a random access channel (RACH) procedure; as well as In response to receiving the preamble, a random access response (RAR) is sent to the UE, wherein the RAR includes a physical downlink control channel (PDCCH) on a physical downlink shared channel (PDSCH) resource, and wherein a cyclic redundancy check (CRC) of the RAR includes a configuration based on a configuration and size of a CRC for the PDSCH.

11. The device according to claim 10, wherein: The PDCCH at least partially schedules the PDSCH.

12. The device according to claim 10, wherein: The frequency domain resources or time domain resources used for the RAR are allocated based on a random access radio network temporary identifier (RA-RNTI).

13. The device according to claim 12, wherein: The time domain resource allocation for the PDCCH and the PDSCH is the same, wherein the time domain resource allocation for the PDCCH includes a subset of the time domain resource allocation for the PDSCH.

14. The device according to claim 12, wherein: The frequency domain resource allocation for the PDCCH is a subset of the frequency domain resource allocation for the PDSCH, wherein the frequency domain resource allocation for the PDSCH is based on at least one of downlink control information (DCI) or the frequency domain resource allocation for the PDCCH.

15. A method of wireless communication at a user equipment (UE), comprising: Sending a preamble to the base station to initiate a random access channel (RACH) procedure; as well as In response to the transmitted preamble, a random access response (RAR) is received from the base station, wherein the RAR includes a physical downlink control channel (PDCCH) on a physical downlink shared channel (PDSCH) resource, and wherein a cyclic redundancy check (CRC) of the RAR includes a configuration based on a configuration and size of a CRC for the PDSCH.

16. The method according to claim 15, wherein: The PDCCH at least partially schedules the PDSCH.

17. The method according to claim 15, wherein: The PDCCH is encoded using low-density parity check (LDPC) coding.

18. The method according to claim 15, wherein: The frequency domain resources or time domain resources used for the RAR are allocated based on a random access radio network temporary identifier (RA-RNTI).

19. The method according to claim 18, wherein: The time domain resource allocation for the PDCCH and PDSCH is the same.

20. The method according to claim 18, wherein: The time domain resource allocation for the PDCCH includes a subset of the time domain resource allocation for the PDSCH.

21. The method according to claim 18, wherein: The frequency domain resource allocation for the PDCCH is a subset of the frequency domain resource allocation for the PDSCH.

22. The method according to claim 18, wherein: The frequency domain resource allocation for the PDSCH is based on at least one of downlink control information (DCI) or the frequency domain resource allocation for the PDCCH.

23. The method according to claim 18, wherein: The time domain resource allocation for the PDSCH is based on at least one of downlink control information (DCI) or the time domain resource allocation for the PDCCH.

24. An apparatus for wireless communication at a user equipment (UE), comprising: Memory; as well as at least one processor coupled to the memory and configured to: Sending a preamble to the base station to initiate a random access channel (RACH) procedure; as well as In response to the transmitted preamble, a random access response (RAR) is received from the base station, wherein the RAR includes a physical downlink control channel (PDCCH) on a physical downlink shared channel (PDSCH) resource, and wherein a cyclic redundancy check (CRC) of the RAR includes a configuration based on a configuration and size of a CRC for the PDSCH.

25. The device according to claim 24, wherein: The PDCCH at least partially schedules the PDSCH.

26. The device according to claim 24, wherein: The frequency domain resources or time domain resources used for the RAR are allocated based on a random access radio network temporary identifier (RA-RNTI).

27. The device according to claim 26, wherein The time domain resource allocation for the PDCCH and the PDSCH is the same, wherein the time domain resource allocation for the PDCCH includes a subset of the time domain resource allocation for the PDSCH.

28. The device according to claim 26, wherein The frequency domain resource allocation for the PDCCH is a subset of the frequency domain resource allocation for the PDSCH, wherein the frequency domain resource allocation for the PDSCH is based on at least one of downlink control information (DCI) or the frequency domain resource allocation for the PDCCH.