WO2021109355A1 - Methods and devices for updating data transmission during inter-donor migration - Google Patents

Methods and devices for updating data transmission during inter-donor migration Download PDF

Info

Publication number
WO2021109355A1
WO2021109355A1 PCT/CN2020/079252 CN2020079252W WO2021109355A1 WO 2021109355 A1 WO2021109355 A1 WO 2021109355A1 CN 2020079252 W CN2020079252 W CN 2020079252W WO 2021109355 A1 WO2021109355 A1 WO 2021109355A1
Authority
WO
WIPO (PCT)
Prior art keywords
iab
node
donor
inter
status
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2020/079252
Other languages
English (en)
French (fr)
Inventor
Hao Zhu
Ying Huang
Lin Chen
Liping Wang
Kun CAO
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by ZTE Corp filed Critical ZTE Corp
Priority to EP20895932.0A priority Critical patent/EP4104509A4/en
Priority to KR1020227031545A priority patent/KR20220162696A/ko
Priority to JP2022554826A priority patent/JP7651587B2/ja
Priority to PCT/CN2020/079252 priority patent/WO2021109355A1/en
Priority to CA3171389A priority patent/CA3171389A1/en
Priority to CN202080098404.2A priority patent/CN115280842B/zh
Publication of WO2021109355A1 publication Critical patent/WO2021109355A1/en
Priority to US17/943,317 priority patent/US20230007544A1/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/02—Buffering or recovering information during reselection ; Modification of the traffic flow during hand-off
    • H04W36/023—Buffering or recovering information during reselection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/10—Reselecting an access point controller
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04—Large scale networks; Deep hierarchical networks
    • H04W84/042—Public Land Mobile systems, e.g. cellular systems
    • H04W84/047—Public Land Mobile systems, e.g. cellular systems using dedicated repeater stations
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices
    • H04W88/085—Access point devices with remote components

Definitions

  • the present disclosure is directed generally to wireless communications. Particularly, the present disclosure relates to methods and devices for updating data transmission during inter-donor migration.
  • Wireless communication technologies are moving the world toward an increasingly connected and networked society.
  • LTE long term evolution
  • NR fifth generation new radio
  • mmWave millimeter wave
  • MIMO massive multiple input multiple output
  • MIMO massive multiple input multiple output
  • the 5G NR may provide a much faster speed and much shorter latency.
  • the 5G NR may include an integrated access backhaul (IAB) implementation.
  • the IAB implementation may include one or more IAB-donors and multiple connecting IAB-nodes.
  • IAB integrated access backhaul
  • the present disclosure may address at least some of problems/issues associated with the existing system to improve the performance of the wireless communication.
  • This document relates to methods, systems, and devices for wireless communication, and more specifically, for updating data transmission for a downstream device of a migrating integrated access backhaul node (IAB-node) during inter-donor migration.
  • IAB-node migrating integrated access backhaul node
  • the present disclosure describes a method for wireless communication.
  • the method includes receiving, by a receiving device, a radio resource control (RRC) message sent from a transmitting device, the RRC message comprising first information which indicates inter IAB-donor migration related information, the transmitting device comprising one of a subset, the 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.
  • RRC radio resource control
  • the present disclosure describes a method for wireless communication.
  • the method includes receiving, by a receiving device, a medium access control (MAC) control element (CE) sent from a transmitting device, the MAC CE comprising a first information which indicates inter IAB-donor migration related information.
  • MAC medium access control
  • CE control element
  • the present disclosure describes a method for wireless communication.
  • the method includes sending, by a first IAB-node as a transmitting device, a backhaul adaptation protocol (BAP) control protocol data unit (PDU) to a second IAB-node, the BAP control PDU comprising first information that indicates indicates inter IAB-donor migration related information.
  • BAP backhaul adaptation protocol
  • PDU protocol data unit
  • the present disclosure describes a method for wireless communication.
  • the method includes sending, by a first IAB-node as a transmitting device, a backhaul adaptation protocol (BAP) control protocol data unit (PDU) to a second IAB-node, the BAP control PDU comprising first information that indicates inter IAB-donor migration related information.
  • BAP backhaul adaptation protocol
  • PDU protocol data unit
  • an apparatus for wireless communication may include a memory storing instructions and a processing circuitry in communication with the memory.
  • the processing circuitry executes the instructions, the processing circuitry is configured to carry out the above methods.
  • a device for wireless communication may include a memory storing instructions and a processing circuitry in communication with the memory.
  • the processing circuitry executes the instructions, the processing circuitry is configured to carry out the above methods.
  • a computer-readable medium comprising instructions which, when executed by a computer, cause the computer to carry out the above methods.
  • FIG. 1 shows an example of a wireless communication system include an integrated access backhaul (IAB) system.
  • IAB integrated access backhaul
  • FIG. 2 shows an example of an IAB-donor or IAB-node.
  • FIG. 3 shows an example of a user equipment.
  • FIG. 4 shows a schematic diagram of a migrating IAB-node in an inter-donor migration.
  • FIG. 5 shows a flow diagram of a method for wireless communication.
  • FIG. 6 shows an exemplary logic flow of the method for wireless communication in FIG. 5.
  • FIG. 7A shows a flow diagram of another method for wireless communication.
  • FIG. 7B shows an example of a medium access control (MAC) control element (CE) .
  • MAC medium access control
  • CE control element
  • FIG. 7C shows an example of a dedicated logic channel identifier (LCID) value.
  • LCID dedicated logic channel identifier
  • FIG. 8 shows an exemplary logic flow of the method for wireless communication in FIG. 7A.
  • FIG. 9A shows a flow diagram of another method for wireless communication.
  • FIG. 9B shows several examples of configuration formats for a backhaul adaptation protocol (BAP) control protocol data unit (PDU) .
  • BAP backhaul adaptation protocol
  • PDU protocol data unit
  • FIG. 9C shows one example of a backhaul adaptation protocol (BAP) control protocol data unit (PDU) .
  • BAP backhaul adaptation protocol
  • PDU control protocol data unit
  • FIG. 9D shows another example of a backhaul adaptation protocol (BAP) control protocol data unit (PDU) .
  • BAP backhaul adaptation protocol
  • PDU control protocol data unit
  • FIG. 9E shows one example of a dedicated radio link failure (RLF) indication type value.
  • RLF radio link failure
  • FIG. 10 shows an exemplary logic flow of the method for wireless communication in FIG. 9A.
  • terms, such as “a”, “an” , or “the” may be understood to convey a singular usage or to convey a plural usage, depending at least in part upon context.
  • the term “based on” or “determined by” may be understood as not necessarily intended to convey an exclusive set of factors and may, instead, allow for existence of additional factors not necessarily expressly described, again, depending at least in part on context.
  • the present disclosure describes methods and devices for updating data transmission for a downstream device of a migrating integrated access backhaul node (IAB-node) during inter-donor migration.
  • IAB-node migrating integrated access backhaul node
  • Next generation (NG) or 5th generation (5G)
  • wireless communication may provide a range of capabilities from downloading with fast speeds to support real-time low-latency communication.
  • LTE long-term evolution
  • the 5G new radio (NR) technology have a much wider spectrum, for example, including millimeter wave (mmWave) frequency bands.
  • MIMO massive multiple input multiple output
  • the 5G NR may provide a much faster speed and much shorter latency.
  • the 5G NR may include a development of an integrated access backhaul (IAB) implementation.
  • the IAB implementation may include one or more IAB-donors and multiple connecting IAB-nodes.
  • the IAB implementation may communicate between one or more IAB-donors and one or more IAB-nodes via wireless backhaul and relay links.
  • the IAB implementation may provide a flexible NR cell configuration and increase cell density without increasing the density of IAB-donors.
  • An IAB system may include one or more IAB-donors and one or more IAB-nodes, which collectively provide wireless connection service to one or more user equipment (UEs) (e.g., smartphones) .
  • the IAB-donors and IAB-nodes may be wireless network base stations including a NG radio access network (NG-RAN) base station, which may include a nodeB (NB, e.g., a gNB) in a mobile telecommunications context.
  • NG-RAN NG radio access network
  • NB nodeB
  • the IAB-donor may provide access backhaul to one or more connecting child IAB-nodes, and may connect to a core network via a wired communication.
  • the core network may include a 5G core network (5GC) .
  • 5GC 5G core network
  • the wired communication may include a fiber transport communication.
  • the IAB-node may include wireless access link and wireless backhaul link.
  • the wireless access link may be used for communication between a UE and the IAB-node.
  • the wireless backhaul link may be used for communication between the IAB-node and the IAB-donor, and/or communications between one IAB-node with another IAB-node.
  • the IAB-node does not need a wired communication network for data backhaul.
  • the IAB-node does not include a wired communication network for data backhaul, so that IAB-node are more flexible and easier to implement, mitigating the burden of implementing wired communication network.
  • the access link and backhaul link may use transmission bands with same frequency (known as in-band relay) , or use transmission bands with different frequency (known as out-band relay) .
  • the IAB-donor 130 may provide access backhaul 140 to one or more connecting child IAB-nodes (152 and 154) .
  • the IAB-donor 130 may connect to a core network 110 via a wired communication 120.
  • the core network 110 may include a 5G core network (5GC) .
  • the wired communication 120 may include a fiber transport communication.
  • An IAB-donor may provide a wireless connection to one or more user equipment (UE) .
  • the UE may be a mobile device, for example, a smart phone or a mobile communication module disposed in a vehicle.
  • the IAB-donor 130 may provide a wireless connection 160 to a UE 172.
  • a child IAB-node may provide a wireless connection to one or more UEs.
  • the IAB-node 152 may provide a wireless connection 160 to a UE 174.
  • a child IAB-node may provide access backhaul to one or more downstream IAB-nodes.
  • the IAB-node 154 may provide access backhaul 140 to a downstream IAB-node 156 and a downstream IAB-node 157.
  • the IAB-node 156 may be called as a child IAB-node of the IAB-node 154; and the IAB-node 157 may be called as a grandchild IAB-node of the IAB-node 154.
  • the grandchild IAB-node 157 may also provide access backhaul to one or more connecting great-grandchild IAB-nodes and/or provide wireless connection to one or more UEs (for example, UE 178) .
  • the IAB system 100 may include another IAB-donor 135.
  • the IAB-donor 135 may also connect to the core network (e.g., 5GC) 110 via a wired communication 120.
  • the IAB-donor 135 may provide access backhaul 140 to one or more connecting child IAB-nodes 158; and the IAB-node 158 may provide a wireless connection 160 to one or more UE 176.
  • the IAB-node 156 which currently connects to the IAB-donor 130 via the IAB-node 154, may migrate to the IAB-donor 135. This may be called as an inter-donor migration and the IAB-node 156 may be called as a migrating IAB-node.
  • IAB-node or UE downstream device
  • the target gNB may retransmit a portion of the data packets so as to ensure a continuation of the communication service to a UE.
  • the UE may send a packet data convergence protocol (PDCP) status report to the target gNB.
  • the PDCP status report may inform the target gNB the conditions (e.g., failure or success conditions) of the data packets received by the UE, and thus, the target gNB may decide which data packet is selected for retransmission or transmission.
  • UE’s sending PDCP status report may be triggered by PDCP data recovery and/or PDCP re-establishment.
  • UE may need to retransmit PDCP protocol data units (PDUs) or PDCP service data units (SDUs) that have not been confirmed by a lower layer (for example, radio link control (RLC) layer) .
  • PDUs PDCP protocol data units
  • SDUs PDCP service data units
  • UE may send PDCP status report during inter-gNB migration by the following procedures.
  • the target gNB may send a radio resource control (RRC) message via the source gNB.
  • RRC radio resource control
  • the RRC message may be configured inside a RRC container of the source gNB and the UE; the RRC message may also include an information element of reestablishPDCP.
  • the information element of reestablishPDCP may trigger PDCP re-establishment procedure, and trigger UE to send PDCP status reporter.
  • the UE may send the PDCP statu report to target gNB after the connection between the UE and the target gNB is successfully established.
  • the UE may report the PDCP status report.
  • some problems/issues occur.
  • One of the problems/issues may include that, after the migrating IAB-node establishes connection between the IAB-node and target gNB-CU, a UE connecting with the migrating IAB-node may need be triggered to send PDCP status report to the target IAB-donor.
  • the triggering events may include one of the PDCP data recovery procedure and the PDCP re-establishment procedure. This may lead to retransmission of data packets which could arrive at IAB-donor CU but was in the source route during the period of the migrating IAB-node's migration, then wasting network resources and resulting in low performance.
  • the present disclosure describes embodiments of methods and devices of updating configuration information for at least one of the migrating IAB-node and/or the downstream devices of the migrating IAB-node during the inter-donor migration of the migrating IAB-node, addressing at least some of the problems discussed above.
  • the downstream IAB-node and/or corresponding UEs may send PDCP status report to the target IAB-node without receiving either PDCP data recovery or PDCP re-establishment process.
  • FIG. 2 shows 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 the IAB-nodes (152, 154, 156, and 158) in FIG. 1.
  • the base station 200 may include radio transmitting/receiving (Tx/Rx) circuitry 208 to transmit/receive communication with one or more UEs, and/or one or more other base stations.
  • the base station may also include network interface circuitry 209 to communicate the base station with other base stations and/or a core network, e.g., optical or wireline interconnects, Ethernet, and/or other data transmission mediums/protocols.
  • the base station 200 may optionally include an input/output (I/O) interface 206 to communicate with an operator or the like.
  • I/O input/output
  • the base station may also include system circuitry 204.
  • System circuitry 204 may include processor (s) 221 and/or memory 222.
  • Memory 222 may include an operating system 224, instructions 226, and parameters 228.
  • Instructions 226 may be configured for the one or more of the processors 124 to perform the functions of the base station.
  • the parameters 228 may include parameters to support execution of the instructions 226. For example, parameters may include network protocol settings, bandwidth parameters, radio frequency mapping assignments, and/or other parameters.
  • FIG. 3 shows an exemplary user equipment (UE) 300.
  • the UE 300 may be a mobile device, for example, a smart phone or a mobile communication module disposed in a vehicle.
  • the UE 300 may be an exemplary implementation of at least one of the UEs (172, 174, and 176) in FIG. 1.
  • the UE 300 may include communication interfaces 302, a system circuitry 304, an input/output interfaces (I/O) 306, a display circuitry 308, and a storage 309.
  • the display circuitry may include a user interface 310.
  • the system circuitry 304 may include any combination of hardware, software, firmware, or other logic/circuitry.
  • the system circuitry 304 may be implemented, for example, with one or more systems on a chip (SoC) , application specific integrated circuits (ASIC) , discrete analog and digital circuits, and other circuitry.
  • SoC systems on a chip
  • ASIC application specific integrated circuits
  • the system circuitry 304 may be a part of the implementation of any desired functionality in the UE 300.
  • the system circuitry 304 may include logic that facilitates, as examples, decoding and playing music and video, e.g., MP3, MP4, MPEG, AVI, FLAC, AC3, or WAV decoding and playback; running applications; accepting user inputs; saving and retrieving application data; establishing, maintaining, and terminating cellular phone calls or data connections for, as one example, internet connectivity; establishing, maintaining, and terminating wireless network connections, Bluetooth connections, or other connections; and displaying relevant information on the user interface 310.
  • the user interface 310 and the inputs/output (I/O) interfaces 306 may include a graphical user interface, touch sensitive display, haptic feedback or other haptic output, voice or facial recognition inputs, buttons, switches, speakers and other user interface elements.
  • I/O interfaces 306 may include microphones, video and still image cameras, temperature sensors, vibration sensors, rotation and orientation sensors, headset and microphone input /output jacks, Universal Serial Bus (USB) connectors, memory card slots, radiation sensors (e.g., IR sensors) , and other types of inputs.
  • USB Universal Serial Bus
  • the communication interfaces 302 may include a Radio Frequency (RF) transmit (Tx) and receive (Rx) circuitry 316 which handles transmission and reception of signals through one or more antennas 314.
  • the communication interface 302 may include one or more transceivers.
  • the transceivers may be wireless transceivers that include modulation /demodulation circuitry, digital to analog converters (DACs) , shaping tables, analog to digital converters (ADCs) , filters, waveform shapers, filters, pre-amplifiers, power amplifiers and/or other logic for transmitting and receiving through one or more antennas, or (for some devices) through a physical (e.g., wireline) medium.
  • the transmitted and received signals may adhere to any of a diverse array of formats, protocols, modulations (e.g., QPSK, 16-QAM, 64-QAM, or 256-QAM) , frequency channels, bit rates, and encodings.
  • the communication interfaces 302 may include transceivers that support transmission and reception under the 2G, 3G, BT, WiFi, Universal Mobile Telecommunications System (UMTS) , High Speed Packet Access (HSPA) +, 4G /Long Term Evolution (LTE) , and 5G standards.
  • UMTS Universal Mobile Telecommunications System
  • HSPA High Speed Packet Access
  • LTE Long Term Evolution
  • 5G 5G
  • the system circuitry 304 may include one or more processors 321 and memories 322.
  • the memory 322 stores, for example, an operating system 324, instructions 326, and parameters 328.
  • the processor 321 is configured to execute the instructions 326 to carry out desired functionality for the UE 300.
  • the parameters 328 may provide and specify configuration and operating options for the instructions 326.
  • the memory 322 may also store any BT, WiFi, 3G, 4G, 5G or other data that the UE 300 will send, or has received, through the communication interfaces 302.
  • a system power for the UE 300 may be supplied by a power storage device, such as a battery or a transformer.
  • the present disclosure describes several embodiments of methods and devices for updating data transmission for at least one downstream device of a migrating integrated access backhaul node (IAB-node) during inter-donor migration, which may be implemented, partly or totally, on the wireless network base station and/or the user equipment described above in FIGS. 2 and 3.
  • IAB-node migrating integrated access backhaul node
  • an IAB system 400 may include one or more IAB-donors (410 and 420) .
  • An IAB-node 450 which currently connects to the IAB-donor 410 via an IAB-node 430, may migrate to the IAB-donor 420 via an IAB-node 440. This may be called an inter-donor migration.
  • the IAB-node 450 may be a migrating IAB-node; the IAB-donor 410 may be a source IAB-donor; the IAB-node 430 may be a source parent IAB-node; the IAB-donor 420 may be a target IAB-donor; the IAB-node 440 may be a target parent IAB-node.
  • one IAB-node there may be one or more upstream IAB-nodes 492, which may collectively connect the IAB-node to the corresponding IAB-donor; and there may be one or more downstream devices 494 connecting to the IAB-node, which may include one or more downstream IAB-nodes and/or one or more downstream UEs.
  • the migrating IAB-node 450 may connect to a IAB-donor via one or more IAB-nodes, which may be collectively called as parent IAB-nodes.
  • the source IAB-donor 410 may include a central unit (CU) 412 and a distributed unit (DU) 414, and the source IAB-donor CU 412 may communicate with the source IAB-donor DU 414.
  • the source parent IAB-node 430 in communication with the source IAB-donor 410 may include a mobile termination (MT) 432 and a distributed unit (DU) 434.
  • the target IAB-donor 420 may include a CU 422 and a DU 424, and the target IAB-donor CU 422 may communicate with the target IAB-donor DU 424.
  • the target IAB-node 440 in communication with the target IAB-donor 420 may include a MT 442 and a DU 444.
  • the migrating IAB-node 450 may be in communication with the source parent IAB-node 430.
  • the migrating IAB-node 450 may include a MT 452 and a DU 454.
  • the migrating IAB-node 450 may be in communication with a UE 470.
  • the migrating IAB-node 450 may be in communication with a child IAB-node 460.
  • the child IAB-node 460 may include a MT 462 and a DU 464.
  • the child IAB-node 460 may be in communication with a UE 472.
  • the migrating IAB-node 450 may change its attachment point from the source parent IAB-node 430 connecting to the source IAB-donor 410 to a target IAB-node 440 connecting to the target IAB-donor 420.
  • a handover (HO) process may occur during the inter-donor migration, and this may be an inter-CU HO scenario.
  • the migrating IAB-node DU 454 may communicate with the target IAB-donor CU 422 via F1-AP message 482.
  • the present disclosure describes various embodiment of a method 500 for using a radio resource control (RRC) message to inform at least one downstream device of a migrating integrated access backhaul node (IAB-node) that the migrating IAB-node occurs an inter-donor migration from a source IAB-donor to a target IAB-donor.
  • RRC radio resource control
  • the method may solve a problem/issue associated with requiring PDCP data recovery and/or PDCP re-establishment for a receiving device to trigger sending PDCP status reporting.
  • the method 500 may include a portion or all of the following steps: step 510: receiving, by the at least one downstream device of the migrating IAB-node, a radio resource control (RRC) message sent from a target IAB-donor central unit (CU) , the RRC message comprising an information element (IE) indicating that the migrating IAB-node occurs an inter-donor migration; and step 520: in response to the IE further indicating a successful inter-donor migration or a trigger for the receiving device to perform the procedure of packet data convergence protocol (PDCP) status reporting, sending, by the at least one downstream device, a packet data convergence protocol (PDCP) status report to the target IAB-donor, the PDCP status report corresponding to a radio link control acknowledged mode (RLC-AM) bearer which has been configured to be allowed to send a PDCP status report in the uplink.
  • RRC radio resource control
  • the method 500 may optionally and additionally or alternatively include step 530: in response to the IE further indicating a successful inter-donor migration, resuming, by the at least one downstream device, the data transmission of radio bearers.
  • the method 500 may optionally and additionally or alternatively include step 540: in response to the first information further indicating the ongoing status of the inter-donor migration or the starting status of the inter-donor migration, the receiving device stops data transmission of all radio bearers.
  • the method 500 may optionally and additionally or alternatively include step 550: in response to the first information further indicating the failed status of the inter-donor migration, the receiving device stops or cancels the behaviors related to the inter-donor migration.
  • the RRC message may be a RRC Reconfiguration message.
  • the IE may indicate a status of the inter-donor migration. In one implementation, the IE may include a value of either TRUE or FALSE. In another implementation, the IE may include a value of TRUE only.
  • the TRUE value of the IE in the RRC message may indicate a successful inter-donor migration.
  • the TRUE value of the IE may indicate to trigger the at least one downstream device to send the PDCP status report corresponding to a radio link control acknowledged mode (RLC-AM) bearer which has been configured to be allowed to send the PDCP status report in the uplink.
  • RLC-AM radio link control acknowledged mode
  • the FALSE value of the IE in the RRC message may indicate a failed inter-donor migration. In another implementation, the FALSE value of the IE may indicate not to trigger the receiving end to send the PDCP status report corresponding to the RLC-AM bearer which has been configured to be allowed to send the PDCP status report in the uplink.
  • FIG. 6 shows a logic flow of a method 600 for using a RRC message to update data transmission for at least one downstream device of a migrating IAB-node during an inter-donor migration from a source IAB-donor to a target IAB-donor.
  • FIG. 6 shows a logic flow of a method 600 for using a RRC message to inform at least one downstream device of a migrating IAB-node that the migrating IAB-node occurs an inter-donor migration from a source IAB-donor to a target IAB-donor.
  • a target IAB-donor CU 680 may send a RRC message to an IAB-node MT 682.
  • the IAB-node may include a migrating IAB-node.
  • the IAB-node may include a downstream IAB-node of the migrating IAB-node.
  • the target IAB-donor CU 680 may send a RRC message to a UE 684.
  • the UE 684 may include a UE connecting with the migrating IAB-node.
  • the UE 684 may include a UE connecting to a downstream IAB-node of the migrating IAB-node.
  • the IAB-node MT 682 may sends a packet data convergence protocol (PDCP) status report to the target IAB-donor.
  • the PDCP status report may correspond to a radio link control acknowledged mode (RLC-AM) bearer which has been configured to be allowed to send a PDCP status report in a uplink.
  • RLC-AM radio link control acknowledged mode
  • the UE 684 may sends a PDCP status report to the target IAB-donor.
  • the PDCP status report may correspond to a radio link control acknowledged mode (RLC-AM) bearer which has been configured to be allowed to send a PDCP status report in a uplink.
  • RLC-AM radio link control acknowledged mode
  • the present disclosure describes various embodiment of a method 700 for using a medium access control (MAC) control element (CE) to inform at least one downstream device of a migrating integrated access backhaul node (IAB-node) that the migrating IAB node occurs an inter-donor migration from a source IAB-donor to a target IAB-donor.
  • the method may solve a problem/issue associated with requiring PDCP data recovery and/or PDCP re-establishment for a receiving device to trigger sending PDCP status reporting.
  • the method 700 may include a portion or all of the following steps:
  • step 710 sending, by an IAB-node DU, a medium access control (MAC) control element (CE) to at least one downstream device of the IAB-node, the MAC CE indicating that the migrating IAB-node occurs an inter-donor migration;
  • MAC medium access control
  • CE control element
  • step 720 when a receiving device is a UE and the IE further indicates a successful inter-donor migration or triggering a procedure of PDCP status reporting or a trigger for the receiving device to perform the procedure of PDCP status reporting, the UE sends a PDCP status report to the target IAB-donor, the PDCP status report corresponding to a radio link control acknowledged mode (RLC-AM) bearer which has been configured to be allowed to send a PDCP status report in the uplink;
  • RLC-AM radio link control acknowledged mode
  • step 730 when a receiving device is an IAB-node, the IAB-node sends a MAC CE to its child IAB-node and/or its connecting UE;
  • step 740 in response to the received MAC CE indicating a successful inter-donor migration, the UE may resume the data transmission of radio bearers;
  • step 750 when the IE further indicates an ongoing status of an inter-donor migration or a stating status of an inter-donor migration, the receiving device (for example, an IAB-node or a UE) stops data transmission for all radio bearers; and
  • step 760 when the IE further indicates an failed status of an inter-donor migration, the receiving device (for example, an IAB-node or a UE) considers a radio link failure occurs in a link where the MAC CE is received.
  • the receiving device for example, an IAB-node or a UE
  • the MAC CE is identified by a MAC subheader 750 including a logic channel ID (LCID) 755.
  • the LCID may include a reserved value which has no conflict with other values.
  • a LCID value 782 may correspond to an index 780 to the LCID value.
  • the LCID may have 6 binary bits, and the value of LCID for downlink-shared channel (DL-SCH) may include a reserved range 784 of between 33 and 44, inclusive; and the Only PDCP Status Reporting 785 may include a value of 44.
  • the MAC CE may have a fixed size of zero bits for its load.
  • FIG. 8 shows a logic flow of a method 800 for using a MAC CE to update data transmission for at least one downstream device of a migrating IAB-node during an inter-donor migration from a source IAB-donor to a target IAB-donor.
  • FIG. 8 shows a logic flow of a method 600 for using a MAC CE to inform at least one downstream device of a migrating IAB-node that the migrating IAB-node occurs an inter-donor migration from a source IAB-donor to a target IAB-donor.
  • an IAB-node DU 881 may send a MAC CE to a child IAB-node MT 682.
  • the IAB-node may include a migrating IAB-node; and the condition may include that the migrating IAB-node succeeds in establishing or fails in establishing or undergoes establishing a connection with an upstream device.
  • the upstream device may include one of the target IAB-donor and a target parent IAB-node of the migrating IAB-node.
  • the IAB-node may include a target parent IAB-node of the migrating IAB-node; and condition may include that the migrating IAB-node succeeds in establishing or fails in establishing or undergoes establishing or starts establishing a connection with the target parent IAB-node of the migrating IAB-node.
  • the IAB node may include a child IAB-node; and the condition may include whether the child IAB-node receives the MAC CE from a parent IAB-node of the child IAB-node.
  • the condition may include the migrating IAB-node; and the preset condition may include that the migrating IAB-node receives a radio resource control (RRC) message sent from a target IAB-donor CU and the received RRC message comprises an information element (IE) indicating an information related to inter-donor migration.
  • RRC radio resource control
  • IE information element
  • the IAB-node DU 881 may send a MAC CE to a UE 884.
  • the UE 884 connects to the IAB-node.
  • the 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 acknowledged mode (RLC-AM) bearer which has been configured to be allowed to send a PDCP status report in a uplink.
  • RLC-AM radio link control acknowledged mode
  • the IAB-node 882 may send the MAC CE to one or more downstream IAB-node and/or UE of the IAB-node 882.
  • the UE 884 may send a PDCP status report to the target IAB-donor 880.
  • the PDCP status report may correspond to a RLC-AM bearer, which has been configured to be allowed to send a PDCP status report in an uplink.
  • the UE 884 may resume the data transmission of radio bearers.
  • the receiving device in response to the received MAC CE indicating an ongoing status of inter-donor migration or a starting status of inter-donor migration, the receiving device (the IAB-node 882, or the UE 884) may stop data transmission of all radio bearers.
  • the receiving device in response to the received MAC CE indicating failed status of inter-donor migration, the receiving device (the IAB-node 882, or the UE 884) may consider a radio link failure occurs in a link where the MAC CE is received.
  • the present disclosure describes various embodiment of a method 900 for using a backhaul adaptation protocol (BAP) control protocol data unit (PDU) to inform at least one downstream device of a migrating integrated access backhaul node (IAB-node) of an information related to inter-donor migration where the migrating IAB-node migrates from a source IAB-donor to a target IAB-donor.
  • BAP backhaul adaptation protocol
  • PDU control protocol data unit
  • the information related to inter-donor migration in BAP control PDU further comprising that at least one of an upstream IAB nodes of the first IAB-node occurs an inter-donor migration from a source IAB-donor to a target IAB-donor, or a successful status of the inter-donor migration, or an ongoing status of the inter-donor migration, or a starting status of the inter-donor migration, or a failed status of the inter-donor migration, or an indication triggering the receiving device to perform the procedure of packet data convergence protocol (PDCP) status reporting
  • PDCP packet data convergence protocol
  • the method 900 may include a portion or all of the following steps: step 910: sending, by an IAB-node DU, a BAP control PDU to at least one downstream IAB-node of the IAB-node; step 920: when a receiving IAB-node receives the BAP control PDU indicating an information related to inter-donor migration, the receiving IAB-node sends a BAP control PDU to its child IAB-node and/or sends a MAC CE indicating an information related to inter-donor migration; and step 930: when a receiving IAB-node receives the BAP control PDU indicating a successful inter-donor migration or a trigger for the receiving device to perform procedure of PDCP status reporting, the receiving IAB-node sends a PDCP status report to the target IAB-donor and/or resume the data transmission of radio bearers; and step 940: when a receiving IAB-node receives the BAP control PDU
  • the BAP control PDU may include a dedicated information element (IE) in any one of the three configuration formats 950, 952, and 954.
  • the IE may be called as OnlyPDCPStatusReportInitialization.
  • the IE may indicate a status of the inter-donor migration. In one implementation, the IE may include a value of either TRUE or FALSE. In another implementation, the IE may include a value of TRUE only.
  • the TRUE value of the IE in the BAP control PDU may indicate a successful inter-donor migration.
  • the TRUE value of the IE may indicate to trigger the at least one downstream device to send the PDCP status report corresponding to a radio link control acknowledged mode (RLC-AM) bearer which has been configured to be allowed to send the PDCP status report in the uplink.
  • RLC-AM radio link control acknowledged mode
  • the FALSE value of the IE in the BAP control PDU may indicate a failed inter-donor migration. In another implementation, the FALSE value of the IE may indicate a radio link failure occurs in a link where the BAP control PDU is received.
  • the BAP control PDU may include assigning a dedicated value to one already existing information element.
  • the dedicated value may include a reserved value which has no conflict with other values.
  • a PDU type 961 may be used, and a new dedicated value may be assigned to the PDU type.
  • the dedicated value for the PDU type in the BAP control PDU may indicate a trigger for downstream nodes to perform PDCP status reporting, or a status of the inter-donor migration selected form any subset of a set including a successful status, a failed status, an ongoing status, and a starting status.
  • the dedicated value for the PDU type in the BAP control PDU may indicate to trigger the at least one downstream device to send the PDCP status report corresponding to a radio link control acknowledged mode (RLC-AM) bearer which has been configured to be allowed to send the PDCP status report in the uplink.
  • RLC-AM radio link control acknowledged mode
  • a radio link failure (RLF) indication type 971 may be used, and a new dedicated value may be assigned to the RLF indication type.
  • the RLF indication type may have 2 binary bits, and the binary value of RLF indication type may include a reserved range 984 of between 00 and 11, inclusive; and as an example but not limited to, the dedicated value 985 indicating a status of inter-donor migration or a trigger for downstream nodes to perform may include a binary value of 11.
  • FIG. 10 shows a logic flow of a method 1000 for using a BAP control PDU to update data transmission for at least one downstream device of a migrating IAB-node during an inter-donor migration from a source IAB-donor to a target IAB-donor.
  • FIG. 10 shows a logic flow of a method 1000 for using a BAP control PDU to inform at least one downstream device of a migrating IAB-node that the migrating IAB-node occurs an inter-donor migration from a source IAB-donor to a target IAB-donor.
  • an IAB-node DU 1081 may send a BAP control PDU to a child IAB-node MT 1082.
  • the IAB-node may include a migrating IAB-node; and the condition may include whether the migrating IAB-node successfully establishes a connection with an upstream device.
  • the upstream device may include one of the target IAB-donor and a target parent IAB-node of the migrating IAB-node.
  • the IAB-node may include a target parent IAB-node of the migrating IAB-node; and the condition may include whether the migrating IAB-node successfully establishes a connection with the target parent IAB-node of the migrating IAB-node.
  • the IAB node may include a child IAB-node; and the condition may include whether the child IAB-node receives the BAP control PDU from a parent IAB-node of the child IAB-node.
  • the IAB node 1081 in FIG. 10 may include the migrating IAB-node; and the preset condition may include that the migrating IAB-node receives a radio resource control (RRC) message sent from a target IAB-donor CU and the received RRC message comprises an information element (IE) indicating an information related to inter-donor migration.
  • RRC radio resource control
  • the child IAB-node 1082 may send a BAP control PDU to one or more downstream IAB-nodes of the child IAB-node 1082.
  • the child IAB-node 1082 may send a MAC CE to one or more downstream IAB-node and/or UE of the child IAB-node 1082.
  • the MAC CE may be any embodiments as discussed above.
  • the 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 acknowledged mode (RLC-AM) bearer that has been configured to be allowed to send a PDCP status report in an uplink.
  • RLC-AM radio link control acknowledged mode
  • the child IAB-node 1082 may resume the data transmission of radio bearers.
  • the child IAB-node 1082 may stop data transmission of all radio bearers.
  • the child IAB-node 1082 may consider a radio link failure occurs in a link where the BAP control PDU is received.
  • the present disclosure describes methods, apparatus, and computer-readable medium for wireless communication.
  • the present disclosure addressed the issues with updating data transmission of one or more downstream integrated access backhaul (IAB) nodes during inter-donor migration.
  • IAB integrated access backhaul
  • the methods, devices, and computer-readable medium described in the present disclosure may facilitate the performance of wireless communication by using a RRC message, or using a MAC CE, or using a BAP control PDU to inform at least one downstream device of a migrating IAB-node during inter-donor migration, thus improving migration efficiency and overall wireless network performance.
  • the methods, devices, and computer-readable medium described in the present disclosure may improves the overall efficiency of the wireless communication systems.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
PCT/CN2020/079252 2020-03-13 2020-03-13 Methods and devices for updating data transmission during inter-donor migration Ceased WO2021109355A1 (en)

Priority Applications (7)

Application Number Priority Date Filing Date Title
EP20895932.0A EP4104509A4 (en) 2020-03-13 2020-03-13 METHODS AND DEVICES FOR UPDATING DATA TRANSFER DURING MIGRATION BETWEEN DONORS
KR1020227031545A KR20220162696A (ko) 2020-03-13 2020-03-13 도너간 마이그레이션 중에 데이터 전송을 업데이트하기 위한 방법 및 디바이스
JP2022554826A JP7651587B2 (ja) 2020-03-13 2020-03-13 ドナー間の移行中にデータ伝送を更新する方法およびデバイス
PCT/CN2020/079252 WO2021109355A1 (en) 2020-03-13 2020-03-13 Methods and devices for updating data transmission during inter-donor migration
CA3171389A CA3171389A1 (en) 2020-03-13 2020-03-13 Methods and devices for updating data transmission during inter-donor migration
CN202080098404.2A CN115280842B (zh) 2020-03-13 用于在施主间迁移期间更新数据传输的方法和设备
US17/943,317 US20230007544A1 (en) 2020-03-13 2022-09-13 Methods and devices for updating data transmission during inter-donor migration

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/079252 WO2021109355A1 (en) 2020-03-13 2020-03-13 Methods and devices for updating data transmission during inter-donor migration

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/943,317 Continuation US20230007544A1 (en) 2020-03-13 2022-09-13 Methods and devices for updating data transmission during inter-donor migration

Publications (1)

Publication Number Publication Date
WO2021109355A1 true WO2021109355A1 (en) 2021-06-10

Family

ID=76222308

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/079252 Ceased WO2021109355A1 (en) 2020-03-13 2020-03-13 Methods and devices for updating data transmission during inter-donor migration

Country Status (6)

Country Link
US (1) US20230007544A1 (https=)
EP (1) EP4104509A4 (https=)
JP (1) JP7651587B2 (https=)
KR (1) KR20220162696A (https=)
CA (1) CA3171389A1 (https=)
WO (1) WO2021109355A1 (https=)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023028831A1 (en) * 2021-08-31 2023-03-09 Nec Corporation Methods, devices, and computer readable medium for communication

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022199698A1 (en) * 2021-03-25 2022-09-29 FG Innovation Company Limited Method of triggering packet data convergence protocol status report and related device

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110536350A (zh) * 2019-02-14 2019-12-03 中兴通讯股份有限公司 Iab链路控制方法、通信单元、计算机可读存储介质
WO2019242683A1 (zh) * 2018-06-21 2019-12-26 华为技术有限公司 路径变更方法及装置
WO2019246446A1 (en) 2018-06-21 2019-12-26 Google Llc Maintaining communication and signaling interfaces through a donor base station handover
CN110740485A (zh) * 2019-09-30 2020-01-31 河南牧业经济学院 集成接入和回程系统的节点选择方法及其装置
US20200053600A1 (en) 2017-02-03 2020-02-13 Samsung Electronics Co., Ltd. Method and apparatus for transmitting data in a mobile communication system
CN110830979A (zh) * 2018-08-09 2020-02-21 中兴通讯股份有限公司 信息传输方法及装置
US20210058985A1 (en) 2018-05-09 2021-02-25 Kyocera Corporation Mobile communication system, relay node, and base station

Family Cites Families (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11219077B2 (en) * 2017-05-05 2022-01-04 Samsung Electronics Co., Ltd. Method and apparatus for coordination of RRC configurations between interworking nodes in dual connectivity
US11483891B2 (en) * 2017-08-11 2022-10-25 Samsung Electronics Co., Ltd. Method for performing bearer type change of a plurality of bearers configured for user equipment
US11190989B2 (en) * 2018-05-22 2021-11-30 Apple Inc. Mobility management for inter-gNB (next generation node-b) handover in new radio (NR) systems
WO2019246350A1 (en) * 2018-06-20 2019-12-26 Convida Wireless, Llc Efficient buffer management in multi-hops data forwarding
WO2019245329A1 (en) * 2018-06-21 2019-12-26 Lg Electronics Inc. Method and apparatus for performing conditional cell change in wireless communication system
US10939357B2 (en) * 2018-07-03 2021-03-02 Nokia Solutions And Networks Oy Integrated access and backhaul adaptation layer status report
KR20200013576A (ko) * 2018-07-30 2020-02-07 주식회사 케이티 5g 무선 릴레이를 위한 흐름 제어 방법 및 장치
WO2020027508A1 (en) * 2018-07-31 2020-02-06 Samsung Electronics Co., Ltd. Wireless node communication method and apparatus in wireless communication system
KR102654118B1 (ko) * 2018-08-07 2024-04-03 삼성전자주식회사 무선 통신 시스템에서 데이터를 송수신하는 방법 및 장치
US11758432B2 (en) * 2018-08-09 2023-09-12 Telefonaktiebolaget Lm Ericsson (Publ) Enhanced end to end flow control for multi-hop integrated access backhaul (IAB) networks
CN118574248A (zh) * 2018-09-19 2024-08-30 三星电子株式会社 用于在无线通信系统中发送和接收数据的方法和装置
US12075505B2 (en) * 2019-02-13 2024-08-27 Telefonaktiebolaget Lm Ericsson (Publ) Efficient backhaul-link failure recovery in integrated access backhaul (IAB) networks
JP6977187B2 (ja) * 2019-02-14 2021-12-08 京セラ株式会社 通信制御方法
JP7303290B2 (ja) * 2019-03-28 2023-07-04 京セラ株式会社 通信制御方法
WO2020222308A1 (en) * 2019-05-02 2020-11-05 Sharp Kabushiki Kaisha Conditional handovers for wireless relay networks
KR102913947B1 (ko) * 2019-07-08 2026-01-15 퀄컴 인코포레이티드 비확인 응답 모드(um) 데이터 라디오 베어러(drb)를 위한 무손실 송신
US20210045168A1 (en) * 2019-08-07 2021-02-11 Lg Electronics Inc. Method and apparatus for transmitting data unit based on backhaul identifier in wireless communication system
US11363662B2 (en) * 2019-11-20 2022-06-14 Lg Electronics Inc. Method and apparatus for reporting a connection failure with a target network during handover in a wireless communication system
EP4093084B1 (en) * 2020-02-05 2025-08-20 Samsung Electronics Co., Ltd. Device and method for transmitting and receiving signal in wireless communication system

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200053600A1 (en) 2017-02-03 2020-02-13 Samsung Electronics Co., Ltd. Method and apparatus for transmitting data in a mobile communication system
US20210058985A1 (en) 2018-05-09 2021-02-25 Kyocera Corporation Mobile communication system, relay node, and base station
WO2019242683A1 (zh) * 2018-06-21 2019-12-26 华为技术有限公司 路径变更方法及装置
WO2019246446A1 (en) 2018-06-21 2019-12-26 Google Llc Maintaining communication and signaling interfaces through a donor base station handover
CN110830979A (zh) * 2018-08-09 2020-02-21 中兴通讯股份有限公司 信息传输方法及装置
CN110536350A (zh) * 2019-02-14 2019-12-03 中兴通讯股份有限公司 Iab链路控制方法、通信单元、计算机可读存储介质
CN110740485A (zh) * 2019-09-30 2020-01-31 河南牧业经济学院 集成接入和回程系统的节点选择方法及其装置

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
QUALCOMM INCORPORATED: "Integrated Access and Backhaul for NR", 3GPP DRAFT; RP-192518, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. TSG RAN, no. Sitges, Spain; 20191209 - 20191212, 2 December 2019 (2019-12-02), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051834156 *
See also references of EP4104509A4

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023028831A1 (en) * 2021-08-31 2023-03-09 Nec Corporation Methods, devices, and computer readable medium for communication

Also Published As

Publication number Publication date
CA3171389A1 (en) 2021-06-10
EP4104509A4 (en) 2023-04-12
EP4104509A1 (en) 2022-12-21
JP7651587B2 (ja) 2025-03-26
CN115280842A (zh) 2022-11-01
KR20220162696A (ko) 2022-12-08
JP2023507680A (ja) 2023-02-24
US20230007544A1 (en) 2023-01-05

Similar Documents

Publication Publication Date Title
US12610291B2 (en) Methods and devices for updating IAB-node configuration information during inter-donor migration
US12425936B2 (en) Methods and devices for enhancing mobility robustness to integrated access and backhaul for new radio
US12089070B2 (en) Methods and devices for updating configuration information of downstream devices during inter-donor migration
US20230199879A1 (en) Methods and devices for enhancing integrated access backhaul networks for new radio
US12520213B2 (en) Methods and devices for enhancing integrated access backhaul networks for new radio
AU2022470393B2 (en) Method, device, and system for congestion control in wireless networks
US20230007544A1 (en) Methods and devices for updating data transmission during inter-donor migration
WO2022151017A1 (en) Methods and devices for configuring integrated access and backhaul nodes during inter-donor migration
CN115280842B (zh) 用于在施主间迁移期间更新数据传输的方法和设备
EP4537582A1 (en) Methods, devices, and systems for supporting l1/l2 based inter-cell mobility
CA3162217C (en) Methods and devices for updating iab-node configuration information during inter-donor migration
WO2025166596A1 (en) Methods and devices for data service management in wireless communication system
US12396001B2 (en) Methods and devices for data transmission based on switching quality of service flow
WO2025166575A1 (en) Methods and devices for managing data service session in wireless system
US20240349140A1 (en) Methods, devices, and systems for modifying candidate cells for l1/l2 based inter-cell mobility
WO2025147826A1 (en) Methods, devices, and systems for supporting pdu set based handling
WO2025179559A1 (en) Methods and devices for transferring data service control data in wireless communication system
WO2026081063A1 (en) Methods, devices, and systems for unmanned aerial vehicle information reporting and authorization

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20895932

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2022554826

Country of ref document: JP

Kind code of ref document: A

Ref document number: 3171389

Country of ref document: CA

WWE Wipo information: entry into national phase

Ref document number: 202217052268

Country of ref document: IN

ENP Entry into the national phase

Ref document number: 2020895932

Country of ref document: EP

Effective date: 20220913

NENP Non-entry into the national phase

Ref country code: DE

WWG Wipo information: grant in national office

Ref document number: 202217052268

Country of ref document: IN