Patent Application
20240340888
The invention is directed to the field of Narrow Band Internet of Things (NB-IoT) non-terrestrial network (NTN), where NB-IoT devices are connected to the gNodeB (gNB) through a satellite.
The 3rd Generation Partnership Project (3GPP) started to extend its 5th Generation (5G) wireless standard to support mobile access through satellites. The Narrow Band Internet of Things (NB-IoT), as a part the 5G standard, is also supporting wireless access through Low/Medium/Geostationary Earth Orbit (LEO/MEO/GEO) satellites. In the context of 5G standard, a network with satellite support is called a non-terrestrial network (NTN).
To enhance the scheduling efficiency in Uplink (UL) and Downlink (DL) directions, 3GPP has already included multi-Transmission Block (TB) scheduling capability in the specification for NB-IoT (npusch-MultiTB-Config and npdsch-MultiTB-Config for UL and DL, respectively), which means multiple TBs can be scheduled using single Downlink Control Information (DCI). In NB-IoT case, because of the limited number of Hybrid Automatic Repeat Request (HARQ) processes, a maximum of two TBs can be scheduled. Therefore, only a single bit in DCI is assigned to indicate the number of scheduled TBs (“Number of scheduled TB” field in DCI). According to Table 1, this solution increases the User Equipment (UE) UL peak data rate by 98%, 84%, 79%, and 55% for GEO, LEO1200, LEO600, and terrestrial NB-IoT.
One of the main characteristics of the NTN is the longer Round Trip Time (RTT) compared to the terrestrial network. The long RTT is due to the very long distance between the satellite in the sky and the User Equipment (UE)/gNB on the surface of the earth. On the other hand, due to the limited number of HARQ processes in NB-IoT (e.g., currently 2), and due to the constrained size of Downlink Control Information (DCI), the number of uplink (UL)/downlink (DL) transmissions scheduled by a single DCI is limited. The protocol limitations in NB-IoT along with the long RTT in NTN will result in a long cycle for scheduling UE using DCI over Narrowband Physical Downlink Control Channel (NPDCCH) and the subsequent UL/DL transmission over Narrowband Physical Uplink Shared Channel (NPUSCH)/Narrowband Physical Downlink Shared Channel (NPDSCH). This long cycle, in turn, will reduce the UE and network peak data rate. This issue is more prominent in the UL direction.
The maximum transport block size (TBS) is 2536 bits. The shortest RU allocation to reach this TBS is when IRU=4 (or NRU=5). The minimum value for k0 is 8. Assuming the reference point on gNB (hence, kmac=0) and based on the mentioned values, the peak data rate values for different scenarios are given in Table 1. Table 1 shows the UE UL peak data rate highlighting the impact of RTT as well as the impact of multi-TB scheduling.
The following two points regarding the results presented in Table 1 should be noted:
In summary, the UL scheduling in NTN is a costly process and the current NB-IoT specification only allows up to two TBs scheduling using a single DCI N0. On the other hand, increasing the number of TBs scheduled by a single DCI N0 requires additional HARQ processes and additional bits in DCI N0. All these constraints will limit the achievable UL data rate.
Accordingly, there is a need for a system that facilitates NB-IoT devices connected to the gNodeB (gNB) through a satellite that overcomes, alleviates, and/or mitigates one or more of the aforementioned and other deleterious effects described above.
Accordingly, it is desired to provide a system and method in the field of Narrow Band Internet of Things (NB-IoT) non-terrestrial network (NTN), where NB-IoT devices are connected to the gNodeB (gNB) through a satellite.
It is further desired to provide a system and method that increases the peak data rate that can be achieved for NB-IoT.
It is still further desired to provide a system and method that enhances scheduling efficiency in HARQ-ACK disabled IoT NTN.
In one configuration, a system is provided that is based on a feature developed for NR and NB-IoT NTN, referred to as HARQ feedback disabling, where the method is applied on HARQ feedback-disabled UEs.
The system and method may employ the unused bits of DCI for a HARQ feedback-disabled UE to indicate scheduling of more than two TBs. In this way, the method has a minor specification impact allowing the UE to re-interpret some unused bits in DCI when the HARQ feedback is disabled.
The enhancements in UE UL peak data rate comparing to two-TB scheduling case are 97%, 72%, 65%, and 38% for GEO, LEO1200, LEO600, and terrestrial NB-IoT.
For this application the following terms and definitions shall apply:
The term “data” as used herein means any indicia, signals, marks, symbols, domains, symbol sets, representations, and any other physical form or forms representing information, whether permanent or temporary, whether visible, audible, acoustic, electric, magnetic, electromagnetic or otherwise manifested. The term “data” as used to represent predetermined information in one physical form shall be deemed to encompass any and all representations of the same predetermined information in a different physical form or forms.
The term “network” as used herein includes both networks and internetworks of all kinds, including the Internet, and is not limited to any particular type of network or inter-network.
The terms “first” and “second” are used to distinguish one element, set, data, object or thing from another, and are not used to designate relative position or arrangement in time.
The terms “coupled”, “coupled to”, “coupled with”, “connected”, “connected to”, and “connected with” as used herein each mean a relationship between or among two or more devices, apparatus, files, programs, applications, media, components, networks, systems, subsystems, and/or means, constituting any one or more of (a) a connection, whether direct or through one or more other devices, apparatus, files, programs, applications, media, components, networks, systems, subsystems, or means, (b) a communications relationship, whether direct or through one or more other devices, apparatus, files, programs, applications, media, components, networks, systems, subsystems, or means, and/or (c) a functional relationship in which the operation of any one or more devices, apparatus, files, programs, applications, media, components, networks, systems, subsystems, or means depends, in whole or in part, on the operation of any one or more others thereof.
As used herein, the phrases “at least one,” “one or more,” “or,” and “and/or” are open-ended expressions that are both conjunctive and disjunctive in operation. For example, each of the expressions “at least one of A, B and C,” “at least one of A, B, or C,” “one or more of A, B, and C,” “one or more of A, B, or C,” “A, B, and/or C,” and “A, B, or C” means A alone, B alone, C alone, A and B together, A and C together, B and C together, or A, B and C together.
The term “automatic” and variations thereof, as used herein, refers to any process or operation done without material human input when the process or operation is performed. However, a process or operation can be automatic, even though performance of the process or operation uses material or immaterial human input, if the input is received before performance of the process or operation. Human input is deemed to be material if such input influences how the process or operation will be performed. Human input that consents to the performance of the process or operation is not deemed to be “material.”
In one configuration, a method for increasing a peak data rate that can be achieved in HARQ feedback-disabled User Equipment (UE) in a Narrow Band Internet of Things (NB-IoT) non-terrestrial network (NTN) system where NB-IoT devices are connected to the gNodeB (gNB) through a satellite is provided, the method comprising the steps of: receiving Downlink Control Information (DCI) NO at UE, and the UE checking a Hybrid Automatic Repeat Request (HARQ) process number field. The method further comprises the steps of: confirming HARQ feedback is disabled for the indicated HARQ process number; and determining an actual number of scheduled Transmission Blocks (TB) in an Uplink based on a New Data Indicator field and a Number of Scheduled TBs for Unicast field in the DCI N0. The method is provided such that the actual number of scheduled TBs is greater than two.
In another configuration, a HARQ-ACK resource field and the New Data Indicator field are used along with the Number of Scheduled TBs for Unicast field (6 bits in total) to indicate a total number of total scheduled TBs.
In one configuration a method for increasing a peak data rate in HARQ feedback-disabled User Equipment (UE) in a Narrow Band Internet of Things (NB-IoT) non-terrestrial network (NTN) system where the UE is connected to a gNodeB (gNB) through a satellite is provided, the method comprising the steps of: receiving Downlink Control Information (DCI) NO at the UE, and the UE checking a Hybrid Automatic Repeat Request (HARQ) process number field in the DCI N0. The method further comprises the steps of: the UE confirming that HARQ feedback is disabled for the HARQ process number field, and the UE determining a number of scheduled Transmission Blocks (TB) in an Uplink (UL) based on a New Data Indicator (NDI) field and a Number of Scheduled TBs for Unicast field in the DCI N0. The method is provided such that the number of scheduled TBs being greater than two without adding new bits to the DCI N0.
In another configuration a system for increasing a peak data rate in HARQ feedback-disabled User Equipment (UE) in a Narrow Band Internet of Things (NB-IoT) non-terrestrial network (NTN) system is provided where the UE is connected to a gNodeB (gNB) through a satellite, the system comprising: software executing on a server transmitting Downlink Control Information (DCI) NO via gNodeB (gNB) to a gateway to a satellite and to UE. The system is provided such that the UE checks a Hybrid Automatic Repeat Request (HARQ) process number field in the DCI N0 and confirms that HARQ feedback is disabled for the HARQ process number field. The system is further provided such that the UE determines a number of scheduled Transmission Blocks (TB) in an Uplink (UL) based on a New Data Indicator (NDI) field and a Number of Scheduled TBs for Unicast field in the DCI N0. Finally, the system is provided such that the number of scheduled TBs is greater than two without adding new bits to the DCI N0.
The above-described and other features and advantages of the present disclosure will be appreciated and understood by those skilled in the art from the following detailed description, drawings, and appended claims.
Referring now to the drawings, wherein like reference numerals designate corresponding structure throughout the views.
Satellite 106 is called a NTN payload in 3GPP and can be either bent-pipe or regenerative payload. A bent-pipe payload does not have any functionality of radio access network (RAN). It is referred to as a bent-pipe as it represents the U-shape flow of signals since a transponder is just a signal repeater that bounces back any signals received after they are processed and amplified. In essence, bent pipe means a satellite system that transmits to an Earth station essentially the same signal it receives. A regenerative payload implements some of RAN capabilities. The regenerative payload “regenerates” or transforms and amplifies an uplink RF signal with signal-processing techniques before transmitting it on a downlink. The current system is usable with either bent-pipe or regenerative payloads.
As stated previously, NTN requires longer Round Trip Time (RTT) when compared to terrestrial networks due to long distances between satellites and surface-located User Equipment (UE)/gNB. Additionally, the number of uplink (UL)/downlink (DL) transmissions scheduled by a single Downlink Control Information (DCI) is limited due to 1) the limited number (e.g., two) of Hybrid Automatic Repeat Request (HARQ) processes in NB-IoT and 2) that constrained size of DCI. These protocol limitations in conjunction with the long RTT results in a long cycle for scheduling UE using DCI over NPDCCH and the subsequent UL/DL transmission over NPUSCH/NPDSCH, which functions to reduce the UE and network peak data rate. This issue is illustrated in
To quantify this impact and to form a basis for future comparison, peak UE UL data rate for single-TB and two-TB scheduling scenarios are calculated. For this purpose, one cycle of NPDCCH scheduling and NPUSCH transmission is illustrated for single-TB cases in
Accordingly, as was stated previously, the current NB-IoT specification only allows up to two TBs scheduling using a single DCI N0. Likewise, increasing the number of TBs scheduled by a single DCI N0 requires additional HARQ processes and additional bits in DCI N0. As such, the UL data rate is severely limited.
HARQ feedback disabling is available for NB-IoT NTN such that the gNB can configure UE with a HARQ feedback disabled HARQ process. Therefore, any DL transmission that is occurring through this HARQ process will not have HARQ ACK/NACK feedback, and hence, no Media Access Control (MAC) layer retransmission. It should be noted that the MAC layer is a part of the data link protocol that controls access to the physical transmission medium in local networks. Similarly, any UL transmission that is occurring through this HARQ process will not have a MAC layer retransmission. In other words, from a MAC layer perspective, any transmitted packet is a new packet and there will be no retransmission. This means that the “New data indicator (NDI)” field in DCI N0 and DCI N1 has no application for a NPUSCH/NPDSCH transmission through a HARQ feedback disabled HARQ process.
However, the HARQ disabled HARQ process is available for the next transmission, right after the end of a first transmission. In other words, gNB does not need to wait until implicit/explicit confirmation of successful reception of one transmission to schedule another transmission using the same HARQ process.
Finally, as previously discussed, the UL scheduling in IoT NTN is a costly process, because there is one RTT between DCI N0 and the corresponding NPUSCH. As such, it would be good to facilitate the gNB to schedule as many TBs as possible using a single DCI.
It should be noted that, while various functions and methods will be described and presented in a sequence of steps, the sequence has been provided merely as an illustration of one advantageous configuration, and that it is not necessary to perform these functions in the specific order illustrated. It is further contemplated that any of these steps may be moved and/or combined relative to any of the other steps. In addition, it is still further contemplated that it may be advantageous, depending upon the application, to utilize all or any portion of the functions described herein.
In one configuration a method uses the NDI bit in DCI N0 together with a “Number of scheduled TB for Unicast” field to indicate scheduling of up to four TBs using a single DCI and through a HARQ feedback disabled HARQ process. These two fields in the structure of DCI N0 are highlighted in Table 2 shown below for DCI Format NO.
The obtained gain using the proposed multi-TB scheduling is illustrated in
To quantify the obtained gain by deploying this configuration, the result presented in Table 1 is extended to a four-TB scheduling scenario. The peak data rate of UE in UL direction in different scenarios is presented in Table 3. When compared with conventional two-TB scheduling, a 97%, 72%, 65%, and 38% improvement in UE data rate for GEO, LEO1200, LEO600, and terrestrial NB-IoT is observed.
One important aspect of this system and method is that the obtained gain is achieved without adding new bits to DCI N0, or any extra communication overhead. The only change needed to incorporate the proposed enhancement is to re-interpret the NDI bit of DCI N0, when the transmission is through HARQ feedback-disabled HARQ process.
DCI N0 has a bit length/size of 23 and is used for UL Grant (NPUSCH Scheduling). The bits are allocated as follows:
In one configuration, the UEs behavior regarding interpreting DCI bits is explained as follows:
Note that all the transmitted TBs scheduled by this DCI N0 uses the same HARQ feedback disabled HARQ process.
In another configuration, the same principle is applied to DL scheduling and transmission. For DL transmissions through a HARQ feedback-disabled HARQ process, the unused bits of DCI N1 can be used to indicate multiple TB scheduling (beyond conventional two-TB transmission). For example, “HARQ-ACK resource” field and “New data indicator” field can be used along with “Number of scheduled TB for Unicast” field (6 bits in total) to indicate the number of total scheduled TBs. Note that the first two fields need to be reinterpreted for a HARQ feedback disabled case to be used as part of the number of scheduled TB indicator.
While the present disclosure has been described with reference to one or more exemplary embodiments, it will be understood by those skilled in the art that various changes may be made and equivalents may be substituted for elements thereof without departing from the scope of the present disclosure. In addition, many modifications may be made to adapt a particular situation or material to the teachings of the disclosure without departing from the scope thereof. Therefore, it is intended that the present disclosure not be limited to the particular embodiment(s) disclosed as the best mode contemplated, but that the disclosure will include all embodiments falling within the scope of the appended claims.
This application claims the benefit of U.S. Application 63/494,856, filed Apr. 7, 2023 the contents of which are incorporated by reference herein.
| Number | Date | Country | |
|---|---|---|---|
| 63494856 | Apr 2023 | US |
