Uplink transmission timer extension

By introducing an uplink transmission timer extension mechanism in wireless communication and using closed-loop timing advance command messages to maintain UE uplink synchronization, the communication interruption problem caused by the expiration of GNSS validity period is solved, achieving efficient resource utilization and network flexibility.

CN122642091APending Publication Date: 2026-08-25QUALCOMM INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202480086019.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2024-01-31
Filing Date
2024-12-13
Publication Date
2026-08-25

AI Technical Summary

Technical Problem

In wireless communication, user equipment (UE) may lose uplink synchronization due to inaccurate positioning information, resulting in communication disconnection and resource waste. This is especially true when GNSS validity expires, as existing technologies struggle to effectively maintain uplink synchronization.

Method used

An uplink transmission timer extension mechanism is introduced. By using the indicator in the closed-loop timing advance command message, the UE is allowed to continue uplink transmission during the GNSS invalid period. The uplink transmission extension command and timing advance command are conveyed using the same format MAC CE message, avoiding the transition to RRC idle mode.

Benefits of technology

It effectively maintains uplink synchronization, reduces communication interruptions, and improves network flexibility and resource utilization efficiency, especially in emergency communication scenarios, avoiding unnecessary mode switching and delays caused by GNSS updates.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN122642091A_ABST
    Figure CN122642091A_ABST
Patent Text Reader

Abstract

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a UE can receive a closed loop timing advance command message, the closed loop timing advance command message including an indicator associated with the closed loop timing advance command message, the indicator including at least one of a timing advance value or an uplink transmission extension indication. The UE can transmit one or more communications on an uplink in accordance with an interpretation of the closed loop timing advance command message, the interpretation of the closed loop timing advance command message based on the indicator. Numerous other aspects are described.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] Cross-reference to related applications

[0002] This patent application claims priority to U.S. Patent Application No. 18 / 428,430, filed January 31, 2024, entitled “UPLINK TRANSMISSION TIMEREXTENSION,” which is assigned to the assignee of this application. The disclosure of the earlier application is considered part of this patent application and is incorporated herein by reference. Background Technology

[0003] All aspects of this disclosure relate to wireless communication in general, and more particularly to techniques, apparatus and methods for uplink transmission.

[0004] Wireless communication systems are widely deployed to provide a variety of services, including voice, text, messaging, video, data, and / or other services. Services may include unicast, multicast, and / or broadcast services, etc. Typical wireless communication systems employ multiple access radio access technologies (RATs) capable of supporting communication with multiple users by sharing available system resources (e.g., time-domain resources, frequency-domain resources, spatial-domain resources, and / or device transmit power, etc.). Examples of such multiple access RATs include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single-Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems.

[0005] The aforementioned Multiple Access RATs have been adopted in various telecommunications standards to provide a common protocol enabling different wireless communication devices to communicate at the city, national, regional, or global level. An example telecommunications standard is New Radio (NR). NR (also known as 5G) is part of the continuous evolution of mobile broadband announced by the 3rd Generation Partnership Project (3GPP). NR (and other mobile broadband evolutions beyond NR) can be designed to better support the Internet of Things (IoT) and reduced-capacity device deployments, industrial connectivity, millimeter-wave (mmWave) expansion, licensed and unlicensed spectrum access, non-terrestrial network (NTN) deployments, sidelinks and other device-to-device direct communication technologies (e.g., cellular vehicle-to-everything (CV2X) communications), massive MIMO, decomposed network architectures and network topology expansion, multi-subscriber implementations, high-precision positioning and / or radio frequency (RF) sensing, and more. As the demand for mobile broadband access continues to grow, further improvements to NR can be implemented, and other radio access technologies (such as 6G) can be introduced to further advance mobile broadband evolution. Summary of the Invention

[0006] Some aspects described herein relate to a method of wireless communication performed at a user equipment (UE). The method may include receiving a closed-loop timing advance command message, the closed-loop timing advance command message including an indicator associated with the closed-loop timing advance command message, the indicator including at least one of a timing advance value or an uplink transmission extension indication. The method may include transmitting one or more communications on an uplink based on an interpretation of the closed-loop timing advance command message, the interpretation of the closed-loop timing advance command message being based on the indicator.

[0007] Some aspects described herein relate to a method for wireless communication performed by a network node. The method may include sending a closed-loop timing advance command message, the closed-loop timing advance command message including an indicator associated with the closed-loop timing advance command message, the indicator including at least one of a timing advance value or an uplink transmission extension indicator. The method may include receiving one or more communications on an uplink based on an interpretation of the closed-loop timing advance command message, the interpretation of which is based on the indicator.

[0008] Some aspects described herein relate to a UE for wireless communication. The UE may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured to receive a closed-loop timing advance command message, the closed-loop timing advance command message including an indicator associated with the closed-loop timing advance command message, the indicator including at least one of a timing advance value or an uplink transmission extension indicator. The one or more processors may be configured to transmit one or more communications on an uplink based on an interpretation of the closed-loop timing advance command message, the interpretation of which is based on the indicator.

[0009] Some aspects described herein relate to a network node for wireless communication. The network node may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured to transmit a closed-loop timing advance command message, the closed-loop timing advance command message including an indicator associated with the closed-loop timing advance command message, the indicator including at least one of a timing advance value or an uplink transmission extension indicator. The one or more processors may be configured to receive one or more communications on an uplink based on an interpretation of the closed-loop timing advance command message, the interpretation of which is based on the indicator.

[0010] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a UE. When executed by one or more processors of the UE, the set of instructions enables the UE to receive a closed-loop timing advance command message, the closed-loop timing advance command message including an indicator associated with the closed-loop timing advance command message, the indicator including at least one of a timing advance value or an uplink transmission extension indicator. When executed by one or more processors of the UE, the set of instructions enables the UE to transmit one or more communications on the uplink based on an interpretation of the closed-loop timing advance command message, the interpretation of which is based on the indicator.

[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a network node. When executed by one or more processors of the network node, the set of instructions causes the network node to send a closed-loop timing advance command message, the closed-loop timing advance command message including an indicator associated with the closed-loop timing advance command message, the indicator including at least one of a timing advance value or an uplink transmission extension indicator. When executed by one or more processors of the network node, the set of instructions causes the network node to receive one or more communications on an uplink based on an interpretation of the closed-loop timing advance command message, the interpretation of which is based on the indicator.

[0012] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for receiving a closed-loop timing advance command message, the closed-loop timing advance command message including an indicator associated with the closed-loop timing advance command message, the indicator including at least one of a timing advance value or an uplink transmission extension indication. The apparatus may include components for transmitting one or more communications on an uplink based on an interpretation of the closed-loop timing advance command message, the interpretation of which is based on the indicator.

[0013] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for transmitting a closed-loop timing advance command message, the closed-loop timing advance command message including an indicator associated with the closed-loop timing advance command message, the indicator including at least one of a timing advance value or an uplink transmission extension indication. The apparatus may include components for receiving one or more communications on an uplink based on an interpretation of the closed-loop timing advance command message, the interpretation of which is based on the indicator.

[0014] Various aspects of this disclosure may be implemented or be implemented as described in whole by or embodied in the methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network nodes, network entities, wireless communication devices and / or processing systems as fully described in the specification and drawings and illustrated in the specification and drawings.

[0015] The preceding paragraphs of this section have broadly summarized some aspects of this disclosure. These and additional aspects and associated improvements will be described below. The disclosed aspects may serve as the basis for modifying or designing other aspects for performing the same or similar purposes of this disclosure. Such equivalent aspects do not depart from the scope of the appended claims. The characteristics of the aspects disclosed herein, their organization and operation, and associated improvements will be better understood from the following description taken in conjunction with the accompanying drawings. Attached Figure Description

[0016] The accompanying drawings illustrate some aspects of this disclosure but do not limit its scope, as other aspects can be achieved by this description. Each drawing in the drawings is provided for illustrative and descriptive purposes and not as a definition of limitation of the claims. Identical or similar reference numerals in different drawings may identify identical or similar elements.

[0017] Figure 1 This is a diagram illustrating an example of a wireless communication network according to the present disclosure.

[0018] Figure 2 This is a diagram illustrating communication between an example network node and an example UE in a wireless network according to this disclosure.

[0019] Figure 3 This is a diagram illustrating an example decomposed base station architecture according to this disclosure.

[0020] Figure 4 This is a diagram illustrating examples of downlink and uplink transmissions between a network node and a UE in a wireless network according to this disclosure.

[0021] Figure 5 This is a diagram illustrating an example of an uplink transmit timer extension according to this disclosure.

[0022] Figure 6 This is a diagram illustrating an example of an uplink transmit timer extension according to this disclosure.

[0023] Figure 7 This is a diagram illustrating an example process performed, for example, at the UE or at a device of the UE, according to this disclosure.

[0024] Figure 8This is a diagram illustrating an example process performed, for example, at a network node or a device of a network node, according to the present disclosure.

[0025] Figure 9 This is a diagram of an example device for wireless communication according to the present disclosure.

[0026] Figure 10 This is a diagram illustrating an example of a hardware implementation of a device employing a processing system according to the present disclosure.

[0027] Figure 11 The diagram illustrates an example of a specific implementation of the code and circuitry for a device according to this disclosure.

[0028] Figure 12 This is a diagram of an example device for wireless communication according to the present disclosure.

[0029] Figure 13 This is a diagram illustrating an example of a hardware implementation of a device employing a processing system according to the present disclosure.

[0030] Figure 14 The diagram illustrates an example of a specific implementation of the code and circuitry for a device according to this disclosure. Detailed Implementation

[0031] When operating within a network, a User Equipment (UE) can use location information (such as information identifying the UE's location, the speed and direction of travel of the UE, or other characteristics of the UE) for one or more purposes. For example, the UE can use information identifying its location to determine which cells or Radio Access Technologies (RATs) are available at the UE's location. In this example, the UE can connect to a cell or RAT available at the UE's location. In another example, the UE can use information identifying the UE's speed and direction of travel to determine that the UE is moving from a first coverage area of ​​a first cell to a second coverage area of ​​a second cell. In this example, the UE can actively perform mobility operations to switch from receiving network services via the first cell to receiving network services via the second cell. In yet another example, the UE can use location information to determine timing information.

[0032] The UE can determine the propagation delay associated with communication between a first location of the UE and a second location of the network node. The propagation delay may include a time period (which may be on the order of milliseconds (ms)) during which a transmission propagates from the first location of the UE to the second location of the network node. In some examples, the propagation delay may include a time period associated with sending the transmission (e.g., the time period between generating the waveform and transmitting the waveform by an antenna at the UE) or a time period associated with receiving the transmission (e.g., the time period between receiving the waveform at an antenna at the network node and processing the transmission to derive the information conveyed by the waveform).

[0033] The UE can adjust the monitoring period or transmission period based on propagation delay to ensure synchronization between the first timing at the UE and the second timing at the network node. The monitoring period can include the time during which the UE monitors transmissions (e.g., transmissions from a network node or another UE). Similarly, the transmission period can include the time during which the UE transmits communication (e.g., to a network node or another UE). For example, the UE can shift the monitoring period based on propagation delay so that the UE monitors communication during the time when communication will arrive (when propagation delay is taken into account) rather than during the time communication is transmitted. Similarly, the UE can shift the transmission period based on propagation delay so that when communication arrives at the target (e.g., a network node or another UE), the target is monitoring the communication.

[0034] UEs can use different techniques to determine positioning information. For example, some UEs can use one or more accelerometers to determine velocity and direction information. In this example, by measuring the amount of acceleration in one or more directions, the UE can estimate the velocity and / or direction of travel. Some UEs can use triangulation or trilateration techniques to determine positioning information. For example, the UE can measure a set of signals from a set of sources (e.g., a set of base stations) and triangulate the UE's position relative to the set of sources based on characteristics of the signal set (e.g., signal strength, signal delay, or Doppler shift). Some UEs can use non-terrestrial navigation sources to determine positioning information. For example, the UE can receive a set of signals from a Global Navigation Satellite System (GNSS) provider and use these signals to perform, for example, triangulation or trilateration determination. Examples of GNSS providers that provide positioning, navigation, and timing (PNT) services include the Global Positioning System (GPS), the BeiDou Navigation Satellite System (BDS), and the Galileo Navigation System. Different GNSS providers may be available at different locations, for different UEs, and / or at different granularity levels.

[0035] When a UE uses inaccurate location information, it may determine inaccurate propagation delays. This could result in the UE sending a communication that arrives at its target when the target is not monitoring it. Similarly, it could cause the UE to monitor a communication before it arrives. Therefore, using inaccurate location information can lead to communication drops, retransmissions, bit loss (e.g., requiring processor-intensive error recovery schemes to recover the bits), or other problems. Therefore, the UE can periodically update its location information to avoid overutilization of processing or power resources.

[0036] To update positioning information, the UE can trigger GNSS measurements. GNSS measurements may include determining the transmission time of a GNSS signal set, the reception angle of that GNSS signal set, carrier phase measurements of that GNSS signal set, or another type of measurement. In some scenarios, the UE may not be able to trigger GNSS measurements during a certain time period, which may be referred to as the "GNSS validity period." The GNSS validity period includes the time period during which GNSS measurements are considered valid. In other words, the GNSS validity period is the time period during which the UE can use GNSS measurements without errors in the positioning information. Therefore, GNSS invalidity is a UE state where no recent GNSS measurement has occurred within the configured time period.

[0037] An example where a UE might fail to trigger GNSS measurements during a GNSS validity period is when the UE is sending high-priority communications on the uplink. In this example, the UE might be unable to interrupt high-priority communications on the uplink to perform GNSS measurements on the downlink. In Internet of Things (IoT) non-terrestrial network (NTN) deployments, GNSS validity expires when the validity timer associated with updating location information expires before the UE has performed GNSS measurements and reset the validity timer. When the UE's GNSS validity expires, the UE's location is considered outdated, and timing based on the UE's location is considered invalid. When timing is considered invalid, the UE may lack uplink synchronization with network nodes (e.g., NTN network nodes) that are providing network services to the UE. When the UE lacks uplink synchronization, the UE can transition from Radio Resource Control (RRC) connected mode to RRC idle mode. In RRC idle mode, the UE can update its location information to restore its location information and GNSS validity to a valid state.

[0038] However, in some scenarios, it is desirable for the UE to continue transmitting on the uplink even after the GNSS validity has expired. For example, in emergency communication scenarios, the trade-off between some communication interruptions due to a lack of uplink synchronization and the complete communication interruption associated with entering RRC idle mode and updating GNSS validity may tend to result in some communication interruptions. In such scenarios, the UE may have the capability to remain in RRC connected mode after the GNSS validity has expired.

[0039] When GNSS validity becomes obsolete and the UE is configured to remain in RRC connection mode, the UE can start a timer. T3xx To continue uplink transmission. When the GNSS validity timer expires (and the GNSS validity becomes obsolete), the UE starts a timer. T3xx And use a timer T3xx This is used to track a specific time period during which the UE continues to transmit on the uplink (and forgoes transitioning to RRC idle mode) even though GNSS is disabled. In other words, as long as the timer... T3xx By maintaining operation, the UE retains its uplink synchronization state and can perform uplink transmissions, even after the GNSS validity period expires. (Timer) T3xx After the timeout period expires, the UE can switch to RRC idle mode to restore GNSS validity. The network node can send a Media Access Control (MAC) Control Element (CE) message via RRC signaling to request the UE to reset the timer. T3xx For example, in a timer T3xx Before the expiration date, and when the UE has the configured amount of data for uplink transmission or the configured data priority for uplink transmission, the network node may request the UE to reset the timer. T3xx Regarding timers T3xx Additional details, including its extensions, are described in 3GPP Technical Specification (TS) 36.331, Version 18, 18.0.0. This is achieved by resetting the timer. T3xx Despite the lack of GNSS availability, the UE can extend the uplink transmission time. Different MAC CE message formats are specified for the UE to receive timing-related commands. The UE may lack information to distinguish between the different formats and associated purposes of different MAC CEs. When the UE cannot distinguish between different formats and associated purposes, it may not be able to correctly interpret the received MAC CEs or receive commands that the network node is attempting to send to the UE. Due to the lack of command reception, the UE may be unable to extend the timer. T3xx Consequently, it became impossible to continue sending.

[0040] Overall, various aspects involve uplink transmit timer extensions. Some aspects involve more specifically a single MAC CE format, which can be used to convey uplink transmit extension commands and reset timers. T3xx This includes commands for conveying Timing Advance (TA) commands (such as closed-loop TA commands). A closed-loop TA command may refer to a TA value signaled by the network node to the UE. In contrast, an open-loop TA command is a TA value determined autonomously by the UE without receiving explicit signaling from the network node identifying the TA value. In some aspects, the network node can configure reserved bit indicators in the MAC CE to indicate whether the MAC CE is signaling a TA command (such as a closed-loop TA command for closed-loop timing control) or an uplink transmission extension command. For example, the network node can set a Language Code Identifier (LCID) code point to indicate whether the MAC CE is conveying a TA command, an uplink transmission extension, or a TA command with an uplink transmission extension. Additionally or alternatively, the network node can set a Timing Advance Group (TAG) identifier in the TA command to indicate whether the MAC CE is conveying a TA command, an uplink transmission extension, or a TA command with an uplink transmission extension.

[0041] When a UE receives a MAC CE, it can use indicators within the MAC CE to determine how to interpret one or more fields of the MAC CE or the purpose of the MAC CE. For example, the UE can interpret indicators in the MAC CE as indicating that the MAC CE is associated with conveying uplink transmission extensions, TA commands, or both uplink transmission extensions and TA commands. In this example, the UE can interpret the LCID code point or another reserved bit indicator as an indicator. Therefore, the UE can interpret the TA command or TAG ID of the MAC CE based on the value in the LCID code point or another reserved bit indicator. For example, the UE can interpret a TA command as conveying a TA value.

[0042] Specific aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential improvements. In some examples, by including an indicator in the MAC CE to indicate the MAC CE purpose, the described techniques can be used to provide TA commands, uplink transmission extensions, or TA commands with uplink transmission extensions within a MAC CE of the same format. The uplink transmission extension may be a reset... T3xxThe timer indication enables the UE to continue uplink transmissions during GNSS invalidity periods. The TA command can be associated with the timing configured for UE transmissions during the extended uplink transmission period. By providing multiple possible messages using a MAC CE of the same format, the described technique improves signaling flexibility without additional signaling overhead. By providing uplink transmission extension within the TA command MAC CE, the described technique improves network flexibility compared to extending uplink transmissions performed by the UE after the GNSS validity period expires.

[0043] Various aspects of this disclosure are described below with reference to the accompanying drawings. However, aspects of this disclosure may be embodied in many different forms and should not be construed as limited to any specific aspect illustrated or described with reference to the drawings or otherwise presented in this disclosure. Rather, these aspects are provided so that this disclosure will be comprehensive and complete, and will fully convey the scope of protection of this disclosure to those skilled in the art. Those skilled in the art will understand that the scope of this disclosure is intended to cover any aspect of this disclosure disclosed herein, whether implemented independently of or in combination with any other aspect of this disclosure. For example, various combinations or numbers of aspects set forth herein may be used to implement an apparatus or a method of practice. Furthermore, the scope of this disclosure is intended to cover apparatuses having structures and / or functionalities other than those available for practicing the various aspects of this disclosure set forth herein, or methods of practice using these other structures and / or functionalities. Any aspect of this disclosure disclosed herein may be embodied by one or more elements of the claims.

[0044] Various methods, operations, apparatuses, and techniques will now be presented with reference to them. These methods, operations, apparatuses, and techniques will be described in detail below and illustrated in the accompanying drawings by various boxes, modules, components, circuits, steps, processes, or algorithms (collectively, “elements”). These elements may be implemented using hardware, software, or a combination of hardware and software. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole.

[0045] Multiple access radio access technology (RAT) has been adopted in various telecommunications standards to provide a common protocol that enables wireless communication devices to communicate at the city, enterprise, national, regional, or global level. For example, 5G New Radio (NR) is part of the continuous mobile broadband evolution announced by the 3rd Generation Partnership Project (3GPP). 5G NR supports a variety of technologies and use cases, including enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), massive machine-type communication (mMTC), millimeter wave (mmWave) technology, beamforming, network slicing, edge computing, Internet of Things (IoT) connectivity and management, and network function virtualization (NFV).

[0046] With increasing demand for broadband access and the evolution of technologies supported by wireless communication networks, further technological improvements can be adopted in or implemented for 5G NR or future RATs (such as 6G) to further advance the evolution of wireless communication for a variety of existing and new use cases and applications. These technological improvements can be associated with new frequency band extensions, licensed and unlicensed spectrum access, overlapping spectrum use, small cell deployments, non-terrestrial network (NTN) deployments, decomposed network architectures and network topology extensions, device aggregation, advanced duplex communication, sidelinks and other device-to-device direct communication, IoT (including passive or ambient IoT) networks, reduced-capacity (RedCap) UE functionality, industrial connectivity, multi-subscriber implementations, high-precision positioning, radio frequency (RF) sensing and / or artificial intelligence or machine learning (AI / ML), and more. Such technological improvements can support use cases such as wireless backhaul, wireless data centers, extended reality (XR) and metaverse applications, meta-services for supporting vehicle connectivity, holographic and mixed reality communications, autonomous and collaborative robots, vehicle platooning and collaborative manipulation, sensor networks, posture monitoring, brain-computer interfaces, digital twin applications, asset management, and general coverage applications using off-ground and / or aerial platforms, etc. The methods, operations, apparatuses, and techniques described herein can implement one or more of the foregoing technologies and / or support one or more of the foregoing use cases.

[0047] Figure 1This is a diagram illustrating an example of a wireless communication network 100 according to the present disclosure. The wireless communication network 100 may be a 5G (or NR) network or a 6G network, or may include elements of a 5G (or NR) network or elements of a 6G network, etc. The wireless communication network 100 may include a plurality of network nodes 110, shown as network node (NN) 110a, network node 110b, network node 110c, and network node 110d. Network nodes 110 may support communication with a plurality of UEs 120 (shown as UE120a, UE 120b, UE 120c, UE 120d, and UE 120e).

[0048] Network nodes 110 and UEs 120 of wireless communication network 100 can communicate using the electromagnetic spectrum, which can be subdivided into various categories, frequency bands, carriers, and / or channels according to frequency or wavelength. For example, devices of wireless communication network 100 can communicate using one or more operating frequency bands. In some aspects, multiple wireless communication networks 100 can be deployed in a given geographical area. Each wireless communication network 100 can support a specific RAT (which may also be referred to as an air interface) and can operate on one or more carrier frequencies in one or more frequency ranges. Examples of RATs include 4G RATs, 5G / NRRATs, and / or 6G RATs, etc. In some examples, when multiple RATs are deployed in a given geographical area, each RAT in that geographical area can operate on a different frequency to avoid interference with each other.

[0049] Various operating frequency bands have been defined as frequency ranges designated FR1 (410 MHz to 7.125 GHz), FR2 (24.25 GHz to 52.6 GHz), FR3 (7.125 GHz to 24.25 GHz), FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Although a portion of FR1 is greater than 6 GHz, in some documents and articles, FR1 is often (interchangeably) referred to as the “sub-6 GHz” band. Similarly, in some documents and articles, FR2 is often (interchangeably) referred to as the “millimeter wave” band, but this is different from the extremely high frequency (EHF) band (30 GHz to 300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU). The frequencies between FR1 and FR2 are often referred to as the intermediate frequency band, including FR3. Frequency bands falling within FR3 can inherit FR1 or FR2 characteristics, thereby effectively extending the characteristics of FR1 or FR2 into mid-band frequencies. Therefore, "below 6 GHz" (if used herein) can broadly refer to frequencies less than 6 GHz, within FR1, and / or included in mid-band frequencies. Similarly, the term "millimeter wave" (if used herein) can broadly refer to frequencies included in mid-band frequencies, within FR2, FR4, FR4-a, FR4-1, or FR5, and / or within the EHF band. Higher frequency bands can extend 5G NR operation, 6G operation, and / or other RATs above 52.6 GHz. For example, each of FR4a, FR4-1, FR4, and FR5 falls within the EHF band. In some examples, wireless communication network 100 can implement dynamic spectrum sharing (DSS), where multiple RATs (e.g., 4G / LTE and 5G / NR) are implemented within a single frequency band using dynamic bandwidth allocation (e.g., based on user demand). It is conceivable that the frequencies included in these operating frequency bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1 and / or FR5) can be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0050] Network node 110 may include one or more devices, components, or systems that enable communication between UE 120 and one or more devices, components, or systems of wireless communication network 100. Network node 110 may be, may include, or may also be referred to as an NR network node, 5G network node, 6G network node, node B, eNB, gNB, access point (AP), transmit / receive point (TRP), mobility element, core, network entity, network element, network equipment, and / or another type of device, component, or system included in a radio access network (RAN).

[0051] Network node 110 may be implemented as a single physical node (e.g., a single physical structure) or as two or more physical nodes (e.g., two or more different physical structures). For example, network node 110 may be a device or system implementing a portion of a radio protocol stack, a device or system implementing a complete radio protocol stack (such as a complete gNB protocol stack), or a collection of devices or systems collectively implementing a complete radio protocol stack. For example, and as shown, network node 110 may be an aggregated network node (with an aggregated architecture), meaning that network node 110 can implement a complete radio protocol stack physically and logically integrated within a single node (e.g., a single physical structure) in the wireless communication network 100. For example, aggregated network node 110 may consist of a single standalone base station or a single TRP that uses the complete radio protocol stack to implement or facilitate communication between UE 120 and the core network of wireless communication network 100.

[0052] Alternatively, and also as shown in the figure, network node 110 can be a decomposed network node (sometimes referred to as a decomposed base station), meaning that network node 110 can realize a radio protocol stack that is physically distributed and / or logically distributed among two or more nodes in the same or different geographic locations. For example, a decomposed network node may have a decomposed architecture. In some deployments, decomposed network node 110 may be used in integrated access and backhaul (IAB) networks, in open radio access networks (O-RAN) (such as network configurations compliant with the O-RAN Alliance), or in virtualized radio access networks (vRAN) (also referred to as cloud radio access networks (C-RAN)) to facilitate scaling by decomposing base station functionality into multiple units that can be deployed independently.

[0053] Network nodes 110 of the wireless communication network 100 may include one or more central units (CUs), one or more distributed units (DUs), and / or one or more radio units (RUs). CUs may host one or more higher-layer control functions, such as Radio Resource Control (RRC) functions, Packet Data Convergence Protocol (PDCP) functions, and / or Service Data Adaptation Protocol (SDAP) functions, etc. DUs may host one or more of the Radio Link Control (RLC) layer, Media Access Control (MAC) layer, and / or one or more higher physical (PHY) layers, at least in part, according to functional splits (such as functional splits defined by 3GPP). In some examples, DUs may also host one or more lower PHY layer functions, such as Fast Fourier Transform (FFT), Inverse FFT (iFFT), beamforming, Physical Random Access Channel (PRACH) extraction and filtering, and / or scheduling of resources for one or more UEs 120, etc. RUs may host RF processing functions or lower PHY layer functions, such as FFT, iFFT, beamforming, or PRACH extraction and filtering, etc., according to functional splits (such as lower-layer functional splits). In this type of architecture, each RU can be operated to handle over-the-air (OTA) communications with one or more UE 120s.

[0054] In some aspects, a single network node 110 may include a combination of one or more CUs, one or more DUs, and / or one or more RUs. Additionally or alternatively, network node 110 may include one or more near real-time (near RT) RAN Intelligent Controllers (RICs) and / or one or more non-real-time (non-RT) RICs. In some examples, CUs, DUs, and / or RUs may be implemented as virtual units, such as Virtual Central Units (VCUs), Virtual Distributed Units (VDUs), or Virtual Radio Units (VRUs), etc. Virtual units may be implemented as virtual network functions, such as those associated with cloud deployments.

[0055] Some network nodes 110 (e.g., base stations, RUs, or TRPs) can provide communication coverage for specific geographic areas. In 3GPP, the term "cell" can refer to the coverage area of ​​network node 110 or to network node 110 itself, depending on the context in which the term is used. Network node 110 can support one or more (e.g., three) cells. In some examples, network node 110 can provide communication coverage for macro cells, pico cells, femto cells, or another type of cell. A macro cell can cover a relatively large geographic area (e.g., a radius of several kilometers) and can allow unrestricted access by UE 120 with a service subscription. A pico cell can cover a relatively small geographic area and can allow unrestricted access by UE 120 with a service subscription. A femto cell can cover a relatively small geographic area (e.g., a residential area) and can allow restricted access by UE 120 associated with that femto cell (e.g., UE 120 in a Closed Subscriber Group (CSG)). A network node 110 used for a macro cell may be referred to as a macro network node. Network node 110 used for a picocell may be referred to as a pico network node. Network node 110 used for a femtocell may be referred to as a femto network node or a home network node. In some examples, the cell may not necessarily be stationary. For example, the geographical area of ​​the cell may move depending on the location of the associated mobile network node 110 (e.g., a train, satellite base station, drone, or NTN network node).

[0056] The wireless communication network 100 can be a heterogeneous network, comprising different types of network nodes 110, such as macro network nodes, piconet nodes, femtonet nodes, relay network nodes, aggregation network nodes, and / or decomposition network nodes, etc. Figure 1 In the example shown, network node 110a can be a macro network node for macro cell 130a, network node 110b can be a pico network node for pico cell 130b, and network node 110c can be a femto network node for femto cell 130c. Compared to other types of network nodes 110, the various types of network nodes 110 typically transmit at different power levels, serve different coverage areas, and / or have different effects on interference in the wireless communication network 100. For example, macro network nodes may have high transmit power levels (e.g., 5 watts to 40 watts), while pico network nodes, femto network nodes, and relay network nodes may have lower transmit power levels (e.g., 0.1 watts to 2 watts).

[0057] In some examples, network node 110 may be, may include, or operate as a RU, TRP, or base station communicating with one or more UEs 120 via a radio access link (which may be referred to as a "Uu" link). The radio access link may include a downlink and an uplink. A "downlink" (or "DL") refers to the communication direction from network node 110 to UE 120, and an "uplink" (or "UL") refers to the communication direction from UE 120 to network node 110. Downlink channels may include one or more control channels and one or more data channels. Downlink control channels may be used to transmit downlink control information (DCI) (e.g., scheduling information, reference signals, and / or configuration information) from network node 110 to UE 120. Downlink data channels may be used to transmit downlink data (e.g., user data associated with UE 120) from network node 110 to UE 120. Downlink control channels may include one or more physical downlink control channels (PDCCH), and downlink data channels may include one or more physical downlink shared channels (PDSCH). The uplink channel may similarly include one or more control channels and one or more data channels. The uplink control channel can be used to transmit uplink control information (UCI) from UE 120 to network node 110 (e.g., transmitting corresponding reference signals and / or feedback with one or more downlinks). The uplink data channel can be used to transmit uplink data (e.g., user data associated with UE 120) from UE 120 to network node 110. The uplink control channel may include one or more physical uplink control channels (PUCCH), and the uplink data channel may include one or more physical uplink shared channels (PUSCH). The downlink and uplink may each include a set of resources on which network node 110 and UE 120 can communicate.

[0058] Downlink and uplink resources may include time-domain resources (frames, subframes, time slots, and / or symbols), frequency-domain resources (bands, component carriers, subcarriers, resource blocks, and / or resource elements), and / or spatial-domain resources (specific transmission directions and / or beam parameters). Frequency-domain resources in some bands may be subdivided into bandwidth portions (BWPs). A BWP may be a contiguous block of frequency-domain resources allocated to one or more UEs 120 (e.g., a contiguous block of resource blocks). UEs 120 may be configured using both uplink and downlink BWPs (where the uplink and downlink BWPs may be the same BWP or different BWPs). BWPs may be dynamically configured and / or reconfigured (e.g., by sending DCI configuration to one or more UEs 120 via network node 110), meaning that BWPs may be adjusted in real-time (or near real-time) based on changing network conditions in the wireless communication network 100 and / or based on the specific requirements of one or more UEs 120. This allows for more efficient use of available frequency domain resources in the wireless communication network 100, as fewer frequency domain resources can be allocated to the BWP for UE 120 (which reduces the number of frequency domain resources that UE 120 needs to monitor), thus allowing more frequency domain resources to be distributed across multiple UE 120s. Therefore, the BWP can also assist in the implementation of such UE 120s by facilitating the configuration of smaller bandwidths for communications performed by lower-capacity UE 120s.

[0059] As described above, in some aspects, the wireless communication network 100 may be an IAB network, may include an IAB network, or may be included in an IAB network. In an IAB network, at least one network node 110 is an anchor network node communicating with a core network. The anchor network node 110 may also be referred to as an IAB donor (or "IAB donor"). The anchor network node 110 may be connected to the core network via a wired backhaul link. For example, the Ng interface of the anchor network node 110 may terminate at the core network. Additionally or alternatively, the anchor network node 110 may be connected to one or more devices in the core network that provide core access and mobility management functions (AMF). An IAB network typically also includes multiple non-anchor network nodes 110, which may also be referred to as relay network nodes or simply IAB nodes (or "IAB-nodes"). Each non-anchor network node 110 can directly communicate with the anchor network node 110 via a wireless backhaul link to access the core network, or can indirectly communicate with the anchor network node 110 via one or more other non-anchor network nodes 110 and an associated wireless backhaul link forming a backhaul path to the core network. Some anchor network nodes 110 or other non-anchor network nodes 110 can also directly communicate with one or more UEs 120 via a wireless access link carrying access services. In some examples, network resources used for wireless communication (such as time resources, frequency resources, and / or spatial resources) can be shared between the access link and the backhaul link.

[0060] In some examples, any network node 110 relaying communication may be referred to as a relay network node, a relay station, or simply a repeater. A repeater may receive communications from an upstream station (e.g., another network node 110 or UE 120) and transmit communications to a downstream station (e.g., UE 120 or another network node 110). In one or more examples, the wireless communication network 100 may include or be referred to as a "multi-hop network." Figure 1 In the example shown, network node 110d (e.g., a relay network node) can communicate with network node 110a (e.g., a macro network node) and UE 120d to facilitate communication between network node 110a and UE 120d. Additionally or alternatively, UE 120 can be a relay station capable of relaying transmissions to or from other UE 120s, or can operate as such a relay station. UE 120 relaying communication can be referred to as a UE repeater or relay UE, etc.

[0061] UE 120 may be physically distributed throughout the wireless communication network 100, and each UE 120 may be stationary or mobile. UE 120 may be, may include, an access terminal, another terminal, a mobile station, or a subscriber unit, or may be included in an access terminal, another terminal, a mobile station, or a subscriber unit. UE 120 may be, or may include, a cellular phone (e.g., a smartphone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smartwatch, smart clothing, smart glasses, a smart wristband and / or smart jewelry (such as a smart ring or smart bracelet)), an entertainment device (e.g., a music device, a video device and / or a satellite radio), an XR device, a vehicle component or sensor, a smart meter or sensor, industrial manufacturing equipment, a Global Navigation Satellite System (GNSS) device (such as a Global Positioning System device or another type of positioning device), a UE function of a network node, and / or any other suitable device or function that can communicate via a wireless medium, or may be coupled to them.

[0062] UE 120 and / or network node 110 may include one or more chips, system-on-a-chip (SoC), chipsets, packages, or devices that individually or collectively constitute or include a processing system. The processing system includes processor (or “processing”) circuitry in the form of one or more processors, microprocessors, processing units (such as central processing units (CPUs), graphics processing units (GPUs), neural processing units (NPUs), and / or digital signal processors (DSPs)), processing blocks, application-specific integrated circuits (ASICs), programmable logic devices (PLDs) (such as field-programmable gate arrays (FPGAs)), or other discrete gate or transistor logic components or circuits (all of which are generally referred to herein individually as “processors” or collectively as “processors” or “processor circuitry”). Processors may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, a combination of one or more microprocessors with a DSP core, or any other such configuration. One or more of these processors may be individually or collectively configured to perform the various functions or operations described herein. A processor group that can be configured or configured to perform a set of functions may include a first processor that can be configured or configured to perform a first function in the set, and a second processor that can be configured or configured to perform a second function in the set, or may include the entire processor group that is configured or configured to perform the set of functions.

[0063] The processing system may also include memory circuitry in the form of one or more memory devices, memory blocks, memory elements, or other discrete gate or transistor logic components or circuits, each of which may include tangible storage media such as random access memory (RAM) or read-only memory (ROM) or combinations thereof (all of which are generally referred to herein individually as "memory" or collectively as "memory" or "memory circuitry"). One or more of these memories may be coupled to one or more processors in the processor (e.g., operatively coupled, communicatively coupled, electronically coupled, or electrically coupled) and may store processor-executable code (such as software) individually or collectively, which, when executed by one or more processors in the processor, may configure one or more processors in the processor to perform the various functions or operations described herein. Additionally or alternatively, in some examples, one or more processors in the processor may be pre-configured to perform the various functions or operations described herein without being configured by software. The processing system may also include or be coupled to one or more modems (such as Wi-Fi (e.g., IEEE compliant) modems or cellular (e.g., 3GPP 4G LTE, 5G, or 6G compliant) modems). In some embodiments, one or more processors of the processing system include or implement one or more modems among the modems. The processing system may also include, or be coupled to, multiple radio components (collectively, “radio components”), multiple RF chains, or multiple transceivers, each of which may in turn be coupled to one or more antennas among multiple antennas. In some embodiments, one or more processors of the processing system include or implement one or more of the radio components, RF chains, or transceivers. UE 120 may be included or may be contained in a housing that houses components associated with UE 120, including the processing system.

[0064] Some UEs 120 may be considered Machine Type Communication (MTC) UEs, Evolved or Enhanced Machine Type Communication (eMTC) UEs, Further Enhanced eMTC (feMTC) UEs, or Enhanced feMTC (efeMTC) UEs, or further evolutions thereof, all of which may be referred to simply as "MTC UEs". MTC UEs may be, may include, or may be included in or coupled with the following: robots, unmanned aerial vehicles, remote devices, sensors, instruments, monitors, and / or location tags. Some UEs 120 may be considered IoT devices and / or may be implemented as NB-IoT (Narrowband IoT) devices. IoT UEs or NB-IoT devices may be, may include, or may be included in or coupled with the following: industrial machines, appliances, refrigerators, doorbell camera devices, home automation devices, and / or lighting fixtures, etc. Some UEs 120 may be considered customer premises equipment, which may include telecommunications equipment installed at a customer location (such as a home or office) to enable access to a service provider’s network (such as being included in or communicating with the wireless communication network 100).

[0065] Some UEs 120 can be categorized according to different categories associated with varying levels of complexity and / or capabilities. UEs 120 in the first category facilitate large-scale IoT within the wireless communication network 100 and offer lower complexity and / or lower cost compared to UEs 120 in the second category. UEs 120 in the second category may include mission-critical IoT devices capable of URLLC, enhanced mobile broadband (eMBB), and / or precise positioning within the wireless communication network 100, legacy UEs, baseline UEs, high-level UEs, advanced UEs, full-capability UEs, and / or premium UEs. UEs 120 in the third category may have intermediate-level complexity and / or capabilities (e.g., capabilities between those of UEs 120 in the first category and those of UEs 120 in the second category). UEs 120 in the third category may be referred to as reduced-capability UEs (“RedCap UEs”), intermediate-level UEs, NR lightweight UEs, and / or NR simplified UEs, etc. RedCap UEs bridge the gap in capabilities and complexity between NB-IoT devices and / or eMTC UEs and mission-critical IoT devices and / or premium UEs. RedCap UEs can include, for example, wearable devices, IoT devices, industrial sensors, and / or cameras associated with limited bandwidth, power capacity, and / or transmission range. RedCap UEs can support healthcare environments, building automation, power distribution, process automation, transportation and logistics, and / or smart city deployments, among others.

[0066] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) can communicate directly with each other using sidelink communication (e.g., without communication through a network node 110 acting as an intermediary). As an example, UE 120a can directly send data, control information, or other signaling to UE 120e as sidelink communication. This contrasts with, for example, UE 120a first sending data to network node 110 in UL communication, and then that network node sending data to UE 120e in DL communication. In various examples, UE 120 can use peer-to-peer (P2P) communication protocols, device-to-device (D2D) communication protocols, vehicle-to-everything (V2X) communication protocols (which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, and / or vehicle-to-pedestrian (V2P) protocols), and / or mesh network communication protocols to send and receive sidelink communication. In some deployments and configurations, network node 110 may schedule and / or allocate resources for sidelink communication between UEs 120 in the wireless communication network 100. In some other deployments and configurations, UE 120 (instead of network node 110) may perform or cooperate with or negotiate with one or more other UEs to perform scheduling operations, resource selection operations, and / or other operations for sidelink communication.

[0067] In various examples, in addition to half-duplex operation, some network nodes and UEs in the wireless communication network 100, including network node 110 and UE 120, can also be configured for full-duplex operation. Network node 110 or UE 120 operating in half-duplex mode can perform only one of transmission or reception during a specific time resource period (such as a specific time slot, symbol, or other time period). Half-duplex operation may involve time division duplex (TDD), where the DL transmission of network node 110 and the UL transmission of UE 120 do not occur in the same time resource (i.e., the transmissions do not overlap in time). In contrast, network node 110 or UE 120 operating in full-duplex mode can transmit and receive communications concurrently (e.g., within the same time resource). By operating in full-duplex mode, network node 110 and / or UE 120 can generally increase the capacity of the network and radio access links. In some examples, full-duplex operation may involve frequency division duplex (FDD), in which network node 110 performs DL transmission in a first frequency band or on a first component carrier, and UE 120 performs transmission in a second frequency band or on a second component carrier, the second frequency band or the second component carrier being different from the first frequency band or the first component carrier, respectively. In some examples, full-duplex operation may be enabled for UE 120 but not for network node 110. For example, UE 120 may simultaneously transmit UL to the first network node 110 and receive DL transmissions from the second network node 110 in the same time resources. In some other examples, full-duplex operation may be enabled for network node 110 but not for UE 120. For example, network node 110 may simultaneously transmit DL to the first UE 120 and receive UL transmissions from the second UE 120 in the same time resources. In some other examples, full-duplex operation may be enabled for both network node 110 and UE 120.

[0068] In some examples, UE 120 and network node 110 can perform MIMO communication. "MIMO" generally refers to the simultaneous transmission or reception of multiple signals (such as multiple layers or multiple data streams) using the same time and frequency resources. MIMO techniques typically utilize multipath propagation. MIMO can be implemented using various spatial processing or spatial multiplexing operations. In some examples, MIMO can support simultaneous transmission to multiple receivers, which is called multi-user MIMO (MU-MIMO). Some RATs can employ advanced MIMO techniques such as mTRP operations (including redundant transmission or reception on multiple TRPs), reciprocity in the time or frequency domain, single-frequency network (SFN) transmission, or noncoherent joint transmission (NC-JT).

[0069] In some aspects, UE 120 includes: components for receiving a closed-loop timing advance command message, the closed-loop timing advance command message including an indicator associated with the closed-loop timing advance command message, the indicator including at least one of a timing advance value or an uplink transmission extension indicator; and / or components for transmitting one or more communications on the uplink based on an interpretation of the closed-loop timing advance command message, the interpretation of the closed-loop timing advance command message being based on the indicator. Components enabling UE 120 to perform the operations described herein may include, for example, one or more of a communications manager 140, an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, or a memory 282.

[0070] In some aspects, network node 110 includes: components for transmitting a closed-loop timing advance command message, the closed-loop timing advance command message including an indicator associated with the closed-loop timing advance command message, the indicator including at least one of a timing advance value or an uplink transmission extension indicator; and / or components for receiving one or more communications on the uplink based on an interpretation of the closed-loop timing advance command message, the interpretation of the closed-loop timing advance command message being based on the indicator. Components enabling network node 110 to perform the operations described herein may include, for example, one or more of a communication manager 150, a transmit processor 214, a TX MIMO processor 216, a modem 232, an antenna 234, a MIMO detector 236, a receive processor 238, a controller / processor 240, a memory 242, or a scheduler 246.

[0071] As indicated above, Figure 1 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 1 The examples described are different.

[0072] Figure 2 This is a diagram illustrating communication between an example network node 110 and an example UE 120 in a wireless network according to the present disclosure.

[0073] like Figure 2As shown, network node 110 may include a data source 212, a transmit processor 214, a transmit (TX) MIMO processor 216, a set of modems 232 (shown as 232a to 232t, where t≥1), a set of antennas 234 (shown as 234a to 234v, where v≥1), a MIMO detector 236, a receive processor 238, a data sink 239, a controller / processor 240, a memory 242, a communication unit 244, a scheduler 246, and / or a communication manager 150, etc. In some configurations, one or a combination of antennas 234, modems 232, MIMO detectors 236, receive processors 238, transmit processors 214, and / or TX MIMO processors 216 may be included in the transceiver of network node 110. The transceiver may be under the control of and used by one or more processors (such as controller / processor 240), and in some respects, may perform aspects of the methods, procedures and / or operations described herein in conjunction with processor-readable code stored in memory 242. In some respects, network node 110 may include one or more interfaces, communication components and / or other components that facilitate communication with UE 120 or another network node.

[0074] The terms “processor,” “controller,” or “controller / processor” can refer to one or more controllers and / or one or more processors. For example, references to “a / the processor,” “a / the controller / processor,” etc. (in the singular) should be understood as referring to a combination of… Figure 2 The processor described refers to any one or more processors, such as a single processor or a combination of multiple different processors. The reference to "one or more processors" should be understood as a combination of references. Figure 2 Any one or more processors described herein. For example, one or more processors of network node 110 may include transmit processor 214, TX MIMO processor 216, MIMO detector 236, receive processor 238, and / or controller / processor 240. Similarly, one or more processors of UE 120 may include MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, and / or controller / processor 280.

[0075] In some aspects, a single processor can perform all operations described as being performed by one or more processors. In some aspects, a first set of one or more processors can perform a first operation described as being performed by that one or more processors, and a second set of one or more processors can perform a second operation described as being performed by that one or more processors. The first set of processors and the second set of processors can be the same set of processors or can be different sets of processors. The reference to "one or more memories" should be understood to refer to any one or more memories of the corresponding device, such as those in combination. Figure 2 The memory described. For example, an operation described as being performed by one or more memories can be performed by the same subset of the one or more memories or by different subsets of the one or more memories.

[0076] For downlink communication from network node 110 to UE 120, transmit processor 214 may receive data (“downlink data”) intended for use by UE 120 (or a set of UEs including UE 120) from data source 212 (such as a data pipeline or data queue). In some examples, transmit processor 214 may select one or more MCSs for UE 120 based on one or more Channel Quality Indicators (CQIs) received from UE 120. Network node 110 may process the data (e.g., including encoding the data) according to the MCS selected for UE 120 for transmission to UE 120 on the downlink, thereby generating data symbols. Transmit processor 214 may process system information (e.g., semi-static resource partitioning information (SRPI)) and / or control information (e.g., CQI requests, grants, and / or upper-layer signaling) and provide overhead symbols and / or control symbols. The transmitting processor 214 can generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS), demodulation reference signals (DMRS), or channel state information (CSI) reference signals (CSI-RS)) and / or synchronization signals (e.g., primary synchronization signal (PSS) or secondary synchronization signal (SSS)).

[0077] The TX MIMO processor 216 can perform space processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols where applicable, and can output a set of symbol streams (e.g., TA set of output symbol streams is provided to modem 232. For example, each output symbol stream may be provided to a corresponding modulator component (shown as MOD) of modem 232. Each modem 232 may use the corresponding modulator component to process (e.g., modulate) the corresponding output symbol stream (e.g., for orthogonal frequency division multiplexing (OFDM)) to obtain an output sample stream. Each modem 232 may further use the corresponding modulator component to process (e.g., convert to analog, amplify, filter, and / or upconvert) the output sample stream to obtain a time-domain downlink signal. Modems 232a to 232t may transmit the set of downlink signals (e.g., via a set of corresponding antennas 234) together. T (One downlink signal).

[0078] Downlink signals may include DCI communication, MAC control element (MAC-CE) communication, RRC communication, downlink reference signals, or another type of downlink communication. Downlink signals may be transmitted on the PDCCH, PDSCH, and / or on another downlink channel. Downlink signals may carry one or more transport blocks (TBs) of data. A TB may be a data unit transmitted via the air interface in the wireless communication network 100. A data stream (e.g., from data source 212) may be encoded into multiple TBs for transmission via the air interface. The number of TBs used to carry data associated with a particular data stream may be associated with a TB size shared by multiple TBs. The TB size may be based on the radio channel conditions of the air interface, the MCS used to encode the data, downlink resources allocated for transmitting data, and / or other parameters, or otherwise associated with them. Generally, a larger TB size allows for a larger amount of data to be transmitted in a single transmission, reducing signaling overhead. However, a larger TB size may be more prone to transmission and / or reception errors than a smaller TB size, but such errors can be mitigated through more robust error correction techniques.

[0079] For uplink communication from UE 120 to network node 110, the uplink signal from UE 120 may be received by antenna 234, processed by modem 232 (e.g., demodulator component of modem 232, shown as DEMOD), detected where applicable by MIMO detector 236 (e.g., receive (Rx) MIMO processor), and / or further processed by receive processor 238 to obtain decoded data and / or control information. Receive processor 238 may provide the decoded data to data sink 239 (which may be a data pipeline, data queue, and / or another type of data sink) and provide the decoded control information to processors such as controller / processor 240.

[0080] Network node 110 may use scheduler 246 to schedule one or more UEs 120 for downlink or uplink communication. In some aspects, scheduler 246 may use DCI to dynamically schedule DL transmissions to and / or UL transmissions from UE 120. In some examples, scheduler 246 may allocate repetitive time-domain and / or frequency-domain resources that UE 120 may use for transmitting and / or receiving communication with RRC configuration (e.g., semi-static configuration), for example, to perform semi-persistent scheduling (SPS) or to configure configuration grant (CG) for UE 120.

[0081] One or more of the following may be included in the RF chain of network node 110: transmit processor 214, TX MIMO processor 216, modem 232, antenna 234, MIMO detector 236, receive processor 238, and / or controller / processor 240. The RF chain may include one or more filters, mixers, oscillators, amplifiers, analog-to-digital converters (ADCs), and / or other devices for converting analog signals (such as those used for transmission or reception via an air interface) to digital signals (such as those used for processing by one or more processors of network node 110). In some aspects, the RF chain may be a transceiver of network node 110, or may be included in such a transceiver.

[0082] In some examples, network node 110 may use communication unit 244 to communicate with the core network and / or other network nodes. Communication unit 244 may support wired and / or wireless communication protocols and / or connections, such as Ethernet, fiber optic, Common Public Radio Interface (CPRI), and / or wired or wireless backhaul, etc. Network node 110 may use communication unit 244 to send and / or receive data associated with UE 120, or to execute network control signaling, etc. Communication unit 244 may include transceivers and / or interfaces, such as network interfaces.

[0083] UE 120 may include a collection of antennas 252 (shown as antennas 252a to 252r, where r ≥ 1), a collection of modems 254 (shown as modems 254a to 254u, where u ≥ 1), a MIMO detector 256, a receive processor 258, a data sink 260, a data source 262, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, a memory 282, and / or a communication manager 140, etc. One or more components of UE 120 may be included in housing 284. In some aspects, one or a combination of antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, or TX MIMO processor 266 may be included in a transceiver included in UE 120. The transceiver may be under the control of and used by one or more processors (such as controller / processor 280), and in some respects, may perform aspects of the methods, procedures, or operations described herein in conjunction with processor-readable code stored in memory 282. In some respects, UE 120 may include another interface, another communication component, and / or another component that facilitates communication with network node 110 and / or another UE 120.

[0084] For downlink communication from network node 110 to UE 120, the set of antennas 252 can receive downlink communication or signals from network node 110, and can receive the set of downlink signals (e.g., R Each received signal is provided to a set of modems 254. For example, each received signal may be provided to a corresponding demodulator component (shown as DEMOD) of modem 254. Each modem 254 may use the corresponding demodulator component to condition (e.g., filter, amplify, down-convert, and / or digitize) the received signal to obtain an input sample. Each modem 254 may use the corresponding demodulator component to further demodulate or process the input sample (e.g., for OFDM) to obtain a received symbol. MIMO detector 256 may obtain the received symbols from the set of modems 254, may perform MIMO detection on the received symbols where applicable, and may provide the detected symbols. Receiver processor 258 may process (e.g., decode) the detected symbols, may provide the decoded data for UE 120 to data sink 260 (which may include data pipelines, data queues, and / or applications executed on UE 120), and may provide the decoded control information and system information to controller / processor 280.

[0085] For uplink communication from UE 120 to network node 110, the transmitting processor 264 may receive and process data (“uplink data”) from data source 262 (such as data pipelines, data queues, and / or applications running on UE 120) and control information from controller / processor 280. The control information may include one or more parameters, feedback, one or more signal measurements, and / or other types of control information. In some aspects, the receiving processor 258 and / or controller / processor 280 may determine one or more parameters related to the transmission of uplink communication for received signals (such as those received from network node 110 or another UE). One or more parameters may include a Reference Signal Received Power (RSRP) parameter, a Received Signal Strength Indicator (RSSI) parameter, a Reference Signal Received Quality (RSRQ) parameter, a CQI parameter, or a Transmit Power Control (TPC) parameter, etc. The control information may include indications of the RSRP parameter, RSSI parameter, RSRQ parameter, CQI parameter, TPC parameter, and / or another parameter. Control information can facilitate parameter selection and / or scheduling for UE 120 by network node 110.

[0086] Transmit processor 264 can generate reference symbols for one or more reference signals, such as uplink DMRS, uplink sounding reference signal (SRS), and / or another type of reference signal. Symbols from transmit processor 264 can be pre-decoded by TX MIMO processor 266 where applicable, and further processed by a set of modems 254 (e.g., for DFT-s-OFDM or CP-OFDM). TX MIMO processor 266 can perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols where applicable, and can output a set of symbol streams (e.g., ... U A set of output symbol streams is provided to modem 254. For example, each output symbol stream may be provided to a corresponding modulator component (shown as MOD) of modem 254. Each modem 254 may use the corresponding modulator component to process (e.g., modulate) the corresponding output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modem 254 may further use the corresponding modulator component to process (e.g., convert to analog, amplify, filter, and / or upconvert) the output sample stream to obtain an uplink signal.

[0087] Modems 254a to 254u can transmit uplink signal sets (e.g., via a set of corresponding antennas 252) R One uplink signal or UUplink signals may include UCI communication, MAC-CE communication, RRC communication, or another type of uplink communication. Uplink signals may be transmitted on PUSCH, PUCCH, and / or another type of uplink channel. Uplink signals may carry one or more TBs of data. Sidelink data and control transmission (i.e., transmission directly between two or more UEs 120) may typically use techniques similar to those described for uplink data and control transmission, and may use sidelink-specific channels such as the Physical Sidelink Shared Channel (PSSCH), Physical Sidelink Control Channel (PSCCH), and / or Physical Sidelink Feedback Channel (PSFCH).

[0088] One or more antennas in the set of antennas 252 or the set of antennas 234 may include one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, etc., or may be included in one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, or antenna arrays may include one or more antenna elements (within a single housing or multiple housings), a set of coplanar antenna elements, a set of non-coplanar antenna elements, or with one or more transmitting or receiving components (such as...) Figure 2 An antenna module is a combination of one or more antenna elements coupled to one or more components. As used herein, "antenna" can mean one or more antennas, one or more antenna panels, one or more antenna groups, one or more collections of antenna elements, or one or more antenna arrays. "Antenna panel" can mean a group of antennas (such as antenna elements) arranged in an array or panel that can facilitate beamforming by manipulating the parameters of that group of antennas. "Antenna module" can mean a circuit that includes one or more antennas, and may also include one or more other components (such as filters, amplifiers, or processors) associated with integrating the antenna module into a wireless communication device.

[0089] In some examples, each antenna element of antenna 234 or antenna 252 may include one or more sub-elements for radiating or receiving radio frequency signals. For example, a single antenna element may include a first sub-element cross-polarized with a second sub-element that can be used to independently transmit the cross-polarized signal. Antenna elements may include patch antennas, dipole antennas, and / or other types of antennas arranged in a linear pattern, a two-dimensional pattern, or another pattern. The spacing between antenna elements can allow signals with a desired wavelength transmitted individually by the antenna elements to interact or interfere (e.g., to form a desired beam) in various directions. For example, given a desired wavelength or frequency range, the spacing may provide a quarter wavelength, half a wavelength, or another fraction of the wavelength between adjacent antenna elements to allow desired constructive and destructive interference modes of signals transmitted by individual antenna elements within that desired range.

[0090] The amplitude and / or phase of signals transmitted via antenna elements and / or sub-elements can be modulated and (e.g., by manipulating phase shifts, phase offsets, and / or amplitudes) shifted relative to each other to generate one or more beams; this is known as beamforming. The term "beam" can refer to the directional transmission of a wireless signal toward a receiving device or otherwise in a desired direction. "Beam" can also generally refer to the direction associated with such directional signal transmission, the set of directional resources associated with the signal transmission (e.g., angle of arrival, horizontal direction, and / or vertical direction), and / or a set of parameters indicating one or more aspects of the directional signal, the direction associated with the signal, and / or the set of directional resources associated with the signal. In some implementations, antenna elements can be individually selected or deselected for the directional transmission of a signal (or multiple signals) by controlling the amplitude of one or more corresponding amplifiers and / or the phase of the signal to form one or more beams. The shape of the beam (such as amplitude, width, and / or the presence of sidelobes) and / or the direction of the beam (such as the angle of the beam relative to the surface of the antenna array) can be dynamically controlled by modifying the phase shifts, phase offsets, and / or amplitudes of multiple signals relative to each other.

[0091] Different UEs 120 or network nodes 110 may include different numbers of antenna elements. For example, UE 120 may include a single antenna element, two antenna elements, four antenna elements, eight antenna elements, or different numbers of antenna elements. As another example, network node 110 may include eight antenna elements, 24 antenna elements, 64 antenna elements, 128 antenna elements, or different numbers of antenna elements. Generally speaking, a larger number of antenna elements provides increased control over the parameters used for beamforming compared to a smaller number of antenna elements, while a smaller number of antenna elements may be less complex to implement and can use less power. Multiple antenna elements can support multi-layer transmission, in which the same time and frequency resources are used to utilize spatial multiplexing to transmit a first layer of communication (which may include a first data stream) and a second layer of communication (which may include a second data stream).

[0092] Although Figure 2 The boxes in the diagram are illustrated as different components, but the functions described above with respect to these boxes may be implemented in a single hardware, software, or combined component, or in various combinations of components. For example, the functions described with respect to transmit processor 264, receive processor 258, and / or TX MIMO processor 266 may be performed by or under the control of controller / processor 280.

[0093] Figure 3 This is an illustration of an example disaggregated base station architecture 300 according to the present disclosure. One or more components of the example disaggregated base station architecture 300 may be, may include, or may be included in one or more network nodes (such as one or more network nodes 110). The disaggregated base station architecture 300 may include a CU 310, which may communicate directly with the core network 320 via a backhaul link, or may communicate indirectly with the core network 320 via one or more disaggregated control units (such as non-RT RIC 350 and / or near-RT RIC 370 associated with a Service Management and Orchestration (SMO) framework 360 (e.g., via an E2 link)). The CU 310 may communicate with one or more DUs 330 via a corresponding midhaul link (such as via an F1 interface). Each DU in the DU 330 may communicate with one or more RUs 340 via a corresponding fronthaul link. Each RU in the RU 340 may communicate with one or more UEs 120 via a corresponding RF access link. In some deployments, UE 120 can be served by multiple RU 340s simultaneously.

[0094] Each component in the decomposed base station architecture 300 (including CU 310, DU 330, RU 340, near-RT RIC 370, non-RT RIC 350, and SMO frame 360) may include one or more interfaces or be coupled to one or more interfaces for receiving or transmitting signals, such as data or information, via wired or wireless transmission media.

[0095] In some respects, the CU 310 can be logically divided into one or more CU user plane (CU-UP) units and one or more CU control plane (CU-CP) units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 310 can be deployed to communicate with one or more DU 330s for network control and signaling, as needed. Each DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RU 340s. For example, the DU 330 may host various layers, such as the RLC layer, MAC layer, or one or more PHY layers (such as one or more high PHY layers or one or more low PHY layers). Each layer (which may also be referred to as a module) can be implemented using an interface for signaling to other layers (and modules) hosted by the DU 330, or for signaling to control functions hosted by the CU 310. Each RU 340 may implement lower-layer functionality. In some respects, the real-time and non-real-time aspects of communication with the control plane and user plane of the RU 340 can be controlled by the corresponding DU 330.

[0096] The SMO framework 360 supports RAN deployment and provisioning for both non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 360 supports the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, the SMO framework 360 can interact with cloud computing platforms such as the Open Cloud (O-Cloud) platform 390 to perform network element lifecycle management (such as instantiating virtualized network elements) via cloud computing platform interfaces such as the O2 interface. Virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 350, and / or near-RT RIC 370. In some aspects, the SMO framework 360 can communicate with hardware aspects of the 4G RAN, 5G NR RAN, and / or 6G RAN (such as the Open eNB (O-eNB) 380) via the O1 interface. Additionally or alternatively, the SMO framework 360 can communicate directly with each of one or more RUs 340 via the corresponding O1 interface. In some deployments, this configuration enables each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0097] The non-RT RIC 350 may include or implement logic functions that enable non-real-time control and optimization of RAN elements and resources, including AI / ML workflows for model training and updates, and / or policy-based guidance of applications and / or features in the near-RT RIC 370. The non-RT RIC 350 may be coupled to or communicate with the near-RT RIC 370, such as via an A1 interface. The near-RT RIC 370 may include or implement logic functions that enable near real-time control and optimization of RAN elements and resources via an interface, such as an E2 interface, through data collection and actions, connecting one or more CU 310s, one or more DU 330s, and / or O-eNBs to the near-RT RIC 370.

[0098] In some aspects, to generate AI / ML models to be deployed in the near-RT RIC 370, the non-RT RIC 350 may receive parameters or external enrichment information from an external server. This information can be utilized by the near-RT RIC 370 and can be received from non-network data sources or network functions at the SMO framework 360 or the non-RT RIC 350. In some examples, the non-RT RIC 350 or near-RT RIC 370 may modulate RAN behavior or performance. For example, the non-RT RIC 350 may monitor long-term trends and patterns in performance and may employ AI / ML models to perform corrective actions via the SMO framework 360 (such as reconfiguration via the O1 interface) or via the creation of RAN management policies (such as A1 interface policies).

[0099] As indicated above, Figure 3 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 3 The examples described are different.

[0100] Figure 1 , Figure 2 or Figure 3 Network node 110, its controller / processor 240, UE 120, UE 120's controller / processor 280, CU 310, DU 330, RU 340, or any other component may implement one or more technologies associated with uplink transmit timer extension or perform one or more operations associated with uplink transmit timer extension, as described in more detail elsewhere herein. For example, network node 110's controller / processor 240, UE 120's controller / processor 280, CU 310, DU 330, RU 340, or any other component may implement one or more technologies associated with uplink transmit timer extension or perform one or more operations associated with uplink transmit timer extension, as described in more detail elsewhere herein. Figure 2 Any other component, CU 310, DU 330, or RU 340 may execute or instruct, for example Figure 7 Process 700 Figure 8The operation of process 800 or other processes as described herein (alone or in combination with one or more other processors). Memory 242 may store data and program code for network node 110, CU 310, DU 330, or RU 340. Memory 282 may store data and program code for UE 120. In some examples, memory 242 or memory 282 may include a non-transitory computer-readable medium storing a set of instructions (e.g., code or program code) for wireless communication. Memory 242 may include one or more memories, such as a single memory or multiple different memories (of the same or different types). Memory 282 may include one or more memories, such as a single memory or multiple different memories (of the same or different types). For example, the set of instructions may be made executable by one or more processors of network node 110, UE 120, CU 310, DU 330, or RU 340 when executed (e.g., directly, or after compilation, transformation, or interpretation). Figure 7 Process 700 Figure 8 The process 800 or other processes as described herein. In some examples, the execution instructions may include run instructions, transform instructions, compile instructions, and / or interpret instructions, etc.

[0101] Figure 4 This is a diagram illustrating example 400 of downlink and uplink transmissions between network node 110 and UE 120 in a wireless network 100 according to this disclosure. In some examples, downlink and / or uplink transmissions are based at least in part on timing advance and / or a protection period between communications. As an example, network node 110 may be configured to end downlink transmissions before the start of the protection period. As another example, UE 120 may advance the start time of uplink transmissions at least in part based on timing advance.

[0102] As indicated by reference numeral 402-1, network node 110 may initiate downlink transmission 404-1 to UE 120 at a first time point. In some examples, the first time point may be based at least in part on a timing scheme defined by a telecommunications system and / or telecommunications standard. For illustration, telecommunications standards may define various time divisions for scheduling transmissions between devices. As an example, a timing scheme may define radio frames (sometimes called frames), where each radio frame has a predetermined duration (e.g., 10 milliseconds (msec)). Each radio frame may be further divided into a set Z ( Z ≥1) subframes, wherein each subframe may have a predetermined duration (e.g., 1 msec). Each subframe may be further divided into a set of time slots and / or each time slot may include a set of LA symbol period (e.g., fourteen symbol periods, seven symbol periods, or another number of symbol periods). Thus, the first time point as indicated by reference numeral 402-1 may be based at least in part on time divisions as defined by the telecommunications system (e.g., frames, subframes, time slots, mini-time slots, and / or symbols).

[0103] In some examples, network node 110 and UE 120 may communicate wirelessly with each other, at least in part, based on a defined time division (e.g., directly or via one or more network nodes). However, each device may have a different timing reference for the time division. For illustration, and as shown by reference numeral 402-1, network node 110 may begin downlink transmission 404-1 at a specific time point, which may be associated at least in part with the time angle of network node 110 in relation to a defined time division. For example, network node 110 may associate the specific time point with a defined time division (such as the start of a symbol, the start of a time slot, the start of a subframe, and / or the start of a frame).

[0104] However, downlink transmissions may cause a time propagation delay 406, such as a time delay based at least in part on the downlink transmission traveling between network node 110 (e.g., RU) and UE 120. As shown by reference numeral 402-2, UE 120 may receive downlink transmission 404-2 (corresponding to downlink transmission 404-1 transmitted by network node 110) at a second time point, which is later than the first time point. However, from the time perspective of UE 120, UE 120 may associate the second physical time point shown by reference numeral 402-2 with a specific time point of the same defined time division as network node 110 (e.g., the start of the same symbol, the start of the same mini-slot, the start of the same slot, the start of the same subframe, and / or the start of the same frame). Therefore, as shown by example 400, there may be a time delay between the time perspective of UE 120 and the time perspective of network node 110.

[0105] In wireless communication technologies such as 4G / LTE and 5G / NR, a timing advance (TA) value is used to control the timing of uplink transmissions by a UE (e.g., UE120, etc.), such that a network node 110 (e.g., RU) receives the uplink transmission at a time aligned with its internal timing. The network node 110 can determine the TA value to the UE (e.g., directly or via one or more network nodes) by measuring the time difference between the reception of the uplink transmission from the UE and the subframe timing used by the network node 110 (e.g., by determining the difference between when the uplink transmission was assumed to have been received by the network node 110 according to the subframe timing and when it was actually received). The network node 110 can send a TA command (TAC) to instruct the UE to transmit future uplink communication earlier or later, thereby reducing or eliminating the time difference and aligning the timing between the UE and the network node 110. For example, as shown by reference numeral 401, the network node 110 can send a MAC CE, which includes a timing advance command as at least one octet of the MAC CE. The MAC CE includes a Timing Advance Group (TAG) identifier and a TA command. The TAG identifier indicates which TAG the TA command applies to. In some examples, the MAC CE may include a Language Code Identifier (LCID) code point, as described in more detail herein. The TA command is used to cancel timing differences between the UE and network node 110 caused by different propagation delays occurring when the UE is at different distances from network node 110. If the TA command is not used, uplink transmissions from different UEs (e.g., located at different distances from network node 110) may conflict due to timing deviations, even if uplink transmissions are scheduled for different subframes.

[0106] For illustration, without adjusting the start time of uplink transmission, UE 120 can be configured to begin uplink transmission at a scheduled time point at least in part based on a time division defined elsewhere herein. As shown by reference numeral 410-1, the start of the scheduled time point can occur at a third physical time point at least in part based on the timing angle of UE 120. However, and as shown by reference numeral 410-2, the scheduled time point referencing the timing angle of network node 110 (e.g., RU) can occur at a fourth physical time point, which precedes the third physical time point as shown by reference numeral 410-1. Therefore, network node 110 can (e.g., directly or via one or more network nodes) instruct UE 120 to apply timing advance 408 to uplink transmission to better align the reception of uplink transmission with the timing angle of network node 110. However, in some examples, the fourth time point indicated by reference numeral 410-2 may occur at or near the same physical time point as the third time point indicated by reference numeral 410-1, causing uplink transmission from UE 120 to network node 110 to result in a propagation delay 406. In such scenarios, network node 110 may instruct UE 120 to apply a timing advance with a time duration corresponding to the propagation delay 406. Network node 110 may send a Media Access Control (MAC) control element (CE) with a configured format to convey a timing advance command or timing advance value associated with identifying the timing advance.

[0107] As illustrated in Example 400, UE 120 may adjust the start time of uplink transmission 412-1 at least in part based on timing advance 408 and the start of the scheduling time point (e.g., at the third physical time point indicated by reference numeral 410-1). Based at least in part on propagation delay, network node 110 may receive uplink transmission 412-2 (corresponding to uplink transmission 412-1 transmitted by UE 120) at the fourth physical time point indicated by reference numeral 410-2.

[0108] In some examples, the timing advance value may be based at least in part on twice the estimated propagation delay (e.g., propagation delay 406) and / or at least in part on the round-trip time (RTT). Some network deployments (such as non-terrestrial network (NTN) deployments or network deployments with repeaters) may have relatively large RTT values, which may make the use of timing advance beneficial in avoiding resource conflicts and / or communication interruptions. Network node 110 (e.g., DU or CU) may estimate the propagation delay and / or select the timing advance value at least in part based on communication with UE 120. As an example, network node 110 may estimate the propagation delay at least in part based on network access request messages from UE 120. Additionally or alternatively, network node 110 may estimate and / or select the timing advance value from a fixed set of timing advance values.

[0109] As indicated above, Figure 4 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 4 The examples described are different.

[0110] Figure 5 This is a diagram illustrating example 500 of an uplink transmit timer extension according to this disclosure. For example... Figure 5 As shown, Example 500 includes communication between network node 110 and UE 120.

[0111] As in Figure 5 As shown by reference numeral 502, UE 120 and network node 110 can communicate within resource sets (such as resource block (RB) sets, symbol sets, time slot sets, or frame sets). For example, UE 120 can transmit to network node 110 on the uplink. As shown by reference numeral 504, UE 120 can receive TA commands from network node 110. For example, UE 120 can receive a MAC CE associated with conveying the TA command to maintain timing synchronization between UE 120 and network node 110. As shown, the MAC CE may include a TAG ID and the TA command. Furthermore, the MAC CE may include a MAC subheader with a Language Code Identifier (LCID) code point. The LCID code point can be a configurable value that can be assigned to one or more indications (such as an indication of a recommended bit rate, an indication of a TA command, or a padding bit set), or can be reserved for another purpose, as described herein. As indicated by reference numeral 506, at the first moment, based on receiving a TA command from network node 110, UE 120 may start a timing alignment timer (TAT timer). For example, UE 120 may start a TAT timer based on having received a TA command to track the period during which UE 120 maintains timing synchronization with network node 110.

[0112] As in Figure 5 As further illustrated by reference numeral 508, at a second time, the Global Navigation Satellite System (GNSS) validity expires for UE 120. GNSS validity is a period of time following the execution of GNSS measurements during which the positioning information of UE 120 is considered valid. In other words, UE 120 performs GNSS signal measurements and can determine positioning information (e.g., position, velocity, direction) based on these measurements (e.g., using triangulation or trilateration). After performing GNSS signal measurements, UE 120 starts a GNSS validity timer. Each time UE 120 performs another GNSS measurement, UE 120 resets the GNSS validity timer. However, when the GNSS validity timer expires and UE 120 has not performed a GNSS measurement, UE 120 may consider the positioning information outdated and invalid for uplink synchronization with network node 110 (e.g., in an NTN deployment, this synchronization is calculated based on UE 120's first positioning and network node 110's second positioning). When GNSS validity expires, UE 120 can switch to Radio Resource Control (RRC) idle mode (e.g., from RRC connected mode) to restore GNSS validity.

[0113] However, when UE 120 has received a TA command to synchronize timing with network node 110, UE 120 can extend the uplink transmission for a certain period of time. For example, as shown by reference numeral 510, UE 120 can start an uplink transmission extension timer. T3xx In relation to timers T3xx During the associated uplink transmission extension period, UE 120 can use timing synchronization derived from the timing advance command to continue transmitting on the uplink. As shown by reference numeral 512, during the uplink transmission extension timer... T3xx When the timer expires, the TAT timer may not have expired yet. In other words, it is related to the timer... T3xx The associated uplink transmission extension period has expired, but the timing advance command to synchronize UE 120 with network node 110 remains valid. Therefore, UE 120 may be able to start and reset the timer. T3xx The associated new uplink transmission extension period. However, no signaling was established from network node 110 to indicate the timer. T3xx In the event of a reset, there may be a conflict between network node 110 and UE 120 regarding whether UE 120 has reset its timer. T3xx Alternatively, it may transition to an RRC idle state to restore GNSS validity. In this scenario, network node 110 may lose synchronization with UE 120 and may experience a communication interruption.

[0114] As indicated above, Figure 5 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 5 The examples described are different.

[0115] The overall scope involves uplink transmit timer extensions across various aspects. Some aspects are more specifically related to a single MAC CE format, which can be used to convey uplink transmit extension commands and reset timers. T3xx And for conveying TA commands. In some aspects, network nodes can configure reserved bit indicators in the MAC CE to indicate whether the MAC CE is signaling a TA command or sending an uplink extended command. For example, a network node can set a Language Code Identifier (LCID) code point to indicate that the MAC CE is conveying a TA command, sending an uplink extended command, or a TA command with uplink extended command. The LCID code point can be conveyed in the LCID field of the MAC CE subheader. Additionally or alternatively, a network node can set a Timing Advance Group (TAG) identifier in the TA command to indicate whether the MAC CE is conveying a TA command, sending an uplink extended command, or a TA command with uplink extended command.

[0116] Specific aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential improvements. In some examples, by including an indicator in the MAC CE to indicate the purpose of the MAC CE, the described techniques can be used to provide TA commands, uplink transmission extensions, or TA commands with uplink transmission extensions within a MAC CE of the same format. By providing multiple possible messages using a MAC CE of the same format, the described techniques improve signaling flexibility without additional signaling overhead. By providing uplink transmission extensions within a TA command MAC CE, the described techniques improve network flexibility relative to extending uplink transmissions performed by the UE after the expiration of GNSS validity.

[0117] Figure 6 This is a diagram illustrating example 600 associated with an uplink transmit timer extension according to this disclosure. (See diagram for example...) Figure 6 As shown, Example 600 includes communication between network node 110 and UE 120.

[0118] As in Figure 6As further shown by reference numeral 610 in the accompanying drawings, UE 120 may receive a TA command. For example, UE 120 may receive a MAC CE having a configuration format for conveying the TA command. In some aspects, the TA command may include a TA value that UE 120 may use to synchronize communication with network node 110. For example, UE 120 may apply the TA value and may start a TAT timer associated with the period during which the tracking TA command remains valid.

[0119] As in Figure 6 As further illustrated by reference numeral 620 in the accompanying drawing, UE 120 can determine the expiration of GNSS validity. For example, UE 120 can determine that a positioning timer associated with a GNSS measurement has expired. In this example, UE 120 can determine that no new GNSS measurement has been performed within at least the configured time period, and can determine that the previous GNSS measurement is invalid. As described above, in some scenarios, UE 120 can enter RRC idle mode to restore GNSS validity. However, as described herein, when UE 120 is configured to use uplink transmission extended timers... T3xx When extending uplink transmission, UE 120 can avoid transitioning to RRC idle mode (e.g., from RRC active mode) and can continue transmitting on the uplink. For example, as shown by reference numeral 630, UE 120 can set an uplink transmission extension timer. T3xx Based on setting the uplink transmission extension timer. T3xx UE 120 may send one or more first uplink transmissions, as shown by reference numeral 640 in the attached figure.

[0120] As in Figure 6 As further shown by reference numeral 650 in the accompanying drawings, UE 120 may receive a TA command. For example, UE 120 may receive a MAC CE in a configuration format associated with conveying the TA command. In some aspects, UE 120 may receive a second TA command after receiving a first TA command. For example, UE 120 may receive a first TA command that triggers UE 120 to set a first uplink transmit extension timer, and may receive a second TA command that triggers UE 120 to reset the first uplink transmit extension timer or set a second uplink transmit extension timer.

[0121] In some respects, network node 110 may configure bit indicators in the MAC CE to indicate the purpose or interpretation of the MAC CE. The MAC CE may include a timing advance command with an uplink transmit extension MAC CE, which is identified by a MAC Protocol Data Unit (PDU) subheader with a configuration indicator. For example, as shown by reference numeral 650-A, network node 110 may configure a reserved LCID code point for downlink scheduling (DL-SCH) using configuration values. In this example, options for the LCID code point value may include a first value indicating that the MAC CE is associated with a first action (such as a timing advance value provided by the application). Additionally or alternatively, options for the LCID code point value may include a second value indicating that the MAC CE is associated with a second action (such as extending uplink transmission after the current GNSS validity period expires or restarting the uplink transmit extension timer). T3xx This is associated with the MAC CE. Additionally or alternatively, the LCID code point may have a value in the closed-loop timing advance command message that indicates both the timing advance value and the uplink transmission extension. For example, as shown, the value "01110" may indicate that the MAC CE is associated with both the TA command and the uplink transmission extension indication. In these examples, when UE 120 receives the MAC CE and the MAC entity of UE 120 reads the MAC CE command and the LCID, UE 120 may apply the MAC CE command to the uplink transmission extension timer. T3xx .

[0122] In some aspects, network node 110 may configure a TAG identifier value in the TA command MAC CE. For example, as shown by reference numeral 650-B, network node 110 may send a MAC CE that includes a TAG identifier value for repurposed purposes, such that when network node 110 includes a configuration value (e.g., 0, 1, or 2, etc.) in the TAG identifier value field, UE 120 may use this configuration behavior to interpret the TA command MAC CE. In this example, the MAC CE may include 2 bits for conveying the TAG ID and 6 bits for conveying the TA command. In one or more examples, when the TAG identifier value is 0, 1, or 2, UE 120 may interpret the TA command MAC CE as providing both the TA command value and an uplink transmission extension indication. Alternatively, in one or more examples, when the TAG identifier value is 3, UE 120 may interpret the TA command MAC CE as not providing an uplink transmission extension indication (even though uplink transmission extension is enabled for UE 120). In other words, when the TA command MAC CE is configured with uplink transmit extension, the configured TAG identifier value (e.g., "3" or bit value "11") indicates, for example, that a special cell (SpCell) has a TAG identifier "0", and the uplink transmit extension is not applicable (not applicable to a specific TA command MAC CE).

[0123] In some respects, UE 120 may interpret the TAG identifier value as an indication of whether the TA command MAC CE provides an uplink transmission extension indication based on the network node 110 configuration. For example, network node 110 may enable or configure uplink transmission extension capability for UE 120. In this example, when UE 120 is configured with uplink transmission extension capability, UE 120 may interpret the TAG identifier field value to determine whether the received TA command MAC CE conveys an uplink transmission extension indication. Additionally or alternatively, UE 120 may interpret the TAG identifier field value based on the LCID code point value. For example, when UE 120 receives a TA command MAC CE with an LCID code point value configured to indicate that uplink transmission extension indication is included, UE 120 may interpret the TAG identifier field value to determine whether uplink transmission extension is applied.

[0124] As in Figure 6As further illustrated by reference numeral 660 in the accompanying drawing, UE 120 sets an uplink transmit extension timer. For example, based on the interpretation of MAC CE as conveying an indication to extend the uplink transmit extension timer, UE 120 may set a new uplink transmit extension timer or reset an existing one. Additionally or alternatively, UE 120 may apply a TA command value. For example, when UE 120 interprets TA command MAC CE as conveying both an uplink transmit extension indication and a TA command value, UE 120 may reset or extend the uplink transmit extension timer and may update the TA value used for timing synchronization.

[0125] In some respects, UE 120 can apply MAC CE commands with configured timing (e.g., uplink transmit timer extension commands received in TA command MAC CE). For example, the MAC entity of UE 120 can wait until the current... T3xx When the timer expires, a notification is sent to the upper layer of UE 120 (e.g., the RRC entity). T3xx The timer is restarted, and the uplink transmission period is extended. In this example, the TA command MAC CE causes the second uplink transmission extension period to occur consecutively with the first uplink transmission extension period, resulting in two complete uplink transmission extension periods for uplink transmission. In other words, when a TA command with an uplink transmission extension MAC CE is received, UE 120 can apply an uplink transmission extension update to extend the first uplink transmission extension period (e.g., as the second uplink transmission extension period).

[0126] Additionally or alternatively, the MAC entity of UE 120 may immediately request the RRC entity of UE 120 to restart. T3xx Timer. In this example, the TA command MAC CE causes the second uplink transmit extension period to interrupt the first uplink transmit period, resulting in fewer than two full uplink transmit extension periods occurring for uplink transmission. In other words, UE120 may experience part of the first... T3xx Timer period and full second T3xx Timer period. Whether to extend the uplink transmission period immediately or after the previous uplink transmission period is completed using the TA command MAC CE can be based on the signaling notification configuration, the specified static configuration, or the indicator in the TA command MAC CE.

[0127] As in Figure 6As further illustrated by reference numeral 670 in the accompanying drawings, UE 120 may transmit one or more uplink transmissions. For example, UE 120 may transmit one or more uplink transmissions during a time period associated with an active uplink transmission extension timer (e.g., before the uplink transmission extension timer expires). In some aspects, one or more uplink transmissions may include a second or more uplink transmissions. For example, UE 120 may transmit a first or more uplink transmissions during a first time period associated with a first uplink transmission extension timer (e.g., triggered by a first TA command MAC CE), and may transmit a second or more uplink transmissions during a second time period associated with a second uplink transmission extension timer (or a reset first uplink transmission extension timer) (e.g., triggered by a second TA command MAC CE). Although some aspects are described herein in reference to two uplink transmission extensions, any number of uplink transmission extensions may be used.

[0128] As indicated above, Figure 6 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 6 The examples described are different.

[0129] Figure 7 This is a diagram illustrating an example process 700 performed, for example, at a UE or a device of a UE, according to this disclosure. Example process 700 is an example in which a device or UE (e.g., UE 120) performs operations associated with an uplink transmit timer extension.

[0130] like Figure 7 As shown, in some aspects, process 700 may include receiving a closed-loop timing advance command message, the closed-loop timing advance command message including an indicator associated with the closed-loop timing advance command message, the indicator including at least one of a timing advance value or an uplink transmission extension indication (box 710). For example, the UE (e.g., using...) Figure 9 The communication manager 140 and / or receiving component 902 depicted herein can receive a closed-loop timing advance command message, which includes an indicator associated with the closed-loop timing advance command message, the indicator including at least one of a timing advance value or an uplink transmission extension indicator, as described above.

[0131] like Figure 7 As shown, in some aspects, process 700 may include including an indicator in the LCID value (box 720). For example, the UE (e.g., using...) Figure 9The communication manager 140 and / or receiving component 902 depicted herein may receive a closed-loop timing advance command message, which includes an LCID value as an indicator of the interpretation of the closed-loop timing advance command, as described above.

[0132] like Figure 7 As shown, in some aspects, process 700 may include including an indicator in the TAG value (box 730). For example, the UE (e.g., using...) Figure 9 The communication manager 140 and / or receiving component 902 depicted herein can receive a closed-loop timing advance command message, which includes a TAG identifier value as an indicator of the interpretation of the closed-loop timing advance command, as described above.

[0133] like Figure 7 As shown, in some aspects, process 700 may include interpreting the closed-loop timing advance command message as a timing advance command (block 740). For example, the UE (e.g., using...) Figure 9 The communication manager 140 and / or determination component 908 described herein may interpret the content of the closed-loop timing advance command message to include the timing advance command, as described above.

[0134] like Figure 7 As shown, in some aspects, process 700 may include interpreting the closed-loop timing advance command message as an uplink transmission extension (box 750). For example, the UE (e.g., using...) Figure 9 The communication manager 140 and / or determination component 908 described herein may interpret the content of the closed-loop timing advance command message to include uplink transmission extensions, as described above.

[0135] like Figure 7 As shown, in some aspects, process 700 may include interpreting the closed-loop timing advance command message as a timing advance command and an uplink transmission extension (box 760). For example, the UE (e.g., using...) Figure 9 The communication manager 140 and / or determination component 908 described herein may interpret the content of the closed-loop timing advance command message as including the timing advance command and uplink transmission extension, as described above.

[0136] like Figure 7 As further shown, in some aspects, process 700 may include sending one or more communications on the uplink based on the interpretation of the closed-loop timing advance command message, the interpretation of which is based on an indicator (box 770). For example, the UE (e.g., using...) Figure 9The communication manager 140 and / or transmitting component 904 described herein can transmit one or more communications on the uplink based on the interpretation of the closed-loop timing advance command message, the interpretation of which is based on an indicator as described above.

[0137] Process 700 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0138] In the first aspect, the closed-loop timing advance command message is the closed-loop timing advance command MAC CE.

[0139] In the second aspect, either alone or in combination with the first aspect, the indicator is a code point that conveys a value mapped to at least one of a timing advance value or an uplink transmission extension indicator.

[0140] In the third aspect, either alone or in combination with one or more of the first and second aspects, the uplink transmission extension indication is associated with the application uplink transmission extension update.

[0141] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, an uplink transmission extension update is applied to the uplink transmission extension timer after the uplink transmission extension timer expires.

[0142] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, an uplink transmission extension update is applied to the uplink transmission extension timer before the uplink transmission extension timer expires.

[0143] In the sixth aspect, the indicator is associated with the TAG identification field, either alone or in combination with one or more of the first to fifth aspects.

[0144] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the first value of the TAG identifier field indicates that the closed-loop timing advance command message conveys a timing advance value and an uplink transmission extension indication, and the second value of the TAG identifier field indicates that the closed-loop timing advance command message conveys a timing advance value and does not convey an uplink transmission extension indication.

[0145] In the eighth aspect, the interpretation of the closed-loop timing advance command message is based on the configuration of the UE capabilities, either alone or in combination with one or more of the first to seventh aspects.

[0146] In the ninth aspect, either alone or in combination with one or more of the first to eighth aspects, the interpretation of the closed-loop timing advance command message is based on the configured logical channel identifier code point value associated with the closed-loop timing advance command message.

[0147] although Figure 7 An example box of process 700 is shown, but in some respects, process 700 may include... Figure 7 The boxes depicted may be fewer, different, or arranged differently compared to additional boxes. Alternatively, two or more boxes in the process 700 may be executed in parallel.

[0148] Figure 8 This is a diagram illustrating an example process 800 performed, for example, at a network node or a device of a network node, according to the present disclosure. Example process 800 is an example in which a device or network node (e.g., network node 110) performs operations associated with an uplink transmit timer extension.

[0149] like Figure 8 As shown, in some aspects, process 800 may include sending a closed-loop timing advance command message, the closed-loop timing advance command message including an indicator associated with the closed-loop timing advance command message, the indicator including at least one of a timing advance value or an uplink transmission extension indicator (box 810). For example, network nodes (e.g., using...) Figure 12 The communication manager 150 and / or the transmitting component 1204 depicted herein can transmit a closed-loop timing advance command message, which includes an indicator associated with the closed-loop timing advance command message, the indicator including at least one of a timing advance value or an uplink transmission extension indicator, as described above.

[0150] like Figure 8 As shown, in some aspects, process 800 may include including an indicator in the LCID value (box 820). For example, a network node (e.g., using...) Figure 12 The communication manager 150 and / or the transmitting component 1204 depicted herein may transmit a closed-loop timing advance command message, which includes an LCID value as an indicator of the interpretation of the closed-loop timing advance command, as described above.

[0151] like Figure 8 As shown, in some aspects, process 800 may include including an indicator in the TAG value (box 830). For example, a network node (e.g., using...) Figure 12 The communication manager 150 and / or transmitting component 1204 depicted herein may transmit a closed-loop timing advance command message, which includes a TAG identifier value as an indicator of the interpretation of the closed-loop timing advance command, as described above.

[0152] like Figure 8 As further shown, in some aspects, process 800 may include receiving one or more communications on the uplink based on the interpretation of a closed-loop timing advance command message, the interpretation of which is based on an indicator (box 840). For example, a network node (e.g., using...) Figure 12 The communication manager 150 and / or receiving component 1202 depicted herein can receive one or more communications on the uplink based on the interpretation of the closed-loop timing advance command message, the interpretation of which is based on an indicator as described above.

[0153] Process 800 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0154] In the first aspect, the closed-loop timing advance command message is the closed-loop timing advance command MAC CE.

[0155] In the second aspect, either alone or in combination with the first aspect, the indicator is a code point that conveys a value mapped to at least one of a timing advance value or an uplink transmission extension indicator.

[0156] In the third aspect, either alone or in combination with one or more of the first and second aspects, the uplink transmission extension indication is associated with the application uplink transmission extension update.

[0157] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, an uplink transmission extension update is applied to the uplink transmission extension timer after the uplink transmission extension timer expires.

[0158] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, an uplink transmission extension update is applied to the uplink transmission extension timer before the uplink transmission extension timer expires.

[0159] In the sixth aspect, the indicator is associated with the TAG identification field, either alone or in combination with one or more of the first to fifth aspects.

[0160] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the first value of the TAG identifier field indicates that the closed-loop timing advance command message conveys a timing advance value and an uplink transmission extension indication, and the second value of the TAG identifier field indicates that the closed-loop timing advance command message conveys a timing advance value and does not convey an uplink transmission extension indication.

[0161] In the eighth aspect, the interpretation of the closed-loop timing advance command message is based on the configuration of the UE capabilities, either alone or in combination with one or more of the first to seventh aspects.

[0162] In the ninth aspect, either alone or in combination with one or more of the first to eighth aspects, the interpretation of the closed-loop timing advance command message is based on the configured logical channel identifier code point value associated with the closed-loop timing advance command message.

[0163] although Figure 8 An example box of process 800 is shown, but in some respects, process 800 may include... Figure 8 The boxes depicted may be fewer, different, or arranged differently compared to additional boxes. Alternatively, two or more boxes in the process 800 may be executed in parallel.

[0164] Figure 9 This is a diagram of an example device 900 for wireless communication according to the present disclosure. Device 900 may be a UE, or a UE may include device 900. In some aspects, device 900 includes a receiving component 902 and a transmitting component 904 that can communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, device 900 can use the receiving component 902 and the transmitting component 904 to communicate with another device 906 (such as a UE, a base station, or another wireless communication device). As further shown, device 900 may include a communication manager 140. Communication manager 140 may include a determining component 908, etc.

[0165] In some respects, device 900 can be configured to perform the functions described herein. Figure 6 One or more operations described herein. Additionally or alternatively, device 900 may be configured to perform one or more processes described herein, such as Figure 7 The process is 700. In some respects, Figure 9 The illustrated device 900 and / or one or more components may include a combination Figure 2 One or more components of the described UE. Additionally or alternatively, Figure 9 One or more components shown can be combined Figure 2 Implementation within one or more of the described components. Additionally or alternatively, one or more components in the set of components may be implemented at least partially as software stored in one or more memories. For example, a component (or a portion thereof) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the function or operation of the component.

[0166] Receiver 902 may receive communications from device 906, such as reference signals, control information, data communications, or combinations thereof. Receiver 902 may provide the received communications to one or more other components of device 900. In some aspects, receiver 902 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) and may provide the processed signals to one or more other components of device 900. In some aspects, receiver 902 may include combinations of... Figure 2 The described UE includes one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receiver processors, one or more controllers / processors, one or more memories, or combinations thereof.

[0167] Transmitting component 904 can transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 906. In some aspects, one or more other components of device 900 can generate communications and provide the generated communications to transmitting component 904 for transmission to device 906. In some aspects, transmitting component 904 can perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and can transmit the processed signals to device 906. In some aspects, transmitting component 904 may include combinations of... Figure 2 The described UE may include one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers / processors, one or more memories, or combinations thereof. In some aspects, the transmit component 904 may co-located with the receive component 902 in one or more transceivers.

[0168] Receiving component 902 can receive a closed-loop timing advance command message, which includes an indicator associated with the closed-loop timing advance command message, the indicator including at least one of a timing advance value or an uplink transmission extension indicator. Transmitting component 904 can transmit one or more communications on the uplink based on the interpretation of the closed-loop timing advance command message, the interpretation of which is based on the indicator. Determining component 908 can interpret the received closed-loop timing advance command message to determine whether the closed-loop timing advance command message conveys a timing advance command, an uplink transmission extension, or both. In other words, determining component 908 can interpret a first value in the closed-loop timing advance command message as indicating that the closed-loop timing command conveys an uplink transmission extension and a timing advance value, interpret a second value as indicating that the closed-loop timing command conveys an uplink transmission extension instead of a timing advance value, or interpret a third value as indicating that the closed-loop timing command conveys a timing advance value instead of an uplink transmission extension, and so on.

[0169] Figure 9 The number and arrangement of components shown are provided as an example. In reality, they can exist in... Figure 9 The components shown are compared to additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 9 The two or more components shown can be implemented within a single component, or Figure 9 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 9 The collection of (one or more) components shown is executable and described as being composed of Figure 9 The other set of components shown performs one or more functions.

[0170] Figure 10 This is an illustration of an example 1000 of a hardware implementation of a device 1005 employing a processing system 1010 according to the present disclosure. The device 1005 may be a UE or may be located at a UE (e.g., included in a UE).

[0171] Processing system 1010 can be implemented using a bus architecture represented overall by bus 1015. Bus 1015 may include any number of interconnect buses and bridges, depending on the specific application of processing system 1010 and overall design constraints. Bus 1015 links together various circuits including one or more processors and / or hardware components (represented by one or more processors 1020 (e.g., processors 1020a, 1020b, or 1020c), the illustrated components, and one or more computer-readable media / memory 1025 (e.g., computer-readable media / memory 1025a, 1025b, or 1025c)). Bus 1015 may also link various other circuits, such as timing sources, peripheral devices, voltage regulators, and / or power management circuits.

[0172] The processing system 1010 may be coupled to one or more transceivers 1030. The transceiver 1030 is coupled to one or more antennas 1035. The transceiver 1030 provides components for communicating with various other devices via a transmission medium. The transceiver 1030 receives signals from the one or more antennas 1035, extracts information from the received signals, and provides the extracted information to the processing system 1010 (specifically, the receiving component 902). Furthermore, the transceiver 1030 receives information from the processing system 1010 (specifically, the transmitting component 904) and generates signals to be applied to the one or more antennas 1035, at least in part, based on the received information.

[0173] Processing system 1010 includes one or more processors 1020 coupled to computer-readable medium / memory 1025. Processor 1020 is responsible for general processing, including executing software stored on computer-readable medium / memory 1025. When executed by processor 1020, the software causes processing system 1010 to perform the various functions described herein with respect to any particular device. Computer-readable medium / memory 1025 can also be used to store data manipulated by processor 1020 during software execution. Processing system also includes at least one of the illustrated components. These components may be software modules running in processor 1020, residing in / stored on computer-readable medium / memory 1025, one or more hardware modules coupled to processor 1020, or some combination thereof.

[0174] In some aspects, processing system 1010 may be a component of UE 120 and may include one or more memories (such as memory 282), and / or may include one or more processors (such as at least one of TX MIMO processor 266, RX processor 258, and / or controller / processor 280). In some aspects, apparatus 1005 for wireless communication includes: components for receiving a closed-loop timing advance command message, the closed-loop timing advance command message including an indicator associated with the closed-loop timing advance command message, the indicator including at least one of timing advance value or uplink transmission extension indication; and components for transmitting one or more communications on the uplink based on an interpretation of the closed-loop timing advance command message, the interpretation of the closed-loop timing advance command message being based on the indicator. The aforementioned components may be one or more of the aforementioned components of apparatus 900 and / or processing system 1010 of apparatus 1005 configured to perform the functions stated by the aforementioned components. As described elsewhere herein, processing system 1010 may include TX MIMO processor 266, RX processor 258, and / or controller / processor 280. In one configuration, the aforementioned components may be a TX MIMO processor 266, an RX processor 258, and / or a controller / processor 280 configured to perform the functions and / or operations set forth herein.

[0175] Figure 10 This is provided as an example. Other examples can be combined with it. Figure 10 The examples described are different.

[0176] Figure 11 This is a diagram illustrating an example 1100 of a specific implementation of code and circuitry for device 1105 according to the present disclosure. The circuitry may include processing circuitry and memory circuitry. Device 1105 may be a UE, or a UE may include device 1105.

[0177] like Figure 11 As shown, device 1105 may include circuitry for receiving a closed-loop timing advance command message, the closed-loop timing advance command message including an indicator associated with the closed-loop timing advance command message, the indicator including at least one of a timing advance value or an uplink transmission extension indication (circuit 1120). For example, circuit 1120 may enable device 1105 to receive a closed-loop timing advance command message, the closed-loop timing advance command message including an indicator associated with the closed-loop timing advance command message, the indicator including at least one of a timing advance value or an uplink transmission extension indication.

[0178] like Figure 11As shown, apparatus 1105 may include code stored in computer-readable medium 1025 for receiving a closed-loop timing advance command message, the closed-loop timing advance command message including an indicator associated with the closed-loop timing advance command message, the indicator including at least one of a timing advance value or an uplink transmission extension indication (code 1125). For example, when executed by processor 1020, code 1125 may cause processor 1020 to cause transceiver 1030 to receive the closed-loop timing advance command message, the closed-loop timing advance command message including an indicator associated with the closed-loop timing advance command message, the indicator including at least one of a timing advance value or an uplink transmission extension indication.

[0179] like Figure 11 As shown, device 1105 may include circuitry for transmitting one or more communications on the uplink based on an interpretation of a closed-loop timing advance command message, the interpretation of which is based on an indicator (circuit 1130). For example, circuit 1130 may enable device 1105 to transmit one or more communications on the uplink based on an interpretation of a closed-loop timing advance command message, the interpretation of which is based on an indicator.

[0180] like Figure 11 As shown, apparatus 1105 may include code stored in computer-readable medium 1025 for transmitting one or more communications on an uplink based on an interpretation of a closed-loop timing advance command message, the interpretation of which is based on an indicator (code 1135). For example, when executed by processor 1020, code 1135 may cause processor 1020 to cause transceiver 1030 to transmit one or more communications on an uplink based on an interpretation of the closed-loop timing advance command message, the interpretation of which is based on an indicator.

[0181] Figure 11 This is provided as an example. Other examples can be combined with it. Figure 11 The examples described are different.

[0182] Figure 12 This is a diagram of an example device 1200 for wireless communication according to the present disclosure. Device 1200 may be a network node, or a network node may include device 1200. In some aspects, device 1200 includes a receiving component 1202 and a transmitting component 1204 that can communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, device 1200 can use the receiving component 1202 and the transmitting component 1204 to communicate with another device 1206 (such as a UE, a base station, or another wireless communication device). As further shown, device 1200 may include a communication manager 150. Communication manager 150 may include a configuration component 1208, etc.

[0183] In some respects, device 1200 can be configured to perform the functions described herein. Figure 6 One or more operations described herein. Additionally or alternatively, the apparatus 1200 may be configured to perform one or more processes described herein, such as Figure 8 The process is 800. In some respects, Figure 12 The illustrated device 1200 and / or one or more components may include a combination Figure 2 One or more components of the described network node. Additionally or alternatively, Figure 12 One or more components shown can be combined Figure 2 Implementation within one or more of the described components. Additionally or alternatively, one or more components in the set of components may be implemented at least partially as software stored in one or more memories. For example, a component (or a portion thereof) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the function or operation of the component.

[0184] Receiver 1202 may receive communications from device 1206, such as reference signals, control information, data communications, or combinations thereof. Receiver 1202 may provide the received communications to one or more other components of device 1200. In some aspects, receiver 1202 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) and may provide the processed signals to one or more other components of device 1200. In some aspects, receiver 1202 may include combinations of... Figure 2 The described network node includes one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receiver processors, one or more controllers / processors, one or more memories, or combinations thereof.

[0185] Transmitting component 1204 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1206. In some aspects, one or more other components of device 1200 may generate communications and provide the generated communications to transmitting component 1204 for transmission to device 1206. In some aspects, transmitting component 1204 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to device 1206. In some aspects, transmitting component 1204 may include combinations of... Figure 2The described network node includes one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers / processors, one or more memories, or combinations thereof. In some aspects, the transmit component 1204 may co-located with the receive component 1202 in one or more transceivers.

[0186] Transmitting component 1204 can transmit a closed-loop timing advance command message, which includes an indicator associated with the closed-loop timing advance command message, the indicator including at least one of a timing advance value or an uplink transmission extension indicator. Receiving component 1202 can receive one or more communications on the uplink based on the interpretation of the closed-loop timing advance command message, the interpretation of which is based on the indicator. Configuration component 1208 can configure the values ​​in the closed-loop timing advance command message to convey an indication of whether the closed-loop timing advance command is used to signal a timing advance value, an uplink transmission extension, or both a timing advance value and an uplink transmission extension.

[0187] Figure 12 The number and arrangement of components shown are provided as an example. In reality, they can exist in... Figure 12 The components shown are compared to additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 12 The two or more components shown can be implemented within a single component, or Figure 12 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 12 The collection of (one or more) components shown is executable and described as being composed of Figure 12 The other set of components shown performs one or more functions.

[0188] Figure 13 This is an illustration of an example 1300 of a hardware implementation of a device 1305 employing a processing system 1310 according to the present disclosure. Device 1305 may be a network node or may be located at a network node (e.g., included in a network node).

[0189] Processing system 1310 may be implemented using a bus architecture represented overall by bus 1315. Bus 1315 may include any number of interconnect buses and bridges, depending on the specific application of processing system 1310 and overall design constraints. Bus 1315 links together various circuits including one or more processors and / or hardware components (represented by one or more processors 1320 (e.g., processors 1320a, 1320b, or 1320c), the illustrated components, and one or more computer-readable media / memories 1325 (e.g., computer-readable media / memories 1325a, 1325b, or 1325c)). Bus 1315 may also link various other circuits, such as timing sources, peripheral devices, voltage regulators, and / or power management circuitry.

[0190] Processing system 1310 may be coupled to one or more transceivers 1330. Transceiver 1330 is coupled to one or more antennas 1335. Transceiver 1330 provides components for communicating with various other devices via a transmission medium. Transceiver 1330 receives signals from one or more antennas 1335, extracts information from the received signals, and provides the extracted information to processing system 1310 (specifically, receiving component 1202). Furthermore, transceiver 1330 receives information from processing system 1310 (specifically, transmitting component 1204) and generates signals to be applied to one or more antennas 1335, at least in part, based on the received information.

[0191] Processing system 1310 includes one or more processors 1320 coupled to computer-readable medium / memory 1325. Processor 1320 is responsible for general processing, including executing software stored on computer-readable medium / memory 1325. When executed by processor 1320, the software causes processing system 1310 to perform the various functions described herein with respect to any particular device. Computer-readable medium / memory 1325 can also be used to store data manipulated by processor 1320 during software execution. Processing system also includes at least one of the illustrated components. These components may be software modules running in processor 1320, residing in / stored on computer-readable medium / memory 1325, one or more hardware modules coupled to processor 1320, or some combination thereof.

[0192] In some aspects, processing system 1310 may be a component of network node 110 and may include one or more memories (such as memory 242), and / or may include one or more processors (such as at least one of TX MIMO processor 216, RX processor 238, and / or controller / processor 240). In some aspects, apparatus 1305 for wireless communication includes: components for transmitting a closed-loop timing advance command message, the closed-loop timing advance command message including an indicator associated with the closed-loop timing advance command message, the indicator including at least one of timing advance value or uplink transmission extension indication; and components for receiving one or more communications on the uplink based on an interpretation of the closed-loop timing advance command message, the interpretation of the closed-loop timing advance command message being based on the indicator. The aforementioned components may be one or more of the aforementioned components of processing system 1310 of apparatus 1200 and / or apparatus 1305 configured to perform the functions stated by the aforementioned components. As described elsewhere herein, processing system 1310 may include TX MIMO processor 216, receiver processor 238, and / or controller / processor 240. In one configuration, the aforementioned components may be a TX MIMO processor 216, a receiver processor 238, and / or a controller / processor 240 configured to perform the functions and / or operations set forth herein.

[0193] Figure 13 This is provided as an example. Other examples can be combined with it. Figure 13 The examples described are different.

[0194] Figure 14 This is a diagram illustrating an example 1400 of a specific implementation of code and circuitry for device 1405 according to the present disclosure. The circuitry may include processing circuitry and memory circuitry. Device 1405 may be a network node, or a network node may include device 1405.

[0195] like Figure 14 As shown, device 1405 may include circuitry for transmitting a closed-loop timing advance command message, the closed-loop timing advance command message including an indicator associated with the closed-loop timing advance command message, the indicator including at least one of a timing advance value or an uplink transmission extension indication (circuit 1420). For example, circuit 1420 may enable device 1405 to transmit a closed-loop timing advance command message, the closed-loop timing advance command message including an indicator associated with the closed-loop timing advance command message, the indicator including at least one of a timing advance value or an uplink transmission extension indication.

[0196] like Figure 14As shown, apparatus 1405 may include code stored in computer-readable medium 1325 for transmitting a closed-loop timing advance command message, the closed-loop timing advance command message including an indicator associated with the closed-loop timing advance command message, the indicator including at least one of a timing advance value or an uplink transmission extension indication (code 1425). For example, when executed by processor 1320, code 1425 may cause processor 1320 to cause transceiver 1330 to transmit a closed-loop timing advance command message, the closed-loop timing advance command message including an indicator associated with the closed-loop timing advance command message, the indicator including at least one of a timing advance value or an uplink transmission extension indication.

[0197] like Figure 14 As shown, device 1405 may include circuitry for receiving one or more communications on the uplink based on an interpretation of a closed-loop timing advance command message, the interpretation of which is based on an indicator (circuit 1430). For example, circuit 1430 may enable device 1405 to receive one or more communications on the uplink based on an interpretation of a closed-loop timing advance command message, the interpretation of which is based on an indicator.

[0198] like Figure 14 As shown, apparatus 1405 may include code stored in computer-readable medium 1325 for receiving one or more communications on an uplink based on the interpretation of a closed-loop timing advance command message, the interpretation of which is based on an indicator (code 1435). For example, when executed by processor 1320, code 1435 may cause processor 1320 to cause transceiver 1330 to receive one or more communications on an uplink based on the interpretation of the closed-loop timing advance command message, the interpretation of which is based on an indicator.

[0199] Figure 14 This is provided as an example. Other examples can be combined with it. Figure 14 The examples described are different.

[0200] The following provides an overview of some aspects of this disclosure: Aspect 1: A method of wireless communication performed at a user equipment (UE), the method comprising: receiving a closed-loop timing advance command message, the closed-loop timing advance command message including an indicator associated with the closed-loop timing advance command message, the indicator including at least one of a timing advance value or an uplink transmission extension indication; and transmitting one or more communications on an uplink based on an interpretation of the closed-loop timing advance command message, the interpretation of the closed-loop timing advance command message being based on the indicator.

[0201] Aspect 2: According to the method of aspect 1, the closed-loop timing advance command message is a closed-loop timing advance command media access control (MAC) control element (CE).

[0202] Aspect 3: The method according to any one of Aspects 1 to 2, wherein the indicator is a code point that conveys a value mapped to at least one of the timing advance value or the uplink transmission extension indicator.

[0203] Aspect 4: The method according to any one of Aspects 1 to 3, wherein the uplink transmission extension indication is associated with the application uplink transmission extension update.

[0204] Aspect 5: According to the method of aspect 4, wherein after the uplink transmission extension timer expires, the uplink transmission extension update is applied to the uplink transmission extension timer.

[0205] Aspect 6: According to the method of aspect 4, wherein the uplink transmission extension update is applied to the uplink transmission extension timer before the expiration of the uplink transmission extension timer.

[0206] Aspect 7: The method according to any one of Aspects 1 to 6, wherein the indicator is associated with a timing advance group (TAG) identification field.

[0207] Aspect 8: According to the method of aspect 7, wherein the first value of the TAG identifier field indicates that the closed-loop timing advance command message conveys the timing advance value and the uplink transmission extension indication, and wherein the second value of the TAG identifier field indicates that the closed-loop timing advance command message conveys the timing advance value and does not convey the uplink transmission extension indication.

[0208] Aspect 9: The method according to any one of Aspects 1 to 8, wherein the interpretation of the closed-loop timing advance command message is based on the configuration of the UE capabilities.

[0209] Aspect 10: The method according to any one of Aspects 1 to 9, wherein the interpretation of the closed-loop timing advance command message is based on the logical channel identifier code point value configured in association with the closed-loop timing advance command message.

[0210] Aspect 11: A method of wireless communication performed by a network node, the method comprising: transmitting a closed-loop timing advance command message, the closed-loop timing advance command message including an indicator associated with the closed-loop timing advance command message, the indicator including at least one of a timing advance value or an uplink transmission extension indicator; and receiving one or more communications on an uplink based on an interpretation of the closed-loop timing advance command message, the interpretation of the closed-loop timing advance command message being based on the indicator.

[0211] Aspect 12: According to the method of aspect 11, the closed-loop timing advance command message is a closed-loop timing advance command media access control (MAC) control element (CE).

[0212] Aspect 13: The method according to any one of Aspects 11 to 12, wherein the indicator is a code point that conveys a value mapped to at least one of the timing advance value or the uplink transmission extension indicator.

[0213] Aspect 14: The method according to any one of Aspects 11 to 13, wherein the uplink transmission extension indication is associated with the application uplink transmission extension update.

[0214] Aspect 15: According to the method of aspect 14, wherein after the uplink transmission extension timer expires, the uplink transmission extension update is applied to the uplink transmission extension timer.

[0215] Aspect 16: The method according to aspect 14, wherein the uplink transmission extension update is applied to the uplink transmission extension timer before the uplink transmission extension timer expires.

[0216] Aspect 17: The method according to any one of Aspects 11 to 16, wherein the indicator is associated with a timing advance group (TAG) identification field.

[0217] Aspect 18: According to the method of aspect 17, wherein the first value of the TAG identifier field indicates that the closed-loop timing advance command message conveys the timing advance value and the uplink transmission extension indication, and wherein the second value of the TAG identifier field indicates that the closed-loop timing advance command message conveys the timing advance value and does not convey the uplink transmission extension indication.

[0218] Aspect 19: The method according to any one of Aspects 11 to 18, wherein the interpretation of the closed-loop timing advance command message is based on the configuration of UE capabilities.

[0219] Aspect 20: The method according to any one of Aspects 11 to 19, wherein the interpretation of the closed-loop timing advance command message is based on the logical channel identifier code point value configured in association with the closed-loop timing advance command message.

[0220] Aspect 21: An apparatus for wireless communication at a device, the apparatus comprising: one or more processors; one or more memories coupled to the one or more processors; and instructions stored in the one or more memories and executable by the one or more processors to cause the apparatus to perform the method according to one or more of aspects 1 to 20.

[0221] Aspect 22: An apparatus for wireless communication at a device, the apparatus comprising: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors being configured to cause the device to perform the method according to one or more of aspects 1 to 20.

[0222] Aspect 23: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 1 to 20.

[0223] Aspect 24: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by one or more processors to perform the methods described in one or more of aspects 1 to 20.

[0224] Aspect 25: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method according to one or more of aspects 1 to 20.

[0225] Aspect 26: A device for wireless communication, the device including a processing system comprising one or more processors and one or more memories coupled to the one or more processors, the processing system being configured to cause the device to perform the method according to one or more of aspects 1 to 20.

[0226] Aspect 27: An apparatus for wireless communication at a device, the apparatus comprising one or more memories and one or more processors coupled to the one or more memories, the one or more processors being individually or collectively configured to cause the device to perform the method according to one or more of aspects 1 to 20.

[0227] Aspect 28: An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors being configured to cause the UE to: receive a closed-loop timing advance command message, the closed-loop timing advance command message including an indicator associated with the closed-loop timing advance command message, the indicator including at least one of a timing advance value or an uplink transmission extension indication; and transmit one or more communications on an uplink based on an interpretation of the closed-loop timing advance command message, the interpretation of the closed-loop timing advance command message being based on the indicator.

[0228] Aspect 29: The apparatus according to aspect 28, wherein the one or more processors are individually or jointly configured to cause the UE to: receive the closed-loop timing advance command message, the closed-loop timing advance command message including the indicator associated with the closed-loop timing advance command message, the indicator including at least one of the timing advance value or the uplink transmission extension indication; and transmit one or more communications on the uplink based on the interpretation of the closed-loop timing advance command message, the interpretation of the closed-loop timing advance command message being based on the indicator.

[0229] Aspect 30: An apparatus for wireless communication at a network node, the apparatus comprising: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors being configured to cause the network node to: transmit a closed-loop timing advance command message, the closed-loop timing advance command message including an indicator associated with the closed-loop timing advance command message, the indicator including at least one of a timing advance value or an uplink transmission extension indication; and receive one or more communications on an uplink based on an interpretation of the closed-loop timing advance command message, the interpretation of the closed-loop timing advance command message being based on the indicator.

[0230] Aspect 31: The apparatus according to aspect 30, wherein the one or more processors are individually or jointly configured to cause the network node to: send the closed-loop timing advance command message, the closed-loop timing advance command message including the indicator associated with the closed-loop timing advance command message, the indicator including at least one of the timing advance value or the uplink transmission extension indication; and receive one or more communications on the uplink based on an interpretation of the closed-loop timing advance command message, the interpretation of the closed-loop timing advance command message being based on the indicator.

[0231] A user equipment (UE) includes: a processing system including processor circuitry and memory circuitry storing code and coupled to the processor circuitry, the processing system being configured to cause the UE to: receive a closed-loop timing advance command message, the closed-loop timing advance command message including an indicator associated with the closed-loop timing advance command message, the indicator including at least one of a timing advance value or an uplink transmission extension indicator; and transmit one or more communications on an uplink based on an interpretation of the closed-loop timing advance command message, the interpretation of the closed-loop timing advance command message being based on the indicator.

[0232] A network node includes: a processing system including processor circuitry and memory circuitry storing code and coupled to the processor circuitry, the processing system being configured to cause the network node to: send a closed-loop timing advance command message, the closed-loop timing advance command message including an indicator associated with the closed-loop timing advance command message, the indicator including at least one of a timing advance value or an uplink transmission extension indicator; and receive one or more communications on an uplink based on an interpretation of the closed-loop timing advance command message, the interpretation of the closed-loop timing advance command message being based on the indicator.

[0233] While the foregoing disclosure provides examples and descriptions, it is not intended to be exhaustive or to limit the aspects to the precise form disclosed. Modifications and variations may be made based on the foregoing disclosure, or from various forms of practice.

[0234] As used herein, the term "component" is intended to be broadly interpreted as hardware or a combination of hardware and at least one of software or firmware. "Software" should be broadly interpreted as instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable programs, threads of execution, procedures, or functions, whether referred to as software, firmware, middleware, microcode, hardware description languages, or other terms. As used herein, a "processor" is implemented in hardware or a combination of hardware and software. It will be apparent that the systems or methods described herein may be implemented in various forms of hardware or combinations of hardware and software. The actual dedicated control hardware or software code used to implement these systems or methods is not limited in any way. Therefore, the operation and behavior of these systems or methods are described herein without reference to any specific software code, as those skilled in the art will understand that the software and hardware can be designed to implement these systems or methods, at least in part, based on the description herein. Unless otherwise stated, a component configured to perform a function means that the component has the capability to perform that function, but it is not necessary for the component to actually perform that function.

[0235] As used in this article, depending on the context, "meeting the threshold" can mean a value greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, etc.

[0236] As used in this article, the phrase “at least one of” in a list of items refers to any combination of these items, including a single member. As an example, “at least one of the following: a, b, or c” is intended to cover a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination with multiple of the same element (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c, and c+c+c, or any other ordering of a, b, and c).

[0237] No element, action, or instruction used herein should be construed as essential or necessary unless explicitly stated otherwise. Furthermore, as used herein, the articles “a” and “an” are intended to include one or more items and are used interchangeably with “one or more.” Similarly, as used herein, the article “the” is intended to include one or more items mentioned in connection with the article “the” and is used interchangeably with “one or more.” Furthermore, as used herein, the terms “set” and “group” are intended to include one or more items and are used interchangeably with “one or more.” If only one item is desired, the phrase “only one” or similar terminology will be used. Moreover, as used herein, the terms “having” and similar terms are intended as open-ended terms that do not limit the elements they modify (e.g., “having” A may also have B). Additionally, the phrase “based on” is intended to mean “based on or otherwise related to” unless otherwise explicitly stated. Furthermore, as used herein, the term “or” is intended to be inclusive when used consecutively and is interchangeable with “and / or” unless otherwise explicitly stated (e.g., if used in conjunction with “either of the two” or “only one of them”). It should be understood that “one or more” is equivalent to “at least one”.

[0238] Although specific combinations of features are set forth in the claims or disclosed in the description, these combinations are not intended to limit the disclosure of various aspects. Many of these features may be combined in ways not specifically stated in the claims or disclosed in the description. The disclosure of various aspects includes each dependent claim in combination with each other claim in the claim set.

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: One or more memory units; and One or more processors, said one or more processors being coupled to said one or more memories and configured to cause the UE to: Receive a closed-loop timing advance command message, the closed-loop timing advance command message including an indicator associated with the closed-loop timing advance command message, wherein the indicator includes at least one of a timing advance value or an uplink transmission extension indicator; as well as One or more communications are sent on the uplink based on the interpretation of the closed-loop timing advance command message, the interpretation of the closed-loop timing advance command message being based on the indicator.

2. The apparatus according to claim 1, wherein the closed-loop timing advance command message is a closed-loop timing advance command media access control (MAC) control element (CE).

3. The apparatus of claim 1, wherein the indicator is a code point that conveys a value mapped to at least one of the timing advance value or the uplink transmission extension indicator.

4. The apparatus of claim 1, wherein the uplink transmission extension indication is associated with the application of the uplink transmission extension update.

5. The apparatus of claim 4, wherein after the uplink transmit extension timer expires, the uplink transmit extension update is applied to the uplink transmit extension timer.

6. The apparatus of claim 4, wherein the uplink transmission extension update is applied to the uplink transmission extension timer before the uplink transmission extension timer expires.

7. The apparatus of claim 1, wherein the indicator is associated with a timing advance group (TAG) identifier field.

8. The apparatus of claim 7, wherein the first value of the TAG identifier field indicates that the closed-loop timing advance command message conveys the timing advance value and the uplink transmission extension indication, and The second value of the TAG identifier field indicates that the closed-loop timing advance command message conveys the timing advance value and does not convey the uplink transmission extension indication.

9. The apparatus of claim 1, wherein the interpretation of the closed-loop timing advance command message is based on the configuration of UE capabilities.

10. The apparatus of claim 1, wherein the interpretation of the closed-loop timing advance command message is based on a configured logical channel identifier code point value associated with the closed-loop timing advance command message.

11. An apparatus for wireless communication at a network node, the apparatus comprising: One or more memory units; and One or more processors, said one or more processors coupled to said one or more memories and configured to cause the network node to: Send a closed-loop timing advance command message, the closed-loop timing advance command message including an indicator associated with the closed-loop timing advance command message, wherein the indicator includes at least one of a timing advance value or an uplink transmission extension indicator; as well as One or more communications are received on the uplink based on the interpretation of the closed-loop timing advance command message, the interpretation of the closed-loop timing advance command message being based on the indicator.

12. The apparatus of claim 11, wherein the closed-loop timing advance command message is a closed-loop timing advance command media access control (MAC) control element (CE).

13. The apparatus of claim 11, wherein the indicator is a code point that conveys a value mapped to at least one of the timing advance value or the uplink transmission extension indicator.

14. The apparatus of claim 11, wherein the uplink transmission extension indication is associated with the application of the uplink transmission extension update.

15. The apparatus of claim 14, wherein the uplink transmission extension update is applied to the uplink transmission extension timer after the uplink transmission extension timer expires.

16. The apparatus of claim 14, wherein the uplink transmission extension update is applied to the uplink transmission extension timer before the uplink transmission extension timer expires.

17. The apparatus of claim 11, wherein the indicator is associated with a timing advance group (TAG) identifier field.

18. The apparatus of claim 17, wherein the first value of the TAG identifier field indicates that the closed-loop timing advance command message conveys the timing advance value and the uplink transmission extension indication, and The second value of the TAG identifier field indicates that the closed-loop timing advance command message conveys the timing advance value and does not convey the uplink transmission extension indication.

19. The apparatus of claim 11, wherein the interpretation of the closed-loop timing advance command message is based on the configuration of UE capabilities.

20. A method for wireless communication performed at a user equipment (UE), the method comprising: Receive a closed-loop timing advance command message, the closed-loop timing advance command message including an indicator associated with the closed-loop timing advance command message, the indicator including at least one of a timing advance value or an uplink transmission extension indicator; as well as One or more communications are sent on the uplink based on the interpretation of the closed-loop timing advance command message, the interpretation of the closed-loop timing advance command message being based on the indicator.