Prosecution Insights
Last updated: October 02, 2026
Application No. 18/981,020

DATA INTERACTION METHOD, NON-TRANSITORY COMPUTER-READABLE MEDIUM, AND ELECTRONIC DEVICE

Non-Final OA §103
Filed
Dec 13, 2024
Priority
Dec 14, 2023 — CN 202311725200.9
Examiner
SAMWEL, DANIEL
Art Unit
Tech Center
Assignee
Beijing Volcano Engine Technology Co., Ltd.
OA Round
1 (Non-Final)
75%
Grant Probability
Favorable
1-2
OA Rounds
10m
Est. Remaining
99%
With Interview

Examiner Intelligence

Grants 75% — above average
75%
Career Allowance Rate
275 granted / 368 resolved
+14.7% vs TC avg
Strong +24% interview lift
Without
With
+24.4%
Interview Lift
resolved cases with interview
Typical timeline
2y 8m
Avg Prosecution
19 currently pending
Career history
384
Total Applications
across all art units

Statute-Specific Performance

§101
11.3%
-28.7% vs TC avg
§103
51.1%
+11.1% vs TC avg
§102
19.5%
-20.5% vs TC avg
§112
11.5%
-28.5% vs TC avg
Black line = Tech Center average estimate • Based on career data from 368 resolved cases

Office Action

§103
DETAILED ACTION The action is responsive to the Application filed on 12/13/2024. Claims 1-20 are pending in the case. Claims 1, 9 and 16 are independent claims. 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: “a storage apparatus, having” and “a processing apparatus, configured to execute” in claim 16. 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. Claim Rejections - 35 USC § 103 In the event the determination of the status of the application as subject to AIA 35 U.S.C. 102 and 103 (or as subject to pre-AIA 35 U.S.C. 102 and 103) is incorrect, any correction of the statutory basis (i.e., changing from AIA to pre-AIA ) for the rejection will not be considered a new ground of rejection if the prior art relied upon, and the rationale supporting the rejection, would be the same under either status. 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. Claims 1-3, 6-11 and 14-18 are rejected under 35 U.S.C. 103 as being unpatentable over Fozdar et al. (US 20250077538 A1, hereinafter Fozdar) in view of Liao (US 20230014265 A1). As to claim 1, Fozdar discloses a data interaction method, comprising: displaying target data pushed by a data platform through a first display panel on a display interface of a first application ("As shown in FIG. 3A, the exemplary GUI 300 includes various UI elements that are designed to assist the user with performing a data integration task by building a data pipeline. In accordance with some embodiments of the present techniques, a window 302 is provided along the righthand side of the GUI 300, where such window 302 is designed to enable the user to provide input for performing the natural language-based data integration process described herein. Specifically, the exemplary window 302 shown in FIG. 3A provides a chat bot-style implementation of the present techniques. In this particular embodiment, the window 302 includes a chat bot introduction 304 stating, 'Welcome: Simply tell me what you want to do, and I will do all the steps for you. No need to hunt for commands or help articles.' The window 302 also includes a text field 306 that allows the user to respond by providing input in the form of a natural language query corresponding to a desired data integration task," Fozdar paragraph 0043; "Turning now to FIG. 3B, the user has input the following natural language query into the text field 306: 'Add a copy activity that copies incremental data from SQL via Source1 into Container1/Folder1 via Destination1. Look up the country name from Table1 in SQL via Source1 to use as a parameter for copy source table in SQL.' In response to this natural language query, the natural language-based data integration system described herein has generated and output a corresponding data pipeline, as shown in window 308. In addition, as shown in box 310, the chat bot has responded by stating, 'I'm creating the pipeline for you . . . I've updated the pipeline for you. What's next?'," Fozdar paragraph 0044, pushing pipeline data to the app and displaying some information at 310); and an interactive control in the first display panel ("As shown in the window 302, a number of buttons are then surfaced, including a 'Regenerate Pipeline' button 312, a 'Run Pipeline' button 314, and a 'Send Email When Any Activity Fails' button 316, as well as a second text field 318 that enables the user to direct the modification of the generated data pipeline, if desired," Fozdar paragraph 0044, multiple controls to interact with the data in some way), and displaying, on the display interface of the first application, a data interaction result based on the target data through a second display panel, wherein the second display panel is displayed side by side with or in parallel to the first display panel ("In response to this natural language query, the natural language-based data integration system described herein has generated and output a corresponding data pipeline, as shown in window 308," Fozdar paragraph 0044; Fozdar Figure 3B windows 308 and 310 are side by side). However Fozdar does not appear to explicitly disclose in response to a trigger operation on an interactive control in the first display panel, reducing the first display panel for display, and displaying, on the display interface of the first application, a data interaction result. Liao teaches in response to a trigger operation on an interactive control in the first display panel, reducing the first display panel for display, and displaying, on the display interface of the first application, a data interaction result ("Specifically, after the user views the mail sharing information in the target dialog window in the IM client, the mail viewing operation may be triggered by performing a click operation on the mail sharing information. The click operation may be, but not limited to, a touch-click or a mouse-click," Liao paragaph 0042; "Specifically, in response to detecting the mail viewing operation, the IM client may create the mail display window that is displayed independently from the target IM dialog window at a preset position of the target IM dialog window, such as a position on the right side, left side, upper side or lower side. Therefore, the target IM dialog window and the mail display window are displayed in parallel, so that the displayed mail information and dialog information are also displayed in parallel, and thus the user may more conveniently view the mail information and the dialog information at the same time, and the user experience is further improved. For example, FIG. 4 shows an example of a mail display window. An IM client in FIG. 4 is integrated in a PC. In response to detecting a mail viewing operation, a mail display window is automatically created on the right side of a target IM dialog window, so that the target IM dialog window and the mail display window may display information in parallel. FIG. 5 shows another example of a mail display window. An IM client in FIG. 5 is integrated in a mobile terminal. In response to detecting a mail viewing operation, due to a limited screen size, a target IM dialog window may be displayed in a reduced size, and a mail display window may be automatically created on the lower side of the reduced target IM dialog window," Liao paragraph 0045; Liao Figure 3 "Open Shared Mail" button; Liao Figure 4). Accordingly it would have been obvious to a person of ordinary skill in the art before the effective filing date of the claimed invention to modify the method of Fozdar to display the initial chatbot interface in full screen and display a control for displaying Fozdar’s data interaction result as taught by Liao. One would have been motivated to make such a combination so that the chatbot interface could be larger on the initial view only becoming smaller when the user chooses to display the additional data thus improving readability of the initial interface and improving user choice. As to claim 2, Fozdar as modified by Liao further discloses the data interaction method according to claim 1, wherein the in response to a trigger operation on an interactive control in the first display panel, reducing the first display panel for display, and displaying, on the display interface of the first application, a data interaction result based on the target data through a second display panel, comprises: in response to a trigger operation on a first view control in the first display panel, displaying, on the display interface of the first application, data details corresponding to the target data through the second display panel, wherein the data details comprise data interpretation information of the target data and/or a data chart generated based on the target data ("More specifically, the present techniques provide a natural language-based data integration system that leverages an LLM as a controller for invoking and coordinating the execution of various application programming interfaces (APIs) in order to generate valid data pipelines, including Extract, Transform, and Load (ETL) data pipelines and/or Extract, Load, and Transform (ELT) data pipelines," Fozdar paragraph 0016; "In various embodiments, the user then provides input indicating a desire to run or regenerate the data pipeline (among other potential tasks), and the data integration application 102 responds by performing the task requested by the user," Fozdar paragraph 0031, displayed option to regenerate the pipeline which will be displayed in the second panel); and/or in response to a trigger operation on a second view control in the first display panel, displaying, on the display interface of the first application, a structured query language (SQL) statement for querying the target data through the second display panel. As to claim 3, Fozdar as modified by Liao further discloses the data interaction method according to claim 1, further comprising: displaying a preset analysis instruction for the target data in the first display panel; and in response to a selection operation on a target analysis instruction in the preset analysis instruction, displaying, in the first display panel, a data analysis result obtained by analyzing the target data according to the target analysis instruction ("Turning now to FIG. 3B, the user has input the following natural language query into the text field 306: 'Add a copy activity that copies incremental data from SQL via Source1 into Container1/Folder1 via Destination1. Look up the country name from Table1 in SQL via Source1 to use as a parameter for copy source table in SQL.' In response to this natural language query, the natural language-based data integration system described herein has generated and output a corresponding data pipeline, as shown in window 308. In addition, as shown in box 310, the chat bot has responded by stating, 'I'm creating the pipeline for you . . . I've updated the pipeline for you. What's next?' As shown in the window 302, a number of buttons are then surfaced, including a 'Regenerate Pipeline' button 312, a 'Run Pipeline' button 314, and a 'Send Email When Any Activity Fails' button 316, as well as a second text field 318 that enables the user to direct the modification of the generated data pipeline, if desired," Fozdar paragraph 0044, text box for further user input to direct modification of the data pipeline where the output to the text input will be displayed in first panel 302). As to claim 6, Fozdar as modified by Liao further discloses the data interaction method according to claim 1, wherein the second display panel displays a sub-interactive control for performing an interactive function on the data interaction result, and the data interaction method further comprises: in response to a trigger operation on the sub-interactive control in the second display panel, jumping to the data platform, and displaying a function tab related to the interactive function corresponding to the sub-interactive control in the data platform (Fozdar Figure 3B "Parameters", "Variables", "Settings", "Output" tab controls and controls on the right of the pipeline view in 310 to search, zoom in and out and perform other functions on the data pipeline); and/or in response to a trigger operation on the sub-interactive control in the second display panel, displaying a sub-interaction result in the second display panel, wherein the sub-interaction result is obtained by performing the interactive function corresponding to the sub-interactive control. As to claim 7, Fozdar as modified by Liao further discloses the data interaction method according to claim 6, wherein the in response to a trigger operation on the sub-interactive control in the second display panel, jumping to the data platform, and displaying a function tab related to the interactive function corresponding to the sub-interactive control in the data platform comprises: in response to a trigger operation on a first sub-interactive control in the second display panel, jumping to the data platform, and displaying a dataset tab in the data platform, wherein the first sub-interactive control is used to view a dataset associated with the data interaction result (Fozdar Figure 3B "Parameters", "Variables", and "Output" tab controls to view the dataset data); and/or in response to a trigger operation on a second sub-interactive control in the second display panel, jumping to the data platform, and displaying an SQL tab in the data platform, wherein the second sub-interactive control is used to view an SQL statement for generating the data interaction result. As to claim 8, Fozdar as modified by Liao further discloses the data interaction method according to claim 6, wherein the data interaction result comprises a data chart generated based on the target data, and the in response to a trigger operation on the sub-interactive control in the second display panel, displaying a sub-interaction result in the second display panel comprises: in response to a trigger operation on a target third sub-interactive control in the second display panel, switching, in the second display panel, a chart type of the data chart according to a chart type corresponding to the target third sub-interactive control, wherein the second display panel displays a plurality of third sub-interactive controls that are different, each of the plurality of third sub-interactive controls is used to indicate one data chart type, and the target third sub-interactive control is one of the plurality of third sub-interactive controls (Fozdar Figure 3B "Parameters", "Variables", "Settings", "Output" tab controls and controls on the right of the pipeline view in 310 to search, zoom in and out and perform other functions on the data pipeline where the displayed parameters can be edited, added to or deleted and thus changes the flowchart displayed). As to claim 9, Fozdar discloses a non-transitory computer-readable medium having a computer program stored thereon, wherein when the computer program is executed by a processing apparatus, causes the processing apparatus to implement a data interaction method, and the data interaction method (“In the present disclosure, a machine readable medium may be a tangible medium, which may contain or store a program used by the instruction execution system, apparatus, or device or a program used in combination with the instruction execution system, apparatus, or device,” Fozdar paragraph 0132) comprises: displaying target data pushed by a data platform through a first display panel on a display interface of a first application ("As shown in FIG. 3A, the exemplary GUI 300 includes various UI elements that are designed to assist the user with performing a data integration task by building a data pipeline. In accordance with some embodiments of the present techniques, a window 302 is provided along the righthand side of the GUI 300, where such window 302 is designed to enable the user to provide input for performing the natural language-based data integration process described herein. Specifically, the exemplary window 302 shown in FIG. 3A provides a chat bot-style implementation of the present techniques. In this particular embodiment, the window 302 includes a chat bot introduction 304 stating, 'Welcome: Simply tell me what you want to do, and I will do all the steps for you. No need to hunt for commands or help articles.' The window 302 also includes a text field 306 that allows the user to respond by providing input in the form of a natural language query corresponding to a desired data integration task," Fozdar paragraph 0043; "Turning now to FIG. 3B, the user has input the following natural language query into the text field 306: 'Add a copy activity that copies incremental data from SQL via Source1 into Container1/Folder1 via Destination1. Look up the country name from Table1 in SQL via Source1 to use as a parameter for copy source table in SQL.' In response to this natural language query, the natural language-based data integration system described herein has generated and output a corresponding data pipeline, as shown in window 308. In addition, as shown in box 310, the chat bot has responded by stating, 'I'm creating the pipeline for you . . . I've updated the pipeline for you. What's next?'," Fozdar paragraph 0044, pushing pipeline data to the app and displaying some information at 310); and an interactive control in the first display panel ("As shown in the window 302, a number of buttons are then surfaced, including a 'Regenerate Pipeline' button 312, a 'Run Pipeline' button 314, and a 'Send Email When Any Activity Fails' button 316, as well as a second text field 318 that enables the user to direct the modification of the generated data pipeline, if desired," Fozdar paragraph 0044, multiple controls to interact with the data in some way), and displaying, on the display interface of the first application, a data interaction result based on the target data through a second display panel, wherein the second display panel is displayed side by side with or in parallel to the first display panel ("In response to this natural language query, the natural language-based data integration system described herein has generated and output a corresponding data pipeline, as shown in window 308," Fozdar paragraph 0044; Fozdar Figure 3B windows 308 and 310 are side by side). However Fozdar does not appear to explicitly disclose in response to a trigger operation on an interactive control in the first display panel, reducing the first display panel for display, and displaying, on the display interface of the first application, a data interaction result. Liao teaches in response to a trigger operation on an interactive control in the first display panel, reducing the first display panel for display, and displaying, on the display interface of the first application, a data interaction result ("Specifically, after the user views the mail sharing information in the target dialog window in the IM client, the mail viewing operation may be triggered by performing a click operation on the mail sharing information. The click operation may be, but not limited to, a touch-click or a mouse-click," Liao paragaph 0042; "Specifically, in response to detecting the mail viewing operation, the IM client may create the mail display window that is displayed independently from the target IM dialog window at a preset position of the target IM dialog window, such as a position on the right side, left side, upper side or lower side. Therefore, the target IM dialog window and the mail display window are displayed in parallel, so that the displayed mail information and dialog information are also displayed in parallel, and thus the user may more conveniently view the mail information and the dialog information at the same time, and the user experience is further improved. For example, FIG. 4 shows an example of a mail display window. An IM client in FIG. 4 is integrated in a PC. In response to detecting a mail viewing operation, a mail display window is automatically created on the right side of a target IM dialog window, so that the target IM dialog window and the mail display window may display information in parallel. FIG. 5 shows another example of a mail display window. An IM client in FIG. 5 is integrated in a mobile terminal. In response to detecting a mail viewing operation, due to a limited screen size, a target IM dialog window may be displayed in a reduced size, and a mail display window may be automatically created on the lower side of the reduced target IM dialog window," Liao paragraph 0045; Liao Figure 3 "Open Shared Mail" button; Liao Figure 4). Accordingly it would have been obvious to a person of ordinary skill in the art before the effective filing date of the claimed invention to modify the non-transitory computer-readable medium of Fozdar to display the initial chatbot interface in full screen and display a control for displaying the data interaction result as taught by Liao. One would have been motivated to make such a combination so that the chatbot interface could be larger on the initial view only becoming smaller when the user chooses to display the additional data thus improving readability of the initial interface and improving user choice. As to claim 10, it is substantially similar to claim 2 and is therefore rejected using the same rationale as above. As to claim 11, it is substantially similar to claim 3 and is therefore rejected using the same rationale as above. As to claim 14, it is substantially similar to claim 6 and is therefore rejected using the same rationale as above. As to claim 15, it is substantially similar to claim 7 and is therefore rejected using the same rationale as above. As to claim 16, Fozdar discloses an electronic device, comprising: a storage apparatus, having a computer program stored thereon (“In the present disclosure, a machine readable medium may be a tangible medium, which may contain or store a program used by the instruction execution system, apparatus, or device or a program used in combination with the instruction execution system, apparatus, or device,” Fozdar paragraph 0132); and a processing apparatus, configured to execute the computer program in the storage apparatus, to implement a data interaction method, and the data interaction method (“In the present disclosure, a machine readable medium may be a tangible medium, which may contain or store a program used by the instruction execution system, apparatus, or device or a program used in combination with the instruction execution system, apparatus, or device,” Fozdar paragraph 0132) comprises: displaying target data pushed by a data platform through a first display panel on a display interface of a first application ("As shown in FIG. 3A, the exemplary GUI 300 includes various UI elements that are designed to assist the user with performing a data integration task by building a data pipeline. In accordance with some embodiments of the present techniques, a window 302 is provided along the righthand side of the GUI 300, where such window 302 is designed to enable the user to provide input for performing the natural language-based data integration process described herein. Specifically, the exemplary window 302 shown in FIG. 3A provides a chat bot-style implementation of the present techniques. In this particular embodiment, the window 302 includes a chat bot introduction 304 stating, 'Welcome: Simply tell me what you want to do, and I will do all the steps for you. No need to hunt for commands or help articles.' The window 302 also includes a text field 306 that allows the user to respond by providing input in the form of a natural language query corresponding to a desired data integration task," Fozdar paragraph 0043; "Turning now to FIG. 3B, the user has input the following natural language query into the text field 306: 'Add a copy activity that copies incremental data from SQL via Source1 into Container1/Folder1 via Destination1. Look up the country name from Table1 in SQL via Source1 to use as a parameter for copy source table in SQL.' In response to this natural language query, the natural language-based data integration system described herein has generated and output a corresponding data pipeline, as shown in window 308. In addition, as shown in box 310, the chat bot has responded by stating, 'I'm creating the pipeline for you . . . I've updated the pipeline for you. What's next?'," Fozdar paragraph 0044, pushing pipeline data to the app and displaying some information at 310); and an interactive control in the first display panel ("As shown in the window 302, a number of buttons are then surfaced, including a 'Regenerate Pipeline' button 312, a 'Run Pipeline' button 314, and a 'Send Email When Any Activity Fails' button 316, as well as a second text field 318 that enables the user to direct the modification of the generated data pipeline, if desired," Fozdar paragraph 0044, multiple controls to interact with the data in some way), and displaying, on the display interface of the first application, a data interaction result based on the target data through a second display panel, wherein the second display panel is displayed side by side with or in parallel to the first display panel ("In response to this natural language query, the natural language-based data integration system described herein has generated and output a corresponding data pipeline, as shown in window 308," Fozdar paragraph 0044; Fozdar Figure 3B windows 308 and 310 are side by side). However Fozdar does not appear to explicitly disclose in response to a trigger operation on an interactive control in the first display panel, reducing the first display panel for display, and displaying, on the display interface of the first application, a data interaction result. Liao teaches in response to a trigger operation on an interactive control in the first display panel, reducing the first display panel for display, and displaying, on the display interface of the first application, a data interaction result ("Specifically, after the user views the mail sharing information in the target dialog window in the IM client, the mail viewing operation may be triggered by performing a click operation on the mail sharing information. The click operation may be, but not limited to, a touch-click or a mouse-click," Liao paragaph 0042; "Specifically, in response to detecting the mail viewing operation, the IM client may create the mail display window that is displayed independently from the target IM dialog window at a preset position of the target IM dialog window, such as a position on the right side, left side, upper side or lower side. Therefore, the target IM dialog window and the mail display window are displayed in parallel, so that the displayed mail information and dialog information are also displayed in parallel, and thus the user may more conveniently view the mail information and the dialog information at the same time, and the user experience is further improved. For example, FIG. 4 shows an example of a mail display window. An IM client in FIG. 4 is integrated in a PC. In response to detecting a mail viewing operation, a mail display window is automatically created on the right side of a target IM dialog window, so that the target IM dialog window and the mail display window may display information in parallel. FIG. 5 shows another example of a mail display window. An IM client in FIG. 5 is integrated in a mobile terminal. In response to detecting a mail viewing operation, due to a limited screen size, a target IM dialog window may be displayed in a reduced size, and a mail display window may be automatically created on the lower side of the reduced target IM dialog window," Liao paragraph 0045; Liao Figure 3 "Open Shared Mail" button; Liao Figure 4). Accordingly it would have been obvious to a person of ordinary skill in the art before the effective filing date of the claimed invention to modify the device of Fozdar to display the initial chatbot interface in full screen and display a control for displaying the data interaction result as taught by Liao. One would have been motivated to make such a combination so that the chatbot interface could be larger on the initial view only becoming smaller when the user chooses to display the additional data thus improving readability of the initial interface and improving user choice. As to claim 17, it is substantially similar to claim 2 and is therefore rejected using the same rationale as above. As to claim 18, it is substantially similar to claim 3 and is therefore rejected using the same rationale as above. Claims 4, 12 and 19 are rejected under 35 U.S.C. 103 as being unpatentable over Fozdar et al. (US 20250077538 A1, hereinafter Fozdar) in view of Liao (US 20230014265 A1) in further view of Tung et al. (US 20200134002 A1, hereinafter Tung). As to claim 4, Fozdar as modified by Liao further discloses the data interaction method according to claim 1, further comprising: displaying a switching control for switching a dataset to which displayed data belongs in the first display panel and displaying, in the first display panel, data in the target dataset ("The memory 524 further includes a database 532, which may be configured to store (among other data) various datasets that are suitable to undergo (or have already undergone) the natural language-based data integration process described herein," Fozdar paragraph 0063; "Turning now to FIG. 3B, the user has input the following natural language query into the text field 306: 'Add a copy activity that copies incremental data from SQL via Source1 into Container1/Folder1 via Destination1. Look up the country name from Table1 in SQL via Source1 to use as a parameter for copy source table in SQL.' In response to this natural language query, the natural language-based data integration system described herein has generated and output a corresponding data pipeline... As shown in the window 302, a number of buttons are then surfaced, including a 'Regenerate Pipeline' button 312, a 'Run Pipeline' button 314, and a 'Send Email When Any Activity Fails' button 316, as well as a second text field 318 that enables the user to direct the modification of the generated data pipeline, if desired," Fozdar paragraph 0044, multiple data sets are available and additional text input can change "Source1" to some other dataset). However neither Fozdar nor Liao appear to explicitly disclose in response to a trigger operation on the switching control, displaying selectable candidate datasets in the first display panel. Tung teaches in response to a trigger operation on the switching control, displaying selectable candidate datasets in the first display panel (“Rich text box engine 228 may also include functions and methods with a rich text box to enable functionality such as auto-completion and mentioning. For example, when users 102 enter a triggering character, e.g. ‘@’, a list of accounts, documents, live applications, and other components within the cloud collaboration platform may display in the rich text box. Users 102 may refine the displayed entities further by entering more characters or substrings. Users 102 may select, using a mouse or keyboard gesture, from the list of accounts, documents, and other components to auto-complete the mention within the rich text box. The auto-complete values, i.e., the options presenting for auto-completion, may be pulled by cloud collaboration platform 110 from data 122 via search module 116. Accordingly, a third-party live application need not access data about users or documents in the system to provide this functionality, furthering data security within the system. By using the auto-complete functionality within a rich text box embedded in a live application, developers may spare users 102 from entering an entire user name, document name, etc., to reference that entity within the live application,” Tung paragraph 0051). Accordingly it would have been obvious to a person of ordinary skill in the art before the effective filing date of the claimed invention to modify the method of Fozdar to show a list of candidate datasets as taught by Tung. One would have been motivated to make such a combination so that the user is spared from entering an entire document/dataset name thus resulting in less work and greater ease of use for the user (Tung paragraph 0051) As to claim 12, it is substantially similar to claim 4 and is therefore rejected using the same rationale as above. As to claim 19, it is substantially similar to claim 4 and is therefore rejected using the same rationale as above. Claims 5, 13 and 20 are rejected under 35 U.S.C. 103 as being unpatentable over Fozdar et al. (US 20250077538 A1, hereinafter Fozdar) in view of Liao (US 20230014265 A1) in further view of Chaudhuri et al. (US 20200394190 A1, hereinafter Chaudhuri). As to claim 5, Fozdar as modified by Liao further discloses the data interaction method according to claim 1, however neither Fozdar nor Liao appear to explicitly disclose a limitation further comprising: displaying a result feedback control for the data interaction result while the data interaction result is displayed, wherein the result feedback control comprises a first feedback control for representing positive feedback and/or a second feedback control for representing negative feedback; in response to a trigger operation on the first feedback control, using a positive feedback result corresponding to the first feedback control as a feedback result for the data interaction result, wherein the feedback result for the data interaction result is used by the data platform for function optimization; and in response to a trigger operation on the second feedback control, using a negative feedback result corresponding to the second feedback control as a feedback result for the data interaction result. Chaudhuri teaches a limitation further comprising: displaying a result feedback control for the data interaction result while the data interaction result is displayed, wherein the result feedback control comprises a first feedback control for representing positive feedback and/or a second feedback control for representing negative feedback (“FIG. 3 is an exemplary user interface, according to an embodiment of the present invention. As shown in FIG. 3, SQL queries may be executed against a database. At input 310, a user may enter a query in natural language. The input may be entered by the user via text or voice, selected from a set of options and/or other input or command. Additional specifics may be provided at 312, 314 and 316. These inputs may be predetermined and available via drop down windows. Other inputs may be provided. The result set may be transformed into various formats, including text 318, grid 320 and chart 322. The Graph representation of the intermediate query in a simplified format, the actual question asked, and the response may be sent back to the user interface. In addition, user interactions may be captured. For example, the amount of time spent by the user in each grid and the feedback button clicked, e.g., Bookmark, Incorrect, Correct or More options represented by 324, may be stored for further training and reinforced learning,” Chaudhuri paragraph 0054); in response to a trigger operation on the first feedback control, using a positive feedback result corresponding to the first feedback control as a feedback result for the data interaction result, wherein the feedback result for the data interaction result is used by the data platform for function optimization (“In addition, user interactions may be captured. For example, the amount of time spent by the user in each grid and the feedback button clicked, e.g., Bookmark, Incorrect, Correct or More options represented by 324, may be stored for further training and reinforced learning,” Chaudhuri paragraph 0054); and in response to a trigger operation on the second feedback control, using a negative feedback result corresponding to the second feedback control as a feedback result for the data interaction result (“In addition, user interactions may be captured. For example, the amount of time spent by the user in each grid and the feedback button clicked, e.g., Bookmark, Incorrect, Correct or More options represented by 324, may be stored for further training and reinforced learning,” Chaudhuri paragraph 0054). Accordingly it would have been obvious to a person of ordinary skill in the art before the effective filing date of the claimed invention to modify the method of Fozdar to allow the user to provide feedback on the data interaction result for function optimization as taught by Chaudhuri. One would have been motivated to make such a combination so that answers could become more relevant and more aligned with the user’s expectations over time thus resulting in less frustration for the user and greater utility for the finished product. As to claim 13, it is substantially similar to claim 5 and is therefore rejected using the same rationale as above. As to claim 20, it is substantially similar to claim 5 and is therefore rejected using the same rationale as above. Conclusion The prior art made of record and not relied upon is considered pertinent to applicant's disclosure: US 11068477 B1 to Tuckfield et al. discloses natural language processing with pre-specified SQL queries where data is pushed to a chat interface and where specific SQL statements can be output for display to the user; US 20180329993 A1 to Bedadala et al. discloses natural language processing integrated with database and data storage management where SQL queries are used to push data to the user in a chat interface; and US 20200044992 A1 to Kumar et al. discloses displaying data sets responsive to natural language messages received by chatbots where chat messages are displayed in a first panel of a chatbot interface and data sets are displayed in a second panel of the chatbot interface. Any inquiry concerning this communication or earlier communications from the examiner should be directed to DANIEL SAMWEL whose telephone number is (313) 446-6549. The examiner can normally be reached Monday through Thursday 8:00-6:00 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, Kieu Vu can be reached at (571) 272-4057. 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. /DANIEL SAMWEL/Primary Examiner, Art Unit 2171
Read full office action

Prosecution Timeline

Dec 13, 2024
Application Filed
Sep 22, 2026
Non-Final Rejection mailed — §103 (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12737050
USER INTERFACES FOR GESTURE DETECTION
2y 5m to grant Granted Sep 15, 2026
Patent 12730654
SYSTEM AND COMPUTER-IMPLEMENTED METHOD TO GENERATE A CONFIGURATION FOR EXTERNAL DATAPOINT ACCESS
3y 5m to grant Granted Sep 08, 2026
Patent 12724523
Information Display Method and Electronic Device
3y 0m to grant Granted Sep 01, 2026
Patent 12718507
SYSTEMS AND METHODS FOR SMART PLACEMENT OF VIRTUAL OBJECTS
2y 9m to grant Granted Aug 25, 2026
Patent 12693877
PERSONALIZED DATA PROCESSING EXPERIENCE AND CANVAS INTERFACES
2y 6m to grant Granted Jul 28, 2026
Study what changed to get past this examiner. Based on 5 most recent grants.

Strategy Recommendation AI-generated — please review before filing

Get a prosecution strategy drawn from examiner precedents, rejection analysis, and claim mapping.
Typically takes 5-10 seconds — AI-generated, attorney review required before filing

Prosecution Projections

1-2
Expected OA Rounds
75%
Grant Probability
99%
With Interview (+24.4%)
2y 8m (~10m remaining)
Median Time to Grant
Low
PTA Risk
Based on 368 resolved cases by this examiner. Grant probability derived from career allowance rate.

Sign in with your work email

Enter your email to receive a magic link. No password needed.

Personal email addresses (Gmail, Yahoo, etc.) are not accepted.

Free tier: 3 strategy analyses per month