Detailed Action
1. The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA . This is the initial office action based on the application filed on December 22nd, 2023, which claim 1-12, 15, 18-24 have been presented for examination.
Status of Claims
2. Claims 1-12, 15, 18-24 are pending in the application, of which claims 1, 7 and 15 are in independent form and these claims (1-12, 15, 18-24) are subject to following rejection(s) and/or objection(s) set forth in the following Office Action below.
Examiner Notes
3. (A). Information Disclosure Statement (IDS): The information disclosure statements filed on 01/05/2024 comply with the provisions of 37 CFR 1.97, 1.98. They have been placed in the application file and the information referred to therein has been considered as to the merits.
(B). Priority: Effective filing date considered for the following office action is 09/01/2021.
(C). Examiner has cited particular columns with line numbers, and/or paragraph numbers, references, or figures and NPL document (denoted with i.e. page 3:12-18 [12-18 represent line numbers]) in the references applied to the claims below 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 reference in entirety, as potentially teaching all or part of the claimed invention. Please see MPEP § 2141.02 and § 2123.
(D). Claimed limitations are provided with the Bold fonts in the art rejection in order to distinguish from the cited portion.
Claim Rejections – 35 USC §102
4. 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 –
(a)(1) the claimed invention was patented, described in a printed publication, or in public use, on sale or otherwise available to the public before the effective filing date of the claimed invention.
(a)(2) the claimed invention was described in a patent issued under section 151, or in an application for patent published or deemed published under section 122(b), in which the patent or application, as the case may be, names another inventor and was effectively filed before the effective filing date of the claimed invention.
5. Claims 1 and 15 are rejected under 35 U.S.C. 102(a)(1) as being anticipated by Shuai-qi Wang (CN 110928545 A -herein after Wang).
Per claim 1:
Wang discloses:
A method for processing a component (At least see page 2:15 - disclosure provides a method for distributing component), in comprising:
sending a block information entity request to a target platform, the block information entity request comprising a block identifier corresponding to a target component (At least see page 2:17-18 - receiving component obtaining request sent by a first terminal, the component acquisition request includes a target component identifier);
receiving a block information entity corresponding to the target component sent by the target platform (At least see page 2:19-20 - obtaining component information from the component library target component corresponding to the identifier of the target component); and
invoking a component software development kit to render the target component in a document based on the block information entity (At least see page 12:4-7 -development single page application can by way of example SDK acquisition component and reference component. Examples of assemblies may be page reference and rendering into a part of the page, to realize the function of the page).
Per claim 15:
Wang discloses:
An electronic device (At least see page 2:11-12 - disclosure provides a method for distributing assembly, single development method, device and storage medium page application), in comprising:
one or more processors (At least see page 17:26-2 - device 800 includes a processing component 822 further comprises one or more processors); and
a storage device for storing one or more programs which, when executed by the one or more processors (At least see page 17:27-29 memory resources represented by storage 832, for storing instruction execution by processing component 822, such as an application program. an application program stored in the memory 832), cause the one or more processors to perform acts comprising:
sending a block information entity request to a target platform, the block information entity request comprising a block identifier corresponding to a target component (At least see page 2:17-18 - receiving component obtaining request sent by a first terminal, the component acquisition request includes a target component identifier);
receiving a block information entity corresponding to the target component sent by the target platform (At least see page 2:19-20 - obtaining component information from the component library target component corresponding to the identifier of the target component); and
invoking a component software development kit to render the target component in a document based on the block information entity (At least see page 12:4-7 -development single page application can by way of example SDK acquisition component and reference component. Examples of assemblies may be page reference and rendering into a part of the page, to realize the function of the page).
6. Claims 7-12 are rejected under 35 U.S.C. 102(a)(2) as being anticipated by Islam et al. (US Patent Application Publication No. 2021/0303297 A1 -herein after Islam).
Per claim 7:
Islam discloses:
A method for processing a component (At least see ¶[0007] A computer implemented method is described, the method including, at a first server system providing one or more software services to one or more users), in comprising:
in response to receiving a trigger operation on a first target control in a document page (At least see ¶[0063] - user interface may display details of the task and include with the details a selectable button, icon, menu item or other user interface element that, when selected, causes display of the code associated with the task), displaying a component panel, the component panel comprising at least one target component (At least see ¶[0020] - software service comprises causing display of the code object (component) at the client system and providing the user with an interface for varying the code object and creating the varied code object [emphasis added]), and the first target control having a one-to-one correspondence with a content line in the document page (At least see ¶[0013] - document management service maintains a software code repository and the content of the at least one object is software code and wherein the varied content comprises an addition, the addition comprising at least one of a comment to the software code and metadata indicating an action to be performed by the document management service in relation to the software code); and
in response to a selection operation on the target component, displaying component content corresponding to the target component in a content line associated with the first target control in the document page (At least see ¶[0063] SaaS user interface may include a mechanism to invoke the on-premises client application 162 to obtain the code identifiers or the code itself. For example, the user may operate the on-premises client application 162 to access the document management service 130 and data repository 132 and pass, automatically or manually, the code identifier(s) or the relevant part of the code to the cloud server service 112).
Per claim 8:
Islam discloses:
in response to a focus selection of an empty content line in the document page, displaying the first target control at a position associated with the empty content line (At least see ¶[0055] - a field (empty content line) to input the nature of the task and a field to provide input that directly or indirectly specifies the identifier of code [emphasis added]).
Per claim 9:
Islam discloses:
in response to a focus selection of a non-empty content line in the document displaying a second target control at a position associated with the non-empty content line, the second target control being used to edit content in the content line (At least see ¶[0077] - screen display 500 provides an interface for varying the code. For example region 502 may be a text editing field).
Per claim 10:
Islam discloses:
displaying the component content corresponding to the target component in a line adjacent to the content line corresponding to the first target control (At least see FIG. 4 and FIG. 5 with associated text); or
displaying the component content corresponding to the target component in the content line corresponding to the first target control.
Per claim 11:
Islam discloses:
displaying component content corresponding to the target component in a content line associated with the first target control in the document page comprises:
expanding a range of the content line corresponding to the first target control, and displaying the component content corresponding to the target component in the expanded content line (At least see ¶[0058] - on-premises system 120 and/or the cloud server system associates with a task additional code to that of the code identifier or provides additional code beyond the stored association. Taking an example a task to review a line of code that was modified, then the additional code may be plus and minus 10 lines of code from the line of code that was modified).
Per claim 12:
Islam discloses:
displaying component content corresponding to the target component in a content line associated with the first target control in the document page comprises:
associating the component content corresponding to the target component with the content line to generate a component block, the component block being editable as a whole (At least see ¶[0071] - in relation to input that varies the code received in step 306 and displayed in step 308 (e.g. by adding new code, deleting existing code, or editing the code). The cloud server service 112 provides the user interface for receiving the input varying the code. The varied code is packaged for communication and communicated to the document management service 130 by the cloud proxy application 110. The document management service 130 then updates the code repository based on the received varied code).
Claim Rejections – 35 USC §103
7. 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 of this title, 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.
8. Claims 2-6 and 18-22 are rejected under 35 U.S.C. 103 as being unpatentable over Shuai-qi Wang (Chinese Patent Application Publication No. 2019/11226708 A -herein after Wang) in view of Islam et al. (US Patent Application Publication No. 2021/0303297 A1 -herein after Islam).
Per claim 2:
Wang sufficiently discloses the method as set forth above, but Wang does not explicitly disclose: wherein before the sending a block information entity request to a target platform, the method further comprises: in response to a trigger on a target component button, obtaining the block identifier corresponding to the target component.
However, Islam discloses:
wherein before the sending a block information entity request to a target platform, the method further comprises: in response to a trigger on a target component button, obtaining the block identifier corresponding to the target component (At least see ¶[0076] selectable button or icon 403 is provided together with the task information. Selection of the icon 403 causes a request for code associated with the task information displayed in the first region 401. For example, selection of the icon 403 may send to the cloud server system 102 a request for code associated with the task, which request is received and acted on as per process 301).
It would have been obvious to one ordinary skill in the art before the effective filing date of the claimed to incorporate Islam into Wang’s invention because information provided by the cloud server service is provided in a first region and/or a second region of the screen display, and the information in the first region may relate to a task to be performed in relation to code in the code repository and the information in the second region may relate to the project that the task forms a part of, which the information in the first region is updated based on user interactions with information provided in the second region; as such, the interactions may include, for example, navigating a plurality of tasks and selecting one of the tasks, with the information in the first region reflecting the selected task (please see ¶[0076]).
Per claim 3:
Wang however, discloses:
in response to a trigger on a target component button, obtaining a type identifier corresponding to the target component (At least see page 10:17-19 -component index directory according to the each component function, the component identifies the classification record of each component to facilitate faster index to the target component identification [emphasis added]);
displaying a first interface based on the type identifier, and obtaining a setting parameter input through the first interface (At least see page 10:8-9 - component distribution platform can be set in a component index index catalog, component directory can be recorded in a component identifier of each component in the component library);
sending a service instance creation request to a service side, the service instance creation request comprising the setting parameter to enable the service side to send a block creation request to the target platform, and the block creation request comprising the type identifier and the setting parameter to enable the target platform to generate the block information entity and establish a correspondence relationship between the block information entity and the block identifier (At least see page 12:18-21 -providing component for the development of single-page application distribution service, the front end development of single page application can obtain the resource service more refined, so as to realize for the development of single-page application providing micro-front service); and
receiving the block identifier sent by the service side, the block identifier of the service side being from the target platform (At least see page 6:19-21 -sending the component to obtain the request distribution to the assembly platform through the first terminal, component distribution platform from the component base to obtain component information of the target component corresponding to the target component identifier).
Per claim 4:
Islam also discloses:
in response to a trigger operation performed by a user on the document, displaying a list of components (At least see ¶[0059] -on-premises client application 162 may be operated independently of the cloud server service 112 or may both may configured so that when a task is generated an option is provided to invoke the on-premises client application 162 in order to access the document management service 130 and provide the code identifier(s) for the task), the list of components comprising the target component button (At least see ¶[0063] - user interface may display details of the task and include with the details a selectable button, icon, menu item or other user interface element that, when selected, causes display of the code associated with the task).
It would have been obvious to one ordinary skill in the art before the effective filing date of the claimed to incorporate Islam into Wang’s invention because information provided by the cloud server service is provided in a first region and/or a second region of the screen display, and the information in the first region may relate to a task to be performed in relation to code in the code repository and the information in the second region may relate to the project that the task forms a part of, which the information in the first region is updated based on user interactions with information provided in the second region; as such, the interactions may include, for example, navigating a plurality of tasks and selecting one of the tasks, with the information in the first region reflecting the selected task (please see ¶[0076]).
Per claim 5:
Wang also discloses:
in response to the trigger operation performed by the user on the document, obtaining an available component corresponding to the user based on a permission of the user (At least see page 8:19-22 -matched tool assembly 121 used to help page developer using the component distribution service provided by the distribution platform 110. running frame matched 121 and assembly tool distribution platform 110 of adaptation, the application tool 121, which can generate component acquisition request (developer permits) [emphasis added]).
Per claim 6:
Wang sufficiently discloses the method as set forth above, but Wang does not explicitly disclose: setting a host of the target component as the document.
However, Islam discloses:
setting a host of the target component as the document (At least see ¶[0063] -user interface includes a mechanism to selectively request or display code from the document management service 130. For instance, if a task has been set up in process 201, then the user interface may display details of the task and include with the details a selectable button, icon, menu item or other user interface element that, when selected, causes display of the code associated with the task).
It would have been obvious to one ordinary skill in the art before the effective filing date of the claimed to incorporate Islam into Wang’s invention because information provided by the cloud server service is provided in a first region and/or a second region of the screen display, and the information in the first region may relate to a task to be performed in relation to code in the code repository and the information in the second region may relate to the project that the task forms a part of, which the information in the first region is updated based on user interactions with information provided in the second region; as such, the interactions may include, for example, navigating a plurality of tasks and selecting one of the tasks, with the information in the first region reflecting the selected task (please see ¶[0076]).
Per claim 18:
Wang sufficiently discloses the device as set forth above, but Wang does not explicitly disclose: wherein before the sending a block information entity request to a target platform, the method further comprises: in response to a trigger on a target component button, obtaining the block identifier corresponding to the target component.
However, Islam discloses:
wherein before the sending a block information entity request to a target platform, the method further comprises: in response to a trigger on a target component button, obtaining the block identifier corresponding to the target component (At least see ¶[0076] selectable button or icon 403 is provided together with the task information. Selection of the icon 403 causes a request for code associated with the task information displayed in the first region 401. For example, selection of the icon 403 may send to the cloud server system 102 a request for code associated with the task, which request is received and acted on as per process 301).
It would have been obvious to one ordinary skill in the art before the effective filing date of the claimed to incorporate Islam into Wang’s invention because information provided by the cloud server service is provided in a first region and/or a second region of the screen display, and the information in the first region may relate to a task to be performed in relation to code in the code repository and the information in the second region may relate to the project that the task forms a part of, which the information in the first region is updated based on user interactions with information provided in the second region; as such, the interactions may include, for example, navigating a plurality of tasks and selecting one of the tasks, with the information in the first region reflecting the selected task (please see ¶[0076]).
Per claim 19:
Wang however, discloses:
in response to a trigger on a target component button, obtaining a type identifier corresponding to the target component (At least see page 10:17-19 -component index directory according to the each component function, the component identifies the classification record of each component to facilitate faster index to the target component identification [emphasis added]);
displaying a first interface based on the type identifier, and obtaining a setting parameter input through the first interface (At least see page 10:8-9 - component distribution platform can be set in a component index index catalog, component directory can be recorded in a component identifier of each component in the component library);
sending a service instance creation request to a service side, the service instance creation request comprising the setting parameter to enable the service side to send a block creation request to the target platform, and the block creation request comprising the type identifier and the setting parameter to enable the target platform to generate the block information entity and establish a correspondence relationship between the block information entity and the block identifier (At least see page 12:18-21 -providing component for the development of single-page application distribution service, the front end development of single page application can obtain the resource service more refined, so as to realize for the development of single-page application providing micro-front service); and
receiving the block identifier sent by the service side, the block identifier of the service side being from the target platform (At least see page 6:19-21 -sending the component to obtain the request distribution to the assembly platform through the first terminal, component distribution platform from the component base to obtain component information of the target component corresponding to the target component identifier).
Per claim 20:
Islam also discloses:
in response to a trigger operation performed by a user on the document, displaying a list of components (At least see ¶[0059] -on-premises client application 162 may be operated independently of the cloud server service 112 or may both may configured so that when a task is generated an option is provided to invoke the on-premises client application 162 in order to access the document management service 130 and provide the code identifier(s) for the task), the list of components comprising the target component button (At least see ¶[0063] - user interface may display details of the task and include with the details a selectable button, icon, menu item or other user interface element that, when selected, causes display of the code associated with the task).
It would have been obvious to one ordinary skill in the art before the effective filing date of the claimed to incorporate Islam into Wang’s invention because information provided by the cloud server service is provided in a first region and/or a second region of the screen display, and the information in the first region may relate to a task to be performed in relation to code in the code repository and the information in the second region may relate to the project that the task forms a part of, which the information in the first region is updated based on user interactions with information provided in the second region; as such, the interactions may include, for example, navigating a plurality of tasks and selecting one of the tasks, with the information in the first region reflecting the selected task (please see ¶[0076]).
Per claim 21:
Wang also discloses:
in response to the trigger operation performed by the user on the document, obtaining an available component corresponding to the user based on a permission of the user (At least see page 8:19-22 -matched tool assembly 121 used to help page developer using the component distribution service provided by the distribution platform 110. running frame matched 121 and assembly tool distribution platform 110 of adaptation, the application tool 121, which can generate component acquisition request (developer permits) [emphasis added]).
Per claim 22:
Wang sufficiently discloses the method as set forth above, but Wang does not explicitly disclose: setting a host of the target component as the document.
However, Islam discloses:
setting a host of the target component as the document (At least see ¶[0063] -user interface includes a mechanism to selectively request or display code from the document management service 130. For instance, if a task has been set up in process 201, then the user interface may display details of the task and include with the details a selectable button, icon, menu item or other user interface element that, when selected, causes display of the code associated with the task).
It would have been obvious to one ordinary skill in the art before the effective filing date of the claimed to incorporate Islam into Wang’s invention because information provided by the cloud server service is provided in a first region and/or a second region of the screen display, and the information in the first region may relate to a task to be performed in relation to code in the code repository and the information in the second region may relate to the project that the task forms a part of, which the information in the first region is updated based on user interactions with information provided in the second region; as such, the interactions may include, for example, navigating a plurality of tasks and selecting one of the tasks, with the information in the first region reflecting the selected task (please see ¶[0076]).
9. Claims 23-24 are rejected under 35 U.S.C. 103 as being unpatentable over Shuai-qi Wang (Chinese Patent Application Publication No. 2019/11226708 A -herein after Wang) in view of Richstein et al. (US Patent Application Publication No. 2018/0239601 A1 -herein after Richstein).
Per claim 23:
Wang sufficiently discloses the device as set forth above, but Wang does not explicitly disclose: target component is one or more of an instant messaging communication component, a timer, a workbench, or a calendar.
However, Reichstein discloses:
target component is one or more of an instant messaging communication component, a timer, a workbench, or a calendar (At least see ¶[0020] - component designer 114 may enable the user to select a calendar selection tool to achieve the same function as well (e.g., in which the user can select a particular date on a calendar, rather than using a scroll feature)).
It would have been obvious to one ordinary skill in the art before the effective filing date of the claimed invention to incorporate Reichstein into Wang’s invention because Reichstein teaching provides interactive a standard software development kit (SDK), which the interactive SDK documentation tool 102 provides a less time and resource consuming (developer and computing cycles), more efficient alternative to the standard programming model within ADE 104 with fewer opportunities for developer error; whereas, SDK kit reduces the time, learning curve, and computing cycles necessary to develop code for applications, and enable the developer to customize the style, arrangement, and features of the selected interface component(s) without coding (and thus without wasting computing cycles on debugging and compiling and testing the code), and may generate the corresponding program code for the developer (please see ¶[0017] and ¶[0018]).
Per claim 24:
Wang sufficiently discloses the method as set forth above, but Wang does not explicitly disclose: target component is one or more of an instant messaging communication component, a timer, a workbench, or a calendar.
However, Reichstein discloses:
target component is one or more of an instant messaging communication component, a timer, a workbench, or a calendar (At least see ¶[0020] - component designer 114 may enable the user to select a calendar selection tool to achieve the same function as well (e.g., in which the user can select a particular date on a calendar, rather than using a scroll feature)).
It would have been obvious to one ordinary skill in the art before the effective filing date of the claimed invention to incorporate Reichstein into Wang’s invention because Reichstein teaching provides interactive a standard software development kit (SDK), which the interactive SDK documentation tool 102 provides a less time and resource consuming (developer and computing cycles), more efficient alternative to the standard programming model within ADE 104 with fewer opportunities for developer error; whereas, SDK kit reduces the time, learning curve, and computing cycles necessary to develop code for applications, and enable the developer to customize the style, arrangement, and features of the selected interface component(s) without coding (and thus without wasting computing cycles on debugging and compiling and testing the code), and may generate the corresponding program code for the developer (please see ¶[0017] and ¶[0018]).
CONCLUSION
10. The prior art made of record and have yet relied upon is considered pertinent to applicant's disclosure, and will be frequently referred as to support the responses to the Applicant’s arguments. See MPEP § 707.05 For Examples:
I. Conley et al. (US 20180217820 A1) discloses “A platform interface may include a Graphical User Interface (GUI) presented by a platform that integrates applications. A platform interface displays information to a user and receives information from the user. A platform interface may include elements for receiving user input, such as radio buttons, text boxes, and scroll bars. As an example, a platform interface may include a button that allows a user to switch to one of the integrated applications” (please see [0005]).
II. Ali et al. (US 20170102925 A1) teaches “generating programming code from templates with API records stored using a data structure which corresponds to pointers included in the templates, wherein the templates are arranged in template sets such that two or more sets include two or more templates having pointers to the data structure in common wherein each set corresponds to a programming language to allow a selection of programming languages for code combined with any API selected and stored using the data structure” (please see [0026]), and “one or more servers each having memory and a processor and arranged to provide one or more of the following functional modules; an API description interface module for receiving a description of the API in a predetermined format; a parsing module arranged to parse the API description to generate a data structure (SDL) describing the API in a generic language; a plurality of programming environment templates; a user interface module for receiving a user selection of a programming environment; a transformation engine arranged to transform the data structure into an SDK using a said template corresponding to the selected programming environment” (please see [0087]).
III. Savliwala et al. (US 20160085521 A1) discloses “a user interface presented to a first application developer. The system includes a data store configured to store information identifying a plurality of functions. Each of the plurality of functions corresponds to external functionality available from third party applications. The system includes an app functionality management module configured to receive a selection from the first application developer of a first function of the plurality of functions to supplement functionality of a first application under development by the first application developer. The system includes a code generation module configured to provide a first software object to the first developer for incorporation into at least a first state of the first application. The first state includes a first user interface element associated with a first entity. The first software object includes instructions for, in response to user selection of the first user interface element, preparing a query wrapper including a combination of (i) a predefined text string corresponding to the first function and (ii) a name of the first entity. The first software object includes instructions for transmitting the query wrapper to a search system. The first software object includes instructions for receiving a result set from the search system. The result set includes a plurality of items. A first item of the plurality of items includes (i) an identifier of a target application and (ii) an access mechanism for a specified state of the target application. The first software object includes instructions for displaying the plurality of items. The first software object includes instructions for, in response to user selection of the first item, actuating the access mechanism to open the target application to the specified state” (please see [0006]).
IV. Perez et al. (US 20120047130 A1) discloses “automatically selecting at least one service for use with a modeled user interface (UI). One process includes operations for identifying a modeled UI at design time in an integrated development environment (IDE) and collecting a set of information associated with the modeled UI. At least one service repository storing a set of services is searched based at least in part on the collected set of information associated with the modeled UI. At least a portion of the set of services is presented via a graphical user interface associated with the IDE. A selection of at least one of the presented set of services is received, and an augmented version of the modeled UI is generated based on the received selection” (please see [0005]).
—o—o—o—
11. Any inquiry concerning this communication or earlier communications from the examiner should be directed to ZIAUL A. CHOWDHURY whose telephone number is (571)270-7750. The examiner can normally be reached on 9:30PM 6:30PM Monday -Friday.
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, Hyung S. Sough can be reached on 571-272-6799. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300.
Status information for published applications may be obtained from Patent Public Search tool (for all users) – A link to the Patent Public Search Tool is available at www. Uspto.gov/PatentPublicSearch. To find a U.S. patent or U.S. patent application publication, open the Patent Public Search tool by selecting “Start search”. Type the U.S. patent or U.S. patent application publication number in the “Search” panel without any punctuation and followed by an”.pn.”.
Should you have questions on access to the 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.
/ZIAUL A CHOWDHURY/ Primary Examiner, Art Unit 2192
02/06/2026