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 .
This office action is in response to application filed on May 8, 2025, in which claim 1 is pending in this application.
Double Patenting
A rejection based on double patenting of the “same invention” type finds its support in the language of 35 U.S.C. 101 which states that “whoever invents or discovers any new and useful process... may obtain a patent therefor...” (Emphasis added). Thus, the term “same invention,” in this context, means an invention drawn to identical subject matter. See Miller v. Eagle Mfg. Co., 151 U.S. 186 (1894); In re Vogel, 422 F.2d 438, 164 USPQ 619 (CCPA 1970); In re Ockert, 245 F.2d 467, 114 USPQ 330 (CCPA 1957).
A statutory type (35 U.S.C. 101) double patenting rejection can be overcome by canceling or amending the claims that are directed to the same invention so they are no longer coextensive in scope. The filing of a terminal disclaimer cannot overcome a double patenting rejection based upon 35 U.S.C. 101.
Instant application 19/202519
Patent No. 12306822
1. A system to notify an event for one or more objects deployed in a connected environment having a plurality of distinct ecosystems, the system comprising: a processor to: receive a request from a user to generate the event, wherein the event is indicative of a modification of an object deployed in the connected environment; process the request for the modification of the object to obtain a modified object; record the event in a timeline database for a timeline of the object, wherein the event is recorded in the timeline database in a timeline table, the event being recorded with attributes comprising an object identifier, a timestamp, a user identifier, and an event type; publish the timeline table with the modified object for the user; update the event in a user table, the event being recorded with attributes comprising an object identifier, a user identifier, a notification type, and a frozen flag; identify one or more linked users based on the modified object in the timeline table and the user table, wherein the one or more linked users include at least one of a user referenced in the modified object and a user subscribed to receive a notification of an occurrence of the event for the object; determine the notification type of the one or more linked users in the user table, wherein the notification type indicates a user preference to receive the notification of the occurrence of the event for the object; and select a user from the one or more linked users based on the user preference; and notify the selected user of the event.
1. A system to notify an event for one or more objects deployed in a connected environment having a plurality of distinct ecosystems, the system comprising: a processor to: receive a request from a user to generate the event, wherein the event is indicative of a modification of an object deployed in the connected environment; process the request for the modification of the object to obtain a modified object; record the event in a timeline database for a timeline of the object, wherein the event is recorded in the timeline database in a timeline table, the event being recorded with attributes comprising an object identifier, a timestamp, a user identifier, and an event type; publish the timeline table with the modified object for the user; update the event in a user table, the event being recorded with attributes comprising an object identifier, a user identifier, a notification type, and a frozen flag; identify one or more linked users based on the modified object in the timeline table and the user table, wherein the one or more linked users include at least one of a user referenced in the modified object and a user subscribed to receive a notification of an occurrence of the event for the object; determine the notification type of the one or more linked users in the user table, wherein the notification type indicates a user preference to receive the notification of the occurrence of the event for the object; and select a user from the one or more linked users based on the user preference; and notify the selected user of the event.
Conclusion
Any inquiry concerning this communication or earlier communications from the examiner should be directed to NOOSHA ARJOMANDI whose telephone number is (571)272-9784. The examiner can normally be reached on (571)272-9784.
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, Sanjiv Shah can be reached on (571)272-4098. 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.
January 24, 2026
/NOOSHA ARJOMANDI/Primary Examiner, Art Unit 2166