Cross-carrier shared channel duplication
By using a single DCI to schedule multiple duplication of transmission blocks on different carrier in the wireless communication system, the problem of insufficient flexibility in the existing technologies has been solved, and more efficient signaling processing and user experience improvement have been achieved.
Patent Information
- Application Number
- CN202080078976.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2020-11-18
- Filing Date
- 2020-11-19
- Publication Date
- 2025-01-24
- Estimated Expiration
- 2040-11-19
AI Technical Summary
The existing wireless communication systems are inadequate in repeated scheduling across multiple carrier shared channels, resulting in reduced throughput and increased signaling overhead.
Scheduling multiple transmissions or repetitions of a transport block on different component carriers (CCs) by using a single downlink control information (DCI), dynamically or statically based on the nominal repetition number, length and associated indicators of the transport block .
It improves signaling efficiency, reduces waiting time, enhances flexible scheduling of transmission blocks, and improves coverage area and user experience.
Smart Images

Figure CN114762429B_ABST
Abstract
Description
[0001] Cross-references
[0002] This patent application claims priority to U.S. patent application No. 16 / 951,428, entitled “CROSS CARRIER SHARED CHANNEL REPETITION,” filed by FAKOORIAN et al. on November 18, 2020, which claims priority to U.S. Provisional Patent Application No. 62 / 941,631, entitled “CROSS CARRIER SHARED CHANNEL REPETITION,” filed by FAKOORIAN et al. on November 27, 2019, which applications are assigned to the assignee of this application. Technical Field
[0003] The following relates generally to wireless communications, and more particularly to cross-carrier shared channel repetition.
[0004] background
[0005] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcasting, etc. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems (such as long term evolution (LTE) systems, advanced LTE (LTE-A) systems, or LTE-A Pro systems), and fifth generation (5G) systems that may be referred to as new radio (NR) systems. These systems may use various technologies, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations or one or more network access nodes, each base station or network access node simultaneously supporting the communication of multiple communication devices, which may be referred to as user equipment (UE) in addition.
[0006] The control information for the UE may be used to schedule uplink or downlink transmissions between the UE and the base station. The control information may schedule transmissions via a component carrier (CC) configured for uplink communication or downlink communication. However, such control information may be limited in flexibility for scheduling via multiple CCs, which may result in reduced throughput or increased signaling overhead.
[0007] Overview
[0008] The described technology relates to improved methods, systems, devices and apparatuses for supporting cross-carrier shared channel repetition. In general, the described technology provides for scheduling multiple transmissions or repetitions of a transport block on different component carriers (CCs) using a single downlink control information (DCI). The scheduling of (transport blocks) can be indicated statically or dynamically by the DCI, and the time resources scheduled for the transmission of (transport blocks) can be different between CCs. In addition, the scheduling across multiple CCs can be based on, for example, factors such as the nominal number of repetitions of (transport blocks), the nominal length of each repetition (transport blocks), the start and length indicator (SLIV) associated with the (transport blocks), etc.
[0009] A method of wireless communication at a user equipment (UE) is described. The method may include identifying a set of CCs supported by the UE for communicating with a base station, receiving a downlink control message from the base station, the downlink control message scheduling multiple repetitions of a transport block for the UE, wherein a first repetition of the multiple repetitions is scheduled on a first CC of the CC set, and a second repetition of the multiple repetitions is scheduled on a second CC of the CC set, and transmitting or receiving the first repetition via the first CC, and transmitting or receiving the second repetition via the second CC.
[0010] An apparatus for wireless communication at a UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: identify a set of CCs supported by the UE for communicating with a base station, receive a downlink control message from the base station, the downlink control message scheduling multiple repetitions of a transport block for the UE, wherein a first repetition of the multiple repetitions is scheduled on a first CC of the CC set, and a second repetition of the multiple repetitions is scheduled on a second CC of the CC set, and transmit or receive the first repetition via the first CC, and transmit or receive the second repetition via the second CC.
[0011] Another apparatus for wireless communication at a UE is described. The apparatus may include means for identifying a set of CCs supported by the UE for communicating with a base station, receiving a downlink control message from the base station, the downlink control message scheduling multiple repetitions of a transport block for the UE, wherein a first repetition of the multiple repetitions is scheduled on a first CC of the CC set, and a second repetition of the multiple repetitions is scheduled on a second CC of the CC set, and transmitting or receiving the first repetition via the first CC, and transmitting or receiving the second repetition via the second CC.
[0012] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by a processor for the following operations: identifying a set of CCs supported by the UE for communicating with a base station, receiving a downlink control message from the base station, the downlink control message scheduling multiple repetitions of a transport block for the UE, wherein a first repetition of the multiple repetitions is scheduled on a first CC of the CC set, and a second repetition of the multiple repetitions is scheduled on a second CC of the CC set, and transmitting or receiving the first repetition via the first CC, and transmitting or receiving the second repetition via the second CC.
[0013] Some examples of the methods, apparatus (devices), and non-transitory computer-readable media described herein may further include operations, features, apparatus, or instructions for the following actions: receiving an indication that multiple repetitions of a transport block may be scheduled via a first and second CC according to one or both of a frequency division multiplexing (FDM) scheme or a time division multiplexing (TDM) scheme.
[0014] In some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein, the indication may be received via radio resource control (RRC) signaling, a medium access control (MAC) control element (MAC-CE), or a DCI.
[0015] Some examples of the methods, apparatus (devices), and non-transitory computer-readable media described herein may further include operations, features, apparatus, or instructions for the following actions: receiving an indication of a subset of multiple repetitions of the CC set that can be used for a transport block, the subset including at least a first CC and a second CC, wherein the indication may be received via RRC signaling, MAC-CE, or DCI.
[0016] In some examples of the methods, apparatus (devices), and non-transitory computer-readable media described herein, the indication includes a set of carrier indices corresponding to the subset of the set of CCs.
[0017] Some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for receiving an indication of at least one CC in the set of CCs to be dropped for multiple repetitions of a transport block.
[0018] Some examples of the methods, apparatus (devices), and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for receiving an indication of a starting CC for a plurality of repetitions of a transport block.
[0019] Some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein may further include operations, features, apparatuses, or instructions for transmitting feedback for a subset of the CC set, and receiving an indication of a starting CC for multiple repetitions of a transport block based on the feedback, wherein the subset includes the starting CC.
[0020] In some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein, the feedback indicates an acknowledgement (ACK) / negative ACK (NACK) feedback or a signal to interference plus noise ratio (SINR) for each CC in the subset.
[0021] Some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for the following actions: receiving a reference subcarrier spacing configuration for each CC in a subset of the CC set via RRC signaling, and determining a number of code elements between a downlink control message and a first repetition transmission or reception via a first CC based on the reference subcarrier spacing configuration.
[0022] In some examples of the methods, apparatus (devices), and non-transitory computer-readable media described herein, the number of symbols can be based on a minimum or maximum slot format indicator for the subset, an indication within a downlink control message, a subcarrier spacing of the first CC, or a subcarrier spacing associated with a downlink control message.
[0023] Some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein may further include operations, features, apparatuses, or instructions for determining a first number of symbols between a downlink control message and a first repeated transmission or reception via the first CC based on the subcarrier spacing of the first CC, and determining a second number of symbols between a downlink control message and a second repeated transmission or reception via the second CC based on the subcarrier spacing of the second CC.
[0024] Some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for the following actions: receiving a reference subcarrier spacing configuration for each CC in a subset of the CC set via RRC signaling, and determining a time slot for a first repeated transmission or reception via a first CC based on the reference subcarrier spacing configuration.
[0025] Some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for determining a first time slot for a first repetition of transmission or reception via the first CC based on the subcarrier spacing of the first CC, and determining a second time slot for a second repetition of transmission or reception via the second CC based on the subcarrier spacing of the second CC.
[0026] Some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for the following actions: receiving a reference subcarrier spacing configuration for each CC in a subset of the CC set via RRC signaling, and determining a starting codeword and a time length for a first repeated transmission or reception via a first CC based on the reference subcarrier spacing configuration, wherein the starting codeword and the time length may be the same for the first CC and the second CC.
[0027] Some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein may further include operations, features, apparatuses, or instructions for the following actions: determining a number of codewords for transmission or reception of a first repetition via a first CC, wherein the number of codewords may be the same for the first CC and the second CC.
[0028] Some examples of the methods, apparatus (devices), and non-transitory computer-readable media described herein may further include operations, features, apparatus, or instructions for the following actions: determining a transport block size for a first repeated transmission or reception via a first CC based on a nominal time length and a nominal resource element set indicated by a downlink control message, wherein the transport block size may be the same for the first CC and the second CC.
[0029] Some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein may further include operations, features, apparatuses, or instructions for the following actions: determining a transport block size for a first repeated transmission or reception via the first CC based on a nominal resource element set for the first CC and the second CC, wherein the transport block size may be the same for the first CC and the second CC.
[0030] A method for wireless communication at a base station is described. The method may include: identifying a set of CCs supported by a UE for communicating with the base station, transmitting a downlink control message to the UE, the downlink control message scheduling multiple repetitions of a transport block for the UE, wherein a first repetition of the multiple repetitions is scheduled on a first CC of the CC set, and a second repetition of the multiple repetitions is scheduled on a second CC of the CC set, and transmitting or receiving the first repetition via the first CC, and transmitting or receiving the second repetition via the second CC.
[0031] An apparatus for wireless communication at a base station is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: identify a set of CCs supported by a UE for communicating with a base station, transmit a downlink control message to the UE, the downlink control message scheduling multiple repetitions of a transport block for the UE, wherein a first repetition of the multiple repetitions is scheduled on a first CC of the CC set, and a second repetition of the multiple repetitions is scheduled on a second CC of the CC set, and transmit or receive the first repetition via the first CC, and transmit or receive the second repetition via the second CC.
[0032] Another apparatus for wireless communication at a base station is described. The apparatus may include means for identifying a set of CCs supported by a UE for communicating with the base station, transmitting a downlink control message to the UE, the downlink control message scheduling multiple repetitions of a transport block for the UE, wherein a first repetition of the multiple repetitions is scheduled on a first CC of the CC set, and a second repetition of the multiple repetitions is scheduled on a second CC of the CC set, and transmitting or receiving the first repetition via the first CC, and transmitting or receiving the second repetition via the second CC.
[0033] A non-transitory computer-readable medium storing code for wireless communication at a base station is described. The code may include instructions executable by a processor for the following operations: identifying a set of CCs supported by a UE for communicating with the base station, transmitting a downlink control message to the UE, the downlink control message scheduling multiple repetitions of a transport block for the UE, wherein a first repetition of the multiple repetitions is scheduled on a first CC of the CC set, and a second repetition of the multiple repetitions is scheduled on a second CC of the CC set, and transmitting or receiving the first repetition via the first CC, and transmitting or receiving the second repetition via the second CC.
[0034] Some examples of the methods, apparatus (devices), and non-transitory computer-readable media described herein may further include operations, features, apparatus, or instructions for transmitting an indication that multiple repetitions of a transport block may be scheduled via a first and second CC according to one or both of an FDM scheme or a TDM scheme.
[0035] In some examples of the methods, apparatus (devices), and non-transitory computer-readable media described herein, the indication may be transmitted via RRC signaling, MAC-CE, or DCI.
[0036] Some examples of the methods, apparatus (devices), and non-transitory computer-readable media described herein may further include operations, features, apparatus, or instructions for the following actions: transmitting an indication of a subset of the CC set that can be used for multiple repetitions of a transport block, the subset including at least a first CC and a second CC, wherein the indication may be transmitted via RRC signaling, MAC-CE, or DCI.
[0037] In some examples of the methods, apparatus (devices), and non-transitory computer-readable media described herein, the indication includes a set of carrier indices corresponding to the subset of the set of CCs.
[0038] Some examples of methods, apparatuses (devices), and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for transmitting an indication of at least one CC in the set of CCs to be dropped for multiple repetitions of a transport block.
[0039] Some examples of the methods, apparatus (devices), and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for transmitting an indication of a starting CC for a plurality of repetitions of a transport block.
[0040] Some examples of the methods, apparatus (devices), and non-transitory computer-readable media described herein may further include operations, features, apparatuses, or instructions for the following actions: receiving feedback from the UE for a subset of the CC set, and transmitting an indication of a starting CC for multiple repetitions of a transport block based on the feedback, wherein the subset includes the starting CC.
[0041] In some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein, the feedback indicates ACK / NACK feedback or SINR for each CC in the subset.
[0042] Some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for transmitting, via RRC signaling, a reference subcarrier spacing configuration for each CC in a subset of the CC set, scheduling a first repetition of transmission or reception via a first CC based on the reference subcarrier spacing configuration, and scheduling a second repetition of transmission or reception via a second CC based on the reference subcarrier spacing configuration.
[0043] Some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein may further include operations, features, apparatuses, or instructions for scheduling a first repetition of transmission or reception via a first CC based on a first subcarrier spacing configuration associated with the first CC, and scheduling a second repetition of transmission or reception via a second CC based on a second subcarrier spacing configuration associated with the second CC.
[0044] Some examples of the methods, apparatus (devices), and non-transitory computer-readable media described herein may further include operations, features, apparatus, or instructions for scheduling transmission or reception of a first repetition via a first CC based on a subcarrier spacing configuration associated with a downlink control message. BRIEF DESCRIPTION OF THE DRAWINGS
[0045] Figures 1 to 4 An example wireless communication system supporting cross-carrier shared channel repetition in accordance with aspects of the present disclosure is illustrated.
[0046] Figure 5 An example of a process flow to support cross-carrier shared channel repetition in accordance with aspects of the present disclosure is illustrated.
[0047] Figure 6 and Figure 7 A block diagram of an apparatus supporting cross-carrier shared channel repetition according to aspects of the present disclosure is shown.
[0048] Figure 8 A block diagram of a communication manager supporting cross-carrier shared channel duplication is shown in accordance with aspects of the present disclosure.
[0049] Fig. 9 A diagram of a system including a device supporting cross-carrier shared channel repetition is shown in accordance with aspects of the present disclosure.
[0050] Fig.10 and Fig.11 A block diagram of an apparatus supporting cross-carrier shared channel repetition according to aspects of the present disclosure is shown.
[0051] Fig.12A block diagram of a communication manager supporting cross-carrier shared channel duplication is shown in accordance with aspects of the present disclosure.
[0052] Fig.13 A diagram of a system including a device supporting cross-carrier shared channel repetition is shown in accordance with aspects of the present disclosure.
[0053] Figures 14 to 20 A flow chart illustrating a method of supporting cross-carrier shared channel repetition according to aspects of the present disclosure is shown.
[0054] Detailed Description
[0055] Downlink control information (DCI) may be used by a base station to schedule one or more transport blocks for a user equipment (UE) as part of an uplink or downlink data transmission, which may be transmitted via an uplink data channel (e.g., a physical uplink shared channel (PUSCH)) or a downlink data channel (e.g., a physical downlink shared channel (PDSCH)) scheduled by the DCI. In addition, the uplink or downlink may be scheduled by the DCI across more than one component carrier (CC). For example, a base station may repeatedly schedule multiple transmissions or repetitions of a transport block using a cross-CC shared channel, such that the DCI is transmitted via a first CC and the transmission is scheduled via multiple other CCs different from the first CC.
[0056] Techniques for cross-CC shared channel repetition using a single DCI are described herein. The techniques may facilitate scheduling one or more transport blocks across multiple CCs for uplink or downlink communications. A single DCI may be used to schedule multiple transmissions or repetitions of one or more transport blocks across multiple CCs. In addition, the scheduling of transport blocks may be indicated statically or dynamically by the DCI based on factors associated with CCs, transport blocks, UEs, or base stations, etc.
[0057] Various aspects of the present disclosure are initially described in the context of a wireless communication system. Various aspects of the present disclosure are described with respect to process flows. Various aspects of the present disclosure are further illustrated and described by and with reference to apparatus diagrams, system diagrams, and flow charts related to downlink control information for scheduling one or more transport blocks.
[0058] Figure 1An example of a wireless communication system 100 supporting cross-carrier shared channel repetition according to various aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more base stations 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a long term evolution (LTE) network, an advanced LTE (LTE-A) network, an LTE-A Pro network, or a new radio (NR) network. In some examples, the wireless communication system 100 may support enhanced broadband communications, ultra-reliable (e.g., mission-critical) communications, low latency communications, communications with low-cost and low-complexity devices, or any combination thereof.
[0059] The base stations 105 may be dispersed throughout a geographic area to form the wireless communication system 100, and may be different forms of devices or devices with different capabilities. The base stations 105 and the UEs 115 may communicate wirelessly via one or more communication links 125. Each base station 105 may provide a coverage area 110 over which the UEs 115 and the base stations 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area over which the base stations 105 and the UEs 115 may support communication of signals according to one or more radio access technologies.
[0060] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile, or stationary and mobile at different times. The UEs 115 may be different forms of devices or devices with different capabilities. Figure 1 Some example UEs 115 are illustrated in FIG. 1. The UEs 115 described herein may be capable of communicating with various types of devices, such as other UEs 115, base stations 105, or network equipment (e.g., core network nodes, relay devices, integrated access and backhaul (IAB) nodes, or other network equipment), such as Figure 1 as shown in .
[0061] Each base station 105 may communicate with the core network 130 or with each other or both. For example, the base station 105 may interface with the core network 130 via one or more backhaul links 120 (e.g., via S1, N2, N3, or other interfaces). The base stations 105 may communicate with each other directly (e.g., directly between the base stations 105) or indirectly (e.g., via the core network 130), or directly and indirectly on the backhaul link 120 (e.g., via X2, Xn, or other interfaces). In some examples, the backhaul link 120 may be or include one or more wireless links.
[0062] One or more of the base stations 105 described herein may include or may be referred to by a person of ordinary skill in the art as a base transceiver station, a radio base station, an access point, a radio transceiver, a B node, an evolved B node (eNB), a next generation B node or a gigabit B node (any of which may be referred to as a gNB), a home B node, a home evolved B node, or other suitable terminology.
[0063] UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable term, where a "device" may also be referred to as a unit, a station, a terminal, or a client, etc. UE 115 may also include or may be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, UE 115 may include or be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc., which may be implemented in various objects such as electrical appliances or vehicles, meters, etc.
[0064] The UE 115 described herein may be capable of communicating with various types of devices, such as other UEs 115, which may sometimes act as relays, as well as base stations 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, relay base stations, etc. Figure 1 as shown in .
[0065] The UE 115 and the base station 105 may communicate wirelessly with each other via one or more communication links 125 on one or more carriers. The term "carrier" may refer to a set of radio frequency spectrum resources having a defined physical layer structure for supporting the communication link 125. For example, a carrier for the communication link 125 may include a portion of a radio frequency spectrum band (e.g., a bandwidth portion (BWP)) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling for coordinating carrier operations, user data, or other signaling. The wireless communication system 100 may support communication with the UE 115 using carrier aggregation or multi-carrier operation. The UE 115 may be configured with multiple downlink CCs and one or more uplink CCs according to the carrier aggregation configuration. Carrier aggregation may be used in conjunction with both frequency division duplex (FDD) and time division duplex (TDD) CCs.
[0066] In some examples (e.g., in a carrier aggregation configuration), a carrier may also have acquisition signaling or control signaling that coordinates the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute Radio Frequency Channel Number (EARFCN)) and may be located according to a channel grid for discovery by UE 115. A carrier may operate in a standalone mode in which initial acquisition and connection may be made by UE 115 via the carrier, or a carrier may operate in a non-standalone mode in which a connection is anchored using a different carrier (e.g., a different carrier of the same or different radio access technology).
[0067] The communication link 125 shown in the wireless communication system 100 may include an uplink transmission from the UE 115 to the base station 105, or a downlink transmission from the base station 105 to the UE 115. A carrier may carry downlink or uplink communications (e.g., in an FDD mode), or may be configured to carry both downlink and uplink communications (e.g., in a TDD mode).
[0068] A carrier may be associated with a particular bandwidth of a radio frequency spectrum, and in some examples, the carrier bandwidth may be referred to as a "system bandwidth" of the carrier or wireless communication system 100. For example, the carrier bandwidth may be one of several determined bandwidths (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz (MHz)) of a carrier of a particular radio access technology. Devices (e.g., base stations 105, UEs 115, or both) of the wireless communication system 100 may have a hardware configuration that supports communications on a particular carrier bandwidth, or may be configurable to support communications on one of a set of carrier bandwidths. In some examples, the wireless communication system 100 may include a base station 105 or UE 115 that supports simultaneous communications via carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate on a portion (e.g., subband, BWP) or all of a carrier bandwidth.
[0069] The signal waveform transmitted on the carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system using MCM technology, a resource element may include a code element period (e.g., the duration of a modulation code element) and a subcarrier, where the code element period and the subcarrier spacing are inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both). Thus, the more resource elements received by UE 115 and the higher the order of the modulation scheme, the higher the data rate of UE 115 can be. Wireless communication resources may refer to a combination of radio frequency spectrum resources, time resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial layers may further improve the data rate or data integrity of communication with UE 115.
[0070] One or more parameter designs for a carrier may be supported, where the parameter designs may include subcarrier spacing (Δf) and cyclic prefixes. A carrier may be divided into one or more BWPs with the same or different parameter designs. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time, and communications for a UE 115 may be limited to the one or more active BWPs.
[0071] The time interval of the base station 105 or the UE 115 can be expressed as a multiple of a basic time unit, and the basic time unit can be, for example, a sampling period T s =1 / (Δf max ·N f ) seconds, where Δf max It can represent the maximum supported subcarrier spacing, and N fMay represent the maximum supported discrete Fourier transform (DFT) size. The time intervals of the communication resources may be organized according to radio frames each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023). Each frame may include a plurality of consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may be divided into subframes (e.g., in the time domain), and each subframe may be further divided into a number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a number of codeword periods (e.g., depending on the length of the cyclic prefix added before each codeword period). In some wireless communication systems 100, the time slot may be further divided into a plurality of mini-slots containing one or more codewords. Excluding the cyclic prefix, each codeword period may include one or more (e.g., Nf) sampling periods. The duration of the codeword period may depend on the subcarrier spacing or the operating frequency band.
[0072] A subframe, slot, mini-slot, or symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., the number of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in bursts of shortened TTIs (sTTIs)).
[0073] Physical channels may be multiplexed on a carrier according to various techniques. Physical control channels and physical data channels may be multiplexed on a downlink carrier, for example, using one or more of a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique. A control region (e.g., a control resource set (CORESET)) for a physical control channel may be defined by a number of symbol periods and may extend across a system bandwidth or a subset of a system bandwidth of a carrier. One or more control regions (e.g., CORESETs) may be configured for a set of UEs 115. For example, one or more of the UEs 115 may monitor or search a control region for control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. An aggregation level for a control channel candidate may refer to the number of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space sets may include a common search space set configured for transmitting control information to multiple UEs 115 and a UE-specific search space set for transmitting control information to a specific UE 115 .
[0074] Each base station 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hot spots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used to communicate with a base station 105 (e.g., on a carrier), and may be associated with an identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or other) used to distinguish adjacent cells. In some examples, a cell may also refer to a geographic coverage area 110 or a portion of a geographic coverage area 110 (e.g., a sector) on which a logical communication entity operates. The range of such a cell may range from a smaller area (e.g., a structure, a subset of a structure) to a larger area depending on various factors (such as the capabilities of the base station 105). For example, a cell may be or include a building, a subset of a building, or an external space between or overlapping a geographic coverage area 110, as well as other examples.
[0075] A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access to UEs 115 that have service subscriptions with a network provider that supports the macro cell. A small cell may be associated with a lower power base station 105 (compared to a macro cell), and the small cell may operate in the same or different (e.g., licensed, unlicensed) frequency band as the macro cell. A small cell may provide unrestricted access to UEs 115 that have service subscriptions with a network provider, or may provide restricted access to UEs 115 associated with the small cell (e.g., UEs 115 in a closed subscriber group (CSG), UEs 115 associated with users in a home or office). A base station 105 may support one or more cells and may also support communications on one or more cells using one or more CCs.
[0076] In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB)) that may provide access to different types of devices.
[0077] In some examples, base stations 105 may be mobile and thus provide communication coverage for mobile geographic coverage areas 110. In some examples, different geographic coverage areas 110 associated with different technologies may overlap, but the different geographic coverage areas 110 may be supported by the same base station 105. In other examples, overlapping geographic coverage areas 110 associated with different technologies may be supported by different base stations 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of base stations 105 provide coverage for various geographic coverage areas 110 using the same or different radio access technologies.
[0078] The wireless communication system 100 may support synchronous or asynchronous operation. For synchronous operation, the base stations 105 may have similar frame timing, and transmissions from different base stations 105 may be approximately aligned in time. For asynchronous operation, the base stations 105 may have different frame timing, and transmissions from different base stations 105 may not be aligned in time in some examples. The techniques described herein may be used for synchronous or asynchronous operation.
[0079] Some UEs 115, such as MTC or IoT devices, may be low-cost or low-complexity devices and may provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC may refer to data communication technology that allows devices to communicate with each other or with a base station 105 without human intervention. In some examples, M2M communication or MTC may include communications from devices that integrate sensors or meters to measure or capture information and relay such information to a central server or application that utilizes the information or presents the information to a person interacting with the application. Some UEs 115 may be designed to collect information or implement automated behavior of machines or other devices. Examples of applications for MTC devices include: smart metering, inventory monitoring, water level monitoring, equipment monitoring, health care monitoring, field survival monitoring, weather and geographic event monitoring, queue management and tracking, remote security sensing, physical access control, and transaction-based commercial charging.
[0080] Some UEs 115 may be configured to employ a reduced power consumption mode of operation, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception but not simultaneous transmission and reception). In some examples, half-duplex communication may be performed with a reduced peak rate. Other power saving techniques for UE 115 include entering a power saving deep sleep mode when not engaged in active communications, operating on a limited bandwidth (e.g., according to narrowband communications), or a combination of these techniques. For example, some UEs 115 may be configured to operate using a narrowband protocol type that is associated with a defined portion or range (e.g., a subcarrier or resource block (RB) set) within a carrier, within a guard band of a carrier, or outside a carrier.
[0081] The wireless communication system 100 may be configured to support ultra-reliable communication or low latency communication or various combinations thereof. For example, the wireless communication system 100 may be configured to support ultra-reliable low latency communication (URLLC) or mission-critical communication. UE 115 may be designed to support ultra-reliable, low latency or critical functions (e.g., mission-critical functions). Ultra-reliable communication may include private communication or group communication, and may be supported by one or more mission-critical services (such as mission-critical push-to-talk (MCPTT), mission-critical video (MCVideo), or mission-critical data (MCData). Support for mission-critical functions may include prioritization of services, and mission-critical services may be used for public safety or general commercial applications. The terms ultra-reliable, low latency, critical mission, and ultra-reliable low latency may be used interchangeably herein.
[0082] In some examples, UE 115 may also be able to communicate directly with other UE 115 over a device-to-device (D2D) communication link 135 (e.g., using a peer-to-peer (P2P) or D2D protocol). One or more UEs 115 utilizing D2D communication may be within a geographic coverage area 110 of a base station 105. Other UEs 115 in such a group may be outside the geographic coverage area 110 of the base station 105, or may not be able to receive transmissions from the base station 105 for other reasons. In some examples, each group of UEs 115 communicating via D2D communication may utilize a one-to-many (1:M) system, wherein each UE 115 transmits to each other UE 115 in the group. In some examples, the base station 105 facilitates the scheduling of resources for D2D communication. In other cases, D2D communication is performed between each UE 115 without involving the base station 105.
[0083] In some systems, the D2D communication link 135 can be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, the vehicles can communicate using vehicle-to-everything (V2X) communications, vehicle-to-vehicle (V2V) communications, or some combination of these communications. The vehicles can signal information related to traffic conditions, signal scheduling, weather, safety, emergency situations, or any other information related to the V2X system. In some examples, vehicles in the V2X system can communicate with roadside infrastructure (such as roadside units), or with the network, or both, using vehicle-to-network (V2N) communications via one or more network nodes (e.g., base station 105).
[0084] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), and the EPC or 5GC may include at least one control plane entity (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) for managing access and mobility, and at least one user plane entity (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)) for routing packets or interconnecting to an external network. The control plane entity may manage non-access layer (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by a base station 105 associated with the core network 130. User IP packets may be delivered through a user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to a network operator IP service 150. Operator IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.
[0085] Some network devices (such as base stations 105) may include subcomponents, such as access network entities 140, which may be examples of access node controllers (ANCs). Each access network entity 140 may communicate with each UE 115 through one or more other access network transport entities 145, which may be referred to as radio heads, smart radio heads, or transmission / reception points (TRPs). Each access network transport entity 145 may include one or more antenna panels. In some configurations, the various functions of each access network entity 140 or base station 105 may be distributed across various network devices (e.g., radio heads and ANCs) or merged into a single network device (e.g., base station 105).
[0086] The wireless communication system 100 may operate using one or more frequency bands, typically in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). In general, the 300 MHz to 3 GHz region is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelengths range from about 1 decimeter to 1 meter long. UHF waves may be blocked or redirected by buildings and environmental features, but these waves may penetrate various structures sufficiently for macro cells to provide service to UEs 115 located indoors. Transmissions using UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) than transmissions using smaller frequencies and longer waves in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.
[0087] The wireless communication system 100 may also operate in a super high frequency (SHF) zone using a frequency band from 3 GHz to 30 GHz (also known as a centimeter band) or in an extremely high frequency (EHF) zone of a spectrum (e.g., from 30 GHz to 300 GHz) (also known as a millimeter band). In some examples, the wireless communication system 100 may support millimeter wave (mmW) communications between UE 115 and base station 105, and the EHF antenna of the corresponding device may be smaller and more closely spaced than the UHF antenna. In some examples, this may facilitate the use of antenna arrays within the device. However, the propagation of EHF transmissions may be subject to even greater atmospheric attenuation and a shorter range than SHF or UHF transmissions. The technology disclosed herein may be adopted across transmissions using one or more different frequency zones, and the use of frequency bands specified across these frequency zones may vary by country or regulatory agency.
[0088] The wireless communication system 100 may utilize both licensed and unlicensed radio frequency spectrum bands. For example, the wireless communication system 100 may employ licensed assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology in an unlicensed band (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band). When operating in an unlicensed radio frequency spectrum band, devices (such as base stations 105 and UEs 115) may employ carrier sensing for conflict detection and avoidance. In some examples, operations in an unlicensed band may be based on a carrier aggregation configuration (e.g., LAA) in coordination with CCs operating in a licensed band. Operations in an unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among others.
[0089] The base station 105 or UE 115 may be equipped with multiple antennas, which can be used to employ technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of the base station 105 or UE 115 may be located in one or more antenna arrays or antenna panels that can support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly (such as an antenna tower). In some examples, the antennas or antenna arrays associated with the base station 105 may be located at different geographical locations. The base station 105 may have an antenna array having antenna ports of several rows and columns that the base station 105 can use to support beamforming for communications with the UE 115. Similarly, the UE 115 may have one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support radio frequency beamforming for signals transmitted via the antenna ports.
[0090] The base station 105 or UE 115 can use MIMO communication to utilize multipath signal propagation and improve spectral efficiency by transmitting or receiving multiple signals via different spatial layers. Such technology may be referred to as spatial multiplexing. For example, the transmitting device may transmit multiple signals via different antennas or different antenna combinations. Similarly, the receiving device may receive multiple signals via different antennas or different antenna combinations. Each of the multiple signals may be referred to as a separate spatial stream and may carry bits associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports for channel measurement and reporting. MIMO technology includes single-user MIMO (SU-MIMO), in which multiple spatial layers are transmitted to the same receiving device; and multi-user MIMO (MU-MIMO), in which multiple spatial layers are transmitted to multiple devices.
[0091] The wireless communication system 100 may be a packet-based network that operates according to a layered protocol stack. In the user plane, the communication of the carrier or grouping data convergence protocol (PDCP) layer may be IP-based. The radio link control (RLC) layer may perform grouping segmentation and regrouping to communicate on a logical channel. The media access control (MAC) layer may perform priority handling and multiplex logical channels into transport channels. The MAC layer may also use error detection techniques, error correction techniques, or both to support retransmission of the MAC layer to improve link efficiency. In the control plane, the radio resource control (RRC) protocol layer may provide the establishment, configuration, and maintenance of an RRC connection that supports a radio bearer of user plane data between a UE 115 and a base station 105 or a core network 130. At the physical layer, transport channels may be mapped to physical channels.
[0092] UE 115 and base station 105 may support retransmission of data to increase the likelihood that the data is successfully received. Hybrid automatic repeat request (HARQ) feedback is a technique for increasing the likelihood that data is correctly received on communication link 125. HARQ may include a combination of error detection (e.g., using cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ may improve the throughput of the MAC layer in poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, a device may support simultaneous slot HARQ feedback, wherein the device may provide HARQ feedback in a specific time slot for data received in a previous symbol in the time slot. In other cases, the device may provide HARQ feedback in a subsequent time slot or according to some other time interval.
[0093] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, and the like. These systems may be multiple access systems capable of supporting communication with multiple users by sharing available system resources (e.g., time, frequency, and power). A wireless network (e.g., a wireless local area network (WLAN), such as a Wi-Fi (i.e., an Institute of Electrical and Electronics Engineers (IEEE) 802.11) network) may include an access point (AP) that can communicate with one or more wireless or mobile devices. An AP may be coupled to a network (such as the Internet) and may enable a mobile device to communicate via the network (or to communicate with other devices coupled to the access point). A wireless device may communicate bidirectionally with a network device. For example, in a WLAN, a device may communicate with an associated AP via a downlink (e.g., a communication link from an AP to a device) and an uplink (e.g., a communication link from a device to an AP). A wireless personal area network (PAN), which may include a Bluetooth connection, may provide a short-range wireless connection between two or more paired wireless devices. For example, a wireless device (such as a cellular telephone) may utilize wireless PAN communications to exchange information, such as audio signals, with a wireless head mounted device.
[0094] The techniques described herein may facilitate scheduling one or more transport blocks across multiple CCs for uplink or downlink communications. A single DCI may be used to schedule multiple transmissions or repetitions of one or more transport blocks across multiple CCs. In addition, the scheduling of transport blocks may be indicated statically or dynamically by the DCI based on multiple factors associated with CCs, transport blocks, UEs, or base stations, as well as other factors.
[0095] Thus, the wireless communication system 100 can more efficiently utilize the transmission or reception resources available to the base station 105 and the UE 115 to transmit or receive one or more transport blocks as scheduled by the DCI. Such features can improve signaling efficiency and reduce latency by increasing the number of CCs available for transmission or reception at a given time and by facilitating efficient determination of the scheduling of transport blocks using a single DCI. In some examples, scheduling the repetition of one or more transport blocks across multiple CCs can improve the coverage area available for transmission and reception between the base station 105 and the UE 115. In some examples, using a single DCI to schedule the repetition or transmission of one or more transport blocks across multiple CCs can reduce the power consumption of the UE 115 when communicating with the base station 105. By scheduling the repetition of transport blocks across multiple CCs using a single DCI that can statically or dynamically determine the scheduling of repetitions, the user experience of the UE 115 can be improved by increased battery life of the UE 115, increased data throughput, increased transmission and reception availability, and reduced possibility of data loss.
[0096] Figure 2 An example of a wireless communication system 200 that supports cross-CC shared channel duplication according to aspects of the present disclosure is illustrated. In some examples, the wireless communication system 200 can implement aspects of the wireless communication system 100. The wireless communication system 200 can include a UE 115-a and a base station 105-a, which can be referenced Figure 1 Examples of UE 115 and base station 105 are described.
[0097] In some cases, the base station 105-a and the UE 115-a may communicate using the downlink link 205 and the uplink link 210. The base station 105-a may transmit a DCI to the UE 115-a on the downlink link 205 to schedule the transmission. For example, the DCI may schedule resources for the base station 105-a to repeat across CC shared channels on the downlink link 205 to the UE 115-a for downlink communication. Alternatively, the DCI may schedule the UE 115-a to transmit to the base station 105-a on the uplink link 210 using cross-CC shared channel repetitions for uplink communication. In some cases, cross-CC shared channel repetitions may be used to carry uplink or downlink data, which may be transmitted on an uplink data channel (e.g., PUSCH) or a downlink data channel (e.g., PDSCH) scheduled by the DCI.
[0098] In some cases, a single DCI transmission may schedule multiple transmissions or repetitions of a transport block on different CCs. Figure 2As illustrated in FIG. 2 , DCI 215 may schedule PUSCH repetitions on multiple different CCs. For example, DCI 215 may schedule a first repetition 245 on four symbols on a first CC 220, a second repetition 250 on four symbols on a second CC 225, and a third repetition 255 on four symbols on a third CC 230. In the illustrated example, each of the repetitions occurs within a first slot 235 and on overlapping symbols across CCs.
[0099] In some cases, DCI 215 may support scheduling multiple PDSCH or PUSCH repetitions across one or more of the CCs. For example, the repetitions may be scheduled according to an FDM scheme. When the FDM scheme is used, due to intra-band repetitions, DCI 215 may incorporate power sharing across CCs as part of the scheduled PUSCH repetitions. In some cases, repetitions may be scheduled according to a TDM scheme. When the TDM scheme is used, power sharing is not indicated, however, system latency may increase compared to using the FDM scheme during scheduled PUSCH repetitions. In some cases, UE 115-a may be configured or dynamically indicated by DCI 215 to operate using one of the FDM or TDM schemes, or to perform each repetition on a single CC.
[0100] In some cases, a single DCI 215 may indicate which CCs will be used for each repetition. In some cases, the CCs to be used as part of the repetition scheme may be indicated dynamically or semi-statically. In some cases, the CCs may be indicated dynamically via the DCI 215. In such a case, starting with the first CC 220, the carrier indicator field (CIF) may indicate which CC index may be dropped, and the following CCs (e.g., the CCs to be used) may be indicated by a modulo. In this example, the modulo may be the CIF plus k, N cap(封顶) , where k = 0, 1, ..., and N cap is equal to the number of configured uplink cells or the number of configured downlink cells for PUSCH or PDSCH repetition, respectively.
[0101] In some cases, the CCs to participate in the scheduled repetition may be dynamically indicated through the DCI 215 using an indication from the UE 115-a. For example, as part of a downlink transmission, the UE 115-a may provide a "soft" ACK / NACK that may generate information related to the SINR or decodability of each of the CCs. The CIF within the DCI 215 may acknowledge such a suggestion from the UE 115-a, and may acknowledge the suggestion by indicating the CC index at the top of a list maintained by the UE 115-a. Additional CCs may be obtained by the module from a list maintained by the UE 115-a, which list also includes information related to the ordering of the CCs (e.g., according to an order based on priority, signal quality or other measurement, or other parameters related to the CCs).
[0102] Figure 3 An example of a wireless communication system 300 that supports cross-CC shared channel duplication according to aspects of the present disclosure is illustrated. In some examples, the wireless communication system 300 can implement aspects of the wireless communication system 100 or 200. The wireless communication system 300 may include a UE 115-b and a base station 105-b, which may be as described with reference to Figure 1 Examples of UE 115 and base station 105 are described.
[0103] In this scenario, the base station 105-b and the UE 115-b may communicate using the downlink link 305 and the uplink link 310. The base station 105-b may transmit a DCI 315 to the UE 115-c on the downlink link 305 to schedule transmissions. For example, the DCI 315 may schedule resources for the base station 105-b to repeat across CC shared channels on the downlink link 305 to the UE 115-b for downlink communications. Alternatively, the DCI 315 may schedule the UE 115-b to transmit to the base station 105-b on the uplink link 310 using the cross-CC shared channel repetition for uplink communications. In some cases, the cross-CC shared channel repetition may be used to carry uplink or downlink data, which may be transmitted on an uplink data channel (e.g., PUSCH) or a downlink data channel (e.g., PDSCH) scheduled by the DCI 315.
[0104] In some cases, such as Figure 3As illustrated in , a single DCI transmission may schedule multiple transmissions or repetitions of a transport block on different CCs. In such a case, DCI 315 may schedule PUSCH repetitions on multiple different CCs. For example, DCI 315 may schedule a first repetition 345 on four symbols on a first CC 320, a second repetition 350 on four symbols on a second CC 325, and a third repetition 355 on four symbols on a third CC 330. In the illustrated example, the first repetition 345 is located within the first time slot 235, and the second repetition 350 and the third repetition 355 are staggered relative to the first repetition and relative to each other within a second time slot 340, which consecutively follows the first time slot 335, such that no repetitions or only a portion of the repetitions overlap in time.
[0105] In this example embodiment, a single carrier N 2 The transmission on the shared channel (which is the number of symbols between the reception of the DCI and the transmission of the shared channel scheduled by the DCI) may be based on μ, where μ corresponds to the maximum T proc,2 One of the corresponding μDL or μUL. In such an example, μDL can correspond to the subcarrier spacing of a downlink channel used to transmit a physical downlink control channel (PDCCH) carrying DCI 215 for scheduling PUSCH. In addition, in such an example, μUL can correspond to the subcarrier spacing of an uplink channel used to transmit PUSCH.
[0106] In some cases, for PUSCH repetitions using different CCs, N for each CC may be obtained. 2 . In some cases, the μUL may correspond to a reference subcarrier spacing (SCS) configuration. In such a case, the UE 115-b may be provided by a reference SCS configuration for each cell, and the μUL may be the minimum μUL or the maximum μUL across the configured cells. In some cases, the μUL may be determined by using a constant, which may be provided by a CIF in the DCI 215. In some cases, the μUL may correspond to the subcarrier spacing of the active uplink BWP for the cell given by the DCI 215. In some cases, the μUL may correspond to the subcarrier spacing of the μDL used to transmit the PDCCH carrying the DCI 215. In some additional examples, the μUL for each cell may correspond to the SCS of one of the active uplink BWP or the default uplink BWP used to transmit the PUSCH.
[0107] In some cases, PUSCH repetitions may be on separate and different CCs, and the K used for transmission on each CC may be obtained through time domain resource allocation (TDRA) based on a parameter set. 2In some cases, it can be possible to check μPUSCH and K 2 To determine the parameter set, μPUSCH and K 2 Both may correspond to a reference SCS configuration indicating that each repetition may start simultaneously. 2 The SCS may correspond to one of the active UL BWP or the default UL BWP used to transmit the PUSCH.
[0108] For downlink shared channels, PDSCH repetitions can be on separate and different CCs, and the K for transmission on each CC can be obtained through TDRA based on the parameter set. 0 In some cases, it can be possible to check μPDSCH and K 0 To determine the parameter set, μPDSCH and K 0 Both may correspond to a reference SCS configuration indicating that each repetition may start simultaneously. 0 The SCS may correspond to one of the active downlink BWP or the default downlink BWP used to transmit the PDSCH.
[0109] Figure 4 An example of a wireless communication system 400 that supports cross-CC shared channel duplication according to aspects of the present disclosure is illustrated. In some examples, the wireless communication system 400 can implement aspects of the wireless communication systems 100, 200, or 300. The wireless communication system 400 may include a UE 115-c and a base station 105-c, which may be referenced Figure 1 Examples of UE 115 and base station 105 are described.
[0110] In this scenario, the base station 105-c and the UE 115-c may communicate using a downlink link 405 and an uplink link 410. The base station 105-c may transmit a DCI 415 to the UE 115-c on the downlink link 405 to schedule transmissions. For example, the DCI 415 may schedule resources for the base station 105-c to repeat across CC shared channels on the downlink link 405 to the UE 115-c for downlink communications. Alternatively, the DCI 415 may schedule the UE 115-c to transmit to the base station 105-c on the uplink link 410 using the cross-CC shared channel repetition for uplink communications. In some cases, the cross-CC shared channel repetition may be used to carry uplink or downlink data, which may be transmitted on an uplink data channel (e.g., PUSCH) or a downlink data channel (e.g., PDSCH) scheduled by the DCI 415.
[0111] In some cases, such as Figure 4 As explained in , a single DCI transmission may schedule multiple transmissions or repetitions of a transport block on different CCs. In such a case, DCI 415 may schedule PUSCH repetitions on multiple different CCs. For example, DCI 415 may schedule a first repetition 445 on four symbols on a first CC 420, a second repetition 450 on two symbols on a second CC 425, and a third repetition 455 on four symbols on a third CC 430. Here, the second CC 425 is configured with a different SCS than the first CC 420 and the third CC 430, as shown, the different SCS corresponding to different symbol durations of the symbols of the second CC 425 compared to the symbols of the first CC 420 and the third CC 430. In the illustrated example, the first repetition 445 is located within the first time slot 435, and the second repetition 450 and the third repetition 455 are located relative to each other within the second time slot 440, which is adjacent to the first time slot 435, such that the second repetition 450 at least partially overlaps with the third repetition 455.
[0112] In some cases, when each repetition occurs on a separate CC, the SLIV indicated by a single DCI may represent the number of symbols and the nominal transmission time on a reference SCS. In such a case, the reference SCS may be determined using the methods described herein. In some examples, each of the multiple CCs may be transmitted using the same absolute time, i.e., the number of symbols for each CC will vary based on the symbol duration and SCS of the corresponding CC. That is, the repetitions scheduled on each CC may span the same duration in time, but due to the varying SCS configured for the CC, the repetitions may be scheduled on a different number of symbols for one or more of the CCs.
[0113] In some cases, the SLIV indicated by a single DCI (such as DCI 415) may represent the number of symbols used for data transmission, which may be the same across each CC in the multiple CCs. In such an example, even if the number of symbols for each CC is the same, the absolute transmission time for each CC may be different.
[0114] In some cases, when repetitions on different CCs are scheduled by a single DCI, the transport block size may be determined based on a nominal length and nominal REs for transmission, which may be indicated by the DCI 415. Furthermore, in some cases, the transport block size may be determined based on nominal REs that are common across all CCs. In such cases, the different repetitions are typically not self-decodable.
[0115] Figure 5An example of a process flow 500 for supporting cross-CC shared channel duplication according to aspects of the present disclosure is illustrated. In some examples, the process flow 500 can implement aspects of the wireless communication system 100, 200, 300, or 400. The process flow 500 may include a base station 105-d and a UE 115-d, which may be as described with reference to Figure 1 , 2 , 3 and 4 describe examples of UE 115 and base station 105.
[0116] When transmitting the DCI, the base station 105 - d may communicate with the UE 115 - d to facilitate cross-CC shared channel repetition.
[0117] At 505, the base station 105-d may identify a set of CCs supported by the UE 115-d for communicating with the base station 105-d. In some cases, the UE 115-d may identify the set of CCs supported by the UE 115-d for communicating with the base station 105-d. In some cases, the set of CCs supported by the UE 115-d may include a first CC and a second CC. In some cases, the UE 115-d may support multiple CCs for communicating with the base station 105-d.
[0118] At 510, UE 115-d may receive a downlink control message from base station 105-d. In some cases, the downlink control message may schedule multiple repetitions of a transport block for UE 115-d. In some cases, a first repetition of the multiple repetitions may be scheduled on a first CC in the set of CCs. In some cases, a second repetition of the multiple repetitions may be scheduled on a second CC in the set of CCs.
[0119] In some cases, one of the UE 115-d or the base station 105-d may receive a reference SCS configuration for each CC in a subset of the CC set via RRC signaling. In such a case, the one of the UE 115-d or the base station 105-d may determine the number of symbols between the transmission of the downlink control message and the first repetition via the first CC based at least in part on the reference SCS configuration. In some cases, the one of the UE 115-d or the base station 105-d may determine the number of symbols between the reception of the downlink control message and the first repetition. In some such cases, the number of symbols is based at least in part on a minimum or maximum slot format indicator of the subset, an indication within the downlink control message, the SCS of the first CC, or an SCS associated with the downlink control message.
[0120] At 515, UE 115-d may determine a first number of symbols between the downlink control message and the transmission of the first repetition. In some cases, UE 115-d may determine the first number of symbols between the downlink control message and the reception of the first repetition. In some cases, UE 115-d may determine the first number of symbols between the downlink control message and the transmission or reception of the first repetition via the first CC based at least in part on the SCS of the first CC.
[0121] At 520, UE 115-d may determine a second number of symbols between the downlink control message and the transmission of the second repetition. In some cases, UE 115-d may determine the second number of symbols between the downlink control message and the reception of the second repetition. In some cases, UE 115-d may determine the second number of symbols between the downlink control message and the transmission or reception of the second repetition via the first CC based at least in part on the SCS of the second CC.
[0122] In some cases, one of the UE 115-d or the base station 105-d may determine a first time slot for a first repetition of transmission or reception via the first CC based at least in part on the SCS of the first CC. In such a case, the one of the UE 115-d or the base station 105-d may determine a second time slot for a second repetition of transmission or reception via the second CC based at least in part on the SCS of the second CC.
[0123] In some examples, one of the UE 115-d or the base station 105-d may receive a reference SCS configuration for each CC in the subset of the CC set via RRC signaling. In such examples, the one of the UE 115-d or the base station 105-d may determine a starting symbol and a time length for a first repeated transmission or reception via the first CC based at least in part on the reference SCS configuration. In these such examples, the starting symbol and the time length may be the same for the first CC and the second CC.
[0124] In some cases, one of the base station 105-d or the UE 115-d may determine the number of symbols for the first repetition of transmission or reception via the first CC. In such an example, the number of symbols may be the same for the first CC and the second CC. In some examples, one of the base station 105-d or the UE 115-d may determine the transport block size for the first repetition of transmission or reception via the first CC based at least in part on the nominal time length and the nominal resource element set indicated by the downlink control message. In such an example, the transport block size may be the same for the first CC and the second CC.
[0125] In some cases, one of the base station 105-d or the UE 115-d may determine a transport block size for a first repeated transmission or reception via the first CC based at least in part on nominal resource element sets for the first CC and the second CC.
[0126] At 525, the base station 105-d may receive an indication of a scheduled transport block. In some cases, the indication received by the base station 105-d may indicate that multiple repetitions of the transport block are scheduled via the first and second CCs. In some cases, the multiple repetitions of the transport block may be scheduled via the first and second CCs according to one or both of an FDM scheme or a TDM scheme. In some cases, the indication may be received via RRC signaling, MAC-CE, or DCI.
[0127] In some examples, one of the base station 105-d or the UE 115-d may receive an indication of a subset of the CC set that may be used for multiple repetitions of a transport block. In some cases, the subset may include at least a first CC and a second CC. In some cases, the indication of the subset may be received by the base station 105-d via RRC signaling, MAC-CE, or DCI. In some cases, the indication of the subset includes a set of carrier indices corresponding to the subset of the CC set.
[0128] In some cases, one of the base station 105-d or the UE 115-d may receive an indication of at least one CC in the set of CCs from which multiple repetitions to be used for a transport block are discarded. In some cases, one of the base station 105-d or the UE 115-d may receive an indication of a starting CC for multiple repetitions of a transport block. In some examples, one of the UE 115-d or the base station 105-d may transmit feedback for a subset of CCs, and the UE 115-d or the base station 105-d may receive an indication of a starting CC for multiple repetitions of a transport block based at least in part on the feedback. In such an example, the subset may include a starting CC, and the feedback may indicate ACK / NACK feedback or SINR for each CC in the subset.
[0129] In some cases, one of the base station 105-d or the UE 115-d may receive a reference SCS configuration for each CC in a subset of the CC set via RRC signaling. In such a case, the one of the base station 105-d or the UE 115-d may determine a time slot for a first repeated transmission or reception via a first CC based at least in part on the reference SCS configuration.
[0130] At 530, UE 115-d may transmit a first repetition via the first CC, and at 535, UE 115-d may transmit a second repetition via the second CC.
[0131] Figure 6 A block diagram 600 of a device 605 supporting cross-carrier shared channel repetition according to aspects of the present disclosure is shown. The device 605 may be an example of aspects of a UE 115 as described herein. The device 605 may include a receiver 610, a communication manager 615, and a transmitter 620. The device 605 may also include a processor. Each of these components may be in communication with each other (e.g., via one or more buses).
[0132] The receiver 610 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to cross-carrier shared channel repetition, etc.). The information may be passed to other components of the device 605. The receiver 610 may be a reference Fig. 9 Examples of aspects of the described transceiver 920. The receiver 610 may utilize a single antenna or a collection of antennas.
[0133] The communication manager 615 may identify a CC set supported by the UE for communicating with the base station, receive a downlink control message from the base station, the downlink control message scheduling multiple repetitions of a transport block for the UE, wherein a first repetition of the multiple repetitions is scheduled on a first CC of the CC set, a second repetition of the multiple repetitions is scheduled on a second CC of the CC set, and transmit or receive the first repetition via the first CC, and transmit or receive the second repetition via the second CC. The communication manager 615 may be an example of aspects of the communication manager 910 described herein.
[0134] The communication manager 615 or its subcomponents may be implemented in hardware, in code (e.g., software or firmware) executed by a processor, or any combination thereof. If implemented in code executed by a processor, the functions of the communication manager 615 or its subcomponents may be performed by a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device designed to perform the functions described in the present disclosure, discrete gate or transistor logic, discrete hardware components, or any combination thereof.
[0135] The communication manager 615 or its subcomponents may be physically located at various locations, including being distributed such that portions of functionality are implemented by one or more physical components at different physical locations. In some examples, according to various aspects of the present disclosure, the communication manager 615 or its subcomponents may be separate and distinct components. In some examples, according to various aspects of the present disclosure, the communication manager 615 or its subcomponents may be combined with one or more other hardware components, including but not limited to input / output (I / O) components, a transceiver, a network server, another computing device, one or more other components described in the present disclosure, or a combination thereof.
[0136] The transmitter 620 can transmit signals generated by other components of the device 605. In some examples, the transmitter 620 can be co-located with the receiver 610 in a transceiver module. For example, the transmitter 620 can be a reference Fig. 9 Examples of aspects of the described transceiver 920. The transmitter 620 may utilize a single antenna or a collection of antennas.
[0137] The communication manager 615 as described herein may be implemented to achieve one or more potential advantages. One implementation may provide reduced signaling overhead when scheduling communications across multiple CCs. For example, the device 605 may receive a DCI that schedules uplink or downlink communications on multiple CCs. By using a single DCI to schedule communications for multiple CCs, signaling overhead and signal monitoring performed by the device 604 may be reduced.
[0138] By utilizing such techniques, a processor of UE 115 (e.g., a processor controlling receiver 610, communication manager 615, transmitter 620, etc.) can reduce processing resources used for communication. For example, when a single DCI scheduled across multiple CCs is received, the processor can refrain from monitoring one or more CCs for additional control messages corresponding to those CCs. Thus, device 605 can reduce power consumption and increase battery life.
[0139] Figure 7 A block diagram 700 of a device 705 supporting cross-carrier shared channel repetition according to aspects of the present disclosure is shown. The device 705 may be an example of aspects of the device 605 or UE 115 as described herein. The device 705 may include a receiver 710, a communication manager 715, and a transmitter 735. The device 705 may also include a processor. Each of these components may be in communication with each other (e.g., via one or more buses).
[0140] The receiver 710 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to cross-carrier shared channel repetition, etc.). The information may be passed to other components of the device 705. The receiver 710 may be a reference Fig. 9 Examples of aspects of the described transceiver 920. The receiver 710 may utilize a single antenna or a collection of antennas.
[0141] The communication manager 715 may be an example of aspects of the communication manager 615 as described herein. The communication manager 715 may include a CC manager 720, a downlink control receiver 725, and a repeat communication component 730. The communication manager 715 may be an example of aspects of the communication manager 910 as described herein.
[0142] CC manager 720 may identify a set of CCs supported by the UE for communicating with a base station.
[0143] The downlink control receiver 725 can receive a downlink control message from a base station, which downlink control message schedules multiple repetitions of a transmission block for the UE, wherein a first repetition of the multiple repetitions is scheduled on a first CC in the CC set, and a second repetition of the multiple repetitions is scheduled on a second CC in the CC set.
[0144] The repetition communicating component 730 can transmit or receive the first repetition via the first CC and transmit or receive the second repetition via the second CC.
[0145] The transmitter 735 can transmit signals generated by other components of the device 705. In some examples, the transmitter 735 can be co-located with the receiver 710 in a transceiver module. For example, the transmitter 735 can be a reference Fig. 9 Examples of aspects of the described transceiver 920. The transmitter 735 may utilize a single antenna or a collection of antennas.
[0146] Figure 8 A block diagram 800 of a communication manager 805 supporting cross-carrier shared channel repetition in accordance with aspects of the present disclosure is shown. The communication manager 805 may be an example of aspects of the communication manager 615, the communication manager 715, or the communication manager 910 described herein. The communication manager 805 may include a CC manager 810, a downlink control receiver 815, a repetition communication component 820, an indication receiver 825, a feedback transmitter 830, a configuration receiver 835, a symbol component 840, a slot manager 845, a SLIV module 850, and a block size manager 855. Each of these modules may communicate directly or indirectly with each other (e.g., via one or more buses).
[0147] CC manager 810 may identify a set of CCs supported by the UE for communicating with a base station.
[0148] The downlink control receiver 815 can receive a downlink control message from a base station, which downlink control message schedules multiple repetitions of a transmission block for the UE, wherein a first repetition of the multiple repetitions is scheduled on a first CC in the CC set, and a second repetition of the multiple repetitions is scheduled on a second CC in the CC set.
[0149] Repetition communicating component 820 can transmit or receive the first repetition via the first CC and transmit or receive the second repetition via the second CC.
[0150] The indication receiver 825 may receive an indication that a plurality of repetitions of a transport block are scheduled via the first and second CCs according to one or both of an FDM scheme or a TDM scheme.
[0151] In some examples, the indication receiver 825 may receive an indication of a subset of the CC set that may be used for multiple repetitions of a transport block, the subset including at least a first CC and a second CC, wherein the indication is received via RRC signaling, MAC-CE, or DCI.
[0152] In some examples, the indication receiver 825 may receive an indication of at least one CC in the set of CCs to be dropped for multiple repetitions of a transport block.
[0153] In some examples, indication receiver 825 may receive an indication of a starting CC for multiple repetitions of a transport block.
[0154] In some examples, an indication of a starting CC for a plurality of repetitions of a transport block is received based on the feedback, wherein the subset includes the starting CC.
[0155] In some cases, the indication is received via RRC signaling, MAC-CE, or DCI.
[0156] In some cases, the indication includes a set of carrier indices corresponding to the subset of the set of CCs.
[0157] Feedback transmitter 830 may transmit feedback for a subset of the set of CCs.
[0158] In some cases, the feedback indicates ACK / NACK feedback or SINR for each CC in the subset.
[0159] The configuration receiver 835 may receive a reference SCS configuration for each CC in the subset of the CC set via RRC signaling.
[0160] The symbol component 840 may determine a number of symbols between a downlink control message and a transmission or reception of a first repetition via a first CC based on a reference SCS configuration.
[0161] In some examples, the codeword component 840 can determine a first codeword number between a downlink control message and a first repetition transmission or reception via the first CC based on the SCS of the first CC.
[0162] In some examples, the codeword component 840 can determine a second codeword number between the downlink control message and the second repeated transmission or reception via the second CC based on the SCS of the second CC.
[0163] In some examples, the symbol component 840 can determine a number of symbols for transmission or reception of a first repetition via a first CC, where the number of symbols is the same for the first CC and the second CC.
[0164] In some cases, the number of symbols is based on a minimum or maximum slot format indicator for the subset, an indication within a downlink control message, the SCS of the first CC, or an SCS associated with a downlink control message.
[0165] The time slot manager 845 may determine a time slot for a first repeated transmission or reception via a first CC based on a reference SCS configuration.
[0166] In some examples, the timeslot manager 845 may determine a first timeslot for a first repeated transmission or reception via the first CC based on the SCS of the first CC.
[0167] In some examples, the timeslot manager 845 may determine a second timeslot for a second repeated transmission or reception via the second CC based on the SCS of the second CC.
[0168] The SLIV module 850 may determine a starting symbol and a time length for transmission or reception of a first repetition via a first CC based on a reference SCS configuration, wherein the starting symbol and the time length are the same for the first CC and the second CC.
[0169] The block size manager 855 may determine a transport block size for a first repeated transmission or reception via the first CC based on a nominal time length and a nominal resource element set indicated by a downlink control message, wherein the transport block size is the same for the first CC and the second CC.
[0170] In some examples, the block size manager 855 may determine a transport block size for a first repetition of transmission or reception via the first CC based on a nominal resource element set for the first CC and the second CC.
[0171] Fig. 9 A diagram of a system 900 including a device 905 supporting cross-carrier shared channel repetition according to various aspects of the present disclosure is shown. The device 905 may be an example of a device 605, a device 705, or a UE 115 as described herein or include components of the above devices. The device 905 may include components for two-way voice and data communications, including components for transmitting and receiving communications, including a communication manager 910, an I / O controller 915, a transceiver 920, an antenna 925, a memory 930, and a processor 940. These components may be in electronic communication via one or more buses (e.g., a bus 945).
[0172] The communication manager 910 can identify a CC set supported by the UE for communicating with the base station, receive a downlink control message from the base station, and schedule multiple repetitions of a transmission block for the UE, wherein a first repetition of the multiple repetitions is scheduled on a first CC of the CC set, a second repetition of the multiple repetitions is scheduled on a second CC of the CC set, and the first repetition is transmitted or received via the first CC, and the second repetition is transmitted or received via the second CC.
[0173] I / O controller 915 can manage input and output signals of device 905. I / O controller 915 can also manage peripheral devices that are not integrated into device 905. In some cases, I / O controller 915 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 915 can utilize an operating system, such as Or another known operating system. In other cases, I / O controller 915 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 915 may be implemented as part of a processor. In some cases, a user may interact with device 905 via I / O controller 915 or via hardware components controlled by I / O controller 915.
[0174] The transceiver 920 may communicate bidirectionally via one or more antennas, wired or wireless links, as described herein. For example, the transceiver 920 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 920 may also include a modem to modulate packets and provide the modulated packets to an antenna for transmission, and demodulate packets received from an antenna.
[0175] In some cases, a wireless device may include a single antenna 925. However, in some cases, the device may have more than one antenna 925, which may be capable of transmitting or receiving multiple wireless transmissions concurrently.
[0176] The memory 930 may include random access memory (RAM) and read-only memory (ROM). The memory 930 may store computer-readable, computer-executable code 935 including instructions that, when executed, cause the processor to perform the various functions described herein. In some cases, the memory 930 may include, among other things, a basic I / O system (BIOS) that may control basic hardware or software operations, such as interaction with peripheral components or devices.
[0177] The processor 940 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a central processing unit (CPU), a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 940 may be configured to operate a memory array using a memory controller. In other cases, the memory controller may be integrated into the processor 940. The processor 940 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 930) so that the device 905 performs various functions (e.g., functions or tasks that support cross-carrier shared channel repetition).
[0178] The code 935 may include instructions for implementing various aspects of the present disclosure, including instructions for supporting wireless communications. The code 935 may be stored in a non-transitory computer-readable medium, such as a system memory or other type of memory. In some cases, the code 935 may not be directly executed by the processor 940, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein.
[0179] Fig.10 A block diagram 1000 of a device 1005 supporting cross-carrier shared channel repetition according to aspects of the present disclosure is shown. The device 1005 may be an example of aspects of a base station 105 as described herein. The device 1005 may include a receiver 1010, a communication manager 1015, and a transmitter 1020. The device 1005 may also include a processor. Each of these components may be in communication with each other (e.g., via one or more buses).
[0180] The receiver 1010 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to cross-carrier shared channel repetition, etc.). The information may be passed to other components of the device 1005. The receiver 1010 may be a reference Fig.13 Examples of various aspects of the described transceiver 1320. The receiver 1010 may utilize a single antenna or a collection of antennas.
[0181] The communication manager 1015 may identify a CC set supported by the UE for communicating with the base station, transmit a downlink control message to the UE, the downlink control message scheduling multiple repetitions of a transport block for the UE, wherein a first repetition of the multiple repetitions is scheduled on a first CC of the CC set, and a second repetition of the multiple repetitions is scheduled on a second CC of the CC set, and transmit or receive the first repetition via the first CC, and transmit or receive the second repetition via the second CC. The communication manager 1015 may be an example of aspects of the communication manager 1310 described herein.
[0182] The communication manager 1015 or its subcomponents may be implemented in hardware, in code (e.g., software or firmware) executed by a processor, or any combination thereof. If implemented in code executed by a processor, the functions of the communication manager 1015 or its subcomponents may be performed by a general purpose processor, DSP, ASIC, FPGA or other programmable logic device designed to perform the functions described in this disclosure, discrete gate or transistor logic, discrete hardware components, or any combination thereof.
[0183] The communication manager 1015 or its subcomponents may be physically located at various locations, including being distributed such that portions of functionality are implemented by one or more physical components at different physical locations. In some examples, according to various aspects of the present disclosure, the communication manager 1015 or its subcomponents may be separate and distinct components. In some examples, according to various aspects of the present disclosure, the communication manager 1015 or its subcomponents may be combined with one or more other hardware components (including, but not limited to, I / O components, a transceiver, a network server, another computing device, one or more other components described in the present disclosure, or a combination thereof).
[0184] The transmitter 1020 may transmit signals generated by other components of the device 1005. In some examples, the transmitter 1020 may be co-located with the receiver 1010 in a transceiver module. For example, the transmitter 1020 may be a reference Fig.13 Examples of aspects of the described transceiver 1320. The transmitter 1020 may utilize a single antenna or a collection of antennas.
[0185] Fig.11 A block diagram 1100 of a device 1105 supporting cross-carrier shared channel repetition according to aspects of the present disclosure is shown. The device 1105 may be an example of aspects of a device 1105 or base station 105 as described herein. The device 1105 may include a receiver 1110, a communication manager 1115, and a transmitter 1135. The device 1105 may also include a processor. Each of these components may be in communication with each other (e.g., via one or more buses).
[0186] The receiver 1110 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to cross-carrier shared channel repetition, etc.). The information may be passed to other components of the device 1105. The receiver 1110 may be a reference Fig.13 Examples of aspects of the described transceiver 1320. The receiver 1110 may utilize a single antenna or a collection of antennas.
[0187] The communication manager 1115 may be an example of aspects of the communication manager 1015 as described herein. The communication manager 1115 may include a CC module 1120, a downlink control transmitter 1125, and a repetition manager 1130. The communication manager 1115 may be an example of aspects of the communication manager 1310 described herein.
[0188] The CC module 1120 may identify a set of CCs supported by the UE for communicating with a base station.
[0189] The downlink control transmitter 1125 can transmit a downlink control message to the UE, which schedules multiple repetitions of a transmission block for the UE, wherein a first repetition of the multiple repetitions is scheduled on a first CC in the CC set, and a second repetition of the multiple repetitions is scheduled on a second CC in the CC set.
[0190] The repetition manager 1130 may transmit or receive the first repetition via the first CC and transmit or receive the second repetition via the second CC.
[0191] The transmitter 1135 may transmit signals generated by other components of the device 1105. In some examples, the transmitter 1135 may be co-located with the receiver 1110 in a transceiver module. Fig.13 Examples of various aspects of the described transceiver 1320. The transmitter 1135 may utilize a single antenna or a collection of antennas.
[0192] Fig.12 A block diagram 1200 of a communication manager 1205 supporting cross-carrier shared channel repetition in accordance with aspects of the present disclosure is shown. The communication manager 1205 may be an example of aspects of the communication manager 1015, the communication manager 1115, or the communication manager 1310 described herein. The communication manager 1205 may include a CC module 1210, a downlink control transmitter 1215, a repetition manager 1220, an indication transmitter 1225, a feedback receiver 1230, a configuration transmitter 1235, and a scheduling manager 1240. Each of these modules may communicate directly or indirectly with each other (e.g., via one or more buses).
[0193] The CC module 1210 may identify a CC set supported by the UE for communicating with a base station.
[0194] The downlink control transmitter 1215 can transmit a downlink control message to the UE, which schedules multiple repetitions of a transmission block for the UE, wherein a first repetition of the multiple repetitions is scheduled on a first CC in the CC set, and a second repetition of the multiple repetitions is scheduled on a second CC in the CC set.
[0195] The repetition manager 1220 may transmit or receive the first repetition via the first CC and transmit or receive the second repetition via the second CC.
[0196] The indication transmitter 1225 may transmit an indication that a plurality of repetitions of a transport block are scheduled via the first and second CCs according to one or both of an FDM scheme or a TDM scheme.
[0197] In some examples, the indication transmitter 1225 may transmit an indication of a subset of the CC set that can be used for multiple repetitions of a transport block, the subset including at least a first CC and a second CC, wherein the indication is transmitted via RRC signaling, MAC-CE, or DCI.
[0198] In some examples, indication transmitter 1225 may transmit an indication of at least one CC in the set of CCs to be dropped for multiple repetitions of a transport block.
[0199] In some examples, indication transmitter 1225 may transmit an indication of a starting CC for multiple repetitions of a transport block.
[0200] In some examples, an indication of a starting CC for a plurality of repetitions of a transport block is transmitted based on the feedback, wherein the subset includes the starting CC.
[0201] In some cases, the indication is transmitted via RRC signaling, MAC-CE or DCI.
[0202] In some cases, the indication includes a set of carrier indices corresponding to the subset of the set of CCs.
[0203] Feedback receiver 1230 may receive feedback from the UE for a subset of the CC set.
[0204] In some cases, the feedback indicates ACK / NACK feedback or SINR for each CC in the subset.
[0205] The configuration transmitter 1235 may transmit a reference SCS configuration for each CC in the subset of the CC set via RRC signaling.
[0206] The scheduling manager 1240 may schedule transmission or reception of a first repetition via a first CC based on a reference SCS configuration.
[0207] In some examples, schedule manager 1240 may schedule transmission or reception of a second repetition via a second CC based on a reference SCS configuration.
[0208] In some examples, schedule manager 1240 may schedule a first repetition of transmission or reception via the first CC based on a first SCS configuration associated with the first CC.
[0209] In some examples, schedule manager 1240 may schedule second repeated transmission or reception via the second CC based on a second SCS configuration associated with the second CC.
[0210] In some examples, the scheduling manager 1240 may schedule the transmission or reception of a first repetition via the first CC based on an SCS configuration associated with the downlink control message.
[0211] Fig.13 A diagram of a system 1300 including a device 1305 supporting cross-carrier shared channel repetition according to aspects of the present disclosure is shown. The device 1305 may be an example of or include components of the device 1105, device 1205, or base station 105 as described herein. The device 1305 may include components for two-way voice and data communications, including components for transmitting and receiving communications, including a communication manager 1310, a network communication manager 1315, a transceiver 1320, an antenna 1325, a memory 1330, a processor 1340, and an inter-station communication manager 1345. These components may be in electronic communication via one or more buses (e.g., bus 1350).
[0212] The communication manager 1310 can identify a CC set supported by the UE for communicating with the base station, transmit a downlink control message to the UE, wherein the downlink control message schedules multiple repetitions of a transmission block for the UE, wherein a first repetition of the multiple repetitions is scheduled on a first CC of the CC set, and a second repetition of the multiple repetitions is scheduled on a second CC of the CC set, and the first repetition is transmitted or received via the first CC, and the second repetition is transmitted or received via the second CC.
[0213] The network communications manager 1315 may manage communications with the core network (eg, via one or more wired backhaul links). For example, the network communications manager 1315 may manage the delivery of data communications for client devices, such as one or more UEs 115.
[0214] The transceiver 1320 may communicate bidirectionally via one or more antennas, wired or wireless links, as described herein. For example, the transceiver 1320 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 1320 may also include a modem to modulate packets and provide the modulated packets to an antenna for transmission, and demodulate packets received from an antenna.
[0215] In some cases, a wireless device may include a single antenna 1325. However, in some cases, the device may have more than one antenna 1325, which may be capable of transmitting or receiving multiple wireless transmissions concurrently.
[0216] Memory 1330 may include RAM, ROM, or a combination thereof. Memory 1330 may store computer readable code 1335 including instructions that, when executed by a processor (e.g., processor 1340), cause the device to perform various functions described herein. In some cases, memory 1330 may include, among other things, a BIOS that may control basic hardware or software operations, such as interaction with peripheral components or devices.
[0217] Processor 1340 may include an intelligent hardware device (e.g., a general purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, processor 1340 may be configured to operate a memory array using a memory controller. In some cases, the memory controller may be integrated into processor 1340. Processor 1340 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1330) to cause device 1305 to perform various functions (e.g., functions or tasks that support cross-carrier shared channel repetition).
[0218] The inter-site communication manager 1345 may manage communications with other base stations 105 and may include a controller or scheduler for controlling communications with UE 115 in cooperation with other base stations 105. For example, the inter-site communication manager 1345 may coordinate scheduling of transmissions to UE 115 for various interference mitigation techniques such as beamforming or joint transmission. In some examples, the inter-site communication manager 1345 may provide an X2 interface within an LTE / LTE-A wireless communication network technology to provide communications between base stations 105.
[0219] The code 1335 may include instructions for implementing various aspects of the present disclosure, including instructions for supporting wireless communications. The code 1335 may be stored in a non-transitory computer-readable medium, such as a system memory or other type of memory. In some cases, the code 1335 may not be directly executed by the processor 1340, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein.
[0220] Fig.14 1400 for supporting cross-carrier shared channel duplication according to aspects of the present disclosure. The operations of the method 1400 may be implemented by the UE 115 or its components as described herein. For example, the operations of the method 1400 may be implemented by the UE 115 or its components as described herein. Figures 6 to 9 In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the functions described herein. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the functions described herein.
[0221] At 1405, the UE may identify a set of CCs supported by the UE for communicating with the base station. The operations of 1405 may be performed according to the methods described herein. In some examples, aspects of the operations of 1405 may be performed as described in reference to Figures 6 to 9 The CC manager described is executed.
[0222] At 1410, the UE may receive a downlink control message from a base station, the downlink control message scheduling multiple repetitions of a transport block for the UE, wherein a first repetition of the multiple repetitions is scheduled on a first CC in the CC set, and a second repetition of the multiple repetitions is scheduled on a second CC in the CC set. The operations of 1410 may be performed according to the methods described herein. In some examples, aspects of the operations of 1410 may be performed as described with reference to Figures 6 to 9 The described downlink control is performed by a receiver.
[0223] At 1415, the UE may transmit or receive the first repetition via the first CC and transmit or receive the second repetition via the second CC. The operations of 1415 may be performed according to the methods described herein. In some examples, aspects of the operations of 1415 may be performed as described in reference to Figures 6 to 9 The described repetitive communication components are performed.
[0224] Fig.15 1 is a flow chart illustrating a method 1500 for supporting cross-carrier shared channel duplication according to aspects of the present disclosure. The operations of the method 1500 may be implemented by a UE 115 or a component thereof as described herein. For example, the operations of the method 1500 may be implemented by a UE 115 or a component thereof as described herein. Figures 6 to 9In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the functions described herein. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the functions described herein.
[0225] At 1505, the UE may identify a set of CCs supported by the UE for communicating with a base station. The operations of 1505 may be performed according to the methods described herein. In some examples, aspects of the operations of 1505 may be performed as described in reference to Figures 6 to 9 The CC manager described is executed.
[0226] At 1510, the UE may receive an indication of at least one CC in the CC set to be dropped for multiple repetitions of a transport block. The operations of 1510 may be performed according to the methods described herein. In some examples, aspects of the operations of 1510 may be performed as described with reference to Figures 6 to 9 The described instructions are for the receiver to execute.
[0227] At 1515, the UE may receive a downlink control message from the base station, the downlink control message scheduling multiple repetitions of the transport block for the UE, wherein a first repetition of the multiple repetitions is scheduled on a first CC in the CC set, and a second repetition of the multiple repetitions is scheduled on a second CC in the CC set. The operations of 1515 may be performed according to the methods described herein. In some examples, aspects of the operations of 1515 may be performed as described with reference to Figures 6 to 9 The described downlink control is performed by a receiver.
[0228] At 1520, the UE may transmit or receive the first repetition via the first CC and transmit or receive the second repetition via the second CC. The operations of 1520 may be performed according to the methods described herein. In some examples, aspects of the operations of 1520 may be performed as described in reference to Figures 6 to 9 The described repetitive communication components are performed.
[0229] Fig.16 1 is a flow chart illustrating a method 1600 for supporting cross-carrier shared channel duplication according to aspects of the present disclosure. The operations of the method 1600 may be implemented by a UE 115 or a component thereof as described herein. For example, the operations of the method 1600 may be implemented by a UE 115 or a component thereof as described herein. Figures 6 to 9 The base station communication manager described herein may be used to perform. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the functions described herein. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the functions described herein.
[0230] At 1605, the UE may identify a set of CCs supported by the UE for communicating with the base station. The operations of 1605 may be performed according to the methods described herein. In some examples, aspects of the operations of 1605 may be performed as described in reference to Figures 6 to 9 The CC manager described is executed.
[0231] At 1610, the UE may receive an indication of a starting CC for a plurality of repetitions of a transport block. The operations of 1610 may be performed according to the methods described herein. In some examples, aspects of the operations of 1610 may be performed as described with reference to Figures 6 to 9 The described instructions are for the receiver to execute.
[0232] At 1615, the UE may receive a downlink control message from the base station, the downlink control message scheduling multiple repetitions of the transport block for the UE, wherein a first repetition of the multiple repetitions is scheduled on a first CC in the CC set, and a second repetition of the multiple repetitions is scheduled on a second CC in the CC set. The operations of 1615 may be performed according to the methods described herein. In some examples, aspects of the operations of 1615 may be performed as described with reference to Figures 6 to 9 The described downlink control is performed by a receiver.
[0233] At 1620, the UE may transmit or receive the first repetition via the first CC and transmit or receive the second repetition via the second CC. The operations of 1620 may be performed according to the methods described herein. In some examples, aspects of the operations of 1620 may be performed as described in reference to Figures 6 to 9 The described repetitive communication components are performed.
[0234] Fig.17 1 is a flow chart illustrating a method 1700 for supporting cross-carrier shared channel duplication according to aspects of the present disclosure. The operations of the method 1700 may be implemented by a UE 115 or a component thereof as described herein. For example, the operations of the method 1700 may be implemented by a UE 115 or a component thereof as described herein. Figures 6 to 9 In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the functions described herein. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the functions described herein.
[0235] At 1705, the UE may identify a set of CCs supported by the UE for communicating with a base station. The operations of 1705 may be performed according to the methods described herein. In some examples, aspects of the operations of 1705 may be performed as described in reference to Figures 6 to 9 The CC manager described is executed.
[0236] At 1710, the UE may transmit feedback for a subset of the CC set. The operations of 1710 may be performed according to the methods described herein. In some examples, aspects of the operations of 1710 may be performed as described with reference to Figures 6 to 9 The feedback transmitter described is implemented.
[0237] At 1715, the UE may receive an indication of a starting CC for a plurality of repetitions of a transport block based on the feedback, wherein the subset includes the starting CC. The operations of 1715 may be performed according to the methods described herein. In some examples, aspects of the operations of 1715 may be performed as described with reference to Figures 6 to 9 The described instructions are for the receiver to execute.
[0238] At 1720, the UE may receive a downlink control message from a base station, the downlink control message scheduling multiple repetitions of a transport block for the UE, wherein a first repetition of the multiple repetitions is scheduled on a first CC in the CC set, and a second repetition of the multiple repetitions is scheduled on a second CC in the CC set. The operations of 1720 may be performed according to the methods described herein. In some examples, aspects of the operations of 1720 may be performed as described with reference to Figures 6 to 9 The described downlink control is performed by a receiver.
[0239] At 1725, the UE may transmit or receive the first repetition via the first CC and transmit or receive the second repetition via the second CC. The operations of 1725 may be performed according to the methods described herein. In some examples, aspects of the operations of 1725 may be performed as described in reference to Figures 6 to 9 The described repeated communication components are performed.
[0240] Fig.18 1 is a flow chart illustrating a method 1800 for supporting cross-carrier shared channel repetition according to aspects of the present disclosure. The operations of the method 1800 may be implemented by a base station 105 or components thereof as described herein. For example, the operations of the method 1800 may be implemented by a base station 105 or components thereof as described herein. Figures 10 to 13 In some examples, a base station may execute an instruction set to control functional elements of the base station to perform the functions described herein. Additionally or alternatively, a base station may use dedicated hardware to perform various aspects of the functions described herein.
[0241] At 1805, the base station may identify a set of CCs supported by the UE for communicating with the base station. The operations of 1805 may be performed according to the methods described herein. In some examples, aspects of the operations of 1805 may be performed as described with reference to Figures 10 to 13 The CC module described is used to perform.
[0242] At 1810, the base station may transmit a downlink control message to the UE, the downlink control message scheduling multiple repetitions of a transport block for the UE, wherein a first repetition of the multiple repetitions is scheduled on a first CC in the CC set, and a second repetition of the multiple repetitions is scheduled on a second CC in the CC set. The operations of 1810 may be performed according to the methods described herein. In some examples, aspects of the operations of 1810 may be performed as described in reference to Figures 10 to 13 The described downlink control transmitter is performed.
[0243] At 1815, the base station may transmit or receive the first repetition via the first CC and transmit or receive the second repetition via the second CC. The operations of 1815 may be performed according to the methods described herein. In some examples, aspects of the operations of 1815 may be performed as described in reference to Figures 10 to 13 The described duplication manager is implemented.
[0244] Fig.19 1 is a flow chart illustrating a method 1900 for supporting cross-carrier shared channel repetition according to aspects of the present disclosure. The operations of the method 1900 may be implemented by a base station 105 or components thereof as described herein. For example, the operations of the method 1900 may be implemented by a base station 105 or components thereof as described herein. Figures 10 to 13 In some examples, a base station may execute an instruction set to control functional elements of the base station to perform the functions described herein. Additionally or alternatively, a base station may use dedicated hardware to perform various aspects of the functions described herein.
[0245] At 1905, the base station may identify a set of CCs supported by the UE for communicating with the base station. The operations of 1905 may be performed according to the methods described herein. In some examples, aspects of the operations of 1905 may be performed as described with reference to Figures 10 to 13 The CC module described is used to perform.
[0246] At 1910, the base station may transmit an indication that multiple repetitions of a transport block are scheduled via the first and second CCs according to one or both of an FDM scheme or a TDM scheme. The operations of 1910 may be performed according to the methods described herein. In some examples, aspects of the operations of 1910 may be performed as described with reference to Figures 10 to 13 The description instructs the transmitter to perform.
[0247] At 1915, the base station may transmit a downlink control message to the UE, the downlink control message scheduling multiple repetitions of the transport block for the UE, wherein a first repetition of the multiple repetitions is scheduled on a first CC in the CC set, and a second repetition of the multiple repetitions is scheduled on a second CC in the CC set. The operations of 1915 may be performed according to the methods described herein. In some examples, aspects of the operations of 1915 may be performed as described in reference to Figures 10 to 13 The described downlink control transmitter is performed.
[0248] At 1920, the base station may transmit or receive the first repetition via the first CC and transmit or receive the second repetition via the second CC. The operations of 1920 may be performed according to the methods described herein. In some examples, aspects of the operations of 1920 may be performed as described in reference to Figures 10 to 13 The described duplication manager is implemented.
[0249] Fig. 20 1 is a flow chart illustrating a method 2000 for supporting cross-carrier shared channel repetition according to aspects of the present disclosure. The operations of the method 2000 may be implemented by a base station 105 or components thereof as described herein. For example, the operations of the method 2000 may be implemented by a base station 105 or components thereof as described herein. Figures 10 to 13 In some examples, a base station may execute an instruction set to control functional elements of the base station to perform the functions described herein. Additionally or alternatively, a base station may use dedicated hardware to perform various aspects of the functions described herein.
[0250] At 2005, the base station may identify a set of CCs supported by the UE for communicating with the base station. The operations of 2005 may be performed according to the methods described herein. In some examples, aspects of the operations of 2005 may be performed as described with reference to Figures 10 to 13 The CC module described is used to perform.
[0251] At 2010, the base station may transmit an indication of a subset of the CC set that may be used for a plurality of repetitions of a transport block, the subset comprising at least a first CC and a second CC, wherein the indication is transmitted via RRC signaling, MAC-CE, or DCI. The operations of 2010 may be performed according to the methods described herein. In some examples, aspects of the operations of 2010 may be performed as described with reference to Figures 10 to 13 The description instructs the transmitter to perform.
[0252] At 2015, the base station may transmit a downlink control message to the UE, the downlink control message scheduling multiple repetitions of the transport block for the UE, wherein a first repetition of the multiple repetitions is scheduled on a first CC in the CC set, and a second repetition of the multiple repetitions is scheduled on a second CC in the CC set. The operations of 2015 may be performed according to the methods described herein. In some examples, aspects of the operations of 2015 may be performed as described in reference to Figures 10 to 13 The described downlink control transmitter is performed.
[0253] At 2020, the base station may transmit or receive the first repetition via the first CC and transmit or receive the second repetition via the second CC. The operations of 2020 may be performed according to the methods described herein. In some examples, various aspects of the operations of 2020 may be performed as described in reference to Figures 10 to 13 The described duplication manager is implemented.
[0254] It should be noted that the methods described herein describe possible implementations, and that the various operations and steps may be rearranged or otherwise modified and other implementations are possible. Furthermore, aspects from two or more methods may be combined.
[0255] The following provides an overview of various aspects of the disclosure:
[0256] Aspect 1: A method for performing wireless communications at a UE, comprising: identifying a set of component carriers supported by the UE for communicating with a base station; receiving a downlink control message from the base station, the downlink control message scheduling multiple repetitions of a transmission block for the UE, wherein a first repetition of the multiple repetitions is scheduled on a first component carrier of the component carrier set, and a second repetition of the multiple repetitions is scheduled on a second component carrier of the component carrier set; and transmitting or receiving the first repetition via the first component carrier, and transmitting or receiving the second repetition via the second component carrier.
[0257] Aspect 2: The method of aspect 1 further comprises: receiving an indication that multiple repetitions of the transport block are scheduled via the first and second component carriers according to one or both of a frequency division multiplexing (FDM) scheme or a time division multiplexing (TDM) scheme.
[0258] Aspect 3: The method of aspect 2, wherein the indication is received via RRC signaling, a medium access control (MAC) control element (MAC-CE) or DCI.
[0259] Aspect 4: The method as in any one of Aspects 1 to 3 further includes: receiving an indication of multiple repeated subsets of the component carrier set that can be used for a transmission block, the subset including at least a first component carrier and a second component carrier, wherein the indication is received via RRC signaling, a media access control (MAC) control element (MAC-CE) or a DCI.
[0260] Aspect 5: The method of aspect 4, wherein the indication comprises a set of carrier indices corresponding to the subset of the set of component carriers.
[0261] Aspect 6: The method according to any one of aspects 1 to 5, further comprising: receiving an indication of at least one component carrier in the component carrier set to be dropped for multiple repetitions of the transport block.
[0262] Aspect 7: The method according to any one of aspects 1 to 6, further comprising: receiving an indication of a starting component carrier for a plurality of repetitions of a transport block.
[0263] Aspect 8: The method of any one of Aspects 1 to 7 further includes: transmitting feedback for a subset of the component carrier set; and receiving an indication of a starting component carrier for multiple repetitions of a transmission block based at least in part on the feedback, wherein the subset includes the starting component carrier, and the feedback indicates ACK / negative ACK (NACK) feedback or signal to interference plus noise ratio (SINR) for each component carrier in the subset.
[0264] Aspect 9: The method as in any one of Aspects 1 to 8 further includes: receiving a reference subcarrier spacing configuration for each component carrier in a subset of the component carrier set via RRC signaling; and determining the number of code elements between a downlink control message and a first repeated transmission or reception via a first component carrier based at least in part on the reference subcarrier spacing configuration.
[0265] Aspect 10: A method as in Aspect 9, wherein the number of codewords is based at least in part on a minimum or maximum time slot format indicator of the subset, an indication within a downlink control message, a subcarrier spacing of the first component carrier, or a subcarrier spacing associated with a downlink control message.
[0266] Aspect 11: The method as described in any one of Aspects 1 to 10 further includes: determining a first number of code elements between a downlink control message and a first repeated transmission or reception via the first component carrier at least partially based on the subcarrier spacing of the first component carrier; and determining a second number of code elements between a downlink control message and a second repeated transmission or reception via the second component carrier at least partially based on the subcarrier spacing of the second component carrier.
[0267] Aspect 12: The method of any one of Aspects 1 to 11 further includes: receiving a reference subcarrier spacing configuration for each component carrier in a subset of the component carrier set via RRC signaling; and determining a time slot for a first repeated transmission or reception via a first component carrier based at least in part on the reference subcarrier spacing configuration.
[0268] Aspect 13: The method of any one of Aspects 1 to 12 further includes: determining a first time slot for a first repeated transmission or reception via the first component carrier based at least in part on the subcarrier spacing of the first component carrier; and determining a second time slot for a second repeated transmission or reception via the second component carrier based at least in part on the subcarrier spacing of the second component carrier.
[0269] Aspect 14: The method as in any one of Aspects 1 to 13 further includes: receiving a reference subcarrier spacing configuration for each component carrier in a subset of the component carrier set via RRC signaling; and determining a starting codeword and time length for a first repetition of transmission or reception via a first component carrier based at least in part on the reference subcarrier spacing configuration, wherein the starting codeword and time length are the same for the first component carrier and the second component carrier.
[0270] Aspect 15: The method of any one of aspects 1 to 14, further comprising: determining a number of symbols for a first repeated transmission or reception via the first component carrier, wherein the number of symbols is the same for the first component carrier and the second component carrier.
[0271] Aspect 16: The method as in any one of Aspects 1 to 15 further includes: determining a transmission block size for a first repeated transmission or reception via a first component carrier based at least in part on a nominal time length and a nominal resource element set indicated by a downlink control message, wherein the transmission block size is the same for the first component carrier and the second component carrier.
[0272] Aspect 17: The method of any one of Aspects 1 to 16, further comprising: determining a transport block size for a first repeated transmission or reception via the first component carrier based at least in part on a nominal resource element set for the first component carrier and the second component carrier.
[0273] Aspect 18: A method for performing wireless communications at a base station, comprising: identifying a set of component carriers supported by a UE for communicating with the base station; transmitting a downlink control message to the UE, the downlink control message scheduling multiple repetitions of a transmission block for the UE, wherein a first repetition of the multiple repetitions is scheduled on a first component carrier of the component carrier set, and a second repetition of the multiple repetitions is scheduled on a second component carrier of the component carrier set; and transmitting or receiving the first repetition via the first component carrier, and transmitting or receiving the second repetition via the second component carrier.
[0274] Aspect 19: The method of aspect 18, further comprising: transmitting an indication that the multiple repetitions of the transport block are scheduled via the first and second component carriers according to one or both of a frequency division multiplexing (FDM) scheme or a time division multiplexing (TDM) scheme.
[0275] Aspect 20: The method of aspect 19, wherein the indication is transmitted via RRC signaling, a medium access control (MAC) control element (MAC-CE) or DCI.
[0276] Aspect 21: The method of any one of Aspects 18 to 20 further includes: transmitting an indication of multiple repeated subsets of the component carrier set that can be used for a transmission block, the subset including at least a first component carrier and a second component carrier, wherein the indication is transmitted via RRC signaling, a media access control (MAC) control element (MAC-CE) or a DCI.
[0277] Aspect 22: The method of Aspect 21, wherein the indication comprises a set of carrier indices corresponding to the subset of the set of component carriers.
[0278] Aspect 23: The method according to any one of aspects 18 to 22, further comprising: transmitting an indication of at least one component carrier in the component carrier set to be dropped for multiple repetitions of the transport block.
[0279] Aspect 24: The method of any one of aspects 18 to 23, further comprising: transmitting an indication of a starting component carrier for a plurality of repetitions of a transport block.
[0280] Aspect 25: The method of any one of Aspects 18 to 24 further includes: receiving feedback from the UE for a subset of the component carrier set; and transmitting an indication of a starting component carrier for multiple repetitions of a transmission block based at least in part on the feedback, wherein the subset includes the starting component carrier, and the feedback indicates ACK / negative ACK (NACK) feedback or signal to interference plus noise ratio (SINR) for each component carrier in the subset.
[0281] Aspect 26: The method of any one of Aspects 18 to 25 further includes: transmitting a reference subcarrier spacing configuration for each component carrier in a subset of the component carrier set via RRC signaling; scheduling a first repeated transmission or reception via a first component carrier based at least in part on the reference subcarrier spacing configuration; and scheduling a second repeated transmission or reception via a second component carrier based at least in part on the reference subcarrier spacing configuration.
[0282] Aspect 27: A method as in any one of Aspects 18 to 26, further comprising: scheduling a first repeated transmission or reception via the first component carrier based at least in part on a first subcarrier spacing configuration associated with the first component carrier; and scheduling a second repeated transmission or reception via the second component carrier based at least in part on a second subcarrier spacing configuration associated with the second component carrier.
[0283] Aspect 28: The method of any one of aspects 18 to 27, further comprising: scheduling transmission or reception of the first repetition via the first component carrier based at least in part on a subcarrier spacing configuration associated with the downlink control message.
[0284] Aspect 29: An apparatus for performing wireless communication at a UE, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method as in any one of Aspects 1 to 17.
[0285] Aspect 30: An apparatus for wireless communication at a UE, comprising at least one device for performing the method of any one of aspects 1 to 17.
[0286] Aspect 31: A non-transitory computer-readable medium storing a code for wireless communication at a UE, the code comprising instructions executable by a processor to perform the method of any one of aspects 1 to 17.
[0287] Aspect 32: An apparatus for performing wireless communications at a base station, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method as described in any one of Aspects 18 to 28.
[0288] Aspect 33: An apparatus for wireless communication at a base station, comprising at least one means for performing the method of any one of Aspects 18 to 28.
[0289] Aspect 34: A non-transitory computer-readable medium storing code for wireless communication at a base station, the code comprising instructions executable by a processor to perform the method of any one of aspects 18 to 28.
[0290] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein may also be applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the described techniques may be applied to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.
[0291] The information and signals described herein may be represented using any of a variety of different techniques and technologies. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout this description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
[0292] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or performed with 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 in the alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).
[0293] 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 by a computer-readable medium as one or more instructions or codes. Other examples and implementations fall within the scope of the present 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 that implement the functions may also be physically located in various locations, including being distributed so that parts of the functions are implemented at different physical locations.
[0294] Computer-readable medium includes both non-transient computer storage medium and communication medium, and it includes any medium that facilitates computer program to transfer from one place to another place.Non-transient storage medium can be any available medium that can be accessed by general or special-purpose computer.As an example and not limitation, non-transient computer-readable medium can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disk (CD) ROM or other optical disk storage, disk storage or other magnetic storage device, or can be used to carry or store instruction or data structure form of desired program code means and can be accessed by general or special-purpose computer or general or special-purpose processor any other non-transient medium.Similarly, any connection is also properly referred to as computer-readable medium.For example, if software is transmitted from website, server or other remote source using coaxial cable, optical fiber cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave, then this coaxial cable, optical fiber cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are just included in the definition of computer-readable medium. Disk and disc as used herein include CDs, laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs, where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.
[0295] As used herein (including in the claims), "or" used in a list of items (e.g., a list of items with a phrase such as "at least one of" or "one or more of") indicates an inclusive list, so that, 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). Similarly, as used herein, the phrase "based on" should not be interpreted as referring to a closed set of conditions. For example, an example step described as being 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" should be interpreted in the same manner as the phrase "based at least in part on."
[0296] In the accompanying drawings, similar components or features may have the same reference number. In addition, various components of the same type may be distinguished by following the reference number with a dash and a second reference number that distinguishes between similar components. If only the first reference number is used in the specification, the description may apply to any of the similar components having the same first reference number regardless of the second reference number, or other subsequent reference numbers.
[0297] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that can be implemented or fall within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration" and does not mean "better than" or "better than other examples." This detailed description includes specific details to provide 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.
[0298] The description herein is provided to enable one of ordinary skill in the art to make or use the present disclosure. Various modifications to the present disclosure will be apparent to one of ordinary skill in the art, and the universal principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Thus, the present disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.
Claims
1. A method for wireless communication at a user equipment (UE), comprising: receiving a downlink control message that schedules a plurality of repetitions of a transport block for the UE, wherein a first repetition of the plurality of repetitions is scheduled on a first component carrier in a set of component carriers supported by the UE for communication, and a second repetition of the plurality of repetitions is scheduled on a second component carrier in the set of component carriers; receiving an indication that the plurality of repetitions of the transport block are scheduled via the first component carrier and the second component carrier according to one or both of a frequency division multiplexing (FDM) scheme or a time division multiplexing (TDM) scheme; as well as The first repetition is communicated via the first component carrier, and the second repetition is communicated via the second component carrier.
2. The method of claim 1 , wherein the plurality of repetitions with respect to the transport block are scheduled according to one or both of an FDM scheme or a TDM scheme as indications of the first component carrier and the second component carrier are received via radio resource control (RRC) signaling, a medium access control (MAC) control element (MAC-CE), or downlink control information (DCI).
3. The method of claim 1, further comprising: Receive an indication of a subset of the set of component carriers that can be used for the multiple repetitions of the transport block, the subset including at least the first component carrier and the second component carrier, wherein the indication is received via radio resource control (RRC) signaling, a medium access control (MAC) control element (MAC-CE), or downlink control information (DCI).
4. The method of claim 3, wherein the indication of the subset of the set of component carriers available for the plurality of repetitions of the transport block comprises a set of carrier indices corresponding to the subset of the set of component carriers.
5. The method of claim 1, further comprising: An indication of at least one component carrier in the set of component carriers to be dropped for the plurality of repetitions of the transport block is received.
6. The method of claim 1, further comprising: An indication of a starting component carrier for the plurality of repetitions of the transport block is received.
7. The method of claim 1, further comprising: transmitting feedback for a subset of the set of component carriers; as well as and receiving an indication of a starting component carrier for the plurality of repetitions of the transport block based at least in part on the feedback, wherein the subset includes the starting component carrier, and the feedback indicates an acknowledgement (ACK) / negative ACK (NACK) feedback or a signal to interference plus noise ratio (SINR) for each component carrier in the subset.
8. The method of claim 1, further comprising: receiving, via radio resource control (RRC) signaling, a reference subcarrier spacing configuration for each component carrier in a subset of the set of component carriers; as well as A number of symbols between the downlink control message and communication of the first repetition via the first component carrier is determined based at least in part on the reference subcarrier spacing configuration.
9. The method of claim 8, wherein the number of symbols is based at least in part on a minimum or maximum slot format indicator for the subset, an indication within the downlink control message, a subcarrier spacing of the first component carrier, or a subcarrier spacing associated with the downlink control message.
10. The method of claim 1, further comprising: determining a first number of symbols between the downlink control message and the communication of the first repetition via the first component carrier based at least in part on a subcarrier spacing of the first component carrier; as well as A second number of symbols between the downlink control message and communication of the second repetition via the second component carrier is determined based at least in part on a subcarrier spacing of the second component carrier.
11. The method of claim 1, further comprising: receiving, via radio resource control (RRC) signaling, a reference subcarrier spacing configuration for each component carrier in a subset of the set of component carriers; as well as A time slot for delivery of the first repetition via the first component carrier is determined based at least in part on the reference subcarrier spacing configuration.
12. The method of claim 1, further comprising: determining a first time slot for delivery of the first repetition via the first component carrier based at least in part on a subcarrier spacing of the first component carrier; as well as A second time slot for delivery of the second repetition via the second component carrier is determined based at least in part on a subcarrier spacing of the second component carrier.
13. The method of claim 1, further comprising: receiving, via radio resource control (RRC) signaling, a reference subcarrier spacing configuration for each component carrier in a subset of the set of component carriers; as well as A starting symbol and a time length for delivery of the first repetition via the first component carrier are determined based at least in part on the reference subcarrier spacing configuration, wherein the starting symbol and time length are the same for the first component carrier and the second component carrier.
14. The method of claim 1, further comprising: A number of symbols for delivery of the first repetition via the first component carrier is determined, wherein the number of symbols is the same for the first component carrier and the second component carrier.
15. The method of claim 1, further comprising: A transport block size for delivery of the first repetition via the first component carrier is determined based at least in part on a nominal time length and a nominal set of resource elements indicated by the downlink control message, wherein the transport block size is the same for the first component carrier and the second component carrier.
16. The method of claim 1, further comprising: A transport block size for delivery of the first repetition via the first component carrier is determined based at least in part on nominal resource element sets for the first component carrier and the second component carrier.
17. A method for wireless communication at a network device, comprising: transmitting a downlink control message to a user equipment (UE), the downlink control message scheduling a plurality of repetitions of a transport block for the UE, wherein a first repetition of the plurality of repetitions is scheduled on a first component carrier in a set of component carriers supported by the UE for communicating with the network device, and a second repetition of the plurality of repetitions is scheduled on a second component carrier in the set of component carriers; transmitting an indication that the plurality of repetitions of the transport block are scheduled via the first component carrier and the second component carrier according to one or both of a frequency division multiplexing (FDM) scheme or a time division multiplexing (TDM) scheme; as well as The first repetition is communicated via the first component carrier, and the second repetition is communicated via the second component carrier.
18. The method of claim 17, wherein: The multiple repetitions of the transport block are scheduled according to one or both of an FDM scheme or a TDM scheme as indications of the first component carrier and the second component carrier transmitted via radio resource control (RRC) signaling, a medium access control (MAC) control element (MAC-CE), or downlink control information (DCI).
19. The method of claim 17, further comprising: transmitting an indication of a subset of the set of component carriers that can be used for the plurality of repetitions of the transport block, the subset comprising at least the first component carrier and the second component carrier, wherein the indication is transmitted via radio resource control (RRC) signaling, a medium access control (MAC) control element (MAC-CE), or downlink control information (DCI).
20. The method of claim 19, wherein the indication of the subset of the set of component carriers available for the plurality of repetitions of the transport block comprises a set of carrier indices corresponding to the subset of the set of component carriers.
21. The method of claim 17, further comprising: An indication of at least one component carrier in the set of component carriers to be dropped for the plurality of repetitions of the transport block is transmitted.
22. The method of claim 17, further comprising: An indication of a starting component carrier for the plurality of repetitions of the transport block is transmitted.
23. The method of claim 17, further comprising: receiving feedback from the UE for a subset of the set of component carriers; as well as An indication of a starting component carrier for the plurality of repetitions of the transport block is transmitted based at least in part on the feedback, wherein the subset includes the starting component carrier and the feedback indicates an acknowledgement (ACK) / negative ACK (NACK) feedback or a signal to interference plus noise ratio (SINR) for each component carrier in the subset.
24. The method of claim 17, further comprising: transmitting, via radio resource control (RRC) signaling, a reference subcarrier spacing configuration for each component carrier in a subset of the set of component carriers; scheduling delivery of the first repetition via the first component carrier based at least in part on the reference subcarrier spacing configuration; as well as Delivery of the second repetition via the second component carrier is scheduled based at least in part on the reference subcarrier spacing configuration.
25. The method of claim 17, further comprising: scheduling delivery of the first repetition via the first component carrier based at least in part on a first subcarrier spacing configuration associated with the first component carrier; as well as Delivery of the second repetition via the second component carrier is scheduled based at least in part on a second subcarrier spacing configuration associated with the second component carrier.
26. The method of claim 17, further comprising: Delivery of the first repetition via the first component carrier is scheduled based at least in part on a subcarrier spacing configuration associated with the downlink control message.
27. An apparatus for wireless communication at a user equipment (UE), comprising: means for receiving a downlink control message that schedules a plurality of repetitions of a transport block for the UE, wherein a first repetition of the plurality of repetitions is scheduled on a first component carrier in a set of component carriers supported by the UE for communication, and a second repetition of the plurality of repetitions is scheduled on a second component carrier in the set of component carriers; means for receiving an indication that the plurality of repetitions of the transport block are scheduled via the first component carrier and the second component carrier according to one or both of a frequency division multiplexing (FDM) scheme or a time division multiplexing (TDM) scheme; as well as Means for communicating the first repetition via the first component carrier, and communicating the second repetition via the second component carrier.
28. The apparatus of claim 27, further comprising means for performing any of claims 2-16.
29. A device for wireless communication at a network device, comprising: means for transmitting a downlink control message to a user equipment (UE), the downlink control message scheduling a plurality of repetitions of a transport block for the UE, wherein a first repetition of the plurality of repetitions is scheduled on a first component carrier in a set of component carriers supported by the UE for communicating with the network device, and a second repetition of the plurality of repetitions is scheduled on a second component carrier in the set of component carriers; means for transmitting an indication that the plurality of repetitions of the transport block are scheduled via the first component carrier and the second component carrier according to one or both of a frequency division multiplexing (FDM) scheme or a time division multiplexing (TDM) scheme; as well as Means for communicating the first repetition via the first component carrier, and communicating the second repetition via the second component carrier.
30. The apparatus of claim 29, further comprising means for performing any of claims 18-26.
Citation Information
Patent Citations
System and Method for Reliable Transmission over Network Resources
US20190215104A1