DETAILED ACTION
The present application is being examined under the pre-AIA first to invent provisions.
This office action is in responsive to communication(s): original application filed on 08/22/2024, said application claims a priority filing date of 04/10/2012.
Claims 1-18 are pending. Claims 1 and 10 are independent.
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 –
(b) the invention was patented or described in a printed publication in this or a foreign country or in public use or on sale in this country, more than one year prior to the date of application for patent in the United States.
Claims 1-8 and 10-17 are rejected under 35 U.S.C. 102(b) as being anticipated by Poston et al. (U.S. Publication 2017/0235800; hereinafter “Poston”).
In regard to independent claims 1 and 10, Poston teaches a method for displaying a content object to a user of a controlling application comprising:
in response to the user accessing a record in the controlling application, receiving, by a dynamic content engine comprising at least one processor, a notification of the user’s access of the record, the notification comprising a primary key and a record type for the record;
retrieving one or more display commands for the record based on the record type, each display command specifying one or more data required from the controlling application to display the content object;
retrieving, in real-time, the specified one or more data that is associated with the primary key from the controlling application;
retrieving one or more related data from the controlling application that is related to the specified one or more data; and
populating a user interface with the specified one or more data and the one or more related data for display to the user and for subsequent access by the user of the content object associated with the record in the controlling application, wherein the user interface visually reflects relationships among the records, or the data in the records, in the controlling application and provides access to the content object (Poston, figure 1; “Clarification: notifications displayed in figure 1(a) and 1(b) and user interface populated with data related with the notification is displayed in 1(c)").
In regard to dependent claims 2 and 11, Poston teaches the content object comprises a document file, an image file, or a video file (Poston, table 2)
In regard to dependent claims 3 and 12, Poston teaches the content object comprises a folder, wherein the folder comprises a document file, an image file, or a video file. (Poston, paragraph 0113, lines 8-15).
In regard to dependent claims 4 and 13, Poston teaches in response to the user locating content that does not otherwise exist in the controlling application, instructing the controlling application to create a new record, wherein the instructing further comprises providing a record type to the controlling application, wherein the record type specifies a type of the content; and
upon receiving a second primary key for the new record, associating the content with the primary key (Poston, paragraph 0090, lines 9-11; “Note: new record is created when record does not exists”).
In regard to dependent claims 5 and 14, Poston teaches the user interface visually reflects hierarchical relationships among the records, or the data in the records, in the controlling application (Poston, figure 1c).
In regard to dependent claims 6 and 15, Poston teaches the user interface visually reflects direct relationships among the records, or the data in the records, in the controlling application (Poston, figure 2).
In regard to dependent claims 7 and 16, Poston teaches the user interface visually reflects indirect relationships among the records, or the data in the records, in the controlling application (Poston, paragraph 0096, lines 20-32; figure 1c; “Note: indirect relationship is displayed under Germany which is determined dynamically”).
In regard to dependent claims 8 and 17, Poston in response to the user navigating between a first record reflected in the user interface to a second record in the user interface:
receiving, by the dynamic content engine, a notification of the user’s access of the second record, the notification comprising a second primary key about the second record;
retrieving one or more display commands for the second record based on the second primary key, each display command specifying one or more second data required from the controlling application;
retrieving the specified one or more second data from the controlling application; populating a user interface with the specified one or more second data for display to the
user. (Poston, figure 6, figure 4, paragraph 0104, lines 3-6; “Note: after navigating first record, user is able to drill down 2nd, third, 4th etc record in both text entry and selection of the parent node").
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 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 Ornum, 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).
Claims 1 and 10 are rejected on the ground of nonstatutory obviousness-type double patenting as being unpatentable over claims 1 and 8, of US Patent 9,046,993 by Bimson et al. (hereinafter ‘993). Although the conflicting claims are not identical, they are not patentably distinct from each other because:
The scope of claim limitations 1 and 10 of instant application falls within the scope of the claim limitations 1 and 8 of '993 underlined below:
Instant Application 18/812456
Reference Patent # 9046993
Claim 1. A method for displaying a content object to a user of a controlling application comprising: in response to the user accessing a record in the controlling application, receiving, by a dynamic content engine comprising at least one processor, a notification of the user's access of the record, the notification comprising a primary key and a record type for the record; retrieving one or more display commands for the record based on the record type, each display command specifying one or more data required from the controlling application to display the content object;
retrieving, in real-time, the specified one or more data that is associated with the primary key from the controlling application;
retrieving one or more related data from the controlling application that is related to the specified one or more data; and
populating a user interface with the specified one or more data and the one or more related data for display to the user and for subsequent access by the user of the content object associated with the record in the controlling application, wherein the user interface visually reflects relationships among the records, or the data in the records, in the controlling application and provides access to the content object.
Claim 1. A method for displaying a content object to a user of a controlling application comprising: in response to the user accessing a record in the controlling application, receiving, by a dynamic content engine comprising at least one processor, a notification of the user's access of the record, the notification comprising a primary key and a record type for the record; retrieving one or more display commands for the record based on the record type, each display command specifying one or more data required from the controlling application to display the content object;
retrieving, in real-time, the specified one or more data that is associated with the primary key from the controlling application;
retrieving one or more related data from the controlling application that is related to the specified one or more data; and
populating a user interface with the specified one or more data and the one or more related data for display to the user and for subsequent access by the user of the content object associated with the record in the controlling application, wherein the user interface visually reflects relationships among the records, or the data in the records, in the controlling application and provides access to the content object
wherein the content object comprises a document file, an image
file, or a video file,
wherein in response to a request by the user, instructing the controlling application to export one or more second data for the record; inducting the one or more second data; and associating the one or more second data with the
Conclusion
Any inquiry concerning this communication or earlier communications from the examiner should be directed to REZA NABI whose telephone number is (571)270-7592. The examiner can normally be reached Monday - Friday 8:00 am - 5:00 pm 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, WILLIAM BASHORE can be reached at 571-272-4088. 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.
/Reza Nabi/
Primary Examiner, Art Unit 2174
Prosecution Insights