Method and device for determining timing advance value

Abstract

Embodiments of the present disclosure relate to methods and apparatus for determining a timing advance value. According to some embodiments of the present disclosure, a method includes: receiving, at a third node, information related to a timing advance (TA) value for uplink transmission from a second node, wherein the second node is a parent node of the third node; and determining a first TA value for uplink transmission based on the information.

Description

Technical Field

[0001] Embodiments of the present disclosure relate generally to wireless communication techniques, and more particularly to timing advance (TA) value determination and indication. Background Art

[0002] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, broadcasts, etc. Wireless communication systems may employ a variety of access technologies capable of supporting communication with multiple users by sharing available system resources such as time, frequency, and power. Examples of wireless communication systems may include fourth generation (4G) systems such as long term evolution (LTE) systems, LTE-advanced (LTE-A) systems, or LTE-A Pro systems, and fifth generation (5G) systems which may also be referred to as new radio (NR) systems.

[0003] In order to expand the coverage and availability of wireless communication systems (such as 5G systems), 3GPP is envisioning an integrated access and backhaul (IAB) architecture to support multi-hop relays. In an IAB network, an IAB node may jump through one or more IAB nodes before reaching a base station (also referred to as an "IAB donor" or "donor node"). A single hop can be considered a special case of a multi-hop. Multi-hop backhaul is relatively beneficial because it provides a relatively larger coverage extension than a single-hop backhaul. In relatively high-frequency radio communication systems (e.g., radio signals transmitted in frequency bands above 6 GHz), relatively narrow or small signal coverage can benefit from multi-hop backhaul technology.

[0004] The industry desires techniques for determining and indicating a timing advance (TA) value in an IAB network. Summary of the invention

[0005] An embodiment of the present disclosure provides a method. The method may include: receiving, at a third node, information related to a timing advance (TA) value for uplink transmission from a second node, wherein the second node is a parent node of the third node; and determining a first TA value for uplink transmission based on the information.

[0006] Another embodiment of the present disclosure provides a method. The method may include: transmitting information related to a timing advance (TA) value for uplink transmission at a third node from a second node to the third node, wherein the second node is a parent node of the third node.

[0007] Another embodiment of the present application provides an apparatus. The apparatus includes: at least one non-transitory computer-readable medium having computer-executable instructions stored thereon; at least one receiving circuit system; at least one transmitting circuit system; and at least one processor coupled to the at least one non-transitory computer-readable medium, the at least one receiving circuit system, and the at least one transmitting circuit system. The computer-executable instructions cause the at least one processor to implement any one of the methods mentioned above. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] In order to describe the manner in which the advantages and features of the present disclosure can be obtained, the description of the present disclosure is presented by reference to specific embodiments of the present disclosure illustrated in the accompanying drawings. These drawings depict only exemplary embodiments of the present disclosure and therefore should not be considered limiting of its scope.

[0009] Figure 1 is a schematic diagram illustrating an exemplary wireless communication system according to some embodiments of the present disclosure;

[0010] Figure 2 illustrating exemplary timing relationships in a wireless communication system according to some embodiments of the present disclosure;

[0011] Figure 3 A flowchart illustrating an exemplary procedure for determining a TA value according to some embodiments of the present disclosure;

[0012] Figure 4 A flowchart illustrating an exemplary procedure for selecting a TA value according to some embodiments of the present disclosure;

[0013] Figure 5 Describing an exemplary periodic TA value selection scheme according to some embodiments of the present disclosure;

[0014] Figure 6 A flowchart illustrating an exemplary procedure for selecting a TA value according to some embodiments of the present disclosure;

[0015] Figure 7 Describe an exemplary TA value selection scheme according to some embodiments of the present disclosure;

[0016] Figure 8 A flowchart illustrating an exemplary procedure for determining a TA value according to some embodiments of the present disclosure; and

[0017] Fig. 9 A block diagram illustrating an exemplary apparatus according to some embodiments of the present disclosure. DETAILED DESCRIPTION

[0018] The detailed description of the drawings is intended as a description of the preferred embodiments of the present disclosure and is not intended to represent the only form in which the present disclosure can be practiced. It should be understood that the same or equivalent functions can be achieved by different embodiments that are intended to be encompassed within the spirit and scope of the present disclosure.

[0019] Reference will now be made in detail to some embodiments of the present disclosure, examples of which are illustrated in the accompanying drawings. To facilitate understanding, embodiments are provided under specific network architectures and new service cases, such as 3rd Generation Partnership Project (3GPP) 5G (NR), 3GPP Long Term Evolution (LTE), etc. It is contemplated that all embodiments in the present disclosure are also applicable to similar technical problems as network architectures and new service cases evolve; and in addition, the terms cited in the present disclosure may be changed, which should not affect the principles of the present disclosure.

[0020] Figure 1 is a schematic diagram illustrating an exemplary wireless communication system 100 according to some embodiments of the present disclosure.

[0021] like Figure 1 As shown in FIG. 1 , wireless communication system 100 may include a base station (eg, BS 110), some IAB nodes (eg, IAB node 120A, IAB node 120B, IAB node 120C, and IAB node 120D), and a UE (eg, UE 130). Figure 1 A specific number of UEs, IAB nodes, and BSs are depicted in FIG. 1 , but it is contemplated that any number of UEs, IAB nodes, and BSs may be included in the wireless communication system 100 .

[0022] UE 130 may be any type of device configured to operate and / or communicate in a wireless environment. For example, UE 130 may include a computing device, such as a desktop computer, a laptop computer, a personal digital assistant (PDA), a tablet computer, a smart TV (e.g., a TV connected to the Internet), a set-top box, a game console, a security system (including a security camera), a vehicle-mounted computer, a network device (e.g., a router, a switch, and a modem), or the like. According to some embodiments of the present disclosure, UE 130 may include a portable wireless communication device, a smart phone, a cellular phone, a flip phone, a device with a user identity module, a personal computer, a selective call receiver, or any other device capable of sending and receiving communication signals on a wireless network. In some embodiments of the present disclosure, UE 130 may include a wearable device, such as a smart watch, a fitness bracelet, an optical head-mounted display, an Internet of Things (IoT) device, or the like. In addition, UE 130 may be referred to as a subscriber unit, a mobile device, a mobile station, a user, a terminal, a mobile terminal, a wireless terminal, a fixed terminal, a subscriber station, a user terminal, or a device, or described using other terms used in the art.

[0023] BS 110 can communicate with the core network ( Figure 1 The core network (CN) may include multiple core network components, such as a mobility management entity (MME) ( Figure 1 not shown) or Access and Mobility Management Function (AMF) ( Figure 1 The CN can be used to provide UE with access to the Public Switched Telephone Network (PTSN) and / or other networks ( Figure 1 Gateway (not shown).

[0024] The wireless communication system 100 may be compatible with any type of network capable of sending and receiving wireless communication signals. For example, the wireless communication system 100 is compatible with a wireless communication network, a cellular telephone network, a network based on time division multiple access (TDMA), a network based on code division multiple access (CDMA), a network based on orthogonal frequency division multiple access (OFDMA), an LTE network, a network based on 3GPP, a 3GPP 5G network, a satellite communication network, a high altitude platform network, and / or other communication networks.

[0025] It should be understood by those skilled in the art that, as technology develops and advances, the terms described in the present disclosure may change, but should not affect or limit the principle and spirit of the present disclosure.

[0026] refer to Figure 1 , the IAB node 120A may be directly connected to the BS 110. The IAB node 120B may reach the BS 110 by hopping through the IAB node 120A. The IAB node 120A is a parent IAB node of the IAB node 120B. In other words, the IAB node 120B is a child IAB node of the IAB node 120A.

[0027] The IAB node 120C can reach the BS 110 by jumping through the IAB node 120B and the IAB node 120A. The IAB node 120D can reach the BS 110 by jumping through the IAB node 120C, the IAB node 120B, and the IAB node 120A. The IAB node 120A and the IAB node 120B can be upstream IAB nodes of the IAB node 120C, and the IAB node 120B can be the parent IAB node of the IAB node 120C. The IAB node 120A, the IAB node 120B, and the IAB node 120C can be the upstream IAB node of the IAB node 120D, and the IAB node 120C can be the parent IAB node of the IAB node 120D. The IAB node 120B, the IAB node 120C, and the IAB node 120D can be the downstream IAB node of the IAB node 120A. The IAB node 120C and the IAB node 120D may be downstream IAB nodes of the IAB node 120B. The IAB node 120D may be a downstream IAB node of the IAB node 120C.

[0028] User equipment (UE) 130 may be connected to IAB node 120D. In other words, UE 130 may be served by IAB node 120D. IAB node 120B, IAB node 120C, IAB node 120D, and UE 130 may be downstream nodes of IAB node 120A. IAB node 120C, IAB node 120D, and UE 130 may be downstream nodes of IAB node 120B.

[0029] According to some other embodiments of the present disclosure, each of the BS 110, the IAB node 120A, the IAB node 120B, the IAB node 120C, and the IAB node 120D may be directly connected to one or more UEs. According to some other embodiments of the present disclosure, each of the BS 110, the IAB node 120A, the IAB node 120B, the IAB node 120C, and the IAB node 120D may be directly connected to one or more IAB nodes.

[0030] Each of the IAB node 120A, IAB node 120B, IAB node 120C, and IAB node 120D may include a distributed unit (DU) and a mobile terminal (MT). In the context of the present disclosure, MT is referred to as a function residing in an IAB node of a radio interface layer that terminates a backhaul Uu interface toward an IAB donor or other IAB nodes. An IAB node may be connected to an upstream IAB node or BS (e.g., an IAB donor) via the MT function. An IAB node may be connected to a UE and a downstream IAB node via a DU.

[0031] In an IAB deployment such as the wireless communication system 100, a BS (e.g. Figure 1 The BS 110 in FIG. 110 may also be referred to as an IAB donor or donor node. Figure 1 A radio link between a BS 110 in a wireless communication network and an IAB node or between two IAB nodes may be referred to as a backhaul link (BL). Figure 1 The radio link between the BS 110 in the example and the UE or between the IAB node and the UE may be referred to as an access link (AL). Figure 1 , radio links 140-0 to 140-3 are BL, and radio link 150 is AL.

[0032] exist Figure 1In the wireless communication system 100 of FIG. 1 , the IAB node 120A needs to support the following links: downlink (DL) reception (Rx) from the BS 110 via the link 140-0, uplink (UL) transmission (Tx) to the BS 110 via the link 140-0; and UL Rx from the child IAB node 120B via the link 140-1, and DL Tx to the child IAB node 120B via the link 140-1. Similarly, the IAB node 120B needs to support the following links: DL Rx from the parent IAB node 120A via the link 140-1, and UL Tx to the parent IAB node 120A via the link 140-1; and UL Rx from the child IAB node 120C via the link 140-2, and DL Tx to the child IAB node 120C via the link 140-2. The IAB node 120C needs to support the following links: DL Rx from the parent IAB node 120B via link 140-2, UL Tx to the parent IAB node 120B via link 140-2; and UL Rx from the child IAB node 120D via link 140-3, DL Tx to the child IAB node 120D via link 140-3.

[0033] The RANP objectives of the 3GPP Release 17 (R17) IAB Work Item Description (WID) include:

[0034] -Duplex Enhancement [RAN1-led, RAN2, RAN3, RAN4]:

[0035] Enhanced specification of resource multiplexing between child and parent links of IAB nodes, including:

[0036] o Supporting simultaneous operation (transmission and / or reception) of child and parent links (i.e., MT Tx / DU Tx, MT Tx / DU Rx, MT Rx / DU Tx, MT Rx / DU Rx) of an IAB node.

[0037] o Support of dual connectivity scenarios defined by RAN2 / RAN3 in the context of topology redundancy to improve robustness and load balancing.

[0038] • IAB node timing modes to support simultaneous operation (transmission and / or reception) by child and parent links of an IAB node, extensions for DL / UL power control, and specification of cross-link interference (CLI) and interference measurements for BH links, as required.

[0039] Regarding IAB node synchronization and timing alignment, seven different TX and RX timing configurations for different links are considered in 3GPP TR 38.874 (i.e., case #1 to case #7). The method and apparatus according to the embodiments of the present application are related to the following three cases:

[0040] Case #1 involves DL transmission timing alignment across IAB nodes and IAB donors. If DL Tx and UL Rx are not well aligned at the parent node, the child node needs additional information about the alignment to correctly set its DL TX timing for over-the-air (OTA) timing and synchronization.

[0041] Case #6 involves DL transmission timing aligned across IAB nodes and IAB donors and UL transmission timing aligned within an IAB node. DL transmission timing for all IAB nodes is aligned with the parent IAB node or donor DL ​​timing. UL transmission timing of an IAB node may be aligned with DL transmission timing of an IAB node.

[0042] Case #7 involves DL transmission timing alignment across IAB nodes and IAB donors and UL reception timing aligned within an IAB node. DL transmission timing for all IAB nodes is aligned with the parent IAB node or donor DL ​​timing. UL reception timing of an IAB node may be aligned with DL reception timing of an IAB node. If DL TX and UL RX are not well aligned at the parent node, the child node needs additional information about the alignment to correctly set its DL TX timing for OTA-based timing and synchronization.

[0043] All three of the above configurations involve synchronized DL transmissions across the nodes, making the network appear synchronized to the UE. Below is an overview of the three timing cases:

[0044] 1) Case #1 Timing

[0045] · Align the DL Tx of the sublink with the DL Tx of the parent link

[0046] οThe presence of T_delta is considered to be aligned

[0047] · Alignment of the UL Rx of the sub-link with the DL Tx of the sub-link

[0048] Can be used for time division multiplexing (TDM) among different hops

[0049] 2) Case #6 Timing

[0050] · The DL Tx of the sub-link is consistent with the parent link (e.g. Figure 1 DL Tx alignment of link 140-1)

[0051] · Alignment of the UL Tx of the sub-link with the DL Tx of the sub-link

[0052] o can be used for sub-links (e.g. Figure 1 Link 140-2 in Figure 1Space division multiplexing (SDM) and / or frequency division multiplexing (FDM) between links 140-3) in

[0053] 3) Case #7 Timing

[0054] · Align the DL Tx of the sublink with the DL Tx of the parent link

[0055] · Alignment of the UL Rx of the sublink with the DL Rx of the parent link

[0056] Can be used for sub-links (e.g. Figure 1 140-2) and the parent link (e.g. Figure 1 SDM and / or FDM between links 140-1) in

[0057] Regarding the indication of the “T_delta” value, NR Release 16 (R16) specifies: “In order to increase the DL TX timing of the IAB node by setting the DL TX timing of the IAB node to be earlier than its DL Rx timing (T A / 2+T_delta) to align the DL TX timing of the IAB node with that of the parent node, T_delta should be set at the parent node to (-1 / 2) of the time interval between the start of UL RX frame i and the start of DL TX frame i of the IAB node.

[0058] Of the three cases above, case #1 is specified in NR R16. Case #6 and case #7 will be supported in NR Release 17 (R17) to support SDM / FDM in different hops in the IAB network. Embodiments of the present application provide solutions to support the above timing cases. Some embodiments of the present application provide methods and devices for determining the timing advance (TA) value in the above three cases. Some embodiments of the present application provide methods and devices for selecting or indicating the TA value. More details about the embodiments of the present disclosure will be described in the following text in combination with the accompanying drawings.

[0059] Figure 2 An exemplary timing relationship in a wireless communication system according to some embodiments of the present disclosure is described. For example, Figure 2 The timing relationships shown in can be applied to Figure 1 The wireless communication system 100 in FIG. Figure 2 The timing relationship in the can determine the different timing conditions such as Figure 1 TA value of link 140-2 shown in FIG.

[0060] refer to Figure 2, case #1, case #6, and case #7 are not adopted at block 210. In this case, assuming that the IAB node 120A performs a DL transmission via the link 140-1 at time T0 (e.g., “① DL Tx performed by the IAB node 120A via the link 140-1” in block 210), the IAB node 120B may receive the DL transmission after the propagation delay (PA_1,2) of the link 140-1 (e.g., “② DL Rx performed by the IAB node 120B via the link 140-1” in block 210). In order to align the UL reception and DL transmission performed by the IAB node 120A via the link 140-1, the transition time may be considered. For example, if Figure 2 As shown in FIG. 2 , UL reception by IAB node 120A may start at T0-2×(-T_delta) (e.g., “③ UL Rx by IAB node 120A via link 140-1” in block 210). UL transmission by IAB node 120B via link 140-1 may start at T0+PA_1,2-TA_1,2 (e.g., “④ UL Tx by IAB node 120B via link 140-1” in block 210). TA_1,2 may represent a timing advance value between IAB node 120A and IAB node 120B.

[0061] In all three cases, namely, case #1, case #6 and case #7, the DL transmissions at the IAB nodes are aligned. Figure 2 , "① DL Tx performed by IAB node 120A via link 140-1" in block 210, "⑤ DL Tx performed by IAB node 120B via link 140-2" in block 220, and " The DL Tx" performed by the IAB node 120C via the link 140-3 is aligned.

[0062] Due to the propagation delay (PA_2,3) of link 140-2, IAB node 120C may receive a DL transmission from IAB node B after the propagation delay (PA_2,3) of link 140-2 (eg, "⑥ DL Rx by IAB node 120C via link 140-2" in block 220).

[0063] In case #1, the UL reception at the IAB node is aligned with the DL transmission at the IAB node. Figure 2, "⑤ DL Tx performed by IAB node 120B via link 140-2" in block 220 and "⑧ UL Rx performed at IAB node 120B via link 140-2 for case #1" in block 230 are aligned by taking the transition time into account. For example, UL reception performed by IAB node 120B via link 140-2 may start at T0-2×(-T_delta_2,3). The timing advance value between IAB node 120B and IAB node 120C in case #1 may be represented by TA_2,3,1. Therefore, at "⑨ UL Tx performed by IAB node 120C via link 140-2 for case #1" in block 230, TA_2,3,1 may be determined by the following equation (1):

[0064] TA_2,3,1=2×PA_2,3+2×(-T_delta_2,3) (1)

[0065] According to equation (1), TA_2,3,1 contains the effects of both PA_2,3 and T_delta_2,3. In NR R15, TA_2,3,1 may be indicated in a random access response (RAR) and a medium access control (MAC) control element (CE). As mentioned above, PA_2,3 is the propagation delay between the IAB node 120B and the IAB node 120C of the link 140-2. T_delta_2,3 may be the T_delta value indicated in the medium access control (MAC) control element (CE) to indicate the timing difference between the DL Tx and UL Rx at the IAB node 120B of the link 140-2. According to the NR R16 protocol, T_delata_2,3=DL Tx timing at the IAB node 120B of the link 140-2-UL Rx timing at the IAB node 120B. Although TA_2,3,1 is affected by PA_2,3 and T_delta_2,3, only a single TA value TA_2,3,1 is indicated to determine the UL Tx timing for case #1. Therefore, the TA value used to determine the UL Tx timing in case #1 may be based on the mechanism specified in NR R15.

[0066] In case #6, the UL transmission at the IAB node is aligned with the DL transmission at the IAB node (as well as the DL transmission at the upstream and downstream IAB nodes). Figure 2, "⑤DL Tx performed by IAB node 120B via link 140-2" in block 220 and "⑦UL Tx performed by IAB node 120C via link 140-2 for case #6" in block 220 are aligned. In this example, no conversion time is required. The timing advance value between IAB node 120B and IAB node 120C in case #6 can be represented by TA_2,3,6. Therefore, at "⑦UL Tx performed by IAB node 120C via link 140-2 for case #6" in block 220, TA_2,3,6 can be determined by the following equation (2):

[0067] TA_2,3,6=PA_2,3=TA_2,3,1 / 2+T_delta_2,3 (2)

[0068] As explained above, in case #6, the UL Tx timing of link 140-2 (i.e., UL Tx at IAB node 120C) is the same as the DL Tx timing of IAB node 120C, and is also the same as the DL Tx timing of IAB node 120B, so the TA value may be determined by the TA value of link 140-2 and the T_delta value of link 140-2. The necessary signaling is the same in NR R16 as the DL Tx timing determination for case #1. Therefore, the TA value used to determine the UL Tx timing in case #6 may be based on the mechanism specified in NR R16.

[0069] In case #7, the UL reception at the IAB node is aligned with the DL reception at the IAB node. Figure 2 , "② DL Rx by IAB node 120B via link 140-1" in block 210 and "⑩ UL Rx by IAB node 120B via link 140-2 for case #7" in block 240 are aligned. The timing advance value between IAB node 120B and IAB node 120C in case #7 may be represented by TA_2,3,7. Therefore, in " At UL Tx" performed by IAB node 120C via link 140-2 for case #7, TA_2,3,7 may be determined by the following equation (3):

[0070] TA_2,3,7=2×PA_2,3–PA_1,2=2×(TA_2,3,1 / 2+T_delta_2,3)–PA_1,2 (3)

[0071] In equation (3), TA_2,3,1 is the TA value introduced for link 140-2 in NR R15, and T_delta_2,3 is the T_delta value introduced for link 140-2 in NR R16. Therefore, the value PA_1,2 (i.e., the propagation delay of link 140-1) is needed for the calculation of the TA value to determine the UL Tx timing for case #7.

[0072] Therefore, in order to support case #7, in some embodiments of the present application, a child node of the IAB node (eg Figure 1 The IAB node 120C in FIG. 1 indicates an IAB node (eg, Figure 1 The parent link (eg, Figure 1 The propagation delay of the link 140-1 in the Figure 1 UL Tx timing of the IAB node 120C in.

[0073] Figure 3 A flowchart illustrating an exemplary procedure 300 for determining a TA value according to some embodiments of the present disclosure. The details described in all the foregoing embodiments of the present disclosure may be applicable to Figure 3 The process 300 may be performed by an IAB node.

[0074] refer to Figure 3 In operation 311, the IAB node (eg Figure 1 The IAB node 120C in the example may be derived from its parent node (e.g. Figure 1 The IAB node 120B in the embodiment of the present disclosure receives information related to the TA value for uplink transmission. In some embodiments of the present disclosure, the information may be received via MAC CE signaling. In operation 313, the IAB node may determine the TA value (e.g., TA_2, 3, 7) for uplink transmission based on the information.

[0075] In some embodiments of the present disclosure, the information may indicate the grandparent node (eg Figure 1 The IAB node 120A in the IAB node) and the parent node of the IAB node (eg Figure 1 The information may include a propagation delay associated with a link between an IAB node 120B in the IAB node and an IAB node 120B in the IAB node. For example, a plurality of propagation delay values ​​may be configured or predefined at the IAB node. The information may indicate a propagation delay value from the plurality of propagation delay values. The IAB node may determine a TA value for uplink transmission based on the information and the plurality of propagation delay values.

[0076] In some embodiments of the present disclosure, an IAB node (eg Figure 1 The IAB node 120C in the example may further receive a grandparent node (eg Figure 1 The IAB node 120A in the IAB node) and the parent node of the IAB node (eg Figure 1 The IAB node may further determine a TA value for uplink transmission based on the indication of the SCS.

[0077] For example, "μ = 0" may indicate an SCS of 15 kHz, "μ = 1" may indicate an SCS of 30 kHz, "μ = 2" may indicate an SCS of 60 kHz, and "μ = 3" may indicate an SCS of 120 kHz. The relationship between the propagation delay value and the SCS may be expressed as: "Propagation delay value = i × 16 × 64 / 2 μ ”, where i can be 0, 1, 2, ... or 3846 and is indicated in the received information associated with the TA value (hereinafter referred to as the “index in the information”).

[0078] In some embodiments of the present disclosure, an IAB node (eg Figure 1 The IAB node 120C in the example may implicitly determine the grandparent node of the IAB node (e.g. Figure 1 The IAB node 120A in the IAB node) and the parent node of the IAB node (eg Figure 1 In some examples, the IAB node may determine the SCS based on a frequency band associated with a link between a grandparent node of the IAB node and a parent node of the IAB node. In an example, the IAB node may determine that the SCS of frequency range 1 (FR1) is 15 kHz and the SCS of frequency range 2 (FR2) is 60 kHz. The IAB node may further determine a TA value for uplink transmission based on the determined SCS.

[0079] For example, the relationship between the propagation delay value and the SCS can be expressed as: "propagation delay value = i × 16 × 64 / 2 μ ”, where i can be 0, 1, 2, ... or 3846 and is an index in the information, and the value of μ is based on the SCS determined by the IAB node. For example, “μ=0” may indicate an SCS of 15 kHz, “μ=1” may indicate an SCS of 30 kHz, “μ=2” may indicate an SCS of 60 kHz, and “μ=3” may indicate an SCS of 120 kHz.

[0080] Based on the above description, the IAB node may determine different TA values ​​in different timing situations (eg, Figure 2, TA_2,3,1 for case #1, TA_2,3,6 for case #6, and TA_2,3,7 for case #7). Although all timing cases (i.e., corresponding to multiple TA values) may be supported in the network, a specific timing case may be adopted at a specific time instance based on, for example, scheduling decisions and traffic conditions. This means that for a specific UL transmission, the IAB node may be instructed to adopt a specific timing case. Moreover, for different timing cases, different TA value determination or selection methods may be adopted.

[0081] Embodiments of the present application further provide solutions to indicate time instances where corresponding TA values ​​are adopted. Some embodiments of the present application provide a semi-static TA value selection mechanism (also referred to as a periodic scheme). Some embodiments of the present application provide a dynamic TA value selection mechanism (also referred to as an aperiodic scheme). Both mechanisms may be used alone or in combination. More details about embodiments of the present disclosure will be described in the following text in combination with the accompanying drawings.

[0082] Figure 4 A flowchart illustrating an exemplary procedure 400 for selecting a TA value according to some embodiments of the present disclosure. The details described in all the previous embodiments of the present disclosure may be applied to Figure 4 The embodiments shown in .

[0083] refer to Figure 4 In operation 411, the IAB node (eg Figure 1 The IAB node 120C in the embodiment may receive configuration information for selecting from a plurality of TA values ​​(e.g., Figure 2 , TA_2,3,1 for case #1, TA_2,3,6 for case #6, and TA_2,3,7 for case #7) select a TA value. In operation 413, the IAB node may select a TA value to be applied to uplink transmission from a plurality of TA values ​​based on the configuration information. In some embodiments of the present application, the configuration information may be configured per cell or per TA group (TAG).

[0084] In some embodiments of the present application, the exemplary procedure 400 is associated with a semi-static TA value selection mechanism. For example, a periodic pattern may be configured for each TA value in a plurality of TA values. For example, configuration information for selecting a TA value may indicate at least one of a periodicity, an offset, and a duration for each TA value in a plurality of TA values. In some embodiments of the present application, the periodic pattern (e.g., configuration information) may be configured via RRC signaling.

[0085] In some of these embodiments, the configured TA value may only be applicable to UL transmissions within the corresponding duration (e.g., time domain resources of, for example, UL symbols). For symbols or time slots that overlap due to changes in the TA value, the previous symbol or time slot may have a higher priority. In addition, when a periodic TA value is not indicated for a time domain resource for uplink transmission, the most recent TA value may be applied at the time domain resource for uplink transmission.

[0086] Figure 5 An exemplary periodic TA value selection scheme 500 according to some embodiments of the present disclosure is described. The details described in all the above embodiments of the present disclosure are applicable to Figure 5 The embodiment shown in Figure 5 In the example, it is assumed that the SCS is 15kHz. It should be understood by those skilled in the art that the SCS can be any other supported value.

[0087] refer to Figure 5 , the IAB node may support three TA values ​​for UL transmission. In some examples, the three TA values ​​may be TA_1 = 20 μs for case #1 UL Tx timing, TA_2 = 10 μs for case #6 UL Tx timing, and TA_3 = -5 μs for case #7 UL Tx timing. The IAB node may be configured with a corresponding periodic pattern for each TA value.

[0088] For example, the IAB node may be configured with pattern_1 for TA_1, pattern_2 for TA_2, and pattern_3 for TA_3. Figure 5 As shown at 510, pattern_1 for TA_1 may have a periodicity of 40ms, an offset of 0ms, and a duration of 20ms. pattern_2 for TA_2 may have a periodicity of 40ms, an offset of 20ms, and a duration of 5ms. pattern_3 for TA_3 may have a periodicity of 40ms, an offset of 25ms, and a duration of 10ms.

[0089] In this configuration, for every 40 ms, 0 to 19 ms of the corresponding 40 ms may be associated with case #1 and may be used, for example, for TDM between link 140-1 and link 140-2, such as Figure 1 corresponding 40ms 20ms to 24ms may be associated with case # 6, and may be used, for example, for SDM / FDM between link 140-2 and link 140-3, such as Figure 1 and 25ms to 34ms of the corresponding 40ms may be associated with case #7 and may be used for SDM / FDM between link 140-1 and link 140-2.

[0090] For a duration of 35 to 39 ms corresponding to 40 ms (e.g., Figure 5 At 501 in the UL), the TA value of the UL transmission may be based on a default TA value (e.g., one or another TA value supported by the IAB node) or a recent TA value, or may be determined based on aperiodic signaling as described in the text below. For example, the default TA value may be one of the TA values ​​supported by the IAB node. Figure 5 In the example, the most recent TA value may be TA_3.

[0091] In this way, the IAB node will know the TA value to be applied for UL transmission. Figure 5 As shown in FIG. 1 , pattern_1 is configured for slot 0 to slot 4. Therefore, for UL symbols in slot 0 to slot 4, the IAB node may adopt TA_1 (eg, UL Tx timing is 20 μs for case #1).

[0092] Return to reference Figure 4 In some embodiments of the present application, the exemplary procedure 400 is associated with a dynamic TA value selection mechanism. In some embodiments of the present application, the dynamic TA value selection mechanism can only be applied to time domain resources when no periodic TA value is indicated for the time domain resources.

[0093] In some examples, the IAB node may receive configuration information for selecting a TA value via RRC signaling or MAC CE signaling. In the case where three timing cases are supported at the IAB node, 2 bits may be included in the RRC signaling or MAC CE signaling to indicate one of the three timing cases (e.g., three TA values). In some embodiments of the present application, the indicated or selected TA value may be applied after an application delay indicated by the RRC signaling or MAC CE signaling.

[0094] In some other examples, the IAB node may receive configuration information for selecting a TA value via group common downlink control information (DCI) (e.g., DCI format 2_0, DCI format 2_5, etc.). In these examples, in some embodiments of the present application, the indicated or selected TA value may be applied at the same time slot as the group common DCI. In some other embodiments of the present application, the IAB node may receive RRC signaling or MAC CE signaling, and may apply the selected TA value after an application delay indicated by the RRC signaling or MAC CE signaling.

[0095] In some embodiments of the present application, the configuration information may be indicated by a reserved time slot format index in a group common DCI. For example, in a group common DCI, 8 bits may be allocated for indicating a time slot format index, and thus 2 8(256) slot formats. However, only a portion (e.g., 56) of the 256 slot format indices may be standardized, and the remaining slot format indices are reserved. Some of these reserved slot format indices may be used to indicate timing situations (e.g., TA values). In the case where three timing situations are supported at the IAB node, three slot format indices may be used to indicate one of the three timing situations (e.g., three TA values).

[0096] In some other embodiments of the present application, the IAB node may receive RRC signaling indicating a position in the group common DCI. The position may be the starting position of the bits of the configuration information in the group common DCI. For example, the configuration information may include 2 bits for indicating one of three timing conditions (e.g., three TA values), and the position indicated in the RRC signaling may indicate the position of the 2 bits in the DCI.

[0097] In yet other examples, the IAB node may receive configuration information for selecting a TA value via a UE-specific DCI (or dynamic DCI, such as DCI format 0_0, DCI format 0_1, and DCI format 0_2). In some embodiments of the present application, a dedicated (new) field in the UE-specific DCI may be used to indicate one of multiple TA values. In the case where three timing cases are supported at the IAB node, a 2-bit dedicated field in the DCI may be used to indicate one of the three timing cases (e.g., three TA values).

[0098] In these examples, in some embodiments of the present application, the IAB node may apply the indicated or selected TA value after a delay indicated by the UE-specific DCI. When an uplink transmission scheduled by the UE-specific DCI precedes the application of the indicated TA value, the IAB node may apply the most recent TA value for the uplink transmission scheduled by the UE-specific DCI. In some embodiments of the present application, the IAB node may apply the indicated TA value at the time domain resource when a periodic TA value is not indicated for the time domain resource.

[0099] In some embodiments of the present application, the configuration information may be indicated by a time domain resource allocation field (or time domain resource assignment field) in a UE-specific DCI. A new column may be added to the time domain resource allocation table to indicate the TA selection.

[0100] For example, Table 1 below shows an exemplary time domain resource allocation table from the 3GPP specification for NR systems. Table 1A below shows a table updated by adding a new column to indicate TA selection in an IAB network. It should be understood that Tables 1 and 1A are for illustrative purposes only and should not be construed as limiting embodiments of the present disclosure.

[0101] Table 1: Default physical uplink shared channel (PUSCH) time domain resource allocation for normal cyclic prefix (CP) A

[0102]

[0103] Table 1A: Default PUSCH time domain resource allocation for normal CP A

[0104]

[0105] Compared with Table 1, the last column on the right side of Table 1A indicates the TA type related to TA selection at the IAB node. The time domain resource allocation field in the DCI may correspond to the row index in the above two tables. For example, the time domain resource allocation field indicating "0111" corresponds to the row index "8". 2 Refers to the delay between the physical downlink control channel (PDCCH) and the scheduled PUSCH, and j is determined by the SCS. For example, when the SCS is 15kHz, the value of j is "1". In this case, when the row index is "8", K2=j+1=2. The PUSCH mapping type indicates whether the PUSCH mapping starts from the time slot boundary. Type A means that it starts from the time slot boundary, and type B means that it can start at any symbol. For example, when the row index is "8", the PUSCH mapping starts from the time slot boundary. S corresponds to the starting position of the PUSCH. For example, when the row index is "8", the starting position of the PUSCH is symbol #0, that is, the time slot boundary. L corresponds to the length of the PUSCH, for example, how many symbols are occupied by the PUSCH. For example, when the row index is "8", the length of the PUSCH is 14 symbols. In Table 1A, the TA type indicates the TA value to be adopted at the IAB node. For example, when the row index is "8", the IAB node may adopt the TA value associated with case #1, e.g. Figure 2 TA_2,3,1 shown in the figure.

[0106] In some embodiments of the present application, the configuration information may be indicated by a bandwidth part (BWP) indicator field in a UE-specific DCI. For example, the TA selection and the BWP indicator may be encoded together. Different BWPs may be associated with different TA values. The reason is that when FDM is employed between adjacent hops, BWP selection restrictions may be necessary.

[0107] For example, Table 2 below shows an exemplary BWP indicator table from the 3GPP specification for NR systems. Table 2A below shows a BWP indicator table enhanced by adding a new column to indicate TA selection in an IAB network. In this way, the BWP indicator field can indicate both the BWP ID and the TA type. It should be understood that Tables 2 and 2A are for illustrative purposes only and should not be construed as limiting embodiments of the present disclosure.

[0108] Table 2: Bandwidth fraction indicators

[0109]

[0110] Table 2A: Bandwidth Partial Indicators

[0111]

[0112] Compared to Table 2, the last column on the right side of Table 2A indicates the TA type associated with TA selection at the IAB node. The BWP indicator indicates on which BWP the scheduled PUSCH is transmitted. For example, in both tables, when the BWP indicator indicates "01", the scheduled PUSCH should be transmitted on the BWP with BWP ID "2". In Table 2A, when the BWP indicator indicates "01", the IAB node can adopt the TA value associated with case #1, such as Figure 2 TA_2,3,1 shown in the figure.

[0113] In some embodiments of the present application, the configuration information may be indicated by the antenna port field in the UE-specific DCI. For example, TA selection and demodulation reference signal (DMRS) port index may be co-encoded. The reason is that when SDM is adopted between adjacent hops, DMRS port selection restrictions may be necessary.

[0114] For example, Tables 3, 4, 5, and 6 below show exemplary antenna port tables from the 3GPP specification for NR systems. Tables 3A, 4A, 5A, and 6A below show antenna port tables enhanced by adding new columns to indicate TA selection in IAB networks, respectively. In this way, the antenna port field can indicate both the DMRS port and the TA type. It should be understood that the following tables are for illustrative purposes only and should not be construed as limiting the embodiments of the present disclosure.

[0115] Table 3: Antenna port, transform precoder disabled, dmrs-Type=1, maxLength=2, rank=1

[0116] value Number of DMRS CDM groups without data DMRS Port Number of leading symbols 0 1 0 1 1 1 1 1 2 2 0 1 3 2 1 1 4 2 2 1 5 2 3 1 6 2 0 2 7 2 1 2 8 2 2 2 9 2 3 2 10 2 4 2 11 2 5 2 12 2 6 2 13 2 7 2 14 to 15 reserve reserve reserve

[0117] Table 4: Antenna port, transform precoder disabled, dmrs-Type=1, maxLength=2, rank=2

[0118] value Number of DMRS CDM groups without data DMRS Port Number of leading symbols 0 1 0,1 1 1 2 0,1 1 2 2 2,3 1 3 2 0,2 1 4 2 0,1 2 5 2 2,3 2 6 2 4,5 2 7 2 6,7 2 8 2 0,4 2 9 2 2,6 2 10 to 15 reserve reserve reserve

[0119] Table 5: Antenna port, transform precoder disabled, dmrs-Type=1, maxLength=2, rank=3

[0120] value Number of DMRS CDM groups without data DMRS Port Number of leading symbols 0 2 0 to 2 1 1 2 0,1,4 2 2 2 2,3,6 2 3 to 15 reserve reserve reserve

[0121] Table 6: Antenna port, transform precoder disabled, dmrs-Type=1, maxLength=2, rank=4

[0122] value Number of DMRS CDM groups without data DMRS Port Number of leading symbols 0 2 0 to 3 1 1 2 0,1,4,5 2 2 2 2,3,6,7 2 3 2 0,2,4,6 2 4 to 15 reserve reserve reserve

[0123] Table 3A: Antenna port, transform precoder disabled, dmrs-Type=1, maxLength=2, rank=1

[0124]

[0125] Table 4A: Antenna port, transform precoder disabled, dmrs-Type=1, maxLength=2, rank=2

[0126]

[0127] Table 5A: Antenna port, transform precoder disabled, dmrs-Type=1, maxLength=2, rank=3

[0128]

[0129] Table 6A: Antenna port, transform precoder disabled, dmrs-Type=1, maxLength=2, rank=4

[0130]

[0131] Compared with Tables 3, 4, 5 and 6, the last column on the right side of Tables 3A, 4A, 5A and 6A, respectively, indicates the TA type related to TA selection at the IAB node. In the above table, "DMRS port" refers to the DMRS port adopted by the scheduled PUSCH. "Number of preamble symbols" indicates whether the preamble DMRS (e.g., the first DMRS) occupies one or two symbols. "Number of DMRS CDM groups without data" indicates the number of code division multiplexing (CDM) groups without any PUSCH on the time domain resources corresponding to the DMRS.

[0132] Figure 6 A flowchart illustrating an exemplary procedure 600 for selecting a TA value according to some embodiments of the present disclosure. The details described in all the previous embodiments of the present disclosure may be applied to Figure 6 The embodiments shown in .

[0133] refer to Figure 6 In operation 611, the IAB node (eg Figure 1The IAB node 120C in the embodiment may receive a UE-specific DCI. The UE-specific DCI may be scrambled by a radio network temporary identifier (RNTI). In operation 613, the IAB node may select a TA value (e.g., Figure 2 , TA_2,3,1 for case #1, TA_2,3,6 for case #6, and TA_2,3,7 for case #7) select the TA value to be applied to uplink transmission. In some embodiments of the present application, the configuration information may be configured per cell or per TA group (TAG).

[0134] In some embodiments of the present application, the selected TA value may be applied after a delay indicated by the UE-specific DCI. When an uplink transmission scheduled by the UE-specific DCI precedes the application of the selected TA value, the IAB node may apply the most recent TA value for the uplink transmission scheduled by the UE-specific DCI. In some embodiments of the present application, the IAB node may apply the selected TA value at the time domain resource when a periodic TA value is not indicated for the time domain resource.

[0135] Figure 7 An exemplary non-periodic TA value selection scheme 700 according to some embodiments of the present disclosure is illustrated. The details described in all the above embodiments of the present disclosure are applicable to Figure 7 The embodiment shown in Figure 7 In the example, it is assumed that the SCS is 15kHz. It should be understood by those skilled in the art that the SCS can be any other supported value.

[0136] refer to Figure 7 , IAB nodes (e.g. Figure 1 The IAB node 120C in FIG. 1 may support three TA values ​​for UL transmission. In some examples, the three TA values ​​may be TA_1 = 20 μs for case #1 UL Tx timing, TA_2 = 10 μs for case #6 UL Tx timing, and TA_3 = -5 μs for case #7 UL Tx timing. The IAB node may be configured with a corresponding periodic pattern for each TA value.

[0137] For example, the IAB node may be configured with pattern_1 for TA_1, pattern_2 for TA_2, and pattern_3 for TA_3. Figure 5As shown at 510, pattern_1 for TA_1 may have a periodicity of 40ms, an offset of 0ms, and a duration of 20ms. pattern_2 for TA_2 may have a periodicity of 40ms, an offset of 20ms, and a duration of 5ms. pattern_3 for TA_3 may have a periodicity of 40ms, an offset of 25ms, and a duration of 10ms.

[0138] In this configuration, for every 40 ms, 0 to 19 ms of the corresponding 40 ms may be associated with case #1 and may be used, for example, for TDM between link 140-1 and link 140-2, such as Figure 1 corresponding 40ms 20ms to 24ms may be associated with case # 6, and may be used, for example, for SDM / FDM between link 140-2 and link 140-3, such as Figure 1 and 25ms to 34ms of the corresponding 40ms may be associated with case #7 and may be used for SDM / FDM between link 140-1 and link 140-2.

[0139] For a duration of 35 to 39 ms corresponding to 40 ms (e.g., Figure 7 701 in the above), the IAB node may be based on Figure 4 and 6 The described aperiodic TA value indication signaling determines the TA value used for UL transmission.

[0140] In some embodiments of the present application, the IAB node may apply the determined TA value after a delay indicated by the UE-specific DCI. In these embodiments, when an uplink transmission scheduled by the UE-specific DCI precedes the application of the determined TA value, the IAB node may apply the most recent TA value for the uplink transmission scheduled by the UE-specific DCI.

[0141] For example, in some examples, the IAB node may use the scheduling delay in the UE-specific DCI as the delay for the determined TA value. Figure 7 , assuming that a UE-specific DCI indicating TA_2 is detected in time slot 35 at 711, and the UE-specific DCI indicates a delay 715 (e.g., scheduling delay = 2 time slots + 13 symbols), the IAB node may adopt TA_2 for UL transmission at 717.

[0142] In some other examples, the delay for the determined TA value may be different from the scheduled delay. Figure 7, the UE-specific DCI detected at 711 may indicate a delay 723 for scheduling PUSCH (e.g., scheduling delay = 8 symbols) and a delay 715 for the determined TA value (e.g., application delay = 2 slots + 13 symbols). In this example, the IAB node will not adopt TA_2 indicated in the UE-specific DCI for UL transmission at 713 because TA_2 is not applicable according to the delay for the determined TA value until 717. Instead, the IAB node will adopt the latest TA value (e.g., TA_3) for UL transmission at 713.

[0143] In some embodiments of the present application, the IAB node may apply the determined TA value at the same time slot as the group common DCI. Figure 7 , assuming that a group common DCI indicating TA_3 is detected at 719, the IAB node may adopt TA_3 for UL transmission in time slot 39. Figure 7 In the example of , the UL symbol in slot 39 starts at 721 (eg, symbol 8 of slot 39), and therefore, TA_3 is adopted at 721. In some embodiments of the present application, additional RRC signaling or MACCE signaling may be used to indicate the application delay of the TA value indicated in the group common DCI.

[0144] In some embodiments of the present application, when no periodic TA value is indicated for a time domain resource used for uplink transmission, a latest TA value (periodic or aperiodic TA indication) may be applied at the time domain resource used for uplink transmission.

[0145] For example, refer to Figure 7 , the aperiodic TA indication at 711 may indicate that TA_2 is applied for UL transmission at 713. No aperiodic or periodic TA value indication may be applied for UL transmission at 717. In this case, the IAB node will adopt the most recent TA value (e.g., TA_2) for UL transmission at 717.

[0146] In some other embodiments of the present disclosure, aperiodic TA value indication signaling may be applicable to time domain resources with periodic TA value indication. In these embodiments, aperiodic TA value indication may have a higher priority than periodic TA value indication.

[0147] In some other embodiments of the present disclosure, aperiodic TA value indication signaling may not be applied to time domain resources without periodic TA value indication. In these embodiments, the most recent TA value may be applied to time domain resources used for uplink transmission. For example, assuming that Figure 7In the time slots 35 to 39 shown in FIG. 4 , no non-periodic TA value indication signaling is applied to UL transmission resources, then the IAB node may adopt TA_3 for UL symbols at 713 , 717 , and 721 .

[0148] Figure 8 A flowchart illustrating an exemplary procedure 800 for determining a TA value according to some embodiments of the present disclosure. The details described in all the foregoing embodiments of the present disclosure may be applicable to Figure 8 The process 800 may be performed by an IAB node.

[0149] refer to Figure 8 In operation 811, the IAB node (eg Figure 1 The IAB node 120B in FIG. 1 may transmit information related to the TA value for uplink transmission to its child nodes (eg, Figure 1 In some embodiments of the present disclosure, the information may be transmitted via MAC CE signaling.

[0150] In some embodiments of the present disclosure, the information may indicate a propagation delay associated with a link between the IAB node and the parent node of the IAB node. In some embodiments of the present disclosure, the IAB node may further transmit an indication of an SCS associated with a link between the IAB node and the parent node of the IAB node. In some embodiments of the present disclosure, the indication of the SCS may be transmitted via RRC signaling or MAC CE signaling. Details about this indication are similar to those about Figure 3 The details of the description are therefore omitted herein.

[0151] In some embodiments of the present disclosure, procedure 800 may further include operation 813 (indicated by a dashed box as an option). In operation 813, the IAB node may transmit configuration information to its child node. The configuration information may be used to select a TA value to be applied to uplink transmission at the child node from a plurality of TA values.

[0152] The configuration information may be associated with an aperiodic TA indication or a periodic TA indication. Figures 4 to 7 The details of the described aperiodic TA indication and periodic TA indication may be applicable here. For example, in some embodiments of the present disclosure, the configuration information may be configured per cell or per TA group (TAG).

[0153] In some embodiments of the present disclosure, the configuration information may indicate at least one of the periodicity, offset, and duration of each TA value in the plurality of TA values. The configuration information may be transmitted via RRC signaling.

[0154] In some embodiments of the present disclosure, the configuration information may be transmitted via RRC signaling or MAC CE signaling.

[0155] In some embodiments of the present disclosure, the configuration information may be transmitted via a group common DCI. In some instances, the configuration information may be indicated by a reserved slot format index in the group common DCI. In some instances, the IAB node may further transmit RRC signaling indicating a position in the group common DCI. The position may indicate the starting position of a bit of the configuration information in the group common DCI.

[0156] In some embodiments of the present disclosure, the configuration information may be transmitted via a UE-specific DCI. In some instances, the configuration information may be included in a dedicated field in the UE-specific DCI. In some instances, the configuration information may be indicated by a time domain resource allocation field in the UE-specific DCI. In some instances, the configuration information may be indicated by a bandwidth part (BWP) indicator field in the UE-specific DCI. In some instances, the configuration information may be indicated by an antenna port field in the UE-specific DCI.

[0157] In some embodiments of the present disclosure, procedure 800 may not include operation 813. The IAB node may transmit UE-specific DCI scrambled by RNTI to its child nodes. The RNTI may be associated with a TA value among a plurality of values ​​to be applied to uplink transmissions at the child nodes.

[0158] It should be understood by those skilled in the art that the sequence of operations in the above exemplary procedures may be changed and some operations in the above exemplary procedures may be exempted or modified without departing from the spirit and scope of the present disclosure.

[0159] Fig. 9 A block diagram illustrating an exemplary apparatus 900 according to some embodiments of the present disclosure.

[0160] like Fig. 9 As shown in FIG. 1 , the apparatus 900 may include at least one non-transitory computer-readable medium 901, at least one receiving circuit system 902, at least one transmitting circuit system 904, and at least one processor 906 coupled to the non-transitory computer-readable medium 901, the receiving circuit system 902, and the transmitting circuit system 904.

[0161] Although elements such as at least one processor 906, transmit circuitry 904, and receive circuitry 902 are described in the singular in this figure, the plural is contemplated unless limitation to the singular is explicitly stated. In some embodiments of the present application, receive circuitry 902 and transmit circuitry 904 are combined into a single device, such as a transceiver. In a particular embodiment of the present application, apparatus 900 may further include an input device, a memory, and / or other components.

[0162] In some embodiments of the present disclosure, the non-transitory computer-readable medium 901 may store computer-executable instructions for causing the processor to implement the method for the UE described above. For example, when the computer-executable instructions are executed, the processor 906 interacts with the receiving circuit system 902 and the transmitting circuit system 904 to perform the method for transmitting the UE in the above-described manner. Figures 1 to 8 The operation of the IAB node is depicted in FIG.

[0163] It should be understood by those of ordinary skill in the art that the operations or steps of the methods described in conjunction with the aspects disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. The software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. In addition, in some aspects, the operations or steps of the methods may reside as one or any combination or set of codes and / or instructions on a non-transitory computer-readable medium, which may be incorporated into a computer program product.

[0164] Although the present disclosure has been described with reference to specific embodiments of the present disclosure, it is apparent that many substitutions, modifications, and variations may be apparent to those skilled in the art. For example, the various components of the embodiments may be interchanged, added, or substituted in other embodiments. Moreover, all elements of each figure are not necessary for the operation of the disclosed embodiments. For example, it will enable a person of ordinary skill in the field of the disclosed embodiments to make and use the teachings of the present disclosure by simply adopting the elements of the independent claims. Therefore, the embodiments of the present disclosure set forth herein are intended to be illustrative rather than restrictive. Various changes may be made without departing from the spirit and scope of the present disclosure.

[0165] In this archive, the term "includes / including" or any other variation thereof is intended to cover non-exclusive inclusion, so that the process, method, article or equipment containing a list of elements not only contains those elements but also may contain other elements that are not explicitly listed or inherent to this process, method, article or equipment. Elements beginning with "a / an" or the like (without more constraints) do not exclude the presence of additional identical elements in the process, method, article or equipment containing the elements. Moreover, the term "another" is defined as at least a second or more. As used herein, the term "having" and the like are defined as "comprising".

Claims

1. A method for wireless communication, comprising: include: receiving, at a third node from a second node, configuration information related to a timing advance TA value for uplink transmission, wherein the second node is a parent node of the third node, wherein the configuration information indicates a period of each TA value in a plurality of TA values, each TA value in the plurality of TA values ​​corresponding to a timing configuration; and A first TA value for uplink transmission is determined from among the plurality of TA values ​​based on the configuration information. 2 . The method of claim 1 , wherein the configuration information further indicates at least one of an offset and a duration of each TA value in the plurality of TA values.

3. The method according to claim 1 or 2, wherein the configuration information is received via Radio Resource Control (RRC) signaling.

4. A device for wireless communication, wherein include: at least one non-transitory computer-readable medium having computer-executable instructions stored thereon; at least one receiving circuit system; at least one transmission circuit system; and at least one processor coupled to the at least one non-transitory computer-readable medium, the at least one receiving circuitry, and the at least one transmitting circuitry, wherein the computer executable instructions cause the at least one processor to: receiving, at a third node from a second node, configuration information related to a timing advance TA value for uplink transmission, wherein the second node is a parent node of the third node, wherein the configuration information indicates a period of each TA value in a plurality of TA values, each TA value in the plurality of TA values ​​corresponding to a timing configuration; and A first TA value for uplink transmission is determined from among the plurality of TA values ​​based on the configuration information. 5 . The apparatus of claim 4 , wherein the configuration information further indicates at least one of an offset and a duration of each TA value in the plurality of TA values.

6. The apparatus according to claim 4 or 5, wherein the configuration information is received via Radio Resource Control (RRC) signaling. 7 . The apparatus according to claim 4 , wherein the configuration information is configured per cell or per TA group (TAG) and is received via radio resource control (RRC) signaling or medium access control (MAC) control element (CE) signaling.

8. The device according to claim 4, in: The configuration information is received via group common downlink control information DCI; The configuration information is indicated by a reserved time slot format index in the group common DCI; and The computer executable instructions further cause the at least one processor to: A radio resource control (RRC) signaling or a medium access control (MAC) control element (CE) signaling is received, indicating a starting position of bits of the configuration information in the group common DCI.

9. The apparatus of claim 4, wherein the computer executable instructions further cause the at least one processor to: receiving downlink control information DCI dedicated to a user equipment UE scrambled by a radio network temporary identifier RNTI; and A TA value to be applied for uplink transmission is selected from the plurality of TA values ​​based on the RNTI.

10. The device according to claim 4, in: The configuration information is received via downlink control information (DCI) dedicated to a user equipment (UE); and the configuration information is included in a dedicated field in the UE-specific DCI.

11. The apparatus of claim 8, wherein the computer executable instructions further cause the at least one processor to: Receiving radio resource control RRC signaling or media access control MAC control element CE signaling; applying the TA value after an application delay indicated by one of the RRC signaling or the MAC CE signaling; and The TA value is applied at the same time slot as the group common DCI.

12. The apparatus of claim 8, wherein the computer executable instructions further cause the at least one processor to: When no periodic TA value is indicated for a time domain resource, the TA value is applied at the time domain resource.

13. The apparatus of claim 4, wherein the computer executable instructions further cause the at least one processor to: When no periodic TA value is indicated for a time domain resource used for uplink transmission, a latest TA value is applied at the time domain resource used for the uplink transmission.

14. The apparatus of claim 9, wherein the computer executable instructions cause the at least one processor to: Configuration information is transmitted to the third node via one of radio resource control (RRC) signaling or media access control (MAC) control element (CE) signaling, wherein the configuration information is used to select a TA value to be applied to uplink transmission at the third node from a plurality of TA values, wherein the configuration information indicates at least one of a periodicity, an offset, and a duration of each TA value in the plurality of TA values.

15. A device for wireless communication, wherein include: at least one non-transitory computer-readable medium having computer-executable instructions stored thereon; at least one receiving circuit system; at least one transmission circuit system; and at least one processor coupled to the at least one non-transitory computer-readable medium, the at least one receiving circuitry, and the at least one transmitting circuitry, wherein the computer executable instructions cause the at least one processor to: Configuration information related to a timing advance TA value for uplink transmission at a third node is transmitted from a second node to the third node, wherein the second node is a parent node of the third node, wherein the configuration information indicates a period of each TA value in a plurality of TA values, each TA value in the plurality of TA values ​​corresponding to a timing configuration.

16. The apparatus of claim 15, wherein the configuration information further indicates at least one of an offset and a duration for each TA value of the plurality of TA values.

Images