System information block and ultra-compact downlink control information design for non-terrestrial network enhancements

Abstract

Systems and methods for using ultra-compact downlink control information (DCI) in conjunction with one or more scheduled physical downlink shared channels (PDSCHs) are disclosed herein. A base station may transmit, to a user equipment (UE), an ultra-compact DCI that schedules one or more scheduled PDSCHs. The one or more scheduled PDSCHs may schedule a data PDSCH or a physical uplink shared channel (PUSCH) to be used for user / application layer data transmissions. The ultra-compact DCI and / or one or more scheduled PDSCHs may be configured by a system information block (SIB). The ultra compact DCI and / or the one or more scheduled PDSCHs may schedule a physical uplink control channel (PUCCH) for hybrid automatic repeat request acknowledgement (HARQ-ACK) signaling with respect to the one or more scheduled PDSCHs. Aspects related to using these systems and methods in non-terrestrial network (NTN) environments are contemplated.

Description

Technical Field

[0001] The present application as a whole relates to wireless communication systems, including wireless communication systems that use ultra-compact DCI and / or one or more scheduled physical downlink shared channels (PDSCH) for scheduling PDSCH and / or scheduled physical uplink shared channels (PUSCH) for data transmission (e.g., user / application data transmission). Background Art

[0002] Wireless mobile communication technologies use various standards and protocols to send data between base stations and wireless communication devices. Wireless communication system standards and protocols may include, for example, the 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) (e.g., 4G), 3GPP New Radio (NR) (e.g., 5G), and the IEEE 802.11 standard for wireless local area networks (WLANs) (commonly referred to within industry organizations as WLANs). ).

[0003] As envisioned by 3GPP, different wireless communication system standards and protocols may use various radio access networks (RANs) to communicate between base stations of the RAN (which may also sometimes be referred to as RAN nodes, network nodes, or simply nodes) and wireless communication devices referred to as user equipment (UE). 3GPP RANs may include, for example, Global System for Mobile Communications (GSM), Enhanced Data Rates for GSM Evolution (EDGE) RAN (GERAN), Universal Terrestrial Radio Access Network (UTRAN), Evolved Universal Terrestrial Radio Access Network (E-UTRAN), and / or Next Generation Radio Access Network (NG-RAN).

[0004] Each RAN may use one or more radio access technologies (RATs) for communication between base stations and UEs. For example, GERAN implements GSM and / or EDGE RAT, UTRAN implements Universal Mobile Telecommunications System (UMTS) RAT or other 3GPP RAT, E-UTRAN implements LTE RAT (sometimes referred to as LTE), and NG-RAN implements NR RAT (sometimes referred to as 5G RAT, 5G NR RAT, or NR in this document). In some deployments, E-UTRAN may also implement NR RAT. In some deployments, NG-RAN may also implement LTE RAT.

[0005] The base stations used by the RAN may correspond to the RAN. An example of an E-UTRAN base station is an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (also commonly denoted as an evolved Node B, enhanced Node B, eNodeB, or eNB). An example of an NG-RAN base station is a Next Generation Node B (sometimes also referred to as a gNodeB or gNB).

[0006] The RAN provides communication services together with external entities through its connection with the Core Network (CN). For example, E-UTRAN may utilize the Evolved Packet Core Network (EPC), while NG-RAN may utilize the 5G Core Network (5GC). BRIEF DESCRIPTION OF THE DRAWINGS

[0007] To easily identify the discussion of any particular element or act, the most significant digit(s) in a reference number refers to the drawing number that first introduces the element.

[0008] Figure 1 An NTN architecture of a wireless communication system according to an embodiment is illustrated.

[0009] Figure 2 An NTN architecture of a wireless communication system according to an embodiment is illustrated.

[0010] Figure 3 A schematic diagram illustrating a dynamic resource grant process for DL ​​data transmission according to an embodiment is illustrated.

[0011] Figure 4 A schematic diagram illustrating a dynamic resource grant process for UL data transmission according to an embodiment is illustrated.

[0012] Figure 5 A schematic diagram illustrating a dynamic resource grant process for DL ​​data transmission using ultra-compact DCI and one or more scheduled PDSCHs according to an embodiment is illustrated.

[0013] Figure 6 A schematic diagram illustrating a dynamic resource grant process for DL ​​data transmission using ultra-compact DCI and one or more scheduled PDSCHs according to an embodiment is illustrated.

[0014] Figure 7 A diagram illustrating a dynamic resource grant process for UL data transmission using ultra-compact DCI and one or more scheduled PDSCHs according to an embodiment is illustrated.

[0015] Figure 8 A diagram illustrating a dynamic resource grant process for UL data transmission using ultra-compact DCI and one or more scheduled PDSCHs according to an embodiment is illustrated.

[0016] Fig. 9 A method of a UE according to an implementation scheme is illustrated.

[0017] Fig.10 A method of a base station according to an embodiment is illustrated.

[0018] Fig.11A schematic diagram illustrating a dynamic resource grant process for DL ​​data transmission according to an embodiment is illustrated.

[0019] Fig.12 A method of a UE according to an implementation scheme is illustrated.

[0020] Fig.13 A method of a base station according to an embodiment is illustrated.

[0021] Fig.14 A method of a UE according to an implementation scheme is illustrated.

[0022] Fig.15 A method of a base station according to an embodiment is illustrated.

[0023] Fig.16 An example architecture of a wireless communication system according to embodiments disclosed herein is illustrated.

[0024] Fig.17 A system for performing signaling between a wireless device and a RAN device connected to a core network of a CN device according to an embodiment disclosed herein is illustrated. DETAILED DESCRIPTION

[0025] The various embodiments are described with respect to a UE. However, reference to a UE is provided for illustrative purposes only. The example embodiments may be used with any electronic component that can establish a connection with a network and is configured with hardware, software, and / or firmware for exchanging information and data with the network. Therefore, a UE as described herein is used to represent any suitable electronic component.

[0026] Figure 1 A non-terrestrial network (NTN) architecture 100 of a wireless communication system according to an embodiment is illustrated. The NTN architecture 100 includes a core network (CN) 102, a ground base station 104, a satellite gateway 106, a satellite 108, and a UE 110. The ground base station 104, the satellite gateway 106, and the satellite 108 may be included in a RAN 112.

[0027] In some embodiments, RAN 112 comprises E-UTRAN, CN 102 comprises EPC, and ground base station 104 comprises eNB. In these cases, CN link 114 connecting CN 102 and ground base station 104 may comprise an S1 interface.

[0028] In some embodiments, RAN 112 includes NG-RAN, CN 102 includes 5GC, and ground base station 104 includes gNB or next generation eNB (ng-eNB). In such a case, the CN link 114 connecting CN 102 and ground base station 104 may include an NG interface.

[0029] The NTN architecture 100 illustrates an architecture based on a "bent pipe" or "transparent" satellite. In such a bent pipe system, a ground base station 104 communicates with a satellite 108 via a feeder link 116 using a satellite gateway 106. The satellite 108 may be equipped with one or more antennas capable of broadcasting a cell according to the RAN 112, and the UE 110 may be equipped with one or more antennas (e.g., a mobile parabolic antenna, an omnidirectional phased array antenna, etc.) capable of communicating with the satellite 108 via a Uu interface on the cell (such communication may be said to use the service link 118 shown). The payload disposed on the satellite 108 then transparently forwards data between the satellite gateway 106 and the UE 110 using the feeder link 116 between the satellite gateway 106 and the satellite 108 and the service link 118 between the satellite 108 and the UE 110. The payload may perform RF conversion and / or amplification in both the uplink (UL) and the downlink (DL) to enable this communication.

[0030] exist Figure 1 In the illustrated embodiment, the ground base station 104 is shown without the capability of directly conducting ground wireless communication with the UE. However, it is contemplated that in other embodiments, such a ground base station that communicates with the satellite 108 using the satellite gateway 106 may (also) have this functionality (i.e., as will be described below). Fig.16 of ground base station 1612 and ground base station 1614).

[0031] Figure 2 The NTN architecture 200 of a wireless communication system according to an embodiment is illustrated. The NTN architecture 200 includes a CN 202, a satellite gateway 204, a satellite base station 206, and a UE 208. The satellite gateway 204 and the satellite base station 206 may be included in a RAN 210.

[0032] In some embodiments, RAN 210 comprises E-UTRAN and CN 202 comprises EPC. In these cases, CN link 212 connecting CN 202 and satellite gateway 204 may comprise an S1 interface.

[0033] In some embodiments, RAN 210 includes NG-RAN and CN 202 includes 5GC. In such a case, CN link 212 connecting CN 202 and satellite gateway 204 may include an NG interface.

[0034] The NTN architecture 200 implements a "regenerative" satellite-based architecture. In such a regenerative system, the functions of a base station are located on a satellite base station 206, and communications between these base station functions and the CN 202 occur via a satellite gateway 204 and a feeder link 214 forwarded to the satellite base station 206 via an interface found on a CN link 212 (e.g., an S1 interface and / or an NG interface). The satellite base station 206 may be equipped with one or more antennas capable of broadcasting a cell in accordance with the RAN 210, and the UE 208 may be equipped with one or more antennas (e.g., a mobile parabolic antenna, an omnidirectional phased array antenna, etc.) capable of communicating with the satellite base station 206 via a Uu interface on the cell (such communications may be said to use the service link 216 shown). The payload located on the satellite base station 206 then forwards data between the satellite gateway 204 and the satellite base station 206 using the feeder link 214 between the satellite gateway 204 and the satellite base station 206 and the service link 216 between the satellite base station 206 and the UE 208. The payload may perform RF conversion and / or amplification in both the uplink (UL) and downlink (DL) to enable this communication, as well as implement the functionality of a base station (e.g., such as an eNB, ng-eNB, or gNB, such as a type corresponding to RAN 210) as those already provided at satellite base station 206.

[0035] In an embodiment of the NTN architecture including an NG-RAN that also uses integrated access and backhaul (IAB), it is possible that a gNB control unit function (CU) may be located on the ground and may communicate with a satellite carrying a corresponding gNB donor unit function (DU) using a satellite gateway, wherein the F1 interface between the CU and DU is supported by the feeder link 214. In such a case, the CU and DU may each be understood as part of the NG-RAN.

[0036] The characteristic differences of NTN relative to terrestrial networks may include relatively large propagation delays and the possibility that the satellite moves relative to the current position of the UE. Therefore, improvements to wireless communication systems may be intended to help mitigate the undesirable effects caused by these situations. Given the real-world characteristics of NTN performance (e.g., as opposed to idealized situations), such improvements may respond to the need to improve the various services (e.g., voice services, data services) provided by the NTN to the UE. Such improvements to the use of NTN may be arranged to take into account relevant regulatory restrictions, such as (for example) restrictions on power flux density (PFD) at the ground / ground level established by the International Telecommunication Union (ITU). It should be understood that in some cases, such improvements may be achieved (at least in part) by specific use of one or more physical radio channels in a manner that helps alleviate these and other NTN-related issues.

[0037] In some cases, a pairing of the L-band (e.g., 1610 megahertz (MHz) to 1618.775 MHz) and the S-band (e.g., 2483.5 MHz to 2500 MHz) may be considered. For example, it is possible that the L-band may be used for UL between a satellite and a UE, while the S-band may be used for DL ​​between a satellite and a UE.

[0038] Depending on various regulations, PFD restrictions on the use of this S-band may apply. For example, in a mobile satellite service environment in the range 2483.5 MHz to 2500 MHz, the PFD restrictions may be calculated using the PFD calculation factor P (in dB(W / m 2 ) per MHz or X kilohertz (kHz)) and r (expressed in dB / degree). The values ​​of these PFD calculation factors may depend on whether the satellite is a GSO or non-GSO satellite. Appropriate values ​​of the PFD calculation factors may be applied in a defined manner relative to the angle of arrival above the horizontal plane (relative to a location on the Earth's surface) δ (in degrees) to achieve the PFD limit.

[0039] For example, a satellite in geostationary orbit (GSO) may correspond to a PFD calculation factor of P = -146 dB (W / m 2 )(4kHz) or -128dB(W / m 2 )(1MHz), and r = 0.5dB / degree, while a satellite in a non-GSO may correspond to a parameter P = -144dB(W / m 2 )(4kHz) or -126dB(W / m 2 )(1MHz), and r = 0.65dB / degree. In some areas, satellites in non-GSO may instead use P = -142.5dB (W / m 2 ), and uses -124.5dB(W / m 2 ).

[0040] Then, using the appropriate PFD calculation factors P and r based on the applicable satellite information, the PFD limit relative to the satellite can be calculated based on the applicable delta between the UE location and the satellite using the following equation:

[0041] PFD = P, for 0°≤δ≤5°;

[0042] PFD = P + r(δ-5), for 5°≤δ≤25°; and

[0043] PFD=P+20r, for 25°≤δ≤90°.

[0044] Within such calculated PFD constraints, it is possible that the DL transmit power (or effective isotropically radiated power (EIRP)) in the range of 2483.5 MHz to 2500 MHz is insufficient to cover the entire geographic cell of the satellite with strong coverage.

[0045] Thus, use of the embodiments described herein may, for example, enhance the DL coverage experienced by a UE within a satellite cell, when the circumstances described herein are applicable.

[0046] Figure 3 A diagram 300 is illustrated of a dynamic resource grant process for DL ​​data transmission according to an embodiment. The diagram 300 illustrates sending downlink control information (DCI) 302 from a base station to a UE. The DCI 302 may be carried in a physical downlink control channel (PDCCH). The DCI 302 may be, for example, DCI format 1_0, 1_1, or 1_2.

[0047] The DCI 302 may indicate to the UE that the network has allocated a PDSCH 304 with DL data resources for the UE (e.g., the network has scheduled the use of the PDSCH 304 for the UE), and may further indicate to the UE the time and frequency location of the PDSCH 304. As shown, a minimum offset K0 308 between the DCI 302 that schedules the PDSCH 304 and the PDSCH 304 itself may be maintained by the network.

[0048] The DCI 302 may also indicate to the UE that the network has allocated PUCCH 306 for use by the UE for any hybrid automatic repeat request acknowledgement (HARQ-ACK) signaling related to the UE's reception and attempted decoding of PDSCH 304 (e.g., the network has scheduled the UE's use of PUCCH 306). As shown, a minimum offset K1 310 between PDSCH 304 and PUCCH 306 may be maintained by the network.

[0049] The UE may therefore attempt to receive and decode the PDSCH 304 at the time / frequency resources indicated for the PDSCH 304 in the DCI 302. The UE may then send HARQ-ACK signaling corresponding to the result on the PUCCH 306. For example, if the UE's reception and decoding of the PDSCH 304 is successful, the HARQ-ACK signaling on the PUCCH 306 may include an acknowledgement (ACK). If the reception and / or decoding of the PDSCH 304 is unsuccessful, the HARQ-ACK signaling on the PUCCH 306 may instead include a negative acknowledgement (NACK).

[0050] Figure 4A diagram 400 is illustrated of a dynamic resource grant process for UL data transmission according to an embodiment. The diagram 400 illustrates sending DCI 402 from a base station to a UE. The DCI 402 may be carried in a PDCCH. The DCI 402 may be, for example, DCI format 0_0, 0_1, or 0_2.

[0051] The DCI 402 may indicate to the UE that the network has allocated a PUSCH 404 for the UE to use to send UL data (e.g., the network has scheduled the use of the PUSCH 404 for the UE), and may further indicate to the UE the time and frequency location of the PUSCH 404. As shown, a minimum offset K2 406 between the DCI 402 that schedules the PUSCH 404 and the PUSCH 404 itself may be maintained by the network.

[0052] Therefore, the UE may send data on the PUSCH 404 at the time / frequency resources indicated for the PUSCH 404 in the DCI 402 .

[0053] Figure 3 and Figure 4 The process of can be successfully used in some situations (e.g., situations involving all-terrestrial networks), where aspects of the behavior and / or relationship between the base station and the UE can be implicitly assumed in those scenarios. However, it has been recognized that in various situations, the Figure 3 and Figure 4 As shown in (and about Figure 3 and Figure 4 Modifications of the process described may be beneficial.

[0054] For example, to address NTN related issues of additional signaling propagation time and / or distance and / or PFD limitations, it has been determined that PDSCH coverage provided by satellites of NTNs may be improved by using a (relatively large number of) PDSCH repetitions.

[0055] Further, it has been recognized that in an NTN environment, PDCCH transmission (e.g., as described herein, for DCI) may represent a bottleneck in various situations. For example, in the case where repeated PDCCHs are not configured for use in an NTN network, a (respectively, single) PDCCH may be more likely to be lost in an NTN context than in another context (e.g., compared to an all-terrestrial context). Further, in some situations (e.g., due to the relatively increased signaling propagation time of the PDCCH in the NTN context), the use of PDCCH repetition in the NTN context (in an attempt to reduce the chance of complete loss of PDCCH signaling) may have a disproportionately large negative impact on the overall network throughput.

[0056] Therefore, it has been recognized that by simplifying the use of DCI, the impact of these PDCCH related aspects can be reduced.DCI constructed and / or used according to such simplified usage may be referred to herein as "ultra-compact DCI".

[0057] In some embodiments, such simplification may be achieved via the use of a DCI format for ultra-compact DCI, which results in an overall reduction in the payload size of the ultra-compact DCI compared to the payload size of DCI according to other DCI formats under the same parameters / environment. In some embodiments, this may be achieved by omitting one or more fields from the ultra-compact DCI that would otherwise appear in DCI of other DCI formats. In some wireless communication networks, such as those implementing LTE RAT and / or NR RAT, it may be possible that such ultra-compact DCI may therefore have a reduced payload size compared to "compact DCI" known to those networks (e.g., DCI of formats 1_2 and / or 0_2).

[0058] In some embodiments, such simplification may (alternatively or additionally) be achieved by using fixed values ​​for one or more fields within the ultra-compact DCI (which may help speed up and / or simplify decoding of the ultra-compact DCI at the UE). In some of these embodiments, it may be that the payload size of the ultra-compact DCI may therefore not necessarily be smaller than the payload size of a DCI of another DCI format known / used in the relevant wireless communication system.

[0059] It should be noted that in some embodiments, the DCI format of the ultra-compact DCI may define fields beyond those provided by other DCI formats known / defined in the wireless communication system. Thus, in a subset of these embodiments, the ultra-compact DCI may have a larger payload size (due to these additional fields) than the payload size of a DCI of another DCI format known / used in the relevant wireless communication system.

[0060] Further, the embodiments of the present invention may provide at least some scheduling information of the PDSCH or PUSCH for data transmission in one or more intervening PDSCHs that appear between the ultra-compact DCI and the PDSCH / PUSCH for data transmission (rather than placing the information within the ultra-compact DCI). These one or more intervening PDSCHs may be referred to herein as "scheduling PDSCHs". By using one or more such scheduling PDSCHs to transmit scheduling information of the PDSCH / PUSCH for data transmission between the base station and the UE, the payload size of the ultra-compact DCI may be reduced accordingly. In the present invention, the PDSCH for data transmission may be referred to as a "data PDSCH" to distinguish it from any scheduling PDSCH under discussion.

[0061] As will be described, in some embodiments, the ultra-compact DCI and / or the scheduled PDSCH may further include scheduling information for a PUCCH, which may be used by the UE to provide HARQ-ACK signaling to the base station relative to the scheduled PDSCH. In some embodiments, the PUCCH appears between the scheduled PDSCH and the data PDSCH / PUSCH for data transmission. In some embodiments, the PUCCH may appear after the scheduled PDSCH and the data PDSCH / PUSCH for data transmission.

[0062] Finally, it is possible that one or more scheduled PDSCHs include PDSCH repetitions (even in cases where, for example, PDCCH repetitions for ultra-compact DCI are not available and / or are not used), thereby increasing the chances of successfully receiving and decoding the accompanying scheduling information for the HARQ data PDSCH / PUSCH / PUCCH at the UE (as the case may be).

[0063] Figure 5 A diagram 500 is illustrated illustrating a dynamic resource grant process for DL ​​data transmission using ultra-compact DCI and one or more scheduling PDSCHs according to an embodiment. More specifically, the diagram 500 illustrates scheduling a data PDSCH 506 for DL ​​data transmission using an ultra-compact DCI 502 and one or more scheduling PDSCHs 504.

[0064] Diagram 500 illustrates that ultra-compact DCI 502 is sent by a base station and received at a UE. Ultra-compact DCI 502 provides sufficient information to the UE so that the UE knows the time and frequency location of one or more scheduled PDSCHs 504 (eg, ultra-compact DCI 502 schedules one or more scheduled PDSCHs 504).

[0065] The one or more scheduled PDSCHs 504 are then sent by the base station as scheduled and received at the UE. The one or more scheduled PDSCHs 504 may include one or more medium access control elements (MAC CEs) that include scheduling information for the data PDSCH 506. The one or more scheduled PDSCHs 504 thus provide sufficient information to the UE (e.g., in the MAC CE) so that the UE knows the time and frequency location of the data PDSCH 506 (e.g., the one or more scheduled PDSCHs 504 schedule the data PDSCH 506).

[0066] In some embodiments, one or more scheduling PDSCHs 504 include PDSCH repetitions. For example, in the case where one or more scheduling PDSCHs 504 include at least two PDSCHs, each of the two PDSCHs may be identical. In such a case, each of the one or more scheduling PDSCHs 504 will have, for example, the same MAC CE with scheduling information of the data PDSCH 506. Such repeated use may provide the UE with additional reception opportunities for the data, thereby increasing the probability that the UE successfully receives and / or decodes the data.

[0067] The data PDSCH 506 is then scheduled to be sent by the base station and received at the UE. The data PDSCH 506 may include, for example, user plane (UP) data (eg, application layer data of an application running on the UE).

[0068] As shown, a minimum offset K3 508 between the last of the one or more scheduled PDSCHs 504 and the data PDSCH 506 can be maintained by the network. In other words, the ultra-compact DCI 502 can schedule one or more scheduled PDSCHs 504, and one or more scheduled PDSCHs 504 can schedule the data PDSCH 506, thereby maintaining the minimum offset K3 508.

[0069] The base station may transmit a system information block (SIB) that includes configuration information for the ultra-compact DCI 502 and / or one or more scheduled PDSCHs 504. The configuration information for the ultra-compact DCI 502 found in the SIB may be used by the UE to locate the ultra-compact DCI 502.

[0070] Further, the configuration information of the one or more scheduled PDSCHs 504 found in the SIB may be further used to locate the one or more scheduled PDSCHs 504 (in other words, the ultra-compact DCI 502 may schedule the one or more scheduled PDSCHs 504 based on / with the background assumption of any configuration of the one or more scheduled PDSCHs 504 provided in the SIB). In some cases, the configuration information for the one or more scheduled PDSCHs 504 in the SIB may correlate the time and / or frequency location of any one of the one or more scheduled PDSCHs 504 relative to the received ultra-compact DCI 502.

[0071] The SIB can be Figure 5 The base station of the dynamic resource grant process (eg, sending an ultra-compact DCI 502) sends Figure 5 Alternatively, the SIB may be sent by another base station to the UE of the dynamic resource grant process. Figure 5 UE.

[0072] In some cases, after receiving the data PDSCH 506, the UE may reply to the base station with HARQ-ACK signaling on the PUCCH ( Figure 5 (not shown in FIG. 1 ). For example, if the UE successfully receives and decodes the data PDSCH 506, the HARQ-ACK signaling may include an ACK. If the UE successfully receives and / or decodes the data PDSCH 506, the HARQ-ACK signaling may include a NACK instead.

[0073] Figure 6 A diagram 600 is shown illustrating a dynamic resource grant process for DL ​​data transmission using ultra-compact DCI and one or more scheduled PDSCHs according to an embodiment. Figure 5 Thus, diagram 600 illustrates the use of ultra-compact DCI 502, one or more scheduling PDSCHs 504, data PDSCHs 506, and offset K3 508, as described with respect to FIG. Figure 5 As described in the schematic diagram 500. In addition to Figure 5 In addition to these elements of the schematic diagram 500, Figure 6 Schematic diagram 600 additionally illustrates the scheduling and use of PUCCH 602 with HARQ-ACK signaling.

[0074] The PUCCH 602 may be used to provide HARQ-ACK signaling from the UE to the base station, which indicates whether the UE is able to receive and decode the information provided by one or more scheduling PDSCHs 504. If the UE's reception and decoding of the scheduling information of the data PDSCH 506 from the one or more scheduling PDSCHs 504 is successful, the HARQ-ACK signaling in the PUCCH 602 may include an ACK. If the UE's reception and / or decoding of the scheduling information of the data PDSCH 506 from the one or more scheduling PDSCHs 504 is unsuccessful, the HARQ-ACK signaling in the PUCCH 602 may instead include a NACK. In the case of a NACK (or in the case that any expected PUCCH 602 does not arrive at the base station at all), the base station may determine that the UE cannot use the data PDSCH 506 under any circumstances, and may cancel its transmission of the data PDSCH 506 accordingly in order to save network resources.

[0075] like Figure 6 As shown in schematic diagram 600, the ultra-compact DCI 502 and any one of the one or more scheduled PDSCHs 504 (or any combination of any of these) provide sufficient information to the UE so that the UE knows the time and frequency location of the PUCCH 602 (e.g., some / all of the scheduled PUCCHs 602 in the ultra-compact DCI 502 and / or one or more scheduled PDSCHs 504).

[0076] Alternatively (or additionally), the SIB received at the UE may provide configuration information for the PUCCH 602, including (but not limited to) providing information about the time and / or frequency location of the PUCCH 602. In such a case, the configuration information for the PUCCH 602 in the SIB may correlate the time and / or frequency location of the PUCCH 602 relative to any of the received ultra-compact DCI 502 and / or one or more scheduling PDSCHs 504.

[0077] Figure 6 Schematic diagram 600 illustrates a PUCCH 602 between one or more scheduling PDSCHs 504 and a data PDSCH 506. It should be noted that in alternative embodiments, the PUCCH 602 described herein may be located after the data PDSCH 506 instead.

[0078] Figure 7A diagram 700 illustrates a dynamic resource grant process for UL data transmission using ultra-compact DCI and one or more scheduled PDSCHs according to an embodiment. More specifically, the diagram 700 illustrates the use of ultra-compact DCI 702 and one or more scheduled PDSCHs 704 to schedule a PUSCH 706 for UL data transmission.

[0079] Diagram 700 illustrates that ultra-compact DCI 702 is sent by a base station and received at a UE. Ultra-compact DCI 702 provides sufficient information to the UE so that the UE knows the time and frequency location of one or more scheduled PDSCHs 704 (eg, ultra-compact DCI 702 schedules one or more scheduled PDSCHs 704).

[0080] The one or more scheduled PDSCHs 704 are then sent by the base station as scheduled and received at the UE. The one or more scheduled PDSCHs 704 may include one or more medium access control elements (MAC CEs) that include scheduling information for the PUSCH 706. The one or more scheduled PDSCHs 704 thus provide sufficient information to the UE (e.g., in the MAC CE) so that the UE knows the time and frequency location of the PUSCH 706 (e.g., the one or more scheduled PDSCHs 704 schedule the PUSCH 706).

[0081] In some embodiments, one or more scheduled PDSCHs 704 include PDSCH repetitions. For example, in the case where one or more scheduled PDSCHs 704 include at least two PDSCHs, each of the two PDSCHs may be identical. In such a case, each of the one or more scheduled PDSCHs 704 will have, for example, the same MAC CE with scheduling information of the PUSCH 706. Such repeated use may provide the UE with additional reception opportunities for the data, thereby increasing the probability that the UE successfully receives and / or decodes the data.

[0082] The PUSCH 706 is then scheduled to be transmitted by the UE. The PUSCH 706 may include, for example, user plane (UP) data (eg, application layer data of applications running on the UE).

[0083] As shown, a minimum offset K4 708 between the last of one or more scheduled PDSCHs 704 and PUSCH 706 may be maintained by the network. In other words, ultra-compact DCI 702 may schedule one or more scheduled PDSCHs 704, and one or more scheduled PDSCHs 704 may schedule PUSCH 706, thereby maintaining the minimum offset K4 708.

[0084] The base station may transmit a system information block (SIB) that includes configuration information for the ultra-compact DCI 702 and / or one or more scheduled PDSCHs 704. The configuration information for the ultra-compact DCI 702 found in the SIB may be used by the UE to locate the ultra-compact DCI 702.

[0085] Further, the configuration information of the one or more scheduled PDSCHs 704 found in the SIB may be further used to locate the one or more scheduled PDSCHs 704 (in other words, the ultra-compact DCI 702 may schedule the one or more scheduled PDSCHs 704 based on / with the background assumption of any configuration of the one or more scheduled PDSCHs 704 provided in the SIB). In some cases, the configuration information for the one or more scheduled PDSCHs 704 in the SIB may correlate the time and / or frequency location of any one of the one or more scheduled PDSCHs 704 relative to the received ultra-compact DCI 702.

[0086] The SIB can be Figure 7 The base station of the dynamic resource grant process (eg, sending an ultra-compact DCI 702) sends Figure 7 Alternatively, the SIB may be sent by another base station to the UE of the dynamic resource grant process. Figure 7 UE.

[0087] Figure 8 A diagram 800 is shown illustrating a dynamic resource grant process for UL data transmission using ultra-compact DCI and one or more scheduled PDSCHs according to an embodiment. Figure 7 Thus, diagram 800 illustrates the use of ultra-compact DCI 702, one or more scheduled PDSCHs 704, PUSCH 706, and offset K4 708, as described with respect to FIG. Figure 7 700 as described. In addition to Figure 7 In addition to these elements of the schematic diagram 700, Figure 8 Schematic diagram 800 additionally illustrates the scheduling and use of PUCCH 802 with HARQ-ACK signaling.

[0088] The PUCCH 802 may be used to provide HARQ-ACK signaling from the UE to the base station, which indicates whether the UE is able to receive and decode the information provided by one or more scheduled PDSCHs 704. If the UE's reception and decoding of the scheduling information of the PUSCH 706 from the one or more scheduled PDSCHs 704 is successful, the HARQ-ACK signaling in the PUCCH 802 may include an ACK. If the UE's reception and / or decoding of the scheduling information of the PUSCH 706 from the one or more scheduled PDSCHs 704 is unsuccessful, the HARQ-ACK signaling in the PUCCH 802 may instead include a NACK. In the case of a NACK (or in the case that any expected PUCCH 802 does not arrive at the base station at all), the base station may determine that the UE cannot use the PUSCH 706 under any circumstances, and may cancel its scheduled reception attempt for the PUSCH 706 accordingly in order to save network resources.

[0089] like Figure 8 As shown in schematic diagram 800, the ultra-compact DCI 702 and any one of the one or more scheduled PDSCHs 704 (or any combination of any of these) provide sufficient information to the UE so that the UE knows the time and frequency location of the PUCCH 802 (e.g., some / all of the scheduled PUCCH 802 in the ultra-compact DCI 702 and / or one or more scheduled PDSCHs 704).

[0090] Alternatively (or additionally), the SIB received at the UE may provide configuration information for the PUCCH 802, including (but not limited to) providing information about the time and / or frequency location of the PUCCH 802. In such a case, the configuration information for the PUCCH 802 in the SIB may correlate the time and / or frequency location of the PUCCH 802 relative to any of the received ultra-compact DCI 702 and / or one or more scheduling PDSCHs 704.

[0091] Figure 8 Schematic diagram 800 illustrates one or more PUCCHs 802 scheduled between PDSCH 704 and PUSCH 706. It should be noted that in alternative embodiments, the PUCCH 802 described herein may be located after the PUSCH 706 instead.

[0092] SIB Design

[0093] Now discuss the SIB with ultra-compact DCI and / or configuration information for one or more scheduled PDSCHs. As described herein, the SIB may be received at a UE prior to receiving and / or decoding, for example, ultra-compact DCI and / or one or more PDSCHs (eg, corresponding to configuration information in the SIB).

[0094] Various formats of SIBs with configuration information for ultra-compact DCI and / or one or more scheduled PDSCHs are contemplated. In some embodiments, it is possible to use SIB1 as understood in the definition of some wireless communication systems to transmit configuration information for ultra-compact DCI and / or one or more scheduled PDSCHs. In some embodiments, an NTN-specific SIB format may be used to transmit configuration information for ultra-compact DCI and / or one or more scheduled PDSCHs. In the definition of certain types of wireless communication systems, such an NTN-specific SIB format may be designated as SIBx. In some embodiments, a new SIB format (e.g., different from SIB1 or SIBx and new in the wireless communication system) may be used.

[0095] The SIB with configuration information for ultra-compact DCI and / or one or more scheduled PDSCHs may be used for either the UL transmission case or the DL transmission case as described herein.

[0096] The SIB may include an indication of whether one or more scheduled PDSCHs for ultra-compact DCI are allowed to be used. In such a case, if the indication is for one or more scheduled PDSCHs for ultra-compact DCI, the SIB may also include configuration information for ultra-compact DCI and / or one or more scheduled PDSCHs.

[0097] Configuration information for an ultra-compact DCI found in the SIB may include resource mapping rules for identifying resources used by one or more scheduled PDSCHs relative to the resources used by the ultra-compact DCI. For example, such mapping rules may provide a 1:1 mapping scheme that a UE may use to determine the time and / or frequency location of one or more scheduled PDSCHs scheduled by an ultra-compact DCI relative to the time and / or frequency location of the ultra-compact DCI itself. In such an embodiment, it may be possible that the ultra-compact DCI does not need to make explicit TDRA and / or FDRA indications corresponding to one or more scheduled PDSCHs.

[0098] If PDCCH repetitions are to be used to transmit ultra-compact DCI, the configuration information for ultra-compact DCI found in the SIB may include the number of PDCCH repetitions that carry the repetitions of the ultra-compact DCI. The SIB may further indicate whether these PDCCH repetitions use intra-slot repetitions or inter-slot repetitions.

[0099] Configuration information for ultra-compact DCI found in the SIB may include an indication of one or more fields used in the ultra-compact DCI. It is possible that one or more fields of the ultra-compact DCI understood by the wireless communication system are optional (e.g., because this is not strictly required, because information corresponding to these fields can be found in one or more scheduling PDSCHs, and / or because the UE is configured to use a predefined value for the field if the field is not present). Therefore, the SIB may include an indication of which of these fields are present (or not present) in the ultra-compact DCI to be transmitted.

[0100] Configuration information for ultra-compact DCI found in the SIB may include an indication of whether a new data indicator (NDI) field is included in the ultra-compact DCI. This may inform the UE whether to operate in accordance with / provide for the use of the NDI field with respect to the ultra-compact DCI.

[0101] The SIB with configuration information for ultra-compact DCI and / or one or more scheduled PDSCHs may include numerology information for a PDCCH carrying ultra-compact DCI and / or one or more scheduled PDSCHs. In some cases, it is possible to use a subcarrier spacing (SCS) for the PDCCH for ultra-compact DCI and / or one or more scheduled PDSCHs that is smaller than the subcarrier spacing configured for resources corresponding to / overlapping with the resources used by the PDCCH for ultra-compact DCI and / or one or more scheduled PDSCHs within the wireless communication system. For example, in NR, it is possible that a PDCCH with ultra-compact DCI and / or one or more scheduled PDSCHs may use a 3.75 kilohertz (kHz) SCS and / or a 7.5kHz SCS, where typically at least 15kHz SCS may be used for other channels / transmissions. Using a relatively small SCS in this manner can increase the coverage of the PDCCH for ultra-compact DCI and / or one or more scheduled PDSCHs.

[0102] Configuration information for one or more scheduled PDSCHs found in the SIB may include modulation and coding scheme (MCS) information for the one or more scheduled PDSCHs.

[0103] The configuration information for the one or more scheduled PDSCHs found in the SIB may include a HARQ process number for the one or more scheduled PDSCHs.

[0104] Configuration information for one or more scheduled PDSCHs found in the SIB may include a redundancy version (RV) for the scheduled PDSCH.

[0105] Configuration information for one or more scheduled PDSCHs found in the SIB may include the number of PDSCH repetitions within the one or more scheduled PDSCHs.

[0106] The configuration information for one or more scheduled PDSCHs found in the SIB may include the maximum number of layers for the one or more scheduled PDSCHs. In some embodiments, it is possible that when the maximum number of layers for the one or more scheduled PDSCHs is not 1, there is configuration information for the maximum number of layers; otherwise, the information may not be included (and the UE may thereby implicitly interpret the maximum number of layers as 1).

[0107] Configuration information for one or more scheduled PDSCHs found in the SIB may include the aggregation level of the one or more scheduled PDSCHs. In some embodiments, it is possible that when the aggregation level of the one or more scheduled PDSCHs is not 16, there is configuration information for the aggregation level; otherwise, the information may not be included (and the UE may thereby implicitly understand the aggregation as a pre-understood value (e.g., 16)).

[0108] The SIB with the ultra-compact DCI and / or the configuration information of one or more scheduling PDSCHs may also include the configuration information of the data PDSCH.

[0109] The configuration information for the data PDSCH found in the SIB may include the maximum number of layers for the data PDSCH. In some embodiments, it is possible that when the maximum number of layers for the data PDSCH is not 1, there is configuration information for the maximum number of layers; otherwise, this information may not be included (and the UE may thereby implicitly interpret the maximum number of layers as 1).

[0110] Fig. 9 A method 900 of a UE according to an embodiment is illustrated. The method 900 includes receiving 902 a SIB from a base station, the SIB including first configuration information for an ultra-compact DCI and second configuration information for one or more scheduled PDSCHs.

[0111] The method 900 further includes receiving 904 an ultra-compact DCI from a base station, wherein the ultra-compact DCI corresponds to the first configuration information.

[0112] The method 900 further includes receiving 906 one or more scheduled PDSCHs from the base station, wherein the one or more scheduled PDSCHs correspond to the second configuration information.

[0113] In some embodiments of method 900, the first configuration information for the ultra-compact DCI includes one or more of the following: a resource mapping rule for identifying resources used by one or more scheduling PDSCHs relative to resources used by the ultra-compact DCI; the number of PDCCH repetitions carrying the ultra-compact DCI repetitions; an indication of one or more fields used in the ultra-compact DCI; and an indication of whether an NDI field is included in the ultra-compact DCI.

[0114] In some embodiments of method 900, the SIB further includes numerology information of the PDCCH carrying the ultra-compact DCI.

[0115] In some embodiments of method 900, the second configuration information for one or more scheduled PDSCHs includes one or more of the following: MCS information for one or more scheduled PDSCHs; HARQ process numbers for one or more scheduled PDSCHs; RV for the scheduled PDSCH; the number of PDSCH repetitions within one or more scheduled PDSCHs; the maximum number of layers of one or more scheduled PDSCHs; and aggregation levels of one or more scheduled PDSCHs.

[0116] Embodiments contemplated herein include an apparatus comprising means for performing one or more elements of method 900. The apparatus may be, for example, an apparatus that is a UE (such as wireless device 1702 as a UE, as described herein).

[0117] Embodiments contemplated herein include one or more non-transitory computer-readable media including instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of method 900. The non-transitory computer-readable medium may be, for example, a memory of a UE (such as memory 1706 of wireless device 1702 as a UE, as described herein).

[0118] Embodiments contemplated herein include an apparatus comprising logic, modules, or circuits for performing one or more elements of the method 900. The apparatus may be, for example, an apparatus of a UE (such as the wireless device 1702 as a UE, as described herein).

[0119] Embodiments contemplated herein 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 one or more elements of method 900. The apparatus may be, for example, an apparatus that is a UE (such as wireless device 1702 as a UE, as described herein).

[0120] Embodiments contemplated herein include signals as described in or in connection with one or more elements of method 900 .

[0121] Embodiments contemplated herein include a computer program or computer program product including instructions, wherein execution of the program by a processor causes the processor to perform one or more elements of method 900. The processor may be a processor of a UE (such as processor 1704 of wireless device 1702 as a UE, as described herein). These instructions may be located, for example, in a processor and / or on a memory of a UE (such as memory 1706 of wireless device 1702 as a UE, as described herein).

[0122] Fig.10 A method 1000 of a base station according to an embodiment is illustrated. The method 1000 includes sending 1002 a SIB to a UE, the SIB including first configuration information for an ultra-compact DCI and second configuration information for one or more scheduled PDSCHs.

[0123] The method 1000 further includes sending 1004 an ultra-compact DCI to the UE, wherein the ultra-compact DCI corresponds to the first configuration information.

[0124] The method 1000 further includes sending 1006 one or more scheduled PDSCHs to the UE, wherein the one or more scheduled PDSCHs correspond to the second configuration information.

[0125] In some embodiments of method 1000, the first configuration information for the ultra-compact DCI includes one or more of the following: a resource mapping rule for identifying resources used by one or more scheduling PDSCHs relative to resources used by the ultra-compact DCI; the number of PDCCH repetitions carrying the ultra-compact DCI repetitions; an indication of one or more fields used in the ultra-compact DCI; and an indication of whether an NDI field is included in the ultra-compact DCI.

[0126] In some embodiments of method 1000, the SIB further includes numerology information of a PDCCH carrying an ultra-compact DCI.

[0127] In some embodiments of method 1000, the second configuration information for one or more scheduled PDSCHs includes one or more of the following: MCS information for one or more scheduled PDSCHs; HARQ process numbers for one or more scheduled PDSCHs; RV for the scheduled PDSCH; the number of PDSCH repetitions within one or more scheduled PDSCHs; the maximum number of layers of one or more scheduled PDSCHs; and aggregation levels of one or more scheduled PDSCHs.

[0128] Embodiments contemplated herein include an apparatus comprising means for performing one or more elements of method 1000. The apparatus may be, for example, an apparatus that is a base station (such as RAN device 1718 as a base station, as described herein).

[0129] Embodiments contemplated herein include one or more non-transitory computer-readable media including instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of method 1000. This non-transitory computer-readable medium may be, for example, a memory of a base station (e.g., memory 1722 of RAN device 1718 as a base station, as described herein).

[0130] Embodiments contemplated herein include an apparatus including logical components, modules, or circuits for performing one or more elements of the method 1000. The apparatus may be, for example, an apparatus of a base station (such as the RAN device 1718 as a base station, as described herein).

[0131] Embodiments contemplated herein 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 one or more elements of method 1000. The apparatus may be, for example, an apparatus that is a base station (such as RAN device 1718 as a base station, as described herein).

[0132] Embodiments contemplated herein include signals as described in or in connection with one or more elements of method 1000 .

[0133] Embodiments contemplated herein include a computer program or computer program product including instructions, wherein execution of the program by a processing element causes the processing element to perform one or more elements of method 1000. The processor may be a processor of a base station (such as processor 1720 of RAN device 1718 as a base station, as described herein). These instructions may be located, for example, in a processor and / or on a memory of a base station (such as memory 1722 of RAN device 1718 as a base station, as described herein).

[0134] Ultra-compact DCI design for downlink data transmission scheduling

[0135] An implementation of an ultra-compact DCI design in the case of scheduling DL data transmission is now discussed.

[0136] Various formats of ultra-compact DCI for DL ​​data transmission are contemplated. In some embodiments, the ultra-compact DCI may be DCI format 1_2, as may be understood in the definition of some wireless communication systems. In some embodiments, the ultra-compact DCI may be a DCI format having a reduced payload size compared to the payload size of a "compact DCI", as may be understood in the definition of some wireless communication systems. For example, in an NR RAT, it is possible that, assuming the same circumstances, the ultra-compact DCI may have a smaller payload size than a "compact DCI" (e.g., following format 1_2).

[0137] The ultra-compact DCI may include one or more fields related to one or more scheduled PDSCHs that schedule data PDSCHs for DL ​​data transmission. These fields may indicate to the UE how to receive and / or decode one or more scheduled PDSCHs at the UE. Then, based on the scheduled PDSCH, the UE determines the scheduling of the data PDSCH, and thereby enables the UE to subsequently receive the data PDSCH.

[0138] The field for one or more scheduled PDSCHs in the ultra-compact DCI may include a time domain resource allocation (TDRA) table index field for one or more scheduled PDSCHs. In the case where the time resource of one or more scheduled PDSCHs is implicitly understood at the UE based on the time and / or frequency resources of the received ultra-compact DCI (e.g., by using a mapping scheme configured by the SIB), this field may not exist.

[0139] The fields for one or more scheduled PDSCHs in the ultra-compact DCI may include a frequency domain resource allocation (FDRA) field for one or more scheduled PDSCHs. The FDRA field may be configured to indicate a bitmap or (starting resource block (RB), length of RB) pair in its field data. In the case where the frequency resources of one or more scheduled PDSCHs are implicitly understood at the UE based on the time and / or frequency resources of the received ultra-compact DCI (e.g., by using a mapping scheme configured by the SIB), this field may not exist.

[0140] The field for one or more scheduled PDSCHs in the ultra-compact DCI may include an MCS field for one or more scheduled PDSCHs. The MCS field may indicate an absolute MCS for one or more scheduled PDSCHs. Alternatively, the MCS field may indicate an incremental MCS relative to a reference MCS that has been configured to the UE by a higher layer.

[0141] The field for one or more scheduled PDSCHs in the ultra-compact DCI may include an RV field for one or more scheduled PDSCHs.

[0142] The field for one or more scheduled PDSCHs in the ultra-compact DCI may include a HARQ process number field for the one or more scheduled PDSCHs.

[0143] The fields for the one or more scheduled PDSCHs in the ultra-compact DCI may include an NDI field for the one or more scheduled PDSCHs. It is contemplated that in some embodiments, DCI-based retransmissions of the one or more scheduled PDSCHs are not allowed.

[0144] The fields for the one or more scheduled PDSCHs in the ultra-compact DCI may include a downlink allocation indicator (DAI) field for the one or more scheduled PDSCHs. It is contemplated that in some embodiments, aggregated HARQ-ACK feedback is not allowed.

[0145] The field for one or more scheduled PDSCHs in the ultra-compact DCI may include a PDSCH repetition number field for the one or more scheduled PDSCHs.

[0146] It is contemplated that in some embodiments, one of the PDSCH repetition number field and the MCS field is configured in the SIB, while the other is indicated in the ultra-compact DCI. For example, if the MCS information is configured in the SIB, it is possible that the ultra-compact DCI includes a PDSCH repetition number field for one or more scheduled PDSCHs (instead of an MCS field for one or more PDSCH repetitions). As another example, if the number of PDSCH repetitions for one or more scheduled PDSCHs is configured in the SIB, it is possible that the ultra-compact DCI may include an MCS field for one or more scheduled PDSCHs (instead of a PDSCH repetition number field for one or more scheduled PDSCHs).

[0147] In some embodiments, one or more of the TDRA table index field, FDRA field, MCS field, RV field, HARQ process number field, NDI field, DAI field, and / or PDSCH repetition number field in the ultra-compact DCI may use fixed data. In other words, one or more of these fields may use predetermined data. This may be useful in cases where the UE does not use / need data from these fields (for example, because the UE is configured to operate without the data, or knows the data in another way), but the inclusion of the field (with fixed data) makes the ultra-compact DCI easier to decode. For example, this may occur when the fixed data is known to the UE (and therefore expected at the UE). In such a case, the inclusion of a field with fixed data expected by the UE enhances the UE's ability to perform polarity or linear decoding as a whole on the ultra-compact DCI.

[0148] The ultra-compact DCI may include one or more fields related to HARQ-ACK signaling for one or more scheduled PDSCHs. As described herein, in some embodiments, the UE sends a PUCCH including HARQ-ACK signaling for one or more scheduled PDSCHs in response to it receiving one or more scheduled PDSCHs. Therefore, the data in these fields may relate to the manner in which the PUCCH with the HARQ-ACK signaling is encoded and / or sent.

[0149] The field for HARQ-ACK signaling of one or more scheduled PDSCHs may include a PUCCH resource indicator field for HARQ-ACK signaling.

[0150] The field for HARQ-ACK signaling of one or more scheduled PDSCHs may include a transmit power control (TPC) command field for HARQ-ACK signaling.

[0151] The field for HARQ-ACK signaling of one or more scheduled PDSCHs may include a PDSCH to HARQ feedback timing indicator field for HARQ-ACK signaling.

[0152] In other embodiments, one or more of these fields associated with HARQ-ACK signaling for one or more scheduled PDSCHs may not be present in the ultra-compact DCI (or alternatively, may contain fixed values ​​that are not actively used by the UE to facilitate decoding of the ultra-compact DCI). This situation may correspond to the situation as described herein, where HARQ-ACK signaling for one or more scheduled PDSCHs is not used, or where one or more data items corresponding to these fields are provided to the UE in one or more PDSCHs scheduled by the ultra-compact DCI (e.g., in the MAC CE of these one or more PDSCHs) rather than in the ultra-compact DCI itself.

[0153] The omission / fixing of these fields may also correspond to the case where the base station is configured to infer whether the UE successfully received / decoded one or more scheduling PDSCHs from the HARQ-ACK signaling for the data PDSCH. In such a case, failure to receive the expected HARQ-ACK signaling for the data PDSCH may mean that one or more scheduling PDSCHs were not received and / or were not successfully decoded at the UE.

[0154] In the case that the HARQ process number used by one or more scheduled PDSCHs is configured with HARQ feedback disabled, the ultra-compact DCI may omit / fix these fields. In such a case, the network will not expect HARQ-ACK signaling for one or more scheduled PDSCHs.

[0155] In some embodiments where one or more of these fields are included (and not fixed) in the ultra-compact DCI, it is possible that the UE may use the PUCCH for both HARQ-ACK signaling and data PDSCHs of one or more scheduled PDSCHs. Fig.11 A diagram 1100 is illustrated illustrating a dynamic resource grant process for DL ​​data transmission according to an embodiment. More specifically, the diagram 1100 illustrates the use of ultra-compact DCI 1102 to schedule one or more scheduling PDSCHs 1106, which then schedule data PDSCHs 1108 for DL ​​data transmission. Fig.11 The schematic diagram 1100 of FIG. 1 additionally illustrates the scheduling and use of a PUCCH 1104 with HARQ-ACK signaling for one or more scheduled PDSCHs 1106. Fig.11In the embodiment of FIG. 1 , note that the PUCCH 1104 appears after the data PDSCH 1108 .

[0156] The ultra-compact DCI 1102 may include one or more of the following: a PUCCH resource indicator field 1106 for HARQ-ACK signaling of one or more scheduled PDSCHs, a TPC command field 1106 for HARQ-ACK signaling of one or more scheduled PDSCHs, and / or a PDSCH to HARQ feedback timing indicator field 1106 for HARQ-ACK signaling of one or more scheduled PDSCHs. Fig.11 As shown, data from one or more of these fields may be used to schedule PUCCH 1104 and / or determine the manner in which PUCCH 1104 is transmitted.

[0157] Further, the UE may also be configured to use the PUCCH 1104 for HARQ-ACK signaling for the data PDSCH 1108 (in addition to using it for HARQ-ACK signaling for one or more scheduling PDSCHs 1106). In such a case, the total HARQ-ACK signaling may include two bits (one bit for each type of HARQ-ACK signaling). In such a case, the first of the two bits may provide HARQ-ACK signaling for one or more scheduling PDSCHs 1106, and the second of the two bits may provide HARQ-ACK signaling for the data PDSCH 1108. For example, including two bits of "10" in the PUCCH 1104 may mean that one or more scheduling PDSCHs 1106 are received (corresponding to "1" in the first bit) and that the data PDSCH 1108 is not received (corresponding to "0" in the second bit).

[0158] In accordance with Fig.11 In an embodiment, it is possible that the MAC CE for one or more scheduled PDSCHs 1106 does not schedule the PUCCH for HARQ-ACK signaling for data PDSCH 1108 (because the HARQ-ACK signaling is instead scheduled by the ultra-compact DCI 1102 in PUCCH 1104 for both the HARQ-ACK signaling for one or more scheduled PDSCHs 1106 and the HARQ-ACK signaling for data PDSCH 1108). Further, it is possible that in such a case, the offset K31110 may not need to be greater than the UE base station RTT (because in this case, the UL signaling of the PUCCH between the one or more scheduled PDSCHs 1106 and the data PDSCH 1108 does not need to be considered).

[0159] Ultra-compact DCI design for uplink data transmission scheduling

[0160] An implementation of an ultra-compact DCI design in the case of scheduling UL data transmission is now discussed.

[0161] Various formats of ultra-compact DCI for UL data transmission scheduling are contemplated. In some embodiments, the ultra-compact DCI may be DCI format 1_2, as may be understood in the definition of some wireless communication systems. In some embodiments, the ultra-compact DCI may be a DCI format having a reduced payload size compared to the payload size of a "compact DCI", as may be understood in the definition of some wireless communication systems. For example, in an NR RAT, it is possible that, assuming the same circumstances, the ultra-compact DCI may have a smaller payload size than a "compact DCI" (e.g., following format 1_2).

[0162] The ultra-compact DCI may include one or more fields related to one or more scheduled PDSCHs that schedule PUSCHs for UL data transmission. These fields may indicate to the UE the manner in which one or more scheduled PDSCHs are received and / or decoded at the UE. Then, based on the scheduled PDSCH, the UE determines the scheduling of the PUSCH, and thereby enables the UE to subsequently send the PUSCH in a manner in which the PUSCH can be received by the base station.

[0163] The field for one or more scheduled PDSCHs in the ultra-compact DCI may include a TDRA table index field for one or more scheduled PDSCHs. This field may not exist in the case where the time resources of one or more scheduled PDSCHs are implicitly understood at the UE based on the time and / or frequency resources of the received ultra-compact DCI (e.g., by using a mapping scheme configured by the SIB).

[0164] The field for one or more scheduled PDSCHs in the ultra-compact DCI may include an FDRA field for one or more scheduled PDSCHs. This field may not exist in the case where the frequency resources of one or more scheduled PDSCHs are implicitly understood at the UE based on the time and / or frequency resources of receiving the ultra-compact DCI (e.g., by using a mapping scheme configured by the SIB).

[0165] The field for one or more scheduled PDSCHs in the ultra-compact DCI may include an MCS field for one or more scheduled PDSCHs. The MCS field may indicate an absolute MCS for one or more scheduled PDSCHs. Alternatively, the MCS field may indicate an incremental MCS relative to a reference MCS that has been configured to the UE by a higher layer.

[0166] The field for one or more scheduled PDSCHs in the ultra-compact DCI may include an RV field for one or more scheduled PDSCHs.

[0167] The field for one or more scheduled PDSCHs in the ultra-compact DCI may include a HARQ process number field for the one or more scheduled PDSCHs.

[0168] The fields for the one or more scheduled PDSCHs in the ultra-compact DCI may include an NDI field for the one or more scheduled PDSCHs. It is contemplated that in some embodiments, DCI-based retransmissions of the one or more scheduled PDSCHs are not allowed.

[0169] The field for one or more scheduled PDSCHs in the ultra-compact DCI may include a DAI field for one or more scheduled PDSCHs. It is contemplated that in some embodiments, aggregated HARQ-ACK feedback is not allowed.

[0170] The field for one or more scheduled PDSCHs in the ultra-compact DCI may include a PDSCH repetition number field for the one or more scheduled PDSCHs.

[0171] It is contemplated that in some embodiments, one of the PDSCH repetition number field and the MCS field is configured in the SIB, while the other is indicated in the ultra-compact DCI. For example, if the MCS information is configured in the SIB, it is possible that the ultra-compact DCI includes a PDSCH repetition number field for one or more scheduled PDSCHs (instead of an MCS field for one or more PDSCH repetitions). As another example, if the number of PDSCH repetitions for one or more scheduled PDSCHs is configured in the SIB, it is possible that the ultra-compact DCI may include an MCS field for one or more scheduled PDSCHs (instead of a PDSCH repetition number field for one or more scheduled PDSCHs).

[0172] In some embodiments, one or more of the MCS field, RV field, HARQ process number field, NDI field, DAI field, and / or PDSCH repetition number field found in the ultra-compact DCI may use fixed data. In other words, one or more of these fields may use predetermined data. This may be useful in situations where the UE does not use / need data from these fields (e.g., because the UE is configured to operate without the data, or knows the data in another way), but the inclusion of the field (with fixed data) makes the ultra-compact DCI easier to decode. For example, this may occur in situations where the fixed data is known to the UE (and therefore expected at the UE). In such a case, the inclusion of fields with fixed data expected by the UE improves the UE's ability to perform polarity or linear decoding on the ultra-compact DCI as a whole.

[0173] The ultra-compact DCI may include one or more fields related to the PUSCH. For example, the ultra-compact DCI may include a TPC command for the PUSCH, which controls the power at which the UE transmits the PUSCH.

[0174] The ultra-compact DCI may include one or more fields related to HARQ-ACK signaling for one or more scheduled PDSCHs. As described herein, in some embodiments, the UE sends a PUCCH including HARQ-ACK signaling for one or more scheduled PDSCHs in response to it receiving one or more scheduled PDSCHs. Therefore, the data in these fields may relate to the manner in which the PUCCH with the HARQ-ACK signaling is encoded and / or sent.

[0175] The field for HARQ-ACK signaling of one or more scheduled PDSCHs may include a PUCCH resource indicator field for HARQ-ACK signaling.

[0176] The field for HARQ-ACK signaling of one or more scheduled PDSCHs may include a TPC command field for HARQ-ACK signaling.

[0177] The field for HARQ-ACK signaling of one or more scheduled PDSCHs may include a PDSCH to HARQ feedback timing indicator field for HARQ-ACK signaling.

[0178] In other embodiments, one or more of these fields associated with HARQ-ACK signaling for one or more scheduled PDSCHs may not be present in the ultra-compact DCI (or alternatively, may contain fixed values ​​that are not actively used by the UE to facilitate decoding of the ultra-compact DCI). This situation may correspond to the situation as described herein, where HARQ-ACK signaling for one or more scheduled PDSCHs is not used, or where one or more data items corresponding to these fields are provided to the UE in one or more PDSCHs scheduled by the ultra-compact DCI (e.g., in the MAC CE of these one or more PDSCHs) rather than in the ultra-compact DCI itself.

[0179] In the case that the HARQ process number used by one or more scheduled PDSCHs is configured with HARQ feedback disabled, the ultra-compact DCI may omit / fix these fields. In such a case, the network will not expect HARQ-ACK signaling for one or more scheduled PDSCHs.

[0180] It should be noted that a person of ordinary skill in the art having the present disclosure may understand that one or more features discussed in the "Ultra-compact DCI design for downlink data transmission scheduling" section may also be used in the UL data transmission scheduling case, and / or various features discussed in the "Ultra-compact DCI design for uplink data transmission scheduling" section may also be used in the DL data transmission scheduling case. Therefore, the use of these section headings herein is provided for organizational purposes only and should not be interpreted as a hard limitation on any crossover of features between cases that may be appropriate.

[0181] Additional Ultra-Compact DCI Design Considerations

[0182] Ultra-compact DCI can be received in a PDCCH with cyclic redundancy check (CRC) bits, where the CRC bits are scrambled by one of a cell radio network temporary identity (RNTI) (C-RNTI), a configured scheduling RNTI (CS-RNTI), a modulation and coding scheme cell RNTI (MCS-C-RNTI), a random access RNTI (RA-RNTI), a temporary cell RNTI (TC-RNTI) (with DCI format 1_0), a paging RNTI (P-RNTI) and a system information RNTI (SI-RNTI).

[0183] To support such scrambling using RA-RNTI, the number of PDSCH repetitions for one or more scheduled PDSCHs may be indicated to the UE. In one embodiment, the number of PDSCH repetitions for one or more scheduled PDSCHs may be indicated in a SIB sent to the UE. In another embodiment, the number of PDSCH repetitions for one or more scheduled PDSCHs may be indicated in a random access response (RAR) sent by the base station to the UE. In this case, the RAR may use the MCS field, and a subset of the MCS field may be used to indicate the number of PDSCH repetitions. For example, it is possible that the MCS field may have four bits, and two of the four bits are used to indicate the number of PDSCH repetitions.

[0184] It is possible that, where P-RNTI or SI-RNTI is used, the associated ultra-compact DCI has been broadcast (e.g., configured for use by more than one UE). It is therefore possible that using P-RNTI or SI-RNTI in this manner may correspond to a situation where PUCCH with HARQ-ACK signaling for one or more scheduled PDSCHs is not used.

[0185] In some embodiments, ultra-compact DCI can be received in one or more PDCCH repetitions. These repetitions can be intra-slot repetitions rather than inter-slot repetitions. When using PDCCH repetitions, it is possible that some or all of the PDCCH repetitions overlap with the time slots occupied by the synchronization signaling block (SSB) to be sent by the base station. In some such cases, overlapping PDCCH repetitions are skipped. In some such cases, overlapping PDCCH repetitions are postponed.

[0186] In some embodiments, ultra-compact DCI is received in one or more of a plurality of PDCCHs, wherein each of the plurality of PDCCHs is transmitted by a different transmit reception point (TRP). In such a case, it is possible that each of the plurality of PDCCHs is associated with a different search space set (e.g., corresponding to the TRP of the PDCCH).

[0187] In such cases, it is possible that multiple PDCCHs may be time division multiplexed (TDMed) with each other. In some such embodiments, PDCCHs from multiple TRPs may be time division multiplexed (TDMed) in a single time slot. In other such embodiments, PDCCHs from multiple TRPs may be time division multiplexed (TDMed) across different / multiple time slots.

[0188] It is possible (additionally or alternatively) that multiple PDCCHs are frequency division multiplexed (FDMed) with each other. In such an embodiment, different frequency locations of a set of search spaces for PDCCHs may be used for the frequency division multiplexing.

[0189] It is possible (additionally or alternatively) that multiple PDCCHs are spatially division multiplexed (SDMed) (e.g., each PDCCH may be sent using a different / specific beam direction determined based on the TRP of the specific PDCCH).

[0190] When multiple PDCCHs are used, it is possible that the multiple PDCCHs use PDCCH repetition. In other words, it is possible that some or all of the multiple PDCCHs are identical (e.g., have the same content). In this case, receiving two or more of the PDCCHs at the UE allows the UE to utilize the empirical gain of these repetitions to help decode the ultra-compact DCI from the PDCCH.

[0191] In other cases, it is possible that different content corresponding to an ultra-compact DCI is transmitted in each of the multiple PDCCHs (e.g., each may use a DCI that includes a portion of the content of a single (logical) ultra-compact DCI, as already described herein). Thus, a first field for an ultra-compact DCI may be included in a first of the multiple PDCCHs, while a second field for the same ultra-compact DCI may be included in a second of the multiple PDCCHs, etc. Upon receiving a set of such PDCCHs with a representative portion of the ultra-compact DCI, the UE is able to determine the ultra-compact DCI.

[0192] Fig.12 A method 1200 of a UE according to an embodiment is illustrated. The method 1200 includes receiving 1202 an ultra-compact DCI from a base station, the ultra-compact DCI including a first field of one or more scheduling PDSCHs for scheduling a data PDSCH.

[0193] The method 1200 further includes receiving 1204 one or more scheduled PDSCHs from the base station, wherein the one or more scheduled PDSCHs correspond to data of the first field.

[0194] The method 1200 further includes receiving 1206 a data PDSCH scheduled by the one or more scheduling PDSCHs from the base station.

[0195] In some embodiments of the method 1200, the first field for the one or more scheduled PDSCHs includes one or more of the following: a TDRA table index field for the one or more scheduled PDSCHs, a FDRA field for the one or more scheduled PDSCHs, an MCS field for the one or more scheduled PDSCHs, an RV field for the one or more scheduled PDSCHs, a HARQ process number field for the one or more scheduled PDSCHs, an NDI field for the one or more scheduled PDSCHs, a DAI field for the one or more scheduled PDSCHs, and a PDSCH repetition number field for the one or more scheduled PDSCHs. In some of these embodiments, one or more of the MCS field, the RV field, the HARQ process number field, the NDI field, the DAI field, and the PDSCH repetition number field include fixed data.

[0196] In some embodiments, method 1200 further includes sending a PUCCH including first HARQ-ACK signaling for one or more scheduled PDSCHs to the base station, wherein the ultra-compact DCI further includes a second field for the first HARQ-ACK signaling for one or more scheduled PDSCHs.

[0197] In some of these embodiments, the second field for the first HARQ-ACK signaling includes one or more of the following: a PUCCH resource indicator field for the first HARQ-ACK signaling, a TPC command field for the first HARQ-ACK signaling, and a PDSCH to HARQ feedback timing indicator field for the first HARQ-ACK signaling. In some of these cases, one or more of the PUCCH resource indicator field, the TPC command field, and the PDSCH to HARQ feedback timing indicator field present in the ultra-compact DCI includes fixed data.

[0198] In some of these embodiments, the PUCCH further includes second HARQ-ACK signaling for the data PDSCH.

[0199] In some implementations of the method 1200, the ultra-compact DCI is received in a PDCCH with CRC bits scrambled by one of C-RNTI, CS-RNTI, MCS-C-RNTI, RA-RNTI, TC-RNTI, P-RNTI, and SI-RNTI.

[0200] In some implementations of method 1200, the ultra-compact DCI is received in one or more PDCCH repetitions.

[0201] In some embodiments of method 1200, ultra-compact DCI is received in one or more of a plurality of PDCCHs, wherein each of the plurality of PDCCHs is sent by a different TRP. In some of these embodiments, each of the plurality of PDCCHs is associated with a different search space set. In some of these embodiments, the plurality of PDCCHs are one or more of TDMed, FDMed, and SDMed. In some of these embodiments, each of the plurality of PDCCHs is identical.

[0202] In some implementations of method 1200, the ultra-compact DCI has a first payload size that is smaller than a second payload size of the compact DCI.

[0203] In some embodiments of method 1200, the ultra-compact DCI is DCI format 1_2.

[0204] Embodiments contemplated herein include an apparatus comprising means for performing one or more elements of the method 1200. The apparatus may be, for example, an apparatus that is a UE (such as the wireless device 1702 as a UE, as described herein).

[0205] Embodiments contemplated herein include one or more non-transitory computer-readable media including instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of method 1200. The non-transitory computer-readable medium may be, for example, a memory of a UE (such as memory 1706 of wireless device 1702 as a UE, as described herein).

[0206] Embodiments contemplated herein include an apparatus including logical components, modules, or circuits for performing one or more elements of the method 1200. The apparatus may be, for example, an apparatus of a UE (such as the wireless device 1702 as a UE, as described herein).

[0207] Embodiments contemplated herein 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 one or more elements of the method 1200. The apparatus may be, for example, an apparatus that is a UE (such as wireless device 1702 as a UE, as described herein).

[0208] Embodiments contemplated herein include a signal as described in or associated with one or more elements of method 1200 .

[0209] Embodiments contemplated herein include a computer program or computer program product including instructions, wherein execution of the program by a processor causes the processor to perform one or more elements of the method 1200. The processor may be a processor of a UE (such as the processor 1704 of the wireless device 1702 as a UE, as described herein). These instructions may be located, for example, in a processor and / or on a memory of a UE (such as the memory 1706 of the wireless device 1702 as a UE, as described herein).

[0210] Fig.13 A method 1300 of a base station according to an embodiment is illustrated. The method 1300 includes sending 1302 an ultra-compact DCI to a UE, the ultra-compact DCI including a first field of one or more scheduling PDSCHs for scheduling data PDSCHs.

[0211] The method 1300 further includes transmitting 1304 one or more scheduled PDSCHs to the UE, wherein the one or more scheduled PDSCHs correspond to data of the first field.

[0212] The method 1300 further includes transmitting 1306 to the UE a data PDSCH scheduled by the one or more scheduling PDSCHs.

[0213] In some embodiments of the method 1300, the first field for the one or more scheduled PDSCHs includes one or more of the following: a TDRA table index field for the one or more scheduled PDSCHs, a FDRA field for the one or more scheduled PDSCHs, an MCS field for the one or more scheduled PDSCHs, an RV field for the one or more scheduled PDSCHs, a HARQ process number field for the one or more scheduled PDSCHs, an NDI field for the one or more scheduled PDSCHs, a DAI field for the one or more scheduled PDSCHs, and a PDSCH repetition number field for the one or more scheduled PDSCHs. In some of these embodiments, one or more of the MCS field, the RV field, the HARQ process number field, the NDI field, the DAI field, and the PDSCH repetition number field include fixed data.

[0214] In some embodiments, method 1300 further includes receiving a PUCCH including first HARQ-ACK signaling for one or more scheduled PDSCHs from the UE, wherein the ultra-compact DCI further includes a second field of the first HARQ-ACK signaling for the one or more scheduled PDSCHs.

[0215] In some of these embodiments, the second field for the first HARQ-ACK signaling includes one or more of the following: a PUCCH resource indicator field for the first HARQ-ACK signaling, a TPC command field for the first HARQ-ACK signaling, and a PDSCH to HARQ feedback timing indicator field for the first HARQ-ACK signaling. In some of these cases, one or more of the PUCCH resource indicator field, the TPC command field, and the PDSCH to HARQ feedback timing indicator field present in the ultra-compact DCI includes fixed data.

[0216] In some of these embodiments, the PUCCH further includes second HARQ-ACK signaling for the data PDSCH.

[0217] In some implementations of the method 1300, ultra-compact DCI is sent in a PDCCH with CRC bits scrambled by one of C-RNTI, CS-RNTI, MCS-C-RNTI, RA-RNTI, TC-RNTI, P-RNTI, and SI-RNTI.

[0218] In some implementations of method 1300, the ultra-compact DCI is sent in one or more PDCCH repetitions.

[0219] In some implementations of method 1300, the ultra-compact DCI has a first payload size that is smaller than a second payload size of the compact DCI.

[0220] In some embodiments of method 1300, the ultra-compact DCI is DCI format 1_2.

[0221] Embodiments contemplated herein include an apparatus comprising means for performing one or more elements of the method 1300. The apparatus may be, for example, an apparatus that is a base station (such as the RAN device 1718 as a base station, as described herein).

[0222] Embodiments contemplated herein include one or more non-transitory computer-readable media including instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of method 1300. This non-transitory computer-readable medium may be, for example, a memory of a base station (e.g., memory 1722 of RAN device 1718 as a base station, as described herein).

[0223] Embodiments contemplated herein include an apparatus comprising logical components, modules, or circuits for performing one or more elements of the method 1300. The apparatus may be, for example, an apparatus of a base station (such as the RAN device 1718 as a base station, as described herein).

[0224] Embodiments contemplated herein 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 one or more elements of method 1300. The apparatus may be, for example, an apparatus that is a base station (such as RAN device 1718 as a base station, as described herein).

[0225] Embodiments contemplated herein include a signal as described in or associated with one or more elements of method 1300 .

[0226] Embodiments contemplated herein include a computer program or computer program product including instructions, wherein execution of the program by a processing element causes the processing element to perform one or more elements of the method 1300. The processor may be a processor of a base station (such as the processor 1720 of the RAN device 1718 as a base station, as described herein). These instructions may be located, for example, in a processor and / or on a memory of a base station (such as the memory 1722 of the RAN device 1718 as a base station, as described herein).

[0227] Fig.14 A method 1400 of a UE according to an embodiment is illustrated. The method 1400 includes receiving 1402 an ultra-compact DCI from a base station, the ultra-compact DCI including a first field for scheduling one or more scheduled PDSCHs for scheduling a PUSCH.

[0228] The method 1400 further includes receiving 1404 one or more scheduled PDSCHs from the base station, wherein the one or more scheduled PDSCHs correspond to data of the first field.

[0229] The method 1400 further includes sending 1406 a PUSCH scheduled by one or more scheduling PDSCHs to a base station.

[0230] In some embodiments of method 1400, the first field for one or more scheduled PDSCHs includes one or more of the following: a TDRA table index field for one or more scheduled PDSCHs, a FDRA field for one or more scheduled PDSCHs, an MCS field for one or more scheduled PDSCHs, an RV field for one or more scheduled PDSCHs, a HARQ process number field for one or more scheduled PDSCHs, an NDI field for one or more scheduled PDSCHs, a DAI field for one or more scheduled PDSCHs, and a PDSCH repetition number field within one or more scheduled PDSCHs. In some of these embodiments, one or more of the MCS field, the RV field, the HARQ process number field, the NDI field, the DAI field, and the PDSCH repetition number field present in the ultra-compact DCI includes fixed data.

[0231] In some embodiments of the method 1400, the ultra-compact DCI further includes a TPC command for the PUSCH.

[0232] In some embodiments, method 1400 further includes sending a PUCCH including HARQ-ACK signaling for one or more scheduled PDSCHs to the base station, wherein the ultra-compact DCI further includes a second field for HARQ-ACK signaling. In some of these embodiments, the second field for HARQ-ACK signaling includes one or more of the following: a PUCCH resource indicator field for HARQ-ACK signaling, a TPC command field for HARQ-ACK signaling, and a PDSCH to HARQ feedback timing indicator field for HARQ-ACK signaling. In some of these cases, one or more of the PUCCH resource indicator field, the TPC command field, and the PDSCH to HARQ feedback timing indicator field present in the ultra-compact DCI includes fixed data.

[0233] In some implementations of the method 1400, the ultra-compact DCI is received in a PDCCH with CRC bits scrambled by one of C-RNTI, CS-RNTI, MCS-C-RNTI, RA-RNTI, TC-RNTI, P-RNTI, and SI-RNTI.

[0234] In some implementations of method 1400, the ultra-compact DCI is received in one or more PDCCH repetitions.

[0235] In some embodiments of method 1400, ultra-compact DCI is received in one or more of a plurality of PDCCHs, wherein each of the plurality of PDCCHs is sent by a different TRP. In some of these embodiments, each of the plurality of PDCCHs is associated with a different search space set. In some of these embodiments, the plurality of PDCCHs are one or more of TDMed, FDMed, and SDMed. In some of these embodiments, each of the plurality of PDCCHs is identical.

[0236] In some implementations of method 1400, the ultra-compact DCI has a first payload size that is smaller than a second payload size of the compact DCI.

[0237] In some embodiments of method 1400, the ultra-compact DCI is DCI format 1_2.

[0238] Embodiments contemplated herein include an apparatus comprising means for performing one or more elements of the method 1400. The apparatus may be, for example, an apparatus that is a UE (such as the wireless device 1702 as a UE, as described herein).

[0239] Embodiments contemplated herein include one or more non-transitory computer-readable media including instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of method 1400. The non-transitory computer-readable medium may be, for example, a memory of a UE (such as memory 1706 of wireless device 1702 as a UE, as described herein).

[0240] Embodiments contemplated herein include an apparatus comprising logical components, modules, or circuits for performing one or more elements of the method 1400. The apparatus may be, for example, an apparatus of a UE (such as the wireless device 1702 as a UE, as described herein).

[0241] Embodiments contemplated herein 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 one or more elements of method 1400. The apparatus may be, for example, an apparatus of a UE (such as wireless device 1702 as a UE, as described herein).

[0242] Embodiments contemplated herein include signals as described in or related to one or more elements of method 1400 .

[0243] Embodiments contemplated herein include a computer program or computer program product including instructions, wherein execution of the program by a processor causes the processor to perform one or more elements of the method 1400. The processor may be a processor of a UE (such as the processor 1704 of the wireless device 1702 as a UE, as described herein). These instructions may be located, for example, in a processor and / or on a memory of a UE (such as the memory 1706 of the wireless device 1702 as a UE, as described herein).

[0244] Fig.15 A method 1500 of a base station according to an embodiment is illustrated. The method 1500 includes sending 1502 an ultra-compact DCI to a UE, the ultra-compact DCI including a first field of one or more scheduled PDSCHs for scheduling a PUSCH.

[0245] The method 1500 further includes transmitting 1504 one or more scheduled PDSCHs to the UE, wherein the one or more scheduled PDSCHs correspond to data of the first field.

[0246] The method 1500 further includes receiving 1506 from the UE a PUSCH scheduled by one or more scheduling PDSCHs.

[0247] In some embodiments of method 1500, the first field for one or more scheduled PDSCHs includes one or more of the following: a TDRA table index field for one or more scheduled PDSCHs, a FDRA field for one or more scheduled PDSCHs, an MCS field for one or more scheduled PDSCHs, an RV field for one or more scheduled PDSCHs, a HARQ process number field for one or more scheduled PDSCHs, an NDI field for one or more scheduled PDSCHs, a DAI field for one or more scheduled PDSCHs, and a PDSCH repetition number field within one or more scheduled PDSCHs. In some of these embodiments, one or more of the MCS field, the RV field, the HARQ process number field, the NDI field, the DAI field, and the PDSCH repetition number field present in the ultra-compact DCI includes fixed data.

[0248] In some embodiments of method 1500, the ultra-compact DCI further includes a TPC command for the PUSCH.

[0249] In some embodiments, method 1500 further includes receiving a PUCCH including HARQ-ACK signaling for one or more scheduled PDSCHs from the UE, wherein the ultra-compact DCI further includes a second field for the HARQ-ACK signaling. In some of these embodiments, the second field for the HARQ-ACK signaling includes one or more of the following: a PUCCH resource indicator field for the HARQ-ACK signaling, a TPC command field for the HARQ-ACK signaling, and a PDSCH to HARQ feedback timing indicator field for the HARQ-ACK signaling. In some of these cases, one or more of the PUCCH resource indicator field, the TPC command field, and the PDSCH to HARQ feedback timing indicator field present in the ultra-compact DCI includes fixed data.

[0250] In some implementations of method 1500, ultra-compact DCI is received in a PDCCH with CRC bits scrambled by one of C-RNTI, CS-RNTI, MCS-C-RNTI, RA-RNTI, TC-RNTI, P-RNTI, and SI-RNTI.

[0251] In some implementations of method 1500, ultra-compact DCI is sent in one or more PDCCH repetitions.

[0252] In some implementations of method 1500, the ultra-compact DCI has a first payload size that is smaller than a second payload size of the compact DCI.

[0253] In some embodiments of method 1500, the ultra-compact DCI is DCI format 1_2.

[0254] Embodiments contemplated herein include an apparatus comprising means for performing one or more elements of the method 1500. The apparatus may be, for example, an apparatus that is a base station (such as the RAN device 1718 as a base station, as described herein).

[0255] Embodiments contemplated herein include one or more non-transitory computer-readable media including instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of method 1500. This non-transitory computer-readable medium may be, for example, a memory of a base station (e.g., memory 1722 of RAN device 1718 as a base station, as described herein).

[0256] Embodiments contemplated herein include an apparatus comprising logical components, modules, or circuits for performing one or more elements of the method 1500. The apparatus may be, for example, an apparatus of a base station (such as the RAN device 1718 as a base station, as described herein).

[0257] Embodiments contemplated herein 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 one or more elements of method 1500. The apparatus may be, for example, an apparatus that is a base station (such as RAN device 1718 as a base station, as described herein).

[0258] Embodiments contemplated herein include signals as described in or related to one or more elements of method 1500 .

[0259] Embodiments contemplated herein include a computer program or computer program product including instructions, wherein execution of the program by a processing element causes the processing element to perform one or more elements of the method 1500. The processor may be a processor of a base station (such as the processor 1720 of the RAN device 1718 as a base station, as described herein). These instructions may be located, for example, in the processor and / or on a memory of the base station (such as the memory 1722 of the RAN device 1718 as a base station, as described herein).

[0260] Fig.16 An example architecture of a wireless communication system 1600 according to the embodiments disclosed herein is illustrated. The description provided below is for an example wireless communication system 1600 operating in conjunction with LTE system standards and / or 5G or NR system standards provided in 3GPP technical specifications and other 3GPP documents.

[0261] like Fig.16 As shown, the wireless communication system 1600 includes UE 1602 and UE 1604 (although any number of UEs may be used). In this example, UE 1602 and UE 1604 are illustrated as smartphones (e.g., handheld touch screen mobile computing devices capable of connecting to one or more cellular networks), but may also include any mobile or non-mobile computing device configured for wireless communication.

[0262] UE 1602 and UE 1604 may be configured to be communicatively coupled to RAN 1606. In an embodiment, RAN 1606 may be NG-RAN, E-UTRAN, etc. UE 1602 and UE 1604 utilize connections (or channels) (shown as connection 1608 and connection 1610, respectively) with RAN 1606, where each connection (or channel) includes a physical communication interface. RAN 1606 may include one or more base stations (such as ground base station 1612, ground base station 1614, satellite base station 1636, and satellite base station 1638) and / or other entities that enable connection 1608 and connection 1610 (e.g., satellite 1642, which may not have base station functionality). One or more satellite gateways 1634 may be used in conjunction with the RAN 1606 to communicate with the RAN 1606. Figure 1 The NTN architecture 100 and Figure 2 The NTN architecture 200 depicts the manner (and with appropriate elements) in which the satellite base station 1636, the satellite base station 1638 and / or the satellite 1642 are integrated into the RAN 1606.

[0263] In this example, connection 1608 and connection 1610 are air interfaces that enable such communicative coupling and may conform to the RAT, such as LTE and / or NR, used by RAN 1606. It is contemplated that in some embodiments, connection 1608 and connection 1610 may comprise service links between their respective UE 1602, UE 1604 and one or more of satellite base station 1636, satellite base station 1638, and satellite 1642.

[0264] In some implementations, UE 1602 and UE 1604 may also directly exchange communication data via side link interface 1616 .

[0265] UE 1604 is shown as being configured to access an access point (shown as AP 1618) via connection 1620. By way of example, connection 1620 may include a local wireless connection, such as a connection conforming to any IEEE 802.11 protocol, wherein AP 1618 may include In this example, AP 1618 can connect to another network (eg, the Internet) without going through CN 1624.

[0266] In an embodiment, UE 1602 and UE 1604 may be configured to communicate with each other over a multi-carrier communication channel using orthogonal frequency division multiplexing (OFDM) communication signals according to various communication techniques, such as, but not limited to, orthogonal frequency division multiple access (OFDMA) communication techniques (e.g., for downlink communications) or single carrier frequency division multiple access (SC-FDMA) communication techniques (e.g., for uplink and ProSe or sidelink communications), and with terrestrial base station 1612, ground base station 1614, satellite base station 1636, satellite base station 1638, and / or satellite 1642, although the scope of the embodiments is not limited in this respect. The OFDM signal may include multiple orthogonal subcarriers.

[0267] In some embodiments, all or part of ground base station 1612, ground base station 1614, satellite base station 1636 and / or satellite base station 1638 may be implemented as one or more software entities running on a server computer as part of a virtual network.

[0268] In addition or in other embodiments, the ground base station 1612 or the ground base station 1614 can be configured to communicate with each other via the interface 1622. In an embodiment where the wireless communication system 1600 is an LTE system (e.g., when the CN 1624 is an EPC), the interface 1622 can be an X2 interface. The X2 interface can be defined between two or more base stations (e.g., two or more eNBs, etc.) connected to the EPC and / or between two eNBs connected to the EPC. It is contemplated that an inter-satellite link (ISL) can carry the X2 interface between the two satellite base stations.

[0269] In an embodiment where the wireless communication system 1600 is an NR system (e.g., when the CN 1624 is a 5GC), the interface 1622 may be an Xn interface. The Xn interface is defined between two or more base stations connected to the 5GC (e.g., the CN 1624). For example, the Xn interface may be between two or more gNBs connected to the 5GC, between a gNB and an eNB connected to the 5GC, between two eNBs connected to the 5GC, and / or between two or more satellite base stations via an ISL (e.g., as in the interface 1640 between the satellite base station 1636 and the satellite base station 1638).

[0270] RAN 1606 is shown as being communicatively coupled to CN 1624. CN 1624 may include one or more network elements 1626 configured to provide various data and telecommunication services to customers / subscribers (e.g., UE 1602 and users of UE 1604) connected to CN 1624 via RAN 1606. The components of CN 1624 may be implemented in one physical device or separate physical devices including components for reading and executing instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium). For example, the components of CN 1624 may be implemented in one or more processors and / or one or more associated memories.

[0271] In an embodiment, CN 1624 may be an EPC, and RAN 1606 may be connected to CN 1624 via an S1 interface 1628. In an embodiment, S1 interface 1628 may be divided into two parts: an S1 user plane (S1-U) interface, which carries traffic data between ground base station 1612, ground base station 1614, satellite base station 1636 or interface 1640 and a serving gateway (S-GW); and an S1-MME interface, which is a signaling interface between ground base station 1612, ground base station 1614, satellite base station 1636 or interface 1640 and a mobility management entity (MME).

[0272] In an embodiment, CN 1624 may be a 5GC, and RAN 1606 may be connected to CN 1624 via an NG interface 1628. In an embodiment, NG interface 1628 may be divided into two parts: an NG user plane (NG-U) interface, which carries traffic data between ground base station 1612, ground base station 1614, satellite base station 1636, or satellite base station 1638 and a user plane function (UPF); and an S1 control plane (NG-C) interface, which is a signaling interface between ground base station 1612, ground base station 1614, satellite base station 1636, or satellite base station 1638 and an access and mobility management function (AMF).

[0273] Generally speaking, the application server 1630 may be an element that provides applications that use Internet Protocol (IP) bearer resources with the CN 1624 (e.g., packet-switched data services). The application server 1630 may also be configured to support one or more communication services (e.g., VoIP sessions, group communication sessions, etc.) for the UE 1602 and UE 1604 via the CN 1624. The application server 1630 may communicate with the CN 1624 via the IP communication interface 1632.

[0274] Fig.17A system 1700 for performing signaling 1734 between a wireless device 1702 and a RAN device 1718 of a core network connected to a CN device 1736 according to an embodiment disclosed herein is illustrated. The system 1700 can be part of a wireless communication system as described herein. The wireless device 1702 can be, for example, a UE of a wireless communication system. The RAN device 1718 can be, for example, a base station (e.g., an eNB or gNB) of a wireless communication system that is, for example, a ground base station or a satellite base station. In the case where the RAN device 1718 is a ground base station, the RAN device 1718 can communicate with a satellite that directly provides a radio access connection to the UE in the manner described herein. The CN device 1736 can be one or more devices that make up the CN, as described herein.

[0275] The wireless device 1702 may include one or more processors 1704. The processor 1704 may execute instructions to cause various operations of the wireless device 1702 to be performed, as described herein. The processor 1704 may include one or more baseband processors implemented using, for example, a central processing unit (CPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a controller, a field programmable gate array (FPGA) device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.

[0276] The wireless device 1702 may include a memory 1706. The memory 1706 may be a non-transitory computer-readable storage medium storing instructions 1708 (which may include, for example, instructions executed by the processor 1704). The instructions 1708 may also be referred to as program code or a computer program. The memory 1706 may also store data used by the processor 1704 and results calculated by the processor.

[0277] The wireless device 1702 may include one or more transceivers 1710 that may include radio frequency (RF) transmitter and / or receiver circuitry that uses an antenna 1712 of the wireless device 1702 to facilitate signaling (e.g., signaling 1734) transmitted or received by the wireless device 1702 with other devices (e.g., RAN devices 1718) according to a corresponding RAT. In some embodiments, the antenna 1712 may include a mobile parabolic antenna, an omnidirectional phased array antenna, or some other antenna suitable for communicating with a satellite (e.g., as described above in conjunction with Figure 1 UE 110 and Figure 2 UE 208 described above).

[0278] For RAN equipment 1718 as a ground base station, network equipment signaling 1734 may occur on a feeder link between the wireless device 1702 and the satellite and a service link between the satellite and the RAN equipment 1718 (e.g., as combined with Figure 1 For RAN device 1718 as a satellite base station, signaling 1734 may occur over a feeder link between wireless device 1702 and RAN device 1718 (e.g., as described in conjunction with Figure 2 described).

[0279] The wireless device 1702 may include one or more antennas 1712 (e.g., one, two, four, or more). For implementations with multiple antennas 1712, the wireless device 1702 may exploit the spatial diversity of such multiple antennas 1712 to transmit and / or receive multiple different data streams on the same time-frequency resources. This behavior may be referred to as, for example, multiple-input multiple-output (MIMO) behavior (referring to multiple antennas used at each of the transmitting device and the receiving device to implement this aspect). The MIMO transmission performed by the wireless device 1702 may be implemented based on precoding (or digital beamforming) applied at the wireless device 1702, which multiplexes the data streams across the antennas 1712 based on known or assumed channel characteristics, so that each data stream is received with appropriate signal strength relative to the other streams and at a desired location in the spatial domain (e.g., the location of the receiver associated with the data stream). Certain embodiments may use a single-user MIMO (SU-MIMO) approach (where data streams are all directed to a single receiver) and / or a multi-user MIMO (MU-MIMO) approach (where separate data streams may be directed to separate (different) receivers in different locations in the spatial domain).

[0280] In certain embodiments with multiple antennas, the wireless device 1702 may implement analog beamforming techniques whereby the phases of signals transmitted by the antennas 1712 are relatively adjusted to direct the (joint) transmissions of the antennas 1712 (this is sometimes referred to as beam steering).

[0281] The wireless device 1702 may include one or more interfaces 1714. The interfaces 1714 may be used to provide input to or output from the wireless device 1702. For example, a wireless device 1702 that is a UE may include an interface 1714, such as a microphone, a speaker, a touch screen, buttons, etc., to allow a user of the UE to provide input and / or output to the UE. Other interfaces of such a UE may be composed of transmitters, receivers, and other circuits that allow the UE to communicate with other devices (e.g., in addition to the transceiver 1710 / antenna 1712 described above), and may communicate according to known protocols (e.g., etc.) to perform the operation.

[0282] The wireless device 1702 may include a scheduling module 1716. The scheduling module 1716 may be implemented via hardware, software, or a combination thereof. For example, the scheduling module 1716 may be implemented as a processor, circuit, and / or instructions 1708 stored in the memory 1706 and executed by the processor 1704. In some examples, the scheduling module 1716 may be integrated within the processor 1704 and / or the transceiver 1710. For example, the scheduling module 1716 may be implemented by a combination of software components (e.g., executed by a DSP or a general purpose processor) and hardware components (e.g., logic gates and circuits) within the processor 1704 or the transceiver 1710.

[0283] The scheduling module 1716 may be used in various aspects of the present disclosure, for example, Figures 3 to 15 The scheduling module 1716 is configured to, for example, process ultra-compact DCI received at the wireless device 1702 and / or schedule PDSCH.

[0284] The RAN device 1718 may include one or more processors 1720. The processor 1720 may execute instructions to perform various operations of the RAN device 1718 as described herein. The processor 1704 may include one or more baseband processors implemented using, for example, a CPU, a DSP, an ASIC, a controller, an FPGA device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.

[0285] The RAN device 1718 may include a memory 1722. The memory 1722 may be a non-transitory computer-readable storage medium storing instructions 1724 (which may include, for example, instructions executed by the processor 1720). The instructions 1724 may also be referred to as program code or a computer program. The memory 1722 may also store data used by the processor 1720 and results calculated by the processor.

[0286] The RAN device 1718 may include one or more transceivers 1726 that may include RF transmitter and / or receiver circuits that use antennas 1728 of the RAN device 1718 to facilitate signaling (e.g., signaling 1734) transmitted or received by the RAN device 1718 with other devices (e.g., wireless device 1702) in accordance with a corresponding RAT.

[0287] The RAN device 1718 may include one or more antennas 1728 (e.g., one, two, four, or more). In an embodiment with multiple antennas 1728, the RAN device 1718 may perform MIMO, digital beamforming, analog beamforming, beam steering, etc. as described above.

[0288] For RAN equipment 1718 that is a terrestrial base station, one or more of the transceiver 1726 and / or antenna 1728 may alternatively reside on a satellite gateway associated with the base station (e.g., as described in reference to Figure 1 For the RAN device 1718 as a satellite base station, the transceiver 1726 and / or the antenna 1728 may be present on the satellite, and one or more of these antennas 1728 may be antennas suitable for satellite communication (such as mobile parabolic antennas, omnidirectional phased array antennas, etc.).

[0289] The RAN device 1718 may include one or more interfaces 1730. The interface 1730 may be used to provide input to or output from the RAN device 1718. For example, the RAN device 1718 as a base station may include an interface 1730 composed of a transmitter, a receiver and other circuits (e.g., in addition to the transceiver 1726 / antenna 1728 already described), which enables the base station to communicate with other equipment in the CN and / or enables the base station to communicate with external networks, computers, databases, etc., for the purpose of operating, managing and maintaining the base station or other equipment operably connected to the base station.

[0290] The RAN device 1718 may include a scheduling module 1732. The scheduling module 1732 may be implemented via hardware, software, or a combination thereof. For example, the scheduling module 1732 may be implemented as a processor, circuit, and / or instructions 1724 stored in the memory 1722 and executed by the processor 1720. In some examples, the scheduling module 1732 may be integrated within the processor 1720 and / or the transceiver 1726. For example, the scheduling module 1732 may be implemented by a combination of software components (e.g., executed by a DSP or a general purpose processor) and hardware components (e.g., logic gates and circuits) within the processor 1720 or the transceiver 1726.

[0291] The scheduling module 1732 may be used in various aspects of the present disclosure, for example, Figures 3 to 15 The scheduling module 1732 is configured to, for example, generate and / or send ultra-compact DCI and / or schedule PDSCH to be sent by the RAN device 1718.

[0292] RAN device 1718 can communicate with CN device 1736 via interface 1746, which can be similar to Fig.16 Interface 1628 (for example, it can be S1 and / or NG interface, either of which can be divided into user plane and control plane parts).

[0293] The CN device 1736 may include one or more processors 1738. The processor 1738 may execute instructions to perform various operations of the CN device 1736 as described herein. The processor 1738 may include one or more baseband processors implemented using, for example, a CPU, a DSP, an ASIC, a controller, an FPGA device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.

[0294] CN device 1736 may include memory 1740. Memory 1740 may be a non-transitory computer-readable storage medium storing instructions 1742 (which may include, for example, instructions executed by processor 1738). Instructions 1742 may also be referred to as program code or a computer program. Memory 1740 may also store data used by processor 1738 and results calculated by the processor.

[0295] The CN device 1736 may include one or more interfaces 1744. The interfaces 1744 may be used to provide input to or output from the CN device 1736. For example, the CN device 1736 may include an interface 1730 consisting of a transmitter, a receiver, and other circuits that enable the CN device 1736 to communicate with other equipment in the CN, and / or enable the CN device 1736 to communicate with an external network, computer, database, etc., for the purpose of operating, managing, and maintaining the CN device 1736 or other equipment operably connected to the CN device.

[0296] For one or more embodiments, at least one of the components set forth in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, and / or methods as described herein. For example, a baseband processor as described herein in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples set forth herein. For another example, circuits associated with a UE, a base station, a network element, etc. as described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples set forth herein.

[0297] Unless otherwise expressly stated, any of the above embodiments may be combined with any other embodiment (or combination of embodiments). The foregoing description of one or more specific implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise form disclosed. In view of the above teachings, modifications and variations are possible or can be obtained from the practice of various embodiments.

[0298] Embodiments and implementations of the systems and methods described herein may include various operations that may be embodied in machine executable instructions to be executed by a computer system. A computer system may include one or more general or special purpose computers (or other electronic devices). A computer system may include hardware components that include specific logic components for performing operations; or may include a combination of hardware, software, and / or firmware.

[0299] It should be appreciated that the systems described herein include descriptions of specific embodiments. These embodiments may be combined into a single system, partially combined into other systems, separated into multiple systems, or otherwise divided or combined. In addition, it is contemplated that parameters, attributes, aspects, etc. of another embodiment may be used in one embodiment. For clarity, these parameters, attributes, aspects, etc. are described only in one or more embodiments, and it should be appreciated that these parameters, attributes, aspects, etc. may be combined with or substituted for parameters, attributes, aspects, etc. of another embodiment unless expressly stated herein.

[0300] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of the authorized use should be clearly stated to users.

[0301] Although the foregoing has been described in considerable detail for the sake of clarity, it will be apparent that certain changes and modifications may be made without departing from the principles of the invention. It should be noted that there are many alternative ways to implement both the processes and the apparatus described herein. Therefore, the embodiments of the present invention should be regarded as illustrative rather than restrictive, and the specification is not limited to the details given herein, but may be modified within the scope and equivalents of the appended claims.

Claims

1. A method of a user equipment (UE), the method include: A system information block (SIB) is received from a base station, the SIB comprising: first configuration information for ultra-compact downlink control information (DCI); and second configuration information for one or more scheduling physical downlink shared channels (PDSCH); receiving an ultra-compact DCI from the base station, wherein the ultra-compact DCI corresponds to the first configuration information; and The one or more scheduled PDSCHs are received from the base station, wherein the one or more scheduled PDSCHs correspond to the second configuration information.

2. The method according to claim 1, in, The first configuration information for the ultra-compact DCI includes one or more of the following: a resource mapping rule for identifying resources used by the one or more scheduled PDSCHs relative to resources used by the ultra-compact DCI; the number of physical downlink control channel (PDCCH) repetitions carrying the repetitions of the ultra-compact DCI; an indication of one or more fields used in the ultra-compact DCI; and An indication of whether a New Data Indicator (NDI) field is included in the ultra-compact DCI.

3. The method according to claim 1, in, The SIB further includes numerology information of a physical downlink control channel (PDCCH) for carrying the ultra-compact DCI.

4. The method according to claim 1, in, The second configuration information for the one or more scheduled PDSCHs includes one or more of the following: Modulation and coding scheme (MCS) information for the one or more scheduled PDSCHs; A hybrid automatic repeat request (HARQ) process number for the one or more scheduled PDSCHs; A redundancy version (RV) for the scheduled PDSCH; the number of PDSCH repetitions within the one or more scheduled PDSCHs; The maximum number of layers of the one or more scheduled PDSCHs; and The one or more aggregation levels of the scheduled PDSCH.

5. A method of a user equipment (UE), the method include: receiving ultra-compact downlink control information (DCI) from a base station, the ultra-compact DCI including a first field for scheduling one or more scheduled physical downlink shared channels (PDSCHs) for scheduling data PDSCHs; receiving the one or more scheduled PDSCHs from the base station, wherein the one or more scheduled PDSCHs correspond to data of the first field; as well as The data PDSCH scheduled by the one or more scheduling PDSCHs is received from the base station.

6. The method according to claim 5, in, The first field for the one or more scheduled PDSCHs includes one or more of the following: A time domain resource allocation (TDRA) table index field for the one or more scheduled PDSCHs; a frequency domain resource allocation (FDRA) field for the one or more scheduled PDSCHs; a modulation and coding scheme (MCS) field for the one or more scheduled PDSCHs; a redundancy version (RV) field for the one or more scheduled PDSCHs; A Hybrid Automatic Repeat Request (HARQ) process number field for one or more scheduled PDSCHs; a new data indicator (NDI) field for the one or more scheduled PDSCHs; a downlink allocation indicator (DAI) field for the one or more scheduled PDSCHs; as well as A PDSCH repetition number field is used for the one or more scheduled PDSCHs.

7. The method according to claim 6, in, One or more of the MCS field, the RV field, the HARQ process number field, the NDI field, the DAI field, and the PDSCH repetition number field includes fixed data.

8. The method according to claim 5 further includes sending a physical uplink control channel (PUCCH) to the base station, the PUCCH including a first hybrid automatic repeat request (HARQ) acknowledgment (HARQ-ACK) signaling for the one or more scheduled PDSCHs, wherein the ultra-compact DCI further includes a second field of the first HARQ-ACK signaling for the one or more scheduled PDSCHs.

9. The method according to claim 8, in, The second field used for the first HARQ-ACK signaling includes one or more of the following: a PUCCH resource indicator field for the first HARQ-ACK signaling; a transmit power control (TPC) command field for the first HARQ-ACK signaling; and A PDSCH to HARQ feedback timing indicator field is used for the first HARQ-ACK signaling.

10. The method according to claim 9, in, One or more of the PUCCH resource indicator field, the TPC command field, and the PDSCH to HARQ feedback timing indicator field present in the ultra-compact DCI includes fixed data.

11. The method according to claim 8, in, The PUCCH further includes second HARQ-ACK signaling for the data PDSCH.

12. The method according to claim 5, in, The ultra-compact DCI is received in a physical downlink control channel (PDCCH) having cyclic redundancy check (CRC) bits scrambled by one of: Cell Radio Network Temporary Identity (RNTI) (C-RNTI); Configured Scheduling RNTI (CS-RNTI); Modulation and Coding Scheme Cell RNTI (MCS-C-RNTI); Random access RNTI (RA-RNTI); Temporary cell RNTI (TC-RNTI); Paging RNTI (RNTI); and System Information RNTI (SI-RNTI).

13. The method according to claim 5, in, The ultra-compact DCI is received in one or more physical downlink control channel (PDCCH) repetitions.

14. The method according to claim 5, in, The ultra-compact DCI is received in one or more of a plurality of physical downlink control channels (PDCCHs), wherein each of the plurality of PDCCHs is transmitted by a different transmit reception point (TRP).

15. The method according to claim 14, in, Each of the plurality of PDCCHs is associated with a different set of search spaces.

16. The method according to claim 14, in, The plurality of PDCCHs are one or more of time division multiplexed (TDMed), frequency division multiplexed (FDMed), and space division multiplexed (SDMed).

17. The method according to claim 14, in, Each of the plurality of PDCCHs is identical.

18. The method according to claim 5, in, The ultra-compact DCI has a first payload size that is smaller than a second payload size of the compact DCI.

19. The method according to claim 5, in, The ultra-compact DCI is DCI format 1_2.

20. A method of a user equipment (UE), the method include: receiving ultra-compact downlink control information (DCI) from a base station, the DCI including a first field for scheduling one or more physical downlink shared channels (PDSCH) for scheduling a physical uplink shared channel (PUSCH); and receiving the one or more scheduled PDSCHs from the base station, wherein the one or more scheduled PDSCHs correspond to data of the first field; as well as The PUSCH scheduled by the one or more scheduling PDSCHs is sent to the base station.

21. The method according to claim 20, in, The first field for the one or more scheduled PDSCHs includes one or more of the following: A time domain resource allocation (TDRA) table index field for the one or more scheduled PDSCHs; a frequency domain resource allocation (FDRA) field for the one or more scheduled PDSCHs; a modulation and coding scheme (MCS) field for the one or more scheduled PDSCHs; a redundancy version (RV) field for the one or more scheduled PDSCHs; A Hybrid Automatic Repeat Request (HARQ) process number field for one or more scheduled PDSCHs; a new data indicator (NDI) field for the one or more scheduled PDSCHs; a downlink allocation indicator (DAI) field for the one or more scheduled PDSCHs; and The PDSCH repetition number field within the one or more scheduled PDSCHs.

22. The method according to claim 21, in, One or more of the MCS field, the RV field, the HARQ process number field, the NDI field, the DAI field, and the PDSCH repetition number field present in the ultra-compact DCI includes fixed data.

23. The method according to claim 20, in, The ultra-compact DCI further includes a transmit power control (TPC) command for the PUSCH.

24. The method of claim 20, further comprising sending a physical uplink control channel (PUCCH) to the base station, the PUCCH comprising a hybrid automatic repeat request (HARQ) acknowledgment (HARQ-ACK) signaling for the one or more scheduled PDSCHs, wherein the ultra-compact DCI further comprises a second field for the HARQ-ACK signaling.

25. The method according to claim 24, in, The second field used for the HARQ-ACK signaling includes one or more of the following: a PUCCH resource indicator field for the HARQ-ACK signaling; a transmit power control (TPC) command field for the HARQ-ACK signaling; and A PDSCH to HARQ feedback timing indicator field is used for the HARQ-ACK signaling.

26. The method according to claim 25, in, One or more of the PUCCH resource indicator field, the TPC command field, and the PDSCH to HARQ feedback timing indicator field present in the ultra-compact DCI includes fixed data.

27. The method according to claim 20, in, The ultra-compact DCI is received in a physical downlink control channel (PDCCH) having cyclic redundancy check (CRC) bits scrambled by one of: Cell Radio Network Temporary Identity (RNTI) (C-RNTI); Configured Scheduling RNTI (CS-RNTI); Modulation and Coding Scheme Cell RNTI (MCS-C-RNTI); Random access RNTI (RA-RNTI); Temporary cell RNTI (TC-RNTI); Paging RNTI (RNTI); and System Information RNTI (SI-RNTI).

28. The method according to claim 20, in, The ultra-compact DCI is received in one or more physical downlink control channel (PDCCH) repetitions.

29. The method according to claim 20, in, The ultra-compact DCI is received in one or more of a plurality of physical downlink control channels (PDCCHs), wherein each of the plurality of PDCCHs is transmitted by a different transmit reception point (TRP).

30. The method according to claim 29, in, Each of the plurality of PDCCHs is associated with a different set of search spaces.

31. The method according to claim 29, in, The plurality of PDCCHs are one or more of time division multiplexed (TDMed), frequency division multiplexed (FDMed), and space division multiplexed (SDMed).

32. The method according to claim 29, in, Each of the plurality of PDCCHs is identical.

33. The method according to claim 20, in, The ultra-compact DCI has a first payload size that is smaller than a second payload size of the compact DCI.

34. The method according to claim 20, in, The ultra-compact DCI is DCI format 1_2.

35. An apparatus comprising means for performing the method according to any one of claims 1 to 34.

36. A computer-readable medium comprising instructions, which, when executed by one or more processors of an electronic device, cause the electronic device to perform the method according to any one of claims 1 to 34.

37. An apparatus comprising logic components, modules or circuits for performing the method of any one of claims 1 to 34.

Images