DETAILED ACTION
In response to communications filed 01/07/2026.
Claims 24-27 are new.
Claims 1-9, 15, 18, 20, 21 and 24-27 are pending for examination
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 .
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 01/07/2026 has been entered.
Claim Rejections - 35 USC § 103
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 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 set forth in Graham v. John Deere Co., 383 U.S. 1, 148 USPQ 459 (1966), that are applied for establishing a background for determining obviousness under 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 1-9, 15, 18, 20, 21 and 24-27 are rejected under 35 U.S.C. 103 as being unpatentable over Kim et al. (US 2023/0134552 A1) in view of Wu (US 2023/0189110 A1) hereinafter “Kim” and “Wu” respectively.
Regarding Claim 1, Kim teaches A method in a user equipment (UE) (Kim: paragraphs 0158-0160 & Fig. 13, terminal or user equipment) for managing configurations received from a radio access network (RAN) (Kim: paragraph 0054 & Figs. 1-2, wireless access network) the method comprising:
receiving, by the UE and from a first network node (Kim: paragraph 0159 & Fig. 13, source base station or source cell) that supports both a first configuration (Kim: paragraph 0159, (non-DAPS)) configuration or normal handover operation) and a second configuration (Kim: paragraphs 0159-0160 & Fig. 13, DAPS related configuration), (i) the first configuration configuring the UE to utilize a first set of functions (Kim: paragraph 0159, said normal handover operation), and (ii) the second configuration supplementing the first configuration and configuring the UE to utilize a second set of additional functions (Kim: paragraph 0159-160 & Fig. 13, DAPS-related configuration information (in addition to normal configuration) for DAPS handover procedure);
communicating, by the UE, with the first network node in accordance with the first configuration (Kim: paragraph 0158 & Fig. 13, UE maintaining data transmission or reception with a source base station during handover process, thus communicating according to the first configuration; see also paragraph 0158 & Fig. 6, data transmission or reception operation with source cell);
determining, by the UE, that the UE is to re-establish a radio connection with the RAN (Kim: paragraphs 0158-0160 & Fig. 13, handover procedure to target cell) via a second network node (Kim: paragraphs 0159-0160 & Fig. 13, target base station or target cell) that supports the first configuration but not the second configuration (Kim: paragraph 0159 & Fig. 13, required configuration information operation (normal configuration or non-DAPS) to the target cell, thus teaching the target supports only the first configuration; see also paragraph 0160, UE maintaining connection with source cell for which DAPS is configured);
releasing, by the UE, the second configuration so that the UE is no longer configured to utilize the second set of additional functions (Kim: paragraph 0160 & Fig. 13, target sends a RRC Reconfiguration message (including daps-SourceRelease field) for UE to stop data transmission or reception with the source base station, thus teaching the UE no longer utilizes the DAPS operation); and
communicating, by the UE, with the second network node in accordance with the first configuration (Kim: paragraph 0160 & Fig. 13, data transmission and reception in downlink/uplink between UE and target cell).
Kim fails to explicitly teach the second configuration further includes at least one of a sidelink configuration or a reference time reporting configuration. However, Wu from an analogous art similarly teaches a DAPS handover procedure wherein a UE transmits a RRC reconfiguration information for a sidelink communication with another UE (Wu: paragraphs 0110-0112 & Figs. 4A-4B)
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 Kim to include sidelink configurations for DAPS handover as taught by Wu so as to utilize sidelink resources to facilitate a handover.
Regarding Claim 2, Kim-Wu teaches the respective claim(s) as presented above and further teaches wherein the UE releases the second configuration prior to re-establishing the radio connection with the second network node (Kim: paragraph 0160 & Fig. 13, target sends a RRC Reconfiguration message (including daps-SourceRelease field) for UE to stop data transmission or reception with the source base station).
Regarding Claim 3, Kim-Wu teaches the respective claim(s) as presented above and further teaches wherein the UE releases the second configuration in response to detecting a communication failure with the first network node (Kim: paragraphs 0158-0160, handover procedure from source cell to target cell, thus detecting a failure with a communication or link with the source cell).
Regarding Claim 4, Kim-Wu teaches the respective claim(s) as presented above and further teaches wherein the UE releases the second configuration in response to the determining that the UE is to re-establish the radio connection with the second network node (Kim: paragraph 0160 & Fig. 13, target sends a RRC Reconfiguration message (including daps-SourceRelease field) for UE to stop data transmission or reception with the source base station).
Regarding Claim 5, Kim-Wu teaches the respective claim(s) as presented above and further teaches communicating, by the UE, with the second network node using the first configuration after the UE re-establishes the radio connection with the second network node (Kim: paragraph 0160 & Fig. 13, target sends a RRC Reconfiguration message (including daps-SourceRelease field) for UE to stop data transmission or reception with the source base station).
Regarding Claim 6, Kim-Wu teaches the respective claim(s) as presented above and further teaches wherein the UE determines that the UE is to re-establish the radio connection with the second network node after the UE detects a communication failure with the first network node (Kim: paragraphs 0158-0160, handover procedure from source cell to target cell, thus detecting a failure with a communication or link with the source cell).
Regarding Claim 7, Kim teaches A User Equipment (UE) (Kim: paragraphs 0158-0160 & Fig. 13, terminal or user equipment; see also paragraph 0179 & Fig. 16), comprising:
a Radio Resource Control (RRC) controller (Kim: paragraph 0179 & Fig. 16, controller); and
a RAN interface (Kim: paragraph 0180 & Fig. 16, RF processor),
the RRC controller being configured to:
receive, via the RAN interface from a first network node (Kim: paragraph 0159 & Fig. 13, source base station or source cell) that supports both a first configuration (Kim: paragraph 0159, (non-DAPS)) configuration or normal handover operation) and a second configuration (Kim: paragraphs 0159-0160 & Fig. 13, DAPS related configuration), (i) the first configuration configuring the UE to utilize a first set of functions (Kim: paragraph 0159, said normal handover operation), and (ii) the second configuration supplementing the first configuration and configuring the UE to utilize a second set of additional functions (Kim: paragraph 0159-160 & Fig. 13, DAPS-related configuration information (in addition to normal configuration) for DAPS handover procedure);
communicate, via the RAN interface, with the first network node in accordance with the first configuration (Kim: paragraph 0158 & Fig. 13, UE maintaining data transmission or reception with a source base station during handover process, thus communicating according to the first configuration; see also paragraph 0158 & Fig. 6, data transmission or reception operation with source cell);
determine that the UE is to re-establish a radio connection with the RAN (Kim: paragraphs 0158-0160 & Fig. 13, handover procedure to target cell) via a second network node (Kim: paragraphs 0159-0160 & Fig. 13, target base station or target cell) that supports the first configuration but not the second configuration (Kim: paragraph 0159 & Fig. 13, required configuration information operation (normal configuration or non-DAPS) to the target cell, thus teaching the target supports only the first configuration; see also paragraph 0160, UE maintaining connection with source cell for which DAPS is configured);
release the second configuration so that the UE is no longer configured to utilize the second set of additional functions (Kim: paragraph 0160 & Fig. 13, target sends a RRC Reconfiguration message (including daps-SourceRelease field) for UE to stop data transmission or reception with the source base station, thus teaching the UE no longer utilizes the DAPS operation); and
communicate, via the RAN interface, with the second network node in accordance with the first configuration (Kim: paragraph 0160 & Fig. 13, data transmission and reception in downlink/uplink between UE and target cell).
Kim fails to explicitly teach the second configuration further includes at least one of a sidelink configuration or a reference time reporting configuration. However, Wu from an analogous art similarly teaches a DAPS handover procedure wherein a UE transmits a RRC reconfiguration information for a sidelink communication with another UE (Wu: paragraphs 0110-0112 & Figs. 4A-4B)
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 Kim to include sidelink configurations for DAPS handover as taught by Wu so as to utilize sidelink resources to facilitate a handover.
Regarding Claim 8, Kim teaches A method for managing configurations in a first network node (Kim: paragraph 0159 & Fig. 13, source base station or source cell) operating in a radio access network (RAN) (Kim: paragraph 0054 & Figs. 1-2, wireless access network), the method comprising:
communicating, by the first network node, with a user equipment (UE) (Kim: paragraphs 0158-0160 & Fig. 13, terminal or user equipment) according to (i) a first configuration (Kim: paragraph 0159, (non-DAPS)) configuration or normal handover operation) configuring the UE to utilize a first set of functions (Kim: paragraph 0159, said normal handover operation) and (ii) a second configuration (Kim: paragraphs 0159-0160 & Fig. 13, DAPS related configuration) supplementing the first configuration configuring the UE to utilize a second set of additional functions (Kim: paragraph 0159-160 & Fig. 13, DAPS-related configuration information (in addition to normal configuration) for DAPS handover procedure);
determining, by the first network node, that the UE is to communicate (Kim: paragraphs 0158-0160 & Fig. 13, handover procedure to target cell) with a second network node operating in the RAN (Kim: paragraphs 0159-0160 & Fig. 13, target base station or target cell);
in response to determining that the second network node does not support the second set of additional functions (Kim: paragraph 0159 & Fig. 13, required configuration information operation (normal configuration or non-DAPS) to the target cell, thus teaching the target supports only the first configuration; see also paragraph 0160, UE maintaining connection with source cell for which DAPS is configured), transmitting the first configuration to the second network node and preventing the second configuration from being transmitted to the second network node (Kim: paragraphs 0158-0160 & Fig. 13, normal handover procedure to target cell, thus teaching the DAPS handover is prevented or not transmitted to the target cell).
Kim fails to explicitly teach the second configuration further includes at least one of a sidelink configuration or a reference time reporting configuration. However, Wu from an analogous art similarly teaches a DAPS handover procedure wherein a UE transmits a RRC reconfiguration information for a sidelink communication with another UE (Wu: paragraphs 0110-0112 & Figs. 4A-4B)
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 Kim to include sidelink configurations for DAPS handover as taught by Wu so as to utilize sidelink resources to facilitate a handover.
Regarding Claim 9, Kim-Wu teaches the respective claim(s) as presented above and further teaches determining that first network node is to transmit handover preparation information to the second network node (Kim: paragraphs 0158-0160, handover procedure from source cell to target cell).
Regarding Claim 15, Kim teaches A base station (Kim: paragraph 0159 & Fig. 13, source base station or source cell) operating in a radio access network (RAN) (Kim: paragraph 0054 & Figs. 1-2, wireless access network), that includes a first network node (Kim: paragraph 0159 & Fig. 13, said source base station or source cell) and a second network node Kim: paragraphs 0159-0160 & Fig. 13, target base station or target cell), the base station being the first network node (Kim: paragraph 0159 & Fig. 13, source base station or source cell) and comprising:
a Radio Resource Control (RRC) controller (Kim: paragraph 0195 & Fig. 17, controller); and
a RAN interface (Kim: paragraph 0197 & Fig. 17, RF processor),
the RRC controller being configured to:
communicate, via the RAN interface, with a user equipment (UE) (Kim: paragraphs 0158-0160 & Fig. 13, terminal or user equipment) according to (i) a first configuration (Kim: paragraph 0159, (non-DAPS)) configuration or normal handover operation) configuring the UE to utilize a first set of functions (Kim: paragraph 0159, said normal handover operation), and (ii) a second configuration (Kim: paragraphs 0159-0160 & Fig. 13, DAPS related configuration) supplementing the first configuration and configuring the UE to utilize a second set of additional functions (Kim: paragraph 0159-160 & Fig. 13, DAPS-related configuration information (in addition to normal configuration) for DAPS handover procedure);
determine that the UE is to communicate (Kim: paragraphs 0158-0160 & Fig. 13, handover procedure to target cell) with a second network node operating in the RAN (Kim: paragraphs 0159-0160 & Fig. 13, target base station or target cell); and
in response to a determination that the second network node does not support the second set of additional functions (Kim: paragraph 0159 & Fig. 13, required configuration information operation (normal configuration or non-DAPS) to the target cell, thus teaching the target supports only the first configuration; see also paragraph 0160, UE maintaining connection with source cell for which DAPS is configured), transmit the first configuration to the second network node and prevent the second configuration from being transmitted to the second network node (Kim: paragraphs 0158-0160 & Fig. 13, normal handover procedure to target cell, thus teaching the DAPS handover is prevented or not transmitted to the target cell).
Kim fails to explicitly teach the second configuration further includes at least one of a sidelink configuration or a reference time reporting configuration. However, Wu from an analogous art similarly teaches a DAPS handover procedure wherein a UE transmits a RRC reconfiguration information for a sidelink communication with another UE (Wu: paragraphs 0110-0112 & Figs. 4A-4B)
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 Kim to include sidelink configurations for DAPS handover as taught by Wu so as to utilize sidelink resources to facilitate a handover.
Regarding Claim 16, Kim-Wu teaches the respective claim(s) as presented above and further teaches the first network node is to transmit handover preparation information to the second network node (Kim: paragraphs 0158-0160, handover procedure from source cell to target cell).
Regarding Claim 18, Kim-Wu teaches the respective claim(s) as presented above and further teaches a computer-readable medium storing machine-readable instructions that, when executed by the RRC controller (Kim: paragraph 0321, computer readable storage medium implementation executing a processor) cause the RRC controller to:
communicate with the user equipment (UE) according to (i) the first configuration (Kim: paragraph 0159, (non-DAPS)) configuration or normal handover operation) and (ii) the second configuration (Kim: paragraphs 0159-0160 & Fig. 13, DAPS related configuration);
determine that the UE is to communicate with the second network node (Kim: paragraphs 0159-0160 & Fig. 13, target base station or target cell); and
in response to the determination that the second node does not support the second set of additional functions (Kim: paragraph 0159 & Fig. 13, required configuration information operation (normal configuration or non-DAPS) to the target cell, thus teaching the target supports only the first configuration; see also paragraph 0160, UE maintaining connection with source cell for which DAPS is configured), transmit the first configuration to the second network node and prevent the second configuration from being transmitted to the second network node (Kim: paragraphs 0158-0160 & Fig. 13, normal handover procedure to target cell, thus teaching the DAPS handover is prevented or not transmitted to the target cell).
Regarding Claim 20, Kim-Wu teaches the respective claim(s) as presented above and further teaches a computer-readable medium storing machine-readable instructions that, when executed by the RRC controller (Kim: paragraph 0321, computer readable storage medium implementation executing a processor), cause the RRC controller to:
receive, from the first network node (Kim: paragraph 0159 & Fig. 13, source base station or source cell), (i) the first configuration (Kim: paragraph 0159, (non-DAPS)) configuration or normal handover operation), and (ii) the second configuration (Kim: paragraphs 0159-0160 & Fig. 13, DAPS related configuration);
determine that the UE is to re-establish the radio connection with the RAN via the second network node (Kim: paragraphs 0158-0160 & Fig. 13, handover procedure to target cell);
release the second configuration so that the UE is no longer configured to utilize the second set of additional functions (Kim: paragraph 0160 & Fig. 13, target sends a RRC Reconfiguration message (including daps-SourceRelease field) for UE to stop data transmission or reception with the source base station, thus teaching the UE no longer utilizes the DAPS operation); and
communicate with the second network node in accordance with the first configuration (Kim: paragraph 0160 & Fig. 13, data transmission and reception in downlink/uplink between UE and target cell).
Regarding Claim 21, Kim-Wu teaches the respective claim(s) as presented above and further teaches wherein the UE releases the second configuration prior to re-establishing the radio connection with the second network node (Kim: paragraph 0160 & Fig. 13, target sends a RRC Reconfiguration message (including daps-SourceRelease field) for UE to stop data transmission or reception with the source base station).
Regarding Claim 24, Kim-Wu teaches the respective claim(s) as presented above and further teaches transmit the first configuration to the second network node and prevent the second configuration from being transmitted to the second network node in response to the determination that the second node does not support the second set of additional functions (Kim: paragraphs 0158-0160 & Fig. 13, normal handover procedure to target cell, thus teaching the DAPS handover is prevented or not transmitted to the target cell).
Regarding Claim 25, Kim-Wu teaches the respective claim(s) as presented above and further teaches wherein the UE releases the second configuration in response to detecting a communication failure with the first network node (Kim: paragraphs 0158-0160, handover procedure from source cell to target cell, thus detecting a failure with a communication or link with the source cell).
Regarding Claim 26, Kim-Wu teaches the respective claim(s) as presented above and further teaches wherein the UE releases the second configuration in response to the determination that the UE is to re-establish the radio connection with the second network node (Kim: paragraph 0160 & Fig. 13, target sends a RRC Reconfiguration message (including daps-SourceRelease field) for UE to stop data transmission or reception with the source base station).
Regarding Claim 27, Kim-Wu teaches the respective claim(s) as presented above and further teaches wherein the UE communicates with the second network node using the first configuration after the UE re-establishes the radio connection with the second network (Kim: paragraph 0160 & Fig. 13, target sends a RRC Reconfiguration message (including daps-SourceRelease field) for UE to stop data transmission or reception with the source base station).
Response to Arguments
Applicant’s arguments with respect to amended claims 1, 7, 8 and 15 have been considered but are moot in view of the new ground(s) of rejection.
Conclusion
Any inquiry concerning this communication or earlier communications from the examiner should be directed to NAJEEB ANSARI whose telephone number is (571)270-5446. The examiner can normally be reached Monday-Friday 10am to 2pm.
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, ASAD NAWAZ can be reached at (571) 272-3988. 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.
/NAJEEB ANSARI/Examiner, Art Unit 2463
/ASAD M NAWAZ/Supervisory Patent Examiner, Art Unit 2463
Prosecution Insights