Method and apparatus for updating data transmission during inter-donor migration

Abstract

The present disclosure describes methods, systems, and devices for notifying at least one downstream device of a migrating integrated access backhaul node (IAB node) of an inter-donor migration status of the migrating IAB node experiencing a migration from a source IAB donor to a target IAB donor. The method includes receiving, by a receiving device, a radio resource control (RRC) message transmitted from an IAB donor. The RRC message includes an information element indicating the inter-donor migration status of the migrating IAB node. The method further includes transmitting, by the receiving device, a packet data convergence protocol (PDCP) status report to the target IAB donor in response to the information element indicating a successful inter-donor migration. The PDCP status report corresponds to a radio link control-acknowledged mode (RLC-AM) bearer configured to be allowed to transmit the PDCP status report in uplink and configured to update data transmission of the receiving device.

Description

Method and apparatus for updating data transmission during inter-donor migration Technical Field

[0001] This disclosure generally relates to wireless communications. In particular, this disclosure relates to methods and apparatus for updating data transmissions during inter-donor migration. Background Technology

[0002] Wireless communication technologies are propelling the world toward an increasingly interconnected and networked society. Compared to Long Term Evolution (LTE), fifth-generation (5G) New Radio (NR) technology offers a wider spectrum, including millimeter-wave (mmWave) bands. With the development of massive MIMO and / or multi-beam systems, 5G NR can provide faster speeds and lower latency.

[0003] 5G NR can include an Integrated Access Backhaul (IAB) implementation. An IAB implementation can include one or more IAB donors and multiple connected IAB nodes. Currently, there are challenges and / or problems associated with data transmission for updating downstream devices, particularly when an IAB node migrates from one IAB donor to another.

[0004] This disclosure can solve at least some of the challenges / problems associated with existing systems in order to improve the performance of wireless communication. Summary of the Invention

[0005] This application relates to methods, systems, and apparatus for wireless communication, and more specifically, to methods, systems, and apparatus for updating data transmission of downstream devices of a migration integrated access backhaul node (IAB node) during inter-donor migration.

[0006] In one embodiment, this disclosure describes a wireless communication method. The method includes a receiving device receiving a Radio Resource Control (RRC) message transmitted from a transmitting device. The RRC message includes first information indicating inter-donor migration related information of an IAB. The transmitting device includes one of a subset comprising at least one of a target nodeB (gNB), a target gNB central unit (gNB-CU), a source gNB, and a source gNB-CU.

[0007] In another embodiment, this disclosure describes a wireless communication method. The method includes receiving, by a receiving device, media access control (MAC) control information (CE) transmitted from a transmitting device, the MAC CE including first information indicative of inter-donor migration related information.

[0008] In another embodiment, this disclosure describes a wireless communication method. The method includes a first IAB node, acting as a transmitting device, sending a Backhaul Adaptation Protocol (BAP) Control Protocol Data Unit (PDU) to a second IAB node. The BAP control PDU includes first information indicating inter-IAB donor migration related information.

[0009] In another embodiment, this disclosure describes a wireless communication method. The method includes a first IAB node, acting as a transmitting device, sending a Backhaul Adaptation Protocol (BAP) Control Protocol Data Unit (PDU) to a second IAB node. The BAP control PDU includes first information indicating inter-IAB donor migration related information.

[0010] In some other embodiments, a wireless communication device may include a memory storing instructions and processing circuitry communicating with the memory. When the processing circuitry executes the instructions, it is configured to perform the methods described above.

[0011] In some other embodiments, a wireless communication device may include a memory storing instructions and processing circuitry communicating with the memory. When the processing circuitry executes the instructions, it is configured to perform the methods described above.

[0012] In some other embodiments, a computer-readable medium includes instructions that, when executed by a computer, cause the computer to perform the methods described above.

[0013] The foregoing and other aspects and their embodiments are described in more detail in the accompanying drawings, description and claims. Attached Figure Description

[0014] Figure 1 shows an example of a wireless communication system including an integrated access backhaul (IAB) system.

[0015] Figure 2 shows an example of an IAB donor or IAB node.

[0016] Figure 3 shows an example of a user device.

[0017] Figure 4 shows a schematic diagram of the migration IAB node in the donor migration process.

[0018] Figure 5 shows a flowchart of the wireless communication method.

[0019] Figure 6 illustrates an exemplary logic flow of the wireless communication method in Figure 5.

[0020] Figure 7A shows a flowchart of another wireless communication method.

[0021] Figure 7B shows an example of a Media Access Control (MAC) control element (CE).

[0022] Figure 7C shows an example of a dedicated logical channel identifier (LCID) value.

[0023] Figure 8 illustrates an exemplary logic flow of the wireless communication method in Figure 7A.

[0024] Figure 9A shows a flowchart of another wireless communication method.

[0025] Figure 9B shows several examples of the configuration format of the Backhaul Adaptation Protocol (BAP) Control Protocol Data Unit (PDU).

[0026] Figure 9C shows an example of a Backhaul Adaptation Protocol (BAP) Control Protocol Data Unit (PDU).

[0027] Figure 9D shows another example of a Backhaul Adaptation Protocol (BAP) Control Protocol Data Unit (PDU).

[0028] Figure 9E shows an example of a Private Radio Link Failure (RLF) indication type value.

[0029] Figure 10 illustrates an exemplary logic flow of the wireless communication method in Figure 9A. Detailed Implementation

[0030] This disclosure will now be described in detail below with reference to the accompanying drawings, which form part of this disclosure, and specific examples of embodiments are illustrated by way of example. However, it should be noted that this disclosure may be embodied in various different forms, and therefore the subject matter covered or claimed is intended to be construed as not being limited to any of the embodiments described below.

[0031] Throughout the specification and claims, terms may have subtle meanings implied or suggested by the context, rather than explicitly stated meanings. Similarly, the phrases “in one embodiment” or “in some embodiments” as used herein do not necessarily refer to the same embodiment, and the phrases “in another embodiment” or “in other embodiments” as used herein do not necessarily refer to different embodiments. For example, the claimed subject matter includes all or part of exemplary embodiments or combinations of embodiments.

[0032] Generally, terms can be understood, at least in part, from their usage in the context. For example, terms such as “and,” “or,” or “and / or” as used herein can include a variety of meanings, which can depend, at least in part, on the context in which they are used. Typically, “or” when used to relate a list, such as A, B, or C, means A, B, and C (inclusive meaning) and A, B, or C (exclusive meaning). Furthermore, the terms “one or more” or “at least one” as used herein, depending at least in part on the context, can be used to describe any feature, structure, or characteristic in the singular or in the plural form to describe a combination of features, structures, or characteristics. Similarly, terms such as “a,” “an,” or “the” can also be understood to express singular or plural usage, depending at least in part on the context. Furthermore, the terms “based on” or “determined by” can be understood as not necessarily intended to convey a set of exclusive factors; rather, they may allow for the presence of other factors that are not necessarily explicitly described, at least in part depending on the context.

[0033] This disclosure describes a method and apparatus for updating data transmission of downstream devices in a migration integrated access backhaul node (IAB node) during donor migration.

[0034] Next-generation (NG) or fifth-generation (5G) wireless communication can provide a range of capabilities, from high-speed downloads to supporting real-time, low-latency communication. Compared to Long Term Evolution (LTE), 5G New Radio (NR) technology has a wider spectrum, including millimeter-wave (mmWave) bands. With the development of massive MIMO and / or multi-beam systems, 5G NR can provide faster speeds and lower latency. 5G NR can include the development of Integrated Access Backhaul (IAB) implementations. IAB implementations can include one or more IAB donors and multiple connected IAB nodes. IAB implementations can communicate between one or more IAB donors and one or more IAB nodes via wireless backhaul and relay links. IAB implementations can provide flexible NR cell configurations and increase cell density without increasing the density of IAB donors.

[0035] An IAB system may include one or more IAB donors and one or more IAB nodes, which together provide wireless connectivity services to one or more user equipments (UEs) (e.g., smartphones). IAB donors and IAB nodes may be radio network base stations including NG Radio Access Network (NG-RAN) base stations, which may include nodeBs (NBs, e.g., gNBs) in a mobile telecommunications context. IAB donors may provide access backhaul to one or more connected sub-IAB nodes and may be connected to the core network via wired communication. In one embodiment, the core network may include a 5G core network (5GC). In another embodiment, the wired communication may include fiber optic transmission communication. IAB nodes may include radio access links and radio backhaul links. The radio access link may be used for communication between the UE and the IAB node. The radio backhaul link may be used for communication between the IAB node and the IAB donor and / or communication between one IAB node and another IAB node. Therefore, IAB nodes do not require a wired communication network for data backhaul. In some embodiments, IAB nodes do not include a wired communication network for data backhaul, thus making IAB nodes more flexible and easier to implement, reducing the burden of implementing a wired communication network. Access links and backhaul links can use the same transmission frequency band (referred to as in-band repeaters) or use transmission frequency bands with different frequencies (referred to as out-of-band repeaters).

[0036] Referring to Figure 1, IAB donor 130 can provide access backhaul 140 to one or more connected sub-IAB nodes (152 and 154). IAB donor 130 can be connected to core network 110 via wired communication 120. In one embodiment, core network 110 may include a 5G core network (5GC). In another embodiment, wired communication 120 may include fiber optic transmission communication.

[0037] An IAB donor can provide wireless connectivity to one or more user equipment (UEs). The UE can be a mobile device, such as a smartphone or a mobile communication module installed in a vehicle. For example, IAB donor 130 can provide wireless connectivity 160 to UE 172.

[0038] Similarly, but not limited to, a sub-IAB node can provide radio connectivity to one or more UEs. For example, IAB node 152 can provide radio connectivity 160 to UE 174.

[0039] Similarly, but not limited to, a child IAB node can provide access backhaul to one or more downstream IAB nodes. For example, IAB node 154 can provide access backhaul 140 to downstream IAB nodes 156 and 157. In the view of IAB node 154, IAB node 156 can be referred to as a child IAB node of IAB node 154; and IAB node 157 can be referred to as a grandchild IAB node of IAB node 154.

[0040] Similarly, but not limited to, grandchild IAB node 157 may also provide access backhaul to one or more connected great-grandchild IAB nodes and / or provide radio connectivity to one or more UEs (e.g., UE 178).

[0041] In one implementation, IAB system 100 may include another IAB donor 135. IAB donor 135 may also be connected to core network (e.g., 5GC) 110 via wired communication 120. IAB donor 135 may provide access backhaul 140 to one or more connected child IAB nodes 158; and IAB node 158 may provide radio connectivity 160 to one or more UEs 176.

[0042] IAB node 156, currently connected to IAB donor 130 via IAB node 154, can migrate to IAB donor 135. This can be referred to as an inter-donor migration, and IAB node 156 can be referred to as a migrating IAB node. Currently, there are challenges and / or issues associated with updating data transmissions of downstream devices (IAB nodes or UEs) during and / or after inter-donor migrations.

[0043] In one embodiment with an NR system, after inter-gNB migration, the target gNB may retransmit a portion of a data packet to ensure continued communication service to the UE. To minimize the portion of the data packet, the UE may send a Packet Data Convergence Protocol (PDCP) status report to the target gNB. The PDCP status report informs the target gNB of the status of the data packets received by the UE (e.g., failure or success), allowing the target gNB to decide which data packet to retransmit or transmit. In current systems, the UE can trigger the sending of a PDCP status report via PDCP data recovery and / or PDCP reconstruction. In both embodiments with PDCP reconstruction and PDCP data recovery, the UE may need to retransmit PDCP Protocol Data Units (PDUs) or PDCP Service Data Units (SDUs) that have not yet been acknowledged by a lower layer (e.g., the Radio Link Control (RLC) layer).

[0044] In one implementation with PDCP reconstruction, the UE can send a PDCP status report during inter-gNB migration via the following procedure: The target gNB can send a Radio Resource Control (RRC) message via the source gNB. The RRC message can be configured within the RRC containers of both the source gNB and the UE; the RRC message can also include an information element for PDCP reconstruction. The information element for PDCP reconstruction can trigger the PDCP reconstruction process and trigger the UE to send a PDCP status report. After successfully establishing a connection between the UE and the target gNB, the UE can send a PDCP status report to the target gNB.

[0045] In IAB systems, to avoid unnecessary packet retransmissions and ensure service continuity, UEs can report PDCP status reports. However, some challenges / problems arise. One potential challenge / problem is that after a migrating IAB node establishes a connection between the IAB node and the target gNB-CU, it may be necessary to trigger the UE connected to the migrating IAB to send a PDCP status report to the target IAB donor. The triggering event could include either the PDCP data recovery process or the PDCP reconstruction process. This could lead to retransmissions of packets that could reach the IAB donor CU but were in the source route during the migration of the migrating IAB node, wasting network resources and resulting in low performance.

[0046] This disclosure describes embodiments of methods and apparatus for updating configuration information of at least one of the migrating IAB node and / or its downstream devices during donor-to-donor migration of a migrating IAB node, addressing at least some of the aforementioned problems. In the embodiments, the downstream IAB node and / or the corresponding UE can send a PDCP status report to the target IAB node without receiving a PDCP data recovery or PDCP reconstruction process.

[0047] Figure 2 illustrates an exemplary wireless communication base station 200. The wireless communication base station 200 may be an exemplary implementation of at least one of the IAB donors (130 and 135) and IAB nodes (152, 154, 156, and 158) in Figure 1. The base station 200 may include wireless transmit / receive (Tx / Rx) circuitry 208 for transmitting / receiving communications with one or more UEs and / or one or more other base stations. The base station may also include network interface circuitry 209 to enable communication between the base station and other base stations and / or the core network (e.g., optical or wired interconnect, Ethernet, and / or other data transmission media / protocols). The base station 200 may optionally include input / output (I / O) interfaces 206 for communication with operators, etc.

[0048] The base station may also include system circuitry 204. System circuitry 204 may include processor 221 and / or memory 222. Memory 222 may include operating system 224, instructions 226, and parameters 228. Instructions 226 may be configured for use by one or more processors 124 to perform base station functions. Parameters 228 may include parameters that support the execution of instructions 226. For example, parameters may include network protocol settings, bandwidth parameters, radio frequency mapping allocation, and / or other parameters.

[0049] Figure 3 illustrates an exemplary user equipment (UE) 300. UE 300 may be a mobile device, such as a smartphone or a mobile communication module located in a vehicle. UE 300 may be an exemplary implementation of at least one of the UEs (172, 174, and 176) in Figure 1. UE 300 may include a communication interface 302, system circuitry 304, input / output interface (I / O) 306, display circuitry 308, and storage device 309. The display circuitry may include a user interface 310. System circuitry 304 may include any combination of hardware, software, firmware, or other logic / circuit. System circuitry 304 may be implemented, for example, with one or more system-on-chip (SoC), application-specific integrated circuit (ASIC), discrete analog and digital circuitry, and other circuitry. System circuitry 304 may be part of an implementation of any desired functionality in UE 300. In this regard, system circuitry 304 may include, for example, logic to facilitate decoding and playback of music and video, such as MP3, MP4, MPEG, AVI, FLAC, AC3, or WAV decoding and playback; running applications; accepting user input; saving and retrieving application data; establishing, maintaining, and terminating cellular phone calls or data connections, for example, for internet connections; establishing, maintaining, and terminating wireless network connections, Bluetooth connections, or other connections; and logic to display relevant information on user interface 310. User interface 310 and input / output (I / O) interface 306 may include a graphical user interface, a touch-sensitive display, haptic feedback or other haptic outputs, voice or facial recognition inputs, buttons, switches, speakers, and other user interface elements. Additional examples of I / O interface 306 may include a microphone, video and still image cameras, temperature sensors, vibration sensors, rotation and orientation sensors, headphone and microphone input / output jacks, a universal serial bus (USB) connector, a memory card slot, radiation sensors (e.g., IR sensors), and other types of inputs.

[0050] Referring to Figure 3, communication interface 302 may include radio frequency (RF) transmit (Tx) and receive (Rx) circuitry 316 that processes the transmission and reception of signals via one or more antennas 314. Communication interface 302 may include one or more transceivers. The transceiver may be a wireless transceiver, including modulation / demodulation circuitry, a digital-to-analog converter (DAC), a shaping table, an analog-to-digital converter (ADC), filters, waveform shapers, filters, preamplifiers, power amplifiers, and / or other logic for transmission and reception via one or more antennas or (for some devices) via a physical (e.g., wired) medium. The transmitted and received signals may follow any of a variety of formats, protocols, modulations (e.g., QPSK, 16-QAM, 64-QAM, or 256-QAM), frequency channels, bit rates, and encodings. As a specific example, communication interface 302 may include a transceiver supporting transmission and reception under 2G, 3G, BT, WiFi, Universal Mobile Telecommunications System (UMTS), High-Speed ​​Packet Access (HSPA)+, 4G / LTE, and 5G standards. However, the techniques described below can be applied to other wireless communication technologies, whether from the 3rd Generation Partnership Project (3GPP), the GSM Association, 3GPP2, IEEE, or other partners or standards bodies.

[0051] Referring to Figure 3, system circuitry 304 may include one or more processors 321 and memory 322. Memory 322 stores, for example, an operating system 324, instructions 326, and parameters 328. Processor 321 is configured to execute instructions 326 to perform the desired functions of UE 300. Parameters 328 can provide and specify configuration and operation options for instructions 326. Memory 322 may also store any BT, WiFi, 3G, 4G, 5G, or other data that UE 300 will send or has received via communication interface 302. In various embodiments, system power for UE 300 may be provided by power storage devices such as batteries or transformers.

[0052] This disclosure describes several embodiments of methods and apparatus for updating data transmission of at least one downstream device of a migration integrated access backhaul node (IAB node) during donor migration, which may be implemented in part or in whole at a wireless network base station and / or user equipment described above in Figures 2 and 3.

[0053] Referring to Figure 4, the IAB system 400 may include one or more IAB donors (410 and 420). An IAB node 450 currently connected to IAB donor 410 via IAB node 430 can migrate to IAB donor 420 via IAB node 440. This can be referred to as inter-donor migration. IAB node 450 can be the migrating IAB node; IAB donor 410 can be the source IAB donor; IAB node 430 can be the source parent IAB node; IAB donor 420 can be the target IAB donor; and IAB node 440 can be the target parent IAB node.

[0054] In some embodiments, for an IAB node, there may be one or more upstream IAB nodes 492, which can connect the IAB node together to the corresponding IAB donor; and there may be one or more downstream devices 494 connected to the IAB node, which may include one or more downstream IAB nodes and / or one or more downstream UEs.

[0055] In some embodiments, the migrating IAB node 450 can connect to the IAB donor through one or more IAB nodes, which can be collectively referred to as the parent IAB node.

[0056] Source IAB donor 410 may include a central unit (CU) 412 and a distribution unit (DU) 414, and source IAB donor CU 412 may communicate with source IAB donor DU 414. Source parent IAB node 430 communicating with source IAB donor 410 may include a mobile terminal (MT) 432 and a distribution unit (DU) 434. Target IAB donor 420 may include CU 422 and DU 424, and target IAB donor CU 422 may communicate with target IAB donor DU 424. Target IAB node 440 communicating with target IAB donor 420 may include MT 442 and DU 444.

[0057] Prior to donor migration, the migrating IAB node 450 can communicate with the source parent IAB node 430. The migrating IAB node 450 may include MT 452 and DU 454. In one embodiment, the migrating IAB node 450 can communicate with UE 470. In another embodiment, the migrating IAB node 450 can communicate with a child IAB node 460. The child IAB node 460 may include MT 462 and DU 464. In one embodiment, the child IAB node 460 can communicate with UE 472.

[0058] Referring to Figure 4, migrating IAB node 450 can change its attachment point from the source parent IAB node 430 connected to the source IAB donor 410 to the target IAB node 440 connected to the target IAB donor 420. In one embodiment, a handover (HO) process can occur during inter-donor migration, which could be an inter-CU HO scenario. Migrating IAB node DU 454 can communicate with the target IAB donor CU 422 via F1-AP message 482.

[0059] Referring to Figure 5, this disclosure describes various embodiments of a method 500 for using Radio Resource Control (RRC) messages to notify at least one downstream device of a migrated Integrated Access Backhaul Node (IAB Node) that an inter-donor migration of the migrated IAB Node has occurred from a source IAB donor to a target IAB donor. This method can solve the challenges / problems associated with requiring a receiving device to perform PDCP data recovery and / or PDCP reconstruction to trigger the transmission of a PDCP status report.

[0060] Method 500 may include some or all of the following steps: Step 510: At least one downstream device of the migrating IAB node receives a Radio Resource Control (RRC) message sent from the target IAB donor central unit (CU), the RRC message including an Information Element (IE) indicating that an inter-donor migration has occurred at the migrating IAB node; and Step 520: In response to the IE further indicating a successful inter-donor migration or triggering the receiving device to perform a Packet Data Convergence Protocol (PDCP) status report, at least one downstream device sends a Packet Data Convergence Protocol (PDCP) status report to the target IAB donor, the PDCP status report corresponding to a Radio Link Control Acknowledgment Mode (RLC-AM) bearer that has been configured to allow the transmission of PDCP status reports in the uplink.

[0061] Method 500 may optionally, additionally, or alternatively include step 530: in response to IE further indicating a successful inter-donor migration, data transmission of the wireless bearer is resumed by at least one downstream device.

[0062] Method 500 may optionally, additionally, or alternatively include step 540: in response to first information further indicating the in-progress state of inter-donor migration or the start state of inter-donor migration, the receiving device stops the data transmission of all radio bearers.

[0063] Method 500 may optionally, additionally, or alternatively include step 550: in response to first information further indicating the failure status of the inter-donor migration, the receiving device stops or cancels the behavior related to the inter-donor migration.

[0064] In one implementation, the RRC message may be an RRC reconfiguration message.

[0065] In one implementation, the IE can indicate the status of a migration between donors. In one implementation, the IE can include a TRUE or FALSE value. In another implementation, the IE can include only a TRUE value.

[0066] In one implementation, the TRUE value of the IE in the RRC message can indicate a successful inter-donor migration. In another implementation, the TRUE value of the IE can indicate triggering at least one downstream device to send a PDCP status report corresponding to a Radio Link Control Acknowledgment Mode (RLC-AM) bearer that has been configured to be allowed to send PDCP status reports in the uplink.

[0067] In one implementation, the FALSE value of the IE in the RRC message can indicate a failed inter-donor migration. In another implementation, the FALSE value of the IE can indicate that the receiver should not be triggered to send a PDCP status report corresponding to the RLC-AM bearer, which has been configured to be allowed to send PDCP status reports in the uplink.

[0068] Figure 6 illustrates the logical flow of a method 600 for updating data transmission of at least one downstream device of a migrating IAB node using RRC messages during an inter-donor migration from a source IAB donor to a target IAB donor. In another embodiment, Figure 6 illustrates the logical flow of a method 600 for notifying at least one downstream device of a migrating IAB node that an inter-donor migration from a source IAB donor to a target IAB donor has occurred using RRC messages.

[0069] Referring to step 610 in Figure 6, after the inter-donor migration, the target IAB donor CU 680 can send an RRC message to the IAB node MT 682. In one embodiment, the IAB node may include the migrating IAB node. In another embodiment, the IAB node may include a downstream IAB node of the migrating IAB node.

[0070] Referring to step 620 in Figure 6, during inter-donor migration, the target IAB donor CU 680 may send an RRC message to UE 684. In one embodiment, UE 686 may include a UE connected to the migrating IAB node. In another embodiment, UE 684 may include a UE connected to a downstream IAB node of the migrating IAB node.

[0071] Referring to step 630 in Figure 6, in response to the received RRC message including an IE indicating a successful inter-donor migration, the IAB node MT 682 can send a Packet Data Convergence Protocol (PDCP) status report to the target IAB donor. The PDCP status report may correspond to a Radio Link Control Acknowledgment Mode (RLC-AM) bearer that has been configured to allow the transmission of PDCP status reports in the uplink.

[0072] Referring to step 640 in Figure 6, in response to the received RRC message including an IE indicating a successful inter-donor migration, UE 684 may send a PDCP status report to the target IAB donor. The PDCP status report may correspond to a Radio Link Control Acknowledgment Mode (RLC-AM) bearer that has been configured to allow the transmission of PDCP status reports in the uplink.

[0073] Referring to Figure 7A, this disclosure describes various embodiments of a method 700 for notifying at least one downstream device of a Migrating Integrated Access Backhaul Node (IAB Node) of an inter-donor migration from a source IAB donor to a target IAB donor using a Media Access Control (MAC) control element (CE). This method can solve the challenges / problems associated with requiring a receiving device to perform PDCP data recovery and / or PDCP reconstruction to trigger the transmission of a PDCP status report.

[0074] Method 700 may include some or all of the following steps:

[0075] Step 710: The IAB node DU sends a Media Access Control (MAC) control element (CE) to at least one downstream device of the IAB node, the MAC CE indicating that an inter-donor migration has occurred in the migrating IAB node;

[0076] Step 720: When the receiving device is a UE and the IE further indicates a successful inter-donor migration or triggers a PDCP status report process or triggers the receiving device to perform a PDCP status report process, the UE sends a PDCP status report to the target IAB donor. The PDCP status report corresponds to a Radio Link Control Acknowledgment Mode (RLC-AM) bearer that has been configured to be allowed to send PDCP status reports in the uplink.

[0077] Step 730: When the receiving device is an IAB node, the IAB node sends a MAC CE to its child IAB nodes and / or the UEs connected to it;

[0078] Step 740: In response to the received MAC CE indicating a successful inter-donor migration, the UE can resume data transmission on the radio bearer;

[0079] Step 750: When the IE further indicates that the inter-donor migration is in progress or has started, the receiving device (e.g., an IAB node or a UE) stops all radio bearer data transmission; and

[0080] Step 760: When the IE further indicates the failure status of the inter-donor migration, the receiving device (e.g., IAB node or UE) considers that a radio link failure has occurred in the link where the MAC CE was received.

[0081] In one embodiment, referring to FIG7B, the MAC CE is identified by a MAC subheader 750 including a Logical Channel ID (LCID) 755. In another embodiment, the LCID may include a reserved value that does not conflict with other values. For example, referring to FIG7C, the LCID value 782 may correspond to the index 780 of the LCID value. For the LCID shown in FIG7B, the LCID may have 6 binary bits, and the value of the LCID for the downlink shared channel (DL-SCH) may include a reserved range 784 between 33 and 44 (inclusive); and the unique PDCP status report 785 may include a value of 44. In another embodiment, the MAC CE may have a fixed size of zero bits for its payload.

[0082] Figure 8 illustrates the logical flow of a method 800 for updating data transmission of at least one downstream device of a migrating IAB node using MAC CE during an inter-donor migration from a source IAB donor to a target IAB donor. In another embodiment, Figure 8 illustrates the logical flow of a method 600 for using MAC CE to notify at least one downstream device of a migrating IAB node that an inter-donor migration from a source IAB donor to a target IAB donor has occurred.

[0083] Referring to step 810 in Figure 8, during the inter-donor migration, IAB node DU 881 may send a MAC CE to child IAB node MT 682 when one of the following conditions is met.

[0084] In one implementation, an IAB node may include a migrating IAB node; and the condition may include the migrating IAB node successfully establishing or failing to establish or undergo a connection with an upstream device. The upstream device may include one of the target IAB donor and the target parent IAB node of the migrating IAB node.

[0085] In another implementation, the IAB node may include the target parent IAB node of the migrating IAB node; and the condition may include the migrating IAB node successfully establishing or failing to establish or experience or begin establishing a connection with the target parent IAB node of the migrating IAB node.

[0086] In another implementation, an IAB node may include a child IAB node; and the condition may include whether the child IAB node receives a MAC CE from its parent IAB node.

[0087] In another implementation, the condition may include migrating an IAB node; and the preset condition may include the migrating IAB node receiving a Radio Resource Control (RRC) message sent from the target IAB donor CU, and the received RRC message includes an Information Element (IE) indicating information related to the migration between donors.

[0088] Referring to step 820 in Figure 8, during the inter-donor migration, when conditions are met, IAB node DU 881 can send a MAC CE to UE 884. UE 884 then connects to the IAB node.

[0089] Referring to step 830 in Figure 8, optionally and additionally, in response to a received MAC CE indicating a successful inter-donor migration or triggering the receiving device to execute a Packet Data Convergence Protocol (PDCP) status report, IAB node 882 may send a PDCP status report to the target IAB donor 880. The PDCP status report may correspond to a Radio Link Control Acknowledgment Mode (RLC-AM) bearer that has been configured to allow the transmission of PDCP status reports in the uplink.

[0090] Referring to step 835 in Figure 8, in response to the received MAC CE, IAB node 882 may send the MAC CE to one or more downstream IAB nodes and / or UEs of IAB node 882.

[0091] Referring to step 840 in Figure 8, in response to a received MAC CE indicating a successful inter-donor migration or triggering the receiving device to execute a Packet Data Convergence Protocol (PDCP) status report, UE 884 may send a PDCP status report to the target IAB donor 880. The PDCP status report may correspond to an RLC-AM bearer that has been configured to be allowed to send PDCP status reports in the uplink.

[0092] Referring to step 840 in Figure 8, in response to the received MAC CE indication of a successful inter-donor migration, UE 884 can resume data transmission of the radio bearer.

[0093] Referring to steps 835 and 840 in Figure 8, in response to the received MAC CE indicating the in progress or start of inter-donor migration, the receiving device (IAB node 882 or UE 884) may stop all radio bearer data transmission.

[0094] Referring to steps 835 and 840 in Figure 8, in response to the received MAC CE indicating a failure state of inter-donor migration, the receiving device (IAB node 882 or UE 884) can assume that a radio link failure has occurred in the link where the MAC CE was received.

[0095] Referring to Figure 9A, this disclosure describes various embodiments of a method 900 for notifying at least one downstream device of a migration integrated access backhaul node (IAB node) of information related to inter-donor migration using a Backhaul Adaptation Protocol (BAP) control protocol data unit (PDU), wherein the migration IAB node migrates from a source IAB donor to a target IAB donor. This method can address challenges / problems associated with requiring a receiving device to perform PDCP data recovery and / or PDCP reconstruction to trigger the transmission of a PDCP status report. The information related to inter-donor migration in the BAP control PDU also includes: at least one upstream IAB node of the first IAB node has experienced an inter-donor migration from a source IAB donor to a target IAB donor, or a successful inter-donor migration status, or an inter-donor migration in progress status, or an inter-donor migration start status, or an inter-donor migration failure status, or an indication that triggers the receiving device to perform a Packet Data Convergence Protocol (PDCP) status report procedure.

[0096] Method 900 may include some or all of the following steps: Step 910: IAB node DU sends BAP control PDU to at least one downstream IAB node of the IAB node; Step 920: When the receiving IAB node receives a BAP control PDU indicating information related to inter-donor migration, the receiving IAB node sends a BAP control PDU to its child IAB nodes and / or sends a MAC indicating information related to inter-donor migration. CE; and step 930: when the receiving IAB node receives a BAP control PDU indicating a successful inter-donor migration or triggering the receiving device to perform a PDCP status report, the receiving IAB node sends a PDCP status report to the target IAB donor and / or resumes data transmission of the radio bearer; and step 940: when the receiving IAB node receives a BAP control PDU indicating an in-progress status or a start status of an inter-donor migration, the receiving IAB node may stop data transmission of all radio bearers; and step 950: when the receiving IAB node receives a BAP control PDU indicating a failed status of an inter-donor migration, the receiving IAB node may consider that a radio link failure has occurred in the link where the BAP control PDU was received.

[0097] In some embodiments with reference to FIG9B, the BAP control PDU may include a dedicated information element (IE) of any one of the three configuration formats 950, 952, and 954. In one embodiment, the IE may be referred to as OnlyPDCPStatusReportInitialization.

[0098] In one implementation, the IE can indicate the status of a migration between donors. In one implementation, the IE can include a TRUE or FALSE value. In another implementation, the IE can include only a TRUE value.

[0099] In one implementation, the TRUE value of the IE in the BAP control PDU can indicate a successful inter-donor migration. In another implementation, the TRUE value of the IE can indicate triggering at least one downstream device to send a PDCP status report corresponding to a Radio Link Control Acknowledgment Mode (RLC-AM) bearer, which has been configured to be allowed to send PDCP status reports in the uplink.

[0100] In one implementation, the FALSE value of the IE in the BAP control PDU can indicate a failed inter-donor migration. In another implementation, the FALSE value of the IE can indicate a radio link failure that occurred in the link that received the BAP control PDU.

[0101] In some embodiments referring to Figures 9C and 9D, the BAP control PDU may include assigning a dedicated value to an existing information element. The dedicated value may include a reserved value that does not conflict with other values.

[0102] In one embodiment referring to Figure 9C, PDU type 961 can be used, and new dedicated values ​​can be assigned to the PDU type. In one embodiment, the dedicated value of the PDU type in the BAP control PDU can instruct a downstream node to perform a PDCP status report, or a donor migration status selected from any subset of the set including success, failure, in progress, and start states. In another embodiment, the dedicated value of the PDU type in the BAP control PDU can instruct at least one downstream device to send a PDCP status report corresponding to a Radio Link Control Acknowledgment Mode (RLC-AM) bearer, which has been configured to be allowed to send PDCP status reports in the uplink.

[0103] In another embodiment referring to FIG9D, a Radio Link Failure (RLF) indication type 971 can be used, and a new dedicated value can be assigned to the RLF indication type. For example, in FIG9D and FIG9E, the RLF indication type can have 2 binary bits, and the binary value of the RLF indication type can include a reserved range 984 between 00 and 11 (inclusive); and by way of example, but not limited to, a dedicated value 985 indicating the status of inter-donor migration or triggering downstream node execution can include the binary value 11.

[0104] Figure 10 illustrates the logical flow of a method 1000 for updating data transmission of at least one downstream device of a migrating IAB node using a BAP control PDU during an inter-donor migration from a source IAB donor to a target IAB donor. In another embodiment, Figure 10 illustrates the logical flow of a method 1000 for notifying at least one downstream device of a migrating IAB node that an inter-donor migration from a source IAB donor to a target IAB donor has occurred using a BAP control PDU.

[0105] Referring to step 1010 in Figure 10, during the inter-donor migration, IAB node DU 1081 can send a BAP control PDU to child IAB node MT 1082 when the following conditions are met.

[0106] In one implementation, the IAB node may include a migrating IAB node; and the condition may include whether the migrating IAB node has successfully established a connection with an upstream device. The upstream device may include one of the target IAB donor and the target parent IAB node of the migrating IAB node.

[0107] In another implementation, the IAB node may include the target parent IAB node of the migrated IAB node; and the condition may include whether the migrated IAB node has successfully established a connection with the target parent IAB node of the migrated IAB.

[0108] In another implementation, an IAB node may include a child IAB node; and the condition may include whether the child IAB node receives a BAP control PDU from the child IAB node's parent IAB node.

[0109] In another embodiment, optionally and alternatively, the IAB node 1081 in FIG10 may include a migrating IAB node; and the preset conditions may include the migrating IAB node receiving a Radio Resource Control (RRC) message sent from the target IAB donor CU, and the received RRC message includes an Information Element (IE) indicating information related to the migration between donors.

[0110] Referring to step 1020 in Figure 10, in response to the received BAP control PDU, the sub-IAB node 1082 may send a BAP control PDU to one or more downstream IAB nodes of the sub-IAB node 1082.

[0111] Optionally, additionally, or alternatively, referring to step 1030 in FIG10, in response to the received BAP control PDU, sub-IAB node 1082 may send a MAC CE to one or more downstream IAB nodes and / or UEs of sub-IAB node 1082. The MAC CE may be any of the embodiments described above.

[0112] Optionally, additionally, or alternatively, referring to step 1040 in Figure 10, in response to a received BAP control PDU indicating a successful inter-donor migration or triggering a downstream node to execute a PDCP status report, IAB node 1082 may send a PDCP status report to the target IAB donor 1080. The PDCP status report may correspond to a Radio Link Control Acknowledgment Mode (RLC-AM) bearer that has been configured to allow the transmission of PDCP status reports in the uplink.

[0113] Optionally and additionally or alternatively, referring to step 1050 in FIG10, in response to the received BAP control PDU instruction, the sub-IAB node 1082 may resume data transmission of the radio bearer.

[0114] Optionally and additionally or alternatively, referring to step 1060 in FIG10, in response to a received BAP control PDU indicating the in-process state or the start state of the inter-donor migration, the sub-IAB node 1082 may stop all radio bearer data transmission.

[0115] Optionally and additionally or alternatively, referring to step 1070 in FIG10, in response to the received BAP control PDU indicating a failure state of inter-donor migration, sub-IAB node 1082 may consider that a radio link failure has occurred in the link where the BAP control PDU was received.

[0116] This disclosure describes methods, apparatus, and computer-readable media for wireless communication. This disclosure addresses the problem of updating data transmissions of one or more downstream Integrated Access Backhaul (IAB) nodes during inter-donor migration. The methods, apparatus, and computer-readable media described in this disclosure can improve wireless communication performance by notifying at least one downstream device of the migrating IAB node during inter-donor migration using RRC messages, MAC CE, or BAP control PDU, thereby improving migration efficiency and overall wireless network performance. The methods, apparatus, and computer-readable media described in this disclosure can improve the overall efficiency of wireless communication systems.

[0117] References to features, advantages, or similar language in this specification do not imply that all features and advantages achievable with this solution should or be included in any single implementation thereof. Rather, references to features and advantages are understood to mean that a particular feature, advantage, or characteristic described in connection with an embodiment is included in at least one embodiment of this solution. Therefore, the discussion of features and advantages and similar language throughout this specification may, but does not necessarily, refer to the same embodiments.

[0118] Furthermore, in one or more embodiments, the features, advantages, and characteristics of this solution can be combined in any suitable manner. Based on the description herein, those skilled in the art will recognize that this solution can be practiced without one or more specific features or advantages of a particular embodiment. In other instances, additional features and advantages may be recognized in certain embodiments that may not be present in all embodiments of this solution.

Claims

1. A wireless communication method, comprising: During the inter-donor migration of a migrating IAB node from a source IAB donor to a target IAB donor, a receiving device receives a Radio Resource Control (RRC) message sent by the target IAB donor. The RRC message includes first information indicating the success status of the inter-donor migration. The receiving device is a downstream device connected to the migrating IAB node. In response to the first information indicating a successful migration status between the donors, the receiving device triggers the sending of one or more Packet Data Convergence Protocol (PDCP) status reports to the target IAB donor.

2. The method according to claim 1, further comprising: The one or more PDCP status reports correspond to a Radio Link Control Acknowledgment Mode (RLC-AM) bearer that has been configured to send the one or more PDCP status reports in the uplink.

3. The method according to claim 1, wherein: The receiving device includes at least one user equipment (UE) connected to the migration IAB node.

4. The method according to claim 1, wherein: The receiving device includes at least one user equipment (UE) connected to a downstream IAB node of the migrating IAB node.

5. The method according to claim 1, wherein: The receiving device includes at least one downstream IAB node for migrating IAB nodes.

6. A wireless communication method, comprising: During inter-donor migration from a source IAB donor to a target IAB donor, a receiving device receives a Media Access Control (MAC) control element (CE) sent by the migrating IAB node when a first condition is met. The MAC CE includes first information indicating a successful inter-donor migration status. The receiving device includes at least one of a User Equipment (UE) and a sub-IAB node connected to the transmitting device. The first condition includes the migrating IAB node receiving a Radio Resource Control (RRC) message sent by the target IAB donor (CU) and the received RRC message including an Information Element (IE) indicating a successful inter-donor migration status. In response to the first information indicating the successful inter-donor migration status, one or more Packet Data Convergence Protocol (PDCP) status reports are triggered to be sent to the target IAB donor.

7. The method according to claim 6, further comprising: The one or more PDCP status reports correspond to a Radio Link Control Acknowledgment Mode (RLC-AM) bearer that has been configured to send the one or more PDCP status reports in the uplink.

8. A wireless communication method, comprising: During an inter-donor migration from a source IAB donor to a target IAB donor, the migrating IAB node, acting as a transmitting device, sends a Backhaul Adaptation Protocol (BAP) Control Protocol Data Unit (PDU) to a second IAB node when a first condition is met. The BAP Control PDU includes first information indicating a successful inter-donor migration status. The second IAB node includes at least one of the migrating IAB node's child IAB nodes. The first condition includes the transmitting device receiving an RRC message from the target donor CU, wherein the RRC message includes an indication that at least one upstream IAB node of the receiving device has undergone an inter-donor migration. In response to the first information, the second IAB node sends a MAC CE indicating the first information to a third device, which includes at least one child device of the second IAB node. In response to the first information indicating a successful inter-donor migration status, the third device triggers the sending of one or more Packet Data Convergence Protocol (PDCP) status reports to the target IAB donor.

9. The method according to claim 8, further comprising: The one or more PDCP status reports correspond to a Radio Link Control Acknowledgment Mode (RLC-AM) bearer that has been configured to send the one or more PDCP status reports in the uplink.

10. A wireless communication device comprising a processor and a memory, wherein, The processor is configured to read code from the memory and implement the method of any one of claims 1 to 9.

11. A computer program product comprising computer-readable program medium code stored thereon, the code, when executed by a processor, causing the processor to perform the method of any one of claims 1 to 9.

Images