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 § 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.
Claim(s) 1, 3-6, 11, 12, 14, 16, and 21 is/are rejected under 35 U.S.C. 103 as being unpatentable over Nokia Re-routing enhancements and RLF indications in IAB 'Nokia' in view of Pradas WO 2020085969 and Chen US 20230388894.
Regarding claim 1, 12, and 21, Nokia teaches a comprising:
detecting, by an integrated access and backhaul (IAB) node, a backhaul (BH) problem on a first BH link,
wherein the IAB node has the first BH link with a first parent node (section 2.2 IAB#2) and a second BH link with a second parent node (section 2.2 IAB#4), and
wherein the first BH link is related to first traffic and second traffic;
based on detecting the BH problem, performing, by the IAB node, a re-routing for the first traffic over the second BH link (see section 2.2: fig. 1, in case Path#1 is not available due to BH RLF between IAB#1 and IAB#2, IAB#1 may select Path #2).
Nokia is silent on transmitting, by the IAB node to a child node, a backhaul adaptation protocol (BAP) control protocol data unit (PDU) for a notification of the BH problem.
Pradas teaches transmitting, by the IAB node to a child node, a backhaul adaptation protocol (BAP) control protocol data unit (PDU) for a notification of the BH problem (Such embodiments include receiving, from a first upstream node in the IAB network, a first indication of failure of a first backhaul link (i.e. RLF) in a first network path that includes the intermediate node, the first upstream node, and a destination node for uplink data in the IAB network, Embodiments also include, based on information associated with the first indication, selectively forwarding the first indication (e.g., based on content of the first indication) to one or more downstream nodes in the IAB network, abstract).
Therefore it would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention, to modify the system of Nokia by transmitting, by the IAB node to a child node, a backhaul adaptation protocol (BAP) control protocol data unit (PDU) for a notification of the BH problem, as shown by Pradas. This modification would benefit the system by informing the child node of the link failure.
The combination is silent on wherein the BAP control PDU comprises i) information for the first traffic for which re-routing is performed by the IAB node, and ii) information for the second traffic for which re-routing is not performed by the IAB node.
Chen teaches wherein the BAP control PDU comprises i) information for the first traffic for which re-routing is performed by the IAB node (first transmission path), and ii) information for the second traffic (second transmission path)for which re-routing is not performed by the IAB node ([0050] In addition, if the packet rerouting happens, the IAB node or donor DU 316 may send rerouting reporting information regarding the rerouting to the donor CU 318. In various examples, the rerouting reporting information comprises at least one of the following: a BAP routing ID of the first transmission path; a BAP routing ID of the second transmission path; a duration of the rerouting; a data rate of the second transmission path; and/or a data volume of the second transmission path).
Therefore it would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention, to modify the system of the combination by wherein the BAP control PDU comprises i) information for the first traffic for which re-routing is performed by the IAB node (first transmission path), and ii) information for the second traffic (second transmission path)for which re-routing is not performed by the IAB node, as shown by Chen. This modification would benefit the system by informing the child node that additional traffic has been rerouted to the second transmission path. The child node may then decide to load balance data that will be transmitted the second transmission path.
Regarding claim 3, the problem comprises at least one of:
a radio link failure (RLF) on the backhaul connection (Nokia: see section 2.2);
a transmission delay over the backhaul connection exceeding a threshold;
an amount of queued packets over the backhaul connection exceeding a threshold; or
a quality of the backhaul connection being lower than a threshold.
Regarding claim 4, 14, wherein the BAP control PDU further comprises a notification that the BH problem for the
first BH link is detected (Pradas: abstract).
Regarding claim 5, BAP control PDU further comprises a notification that the IAB node has performed a re-routing routing path for the one or more first data flows traffic (Chen: [0050])).
Regarding claim 6, the BAP control PDU
further comprises a notification that IAB node has not
performed a re-routing for the second traffic (Chen: [0050]: note no mention of traffic on the second path has been rerouted).
Regarding claim 11, the first wireless device (Nokia: fig. 1 IAB1) is in communication with at least one of a user equipment (UE), a mobile device, a network (Nokia: fig. 1 IAB2) or autonomous vehicles.
Regarding claim 16, transmitting, to a next-hop node for the fourth wireless device in downstream direction, a re-routing notification informing that a re-routing for the one or more first
data flows switched traffic is performed (Chen: [0050]).
Response to Arguments
Applicant’s arguments with respect to the amended independent claim(s) have been considered but are moot because the new ground of rejection does not rely on any reference applied in the prior rejection of record for any teaching or matter specifically challenged in the argument.
Conclusion
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 RONALD B ABELSON whose telephone number is (571)272-3165. The examiner can normally be reached M-F 8:00-4:30.
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, Ayaz Sheikh can be reached at 571-272-3795. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300.
Information regarding the status of published or unpublished applications may be obtained from Patent Center. Unpublished application information in Patent Center is available to registered users. To file and manage patent submissions in Patent Center, visit: https://patentcenter.uspto.gov. Visit https://www.uspto.gov/patents/apply/patent-center for more information about Patent Center and https://www.uspto.gov/patents/docx for information about filing in DOCX format. For additional questions, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000.
/RONALD B ABELSON/ Primary Examiner, Art Unit 2476
Prosecution Insights