Prosecution Insights
Last updated: May 29, 2026
Application No. 18/220,345

INTEGRATED ACCESS AND BACKHAUL COMMUNICATION METHOD AND APPARATUS

Non-Final OA §102
Filed
Jul 11, 2023
Priority
Jan 13, 2021 — continuation of PCTCN2021071577
Examiner
DONADO, FRANK E
Art Unit
2641
Tech Center
2600 — Communications
Assignee
1Finity Inc.
OA Round
3 (Non-Final)
69%
Grant Probability
Favorable
3-4
OA Rounds
2m
Est. Remaining
99%
With Interview

Examiner Intelligence

Grants 69% — above average
69%
Career Allowance Rate
363 granted / 523 resolved
+7.4% vs TC avg
Strong +59% interview lift
Without
With
+59.3%
Interview Lift
resolved cases with interview
Typical timeline
3y 0m
Avg Prosecution
14 currently pending
Career history
545
Total Applications
across all art units

Statute-Specific Performance

§101
0.3%
-39.7% vs TC avg
§103
86.0%
+46.0% vs TC avg
§102
12.5%
-27.5% vs TC avg
§112
0.7%
-39.3% vs TC avg
Black line = Tech Center average estimate • Based on career data from 523 resolved cases

Office Action

§102
DETAILED ACTION Continued Examination Under 37 CFR 1.114 A request for continued examination under 37 CFR 1.114, including the fee set forth in 37 CFR 1.17(e), was filed in this application after final rejection. Since this application is eligible for continued examination under 37 CFR 1.114, and the fee set forth in 37 CFR 1.17(e) has been timely paid, the finality of the previous Office action has been withdrawn pursuant to 37 CFR 1.114. Applicant's submission filed on 4/16/2026 has been entered. Response to Amendment This Action is in response to the amendment dated 4/16/2026, for which the amendment and corresponding arguments filed on the same date have been entered. Claims 1, 2, 10-12, 18 and 19 are currently pending in this application, with claims 1, 11 and 19 being independent. Claims 1, 11 and 19 have been amended. No claims have been added. Response to Arguments Applicant's arguments filed 4/16/2026 have been fully considered, but are not persuasive. On pages 7-11 of the arguments, the applicant makes similar arguments regarding the amended claims. Applicant states the reserved field range 0100-1111 also includes values such as 0110, 1110, 1111, etc., but that, while Lagrange appears to mention this solution, the values and their corresponding indications are uncertain and that, therefore, Lagrange does not propose a specific indication scheme, also stating that that the Office Action's interpretation to equate the broad field range in Lagrange with the specific correspondence provided in Applicant's claim 1 is incorrect. Applicant also argues Applicant's claim 1 provides a specific indication scheme in which specific bit values (0011, 0100, 0101) within a specific field of the BAP Control PDU uniquely indicate three distinct states: "RLF failure," "RLF detection," and "RLF success," respectively. Examiner respectfully disagrees. Regarding the 0011 in the field of the BAP control PDU indicating when the RLF occurs on a backhaul link between the IAB node and a parent node, Lagrange teaches BH RLF Indication set specifically to “0011” used for when the IAB-node 402 indicates the RLF failure between IAB-node 402 and parent IAB-node 401 using Control PDU 600 that includes field 602, indicating RLF failure is determined, as indicated in the cited [0178] and [0209]. Regarding the 0100 in the field of the BAP control PDU indicating a detection that a RLF occurs on a backhaul link between the IAB and a parent node, Lagrange teaches BH RLF indication set specifically to “0100” within the reserved values 0100-1111 is sent as Control PDU BH RLF indication to signal a radio link recovery, the occurrence of the RLF recovery indicating the RLF failure was detected between IAB-node 402 and the parent IAB-node 401 and therefore RLF detection, as indicated in the cited [0178] and [0209]. Regarding the 0101 field indicating RLF recovery being successful when the RLF occurs on a backhaul link between the IAB node and a parent node, although Lagrange doesn’t state the 0101 field specifically, since Lagrange still teaches the field can include any number within the range from 0100-1111, the Control PDU BH RLF Indication field 602, which indicates the RLF failure between IAB-node 402 and parent IAB-node 401, can also include the 0101 field, the value taken from the reserved values 0100-1111 being used to signal a radio link recovery and therefore RLF success, as indicated in the cited [0178] and [0209]. Therefore, Lagrange teaches the argued limitations. Claim Rejections - 35 USC § 102 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. The following is a quotation of the appropriate paragraphs of 35 U.S.C. 102 that form the basis for the rejections under this section made in this Office action: A person shall be entitled to a patent unless – (a)(2) the claimed invention was described in a patent issued under section 151, or in an application for patent published or deemed published under section 122(b), in which the patent or application, as the case may be, names another inventor and was effectively filed before the effective filing date of the claimed invention. Claims 1, 2, 10-12, 18 and 19 are rejected under 35 U.S.C. 102(a2) as being anticipated by Lagrange, et al (US PG Publication 2024/0056940), hereafter Lagrange. Regarding claim 1, Lagrange teaches an integrated access and backhaul (IAB) communication method, comprising: detecting, by an IAB node, that on a backhaul link between the IAB node and a parent node, a radio link failure (RLF) occurs or a radio link failure (RLF) recovery is successful, or a radio link failure (RLF) recovery is failure ([0149] Note that for BH RLC channels in downstream direction (parent to child direction, e.g. IAB-node 402 towards IAB-node 403 in FIG. 4), in upstream direction (child to parent direction, e.g. IAB-node 402 towards IAB-node 401) [0178] IAB-node 402 detects a radio link failure for link 410 with IAB-node 401 and fails to recover it from RLF (As explained in [0149], in the downlink direction, the parent node is IAB-node 401, and subsequently the IAB-node 403 becomes the child node of IAB-node 402. Therefore, the IAB-node 402 detects RLF failure between IAB-node 402 and parent IAB-node 401, along with that it fails to recover from RLF)); and transmitting, by the IAB node, RLF indication information to an IAB child node or a terminal equipment by using a Backhaul Adaptation Protocol (BAP) control Protocol Data Unit (PDU), the RLF indication information being used for indicating one of three backhaul radio link failure (BH RLF) types ([0173] FIG. 6 illustrates the format of a BH RLF indication. It is a Control PDU for BH RLF indication 600 [0174] The corresponding BAP packet is a BAP Control packet. This bit is set to ‘0’ for BH RLF indication Control PDU 600 [0178] IAB-node 402 detects a radio link failure for link 410 with IAB-node 401 and fails to recover it from RLF. It thus sends a Control PDU for BH RLF indication 600 to its child IAB-nodes 403 receiving the BH RLF indication 600 (BAP control PDU message 600 is sent from IAB-node 402 to child IAB-node 403 and includes the RLF indication that indicates the RLF failure between IAB-node 402 and parent IAB-node 401, along with that it fails to recover from RLF)); wherein the BAP control PDU is constructed to transmit the RLF indication information, wherein a field indicates a type of control information included in the BAP control PDU ([0173] FIG. 6 illustrates the format of a BH RLF indication. It is a Control PDU for BH RLF indication 600 [0174] It is made of a one-byte header 60 comprising fields 601 to 605. Field 601, indicating whether the corresponding BAP packet is a BAP Control packet. This bit is set to ‘0’ for BH RLF indication Control PDU 600); wherein a plurality of bits in the field of the BAP control PDU indicates one of the three backhaul radio link failure (BH RLF) types ([0173] FIG. 6 illustrates the format of a BH RLF indication. It is a Control PDU for BH RLF indication 600 [0174] It is made of a one-byte header 60 comprising fields 601 to 605. Field 601, indicating whether the corresponding BAP packet is a BAP Control packet. This bit is set to ‘0’ for BH RLF indication Control PDU 600 [0178] IAB-node 402 detects a radio link failure for link 410 with IAB-node 401 and fails to recover it from RLF. It thus sends a Control PDU for BH RLF indication 600 (The message 600 includes one-byte (1 byte = 8 bits) header in the fields, is a BAP control PDU and indicates the RLF failure between IAB-node 402 and parent IAB-node 401, along with that it fails to recover from RLF)); wherein 0011 in the field of the BAP control PDU indicates BH RLF indication, the BH RLF indication denotes the IAB node detected that a radio link failure (RLF) occurs on a backhaul link between the IAB node and a parent node, and a radio link (RLF) recovery is failure ([0178] IAB-node 402 detects a radio link failure for link 410 with IAB-node 401 and fails to recover it from RLF. It thus sends a Control PDU for BH RLF indication 600 (here below “BH RLF indication”) to its child IAB-nodes. Child IAB-node 403 receiving the BH RLF indication 600 infers IAB-node 402 is no longer reliable and then establishes another connection to a different parent IAB-node (not shown) [0209] In these various embodiments of Control PDU for BH RLF Indication 600a, field 602 is set to “0011”. Field 602 may be used to distinctly signal whether the BH RLF Indication 600a signals a radio link deficiency (including failure). Value “0011” may be kept to signal a radio link deficiency (IAB-node 402 indicates the RLF failure between IAB-node 402 and parent IAB-node 401 using Control PDU 600 that includes field 602 for BH RLF Indication set to “0011”)), 0100 in the field of the BAP control PDU indicates BH RLF detection indication, the BH RLF detection indication denotes the IAB node detected that a radio link failure (RLF) occurs on a backhaul link between the IAB and a parent node ([0178] IAB-node 402 detects a radio link failure for link 410 with IAB-node 401 and fails to recover it from RLF. It thus sends a Control PDU for BH RLF indication 600 (here below “BH RLF indication”) to its child IAB-nodes. Child IAB-node 403 receiving the BH RLF indication 600 infers IAB-node 402 is no longer reliable and then establishes another connection to a different parent IAB-node (not shown) [0209] In these various embodiments of Control PDU for BH RLF Indication 600a, field 602 may be used to distinctly signal whether the BH RLF Indication 600a signals a radio link deficiency (including failure). A value (taken from the reserved values 0100-1111) may be used to signal a radio link recovery [0210] The example of FIG. 6a thus discloses a Control protocol data unit, PDU, for backhaul, BH, radio link failure, RLF, indication including a field of which taking a value indicating a detected link condition change in an Integrated Access and Backhaul, IAB (IAB-node 402 sends Control PDU to indicate the RLF failure between IAB-node 402 and parent IAB-node 401 using Control PDU 600 that includes field 602 for BH RLF Indication, the BH RLF indication including a value taken from the reserved values 0100-1111 used to signal a radio link recovery, meaning the field may include the value 0100, which is included within the reserved values 0100-1111, indicates the RLF failure was detected between IAB-node 402 and the parent IAB-node 401))), and 0101 in the field of the BAP control PDU indicates BH RLF recovery indication, the BH RLF recovery indication denotes the IAB node detected that a radio link failure (RLF) occurs on a backhaul link between the IAB node and a parent node, and a radio link failure (RLF) recovery is successful ([0178] IAB-node 402 detects a radio link failure for link 410 with IAB-node 401 and fails to recover it from RLF. It thus sends a Control PDU for BH RLF indication 600 (here below “BH RLF indication”) to its child IAB-nodes. Child IAB-node 403 receiving the BH RLF indication 600 infers IAB-node 402 is no longer reliable and then establishes another connection to a different parent IAB-node (not shown) [0209] In these various embodiments of Control PDU for BH RLF Indication 600a, field 602 may be used to distinctly signal whether the BH RLF Indication 600a signals a radio link deficiency (including failure). A value (taken from the reserved values 0100-1111) may be used to signal a radio link recovery [0210] The example of FIG. 6a thus discloses a Control protocol data unit, PDU, for backhaul, BH, radio link failure, RLF, indication including a field of which taking a value indicating a detected link condition change in an Integrated Access and Backhaul, IAB (IAB-node 402 sends Control PDU to indicate the RLF failure between IAB-node 402 and parent IAB-node 401 using Control PDU 600 that includes field 602 for BH RLF Indication, the BH RLF indication including a value taken from the reserved values 0100-1111 used to signal a radio link recovery, meaning the field may include the value 0101, which is included within the reserved values 0100-1111, indicates the RLF failure was detected between IAB-node 402 and the parent IAB-node 401, along with a RLF recovery)). Regarding claim 2, Lagrange teaches the method according to claim 1, wherein the three backhaul radio link failure (BH RLF) type comprises: a first type of backhaul radio link failure (BH RLF) denoting the IAB node detected that a radio link failure (RLF) occurs on a backhaul link between the IAB node and a parent node ([0178] IAB-node 402 detects a radio link failure for link 410 with IAB-node 401 (Indicates the RLF failure between IAB-node 402 and parent IAB-node 401)); a second type of backhaul radio link failure (BH RLF) denoting the IAB node detected that a radio link failure (RLF) occurs on a backhaul link between the IAB node and a parent node, and a radio link failure (RLF) recovery is successful ([0209] In these various embodiments of Control PDU for BH RLF Indication 600a, field 602 may be used to distinctly signal whether the BH RLF Indication 600a signals a radio link recovery); or a third type of backhaul radio link failure (BH RLF) denoting the IAB node detected that a radio link failure (RLF) occurs on a backhaul link between the IAB node and a parent node, and a radio link failure (RLF) recovery is failure ([0178] IAB-node 402 detects a radio link failure for link 410 with IAB-node 401 and fails to recover it from RLF (Indicates the RLF failure between IAB-node 402 and parent IAB-node 401, along with that it fails to recover from RLF)). Regarding claim 10, Lagrange teaches the method according to claim 1, wherein 0011 in the field of the BAP control PDU indicates a third type of backhaul radio link failure (BH RLF) ([0209] In these various embodiments of Control PDU for BH RLF Indication 600a, field 602 is set to “0011”. Field 602 may be used to distinctly signal whether the BH RLF Indication 600a signals a radio link deficiency (including failure). Value “0011” may be kept to signal a radio link deficiency), 0100 in the field of the BAP control PDU indicates a first type of backhaul radio link failure (BH RLF) ([0209] In these various embodiments of Control PDU for BH RLF Indication 600a, field 602 may be used to distinctly signal whether the BH RLF Indication 600a signals a radio link deficiency (including failure). A value (taken from the reserved values 0100-1111) may be used to signal a radio link recovery [0210] The example of FIG. 6a thus discloses a Control protocol data unit, PDU, for backhaul, BH, radio link failure, RLF, indication including a field of which taking a value indicating a detected link condition change in an Integrated Access and Backhaul, IAB (BH RLF Indication 600a with field 602 is used to distinctly signal the BH RLF indication that includes a value (taken from the reserved values 0100-1111), the BH RLF indication including a field of which taking a value indicating a detected link condition change in an Integrated Access and Backhaul, IAB, meaning the value taken from the reserved value in 0100-1111, which includes 0100, is used by the BH RLF indication to indicate a detected link condition change in an Integrated Access and Backhaul, IAB. The field 0100 then can be used to indicate the BH RLF is detected)), 0101 in the field of the BAP control PDU indicates a second type of backhaul radio link failure (BH RLF) ([0209] while a new value (taken from the reserved values 0100-1111) may be used to signal a radio link recovery (0101 is located within the reserved values 0100-1111)). Regarding claim 11, Lagrange teaches an apparatus, applicable to an integrated access and backhaul (IAB) communication device, the apparatus comprising (Fig. 4 IAB-node 402 [0023] A detecting IAB-node having Backhaul, BH, radio links established with other IAB-node [0393] FIG. 11 shows a schematic representation a communication device, in accordance with one or more example embodiments of the present disclosure [0394] The communication device 1100 comprises a communication bus 1113 to which there are preferably connected: [0395] a central processing unit 1111, such as a microprocessor, denoted CPU); processor circuitry configured to detect that on a backhaul link between a IAB node and a parent node, a radio link failure (RLF) occurs or a radio link failure (RLF) recovery is successful, or a radio link recovery (RLF) recovery is failure ([0149] Note that for BH RLC channels in downstream direction (parent to child direction, e.g. IAB-node 402 towards IAB-node 403 in FIG. 4), in upstream direction (child to parent direction, e.g. IAB-node 402 towards IAB-node 401) [0178] IAB-node 402 detects a radio link failure for link 410 with IAB-node 401 and fails to recover it from RLF (As explained in [0149], in the downlink direction, the parent node is IAB-node 401, and subsequently the IAB-node 403 becomes the child node of IAB-node 402. Therefore, the IAB-node 402 detects RLF failure between IAB-node 402 and parent IAB-node 401, along with that it fails to recover from RLF)), and a transmitter configured to transmit RLF indication information to an IAB child node or a terminal equipment by using a BAP control PDU; the RLF indication information being used for indicating one of three backhaul radio link failure (BH RLF) type ([0173] FIG. 6 illustrates the format of a BH RLF indication. It is a Control PDU for BH RLF indication 600 [0174] The corresponding BAP packet is a BAP Control packet. This bit is set to ‘0’ for BH RLF indication Control PDU 600 [0178] IAB-node 402 detects a radio link failure for link 410 with IAB-node 401 and fails to recover it from RLF. It thus sends a Control PDU for BH RLF indication 600 to its child IAB-nodes 403 receiving the BH RLF indication 600 (BAP control PDU message 600 is sent from IAB-node 402 to child IAB-node 403 and includes the RLF indication that indicates the RLF failure between IAB-node 402 and parent IAB-node 401, along with that it fails to recover from RLF)); wherein the BAP control PDU is constructed to transmit the RLF indication information, wherein a field indicates a type of control information included in the BAP control PDU ([0173] FIG. 6 illustrates the format of a BH RLF indication. It is a Control PDU for BH RLF indication 600 [0174] It is made of a one-byte header 60 comprising fields 601 to 605. Field 601, indicating whether the corresponding BAP packet is a BAP Control packet. This bit is set to ‘0’ for BH RLF indication Control PDU 600); wherein a plurality of bits in the field of the BAP control PDU indicates one of the three backhaul radio link failure (BH RLF) types ([0173] FIG. 6 illustrates the format of a BH RLF indication. It is a Control PDU for BH RLF indication 600 [0174] It is made of a one-byte header 60 comprising fields 601 to 605. Field 601, indicating whether the corresponding BAP packet is a BAP Control packet. This bit is set to ‘0’ for BH RLF indication Control PDU 600 [0178] IAB-node 402 detects a radio link failure for link 410 with IAB-node 401 and fails to recover it from RLF. It thus sends a Control PDU for BH RLF indication 600 (The message 600 includes one-byte (1 byte = 8 bits) header in the fields, is a BAP control PDU and indicates the RLF failure between IAB-node 402 and parent IAB-node 401, along with that it fails to recover from RLF)); wherein 0011 in the field of the BAP control PDU indicates BH RLF indication, the BH RLF indication denotes the IAB node detected that a radio link failure (RLF) occurs on a backhaul link between the IAB node and a parent node, and a radio link (RLF) recovery is failure ([0178] IAB-node 402 detects a radio link failure for link 410 with IAB-node 401 and fails to recover it from RLF. It thus sends a Control PDU for BH RLF indication 600 (here below “BH RLF indication”) to its child IAB-nodes. Child IAB-node 403 receiving the BH RLF indication 600 infers IAB-node 402 is no longer reliable and then establishes another connection to a different parent IAB-node (not shown) [0209] In these various embodiments of Control PDU for BH RLF Indication 600a, field 602 is set to “0011”. Field 602 may be used to distinctly signal whether the BH RLF Indication 600a signals a radio link deficiency (including failure). Value “0011” may be kept to signal a radio link deficiency (IAB-node 402 indicates the RLF failure between IAB-node 402 and parent IAB-node 401 using Control PDU 600 that includes field 602 for BH RLF Indication set to “0011”)), 0100 in the field of the BAP control PDU indicates BH RLF detection indication, the BH RLF detection indication denotes the IAB node detected that a radio link failure (RLF) occurs on a backhaul link between the IAB and a parent node ([0178] IAB-node 402 detects a radio link failure for link 410 with IAB-node 401 and fails to recover it from RLF. It thus sends a Control PDU for BH RLF indication 600 (here below “BH RLF indication”) to its child IAB-nodes. Child IAB-node 403 receiving the BH RLF indication 600 infers IAB-node 402 is no longer reliable and then establishes another connection to a different parent IAB-node (not shown) [0209] In these various embodiments of Control PDU for BH RLF Indication 600a, field 602 may be used to distinctly signal whether the BH RLF Indication 600a signals a radio link deficiency (including failure). A value (taken from the reserved values 0100-1111) may be used to signal a radio link recovery [0210] The example of FIG. 6a thus discloses a Control protocol data unit, PDU, for backhaul, BH, radio link failure, RLF, indication including a field of which taking a value indicating a detected link condition change in an Integrated Access and Backhaul, IAB (IAB-node 402 sends Control PDU to indicate the RLF failure between IAB-node 402 and parent IAB-node 401 using Control PDU 600 that includes field 602 for BH RLF Indication, the BH RLF indication including a value taken from the reserved values 0100-1111 used to signal a radio link recovery, meaning the field may include the value 0100, which is included within the reserved values 0100-1111, indicates the RLF failure was detected between IAB-node 402 and the parent IAB-node 401)), and 0101 in the field of the BAP control PDU indicates BH RLF recovery indication, the BH RLF recovery indication denotes the IAB node detected that a radio link failure (RLF) occurs on a backhaul link between the IAB node and a parent node, and a radio link failure (RLF) recovery is successful ([0178] IAB-node 402 detects a radio link failure for link 410 with IAB-node 401 and fails to recover it from RLF. It thus sends a Control PDU for BH RLF indication 600 (here below “BH RLF indication”) to its child IAB-nodes. Child IAB-node 403 receiving the BH RLF indication 600 infers IAB-node 402 is no longer reliable and then establishes another connection to a different parent IAB-node (not shown) [0209] In these various embodiments of Control PDU for BH RLF Indication 600a, field 602 may be used to distinctly signal whether the BH RLF Indication 600a signals a radio link deficiency (including failure). A value (taken from the reserved values 0100-1111) may be used to signal a radio link recovery [0210] The example of FIG. 6a thus discloses a Control protocol data unit, PDU, for backhaul, BH, radio link failure, RLF, indication including a field of which taking a value indicating a detected link condition change in an Integrated Access and Backhaul, IAB (IAB-node 402 sends Control PDU to indicate the RLF failure between IAB-node 402 and parent IAB-node 401 using Control PDU 600 that includes field 602 for BH RLF Indication, the BH RLF indication including a value taken from the reserved values 0100-1111 used to signal a radio link recovery, meaning the field may include the value 0101, which is included within the reserved values 0100-1111, indicates the RLF failure was detected between IAB-node 402 and the parent IAB-node 401, along with a RLF recovery)). Regarding claim 12, Lagrange teaches the apparatus according to claim 11, wherein the three backhaul radio link failure (BH RLF) type comprises: a first type of backhaul radio link failure (BH RLF) denoting the IAB node detected that a radio link failure (RLF) occurs on a backhaul link between the IAB node and a parent node ([0178] IAB-node 402 detects a radio link failure for link 410 with IAB-node 401 (Indicates the RLF failure between IAB-node 402 and parent IAB-node 401)); a second type of backhaul radio link failure (BH RLF) denoting the IAB node detected that a radio link failure (RLF) occurs on a backhaul link between the IAB node and a parent node, and a radio link failure (RLF) recovery is successful ([0209] In these various embodiments of Control PDU for BH RLF Indication 600a, field 602 may be used to distinctly signal whether the BH RLF Indication 600a signals a radio link recovery); or a third type of backhaul radio link failure (BH RLF) denoting the IAB node detected that a radio link failure (RLF) occurs on a backhaul link between the IAB node and a parent node, and a radio link failure (RLF) recovery is failure ([0178] IAB-node 402 detects a radio link failure for link 410 with IAB-node 401 and fails to recover it from RLF (Indicates the RLF failure between IAB-node 402 and parent IAB-node 401, along with that it fails to recover from RLF)). Regarding claim 18, Lagrange teaches the apparatus according to claim 11, wherein 0011 in the field of the BAP control PDU indicates a third type of backhaul radio link failure (BH RLF) ([0209] In these various embodiments of Control PDU for BH RLF Indication 600a, field 602 is set to “0011”. Field 602 may be used to distinctly signal whether the BH RLF Indication 600a signals a radio link deficiency (including failure). Value “0011” may be kept to signal a radio link deficiency), 0100 in the field of the BAP control PDU indicates a first type of backhaul radio link failure (BH RLF) ([0209] In these various embodiments of Control PDU for BH RLF Indication 600a, field 602 may be used to distinctly signal whether the BH RLF Indication 600a signals a radio link deficiency (including failure). A value (taken from the reserved values 0100-1111) may be used to signal a radio link recovery [0210] The example of FIG. 6a thus discloses a Control protocol data unit, PDU, for backhaul, BH, radio link failure, RLF, indication including a field of which taking a value indicating a detected link condition change in an Integrated Access and Backhaul, IAB (BH RLF Indication 600a with field 602 is used to distinctly signal the BH RLF indication that includes a value (taken from the reserved values 0100-1111), the BH RLF indication including a field of which taking a value indicating a detected link condition change in an Integrated Access and Backhaul, IAB, meaning the value taken from the reserved value in 0100-1111, which includes 0100, is used by the BH RLF indication to indicate a detected link condition change in an Integrated Access and Backhaul, IAB. The field 0100 then can be used to indicate the BH RLF is detected)), 0101 in the field of the BAP control PDU indicates a second type of backhaul radio link failure (BH RLF) ([0209] while a new value (taken from the reserved values 0100-1111) may be used to signal a radio link recovery (0101 is located within the reserved values 0100-1111)). Regarding claim 19, Lagrange teaches a communication system, comprising: an IAB node configured to (Fig. 4 IAB-node 402 [0023] A detecting IAB-node having Backhaul, BH, radio links established with other IAB-node: detect that on a backhaul link between the IAB node and a parent node, a radio link failure (RLF) occurs or a radio link failure (RLF) recovery is successful, or a radio link failure (RLF) recovery is failure ([0149] Note that for BH RLC channels in downstream direction (parent to child direction, e.g. IAB-node 402 towards IAB-node 403 in FIG. 4), in upstream direction (child to parent direction, e.g. IAB-node 402 towards IAB-node 401) [0178] IAB-node 402 detects a radio link failure for link 410 with IAB-node 401 and fails to recover it from RLF (As explained in [0149], in the downlink direction, the parent node is IAB-node 401, and subsequently the IAB-node 403 becomes the child node of IAB-node 402. Therefore, the IAB-node 402 detects RLF failure between IAB-node 402 and parent IAB-node 401, along with that it fails to recover from RLF)), and transmit RLF indication information to an IAB child node or a terminal equipment by using a BAP control PDU ([0173] FIG. 6 illustrates the format of a BH RLF indication. It is a Control PDU for BH RLF indication 600 [0174] The corresponding BAP packet is a BAP Control packet. This bit is set to ‘0’ for BH RLF indication Control PDU 600 [0178] IAB-node 402 sends a Control PDU for BH RLF indication 600 to its child IAB-nodes 403 receiving the BH RLF indication 600 (BAP control PDU message 600 is sent from IAB-node 402 to child IAB-node 403 and includes the RLF indication)); the RLF indication information being used for indicating one of three backhaul radio link failure (BH RLF) type ([0178] IAB-node 402 detects a radio link failure for link 410 with IAB-node 401 and fails to recover it from RLF. It thus sends a Control PDU for BH RLF indication 600 to its child IAB-nodes 403 receiving the BH RLF indication 600 (The BAP control PDU message 600 sent from IAB-node 402 to child IAB-node 403 that includes the RLF indication indicates the RLF failure between IAB-node 402 and parent IAB-node 401, along with that it fails to recover from RLF)); wherein the BAP control PDU is constructed to transmit the RLF indication information, wherein a field indicates a type of control information included in the BAP control PDU ([0173] FIG. 6 illustrates the format of a BH RLF indication. It is a Control PDU for BH RLF indication 600 [0174] It is made of a one-byte header 60 comprising fields 601 to 605. Field 601, indicating whether the corresponding BAP packet is a BAP Control packet. This bit is set to ‘0’ for BH RLF indication Control PDU 600); wherein a plurality of bits in the field of the BAP control PDU indicates one of the three backhaul radio link failure (BH RLF) types ([0173] FIG. 6 illustrates the format of a BH RLF indication. It is a Control PDU for BH RLF indication 600 [0174] It is made of a one-byte header 60 comprising fields 601 to 605. Field 601, indicating whether the corresponding BAP packet is a BAP Control packet. This bit is set to ‘0’ for BH RLF indication Control PDU 600 [0178] IAB-node 402 detects a radio link failure for link 410 with IAB-node 401 and fails to recover it from RLF. It thus sends a Control PDU for BH RLF indication 600 (The message 600 includes one-byte (1 byte = 8 bits) header in the fields, is a BAP control PDU and indicates the RLF failure between IAB-node 402 and parent IAB-node 401, along with that it fails to recover from RLF)); wherein 0011 in the field of the BAP control PDU indicates BH RLF indication, the BH RLF indication denotes the IAB node detected that a radio link failure (RLF) occurs on a backhaul link between the IAB node and a parent node, and a radio link (RLF) recovery is failure ([0178] IAB-node 402 detects a radio link failure for link 410 with IAB-node 401 and fails to recover it from RLF. It thus sends a Control PDU for BH RLF indication 600 (here below “BH RLF indication”) to its child IAB-nodes. Child IAB-node 403 receiving the BH RLF indication 600 infers IAB-node 402 is no longer reliable and then establishes another connection to a different parent IAB-node (not shown) [0209] In these various embodiments of Control PDU for BH RLF Indication 600a, field 602 is set to “0011”. Field 602 may be used to distinctly signal whether the BH RLF Indication 600a signals a radio link deficiency (including failure). Value “0011” may be kept to signal a radio link deficiency (IAB-node 402 indicates the RLF failure between IAB-node 402 and parent IAB-node 401 using Control PDU 600 that includes field 602 for BH RLF Indication set to “0011”)), 0100 in the field of the BAP control PDU indicates BH RLF detection indication, the BH RLF detection indication denotes the IAB node detected that a radio link failure (RLF) occurs on a backhaul link between the IAB and a parent node ([0178] IAB-node 402 detects a radio link failure for link 410 with IAB-node 401 and fails to recover it from RLF. It thus sends a Control PDU for BH RLF indication 600 (here below “BH RLF indication”) to its child IAB-nodes. Child IAB-node 403 receiving the BH RLF indication 600 infers IAB-node 402 is no longer reliable and then establishes another connection to a different parent IAB-node (not shown) [0209] In these various embodiments of Control PDU for BH RLF Indication 600a, field 602 may be used to distinctly signal whether the BH RLF Indication 600a signals a radio link deficiency (including failure). A value (taken from the reserved values 0100-1111) may be used to signal a radio link recovery [0210] The example of FIG. 6a thus discloses a Control protocol data unit, PDU, for backhaul, BH, radio link failure, RLF, indication including a field of which taking a value indicating a detected link condition change in an Integrated Access and Backhaul, IAB (IAB-node 402 sends Control PDU to indicate the RLF failure between IAB-node 402 and parent IAB-node 401 using Control PDU 600 that includes field 602 for BH RLF Indication, the BH RLF indication including a value taken from the reserved values 0100-1111 used to signal a radio link recovery, meaning the field may include the value 0100, which is included within the reserved values 0100-1111, indicates the RLF failure was detected between IAB-node 402 and the parent IAB-node 401))), and 0101 in the field of the BAP control PDU indicates BH RLF recovery indication, the BH RLF recovery indication denotes the IAB node detected that a radio link failure (RLF) occurs on a backhaul link between the IAB node and a parent node, and a radio link failure (RLF) recovery is successful ([0178] IAB-node 402 detects a radio link failure for link 410 with IAB-node 401 and fails to recover it from RLF. It thus sends a Control PDU for BH RLF indication 600 (here below “BH RLF indication”) to its child IAB-nodes. Child IAB-node 403 receiving the BH RLF indication 600 infers IAB-node 402 is no longer reliable and then establishes another connection to a different parent IAB-node (not shown) [0209] In these various embodiments of Control PDU for BH RLF Indication 600a, field 602 may be used to distinctly signal whether the BH RLF Indication 600a signals a radio link deficiency (including failure). A value (taken from the reserved values 0100-1111) may be used to signal a radio link recovery [0210] The example of FIG. 6a thus discloses a Control protocol data unit, PDU, for backhaul, BH, radio link failure, RLF, indication including a field of which taking a value indicating a detected link condition change in an Integrated Access and Backhaul, IAB (IAB-node 402 sends Control PDU to indicate the RLF failure between IAB-node 402 and parent IAB-node 401 using Control PDU 600 that includes field 602 for BH RLF Indication, the BH RLF indication including a value taken from the reserved values 0100-1111 used to signal a radio link recovery, meaning the field may include the value 0101, which is included within the reserved values 0100-1111, indicates the RLF failure was detected between IAB-node 402 and the parent IAB-node 401, along with a RLF recovery)). Conclusion Citation of Pertinent Prior Art not Applied The prior art made of record and not relied upon is considered pertinent to applicant's disclosure. Luo, et al (US PG Publication 2022/0141749), hereafter Luo, teaches an IAB link control method. Any inquiry concerning this communication or earlier communications from the examiner should be directed to Examiner Frank Donado whose telephone number is (571) 270-5361. The examiner can normally be reached Mondays through Fridays between 8 am and 4 pm. Examiner interviews are available via telephone 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 Patent Examiner (SPE) Charles Appiah can be reached at 571-272-7904. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300. Information regarding the status of an application may be obtained from the Patent Application Information Retrieval (PAIR) system. Status information for published applications may be obtained from either Private PAIR or Public PAIR. Status information for unpublished applications is available through Private PAIR only. For more information about the PAIR system, see http://pair-direct.uspto.gov. Should you have questions on access to the Private PAIR system, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative or access to the automated information system, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000. /FRANK E DONADO/Examiner, Art Unit 2641 /CHARLES N APPIAH/Supervisory Patent Examiner, Art Unit 2641
Read full office action

Prosecution Timeline

Jul 11, 2023
Application Filed
Jul 29, 2025
Non-Final Rejection mailed — §102
Oct 20, 2025
Response Filed
Jan 27, 2026
Final Rejection mailed — §102
Apr 16, 2026
Request for Continued Examination
Apr 17, 2026
Response after Non-Final Action
May 01, 2026
Non-Final Rejection mailed — §102 (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12634776
Radio Link Monitoring During Handover
11m to grant Granted May 19, 2026
Patent 12621738
COMMUNICATION METHOD AND RELATED DEVICE
3y 0m to grant Granted May 05, 2026
Patent 12610372
DOWNLINK DATA RECEPTION OPERATION
4y 0m to grant Granted Apr 21, 2026
Patent 12610299
USER EQUIPMENT, NODE, AND COMMUNICATION METHOD
2y 8m to grant Granted Apr 21, 2026
Patent 12598027
COMMUNICATION METHOD AND APPARATUS
4y 1m to grant Granted Apr 07, 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

3-4
Expected OA Rounds
69%
Grant Probability
99%
With Interview (+59.3%)
3y 0m (~2m remaining)
Median Time to Grant
High
PTA Risk
Based on 523 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