Scheduling physical downlink shared channel design for non-terrestrial network enhancements
Ultra-compact DCI and scheduled PDSCHs with repetitions address NTN challenges, enhancing downlink coverage and network throughput by simplifying control signaling and improving data transmission efficiency.
Patent Information
- Application Number
- CN202380036313.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-04-28
- Filing Date
- 2023-04-27
- Publication Date
- 2024-12-06
AI Technical Summary
Wireless communication systems in non-terrestrial networks (NTN) face challenges due to large propagation delays and power flux density restrictions, leading to inadequate downlink coverage and increased loss of downlink control channel signaling, which affects overall network throughput.
The use of ultra-compact DCI and scheduled PDSCHs to simplify downlink control information, reducing payload size and enhancing PDSCH coverage by incorporating PDSCH repetitions, along with HARQ-ACK signaling through PUCCH, to improve data transmission efficiency in NTN environments.
Enhances downlink coverage and reduces the impact of PDCCH-related bottlenecks, improving network throughput and reliability in NTN systems by ensuring successful data transmission and acknowledgment.
Smart Images

Figure CN119096491A_ABST
Abstract
Description
Technical Field
[0001] The present application generally relates to wireless communication systems, including wireless communication systems using ultra-compact DCI and / or one or more physical downlink shared channels (PDSCHs) for scheduling PDSCHs and / or physical uplink shared channels (PUSCHs) 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) (often referred to by industry groups as Wi-Fi). ® ).
[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 called user equipment (UE). The 3GPP RAN 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 simply 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] A base station 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 often 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 (also sometimes referred to as a gNodeB or gNB).
[0006] The RAN provides its communication services together with external entities through its connection with the Core Network (CN). For example, E-UTRAN may utilize the Evolved Packet Core (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 action, 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.11 A method of a UE according to an implementation scheme is illustrated.
[0019] Fig.12 A method of a base station according to an embodiment is illustrated.
[0020] Fig.13 An example architecture of a wireless communication system according to embodiments disclosed herein is illustrated.
[0021] Fig.14 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
[0022] Various embodiments are described with reference to UE. However, reference to 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, UE as described herein is used to represent any suitable electronic component.
[0023] 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 terrestrial base station 104, a satellite gateway 106, a satellite 108, and a UE 110. The terrestrial base station 104, the satellite gateway 106, and the satellite 108 may be included in a RAN 112.
[0024] 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.
[0025] 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, CN link 114 connecting CN 102 and ground base station 104 may include an NG interface.
[0026] The NTN architecture 100 illustrates a "bent pipe" or "transparent" satellite-based architecture. 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.
[0027] exist Figure 1 In the illustrated embodiment, the ground base station 104 is shown without the capability of directly communicating with the UE on the ground wirelessly. 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.13 of ground base station 1312 and ground base station 1314).
[0028] 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.
[0029] 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.
[0030] 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.
[0031] The NTN architecture 200 implements a "regenerative" satellite-based architecture. In such a regenerative system, base station functions 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.
[0032] 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.
[0033] 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 alleviate 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 (e.g.) 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.
[0034] 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.
[0035] 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 The values of these PFD calculation factors may depend on whether the satellite is a GSO satellite or a non-GSO satellite. Appropriate values of the PFD calculation factors may be relative to the angle of arrival above the horizontal plane (relative to a location on the Earth's surface) δ (in degrees) is applied in a defined manner to achieve the PFD limit.
[0036] For example, a satellite in geostationary orbit (GSO) might correspond to a PFD calculation factor of P = -146dB(W / m 2 ) (4kHz) or -128dB (W / m 2 ) (1MHz), and r = 0.5dB / degree, while satellites in non-GSO may correspond to the parameter P = -144dB(W / m 2 ) (4kHz) or -126dB (W / m 2 ) (1MHz), and r = 0.65 dB / degree. In some areas, satellites in non-GSO may instead use the 4 kHz P = -142.5dB(W / m 2 ), and -124.5dB (W / m 2 ).
[0037] Then, based on the applicable satellite information, use the appropriate PFD calculation factor P and r , the following formula can be used based on the applicable distance between the UE position and the satellite δ Calculate the PFD limits relative to the satellite:
[0038] PFD = P , for 0°≤ δ≤5°;
[0039] PFD = P + r ( δ - 5), for 5°≤ δ ≤25°; and
[0040] PFD = P + 20 r , for 25°≤ δ ≤90°.
[0041] Within such calculated PFD constraints, it is likely 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.
[0042] 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.
[0043] 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.
[0044] 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.
[0045] 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.
[0046] 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).
[0047] Figure 4 A 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.
[0048] 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.
[0049] Therefore, the UE may send data on the PUSCH 404 at the time / frequency resources indicated for the PUSCH 404 in the DCI 402 .
[0050] Figure 3 and Figure 4 The process of may 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 may 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 procedure described may be beneficial.
[0051] For example, to address NTN related issues of additional signaling propagation time and / or distance and / or PFD limitations, it has been determined that the PDSCH coverage provided by satellites of the NTN may be improved by using a (relatively large number of) PDSCH repetitions.
[0052] 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 negative impact on the overall network throughput.
[0053] 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".
[0054] 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 be present 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).
[0055] 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.
[0056] 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.
[0057] 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.
[0058] 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.
[0059] 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 of the HARQ data PDSCH / PUSCH / PUCCH at the UE (as the case may be).
[0060] 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.
[0061] 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, the ultra-compact DCI 502 schedules one or more scheduled PDSCHs 504).
[0062] 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).
[0063] 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.
[0064] 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).
[0065] 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.
[0066] 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.
[0067] 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.
[0068] 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.
[0069] 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 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.
[0070] 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.
[0071] 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.
[0072] like Figure 6 As shown in schematic diagram 600, any one of the ultra-compact DCI 502 and one or more scheduled PDSCHs 504 (or any combination of any of these) provides 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 ultra-compact DCI 502 and / or one or more scheduled PDSCHs 504 scheduled PUCCH 602).
[0073] 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 scheduled PDSCHs 504.
[0074] 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.
[0075] 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.
[0076] 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).
[0077] 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).
[0078] 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.
[0079] 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).
[0080] 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.
[0081] 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.
[0082] 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.
[0083] The SIB can be Figure 7 The base station of the dynamic resource grant process (eg, sending 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.
[0084] 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.
[0085] 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.
[0086] like Figure 8 As shown in schematic diagram 800, any one of the ultra-compact DCI 702 and one or more scheduled PDSCHs 704 (or any combination of any of these) provides 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 ultra-compact DCI 702 and / or one or more scheduled PDSCHs 704 are scheduled PUCCH 802).
[0087] 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 scheduled PDSCHs 704.
[0088] 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.
[0089] Scheduling PDSCH design for downlink data transmission scheduling
[0090] An implementation of scheduling PDSCH design in the case of scheduling DL data transmission is now discussed.
[0091] One or more scheduled PDSCHs for scheduling DL data transmission on the data PDSCH may include a MAC CE including scheduling information of the data PDSCH.
[0092] One or more scheduling PDSCHs may include one or more fields related to the data PDSCH for DL transmission. These fields may indicate to the UE the manner in which the data PDSCH is received and / or decoded. Thus, the UE may determine the scheduling of the data PDSCH so that it can subsequently receive the data PDSCH.
[0093] The field for the data PDSCH in one or more scheduled PDSCHs may include a time domain resource allocation (TDRA) table index field for the data PDSCH. The TDRA table index field may correspond to a TDRA table configured specifically for use with the scheduled PDSCH. The index provided by the TDRA table index field may reference an entry in the TDRA table, which includes K3 Information field (which is the time gap between the last of one or more scheduling PDSCHs and the data PDSCH K3 associated), one or more of the mappingType field, startSymbolAndLength field and / or the repetitionNumber field.
[0094] The field of the data PDSCH in the one or more scheduled PDSCHs may include a frequency domain resource allocation (FDRA) field for the data PDSCH. The FDRA field may be configured to indicate a bitmap or a (starting resource block (RB), length of the RB) pair in its field data.
[0095] The field of the data PDSCH in the one or more scheduling PDSCHs may include a modulation and coding scheme (MCS) field for the data PDSCH.
[0096] The field of the data PDSCH in the one or more scheduled PDSCHs may include a hybrid automatic repeat request (HARQ) process number field for the data PDSCH.
[0097] The field of the data PDSCH in the one or more scheduling PDSCHs may include a redundancy version (RV) field for the data PDSCH.
[0098] The field of the data PDSCH in the one or more scheduled PDSCHs may include a new data indicator (NDI) field for the data PDSCH.
[0099] The field of the data PDSCH in the one or more scheduling PDSCHs may include a downlink allocation indicator (DAI) field for the data PDSCH.
[0100] The field for the data PDSCH in the one or more scheduled PDSCHs may include a virtual resource block (VRB) to physical resource block (PRB) mapping field for the data PDSCH.
[0101] The field of the data PDSCH in the one or more scheduled PDSCHs may include a demodulation reference signal (DMRS) port field for the data PDSCH. This field may be present in case of supporting multi-layer transmission of the one or more scheduled PDSCHs.
[0102] The field of the data PDSCH in the one or more scheduling PDSCHs may include a transport block (TB) number field. This may support the use of more than one data PDSCH on more than one TB, which is possible in some embodiments.
[0103] One or more scheduled PDSCHs may include one or more fields related to HARQ-ACK signaling for the data PDSCH. As described herein, in some embodiments, the UE sends a PUCCH including HARQ-ACK signaling for the data PDSCH in response to its reception of the data PDSCH. 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. These fields may be present in the same MAC CE of one or more scheduled PDSCHs that include one or more fields related to the data PDSCH.
[0104] The field for HARQ-ACK signaling for the data PDSCH may include a PUCCH resource indicator field for HARQ-ACK signaling.
[0105] The field for HARQ-ACK signaling of the data PDSCH may include a transmit power control (TPC) command field for the HARQ-ACK signaling.
[0106] The field for HARQ-ACK signaling for the data PDSCH may include a PDSCH to HARQ feedback timing indicator field for HARQ-ACK signaling.
[0107] The UE may understand that there is a time gap between one or more scheduling PDSCHs and the data PDSCHs scheduled by the one or more scheduling PDSCHs. K3 The time gap K3 It can be equivalent to the "offset K3" described in this article. K3 The value of may be large (e.g., relative to the minimum offset applied between a DCI and a PDSCH directly scheduled by the DCI without using ultra-compact DCI / one or more scheduled PDSCHs).K0 ). Large-sized time gaps K3 Sufficient time may be allowed to allow decoding and / or processing of one or more scheduled PDSCHs (e.g., in the case where PDSCH repetition is used and therefore there are multiple PDSCHs in one or more scheduled PDSCHs, sufficient decoding and / or processing time may be allowed). K3 Indicator to identify the time gap to the UE K3 .
[0108] Time gap K3 There may be minimum constraints. For example, it may be possible that the time gap K3 should be large enough to take into account the minimum processing time of the UE to decode one or more scheduled PDSCHs, which can be expressed as T proc,3 Furthermore, the time gap K3 The round-trip time (RTT) from the UE to the base station should also be considered.
[0109] Operated at UE T proc,3 The value of may depend on the capabilities of the UE. T proc,3 The value of may include / take into account, for example, a MAC CE decoding delay corresponding to decoding of one or more MAC CEs scheduling PDSCHs (e.g., a delay in decoding one or more MAC CEs scheduling PDSCHs at the MAC layer, beyond an initial physical layer decoding of one or more scheduling PDSCHs).
[0110] Determine the time gap at the UE K3 In a first implementation, it is possible that the UE knows the time gap K3 The basic gap portion corresponds to the timing reference point factor of the UE to base station communication. The basic gap can be expressed as K Offset+ Kmac ,in K The offset is the first amount of time that ensures signaling causality between the UE and a signaling timing reference point (which may be on a satellite, for example) used for UE-to-base station signaling, and where Kmac is a second amount of time that takes into account the delay between the base station and the signaling timing reference point.
[0111] The UE may then send a basic gap amount (e.g., K Offset+ Kmac )Add additional offset ( AO value). AO The value can be equal to or greater than the UE's T proc,3The AO value may also take into account the RTT factor between the UE and the base station (which may be useful, for example, if the time of any HARQ-ACK signaling of one or more scheduled PDSCHs to be used / expected by the base station needs to be taken into account). Corresponding to the first embodiment, the AO value from the base station K3 The instructions may include the AO value.
[0112] Upon receiving the K3 When indicated, the UE can use K Offset +Kmac + AO Calculate time gap K3 .
[0113] Determine the time gap at the UE K3 In a second embodiment, K3 The indication may include the direct frame number (DFN) and the time gap K3 For example, the time slot may be the time slot index of the time slot after K3 The first time slot that occurs after that.
[0114] In some embodiments, it is possible that one or more scheduled PDSCHs may include some application layer / user data.
[0115] When one or more scheduled PDSCHs comprise PDSCH repetitions, it is possible that the number of PDSCH repetitions is predefined or fixed at the UE.
[0116] In some cases, it is possible that the number of repetitions is configured by a SIB received at the UE. In such cases, it is possible that SIB1 as understood in the definition of some wireless communication systems provides this information; in other cases, a NTN-specific SIB format may be used to provide this information. In the definition of certain types of wireless communication systems, this NTN-specific SIB format may be designated as a SIB.
[0117] In some cases, it is possible that the number of repetitions may be dynamically indicated in an ultra-compact DCI that schedules one or more scheduled PDSCHs. In some such cases, a field in the ultra-compact DCI may indicate the number of PDSCH repetitions. In some such cases, the TDRA entry indicated in the ultra-compact DCI may be understood by the UE as corresponding to a specific number of PDSCH repetitions.
[0118] It is possible that the ultra-compact DCI does not contain values related to the reception and / or decoding method of one or more scheduled PDSCHs scheduled by the ultra-compact DCI. For example, the ultra-compact DCI may omit fields for these values and / or may use fixed values for this information (in order to facilitate decoding of the ultra-compact DCI).
[0119] In such a case, it can be understood that within the wireless communication system, in order to perform reception and / or decoding of one or more scheduled PDSCHs, the UE can use predefined values of this information and / or can receive these values from another source.
[0120] Therefore, one or more scheduled PDSCHs may be received according to a predefined MCS value and a predefined MCS table. For example, the UE may use MCS = 0 in MCS table 1 or MCS table 3 to cover low signal-to-noise ratio (SNR) situations. Alternatively, one or more of the radio resource control (RRC) configuration and the SIB may provide the UE with a configured MCS value and a configured MCS table for use.
[0121] Further, it is possible to receive one or more scheduled PDSCHs according to a predefined redundancy version (RV) value. For example, the UE may use RV = 0. Alternatively, one or more of the RRC configuration and the SIB may provide the UE with a configured RV value for use.
[0122] Further, it is possible to receive one or more scheduled PDSCHs according to a predefined HARQ process number. For example, the UE may use HARQ process number = 0. Alternatively, one or more of the RRC configuration and the SIB may provide the UE with a configured HARQ process number for use. Such a HARQ process may be configured when HARQ feedback between the UE and the base station is enabled.
[0123] Further, it is possible to receive one or more scheduled PDSCHs according to a predefined NDI value. In such a case, there may be no need to combine with a previous scheduled PDSCH transmission.
[0124] Further, it is possible to receive one or more scheduled PDSCHs according to a predefined DAI value. In such a case, it is possible to use dedicated HARQ-ACK resources for one or more scheduled PDSCHs.
[0125] Fig. 9 A method 900 of a UE according to an embodiment is illustrated. The method 900 includes receiving 902 an ultra-compact DCI scheduling one or more scheduled PDSCHs from a base station.
[0126] The method 900 further includes receiving 904 one or more scheduling PDSCHs from a base station, the one or more scheduling PDSCHs including a MAC CE having a first field for a data PDSCH.
[0127] The method 900 further includes decoding 906 a MAC CE from one or more scheduled PDSCHs.
[0128] The method 900 further includes receiving 908 a data PDSCH from a base station, wherein the data PDSCH corresponds to data of the first field.
[0129] In some embodiments of method 900, the first field for data PDSCH includes one or more of the following: a TDRA table index field for data PDSCH, a FDRA field for data PDSCH, an MCS field for data PDSCH, a HARQ process number field for data PDSCH, an RV field for data PDSCH, an NDI field for data PDSCH, a DAI field for data PDSCH, a VRB to PRB mapping field for data PDSCH, a DMRS port field for data PDSCH, and a TB number field for data PDSCH.
[0130] In some embodiments, the method 900 further includes sending a PUCCH including first HARQ-ACK signaling for a data PDSCH to the base station, wherein the MAC CE further includes a second field for the HARQ-ACK signaling for the data PDSCH. 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.
[0131] In some embodiments of method 900, the MAC CE includes a method for K3 To schedule data PDSCH K3 Indicates the time gap K3 is the amount of time between one or more scheduling PDSCHs and a data PDSCH that is greater than the RTT used for signaling between the UE and the base station. In some of these embodiments, K3 Indicates that an additional offset value is included AO , and the time gap K3 equal K offset + Kmac + AO ,in KOffsetis the first amount of time that ensures signaling causality between the UE and the signaling timing reference point used for UE-to-base station signaling, Kmac is a second amount of time that takes into account the delay between the base station and the signaling timing reference point, and AO Is equal to or greater than the processing time of the UE to decode the MACCE from one or more scheduled PDSCHs T proc,3 In some of these embodiments, K3 Indication includes DFN and time gap K3 The slot index of the following slot.
[0132] In some embodiments of method 900, one or more scheduled PDSCHs include application layer data.
[0133] In some embodiments of the method 900, the number of PDSCH repetitions in the one or more scheduled PDSCHs is one of: predefined at the UE, configured by a SIB received at the UE, and indicated by an ultra-compact DCI.
[0134] In some embodiments of method 900, one or more scheduled PDSCHs are received according to one or more of the following: a predefined MCS value and a predefined MCS table, or a configured MCS value and a configured MCS table, each configured MCS value and configured MCS table being configured in one or more of an RRC configuration and a SIB; a predefined RV value, or a configured RV value configured in one or more of the RRC configuration and the SIB; a predefined HARQ process number, or a configured HARQ process number configured in one or more of the RRC configuration and the SIB; a predefined NDI value; and a predefined DAI value.
[0135] 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 1402 as a UE, as described herein).
[0136] 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 1406 of wireless device 1402 as a UE, as described herein).
[0137] 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 1402 as a UE, as described herein).
[0138] 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 of a UE (such as wireless device 1402 as a UE, as described herein).
[0139] Embodiments contemplated herein include signals as described in or in connection with one or more elements of method 900 .
[0140] 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 1404 of wireless device 1402 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 1406 of wireless device 1402 as a UE, as described herein).
[0141] Fig.10 A method of a base station according to an embodiment is illustrated. The method 1000 includes sending 1002 an ultra-compact DCI scheduling one or more scheduling PDSCHs to a UE.
[0142] The method 1000 further includes sending 1004 one or more scheduling PDSCHs to the UE, the one or more scheduling PDSCHs including a MAC CE having a first field for a data PDSCH.
[0143] The method 1000 further includes sending 1006 a data PDSCH to the UE, wherein the data PDSCH corresponds to data of the first field.
[0144] In some embodiments of method 1000, the first field for data PDSCH includes one or more of the following: a TDRA table index field for data PDSCH, a FDRA field for data PDSCH, an MCS field for data PDSCH, a HARQ process number field for data PDSCH, an RV field for data PDSCH, an NDI field for data PDSCH, a DAI field for data PDSCH, a VRB to PRB mapping field for data PDSCH, a DMRS port field for data PDSCH, and a TB number field for data PDSCH.
[0145] In some embodiments, the method 1000 further includes receiving a PUCCH including first HARQ-ACK signaling for a data PDSCH from the UE, wherein the MAC CE further includes a second field for the HARQ-ACK signaling for the data PDSCH. 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.
[0146] In some embodiments of method 1000, the MAC CE includes a method for K3 To schedule data PDSCH K3 Indicates the time gap K3 is the amount of time between one or more scheduling PDSCHs and a data PDSCH that is greater than the RTT used for signaling between the UE and the base station. In some of these embodiments, K3 Indicates that an additional offset value is included AO , and the time gap K3 equal K offset + Kmac + AO ,in KOffset is the first amount of time that ensures signaling causality between the UE and the signaling timing reference point used for UE-to-base station signaling, Kmac is a second amount of time that takes into account the delay between the base station and the signaling timing reference point, and AO Is equal to or greater than the processing time of the UE to decode the MAC CE from one or more scheduled PDSCHs T proc,3 In some of these embodiments, K3 Indication includes DFN and time gap K3 The slot index of the following slot.
[0147] In some embodiments of method 1000, one or more scheduled PDSCHs include application layer data.
[0148] In some embodiments of the method 1000, the number of PDSCH repetitions in the one or more scheduled PDSCHs is one of: predefined at the UE, configured by a SIB received at the UE, and indicated by an ultra-compact DCI.
[0149] In some embodiments of method 1000, the UE receives one or more scheduled PDSCHs based on one or more of the following: a predefined MCS value and a predefined MCS table, or a configured MCS value and a configured MCS table, each configured MCS value and configured MCS table being configured to the UE in one or more of the RRC configuration and the SIB; a predefined RV value, or a configured RV value configured to the UE in one or more of the RRC configuration and the SIB; a predefined HARQ process number, or a configured HARQ process number configured in one or more of the RRC configuration and the SIB; a predefined NDI value; and a predefined DAI value.
[0150] 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 1418 as a base station, as described herein).
[0151] 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. The non-transitory computer-readable medium may be, for example, a memory of a base station (such as memory 1422 of RAN device 1418 as a base station, as described herein).
[0152] 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 1418 as a base station, as described herein).
[0153] 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 1418 as a base station, as described herein).
[0154] Embodiments contemplated herein include signals as described in or in connection with one or more elements of method 1000 .
[0155] 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 1420 of RAN device 1418 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 1422 of RAN device 1418 as a base station, as described herein).
[0156] Scheduling PDSCH design for uplink data transmission scheduling
[0157] An implementation scheme for scheduling PDSCH design in the case of scheduling UL data transmission is now discussed.
[0158] One or more scheduled PDSCHs for scheduling UL data transmission on the PUSCH may include a MAC CE including scheduling information of the PUSCH.
[0159] One or more scheduled PDSCHs may include one or more fields related to the PUSCH for UL transmission. These fields may indicate to the UE the manner in which the PUSCH is encoded and / or transmitted. Thus, the UE may be enabled to transmit the PUSCH at a timing and manner that is expected / receivable by the base station.
[0160] The field for PUSCH in one or more scheduled PDSCHs may include a TDRA table index field for PUSCH. The TDRA table index field may correspond to a TDRA table configured specifically for use with the scheduled PDSCH. The index provided by the TDRA table index field may reference an entry in the TDRA table, which includes K4 Information field (which is the time gap between the last of one or more scheduled PDSCHs and the PUSCH K4 associated), one or more of the mappingType field, startSymbolAndLength field and / or the repetitionNumber field.
[0161] The field for PUSCH in one or more scheduled PDSCHs may include a FDRA field for PUSCH. The FDRA field may be configured to indicate a bitmap or a (start RB, length of RB) pair in its field data.
[0162] The fields for PUSCH in one or more scheduled PDSCHs may include a frequency hopping flag field for PUSCH.
[0163] The fields for PUSCH in one or more scheduled PDSCHs may include an MCS field for PUSCH.
[0164] The fields for PUSCH in one or more scheduled PDSCHs may include a HARQ process number field for PUSCH.
[0165] The fields for PUSCH in one or more scheduled PDSCHs may include an RV field for PUSCH.
[0166] The fields for PUSCH in one or more scheduled PDSCHs may include an NDI field for PUSCH.
[0167] The fields for PUSCH in one or more scheduled PDSCHs may include a DAI field for PUSCH.
[0168] The fields for PUSCH in one or more scheduled PDSCHs may include a DMRS port field for PUSCH.
[0169] The fields for PUSCH in one or more scheduled PDSCHs may include precoding information and a layer number indicator field for PUSCH.
[0170] The fields for the PUSCH in the one or more scheduled PDSCHs may include a sounding reference signal (SRS) resource indicator field for the PUSCH.
[0171] The UE may understand that there is a time gap between one or more scheduled PDSCHs and the PUSCH scheduled by the one or more scheduled PDSCHs. K4 The time gap K4 It can be equivalent to the "offset K4" described in this article. K4 Indicator to identify the time gap to the UE K4 .
[0172] Time gap K4 There may be minimum constraints. For example, it is possible that the time gap K4 should be large enough to take into account the minimum processing time of the UE to decode one or more scheduled PDSCHs, which can be expressed as T proc,4 .
[0173] Operated at UE T proc,4 The value of may depend on the capabilities of the UE. Tproc,4 The value of may include / take into account, for example, the MAC CE decoding delay corresponding to the decoding of one or more MAC CEs scheduling PDSCHs (e.g., the delay in decoding one or more MAC CEs scheduling PDSCHs at the MAC layer, beyond the initial physical layer decoding of PDSCH).
[0174] Determine the time gap at the UE K4 In the first implementation, it is possible that the UE may know the time gap K4 The basic gap portion corresponds to the processing time of one or more MAC CEs scheduling PDSCH at the UE.
[0175] The UE may then add an additional offset to the basic gap amount ( AO value). AO The value can be equal to or greater than the UE's T proc,4 The AO value may also take into account the RTT factor between the UE and the base station (which may be useful, for example, if the time of any HARQ-ACK signaling of one or more scheduled PDSCHs to be used / expected by the base station needs to be taken into account). Corresponding to the first embodiment, the AO value from the base station K4 The instructions may include the AO value.
[0176] Upon receiving the K4 When indicated, the UE can calculate the basic gap + AO Time gap K4 .
[0177] Determine the time gap at the UE K4 In a second embodiment, K4 Indications may include DFN and time gap K4 For example, the time slot may be the time slot index of the time slot after K4 The first time slot that occurs after that.
[0178] When one or more scheduled PDSCHs comprise PDSCH repetitions, it is possible that the number of PDSCH repetitions is predefined or fixed at the UE.
[0179] In some cases, it is possible that the number of repetitions is configured by a SIB received at the UE. In such cases, it is possible that SIB1 as understood in the definition of some wireless communication systems provides this information; in other cases, a NTN-specific SIB format may be used to provide this information. In the definition of certain types of wireless communication systems, this NTN-specific SIB format may be designated as a SIB.
[0180] In some cases, it is possible that the number of repetitions may be dynamically indicated in an ultra-compact DCI that schedules one or more scheduled PDSCHs. In some such cases, a field in the ultra-compact DCI may indicate the number of PDSCH repetitions. In some such cases, the TDRA entry indicated in the ultra-compact DCI may be understood by the UE as corresponding to a specific number of PDSCH repetitions.
[0181] It is possible that the ultra-compact DCI does not contain values related to the reception and / or decoding method of one or more scheduled PDSCHs scheduled by the ultra-compact DCI. For example, the ultra-compact DCI may omit fields for these values and / or may use fixed values for this information (in order to facilitate decoding of the ultra-compact DCI).
[0182] In such a case, it can be understood that within the wireless communication system, in order to perform reception and / or decoding of one or more scheduled PDSCHs, the UE can use predefined values of this information and / or can receive these values from another source.
[0183] Therefore, one or more scheduled PDSCHs may be received according to a predefined MCS value and a predefined MCS table. For example, the UE may use MCS = 0 in MCS table 1 or MCS table 3 to cover the low SNR situation. Alternatively, one or more of the RRC configuration and the SIB may provide the UE with a configured MCS value and a configured MCS table for use.
[0184] Further, it is possible to receive one or more scheduled PDSCHs according to a predefined RV value. For example, the UE may use RV = 0. Alternatively, one or more of the RRC configuration and the SIB may provide the UE with a configured RV value for use.
[0185] Further, it is possible to receive one or more scheduled PDSCHs according to a predefined HARQ process number. For example, the UE may use HARQ process number = 0. Alternatively, one or more of the RRC configuration and the SIB may provide the UE with a configured HARQ process number for use. Such a HARQ process may be configured when HARQ feedback between the UE and the base station is enabled.
[0186] Further, it is possible to receive one or more scheduled PDSCHs according to a predefined NDI value. In such a case, there may be no need to combine with a previous scheduled PDSCH transmission.
[0187] Further, it is possible to receive one or more scheduled PDSCHs according to a predefined DAI value. In such a case, it is possible to use dedicated HARQ-ACK resources for one or more scheduled PDSCHs.
[0188] In some cases, the UE may be configured to send feedback about one or more scheduled PDSCHs in the form of HARQ-ACK signaling in the PUCCH. In such a case, it is possible that the HARQ-ACK signaling includes an ACK to indicate that the UE has successfully received and decoded one or more scheduled PDSCHs, so it will use the PUSCH resources allocated by the one or more scheduled PDSCHs. Further, it is possible that the HARQ-ACK signaling includes a NACK to indicate a failure to receive and / or decode one or more scheduled PDSCHs, so it will not use the PUSCH resources allocated by one or more scheduled PDSCHs. It should be noted that HARQ-ACK signaling will not be sent in the case where the UE is unaware of the transmission of one or more scheduled PDSCHs. When the base station fails to receive such expected HARQ-ACK signaling, it can infer that the PUSCH resources allocated by one or more scheduled PDSCHs will not be used by the UE.
[0189] The PUCCH including such HARQ-ACK signaling may further include channel state information (CSI) parameters for the PUSCH. For example, the PUCCH may indicate the MCS and / or the number of layers associated with the PUSCH, etc.
[0190] Fig.11 A method 1100 of a UE according to an embodiment is illustrated. The method 1100 includes receiving 1102 an ultra-compact DCI scheduling one or more scheduled PDSCHs from a base station.
[0191] The method 1100 further includes receiving 1104 one or more scheduled PDSCHs from a base station, the one or more scheduled PDSCHs including a MAC CE having a first field for a PUSCH.
[0192] The method 1100 further includes decoding 1106 a MAC CE from one or more scheduled PDSCHs.
[0193] The method 1100 further includes sending 1108 a PUSCH to the base station, wherein the PUSCH corresponds to data of the first field.
[0194] In some embodiments of method 1100, the first field for PUSCH includes one or more of the following: a TDRA table index field for PUSCH, a FDRA field for PUSCH, a frequency hopping flag field for PUSCH, an MCS field for PUSCH, a HARQ process number field for PUSCH, an RV field for PUSCH, an NDI field for PUSCH, a DAI field for PUSCH, a DMRS port field for PUSCH, a precoding information and layer number indicator field for PUSCH, and an SRS resource indicator field for PUSCH.
[0195] In some embodiments of the method 1100, the MAC CE includes a method for K4 To schedule PUSCH K4 Indicates the time gap K4 is the amount of time between one or more scheduled PDSCHs and PUSCHs that is greater than the MAC CE processing time of the MAC CE. In some of these embodiments, K4 The indication includes a processing time equal to or greater than the UE decoding one or more scheduled PDSCHs T proc,4 Additional offset value, and time gap K4 is equal to the MAC CE processing time plus an additional offset value. In some of these embodiments, K4 Indications include DFN and time gap K4 The slot index of the following slot.
[0196] In some embodiments of the method 1100, the number of PDSCH repetitions in the one or more scheduled PDSCHs is one of: predefined at the UE, configured by a SIB received at the UE, and indicated by an ultra-compact DCI.
[0197] In some embodiments of method 1100, one or more scheduled PDSCHs are received according to one or more of the following: a predefined MCS value and a predefined MCS table, or a configured MCS value and a configured MCS table, each configured MCS value and configured MCS table configured in one or more of the RRC configuration and the SIB; a predefined RV value, or a configured RV value configured in one or more of the RRC configuration and the SIB; a predefined HARQ process number, or a configured HARQ process number configured in one or more of the RRC configuration and the SIB; a predefined NDI value; and a predefined DAI value.
[0198] In some embodiments, method 1100 further includes sending a PUCCH to the base station, the PUCCH including HARQ-ACK signaling for one or more scheduled PDSCHs and CSI parameters for the PUSCH.
[0199] Embodiments contemplated herein include an apparatus comprising means for performing one or more elements of the method 1100. The apparatus may be, for example, an apparatus that is a UE (such as the wireless device 1402 as a UE, as described herein).
[0200] 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 1100. The non-transitory computer-readable medium may be, for example, a memory of a UE (such as memory 1406 of wireless device 1402 as a UE, as described herein).
[0201] Embodiments contemplated herein include an apparatus including logical components, modules, or circuits for performing one or more elements of the method 1100. The apparatus may be, for example, an apparatus of a UE (such as the wireless device 1402 as a UE, as described herein).
[0202] 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 1100. The apparatus may be, for example, an apparatus of a UE (such as wireless device 1402 as a UE, as described herein).
[0203] Embodiments contemplated herein include a signal as described in or associated with one or more elements of method 1100 .
[0204] 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 1100. The processor may be a processor of a UE (such as the processor 1404 of the wireless device 1402 as a UE, as described herein). These instructions may be located, for example, in the processor and / or on a memory of the UE (such as the memory 1406 of the wireless device 1402 as a UE, as described herein).
[0205] Fig.12A method 1200 of a base station according to an embodiment is illustrated. The method 1200 includes sending 1202 an ultra-compact DCI scheduling one or more scheduled PDSCHs to a UE.
[0206] The method 1200 further includes sending 1204 one or more scheduled PDSCHs to the UE, the one or more scheduled PDSCHs including a MAC CE having a first field for the PUSCH.
[0207] The method 1200 further includes receiving 1206 a PUSCH from the UE, wherein the PUSCH corresponds to data of the first field.
[0208] In some embodiments of method 1200, the first field for PUSCH includes one or more of the following: a TDRA table index field for PUSCH, a FDRA field for PUSCH, a frequency hopping flag field for PUSCH, an MCS field for PUSCH, a HARQ process number field for PUSCH, an RV field for PUSCH, an NDI field for PUSCH, a DAI field for PUSCH, a DMRS port field for PUSCH, a precoding information and layer number indicator field for PUSCH, and an SRS resource indicator field for PUSCH.
[0209] In some embodiments of the method 1200, the MAC CE includes a method for K4 To schedule PUSCH K4 Indicates the time gap K4 is the amount of time between one or more scheduled PDSCHs and PUSCHs that is greater than the MAC CE processing time of the MAC CE. In some of these embodiments, K4 The indication includes a processing time equal to or greater than the UE decoding one or more scheduled PDSCHs T proc,4 Additional offset value, and time gap K4 is equal to the MAC CE processing time plus an additional offset value. In some of these embodiments, K4 Indications include DFN and time gap K4 The slot index of the following slot.
[0210] In some embodiments of the method 1200, the number of PDSCH repetitions in the one or more scheduled PDSCHs is one of: predefined at the UE, configured by a SIB received at the UE, and indicated by an ultra-compact DCI.
[0211] In some embodiments of method 1200, one or more scheduled PDSCHs are sent to the UE based on one or more of the following: a predefined MCS value and a predefined MCS table, or a configured MCS value and a configured MCS table, each configured MCS value and configured MCS table configured in one or more of the RRC configuration and the SIB; a predefined RV value, or a configured RV value configured in one or more of the RRC configuration and the SIB; a predefined HARQ process number, or a configured HARQ process number configured in one or more of the RRC configuration and the SIB; a predefined NDI value; and a predefined DAI value.
[0212] In some embodiments, the method 1200 further includes receiving a PUCCH from the UE, the PUCCH including HARQ-ACK signaling for one or more scheduled PDSCHs and CSI parameters for the PUSCH.
[0213] 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 base station (such as the RAN device 1418 as a base station, as described herein).
[0214] 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 base station (such as memory 1422 of RAN device 1418 as a base station, as described herein).
[0215] 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 base station (such as the RAN device 1418 as a base station, as described herein).
[0216] 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 base station (such as the RAN device 1418 as a base station, as described herein).
[0217] Embodiments contemplated herein include a signal as described in or associated with one or more elements of method 1200 .
[0218] 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 1200. The processor may be a processor of a base station (such as the processor 1420 of the RAN device 1418 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 1422 of the RAN device 1418 as a base station, as described herein).
[0219] 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 "Scheduling PDSCH 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 "Scheduling PDSCH 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.
[0220] Fig.13 An exemplary architecture of a wireless communication system 1300 according to an embodiment disclosed herein is illustrated. The description provided below is for an exemplary wireless communication system 1300 operating in conjunction with LTE system standards and / or 5G or NR system standards provided in 3GPP technical specifications and other 3GPP documents.
[0221] like Fig.13 As shown, the wireless communication system 1300 includes UE 1302 and UE 1304 (although any number of UEs may be used). In this example, UE 1302 and UE 1304 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.
[0222] UE 1302 and UE 1304 may be configured to be communicatively coupled to RAN 1306. In an embodiment, RAN 1306 may be NG-RAN, E-UTRAN, etc. UE 1302 and UE 1304 utilize connections (or channels) (shown as connection 1308 and connection 1310, respectively) with RAN 1306, where each connection (or channel) includes a physical communication interface. RAN 1306 may include one or more base stations (such as ground base station 1312, ground base station 1314, satellite base station 1336, and satellite base station 1338) and / or other entities (e.g., satellite 1342, which may not have base station functionality) that enable connection 1308 and connection 1310. One or more satellite gateways 1334 may be used in conjunction with the RAN 1306 to communicate with the RAN 1306. 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 1336 , the satellite base station 1338 , and / or the satellite 1342 are integrated into the RAN 1306 .
[0223] In this example, connection 1308 and connection 1310 are air interfaces that enable such communication coupling and may conform to the RAT used by RAN 1306, such as, for example, LTE and / or NR. It is contemplated that in some embodiments, connection 1308 and connection 1310 may include service links between their respective UE 1302, UE 1304 and one or more of satellite base station 1336, satellite base station 1338, and satellite 1342.
[0224] In some implementations, UE 1302 and UE 1304 may also directly exchange communication data via side link interface 1316 .
[0225] UE 1304 is shown as being configured to access an access point (shown as AP 1318) via connection 1320. By way of example, connection 1320 may include a local wireless connection, such as a connection conforming to any IEEE 802.11 protocol, wherein AP 1318 may include a Wi-Fi ® In this example, AP 1318 can connect to another network (eg, the Internet) without going through CN 1324.
[0226] In an embodiment, UE 1302 and UE 1304 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), terrestrial base station 1312, ground base station 1314, satellite base station 1336, satellite base station 1338, and / or satellite 1342, although the scope of the embodiments is not limited in this respect. The OFDM signal may include multiple orthogonal subcarriers.
[0227] In some embodiments, all or part of ground base station 1312, ground base station 1314, satellite base station 1336 and / or satellite base station 1338 may be implemented as one or more software entities running on a server computer as part of a virtual network.
[0228] In addition or in other embodiments, the ground base station 1312 or the ground base station 1314 can be configured to communicate with each other via the interface 1322. In an embodiment where the wireless communication system 1300 is an LTE system (e.g., when the CN 1324 is an EPC), the interface 1322 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.
[0229] In an embodiment where the wireless communication system 1300 is a NR system (e.g., when the CN 1324 is a 5GC), the interface 1322 may be an Xn interface. The Xn interface is defined between two or more base stations connected to the 5GC (e.g., the CN 1324). 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 1340 between the satellite base station 1336 and the satellite base station 1338).
[0230] RAN 1306 is shown as being communicatively coupled to CN 1324. CN 1324 may include one or more network elements 1326 configured to provide various data and telecommunication services to customers / subscribers (e.g., UE 1302 and users of UE 1304) connected to CN 1324 via RAN 1306. Components of CN 1324 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, components of CN 1324 may be implemented in one or more processors and / or one or more associated memories.
[0231] In an embodiment, CN 1324 may be an EPC, and RAN 1306 may be connected to CN 1324 via an S1 interface 1328. In an embodiment, S1 interface 1328 may be divided into two parts: an S1 user plane (S1-U) interface, which carries traffic data between ground base station 1312, ground base station 1314, satellite base station 1336 or interface 1340 and a serving gateway (S-GW); and an S1-MME interface, which is a signaling interface between ground base station 1312, ground base station 1314, satellite base station 1336 or interface 1340 and a mobility management entity (MME).
[0232] In an embodiment, CN 1324 may be a 5GC, and RAN 1306 may be connected to CN 1324 via an NG interface 1328. In an embodiment, NG interface 1328 may be divided into two parts: an NG user plane (NG-U) interface, which carries traffic data between ground base station 1312, ground base station 1314, satellite base station 1336, or satellite base station 1338 and a user plane function (UPF); and an S1 control plane (NG-C) interface, which is a signaling interface between ground base station 1312, ground base station 1314, satellite base station 1336, or satellite base station 1338 and an access and mobility management function (AMF).
[0233] In general, the application server 1330 may be an element that provides applications (e.g., packet-switched data services) that use Internet Protocol (IP) bearer resources with the CN 1324. The application server 1330 may also be configured to support one or more communication services (e.g., VoIP sessions, group communication sessions, etc.) for the UE 1302 and UE 1304 via the CN 1324. The application server 1330 may communicate with the CN 1324 via an IP communication interface 1332.
[0234] Fig.14 A system 1400 is illustrated for performing signaling 1434 between a wireless device 1402 and a RAN device 1418 of a core network connected to a CN device 1436 according to an embodiment disclosed herein. The system 1400 may be part of a wireless communication system as described herein. The wireless device 1402 may be, for example, a UE of a wireless communication system. The RAN device 1418 may be, for example, a base station (e.g., an eNB or a gNB) of the wireless communication system that is a terrestrial base station or a satellite base station. In the case where the RAN device 1418 is a terrestrial base station, the RAN device 1418 may communicate with a satellite that provides a radio access connection directly to the UE in the manner described herein. The CN device 1436 may be one or more devices that make up a CN, as described herein.
[0235] The wireless device 1402 may include one or more processors 1404. The processor 1404 may execute instructions to cause various operations of the wireless device 1402 to be performed, as described herein. The processor 1404 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.
[0236] The wireless device 1402 may include a memory 1406. The memory 1406 may be a non-transitory computer-readable storage medium that stores instructions 1408 (which may include, for example, instructions executed by the processor 1404). The instructions 1408 may also be referred to as program code or a computer program. The memory 1406 may also store data used by the processor 1404 and results computed by the processor.
[0237] The wireless device 1402 may include one or more transceivers 1410 that may include radio frequency (RF) transmitter and / or receiver circuitry that uses an antenna 1412 of the wireless device 1402 to facilitate signaling (e.g., signaling 1434) transmitted or received by the wireless device 1402 with other devices (e.g., RAN devices 1418) in accordance with a corresponding RAT. In some embodiments, the antenna 1412 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).
[0238] For RAN equipment 1418 as a ground base station, network equipment signaling 1434 may occur on a feeder link between the wireless device 1402 and the satellite and a service link between the satellite and the RAN equipment 1418 (e.g., as combined with Figure 1 For RAN device 1418 as a satellite base station, signaling 1434 may occur over a feeder link between wireless device 1402 and RAN device 1418 (e.g., as described in conjunction with Figure 2 described).
[0239] The wireless device 1402 may include one or more antennas 1412 (e.g., one, two, four, or more). For implementations with multiple antennas 1412, the wireless device 1402 may exploit the spatial diversity of such multiple antennas 1412 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 the multiple antennas used at each of the transmitting device and the receiving device to implement this aspect). MIMO transmissions by the wireless device 1402 may be implemented based on precoding (or digital beamforming) applied at the wireless device 1402, which multiplexes the data streams across the antennas 1412 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).
[0240] In certain embodiments with multiple antennas, the wireless device 1402 may implement analog beamforming techniques whereby the phases of signals transmitted by the antennas 1412 are relatively adjusted so that the (joint) transmissions of the antennas 1412 can be directed (this is sometimes referred to as beam steering).
[0241] The wireless device 1402 may include one or more interfaces 1414. The interfaces 1414 may be used to provide input to or output from the wireless device 1402. For example, a wireless device 1402 that is a UE may include an interface 1414, such as a microphone, a speaker, a touch screen, buttons, etc., to allow a user of the UE to 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 1410 / antenna 1412 described above), and may communicate according to known protocols (e.g., Wi-Fi ® ,Bluetooth ® etc.) to perform the operation.
[0242] The wireless device 1402 may include a scheduling module 1416. The scheduling module 1416 may be implemented via hardware, software, or a combination thereof. For example, the scheduling module 1416 may be implemented as a processor, circuit, and / or instructions 1408 stored in the memory 1406 and executed by the processor 1404. In some examples, the scheduling module 1416 may be integrated within the processor 1404 and / or the transceiver 1410. For example, the scheduling module 1416 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 1404 or the transceiver 1410.
[0243] The scheduling module 1416 may be used in various aspects of the present disclosure, for example, Figures 3 to 12 The scheduling module 1416 is configured to, for example, process ultra-compact DCI received at the wireless device 1402 and / or schedule PDSCH.
[0244] The RAN device 1418 may include one or more processors 1420. The processor 1420 may execute instructions to perform various operations of the RAN device 1418 as described herein. The processor 1404 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.
[0245] The RAN device 1418 may include a memory 1422. The memory 1422 may be a non-transitory computer-readable storage medium storing instructions 1424 (which may include, for example, instructions executed by the processor 1420). The instructions 1424 may also be referred to as program code or a computer program. The memory 1422 may also store data used by the processor 1420 and results calculated by the processor.
[0246] The RAN device 1418 may include one or more transceivers 1426 that may include RF transmitter and / or receiver circuits that use antennas 1428 of the RAN device 1418 to facilitate signaling (e.g., signaling 1434) sent or received by the RAN device 1418 with other devices (e.g., wireless device 1402) in accordance with the corresponding RAT.
[0247] The RAN device 1418 may include one or more antennas 1428 (eg, one, two, four, or more). In an embodiment with multiple antennas 1428, the RAN device 1418 may perform MIMO, digital beamforming, analog beamforming, beam steering, etc. as described above.
[0248] For RAN equipment 1418 that is a terrestrial base station, one or more of the transceiver 1426 and / or antenna 1428 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 1418 as a satellite base station, the transceiver 1426 and / or the antenna 1428 may be present on the satellite, and one or more of these antennas 1428 may be antennas suitable for satellite communication (such as mobile parabolic antennas, omnidirectional phased array antennas, etc.).
[0249] The RAN device 1418 may include one or more interfaces 1430. The interface 1430 may be used to provide input to or output from the RAN device 1418. For example, the RAN device 1418 as a base station may include an interface 1430 composed of a transmitter, a receiver and other circuits (e.g., in addition to the transceiver 1426 / antenna 1428 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.
[0250] The RAN device 1418 may include a scheduling module 1432. The scheduling module 1432 may be implemented via hardware, software, or a combination thereof. For example, the scheduling module 1432 may be implemented as a processor, circuit, and / or instructions 1424 stored in the memory 1422 and executed by the processor 1420. In some examples, the scheduling module 1432 may be integrated within the processor 1420 and / or the transceiver 1426. For example, the scheduling module 1432 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 1420 or the transceiver 1426.
[0251] The scheduling module 1432 may be used in various aspects of the present disclosure, for example, Figures 3 to 12 The scheduling module 1432 is configured to, for example, generate and / or send ultra-compact DCI and / or schedule PDSCH to be sent by the RAN device 1418.
[0252] RAN device 1418 can communicate with CN device 1436 via interface 1446, which can be similar to Fig.13 Interface 1328 (for example, can be S1 and / or NG interface, either of which can be divided into user plane and control plane parts).
[0253] The CN device 1436 may include one or more processors 1438. The processor 1438 may execute instructions to perform various operations of the CN device 1436 as described herein. The processor 1438 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.
[0254] CN device 1436 may include memory 1440. Memory 1440 may be a non-transitory computer-readable storage medium storing instructions 1442 (which may include, for example, instructions executed by processor 1438). Instructions 1442 may also be referred to as program code or a computer program. Memory 1440 may also store data used by processor 1438 and results calculated by the processor.
[0255] The CN device 1436 may include one or more interfaces 1444. The interfaces 1444 may be used to provide input to or output from the CN device 1436. For example, the CN device 1436 may include an interface 1430 composed of a transmitter, a receiver, and other circuits that enable the CN device 1436 to communicate with other equipment in the CN, and / or enable the CN device 1436 to communicate with an external network, computer, database, etc., for the purpose of operating, managing, and maintaining the CN device 1436 or other equipment operably connected to the CN device.
[0256] 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 set forth 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.
[0257] Unless explicitly stated otherwise, 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.
[0258] 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.
[0259] 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.
[0260] 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.
[0261] 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 of implementing 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 comprising: receiving ultra-compact downlink control information (DCI) for scheduling one or more physical downlink shared channels (PDSCHs) from a base station; receiving the one or more scheduling PDSCHs from the base station, the one or more scheduling PDSCHs comprising a medium access control element (MAC CE) having a first field for a data PDSCH; decoding the MAC CE from the one or more scheduled PDSCHs; and The data PDSCH is received from the base station, wherein the data PDSCH corresponds to data of the first field.
2. The method of claim 1 , wherein the first field for the data PDSCH comprises one or more of: A time domain resource allocation (TDRA) table index field for the data PDSCH; a frequency domain resource allocation (FDRA) field for the data PDSCH; a modulation and coding scheme (MCS) field for the data PDSCH; A Hybrid Automatic Repeat Request (HARQ) process number field for the data PDSCH; a redundancy version (RV) field for the data PDSCH; a new data indicator (NDI) field for the data PDSCH; a downlink allocation indicator (DAI) field for the data PDSCH; a virtual resource block (VRB) to physical resource block (PRB) mapping field for the data PDSCH; a demodulation reference signal (DMRS) port field for the data PDSCH; as well as The Transport Block (TB) number field is used for the data PDSCH.
3. The method of claim 1, further comprising sending a physical uplink control channel (PUCCH) including hybrid automatic repeat request (HARQ) acknowledgement (HARQ-ACK) signaling for the data PDSCH to the base station, wherein the MAC CE further includes a second field for the HARQ-ACK signaling for the data PDSCH.
4. The method of claim 3, wherein the second field used for the HARQ-ACK signaling comprises 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.
5. The method according to claim 1, wherein the MAC CE includes a K3 To schedule the data PDSCH K3 Indicates the time gap in which K3is an amount of time between the one or more scheduling PDSCHs and the data PDSCH, the amount of time being greater than a round trip time (RTT) of signaling between the UE and the base station.
6. The method according to claim 5, wherein the K3 Indicates that an additional offset value is included AO , and wherein the time interval K3 equal: K Offset+ Kmac + AO ;in: K The offset is a first amount of time that ensures signaling causality between the UE and a signaling timing reference point for UE-to-base station signaling; Kmac is a second amount of time that takes into account a delay between the base station and the signaling timing reference point; and AO Equal to or greater than the processing time of the UE to decode the MAC CE from the one or more scheduled PDSCHs T proc,3 .
7. The method according to claim 5, wherein the K3 The indication includes the direct frame number (DFN) and the time gap in the K3 The slot index of the following slot.
8. The method of claim 1, wherein the one or more scheduled PDSCHs include application layer data.
9. The method of claim 1 , wherein the number of PDSCH repetitions in the one or more scheduled PDSCHs is one of: predefined at the UE; configured by a system information block (SIB) received at the UE; and Indicated by the ultra-compact DCI.
10. The method of claim 1, wherein the one or more scheduling PDSCHs are received according to one or more of the following: a predefined modulation and coding scheme (MCS) value and a predefined MCS table, or a configured MCS value and a configured MCS table, each configured MCS value and configured MCS table being configured in one or more of a radio resource control (RRC) configuration and a system information block (SIB); a predefined redundancy version (RV) value, or a configured RV value configured in one or more of the RRC configuration and the SIB; a predefined Hybrid Automatic Repeat Request (HARQ) process number, or a configured HARQ process number configured in one or more of the RRC configuration and the SIB; predefined New Data Indicator (NDI) values; and Predefined Downlink Allocation Indicator (DAI) values.
11. A method of a user equipment (UE), the method comprising: receiving ultra-compact downlink control information (DCI) for scheduling one or more physical downlink shared channels (PDSCHs) from a base station; receiving the one or more scheduled PDSCHs from the base station, the one or more scheduled PDSCHs comprising a medium access control element (MAC CE) having a first field for a PUSCH; decoding the MAC CE from the one or more scheduled PDSCHs; and The PUSCH is sent to the base station, wherein the PUSCH corresponds to data of the first field.
12. The method of claim 11, wherein the first field for the PUSCH comprises one or more of: A time domain resource allocation (TDRA) table index field for the PUSCH; A frequency domain resource allocation (FDRA) field for the PUSCH; A frequency hopping flag field for the PUSCH; a modulation and coding scheme (MCS) field for the PUSCH; A Hybrid Automatic Repeat Request (HARQ) process number field for the PUSCH; a redundancy version (RV) field for the PUSCH; a New Data Indicator (NDI) field for the PUSCH; a downlink allocation indicator (DAI) field for the PUSCH; A demodulation reference signal (DMRS) port field for the PUSCH; Precoding information and layer indicator field for the PUSCH; as well as A sounding reference signal (SRS) resource indicator field is used for the PUSCH.
13. The method according to claim 11, wherein the MAC CE includes a K4 To schedule the PUSCH K4 Indicates the time gap in which K4 It is the amount of time between the one or more scheduled PDSCHs and the PUSCH, and the amount of time is greater than the MAC CE processing time of the MAC CE.
14. The method according to claim 13, wherein: Said K4 The indication includes an additional offset value, the additional offset value being equal to or greater than a processing time for the UE to decode the one or more scheduled PDSCHs T proc,4 ,and The time interval K4 Equal to the MAC CE processing time plus the additional offset value.
15. The method according to claim 13, wherein the K4 The indication includes the direct frame number (DFN) and the time gap in the K4 The slot index of the following slot.
16. The method of claim 11, wherein the number of PDSCH repetitions in the one or more scheduled PDSCHs is one of: predefined at the UE; configured by a system information block (SIB) received at the UE; and Indicated by the ultra-compact DCI.
17. The method of claim 11, wherein the one or more scheduling PDSCHs are received according to one or more of: a predefined modulation and coding scheme (MCS) value and a predefined MCS table, or a configured MCS value and a configured MCS table, each configured MCS value and configured MCS table being configured in one or more of a radio resource control (RRC) configuration and a system information block (SIB); a predefined redundancy version (RV) value, or a configured RV value configured in one or more of the RRC configuration and the SIB; a predefined Hybrid Automatic Repeat Request (HARQ) process number, or a configured HARQ process number configured in one or more of the RRC configuration and the SIB; predefined New Data Indicator (NDI) values; and Predefined Downlink Allocation Indicator (DAI) values.
18. The method of claim 11, further comprising sending a physical uplink control channel (PUCCH) to the base station, the PUCCH comprising: Hybrid Automatic Repeat Request (HARQ) Acknowledgement (HARQ-ACK) signaling for the one or more scheduled PDSCHs; as well as Channel state information (CSI) parameters for the PUSCH.
19. An apparatus comprising means for performing the method according to any one of claims 1 to 18.
20. 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 18.
21. An apparatus comprising logic components, modules or circuits for performing the method according to any one of claims 1 to 18.
Citation Information
Patent Citations
Method and composition for combating weeds
EP0001328A1
