DETAILED ACTION
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 .
Priority
The instant application is a National Stage entry of PCT/KR2023/022023, International Filing Date: 12/29/2023, claims foreign priority to Indian patent application 202341000118, filed 01/02/2023, claims foreign priority to Indian patent application 2023 41000118, filed 12/05/2023.
Claim Rejections - 35 USC § 112
The following is a quotation of 35 U.S.C. 112(b):
(b) CONCLUSION.—The specification shall conclude with one or more claims particularly pointing out and distinctly claiming the subject matter which the inventor or a joint inventor regards as the invention.
The following is a quotation of 35 U.S.C. 112 (pre-AIA ), second paragraph:
The specification shall conclude with one or more claims particularly pointing out and distinctly claiming the subject matter which the applicant regards as his invention.
Claims 1-15 are rejected under 35 U.S.C. 112(b) or 35 U.S.C. 112 (pre-AIA ), second paragraph, as being indefinite for failing to particularly point out and distinctly claim the subject matter which the inventor or a joint inventor (or for applications subject to pre-AIA 35 U.S.C. 112, the applicant), regards as the invention.
As to claim 1, the claim recites the limitation “indicating at least one no recommendation should be given”. The limitation renders the claim indefinite because it is not clear what the applicant intended to limit by “one no recommendation…”. The examiner suggests rephrasing the limitation to make it clear.
As to claims 5, 9 and 13, the claims are also rejected for the same reason of claim 1 above.
As to claim 4, the claim additionally recites the limitations “of the starting time attribute, the stopping time attribute, or the scope associated with the analytics”. There is insufficient antecedent basis for the limitations in the claim.
As to the claim(s) that are dependent on claim(s) 1, 5, 9 or 13, the dependent claim(s) are also rejected under 112(b) for the same reason of their base claim(s).
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.
Claim(s) 1-3, 5-7, 9-11 and 13-14 is/are rejected under 35 U.S.C. 102(a)(2) as being anticipated by Khare et al. (Pub. No.: US 20230065199 A1).
As to claim 1, Khare teaches a method performed by a management data analytics (MDA) consumer in a wireless communication system, the method comprising:
identifying a filter associated with a list of distinguished names (DNs) indicating at least one no recommendation should be given (paragraph [0161], “the MDAS consumer, which may be the OAM 500, may request analytics with particular conditions. The conditions may for example include particular reporting times, filters etc. from the MDAS MnS producer 502 for a particular NF or NF chain providing the range of timers and the flow ID” and paragraph [0177]);
transmitting, to a MDA producer, a request message including the filter (paragraph [0161], “the MDAS consumer, which may be the OAM 500, may request analytics with particular conditions. The conditions may for example include particular reporting times, filters etc…”); and
receiving, from the MDA producer, as a response to the request message, a report message including at least one recommendation identified based on the filter (paragraph [0176], “…The output may be provided when the conditions (e.g. the reporting times, filters etc.) set by the OAM are met. The output may comprise one or more recommended timer adjustments for one or more timers associated with a NF or site or inter-site communications …” and fig. 5).
As to claim 2, Khare teaches wherein the request message further includes at least one of a starting time attribute, a stopping time attribute, or a scope associated with an analytics (paragraph [0110], “NF1 sends a service request to NF2 and starts e.g. 5 seconds this timer ”).
As to claim 3, Khare teaches wherein the request message further includes at least one disallowed management object instance (MOI) (paragraph [0162], “the request may comprise a Management Object Instance (MOI). The MOI contain different parameters which may enable the OAM 500 to request the particular capabilities of the analytics”).
As to claim 5, Khare teaches a method performed by a management data analytics (MDA) producer in a wireless communication system, the method comprising:
receiving, from a MDA consumer, a request message including a filter associated with a list of distinguished names (DNs) indicating at least one no recommendation should be given (paragraph [0161], “the MDAS consumer, which may be the OAM 500, may request analytics with particular conditions. The conditions may for example include particular reporting times, filters etc. from the MDAS MnS producer 502 for a particular NF or NF chain providing the range of timers and the flow ID” and paragraph [0177]);
identifying at least one recommendation based on the filter (paragraph [0161], “the MDAS consumer, which may be the OAM 500, may request analytics with particular conditions. The conditions may for example include particular reporting times, filters etc…”); and
transmitting, to the MDA producer, as a response to the request message, a report message including the at least one recommendation (paragraph [0176], “…The output may be provided when the conditions (e.g. the reporting times, filters etc.) set by the OAM are met. The output may comprise one or more recommended timer adjustments for one or more timers associated with a NF or site or inter-site communications …” and fig. 5).
As to claim 6, Khare teaches wherein the request message further includes at least one of a starting time attribute, a stopping time attribute, or a scope associated with an analytics (paragraph [0110], “NF1 sends a service request to NF2 and starts e.g. 5 seconds this timer ”).
As to claim 7, Khare teaches wherein the request message further includes at least one disallowed management object instance (MOI) (paragraph [0162], “the request may comprise a Management Object Instance (MOI). The MOI contain different parameters which may enable the OAM 500 to request the particular capabilities of the analytics”).
As to claim 9, Khare teaches A management data analytics (MDA) consumer in a wireless communication system, comprising: a transceiver; and a controller coupled with the transceiver (fig. 3), the controller configured to:
identify a filter associated with a list of distinguished names (DNs) indicating at least one no recommendation should be given (paragraph [0161], “the MDAS consumer, which may be the OAM 500, may request analytics with particular conditions. The conditions may for example include particular reporting times, filters etc. from the MDAS MnS producer 502 for a particular NF or NF chain providing the range of timers and the flow ID” and paragraph [0177]),
transmit, to a MDA producer, a request message including the filter (paragraph [0161], “the MDAS consumer, which may be the OAM 500, may request analytics with particular conditions. The conditions may for example include particular reporting times, filters etc…”), and
receive, from the MDA producer, as a response to the request message, a report message including at least one recommendation identified based on the filter (paragraph [0176], “…The output may be provided when the conditions (e.g. the reporting times, filters etc.) set by the OAM are met. The output may comprise one or more recommended timer adjustments for one or more timers associated with a NF or site or inter-site communications …” and fig. 5).
As to claim 10, Khare teaches wherein the request message further includes at least one of a starting time attribute, a stopping time attribute, or a scope associated with an analytics (paragraph [0110], “NF1 sends a service request to NF2 and starts e.g. 5 seconds this timer ”).
As to claim 11, Khare teaches wherein the request message further includes at least one disallowed management object instance (MOI) (paragraph [0162], “the request may comprise a Management Object Instance (MOI). The MOI contain different parameters which may enable the OAM 500 to request the particular capabilities of the analytics”).
As to claim 13, Khare teaches A management data analytics (MDA) producer in a wireless communication system, comprising: a transceiver; and a controller coupled with the transceiver (fig. 3), the controller configured to:
receive, from a MDA consumer, a request message including a filter associated with a list of distinguished names (DNs) indicating at least one no recommendation should be given (paragraph [0161], “the MDAS consumer, which may be the OAM 500, may request analytics with particular conditions. The conditions may for example include particular reporting times, filters etc. from the MDAS MnS producer 502 for a particular NF or NF chain providing the range of timers and the flow ID” and paragraph [0177]),
identify at least one recommendation based on the filter (paragraph [0161], “the MDAS consumer, which may be the OAM 500, may request analytics with particular conditions. The conditions may for example include particular reporting times, filters etc…”), and
transmit, to the MDA consumer, as a response to the request message, a report message including the at least one recommendation (paragraph [0176], “…The output may be provided when the conditions (e.g. the reporting times, filters etc.) set by the OAM are met. The output may comprise one or more recommended timer adjustments for one or more timers associated with a NF or site or inter-site communications …” and fig. 5).
As to claim 14, Khare teaches wherein the request message further includes at least one of a starting time attribute, a stopping time attribute, or a scope associated with an analytics (paragraph [0110], “NF1 sends a service request to NF2 and starts e.g. 5 seconds this timer”).
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) 4, 8, 12 and 15 is/are rejected under 35 U.S.C. 103 as being unpatentable over Khare et al. (Pub. No.: US 20230065199 A1) in view of ETSI TS 128 536 V14.4.1 (“TS” hereinafter, TS was cited in the IDS dated 4/17/2026).
As to claim 4, Khare does not explicitly teach attributes determined based on assurance goal.
However, in the same field of endeavor (communication networks) TS teaches at least one of the starting time attribute, the stopping time attribute, or the scope associated with the analytics is determined based on an assurance goal (pg. 17, “observationTime”).
Based on Khare in view of TS, it would have been obvious to a person of ordinary skill in the art, before the effective filing date of the claimed invention, to incorporate attributes determined based on assurance goal (taught by TS) with network data analytics (taught by Khare) in order to continuously deliver the requested level of communication service quality to the consumer as motivated by TS (pg. 6).
As to claims 8, the limitations of the claim are substantially similar to claim 4. Please refer to claim 4 above
As to claims 12, the limitations of the claim are substantially similar to claim 4. Please refer to claim 4 above
As to claim 15, Khare teaches wherein the request message further includes at least one disallowed management object instance (MOI) (paragraph [0162], “the request may comprise a Management Object Instance (MOI). The MOI contain different parameters which may enable the OAM 500 to request the particular capabilities of the analytics”).
Khare does not explicitly teach attributes determined based on assurance goal.
However, in the same field of endeavor (communication networks) TS teaches at least one of the starting time attribute, the stopping time attribute, or the scope associated with the analytics is determined based on an assurance goal (pg. 17, “observationTime”).
Based on Khare in view of TS, it would have been obvious to a person of ordinary skill in the art, before the effective filing date of the claimed invention, to incorporate attributes determined based on assurance goal (taught by TS) with network data analytics (taught by Khare) in order to continuously deliver the requested level of communication service quality to the consumer as motivated by TS (pg. 6).
Conclusion
Any inquiry concerning this communication or earlier communications from the examiner should be directed to ABDULKADER M ALRIYASHI whose telephone number is (313)446-6551. The examiner can normally be reached Monday - Friday, 8AM - 5PM Alt, Friday, EST.
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, JOON HWANG can be reached at (571)272-4036. 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.
/Abdulkader M Alriyashi/Primary Examiner, Art Unit 2447 7/25/2026
Prosecution Insights