Sync signal block pattern with gaps

Abstract

Certain aspects of the present disclosure provide techniques for a synchronization signal block (SSB) pattern with gaps. A method that may be performed by a network entity (e.g., a base station) generally includes determining a synchronization signal block (SSB) pattern that identifies SSB positions for sweeping a set of SSB beams over a plurality of SSB bursts, wherein at least some of the SSB positions have gaps between them, wherein the SSB pattern identifies a subset of the set of SSB beams to be used per SSB burst. The method generally includes transmitting the SSBs over the plurality of SSB bursts according to the pattern.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. Application No. 17 / 199,100, filed on March 11, 2021, which claims the benefit of and priority to U.S. Provisional Application No. 62 / 989,565, filed on March 13, 2020, both of which are assigned to the assignee of this application and are hereby expressly incorporated herein by reference in their entirety as if fully set forth below and for all applicable purposes.

[0003] background

[0004] public domain

[0005] Aspects of the present disclosure relate to wireless communications, and more particularly, to techniques for transmitting synchronization signal blocks (SSBs) according to a pattern with gaps.

[0006] Related technical description

[0007] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, broadcasts, etc. These wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple-access systems include 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, 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, to name a few.

[0008] 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. New radio (e.g., 5G NR) is an example of an emerging telecommunication standard. NR is an enhancement to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by using OFDMA with a cyclic prefix (CP) on the downlink (DL) and uplink (UL) to improve spectrum efficiency, reduce costs, improve services, utilize new spectrum, and better integrate with other open standards. To this end, NR supports beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation.

[0009] However, as the demand for mobile broadband access continues to grow, there is a need for further improvements to NR and LTE technologies. Preferably, these improvements should also apply to other multiple access technologies and the telecommunication standards that employ them.

[0010] Overview

[0011] The systems, methods, and devices of the present disclosure each have several aspects, no single one of which is solely responsible for its desirable attributes. After considering this discussion, and particularly after reading the section entitled "Detailed Description," one will understand how the features of the present disclosure provide advantages including improved blind decoding and channel estimation (BD / CE) constraints and configuration of New Radio (NR) physical downlink control channel (PDCCH) repetitions.

[0012] Certain aspects of the subject matter described in this disclosure may be implemented in a method for wireless communications by a network entity. The method generally includes determining a synchronization signal block (SSB) pattern that identifies SSB positions for sweeping a set of SSB beams over a plurality of SSB bursts, wherein at least some of the SSB positions have gaps between them, wherein the SSB pattern identifies a subset of the set of SSB beams to be used per SSB burst. The method generally includes transmitting the SSBs over the plurality of SSB bursts according to the pattern.

[0013] Certain aspects of the subject matter described in this disclosure can be implemented in a method for wireless communication by a user equipment (UE). The method generally includes determining an SSB pattern that identifies SSB positions for a network entity to sweep a set of SSB beams over a plurality of SSB bursts, wherein at least some of the SSB positions have gaps between them, wherein the SSB pattern identifies a subset of the set of SSB beams to be used per SSB burst. The method generally includes monitoring SSBs over the plurality of SSB bursts according to the pattern.

[0014] Certain aspects of the subject matter described in this disclosure can be implemented in a device for wireless communication. The device generally includes at least one processor and a memory coupled to the at least one processor. The memory generally includes code executable by the at least one processor to cause the device to: determine an SSB pattern identifying SSB positions for sweeping a set of SSB beams over a plurality of SSB bursts, wherein at least some of the SSB positions have gaps between them, wherein the SSB pattern identifies a subset of the set of SSB beams to be used per SSB burst. The memory generally includes code executable by the at least one processor to cause the device to transmit SSBs over the plurality of SSB bursts according to the pattern.

[0015] Certain aspects of the subject matter described in this disclosure can be implemented in a device for wireless communication. The device generally includes at least one processor and memory coupled to the at least one processor. The memory includes code executable by the at least one processor to cause the device to: determine an SSB pattern that identifies SSB positions for a network entity to sweep a set of SSB beams over a plurality of SSB bursts, wherein at least some of the SSB positions have gaps between them, wherein the SSB pattern identifies a subset of the set of SSB beams to be used per SSB burst. The memory generally includes code executable by the at least one processor to cause the device to monitor SSBs over the plurality of SSB bursts according to the pattern.

[0016] Certain aspects of the subject matter described in this disclosure can be implemented in a device for wireless communication. The device generally includes means for determining an SSB pattern that identifies SSB positions for sweeping a set of SSB beams over a plurality of SSB bursts, wherein at least some of the SSB positions have gaps between them, wherein the SSB pattern identifies a subset of the set of SSB beams to be used per SSB burst. The device generally includes means for transmitting an SSB over the plurality of SSB bursts according to the pattern.

[0017] Certain aspects of the subject matter described in this disclosure can be implemented in a device for wireless communication. The device generally includes means for determining an SSB pattern that identifies SSB positions for a network entity to sweep a set of SSB beams over a plurality of SSB bursts, wherein at least some of the SSB positions have gaps between them, wherein the SSB pattern identifies a subset of the set of SSB beams to be used per SSB burst. The device generally includes means for monitoring SSBs over the plurality of SSB bursts according to the pattern.

[0018] Certain aspects of the subject matter described in this disclosure can be implemented in a computer-readable medium having computer-executable code stored thereon for wireless communication. The computer-readable medium generally includes code for determining an SSB pattern identifying SSB positions for sweeping a set of SSB beams over a plurality of SSB bursts, wherein at least some of the SSB positions have gaps between them, wherein the SSB pattern identifies a subset of the set of SSB beams to be used per SSB burst. The computer-readable medium generally includes code for transmitting SSBs over the plurality of SSB bursts according to the pattern.

[0019] Certain aspects of the subject matter described in this disclosure can be implemented in a computer-readable medium having computer-executable code stored thereon for wireless communication. The computer-readable medium generally includes code for determining an SSB pattern that identifies SSB positions for a network entity to sweep a set of SSB beams over a plurality of SSB bursts, wherein at least some of the SSB positions have gaps therebetween, wherein the SSB pattern identifies a subset of the set of SSB beams to be used per SSB burst. The computer-readable medium generally includes code for monitoring SSBs over the plurality of SSB bursts according to the pattern.

[0020] To accomplish the foregoing and related ends, one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims. The following description and accompanying drawings set forth in detail certain illustrative features of the one or more aspects. However, these features are indicative of but a few of the various ways in which the principles of the various aspects may be employed. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] In order that the manner in which the above-recited features of the present disclosure may be understood in detail, a more particular description of what has been briefly summarized above may be given with reference to various aspects, some of which are illustrated in the accompanying drawings. It should be noted, however, that the drawings illustrate only certain aspects of the present disclosure and that the description may admit to other equally effective aspects.

[0023] Figure 1 is a block diagram conceptually illustrating an example wireless communication network in accordance with certain aspects of the present disclosure.

[0024] Figure 2 is a block diagram conceptually illustrating designs of example base stations (BSs) and user equipment (UEs) in accordance with certain aspects of the present disclosure.

[0025] Figure 3 is an example frame format for New Radio (NR) in accordance with certain aspects of the present disclosure.

[0026] Figure 4 Illustrated how different synchronization signal blocks (SSBs) may be sent using different beams in accordance with certain aspects of the present disclosure.

[0027] Figure 5 An exemplary transmission resource mapping is shown in accordance with certain aspects of the present disclosure.

[0028] Figure 6 Illustrated are examples of SSB patterns for different subcarrier spacings (SCSs), in accordance with certain aspects of the present disclosure.

[0029] Figure 7 is a flow diagram illustrating example operations for wireless communications by a network entity in accordance with certain aspects of the present disclosure.

[0030] Figure 8 is a flow diagram illustrating example operations for wireless communications by a UE in accordance with certain aspects of the present disclosure.

[0031] Figure 9A and Figure 9B An example of an SSB mode in accordance with certain aspects of the present disclosure is illustrated.

[0032] Figure 10 Illustrated are examples of SSB patterns with gaps across multiple SSB bursts, in accordance with certain aspects of the present disclosure.

[0033] Figure 11 Illustrated is an example mapping of SSBs to physical downlink control channel (PDCCH) resources in accordance with certain aspects of the present disclosure.

[0034] Figure 12 Illustrated is an example of frequency division multiplexing of PDCCH and remaining minimum system information (RMSI) resources with SSBs, in accordance with certain aspects of the present disclosure.

[0035] Figure 13 is an example of an SSB pattern with gaps on multiple SSB bursts in the context of a listen-before-talk procedure in accordance with certain aspects of the present disclosure.

[0036] Figure 14 is an example of an SSB pattern with gaps across multiple SSB bursts in accordance with certain aspects of the present disclosure.

[0037] Figure 15 Another example mapping of SSBs to PDCCH resources is illustrated in accordance with certain aspects of the present disclosure.

[0038] Figure 16 Another example of frequency division multiplexing of PDCCH and RMSI resources with SSBs is illustrated, in accordance with certain aspects of the present disclosure.

[0039] Figure 17 Illustrated is a communications device that may include various components configured to perform operations for the techniques disclosed herein, in accordance with certain aspects of the present disclosure.

[0040] Figure 18 Illustrated is a communications device that may include various components configured to perform operations for the techniques disclosed herein, in accordance with certain aspects of the present disclosure.

[0041] To facilitate understanding, identical reference numerals have been used, where possible, to designate identical elements that are common to the figures. It is contemplated that elements disclosed in one aspect may be beneficially utilized in other aspects without specific recitation.

[0042] Detailed description

[0043] Aspects of the present disclosure provide apparatus, methods, processing systems, and computer-readable media for techniques for transmitting synchronization signal blocks (SSBs) according to a pattern with gaps.

[0044] The following description provides examples for transmitting SSB according to a pattern with gaps, and does not limit the scope, applicability, or examples set forth in the claims. Changes may be made to the functions and arrangements of the elements discussed without departing from the present disclosure. Various examples may omit, substitute, or add various procedures or components as appropriate. For example, the methods described may be performed in an order different from that described, and various steps may be added, omitted, or combined. Moreover, features described with reference to some examples may be combined in some other examples. For example, a device may be implemented or a method may be practiced using any number of the aspects set forth herein. In addition, the present disclosure is intended to cover such devices or methods practiced using other structures, functionalities, or structures and functionalities that are in addition to or in addition to the various aspects of the present disclosure set forth herein. It should be understood that any aspect of the present disclosure disclosed herein may be implemented by one or more elements of the claims. The word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any aspect described herein as "exemplary" is not necessarily to be construed as superior to or preferable to other aspects.

[0045] In general, any number of wireless networks may be deployed in a given geographic area. Each wireless network may support a specific radio access technology (RAT) and may operate on one or more frequencies. A RAT may also be referred to as a radio technology, air interface, etc. A frequency may also be referred to as a carrier, subcarrier, frequency channel, tone, subband, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs.

[0046] The techniques described herein can be used for various wireless networks and radio technologies. Although various aspects may be described herein using terms typically associated with 3G, 4G, and / or new radio (e.g., 5G NR) wireless technologies, various aspects of the present disclosure may be applied in communication systems based on other generations.

[0047] NR access can support various wireless communication services, such as enhanced mobile broadband (eMBB) targeting wide bandwidth (e.g., 80 MHz or above), millimeter wave (mmW) targeting high carrier frequency (e.g., 25 GHz or above), massive machine type communication (MTC) targeting non-backward compatible MTC technology, and / or mission-critical services targeting ultra-reliable low latency communication (URLLC). These services may include latency and reliability requirements. These services may also have different transmission time intervals (TTIs) to meet corresponding quality of service (QoS) requirements. In addition, these services can coexist in the same subframe.

[0048] NR supports beamforming and the beam direction can be dynamically configured. MIMO transmission with precoding can also be supported. MIMO configuration in the DL can support up to 8 transmit antennas (with multi-layer DL transmission of up to 8 streams) and up to 2 streams per UE. Multi-layer transmission of up to 2 streams per UE can be supported. Aggregation of multiple cells can be supported using up to 8 serving cells.

[0049] Figure 1 An example wireless communication network 100 is illustrated in which aspects of the present disclosure may be implemented. For example, the wireless communication network 100 may include a base station (BS) 110 and a user equipment (UE) 120 configured to transmit and monitor synchronization signal blocks (SSBs) transmitted according to an SSB pattern with gaps across multiple SSB bursts. Figure 1 As shown in FIG, BS 110a includes a gap module 112. According to aspects of the present disclosure, the gap module 112 may be configured to perform Figure 7 Additionally, as explained in Figure 1 As shown in FIG, UE 120a includes a gap module 122. According to aspects of the present disclosure, the gap module 122 may be configured to perform Figure 8 The operations illustrated in and other operations disclosed herein for determining an SSB pattern with gaps in multiple SSB bursts.

[0050] The wireless communication network 100 may be a NR system (e.g., a 5G NR network). Figure 1 As shown, the wireless communication network 100 may be in communication with a core network 132. The core network 132 may be in communication with one or more base stations (BSs) 110 and / or user equipments (UEs) 120 in the wireless communication network 100 via one or more interfaces.

[0051] BS 110 may provide communication coverage for a particular geographic area (sometimes referred to as a "cell"), which may be stationary or mobile depending on the location of mobile BS 110. In some examples, BS 110 may interconnect with each other and / or one or more other BSs or network nodes (not shown) in wireless communication network 100 via various types of backhaul interfaces (e.g., direct physical connections, wireless connections, virtual networks, etc.) using any suitable transport network. Figure 1 In the example shown in FIG, BSs 110a, 110b, and 110c may be macro BSs for macro cells 102a, 102b, and 102c, respectively. BS 110x may be a pico BS for pico cell 102x. BSs 110y and 110z may be femto BSs for femto cells 102y and 102z, respectively. A BS may support one or more cells. A network controller 130 may be coupled to a group of BSs 110 and provide coordination and control for these BSs 110 (e.g., via a backhaul).

[0052] BS 110 communicates with UEs 120a-y (each also individually referred to herein as UE 120 or collectively referred to herein as UE 120) in wireless communication network 100. UEs 120 (e.g., 120x, 120y, etc.) may be dispersed throughout wireless communication network 100, and each UE 120 may be stationary or mobile. Wireless communication network 100 may also include relay stations (e.g., relay station 110r) (also referred to as relays, etc.) that receive transmissions of data and / or other information from an upstream station (e.g., BS 110a or UE 120r) and send transmissions of the data and / or other information to a downstream station (e.g., UE 120 or BS 110), or that relay transmissions between UEs 120 to facilitate communication between the devices.

[0053] The network controller 130 may be coupled to a set of BSs and provide coordination and control of the BSs. In various aspects, the network controller 130 may be in communication with a core network 132 (e.g., a 5G core network (5GC)), which provides various network functions such as access and mobility management, session management, user plane functions, policy control functions, authentication server functions, unified data management, application functions, network exposure functions, network repository functions, network slice selection functions, etc.

[0054] Figure 2 Illustrated are BS 110a and UE 120a (e.g., in Figure 1 Example components of the wireless communication network 100).

[0055] At BS 110a, transmit processor 220 may receive data from data source 212 and control information from controller / processor 240. The control information may be for a physical broadcast channel (PBCH), a physical control format indicator channel (PCFICH), a physical hybrid ARQ indicator channel (PHICH), a physical downlink control channel (PDCCH), a group common PDCCH (GC PDCCH), etc. The data may be for a physical downlink shared channel (PDSCH), etc. A medium access control (MAC)-control element (MAC-CE) is a MAC layer communication structure that may be used for the exchange of control commands between wireless nodes. The MAC-CE may be carried in a shared channel, such as a physical downlink shared channel (PDSCH), a physical uplink shared channel (PUSCH), or a physical sidelink shared channel (PSSCH).

[0056] The processor 220 may process (e.g., encode and symbol map) data and control information to obtain data symbols and control symbols, respectively. The transmit processor 220 may also generate reference symbols (such as for the primary synchronization signal (PSS), secondary synchronization signal (SSS), and channel state information reference signal (CSI-RS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on ​​the data symbols, control symbols, and / or reference symbols, as applicable, and may provide an output symbol stream to a modulator (MOD) in transceivers 232a-232t. Each modulator in transceivers 232a-232t may process a respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. Downlink signals from the modulators in transceivers 232a-232t may be transmitted via antennas 234a-234t, respectively.

[0057] At UE 120a, antennas 252a-252r may receive downlink signals from BS 110a and may provide received signals to demodulators 254a-254r (DEMOD) in the transceiver, respectively. Each demodulator in transceivers 254a-254r may condition (e.g., filter, amplify, downconvert, and digitize) its respective received signal to obtain input samples. Each demodulator may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. A MIMO detector 256 may obtain received symbols from all demodulators in transceivers 254a-254r, perform MIMO detection on the received symbols where applicable, and provide detected symbols. A receive processor 258 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for UE 120a to a data sink 260, and provide decoded control information to a controller / processor 280.

[0058] On the uplink, at the UE 120a, a transmit processor 264 may receive and process data from a data source 262 (e.g., for a physical uplink shared channel (PUSCH)) and control information from the controller / processor 280 (e.g., for a physical uplink control channel (PUCCH)). The transmit processor 264 may also generate reference symbols for reference signals (e.g., a sounding reference signal (SRS)). The symbols from the transmit processor 264 may be precoded by the TX MIMO processor 266, if applicable, further processed by modulators in the transceivers 254a-254r (e.g., for SC-FDM, etc.), and transmitted to the BS 110a. At BS 110a, the uplink signal from UE 120a may be received by antenna 234, processed by modulators in transceivers 232a-232t, detected by MIMO detector 236 if applicable, and further processed by receive processor 238 to obtain decoded data and control information sent by UE 120a. Receive processor 238 may provide the decoded data to a data sink 239 and the decoded control information to a controller / processor 240.

[0059] Memories 242 and 282 may store data and program codes for BS 110a and UE 120a, respectively. A scheduler 244 may schedule UEs for data transmission on the downlink and / or uplink.

[0060] The antennas 252, processors 266, 258, 264, and / or controller / processor 280 of the UE 120a, and / or the antennas 234, processors 220, 230, 238, and / or controller / processor 240 of the BS 110 may be used to perform the various techniques and methods described herein for determining an SSB pattern with gaps in a plurality of SSB bursts. For example, in accordance with aspects of the present disclosure, Figure 2 As shown in FIG, the controller / processor 240 of BS 110a includes a gap module 241, which may be configured to perform Figure 7 The operations illustrated in and other aspects described herein for determining an SSB pattern with gaps in a plurality of SSB bursts. According to aspects of the present disclosure, Figure 2 As shown in FIG, the controller / processor 280 of the UE 120a includes a gap module 281, which may be configured to perform Figure 8 The operations illustrated in and other aspects described herein for determining an SSB pattern with gaps in multiple SSB bursts. Although shown at the controller / processor, other components of the UE 120a and BS 110a may also be used to perform the operations described herein.

[0061] NR can utilize orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) on both the uplink and downlink. NR can support half-duplex operation using time division duplexing (TDD). OFDM and single-carrier frequency division multiplexing (SC-FDM) divide the system bandwidth into multiple orthogonal subcarriers, often referred to as tones, bins, etc. Each subcarrier can be modulated with data. Modulation symbols can be sent in the frequency domain with OFDM and in the time domain with SC-FDM. The spacing between adjacent subcarriers can be fixed, and the total number of subcarriers can depend on the system bandwidth. The minimum resource allocation (so-called resource block (RB)) can be 12 contiguous subcarriers. The system bandwidth can also be divided into subbands. For example, a subband can cover multiple RBs. NR can support a base subcarrier spacing (SCS) of 15 kHz, and other SCSs (e.g., 30 kHz, 60 kHz, 120 kHz, 240 kHz, etc.) can be defined relative to the base SCS.

[0062] Figure 33 is a diagram showing an example of a frame format 300 for NR. The transmission timeline for each of the downlink and uplink may be divided into units of radio frames. Each radio frame may have a predetermined duration (e.g., 10 ms) and may be divided into 10 subframes with indices 0 to 9, each subframe being 1 ms. Each subframe may include a variable number of slots (e.g., 1, 2, 4, 8, 16, ... slots), depending on the SCS. Each slot may include a variable number of symbol periods (e.g., 7 or 14 symbols), depending on the SCS. An index may be assigned to the symbol period in each slot. A minislot (which may be referred to as a subslot structure) refers to a transmission time interval having a duration less than a slot (e.g., 2, 3, or 4 symbols).

[0063] Each symbol in a slot may indicate the link direction (e.g., DL, UL, or flexible) used for data transmission, and the link direction used for each subframe may be dynamically switched. The link direction may be based on the slot format. Each slot may include DL / UL data and DL / UL control information.

[0064] In NR, a synchronization signal (SS) block (SSB) is transmitted. The SS block includes PSS, SSS, and two-symbol PBCH. The SS block can be in a fixed time slot position (such as Figure 3 The PBCH is transmitted in symbols 0-3 (shown in [ 0-3 ]). The PSS and SSS can be used by the UE for cell search and acquisition. The PSS provides half-frame timing, while the SS provides CP length and frame timing. The PSS and SSS provide cell identity. The PBCH carries some basic system information, such as downlink system bandwidth, timing information within radio frames, SS burst set periodicity, and system frame number.

[0065] Further system information, such as Remaining Minimum System Information (RMSI), System Information Blocks (SIBs), Other System Information (OSI), may be transmitted on the Physical Downlink Shared Channel (PDSCH) in certain subframes.

[0066] like Figure 4 As shown in the figure, SS blocks can be organized into SS burst sets to support beam sweeping. As shown in the figure, each SSB within the burst set can be transmitted using a different beam, which can help the UE quickly acquire both transmit (Tx) and receive (Rx) beams (especially for mmW applications). The physical cell identity (PCI) can still be decoded from the PSS and SSS of the SSB.

[0067] Certain deployment scenarios may include one or both NR deployment options. An option may be configured for non-standalone (NSA) and / or standalone (SA) options. Standalone cells may need to broadcast both SSBs and remaining minimum system information (RMSI) (e.g., using SIB1 and SIB2). Non-standalone cells may only need to broadcast SSBs, not RMSI. In a single carrier in NR, multiple SSBs may be sent at different frequencies and may include different types of SSBs.

[0068] Control Resource Set (CORESET)

[0069] A control resource set (CORESET) for an OFDMA system (e.g., a communication system that transmits a PDCCH using an OFDMA waveform) may include a set of one or more control resources (e.g., time and frequency resources) configured within the system bandwidth (e.g., a specific region on the NR downlink resource grid) for communicating the PDCCH and a parameter set used to carry the PDCCH / DCI. For example, the CORESET may be similar in region to the LTE PDCCH region (e.g., the first 1, 2, 3, or 4 OFDM symbols in a subframe).

[0070] Within each CORESET, one or more search spaces (e.g., common search space (CSS), UE-specific search space (USS), etc.) may be defined for a given UE. A search space is generally an area or portion where a communication device (e.g., a UE) may search for control information.

[0071] According to various aspects of the present disclosure, a CORESET is a time-frequency domain resource set defined in units of resource element groups (REGs). Each REG may include a fixed number (e.g., twelve) frequency tones / subcarriers in one symbol period (e.g., the symbol period of a time slot), where one frequency tone in one symbol period is called a resource element (RE). A fixed number of REGs (such as six) may be included in a control channel element (CCE). A CCE set may be used to transmit a new radio PDCCH (NR-PDCCH), where different numbers of CCEs in a set are used to transmit NR-PDCCH using different aggregation levels. Multiple CCE sets may be defined as search spaces for UEs, and thereby a B node or other base station may transmit NR-PDCCH to the UE by transmitting NR-PDCCH in a CCE set that is a decoding candidate within the search space defined for the UE. The UE may receive the NR-PDCCH by searching in the search space for the UE and decoding the NR-PDCCH transmitted by the B node.

[0072] As mentioned above, different aggregation levels can be used to transmit CCE sets. The aggregation level can be generally defined as the number of CCEs that include PDCCH candidates and can include aggregation levels 1, 2, 4, 8, and 18, which can be configured by the radio resource control (RRC) configuration of the search space set (SS set). The CORESET can be linked to the SS set within the RRC configuration. For each aggregation level, the number of PDCCH candidates can be RRC configurable.

[0073] The operating characteristics of a Node B or other base station in an NR communication system may depend on the frequency range (FR) in which the system operates. The frequency range may include one or more operating bands (e.g., the "n1" band, the "n2" band, the "n7" band, and the "n41" band), and the communication system (e.g., one or more Node Bs and a UE) may operate in one or more operating bands. Frequency ranges and operating bands are described in more detail in TS 38.104 (Release 15), "Base station (BS) radio transmission and reception," available from the 3GPP website.

[0074] As described above, a CORESET is a collection of time and frequency domain resources. A CORESET can be configured to communicate PDCCH within the system bandwidth. A UE can determine a CORESET and monitor the CORESET for control channels. During initial access, the UE can identify the initial CORESET (CORESET#0) configuration from a field in the Master Information Block (MIB) (e.g., pdcchConfigSIB1). This initial CORESET can then be used to configure the UE (e.g., via dedicated (UE-specific) signaling along with other CORESETs and / or bandwidth portions). When the UE detects a control channel in a CORESET, the UE attempts to decode the control channel, and the UE communicates with the transmitting BS (e.g., transmitting cell) based on the control data provided in the control channel (e.g., transmitted via the CORESET).

[0075] In some cases, CORESET #0 may include a different number of resource blocks (RBs). For example, in some cases, CORESET #0 may include one of 24, 48, or 96 RBs. For other CORESETS, a 45-bit bitmap may be used to configure the available RB groups, where each bit in the bitmap corresponds to 6 RBs within a bandwidth part (BWP) and the most significant bit corresponds to the first RB group in the BWP.

[0076] According to aspects of the present disclosure, when a UE is connected to a cell (or BS), the UE may receive a master information block (MIB). The MIB may be in a synchronization signal and physical broadcast channel (SS / PBCH) block on a sync raster (e.g., in the PBCH of the SS / PBCH block). In some scenarios, the sync raster may correspond to an SSB. Based on the frequency of the sync raster, the UE may determine the operating frequency band of the cell. Based on the operating frequency band of the cell, the UE may determine the minimum channel bandwidth and subcarrier spacing (SCS) of the channel. The UE may then determine an index based on the MIB (e.g., four bits in the MIB conveying an index in the range 0-15).

[0077] Given this index, the UE can look up or locate the CORESET configuration (this initial CORESET configured via the MIB is generally referred to as CORESET #0). This can be done based on one or more tables of CORESET configurations. These configurations (including a single table scenario) may include various subsets of indices indicating valid CORESET configurations for various combinations of minimum channel bandwidth and subcarrier spacing (SCS). In some arrangements, each combination of minimum channel bandwidth and SCS may be mapped to a subset of indices in the table.

[0078] Alternatively or additionally, the UE may select a search space CORESET configuration table from several tables of CORESET configurations. These configurations may be based on the minimum channel bandwidth and the SCS. The UE may then look up the CORESET configuration (e.g., Type 0 - PDCCH search space CORESET configuration) from the selected table based on the index. After determining the CORESET configuration (e.g., from a single table or a selected table), the UE may then determine the CORESET to monitor based on the location (in time and frequency) of the SS / PBCH blocks and the CORESET configuration (as mentioned above).

[0079] Figure 5 An exemplary transmission resource mapping 500 is shown in accordance with aspects of the present disclosure. In the exemplary mapping, a BS (e.g., Figure 1 BS 110a) shown in FIG transmits SS / PBCH block 502. The SS / PBCH block includes a MIB that conveys an index to a table that relates the time and frequency resources of CORESET 504 to the time and frequency resources of the SS / PBCH block.

[0080] The BS may also transmit control signaling. In some scenarios, the BS may also transmit control signaling to the UE (e.g., Figure 15 ). The BS transmits a PDCCH to the UE 120 (shown in FIG). The PDCCH may schedule a PDSCH 506. The BS then transmits the PDSCH to the UE. The UE may receive the MIB in the SS / PBCH block, determine an index, look up the CORESET configuration based on the index, and determine the CORESET from the CORESET configuration and the SS / PBCH block. The UE may then monitor the CORESET, decode the PDCCH in the CORESET, and receive the PDSCH assigned by the PDCCH.

[0081] Different CORESET configurations may have different parameters defining the corresponding CORESET. For example, each configuration may indicate the number of resource blocks (e.g., 24, 48, or 96), the number of symbols (e.g., 1-3), and an offset indicating the frequency position (e.g., 0-38 RBs).

[0082] Furthermore, REG clusters can be used to convey a core set. Each REG in a REG cluster can be adjacent in the frequency domain and / or time domain. In some cases, the time domain may be prioritized before the frequency domain. REG cluster sizes can include 2, 3, or 6 for interleaved mapping, and 6 for non-interleaved mapping.

[0083] As mentioned above, a CCE set may be used to transmit a New Radio PDCCH (NR-PDCCH), where different numbers of CCEs in the set are used to transmit the NR-PDCCH using different aggregation levels. The mapping of the PDCCH candidates of an SS set to the CCEs of the associated CORESET may be achieved with the aid of a hash function, such as Figure 6 The hash function can randomize the PDCCH candidates in CORESET p in time slot n. s and can be performed according to the following formula:

[0084]

[0085] where for simplicity, single carrier operation with a single SS set indexed as s is assumed, L is the aggregation level, N CCE,p is the total number of CCEs for a given CORESET p, m (0, 1, ..., M (L) -1) is the candidate index, where M (L) is the number of PDCCH candidates for ALL, i(0, 1, ..., L-1) is the adjacent CCE index of the PDCCH candidate, for the CSS set, About USS Collection It is based on the UE's C-RNTI and timeslot number n s , a pseudo-random variable, and Indicates a floor operation.

[0086] Example Sync Signal Block Burst Design with Gaps

[0087] As mentioned above, synchronization signal (SS) blocks (SSBs) can be organized into SS bursts to support beam sweeping. In 5G New Radio (NR), SSBs can be transmitted using up to 64 different beam directions in a set called an SS burst set. SS blocks in an SS burst set are transmitted in the same frequency region, while SS blocks in different SS burst sets can be transmitted at different frequency locations.

[0088] In NR systems, there is an SSB burst mode (also referred to herein as SSB mode) defined for an SSB burst set in the frequency range 2 (FR2) range (i.e., 24.25 GHz to 52.6 GHz) with a 120 kHz subcarrier spacing (SCS) or a 240 kHz SCS. Figure 6 An example SSB pattern with a 120kHz subcarrier spacing (SCS) and an example SSB pattern with a 240kHz SCS are illustrated. Each SSB pattern indicates the SSB beam to be used to transmit the SSB and also indicates the SSB position of the SSB beam. The SSB burst in the SSB pattern is 5ms or 2ms for the 120kHz SCS and 240kHz SCS, respectively.

[0089] Although there is an SSB mode for FR2, there is a need to address the SSB mode in the 60 GHz band. One way to address the need for an SSB mode in the 60 GHz band is to utilize the SSB burst mode used in FR2 because the 60 GHz band is close to FR2. However, applying the SSB burst mode used in FR2 requires modifying the SSB burst mode for use in the 60 GHz band. For example, since the bandwidth of each channel in the 60 GHz band can be up to 2 GHz, the SSB burst mode used in FR2 may need to be paired with a higher SCS data transmission (e.g., 960 kHz or greater) because a 120 kHz SCS data transmission may be too narrow.

[0090] Even with modifications, many of the design aspects used with the SSB mode used in FR2 can be used for the SSB mode in the 60 GHz band.

[0091] There is also a need to send ultra-reliable low latency communication (URLLC) traffic. Due to the large number of SSBs when sweeping multiple directions, it may be desirable to multiplex URLLC data within the SSB burst. The current SSB burst design pattern may not include enough gaps for URLLC traffic. This demand for sending URLLC traffic includes URLLC downlink (DL) traffic, which is not suitable for the same analog beam of SSB transmission, thereby preventing frequency division multiplexing (FDM). URLLC traffic may also include URLLC uplink (UL) traffic and / or control transmissions, where a relatively large downlink (DL) / UL switching gap is required over the transmission time. URLLC traffic may not be able to wait for the end of the SSB burst before transmitting. In some cases, to address this demand, the network can utilize the gaps in the SSB pattern by sending fewer SSBs, but sweeping fewer SSBs may affect beam management and overall performance.

[0092] However, aspects of the present disclosure propose an SSB mode that introduces gaps in the SSB burst mode without increasing the maximum SSB burst length or reducing the number of supported beams.

[0093] Figure 7 8 is a flow diagram illustrating example operations 700 for wireless communication in accordance with certain aspects of the present disclosure. Operations 700 may be performed, for example, by a network entity, such as, for example, BS 110a in wireless communication network 100. Operations 700 may be operations performed by the network entity that are complementary to operations 800 performed by a UE.

[0094] Operations 700 begin at 702 by determining an SSB pattern that identifies SSB positions for sweeping a set of SSB beams over a plurality of SSB bursts with gaps between at least some of the SSB positions, wherein the SSB pattern identifies a subset of the set of SSB beams to use per SSB burst.

[0095] In some aspects, at 704, the network entity signals information about the mode via a Remaining Minimum System Information (RMSI) Information Element (IE).

[0096] In some aspects, at 706, the network entity signals to at least one user equipment (UE) which SSBs are transmitted in which SSB burst.

[0097] In some aspects, at 708, the network entity signals, for the set of SSB bursts, a set of SSB positions per SSB burst for transmitting the SSB.

[0098] In some aspects, at 710, the network entity signals a parameter indicating an SSB position per SSB burst to allow the UE to perform rate matching in each SSB burst.

[0099] At 712, the network entity transmits SSBs over the plurality of SSB bursts according to the pattern.

[0100] Figure 8 8 is a flow diagram illustrating example operations 800 for wireless communication in accordance with certain aspects of the present disclosure. Operations 800 may be performed, for example, by a UE (e.g., such as UE 120a in wireless communication network 100). Operations 800 may be operations performed by the UE that are complementary to operations 700 performed by a network entity.

[0101] Operation 800 begins at 802 by determining an SSB pattern that identifies SSB positions for a network entity to sweep a set of SSB beams over a plurality of SSB bursts, wherein at least some of the SSB positions have gaps therebetween, wherein the SSB pattern identifies a subset of the set of SSB beams to be used per SSB burst.

[0102] In some aspects, at 804, the UE receives signaling information regarding the mode from a network entity via an RMSI IE.

[0103] In some aspects, at 806, the UE receives signaling from the network entity regarding which SSBs are transmitted in which SSB burst.

[0104] In some aspects, at 808, the UE receives signaling from the network entity regarding parameters indicating SSB locations per burst, and the UE performs rate matching in each burst based on the signaled parameters.

[0105] In some aspects, at 810, the UE receives signaling from a network entity regarding a set of SSB positions per SSB burst for transmitting an SSB for a set of SSB bursts.

[0106] At 812, the UE monitors the SSBs over the plurality of SSB bursts according to the pattern.

[0107] Generally speaking, beam sweeping is done in a single SSB burst set. Figure 9A An example SSB pattern is illustrated where beam sweeping can be completed in a first SSB burst set, and the complete beam sweep is repeated using the same SSB pattern in a second SSB burst set. However, there are few gaps between the SSB beams in the SSB burst set. Figure 9BAn example SSB pattern is illustrated in which beam sweeping is accomplished using an increased SSB burst period in a first SSB burst set to reduce overhead. However, despite having an increased burst period, this example SSB pattern does not address the reduced space for other beams to be transmitted.

[0108] As mentioned above, aspects of the present disclosure provide techniques for introducing gaps in SSB burst mode without increasing the maximum SSB burst length (e.g., 5 ms for 120 kHz SCS) or reducing the number of beams supported. Aspects of the present disclosure also attempt to reduce regulatory impact and allow SSB burst mode backward compatibility.

[0109] A network entity sweeps up to 64 SSB beams over a plurality of SSB bursts without changing the SSB pattern in time. According to various aspects, the network entity and / or the UE determines an SSB pattern for sweeping a set of SSB beams over a plurality of SSB bursts with gaps between some of the SSB transmissions. The network entity and / or the UE transmits and / or monitors SSBs over the plurality of SSB bursts according to the pattern. In some cases, the network entity and / or the UE provides signaling information about the pattern via the RMSI IE.

[0110] Figure 10 An example SSB pattern is illustrated with gaps between SSB beams over multiple SSB bursts. According to various aspects, the SSB pattern involves transmitting SSBs on different SSB beam subsets per SSB burst. For example, in the illustrated example, a first SSB beam subset is swept during a first SSB burst, and a second SSB beam subset is swept during a second SSB burst.

[0111] In the illustrated example, the SSB beams in different subsets are different, and the SSBs in different subsets are transmitted at different SSB positions. For example, one subset may include SSB beams located at even-numbered SSB indices, while another subset may include SSB beams located at odd-numbered SSB indices. The example pattern with gaps increases the period in which the SSB beams are transmitted, and the increase in the periodicity of the SSB burst transmissions will create longer SSB bursts in which it is difficult to time division multiplex (TDM) URLLC traffic. Accordingly, including gaps between the SSB beams in the SSB pattern allows other data (e.g., URLLC traffic) to be multiplexed. Although Figure 10 The example of illustrates two SSB sets, but any number of sets can be used in any number of SSB bursts to complete beam sweeping.

[0112] As mentioned, the network entity determines an SSB pattern that identifies different subsets of SSBs to be used per SSB burst. These SSBs are transmitted using SSB beams at specific locations (identified by SSB indices), which may be quasi-co-located (QCL), but the SSBs may not be transmitted by the same SSB beam in every SSB burst. Beam sweeping may be performed over a longer period of time and may require multiple SSB bursts to complete a complete SSB beam sweep. The initial SSB search may require more time (e.g., multiple SSB bursts or periods), or the period may be smaller to compensate.

[0113] In some cases, the UE may know which SSB beams are in each SSB burst after connecting to the network entity. The network entity may provide signaling (e.g., radio resource control (RRC) signaling) to provide information about the SSB beams in each SSB burst and about rate matching behavior. In NR, physical downlink shared channel (PDSCH) transmissions may be rate matched around the SSB as indicated by an RRC parameter (e.g., ssb-PositionInBurst (ssb position in burst)). The SSB pattern may be applied to each SSB burst, but the SSB pattern determined by the network entity may be different in each SSB burst. Depending on some scenarios, the RRC parameter (e.g., ssb-PositionInBurst) may indicate the union of SSB positions across multiple SSB bursts. The network entity may introduce an RRC parameter (e.g., ssb-PositionInBurst) to tell the UE how to perform rate matching in each SSB burst (if configured). In some examples, the network entity may define a period for the configuration of a per-burst SSB pattern for each period.

[0114] In some cases, the network entity may determine how to transmit the SSBs in each SSB burst. This determination by the network entity may depend on the demand for URLLC traffic. In some cases, the SSBs in each SSB burst may have gaps between them to allow for multiplexing of other emergency traffic.

[0115] The physical broadcast channel (PBCH) payload may be the same as the SSB pattern used in FR2 (e.g., same single frequency network (SFN), same half-frame index, same SSB index). Accordingly, the UE may recover timing after detecting the SSB pattern, regardless of whether the pattern is used in FR2 or in the 60 GHz band.

[0116] For initial access in SSB beam sweeping, the NR UE may assume an SSB periodicity of 20ms. When the network entity determines SSB beam subsets and places each subset in a different SSB burst, if each SSB burst period is 20ms, then SSB beam sweeping may take up to 40ms. In some examples, the network entity may transmit SSBs using an SSB burst period of 10ms and complete beam sweeping every 20ms, thereby reducing the impact on initial access beam search.

[0117] In some cases, for an SSB burst period of an SSB pattern with gaps that is the same as an SSB burst period in FR2, the overall measurement time for radio link monitoring (RLM) and / or radio resource management (RRM) measurements may be longer. By splitting the SSB pattern between multiple SSB bursts, the measurement time may depend on the number of SSB bursts. For example, when SSBs are transmitted using SSB beam subsets in two different SSB bursts, the RLM and / or RRM measurement time may be doubled. In some cases, an RRC parameter (e.g., ssb-PositionPerBurst) may be provided for RLM and / or RRM measurements. Using the RRC parameter, the UE may perform micro-sleep between SSB transmissions during the gaps to compensate for the power loss caused by the longer measurement time.

[0118] The SSB pattern with gaps for the 60 GHz band can coexist with the SSB pattern used in FR2 and other SSB patterns. The network may decide between using the SSB pattern used in FR2 and the SSB pattern with gaps for the 60 GHz band depending on various factors. For example, the network may decide to use the SSB pattern with gaps for the 60 GHz band for URLLC traffic. In some cases, the SSB pattern disclosed herein may be understood by introducing a new IE in the RMSI after the network entity reads the RMSI.

[0119] In some cases, physical random access channel (PRACH) transmissions may not have any impact on the SSB pattern with gaps for the 60 GHz band. However, some PRACH opportunities may be mapped from the SSB index.

[0120] Figure 11An example of type 0 physical downlink control channel (PDCCH) monitoring used in conjunction with the SSB pattern with gaps for the 60 GHz band is illustrated. Based on the detected SSBs, the UE monitors the PDCCH that schedules the physical downlink shared channel (PDSCH) carrying the RMSI. Type 0 PDCCH monitoring can work for the SSB pattern used in FR and the SSB pattern with gaps for the 60 GHz band. In general, type 0 PDCCH monitoring involves mapping of SSBs to the PDCCH resources to be monitored. In one example, the SSB pattern with gaps for the 60 GHz band can put type 0 PDCCH transmissions for all beams together (e.g., all SSBs are mapped to the same PDCCH resources). As Figure 11 As explained in

[15] , Type 0 PDCCH transmissions (RMSI sweeps for all beams) for two SSB beam subsets in an SSB burst are put together. This example of Type 0 PDCCH monitoring can be used in conjunction with an offset relative to the start of the SSB burst window. As a result, the resources used for Type 0 PDCCH monitoring may not depend on where the SSB is detected.

[0121] Figure 12 Another example of type 0 PDCCH monitoring used in conjunction with a gapped SSB pattern in the 60 GHz band is described. In this example, type 0 PDCCH monitoring and RMSI physical downlink shared channel (PDSCH) transmission can be frequency-division multiplexed (FDM) with the same QCL SSB according to a gapped SSB pattern in the 60 GHz band. Type 0 PDCCH and RMSI PDSCH can be in the same SSB burst as the corresponding SSB. When the UE detects the SSB, the UE can monitor the type 0 PDCCH transmission at a located position in a later SSB burst. This monitoring may depend on the SSB burst period (e.g., a 20 ms interval). If the SSB burst period is 20 ms, the QCLed type 0 PDCCH transmission can be transmitted every 40 ms. In some cases, if the UE waits longer, the UE may see the RMSI transmission (which is with the SSB FDM). If the SSB burst period is 10 m under a full sweep of 20 ms, the QCLed type 0 PDCCH transmission can be transmitted every 20 ms at the same position. Accordingly, the UE may maintain detection performance between the SSB mode disclosed herein and the SSB mode used in FR2.

[0122] Figure 13An example of a listen-before-talk (LBT) process used in conjunction with an SSB pattern with gaps in the 60 GHz band is explained. Since the 60 GHz band is in an unlicensed band, channel transmissions in the band are subject to an LBT process and such an LBT process may fail, wherein transmission (of an SSB burst) may not occur. Accordingly, if an SSB burst fails to be transmitted due to the LBT process as illustrated in the crossed-out SSB burst, the SSB may be transmitted by multiplexing with other SSBs in other SSB bursts. In some cases, if an SSB burst fails to be transmitted due to the LBT process, the SSB may be transmitted in the next SSB burst along with the SSB that was originally transmitted in the next SSB burst according to the SSB pattern with gaps.

[0123] Depending on some scenarios, the network entity may not perform rate matching around these SSBs because rate matching is configured via RRC. However, scheduling may avoid scheduling these resources. In some cases, opportunities for transmission may be available even if LBT does not fail. For example, an SSB beam may have been designated for URLLC, but there is no URLLC traffic in a particular SSB burst, and therefore the SSB may be transmitted using the SSB beam designated for URLLC. In some cases, the transmission may not require a full SSB burst. The transmission may require an SSB beam subset of the SSB burst, which may depend on the presence of URLLC traffic.

[0124] Figure 14 An example SSB pattern with gaps and shifted SSB beams in the 60 GHz band is illustrated. In the illustrated example, the same SSB position is used in each burst, but a different SSB beam is used for each SSB position. According to various aspects, the SSB pattern involves a set of SSB positions in the SSB pattern for transmitting SSBs, and for each SSB beam subset, the network transmits the SSB on each SSB beam subset using a selected SSB position in each SSB burst. In such aspects, each SSB burst can have a different set of SSB beams in the selected position.

[0125] According to various aspects, the same set of SSB positions is transmitted in each SSB burst, while the QCL assumptions for the SSBs at the same positions in different SSB bursts may be different (e.g., different beam / spatial QCL assumptions). In some cases, RRC signaling may indicate the same SSB positions, while the QCL assumptions are for every N SSB bursts, rather than for every SSB burst. In some cases, the network entity may perform rate matching for an SSB pattern with gaps and shifted SSBs similar to rate matching for an SSB pattern in FR2. The rate matching behavior may remain the same with respect to RRC parameters (e.g., ssb-PositionInBurst). However, in some cases, beam tracking may be affected.

[0126] In NR, PDSCH transmissions can be rate matched around the SSB as indicated by the RRC parameter (e.g., ssb-PositionInBurst). In some cases, the same pattern can be applied to each SSB burst because the SSB position is the same across multiple SSB bursts, even if the SSB pattern is different in different SSB bursts. In some systems, the RRC parameter (e.g., ssb-PositionInBurst) can be the same as Release 15, but the QCL can be different.

[0127] As mentioned, the SSB pattern with gaps can coexist with the SSB pattern used in FR2 and with other patterns used in other frequency ranges. In some cases, the network entity may be able to select between different SSB patterns regardless of the frequency range for which the SSB pattern is designated. In some cases, an RRC parameter is introduced in the RMSI to indicate that the SSB is only QCLed every N SSB bursts. Accordingly, when N is configured, the UE may assume QCL for SSBs of the same index and the same SSB burst index depending on the value of N.

[0128] Figure 15 An example of Type 0 PDCCH monitoring using an SSB pattern with gaps and shifted SSB beams is illustrated. As illustrated, for the same SSB position in different bursts, the UE can monitor both positions for a PDCCH that schedules a PDSCH carrying RMSI corresponding to the two corresponding SSB beam QCLs.

[0129] As with the SSB pattern with gaps mentioned earlier, Type 0 PDCCH monitoring works for SSB patterns with gaps and shifted SSB beams. In one example, the Type 0 PDCCHs used for all beams together can be put together. An offset relative to the start of a full SSB burst period (e.g., a 20ms window) can be used in conjunction with the SSB pattern with gaps and shifted beams. However, since the SSB pattern may have shifted SSB beams, two SSBs with different QCLs may have the same SSB index / position. In some cases, the mapping of SSBs to Type 0 PDCCH transmissions used in FR2 may be used to map SSBs at the same location. In some cases, the network entity may use one QCL at a time for transmission due to analog beam limitations. In one case, each SSB may have two non-overlapping opportunities for Type 0 PDCCH monitoring, and the network entity may transmit a Type 0 PDCCH transmission for each of the two beams. In some cases, the network entity may transmit RMSI, PDCCH, and / or PDSCH for one of these beams (of multiple beams mapped to the same SSB index) at a time. The network entity may alternate these beams over different RMSI sweeps. The UE may detect RMSI for the detected SSB index and may determine the RMSI with the matching beam. In some cases, RMSI for other SSB beams may also be decodable.

[0130] Figure 16

[0014] This is an example of Type 0 PDCCH monitoring using an SSB pattern with gaps and shifted SSB beams in accordance with aspects of the present disclosure. In one example, a Type 0 PDCCH transmission and an RMSI PDSCH transmission are FDMed together with SSBs of the same QCL. The UE may attempt to decode the Type 0 PDCCH transmission that is frequency division multiplexed with the SSBs. In some cases, the UE may count Type 0 PDCCH transmissions for other non-QCL SSBs. In such cases, there is little to no impact on UE processing, and if the UE cannot decode the Type 0 PDCCH and / or RMSI using the wrong QCL, the UE may try again during another SSB burst.

[0131] Figure 17 Illustrated are operations that may include being configured to perform the techniques disclosed herein (such as Figure 717. The communication device 1700 includes various components (e.g., corresponding to means-plus-function components) that perform the operations illustrated in FIG. 17. The communication device 1700 includes a processing system 1702 coupled to a transceiver 1708 (e.g., a transmitter and / or a receiver). The transceiver 1708 is configured to transmit and receive signals for the communication device 1700 (such as the various signals described herein) via an antenna 1710. The processing system 1702 can be configured to perform processing functions for the communication device 1700, including processing signals received and / or to be transmitted by the communication device 1700.

[0132] The processing system 1702 includes a processor 1704 coupled to a computer-readable medium / memory 1712 via a bus 1706. In some aspects, the computer-readable medium / memory 1712 is configured to store instructions (e.g., computer-executable code) that, when executed by the processor 1704, cause the processor 1704 to perform Figure 717. In some aspects, the computer-readable medium / memory 1712 stores code 1714 for determining an SSB pattern that identifies SSB positions for sweeping a set of SSB beams over a plurality of SSB bursts, wherein at least some of the SSB positions have gaps between them, wherein the SSB pattern identifies a subset of the set of SSB beams to be used per SSB burst; and code 1716 for transmitting SSBs over the plurality of SSB bursts according to the SSB pattern. In some aspects, the computer-readable medium / memory 1712 may store code 1718 for signaling information about the pattern via an RMSI IE. In some aspects, the computer-readable medium / memory 1712 may store code 1720 for signaling to at least one UE which SSBs are transmitted in which SSB burst. In certain aspects, the computer-readable medium / memory 1712 may store code 1722 for signaling, for a set of SSB bursts, a set of SSB positions for transmitting an SSB per SSB burst. In certain aspects, the computer-readable medium / memory 1712 may store code 1724 for signaling parameters indicating the SSB positions per SSB burst to allow a UE to perform rate matching in each SSB burst. In certain aspects, the processor 1704 has circuitry configured to implement the code stored in the computer-readable medium / memory 1712. The processor 1704 includes circuitry 1734 for determining an SSB pattern identifying SSB positions for sweeping a set of SSB beams over a plurality of SSB bursts, wherein at least some of the SSB positions have gaps between them, wherein the SSB pattern identifies a subset of the set of SSB beams to be used per SSB burst; and circuitry 1736 for transmitting SSBs over the plurality of SSB bursts according to the SSB pattern. In certain aspects, the processor 1704 may include circuitry 1738 for signaling information about the mode via the RMSI IE. In certain aspects, the processor 1704 may include circuitry 1740 for signaling to at least one UE which SSBs are transmitted in which SSB burst. In certain aspects, the processor 1704 may include circuitry 1742 for signaling, for a set of SSB bursts, a set of SSB positions per SSB burst for transmitting the SSBs. In certain aspects, the processor 1704 may include circuitry 1744 for signaling a parameter indicating the SSB position per SSB burst to allow the UE to perform rate matching in each SSB burst.

[0133] In some cases, the means for transmitting (or means for outputting for transmission) includes a transmitter and / or antenna 234 of BS 110a and / or Figure 17 The circuit system 1734 of the communication device 1700 in FIG. The means for receiving (or the means for obtaining) may include Figure 2 Receiver and / or antenna 234 of BS 110a illustrated in FIG. Means for communicating may include a transmitter, a receiver, or both. Means for generating, means for performing, means for determining, means for taking action, means for determining, means for coordinating may include a processing system, which may include one or more processors, such as Figure 2 The transmit processor 220, TX MIMO processor 230, receive processor 238 and / or controller / processor 240 of BS 110a illustrated in FIG. Figure 17 The processing system 1702 of the communication device 1700 in FIG.

[0134] Figure 18 Illustrated are operations that may include being configured to perform the techniques disclosed herein (such as Figure 8 1800 includes various components (e.g., corresponding to means-plus-function components) for the operations illustrated in the accompanying drawings. The communication device 1800 includes a processing system 1802 coupled to a transceiver 1808 (e.g., a transmitter and / or receiver). The transceiver 1808 is configured to transmit and receive signals for the communication device 1800 (such as the various signals described herein) via an antenna 1810. The processing system 1802 can be configured to perform processing functions for the communication device 1800, including processing signals received and / or to be transmitted by the communication device 1800.

[0135] The processing system 1802 includes a processor 1804 coupled to a computer-readable medium / memory 1812 via a bus 1806. In some aspects, the computer-readable medium / memory 1812 is configured to store instructions (e.g., computer-executable code) that, when executed by the processor 1804, cause the processor 1804 to perform Figure 818 or other operations for performing the various techniques discussed herein for transmitting SSBs according to a pattern with gaps. In certain aspects, the computer-readable medium / memory 1812 stores code 1814 for determining an SSB pattern that identifies SSB positions for a network entity to sweep a set of SSB beams over a plurality of SSB bursts, wherein at least some of the SSB positions have gaps between them, wherein the SSB pattern identifies a subset of the set of SSB beams to be used per SSB burst; and code 1816 for monitoring SSBs over the plurality of SSB bursts according to the SSB pattern. In certain aspects, the computer-readable medium / memory 1812 may store code 1818 for receiving signaling information regarding the pattern from the network entity via an RMSI IE. In certain aspects, the computer-readable medium / memory 1812 may store code 1820 for receiving signaling from the network entity regarding which SSBs are transmitted in which SSB burst. In certain aspects, the computer-readable medium / memory 1812 may store code 1822 for receiving signaling from a network entity regarding parameters indicating SSB positions per burst and performing rate matching in each burst based on the signaled parameters. In certain aspects, the computer-readable medium / memory 1812 may store code 1824 for receiving signaling from a network entity regarding a set of SSB positions per SSB burst for transmitting an SSB for a set of SSB bursts. In certain aspects, the computer-readable medium / memory 1812 may store code. In certain aspects, the processor 1804 may have circuitry configured to implement the code stored in the computer-readable medium / memory 1812. Processor 1804 includes circuitry 1834 for determining an SSB pattern that identifies SSB positions for a network entity to sweep a set of SSB beams over a plurality of SSB bursts, wherein at least some of the SSB positions have gaps between them, wherein the SSB pattern identifies a subset of the set of SSB beams to be used per SSB burst; and circuitry 1836 for monitoring SSBs over the plurality of SSB bursts according to the SSB pattern. In certain aspects, processor 1804 may include circuitry 1838 for receiving signaling information regarding the pattern from the network entity via an RMSI IE. In certain aspects, processor 1804 may include circuitry 1840 for receiving signaling from the network entity regarding which SSBs are transmitted in which SSB burst. In certain aspects, processor 1804 may include circuitry 1842 for receiving signaling from the network entity regarding parameters indicating SSB positions per burst and performing rate matching in each burst based on the signaled parameters. In certain aspects, processor 1804 may include circuitry 1844 for receiving signaling from a network entity regarding, for a set of SSB bursts, a set of SSB positions per SSB burst for transmitting the SSB.

[0136] For example, means for transmitting (or means for outputting for transmission) may include Figure 2 The transmitter unit 254 and / or antenna(s) 252 of the UE 120a illustrated in FIG. Means for receiving (or means for obtaining) may include Figure 2 The receiver and / or antenna 252 and / or Figure 18 The circuit system 1836 of the communication device 1800 in FIG. 1836 may include a transmitter, a receiver, or both. The means for generating, the means for performing, the means for determining, the means for taking action, the means for determining, and the means for coordinating may include a processing system, which may include one or more processors, such as Figure 2 The receive processor 258, transmit processor 264, TX MIMO processor 266 and / or controller / processor 280 of the UE 120a illustrated in FIG. Figure 18 The processing system 1802 of the communication device 1800 in FIG.

[0137] Example aspects

[0138] Implementation examples are described in the following numbered aspects:

[0139] Aspect 1: A method for a network entity to conduct wireless communications, comprising: determining a synchronization signal block (SSB) pattern that identifies SSB positions for sweeping a set of SSB beams over a plurality of SSB bursts, wherein at least some of the SSB positions have gaps between them, wherein the SSB pattern identifies a subset of the set of SSB beams to be used per SSB burst; and transmitting the SSBs over the plurality of SSB bursts according to the pattern.

[0140] Aspect 2: The method of aspect 1 further comprises signaling information about the mode via a remaining minimum system information (RMSI) information element (IE).

[0141] Aspect 3: The method of any one of aspects 1-2, wherein the subset of the set of SSB beams in the SSB pattern to be used per SSB burst is different between each SSB burst.

[0142] Aspect 4: A method as in Aspect 3, wherein the pattern identifies: a first SSB beam subset to be used at a corresponding first SSB position subset in a first SSB burst; and a second SSB beam subset to be used at a corresponding second SSB position subset in a second SSB burst, wherein the first SSB position subset and the second SSB position subset do not overlap.

[0143] Aspect 5: The method of any of aspects 3-4, wherein SSBs at a specific SSB position within an SSB burst share a common quasi-colocation (QCL) assumption.

[0144] Aspect 6: The method of any one of aspects 3-5, further comprising signaling to at least one UE which SSBs are transmitted in which SSB burst.

[0145] Aspect 7: The method of any one of aspects 3-6, further comprising signaling a parameter indicating a SSB position per burst to allow the UE to perform rate matching in each SSB burst.

[0146] Aspect 8: The method of any one of aspects 3-7, wherein each SSB within the first SSB burst and the second SSB burst indicates an offset from the same physical downlink control channel (PDCCH) burst that schedules remaining minimum system information (RMSI).

[0147] Aspect 9: The method of any one of aspects 3-8, wherein the network entity multiplexes a physical downlink control channel (PDCCH) and corresponding remaining minimum system information (RMSI) with SSBs sharing a quasi co-location (QCL) assumption via frequency division multiplexing (FDM).

[0148] Aspect 10: The method of any one of aspects 3-9, wherein if transmission of one SSB burst fails due to a clear channel assessment (CCA) failure, the SSBs of the failed SSB burst are multiplexed in one or more other SSB bursts.

[0149] Aspect 11: The method of any of aspects 1-10, wherein the pattern identifies a set of SSB positions for transmitting SSBs per SSB burst; and different SSB beams per the same SSB position in different SSB bursts.

[0150] Aspect 12: The method of aspect 11 further comprises, for an SSB burst set, signaling a set of SSB positions for transmitting the SSB per SSB burst.

[0151] Aspect 13: The method of any of aspects 11-12, wherein the SSBs at a specific SSB position of every N SSB burst share a common quasi-colocation (QCL) assumption.

[0152] Aspect 14: A method as in any of Aspects 11-13, wherein when a physical downlink control channel (PDCCH) and corresponding remaining minimum system information (RMSI) share the same quasi-co-location assumption with one of the SSBs at the same position in multiple bursts each time, the SSBs at the same position in multiple bursts are mapped to the same PDCCH that schedules the remaining minimum system information (RMSI).

[0153] Aspect 15: A method for wireless communication by a user equipment (UE), comprising: determining a synchronization signal block (SSB) pattern that identifies SSB positions for a network entity to sweep a set of SSB beams over multiple SSB bursts, wherein at least some of the SSB positions have gaps between them, wherein the SSB pattern identifies a subset of the set of SSB beams to be used per SSB burst; and monitoring the SSBs over the multiple SSB bursts according to the pattern.

[0154] Aspect 16: The method of aspect 15 further comprises: receiving signaling information about the mode from the network entity via a remaining minimum system information (RMSI) information element (IE).

[0155] Aspect 17: The method of any one of aspects 15-16, wherein a subset of the set of SSB beams of the SSB pattern to be used per SSB burst is different between each SSB burst.

[0156] Aspect 18: A method as in Aspect 17, wherein the pattern identifies: a first SSB beam subset to be used at a corresponding first SSB position subset in a first SSB burst; and a second SSB beam subset to be used at a corresponding second SSB position subset in a second SSB burst, wherein the first SSB position subset and the second SSB position subset do not overlap.

[0157] Aspect 19: The method of any of aspects 17-18, wherein SSBs at a specific SSB position within an SSB burst share a common quasi-colocation (QCL) assumption.

[0158] Aspect 20: The method of any one of aspects 17-19, further comprising: receiving signaling from the network entity regarding which SSBs are transmitted in which SSB burst.

[0159] Aspect 21: The method of any one of aspects 17-20, further comprising: receiving signaling regarding a parameter indicating a SSB position per burst from the network entity; and performing rate matching in each burst based on the signaled parameter.

[0160] Aspect 22: The method of any one of aspects 17-21, wherein each SSB within the first SSB burst and the second SSB burst indicates an offset from the same physical downlink control channel (PDCCH) burst that schedules remaining minimum system information (RMSI).

[0161] Aspect 23: The method of any one of aspects 17-22, wherein the network entity multiplexes a physical downlink control channel (PDCCH) and corresponding remaining minimum system information (RMSI) with SSBs sharing a quasi co-location (QCL) assumption via frequency division multiplexing (FDM).

[0162] Aspect 24: The method of any one of aspects 17-23, wherein the SSBs of one SSB burst are multiplexed in one or more other SSB bursts.

[0163] Aspect 25: The method of any of aspects 15-24, wherein the pattern identifies a set of SSB positions for transmitting SSBs per SSB burst; and different SSB beams per the same SSB position in different SSB bursts.

[0164] Aspect 26: The method of aspect 25 further comprises: receiving signaling regarding a set of SSB positions for transmitting an SSB per SSB burst from the network entity for the SSB burst set.

[0165] Aspect 27: The method of any of Aspects 25-26, wherein the SSBs at a specific SSB position of every N SSB burst share a common quasi-colocation (QCL) assumption.

[0166] Aspect 28: A method as in any of Aspects 25-27, wherein when a physical downlink control channel (PDCCH) and corresponding remaining minimum system information (RMSI) share the same quasi-co-location assumption with one of the SSBs at the same position in multiple bursts each time, the SSBs at the same position in multiple bursts are mapped to the same PDCCH that schedules the remaining minimum system information (RMSI).

[0167] Aspect 29: An apparatus comprising means for performing the method of any one of aspects 1 to 28.

[0168] Aspect 30: An apparatus comprising: at least one processor and a memory coupled to the at least one processor, the memory comprising code, the code executable by the at least one processor to cause the apparatus to perform the method of any one of aspects 1 to 28.

[0169] Aspect 31: A computer-readable medium having stored thereon computer-executable code for wireless communication, the computer-executable code, when executed by at least one processor, causing an apparatus to perform the method of any one of aspects 1 to 28.

[0170] The techniques described herein may be used for various wireless communication technologies such as NR (e.g., 5G NR), 3GPP Long Term Evolution (LTE), Advanced LTE (LTE-A), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), Time Division Synchronous Code Division Multiple Access (TD-SCDMA), and other networks. The terms "network" and "system" are often used interchangeably. A CDMA network may implement radio technologies such as Universal Terrestrial Radio Access (UTRA) and cdma2000. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. cdma2000 covers IS-2000, IS-95, and IS-856 standards. A TDMA network may implement radio technologies such as Global System for Mobile Communications (GSM). OFDMA networks can implement radio technologies such as NR (e.g., 5G RA), Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDMA, and others. UTRA and E-UTRA are parts of the Universal Mobile Telecommunications System (UMTS). LTE and LTE-A are versions of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization called the 3rd Generation Partnership Project (3GPP). cdma2000 and UMB are described in documents from an organization called the 3rd Generation Partnership Project 2 (3GPP2). NR is an emerging wireless communication technology under development.

[0171] In 3GPP, the term "cell" can refer to the coverage area of ​​a Node B (NB) and / or the NB subsystem serving that coverage area, depending on the context in which the term is used. In NR systems, the terms "cell" and base station (BS), next-generation Node B (gNB or g-Node B), access point (AP), distributed unit (DU), carrier, or transmit reception point (TRP) can be used interchangeably. A BS can provide communication coverage for macro cells, pico cells, femto cells, and / or other types of cells. A macro cell can cover a relatively large geographic area (e.g., several kilometers in radius) and can allow unrestricted access by UEs with service subscriptions. A pico cell can cover a relatively small geographic area and can allow unrestricted access by UEs with service subscriptions. A femto cell can cover a relatively small geographic area (e.g., a residence) and can allow restricted access by UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG), UEs for users in a residence, etc.). A BS for a macro cell can be referred to as a macro BS. A BS for a pico cell may be referred to as a pico BS. A BS for a femto cell may be referred to as a femto BS or a home BS.

[0172] A UE may also be referred to as a mobile station, a terminal, an access terminal, a subscriber unit, a station, a customer premises equipment (CPE), a cellular phone, a smartphone, 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 computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, an appliance, a medical device or medical equipment, a biometric sensor / device, a wearable device (such as a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring, a smart bracelet, etc.)), an entertainment device (e.g., a music device, a video device, a satellite radio, etc.), a vehicle component or sensor, a smart meter / sensor, industrial manufacturing equipment, a global positioning system device, or any other suitable device configured to communicate via a wireless or wired medium. Some UEs may be considered machine type communication (MTC) devices or evolved MTC (eMTC) devices. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, etc., which can communicate with a base station, another device (e.g., a remote device), or some other entity. A wireless node can provide connectivity to or to a network (e.g., a wide area network (such as the Internet) or a cellular network) via, for example, a wired or wireless communication link. Some UEs may be considered Internet of Things (IoT) devices, which may be narrowband IoT (NB-IoT) devices.

[0173] In some examples, access to the air interface may be scheduled. A scheduling entity (e.g., a BS) allocates resources for communication between some or all devices and equipment within its service area or cell. The scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more subordinate entities. That is, for scheduled communications, the subordinate entities utilize the resources allocated by the scheduling entity. The base station is not the only entity that can be used as a scheduling entity. In some examples, a UE may act as a scheduling entity and may schedule resources for one or more subordinate entities (e.g., one or more other UEs), and other UEs may utilize the resources scheduled by the UE for wireless communication. In some examples, a UE may act as a scheduling entity in a peer-to-peer (P2P) network and / or in a mesh network. In the mesh network example, UEs may communicate directly with each other in addition to communicating with the scheduling entity.

[0174] Each method disclosed herein includes one or more steps or actions for implementing the method. These method steps and / or actions can be interchangeable with each other. In other words, unless a specific order of steps or actions is specified, the order and / or use of the specific steps and / or actions can be changed without departing from the scope of the claims.

[0175] As used herein, a phrase referring to "at least one of" a list of items refers to any combination of those items, including single members. As an example, "at least one of a, b, or c" is intended to encompass: a, b, c, ab, ac, bc, and abc, as well as any combination with multiples of the same elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or any other ordering of a, b, and c).

[0176] As used herein, the term "determining" encompasses a wide variety of actions. For example, "determining" may include calculating, computing, processing, deriving, investigating, searching (e.g., searching in a table, database, or another data structure), ascertaining, and the like. Furthermore, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), and the like. Furthermore, "determining" may include resolving, selecting, choosing, establishing, and the like.

[0177] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the universal principles defined herein may be applied to other aspects. Reference to a singular element is not intended to mean "one and only one" (unless specifically stated otherwise), but rather "one or more." Unless otherwise specifically stated, the term "some" refers to one or more. All structural and functional equivalents currently or hereafter known to those of ordinary skill in the art for the elements of the various aspects described throughout this disclosure are expressly incorporated herein by reference and are intended to be covered by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly stated in the claims. No element of a claim should be interpreted under the provisions of 35 USC § 112(f) unless the element is explicitly stated using the phrase "means for..." or, in the case of a method claim, the element is stated using the phrase "step for..."

[0178] The various operations of the methods described above may be performed by any suitable device capable of performing the corresponding functions. These devices may include various hardware and / or software components and / or modules, including but not limited to circuits, application specific integrated circuits (ASICs), or processors. Generally, where there are operations illustrated in the figures, these operations may have corresponding counterpart means-plus-function components with similar numbering.

[0179] The various illustrative logical blocks, modules, and circuits described in conjunction with the present disclosure may be implemented or executed with a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any commercially available processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0180] If implemented in hardware, an example hardware configuration may include a processing system in a wireless node. The processing system may be implemented using a bus architecture. Depending on the specific application and overall design constraints of the processing system, the bus may include any number of interconnecting buses and bridges. The bus may link together various circuits including a processor, a machine-readable medium, and a bus interface. The bus interface may be used to connect a network adapter, etc., to the processing system via the bus. The network adapter may be used to implement signal processing functions at the PHY layer. In a user terminal (see Figure 1 ), a user interface (e.g., a keypad, display, mouse, joystick, etc.) may also be connected to the bus. The bus may also link various other circuits (such as timing sources, peripherals, voltage regulators, power management circuits, etc.), which are well known in the art and therefore will not be described in detail. The processor may be implemented using one or more general and / or special purpose processors. Examples include microprocessors, microcontrollers, DSP processors, and other circuit systems capable of executing software. Those skilled in the art will recognize how to best implement the functionality described with respect to the processing system, depending on the specific application and the overall design constraints imposed on the overall system.

[0181] If implemented in software, each function may be stored as one or more instructions or codes on or transmitted via a computer-readable medium. Software should be broadly interpreted to mean instructions, data, or any combination thereof, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. Computer-readable media includes both computer storage media and communication media, including any media that facilitates the transfer of a computer program from one location to another. The processor may be responsible for managing the bus and general processing, including executing software modules stored on a machine-readable storage medium. A computer-readable storage medium may be coupled to the processor so that the processor can read and write information from / to the storage medium. In an alternative embodiment, the storage medium may be integrated into the processor. As an example, the machine-readable medium may include a transmission line, a carrier modulated by data, and / or a computer-readable storage medium having instructions stored thereon that is separate from the wireless node, all of which may be accessed by the processor via a bus interface. Alternatively or additionally, the machine-readable medium or any portion thereof may be integrated into the processor, such as a cache and / or general register file. As examples, examples of machine-readable storage media may include RAM (random access memory), flash memory, ROM (read-only memory), PROM (programmable read-only memory), EPROM (erasable programmable read-only memory), EEPROM (electrically erasable programmable read-only memory), registers, magnetic disks, optical disks, hard drives, or any other suitable storage media, or any combination thereof. Machine-readable media may be embodied in a computer program product.

[0182] A software module may include a single instruction or many instructions and may be distributed across several different code segments, between different programs, and across multiple storage media. A computer-readable medium may include several software modules. These software modules include instructions that, when executed by a device (such as a processor), cause a processing system to perform various functions. These software modules may include a transmitting module and a receiving module. Each software module may reside in a single storage device or be distributed across multiple storage devices. As an example, when a triggering event occurs, a software module may be loaded from a hard drive into RAM. During the execution of the software module, the processor may load some instructions into a cache to increase access speed. One or more cache lines may then be loaded into a general register file for execution by the processor. When describing the functionality of a software module below, it will be understood that such functionality is implemented by the processor when the processor executes instructions from the software module.

[0183] Likewise, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies (such as infrared (IR), radio, and microwave), then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies (such as infrared, radio, and microwave) are included in the definition of medium. Disk and disc, as used herein, include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Disks typically reproduce data magnetically, while discs reproduce data optically using lasers. Thus, in some aspects, computer-readable media may include non-transitory computer-readable media (e.g., tangible media). Additionally, for other aspects, computer-readable media may include transient computer-readable media (e.g., signals). Combinations of the above should also be included within the scope of computer-readable media.

[0184] Thus, certain aspects may include a computer program product for performing the operations presented herein. For example, such a computer program product may include a computer-readable medium having instructions stored (and / or encoded) thereon, the instructions being executable by one or more processors to perform the operations described herein, such as for performing the operations described herein and in Figure 7 and / or Figure 8 Instructions for the operations explained in .

[0185] In addition, it should be appreciated that the modules and / or other appropriate means for performing the methods and techniques described herein can be downloaded and / or otherwise obtained by the user terminal and / or base station where applicable. For example, such a device can be coupled to a server to facilitate the transfer of the means for performing the methods described herein. Alternatively, the various methods described herein can be provided via a storage device (e.g., RAM, ROM, a physical storage medium such as a compact disc (CD) or floppy disk, etc.) so that once the storage device is coupled to or provided to the user terminal and / or base station, the device can obtain the various methods. In addition, any other suitable technology suitable for providing the methods and techniques described herein to a device can be utilized.

[0186] It will be understood that the claims are not limited to the precise configuration and components illustrated above. Various changes, substitutions and variations may be made in the arrangement, operation and details of the methods and apparatus described above without departing from the scope of the claims.

Claims

1. An apparatus for wireless communication, comprising: at least one processor; as well as At least one memory coupled to the at least one processor, the at least one memory comprising code executable by the at least one processor to cause the apparatus to: determining a synchronization signal block (SSB) pattern identifying SSB positions for sweeping a set of SSB beams over a plurality of SSB bursts with gaps between at least some of the SSB positions, wherein the SSB pattern identifies a different subset of the set of SSB beams to be used per SSB burst according to a periodicity in the plurality of SSB bursts; transmitting a message indicating which SSBs are to be transmitted in which SSB burst of the plurality of SSB bursts; as well as The SSBs are transmitted over the plurality of SSB bursts according to the SSB pattern and the message, wherein each SSB burst in the plurality of SSB bursts is periodically transmitted in a different half-frame.

2. The apparatus of claim 1 , wherein the at least one memory further comprises code executable by the at least one processor to cause the apparatus to perform the following operations: signaling information about the SSB mode via a remaining minimum system information (RMSI) information element (IE).

3. The apparatus of claim 1 , wherein the SSB mode identifier: a first subset of SSB beams to be used at a corresponding first subset of SSB positions in a first SSB burst; and A second subset of SSB beams to be used at a corresponding second subset of SSB positions in a second SSB burst, wherein the first subset of SSB positions and the second subset of SSB positions do not overlap.

4. The apparatus of claim 1, wherein: SSBs at specific SSB positions within an SSB burst share a quasi-colocation (QCL) assumption.

5. The apparatus of claim 1 , wherein the at least one memory further comprises code executable by the at least one processor to cause the apparatus to: Parameters indicating the SSB position per burst are signaled to allow the UE to perform rate matching in each burst.

6. The apparatus of claim 1 , wherein each SSB within the first SSB burst and the second SSB burst indicates an offset from a same physical downlink control channel (PDCCH) burst that schedules remaining minimum system information (RMSI).

7. An apparatus as described in claim 1, wherein the at least one memory further includes code that can be executed by the at least one processor to cause the apparatus to perform the following operations: multiplexing a physical downlink control channel (PDCCH) and corresponding remaining minimum system information (RMSI) with an SSB sharing a quasi co-location (QCL) assumption via frequency division multiplexing (FDM).

8. The apparatus of claim 1 , wherein if transmission of one SSB burst fails due to a clear channel assessment (CCA) failure, the SSBs of the failed SSB burst are multiplexed in one or more other SSB bursts.

9. The apparatus of claim 1 , wherein the SSB mode identifier: a set of SSB positions per SSB burst for transmitting the SSB; and Different SSB beams per same SSB position in different SSB bursts.

10. The apparatus of claim 9, wherein the at least one memory further comprises code executable by the at least one processor to cause the apparatus to: The set of SSB positions for transmitting the SSBs per SSB burst is signaled for the SSB burst set.

11. The apparatus of claim 9, wherein: The SSBs at a specific SSB position every N SSB burst share a common quasi-colocation (QCL) assumption.

12. The apparatus of claim 9 , wherein when a physical downlink control channel (PDCCH) and corresponding remaining minimum system information (RMSI) share the same quasi-co-location assumption with one of the SSBs at the same position in a plurality of bursts each time, the SSBs at the same position in a plurality of bursts are mapped to the same PDCCH that schedules the remaining minimum system information (RMSI).

13. An apparatus for wireless communication, comprising: at least one processor; as well as At least one memory coupled to the at least one processor, the at least one memory comprising code executable by the at least one processor to cause the apparatus to: determining a synchronization signal block (SSB) pattern that identifies SSB positions for a network entity to sweep a set of SSB beams over a plurality of SSB bursts, wherein at least some of the SSB positions have gaps therebetween, wherein the SSB pattern identifies a different subset of the set of SSB beams to be used per SSB burst according to a periodicity in the plurality of SSB bursts; receiving a message indicating which SSBs are to be transmitted in which of the SSB bursts; as well as SSBs are monitored over the plurality of SSB bursts according to the SSB pattern and the message, wherein each SSB burst in the plurality of SSB bursts is monitored in a different half-frame.

14. The apparatus of claim 13, wherein the at least one memory further comprises code executable by the at least one processor to cause the apparatus to: Signaling information regarding the SSB mode is received from the network entity via a Remaining Minimum System Information (RMSI) Information Element (IE).

15. The apparatus of claim 13, wherein the SSB mode identifier: a first subset of SSB beams to be used at a corresponding first subset of SSB positions in a first SSB burst; and A second subset of SSB beams to be used at a corresponding second subset of SSB positions in a second SSB burst, wherein the first subset of SSB positions and the second subset of SSB positions do not overlap.

16. The apparatus of claim 13, wherein: SSBs at specific SSB positions within an SSB burst share a quasi-colocation (QCL) assumption.

17. The apparatus of claim 13, wherein the at least one memory further comprises code executable by the at least one processor to cause the apparatus to: receiving a parameter indicating a position of an SSB per burst from the network entity; and Rate matching in each burst is performed based on the parameters.

18. The apparatus of claim 13, wherein each SSB within the first SSB burst and the second SSB burst indicates an offset from a same physical downlink control channel (PDCCH) burst that schedules remaining minimum system information (RMSI).

19. The apparatus of claim 13, wherein the at least one memory further comprises code executable by the at least one processor to cause the network entity to perform the following operations: multiplexing a physical downlink control channel (PDCCH) and corresponding remaining minimum system information (RMSI) with an SSB sharing a quasi co-location (QCL) assumption via frequency division multiplexing (FDM).

20. The apparatus of claim 13, wherein: The SSBs of one SSB burst are multiplexed in one or more other SSB bursts.

21. The apparatus of claim 13, wherein the SSB mode identifier: a set of SSB positions per SSB burst for transmitting the SSB; and Different SSB beams per same SSB position in different SSB bursts.

22. The apparatus of claim 21 , wherein the at least one memory further comprises code executable by the at least one processor to cause the apparatus to: Signaling is received from the network entity regarding the set of SSB positions per SSB burst for transmitting an SSB for a set of SSB bursts.

23. The apparatus of claim 21, wherein: The SSBs at a specific SSB position every N SSB burst share a common quasi-colocation (QCL) assumption.

24. The apparatus of claim 21 , wherein when a physical downlink control channel (PDCCH) and corresponding remaining minimum system information (RMSI) share the same quasi-co-location assumption with one of the SSBs at the same position in a plurality of bursts each time, the SSBs at the same position in the plurality of bursts are mapped to the same PDCCH that schedules the remaining minimum system information (RMSI).

25. A method for wireless communication by a network entity, comprising: determining a synchronization signal block (SSB) pattern identifying SSB positions for sweeping a set of SSB beams over a plurality of SSB bursts with gaps between at least some of the SSB positions, wherein the SSB pattern identifies a different subset of the set of SSB beams to be used per SSB burst according to a periodicity in the plurality of SSB bursts; transmitting a message indicating which SSBs are to be transmitted in which SSB burst of the plurality of SSB bursts; as well as SSBs are transmitted over the plurality of SSB bursts according to the SSB pattern and the message, wherein each SSB burst in the plurality of SSB bursts is periodically transmitted in a different half-frame.

26. The method of claim 25, further comprising: Information about the SSB mode is signaled via a Remaining Minimum System Information (RMSI) Information Element (IE).

27. The method of claim 25, wherein the SSB mode identifier: a first subset of SSB beams to be used at a corresponding first subset of SSB positions in a first SSB burst; and A second subset of SSB beams to be used at a corresponding second subset of SSB positions in a second SSB burst, wherein the first subset of SSB positions and the second subset of SSB positions do not overlap.

28. The method of claim 25, wherein: The SSBs at a specific SSB position within an SSB burst share a quasi-colocation (QCL) assumption.

29. The method of claim 25, further comprising: Parameters indicating the SSB position per burst are signaled to allow the UE to perform rate matching in each burst.

30. The method of claim 25, wherein each SSB within the first SSB burst and the second SSB burst indicates an offset from a same physical downlink control channel (PDCCH) burst that schedules remaining minimum system information (RMSI).

31. The method of claim 25, further comprising: The physical downlink control channel (PDCCH) and the corresponding remaining minimum system information (RMSI) are multiplexed together with the SSBs sharing the quasi co-location (QCL) assumption via frequency division multiplexing (FDM).

32. The method of claim 25, wherein if transmission of one SSB burst fails due to a clear channel assessment (CCA) failure, the SSBs of the failed SSB burst are multiplexed in one or more other SSB bursts.

33. The method of claim 25, wherein the SSB mode identifier: a set of SSB positions per SSB burst for transmitting the SSB; and Different SSB beams per same SSB position in different SSB bursts.

34. The method of claim 33, further comprising: The set of SSB positions for transmitting the SSBs per SSB burst is signaled for the SSB burst set.

35. The method of claim 33, wherein: The SSBs at a specific SSB position every N SSB burst share a common quasi-colocation (QCL) assumption.

36. A method as claimed in claim 33, wherein when a physical downlink control channel (PDCCH) and the corresponding remaining minimum system information (RMSI) share the same quasi-co-location assumption with one of the SSBs at the same position in multiple bursts each time, the SSBs at the same position in multiple bursts are mapped to the same PDCCH that schedules the remaining minimum system information (RMSI).

37. A method for wireless communication by a user equipment (UE), comprising: determining a synchronization signal block (SSB) pattern that identifies SSB positions for a network entity to sweep a set of SSB beams over a plurality of SSB bursts, wherein at least some of the SSB positions have gaps therebetween, wherein the SSB pattern identifies a different subset of the set of SSB beams to be used per SSB burst according to a periodicity in the plurality of SSB bursts; receiving a message indicating which SSBs are to be transmitted in which SSB burst of the plurality of SSB bursts; as well as SSBs are monitored over the plurality of SSB bursts according to the SSB pattern and the message, wherein each SSB burst in the plurality of SSB bursts is monitored in a different half-frame.

38. The method of claim 37, further comprising: Signaling information regarding the SSB mode is received from the network entity via a Remaining Minimum System Information (RMSI) Information Element (IE).

39. The method of claim 37, wherein the SSB mode identifier: a first subset of SSB beams to be used at a corresponding first subset of SSB positions in a first SSB burst; and A second subset of SSB beams to be used at a corresponding second subset of SSB positions in a second SSB burst, wherein the first subset of SSB positions and the second subset of SSB positions do not overlap.

40. The method of claim 37, wherein: The SSBs at a specific SSB position within an SSB burst share a quasi-colocation (QCL) assumption.

41. The method of claim 37, further comprising: receiving, from the network entity, a parameter indicating a position of a SSB per burst; as well as Rate matching in each burst is performed based on the parameters.

42. The method of claim 37, wherein each SSB within the first SSB burst and the second SSB burst indicates an offset from the same physical downlink control channel (PDCCH) burst that schedules remaining minimum system information (RMSI).

43. The method of claim 37, further comprising: The physical downlink control channel (PDCCH) and the corresponding remaining minimum system information (RMSI) are multiplexed together with the SSBs sharing the quasi co-location (QCL) assumption via frequency division multiplexing (FDM).

44. The method of claim 37, wherein: The SSBs of one SSB burst are multiplexed in one or more other SSB bursts.

45. The method of claim 37, wherein the SSB mode identifier: a set of SSB positions per SSB burst for transmitting the SSB; and Different SSB beams per same SSB position in different SSB bursts.

46. ​​The method of claim 45, further comprising: Signaling is received from the network entity regarding the set of SSB positions per SSB burst for transmitting an SSB for a set of SSB bursts.

47. The method of claim 45, wherein: The SSBs at a specific SSB position every N SSB burst share a common quasi-colocation (QCL) assumption.

48. A method as claimed in claim 45, wherein when a physical downlink control channel (PDCCH) and the corresponding remaining minimum system information (RMSI) share the same quasi-co-location assumption with one of the SSBs at the same position in multiple bursts each time, the SSBs at the same position in multiple bursts are mapped to the same PDCCH that schedules the remaining minimum system information (RMSI).

Images