EP4278530A1 - Abschwächung von zeitbereichsüberlappungen mit transportblock über mehrslot-übertragungen - Google Patents

Abschwächung von zeitbereichsüberlappungen mit transportblock über mehrslot-übertragungen

Info

Publication number
EP4278530A1
EP4278530A1 EP21920077.1A EP21920077A EP4278530A1 EP 4278530 A1 EP4278530 A1 EP 4278530A1 EP 21920077 A EP21920077 A EP 21920077A EP 4278530 A1 EP4278530 A1 EP 4278530A1
Authority
EP
European Patent Office
Prior art keywords
tboms
slot
pucch
overlaps
slots
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
Application number
EP21920077.1A
Other languages
English (en)
French (fr)
Inventor
Gang Xiong
Debdeep CHATTERJEE
Yingyang Li
Sergey Sosnin
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Intel Corp
Original Assignee
Intel Corp
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Intel Corp filed Critical Intel Corp
Publication of EP4278530A1 publication Critical patent/EP4278530A1/de
Pending legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0003—Two-dimensional division
    • H04L5/0005—Time-frequency
    • H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
    • H04L5/001—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT the frequencies being arranged in component carriers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0048—Allocation of pilot signals, i.e. of signals known to the receiver
    • H04L5/0051—Allocation of pilot signals, i.e. of signals known to the receiver of dedicated pilots, i.e. pilots destined for a single user or terminal

Definitions

  • Various embodiments generally may relate to the field of wireless communications. For example, some embodiments may relate to techniques for mitigation of time-domain overlaps related to transport block over multiple slot (TBoMS) transmissions.
  • TBoMS transport block over multiple slot
  • next generation wireless communication system which may be referred to as fifth generation (5G) or new radio (NR) will provide increased access to information and sharing of data by various users and applications.
  • 5G fifth generation
  • NR new radio
  • NR is expected to be a unified network/system that meets vastly different and sometime conflicting performance dimensions and services.
  • NR may evolve based on third generation partnership project (3 GPP) LTE- Advanced (LTE-A) with additional potential new Radio Access Technologies (RATs) to enrich people lives with better, simple and seamless wireless connectivity solutions.
  • 3 GPP third generation partnership project
  • LTE-A LTE- Advanced
  • RATs Radio Access Technologies
  • NR may be deployed at relatively higher carrier frequency in frequency range 1 (FR1), e.g., at 3.5 gigahertz (GHz). In this case, coverage loss may occur due to larger path-loss, which makes it more challenging to maintain an adequate quality of service.
  • FR1 frequency range 1
  • UE user equipment
  • FIG. 1 depicts an example of uplink control information (UCI) multiplexing on PUSCH.
  • UCI uplink control information
  • Figure 2 depicts an example of handling overlaps between a single-slot physical uplink control channel (PUCCH) and an TBoMS, in accordance with various embodiments.
  • PUCCH physical uplink control channel
  • Figure 3 depicts an alternative example of handling overlaps between a single-slot PUCCH and an TBoMS, in accordance with various embodiments.
  • Figure 4 depicts an alternative example of handling overlaps between a single-slot PUCCH and an TBoMS, in accordance with various embodiments.
  • Figure 5 depicts an alternative example of handling overlaps between a single-slot PUCCH and an TBoMS, in accordance with various embodiments.
  • Figure 6 depicts an example of handling overlaps between TBoMS and PUCCH with repetition, in accordance with various embodiments.
  • Figure 7 depicts an example of handling overlaps between single-slot PUCCH, PUSCH, and TBoMS, in accordance with various embodiments.
  • Figure 8 depicts an alternative example of handling overlaps between single-slot PUCCH, PUSCH, and TBoMS, in accordance with various embodiments.
  • Figure 9 depicts an example of UI multiplexed on a transmission occasion of TBoMS, in accordance with various embodiments.
  • Figure 10 depicts an example of collision handling between a TBoMS transmission and downlink (DL) symbols, in accordance with various embodiments.
  • Figure 11 depicts an example of collision handling between a TBoMS transmission and more than one PUCCH, in accordance with various embodiments.
  • Figure 12 depicts an alternative example of collision handling between a TBoMS transmission and more than one PUCCH, in accordance with various embodiments.
  • Figure 13 depicts an example of one technique for mitigation of time-domain overlap related to a TBoMS transmission.
  • Figure 14 depicts an alternative example of one technique for mitigation of time-domain overlap related to a TBoMS transmission.
  • Figure 15 depicts an alternative example of one technique for mitigation of time-domain overlap related to a TBoMS transmission.
  • Figure 16 schematically illustrates a wireless network in accordance with various embodiments.
  • Figure 17 schematically illustrates components of a wireless network in accordance with various embodiments.
  • Figure 18 schematically illustrates components of a wireless network in accordance with various embodiments.
  • Embodiments herein relate to mitigation of time-domain overlap related to transmission of a TBoMS.
  • the TBoMS may overlap with a scheduled physical uplink control channel (PUCCH) transmission.
  • PUCCH physical uplink control channel
  • all or part of the PUCCH transmission may be dropped.
  • uplink control information UCI
  • the TBoMS may overlap with scheduled downlink symbol transmission. In these embodiments, all or part of the TBoMS may be dropped.
  • Other embodiments may be presented.
  • PUSCH For NR, dynamic grant and configured grant based PUSCH transmission are supported.
  • DCI downlink control information
  • PUSCH is scheduled by downlink control information (DCI) format 0 0, 0 1 or 0 2.
  • DCI downlink control information
  • two types of configured grant PUSCH transmission are specified.
  • uplink (UL) data transmission is only based on radio resource control (RRC) (re)configuration without any layer 1 (LI) signaling.
  • RRC radio resource control
  • semi-static resource(s) may be configured for one UE, which may include time and frequency resource(s), modulation and coding scheme, reference signal, etc.
  • UL data transmission is based on both RRC configuration and LI signaling to activate/deactivate UL data transmission, which is similar to semi-persistent (SPS) uplink transmission as defined in legacy LTE specifications.
  • SPS semi-persistent
  • a number of repetitions can be configured for the transmission of PUSCH to help improve the coverage performance.
  • repetition is employed for the transmission of PUCCH and PUSCH, the same time domain resource allocation (TDRA) may be used in each slot. Further, inter-slot frequency hopping may be configured to improve the performance by exploiting frequency diversity.
  • release 16 the number of repetitions for PUSCH may be dynamically indicated in the DCI.
  • the UE may multiplex uplink control information (UCI) on the PUSCH and drop the PUCCH, as shown in Figure 1.
  • UCI uplink control information
  • the term “drop” refers to not transmitting a given set of data that was previously intended or scheduled to be transmitted.
  • Figure 1 depicts an example 100 of uplink control information (UCI) multiplexing on PUSCH.
  • the PUCCH 115 and PUSCH 120 may overlap within a given slot. Therefore, as shown at 110, the PUCCH 115 may be dropped (i.e., not transmitted) in the slot, and the UCI may be transmitted on the PUSCH at 125.
  • the UE may multiplex UCI on the PUSCH in the overlapped slot and drop the PUCCH.
  • a TB carried by a PUSCH scheduled within a slot or resource allocation of one data transmission is confined with a slot.
  • transport block size (TBS) is determined based on the number of resource elements (RE) in a slot.
  • a TB may span more than one slots, where a smaller number of physical resource blocks (PRBs) may be allocated in frequency so as to improve link budget for PUSCH transmission.
  • PRBs physical resource blocks
  • embodiments herein provide mechanisms for handling time-domain overlaps involving PUSCH with transport block spanning multiple slots.
  • embodiments include:
  • PUSCH transmission carrying a TB which spans more than one slots can be combined with PUSCH transmission with repetition or without repetition.
  • a PUSCH carrying a TB which spans multiple slots may be referred to herein as “multi-slot PUSCH,” “mPUSCH,” “TBoMS,” or “TBoMS PUSCH.”
  • the UE may multiplex UCI on the PUSCH and drop the PUCCH, as shown in the Figure 1, above. Further, when a single slot PUCCH overlaps with a multi-slot PUSCH repetition in a slot, and if the timeline requirement as defined in Section 9.2.5 in TS38.213 is satisfied for the overlapped slot, UE would multiplex UCI on the PUSCH in the overlapped slot and drop the PUCCH.
  • a transport block (TB) carried by a PUSCH is scheduled within a slot or resource allocation of one data transmission is confined with a slot.
  • transport block size (TBS) is determined based on the number of resource elements (RE) in a slot.
  • a transport block may span more than one slots, where a smaller number of physical resource blocks (PRBs) may be allocated in frequency so as to improve link budget for PUSCH transmission.
  • PRBs physical resource blocks
  • the UCI is multiplexed on the first slot of TBoMS transmission, and PUCCH is dropped in the overlapped slot. Further, in the slots other than the first slot, TBoMS is transmitted without UCI. Note that for this option, the timeline requirement may be defined in accordance with the first symbol in the first slot of the TBoMS spanning multiple slots and the first symbol of PUCCH.
  • UCI is only multiplexed in the first slot of TBoMS.
  • the amount of resource allocated for UCI is determined in accordance with the amount of resource allocated in the first slot for TBoMS transmission.
  • Figure 2 illustrates one example 200 of handling overlaps between a single slot PUCCH and TBoMS.
  • UCI is only multiplexed on the TBoMS 205 in the first slot 210.
  • TBoMS 215 is transmitted in the second slot 220, and PUCCH 225 is dropped.
  • the amount of resource allocated for UCI is determined in accordance with the amount of resource allocated in the first slot 210 for TBoMS transmission.
  • TBoMS spans full slots in the following figures, the same design principle may be extended to the case when TBoMS spans partial slots.
  • the same time domain resource allocation is allocated in each slot for TBoMS spanning multiple slots.
  • the amount of resource allocated for UCI may be determined in accordance with the amount of resource allocated in all allocated slots for TBoMS transmission. In this case, the amount of the resource allocated for the UCI transmission may exceed the resource in one slot, which indicates that, when mapping from the first slot of the TBoMS, the UCI may be also multiplexed in the slots other than the first slot for TBoMS transmission.
  • Figure 3 illustrates one example 300 of handling overlaps between single slot PUCCH and TBoMS.
  • UCI is multiplexed on the TBoMS 305 and transmitted on the first slot 310 and second slot 320, and PUCCH 325 is dropped in the second slot 320.
  • the number of symbols for UCI may be larger than the number of symbols allocated for TBoMS in the first slot 310, which indicates that UCI may be also multiplexed in the second slot 320.
  • the total number of REs in all the slots that are allocated to the TBoMS may be used.
  • Q CK coded modulation symbols per layer for HARQ-ACK transmission
  • the number of REs for UL-SCH may be determined by multiplying the number of slots allocated for TBoMS and the number of REs for UL-SCH in each slot.
  • the code block size for UL-SCH may be determined by dividing the total number of code block sizes with the number of slots allocated for TBoMS.
  • UCI is multiplexed on the overlapped slot between PUCCH and TBoMS.
  • the amount of resources allocated for UCI is determined in accordance with the amount of resources allocated in the overlapped slot for TBoMS transmission.
  • the timeline requirement may be defined in accordance with the first symbol in the overlapped slot of the TBoMS spanning multiple slots and the first symbol of PUCCH.
  • the timeline requirement for this option may be defined considering the first symbol in the first slot of the TBoMS transmission. Such consideration may be necessary if the rate-matching operation for the TBoMS is performed considering the set of REs with UCI as not available.
  • UCI is multiplexed on the overlapped slot between PUCCH and TBoMS, and possibly the slots before or after the overlapped slot.
  • the amount of resources allocated for UCI is determined in accordance with the amount of resources allocated in the slots including and before or after overlapped slot for TBoMS transmission.
  • rate matching for PUSCH is performed assuming that the set of REs are available for PUSCH transmission. Consequently, the modulation symbols of UCI will puncture the modulation symbols of PUSCH on the set of REs. In another example, rate matching for PUSCH is performed assuming that the set of REs are not available for PUSCH transmission.
  • the UE may transmit the single slot PUCCH in the overlapped slot.
  • the timeline requirement may be defined in accordance with the first symbol in the first slot of the TBoMS spanning multiple slots and the first symbol of PUCCH.
  • Figure 4 illustrates one example 400 of handling overlaps between single slot PUCCH 425 and TBoMS 405 that spans a first slot 410 and a second slot 420.
  • the TBoMS 405 that spans the first slot 410 and the second slot 420 is dropped, and PUCCH 425 carrying UCI is transmitted.
  • the timeline requirement may be defined in accordance with the first symbol in the first slot of the TBoMS spanning multiple slots and the first symbol of PUCCH.
  • the timeline requirement may be defined in accordance with the first symbol in the overlapped slot for TBoMS spanning multiple slots and the first symbol of PUCCH.
  • the TBoMS in the overlapped slot and remaining slots after the overlapped slot is dropped.
  • PUCCH in the overlapped slot is transmitted.
  • the UE in addition to not transmitting TBoMS in the overlapping and subsequent slots, the UE may or may not (e.g., up to UE implementation) transmit the TBoMS in the slots preceding the overlapping slot, including the possibility of dropping of the entire TBoMS.
  • the timeline requirement may be defined in accordance with the first symbol in the overlapped slot for TBoMS spanning multiple slots and the first symbol of PUCCH.
  • Figure 5 illustrates one example 500 of handling overlaps between single slot PUCCH 525 and TBoMS 505.
  • TBoMS 505 carrying a TB spans 4 slots (510, 520, 530, and 540) and PUCCH 525 overlaps with the TBoMS 505 in slot #2 530.
  • Option 6 if the timeline requirement is satisfied, TBoMS 505 in slot #2 530 and slot #3 540 is dropped and PUCCH 525 is transmitted in slot #2 520.
  • rate matching for PUSCH may still be performed assuming all slots are available for PUSCH transmission.
  • rate matching for PUSCH may be done assuming the dropped slot(s) due to overlapped with PUCCH are not available for PUSCH transmission.
  • the timeline requirement may be defined in accordance with the first symbol of the first slot of the TBoMS.
  • the whole TBoMS spanning multiple slots is dropped.
  • UE shall transmit the PUCCH with repetition in the overlapped slots.
  • the timeline requirement may be defined in accordance with the first symbol in the first slot of the TBoMS spanning multiple slots and the first symbol of PUCCH.
  • Figure 6 illustrates one example 600 of handling overlaps between TBoMS and PUCCH with repetition.
  • TBoMS 605 carrying a TB spans 4 slots (610, 620, 630, and 640) and PUCCH 625 with repetition overlaps with the TBoMS 605 in slot #2 630 and #3 640. Based on this option, if the timeline requirement is satisfied, the whole TBoMS 605 is dropped and PUCCH 625 with repetition is transmitted.
  • the timeline requirement is defined with respect to the first symbol of the overlapping slot, and the UE is not expected to transmit TBoMS starting at least from the overlapping slot, but may not transmit the TBoMS in the one or more slot(s) preceding the overlapping slot.
  • the TBoMS repetition when TBoMS with repetition overlaps with single slot or multislot PUCCH, if the timeline requirement as defined in Section 9.2.5 in TS38.213 is satisfied, the TBoMS repetition, that includes the overlapped slot, is dropped and the single slot or multi-slot PUCCH is transmitted. Further, in one option, UE shall drop the TBoMS repetition without deferral. Alternatively, TBoMS is postponed until all the repetitions are reached.
  • the UE may not expect that TBoMS with repetitions overlap with PUCCH carrying HARQ-ACK feedback, with or without repetitions.
  • the TBoMS may be transmitted and the PUCCH transmissions dropped.
  • the PUCCH that is not transmitted may include all repetitions of the PUCCH or only the repetitions that overlap with the one or more TBoMS repetitions.
  • the UE when an TBoMS may overlap with another PUCCH, either of them with or without repetitions, the UE is expected to transmit the TBoMS and drop the PUCCH without multiplexing the corresponding UCI in the TBoMS.
  • the UE may be expected to transmit the TBoMS and drop the PUCCH without any UCI multiplexing in the TBoMS if the overlapping PUCCH is to convey one or more of: Scheduling Request (SR), periodic Channel State Information (P-CSI) feedback, semi-persistent CSI (SP-CSI) feedback, and HARQ-ACK feedback (which may be subject to additional conditions).
  • SR Scheduling Request
  • P-CSI periodic Channel State Information
  • SP-CSI semi-persistent CSI
  • HARQ-ACK feedback which may be subject to additional conditions.
  • the UE may be expected to transmit the TBoMS and drop the PUCCH without any UCI multiplexing in the TBoMS if the overlapping PUCCH is to convey HARQ-ACK feedback of more than two bits payload.
  • the UE may not expect an TBoMS to overlap in time with a PUCCH with payload of more than two bits HARQ-ACK feedback.
  • the UE may multiplex the UCI on a PUSCH which does not carry a TB spanning multiple slots. Further, UE drops the PUCCH and transmits TBoMS which spans multiple slots.
  • a UE transmits multiple PUSCHs in a slot on respective serving cells, that includes dynamic grant based TBoMS (DG-TBoMS) which spans multiple slots and configured grant PUSCH (CG-PUSCH), and if timeline requirement is satisfied, UE multiplexes the UCI in the CG-PUSCH and drops PUCCH. Further, UE transmits DG-TBoMS which spans multiple slots.
  • DG-TBoMS dynamic grant based TBoMS
  • CG-PUSCH configured grant PUSCH
  • a UE transmits multiple PUSCHs in a slot on respective serving cells that includes dynamic grant based PUSCH (DG-PUSCH) and configured grant TBoMS (CG-PUSCH) which spans multiple slots, and if timeline requirement is satisfied, UE multiplexes the UCI in the DG- PUSCH and drops PUCCH. Further, UE transmits CG- TBoMS which spans multiple slots.
  • DG-PUSCH dynamic grant based PUSCH
  • CG-PUSCH configured grant TBoMS
  • Figure 7 illustrates one example 700 of handling overlaps between single slot PUCCH 725, CG-PUSCH 720 and DG-TBoMS 715 which spans multiple slots.
  • DG-TBoMS 715 carrying a TB spans 2 slots 705 and 710. If the timeline requirement is satisfied, UE multiplexes UCI on CG-PUSCH at 730, and transmits DG-TBoMS 715 which spans 2 slots. Further, UE drops PUCCH 725 in the overlapped slot.
  • UE transmits multiple PUSCHs in a slot on respective serving cells and if timeline requirement is satisfied, UE multiplexes the UCI in a PUSCH of the serving cell with the smallest ServCelllndex which does not carry a TB spanning multiple slots. Further, UE drops PUCCH and transmits TBoMS which spans multiple slots.
  • Figure 8 illustrates one example 800 of handling overlaps between single slot PUCCH 825, PUSCH 820, and TBoMS 815 which spans multiple slots.
  • TBoMS 815 carrying a TB spans 2 slots 805 and 810. Further, TBoMS 815 is scheduled in CC#0 and single slot PUSCH 820 is scheduled in CC#1. If the timeline requirement is satisfied, UE multiplexes UCI on PUSCH at 830 on CC#1 and transmits TBoMS 815 which spans 2 slots. Further, UE drops PUCCH 825 in the overlapped slot.
  • UE transmits more than one PUSCHs in the slot on the serving cell with the smallest ServCelllndex, and if timeline requirement is satisfied, UE multiplexes the UCI in the earliest PUSCH in the slot which does not carry a TB spanning multiple slots. Further, UE drops PUCCH and transmits TBoMS which spans multiple slots.
  • TBoMS spanning multiple slots is always treated with a smaller priority index or low priority and it may not be possible to configure (for CG TBoMS) or indicate (for DG TBoMS) priority index 1 for TBoMS.
  • TBoMS spanning multiple slots overlaps with PUCCH and/or PUSCH with a larger priority index or high priority, and if the timeline requirement is satisfied, UE is expected to cancel the TBoMS transmissions in the slot when overlapping with the PUCCH/PUSCH transmission of larger priority index.
  • UE may drop the whole TBoMS which spans multiple slots. Alternatively, UE may only drop the TBoMS in the overlapped slot(s).
  • priority index 1 when priority index 1 is indicated or configured for transmission of TBoMS spanning multiple slots, and when a smaller priority index (priority index 0) is indicated for PUCCH carrying UCI or PUSCH with single slot transmission or another TBoMS, TBoMS spanning multiple slots is transmitted and PUCCH carrying UCI or PUSCH with single slot transmission or the other TBoMS with priority index 0 is cancelled.
  • TBoMS in a slot is overlapped with a downlink symbol that is indicated by tdd-UL-DL-ConfigurationCommon and/or tdd-UL-DL- ConfigurationDedicated, and/or by slot format indicator (SFI) in DCI format 2
  • SFI slot format indicator
  • TBoMS in the overlapping slot is dropped.
  • the minimum application time for dynamic SFI may be defined considering the first symbol of the TBoMS in the overlapping slot.
  • rate matching for PUSCH is still performed assuming all slots are available for PUSCH transmission.
  • rate matching for PUSCH is performed assuming the dropped slot(s) due to overlapped with PUCCH are not available for PUSCH transmission.
  • the minimum application time for dynamic SFI may be defined considering the first symbol of the TBoMS in the first slot allocated for the TBoMS.
  • TBoMS in a slot is overlapped with a downlink symbol that is indicated by tdd-UL-DL-ConfigurationCommon and/or tdd-UL-DL- ConfigurationDedicated, and/or by slot format indicator (SFI) in DCI 2
  • SFI slot format indicator
  • rate matching for TBoMS is still performed assuming all symbols in all the allocated slots are available for TBoMS transmission.
  • rate matching for TBoMS is performed assuming the overlapped symbols are not available for TBoMS transmission.
  • the UE may need to resume transmitting symbols of the TBoMS after a number of overlapping symbols/slots in which the TBoMS is not transmitted
  • the UE may need additional DL-to-UL switching time if it may switch to DL during the DL symbols to receive DL signals or channels.
  • switching time may not be available if the UE is to resume transmission from the symbol immediately following the DL symbols.
  • the UE may not transmit (e.g., via “puncturing” or via rate-matching) the TBoMS in one or more symbols immediately following a number of DL symbols that may overlap with a granted TBoMS.
  • the number of one or more symbols to accommodate the DL-to-UL switching time could be configured or specified as a function of subcarrier spacing (SCS) of the UL BWP in which the TBoMS is transmitted, or determined based on the DL-to-UL switching time specified in 3GPP TS 38.211, Table 4.3.2-3.
  • SCS subcarrier spacing
  • the techniques described herein may apply for a transmission occasion or a slot of TBoMS or a transmission duration of a TBoMS where redundancy version is refreshed. More specifically, when PUCCH overlaps with a transmission occasion of TBoMS, UCI is multiplexed on the TBoMS in the transmission occasion or the slot when the timeline requirement is satisfied and the PUCCH is dropped. Note that based on the aforementioned embodiments, the UCI may be multiplexed on TBoMS in the overlapped slot or transmission duration where redundancy version is refreshed.
  • Figure 9 illustrates one example 900 of handling overlapping between TBoMS and PUCCH.
  • the UCI is multiplexed on the overlapped transmission occasion, e.g., 1 st transmission occasion of the TBoMS 905 and the PUCCH 910 is dropped.
  • UE transmits the 2 nd transmission occasion of the TBoMS 915 without UCI multiplexing.
  • a transmission occasion or a slot or a transmission duration of a TBoMS where redundancy version is refreshed overlaps with a downlink symbol that is indicated by tdd-UL-DL-ConfigurationCommon and/or tdd-UL-DL- ConfigurationDedicated, and/or by slot format indicator (SFI) in DCI format 2 0 and/or SSB transmission, and/or CORESETO with TypeO-PDCCH CSS set and invalid UL symbols or cancellation indication (CI)
  • SFI slot format indicator
  • CI TypeO-PDCCH CSS set and invalid UL symbols or cancellation indication
  • Figure 10 illustrates one example of handling collision of TBoMS with DL symbols.
  • a first transmission occasion of a TBoMS 1005 overlaps with DL symbolslOlO.
  • the first transmission occasion of the TBoMS 1005 is dropped.
  • UE continues to transmit the 2 nd transmission occasion of the TBoMS 1015.
  • UCIs in more than one PUCCHs are grouped and multiplexed on the transmission occasion of the TBoMS or the TBoMS and the more than one PUCCHs are dropped.
  • the UCIs may be concatenated based on the rule as defined in Rel-15, e.g., first HARQ-ACK, then SR and CSI part 1 and part 2, if any.
  • Figure 11 illustrates one example 1100 of handling collision between TBoMS and more than one PUCCHs.
  • PUCCH #0 in a first slot and PUCCH #1 in a second slot overlap with a transmission occasion of a TBoMS or a TBoMS as shown at 1105. If the timeline requirement is satisfied, UCI#0 and #1 are multiplexed on the transmission occasion of the TBoMS or the TBoMS as shown at 1110.
  • Figure 12 illustrates one example 1200 of one example of handling collision between TBoMS and more than one PUCCHs.
  • PUCCH #0 in a first slot and PUCCH #1 in a second slot overlap with a transmission occasion of a TBoMS or a TBoMS as shown at 1205. If the timeline requirement is satisfied, UCI#0 is multiplexed on the transmission occasion of the TBoMS or the TBoMS in the first slot and UCI#1 is multiplexed on the transmission occasion of the TBoMS or the TBoMS in the second slot as shown at 1210.
  • this may also depend on the priority of the TBoMS and the PUCCHs.
  • the aforementioned embodiments can be straightforwardly extended to the case when a transmission occasion or a transmission duration of a TBoMS where redundancy version is refreshed or a TBoMS overlaps with a group of PUCCHs which includes more than one PUCCH in different slots.
  • Figure 13 depicts an example of one technique for mitigation of time-domain overlap related to a TBoMS transmission.
  • the technique may include determining, at 1305 by a UE, that one or more symbols overlap in time between a PUCCH and a TBoMS.
  • the technique may further include dropping, at 1310 by the UE based on satisfaction of the determination that the one or more symbols overlap, at least a portion of the TBoMS.
  • the technique may further include transmitting, at 1315 by the UE, the PUCCH.
  • Figure 14 depicts an alternative example of one technique for mitigation of time-domain overlap related to a TBoMS transmission.
  • the technique may include determining, at 1405 by a UE, that a slot in which a PUCCH is to be transmitted overlaps in time with a slot in which a TBoMS is to be transmitted.
  • the technique may further include dropping, at 1410 by the UE based on determination that the slot of the PUCCH overlaps in time with the slot in which the TBoMS is to be transmitted, the PUCCH.
  • the technique may further include multiplexing, at 1415 by the UE, UCI on a portion of the TBoMS.
  • the technique may further include transmitting, at 1420 by the UE, the TBoMS.
  • Figure 15 depicts an alternative example of one technique for mitigation of time-domain overlap related to a TBoMS transmission.
  • the technique may include determining, at 1505 by the UE, that a TBoMS overlaps in time at least one downlink symbol in a slot.
  • the technique may further include dropping, at 1510 by the UE based on the determination, a portion of the TBoMS that overlaps the downlink symbols.
  • FIGS 16-18 illustrate various systems, devices, and components that may implement aspects of disclosed embodiments.
  • FIG 16 illustrates a network 1600 in accordance with various embodiments.
  • the network 1600 may operate in a manner consistent with 3GPP technical specifications for LTE or 5G/NR systems.
  • 3GPP technical specifications for LTE or 5G/NR systems 3GPP technical specifications for LTE or 5G/NR systems.
  • the example embodiments are not limited in this regard and the described embodiments may apply to other networks that benefit from the principles described herein, such as future 3GPP systems, or the like.
  • the network 1600 may include a UE 1602, which may include any mobile or non-mobile computing device designed to communicate with a RAN 1604 via an over-the-air connection.
  • the UE 1602 may be communicatively coupled with the RAN 1604 by a Uu interface.
  • the UE 1602 may be, but is not limited to, a smartphone, tablet computer, wearable computer device, desktop computer, laptop computer, in-vehicle infotainment, in-car entertainment device, instrument cluster, head-up display device, onboard diagnostic device, dashtop mobile equipment, mobile data terminal, electronic engine management system, electronic/engine control unit, electronic/engine control module, embedded system, sensor, microcontroller, control module, engine management system, networked appliance, machine-type communication device, M2M or D2D device, loT device, etc.
  • the network 1600 may include a plurality of UEs coupled directly with one another via a sidelink interface.
  • the UEs may be M2M/D2D devices that communicate using physical sidelink channels such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc.
  • the UE 1602 may additionally communicate with an AP 1606 via an over-the-air connection.
  • the AP 1606 may manage a WLAN connection, which may serve to offload some/all network traffic from the RAN 1604.
  • the connection between the UE 1602 and the AP 1606 may be consistent with any IEEE 802.11 protocol, wherein the AP 1606 could be a wireless fidelity (Wi-Fi®) router.
  • the UE 1602, RAN 1604, and AP 1606 may utilize cellular- WLAN aggregation (for example, LWA/LWIP).
  • Cellular- WLAN aggregation may involve the UE 1602 being configured by the RAN 1604 to utilize both cellular radio resources and WLAN resources.
  • the RAN 1604 may include one or more access nodes, for example, AN 1608.
  • AN 1608 may terminate air-interface protocols for the UE 1602 by providing access stratum protocols including RRC, PDCP, RLC, MAC, and LI protocols. In this manner, the AN 1608 may enable data/voice connectivity between CN 1620 and the UE 1602.
  • the AN 1608 may be implemented in a discrete device or as one or more software entities running on server computers as part of, for example, a virtual network, which may be referred to as a CRAN or virtual baseband unit pool.
  • the AN 1608 be referred to as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc.
  • the AN 1608 may be a macrocell base station or a low power base station for providing femtocells, picocells or other like cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells.
  • the RAN 1604 may be coupled with one another via an X2 interface (if the RAN 1604 is an LTE RAN) or an Xn interface (if the RAN 1604 is a 5G RAN).
  • the X2/Xn interfaces which may be separated into control/user plane interfaces in some embodiments, may allow the ANs to communicate information related to handovers, data/context transfers, mobility, load management, interference coordination, etc.
  • the ANs of the RAN 1604 may each manage one or more cells, cell groups, component carriers, etc. to provide the UE 1602 with an air interface for network access.
  • the UE 1602 may be simultaneously connected with a plurality of cells provided by the same or different ANs of the RAN 1604.
  • the UE 1602 and RAN 1604 may use carrier aggregation to allow the UE 1602 to connect with a plurality of component carriers, each corresponding to a Pcell or Scell.
  • a first AN may be a master node that provides an MCG and a second AN may be secondary node that provides an SCG.
  • the first/second ANs may be any combination of eNB, gNB, ng-eNB, etc.
  • the RAN 1604 may provide the air interface over a licensed spectrum or an unlicensed spectrum.
  • the nodes may use LAA, eLAA, and/or feLAA mechanisms based on CA technology with PCells/Scells.
  • the nodes Prior to accessing the unlicensed spectrum, the nodes may perform medium/carrier-sensing operations based on, for example, a listen-before-talk (LBT) protocol.
  • LBT listen-before-talk
  • the UE 1602 or AN 1608 may be or act as a RSU, which may refer to any transportation infrastructure entity used for V2X communications.
  • An RSU may be implemented in or by a suitable AN or a stationary (or relatively stationary) UE.
  • An RSU implemented in or by: a UE may be referred to as a “UE-type RSU”; an eNB may be referred to as an “eNB-type RSU”; a gNB may be referred to as a “gNB-type RSU”; and the like.
  • an RSU is a computing device coupled with radio frequency circuitry located on a roadside that provides connectivity support to passing vehicle UEs.
  • the RSU may also include internal data storage circuitry to store intersection map geometry, traffic statistics, media, as well as applications/software to sense and control ongoing vehicular and pedestrian traffic.
  • the RSU may provide very low latency communications required for high speed events, such as crash avoidance, traffic warnings, and the like. Additionally or alternatively, the RSU may provide other cellular/WLAN communications services.
  • the components of the RSU may be packaged in a weatherproof enclosure suitable for outdoor installation, and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller or a backhaul network.
  • the RAN 1604 may be an LTE RAN 1610 with eNBs, for example, eNB 1612.
  • the LTE RAN 1610 may provide an LTE air interface with the following characteristics: SCS of 15 kHz; CP-OFDM waveform for DL and SC-FDMA waveform for UL; turbo codes for data and TBCC for control; etc.
  • the LTE air interface may rely on CSI-RS for CSI acquisition and beam management; PDSCH/PDCCH DMRS for PDSCH/PDCCH demodulation; and CRS for cell search and initial acquisition, channel quality measurements, and channel estimation for coherent demodulation/detection at the UE.
  • the LTE air interface may operating on sub-6 GHz bands.
  • the RAN 1604 may be an NG-RAN 1614 with gNBs, for example, gNB 1616, or ng-eNBs, for example, ng-eNB 1618.
  • the gNB 1616 may connect with 5G-enabled UEs using a 5GNR interface.
  • the gNB 1616 may connect with a 5G core through an NG interface, which may include an N2 interface or an N3 interface.
  • the ng-eNB 1618 may also connect with the 5G core through an NG interface, but may connect with a UE via an LTE air interface.
  • the gNB 1616 and the ng-eNB 1618 may connect with each other over an Xn interface.
  • the NG interface may be split into two parts, an NG user plane (NG-U) interface, which carries traffic data between the nodes of the NG-RAN 1614 and a UPF 1648 (e.g., N3 interface), and an NG control plane (NG-C) interface, which is a signaling interface between the nodes of the NG-RAN1614 and an AMF 1644 (e.g., N2 interface).
  • NG-U NG user plane
  • N3 interface e.g., N3 interface
  • N-C NG control plane
  • the NG-RAN 1614 may provide a 5G-NR air interface with the following characteristics: variable SCS; CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL; polar, repetition, simplex, and Reed-Muller codes for control and LDPC for data.
  • the 5G-NR air interface may rely on CSI-RS, PDSCH/PDCCH DMRS similar to the LTE air interface.
  • the 5G-NR air interface may not use a CRS, but may use PBCH DMRS for PBCH demodulation; PTRS for phase tracking for PDSCH; and tracking reference signal for time tracking.
  • the 5G-NR air interface may operating on FR1 bands that include sub-6 GHz bands or FR2 bands that include bands from 24.25 GHz to 52.6 GHz.
  • the 5G-NR air interface may include an SSB that is an area of a downlink resource grid that includes PSS/SSS/PBCH.
  • the 5G-NR air interface may utilize BWPs for various purposes.
  • BWP can be used for dynamic adaptation of the SCS.
  • the UE 1602 can be configured with multiple BWPs where each BWP configuration has a different SCS. When a BWP change is indicated to the UE 1602, the SCS of the transmission is changed as well.
  • Another use case example of BWP is related to power saving.
  • multiple BWPs can be configured for the UE 1602 with different amount of frequency resources (for example, PRBs) to support data transmission under different traffic loading scenarios.
  • a BWP containing a smaller number of PRBs can be used for data transmission with small traffic load while allowing power saving at the UE 1602 and in some cases at the gNB 1616.
  • a BWP containing a larger number of PRBs can be used for scenarios with higher traffic load.
  • the RAN 1604 is communicatively coupled to CN 1620 that includes network elements to provide various functions to support data and telecommunications services to customers/subscribers (for example, users of UE 1602).
  • the components of the CN 1620 may be implemented in one physical node or separate physical nodes.
  • NFV may be utilized to virtualize any or all of the functions provided by the network elements of the CN 1620 onto physical compute/storage resources in servers, switches, etc.
  • a logical instantiation of the CN 1620 may be referred to as a network slice, and a logical instantiation of a portion of the CN 1620 may be referred to as a network sub-slice.
  • the CN 1620 may be an LTE CN 1622, which may also be referred to as an EPC.
  • the LTE CN 1622 may include MME 1624, SGW 1626, SGSN 1628, HSS 1630, PGW 1632, and PCRF 1634 coupled with one another over interfaces (or “reference points”) as shown. Functions of the elements of the LTE CN 1622 may be briefly introduced as follows.
  • the MME 1624 may implement mobility management functions to track a current location of the UE 1602 to facilitate paging, bearer activation/deactivation, handovers, gateway selection, authentication, etc.
  • the SGW 1626 may terminate an SI interface toward the RAN and route data packets between the RAN and the LTE CN 1622.
  • the SGW 1626 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 SGSN 1628 may track a location of the UE 1602 and perform security functions and access control. In addition, the SGSN 1628 may perform inter-EPC node signaling for mobility between different RAT networks; PDN and S-GW selection as specified by MME 1624; MME selection for handovers; etc.
  • the S3 reference point between the MME 1624 and the SGSN 1628 may enable user and bearer information exchange for inter-3 GPP access network mobility in idle/active states.
  • the HSS 1630 may include a database for network users, including subscription-related information to support the network entities’ handling of communication sessions.
  • the HSS 1630 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.
  • An S6a reference point between the HSS 1630 and the MME 1624 may enable transfer of subscription and authentication data for authenticating/authorizing user access to the LTE CN 1620.
  • the PGW 1632 may terminate an SGi interface toward a data network (DN) 1636 that may include an application/content server 1638.
  • the PGW 1632 may route data packets between the LTE CN 1622 and the data network 1636.
  • the PGW 1632 may be coupled with the SGW 1626 by an S5 reference point to facilitate user plane tunneling and tunnel management.
  • the PGW 1632 may further include a node for policy enforcement and charging data collection (for example, PCEF).
  • the SGi reference point between the PGW 1632 and the data network 16 36 may be an operator external public, a private PDN, or an intra-operator packet data network, for example, for provision of IMS services.
  • the PGW 1632 may be coupled with a PCRF 1634 via a Gx reference point.
  • the PCRF 1634 is the policy and charging control element of the LTE CN 1622.
  • the PCRF 1634 may be communicatively coupled to the app/content server 1638 to determine appropriate QoS and charging parameters for service flows.
  • the PCRF 1632 may provision associated rules into a PCEF (via Gx reference point) with appropriate TFT and QCI.
  • the CN 1620 may be a 5GC 1640.
  • the 5GC 1640 may include an AUSF 1642, AMF 1644, SMF 1646, UPF 1648, NSSF 1650, NEF 1652, NRF 1654, PCF 1656, UDM 1658, and AF 1660 coupled with one another over interfaces (or “reference points”) as shown.
  • Functions of the elements of the 5GC 1640 may be briefly introduced as follows.
  • the AUSF 1642 may store data for authentication of UE 1602 and handle authentication- related functionality.
  • the AUSF 1642 may facilitate a common authentication framework for various access types.
  • the AUSF 1642 may exhibit an Nausf service-based interface.
  • the AMF 1644 may allow other functions of the 5GC 1640 to communicate with the UE 1602 and the RAN 1604 and to subscribe to notifications about mobility events with respect to the UE 1602.
  • the AMF 1644 may be responsible for registration management (for example, for registering UE 1602), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization.
  • the AMF 1644 may provide transport for SM messages between the UE 1602 and the SMF 1646, and act as a transparent proxy for routing SM messages.
  • AMF 1644 may also provide transport for SMS messages between UE 1602 and an SMSF.
  • AMF 1644 may interact with the AUSF 1642 and the UE 1602 to perform various security anchor and context management functions.
  • AMF 1644 may be a termination point of a RAN CP interface, which may include or be an N2 reference point between the RAN 1604 and the AMF 1644; and the AMF 1644 may be a termination point of NAS (Nl) signaling, and perform NAS ciphering and integrity protection.
  • AMF 1644 may also support NAS signaling with the UE 1602 over an N3 IWF interface.
  • the SMF 1646 may be responsible for SM (for example, session establishment, tunnel management between UPF 1648 and AN 1608); UE IP address allocation and management (including optional authorization); selection and control of UP function; configuring traffic steering at UPF 1648 to route traffic to proper destination; termination of interfaces toward policy control functions; controlling part of policy enforcement, charging, and QoS; lawful intercept (for SM events and interface to LI system); termination of SM parts of NAS messages; downlink data notification; initiating AN specific SM information, sent via AMF 1644 overN2 to AN 1608; and determining SSC mode of a session.
  • SM may refer to management of a PDU session, and a PDU session or “session” may refer to a PDU connectivity service that provides or enables the exchange of PDUs between the UE 1602 and the data network 1636.
  • the UPF 1648 may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point of interconnect to data network 1636, and a branching point to support multi-homed PDU session.
  • the UPF 1648 may also perform packet routing and forwarding, perform packet inspection, enforce the user plane part of policy rules, lawfully intercept packets (UP collection), perform traffic usage reporting, perform QoS handling for a user plane (e.g., packet filtering, gating, UL/DL rate enforcement), perform uplink traffic verification (e.g., SDF- to-QoS flow mapping), transport level packet marking in the uplink and downlink, and perform downlink packet buffering and downlink data notification triggering.
  • UPF 1648 may include an uplink classifier to support routing traffic flows to a data network.
  • the NSSF 1650 may select a set of network slice instances serving the UE 1602.
  • the NSSF 1650 may also determine allowed NSSAI and the mapping to the subscribed S-NSSAIs, if needed.
  • the NSSF 1650 may also determine the AMF set to be used to serve the UE 1602, or a list of candidate AMFs based on a suitable configuration and possibly by querying the NRF 1654.
  • the selection of a set of network slice instances for the UE 1602 may be triggered by the AMF 1644 with which the UE 1602 is registered by interacting with the NSSF 1650, which may lead to a change of AMF.
  • the NSSF 1650 may interact with the AMF 1644 via an N22 reference point; and may communicate with another NSSF in a visited network via an N31 reference point (not shown). Additionally, the NSSF 1650 may exhibit an Nnssf service-based interface.
  • the NEF 1652 may securely expose services and capabilities provided by 3 GPP network functions for third party, internal exposure/re-exposure, AFs (e.g., AF 1660), edge computing or fog computing systems, etc.
  • the NEF 1652 may authenticate, authorize, or throttle the AFs.
  • NEF 1652 may also translate information exchanged with the AF 1660 and information exchanged with internal network functions. For example, the NEF 1652 may translate between an AF-Service-Identifier and an internal 5GC information.
  • NEF 1652 may also receive information from other NFs based on exposed capabilities of other NFs. This information may be stored at the NEF 1652 as structured data, or at a data storage NF using standardized interfaces. The stored information can then be re-exposed by the NEF 1652 to other NFs and AFs, or used for other purposes such as analytics. Additionally, the NEF 1652 may exhibit an Nnef servicebased interface.
  • the NRF 1654 may support service discovery functions, receive NF discovery requests from NF instances, and provide the information of the discovered NF instances to the NF instances. NRF 1654 also maintains information of available NF instances and their supported services. As used herein, the terms “instantiate,” “instantiation,” and the like may refer to the creation of an instance, and an “instance” may refer to a concrete occurrence of an object, which may occur, for example, during execution of program code. Additionally, the NRF 1654 may exhibit the Nnrf service-based interface.
  • the PCF 1656 may provide policy rules to control plane functions to enforce them, and may also support unified policy framework to govern network behavior.
  • the PCF 1656 may also implement a front end to access subscription information relevant for policy decisions in a UDR of the UDM 1658.
  • the PCF 1656 exhibit an Npcf service-based interface.
  • the UDM 1658 may handle subscription-related information to support the network entities’ handling of communication sessions, and may store subscription data of UE 1602. For example, subscription data may be communicated via an N8 reference point between the UDM 1658 and the AMF 1644.
  • the UDM 1658 may include two parts, an application front end and a UDR.
  • the UDR may store subscription data and policy data for the UDM 1658 and the PCF 1656, and/or structured data for exposure and application data (including PFDs for application detection, application request information for multiple UEs 1602) for the NEF 1652.
  • the Nudr service-based interface may be exhibited by the UDR 221 to allow the UDM 1658, PCF 1656, and NEF 1652 to access a particular set of the stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to notification of relevant data changes in the UDR.
  • the UDM may include a UDM- FE, which is in charge of processing credentials, location management, subscription management and so on. Several different front ends may serve the same user in different transactions.
  • the UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identification handling, access authorization, registration/mobility management, and subscription management.
  • the UDM 1658 may exhibit the Nudm service-based interface.
  • the AF 1660 may provide application influence on traffic routing, provide access to NEF, and interact with the policy framework for policy control.
  • the 5GC 1640 may enable edge computing by selecting operator/3 rd party services to be geographically close to a point that the UE 1602 is attached to the network. This may reduce latency and load on the network.
  • the 5GC 1640 may select a UPF 1648 close to the UE 1602 and execute traffic steering from the UPF 1648 to data network 1636 via the N6 interface. This may be based on the UE subscription data, UE location, and information provided by the AF 1660. In this way, the AF 1660 may influence UPF (re)selection and traffic routing.
  • the network operator may permit AF 1660 to interact directly with relevant NFs. Additionally, the AF 1660 may exhibit an Naf service-based interface.
  • the data network 1636 may represent various network operator services, Internet access, or third party services that may be provided by one or more servers including, for example, application/content server 1638.
  • FIG 17 schematically illustrates a wireless network 1700 in accordance with various embodiments.
  • the wireless network 1700 may include a UE 1702 in wireless communication with an AN 1704.
  • the UE 1702 and AN 1704 may be similar to, and substantially interchangeable with, like-named components described elsewhere herein.
  • the UE 1702 may be communicatively coupled with the AN 1704 via connection 1706.
  • connection 1706 is illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols such as an LTE protocol or a 5G NR. protocol operating at mmWave or sub-6GHz frequencies.
  • cellular communications protocols such as an LTE protocol or a 5G NR. protocol operating at mmWave or sub-6GHz frequencies.
  • the UE 1702 may include a host platform 1708 coupled with a modem platform 1710.
  • the host platform 1708 may include application processing circuitry 1712, which may be coupled with protocol processing circuitry 1714 of the modem platform 1710.
  • the application processing circuitry 1712 may run various applications for the UE 1702 that source/sink application data.
  • the application processing circuitry 1712 may further implement one or more layer operations to transmit/receive application data to/from a data network. These layer operations may include transport (for example UDP) and Internet (for example, IP) operations
  • the protocol processing circuitry 1714 may implement one or more of layer operations to facilitate transmission or reception of data over the connection 1706.
  • the layer operations implemented by the protocol processing circuitry 1714 may include, for example, MAC, RLC, PDCP, RRC and NAS operations.
  • the modem platform 1710 may further include digital baseband circuitry 1716 that may implement one or more layer operations that are “below” layer operations performed by the protocol processing circuitry 1714 in a network protocol stack. These operations may include, for example, PHY operations including one or more of HARQ-ACK functions, scrambling/descrambling, encoding/decoding, layer mapping/de-mapping, modulation symbol mapping, received symbol/bit metric determination, multi-antenna port precoding/decoding, which may include one or more of space-time, space-frequency or spatial coding, reference signal generation/detection, preamble sequence generation and/or decoding, synchronization sequence generation/detection, control channel signal blind decoding, and other related functions.
  • PHY operations including one or more of HARQ-ACK functions, scrambling/descrambling, encoding/decoding, layer mapping/de-mapping, modulation symbol mapping, received symbol/bit metric determination, multi-antenna port precoding/decoding, which may
  • the modem platform 1710 may further include transmit circuitry 1718, receive circuitry 1720, RF circuitry 1722, and RF front end (RFFE) 1724, which may include or connect to one or more antenna panels 1726.
  • the transmit circuitry 1718 may include a digital -to-analog converter, mixer, intermediate frequency (IF) components, etc.
  • the receive circuitry 1720 may include an analog-to-digital converter, mixer, IF components, etc.
  • the RF circuitry 1722 may include a low-noise amplifier, a power amplifier, power tracking components, etc.
  • RFFE 1724 may include filters (for example, surface/bulk acoustic wave filters), switches, antenna tuners, beamforming components (for example, phase-array antenna components), etc.
  • transmit/receive components may be specific to details of a specific implementation such as, for example, whether communication is TDM or FDM, in mmWave or sub-6 gHz frequencies, etc.
  • the transmit/receive components may be arranged in multiple parallel transmit/receive chains, may be disposed in the same or different chips/modules, etc.
  • the protocol processing circuitry 1714 may include one or more instances of control circuitry (not shown) to provide control functions for the transmit/receive components.
  • a UE reception may be established by and via the antenna panels 1726, RFFE 1724, RF circuitry 1722, receive circuitry 1720, digital baseband circuitry 1716, and protocol processing circuitry 1714.
  • the antenna panels 1726 may receive a transmission from the AN 1704 by receive-beamforming signals received by a plurality of antennas/antenna elements of the one or more antenna panels 1726.
  • a UE transmission may be established by and via the protocol processing circuitry 1714, digital baseband circuitry 1716, transmit circuitry 1718, RF circuitry 1722, RFFE 1724, and antenna panels 1726.
  • the transmit components of the UE 1704 may apply a spatial filter to the data to be transmitted to form a transmit beam emitted by the antenna elements of the antenna panels 1726.
  • the AN 1704 may include a host platform 1728 coupled with a modem platform 1730.
  • the host platform 1728 may include application processing circuitry 1732 coupled with protocol processing circuitry 1734 of the modem platform 1730.
  • the modem platform may further include digital baseband circuitry 1736, transmit circuitry 1738, receive circuitry 1740, RF circuitry 1742, RFFE circuitry 1744, and antenna panels 1746.
  • the components of the AN 1704 may be similar to and substantially interchangeable with like- named components of the UE 1702.
  • the components of the AN 1708 may perform various logical functions that include, for example, RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling.
  • Figure 18 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.
  • Figure 18 shows a diagrammatic representation of hardware resources 1800 including one or more processors (or processor cores) 1810, one or more memory/storage devices 1820, and one or more communication resources 1830, each of which may be communicatively coupled via a bus 1840 or other interface circuitry.
  • a hypervisor 1802 may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 1800.
  • the processors 1810 may include, for example, a processor 1812 and a processor 1814.
  • the processors 1810 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a DSP such as a baseband processor, an ASIC, an FPGA, a radiofrequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.
  • CPU central processing unit
  • RISC reduced instruction set computing
  • CISC complex instruction set computing
  • GPU graphics processing unit
  • DSP such as a baseband processor, an ASIC, an FPGA, a radiofrequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.
  • the memory/storage devices 1820 may include main memory, disk storage, or any suitable combination thereof.
  • the memory/storage devices 1820 may include, but are not limited to, any type of volatile, non-volatile, or semi-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 1830 may include interconnection or network interface controllers, components, or other suitable devices to communicate with one or more peripheral devices 1804 or one or more databases 1806 or other network elements via a network 1808.
  • the communication resources 1830 may include wired communication components (e.g., for coupling via USB, Ethernet, etc.), cellular communication components, NFC components, Bluetooth® (or Bluetooth® Low Energy) components, Wi-Fi® components, and other communication components.
  • Instructions 1850 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 1810 to perform any one or more of the methodologies discussed herein.
  • the instructions 1850 may reside, completely or partially, within at least one of the processors 1810 (e.g., within the processor’s cache memory), the memory/storage devices 1820, or any suitable combination thereof.
  • any portion of the instructions 1850 may be transferred to the hardware resources 1800 from any combination of the peripheral devices 1804 or the databases 1806. Accordingly, the memory of processors 1810, the memory/storage devices 1820, the peripheral devices 1804, and the databases 1806 are examples of computer-readable and machine-readable media.
  • At least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and/or methods as set forth in the example section below.
  • the baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below.
  • circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below in the example section.
  • Example 1 may include a method of wireless communication for a fifth generation (5G) or new radio (NR) system, the method comprising: determining, by a UE, overlaps at least in one symbol between a physical uplink control channel (PUCCH) and a multi-slot physical uplink shared channel (TBoMS) carrying a transport block (TB) which spans more than one slots; dropping, by the UE, the TBoMS carrying the TB which spans more than one slots if timeline requirement is satisfied; and transmitting, by the UE, the PUCCH.
  • 5G fifth generation
  • NR new radio
  • Example 2 may include the method of example 1 or some other example herein, wherein when TBoMS and single slot PUCCH overlap in time, if the timeline requirement is satisfied, uplink control information (UCI) is multiplexed on the first slot of TBoMS transmission, and PUCCH is dropped in the overlapped slot.
  • Example 3 may include the method of example 1 or some other example herein, wherein the timeline requirement may be defined in accordance with the first symbol in the first slot of the TBoMS spanning multiple slots and the first symbol of PUCCH.
  • Example 4 may include the method of example 1 or some other example herein, wherein UCI is only multiplexed in the first slot of TBoMS.
  • Example 5 may include the method of example 1 or some other example herein, wherein the amount of resource allocated for UCI is determined in accordance with the amount of resource allocated in the all slots for TBoMS transmission.
  • Example 6 may include the method of example 1 or some other example herein, wherein UCI is multiplexed on the overlapped slot between PUCCH and TBoMS.
  • Example 7 may include the method of example 1 or some other example herein, wherein UCI is multiplexed on the overlapped slot between PUCCH and TBoMS and possibly the slots after the overlapped slot.
  • Example 8 may include the method of example 1 or some other example herein, wherein when TBoMS and single slot PUCCH overlap in time, if the timeline requirement is satisfied, the whole TBoMS spanning multiple slots is dropped, wherein UE shall transmit the single slot PUCCH in the overlapped slot.
  • Example 9 may include the method of example 1 or some other example herein, wherein when TBoMS and single slot PUCCH overlap in time, if the timeline requirement is satisfied, single slot PUCCH in the overlapped slot is dropped and TBoMS which spans multiple slots is transmitted.
  • Example 10 may include the method of example 1 or some other example herein, wherein when TBoMS and single slot PUCCH overlap in time, if the timeline requirement is satisfied in the overlapped slot, the TBoMS in the overlapped slot is dropped, wherein PUCCH in the overlapped slot is transmitted.
  • Example 11 may include the method of example 1 or some other example herein, wherein TBoMS in the overlapped slot and remaining slots after the overlapped slot is dropped.
  • Example 12 may include the method of example 1 or some other example herein, wherein when TBoMS and PUCCH with repetition overlap in time, if the timeline requirement is satisfied, the whole TBoMS spanning multiple slots is dropped.
  • Example 13 may include the method of example 1 or some other example herein, wherein when TBoMS and PUCCH with repetition overlap in time, if the timeline requirement is satisfied, the TBoMS in the overlapped slots is dropped and PUCCH with repetition is transmitted in the overlapped slots.
  • Example 14 may include the method of example 1 or some other example herein, wherein when TBoMS with repetition overlaps with single slot or multi-slot PUCCH, if the timeline requirement is satisfied, the TBoMS repetition, that includes the overlapped slot, is dropped and the single slot or multi-slot PUCCH is transmitted.
  • Example 15 may include the method of example 1 or some other example herein, wherein when an TBoMS may overlap with another PUCCH, either of them with or without repetitions, the UE is expected to transmit the TBoMS and drop the PUCCH without multiplexing the corresponding UCI in the TBoMS
  • Example 16 may include the method of example 1 or some other example herein, wherein when single slot PUCCH overlaps with multiple PUSCHs in different serving cells or in different symbols in a slot, if the timeline requirement is satisfied, and if multiple PUSCHs include TBoMS which spans multiple slots, UE multiplexes the UCI on a PUSCH which does not carry a TB spanning multiple slots. Further, UE drops the PUCCH and transmits TBoMS which spans multiple slots.
  • Example 17 may include the method of example 1 or some other example herein, wherein if a UE transmits multiple PUSCHs in a slot on respective serving cells, that includes dynamic grant based TBoMS (DG- TBoMS) which spans multiple slots and configured grant PUSCH (CG-PUSCH), and if timeline requirement is satisfied, UE multiplexes the UCI in the CG-PUSCH and drops PUCCH
  • DG- TBoMS dynamic grant based TBoMS
  • CG-PUSCH configured grant PUSCH
  • Example 18 may include the method of example 1 or some other example herein, wherein if a UE transmits multiple PUSCHs in a slot on respective serving cells and if timeline requirement is satisfied, UE multiplexes the UCI in a PUSCH of the serving cell with the smallest ServCelllndex which does not carry a TB spanning multiple slots.
  • Example 19 may include the method of example 1 or some other example herein, wherein if the UE transmits more than one PUSCHs in the slot on the serving cell with the smallest ServCelllndex, and if timeline requirement is satisfied, UE multiplexes the UCI in the earliest PUSCH in the slot which does not carry a TB spanning multiple slots.
  • Example 20 may include the method of example 1 or some other example herein, wherein TBoMS spanning multiple slots is always treated with a smaller priority index and it is not possible to configure (for CG TBoMS) or indicate (for DG TBoMS) priority index 1 for TBoMS.
  • Example 21 may include the method of example 1 or some other example herein, wherein when TBoMS spanning multiple slots overlaps with PUCCH and/or PUSCH with a larger priority index, and if the timeline requirement is satisfied, UE is expected to cancel the TBoMS transmissions before the first symbol overlapping with the PUCCH/PUSCH transmission of larger priority index.
  • Example 22 may include the method of example 1 or some other example herein, wherein when priority index 1 is indicated or configured for transmission of TBoMS spanning multiple slots, and when a smaller priority index (priority index 0) is indicated for PUCCH carrying UCI or PUSCH with single slot transmission or another TBoMS, TBoMS spanning multiple slots is transmitted and PUCCH carrying UCI or PUSCH with single slot transmission or the other TBoMS with priority index 0 is cancelled.
  • priority index 0 priority index
  • Example 23 may include the method of example 1 or some other example herein, wherein if the TBoMS in a slot is overlapped with a downlink symbol that is indicated by tdd- UL-DL-ConfigurationCommon and/or tdd-UL-DL-ConfigurationDedicated, and/or by slot format indicator (SFI) in DCI format 2 0, TBoMS in the overlapping slot is dropped.
  • SFI slot format indicator
  • Example 24 may include the method of example 1 or some other example herein, wherein if the TBoMS in a slot is overlapped with a downlink symbol that is indicated by tdd- UL-DL-ConfigurationCommon and/or tdd-UL-DL-ConfigurationDedicated, and/or by slot format indicator (SFI) in DCI 2 0, TBoMS in the symbols that overlapped with the downlink symbols is dropped.
  • SFI slot format indicator
  • Example 25 may include the method of example 1 or some other example herein, wherein the above embodiments may apply for a transmission occasion or a slot of TBoMS or a transmission duration of a TBoMS where redundancy version is refreshed.
  • Example 26 may include the method of example 1 or some other example herein, wherein when PUCCH overlaps with a transmission occasion of TBoMS, UCI is multiplexed on the TBoMS in the transmission occasion or the slot when the timeline requirement is satisfied and the PUCCH is dropped.
  • Example 27 may include the method of example 1 or some other example herein, wherein when a transmission occasion or a slot or a transmission duration of a TBoMS where redundancy version is refreshed overlaps with a downlink symbol that is indicated by tdd-UL- DL-ConfigurationCommon and/or tdd-UL-DL-ConfigurationDedicated, and/or by slot format indicator (SFI) in DCI format 2 0 and/or SSB transmission, and/or CORESETO with TypeO- PDCCH CSS set and invalid UL symbols or cancellation indication (CI), the transmission occasion or the slot or the transmission duration of the TBoMS is dropped, while the remaining of the transmission occasion or the slot or the transmission duration of the TBoMS is still transmitted.
  • SFI slot format indicator
  • CI TypeO- PDCCH CSS set and invalid UL symbols or cancellation indication
  • Example 28 may include the method of example 1 or some other example herein, wherein when a transmission occasion or a transmission duration of a TBoMS where redundancy version is refreshed or a TBoMS overlaps with a group of PUCCHs which includes more than one PUCCH in different slots, and if the timeline requirement is satisfied, UCIs in more than one PUCCHs are grouped and multiplexed on the transmission occasion of the TBoMS or the TBoMS and the more than one PUCCHs are dropped.
  • Example 29 may include the method of example 1 or some other example herein, wherein when a transmission occasion or a transmission duration of a TBoMS where redundancy version is refreshed or a TBoMS overlaps with a group of PUCCHs which includes more than one PUCCH in different slots, and if the timeline requirement is satisfied, UCI in a first PUCCH is multiplexed on the TBoMS in a first slot and UCI in a second PUCCH is multiplexed on the TBoMS in a second slot, and the more than one PUCCHs are dropped.
  • Example 30 may include a method comprising: determining that one or more symbols overlap between a physical uplink control channel (PUCCH) and an uplink transport block (TB) which spans multiple slots (TBoMS); dropping transmission of all or part of the TBoMS if a timeline requirement is satisfied; and transmitting the PUCCH.
  • PUCCH physical uplink control channel
  • TB uplink transport block
  • ToMS multiple slots
  • Example 31 may include the method of example 30 or some other example herein, wherein the TBoMS is a multi-slot PUSCH (TBoMS).
  • TBoMS multi-slot PUSCH
  • Example 32 may include a method comprising: determining that a slot of a scheduled PUCCH overlaps in time with a transport block that spans multiple slots (TBoMS); multiplexing uplink control information (UCI) on to a slot of the TBoMS for transmission; and dropping transmission of the PUCCH in the overlapped slot.
  • TBoMS transport block that spans multiple slots
  • UCI uplink control information
  • Example 33 may include the method of example 32 or some other example herein, wherein the UCI is multiplexed if a timeline requirement is satisfied.
  • Example 34 may include the method of example 32-33 or some other example herein, wherein UCI is only multiplexed in one slot of TBoMS.
  • Example 35 may include the method of example 32-34 or some other example herein, wherein UCI is multiplexed on the slot that overlaps between the PUCCH and the TBoMS.
  • Example 36 may include the method of example 32-35 or some other example herein, wherein if the TBoMS in a slot is overlapped with a downlink symbol that is indicated by tdd- UL-DL-ConfigurationCommon and/or tdd-UL-DL-ConfigurationDedicated, and/or by slot format indicator (SFI) in DCI 2 0, TBoMS in the symbols that overlapped with the downlink symbols is dropped.
  • SFI slot format indicator
  • Example 37 may include the method of example 32-36 or some other example herein, wherein the scheduled PUCCH overlaps with a transmission occasion or a slot of the TBoMS or a transmission duration of the TBoMS where redundancy version is refreshed.
  • Example 38 may include the method of example 32-37 or some other example herein, wherein the PUCCH overlaps with a transmission occasion of the TBoMS, and wherein the UCI is multiplexed on the TBoMS in the transmission occasion or the slot when a timeline requirement is satisfied.
  • Example 39 may include the method of example 32-38 or some other example herein, wherein the TBoMS is a multi-slot PUSCH (TBoMS).
  • TBoMS multi-slot PUSCH
  • Example 40 may include the method of example 30-39 or some other example herein, wherein the method is performed by a UE or a portion thereof.
  • Example 41 includes a method to be performed by a user equipment (UE) in a wireless network, the method comprising: determining, by the UE, that one or more symbols overlap in time between a physical uplink control channel (PUCCH) and a transport block (TB) which spans multiple slots (TBoMS); dropping, by the UE based on satisfaction of the determination that the one or more symbols overlap, at least a portion of the TBoMS; and transmitting, by the UE, the PUCCH.
  • PUCCH physical uplink control channel
  • TB transport block
  • TBoMS transport block
  • Example 41 includes a method to be performed by a user equipment (UE) in a wireless network, the method comprising: determining, by the UE, that one or more symbols overlap in time between a physical uplink control channel (PUCCH) and a transport block (TB) which spans multiple slots (TBoMS); dropping, by the UE based on satisfaction of the determination that the one or more symbols overlap, at least a portion of the TBo
  • Example 42 includes the method of example 41, or some other example herein, wherein the TBoMS is a multi-slot PUSCH (TBoMS).
  • TBoMS multi-slot PUSCH
  • Example 43 includes the method of example 41, or some other example herein, further comprising: identifying, by the UE, that a timeline is satisfied; and dropping, by the UE, the at least the portion of the TBoMS based on the determination that the one or more symbols overlap and the determination that the timeline is satisfied.
  • Example 44 includes the method of any of examples 41-43, or some other example herein, wherein the at least the portion of the TBoMS is a subset of slots of the TBoMS that is less than all slots of the TBoMS.
  • Example 45 includes the method of any of examples 41-43, or some other example herein, wherein the at least the portion of the TBoMS is all slots of the TBoMS.
  • Example 46 includes the method of any of examples 41-43, or some other example herein, further comprising transmitting, by the UE, the TBoMS in a slot that is different than a slot in which the PUCCH overlaps the TBoMS.
  • Example 47 includes the method of any of examples 41-43, or some other example herein, further comprising transmitting, by the UE, the PUCCH in a plurality of slots.
  • Example 48 includes a method to be performed by a user equipment (UE) in a wireless network, the method comprising: determining, by the UE, that a slot of a scheduled physical uplink control channel (PUCCH) overlaps in time with a transport block that spans multiple slots (TBoMS); multiplexing, by the UE based on the determination, uplink control information (UCI) onto a slot of the TBoMS for transmission; dropping, by the UE, transmission of the PUCCH in the overlapped slot; and transmitting, by the UE, the TBoMS.
  • UE user equipment
  • Example 49 includes the method of example 48, or some other example herein, wherein the TBoMS is a multi-slot PUSCH (TBoMS).
  • TBoMS multi-slot PUSCH
  • Example 50 includes the method of example 48, or some other example herein, further comprising: identifying, by the UE, that a timeline is satisfied; and multiplexing, by the UE, the UCI based on the determination that the slot of the PUCCH overlaps in time with the transport block and the determination that the timeline is satisfied.
  • Example 51 includes the method of any of examples 48-50, or some other example herein, further comprising multiplexing, by the UE, the UCI onto only one slot of the TBoMS.
  • Example 52 includes the method of any of examples 48-50, or some other example herein, further comprising: transmitting, by the UE, the TBoMS with the UCI multiplexed thereon in a slot that is different than the slot in which the PUCCH overlaps in time with the TBoMS; and transmitting, by the UE, the TBoMS without the multiplexed thereon in the slot in which the PUCCH overlaps in time with the TBoMS.
  • Example 53 includes the method of any of examples 48-50, or some other example herein, wherein the TBoMS is a transmission occasion of the TBoMS.
  • Example 54 includes the method of any of examples 48-50, or some other example herein, wherein the TBoMS is a TBoMS in which the redundancy version is refreshed.
  • Example 55 includes a method to be performed by a user equipment (UE) in a wireless network, the method comprising: determining, by the UE, that a transport block (TB) which spans multiple slots (TBoMS) overlaps in time at least one downlink symbol in a slot; and dropping, by the UE based on the determination, a portion of the TBoMS that overlaps the downlink symbols.
  • UE user equipment
  • Example 56 includes the method of example 55, or some other example herein, wherein the at least one downlink symbol is indicated by tdd-UL-DL-Configuration Common.
  • Example 57 includes the method of example 55, or some other example herein, wherein the at least one downlink symbol is indicated by tdd-UL-DL-ConfigurationDedicated.
  • Example 58 includes the method of example 55, or some other example herein, wherein the at least one downlink symbol is indicated by a slot format indicator (SFI) in downlink control information (DCI).
  • SFI slot format indicator
  • DCI downlink control information
  • Example 59 includes the method of any of examples 55-58, or some other example herein, wherein the TBoMS is a multi-slot PUSCH (TBoMS).
  • TBoMS multi-slot PUSCH
  • Example 60 includes the method of any of examples 55-58, or some other example herein, further comprising dropping, by the UE, the TBoMS in the slot; and transmitting, by the UE, the TBoMS in a slot that is different than a slot in which the TBoMS overlaps the at least one downlink symbol.
  • Example 61 includes a method to be performed by a user equipment (UE) in a wireless network, the method comprising: determining, by the UE, that a slot in which a physical uplink control channel (PUCCH) is to be transmitted overlaps in time with a slot in which a transport block (TB) which spans multiple slots (TBoMS) is to be transmitted; dropping, by the UE based on determination that the slot of the PUCCH overlaps in time with the slot in which the TBoMS is to be transmitted, the PUCCH; multiplexing, by the UE, uplink control information (UCI) on a portion of the TBoMS; and transmitting, by the UE, the TBoMS.
  • PUCCH physical uplink control channel
  • TB transport block
  • TBoMS transport block
  • Example 62 includes the method of example 61, or some other example herein wherein the portion of the TBoMS is a subset of slots of the TBoMS that is less than all allocated slots of the TBoMS.
  • Example 63 includes the method of example 61, or some other example herein, wherein the portion of the TBoMS is all allocated slots of the TBoMS.
  • Example 64 includes the method of any of examples 61-63, or some other example herein, wherein the portion of the TBoMS is a portion of the TBoMS in the slot that overlaps in time with the slot in which the PUCCH was to be transmitted.
  • Example 65 includes the method of any of examples 61-63, or some other example herein, wherein the portion of the TBoMS is a portion of the TBoMS in a slot that is different than the slot that overlaps in time with the slot in which the PUCCH was to be transmitted.
  • Example 66 includes the method of any of examples 61-63, or some other example herein, further comprising determining, by the UE, a number of resource elements (RE) for the UCI based on a number of slots allocated for the TBoMS.
  • RE resource elements
  • Example 67 includes the method of any of examples 61-63, or some other example herein, wherein determining that the slot in which the PUCCH is to be transmitted overlaps in time with a slot in which the TBoMS is to be transmitted includes determining, by the UE, that a timeline requirement is satisfied.
  • Example 68 includes the method of example 67, or some other example herein, wherein the timeline requirement is based on a first symbol of the PUCCH and a first symbol of the TBoMS.
  • Example 69 may include an apparatus comprising means to perform one or more elements of a method described in or related to any of examples 1-68, or any other method or process described herein.
  • Example 70 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-68, or any other method or process described herein.
  • Example 71 may include an apparatus comprising logic, modules, or circuitry to perform one or more elements of a method described in or related to any of examples 1-68, or any other method or process described herein.
  • Example 72 may include a method, technique, or process as described in or related to any of examples 1-68, or portions or parts thereof.
  • Example 73 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-68, or portions thereof.
  • Example 74 may include a signal as described in or related to any of examples 1-68, or portions or parts thereof.
  • Example 75 may include a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples 1-68, or portions or parts thereof, or otherwise described in the present disclosure.
  • PDU protocol data unit
  • Example 76 may include a signal encoded with data as described in or related to any of examples 1-68, or portions or parts thereof, or otherwise described in the present disclosure.
  • Example 77 may include a signal encoded with a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples 1-68, or portions or parts thereof, or otherwise described in the present disclosure.
  • PDU protocol data unit
  • Example 78 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors is to cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-68, or portions thereof.
  • Example 79 may include a computer program comprising instructions, wherein execution of the program by a processing element is to cause the processing element to carry out the method, techniques, or process as described in or related to any of examples 1-68, or portions thereof.
  • Example 80 may include a signal in a wireless network as shown and described herein.
  • Example 81 may include a method of communicating in a wireless network as shown and described herein.
  • Example 82 may include a system for providing wireless communication as shown and described herein.
  • Example 83 may include a device for providing wireless communication as shown and described herein.
  • circuitry refers to, is part of, or includes hardware components such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) and/or memory (shared, dedicated, or group), an Application Specific Integrated Circuit (ASIC), a field-programmable device (FPD) (e.g., a field-programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high-capacity PLD (HCPLD), a structured ASIC, or a programmable SoC), digital signal processors (DSPs), etc., that are configured to provide the described functionality.
  • FPD field-programmable device
  • FPGA field-programmable gate array
  • PLD programmable logic device
  • CPLD complex PLD
  • HPLD high-capacity PLD
  • DSPs digital signal processors
  • the circuitry may execute one or more software or firmware programs to provide at least some of the described functionality.
  • the term “circuitry” may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) with the program code used to carry out the functionality of that program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuitry.
  • processor circuitry refers to, is part of, or includes circuitry capable of sequentially and automatically carrying out a sequence of arithmetic or logical operations, or recording, storing, and/or transferring digital data.
  • Processing circuitry may include one or more processing cores to execute instructions and one or more memory structures to store program and data information.
  • processor circuitry may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, and/or any other device capable of executing or otherwise operating computerexecutable instructions, such as program code, software modules, and/or functional processes.
  • Processing circuitry may include more hardware accelerators, which may be microprocessors, programmable processing devices, or the like.
  • the one or more hardware accelerators may include, for example, computer vision (CV) and/or deep learning (DL) accelerators.
  • CV computer vision
  • DL deep learning
  • application circuitry and/or “baseband circuitry” may be considered synonymous to, and may be referred to as, “processor circuitry.”
  • interface circuitry refers to, is part of, or includes circuitry that enables the exchange of information between two or more components or devices.
  • interface circuitry may refer to one or more hardware interfaces, for example, buses, I/O interfaces, peripheral component interfaces, network interface cards, and/or the like.
  • user equipment refers to a device with radio communication capabilities and may describe a remote user of network resources in a communications network.
  • the term “user equipment” or “UE” may be considered synonymous to, and may be referred to as, client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc.
  • the term “user equipment” or “UE” may include any type of wireless/wired device or any computing device including a wireless communications interface.
  • network element refers to physical or virtualized equipment and/or infrastructure used to provide wired or wireless communication network services.
  • network element may be considered synonymous to and/or referred to as a networked computer, networking hardware, network equipment, network node, router, switch, hub, bridge, radio network controller, RAN device, RAN node, gateway, server, virtualized VNF, NFVI, and/or the like.
  • computer system refers to any type interconnected electronic devices, computer devices, or components thereof. Additionally, the term “computer system” and/or “system” may refer to various components of a computer that are communicatively coupled with one another. Furthermore, the term “computer system” and/or “system” may refer to multiple computer devices and/or multiple computing systems that are communicatively coupled with one another and configured to share computing and/or networking resources.
  • appliance refers to a computer device or computer system with program code (e.g., software or firmware) that is specifically designed to provide a specific computing resource.
  • program code e.g., software or firmware
  • a “virtual appliance” is a virtual machine image to be implemented by a hypervisor-equipped device that virtualizes or emulates a computer appliance or otherwise is dedicated to provide a specific computing resource.
  • resource refers to a physical or virtual device, a physical or virtual component within a computing environment, and/or a physical or virtual component within a particular device, such as computer devices, mechanical devices, memory space, processor/CPU time, processor/CPU usage, processor and accelerator loads, hardware time or usage, electrical power, input/output operations, ports or network sockets, channel/link allocation, throughput, memory usage, storage, network, database and applications, workload units, and/or the like.
  • a “hardware resource” may refer to compute, storage, and/or network resources provided by physical hardware element(s).
  • a “virtualized resource” may refer to compute, storage, and/or network resources provided by virtualization infrastructure to an application, device, system, etc.
  • network resource or “communication resource” may refer to resources that are accessible by computer devices/ systems via a communications network.
  • system resources may refer to any kind of shared entities to provide services, and may include computing and/or network resources. System resources may be considered as a set of coherent functions, network data objects or services, accessible through a server where such system resources reside on a single host or multiple hosts and are clearly identifiable.
  • channel refers to any transmission medium, either tangible or intangible, which is used to communicate data or a data stream.
  • channel may be synonymous with and/or equivalent to “communications channel,” “data communications channel,” “transmission channel,” “data transmission channel,” “access channel,” “data access channel,” “link,” “data link,” “carrier,” “radiofrequency carrier,” and/or any other like term denoting a pathway or medium through which data is communicated.
  • link refers to a connection between two devices through a RAT for the purpose of transmitting and receiving information.
  • instantiate refers to the creation of an instance.
  • An “instance” also refers to a concrete occurrence of an object, which may occur, for example, during execution of program code.
  • Coupled may mean two or more elements are in direct physical or electrical contact with one another, may mean that two or more elements indirectly contact each other but still cooperate or interact with each other, and/or may mean that one or more other elements are coupled or connected between the elements that are said to be coupled with each other.
  • directly coupled may mean that two or more elements are in direct contact with one another.
  • communicatively coupled may mean that two or more elements may be in contact with one another by a means of communication including through a wire or other interconnect connection, through a wireless communication channel or link, and/or the like.
  • information element refers to a structural element containing one or more fields.
  • field refers to individual contents of an information element, or a data element that contains content.
  • SMTC refers to an SSB-based measurement timing configuration configured by SSB-MeasurementTimingConfiguration .
  • SSB refers to an SS/PBCH block.
  • a “Primary Cell” refers to the MCG cell, operating on the primary frequency, in which the UE either performs the initial connection establishment procedure or initiates the connection re-establishment procedure.
  • Primary SCG Cell refers to the SCG cell in which the UE performs random access when performing the Reconfiguration with Sync procedure for DC operation.
  • Secondary Cell refers to a cell providing additional radio resources on top of a Special Cell for a UE configured with CA.
  • Secondary Cell Group refers to the subset of serving cells comprising the PSCell and zero or more secondary cells for a UE configured with DC.
  • the term “Serving Cell” refers to the primary cell for a UE in RRC CONNECTED not configured with CA/DC there is only one serving cell comprising of the primary cell.
  • serving cell refers to the set of cells comprising the Special Cell(s) and all secondary cells for a UE in RRC CONNECTED configured with CA/.
  • Special Cell refers to the PCell of the MCG or the PSCell of the SCG for DC operation; otherwise, the term “Special Cell” refers to the Pcell.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)
EP21920077.1A 2021-01-14 2021-12-28 Abschwächung von zeitbereichsüberlappungen mit transportblock über mehrslot-übertragungen Pending EP4278530A1 (de)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US202163137446P 2021-01-14 2021-01-14
US202163185133P 2021-05-06 2021-05-06
PCT/US2021/065320 WO2022154962A1 (en) 2021-01-14 2021-12-28 Mitigation of time-domain overlaps involving transport block over multiple slots transmissions

Publications (1)

Publication Number Publication Date
EP4278530A1 true EP4278530A1 (de) 2023-11-22

Family

ID=82448525

Family Applications (1)

Application Number Title Priority Date Filing Date
EP21920077.1A Pending EP4278530A1 (de) 2021-01-14 2021-12-28 Abschwächung von zeitbereichsüberlappungen mit transportblock über mehrslot-übertragungen

Country Status (2)

Country Link
EP (1) EP4278530A1 (de)
WO (1) WO2022154962A1 (de)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2023546418A (ja) 2020-10-14 2023-11-02 ウィルス インスティテュート オブ スタンダーズ アンド テクノロジー インコーポレイティド 無線通信システムにおいて上りリンク送信方法、装置及びシステム

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10966223B2 (en) * 2018-01-22 2021-03-30 Apple Inc. Handling overlapping of PUCCH and PUSCH for new radio systems
AU2018408003A1 (en) * 2018-02-11 2020-10-01 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Data transmission method, apparatus, computer device and storage medium
US11019682B2 (en) * 2018-06-18 2021-05-25 Apple Inc. Methods to multiplex control information in accordance with multi-slot transmissions in new radio (NR) systems
WO2020196546A1 (en) * 2019-03-25 2020-10-01 Sharp Kabushiki Kaisha COLLISION HANDLING and UCI MULTIPLEXING for URLLC PUCCH and eMBB PUSCH

Also Published As

Publication number Publication date
WO2022154962A1 (en) 2022-07-21

Similar Documents

Publication Publication Date Title
US11871436B2 (en) Apparatus for UE measurement delay and granularity for new radio positioning measurement
US11950267B2 (en) Mechanisms for transmission of multiple downlink control information
US11792814B2 (en) Techniques for cancelation of one or more uplink transmissions from a user equipment
US11871460B2 (en) Domain name system (DNS)-based discovery of regulatory requirements for non-3GPP inter-working function (N3IWF) selection
WO2022155108A1 (en) Enhanced inter-slot frequency hopping for uplink coverage in 5g systems
WO2023091417A1 (en) Enhanced sounding reference signal (srs) operation for fifth-generation (5g) systems
US20230246689A1 (en) Support of simplified multiple input multiple output features for reduced capability user equipment in new radio systems
EP4278530A1 (de) Abschwächung von zeitbereichsüberlappungen mit transportblock über mehrslot-übertragungen
US11979894B2 (en) Soft resource availability indication for integrated access and backhaul (IAB) operation in paired spectrum
WO2022011527A1 (en) Srs configuration and transmission in multi-dci multi-trp and carrier aggregation
WO2022154961A1 (en) Support for edge enabler server and edge configuration server lifecycle management
US11751228B2 (en) Methods and apparatuses for uplink spatial relation info switch
EP4207666A1 (de) Konfiguration von pdcch-überwachungsgelegenheiten für mehrschlitz-pdcch-überwachungsfähigkeit
US20230164670A1 (en) Reduced complexity channel coding for reduced capability new radio user equipment
EP4239479A1 (de) Orchestrierung von rechnerdiensten und ressourcen für systeme der nächsten generation
US20240187172A1 (en) Single trp and multiple trp dynamic switching for single dci based pusch transmissions
WO2023212049A1 (en) Mechanisms for multi-carrier transmit switching for new radio systems in 5g ran1
WO2023033813A1 (en) Group-based channel state information reference signal (csi)-rs) transmission
WO2023154921A1 (en) Reception of new radio (nr) multicast and broadcast service (mbs) control and data in the downlink
WO2023205381A1 (en) Physical downlink control channel (pdcch) monitoring capability for multi-cell scheduling
WO2022155505A1 (en) Techniques for flexible aperiodic sounding reference signal (srs) triggering
EP4320976A1 (de) Verbesserte priorisierung der entwöhnung innerhalb eines benutzers für uplink-übertragungen
WO2023205293A1 (en) Physical downlink control channel (pdcch) transmission with multi-cell scheduling
WO2022155368A1 (en) New radio physical layer hard, soft, not available (h/s/na) in distributed unit (du) frequency-domain
WO2022235690A1 (en) Enhanced service function chaining in next generation cellular networks

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

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: 20230419

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)