Transmission extension in non-terrestrial wireless networks

Abstract

Disclosed are methods, systems, and computer-readable medium to perform operations including: interfacing with a transceiver to receive an uplink (UL) transmission extension command from a non-terrestrial network (NTN); responsive to receiving the UL transmission extension command, determining whether a value of a time alignment timer is first predetermined value or second predetermined value; and selecting, based on whether the value of the time alignment timer is the first predetermined value or the second predetermined value, an initial value for an UL transmission extension duration timer.

Description

TRANSMISSION EXTENSION IN NON-TERRESTRIAL WIRELESS NETWORKSCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims priority to U.S. Provisional Application No. 63 / 554,706, filed on February 16, 2024, which is incorporated herein by reference in its entirety.BACKGROUND

[0002] Wireless communication networks provide integrated communication platforms and telecommunication services to wireless user devices. Example telecommunication services include telephony, data (e.g., voice, audio, and / or video data), messaging, and / or other services. The wireless communication networks have wireless access nodes that exchange wireless signals with the wireless user devices using wireless network protocols, such as protocols described in various telecommunication standards promulgated by the Third Generation Partnership Project (3GPP). Example wireless communication networks include time division multiple access (TDMA) networks, frequency-division multiple access (FDMA) networks, orthogonal frequency-division multiple access (OFDMA) networks, Long Term Evolution (LTE), and Fifth Generation New Radio (5G NR). The wireless communication networks facilitate mobile broadband service using technologies such as OFDM, multiple input multiple output (MIMO), advanced channel coding, massive MIMO, beamforming, and / or other features.

[0003] More recently, to increase network coverage and support use cases that are beyond the capabilities of ground-based (e.g., terrestrial) infrastructure, 3GPP has released standards that introduce a non -terrestrial network (NTN) that uses airborne or space-borne platforms (e.g., non-geo- stationary satellites) to serve as access nodes or base stations. A non-terrestrial network can be integrated with terrestrial infrastructure, e.g., 5G NR infrastructure, to supplement the network coverage of the terrestrial infrastructure. A non-terrestrial network can also be used to independently provide network coverage to devices, e.g., Internet of Things (loT) devices, that are located in areas without terrestrial network coverage.SUMMARY

[0004] In accordance with one aspect of the present disclosure, a method involves receiving an uplink (UL) transmission extension command from a non-terrestrial network (NTN); responsive to receiving the UL transmission extension command, determining whether a value of a time alignment timer is first predetermined value or second predetermined value; and selecting, based on whether the value of the time alignment timer is the first predetermined value or the second predetermined value, an initial value for an UL transmission extension duration timer.

[0005] Other versions include corresponding systems, apparatus that include one or more processors, and computer programs to perform the actions of methods defined by instructions encoded on computer readable storage devices. These and other versions may optionally include one or more of the following features.

[0006] In some implementations, the UL transmission extension command is a Medium Access Control (MAC) Control Element (CE).

[0007] In some implementations, the MAC CE includes a first bit including the UL transmission extension command.

[0008] In some implementations, the MAC CE is a GNSS measurement command MAC CE.

[0009] In some implementations, the GNSS measurement command MAC CE includes one or more bits repurposed as the UL transmission extension command.

[0010] In some implementations, the method further involves interfacing with the transceiver to receive an information element (IE) that includes the value of the time alignment timer.

[0011] In some implementations, determining whether a value of a time alignment timer is the first predetermined value or the second predetermined value involves determining that the value of the time alignment timer is the first predetermined value, and where setting, based on whether the value of the time alignment timer is the first predetermined value or the second predetermined value, an initial value for an UL transmission extension duration timer involves setting the initial value for the UL transmission extension duration timer as a configured parameter Y.

[0012] In some implementations, determining whether a value of a time alignment timer is the first predetermined value or the second predetermined value involves determining that thevalue of the time alignment timer is the second predetermined value, and where setting, based on whether the value of the time alignment timer is the first predetermined value or the second predetermined value, an initial value for an UL transmission extension duration timer involves setting the initial value for the UL transmission extension duration timer equal to the value of the time alignment timer.

[0013] In some implementations, where, after the UL transmission extension command is received, a transmission extension duration starts after a GNSS validity duration expires or the UL transmission extension duration timer expires.

[0014] In some implementations, the transmission extension duration starts at the point of the end of a subframe in which the UL transmission extension command is received.

[0015] In some implementations, the method further involves interfacing with the transceiver to report an UL transmission extension capability.

[0016] In some implementations, the capability includes an indication whether the UL transmission extension capability operates when the time alignment timer is the first predetermined value, the second predetermined value, or both.

[0017] In some implementations, the first predetermined value is infinity and the second predetermined value is not infinity.

[0018] The details of one or more embodiments of these systems and methods are set forth in the accompanying drawings and the description below. Other features, objects, and advantages of these systems and methods will be apparent from the description and drawings, and from the claims.BRIEF DESCRIPTION OF THE FIGURES

[0019] FIG. 1 illustrates an example non-terrestrial network (NTN).

[0020] FIG. 2 illustrates a timing advance command Medium Access Control (MAC) Control Element (CE).

[0021] FIG. 3 A illustrates a new extension command MAC CE.

[0022] FIG. 3B illustrates a global navigation satellite systems (GNSS) Measurement Command MAC CE.

[0023] FIG. 4 A and FIG. 4B illustrate example extension duration start time options.

[0024] FIG. 5 illustrates an example uplink (UL) transmission extension.

[0025] FIG. 6A illustrates a flowchart of an example method.

[0026] FIG. 6B illustrates a flowchart of another example method.

[0027] FIG. 7 illustrates an example user equipment (UE).

[0028] FIG. 8 illustrates an example access node.DETAILED DESCRIPTION

[0029] A non-terrestrial network (NTN) is a network that includes non-terrestrial flying equipment that serve as access nodes to user equipment (UEs). An NTN can include satellites, high-altitude platform systems (HAPS), an air-to-ground network, and low-altitude unmanned aerial vehicles (UAVs), among other equipment. Due to the relative movements of a UE and / or a satellite serving the UE, the UE can suffer from a Doppler frequency shift and lose synchronization with the satellite (and by extension the NTN).

[0030] To overcome the Doppler frequency shift, a UE can take actions based on a global navigation satellite system (GNSS) location of the UE. Specifically, a UE with GNSS capabilities communicates with a GNSS to determine the UE’s position. The UE then calculates, based on its position, the relative speed between the UE and the NTN satellite, as well as the round-trip time (RTT) between the UE and the satellite. From the relative speed, the UE calculates and applies a pre-compensation for the Doppler frequency shift to ensure that the UE’s service link or uplink (UL) signal is received at the NTN satellite on the desired frequency. The UE’s position is considered valid for a duration called a GNSS validity duration. Once this duration expires, the UE must reacquire its GNSS position by communicating with the GNSS before the UE can perform UL communications with the NTN.

[0031] One of the objectives of Release 18 of the 3GPP work items is to enhance GNSS operations, e.g., for Narrowband-Internet of Things / enhanced Machine Type Communication (NB-IoT / eMTC) devices. Specifically, the objective is to improve GNSS operations for a new position fix for UE pre-compensation during long connection times and for reduced power consumption. One limitation, however, is that UEs, e.g., NB-IoT / eMTC devices, are assumed to not be able to perform simultaneous GNSS and NTN operations (for power saving purposes).

[0032] This disclosure describes systems and methods for enhancing GNSS and NTN operations. In some implementations, the systems and methods extend under certain conditions an UL transmission duration after a GNSS validity duration expires, thereby allowing a UE to perform UL transmissions to the NTN without first performing GNSS reacquisition. As described in more detail below, doing so saves power as the UE can continue to perform UL transmissions to the NTN without first reacquiring the UE’s location from the GNSS.

[0033] FIG. 1 illustrates an example non -terrestrial network (NTN) 100, according to some implementations. Generally, the non-terrestrial network 100 can include any network that uses non-terrestrial components, such as satellites, airplanes, and UAVs, to provide networkcoverage to a UE. In the example of FIG. 1, the non-terrestrial network 100 includes a nongeo-stationary satellite 102 (“satellite 102”) that has a moving coverage area 104. The nonterrestrial network 100 also includes a core network 106, e.g., a 4G or 5G core network. Although FIG. 1 shows the satellite 102 directly coupled to the core network 106 via link 110, the satellite 102 may alternatively be indirectly coupled to the core network 106, perhaps via a terrestrial base station (not illustrated). In such examples, the link between the satellite 102 and the terrestrial base station is called a feeder link.

[0034] The non-terrestrial network 100 can serve UEs that are located in a coverage area of one of the non-terrestrial components of the network. For example, the non-terrestrial network 100 can serve a UE 108 when the UE is located within the coverage area 104. The UE 108 and any other UE in the system may be, for example, laptop computers, smartphones, tablet computers, machine-type devices, intelligent transportation systems, loT devices, NB- loT / eMTC devices, or any other wireless devices with or without a user interface. The nonterrestrial network 100 can provide the UE 108 with network connectivity to a broader network (not shown in FIG. 1), such as the Internet.

[0035] In some implementations, the satellite 102 provides network services to UEs via a service link. The satellite 102 can implement either a transparent payload or a regenerative payload. A transparent payload refers to an arrangement in which the satellite 102 receives a signal and transmits an amplified version of the signal. For example, the satellite 102 receives uplink communications from the UE 108 on service link frequencies and transmits an amplified version of the signal to the core network 106 on feeder link frequencies or may receive downlink communications from the core network 106 on the feeder link frequencies and transmit an amplified version of the signal to the UE 108 on the service link frequencies.

[0036] A regenerative payload refers to an arrangement in which the satellite 102 acts as a distributed unit (DU) or a base station (e.g., access node 800 in FIG. 8). In this arrangement, the satellite 102 regenerates received signals with signal-processing techniques (e.g., demodulation, decoding, switching, encoding, modulation, etc.) before being retransmitted. The satellite 102 generates one or more beams over a service area bounded by its field of view, which can depend on the antenna diagram and minimum elevation angle of the satellite. The coverage areas of the beams are typically elliptically shaped, e.g., the coverage area 104.

[0037] The example shown in FIG. 1 is not intended to limit the exemplary embodiments in any way. The non-terrestrial network 100 may be integrated with a 5GNR radio access network(RAN) and / or other networks in any of a variety of manners. For example, the non-terrestrial network 100 may include a low earth orbit (LEO) constellation including an array of satellites and gateways with broad interconnectivity via ground-to-ground station (G2G) links, satellite- to-satellite (S2S) links, ground-to-satellite (G2S) links, and satellite-to-ground (S2G) links. Other types of satellite-based NTNs include geostationary-orbiting (GEO) satellites or medium-earth-orbiting (MEO) satellites. Additionally, the non-terrestrial network 100 may include more than one satellite that provides coverage to the UE 108 at overlapping or different times.

[0038] In line with the discussion above, one aspect of GNSS operation enhancement is extending the duration over which a UE can communicate with the non-terrestrial network 100. Under this enhancement, the UL transmission to the NTN is allowed in an extension duration “X” after the original GNSS validity duration expires without the need for GNSS reacquisition. This UL transmission extension can be used when certain conditions are satisfied, for example, when a frequency error and a timing error are within predefined frequency and timing error requirements (with a closed loop time correction). This mechanism is especially useful for low power UEs, e.g., NB-IoT / eMTC devices, since extending the GNSS validity duration without GNSS reacquisition saves device power. This disclosure describes configurations of the UL transmission extension, timers that track the UL transmission extension, and extension commands that trigger the UL transmission extension.

[0039] In some implementations, the length of the extension duration X depends on an information element (IE) TimeAlignmentTimer sent from the non-terrestrial network 100 to the UE 108, perhaps via higher layer signaling, e.g., Radio Resource Control (RRC) signaling. The IE TimeAlignmentTimer carries one of the following values {sf500, sf75O, sfl280, sfl920, sf2560, sf5120, sfl0240, infinity}, where sf is subframe. This IE sets the value of a UE timer called timeAlignmentTimer . The IE TimeAlignmentTimer is described in 3GPP TS 36.311 and the timeAlignmentTimer is described in 3GPP TS 36.321.

[0040] In some implementations, the length of the extension duration X depends on whether the IE TimeAlignmentTimer is set to infinity or to a value not infinity (e.g., sf500, sf75O, sfl280, etc.). When TimeAlignmentTimer is not set to infinity, the UE is configured to set the duration X equal to the time remaining on the timeAlignmentTimer. And when the IE TimeAlignmentTimer is set to infinity, the UE is configured to set the duration X equal to a parameter Y that the non-terrestrial network 100 configures to the UE (e.g., via RRC signalingor an extension command, as described in more detail below). In one example, the nonterrestrial network 100 configures the parameter Y using a 3 -bit field that can have the following values [sf500, sf75O, sfl280, sfl920, sf2560, sf5120, sfl0240]. Upon receiving the parameter Y from the non-terrestrial network 100, the UE sets a new timer called ULTransmissionExtensionTimer to the value of the parameter Y. Thus, when the IE TimeAlignmentTimer is infinity, the end of the duration X is at the point when the new timer ULTransmissionExtensionTimer expires. The UE can be configured to reset, after receiving the parameter Y, the ULTransmissionExtensionTimer using the parameter each time the UE receives an extension command from the non-terrestrial network 100.

[0041] In some implementations, the non-terrestrial network 100 uses an extension command to trigger the UE 108 to extend the UL transmission duration after the GNSS validity duration expires. The UE 108, upon receiving the extension command, extends the UL transmission duration for the duration X.

[0042] In some implementations, the non-terrestrial network 100 is configured to reuse an existing timing advance command MAC CE as the UL transmission duration extension command. In one option, the non-terrestrial network 100 reuses an existing timing advance command MAC CE as the extension command. In another option, the non-terrestrial network 100 reinterprets certain bits, e.g., one or more of the Timing Advance Group Identifier (TAG Id) in the timing advance command MAC CE, as the extension command. Note that the TAG Id field is not otherwise used in the non-terrestrial network 100.

[0043] FIG. 2 illustrates a timing advance command MAC CE 200, according to some implementations. In some implementations, the non-terrestrial network 100 is configured to reuse an existing timing advance command MAC CE 200 as the UL transmission duration extension command. In one option, the non -terrestrial network 100 directly reuses the timing advance command MAC CE 200 as the extension command. In this option, the UE 108 is configured to assume that an extension command has been received if the UE receives a timing advance command MAC CE from the non-terrestrial network 100. In another option, the nonterrestrial network 100 reinterprets the TAG Id bit(s) as the extension command. In this option, if one of the TAG Id bit(s) is set to “1,” the UE 108 assumes that an extension command has been received.

[0044] In some implementations, the non-terrestrial network 100 is configured to use a message other than the timing advance command MAC CE as the extension command. Asdescribed in FIG. 3 A below, in a first option, the non-terrestrial network 100 is configured to use a newly defined MAC CE as the extension command. In a second option, as described in FIG. 3B below, the non-terrestrial network 100 is configured to repurpose a bit of an existing MAC CE as the extension command.

[0045] FIG. 3A illustrates a new extension command MAC CE 300, according to some implementations. In this option of using a newly defined MAC CE, the non-terrestrial network 100 uses 1 bit of the MAC CE 300, e.g., bit “C,” to indicate the UL transmission extension (e.g., “1” indicates that extending the UL transmission is allowed) and uses 3 bits of the MAC CE 300 to indicate the length of the duration X from the set of [sf500, sf75O, sfl280, sfl920, sf2560, sf5120, sfl0240]. As shown in FIG. 3 A, the MAC CE 300 also include reserve bits “R ”

[0046] FIG. 3B illustrates a GNSS Measurement Command MAC CE 310 that includes bits that are repurposed as an extension command, according to some implementations. In this example, the GNSS Measurement Command MAC CE 310 is an existing MAC CE whose bits can be reproposed as an extension command. Here, when the field “T” in the MAC CE 310 is set to “1,” one reserved bit, R, is used as the extension command. For example, the reserved bit having a value of “1” indicates an extension command. In this option, the bits dedicated for the GNSS measurement gap length are used to indicate the gap for autonomous GNSS measurements. When the field “T” in the MAC CE 310 is set to “0,” one reserved bit, R, is used as the extension command. Another reserved bit is used to indicate whether the remaining 4 bits in the MAC CE 310, i.e., the GNSS measurement gap length bits, are used to indicate a GNSS measurement gap length.

[0047] The possible extension commands and timers described above are summarized in the following tables.

[0048] As described, the disclosed systems and methods support two cases for UL transmission extension. In the first case, the IE TimeAlignmentTimer is configured with a value other than infinity, and the timer length of the UL transmission extension is duration X. In the second case, the IE TimeAlignmentTimer is configured with infinity, and the timer length of the UL transmission extension is configured by parameter Y.

[0049] In some implementations, a unified approach is applied to both cases to simplify the UE and base station implementation. In the unified approach, the combination of extension commands (Extension Command Type 1, Extension Command Type 2) and timer (Timer Type 1, Timer Type 2) is the same for both cases. The different possible combinations include: (Extension Command Type 1, Timer Type 1), (Extension Command Type 2, Timer Type 2), (Extension Command Type 1, Timer Type 2), and (Extension Command Type 2, Timer Type 1).

[0050] In some implementations, different approaches are defined for the two cases depending on whether the IE TimeAlignmentTimer is set to infinity or not. If the IE TimeAlignmentTimer is configured with infinity, the combination of (Extension Command Type 2, Timer Type 2) is applied. And there are two options if the TimeAlignmentTimer is not configured with infinity. In a first option, the combination of (Extension Command Type 1, Timer Type 1) is applied. In a second option, the combination of (Extension Command Type 2, Timer Type 1) is applied.

[0051] In some implementations, the wireless network is configured with different options for the start time of transmission extension duration X. In a first option, Start Time Option 1, the start time of duration X is at the point where original GNSS validity duration expires or the timer (with duration X) expires (if a first extension command has already been received). The extension command is received before the GNSS validity duration expires or before k subframes of the timer expiring, where k subframes is the processing time for downlink signaling handling. In a second option, Start Time Option 2, the start time of duration X is at the point where the end of subframe in which the extension command is received. In this option, the timer is reset after receiving the extension command.

[0052] FIG. 4A and FIG. 4B illustrate example extension duration start time options, according to some implementations. Specifically, FIG. 4A illustrates Start Time Option 1 and FIG. 4B illustrates Start Time Option 2. As shown in FIG. 4A, under Start Time Option 1, the extension duration starts after the GNSS validity duration expires or after the UL transmission extension timer expires. And as shown in FIG. 4B, under Start Time Option 2, the extension duration starts upon receipt of an extension command (or shortly thereafter).

[0053] In some implementations, the UE is configured to report the capability of supporting an UL transmission extension for one or more of the two cases of UL transmission extension: timeAlignmentTimer is configured with a value other than infinity, and timeAlignmentTimer is configured with infinity. The capability is reported per UE with Geostationary Satellite Orbit (GSO) and Non-Geostationary Satellite Orbit (NGSO) differentiation. The capability is reported per UE with NGSO; GSO is supported by default. In some implementations, the UE can also report the capability of supporting the configuration of duration X, duration Y, or both.

[0054] FIG. 5 illustrates an example UL transmission extension, according to some implementations. In this example, the UE reports to the NTN the UE’s capability of supporting configuration of duration X or Y or both. The NTN enables UL transmission extension and configures duration X or Y. Then, the UE in RRC connected state could perform the GNSS measurement according to the received aperiodic trigging signaling. The UE reports the remaining GNSS validity duration to the network. In response, the network sends the UL transmission extension command before the GNSS validity duration expires. After receiving the command, the UE assumes the UL transmission is allowed within the duration X. The starting point of X is end of subframe with extension command (Start Time Option 2 is assumed here). Before the duration X expires, the UE receives another extension command. Then, the UL transmission extension is again on top of previous extension period X, and the timer is reset. The starting point of duration X is end of subframe with the second extension command. If UE doesn’t receive the UL transmission extension command, duration X is ending at the point where timer expires. UE goes to idle mode or performs autonomous GNSS measurement according to network configuration.

[0055] FIG. 6A illustrates a flowchart of an example method 600, according to some implementations. For clarity of presentation, the description that follows generally describes method 600 in the context of the other figures in this description. For example, method 600 can be performed by UE 108 of FIG. 1. It will be understood that method 600 can be performed,for example, by any suitable system, environment, software, hardware, or a combination of systems, environments, software, and hardware, as appropriate. In some implementations, various steps of method 600 can be run in parallel, in combination, in loops, or in any order.

[0056] At step 602, method 600 involves receiving an uplink (UL) transmission extension command from a non-terrestrial network (NTN).

[0057] At step 604, method 600 involves in response to receiving the UL transmission extension command, determining an UL transmission extension duration.

[0058] At step 606, method 600 involves running a timer for UL transmission during the UL transmission extension duration.

[0059] In some implementations, the UL transmission extension command is a Medium Access Control (MAC) Control Element (CE).

[0060] In some implementations, the MAC CE is a timing advance command MAC CE.

[0061] In some implementations, the timing advance command MAC CE includes a Timing Advance Group Identifier (TAG Id) field including at least one bit, and wherein the at least one bit includes the UL transmission extension command.

[0062] In some implementations, the MAC CE includes: (i) a first bit including the UL transmission extension command, and (ii) three bits indicating the UL transmission extension duration.

[0063] In some implementations, the MAC CE is a GNSS measurement command MAC CE.

[0064] In some implementations, the GNSS measurement command MAC CE includes one or more bits repurposed as the UL transmission extension command.

[0065] In some implementations, determining an UL transmission extension duration involves receiving a TimeAlignmentTimer information element (IE); determining whether a value of the TimeAlignmentTimer IE is infinity or not infinity; and determining a length of the UL transmission extension duration based on whether the value of the TimeAlignmentTimer IE is infinity or not infinity.

[0066] In some implementations, determining the length of the UL transmission extension duration based on whether the value of the TimeAlignmentTimer IE is infinity or not infinity involves if the value of the TimeAlignmentTimer IE is infinity, setting the length of the ULtransmission extension duration equal to a configured parameter Y; and if the value of the TimeAlignmentTimer IE is not infinity, determining that the length of the UL transmission extension duration is the value of the TimeAlignmentTimer IE.

[0067] In some implementations, the running timer is determined based on: if the value of the TimeAlignmentTimer IE is infinity, the running timer is an ULTransmissionExtensionTimer, and if the value of the TimeAlignmentTimer IE is not infinity, running timer is TimeAlignmentTimer.

[0068] In some implementations, the running timer is a TimeAlignmentTimer.

[0069] In some implementations, the running timer is an ULTransmissionExtensionTimer.

[0070] In some implementations, the same UL transmission extension command is applied whether the value of TimeAlignmentTimer is infinite or not infinite.

[0071] In some implementations, determining the UL transmission extension duration involves receiving the UL transmission extension duration in higher layer signaling or in a Medium Access Control (MAC) Control Element (CE) that includes the transmission extension command.

[0072] In some implementations, after the UL transmission extension command is received, the transmission extension duration starts after a GNSS validity duration expires or the running timer expires.

[0073] In some implementations, the transmission extension duration starts at the point of the end of subframe where UL transmission extension command is received.

[0074] In some implementations, the UE reports the capability of UL transmission extension.

[0075] In some implementations, the capability includes TimeAlignmentTimer is infinity, or not infinity or both.

[0076] As described above, the IE TimeAlignmentTimer is specified in TS 36.331. More specifically, TS 36.331 specifies the IE TimeAlignmentTimer as follows:• TimeAlignmentTimer-. The IE TimeAlignmentTimer is used to configure the time alignment timer as specified in TS 36.321. The values are in ms.• TimeAlignmentTimer-. The IE TimeAlignmentTimer is used to control how long the UE considers the serving cells belonging to the associated TAG to be uplink time aligned.Corresponds to the Timer for time alignment in TS 36.321. Value in number of subframes. Value sf500 corresponds to 500 sub-frames, sf75O corresponds to 750 subframes and so on.TimeAlignmentTimer information element- ASN1 STARTTimeAlignmentTimer : := ENUMERATED { sf5OO, sf75O, sfl280, sfl920, sf2560, sf5120, sf 10240, infinity}- ASN1STOP

[0077] As also described above, the timer timeAlignmentTimer is specified in TS 36.321. More specifically, TS 36.321specifies the timer timeAlignmentTimer as follows:• timeAlignmentTimer in TS: The MAC entity has a configurable timer timeAlignmentTimer per TAG. The timeAlignmentTimer is used to control how long the MAC entity considers the Serving Cells belonging to the associated TAG to be uplink time aligned, as specified in TS 36.331.

[0078] FIG. 6B illustrates a flowchart of an example method 610, according to some implementations. For clarity of presentation, the description that follows generally describes method 610 in the context of the other figures in this description. For example, method 610 can be performed by UE 108 of FIG. 1. It will be understood that method 610 can be performed, for example, by any suitable system, environment, software, hardware, or a combination of systems, environments, software, and hardware, as appropriate. In some implementations, various steps of method 610 can be run in parallel, in combination, in loops, or in any order.

[0079] At step 612, method 610 involves interfacing with a transceiver to receive an uplink (UL) transmission extension command from a non-terrestrial network (NTN).

[0080] At step 614, method 610 involves responsive to receiving the UL transmission extension command, determining whether a value of a time alignment timer is first predetermined value or second predetermined value.

[0081] At step 616, method 610 involves selecting, based on whether the value of the time alignment timer is the first predetermined value or the second predetermined value, an initial value for an UL transmission extension duration timer.

[0082] In some implementations, the UL transmission extension command is a Medium Access Control (MAC) Control Element (CE).

[0083] In some implementations, the MAC CE includes a first bit including the UL transmission extension command.

[0084] In some implementations, the MAC CE is a GNSS measurement command MAC CE.

[0085] In some implementations, the GNSS measurement command MAC CE includes one or more bits repurposed as the UL transmission extension command.

[0086] In some implementations, the method further involving interfacing with the transceiver to receive an information element (IE) that includes the value of the time alignment timer.

[0087] In some implementations, determining whether a value of a time alignment timer is the first predetermined value or the second predetermined value involves determining that the value of the time alignment timer is the first predetermined value, and where setting, based on whether the value of the time alignment timer is the first predetermined value or the second predetermined value, an initial value for an UL transmission extension duration timer involves setting the initial value for the UL transmission extension duration timer as a configured parameter Y.

[0088] In some implementations, determining whether a value of a time alignment timer is the first predetermined value or the second predetermined value involves determining that the value of the time alignment timer is the second predetermined value, and where setting, based on whether the value of the time alignment timer is the first predetermined value or the second predetermined value, an initial value for an UL transmission extension duration timer involves setting the initial value for the UL transmission extension duration timer equal to the value of the time alignment timer.

[0089] In some implementations, where, after the UL transmission extension command is received, a transmission extension duration starts after a GNSS validity duration expires or the UL transmission extension duration timer expires.

[0090] In some implementations, the transmission extension duration starts at the point of the end of a subframe in which the UL transmission extension command is received.

[0091] In some implementations, the method further involves interfacing with the transceiver to report an UL transmission extension capability.

[0092] In some implementations, the capability includes an indication whether the UL transmission extension capability operates when the time alignment timer is the first predetermined value, the second predetermined value, or both.

[0093] In some implementations, the first predetermined value is infinity and the second predetermined value is not infinity.

[0094] FIG. 7 illustrates an example UE 700, according to some implementations. The UE 700 may be similar to and substantially interchangeable with UE 108 of FIG. 1.

[0095] The UE 700 may be any mobile or non-mobile computing device, such as, for example, mobile phones, computers, tablets, industrial wireless sensors (for example, microphones, pressure sensors, thermometers, motion sensors, accelerometers, inventory sensors, electric voltage / current meters, etc.), video devices (for example, cameras, video cameras, etc.), wearable devices (for example, a smart watch), or relaxed-IoT devices.

[0096] The UE 700 may include processors 702, RF interface circuitry 704, memory / storage 706, user interface 708, sensors 710, driver circuitry 712, power management integrated circuit (PMIC) 714, one or more antenna(s) 716, and battery 718. The components of the UE 700 may be implemented as integrated circuits (ICs), portions thereof, discrete electronic devices, or other modules, logic, hardware, software, firmware, or a combination thereof. The block diagram of FIG. 7 is intended to show a high-level view of some of the components of the UE 700. However, some of the components shown may be omitted, additional components may be present, and different arrangement of the components shown may occur in other implementations.

[0097] The components of the UE 700 may be coupled with various other components over one or more interconnects 720, which may represent any type of interface, input / output, bus (local, system, or expansion), transmission line, trace, optical connection, etc., that allows various circuit components (on common or different chips or chipsets) to interact with one another.

[0098] The processors 702 may include processor circuitry such as, for example, baseband processor circuitry (BB) 722A, central processor unit circuitry (CPU) 722B, and graphics processor unit circuitry (GPU) 722C. The processors 702 may include any type of circuitry or processor circuitry that executes or otherwise operates computer-executable instructions, suchas program code, software modules, or functional processes from memory / storage 706 to cause the UE 700 to perform operations as described herein.

[0099] In some implementations, the baseband processor circuitry 722A may access a communication protocol stack 724 in the memory / storage 706 to communicate over a 3GPP compatible network. In general, the baseband processor circuitry 722A may access the communication protocol stack to: perform user plane functions at a physical (PHY) layer, medium access control (MAC) layer, radio link control (RLC) layer, packet data convergence protocol (PDCP) layer, service data adaptation protocol (SDAP) layer, and PDU layer; and perform control plane functions at a PHY layer, MAC layer, RLC layer, PDCP layer, RRC layer, and a non-access stratum layer. In some implementations, the PHY layer operations may additionally / altematively be performed by the components of the RF interface circuitry 704. The baseband processor circuitry 722A may generate or process baseband signals or waveforms that carry information in 3 GPP-compatible networks. In some implementations, the waveforms for NR may be based cyclic prefix orthogonal frequency division multiplexing (OFDM) “CP-OFDM” in the uplink or downlink, and discrete Fourier transform spread OFDM “DFT-S-OFDM” in the uplink.

[0100] The memory / storage 706 may include one or more non-transitory, computer-readable media that includes instructions (for example, communication protocol stack 724) that may be executed by one or more of the processors 702 to cause the UE 700 to perform various operations described herein. The memory / storage 706 include any type of volatile or nonvolatile memory that may be distributed throughout the UE 700. In some implementations, some of the memory / storage 706 may be located on the processors 702 themselves (for example, LI and L2 cache), while other memory / storage 706 is external to the processors 702 but accessible thereto via a memory interface. The memory / storage 706 may include any suitable volatile or non-volatile memory such as, but not limited to, dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read only memory (EPROM), electrically erasable programmable read only memory (EEPROM), Flash memory, solid-state memory, or any other type of memory device technology.

[0101] The RF interface circuitry 704 may include transceiver circuitry and radio frequency front module (RFEM) that allows the UE 700 to communicate with other devices over a radio access network. The RF interface circuitry 704 may include various elements arranged intransmit or receive paths. These elements may include, for example, switches, mixers, amplifiers, filters, synthesizer circuitry, control circuitry, etc.

[0102] In the receive path, the RFEM may receive a radiated signal from an air interface via antenna(s) 716 and proceed to filter and amplify (with a low-noise amplifier) the signal. The signal may be provided to a receiver of the transceiver that downconverts the RF signal into a baseband signal that is provided to the baseband processor of the processors 702.

[0103] In the transmit path, the transmitter of the transceiver up-converts the baseband signal received from the baseband processor and provides the RF signal to the RFEM. The RFEM may amplify the RF signal through a power amplifier prior to the signal being radiated across the air interface via the antenna(s) 716. In various implementations, the RF interface circuitry 704 may be configured to transmit / receive signals in a manner compatible with NR access technologies.

[0104] The antenna(s) 716 may include one or more antenna elements to convert electrical signals into radio waves to travel through the air and to convert received radio waves into electrical signals. The antenna elements may be arranged into one or more antenna panels. The antenna(s) 716 may have antenna panels that are omnidirectional, directional, or a combination thereof to enable beamforming and multiple input, multiple output communications. The antenna(s) 716 may include microstrip antennas, printed antennas fabricated on the surface of one or more printed circuit boards, patch antennas, phased array antennas, etc. The antenna(s) 716 may have one or more panels designed for specific frequency bands including bands in FR1 or FR2.

[0105] The user interface 708 includes various input / output (VO) devices designed to enable user interaction with the UE 700. The user interface 708 includes input device circuitry and output device circuitry. Input device circuitry includes any physical or virtual means for accepting an input including, inter alia, one or more physical or virtual buttons (for example, a reset button), a physical keyboard, keypad, mouse, touchpad, touchscreen, microphones, scanner, headset, or the like. The output device circuitry includes any physical or virtual means for showing information or otherwise conveying information, such as sensor readings, actuator position(s), or other like information. Output device circuitry may include any number or combinations of audio or visual display, including, inter alia, one or more simple visual outputs / indicators (for example, binary status indicators such as light emitting diodes “LEDs” and multi -character visual outputs), or more complex outputs such as display devices ortouchscreens (for example, liquid crystal displays “LCDs,” LED displays, quantum dot displays, projectors, etc.), with the output of characters, graphics, multimedia objects, and the like being generated or produced from the operation of the UE 700.

[0106] The sensors 710 may include devices, modules, or subsystems whose purpose is to detect events or changes in its environment and send the information (sensor data) about the detected events to some other device, module, subsystem, etc. Examples of such sensors include, inter alia, inertia measurement units including accelerometers, gyroscopes, or magnetometers; microelectromechanical systems or nanoelectromechanical systems including 3-axis accelerometers, 3-axis gyroscopes, or magnetometers; level sensors; temperature sensors (for example, thermistors); pressure sensors; image capture devices (for example, cameras or lens less apertures); light detection and ranging sensors; proximity sensors (for example, infrared radiation detector and the like); depth sensors; ambient light sensors; ultrasonic transceivers; microphones or other like audio capture devices; etc.

[0107] The driver circuitry 712 may include software and hardware elements that operate to control particular devices that are embedded in the UE 700, attached to the UE 700, or otherwise communicatively coupled with the UE 700. The driver circuitry 712 may include individual drivers allowing other components to interact with or control various input / output (I / O) devices that may be present within, or connected to, the UE 700. For example, driver circuitry 712 may include a display driver to control and allow access to a display device, a touchscreen driver to control and allow access to a touchscreen interface, sensor drivers to obtain sensor readings of sensors 710 and control and allow access to sensors 710, drivers to obtain actuator positions of electro-mechanic components or control and allow access to the electro-mechanic components, a camera driver to control and allow access to an embedded image capture device, audio drivers to control and allow access to one or more audio devices.

[0108] The PMIC 714 may manage power provided to various components of the UE 700. In particular, with respect to the processors 702, the PMIC 714 may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion.

[0109] In some implementations, the PMIC 714 may control, or otherwise be part of, various power saving mechanisms of the UE 700. A battery 718 may power the UE 700, although in some examples the UE 700 may be mounted deployed in a fixed location, and may have a power supply coupled to an electrical grid. The battery 718 may be a lithium ion battery, a metal-air battery, such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, andthe like. In some implementations, such as in vehicle-based applications, the battery 718 may be a typical lead-acid automotive battery.

[0110] FIG. 8 illustrates an example access node 800 (e.g., a base station or gNB), according to some implementations. The access node 800 may be similar to and substantially interchangeable with base station 102. The access node 800 may include processors 802, RF interface circuitry 804, core network (CN) interface circuitry 806, memory / storage circuitry 808, and one or more antenna(s) 810.[OHl] The components of the access node 800 may be coupled with various other components over one or more interconnects 812. The processors 802, RF interface circuitry 804, memory / storage circuitry 808 (including communication protocol stack 814), antenna(s) 810, and interconnects 812 may be similar to like-named elements shown and described with respect to FIG. 7. For example, the processors 802 may include processor circuitry such as, for example, baseband processor circuitry (BB) 816A, central processor unit circuitry (CPU) 816B, and graphics processor unit circuitry (GPU) 816C.

[0112] The CN interface circuitry 806 may provide connectivity to a core network, for example, a 5th Generation Core network (5GC) using a 5GC -compatible network interface protocol such as carrier Ethernet protocols, or some other suitable protocol. Network connectivity may be provided to / from the access node 800 via a fiber optic or wireless backhaul. The CN interface circuitry 806 may include one or more dedicated processors or FPGAs to communicate using one or more of the aforementioned protocols. In some implementations, the CN interface circuitry 806 may include multiple controllers to provide connectivity to other networks using the same or different protocols.

[0113] As used herein, the terms “access node,” “access point,” or the like may describe equipment that provides the radio baseband functions for data and / or voice connectivity between a network and one or more users. These access nodes can be referred to as BS, gNBs, RAN nodes, eNBs, NodeBs, RSUs, TRxPs or TRPs, and so forth, and can include ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell). As used herein, the term “NG RAN node” or the like may refer to an access node 800 that operates in an NR or 5G system (for example, a gNB), and the term “E-UTRAN node” or the like may refer to an access node 800 that operates in an LTE or 4G system (e.g., an eNB). According to various implementations, the access node 800 may be implemented as one or more of a dedicated physical device such as a macrocell base station,and / or a low power (LP) base station for providing femtocells, picocells or other like cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells.

[0114] In some implementations, all or parts of the access node 800 may be implemented as one or more software entities running on server computers as part of a virtual network, which may be referred to as a CRAN and / or a virtual baseband unit pool (vBBUP). In V2X scenarios, the access node 800 may be or act as a “Road Side Unit.” The term “Road Side Unit” or “RSU” may refer to any transportation infrastructure entity used for V2X communications. An RSU may be implemented in or by a suitable RAN node or a stationary (or relatively stationary) UE, where an RSU implemented in or by a UE may be referred to as a “UE-type RSU,” an RSU implemented in or by an eNB may be referred to as an “eNB-type RSU,” an RSU implemented in or by a gNB may be referred to as a “gNB-type RSU,” and the like.

[0115] In the following sections, further exemplary embodiments are provided.

[0116] Example 1 includes a method that involves interfacing with a transceiver to receive an uplink (UL) transmission extension command from a non-terrestrial network (NTN); responsive to receiving the UL transmission extension command, determining whether a value of a time alignment timer is first predetermined value or second predetermined value; and selecting, based on whether the value of the time alignment timer is the first predetermined value or the second predetermined value, an initial value for an UL transmission extension duration timer.

[0117] Example 2 is the method of Example 1, where the UL transmission extension command is a Medium Access Control (MAC) Control Element (CE).

[0118] Example 3 is the method of Example 2, where the MAC CE includes a first bit including the UL transmission extension command.

[0119] Example 4 is the method of Example 2, where the MAC CE is a GNSS measurement command MAC CE.

[0120] Example 5 is the method of Example 2, where the GNSS measurement command MAC CE includes one or more bits repurposed as the UL transmission extension command.

[0121] Example 6 is the method of Example 1, the method further involving interfacing with the transceiver to receive an information element (IE) that includes the value of the time alignment timer.

[0122] Example 7 is the method of Example 1, where determining whether a value of a time alignment timer is the first predetermined value or the second predetermined value involves determining that the value of the time alignment timer is the first predetermined value, and where setting, based on whether the value of the time alignment timer is the first predetermined value or the second predetermined value, an initial value for an UL transmission extension duration timer involves setting the initial value for the UL transmission extension duration timer as a configured parameter Y.

[0123] Example 8 is the method of Example 1, where determining whether a value of a time alignment timer is the first predetermined value or the second predetermined value involves determining that the value of the time alignment timer is the second predetermined value, and where setting, based on whether the value of the time alignment timer is the first predetermined value or the second predetermined value, an initial value for an UL transmission extension duration timer involves setting the initial value for the UL transmission extension duration timer equal to the value of the time alignment timer.

[0124] Example 9 is the method of Example 1, where, after the UL transmission extension command is received, a transmission extension duration starts after a GNSS validity duration expires or the UL transmission extension duration timer expires.

[0125] Example 10 is the method of Example 1, the transmission extension duration starts at the point of the end of a subframe in which the UL transmission extension command is received.

[0126] Example 11 is the method of Example 1, the method further involving interfacing with the transceiver to report an UL transmission extension capability.

[0127] Example 12 is the method of Example 11, where the capability includes an indication whether the UL transmission extension capability operates when the time alignment timer is the first predetermined value, the second predetermined value, or both.

[0128] Example 12 is the method of Example 1, where the first predetermined value is infinity and the second predetermined value is not infinity.

[0129] Example 13 may include one or more non-transitory computer-readable media including instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of examples 1-12, or any other method or process described herein.

[0130] Example 14 may include an apparatus including logic, modules, and / or circuitry (e.g., processing circuitry) to perform one or more elements of a method described in or related to any of examples 1-13, or any other method or process described herein.

[0131] Example 15 may include an apparatus including: one or more processors and one or more computer-readable media including instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-13, or portions thereof.

[0132] Example 16 may include a computer program including instructions, wherein execution of the program by a processing element is to cause the processing element to carry out the method, techniques, or process as described in or related to any of examples 1-13, or portions thereof. The operations or actions performed by the instructions executed by the processing element can include the methods of any one of examples 1-13.

[0133] Example 17 may include a method of communicating in a wireless network as shown and described herein.

[0134] Example 18 may include a system for providing wireless communication as shown and described herein. The operations or actions performed by the system can include the methods of any one of examples 1-13.

[0135] Example 19 may include a device for providing wireless communication as shown and described herein. The operations or actions performed by the device can include the methods of any one of examples 1-13.

[0136] An apparatus, e.g., a user equipment, including one or more baseband processors, and so forth, can be configured to perform particular operations or actions by virtue of having software, firmware, hardware, and / or a combination of them that in operation causes the apparatus to perform the actions. The operations or actions performed by the apparatus can include the methods of any one of examples 1-13.

[0137] Various components may be described as performing a task or tasks, for convenience in the description. Such descriptions should be interpreted as including the phrase “configured to.” Reciting a component that is configured to perform one or more tasks is expressly intended not to invoke 35 U.S.C. § 112(f) interpretation for that component.

[0138] The foregoing description of one or more implementations provides illustration and description but is not intended to be exhaustive or to limit the scope of embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.

[0139] Although the embodiments above have been described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be interpreted to embrace all such variations and modifications.

[0140] It is well understood that the use of personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users. In particular, personally identifiable information data should be managed and handled so as to minimize risks of unintentional or unauthorized access or use, and the nature of authorized use should be clearly indicated to users.

Claims

CLAIMSWe Claim:

1. One or more processors configured to perform operations comprising: interfacing with a transceiver to receive an uplink (UL) transmission extension command from a non-terrestrial network (NTN); responsive to receiving the UL transmission extension command, determining whether a value of a time alignment timer is first predetermined value or second predetermined value; and selecting, based on whether the value of the time alignment timer is the first predetermined value or the second predetermined value, an initial value for an UL transmission extension duration timer.

2. The one or more processors of claim 1, wherein the UL transmission extension command is a Medium Access Control (MAC) Control Element (CE).

3. The one or more processors of claim 2, wherein the MAC CE comprises a first bit comprising the UL transmission extension command.

4. The one or more processors of claim 2, wherein the MAC CE is a GNSS measurement command MAC CE.

5. The one or more processors of claim 2, wherein the GNSS measurement command MAC CE comprises one or more bits repurposed as the UL transmission extension command.

6. The one or more processors of claim 1, the method further comprising: interfacing with the transceiver to receive an information element (IE) that comprises the value of the time alignment timer.

7. The one or more processors of claim 1, wherein determining whether a value of a time alignment timer is the first predetermined value or the second predetermined value comprises determining that the value of the time alignment timer is the first predetermined value, and wherein setting, based on whether the value of the time alignment timer is the firstpredetermined value or the second predetermined value, an initial value for an UL transmission extension duration timer comprises: setting the initial value for the UL transmission extension duration timer as a configured parameter Y.

8. The one or more processors of claim 1, wherein determining whether a value of a time alignment timer is the first predetermined value or the second predetermined value comprises determining that the value of the time alignment timer is the second predetermined value, and wherein setting, based on whether the value of the time alignment timer is the first predetermined value or the second predetermined value, an initial value for an UL transmission extension duration timer comprises: setting the initial value for the UL transmission extension duration timer equal to the value of the time alignment timer.

9. The one or more processors of claim 1, wherein, after the UL transmission extension command is received, a transmission extension duration starts after a GNSS validity duration expires or the UL transmission extension duration timer expires.

10. The one or more processors of claim 1, wherein the transmission extension duration starts at the point of the end of a subframe in which the UL transmission extension command is received.

11. The one or more processors of claim 1, further comprising: interfacing with the transceiver to report an UL transmission extension capability.

12. The one or more processors of claim 11, wherein the capability includes an indication whether the UL transmission extension capability operates when the time alignment timer is the first predetermined value, the second predetermined value, or both.

13. The one or more processors of claim 1, wherein the first predetermined value is infinity and the second predetermined value is not infinity.

14. A method of performing the operations of claims 1-13.

15. A user equipment (UE) comprising the one or more processors of claims 1-13.

16. A user equipment (UE) configured to perform the operations of claims 1-13.

17. A non-transitory computer storage medium encoded with instructions that, when executed by one or more processors, cause the one or more processors to perform the operations of claims 1-13.

Images