Process for non-terrestrial network coverage enhancement with ultra-compact downlink control information and scheduled physical downlink shared channel
Ultra-compact DCI and scheduled PDSCHs address the challenges of reduced downlink coverage and PDCCH reliability in NTNs, improving network throughput and reliability.
Patent Information
- Application Number
- CN202380036727.2
- 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
Non-terrestrial networks (NTNs) face challenges with reduced downlink coverage due to PFD limitations and increased propagation delays, which affect the reliability of PDCCH transmissions and overall network throughput.
Implementing innovative methods for non-terrestrial networks (NTNs) by using a combination of ultra-compact DCI and scheduling PDSCHs to enhance the reliability of data transmission.
The proposed solution improves downlink coverage and reduces the impact of PDCCH-related issues, thereby enhancing the overall network throughput and reliability in NTN environments.
Smart Images

Figure CN119096494A_ABST
Abstract
Description
Technical Field
[0001] The present application as a whole 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) (commonly referred to within industry organizations as WLANs). ).
[0003] As envisioned by 3GPP, different wireless communication system standards and protocols may use various radio access networks (RANs) to communicate between base stations of the RAN (which may also sometimes be referred to as RAN nodes, network nodes, or simply nodes) and wireless communication devices referred to as user equipment (UE). 3GPP RANs may include, for example, Global System for Mobile Communications (GSM), Enhanced Data Rates for GSM Evolution (EDGE) RAN (GERAN), Universal Terrestrial Radio Access Network (UTRAN), Evolved Universal Terrestrial Radio Access Network (E-UTRAN), and / or Next Generation Radio Access Network (NG-RAN).
[0004] Each RAN may use one or more radio access technologies (RATs) for communication between base stations and UEs. For example, GERAN implements GSM and / or EDGE RAT, UTRAN implements Universal Mobile Telecommunications System (UMTS) RAT or other 3GPP RAT, E-UTRAN implements LTE RAT (sometimes referred to as LTE), and NG-RAN implements NR RAT (sometimes referred to as 5G RAT, 5G NR RAT, or NR in this document). In some deployments, E-UTRAN may also implement NR RAT. In some deployments, NG-RAN may also implement LTE RAT.
[0005] The base stations used by the RAN may correspond to the RAN. An example of an E-UTRAN base station is an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (also commonly denoted as an evolved Node B, enhanced Node B, eNodeB, or eNB). An example of an NG-RAN base station is a Next Generation Node B (sometimes also referred to as a gNodeB or gNB).
[0006] The RAN provides communication services together with external entities through its connection with the Core Network (CN). For example, E-UTRAN may utilize the Evolved Packet Core Network (EPC), while NG-RAN may utilize the 5G Core Network (5GC). BRIEF DESCRIPTION OF THE DRAWINGS
[0007] To easily identify the discussion of any particular element or act, the most significant digit(s) in a reference number refers to the drawing number that first introduces the element.
[0008] Figure 1 An NTN architecture of a wireless communication system according to an embodiment is illustrated.
[0009] Figure 2 An NTN architecture of a wireless communication system according to an embodiment is illustrated.
[0010] Figure 3 A schematic diagram illustrating a dynamic resource grant process for DL data transmission according to an embodiment is illustrated.
[0011] Figure 4 A schematic diagram illustrating a dynamic resource grant process for UL data transmission according to an embodiment is illustrated.
[0012] Figure 5 A schematic diagram illustrating a dynamic resource grant process for DL data transmission using ultra-compact DCI and one or more scheduled PDSCHs according to an embodiment is illustrated.
[0013] Figure 6 A schematic diagram illustrating a dynamic resource grant process for DL data transmission using ultra-compact DCI and one or more scheduled PDSCHs according to an embodiment is illustrated.
[0014] Figure 7 A method of a base station according to an embodiment is illustrated.
[0015] Figure 8 A method of a UE according to an implementation scheme is shown.
[0016] Fig. 9 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.
[0017] Fig.10 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.
[0018] Fig.11 A method of a base station according to an embodiment is illustrated.
[0019] Fig.12 A method of a UE according to an implementation scheme is shown.
[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] The various embodiments are described with respect to a UE. However, reference to a UE is provided for illustrative purposes only. The example embodiments may be used with any electronic component that can establish a connection with a network and is configured with hardware, software, and / or firmware for exchanging information and data with the network. Therefore, a UE as described herein is used to represent any suitable electronic component.
[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 terrestrial base station 104 comprises eNB. In these cases, CN link 114 connecting CN 102 and terrestrial base station 104 may comprise an S1 interface.
[0025] In some embodiments, RAN 112 includes NG-RAN, CN 102 includes 5GC, and land base station 104 includes gNB or next generation eNB (ng-eNB). In this case, CN link 114 connecting CN 102 and land 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 terrestrial 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 terrestrial base station 104 is shown without the capability to directly communicate with the UE via terrestrial wireless communications. However, it is contemplated that in other embodiments, such a terrestrial 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 land base station 1312 and land 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 this 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, the functions of a base station are located on a satellite base station 206, and communications between these base station functions and the CN 202 occur via a satellite gateway 204 and a feeder link 214 forwarded to the satellite base station 206 via an interface found on a CN link 212 (e.g., an S1 interface and / or an NG interface). The satellite base station 206 may be equipped with one or more antennas capable of broadcasting a cell in accordance with the RAN 210, and the UE 208 may be equipped with one or more antennas (e.g., a mobile parabolic antenna, an omnidirectional phased array antenna, etc.) capable of communicating with the satellite base station 206 via a Uu interface on the cell (such communications may be said to use the service link 216 shown). The payload located on the satellite base station 206 then forwards data between the satellite gateway 204 and the satellite base station 206 using the feeder link 214 between the satellite gateway 204 and the satellite base station 206 and the service link 216 between the satellite base station 206 and the UE 208. The payload may perform RF conversion and / or amplification in both the uplink (UL) and downlink (DL) to enable this communication, as well as implement the functionality of a base station (e.g., as an eNB, ng-eNB, or gNB of the type corresponding to RAN 210), as these are already located on the 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 land 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 location of the UE. Therefore, improvements to wireless communication systems may be intended to help mitigate the undesirable effects caused by these situations. In view of 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 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 can 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 (expressed in dB / degree). The values of these PFD calculation factors may depend on whether the satellite is a GSO or non-GSO satellite. Appropriate values of the PFD calculation factors may be applied in a defined manner relative to the angle of arrival above the horizontal plane (relative to a location on the Earth's surface) δ (in degrees) to achieve the PFD limit.
[0036] For example, a satellite in geostationary orbit (GSO) may correspond to a PFD calculation factor of P = -146 dB (W / m 2 )(4kHz) or -128dB(W / m 2 )(1MHz), and r = 0.5dB / degree, while a satellite in a non-GSO may correspond to a parameter P = -144dB(W / m 2 )(4kHz) or -126dB(W / m 2 )(1MHz), and r = 0.65dB / degree. In some areas, satellites in non-GSO may instead use P = -142.5dB (W / m 2 ), and using -124.5dB(W / m 2 ).
[0037] Then, using the appropriate PFD calculation factors P and r based on the applicable satellite information, the PFD limit relative to the satellite can be calculated based on the applicable delta between the UE location and the satellite using the following equation:
[0038] PFD = P, for 0°≤δ≤5°;
[0039] PFD = P + r(δ-5), for 5°≤δ≤25°; and
[0040] PFD=P+20r, for 25°≤δ≤90°.
[0041] Within such calculated PFD constraints, it is possible that the DL transmit power (or effective isotropically radiated power (EIRP)) in the range of 2483.5 MHz to 2500 MHz is insufficient to cover the entire geographic cell of the satellite with strong coverage.
[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 transmitting 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 4A diagram 400 is illustrated illustrating a dynamic resource granting process for UL data transmission according to an embodiment. The diagram 400 illustrates transmitting 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 can be successfully used in some situations (e.g., situations involving all-terrestrial networks), where aspects of the behavior and / or relationship between the base station and the UE can be implicitly assumed in those scenarios. However, it has been recognized that in various situations, the Figure 3 and Figure 4 As shown in (and about Figure 3 and Figure 4 Modifications of the process described may be beneficial.
[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 PDSCH coverage provided by satellites of NTNs 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 large 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 appear in DCI of other DCI formats. In some wireless communication networks, such as those implementing LTE RAT and / or NR RAT, it may be possible that such ultra-compact DCI may therefore have a reduced payload size compared to "compact DCI" known to those networks (e.g., DCI of formats 1_2 and / or 0_2).
[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 for 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, 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 can 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 (not shown in FIG. 1 ). For example, if the UE successfully receives and decodes the data PDSCH 506, the HARQ-ACK signaling may include an ACK. If the UE successfully receives and / or decodes the data PDSCH 506, the HARQ-ACK signaling may include a NACK instead.
[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 scheduling and usage 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, the ultra-compact DCI 502 and any one of the one or more scheduled PDSCHs 504 (or any combination of any of these) provide sufficient information to the UE so that the UE knows the time and frequency location of the PUCCH 602 (e.g., some / all of the scheduled PUCCHs 602 in the ultra-compact DCI 502 and / or one or more scheduled PDSCHs 504).
[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 scheduling 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 7 A method 700 of a base station according to an embodiment is illustrated. The method 700 comprises sending 702 to a UE an ultra-compact DCI scheduling one or more scheduling PDSCHs, the one or more scheduling PDSCHs scheduling a data PDSCH.
[0076] The method 700 also includes sending 704 the one or more scheduled PDSCHs to the UE.
[0077] The method 700 also includes transmitting 706 to the UE a data PDSCH as scheduled by the one or more scheduling PDSCHs.
[0078] In some embodiments, the method 700 further includes receiving a PUCCH with HARQ-ACK signaling from the UE, the HARQ-ACK signaling indicating that the UE decoded scheduling information from one or more scheduled PDSCHs. In some of these embodiments, the ultra-compact DCI schedules the PUCCH. In some of these embodiments, one or more scheduled PDSCHs schedule the PUCCH.
[0079] In some embodiments, method 700 also includes sending a SIB including configuration information for the ultra-compact DCI.
[0080] In some embodiments, method 700 further includes sending a SIB including configuration information for one or more scheduled PDSCHs.
[0081] In some embodiments, method 700 further includes sending a SIB including configuration information for a PUCCH used for HARQ-ACK signaling corresponding to one or more scheduled PDSCHs.
[0082] In some implementations of method 700, one or more scheduled PDSCHs use a MAC CE to schedule a data PDSCH.
[0083] In some embodiments of method 700, the one or more scheduled PDSCHs include PDSCH repetitions.
[0084] In some embodiments, method 700 further includes receiving HARQ-ACK signaling from the UE indicating that the UE received the data PDSCH.
[0085] Embodiments contemplated herein include an apparatus comprising means for performing one or more elements of method 700. 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).
[0086] 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 700. 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).
[0087] Embodiments contemplated herein include an apparatus comprising logic, modules, or circuits operable to perform one or more elements of the method 700. 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).
[0088] Embodiments contemplated herein include an apparatus comprising: one or more processors and one or more computer-readable media, the 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 700. 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).
[0089] Embodiments contemplated herein include a signal as described in or in connection with one or more elements of method 700 .
[0090] 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 700. 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).
[0091] Figure 8 A method 800 of a UE according to an embodiment is shown. The method 800 includes receiving 802 from a base station an ultra-compact DCI scheduling one or more scheduling PDSCHs, the one or more scheduling PDSCHs scheduling a data PDSCH.
[0092] The method 800 also includes receiving 804 the one or more scheduled PDSCHs from a base station.
[0093] The method 800 also includes receiving 806 a data PDSCH from a base station, as scheduled by one or more scheduling PDSCHs.
[0094] In some embodiments, method 800 further includes transmitting a PUCCH with HARQ-ACK signaling to the base station, the HARQ-ACK signaling indicating that the UE decoded scheduling information from one or more scheduled PDSCHs. In some of these embodiments, the ultra-compact DCI schedules the PUCCH. In some of these embodiments, one or more scheduled PDSCHs schedule the PUCCH.
[0095] In some embodiments, method 800 also includes receiving a SIB including configuration information for an ultra-compact DCI.
[0096] In some embodiments, method 800 further includes receiving a SIB including configuration information for one or more scheduled PDSCHs.
[0097] In some embodiments, method 800 further includes receiving a SIB including configuration information for a PUCCH used for HARQ-ACK signaling corresponding to one or more scheduled PDSCHs.
[0098] In some embodiments of method 800, the one or more scheduling PDSCHs use a MAC CE to schedule a data PDSCH.
[0099] In some embodiments of method 800, the one or more scheduled PDSCHs include PDSCH repetitions.
[0100] In some embodiments, method 800 further includes transmitting HARQ-ACK signaling to the base station indicating that the UE received the data PDSCH.
[0101] Embodiments contemplated herein include an apparatus comprising means for performing one or more elements of method 800. The apparatus may be, for example, an apparatus that is a UE (such as wireless device 1402 as a UE, as described herein).
[0102] 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 800. 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).
[0103] Embodiments contemplated herein include an apparatus comprising logic, modules, or circuits for performing one or more elements of the method 800. The apparatus may be, for example, an apparatus of a UE (such as the wireless device 1402 as a UE, as described herein).
[0104] Embodiments contemplated herein include an apparatus comprising: one or more processors and one or more computer-readable media, the 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 800. The apparatus may be, for example, an apparatus that is a UE (such as the wireless device 1402 as a UE, as described herein).
[0105] Embodiments contemplated herein include a signal as described in or in connection with one or more elements of method 800 .
[0106] 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 800. 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).
[0107] Fig. 9 A diagram 900 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 900 illustrates the use of ultra-compact DCI 902 and one or more scheduled PDSCHs 904 to schedule a PUSCH 906 for UL data transmission.
[0108] Diagram 900 illustrates that ultra-compact DCI 902 is sent by a base station and received at a UE. Ultra-compact DCI 902 provides sufficient information to the UE so that the UE knows the time and frequency location of one or more scheduled PDSCHs 904 (eg, ultra-compact DCI 902 schedules one or more scheduled PDSCHs 904).
[0109] The one or more scheduled PDSCHs 904 are then sent by the base station as scheduled and received at the UE. The one or more scheduled PDSCHs 904 may include one or more medium access control elements (MAC CEs) that include scheduling information for the PUSCH 906. The one or more scheduled PDSCHs 904 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 906 (e.g., the one or more scheduled PDSCHs 904 schedule the PUSCH 906).
[0110] In some embodiments, one or more scheduled PDSCHs 904 include PDSCH repetitions. For example, in the case where one or more scheduled PDSCHs 904 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 904 will have, for example, the same MAC CE with scheduling information for the PUSCH 906. Such repeated use can provide the UE with additional reception opportunities for the data, thereby increasing the probability that the UE successfully receives and / or decodes the data.
[0111] The PUSCH 906 is then scheduled to be transmitted by the UE. The PUSCH 906 may include, for example, user plane (UP) data (eg, application layer data of applications running on the UE).
[0112] As shown, the minimum offset K4 908 between the last scheduled PDSCH in one or more scheduled PDSCHs 904 and PUSCH 906 can be maintained by the network. In other words, the ultra-compact DCI 902 can schedule one or more scheduled PDSCHs 904, and one or more scheduled PDSCHs 904 can schedule PUSCH 906, thereby maintaining the minimum offset K4908.
[0113] The base station may transmit a system information block (SIB) including configuration information for the ultra-compact DCI 902 and / or one or more scheduled PDSCHs 904. The configuration information for the ultra-compact DCI 902 as found in the SIB may be used by a UE to locate the ultra-compact DCI 902.
[0114] Further, the configuration information of the one or more scheduled PDSCHs 904 as found in the SIB may be further used to locate the one or more scheduled PDSCHs 904 (in other words, the ultra-compact DCI 902 may schedule the one or more scheduled PDSCHs 904 based on / with the background assumption of any configuration of the one or more scheduled PDSCHs 904 provided in the SIB). In some cases, the configuration information for the one or more scheduled PDSCHs 904 in the SIB may correlate the time and / or frequency location of any one of the one or more scheduled PDSCHs 904 relative to the received ultra-compact DCI 902.
[0115] The SIB can be Fig. 9 The base station of the dynamic resource grant process (eg, sending ultra-compact DCI 902) sends Fig. 9 Alternatively, the SIB can be sent by another base station to the UE of the dynamic resource grant process. Fig. 9 UE.
[0116] Fig.10 A diagram 1000 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. Fig. 9 Thus, diagram 1000 illustrates the use of ultra-compact DCI 902, one or more scheduled PDSCHs 904, PUSCH 906, and offset K4 908, as described with respect to FIG. Fig. 9 900 as described. In addition to Fig. 9 In addition to these elements of the schematic diagram 900, Fig.10 Schematic diagram 1000 additionally illustrates the scheduling and use of PUCCH 1002 with HARQ-ACK signaling.
[0117] The PUCCH 1002 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 904. If the UE's reception and decoding of the scheduling information of the PUSCH 906 from the one or more scheduled PDSCHs 904 is successful, the HARQ-ACK signaling in the PUCCH 1002 may include an ACK. If the UE's reception and / or decoding of the scheduling information of the PUSCH 906 from the one or more scheduled PDSCHs 904 is unsuccessful, the HARQ-ACK signaling in the PUCCH 1002 may instead include a NACK. In the case of a NACK (or in the case that any expected PUCCH 1002 does not arrive at the base station at all), the base station may determine that the UE cannot use the PUSCH 906 under any circumstances, and may cancel its scheduled reception attempt for the PUSCH 906 accordingly in order to save network resources.
[0118] like Fig.10 As shown in schematic diagram 1000, the ultra-compact DCI 902 and any one of the one or more scheduled PDSCHs 904 (or any combination of any of these) provide sufficient information to the UE so that the UE knows the time and frequency location of the PUCCH 1002 (e.g., some / all of the scheduled PUCCHs 1002 in the ultra-compact DCI 902 and / or one or more scheduled PDSCHs 904).
[0119] Alternatively (or additionally), the SIB received at the UE may provide configuration information for the PUCCH 1002, including (but not limited to) providing information about the time and / or frequency location of the PUCCH 1002. In such a case, the configuration information of the PUCCH 1002 in the SIB may correlate the time and / or frequency location of the PUCCH 1002 relative to any of the received ultra-compact DCI 902 and / or one or more scheduled PDSCHs 904.
[0120] Fig.10 Schematic diagram 1000 illustrates one or more PUCCHs 1002 scheduled between PDSCH 904 and PUSCH 906. It should be noted that in alternative embodiments, the PUCCH 1002 described herein may be located after PUSCH 906 instead.
[0121] Fig.11 A method 1100 of a base station according to an embodiment is illustrated. The method 1100 includes sending 1102 to a UE an ultra-compact DCI scheduling one or more scheduled PDSCHs, the one or more scheduled PDSCHs scheduling a PUSCH.
[0122] The method 1100 also includes sending 1104 one or more scheduled PDSCHs to the UE.
[0123] The method 1100 also includes receiving 1106 a PUSCH from the UE as scheduled by one or more scheduling PDSCHs.
[0124] In some embodiments, method 1100 further includes receiving a PUCCH with HARQ-ACK signaling from the UE, the HARQ-ACK signaling indicating that the UE decoded scheduling information from one or more scheduled PDSCHs. In some of these embodiments, the ultra-compact DCI schedules the PUCCH. In some of these embodiments, one or more scheduled PDSCHs schedule the PUCCH.
[0125] In some embodiments, method 1100 also includes sending a SIB including configuration information for the ultra-compact DCI.
[0126] In some embodiments, method 1100 further includes sending a SIB including configuration information for one or more scheduled PDSCHs.
[0127] In some embodiments, method 1100 also includes sending a SIB including configuration information for a PUCCH used for HARQ-ACK signaling corresponding to one or more scheduled PDSCHs.
[0128] In some implementations of method 1100, one or more scheduled PDSCHs use MAC CE to schedule PUSCH.
[0129] In some embodiments of method 1100, one or more scheduled PDSCHs include PDSCH repetitions.
[0130] 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 base station (such as the RAN device 1418 as a base station, as described herein).
[0131] 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 base station (such as memory 1422 of RAN device 1418 as a base station, as described herein).
[0132] 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 base station (such as the RAN device 1418 as a base station, as described herein).
[0133] 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 that is a base station (such as RAN device 1418 as a base station, as described herein).
[0134] Implementations contemplated herein include signals as described in or related to one or more elements of method 1100 .
[0135] 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 1100. 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 a processor and / or on a memory of a base station (such as the memory 1422 of the RAN device 1418 as a base station, as described herein).
[0136] Fig.12A method 1200 of a UE according to an embodiment is shown. The method 1200 includes receiving 1202 an ultra-compact DCI scheduling one or more scheduled PDSCHs from a base station, the one or more scheduled PDSCHs scheduling a PUSCH.
[0137] The method 1200 also includes receiving 1204 the one or more scheduled PDSCHs from a base station.
[0138] The method 1200 also includes sending 1206 a PUSCH to a base station as scheduled by one or more scheduling PDSCHs.
[0139] In some embodiments, method 1200 further comprises transmitting a PUCCH with HARQ-ACK signaling to the base station, the HARQ-ACK signaling indicating that the UE decoded scheduling information from one or more scheduled PDSCHs. In some of these embodiments, the ultra-compact DCI schedules the PUCCH. In some of these embodiments, one or more scheduled PDSCHs schedule the PUCCH.
[0140] In some embodiments, method 1200 also includes receiving a SIB including configuration information for an ultra-compact DCI.
[0141] In some embodiments, method 1200 also includes receiving a SIB including configuration information for one or more scheduled PDSCHs.
[0142] In some embodiments, method 1200 also includes receiving a SIB including configuration information for a PUCCH used for HARQ-ACK signaling corresponding to one or more scheduled PDSCHs.
[0143] In some implementations of method 1200, one or more scheduled PDSCHs use MAC CE to schedule PUSCH.
[0144] In some embodiments of the method 1200, the one or more scheduled PDSCHs include PDSCH repetitions.
[0145] Embodiments contemplated herein include an apparatus comprising means for performing one or more elements of the method 1200. The apparatus may be, for example, an apparatus that is a UE (such as the wireless device 1402 as a UE, as described herein).
[0146] Embodiments contemplated herein include one or more non-transitory computer-readable media including instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of method 1200. The non-transitory computer-readable medium may be, for example, a memory of a UE (such as memory 1406 of wireless device 1402 as a UE, as described herein).
[0147] Embodiments contemplated herein include an apparatus including logical components, modules, or circuits for performing one or more elements of the method 1200. The apparatus may be, for example, an apparatus of a UE (such as the wireless device 1402 as a UE, as described herein).
[0148] Embodiments contemplated herein include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of the method 1200. The apparatus may be, for example, an apparatus that is a UE (such as the wireless device 1402 as a UE, as described herein).
[0149] Embodiments contemplated herein include signals as described in or related to one or more elements of method 1200 .
[0150] Embodiments contemplated herein include a computer program or computer program product including instructions, wherein execution of the program by a processor causes the processor to perform one or more elements of the method 1200. The processor may be a processor of a UE (such as the processor 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).
[0151] 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.
[0152] like Fig.13As 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 smart phones (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.
[0153] 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 land base station 1312, land base station 1314, satellite base station 1336, and satellite base station 1338) and / or other entities that enable connection 1308 and connection 1310 (e.g., satellite 1342, which may not have base station functionality). 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 integration of satellite base stations 1336, satellite base stations 1338 and / or satellites 1342 into the RAN 1306 in a manner described (and with appropriate elements).
[0154] 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.
[0155] In some implementations, UE 1302 and UE 1304 may also directly exchange communication data via side link interface 1316 .
[0156] 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 In this example, AP 1318 can connect to another network (eg, the Internet) without going through CN 1324.
[0157] In an embodiment, UE 1302 and UE 1304 may be configured to communicate with each other, terrestrial base station 1312, terrestrial base station 1314, satellite base station 1336, satellite base station 1338, and / or satellite 1342 using orthogonal frequency division multiplexing (OFDM) communication signals over a multi-carrier communication channel in accordance with 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), although the scope of the embodiments is not limited in this respect. The OFDM signal may include multiple orthogonal subcarriers.
[0158] In some embodiments, all or part of terrestrial base station 1312, terrestrial 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.
[0159] In addition or in other embodiments, the terrestrial base station 1312 or the terrestrial 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 two satellite base stations.
[0160] In an embodiment where the wireless communication system 1300 is an 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).
[0161] 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. The 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, the components of CN 1324 may be implemented in one or more processors and / or one or more associated memories.
[0162] 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 terrestrial base station 1312, terrestrial 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 terrestrial base station 1312, terrestrial base station 1314, satellite base station 1336 or interface 1340 and a mobility management entity (MME).
[0163] 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 terrestrial base station 1312, terrestrial 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 terrestrial base station 1312, terrestrial base station 1314, satellite base station 1336, or satellite base station 1338 and an access and mobility management function (AMF).
[0164] 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 the UE 1304 via the CN 1324. The application server 1330 may communicate with the CN 1324 via the IP communication interface 1332.
[0165] Fig.14A system 1400 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 is illustrated. The system 1400 can be part of a wireless communication system as described herein. The wireless device 1402 can be, for example, a UE of a wireless communication system. The RAN device 1418 can be, for example, a base station (e.g., an eNB or gNB) of a wireless communication system that is, for example, 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 can communicate with a satellite that directly provides a radio access connection to the UE in the manner described herein. The CN device 1436 can be one or more devices that make up the CN, as described herein.
[0166] 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.
[0167] 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.
[0168] 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) according to 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).
[0169] For RAN equipment 1418 as a terrestrial base station, network equipment signaling 1434 may occur on a feeder link between the wireless device 1402 and the satellite and on 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).
[0170] The wireless device 1402 may include one or more antennas 1412 (e.g., one, two, four, or more). For embodiments 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 multiple antennas used at each of the transmitting device and the receiving device to implement this aspect). MIMO transmission 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).
[0171] 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).
[0172] 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 provide input and / or output to the UE. Other interfaces of such a UE may be composed of transmitters, receivers, and other circuits that allow the UE to communicate with other devices (e.g., in addition to the transceiver 1410 / antenna 1412 described above), and may communicate according to known protocols (e.g., etc.) to perform the operation.
[0173] 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.
[0174] 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.
[0175] 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.
[0176] 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.
[0177] The RAN device 1418 may include one or more transceivers 1426 that may include RF transmitter and / or receiver circuitry that uses an antenna 1428 of the RAN device 1418 to facilitate signaling (e.g., signaling 1434) transmitted or received by the RAN device 1418 with other devices (e.g., wireless device 1402) in accordance with a corresponding RAT.
[0178] The RAN device 1418 may include one or more antennas 1428 (e.g., 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.
[0179] 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.).
[0180] 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 circuit systems (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.
[0181] 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.
[0182] 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 for transmission by the RAN device 1418.
[0183] RAN device 1418 can communicate with CN device 1436 via interface 1446, which can be similar to Fig.13 Interface 1328 (for example, it can be S1 and / or NG interface, either of which can be divided into user plane and control plane parts).
[0184] 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.
[0185] 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 computer programs. Memory 1440 may also store data used by processor 1438 and results calculated by the processor.
[0186] 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 circuit systems, which enables the CN device 1436 to communicate with other equipment in the CN, and / or enables the CN device 1436 to communicate with external networks, computers, databases, etc., for the purpose of operating, managing, and maintaining the CN device 1436 or other equipment operably connected to the CN device.
[0187] For one or more embodiments, at least one of the components set forth in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, and / or methods as described herein. For example, a baseband processor as described herein in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples set forth herein. For another example, circuits associated with a UE, a base station, a network element, etc. as described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples set forth herein.
[0188] Unless otherwise expressly stated, any of the above embodiments may be combined with any other embodiment (or combination of embodiments). The foregoing description of one or more specific implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise form disclosed. In view of the above teachings, modifications and variations are possible or can be obtained from the practice of various embodiments.
[0189] 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.
[0190] 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.
[0191] It is well known that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized as meeting or exceeding 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 authorized use should be clearly indicated to users.
[0192] Although the foregoing has been described in considerable detail for the sake of clarity, it will be apparent that certain changes and modifications may be made without departing from the principles of the invention. It should be noted that there are many alternative ways to implement both the processes and the apparatus described herein. Therefore, the embodiments of the present invention should be regarded as illustrative rather than restrictive, and the specification is not limited to the details given herein, but may be modified within the scope and equivalents of the appended claims.
Claims
1. A method of a base station, the method comprising: sending ultra-compact downlink control information (DCI) to a user equipment (UE) scheduling one or more scheduled physical downlink shared channels (PDSCHs), the one or more scheduled physical downlink shared channels (PDSCHs) scheduling data PDSCHs; Sending the one or more scheduled PDSCHs to the UE; as well as The data PDSCH as scheduled by the one or more scheduling PDSCHs is sent to the UE.
2. The method according to claim 1, further comprising: A physical uplink control channel (PUCCH) with hybrid automatic repeat request acknowledgement (HARQ-ACK) signaling is received from the UE, the hybrid automatic repeat request acknowledgement (HARQ-ACK) signaling indicating that the UE decoded scheduling information from the one or more scheduling PDSCHs. The method according to claim 2 , wherein the ultra-compact DCI schedules the PUCCH. The method according to claim 2 , wherein the one or more scheduled PDSCHs schedule the PUCCH. 5 . The method of claim 1 , further comprising transmitting a system information block (SIB) including configuration information for the ultra-compact DCI. 6 . The method of claim 1 , further comprising transmitting a system information block (SIB) including configuration information for the one or more scheduled PDSCHs.
7. The method of claim 1 , further comprising sending a system information block (SIB) including configuration information for a physical uplink control channel (PUCCH) used for hybrid automatic repeat request acknowledgement (HARQ-ACK) signaling corresponding to the one or more scheduled PDSCHs.
8. The method of claim 1, wherein the one or more scheduled PDSCHs schedule the data PDSCH using a medium access control control element (MAC CE).
9. The method of claim 1, wherein the one or more scheduled PDSCHs comprise PDSCH repetitions.
10. The method of claim 1, further comprising receiving hybrid automatic repeat request acknowledgement (HARQ-ACK) signaling from the UE indicating that the UE received the data PDSCH.
11. A method of a user equipment (UE), the method comprising: receiving ultra-compact downlink control information (DCI) scheduling one or more scheduled physical downlink shared channels (PDSCHs) from a base station, the one or more scheduled physical downlink shared channels (PDSCHs) scheduling data PDSCHs; receiving the one or more scheduling PDSCHs from the base station; as well as The data PDSCH is received from the base station as scheduled by the one or more scheduling PDSCHs.
12. The method according to claim 11, further comprising: A physical uplink control channel (PUCCH) with hybrid automatic repeat request acknowledgement (HARQ-ACK) signaling is transmitted to the base station, the hybrid automatic repeat request acknowledgement (HARQ-ACK) signaling indicating that the UE decoded scheduling information from the one or more scheduling PDSCHs. The method according to claim 12 , wherein the ultra-compact DCI schedules the PUCCH. The method of claim 12 , wherein the one or more scheduled PDSCHs schedule the PUCCH.
15. The method of claim 11, further comprising receiving a system information block (SIB) including configuration information for the ultra-compact DCI.
16. The method of claim 11, further comprising receiving a system information block (SIB) including configuration information for the one or more scheduled PDSCHs.
17. The method of claim 11, further comprising receiving a system information block (SIB) comprising configuration information for a physical uplink control channel (PUCCH) used for hybrid automatic repeat request acknowledgement (HARQ-ACK) signaling corresponding to the one or more scheduled PDSCHs.
18. The method of claim 11, wherein the one or more scheduled PDSCHs schedule the data PDSCH using a medium access control control element (MAC CE).
19. The method of claim 11, wherein the one or more scheduled PDSCHs comprise PDSCH repetitions.
20. The method of claim 11, further comprising transmitting, to the base station, hybrid automatic repeat request acknowledgement (HARQ-ACK) signaling indicating that the UE received the data PDSCH.
21. A method of a base station, the method comprising: sending ultra-compact downlink control information (DCI) to a user equipment (UE) scheduling one or more scheduled physical downlink shared channels (PDSCHs) that schedule a physical uplink shared channel (PUSCH); sending the one or more scheduled PDSCHs to the UE; and The PUSCH is received from the UE as scheduled by the one or more scheduling PDSCHs.
22. The method according to claim 21, further comprising: A physical uplink control channel (PUCCH) with hybrid automatic repeat request acknowledgement (HARQ-ACK) signaling is received from the UE, the hybrid automatic repeat request acknowledgement (HARQ-ACK) signaling indicating that the UE decoded scheduling information from the one or more scheduling PDSCHs.
23. The method of claim 22, wherein the ultra-compact DCI schedules the PUCCH.
24. The method of claim 22, wherein the one or more scheduled PDSCHs schedule the PUCCH.
25. The method of claim 21, further comprising transmitting a system information block (SIB) including configuration information for the ultra-compact DCI.
26. The method of claim 21, further comprising transmitting a system information block (SIB) including configuration information for the one or more scheduled PDSCHs.
27. The method of claim 21, further comprising sending a system information block (SIB) comprising configuration information for a physical uplink control channel (PUCCH) used for hybrid automatic repeat request acknowledgement (HARQ-ACK) signaling corresponding to the one or more scheduled PDSCHs.
28. The method of claim 21, wherein the one or more scheduled PDSCHs schedule the PUSCH using a medium access control control element (MAC CE).
29. The method of claim 21, wherein the one or more scheduled PDSCHs comprise PDSCH repetitions.
30. A method of a user equipment (UE), the method comprising: receiving, from a base station, ultra-compact downlink control information (DCI) scheduling one or more scheduled physical downlink shared channels (PDSCHs) scheduling a physical uplink shared channel (PUSCH); receiving the one or more scheduling PDSCHs from the base station; as well as The PUSCH as scheduled by the one or more scheduling PDSCHs is sent to the base station.
31. The method of claim 30, further comprising: A physical uplink control channel (PUCCH) with hybrid automatic repeat request acknowledgement (HARQ-ACK) signaling is transmitted to the base station, the hybrid automatic repeat request acknowledgement (HARQ-ACK) signaling indicating that the UE decoded scheduling information from the one or more scheduling PDSCHs.
32. The method of claim 31, wherein the ultra-compact DCI schedules the PUCCH.
33. The method of claim 31, wherein the one or more scheduled PDSCHs schedule the PUCCH.
34. The method of claim 30, further comprising receiving a system information block (SIB) including configuration information for the ultra-compact DCI.
35. The method of claim 30, further comprising receiving a system information block (SIB) comprising configuration information for the one or more scheduled PDSCHs.
36. The method of claim 30, further comprising receiving a system information block (SIB) comprising configuration information for a physical uplink control channel (PUCCH) used for hybrid automatic repeat request acknowledgement (HARQ-ACK) signaling corresponding to the one or more scheduled PDSCHs.
37. The method of claim 30, wherein the one or more scheduled PDSCHs schedule the PUSCH using a medium access control control element (MAC CE).
38. The method of claim 30, wherein the one or more scheduled PDSCHs comprise PDSCH repetitions.
39. An apparatus comprising means for performing the method according to any one of claims 1 to 38.
40. 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 38.
41. An apparatus comprising logic components, modules or circuits for performing the method of any one of claims 1 to 38.
