Timing advance management in wireless systems
Through the timed advance information request and configuration mechanism between the terminal device and the network node, the problem of inflexible timing adjustment in the prior art is solved, dynamic management of multiple TA values is realized, and communication efficiency and quality are improved.
Patent Information
- Application Number
- CN202280095223.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2022-04-29
- Publication Date
- 2024-12-03
AI Technical Summary
The lack of effective timing advance management mechanism in existing wireless communication systems, resulting in inflexible timing adjustment and inability to meet the needs of multi-TA value configuration, affecting communication efficiency and quality.
The terminal device requests the network nodes to advance adjustment information in timing and the network node configures and receives these requests based on conditions to realize dynamic management and adjustment of multiple TA values.
It improves the flexibility and efficiency of the timing adjustment of the communication system, and can dynamically configure multiple TA values according to different conditions, enhancing communication quality and reliability.
Smart Images

Figure CN119072997A_ABST
Abstract
Description
Technical Field
[0001] The exemplary and non-limiting exemplary embodiments relate generally to communications, and more particularly to timing advance management in wireless systems. Background Art
[0002] It is known to facilitate timing mechanisms in communication networks. Summary of the invention
[0003] According to one aspect, a method comprises: applying, by a terminal device, timing advance adjustment information on a cell of a network node; and indicating, by the terminal device to the network node, a request for further timing advance adjustment information to be maintained on the cell.
[0004] According to one aspect, a method includes: sending configuration information from a network node to a terminal device, the configuration information including: one or more conditions for triggering a request for another timing advance adjustment information to be maintained on a cell of the network node; and receiving, by the network node, a request for another timing advance adjustment information to be maintained by the terminal device from the terminal device based on the one or more conditions.
[0005] According to one aspect, an apparatus comprises: means for applying, by a terminal device, timing advance adjustment information about a cell of a network node; and means for indicating, by the terminal device to the network node, a request for further timing advance adjustment information to be maintained on the cell.
[0006] According to one aspect, an apparatus includes: a component for sending configuration information from a network node to a terminal device, the configuration information including: one or more conditions for triggering a request for another timing advance adjustment information to be maintained on a cell of the network node; and a component for receiving, by the network node, a request for another timing advance adjustment information to be maintained by the terminal device from the terminal device based on the one or more conditions.
[0007] According to one aspect, a machine-readable, non-transitory program storage device is provided, the device tangibly embodying a program of instructions executable by the machine for performing operations, the operations comprising: applying, by a terminal device, timing advance adjustment information about a cell of a network node; and indicating, by the terminal device to the network node, a request for another timing advance adjustment information to be maintained on the cell.
[0008] According to one aspect, a machine-readable, non-volatile program storage device is provided, which tangibly embodies a program of instructions executable by the machine for performing operations, the operations comprising: sending configuration information from a network node to a terminal device, the configuration information comprising: one or more conditions for triggering a request for another timing advance adjustment information to be maintained on a cell of the network node; and receiving, by the network node, a request for another timing advance adjustment information to be maintained by the terminal device from the terminal device based on the one or more conditions.
[0009] According to one aspect, an apparatus comprises: at least one processor; and at least one memory comprising computer program code; wherein the at least one memory and the computer program code are configured to, together with the at least one processor, cause the apparatus to at least: apply timing advance adjustment information about a cell of a network node by a terminal device; and indicate, by the terminal device to the network node, a request for another timing advance adjustment information to be maintained on the cell.
[0010] According to one aspect, an apparatus comprises: at least one processor; and at least one memory comprising computer program code; wherein the at least one memory and the computer program code are configured to, together with the at least one processor, enable the apparatus to at least: send configuration information from a network node to a terminal device, the configuration information comprising: one or more conditions for triggering a request for another timing advance adjustment information to be maintained on a cell of the network node; and receive, by the network node, a request for another timing advance adjustment information to be maintained by the terminal device from the terminal device based on the one or more conditions. BRIEF DESCRIPTION OF THE DRAWINGS
[0011] The above-described aspects and other features are explained in the following description taken in conjunction with the accompanying drawings.
[0012] Figure 1 is a block diagram of one possible non-limiting system in which example embodiments may be practiced.
[0013] Figure 2 An example timing advance command MAC CE is shown.
[0014] Figure 3 An example absolute timing advance command MAC CE is shown.
[0015] Figure 4 An example of inter-cell mTRP communication is shown.
[0016] Figure 5 is an example apparatus configured to implement the examples described herein.
[0017] Figure 6is an example method performed with a user device to implement the examples described herein.
[0018] Figure 7 is an example method performed with a network node to implement the examples described herein. DETAILED DESCRIPTION
[0019] Steering Figure 1 , which shows a block diagram of one possible non-limiting example in which the example may be practiced. A user equipment (UE) 110, a radio access network (RAN) node 170, and (multiple) network elements 190 are shown. Figure 1 In the example of FIG. 1 , a user equipment (UE) 110 wirelessly communicates with a wireless network 100. A UE is a wireless device that can access the wireless network 100. The UE 110 includes one or more processors 120, one or more memories 125, and one or more transceivers 130 interconnected by one or more buses 127. Each transceiver 130 in the one or more transceivers 130 includes a receiver Rx 132 and a transmitter Tx 133. The one or more buses 127 may be address, data, or control buses, and may include any interconnection mechanism, such as a series of lines on a motherboard or integrated circuit, optical fiber, or other optical communication devices. The one or more transceivers 130 are connected to one or more antennas 128. The one or more memories 125 include computer program code 123. The UE 110 includes a module 140, which includes one or both of the parts 140-1 and / or 140-2, which can be implemented in a variety of ways. The module 140 can be implemented in hardware as the module 140-1, such as being implemented as part of the one or more processors 120. Module 140-1 may also be implemented as an integrated circuit or by other hardware such as a programmable gate array. In another example, module 140 may be implemented as module 140-2, which is implemented as computer program code 123 and executed by one or more processors 120. For example, one or more memories 125 and computer program code 123 may be configured to, together with one or more processors 120, enable user equipment 110 to perform one or more of the operations described herein. UE 110 communicates with RAN node 170 via wireless link 111.
[0020] In this example, the RAN node 170 is a base station that provides access to the wireless network 100 for wireless devices such as UE 110. The RAN node 170 may be, for example, a base station for 5G, also known as New Radio (NR). In 5G, the RAN node 170 may be a NG-RAN node, which is defined as a gNB or ng-eNB. A gNB is a node that provides NR user plane and control plane protocol termination towards the UE and is connected to a 5GC (such as, for example, (multiple) network elements 190) via an NG interface (such as connection 131). An ng-eNB is a node that provides E-UTRA user plane and control plane protocol termination towards the UE and is connected to a 5GC via an NG interface (such as connection 131). The NG-RAN node may include multiple gNBs, which may also include a central unit (CU) (gNB-CU) 196 and (multiple) distributed units (DU) (gNB-DU), of which DU 195 is shown. Note that the DU 195 may include or be coupled to and control a radio unit (RU). The gNB-CU 196 is a logical node that hosts the RRC, SDAP, and PDCP protocols of a gNB, or the radio resource control (RRC) and PDCP protocols of an en-gNB that controls the operation of one or more gNB-DUs. The gNB-CU 196 terminates the F1 interface connected to the gNB-DU 195. The F1 interface is illustrated as reference numeral 198, although reference numeral 198 also illustrates a link between a remote element of the RAN node 170 and a centralized element of the RAN node 170, such as a link between the gNB-CU 196 and the gNB-DU 195. The gNB-DU 195 is a logical node that hosts the RLC, MAC, and PHY layers of a gNB or en-gNB, and its operation is controlled in part by the gNB-CU 196. One gNB-CU 196 supports one or more cells. One cell can be supported by one gNB-DU 195, or one cell can be supported / shared with multiple DUs under RAN sharing. The gNB-DU 195 terminates the F1 interface 198 connected to the gNB-CU 196. Note that the DU 195 is considered to include the transceiver 160, for example, as part of the RU, but some examples in this regard may have the transceiver 160 as part of a separate RU, for example, under the control of the DU 195 and connected to the DU 195. The RAN node 170 may also be an eNB (evolved NodeB) base station for LTE (Long Term Evolution), or any other suitable base station or node.
[0021] The RAN node 170 includes one or more processors 152, one or more memories 155, one or more network interfaces ((multiple) N / WI / F) 161, and one or more transceivers 160 interconnected by one or more buses 157. Each of the one or more transceivers 160 includes a receiver Rx 162 and a transmitter Tx 163. The one or more transceivers 160 are connected to one or more antennas 158. The one or more memories 155 include computer program code 153. The CU 196 may include (multiple) processors 152, (multiple) memories 155, and a network interface 161. Note that the DU 195 may also include its own memory / memory, and (multiple) processors, and / or other hardware, but these are not shown.
[0022] The RAN node 170 includes a module 150, which includes one or both of the parts 150-1 and / or 150-2, which can be implemented in a variety of ways. The module 150 can be implemented in hardware as the module 150-1, such as being implemented as part of one or more processors 152. The module 150-1 can also be implemented as an integrated circuit or by other hardware such as a programmable gate array. In another example, the module 150 can be implemented as a module 150-2, which is implemented as a computer program code 153 and executed by one or more processors 152. For example, one or more memories 155 and the computer program code 153 are configured to, together with the one or more processors 152, enable the RAN node 170 to perform one or more operations in the operations described herein. Note that the functionality of the module 150 can be distributed, such as being distributed between the DU 195 and the CU 196, or implemented separately in the DU 195.
[0023] One or more network interfaces 161 communicate over a network, such as via links 176 and 131. Two or more gNBs 170 may communicate using, for example, link 176. Link 176 may be wired or wireless or both, and may implement, for example, an Xn interface for 5G, an X2 interface for LTE, or other suitable interfaces for other standards.
[0024] The one or more buses 157 may be address, data, or control buses, and may include any interconnection mechanism, such as a series of wires on a motherboard or integrated circuit, optical fiber, or other optical communication device, wireless channel, etc. For example, the one or more transceivers 160 may be implemented as a remote radio head (RRH) 195 for LTE, or a distributed unit (DU) 195 for a gNB implementation for 5G, where other elements of the RAN node 170 may be physically located at a different location from the RRH / DU 195, and the one or more buses 157 may be implemented in part, for example, as fiber optic cables, or other suitable network connections for connecting other elements of the RAN node 170 (e.g., central unit (CU), gNB-CU 196) to the RRH / DU 195. Reference numeral 198 also indicates these suitable network link(s).
[0025] Relay nodes in NR are called integrated access and backhaul nodes. The mobile terminal part of the IAB node facilitates the backhaul (also called parent link) connection. In other words, it is the function that carries the UE functionality. The distributed unit part of the IAB node facilitates the so-called access link (also called child link) connection (i.e., for the access link UE, and in the case of multi-hop IAB, for the backhaul of other IAB nodes). In other words, it is responsible for certain base station functions. The IAB scenario can follow a so-called split architecture, where the central unit hosts the high-level protocols for the UE and terminates the control plane and user plane interfaces with the 5G core network.
[0026] Note that the description herein indicates that a "cell" performs a function, but it should be clear that the device that forms the cell can perform the function. A cell constitutes part of a base station. That is, each base station can have multiple cells. For example, a single carrier frequency and associated bandwidth can have three cells, each covering one-third of a 360-degree area, so the coverage area of a single base station covers an approximate ellipse or circle. In addition, each cell can correspond to a single carrier, and a base station can use multiple carriers. So if each carrier has 3 120-degree cells and there are 2 carriers, the base station has a total of 6 cells.
[0027] The wireless network 100 may include one or more network elements 190, which may include core network functions and provide connectivity to other networks such as telephone networks and / or data communication networks (e.g., the Internet) via one or more links 181. Such core network functions for 5G may include: location management functions ((multiple) LMFs), and / or (multiple) access and mobility management functions (AMFs), and / or user plane functions (UPFs), and / or (multiple) session management functions (SMFs). Such core network functions for LTE may include MME (mobility management entity) / SGW (serving gateway) functions. Such core network functions may include SON (self-organizing / optimizing network) functions. These are merely illustrative functions that may be supported by (multiple) network elements 190, and it is noted that both 5G and LTE functions may be supported. The RAN node 170 is coupled to the network element 190 via a link 131. The link 131 may be implemented as, for example, an NG interface for 5G, or an S1 interface for LTE, or other suitable interfaces for other standards. Network element 190 includes one or more processors 175, one or more memories 171, and one or more network interfaces (N / WI / F) 180 interconnected by one or more buses 185. One or more memories 171 include computer program code 173.
[0028] The wireless network 100 can implement network virtualization, which is a process of combining hardware and software network resources and network functions into a single software-based management entity or virtual network. Network virtualization involves platform virtualization, which is usually used in conjunction with resource virtualization. Network virtualization is divided into external network virtualization, which combines many networks or network parts into virtual units, or internal network virtualization, which provides network-like functions for software containers on a single system. Note that the virtualized entities generated by network virtualization are still implemented to some extent using hardware such as processors 152 or 175, and memories 155 and 171, and such virtualized entities also produce technical effects.
[0029] Computer readable memories 125, 155, and 171 may be of any type suitable for the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor-based memory devices, flash memory, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. Computer readable memories 125, 155, and 171 may be components for performing storage functions. Processors 120, 152, and 175 may be of any type suitable for the local technical environment and may include, as non-limiting examples, one or more of a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. Processors 120, 152, and 175 may be components for performing functions such as control of UE 110, RAN node 170, (multiple) network elements 190, and other functions described herein.
[0030] In general, various example embodiments of user device 110 may include, but are not limited to, a cellular telephone with wireless communication capabilities (such as a smart phone, a tablet computer, a personal digital assistant (PDA)), a portable computer with wireless communication capabilities, an image capture device with wireless communication capabilities (such as a digital camera), a gaming device with wireless communication capabilities, a music storage and playback device with wireless communication capabilities, an Internet device allowing wireless Internet access and browsing, a tablet computer with wireless communication capabilities, a head-mounted display (such as a display implementing virtual / augmented / mixed reality), and a portable unit or terminal incorporating a combination of such functionality.
[0031] UE 110, RAN node 170, and / or network element(s) 190 (and associated memory, computer program code, and modules) may be configured to implement (e.g., in part) the methods described herein, including timing advance management in a wireless system. Figure 1 The computer program code 123, module 140-1, module 140-2, and other elements / features of the UE 110 shown may implement the user equipment related aspects of the methods described herein. Similarly, Figure 1 The computer program code 153, module 150-1, module 150-2, and other elements / features of the RAN node 170 shown in the figure may implement the gNB / TRP-related aspects of the methods described herein. Figure 1 The computer program code 173 and other elements / features of the network element(s) 190 shown in may be configured to implement the network element related aspects of the methods described herein.
[0032] Therefore, having introduced a suitable but non-limiting technical context for the practice of the example embodiments, the example embodiments are now described in more detail.
[0033] The examples described herein relate to feMIMO evolution work items in RAN1. More specifically, the examples described herein relate to multi-TA maintenance / operation.
[0034] RAN1 includes several work items (1-7 following, with a focus on item 7) related to the examples described in this article.
[0035] 1. Study and, where justified, specify CSI reporting enhancements for high / medium UE speeds by leveraging time domain correlation / Doppler domain information to assist DL precoding, for FR1, as follows: a) Rel-16 / 17 Type II codebook refinement without modifying the spatial and frequency domain basis, and b) UE reporting of time domain channel properties measured via CSI-RS for tracking.
[0036] 2. Use the Rel-17 unified TCI framework and specify extensions to the Rel-17 unified TCI framework to indicate multiple DL and ULTCI states, focusing on multi-TRP use cases.
[0037] 3. Study and, where justified, specify a higher number of orthogonal DMRS ports for downlink and uplink MU-MIMO (without increasing DM-RS overhead), for CP-OFDM only, a) striving for common design between DL and UL DMRS, and b) up to 24 orthogonal DMRS ports, where the maximum number of orthogonal ports for single-symbol DMRS and dual-symbol DMRS is doubled for each applicable DMRS type.
[0038] 4. Study and, where reasonable, specify enhancements to CSI acquisition for coherent JT for FR1 and up to 4 TRPs, assuming ideal backhaul and synchronization, and the same number of antenna ports on the TRPs, as follows: a) Rel-16 / 17 Type II codebook refinement for CJT mTRPs and their associated CSI reports for FDD, taking into account throughput-overhead trade-offs; b) SRS enhancement for managing inter-TRP cross-SRS interference for TDD CJT via SRS capacity enhancement and / or interference randomization, with the constraints that 1) no additional SRS resources are consumed, 2) existing SRS comb structure is reused, and 3) no new SRS root sequences are used; and c) note that the maximum number of CSI-RS ports per resource remains the same as in Rel-17, i.e., 32.
[0039] 5. Study and, where justified, specify UL DMRS, SRS, SRI and TPMI (including codebook) enhancements to enable 8Tx UL operation to support 4 or more layers per UE in the UL for CPE / FWA / vehicle / industrial equipment. Potential limitations to this target range (including coherence assumptions, full power / non-full power modes) will be identified as part of the study.
[0040] 6. Study and, if necessary, specify the following items to facilitate simultaneous multi-panel UL transmissions to improve UL throughput / reliability, with a focus on FR2 and multi-TRP, assuming up to 2 TRPs and up to 2 panels, for CPE / FWA / vehicles / industrial equipment (as applicable): a) UL precoding indication for PUSCH, where no new codebook is introduced for multi-panel simultaneous transmission. Considering multi-TRP operation based on single DCI and multi-DCI, the total number of layers on all panels is up to four, and the total number of codewords is up to two; b) UL beam indication for PUCCH / PUSCH, where assuming the unified TCI framework extension in Objective 2, considering multi-TRP operation based on single DCI and multi-DCI. For the case of multi-TRP operation based on multi-DCI, only PUSCH+PUSCH, or PUCCH+PUCCH are transmitted on two panels in the same CC.
[0041] 7. Study and, where justified, specify: a) two TAs for UL multi-DCI for multi-TRP operation, and b) power control for UL single DCI for multi-TRP operation assuming the unified TCI framework extension in Goal 2. For the case of simultaneous UL transmissions from multiple panels, operation is limited to Goal 6 scenarios only.
[0042] Timing Advance Command MAC CE
[0043] refer to Figure 2 , the timing advance command MAC CE 200 is identified by a MAC subheader with a logical channel ID (LCID), as specified in 3GPP TS 38.321 V17.0.0 (2022-03). The timing advance command MAC CE 200 has a fixed size and comprises a single octet 202 defined as follows ( Figure 6 .1.3.4-1: Timing Advance Command MAC CE, such as Figure 2 204. The TAG ID field 204 indicates the TAG identity of the addressed TAG. The TAG containing the SpCell has a TAG identity of 0. The length of the field is 2 bits; b) Timing Advance Command 206. The Timing Advance Command field 206 indicates the index value T used to control the timing adjustment amount that the MAC entity must apply. A(0, 1, 2, ... 63) (as specified in TS 38.213). The length of the timing advance command field 206 is 6 bits. Figure 2 As shown in , the bit partitioning is indicated as item 208.
[0044] Absolute timing advance command MAC CE
[0045] refer to Figure 3 , the absolute timing advance command MAC CE 300 is identified by a MAC subheader with an eLCID as specified in 3GPP TS 38.321 V17.0.0 (2022-03) b. The absolute timing advance command MAC CE 300 has a fixed size and includes two octets (302, 304) as defined below (the absolute timing advance command MAC CE, as Figure 3 As shown in the figure): a) Timing Advance Command 306. The Timing Advance Command field 306 indicates the index value TA used to control the timing adjustment amount that the MAC entity must apply in TS 38.213. The size of the Timing Advance Command field 306 is 12 bits; b) R 308: Reserved bit, set to "0". As shown in the figure Figure 3 As shown in , the bit partitioning is indicated as item 310.
[0046] The unified TCI framework in R17 is as follows. On the unified TCI framework, the following aspects have been clarified and / or agreed upon so far in RAN1 (including for RAN node 170): a) a common TCI state (also called indicated TCI) used for a group of signals and channels at a time, b) a TCI state can be a joint DL / UL, a separate DL TCI state, and a separate UL TCI state, c) RRC configures a group (or pool) of joint and / or separate TCI states; d) MAC activates multiple (for example, 8) joint and / or separate TCI states. Before the first indication, the first activated TCI state is the current indicated TCI state, e) DCI indicates that one of the activated TCI states is an indicated TCI state (which can be a common TCI state).
[0047] Regarding the TCI status indication based on DCI, the following consensus has been reached so far. DCI format 1_1 / 1_2 with and without DL allocation is used to carry the TCI status indication. The indication is confirmed by the UE through HARQ ACK. The application time of the beam indication is the first time slot of at least X milliseconds or Y symbols after the last symbol of the confirmation of the joint or individual DL / UL beam indication. The TCI field code point can be joint or individual. The joint TCI field code point can include TCI states for both DL and UL. The individual TCI field code point includes a pair of DL TCI states and UL TCI states, one DL TCI state (maintaining the current UL TCI state), and one UL TCI state (maintaining the current DL TCI state).
[0048] Currently, the UE can acquire timing advance during the random access procedure (e.g., when it does not have a TA). For example, in a CBRA (contention-based random access) procedure, the UE sends a random access preamble, and in the random access response, the network provides the UE with an absolute timing advance command (TAC). In order to continuously adjust the timing advance, the network can periodically update the UE's timing advance by sending a TAC, which in turn restarts / starts the time alignment timer.
[0049] Currently, it is not supported to have multiple TA values per serving cell (in one serving cell, or in inter-cell beam management, or in multiple TRP communications). In inter-cell communications (inter-cell beam management, or inter-cell multiple TRP communications), refer to Figure 4 , UE 110 may be configured to communicate with serving cell 402 and one or more cells 404 having a PCI (PCI=2) different from serving cell 402 (PCI=1). Cell 404 having a PCI (PCI=2) different from serving cell 402 (PCI=1) may communicate with UE 110 but may not be configured as a serving cell, such as in carrier aggregation, where each cell may be referred to as a serving cell. UE 110 may be configured with multiple TA groups, and the multiple TA groups may include one or more serving cells. However, for a single TA group, UE 110 may maintain only a single TA for each cell.
[0050] A UE compliant with the 38.321 technical standard may be configured with multiple timing advance groups (TAGs), and each TAG may have one or more serving cells (referred to as carrier aggregation).
[0051] The examples described herein are intended to enhance the current TA framework by proposing UE initiated actions to help the network configure a second TA value to be maintained (e.g., the network (e.g., RAN 170, see Figure 2 , Figure 4 ) may periodically adjust one or more TA values of UE 110).
[0052] In the main example, refer to Figure 4 , the UE 110 may be configured to indicate information related to timing advance management (TAI, timing advance information) in the current serving cell 402. In any example, the (serving) cell may include a serving cell 402 (PCell or SCell) and a cell (additional cell or secondary cell) 404 having a PCI different from that of the serving cell, or a cell that may be used for communication with the UE 110. When a cell (e.g., 404) having a different PCI is configured by a serving cell (e.g., 402) or is part of a serving cell configuration, a cell (e.g., 404) having a different PCI (PCI=2) may be associated with a specific serving cell (e.g., 402 with PCI=1). In other words, a cell (e.g., additional cell, secondary cell) having a PCI different from that of the serving cell may be a cell for inter-cell beam management or inter-cell mTRP. The indication may be provided during a contention-based random access procedure, for example in msg.3, where msg.3 may include a MAC CE for the indication. The indication may be provided to a serving cell (e.g., 402) or a cell having a PCI different from the serving cell (e.g., 404). The indication may be provided to a serving cell or a cell having a PCI different from the serving cell during a random access procedure. The indication may be provided after a contention-based random access procedure, for example in a separate uplink MAC CE. The indication may be provided in an uplink control message, such as a MAC CE on a PUSCH. The MAC CE may also be multiplexed into an UL grant on a PUSCH. The indication may be provided in an uplink control message / channel such as a PUCCH, for example using a PUCCH format carrying indication information or using a PUCCH.
[0053] More specifically, the indication may be triggered based on conditions and / or thresholds determined by the UE, where the configuration for triggering may be provided by the network (e.g., using RRC signaling). In the indication, the UE may provide information that a specific condition regarding timing advance information (TAI) may have been triggered, and the UE 110 may request / indicate that a second TA value (second TA loop) for the serving cell 402 will be required.
[0054] The one or more conditions may include one or more of the following (followed by 1-2 items, where they may be combined conditions):
[0055] 1) The UE observes a downlink timing difference between one or more downlink reference signals (RS) relative to the timing for the first / current TA value (TA loop). The timing difference threshold may be configured, for example, as X nanoseconds or X microseconds. The timing difference threshold may be a multiple (N times) of the TA step size, N*TA (or, for example, N*x nanoseconds).
[0056] 2) Different UE antenna panels may be associated with an activated TCI state for UL transmission (but not yet indicated, e.g., the UE is not currently configured to use UL or joint DL / UL transmission, or after the UE is instructed to use multiple uplinks). Alternatively, the condition may be an indication of an activated TCI state for UL or joint DL / UL transmission. The indication may refer to the operation of the UE applying the indicated TCI state for transmission / reception. In other words, the network may configure the UE with multiple uplink links (or joint DL / UL) and activate one or more of these links so that scheduling for simultaneous transmissions can be performed. The links may be transmitted with different antenna panels and different DL RSs are used as references for UL transmissions (thus, if the timing difference is higher than a threshold, the UE may need to maintain / apply multiple TA values).
[0057] When the UE determines that the configured triggering condition applies, the UE triggers transmission of an indication (eg, MAC CE).
[0058] In one example, if a UE (e.g., UE 110) initiates a random access procedure (e.g., for buffer status reporting purposes), it may indicate during or after the random access procedure (e.g., in a MAC CE in msg.3) which TA value (maintained TA loop, e.g., first loop or second loop) the DL RS selected in the random access procedure is associated with. This indicates to the network which of the maintained TA values (TA loops) the UE may associate with the selected DL RS for random access.
[0059] In one example, the TAI may include an indication that the RS selected for a random access procedure (eg, CBRA) is considered to be part of a specific TA value (TA loop) maintained by the UE.
[0060] The request may indicate to the network (NW node 170) that another timing adjustment loop (e.g., a second loop) be configured for communication purposes, and / or indicate that a specific downlink reference signal may be observed to be received by the UE at a different timing relative to the currently observed downlink timing (based on the current timing of the first loop). This may be indicated by using a TAI value different from the currently used value.
[0061] In one embodiment, the UE may be configured to trigger an indication of a second TA value (TA loop) when the UE receives a MAC CE activation for at least a second TCI state, or more than one TCI state, and from the UE's perspective, the UE observes a timing difference in the downlink reference signal (DL RS) indicated by the first TCI state, and the second TCI state (qcl-typeD if there are multiple) exceeds a configured threshold or satisfies a condition or criterion. Alternatively, as a condition, when the UE determines that it is configured with more than one CORESETPoolIndex (indicating that the UE is configured with mTRP communication), it may be configured to trigger a TAI indication to the network. The configured threshold, condition, or criterion may be that the TA difference is greater than X nanoseconds / microseconds, etc. The configured threshold, condition, or criterion may be that the TA difference is greater than N TA steps T between the DL RS associated with the UE's PUCCH / PUSCH transmission (e.g., two unified TCI states). A (0, 1, 2...63).
[0062] In one embodiment, the configuration conditions for indicating the need for a second TA value (TA loop) may be adjusted as follows. The network may activate at least a second TCI state or multiple TCI states. The network may indicate (in addition to activation) at least a second TCI state. In an alternative, the network may activate at least a second TCI state or multiple TCI states, and the UE observes the timing difference (more than N steps, or N nanoseconds) of the DLRS relative to the first TA value (TA loop or TA reference timing). The second TCI may have an RS with a PCI different from that of the serving cell, or at least two TCI states are associated with different PCIs (e.g., one serving and one PCI different from that of the serving cell). For example, considering inter-cell beam management / mTRP, in one example, when the UE receives a MAC CE, the UE may determine whether a second TA loop needs to be initiated, which activates a unified TCI state, which is a joint DL / UL or separate UL TCI state for beam indication, and wherein the RS indicated by the TCI state is associated with a PCI different from the serving cell PCI.
[0063] The configuration conditions for indicating the need for a second TA-loop may depend on different UE panels associated with the active TCI state for UL transmissions.
[0064] In one embodiment, if the UE observes a TA difference that is above a threshold of the current TA value (TA loop), the UE may trigger a CBRA procedure. In one option, the UE may need to select a DL RS (or one of the DL RSs, such as an SSB) for CBRA in which the timing difference for CBRA is observed (e.g., the number of TA steps that the UE is allowed / able to adjust on its own) and indicates a TAI (e.g., a first maintenance TA value or a second maintenance TA value in a MAC CE). The selection of the SSB may further depend on a specific RSRP threshold.
[0065] In any of the embodiments, if the UE is configured to determine whether the timing difference condition is met, it may determine to use the current timing for UL transmission, for example relative to a reference RS (reference signal), or to use a TA value (a timing advance value associated with a first maintenance TA value). Other methods are not excluded.
[0066] In one embodiment, the TAI information may include an indication or information about one or more maintained TA values. For example, if the UE 110 includes information indicating a second TA value (i.e., another TA value), this may indicate to the network node 170 that the message or transmission is used to maintain or request an additional TA value. For example, in a MAC CE, the TAI information may include a bitmap of N bits, such as 2 bits, where a 1-bit field provides information about a first TA value (TA ring 1) and a field provides information about a second TA value (TA ring 2). One value of the bit (e.g., 0) indicates that the UE does not need a TA for the associated ring. Another value of the bit (e.g., 1) indicates that the UE 110 may need another TA for the associated ring. For example, in a MAC CE, the TAI information may include a bitmap of N bits, such as 1 bit, where a 1-bit field may provide information about a second TA value (TA ring 2). The information may be a request to maintain a second TA value (e.g., for UL communication). For example, the TAI information may include at least one (e.g., 1-bit) field indicating that the second TA value is to be maintained. In one embodiment, the TAI information in the MAC CE may include a 1-bit field, in which one value indicates the TA value to be maintained (TA ring, for example, for the first ring, bit value = 0, for the second ring, bit value = 1, and vice versa).
[0067] In one embodiment, in any of the embodiments, the indication for maintaining the TA value may refer to a request for a second TA value to be maintained. Alternatively, the maintenance may refer to a request to update the TA value for a specific maintained TA value (TA loop). In one example, in the absence of any TA indication, the UE 110 may not need to apply a TA command for a specific TA loop. In one example, the UE 110 may use the given TA value in msg.2 for subsequent UL transmissions during the random access procedure.
[0068] In one embodiment, the UE is configured with the following conditions to include the TAI information MAC CE in msg.3 or provide it as part of the random access procedure or after the random access procedure: If the RS selected for the CBRA procedure does not correspond to any DL RS configured as an active TCI state associated with the specific TA value (TA loop) maintained, the UE does not include the TAI MAC CE in msg.3. In this case, the UE may not apply the provided TA to any loop, but may use it during the RA procedure. In any of the embodiments, the bit field or set of fields providing the TAI information may be a (new) MAC CE, or part of an existing MAC CE.
[0069] In one embodiment, the MAC CE may also include an indication of an identifier or multiple identifiers of one or more DL RS set identifiers that the UE requests to be associated with the second TA value (TA loop). The (multiple) identifiers of the (multiple) DL RSs may be different from the selected DL RSs for CBRA. In the event that any of the indicated DL RSs does not correspond to the selected DL RS for RA, the UE may expect the NW to trigger a PDCCH command to maintain the second TA value. The DL RS may be indicated by reference to a TCI state or a TCI state index (e.g., listed in the MAC CE). The DL RS that may be indicated may be an RS used as a spatial relationship for one or more UL channels / signals. The indicated DL RS list may include a list of SSB index values.
[0070] In one embodiment, the MAC CE may include an indication of (a)(multiple) DL RS set identifiers, where the UE may request an association with a specific TA value (TA loop identifier, such as a first TA value or a second TA value). For example, the MAC CE may include an indication of (a)(multiple) DL RS set identifiers, where the UE may request an association with a second TA value (TA loop). The DL RS set may be configured by the network (e.g., set #1 may have DLRS #1 and DLRS #2, and set #2 may have DLRS #3 and DLRS #4, etc.). A DL RS set may have one or more DL RSs. When at least one DL SS satisfies the conditions described herein (e.g., an observed DL timing difference relative to a reference DL resource), the UE may determine that at least one condition for triggering an indication of a DL RS set (e.g., an association of a DL RS set with a TA loop) is satisfied. In some examples, all DL RSs in the group may have to satisfy a condition (e.g., a timing difference condition). For example, the timing difference condition may be that the UE observes a downlink timing difference between one or more downlink reference signals (RS) relative to the timing used for uplink timing (eg, the timing for the first / current / another TA value).
[0071] In one embodiment, when the UE has determined that the TAT (time alignment timer, upon expiration, the UE cannot consider it to be time aligned for UL transmission) of a specific TA loop has expired, but it selects the DLRS for the CBRA procedure as the RS associated with a ring different from the expired ring, the expired ring can be indicated in the MAC CE.
[0072] In one embodiment, when the UE has determined that the TAT (time alignment timer, upon expiration, the UE cannot consider it to be time aligned for UL transmission) of a specific TA loop has expired, but it selects the DL RS for the CBRA procedure as the RS associated with a loop different from the expired ring, the UE can indicate the ring associated with the DL RS, for example in a MAC CE.
[0073] In one embodiment, considering inter-cell beam management / mTRP, in one example, the UE may determine the need to maintain a second TA value (TA loop) when the UE receives a MAC CE activating a unified TCI state, which is a joint DL / UL or separate UL TCI state for beam indication, and wherein the RS indicated by the TCI state is associated with a PCI different from the serving cell PCI, or when the UE receives an indication of a TCI state (joint DL / UI or separate UL).
[0074] The benefit is that by relying on UE indications, the network can be assisted in the configuration of multiple TA values (TA loops) based on the conditions observed by the UE.
[0075] In an example embodiment, the TA loop may be a specified timing advance value that may be periodically adjusted by the network node 170 and / or maintained by the UE 110. The UE 110 may have or may be configured to apply one or more timing advance values per serving cell for a particular UL signal / channel sent to a serving cell or to a serving cell and a cell having a PCI different from that of the serving cell. For example, the UE may send one uplink signal / channel using a first TA value (maintained by a periodic / aperiodic adjustment indication and / or a TA loop / procedure adjusted by the UE), and the UE may send a second uplink signal / channel using a second TA value (maintained by a periodic / aperiodic adjustment indication and / or a TA loop / procedure adjusted by the UE). These values may be controlled individually by the network (e.g., using a periodic TA command specific to the maintained timing advance value (first or second)). In one implementation, the serving cell timing advance value may include applying at least one timing advance value to a cell having a PCI different from that of the serving cell. The cell 404 having a different PCI from the serving cell 402 may be referred to as inter-cell mTRP communication, or inter-cell beam management (i.e., the cell parameters of the cell with a different PCI are configured in the serving cell configuration, or as part of the configuration).
[0076] In an example embodiment, when the random access procedure is initiated by a PDCCH order (ie, a network-triggered random access procedure), the UE may indicate / include TAI information during the random access procedure (eg, in msg.3). The random access procedure may be a contention-based RA procedure.
[0077] In an example embodiment, information about timing advance received by the UE 110 during the RA procedure (e.g., in msg.2 and / or msg.4), or after the RA procedure, may be associated with the indicated TAI (e.g., the first TA-loop or the second TA-loop). For example, if the UE 110 receives a TAC in msg.2 and then indicates the TAI in msg.3, it may associate the TA command with the indicated TAI (e.g., the first TA-loop or the second TA-loop). Alternatively, the UE may be provided with a TAC (absolute or relative) by the network in msg.4. The TAC in msg.4 may be provided in msg.3 as a response to the TAI indication. In one example, the msg.4 TA information may be associated with the indicated TAI. As another example, the UE may use the TAC received in msg.2 of the RA procedure for subsequent transmissions, and may receive additional information from the network that the TA value provided in the TAC command is associated with a specific TA-loop (e.g., the first or second).
[0078] therefore, Figure 4 An example of inter-cell mTRP communication is shown, which may include UE 110, serving cell 402 with a PCI value of 1, and non-serving cell 404 with a PCI value of 2 (different from the PCI value of serving cell 402). Figure 4 As shown in , at 405, the terminal device 110 indicates to the network node 170 a request for TA loop timing advance adjustment information to be maintained on the serving cell 402 or the non-serving cell 404. At 406, the UE 110 receives configuration information about one or more conditions that trigger or enable application of the timing advance adjustment information from the network node 170. At 408, the terminal device 110 may apply the timing advance adjustment information about the serving cell 402 of the network node 170. At 410, the terminal device 110 may apply the timing advance adjustment information about the non-serving cell 404 of the network node 170.
[0079] The examples described in this document may serve as a potential contribution to the Release 18 discussions in RAN1#109.
[0080] Figure 5 An example apparatus 500 is configured to implement the examples described herein, which may be implemented in hardware. The apparatus 500 includes at least one processor 502 (e.g., an FPGA and / or a CPU), at least one memory 504 including computer program code 505, wherein the at least one memory 504 and the computer program code 505 are configured to, together with the at least one processor 502, cause the apparatus 500 to implement circuit systems, processes, components, modules, or functions (collectively referred to as control 506) to implement the examples described herein, including timing advance management in a wireless system. The memory 504 may be a non-volatile memory, a transient memory, a volatile memory (e.g., a RAM), or a non-volatile memory (e.g., a ROM).
[0081] The device 500 optionally includes a display and / or I / O interface 508, which can be used to display aspects or states of the methods described herein (e.g., while one of the methods is being executed, or at a subsequent time), or to receive input from a user, such as using a keypad, camera, touch screen, touch area, microphone, biometrics, etc. The device 500 includes one or more communications, such as (multiple) network (N / W) interfaces (I / F) 510. (Multiple) communication I / F 510 can be wired and / or wireless, and communicate on the Internet / (multiple) other networks via any communication technology. (Multiple) communication I / F 510 can include one or more transmitters and one or more receivers. (Multiple) communication I / F 510 can include standard well-known components, such as amplifiers, filters, frequency converters, modulators (demodulators) and encoder / decoder circuit systems, and one or more antennas.
[0082] The apparatus 500 for implementing the functionality of the control 506 may be a UE 110, a RAN node 170 (e.g., a gNB), or a network element (s) 190. Thus, the processor 502 may correspond to the processor (s) 120, the processor (s) 152, and / or the processor (s) 175, the memory 504 may correspond to the memory (s) 125, the memory (s) 155, and / or the memory (s) 171, the computer program code 505 may correspond to the computer program code 123, the module 140-1, the module 140-2, and / or the computer program code 153, the module 150-1, the module 150-2, and / or the computer program code 173, and the communication I / F (s) 510 may correspond to the transceiver 130, the antenna (s) 128, the transceiver 160, the antenna (s) 158, the N / WI / F (s) 161, and / or the N / WI / F (s) 180. Alternatively, apparatus 500 may not correspond to any of UE 110, RAN node 170, or network element(s) 190, as apparatus 500 may be part of a Self-Organizing / Optimizing Network (SON) node, such as in the cloud.
[0083] The apparatus 500 may also be distributed throughout the network (eg, 100), including within and between the apparatus 500 and any network elements (such as a network control element (NCE) 190, and / or a RAN node 170, and / or a UE 110).
[0084] like Figure 5As shown in , interface 512 enables data communication between various items of apparatus 500. For example, interface 512 can be one or more buses, such as address, data, or control buses, and can include any interconnection mechanism, such as a series of lines on a motherboard or integrated circuit, optical fiber, or other optical communication devices. Computer program code 505 including control 506 can include object-oriented software that is configured to pass data / messages between objects within computer program code 505. Apparatus 500 need not include each of the features described, or may include other features.
[0085] Figure 6 6 is an example method 600 for implementing the example embodiments described herein. At 610, the method includes: applying, by a terminal device, timing advance adjustment information about a cell of a network node. At 620, the method includes: indicating, by the terminal device to the network node, a request for further timing advance adjustment information to be maintained on the cell. The method 600 may be performed using a user equipment (e.g., UE 110).
[0086] Figure 7 7 is an example method 700 for implementing the example embodiments described herein. At 710, the method includes: sending configuration information from a network node to a terminal device, the configuration information including: one or more conditions for triggering a request for another timing advance adjustment information to be maintained on a cell of the network node. At 720, the method includes: receiving, by the network node, a request for another timing advance adjustment information to be maintained by the terminal device based on the one or more conditions. The method 700 may be performed using a network node (e.g., RAN node 170).
[0087] The following examples (1-88) are provided and described herein.
[0088] Example 1: A method comprising: applying, by a terminal device, timing advance adjustment information on a cell of a network node; and indicating, by the terminal device to the network node, a request for further timing advance adjustment information to be maintained on the cell.
[0089] Example 2: The method according to Example 1 includes: indicating the request to the network node during a random access procedure in the cell.
[0090] Example 3: The method according to Example 2 includes: sending a request via a MAC CE in a message 3 associated with a random access procedure.
[0091] Example 4: The method according to Example 1 includes: indicating the request to the network node after a random access procedure in the cell.
[0092] Example 5: A method according to any one of Examples 1 to 4, wherein the cell comprises: a serving cell, or a cell having a physical cell ID (PCI) different from that of the serving cell.
[0093] Example 6: The method according to Example 4 includes: sending the request via an uplink MAC CE in the cell.
[0094] Example 7: The method of Example 6, wherein the uplink MAC CE is multiplexed into or sent on an uplink grant on a PUSCH in the cell.
[0095] Example 8: The method according to Example 1 includes: determining one or more conditions for triggering a request; and sending a request based on the determined one or more conditions.
[0096] Example 9: The method according to Example 8 includes: receiving configuration information about one or more conditions from a network node.
[0097] Example 10: The method of Example 9, wherein configuration information regarding the one or more conditions is received via RRC signaling or a downlink MAC CE.
[0098] Example 11: A method according to Example 1, wherein the request indicates that the requested further timing advance adjustment information will be applied for subsequent uplink communication purposes, and / or indicates that at least one downlink is observed to be received by the terminal device using timing that is different from the currently observed downlink timing.
[0099] Example 12: The method of Example 11, wherein the currently observed downlink timing is based on timing advance adjustment information about the cell.
[0100] Example 13: A method, comprising: sending configuration information from a network node to a terminal device, the configuration information comprising: one or more conditions for triggering a request for another timing advance adjustment information to be maintained on a cell of the network node; and receiving, by the network node, a request for another timing advance adjustment information to be maintained by the terminal device from the terminal device based on the one or more conditions.
[0101] Example 14: The method according to Example 13 includes: receiving a request from a terminal device during a random access procedure in a cell.
[0102] Example 15: A method according to any one of Examples 13 to 14, wherein the cell includes: a serving cell, or a cell having a PCI different from a PCI of the serving cell.
[0103] Example 16: The method of Example 14, comprising: receiving the request in a message 3 associated with the random access procedure via the MAC CE.
[0104] Example 17: The method according to Example 13 includes: receiving a request from a terminal device after a random access procedure in a cell.
[0105] Example 18: The method of Example 17, comprising: receiving the request via an uplink MAC CE in the cell.
[0106] Example 19: The method of Example 18, wherein the uplink MAC CE is multiplexed into an uplink grant on a PUSCH in the cell.
[0107] Example 20: The method of Example 13, wherein configuration information regarding the one or more conditions is sent via RRC signaling or downlink MAC CE.
[0108] Example 21: A method according to Example 13, wherein the request indicates that the requested further timing advance adjustment information will be applied for subsequent uplink communication purposes, and / or indicates that at least one downlink is observed to be received by the terminal device using timing that is different from the currently observed downlink timing.
[0109] Example 22: The method of Example 21, wherein the currently observed downlink timing is based on timing advance adjustment information about the cell.
[0110] Example 23: An apparatus comprising: means for applying, by a terminal device, timing advance adjustment information about a cell of a network node; and means for indicating, by the terminal device to the network node, a request for further timing advance adjustment information to be maintained on the cell.
[0111] Example 24: The apparatus of Example 23, comprising: means for indicating a request to a network node during a random access procedure in a cell.
[0112] Example 25: The apparatus of Example 24, comprising: means for sending the request via the MAC CE in a message 3 associated with a random access procedure.
[0113] Example 26: The apparatus according to Example 23, comprising: a component for indicating the request to the network node after a random access procedure in the cell.
[0114] Example 27: An apparatus according to any one of Examples 23 to 26, wherein the cell includes: a serving cell, or a cell having a physical cell ID (PCI) different from that of the serving cell.
[0115] Example 28: The apparatus of Example 26, comprising: means for sending the request via an uplink MAC CE in the cell.
[0116] Example 29: The apparatus of Example 28, wherein the uplink MAC CE is multiplexed into or sent on an uplink grant on a PUSCH in a cell.
[0117] Example 30: The apparatus according to Example 23 comprises: a component for determining one or more conditions for triggering a request; and a component for sending a request based on the determined one or more conditions.
[0118] Example 31: The apparatus according to Example 30 comprises: a component for receiving configuration information about one or more conditions from a network node.
[0119] Example 32: The apparatus of Example 31, wherein configuration information regarding the one or more conditions is received via RRC signaling or a downlink MAC CE.
[0120] Example 33: An apparatus according to Example 23, wherein the request indicates that the requested further timing advance adjustment information will be applied for subsequent uplink communication purposes, and / or indicates that at least one downlink is observed to be received by the terminal device using timing that is different from the currently observed downlink timing.
[0121] Example 34: An apparatus according to Example 33, wherein the currently observed downlink timing is based on timing advance adjustment information about the cell.
[0122] Example 35: An apparatus comprising: a component for sending configuration information from a network node to a terminal device, the configuration information comprising: one or more conditions for triggering a request for another timing advance adjustment information to be maintained on a cell of the network node; and a component for receiving, by the network node, a request for another timing advance adjustment information to be maintained by the terminal device from the terminal device based on the one or more conditions.
[0123] Example 36: An apparatus according to Example 35, comprising: a component for receiving a request from a terminal device during a random access procedure in a cell.
[0124] Example 37: An apparatus according to any one of Examples 35 to 36, wherein the cell includes: a serving cell, or a cell having a PCI different from a PCI of the serving cell.
[0125] Example 38: The apparatus of Example 36, comprising: means for receiving a request in a message 3 associated with a random access procedure via a MAC CE.
[0126] Example 39: An apparatus according to Example 35, comprising: a component for receiving a request from a terminal device after a random access procedure in a cell.
[0127] Example 40: The apparatus of Example 39, comprising: means for receiving a request via an uplink MAC CE in a cell.
[0128] Example 41: The apparatus of Example 40, wherein the uplink MAC CE is multiplexed into an uplink grant on a PUSCH in the cell.
[0129] Example 42: The apparatus of Example 35, wherein configuration information regarding the one or more conditions is sent via RRC signaling or a downlink MAC CE.
[0130] Example 43: An apparatus according to Example 35, wherein the request indicates that the requested further timing advance adjustment information will be applied for subsequent uplink communication purposes and / or indicates that timing observed by at least one downlink will be received by the terminal device using timing that is different from the currently observed downlink timing.
[0131] Example 44: An apparatus according to Example 43, wherein the currently observed downlink timing is based on timing advance adjustment information about the cell.
[0132] Example 45: A machine-readable, non-transitory program storage device tangibly embodying a program of instructions executable by the machine for performing operations, the operations comprising: applying, by a terminal device, timing advance adjustment information about a cell of a network node; and indicating, by the terminal device to the network node, a request for another timing advance adjustment information to be maintained on the cell.
[0133] Example 46: The non-transitory program storage device according to Example 45, the operations comprising: indicating the request to the network node during a random access procedure in the cell.
[0134] Example 47: The non-transitory program storage device of Example 46, the operations comprising: sending the request via the MAC CE in a message 3 associated with a random access procedure.
[0135] Example 48: The non-transitory program storage device according to Example 45, the operations comprising: indicating the request to the network node after a random access procedure in the cell.
[0136] Example 49: A non-transitory program storage device according to any one of Examples 45 to 48, wherein the cell comprises: a serving cell, or a cell having a physical cell ID (PCI) different from a serving cell.
[0137] Example 50: The non-transitory program storage device of Example 48, the operations comprising: sending the request via an uplink MAC CE in the cell.
[0138] Example 51: A non-transitory program storage device according to Example 50, wherein the uplink MAC CE is multiplexed into or sent on an uplink grant on a PUSCH in the cell.
[0139] Example 52: The non-transitory program storage device of Example 45, the operation comprising: determining one or more conditions for triggering a request; and sending the request based on the determined one or more conditions.
[0140] Example 53: The non-transitory program storage device according to Example 52, the operation comprising: receiving configuration information about one or more conditions from a network node.
[0141] Example 54: The non-transitory program storage device of Example 53, wherein the configuration information regarding the one or more conditions is received via RRC signaling or a downlink MAC CE.
[0142] Example 55: A non-volatile program storage device according to Example 45, wherein the request indicates that the requested further timing advance adjustment information will be applied for subsequent uplink communication purposes, and / or indicates that at least one downlink is observed to be received by the terminal device using timing that is different from the currently observed downlink timing.
[0143] Example 56: A non-transitory program storage device according to Example 55, wherein the currently observed downlink timing is based on timing advance adjustment information about the cell.
[0144] Example 57: A machine-readable, non-volatile program storage device, tangibly embodying a program of machine-executable instructions for performing operations, the operations comprising: sending configuration information from a network node to a terminal device, the configuration information comprising: one or more conditions for triggering a request for another timing advance adjustment information to be maintained on a cell of the network node; and receiving, by the network node from the terminal device, a request for another timing advance adjustment information to be maintained by the terminal device based on the one or more conditions.
[0145] Example 58: The non-transitory program storage device according to Example 57, the operation comprising: receiving a request from a terminal device during a random access procedure in a cell.
[0146] Example 59: A non-transitory program storage device according to any one of Examples 57 to 58, wherein the cell comprises: a serving cell, or a cell having a PCI different from a PCI of the serving cell.
[0147] Example 60 The non-transitory program storage device of Example 58, the operations comprising: receiving the request via the MAC CE in a message 3 associated with a random access procedure.
[0148] Example 61: The non-transitory program storage device according to Example 57, the operation comprising: receiving a request from a terminal device after a random access procedure in a cell.
[0149] Example 62: The non-transitory program storage device of Example 61, the operations comprising: receiving the request via an uplink MAC CE in the cell.
[0150] Example 63: A non-transitory program storage device according to Example 62, wherein the uplink MAC CE is multiplexed into an uplink grant on a PUSCH in the cell.
[0151] Example 64: The non-transitory program storage device of Example 57, wherein the configuration information regarding the one or more conditions is sent via RRC signaling or a downlink MAC CE.
[0152] Example 65: A non-volatile program storage device according to Example 57, wherein the request indicates that the requested further timing advance adjustment information will be applied for subsequent uplink communication purposes, and / or indicates that at least one downlink is observed to be received by the terminal device using timing that is different from the currently observed downlink timing.
[0153] Example 66: A non-transitory program storage device according to Example 65, wherein the currently observed downlink timing is based on timing advance adjustment information about the cell.
[0154] Example 67: An apparatus comprising: at least one processor; and at least one memory comprising computer program code; wherein the at least one memory and the computer program code are configured, together with the at least one processor, to cause the apparatus to at least: apply timing advance adjustment information about a cell of a network node by a terminal device; and indicate, by the terminal device to the network node, a request for another timing advance adjustment information to be maintained on the cell.
[0155] Example 68: The apparatus according to Example 67, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to at least: indicate a request to a network node during a random access procedure in a cell.
[0156] Example 69: The apparatus of Example 68, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to at least: send the request via the MAC CE in a message 3 associated with a random access procedure.
[0157] Example 70: The apparatus according to Example 67, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to at least: indicate a request to a network node after a random access procedure in a cell.
[0158] Example 71: An apparatus according to any one of Examples 67 to 70, wherein the cell includes: a serving cell, or a cell having a physical cell ID (PCI) different from that of the serving cell.
[0159] Example 72: The apparatus of Example 70, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to at least: send the request via an uplink MAC CE in the cell.
[0160] Example 73: The apparatus of Example 72, wherein the uplink MAC CE is multiplexed into or sent on an uplink grant on a PUSCH in a cell.
[0161] Example 74: An apparatus according to Example 67, wherein at least one memory and computer program code are configured to, together with at least one processor, cause the apparatus to at least: determine one or more conditions for triggering a request; and send a request based on the determined one or more conditions.
[0162] Example 75: The apparatus according to Example 74, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to at least: receive configuration information regarding one or more conditions from a network node.
[0163] Example 76: The apparatus of Example 75, wherein configuration information regarding the one or more conditions is received via RRC signaling or a downlink MAC CE.
[0164] Example 77: An apparatus according to Example 67, wherein the request indicates that the requested further timing advance adjustment information will be applied for subsequent uplink communication purposes, and / or indicates that at least one downlink is observed to be received by the terminal device using timing that is different from the currently observed downlink timing.
[0165] Example 78: An apparatus according to Example 77, wherein the currently observed downlink timing is based on timing advance adjustment information about the cell.
[0166] Example 79: An apparatus comprising: at least one processor; and at least one memory comprising computer program code; wherein the at least one memory and the computer program code are configured, together with the at least one processor, so that the apparatus at least: sends configuration information from a network node to a terminal device, the configuration information comprising: one or more conditions for triggering a request for another timing advance adjustment information to be maintained on a cell of the network node; and receives, by the network node, a request for another timing advance adjustment information to be maintained by the terminal device from the terminal device based on the one or more conditions.
[0167] Example 80: The apparatus according to Example 79, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to at least: receive a request from a terminal device during a random access procedure in a cell.
[0168] Example 81: An apparatus according to any one of Examples 79 to 80, wherein the cell includes: a serving cell, or a cell having a PCI different from a PCI of the serving cell.
[0169] Example 82: The apparatus of Example 80, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to at least: receive a request via a MAC CE in a message 3 associated with a random access procedure.
[0170] Example 83: The apparatus according to Example 79, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to at least: receive a request from a terminal device after a random access procedure in a cell.
[0171] Example 84: The apparatus of Example 83, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to at least: receive the request via an uplink MAC CE in the cell.
[0172] Example 85: The apparatus of Example 84, wherein the uplink MAC CE is multiplexed into an uplink grant on a PUSCH in the cell.
[0173] Example 86: The apparatus of Example 79, wherein configuration information regarding the one or more conditions is sent via RRC signaling or a downlink MAC CE.
[0174] Example 87: An apparatus according to Example 79, wherein the request indicates that the requested further timing advance adjustment information will be applied for subsequent uplink communication purposes, and / or indicates that at least one downlink is observed to be received by the terminal device using timing that is different from the currently observed downlink timing.
[0175] Example 88: An apparatus according to Example 87, wherein the currently observed downlink timing is based on timing advance adjustment information about the cell.
[0176] References to "computers," "processors," and the like should be understood to cover not only computers having different architectures (such as single / multi-processor architectures and sequential or parallel architectures), but also special purpose circuits, such as field programmable gate arrays (FPGAs), application specific circuits (ASICs), signal processing devices, and other processing circuit systems. References to computer programs, instructions, code, and the like should be understood to cover software or firmware for programmable processors, such as, for example, the programmable content of hardware devices, whether instructions for a processor, or configuration settings for a fixed function device, gate array, or programmable logic device, and the like.
[0177] The memory(s) described herein may be implemented using any suitable data storage technology, such as semiconductor-based memory devices, flash memory, magnetic memory devices and systems, optical memory devices and systems, non-volatile memory, transient memory, fixed memory, and removable memory. The memory(s) may include a database for storing data.
[0178] As used herein, the term "circuitry" may refer to the following: (a) hardware circuit implementations, such as implementations in analog and / or digital circuitry, and (b) combinations of circuitry and software (and / or firmware), such as, as applicable: (i) a combination of (multiple) processors, or (ii) portions of (multiple) processors / software, including (multiple) digital signal processors, software, and (multiple) memories, which work together to enable the device to perform various functions, and (c) circuits that require software or firmware to operate (even if the software or firmware is not physically present), such as (multiple) microprocessors or portions of (multiple) microprocessors. As another example, as used herein, the term "circuitry" would also cover implementations of only a processor (or multiple processors) or a portion of a processor and its accompanying software and / or firmware. For example, if applicable to the particular element, the term "circuitry" would also cover a baseband integrated circuit or application processor integrated circuit for a mobile phone, or a similar integrated circuit in a server, cellular network device, or another network device.
[0179] In the figure, the arrows between individual blocks indicate the operational couplings between them and the direction of data flow over these couplings.
[0180] It should be understood that the above description is illustrative only. Those skilled in the art may design various alternatives and modifications. For example, the features described in the various dependent claims may be combined with each other in any suitable (multiple) combination. In addition, the features of the above-mentioned different example embodiments may be selectively combined into new example embodiments. Therefore, this specification is intended to cover all such alternatives, modifications, and variations that fall within the scope of the appended claims.
[0181] The following abbreviations and abbreviations that may appear in the specification and / or drawings are defined as follows (abbreviations and abbreviations may be appended to each other or may be appended with other characters such as dashes or hyphens):
[0182] 4G: Fourth Generation
[0183] 5G: Fifth Generation
[0184] 5GC: 5G core network
[0185] ACK: Acknowledgement
[0186] aka: Also known as
[0187] AMF: Access and Mobility Management Function
[0188] ASIC: Application-Specific Integrated Circuit
[0189] CBRA: Contention-based random access
[0190] CC: Component Carrier
[0191] CE: Control Element
[0192] CJT: Coherent Joint Transmission
[0193] CORESET: Control resource set
[0194] CP: Cyclic Prefix
[0195] CPE: Customer Premises Equipment
[0196] CPU: Central Processing Unit
[0197] CSI: Channel State Information
[0198] CU: Central Unit or Centralized Unit
[0199] DCI: Downlink Control Information
[0200] DL: Downlink
[0201] DLRS: Downlink Reference Signal
[0202] DMRS: Demodulation Reference Signal
[0203] DSP: Digital Signal Processor
[0204] DU: Distributed Unit
[0205] eNB: Evolved Node B (e.g., LTE base station)
[0206] EN-DC: E-UTRAN New Radio - Dual Connectivity
[0207] en-gNB: A node that provides NR user plane and control plane protocol termination towards the UE and acts as a secondary node in EN-DC
[0208] E-UTRA: Evolved Universal Terrestrial Radio Access, also known as LTE radio access technology E-UTRAN: E-UTRA network
[0209] F1: Interface between CU and DU
[0210] FDD: Frequency Division Duplex
[0211] feMIMO: Further enhanced MIMO FPGA: Field Programmable Gate Array
[0212] FR: Frequency range
[0213] FWA: Fixed Wireless Access
[0214] gNB: A base station for 5G / NR, i.e., a node that provides NR user plane and control plane protocol termination towards the UE and is connected to the 5GC via the NG interface
[0215] HARQ: Hybrid Automatic Repeat Request
[0216] IAB: Integrated Access and Backhaul
[0217] ID: Identifier
[0218] I / F: Interface
[0219] I / O: Input / Output
[0220] JT: Joint Transmission
[0221] eLCID: Extended Logical Channel ID
[0222] LCID: Logical Channel ID
[0223] LMF: Location Management Function
[0224] LTE: Long Term Evolution (4G)
[0225] MAC: Media Access Control
[0226] MIMO: Multiple Input Multiple Output
[0227] MME: Mobility Management Entity
[0228] msg.2: Message 2 of the 4-step RACH procedure, Random Access Response msg.3: Message 3 of the 4-step RACH procedure involving scheduled UL transmission, RRC Connection Request
[0229] msg.4: Message 4 in the 4-step RACH process, contention resolution
[0230] mTRP: Multi-TRP
[0231] MU: Multi-User
[0232] NCE: Network Control Element
[0233] ng or NG: New Generation
[0234] ng-eNB: Next Generation eNB NG-RAN: Next Generation Radio Access Network
[0235] NR: New Radio (5G)
[0236] NW: Network
[0237] N / W: Network
[0238] OFDM: Orthogonal Frequency Division Multiplexing
[0239] PCI: Physical Cell ID
[0240] PDA: Personal Digital Assistant
[0241] PDCCH: Physical Downlink Control Channel
[0242] PDCP: Packet Data Convergence Protocol
[0243] PHY: Physical layer
[0244] PUCCH: Physical Uplink Control Channel
[0245] PUSCH: Physical Uplink Shared Channel
[0246] qcl: quasi-colocation
[0247] R: retain or release, depending on the context
[0248] RA: Random Access
[0249] RACH: Random Access Channel
[0250] RAM: Random Access Memory
[0251] RAN: Radio Access Network
[0252] RAN1: Radio Layer 1
[0253] Rel-: version
[0254] RLC: Radio Link Control
[0255] ROM: Read Only Memory
[0256] RRC: Radio Resource Control (protocol)
[0257] RS: Reference signal
[0258] RU: Radio Unit
[0259] Rx: Receiver or Receive
[0260] SGW: Serving Gateway
[0261] SMF: Session Management Function
[0262] SON: Self-Organizing / Optimizing Network
[0263] SpCell: Dedicated Cell
[0264] SRI: SRS resource indicator
[0265] SRS: Sounding Reference Signal
[0266] SSB: Synchronization Signal Block
[0267] TA: Timing ahead
[0268] TAC: Timing Advance Command
[0269] TAG: Timing Advance Group
[0270] TAI: Timing Advance Information
[0271] TAT: Time Alignment Timer
[0272] TCI: Transmission Configuration Indicator
[0273] TDD: Time Division Duplex
[0274] TPMI: Transmitted Precoding Matrix Indicator
[0275] TRP: Transmission and / or Reception Point
[0276] TS: Technical Specification
[0277] Tx: Transmitter or Transmit
[0278] Type-II: Codebook for CSI feedback, used to report the wideband and subband amplitude information of the selected beam
[0279] UE: User Equipment (e.g., wireless device, typically a mobile device)
[0280] UL: Uplink
[0281] UPF: User Plane Function
[0282] X2: Network interface between RAN nodes and between RAN and core network
[0283] Xn: Network interface between NG-RAN nodes
Claims
1. A method comprising: applying, by the terminal device, timing advance adjustment information about a cell of the network node; as well as A request for further timing advance adjustment information to be maintained on the cell is indicated by the terminal device to the network node.
2. The method according to claim 1, comprising: The request is indicated to the network node during a random access procedure in the cell.
3. The method according to claim 2, comprising: The request is sent via MAC CE in message 3 associated with the random access procedure.
4. The method according to claim 1, comprising: The request is indicated to the network node following a random access procedure in the cell.
5. The method according to any one of claims 1 to 4, wherein the cell comprises: A serving cell, or a cell having a physical cell ID (PCI) different from the serving cell's PCI.
6. The method according to claim 4, comprising: The request is sent via an uplink MAC CE in the cell.
7. The method of claim 6, wherein the uplink MAC CE is multiplexed to an uplink grant on a PUSCH in the cell or is sent on an uplink grant on a PUSCH in the cell.
8. The method according to claim 1, comprising: determining one or more conditions for triggering the request; as well as Based on the determined one or more conditions, the request is sent.
9. The method according to claim 8, comprising: Configuration information regarding the one or more conditions is received from the network node.
10. The method of claim 9, wherein the configuration information about the one or more conditions is received via RRC signaling or downlink MAC CE.
11. The method of claim 1, wherein the request for the further timing advance adjustment information enables configuration of the terminal device to maintain a further timing advance loop in addition to a timing advance loop already maintained with the cell.
12. The method of claim 1, wherein the further timing advance adjustment information has a timing advance value different from a currently observed downlink timing value currently used by the terminal device.
13. A method according to claim 12, wherein the request indicates that the requested another timing advance adjustment information will be applied for subsequent uplink communication purposes, and / or indicates that at least one downlink is observed to be received by the terminal device using the another timing advance value, and the another timing advance value is different from the currently observed downlink timing.
14. The method of claim 11, wherein an uplink having another timing value and a current uplink timing value at any given time is independently maintained and updated by the network node.
15. A method according to claim 12, wherein when the terminal device receives a downlink MAC control element (MAC CE) activating at least a second transmission control information (TCI) state, the terminal device is configured to trigger the indication of the other timing advance loop, and the terminal device observes the timing difference of the downlink reference signal (DL RS) indicated by the first TCI state and the second TCI state that exceeds the configured threshold condition or standard.
16. The method of claim 15, wherein the threshold condition or criterion comprises one of the following: When the timing difference is greater than the defined nanoseconds / microseconds, and When the timing difference is greater than a defined number of Timing Advance (TA) steps between the DL_RS associated with the PUCCH / PUSCH transmissions of the terminal device.
17. The method according to claim 15, wherein the configuration condition for indicating the another timing advance loop comprises: The network activates at least the second TCI state or multiple TCI states, and the terminal device is configured to observe the timing difference exceeding a defined number of steps of the DL_RS.
18. The method of claim 15, wherein the downlink MAC CE activates at least a second transmission configuration indicator (TCI) state to indicate one or more downlink reference signals.
19. A method comprising: sending configuration information from a network node to a terminal device, the configuration information comprising: one or more conditions for triggering a request for further timing advance adjustment information to be maintained on a cell of the network node; and The request for the further timing advance adjustment information to be maintained by the terminal device is received, by the network node, from the terminal device based on the one or more conditions.
20. The method according to claim 19, comprising: The request is received from the terminal device during a random access procedure in the cell.
21. The method according to claim 20, comprising: The request is received from the terminal device via a MAC CE in a message 3 associated with the random access procedure.
22. The method according to claim 19, comprising: An indication from the request is received from the terminal device following a random access procedure in the cell.
23. The method according to any one of claims 19 to 22, wherein the cell comprises: A serving cell, or a cell having a PCI different from the PCI of the serving cell.
24. The method according to claim 22, comprising: The request is received via an uplink MAC CE in the cell.
25. The method of claim 24, wherein the uplink MAC CE is multiplexed into an uplink grant on a PUSCH in the cell.
26. The method according to claim 24, comprising: Sending configuration information about the one or more conditions to the terminal device.
27. The method of claim 26, wherein the configuration information about the one or more conditions is transmitted via RRC signaling or downlink MAC CE.
28. The method of claim 19, wherein the request for the further timing advance adjustment information enables configuration of the terminal device to maintain a further timing advance loop in addition to a timing advance loop already maintained with the cell.
29. The method of claim 19, wherein the further timing advance adjustment information has a timing advance value that is different from a currently observed downlink timing value currently used by the terminal device.
30. A method according to claim 29, wherein the request indicates that the requested another timing advance adjustment information will be applied for subsequent uplink communication purposes, and / or indicates that at least one downlink is observed to be received by the terminal device using the another timing advance value, and the another timing advance value is different from the currently observed downlink timing.
31. The method of claim 28, wherein an uplink having another timing value and a current uplink timing value at any given time is independently maintained and updated by the network node.
32. The method of claim 29, comprising: sending a downlink MAC control element (MAC CE) activating at least a second transmission control information (TCI) state; as well as The terminal device is triggered to indicate the other timing advance loop and a timing difference of the downlink reference signal (DL RS) indicated by the first TCI state and the second TCI state is observed that exceeds a configured threshold condition or criterion.
33. The method of claim 32, wherein the threshold condition or criterion comprises one of: When the timing difference is greater than the defined nanoseconds / microseconds, and When the timing difference is greater than a defined number of Timing Advance (TA) steps between the DL_RS associated with the PUCCH / PUSCH transmissions of the terminal device.
34. The method according to claim 32, wherein the configuration condition for indicating the another timing advance loop comprises: The network activates at least the second TCI state or multiple TCI states, and the terminal device is configured to observe the timing difference exceeding a defined number of steps of the DL_RS.
35. The method of claim 32, wherein the downlink MAC CE activates at least a second transmission configuration indicator (TCI) state to indicate one or more downlink reference signals.
36. An apparatus comprising: means for applying, by a terminal device, timing advance adjustment information about a cell of a network node; as well as Means for indicating, by the terminal device to the network node, a request for further timing advance adjustment information to be maintained on the cell.
37. An apparatus comprising: means for sending configuration information from a network node to a terminal device, the configuration information comprising: one or more conditions for triggering a request for further timing advance adjustment information to be maintained on a cell of the network node; and Means for receiving, by the network node, from the terminal device, the request for the further timing advance adjustment information to be maintained by the terminal device based on the one or more conditions.
38. A non-transitory program storage device readable by a machine, tangibly embodying a program of instructions executable by the machine for performing operations comprising: applying, by the terminal device, timing advance adjustment information about a cell of the network node; as well as A request for further timing advance adjustment information to be maintained on the cell is indicated by the terminal device to the network node.
39. The non-transitory program storage device of claim 38, the operations comprising: The request is indicated to the network node during a random access procedure in the cell.
40. The non-transitory program storage device of claim 39, the operations comprising: The request is sent via MAC CE in message 3 associated with the random access procedure.
41. The non-transitory program storage device of claim 38, the operations comprising: The request is indicated to the network node following a random access procedure in the cell.
42. A non-transitory program storage device according to any one of claims 38 to 41, wherein the cell comprises: A serving cell, or a cell having a physical cell ID (PCI) different from the serving cell's PCI.
43. The non-transitory program storage device of claim 41 , the operations comprising: The request is sent via an uplink MAC CE in the cell.
44. The non-transitory program storage device of claim 43, wherein the uplink MAC CE is multiplexed into or sent on an uplink grant on a PUSCH in the cell.
45. The non-transitory program storage device of claim 38, the operations comprising: determining one or more conditions for triggering the request; as well as Based on the determined one or more conditions, the request is sent.
46. The non-transitory program storage device of claim 45, the operations comprising: Configuration information regarding the one or more conditions is received from the network node.
47. The non-transitory program storage device of claim 46, wherein the configuration information regarding the one or more conditions is received via RRC signaling or a downlink MAC CE.
48. The non-transitory program storage device of claim 38, wherein the request for the further timing advance adjustment information enables configuration of the terminal device to maintain a further timing advance loop in addition to a timing advance loop already maintained with the cell.
49. The non-transitory program storage device of claim 38, wherein the further timing advance adjustment information has a timing advance value that is different from a currently observed downlink timing value currently used by the terminal device.
50. A non-volatile program storage device according to claim 49, wherein the request indicates that the requested another timing advance adjustment information will be applied for subsequent uplink communication purposes, and / or indicates that at least one downlink is observed to be received by the terminal device using the another timing advance value, and the another timing advance value is different from the currently observed downlink timing.
51. The non-transitory program storage device of claim 48, wherein an uplink having another timing value and a current uplink timing value at any given time is independently maintained and updated by the network node.
52. A non-transitory program storage device according to claim 49, wherein when the terminal device receives a downlink MAC control element (MAC CE) activating at least a second transmission control information (TCI) state, the terminal device is configured to trigger the indication of the other timing advance loop, and the terminal device observes a timing difference of the downlink reference signal (DL RS) indicated by the first TCI state and the second TCI state that exceeds a configured threshold condition or standard.
53. The non-transitory program storage device of claim 52, wherein the threshold condition or criterion comprises one of: When the timing difference is greater than the defined nanoseconds / microseconds, and When the timing difference is greater than a defined number of Timing Advance (TA) steps between the DL_RS associated with the PUCCH / PUSCH transmissions of the terminal device.
54. The non-transitory program storage device of claim 52, wherein the configuration condition for indicating the another timing advance loop comprises: The network activates at least the second TCI state or multiple TCI states, and the terminal device is configured to observe the timing difference exceeding a defined number of steps of the DL_RS.
55. The non-transitory program storage device of claim 52, wherein the downlink MAC CE activates at least a second transmission configuration indicator (TCI) state to indicate one or more downlink reference signals.
56. A non-transitory program storage device readable by a machine, tangibly embodying a program of instructions executable by the machine for performing operations comprising: sending configuration information from a network node to a terminal device, the configuration information comprising: one or more conditions for triggering a request for further timing advance adjustment information to be maintained on a cell of the network node; and The request for the further timing advance adjustment information to be maintained by the terminal device is received, by the network node, from the terminal device based on the one or more conditions.
57. The non-transitory program storage device of claim 56, the operations comprising: The request is received from the terminal device during a random access procedure in the cell.
58. The non-transitory program storage device of claim 57, comprising: The request is received from the terminal device via a MAC CE in a message 3 associated with the random access procedure.
59. The non-transitory program storage device of claim 56, comprising: An indication from the request is received from the terminal device following a random access procedure in the cell.
60. A non-transitory program storage device according to any one of claims 56 to 59, wherein the cell comprises: A serving cell, or a cell having a PCI different from the PCI of the serving cell.
61. The non-transitory program storage device of claim 59, the operations comprising: The request is received via an uplink MAC CE in the cell.
62. The method of claim 61, wherein the uplink MAC CE is multiplexed into an uplink grant on a PUSCH in the cell.
63. The method of claim 61, comprising: Sending configuration information about the one or more conditions to the terminal device.
64. The method of claim 63, wherein the configuration information about the one or more conditions is sent via RRC signaling or downlink MAC CE.
65. The method of claim 56, wherein the request for the further timing advance adjustment information enables configuration of the terminal device to maintain a further timing advance loop in addition to a timing advance loop already maintained with the cell.
66. The method of claim 56, wherein the further timing advance adjustment information has a timing advance value that is different from a currently observed downlink timing value currently used by the terminal device.
67. A method according to claim 66, wherein the request indicates that the requested another timing advance adjustment information will be applied for subsequent uplink communication purposes, and / or indicates that at least one downlink is observed to be received by the terminal device using the another timing advance value, and the another timing advance value is different from the currently observed downlink timing.
68. The method of claim 65, wherein an uplink having another timing value and a current uplink timing value at any given time is independently maintained and updated by the network node.
69. The method of claim 66, comprising: sending a downlink MAC control element (MAC CE) activating at least a second transmission control information (TCI) state; as well as The terminal device is triggered to indicate the other timing advance loop and a timing difference of the downlink reference signal (DL RS) indicated by the first TCI state and the second TCI state is observed that exceeds a configured threshold condition or criterion.
70. The method of claim 69, wherein the threshold condition or criterion comprises one of: When the timing difference is greater than the defined nanoseconds / microseconds, and When the timing difference is greater than a defined number of Timing Advance (TA) steps between the DL_RS associated with the PUCCH / PUSCH transmissions of the terminal device.
71. The method of claim 69, wherein the configuration condition for indicating the another timing advance loop comprises: The network activates at least the second TCI state or multiple TCI states, and the terminal device is configured to observe the timing difference exceeding a defined number of steps of the DL_RS.
72. The method of claim 69, wherein the downlink MAC CE activates at least a second transmission configuration indicator (TCI) state to indicate one or more downlink reference signals.
73. An apparatus comprising: at least one processor; as well as at least one memory including computer program code; wherein the at least one memory and the computer program code are configured to, together with the at least one processor, cause the apparatus to at least: applying, by the terminal device, timing advance adjustment information about a cell of the network node; as well as A request for further timing advance adjustment information to be maintained on the cell is indicated by the terminal device to the network node.
74. The apparatus of claim 73, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to at least: The request is indicated to the network node during a random access procedure in the cell.
75. The apparatus of claim 74, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to at least: The request is sent via MAC CE in message 3 associated with the random access procedure.
76. The apparatus of claim 73, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to at least: The request is indicated to the network node following a random access procedure in the cell.
77. The apparatus of claim 74, wherein the at least one memory and the computer program code are configured to: The request is sent via MAC CE in message 3 associated with the random access procedure.
78. The apparatus of claim 73, wherein the at least one memory and the computer program code are configured to: The request is indicated to the network node following a random access procedure in the cell.
79. The apparatus of any one of claims 73 to 76, wherein the cell comprises: A serving cell, or a cell having a physical cell ID (PCI) different from the serving cell's PCI.
80. The apparatus of claim 76, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to at least: The request is sent via an uplink MAC CE in the cell.
81. The apparatus of claim 80, wherein the uplink MAC CE is multiplexed into or sent on an uplink grant on a PUSCH in the cell.
82. The apparatus of claim 73, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to at least: determining one or more conditions for triggering the request; and Based on the determined one or more conditions, the request is sent.
83. The apparatus of claim 82, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to at least: Configuration information regarding the one or more conditions is received from the network node.
84. The apparatus of claim 83, wherein the configuration information regarding the one or more conditions is received via RRC signaling or a downlink MAC CE.
85. The apparatus of claim 73, wherein the request for the further timing advance adjustment information enables configuration of the terminal device to maintain a further timing advance loop in addition to a timing advance loop already maintained with the cell.
86. An apparatus according to claim 73, wherein the other timing advance adjustment information has a timing advance value different from a current observed downlink timing value currently used by the terminal device.
87. An apparatus according to claim 86, wherein the request indicates that the requested another timing advance adjustment information will be applied for subsequent uplink communication purposes, and / or indicates that at least one downlink is observed to be received by the terminal device using the another timing advance value, and the another timing advance value is different from the currently observed downlink timing.
88. The apparatus of claim 85, wherein an uplink having another timing value and a current uplink timing value at any given time is independently maintained and updated by the network node.
89. An apparatus according to claim 86, wherein when the terminal device receives a downlink MAC control element (MAC CE) activating at least a second transmission control information (TCI) state, the terminal device is configured to trigger the indication of the other timing advance loop, and the terminal device observes a timing difference of the downlink reference signal (DL RS) indicated by the first TCI state and the second TCI state that exceeds a configured threshold condition or standard.
90. The apparatus of claim 89, wherein the threshold condition or criterion comprises one of: When the timing difference is greater than the defined nanoseconds / microseconds, and When the timing difference is greater than a defined number of Timing Advance (TA) steps between the DL_RS associated with the PUCCH / PUSCH transmissions of the terminal device.
91. The apparatus of claim 89, wherein the configuration condition for indicating the another timing advance loop comprises: The network activates at least the second TCI state or multiple TCI states, and the terminal device is configured to observe the timing difference exceeding a defined number of steps of the DL_RS.
92. The apparatus of claim 89, wherein the downlink MAC CE activates at least a second transmission configuration indicator (TCI) state to indicate one or more downlink reference signals.
93. An apparatus comprising: at least one processor; as well as at least one memory including computer program code; wherein the at least one memory and the computer program code are configured to, together with the at least one processor, cause the apparatus to at least: sending configuration information from a network node to a terminal device, the configuration information comprising: one or more conditions for triggering a request for further timing advance adjustment information to be maintained on a cell of the network node; as well as The request for further timing advance adjustment information to be maintained by the terminal device is received, by the network node, from the terminal device based on the one or more conditions.
94. The apparatus of claim 93, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to at least: The request is received from the terminal device during a random access procedure in the cell.
95. The apparatus of claim 94, wherein the at least one memory and the computer program code are configured to: The request is received from the terminal device via a MAC CE in a message 3 associated with the random access procedure.
96. The apparatus of claim 93, wherein the at least one memory and the computer program code are configured to: An indication from the request is received from the terminal device following a random access procedure in the cell.
97. The apparatus of any one of claims 93 to 96, wherein the cell comprises: A serving cell, or a cell having a PCI different from the PCI of the serving cell.
98. The apparatus of claim 95, wherein the at least one memory and the computer program code are configured to: The request is received via an uplink MAC CE in the cell.
99. The apparatus of claim 97, wherein the uplink MAC CE is multiplexed into an uplink grant on a PUSCH in the cell.
100. The apparatus of claim 98, wherein the uplink MAC CE is multiplexed into an uplink grant on a PUSCH in the cell.
101. The apparatus of claim 98, wherein the at least one memory and the computer program code are configured to: Sending configuration information about the one or more conditions to the terminal device.
102. The apparatus of claim 100, wherein the configuration information regarding the one or more conditions is transmitted via RRC signaling or a downlink MAC CE.
103. The apparatus of claim 93, wherein the request for the further timing advance adjustment information enables configuration of the terminal device to maintain a further timing advance loop in addition to a timing advance loop already maintained with the cell.
104. An apparatus according to claim 93, wherein the other timing advance adjustment information has a timing advance value different from a currently observed downlink timing value currently used by the terminal device.
105. An apparatus according to claim 103, wherein the request indicates that the requested another timing advance adjustment information will be applied for subsequent uplink communication purposes, and / or indicates that at least one downlink is observed to be received by the terminal device using the another timing advance value, and the another timing advance value is different from the currently observed downlink timing.
106. The apparatus of claim 102, wherein an uplink having another timing value and a current uplink timing value at any given time is independently maintained and updated by the network node.
107. The apparatus of claim 103, wherein the at least one memory and the computer program code are configured to: sending a downlink MAC control element (MAC CE) activating at least a second transmission control information (TCI) state; and The terminal device is triggered to indicate the other timing advance loop and a timing difference of the downlink reference signal (DL RS) indicated by the first TCI state and the second TCI state is observed that exceeds a configured threshold condition or criterion.
108. The apparatus of claim 106, wherein the threshold condition or criterion comprises one of: When the timing difference is greater than the defined nanoseconds / microseconds, and When the timing difference is greater than a defined number of Timing Advance (TA) steps between the DL_RS associated with the PUCCH / PUSCH transmissions of the terminal device.
109. The apparatus of claim 106, wherein the configuration condition for indicating the another timing advance loop comprises: The network activates at least the second TCI state or multiple TCI states, and the terminal device is configured to observe the timing difference exceeding a defined number of steps of the DL_RS.
110. The apparatus of claim 106, wherein the downlink MAC CE activates at least a second transmission configuration indicator (TCI) state to indicate one or more downlink reference signals.
