Prosecution Insights
Last updated: October 02, 2026
Application No. 18/563,833

FLOW CONTROL FEEDBACK IN AN INTEGRATED ACCESS AND BACKHAUL NETWORK

Non-Final OA §103
Filed
Nov 22, 2023
Priority
May 27, 2021 — GB 2107610.4 +1 more
Examiner
LIN, WILL W
Art Unit
2412
Tech Center
2400 — Computer Networks
Assignee
Canon Inc.
OA Round
2 (Non-Final)
94%
Grant Probability
Favorable
2-3
OA Rounds
0m
Est. Remaining
99%
With Interview

Examiner Intelligence

Grants 94% — above average
94%
Career Allowance Rate
476 granted / 509 resolved
+35.5% vs TC avg
Moderate +6% lift
Without
With
+5.8%
Interview Lift
resolved cases with interview
Fast prosecutor
2y 1m
Avg Prosecution
20 currently pending
Career history
536
Total Applications
across all art units

Statute-Specific Performance

§101
5.7%
-34.3% vs TC avg
§103
59.9%
+19.9% vs TC avg
§102
3.5%
-36.5% vs TC avg
§112
18.8%
-21.2% vs TC avg
Black line = Tech Center average estimate • Based on career data from 509 resolved cases

Office Action

§103
Notice of Pre-AIA or AIA Status The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA . DETAILED ACTION This office action is in response to the amendments filed on 06/10/2026. Claims 1-14, 17-26, 29-30, 32-35 and 37-47 are currently pending. Claims 1-11, 17-23, 29-30, 32-35 and 37-47 are rejected. Claims 12-14 and 24-26 are objected to. Claims 1, 34-35 and 37 are independent claims. Response to Amendment Claim Rejections - 35 USC § 103 6. In the event the determination of the status of the application as subject to AIA 35 U.S.C. 102 and 103 (or as subject to pre-AIA 35 U.S.C. 102 and 103) is incorrect, any correction of the statutory basis for the rejection will not be considered a new ground of rejection if the prior art relied upon, and the rationale supporting the rejection, would be the same under either status. 7. The following is a quotation of 35 U.S.C. 103 which forms the basis for all obviousness rejections set forth in this Office action: A patent for a claimed invention may not be obtained, notwithstanding that the claimed invention is not identically disclosed as set forth in section 102 of this title, if the differences between the claimed invention and the prior art are such that the claimed invention as a whole would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which the claimed invention pertains. Patentability shall not be negated by the manner in which the invention was made. 8. The factual inquiries set forth in Graham v. John Deere Co., 383 U.S. 1, 148 USPQ 459 (1966), that are applied for establishing a background for determining obviousness under pre-AIA 35 U.S.C. 103(a) are summarized as follows: 1. Determining the scope and contents of the prior art. 2. Ascertaining the differences between the prior art and the claims at issue. 3. Resolving the level of ordinary skill in the pertinent art. 4. Considering objective evidence present in the application indicating obviousness or nonobviousness. 9. Claims 1-11, 17-23, 29-30, 32-35 and 37-47 are rejected under 35 U.S.C. 103 as being unpatentable over Sung-pyo HONG (US 2021/0127293 A1) hereinafter HONG. For claim 1, HONG teaches a method for processing a flow control feedback in an Integrated Access and Backhaul, IAB, network comprising a plurality of IAB nodes, each IAB node of the plurality of IAB nodes configured to deliver data received over an ingress link to an egress link for transmission, the method, at an IAB node [0009] a method of an integrated access and backhaul (IAB) node;monitoring an uplink buffer status or a downlink buffer status in the IABnode, and transmitting uplink buffer status information or downlink bufferstatus information to the donor base station or an associated parent IABnode based on the result of the monitoring for the uplink buffer status or the downlink buffer status and figures 8-15), comprising: receiving, from another IAB node over an egress backhaul link between the IAB node and the another IAB node, a flow control feedback comprising link identification information (paragraphs [0155]-[0163]; [0279]-[0285] IAB node [i.e., another IAB node] performs a step of transmitting downlink buffer status information or uplink buffer status information to the donor base station or an associated parent IAB node [i.e., receiving from another IAB node over an egress backhaul link a flow control information] based on a result of the monitoring for the uplink buffer status or the downlink buffer status; uplink buffer status information or downlink buffer status information may include at least one of buffer size information, IAB node identifier information, backhaul RLC channel identifier information [i.e., flow control feedback comprising link identification information]; buffer size may be calculated by adding one or more buffer size(s) included in Buffer Status Report (BSR) received from a child IAB node; buffer size may be calculated by adding one or more buffer size(s) included in BSR received from a child IAB node within n hop(s) (n=0 or a positive integer) [i.e., updating information included in the flow control feedback for at least one of the determined at least one ingress backhaul link]; IAB node may transmit the uplink buffer status information to an associated parent IAB node by including the uplink buffer status information in a MAC control element (MAC CE) or a backhaul adaptation protocol (BAP) control PDU and figures 8-15); determining at least one ingress backhaul link for use in forwarding the flow control feedback (paragraphs [0279]-[0285] one or more buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; IAB node may transmit the uplink buffer status information to an associated parent IAB node by including the uplink buffer status information in a MAC control element (MAC CE) or a backhaul adaptation protocol (BAP) control PDU and figures 8-15); updating information included in the flow control feedback for at least one of the determined at least one ingress backhaul link to provide an updated flow control feedback for the at least one of the determined at least one ingress backhaul link (paragraphs [0279]-[0285] buffer size may be calculated by adding one or more buffer size(s) included in Buffer Status Report (BSR) received from a child IAB node; buffer size may be calculated by adding one or more buffer size(s) included in BSR received from a child IAB node within n hop(s) (n=0 or a positive integer) [i.e., updating information included in the flow control feedback for at least one of the determined at least one ingress backhaul link] and figures 8-15), wherein updating information included in the flow control feedback includes updating the link identification information included in the flow control feedback (paragraphs [0158], [0329] the uplink buffer status information or downlink buffer status information may include at least one of buffer size information, IAB node identifier information, backhaul RLC channel identifier information, UE bearer identifier information and logical channel group identifier information. It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the method to have wherein updating information included in the flow control feedback includes updating the link identification information included in the flow control feedback because it is a normal design procedure for the skilled person in the art.). transmitting the updated flow control feedback over the at least one of the determined at least one ingress backhaul link (paragraphs [0279]-[0285] buffer size may be calculated by adding one or more buffer size(s) included in Buffer Status Report (BSR) received from a child IAB node; buffer size may be calculated by adding one or more buffer size(s) included in BSR received from a child IAB node within n hop(s) (n=0 or a positive integer); status information described above may be delivered to a directly- connected parent IAB node and figures 8-15). For claim 2, HONG further teaches the method of claim 1, wherein determining at least one ingress backhaul link comprises determining, based on the link identification information, at least one ingress backhaul link for use in forwarding the flow control feedback (paragraphs [0104]; [0155]-[0163]; [0279]-[0285]; [0327]-[0328] uplink buffer status information or downlink buffer status information may include at least one of buffer size information, IAB node identifier information, backhaul RLC channel identifier information; backhaul RLC channel identifier information may mean information for identifying a backhaul RLC channel associated with a corresponding IAB node; a relay node selects a backhaul RLC channel for transmitting the uplink user data based on at least one of the UE bearer identifier and donor base station address information; buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; buffer size may be calculated by adding one or more buffer size(s) included in BSR received from a child IAB node within n hop(s) (n=0 or a positive integer); buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; periodic reporting, congestion/buffer status reporting of an IAB node according to a specific condition, or periodic congestion/buffer status reporting of the IAB node based on a specific condition maybe performed; donor base station is able to effectively perform topology adjustment and radio resource control by a radio bearer establishment/revision/modification/change; buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; IAB node may transmit the uplink buffer status information to an associated parent IAB node by including the uplink buffer status information in a MAC control element (MAC CE) or a backhaul adaptation protocol (BAP) control PDU and figures 8-15). For claim 3, HONG further teaches the method of claim 1 wherein the link identification information includes a backhaul RLC channel identifier for identifying a backhaul RLC channel of the egress backhaul link (paragraphs [0104]; [0155]-[0163]; [0279]-[0285]; [0327]-[0328] uplink buffer status information or downlink buffer status information may include at least one of buffer size information, IAB node identifier information, backhaul RLC channel identifier information; backhaul RLC channel identifier information may mean information for identifying a backhaul RLC channel associated with a corresponding IAB node; a relay node selects a backhaul RLC channel for transmitting the uplink user data based on at least one of the UE bearer identifier and donor base station address information; buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; buffer size may be calculated by adding one or more buffer size(s) included in BSR received from a child IAB node within n hop(s) (n=0 or a positive integer); buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; periodic reporting, congestion/buffer status reporting of an IAB node according to a specific condition, or periodic congestion/buffer status reporting of the IAB node based on a specific condition maybe performed; donor base station is able to effectively perform topology adjustment and radio resource control by a radio bearer establishment/revision/modification/change; buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; IAB node may transmit the uplink buffer status information to an associated parent IAB node by including the uplink buffer status information in a MAC control element (MAC CE) or a backhaul adaptation protocol (BAP) control PDU and figures 8-15). For claim 4, HONG further teaches the method of claim 3, wherein the IAB node is configured with backhaul RLC channel mapping configuration information for mapping backhaul RLC channel identifiers from egress to ingress backhaul links, wherein determining at least one ingress backhaul link comprises determining, based on the backhaul RLC channel identifier for the egress backhaul link and the backhaul RLC channel mapping configuration information, the at least one ingress backhaul link(paragraphs [0104]; [0155]-[0163]; [0279]-[0285]; [0327]-[0328] uplink buffer status information or downlink buffer status information may include at least one of buffer size information, IAB node identifier information, backhaul RLC channel identifier information; backhaul RLC channel identifier information may mean information for identifying a backhaul RLC channel associated with a corresponding IAB node; a relay node selects a backhaul RLC channel for transmitting the uplink user data based on at least one of the UE bearer identifier and donor base station address information; buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; buffer size may be calculated by adding one or more buffer size(s) included in BSR received from a child IAB node within n hop(s) (n=0 or a positive integer); buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; periodic reporting, congestion/buffer status reporting of an IAB node according to a specific condition, or periodic congestion/buffer status reporting of the IAB node based on a specific condition maybe performed; donor base station is able to effectively perform topology adjustment and radio resource control by a radio bearer establishment/revision/modification/change; buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; IAB node may transmit the uplink buffer status information to an associated parent IAB node by including the uplink buffer status information in a MAC control element (MAC CE) or a backhaul adaptation protocol (BAP) control PDU and figures 8-15). For claim 5, HONG further teaches the method of claim 4, further comprising: for at least one of the determined at least one ingress backhaul link, determining a backhaul RLC channel identifier for a backhaul RLC channel of the ingress backhaul link associated with the backhaul RLC channel identifier for the egress backhaul link using the backhaul RLC channel mapping configuration information, wherein updating information included in the flow control feedback for the at least one of the determined at least one ingress backhaul link comprises: updating the link identification information of the flow control feedback to replace the backhaul RLC channel identifier for identifying a backhaul RLC channel of the egress backhaul link in the flow control feedback with the backhaul RLC channel identifier for the backhaul RLC channel of the ingress backhaul link to provide the updated flow control feedback for transmission over the ingress backhaul link (paragraphs [0104]; [0155]-[0163]; [0279]-[0285]; [0327]- [0328] uplink buffer status information or downlink buffer status information may include at least one of buffer size information, IAB node identifier information, backhaul RLC channel identifier information; backhaul RLC channel identifier information may mean information for identifying a backhaul RLC channel associated with a corresponding IAB node; a relay node selects a backhaul RLC channel for transmitting the uplink user data based on at least one of the UE bearer identifier and donor base station address information; buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; buffer size may be calculated by adding one or more buffer size(s) included in BSR received from a child IAB node within n hop(s) (n=0 or a positive integer); buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; periodic reporting, congestion/buffer status reporting of an IAB node according to a specific condition, or periodic congestion/buffer status reporting of the IAB node based on a specific condition maybe performed; donor base station is able to effectively perform topology adjustment and radio resource control by a radio bearer establishment/revision/modification/change; buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; IAB node may transmit the uplink buffer status information to an associated parent IAB node by including the uplink buffer status information in a MAC control element (MAC CE) or a backhaul adaptation protocol (BAP) control PDU and figures 8-15). For claim 6, HONG further teaches the method of claim 4, further comprising: for at least one of the determined at least one ingress backhaul link, determining, at least one additional backhaul RLC channel of the ingress backhaul link not associated with the backhaul RLC channel of the egress backhaul link using the backhaul RLC channel mapping configuration information; for each of the at least one additional backhaul RLC channel, determining the backhaul RLC channel identifier of the additional backhaul RLC channel and status information for the additional backhaul RLC channel, wherein updating information included in the flow control feedback for the at least one of the determined at least one ingress backhaul link comprises: updating the flow control feedback to include the backhaul RLC channel identifier and status information for the at least one additional backhaul RLC channel (paragraphs [0104]; [0155]-[0163]; [0279]-[0285]; [0327]-[0328] uplink buffer status information or downlink buffer status information may include at least one of buffer size information, IAB node identifier information, backhaul RLC channel identifier information; backhaul RLC channel identifier information may mean information for identifying a backhaul RLC channel associated with a corresponding IAB node; a relay node selects a backhaul RLC channel for transmitting the uplink user data based on at least one of the UE bearer identifier and donor base station address information; buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; buffer size may be calculated by adding one or more buffer size(s) included in BSR received from a child IAB node within n hop(s) (n=0 or a positive integer); buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; periodic reporting, congestion/buffer status reporting of an IAB node according to a specific condition, or periodic congestion/buffer status reporting of the IAB node based on a specific condition maybe performed; donor base station is able to effectively perform topology adjustment and radio resource control by a radio bearer establishment/revision/modification/change; buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; IAB node may transmit the uplink buffer status information to an associated parent IAB node by including the uplink buffer status information in a MAC control element (MAC CE) or a backhaul adaptation protocol (BAP) control PDU and figures 8-15). For claim 7, HONG further teaches the method of claim 3, wherein the link identification information includes a first backhaul RLC channel identifier for a first backhaul RLC channel of the egress backhaul link and a second backhaul RLC channel identifier for a second backhaul RLC channel of the egress backhaul link and wherein the flow control feedback further comprises first status information for the first backhaul RLC channel and second status information for the second backhaul RLC channel, wherein determining at least one ingress backhaul link comprises determining, based on the first backhaul RLC channel identifier, a first ingress backhaul link and determining, based on the second backhaul RLC channel identifier, a second ingress backhaul link, wherein updating information included in the flow control feedback for at least one of the determined at least one ingress backhaul link comprises: updating information included in the flow control feedback for the first ingress backhaul link by removing the second backhaul RLC channel identifier and second status information for the second backhaul RLC channel to provide a first updated flow control feedback for the first ingress backhaul link, wherein transmitting the updated flow control feedback comprises transmitting the first updated flow control feedback over the first ingress backhaul link(paragraphs [0104]; [0155]-[0163]; [0279]-[0285]; [0327]-0328] uplink buffer status information or downlink buffer status information may include at least one of buffer size information, IAB node identifier information, backhaul RLC channel identifier information; backhaul RLC channel identifier information may mean information for identifying a backhaul RLC channel associated with a corresponding IAB node; a relay node selects a backhaul RLC channel for transmitting the uplink user data based on at least one of the UE bearer identifier and donor base station address information; buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; buffer size may be calculated by adding one or more buffer size(s) included in BSR received from a child IAB node within n hop(s) (n=0 or a positive integer); buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; periodic reporting, congestion/buffer status reporting of an IAB node according to a specific condition, or periodic congestion/buffer status reporting of the IAB node based on a specific condition maybe performed; donor base station is able to effectively perform topology adjustment and radio resource control by a radio bearer establishment/revision/modification/change; buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; IAB node may transmit the uplink buffer status information to an associated parent IAB node by including the uplink buffer status information in a MAC control element (MAC CE) or a backhaul adaptation protocol (BAP) control PDU and figures 8-15). For claim 8, HONG further teaches the method of claim 7, wherein updating information included in the flow control feedback for at least one of the determined at least one ingress backhaul link further comprises: updating information included in the flow control feedback for the second ingress backhaul link by removing the first backhaul RLC channel identifier and first status information for the first backhaul RLC channel to provide a second updated flow control feedback for the second ingress backhaul link; wherein transmitting the updated flow control feedback comprises transmitting the second updated flow control feedback over the second ingress backhaul link (paragraphs [0104]; [0155]-[0163]; [0279]-[0285]; [0327]-[0328] uplink buffer status information or downlink buffer status information may include at least one of buffer size information, IAB node identifier information, backhaul RLC channel identifier information; backhaul RLC channel identifier information may mean information for identifying a backhaul RLC channel associated with a corresponding IAB node; a relay node selects a backhaul RLC channel for transmitting the uplink user data based on at least one of the UE bearer identifier and donor base station address information; buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; buffer size may be calculated by adding one or more buffer size(s) included in BSR received from a child IAB node within n hop(s) (n=0 or a positive integer); buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; periodic reporting, congestion/buffer status reporting of an IAB node according to a specific condition, or periodic congestion/buffer status reporting of the IAB node based on a specific condition maybe performed; donor base station is able to effectively perform topology adjustment and radio resource control by a radio bearer establishment/revision/modification/change; buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; IAB node may transmit the uplink buffer status information to an associated parent IAB node by including the uplink buffer status information in a MAC control element (MAC CE) or a backhaul adaptation protocol (BAP) control PDU and figures 8-15). For claim 9, HONG further teaches the method of claim 3, wherein the IAB node is configured with a backhaul RLC channel mapping configuration table including at least one entry, each entry having a next hop address field for a next hop address of an IAB node that is next to the IAB node in a routing path for data, a prior hop address field for a prior hop address of a prior hop IAB node that is prior to the IAB node in the routing path for data, an ingress backhaul RLC channel identifier field for the backhaul RLC channel identifier of a backhaul RLC channel of an ingress backhaul link between the IAB node and the prior hop IAB node and an egress backhaul RLC channel identifier field for a backhaul RLC channel identifier of a backhaul RLC channel for an egress backhaul link between the IAB node and the next hop IAB node, wherein determining at least one ingress backhaul link comprises: identifying a backhaul RLC channel identifier in the flow control feedback; checking each entry in the backhaul RLC channel mapping configuration table to determine whether the identified backhaul RLC channel identifier in the flow control feedback matches an egress backhaul RLC channel identifier in the egress backhaul RLC channel identifier field of an entry and whether an address of the another IAB node matches a next hop address in the next hop address field of the entry; when the identified backhaul RLC channel identifier in the flow control feedback matches the egress backhaul RLC channel identifier in the egress backhaul RLC channel identifier field of an entry and the address of the another IAB node matches the next hop address in the next hop address field of the entry, identifying a matched entry; for each matched entry, using the prior hop address in the prior hop address field of the matched entry to identify an IAB node as a prior hop IAB node having the prior hop address and determining a backhaul link between the prior hop IAB node and the IAB node as an ingress backhaul link for use in forwarding the flow control feedback (paragraphs [0104]; [0155]-[0163]; [0279]-[0285]; [0327]-[0328] uplink buffer status information or downlink buffer status information may include at least one of buffer size information, IAB node identifier information, backhaul RLC channel identifier information; backhaul RLC channel identifier information may mean information for identifying a backhaul RLC channel associated with a corresponding IAB node; a relay node selects a backhaul RLC channel for transmitting the uplink user data based on at least one of the UE bearer identifier and donor base station address information; buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; buffer size may be calculated by adding one or more buffer size(s) included in BSR received from a child IAB node within n hop(s) (n=0 or a positive integer); buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; periodic reporting, congestion/buffer status reporting of an IAB node according to a specific condition, or periodic congestion/buffer status reporting of the IAB node based on a specific condition maybe performed; donor base station is able to effectively perform topology adjustment and radio resource control by a radio bearer establishment/revision/modification/change; buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; IAB node may transmit the uplink buffer status information to an associated parent IAB node by including the uplink buffer status information in a MAC control element (MAC CE) or a backhaul adaptation protocol (BAP) control PDU and figures 8-15). For claim 10, HONG further teaches the method of claim 9, further comprising: checking each entry in the backhaul RLC channel mapping configuration table to determine whether the identified backhaul RLC channel identifier in the flow control feedback matches an egress backhaul RLC channel identifier in the egress backhaul RLC channel identifier field of an entry, whether an address of the another IAB node matches a next hop address in the next hop address field of the entry and whether the determined ingress backhaul link is associated with an IAB node having an address that matches a prior hop address in the prior hop address field of the entry; when the identified backhaul RLC channel identifier in the flow control feedback matches the egress backhaul RLC channel identifier in the egress backhaul RLC channel identifier field of an entry, the address of the another IAB node matches the next hop address in the next hop address field of the entry, and the determined ingress backhaul link is associated with an IAB node having an address that matches a prior hop address in the prior hop address field of the entry, identifying a matched entry; for the matched entry, identifying the backhaul RLC channel identifier in the ingress backhaul RLC channel identifier field of the matched entry as the backhaul RLC channel identifier for the determined ingress backhaul link, wherein updating the link identification information comprises: updating the link identification information of the flow control feedback to include the identified backhaul RLC channel identifier for the determined ingress backhaul link to provide the updated flow control feedback for transmission over the determined ingress backhaul link (paragraphs [0104]; [0155]-[0163]; [0279]-[0285]; [0327]-[0328] uplink buffer status information or downlink buffer status information may include at least one of buffer size information, IAB node identifier information, backhaul RLC channel identifier information; backhaul RLC channel identifier information may mean information for identifying a backhaul RLC channel associated with a corresponding IAB node; a relay node selects a backhaul RLC channel for transmitting the uplink user data based on at least one of the UE bearer identifier and donor base station address information; buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; buffer size may be calculated by adding one or more buffer size(s) included in BSR received from a child IAB node within n hop(s) (n=0 or a positive integer); buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; periodic reporting, congestion/buffer status reporting of an IAB node according to a specific condition, or periodic congestion/buffer status reporting of the IAB node based on a specific condition maybe performed; donor base station is able to effectively perform topology adjustment and radio resource control by a radio bearer establishment/revision/modification/change; buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; IAB node may transmit the uplink buffer status information to an associated parent IAB node by including the uplink buffer status information in a MAC control element (MAC CE) or a backhaul adaptation protocol (BAP) control PDU and figures 8-15). For claim 11, HONG further teaches the method of claim 10, wherein updating the link identification information comprises replacing the backhaul RLC channel identifier for the egress backhaul link with the identified backhaul RLC channel identifier for the ingress backhaul link (paragraphs [0104]; [0155]-[0163]; [0279]-[0285]; [0327]-[0328] uplink buffer status information or downlink buffer status information may include at least one of buffer size information, IAB node identifier information, backhaul RLC channel identifier information; backhaul RLC channel identifier information may mean information for identifying a backhaul RLC channel associated with a corresponding IAB node; a relay node selects a backhaul RLC channel for transmitting the uplink user data based on at least one of the UE bearer identifier and donor base station address information; buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; buffer size may be calculated by adding one or more buffer size(s) included in BSR received from a child IAB node within n hop(s) (n=0 or a positive integer); buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; periodic reporting, congestion/buffer status reporting of an IAB node according to a specific condition, or periodic congestion/buffer status reporting of the IAB node based on a specific condition maybe performed; donor base station is able to effectively perform topology adjustment and radio resource control by a radio bearer establishment/revision/modification/change; buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; IAB node may transmit the uplink buffer status information to an associated parent IAB node by including the uplink buffer status information in a MAC control element (MAC CE) or a backhaul adaptation protocol (BAP) control PDU and figures 8-15). For claim 17, HONG further teaches the method of claim 1, wherein the link identification information includes a routing identifier for identifying a routing path for routing data in the IAB network to a destination IAB node (paragraphs [0156]-[0157]; [0327]-[0328] IAB node may transmit the uplink buffer status information to an associated parent IAB node by including the uplink buffer status information in a MAC control element (MAC CE) or a backhaul adaptation protocol (BAP) control PDU; uplink buffer status information may be included in a MAC control element (MAC CE) or a backhaul adaptation protocol (BAP) control PDU; IAB node 1600 may deliver the uplink buffer status information to a child IAB node configured in a lower level; uplink buffer status information may be included in a MAC control element (MAC CE) or a backhaul adaptation protocol (BAP) control PDU and figures 8-15). For claim 18, HONG further teaches the method of claim 17, further comprising providing mapping information for mapping at least one routing identifier to at least one ingress backhaul link, wherein determining at least one ingress backhaul link comprises determining, based on the routing identifier and the mapping information, the at least one ingress backhaul link (paragraphs [0156]-[0157]; [0327]-[0328] IAB node may transmit the uplink buffer status information to an associated parent IAB node by including the uplink buffer status information in a MAC control element (MAC CE) or a backhaul adaptation protocol (BAP) control PDU; uplink buffer status information may be included in a MAC control element (MAC CE) or a backhaul adaptation protocol (BAP) control PDU; IAB node 1600 may deliver the uplink buffer status information to a child IAB node configured in a lower level; uplink buffer status information may be included in a MAC control element (MAC CE) or a backhaul adaptation protocol (BAP) control PDU and figures 8-15). For claim 19, HONG further teaches the method of claim 17, wherein the routing identifier is a Backhaul Adaptation Protocol, BAP, routing identifier including a path identifier for identifying a routing path for routing data in the IAB network to a destination IAB node, and an address of the destination IAB node (paragraphs [0156]-[0157]; [0327]-[0328] IAB node may transmit the uplink buffer status information to an associated parent IAB node by including the uplink buffer status information in a MAC control element (MAC CE) or a backhaul adaptation protocol (BAP) control PDU; uplink buffer status information may be included in a MAC control element (MAC CE) or a backhaul adaptation protocol (BAP) control PDU; IAB node 1600 may deliver the uplink buffer status information to a child IAB node configured in a lower level; uplink buffer status information may be included in a MAC control element (MAC CE) or a backhaul adaptation protocol (BAP) control PDU and figures 8-15). For claim 20, HONG further teaches the method of claim 17, wherein the link identification information includes a first routing identifier for a first routing path and a second routing identifier for a second routing path and wherein the flow control feedback further comprises first status information associated with the first routing identifier and second status information associated with the second routing identifier, wherein determining at least one ingress backhaul link comprises determining, based on the first routing identifier, a first ingress backhaul link and determining, based on the second routing identifier, a second ingress backhaul link, wherein updating information included in the flow control feedback for at least one of the determined at least one ingress backhaul link comprises: updating information included in the flow control feedback for the first ingress backhaul link by removing the second routing identifier and second status information to provide a first updated flow control feedback for the first ingress backhaul link, wherein transmitting the updated flow control feedback comprises transmitting the first updated flow control feedback over the first ingress backhaul link (paragraphs [0104]; [0155]-[0163]; [0279]-[0285]; [0327]-0328] uplink buffer status information or downlink buffer status information may include at least one of buffer size information, IAB node identifier information, backhaul RLC channel identifier information; backhaul RLC channel identifier information may mean information for identifying a backhaul RLC channel associated with a corresponding IAB node; a relay node selects a backhaul RLC channel for transmitting the uplink user data based on at least one of the UE bearer identifier and donor base station address information; buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; buffer size may be calculated by adding one or more buffer size(s) included in BSR received from a child IAB node within n hop(s) (n=0 or a positive integer); buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; periodic reporting, congestion/buffer status reporting of an IAB node according to a specific condition, or periodic congestion/buffer status reporting of the IAB node based on a specific condition maybe performed; donor base station is able to effectively perform topology adjustment and radio resource control by a radio bearer establishment/revision/modification/change; buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; IAB node may transmit the uplink buffer status information to an associated parent IAB node by including the uplink buffer status information in a MAC control element (MAC CE) or a backhaul adaptation protocol (BAP) control PDU and figures 8-15). For claim 21, HONG further teaches the method of claim 20, wherein updating information included in the flow control feedback for at least one of the determined at least one ingress backhaul link further comprises: updating information included in the flow control feedback for the second ingress backhaul link by removing the first routing identifier and first status information to provide a second updated flow control feedback for the second ingress backhaul link; wherein transmitting the updated flow control feedback comprises transmitting the second updated flow control feedback over the second ingress backhaul link (paragraphs [0104]; [0155]-[0163]; [0279]-[0285]; [0327]-0328] uplink buffer status information or downlink buffer status information may include at least one of buffer size information, IAB node identifier information, backhaul RLC channel identifier information; backhaul RLC channel identifier information may mean information for identifying a backhaul RLC channel associated with a corresponding IAB node; a relay node selects a backhaul RLC channel for transmitting the uplink user data based on at least one of the UE bearer identifier and donor base station address information; buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; buffer size may be calculated by adding one or more buffer size(s) included in BSR received from a child IAB node within n hop(s) (n=0 or a positive integer); buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; periodic reporting, congestion/buffer status reporting of an IAB node according to a specific condition, or periodic congestion/buffer status reporting of the IAB node based on a specific condition maybe performed; donor base station is able to effectively perform topology adjustment and radio resource control by a radio bearer establishment/revision/modification/change; buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; IAB node may transmit the uplink buffer status information to an associated parent IAB node by including the uplink buffer status information in a MAC control element (MAC CE) or a backhaul adaptation protocol (BAP) control PDU and figures 8-15). For claim 22, HONG further teaches the method of claim 17, further comprising: for at least one of the determined at least one ingress backhaul link, determining at least one additional routing identifier for an additional routing path associated with the at least one of the determined at least one ingress backhaul link, the at least one additional routing identifier not being included in the link identification information of the received flow control feedback; for each of the at least one additional routing identifier, determining status information associated with the additional routing path, wherein updating information included in the flow control feedback for the at least one of the determined at least one ingress backhaul link comprises: updating the flow control feedback to include the at least one additional routing identifier and status information associated with the at least one additional routing path (paragraphs [0104]; [0155]-[0163]; [0279]-[0285]; [0327]-0328] uplink buffer status information or downlink buffer status information may include at least one of buffer size information, IAB node identifier information, backhaul RLC channel identifier information; backhaul RLC channel identifier information may mean information for identifying a backhaul RLC channel associated with a corresponding IAB node; a relay node selects a backhaul RLC channel for transmitting the uplink user data based on at least one of the UE bearer identifier and donor base station address information; buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; buffer size may be calculated by adding one or more buffer size(s) included in BSR received from a child IAB node within n hop(s) (n=0 or a positive integer); buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; periodic reporting, congestion/buffer status reporting of an IAB node according to a specific condition, or periodic congestion/buffer status reporting of the IAB node based on a specific condition maybe performed; donor base station is able to effectively perform topology adjustment and radio resource control by a radio bearer establishment/revision/modification/change; buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; IAB node may transmit the uplink buffer status information to an associated parent IAB node by including the uplink buffer status information in a MAC control element (MAC CE) or a backhaul adaptation protocol (BAP) control PDU and figures 8-15). For claim 23, HONG further teaches the method of claim 18, wherein the routing identifier is a Backhaul Adaptation Protocol, BAP, routing identifier including a path identifier for identifying a routing path for routing data in the IAB network to a destination IAB node, and an address of the destination IAB node, wherein the mapping information comprises a mapping table including at least one entry, each entry having a BAP routing identifier field for a BAP routing identifier and a prior hop address field for an address of an IAB node that is prior to the IAB node in the routing path identified by the BAP routing identifier, wherein determining at least one ingress backhaul link comprises: identifying a BAP routing identifier in the flow control feedback; checking each entry in the mapping table to determine whether the identified BAP routing identifier in the flow control feedback matches the BAP routing identifier in the BAP routing identifier field; when the identified BAP routing identifier in the flow control feedback matches the BAP routing identifier in the BAP routing identifier field of an entry, identifying a matched entry; for each matched entry, using the address in the prior hop address field of the entry to identify an IAB node as a prior hop IAB node and determining a backhaul link between the prior hop IAB node and the IAB node as an ingress backhaul link for use in forwarding the flow control feedback (paragraphs [0156]-[0157]; [0327]-[0328] IAB node may transmit the uplink buffer status information to an associated parent IAB node by including the uplink buffer status information in a MAC control element (MAC CE) or a backhaul adaptation protocol (BAP) control PDU; uplink buffer status information may be included in a MAC control element (MAC CE) or a backhaul adaptation protocol (BAP) control PDU; IAB node 1600 may deliver the uplink buffer status information to a child IAB node configured in a lower level; uplink buffer status information may be included in a MAC control element (MAC CE) or a backhaul adaptation protocol (BAP) control PDU and figures 8-15). For claim 29, HONG further teaches the method of claim 1, further comprising: determining the received flow control feedback is to be forwarded (paragraphs [0104]; [0155]-[0163]; [0279]-[0285]; [0327]-[0328] and figures 8-15). For claim 30, HONG further teaches the method of claim 29, wherein determining the received flow control feedback is to be forwarded comprises at least one of: determining that the received flow control feedback indicates congestion; or determining that the received flow control feedback indicates congestion and in response to determining that no corrective action for the congestion can be performed by the IAB node (paragraphs [0104]; [0155]-[0163]; [0279]-[0285]; [0327]-[0328] uplink buffer status information or downlink buffer status information may include at least one of buffer size information, IAB node identifier information, backhaul RLC channel identifier information; backhaul RLC channel identifier information may mean information for identifying a backhaul RLC channel associated with a corresponding IAB node; a relay node selects a backhaul RLC channel for transmitting the uplink user data based on at least one of the UE bearer identifier and donor base station address information; buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; buffer size may be calculated by adding one or more buffer size(s) included in BSR received from a child IAB node within n hop(s) (n=0 or a positive integer); buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; periodic reporting, congestion/buffer status reporting of an IAB node according to a specific condition, or periodic congestion/buffer status reporting of the IAB node based on a specific condition maybe performed; donor base station is able to effectively perform topology adjustment and radio resource control by a radio bearer establishment/revision/modification/change; buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; IAB node may transmit the uplink buffer status information to an associated parent IAB node by including the uplink buffer status information in a MAC control element (MAC CE) or a backhaul adaptation protocol (BAP) control PDU and figures 8-15). For claim 32, HONG further teaches the method of claim 1, wherein updating the link identification information includes replacing or removing the link identification information in the flow control feedback (paragraphs [0104]; [0155]-[0163]; [0279]-[0285]; [0327]-[0328] uplink buffer status information or downlink buffer status information may include at least one of buffer size information, IAB node identifier information, backhaul RLC channel identifier information; backhaul RLC channel identifier information may mean information for identifying a backhaul RLC channel associated with a corresponding IAB node; a relay node selects a backhaul RLC channel for transmitting the uplink user data based on at least one of the UE bearer identifier and donor base station address information; buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; buffer size may be calculated by adding one or more buffer size(s) included in BSR received from a child IAB node within n hop(s) (n=0 or a positive integer); buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; periodic reporting, congestion/buffer status reporting of an IAB node according to a specific condition, or periodic congestion/buffer status reporting of the IAB node based on a specific condition maybe performed; donor base station is able to effectively perform topology adjustment and radio resource control by a radio bearer establishment/revision/modification/change; buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; IAB node may transmit the uplink buffer status information to an associated parent IAB node by including the uplink buffer status information in a MAC control element (MAC CE) or a backhaul adaptation protocol (BAP) control PDU and figures 8-15). For claim 33, HONG further teaches the method of claim 3, wherein updating the link identification information included in the flow control feedback includes updating the link identification information of the flow control feedback by replacing the backhaul RLC channel identifier for identifying the backhaul RLC channel of the egress backhaul link in the flow control feedback with a backhaul RLC channel identifier for a backhaul RLC channel of the at least one of the determined at least one ingress backhaul link to provide the updated flow control feedback (paragraphs [0104]; [0155]-[0163]; [0279]-[0285]; [0327]-[0328] uplink buffer status information or downlink buffer status information may include at least one of buffer size information, IAB node identifier information, backhaul RLC channel identifier information; backhaul RLC channel identifier information may mean information for identifying a backhaul RLC channel associated with a corresponding IAB node; a relay node selects a backhaul RLC channel for transmitting the uplink user data based on at least one of the UE bearer identifier and donor base station address information; buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; buffer size may be calculated by adding one or more buffer size(s) included in BSR received from a child IAB node within n hop(s) (n=0 or a positive integer); buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; periodic reporting, congestion/buffer status reporting of an IAB node according to a specific condition, or periodic congestion/buffer status reporting of the IAB node based on a specific condition maybe performed; donor base station is able to effectively perform topology adjustment and radio resource control by a radio bearer establishment/revision/modification/change; buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; IAB node may transmit the uplink buffer status information to an associated parent IAB node by including the uplink buffer status information in a MAC control element (MAC CE) or a backhaul adaptation protocol (BAP) control PDU and figures 8-15). For claim 34, HONG teaches a method for processing a flow control feedback in an Integrated Access and Backhaul, IAB, network comprising a plurality of IAB nodes, each IAB node of the plurality of IAB nodes configured to deliver data received over an ingress link to an egress link for transmission node (paragraph [0009] a method of an integrated access and backhaul (IAB) node;monitoring an uplink buffer status or a downlink buffer status in the IABnode, and transmitting uplink buffer status information or downlink bufferstatus information to the donor base station or an associated parent IABnode based on the result of the monitoring for the uplink buffer status or the downlink buffer status and figures 8-15), the method, at an IAB node, comprising: receiving, from another IAB node over an egress backhaul link between the IAB node and the another IAB node, a flow control feedback comprising a Backhaul Adaptation Protocol, BAP, routing identifier including a path identifier for identifying a routing path for routing data in the IAB network to a destination IAB node, and an address of the destination IAB node (paragraphs [0009]; [0104]; [0279]-[0285]; [0327]-[0328] a method of an integrated access and backhaul (IAB) node; monitoring an uplink buffer status or a downlink buffer status in the IAB node, and transmitting uplink buffer status information or downlink buffer status information to the donor base station or an associated parent IAB node based on the result of the monitoring for the uplink buffer status or the downlink buffer status; a relay node selects a backhaul RLC channel for transmitting the uplink user data based on at least one of the UE bearer identifier and donor base station address information; IAB node may transmit the uplink buffer status information to an associated parent IAB node by including the uplink buffer status information in a MAC control element (MAC CE) or a backhaul adaptation protocol (BAP) control PDU and figures 8-15); determining, based on the BAP routing identifier, at least one ingress backhaul link for use in forwarding the flow control feedback (paragraphs [0279]-[0285]; [0327]-[0328] one or more buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; IAB node may transmit the uplink buffer status information to an associated parent IAB node by including the uplink buffer status information in a MAC control element (MAC CE) or a backhaul adaptation protocol (BAP) control PDU and figures 8-15); updating information included in the flow control feedback for the at least one of the determined at least one ingress backhaul link to provide an updated flow control feedback, wherein updating information included in the flow control feedback includes updating BAP routing identifier information included in the flow control feedback for the at least one of the determined at least one ingress backhaul link transmitting the flow control feedback over the at least one ingress backhaul link ([0279]-[0285]; [0327]-[0328] a method of an integrated access and backhaul (IAB) node; monitoring an uplink buffer status or a downlink buffer status in the IAB node, and transmitting uplink buffer status information or downlink buffer status information to the donor base station or an associated parent IAB node based on the result of the monitoring for the uplink buffer status or the downlink buffer status; a relay node selects a backhaul RLC channel for transmitting the uplink user data based on at least one of the UE bearer identifier and donor base station address information; IAB node may transmit the uplink buffer status information to an associated parent IAB node by including the uplink buffer status information in a MAC control element (MAC CE) or a backhaul adaptation protocol (BAP) control PDU and figures 8-15. It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the method to have updating information included in the flow control feedback includes updating BAP routing identifier information included in the flow control feedback for the at least one of the determined at least one ingress backhaul link transmitting the flow control feedback over the at least one ingress backhaul link because it is a normal design procedure for the skilled person in the art.); transmitting the updated flow control feedback over the at least one ingress backhaul link ([0279]-[0285]; [0327]-[0328] a method of an integrated access and backhaul (IAB) node; monitoring an uplink buffer status or a downlink buffer status in the IAB node, and transmitting uplink buffer status information or downlink buffer status information to the donor base station or an associated parent IAB node based on the result of the monitoring for the uplink buffer status or the downlink buffer status; a relay node selects a backhaul RLC channel for transmitting the uplink user data based on at least one of the UE bearer identifier and donor base station address information; IAB node may transmit the uplink buffer status information to an associated parent IAB node by including the uplink buffer status information in a MAC control element (MAC CE) or a backhaul adaptation protocol (BAP) control PDU and figures 8-15). For claim 35, HONG teaches an apparatus for an Integrated Access and Backhaul, IAB, node for an IAB network, the apparatus comprising: at least one processor (HONG, Fig. 16, item 1610) configured to: receive, from another IAB node over an egress backhaul link between the IAB node and the another IAB node, a flow control feedback comprising link identification information (paragraphs [0155]-[0163]; [0279]-[0285] IAB node [i.e., another IAB node] performs a step of transmitting downlink buffer status information or uplink buffer status information to the donor base station or an associated parent IAB node [i.e., receiving from another IAB node over an egress backhaul link a flow control information] based on a result of the monitoring for the uplink buffer status or the downlink buffer status; uplink buffer status information or downlink buffer status information may include at least one of buffer size information, IAB node identifier information, backhaul RLC channel identifier information [i.e., flow control feedback comprising link identification information]; buffer size may be calculated by adding one or more buffer size(s) included in Buffer Status Report (BSR) received from a child IAB node; buffer size may be calculated by adding one or more buffer size(s) included in BSR received from a child IAB node within n hop(s) (n=0 or a positive integer) [i.e., updating information included in the flow control feedback for at least one of the determined at least one ingress backhaul link]; IAB node may transmit the uplink buffer status information to an associated parent IAB node by including the uplink buffer status information in a MAC control element (MAC CE) or a backhaul adaptation protocol (BAP) control PDU and figures 8-15); determine at least one ingress backhaul link for use in forwarding the flow control feedback (paragraphs [0279]-[0285] one or more buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; IAB node may transmit the uplink buffer status information to an associated parent IAB node by including the uplink buffer status information in a MAC control element (MAC CE) or a backhaul adaptation protocol (BAP) control PDU and figures 8-15); updating information included in the flow control feedback for at least one of the determined at least one ingress backhaul link to provide an updated flow control feedback for the at least one of the determined at least one ingress backhaul link (paragraphs [0279]-[0285] buffer size may be calculated by adding one or more buffer size(s) included in Buffer Status Report (BSR) received from a child IAB node; buffer size may be calculated by adding one or more buffer size(s) included in BSR received from a child IAB node within n hop(s) (n=0 or a positive integer) [i.e., updating information included in the flow control feedback for at least one of the determined at least one ingress backhaul link] and figures 8-15), wherein updating information included in the flow control feedback includes updating the link identification information included in the flow control feedback (paragraphs [0158], [0329] the uplink buffer status information or downlink buffer status information may include at least one of buffer size information, IAB node identifier information, backhaul RLC channel identifier information, UE bearer identifier information and logical channel group identifier information. It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the method to have wherein updating information included in the flow control feedback includes updating the link identification information included in the flow control feedback because it is a normal design procedure for the skilled person in the art.). transmitting the updated flow control feedback over the at least one of the determined at least one ingress backhaul link (paragraphs [0279]-[0285] buffer size may be calculated by adding one or more buffer size(s) included in Buffer Status Report (BSR) received from a child IAB node; buffer size may be calculated by adding one or more buffer size(s) included in BSR received from a child IAB node within n hop(s) (n=0 or a positive integer); status information described above may be delivered to a directly- connected parent IAB node and figures 8-15). For claim 37, HONG teaches a non-transitory computer-readable storage medium carrying a computer program comprising instructions which, when the computer program is executed by at least one processor of an Integrated Access and Backhaul, IAB, node (HONG, Fig. 16, item 1610), cause the at least one processor to: receive, from another IAB node over an egress backhaul link between the IAB node and the another IAB node, a flow control feedback comprising link identification information (paragraphs [0155]-[0163]; [0279]-[0285] IAB node [i.e., another IAB node] performs a step of transmitting downlink buffer status information or uplink buffer status information to the donor base station or an associated parent IAB node [i.e., receiving from another IAB node over an egress backhaul link a flow control information] based on a result of the monitoring for the uplink buffer status or the downlink buffer status; uplink buffer status information or downlink buffer status information may include at least one of buffer size information, IAB node identifier information, backhaul RLC channel identifier information [i.e., flow control feedback comprising link identification information]; buffer size may be calculated by adding one or more buffer size(s) included in Buffer Status Report (BSR) received from a child IAB node; buffer size may be calculated by adding one or more buffer size(s) included in BSR received from a child IAB node within n hop(s) (n=0 or a positive integer) [i.e., updating information included in the flow control feedback for at least one of the determined at least one ingress backhaul link]; IAB node may transmit the uplink buffer status information to an associated parent IAB node by including the uplink buffer status information in a MAC control element (MAC CE) or a backhaul adaptation protocol (BAP) control PDU and figures 8-15); determine at least one ingress backhaul link for use in forwarding the flow control feedback (paragraphs [0279]-[0285] one or more buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; IAB node may transmit the uplink buffer status information to an associated parent IAB node by including the uplink buffer status information in a MAC control element (MAC CE) or a backhaul adaptation protocol (BAP) control PDU and figures 8-15); updating information included in the flow control feedback for at least one of the determined at least one ingress backhaul link to provide an updated flow control feedback for the at least one of the determined at least one ingress backhaul link (paragraphs [0279]-[0285] buffer size may be calculated by adding one or more buffer size(s) included in Buffer Status Report (BSR) received from a child IAB node; buffer size may be calculated by adding one or more buffer size(s) included in BSR received from a child IAB node within n hop(s) (n=0 or a positive integer) [i.e., updating information included in the flow control feedback for at least one of the determined at least one ingress backhaul link] and figures 8-15), wherein updating information included in the flow control feedback includes updating the link identification information included in the flow control feedback (paragraphs [0158], [0329] the uplink buffer status information or downlink buffer status information may include at least one of buffer size information, IAB node identifier information, backhaul RLC channel identifier information, UE bearer identifier information and logical channel group identifier information. It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the method to have wherein updating information included in the flow control feedback includes updating the link identification information included in the flow control feedback because it is a normal design procedure for the skilled person in the art.). transmitting the updated flow control feedback over the at least one of the determined at least one ingress backhaul link (paragraphs [0279]-[0285] buffer size may be calculated by adding one or more buffer size(s) included in Buffer Status Report (BSR) received from a child IAB node; buffer size may be calculated by adding one or more buffer size(s) included in BSR received from a child IAB node within n hop(s) (n=0 or a positive integer); status information described above may be delivered to a directly- connected parent IAB node and figures 8-15). For claim 38, HONG further teaches the method of claim 17, wherein updating the link identification information included in the flow control feedback includes removing one or more routing identifiers not associated with the at least one of the determined at least one ingress backhaul link (paragraphs [0104]; [0155]-[0163]; [0279]-[0285]; [0327]-[0328] uplink buffer status information or downlink buffer status information may include at least one of buffer size information, IAB node identifier information, backhaul RLC channel identifier information; backhaul RLC channel identifier information may mean information for identifying a backhaul RLC channel associated with a corresponding IAB node; a relay node selects a backhaul RLC channel for transmitting the uplink user data based on at least one of the UE bearer identifier and donor base station address information; buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; buffer size may be calculated by adding one or more buffer size(s) included in BSR received from a child IAB node within n hop(s) (n=0 or a positive integer); buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; periodic reporting, congestion/buffer status reporting of an IAB node according to a specific condition, or periodic congestion/buffer status reporting of the IAB node based on a specific condition maybe performed; donor base station is able to effectively perform topology adjustment and radio resource control by a radio bearer establishment/revision/modification/change; buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; IAB node may transmit the uplink buffer status information to an associated parent IAB node by including the uplink buffer status information in a MAC control element (MAC CE) or a backhaul adaptation protocol (BAP) control PDU and figures 8-15). For claim 39, HONG further teaches the method of claim 34, wherein updating the BAP routing identifier information includes removing one or more BAP routing identifiers not associated with the at least one of the determined at least one ingress backhaul link (paragraphs [0104]; [0155]-[0163]; [0279]-[0285]; [0327]-[0328] uplink buffer status information or downlink buffer status information may include at least one of buffer size information, IAB node identifier information, backhaul RLC channel identifier information; backhaul RLC channel identifier information may mean information for identifying a backhaul RLC channel associated with a corresponding IAB node; a relay node selects a backhaul RLC channel for transmitting the uplink user data based on at least one of the UE bearer identifier and donor base station address information; buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; buffer size may be calculated by adding one or more buffer size(s) included in BSR received from a child IAB node within n hop(s) (n=0 or a positive integer); buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; periodic reporting, congestion/buffer status reporting of an IAB node according to a specific condition, or periodic congestion/buffer status reporting of the IAB node based on a specific condition maybe performed; donor base station is able to effectively perform topology adjustment and radio resource control by a radio bearer establishment/revision/modification/change; buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; IAB node may transmit the uplink buffer status information to an associated parent IAB node by including the uplink buffer status information in a MAC control element (MAC CE) or a backhaul adaptation protocol (BAP) control PDU and figures 8-15). For claim 40, HONG further teaches the apparatus of claim 35, wherein determining at least one ingress backhaul link comprises determining, based on the link identification information, at least one ingress backhaul link for use in forwarding the flow control feedback (paragraphs [0104]; [0155]-[0163]; [0279]-[0285]; [0327]-[0328] uplink buffer status information or downlink buffer status information may include at least one of buffer size information, IAB node identifier information, backhaul RLC channel identifier information; backhaul RLC channel identifier information may mean information for identifying a backhaul RLC channel associated with a corresponding IAB node; a relay node selects a backhaul RLC channel for transmitting the uplink user data based on at least one of the UE bearer identifier and donor base station address information; buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; buffer size may be calculated by adding one or more buffer size(s) included in BSR received from a child IAB node within n hop(s) (n=0 or a positive integer); buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; periodic reporting, congestion/buffer status reporting of an IAB node according to a specific condition, or periodic congestion/buffer status reporting of the IAB node based on a specific condition maybe performed; donor base station is able to effectively perform topology adjustment and radio resource control by a radio bearer establishment/revision/modification/change; buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; IAB node may transmit the uplink buffer status information to an associated parent IAB node by including the uplink buffer status information in a MAC control element (MAC CE) or a backhaul adaptation protocol (BAP) control PDU and figures 8-15). For claim 41, HONG further teaches the apparatus of claim 35, wherein the link identification information includes a backhaul RLC channel identifier for identifying a backhaul RLC channel of the egress backhaul link (paragraphs [0104]; [0155]-[0163]; [0279]-[0285]; [0327]-[0328] uplink buffer status information or downlink buffer status information may include at least one of buffer size information, IAB node identifier information, backhaul RLC channel identifier information; backhaul RLC channel identifier information may mean information for identifying a backhaul RLC channel associated with a corresponding IAB node; a relay node selects a backhaul RLC channel for transmitting the uplink user data based on at least one of the UE bearer identifier and donor base station address information; buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; buffer size may be calculated by adding one or more buffer size(s) included in BSR received from a child IAB node within n hop(s) (n=0 or a positive integer); buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; periodic reporting, congestion/buffer status reporting of an IAB node according to a specific condition, or periodic congestion/buffer status reporting of the IAB node based on a specific condition maybe performed; donor base station is able to effectively perform topology adjustment and radio resource control by a radio bearer establishment/revision/modification/change; buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; IAB node may transmit the uplink buffer status information to an associated parent IAB node by including the uplink buffer status information in a MAC control element (MAC CE) or a backhaul adaptation protocol (BAP) control PDU and figures 8-15). For claim 42, HONG further teaches the apparatus of claim 35, wherein updating the link identification information includes replacing or removing the link identification information in the flow control feedback (paragraphs [0104]; [0155]-[0163]; [0279]-[0285]; [0327]-[0328] uplink buffer status information or downlink buffer status information may include at least one of buffer size information, IAB node identifier information, backhaul RLC channel identifier information; backhaul RLC channel identifier information may mean information for identifying a backhaul RLC channel associated with a corresponding IAB node; a relay node selects a backhaul RLC channel for transmitting the uplink user data based on at least one of the UE bearer identifier and donor base station address information; buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; buffer size may be calculated by adding one or more buffer size(s) included in BSR received from a child IAB node within n hop(s) (n=0 or a positive integer); buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; periodic reporting, congestion/buffer status reporting of an IAB node according to a specific condition, or periodic congestion/buffer status reporting of the IAB node based on a specific condition maybe performed; donor base station is able to effectively perform topology adjustment and radio resource control by a radio bearer establishment/revision/modification/change; buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; IAB node may transmit the uplink buffer status information to an associated parent IAB node by including the uplink buffer status information in a MAC control element (MAC CE) or a backhaul adaptation protocol (BAP) control PDU and figures 8-15). For claim 43, HONG further teaches the apparatus of claim 41, wherein updating the link identification information included in the flow control feedback includes updating the link identification information of the flow control feedback by replacing the backhaul RLC channel identifier for identifying the backhaul RLC channel of the egress backhaul link in the flow control feedback with a backhaul RLC channel identifier for a backhaul RLC channel of the at least one of the determined at least one ingress backhaul link to provide the updated flow control feedback (paragraphs [0104]; [0155]-[0163]; [0279]-[0285]; [0327]-[0328] uplink buffer status information or downlink buffer status information may include at least one of buffer size information, IAB node identifier information, backhaul RLC channel identifier information; backhaul RLC channel identifier information may mean information for identifying a backhaul RLC channel associated with a corresponding IAB node; a relay node selects a backhaul RLC channel for transmitting the uplink user data based on at least one of the UE bearer identifier and donor base station address information; buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; buffer size may be calculated by adding one or more buffer size(s) included in BSR received from a child IAB node within n hop(s) (n=0 or a positive integer); buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; periodic reporting, congestion/buffer status reporting of an IAB node according to a specific condition, or periodic congestion/buffer status reporting of the IAB node based on a specific condition maybe performed; donor base station is able to effectively perform topology adjustment and radio resource control by a radio bearer establishment/revision/modification/change; buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; IAB node may transmit the uplink buffer status information to an associated parent IAB node by including the uplink buffer status information in a MAC control element (MAC CE) or a backhaul adaptation protocol (BAP) control PDU and figures 8-15). For claim 44, HONG further teaches the apparatus of claim 35, wherein the link identification information includes a routing identifier for identifying a routing path for routing data in the IAB network to a destination IAB node (paragraphs [0104]; [0155]-[0163]; [0279]-[0285]; [0327]- [0328] uplink buffer status information or downlink buffer status information may include at least one of buffer size information, IAB node identifier information, backhaul RLC channel identifier information; backhaul RLC channel identifier information may mean information for identifying a backhaul RLC channel associated with a corresponding IAB node; a relay node selects a backhaul RLC channel for transmitting the uplink user data based on at least one of the UE bearer identifier and donor base station address information; buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; buffer size may be calculated by adding one or more buffer size(s) included in BSR received from a child IAB node within n hop(s) (n=0 or a positive integer); buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; periodic reporting, congestion/buffer status reporting of an IAB node according to a specific condition, or periodic congestion/buffer status reporting of the IAB node based on a specific condition maybe performed; donor base station is able to effectively perform topology adjustment and radio resource control by a radio bearer establishment/revision/modification/change; buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; IAB node may transmit the uplink buffer status information to an associated parent IAB node by including the uplink buffer status information in a MAC control element (MAC CE) or a backhaul adaptation protocol (BAP) control PDU and figures 8-15). For claim 45, HONG further teaches the apparatus of claim 44, wherein the routing identifier is a Backhaul Adaptation Protocol, BAP, routing identifier including a path identifier for identifying a routing path for routing data in the IAB network to a destination IAB node, and an address of the destination IAB node (paragraphs [0104]; [0155]-[0163]; [0279]-[0285]; [0327]-[0328] uplink buffer status information or downlink buffer status information may include at least one of buffer size information, IAB node identifier information, backhaul RLC channel identifier information; backhaul RLC channel identifier information may mean information for identifying a backhaul RLC channel associated with a corresponding IAB node; a relay node selects a backhaul RLC channel for transmitting the plink user data based on at least one of the UE bearer identifier and donor base station address information; buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; buffer size may be calculated by adding one or more buffer size(s) included in BSR received from a child IAB node within n hop(s) (n=0 or a positive integer); buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; periodic reporting, congestion/buffer status reporting of an IAB node according to a specific condition, or periodic congestion/buffer status reporting of the IAB node based on a specific condition maybe performed; donor base station is able to effectively perform topology adjustment and radio resource control by a radio bearer establishment/revision/modification/change; buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; IAB node may transmit the uplink buffer status information to an associated parent IAB node by including the uplink buffer status information in a MAC control element (MAC CE) or a backhaul adaptation protocol (BAP) control PDU and figures 8-15). For claim 46, HONG further teaches the apparatus of claim 44, wherein updating the link identification information included in the flow control feedback includes removing one or more routing identifiers not associated with the at least one of the determined at least one ingress backhaul link (paragraphs [0104]; [0155]-[0163]; [0279]-[0285]; [0327]-[0328] uplink buffer status information or downlink buffer status information may include at least one of buffer size information, IAB node identifier information, backhaul RLC channel identifier information; backhaul RLC channel identifier information may mean information for identifying a backhaul RLC channel associated with a corresponding IAB node; a relay node selects a backhaul RLC channel for transmitting the uplink user data based on at least one of the UE bearer identifier and donor base station address information; buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; buffer size may be calculated by adding one or more buffer size(s) included in BSR received from a child IAB node within n hop(s) (n=0 or a positive integer); buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; periodic reporting, congestion/buffer status reporting of an IAB node according to a specific condition, or periodic congestion/buffer status reporting of the IAB node based on a specific condition maybe performed; donor base station is able to effectively perform topology adjustment and radio resource control by a radio bearer establishment/revision/modification/change; buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; IAB node may transmit the uplink buffer status information to an associated parent IAB node by including the uplink buffer status information in a MAC control element (MAC CE) or a backhaul adaptation protocol (BAP) control PDU and figures 8-15). For claim 47, HONG further teaches the method of claim 1, wherein determining at least one ingress backhaul link comprises determining, based on the link identification information, at least one ingress backhaul link for use in forwarding the flow control feedback (paragraphs [0104]; [0155]-[0163]; [0279]-[0285]; [0327]-[0328] uplink buffer status information or downlink buffer status information may include at least one of buffer size information, IAB node identifier information, backhaul RLC channel identifier information; backhaul RLC channel identifier information may mean information for identifying a backhaul RLC channel associated with a corresponding IAB node; a relay node selects a backhaul RLC channel for transmitting the uplink user data based on at least one of the UE bearer identifier and donor base station address information; buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; buffer size may be calculated by adding one or more buffer size(s) included in BSR received from a child IAB node within n hop(s) (n=0 or a positive integer); buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; periodic reporting, congestion/buffer status reporting of an IAB node according to a specific condition, or periodic congestion/buffer status reporting of the IAB node based on a specific condition maybe performed; donor base station is able to effectively perform topology adjustment and radio resource control by a radio bearer establishment/revision/modification/change; buffer size(s) may be added through mapping information between a backhaul RLC channel of the child IAB node and a backhaul RLC channel of a parent IAB node; IAB node may transmit the uplink buffer status information to an associated parent IAB node by including the uplink buffer status information in a MAC control element (MAC CE) or a backhaul adaptation protocol (BAP) control PDU and figures 8-15). Allowable Subject Matter 10. Claims 12-14 and 24-26 are objected to are objected to as being dependent upon a rejected base claim but would be allowable if rewritten in independent form including all of the limitations of the base claim and any intervening claims. Response to Arguments 11. Applicant's arguments filed 06/10/2026 have been fully considered but they are moot because of the new ground of rejection. Conclusion 12. Any inquiry concerning this communication or earlier communications from the examiner should be directed to WILL W LIN whose telephone number is (571)272-8749. The examiner can normally be reached M-F 8:00-5:00. Examiner interviews are available via telephone, in-person, and video conferencing using a USPTO supplied web-based collaboration tool. To schedule an interview, applicant is encouraged to use the USPTO Automated Interview Request (AIR) at http://www.uspto.gov/interviewpractice. If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Charles Jiang can be reached at 571-270-7191. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300. Information regarding the status of published or unpublished applications may be obtained from Patent Center. Unpublished application information in Patent Center is available to registered users. To file and manage patent submissions in Patent Center, visit: https://patentcenter.uspto.gov. Visit https://www.uspto.gov/patents/apply/patent-center for more information about Patent Center and https://www.uspto.gov/patents/docx for information about filing in DOCX format. For additional questions, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000. /WILL W LIN/Primary Examiner, Art Unit 2412
Read full office action

Prosecution Timeline

Nov 22, 2023
Application Filed
Feb 11, 2026
Non-Final Rejection mailed — §103
Jun 10, 2026
Response Filed
Sep 16, 2026
Non-Final Rejection mailed — §103 (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12745307
SESSION ESTABLISHMENT IN A WIRELESS NETWORK IN VIEW OF INTERFACE FAILURE
2y 9m to grant Granted Sep 22, 2026
Patent 12720641
Small Data Transmission
3y 6m to grant Granted Aug 25, 2026
Patent 12720429
METHOD AND APPARATUS FOR DETERMINING A TIME WINDOW, AND CHIP
2y 8m to grant Granted Aug 25, 2026
Patent 12689108
MULTIPLEXER, AND SPECTRUM ANALYZER, SIGNAL ANALYZER, AND SIGNAL GENERATION DEVICE USING SAME, AND MULTIPLEXER CONTROL METHOD
2y 3m to grant Granted Jul 21, 2026
Patent 12672199
METHOD AND DEVICE IN NODES USED FOR WIRELESS COMMUNICATION
2y 10m to grant Granted Jun 30, 2026
Study what changed to get past this examiner. Based on 5 most recent grants.

Strategy Recommendation AI-generated — please review before filing

Get a prosecution strategy drawn from examiner precedents, rejection analysis, and claim mapping.
Typically takes 5-10 seconds — AI-generated, attorney review required before filing

Prosecution Projections

2-3
Expected OA Rounds
94%
Grant Probability
99%
With Interview (+5.8%)
2y 1m (~0m remaining)
Median Time to Grant
Moderate
PTA Risk
Based on 509 resolved cases by this examiner. Grant probability derived from career allowance rate.

Sign in with your work email

Enter your email to receive a magic link. No password needed.

Personal email addresses (Gmail, Yahoo, etc.) are not accepted.

Free tier: 3 strategy analyses per month