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 .
Claim Interpretation
The following is a quotation of 35 U.S.C. 112(f):
(f) Element in Claim for a Combination. – An element in a claim for a combination may be expressed as a means or step for performing a specified function without the recital of structure, material, or acts in support thereof, and such claim shall be construed to cover the corresponding structure, material, or acts described in the specification and equivalents thereof.
The following is a quotation of pre-AIA 35 U.S.C. 112, sixth paragraph:
An element in a claim for a combination may be expressed as a means or step for performing a specified function without the recital of structure, material, or acts in support thereof, and such claim shall be construed to cover the corresponding structure, material, or acts described in the specification and equivalents thereof.
The claims in this application are given their broadest reasonable interpretation using the plain meaning of the claim language in light of the specification as it would be understood by one of ordinary skill in the art. The broadest reasonable interpretation of a claim element (also commonly referred to as a claim limitation) is limited by the description in the specification when 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, is invoked.
As explained in MPEP § 2181, subsection I, claim limitations that meet the following three-prong test will be interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph:
(A) the claim limitation uses the term “means” or “step” or a term used as a substitute for “means” that is a generic placeholder (also called a nonce term or a non-structural term having no specific structural meaning) for performing the claimed function;
(B) the term “means” or “step” or the generic placeholder is modified by functional language, typically, but not always linked by the transition word “for” (e.g., “means for”) or another linking word or phrase, such as “configured to” or “so that”; and
(C) the term “means” or “step” or the generic placeholder is not modified by sufficient structure, material, or acts for performing the claimed function.
Use of the word “means” (or “step”) in a claim with functional language creates a rebuttable presumption that the claim limitation is to be treated in accordance with 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph. The presumption that the claim limitation is interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, is rebutted when the claim limitation recites sufficient structure, material, or acts to entirely perform the recited function.
Absence of the word “means” (or “step”) in a claim creates a rebuttable presumption that the claim limitation is not to be treated in accordance with 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph. The presumption that the claim limitation is not interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, is rebutted when the claim limitation recites function without reciting sufficient structure, material or acts to entirely perform the recited function.
Claim limitations in this application that use the word “means” (or “step”) are being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, except as otherwise indicated in an Office action. Conversely, claim limitations in this application that do not use the word “means” (or “step”) are not being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, except as otherwise indicated in an Office action.
This application includes one or more claim limitations that do not use the word “means,” but are nonetheless being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, because the claim limitation(s) uses a generic placeholder that is coupled with functional language without reciting sufficient structure to perform the recited function and the generic placeholder is not preceded by a structural modifier. Such claim limitation(s) is/are: “ first management apparatus, configured to determine … send …” and "data analysis apparatus activates or de-activates the data analysis function ..." and “a receiving apparatus, configured to receive the configuration information …performing data analysis … sending configuration information …” in claims 34-36.
Because this/these claim limitation(s) is/are being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, it/they is/are being interpreted to cover the corresponding structure described in the specification as performing the claimed function, and equivalents thereof.
If applicant does not intend to have this/these limitation(s) interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, applicant may: (1) amend the claim limitation(s) to avoid it/them being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph (e.g., by reciting sufficient structure to perform the claimed function); or (2) present a sufficient showing that the claim limitation(s) recite(s) sufficient structure to perform the claimed function so as to avoid it/them being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph. SEE ALSO MPEP 2181: Therefore, the broadest reasonable interpretation of a claim limitation that invokes 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, is the structure, material or act described in the specification as performing the entire claimed function and equivalents to the disclosed structure, material or act. As a result, section 112(f) or pre-AIA section 112, sixth paragraph, limitations will, in some cases, be afforded a more narrow interpretation than a limitation that is not crafted in "means plus function" format. See related 112a and 112b rejections below for details of written description analyses.
Claim Rejections - 35 USC § 112
The following is a quotation of the first paragraph of 35 U.S.C. 112(a):
(a) IN GENERAL.—The specification shall contain a written description of the invention, and of the manner and process of making and using it, in such full, clear, concise, and exact terms as to enable any person skilled in the art to which it pertains, or with which it is most nearly connected, to make and use the same, and shall set forth the best mode contemplated by the inventor or joint inventor of carrying out the invention.
The following is a quotation of the first paragraph of pre-AIA 35 U.S.C. 112:
The specification shall contain a written description of the invention, and of the manner and process of making and using it, in such full, clear, concise, and exact terms as to enable any person skilled in the art to which it pertains, or with which it is most nearly connected, to make and use the same, and shall set forth the best mode contemplated by the inventor of carrying out his invention.
Claims 34-36 are rejected under 35 U.S.C. 112(a) or 35 U.S.C. 112 (pre-AIA ), first paragraph, as failing to comply with the written description requirement. The claim(s) contains subject matter which was not described in the specification in such a way as to reasonably convey to one skilled in the relevant art that the inventor or a joint inventor, or for applications subject to pre-AIA 35 U.S.C. 112, the inventor(s), at the time the application was filed, had possession of the claimed invention.
Specifically, claim limitation(s) is/are: “ first management apparatus, configured to determine … send …” and "data analysis apparatus activates or de-activates the data analysis function ..." and “a receiving apparatus, configured to receive the configuration information …performing data analysis … sending configuration information …” in claims 34-36 invokes 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph. However, the written description fails to disclose the corresponding structure, material, or acts for performing the entire claimed function and to clearly link the structure, material, or acts to the function. Specifically, required structure to properly invoke 1112 is disclosed (see at least IFW: fig 10 processor(s) 1001, memory 1002, [0314]) for non-specialized functions of ‘receive’; however for all other specialized functions there are no algorithm(s) (at least two steps) for claimed limitation(s), at best, algorithm for claimed “determining” and “performing” Is disclosed (see IFW fig 2 & 5, [0133;136;147;202;208-211;305]); however, there are no other required algorithms (at least two steps) for other claimed functions of “first management apparatus to determine” and “receiving apparatus to perform.” For example disclosure merely discloses further details about the claimed configuration information – and a description of the configuration information is not an algorithm (at least 2 steps) and disclosure otherwise merely reiterates claim language (see IFW fig 2 & 5, [0133;136;147;202;208-211;305]) that is not an algorithm (at least two steps). Therefore, the written description is deficient.
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 34-36 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.
Claim limitation(s) is/are: “ first management apparatus, configured to determine … send …” and "data analysis apparatus activates or de-activates the data analysis function ..." and “a receiving apparatus, configured to receive the configuration information …performing data analysis … sending configuration information …” in claims 34-36 invokes 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph. However, the written description fails to disclose the corresponding structure, material, or acts for performing the entire claimed function and to clearly link the structure, material, or acts to the function. Specifically, required structure to properly invoke 1112 is disclosed (see at least IFW: fig 10 processor(s) 1001, memory 1002, [0314]) for non-specialized functions of ‘receive’; however for all other specialized functions there are no algorithm(s) (at least two steps) for claimed limitation(s), at best, algorithm for claimed “determining” and “performing” Is disclosed (see IFW fig 2 & 5, [0133;136;147;202;208-211;305]); however, there are no other required algorithms (at least two steps) for other claimed functions of “first management apparatus to determine” and “receiving apparatus to perform.” For example disclosure merely discloses further details about the claimed configuration information – and a description of the configuration information is not an algorithm (at least 2 steps) and disclosure otherwise merely reiterates claim language (see IFW fig 2 & 5, [0133;136;147;202;208-211;305])that is not an algorithm (at least two steps). Therefore, the claim is indefinite and is rejected under 35 U.S.C. 112(b) or pre-AIA 35 U.S.C. 112, second paragraph.
Applicant may:
(a) Amend the claim so that the claim limitation will no longer be interpreted as a limitation under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph;
(b) Amend the written description of the specification such that it expressly recites what structure, material, or acts perform the entire claimed function, without introducing any new matter (35 U.S.C. 132(a)); or
(c) Amend the written description of the specification such that it clearly links the structure, material, or acts disclosed therein to the function recited in the claim, without introducing any new matter (35 U.S.C. 132(a)).
If applicant is of the opinion that the written description of the specification already implicitly or inherently discloses the corresponding structure, material, or acts and clearly links them to the function so that one of ordinary skill in the art would recognize what structure, material, or acts perform the claimed function, applicant should clarify the record by either:
(a) Amending the written description of the specification such that it expressly recites the corresponding structure, material, or acts for performing the claimed function and clearly links or associates the structure, material, or acts to the claimed function, without introducing any new matter (35 U.S.C. 132(a)); or
(b) Stating on the record what the corresponding structure, material, or acts, which are implicitly or inherently set forth in the written description of the specification, perform the claimed function. For more information, see 37 CFR 1.75(d) and MPEP §§ 608.01(o) and 2181.
To overcome this/these rejection(s), applicant is encouraged to amend claims with substance equivalent to ‘A system, comprising: one or more processors executing instructions stored in memory to provide: first management apparatus ....’
Double Patenting
The nonstatutory double patenting rejection is based on a judicially created doctrine grounded in public policy (a policy reflected in the statute) so as to prevent the unjustified or improper timewise extension of the “right to exclude” granted by a patent and to prevent possible harassment by multiple assignees. A nonstatutory double patenting rejection is appropriate where the conflicting claims are not identical, but at least one examined application claim is not patentably distinct from the reference claim(s) because the examined application claim is either anticipated by, or would have been obvious over, the reference claim(s). See, e.g., In re Berg, 140 F.3d 1428, 46 USPQ2d 1226 (Fed. Cir. 1998); In re Goodman, 11 F.3d 1046, 29 USPQ2d 2010 (Fed. Cir. 1993); In re Longi, 759 F.2d 887, 225 USPQ 645 (Fed. Cir. 1985); In re Van Ornum, 686 F.2d 937, 214 USPQ 761 (CCPA 1982); In re Vogel, 422 F.2d 438, 164 USPQ 619 (CCPA 1970); In re Thorington, 418 F.2d 528, 163 USPQ 644 (CCPA 1969).
A timely filed terminal disclaimer in compliance with 37 CFR 1.321(c) or 1.321(d) may be used to overcome an actual or provisional rejection based on nonstatutory double patenting provided the reference application or patent either is shown to be commonly owned with the examined application, or claims an invention made as a result of activities undertaken within the scope of a joint research agreement. See MPEP § 717.02 for applications subject to examination under the first inventor to file provisions of the AIA as explained in MPEP § 2159. See MPEP § 2146 et seq. for applications not subject to examination under the first inventor to file provisions of the AIA . A terminal disclaimer must be signed in compliance with 37 CFR 1.321(b).
The filing of a terminal disclaimer by itself is not a complete reply to a nonstatutory double patenting (NSDP) rejection. A complete reply requires that the terminal disclaimer be accompanied by a reply requesting reconsideration of the prior Office action. Even where the NSDP rejection is provisional the reply must be complete. See MPEP § 804, subsection I.B.1. For a reply to a non-final Office action, see 37 CFR 1.111(a). For a reply to final Office action, see 37 CFR 1.113(c). A request for reconsideration while not provided for in 37 CFR 1.113(c) may be filed after final for consideration. See MPEP §§ 706.07(e) and 714.13.
The USPTO Internet website contains terminal disclaimer forms which may be used. Please visit www.uspto.gov/patent/patents-forms. The actual filing date of the application in which the form is filed determines what form (e.g., PTO/SB/25, PTO/SB/26, PTO/AIA /25, or PTO/AIA /26) should be used. A web-based eTerminal Disclaimer may be filled out completely online using web-screens. An eTerminal Disclaimer that meets all requirements is auto-processed and approved immediately upon submission. For more information about eTerminal Disclaimers, refer to www.uspto.gov/patents/apply/applying-online/eterminal-disclaimer.
Claims 18-36 are rejected on the ground of nonstatutory double patenting as being unpatentable over claims 1-19 of U.S. Patent No. 12,273,251. Although the claims at issue are not identical, they are not patentably distinct from each other because conflicting claims are in a patent by the same inventive entity. See table below.
Furthermore, where claims in the instant application are broader than the claims of the ‘251 patent, it would have been obvious to one of ordinary skill in the art at the time the invention was made to omit elements when the remaining elements perform as before. A person of ordinary skill could have arrived at the present claims by omitting the details of the ‘251 patent claims. See In re Karlson (CCPA) 136 USPQ 184, decided January 16, 1963 ("Omission of element and its function in combination is obvious expedient if remaining elements perform same function as before").
Instant application
‘251 patent
Claims 18, 26, 30, 34 (clms 18, 30 exemplary)
18. A method, comprising:
determining, by one or more first processors of a first management apparatus, configuration information of a data analysis apparatus, wherein the configuration information comprises:
state information to activate or de-activate a data analysis function of the data analysis apparatus,
wherein the data analysis apparatus activates or de-activates the data analysis function of the data analysis apparatus in response to receiving the state information;
scope information indicating a scope of data analysis to be performed by the data analysis apparatus; and
N data analysis types, wherein each of the N data analysis types indicates an analysis type of data analysis performed by the data analysis apparatus, and N is an integer greater than or equal to 1,
wherein the state information indicates to activate or de-activate a corresponding data analysis function of each of the N data analysis types;
sending, by the one or more first processors of the first management apparatus, the configuration information; and
receiving, by one or more second processors of a receiving end apparatus, the configuration information.
34. A non-transitory computer-readable media storing computer instructions, that when executed by one or more processors, cause an apparatus to:
receive configuration information,
wherein a data analysis function of a data analysis apparatus is configured with the configuration information, and the configuration information comprises:
state information to activate or de-activate the data analysis function of the data analysis apparatus, wherein the data analysis apparatus activates or de-activates the data analysis function of the data analysis apparatus in response to receiving the state information;
scope information indicating a scope of data analysis performed by the data analysis apparatus; and
N data analysis types, wherein each of the N data analysis types indicates an analysis type of data analysis performed by the data analysis apparatus, and N is an integer greater than or equal to 1, wherein the state information indicates to activate or de-activate a corresponding data analysis function of each of the N data analysis types; and when the apparatus is the data analysis apparatus, performing data analysis based on the configuration information; or
when the apparatus is a second management apparatus, sending the configuration information to the data analysis apparatus, wherein the second management apparatus manages the data analysis apparatus.
20. The method according to claim 18, wherein the data analysis function of the data analysis apparatus is configured with the configuration information.
23. The method according to claim 18, wherein sending the configuration information comprises:
sending a first configuration request to a second management apparatus,
wherein the first configuration request comprises the configuration information, and the first configuration request requests the second management apparatus to configure the data analysis function of the data analysis apparatus,
wherein the receiving end apparatus is the second management apparatus.
24. The method according to claim 18, wherein sending the configuration information comprises:
sending the configuration information to the data analysis apparatus, wherein the receiving end apparatus is the data analysis apparatus.
35. The system according to claim 34, wherein:
when the receiving end apparatus is the data analysis apparatus, the receiving end apparatus is further configured to perform data analysis based on the configuration information.
36. The system according to claim 34, wherein:
when the receiving end apparatus is a second management apparatus, the receiving end apparatus is further configured to send the configuration information to the data analysis apparatus, wherein the second management apparatus is an apparatus managing the data analysis apparatus.
Claims 1, 6, 11, 15 (clms 1, 6 exemplary)
1. A method, comprising:
determining, by one or more processors of a first management apparatus, configuration information of a data analysis apparatus, wherein a data analysis function of the data analysis apparatus is configured with the configuration information, and the configuration information comprises:
state information to activate or de-activate the data
analysis function of the data analysis apparatus,
wherein the data analysis apparatus activates or
de-activates the data analysis function of the data
analysis apparatus in response to receiving the state
information;
scope information indicating a scope of data analysis to be performed by the data analysis apparatus; and
N data analysis types, wherein each of the N data
analysis types indicates an analysis type of data analysis performed by the data analysis apparatus,
and N is an integer greater than or equal to 1,
wherein the state information indicates to activate or deactivate a corresponding data analysis function of each of the N data analysis types; and
sending, by the one or more processors of the first
management apparatus, the configuration information.
6. A method, comprising:
receiving, by one or more processors of a receiving end apparatus, configuration information,
wherein a data analysis function of a data analysis apparatus is configured with the configuration information, and the configuration information comprises:
state information to activate or de-activate the data
analysis function of the data analysis apparatus,
wherein the data analysis apparatus activates or
de-activates the data analysis function of the data analysis apparatus in response to receiving the state
information;
scope information indicating a scope of data analysis performed by the data analysis apparatus; and
N data analysis types, wherein each of the N data
analysis types indicates an analysis type of data
analysis performed by the data analysis apparatus,
and N is an integer greater than or equal to 1, wherein the state information indicates to activate or deactivate a corresponding data analysis function of each of the N data analysis types; and
when the receiving end apparatus is the data analysis apparatus, performing data analysis based on the configuration information; or
when the receiving end apparatus is a second management apparatus, sending the configuration information to the data analysis apparatus, wherein the second management apparatus is an apparatus managing the data analysis apparatus.
10. The method according to claim 6, wherein:
when the receiving end apparatus is the second management apparatus, receiving configuration information comprises: receiving a first configuration request from a first management apparatus, wherein the first configuration request comprises the configuration information, and the configuration information requests the second management apparatus to configure the data analysis function of the data analysis apparatus; or
when the receiving end apparatus is the data analysis apparatus, receiving configuration information comprises: receiving the configuration information from the first management apparatus or the second management apparatus.
Claims 19, 27, 31 (clm 19 exemplary)
The method according to claim 18, wherein the configuration information further comprises:
data source information indicating a data source of data analysis performed by the data analysis apparatus; or
a constraint indicating a constraint of data analysis performed by the data analysis apparatus.
Claims 2, 7, 12, 16 (clm 2 exemplary)
The method according to claim 1, wherein the configuration information further comprises:
data source information indicating a data source of data analysis performed by the data analysis apparatus; or
a constraint indicating a constraint of data analysis performed by the data analysis apparatus.
Claims 21, 28, 32 (clm 21 exemplary)
The method according to claim 19, wherein the N data analysis types comprise:
load data analysis, service experience data analysis, network performance data analysis, congestion data analysis, QoS data analysis, energy saving data analysis, traffic steering data analysis, MIMO data analysis, or UE trajectory data analysis.
Claims 3, 8, 13, 17, (clm 3 exemplary)
The method according to claim 2, wherein the N data
analysis types comprise:
load data analysis, service experience data analysis, network performance data analysis, congestion data analysis, QoS data analysis, energy saving data analysis, traffic steering data analysis, MIMO data analysis, or UE trajectory data analysis.
Claims 22, 29, 33 (clm 22 exemplary)
The method according to claim 18, wherein the scope information comprises:
a network element list indicating the data analysis apparatus to analyze data of a network element in the network element list;
a tracking area code list indicating the data analysis apparatus to analyze data of a tracking area code in the tracking area code list;
a cell list indicating the data analysis apparatus to analyze data of a cell in the cell list;
a network slice list indicating the data analysis apparatus to analyze data of a network slice in the network slice list; or
a geographical area indicating the data analysis apparatus to analyze data in the geographical area.
Claims 4, 9, 14,18 (clm 4 exemplary)
The method according to claim 1, wherein the scope
information comprises:
a network element list indicating the data analysis apparatus to analyze data of a network element in the network element list;
a tracking area code list indicating the data analysis
apparatus to analyze data of a tracking area code in the tracking area code list;
a cell list indicating the data analysis apparatus to analyze data of a cell in the cell list;
a network slice list indicating the data analysis apparatus to analyze data of a network slice in the network slice list; or
a geographical area indicating the data analysis apparatus to analyze data in the geographical area.
23. The method according to claim 18, wherein sending the configuration information comprises:
sending a first configuration request to a second management apparatus,
wherein the first configuration request comprises the configuration information, and the first configuration request requests the second management apparatus to configure the data analysis function of the data analysis apparatus,
wherein the receiving end apparatus is the second management apparatus.
5. The method according to claim 1, wherein sending the configuration information comprises:
sending a first configuration request to a second management apparatus,
wherein the first configuration request comprises the configuration information, and the first configuration request requests the second management apparatus to configure the data analysis function of the data analysis apparatus; or
sending the configuration information to the data analysis apparatus.
10. The method according to claim 6, wherein:
when the receiving end apparatus is the second management apparatus, receiving configuration information comprises: receiving a first configuration request from a first management apparatus, wherein the first configuration request comprises the configuration information, and the configuration information requests the second management apparatus to configure the data
analysis function of the data analysis apparatus; or
when the receiving end apparatus is the data analysis
apparatus, receiving configuration information comprises: receiving the configuration information from the first management apparatus or the second management apparatus.
25. The method according to claim 18, wherein the N data analysis types includes a first data analysis type and a second data analysis type that is different from the first data analysis type,
wherein the state information includes first state information and second state information that is different from the first state information,
wherein the first state information indicates to activate or de-activate a first data analysis function of the first data analysis type,
and wherein the second state information indicates to activate or de-activate a second data analysis function of the second data analysis type.
19. The method according to claim 1, wherein the N data analysis types includes a first data analysis type and a second data analysis type that is different from the first data analysis type,
wherein the state information includes first state information and second state information that is different from the first state information,
wherein the first state information indicates to activate or de-activate a data analysis function of the first data analysis type,
and wherein the second state information indicates to activate or de-activate a data analysis function of the second data analysis type.
Conclusion
The following prior art made of record and not relied upon is considered pertinent to applicant’s disclosure.
A) US 20230100296 – Chong
A communication method includes receiving, by a second data analytics network element, a status analytics output of a target object from a first data analytics network element. The target object includes one or more of a network device, a sub-domain of a network, an all-domain of a network, or a terminal device. The communication method also includes obtaining, by the second data analytics network element based on the status analytics output of the target object, first input data corresponding to a target type of analytics. The status analytics output of the target object indicates that the target object is in an abnormal state, indicating that the first input data does not comprise data corresponding to the target object. The communication method further includes generating, by the second data analytics network element based on the first input data, a first analytics output corresponding to the target type of analytics.
B) US 20230409664 – Yamaguchi
Data analysis device 1 includes: a difference value calculator that calculates, in data section (i, i+1) in which ith data at a predetermined date and time among the plurality of pieces of data is used as a start point value and (i+1)th data at a date and time after the predetermined date and time is used as an end point value, explanatory variable difference value ΔX that is a difference between start point value X(i) of explanatory variable X included in the ith data and end point value X(i+1) of explanatory variable X included in the (i+1)th data, and target variable difference value ΔY that is a difference between start point value Y(i) of target variable Y included in the ith data and end point value Y(i+1) of target variable Y included in the (i+1) data; and a difference model derivation unit that derives difference model M indicating a relationship between explanatory variable difference value ΔX and target variable difference value ΔY based on a plurality of the explanatory variable difference values ΔX and a plurality of the target variable difference values ΔY.
C) US 12177084 – Tamagnan
A method for providing data relating to at least one user device to a data analysis entity. The method includes: collecting, for a plurality of events having impacted on at least one state of the user device in the network, data relating to the at least one impacted state; and supplying, to the data analysis entity, for at least one such state of the user device, at least one statistic obtained for this state by aggregating data relating to this state collected during the collecting step and a part of the data corresponding to an integer X greater than or equal to 1 of events among the most recent events of the plurality of events.
D) US 20230237071 – Zhu
A method includes: obtaining a multi-type service data report that requires data analysis; analyzing and processing the multi-type service data report to determine N types of service data that fluctuate in the multi-type service data report, where N is an integer greater than or equal to 1; and screening out abnormal service data that abnormally fluctuates from the N types of service data and exporting the abnormal service data. A system for big data analysis is further provided. Instead of simply regarding fluctuant service data as abnormal service data, the method and the system determine abnormal service data based on the N types of fluctuant service data in the multi-type service data report. This reduces overreactions and helps reasonably measure service data. Therefore, service data can be thoroughly analyzed.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to JUNE SISON whose telephone number is (571)270-5693. The examiner can normally be reached 9:00 am - 5:00 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, Emmanuel Moise can be reached at 571-272-3865. 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.
/JUNE SISON/Primary Examiner, Art Unit 2455
Prosecution Insights