WO2022132438A1 - Downlink scheduling information transmission for high carrier frequencies - Google Patents

Abstract

Various embodiments herein provide techniques related to identifying, by a user equipment (UE), a received downlink control information (DCI) to schedule transmission of multiple code block bundles (CBBs). The DCI may indicate a new data indicator (NDI) for respective ones of the multiple CBBs. The technique may further relate to facilitating transmission or reception of one or more of the CBBs based on the DCI. Other embodiments may be described or claimed.

Description

DOWNLINK SCHEDULING INFORMATION TRANSMISSION FOR HIGH CARRIER FREQUENCIES

CROSS REFERENCE TO RELATED APPLICATION

The present application claims priority to U.S. Provisional Patent Application No. 63/125,318, which was filed December 14, 2020; U.S. Provisional Patent Application No. 63/134,109, which was filed January 5, 2021; and U.S. Provisional Patent Application No. 63/138,984, which was filed January 19, 2021.

FIELD

Various embodiments generally may relate to the field of wireless communications. For example, some embodiments may relate to downlink scheduling information transmission for high carrier frequencies.

BACKGROUND

Mobile communication has evolved significantly from early voice systems to current highly sophisticated integrated communication platforms. The next generation wireless communication system, fifth generation (5G), which may also be referred to as new radio (NR), may provide access to information and sharing of data anywhere, anytime by various users and applications. NR may be a unified network/ system that targets to meet vastly different and sometimes conflicting performance dimensions and services. Such diverse multi-dimensional requirements may be driven by different services and applications. In general, NR will evolve based on third generation partnership project (3GPP) long term evolution (LTE)-Advanced with additional potential new Radio Access Technologies (RATs) to enrich people lives with better, simple and seamless wireless connectivity solutions. NR may deliver fast, rich contents and services to wireless connectivity. Generally, the NR system operate based on a concept of slot. A physical downlink shared channel (PDSCH) or a physical uplink shared channel (PUSCH) may be restricted within a slot.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments will be readily understood by the following detailed description in conjunction with the accompanying drawings. To facilitate this description, like reference numerals designate like structural elements. Embodiments are illustrated by way of example and not by way of limitation in the figures of the accompanying drawings. Figure 1 schematically illustrates an example of long PDSCH transmission duration, in accordance with various embodiments.

Figure 2 illustrates an example of early termination of PDSCH transmission, in accordance with various embodiments.

Figure 3 illustrates an example of an indication of a new transmission or a retransmission, in accordance with various embodiments.

Figure 4 illustrates an alternative example of an indication of new transmission or retransmission, in accordance with various embodiments.

Figure 5 illustrates an alternative example of an indication of new transmission or retransmission, in accordance with various embodiments.

Figure 6 illustrates an example format for compressed signaling, in accordance with various embodiments.

Figure 7 schematically illustrates an example of grouping of new data indicator (NDI) and hybrid automatic repeat request (HARQ)-acknowledgement (ACK) bits for compressed signaling, in accordance with various embodiments.

Figure 8 illustrates an example of differential processing for compression, in accordance with various embodiments.

Figure 9 illustrates an example technique to be performed by a user equipment (UE), in accordance with various embodiments.

Figure 10 illustrates an example technique to be performed by a base station, in accordance with various embodiments.

Figure 11 schematically illustrates components of a wireless network in accordance with various embodiments.

Figure 12 schematically illustrates a wireless network in accordance with various embodiments.

Figure 13 schematically illustrates components of a wireless network in accordance with various embodiments.

DETAILED DESCRIPTION

The following detailed description refers to the accompanying drawings. The same reference numbers may be used in different drawings to identify the same or similar elements. In the following description, for purposes of explanation and not limitation, specific details are set forth such as particular structures, architectures, interfaces, techniques, etc. in order to provide a thorough understanding of the various aspects of various embodiments. However, it will be apparent to those skilled in the art having the benefit of the present disclosure that the various aspects of the various embodiments may be practiced in other examples that depart from these specific details. In certain instances, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the various embodiments with unnecessary detail. For the purposes of the present document, the phrases “A or B” and “A/B” mean (A), (B), or (A and B).

As previously noted, Mobile communication has evolved significantly from early voice systems to current highly sophisticated integrated communication platforms. The next generation wireless communication system, fifth generation (5G), which may also be referred to as NR, may provide access to information and sharing of data anywhere, anytime by various users and applications. NR may be a unified network/ system that targets to meet vastly different and sometimes conflicting performance dimensions and services. Such diverse multidimensional requirements may be driven by different services and applications. In general, NR will evolve based on third generation partnership project (3GPP) LTE-Advanced with additional potential new Radio Access Technologies (RATs) to enrich people lives with better, simple and seamless wireless connectivity solutions. NR may deliver fast, rich contents and services to wireless connectivity.

Additionally, as previously noted, the NR system operate based on a concept of slot. A PDSCH or a PUSCH may be restricted within a slot. Such restriction on PDSCH or PUSCH may still applies in high frequency carrier bands (e.g., carrier frequencies above approximately 52.6 gigahertz (GHz)). On the other hand, for a system operating at or above the approximately 52.6GHz carrier frequency, especially for Terahertz communication, a larger subcarrier spacing may be needed to combat severe phase noise. In cases where a larger subcarrier spacing, e.g., approximately 1.92 megahertz (MHz) or approximately 3.84MHz is employed, the slot duration may be relatively short. For instance, for a 1.92MHz subcarrier spacing, one slot duration may be approximately 7.8 microseconds (ps). This slot duration may not be sufficient for higher layer processing, including Medium Access Layer (MAC) and Radio Link Control (RLC), etc., because it may be too short. In order to address this issue, a next generation NodeB (gNB) may schedule the downlink (DL) or uplink (UL) data transmission across a slot boundary with long transmission duration. In other words, the slot concept may not be used when scheduling a given data transmission.

Figure 1 schematically illustrates an example of long PDSCH transmission duration, in accordance with various embodiments. Specifically, Figure 1 depicts a transmission 100 with a plurality of slots 105. A PDSCH transmission 110 may span several ones of the slots 105 as shown. In DL transmission, more DL traffic may arrive at the gNB when the gNB is still sending out DL downlink control information (DCI) or a previous PDSCH transmission. This new DL traffic may cause the gNB to send a new DL DCI to schedule a PDSCH, which may result in the delay of data transmissions. In one embodiment, the gNB may be allowed to schedule more DL resources than those required to transmit the current DL data in the buffer. Consequently, if new DL traffic arrives, the gNB may continue the PDSCH transmission for the new DL traffic on the scheduled DL resource. On the other hand, if there is no new incoming DL traffic, it may be desirable for the scheduled DL resources to be released earlier, e.g. early termination of the PDSCH transmission. In addition to the case of lacking new DL traffic, there may also exist other reasons that the gNB needs to terminate a DL transmission earlier. Figure 2 illustrates an example for which the allocated DL resources could carry 10 CBs, e.g. CBs 0-9 at 205. However, the DL transmission may be terminated only after the transmission of 6 CBs, e.g. CBs 6-9 at 210.

For the DL or UL transmission in NR, a transport block (TB) from the MAC layer may be transmitted at physical layer. For the hybrid automatic repeat request (HARQ) transmission of a giv4n DL transmission, a single HARQ-ACK bit may be reported by UE for a TB. Alternatively, if code block (CB) group (CBG) based transmission is configured, e.g. a TB is divided into n CBGs, n < N, N = 1,2, 4, 8 , a CBG may include one or multiple code block CBs. A CBG transmission indicator (CBGTI) field may be used to indicate whether a CBG is scheduled or not by a DCI. A UE may report n or N HARQ-ACK bits for the TB. One HARQ-ACK bit may be reported for each CBG. N may represent the maximum number of CBGs which may be configured by high layer. If a DCI schedules X TBs, then there may be X NDI bits in the DCI. For a system operating above 52.6GHz carrier frequency, especially for Terahertz communication, when the number of TBs or CBGs that are scheduled by a DCI is or may be large, a direct extension of the NDI or CBGTI field may result in large overhead in DCI. Various embodiments herein provide solutions for efficient indication in the DCI.

Specifically, embodiments herein relate to a detailed scheme to transmit downlink scheduling information for a carrier frequency at or above approximately 52.6GHz.

In the following descriptions, a DL or UL data transmission scheduled by a DCI may include M code block bundle (CBB)s, M CBGs, and/or M TBs. Each CBB may include one or multiple consecutive CBs. Cyclic redundancy check (CRC) may be added for each CB. However, there may not exist an additional CRC for the multiple CBs of a CB. A CBB may correspond to a MAC protocol data unit (PDU) or a TB. A separate HARQ process number (HPN) may be assigned to a CBB. A CBB may be mapped to all time/frequency resources of certain consecutive symbols. By this way, symbol alignment may be achieved for a CBB. A HARQ-ACK bit may be reported for a CBB. Alternatively, HARQ-ACK bits of multiple CBBs may be bundled into one bit to reduce the overhead of HARQ-ACK feedback.

Note that, for the sake of discussion of embodiments herein, CBB, CBG, and TB may be used inter changably.

HPN, NDI, redundancy version (RY) in a PCI

In the following embodiments, if early termination of PDSCH or PUSCH is not applied, the gNB or UE may continuously transmit the PDSCH or PUSCH in all the indicated time/frequency resources by the DCI. On the other hand, if early termination of PDSCH or PUSCH is applied, only the starting CBBs until the time of early termination may be transmitted. The remaining CBBs may be dropped.

In one embodiment of the disclosure, to schedule a downlink or uplink transmission, a DCI may indicate one or more of the following:

A start HPN which may apply to the first CBB scheduled by the DCI. The consecutive HPNs starting from the indicated start HPN may be serially used for subsequent multiple CBBs scheduled by the DCI.

One NDI bit for each CBB. The number of NDI bits may need to be dimensioned by the maximum number of CBBs which may be scheduled by the DCI. However, the actual number of CBBs transmitted by the gNB or UE may be smaller than the above maximum number.

One RV bit for each CBB. The number of RV bits may be equal to the number of NDI bits.

In one embodiment of the disclosure, if a joint DCI is used to schedule both downlink and uplink transmission, the DCI may indicate one or more of the following:

A start HPN which may apply to the first CBB scheduled by the DCI. The consecutive HPNs starting from the indicated start HPN may be serially used for subsequent CBBs scheduled by the DCI.

One NDI bit for each CBB of the scheduled PDSCH and PUSCH. The total number of NDI bits of the scheduled PDSCH and PUSCH by the DCI may be configured by high layer signaling. The exact number of NDI bits for the scheduled PDSCH and PUSCH may be further determined by a high layer signaling or indicated by the DCI. The actual number of CBBs transmitted by the gNB or NE may be smaller than the above maximum number.

One RV bit for each CBB. The number of RV bits may be equal to the number of NDI bits. In one embodiment of the disclosure, to schedule a downlink or uplink transmission, a DCI may indicate one or more of the following:

A start HPN which may apply to the first CBB scheduled by the DCI. The consecutive HPNs starting from the indicated start HPN may be serially used for the multiple subsequent CBBs scheduled by the DCI.

One NDI bit for each CBB. The number of NDI bits may need to be dimensioned by the maximum number of CBBs which can be scheduled by the DCI. However, the actual number of CBB transmitted by the gNB or NE may be smaller than the above maximum number.

One RV for all scheduled new transmissions and/or one RV for all scheduled retransmissions. Whether a CBB is a new transmission or retransmission may be derived by the NDI bit of the CBB. Then, the RV for the CBB can be determined.

In one embodiment of the disclosure, if a joint DCI is used to schedule both downlink and uplink transmission, the DCI may indicate

A start HPN which may apply to the first CBB scheduled by the DCI. The consecutive HPNs starting from the indicated start HPN may be serially used for the multiple subsequent CBBs scheduled by the DCI.

One NDI bit for each CBB of the scheduled PDSCH and PUSCH. The total number of NDI bits of the scheduled PDSCH and PUSCH by the DCI may be configured by high layer signaling. The exact number of NDI bits for the scheduled PDSCH and PUSCH may be further determined by a high layer signaling or indicated by the DCI. The actual number of CBBs transmitted by the gNB or NE may be smaller than the above maximum number.

One RV for all scheduled new transmissions and/or one RV for all scheduled retransmissions. Whether a CBB is a new transmission or retransmission may be derived by the NDI bit of the CBB. Then, the RV for the CBB can be determined.

In one embodiment of the disclosure, the CBBs that are scheduled by a DCI may be divided into two sets, e.g. setA and setB. To schedule a downlink or uplink transmission, the DCI may indicate one or more of the following:

A start HPN which may apply to the first CBB scheduled by the DCI. The consecutive HPNs starting from the indicated start HPN may be serially used for the multiple subsequent CBBs scheduled by the DCI.

One NDI bit may be indicated in the DCI to determine a new transmission or a retransmission for the HARQ process with start HPN. The same determination of new transmission or retransmission may apply to all CBBs in setA. The CBBs in setB may be indicated explicitly by the DCI. For example, the offset B from the indicated start HPN and the number of HPNs for setB may be be indicated. Alternatively, only offset B from the indicated start HPN may be indicated for setB, and setB may last until the maximum number of CCBs that are scheduled by the DCI have been transmitted. Alternatively, multiple sets of consecutive CCBs may be indicated for setB. In all cases, the setB may last until the maximum number of CCBs that are scheduled by the DCI are transmitted. A CBB in setB may have a different new transmission or retransmission from setA.

One RV for setA and/or one RV for setB. Each of the RV fields may use 2 bits or 1 bit.

Figure 3 illustrates the differentiation of setA 310 and setB 315. Specifically, Figure 3 depicts the start HPN 305, CBB setA 310, CBB setB 315, the maximum configured number of CBBs 320, the number of CBBs 325 in CBB set B 315, and the offset B 330. SetB 315 may have a size of 0 CBB, so that all scheduled CBB belong to setA 310 and follow the new transmission or retransmission of the HARQ process with start HPN 305.

In this scheme, if NDI is not indicated in the DCI, a fixed determination of new transmission or retransmission could apply to setA 310 and setB 315.

In this scheme, instead of a single NDI bit, two NDI bits can be indicated in the DCI to determine a new transmission or a retransmission for the HARQ process with start HPN. The same determination of new transmission or retransmission may apply to all CBBs in setA. The two NDI bits include one toggling bit and one absolute bit. From the gNB point of view, the toggling bit may indicate whether the current DCI schedules a new transmission or a retransmission for the HARQ process with the start HPN by checking whether the bit is toggled or not toggled. Meanwhile, the absolute bit may indicate whether the current DCI schedules a new transmission or a retransmission for the HARQ process with start HPN by checking the value of the bit directly. The toggling bit and the absolute bit may indicate the same information.

From the UE point of view, the absolute bit may indicate whether the current DCI schedules a new transmission or a retransmission for the HARQ process with start HPN by checking the value of the bit directly. Meanwhile, the toggling bit indicates whether the current DCI schedules a new TB or retransmission of the latest TB for the HARQ process with start HPN by checking whether the bit is toggled or not toggled. When the absolute bit indicates retransmission and the toggling bit indicates anew TB, the UE may be able to identify that at least one PDCCH is missed, and so the UE may schedule a retransmission of a new TB.

Figure 4 illustrates an example to check whether it is new transmission or retransmission for the start HPN using 2 NDI bits. For the sake of the discussion of Figure 4, it is assumed that the gNB sends a PDCCH 1 405 with HPN x which schedules a PDSCH. The toggling bit and absolute bit for NDI in PDCCH 1 405 are ‘0’ and ‘0’ respectively. Then, the UE may correctly receive (based on PDCCH 1 405) the PDSCH and transmits an ACK. The gNB may receive the ACK successfully and decide to schedule anew TB by transmitting PDCCH 2 410 using the same HPN x. To indicate a new transmission, the toggling bit and absolute bit for NDI in PDCCH 2 410 are ‘1’ and ‘1’ respectively. However, the UE may miss the PDCCH 2 410. The gNB may then transmit a PDCCH 3 415, which may schedule a retransmission of the new TB. The toggling bit and absolute bit for NDI in PDCCH 3 415 are ‘1’ and ‘0’ respectively. From the gNB point of view, comparing with PDCCH 2, the toggling bit in PDCCH 3 is not toggled, so it indicates retransmission, while the absolute bit indicates value ‘0’ which may also mean retransmission. From the UE point of view, after detection of PDCCH 3 415, the UE may know it is a retransmission by the absolute bit with value ‘O’. Meanwhile, the UE may know it is the retransmission of a new TB since the toggling bit is toggled in both PDCCH 3 415 and PDCCH 2 410.

In one embodiment of the disclosure, the CBBs for uplink data transmission that are scheduled by a DCI may be divided into three sets, e.g. setA, setB and setC. To schedule a downlink or uplink transmission, a DCI may indicate one or more of the following:

A start HPN, which may apply to the first CBB indicated by the DCI. The consecutive HPNs starting from the indicated start HPN may be serially used for the multiple subsequent CBBs indicated by the DCI.

One NDI bit may be indicated in the DCI to determine a new transmission or a retransmission for the HARQ process with the start HPN. The same determination of new transmission or retransmission may apply to all CBBs in setA.

The offset A of the first CBB in setA. The CBBs before the first CCB of setA may belong to setC. For a HPN in setC, it may be indicated that the CBB of the HPN is already successfully received at gNB, and there is no new CBB scheduled for the HPN. The CBBs in setB may be indicated explicitly by the DCI. A CBB in setB may have a different new transmission or retransmission from setA. For example, the offset B from the indicated start HPN and the number of HPNs for setB may be indicated by the DCI. Alternatively, only offset B from the indicated start HPN may be indicated for setB. Alternatively, multiple sets of consecutive CCBs may be indicated for setB. In all cases, the setB may last until the maximum number of CCBs that can be scheduled by the DCI. The total number of CBBs in setA, setB and setC may not exceed the maximum number of CBBs that are schedulable by a DCI. Alternatively, there may be no restriction on number of CBBs in setC, therefore, the total number of CBBs in setB and setC may not exceed the maximum number of CBBs that are schedulable by a DCI. One RV for setA and/or one RV for setB. Each RV field may use 2 bits or 1 bit.

Figure 5 illustrates the differentiation of setA 510, setB 515, and setC 535. Specifically, Figure 5 depicts the start HPN 505, CBB setA 510, CBB setB 515, the maximum configured number of CBBs 520, the number of CBBs 525 in CBB setB 515, the offset B 530, the CBB setC 535, and the offset A 540.

The offset A 540 may be 0, so that there is no CBB in setC 535. For a CBB in setC 535 of a UL transmission, the UE may flush the buffer of the CBB at the UE side. setB 515 may have a size of 0 CBB, so that all scheduled CBBs may belong to setA 510 and follow the new transmission or retransmission of the HARQ process with start HPN.

In this scheme, if NDI is not indicated in the DCI, a fixed determination of new transmission or retransmission could apply to setA 510 and/or setB 515.

In this scheme, instead of a single NDI bit, two NDI bits may be indicated in the DCI to determine a new transmission or a retransmission for the HARQ process with the start HPN 505. The same determination of new transmission or retransmission applies to all CBBs in setA 510. The two NDI bits includes one toggling bit and one absolute bit. From the gNB point of view, the toggling bit may indicate whether the current DCI schedules a new transmission or a retransmission for the HARQ process with start HPN by checking whether the bit is toggled or not toggled. Meanwhile, the absolute bit may indicate whether the current DCI schedules a new transmission or a retransmission for the HARQ process with start HPN 505 by checking the value of the bit directly. The toggling bit and the absolute bit may indicate the same information.

From the UE point of view, the absolute bit may indicate whether the current DCI schedules a new transmission or a retransmission for the HARQ process with start HPN 505 by checking the value of the bit directly. Meanwhile, the toggling bit may indicate whether the current DCI schedules a new TB or retransmission of the latest TB for the HARQ process with start HPN 505 by checking whether the bit is toggled or not toggled.

HARQ-ACK codebook based on HARQ processes

NR supports use of a Type3 HARQ-ACK codebook, which may be used to report HARQ- ACK bits for all configured HARQ processes. If the number of HPNs is large, e.g., on the order of approximately 100, the overhead for HARQ-ACK feedback in UL may also become very large too.

In one embodiment of the disclosure, to help to reduce the payload size of HARQ-ACK feedback, the start HPN and the number of consecutive HPNs may be indicated by a DCI. In this manner, the UE may only report HARQ-ACK for the indicated number of consecutive HPNs. Joint PCI to schedule PDSCH and/or PUSCH

A DCI may dynamically indicate the scheduling of PDSCH only, PUSCH only, or both PDSCH and PUSCH. In this case where both PDSCH and PUSCH are indicated, a two-bit field in the DCI is sufficient to differentiate the scheduling of PDSCH/PUSCH. It may be assumed for the sake of discussion of embodiments herein that HARQ-ACK is transmitted on PUSCH without the introduction of PUCCH.

If both PDSCH and PUSCH are scheduled by a DCI, the DCI may further indicate whether HARQ-ACK for a set of PDSCH(s) can be piggybacked on the PUSCH, e.g., by a 1 -bit indicator. In one embodiment, the set of PDSCH(s) may include the PDSCH scheduled by the DCI. In another embodiment, the set of PDSCH(s) may be required to include the PDSCH scheduled by the DCI.

If PDSCH is scheduled by a DCI without a scheduled UL data transmission, the fields in the DCI that are typically used for the UL data scheduling may be reused to indicate a PUSCH resource for the HARQ-ACK feedback. For example, certain value(s) of the timedomainresourceallocation (TDRA) field for PUSCH may be used to indicate the PUSCH resource. The value(s) may indicate a PUSCH resource that may not be used to carry uplink data transmission. Alternatively, the value(s) may indicate a PUSCH resource that may be used carry uplink data transmission irrespective of the piggyback of uplink control information.

If PUSCH is scheduled by a DCI without a scheduled DL data transmission, the DCI may further indicate whether HARQ-ACK for a set of PDSCH(s) may be piggybacked on the PUSCH, e.g., using a 1 -bit indicator.

Compression of NDI and HARQ-ACK

In one embodiment NDI indication in DCI and HARQ-ACK reporting in UL control information (UCI) for CBBs may be compressed to reduce signaling overhead. The compression may be achieved by signaling of the index of the bit sequence corresponding to the desired NDI and HARQ-ACK instead of the actual sequences of the bits. The overhead reduction may be achieved by defining an index for bit sequences more frequently used in the system. More specifically, the typical block error rate (BLER) is 0.1 for PDSCH and PUSCH transmission meaning that only 10% of CBBs are transmitted with errors.

For a sequence of length N corresponding to N CBBs, the compressed signaling may be defined as follows:

• 1 -bit indicating type of pattern - K ones or K zeros in the sequence of length N

• ceil(log2(Kmax) bits - actual number K (K<Kmax) of ones / zeros (depending of pattern type) in the sequence of length N • ceil(log2(nchoosek(N,K))) bits - index indicating position of K ones / zeros in the sequence of length N using combinatorial index (binomial coefficient enumeration) based on nchoosek() function

The format of compressed signaling is illustrated in Figure 6. Specifically, Figure 6 depicts a portion 605 that indicates pattern type (e.g., corresponding to the 1 -bit indicating type of pattern), a portion 610 that indicates the number of ones/zeros in the sequence (e.g., the ceil(log2(Kmax) bits), and a portion 615 that indicates the position of the ones and zeros in the sequence (e.g., the ceil(log2(nchoosek(N,K))) bits).

In another embodiment the sequence of bits used for NDI indication or HARQ-ACK reporting may be segmented into multiple sub-sequences of a pre-determined length. Each subsequence may be compressed independently from each other. An example of this is depicted in Figure 7 showing the overall sequence of bits 700, and then multiple sub-sequences 705 that are identifies as Group 1, Group 2, ... , Group P-1, and Group P.

In the other embodiment HARQ-ACK and NDI compression may be achieved by using start and length indicator value (SLIV) indication in the sequence of length N assuming a consecutive HARQ-ACK/NACK bits. The signaling of the offset and window may be defined by the nchoosek() function as described below. The signaling may optionally indicate the individual HARQ-ACK bits or NDI within the indicated window using combinatorial index (binomial coefficient enumeration) based on nchoosek() function such that K can be kept small.

The nchoosek function may be defined as n(n-l)(n-2)...(n-k+l) / k!. The combinatorial index may be defined as follows:

where 1 < so < si < ... < SK-I < N are the K sorted indices of bit for indication in the sequence of length N, and x > y

x < y

In another embodiment of the disclosure, the sequence of HARQ-ACK or NDI bits may be processed differentially to further reduce the number of bits for indications using a combinatorial index. More specifically, the original sequence b(i) may be updated to sequence c(i) as follows c(i) = b(i) ® b(i — 1) , where ® is XOR operation, i = 1...N and b(0) = 0. Then the compression function may be applied to the sequence c(i) . The example of this embodiment is illustrated in Figure 8. Specifically, Figure 8 depicts an example b it sequence b(i) 805 and c(i) 810. In some embodiments, the electronic device(s), network(s), system(s), chip(s) or component(s), or portions or implementations thereof, of Figures 11-13, below, or some other figure herein, may be configured to perform one or more processes, techniques, or methods as described herein, or portions thereof. One such process is depicted in Figure 9. In some embodiments, the process of Figure 9 may be performed by a UE or a portion thereof. For example, the process may include, at 901, identifying a received DCI to schedule transmission of multiple CBBs, wherein the DCI indicates aNDI for respective ones of the multiple CBBs.

At 902, the process may further include facilitating transmission or reception for one or more of the CBBs based on the DCI. For example, the CBBs may include downlink CBBs (e.g., received by the UE on a PDSCH) and/or uplink CBBs (e.g., transmitted by the UE on a PUSCH).

Figure 10 illustrates another process in accordance with various embodiments. In some embodiments, the process of Figure 10 may be performed by a base station (e.g., a gNB) or a portion thereof. For example, the process may include, at 1001, facilitating transmission of a DCI to a UE, the DCI to schedule transmission of multiple CBBs, wherein the DCI indicates a NDI for respective ones of the CBBs.

At 1002, the process may further include facilitating transmission or reception of the multiple CBBs based on the DCI. For example, the CBBs may include downlink CBBs (e.g., transmitted by the gNB on a PDSCH) and/or uplink CBBs (e.g., received by the gNB on a PUSCH).

For one or more embodiments, 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. For example, 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. For another example, 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.

Figures 11-13 illustrate various systems, devices, and components that may implement aspects of disclosed embodiments.

Figure 11 illustrates a network 1100 in accordance with various embodiments. The network 1100 may operate in a manner consistent with 3GPP technical specifications for LTE or 5G/NR systems. However, 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 1100 may include a UE 1102, which may include any mobile or non-mobile computing device designed to communicate with a RAN 1104 via an over-the-air connection. The UE 1102 may be communicatively coupled with the RAN 1104 by a Uu interface. The UE 1102 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, electron! c/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.

In some embodiments, the network 1100 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.

In some embodiments, the UE 1102 may additionally communicate with an AP 1106 via an over-the-air connection. The AP 1106 may manage a WLAN connection, which may serve to offload some/all network traffic from the RAN 1104. The connection between the UE 1102 and the AP 1106 may be consistent with any IEEE 802.11 protocol, wherein the AP 1106 could be a wireless fidelity (Wi-Fi®) router. In some embodiments, the UE 1102, RAN 1104, and AP 1106 may utilize cellular- WLAN aggregation (for example, LWA/LWIP). Cellular- WLAN aggregation may involve the UE 1102 being configured by the RAN 1104 to utilize both cellular radio resources and WLAN resources.

The RAN 1104 may include one or more access nodes, for example, AN 1108. AN 1108 may terminate air interface protocols for the UE 1102 by providing access stratum protocols including RRC, PDCP, RLC, MAC, and LI protocols. In this manner, the AN 1108 may enable data/voice connectivity between CN 1120 and the UE 1102. In some embodiments, the AN 1108 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 1108 be referred to as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc. The AN 1108 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.

In embodiments in which the RAN 1104 includes a plurality of ANs, they may be coupled with one another via an X2 interface (if the RAN 1104 is an LTE RAN) or an Xn interface (if the RAN 1104 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 1104 may each manage one or more cells, cell groups, component carriers, etc. to provide the UE 1102 with an air interface for network access. The UE 1102 may be simultaneously connected with a plurality of cells provided by the same or different ANs of the RAN 1104. For example, the UE 1102 and RAN 1104 may use carrier aggregation to allow the UE 1102 to connect with a plurality of component carriers, each corresponding to a Pcell or Scell. In dual connectivity scenarios, 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 1104 may provide the air interface over a licensed spectrum or an unlicensed spectrum. To operate in the unlicensed spectrum, the nodes may use LAA, eLAA, and/or feLAA mechanisms based on CA technology with PCells/Scells. Prior to accessing the unlicensed spectrum, the nodes may perform medium/carrier-sensing operations based on, for example, a listen-before-talk (LBT) protocol.

In V2X scenarios the UE 1102 or AN 1108 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. In one example, 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.

In some embodiments, the RAN 1104 may be an LTE RAN 1110 with eNBs, for example, eNB 1112. The LTE RAN 1110 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.

In some embodiments, the RAN 1104 may be an NG-RAN 1114 with gNBs, for example, gNB 1116, or ng-eNBs, for example, ng-eNB 1118. The gNB 1116 may connect with 5G-enabled UEs using a 5G NR interface. The gNB 1116 may connect with a 5G core through an NG interface, which may include an N2 interface or an N3 interface. The ng-eNB 1118 may also connect with the 5G core through an NG interface, but may connect with a UE via an LTE air interface. The gNB 1116 and the ng-eNB 1118 may connect with each other over an Xn interface.

In some embodiments, 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 1114 and a UPF 1148 (e.g., N3 interface), and an NG control plane (NG-C) interface, which is a signaling interface between the nodes of the NG-RAN1114 and an AMF 1144 (e.g., N2 interface).

The NG-RAN 1114 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.

In some embodiments, the 5G-NR air interface may utilize BWPs for various purposes. For example, BWP can be used for dynamic adaptation of the SCS. For example, the UE 1102 can be configured with multiple BWPs where each BWP configuration has a different SCS. When a BWP change is indicated to the UE 1102, the SCS of the transmission is changed as well. Another use case example of BWP is related to power saving. In particular, multiple BWPs can be configured for the UE 1102 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 1102 and in some cases at the gNB 1116. A BWP containing a larger number of PRBs can be used for scenarios with higher traffic load.

The RAN 1104 is communicatively coupled to CN 1120 that includes network elements to provide various functions to support data and telecommunications services to customers/subscribers (for example, users of UE 1102). The components of the CN 1120 may be implemented in one physical node or separate physical nodes. In some embodiments, NFV may be utilized to virtualize any or all of the functions provided by the network elements of the CN 1120 onto physical compute/storage resources in servers, switches, etc. A logical instantiation of the CN 1120 may be referred to as a network slice, and a logical instantiation of a portion of the CN 1120 may be referred to as a network sub-slice.

In some embodiments, the CN 1120 may be an LTE CN 1122, which may also be referred to as an EPC. The LTE CN 1122 may include MME 1124, SGW 1126, SGSN 1128, HSS 1130, PGW 1132, and PCRF 1134 coupled with one another over interfaces (or “reference points”) as shown. Functions of the elements of the LTE CN 1122 may be briefly introduced as follows.

The MME 1124 may implement mobility management functions to track a current location of the UE 1102 to facilitate paging, bearer activation/deactivation, handovers, gateway selection, authentication, etc.

The SGW 1126 may terminate an SI interface toward the RAN and route data packets between the RAN and the LTE CN 1122. The SGW 1126 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 1128 may track a location of the UE 1102 and perform security functions and access control. In addition, the SGSN 1128 may perform inter-EPC node signaling for mobility between different RAT networks; packet data network (PDN) and S-GW selection as specified by MME 1124; MME selection for handovers; etc. The S3 reference point between the MME 1124 and the SGSN 1128 may enable user and bearer information exchange for inter-3GPP access network mobility in idle/active states.

The HSS 1130 may include a database for network users, including subscription-related information to support the network entities’ handling of communication sessions. The HSS 1130 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc. An S6a reference point between the HSS 1130 and the MME 1124 may enable transfer of subscription and authentication data for authenticating/ authorizing user access to the LTE CN 1120.

The PGW 1132 may terminate an SGi interface toward a data network (DN) 1136 that may include an application/content server 1138. The PGW 1132 may route data packets between the LTE CN 1122 and the data network 1136. The PGW 1132 may be coupled with the SGW 1126 by an S5 reference point to facilitate user plane tunneling and tunnel management. The PGW 1132 may further include a node for policy enforcement and charging data collection (for example, PCEF). Additionally, the SGi reference point between the PGW 1132 and the data network 11 36 may be an operator external public, a private PDN, or an intra-operator PDN, for example, for provision of IMS services. The PGW 1132 may be coupled with a PCRF 1134 via a Gx reference point.

The PCRF 1134 is the policy and charging control element of the LTE CN 1122. The PCRF 1134 may be communicatively coupled to the app/content server 1138 to determine appropriate QoS and charging parameters for service flows. The PCRF 1132 may provision associated rules into a PCEF (via Gx reference point) with appropriate TFT and QCI.

In some embodiments, the CN 1120 may be a 5GC 1140. The 5GC 1140 may include an AUSF 1142, AMF 1144, SMF 1146, UPF 1148, NSSF 1150, NEF 1152, NRF 1154, PCF 1156, UDM 1158, and AF 1160 coupled with one another over interfaces (or “reference points”) as shown. Functions of the elements of the 5GC 1140 may be briefly introduced as follows.

The AUSF 1142 may store data for authentication of UE 1102 and handle authentication- related functionality. The AUSF 1142 may facilitate a common authentication framework for various access types. In addition to communicating with other elements of the 5GC 1140 over reference points as shown, the AUSF 1142 may exhibit an Nausf service-based interface.

The AMF 1144 may allow other functions of the 5GC 1140 to communicate with the UE 1102 and the RAN 1104 and to subscribe to notifications about mobility events with respect to the UE 1102. The AMF 1144 may be responsible for registration management (for example, for registering UE 1102), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization. The AMF 1144 may provide transport for SM messages between the UE 1102 and the SMF 1146, and act as a transparent proxy for routing SM messages. AMF 1144 may also provide transport for SMS messages between UE 1102 and an SMSF. AMF 1144 may interact with the AUSF 1142 and the UE 1102 to perform various security anchor and context management functions. Furthermore, AMF 1144 may be a termination point of a RAN CP interface, which may include or be an N2 reference point between the RAN 1104 and the AMF 1144; and the AMF 1144 may be a termination point of NAS (Nl) signaling, and perform NAS ciphering and integrity protection. AMF 1144 may also support NAS signaling with the UE 1102 over an N3 IWF interface.

The SMF 1146 may be responsible for SM (for example, session establishment, tunnel management between UPF 1148 and AN 1108); UE IP address allocation and management (including optional authorization); selection and control of UP function; configuring traffic steering at UPF 1148 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 1144 over N2 to AN 1108; 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 1102 and the data network 1136.

The UPF 1148 may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point of interconnect to data network 1136, and a branching point to support multi-homed PDU session. The UPF 1148 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 1148 may include an uplink classifier to support routing traffic flows to a data network.

The NSSF 1150 may select a set of network slice instances serving the UE 1102. The NSSF 1150 may also determine allowed NSSAI and the mapping to the subscribed S-NSSAIs, if needed. The NSSF 1150 may also determine the AMF set to be used to serve the UE 1102, or a list of candidate AMFs based on a suitable configuration and possibly by querying the NRF 1154. The selection of a set of network slice instances for the UE 1102 may be triggered by the AMF 1144 with which the UE 1102 is registered by interacting with the NSSF 1150, which may lead to a change of AMF. The NSSF 1150 may interact with the AMF 1144 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 1150 may exhibit an Nnssf service-based interface.

The NEF 1152 may securely expose services and capabilities provided by 3GPP network functions for third party, internal exposure/re-exposure, AFs (e.g., AF 1160), edge computing or fog computing systems, etc. In such embodiments, the NEF 1152 may authenticate, authorize, or throttle the AFs. NEF 1152 may also translate information exchanged with the AF 1160 and information exchanged with internal network functions. For example, the NEF 1152 may translate between an AF-Service-Identifier and an internal 5GC information. NEF 1152 may also receive information from other NFs based on exposed capabilities of other NFs. This information may be stored at the NEF 1152 as structured data, or at a data storage NF using standardized interfaces. The stored information can then be re-exposed by the NEF 1152 to other NFs and AFs, or used for other purposes such as analytics. Additionally, the NEF 1152 may exhibit an Nnef servicebased interface.

The NRF 1154 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 1154 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 1154 may exhibit the Nnrf service-based interface.

The PCF 1156 may provide policy rules to control plane functions to enforce them, and may also support unified policy framework to govern network behavior. The PCF 1156 may also implement a front end to access subscription information relevant for policy decisions in a UDR of the UDM 1158. In addition to communicating with functions over reference points as shown, the PCF 1156 exhibit an Npcf service-based interface.

The UDM 1158 may handle subscription-related information to support the network entities’ handling of communication sessions, and may store subscription data of UE 1102. For example, subscription data may be communicated via an N8 reference point between the UDM 1158 and the AMF 1144. The UDM 1158 may include two parts, an application front end and a UDR. The UDR may store subscription data and policy data for the UDM 1158 and the PCF 1156, and/or structured data for exposure and application data (including PFDs for application detection, application request information for multiple UEs 1102) for the NEF 1152. The Nudr service-based interface may be exhibited by the UDR 221 to allow the UDM 1158, PCF 1156, and NEF 1152 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. In addition to communicating with other NFs over reference points as shown, the UDM 1158 may exhibit the Nudm service-based interface.

The AF 1160 may provide application influence on traffic routing, provide access to NEF, and interact with the policy framework for policy control.

In some embodiments, the 5GC 1140 may enable edge computing by selecting operator/3^rd party services to be geographically close to a point that the UE 1102 is attached to the network. This may reduce latency and load on the network. To provide edge computing implementations, the 5GC 1140 may select a UPF 1148 close to the UE 1102 and execute traffic steering from the UPF 1148 to data network 1136 via the N6 interface. This may be based on the UE subscription data, UE location, and information provided by the AF 1160. In this way, the AF 1160 may influence UPF (re)selection and traffic routing. Based on operator deployment, when AF 1160 is considered to be a trusted entity, the network operator may permit AF 1160 to interact directly with relevant NFs. Additionally, the AF 1160 may exhibit an Naf service-based interface. The data network 1136 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 1138.

Figure 12 schematically illustrates a wireless network 1200 in accordance with various embodiments. The wireless network 1200 may include a UE 1202 in wireless communication with an AN 1204. The UE 1202 and AN 1204 may be similar to, and substantially interchangeable with, like-named components described elsewhere herein.

The UE 1202 may be communicatively coupled with the AN 1204 via connection 1206. The connection 1206 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 5GNR protocol operating at mmWave or sub-6GHz frequencies.

The UE 1202 may include a host platform 1208 coupled with a modem platform 1210. The host platform 1208 may include application processing circuitry 1212, which may be coupled with protocol processing circuitry 1214 of the modem platform 1210. The application processing circuitry 1212 may run various applications for the UE 1202 that source/sink application data. The application processing circuitry 1212 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 1214 may implement one or more of layer operations to facilitate transmission or reception of data over the connection 1206. The layer operations implemented by the protocol processing circuitry 1214 may include, for example, MAC, RLC, PDCP, RRC and NAS operations.

The modem platform 1210 may further include digital baseband circuitry 1216 that may implement one or more layer operations that are “below” layer operations performed by the protocol processing circuitry 1214 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.

The modem platform 1210 may further include transmit circuitry 1218, receive circuitry 1220, RF circuitry 1222, and RF front end (RFFE) 1224, which may include or connect to one or more antenna panels 1226. Briefly, the transmit circuitry 1218 may include a digital-to-analog converter, mixer, intermediate frequency (IF) components, etc.; the receive circuitry 1220 may include an analog-to-digital converter, mixer, IF components, etc.; the RF circuitry 1222 may include a low-noise amplifier, a power amplifier, power tracking components, etc.; RFFE 1224 may include filters (for example, surface/bulk acoustic wave filters), switches, antenna tuners, beamforming components (for example, phase-array antenna components), etc. The selection and arrangement of the components of the transmit circuitry 1218, receive circuitry 1220, RF circuitry 1222, RFFE 1224, and antenna panels 1226 (referred generically as “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. In some embodiments, the transmit/receive components may be arranged in multiple parallel transmit/receive chains, may be disposed in the same or different chips/modules, etc.

In some embodiments, the protocol processing circuitry 1214 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 1226, RFFE 1224, RF circuitry 1222, receive circuitry 1220, digital baseband circuitry 1216, and protocol processing circuitry 1214. In some embodiments, the antenna panels 1226 may receive a transmission from the AN 1204 by receive-beamforming signals received by a plurality of antennas/antenna elements of the one or more antenna panels 1226.

A UE transmission may be established by and via the protocol processing circuitry 1214, digital baseband circuitry 1216, transmit circuitry 1218, RF circuitry 1222, RFFE 1224, and antenna panels 1226. In some embodiments, the transmit components of the UE 1204 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 1226.

Similar to the UE 1202, the AN 1204 may include a host platform 1228 coupled with a modem platform 1230. The host platform 1228 may include application processing circuitry 1232 coupled with protocol processing circuitry 1234 of the modem platform 1230. The modem platform may further include digital baseband circuitry 1236, transmit circuitry 1238, receive circuitry 1240, RF circuitry 1242, RFFE circuitry 1244, and antenna panels 1246. The components of the AN 1204 may be similar to and substantially interchangeable with like- named components of the UE 1202. In addition to performing data transmission/reception as described above, the components of the AN 1208 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 13 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. Specifically, Figure 13 shows a diagrammatic representation of hardware resources 1300 including one or more processors (or processor cores) 1310, one or more memory /storage devices 1320, and one or more communication resources 1330, each of which may be communicatively coupled via a bus 1340 or other interface circuitry. For embodiments where node virtualization (e.g., NFV) is utilized, a hypervisor 1302 may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 1300.

The processors 1310 may include, for example, a processor 1312 and a processor 1314. The processors 1310 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 digital signal processors (DSP) such as a baseband processor, an Application Specific Integrated Circuit (ASIC), an FPGA, a radio frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.

The memory /storage devices 1320 may include main memory, disk storage, or any suitable combination thereof. The memory /storage devices 1320 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.

The communication resources 1330 may include interconnection or network interface controllers, components, or other suitable devices to communicate with one or more peripheral devices 1304 or one or more databases 1306 or other network elements via a network 1308. For example, the communication resources 1330 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 1350 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 1310 to perform any one or more of the methodologies discussed herein. The instructions 1350 may reside, completely or partially, within at least one of the processors 1310 (e.g., within the processor’s cache memory), the memory /storage devices 1320, or any suitable combination thereof. Furthermore, any portion of the instructions 1350 may be transferred to the hardware resources 1300 from any combination of the peripheral devices 1304 or the databases 1306. Accordingly, the memory of processors 1310, the memory/storage devices 1320, the peripheral devices 1304, and the databases 1306 are examples of computer-readable and machine-readable media.

EXAMPLES

Example 1 may include a method of wireless communication to transmit downlink scheduling information for above 52.6GHz carrier frequency.

Example 2 may include the method of example 1 or some other example herein, wherein if a joint DCI is used to schedule both downlink and uplink transmission, the total number of NDI bits of the scheduled PDSCH and PUSCH by the DCI is configured by high layer signaling.

Example 3 may include the method of example 2 or some other example herein, wherein the exact number of NDI bits for the scheduled PDSCH and PUSCH is determined by a high layer signaling or indicated by the DCI.

Example 4 may include the method of example 1 or some other example herein, wherein the CBBs that are scheduled by a DCI is divided into two sets, e.g. setA and setB, the DCI indicates a start HPN and one NDI bit to determine a new transmission or a retransmission for the HARQ process with start HPN.

Example 5 may include the method of example 4 or some other example herein, wherein the determined new transmission or retransmission applies to all CBBs in set A.

Example 6 may include the method of example 4 or some other example herein, wherein the CBBs in setB are indicated explicitly by the DCI which use a different new transmission or retransmission from setA.

Example 7 may include the method of example 4 or some other example herein, wherein the DCI includes one RV for set A and/or one RV for setB.

Example 8 may include the method of example 1 or some other example herein, wherein the CBBs that are scheduled by a DCI is divided into three sets, e.g. setA, setB and setC, the DCI indicates a start HPN and one NDI bit to determine a new transmission or a retransmission for the HARQ process with start HPN.

Example 9 may include the method of example 8 or some other example herein, wherein for a HPN in setC, it is ACKed and there is no new CBB scheduled with the HPN.

Example 10 may include the method of example 8 or some other example herein, wherein the start CBB of setA is indicated by an offset from the start HARQ procee number, and the determined new transmission or retransmission applies to all CBBs in set A. Example 11 may include the method of example 8 or some other example herein, wherein the CBBs in setB are indicated explicitly by the DCI which use a different new transmission or retransmission from setA.

Example 12 may include the method of example 8 or some other example herein, wherein the DCI includes one RV for set A and/or one RV for setB.

Example 13 may include the method of example 1 or some other example herein, wherein the DCI indicates a start HPN and a number of consecutive HARQ process numbers.

Example 14 may include the method of example 1 or some other example herein, wherein if a DCI dynamically indicates the scheduling of PDSCH and PUSCH, the DCI indicates whether HARQ-ACK for a set of PDSCH(s) is piggybacked on the PUSCH.

Example 15 may include the method of example 14 or some other example herein, wherein the set of PDSCH(s) doesn’t include the PDSCH scheduled by the DCI, or , the set of PDSCH(s) include the PDSCH scheduled by the DCI.

Example 16 may include the method of example 1 or some other example herein, wherein if a DCI dynamically indicates the scheduling of PDSCH without PUSCH, the fields in the DCI that is for the uplink data scheduling is reused to indicate a PUSCH resource for the HARQ-ACK feedback.

Example 17 may include the method of example 16 or some other example herein, wherein TDRA field for PUSCH scheduling indicates the PUSCH resource.

Example 18 may include a method of compressed control signaling, wherein the compression is applied to the sequence of length N based on the combinatorial index.

Example 19 may include the method of example 18 or some other example herein, wherein the control signaling is DL control information (DCI).

Example 20 may include the method of example 18 or some other example herein, wherein the control signaling is UCI.

Example 21 may include the method of examples 18 and/or 19 or some other example herein, wherein the sequence of length N is NDI field.

Example 22 may include the method of examples 18 and/or 20 or some other example herein, wherein the sequence of length N is HARQ-ACK field.

Example 23 may include the method of example 18 or some other example herein, wherein the compressed sequence include pattern type field indicating whether the sequence of length N contains K ones (N-K zeros) or K zeros (N-K ones).

Example 24 may include the method of example 18 or some other example herein, wherein the compressed sequence include the actual number K (K<Kmax) of ones / zeros (depending of pattern type) in the sequence of length N. Example 25 may include the method of example 18 or some other example herein, wherein the compressed sequence include combinatorial index indicating position of K ones or K zeros in the sequence of length N.

Example 26 may include the method of example 18 or some other example herein, wherein the sequence of length N is additionally processed before compression using differential equation, wherein differential operation is exclusive or (XOR) operation between two adjacent bits.

Example 27 may include the method of example 18 or some other example herein, wherein the sequence of length N is additionally segmented into two or more blocks of smaller length before applying compression operation.

Example 28 may include the method of example 16 or some other example herein, wherein TDRA field for PUSCH scheduling indicates the PUSCH resource.

Example 29 may include a method comprising: receiving a DCI to schedule transmission of multiple code block bundles CBBs, wherein the DCI indicates aNDI for each of the CBBs; and transmitting or receiving the CBBs based on the DCI.

Example 30 may include the method of example 29 or some other example herein, wherein the CBBs include a downlink CBB and an uplink CBB.

Example 31 may include the method of example 29-30 or some other example herein, wherein the DCI indicates a start HPN for a first CBB of the multiple CBBs.

Example 32 may include the method of example 29-31 or some other example herein, further comprising receiving configuration information to indicate a size of an NDI field that includes the NDIs.

Example 33a may include the method of example 29-32 or some other example herein, wherein the NDIs are individual bits.

Example 33b may include the method of example 29-32 or some other example herein, wherein the NDIs include a toggling bit and an absolute bit.

Example 33c may include the method of example 33b or some other example herein, wherein the toggling bit is to indicate whether the DCI schedules a new transmission or a retransmission for the associated HARQ process based on whether a value of the toggling bit is toggled, and wherein the absolute bit is to indicate whether the DCI schedules a new transmission or a retransmission for the associated HARQ process based on a direct value of the absolute bit. Example 34 may include the method of example 29-33 or some other example herein, wherein the DCI further includes a redundancy version (RV) indicator for each CBB of the multiple CBBs.

Example 35 may include the method of example 29-33 or some other example herein, wherein the DCI further includes an RV indicator that applies to all new transmissions and/or an RV indicator that applies to all retransmissions scheduled by the DCI.

Example 36 may include the method of example 29-35 or some other example herein, wherein the DCI includes an index that indicates a bit sequence that corresponds to the NDIs.

Example 37 may include the method of example 29-36 or some other example herein, wherein the method is performed by a UE or a portion thereof.

Example 38 may include a method comprising: transmitting a DCI to a UE to schedule transmission of multiple CBBs, wherein the DCI indicates a NDI for each of the CBBs; and transmitting or receiving the CBBs based on the DCI.

Example 39 may include the method of example 38 or some other example herein, wherein the CBBs include a downlink CBB and an uplink CBB.

Example 40 may include the method of example 38-39 or some other example herein, wherein the DCI indicates a start HPN for a first CBB of the multiple CBBs.

Example 41 may include the method of example 38-40 or some other example herein, further comprising transmitting configuration information to the UE to indicate a size of an NDI field that includes the NDIs.

Example 42a may include the method of example 38-41 or some other example herein, wherein the NDIs are individual bits.

Example 42b may include the method of example 38-41 or some other example herein, wherein the NDIs include a toggling bit and an absolute bit.

Example 42c may include the method of example 42b or some other example herein, wherein, from a perspective of the UE, the toggling bit is to indicate whether the DCI schedules a new transmission or a retransmission for the associated HARQ process based on whether a value of the toggling bit is toggled, and wherein the absolute bit is to indicate whether the DCI schedules a new transmission or a retransmission for the associated HARQ process based on a direct value of the absolute bit.

Example 43 may include the method of example 38-42 or some other example herein, wherein the DCI further includes a redundancy version (RV) indicator for each CBB of the multiple CBBs. Example 44 may include the method of example 38-42 or some other example herein, wherein the DCI further includes an RV indicator that applies to all new transmissions and/or an RV indicator that applies to all retransmissions scheduled by the DCI.

Example 45 may include the method of example 38-43 or some other example herein, wherein the DCI includes an index that indicates a bit sequence that corresponds to the NDIs.

Example 46 may include the method of example 38-45 or some other example herein, wherein the method is performed by a gNB or a portion thereof.

Example 47 may include the method of example 29-46 or some other example herein, wherein the CBBs are scheduled for transmission on a frequency of greater than 52.6 GHz.

Example 48 includes a user equipment (UE) comprising: one or more processors; and one or more non-transitory computer-readable media comprising instructions that, upon execution of the instructions by the one or more processors, are to cause the one or more processors to: identify a received downlink control information (DCI) to schedule transmission of multiple code block bundles (CBBs), wherein the DCI indicates a new data indicator (NDI) for respective ones of the multiple CBBs; and facilitate transmission or reception of one or more of the CBBs based on the DCI.

Example 49 includes the UE of example 48, or some other example herein, wherein the multiple CBBs include a downlink CBB and an uplink CBB.

Example 50 includes the UE of example 48, or some other example herein, wherein the DCI indicates a start hybrid automatic repeat request (HARQ) process number (HPN) for a first CBB of the multiple CBBs.

Example 51 includes the UE of example 48, or some other example herein, wherein the instructions are further to cause the one or more processors to identify received configuration information that indicates a number of NDI bits that includes the NDIs for the respective ones of the multiple CBBs.

Example 52 includes the UE of example 48, or some other example herein, wherein the NDIs for the respective ones of the multiple CBBs are individual bits.

Example 53 includes the UE of example 48, or some other example herein, wherein respective NDIs for the respective ones of the multiple CBBs include a toggling bit and an absolute bit.

Example 54 includes the UE of example 53, or some other example herein, wherein the toggling bit is to indicate whether the DCI schedules a new transmission or a retransmission for the associated HARQ process based on whether a value of the toggling bit is toggled, and wherein the absolute bit is to indicate whether the DCI schedules a new transmission or a retransmission for the associated HARQ process based on a direct value of the absolute bit. Example 55 includes the UE of example 48, or some other example herein, wherein the DCI further includes a redundancy version (RV) indicator for respective CBBs of the multiple CBBs.

Example 56 includes the UE of example 48, or some other example herein, wherein the DCI further includes a redundancy version (RV) indicator that applies to all new transmissions scheduled by the DCI, or an RV indicator that applies to all retransmissions scheduled by the DCI.

Example 57 includes the UE of example 48, or some other example herein, wherein the DCI includes an index that indicates a bit sequence that corresponds to the NDIs for the respective ones of the multiple CBBs, wherein the bit sequence is based on an nchoosekQ function or a combinatorial index.

Example 58 includes a base station comprising: one or more processors; and one or more non-transitory computer-readable media comprising instructions that, upon execution of the instructions by the one or more processors, are to cause the one or more processors to: facilitate transmission of a downlink control information (DCI) to a user equipment (UE), the DCI to schedule transmission of multiple code block bundles (CBBs), wherein the DCI indicates a new data indicator (NDI) for respective ones of the CBBs; and facilitate transmission or reception of the multiple CBBs based on the DCI.

Example 59 includes the base station of example 58, or some other example herein, wherein the multiple CBBs include a downlink CBB and an uplink CBB.

Example 60 includes the base station of example 58, or some other example herein, wherein the DCI indicates a start hybrid automatic repeat request (HARQ) process number (HPN) for a first CBB of the multiple CBBs.

Example 61 includes the base station of example 58, or some other example herein, wherein the instructions are further to facilitate transmission of configuration information to the UE, the configuration information to indicate a number of NDI bits that includes the NDIs for the respective ones of the CBBs.

Example 62 includes the base station example 58, or some other example herein, wherein the NDIs for the respective ones of the CBBs are individual bits.

Example 63 includes the base station example 58, or some other example herein, wherein respective NDIs include a toggling bit and an absolute bit.

Example 64 includes the base station of example 58, or some other example herein, wherein the DCI further includes a redundancy version (RV) indicator for each CBB of the multiple CBBs. Example 65 includes the base station of example 58, or some other example herein, wherein the DCI further includes a redundancy version (RV) indicator that applies to all new transmissions scheduled by the DCI or all retransmissions scheduled by the DCI.

Example 66 includes the base station of example 58, or some other example herein, wherein the DCI includes an index that indicates a bit sequence that corresponds to the NDIs, wherein the bit sequence is based on an nchoosekQ function or a combinatorial index.

Example 67 includes the base station of example 58, or some other example herein, wherein the CBBs are scheduled for transmission on a frequency of greater than 52.6 gigahertz (GHz).

Example 68 may include an apparatus comprising means to perform one or more elements of a method described in or related to any of examples 1-67, or any other method or process described herein.

Example 69 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-67, or any other method or process described herein.

Example 70 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-67, or any other method or process described herein.

Example 71 may include a method, technique, or process as described in or related to any of examples 1-67, or portions or parts thereof.

Example 72 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-67, or portions thereof.

Example 73 may include a signal as described in or related to any of examples 1-67, or portions or parts thereof.

Example 74 may include a datagram, packet, frame, segment, PDU, or message as described in or related to any of examples 1-67, or portions or parts thereof, or otherwise described in the present disclosure.

Example 75 may include a signal encoded with data as described in or related to any of examples 1-67, or portions or parts thereof, or otherwise described in the present disclosure.

Example 76 may include a signal encoded with a datagram, packet, frame, segment, PDU, or message as described in or related to any of examples 1-67, or portions or parts thereof, or otherwise described in the present disclosure. Example 77 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-67, or portions thereof.

Example 78 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-67, or portions thereof.

Example 79 may include a signal in a wireless network as shown and described herein.

Example 80 may include a method of communicating in a wireless network as shown and described herein.

Example 81 may include a system for providing wireless communication as shown and described herein.

Example 82 may include a device for providing wireless communication as shown and described herein.

Any of the above-described examples may be combined with any other example (or combination of examples), unless explicitly stated otherwise. The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.

For the purposes of the present document, the following terms and definitions are applicable to the examples and embodiments discussed herein.

The term “circuitry” as used herein 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 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), DSPs, etc., that are configured to provide the described functionality. In some embodiments, 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. The term “processor circuitry” as used herein 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. The term “processor circuitry” may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a singlecore processor, a dual-core processor, a triple-core processor, a quad-core processor, and/or any other device capable of executing or otherwise operating computer-executable 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. The terms “application circuitry” and/or “baseband circuitry” may be considered synonymous to, and may be referred to as, “processor circuitry.”

The term “interface circuitry” as used herein refers to, is part of, or includes circuitry that enables the exchange of information between two or more components or devices. The term “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. The term “user equipment” or “UE” as used herein 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. Furthermore, the term “user equipment” or “UE” may include any type of wireless/wired device or any computing device including a wireless communications interface.

The term “network element” as used herein refers to physical or virtualized equipment and/or infrastructure used to provide wired or wireless communication network services. The term “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.

The term “computer system” as used herein 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.

The term “appliance,” “computer appliance,” or the like, as used herein 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. 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.

The term “resource” as used herein 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. The term “network resource” or “communication resource” may refer to resources that are accessible by computer devices/systems via a communications network. The term “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.

The term “channel” as used herein refers to any transmission medium, either tangible or intangible, which is used to communicate data or a data stream. The term “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. Additionally, the term “link” as used herein refers to a connection between two devices through a RAT for the purpose of transmitting and receiving information.

The terms “instantiate,” “instantiation,” and the like as used herein 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. The terms “coupled,” “communicatively coupled,” along with derivatives thereof are used herein. The term “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. The term “directly coupled” may mean that two or more elements are in direct contact with one another. The term “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.

The term “information element” refers to a structural element containing one or more fields. The term “field” refers to individual contents of an information element, or a data element that contains content.

The term “SMTC” refers to an SSB-based measurement timing configuration configured by SSB-MeasurementTimingConfiguration.

The term “SSB” refers to an SS/PBCH block.

The term “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.

The term “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.

The term “Secondary Cell” refers to a cell providing additional radio resources on top of a Special Cell for a UE configured with CA.

The term “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.

The term “serving cell” or “serving cells” refers to the set of cells comprising the Special Cell(s) and all secondary cells for a UE in RRC_CONNECTED configured with CA/.

The term “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.

Claims

1. A user equipment (UE) comprising: one or more processors; and one or more non-transitory computer-readable media comprising instructions that, upon execution of the instructions by the one or more processors, are to cause the one or more processors to: identify a received downlink control information (DCI) to schedule transmission of multiple code block bundles (CBBs), wherein the DCI indicates a new data indicator (NDI) for respective ones of the multiple CBBs; and facilitate transmission or reception of one or more of the CBBs based on the DCI.

2. The UE of claim 1, wherein the multiple CBBs include a downlink CBB and an uplink CBB.

3. The UE of claim 1, wherein the DCI indicates a start hybrid automatic repeat request (HARQ) process number (HPN) for a first CBB of the multiple CBBs.

4. The UE of claim 1, wherein the instructions are further to cause the one or more processors to identify received configuration information that indicates a number of NDI bits that includes the NDIs for the respective ones of the multiple CBBs.

5. The UE of any of claims 1-4, wherein the NDIs for the respective ones of the multiple CBBs are individual bits.

6. The UE of any of claims 1-4, wherein respective NDIs for the respective ones of the multiple CBBs include a toggling bit and an absolute bit.

7. The UE of claim 6, wherein the toggling bit is to indicate whether the DCI schedules a new transmission or a retransmission for the associated HARQ process based on whether a value of the toggling bit is toggled, and wherein the absolute bit is to indicate whether the DCI schedules a new transmission or a retransmission for the associated HARQ process based on a direct value of the absolute bit.

34

8. The UE of any of claims 1-4, wherein the DCI further includes a redundancy version (RV) indicator for respective CBBs of the multiple CBBs.

9. The UE of any of claims 1-4, wherein the DCI further includes a redundancy version (RV) indicator that applies to all new transmissions scheduled by the DCI, or an RV indicator that applies to all retransmissions scheduled by the DCI.

10. The UE of any of claims 1-4, wherein the DCI includes an index that indicates a bit sequence that corresponds to the NDIs for the respective ones of the multiple CBBs, wherein the bit sequence is based on an nchoosek() function or a combinatorial index.

11. A base station comprising: one or more processors; and one or more non-transitory computer-readable media comprising instructions that, upon execution of the instructions by the one or more processors, are to cause the one or more processors to: facilitate transmission of a downlink control information (DCI) to a user equipment (UE), the DCI to schedule transmission of multiple code block bundles (CBBs), wherein the DCI indicates a new data indicator (NDI) for respective ones of the CBBs; and facilitate transmission or reception of the multiple CBBs based on the DCI.

12. The base station of claim 11, wherein the multiple CBBs include a downlink CBB and an uplink CBB.

13. The base station of claim 11, wherein the DCI indicates a start hybrid automatic repeat request (HARQ) process number (HPN) for a first CBB of the multiple CBBs.

14. The base station of claim 11, wherein the instructions are further to facilitate transmission of configuration information to the UE, the configuration information to indicate a number of NDI bits that includes the NDIs for the respective ones of the CBBs.

15. The base station claim 11, wherein the NDIs for the respective ones of the CBBs are individual bits.

35

16. The base station claim 11, wherein respective NDIs include a toggling bit and an absolute bit.

17. The base station of claim 11, wherein the DCI further includes a redundancy version (RV) indicator for each CBB of the multiple CBBs.

18. The base station of claim 11, wherein the DCI further includes a redundancy version (RV) indicator that applies to all new transmissions scheduled by the DCI or all retransmissions scheduled by the DCI.

19. The base station of claim 11, wherein the DCI includes an index that indicates a bit sequence that corresponds to the NDIs, wherein the bit sequence is based on an nchoosekQ function or a combinatorial index.

20. The base station of any of claims 11-19, wherein the CBBs are scheduled for transmission on a frequency of greater than 52.6 gigahertz (GHz).