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 .
Claim Rejections - 35 USC § 102
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, 4, 7, 8, 11, 12, 14 and 19 are rejected under 35 U.S.C. 102(a)(2) as being anticipated by Akl et al (US 2022/0132393 A1).
Claim 1. Akl shows an apparatus for transmitting and receiving signals (fig. 9), applicable to an integrated access and backhaul node (IAB-node) (fig. 9: IAB-node 904/906/908), the apparatus comprising: a processor (fig. 3: controller / processor 359/375) configured to, when a destination Backhaul Adaptation Protocol (BAP) address of a first path of the IAB-node is unreachable ([0079]: CU2 may ensure that the selected BAP routing ID does not conflict with another BAP routing ID within the section managed by CU2, but in some aspects may still conflict with one used within the section managed by CU1), change routes of first path data ([0080]: the IAB-node 1 may perform header rewriting, such that the IAB-node 1 modifies a BAP routing ID (e.g. BAP routing ID=2) of a packet that it receives on the second portion to another BAP routing ID (e.g. BAP routing ID=1) to be used on the first portion; [0084]: modifying the first routing identifier to a second routing identifier may comprise a change of destination BAP address of the packet); and a transmitter (fig. 3: TX/RX 318 or RX/TX 354) configured to, based on the changed routes, transmit the first path data ([0083]: the IAB-node may modify the header of the packet to carry a second routing ID based on a routing configuration (e.g. header rewriting configuration) that maps the first routing identifier to a second routing identifier wherein the IAB-node may determine a next-hop node based on the second routing ID and the IAB-node may send the packet to the next-hop node), wherein the transmitter is further configured to transmit the first path data to a backhaul RLC channel between the IAB-node and a next hop of node of the second path (fig. 9 and [0077]: IAB-node 3 908 may be connected to the CU2 of the IAB-donor 2 902B. CU1 of the IAB-donor 1 902A may route Fl-U traffic over a secondary path via a donor-DU associated with CU2 of the IAB-donor 2 902B to facilitate load-balancing or redundancy between the IAB-donors; [0083]: the IAB-node may determine a next-hop node based on the second routing ID and the IAB-node may send the packet to the next-hop node; [0084]: the BAP route that includes the next-hop node may be managed by a first IAB-donor-CU, and the BAP route that includes the pre-hop node may be managed by a second IAB-donor-CU; [0087]: the packet may be received from the pre-hop node, and the packet may be transmitted to the next-hop node through the egress backhaul RLC channel).
Claim 2. Akl shows the apparatus according to claim 1, wherein the changing routes of the first path data includes: changing a destination BAP address of the first path data into a destination BAP address of a second path ([0084]: modifying the first routing identifier to a second routing identifier may comprise a change of destination BAP address of the packet… modifying the first routing identifier to a second routing identifier may comprise a change of BAP path ID of the packet), or changing a destination BAP address of the first path data into a destination BAP address of a second path (see above), and changing a path ID of the first path data into a path ID of the second path (see above).
Claim 4. Akl shows the apparatus according to claim 1, wherein that a destination BAP address of a first path of the IAB-node is unreachable comprises that: the destination BAP address of the first path of the IAB-node is unreachable due to that the IAB-node is handed over to a new parent node ([0081]: MT1 is initially connected to donor-DU1 and then switches parents to IAB-node 3), or the destination BAP address of the first path of the IAB-node is unreachable due to that a radio link failure occurs in a link between the IAB-node and a first parent node (n/a).
Claim 7. Akl shows the apparatus according to claim 4, further comprising: a receiver configured to receive a path reconfiguration parameter transmitted by the donor-CU ([0074] – [0075]: the IAB-donor-CU-UP inserts within an IP packet QoS mapping information…), the path reconfiguration parameter including a mapping between the destination BAP address of the first path data and the destination BAP address of the second path ([0074] – [0075]: …which includes the DSCP and the IP flow label wherein based on the QoS mapping information, the IAB-donor-CU-CP configures a routing path for the IAB-donor-DU, so when the IAB-donor-DU receives an IP packet, the IAB-donor-DU decides how to route the traffic), or including a mapping between the destination BAP address and the path ID of the first path data and the destination BAP address and the path ID of the second path (see above).
Claim 8. Akl shows the apparatus according to claim 4, further comprising a receiver configured to receive path reconfiguration parameters transmitted by the donor-CU ([0074]: based on the QoS mapping information, the IAB-donor-CU-CP configures a routing path for the IAB-donor-DU, so when the IAB-donor-DU receives an IP packet, the IAB-donor-DU decides how to route the traffic), the path reconfiguration parameters including the destination BAP address of the second path ([0075]: the downlink mapping configuration indicates a mapping between the IP header fields (destination IP address, DCSP and/IPv6 flow label) and a BAP routing ID), the path ID of the second path ([0077]: MT1 may migrate from the first donor to the second donor, where at least one of the UEs or child/descendant MTs is not yet migrated to the second donor) and an ID of the backhaul RLC channel between the IAB-node and the next hop of node of the second path ([0079]: if the BAP routing ID for the inter-domain backhaul routing path; [0083]: the IAB-node may determine a next-hop node based on the second routing ID and the IAB-node may send the packet to the next-hop node).
---------- ---------- ----------
Claim 11. Akl shows an apparatus for transmitting and receiving signals (fig. 9), applicable to a child node of an integrated access and backhaul node (IAB-node) (fig. 9 and [0077]: at least one of the UEs or child/descendant MTs is not yet migrated to the second donor), the apparatus comprising: a processor (fig. 3: controller / processor 359/375) configured to, when a destination Backhaul Adaptation Protocol (BAP) address of a first path of the IAB-node is unreachable ([0079]: CU2 may ensure that the selected BAP routing ID does not conflict with another BAP routing ID within the section managed by CU2, but in some aspects may still conflict with one used within the section managed by CU1), change routes of first path data ([0080]: the IAB-node 1 may perform header rewriting, such that the IAB-node 1 modifies a BAP routing ID (e.g. BAP routing ID=2) of a packet that it receives on the second portion to another BAP routing ID (e.g. BAP routing ID=1) to be used on the first portion; [0084]: modifying the first routing identifier to a second routing identifier may comprise a change of destination BAP address of the packet); and a transmitter (fig. 3: TX/RX 318 or RX/TX 354) configured to, based on the changed routes, transmit the first path data ([0083]: the IAB-node may modify the header of the packet to carry a second routing ID based on a routing configuration (e.g. header rewriting configuration) that maps the first routing identifier to a second routing identifier wherein the IAB-node may determine a next-hop node based on the second routing ID and the IAB-node may send the packet to the next-hop node), wherein the transmitter configured to transmit the first path data to a backhaul RLC channel between the child node and a next hop of node of the second path (fig. 9 and [0077]: IAB-node 3 908 may be connected to the CU2 of the IAB-donor 2 902B. CU1 of the IAB-donor 1 902A may route Fl-U traffic over a secondary path via a donor-DU associated with CU2 of the IAB-donor 2 902B to facilitate load-balancing or redundancy between the IAB-donors; [0083]: the IAB-node may determine a next-hop node based on the second routing ID and the IAB-node may send the packet to the next-hop node; [0084]: the BAP route that includes the next-hop node may be managed by a first IAB-donor-CU, and the BAP route that includes the pre-hop node may be managed by a second IAB-donor-CU; [0087]: the packet may be received from the pre-hop node, and the packet may be transmitted to the next-hop node through the egress backhaul RLC channel).
Claim 12. Akl shows the apparatus according to claim 11, wherein the changing routes of the first path data includes: changing a destination BAP address of the first path data into a destination BAP address of a second path ([0084]: modifying the first routing identifier to a second routing identifier may comprise a change of destination BAP address of the packet… modifying the first routing identifier to a second routing identifier may comprise a change of BAP path ID of the packet), or changing a destination BAP address of the first path data into a destination BAP address of a second path (see above), and changing a path ID of the first path data into a path ID of the second path (see above).
Claim 14. Akl shows the apparatus according to claim 11, wherein that a destination BAP address of a first path of the IAB-node is unreachable comprises that: the destination BAP address of the first path of the IAB-node is unreachable due to that the IAB-node is handed over to a new parent node ([0081]: MT1 is initially connected to donor-DU1 and then switches parents to IAB-node 3), or the destination BAP address of the first path of the IAB-node is unreachable due to that a radio link failure occurs in a link between the IAB-node and a first parent node (n/a).
Claim 19. Akl shows the apparatus according to claim 14, further comprising a receiver configured to receive path reconfiguration parameters transmitted by the donor-CU, the path reconfiguration parameters comprising the destination BAP address and path ID of the first path ([0074] – [0075]: the IAB-donor-CU-UP inserts within an IP packet QoS mapping information, which includes the DSCP and the IP flow label wherein based on the QoS mapping information, the IAB-donor-CU-CP configures a routing path for the IAB-donor-DU, so when the IAB-donor-DU receives an IP packet, the IAB-donor-DU decides how to route the traffic).
---------- ---------- ----------
Claim Rejections - 35 USC § 103
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, 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.
The factual inquiries for establishing a background for determining obviousness under 35 U.S.C. 103 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.
This application currently names joint inventors. In considering patentability of the claims the examiner presumes that the subject matter of the various claims was commonly owned as of the effective filing date of the claimed invention(s) absent any evidence to the contrary. Applicant is advised of the obligation under 37 CFR 1.56 to point out the inventor and effective filing dates of each claim that was not commonly owned as of the effective filing date of the later invention in order for the examiner to consider the applicability of 35 U.S.C. 102(b)(2)(C) for any potential 35 U.S.C. 102(a)(2) prior art against the later invention.
Claims 5 and 15 are rejected under 35 U.S.C. 103 as being unpatentable over Akl et al in view of Maattanen et al (US 2021/0385675 A1).
Claim 5. Akl shows the apparatus according to claim 4; Akl does not expressly describe wherein, the processor is further configured to: trigger start of a timer after changing the routes of the first path data, and stopping changing the routes of the first path data after the timer expires, or stop changing the routes of the first path data after the unsuccessfully transmitted first path data are transmitted, or stop changing the routes of the first path data after the unsuccessfully transmitted first path data are transmitted and it is determined that the unsuccessfully transmitted first path data are transmitted by a downstream child node.Maattanen teaches features of: triggering start of a timer after changing routes of a first path data ([0071]: initiating a radio link failure (RLF) timer after a predetermined number of consecutive OOS conditions; [0073]: initiating a link recovery procedure after expiration of the RLF timer or after detecting a beam failure; [0172]: pause (or halt) timer and resume after the switch), and stopping changing the routes of the first path data after the timer expires ([0172]: pause (or halt) timer and resume after the switch – timer halts, switching stops), or stopping changing the routes of the first path data after the unsuccessfully transmitted first path data are transmitted (n/a), or stopping changing the routes of the first path data after the unsuccessfully transmitted first path data are transmitted (n/a) and it is determined that the unsuccessfully transmitted first path data are transmitted by a downstream child node ([0164]: UE stops averaging the RS quality (e.g. for determining IS/OOS or beam failure) when the switch happens).It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to implement the timer features as taught by Maattanen in the apparatus of Akl to increase capacity and improve spatial reuse of control channel resources, improve inter-cell interference coordination (ICIC) and support antenna beamforming and/or transmit diversity for control channel.
Claim 15. Akl shows the apparatus according to claim 14; Akl does not expressly describe wherein the processor is further configured to: trigger start of a timer after changing the routes of the first path data, and stopping changing the routes of the first path data after the timer expires, or stop changing the routes of the first path data after the unsuccessfully transmitted first path data are transmitted, or stop changing the routes of the first path data after the unsuccessfully transmitted first path data are transmitted and it is determined that the unsuccessfully transmitted first path data are transmitted by a downstream child node.Maattanen teaches features of: triggering start of a timer after changing routes of a first path data ([0071]: initiating a radio link failure (RLF) timer after a predetermined number of consecutive OOS conditions; [0073]: initiating a link recovery procedure after expiration of the RLF timer or after detecting a beam failure; [0172]: pause (or halt) timer and resume after the switch), and stopping changing the routes of the first path data after the timer expires ([0172]: pause (or halt) timer and resume after the switch – timer halts, switching stops), or stopping changing the routes of the first path data after the unsuccessfully transmitted first path data are transmitted (n/a), or stopping changing the routes of the first path data after the unsuccessfully transmitted first path data are transmitted (n/a) and it is determined that the unsuccessfully transmitted first path data are transmitted by a downstream child node ([0164]: UE stops averaging the RS quality (e.g. for determining IS/OOS or beam failure) when the switch happens). It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to implement the timer features as taught by Maattanen in the apparatus of Akl to increase capacity and improve spatial reuse of control channel resources, improve inter-cell interference coordination (ICIC) and support antenna beamforming and/or transmit diversity for control channel.
---------- ---------- ----------
Claim 20 is rejected under 35 U.S.C. 103 as being unpatentable over Akl et al in view of Zhu et al (US 2023/0199879 A1).
Claim 20. Akl shows the apparatus according to claim 19, wherein in the case where the destination BAP address of the first path is unreachable due to that the IAB-node is handed over to a new parent node ([0081]: MT1 is initially connected to donor-DU1 and then switches parents to IAB-node 3), the path reconfiguration parameters are transmitted by an RRC reconfiguration message before the IAB-node is handed over ([0087]: the routing configuration may be transmitted through one of RRC signaling).Akl does not expressly describe wherein: after a second transceiver receives a handover success indication transmitted by the IAB-node after completing random access to the new parent node, a second processor triggers changing the routes of the first path data.Zhu teaches features of: after a second transceiver receives a handover success indication transmitted by the IAB-node after completing random access to the new parent node ([0078]: the recovery IAB-MT performs synchronization and random access channel (RACH) to a new parent node, which is served by a new IAB-donor-CU), a second processor triggers changing the routes of the first path data ([0087]: the IAB-donor-CU updates the UL BH information associated to each general packet radio service (GPRS) tunneling protocol (GTP)-tunnel to migrating IAB-node).It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to implement the features as taught by Zhu in the apparatus of Akl to provide a flexible NR cell configuration and increase cell density without increasing the density of IAB-donors.
========== ========== ==========
Response to Arguments
Applicant’s arguments and amendments filed 4th May 2026 have been fully considered but they are not persuasive.
The original claims 3 and 13 limitations have been incorporated into independent claims 1 and 11 respectively. The examiner maintains that Akl teaches the limitations – specifically figure 9 and paragraph 0077 cite secondary path in relation to IAB-node and backhaul RLC; the claim rejection citations have been added to address the issue (see claims 1 and 11).
The applicant is welcome to contact the examiner to discuss the case.
========== ========== ==========
Allowable Subject Matter
Claims 6, 9, 10, 16, 17 and 18 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.
---------- ---------- ----------
Conclusion
The prior art made of record is considered pertinent to applicant’s disclosure.
Zhu et al, US 2021/0105795 A1: a path change method comprising steps of establishing, by a first node, a first path and a second path between a first node and a second node, where both the first node and the second node are nodes in the radio access network, and the first node is a wireless backhaul node, a donor node, or a distributed unit of the donor node; sending, by the first node, a data packet to the second node through the first path; and when the first node determines that a path change condition is met, changing, by the first node, from the first path to the second path to send the data packet to the second node.
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 nonprovisional extension fee (37 CFR 1.17(a)) 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 mailing date of this final action.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to Xavier S Wong whose telephone number is (571)270-1780. The examiner can normally be reached on 11:30 am - 8:30 pm Mon to Fri.
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, Jeffrey Rutkowski can be reached on 571.270.1215. 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.
/XAVIER S WONG/Primary Examiner, Art Unit 2415 16th May 2026
Prosecution Insights