GOLITSCHEK EDLER VON ELBWART ALEXANDER JOHANN MARIA (DE)
JUNG HYEJUNG (US)
BHAMRI ANKIT (DE)
NANGIA VIJAY (US)
LÖHR JOACHIM (DE)
MODERATOR (ERICSSON): "Summary#2 - URLLC/IIoT operation on Unlicensed Band", vol. RAN WG1, no. E-meeting; 20210125 - 20210205, 27 January 2021 (2021-01-27), XP051975981, Retrieved from the Internet
TCL: "Enhancements for unlicensed band URLLC/IIoT", vol. RAN WG1, no. e-Meeting; 20210125 - 20210205, 18 January 2021 (2021-01-18), XP051970434, Retrieved from the Internet
CLAIMS 1. A user equipment (“UE”) apparatus, the apparatus comprising: a transceiver that receives a scheduling downlink control information (“DCI”) for scheduling a set of physical uplink shared channel (“PUSCH”) transmissions, the set of PUSCH transmissions comprising at least two PUSCH transmissions; and a processor that: determines a channel occupancy time (“COT”) initiator for each PUSCH transmission of the set of PUSCH transmissions; and determines a set of COTs associated with the set of PUSCH transmissions based on the determined COT initiator for each PUSCH transmission of the set of PUSCH transmissions, wherein the transceiver transmits the set of PUSCH transmissions without transmitting a set of symbols of the set of PUSCH transmissions that overlap with idle periods of the determined set of COTs. 2. The apparatus of claim 1, wherein the processor determines the COT initiator for each PUSCH transmission of the set of PUSCH transmissions based on the scheduling DCI. 3. The apparatus of claim 2, wherein the COT initiator for all PUSCH transmissions of the set of PUSCH transmissions is the same. 4. The apparatus of claim 2, wherein the set of PUSCH transmissions are contiguous PUSCH transmissions without a time gap in between transmissions and are associated with the same COT initiator. 5. The apparatus of claim 2, wherein each PUSCH transmission of the set of PUSCH transmissions has a separate start and length indicator value (“SLIV”) and mapping type. 6. The apparatus of claim 1, wherein the scheduling DCI indicates a row index from a PUSCH time allocation table, the row comprising time domain scheduling information including a starting symbol and a length of each PUSCH transmission of the set of PUSCH transmissions and the COT initiator for each PUSCH transmission of the set of PUSCH transmissions. 7. The apparatus of claim 1, wherein the processor places each PUSCH transmission of the set of PUSCH transmissions in at least one group, a bit in the scheduling DCI indicating the COT initiator for each group of the set of PUSCH transmissions. 8. The apparatus of claim 1, wherein the processor determines the COT initiator for a subset of PUSCH transmissions of the set of PUSCH transmissions based on the scheduling DCI. 9. The apparatus of claim 1, wherein at least one last symbol of a first PUSCH transmission of the set of PUSCH transmissions is an invalid symbol in response to the first PUSCH transmission and a second PUSCH transmission of the set of PUSCH transmissions having different COT initiators. 10. The apparatus of claim 1, wherein the set of PUSCH transmissions comprises a subset of PUSCH transmissions associated with repetitions of a transport block. 11. The apparatus of claim 10, wherein the repetitions of the transport block correspond to repetition type B and wherein actual repetitions associated with a nominal repetition have the same COT initiator. 12. The apparatus of claim 11, wherein the COT initiator for the subset of PUSCH transmissions is a gNB and a PUSCH of the subset of PUSCH transmissions overlaps with an idle period of the COT corresponding to the COT initiator, the processor determining invalid symbols based on the overlap and dropping remaining symbols of the PUSCH after the determined invalid symbols. 13. The apparatus of claim 12, wherein the transceiver does not transmit in the determined invalid symbols. 14. A method at a user equipment (“UE”), the method comprising: receiving a scheduling downlink control information (“DCI”) for scheduling a set of physical uplink shared channel (“PUSCH”) transmissions, the set of PUSCH transmissions comprising at least two PUSCH transmissions; determining a channel occupancy time (“COT”) initiator for each PUSCH transmission of the set of PUSCH transmissions; determining a set of COTs associated with the set of PUSCH transmissions based on the determined COT initiator for each PUSCH transmission of the set of PUSCH transmissions; and transmitting the set of PUSCH transmissions without transmitting a set of symbols of the set of PUSCH transmissions that overlap with idle periods of the determined set of COTs. 15. A network node apparatus, the apparatus comprising: a transceiver that: transmits, to a user equipment (“UE”), a scheduling downlink control information (“DCI”) for scheduling a set of physical uplink shared channel (“PUSCH”) transmissions, the set of PUSCH transmissions comprising at least two PUSCH transmissions; and receives, from the UE, the set of PUSCH transmissions, the set of PUSCH transmissions not comprising a set of symbols that overlap with idle periods of a set of channel occupancy times (“COTs”) associated with the set of PUSCH transmissions. |
Table 3A: Applicable PUSCH time domain resource allocation for DCI format 0_1 in UE specific search space scrambled with C-RNTI, MCS-C-RNTI, CS-RNTI or SP-CSI-RNTI search space scrambled with C-RNTI, MCS-C-RNTI, CS-RNTI or SP-CSI-RNTI
Table 4: Default PUSCH time domain resource allocation A for normal CP Table 5: Default PUSCH time domain resource allocation A for extended CP Table 6: Definition of value j Table 7: Definition of value Δ [0099] Regarding COT initiator determination for G transmissions, in one embodiment, when a configured UL transmission starts after a UE FFP boundary and ends before the idle period of that UE FFP associated to the UE, if the UE has already initiated the UE FFP, then the UE assumes that the configured UL transmission corresponds to UE-initiated COT; otherwise, if the transmission is confined within a gNB FFP before the idle period of that gNB FFP, and if the UE has already determined that gNB has initiated that gNB FFP, then UE assumes that the configured UL transmission corresponds to gNB-initiated COT. [00100] The solutions described herein provide mechanisms to determine the COT initiator for each PUSCH transmission of a multi-PUSCH transmission or for each repetition of PUSCH repetitions, wherein the multiple PUSCH transmissions or repetitions are scheduled by a single DCI. [00101] It should be noted that throughout the disclosure, the terms symbol/slot/subslot/transmission time interval (“TTI”) can be a time unit with a particular duration (e.g., symbol could be a fraction/percentage of an orthogonal frequency division multiplexing (“OFDM”) symbol length associated with a particular subcarrier spacing (“SCS”)). [00102] In the following embodiments and implementations, sharing a COT implies that the device or node with which the COT is shared can forego an indicated or configured channel access category/type for channel sensing and instead apply/perform a channel access according to a category/type whose characteristic includes a generally shorter sensing period, an increased likelihood for the channel sensing to result in being able to transmit, or no required sensing period prior to transmission in the shared COT. [0100] Throughout this disclosure, u-FFP refers to a UE-FFP (an FFP associated/configured for UE-initiated COT), g-FFP refers to a gNB-FFP (an FFP associated/configured for gNB-initiated COT), PUSCH-g refers to a PUSCH transmission that is sent based on a gNB being a COT initiator, and PUSCH-u refers to a PUSCH transmission that is sent based on a UE being a COT initiator. [0101] Some benefits of having a different COT initiator for different PUSCH transmissions/repetitions are represented in Figure(s) 3-5. [0102] Figure 3 depicts a DCI 302 that schedules PUSCH-g 304 and PUSCH-u 306. In one embodiment, gNB has initiated a COT in G-FFP1308 (e.g., to serve other UEs or to schedule the UE). In one embodiment, the UE has not initiated a COT in U-FFP1310. In one embodiment, PUSCH-g 304 is not aligned with a u-FFP boundary and transmitted based on gNB as COT initiator. In one embodiment, PUSCH-u 306 can be sent during g-idle 312 (if COT initiator for PUSCH-u 306 is indicated to be the UE) as the gNB does not have any other data to initiate a g- COT in G-FFP2 314. In one embodiment, g-idle 312 maybe longer than u-idle 316 and/or the overlap of g-idle 312 and PUSCH-u 306 may also be longer than the overlap of PUSCH-g 304 and u-idle 316. In one embodiment, an LBT/gap may be required between PUSCH-g 304 and PUSCH- u 306 of the UE (e.g., PUSCH-g 304 ends (or PUSCH-g 304 symbols overlapping with u-idle 316 are considered as invalid symbols) prior to u-idle 316). [0103] Figure 4 depicts a scenario where, in one embodiment, UE1 402 has already initiated a COT due to a 1 st configured grant (“CG”)-PUSCH 406 transmission (e.g., as CG- PUSCH is aligned with U-FFP1 408 boundary). In one embodiment, gNB knows there is a 2 nd CG-PUSCH 410 coming up and would like to schedule UL transmission right after the 2 nd CG- PUSCH 410. In one embodiment, the 2 nd CG-PUSCH 410 is sent according to UE-COT (e.g., based on the agreed UE behavior for determining the COT initiator in case of CG transmissions, as explained above), and transmitting PUSCH-u 412 according to UE-COT could avoid LBT prior to PUSCH-u 412 transmission; whereas LBT maybe required if PUSCH-u 412 is instead a PUSCH-g 414 as it has to be transmitted assuming g-COT. In one embodiment, gNB wants to schedule a PUSCH 416 for UE2404. To be able to do that, PUSCH-g 414 for UE1402 needs to be sent assuming g-COT. In one embodiment, an LBT/gap may be required between PUSCH-u 412 and PUSCH-g 414 of UE1402. [0104] In an embodiment, if a UE receives an indication from a network entity (e.g. gNB) to perform an UL transmission to the network entity (e.g. PUCCH or PUSCH transmission indicated by DCI), where the UL transmission would occur within a UE-initiated COT (i.e. the COT initiated by the UE) and yet the UL transmission is indicated to be performed according to a network entity-initiated COT, the UE considers that the remaining UE-initiated COT duration is not valid and performs the UL transmission according to the network entity-initiated COT. In an example, if the UL transmission indicated by the network entity overlaps with an idle period of UE’s FFP, the UE performs the UL transmission during the idle period of UE’s FFP, as long as the idle period of UE’s FFP does not overlap with an idle period of network entity’s FFP. In an implementation, the invalid remaining UE-initiated COT duration starts from X symbols after the last symbol of a PDCCH, where the UE detects a DCI format indicating the UL transmission. [0105] In an embodiment, if a UE receives an indication from a network entity to perform a plurality of UL transmissions to the network entity (e.g., multiple PUCCH or PUSCH transmissions or PUCCH/PUSCH repetitions indicated by one DCI), where a subset of UL transmissions would occur within a UE-initiated COT (e.g., the COT that has already been initiated by the UE) and yet the subset of UL transmissions is indicated to be performed according to a network entity-initiated COT, as shown in Figure 4, the UE considers that the remaining UE- initiated COT duration starting from the earliest symbol of the subset of UL transmissions is not valid and performs the subset of UL transmissions according to the network entity-initiated COT. [0106] In an embodiment, if a UE receives an indication from a network entity to perform a plurality of UL transmissions to the network entity (e.g., multiple PUCCH or PUSCH transmissions or PUCCH/PUSCH repetitions indicated by one DCI), where a subset of UL transmissions would occur within UE’s FFP and is indicated to be performed according to a UE- initiated COT, as shown in Figure 3, the UE considers that a remaining network entity-initiated COT duration starting from the earliest symbol of the subset of UL transmissions is not valid, initiates a UE COT according to UE’s FFP configuration, and performs the subset of UL transmissions based on the UE-initiated COT. In an example, the UE performs the subset of UL transmissions during the idle period of network entity’s FFP, as long as the idle period of network entity’s FFP does not overlap with an idle period of UE’s FFP. [0107] Regarding Multi-PUSCH transmission, two examples of multi-PUSCH transmissions are shown in Figure 5. Figure 5 depicts a multi-PUSCH transmission scheduled by the DCI 502. The 1st transmission of a first multi-PUSCH transmission 504a starts from a U-FFP 506 boundary whereas the 1st transmission of a second multi-PUSCH transmission 508a does not start from a U-FFP 506 boundary. In an example, the 1st transmission of a first multi-PUSCH transmission 504a can be transmitted based on a UE-initiated COT and the remaining PUSCHs 540a-c can be sent based on gNB-initiated COT. In another example, all of the PUSCHs 508a-d of the second multi-PUSCH transmission can be based on gNB-initiated COT. [0108] In an embodiment, multi-PUSCH time-domain allocation table (a TDRA table) is extended to have a field/column indicating whether the UE or gNB is the COT initiator for each PUSCH of the multi-PUSCH. In an implementation, pusch- TimeDomainAllocationListForMultiPUSCH is extended with an individual COT initiator indicator for each PUSCH. In an alternative embodiment, all the PUSCHs of the multi-PUSCH transmission (scheduled via a single scheduling DCI) have the same COT initiator indicated in the scheduling DCI. In another embodiment, the contiguous PUSCHs without gap between PUSCHs of the multi-PUSCH transmission have the same COT initiator. In another embodiment, a first number of consecutive PUSCHs or contiguous PUSCHs without a gap between PUSCHs have the same COT initiator (1st COT initiator) and the rest of the consecutive PUSCHs or contiguous PUSCHs without a gap between PUSCHs have the same COT initiator (2nd COT initiator). In an example, the first number is indicated as a field/column of the multi-PUSCH time-domain allocation table. In another example, the 1st COT initiator is the UE. In another example, a row of the table includes the first number. In one embodiment, the UE determines the COT initiator to be the UE for the first number of consecutive PUSCH transmissions and the gNB for the remaining number of consecutive PUSCH transmissions. In another example, the first number of consecutive PUSCHs occupies the same FFP (e.g., gNB FFP or UE FFP). In an example, the first number of PUSCHs starts from the first PUSCH after reception of the scheduling DCI. [0109] In one embodiment, a field in the scheduling DCI indicates the COT initiator, wherein the indication is only applicable to a 1st number of scheduled PUSCH transmissions out of the total number of PUSCH transmissions scheduled by the DCI. In an example, the indication is only applicable to the first PUSCH transmission. In another example, the COT initiator for each of the rest of transmissions is determined based on rules defined for determining the COT initiator for a configured grant UL transmission. In another example, the first number of consecutive PUSCHs occupies the same FFP (e.g., gNB FFP or UE FFP). In another example, the indicated COT initiator applies until the COT initiator's FFP boundary. In one example, a 2nd DCI indicates the COT initiator for PUSCHs (of the multi-PSUCH) beyond the COT initiator's FFP boundary. In an example, the COT initiator indicated in the second DCI (referred to as 2nd COT initiator) applies until the 2nd COT initiator’s FFP boundary. In an example, the COT initiator for the rest of transmissions is determined based on rules defined for determining the COT initiator for a configured grant UL transmission. [0110] In one embodiment, the COT initiator indication in the scheduling DCI is only applicable to PUSCH transmissions within a predetermined window. In an example, the predetermined window is a time window starting from a reference time point such as the last symbol of the scheduling DCI PDCCH or an offset time with respect to the last symbol of the scheduling DCI PDCCH. In one embodiment, the offset can be determined based on UE capability signaling (such as PUSCH processing capability), or based on RRC signaling, or based on a fixed value in the specifications. In one embodiment, the time window can start from and/or end at the boundary of an upcoming u-FFP or g-FFP. In one embodiment, the duration of the predetermined window can be RRC signaled, signaled in the scheduling DCI (e.g., in number of time units such as symbols, slots, u-FFP, g-FFP, etc.), or the remaining duration of UE-FFP or gNB-FFP. [0111] In one embodiment, a 1st number of consecutive/contiguous PUSCH transmissions of the multi-PUSCH has a 1st COT initiator and the remaining number of consecutive/contiguous PUSCH transmissions of the multi-PUSCH have a 2nd COT initiator. In one embodiment, the UE is not expected to receive a scheduling DCI indicating a 1st number of consecutive/contiguous PUSCH transmissions of the multi-PUSCH has a 1st COT initiator and a next 2nd number of consecutive/contiguous PUSCH transmissions of the multi-PUSCH has a 2nd COT initiator, and a next 3rd number of consecutive/contiguous PUSCH transmissions of the multi-PUSCH has the 1st COT initiator. In one embodiment, this may mandate an additional LBT. In an example, the UE is not expected to perform more than ‘X’ LBTs within transmission duration of a multi-PUSCH transmission. ‘X’ can be specified in 3GPP specifications or can be a UE capability. [0112] In one embodiment, the UE maintains a gap and/or performs LBT between each pair of PUSCH transmissions of the multi-PUSCH if the COT initiator is different for the pair of PUSCH transmissions, e.g., at least for the case that the 1st PUSCH of the pair is transmitted according to g-COT and the latter PUSCH of the pair is transmitted according to the u-COT. In an example, the latter PUSCH is aligned with a u-FFP boundary. In another example, (a) the symbols overlapping with u-idle are considered invalid symbols for the PUSCH-g if the next PUSCH of the multi-PUSCH is a PUSCH-u and/or (b) the symbols overlapping with g-idle are considered invalid symbols for the PUSCH-u if the next PUSCH of the multi-PUSCH is a PUSCH-g. If a symbol is considered invalid, no transmission is performed. This may result in a transmission of PUSCH-u/PUSCH-g only on those symbols that are not considered invalid, i.e. a partial PUSCH- u/PUSCH-g transmission. In an example, the remaining symbols of a PUSCH which has invalid symbols due to overlapping with u-idle or g-idle are (a) dropped or (b) considered as new actual repetition in case PUSCH repetition type B is configured/supported. [0113] In one embodiment, the DCI field indicating the COT initiator for the PUSCH transmissions has a predetermined field size. The field size may be determined based on one or more of the maximum number of contiguous/consecutive PUSCHs (e.g., 8) or having the field size fixed/configured, e.g., X bits, and having scheduled PUSCHs grouped in X groups. For instance, if X= 4 bits, and 8 contiguous PUSCHs scheduled, every two consecutive PUSCHs have the same COT initiator – the COT initiator for the 1st two PUSCHs is determined based on the 1st bit of the 4-bit field and the COT initiator for the 2nd two PUSCHs is determined based on the 2nd bit of the 4-bit field, and so on. [0114] In one embodiment, a first PUSCH transmission and a second PUSCH transmission of the multi-PUSCH transmissions can have different COT initiators if the first PUSCH transmission overlaps with the u-FFP idle and the second PUSCH transmission overlaps with the g-FFP idle (see Figure 3). [0115] In one embodiment, a 2nd DCI can be sent to update the COT initiator for a remaining of the multiple PUSCHs. The 2nd DCI may have a characteristic such as a field indicating whether this DCI is updating the COT initiator assumption for the already scheduled PUSCHs. In one embodiment, the 2nd DCI can update COT initiator assumption for a subset of the PUSCH transmissions of the multi-PUSCH transmission that are at least certain time (e.g., N2 symbols) after the 2nd DCI. In one embodiment, the 2nd DCI may be a group-common PDCCH. The UE may be configured with a position in DCI field and possibly a number of bits for determining the updated COT initiator field in the 2nd DCI. [0116] Regarding PUSCH repetition, the methods and embodiments for COT initiator determination of multi-PUSCH can be used to determine the COT initiator of repetitions of PUSCH repetition (e.g., type B), e.g., instead of a first PUSCH and a second PUSCH of the multi- PUSCH, a first repetition and a second repetition of the PUSCH repetition can be used. [0117] In one embodiment, a field in the scheduling DCI indicates the COT initiator for each (or a first number of) nominal repetition(s). Alternatively, a field in the scheduling DCI indicates the COT initiator for each (or a first number of) actual repetition(s). [0118] In an embodiment, actual PUSCH repetitions associated to a nominal PUSCH repetition have the same COT initiator. The UE can determine the same COT initiator for actual PUSCH repetitions associated to a nominal PUSCH repetition. [0119] In some embodiments, when a DCI can schedule both multiple PUSCHs and corresponding repetitions, then COT initiator can be determined as (1) at least two set of COT initiator indications are signaled (via TDRA or a DCI field), wherein the first set of COT initiator indication is applied to multiple PUSCH transmissions and the second set of COT initiator indication is applied to corresponding PUSCH repetitions; (2) for a first PUSCH transmission and its repetitions, one COT initiator indication is applied, for a second PUSCH transmission and its repetitions, second COT initiator indication is applied, and so on; and/or (3) for a first PUSCH transmission, one COT initiator indication is applied and for its first repetition a second COT initiator indication is applied, for a second repetition of the first PUSCH transmission a third COT initiator indication is applied, and so on. Similarly, for following PUSCH transmissions and corresponding repetitions. [0120] Figure 6 depicts a NR protocol stack 600, according to embodiments of the disclosure. While Figure 6 shows the remote unit 105, the base unit 121 and the mobile core network 130, these are representative of a set of UEs interacting with a RAN node and a NF (e.g., AMF) in a core network. As depicted, the protocol stack 600 comprises a User Plane protocol stack 601 and a Control Plane protocol stack 603. The User Plane protocol stack 601 includes a physical (“PHY”) layer 605, a Medium Access Control (“MAC”) sublayer 610, a Radio Link Control (“RLC”) sublayer 615, a Packet Data Convergence Protocol (“PDCP”) sublayer 620, and Service Data Adaptation Protocol (“SDAP”) layer 625. The Control Plane protocol stack 603 also includes a physical layer 605, a MAC sublayer 610, a RLC sublayer 615, and a PDCP sublayer 620. The Control Place protocol stack 603 also includes a Radio Resource Control (“RRC”) layer 630 and a Non-Access Stratum (“NAS”) layer 635. [0121] The AS protocol stack for the Control Plane protocol stack 603 consists of at least RRC, PDCP, RLC and MAC sublayers, and the physical layer. The AS protocol stack for the User Plane protocol stack 601 consists of at least SDAP, PDCP, RLC and MAC sublayers, and the physical layer. The Layer-2 (“L2”) is split into the SDAP, PDCP, RLC and MAC sublayers. The Layer-3 (“L3”) includes the RRC sublayer 630 and the NAS layer 635 for the control plane and includes, e.g., an Internet Protocol (“IP”) layer or PDU Layer (note depicted) for the user plane. L1 and L2 are referred to as “lower layers” such as PUCCH/PUSCH or MAC CE, while L3 and above (e.g., transport layer, application layer) are referred to as “higher layers” or “upper layers” such as RRC. [0122] The physical layer 605 offers transport channels to the MAC sublayer 610. The MAC sublayer 610 offers logical channels to the RLC sublayer 615. The RLC sublayer 615 offers RLC channels to the PDCP sublayer 620. The PDCP sublayer 620 offers radio bearers to the SDAP sublayer 625 and/or RRC layer 630. The SDAP sublayer 625 offers QoS flows to the mobile core network 130 (e.g., 5GC). The RRC layer 630 provides for the addition, modification, and release of Carrier Aggregation and/or Dual Connectivity. The RRC layer 630 also manages the establishment, configuration, maintenance, and release of Signaling Radio Bearers (“SRBs”) and Data Radio Bearers (“DRBs”). In certain embodiments, a RRC entity functions for detection of and recovery from radio link failure. [0123] Figure 7 depicts a user equipment apparatus 700 that may be used for channel occupancy initiator determination for transmissions in unlicensed spectrum, according to embodiments of the disclosure. In various embodiments, the user equipment apparatus 700 is used to implement one or more of the solutions described above. The user equipment apparatus 700 may be one embodiment of a UE, such as the remote unit 105 and/or the UE 205, as described above. Furthermore, the user equipment apparatus 700 may include a processor 705, a memory 710, an input device 715, an output device 720, and a transceiver 725. In some embodiments, the input device 715 and the output device 720 are combined into a single device, such as a touchscreen. In certain embodiments, the user equipment apparatus 700 may not include any input device 715 and/or output device 720. In various embodiments, the user equipment apparatus 700 may include one or more of: the processor 705, the memory 710, and the transceiver 725, and may not include the input device 715 and/or the output device 720. [0124] As depicted, the transceiver 725 includes at least one transmitter 730 and at least one receiver 735. Here, the transceiver 725 communicates with one or more base units 121. Additionally, the transceiver 725 may support at least one network interface 740 and/or application interface 745. The application interface(s) 745 may support one or more APIs. The network interface(s) 740 may support 3GPP reference points, such as Uu and PC5. Other network interfaces 740 may be supported, as understood by one of ordinary skill in the art. [0125] The processor 705, in one embodiment, may include any known controller capable of executing computer-readable instructions and/or capable of performing logical operations. For example, the processor 705 may be a microcontroller, a microprocessor, a central processing unit (“CPU”), a graphics processing unit (“GPU”), an auxiliary processing unit, a field programmable gate array (“FPGA”), a digital signal processor (“DSP”), a co-processor, an application-specific processor, or similar programmable controller. In some embodiments, the processor 705 executes instructions stored in the memory 710 to perform the methods and routines described herein. The processor 705 is communicatively coupled to the memory 710, the input device 715, the output device 720, and the transceiver 725. In certain embodiments, the processor 705 may include an application processor (also known as “main processor”) which manages application-domain and operating system (“OS”) functions and a baseband processor (also known as “baseband radio processor”) which manages radio functions. [0126] The memory 710, in one embodiment, is a computer readable storage medium. In some embodiments, the memory 710 includes volatile computer storage media. For example, the memory 710 may include a RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/or static RAM (“SRAM”). In some embodiments, the memory 710 includes non-volatile computer storage media. For example, the memory 710 may include a hard disk drive, a flash memory, or any other suitable non-volatile computer storage device. In some embodiments, the memory 710 includes both volatile and non-volatile computer storage media. [0127] In some embodiments, the memory 710 stores data related to CSI enhancements for higher frequencies. For example, the memory 710 may store parameters, configurations, resource assignments, policies, and the like as described above. In certain embodiments, the memory 710 also stores program code and related data, such as an operating system or other controller algorithms operating on the user equipment apparatus 700, and one or more software applications. [0128] The input device 715, in one embodiment, may include any known computer input device including a touch panel, a button, a keyboard, a stylus, a microphone, or the like. In some embodiments, the input device 715 may be integrated with the output device 720, for example, as a touchscreen or similar touch-sensitive display. In some embodiments, the input device 715 includes a touchscreen such that text may be input using a virtual keyboard displayed on the touchscreen and/or by handwriting on the touchscreen. In some embodiments, the input device 715 includes two or more different devices, such as a keyboard and a touch panel. [0129] The output device 720, in one embodiment, is designed to output visual, audible, and/or haptic signals. In some embodiments, the output device 720 includes an electronically controllable display or display device capable of outputting visual data to a user. For example, the output device 720 may include, but is not limited to, an LCD display, an LED display, an OLED display, a projector, or similar display device capable of outputting images, text, or the like to a user. As another, non-limiting, example, the output device 720 may include a wearable display separate from, but communicatively coupled to, the rest of the user equipment apparatus 700, such as a smart watch, smart glasses, a heads-up display, or the like. Further, the output device 720 may be a component of a smart phone, a personal digital assistant, a television, a table computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, or the like. [0130] In certain embodiments, the output device 720 includes one or more speakers for producing sound. For example, the output device 720 may produce an audible alert or notification (e.g., a beep or chime). In some embodiments, the output device 720 includes one or more haptic devices for producing vibrations, motion, or other haptic feedback. In some embodiments, all or portions of the output device 720 may be integrated with the input device 715. For example, the input device 715 and output device 720 may form a touchscreen or similar touch-sensitive display. In other embodiments, the output device 720 may be located near the input device 715. [0131] The transceiver 725 includes at least transmitter 730 and at least one receiver 735. The transceiver 725 may be used to provide UL communication signals to a base unit 121 and to receive DL communication signals from the base unit 121, as described herein. Similarly, the transceiver 725 may be used to transmit and receive SL signals (e.g., V2X communication), as described herein. Although only one transmitter 730 and one receiver 735 are illustrated, the user equipment apparatus 700 may have any suitable number of transmitters 730 and receivers 735. Further, the transmitter(s) 730 and the receiver(s) 735 may be any suitable type of transmitters and receivers. In one embodiment, the transceiver 725 includes a first transmitter/receiver pair used to communicate with a mobile communication network over licensed radio spectrum and a second transmitter/receiver pair used to communicate with a mobile communication network over unlicensed radio spectrum. [0132] In certain embodiments, the first transmitter/receiver pair used to communicate with a mobile communication network over licensed radio spectrum and the second transmitter/receiver pair used to communicate with a mobile communication network over unlicensed radio spectrum may be combined into a single transceiver unit, for example a single chip performing functions for use with both licensed and unlicensed radio spectrum. In some embodiments, the first transmitter/receiver pair and the second transmitter/receiver pair may share one or more hardware components. For example, certain transceivers 725, transmitters 730, and receivers 735 may be implemented as physically separate components that access a shared hardware resource and/or software resource, such as for example, the network interface 740. [0133] In various embodiments, one or more transmitters 730 and/or one or more receivers 735 may be implemented and/or integrated into a single hardware component, such as a multi- transceiver chip, a system-on-a-chip, an ASIC, or other type of hardware component. In certain embodiments, one or more transmitters 730 and/or one or more receivers 735 may be implemented and/or integrated into a multi-chip module. In some embodiments, other components such as the network interface 740 or other hardware components/circuits may be integrated with any number of transmitters 730 and/or receivers 735 into a single chip. In such embodiment, the transmitters 730 and receivers 735 may be logically configured as a transceiver 725 that uses one more common control signals or as modular transmitters 730 and receivers 735 implemented in the same hardware chip or in a multi-chip module. [0134] In one embodiment, the transceiver 725 receives a scheduling downlink control information (“DCI”) for scheduling a set of physical uplink shared channel (“PUSCH”) transmissions, the set of PUSCH transmissions comprising at least two PUSCH transmissions. In one embodiment, the processor 705 determines a channel occupancy time (“COT”) initiator for each PUSCH transmission of the set of PUSCH transmissions and determines a set of COTs associated with the set of PUSCH transmissions based on the determined COT initiator for each PUSCH transmission of the set of PUSCH transmissions. In one embodiment, the transceiver 725 transmits the set of PUSCH transmissions without transmitting a set of symbols of the set of PUSCH transmissions that overlap with idle periods of the determined set of COTs. [0135] In one embodiment, the processor 705 determines the COT initiator for each PUSCH transmission of the set of PUSCH transmissions based on the scheduling DCI. [0136] In one embodiment, the COT initiator for all PUSCH transmissions of the set of PUSCH transmissions is the same. [0137] In one embodiment, at least two PUSCH transmissions of the set of PUSCH transmissions have a different COT initiator. [0138] In one embodiment, the set of PUSCH transmissions are contiguous PUSCH transmissions without a time gap in between transmissions and are associated with the same COT initiator. [0139] In one embodiment, each PUSCH transmission of the set of PUSCH transmissions has a separate start and length indicator value (“SLIV”) and mapping type. [0140] In one embodiment, the scheduling DCI indicates a row index from a PUSCH time allocation table, the row comprising time domain scheduling information including a starting symbol and a length of each PUSCH transmission of the set of PUSCH transmissions and the COT initiator for each PUSCH transmission of the set of PUSCH transmissions. [0141] In one embodiment, the processor 705 places each PUSCH transmission of the set of PUSCH transmissions in at least one group, a bit in the scheduling DCI indicating the COT initiator for each group of the set of PUSCH transmissions. [0142] In one embodiment, the processor 705 determines the COT initiator for a subset of PUSCH transmissions of the set of PUSCH transmissions based on the scheduling DCI. [0143] In one embodiment, at least one last symbol of a first PUSCH transmission of the set of PUSCH transmissions is an invalid symbol in response to the first PUSCH transmission and a second PUSCH transmission of the set of PUSCH transmissions having different COT initiators. [0144] In one embodiment, the transceiver 725 receives a second DCI after the scheduling DCI and the processor determines the set of COTs associated with at least a portion of the set of PUSCH transmissions based on the scheduling DCI and the second DCI. [0145] In one embodiment, the set of PUSCH transmissions comprises a subset of PUSCH transmissions associated with repetitions of a transport block. [0146] In one embodiment, the repetitions of the transport block correspond to repetition type B and wherein actual repetitions associated with a nominal repetition have the same COT initiator. [0147] In one embodiment, the COT initiator for the subset of PUSCH transmissions is a gNB and a PUSCH of the subset of PUSCH transmissions overlaps with an idle period of the COT corresponding to the COT initiator, the processor determining invalid symbols based on the overlap and dropping remaining symbols of the PUSCH after the determined invalid symbols. [0148] In one embodiment, the transceiver 725 does not transmit in the determined invalid symbols. [0149] Figure 8 depicts one embodiment of a network apparatus 800 that may be used for channel occupancy initiator determination for transmissions in unlicensed spectrum, according to embodiments of the disclosure. In some embodiments, the network apparatus 800 may be one embodiment of a RAN node and its supporting hardware, such as the base unit 121 and/or gNB, described above. Furthermore, network apparatus 800 may include a processor 805, a memory 810, an input device 815, an output device 820, and a transceiver 825. In certain embodiments, the network apparatus 800 does not include any input device 815 and/or output device 820. [0150] As depicted, the transceiver 825 includes at least one transmitter 830 and at least one receiver 835. Here, the transceiver 825 communicates with one or more remote units 105. Additionally, the transceiver 825 may support at least one network interface 840 and/or application interface 845. The application interface(s) 845 may support one or more APIs. The network interface(s) 840 may support 3GPP reference points, such as Uu, N1, N2, N3, N5, N6 and/or N7 interfaces. Other network interfaces 840 may be supported, as understood by one of ordinary skill in the art. [0151] When implementing a NEF, the network interface(s) 840 may include an interface for communicating with an application function (i.e., N5) and with at least one network function (e.g., UDR, SFC function, UPF) in a mobile communication network, such as the mobile core network 130. [0152] The processor 805, in one embodiment, may include any known controller capable of executing computer-readable instructions and/or capable of performing logical operations. For example, the processor 805 may be a microcontroller, a microprocessor, a central processing unit (“CPU”), a graphics processing unit (“GPU”), an auxiliary processing unit, a field programmable gate array (“FPGA”), a digital signal processor (“DSP”), a co-processor, an application-specific processor, or similar programmable controller. In some embodiments, the processor 805 executes instructions stored in the memory 810 to perform the methods and routines described herein. The processor 805 is communicatively coupled to the memory 810, the input device 815, the output device 820, and the transceiver 825. In certain embodiments, the processor 805 may include an application processor (also known as “main processor”) which manages application-domain and operating system (“OS”) functions and a baseband processor (also known as “baseband radio processor”) which manages radio function. In various embodiments, the processor 805 controls the network apparatus 800 to implement the above described network entity behaviors (e.g., of the gNB) for channel occupancy initiator determination for transmissions in unlicensed spectrum. [0153] The memory 810, in one embodiment, is a computer readable storage medium. In some embodiments, the memory 810 includes volatile computer storage media. For example, the memory 810 may include a RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/or static RAM (“SRAM”). In some embodiments, the memory 810 includes non-volatile computer storage media. For example, the memory 810 may include a hard disk drive, a flash memory, or any other suitable non-volatile computer storage device. In some embodiments, the memory 810 includes both volatile and non-volatile computer storage media. [0154] In some embodiments, the memory 810 stores data relating to CSI enhancements for higher frequencies. For example, the memory 810 may store parameters, configurations, resource assignments, policies, and the like as described above. In certain embodiments, the memory 810 also stores program code and related data, such as an operating system (“OS”) or other controller algorithms operating on the network apparatus 800, and one or more software applications. [0155] The input device 815, in one embodiment, may include any known computer input device including a touch panel, a button, a keyboard, a stylus, a microphone, or the like. In some embodiments, the input device 815 may be integrated with the output device 820, for example, as a touchscreen or similar touch-sensitive display. In some embodiments, the input device 815 includes a touchscreen such that text may be input using a virtual keyboard displayed on the touchscreen and/or by handwriting on the touchscreen. In some embodiments, the input device 815 includes two or more different devices, such as a keyboard and a touch panel. [0156] The output device 820, in one embodiment, may include any known electronically controllable display or display device. The output device 820 may be designed to output visual, audible, and/or haptic signals. In some embodiments, the output device 820 includes an electronic display capable of outputting visual data to a user. Further, the output device 820 may be a component of a smart phone, a personal digital assistant, a television, a table computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, or the like. [0157] In certain embodiments, the output device 820 includes one or more speakers for producing sound. For example, the output device 820 may produce an audible alert or notification (e.g., a beep or chime). In some embodiments, the output device 820 includes one or more haptic devices for producing vibrations, motion, or other haptic feedback. In some embodiments, all or portions of the output device 820 may be integrated with the input device 815. For example, the input device 815 and output device 820 may form a touchscreen or similar touch-sensitive display. In other embodiments, all or portions of the output device 820 may be located near the input device 815. [0158] As discussed above, the transceiver 825 may communicate with one or more remote units and/or with one or more interworking functions that provide access to one or more PLMNs. The transceiver 825 may also communicate with one or more network functions (e.g., in the mobile core network 80). The transceiver 825 operates under the control of the processor 805 to transmit messages, data, and other signals and also to receive messages, data, and other signals. For example, the processor 805 may selectively activate the transceiver (or portions thereof) at particular times in order to send and receive messages. [0159] The transceiver 825 may include one or more transmitters 830 and one or more receivers 835. In certain embodiments, the one or more transmitters 830 and/or the one or more receivers 835 may share transceiver hardware and/or circuitry. For example, the one or more transmitters 830 and/or the one or more receivers 835 may share antenna(s), antenna tuner(s), amplifier(s), filter(s), oscillator(s), mixer(s), modulator/demodulator(s), power supply, and the like. In one embodiment, the transceiver 825 implements multiple logical transceivers using different communication protocols or protocol stacks, while using common physical hardware. [0160] In one embodiment, the transceiver 825 transmits, to a user equipment (“UE”), a scheduling downlink control information (“DCI”) for scheduling a set of physical uplink shared channel (“PUSCH”) transmissions, the set of PUSCH transmissions comprising at least two PUSCH transmissions and receives, from the UE, the set of PUSCH transmissions, the set of PUSCH transmissions not comprising a set of symbols that overlap with idle periods of a set of channel occupancy times (“COTs”) associated with the set of PUSCH transmissions. [0161] Figure 9 is a flowchart diagram of a method 900 for channel occupancy initiator determination for transmissions in unlicensed spectrum. The method 900 may be performed by a UE as described herein, for example, the remote unit 105 and/or the user equipment apparatus 700. In some embodiments, the method 900 may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like. [0162] In one embodiment, the method 900 begins and receives 905 a scheduling downlink control information (“DCI”) for scheduling a set of physical uplink shared channel (“PUSCH”) transmissions, the set of PUSCH transmissions comprising at least two PUSCH transmissions. In one embodiment, the method 900 determines 910 a channel occupancy time (“COT”) initiator for each PUSCH transmission of the set of PUSCH transmissions. In one embodiment, the method 900 determines 915 a set of COTs associated with the set of PUSCH transmissions based on the determined COT initiator for each PUSCH transmission of the set of PUSCH transmissions. In one embodiment, the method 900 transmits 920 the set of PUSCH transmissions without transmitting a set of symbols of the set of PUSCH transmissions that overlap with idle periods of the determined set of COTs, and the method 900 ends. [0163] Figure 10 is a flowchart diagram of a method 1000 for channel occupancy initiator determination for transmissions in unlicensed spectrum. The method 1000 may be performed by a network device as described herein, for example, the base unit 121, a gNB, and/or the network equipment apparatus 800. In some embodiments, the method 1000 may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like. [0164] In one embodiment, the method 1000 transmits 1005, to a user equipment (“UE”), a scheduling downlink control information (“DCI”) for scheduling a set of physical uplink shared channel (“PUSCH”) transmissions, the set of PUSCH transmissions comprising at least two PUSCH transmissions. In one embodiment, the method 1000 receives 1010, from the UE, the set of PUSCH transmissions, the set of PUSCH transmissions not comprising a set of symbols that overlap with idle periods of a set of channel occupancy times (“COTs”) associated with the set of PUSCH transmissions, and the method 1000 ends. [0165] A first apparatus is disclosed for channel occupancy initiator determination for transmissions in unlicensed spectrum. The first apparatus may include a UE as described herein, for example, the remote unit 105 and/or the user equipment apparatus 700. In some embodiments, the first apparatus may include a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like. [0166] In one embodiment, the first apparatus includes a transceiver that receives a scheduling downlink control information (“DCI”) for scheduling a set of physical uplink shared channel (“PUSCH”) transmissions, the set of PUSCH transmissions comprising at least two PUSCH transmissions. In one embodiment, the first apparatus includes a processor that determines a channel occupancy time (“COT”) initiator for each PUSCH transmission of the set of PUSCH transmissions and determines a set of COTs associated with the set of PUSCH transmissions based on the determined COT initiator for each PUSCH transmission of the set of PUSCH transmissions. In one embodiment, the transceiver transmits the set of PUSCH transmissions without transmitting a set of symbols of the set of PUSCH transmissions that overlap with idle periods of the determined set of COTs. [0167] In one embodiment, the processor determines the COT initiator for each PUSCH transmission of the set of PUSCH transmissions based on the scheduling DCI. [0168] In one embodiment, the COT initiator for all PUSCH transmissions of the set of PUSCH transmissions is the same. [0169] In one embodiment, at least two PUSCH transmissions of the set of PUSCH transmissions have a different COT initiator. [0170] In one embodiment, the set of PUSCH transmissions are contiguous PUSCH transmissions without a time gap in between transmissions and are associated with the same COT initiator. [0171] In one embodiment, each PUSCH transmission of the set of PUSCH transmissions has a separate start and length indicator value (“SLIV”) and mapping type. [0172] In one embodiment, the scheduling DCI indicates a row index from a PUSCH time allocation table, the row comprising time domain scheduling information including a starting symbol and a length of each PUSCH transmission of the set of PUSCH transmissions and the COT initiator for each PUSCH transmission of the set of PUSCH transmissions. [0173] In one embodiment, the processor places each PUSCH transmission of the set of PUSCH transmissions in at least one group, a bit in the scheduling DCI indicating the COT initiator for each group of the set of PUSCH transmissions. [0174] In one embodiment, the processor determines the COT initiator for a subset of PUSCH transmissions of the set of PUSCH transmissions based on the scheduling DCI. [0175] In one embodiment, at least one last symbol of a first PUSCH transmission of the set of PUSCH transmissions is an invalid symbol in response to the first PUSCH transmission and a second PUSCH transmission of the set of PUSCH transmissions having different COT initiators. [0176] In one embodiment, the transceiver receives a second DCI after the scheduling DCI and the processor determines the set of COTs associated with at least a portion of the set of PUSCH transmissions based on the scheduling DCI and the second DCI. [0177] In one embodiment, the set of PUSCH transmissions comprises a subset of PUSCH transmissions associated with repetitions of a transport block. [0178] In one embodiment, the repetitions of the transport block correspond to repetition type B and wherein actual repetitions associated with a nominal repetition have the same COT initiator. [0179] In one embodiment, the COT initiator for the subset of PUSCH transmissions is a gNB and a PUSCH of the subset of PUSCH transmissions overlaps with an idle period of the COT corresponding to the COT initiator, the processor determining invalid symbols based on the overlap and dropping remaining symbols of the PUSCH after the determined invalid symbols. [0180] In one embodiment, the transceiver does not transmit in the determined invalid symbols. [0181] A first method is disclosed for channel occupancy initiator determination for transmissions in unlicensed spectrum. The first method may be performed by a UE as described herein, for example, the remote unit 105 and/or the user equipment apparatus 700. In some embodiments, the first method may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like. [0182] In one embodiment, the first method receives a scheduling downlink control information (“DCI”) for scheduling a set of physical uplink shared channel (“PUSCH”) transmissions, the set of PUSCH transmissions comprising at least two PUSCH transmissions. In one embodiment, the first method determines a channel occupancy time (“COT”) initiator for each PUSCH transmission of the set of PUSCH transmissions and determines a set of COTs associated with the set of PUSCH transmissions based on the determined COT initiator for each PUSCH transmission of the set of PUSCH transmissions. In one embodiment, the first method transmits the set of PUSCH transmissions without transmitting a set of symbols of the set of PUSCH transmissions that overlap with idle periods of the determined set of COTs. [0183] In one embodiment, the first method determines the COT initiator for each PUSCH transmission of the set of PUSCH transmissions based on the scheduling DCI. [0184] In one embodiment, the COT initiator for all PUSCH transmissions of the set of PUSCH transmissions is the same. [0185] In one embodiment, at least two PUSCH transmissions of the set of PUSCH transmissions have a different COT initiator. [0186] In one embodiment, the set of PUSCH transmissions are contiguous PUSCH transmissions without a time gap in between transmissions and are associated with the same COT initiator. [0187] In one embodiment, each PUSCH transmission of the set of PUSCH transmissions has a separate start and length indicator value (“SLIV”) and mapping type. [0188] In one embodiment, the scheduling DCI indicates a row index from a PUSCH time allocation table, the row comprising time domain scheduling information including a starting symbol and a length of each PUSCH transmission of the set of PUSCH transmissions and the COT initiator for each PUSCH transmission of the set of PUSCH transmissions. [0189] In one embodiment, the first method places each PUSCH transmission of the set of PUSCH transmissions in at least one group, a bit in the scheduling DCI indicating the COT initiator for each group of the set of PUSCH transmissions. [0190] In one embodiment, the first method determines the COT initiator for a subset of PUSCH transmissions of the set of PUSCH transmissions based on the scheduling DCI. [0191] In one embodiment, at least one last symbol of a first PUSCH transmission of the set of PUSCH transmissions is an invalid symbol in response to the first PUSCH transmission and a second PUSCH transmission of the set of PUSCH transmissions having different COT initiators. [0192] In one embodiment, the first method receives a second DCI after the scheduling DCI and determines the set of COTs associated with at least a portion of the set of PUSCH transmissions based on the scheduling DCI and the second DCI. [0193] In one embodiment, the set of PUSCH transmissions comprises a subset of PUSCH transmissions associated with repetitions of a transport block. [0194] In one embodiment, the repetitions of the transport block correspond to repetition type B and wherein actual repetitions associated with a nominal repetition have the same COT initiator. [0195] In one embodiment, the COT initiator for the subset of PUSCH transmissions is a gNB and a PUSCH of the subset of PUSCH transmissions overlaps with an idle period of the COT corresponding to the COT initiator, the processor determining invalid symbols based on the overlap and dropping remaining symbols of the PUSCH after the determined invalid symbols. [0196] In one embodiment, the first method does not transmit in the determined invalid symbols. [0197] A second apparatus is disclosed for channel occupancy initiator determination for transmissions in unlicensed spectrum. The second apparatus may include a network device as described herein, for example, the base unit 121, a gNB, and/or the network equipment apparatus 800. In some embodiments, the second apparatus may include a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like. [0198] In one embodiment, the second apparatus includes a transceiver that transmits, to a user equipment (“UE”), a scheduling downlink control information (“DCI”) for scheduling a set of physical uplink shared channel (“PUSCH”) transmissions, the set of PUSCH transmissions comprising at least two PUSCH transmissions and receives, from the UE, the set of PUSCH transmissions, the set of PUSCH transmissions not comprising a set of symbols that overlap with idle periods of a set of channel occupancy times (“COTs”) associated with the set of PUSCH transmissions. [0199] A second method is disclosed for channel occupancy initiator determination for transmissions in unlicensed spectrum. The second method may be performed by a network device as described herein, for example, the base unit 121, a gNB, and/or the network equipment apparatus 800. In some embodiments, the second method may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like. [0200] In one embodiment, the second method transmits, to a user equipment (“UE”), a scheduling downlink control information (“DCI”) for scheduling a set of physical uplink shared channel (“PUSCH”) transmissions, the set of PUSCH transmissions comprising at least two PUSCH transmissions and receives, from the UE, the set of PUSCH transmissions, the set of PUSCH transmissions not comprising a set of symbols that overlap with idle periods of a set of channel occupancy times (“COTs”) associated with the set of PUSCH transmissions. [0201] Embodiments may be practiced in other specific forms. The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the invention is, therefore, indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.