DETAILED ACTION
Response to Amendment
This Action is in response to the amendment dated 10/20/2025, 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, 2, 10-12, 18 and 19 have been amended. Claims 3-9 and 13-17 have been cancelled. No claims have been added. This Action is made FINAL.
Response to Arguments
Applicant's arguments filed 10/20/2025 have been fully considered, but are not persuasive.
On page 8 of the arguments, the applicant argues that, based on the amendment, Lagrange appears to mention an IAB-node sending a BH RLF indication to a child node via a BAP PDU (MDU mentioned in Lagrange, likely referring to PDU), this indication being used to notify the child node that the uplink is unreliable. That is, Lagrange appears to merely mention sending an indication of BH RLF to a child node. However, Lagrange fails to disclose indicating the specific type of BH RLF. Based on this, applicant argues that therefore, Lagrange fails to disclose the claimed feature "the RLF indication information being used for indicating one of three backhaul radio link failure (BH RLF) types” recited in claim 1. On pages 11 and 12 of the arguments, applicant provides a similar argument regarding claims 11 and 19, respectively.
Examiner respectfully disagrees.
As explained in the cited [0178], in response to the IAB-node 402 detecting a radio link failure and failure to recover it from RLF, the IAB-node 402 sends BH RLF indication 600 to its child IAB-nodes 403 receiving the BH RLF indication 600. In other words, the BH RLF indication includes an RLF indication that indicates RLF failure and failure to recover from RLF, which are types of BH RLF. Therefore, Lagrange teaches the argued limitations.
On pages 8-10 of the response, the applicant argues that Lagrange appears to mention using fields in this BH RLF indication 600 to indicate different related types and information of BH RLF, and, in Lagrange, it appears that the reserved values from 0100-1111 can be used for indication. However, Lagrange appears to merely mention the range of this field, not the specific indication scheme. Based on this, applicant argues that therefore, Lagrange fails to disclose the claimed feature "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; wherein 0011 in the field of the BAP control PDU indicates BH RLF indication, 0100 in the field of the BAP control PDU indicates BH RLF detection indication, 0101 in the field of the BAP control PDU indicates BH RLF recovery indication” recited in claim 1. On pages 11 and 12 of the arguments, applicant provides a similar argument regarding claims 11 and 19, respectively.
Examiner respectfully disagrees.
Regarding 0011 indicating BH RLF, as explained in the cited [0209], for BH RLF indication 600a, field 602 is set to “0011” and distinctly signals whether the BH RLF indication signals a radio link deficiency, including failure.
Regarding 0100 indicating BH RLF detection, as explained in the cited [0209] and [0210], 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. This has been further clarified in the rejection below.
Regarding 0101 indicating BH RLF recovery, as explained in the cited [0209], a new value (taken from the reserved values 0100-1111) is used to signal a radio link recovery, meaning 0101 located within the reserved values 0100-1111 indicates recovery.
In addition, the above 3 BH RLF types are represented by bits, because, as explained in the cited [0173] and [0174], BH RLF indication 600 is made of a one-byte header (8 bits) 60 comprising fields 601 to 605, meaning the BH RLF indication is represented by 8 bits included in the one-byte header.
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
([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 BH RLF detection indication
([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 BH RLF recovery indication
([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 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
([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 BH RLF detection indication
([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 BH RLF recovery indication
([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 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
([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 BH RLF detection indication
([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 BH RLF recovery indication
([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)).
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.
Liu, et al (US PG Publication 2022/0377827), hereafter Liu, teaches recovery failure processing using BAP.
Applicant's amendment necessitated the new ground(s) of rejection presented in this Office action. Accordingly, THIS ACTION IS MADE FINAL. See MPEP § 706.07(a). Applicant is reminded of the extension of time policy as set forth in 37 CFR 1.136(a).
A shortened statutory period for reply to this final action is set to expire THREE MONTHS from the mailing date of this action. In the event a first reply is filed within TWO MONTHS of the mailing date of this final action and the advisory action is not mailed until after the end of the THREE-MONTH shortened statutory period, then the shortened statutory period will expire on the date the advisory action is mailed, and any extension fee pursuant to 37 CFR 1.136(a) will be calculated from the mailing date of the advisory action. In no event, however, will the statutory period for reply expire later than SIX MONTHS from the date of this final action.
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