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 .
DETAILED ACTION
This action is response to the applicant’s Arguments/Remarks filed on 12/03/2025.
Claims 1-20 are pending in this Office Action and stand rejected in which claims 1, 9 and 14 are independent claims.
Priority
Acknowledged is this Application claims the benefit of priority from US Application 17810715 (Now U.S. Patent 11928115, issued 03/12/2024), filed 07/05/2022.
Response to Arguments
Applicant's arguments filed 12/03/2025 have been respectfully reviewed and fully considered. However, the arguments with respect to claims 1-20 are moot because the claims are now considered as allowable subject matter subject to the issue of Double Patenting Rejections to be resolved and the scope of invention to be amended as a formality. Please refer to the Paragraph Allowable Subject Matter.
Double Patenting Rejections
The Double Patenting Rejections is hereby respectfully presented as below.
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 obviousness-type 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 Omum, 686 F.2d 937, 214 USPQ 761 (CCPA 1982); In re Vogel, 422 F.2d 438, 164 USPQ 619 (CCPA 1970); and 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 a nonstatutory double patenting ground provided the conflicting application or patent either is shown to be commonly owned with this application, or claims an invention made as a result of activities undertaken within the scope of a joint research agreement. Effective January 1, 1994, a registered attorney or agent of record may sign a terminal disclaimer. A terminal disclaimer signed by the assignee must fully comply with 37 CFR 3.73(b).
This is a provisional obviousness-type double patenting rejection because the conflicting claims have not in fact been patented.
Claims 1-20 are rejected on the ground of nonstatutory obviousness-type double patenting as being unpatentable over claims 1-20 of U.S. Patent 11928125. Although the conflicting are not patentably distinct from each other because since the claims of the U.S. Patent 11928125 contain elements of the claims of the instant application, and as such, would anticipate or would have been obvious over the claims of the instant application.
This is a provisional nonstatutory double patenting rejection because the patentably indistinct claims have not all in fact been patented.
Instant Application claims 1-20
US Patent 11928125 Claims 1-20
1. A system, comprising:
one or more memories; and
one or more processors, coupled to the one or more memories, configured to:
obtain event data including a plurality of events associated with transaction data,
wherein the event data is associated with a generic schema;
infer an event-specific schema, for the event data that defines an organizational structure for the event data based on common attributes among the plurality of events,
wherein the plurality of events include actions or occurrences in a data ecosystem;
store a second dataset in which the event data is partitioned using the structure defined by the event-specific schema;
receive one or more parameters that define an extract, transform, load (ETL) pipeline use case;
generate, based on the received one or more parameters, a third dataset to be processed by the ETL pipeline,
wherein the third dataset includes a subset of the event data included in the second dataset that satisfies one or more registration parameters related to an ETL use case, and
wherein the third dataset to be processed by the ETL pipeline comprises data to be extracted by an ETL system, transformed into a target data format, and loaded where the data is made available for one or more data analytics use cases; and
provide the third dataset to the ETL system configured to process the third dataset into the ETL pipeline and process the third dataset based on the ETL use case.
2. The system of claim 1, wherein the one or more processors are further configured to:
generate an event intelligence report that includes information related to the common attributes or information related to the event-specific schema.
3. The system of claim 1, wherein the common attributes are identified among the plurality of events using one or more data analytics functions.
4. The system of claim 1, wherein the one or more processors are further configured to:
store the second dataset in a data repository.
5. The system of claim 1, wherein the second dataset is compatible with a database query format associated with one or more relational database management systems.
6. The system of claim 1, wherein the plurality of events is associated with one or more of:
interactions with a plurality of applications that generated the plurality of events, or
actions performed by the plurality of applications.
7. The system of claim 1, wherein the second dataset is retained in a data repository for a time period.
8. The system of claim 7, wherein the one or more processors are further configured to:
store the third dataset in an additional data repository for an additional time period that is longer than the time period.
9. A method, comprising:
obtaining, by a system, event data including a plurality of events associated with transaction data,
wherein the event data is associated with a generic schema;
inferring, by a system, an event-specific schema for the event data,
wherein the event-specific schema defines an organizational structure for the event data based on common attributes among the plurality of events, and
wherein the plurality of events include actions or occurrences in a data ecosystem;
storing, by the system, a second dataset in which the event data is partitioned using the organizational structure defined by the event-specific schema;
receiving one or more parameters that define an extract, transform, load (ETL) pipeline use case;
generating, by the system and based on the received one or more parameters, a third dataset to be processed by the ETL pipeline,
wherein the third dataset includes a subset of the event data included in the second dataset that satisfies one or more registration parameters related to an ETL use case, and
wherein the third dataset to be processed by the ETL pipeline comprises data to be extracted by an ETL system, transformed into a target data format, and loaded where the data is made available for one or more data analytics use cases; and
providing the third dataset to the ETL system configured to process the third dataset into the ETL pipeline and process the third dataset based on the ETL use case.
10. The method of claim 9, wherein the generic schema is associated with a data format that supports schema variability among a plurality of applications.
11. The method of claim 9, further comprising:
storing the second dataset in a data repository.
12. The method of claim 11, wherein the second dataset is retained in the data repository for a time period.
13. The method of claim 9, wherein the common attributes are identified among the plurality of events using one or more data analytics functions.
14. A non-transitory computer-readable medium storing a set of instructions, the set of instructions comprising:
one or more instructions that, when executed by one or more processors of a system,
cause the system to:
obtain event data including a plurality of events associated with transaction data,
wherein the event data is associated with a generic schema;
infer an event-specific schema, for the event data that defines an organizational structure for the event data based on common attributes among the plurality of events associated with transaction data,
wherein the plurality of events include actions or occurrences in a data ecosystem;
store a second dataset in which the event data is partitioned using the organizational structure defined by the event-specific schema;
receive one or more parameters that define an extract, transform, load (ETL) pipeline use case;
generate, based on the received one or more parameters, a third dataset to be processed by the ETL pipeline,
wherein the third dataset includes a subset of the event data included in the second dataset that satisfies one or more registration parameters related to an ETL use case, and
wherein the third dataset to be processed by the ETL pipeline comprises data to be extracted by an ETL system, transformed into a target data format, and loaded where the data is made available for one or more data analytics use cases;
provide the third dataset to the ETL system configured to process the third dataset into the ETL pipeline and process the third dataset based on the ETL use case ; and
generate a report that includes information related to the common attributes or information related to the event-specific schema.
15. The non-transitory computer-readable medium of claim 14, wherein the one or more instructions further cause the system to:
provide the report to a client device.
16. The non-transitory computer-readable medium of claim 14, wherein the generic schema is associated with a data format that supports schema variability among a plurality of applications.
17. The non-transitory computer-readable medium of claim 14, wherein the common attributes are identified among the plurality of events using one or more data analytics functions.
18. The non-transitory computer-readable medium of claim 14, wherein the
plurality of events is associated with interactions with a plurality of applications that generated the plurality of events.
19. The non-transitory computer-readable medium of claim 14, wherein the plurality of events is associated with actions performed by a plurality of applications that generated the plurality of events.
20. The non-transitory computer-readable medium of claim 14, wherein:
the second dataset is retained in a data repository for a time period, and
the third dataset is retained in an additional data repository for an additional time period that is longer than the time period.
1. A system for cleaning and organizing event data, comprising:
one or more memories; and
one or more processors, communicatively coupled to the one or more memories, configured to:
obtain, from a first data repository, a first dataset that includes event data
associated with a generic schema, the event data including a plurality of events that include actions or occurrences in a data ecosystem,
infer an event-specific schema for the plurality of events that defines an organizational structure for the event data based on common attributes that are identified among the plurality of events using one or more data analytics functions;
store, in a second data repository, a second dataset in which the event data is partitioned using the organizational structure defined by the event-specific schema;
generate a third dataset to be ingested into an extract, transform, load (ETL) pipeline,
the third dataset including a subset of the event data included in the second dataset that satisfies one or more registration parameters related to an ETL use case; and
provide the third dataset to an ETL system configured to ingest the third dataset into the ETL pipeline and process the third dataset based on the ETL use case.
2. The system of claim 1, wherein the one or more processors are further configured to:
generate an event intelligence report that includes information related to the common attributes that are identified among the plurality of events and information related to the event-specific schema that defines the organizational structure for the event data.
3. The system of claim 1, wherein the generic schema is associated with a data format that supports schema variability among a plurality of applications that generated the plurality of events included in the event data.
4. The system of claim 1, wherein the second dataset is compatible with a database query format associated with one or more relational database management systems.
5. The system of claim 1, wherein the plurality of events represent artifacts related to interactions with or actions performed by a plurality of applications that generated the plurality of events included in the event data.
6. The system of claim 1,
wherein the first dataset is retained in the first data repository for a first short-term time period, and
wherein the second dataset is retained in the second data repository for a second short-term time period that is longer than the first short-term time period.
7. The system of claim 6, wherein the one or more processors are further configured to:
store the third dataset in a third data repository for a long-term time period that is longer than the first short-term time period and the second short-term time period.
8. The system of claim 1, wherein the first dataset includes semi-structured data that does not have a fixed tabular structure or an intrinsic logical organization.
9. A method for cleaning and organizing event data for extract, transform, load (ETL) processing, comprising:
obtaining, by an event log management system, a first dataset from a first data repository,
wherein the first dataset includes event data associated with a generic schema, the event data including a plurality of events that include actions or occurrences in a data ecosystem, and
wherein the generic schema is associated with a data format that supports schema variability among a plurality of applications that generated the event data;
inferring, by the event log management system, an event-specific schema for the plurality of events that defines an organizational structure for the event data based on common attributes that are identified among the plurality of events using one or more data analytics functions;
storing, by the event log management system, a second dataset in a second data repository, wherein the second dataset partitions the event data using the organizational structure defined by the event-specific schema;
generating, by the event log management system, a third dataset to be ingested into an ETL pipeline,
the third dataset including a subset of the event data included in the second dataset that satisfies one or more registration parameters related to an ETL use case; and
providing, by the event log management system, the third dataset to an ETL system configured to ingest the third dataset into the ETL pipeline and process the third dataset based on the ETL use case.
10. The method of claim 9, further comprising:
generating an event intelligence report that includes information related to the common attributes that are identified among the plurality of events and information related to the event-specific schema that defines the organizational structure for the event data.
11. The method of claim 9, wherein the second dataset is compatible with a database query format associated with one or more relational database management systems.
12. The method of claim 9, wherein the plurality of events represent artifacts related to interactions with or actions performed by the plurality of applications.
13. The method of claim 9, wherein the first dataset includes semi-structured data that does not have a fixed tabular structure or an intrinsic logical organization.
14. A non-transitory computer-readable medium storing a set of instructions, the set of instructions comprising:
one or more instructions that, when executed by one or more processors of a system, cause the system to:
obtain, from a first data repository, a first dataset that includes event data associated with a generic schema, the event data including a plurality of events that include actions or occurrences in a data ecosystem,
infer an event-specific schema for the plurality of events that defines an organizational structure for the event data based on common attributes that are identified among the plurality of events using one or more data analytics functions;
store, in a second data repository, a second dataset in which the event data is partitioned using the organizational structure defined by the event-specific schema;
generate a third dataset to be ingested into an extract, transform, load (ETL) pipeline, the third dataset including a subset of the event data included in the second dataset that satisfies one or more registration parameters related to an ETL use case;
provide the third dataset to an ETL system configured to ingest the third dataset into the ETL pipeline and process the third dataset based on the ETL use case; and
generate an event intelligence report that includes information related to the common attributes that are identified among the plurality of events and information related to the event-specific schema that defines the organizational structure for the event data.
15. The non-transitory computer-readable medium of claim 14, wherein the one or more instructions further cause the system to:
provide the event intelligence report to a client device.
16. The non-transitory computer-readable medium of claim 14, wherein the generic schema is associated with a data format that supports schema variability among a plurality of applications that generated the event data.
17. The non-transitory computer-readable medium of claim 14, wherein the second dataset is compatible with a database query format associated with one or more relational database management systems.
18. The non-transitory computer-readable medium of claim 14, wherein the plurality of events represent artifacts related to interactions with or actions performed by a plurality of applications that generated the event data.
19. The non-transitory computer-readable medium of claim 14, wherein the first dataset includes semi-structured data that does not have a fixed tabular structure or an intrinsic logical organization.
20. The non-transitory computer-readable medium of claim 14, wherein: the first dataset is retained in the first data repository for a first short-term time period,
the second dataset is retained in the second data repository for a second short-term time period that is longer than the first short-term time period, and
the third dataset is stored in a third data repository for a long-term time period that is longer than the first short-term time period and the second short-term time period.
“Omission of element and its function in combination is obvious expedient if the remaining elements perform same functions as before.” See In re Karlson (CCPA) 136 USPQ 184, decide Jan 16, 1963, Appl. No. 6857, U.S. Court of Customs and Patent Appeals.
Allowable Subject Matter
In view of a thorough search and examination of the present application, and in light of the following:
Prosecution history of the instant application which went through a full cycle of prosecutions including a non-final rejections, a final rejections, an advisory, a request for continued examination and a non-final rejections after the request;
Prosecution history of the parent application 17810715 (Now U.S. Patent 11928115, issued 03/12/2024), filed 07/05/2022;
The Remarks/Arguments/Amendments the Applicant made on 12/03/2025;
An update search on prior art conducted in domains (PE2E, NPL-ACM, Google, NPL-IEEE, IP.com, Google Patents, Google Scholars, WIPO Patent Scope, etc.),
Claims 1-20 are hereby presented with allowable subject matters.
However, Claims 1-20 are currently objected to as being subjected to rejections on the ground of non-statutory obviousness-type double patenting as being unpatentable over claims 1-20 of Patent No. 11928115, as submitted above, and the claims 1-20 would be allowable when below conditions met:
the above double patenting rejections would be withdrawn as a necessity to an approved terminal disclaimer against the U.S. Patent No. 11928115; and
the limitation “generate/[generating] a report that includes information related to the common attributes or information related to the event-specific schema” of claim 14 is also incorporated int claims 1 and 9.
Related Prior Arts
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure can be found in the PTO-892 Notice of Reference Cited.
Conclusion
THIS ACTION IS MADE FINAL. Applicant is reminded of the extension of time policy as set forth in 37 CFR 1.136(a).
A shortened statutory period for reply to this final action is set to expire THREE MONTHS from the mailing date of this action. In the event a first reply is filed within TWO MONTHS of the mailing date of this final action and the advisory action is not mailed until after the end of the THREE-MONTH shortened statutory period, then the shortened statutory period will expire on the date the advisory action is mailed, and any nonprovisional extension fee (37 CFR 1.17(a)) pursuant to 37 CFR 1.136(a) will be calculated from the mailing date of the advisory action. In no event, however, will the statutory period for reply expire later than SIX MONTHS from the mailing date of this final action.
Examiner has cited particular columns and line numbers in the references applied to the claims above for the convenience of the applicant. Although the specified citations are representative of the teachings of the art and are applied to specific limitations within the individual claim, other passages and figures may apply as well. It is respectfully requested from the applicant in preparing responses, to fully consider the references in entirety as potentially teaching all or part of the claimed invention, as well as the context of the passage as taught by the prior art or disclosed by the Examiner. SEE MPEP 2141.02 [R-5] VI. PRIOR ART MUST BE CONSIDERED IN ITS ENTIRETY, INCLUDING DISCLOSURES THAT TEACH AWAY FROM THE CLAIMS: A prior art reference must be considered in its entirety, i.e., as a whole, including portions that would lead away from the claimed invention. W.L. Gore & Associates, Inc. v. Garlock, Inc., 721 F.2d 1540, 220 USPQ 303 (Fed. Cir. 1983), cert. denied, 469 U.S. 851 (1984) In re Fulton, 391 F.3d 1195, 1201, 73 USPQ2d 1141, 1146 (Fed. Cir. 2004). >See also MPEP §2123.
In the case of amending the Claimed invention, Applicant is respectfully requested to indicate the portion(s) of the specification which dictate(s) the structure relied on for proper interpretation and also to verify and ascertain the metes and bounds of the claimed invention.
Contact Information
Any inquiry concerning this communication or earlier communications from the examiner should be directed to KUEN S LU whose telephone number is (571)272-4114. The examiner can normally be reached on M-F, 8-19, Mid-Flex 2 hours.
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, Mr. Ajay Bhatia can be reached on 5712723906. 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 http://pair-direct.uspto.gov. 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.
KUEN S LU /Kuen S Lu/
Art Unit 2156
Primary Patent Examiner
January 29, 2026