Patent Description:
The following relates to wireless communications, including frequency configuration for control resource set (CORESET) in non-terrestrial networks (NTNs).

These systems may employ technologies such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple-access communications system may include one or more base stations or one or more network access nodes, each simultaneously supporting communication for multiple communication devices, which may be otherwise known as user equipment (UE).

In some examples, a UE may perform a random access procedure to gain access to a network. If multiple UEs attempt to perform the random access procedure at a same time using overlapping frequencies, contention may occur.

<CIT> discloses a synchronization signal/physical broadcasting channel (SS/PBCH) block comprising a PBCH that carries a master information block (MIB) including an SIB <NUM> CORESET configuration, wherein the SIB1 CORESET configuration comprises a frequency location of the CORESET associated with the SS/PBCH block.

The described techniques relate to improved methods, systems, devices, and apparatuses that support frequency configuration for control resource set (CORESET) in non-terrestrial networks (NTNs). Generally, the described techniques provide for a user equipment (UE) to be configured with an offset for a CORESET relative to a synchronization signal block (SSB) based on a CORESET bandwidth, a combination of a first and second parameter associated with the SSB, or both. For example, an NTN device (e.g., a satellite) may transmit, to a UE, at a first frequency an SSB that indicates a second frequency of a CORESET relative to the SSB, where the second frequency is based on one or more of: a CORESET bandwidth, a combination of a first parameter associated with a first portion of the SSB and a second parameter associated with a second portion of the SSB, or both. The UE may monitor the CORESET at the indicated second frequency for a downlink control channel transmission. The NTN device may transmit, to the UE, a downlink control channel transmission over the CORESET. The NTN device may transmit, to the UE, system information (SI) based on the downlink control channel transmission.

A non-terrestrial network (NTN) device or other base station may use multiple beams to communicate with multiple user equipment (UE), and each beam may operate on a disjoint frequency interval from at least one other beam (e.g., beams may have differing bandwidth parts (BWPs)). To enable a UE to gain access to the NTN device, the NTN device may transmit a synchronization signal block (SSB) to the UE. Once the UE decodes the SSB, the UE may determine a location and bandwidth of an initial control resource set (CORESET), which may also be referred to as CORESET #<NUM>. The UE may decode a physical downlink control channel (PDCCH) specified by initial CORESET, may determine resources for receiving a system information block (SIB), and may receive the SIB accordingly. The SIB may configure an initial downlink BWP and an initial uplink BWP which the UE may use to perform random access with the NTN device. The initial downlink BWP may include the frequencies spanned by the corresponding initial CORESET.

In some examples, the SSBs for different beams may be transmitted on a common frequency interval, which may enable UEs to perform initial cell search quicker. However, using a common frequency interval may result in the initial CORESETs for each SSB overlapping at least partially in frequency, as the initial CORESETs may have a value relative to their respective SSBs. As described herein, each initial downlink BWP for performing a random access procedure may include the frequencies of each respective initial CORESET. Thus, one or more of the initial downlink BWPs may overlap in frequency if one or more of the initial CORESETs overlap in frequency. As multiple UEs may perform a random access procedure over different initial downlink BWPs that overlap in frequency, there may be an increased chance that contention may occur (e.g., the transmissions received at or transmitted from the UEs may collide or interfere).

To mitigate contention that occurs at least partially due to overlap between CORESETs in frequency, the NTN device and UE may perform methods to enable the CORESETs to be disjoint from each other in frequency. For instance, the UE may use an offset that is based on a bandwidth of the initial CORESET and an SSB index configured such that CORESETs associated with neighboring beams do not overlap. Additionally, or alternatively, the UE may receive a first and second indicator from the SSB that the UE may combine to determine an offset for a CORESET such that the CORESET does not overlap with CORESETs associated with neighboring beams. Additionally, or alternatively, the UE may receive an offset that is configured such that the initial CORESET for the UE is different from the initial CORESET of a neighboring beam by at least a bandwidth of the initial CORESET of the neighboring beam.

Aspects of the disclosure are initially described in the context of wireless communications systems. Additional aspects of the disclosure are described in the context of CORESET offset schemes, a beam configuration scheme, and a process flow. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to frequency configuration for CORESET in NTNs.

<FIG> illustrates an example of a wireless communications system <NUM> that supports frequency configuration for CORESET in NTNs in accordance with aspects of the present disclosure. The wireless communications system <NUM> may include one or more base stations <NUM>, one or more UEs <NUM>, and a core network <NUM>. In some examples, the wireless communications system <NUM> may be a Long Term Evolution (LTE) network, an LTE-Advanced (LTE-A) network, an LTE-A Pro network, or a New Radio (NR) network. In some examples, the wireless communications system <NUM> may support enhanced broadband communications, ultra-reliable (e.g., mission critical) communications, low latency communications, communications with low-cost and low-complexity devices, or any combination thereof.

The base stations <NUM> may communicate with the core network <NUM>, or with one another, or both. For example, the base stations <NUM> may interface with the core network <NUM> through one or more backhaul links <NUM> (e.g., via an S1, N2, N3, or other interface). The base stations <NUM> may communicate with one another over the backhaul links <NUM> (e.g., via an X2, Xn, or other interface) either directly (e.g., directly between base stations <NUM>), or indirectly (e.g., via core network <NUM>), or both. In some examples, the backhaul links <NUM> may be or include one or more wireless links.

For example, a carrier used for a communication link <NUM> may include a portion of a radio frequency spectrum band (e.g., a BWP) that is operated according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR).

In a system employing MCM techniques, a resource element may consist of one symbol period (e.g., a duration of one modulation symbol) and one subcarrier, where the symbol period and subcarrier spacing (SCS) are inversely related.

The time intervals for the base stations <NUM> or the UEs <NUM> may be expressed in multiples of a basic time unit which may, for example, refer to a sampling period of Ts = <NUM>/(Δfmax ▪ Nf) seconds, where Δfmax may represent the maximum supported SCS, and Nf may represent the maximum supported discrete Fourier transform (DFT) size. Time intervals of a communications resource may be organized according to radio frames each having a specified duration (e.g., <NUM> milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from <NUM> to <NUM>).

Alternatively, each frame may include a variable number of slots, and the number of slots may depend on SCS. The duration of a symbol period may depend on the SCS or frequency band of operation.

A subframe, a slot, a mini-slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communications system <NUM> and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., the number of symbol periods in a TTI) may be variable. Additionally, or alternatively, the smallest scheduling unit of the wireless communications system <NUM> may be dynamically selected (e.g., in bursts of shortened TTIs (sTTIs)).

A control region (e.g., a CORESET) for a physical control channel may be defined by a number of symbol periods and may extend across the system bandwidth or a subset of the system bandwidth of the carrier.

The core network <NUM> may be an evolved packet core (EPC) or <NUM> core (5GC), which may include at least one control plane entity that manages access and mobility (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) and at least one user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW), a Packet Data Network (PDN) gateway (P-GW), or a user plane function (UPF)). The control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management for the UEs <NUM> served by the base stations <NUM> associated with the core network <NUM>. User IP packets may be transferred through the user plane entity, which may provide IP address allocation as well as other functions. The user plane entity may be connected to the network operators IP services <NUM>. The network operators IP services <NUM> may include access to the Internet, Intranet(s), an IP Multimedia Subsystem (IMS), or a Packet-Switched Streaming Service.

The wireless communications system <NUM> may operate using one or more frequency bands, typically in the range of <NUM> megahertz (MHz) to <NUM> gigahertz (GHz). Generally, the region from <NUM> to <NUM> is known as the ultra-high frequency (UHF) region or decimeter band because the wavelengths range from approximately one decimeter to one meter in length. The UHF waves may be blocked or redirected by buildings and environmental features, but the waves may penetrate structures sufficiently for a macro cell to provide service to the UEs <NUM> located indoors. The transmission of UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than <NUM> kilometers) compared to transmission using the smaller frequencies and longer waves of the high frequency (HF) or very high frequency (VHF) portion of the spectrum below <NUM>.

A base station <NUM> or a UE <NUM> may be equipped with multiple antennas, which may be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of a base station <NUM> or a UE <NUM> may be located within one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming. In some examples, antennas or antenna arrays associated with a base station <NUM> may be located in diverse geographic locations. Additionally, or alternatively, an antenna panel may support radio frequency beamforming for a signal transmitted via an antenna port.

In the wireless communications system <NUM> of <FIG>, a UE <NUM> may communicate with a base station <NUM> via a NTN device. The UE <NUM> may be configured with an offset for a CORESET relative to an SSB based on a CORESET bandwidth, a combination of a first and second parameter associated with the SSB, or both. For example, an NTN device (e.g., a satellite, base station <NUM>) may transmit, to a UE <NUM>, at a first frequency an SSB that indicates a second frequency of a CORESET relative to the SSB, where the second frequency is based on one or more of: a CORESET bandwidth, a combination of a first parameter associated with a first portion of the SSB and a second parameter associated with a second portion of the SSB, or both. The UE <NUM> may monitor the CORESET at the indicated second frequency for a downlink control channel transmission. The NTN device may transmit, to the UE <NUM>, a downlink control channel transmission over the CORESET. The NTN device may transmit, to the UE <NUM>, system information (SI) based on the downlink control channel transmission.

<FIG> illustrates an example of a wireless communications system <NUM> that supports frequency configuration for CORESET in NTNs in accordance with aspects of the present disclosure. In some examples, wireless communications system <NUM> may implement aspects of wireless communications system <NUM>. For example, UEs <NUM>-a, <NUM>-b and <NUM>-c may be examples of UEs <NUM> as described with reference to <FIG>.

In some examples, NTN device <NUM> may be an example of a satellite (e.g., a low-earth orbit (LEO) satellite) or a high-altitude platform station (HAPS) (e.g., a balloon). The NTN device <NUM> may use multiple antennas to form multiple beams <NUM> (e.g., multiple narrow beams). The beams <NUM> may operate on disjoint frequency intervals (e.g., may have different BWPs), which may provide interference mitigation. To lessen or minimize the occurrence of cell handover, the beams <NUM> from an NTN device <NUM> may be configured as a single cell.

In some examples, NTN device <NUM> may transmit an SSB <NUM> over one or more of the beams <NUM>. A UE <NUM> may receive the SSB and may decode the SSB <NUM> to obtain a master information block (MIB) that indicates the frequency location and bandwidth of an initial coreset <NUM> (i.e., CORESET #<NUM>) and an initial search space (i.e., search space #<NUM>). The frequency location may be relative to a lowest frequency of the SSB <NUM>. The UE <NUM> may decode a PDCCH transmission determined by (e.g., specified by) the initial CORESET <NUM> and the initial search space. The PDCCH transmission may allocate resources for a SIB (e.g., a SIB referred to as SIB1) on physical downlink shared channel (PDSCH). The UE <NUM> may receive and decode the SIB, which may configure an initial downlink BWP and an initial uplink BWP at the UE <NUM>. The initial downlink BWP may include the initial CORESET <NUM>. If the initial downlink BWP is not configured, the initial downlink BWP may have a same frequency interval as the initial CORESET <NUM>. The UE <NUM> may perform random access on the initial uplink BWP and the initial downlink BWP.

The SSBs <NUM> for different beams <NUM> may be transmitted on a common frequency interval, which may enable UEs <NUM> to perform an initial cell search quicker. For instance, if a common frequency interval is represented as BWP <NUM>, then a beam <NUM> may switch from a second frequency interval (i.e., BWP <NUM>) to BWP <NUM> for transmitting the SSB <NUM>.

As described herein, the location of the initial CORESET <NUM> may be equal to the SSB frequency plus an offset. In some examples, the offset may take one or more predefined values. For instance, if the SCS of the SSB <NUM> is <NUM> and the SCS of the PDCCH is <NUM> and the initial CORESET <NUM> has a bandwidth of <NUM> resource blocks (RB), the offset may be equal to <NUM> RBs, <NUM> RBs, or <NUM> RBs. Multiple beams from an NTN device <NUM> (e.g., a satellite, a HAPS) may be configured to be within a same cell. In cases where one initial downlink BWP is present per cell, overlap between multiple instances of the initial CORESET <NUM> may not occur. As such, offsets that differ from each other by amounts small enough such that overlap between CORESETs occurs (e.g., <NUM> RBs, <NUM> RBs, <NUM> RBs) may be used. However, in cases where there are multiple initial downlink BWPs per cell, overlap may occur if the offsets are too small. For instance, using the common frequency interval may result in overlapping initial downlink BWPs, even if the beams <NUM> have different CORESET #<NUM> configurations in the MIBs (e.g., configured in an information element (IE) referred to as controlResourceSetZero). When multiple instances of the initial CORESET <NUM> overlap in frequency, the corresponding initial downlink BWPs may also overlap in frequency. When the initial downlink BWPs overlap with each other in frequency, contention between UEs <NUM> may occur more frequently.

In general a beam <NUM> may serve one or more UEs <NUM>. For instance, the beam may cover an area as large as <NUM> by <NUM> and may serve multiple UEs <NUM> within that area. However, having too many UEs <NUM> on overlapping initial downlink BWPs may result in increased contention when the UEs <NUM> perform random access procedures on their respective initial downlink BWPs. The methods as described herein may enable downlink BWPs to be disjoint from each other (e.g., non-overlapping in frequency), which may distribute the random access traffic load in a manner that reduces contention.

In one example, NTN device <NUM> may transmit SSB <NUM>-a to UE <NUM>-a over beam <NUM>-a, SSB <NUM>-b to UE <NUM>-b over beam <NUM>-b, and SSB <NUM>-c to UE <NUM>-c over beam <NUM>-c. SSB <NUM>-a may indicate a frequency location for initial CORESET <NUM>-a, SSB <NUM>-b may indicate a frequency location for initial CORESET <NUM>-b, and SSB <NUM>-c may indicate a frequency location for initial CORESET <NUM>-c. For instance, SSB <NUM>-a may indicate a frequency offset of <NUM> RBs relative to SSB <NUM>-a, SSB <NUM>-b may indicate a frequency offset of <NUM> RBs relative to SSB <NUM>-b, and SSB <NUM>-c may indicate a frequency offset of <NUM> RBs relative to SSB <NUM>-c. However, each initial CORESET <NUM> may have a bandwidth that is large enough such that initial CORESET <NUM>-a overlaps with at least one of initial CORESETs <NUM>-b and <NUM>-c. As such, an initial downlink BWP associated with initial CORESET <NUM>-a may overlap with an initial downlink BWP associated with one of initial CORESETs <NUM>-b or <NUM>-c. Thus, when UE <NUM>-a performs a random access procedure over its respective initial downlink BWP, UE <NUM>-a may be more likely to experience contention with UEs <NUM>-b and/or <NUM>-c.

An example of configurations for CORESET #<NUM> may be given in the following table:.

In a first example, to prevent overlap between CORESETs <NUM> (e.g., CORESET #<NUM>) over different beams <NUM>, NTN device <NUM> may determine a frequency offset for the initial CORESET <NUM> relative to an SSB <NUM> based on an SSB index and a bandwidth of each CORESET <NUM>. In such examples, a UE <NUM> may determine the frequency of CORESET <NUM> by adding the SSB frequency plus a frequency offset that is a function of the SSB index and the bandwidth of the CORESET <NUM> (e.g., the latter which may be referred to as Δf ). The SSB index (e.g., ssb-index) may be numbered consecutively (e.g., <NUM>, <NUM>, <NUM>,.

In some examples, the bandwidth of the CORESET <NUM> may be pre-configured or may be obtained through another communication network (e.g., LTE). Additionally, or alternatively, the bandwidth may depend on a geographical location of the UE <NUM>. For instance, if a UE <NUM> is located in or within a threshold distance of an urban area (e.g., an area with higher user density and/or population density), the magnitude of the offset may be larger than when the UE <NUM> is in or within a threshold distance of a rural area (e.g., an area with lower user density and/or population density). If a UE <NUM> receives multiple SSBs <NUM>, the UE <NUM> may do soft combining in decoding the MIB of the SSB <NUM>. Additionally, or alternatively, the offset may be indicated in a physical broadcast channel (PBCH) payload of an SSB <NUM>. For instance, one spare bit in a MIB may be used to indicate the offset. The offset may equal a first bandwidth of an initial downlink BWP if the bit is <NUM> and may equal a second bandwidth (e.g., of an initial downlink BWP) if the bit is <NUM>. Alternatively, the PBCH (e.g., which may include a MIB) in the SSB <NUM> may include additional bits, where each combination of the bits indicates a bandwidth of a downlink BWP, and that bandwidth may be assigned to the offset. The bits may be added to the MIB or may be outside the MIB but still in the PBCH payload (e.g., in physical layer bits). Additionally, or alternatively, each demodulation reference signal (DMRS) sequence associated with the SSB <NUM> may indicate a unique offset value.

In some examples, the CORESET <NUM> of non-neighboring beams <NUM> may use the same frequency, which may be referred to as frequency spatial reuse. In some such examples, the network (e.g., via NTN device <NUM>) may signal a parameter N corresponding to frequency spatial reuse. In some examples, a UE <NUM> may use the parameter N to calculate or determine the frequency offset Δf. In some examples, the frequency location of the initial CORESET <NUM> may be determined as SSBfrequency + α * modulus(SSBindex, N) * Δf,
where SSBfrequency corresponds to a lowest frequency of an SSB <NUM>, α has a value whose absolute value is greater than or equal to <NUM>, SSBindex corresponds to an SSB index associated with the SSB <NUM>, N corresponds to frequency spatial reuse (e.g., N ≥ <NUM>, such as <NUM>), and Δf corresponds to the bandwidth of CORESET #<NUM> and/or an associated initial downlink BWP. Additional details about the first example may be described elsewhere herein, for example, with reference to <FIG>, <FIG>.

According to the invention, a UE <NUM> determines the frequency of an initial CORESET <NUM> as a frequency of an SSB <NUM> plus an offset which is a function (e.g., a combination) of two or more parameters, each indicated by an indicator (e.g., in the SSB <NUM>). According to the invention, a first indicator is associated with a first portion of the SSB <NUM> (e.g., a first field of the SSB <NUM>) and indicates a first parameter and a second identifier is associated with a second portion of the SSB <NUM> (e.g., a second field of the SSB <NUM>) and indicates a second parameter. The first parameter, according to the invention, is a frequency offset derived from an IE in a MIB of the SSB <NUM> (e.g., a controlResourceSetZero IE). The second indicator is carried in a PBCH transmission associated with the SSB <NUM>. According to the invention, one spare bit in a MIB is used to indicate the second parameter. The second parameter equals <NUM> if the bit is <NUM> and is equal a number greater than <NUM> if the bit is <NUM>. Alternatively, a PBCH (e.g., which may include a MIB) associated with the SSB <NUM> may include additional bits, where each combination of the bits indicates a unique value of the second parameter. The bits may be added to the MIB or may be outside the MIB but still in the PBCH payload (e.g., in physical layer bits). Additionally, or alternatively, each DMRS sequence associated with the SSB <NUM> may indicate a unique value for the second parameter. Alternatively, if the second indicator is absent, the second parameter may be set to a function of the bandwidth of the initial CORESET <NUM>, where the bandwidth may be indicated by the CORESET #<NUM> configuration (the IE controlResourceSetZero) in the MIB of an SSB <NUM>. According to the invention, the CORESET #<NUM> location may be calculated as SSBfrequency + first_parameter * second_parameter, where SSBfrequency may be the lowest frequency of the SSB <NUM>, first_parameter may be a frequency offset derived from an IE in the MIB (e.g., controlResourceSetZero), and second_parameter may be a non-negative integer indicated by the second indicator. Additional details about the second example may be described elsewhere herein, for example, with reference to <FIG>.

In a third example, the network (e.g., NTN device <NUM>) may configure the offsets of initial CORESETs <NUM> based on the bandwidths of the initial CORESETs. For instance,
the frequency occupied by an nth initial CORESET <NUM> may be represented by the interval Fn = [fSSB + offn,fSSB + offn + BWn], where fSSB may be the lowest frequency of an SSB <NUM>, offn may be a frequency offset for the nth initial CORESET <NUM>, and BWn may be the bandwidth of the nth initial CORESET <NUM>. The NTN device may configure frequency offsets on the condition where offn+<NUM> - offn ≥ BWn. Configuring the frequency offset in this manner may ensure that Fn+<NUM> and Fn do not overlap (e.g., may ensure that possible initial CORESETs <NUM> do not overlap in frequency). Additional details about the third example may be described elsewhere herein, for example, with reference to <FIG>.

By enabling CORESETs to be disjoint from each other in frequency, the methods as described herein may reduce the occurrence of contention when UEs communicating over beams <NUM> are performing a random access procedure. Reducing contention may improve the efficiency of performing communications.

<FIG> illustrates an example of a CORESET offset scheme <NUM> that supports frequency configuration for CORESET in NTNs in accordance with aspects of the present disclosure. In some examples, CORESET offset scheme <NUM> may implement aspects of wireless communications systems <NUM> and/or <NUM>. For example, CORESET offset scheme <NUM> may represent a communications scheme implemented by an NTN device <NUM> such that CORESETs <NUM> configured at neighboring beams <NUM> are offset from each other in a frequency non-overlapping fashion.

A first UE <NUM> may receive SSB <NUM>-a, where SSB <NUM>-a may indicate a frequency location for initial CORESET <NUM>-a. A second UE <NUM> may receive SSB <NUM>-b, where SSB <NUM>-b may indicate a frequency location for initial CORESET <NUM>-b. A third UE <NUM> may receive SSB <NUM>-c, where SSB <NUM>-c may indicate a frequency location for initial CORESET <NUM>-c.

According to the first example (e.g., as described with reference to <FIG>), the SSBs <NUM>-a, <NUM>-b, and <NUM>-c may indicate a respective SSB index and CORESET bandwidth Δf. In some examples, the CORESET bandwidth Δf indicated by each SSB <NUM> may be the same, but the SSB indices may differ. Accordingly, the frequency location for initial CORESET <NUM>-a may differ from the frequency locations for initial CORESETs <NUM>-b and <NUM>-c such that CORESETs <NUM>-a, <NUM>-b, and <NUM>-c are non-overlapping in frequency.

Additionally, or alternatively, according to the second example (e.g., as described with reference to <FIG>), the SSBs <NUM>-a, <NUM>-b, and <NUM>-c may indicate a first indicator corresponding to a first parameter and a second indicator corresponding to a second parameter. In some examples, the value of the first parameter indicated by the first indicator for each SSB <NUM> may be the same, but the value of the second parameter may differ. Accordingly, the frequency location of initial CORESET <NUM>-a may differ from the frequency locations for initial CORESETs <NUM>-b and <NUM>-c such that CORESETs <NUM>-a, <NUM>-b, and <NUM>-c are non-overlapping in frequency.

Additionally, or alternatively, according to the third example (e.g., as described with reference to <FIG>), the SSBs <NUM>-a, <NUM>-b, and <NUM>-c may indicate offsets configured according to the condition offn+<NUM> - offn ≥ BWn. As such, the frequency location of initial CORESET <NUM>-a may differ from the frequency locations for initial CORESETs <NUM>-b and <NUM>-c such that CORESETs <NUM>-a, <NUM>-b, and <NUM>-c are non-overlapping in frequency.

<FIG> illustrates an example of a beam configuration scheme <NUM>-a and <FIG> illustrates an example of a CORESET offset scheme <NUM>-b that supports frequency configuration for CORESET in NTNs in accordance with aspects of the present disclosure. In some examples, beam configuration scheme <NUM>-a and CORESET offset scheme <NUM>-b may implement aspects of wireless communications systems <NUM> and/or <NUM>. For instance, beam configuration scheme <NUM>-a may represent a configuration of beams for an NTN device <NUM> and CORESET offset scheme <NUM>-b may represent a communications scheme implemented by an NTN device <NUM> such that CORESETs configured at neighboring beams <NUM> are offset from each other in a frequency non-overlapping fashion.

In the present example, an NTN device <NUM> may have eight beams <NUM> (e.g., <NUM>-a, <NUM>-b, <NUM>-c, <NUM>-d, <NUM>-e, <NUM>-f, <NUM>-g, and <NUM>-h). Beams <NUM>-a and <NUM>-e may operate in a first BWP (i.e., BWP <NUM>); beams <NUM>-b and <NUM>-f may operate in a second BWP (i.e., BWP <NUM>); beams <NUM>-c and <NUM>-g may operate in a third BWP (i.e., BWP <NUM>); and beams <NUM>-d and <NUM>-h may operate in a fourth BWP (i.e., BWP <NUM>).

Beams <NUM>-a, <NUM>-b, <NUM>-c, <NUM>-d, <NUM>-e, <NUM>-f, <NUM>-g, and <NUM>-h may transmit respective SSBs that indicate frequency locations for CORESETs <NUM>-a, <NUM>-b, <NUM>-c, <NUM>-d, <NUM>-e, <NUM>-f, <NUM>-g, and <NUM>-h, respectively. According to the methods described with reference to the first example in <FIG>, CORESETs <NUM>-a, <NUM>-b, <NUM>-c, and <NUM>-d may each be disjoint in frequency from one another and CORESETs <NUM>-e, <NUM>-f, <NUM>-g, and <NUM>-h may likewise be disjoint from each other in frequency from one another (e.g., due to being associated with different SSB indices). However, overlap in frequency may occur between CORESETs <NUM>-a and <NUM>-e; <NUM>-b and <NUM>-f; <NUM>-c and <NUM>-g; and <NUM>-d and <NUM>-h (e.g., due to the frequency spatial reuse N being equal to <NUM>).

<FIG> illustrates an example of a process flow <NUM> that supports frequency configuration for CORESET in NTNs in accordance with aspects of the present disclosure. In some examples, process flow <NUM> may implement aspects of wireless communications systems <NUM> and/or <NUM>. For example, UE <NUM>-d may be an example of a UE <NUM> as described with reference to <FIG> and NTN device <NUM>-a may be an example of an NTN device <NUM> as described with reference to <FIG>.

At <NUM>, NTN device <NUM>-a may transmit at a first frequency an SSB that indicates a second frequency of a CORESET relative to the SSB. The second frequency may be based on one or more of: a CORESET bandwidth, a combination of a first parameter associated with a first portion of the SSB and a second parameter associated with a second portion of the SSB, or both. UE <NUM>-d. In some examples, receiving at the first frequency the SSB may include UE <NUM>-d receiving an indication of a frequency offset, where the frequency offset is based on the CORESET bandwidth. In some examples, the frequency offset may be based on an SSB index, a user density at or within a threshold distance of a geographic location of UE <NUM>-d, or both. In some examples, receiving the indication of the frequency offset may include receiving a MIB of the SSB, where the MIB includes the indication of the frequency offset. In some such examples, the indication of the frequency offset may include an explicit indication of the frequency offset (e.g., a field of the MIB indicating the frequency offset). In some examples, the SSB may be associated with a DMRS sequence that maps to the second frequency or to the frequency offset. In some examples, the CORESET bandwidth may include a bandwidth of the CORESET.

In some examples NTN device <NUM>-a may transmit and UE <NUM>-d may receive at the first frequency a second SSB prior to the SSB. In some such examples, the second SSB may indicate a third frequency of a second CORESET relative to the second SSB, where the CORESET bandwidth includes a bandwidth of the second CORESET. In some examples, UE <NUM>-d may receive a MIB, where the first portion of the SSB includes a first field of the MIB. In some such examples, the second portion of the SSB includes one or more of: a spare bit of the MIB, a second field of the MIB, or a field of a PBCH transmission that is outside of the MIB. In some such examples, the first field of the MIB is associated with the CORESET. In some examples, the SSB is associated with a DMRS sequence that maps to the second parameter. In some examples, UE <NUM>-d may determine that the second parameter is absent from the SSB and may determine the second parameter based on the CORESET bandwidth and the absence of the second parameter from the SSB. In some examples, UE <NUM>-d determining the frequency offset may include UE <NUM>-d combining the first parameter and the second parameter. In some such examples, NTN device <NUM>-a may transmit and UE <NUM>-d may receive a second downlink control channel transmission over the second CORESET. Additionally, NTN device <NUM>-a may transmit UE <NUM>-d may receive second SI based on the second downlink control channel transmission.

In some examples, the second frequency and the fourth frequency being configured such that the CORESET and the second CORESET are non-overlapping in frequency includes the second frequency and the fourth frequency being associated with a same CORESET bandwidth and different SSB indices. In some examples, the second frequency and the fourth frequency being configured such that the CORESET and the second CORESET are non-overlapping in frequency includes a value of the first parameter of the first portion of the SSB being the same as a value of the first parameter of the first portion of the second SSB, and a value of the second parameter of the second portion of the SSB being different from a value of the second parameter of the second portion of the second SSB. In some examples, the second frequency and the fourth frequency being configured such that the CORESET and the second CORESET are non-overlapping in frequency includes the second frequency and the fourth frequency differing at least the CORESET bandwidth. In some examples, the first frequency and the third frequency include a same frequency.

In some examples, NTN device <NUM>-a may transmit at a third frequency a second SSB that indicates a fourth frequency of a second CORESET relative to the second SSB, where the fourth frequency is based on one or more of: a bandwidth of the second CORESET, a combination of the first parameter associated with a first portion of the second SSB and the second parameter associated with a second portion of the second SSB, or both. In some such examples, the SSB block at least partially overlaps the second SSB in frequency and the second frequency and the fourth frequency are configured such that the CORESET and the second CORESET are non-overlapping in frequency based on the SSB overlapping with the second SSB.

At <NUM>, UE <NUM>-d may determine the second frequency. In some examples, UE <NUM>-d may determine the second frequency based on the first frequency and a received frequency offset. Additionally, or alternatively, UE <NUM>-d may determine a frequency offset based on the combination of the first parameter and the second parameter and may determine the second frequency based on the first frequency and the frequency offset.

At <NUM>, UE <NUM>-d may monitor the CORESET at the indicated second frequency for a downlink control channel transmission.

At <NUM>, NTN device <NUM>-a may transmit a downlink control channel transmission (e.g., a PDCCH transmission) over the CORESET. UE <NUM>-d may receive the downlink control channel transmission.

At <NUM>, NTN device <NUM>-a may transmit SI (e.g., a SIB) based on the downlink control channel transmission.

In some examples, UE <NUM>-d may determine an initial downlink BWP that overlaps with the CORESET in frequency based on receiving the system information. In some examples, UE <NUM>-d may perform a random access procedure over the initial downlink BWP.

<FIG> shows a block diagram <NUM> of a device <NUM> that supports frequency configuration for CORESET in NTNs in accordance with aspects of the present disclosure. The device <NUM> may be an example of aspects of a UE <NUM> as described herein. The device <NUM> may include a receiver <NUM>, a communication manager <NUM>, and a transmitter <NUM>. The device <NUM> may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).

The receiver <NUM> may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to frequency configuration for CORESET in NTNs, etc.). Information may be passed on to other components of the device <NUM>. The receiver <NUM> may be an example of aspects of the transceiver <NUM> described with reference to <FIG>. The receiver <NUM> may utilize a single antenna or a set of antennas.

The communication manager <NUM> may receive at a first frequency an SSB that indicates a second frequency of a CORESET relative to the SSB, where the second frequency is based on one or more of: a CORESET bandwidth, a combination of a first parameter associated with a first portion of the SSB and a second parameter associated with a second portion of the SSB, or both; monitor the CORESET at the indicated second frequency for a downlink control channel transmission; and receive SI based on the downlink control channel transmission. The communication manager <NUM> may be an example of aspects of the communication manager <NUM> described herein.

The communication manager <NUM>, or its sub-components, may be implemented in hardware, code (e.g., software or firmware) executed by a processor, or any combination thereof. If implemented in code executed by a processor, the functions of the communication manager <NUM>, or its sub-components may be executed by 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, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described in the present disclosure.

The communication manager <NUM>, or its sub-components, may be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations by one or more physical components. In some examples, the communication manager <NUM>, or its sub-components, may be a separate and distinct component in accordance with various aspects of the present disclosure. In some examples, the communication manager <NUM>, or its sub-components, may be combined with one or more other hardware components, including but not limited to an input/output (I/O) component, a transceiver, a network server, another computing device, one or more other components described in the present disclosure, or a combination thereof in accordance with various aspects of the present disclosure.

In some examples, the methods performed by the device <NUM> may have one or more advantages. For instance, by receiving an SSB that indicates an offset based on the CORESET bandwidth or the combination of the first and second parameters, the device <NUM> may be less likely to experience contention with another wireless device (e.g., a UE <NUM>) when performing a random access procedure. As such, on average, the device <NUM> may perform the random access procedure more quickly (e.g., the random access procedure may be associated with less latency or a reduced signaling overhead).

<FIG> shows a block diagram <NUM> of a device <NUM> that supports frequency configuration for CORESET in NTNs in accordance with aspects of the present disclosure. The device <NUM> may be an example of aspects of a device <NUM>, or a UE <NUM> as described herein. The device <NUM> may include a receiver <NUM>, a communication manager <NUM>, and a transmitter <NUM>. The device <NUM> may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).

The communication manager <NUM> may be an example of aspects of the communication manager <NUM> as described herein. The communication manager <NUM> may include an SSB receiver <NUM>, a CORESET monitoring component <NUM>, and a SIB receiver <NUM>. The communication manager <NUM> may be an example of aspects of the communication manager <NUM> described herein.

The SSB receiver <NUM> may receive at a first frequency an SSB that indicates a second frequency of a CORESET relative to the SSB, where the second frequency is based on one or more of: a CORESET bandwidth, a combination of a first parameter associated with a first portion of the SSB and a second parameter associated with a second portion of the SSB, or both.

The CORESET monitoring component <NUM> may monitor the CORESET at the indicated second frequency for a downlink control channel transmission.

The SIB receiver <NUM> may receive SI based on the downlink control channel transmission.

<FIG> shows a block diagram <NUM> of a communication manager <NUM> that supports frequency configuration for CORESET in NTNs in accordance with aspects of the present disclosure. The communication manager <NUM> may be an example of aspects of a communication manager <NUM>, a communication manager <NUM>, or a communication manager <NUM> described herein. The communication manager <NUM> may include an SSB receiver <NUM>, a CORESET monitoring component <NUM>, a SIB receiver <NUM>, a frequency determination component <NUM>, a parameter determination component <NUM>, a BWP overlap component <NUM>, and a random access procedure component <NUM>. Each of these modules may communicate, directly or indirectly, with one another (e.g., via one or more buses).

The SSB receiver <NUM> may receive at a first frequency an SSB that indicates a second frequency of a CORESET relative to the SSB, where the second frequency is based on one or more of: a CORESET bandwidth, a combination of a first parameter associated with a first portion of the SSB and a second parameter associated with a second portion of the SSB, or both. In some examples, the SSB receiver <NUM> may receive an indication of a frequency offset, where the frequency offset is based on the CORESET bandwidth. In some examples, the frequency offset is further based on an SSB index. In some examples, the frequency offset is further based on a user density at or within a threshold distance of a geographic location of the UE.

In some examples, the SSB receiver <NUM> may receive a MIB of the SSB, where the MIB includes the indication of the frequency offset. In some cases, the indication of the frequency offset includes an explicit indication of the frequency offset. In some examples, the SSB is associated with a DMRS sequence that maps to the second frequency. In some cases, the CORESET bandwidth includes a bandwidth of the CORESET. In some examples, the SSB receiver <NUM> may receive at the first frequency a second SSB prior to the SSB, where the second SSB indicates a third frequency of a second CORESET relative to the second SSB, where the CORESET bandwidth includes a bandwidth of the second CORESET.

In some examples, the SSB receiver <NUM> may receive a MIB, where the first portion of the SSB includes a first field of the MIB, and where the second portion of the SSB includes one or more of: a spare bit of the MIB, a second field of the MIB, or a field of a PBCH transmission that is outside of the MIB. In some examples, the first field of the MIB is associated with CORESET. In some examples, the SSB is associated with a DMRS sequence that maps to the second parameter.

The frequency determination component <NUM> may determine the second frequency based on the first frequency and the received frequency offset. In some examples, the frequency determination component <NUM> may determine a frequency offset based on the combination of the first parameter associated with the first portion of the SSB and the second parameter associated with the second portion of the SSB. In some examples, the frequency determination component <NUM> may determine the second frequency based on the first frequency and the frequency offset. In some examples, the frequency determination component <NUM> may combine the first parameter and the second parameter.

The parameter determination component <NUM> may determine that the second parameter is absent from the SSB. In some examples, the parameter determination component <NUM> may determine the second parameter based on the CORESET bandwidth and the absence of the second parameter from the SSB.

The BWP overlap component <NUM> may determine an initial downlink BWP that overlaps with the CORESET in frequency based on receiving the system information.

The random access procedure component <NUM> may perform a random access procedure over the initial downlink BWP.

<FIG> shows a diagram of a system <NUM> including a device <NUM> that supports frequency configuration for CORESET in NTNs in accordance with aspects of the present disclosure. The device <NUM> may be an example of or include the components of device <NUM>, device <NUM>, or a UE <NUM> as described herein. The device <NUM> may include components for bi-directional voice and data communications including components for transmitting and receiving communications, including a communication manager <NUM>, a transceiver <NUM>, an antenna <NUM>, memory <NUM>, and a processor <NUM>. These components may be in electronic communication via or coupled with one or more buses (e.g., bus <NUM>).

The communication manager <NUM> may receive at a first frequency an SSB that indicates a second frequency of a CORESET relative to the SSB, where the second frequency is based on one or more of: a CORESET bandwidth, a combination of a first parameter associated with a first portion of the SSB and a second parameter associated with a second portion of the SSB, or both; monitor the CORESET at the indicated second frequency for a downlink control channel transmission; and receive SI based on the downlink control channel transmission.

In some cases, the memory <NUM> may contain, among other things, a basic IO system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.

The processor <NUM> may include an intelligent hardware device, (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor <NUM> may be configured to operate a memory array using a memory controller. In other cases, a memory controller may be integrated into the processor <NUM>. The processor <NUM> may be configured to execute computer-readable instructions stored in a memory (e.g., the memory <NUM>) to cause the device <NUM> to perform various functions (e.g., functions or tasks supporting frequency configuration for CORESET in NTNs).

<FIG> shows a block diagram <NUM> of a device <NUM> that supports frequency configuration for CORESET in NTNs in accordance with aspects of the present disclosure. The device <NUM> may be an example of aspects of a base station <NUM> and/or an NTN device <NUM> as described herein. The device <NUM> may include a receiver <NUM>, a communication manager <NUM>, and a transmitter <NUM>. The device <NUM> may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).

The communication manager <NUM> may transmit at a first frequency an SSB that indicates a second frequency of a CORESET relative to the SSB, where the second frequency is based on one or more of: a CORESET bandwidth, a combination of a first parameter associated with a first portion of the SSB and a second parameter associated with a second portion of the SSB, or both; transmit a downlink control channel transmission over the CORESET; and transmit SI based on the downlink control channel transmission. The communication manager <NUM> may be an example of aspects of the communication manager <NUM> described herein.

The communication manager <NUM>, or its sub-components, may be implemented in hardware, code (e.g., software or firmware) executed by a processor, or any combination thereof. If implemented in code executed by a processor, the functions of the communication manager <NUM>, or its sub-components may be executed by a general-purpose processor, a DSP, an application-specific integrated circuit (ASIC), a FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described in the present disclosure.

The communication manager <NUM>, or its sub-components, may be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations by one or more physical components. In some examples, the communication manager <NUM>, or its sub-components, may be a separate and distinct component in accordance with various aspects of the present disclosure. In some examples, the communication manager <NUM>, or its sub-components, may be combined with one or more other hardware components, including but not limited to an I/O component, a transceiver, a network server, another computing device, one or more other components described in the present disclosure, or a combination thereof in accordance with various aspects of the present disclosure.

In some examples, the methods performed by the device <NUM> may have one or more advantages. For instance, by transmitting an SSB that indicates an offset based on the CORESET bandwidth or the combination of the first and second parameters, the device <NUM> may distribute the CORESETs for multiple UEs such that the CORESETs are disjoint in frequency. When the CORESETs are disjoint in frequency, the UEs may be less likely to experience contention when performing a random access procedure with the device <NUM>. As such, the device <NUM> may improve the efficiency of wireless communications by reducing the likelihood of the UEs experiencing contention and may therefore provide an improved user experience. In such cases, the device <NUM> may, on average, handle a greater number of UEs during a random access procedure than other devices which do not ensure that the CORESETs are disjoint in frequency.

<FIG> shows a block diagram <NUM> of a device <NUM> that supports frequency configuration for CORESET in NTNs in accordance with aspects of the present disclosure. The device <NUM> may be an example of aspects of a device <NUM>, a base station <NUM>, or an NTN device <NUM> as described herein. The device <NUM> may include a receiver <NUM>, a communication manager <NUM>, and a transmitter <NUM>. The device <NUM> may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).

The communication manager <NUM> may be an example of aspects of the communication manager <NUM> as described herein. The communication manager <NUM> may include an SSB transmitter <NUM>, a downlink control channel transmitter <NUM>, and a SIB transmitter <NUM>. The communication manager <NUM> may be an example of aspects of the communication manager <NUM> described herein.

The SSB transmitter <NUM> may transmit at a first frequency an SSB that indicates a second frequency of a CORESET relative to the SSB, where the second frequency is based on one or more of: a CORESET bandwidth, a combination of a first parameter associated with a first portion of the SSB and a second parameter associated with a second portion of the SSB, or both.

The SIB transmitter <NUM> may transmit SI based on the downlink control channel transmission.

The downlink control channel transmitter <NUM> may transmit a downlink control channel transmission over the CORESET.

<FIG> shows a block diagram <NUM> of a communication manager <NUM> that supports frequency configuration for CORESET in NTNs in accordance with aspects of the present disclosure. The communication manager <NUM> may be an example of aspects of a communication manager <NUM>, a communication manager <NUM>, or a communication manager <NUM> described herein. The communication manager <NUM> may include an SSB transmitter <NUM>, a downlink control channel transmitter <NUM>, a SIB transmitter <NUM>, a frequency determination component <NUM>, a parameter determination component <NUM>, a BWP overlap component <NUM>, and a random access procedure component <NUM>. Each of these modules may communicate, directly or indirectly, with one another (e.g., via one or more buses).

The SSB transmitter <NUM> may transmit at a first frequency an SSB that indicates a second frequency of a CORESET relative to the SSB, where the second frequency is based on one or more of: a CORESET bandwidth, a combination of a first parameter associated with a first portion of the SSB and a second parameter associated with a second portion of the SSB, or both. In some examples, the SSB transmitter <NUM> may transmit an indication of a frequency offset. In some examples, the SSB transmitter <NUM> may transmit, to the UE, the SSB.

In some examples, the SSB transmitter <NUM> may transmit a MIB of the SSB, where the MIB includes the indication of the frequency offset. In some examples, the indication of the frequency offset includes an explicit indication of the frequency offset. In some example, the SSB is associated with a DMRS sequence that maps to the second frequency. In some cases, the CORESET bandwidth includes a bandwidth of the CORESET. In some examples, the SSB transmitter <NUM> may transmit at the first frequency a second SSB prior to the SSB, where the second SSB indicates a third frequency of a second CORESET relative to the second SSB, where the CORESET bandwidth includes a bandwidth of the second CORESET.

In some examples, the SSB transmitter <NUM> may transmit a MIB, where the first portion of the SSB includes a first field of the MIB, and where the second portion of the SSB includes one or more of: a spare bit of the MIB, a second field of the MIB, or a field of a PBCH transmission that is outside of the MIB. In some examples, the first field of the MIB is associated with the CORESET. In some examples, the SSB is associated with a DMRS sequence that maps to a value of the second parameter. In some examples, the SSB transmitter <NUM> may transmit at a third frequency a second SSB that indicates a fourth frequency of a second CORESET relative to the second SSB, where the fourth frequency is based on one or more of: a bandwidth of the second CORESET, a combination of the first parameter associated with a first portion of the second SSB and the second parameter associated with a second portion of the second SSB, or both, where the SSB at least partially overlaps the second SSB in frequency, and where the second frequency and the fourth frequency are configured such that the CORESET and the second CORESET are non-overlapping in frequency based on the SSB overlapping with the second SSB.

In some cases, the second frequency and the fourth frequency being configured such that the CORESET and the second CORESET are non-overlapping in frequency includes the second frequency and the fourth frequency being associated with a same CORESET bandwidth and different SSB indices. In some cases, the second frequency and the fourth frequency being configured such that the CORESET and the second CORESET are non-overlapping in frequency includes a value of the first parameter of the first portion of the SSB being the same as the a value of the first parameter of the first portion of the second SSB and a value of the second parameter of the second portion of the SSB being different from a value of the second parameter of the second portion of the second SSB. In some cases, the second frequency and the fourth frequency being configured such that the CORESET and the second CORESET are non-overlapping in frequency includes the second frequency and the fourth frequency differing by at least the CORESET bandwidth. In some examples, the first frequency and the third frequency may be a same frequency.

The downlink control channel transmitter <NUM> may transmit a downlink control channel transmission over the CORESET. In some examples, the downlink control channel transmitter <NUM> may transmit a second downlink control channel transmission over the second CORESET.

The SIB transmitter <NUM> may transmit SI based on the downlink control channel transmission. In some examples, the SIB transmitter <NUM> may transmit second SI based on the second downlink control channel transmission.

The frequency determination component <NUM> may determine the second frequency based on the first frequency and a frequency offset, where the frequency offset is based on the CORESET bandwidth. In some examples, the frequency determination component <NUM> may determine the frequency offset based on an SSB index. In some examples, the frequency determination component <NUM> may determine the frequency offset based on a user density at or within a threshold distance of a geographic location of a UE. In some examples, the frequency determination component <NUM> may determine a frequency offset based on the combination of the first parameter associated with the first portion of the SSB and the second parameter associated with the second portion of the SSB. In some examples, the frequency determination component <NUM> may determine the second frequency based on the first frequency and the frequency offset. In some examples, the frequency determination component <NUM> may determine the second frequency based on combining the first parameter and the second parameter.

The parameter determination component <NUM> may determine a value of the second parameter based on the CORESET bandwidth.

The BWP overlap component <NUM> may determine an initial downlink BWP that overlaps with the CORESET in frequency.

The random access procedure component <NUM> may perform a random access procedure over the initial downlink BWP based on transmitting the system information.

<FIG> shows a diagram of a system <NUM> including a device <NUM> that supports frequency configuration for CORESET in NTNs in accordance with aspects of the present disclosure. The device <NUM> may be an example of or include the components of device <NUM>, device <NUM>, a base station <NUM>, an NTN device <NUM> as described herein. The device <NUM> may include components for bi-directional voice and data communications including components for transmitting and receiving communications, including a communication manager <NUM>, a network communications manager <NUM>, a transceiver <NUM>, an antenna <NUM>, memory <NUM>, a processor <NUM>, and an inter-station communications manager <NUM>. These components may be in electronic communication via or coupled with one or more buses (e.g., bus <NUM>).

The communication manager <NUM> may transmit at a first frequency an SSB that indicates a second frequency of a CORESET relative to the SSB, where the second frequency is based on one or more of: a CORESET bandwidth, a combination of a first parameter associated with a first portion of the SSB and a second parameter associated with a second portion of the SSB, or both; transmit a downlink control channel transmission over the CORESET; and transmit SI based on the downlink control channel transmission.

The memory <NUM> may include RAM and ROM.

In some examples, the methods performed by the device <NUM> may have one or more advantages. For instance, by transmitting an SSB that indicates an offset based on the CORESET bandwidth or the combination of the first and second parameters, the device <NUM> may distribute the CORESETs for multiple UEs such that the CORESETs are disjoint in frequency. When the CORESETs are disjoint in frequency, the UEs may be less likely to experience contention when performing a random access procedure with the device <NUM>. As such, the device <NUM> may improve the efficiency of wireless communications by reducing the likelihood of the UEs experiencing contention and may therefore provide an improved user experience. In such cases, the device <NUM> may, on average, handle a greater number of UEs during a random access procedure than other devices which do not ensure that the CORESETs are disjoint in frequency.

<FIG> shows a flowchart illustrating a method <NUM> that supports frequency configuration for CORESET in NTNs in accordance with aspects of the present disclosure. The operations of method <NUM> may be implemented by a UE <NUM> or its components as described herein. For example, the operations of method <NUM> may be performed by a communication manager as described with reference to <FIG>. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, a UE may perform aspects of the described functions using special-purpose hardware.

At <NUM>, the UE may receive at a first frequency an SSB that indicates a second frequency of a CORESET relative to the SSB, where the second frequency is based on one or more of: a CORESET bandwidth, a combination of a first parameter associated with a first portion of the SSB and a second parameter associated with a second portion of the SSB, or both. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by an SSB receiver as described with reference to <FIG>.

At <NUM>, the UE may monitor the CORESET at the indicated second frequency for a downlink control channel transmission. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a CORESET monitoring component as described with reference to <FIG>.

At <NUM>, the UE may receive SI based on the downlink control channel transmission. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a SIB receiver as described with reference to <FIG>.

At <NUM>, the UE may receive at a first frequency an SSB that includes an indication of a frequency offset, where the frequency offset is based on a CORESET bandwidth. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by an SSB receiver as described with reference to <FIG>.

At <NUM>, the UE may determine a second frequency relative to the SSB based on the first frequency and the received frequency offset. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a frequency determination component as described with reference to <FIG>.

At <NUM>, the UE may receive at a first frequency a SSB. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by an SSB receiver as described with reference to <FIG>.

At <NUM>, the UE may determine a frequency offset based on a combination of a first parameter associated with a first portion of the SSB and a second parameter associated with a second portion of the SSB. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a frequency determination component as described with reference to <FIG>.

At <NUM>, the UE may determine the second frequency based on the first frequency and the frequency offset. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a frequency determination component as described with reference to <FIG>.

<FIG> shows a flowchart illustrating a method <NUM> that supports frequency configuration for CORESET in NTNs in accordance with aspects of the present disclosure. The operations of method <NUM> may be implemented by a base station <NUM>, an NTN device, or their components as described herein. For example, the operations of method <NUM> may be performed by a communication manager as described with reference to <FIG>. In some examples, a base station or NTN device may execute a set of instructions to control the functional elements of the base station or NTN device to perform the described functions. Additionally, or alternatively, a base station or NTN device may perform aspects of the described functions using special-purpose hardware.

At <NUM>, the base station or the NTN device may transmit at a first frequency an SSB that indicates a second frequency of a CORESET relative to the SSB, where the second frequency is based on one or more of: a CORESET bandwidth, a combination of a first parameter associated with a first portion of the SSB and a second parameter associated with a second portion of the SSB, or both. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by an SSB transmitter as described with reference to <FIG>.

At <NUM>, the base station or the NTN device may transmit a downlink control channel transmission over the CORESET. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a downlink control channel transmitter as described with reference to <FIG>.

At <NUM>, the base station or the NTN device may transmit SI based on the downlink control channel transmission. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a SIB transmitter as described with reference to <FIG>.

For example, due to the nature of software, functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these.

A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. 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, 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 computer-readable medium.

For example, an example step that is described as "based on condition A" may be based on both a condition A and a condition B without departing from the scope of the present disclosure.

The term "example" used herein means "serving as an example, instance, or illustration," and not "preferred" or "advantageous over other examples. In some instances, known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described examples.

Claim 1:
An apparatus for wireless communication, comprising:
means for receiving at a first frequency a synchronization signal block that indicates a second frequency of a control resource set relative to the synchronization signal block, SSB (<NUM>), wherein the second frequency is based at least in part on a combination of a first parameter associated with a first portion of the synchronization signal block and a second parameter associated with a second portion of the synchronization signal block, wherein the first parameter is a frequency offset derived from an information element, IE, in a master information block, MIB, of the SSB (<NUM>) and wherein the second parameter is equal <NUM> if a spare bit in the MIB is o and is equal a number greater than <NUM> if the spare bit is <NUM>, and wherein the second frequency is calculated as the first frequency plus the first parameter multiplied with the second parameter;
means for monitoring the control resource set at the indicated second frequency for a downlink control channel transmission; and
means for receiving system information based at least in part on the downlink control channel transmission.