EP3858044A1 - Time-domain resource allocation for repeated transmissions in new radio - Google Patents
Time-domain resource allocation for repeated transmissions in new radioInfo
- Publication number
- EP3858044A1 EP3858044A1 EP19867863.3A EP19867863A EP3858044A1 EP 3858044 A1 EP3858044 A1 EP 3858044A1 EP 19867863 A EP19867863 A EP 19867863A EP 3858044 A1 EP3858044 A1 EP 3858044A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- time domain
- resource allocation
- domain resource
- shared channel
- transmission
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 230000005540 biological transmission Effects 0.000 title claims abstract description 132
- 238000013468 resource allocation Methods 0.000 title claims description 67
- 230000011664 signaling Effects 0.000 claims description 22
- 238000012545 processing Methods 0.000 claims description 11
- 238000000034 method Methods 0.000 abstract description 47
- 238000004891 communication Methods 0.000 description 36
- 230000008569 process Effects 0.000 description 17
- 230000002776 aggregation Effects 0.000 description 15
- 238000004220 aggregation Methods 0.000 description 15
- 238000013507 mapping Methods 0.000 description 15
- 230000006870 function Effects 0.000 description 13
- 238000007726 management method Methods 0.000 description 9
- 238000010586 diagram Methods 0.000 description 6
- 230000004913 activation Effects 0.000 description 4
- 230000010267 cellular communication Effects 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 230000007246 mechanism Effects 0.000 description 3
- 230000002093 peripheral effect Effects 0.000 description 3
- 230000006399 behavior Effects 0.000 description 2
- 230000001413 cellular effect Effects 0.000 description 2
- 238000006243 chemical reaction Methods 0.000 description 2
- 238000012790 confirmation Methods 0.000 description 2
- 230000008878 coupling Effects 0.000 description 2
- 238000010168 coupling process Methods 0.000 description 2
- 238000005859 coupling reaction Methods 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 238000010295 mobile communication Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 238000001228 spectrum Methods 0.000 description 2
- 230000007704 transition Effects 0.000 description 2
- 230000003213 activating effect Effects 0.000 description 1
- 230000003321 amplification Effects 0.000 description 1
- 238000013459 approach Methods 0.000 description 1
- 238000013475 authorization Methods 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 230000000903 blocking effect Effects 0.000 description 1
- 108010015046 cell aggregation factors Proteins 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000012512 characterization method Methods 0.000 description 1
- 230000006835 compression Effects 0.000 description 1
- 238000007906 compression Methods 0.000 description 1
- 239000000470 constituent Substances 0.000 description 1
- 238000013480 data collection Methods 0.000 description 1
- 230000006837 decompression Effects 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000009977 dual effect Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000005670 electromagnetic radiation Effects 0.000 description 1
- 238000005755 formation reaction Methods 0.000 description 1
- GVVPGTZRZFNKDS-JXMROGBWSA-N geranyl diphosphate Chemical compound CC(C)=CCC\C(C)=C\CO[P@](O)(=O)OP(O)(O)=O GVVPGTZRZFNKDS-JXMROGBWSA-N 0.000 description 1
- 230000017525 heat dissipation Effects 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 239000000463 material Substances 0.000 description 1
- 230000008450 motivation Effects 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 238000003199 nucleic acid amplification method Methods 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 230000010363 phase shift Effects 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 239000000126 substance Substances 0.000 description 1
- 230000002194 synthesizing effect Effects 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/12—Wireless traffic scheduling
- H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
- H04W72/1273—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of downlink data flows
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1867—Arrangements specially adapted for the transmitter end
- H04L1/1887—Scheduling and prioritising arrangements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1867—Arrangements specially adapted for the transmitter end
- H04L1/189—Transmission or retransmission of more than one copy of a message
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1867—Arrangements specially adapted for the transmitter end
- H04L1/1896—ARQ related signaling
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/20—Control channels or signalling for resource management
- H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
Definitions
- embodiments described herein are directed to the allocation of time- domain resources for repeated transmissions.
- Embodiments of the present disclosure may be used in conjunction with transmissions for new radio (NR).
- NR new radio
- FIGS 1 and 2, and 3 illustrate examples of operation flow/algorithmic structures in accordance with some embodiments.
- Figure 4A illustrates an example of back-to-back repetitions indicated dynamically, compared to separate DCI for each retransmission without crossing a slot boundary.
- Figures 4B and 4C illustrates examples of aggregated PUSCH allocation in accordance with some embodiments.
- Figure 5 depicts an architecture of a system of a network in accordance with some embodiments.
- Figure 6 depicts an example of components of a device in accordance with some embodiments.
- Figure 7 depicts an example of interfaces of baseband circuitry in accordance with some embodiments.
- Figure 8 depicts a block diagram illustrating components, according to some embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein.
- a machine-readable or computer-readable medium e.g., a non-transitory machine-readable storage medium
- Embodiments discussed herein may relate to the allocation of time-domain resources for repeated transmissions in new radio (NR). Other embodiments may be described and/or claimed.
- NR new radio
- the phrase“in various embodiments,”“in some embodiments,” and the like may refer to the same, or different, embodiments.
- the terms“comprising,”“having,” and“including” are synonymous, unless the context dictates otherwise.
- the phrase“A and/or B” means (A), (B), or (A and B).
- the phrases“A/B” and“A or B” mean (A), (B), or (A and B), similar to the phrase“A and/or B.”
- the phrase“at least one of A and B” means (A), (B), or (A and B).
- Examples of embodiments may be described as a process depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations may be performed in parallel, concurrently, or simultaneously. In addition, the order of the operations may be re arranged.
- a process may be terminated when its operations are completed, but may also have additional steps not included in the figure(s).
- a process may correspond to a method, a function, a procedure, a subroutine, a subprogram, and the like. When a process corresponds to a function, its termination may correspond to a return of the function to the calling function and/or the main function.
- Examples of embodiments may be described in the general context of computer- executable instructions, such as program code, software modules, and/or functional processes, being executed by one or more of the aforementioned circuitry.
- the program code, software modules, and/or functional processes may include routines, programs, objects, components, data structures, etc., that perform particular tasks or implement particular data types.
- the program code, software modules, and/or functional processes discussed herein may be implemented using existing hardware in existing communication networks. For example, program code, software modules, and/or functional processes discussed herein may be implemented using existing hardware at existing network elements or control nodes.
- NR next generation wireless communication system
- 5G next generation wireless communication system
- NR new radio
- 3GPP LTE-Advanced with additional potential new Radio Access Technologies (RATs) to enrich people lives with beher, simple and seamless wireless connectivity implementations.
- RATs Radio Access Technologies
- Legacy NR included a baseline set of features and components for future cellular communication systems, including the aspects of ultra-reliable low-latency communication (URLLC) by means of flexible resources allocation, scheduling & HARQ, low spectrum efficiency transmission parameters, etc.
- URLLC ultra-reliable low-latency communication
- Embodiments disclosed herein may be directed to enhanced PUSCH transmission, with respect to consideration of the repeated transmissions.
- PUSCH repetition related enhancements are disclosed.
- embodiments disclosed herein may be directed to detailed mechanisms to indicate the time-domain resources for the repeated transmissions to the UE.
- one of the enhancements regarding physical uplink shared channel (PUSCH) and physical downlink shared channel (PDSCH) transmission is consideration of the repeated transmissions.
- Embodiments described herein may be directed to PUSCH and PDSCH repetition related enhancements. In particular, the mechanisms to indicate the time-domain resources for the repeated transmissions to the UE, are discussed and disclosed.
- one of the techniques to improve tradeoff between latency and reliability and overall scheduling flexibility considering current slotted frame structure in NR is to enable dynamic aggregation of PUSCH transmissions.
- legacy PUSCH duration is already quite flexible and could be from 1 symbol to 14 or 12 symbols (for NCP and ECP respectively), it cannot accommodate the cases when relatively short transmission comparable to slot or less than a slot starts in the middle of one slot and ends in another slot.
- Figure 4A illustrates an example of back-to-back repetitions indicated dynamically (at the bottom portion) vs. separate DCI for each retransmission without crossing slot boundary (at the top portion).
- a typical legacy transmission is fitted into one slot (top part of the figure), while enhanced transmission may be achieved by aggregation of two in different slots (bottom part of the figure). It should be noted, that it may also be done by sending two grants, however it may cause large (at least doubled) control overhead which may lead to UE blocking.
- the number of repetitions could be jointly configured to the user equipment (UE) using UE-specific radio resource control (RRC) signaling as part of the time- domain resource allocation table in addition to starting symbol, length of PUSCH, and PUSCH mapping type.
- RRC radio resource control
- the number of repetitions can be indicated along with other time domain resource allocation (RA) information using the currently defined time-domain resource assignment bit-field in DCI format 0 0 (using 4 bits) or in downlink control information (DCI) format 0_l (using 0/1/2/3/4 bits, depending on the number of rows in the higher-layer configured time-domain resource allocation table).
- RA time domain resource allocation
- the numbers of repetitions could be jointly encoded with the start and length indicator value (SLIV) information (latter indicating start and length of the PUSCH) or certain specific combinations of numbers of repetitions (that are indicated dynamically) and start and length combinations may only be supported by the specifications.
- SIV start and length indicator value
- the Time domain resource assignment field value m of the DCI provides a row index in + 1 to an allocated table.
- the indexed row defines the slot offset K2, the start and length indicator SIJV. or directly the start symbol S and the allocation length L, and the PUSCH mapping type to be applied in the PUSCH transmission.
- the Time domain resource assignment field value m of the DCI provides a row index in + 1 to an allocated table.
- the determination of the used resource allocation table is defined in sub-clause 6.1.2.1.1.
- the indexed row defines the slot offset K2, the start and length indicator SUV. or directly the start symbol S and the allocation length L, and the PUSCH mapping type to be applied in the PUSCH transmission.
- the slot where the UE shall transmit the PUSCH is determined by K2 as
- n is the slot with the scheduling DCI
- K2 is based on the numerology
- m h: n and / z m n are the subcarrier spacing configurations for PUSCH
- the starting symbol S relative to the start of the slot, and the number of consecutive symbols L counting from the symbol S allocated for the PUSCH are determined from the start and length indicator SUV of the indexed row:
- the PUSCH mapping type is set to Type A or Type B as defined in Subclause 6.4.1.1.3 of 3GPP TS 38.211 as given by the indexed row.
- the UE may consider the S and L combinations defined in table 6.1.2.1-1 as valid PUSCH allocations:
- the numbers of repetitions could be jointly encoded with the SLIV information (latter indicating start and length of the PUSCH) or certain specific combinations of numbers of repetitions (that are indicated dynamically) and start and length combinations may only be supported by the specifications.
- SLIV l4R (L - l) + S, where L and R should be selected such that 0 ⁇ RL ⁇ 14 - S.
- repetitions of a transmission comprising some lengths, such as a set of values of L, where L ⁇ 14, may not cross slot boundary.
- R 2 and 4 to obtain valid S and L combinations.
- R can be higher layer configured or indicated as part of the scheduling DCI.
- R can also be indicated as part of the index indication from a higher layer configured table pusch-symbolAllocation. , where the indexed row may also define R along with the slot offset K2, the start and length indicator SUV. and the PUSCH mapping type to be applied in the PUSCH transmission.
- UE can be expected to follow the dynamic indication if also configured and as indicated in the scheduling or activation DCI (for Type 2 CG PUSCH). This can be done via a predefined over-riding rule, or by some dynamic indication of which type of signaling (e.g., RRC signaling vs dynamic signaling) to follow.
- RRC signaling vs dynamic signaling
- the RRC signaling may include the repetition level as part of time domain indication field is illustrated in Message Box 1 below, with underline text indicating the changes comparing to current message content.
- Message box 1 Example of updated RRC signaling to include the repetition factor
- repetitions when the repetitions are scheduled, they may be performed in at least two ways:
- Type A Slot-based repetitions, i.e. the same time domain allocation may be used in repeated slots, in particular the starting symbol, duration of PUSCH, and PUSCH mapping type in each slot in an aggregation are the same and derived from the time domain resource allocation field of the DCI scheduling PUSCH or activating Type 2 CG-PUSCH.
- Type B Back-to-back repetitions, i.e. the starting symbol of repetitions other than initial one is derived based on ending symbol of the previous repetition or based on other rule/indication so that repetitions may even be performed within one slot or with minimum/no gap in different slots as illustrated in Figure 1.
- each transmission duration or starting/end symbol position can be different in different slots, which depends on DL control region sizes or CORESET duration, guard period duration, NR physical uplink control channel (NR-PUCCH) duration, and whether reference signal including at least channel state information - reference signal (CSI-RS), sounding reference signal (SRS), RS for beam management, etc., is present within the slot.
- CSI-RS channel state information - reference signal
- SRS sounding reference signal
- a bitmap for the data starting and/or end symbol, e g., in each slot can be configured by higher layers or indicated in the DCI.
- the DCI can be carried in the first stage DCI in case when multiple-stage DCI is used to schedule the data transmission.
- the UE derives the starting positions and/or transmission duration of repetitions across slots boundary(ies), from DL/UL control region or durations of one or more CORESETs and guard period duration for each slot, and SLIV values regarding the TD allocation for the initial transmission as well as other prior repetitions.
- UE may obtain the information regarding the number of symbols for DL control or UL control channel from slot type related information carried by group common PDCCH, and semi-static configuration of guard period duration. After that, UE can derive the data duration for each slot.
- gNB may indicate the CSI-RS or other RS configurations within desired slots to accommodate the repeated transmissions, via DCI for data scheduling or group common PDCCH.
- UE may perform rate-matching around the RS in accordance with configuration.
- two start positions may be indicated, where one or both can be dynamically or semi-statically indicated. It is also possible that the start position of the first repetition is dynamically indicated whereas the start position of the second or subsequent repetitions may be configured by higher layer, e.g., relative to the end of the previous repetitions or based on pre-defmed rules. Such rules may depend on where exactly in the slot the previous repetition ends. Further, different rules can be defined for TDD and FDD, e.g., for certain SFI in TDD, different rules can be identified associated with given SFI.
- the UE identifies available uplink (UL) symbols for mapping of the PUSCH repetitions, e.g., the case where certain symbols in a slot are identified as downlink (DL) symbols by higher layer signaling or the case wherein a UE receives an slot format indication (SFI) indication before or while repetitions are going on, and consequently, the overall transmission may be affected.
- UL uplink
- SFI slot format indication
- the UE may assume those symbols indicated as UL or“Flexible” via semi-static DL-UL configurations (cell-specific and/or UE-specific configurations) as available for mapping of PUSCH repetitions.
- the symbols identified as“Flexible” via semi-static configuration may be further subject to reception of other dynamic triggers, e.g., scheduling DCI formats for DL/UL scheduling or dynamic SFI conveyed via DCI format 2 0.
- other dynamic triggers e.g., scheduling DCI formats for DL/UL scheduling or dynamic SFI conveyed via DCI format 2 0.
- the UE may assume only those symbols indicated as“UL” via semi-static DL-UL configurations (cell-specific and/or UE-specific configurations) as available for mapping of PUSCH repetitions.
- mapping of back-to-back repetitions may be realized only considering the available UL symbols based on semi-static DL-UL configurations and further dropping rules can be defined to address interaction with dynamic SFI as described next.
- the UE may not receive an SFI changing some symbols to DL or’’Flexible”, during the transmissions within the allocated slots. This is because in Rel-l5, any change/update which impacts a dynamically scheduled transmission, is not allowed. In other words, the UE is not expected to have conflict on link (DL or UL) direction between that of dynamic SFI and that of UE specific data (e.g., UE specific DCI triggered PUSCH (grant-based), or DCI granted multi-slot transmission), in Rel-l5.
- DL or UL link
- the UE may receive an SFI changing some symbols to DL or“Flexible.” In such a case, the transmission in the corresponding slot as well as all the subsequent transmissions are dropped. While there is no restriction for type 1 vs type 2 GF transmission in such case, and both may be handled the same, the first PUSCH transmission opportunity for type 2 that follows the activation DCI and the PUSCH transmission opportunity to carrying the Configured Grant PUSCH MAC CE confirmation message in response to a de-activation command, are treated similar to dynamically granted PUSCH, and not subject to dynamic cancelation based on SFI conveyed via DCI format 2 0. From this perspective, for type 2 GF UL, the SFI can then override a subsequent transmission opportunity, but not the very first one or the last PUSCH resource used to carry the MAC CE confirmation in response to a de activation/release command.
- a grant-free PUSCH (repetitions) is going on and the UE receives an SFI changing some symbols to DL or“Flexible”
- only the transmission in the corresponding slot may be dropped, and the transmission in the subsequent transmissions may take place as before.
- only the affected repetitions within a slot that is, with some symbols having conflicting directions (DL or“Flexible” via dynamic SFI) may be dropped, and other repetitions within the same slot or in subsequent slots may still be transmitted.
- the UE maps the generated modulated symbols PUSCH TB assuming all symbols corresponding to a repetition as available, but does not transmit the symbols corresponding to the affected symbols out of those used for a particular repetition of the TB.
- TD time domain
- Joint TD allocation may be defined in an efficient manner in terms of the overall experienced latency. As such, some relationships and/or constraints may be applied between the TD allocations in multiple (e.g., two) slots, to avoid incurring high latency in total. Each of these allocations are able to carry one repetition of PUSCH TB.
- a UE may be configured with K time domain resource allocations, via RRC configuration or Ll-signaling (e.g., by TD resource allocation fields) or a combination thereof. Further, it is possible to jointly configure multiple TD allocations, one for each repetition.
- K K 2 value
- Message box 3 the case of arbitrary number of concatenated TD allocations is presented in Message box 3 below, where the single SLIV field is replaced by a list of SLIV fields.
- Which one to consider, e.g., the legacy table type or the new table type, may be configured as part of PUSCH-Config.
- the size of the list implicitly indicates the number of repetitions corresponding to this particular entry of time domain allocation table.
- the maximum number of entries in the time domain allocation table may be increased from 16 to other value power of 2, e.g. 32 that will cause increase of TD RA field in DCI by at most 1 bit.
- a single length‘L’ and K starting positions‘S’ may be associated with a given entry in the TD allocation table. For example, we may consider transmission of small packets (e.g., 4 symbol duration) with repetitions, where multiple repetitions may need to be accommodated in a duration of 1.5 slot.
- this scheme it is still possible to allocate 14 symbols in the first slot and the remaining, e.g., 6, symbols in the next slot, via two TD allocations. Particularly, such scheme does not impose the constraint of allocating same length with these TD allocation. As such, this allocation scheme allows changing both the starting symbol as well as the transmission length, i.e., having multiple repetitions with different TD durations for each of the PUSCHs.
- the UE may reuse the packetization of the first transmission, for the repeated transmissions.
- the importance and impact of such SLIV encoding optimization may depend on the extent the indications are performed via RRC vs. DCI signaling.
- the SLIV value(s) are indicated via DCI, where the SLIV encoding rule may follow the previous example, or may be optimized further.
- the time domain resource allocation table consists of K2 value, the mapping time, and concatenation of two SLIV values.
- One of the SLIV values may be left empty, for compatibility to the legacy operation.
- Non-empty concatenation entry corresponds to the repetition and the first/second repetition is mapped to the first/second SLIV value, respectively.
- K repetitions with two or more (up to K) SLIV values may be considered.
- the number of SLIV values is less than the number of repetitions, more involved operation is required to encode the corresponding starting positions.
- the SLIV values may associate to the same or different slots (e.g., following the Rel-l5 behavior, where only position within the slots is indicated for the repetitions). Even though associating the SLIV values to the same slot is possible, but in such case, it may be more convenient to consider back to back repetitions, without additional indications.
- the resource allocation information corresponding to the transmission in the subsequent slot(s) may be explicitly indicated using (potentially modified) TD allocation fields.
- a UE may be configured with a rule how to map into slots the multiple provided TD allocations characterizing repetitions.
- the configuration signaling may indicate which TD allocation in the aggregation are mapped to which slot.
- First TD allocation may be mapped to the first slot
- second TD allocation may be mapped to the second slot or both TD allocations are mapped to the first slot.
- the full allocation signaling may only apply to the transmission corresponding to the current slot.
- the TD resource allocation information regarding the transmission of the subsequent repetition(s) may be implicitly derived based on the allocation in the previous slot (e.g., the allocation for transmission in the second slot is derived based on the transmission in the first (current) slot, so on and so forth).
- such implicit indication may be realized by a pre-defined mirroring relationship about the slot boundary.
- the mirroring relationship can be defined in terms of the ending symbol of the transmission in the each slot and the starting symbol of the transmission in its next slot.
- the next slot TD allocation may point to the beginning of that slot (i.e. PUSCH starts at the slot boundary or a few symbols after the slot boundary).
- Same rule can be applied with respect to the starting position for transmission in the third slot and the ending position of the transmission in the second slot, so on and so forth.
- back-to-back repetitions with the same length can be considered, until the TB may cross the slot boundary.
- the next repetition may start at the first available UL symbol in the next slot or subsequent slot when UL symbols are present.
- the time domain resource allocation may be signaled using single SLIV field but re-interpreted based on a flag signaled dynamically in DCI or semi-statically in RRC within time domain allocation table entry. If re-interpretation is enabled, then, in option 1, the resulting starting symbol S may indicate the last symbol of total PUSCH transmission in slot‘n + (K - 1)’ while the value of (S + L - 1) may indicate the first symbol in slot‘n’.
- the single SLIV value may be reinterpreted based on the configured number of repetitions and the re-interpretation flag so that starting symbol S may indicate the starting symbol in slot‘n’ and (S + L - 1) may indicate the last symbol in slot‘n + (K - 1)’.
- the last symbol of the aggregated PUSCH transmission may be calculated as S + L - 1 + 14*(K-1) in case of NCP and S + L - 1 + 12*(K-1) in case of ECP.
- Figure 4C illustrating a possible aggregated PUSCH allocation in case of SLIV re-interpretation option 2.
- the exact same concept may or may not be applicable for GF transmission (some further adjustments may be needed).
- the S value from the SLIV is repeated with periodicity P, which results in multiple starting positions within the slot. These positions are then repeated for every slot. If the periodicity P is less than the slot duration, a single starting symbol is automatically expanded into multiple candidates within the slot based on P.
- the starting positions are effectively determined beforehand (i.e., not indicated in an activation DCI or by higher layer configuration). Still, the starting symbols are not fixed and may vary depending on the location/transmission opportunity of that repetition as well as the previous repetition(s) in the slot.
- each starting position of each TD SLIV value in the concatenation/aggregation is recalculated based on the configured periodicity.
- a UE may not be expected to be configured with a combination of periodicity and TD allocation so that at least one of the TD allocations crosses slot boundary or periodicity boundary.
- TBS determination procedure for PUSCH repetitions may use/apply only first TD allocation while the second and other TD allocations in the concatenation / aggregation are not involved into the TBS determination procedure. This may be needed in case the TD allocation length is different between the first repetition and other repetitions.
- FIG. 5 illustrates an architecture of a system 500 of a network in accordance with some embodiments.
- the system 500 is shown to include a user equipment (UE) 501 and a UE 502.
- the UEs 501 and 502 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks), but may also comprise any mobile or non- mobile computing device, such as Personal Data Assistants (PDAs), pagers, laptop computers, desktop computers, wireless handsets, or any computing device including a wireless communications interface.
- PDAs Personal Data Assistants
- pagers pagers
- laptop computers desktop computers
- wireless handsets or any computing device including a wireless communications interface.
- any of the UEs 501 and 502 can comprise an Internet of Things (IoT) UE, which can comprise a network access layer designed for low-power IoT applications utilizing short-lived UE connections.
- An IoT UE can utilize technologies such as machine-to- machine (M2M) or machine-type communications (MTC) for exchanging data with an MTC server or device via a public land mobile network (PLMN), Proximity-Based Service (ProSe) or device-to-device (D2D) communication, sensor networks, or IoT networks.
- M2M or MTC exchange of data may be a machine-initiated exchange of data.
- An IoT network describes interconnecting IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived connections.
- the IoT UEs may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate the connections of the IoT network.
- the UEs 501 and 502 may be configured to connect, e.g., communicatively couple, with a radio access network (RAN) 510— the RAN 510 may be, for example, an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), a NextGen RAN (NG RAN), or some other type of RAN.
- UMTS Evolved Universal Mobile Telecommunications System
- E-UTRAN Evolved Universal Mobile Telecommunications System
- NG RAN NextGen RAN
- the UEs 501 and 502 utilize connections 503 and 504, respectively, each of which comprises a physical communications interface or layer (discussed in further detail below); in this example, the connections 503 and 504 are illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols, such as a Global System for Mobile Communications (GSM) protocol, a code-division multiple access (CDMA) network protocol, a Push-to-Talk (PTT) protocol, a PTT over Cellular (POC) protocol, a Universal Mobile Telecommunications System (UMTS) protocol, a 3GPP Long Term Evolution (LTE) protocol, a fifth generation (5G) protocol, aNew Radio (NR) protocol, and the like.
- GSM Global System for Mobile Communications
- CDMA code-division multiple access
- PTT Push-to-Talk
- POC PTT over Cellular
- UMTS Universal Mobile Telecommunications System
- LTE Long Term Evolution
- 5G fifth generation
- NR New Radio
- the UEs 501 and 502 may further directly exchange communication data via a ProSe interface 505.
- the ProSe interface 505 may alternatively be referred to as a sidelink interface comprising one or more logical channels, including but not limited to a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Discovery Channel (PSDCH), and a Physical Sidelink Broadcast Channel (PSBCH).
- PSCCH Physical Sidelink Control Channel
- PSSCH Physical Sidelink Shared Channel
- PSDCH Physical Sidelink Discovery Channel
- PSBCH Physical Sidelink Broadcast Channel
- the UE 502 is shown to be configured to access an access point (AP) 506 via connection 507.
- the connection 507 can comprise a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein the AP 506 would comprise a wireless fidelity (WiFi®) router.
- WiFi® wireless fidelity
- the AP 506 is shown to be connected to the Internet without connecting to the core network of the wireless system (described in further detail below).
- the RAN 510 can include one or more access nodes that enable the connections 503 and 504. These access nodes (ANs) can be referred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs), next Generation NodeBs (gNB), RAN nodes, and so forth, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell).
- BSs base stations
- eNBs evolved NodeBs
- gNB next Generation NodeBs
- RAN nodes and so forth, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell).
- the RAN 510 may include one or more RAN nodes for providing macrocells, e.g., macro RAN node 511, and one or more RAN nodes for providing femtocells or picocells (e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells), e.g., low power (LP) RAN node 512.
- macro RAN node 511 e.g., macro RAN node 511
- femtocells or picocells e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells
- LP low power
- any of the RAN nodes 511 and 512 can terminate the air interface protocol and can be the first point of contact for the UEs 501 and 502.
- any of the RAN nodes 511 and 512 can fulfill various logical functions for the RAN 510 including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.
- RNC radio network controller
- the UEs 501 and 502 can be configured to communicate using Orthogonal Frequency-Division Multiplexing (OFDM) communication signals with each other or with any of the RAN nodes 511 and 512 over a multicarrier communication channel in accordance various communication techniques, such as, but not limited to, an Orthogonal Frequency-Division Multiple Access (OFDMA) communication technique (e.g., for downlink communications) or a Single Carrier Frequency Division Multiple Access (SC- FDMA) communication technique (e.g., for uplink and ProSe or sidelink communications), although the scope of the embodiments is not limited in this respect.
- OFDM signals can comprise a plurality of orthogonal subcarriers.
- a downlink resource grid can be used for downlink transmissions from any of the RAN nodes 511 and 512 to the UEs 501 and 502, while uplink transmissions can utilize similar techniques.
- the grid can be a time-frequency grid, called a resource grid or time- frequency resource grid, which is the physical resource in the downlink in each slot.
- a time- frequency plane representation is a common practice for OFDM systems, which makes it intuitive for radio resource allocation.
- Each column and each row of the resource grid corresponds to one OFDM symbol and one OFDM subcarrier, respectively.
- the duration of the resource grid in the time domain corresponds to one slot in a radio frame.
- the smallest time-frequency unit in a resource grid is denoted as a resource element.
- Each resource grid comprises a number of resource blocks, which describe the mapping of certain physical channels to resource elements.
- Each resource block comprises a collection of resource elements; in the frequency domain, this may represent the smallest quantity of resources that currently can be allocated.
- the physical downlink shared channel may carry user data and higher-layer signaling to the UEs 501 and 502.
- the physical downlink control channel (PDCCH) may carry information about the transport format and resource allocations related to the PDSCH channel, among other things. It may also inform the UEs 501 and 502 about the transport format, resource allocation, and H-ARQ (Hybrid Automatic Repeat Request) information related to the uplink shared channel.
- downlink scheduling (assigning control and shared channel resource blocks to the UE 502 within a cell) may be performed at any of the RAN nodes 511 and 512 based on channel quality information fed back from any of the UEs 501 and 502.
- the downlink resource assignment information may be sent on the PDCCH used for (e.g., assigned to) each of the UEs 501 and 502.
- the PDCCH may use control channel elements (CCEs) to convey the control information.
- CCEs control channel elements
- the PDCCH complex-valued symbols may first be organized into quadruplets, which may then be permuted using a sub-block interleaver for rate matching.
- Each PDCCH may be transmitted using one or more of these CCEs, where each CCE may correspond to nine sets of four physical resource elements known as resource element groups (REGs).
- RAGs resource element groups
- QPSK Quadrature Phase Shift Keying
- the PDCCH can be transmitted using one or more CCEs, depending on the size of the downlink control information (DCI) and the channel condition.
- DCI downlink control information
- There can be four or more different PDCCH formats defined in LTE with different numbers of CCEs (e.g., aggregation level, L l, 2, 4, or 8).
- Some embodiments may use concepts for resource allocation for control channel information that are an extension of the above-described concepts. For example, some embodiments may utilize an enhanced physical downlink control channel (EPDCCH) that uses PDSCH resources for control information transmission.
- the EPDCCH may be transmitted using one or more enhanced control channel elements (ECCEs). Similar to above, each ECCE may correspond to nine sets of four physical resource elements known as enhanced resource element groups (EREGs). An ECCE may have other numbers of EREGs in some situations.
- EPCCH enhanced physical downlink control channel
- ECCEs enhanced control channel elements
- each ECCE may correspond to nine sets of four physical resource elements known as enhanced resource element groups (EREGs).
- EREGs enhanced resource element groups
- An ECCE may have other numbers of EREGs in some situations.
- the RAN 510 is shown to be communicatively coupled to a core network (CN) 520— via an Sl interface 513.
- the CN 520 may be an evolved packet core (EPC) network, a NextGen Packet Core (NPC) network, or some other type of CN.
- EPC evolved packet core
- NPC NextGen Packet Core
- the Sl interface 513 is split into two parts: the Sl-U interface 514, which carries traffic data between the RAN nodes 511 and 512 and the serving gateway (S-GW) 522, and the Sl-mobility management entity (MME) interface 515, which is a signaling interface between the RAN nodes 511 and 512 and MMEs 521.
- S-GW serving gateway
- MME Sl-mobility management entity
- the CN 520 comprises the MMEs 521, the S-GW 522, the Packet Data Network (PDN) Gateway (P-GW) 523, and a home subscriber server (HSS) 524.
- the MMEs 521 may be similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS) Support Nodes (SGSN).
- the MMEs 521 may manage mobility aspects in access such as gateway selection and tracking area list management.
- the HSS 524 may comprise a database for network users, including subscription-related information to support the network entities’ handling of communication sessions.
- the CN 520 may comprise one or several HSSs 524, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc.
- the HSS 524 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.
- the S-GW 522 may terminate the Sl interface 513 towards the RAN 510, and routes data packets between the RAN 510 and the CN 520.
- the S-GW 522 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3 GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.
- the P-GW 523 may terminate an SGi interface toward a PDN.
- the P-GW 523 may route data packets between the EPC network and external networks such as a network including the application server 530 (alternatively referred to as application function (AF)) via an Internet Protocol (IP) interface 525.
- the application server 530 may be an element offering applications that use IP bearer resources with the core network (e.g., UMTS Packet Services (PS) domain, LTE PS data services, etc.).
- PS UMTS Packet Services
- LTE PS data services etc.
- the P-GW 523 is shown to be communicatively coupled to an application server 530 via an IP communications interface 525.
- the application server 530 can also be configured to support one or more communication services (e.g., Voice-over-Intemet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UEs 501 and 502 via the CN 520.
- VoIP Voice-over-Intemet Protocol
- PTT sessions PTT sessions
- group communication sessions social networking services, etc.
- the P-GW 523 may further be anode for policy enforcement and charging data collection.
- Policy and Charging Enforcement Function (PCRF) 526 is the policy and charging control element of the CN 520.
- PCRF Policy and Charging Enforcement Function
- HPLMN Home Public Land Mobile Network
- IP-CAN Internet Protocol Connectivity Access Network
- HPLMN Home Public Land Mobile Network
- V-PCRF Visited PCRF
- VPLMN Visited Public Land Mobile Network
- the PCRF 526 may be communicatively coupled to the application server 530 via the P-GW 523.
- the application server 530 may signal the PCRF 526 to indicate a new service flow and select the appropriate Quality of Service (QoS) and charging parameters.
- the PCRF 526 may provision this rule into a Policy and Charging Enforcement Function (PCEF) (not shown) with the appropriate traffic flow template (TFT) and QoS class of identifier (QCI), which commences the QoS and charging as specified by the application server 530.
- PCEF Policy and Charging Enforcement Function
- TFT traffic flow template
- QCI QoS class of identifier
- FIG. 6 illustrates example components of a device 600 in accordance with some embodiments.
- the device 600 may include application circuitry 602, baseband circuitry 604, Radio Frequency (RF) circuitry 606, front-end module (FEM) circuitry 608, one or more antennas 610, and power management circuitry (PMC) 612 coupled together at least as shown.
- the components of the illustrated device 600 may be included in a UE or a RAN node.
- the device 600 may include fewer elements (e.g., a RAN node may not utilize application circuitry 602, and instead include a processor/controller to process IP data received from an EPC).
- the device 600 may include additional elements such as, for example, memory /storage, display, camera, sensor, or input/output (I/O) interface.
- additional elements such as, for example, memory /storage, display, camera, sensor, or input/output (I/O) interface.
- the components described below may be included in more than one device (e.g., said circuitries may be separately included in more than one device for Cloud-RAN (C- RAN) implementations).
- C- RAN Cloud-RAN
- the application circuitry 602 may include one or more application processors.
- the application circuitry 602 may include circuitry such as, but not limited to, one or more single-core or multi-core processors.
- the processor(s) may include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.).
- the processors may be coupled with or may include memory /storage and may be configured to execute instructions stored in the memory /storage to enable various applications or operating systems to run on the device 600.
- processors of application circuitry 602 may process IP data packets received from an EPC.
- the baseband circuitry 604 may include circuitry such as, but not limited to, one or more single-core or multi-core processors.
- the baseband circuitry 604 may include one or more baseband processors or control logic to process baseband signals received from a receive signal path of the RF circuitry 606 and to generate baseband signals for a transmit signal path of the RF circuitry 606.
- Baseband processing circuitry 604 may interface with the application circuitry 602 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 606.
- the baseband circuitry 604 may include a third generation (3G) baseband processor 604A, a fourth generation (4G) baseband processor 604B, a fifth generation (5G) baseband processor 604C, or other baseband processor(s) 604D for other existing generations, generations in development or to be developed in the future (e.g., second generation (2G), sixth generation (6G), etc.).
- the baseband circuitry 604 e.g., one or more of baseband processors 604A-D
- baseband processors 604A-D may be included in modules stored in the memory 604G and executed via a Central Processing Unit (CPU) 604E.
- the radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc.
- modulation/demodulation circuitry of the baseband circuitry 604 may include Fast-Fourier Transform (FFT), precoding, or constellation mapping/demapping functionality.
- encoding/decoding circuitry of the baseband circuitry 604 may include convolution, tail-biting convolution, turbo, Viterbi, or Low Density Parity Check (LDPC) encoder/decoder functionality.
- LDPC Low Density Parity Check
- the baseband circuitry 604 may include one or more audio digital signal processor(s) (DSP) 604F.
- the audio DSP(s) 604F may be include elements for compression/decompression and echo cancellation and may include other suitable processing elements in other embodiments.
- Components of the baseband circuitry may be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some embodiments.
- some or all of the constituent components of the baseband circuitry 604 and the application circuitry 602 may be implemented together such as, for example, on a system on a chip (SOC).
- SOC system on a chip
- the baseband circuitry 604 may provide for communication compatible with one or more radio technologies.
- the baseband circuitry 604 may support communication with an evolved universal terrestrial radio access network (EUTRAN) or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN).
- EUTRAN evolved universal terrestrial radio access network
- WMAN wireless metropolitan area networks
- WLAN wireless local area network
- WPAN wireless personal area network
- multi-mode baseband circuitry Embodiments in which the baseband circuitry 604 is configured to support radio communications of more than one wireless protocol.
- RF circuitry 606 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium.
- the RF circuitry 606 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network.
- RF circuitry 606 may include a receive signal path which may include circuitry to down- convert RF signals received from the FEM circuitry 608 and provide baseband signals to the baseband circuitry 604.
- RF circuitry 606 may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitry 604 and provide RF output signals to the FEM circuitry 608 for transmission.
- the receive signal path of the RF circuitry 606 may include mixer circuitry 606a, amplifier circuitry 606b and filter circuitry 606c.
- the transmit signal path of the RF circuitry 606 may include filter circuitry 606c and mixer circuitry 606a.
- RF circuitry 606 may also include synthesizer circuitry 606d for synthesizing a frequency for use by the mixer circuitry 606a of the receive signal path and the transmit signal path.
- the mixer circuitry 606a of the receive signal path may be configured to down- convert RF signals received from the FEM circuitry 608 based on the synthesized frequency provided by synthesizer circuitry 606d.
- the amplifier circuitry 606b may be configured to amplify the down-converted signals and the filter circuitry 606c may be a low-pass filter (LPF) or band pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals.
- Output baseband signals may be provided to the baseband circuitry 604 for further processing.
- the output baseband signals may be zero-frequency baseband signals, although this is not a requirement.
- mixer circuitry 606a of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.
- the mixer circuitry 606a of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 606d to generate RF output signals for the FEM circuitry 608.
- the baseband signals may be provided by the baseband circuitry 604 and may be filtered by filter circuitry 606c.
- the mixer circuitry 606a of the receive signal path and the mixer circuitry 606a of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and upconversion, respectively.
- the mixer circuitry 606a of the receive signal path and the mixer circuitry 606a of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection).
- the mixer circuitry 606a of the receive signal path and the mixer circuitry 606a of the transmit signal path may be arranged for direct downconversion and direct upconversion, respectively.
- the mixer circuitry 606a of the receive signal path and the mixer circuitry 606a of the transmit signal path may be configured for super heterodyne operation.
- the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the embodiments is not limited in this respect.
- the output baseband signals and the input baseband signals may be digital baseband signals.
- the RF circuitry 606 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 604 may include a digital baseband interface to communicate with the RF circuitry 606.
- ADC analog-to-digital converter
- DAC digital-to-analog converter
- a separate radio IC circuitry may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this respect.
- the synthesizer circuitry 606d may be a fractional-N synthesizer or a fractional N/N+l synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable.
- synthesizer circuitry 606d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.
- the synthesizer circuitry 606d may be configured to synthesize an output frequency for use by the mixer circuitry 606a of the RF circuitry 606 based on a frequency input and a divider control input.
- the synthesizer circuitry 606d may be a fractional N/N+l synthesizer.
- frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a requirement.
- VCO voltage controlled oscillator
- Divider control input may be provided by either the baseband circuitry 604 or the applications processor 602 depending on the desired output frequency.
- a divider control input (e.g., N) may be determined from a look-up table based on a channel indicated by the applications processor 602.
- Synthesizer circuitry 606d of the RF circuitry 606 may include a divider, a delay-locked loop (DLL), a multiplexer and a phase accumulator.
- the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DP A).
- the DMD may be configured to divide the input signal by either N or N+l (e.g., based on a carry out) to provide a fractional division ratio.
- the DLL may include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop.
- the delay elements may be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line.
- Nd is the number of delay elements in the delay line.
- synthesizer circuitry 606d may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other.
- the output frequency may be a LO frequency (fLO).
- the RF circuitry 606 may include an IQ/polar converter.
- FEM circuitry 608 may include a receive signal path, which may include circuitry configured to operate on RF signals received from one or more antennas 610, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 606 for further processing.
- FEM circuitry 608 may also include a transmit signal path, which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 606 for transmission by one or more of the one or more antennas 610.
- the amplification through the transmit or receive signal paths may be done solely in the RF circuitry 606, solely in the FEM 608, or in both the RF circuitry 606 and the FEM 608.
- the FEM circuitry 608 may include a TX/RX switch to switch between transmit mode and receive mode operation.
- the FEM circuitry 608 may include a receive signal path and a transmit signal path.
- the receive signal path of the FEM circuitry 608 may include a low noise amplifier (LNA) to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 606).
- the transmit signal path of the FEM circuitry 608 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 606), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 610).
- PA power amplifier
- the PMC 612 may manage power provided to the baseband circuitry 604.
- the PMC 612 may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion.
- the PMC 612 may often be included when the device 600 is capable of being powered by a battery, for example, when the device is included in a UE.
- the PMC 612 may increase the power conversion efficiency while providing desirable implementation size and heat dissipation characteristics.
- FIG. 6 shows the PMC 612 coupled only with the baseband circuitry 604.
- the PMC 612 may be additionally or alternatively coupled with, and perform similar power management operations for, other components such as, but not limited to, application circuitry 602, RF circuitry 606, or FEM 608.
- the PMC 612 may control, or otherwise be part of, various power saving mechanisms of the device 600. For example, if the device 600 is in an RRC_Connected state, where it is still connected to the RAN node as it expects to receive traffic shortly, then it may enter a state known as Discontinuous Reception Mode (DRX) after a period of inactivity. During this state, the device 600 may power down for brief intervals of time and thus save power.
- DRX Discontinuous Reception Mode
- the device 600 may transition off to an RRC Idle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc.
- the device 600 goes into a very low power state and it performs paging where again it periodically wakes up to listen to the network and then powers down again.
- the device 600 may not receive data in this state, in order to receive data, it must transition back to RRC Connected state.
- An additional power saving mode may allow a device to be unavailable to the network for periods longer than a paging interval (ranging from seconds to a few hours). During this time, the device is totally unreachable to the network and may power down completely. Any data sent during this time incurs a large delay and it is assumed the delay is acceptable.
- Processors of the application circuitry 602 and processors of the baseband circuitry 604 may be used to execute elements of one or more instances of a protocol stack.
- processors of the baseband circuitry 604 alone or in combination, may be used to execute Layer 3, Layer 2, or Layer 1 functionality, while processors of the application circuitry 602 may utilize data (e.g., packet data) received from these layers and further execute Layer 4 functionality (e.g., transmission communication protocol (TCP) and user datagram protocol (UDP) layers).
- Layer 3 may comprise a radio resource control (RRC) layer, described in further detail below.
- RRC radio resource control
- Layer 2 may comprise a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer, described in further detail below.
- Layer 1 may comprise a physical (PHY) layer of a UE/RAN node, described in further detail below.
- FIG. 7 illustrates example interfaces of baseband circuitry in accordance with some embodiments.
- the baseband circuitry 604 of FIG. 6 may comprise processors 604A-604E and a memory 604G utilized by said processors.
- Each of the processors 604A-604E may include a memory interface, 704A-704E, respectively, to send/receive data to/from the memory 604G.
- the baseband circuitry 604 may further include one or more interfaces to communicatively couple to other circuitries/devices, such as a memory interface 712 (e.g., an interface to send/receive data to/from memory external to the baseband circuitry 604), an application circuitry interface 714 (e.g., an interface to send/receive data to/from the application circuitry 602 of FIG. 6), an RF circuitry interface 716 (e.g., an interface to send/receive data to/from RF circuitry 606 of FIG.
- a memory interface 712 e.g., an interface to send/receive data to/from memory external to the baseband circuitry 604
- an application circuitry interface 714 e.g., an interface to send/receive data to/from the application circuitry 602 of FIG. 6
- an RF circuitry interface 716 e.g., an interface to send/receive data to/from RF circuitry 606 of FIG.
- a wireless hardware connectivity interface 718 e.g., an interface to send/receive data to/from Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components
- a power management interface 720 e.g., an interface to send/receive power or control signals to/from the PMC 612.
- FIG. 8 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein.
- FIG. 8 shows a diagrammatic representation of hardware resources 800 including one or more processors (or processor cores) 810, one or more memory /storage devices 820, and one or more communication resources 830, each of which may be communicatively coupled via a bus 840.
- node virtualization e.g., NFV
- a hypervisor 802 may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 800.
- the processors 810 may include, for example, a processor 812 and a processor 814.
- the memory /storage devices 820 may include main memory, disk storage, or any suitable combination thereof.
- the memory /storage devices 820 may include, but are not limited to, any type of volatile or non-volatile memory such as dynamic random access memory (DRAM), static random-access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), Flash memory, solid-state storage, etc.
- DRAM dynamic random access memory
- SRAM static random-access memory
- EPROM erasable programmable read-only memory
- EEPROM electrically erasable programmable read-only memory
- Flash memory solid-state storage, etc.
- the communication resources 830 may include interconnection or network interface components or other suitable devices to communicate with one or more peripheral devices 804 or one or more databases 806 via a network 808.
- the communication resources 830 may include wired communication components (e.g., for coupling via a Universal Serial Bus (USB)), cellular communication components, NFC components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components.
- wired communication components e.g., for coupling via a Universal Serial Bus (USB)
- cellular communication components e.g., for coupling via a Universal Serial Bus (USB)
- NFC components e.g., NFC components
- Bluetooth® components e.g., Bluetooth® Low Energy
- Wi-Fi® components e.g., Wi-Fi® components
- Instructions 850 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 810 to perform any one or more of the methodologies discussed herein.
- the instructions 850 may reside, completely or partially, within at least one of the processors 810 (e.g., within the processor’s cache memory), the memory /storage devices 820, or any suitable combination thereof.
- any portion of the instructions 850 may be transferred to the hardware resources 800 from any combination of the peripheral devices 804 or the databases 806. Accordingly, the memory of processors 810, the memory /storage devices 820, the peripheral devices 804, and the databases 806 are examples of computer-readable and machine-readable media.
- the devices/components of Figures 5-8, and particularly the baseband circuitry of Figure 7, may be used to practice, in whole or in part, any of the operation flow/algorithmic structures depicted in Figures 1-3.
- operation flow/algorithmic structure 100 may include, at 105, Retrieving, from memory, time domain resource allocation information comprising a table that includes an indication of a number of physical shared channel transmission repetitions to be used by a user equipment (UE). Operation flow/algorithmic structure 100 may further include, at 110, generating a first message that includes the time domain resource allocation information table. Operation flow/algorithmic structure 100 may further include, at 115, encoding the furst message for transmission to the UE.
- UE user equipment
- Operation flow/algorithmic structure 100 may further include, at 120, generating a second message that includes an index to the time domain resource allocation information table. Operation flow/algorithmic structure 100 may further include, at 125, encoding the second message for transmission to the UE.
- operation flow/algorithmic structure 200 may include, at 205, receiving a first message comprising time domain resource allocation information that includes a table having an indication of a number of physical shared channel transmission repetitions to be used by the UE. Operation flow/algorithmic structure 200 may further include, at 210, receiving a second message comprising an index to the time domain resource allocation information table. Operation flow/algorithmic structure 200 may further include, at 215, performing repeated physical shared channel transmissions based on the time domain resource allocation information.
- operation flow/algorithmic structure 300 may include, at 305, generating a first message comprising time domain resource allocation information that includes a table of entries, wherein each entry includes an indication of a number of physical shared channel transmission repetitions to be used by a user equipment (UE). Operation flow/algorithmic structure 300 may further include, at 310, encoding the first message for transmission to the UE. Operation flow/algorithmic structure 300 may further include, at 315, generating a second message that includes an index to the time domain resource allocation information table. Operation flow/algorithmic structure 300 may further include, at 320, encoding the second message for transmission to the UE.
- UE user equipment
- Example 1 includes an apparatus comprising: memory to store time domain resource allocation information comprising a table that includes an indication of a number of physical shared channel transmission repetitions to be used by a user equipment (UE); and processing circuitry, coupled with the memory, to: retrieve the time domain resource allocation information table from the memory; generate a first message that includes the time domain resource allocation information table; encode the first message for transmission to the UE; generate a second message that includes an index to the time domain resource allocation information table; and encode the second message for transmission to the UE.
- memory to store time domain resource allocation information comprising a table that includes an indication of a number of physical shared channel transmission repetitions to be used by a user equipment (UE); and processing circuitry, coupled with the memory, to: retrieve the time domain resource allocation information table from the memory; generate a first message that includes the time domain resource allocation information table; encode the first message for transmission to the UE; generate a second message that includes an index to the time domain resource allocation information table; and encode the second message for transmission to the UE.
- UE user equipment
- Example 2 includes the apparatus of example 1 or some other example herein, wherein the first message is encoded for transmission to the UE via radio resource control (RRC) signaling.
- RRC radio resource control
- Example 3 includes the apparatus of example 1 or some other example herein, wherein the second message is included in downlink control information (DCI).
- Example 4 includes the apparatus of example 1 or some other example herein, wherein the time domain resource allocation information is associated with physical uplink shared channel (PUSCH) transmissions or physical downlink shared channel (PDSCH) transmissions.
- PUSCH physical uplink shared channel
- PDSCH physical downlink shared channel
- Example 5 includes the apparatus of example 1 or some other example herein, wherein the time domain resource allocation information further includes a number of shared channel repetitions and a duration for each repetition.
- Example 6 includes the apparatus of example 1 or some other example herein, wherein the time domain resource allocation information further includes a number of shared channel repetitions and a starting symbol or an ending symbol for each shared channel repetition.
- Example 7 includes the apparatus of any of examples 1-6 or some other example herein, wherein the time domain resource allocation information further includes an indication of a start position for a first shared channel repetition and a start position for a second shared channel repetition.
- Example 8 includes one or more computer-readable media storing instructions that, when executed by one or more processors, cause a user equipment (UE) to: receive a first message comprising time domain resource allocation information that includes a table having an indication of a number of physical shared channel transmission repetitions to be used by the UE; receive a second message comprising an index to the time domain resource allocation information table; and perform repeated physical shared channel transmissions based on the time domain resource allocation information.
- UE user equipment
- Example 9 includes the one or more computer-readable media of example 8 or some other example herein, wherein repetitions of a transmission having a length less than a predetermined threshold (L) do not cross a slot boundary.
- L predetermined threshold
- Example 10 includes the one or more computer-readable media of example 8 or some other example herein, wherein the media further stores instructions for causing the UE to determine a starting position of a transmission repetition or a duration of a transmission repetition based on: a downlink/uplink (DL/UL) region, a control resource set (CORESET) duration, a guard period duration for a slot, or a start and length indicator value (SLIV) associated with a time domain allocation for an initial or prior transmission.
- DL/UL downlink/uplink
- CORESET control resource set
- SLIV start and length indicator value
- Example 11 includes the one or more computer-readable media of example 8 or some other example herein, wherein the first message is received via radio resource control (RRC) signaling.
- RRC radio resource control
- Example 12 includes the one or more computer-readable media of example 8 or some other example herein, wherein the second message is included in downlink control information (DCI).
- Example 13 includes the one or more computer-readable media of any one of examples 8-12 or some other example herein, wherein the time domain resource allocation information is associated with physical uplink shared channel (PUSCH) transmissions or physical downlink shared channel (PDSCH) transmissions.
- PUSCH physical uplink shared channel
- PDSCH physical downlink shared channel
- Example 14 includes one or more computer-readable media storing instructions that, when executed by one or more processors, cause a next-generation NodeB (gNB) to: generate a first message comprising time domain resource allocation information that includes a table of entries, wherein each entry includes an indication of a number of physical shared channel transmission repetitions to be used by a user equipment (UE); encode the first message for transmission to the UE; generate a second message that includes an index to the time domain resource allocation information table; and encode the second message for transmission to the UE.
- gNB next-generation NodeB
- Example 15 includes the one or more computer-readable media of example 14 or some other example herein, wherein the first message is encoded for transmission to the UE via radio resource control (RRC) signaling.
- RRC radio resource control
- Example 16 includes the one or more computer-readable media of example 14 or some other example herein, wherein the second message is included in downlink control information (DCI).
- DCI downlink control information
- Example 17 includes the one or more computer-readable media of example 14 or some other example herein, wherein the time domain resource allocation information is associated with physical uplink shared channel (PUSCH) transmissions or physical downlink shared channel (PDSCH) transmissions.
- PUSCH physical uplink shared channel
- PDSCH physical downlink shared channel
- Example 18 includes the one or more computer-readable media of example 14 or some other example herein, wherein the time domain resource allocation information further includes a shared channel duration for each repetition.
- Example 19 includes the one or more computer-readable media of example 14 or some other example herein, wherein the time domain resource allocation information further includes a starting symbol or an ending symbol for each shared channel repetition.
- Example 20 includes the one or more computer-readable media of any one of examples 14-19 or some other example herein, wherein the time domain resource allocation information further includes an indication of a start position for a first shared channel repetition and a start position for a second shared channel repetition.
- Example 21 may include an apparatus comprising means to perform one or more elements of a method described in or related to any of examples 1-20, or any other method or process described herein.
- Example 22 may include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of examples 1-20, or any other method or process described herein.
- Example 23 may include an apparatus comprising logic, modules, and/or circuitry to perform one or more elements of a method described in or related to any of examples 1-20, or any other method or process described herein.
- Example 24 may include a method, technique, or process as described in or related to any of examples 1-20, or portions or parts thereof.
- Example 25 may include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-20, or portions thereof.
- Example 26 may include a method of communicating in a wireless network as shown and described herein.
- Example 27 may include a system for providing wireless communication as shown and described herein.
- Example 28 may include a device for providing wireless communication as shown and described herein.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
Claims
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201862739030P | 2018-09-28 | 2018-09-28 | |
US201862743305P | 2018-10-09 | 2018-10-09 | |
PCT/US2019/053615 WO2020069416A1 (en) | 2018-09-28 | 2019-09-27 | Time-domain resource allocation for repeated transmissions in new radio |
Publications (2)
Publication Number | Publication Date |
---|---|
EP3858044A1 true EP3858044A1 (en) | 2021-08-04 |
EP3858044A4 EP3858044A4 (en) | 2022-06-29 |
Family
ID=69953385
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP19867863.3A Pending EP3858044A4 (en) | 2018-09-28 | 2019-09-27 | Time-domain resource allocation for repeated transmissions in new radio |
Country Status (3)
Country | Link |
---|---|
EP (1) | EP3858044A4 (en) |
CN (1) | CN112335308A (en) |
WO (1) | WO2020069416A1 (en) |
Families Citing this family (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN114070462B (en) * | 2020-07-31 | 2024-09-17 | 华为技术有限公司 | Method and device for repeated transmission |
CN115804188A (en) * | 2020-08-17 | 2023-03-14 | Oppo广东移动通信有限公司 | Data transmission method and equipment |
CN114696967A (en) * | 2020-12-31 | 2022-07-01 | 展讯通信(上海)有限公司 | Coverage enhancement method and device, chip and electronic equipment |
CN114765875A (en) * | 2021-01-15 | 2022-07-19 | 大唐移动通信设备有限公司 | Resource indication method, device and storage medium |
Family Cites Families (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8600413B2 (en) * | 2007-10-30 | 2013-12-03 | Qualcomm Incorporated | Control arrangement and method for communicating paging messages in a wireless communication system |
KR20150060118A (en) * | 2013-11-25 | 2015-06-03 | 주식회사 아이티엘 | Apparatus and method for transmitting harq ack/nack |
BR112016021616B1 (en) * | 2014-03-21 | 2023-04-18 | Huawei Technologies Co., Ltd | METHOD FOR TRANSMISSION OF CONTROL INFORMATION, METHOD FOR RECEIVING CONTROL INFORMATION, BASE STATION AND USER EQUIPMENT |
US10009153B2 (en) * | 2015-01-30 | 2018-06-26 | Motorola Mobility Llc | Apparatus and method for reception and transmission of control channels |
CN107409391B (en) * | 2015-03-31 | 2021-09-10 | 日本电气株式会社 | Method and apparatus for data transmission in wireless communication system |
CN107580797B (en) * | 2015-05-10 | 2020-12-22 | Lg 电子株式会社 | Method and apparatus for adapting repetition level for uplink transmission in wireless communication system |
KR20200020011A (en) * | 2015-08-21 | 2020-02-25 | 후아웨이 테크놀러지 컴퍼니 리미티드 | Wireless communication method, network device, user equipment, and system |
WO2018172136A1 (en) * | 2017-03-23 | 2018-09-27 | Fraunhofer-Gesellschaft zur Förderung der angewandten Forschung e.V. | Reliable data packet transmission among entities of a radio access network of a mobile communication network |
-
2019
- 2019-09-27 CN CN201980040349.9A patent/CN112335308A/en active Pending
- 2019-09-27 WO PCT/US2019/053615 patent/WO2020069416A1/en unknown
- 2019-09-27 EP EP19867863.3A patent/EP3858044A4/en active Pending
Also Published As
Publication number | Publication date |
---|---|
EP3858044A4 (en) | 2022-06-29 |
CN112335308A (en) | 2021-02-05 |
WO2020069416A1 (en) | 2020-04-02 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11778631B2 (en) | Transmission of group common PDCCH (physical downlink control channel) for NR (new radio) | |
US11984987B2 (en) | Prioritization of services for control and data transmission for new radio systems | |
US11140693B2 (en) | Handling overlapping of PUCCH and PUSCH for new radio systems | |
US11751216B2 (en) | Activation of secondary cell containing bandwidth parts | |
US11071170B2 (en) | Reg bundling size and dm-rs pattern for physical downlink control channel | |
US20240040598A1 (en) | Downlink control channel signaling for improved power consumption at a user equipment (ue) | |
US20220322315A1 (en) | Monitoring downlink control channels for unlicensed operation | |
US11057962B2 (en) | Systems and methods to report band combination capabilities in a telecommunication network | |
US20230139455A1 (en) | Frequency domain resource allocation for downlink (dl) and uplink (ul) in new radio (nr) | |
US20190261454A1 (en) | Handling radio resource control (rrc) configured channels and signals with conflict direction | |
US11038652B2 (en) | Concurrent transmission of acknowledgment and scheduling request information on a control channel | |
WO2020051152A1 (en) | UPLINK CONTROL INFORMATION (UCI) MULTIPLEXING ON MULTIPLE PHYSICAL UPLINK SHARED CHANNELS (PUSCHs) | |
US20210219166A1 (en) | Channel quality measurement reporting | |
US12040999B2 (en) | Sounding reference signal (SRS) transmission framework | |
WO2020069359A1 (en) | Physical uplink shared channel (pusch) repetition termination for new radio (nr) | |
WO2018192566A1 (en) | Method and apparatus for numerology configuration in non-coherent joint transmission | |
EP3858044A1 (en) | Time-domain resource allocation for repeated transmissions in new radio | |
WO2018064615A1 (en) | Capability notification for user equipment latency reduction | |
WO2020069428A1 (en) | Sequence-based uplink (ul) transmission cancellation for new radio (nr) | |
WO2017197086A1 (en) | Enabling sounding reference signal component carrier-based switching in wireless communication | |
US11695532B2 (en) | Transmission time interval (TTI) scheduling for physical uplink shared channel (PUSCH) transmissions | |
EP3857834A1 (en) | Management of transmit/receive switching gaps and automatic gain control adaptation for new radio |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE |
|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE |
|
17P | Request for examination filed |
Effective date: 20201216 |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
DAV | Request for validation of the european patent (deleted) | ||
DAX | Request for extension of the european patent (deleted) | ||
A4 | Supplementary search report drawn up and despatched |
Effective date: 20220530 |
|
RIC1 | Information provided on ipc code assigned before grant |
Ipc: H04L 1/18 20060101ALI20220523BHEP Ipc: H04W 72/12 20090101ALI20220523BHEP Ipc: H04W 72/04 20090101AFI20220523BHEP |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: EXAMINATION IS IN PROGRESS |
|
17Q | First examination report despatched |
Effective date: 20240627 |