Network-controlled repeater configuration
Network-controlled repeaters address the limitations of traditional RF repeaters by processing side control information for enhanced network coverage, improving spatial directivity and integration efficiency.
Patent Information
- Application Number
- JP2024541867
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2022-01-12
- Filing Date
- 2023-01-12
- Publication Date
- 2025-01-24
AI Technical Summary
Traditional RF repeaters in wireless communication systems lack the ability to consider performance-enhancing factors such as quasi-static and dynamic downlink or uplink configurations, adaptive transmitter and receiver spatial beamforming, and on-off states, limiting their effectiveness in extending network coverage.
Network-controlled repeaters that receive and process side control information from a base station to perform amplification and forwarding operations more efficiently, utilizing time and space information on the Uu interface for improved spatial directivity and reduced noise amplification, with specific designs for repeater-specific CORESET configurations.
Enhances network coverage flexibility by reducing unnecessary noise amplification, improving spatial directivity, and simplifying network integration, while maintaining cost efficiency.
Smart Images

Figure 2025502225000001_ABST
Abstract
Description
[Technical field]
[0001] Related Applications This application claims priority to U.S. patent application 63 / 298,976, filed January 12, 2022, entitled "Network Controlled Repeater Configuration," the disclosure of which is incorporated by reference in its entirety herein.
[0002] The present disclosure relates to wireless communications, and more particularly to network-controlled repeater configurations. [Background technology]
[0003] A wireless communication system may include one or more network communication devices, such as, for example, base stations, which may be known as eNodeB (eNB), Next Generation NodeB (gNB), or other appropriate technical term. Each network communication device, such as a base station, may support wireless communication for one or more user communication devices, which may be known as user equipment (UE) or other appropriate technical term. A wireless communication system may support wireless communication with one or more user communication devices by utilizing resources of the wireless communication system, such as time resources (e.g., symbols, subslots, slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers). In addition, a wireless communication system may support wireless communication across various radio access technologies (RATs), including third generation (3G) RATs, fourth generation (4G) RATs, fifth generation (5G) RATs, and other suitable 5G and beyond RATs. In some cases, a wireless communication system may be a non-terrestrial based network (NTN) and may support various communication devices for wireless communication in the NTN. For example, NTNs may include network entities on non-ground based vehicles such as satellites, unmanned aerial vehicles (UAVs), and stratospheric platform systems (HAPS), as well as terrestrial network entities such as gateway entities with long-range transmission and reception capabilities.
[0004] Wireless communication coverage is a fundamental aspect of cellular network deployment, and mobile operators rely on different types of network nodes to facilitate full coverage of wireless communication system deployments. Regular, full-stack cell deployment is one option, but it is not always possible or economically viable due to lack of available backhaul. As a result, different types of network nodes are considered by mobile operators to increase the coverage flexibility of their network deployments. For example, integrated access and backhaul (IAB) is a new type of network node that does not require a wired backhaul. Another type of network node is the RF repeater, which simplifies the amplify-and-forward of any signal that the repeater receives. RF repeaters are utilized in 2G, 3G, and 4G systems to supplement the coverage provided by a regular full-stack cell, and Radio Frequency (RF) and Electromagnetic Compatibility (EMC) requirements have been specified for RF repeaters for New Radio (NR), covering both Frequency Range 1 (FR1) and Frequency Range 2 (FR2). Although RF repeaters provide a cost-effective solution to extend network coverage, traditional RF repeaters are limited and are usually implemented simply to perform amplify-and-forward operations. Summary of the Invention [Means for solving the problem]
[0005] The present disclosure relates to methods, apparatus, and systems that allow a network entity, such as a base station, to control repeater configuration. In wireless communication systems, RF repeaters are a cost-effective solution for extending network coverage for New Radio (NR), where repeaters are implemented and utilized to enhance and enhance the coverage flexibility of wireless communication system deployments, as specified for both Frequency Range 1 (FR1) and Frequency Range 2 (FR2). As described in the embodiments of the present disclosure, the network-controlled repeater is an enhancement of the conventional RF repeater, and has the ability to receive and process side control information from the network (e.g., base station, gNB). The side control information allows the network-controlled repeater to perform amplify-and-forward operations more efficiently, facilitating the benefits of mitigating unwanted noise amplification, transmitting and receiving with better spatial directionality, and simplified network integration. The capabilities of network controlled repeaters (RF repeaters) can be enhanced to efficiently extend network coverage in both uplink and downlink communications utilizing side control information from the network due to amplification and forwarding techniques that use time and spatial information on the Uu interface (also called the Uu link).
[0006] Some embodiments of the methods and apparatus described herein further include an apparatus (e.g., a repeater) that receives from a base station a first configuration of a common control search space and a second configuration of the control search space for control information, where the first configuration of the common control search space indicates to the repeater where to place the second configuration of the control search space. A controller of the repeater can decode the control information from the second configuration of the control search space as repeater downlink control information (DCI), and then the controller can apply the control information to a forwarding link between the base station and the user equipment.
[0007] In some embodiments of the methods and apparatus described herein, a repeater common control resource set (CORESET) carries repeater DCI placed in a common control search space of a first configuration, the control search space of a second configuration is a dedicated search space, and a repeater dedicated CORESET carries repeater dedicated DCI placed in the dedicated search space, and the repeater common CORESET carries repeater DCI indicating how to decode the second configuration of the control search space.
[0008] Some embodiments of the methods and apparatus described herein may further include an apparatus (e.g., base station, gNB) that transmits to a repeater. The base station transmits a first configuration of a common control search space to the repeater and transmits a second configuration of a control search space for control information to the repeater. The first configuration of the common control search space indicates to the repeater where to place the second configuration of the control search space, and decodes the control information from the second configuration of the control search space as a repeater DCI usable to control a forwarding link between the apparatus and the user equipment.
[0009] Various aspects of the present disclosure for a network-controlled repeater configuration will now be described with reference to the following drawings, in which like numbers may be used to reference like features or components shown in the drawings. [Brief description of the drawings]
[0010] [Figure 1] FIG. 1 illustrates an example of a wireless communication system supporting network-controlled repeater configuration, according to an aspect of the present disclosure. [Diagram 2] FIG. 1 illustrates an example of a system that supports network-controlled repeater configuration and may use a wireless communication system, according to an aspect of the disclosure. [Diagram 3] FIG. 1 illustrates an example of a repeater common CORESET location that supports network-controlled repeater configuration, according to an aspect of the present disclosure. [Figure 4]A diagram illustrating an example of repeater CORESET periodicity and repeater-specific CORESET configuration indication supporting network-controlled repeater configuration according to an aspect of the present disclosure. [Diagram 5] FIG. 13 illustrates an example of a time information indication to support network-controlled repeater configuration, according to an aspect of the present disclosure. [Figure 6] FIG. 2 illustrates an example block diagram of components of a device (e.g., a repeater) that supports network-controlled repeater configuration, according to an aspect of the disclosure. [Figure 7] FIG. 1 illustrates an example block diagram of components of a device (e.g., a base station) that supports network-controlled repeater configuration, according to an aspect of the disclosure. [Figure 8] FIG. 1 illustrates a flowchart of a method for supporting network-controlled repeater configuration according to an aspect of the disclosure. [Figure 9] FIG. 1 illustrates a flowchart of a method for supporting network-controlled repeater configuration according to an aspect of the disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0011] An embodiment of network-controlled repeater configuration is described in connection with repeater configuration of RF repeaters controlled by a network entity such as a base station (e.g., gNB). In wireless communication systems, RF repeaters are a cost-effective solution for extending network coverage for New Radio (NR), where repeaters are specified for both Frequency Range 1 (FR1) and Frequency Range 2 (FR2), and are implemented and utilized to enhance and enhance the coverage flexibility of wireless communication system deployments. Although RF repeaters provide a cost-effective solution for extending network coverage, conventional RF repeaters are limited and typically implemented to simply perform amplify-and-forward operations without the ability to consider various factors that may enhance performance. These factors may include information about quasi-static and / or dynamic downlink or uplink configurations, adaptive transmitter and / or receiver spatial beamforming, on-off states, and other performance enhancing factors.
[0012] As described in the embodiments of the present disclosure, the network-controlled repeater is an enhancement of the conventional RF repeater, and has the capability to receive and process side control information from the network (e.g., base station, gNB). The side control information allows the network-controlled repeater to perform amplify-and-forward operations more efficiently, facilitating the benefits of mitigating unwanted noise amplification, transmitting and receiving with better spatial directivity, and simplified network integration. The capabilities of the network-controlled repeater (RF repeater) can be enhanced to efficiently extend the network coverage in both uplink and downlink communications utilizing side control information from the network for amplify-and-forward techniques that use time and space information on the Uu interface (also called Uu link). The side control information can include time division multiplexing (TDD) switching, timing information, power control, as well as common and UE-specific spatial information for beamforming.
[0013] In the described technology aspect, the repeater controller is utilized as a new type of UE device with limited UE capabilities to decode some Uu link channels to control the repeater using the Uu link. The repeater controller can detect the synchronization signal block (SSB) to synchronize to the network, decode the master information block (MIB) information, the system information block (SIB) information, and decode the physical downlink control channel (PDCCH) that carries the side control information to the repeater. Given that cost efficiency is an important consideration, the repeater is expected to be equipped with a low-complexity receiver to decode the side control information. Therefore, it is not expected to decode the UE-specific control resource set (CORESET), which requires blind search, and has the cell radio network temporary identifier (C-RNTI) and other configurations for each UE.
[0014] Therefore, controller configuration enhancements and / or repeater-specific CORESET designs may be implemented on the PDCCH framework to carry side control information from the base station to the repeater. Furthermore, by utilizing a portion of the Uu interface to control the repeater, the controller of the repeater can decode the control information with low complexity based in part on some modifications of the framework of the control channel on the Uu link. In the disclosed aspect, a repeater-specific CORESET design is implemented that includes corresponding downlink control information (DCI) for controlling the repeater. The described techniques for network-controlled repeater configuration include a new design of the search space and corresponding core set of the repeater downlink control channel, a repeater-specific DCI for carrying side control information to each repeater, a common DCI for carrying initial configuration information to all repeaters in the network for decoding the repeater-specific DCI, and the configuration of the repeater control search space of the SIB.
[0015] Controlling the repeater configuration by the network (e.g., base station, gNB) allows for various scenarios and assumptions for NR network-controlled repeaters. For example, a network-controlled repeater is an in-band RF repeater used for network coverage extension over multiple bands (e.g., FR1 and FR2 bands), where FR2 deployment may be prioritized for both outdoor and O2I scenarios. The techniques described for network-controlled repeaters apply to single-hop fixed network-controlled repeaters, where the network-controlled repeater is transparent to the UE, and the network-controlled repeater can simultaneously maintain a gNB repeater link and a repeater-UE link. Cost efficiency, related to both the cost of transceivers and the cost of efficient deployment, is also an important consideration for network-controlled repeaters.
[0016] Other considerations for network-controlled repeaters include identifying what side control information is required for the network-controlled repeater, including maximum transmit power assumptions. For example, the side control information may include beamforming information, timing information for aligning the transmit and / or receive boundaries of the network-controlled repeater, information regarding uplink-downlink (UL-DL TDD) configuration, on-off information for efficient interference management and improved energy efficiency, and power control information for efficient interference management. Another consideration, and a focus of this disclosure, is identifying Layer 1 and Layer 2 (L1 / L2) signaling, including its configuration, for carrying the side control information. Other aspects of the network-controlled repeater include identification and authentication of the network-controlled repeater (e.g., with respect to RAN2, RAN3, etc.), which may require coordination with SA3.
[0017] Aspects of the present disclosure are described in the context of a wireless communication system. Aspects of the present disclosure are further illustrated and described with reference to device diagrams and flow charts relating to network-controlled repeater configurations.
[0018] FIG. 1 illustrates an example of a wireless communication system 100 supporting a network-controlled repeater configuration according to aspects of the disclosure. The wireless communication system 100 may include one or more base stations 102, one or more UEs 104, a core network 106, and one or more non-terrestrial based networks (NTS) 108, such as satellite access nodes. The wireless communication system 100 may support various radio access technologies (RATs). In some embodiments, the wireless communication system 100 may be a 4G network, such as an LTE network or an LTE-A network. In some other embodiments, the wireless communication system 100 may be a 5G network, such as an NR network. In other embodiments, the wireless communication system 100 may be a combination of a 4G network and a 5G network. The wireless communication system 100 may support a 5G or later RAT. In addition, the wireless communication system 100 may support technologies such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA).
[0019] One or more base stations 102 may be distributed across a geographic region to form a wireless communication system 100. One or more of the base stations 102 described herein may be or may include or be referred to as a base transceiver station, an access point, a NodeB, an eNB, a gNB, or other suitable technology. The base stations 102 and the UEs 104 may communicate over a communication link 110, which may be a wireless and wired connection. For example, the base stations 102 and the UEs 104 may perform wireless communication over an NR Uu interface. As further shown and described with reference to FIG. 2, a repeater node is implemented to extend or enhance the network coverage of the communication link 110 between the base stations 102 and the UEs 104, where the base stations 102 communicate with the repeaters, which also communicate with the UEs 104 over the communication link.
[0020] The one or more NTSs 108 described herein may be or include any type of TRP (some of which may be onboard geosynchronous and / or geosynchronous (GEO) satellites), MEO satellites, LEO satellites, HAPS, UAVs, aircraft, or other vehicles such as those moving through the Earth's atmosphere and orbiting in space. Any entity referred to as a non-terrestrial station (NTS) in this disclosure may be referred to as a satellite, satellite access node, NTN node, NG-RAN node, NT-TRP, NTN TP, NTN RP, and similar types of entities. The NTS 108 and the UE 104 may communicate via a communication link 112, which may be a wireless connection via a transmit beam and / or a receive beam.
[0021] The base station 102 and / or NTS 108 provide a geographic coverage area 114, and the base station 102 and / or NTS 108 support services (e.g., voice, video, packet data, messaging, broadcast, etc.) for one or more UEs 104 within the geographic coverage area. For example, the base station 102 and UEs 104 may support wireless communication of signals related to the services (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or more radio access technologies. Similarly, the NTS 108 and UEs 104 may support wireless communication of signals related to the services (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or more radio access technologies. In some embodiments, the base station 102 may be mobile, such as when implemented as a gNB onboard a satellite associated with an NTN. In some embodiments, different geographic coverage areas 114 associated with the same or different radio access technologies may overlap, and different geographic coverage areas 114 may be associated with different base stations 102 and / or different NTSs 108. The information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
[0022] One or more UEs 104 may be distributed throughout a geographic or coverage area 114 of the wireless communication system 100. The UEs 104 may include or be referred to as mobile devices, wireless devices, remote devices, handheld devices, or subscriber devices, or other suitable technologies. In some embodiments, the UEs 104 may be referred to as units, stations, terminals, or clients, among other examples. Additionally or alternatively, the UEs 104 may be referred to as Internet-of-Things (IoT) devices, Internet-of-Everything (IoE) devices, or machine-type communication (MTC) devices, among other examples. In some embodiments, the UEs 104 may be fixed in the wireless communication system 100, such as a very small aperture terminal (VSAT), and may be connected to one or more other network nodes serving other UEs. In other embodiments, the UEs 104 may be mobile in the wireless communication system 100, such as an earth station in motion (ESIM).
[0023] One or more UEs 104 may be devices of different forms or capabilities. The UE 104 may communicate with various types of devices, such as base stations 102, other UEs 104, NTSs 108, or network equipment (e.g., a core network 106, relay devices, gateway devices, integrated access and backhaul (IAB) nodes, location servers implementing a location management function (LMF), or other network equipment). Additionally or alternatively, the UE 104 may support communication with other base stations 102 or UEs 104 that may act as relays for the wireless communication system 100.
[0024] The UE 104 may support direct wireless communication with other UEs 104 via the communication link 116. For example, the UE 104 may support direct wireless communication with another UE 104 via a device-to-device (D2D) communication link. In some embodiments, the communication link 116 may be referred to as a sidelink, such as in a vehicle-to-vehicle (V2V) deployment, a vehicle-to-exchange (V2X) deployment, or a cellular V2X deployment. For example, the UE 104 may support direct wireless communication with other UEs 104 via a PC5 interface.
[0025] A base station 102 may support communication with the core network 106, or with another base station 102, or both. For example, a base station 102 may interface to the core network 106 via one or more backhaul links 118 (e.g., via an S1, N2, or other network interface). The base stations 102 may communicate with each other via the backhaul links 118 (e.g., via an X2, Xn, or another network interface). In some embodiments, the base stations 102 may communicate with each other directly (e.g., between the base stations 102). In some other embodiments, the base stations 102 and / or the NTS 108 may communicate with each other indirectly (e.g., via the core network 106). In some embodiments, one or more base stations 102 may include subcomponents such as an access network entity, which may be an example of an access node controller (ANC). The ANC may communicate with one or more UEs 104 via one or more other access network transmission entities, which may be referred to as radio heads, smart radio heads, gateways, TRPs, and other network nodes and / or entities.
[0026] The core network 106 may support user authentication, access authentication, tracking, connectivity, and other access, routing, or mobility functions. The core network 106 may be an evolved packet core (EPC) or 5G Core (5GC) and may include a control plane entity (Mobility Management Entity (MME), Access and Mobility Management Function (AMF)) that manages access and mobility, and a user plane that routes packets or interconnects with external networks (e.g., a Serving Gateway (S-GW), a Packet Data Network (PDN) Gateway (P-GW), or a User Plane Function (UPF)). In some embodiments, the control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management for one or more UEs 104 served by one or more base stations 102 associated with the core network 106.
[0027] In at least one embodiment, one or more of the UE 104, the base station 102, and / or the one or more repeaters are operable to implement various aspects of network-controlled repeater configuration as described herein. For example, utilizing the described techniques, the base station 102 is operable to control the configuration of repeaters in the wireless communication system 100.
[0028] FIG. 2 illustrates an example of a system 200 supporting network-controlled repeater configuration according to an aspect of the disclosure. The system 200 may use and / or be implemented with the wireless communication system 100. The system 200 includes a base station 102 that communicates with a repeater 202 via a communication link 204, which further communicates with a UE 104 via a communication link 206. For example, the base station 102, the repeater 202, and the UE 104 may perform wireless communication over a forwarding link 208 over a Uu interface. Additionally, the base station 102 communicates a repeater search space configuration and a repeater downlink control information (DCI) to a repeater controller 210 via the communication link 204.
[0029] In the described technology aspect, the controller 210 of the repeater 202 can be utilized as a new type of UE device with limited UE capabilities to decode some Uu link channels to control the repeater using the Uu link. The controller 210 of the repeater 202 can detect the synchronization signal block (SSB) for synchronizing to the network, decode the master information block (MIB) information, the system information block (SIB) information, and decode the physical downlink control channel (PDCCH) that carries the side control information to the repeater. Given that cost efficiency is an important consideration, the repeater is expected to be equipped with a low-complexity receiver for decoding the side control information. Therefore, it is not expected to decode the UE-specific control resource set (CORESET) that requires blind search and has the cell radio network temporary identifier (C-RNTI) and other configurations for each UE.
[0030] Accordingly, controller configuration enhancements and / or repeater-specific CORESET designs may be implemented on the PDCCH framework to carry side control information from the base station 102 to the repeater 202. Furthermore, by utilizing a portion of the Uu interface to control the repeater, the controller 210 of the repeater 202 can decode the control information with low complexity based in part on some modifications of the control channel framework for the Uu link. In the disclosed aspect, a repeater-specific CORESET design with corresponding downlink control information (DCI) for controlling the repeater is implemented. The described techniques for network-controlled repeater configuration include a new design of the search space and corresponding core set of the repeater downlink control channel, a repeater-specific DCI for carrying side control information to each repeater, a common DCI for carrying initial configuration information to all repeaters in the network for decoding the repeater-specific DCI, and the configuration of the repeater control search space of the SIB. The repeater can decode the SSB, synchronize to the network, and decode CORESET0 to receive the basic or initial network configuration, which may include carrier frequency, initial bandwidth (BWP), SCS subcarrier spacing, frame number, cell ID, etc.
[0031] The UE 104 is typically implemented with procedures for receiving control information and determining or decoding a physical downlink control channel (PDCCH) (e.g., [TS 38.213]). If the UE is configured with a secondary cell group (SCG), the UE can apply the procedures for both the master cell group (MCG) and the SCG, except for PDCCH monitoring in the Type 0 / 0A / 2-PDCCH common cell space (CSS) set, for which the UE does not need to apply the procedures for the SCG. When the procedures are applied for the MCG, the terms "secondary cell", "multiple secondary cells", "serving cell", and "multiple serving cells" refer to a secondary cell, multiple secondary cells, serving cell, and multiple serving cells belonging to the MCG, respectively. When the procedures are applied for the SCG, the terms "secondary cell", "multiple secondary cells", "serving cell", and "multiple serving cells" refer to a secondary cell, multiple secondary cells (not including a PSCell), serving cell, and multiple serving cells belonging to the SCG, respectively. The term "primary cell" refers to a PSCell of the SCG.
[0032] The UE monitors a set of PDCCH candidates of one or more CORESETs on an active downlink bandwidth portion (DL BWP) based on each activated serving cell being configured for PDCCH monitoring according to a corresponding search space set, and monitoring means decoding each PDCCH candidate according to the monitored DCI format. If the UE is provided with monitoringCapabilityConfig of the serving cell, the UE gets an instruction to monitor the PDCCH on the serving cell for the maximum number of PDCCH candidates and non-overlapping control channel elements (CCEs). For example, per slot (Tables 10.1-2 and 10.1 3) for monitoringCapabilityConfig = r15monitoringcapability, and per span (Tables 10.1 2A and 10.1-3A) for monitoringCapabilityConfig = r16monitoringcapability. If the UE is not provided with monitoringCapabilityConfig, the UE monitors the PDCCH of the serving cell for the maximum number of PDCCH candidates and non-overlapping CCEs per slot.
[0033] The UE indicates the capability to monitor the PDCCH according to one or more of the combinations (X, Y)=(2, 2), (4, 3), and (7, 3) for each SCS configuration for μ=0 and μ=1. A span is the number of consecutive symbols in a slot for which the UE is configured to monitor the PDCCH, with each PDCCH monitoring opportunity being within one span. When the UE monitors the PDCCH of a cell according to the combination (X, Y), the UE supports PDCCH monitoring opportunities in any symbol of the slot with a minimum time separation in symbols between the first symbols of two consecutive spans, including the access slot. A span starts with the first symbol where the PDCCH monitoring opportunity begins and ends with the last symbol where the PDCCH monitoring opportunity ends, with the number of symbols in the span being at most Y.
[0034] If the UE indicates an ability to monitor a PDCCH according to multiple (X, Y) combinations, and a configuration of a search space set for the UE for PDCCH monitoring of a cell results in an interval of every two consecutive PDCCH monitoring spans greater than or equal to the value of X for one or more of the multiple combinations (X, Y), the UE:
number
[0035] The UE capability to monitor the PDCCH per slot or span of the active DL BWP of the serving cell is defined by the maximum number of PDCCH candidates and non-overlapping CCEs that the UE can monitor per slot or span of the active DL BWP of the serving cell, respectively. For monitoring of PDCCH candidates by the UE, if the UE receives ssb-PositionsInBurst in System Information Block 1 (SIB1), does not receive ssb-PositionsInBurst in ServingCellConfigCommon for the serving cell, does not monitor PDCCH candidates in the Type0-PDCCH CSS set, and at least one resource element (RE) for the PDCCH candidate overlaps with at least one RE of a synchronization signal / physical broadcast channel (SS / PBCH) block corresponding to the candidate SS / PBCH block index provided by ssb-PositionsInBurst in SIB1, the UE does not need to monitor the PDCCH candidates. Regarding monitoring of PDCCH candidates by the UE, if the UE receives ssb-PositionsInBurst in ServingCellConfigCommon for the serving cell, does not monitor PDCCH candidates in the Type0-PDCCH CSS set, and at least one RE for the PDCCH candidate overlaps with at least one RE of the candidate SS / PBCH block corresponding to the SS / PBCH block index provided by ssb-PositionsInBurst in ServingCellConfigCommon, the UE does not need to monitor the PDCCH candidates.
[0036] If the UE monitors PDCCH candidates for the Type0-PDCCH CSS set of the serving cell according to a procedure (e.g., described in Section 13), the UE may assume that there are no SS / PBCH blocks transmitted in the REs used to monitor the PDCCH candidates of the serving cell. If at least one RE of the PDCCH candidates for the UE of the serving cell overlaps with at least one RE of the LTE-CRS-ToMatchAround or at least one RE of the LTE-CRS-PatternList, the UE does not need to monitor the PDCCH candidates. If availableRB-SetsPerCell is provided to the UE, the UE does not need to monitor the PDCCH candidates that overlap any RBs of the RB sets indicated as not receivable by the available RB set indicator field of DCI format 2_0 (e.g., described in Section 11.1.1). If the UE does not obtain an available RB set indicator for a symbol, the UE monitors the PDCCH candidates of all RB sets of the symbol.
[0037] The UE is not provided with a coresetPoolIndex or is provided with a coresetPoolIndex with a single value for all CORESETs of all DL BWPs of each scheduling cell from the first set of serving cells.
number
number
number
[0038] If the UE indicates carrier aggregation capability for more than four serving cells in UE-NR-Capability and the UE has not been provided with monitoringCapabilityConfig for any downlink cell or the UE has been provided with monitoringCapabilityConfig = r15monitoringcapability for all downlink cells for which the UE monitors PDCCH, the UE shall include an indication for the maximum number of PDCCH candidates in the UE-NR-Capability. For the maximum number of non-overlapping CCEs the UE can monitor per slot when the UE is configured for carrier aggregation operation over more than four cells. If the UE is not configured for NR-DC operation, the UE shall:
number
number
number
number
[0039] If the UE is configured for NR-DC operation, the UE shall
number
number
number
number
number
[0040] The UE 104 is also implemented with a procedure for determining a PDCCH allocation. The set of PDCCH candidates that the UE monitors is defined in terms of a PDCCH search space set. The search space set may be a common search space (CSS) or a UE-specific search space (USS) set. The UE monitors PDCCH candidates in one or more of the following search space sets: a Type0-PDCCH CSS set configured by pdcch-ConfigSIB1 of MIB, or by searchSpaceSIB1 of PDCCH-ConfigCommon, or by searchSpaceZero of PDCCH-ConfigCommon for DCI formats with cyclic redundancy check (CRC) scrambled by system information radio network temporary identifier (SI-RNTI) on the primary cell of the MCG; a Type0A-PDCCH CSS set configured by searchSpaceOtherSystemInformation of PDCCH-ConfigCommon for DCI formats with CRC scrambled by SI-RNTI on the primary cell of the MCG. A Type1-PDCCH CSS set configured by the ra-SearchSpace in PDCCH-ConfigCommon for DCI formats with CRC scrambled by RA-RNTI, MsgB-RNTI, or TC-RNTI on the primary cell. A Type2-PDCCH CSS set configured by the pagingSearchSpace in PDCCH-ConfigCommon for DCI formats with CRC scrambled by P-RNTI on the primary cell of the MCG.Type3-PDCCH CSS set configured by SearchSpace in PDCCH-Config with searchSpaceType = common for DCI formats with CRC scrambled by INT-RNTI, SFI-RNTI, TPC-PUSCH^RNTI, TPC-PUCCH-RNTI, TPC-SRS-RNTI, or CI-RNTI, and for the primary cell only, USS set configured by SearchSpace in PDCCH-Config with searchSpaceType = ue-Specific for DCI formats with CRC scrambled by C-RNTI, MCS-C-RNTI, SP-CSI-RNTI, CS-RNTI, SL-RNTI, SL-CS-RNTI, or SL quasi-static scheduling V-RNTI.
[0041] For DL BWP, if the UE is not provided with searchSpaceSIB1 for the Type0-PDCCH CSS configured by PDCCH-ConfigCommon, the UE does not monitor PDCCH candidates for the Type0-PDCCH CSS set on the DL BWP. The Type0-PDCCH CSS set is defined by the CCE aggregation level and the number of PDCCH candidates per CCE aggregation level (Table 10.1-1). If the active DL BWP and the initial DL BWP have the same SCS and the same CP length, and the active DL BWP contains all RBs of the CORESET with index 0 or the active DL BWP is the initial DL BWP, the configured CORESET for the Type0-PDCCH CSS set has CORESET index 0 and the Type0-PDCCH CSS set has search space set index 0. [Table 1]
[0042] For DL BWP, if searchSpaceOtherSystemInformation for the Type0A-PDCCH CSS set is not provided to the UE, the UE does not monitor the PDCCH for the Type0A-PDCCH CSS set of the DL BWP. The CCE aggregation levels and the number of PDCCH candidates per CCE aggregation level for the Type0A-PDCCH CSS set are given (Table 10.1-1). For DL BWP, if ra-SearchSpace for the Type1-PDCCH CSS set is not provided to the UE, the UE does not monitor the PDCCH for the Type1-PDCCH CSS set of the DL BWP. If a Type3-PDCCH CSS set or a USS set is not provided to the UE and the UE receives a C-RNTI and a Type1-PDCCH CSS set is provided, the UE monitors the PDCCH candidates of DCI format 0_0 and DCI format 1_0 with CRC scrambled by the C-RNTI of the Type1-PDCCH CSS set.
[0043] If a pagingSearchSpace for the Type2-PDCCH CSS set has not been provisioned to the UE, the UE shall not monitor the PDCCH for the Type2-PDCCH CSS set in DL BWP, given the CCE aggregation level and the number of PDCCH candidates per CCE aggregation level for the Type2-PDCCH CSS set (Table 10.1-1). If a zero-valued searchSpaceID in PDCCH-ConfigCommon for the Type0 / 0A / 2-PDCCH CSS set has been provisioned to the UE, the UE shall determine the monitoring opportunities for the PDCCH candidates in the Type0 / 0A / 2-PDCCH CSS set (e.g., as described in clause 13) and the UE shall be provided with a C-RNTI. The UE monitors PDCCH candidates only at monitoring occasions associated with SS / PBCH blocks, which are determined by the most recent MAC CE activation command indicating a TCI state for an active BWP containing a CORESET with index 0 (e.g., as described in [6, TS 38.214]), including a CSI-RS that is quasi-co-located with the SS / PBCH block, or a random access procedure not initiated by a PDCCH command triggering a contention-free random access procedure.
[0044] If the UE monitors PDCCH candidates of a DCI format with CRC scrambled by C-RNTI and a non-zero value of searchSpaceID in PDCCH-ConfigCommon for a Type0 / 0A / 2-PDCCH CSS set is provided to the UE, the UE may determine monitoring opportunities for PDCCH candidates of the Type0 / 0A / 2-PDCCH CSS set based on the search space set associated with the value of searchSpaceID. The UE may assume that the DM-RS antenna ports associated with PDCCH reception of the CORESET configured by pdcch-ConfigSIB1 of the MIB, the DM-RS antenna ports associated with the corresponding PDSCH reception, and the corresponding SS / PBCH blocks are quasi-co-located with respect to the average gain quasi-co-location "typeA" and "typeD" properties when available (e.g., [6, TS 38.214]) if the UE is not provided with a TCI state indicating quasi-co-location information of the DM-RS antenna ports for PDCCH reception of the CORESET. The values for DM-RS scrambling sequence initialization are the cell ID and SCS provided by subCarrierSpacingCommon of the MIB.
[0045] For single cell operation or operation with carrier aggregation in the same frequency band, if the DM-RS for monitoring a PDCCH in the Type1-PDCCH CSS set is not configured with the same qcl-Type set for the "typeD" property (e.g., [6, TS 38.214]) with the DM RS for monitoring a PDCCH in the Type0 / 0A / 2 / 3-PDCCH CSS set or USS set, and if the PDCCH or an associated PDSCH overlaps with the PDCCH in at least one symbol, the UE is not expected to monitor the PDCCH in the Type0 / 0A / 2 / 3-PDCCH CSS set or USS set, and the UE shall monitor in the Type1-PDCCH CSS set or with the associated PDSCH.
[0046] If one or more search space sets have been provided to the UE by searchSpaceZero, searchSpaceSIB1, searchSpaceOtherSystemInformation, pagingSearchSpace, ra-SearchSpace, and the corresponding one or more of C-RNTI, MCS-C-RNTI, or CS-RNTI, the UE monitors PDCCH candidates of DCI format 0_0 or DCI format 1_0 with CRC scrambled by C-RNTI, MCS-C-RNTI, or CS-RNTI in one or more search space sets for slots in which the UE monitors PDCCH candidates of at least DCI format 0_0 or DCI format 1_0 with CRC scrambled by SI-RNTI, RA-RNTI, MsgB-RNTI, or P-RNTI.
[0047] If the UE has been provided with one or more search space sets by searchSpaceZero, searchSpaceSIB1, searchSpaceOtherSystemInformation, pagingSearchSpace, ra-SearchSpace, or corresponding one or more of the CSSs configured by PDCCH-Config and SI-RNTI, P-RNTI, RA-RNTI, MsgB-RNTI, SFI-RNTI, INT-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, or TPC-SRS-RNTI, for an RNTI from any of these RNTIs, the UE is not expected to process information from two or more DCI formats with CRC scrambled with the per-slot RNTI.
[0048] In an aspect of the present disclosure, with respect to a repeater common or initial search space, the repeater 202 (e.g., a network node) is configured or pre-configured with a repeater search space to decode repeater control information. The repeater is equipped with a transceiver with limited UE capabilities, synchronizes to a network (e.g., a base station 102), and decodes a portion of the Uu link physical channel. The network configures (pre-configures) the repeater with a configuration of two search spaces, one common or initial search space and the other repeater specific search space. The repeater 202 performs Rel17 UE procedures for initial access, detects SSB, synchronizes to the network, decodes the physical broadcast channel (PBCH), and reads MIB information.
[0049] The repeaters 202 of the wireless communication system 100 may be configured (pre-configured) with a repeater common CORESET (CREP-CORESET) (e.g., with a unique controlResourceSetId) and placed at predefined locations of a time and frequency grid with a known aggregation level (AL) for decoding a repeater common downlink control information (DCI) format (e.g., DCI format 2_7), whose cyclic redundancy check (CRC) is scrambled with a pre-known RNTI / ID (e.g., CREP-RNTI) defined by the network operator. This allows fast DCI decoding and low latency application of the control configuration on the forwarding link with known rate matching information common to all repeaters of the network to avoid blind searches of repeaters.
[0050] 3 illustrates an example 300 of a repeater common CORESET location supporting network-controlled repeater configuration according to an aspect of the disclosure. This example illustrates the location of a common search space to be monitored by repeaters of a network after detecting an SSB and synchronizing to the network. Mapping the CORESET REs close to the SSB (e.g., within the initial BWP) and using the same spatial filter with a beam corresponding to the detected SSB beam is beneficial because the estimated channel on the PBCH can be reused to equalize the subcarriers of the CORESET to hold the resource elements (REs) of the control information with no or less Modulated Reference Signal (DMRS) overhead.
[0051] In one embodiment, no modulation reference signal (DMRS) is transmitted in the repeater common CORESET, and quasi-co-location (QCL) for the PBCH DMRS is assumed, and channel information obtained from the PBCH DMRS as the location of the common CORESET is close to the SSB and in the SSB frequency band. In another embodiment, the predefined DMRS is distributed at predefined RE locations for accurate channel estimation. Alternatively, the periodicity of the common CORESET is more frequent than the SSB periodicity, and multiple common CORESET opportunities occur between SSB bursts.
[0052] The repeater common DCI of the common CORESET carries initial or common control information for the repeaters of the network, including the location and size of the repeater-only CORESET, the periodicity of the repeater-only CORESET, DMRS information, QCL assumptions to the corresponding PBCH DMRS or other RS, the aggregation level (AL) of the repeater-only CORESET, the SCS of the repeater CORESET, BWP, etc. Repeaters are expected to be deployed at fixed locations relative to the base station, and the links carrying the control information are expected to be constant or quasi-constant with little time variation. However, flexible configuration of repeater-only CORESETs with different aggregation levels, periodicities, etc. can provide flexibility in repeater CORESET detection performance and may depend on the network requirements and deployment scenarios.
[0053] As an example, Table T1 shows some of the information carried by the repeater common DCI (DCI format 2_7). [Table 2]
[0054] Some bits (e.g., 2 bits shown in the table above) may be signaled to indicate the DMRS of the repeater dedicated CORESET (e.g., 00 indicates no DMRS, and the channel is acquired based on the QCL assumption to the previous monitoring slot (SSB or common CORESET)). Other values indicate a predefined configuration of the DMRS of the repeater CORESET. In another embodiment, the DMRS of the dedicated CORESET follows the configuration shown in CORESET0 and SSB. The number of RBs and symbols used for the common CORESET depends on the predefined AL, modulation and coding, rate matching information, etc. For example, to carry the above-mentioned information bits with quadrature phase shift keying (QPSK) modulation and 1 / 3 code rate without DMRS, 4 RBs are needed, which may be transmitted on one or more symbols. In one embodiment, the common DCI carries information about the on / off function to be used by the repeater according to its ID, and each repeater applies an on / off pattern according to the combination of the indicated on / off function and the repeater's identifier.
[0055] In one example, the repeater-common DCI may also indicate one or more of the following: a time interval during which the DCI is applicable (e.g., the time interval may be indicated as multiple time units, where the time units are slots, repeater-common DCI opportunities, etc.); a discontinuous reception (DRX) configuration, where the repeater only monitors the repeater-only DCI within a determined active time of a DRX cycle, where the DRX cycle and the corresponding active time of the DRX cycle are determined based on the DRX configuration indication indicated in the repeater-common DCI; and a repeater group index. The repeater-common DCI has up to "N" repeater-only indications, where each repeater-only indication has one of a set of indications corresponding to a repeater group index.
[0056] The location of the repeater dedicated CORESET in frequency and time is determined from the indication of the first slot, first symbol of the slot, and first RB of the slot. Each repeater CCE (associated with a dedicated CORESET) starts from an offset associated with the indicated AL and predefined REP-RNTI combination, and each repeater monitors the DCI starting with the corresponding RB (similar CCE index determination rules described in TS38.213 may be reused). An exemplary formula is provided for CCE index calculation for PDCCH candidates with search space aggregation level "L". For a search space set s associated with CORESETp, the carrier indicator field value n CI For the active DL BWP of the serving cell corresponding to
number
number
number
[0057] N CCE,p is the number of bits in CORESETp from 0 to N CCE,p-1 n CI is the carrier indicator field value if the UE is configured with the carrier indicator field according to the CrossCarrierSchedulingConfig of the serving cell for which the PDCCH is monitored, otherwise, n, including the case of any CSS CI =0.
number
number
number
number
[0058] Alternatively, if the repeater is equipped with a transceiver capable of decoding SSB, PDCCH, and PDSCH, the common or initial control information and / or configuration may be signaled using a SIB. After detecting the SSB, CORESET0, the repeater decodes the SIB carried by the PDSCH, in which the repeater common configuration for decoding the repeater specific CORESET is signaled to the repeater. Below is an example of the repeater configuration carried by the SIB as part of the PDCCH-ConfigCommon: [Table 3]
[0059] Here, the repeater search space configuration may carry information for decoding the repeater-only CORESET, such as in the following example: [Table 4]
[0060] In an aspect of the present disclosure, with respect to the repeater-only search space, a repeater 202 (e.g., a network node) is configured (pre-configured) with a repeater search space for decoding repeater control information. The repeater is equipped with a transceiver with limited UE capabilities for decoding SSB and PDCCH. The repeater is configured (pre-configured) with two search spaces, one common or initial search space and the other repeater-only search space. The repeater performs Rel17 UE procedures for initial access, detects SSB, synchronizes to the network, decodes PBCH, reads MIB information to decode CORESET0, and decodes the initial or common repeater CORESET. Repeaters in the network are configured (pre-configured) with the initial CORESET and / or the repeater-only CORESET (REP-CORESET) via SIB (e.g., with a unique controlResourceSetId). The DCI format (e.g. DCI format 2_7A) has a CRC scrambled with a pre-known RNTI / ID (REP-RNTI) defined by the network operator for each deployed repeater. The location of the CORESET, the search space configuration and the periodicity of the repeater-dedicated CORESET are signaled by the network via the repeater initial CORESET and / or via the SIB. In another embodiment, the periodicity of the repeater-dedicated CORESET follows a UE-specific periodicity, for example according to the parameter monitoringSlotPeriodicityAndOffset.
[0061] 4 illustrates an example 400 of repeater CORESET periodicity and repeater-only CORESET configuration indication to support network-controlled repeater configuration according to an embodiment of the present disclosure. This example shows the location of the repeater-only search space to be decoded by each repeater after detecting the SSB, synchronizing to the network, and receiving the repeater initial or common search space configuration. The repeater estimates the channel of the repeater-only CORESET based on the DMRS information or QCL assumptions indicated in the initial CORESET.
[0062] The location of the repeater-dedicated CORESET in frequency and time is signaled via the initial CORESET and / or SIB, including an indication of the first slot, the first symbol of the slot, and the first RB of the slot. Each repeater CCE starts from an offset related to the combination of aggregation level (AL) and predefined REP-RNTI signaled via the initial or common CORESET and / or SIB, and each repeater monitors the DCI (e.g., DCI format 7_2A) starting at the corresponding RB. For example, in AL1 for one CCE, a repeater with REP-RNTI=0 monitors the DCI starting at the indicated first RB, while a repeater with REP-RNTI=3 monitors the DCI starting at an RB offset of three RBs from the indicated first RB, such as the initial or common CORESET. The periodicity of the repeater-dedicated CORESET is indicated via the initial CORESET with the number of slots between two consecutive CORESET locations. For example, 4 bits are used to indicate the periodicity of the repeater-only CORESET with a maximum interval of 16 slots between two occasions with an indication granularity of one slot.
[0063] FIG. 5 illustrates an example 500 of a time information indication supporting network-controlled repeater configuration according to an aspect of the present disclosure. Repeater-dedicated DCI in CORESET carries dynamic control information for repeaters to be applied on the forwarding link between the base station and the UE. The forwarding link includes ON / OFF information for switching the repeater ON or OFF for efficient interference management, as well as Tx power information for UL between the repeater and the base station and DL between the repeater and the UE. The forwarding link also includes TCI information for Tx / Rx beamforming of the forwarding signal to or from the UE, SFI information for dynamic TDD, timing information (e.g., first DL slot offset for the control information (k0) to be applied and for the first UL slot (k1, k2)), applicability information of multiple DL / UL slots for the control information to be applied, as shown in FIG. 5.
[0064] In one example, table T2 shows exemplary contents of DCI (DCI format 2_7A) carried by repeater CORESET. [Table 5]
[0065] In one embodiment, the on / off information is explicitly indicated in the DCI. In another embodiment, the on / off information is indicated using the Tx power information, where a value of 0 in the Tx power field indicates to switch the repeater off and other values indicate to switch the repeater on. The applicability information indicates the number of slots for the control information to be applied on the transmission signal. In one embodiment, the information is explicitly signaled for DL and UL. In another embodiment, the applicability of the control information corresponds to the periodicity of the CORESET (e.g., the applicability is valid until a certain time, one or more slots after the next repeater CORESET opportunity). The repeater is indicated with a bit field in the DCI to terminate the periodic repeater CORESET or to expect an update of the periodicity and / or location information, and then the repeater is expected to receive and monitor the repeater common CORESET, which carries the updated configuration of the repeater dedicated CORESET on the repeater common search space. In one embodiment, the ID of the repeater is updated and signaled in the dedicated DCI. This ID can be applied to decode the next set of CORESET monitoring opportunities.
[0066] Alternatively, if the repeater has not received DCI for the common CORESET for a period of time (e.g., "N" consecutive available common COREST opportunities), the repeater falls back to or uses a default set of parameters for determining dedicated CORESET configuration parameters such as AL, DMRS, etc. In a further alternative configuration, the repeater is implemented with a pre-known location of the repeater-dedicated CORESET. The repeater is not expected to monitor the common CORESET, but is configured (pre-configured) to monitor only the repeater-dedicated CORESET at a pre-known opportunity with a known AL, DCI size, known TCI, and known DMRS configuration.
[0067] In a network-controlled repeater configuration aspect, the common CORESET and the dedicated CORESET overlap. For example, a repeater is not expected to have a repeater-dedicated CORESET that overlaps with the common CORESET in time and / or frequency. In such an overlap, the repeater does not monitor or decode any PDCCH candidates associated with the repeater-dedicated CORESET. In another aspect of a multiple transmit / receive point (TRP), a repeater may be configured (pre-configured) with at least two repeater-dedicated CORESETs, where within a time period (e.g., one dedicated CORESET period), the repeater-dedicated DCI of the first CORESET indicates a first TCI for forwarding DL and UL, and the repeater-dedicated DCI of the second CORESET indicates a second TCI for forwarding DL and UL, and the first and second TCIs are different.
[0068] In another example, a repeater may be configured (pre-configured) with at least two repeater-dedicated CORESETs, where a first subset of instructions in the repeater-common DCI is applicable to the at least two repeater-dedicated CORESETs (e.g., AL, periodicity), and a second subset of instructions in the repeater-common DCI provides individual instructions applicable to each of the repeater-dedicated CORESETs (e.g., first slot / symbol / RB of the repeater-dedicated CORESET, DMRS of the repeater-dedicated CORESET, TCI for receiving the dedicated CORESET). In another example, the repeater is not expected to receive two DCIs corresponding to the first and second dedicated CORESETs, a subset of the instruction parameters (e.g., on-off pattern) indicated by the first DCI is different from that of the second DCI, and the first and second DCIs are received in time units (e.g., slots, spans, CORESET period).
[0069] FIG. 6 illustrates an example of a block diagram 600 of a device 602 supporting a network-controlled repeater configuration according to an aspect of the disclosure. The device 602 is an example of a repeater node or device described herein. The device 602 may support wireless communications and / or control signaling with one or more base stations 102, UEs 104, and any combination thereof. The device 602 may include components for bidirectional communication, including components for transmitting and receiving communications, such as a controller 604, a processor 606, a memory 608, a receiver 610, a transmitter 612, and an I / O controller 614. These components are in electronic communication or are otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).
[0070] The controller 604, the receiver 610, the transmitter 612, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the disclosure as described herein. For example, the controller 604, the receiver 610, the transmitter 612, or various combinations thereof or various components thereof may support a method for performing one or more of the functions described herein.
[0071] In some embodiments, the controller 604, the receiver 610, the transmitter 612, or various combinations or components thereof may be implemented in hardware (e.g., communication management circuitry). The hardware may include a processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or supporting a means for performing the functions described in this disclosure. In some embodiments, the processor 606 and a memory 608 coupled to the processor 606 may be configured to perform one or more of the functions described herein (e.g., by the processor 606 executing instructions stored in the memory).
[0072] Additionally or alternatively, in some implementations, the controller 604, the receiver 610, the transmitter 612, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by the processor 606. When implemented in code executed by the processor 606, the functions of the controller 604, the receiver 610, the transmitter 612, or various combinations or components thereof may be performed by a general purpose processor, a DSP, a central processing unit (CPU), an ASIC, an FPGA, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting a means for performing the functions described in this disclosure).
[0073] In some implementations, the controller 604 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise cooperating with the receiver 610, the transmitter 612, or both. For example, the controller 604 may receive information from the receiver 610, transmit information to the transmitter 612, or may be integrated in combination with the receiver 610, the transmitter 612, or both to receive information, transmit information, or perform various other operations as described herein. Although the controller 604 is illustrated as a separate component, in some implementations, one or more functions described with reference to the controller 604 may be supported or performed by the processor 606, the memory 608, or any combination thereof. For example, the memory 608 may store code, which may include instructions executable by the processor 606 to cause the device 602 to perform various aspects of the disclosure as described herein, or the processor 606 and the memory 608 may be otherwise configured to perform or support such operations.
[0074] For example, the controller 604 may support wireless communications and / or control signaling in a device (e.g., device 602, a repeater) according to examples as disclosed herein. The controller 604 and / or other device components may be configured as or otherwise support an apparatus, such as a repeater, that includes a receiver and a controller, where the receiver receives a first configuration of a common control search space and receives a second configuration of a control search space for control information, where the first configuration of the common control search space indicates where to place the second configuration of the control search space, and where the controller decodes the control information from the second configuration of the control search space as repeater downlink control information and applies the control information to a forwarding link between the base station and the user equipment.
[0075] In addition, the apparatus (e.g., a repeater) includes a repeater common control resource set carrying repeater downlink control information arranged in a common control search space of a first configuration. A control search space of a second configuration is a dedicated search space, and a repeater dedicated control resource set carries repeater downlink control information arranged in the dedicated search space. The repeater common control resource set carries repeater downlink control information indicating how to decode the second configuration of the control search space. The receiver is configured to receive in a system information block a third configuration of the repeater dedicated control resource set including decoding information for decoding the repeater dedicated downlink control information in the repeater dedicated control resource set. A cyclic redundancy check of the repeater downlink control information is scrambled using a predefined common repeater radio network temporary identifier that is common to a plurality of repeaters. A cyclic redundancy check of the repeater dedicated downlink control information in the repeater dedicated control resource set is scrambled using a predefined repeater radio network temporary identifier that is unique to the repeater. The repeater dedicated control channel element starts from an offset related to a combination of an aggregation level and a predefined repeater radio network temporary identifier signaled via the repeater common downlink control information, and the controller is configured to monitor the repeater dedicated downlink control information starting from the corresponding resource block offset to the indicated first resource block. A repeater common control resource set is allocated within the bandwidth of the synchronization signal broadcast channel of an initial bandwidth portion having a predefined time offset until the last symbol of the synchronization signal broadcast channel. The repeater downlink control information carried by the repeater dedicated control resource set includes side control information to be applied on a forwarding link between the base station and the user equipment, the side control information including one or more of timing information, spatial information, power control information, or on / off information. The on / off information is implicitly indicated by the value of the power control information, with a power control field of zero indicating an off state and a power control field of non-zero indicating an on state.
[0076] The controller 604 and / or other device components are configured as or otherwise support a means for wireless communication and / or control signaling in a repeater, including receiving a first configuration of a common control search space and receiving a second configuration of a control search space for control information, where the first configuration of the common control search space indicates where to place the second configuration of the control search space, decoding the control information from the second configuration of the control search space as repeater downlink control information, and applying the control information to a forwarding link between the base station and the user equipment.
[0077] Additionally, the wireless communication in the repeater includes a repeater common control resource set carrying repeater downlink control information arranged in a common control search space of a first configuration. A control search space of a second configuration is a dedicated search space, and a repeater dedicated control resource set carries repeater downlink control information arranged in the dedicated search space. The repeater common control resource set carries repeater downlink control information indicating how to decode the second configuration of the control search space. The receiver is configured to receive in a system information block a third configuration of the repeater dedicated control resource set including decoding information for decoding the repeater dedicated downlink control information in the repeater dedicated control resource set. A cyclic redundancy check of the repeater downlink control information is scrambled using a predefined common repeater radio network temporary identifier that is common to a plurality of repeaters. A cyclic redundancy check of the repeater dedicated downlink control information in the repeater dedicated control resource set is scrambled using a predefined repeater radio network temporary identifier that is unique to the repeater. The repeater dedicated control channel element starts from an offset related to a combination of an aggregation level and a predefined repeater radio network temporary identifier signaled via the repeater common downlink control information, and the controller is configured to monitor the repeater dedicated downlink control information starting from the corresponding resource block offset to the indicated first resource block. A repeater common control resource set is allocated within the bandwidth of the synchronization signal broadcast channel of an initial bandwidth portion having a predefined time offset until the last symbol of the synchronization signal broadcast channel. The repeater downlink control information carried by the repeater dedicated control resource set includes side control information to be applied on a forwarding link between the base station and the user equipment, the side control information including one or more of timing information, spatial information, power control information, or on / off information. The on / off information is implicitly indicated by the value of the power control information, with a power control field of zero indicating an off state and a power control field of non-zero indicating an on state.
[0078] The processor 606 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some implementations, the processor 606 may be configured to operate a memory array using a memory controller. In some other implementations, the memory controller may be integrated into the processor 606. The processor 606 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 608) to cause the device 602 to perform various functions of the present disclosure.
[0079] The memory 608 may include random access memory (RAM) and read only memory (ROM). The memory 608 may store computer-readable computer-executable code including instructions that, when executed by the processor 606, cause the device 602 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as a system memory or another type of memory. In some implementations, the code may not be directly executable by the processor 606, but may (e.g., when compiled and executed) cause a computer to perform functions described herein. In some implementations, the memory 608 may include a basic I / O system (BIOS), which may control basic hardware or software operations, such as interactions with peripheral components or devices, among other things.
[0080] The I / O controller 614 may manage input and output signals for the device 602. The I / O controller 614 may also manage peripheral devices that are not integrated into the device 602. In some implementations, the I / O controller 614 may represent a physical connection or port to an external peripheral device. In some implementations, the I / O controller 614 may utilize an operating system, such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or another operating system known. In some implementations, the I / O controller 614 may be implemented as part of a processor, such as the processor 606. In some implementations, a user may interact with the device 602 through the I / O controller 614 or through hardware components controlled by the I / O controller 614.
[0081] In some implementations, the device 602 may include a single antenna 616. However, in some other implementations, the device 602 may have two or more antennas 616 that may be capable of transmitting or receiving multiple wireless transmissions in parallel. The receiver 610 and the transmitter 612 may communicate bidirectionally via one or more antennas 616, a wired link, or a wireless link as described herein. For example, the receiver 610 and the transmitter 612 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver may also include a modem for modulating packets and providing the modulated packets to the one or more antennas 616 for transmission, and for demodulating packets received from the one or more antennas 616.
[0082] FIG. 7 illustrates an example of a block diagram 700 of a device 702 supporting network-controlled repeater configuration, according to an aspect of the disclosure. The device 702 may be an example of a base station 102, such as a gNB, as described herein. The device 702 may support wireless communication and / or network signaling with one or more base stations 102, UEs 104, NTSs 108, repeaters, or any combination thereof. The device 702 may include components for bidirectional communication, including components for transmitting and receiving communications, such as a communications manager 704, a processor 706, a memory 708, a receiver 710, a transmitter 712, and an I / O controller 714. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).
[0083] The communications manager 704, the receiver 710, the transmitter 712, or various combinations or components thereof may be examples of means for performing various aspects of the disclosure as described herein. For example, the communications manager 704, the receiver 710, the transmitter 712, or various combinations or components thereof may support a method for performing one or more of the functions described herein.
[0084] In some implementations, the communications manager 704, the receiver 710, the transmitter 712, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry). The hardware may include a processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing functions described in this disclosure. In some implementations, the processor 706 and a memory 708 coupled to the processor 706 may be configured to perform one or more of the functions described herein (e.g., by the processor 706 executing instructions stored in the memory 708).
[0085] Additionally or alternatively, in some implementations, the communications manager 704, the receiver 710, the transmitter 712, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by the processor 706. When implemented in code executed by the processor 706, the functions of the communications manager 704, the receiver 710, the transmitter 712, or various combinations or components thereof may be performed by a general purpose processor, a DSP, a central processing unit (CPU), an ASIC, an FPGA, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting a means for performing the functions described in this disclosure).
[0086] In some implementations, the communications manager 704 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise cooperating with the receiver 710, the transmitter 712, or both. For example, the communications manager 704 may receive information from the receiver 710, transmit information to the transmitter 712, or be integrated in combination with the receiver 710, the transmitter 712, or both to receive information, transmit information, or perform various other operations as described herein. Although the communications manager 704 is illustrated as a separate component, in some implementations, one or more functions described with reference to the communications manager 704 may be supported or performed by the processor 706, the memory 708, or any combination thereof. For example, the memory 708 may store code, which may include instructions executable by the processor 706 to cause the device 702 to perform various aspects of the disclosure as described herein, or the processor 706 and the memory 708 may be otherwise configured to perform or support such operations.
[0087] For example, the communications manager 704 may support wireless communications in a device (e.g., device 702, base station) according to examples as disclosed herein. The communications manager 704 and / or other device components may be configured as or otherwise support an apparatus, such as a base station, including a transceiver and a processor coupled to the transceiver, where the processor and transceiver cause the apparatus to transmit a first configuration of a common control search space to a repeater, and a second configuration of a control search space for control information to a repeater, where the first configuration of the common control search space indicates to the repeater where to place the second configuration of the control search space, and to decode the control information from the second configuration of the control search space as repeater downlink control information usable to control a forwarding link between the apparatus and user equipment.
[0088] The communications manager 704 and / or other device components may be configured as or otherwise support a means for wireless communications at a base station, including transmitting a first configuration of a common control search space to a repeater and a second configuration of the control search space for control information to the repeater, where the first configuration of the common control search space indicates to the repeater where to place the second configuration of the control search space, and decoding the control information from the second configuration of the control search space as repeater downlink control information usable to control a forwarding link between the device and user equipment.
[0089] The processor 706 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some implementations, the processor 706 may be configured to operate a memory array using a memory controller. In some other implementations, the memory controller may be integrated into the processor 706. The processor 706 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 708) to cause the device 702 to perform various functions of the present disclosure.
[0090] The memory 708 may include random access memory (RAM) and read only memory (ROM). The memory 708 may store computer-readable computer-executable code including instructions that, when executed by the processor 706, cause the device 702 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as a system memory or another type of memory. In some implementations, the code may not be directly executable by the processor 706, but may (e.g., when compiled and executed) cause a computer to perform the functions described herein. In some implementations, the memory 708 may include a basic I / O system (BIOS), which may control basic hardware or software operations, such as interactions with peripheral components or devices, among other things.
[0091] The I / O controller 714 may manage input and output signals for the device 702. The I / O controller 714 may also manage peripheral devices that are not integrated into the device 702. In some implementations, the I / O controller 714 may represent a physical connection or port to an external peripheral device. In some implementations, the I / O controller 714 may utilize an operating system, such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or another operating system known. In some implementations, the I / O controller 714 may be implemented as part of a processor, such as the processor 706. In some implementations, a user may interact with the device 702 through the I / O controller 714 or through hardware components controlled by the I / O controller 714.
[0092] In some implementations, the device 702 may include a single antenna 716. However, in some other implementations, the device 702 may have two or more antennas 716 that may be capable of transmitting or receiving multiple wireless transmissions in parallel. The receiver 710 and the transmitter 712 may communicate bidirectionally via one or more antennas 716, a wired link, or a wireless link as described herein. For example, the receiver 710 and the transmitter 712 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver may also include a modem for modulating packets and providing the modulated packets to the one or more antennas 716 for transmission, and for demodulating packets received from the one or more antennas 716.
[0093] FIG. 8 illustrates a flowchart of a method 800 for supporting network-controlled repeater configuration, according to an aspect of the disclosure. The operations of method 800 may be performed by a device or components thereof as described herein. For example, the operations of method 800 may be performed by a device such as a repeater as described with reference to FIGS. 1-7. In some implementations, the device may execute a set of instructions to control functional elements of the device to perform the described functions. Additionally or alternatively, the device may perform aspects of the described functions using dedicated hardware.
[0094] At 802, the method includes receiving a first configuration of a common control search space. The operations of 802 may be performed according to examples as described herein. In some implementations, aspects of the operations of 802 may be performed by a device as described with reference to FIGS.
[0095] At 804, the method includes receiving a second configuration of a control search space for the control information, the first configuration of the common control search space indicating where to place the second configuration of the control search space. The operations of 804 may be performed according to examples as described herein. In some implementations, aspects of the operations of 804 may be performed by a device as described with reference to FIGS. 1 and 2.
[0096] At 806, the method includes decoding control information from the second configuration of the control search space as repeater downlink control information. The operations of 806 may be performed according to examples as described herein. In some implementations, aspects of the operations of 806 may be performed by a device as described with reference to FIGS. 1 and 2.
[0097] At 808, the method includes applying the control information to a forwarding link between the base station and the user equipment. The operations of 808 may be performed according to examples as described herein. In some implementations, aspects of the operations of 808 may be performed by a device as described with reference to FIGS. 1 and 2.
[0098] FIG. 9 illustrates a flowchart of a method 900 for supporting network-controlled repeater configuration according to aspects of the disclosure. The operations of method 900 may be performed by a device or components thereof as described herein. For example, the operations of method 900 may be performed by a base station, such as a gNB, as described with reference to FIGS. 1-7. In some implementations, the device may execute a set of instructions to control functional elements of the device to perform the described functions. Additionally or alternatively, the device may perform aspects of the described functions using dedicated hardware.
[0099] At 902, the method may include transmitting to a user equipment. The operations of 902 may be performed according to examples as described herein. In some implementations, aspects of the operations of 902 may be performed by a device as described with reference to FIGS.
[0100] At 904, the method may include transmitting the first configuration of the common control search space to the repeater. The operations of 904 may be performed according to examples as described herein. In some implementations, aspects of the operations of 904 may be performed by a device as described with reference to FIGS.
[0101] At 906, the method includes transmitting a second configuration of a control search space for control information to the repeater, where the first configuration of the common control search space indicates to the repeater where to place the second configuration of the control search space, and decoding the control information from the second configuration of the control search space as repeater downlink control information usable to control a forwarding link between the device and the user equipment. The operations of 906 may be performed according to examples as described herein. In some implementations, aspects of the operations of 906 may be performed by a device as described with reference to FIGS. 1 and 2.
[0102] It should be noted that the methods described herein represent possible implementations, and that operations and steps may be rearranged or otherwise modified, and that other implementations are possible. Furthermore, aspects from two or more of the methods may be combined. The order in which the methods are described is not to be construed as limiting, and any number of the described method operations, or combinations of the described method operations, may be performed in any order to perform the method or alternative methods.
[0103] The various example blocks and components described in connection with the disclosure herein may be implemented or performed using a general purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but alternatively, the 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 in conjunction with a DSP core), or any other such configuration.
[0104] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted via a computer-readable medium as one or more instructions or codes. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination thereof. Features implementing the functions may also be physically located in various locations, including being distributed such that portions of the functions are implemented in different physical locations.
[0105] Computer-readable media includes both non-transitory computer storage media and communication media, including any medium that facilitates transfer of a computer program from one place to another. Non-transitory storage media may be any available medium that can be accessed by a general purpose or special purpose computer. By way of example and not limitation, non-transitory computer-readable media may include RAM, ROM, Electrically Erasable Programmable ROM (EEPROM), Flash memory, Compact Disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code means 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.
[0106] Any connection may be properly termed a computer-readable medium. For example, if the 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, the 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, disk and disc include CDs, laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs, where disks typically reproduce data magnetically and discs reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media.
[0107] As used herein, including in the claims, "or" as used in a list of items (e.g., a list of items ended by a phrase such as "at least one of" or "one or more of") indicates an inclusive list, such as, for example, a list of at least one of 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). Also, as used herein, the phrase "based on" is not to be construed as a reference to a closed set of conditions. For example, an exemplary step described as "based on condition A" may be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" is to be construed similarly to the phrase "based at least in part on. Additionally, as used herein, including in the claims, a "set" may include one or more elements.
[0108] The description set forth herein with reference to the accompanying drawings describes exemplary configurations and does not necessarily represent all examples that may be implemented or fall within the scope of the claims. As used herein, the term "exemplary" means "serving as an example, instance, or illustration" and does not mean "preferred" or "advantageous over other examples." The detailed description includes specific details for the purposes of providing an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.
[0109] The description herein is provided to enable any person skilled in the art to make or use the disclosure. Various modifications of the 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 the disclosure. Thus, the disclosure is not limited to the examples and designs described herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein. [Explanation of symbols]
[0110] 100 Wireless communication system 102 Base station 104UE 106 Core Network 108 Non-Terrestrial Networks (NTS) 110, 112, 116 Communication links 114 Geographical Coverage Area 118 Backhaul Links
Claims
1. An apparatus comprising a receiver and a controller, The receiver, receiving a first configuration of a common control search space; receiving a second configuration of a control search space for control information, the first configuration of the common control search space indicating where to place the second configuration of the control search space; The controller: decode the control information from the second configuration of the control search space as repeater downlink control information; An apparatus that applies the control information to a forwarding link between a base station and a user equipment.
2. 2. The apparatus of claim 1, wherein a repeater common control resource set carries the repeater downlink control information located in the common control search space of the first configuration.
3. 2. The apparatus of claim 1, wherein the control search space of the second configuration is a dedicated search space, and a repeater dedicated control resource set carries repeater dedicated downlink control information located in the dedicated search space.
4. 2. The apparatus of claim 1, wherein a repeater common control resource set carries the repeater downlink control information indicating how to decode the second configuration of the control search space.
5. 10. The apparatus of claim 1, wherein the receiver is configured to receive, in a system information block, a third configuration of the repeater dedicated control resource set including decoding information for decoding the repeater dedicated downlink control information in the repeater dedicated control resource set.
6. 10. The apparatus of claim 1, wherein a cyclic redundancy check of the repeater downlink control information is scrambled using a predefined common repeater radio network temporary identifier that is common to multiple repeaters.
7. 10. The apparatus of claim 1, wherein a cyclic redundancy check of the repeater dedicated downlink control information in the repeater dedicated control resource set is scrambled with a predefined repeater radio network temporary identifier that is unique to the repeater.
8. 2. The apparatus of claim 1, wherein the repeater dedicated control channel elements start from an offset associated with a combination of an aggregation level and a predefined repeater radio network temporary identifier signaled via a repeater common downlink control information, and the controller is configured to monitor the repeater dedicated downlink control information starting from a corresponding resource block offset up to the indicated first resource block.
9. The apparatus of claim 1, wherein the repeater common control resource set is allocated within a bandwidth of the synchronization signal broadcast channel of an initial bandwidth portion having a predetermined time offset until a last symbol of the synchronization signal broadcast channel.
10. 2. The apparatus of claim 1, wherein the repeater downlink control information carried by a repeater dedicated control resource set includes side control information to be applied on the forwarding link between the base station and the user equipment, the side control information including one or more of timing information, spatial information, power control information, or on / off information.
11. 11. The apparatus of claim 10, wherein the on / off information is implicitly indicated by a value of the power control information, with a power control field of zero indicating an off state and a non-zero power control field indicating an on state.
12. A transceiver; a processor coupled to the transceiver, the processor and the transceiver comprising: transmitting a first configuration of a common control search space to a repeater; transmitting a second configuration of a control search space for control information to the repeater, where the first configuration of the common control search space indicates to the repeater where to place the second configuration of the control search space; and decoding the control information from the second configuration of the control search space as repeater downlink control information usable to control a forwarding link between the device and user equipment. An apparatus for causing the apparatus to perform the above.
13. 1. A method in a repeater node, comprising: receiving a first configuration of a common control search space; receiving a second configuration of a control search space for control information, the first configuration of the common control search space indicating where to place the second configuration of the control search space; decoding the control information from the second configuration of the control search space as repeater downlink control information; applying the control information to a forwarding link between a base station and a user equipment; A method comprising:
14. The method of claim 13, wherein a repeater common control resource set carries the repeater downlink control information located in the common control search space of the first configuration.
15. The method of claim 13, wherein the control search space of the second configuration is a dedicated search space, and a repeater dedicated control resource set carries repeater dedicated downlink control information located in the dedicated search space.
16. The method of claim 13, wherein a repeater common control resource set carries the repeater downlink control information indicating how to decode the second configuration of the control search space.
17. 14. The method of claim 13, wherein the receiver is configured to receive in a system information block a third configuration of the repeater dedicated control resource set including decoding information for decoding the repeater dedicated downlink control information in the repeater dedicated control resource set.
18. 14. The method of claim 13, wherein a cyclic redundancy check of the repeater downlink control information is scrambled using a predefined common repeater radio network temporary identifier that is common to multiple repeaters.
19. 14. The method of claim 13, wherein a cyclic redundancy check of the repeater dedicated downlink control information in the repeater dedicated control resource set is scrambled with a predefined repeater radio network temporary identifier that is unique to the repeater.
20. 14. The method of claim 13, wherein the repeater dedicated control channel element starts from an offset related to a combination of an aggregation level signaled via the repeater common downlink control information and a predefined repeater radio network temporary identifier, and the controller is configured to monitor the repeater dedicated downlink control information starting from a corresponding resource block offset up to the indicated first resource block.
Citation Information
Patent Citations
Base station device, repeater device, and wireless communication system, and control methods and programs thereof
JP2023036366A
Method and apparatus for transmitting and receiving control channel for relay backhaul link in wireless communication system
US20120128039A1