Timing alignment in integrated access and backhaul

Abstract

Apparatuses, methods, and systems are disclosed for timing alignment in integrated access and backhaul. One method includes receiving, at an integrated access and backhaul (“IAB”) node of a wireless communication network, a first configuration for receiving a downlink reference signal and a second configuration for receiving an uplink reference signal. The method includes determining timing alignment information associated with the downlink reference signal and the uplink reference signal. The method includes determining a timing misalignment value based on the timing alignment information. The method includes calculating a second reception time based on a first reception time and the timing misalignment value, the first reception time determined based on the downlink reference signal. The method includes applying the second reception time to the IAB node for receiving the uplink reference signal.

Description

[0001] Cross-reference of related applications

[0002] This application claims priority to U.S. Provisional Patent Application No. 63 / 027,252, filed May 19, 2020, entitled “Apparatus, methods, and systems for timing adjustment for cross-link interference management in integrated access and backhaul,” which is incorporated herein by reference. Technical Field

[0003] The topics disclosed in this article generally relate to wireless communication, and more specifically, to timing alignment in integrated access and backhaul. Background Technology

[0004] In some wireless communication systems, user equipment (“UE”) can connect to the fifth-generation (“5G”) core network (“5GC”) within a Public Land Mobile Network (“PLMN”). Timing errors may exist in the integrated access and backhaul processes within the wireless network. Summary of the Invention

[0005] This disclosure discloses a procedure for timing alignment in integrated access and backhaul networks. The procedure can be implemented by devices, systems, methods, and / or computer program products. This disclosure describes solutions to address the problem of obtaining timing alignment for cross-link interference in integrated access and backhaul networks. In embodiments for obtaining timing alignment to receive uplink reference signals, uplink timing acquisition is assisted by downlink timing information obtained from synchronization signals. Attached Figure Description

[0006] A more specific description of the embodiments briefly described above will be presented by referring to specific embodiments illustrated in the accompanying drawings. It should be understood that these drawings depict only some embodiments and should therefore not be considered limiting; the embodiments will be described and explained in additional particular detail using the accompanying drawings, in which:

[0007] Figure 1 This is a schematic block diagram illustrating one embodiment of a wireless communication system for timing alignment in integrated access and backhaul.

[0008] Figure 2AIt is an instance of an Integrated Access and Backhaul (IAB) system (in standalone mode) used for timing alignment in integrated access and backhaul.

[0009] Figure 2B This is a block diagram illustrating an embodiment of a summary of timing alignment in an IAB donor and DU / MT splitting in an IAB node for integrated access and backhaul.

[0010] Figure 3 This is a diagram illustrating one embodiment of a scenario for timing alignment in integrated access and backhaul;

[0011] Figure 4A This is a diagram illustrating one embodiment of the principle timing alignment used in case 1;

[0012] Figure 4B This is a diagram illustrating one embodiment of instance timing alignment for case 1;

[0013] Figure 5 This is a diagram illustrating one embodiment of a timeline used for timing alignment in application scenario 1;

[0014] Figure 6 This is a diagram illustrating one embodiment of the uplink-downlink timing relationship;

[0015] Figure 7A This is a diagram illustrating an embodiment of the timing advance command MAC CE;

[0016] Figure 7B This is a diagram illustrating one embodiment of the absolute timing advance command (MAC CE);

[0017] Figure 7C This is a diagram illustrating one embodiment of the Delta MAC CE.

[0018] Figure 8 It is an example of an IAB system with single-panel and multi-panel IAB nodes for integrating timing alignment in access and backhaul.

[0019] Figure 9 It is an example of an IAB system with single-panel and multi-panel IAB nodes;

[0020] Figure 10A This is a diagram illustrating one embodiment of the principle transmission timing alignment used in case 6;

[0021] Figure 10B This is a diagram illustrating one embodiment of instance transmission timing alignment for case 6;

[0022] Figure 11This is a block diagram illustrating an example embodiment of a method for TX timing alignment at the IAB node (N2);

[0023] Figure 12A This is a diagram illustrating one embodiment of the principle-based receiving timing alignment for case 7;

[0024] Figure 12B This is a diagram illustrating one embodiment of instance receive timing alignment for case 7;

[0025] Figure 13 This is a diagram illustrating one embodiment of RX timing alignment by allowing negative TA;

[0026] Figure 14 This is a block diagram illustrating an example embodiment of a method for RX timing alignment at a child node (N3) or an enhanced UE;

[0027] Figure 15 This is a diagram illustrating an example of additional timing advance commands used for timing alignment in integrated access and backhaul.

[0028] Figure 16 This is a diagram illustrating an example of an additional timing advance command with a sign shift indicator used for timing alignment in integrated access and backhaul.

[0029] Figure 17 This is a block diagram illustrating an example embodiment of a method for RX timing alignment using symbol shift (transformation at N2) at a child node (N3) or an enhanced UE;

[0030] Figure 18 This is a block diagram illustrating an example embodiment of a method for RX timing alignment using symbol shift (transformation at N3) at a child node (N3) or an enhanced UE;

[0031] Figure 19 This is a block diagram illustrating an example embodiment of a method for unified timing alignment at IAB nodes;

[0032] Figure 20 This is a block diagram illustrating an example embodiment of a method for performing uniform timing alignment at IAB nodes using sign shifting and transformations at the parent node of the IAB node.

[0033] Figure 21 This is a block diagram illustrating an example embodiment of a method for performing uniform timing alignment at IAB nodes using sign shifting and transformations at IAB nodes;

[0034] Figure 22 This is a diagram illustrating an example embodiment of a scenario for an IAB system;

[0035] Figure 23 This is a diagram illustrating an example of a timing misalignment between uplink and downlink transmissions;

[0036] Figure 24 This is a block diagram illustrating an example embodiment of a method for TX IAB nodes;

[0037] Figure 25 This is a block diagram illustrating an example embodiment of a method for RX IAB nodes;

[0038] Figure 26 This is a schematic block diagram illustrating one embodiment of a device that can be used for timing alignment in integrated access and backhaul.

[0039] Figure 27 This is a schematic block diagram illustrating another embodiment of a device that can be used for timing alignment in integrated access and backhaul.

[0040] Figure 28 This is a block diagram illustrating an example embodiment of a method for timing alignment in integrated access and backhaul;

[0041] Figure 29 This is a block diagram illustrating an example embodiment of a method for timing alignment in integrated access and backhaul.

[0042] Figure 30 This is a block diagram illustrating an example embodiment of a method for timing alignment in integrated access and backhaul; and

[0043] Figure 31 This is a block diagram illustrating an example embodiment of a method for timing alignment in integrated access and backhaul. Detailed Implementation

[0044] As those skilled in the art will understand, aspects of the embodiments may be embodied as systems, devices, methods, or program products. Therefore, embodiments may take the form of entirely hardware embodiments, entirely software embodiments (including firmware, resident software, microcode, etc.), or embodiments combining software and hardware aspects, all of which can be generally referred to herein as “circuit,” “module,” or “system.” Furthermore, embodiments may take the form of program products embodied in one or more computer-readable storage devices storing machine-readable code, computer-readable code, and / or program code (hereinafter referred to as “code”). Storage devices may be tangible, non-transitory, and / or non-transferable. Storage devices may not embody signals. In certain embodiments, storage devices use only signals to access code.

[0045] Certain functional units described in this specification may be labeled as modules to more specifically emphasize their implementation independence. For example, modules may be implemented as hardware circuitry (including custom-designed very large-scale integration (“VLSI”) circuitry or gate arrays), off-the-shelf semiconductors (e.g., logic chips, transistors), or other discrete components. Modules may also be implemented in programmable hardware devices, such as field-programmable gate arrays, programmable array logic, programmable logic devices, or the like.

[0046] Modules can also be implemented in code and / or software to be executed by various types of processors. An identified module of code may, for example, contain one or more physical or logical blocks of executable code, which may be organized, for example, as objects, programs, or functions. However, an executable file of an identified module does not need to be physically located together, but may contain disparate instructions stored in different locations that, when logically combined, contain the module and achieve the specified purpose of the module.

[0047] In practice, a code module can be a single instruction or many instructions, and can even be distributed across several different code segments, different programming sections, and several memory devices. Similarly, operational data can be identified and described within the module herein, and can be represented in any suitable form and organized within any suitable type of data structure. Operational data can be collected as a single dataset or can be distributed across different locations, including across different computer-readable storage devices. When a module or part of a module is implemented in software, the software portion is stored on one or more computer-readable storage devices.

[0048] Any combination of one or more computer-readable media may be used. The computer-readable media may be a computer-readable storage medium. The computer-readable storage medium may be a storage device for storing code. The storage device may be, for example (but not limited to), an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, device, or apparatus, or any suitable combination of the foregoing.

[0049] Further specific examples of storage devices (a non-exhaustive list) will include the following: electrical connections having one or more wires, portable computer disks, hard disks, random access memory (“RAM”), read-only memory (“ROM”), erasable programmable read-only memory (“EPROM” or flash memory), portable optical disc read-only memory (“CD-ROM”), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing. In the context of this document, a computer-readable storage medium can be any tangible medium that may contain or store programs for use by or in conjunction with an instruction execution system, device, or apparatus.

[0050] The code used to implement the operations of the embodiments may be written in any number of lines and may include one or more programming languages, such as object-oriented programming languages ​​(e.g., Python, Ruby, Java, Smalltalk, C++, or similar languages), conventional procedural programming languages ​​(e.g., the "C" programming language or similar languages), and / or machine languages ​​(e.g., assembly language). The code may execute entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer via any type of network, including local area networks ("LANs") or wide area networks ("WANs"), or may be able to connect to external computers (e.g., via the Internet provided by an Internet service provider).

[0051] References to “an embodiment,” “embodiment,” or similar language throughout this specification mean that a particular feature, structure, or characteristic described in connection with an embodiment is included in at least one embodiment. Therefore, unless expressly specified otherwise, the phrases “in an embodiment,” “in an embodiment,” and similar language appearing throughout this specification may refer to all (but not necessarily) the same embodiment, but rather to “one or more, but not all, embodiments.” Unless expressly specified otherwise, the terms “comprising,” “including,” “having,” and variations thereof mean “comprising (but not limited to).” Unless expressly specified otherwise, the list of items does not imply that any or all items are mutually exclusive. Unless expressly specified otherwise, the terms “a / an” and “described” also mean “one or more.”

[0052] Furthermore, the features, structures, or characteristics described in the embodiments can be combined in any suitable manner. In the following description, numerous specific details are provided to provide a thorough understanding of the embodiments, such as examples of programming, software modules, user selection, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc. However, those skilled in the art will recognize that the embodiments can be practiced without one or more of the specific details (or with other methods, components, materials, etc.). In other instances, well-known structures, materials, or operations have not been shown or described in detail to avoid obscuring aspects of the embodiments.

[0053] Aspects of the embodiments are described below with reference to schematic flowcharts and / or schematic block diagrams of methods, apparatus, systems, and program products according to the embodiments. It should be understood that each block and combination of blocks in the schematic flowcharts and / or schematic block diagrams can be implemented by code. The code can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine, such that instructions executable via the processor of the computer or other programmable data processing apparatus create components for implementing the functions / actions specified in the blocks or blocks of the schematic flowcharts and / or schematic block diagrams.

[0054] The code may also be stored in a storage device, which may instruct a computer, other programmable data processing device or other device to function in a particular manner, such that the instructions stored in the storage device produce an article of writing containing instructions that implement functions / actions specified in the blocks or blocks of the schematic flowchart and / or schematic block diagram.

[0055] The code may also be loaded onto a computer, other programmable data processing apparatus or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer-implemented process, such that the code executing on the computer or other programmable device provides a process for implementing the functions / actions specified in the boxes or blocks of the flowchart and / or schematic block diagram.

[0056] The schematic flowcharts and / or block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of the device, system, method, and program products according to various embodiments. In this regard, each block in the schematic flowchart or block diagram may represent a code module, code segment, or code portion containing one or more executable instructions for implementing (a number of) specified logical functions.

[0057] It should also be noted that in some alternative implementations, the functions described in the boxes may not occur in the order shown in the figures. For example, two boxes shown consecutively may actually be executed substantially concurrently, or the boxes may sometimes be executed in reverse order, depending on the functionality involved. Other steps and methods that are functionally, logically, or effectively equivalent to one or more boxes or portions thereof in the illustrated figures may be considered.

[0058] While various arrow and line types may be used in flowcharts and / or block diagrams, they should not be construed as limiting the scope of the corresponding embodiments. In fact, some arrows or other connectors may be used only to indicate the logical flow of the depicted embodiment. For example, an arrow may indicate a wait or monitoring period of unspecified duration between enumeration steps in a depicted embodiment. It should also be noted that each block and combination of blocks in a block diagram and / or flowchart may be implemented by a system based on dedicated hardware or a combination of dedicated hardware and code that performs the specified function or action.

[0059] The description of the components in each figure can be referenced to the components in the previous figures. Similar numbers refer to similar components in all figures, including alternative embodiments of similar components.

[0060] Generally, this disclosure describes systems, methods, and apparatuses for integrating timing alignment in access and backhaul. In some embodiments, the methods may be executed using computer code embedded in a computer-readable medium. In some embodiments, the apparatus or system may include computer-readable medium containing computer-readable code that, when executed by a processor, causes the apparatus or system to perform at least a portion of the solution described below.

[0061] Integrated Access and Backhaul (“IAB”) is specified for New Radio Access Technology (“NR”) Version 16 (“Rel-16”). The IAB technology aims to improve deployment flexibility and reduce the cost of 5G rollout. It allows service providers to reduce cell planning and spectrum planning efforts when utilizing wireless backhaul technology.

[0062] Although the IAB specification in Rel-16 is not limited to specific multiplexing and duplexing schemes, the focus is on time division multiplexing (“TDM”) between upstream communications (with a parent IAB node / donor) and downstream communications (with a child IAB node or UE).

[0063] RAN#86 has approved enhancements to Rel-17 duplexing to support simultaneous operation (transmission and / or reception) by IAB nodes in both downstream and upstream environments. This duplex enhancement should allow IAB nodes to communicate simultaneously with both parent and child nodes, which requires exceeding the timing alignment enhancements specified in Rel-16, known as Timing Alignment Case 1, which aligns downlink transmission times only at the timeslot level.

[0064] A more detailed problem statement will follow the background section. Then, a system and method for timing alignment of enhanced duplex in IAB systems are proposed. This disclosure is consistent with the following objectives of the WI approved for use in version 17 [RP-193251] (with additional details). emphasize ):

[0065] Duplex enhancement [RAN1-led, RAN2, RAN3, RAN4]:

[0066] a. Enhance the specification for resource multiplexing between child and parent links of IAB nodes, including:

[0067] i. Support simultaneous operation (transmission and / or reception) of child and parent links of IAB nodes (i.e., mobile terminal (“MT”) transmission (“Tx”) / distributed terminal (“DU”) Tx, MT Tx / DU reception (“Rx”), MT Rx / DU Tx, MT Rx / DU Rx).

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

[0069] b. IAB Node Timing Pattern Specification As needed, it can be extended for DL / UL power control and BH link CLI and Interference measurement To support simultaneous operation (transmission and / or reception) by the child and parent links of the IAB node.

[0070] This disclosure presents methods for Tx and Rx timing alignment in IAB systems. Several embodiments of configuration and signaling are provided for each of two cases of Tx and Rx alignment at IAB nodes, which are leading candidates for duplex-enhanced IAB timing alignment in Rel-17. The methods are extensible to a unified framework and signaling, wherein different timing alignment methods can be configured based on node capabilities and applied locally based on scheduling needs.

[0071] Figure 1 A wireless communication system 100 for timing alignment in integrated access and backhaul is depicted according to embodiments of the present disclosure. In one embodiment, the wireless communication system 100 includes at least one remote unit 105, a fifth-generation radio access network (“5G-RAN”) 115, and a mobile core network 140. The 5G-RAN 115 and the mobile core network 140 form a mobile communication network. The 5G-RAN 115 may consist of a 3GPP access network 120 containing at least one cellular base station unit 121 and / or a non-3GPP access network 130 containing at least one access point 131. The remote unit 105 communicates with the 3GPP access network 120 using a 3GPP communication link 123 and / or communicates with the non-3GPP access network 130 using a non-3GPP communication link 133. Although Figure 1The system depicts a specific number of remote units 105, 3GPP access networks 120, cellular base station units 121, 3GPP communication links 123, non-3GPP access networks 130, access points 131, non-3GPP communication links 133, and mobile core networks 140. However, those skilled in the art will recognize that the wireless communication system 100 may include any number of remote units 105, 3GPP access networks 120, cellular base station units 121, 3GPP communication links 123, non-3GPP access networks 130, access points 131, non-3GPP communication links 133, and mobile core networks 140.

[0072] In one implementation, RAN 115 conforms to the 5G system specified in the 3rd Generation Partnership Project (“3GPP”) specifications. For example, RAN 115 may be an NG-RAN implementing NR RAT and / or LTE RAT. In another instance, RAN 115 may contain non-3GPP RATs (e.g., Alternatively, it may conform to the Institute of Electrical and Electronics Engineers (“IEEE”) 802.11 series of WLANs. In another embodiment, RAN 115 conforms to the LTE system specified in the 3GPP specification. However, more generally, the wireless communication system 100 may implement other open or proprietary communication networks, such as Global Microwave Access Interoperability (“WiMAX”) or the IEEE 802.16 series of standards and other networks. This disclosure is not intended to limit implementation to any particular wireless communication system architecture or protocol.

[0073] In one embodiment, remote unit 105 may include a computing device, such as a desktop computer, laptop computer, personal digital assistant (“PDA”), tablet computer, smartphone, smart TV (e.g., a TV connected to the Internet), smart appliance (e.g., an appliance connected to the Internet), set-top box, game console, security system (including security camera), in-vehicle computer, network device (e.g., router, switch, modem), or the like. In some embodiments, remote unit 105 includes a wearable device, such as a smartwatch, fitness tracker, optical head-mounted display, or the like. Furthermore, remote unit 105 may be referred to as UE, subscriber unit, mobile device, mobile station, user, terminal, mobile terminal, fixed terminal, subscriber station, user terminal, wireless transmit / receive unit (“WTRU”), device, or by other terms used in the art. In various embodiments, remote unit 105 includes a subscriber identity and / or identification module (“SIM”) and a mobile equipment (“ME”) that provides mobile terminal functions (e.g., radio transmission, handover, voice encoding and decoding, error detection and correction, signaling, and access to the SIM). In some embodiments, the remote unit 105 may include terminal equipment (“TE”) and / or be embedded in an appliance or device (e.g., a computing device, as described above).

[0074] In one embodiment, remote unit 105 may include a computing device, such as a desktop computer, laptop computer, personal digital assistant (“PDA”), tablet computer, smartphone, smart TV (e.g., a TV connected to the Internet), smart appliance (e.g., an appliance connected to the Internet), set-top box, game console, security system (including security cameras), in-vehicle computer, network device (e.g., router, switch, modem), or the like. In some embodiments, remote unit 105 includes a wearable device, such as a smartwatch, fitness tracker, optical head-mounted display, or the like. Furthermore, remote unit 105 may be referred to as a UE, subscriber unit, mobile device, mobile station, user, terminal, mobile terminal, fixed terminal, subscriber station, user terminal, wireless transmit / receive unit (“WTRU”), device, or by other terms used in the art.

[0075] Remote unit 105 can communicate directly with one or more of the cellular base station units 121 in the 3GPP access network 120 via uplink (“UL”) and downlink (“DL”) communication signals. Additionally, the UL and DL communication signals can be carried via 3GPP communication link 123. Similarly, remote unit 105 can communicate with one or more access points 131 in the non-3GPP access network 130 via UL and DL communication signals carried via non-3GPP communication link 133. Here, access networks 120 and 130 are intermediate networks providing remote unit 105 with access to the mobile core network 140.

[0076] In some embodiments, remote unit 105 communicates with a remote host (e.g., in data network 150 or data network 160) via a network connection to mobile core network 140. For example, an application 107 in remote unit 105 (e.g., a web browser, media client, telephone, and / or Internet Protocol Voice Telephony (“VoIP”) application) can trigger remote unit 105 to establish a Protocol Data Unit (“PDU”) session (or other data connection) with mobile core network 140 via 5G-RAN 115 (i.e., via 3GPP access network 120 and / or non-3GPP network 130). Mobile core network 140 then uses the PDU session to relay services between remote unit 105 and the remote host. The PDU session represents a logical connection between remote unit 105 and user plane function (“UPF”) 141.

[0077] To establish a PDU session (or PDN connection), remote unit 105 must register with mobile core network 140 (also referred to as "attached to mobile core network" in the context of fourth-generation ("4G") systems). Note that remote unit 105 may establish one or more PDU sessions (or other data connections) with mobile core network 140. Thus, remote unit 105 may have at least one PDU session for communicating with packet data network 150. Alternatively, remote unit 105 may have at least one PDU session for communicating with packet data network 160. Remote unit 105 may establish additional PDU sessions to communicate with other data networks and / or other communication peers.

[0078] In the context of a 5G system (“5GS”), the term “PDU session” refers to a data connection that provides end-to-end (“E2E”) user plane (“UP”) connectivity between remote unit 105 and a specific data network (“DN”) via UPF 141. A PDU session supports one or more Quality of Service (“QoS”) streams. In some embodiments, a one-to-one mapping may exist between QoS streams and QoS profiles, such that all packets belonging to a particular QoS stream have the same 5G QoS identifier (“5QI”).

[0079] In the context of a 4G / LTE system, such as an Evolved Packet System (“EPS”), a Packet Data Network (“PDN”) connection (also known as an EPS session) provides end-to-end connectivity between the remote unit and the PDN. The PDN connectivity process establishes an EPS bearer, i.e., a tunnel between the remote unit 105 and the packet gateway (“PGW”, not shown) in the mobile core network 140. In some embodiments, a one-to-one mapping may exist between the EPS bearer and the QoS profile, such that all packets belonging to a particular EPS bearer have the same QoS Class Identifier (“QCI”).

[0080] As described in more detail below, remote unit 105 may use a first data connection (e.g., a PDU session) established with the first mobile core network 140 to establish a second data connection (e.g., a portion of the second PDU session) with the second mobile core network 140. When establishing a data connection (e.g., a PDU session) with the second mobile core network 140, remote unit 105 registers with the second mobile core network 140 using the first data connection.

[0081] Cellular base station unit 121 may be distributed across a geographical area. In some embodiments, cellular base station unit 121 may also be referred to as an access terminal, base station, base station, node B (“NB”), evolved Node B (abbreviated as eNodeB or “eNB”, also referred to as an evolved Universal Terrestrial Radio Access Network (“E-UTRAN”) node B), 5G / NR node B (“gNB”), home node B, relay node, device, IAB donor, IAB node, or any other terminology used in the art. Cellular base station unit 121 typically comprises a portion of a radio access network (“RAN”) (e.g., 3GPP access network 120) communicatively coupled to one or more controllers corresponding to cellular base station unit 121. These and other elements of the radio access network are not described but are generally known to those skilled in the art. Cellular base station unit 121 is connected to mobile core network 140 via 3GPP access network 120.

[0082] Cellular base station unit 121 can serve several remote units 105 within a service area (e.g., a cell or cell sector) via 3GPP wireless communication link 123. Cellular base station unit 121 can communicate directly with one or more of the remote units 105 via communication signals. Typically, cellular base station unit 121 transmits DL communication signals to serve the remote units 105 in the time, frequency, and / or spatial domains. Additionally, DL communication signals can be carried via 3GPP communication link 123. 3GPP communication link 123 can be any suitable carrier in licensed or unlicensed radio spectrum. 3GPP communication link 123 facilitates communication between one or more of the remote units 105 and / or one or more of the cellular base station unit 121. Note that during NR operation (referred to as "NR-U") on unlicensed spectrum, base station unit 121 communicates with remote units 105 via unlicensed (i.e., shared) radio spectrum.

[0083] Non-3GPP access networks 130 may be distributed across a geographical area. Each non-3GPP access network 130 may serve several remote units 105 within its service area. Access points 131 in non-3GPP access networks 130 may communicate directly with one or more remote units 105 by receiving UL communication signals and transmitting DL communication signals to serve remote units 105 in the time, frequency, and / or spatial domains. Both DL and UL communication signals are carried via non-3GPP communication links 133. 3GPP communication links 123 and non-3GPP links 133 may employ different frequencies and / or different communication protocols. In various embodiments, access points 131 may communicate using unlicensed radio spectrum. Mobile core network 140 may provide services to remote units 105 via non-3GPP access networks 130, as described in more detail herein.

[0084] In some embodiments, the non-3GPP access network 130 is connected to the mobile core network 140 via an interworking entity 135. The interworking entity 135 provides interworking between the non-3GPP access network 130 and the mobile core network 140. The interworking entity 135 supports connectivity via the “N2” and “N3” interfaces. As depicted, both the 3GPP access network 120 and the interworking entity 135 use the “N2” interface to communicate with the AMF 143. The 3GPP access network 120 and the interworking entity 135 also use the “N3” interface to communicate with the UPF 141. Although depicted as being outside the mobile core network 140, in other embodiments, the interworking entity 135 may be part of the core network. Although depicted as being outside the non-3GPP RAN 130, in other embodiments, the interworking entity 135 may be part of the non-3GPP RAN 130.

[0085] In some embodiments, the non-3GPP access network 130 may be controlled by the operator of the mobile core network 140 and may have direct access to the mobile core network 140. This non-3GPP AN deployment is referred to as a “trusted non-3GPP access network”. When the non-3GPP access network 130 is operated by a 3GPP operator or a trusted partner, it is considered “trusted” and supports certain security features, such as strong air interface encryption. In contrast, a non-3GPP AN deployment that is not controlled by the operator (or trusted partner) of the mobile core network 140, does not have direct access to the mobile core network 140, or does not support certain security features is referred to as an “untrusted” non-3GPP access network. The interoperability entity 135 deployed in the trusted non-3GPP access network 130 may be referred to herein as a trusted network gateway function (“TNGF”). The interoperability entity 135 deployed in the untrusted non-3GPP access network 130 may be referred to herein as a non-3GPP interoperability function (“N3IWF”). Although depicted as part of a non-3GPP access network 130, in some embodiments, N3IWF may be part of a mobile core network 140 or may be located in a data network 150.

[0086] In one embodiment, the mobile core network 140 is a 5G core (“5GC”) or an evolved packet core (“EPC”) that may be coupled to a data network 150, such as the Internet, private data networks, and other data networks. The remote unit 105 may have a subscription or other account to the mobile core network 140. Each mobile core network 140 belongs to a single Public Land Mobile Network (“PLMN”). This disclosure is not intended to limit implementation to any particular wireless communication system architecture or protocol.

[0087] The mobile core network 140 includes several network functions (“NFs”). As depicted, the mobile core network 140 includes at least one UPF (“UPF”) 141. The mobile core network 140 also includes multiple control plane functions, including (but not limited to) access and mobility management functions (“AMF”) 143, session management functions (“SMF”) 145, policy control functions (“PCF”) 147, authentication server functions (“AUSF”) 148, unified data management functions (“UDM”) and unified data repository functions (“UDR”) serving 5G-RAN 115.

[0088] UPF 141 is responsible for packet routing and forwarding, packet inspection, QoS handling, and external PDU sessions for interconnecting data networks (“DN”) in the 5G architecture. AMF 143 is responsible for NAS signaling termination, NAS encryption and integrity protection, registration management, connection management, mobility management, access authentication and authorization, and security context management. SMF 145 is responsible for session management (i.e., session establishment, modification, and release), remote unit (i.e., UE) IP address allocation and management, DL data notification, and service bootstrapping configuration of UPFs for correct service routing.

[0089] PCF 147 is responsible for unifying the policy framework, providing policy rules to the CP function, and accessing subscription information in the UDR used for policy decisions. AUSF 148 is used as an authentication server.

[0090] The UDM is responsible for the generation of authentication and key negotiation (“AKA”) credentials, user identity processing, access authorization, and subscription management. The UDR is a subscriber repository and can be used to serve several network functions. For example, the UDR may store subscription data, policy-related data, subscriber-related data permitted to be exposed to third-party applications, and similar data. In some embodiments, the UDM and UDR are co-located and depicted as a combined entity “UDM / UDR”149.

[0091] In various embodiments, the mobile core network 140 may also include a network exposure function (“NEF”) (which makes network data and resources easily accessible to customers and network partners, for example, via one or more APIs), a network repository function (“NRF”) (which provides NF service registration and discovery, enabling NFs to identify the appropriate services among themselves and communicate with each other via application programming interfaces (“APIs”), or other NFs defined for 5GC. In some embodiments, the mobile core network 140 may include an authentication, authorization, and accounting (“AAA”) server.

[0092] In various embodiments, the mobile core network 140 supports different types of mobile data connections and different types of network slices, wherein each mobile data connection utilizes a specific network slice. Here, a "network slice" refers to a portion of the mobile core network 140 optimized for a specific service type or communication service. Network examples may be identified by S-NSSAI, while a set of network slices authorized for use by the remote unit 105 is identified by NSSAI. In some embodiments, various network slices may contain individual examples of network functions, such as SMF and UPF 141. In some embodiments, different network slices may share some common network functions, such as AMF 143. For ease of illustration, Figure 1 Different network slices are not shown, but it is assumed that they are supported.

[0093] although Figure 1 The mobile core network 140 may contain any number and type of network functions. Furthermore, in cases where the mobile core network 140 includes an EPC, the described network functions may be replaced by appropriate EPC entities, such as an MME, S-GW, P-GW, HSS, and the like.

[0094] Although Figure 1 This description depicts components of the 5G RAN and 5G core network, but the described embodiments for access authentication via non-3GPP access using pseudonyms are applicable to other types of communication networks and RATs, including IEEE 802.11 variants, GSM, GPRS, UMTS, LTE variants, CDMA 2000, Bluetooth, ZigBee, Sigfox, and the like. For example, in 4G / LTE variants involving EPC, AMF 143 can be mapped to the MME, SMF can be mapped to the control plane portion of the PGW and / or mapped to the MME, UPF 141 can be mapped to the SGW and the user plane portion of the PGW, UDM / UDR 149 can be mapped to the HSS, etc.

[0095] As depicted, remote unit 105 (e.g., UE) can connect to the mobile core network (e.g., a 5G mobile communication network) via two types of access: (1) via 3GPP access network 120 and (2) via non-3GPP access network 130. The first type of access (e.g., 3GPP access network 120) uses 3GPP-defined type wireless communication (e.g., NG-RAN), and the second type of access (e.g., non-3GPP access network 130) uses non-3GPP-defined type wireless communication (e.g., WLAN). 5G-RAN 115 refers to any type of 5G access network (including 3GPP access network 120 and non-3GPP access network 130) that provides access to the mobile core network 140.

[0096] Figure 2A This is an example of an Integrated Access and Backhaul (“IAB”) system 200 (in standalone mode). The core network 202 is connected to the IAB donor 204 of the IAB system 200 via a backhaul link 203 (which is typically wired). The IAB donor 204 includes a central unit (“CU”) 206 that communicates with all distributed units (“DUs”) 210 in the system via an F1 interface 205. The IAB donor 204 is a single logical node that may include a set of functions 208, such as gNB-DU, gNB-CU-CP, gNB-CU-UP, etc. In deployment, the IAB donor 204 can be split according to these functions, which may be all co-located or not.

[0097] Each IAB node 212 is functionally divided into at least one distributed unit (“DU”) and a mobile terminal (“MT”). The MT of IAB node 212 is connected to the DU 210 of its parent node, which may be another IAB node 212 or an IAB donor 204.

[0098] The Uu link between the MT (referred to as IAB-MT) of IAB node 212 and the DU 210 (referred to as IAB-DU) of the parent node is called the radio backhaul link 207. In the radio backhaul link 207, in terms of functionality, the MT is similar to a user equipment (“UE”) 214, and the DU 210 of the parent node is similar to a base station in a conventional cellular radio access link. Therefore, the link from the MT to the serving cell (which is the DU 210 of the parent link) is called the uplink, and the link in the opposite direction is called the downlink. For the sake of brevity, in the remainder of this disclosure, embodiments may simply refer to uplink or downlink between IAB nodes 212, upstream or downstream link of IAB node 212, link between a node and its parent node, link between a node and its child node, etc., without directly referring to IAB-MT, IAB-DU, serving cell, etc.

[0099] Each IAB donor 204 or IAB node 212 can serve UE 214 via access link 209. IAB system 200 is designed to allow multi-hop communication; that is, UE 214 can connect to core network 202 via access link 209 and multiple backhaul links 207 between IAB node 212 and IAB donor 204. For the remainder of this disclosure, unless otherwise stated, "IAB node" generally refers to IAB node 212 or IAB donor 204, unless the connection between CU 206 and core network 202 is involved.

[0100] Figure 2B This is a block diagram illustrating an embodiment of the summary of the CU / DU split in IAB donor 204 and the DU / MT split in IAB node 212. Figure 2B This diagram illustrates the functional breakdown of IAB donor 204 and IAB node 212. In this diagram, IAB node 212 or UE 214 can be served by more than one serving cell (because they support dual connectivity (“DC”)).

[0101] Nodes, links, or the like that closer to IAB donor 204 and / or core network 202 are called upstream nodes or links. For example, the parent node of a subject node is an upstream node of the subject node, and the link to the parent node is an upstream link about the subject node. Similarly, nodes or links farther away from IAB donor 204 and / or core network 202 are called downstream nodes or links. For example, the child nodes of a subject node are downstream nodes of the subject node, and the link to the child node is a downstream link about the subject node.

[0102] For the sake of brevity, the following table summarizes the terminology used in this disclosure and the descriptions that may appear in standard specifications.

[0103]

[0104]

[0105] Table 1.

[0106] Furthermore, where appropriate, "operation" or "communication" may refer to transmission or reception in the uplink (or upstream) or downlink (or downstream). Next, the terms "simultaneous operation" or "simultaneous communication" may refer to multiplexed / multiplexed transmission and / or reception performed by a node through one or more antennas / panels. The details of simultaneous operation should be understood from the context.

[0107] Regarding timing alignment, there are seven timing alignment scenarios:

[0108]

[0109]

[0110] Table 2.

[0111] Approval scenario 1 specifies IAB Rel-16 for TDM focus. Scenario 2 / 3 / 4 / 5 will not be supported. Scenario 6 and 7 are candidates for enhanced timing alignment to facilitate and improve the performance of FDM / SDM between simultaneous upstream and downstream operations.

[0112] Figure 3 This diagram illustrates one embodiment of a scenario used for timing alignment. In this example, IAB donor / node N1 302 is the parent node of IAB node N2 304, and IAB node N2 304 is the parent node of IAB node N3 306. In this example, link 301 between N1 and N2 experiences a longer propagation delay than link 303 between N2 and N3.

[0113] Regarding timing alignment case 1, Figure 4A and 4BThis diagram illustrates an embodiment of timing alignment scenario 1: principle (4A) and example timeline (4B). In this scenario, the timing of downlink transmissions across IAB node 212 is aligned. Figure 4B In the example shown, lined rectangle 402 indicates an operation (e.g., transmission or reception) in a time slot, while shaded rectangle 404 indicates no operation due to half-duplex constraints. Furthermore, solid rectangles represent transmissions and dashed rectangles represent receptions.

[0114] Case 1 timing alignment is achieved by setting the downlink transmission timing to be TA / 2+T_delta ahead of the downlink reception timing, where:

[0115] i.TA is the instantaneous value of timing advance (“TA”), as specified in NR Rel-15, for example. It should be set to the most recent time interval (e.g., gap) between the start of uplink transmission frame i and the start of downlink reception frame i at the child IAB node (e.g., N2).

[0116] ii.T_delta is a parameter specified in IAB Rel-16, which should be set to (-1 / 2) the time interval between the start of the uplink received frame i from the child node (e.g., N2) at the parent node (e.g., N1) and the start of the downlink transmitted frame i to the child node (e.g., N2).

[0117] Figure 5 This is a diagram illustrating one embodiment of the timeline used for timing alignment in Application Case 1. Explanation of timing alignment for IAB Rel-16:

[0118] a. T_delta is sent from the parent node to the child node via MAC-CE signaling. T_delta has a finer granularity than TA, and the signaling is irregular. The individual value range / granularity of T_delta in FR1 and FR2 are discussed in the SI phase.

[0119] b. If the value of TA / 2+T_delta at the IAB node is negative, then the IAB node should not adjust its downlink transmission timing.

[0120] c. From RAN1’s perspective, Rel-16 NR IAB does not introduce signaling for accuracy / quality measurement of downlink transmission timing for IAB nodes.

[0121] d. In Rel-16, when not in RRC_Connected mode, IAB nodes are not expected to receive T_delta.

[0122] e. IAB nodes with multiple parents treat each parent as a separate synchronization source. The question remains: how do IAB nodes determine their downlink transmission timing from multiple values ​​of tentative downlink transmission timing?

[0123] Although cases 6 and 7 are considered candidates for timing alignment applied to enhanced duplex in IAB Rel-17, signaling and addressing issues still need to be specified. In the next section, we review signaling methods to implement cases 6 and 7 and address related issues.

[0124] Regarding the transmission timing adjustments in the physical layer specification Figure 6 This is a diagram illustrating one embodiment of the uplink-downlink timing relationship. The following procedure specified for the UE also applies to IAB-MT. The uplink frame number i used for transmission from the UE should be T before the start of the corresponding downlink frame at the UE. TA =(N TA +N TA,offset )T c Beginning, where N TA,offset Given [38.213], except that T should be used in it. TA Outside of the msgA transmission on PUSCH = 0.

[0125] The timing advance offset value N of the serving cell can be provided to the UE from the n-TimingAdvanceOffset of the serving cell. TA,offset If the n-TimingAdvanceOffset of the serving cell is not provided to the UE, then the UE determines the default value N for the timing advance offset of the serving cell. TA,offset As described in [38.133].

[0126] After receiving the timing advance command for TAG, the UE bases it on the value N that the UE expects to be the same for all serving cells in TAG. TA,offset Furthermore, the uplink timing of PUSCH / SRS / PUCCH transmissions on all serving cells in the TAG is adjusted based on the received timing advance command, wherein the uplink timing for PUSCH / SRS / PUCCH transmissions is the same for all serving cells in the TAG.

[0127] Regarding 2 μ • A 15kHz SCS is used for the timing advance command of the TAG to indicate that the uplink timing is 16.64T relative to the current uplink timing of the TAG. c / 2 μ A multiple change.

[0128] In other cases, the timing advance command T used for TAG A Indicates the current N TAValue N TA_old By index value T A =0,1,2,...,63 to the new N TA Value N TA_new The adjustments, including those for 2 μ ·15kHz SCS, N TA_new =N TA_old +(T A -31)·16·64 / 2 μ .

[0129] If a UE has multiple active UL BWPs in the same TAG, including the ULBWPs in two UL carriers of the serving cell, then the timing advance command value is the maximum SCS relative to the multiple active UL BWPs. The applicable N for UL BWPs with lower SCS... TA_new The value can be rounded to align with the timing advance granularity of the UL BWP with a lower SCS, while meeting the timing advance accuracy requirements in [38.133].

[0130] According to positive or negative values, N TA The adjustment of the value indicates whether the uplink transmission timing used for TAG will be advanced or delayed by the corresponding amount.

[0131] For timing advance commands received on uplink time slot n and for transmissions responding to successRAR except for PUSCHs authorized by RAR UL or PUCCHs with HARQ-ACK information, the corresponding adjustments to uplink transmission timing are applied starting from uplink time slot n+k+1. N T,1 It is the duration in msec of N1 symbols corresponding to the PDSCH processing time of UE processing capability 1 when additional PDSCH DM-RS is configured, where N... T,2 It is the duration in msec of N2 symbols corresponding to the PDSCH preparation time of UE processing capability 1 [38.214], where N TA,max It is the maximum timing advance value in msec that can be provided by the 12-bit TA command field. It is the number of time slots per subframe, and T sf This is the subframe duration of 1 ms. N1 and N2 are determined by the minimum SCS among all configured UL BWPs for all uplink carriers and all configured DL BWPs for the corresponding downlink carriers in the TAG. For μ = 0, the UE assumes N 1,0 =14[38.214]. Time slot n and It is determined by the minimum SCS among all configured UL BWPs relative to all uplink carriers in the TAG. TA,max It is determined by the minimum SCS among all configured UL BWPs relative to all uplink carriers in the TAG and all configured UL BWPs provided by the initialUplinkBWP. Assume T... TA =0, uplink time slot n is the last time slot in the uplink time slots that overlaps with the time slot received by PDSCH, where PDSCH provides timing advance commands and T TA Defined in [38.211].

[0132] If the UE changes the active UL BWP between the time the timing advance command is received and the time the corresponding adjustment is applied to the uplink transmission timing, the UE determines the timing advance command value based on the SCS of the new active UL BWP. If the UE changes the active UL BWP after the adjustment is applied to the uplink transmission timing, the UE assumes the same absolute timing advance command value before and after the change in the active UL BWP.

[0133] If a downlink timing change is received without a timing advance command as described in [38.133] and is not compensated or is only partially compensated by uplink timing adjustment, then the UE therefore changes N. TA .

[0134] If two adjacent time slots overlap due to a TA command, the duration of the latter time slot is reduced relative to the former time slot.

[0135] Regarding timing alignment in the IAB, if the value T is provided from the serving cell to the IAB node... delta Then when (N) TA +N TA,offset )·T c / 2+T delta When >0, IAB nodes can be assumed to be (N) TA +N TA,offset )·T c / 2+T delta It is the time difference between the signal being transmitted from the serving cell to the DU and the signal being received by the IAB node MT, where N is obtained by the "UE". TA and N TA,offset As described in previous chapters regarding tags containing serving cells, IAB nodes can use time differences to determine DU transmission times.

[0136] Regarding the Change Request (“CR”) status, CR R1-2003175 recommends that the above specification be changed to the following.

[0137] If the timing difference MAC CE[11,TS 38.321] is provided from the serving cell to the IAB node, the index T is... delta So when N TA / 2+N delta +T delta ·G step When >0, IAB nodes can be assumed to be (N) TA / 2+N delta +T delta ·G step )·T c It is the time difference between the signal being transmitted from the serving cell to the DU and the signal being received by the IAB node MT. Specifically, in Clause 4.2 concerning the "UE" obtaining N for TAGs containing the serving cell... TA And N delta and G step It was identified as:

[0138] a. If the serving cell providing the timing difference MAC CE operates in FR1, then N delta = -70528 and G step =64,

[0139] b. If the serving cell providing the timing difference MAC CE operates in FR2, then N delta =-17664 and G step =32.

[0140] Figure 7A This is a diagram illustrating one embodiment of the Timing Advance Command (MAC CE). The Timing Advance Command (MAC CE) is identified by the MAC subheader, where LCID = 61. It has a fixed size and consists of a single octet defined as follows:

[0141] a. TAG Identifier (TAG ID): This field indicates the TAG identifier of the addressed TAG. TAGs containing SpCells have TAG identifier 0. The field length is 2 bits.

[0142] b. Timing Advancement Command: This field indicates the index value T of the timing adjustment that must be applied to the MAC entity specified in [38.213]. A (0,1,2…63). The field length is 6 bits.

[0143] Figure 7B This diagram illustrates one embodiment of the Absolute Timing Advance Command (MACCE). The MACCE is identified by the MAC subheader, where LCID = 38. It has a fixed size and consists of two octets defined as follows:

[0144] a. Timing Advancement Command: This field indicates the index value TA used to control the amount of timing adjustments that must be applied to the MAC entity in [38.213]. The field size is 12 bits;

[0145] bR: Reserved bit, set to "0".

[0146] Figure 7C This is a diagram illustrating one embodiment of the timing differential MAC CE. The timing differential MAC CE is identified by the MAC sub-header, where LCID = 46. It has a fixed size and consists of two octets defined as follows:

[0147] aR: Reserved bit, set to 0;

[0148] b.T_delta: This field indicates the index value of Tdelta (0,1,2,…,1199) used to control the timing adjustment amount indicated by the MAC entity specified in [38.213]. The field is 11 bits long.

[0149] Regarding the RRC specification, the RRC field n-TimingAdvanceOffset is defined in both RRC IEs as follows:

[0150]

[0151]

[0152] Regarding IAB node synchronization and timing alignment, this study investigates the feasibility of over-the-air (“OTA”) synchronization and the impact of timing misalignment on IAB performance (e.g., the number of hops supported). Assuming timing requirements for IAB nodes across overlapping coverage areas are <= 3µs, for FR2, TA-based OTA synchronization can support multi-hop IAB networks (up to 5 hops). TA-based OTA synchronization may be insufficient to support multi-hops in FR1.

[0153] Investigate the following alignment levels between IAB nodes / IAB donors or within IAB nodes:

[0154] a. Time slot level alignment;

[0155] b. Symbol-level alignment;

[0156] c. Not aligned.

[0157] This research investigates mechanisms for timing alignment across multi-hop IAB networks. IABs support TA-based synchronization between IAB nodes (including across multiple backhaul hops). The research enhances existing timing alignment mechanisms by incorporating the TA required for IAB nodes to support different transport timing alignment scenarios.

[0158] The following cases of transmission timing alignment across IAB nodes and IAB donors are considered as part of the study;

[0159] a. Case #1: DL transmission timing alignment across IAB nodes and IAB donors:

[0160] i. If the DL TX and UL RX are not properly aligned at the parent node, then the child node needs additional alignment information to correctly set its DL TX timing for OTA-based timing and synchronization.

[0161] b. Case #2: DL and UL transmission timings are aligned within the IAB node;

[0162] c. Case #3: The timing of DL and UL reception is aligned within the IAB node;

[0163] d. Case #4: Within the IAB node, use case 2 during transmission and case 3 during reception;

[0164] e. Case #5: Within an IAB node, in different time slots, Case #1 is used for access link timing and Case 4 is used for backhaul link timing;

[0165] f. Case #6 (Case #1 DL transmission timing + Case #2 UL transmission timing):

[0166] i. Align the DL transmission timing for all IAB nodes with the parent IAB node or donor DL ​​timing.

[0167] ii. The UL transmission timing of the IAB node can be aligned with the DL transmission timing of the IAB node.

[0168] g. Case #7 (Case #1 DL transmission timing + Case #3 UL reception timing):

[0169] i. Align the DL transmission timing for all IAB nodes with the parent IAB node or donor DL ​​timing.

[0170] ii. The UL receiving timing of the IAB node can be aligned with the DL receiving timing of the IAB node;

[0171] iii. If the DL TX and UL RX are not properly aligned at the parent node, the child node needs additional alignment information to correctly set its DL TX timing for OTA-based timing and synchronization.

[0172] The study considers the impact of different scenarios on TDM / FDM / SDM multiplexing of access and backhaul links, the potential impact of imperfect timing adjustments, the overhead of required DL / UL handover gaps, cross-link interference, the feasibility of the situation when an IAB node is connected to one or more parent nodes, and the impact on access UEs (especially compatibility with Rel-15 UEs) as part of the research.

[0173] For both access and backhaul link transmission timing alignment, case #1 is supported.

[0174] For cases where IAB is not supported, see #2 to #5.

[0175] If case 6 is supported, then its use at the IAB node should be controlled by the parent or network.

[0176] To achieve alignment of DL transports between IAB nodes, the following solution examples have been identified:

[0177] a. Alternative 1: IAB nodes may need to implement uplink transmissions in parallel (always time-multiplexed) for scenarios #1 and #6;

[0178] b. Alternative Solution 2: Signal between the parent and IAB nodes to notify the parent node of the time difference in DL Tx and UL Rx timings in order to correct potential misalignment of DL Tx timings at the child node:

[0179] i. The child IAB node compares the corresponding differences between its own DL Tx timing and BH Rx timing; if the difference in the signaling notification from the parent node is greater than the difference measured at the child node, then the child node advances its TX timing; if it is smaller, then it delays its TX timing.

[0180] c. Note: For 6UL transmissions from different child nodes, Alternative 1 and Alternative 2 may require maintaining separate Rx timings at the parent node.

[0181] Case #7 achieves compatibility with Rel-15 UEs by introducing an "effective" negative TA and TDM between sub-IAB nodes / UEs that support the new TA value and those that do not. To achieve alignment between DL and UL receivers within the IAB node, the following solution examples have been identified:

[0182] a. Alternative 1: Introduce negative initial time alignment (TA) for the IAB node to be applied to the child nodes of the IAB node in application scenario #7 timing;

[0183] b. Alternative 2: Apply positive TA, which achieves symbol alignment rather than time slot alignment between DL reception and UL reception at the IAB node;

[0184] c. Alternative 3: Signal the relative offset of the most recent TA value to apply to the child nodes of the IAB node in application case #7 to achieve effective negative TA.

[0185] In addition to OTA synchronization, other technologies such as GNSS and PTP can be used to achieve synchronization across IAB nodes.

[0186] Figure 8 It is an example of an IAB system with single-panel and multi-panel IAB nodes. Figure 9 This is an alternative example of an IAB system with single-panel and multi-panel IAB nodes. Consider IAB networks, such as... Figure 8 and 9 The IAB network is described in the diagram. The IAB network is connected to the core network 202 through one or more IAB donors 204. Each IAB node 212 can be connected to IAB donor 204 and / or other IAB nodes 212 via a wireless backhaul link 207. Each IAB donor 204 / node 212 can also serve UE 214.

[0187] Various options exist regarding the architecture and multiplexing / duplex capabilities of IAB node 212. For example, each IAB node 212 may have one or more antenna panels 802, each antenna panel being connected to the baseband unit via an RF chain. One or more antenna panels 802 may be able to serve the entire space area of ​​interest near the IAB node 212, or otherwise, each antenna panel 802 or each group of antenna panels may provide partial coverage, such as within a sector. An IAB node 212 with multiple antenna panels 802 (each antenna panel serving a separate space area or sector) may still be referred to as a single-panel IAB node 212 because its behavior is similar to that of a single-panel IAB node 212 used for communication in each of the separate space areas or sectors.

[0188] Furthermore, each antenna panel 802 may be half-duplex (“HD”) (meaning it can transmit or receive signals in the frequency band at a time) or full-duplex (“FD”) (meaning it can both transmit and receive signals in the frequency band simultaneously). Unlike full-duplex radio, half-duplex radio is widely implemented and used in practice and is generally assumed to be the default operating mode in wireless systems.

[0189] The table below lists the different duplex scenarios of interest when multiplexing is not limited to Time Division Multiplexing (“TDM”). In this table, IAB Node 1 (N1) is a single-panel IAB node; IAB Node 2 (N2) is a multi-panel IAB node; and Space Division Multiplexing (“SDM”) refers to simultaneous transmission on both the downlink (or downstream) and uplink (or upstream). orReception; Full-duplex (“FD”) means simultaneous transmission and reception in a frequency band by the same antenna panel; and Multi-panel transmission and reception (“MPTR”) means simultaneous transmission and reception by multiple antenna panels, wherein each antenna panel transmits or receives once in one frequency band.

[0190] S1, Case B N1-DL-RX N1-UL-RX SDM S2, Case D N1-DL-RX N1-DL-TX FD S3, Case A N1-UL-TX N1-DL-TX SDM S4, Case C N1-UL-TX N1-UL-RX FD S5, Case B N2-DL-RX N2-UL-RX SDM S6, Case D N2-DL-RX N2-DL-TX MPTR / FD S7, Case A N2-UL-TX N2-DL-TX SDM S8, Case C N2-UL-TX N2-UL-RX MPTR / FD

[0191] Table 3.

[0192] Figure 10A and 10B This diagram illustrates an embodiment of transmission timing alignment (Case 6): principle (10A) and example timeline (10B). One method for timing alignment within an IAB node is to align simultaneous downlink and uplink transmissions. This method is useful, for example, in an FDM scheme, for achieving simultaneous transmission and baseband processing at an IAB node with a single antenna panel connected to a single RF chain. Since the timing of downlink transmissions is expected to be aligned across IAB nodes (i.e., Case 1), this leads to what is known in IAB research projects as timing alignment Case 6.

[0193] Instances of transmission timing alignment in Figure 10A and 10B The text explains that constraints are applied to begin a time slot only at regular intervals within the time slot period. Nodes N1, N2, and N3 are described as follows... Figure 3 describe.

[0194] The method for implementing TX timing alignment of an IAB node may include the following steps. First, the IAB node obtains the DL RX timing, timing advance (TA), and T based on NRRel-15 and IAB Rel-16. delta Next, the IAB node sets the UL TX timing to the DL TX timing, as obtained from Case 1 specified for IAB Rel-16. The method can be summarized as follows.

[0195] Method for IAB node N2:

[0196] a. Obtain DL RX(T) by receiving the reference signal. dl,rx (time series)

[0197] b. Obtain the timing advance (TA) of UL TX (e.g., via the timing advance command MAC CE).

[0198] c. Obtain T delta The value (e.g., via RRC signaling)

[0199] d. By time sequence Transmit uplink signals

[0200] Method for parent node N1:

[0201] a. By time sequence Transmit downlink reference signal

[0202] b. Obtain N TA,offset (Can be known in advance or predefined)

[0203] c. Transmission includes N TA TA commands (e.g., via MAC CE)

[0204] d. Transmission T delta The value (e.g., via RRC signaling)

[0205] e. Transmit control messages to trigger / activate TX timing alignment (Case 6) (e.g., via RRC signaling and / or via MAC CE)

[0206] f. Set TA offset :=N TA,offset .T c

[0207] g. By time sequence Receive uplink signals

[0208] In this method, the reference signal can be a synchronization signal and a physical broadcast channel (“SS / PBCH”) block. TA is obtained using a method similar to NR Rel-15. That is, TA = (N TA +N TA,offset ).T c , where N TA The integer N obtained from the TA command. TA,offset It is an integer offset determined by the standard / configuration, and T c It is a time unit defined by a standard. In the NR system, we obtain T. c = 0.509ns. When IAB node N2 executes the random access procedure, parent node N1 obtains the initial ULRx timing and corresponding timing advance (TA) information (equivalently, estimated propagation delay) from the received PRACH preamble. Parent node N1 can further refine the UL timing estimate using the estimated propagation delay (e.g., obtained from PRACH preamble detection) and the UL signal subsequently received from IAB node N2 (e.g., PUSCH DMRS). When a timing alignment scheme or mode (case 6) is enabled for IAB node N2, parent node N1 can... Set as assumed This corresponds to the delay, which includes propagation delay, timing offsets related to the Tx-Rx switching time, and timing estimation errors.

[0209] T deltaThe value can be signaled by the parent node (in this instance, by N1) according to IAB Rel-16. In some embodiments, T can be used. delta linear functions (e.g., (N) delta +T delta ·G step )) to replace T delta Additional item N delta and multiplication factor G step It can be obtained from signaling or specifications and can be different for different frequency ranges and / or subcarrier spacing.

[0210] The enhanced IAB system is expected to be able to apply different timing alignment modes. This will be explained in more detail in the following sections. Furthermore, we can extend the above approach with signaling that allows enabling or disabling timing alignment modes. This signaling can be a MAC-CE message for semi-persistent activation or deactivation of timing alignment modes, a downlink control information (DCI) message for triggering timing alignment modes within a period of time, such as one or more time slots, or other signaling.

[0211] An alternative embodiment of the Rx timing at parent node N1 is shown below. p,u It is the propagation delay between the IAB node (N2 in this instance) and its upstream node (parent N1 in this instance).

[0212] Method for parent node N1:

[0213] a. By time sequence Transmit downlink reference signal

[0214] b. Obtain N TA,offset

[0215] c. Transmission includes N TA TA command

[0216] d. Transmission T delta value

[0217] e. Transmit control messages to trigger / activate TX timing alignment (Case 6)

[0218] f. Set TA offset :=N TA,offset .T c

[0219] g. Obtain T p,u value

[0220] h. By time sequence Receive uplink signals

[0221] Method for IAB node N2:

[0222] a. Obtain DL RX T by receiving the reference signal dl,rx Timing

[0223] b. Obtain N TA,offset

[0224] c. Receiving includes N TA TA command

[0225] d. Receive T delta

[0226] e. Receive control messages to trigger / activate TX timing alignment (Case 6)

[0227] f. Set TA:=(N TA +N TA,offset ).T c

[0228] g. By time sequence Transmit uplink signals

[0229] The control message that triggers or activates the TX timing alignment mode can be a MAC-CE message, a DCI message, or a combination thereof.

[0230] In these methods, the application of the TX timing alignment mode depends on the control message received for the trigger or activation mode. Therefore, IAB node N2 can apply the default timing alignment mode for resource / slot R (e.g., timing advance) according to NR Rel-15 in the following cases:

[0231] a. No control message received.

[0232] b. A control message is received, but it is not associated with resource / slot R.

[0233] c. A control message is received, but it expires before the resource / slot R is transmitted because the timer associated with the control message has expired.

[0234] d. A control message was received, but it expired due to the subsequent receipt of a deactivation control message. The deactivation control message can be a MAC-CE message, a DCI message, or a combination thereof.

[0235] It should be noted that in the IAB system, downstream communication / operation (i.e., DL TX and / or UL RX) is performed by the IAB-DU in the parent IAB node or IAB donor, and downstream communication / operation (i.e., DL RX and / or UL TX) is performed by the IAB-MT in the IAB node or by the enhanced UE.

[0236] Figure 11This is a block diagram illustrating an example embodiment of a method 1100 for TX timing alignment at an IAB node (N2). In this example embodiment, the IAB node obtains the timing 1105 of DL RX by receiving a reference signal (e.g., a synchronization signal), similar to the method specified for NR Rel-15. Next, the IAB node obtains the timing advance (TA) value 1110, similar to the method specified for NR Rel-15. Then, the IAB node receives T... delta The value is 1115, which can be similar to the method specified in IAB Rel-16. Next, the IAB node determines whether the TX timing alignment mode is activated or triggered 1120.

[0237] If the TX timing alignment mode is activated or triggered, then the IAB node is set to obtain the DL RX timing before (TA / 2+T). delta The timing of UL TX 1125 is executed. Otherwise, the IAB node executes UL TX 1130 with the default timing (e.g., the timing of TA before obtaining the DL RX timing), and method 1100 ends.

[0238] In any of the embodiments discussed in this section, T may be used. delta linear functions (e.g., (N) delta +T delta ·G step )) to replace T delta Additional item N delta and multiplication factor G step It can be obtained from signaling or specifications and can be different for different frequency ranges and / or subcarrier spacing.

[0239] By extension, any timing alignment parameter T in this disclosure can be signaled or applied by a linear function of the parameter (e.g., N+TG), wherein the additional term N and / or the multiplication factor G can be obtained by signaling or by specification and can be different for different frequency ranges and / or subcarrier spacings.

[0240] Any of the timing alignment methods and embodiments proposed in this disclosure can be associated with a timing advance group (“TAG”) identifier (“ID”) via configuration or control message signaling. Thus, when the timing alignment method is applied, the IAB node employing the timing alignment method uses a timing advance (“TA”) parameter associated with the TAG ID.

[0241] Regarding configuration, timing alignment modes (such as the previously proposed TX timing alignment mode) can be fully specified by the standard, and capabilities can be defined by the standard specification. Alternatively, timing alignment modes can be configured by the IAB system, such as by the IAB-CU, to make it operational. First and foremost, since Rel-16 IAB nodes only support Case 1 timing alignment, the TX timing alignment at the IAB node can depend on capability parameters associated with N1 and / or N2, which demonstrate the node's enhancements according to the Rel-17+ specification. Configuration can also depend on other capabilities, such as multi-panel or simultaneous operation capabilities, which can be signaled to the IAB-CU or stored offline in the system.

[0242] For example, when timing alignment is used for transmission at N2, the reception of signals upstream and downstream may be misaligned at N1. In this case, N1 may have multi-panel capability or support multiple Fast Fourier Transform (“FFT”) windows to transmit Orthogonal Frequency Division Multiplexing (“OFDM”) signals. Otherwise, N1 may need to receive signals either from the upstream / parent node N0 or from the downstream / child node N2.

[0243] To meet this requirement, N1 can handle this through proper scheduling. For example, N1 can trigger or activate a TX timing alignment mode at N2 only for resources that do not overlap with upstream operations at N1 that have their own parent node N0 in the time domain. This can be achieved, for example, by associating the control message for triggering or activating the TX timing alignment mode with a semi-persistent schedule (“SPS”) at N2 for resources that do not overlap with upstream operations at N1 in the time domain.

[0244] In cases where requirements are not met, N1 can handle misalignment by implementing or executing signaling to report errors.

[0245] Timing alignment configurations can be associated with resource sets, a set of time slots, etc. This can be achieved, for example, by referencing a timing alignment configuration ID in a resource set configuration or by referencing a resource set configuration ID in a timing alignment mode configuration. In an embodiment, a timing alignment configuration is associated with a semi-persistent scheduler (SPS). This can be achieved, for example, by referencing a timing alignment ID in an SPS-Config IE extension or by referencing an SPS configuration ID (e.g., sps-ConfigIndex-r16) in a timing alignment configuration. Alternatively, the association can be signaled via an activation or trigger message as described later.

[0246] Based on the above capabilities and considerations, timing alignment configurations can be sent to IAB nodes, such as IAB node N2 and / or parent node N1. Configurations may include:

[0247] a. Identifier (ID)

[0248] b. The type of timing alignment, such as TX timing alignment mode.

[0249] c. Indicates whether the configuration is the default parameter.

[0250] d. Parameters, which indicate timing alignment:

[0251] i. Periodic or semi-static

[0252] ii. Semi-persistent, for example, activated or deactivated by MAC-CE signaling.

[0253] iii. Irregular, for example, triggered by DCI signaling,

[0254] e. Parameters used for MAC-CE or DCI signaling, such as bit width.

[0255] f. Parameters used for validity timing, such as slot offset, number of slots, or timer expiration value.

[0256] g. Association with a set of resources, a set of time slots, semi-persistent scheduling (SPS), etc.

[0257] h. Range of resolution parameters and / or timing alignment parameters.

[0258] Regarding activation / deactivation and triggering, as previously described, control messages can activate or trigger TX timing alignment modes. Control messages can be MAC-CE messages used for semi-persistent configuration to activate or trigger periodically configured modes. In either case, the start time (e.g., slot offset) is determined by standards and / or configuration. The validity period is also determined by standards and / or configuration.

[0259] Alternatively, the timer can be specified by the standard and / or configured by the system indicating that the TX timing alignment mode is enabled / active until the timer expires. When the validity of the activation / trigger message expires or upon receiving a deactivation message, the IAB node can switch to the default timing alignment mode, which can be the Case 1 timing alignment mode specified in IAB Rel-16 or another default mode specified by the standard or by configuration.

[0260] Timing alignment activation / trigger messages can also associate timing alignment patterns or configurations with resource sets or semi-persistent schedules. In this case, the message may include information about the timing alignment pattern or configuration (e.g., a first ID), information about the resource set or semi-persistent schedule (e.g., a second ID), validity timing information, and so on.

[0261] It should be noted that switching from one timing alignment mode to another can cause problems at resource boundaries (e.g., slot boundaries). For example, if an IAB node is executing a timing alignment that requires a slot / symbol to start later, followed by another timing alignment that requires a slot / symbol to start relatively earlier, then at least one symbol at the timing alignment switch boundary may be left with a duration shorter than the symbol duration by an interval (greater than the cyclic prefix (CP)). This can lead to incorrect symbols. This problem can be addressed through implementations, for example, by proper resource allocation during scheduling, resource availability indications, etc. Alternatively or additionally, configuration or control messages can determine the behavior of the corresponding IAB node. Consider an instance where a first slot with a first timing alignment occurs exactly before a second slot with a second timing alignment. The configuration or control message can then specify ignoring the last symbol of the first slot or the first symbol of the second slot. The node receiving the configuration or control message can then refuse to transmit or receive signals on the ignored symbol or treat the symbol as unavailable (NA).

[0262] Regarding timing alignment in dual-connectivity scenarios, when an IAB node has multiple parents, such as in dual-connectivity (“DC”), timing alignment with one parent can lead to misalignment with another parent. If an IAB node communicates with one parent at a time, it is expected to perform timing alignment with that parent. However, if an IAB node communicates with multiple parents simultaneously, such as in an FDM scheme, appropriate mechanisms should be in place to ensure correct timing alignment with all parents.

[0263] Consider an instance where IAB node N2 is connected to two parent nodes: primary node (MN) N1 and secondary node (SN) N1'. In this embodiment, N2 always follows the timing alignment with N1. This continues as long as the link between N2 and N1 is operational. In the event of a radio link failure (RLF) between N2 and N1, N2 may switch to follow the timing alignment with N1'.

[0264] In another embodiment, N2 maintains the timing alignment configuration with both N1 and N1'. For example, N2 maintains T delta The different values ​​of T and other timing alignment parameters associated with the link between N2 and any of N1 and N1'. In the case of timing alignment configured by RRC, N2 may maintain a separate configuration with each of N1 and N1', or it may maintain the same configuration and reuse it with the link with N1', possibly with different parameters, such as T delta .

[0265] In an embodiment where communication between links N2-N1 and N2-N1' is time-multiplexed, the protection symbol may be applied as previously explained, i.e., the last symbol of the first time slot or the first symbol of the second time slot, which are consecutive and associated with communication with different parent nodes, may be ignored.

[0266] Figure 12A and 12B This diagram illustrates one embodiment of receive timing alignment (Case 7): principle (12A) and example timeline (12B). Another method for timing alignment within an IAB node is to align simultaneous downlink and uplink reception. This method is useful, for example, in an FDM scheme, for achieving simultaneous reception and baseband processing at an IAB node with a single antenna panel connected to a single RF chain. Since the timing of downlink transmission is expected to be aligned across IAB nodes (i.e., Case 1), this leads to what is known in IAB research projects as timing alignment Case 7.

[0267] Figure 13 This diagram illustrates one embodiment of RX timing alignment by allowing negative TA. In some embodiments, case 7 can be implemented, thereby introducing a "negative TA". Essentially, if RX timing alignment is to be applied at N2, then the timeline will be as shown in the diagram below. In the example on the left, timing advance is positive, while in the example on the right, it is negative.

[0268] A method for implementing RX timing alignment for an IAB node may include the following steps. First, the IAB node obtains the DL RX timing from its parent node based on NRRel-15 and IAB Rel-16, and advances the timing (TA) and T. delta Transmitted to child nodes. Furthermore, the IAB node transmits additional timing advance, which we abbreviate as ATA in this disclosure. Then, in different embodiments, the child node sets its UL TX timing to ATA, TA+ATA, or earlier than its DL RX timing. The values ​​for are as follows. The methods used for IAB nodes and their child nodes can be summarized below.

[0269] Method for IAB node N2:

[0270] a. Obtain DL RX(T) by receiving the reference signal. dl,rx (time series)

[0271] b. Transmission Timing Advancement (TA) Command

[0272] c. Transmission T delta value

[0273] d. Transmit Additional Timing Advancement (ATA) command

[0274] e. Using time sequence Tdl,rx Receive downlink signals

[0275] f. Using time sequence T ul,rx :=T dl,rx Receive uplink signals

[0276] Method for child node N3:

[0277] a. Receive timing advance (TA) command

[0278] b. Receive T delta value

[0279] c. Receive Additional Timing Advancement (ATA) commands

[0280] d. Advance ATA or TA+ATA by timing sequence or Transmit uplink signals

[0281] Note that in the above method:

[0282] a. For the sake of brevity, the process of obtaining DL TX timing alignment according to IAB Rel-16 (Case 1) is omitted;

[0283] b. In the embodiments, obtaining TA and / or T may be omitted. delta The steps, in which the value is not added to ATA in different embodiments.

[0284] In these methods, the reference signal can be a synchronization signal and a physical broadcast channel (SS / PBCH) block. TA is obtained using a method similar to NR Rel-15. That is, TA = (N TA +N TA,offset ).T c , where N TA The integer N obtained from the TA command. TA,offset It is an integer offset determined by the standard / configuration, and T c It is a time unit defined by a standard. In the NR system, we obtain T. c = 0.509ns.

[0285] T delta The value can be signaled by the parent node (in this instance, by N1) according to IAB Rel-16. In some embodiments, T can be used. delta linear functions (e.g., (N) delta +T delta ·G step )) to replace T delta Additional item N delta and multiplication factor G stepIt can be obtained from signaling or specifications and can be different for different frequency ranges and / or subcarrier spacing.

[0286] Child node N3 receives an additional / alternative timing advance value ATA = N ATA .T c , where N ATA These are parameters received from IAB node N2. Typically, N... ATA The possible values ​​are positive, zero, or negative. N can be configured. ATA The range and resolution. N ATA The value of N can be calculated based on a fixed or configurable table. ATA The value can be calculated as the sum of the first and second terms, where the first term is a constant or semi-statically configured variable, and the second term is dynamically signaled.

[0287] We obtain the following examples of values ​​for applying ATA.

[0288] Example A: Timing Alignment via ATA

[0289] a. In the embodiment, child node N3 directly applies the timing advance value ATA = N. ATA .T c , where N ATA These are parameters received from IAB node N2.

[0290] Example B: Timing alignment via TA+ATA

[0291] a. In another embodiment, child node N3 advances the timing value ATA = N ATA .T c It is applied as an additional item to the old time advance value TA.

[0292] Example C: According to Perform timing alignment

[0293] a. In yet another embodiment, child node N3 advances the timing value ATA = N ATA .T c It is applied as an additional option to the DL TX timing specified in IABre-16 (Case 1).

[0294] In some embodiments, one of embodiments A, B, and C may be determined by signaling.

[0295] As previously noted, the enhanced IAB system is expected to be able to apply different timing alignment modes. This will be explained in more detail in the following sections. Furthermore, we can extend the above approach with signaling that allows enabling or disabling timing alignment modes. This signaling can be a MAC-CE message for semi-persistent activation or deactivation of timing alignment modes, a downlink control information (DCI) message for triggering timing alignment modes within a period of time, such as one or more time slots, or other signaling.

[0296] Method for IAB node N2:

[0297] a. Obtain DL RX(T) by receiving the reference signal. dl,rx (time series)

[0298] b. Transmission Timing Advancement (TA) Command

[0299] c. Transmission T delta value

[0300] d. Transmit control messages to trigger / activate RX timing alignment (Case 7)

[0301] e. Transmit Additional Timing Advancement (ATA) command

[0302] f. Using time sequence T dl,rx Receive downlink signals

[0303] g. Using time series T ul,rx :=T dl,rx Receive uplink signals

[0304] Method for child node N3:

[0305] a. Receive timing advance (TA) command

[0306] b. Receive T delta value

[0307] c. Receive control messages to trigger / activate RX timing alignment (Case 7)

[0308] d. Receive Additional Timing Advance (ATA) commands

[0309] e. Advance ATA or TA+ATA by timing sequence or Transmit uplink signals

[0310] Similar to the case of TX timing alignment, the control message that triggers or activates the TX timing alignment mode can be a MAC-CE message, a DCI message, or a combination thereof.

[0311] In these methods, the application of the RX timing alignment mode depends on the control message received for the trigger or activation mode. Therefore, child node N3 can apply the default timing alignment mode for resource / slot R (e.g., timing advance) according to NR Rel-15 in the following cases:

[0312] a. No control message received.

[0313] b. A control message is received, but it is not associated with resource / slot R.

[0314] c. A control message is received, but it expires before the resource / slot R is transmitted because the timer associated with the control message has expired.

[0315] d. A control message was received, but it expired due to the subsequent receipt of a deactivation control message. The deactivation control message can be a MAC-CE message, a DCI message, or a combination thereof.

[0316] The implementation of the method proposed for child nodes can also be applied to enhanced UEs.

[0317] It should be noted that in the IAB system, downstream communication / operation (i.e., DL TX and / or UL RX) is performed by the IAB-DU in the parent IAB node or IAB donor, and downstream communication / operation (i.e., DL RX and / or UL TX) is performed by the IAB-MT in the IAB node or by the enhanced UE.

[0318] Figure 14 This is a block diagram illustrating an example embodiment of a method for RX timing alignment at a child node (N3) or an enhanced UE. In this example, according to embodiment B, it is assumed that ATA is applied by the child node (CN) or the enhanced UE (eUE).

[0319] In this example, method 1400 begins and the CN / eUE obtains the timing 1405 of the DLRX by receiving a reference signal (e.g., a synchronization signal), similar to the method specified for NR Rel-15. Next, the CN / eUE obtains the value 1410 of timing advance (TA), similar to the method specified for NR Rel-15. Then, the CN / eUE receives the value 1415 of additional timing advance (ATA).

[0320] Next, the CN / eUE determines whether the RX timing alignment mode is activated or triggered 1420. If the RX timing alignment mode is activated or triggered, the CN / eUE performs UL TX 1425 with timing set before (TA+ATA) obtained from the DL RX timing. Otherwise, the CN / eUE performs UL TX 1430 with default timing (e.g., timing set before TA obtained from the DL RX timing), and method 1400 ends.

[0321] In any of the embodiments discussed in this section, T may be used. delta linear functions (e.g., (N) delta +T delta ·G step )) to replace T delta Additional item N delta and multiplication factor G step It can be obtained from signaling or specifications and can be different for different frequency ranges and / or subcarrier spacing.

[0322] By extension, any timing alignment parameter T in this disclosure can be signaled or applied by a linear function of the parameter (e.g., N+TG), wherein the additional term N and / or the multiplication factor G can be obtained by signaling or by specification and can be different for different frequency ranges and / or subcarrier spacings.

[0323] Any of the timing alignment methods and embodiments proposed in this disclosure can be associated with a timing advance group (“TAG”) identifier (“ID”) via configuration or control message signaling. Thus, when the timing alignment method is applied, the IAB node employing the timing alignment method uses a timing advance (“TA”) parameter associated with the TAG ID.

[0324] Regarding configuration, timing alignment modes (such as the previously proposed RX timing alignment mode) can be fully specified by the standard, and capabilities can be defined by the standard specification. Alternatively, timing alignment modes can be configured by the IAB system, such as by the IAB-CU, to become operational. First and foremost, since Rel-16 IAB nodes only support Case 1 timing alignment, the RX timing alignment at the IAB node can depend on capability parameters associated with N2 and / or N3 (or enhanced UE), which demonstrate the node's enhancements according to the Rel-17+ specification. Configuration can also depend on other capabilities, such as multi-panel or simultaneous operation capabilities, which can be signaled to the IAB-CU or stored offline in the system.

[0325] For example, when timing alignment is used for reception at N2, signal transmission in the upstream and downstream may be misaligned at N3. In this case, N3 may have multi-panel capability or support multiple Fast Fourier Transform (FFT) windows to transmit Orthogonal Frequency Division Multiplexing (OFDM) signals. Otherwise, N3 may need to transmit the signal to either the upstream / parent node N2 or the downstream / child node (N4 or UE) in one transmission.

[0326] To meet this requirement, the RX timing alignment mode is triggered or activated by N2 only for resources that do not overlap with downstream operations at N3 or the UE, which have their own child node N4, in the time domain. For example, N2 may trigger or activate the RX timing alignment mode for resources indicated as unavailable (NA). In this case, N3 is expected to receive a control message from N2 that triggers or activates the RX timing alignment mode for hard or soft resources indicated as available by an availability indication (AI) message from N2. In an embodiment, after receiving the control message for triggering or activating RX timing alignment for a resource, N3 treats the resource as unavailable (NA).

[0327] Alternatively, N3 can handle this through proper scheduling. This can be achieved, for example, by associating control messages from N2 that trigger or activate RX timing alignment modes with semi-persistent scheduling (SPS), allowing N3 to avoid overlap through proper scheduling.

[0328] In cases where requirements are not met, N3 can handle misalignment by implementing or executing signaling to report errors.

[0329] Timing alignment configurations can be associated with resource sets, a set of time slots, etc. This can be achieved, for example, by referencing a timing alignment configuration ID in a resource set configuration or by referencing a resource set configuration ID in a timing alignment mode configuration. In an embodiment, a timing alignment configuration is associated with a semi-persistent scheduler (SPS). This can be achieved, for example, by referencing a timing alignment ID in an SPS-Config IE extension or by referencing an SPS configuration ID (e.g., sps-ConfigIndex-r16) in a timing alignment configuration. Alternatively, the association can be signaled via an activation or trigger message as described later.

[0330] Based on the above capabilities and considerations, timing alignment configurations can be sent to IAB nodes, such as IAB node N2 and / or child node N3. Configurations may include:

[0331] a. Identifier (ID)

[0332] b. Timing alignment type, such as RX timing alignment mode.

[0333] c. Indicates whether the configuration is the default parameter.

[0334] d. Parameters, which indicate timing alignment:

[0335] e. Periodic or semi-static,

[0336] f. Semi-persistent, for example, activated or deactivated by MAC-CE signaling.

[0337] g. Irregular, for example, triggered by DCI signaling,

[0338] h. Parameters used for MAC-CE or DCI signaling, such as bit width.

[0339] i. Parameters used for validity timing, such as slot offset, number of slots, or timer expiration value.

[0340] j. Association with a set of resources, a set of time slots, semi-persistent scheduling (SPS), etc.

[0341] k. Range of resolution parameters and / or timing alignment parameters.

[0342] Regarding activation / deactivation and triggering, as previously described, control messages can activate or trigger RX timing alignment modes. Control messages can be MAC-CE messages used for semi-persistent configuration to activate or trigger periodically configured modes. In either case, the start time (e.g., slot offset) is determined by standards and / or configuration. The validity period is also determined by standards and / or configuration.

[0343] Alternatively, the timer can be specified by the standard and / or configured by the system indicating that the RX timing alignment mode is enabled / active until the timer expires. Upon the expiration of the activation / trigger message or upon receiving a deactivation message, the IAB node can switch to the default timing alignment mode, which can be the Case 1 timing alignment mode specified in IAB Rel-16 or another default mode specified by the standard or by configuration.

[0344] Timing alignment activation / trigger messages can also associate timing alignment patterns or configurations with resource sets or semi-persistent schedules. In this case, the message may include information about the timing alignment pattern or configuration (e.g., a first ID), information about the resource set or semi-persistent schedule (e.g., a second ID), validity timing information, and so on.

[0345] It should be noted that switching from one timing alignment mode to another can cause problems at resource boundaries (e.g., slot boundaries). For example, if an IAB node is executing a timing alignment that requires a slot / symbol to start later, followed by another timing alignment that requires a slot / symbol to start relatively earlier, then at least one symbol at the timing alignment switch boundary may be left with a duration shorter than the symbol duration by an interval (greater than the cyclic prefix (CP)). This can lead to incorrect symbols. This problem can be addressed through implementations, for example, by proper resource allocation during scheduling, resource availability indications, etc. Alternatively or additionally, configuration or control messages can determine the behavior of the corresponding IAB node. Consider an instance where a first slot with a first timing alignment occurs exactly before a second slot with a second timing alignment. The configuration or control message can then specify ignoring the last symbol of the first slot or the first symbol of the second slot. The node receiving the configuration or control message can then refuse to transmit or receive signals on the ignored symbol or treat the symbol as unavailable (NA).

[0346] Figure 15 This is a diagram illustrating an example of an additional timing advance command. The additional timing advance command can be a MAC-CE message. In this example, the MAC-CE message includes two octets, with 12 bits from these two octets used for N. ATA The value is specified, and 4 bits are reserved (“R”). The standard can specify the number of octets, N ATA The number of digits, the number of digits retained, the multiplication factor, and / or additional terms to calculate the ATA value and / or how to apply the ATA value according to Example A, Example B, or Example C as previously described. ATA The value can be represented as a signed integer to allow negative values ​​for ATA. Additional timing advance commands (MAC CE) can be assigned a separate logical channel identifier (“LCID”) value.

[0347] Regarding omissions and shift signs, as previously shown, the timing advance value used to apply RX timing alignment at the parent node can be negative, depending on the propagation delay. Negative timing advance is essentially the UL TX with respect to the DL RX timing delay. Delayed transmission of a time slot can lead to conflicts with the next time slot, especially when the delay exceeds the CP duration.

[0348] When the timing advance is negative, let D represent positive delay. For example, for "Example A" and "Example B" as described above, D = -ATA and D = -(TA + ATA) respectively.

[0349] In this embodiment, when negative timing advance is performed by child node N3, the transmission of the last symbol can be omitted. When the delay is longer than the symbol duration, N3 can be omitted. The transmission of symbols, where T symIndicates the duration of the symbol containing CP.

[0350] In another embodiment, N3 omits the transmission of the last symbol only if the transmission of the last symbol conflicts with an operation in the next time slot. Otherwise, it transmits the last symbol.

[0351] For example, for compatibility reasons, it might be undesirable to apply negative timing advance. Therefore, in an embodiment, if D is not greater than the symbol duration T... sym Then child node N3 can apply positive timing advance T. sym -D, and shifts the scheduled channels and signals in the time slot backward by one symbol duration relative to the start time of the time slot. This shift is essentially a delay of one symbol duration to correct the reception timing at IAB node N2. Since each symbol is delayed by one symbol duration, the last symbol of the time slot can be omitted.

[0352] It is important to note that when a signal is shifted by one symbol, the symbol index used to calculate the signal (e.g., the probe reference signal (“SRS”)) must be the original symbol index value, i.e., the value before the shift. For example, for an SRS configured on a symbol with index l, the symbol index used for SRS calculation is still l, but the symbol used for SRS transmission is l+1. As mentioned earlier, if l is the index of the last symbol in the time slot, then SRS transmission can be omitted in this example.

[0353] When D is greater than the symbol duration T sym In this case, the proposed shifting method can be applied to X symbols instead of 1 symbol, where In an alternative embodiment, child node N3 may apply positive timing advance XT. sym -D, and shifts the channel and signal scheduled in the time slot backward by X symbol durations relative to the start time of the time slot. Since each symbol is delayed by X symbol durations, the last X symbols of the time slot can be omitted. Similar to the special case described earlier, the symbol index used to calculate the signal (e.g., the sounding reference signal (SRS)) must use the original symbol index value, i.e., the value before the shift. For example, for an SRS configured on a symbol with index l, the symbol index used for SRS calculation is still l, but the symbol used for SRS transmission is l+X. If l+X falls beyond the time slot boundary, then the SRS transmission can be omitted in this example.

[0354] The process of converting a negative timing alignment to a positive timing alignment, plus the shifting, can be handled by IAB node N2 or child node N3. Different embodiments are described below.

[0355] Figure 16This is a diagram illustrating an example of an additional timing advance command with a sign shift indication. In this embodiment, N2 ensures that the timing advance provided to child node N3 is always non-negative. In cases where negative timing advance is required, for example, where ATA is negative in "Example A", N2 sends T along the indication. sym +ATA's positive timing advance value shifts the symbol by one symbol duration. N3 can use, for example... Figure 16 The MAC-CE message shown in the image.

[0356] In this example, N3 applies positive timing advance according to the command. Furthermore, if shift = '1', then N3 shifts the symbols in the time slot as previously described.

[0357] In the case of shifting X symbols, N2 sends a positive timing advance value XT along with the indication from N3 that the number of symbols to be shifted is X. sym +ATA. In this case, the parameter shift can occupy more than one bit and represent the value of X.

[0358] In some embodiments, if the timing advance value calculated according to Embodiment A, Embodiment B or Embodiment C is negative, then it is not desirable for N3 to apply a negative timing advance value and instead apply zero timing advance.

[0359] Figure 17 This is a block diagram illustrating an example embodiment of a method for performing RX timing alignment (transformation at N2) using symbol shifting at a child node (N3) or an enhanced UE. The method can be substantially similar to... Figure 14 The method described herein, for example, an example embodiment of the proposed "transformation at N2" method, has an additional step 1730 for shifting one symbol. In this example, according to embodiment B, it is assumed that ATA is applied by a child node ("CN") or an enhanced UE (eUE).

[0360] In this example, method 1700 begins and the CN / eUE obtains the timing 1705 of the DLRX by receiving a reference signal (e.g., a synchronization signal), similar to the method specified for NR Rel-15. Next, the CN / eUE obtains the value 1710 of timing advance (“TA”), similar to the method specified for NR Rel-15. Then, the CN / eUE receives the value 1715 of additional timing advance (“ATA”).

[0361] Next, the CN / eUE determines whether the RX timing alignment mode is activated or triggered (1720). If the RX timing alignment mode is activated or triggered, the CN / eUE performs UL TX (1725) with timing set before the DL RX timing (TA+ATA), and if the shift is 1, the CN / eUE shifts / delays all symbols by one symbol duration (1730). Otherwise, the CN / eUE performs UL TX (1735) with default timing (e.g., timing set before the DL RX timing (TA)), and method (1700) ends.

[0362] Figure 18 This is a block diagram illustrating an example embodiment of a method for performing RX timing alignment (transformation at N3) using symbol shifting at a child node (N3) or an enhanced UE. In this embodiment, N2 transmits an additional timing advance value, which can result in a negative timing advance value as calculated by N3 according to Embodiment A, Embodiment B, or Embodiment C. N3 then applies the timing advance T. sym -D, and shifts the sign by one sign duration, as previously described. When D is greater than the sign duration T... sym In this case, the N3 application timing is advanced by XT sym -D and shift the sign by X signs, as previously described.

[0363] The diagram depicts an example embodiment of the proposed method of "converting at N3" and shifting one symbol. In this example, according to embodiment B, it is assumed that ATA is applied by a child node ("CN") or an enhanced UE ("eUE").

[0364] In this example, method 1800 begins and the CN / eUE obtains the timing 1805 of the DLRX by receiving a reference signal (e.g., a synchronization signal), similar to the method specified for NR Rel-15. Next, the CN / eUE obtains the value 1810 of timing advance (“TA”), similar to the method specified for NR Rel-15. Then, the CN / eUE receives the value 1815 of additional timing advance (“ATA”).

[0365] Next, the CN / eUE determines whether the RX timing alignment mode is activated or triggered (1820). If the RX timing alignment mode is activated or triggered, the CN / eUE determines (1825) whether TA+ATA ≥ 0. If so, the CN / eUE executes (1830) to set the UL TX timing ahead of the DL RX timing by (TA+ATA). Otherwise, the CN / eUE performs a shift / delay of all symbols by one symbol duration (1835). Then, the CN / eUE sets the UL TX timing (1845) to be ahead of the DL RX timing by (T...). sym+TA+ATA). Otherwise, CN / eUE performs UL TX 1430 with the default timing (e.g., set to the timing of TA before obtaining the DL RX timing), and method 1800 ends.

[0366] Regarding timing alignment in dual-connectivity scenarios, when an IAB node has multiple parents, such as in dual-connectivity (“DC”), timing alignment with one parent can lead to misalignment with another parent. If an IAB node communicates with one parent at a time, it is expected to perform timing alignment with that parent. However, if an IAB node communicates with multiple parents simultaneously, such as in an FDM scheme, appropriate mechanisms should be in place to ensure correct timing alignment with all parents.

[0367] Consider an instance where child node N3 is connected to two IAB nodes: the primary node (“MN”) N2 and the secondary node (“SN”) N2'.

[0368] In this embodiment, N3 always follows the timing alignment with N2. This continues as long as the link between N3 and N2 is operational. In the event of a radio link failure (“RLF”) between N3 and N2, N3 may switch to follow the timing alignment with N2'.

[0369] In another embodiment, N3 maintains a timing alignment configuration with both N2 and N2'. For example, N3 maintains different values ​​for ATA and other timing alignment parameters associated with the link between N3 and either N2 or N2'. In the case of timing alignment configured by RRC, N3 may maintain a separate configuration with each of N2 and N2', or it may maintain the same configuration and reuse it for the link with N2', possibly with different parameters, such as ATA.

[0370] In an embodiment where communication between N3-N3 and N3-N2' links is time-multiplexed, the protection symbol can be applied as previously explained, i.e., the last symbol of the first time slot or the first symbol of the second time slot, which are consecutive and associated with communication with different parent nodes, can be ignored.

[0371] Regarding the acquisition of the ATA value, when child node N3 executes the random access procedure, IAB node N2 obtains the initial UL Rx timing and normal timing advance (TA) information (equivalently, estimated propagation delay) from the received PRACH preamble. IAB node N2 uses the estimated propagation delay (e.g., obtained from PRACH preamble detection) and the UL signal subsequently received from child node N3 (e.g., PUSCH DMRS) to further align the UL Rx timing to the reference UL timing. The normal TA value is based on being set to T. dl,tx Reference UL Rx timing T ul,rxTo calculate.

[0372] When a timing alignment scheme is enabled for IAB node N2 (Case 7), IAB node N2 can reference the UL Rx timing T. ul,rx Set to DL Rx timing T dl,rx ATA is based on being set to T. dl,rx Reference UL Rx timing T ul,rx To calculate.

[0373] Regarding the unified timing alignment framework, it has been demonstrated so far that the proposed timing alignment methods for TX and RX timing alignment modes are universal in terms of configuration, signaling, and behavior. In this section, we provide a unified timing alignment framework that can be used for different timing alignment modes.

[0374] The previously proposed method can be extended to a unified timing alignment method, such as Figures 19 to 21 Examples and implementations are depicted in the text. Figure 19 This is a block diagram illustrating an example embodiment of a method for unified timing alignment at IAB nodes.

[0375] In this example, method 1900 begins and the CN / eUE obtains the timing 1905 of DLRX by receiving a reference signal (e.g., a synchronization signal), similar to the method specified for NR Rel-15. Next, the CN / eUE obtains the value 1910 of timing advance (“TA”), similar to the method specified for NR Rel-15. Then, the CN / eUE receives T... delta The value is 1915.

[0376] Next, CN / eUE determines whether the RX timing alignment mode is activated or triggered. If the RX timing alignment mode is activated or triggered, then CN / eUE determines T:=a.TA+bT. delta +c.ATA 1925. The CN / eUE sets the UL TX timing to 1930, which is T ahead of the DL RX timing. Otherwise, the CN / eUE executes UL TX 1935 with the default timing (e.g., the timing set to the time before TA is obtained from the DL RX timing), and method 1900 ends.

[0377] Figure 20 This is a block diagram illustrating an example embodiment of a method for performing uniform timing alignment at IAB nodes using sign shifting and transformations at the parent node of the IAB node.

[0378] In this example, method 2000 begins and the CN / eUE obtains the timing 2005 of DLRX by receiving a reference signal (e.g., a synchronization signal), similar to the method specified for NR Rel-15. Next, the CN / eUE obtains the timing advance (TA) value 2010, similar to the method specified for NR Rel-15. Then, the CN / eUE receives T... delta The value 2015 and the received value include N ATA And the ATA shift command and set ATA:=N ATA .Tc 2020.

[0379] Next, CN / eUE determines whether the RX timing alignment mode is activated or triggered. If the RX timing alignment mode is activated or triggered, then CN / eUE determines T:=a.TA+bT delta +c.ATA 2030. CN / eUE sets the UL TX timing to be T 2035 ahead of the DL RX timing. CN / eUE shifts / delays all symbols by one symbol duration T. sym 2040. Otherwise, CN / eUE performs UL TX 2045 with the default timing (e.g., set to the timing of TA before obtaining the DL RX timing), and method 2000 ends.

[0380] Figure 21 This is a block diagram illustrating an example embodiment of a method for performing uniform timing alignment at IAB nodes using sign shifting and transformations at IAB nodes.

[0381] In this example, method 2100 begins and the CN / eUE obtains the timing 2105 of DLRX by receiving a reference signal (e.g., a synchronization signal), similar to the method specified for NR Rel-15. Next, the CN / eUE obtains the value 2110 of timing advance (TA), similar to the method specified for NR Rel-15. Then, the CN / eUE receives T... delta The value 2115 and the received value include N ATA And the ATA shift command and set ATA:=N ATA .Tc 2120.

[0382] Next, CN / eUE determines whether the RX timing alignment mode is activated or triggered. If the RX timing alignment mode is activated or triggered, then CN / eUE determines T:=a.TA+bT. delta +c.ATA 2130. CN / eUE determines whether TA ≥ 0.2135. If so, CN / eUE sets the UL TX timing to be T 2035 ahead of the DL RX timing. Otherwise, CN / eUE shifts / delays all symbols by one symbol duration T.sym 2145 and setting the UL TX timing to be ahead of the DL RX timing (T) sym +T)2150. Otherwise, CN / eUE performs UL TX2155 with the default timing (e.g., set to the timing of TA before obtaining the DL RX timing), and method 2100 ends.

[0383] In these instances, the IAB node can obtain the values ​​of a, b, and c through standard specifications, configuration, and / or control signaling.

[0384] Instance values ​​are provided in the table below.

[0385] 1 0 0 The old time sequence was advanced (possible case 1). 0.5 1 0 TX timing alignment (Case 6) 0 0 1 RX timing alignment (Case 7), Example A 1 0 1 RX timing alignment (Case 7), Example B 0.5 1 1 RX timing alignment (Case 7), Example C

[0386] Table 4.

[0387] Regarding configuration, timing alignment patterns can be fully specified by the standard, and capabilities can be defined by the standard specification. Alternatively, they can be configured by the IAB system, such as by the IAB-CU, to become operational. Below is an example of capabilities / features used for timing alignment configuration that can be reported to the IAB-CU via RRC messages (or stored offline in the system).

[0388]

[0389]

[0390] Table 5.

[0391] Timing alignment configurations from the IAB-CU can include the following RRC IEs:

[0392] a. Identifier (ID)

[0393] b. Timing alignment type, such as TX or RX timing alignment mode.

[0394] c. Indicates whether the configuration is the default parameter.

[0395] d. Parameters, which indicate timing alignment:

[0396] e. Periodic or semi-static,

[0397] f. Semi-persistent, for example, activated or deactivated by MAC-CE signaling.

[0398] g. Irregular, for example, triggered by DCI signaling,

[0399] h. Parameters used for MAC-CE or DCI signaling, such as bit width.

[0400] i. Parameters used for validity timing, such as slot offset, number of slots, or timer expiration value.

[0401] j. Association with a set of resources, a set of time slots, semi-persistent scheduling (SPS), etc.

[0402] k. Range of resolution parameters and / or timing alignment parameters

[0403] l. Parameters indicating whether negative timing advance is allowed.

[0404] m. Parameters used to indicate the behavior of shift / delay symbols, ellipsis symbols, guard symbol count, etc.

[0405] Timing adjustments for Cross-Link Interference (“CLI”) management are specified in a separate work item (“WI”) from the IAB in NR Rel-16. The specification provides means for UE-UE interference measurement and reporting. UEs can be configured to monitor one or both of the following:

[0406] a. A sounding reference signal (“SRS”), transmitted by another UE, is used to measure the reference signal received power (“RSRP”).

[0407] b. A set of time-frequency resources for measuring the received signal strength indicator (“RSSI”).

[0408] Regarding the first scenario, in principle, the measuring UE might need to know the alignment requirements with the UE transmitting the SRS. However, CLI Rel-16 WI concludes that timing alignment for CLI measurements is an implementation issue and is not specified in the standard. The main reason for that conclusion is the signaling overhead required to obtain timing information between the two UEs.

[0409] Unlike UEs, given that IAB node MTs are part of the backhaul system and transmit and receive service signals from a potentially large number of UEs, CLI measurement accuracy is significantly more critical to ensure effective communication in ultra-dense deployments. This trigger signaling is used for accurate timing alignment of CLI management across the IAB network.

[0410] CLI management will be extended for IAB in future versions. Similar to UE-UE CLI management, if timing alignment is left to the implementation, then the specification impact on MT-MT CLI management can be minimized. However, the limitations used to obtain timing alignment information between UEs may not apply to the MT. IAB nodes transmit synchronization signals (SS) through their DUs in the downlink. If the timing relationship between the DU and MT in the IAB node is known, then it provides a source of timing information for CLI management that is not available to the UE. The remaining issue is that while this timing information may be sufficient for receiving downlink signals from the IAB node, it may not be sufficient for uplink signals, given that there may be different downlink and uplink timing alignments at the IAB node.

[0411] This paper describes a solution to address the problem of obtaining CLI timing alignment in an IAB network. In an embodiment for obtaining timing alignment to receive uplink reference signals, uplink timing acquisition is assisted by downlink timing information obtained from synchronization signals.

[0412] As background information, the SRS resources defined in Clause 6.4.1.4 of [4, TS 38.211] can be configured for SRS-RSRP measurement using CLI, as defined in Clause 5.1.19 of [7, TS 38.215]. It is undesirable for the UE to measure SRS-RSRP at subcarrier intervals other than those configured for the effective BWP for limiting SRS resources. It is also undesirable for the UE to measure more than 32 SRS resources, and for the UE to receive more than 8 SRS resources in a single timeslot.

[0413] As used herein, the SRS reference signal received power (“SRS-RSRP”) may refer to the linear average of the power distribution (in [W]) of the resource element carrying the probe reference signal (“SRS”). The SRS-RSRP should be measured for the configured resource element within the considered measurement frequency bandwidth during the configured measurement timing.

[0414] For frequency range 1, the reference point for SRS-RSRP should be the UE's antenna connector. For frequency range 2, SRS-RSRP should be measured based on the combined signal from the antenna element corresponding to a given receiver branch. For both frequency ranges 1 and 2, if receiver diversity is being used by the UE, the reported SRS-RSRP value should not be lower than the corresponding SRS-RSRP of any individual receiver branch. This applies to RRC_CONNECTED intra-frequency.

[0415] As used herein, the CLI Received Signal Strength Indicator (“CLI-RSSI”) may refer to the CLI Received Signal Strength Indicator (“CLI-RSSI”), which is defined as the linear average of the total received power (in [W]) observed only in the configured OFDM symbols of the configured measurement time resources within the configured measurement bandwidth from all sources (including co-channel serving and non-serving cells, adjacent channel interference, thermal noise, etc.).

[0416] For frequency range 1, the reference point for RSSI should be the UE's antenna connector. For frequency range 2, CLI-RSSI should be measured based on the combined signal from the antenna element corresponding to a given receiver branch. For both frequency ranges 1 and 2, if receiver diversity is being used by the UE, the reported CLI-RSSI value should not be lower than the corresponding CLI-RSSI of any of the individual receiver branches. This applies to RRC_CONNECTED co-frequency.

[0417] Figure 22 This is a diagram illustrating an example embodiment of a scenario using IAB system 2200. Consider a scenario where IAB node N1 (victim) 2202 is configured to monitor SRS resources from IAB node N2 (aggressor) 2204, as illustrated in the diagram. Figure 23 The timing alignment method described herein may result in misalignment of uplink and downlink transmissions of N2 2204, particularly transmissions containing SSB (and / or CSI-RS (e.g., periodic CSI-RS, such as TRS-tracking RS)) and SRS.

[0418] Figure 23 This diagram illustrates an example of a timing misalignment between uplink and downlink transmissions. Note that the uplink and downlink transmissions may or may not be on the same frequency depending on whether they are configured for Time Division Duplex (“TDD”) or Frequency Division Duplex (“FDD”).

[0419] refer to Figure 22N1 2202 may be interested in detecting synchronization signal blocks (“SSBs”) (and / or CSI-RS (e.g., periodic CSI-RS, such as TRS-tracking RS)) from N2 2204 in order to obtain downlink timing information (“DLTI”) from N2 2204. The SSB may include synchronization signals (“SSs”) (e.g., primary synchronization signal (“PSS”) and secondary synchronization signals (“SSS”)) and a physical broadcast channel (“PBCH”) containing system information. Furthermore, N1 2202 may also be interested in obtaining uplink timing information (“ULTI”) from N2 2204. Once N1 2202 obtains the ULTI, it can perform proper timing alignment to measure the uplink signal power from N2 2204, such as SRS-RSRP.

[0420] There are two possibilities regarding whether N1 2202 is configured with an SSB-based measurement timing configuration (“SMTC”) that overlaps with the SSB transport configuration (“STC”) used for N2 2204. If N1-SMTC overlaps with N2-STC, then N1 2202 can obtain DLTI from N2 2204. N1 2202 should then obtain information about timing misalignment between the downlink transmission of N2 2204 containing SSB and the uplink transmission of N2 2204 containing SRS configured by N1 2202 for measurement. For example, this information can be calculated and transmitted by N2 2204.

[0421] Once N1 2202 obtains the misalignment information, it can apply the information and perform measurements on the SRS transmitted by N2 2204. In another example, N1 2202 can determine the DL TI from N2 2204 by means of a measurement gap configured to overlap with the CSI-RS (e.g., periodic CSI-RS, such as TRS-tracking RS) transmission configuration for N2 2204.

[0422] Examples of relationships between time series are as follows:

[0423] a. For scenario 1, it is compatible with IAB Rel-16 at attacker node N2:

[0424] i. SSB Tx timing at N2-DU:

[0425] ii. SRS Tx timing at N2-MT: T ul,tx =T dl,rx -TA

[0426] b. For case 6 (TX timing aligned at N2):

[0427] i. SSB Tx timing at N2-DU:

[0428] ii. SRS Tx timing at N2-MT:

[0429] c. For case 7 (RX timing aligned at the parent node of N2), Example A:

[0430] i. SSB Tx timing at N2-DU:

[0431] ii. SRS Tx timing at N2-MT: T ul,tx =T dl,rx -ATA

[0432] d. For case 7 (RX timing aligned at the parent node of N2), Example B:

[0433] i. SSB Tx timing at N2-DU:

[0434] ii. SRS Tx timing at N2-MT: T ul,tx =T dl,rx -(TA+ATA)

[0435] e. For case 7 (RX timing aligned at the parent node of N2), Example C:

[0436] i. SSB Tx timing at N2-DU:

[0437] ii. SRS Tx timing at N2-MT:

[0438] Similar to the previous embodiment, T delta In fact, it can be presented as (N) delta +T delta ·G step )·T c Each equation determines the reference timing for the slot boundary, which means that for a time slot with a duration T... slot Given a given equation, the ':=' sign of the signal transmission timing can mean that the start time of the time slot containing the signal is equal to or differs by T from the right-hand side of the equation. slot Integer multiples thereof. Generally, this applies to all timing assignments in this disclosure.

[0439] By comparing the DL TX timing (for SSB transmission) and the UL TX timing (for SRS transmission), it can be seen that:

[0440] a. For the TX timing alignment at the attacker node N2 2204 (Case 6), no dynamic signaling is required for CLI measurements at the victim node N1 2202, except for semi-static configuration information.

[0441] b. For the IAB Rel-16 timing (case 1) and RX timing alignment (case 7) at the attacker node N2 2204, additional signaling may be required to notify the victim node N1 2202 of the timing adjustment between the DL TX timing and UL TX timing of the attacker node N2 2204.

[0442] Therefore, in this embodiment, the victim node N1 2202 may receive control messages, such as MAC-CE messages or DCI messages, from the parent node. These control messages include a timing adjustment T between the timing obtained by receiving the SSB from the attacker node N2 2204 and the timing used to perform measurements on the SRS from the attacker node N2 2204. ul-dl The information is as follows. For the above example, the timing adjustment / misalignment values ​​could be:

[0443] a. For scenario 1, it is compatible with IAB Rel-16 at attacker node N2 2204:

[0444] i.

[0445] b. For attacker node N2 2204, case 6 (TX timing alignment) (dynamic signaling may not be required):

[0446] i.

[0447] c. Regarding Case 7 (RX timing alignment) at the parent node of attacker node N2 2204, Example A:

[0448] i.

[0449] d. For case 7 (RX timing alignment) at the parent node of attacker node N2 2204, Example B:

[0450] i.

[0451] e. For case 7 (RX timing alignment) at the parent node of attacker node N2 2204, Example C:

[0452] i.

[0453] Determine T ul-dlThe fields in the control message for the values ​​can be presented as linear combinations including additional items and / or multiplication factors. They can be specified by standards and / or determined by specifications and can depend on the frequency range (“FR”) and / or numerology / SCS.

[0454] According to one embodiment, the victim IAB node (e.g. Figure 22 The N1 2202 shown in the diagram receives T from the serving cell (e.g., the parent IAB node of the victim IAB node). delta Information and the attacker's IAB node (e.g.) Figure 22 The timing advance value associated with N22204 is shown in the diagram. In one implementation, the attacker's IAB node's T... delta The information is provided to the victim IAB node via dedicated RRC signaling. In another implementation, the attacker IAB node's TA value is provided to the victim IAB node via a dedicated PDSCH containing a new MAC CE carrying the attacker's TA information. The victim IAB node may be configured with one or more attacker IAB node identifiers. The new MAC CE containing the attacker's TA information may include the attacker's identifier and the corresponding attacker's TA information, where attacker T... delta The new RRC information element can include the attacker's identifier and the corresponding attacker's T. delta information.

[0455] In another embodiment, timing adjustment / misalignment information may be broadcast by the attacker node N22204 in a broadcast channel, such as the PBCH, for example, within a system information block, and not necessarily to individual receivers. Specifically, timing adjustment / misalignment information may be contained in a PBCH included by the SSB or in a system information block (“SIB”) addressed in a PBCH included by the SSB.

[0456] Timing misalignment values ​​can be sent to the parent node of attacker 2204, the IAB donor configured by the attacker, and / or similar entities. Therefore, in Figure 22 In the example embodiment depicted, attacker node N2 2204 may send timing misalignment values ​​to other IAB nodes / donors 2206 connected to attacker node N2 2204. The timing misalignment information may then be forwarded to other IAB nodes / donors 2206 connected to attacker node N2 2202 (e.g., via connection 2220), and subsequently forwarded to victim node N1 2202 (e.g., via connection 2215).

[0457] Figure 24This is a block diagram illustrating a method for a TX IAB node (e.g., an attacker node). In one embodiment, method 2400 begins and the IAB node receives an STC 2405 from the network. The STC may be received from the radio resource control (“RRC”) layer of the parent node or may be generated by the central unit (“CU”) of the IAB donor connecting the IAB network to the core network. The IAB node receives an SRS configuration 2410 containing parameters for generating and transmitting a probe reference signal. The configuration may include a seed for generating the SRS, resource allocation for the SRS, hop information, quasi-co-location (“QCL”) information, etc. The configuration may further specify that the SRS is used for cross-link interference (“CLI”) management and may further indicate the association with the STC configuration.

[0458] The IAB node obtains timing alignment configuration and / or indication 2415 for its downlink and / or uplink transmissions. The timing alignment configuration and / or indication may or may not be associated with STC configuration (for downlink) and SRS configuration (for uplink). The IAB node may obtain this information from the IAB network or it may be pre-configured. The timing alignment information may contain timing alignment cases (e.g., Case 1, Case 6, or Case 7, as specified in the standard) or indications of the method for obtaining the timing alignment information. In the case where the RX timing alignment method (Case 7) is used at the IAB node, symbol shifting may be further applied to the SRS, as presented in previous sections.

[0459] Taking into account the timing alignment information used for the downlink and uplink, the IAB node calculates the timing misalignment value T_(ul-dl)2420 between the downlink and uplink. The IAB node may employ one of the timing alignment methods presented in previous chapters. The IAB node transmits one or more SSBs 2425 based on the received STC. Since the SSB transmission occurs in the downlink, the IAB node applies downlink timing alignment based on the previously obtained information.

[0460] The IAB node may further transmit uplink-downlink adjustment / misalignment T_(ul-dl) information 2430. This information may be broadcast, for example, as part of system information broadcast by the IAB node. Alternatively, this step may be omitted if the information is transmitted from the IAB-CU to the RX IAB node (the victim node) or if the IAB node is using TX timing alignment (case 6).

[0461] Finally, the IAB node transmits SRS 2435 according to the received SRS configuration. Since the SRS transmission occurs in the uplink, the IAB node applies downlink timing alignment based on previously obtained information. The misalignment between the downlink transmission containing the SSB and the uplink transmission containing the SRS is expected to equal the calculated timing misalignment value. The misalignment can be the difference between the start time of the slot containing the SSB and the slot containing the SRS, possibly plus or minus an integer multiple of the slot duration associated with the null / SCS, and method 2400 ends.

[0462] Figure 25 This is a block diagram illustrating a method for an RX IAB node (victim). In one embodiment, the IAB node receives an SMTC 2505 from the network. The SMTC may be received from the Radio Resource Control (RRC) layer of the parent node or may be generated by the central unit (CU) of the IAB donor that connects the IAB network to the core network.

[0463] The IAB node receives an SRS measurement configuration 2510 containing SRS generation and transmission parameters. The configuration may include SRS seed, resource allocation parameters, hop information, quasi-co-location (QCL) information, etc. Furthermore, the configuration may specify the type of measurement and reporting, such as Reference Signal Received Power (“RSRP”). ​​The configuration may further specify that the SRS is used for Cross-Link Interference (“CLI”) management and may further indicate its association with the SMTC configuration.

[0464] The IAB node attempts to detect SSB 2515 according to the SMTC configuration. If the IAB node detects an SSB, it obtains downlink timing information of the entity transmitting the SSB (e.g., an attacker node). The IAB node obtains timing adjustment / misalignment T_(ul-dl) information 2520. This information can be obtained from the entity transmitting the SSB, from the network, or a combination thereof. Alternatively, all or part of the information can be obtained from the IAB node's pre-configuration. The information may contain timing adjustment / misalignment values ​​and / or may contain timing alignment conditions (e.g., condition 1, condition 6, or condition 7, as specified in the standard) or instructions on the method of obtaining timing alignment information.

[0465] After obtaining downlink timing information and timing adjustment / misalignment values, the IAB node calculates the uplink timing value 2525. In the case where the TX timing alignment method is used at the TX IAB node (attacker node) (Case 6), the uplink timing of the SRS transmission can be directly obtained from the downlink timing of the SSB transmission, with zero timing offset. Next, the IAB node can apply the uplink timing to receive SRS 2530. Then, the IAB node performs measurement 2535 on the SRS and can generate a report based on the received SRS measurement configuration. Finally, the IAB node transmits an SRS report 2540 containing the measurement results, such as SRS-RSRP, and method 2500 ends.

[0466] In one embodiment, the report includes signal strength values, such as RSRP, SRS-RSRP, RSSI, or the like. The report can be transmitted on a shared channel or a control channel between an IAB node and another node (the parent node of the IAB node, the IAB donor, etc.). For example, refer to... Figure 22 In one embodiment, victim node N1 2202 performs a measurement on the SRS received from attacker node N2 2204 (see connection 2210), and then transmits the report to other IAB nodes / donors 2206 connected to victim node N1 2202 (see connection 2215). In this embodiment, timing information does not need to be transmitted over the connection (e.g., the wire), but instead, victim IAB node 2202 may obtain timing from attacker IAB node 2204's SSB (e.g., via broadcast connection 2205) and then use it to perform a measurement on attacker IAB node 2204's SRS (e.g., via broadcast connection 2210).

[0467] Previously proposed timing misalignment values ​​can be propagated to the RX IAB node. Different alternatives are possible. In one embodiment, the TX IAB node calculates the misalignment value and transmits it to the RX IAB node, for example, by broadcasting it. System information blocks can be used for this purpose. In another embodiment, the misalignment value can be transmitted to the network, for example, via the parent IAB node, and then the network propagates the value to the RX IAB node.

[0468] In the case where TX timing alignment is used at the TX IAB node (attacker node) (Case 6), the timing alignment configuration of the TX IAB node indicating zero timing offset associated with the transmissions of SSB and SRS is sufficient. This information can be transmitted semi-statically to the RX IAB node (victim node) by the IAB-CU. In this case, no dynamic signaling is needed to indicate timing misalignment between the transmissions of SSB and SRS from the TX IAB node, except for an offset equal to an integer multiple of the symbol time.

[0469] If provided by the network, for example through a parent node, then timing misalignment information can be sent to the RX IAB node via semi-static configuration, indications in the DCI, or other signaling methods.

[0470] In special cases, the information provided to the RX IAB node may be a single bit indicating whether uplink and downlink transmissions are aligned. Alternatively, an information bit may indicate whether timing misalignment is below an acceptable threshold. The threshold may be a constant, a configurable value, or obtained from other parameters. The threshold may be a function of the parameters of uplink and / or downlink transmissions (e.g., SSB and / or SRS transmissions performed by the TX IAB node).

[0471] In some embodiments, an attacker node can transmit a report containing timing misalignment by averaging several timing misalignment values ​​during an observation window. The duration of the window and / or the frequency of report transmission can be specified by a standard or configured by the system. In some embodiments, the attacker node can send the average timing misalignment to the network, for example, to the IAB donor CU. The network can then pass this information to the victim node.

[0472] Because there are multiple timing misalignments between the uplink and downlink at the TX IAB node, information for specific transmissions may need to be passed to the RX IAB node. For example, a CLI configuration containing SRS measurement parameters can explicitly associate the timing of the SRS configuration with the SMTC, or otherwise contain SMTC information, allowing the RX IAB node to obtain downlink timing information from a specific SSB transmission.

[0473] In a more general embodiment, the SRS and STC may be associated so that timing misalignment can be explicitly identified. Alternatively or additionally, the SRS measurement and SMTC may be associated with each other.

[0474] If the RX IAB node cannot detect any SSB within the time interval indicated by the SMTC, it may request timing misalignment information from the network. Alternatively, the RX IAB node may attempt to perform a measurement on the SRS and request timing misalignment information only if the measurement fails. As another alternative, if the RX IAB node cannot detect any SSB from the TX IAB node, it may assume a zero timing misalignment value or a fixed value defined by a standard, configuration, or pre-configuration.

[0475] In an alternative embodiment, if the RX IAB node cannot obtain uplink timing alignment information associated with the SRS, it may refuse to transmit the measurement report.

[0476] The following should be noted throughout this disclosure:

[0477] a. Any parameter discussed in this disclosure can actually be presented as a linear function of that parameter in the signaling or specification. For example, T delta In fact, it can be presented as (N) delta +T delta ·G step )·T c .

[0478] b. In any timing assignment of a time slot containing a signal, a timing assignment represented in literal text or in an equation by symbols such as '=" or ':=" can mean that the start time of the time slot containing the signal is equal to a determined value, such as the right-hand side of an equation. Alternatively, the start time of the time slot containing the signal can differ from the determined value by T. slot Integer multiples of T, where T slot This represents the slot duration for a given time interval or subcarrier spacing (“SCS”). Typically, this applies to all timing assignments in this disclosure. In some embodiments, the value may differ by T. symbol Integer multiples of T, not T slot Integer multiples of T, where T symbol The symbol duration represents a given null terminology or subcarrier interval (“SCS”).

[0479] c. Although the entity is called an IAB node, the same approach can be applied to IAB donors, which are IAB entities that connect the core network to the IAB network with minimal or zero modifications.

[0480] d. The different steps described in the text and in the flowchart for example embodiments may be replaced or performed in a different order than that depicted in the diagram.

[0481] e. Each configuration can actually be provided by one or more configurations. An earlier configuration may provide a subset of parameters, while a subsequent configuration may provide another subset of parameters. Alternatively, a subsequent configuration may override values ​​provided by an earlier configuration or pre-configuration.

[0482] f. Configuration may be provided by Radio Resource Control (“RRC”) signaling, Media Access Control (“MAC”) signaling, Physical Layer signaling (e.g., Downlink Control Information (“DCI”) messages), a combination thereof, or other methods. Configuration may include pre-configured or semi-static configurations provided by standards, vendors, and / or network / operator. Each parameter value received by configuration or indication may override previous values ​​of similar parameters.

[0483] g. Despite the frequent mention of IAB, the proposed solution is applicable to wireless relay nodes and other types of wireless communication entities.

[0484] h. The 3GPP RAN discusses the ability of vendors to manufacture IAB systems / devices and operators to deploy IAB systems / devices to negotiate systems / devices. This implies that some information required for signaling between entities is readily available for use in the device, for example, by storing the information in a memory unit (e.g., read-only memory (“ROM”)), exchanging the information via dedicated signaling methods, providing the information by (pre)configuration, or otherwise taking the information into account when creating the hardware and / or software of the IAB system / device or other entities in the network. In this case, the methods described in this disclosure, including the exchange of information, can be extended to similar methods, wherein the information is obtained by those other methods.

[0485] i. This disclosure proposes methods for TX and RX timing alignment in IAB systems. Several embodiments of configuration and signaling are provided for each of two cases of TX and RX alignment at IAB nodes, which are leading candidates for duplex-enhanced IAB timing alignment in Rel-17. The methods are then extended to a unified framework and signaling, wherein different timing alignment methods can be configured based on node capabilities and applied locally based on scheduling needs.

[0486] Figure 26 This description depicts one embodiment of a user equipment device 2600 for timing alignment in integrated access and backhaul, according to embodiments of the present disclosure. The user equipment device 2600 may be an embodiment of remote unit 105 and / or UE 214. Furthermore, the user equipment device 2600 may include a processor 2605, a memory 2610, an input device 2615, an output device 2620, and a transceiver 2625. In some embodiments, the input device 2615 and the output device 2620 are combined into a single device, such as a touchscreen. In some embodiments, the user equipment device 2600 does not include any input device 2615 and / or output device 2620.

[0487] As depicted, transceiver 2625 includes at least one transmitter 2630 and at least one receiver 2635. Here, transceiver 2625 communicates with a mobile core network (e.g., 5GC) via one or more access networks. Additionally, transceiver 2625 may support at least one network interface 2640. Here, at least one network interface 2640 facilitates communication with eNB, gNB, IAB donors, or IAB nodes (e.g., using a "Uu" interface). Furthermore, at least one network interface 2640 may include an interface for communication with AMF, SMF, and / or UPF.

[0488] In some embodiments, transceiver 2625 includes a first transceiver communicating with a mobile communication network via a first access network and a second transceiver communicating with a mobile communication network via a second access network. In other embodiments, transceiver 2625 includes a first function (e.g., a modem) for communicating with the mobile communication network via the first access network and a second function (e.g., a modem) for communicating with the mobile communication network via the second access network.

[0489] In one embodiment, processor 2605 may include any known controller capable of executing computer-readable instructions and / or performing logical operations. For example, processor 2605 may be a microcontroller, microprocessor, central processing unit (“CPU”), graphics processing unit (“GPU”), auxiliary processing unit, field-programmable gate array (“FPGA”), or similar programmable controller. In some embodiments, processor 2605 executes instructions stored in memory 2610 to perform the methods and routines described herein. Processor 2605 is communicatively coupled to memory 2610, input device 2615, output device 2620, and transceiver 2625.

[0490] In one embodiment, memory 2610 is a computer-readable storage medium. In some embodiments, memory 2610 includes volatile computer storage media. For example, memory 2610 may include RAM, which includes dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and / or static RAM (“SRAM”). In some embodiments, memory 2610 includes non-volatile computer storage media. For example, memory 2610 may include a hard disk drive, flash memory, or any other suitable non-volatile computer storage device. In some embodiments, memory 2610 includes both volatile and non-volatile computer storage media. In some embodiments, memory 2610 stores data related to quality of service flow selection for multiple access data connections, such as access network information (“ANI”), IP addresses, and the like. In some embodiments, memory 2610 also stores program code and related data, such as an operating system (“OS”) or other controller algorithms operating on user equipment device 2600 and one or more software applications.

[0491] In one embodiment, input device 2615 may include any known computer input device, including a touch panel, buttons, keyboard, pen, microphone, or the like. In some embodiments, input device 2615 may be integrated with output device 2620, for example, as a touchscreen or similar touch-sensitive display. In some embodiments, input device 2615 includes a touchscreen that allows text to be entered using a virtual keyboard displayed on the touchscreen and / or by handwriting input on the touchscreen. In some embodiments, input device 2615 includes two or more different devices, such as a keyboard and a touch panel.

[0492] In one embodiment, output device 2620 may include any known electronically controllable display or display device. Output device 2620 may be designed to output visual, auditory, and / or tactile signals. In some embodiments, output device 2620 includes an electronic display capable of outputting visual data to a user. For example, output device 2620 may include (but is not limited to) a liquid crystal display (“LCD”), an LED display, an organic light-emitting diode (“OLED”) display, a projector, or a similar display device capable of outputting images, text, or the like to a user. As another non-limiting example, output device 2620 may include a wearable display, such as a smartwatch, smart glasses, a head-mounted display, or the like. Furthermore, output device 2620 may be a component of a smartphone, personal digital assistant, television, desktop computer, laptop computer, personal computer, vehicle dashboard, or the like.

[0493] In some embodiments, the output device 2620 includes one or more speakers for generating sound. For example, the output device 2620 may generate an auditory alarm or notification (e.g., a beep or ring). In some embodiments, the output device 2620 includes one or more haptic devices for generating vibration, motion, or other haptic feedback. In some embodiments, all or part of the output device 2620 may be integrated with the input device 2615. For example, the input device 2615 and the output device 2620 may form a touchscreen or similar touch-sensitive display. In other embodiments, part or all of the output device 2620 may be located near the input device 2615.

[0494] As discussed above, transceiver 2625 communicates with one or more network functions of a mobile communication network via one or more access networks. Transceiver 2625 operates under the control of processor 2605 to transmit and receive messages, data, and other signals. For example, processor 2605 may selectively activate the transceiver (or a portion thereof) at specific times to send and receive messages.

[0495] Transceiver 2625 includes one or more transmitters 2630 and one or more receivers 2635. Although only one transmitter 2630 and one receiver 2635 are described, user equipment device 2600 may have any suitable number of transmitters 2630 and receivers 2635. Furthermore, transmitters 2630 and receivers 2635 may be of any suitable type. In one embodiment, transceiver 2625 includes a first transmitter / receiver pair for communicating with a mobile communication network via licensed radio spectrum and a second transmitter / receiver pair for communicating with a mobile communication network via unlicensed radio spectrum.

[0496] In some embodiments, a first transmitter / receiver pair for communicating with a mobile communication network via licensed radio spectrum and a second transmitter / receiver pair for communicating with a mobile communication network via unlicensed radio spectrum may be combined into a single transceiver unit, such as a single chip that performs functions for use with both licensed and unlicensed radio spectrum. In some embodiments, the first transmitter / receiver pair and the second transmitter / receiver pair may share one or more hardware components. For example, some transceivers 2625, transmitters 2630, and receivers 2635 may be implemented as physically separate components that access shared hardware resources and / or software resources, such as (for example) network interface 2640.

[0497] In various embodiments, one or more transmitters 2630 and / or one or more receivers 2635 may be implemented and / or integrated into a single hardware component, such as a multi-transceiver chip, a single-chip system, an application-specific integrated circuit (“ASIC”), or other types of hardware components. In some embodiments, one or more transmitters 2630 and / or one or more receivers 2635 may be implemented and / or integrated into a multi-chip module. In some embodiments, other components of, for example, network interface 2640 or other hardware components / circuitets may be integrated with any number of transmitters 2630 and / or receivers 2635 into a single chip. In this embodiment, transmitters 2630 and receivers 2635 may be logically configured to use one or more common control signals as transceivers 2625 or modular transmitters 2630 and receivers 2635 configured to be implemented in the same hardware chip or multi-chip module.

[0498] Figure 27This description depicts one embodiment of a user equipment device 2700, which can be used for timing alignment in integrated access and backhaul, according to embodiments of the present disclosure. In some embodiments, the network equipment device 2700 may implement SMF (Software-Defined Function). In other embodiments, the network equipment device 2700 may implement other network functions. Furthermore, the network equipment device 2700 may include a processor 2705, a memory 2710, an input device 2715, an output device 2720, and a transceiver 2725. In some embodiments, the input device 2715 and the output device 2720 are combined into a single device (e.g., a touchscreen). In some embodiments, the network equipment device 2700 does not include any input device 2715 and / or output device 2720.

[0499] As depicted, transceiver 2725 includes at least one transmitter 2730 and at least one receiver 2735. Here, transceiver 2725 communicates with one or more remote units 105. Additionally, transceiver 2725 may support at least one network interface 2740. In some embodiments, transceiver 2725 supports a first interface for communicating with RAN nodes, a second interface for communicating with one or more network functions in the mobile core network (e.g., 5GC), and a third interface for communicating with remote units (e.g., UEs).

[0500] In one embodiment, processor 2705 may include any known controller capable of executing computer-readable instructions and / or performing logical operations. For example, processor 2705 may be a microcontroller, microprocessor, central processing unit (“CPU”), graphics processing unit (“GPU”), auxiliary processing unit, field-programmable gate array (“FPGA”), or similar programmable controller. In some embodiments, processor 2705 executes instructions stored in memory 2710 to perform the methods and routines described herein. Processor 2705 is communicatively coupled to memory 2710, input device 2715, output device 2720, and first transceiver 2725.

[0501] In various embodiments, network equipment device 2700 operates as an IAB node in a wireless communication network. In this embodiment, transceiver 2725 receives a first configuration for receiving downlink reference signals and a second configuration for receiving uplink reference signals. In one embodiment, processor 2705 determines timing alignment information associated with the downlink reference signals and the uplink reference signals; determines a timing misalignment value based on the timing alignment information; calculates a second reception time based on a first reception time and the timing misalignment value, the first reception time being determined based on the downlink reference signals; and applies the second reception time to the IAB node to receive the uplink reference signals.

[0502] In one embodiment, processor 2705 is further configured to perform a measurement on the uplink reference signal at a second reception time, and transceiver 2725 is further configured to transmit a report including information from the performed measurement.

[0503] In one embodiment, the processor 2705 is configured to calculate a second reception time by: obtaining the start time of a first time slot, wherein the first time slot includes a downlink reference signal; and calculating the start time of the second time slot as a timing misalignment value minus the start time of the first time slot plus an integer multiple of the time slot duration, wherein the second time slot includes an uplink reference signal, the integer multiple being obtained based on a first configuration and a second configuration.

[0504] In one embodiment, the processor 2705 is configured to calculate the second receive time by determining that the timing alignment mode is a transmission timing alignment mode as an integer multiple of the first receive time plus the symbol time.

[0505] In one embodiment, transceiver 2725 receives a first configuration for transmitting a downlink reference signal and a second configuration for transmitting an uplink reference signal. In one embodiment, processor 2705 obtains timing alignment information and calculates a timing misalignment value associated with a first transmission time of the downlink reference signal and a second transmission time of the uplink reference signal based on the timing alignment information. In one embodiment, transceiver 2725 transmits the downlink reference signal at the first transmission time; transmits the timing misalignment value; and transmits the uplink reference signal at the second transmission time.

[0506] In one embodiment, transceiver 2725 is configured to transmit a timing misalignment value by at least one of the following: transmitting the timing misalignment value in a System Information Block (“SIB”) associated with a downlink reference signal; and transmitting the timing misalignment value to the serving cell.

[0507] In one embodiment, the processor 2705 is further configured to obtain timing alignment information by at least one of: receiving a third configuration for a timing alignment mode; and receiving a timing alignment control message from the serving cell.

[0508] In one embodiment, the processor 2705 is configured to calculate the second receive time by determining that the timing alignment mode is a transmission timing alignment mode as an integer multiple of the first receive time plus the symbol time.

[0509] In one embodiment, memory 2710 is a computer-readable storage medium. In some embodiments, memory 2710 includes volatile computer storage media. For example, memory 2710 may include RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and / or static RAM (“SRAM”). In some embodiments, memory 2710 includes non-volatile computer storage media. For example, memory 2710 may include a hard disk drive, flash memory, or any other suitable non-volatile computer storage device. In some embodiments, memory 2710 includes both volatile and non-volatile computer storage media. In some embodiments, memory 2710 stores data related to quality of service flow selection for multi-access data connections, such as storing ANI, IP address, UE context, and the like. In some embodiments, memory 2710 also stores program code and related data, such as an operating system (“OS”) or other controller algorithms operating on network equipment device 2700 and one or more software applications.

[0510] In one embodiment, input device 2715 may include any known computer input device, including a touch panel, button, keyboard, light pen, microphone, or the like. In some embodiments, input device 2715 may be integrated with output device 2720 as, for example, a touchscreen or similar touch-sensitive display. In some embodiments, input device 2715 includes a touchscreen, allowing text to be entered using a virtual keyboard displayed on the touchscreen and / or by handwriting on the touchscreen. In some embodiments, input device 2715 includes two or more different devices, such as a keyboard and a touch panel.

[0511] In one embodiment, output device 2720 may include any known electronically controllable display or display device. Output device 2720 may be designed to output visual, auditory, and / or tactile signals. In some embodiments, output device 2720 includes an electronic display capable of outputting visual data to a user. For example, output device 2720 may include (but is not limited to) an LCD display, LED display, OLED display, projector, or similar display device capable of outputting images, text, or the like to a user. As another non-limiting example, output device 2720 may include a wearable display, such as a smartwatch, smart glasses, head-mounted display, or the like. Furthermore, output device 2720 may be a component of a smartphone, personal digital assistant, television, desktop computer, laptop computer, personal computer, vehicle dashboard, or the like.

[0512] In some embodiments, the output device 2720 includes one or more speakers for generating sound. For example, the output device 2720 may generate an auditory alarm or notification (e.g., a beep or ring). In some embodiments, the output device 2720 includes one or more haptic devices for generating vibration, motion, or other haptic feedback. In some embodiments, all or part of the output device 2720 may be integrated with the input device 2715. For example, the input device 2715 and the output device 2720 may form a touchscreen or similar touch-sensitive display. In other embodiments, all or part of the output device 2720 may be located near the input device 2715.

[0513] As discussed above, transceiver 2725 can communicate with one or more remote units and / or with one or more interoperability functions providing access to one or more PLMNs. Transceiver 2725 can also communicate with one or more network functions (e.g., in mobile core network 140). Transceiver 2725 operates under the control of processor 2705 to transmit and receive messages, data, and other signals. For example, processor 2705 can selectively activate the transceiver (or a portion thereof) at specific times to send and receive messages.

[0514] Transceiver 2725 may include one or more transmitters 2730 and one or more receivers 2735. In some embodiments, one or more transmitters 2730 and / or one or more receivers 2735 may share transceiver hardware and / or circuitry. For example, one or more transmitters 2730 and / or one or more receivers 2735 may share antennas, antenna tuners, amplifiers, filters, oscillators, mixers, modulators / demodulators, power supplies, and the like. In one embodiment, transceiver 2725 implements multiple logical transceivers using different communication protocols or protocol stacks while using common physical hardware.

[0515] Figure 28 An embodiment of a method 2800 for timing alignment in integrated access and backhaul is described. In one embodiment, method 2800 may be performed by a wireless network entity, a wireless network node, a network device (such as network equipment device 2700 described above), a processor, a transceiver, an integrated access backhaul node, and / or the like.

[0516] In one embodiment, method 2800 begins and obtains a first uplink transmission time, a downlink transmission time, and a second uplink transmission time for an Integrated Access Backhaul (“IAB”) node of the wireless communication network 2805. In another embodiment, method 2800 determines a timing alignment pattern 2810 for the IAB node. In some embodiments, method 2800 transmits an uplink signal from the IAB node based on one of the first uplink transmission time, the downlink transmission time, and the second uplink transmission time, based on the timing alignment pattern of the IAB node 2815, and method 2800 ends.

[0517] Figure 29 An embodiment of a method 2900 for timing alignment in integrated access and backhaul is described. In one embodiment, method 2900 may be performed by a wireless network entity, a wireless network node, a network device (such as network equipment device 2700 described above), a processor, a transceiver, an integrated access backhaul node, and / or the like.

[0518] In one embodiment, method 2900 begins and obtains downlink reception time 2905 for an Integrated Access Backhaul (“IAB”) node of a wireless communication network. In another embodiment, method 2900 obtains at least one of a first coefficient, a second coefficient, and a third coefficient 2910 for the IAB node. In some embodiments, method 2900 receives at least one of a timing advance value, a timing difference value, and an additional timing advance value 2915 for the IAB node. In various embodiments, method 2900 transmits uplink signal 2920 while applying uplink transmission time, wherein the uplink transmission time is equal to the downlink reception time minus the sum of the first coefficient multiplied by the timing advance value, the second coefficient multiplied by the timing difference value, and the third coefficient multiplied by the additional timing advance value, and method 2900 ends.

[0519] Figure 30 An embodiment of a method 3000 for timing alignment in integrated access and backhaul is described. In one embodiment, method 3000 may be performed by a wireless network entity, a wireless network node, a network device (e.g., network equipment device 2700 described above), a processor, a transceiver, an integrated access backhaul node, and / or the like.

[0520] In one embodiment, method 3000 begins and receives, at an Integrated Access and Backhaul (“IAB”) node of the wireless communication network, a first configuration for receiving downlink reference signals and a second configuration for receiving uplink reference signals 3005. In another embodiment, method 3000 determines timing alignment information 3010 associated with the downlink reference signals and the uplink reference signals.

[0521] In one embodiment, method 3000 determines a timing misalignment value 3015 based on timing alignment information. In another embodiment, method 3000 calculates a second reception time 3020 based on a first reception time and the timing misalignment value, the first reception time being determined based on a downlink reference signal. In one embodiment, method 3000 applies the second reception time to the IAB node to receive the uplink reference signal 3025, and method 3000 terminates.

[0522] Figure 31 An embodiment of a method 3100 for timing alignment in integrated access and backhaul is described. In one embodiment, method 3100 may be performed by a wireless network entity, a wireless network node, a network device (such as network equipment device 2700 described above), a processor, a transceiver, an integrated access backhaul node, and / or the like.

[0523] In one embodiment, method 3100 begins and receives, at an Integrated Access and Backhaul (“IAB”) node of the wireless communication network, a first configuration for transmitting downlink reference signals and a second configuration for transmitting uplink reference signals 3105. In another embodiment, method 3100 obtains timing alignment information 3110.

[0524] In one embodiment, method 3100 calculates a timing misalignment value 3115 associated with a first transmission time of the downlink reference signal and a second transmission time of the uplink reference signal based on timing alignment information. In another embodiment, method 3100 transmits the downlink reference signal 3120 at the first transmission time. In one embodiment, method 3100 transmits the timing misalignment value 3125. In another embodiment, method 3100 transmits the uplink reference signal 3130 at the second transmission time, and method 3100 terminates.

[0525] A first method for timing alignment in integrated access and backhaul is disclosed. In one embodiment, the first method includes receiving a first configuration for receiving downlink reference signals and a second configuration for receiving uplink reference signals at an integrated access and backhaul (“IAB”) node of a wireless communication network. In another embodiment, the first method includes determining timing alignment information associated with the downlink reference signals and the uplink reference signals.

[0526] In some embodiments, the first method includes determining a timing misalignment value based on timing alignment information. In one embodiment, the first method includes calculating a second reception time based on a first reception time and the timing misalignment value, the first reception time being determined based on a downlink reference signal. In some embodiments, the first method includes applying the second reception time to the IAB node to receive the uplink reference signal.

[0527] In one embodiment, the first method includes performing a measurement on an uplink reference signal at a second reception time and transmitting a report including information from the performed measurement. In one embodiment, the first method includes: obtaining a start time of a first time slot, wherein the first time slot includes the downlink reference signal; and calculating the start time of a second time slot as a timing misalignment value minus the start time of the first time slot plus an integer multiple of the time slot duration, the second time slot including the uplink reference signal, the integer multiple being obtained based on a first configuration and a second configuration.

[0528] In one embodiment, timing alignment information is determined based on at least one of a timing misalignment value received from a System Information Block (“SIB”) associated with a downlink reference signal and a second timing misalignment value received from the serving cell. In one embodiment, timing alignment information is determined based on a received third configuration of the timing alignment mode. In one embodiment, calculating the second receive time includes calculating the second receive time as an integer multiple of the first receive time plus the symbol time in response to determining that the timing alignment mode is a transmission timing alignment mode.

[0529] In one embodiment, the first configuration is a synchronization signal block (“SSB”) measurement timing configuration (“SMTC”), the downlink reference signal is a synchronization signal and physical broadcast channel (“SS / PBCH”) block, the second configuration is a probe reference signal reference signal received power (“SRS-RSRP”) configuration, and the uplink signal is a probe reference signal (“SRS”).

[0530] A second method for timing alignment in integrated access and backhaul is disclosed. In one embodiment, the second method includes receiving a first configuration for transmitting downlink reference signals and a second configuration for transmitting uplink reference signals at an integrated access and backhaul (“IAB”) node of a wireless communication network. In one embodiment, the second method includes obtaining timing alignment information.

[0531] In one embodiment, the second method includes calculating a timing misalignment value associated with a first transmission time of the downlink reference signal and a second transmission time of the uplink reference signal based on timing alignment information. In one embodiment, the second method includes transmitting the downlink reference signal at the first transmission time. In one embodiment, the second method includes transmitting the timing misalignment value. In one embodiment, the second method includes transmitting the uplink reference signal at the second transmission time.

[0532] In one embodiment, the timing misalignment value is equal to an integer multiple of the second start time of the second time slot including the uplink reference signal minus the first start time of the first time slot including the downlink reference signal minus the time slot duration, wherein the integer multiple is obtained based on a first configuration and a second configuration. In one embodiment, transmitting the timing misalignment value includes at least one of: transmitting the timing misalignment value in a System Information Block (“SIB”) associated with the downlink reference signal; and transmitting the timing misalignment value to the serving cell.

[0533] In one embodiment, obtaining timing alignment information includes at least one of: receiving a third configuration for a timing alignment mode; and receiving a timing alignment control message from a serving cell. In one embodiment, the timing alignment mode is one of a transmission timing alignment mode and a reception timing alignment mode. In one embodiment, the second method includes calculating a second reception time as an integer multiple of the first reception time plus the symbol time in response to determining that the timing alignment mode is a transmission timing alignment mode.

[0534] In one embodiment, the first configuration is a synchronization signal block (“SSB”) transmission configuration (“STC”), the downlink reference signal is a synchronization signal and physical broadcast channel (“SS / PBCH”) block, and the second configuration is a probe reference signal (“SRS”) configuration, and the uplink signal is SRS.

[0535] A first device for timing alignment in integrated access and backhaul is disclosed. In one embodiment, the first device includes a transceiver that receives a first configuration for receiving a downlink reference signal and a second configuration for receiving an uplink reference signal. In another embodiment, the first device includes a processor that: determines timing alignment information associated with the downlink reference signal and the uplink reference signal; determines a timing misalignment value based on the timing alignment information; calculates a second reception time based on a first reception time and the timing misalignment value, the first reception time being determined based on the downlink reference signal; and applies the second reception time to an IAB node to receive the uplink reference signal.

[0536] In some embodiments, the processor is further configured to perform measurements on the uplink reference signal at a second reception time, and the transceiver is further configured to transmit a report including information from the performed measurements. In one embodiment, the processor is configured to calculate the second reception time by: obtaining the start time of a first time slot, wherein the first time slot includes the downlink reference signal; and calculating the start time of the second time slot as a timing misalignment value minus the start time of the first time slot plus an integer multiple of the time slot duration, the second time slot including the uplink reference signal, the integer multiple being obtained based on a first configuration and a second configuration.

[0537] In one embodiment, timing alignment information is determined based on at least one of a timing misalignment value received from a System Information Block (“SIB”) associated with a downlink reference signal and a second timing misalignment value received from the serving cell. In one embodiment, timing alignment information is determined based on a received third configuration of the timing alignment mode. In one embodiment, the processor is configured to calculate the second receive time by calculating the second receive time as an integer multiple of the first receive time plus the symbol time in response to determining that the timing alignment mode is a transmission timing alignment mode.

[0538] In one embodiment, the first configuration is a synchronization signal block (“SSB”) measurement timing configuration (“SMTC”), the downlink reference signal is a synchronization signal and physical broadcast channel (“SS / PBCH”) block, the second configuration is a probe reference signal reference signal received power (“SRS-RSRP”) configuration, and the uplink reference signal is a probe reference signal (“SRS”).

[0539] A second device for timing alignment in integrated access and backhaul is disclosed. In one embodiment, the second device includes a receiver that receives a first configuration for transmitting downlink reference signals and a second configuration for transmitting uplink reference signals. In one embodiment, the second device includes a processor that: obtains timing alignment information and calculates a timing misalignment value associated with a first transmission time of the downlink reference signal and a second transmission time of the uplink reference signal based on the timing alignment information. In one embodiment, the second device includes a transmitter that transmits the downlink reference signal at a first transmission time, transmits the timing misalignment value, and transmits the uplink reference signal at a second transmission time.

[0540] In one embodiment, the timing misalignment value is equal to an integer multiple of the second start time of the second time slot including the uplink reference signal minus the first start time of the first time slot including the downlink reference signal minus the time slot duration, wherein the integer multiple is obtained based on a first configuration and a second configuration. In one embodiment, the transmitter is configured to transmit the timing misalignment value by at least one of: transmitting the timing misalignment value in a System Information Block (“SIB”) associated with the downlink reference signal; and transmitting the timing misalignment value to the serving cell.

[0541] In one embodiment, the processor is further configured to transmit timing alignment information by at least one of: receiving a third configuration for a timing alignment mode; and receiving a timing alignment control message from the serving cell. In one embodiment, the timing alignment mode is one of a transmission timing alignment mode and a reception timing alignment mode.

[0542] In one embodiment, the processor is configured to calculate the second receive time as an integer multiple of the first receive time plus the symbol time in response to determining that the timing alignment mode is a transmission timing alignment mode. In one embodiment, the first configuration is a synchronization signal block (“SSB”) measurement timing configuration (“SMTC”), the downlink reference signal is a synchronization signal and physical broadcast channel (“SS / PBCH”) block, the second configuration is a probe reference signal reference signal received power (“SRS-RSRP”) configuration, and the uplink signal is a probe reference signal (“SRS”).

[0543] The embodiments may be practiced in other specific forms. The described embodiments should be considered illustrative in all respects and not restrictive. The scope of the invention is therefore indicated by the appended claims rather than by the foregoing description. All variations within the equivalent meaning and scope of the claims are included within their scope.

Claims

1. A method for wireless communication, comprising: At the integrated access and backhaul IAB node, a first configuration for receiving downlink reference signals is received; Receive the downlink reference signal according to the first configuration; The first reception time is determined based on the downlink reference signal; Receive timing misalignment value; Calculate the second reception time based on the first reception time and the timing misalignment value; Receive a second configuration for receiving uplink reference signals; The second reception time is applied to the IAB node to receive the uplink reference signal according to the second configuration; and Measurements are performed on the received uplink reference signal at the second reception time.

2. The method according to claim 1, further comprising: The transmission includes a report containing information from the performed measurements, including a reference signal received power (RSRP) measurement.

3. The method according to claim 1, wherein calculating the second receiving time comprises: Obtain the start time of the first time slot, wherein the first time slot includes the downlink reference signal; and The start time of the second time slot is calculated as the timing misalignment value minus the start time of the first time slot plus an integer multiple of the time slot duration, wherein the second time slot includes the uplink reference signal, and the integer multiple is obtained based on the first configuration and the second configuration.

4. The method of claim 1, wherein the second reception time is further based on a second timing misalignment value received from the serving cell.

5. The method of claim 1, wherein the second reception time is further based on a third configuration of the received timing alignment mode.

6. The method of claim 5, wherein calculating the second reception time comprises: In response to determining that the timing alignment mode is a transmission timing alignment mode, the second reception time is calculated as an integer multiple of the first reception time plus the symbol time.

7. The method according to claim 1, wherein: The first configuration is the Synchronization Signal Block (SSB) Measurement Timing Configuration (SMTC). The downlink reference signal is the synchronization signal and the physical broadcast channel SS / PBCH block; The second configuration is the Sound Reference Signal Received Power (SRS-RSRP) configuration; and The uplink reference signal is the sounding reference signal (SRS).

8. A device for wireless communication, comprising: At least one memory; as well as At least one processor coupled to the at least one memory and configured such that the device: At the integrated access and backhaul IAB node, a first configuration for receiving downlink reference signals is received; Receive the downlink reference signal according to the first configuration; The first reception time is determined based on the downlink reference signal; Receive timing misalignment value; Calculate the second reception time based on the first reception time and the timing misalignment value; Receive a second configuration for uplink reference signals; The second reception time is applied to the IAB node to receive the uplink reference signal according to the second configuration; and Measurements are performed on the received uplink reference signal at the second reception time.

9. The device of claim 8, wherein the at least one processor is configured to cause the device to: The transmission includes a report containing information from the performed measurements, including a reference signal received power (RSRP) measurement.

10. The device of claim 8, wherein the at least one processor is configured such that the device calculates the second reception time by: Obtain the start time of the first time slot, wherein the first time slot includes the downlink reference signal; and The start time of the second time slot is calculated as the timing misalignment value minus the start time of the first time slot plus an integer multiple of the time slot duration, wherein the second time slot includes the uplink reference signal, and the integer multiple is obtained based on the first configuration and the second configuration.

11. The apparatus of claim 8, wherein the second reception time is further based on a second timing misalignment value received from the serving cell.

12. The device of claim 8, wherein the second reception time is further based on a third configuration received in a timing alignment mode.

13. The device of claim 12, wherein the at least one processor is configured such that the device calculates the second reception time by calculating the second reception time as an integer multiple of the first reception time plus the symbol time in response to determining that the timing alignment mode is a transmission timing alignment mode.

14. The device according to claim 8, wherein: The first configuration is the Synchronization Signal Block (SSB) Measurement Timing Configuration (SMTC). The downlink reference signal is the synchronization signal and the physical broadcast channel SS / PBCH block; The second configuration is the Sound Reference Signal Received Power (SRS-RSRP) configuration; and The uplink reference signal is the sounding reference signal (SRS).

15. A device for wireless communication, comprising: At least one memory; as well as At least one processor coupled to the at least one memory and configured such that the device: Receive a first configuration for transmitting downlink reference signals and a second configuration for transmitting uplink reference signals; Determine the timing alignment information associated with the downlink reference signal and the uplink reference signal; Based on the timing alignment information, calculate the timing misalignment value associated with the first transmission time of the downlink reference signal and the second transmission time of the uplink reference signal; and The downlink reference signal is transmitted during the first transmission time; Transmit the timing misalignment value; and The uplink reference signal is transmitted during the second transmission time.

16. The device of claim 15, wherein the timing misalignment value is equal to an integer multiple of the second start time of the second time slot including the uplink reference signal minus the first start time of the first time slot including the downlink reference signal minus the time slot duration.

17. The apparatus of claim 15, wherein the at least one processor is configured such that the apparatus, in response to determining that the timing alignment mode is a transmission timing alignment mode, calculates the second reception time as an integer multiple of the first reception time plus the symbol time.

18. The device of claim 16, wherein the integer multiple is obtained based on the first configuration and the second configuration.

19. The apparatus of claim 15, wherein the at least one processor is configured to cause the apparatus to transmit the timing misalignment value in a System Information Block (SIB) associated with the downlink reference signal or to transmit the timing misalignment value to the serving cell.

20. The device of claim 15, wherein the at least one processor is configured such that the device obtains the timing alignment information by receiving a third configuration for a timing alignment scheme or by receiving a timing alignment control message from a serving cell.

Images