DETAILED ACTION
Claim(s) 1-20 are presented 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 .
Claim Rejections - 35 U.S.C. § 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 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.
Claim(s) 1-20 are rejected under 35 U.S.C. § 103 as being unpatentable over Sun et al. (US 2021/0084173 A1) hereinafter “Sun” in view of IANEV et al. (US 2022/0070963 A1) hereinafter “Ianev”.
Regarding Claims 1 and 9,
Sun discloses a network device [see fig(s). 7 & 11, pg. 16, ¶278 lines 1-5, a policy control function (PCF) network element (i.e. V-PCF/H-PCF) “1100”] comprising:
a processor [see fig(s). 7 & 11, pg. 16, ¶278 lines 1-5, a processor “1101”], wherein the processor is configured to [see fig(s). 7 & 11, pg. 16, ¶278 lines 1-5, the processor “1101” implemented to]:
receive [see fig. 7: Step “730”, pg. 14, ¶234 lines 1-4; ¶235 lines 1-5, receiving], from a second network device [see fig. 7: Step “730”, pg. 14, ¶234 lines 1-4; ¶235 lines 1-5, from a network data analytics function (NWDAF)], network information [see fig. 7: Step “730”, pg. 14, ¶234 lines 1-4; ¶235 lines 1-5, an analytics information request response that is fed back to the V-PCF/H-PCF], generated by the second network device that pertains to an end device [see fig. 7: Step “730”, pg. 14, ¶234 lines 1-4; ¶235 lines 1-5, based on a request that is for the time in which the UE enters the connected mode and that is sent by the V-PCF/H-PCF, the time (timeline) in which the UE enters the connected mode];
generate [see fig. 7: Step “740”, pg. 14, ¶236 lines 1-2; ¶239 lines 1-6, the V-PCF/H-PCF makes], based on the network information [see fig. 7: Step “740”, pg. 14, ¶236 lines 1-2; ¶239 lines 1-6, in the time period in which the terminal apparatus is in the connected mode], updated parameters pertaining to the end device that differ from the parameters [see fig. 7: Step “740”, pg. 14, ¶236 lines 1-2; ¶239 lines 1-6, a policy decision to deliver a UE policy rule to the terminal apparatus]; and
transmit [see fig. 7: Step “750”, pg. 14, ¶237 lines 1-3, the V-PCF/H-PCF sends], to a first network device [see fig. 7: Step “750”, pg. 14, ¶237 lines 1-3, to an access and mobility management function (AMF)], the updated parameters [see fig. 7: Step “750”, pg. 14, ¶237 lines 1-3, a policy control update request response (AM policy control update response)].
Although Sun discloses transmit, to the first network device, the updated parameters, Sun does not explicitly teach transmit “extended discontinuous reception (eDRX) parameters pertaining to an end device, to a first network device”.
However Ianev discloses transmitting [see fig. 4: Step “4”, pg. 5, ¶85 lines 1-7, notifying], by a network device [see fig. 4: Step “4”, pg. 5, ¶85 lines 1-7, by a policy control function (PCF) “740”], extended discontinuous reception (eDRX) parameters pertaining to an end device [see fig. 4: Step “4”, pg. 5, ¶85 lines 1-7, with the updated version of the User Equipment Analytics Reporting Policy (UEARP) parameter for UE “3”], to a first network device [see fig. 4: Step “4”, pg. 5, ¶85 lines 1-7, to an access and mobility management function (AMF) “710”];
receiving [see fig. 4: Step “7”, pg. 5, ¶92 lines 1-6; ¶93 lines 1-5, receiving], by the network device from a second network device [see fig. 4: Step “7”, pg. 5, ¶92 lines 1-6; ¶93 lines 1-5, by the PCF “740” from the NWDAF “720”], network information [see fig. 4: Step “7”, pg. 5, ¶92 lines 1-6; ¶93 lines 1-5, the UEARP analytics or with a proposal for the UEARP], generated by the second network device that pertains to the end device [see fig. 4: Step “7”, pg. 5, ¶92 lines 1-6; ¶93 lines 1-5, invoked by a “Nnwdaf_AnalyticInfo_Response” procedure … including the parameter(s) of: UE identity (UE ID), UEARP, etc. … for which the analytics information is provided by the NWDAF “720” in the “Nnwdaf_AnalyticsInfo_Response” message];
generating [see fig. 4: Step “8”, pg. 5, ¶95 lines 1-10, updating], by the network device based on the network information [see fig. 4: Step “8”, pg. 5, ¶95 lines 1-10, by the PCF “740” based on the NWDAF proposed analytics result about the UEARP (or an UEARP proposal), UE subscription information and any available relevant operator policies], updated eDRX parameters pertaining to the end device that differ from the eDRX parameters [see fig. 4: Step “8”, pg. 5, ¶95 lines 1-10, the UE's UEARP]; and
transmitting [see fig. 4: Step “9”, pg. 5, ¶96 lines 1-5, responding, by sending], by the network device to the first network device [see fig. 4: Step “9”, pg. 5, ¶96 lines 1-5, by the PCF “740” to the AMF “710”], the updated eDRX parameters [see fig. 4: Step “9”, pg. 5, ¶96 lines 1-5, the updated (if any) UEARP].
Therefore, it would have been obvious to one having ordinary skill in the art before the effective filing date of the claimed invention to provide transmit “extended discontinuous reception (eDRX) parameters pertaining to an end device, to a first network device” as taught by Ianev in the system of Sun to improve and optimize mobility and connection management of a UE by providing the UE with: Per UE customized DRX/eDRX and PSM [see Ianev, pg. 6, ¶106 lines 1-4; ¶107 line 1].
Regarding Claims 2 and 10,
The combined system of Sun and Ianev discloses the network device of claim 9.
Sun further discloses wherein the network information pertains to congestion of a radio access network device to which the end device is connected [see fig. 7: Step “730”, pg. 14, ¶234 lines 1-4; ¶235 lines 1-5, the analytics information request response carries a timeline (analytics Info response (timeline))].
Regarding Claims 3 and 11,
The combined system of Sun and Ianev discloses the network device of claim 9.
Sun further discloses wherein the second network device includes a network data analytics function (NWDAF) [see fig. 7: Step “730”, pg. 14, ¶234 lines 1-4; ¶235 lines 1-5, the NWDAF feeds back an analytics information request response to the V-PCF/H-PCF].
Regarding Claims 4 and 12,
The combined system of Sun and Ianev discloses the network device of claim 9.
Sun further discloses wherein the network information pertains to data usage associated with the end device [see fig. 7: Step “730”, pg. 14, ¶234 lines 1-4; ¶235 lines 1-5, the NWDAF sends to the V-PCF/H-PCF based on a request that is for the time in which the UE enters the connected mode and that is sent by the V-PCF/H-PCF, the time (timeline) in which the UE enters the connected mode].
Regarding Claims 5 and 13,
Sun discloses the network device of claim 9.
Sun does not explicitly teach “the second network device includes a charging function”.
However Ianev discloses the second network device includes a charging function [see fig. 4, pg. 5, ¶85 lines 1-7, a policy (charging) control function (PCF) “740”].
Therefore, it would have been obvious to one having ordinary skill in the art before the effective filing date of the claimed invention to provide “the second network device includes a charging function” as taught by Ianev in the system of Sun for the same motivation as set forth in claim 9.
Regarding Claims 6 and 14,
Sun discloses the network device of claim 9.
Sun does not explicitly teach wherein the processor is further configured to: “obtain subscription information that includes the eDRX parameters”.
However Ianev discloses obtain subscription information that includes the eDRX parameters [see fig. 4: Step “4”, pg. 5, ¶83 lines 1-7, the PCF “740” subscribes for analytical results information from the NWDAF “720” and uses a UEARP parameter to set up the types of analytics it is subscribing to].
Therefore, it would have been obvious to one having ordinary skill in the art before the effective filing date of the claimed invention to provide “obtain subscription information that includes the eDRX parameters” as taught by Ianev in the system of Sun for the same motivation as set forth in claim 9.
Regarding Claims 7 and 15,
Sun discloses the network device of claim 9.
Sun does not explicitly teach wherein the processor is further configured to: “generate, based on the network information and rules for calculating the updated eDRX parameters, the updated eDRX parameters”.
However Ianev discloses generate [see fig. 4: Step “8”, pg. 5, ¶95 lines 1-10, updating], based on the network information and rules for calculating the updated eDRX parameters [see fig. 4: Step “8”, pg. 5, ¶95 lines 1-10, by the PCF “740” based on the NWDAF proposed analytics result about the UEARP (or an UEARP proposal), UE subscription information and any available relevant operator policies], the updated eDRX parameters [see fig. 4: Step “8”, pg. 5, ¶95 lines 1-10, the UE's UEARP].
Therefore, it would have been obvious to one having ordinary skill in the art before the effective filing date of the claimed invention to provide “generate, based on the network information and rules for calculating the updated eDRX parameters, the updated eDRX parameters” as taught by Ianev in the system of Sun for the same motivation as set forth in claim 9.
Regarding Claims 8 and 16,
The combined system of Sun and Ianev discloses the network device of claim 9.
Sun further discloses wherein the network device comprises a policy control function (PCF) [see fig(s). 7 & 11, pg. 16, ¶278 lines 1-5, a policy control function (PCF) network element (i.e. V-PCF/H-PCF) “1100”].
Regarding Claim 17,
Sun discloses a non-transitory computer-readable storage medium storing instructions executable by a processor of a network device [see fig(s). 7 & 11, pg. 16, ¶278 lines 1-5, a memory “1104” configured to store program code and data to be implemented by a processor “1101” of a network device “1100”], wherein the instructions are configured to [see fig(s). 7 & 11, pg. 16, ¶278 lines 1-5, the stored program code implemented to]:
receive [see fig. 7: Step “730”, pg. 14, ¶234 lines 1-4; ¶235 lines 1-5, receiving], from a second network device [see fig. 7: Step “730”, pg. 14, ¶234 lines 1-4; ¶235 lines 1-5, from a network data analytics function (NWDAF)], network information [see fig. 7: Step “730”, pg. 14, ¶234 lines 1-4; ¶235 lines 1-5, an analytics information request response that is fed back to the V-PCF/H-PCF], generated by the second network device that pertains to an end device [see fig. 7: Step “730”, pg. 14, ¶234 lines 1-4; ¶235 lines 1-5, based on a request that is for the time in which the UE enters the connected mode and that is sent by the V-PCF/H-PCF, the time (timeline) in which the UE enters the connected mode];
generate [see fig. 7: Step “740”, pg. 14, ¶236 lines 1-2; ¶239 lines 1-6, the V-PCF/H-PCF makes], based on the network information [see fig. 7: Step “740”, pg. 14, ¶236 lines 1-2; ¶239 lines 1-6, in the time period in which the terminal apparatus is in the connected mode], updated parameters pertaining to the end device that differ from the parameters [see fig. 7: Step “740”, pg. 14, ¶236 lines 1-2; ¶239 lines 1-6, a policy decision to deliver a UE policy rule to the terminal apparatus]; and
transmit [see fig. 7: Step “750”, pg. 14, ¶237 lines 1-3, the V-PCF/H-PCF sends], to a first network device [see fig. 7: Step “750”, pg. 14, ¶237 lines 1-3, to an access and mobility management function (AMF)], the updated parameters [see fig. 7: Step “750”, pg. 14, ¶237 lines 1-3, a policy control update request response (AM policy control update response)].
Although Sun discloses transmit, to the first network device, the updated parameters, Sun does not explicitly teach transmit “extended discontinuous reception (eDRX) parameters pertaining to an end device, to a first network device”.
However Ianev discloses transmitting [see fig. 4: Step “4”, pg. 5, ¶85 lines 1-7, notifying], by a network device [see fig. 4: Step “4”, pg. 5, ¶85 lines 1-7, by a policy control function (PCF) “740”], extended discontinuous reception (eDRX) parameters pertaining to an end device [see fig. 4: Step “4”, pg. 5, ¶85 lines 1-7, with the updated version of the User Equipment Analytics Reporting Policy (UEARP) parameter for UE “3”], to a first network device [see fig. 4: Step “4”, pg. 5, ¶85 lines 1-7, to an access and mobility management function (AMF) “710”];
receiving [see fig. 4: Step “7”, pg. 5, ¶92 lines 1-6; ¶93 lines 1-5, receiving], by the network device from a second network device [see fig. 4: Step “7”, pg. 5, ¶92 lines 1-6; ¶93 lines 1-5, by the PCF “740” from the NWDAF “720”], network information [see fig. 4: Step “7”, pg. 5, ¶92 lines 1-6; ¶93 lines 1-5, the UEARP analytics or with a proposal for the UEARP], generated by the second network device that pertains to the end device [see fig. 4: Step “7”, pg. 5, ¶92 lines 1-6; ¶93 lines 1-5, invoked by a “Nnwdaf_AnalyticInfo_Response” procedure … including the parameter(s) of: UE identity (UE ID), UEARP, etc.. for which the analytics information is provided by the NWDAF “720” in the “Nnwdaf_AnalyticsInfo_Response” message …];
generating [see fig. 4: Step “8”, pg. 5, ¶95 lines 1-10, updating], by the network device based on the network information [see fig. 4: Step “8”, pg. 5, ¶95 lines 1-10, by the PCF “740” based on the NWDAF proposed analytics result about the UEARP (or an UEARP proposal), UE subscription information and any available relevant operator policies], updated eDRX parameters pertaining to the end device that differ from the eDRX parameters [see fig. 4: Step “8”, pg. 5, ¶95 lines 1-10, the UE's UEARP]; and
transmitting [see fig. 4: Step “9”, pg. 5, ¶96 lines 1-5, responding, by sending], by the network device to the first network device [see fig. 4: Step “9”, pg. 5, ¶96 lines 1-5, by the PCF “740” to the AMF “710”], the updated eDRX parameters [see fig. 4: Step “9”, pg. 5, ¶96 lines 1-5, the updated (if any) UEARP].
Therefore, it would have been obvious to one having ordinary skill in the art before the effective filing date of the claimed invention to provide transmit “extended discontinuous reception (eDRX) parameters pertaining to an end device, to a first network device” as taught by Ianev in the system of Sun to improve and optimize mobility and connection management of a UE by providing the UE with: Per UE customized DRX/eDRX and PSM [see Ianev, pg. 6, ¶106 lines 1-4; ¶107 line 1].
Regarding Claim 18,
The combined system of Sun and Ianev discloses the non-transitory computer-readable storage medium of claim 17.
Sun further discloses wherein the network information pertains to congestion of a radio access network device to which the end device is connected [see fig. 7: Step “730”, pg. 14, ¶234 lines 1-4; ¶235 lines 1-5, the analytics information request response carries a timeline (analytics Info response (timeline))].
Regarding Claim 19,
Sun discloses the non-transitory computer-readable storage medium of claim 17.
Sun does not explicitly teach wherein the instructions are further configured to: “generate, based on the network information and rules for calculating the updated eDRX parameters, the updated eDRX parameters”.
However Ianev discloses generate [see fig. 4: Step “8”, pg. 5, ¶95 lines 1-10, updating], based on the network information and rules for calculating the updated eDRX parameters [see fig. 4: Step “8”, pg. 5, ¶95 lines 1-10, by the PCF “740” based on the NWDAF proposed analytics result about the UEARP (or an UEARP proposal), UE subscription information and any available relevant operator policies], the updated eDRX parameters [see fig. 4: Step “8”, pg. 5, ¶95 lines 1-10, the UE's UEARP].
Therefore, it would have been obvious to one having ordinary skill in the art before the effective filing date of the claimed invention to provide “generate, based on the network information and rules for calculating the updated eDRX parameters, the updated eDRX parameters” as taught by Ianev in the system of Sun for the same motivation as set forth in claim 17.
Regarding Claim 20,
The combined system of Sun and Ianev discloses the non-transitory computer-readable storage medium of claim 17.
Sun further discloses wherein the network information pertains to data usage associated with the end device [see fig. 7: Step “730”, pg. 14, ¶234 lines 1-4; ¶235 lines 1-5, the NWDAF sends to the V-PCF/H-PCF based on a request that is for the time in which the UE enters the connected mode and that is sent by the V-PCF/H-PCF, the time (timeline) in which the UE enters the connected mode].
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure.
United States Patent Application Publication: Pan et al. (US 2024/0314696 A1); see fig. 2, pgs. 6-8, ¶88-¶138.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to RUSHIL P SAMPAT whose telephone number is (469) 295-9141. The examiner can normally be reached on Mon-Fri (8 AM - 5 PM).
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, Ian Moore can be reached on (571) 272-3085. 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 https://ppair-my.uspto.gov/pair/PrivatePair. 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.
/RUSHIL P. SAMPAT/Primary Examiner- TC 2400, Art Unit 2469