Signaling for system information blocks

Abstract

Some wireless communications systems include terrestrial network (TN) nodes or non-terrestrial network (NTN) nodes (e.g., satellites) for communicating with user equipment (UE). Support for power sharing between beams and reducing the overhead of a downlink channel (e.g., a synchronization signal block (SSB) or one or more system information blocks (SIBs)) can be sought to increase the number of supported beams. In some approaches, to enhance SIB reception, a UE can monitor a plurality of control resource sets (CORESETs) including a first CORESET and at least one repetition of the first CORESET. The repetition of the first CORESET can be positioned relative to the first CORESET. The UE can use the repetition of the first CORESET to communicate a message (e.g., a SIB) with a network entity. Some approaches can support slot aggregation for a PDSCH carrying a SIB or limiting monitoring occasions based on an SSB.

Description

[0001] Cross-references

[0002] This patent application claims priority to U.S. Patent Application No. 19 / 089,992, entitled “SIGNALING FOR SYSTEM INFORMATION BLOCKS,” filed March 25, 2025, and U.S. Provisional Patent Application No. 63 / 574,146, entitled “SIGNALING FOR SYSTEM INFORMATION BLOCKS,” filed April 3, 2024, each of which has been assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

[0003] The following content relates to wireless communications, including signaling used for system information blocks. Background Technology

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, and broadcasting. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth-generation (4G) systems (such as Long Term Evolution (LTE) systems, LTE-A Advanced (LTE-A) systems, or LTE-A Pro systems) and fifth-generation (5G) systems (which may be referred to as New Radio (NR) systems). 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 Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each supporting wireless communication for communication devices, which may be referred to as User Equipment (UE). Summary of the Invention

[0005] Some wireless communication systems include non-terrestrial network (NTN) nodes (e.g., satellites) for communication with user equipment (UEs) located on or near the Earth's surface. Due to limited power and a limited number of radio frequency (RF) chains, a relatively small portion of a satellite beam (e.g., 5%, 10%, 20%, or 30%) can be used for transmission simultaneously. Given the limitations of limited power and RF chains, support for power sharing between beams and reducing the overhead of downlink channels (e.g., synchronization signal blocks (SSBs), system information blocks 1 (SIB1), or other system information blocks (SIBs) (e.g., system information block 19 (SIB19)) can be sought to increase the number of supported beams. To enhance SIB reception, the UE can monitor the search space during a monitoring period to acquire multiple control resource sets (CORESETs), which include a first CORESET and at least one repetition of that first CORESET. The UE can obtain information from network entities (e.g., N) via a second resource element (RE). (Examples include TN nodes or satellites) UEs receive repetitions of the first core set during monitoring, where these second resource elements (REs) are located at a time and frequency defined relative to the first RE associated with the first core set. The repetition of the first core set may include control messages for sending scheduling messages (e.g., PDSCH or SIB1). For example, the core set may include information for scheduling SIBs (e.g., SIB1, SIB19) (e.g., PDCCH, downlink control information (DCI), or other information). The UE may use the information indicated by the control messages included in the repetition of the first core set to communicate this message to network entities.

[0006] A method for wireless communication by a UE is described. The method may include: monitoring a search space during a monitoring period to obtain a set of multiple cores, the set of multiple cores including a first core and a second core; receiving the second core from a network entity via a second RE during the monitoring period, the second REs being located at a time and frequency defined relative to a first RE associated with the first core, the second core including a control message for scheduling the transmission of a message; and communicating the message to the network entity using information indicated by the control message included in the second core.

[0007] A UE for wireless communication is described. The UE may include one or more memories storing processor-executable code and one or more processors coupled to the one or more memories. The one or more processors may operate individually or jointly to execute code such that the UE: monitors a search space during a monitoring period to obtain a set of multiple cores, the set of multiple cores including a first core and a second core; receives the second core from a network entity via a second RE during the monitoring period, the second REs being located at a time and frequency defined relative to a first RE associated with the first core, the second core including a control message for scheduling the transmission of a message; and communicates the message to the network entity using information indicated by the control message included in the second core.

[0008] Another UE for wireless communication is described. This UE may include: components for monitoring a search space during a monitoring period to obtain a set of multiple cores, the set of multiple cores including a first core and a second core; components for receiving the second core from a network entity via second REs during the monitoring period, the second REs being located at a time and frequency defined relative to a first RE associated with the first core, the second core including a control message for scheduling the transmission of a message; and components for communicating the message to a network entity using information indicated by the control message included in the second core.

[0009] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to: monitor a search space during a monitoring period to obtain a set of multiple cores, the set of multiple cores including a first core and a second core; receive the second core from a network entity via second REs located at a time and frequency defined relative to a first RE associated with the first core, the second core including a control message for scheduling the transmission of a message; and communicate the message to the network entity using information indicated by the control message included in the second core.

[0010] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the message includes SIB1 in the Physical Downlink Shared Channel (PDSCH), which can be scheduled based on the set of multiple CORESETs, and the SIB1 indicates the repetition of CORESETs of a type that can be specific to one or more search spaces.

[0011] The methods described herein, examples of UEs and non-transitory computer-readable media may also include repetitive operations, features, components or instructions for receiving the CORESET based on the SIB1.

[0012] Some examples of the methods, UEs, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for the following steps: detecting a failure to decode the first CORESET via the first RE associated with the first CORESET, and in response to the failure to decode the first CORESET, monitoring the second CORESET via the second RE during the monitoring period based on the assumption that CORESET repetition can be activated.

[0013] In some examples of the methods, UEs, and non-transitory computer-readable media described herein, the monitoring of the second CORESET uses blind decoding without prior indication that CORESET repetition can be activated.

[0014] The methods described herein, examples of UEs and non-transitory computer-readable media may also include operations, features, components or instructions for decoding the Physical Downlink Control Channel (PDCCH) using the combination of the first CORESET and the second CORESET.

[0015] In some examples of the methods described herein, UEs, and nontransitory computer-readable media, the second CORESET may be indicated by a cyclic redundancy check (CRC) mask, demodulation reference signal (DMRS) scrambling, or coded DCI bit scrambling.

[0016] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the second CORESET may be indicated by the number of first REs associated with the first CORESET that satisfy a first threshold, by the bandwidth or number of REs associated with the first CORESET that satisfy a second threshold, or by conveying the first CORESET in a specific frequency band.

[0017] The methods described herein, examples of UEs, and nontransitory computer-readable media may also include operations, features, components, or instructions for the following steps: receiving a handover command for a target cell that indicates that CORESET repetition can be activated; and receiving neighboring cell information associated with neighboring cells of the target cell that indicates CORESET repetition information for the neighboring cells.

[0018] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, for the format of a PDCCH scrambled by a System Information Radio Network Temporary Identifier (SI-RNTI) in a specific frequency band, one or more bits of the PDCCH associated with the first CORESET may be fixed or removed.

[0019] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the DCI associated with the first CORESET indicates the number of time slots used to aggregate the PDSCH carrying the SIB.

[0020] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the PDSCH can be scheduled via a common search space (CSS).

[0021] The methods described herein, examples of UEs, and non-transitory computer-readable media may also include operations, features, components, or instructions for receiving synchronization signal blocks (SSBs), wherein the search space may be monitored based on the timing of the monitoring occurring within a threshold period following the SSB.

[0022] A method for wireless communication by a network entity is described. The method may include: transmitting a set of multiple cores in a search space during a monitoring period, the set of multiple cores including a first core and a second core, wherein the second core is transmitted via second REs located at a time and frequency defined relative to a first RE associated with the first core, the second core including a control message for scheduling the transmission of a message; and communicating the message to a UE using information indicated by the control message included in the second core.

[0023] A network entity for wireless communication is described. The network entity may include: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories. The one or more processors may operate individually or jointly to execute code such that the network entity: transmits a set of multiple cores in a search space during a monitoring period, the set of multiple cores including a first core and a second core, wherein the second core is transmitted via second REs located at a time and frequency defined relative to a first RE associated with the first core, the second core including a control message for scheduling the transmission of a message; and communicates the message to a UE using information indicated by the control message included in the second core.

[0024] Another network entity for wireless communication is described. This network entity may include: components for transmitting a set of multiple cores in a search space during a monitoring period, the set of multiple cores including a first core and a second core, wherein the second core is transmitted via second REs located at a time and frequency defined relative to a first RE associated with the first core, the second core including a control message for scheduling the transmission of a message; and components for communicating the message to a UE using information indicated by the control message included in the second core.

[0025] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to: transmit a set of multiple cores in a search space during a monitoring period, the set of multiple cores including a first core and a second core, wherein the second core is transmitted via second REs located at a time and frequency defined relative to a first RE associated with the first core, the second core including a control message for scheduling the transmission of a message; and communicate the message to a UE using information indicated by the control message included in the second core.

[0026] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the message includes SIB1 in a PDSCH that can be scheduled based on a set of multiple CORESETs, and the SIB1 indicates a repetition of a CORESET of a type that can be specific to one or more search spaces.

[0027] Examples of the methods, network entities, and non-transitory computer-readable media described herein may also include repetitive operations, features, components, or instructions for sending the CORESET based on the SIB1.

[0028] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, the second CORESET may be indicated by a CRC mask, DMRS scrambling, or encoded DCI bit scrambling.

[0029] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the second CORESET may be indicated by the number of first REs associated with the first CORESET that satisfy a first threshold, by the bandwidth or number of REs associated with the first CORESET that satisfy a second threshold, or by conveying the first CORESET in a specific frequency band.

[0030] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for the following steps: sending a handover command for a target cell that indicates that CORESET repeating can be activated; and sending neighboring cell information associated with neighboring cells of the target cell that indicates CORESET repeating information for the neighboring cells. Attached Figure Description

[0031] Figure 1 An example of a wireless communication system supporting signaling for system information blocks according to one or more aspects of this disclosure is shown.

[0032] Figure 2 An example of a network architecture supporting signaling for system information blocks, according to one or more aspects of this disclosure, is shown.

[0033] Figure 3 An example of a wireless communication system supporting signaling for system information blocks according to one or more aspects of this disclosure is shown.

[0034] Figure 4 An example of a timing diagram supporting signaling for system information blocks according to one or more aspects of this disclosure is shown.

[0035] Figure 5 An example of a timing diagram supporting signaling for system information blocks according to one or more aspects of this disclosure is shown.

[0036] Figure 6 An example of a process flow supporting signaling for system information blocks according to one or more aspects of this disclosure is shown.

[0037] Figure 7 and Figure 8 A block diagram of a device supporting signaling for system information blocks according to one or more aspects of this disclosure is shown.

[0038] Figure 9 A block diagram of a communication manager supporting signaling for system information blocks, according to one or more aspects of this disclosure, is shown.

[0039] Figure 10 A diagram of a system including devices supporting signaling for system information blocks according to one or more aspects of this disclosure is shown.

[0040] Figure 11 and Figure 12 A block diagram of a device supporting signaling for system information blocks according to one or more aspects of this disclosure is shown.

[0041] Figure 13 A block diagram of a communication manager supporting signaling for system information blocks, according to one or more aspects of this disclosure, is shown.

[0042] Figure 14 A diagram of a system including devices supporting signaling for system information blocks according to one or more aspects of this disclosure is shown.

[0043] Figures 15 to 18 A flowchart illustrating a method for supporting signaling for system information blocks according to one or more aspects of this disclosure is shown. Detailed Implementation

[0044] Some wireless communication systems include non-terrestrial network (NTN) nodes (e.g., satellites) for communication with user equipment (UEs) located on or near the Earth's surface. In some approaches, low Earth orbit (LEO) satellites can support hundreds to thousands of beams or cells. Due to limited power and a limited number of radio frequency (RF) chains, a relatively small portion of a satellite beam can be used for transmission simultaneously. Given these power and RF chain limitations, efforts can be made to increase the number of supported beams by supporting power sharing between beams and reducing the overhead of downlink channels (e.g., synchronization signal blocks (SSBs), system information blocks 1 (SIB1), or other system information blocks (SIBs) such as system information block 19 (SIB19)).

[0045] Due to limited transmit power and channel bandwidth, the UE may attempt to receive SIBs (e.g., multiple repetitions of SIB1) to decode System Information (SI) messages. For example, at a 5 MHz bandwidth, the signal-to-noise ratio (SNR) for decoding the Physical Downlink Shared Channel (PDSCH) of SIB1 with a 10% error rate could be -5.8 dB, or the SNR for scheduling the Physical Downlink Control Channel (PDCCH) with a 1% error rate could be -5.9 dB. For larger SIBs (e.g., SIB19), the specified or target SNR may be even higher. However, the actual SNR used for transmission may be as low as -9 dB. Therefore, network entities may have to send a large number of repetitions to ensure reception by the UE, which could result in increased latency (e.g., 2 seconds) or relatively high downlink overhead.

[0046] The UE can monitor the search space during a monitoring period to obtain multiple control resource sets (CORESETs), which include a first CORESET and at least one second CORESET (e.g., a repetition of the first CORESET). The UE can receive the repetition of the first CORESET during the monitoring period from a network entity (e.g., an NTN node or satellite, etc.) via a second resource element (RE), the second RE being located at a time and frequency defined relative to the first RE associated with the first CORESET (e.g., a predefined time and frequency). The repetition of the first CORESET may include control messages for the transmission of scheduling messages (e.g., PDSCH or SIB1). For example, the CORESET may include information (e.g., PDCCH) for scheduling SIBs (e.g., SIB1). The PDCCH may be a physical channel (e.g., a modulated signal including encoded data bits, cyclic redundancy check (CRC), and DMRS, etc.). In some aspects, the data bits of the PDCCH may be downlink control information (DCI) bits. In some methods, one or more PDCCHs may be included in the CORESET. The UE can use the information indicated by the control message included in the repetition of the first CORESET to communicate messages with network entities. For example, the PDCCH can schedule downlink transmission (e.g., PDSCH) or uplink transmission (e.g., Physical Uplink Shared Channel (PUSCH)).

[0047] By using the first core set and at least one repetition of the first core set, the UE can receive the information in the core set more reliably, which increases the probability of successfully receiving the message (e.g., PDSCH or SIB1). For example, by providing more opportunities to receive the first core set, or by implementing joint decoding of the first core set and the repetition, the message (e.g., SIB1) may be more likely to be successfully scheduled. This increases the probability of receiving the message via a single transmission rather than via multiple transmissions. Because the first core set itself is repeated during monitoring, this also reduces or avoids the need to repeatedly receive PDCCH and PDSCH pairs for successful message reception. Therefore, the latency for successful message reception can also be reduced. In some cases, the message may include SIB1, which can be used to schedule further signaling or allow the UE to establish a link or connection. Therefore, improving the reliability of core set reception via core set repetition may also improve the reliability of subsequent signaling or reduce the latency of subsequent signaling.

[0048] Positioning a repeat of a core set at a predefined time or frequency relative to the first core set reduces overhead signaling. For example, the UE can use a predefined time or frequency relationship between the first core set and the repeats to locate one or more repeats of the first core set, avoiding overhead signaling used to indicate the position of the repeats in time or frequency. Additionally or alternatively, the UE can receive SIB1 indicating the time and frequency relative to the first core set.

[0049] In some methods, the message may include SIB1 in the PDSCH. SIB1 can indicate the repetition of CORESETs specific to a search space type. For example, SIB1 can be used to indicate the repetition of CORESETs of a type that can be used to establish or improve links. In some aspects, SIB1 can indicate the repetition of CORESETs of Type 0 Common Search Space (Type 0CSS) that can be used to schedule SIB19, where SIB19 can be used to obtain important data related to NTN nodes, such as ephemeris, timing, or Doppler information. Using SIB1 to indicate the repetition of SIB type-specific CORESETs avoids repetition for any or all CORESET types, which in turn avoids repetition for other CORESET types, thereby reducing overhead signaling.

[0050] In some methods, the DCI in the CORESET can be used to indicate the number of time slots used for aggregating PDSCHs carrying SIBs. PDSCHs can be scheduled via CSS by the PDCCH (e.g., DCI). Using the DCI to indicate the number of time slots used for aggregation allows for flexibility in allocating resources for PDSCH repetition. Repetition of PDSCHs carrying SIBs increases the probability of receiving both PDSCHs and SIBs. Because SIBs can be used to schedule further scheduling or establish links, allowing indication of PDSCH and SIB repetition provides increased communication reliability. Allowing the use of CSS to schedule PDSCHs carrying SIBs provides increased signaling flexibility and allows multiple UEs to receive SIBs. SIBs can include system information related to all or multiple UEs. In some examples, SIBs can be broadcast. Therefore, PDSCHs carrying SIBs can be scheduled by the PDCCH in the CSS.

[0051] In some methods, the UE may receive a Search Space Buffer (SSB), where space search monitoring can occur within a threshold period following the SSB based on the monitoring timing. The SSB can provide information for receiving signaling (e.g., PDCCH) during that monitoring timing. As the period between the SSB and signaling increases, the information from the SSB (e.g., timing or frequency information) may become less relevant or less accurate for receiving the signaling due to channel variations over time. Therefore, keeping the permitted monitoring timing within that threshold period increases the likelihood of receiving signaling during the SSB-based monitoring timing, as the SSB information is likely to be more relevant or accurate.

[0052] The aspects of this disclosure are first described in the context of a wireless communication system. The aspects of this disclosure are also described in the context of timing diagrams and process flowcharts. The aspects of this disclosure are further illustrated and described with reference to apparatus diagrams, system diagrams, and flowcharts relating to signaling used for system information blocks.

[0053] Figure 1 An example of a wireless communication system 100 supporting signaling for system information blocks according to one or more aspects of this disclosure is shown. The wireless communication system 100 may include one or more devices, such as one or more network devices (e.g., network entity 105), one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating under other systems and radio technologies including future systems and radio technologies not explicitly mentioned herein.

[0054] Network entity 105 may be distributed across a geographical area to form wireless communication system 100, and may include devices employing different forms or having different capabilities. In various examples, network entity 105 may be referred to as a network element, mobility element, radio access network (RAN) node, or network equipment, etc. In some examples, network entity 105 and UE 115 may wirelessly communicate via communication link 125 (e.g., a radio frequency (RF) access link). For example, network entity 105 may support coverage area 110 (e.g., a geographical coverage area) within which UE 115 and network entity 105 may establish communication link 125. Coverage area 110 may be an example of a geographical area within which network entity 105 and UE 115 may support the transmission of signals according to one or more radio access technologies (RATs).

[0055] UE 115 can be distributed throughout the coverage area 110 of wireless communication system 100, and each UE 115 can be stationary or mobile, or stationary and mobile at different times. UE 115 can be devices in different forms or with different capabilities. Figure 1 Examples of UE 115 are illustrated herein. The UE 115 described herein may be able to support communication with various types of devices in the wireless communication system 100 (e.g., other wireless communication devices, including UE 115 or network entity 105), such as... Figure 1 As shown.

[0056] As described herein, a node in the wireless communication system 100 (which may be referred to as a network node or wireless node) may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, apparatus, device, computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node may be UE 115. As another example, a node may be network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be UE 115. In another aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different from these examples. Similarly, references to UE 115, network entity 105, device, equipment, computing system, etc., may include disclosures of UE 115, network entity 105, device, equipment, computing system, etc., as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that a first node is configured to receive information from a second node.

[0057] In some examples, network entity 105 may communicate with core network 130, communicate with each other, or both. For example, network entity 105 may communicate with core network 130 via backhaul communication link 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, network entities 105 may communicate with each other directly (e.g., directly between network entities 105) or indirectly (e.g., via core network 130) via backhaul communication link 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, network entities 105 may communicate with each other via midhaul communication link 162 (e.g., according to midhaul interface protocol) or fronthaul communication link 168 (e.g., according to fronthaul interface protocol) or any combination thereof. The backhaul communication link 120, midhaul communication link 162, or fronthaul communication link 168 may be one or more wired links (e.g., electrical links, fiber optic links) or one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof, or may include one or more wired links (e.g., electrical links, fiber optic links) or one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof. UE 115 may communicate with the core network 130 via communication link 155.

[0058] One or more network entities or network equipment described herein as network entity 105 or network equipment may include or be referred to as base station 140 (e.g., transceiver base station, radio base station, NR base station, access point, radio transceiver, NodeB, eNodeB (eNB), next-generation NodeB or gigabit NodeB (any of which may be referred to as gNB), 5G NB, next-generation eNB (ng-eNB), home NodeB, home eNodeB, or other suitable terms). In some examples, network entity 105 (e.g., base station 140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture that may be configured to utilize a protocol stack physically or logically integrated within a single network entity (e.g., network entity 105 or a single RAN node, such as base station 140).

[0059] In some examples, network entity 105 may be implemented in a decomposed architecture (e.g., a decomposed base station architecture, a decomposed RAN architecture) that can be configured to utilize protocol stacks physically or logically distributed across multiple network entities (e.g., network entity 105) such as an Integrated Access Backhaul (IAB) network, an Open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a Virtualized RAN (vRAN) (e.g., a Cloud RAN (C-RAN)). For example, network entity 105 may include one or more of the following: a Central Unit (CU) such as CU 160, a Distributed Unit (DU) such as DU 165, a Radio Unit (RU) such as RU 170, a RAN Intelligent Controller (RIC) such as RIC 175 (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a Service Management and Orchestration (SMO) system such as SMO system 180, or any combination thereof. RU 170 may also be referred to as a radio headend, intelligent radio headend, remote radio headend (RRH), remote radio unit (RRU), or transmit / receive point (TRP). One or more components of network entity 105 in a decomposed RAN architecture may be co-located, or one or more components of network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities in network entity 105 of a decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0060] The functional splitting among CU 160, DU 165, and RU 170 is flexible and can support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, or any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a protocol stack functional splitting can be used between CU 160 and DU 165, allowing CU 160 to support one or more layers of the protocol stack, and DU 165 to support one or more different layers of the protocol stack. In some examples, CU 160 can host upper protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionality and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). CU 160 (e.g., one or more CUs) may connect to DU 165 (e.g., one or more DUs) or RU 170 (e.g., one or more RUs) or a combination thereof, and DU 165, RU 170, or both may host lower protocol layers, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC) layer, Medium Access Control (MAC) layer) functionality and signaling, and may each be at least partially controlled by CU 160. Additionally or alternatively, a protocol stack functional split may be employed between DU 165 and RU 170, such that DU 165 may support one or more layers of the protocol stack, and RU 170 may support one or more different layers of the protocol stack. DU 165 may (e.g., via one or more different RUs, such as RU 170) support one or more different cells. In some cases, functional decomposition between CU 160 and DU 165, or between DU 165 and RU 170, can be performed within the protocol layer (e.g., some functions of the protocol layer can be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer can be performed by a different one of CU 160, DU 165, or RU 170). CU 160 can be further functionally decomposed into CU control plane (CU-CP) functions and CU user plane (CU-UP) functions. CU 160 can be connected to DU 165 via midhaul communication link 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to RU 170 via fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, the midhaul communication link 162 or the fronthaul communication link 168 may be implemented based on the interfaces (e.g., channels) between the layers of the protocol stack, which are supported by corresponding network entities (e.g., one or more network entities in network entity 105) that communicate via such communication links.

[0061] In some wireless communication systems (e.g., wireless communication system 100), the infrastructure and spectrum resources for radio access can support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities of network entity 105 (e.g., network entity 105 or IAB node 104) may be partially controlled by each other. IAB node 104 may be referred to as a donor entity or IAB donor. DU 165 or RU 170 may be partially controlled by CU 160 associated with network entity 105 or base station 140 (such as a donor network entity or donor base station). One or more donor entities (e.g., IAB donors) may communicate with one or more additional devices (e.g., IAB node 104) via supported access and backhaul links (e.g., backhaul communication link 120). IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by one or more DUs (e.g., DU 165) of a coupled IAB donor. The IAB-MT may be equipped with a separate set of antennas for relaying communication with UE 115, or may share the same antennas (e.g., those of RU 170) for access to IAB node 104 via DU 165 of IAB node 104. (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, IAB node 104 may include one or more DUs (e.g., DU 165) that support communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., IAB node 104, or components of IAB node 104) may be configured to operate according to the techniques described herein.

[0062] For example, the access network (AN) or RAN may include communication between an access node (e.g., an IAB donor), IAB node 104, and one or more UEs 115. The IAB donor may facilitate connectivity between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, an IAB donor may refer to a RAN node having a wired or wireless connection to the core network 130. The IAB donor may include one or more of CU 160, DU 165, and RU 170, in which case CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB donor and IAB node 104 may communicate via an F1 interface according to a protocol defining the signaling messages (e.g., the F1 AP protocol). Additionally or alternatively, CU 160 may communicate with core network 130 via an interface (which may be part of a backhaul link) and may communicate with other CUs (e.g., including CU 160 associated with an alternative IAB donor) via an Xn-C interface (which may be another part of a backhaul link).

[0063] IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for UE 115, radio self-backhaul capability, etc.). DU 165 may act as a distributed scheduling node toward child nodes associated with IAB node 104, and IAB-MT may act as a scheduled node toward a parent node associated with IAB node 104. That is, an IAB donor may be referred to as a parent node communicating with one or more child nodes (e.g., an IAB donor may be relayed by other IAB nodes 104 for UE transmission). Additionally or alternatively, depending on the AN's relay chain or configuration, IAB node 104 may also be referred to as a parent node or child node of other IAB nodes 104. The IAB-MT entity of IAB node 104 can provide a Uu interface to the child IAB node (e.g., IAB node 104) to receive signaling from the parent IAB node (e.g., IAB node 104), and the DU interface (e.g., DU 165) can provide a Uu interface to the parent IAB node to send signaling notifications to the child IAB node or UE 115.

[0064] For example, IAB node 104 may be referred to as a parent node supporting communication to child IAB nodes, or a child IAB node associated with an IAB donor, or both. An IAB donor may include a CU 160 having a wired or wireless connection to core network 130 (e.g., backhaul communication link 120) and may act as a parent node of IAB node 104. For example, an IAB donor's DU 165 may relay transmissions to UE 115 via IAB node 104, or may signal transmissions directly to UE 115, or both. An IAB donor's CU 160 may signal the establishment of a communication link to IAB node 104 via an F1 interface, and IAB node 104 may schedule transmissions (e.g., transmissions relayed from the IAB donor to UE 115) via one or more DUs (e.g., DU 165). In other words, data can be relayed to and from IAB node 104 via signaling through the NR Uu interface of the MT to IAB node 104 (e.g., other IAB nodes). Communication with IAB node 104 can be scheduled by the IAB donor or by DU 165 of IAB node 104.

[0065] When the techniques described herein are applied in the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture can be configured to support the tests described herein. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., components such as IAB node, DU 165, CU 160, RU 170, RIC 175, SMO system 180).

[0066] UE 115 may include or be referred to as a mobile device, wireless device, remote device, handheld device, or subscriber device, or any other suitable term, wherein "device" may also be referred to as a cell, station, terminal, or client, etc. UE 115 may also include or be referred to as a personal electronic device, such as a cellular phone, personal digital assistant (PDA), tablet computer, laptop computer, or personal computer. In some examples, UE 115 may include or be referred to as a wireless local loop (WLL) station, Internet of Things (IoT) device, Internet of Everything (IoE) device, or machine-type communication (MTC) device, etc., which may be implemented in various objects such as appliances, vehicles, or meters.

[0067] The UE 115 described herein may be able to communicate with various types of devices, such as the UE 115 which sometimes operates as a repeater, and network entity 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 As shown.

[0068] UE 115 and network entity 105 can wirelessly communicate with each other via communication link 125 (e.g., one or more access links) using resources associated with one or more carriers. The term "carrier" can refer to a set of RF spectrum resources having a defined PHY layer structure for supporting communication link 125. For example, a carrier for communication link 125 may include a portion of the RF spectrum band (e.g., a bandwidth portion (BWP)) operating according to one or more PHY layer channels for a given RAT (e.g., LTE, LTE-A, LTE-A Pro, NR). Each PHY layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling coordinating operation for the carrier, user data, or other signaling. Wireless communication system 100 can support communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 can be configured using multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used in conjunction with both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers. Communication between network entity 105 and other devices can refer to communication between these devices and any part of network entity 105 (e.g., entity, sub-entity). For example, the terms “send,” “receive,” or “communicate” when referring to network entity 105 can refer to any part of the RAN’s network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) communicating with another device (e.g., directly or via one or more other network entities, such as one or more network entities in network entity 105).

[0069] In some examples, such as in carrier aggregation configurations, a carrier may have acquisition signaling or control signaling that coordinates the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be identified according to a channel grating used for discovery by UE 115. A carrier may operate in standalone mode, in which case initial acquisition and connection can be performed by UE 115 via that carrier, or the carrier may operate in non-standalone mode, in which case different carriers (e.g., of the same or different RATs) are used to anchor the connection.

[0070] The communication link 125 of the wireless communication system 100 may include downlink transmission (e.g., forward link transmission) from network entity 105 to UE 115, uplink transmission (e.g., return link transmission) from UE 115 to network entity 105, or both, as well as other transmission configurations. The carrier may carry downlink communication or uplink communication (e.g., in FDD mode), or may be configured to carry both downlink and uplink communication (e.g., in TDD mode).

[0071] A carrier may be associated with a specific bandwidth of the RF spectrum, and in some examples, the carrier bandwidth may be referred to as the carrier or the “system bandwidth” of the wireless communication system 100. For example, the carrier bandwidth may be one of a set of bandwidths for a carrier for a specific RAT (e.g., 1.4 MHz, 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz). Devices of the wireless communication system 100 (e.g., network entity 105, UE 115, or both) may have a hardware configuration that supports communication using a specific carrier bandwidth, or may be configured to support communication using one of a set of carrier bandwidths. In some examples, the wireless communication system 100 may include a network entity 105 or UE 115 that supports concurrent communication using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate using a portion (e.g., subband, BWP) or all of the carrier bandwidth.

[0072] The signal waveform transmitted via a carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform extended OFDM (DFT-S-OFDM)). In a system employing MCM, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, where the symbol period and subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the decoding rate of the modulation scheme, or both), such that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high modulation scheme order correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, temporal resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0073] It can support one or more sets of parameters for a carrier, and the parameter sets may include subcarrier spacing ( (and cyclic prefix). A carrier can be divided into one or more BWPs with the same or different sets of parameters. In some examples, multiple BWPs can be used to configure UE 115. In some examples, a single BWP of a carrier can be active at a given time, and communication for UE 115 can be constrained to one or more active BWPs.

[0074] The time interval for network entity 105 or UE 115 can be expressed as a multiple of a basic time unit, such as the sampling period. seconds, in response This can represent the supported subcarrier spacing, while This can represent the supported Discrete Fourier Transform (DFT) size. The time interval for organizing communication resources can be based on radio frames, each with a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a System Frame Number (SFN) (e.g., ranging from 0 to 1023).

[0075] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may (e.g., in the time domain) be divided into subframes, and each subframe may also be divided into a number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a number of symbol periods (e.g., depending on the length of the cyclic prefix appended to each symbol period). In some wireless communication systems, such as wireless communication system 100, time slots may be further divided into multiple micro-time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., The duration of a symbol period is associated with a (number) sampling period. The duration of a symbol period can depend on the subcarrier spacing or the operating frequency band.

[0076] A subframe, time slot, micro-time slot, or symbol can be the smallest scheduling unit of the wireless communication system 100 (e.g., in the time domain) and can be referred to as a transmission time interval (TTI). In some examples, the duration of the TTI (e.g., the number of symbol periods in the TTI) can be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 can be dynamically selected (e.g., in a burst of shortened TTIs (sTTIs)).

[0077] Depending on the technology, carriers can be used to multiplex physical channels for communication. For example, one or more of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or hybrid TDM-FDM techniques can be used to multiplex physical control channels and physical data channels for signaling via a downlink carrier. A control region (e.g., CORESET) for the physical control channel can be defined by a set of symbol periods and can extend across the system bandwidth or a subset of the system bandwidth of the carrier. One or more control regions (e.g., CORESET) can be configured for a set of UEs 115. For example, one or more UEs in UE 115 can monitor or search for control regions to obtain control information based on one or more search space sets, and each search space set can include one or more control channel candidates in one or more aggregation levels arranged in a concatenated manner. The aggregation level of control channel candidates can refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space set may include a common search space set configured to transmit control information to UE115 (e.g., one or more UEs), or it may include a UE-specific search space set configured to transmit control information to UE115 (e.g., a particular UE).

[0078] Network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hotspots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used (e.g., using a carrier) to communicate with network entity 105 and may be associated with an identifier used to distinguish adjacent cells (e.g., Physical Cell Identifier (PCID), Virtual Cell Identifier (VCID)). In some examples, a cell may also refer to a coverage area 110 or a portion of coverage area 110 (e.g., a sector) in which a logical communication entity operates. Depending on various factors such as the capabilities of network entity 105, the range of such cells may be from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be a building, a subset of buildings, or external space between or overlapping coverage areas 110, etc., or may include buildings, subsets of buildings, or external space between or overlapping coverage areas, etc.

[0079] Macro cells typically cover a relatively large geographic area (e.g., a radius of several kilometers) and allow unrestricted access to UE 115 that has a service subscription with a network provider supporting the macro cell. In contrast, small cells may be associated with network entities 105 operating at lower power (e.g., base station 140 operating at lower power) and may operate using the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to UE 115 that has a service subscription with a network provider, or restricted access to UE 115 associated with a small cell (e.g., UE 115 in a Closed Subscriber Group (CSG), or UE 115 associated with a user in a home or office). Network entity 105 may support one or more cells and may also use one or more component carriers to support communication via one or more cells.

[0080] In some examples, a carrier can support multiple cells and can be configured with different cells based on different protocol types that can provide access for different types of devices (e.g., MTC, Narrowband IoT (NB-IoT), Enhanced Mobile Broadband (eMBB)).

[0081] In some examples, network entity 105 (e.g., base station 140, RU 170) may be mobile, and thus provide communication coverage to mobile coverage areas (such as coverage area 110). In some examples, coverage areas 110 associated with different technologies (e.g., different coverage areas) may overlap, but coverage areas 110 (e.g., different coverage areas) may be supported by the same network entity (e.g., network entity 105). In some other examples, overlapping coverage areas (such as coverage area 110) associated with different technologies may be supported by different network entities (e.g., network entity 105). The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 use the same or different RATs to support communication to coverage areas 110 (e.g., different coverage areas).

[0082] The wireless communication system 100 can support synchronous or asynchronous operation. For synchronous operation, network entities 105 (e.g., base station 140) can have similar frame timings, and transmissions from different network entities (e.g., different network entities within network entity 105) can be approximately time-aligned. For asynchronous operation, network entities 105 can have different frame timings, and in some examples, transmissions from different network entities (e.g., different network entities within network entity 105) may not be time-aligned. The techniques described herein can be used for both synchronous and asynchronous operation.

[0083] Some UE 115 devices (such as MTC or IoT devices) can be relatively low-cost or low-complexity devices and can provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC can refer to data communication technologies that allow devices to communicate with each other or with network entity 105 (e.g., base station 140) without human intervention. In some examples, M2M communication or MTC may include communication from devices with integrated sensors or instruments to measure or acquire information and relay such information to a central server or application that uses the information or presents it to people interacting with the application. Some UE 115 devices may be designed to collect information or enable automated behavior of machines or other devices. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based service charging.

[0084] Some UE 115s can be configured to operate in a power-saving mode, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception but does not involve concurrent transmission and reception). In some examples, half-duplex communication can be performed at a reduced peak rate. Other power-saving techniques for UE 115 may include: entering a power-saving deep sleep mode when not engaged in active communication, operating with limited bandwidth (e.g., according to narrowband communication), or a combination of these techniques. For example, some UE 115s can be configured to operate using a narrowband protocol type associated with a defined portion or range (e.g., a set of subcarriers or resource blocks (RBs)) within a carrier, within a carrier's guard band, or outside a carrier.

[0085] Wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication, or various combinations thereof. For example, wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable, low-latency, or critical functions. Ultra-reliable communication may include private or group communication and may be supported by one or more services, such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions may include prioritizing services, and such services may be used for public safety or general business applications. The terms “ultra-reliable,” “low-latency,” and “ultra-reliable low-latency” are used interchangeably herein.

[0086] In some examples, UE 115 may be configured to support direct communication with other UEs (e.g., one or more UEs in UE 115) via a device-to-device (D2D) communication link (such as D2D communication link 135) (e.g., according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 in a group performing D2D communication may be within the coverage area 110 of network entity 105 (e.g., base station 140, RU 170), which may support aspects of such D2D communication configured (e.g., scheduled by network entity 105). In some examples, one or more UEs 115 in such a group may be outside the coverage area 110 of network entity 105, or may otherwise be unable or not configured to receive transmissions from network entity 105. In some examples, a group of UEs 115 communicating via D2D communication can support a one-to-many (1:M) system, in which each UE 115 transmits to one or more UEs in the group. In some examples, network entity 105 can facilitate the scheduling of resources used for D2D communication. In some other examples, D2D communication can be performed between UEs 115 without involving network entity 105.

[0087] In some systems, the D2D communication link 135 may be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, vehicles may communicate using vehicle-to-vehicle (V2X) communication, vehicle-to-vehicle (V2V) communication, or a combination of these. Vehicles may signal information related to traffic conditions, signal control, weather, safety, emergencies, or any other information relevant to the V2X system. In some examples, vehicles in a V2X system may communicate with roadside infrastructure (such as roadside units), or communicate with the network via one or more network nodes (e.g., network entity 105, base station 140, RU 170) using vehicle-to-network (V2N) communication, or both.

[0088] Core network 130 provides user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. Core network 130 can be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a Mobility Management Entity (MME), Access and Mobility Management Function (AMF)) for managing access and mobility, and at least one user plane entity (e.g., a Serving Gateway (S-GW), Packet Data Network (PDN) Gateway (P-GW), or User Plane Function (UPF)) for routing packets or interconnecting to external networks. The control plane entity manages non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by network entity 105 (e.g., base station 140) associated with core network 130. User IP packets can be delivered through the user plane entity, which provides IP address allocation and other functions. The user plane entity may connect to one or more network operator IP services 150. IP services 150 may include access to the Internet, intranets, IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0089] Wireless communication system 100 can operate using one or more frequency bands in the range of 300 MHz to 300 GHz. Generally, the area from 300 MHz to 3 GHz is referred to as the Ultra High Frequency (UHF) band or decimeter band because the wavelength range is approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves are sufficient to penetrate structures so that macrocells can provide service to UE 115 located indoors. Compared to communication using smaller frequencies and longer wavelengths in the lower frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz, communication using UHF waves can be associated with smaller antennas and shorter ranges (e.g., less than one hundred kilometers).

[0090] The wireless communication system 100 can also operate in the Ultra High Frequency (SHF) band (also known as the centimeter band) in the range of 3 GHz to 30 GHz or in the Extremely High Frequency (EHF) band (e.g., 30 GHz to 300 GHz) (also known as the millimeter band) using the spectrum. In some examples, the wireless communication system 100 can support millimeter-wave (mmW) communication between the UE 115 and the network entity 105 (e.g., base station 140, RU170), and the EHF antennas of the corresponding devices can be smaller and more closely spaced than UHF antennas. In some examples, such techniques facilitate the use of antenna arrays within the device. However, compared to SHF or UHF transmission, EHF transmission may experience even greater attenuation and a shorter range. The techniques disclosed herein can be adopted for transmission across one or more different frequency bands, and the frequency band usage specified across these frequency bands may vary by country or regulatory authority.

[0091] Wireless communication system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, wireless communication system 100 may employ licensed assisted access (LAA), LTE-Unlicensed (LTE-U) RAT, or NR technology using unlicensed frequency bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band). When operating with unlicensed RF spectrum, devices such as network entity 105 and UE 115 may employ carrier sensing for collision detection and avoidance. In some examples, operation using unlicensed frequency bands may be based on carrier aggregation configurations combined with component carriers operating with licensed frequency bands (e.g., LAA). Operation using unlicensed spectrum may include downlink transmission, uplink transmission, P2P transmission, or D2D transmission, etc.

[0092] Network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels, which can support MIMO operation or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly (such as an antenna tower). In some examples, the antennas or antenna arrays associated with network entity 105 may be located at different geographical locations. Network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that network entity 105 can use to support beamforming for communication with UE 115. Similarly, UE 115 may include one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals transmitted via the antenna ports.

[0093] Network entity 105 or UE 115 can use MIMO communication to leverage multipath signal propagation and improve spectral efficiency by transmitting or receiving multiple signals via different spatial layers. This technique is known as spatial multiplexing. The multiple signals can be transmitted, for example, by a transmitting device via different antennas or different combinations of antennas. Similarly, the multiple signals can be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals can be referred to as a separate spatial stream and can carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers can be associated with different antenna ports used for channel measurement and reporting. MIMO techniques include: single-user MIMO (SU-MIMO), where multiple spatial layers are transmitted to the same receiving device; and multi-user MIMO (MU-MIMO), where multiple spatial layers are transmitted to multiple devices.

[0094] Beamforming (also known as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting or receiving device (e.g., network entity 105, UE 115) to shape or guide an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals transmitted via antenna elements of an antenna array such that some signals propagating along a specific orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to the signals transmitted via the antenna elements may include applying amplitude shifts, phase shifts, or both to the signals carried via the antenna elements associated with the device. The adjustments associated with each of these antenna elements may be defined by a beamforming weight set associated with a specific orientation (e.g., relative to the antenna array of the transmitting or receiving device or relative to some other orientation).

[0095] Network entity 105 or UE 115 may use beam scanning technology as part of beamforming operations. For example, network entity 105 (e.g., base station 140, RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted multiple times by network entity 105 along different directions. For example, network entity 105 may transmit signals according to different beamforming weight sets associated with different transmission directions. Transmission along different beam directions may be used to identify (e.g., by a transmitting device (such as network entity 105) or by a receiving device (such as UE 115)) the beam direction for later transmission or reception by network entity 105.

[0096] Some signals (such as data signals associated with a specific receiving device) may be transmitted by a transmitting device (e.g., network entity 105 or UE 115) along a single beam direction (e.g., a direction associated with a receiving device such as another network entity 105 or UE 115). In some examples, the beam direction associated with transmission along a single beam direction may be determined based on the signals transmitted along one or more beam directions. For example, UE 115 may receive one or more signals transmitted by network entity 105 along different directions and may report to network entity 105 an indication of signals received by UE 115 with the highest signal quality or other acceptable signal quality.

[0097] In some examples, transmissions performed by a device (e.g., network entity 105 or UE 115) may be performed using multiple beam directions, and the device may use a combination of digital pre-decoding or beamforming to generate a combined beam for transmission (e.g., from network entity 105 to UE 115). UE 115 may report feedback indicating pre-decoding weights for one or more beam directions, and this feedback may correspond to a configured set of beams across the system bandwidth or one or more subbands. Network entity 105 may transmit reference signals (e.g., cell-specific reference signals (CRS), channel state information reference signals (CSI-RS)) that may or may not be pre-decoded. UE 115 may provide feedback on beam selection, which may be a pre-decoding matrix indicator (PMI) or codebook-based feedback (e.g., multi-panel codebook, linear combination codebook, port selection codebook). Although these techniques are described with reference to signals transmitted by network entity 105 (e.g., base station 140, RU 170) along one or more directions, UE 115 may use similar techniques to transmit signals multiple times along different directions (e.g., to identify the beam direction used by UE 115 for subsequent transmission or reception), or to transmit signals along a single direction (e.g., to transmit data to a receiving device).

[0098] A receiving device (e.g., UE 115) may perform reception operations according to multiple reception configurations (e.g., directional listening) when receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from a transmitting device (e.g., network entity 105). For example, the receiving device may perform reception according to multiple reception directions by: receiving via different antenna subarrays; processing the received signal according to different antenna subarrays; receiving according to different sets of reception beamforming weights applied to signals received at multiple antenna elements of the antenna array (e.g., different directional listening weight sets); or processing the received signal according to different sets of reception beamforming weights applied to signals received at multiple antenna elements of the antenna array. Any of these operations may be referred to as “listening” according to different reception configurations or reception directions. In some examples, the receiving device may use a single reception configuration to receive along a single beam direction (e.g., when a data signal is received). A single receiver configuration can be aligned along a beam direction determined based on listening according to different receiver configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or other acceptable signal quality based on listening according to multiple beam directions).

[0099] The wireless communication system 100 can be a packet-based network operating according to a layered protocol stack. In the user plane, communication at the bearer or PDCP layer can be IP-based. The RLC layer performs packet segmentation and reassembly for transmission via logical channels. The MAC layer performs priority processing and multiplexing of logical channels to transport channels. The MAC layer can also use error detection, error correction, or both to support retransmission to improve link efficiency. In the control plane, the RRC layer provides the establishment, configuration, and maintenance of RRC connections between the UE 115 and network entity 105 or core network 130 that support user plane data radio bearers. The PHY layer maps transport channels to physical channels.

[0100] UE 115 and network entity 105 can support data retransmission to increase the likelihood of successful data reception. Hybrid Automatic Repeat Request (HARQ) feedback is a technique used to increase the likelihood of correctly receiving data via communication links (e.g., communication link 125, D2D communication link 135). HARQ can include a combination of error detection (e.g., using CRC), forward error correction (FEC), and retransmission (e.g., Automatic Repeat Request (ARQ)). HARQ can improve throughput at the MAC layer under relatively poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, the device can support same-slot HARQ feedback, in which case the device can provide HARQ feedback in a specific time slot for data received via a previous symbol in that time slot. In some other examples, the device can provide HARQ feedback in subsequent time slots or according to a different time interval.

[0101] Some wireless communication systems include NTN nodes (e.g., satellites) for communication with UEs located on or near the Earth's surface. In some approaches, LEO satellites can support hundreds to thousands of beams or cells. Due to limited power and a limited number of RF chains, a relatively small portion of a satellite beam can be used for transmission simultaneously. Given these power and RF chain limitations, efforts can be made to increase the number of supported beams by supporting power sharing between beams and reducing the overhead of downlink channels (e.g., SSBs), SIB1, or other SIBs (e.g., SIB19).

[0102] In some methods used for SIB1 and SI transmission, SIB1 can be transmitted periodically at 160ms intervals. Within a single period, multiple SIB1 transmissions can be scheduled using the PDCCH in type 0 CSS of CORESET0. Up to eight SIB1 transmissions can be scheduled within a single period, with the number of transmissions depending on the network specifics. Other SIBs can be transmitted at configurable intervals (e.g., intervals greater than 160ms). Multiple SIB transmissions within a single period can be executed via scheduling.

[0103] In some methods, the SIB can provide scheduling information. For example, SIB1 can provide scheduling information for one or more other SI messages. In some examples, an SI message can include one or more SIBs. An SI message can include an SI window length parameter. This SI window length can be the same for all scheduled SI messages. The starting position of the SI window can be determined using a formula. In some examples, the UE 115 can search for the PDCCH (e.g., System Information Radio Network Temporary Identifier (SI-RNTI)) during the SI window to receive the SI message. SI periodicity can be configured for each SI message, which may create gaps between two SI windows. Any changes to the SI message may occur after the next SI modification period boundary (except for SI messages used for Earthquake and Tsunami Warning Systems (ETWS), Commercial Mobile Alert Systems (CMAS), or location assistance data (e.g., SIB9 or SIB19 carrying ephemeris data)). This SI modification boundary can include multiple SI windows for repetition or retransmission. List (1) illustrates examples of SI window length (e.g., “si-WindowLength”), SI periodicity (e.g., “si-Periodicity”), and SIB type (e.g., “sibType2” and “sibType3”, etc.).

[0104]

[0105] List (1)

[0106] Due to limited transmit power and channel bandwidth, UE 115 may attempt to receive SIBs (e.g., multiple repetitions of SIB1) to decode SI messages. For example, with a 5MHz bandwidth and a 10% error rate, the signal-to-noise ratio (SNR) for decoding the SIB1 PDSCH could be -5.8dB, or with a 1% error rate, the SNR for scheduling the PDCCH could be -5.9dB. For the relatively larger SIB19, the SNR could be even higher. However, the actual SNR used for transmission could be as low as -9dB. Therefore, network entities may have to send a large number of repetitions to ensure reception by UE 115, which could lead to increased latency or relatively high downlink overhead.

[0107] Enhancements for SIB transmissions are described to help ensure coverage or reduce overhead. Some techniques described herein improve coverage per SIB transmission. In some examples, CORESET repetition or extension can be utilized. For example, a CORESET for monitoring timing can be repeated N times. The frequency and timing of these CORESET repetitions can be specified relative to the initial CORESET. For a potential PDCCH, the same number of REs can be used in the repeated CORESET as in the initial CORESET. In some methods, to allow the UE 115 to distinguish whether repetition has been applied, a CRC mask (e.g., another Radio Network Temporary Identifier (RNTI)), another Demodulation Reference Signal (DMRS) scrambling sequence, or another DCI scrambling can be applied to indicate CORESET repetition. In some examples, slot aggregation can be supported for PDSCHs carrying SIBs. In some methods, the PDCCH monitoring timing for SIB1 or SIB19 can be limited to a threshold time from the transmission SSB.

[0108] UE 115 can monitor the search space during a monitoring period to obtain multiple cores, including a first core and a second core (e.g., at least one repetition of the first core). In some examples, the second core may have the same candidate index and / or aggregation level as the first core. UE 115 can receive repetitions of the first core during the monitoring period from network entities (e.g., NTN nodes or satellites, etc.) via second REs located at a time and frequency defined (e.g., predefined) relative to the first RE associated with the first core. The repetitions of the first core may include control messages for the transmission of scheduling messages (e.g., PDSCH or SIB1). For example, the core may include information (e.g., PDCCH) for scheduling SIBs (e.g., SIB1). UE 115 can use the information indicated by the control messages included in the repetitions of the first core to communicate with network entities.

[0109] By using the first core set and at least one repetition of the first core set, the UE 115 can receive information in the core set more reliably, which increases the probability of successfully receiving a message (e.g., PDSCH or SIB1). For example, by providing more opportunities to receive the first core set, or by implementing joint decoding of the first core set and the repetition, the message (e.g., SIB1) may be more likely to be successfully scheduled. This increases the probability of receiving the message via a single transmission rather than via multiple transmissions. Because the first core set itself is repeated during monitoring, this also reduces or avoids the need to repeatedly receive PDCCH and PDSCH pairs for successful message reception. Therefore, the latency for successful message reception can also be reduced. In some cases, the message may include SIB1, which can be used to schedule further signaling or allow the UE 115 to establish a link or connection. Therefore, improving the reliability of core set reception via core set repetition may also improve the reliability of subsequent signaling or reduce the latency of subsequent signaling.

[0110] Relative to the first core set, locating the repetitions of the core set at a predefined time or predefined frequency reduces overhead signaling. For example, UE 115 can use a predefined time or predefined frequency relationship between the first core set and the repetitions to locate one or more repetitions of the first core set, which avoids overhead signaling used to indicate the position of the repetitions in time or frequency. Additionally or alternatively, the UE can be made able to receive SIB1 indicating the time and frequency relative to the first core set.

[0111] In some methods, the message may include SIB1 in the PDSCH. SIB1 can indicate the repetition of a CORESET of a type specific to one or more search spaces. For example, SIB1 can be used to indicate the repetition of another CORESET for an SIB type that can be used to establish or improve a link. In some aspects, SIB1 can indicate the repetition of a CORESET for SIB19, where SIB19 can be used to obtain important data related to the NTN node, such as ephemeris. In some examples, Doppler information can be derived from this ephemeris and the UE's location. Using SIB1 to indicate the repetition of SIB type-specific CORESETs avoids performing repetition for any or all CORESET types, thereby improving system efficiency and reducing UE complexity. For example, the network can avoid sending some CORESET repetitions, or the UE can avoid receiving some CORESET repetitions.

[0112] In some methods, the DCI in the CORESET can be used to indicate the number of time slots used for aggregation of PDSCHs carrying SIBs. PDSCHs can be carried in the CSS. Using the DCI to indicate the number of time slots used for aggregation allows for flexibility in allocating resources for PDSCH repetition. Repetition of PDSCHs carrying SIBs increases the probability of receiving both PDSCHs and SIBs. Because SIBs can be used for further scheduling or link establishment, allowing indication of repetition of PDSCHs carrying SIB messages provides increased communication reliability.

[0113] In some methods, UE 115 may receive a Search Space Buffer (SSB), where space search monitoring can occur within a threshold period following the SSB based on the monitoring timing. The SSB provides information for receiving signaling (e.g., PDCCH) during that monitoring timing. As the period between the SSB and signaling increases, the information from the SSB may become less relevant or less accurate for receiving the signaling due to channel variations over time. Therefore, keeping the permitted monitoring timing within that threshold period increases the likelihood of receiving signaling during the SSB-based monitoring timing, as the SSB information is likely to be more relevant or accurate.

[0114] Figure 2 An example of a network architecture 200 (e.g., a decomposed base station architecture, a decomposed RAN architecture) supporting signaling for system information blocks according to one or more aspects of this disclosure is shown. Network architecture 200 may exemplify examples for implementing one or more aspects of a wireless communication system 100. Network architecture 200 may include one or more CUs 160-a that can communicate directly with the core network 130-a via a backhaul communication link 120-a, or indirectly with the core network 130-a via one or more decomposed network entities 105 (e.g., a near-RT RIC 175-b via an E2 link or a non-RT RIC 175-a associated with an SMO 180-a (e.g., an SMO framework) or both). CUs 160-a may communicate with one or more DUs 165-a via a corresponding midhaul communication link 162-a (e.g., an F1 interface). DUs 165-a may communicate with one or more RUs 170-a via a corresponding fronthaul communication link 168-a. RU 170-a may be associated with a corresponding coverage area 110-a and may communicate with UE 115-a via one or more communication links 125-a. In some implementations, UE 115-a may be served by multiple RU 170-a simultaneously.

[0115] Each network entity in network entity 105 of network architecture 200 (e.g., CU 160-a, DU 165-a, RU170-a, non-RT RIC 175-a, near-RT RIC 175-b, SMO 180-a, Open Cloud (O-Cloud) 205, Open eNB (O-eNB) 210) may include one or more interfaces or may be coupled to one or more interfaces configured to receive or transmit signals (e.g., data, information) via wired or wireless transmission media. Each network entity 105 or an associated processor (e.g., a controller) that provides instructions to the interfaces of network entity 105 may be configured to communicate with one or more network entities in other network entities 105 via transmission media. For example, these network entities 105 may include wired interfaces configured to receive signals or transmit signals to one or more network entities in other network entities 105 via wired transmission media. Additionally or alternatively, network entity 105 may include a wireless interface that may include a receiver, transmitter, or transceiver (e.g., an RF transceiver) configured to receive signals via a wireless transmission medium or to transmit signals to one or more other network entities in network entity 105, or both.

[0116] In some examples, the CU 160-a can host one or more higher-level control functions. Such control functions may include RRC, PDCP, SDAP, etc. Each control function can be implemented using an interface configured to communicate signaling with other control functions hosted by the CU 160-a. The CU 160-a can be configured to handle user plane functionalities (e.g., CU-UP), control plane functionalities (e.g., CU-CP), or combinations thereof. In some examples, the CU 160-a can be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 160-a can be implemented to communicate with the DU 165-a for network control and signaling purposes, as needed.

[0117] DU 165-a may correspond to a logic unit that includes one or more functions (e.g., base station functions, RAN functions) for controlling the operation of one or more RU 170-a. In some examples, DU 165-a may at least partially host one or more aspects of the RLC layer, MAC layer, and PHY layer (e.g., high PHY layers, such as modules for FEC encoding and decoding, scrambling, modulation and demodulation, etc.), depending at least in part on the functional partitioning, such as those defined by the 3rd Generation Partnership Project (3GPP). In some examples, DU 165-a may also host one or more low PHY layers. Each layer may be implemented using an interface configured to communicate with other layers hosted by DU 165-a or with control functions hosted by CU 160-a.

[0118] In some examples, lower-layer functionality may be implemented by one or more RU 170-a units. For example, an RU 170-a controlled by a DU 165-a may correspond to a logical node that hosts RF processing functions or low-PHY layer functions (e.g., performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, Physical Random Access Channel (PRACH) extraction and filtering, or both) based at least in part on functional decomposition (such as lower-layer functional decomposition). In this architecture, the RU 170-a may be implemented to handle over-the-air (OTA) communications with one or more UE 115-a units. In some specific implementations, the real-time and non-real-time aspects of control plane and user plane communications with the RU 170-a may be controlled by the corresponding DU 165-a unit. In some examples, such configurations enable the DU 165-a and CU 160-a to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0119] The SMO 180-a can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network entities 105. For non-virtualized network entities 105, the SMO 180-a can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operation and maintenance interface (e.g., the O1 interface). For virtualized network entities 105, the SMO 180-a can be configured to interact with a cloud computing platform (e.g., O-Cloud 205) via a cloud computing platform interface (e.g., the O2 interface) to perform network entity lifecycle management (e.g., to instantiate virtualized network entities 105). Such virtualized network entities 105 may include, but are not limited to, CU 160-a, DU 165-a, RU 170-a, and near-RT RIC 175-b. In some specific implementations, the SMO 180-a can communicate with components configured according to the 4G RAN (e.g., via the O1 interface). Additionally or alternatively, in some implementations, the SMO 180-a may communicate directly with one or more RU 170-a via the O1 interface. The SMO 180-a may also include a non-RT RIC 175-a configured to support the functionality of the SMO 180-a.

[0120] The non-RT RIC 175-a can be configured to include logical functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) or machine learning (ML) workflows (including model training and updates, or policy-based guidance of applications / features in the near-RT RIC 175-b). The non-RT RIC 175-a can be coupled to or communicate with the near-RT RIC 175-b (e.g., via the A1 interface). The near-RT RIC 175-b can be configured to include logical functions that enable near real-time control and optimization of RAN elements and resources via data collection and actions on an interface (e.g., via the E2 interface) connecting one or more CU 160-a, one or more DU 165-a, or both, and the O-eNB 210 to the near-RT RIC 175-b.

[0121] In some examples, to generate AI / ML models to be deployed in a near-RT RIC 175-b, a non-RT RIC 175-a may receive parameters or external enrichment information from an external server. This information can be utilized by the near-RT RIC 175-b and can be received from non-network data sources or network functions at the SMO 180-a or non-RT RIC 175-a. In some examples, a non-RT RIC 175-a or near-RT RIC 175-b may be configured to tune RAN behavior or performance. For example, a non-RT RIC 175-a may monitor long-term trends and patterns in performance and employ AI or ML models to perform corrective actions via the SMO 180-a (e.g., via O1 reconfiguration) or via the generation of RAN management policies such as the A1 policy.

[0122] Some examples of the techniques described herein can be implemented or performed by UE 115-a or by RU 170-a, DU 165-a, or CU160-a. For example, RU 170-a may send one or more CORESET repetitions. UE 115-a may perform search space monitoring or may receive one or more CORESET repetitions. In some approaches, RU 170-a or UE 115-a may support slot aggregation for one or more PDSCHs carrying SIBs (e.g., for one or more PDSCHs scheduled using CSS). In some approaches, the timing of one or more PDCCH monitoring (e.g., for SIB1 or SIB19) may be limited to a threshold period relative to SSBs (e.g., after SSBs).

[0123] Figure 3 An example of a wireless communication system 300 supporting signaling for system information blocks according to one or more aspects of this disclosure is shown. In some examples, the wireless communication system 300 may implement aspects of the wireless communication system 100 or the network architecture 200. The wireless communication system 300 may include a UE 115-b and a network entity 375-a. Reference Figure 1 UE 115-b can be an example of UE 115 or UE 115-a, and network entity 375-a can be an example of CU 160-a, DU 165-a or RU 170-a or a combination thereof.

[0124] In some examples, network entity 375-a can be a High Altitude Platform Station (HAPS), a High Altitude Vehicle (HAV), a LEO satellite, or a balloon, etc. For example, network entity 375-a can be in orbit, such as low Earth orbit, medium Earth orbit, geostationary orbit, or other non-geostationary orbits. Network entity 375-a can be located at a certain distance from Earth (e.g., hundreds or thousands of kilometers), which may vary or remain relatively constant. Network entity 375-a may include communication circuitry (e.g., one or more processors, memory, modems, baseband circuitry, etc.), one or more antennas, or one or more transponders to facilitate the reception and transmission of RF signals. Network entity 375-a can provide service to a geographic area of ​​the NTN.

[0125] In some examples, the wireless communication system 300 may include one or more other NTN nodes or one or more TN nodes (in... Figure 3 (Not shown in the image). For example, UE 115-b may communicate with one or more NTN nodes or one or more TN nodes. In some examples, a TN node may be located on or relatively close to the Earth's surface (e.g., within one mile or less of the Earth's surface). In some examples, a TN node may be anchored or attached to the Earth's surface. A TN node may include communication circuitry (e.g., one or more processors, memory, modems, baseband circuitry, etc.) or one or more antennas to facilitate the reception and transmission of RF signals. In some examples, a TN node may provide communication services within a cell area. In some cases, the cell area may be within, partially overlapping with, or located outside the geographic area served by network entity 375-a. In some aspects, network entity 375-a may be a TN node.

[0126] In some examples, network (e.g., RAN) functionality can be partitioned between network entity 375-a (e.g., a satellite, a satellite-based RU, or a RAN gNB DU, etc.) and TN nodes (e.g., a terrestrial DU or a RAN gNB CU, etc.). For example, network entity 375-a could be DU 165 (e.g., implementing DU 165 functionality), and TN nodes could be CUs (e.g., implementing CU 160 functionality). In some examples, NTN and TN nodes can be Next Generation Radio Access Network (NG-RAN) nodes. In some examples, CU 160 and DU 165 can be terrestrial and associated with one or more terrestrial and non-terrestrial cells or RUs. In the NTN, one or more DU 165s can be located on a satellite, and CU 160 can be located on the Earth's surface. In some examples, network entity 375-a and TN nodes can be included in the RAN (e.g., NG-RAN) portion of the wireless communication system 300. In some examples, UE 115-b may be excluded from the RAN (e.g., NG-RAN) portion of the wireless communication system 300.

[0127] UE 115-b can communicate with network entity 375-a using communication link 325. The communication link 325 between UE 115-b and network entity 375-a can be relative to... Figure 1 An example of the described communication link 125.

[0128] Communication link 325 may be a unidirectional link for downlink communication, or it may include a bidirectional link supporting uplink or downlink communication. For example, network entity 375-a may use communication link 325 to send one or more downlink signals, such as downlink control signals or downlink data signals, to UE 115-b on downlink 365 (e.g., downlink channel, downlink resources). In some cases, UE 115-b may use communication link 325 on uplink (e.g., uplink channel, uplink resources, ... Figure 3 (Not shown) Sends one or more signals, such as uplink control signals or uplink data signals, to network entity 375-a.

[0129] In some examples, network entity 375-a may change its position relative to UE 115-b. Additionally or alternatively, UE 115-b may change its position relative to network entity 375-a. For example, relative motion may occur between network entity 375-a and UE 115-b due to the orbit of network entity 375-a, due to the movement of the Earth, due to the movement of UE 115-b, or a combination thereof. Relative motion between network entity 375-a and UE 115-b may cause changes in Doppler effects (e.g., carrier frequency shift), timing (e.g., round-trip time (RTT)), path loss, or location (e.g., ephemeris), which may affect signaling between network entity 375-a and UE 115-b.

[0130] Network entity 375-a may send multiple CORESETs 320 in the search space during a monitoring period. The multiple CORESETs 320 may include a first CORESET 350-a and one or more repetitions 350-b of the first CORESET 350-a. The multiple CORESETs 320 may include a number (e.g., N=2, 3, 4, or another number) of CORESETs, which include the first CORESET 350-a and one or more repetitions 350-b of the first CORESET 350-a. For a PDCCH with CORESET repetitions, each repetition 350-b of the first CORESET 350-a may be identical to the first CORESET 350-a, while using a different resource (e.g., RE) than that used to communicate the first CORESET 350-a for communication (e.g., sending or receiving). For example, a repeating 350-b of the first CORESET 350-a may include the same content (e.g., at least some of the same information, repeated PDCCH), or may be sent using one or more of the same parameters or features as the first CORESET 350-a (e.g., the same number of REs or the same DMRS).

[0131] In some examples, a CORESET can be a resource block. For example, from the perspective of a PDCCH, a CORESET repetition can mean that the resource block containing the PDCCH is repeated. This resource block can be larger than the resources occupied by the PDCCH. In some cases, the REs not occupied by the PDCCH in a CORESET and in a CORESET repetition can be empty or different between repetitions. In some aspects, CORESET repetition can be specific to the type of PDCCH. For example, for a PDCCH scheduled for SIB1, CORESET A and CORESET B (a repetition of CORESET A) can be sent. Both CORESET A and CORESET B can include a PDCCH scheduled for SIB1. In some cases, a CORESET (e.g., CORESET A) can include another PDCCH that will not be included in a repetition of that CORESET (e.g., CORESET B).

[0132] The search space can be a set of resources within a CORESET (e.g., time and frequency resources or REs, etc.), which can be monitored (e.g., by UE 115-b) to detect a specific PDCCH. The monitoring timing is the period during which the UE (e.g., UE 115-b) can monitor the PDCCH.

[0133] UE 115-b can perform search space monitoring 310. For example, UE 115-b can monitor the search space during monitoring for multiple CORESETs 320, wherein the multiple CORESETs 320 may include a first CORESET 350-a and one or more repetitions 350-b of the first CORESET 350-a. In some methods, UE 115-b can monitor the search space by attempting to receive and decode the PDCCH corresponding to the first CORESET 350-a or a repetition 350-b of the first CORESET 350-a.

[0134] UE 115-b may receive repeats of CORESET 350-a from network entity 375-a via a second RE during a monitoring period. For example, UE 115-b may successfully receive and decode the PDCCH of repeats of CORESET 350-b from the search space during a monitoring period. In some examples, the second RE may be located at a predefined time and predefined frequency relative to the first RE associated with the first CORESET 350-a. For example, the second RE may be located at a time offset or frequency offset relative to one or more of the first REs. As used herein, the term “predefined” in the context of a predefined time or predefined frequency may mean that the time or frequency can be determined before the CORESET (e.g., a repeating CORESET) is transmitted. For example, a predefined time or frequency may be configured via signaling (e.g., signaling from network entity 375-a, such as SIB1) before sending the CORESET or its repetitions, or may be stored by network entity 375-a or UE 115-b during the manufacturing or instruction update phase. In some aspects, network entity 375-a may send CORESET repetition information to UE 115-b (e.g., information indicating the number of repetitions, predefined time, predefined frequency, or mapping, etc.). In some methods, network entity 375-a or UE 115-b may store time or frequency relationships (e.g., predefined time, predefined frequency, time offset, frequency offset, or mapping from one or more first REs to a second RE, etc.) to determine the position of the second RE relative to the position of the first REs. For example, UE 115-b can use a predefined time or a predefined frequency (e.g., a time offset or a frequency offset in the RE grid) to determine the position of a certain RE in the second RE (e.g., the starting RE of the CORESET or the starting RE of the PDCCH in the first RE) based on the position of a certain RE in the first RE (e.g., the starting RE of the CORESET repetition or the starting RE of the PDCCH in the first RE).

[0135] In some aspects, a repeat 350-b of the first CORESET 350-a may include a control message scheduling the transmission of message 370. For example, the first CORESET 350-a or each repeat 350-b of the first CORESET may include a DCI message, a control message in a PDCCH, or other control information indicating the scheduling of the transmission of message 370. In some examples, message 370 may include a PDSCH or SIB (e.g., SIB1) scheduled by the control message of the first CORESET 350-a or the control message of the repeat 350-b of the first CORESET 350-a.

[0136] UE 115-b may communicate message 370 to network entity 375-a using information indicated by a control message included in a repeat of CORESET 350-a. For example, network entity 375-a may use information indicated by the control message in repeat 350-b (e.g., indications of time, time slot, resource, RE, etc.) to send message 370, or UE 115-b may use that information to receive the message. In some examples, message 370 may be or may include a PDSCH or SIB (e.g., SIB1). Network entity 375-a or UE 115-b may send or receive message 370 by sending or receiving message 370 according to that information (e.g., indications of time, time slot, resource, RE, etc.).

[0137] In some examples, message 370 may include SIB1 in a PDSCH that is scheduled at least in part based on multiple CORESETs 320 (e.g., based on a first CORESET 350-a or a repetition 350-b of the first CORESET 350-a). SIB1 may indicate the repetition of a CORESET specific to one or more search spaces (e.g., a search space such as type 0CSS, a UE-specific search space (USS), one or more types of one or more search spaces, or all search spaces, etc.). For example, SIB1 may include information about the repetition of a CORESET specific to a search space type (e.g., type 0CSS or USS) (e.g., the number of CORESET repetitions, the position of a subsequent CORESET relative to the first CORESET, or information for concurrent or subsequent transmission, etc.). In some aspects, a search space may be a search space carrying a scheduling message with SIB19. In some examples, SIB1 indicating the repetition of a second CORESET specific to a search space or search space type may allow indicating the repetition of that CORESET without enabling repetition for all CORESET types. In some respects, SIB1 indicating a repeat of a second CORESET specific to a search space or search space type may allow UE 115-b to perform PDCCH decoding with CORESET repeats for a specific search space. Network entity 375-a or UE 115-b may transmit or receive CORESET repeats (e.g., CORESET content) at least in part based on SIB1. For example, network entity 375-a may transmit or UE 115-b may receive a CORESET or one or more repeats of a CORESET. Repeats of a CORESET may increase the probability of successfully receiving that CORESET, which in turn may increase the probability of successfully receiving an SIB of that type corresponding to that CORESET (e.g., SIB19).

[0138] One or more methods may be used to determine or indicate whether or will be communicated a repeat 350-b of the first CORESET 350-a. In some methods, the UE 115-b may detect a decoding failure of the first CORESET 350-a via a first RE associated with the first CORESET 350-a. In response to a decoding failure of the first CORESET 350-a (e.g., a decoding failure of the PDCCH in the first CORESET 350-a), the UE 115-b may monitor the repeat 350-b of the first CORESET 350-a via a second RE during a monitoring period, based on the assumption that CORESET repeating has been activated. In some examples, monitoring of the repeat 350-b of the first CORESET 350-a may use blind decoding without prior indication that CORESET repeating has been activated. For example, if UE 115-b is unable to decode using the first CORESET 350-a, UE 115-b can use a repeat of the first CORESET 350-a, 350-b, to perform blind decoding of the PDDCH. Using hypothetical or blind decoding in failure cases allows for repeated reception or decoding even without an active CORESET repeat indication, which reduces the overhead signaling used to indicate CORESET repeats.

[0139] In some aspects, UE 115-b may use a combination of the first CORESET 350-a and its repeating 350-b to decode the PDCCH. For example, UE 115-b may combine the first CORESET 350-a and its repeating 350-b to more reliably obtain the PDCCH included in the CORESET. In some examples, UE 115-b may perform soft merging of the first CORESET 350-a and its repeating 350-b to decode the PDCCH.

[0140] In some methods, the repeating 350-b of the first CORESET 350-a can be indicated by a CRC mask, DMRS scrambling, or coded DCI bit scrambling. For example, network entity 375-a can output (e.g., transmit) or UE 115-b can receive the first CORESET 350-a with CRC mask, DMRS scrambling, or coded DCI bit scrambling. In some aspects, different CRC, DMRS masks, or scrambling bits can be used to indicate the repeating 350-b. Using CRC masks, DMRS scrambling, or DCI bit scrambling provides a way to indicate the repeating 350-b using limited resources.

[0141] In some examples, a repetition 350-b of the first CORESET 350-a can be indicated by the number of first REs associated with the first CORESET 350-a that satisfy a first threshold. For example, if the number of first REs associated with the first CORESET 350-a (e.g., the total number) is less than the first threshold (e.g., 3 symbols or other number of symbols), UE115-b can determine that a CORESET repetition is active. For example, UE115-b can detect a CORESET repetition without a separate or explicit indication from the network (e.g., in SIB1). For example, if the first threshold is satisfied, the UE can perform blind decoding based on the assumption that a CORESET repetition is active. Additionally or alternatively, if the number of first REs associated with the first CORESET 350-a is less than the first threshold, network entity 375-a can send or UE 115-b can receive a repetition 350-b of the first CORESET 350-a. As used in this article, "meeting the threshold" can refer to, depending on the context, a value greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, or not equal to the threshold.

[0142] In some examples, a repeat 350-b of the first CORESET 350-a can be indicated by the number of bandwidths or REs associated with the first CORESET 350-a that meets a second threshold. For example, if the number of bandwidths or REs associated with the first CORESET 350-a (e.g., the number of REs in the frequency domain dimension) is less than the second threshold (e.g., 10MHz, 5MHz, or other bandwidths or REs), UE 115-b can determine that a CORESET repeat can be activated. Additionally or alternatively, if the number of bandwidths or REs associated with the first CORESET 350-a is less than the second threshold, network entity 375-a can transmit or UE 115-b can receive a repeat 350-b of the first CORESET 350-a.

[0143] In some examples, a repeat 350-b of the first CORESET 350-a can be indicated by communicating the first CORESET 350-a in a specific frequency band. For example, if the first CORESET 350-a is transmitted or received in a specific frequency band (e.g., a predefined or established frequency band), network entity 375-a can indicate that a CORESET repeat is activated, or UE 115-b can determine that a CORESET repeat is activated. Additionally or alternatively, if the first CORESET 350-a is transmitted or received in a specific frequency band, network entity 375-a can transmit or UE 115-b can receive a repeat 350-b of the first CORESET 350-a. Using the number of first REs, the bandwidth or number of REs, or the frequency band to indicate CORESET repeat provides a way to indicate repeat 350-b using limited resources.

[0144] In some methods, network entity 375-a may send, or UE 115-b may receive, a handover command for a target cell, indicating the activation of CORESET repeats for that target cell (e.g., CORESET repeat configuration for SIB1 or CORESET repeat configuration for type 0 CSS, etc.). Network entity 375-a may send, or UE 115-b may receive neighboring cell information associated with neighboring cells of the target cell. The neighboring cell information may indicate CORESET repeat information for neighboring cells (e.g., the number of CORESET repeats, or the relationship between CORESET repeats, etc.).

[0145] In some respects, the PDCCH of the scheduling SIB can be enhanced. For example, for a PDCCH format scrambled by SI-RNTI in a specific frequency band, one or more bits of the PDCCH associated with the first CORESET 350-a can be fixed or removed. For example, for PDCCH format 1_0 scrambled by SI-RNTI in a specific frequency band, some or all of the reserved bits can be removed, or the values ​​of some or all of these bits can be fixed. Removing some or all of the reserved bits, or fixing some or all of the values ​​of these reserved bits, can improve the decoding performance of the PDCCH.

[0146] In some examples, a PDSCH carrying one or more SIBs can be enhanced. The DCI associated with the first CORESET 350-a can indicate the number of slots used for aggregation of the PDSCH carrying the SIBs. For example, network entity 375-a or UE 115-b can support slot aggregation for one or more PDSCHs carrying one or more SIBs. The number of slots aggregated can be indicated in the DCI (e.g., using one or more reserved bits). In some approaches, one or more PDSCHs (e.g., one or more enhanced PDSCHs) can be scheduled using CSS (e.g., the first CORESET 350-a including the DCI or a repetition of the first CORESET 350-a can be conveyed in the CSS).

[0147] In some examples, network entity 375-a may send or UE 115-b may receive an SSB (e.g., before the first CORESET 350-a). The search space may be monitored based on the timing of the monitoring occurring within a threshold period after the SSB. In some aspects, for multiple CORESET 320s, UE 115-b may not monitor the search space after a threshold period following the most recent SSB.

[0148] Figure 4 An example of a timing diagram 400 supporting signaling for system information blocks according to one or more aspects of this disclosure is shown. In some examples, a UE (e.g., UE 115, UE 115-a, or 115-b) or network entity (e.g., network entity 105, CU 160-a, DU 165-a, RU 170-a, network entity 375-a) may utilize or perform reference according to one or more techniques described herein. Figure 4 One or more of the described elements, structures, or operations.

[0149] Figure 4 An example of an enhanced PDCCH scheduling one or more SIBs is shown. Timing diagram 400 is illustrated with frequency 430 varying over time 425. In some examples, the search space is located within monitoring timing 405. Some methods may utilize CORESET repetition or extension. Figure 4 The example illustrates multiple CORESETs, including a first CORESET 415-a, a second CORESET 415-b, and a third CORESET 415-c. The CORESET at monitoring time 405 can be repeated N times, where... Figure 4In the example, N=3. In other examples, other numbers of repetitions may be used or specified (e.g., N=2, N=4, etc.). In some examples, the term "repetition" or variations thereof may refer to the initial element and one or more subsequent elements that match the initial element, or to one or more elements that follow the initial element and match the initial element.

[0150] In some examples, the frequency and time positions of repeating CORESET instances can be defined (e.g., predefined). For example, the first position 435-a (e.g., RE or RE index) of the second CORESET 415-b can be located at a predefined frequency and predefined time relative to the first CORESET 415-a. The second position 435-b (e.g., RE or RE index) of the third CORESET 415-c can be located at a predefined frequency and predefined time relative to the first CORESET 415-a. For example, the RE of the second CORESET 415-b can be located at a predefined frequency offset or predefined time offset (e.g., RE index offset) from the first CORESET 415-a, or the RE of the third CORESET 415-c can be located at a predefined frequency offset or predefined time offset (e.g., RE index offset) from the first CORESET 415-a. In some examples, a CORESET can be positioned relative to the immediately preceding CORESET. For example, the third CORESET 415-c may be located at a predefined frequency and predefined time relative to the second CORESET 415-b.

[0151] like Figure 4As illustrated, a first CORESET 415-a may include a first PDCCH 420-a, a second CORESET 415-b may include a second PDCCH 420-b, and a third CORESET 415-c may include a third PDCCH 420-c. In some examples, the number of REs in a repeating CORESET or PDCCH may be the same as the number of REs in the original CORESET or PDCCH. For example, the second CORESET 415-b and the third CORESET 415-c may have the same number of REs as the first CORESET 415-a. Additionally or alternatively, the second PDCCH 420-b and the third PDCCH 420-c may have the same number of REs as the first PDCCH 420-a. Accordingly, a network entity may transmit or a UE may receive the same number of REs for each of a plurality of CORESETs or for each of a plurality of PDCCHs. For bandwidths of 5MHz or lower, the maximum aggregation level of PDCCH can be 8 (e.g., CORESET can have up to 3 symbols).

[0152] In some examples of PDCCHs, the RE set in duplicate CORESET instances can be derived from the RE set in the original CORESET (e.g., the same RE set from both CORESETs can be used). For example, the RE set of the second PDCCH 420-b within the second CORESET 415-b can be the same as the RE set of the first PDCCH 420-a within the first CORESET 415-a. In some examples, different RE sets can be used for PDCCHs between different CORESETs. In some aspects, the RE relationships of PDCCHs between CORESETs (e.g., the same or different REs) can be predefined.

[0153] In some examples, network entities (e.g., network entity 105, CU 160-a, DU 165-a, RU 170-a, network entity 375-a) may transmit, or UEs (e.g., UE 115, UE 115-a, or 115-b) may receive, one or more of the first CORESET 415-a, the second CORESET 415-b, or the third CORESET 415-c. For example, a UE may monitor one or more search spaces during monitoring timing 405 to receive the first CORESET 415-a, the second CORESET 415-b, or the third CORESET 415-c by attempting to decode the received signals (e.g., the first PDCCH 420-a, the second PDCCH 420-b, and the third PDCCH 420-c) in the REs corresponding to the first CORESET 415-a, the second CORESET 415-b, and the third CORESET 415-c. In some methods, the position of the first CORESET 415-a can be determined by the previously received SSB (in Figure 4 (Not shown in the diagram) to indicate or configure, or the UE may perform blind decoding on one or more search spaces to determine the location of the first CORESET 415-a. Using the location of the first CORESET 415-a and a predefined first location 435-a, the UE may receive the second CORESET 415-b. Using the location of the first CORESET 415-a and a predefined second location 435-b, the UE may receive the third CORESET 415-c. In some methods, the first CORESET 415-a, the second CORESET 415-b, or the third CORESET 415-c (e.g., the first PDCCH 420-a, the second PDCCH 420-b, or the third PDCCH 420-c) may be combined for decoding.

[0154] In some methods, if decoding of the first CORESET 415-a fails, the UE may attempt to decode the second CORESET 415-b or the third CORESET 415-c, which may indicate whether CORESET duplication is activated. For example, for CORESET0 for SIB1, no signaling may be used to notify of CORESET duplication or extension (e.g., before sending the SIB1). For example, for CORESET0 used for SIB1 scheduling, the UE performs blind decoding for both cases with and without CORESET duplication. In some methods, the UE may first attempt to decode the first CORESET 415-a assuming no duplication. If decoding of the first CORESET 415-a fails, the UE may then attempt to decode assuming CORESET duplication is applied.

[0155] In some respects, CORESET repeating can be indicated. For example, CORESET repeating can be indicated via, as referenced... Figure 3 The CRC mask, DMRS scrambling, or encoded DCI bit scrambling associated with the first CORESET 415-a is described to indicate this. For example, to allow the UE to distinguish whether CORESET repetition has been applied, a different CRC mask (e.g., RNTI), a different DMRS scrambling sequence, or a different DCI scrambling may be applied if CORESET repetition is activated (e.g., applied). Additionally or alternatively, the network entity may notify the UE of CORESET0 repetition information in an SIB1 for one or more subsequent SIB1s.

[0156] Additionally or alternatively, CORESET repetition can be indicated by a first number of REs associated with the first CORESET 415-a that satisfies a first threshold, by a bandwidth or number of REs that satisfies a second threshold, or by transmitting the first CORESET 415-a in a frequency band associated with the CORESET repetition. For example, CORESET repetition may be supported in one or more frequency bands (e.g., may be limited thereto), may be supported when the CORESET size (e.g., number of REs) is less than a threshold, or may be supported when the bandwidth is less than a threshold.

[0157] Additionally or alternatively, CORESET repetition can be indicated via a handover command. For example, CORESET repetition information for the target cell of an SIB is included in the handover command. CORESET repetition information for an SIB (e.g., SIB19) for one or more neighboring cells can be included in the neighboring cell information.

[0158] Using one or more of these indications (to allow the UE to distinguish when repetition is activated) can help avoid the following situation: when repetition is not applied, the UE may fail to decode the PDCCH in the initial CORESET, but may attempt to decode subsequent PDCCHs assuming CORESET repetition is applied. Alternatively, using one or more of these indications can help avoid the following situation: when repetition is applied, the UE decodes the PDCCH assuming no repetition is applied.

[0159] In some aspects, the first PDCCH 420-a, the second PDCCH 420-b, or the third PDCCH 420-c may include information (e.g., DCI) for scheduling subsequent PDSCHs or SIBs (e.g., SIB1). Reference Figure 3 and Figure 5 Examples of PDSCH or SIBs scheduled by one or more CORESETs are given.

[0160] Figure 5 An example of a timing diagram 500 supporting signaling for a system information block according to one or more aspects of this disclosure is shown. The timing diagram 500 is illustrated as a change over time 550. In some examples, a UE (e.g., UE 115, UE 115-a, or 115-b) or network entity (e.g., network entity 105, CU 160-a, DU 165-a, RU 170-a, network entity 375-a) may utilize or perform reference according to one or more techniques described herein. Figure 5 One or more of the described elements, structures, or operations.

[0161] exist Figure 5 The diagram illustrates an example of enhancements for SIB transmissions (e.g., SIB1 or SIB19 for NTNs). During initial access and before the UE acquires ephemeris information (e.g., by decoding SIB19), the UE may lack information about the Doppler effect of the received downlink signal, or about time variations due to feeder link delays and satellite movement. For example, in an NTN, the Doppler effect or round-trip time (RTT) can vary over time. Due to Doppler or timing variations, the reception performance of the PDCCH or PDSCH may degrade if it is relatively far from the received SSB in time (e.g., greater than 750ms, 500ms, 250ms, 100ms, or 50ms, etc.). Increasing the periodicity of SSB transmissions can reduce downlink overhead signaling.

[0162] In some examples, a network entity may transmit or a UE may receive SSB 505. To address Doppler or RTT changes following SSB 505, the monitoring timing 555 may be limited to occur within a threshold period 560 after SSB 505 (e.g., from the start or end of SSB 505). For example, the PDCCH 510 monitoring timing for SIB1 or SIB19 may be limited to a threshold period 560 after the transmission of SSB 505. In some aspects, the UE may not monitor PDCCH monitoring timings that occur more than a threshold period 560 (e.g., Xms) after the most recent SSB 505 transmission. The threshold period 560 may be predefined, depending on the subcarrier spacing (SCS) (e.g., it may vary based on it), or depending on the frequency range (e.g., it may vary based on it). In some aspects, one or more monitoring timings may be defined for one or more SIBs (e.g., SIB1 or SIB19) based on the SSB transmission time.

[0163] like Figure 5 As illustrated in the example, monitoring timing 555 occurs within a threshold period 560 following SSB 505. One or more first CORESETs 515 may be received during monitoring timing 555. In some methods, the one or more first CORESETs 515 may include an initial CORESET and one or more CORESET repetitions located at a predefined time or predefined frequency relative to the initial CORESET, as referenced. Figure 3 or Figure 4 As described. For example, one or more PDCCH 510s may be received in one or more first CORESET 515s.

[0164] In some respects, the PDCCH 510 (e.g., one or more PDCCH 510s) of the first SIB 530 can be enhanced. For example, for a PDCCH format scrambled by SI-RNTI in a specific frequency band, one or more bits of the PDCCH 510 associated with the first CORESET 515 may be fixed or removed. For example, for a PDCCH format 1_0 scrambled by SI-RNTI in a specific frequency band, some or all of the reserved bits may be removed, or the values ​​of some or all of these bits may be fixed. Removing some or all of the reserved bits, or fixing some or all of the values ​​of these reserved bits, can improve the decoding performance for the PDCCH 510.

[0165] A PDCCH 510 (e.g., DCI 520) may schedule one or more PDSCH 525s or a first SIB 530 (e.g., one or more SIB1s). In some examples, a DCI 520 associated with a first CORESET 515 (e.g., included in the PDCCH 510) may indicate the number of slots used for aggregation of PDSCH 525s carrying the first SIB 530 (e.g., PDSCH repetition). For example, network entity 375-a or UE 115-b may support slot aggregation for one or more PDSCH 525s carrying one or more first SIBs 530s. The number of slots aggregated may be indicated in the DCI 520 (e.g., using one or more reserved bits). In some approaches, one or more PDSCH 525s may be scheduled using a CSS (e.g., one or more first CORESET 515s including the DCI 520 may be communicated in the CSS).

[0166] The first SIB 530 may indicate the repetition of a second CORESET 535 specific to one or more search space types. In some aspects, CORESET repetition or extension of one or more other SIBs of the serving cell may be signaled in the first SIB 530 (e.g., SIB1). For example, the first SIB 530 may indicate the number or pattern of repetitions of one or more other SIBs that may be specific to a corresponding search space type or SIB type. In some aspects, SIB1 may indicate that CORESET repetition is activated for one or more second CORESETs 535, wherein these second CORESETs 535 are specific to the search space type. For example, CORESET repetition may be specifically applied to SIB19 (e.g., SIB1 may use two CORESET repetitions, and SIB19 may use three CORESET repetitions). Figure 5 As illustrated, one or more second CORESET 535s may include one or more corresponding PDCCH 540s. The second CORESET 535 (e.g., PDCCH) may schedule the second SIB 545.

[0167] In some aspects, repetition of the first CORESET may include a subset of the content of the first CORESET (e.g., and may exclude a second subset of the content of the first CORESET). As an illustrative example, the first CORESET may be used by a first search space with PDCCH repetition enabled and a second search space without PDCCH repetition enabled. In such examples, repetition of the first CORESET may include repetition of the PDCCHs associated with the first search space, and may exclude repetition of the PDCCHs associated with the second search space. In some other examples (e.g., if repetition is enabled for each search space using the first CORESET), repetition of the first CORESET may include the same content as the first CORESET.

[0168] Some examples of the techniques described herein can be performed jointly or independently. In some methods, monitoring timing constraints or thresholding can be performed independently of one or more other techniques described herein. In some methods, CORESET repetition can be performed independently of one or more other techniques described herein. In some methods, slot aggregation (e.g., DCI indicating slot aggregation for PDSCH) can be performed independently of one or more other techniques described herein. In some methods, CORESET repetition indicating a SIB-specific type (e.g., SIB19) can be performed independently of one or more other techniques described herein.

[0169] Figure 6 An example of a process flow 600 supporting signaling for a system information block according to one or more aspects of this disclosure is shown. Process flow 600 may include UE 115-c, which may be an example of UE 115, UE 115-a, or UE 115-b as described herein. Process flow 600 may also include network entity 375-b, which may be an example of network entity 375-a as described herein (e.g., an NTN node, TN node, or other network entity).

[0170] In the following description of process flow 600, communication between UE 115-c and network entity 375-b may be sent in a different order than the example shown, or operations performed by UE 115-c or network entity 375-b may be performed in a different order or at different times. Some operations may also be omitted from process flow 600, or other operations may be added to process flow 600. Furthermore, although some operations or signaling are shown to occur at different times for discussion purposes, these operations may actually occur simultaneously or in some examples within overlapping time periods.

[0171] At 605, network entity 375-b may send an indication to UE 115-c. For example, an indication may be sent to UE 115-c to indicate that CORESET repetition has been activated. In some examples, indication 605 may include a CRC mask, DMRS scrambling, or encoded DCI bit scrambling (e.g., for the first CORESET), or may be included in a handover command. Additionally or alternatively, the indication may be provided by the number of REs satisfying a first threshold, by the bandwidth or number of REs satisfying a second threshold, or by conveying the first CORESET in a specific frequency band. Reference Figure 3 - Figure 5 One or more diagrams in the diagram describe additional examples indicating CORESET repetition.

[0172] At 610, network entity 375-b can send or UE 115-c can receive the first CORESET. For example, UE 115-c can monitor the search space to receive the first CORESET, as referenced. Figure 3 - Figure 5 One or more diagrams in the diagram are described.

[0173] At point 615, network entity 375-b may transmit or UE 115-c may receive a second CORESET. The second CORESET may be a repetition of the first CORESET (e.g., it may have the same candidate index and aggregation level as the first CORESET). For example, UE 115-c may receive the second CORESET at a time or frequency defined relative to the first CORESET, as referenced. Figure 3 - Figure 5 The time and / or frequency are described in one or more figures. In some examples, the time and / or frequency may be indicated via SIB1. In some methods, the time and / or frequency may be represented by a RE relative to one or more first REs corresponding to the first CORESET (e.g., RE offset in time and frequency). In some examples (e.g., for intra-slot repetition), the RE corresponding to the second CORESET may be in the same time slot as the first RE corresponding to the first CORESET. In some examples (e.g., for inter-slot repetition), the RE corresponding to the second CORESET may be in a different time slot than the first RE corresponding to the first CORESET.

[0174] The first or second core set may include information for scheduling SIB1 (e.g., one or more PDCCHs, control messages, or DCIs). For example, UE 115-c may decode the first and second core sets to determine the scheduling (e.g., RE) for SIB1 reception.

[0175] At 620, network entity 375-b can send or UE 115-c can receive SIB1. For example, UE 115-c can receive messages scheduled by the first CORESET or the second CORESET (e.g., PDSCH including SIB1), as referenced. Figure 3 or Figure 5 As described in one or more figures in the diagram. SIB1 may indicate that CORESET repeat is activated for SIB19. For example, SIB1 may include bits, permutations, codes, or other information indicating that CORESET repeat is activated or configured for CORESET communication corresponding to SIB19.

[0176] At position 625, network entity 375-b can send or UE 115-c can receive additional CORESETs. For example, UE 115-c can monitor the search space to receive additional CORESETs, as referenced. Figure 3 or Figure 5 One or more diagrams in the diagram are described.

[0177] At 630, network entity 375-b can transmit or UE 115-c can receive a third CORESET, which can be a repetition of the additional CORESET. For example, UE 115-c can receive a repetition of the additional CORESET at a time or frequency defined relative to the additional CORESET, as referenced. Figure 3 - Figure 5 As described in one or more figures. In some methods, the time or frequency may be represented based on a RE relative to one or more second REs corresponding to the additional CORESET (e.g., RE offset in time and frequency).

[0178] Additional CORESETs or repetitions of additional CORESETs may include information for scheduling SIB19 (e.g., PDCCH, control messages, or DCI). For example, UE 115-c may decode a second CORESET or a repetition of a second CORESET to determine the scheduling (e.g., RE) for SIB19 reception.

[0179] At 635, network entity 375-b can send or UE 115-c can receive SIB19. For example, UE 115-c can receive messages (e.g., PDSCH including SIB19) that are repeatedly scheduled by an additional CORESET or an additional CORESET, as referenced. Figure 3 or Figure 5 The SIB19 may include Doppler information, ephemeris information, or other information (e.g., timing information).

[0180] At 640, network entity 375-b or UE 115-c may communicate based on SIB19 (e.g., transmit or receive one or more signals). For example, UE 115-c may utilize Doppler or ephemeris information from SIB19 for filtering to compensate for Doppler frequency shifts in one or more signals received from network entity 375-b. Additionally or alternatively, UE 115-c may use ephemeris information to track network entity 375-b, perform power control, perform inter-cell handover or transfer, perform transmit signal beamforming, or perform receive signal beamforming, etc.

[0181] Figure 7 A block diagram 700 illustrates a device 705 supporting signaling for system information blocks according to one or more aspects of this disclosure. Device 705 may be an example of various aspects of UE 115 as described herein. Device 705 may include a receiver 710, a transmitter 715, and a communication manager 720. Device 705 or one or more components of device 705 (e.g., receiver 710, transmitter 715, communication manager 720) may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0182] Receiver 710 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to signaling for system information blocks). The information may be delivered to other components of device 705. Receiver 710 may utilize a single antenna or a collection of antennas.

[0183] Transmitter 715 may provide components for transmitting signals generated by other components of device 705. For example, transmitter 715 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to signaling for system information blocks). In some examples, transmitter 715 may be co-located with receiver 710 in a transceiver module. Transmitter 715 may utilize a single antenna or a collection of multiple antennas.

[0184] The communication manager 720, receiver 710, transmitter 715, or various combinations or components thereof may be examples of components used to perform various aspects of signaling for system information blocks as described herein. For example, the communication manager 720, receiver 710, transmitter 715, or various combinations or components thereof may be able to perform one or more of the functions described herein.

[0185] In some examples, the communication manager 720, receiver 710, transmitter 715, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of the following: a processor, digital signal processor (DSP), central processing unit (CPU), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, microcontroller, discrete gate or transistor logic component, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0186] Additionally or alternatively, the communication manager 720, receiver 710, transmitter 715, or various combinations or components thereof may be implemented in code (e.g., as communication management software or firmware) (e.g., referred to as processor executable code) executed by at least one processor. If implemented in code executed by at least one processor, the functionality of the communication manager 720, receiver 710, transmitter 715, or various combinations or components thereof may be performed by (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices configured, either individually or collectively, as components for performing the functions described in this disclosure).

[0187] In some examples, the communication manager 720 may be configured to use a receiver 710, a transmitter 715, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 720 may receive information from the receiver 710, transmit information to the transmitter 715, or integrate with the receiver 710, the transmitter 715, or both to acquire information, output information, or perform various other operations as described herein.

[0188] The communication manager 720 may support wireless communication according to examples disclosed herein. For example, the communication manager 720 may be capable of, configured to, or operable to support components for monitoring a search space during a monitoring period to obtain a set of multiple cores, the set of multiple cores including a first core and a second core. The communication manager 720 may be capable of, configured to, or operable to support components for receiving a second core from a network entity via a second RE during a monitoring period, these second REs being located at a predefined time and predefined frequency relative to a first RE associated with the first core, the second core including control messages for scheduling message transmission. The communication manager 720 may be capable of, configured to, or operable to support components for communicating messages with a network entity using information indicated by control messages included in the second core.

[0189] By including or configuring a communication manager 720 according to an example as described herein, device 705 (e.g., controlling receiver 710, transmitter 715, communication manager 720 or a combination thereof or at least one processor otherwise coupled to them) can support techniques for reducing processing, lowering power consumption or utilizing communication resources more efficiently.

[0190] Figure 8 A block diagram 800 of a device 805 supporting signaling for system information blocks according to one or more aspects of this disclosure is shown. Device 805 may be an example of aspects of device 705 or UE 115 as described herein. Device 805 may include a receiver 810, a transmitter 815, and a communication manager 820. Device 805 or one or more components of device 805 (e.g., receiver 810, transmitter 815, communication manager 820) may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0191] Receiver 810 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to signaling for system information blocks). The information may be delivered to other components of device 805. Receiver 810 may utilize a single antenna or a collection of antennas.

[0192] Transmitter 815 may provide components for transmitting signals generated by other components of device 805. For example, transmitter 815 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to signaling for system information blocks). In some examples, transmitter 815 may be co-located with receiver 810 in a transceiver module. Transmitter 815 may utilize a single antenna or a collection of multiple antennas.

[0193] Device 805 or its various components may be examples of parts for performing various aspects of signaling for system information blocks as described herein. For example, communication manager 820 may include monitoring component 825, repeating component 830, messaging component 835, or any combination thereof. Communication manager 820 may be examples of aspects of communication manager 720 as described herein. In some examples, communication manager 820 or its various components may be configured to use receiver 810, transmitter 815, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 820 may receive information from receiver 810, transmit information to transmitter 815, or be integrated in combination with receiver 810, transmitter 815, or both to acquire information, output information, or perform various other operations as described herein.

[0194] The communication manager 820 may support wireless communication according to examples disclosed herein. The monitoring component 825 is capable of, configured to, or operable to support components for monitoring a search space during a monitoring period to obtain a set of multiple cores, including a first core and a second core. The repeating component 830 is capable of, configured to, or operable to support components for receiving a second core from a network entity via a second RE during a monitoring period, these second REs being located at a predefined time and predefined frequency relative to a first RE associated with the first core, the second core including control messages for scheduling message transmission. The messaging component 835 is capable of, configured to, or operable to support components for communicating messages with a network entity using information indicated by control messages included in the second core.

[0195] Figure 9A block diagram 900 is shown of a communication manager 920 supporting signaling for system information blocks according to one or more aspects of this disclosure. The communication manager 920 may be an example of a communication manager 720, a communication manager 820, or aspects thereof as described herein. The communication manager 920 or its various components may be examples of components for performing various aspects of signaling for system information blocks as described herein. For example, the communication manager 920 may include a monitoring component 925, a repeating component 930, a messaging component 935, a detection component 940, a decoding component 945, a handover component 950, a cell component 955, an SSB receiving component 960, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses).

[0196] The communication manager 920 may support wireless communication according to examples disclosed herein. The monitoring component 925 is capable of, configured to, or operable to support components for monitoring a search space during a monitoring period to obtain a set of multiple cores, including a first core and a second core. The repeating component 930 is capable of, configured to, or operable to support components for receiving a second core from a network entity via a second RE during a monitoring period, these second REs being located at a predefined time and predefined frequency relative to a first RE associated with the first core, the second core including control messages for scheduling message transmission. The messaging component 935 is capable of, configured to, or operable to support components for communicating messages with a network entity using information indicated by control messages included in the second core.

[0197] In some examples, the message includes SIB1 in the PDSCH, which is scheduled based on the set of multiple CORESETs, and the SIB1 indicates the repetition of CORESETs specific to one or more search space types (e.g., one or more search space types).

[0198] In some examples, the repeating component 930 is capable of, can be configured or operable to support repeating components for receiving CORESET based on SIB1.

[0199] In some examples, detection component 940 is capable of, configured to, or operable to support components for detecting a failure to decode the first CORESET via the first RE associated with the first CORESET. In some examples, monitoring component 925 is capable of, configured to, or operable to support components for monitoring a second CORESET via a second RE during a monitoring period based on the assumption that CORESET repetition has been activated in response to a failure to decode the first CORESET.

[0200] In some examples, monitoring of the second CORESET uses blind decoding without prior indication that CORESET repetition has been activated.

[0201] In some examples, the decoding component 945 is capable of, configured to, or operable to support components for decoding the PDCCH using a combination of the first CORESET and the second CORESET.

[0202] In some examples, the second CORESET is indicated by a CRC mask, DMRS scrambling, or coded DCI bit scrambling.

[0203] In some examples, the second CORESET is indicated by the number of first REs associated with the first CORESET that satisfy a first threshold, by the bandwidth or number of REs associated with the first CORESET that satisfy a second threshold, or by transmitting the first CORESET in a specific frequency band.

[0204] In some examples, the handover component 950 is capable of, configured to, or operable to support components for receiving a handover command for a target cell that indicates activation of CORESET repeat. In some examples, the cell component 955 is capable of, configured to, or operable to support components for receiving neighboring cell information associated with neighboring cells of the target cell that indicates CORESET repeat information for that neighboring cell.

[0205] In some examples, for a PDCCH format scrambled by SI-RNTI in a specific frequency band, one or more bits of the PDCCH associated with the first CORESET are fixed or removed.

[0206] In some examples, the DCI associated with the first CORESET indicates the number of time slots used to aggregate the PDSCH carrying the SIB.

[0207] In some examples, PDSCH is dispatched via CSS.

[0208] In some examples, the SSB receiving component 960 is capable of, configured to, or operable to support components for receiving synchronization signal blocks (SSBs), wherein the search space is monitored based on the timing of the monitoring occurring within a threshold period following the SSB.

[0209] Figure 10 A diagram of a system 1000 including device 1005 supporting signaling for system information blocks according to one or more aspects of this disclosure is shown. Device 1005 may be an example of device 705, device 805, or UE 115 as described herein, or may include components thereof. Device 1005 may communicate with one or more other devices (e.g., network entity 105, UE 115, or a combination thereof) (e.g., wirelessly). Device 1005 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 1020, an input / output (I / O) controller (such as I / O controller 1010), a transceiver 1015, one or more antennas 1025, at least one memory 1030, code 1035, and at least one processor 1040. These components may communicate electronically or be coupled in other ways (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 1045).

[0210] I / O controller 1010 manages the input and output signals of device 1005. I / O controller 1010 can also manage peripheral devices not integrated into device 1005. In some cases, I / O controller 1010 may represent a physical connection or port to an external peripheral device. In some cases, I / O controller 1010 may utilize an operating system such as iOS. ® ANDROID ® MS-DOS ® MS-WINDOWS ® OS / 2 ® UNIX ® LINUX ® Alternatively, the I / O controller 1010 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 1010 may be implemented as part of one or more processors, such as at least one processor 1040. In some cases, a user may interact with the device 1005 via the I / O controller 1010 or via hardware components controlled by the I / O controller 1010.

[0211] In some cases, device 1005 may include a single antenna. However, in other cases, device 1005 may have more than one antenna, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 1015 may communicate bidirectionally via one or more antennas 1025 using a wired or wireless link as described herein. For example, transceiver 1015 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 1015 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 1025 for transmission; and demodulating packets received from one or more antennas 1025. Transceiver 1015, or transceiver 1015 and one or more antennas 1025, may be an example of transmitter 715, transmitter 815, receiver 710, receiver 810, or any combination thereof or component thereof as described herein.

[0212] At least one memory 1030 may include random access memory (RAM) and read-only memory (ROM). At least one memory 1030 may store computer-readable code, computer-executable code, or processor-executable code, such as code 1035. Code 1035 may include instructions that, when executed by at least one processor 1040, cause device 1005 to perform the various functions described herein. Code 1035 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1035 may not be directly executable by at least one processor 1040, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, at least one memory 1030 may include a basic I / O system (BIOS), etc., which controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0213] At least one processor 1040 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more CPUs, one or more graphics processing units (GPUs), one or more neural processing units (NPUs) (also referred to as neural network processors or deep learning processors (DLPs)), one or more microcontrollers, one or more ASICs, one or more FPGAs, one or more programmable logic devices, discrete gate or transistor logic units, one or more discrete hardware components, or any combination thereof). In some cases, at least one processor 1040 may be configured to use a memory controller to operate a memory array. In some other cases, the memory controller may be integrated into at least one processor 1040. At least one processor 1040 may be configured to execute computer-readable instructions stored in memory (e.g., at least one memory 1030) to cause device 1005 to perform various functions (e.g., functions or tasks supporting signaling for system information blocks). For example, device 1005 or components of device 1005 may include at least one processor 1040 and at least one memory 1030 coupled to or coupled to at least one processor 1040, wherein at least one processor 1040 and at least one memory 1030 are configured to perform the various functions described herein.

[0214] In some examples, at least one processor 1040 may include multiple processors, and at least one memory 1030 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 1040 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuitry (including, for example, one or both of processor circuitry (which may include at least one processor 1040) and memory circuitry (which may include at least one memory 1030)) or components that receive or receive input and process the input to produce, generate, or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, at least one processor 1040 or a processing system including at least one processor 1040 may be configured, capable of being configured, or operable to cause device 1005 to perform one or more of the functions described herein. Furthermore, as described herein, “configured to,” “capable of being configured to,” and “capable of operating to” are used interchangeably and can be associated with the ability to perform one or more of the functions described herein when executing code 1035 (e.g., processor-executable code) stored in at least one memory 1030 or otherwise executing the code.

[0215] The communication manager 1020 may support wireless communication according to examples disclosed herein. For example, the communication manager 1020 may be capable of, configured to, or operable to support components for monitoring a search space during a monitoring period to obtain a set of multiple cores, the set of multiple cores including a first core and a second core. The communication manager 1020 may be capable of, configured to, or operable to support components for receiving a second core from a network entity via a second RE during a monitoring period, these second REs being located at a predefined time and predefined frequency relative to a first RE associated with a first core, the second core including control messages for scheduling message transmission. The communication manager 1020 may be capable of, configured to, or operable to support components for communicating messages with a network entity using information indicated by control messages included in the second core.

[0216] By including or configuring a communication manager 1020 according to an example as described herein, device 1005 can support technologies for improving communication reliability, reducing latency, reducing power consumption, utilizing communication resources more efficiently, improving coordination between devices, extending battery life, or improving processing power.

[0217] In some examples, the communication manager 1020 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using a transceiver 1015, one or more antennas 1025, or any combination thereof, or otherwise cooperating with them. Although the communication manager 1020 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1020 may be supported or performed by at least one processor 1040, at least one memory 1030, code 1035, or any combination thereof. For example, code 1035 may include instructions that can be executed by at least one processor 1040 to cause the device 1005 to perform various aspects of signaling for system information blocks as described herein, or at least one processor 1040 and at least one memory 1030 may be otherwise configured to perform or support such operations individually or jointly.

[0218] Figure 11A block diagram 1100 of a device 1105 supporting signaling for system information blocks according to one or more aspects of this disclosure is shown. Device 1105 may be an example of aspects of network entity 105 as described herein. Device 1105 may include receiver 1110, transmitter 1115, and communication manager 1120. Device 1105 or one or more components of device 1105 (e.g., receiver 1110, transmitter 1115, communication manager 1120) may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0219] Receiver 1110 may provide components for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be delivered to other components of device 1105. In some examples, receiver 1110 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1110 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0220] Transmitter 1115 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1105. For example, transmitter 1115 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 1115 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 1115 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 1115 and receiver 1110 may be co-located in a transceiver, which may include or be coupled to a modem.

[0221] The communication manager 1120, receiver 1110, transmitter 1115, or various combinations or components thereof may be examples of components used to perform various aspects of signaling for system information blocks as described herein. For example, the communication manager 1120, receiver 1110, transmitter 1115, or various combinations or components thereof may be able to perform one or more of the functions described herein.

[0222] In some examples, the communication manager 1120, receiver 1110, transmitter 1115, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of a processor, DSP, CPU, ASIC, FPGA, or other programmable logic device, microcontroller, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0223] Additionally or alternatively, the communication manager 1120, receiver 1110, transmitter 1115, or various combinations or components thereof may be implemented in code (e.g., as communication management software or firmware) (e.g., referred to as processor executable code) executed by at least one processor. If implemented in code executed by at least one processor, the functionality of the communication manager 1120, receiver 1110, transmitter 1115, or various combinations or components thereof may be executed by (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices configured, either individually or collectively, as components for performing the functions described in this disclosure).

[0224] In some examples, the communication manager 1120 may be configured to use the receiver 1110, the transmitter 1115, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 1120 may receive information from the receiver 1110, transmit information to the transmitter 1115, or be integrated with the receiver 1110, the transmitter 1115, or both to acquire information, output information, or perform various other operations as described herein.

[0225] The communication manager 1120 may support wireless communication according to examples disclosed herein. For example, the communication manager 1120 may be capable of, configured to, or operable to support components for transmitting a set of multiple cores in a search space during a monitoring period, the set of multiple cores including a first core and a second core, wherein the second core is transmitted via second REs located at a predefined time and a predefined frequency relative to a first RE associated with the first core, the second core including control messages for scheduling message transmission. The communication manager 1120 may be capable of, configured to, or operable to support components for communicating messages with the UE using information indicated by control messages included in the second core.

[0226] By including or configuring a communication manager 1120 according to an example as described herein, device 1105 (e.g., controlling receiver 1110, transmitter 1115, communication manager 1120, or a combination thereof, or at least one processor otherwise coupled to them) can support techniques for reducing processing, lowering power consumption, or utilizing communication resources more efficiently.

[0227] Figure 12 A block diagram 1200 of a device 1205 supporting signaling for system information blocks according to one or more aspects of this disclosure is shown. Device 1205 may be an example of aspects of device 1105 or network entity 105 as described herein. Device 1205 may include a receiver 1210, a transmitter 1215, and a communication manager 1220. Device 1205 or one or more components of device 1205 (e.g., receiver 1210, transmitter 1215, communication manager 1220) may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0228] Receiver 1210 may provide components for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be delivered to other components of device 1205. In some examples, receiver 1210 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1210 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0229] Transmitter 1215 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1205. For example, transmitter 1215 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 1215 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 1215 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 1215 and receiver 1210 may be co-located in a transceiver, which may include or be coupled to a modem.

[0230] Device 1205 or its various components may be examples of components used to perform various aspects of signaling for system information blocks as described herein. For example, communication manager 1220 may include repeat manager 1225, message manager 1230, or any combination thereof. Communication manager 1220 may be examples of aspects of communication manager 1120 as described herein. In some examples, communication manager 1220 or its various components may be configured to use receiver 1210, transmitter 1215, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 1220 may receive information from receiver 1210, transmit information to transmitter 1215, or be integrated in combination with receiver 1210, transmitter 1215, or both to acquire information, output information, or perform various other operations as described herein.

[0231] Communication manager 1220 may support wireless communication according to examples disclosed herein. Repeat manager 1225 is capable of, configured to, or operable to support components for transmitting a set of multiple cores in a search space during a monitoring period, the set of multiple cores including a first core and a second core, wherein the second core is transmitted via second REs located at a predefined time and predefined frequency relative to a first RE associated with the first core, the second core including control messages for scheduling message transmission. Message manager 1230 is capable of, configured to, or operable to support components for communicating messages to the UE using information indicated by control messages included in the second core.

[0232] Figure 13A block diagram 1300 is shown of a communication manager 1320 supporting signaling for system information blocks according to one or more aspects of this disclosure. Communication manager 1320 may be an example of communication manager 1120, communication manager 1220, or aspects thereof as described herein. Communication manager 1320 or its various components may be examples of components for performing various aspects of signaling for system information blocks as described herein. For example, communication manager 1320 may include a repeat manager 1325, a message manager 1330, a handover manager 1335, a cell manager 1340, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses). Communication may include communication within protocol layers of a protocol stack, communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack, within devices, components, or virtualization components associated with network entity 105, between devices, components, or virtualization components associated with network entity 105), or any combination thereof.

[0233] Communication manager 1320 may support wireless communication according to examples disclosed herein. Repeat manager 1325 is capable of, configured to, or operable to support components for transmitting a set of multiple cores in a search space during a monitoring period, the set of multiple cores including a first core and a second core, wherein the second core is transmitted via second REs located at a predefined time and predefined frequency relative to a first RE associated with the first core, the second core including control messages for scheduling message transmission. Message manager 1330 is capable of, configured to, or operable to support components for communicating messages to the UE using information indicated by control messages included in the second core.

[0234] In some examples, the message includes SIB1 in the PDSCH, which is scheduled based on the set of multiple CORESETs, and the SIB1 indicates the repetition of CORESETs of a type specific to one or more search spaces.

[0235] In some examples, the repeat manager 1325 is capable of, configured to, or operable to support components for sending repeats of the CORESET based on the SIB1.

[0236] In some examples, the second CORESET is indicated by a CRC mask, DMRS scrambling, or coded DCI bit scrambling.

[0237] In some examples, the second CORESET is indicated by the number of first REs associated with the first CORESET that satisfy a first threshold, by the bandwidth or number of REs associated with the first CORESET that satisfy a second threshold, or by transmitting the first CORESET in a specific frequency band.

[0238] In some examples, the handover manager 1335 is capable of, configured to, or operable to support components for sending a handover command for a target cell that indicates activation of CORESET repeat. In some examples, the cell manager 1340 is capable of, configured to, or operable to support components for sending neighboring cell information associated with neighboring cells of the target cell that indicates CORESET repeat information for that neighboring cell.

[0239] Figure 14 A diagram of a system 1400 is shown, including device 1405 supporting signaling for system information blocks according to one or more aspects of this disclosure. Device 1405 may be an example of device 1105, device 1205, or network entity 105 as described herein, or may include components thereof. Device 1405 may communicate with other network devices or network equipment, such as network entity 105, UE 115, or any combination thereof. Communication may include communication via one or more wired interfaces, one or more wireless interfaces, or any combination thereof. Device 1405 may include components that support output and enable communication, such as a communication manager 1420, a transceiver 1410, one or more antennas 1415, at least one memory 1425, code 1430, and at least one processor 1435. These components may communicate electronically or otherwise (e.g., operative ground, communicative ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 1440).

[0240] Transceiver 1410 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. In some examples, transceiver 1410 may include a wired transceiver and be capable of bidirectional communication with another wired transceiver. Additionally or alternatively, in some examples, transceiver 1410 may include a wireless transceiver and be capable of bidirectional communication with another wireless transceiver. In some examples, device 1405 may include one or more antennas 1415 that are capable of (e.g., concurrently) transmitting or receiving wireless transmissions. Transceiver 1410 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., by one or more antennas 1415, by a wired transmitter); receiving the modulated signal (e.g., from one or more antennas 1415, from a wired receiver); and demodulating the signal. In some embodiments, transceiver 1410 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1415 configured to support various receive or acquire operations, or one or more interfaces coupled to one or more antennas 1415 configured to support various transmit or output operations, or combinations thereof. In some embodiments, transceiver 1410 may include one or more processors or one or more memory components or configured to be coupled to such processors or memory components, which are operable to perform or support operations based on received or acquired information or signals, or to generate information or other signals for transmission or other output, or any combination thereof. In some embodiments, transceiver 1410, or transceiver 1410 and one or more antennas 1415, or transceiver 1410 and one or more antennas 1415 and one or more processors or one or more memory components (e.g., at least one processor 1435, at least one memory 1425, or both) may be included in a chip or chip assembly mounted in device 1405. In some examples, transceiver 1410 may be operable to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, and fronthaul communication link 168).

[0241] At least one memory 1425 may include RAM, ROM, or any combination thereof. At least one memory 1425 may store computer-readable code, computer-executable code, or processor-executable code, such as code 1430. Code 1430 may include instructions that, when executed by one or more of the at least one processor 1435, cause device 1405 to perform the various functions described herein. Code 1430 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1430 may not be directly executable by one of the at least one processor 1435, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, at least one memory 1425 may include a BIOS, etc., that controls basic hardware or software operation, such as interaction with peripheral components or devices. In some examples, at least one processor 1435 may include multiple processors, and at least one memory 1425 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein (e.g., as part of a processing system).

[0242] At least one processor 1435 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more CPUs, one or more graphics processing units (GPUs), one or more neural processing units (NPUs) (also referred to as neural network processors or deep learning processors (DLPs)), one or more microcontrollers, one or more ASICs, one or more FPGAs, one or more programmable logic devices, discrete gate or transistor logic units, one or more discrete hardware components, or any combination thereof). In some cases, at least one processor 1435 may be configured to use a memory controller to operate a memory array. In some other cases, the memory controller may be integrated into one or more processors in at least one processor 1435. At least one processor 1435 may be configured to execute computer-readable instructions stored in memory (e.g., one or more memories in at least one memory 1425) to cause device 1405 to perform various functions (e.g., functions or tasks supporting signaling for system information blocks). For example, device 1405 or components of device 1405 may include at least one processor 1435 and at least one memory 1425 coupled to one or more processors in at least processor 1435, the at least one processor 1435 and the at least one memory 1425 being configured to perform the various functions described herein. At least one processor 1435 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that can (e.g., by executing code 1430) host functions for performing the functions of device 1405. At least one processor 1435 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 1405 (such as within one or more memories in at least one memory 1425).

[0243] In some examples, at least one processor 1435 may include multiple processors, and at least one memory 1425 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 1435 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuitry (including, for example, one or both of processor circuitry (which may include at least one processor 1435) and memory circuitry (which may include at least one memory 1425)) or components that receive or obtain input and process the input to produce, generate, or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, at least one processor 1435 or a processing system including at least one processor 1435 may be configured, configured to, or operable to cause device 1405 to perform one or more of the functions described herein. Furthermore, as described herein, “configured to,” “capable of being configured to,” and “capable of operating to” are used interchangeably and can be associated with the ability to perform one or more of the functions described herein when executing code stored in at least one memory 1425 or otherwise executing code.

[0244] In some examples, bus 1440 may support communication at protocol layers of the protocol stack (e.g., within a protocol layer). In some examples, bus 1440 may support communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack), which may include communication performed within components of device 1405, or communication performed between different components of device 1405 that are co-addressable or may be located in different locations (e.g., where device 1405 may refer to a system in which one or more of communication manager 1420, transceiver 1410, at least one memory 1425, code 1430 and at least one processor 1435 may be located in one component of different components or partitioned between different components).

[0245] In some examples, the communication manager 1420 can manage (e.g., via one or more wired or wireless backhaul links) various aspects of communication with the core network 130. For example, the communication manager 1420 can manage the delivery of data communications by client devices, such as one or more UEs 115. In some examples, the communication manager 1420 can manage communication with one or more other network entities 105 and may include a controller or scheduler for (e.g., coordinating one or more other network devices) controlling communication with UE 115. In some examples, the communication manager 1420 may support an X2 interface within LTE / LTE-A wireless communication network technology to provide communication between network entities 105.

[0246] The communication manager 1420 may support wireless communication according to examples disclosed herein. For example, the communication manager 1420 may be capable of, configured to, or operable to support components for transmitting a set of multiple cores in a search space during a monitoring period, the set of multiple cores including a first core and a second core, wherein the second core is transmitted via second REs located at a predefined time and a predefined frequency relative to a first RE associated with the first core, the second core including control messages for scheduling message transmission. The communication manager 1420 may be capable of, configured to, or operable to support components for communicating messages with the UE using information indicated by control messages included in the second core.

[0247] By including or configuring a communication manager 1420 according to an example as described herein, device 1405 can support technologies for improving communication reliability, reducing latency, reducing power consumption, utilizing communication resources more efficiently, improving coordination between devices, extending battery life, or improving processing power.

[0248] In some examples, the communication manager 1420 may be configured to use or cooperate with transceiver 1410, one or more antennas 1415 (e.g., where applicable), or any combination thereof, to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). Although the communication manager 1420 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1420 may be supported or performed by transceiver 1410, one or more processors in at least one processor 1435, one or more memories in at least one memory 1425, code 1430, or any combination thereof (e.g., by a processing system including at least a portion of at least one processor 1435, at least one memory 1425, code 1430, or any combination thereof). For example, code 1430 may include instructions that can be executed by one or more processors in at least one processor 1435 to cause device 1405 to perform various aspects of signaling for system information blocks as described herein, or at least one processor 1435 and at least one memory 1425 may be otherwise configured to perform or support such operations individually or jointly.

[0249] Figure 15 A flowchart illustrating a method 1500 for supporting signaling for a system information block according to one or more aspects of this disclosure is shown. Operation of method 1500 may be implemented by a UE or its components as described herein. For example, operation of method 1500 may be performed by, as referenced... Figures 1 to 10 The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0250] At 1505, the method may include: monitoring the search space during a monitoring period to obtain a set of multiple CORESETs, the set of multiple CORESETs including a first CORESET and a second CORESET. The operation at 1505 may be performed according to examples as disclosed herein. In some examples, aspects of the operation at 1505 may be derived from references... Figure 9 The monitoring component 925 described is used to perform this.

[0251] At 1510, the method may include: receiving a second CORESET from a network entity via a second RE during a monitoring period, the second RE being located at a predefined time and predefined frequency relative to a first RE associated with the first CORESET, the second CORESET including control messages for the transmission of scheduling messages. The operation of 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1510 may be derived from references... Figure 9 The described repetitive component 930 is executed.

[0252] At 1515, the method may include: communicating a message to a network entity using information indicated by a control message included in the second CORESET. The operation of 1515 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1515 may be provided by reference to [reference needed]. Figure 9 The message component 935 described is used for execution.

[0253] Figure 16 A flowchart illustrating a method 1600 for supporting signaling for a system information block according to one or more aspects of this disclosure is shown. Operation of method 1600 may be implemented by a UE or its components as described herein. For example, operation of method 1600 may be performed by, as referenced... Figures 1 to 10 The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0254] At 1605, the method may include receiving an SSB. The operation of 1605 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1605 may be provided by reference to [reference needed]. Figure 9 The SSB receiving component 960 described herein is used to perform this action.

[0255] At 1610, the method may include: monitoring a search space during a monitoring period to obtain a set of multiple CORESETs, the set of multiple CORESETs including a first CORESET and a second CORESET, wherein the monitoring of the search space is based on the monitoring period occurring within a threshold period after the SSB. The operation of 1610 may be performed according to examples as disclosed herein. In some examples, aspects of the operation at 1610 may be derived from references... Figure 9 The monitoring component 925 described is used to perform this.

[0256] At 1615, the method may include: receiving a second CORESET from a network entity via a second RE during a monitoring period, the second RE being located at a predefined time and predefined frequency relative to a first RE associated with the first CORESET, the second CORESET including control messages for the transmission of scheduling messages. The operation of 1615 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1615 may be provided by reference to [reference]. Figure 9 The described repetitive component 930 is executed.

[0257] At 1620, the method may include: communicating a message to a network entity using information indicated by a control message included in the second CORESET. The operation of 1620 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1620 may be provided by reference to [reference needed]. Figure 9 The message component 935 described is used for execution.

[0258] Figure 17 A flowchart illustrating a method 1700 for signaling for a system information block according to one or more aspects of this disclosure is shown. Operation of method 1700 may be implemented by a network entity or its components as described herein. For example, operation of method 1700 may be implemented by, as referenced... Figures 1 to 6 as well as Figures 11 to 14 The network entity described is used to perform this function. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described function. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described function.

[0259] At 1705, the method may include: transmitting a set of multiple cores in a search space during a monitoring period, the set of multiple cores including a first core and a second core, wherein the second core is transmitted via second REs located at a predefined time and predefined frequency relative to the first RE associated with the first core, the second core including control messages for the transmission of scheduling messages. The operation of 1705 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1705 may be derived from references... Figure 13 The described repeat manager 1325 is used to execute this.

[0260] At 1710, the method may include: communicating a message to the UE using information indicated by a control message included in the second CORESET. The operation of 1710 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1710 may be provided by reference to [reference needed]. Figure 13 The message manager 1330 described is used to execute this.

[0261] Figure 18 A flowchart illustrating a method 1800 for signaling for a system information block according to one or more aspects of this disclosure is shown. The operation of method 1800 may be implemented by a network entity or its components as described herein. For example, the operation of method 1800 may be implemented by, as referenced... Figures 1 to 6 as well as Figures 11 to 14 The network entity described is used to perform this function. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described function. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described function.

[0262] At 1805, the method may include: transmitting a set of multiple cores in a search space during a monitoring period, the set of multiple cores including a first core and a second core, wherein the second core is transmitted via second REs located at a predefined time and predefined frequency relative to the first RE associated with the first core, the second core including control messages for the transmission of scheduling messages. The operation of 1805 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1805 may be provided by reference to [reference needed]. Figure 13 The described repeat manager 1325 is used to execute this.

[0263] At 1810, the method may include: communicating a message to the UE using information indicated by a control message included in the second CORESET. The operation of 1810 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1810 may be provided by reference to [reference needed]. Figure 13 The message manager 1330 described is used to execute this.

[0264] In 1815, the method may include sending a handover command for the target cell, which indicates that CORESET repetition has been activated. The operation of 1815 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1815 may be provided by reference to [reference needed]. Figure 13 The described handover manager 1335 is used to perform this.

[0265] At 1820, the method may include sending neighboring cell information associated with neighboring cells of the target cell, the neighboring cell information indicating CORESET duplication information for the neighboring cells. The operation at 1820 may be performed according to the examples disclosed herein. In some examples, aspects of the operation at 1820 may be provided by reference to [reference needed]. Figure 13 The described cell manager 1340 is used to execute this.

[0266] The following provides an overview of the various aspects of this disclosure: Aspect 1: A method for wireless communication by a UE, the method comprising: monitoring a search space during a monitoring period to obtain a plurality of cores, the plurality of cores including a first core and a second core; receiving the second core from a network entity via a second real-time equipment (RE) during the monitoring period, the second RE being located at a predefined time and a predefined frequency relative to a first RE associated with the first core, the second core including a control message for the transmission of a scheduling message; and communicating the message to the network entity using information indicated by the control message included in the second core.

[0267] Aspect 2: According to the method of aspect 1, wherein the message includes SIB1 in the PDSCH, the PDSCH being scheduled at least in part based on the plurality of CORESETs, and the SIB1 indicating the repetition of CORESETs of a type specific to one or more search spaces.

[0268] Aspect 3: The method according to aspect 2, the method further comprising: receiving the repetition of the CORESET at least in part based on the SIB1.

[0269] Aspect 4: The method according to any one of Aspects 1 to 3, the method further comprising: detecting a failure to decode the first CORESET via the first RE associated with the first CORESET; and, in response to the failure to decode the first CORESET, monitoring the second CORESET via the second RE during the monitoring period, based at least in part on the hypothesis that CORESET repetition has been activated.

[0270] Aspect 5: The method according to aspect 4, wherein the monitoring of the second CORESET uses blind decoding without prior indication of activation of CORESET repetition.

[0271] Aspect 6: The method according to any one of aspects 1 to 5, the method further comprising: using a combination of the first CORESET and the second CORESET to decode the PDCCH.

[0272] Aspect 7: The method according to any one of Aspects 1 to 4, wherein the second CORESET is indicated by a CRC mask, DMRS scrambling, or coded DCI bit scrambling.

[0273] Aspect 8: The method according to any one of Aspects 1 to 4 and 7, wherein the second CORESET is indicated by the number of the first REs associated with the first CORESET that satisfy a first threshold, by the number of bandwidths or REs associated with the first CORESET that satisfy a second threshold, or by conveying the first CORESET in a specific frequency band.

[0274] Aspect 9: The method according to any one of Aspects 1 to 4 and 7 to 8, the method further comprising: receiving a handover command for a target cell, the handover command indicating activation of CORESET repeat; and receiving neighboring cell information associated with neighboring cells of the target cell, the neighboring cell information indicating CORESET repeat information for the neighboring cells.

[0275] Aspect 10: The method according to any one of Aspects 1 to 9, wherein for the format of the PDCCH scrambled by SI-RNTI in a particular frequency band, one or more bits of the PDCCH associated with the first CORESET are fixed or removed.

[0276] Aspect 11: The method according to any one of Aspects 1 to 10, wherein the DCI associated with the first CORESET indicates the number of time slots used for aggregation of the PDSCH carrying the SIB.

[0277] Aspect 12: The method according to aspect 11, wherein the PDSCH is scheduled via CSS.

[0278] Aspect 13: The method according to any one of aspects 1 to 12, the method further comprising: receiving an SSB, wherein the search space is monitored based at least in part on the monitoring timing occurring within a threshold period following the SSB.

[0279] Aspect 14: A method for wireless communication by a network entity, the method comprising: transmitting a plurality of CORESETs in a search space during a monitoring period, the plurality of CORESETs including a first CORESET and a second CORESET, wherein the second CORESET is transmitted via a second RE located at a predefined time and a predefined frequency relative to a first RE associated with the first CORESET, the second CORESET including a control message for the transmission of a scheduling message; and communicating the message to a UE using information indicated by the control message included in the second CORESET.

[0280] Aspect 15: The method according to aspect 14, wherein the message includes SIB1 in the PDSCH, the PDSCH being scheduled at least in part based on the plurality of CORESETs, and the SIB1 indicating the repetition of CORESETs of a type specific to one or more search spaces.

[0281] Aspect 16: The method according to aspect 15, the method further comprising: sending the repetition of the CORESET at least in part based on the SIB1.

[0282] Aspect 17: The method according to any one of Aspects 14 to 16, wherein the second CORESET is indicated by a CRC mask, DMRS scrambling, or encoded DCI bit scrambling.

[0283] Aspect 18: The method according to any one of Aspects 14 to 17, wherein the second CORESET is indicated by the number of the first REs associated with the first CORESET that satisfy a first threshold, by the number of bandwidths or REs associated with the first CORESET that satisfy a second threshold, or by transmitting the first CORESET in a specific frequency band.

[0284] Aspect 19: The method according to any one of Aspects 14 to 18, the method further comprising: sending a handover command for a target cell, the handover command indicating activation of CORESET repeat; and sending neighboring cell information associated with neighboring cells of the target cell, the neighboring cell information indicating CORESET repeat information for the neighboring cells.

[0285] Aspect 20: A UE for wireless communication, the UE comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the UE to perform a method according to any one of aspects 1 to 13.

[0286] Aspect 21: A UE for wireless communication, the UE including at least one component for performing the method according to any one of aspects 1 to 13.

[0287] Aspect 22: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by one or more processors to perform the method according to any one of aspects 1 to 13.

[0288] Aspect 23: A network entity for wireless communication, the network entity comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the network entity to perform a method according to any one of Aspects 14 to 19.

[0289] Aspect 24: A network entity for wireless communication, the network entity comprising at least one component for performing the method according to any one of aspects 14 to 19.

[0290] Aspect 25: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by one or more processors to perform the method according to any one of aspects 14 to 19.

[0291] It should be noted that the methods described herein describe possible specific implementations. Operations and steps may be rearranged or otherwise modified, and other specific implementations are also possible. Furthermore, aspects from two or more of these methods may be combined.

[0292] While aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for illustrative purposes, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in most of the description, the techniques described herein are also applicable to networks outside of LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described are applicable to a variety of other wireless communication systems, such as Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0293] The information and signals described herein can be represented using any of a variety of different techniques and skills. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0294] The various exemplary blocks and components described herein can be implemented or performed using general-purpose processors, DSPs, ASICs, CPUs, graphics processing units (GPUs), neural processing units (NPUs), FPGAs or other programmable logic devices, discrete gate or transistor logic units, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in alternatives, a processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration). Any function or operation described herein that can be performed by a processor may be performed by multiple processors capable of performing the described functions or operations individually or jointly.

[0295] The functions described herein can be implemented using hardware, software executed by a processor, firmware, or any combination thereof. When implemented using software executed by a processor, the functions can be stored as one or more instructions or code on a computer-readable medium or transmitted using one or more instructions or code on a computer-readable medium. Other examples and specific implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination of these. Features implementing the functions can also be physically located in various locations, including various portions distributed such that the functions are implemented in different physical locations.

[0296] Computer-readable media includes both non-transitory computer storage media and communication media, encompassing any medium that facilitates the transfer of a computer program from one location to another. Non-transitory storage media can be any available medium accessible 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, compressed optical disc (CD) ROM or other optical disc storage devices, magnetic disk storage devices or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code components in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Furthermore, any connection is appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of computer-readable media. As used herein, disks and optical discs include CDs, laser discs, optical discs, digital multifunction discs (DVDs), floppy disks, and Blu-ray discs. Disks can magnetically reproduce data, and optical discs can optically reproduce data using lasers. Combinations of the above are also included within the scope of computer-readable media. Any function or operation described herein that can be performed by memory can be performed by multiple memories capable of performing the described function or operation individually or jointly.

[0297] As used herein, the word "or" in a list of items (e.g., a list of items accompanied by phrases such as "at least one of" or "one or more of") in the claims indicates an inclusive list, such that a list of at least one of, for example, A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an example step described as "based on condition A" could be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on".

[0298] As used herein, including in claims, the article “a” preceding a noun is open-ended and is understood to refer to “at least one” or “one or more” of those nouns. Therefore, the terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. For example, where a claim enumerates “components” performing one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components. Thus, the term “component” having a characteristic or performing a function may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent references to a component introduced with the article “a” using the terms “the” or “the” can refer to any or all of the one or more components. For example, a component introduced with the article “a” can be understood to mean “one or more components,” and subsequent reference to “the component” in a claim can be understood as equivalent to referring to “at least one of the one or more components.” Similarly, subsequent references to a component introduced with the terms “the” or “the” as “one or more components” can refer to any or all of the one or more components. For example, reference to "the one or more components" in the subsequent claims can be understood as equivalent to reference to "at least one of the one or more components".

[0299] The term "determine" encompasses a variety of actions, and therefore, "determine" can include calculation, computation, processing, derivation, investigation, searching (such as by searching in a table, database, or other data structure), ascertainment, etc. Furthermore, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in memory), etc. Moreover, "determine" can include parsing, acquiring, selecting, choosing, creating, and other similar actions.

[0300] In the accompanying drawings, similar components or features may have the same reference numerals. Furthermore, various components of the same type can be distinguished by adding a dash after the reference numeral and a second numeral for differentiation between similar components. If only the first reference numeral is used in the specification, the description applies to any of the similar components having the same first reference numeral, regardless of the second or other subsequent reference numerals.

[0301] The description herein, illustrated with reference to the accompanying drawings, describes an example configuration and does not represent all achievable examples or those within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration," not "preferred" or "advantageous over other examples." The detailed description includes specific details used to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some of the drawings, known structures and devices are shown in block diagram form to avoid obscuring the concept of the described examples.

[0302] The description herein is provided to enable those skilled in the art to implement or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A user equipment (UE), the user equipment (UE) comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to one or more memories and capable of operating individually or jointly to execute the code to enable the UE: During the monitoring period, the search space is monitored to obtain multiple control resource sets (CORESET), including a first CORESET and a second CORESET; During the monitoring period, the second CORESET is received from the network entity via a second resource element (RE), the second resource element (RE) being located at a time and frequency defined relative to a first RE associated with the first CORESET, the second CORESET including control messages for the transmission of scheduling messages; as well as The information indicated by the control message included in the second CORESET is used to communicate the message to the network entity.

2. The UE of claim 1, wherein the message includes System Information Block 1 (SIB1) in a Physical Downlink Shared Channel (PDSCH), the PDSCH being scheduled at least in part based on the plurality of CORESETs, and the SIB1 indicating a repetition of a CORESET of a type specific to one or more search spaces.

3. The UE of claim 2, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: The second CORESET is received at least in part based on the SIB1.

4. The UE of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: Receive system information block 1 (SIB1), wherein SIB1 indicates the time and frequency defined relative to the first RE associated with the first CORESET.

5. The UE of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: A failure to decode the first CORESET via the first RE associated with the first CORESET was detected; and In response to the failure to decode the first CORESET, the second CORESET is monitored via the second RE during the monitoring period, based at least in part on the assumption that CORESET repetition is activated.

6. The UE of claim 5, wherein the monitoring of the second CORESET uses blind decoding without prior indication of activation of CORESET repetition.

7. The UE of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: The combination of the first CORESET and the second CORESET is used to decode the Physical Downlink Control Channel (PDCCH).

8. The UE according to claim 1, wherein: The second CORESET is indicated by a cyclic redundancy check (CRC) mask, demodulation reference signal (DMRS) scrambling, or scrambling of encoded downlink control information (DCI) bits.

9. The UE of claim 1, wherein the second CORESET is indicated by the number of the first REs associated with the first CORESET that satisfy a first threshold, by the bandwidth or number of REs associated with the first CORESET that satisfy a second threshold, or by transmitting the first CORESET in a specific frequency band.

10. The UE of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: Receive a handover command for a target cell, the handover command indicating that CORESET repetition is activated; and Receive neighboring cell information associated with neighboring cells of the target cell, the neighboring cell information indicating CORESET duplicate information for the neighboring cells.

11. The UE of claim 1, wherein for the format of the physical downlink control channel (PDCCH) scrambled by the System Information Radio Network Temporary Identifier (SI-RNTI) in a specific frequency band, one or more bits of the PDCCH associated with the first CORESET are fixed or removed.

12. The UE of claim 1, wherein the downlink control information (DCI) associated with the first CORESET indicates the number of time slots for aggregation of the physical downlink shared channel (PDSCH) carrying the system information block (SIB).

13. The UE of claim 12, wherein the Physical Downlink Shared Channel (PDSCH) is scheduled via a Common Search Space (CSS).

14. The UE of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: Receive synchronization signal block (SSB). The search space is monitored at least in part based on the monitoring timing occurring within a threshold period after the SSB.

15. A network entity, the network entity comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to one or more memories and capable of operating individually or jointly to execute the code to enable the network entity: During the monitoring period, multiple control resource sets (CORESETs) are sent in the search space, including a first CORESET and a second CORESET. The second CORESET is transmitted via a second resource element (RE), which is located at a time and frequency defined relative to a first RE associated with the first CORESET. The second CORESET includes control messages for the transmission of scheduling messages. as well as The information indicated by the control message included in the second CORESET is used to communicate the message to the user equipment (UE).

16. The network entity of claim 15, wherein the message includes System Information Block 1 (SIB1) in a Physical Downlink Shared Channel (PDSCH) that is scheduled at least in part based on the plurality of CORESETs, and the SIB1 indicates a repetition of a CORESET of a type specific to one or more search spaces.

17. The network entity of claim 16, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the network entity to: The second CORESET is transmitted at least in part based on the SIB1.

18. The network entity according to claim 15, wherein: The second CORESET is indicated by a cyclic redundancy check (CRC) mask, demodulation reference signal (DMRS) scrambling, or scrambling of encoded downlink control information (DCI) bits.

19. The network entity of claim 15, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the network entity to: Send a handover command for the target cell, the handover command indicating that CORESET repetition is activated; and Send neighboring cell information associated with neighboring cells of the target cell, the neighboring cell information indicating CORESET duplicate information for the neighboring cells.

20. A method for wireless communication by a user equipment (UE), the method comprising: During the monitoring period, the search space is monitored to obtain multiple control resource sets (CORESET), including a first CORESET and a second CORESET; During the monitoring period, the second CORESET is received from the network entity via a second resource element (RE), the second resource element (RE) being located at a time and frequency defined relative to a first RE associated with the first CORESET, the second CORESET including control messages for the transmission of scheduling messages; as well as The information indicated by the control message included in the second CORESET is used to communicate the message to the network entity.

Images