DETAILED ACTION
This action is responsive to the Applicant’s response filed 10/28/25.
As indicated in Applicant’s response, claims 2-21 have been added and claim 1 cancelled. Claims 2-21 are pending a next office action.
Claim Rejections - 35 USC § 103
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 2-8, 11-13, 15-17, 19-20 is/are rejected under § 35 U.S.C. 103 as being unpatentable over Baird et al, USPubN: 2009/0313601 (herein Baird) in view of and Bodin et al, USPubN: 2020/0159502 (herein Bodin) and Mandyam et al, USPN: 8,595,186 (herein Mandyam), further in view of Chawla et al, USPubN: 2014/0052617 (herein Chawla) and Frohwein, USPubN: 2010/0023874 (herein Frohwein)
As per claim 2, Baird discloses an information processing system providing services in cooperation with a cloud system, the information processing system comprising:
a providing server(mashup server – para 0048) to receive, from the service development terminal (Fig. 2B), a developed program (mashup design application 200 – para 0059, 0061) in which a program selected from the list of programs (mashup objects such as … container control palette, and widgets palette – para 0058 – Note0: objects selected from a palette such as container object or widget objects reads on one or more programs being self-contained, reusable SW like a widget - listed for reuse by a new development instance of a mashup application) is reused and embedded (“widget” refers to a self-contained and reusable software element … widget may be … a service call to a web service that is embeddable into a web page - para 0039); and
a component providing server (mashup server - para 0090; Figs. 1-2) including a widget repository (widget repositories – para 0067; Amazon widgets – para 0112; widget repository – para 0085) storing a plurality of widgets, the component providing server (discovery adapter, mashup design application, mashup server – para 0083-0084, 0090 – Note1: mashup service including backend widget repositories reads on component providing server to provide widgets in response to discovery and design actions of a mashup design environment) comprising at least one processor configured to:
provide, to a widget development terminal (widget discovery adapter, mashup design-time – para 0088; para 0096), a list of the widgets (widgets listed in widget pane, pane 402 also lists three widget repositories – para 0112) stored in the widget repository (see above);
an operator terminal (mashup design application, pane 206 includes a lists of … widgets … palettes from which the user select – para 0058; designing a mashup … associated with a given widget – para 0095) comprising at least one processor configured to create a page (para 0039) for providing a service (deployment information … used to deploy and execute a mashup … may include …data structures … assigned to different … services for execution – para 0072; user designing the mashup … visual programming … orchestration processes that execute their embedded business logic as web services – para 0097) by selecting a widget (select … such as … form palette … control palette, widgets palette – para 0058) obtained from the component providing server (see above) and embedding the selected widget in the page (para 0039; their embedded business logic as web services – para 0097; widget included in an application .. or a web page – para 0040), wherein the widget embedded in the page (para 0039 ) is associated with a program for providing the service (para 0038; a widget may be a URL or a service call – para 0039; mashup widgets can be utilized … like any other events from … workflows, forms and controls … like events that are raised at run-time by entities (services … that are external to the mashup – para 0093) corresponding to the page and which is obtained from the service providing server (mashup server - para 0090),
wherein the at least one processor of the service providing server is further configured to execute the program (execute their embedded business logic as web services – para 0097; the mashup is executed at a mashup server – para 0090) associated with the widget embedded in the page (para 0039; widget included in an application … or a web page – para 0040), whereby the widget embedded in the page (events … defined at design time for detection at runtime … loading of a page … and any other web page – para 0090) is operable to provide the corresponding service (para 0038; a widget may be a URL or a service call – para 0039)
A) Nor does Baird explicitly disclose component providing server configured to
receive, from the widget development terminal, a developed widget in which a widget selected from the list is reused and embedded; and
accumulate the developed widget received from the widget development terminal in the widget repository.
Bodin discloses a IDXDP implemented in a cloud environment (para 0010, 0055, 0086) or computing model (para 0086-0087; Fig. 1B) configured as SaaS (para 0088) with cloud resources and IDE (para 0125, 0128; Kony Visualizer within the IDE – para 0130) supported by a autonomous advisor (para 0067, 0071; DevOps advisor – para 0101) to recommend asset/objects from a list (para 0095) or forms (para 0067) enabling designers to selectively create/refine/contextualize widget applications (e.g. building of a particular asset such as a … widget – para 0111; para 0132-0134; para 0153), or services; e.g. to transform a given widget with extended functions found in repositories (suggest to users … enhance a given widget … extended functions … found in … repositories - para 0117) and/or restructure the created application into a second language (JSON format- para 0137, 0145) before committing the widget asset or design to repository (para 0006, para 0369; Fig. 5D) for further reuse by other widget design environments or IDEs in accordance to a different persona (para 0371-0374); hence cloud based development SaaS configured for accumulating developed widget asset received from a development terminal into a repository of structured assets destined recommending these via a IDE selection list/forms for reuse by another designer is recognized.
Mandyam also discloses repository of widgets obtained as result from a developer creating the widget via an API so the widget is uploaded for archiving on a server (col. 10 li. 52-59) on which the widget is validated, reconverted to markup representation and image contents then stored in a repository that is indexed with descriptors to be made accessible across applications as public resources (Fig. 41; col. 39 li. 38-67); hence server configured to a) receive, from the widget development terminal, a developed widget in which a widget can be further selected and reused in page embedded form; and b) accumulate the developed widget from the widget development terminal in the widget repository is recognized.
Thus, based on use mash server and remote repository of widgets as part of implementing widget services via selection form and widget palettes presented within instance of a mash application in Baird whereby one or more reusable widgets can be embedded in a page to implement a service, it would have been obvious for one of ordinary skill in the art before the effective filing date of the invention to implement the repositories of widget asset with use of a provisioning server in Baird so that the server – as in Mandyam - is configured to receive, from the widget development terminal, a developed widget in which a widget selected from the list – as in Bodin - is reused and embedded; and accumulate the developed widget received from the widget development terminal in the widget repository – as set forth in Bodin; because
widgets provided as network-based assets for developing multiple applications and services across cloud computing and enterprises/service environments not only can encompass uploaded developer’s persona, settings and initial context from which the widget was created, then validated/ ingested into a knowledge base as archive item restructured in portable format, image and/or re-deployable package within a reuse repository, but, as a fully accessible self-contained software component can also be fetched from the repository and imported any time into a variety of building contexts enabling a designer to initiate, customize and extend functionalities of widget applications, business transactions or service pages in which one such widget can operate as embedded component, the reuse aspect of widget provided as repository assets facilitating thereby construction of a wide range of web-based application and service rendering, notably when optimization of cloud resources is associated with provisioning of services to a large population of client subscribers.
B) Baird does not explicitly disclose system providing services in cooperation with a cloud system, and comprising
(i) a service providing server including a program repository storing a plurality of programs for providing respective corresponding services, and
at least one processor configured to:
provide, to a service development terminal, a list of the programs stored in the program repository;
(ii) receive, from the service development terminal, a developed program and accumulate the developed program received from the service development terminal in the program repository;
wherein the programs associated with the widgets are developed separately from the widgets, accumulated, and stored in the program repository.
Widget assets fetched from repositories to operate as embedded functionalities such as to implement services in Baird mashup development environment entails extension of the received widget with additional software, APIs or programs as part of the mashup developing a widget-based service or business functionalities.
In Baird’s adaptive aspect of a mashup runtime that implements a widget-bound processes or service execution, parameters, and specifications from repository of prestored definition or events (para 0072, 0094) are consulted to attach or extend functions to the visual rendering/design of a widget, such as adding components to perform authentication or sign-on functionalities associated with controlling dispatch of a service (para 0075) or seeking XML type binding definitions conducive to Javascript functions or service calls (para 0091) deployed in the course of events refreshed under the widget runtime. Hence, consulting a particular repository dedicated for runtime implementation data in order to generate the functional part of a widget design is recognized.
Chawla discloses API-tool in support of a merchant site (para 0063) for implementing a checkout service (Paypal payment – Fig 1A) among cloud services (para 0062) established via an UI and widget-based APIs, where the API-tool generates code which originate from XML-specifications based on which the merchant fetches and incorporates in the page source code representing the widget-embedded checkout functionality of the service, where the page and the widget code are registered as items of a catalog maintained by the merchant site forming the catalog APIs (para 0151) according to which, the merchant may select from the APIs to generate a widget embedded context (para 0154) for a particular function required of the merchant activity or query (Fig. 7B, 7C); hence cataloguing APIs for use by a merchant in implementing a function for a payment site that operates on widgets categories (para 0407) as part of embedded API functionalities entails pre-storing of programs (convertible from structured markup) as part of a vending tool to support implementation of a widget-based service and associated functions such as query, checkout in the sense that the prestored programs are created separate from the widgets is recognized.
Frohwein discloses a widget controller coupled with widget database (para 0089) in administrating widget operations within an integrated UI, providing selective presentation of widgets and implementing various widget management functions (para 0252) to carry out operations such as to add, forward configure a widget (Fig. 13-14), or direct social communications between sites or carry out authentication functions, present advertisement (Fig. 9-10) as well as dispatch queries and searches (para 0260) where the functions provided with the network widget services are basically pre-programmed (para 0003). Hence, fetching programs previously generated by developers then provided as pre-programmed functions for use by a controller in automatically extend widget control and management, as well as effecting advertisement services, discovery/search between sites under management by the widget controller is recognized.
Therefore, it would have been obvious for one of ordinary skill in the art before the effective filing date of the invention to establish a server capability in consulting a particular repository dedicated for runtime implementation data in order to generate the functional part of a widget design of Baird’s mashup environment so that the server operates in a cloud server/computing environment or support infrastructure – as in Chawla – where the server platform thereof is configured to
1) include a program repository storing a plurality of programs – as per Chawla and Frohwein - for providing respective corresponding services, and
provide, to a service development terminal, a list of the programs stored in the program repository – as per the catalog of APIs set forth in Chawla;
2) receive, from the service development terminal, a developed program (as per pre-programmed functions in Frohwein – and accumulate the developed program received from the service development terminal in the program repository – as set forth in 1);
wherein the programs associated with the widgets are developed separately from the widgets then accumulated and stored in the program repository – as set forth in Chawla and Frohwein; because
API or functions provided as network-based pre-compiled, executable programs or reusable assets in support for developing, instantiating operations required for multiple type of applications and cloud-based services across cloud NW and relevant enterprises/service environments not only can integrate uploaded developer’s core signature, parametric settings and initial metadata and variable declaration context from which these programs were created, then ingested into a reuse repository or catalog, often as restructured portable format – e.g. markup re-deployable package - which upon its import into a target environment would allow reconstruction of the pre-programmed function by a mashup environment as in Baird to attach functionality to a widget page instance, but, as a software asset fully accessible via a reuse repository, the program can also be fetched to configure and implement variety of operations and activities associated with a designer context to initiate, customize and extend functionalities of widget applications, or service pages based thereon in which widget page, via selective orchestration by the mashup service, can be implemented or extended with a specific functionality provided from one such imported functions, facilitating thereby construction of a wide range of operations permitted by web-based application/services as well as enhancing the widget development with provision of administrative utilities which are also configured from the same repository programs imported from remote.
C) Nor does Baird explicitly disclose
(i) when the widgets are developed, the stored programs are selected and associated with the corresponding widgets such that the widgets are operable to provide the services of the associated programs.
(ii) wherein the widget embedded in the page is operable to provide the corresponding service on the cloud system
Provision of widget embedded in page as part of a service to implement using widgets repositories associated with cloud computing environment has been shown Bodin, and provision of API to fetch in developing business widget service/payment is shown in Chawla cloud system, so that widget embedded page can be used to implement a corresponding cloud service as set forth in Chawla and Bodin, in that for each developed widget a programs or API stored remotely can be fetched and selectively associated in extending the core widget code, to augment its behavior or add a utility to its management.
Therefore, it would have been obvious for one of ordinary skill in the art before the effective filing date of the invention to implement use of separate repository of pre-configured programs and widgets as set forth above to orchestrate their use or reuse in the implementation of widget-based services or application under a corresponding cloud environment as set forth in Chawla and Bodin, enabling each widget embedded page to provide instance of cloud services by associating or pairing one such pre-built program with a widget, and so because of the same reasons set forth with the presentation of rationales A and B from above.
As per claim 3, Baird discloses system of claim 2, wherein the at least one processor of the service providing server is further configured to acquire history data obtained through provision of services of executed programs, (widgets that have been previously discovered … mashup design application … allow a user to publish specific instances of widgets … may also provide user interfaces that allow a user to search the repository for widgets of interest – para 0102-0103) analyze the history data (access a widget repository and determine the type of the widget specifications - para 0100) and generate proposals for new services (widget discover adapter … search the available widgets – para 0101; Fig. 4) based on the analyzed history data.
As per claim 4, Baird discloses system of claim 2, wherein the component providing server further comprises a content repository (event definition, data repository – para 0072; information from a repository … set of configuration files – para 0071) for reuse in creating the page (by location event definition … in the repository - para 0094)
Baird does not explicitly disclose server further comprises a media repository and is configured to provide lists of content items stored in the content repository and media items stored in the media repository for reuse in creating the page.
The visual design in Baird mashup UI includes forms and incorporation of images to edit a widget formation (Fig. 2B, 2C, 2D); hence incorporation of image from external storage is recognized.
Mandyam discloses content stored in repository for use in declaratory sections of a widget application and discovery API, where content includes video, sounds, text, images that are mostly transcoded, after validation, in markup format, archived (Fig. 41) and made accessible as indexed resources or versioned packages for use/extraction into or across various applications (col. 39 li. 34 to col. 40 li. 9) via downloading (col. 46 li. 32-44) the package (include images - col. 44 li. 47-54) for selective integration into a target widget (comic strips – col. 48 li. 10-22) based on user interacting with presented list of elements (series of elements – col. 54 li. 24-29; col. 54 li. 65 to col. 55 li. 4) or image choices (col. 54 li. 58-61) via a GUI (Figs 24-25; Fig. 40)
Hence, presented widget-related resources and images structured as repository content in form of list or choices for selection and integration by the user into a widget build instance is recognized.
Therefore, it would have been obvious for one of ordinary skill in the art before the effective filing date of the invention to implement repository of widget-build resources in Baird so that the repository would include content, configuration data as well as video, sound, image content – as in Mandyam - which can be preconfigured and made accessible for download or use by a widget design environment, where the content repository and media repository would be configured to provide lists of content items – as in Mandyam - stored in the content repository and media items stored in the media repository for reuse in creating the page; because
widget configuration and built toward a service or application to deploy often require configuration, parameterization as well as including therewith resources media/elements such as text, video, audio and images and providing repositories for administering configuration content and media content as set forth above, would provide a widget development users with a more flexible and enriched variety of importable resources, a wider availability of data content and media content with which to seek/inquire for discovery and offerings – via listing on a UI - enabling improved selection of widget resources, and facilitating user integration of the selection into formation of a media behavior associated with the widget embedded page on which a service is being carried out such as endeavored in Baird’s use of mashup approach.
As per claim 5, Baird does not explicitly disclose system of claim 2, wherein the list of service programs provided by the service providing server is displayed as a graphical user interface screen at the service development terminal.
But presenting via a UI list of programs or APIs (from a repository) for selection by a developer in the configuration and formation of widget page has been addressed as obvious per rationale B in claim 1; therefore, capability to present by a provisioning service, the list of service programs via a graphical user interface screen associated with context of the service development terminal would have been obvious for the reasons set with rationale B.
As per claim 6, Baird discloses system of claim 2, wherein the list of widgets provided by the component providing server is displayed (widgets listed in widget pane, pane 402 also lists three widget repositories – para 0112) as a graphical user interface screen at the widget development terminal.
As per claim 7, Baird does not explicitly disclose system of claim 2, wherein the widget repository stores parameters of the widgets, and the widget development terminal is configured to modify the parameters prior to returning the developed widget to the widget repository to thereby associate the widget with the program for providing the service, from among the programs stored in the program repository of the service providing server.
However, developed widget and parameterization thereof via a developer so that the customized or configured widgets can be returned for storage in a repository has been rendered by rationale A in claim 1, where accumulating developed widgets received from developers in a repository by the server is being addressed as obvious (using Bodin and Mandyam)
Further, a developer context that imports pre-programmed API or code to associate them with formation of widget behavior in developing widget-embedding application or service has been rendered obvious per rationale B in claim 1 (using Chawla and Frohwein).
Thus, use of widget repository for storing parameterized widgets in accordance with previous widget development terminal effect of modifying the parameters prior to returning the developed widget to the widget repository to enable another development context to associate the widget with the program from among the other programs stored in the program repository of the service providing server would be deemed obvious for the reasons set forth in combining obviousness of creating widget repository (from developers source) and programs repository (from developers sources) per rationale A and B from above.
As per claim 8, Baird does not explicitly disclose system of claim 2, wherein the operator terminal is further configured to transmit the created page to the component providing server which stores the created page in a page repository in which created pages are accumulated.
Baird discloses association of a contract with each widget so that a repository storing said contract (para 0098) can be accessed to learn on how to parameterize a new widget implementation (para 0100). Hence, recording a widget in terms of a contract with its functional implications in a repository is recognized.
Developer contexts that associate a widget with its functional components is shown in the formation of digital catalog by a merchant in Chawla, the catalog being authored by the merchant and configured to record executed widget applications (a checkout service – Fig. 12A, 12B) realized on a merchant site and capturing therewith state of the widget and all operations, metadata attached with its deployment, so that, via a API-tool platform, the merchant catalog can be consulted for information (para 0063; a consumer … to view a catalog from a merchant – para 0093) in the course of incorporating API and generating code for another checkout instance.
Therefore, it would have been obvious for one of ordinary skill in the art before the effective filing date of the invention to implement server associated with provisioning Baird’s widget framework so that a contract type repository is configured to record service pages, application data, widget developed with corresponding programs originated from a respective developer context – as in Chawla merchant sites - in terms of a knowledgebase that accumulates widget pages and code associated therewith into a repository that is accessible for use by other widget application builders; because
the information captured with each widget-embedded pages as well as program associated therewith by a authoring context, when accessible from a repository, can be consulted by other widget developing frameworks or widget page builder instances, in that reuse of persisted knowledge and implementation details obtained from past application experiences or developed services would significantly reduce effort and improvisation required of any developer context for having to follow construction steps or workflow that would otherwise dictate sequence of discovering/identifying a widget from scratch, search/selection corresponding programs from a storage source and integration of a paired widget/program into a selected widget in relevance to an instance of developing a given widget-embedded page or service as endeavored in Baird’ s mashup framework.
As per claims 11-12, Baird does not explicitly disclose system of claim 2,
(i) wherein the service providing server further accumulates a newly generated service program in the program repository, the newly generated service program being developed at the service development terminal and transmitted from the service development terminal to the service providing server.
(ii) wherein the component providing server further accumulates a newly generated widget in the widget repository, the newly generated widget being developed at the widget development terminal and transmitted from the widget development terminal to the component providing server.
Accumulating of newly developed programs into a repository of programs or APIs is shown as obvious per the rationale B in claim 1; and accumulating newly developed widgets into a respective repository is shown as obvious per rationale A in claim 1.
Hence, based thereon, it would have been obvious for one of ordinary skill in the art before the effective filing date of the invention to implement the information processing that relies on service provisioning server and component provisioning server in Baird so that
1) said service providing server would accumulate a newly generated service program in the program repository, the newly generated service program being developed at the service development terminal and transmitted from the service development terminal to the service providing server
2) said component providing server further accumulates a newly generated widget in the widget repository, the newly generated widget being developed at the widget development terminal and transmitted from the widget development terminal to the component providing server; because
of the same reasons set forth in rationale B and rationale A from above.
As per claim 13, Baird discloses system of claim 2, wherein each widget includes at least one parameter (para 0098-0099, 0101, 0103) for implementing the service, and defines an action to be performed (mashup event, at runtime triggers an action – claims 12-13, pg. 16; specifications and APIs for rendering a widget - e.g. the action that the widget can respond to, can broadcast – para 0040) when the page is viewed.
As per claim 15, Baird discloses system of claim 2, wherein the service providing server and the component providing server are implemented on separate hardware servers.
(refer to obviousness rationale for programs repository by a component providing server, and widgets repository provided by a component providing server in claim 1).
As per claim 16, Baird discloses an information processing method performed by an information processing system providing services in cooperation with a cloud system, the information processing system comprising (i) a service providing server (refer to claim 2) including a program repository storing a plurality of programs (refer to rationale B of claim 2) for providing respective corresponding services, the service providing server comprising at least one processor, (ii) a component providing server (refer to claim 2) including a widget repository storing a plurality of widgets, (iii) a service development terminal – refer to developer sources to supply programs per rationale B, (iv) a widget development terminal – refer to developers of widgets to upload per rationale A, and (v) an operator terminal (refer terminal to select and embed widget from below), the method comprising:
providing, by the service providing server, a list of the programs stored in the program repository (refer to rationale B of claim 2) to the service development terminal;
receiving, by the service providing server, from the service development terminal, a developed program in which a program selected from the list of programs (refer to rationale B of claim 2) is reused and embedded; accumulating, by the service providing server, the developed program received from the service development terminal in the program repository (refer to rationale B of claim 2);
providing, by the component providing server, a list of the widgets (refer to claim 2) stored in the widget repository to the widget development terminal;
receiving, by the component providing server, from the widget development terminal (refer to rationale A of claim 2), a developed widget in which a widget selected from the list is reused and embedded; accumulating, by the component providing server, the developed widget received from the widget development terminal in the widget repository (refer to rationale A of claim 2);
creating, by the operator terminal, a page for providing a service by selecting (refer to claim 2) a widget obtained from the component providing server and embedding (refer to claim 2) the selected widget in the page,
wherein the widget embedded in the page is associated with a program for providing the service corresponding to the page and which is obtained from the service providing server; and
executing, by the service providing server, the program associated with the widget embedded in the page, whereby the widget embedded in the page is operable to provide the corresponding service on the cloud system, (refer to rationale C of claim 2)
wherein the programs associated with the widgets are developed separately from the widgets (refer to claim 15), accumulated, and stored in the program repository, and, when the widgets are developed, the stored programs are selected and associated with the corresponding widgets such that the widgets are operable to provide the services (refer to rationale C of claim 2) of the associated programs.
As per claim 17, Baird discloses method of claim 16, further comprising:
acquiring, by the service providing server, history data obtained through provision of services of executed programs; analyzing the history data; and generating proposals for new services based on the analyzed history data.
(Refer to rationale of claim 3)
As per claim 19, Baird discloses a non-transitory computer-readable storage medium encoded with computer-readable instructions executable by at least one processor of an information processing system providing services in cooperation with a cloud system, the information processing system comprising (i) a service providing server including a program repository storing a plurality of programs for providing respective corresponding services, (ii) a component providing server including a widget repository storing a plurality of widgets, (iii) a service development terminal, (iv) a widget development terminal, and (v) an operator terminal, the computer-readable instructions being executable by the at least one processor to cause the at least one processor to perform functions comprising: controlling the service providing server to:
provide, to the service development terminal, a list of the programs stored in the program repository;
receive, from the service development terminal, a developed program in which a program selected from the list of programs is reused and embedded; and
accumulate the developed program received from the service development terminal in the program repository;
controlling the component providing server to:
provide, to the widget development terminal, a list of the widgets stored in the widget repository; receive, from the widget development terminal, a developed widget in which a widget selected from the list is reused and embedded; and accumulate the developed widget received from the widget development terminal in the widget repository; and
controlling the operator terminal to:
create a page for providing a service by selecting a widget obtained from the component providing server and embedding the selected widget in the page, wherein the widget embedded in the page is associated with a program for providing the service corresponding to the page and which is obtained from the service providing server; and
controlling the service providing server to execute the program associated with the widget embedded in the page, whereby the widget is operable to provide the corresponding service on the cloud system, wherein the programs associated with the widgets are developed separately from the widgets, accumulated, and stored in the program repository, and, when the widgets are developed, the stored programs are selected and associated with the corresponding widgets such that the widgets are operable to provide the services of the associated programs.
(all of which having been addressed in claim 16)
As per claim 20, Baird discloses non-transitory computer-readable storage medium of claim 19, wherein the computer-readable instructions are executable by the at least one processor to cause the at least one processor to perform further functions comprising controlling the service providing server to: acquire history data obtained through provision of services of executed programs; analyze the history data; and generate proposals for new services based on the analyzed history data.
(all of which having been addressed in claim 3)
Claims 9-10 is/are rejected under § 35 U.S.C. 103 as being unpatentable over Baird et al, USPubN: 2009/0313601 (herein Baird) in view of and Bodin et al, USPubN: 2020/0159502 (herein Bodin) and Mandyam et al, USPN: 8,595,186 (herein Mandyam), further in view of Chawla et al, USPubN: 2014/0052617 (herein Chawla) and Frohwein, USPubN: 2010/0023874 (herein Frohwein) further in view of Kong, Wen-guo, CN109460991, (translation) 03-12-2019, 8 pgs (herein Kong)
As per claims 9-10, Baird does not explicitly disclose system of claim 2,
(i) wherein the programs are cloud native programs executed through an application program interface in the cloud system.
(ii) wherein the service providing server and the component providing server cooperate with a plurality of external cloud systems to provide the service programs and the widgets.
Provision of widget embedded in page as part of a service to implement using widgets repositories associated with cloud computing environment has been shown Bodin, and provision of APIs to fetch in developing business widget service/payment is also shown in Chawla cloud system.
Secure platforms provided to cooperate with mobile device to implement a cloud-based service for payment data exchange system is shown in Wong NFC system (near-field financial payment) using a cloud platform (see Abstract) with communication exchange and connectivity to native application module for receiving and delivering information associated with payment transaction entities or bank processes (pg. 3) comprising authentication centre, bank system platform, third party payment platform, merchant management platform, user management platform, all included and connected to the cloud-based platform, where completion of a near-field financial payment operation is achieved by way of native program system using the security unit associated with the NFC and the mobile device (pg.7); hence a cloud-based system implementing a payment service in cooperatively connecting various cloud-attached subsystem or platforms and using contribution of cloud native program unit, and native application module to support completion of one such financial payment relating a security unit to a client mobile device is recognized.
Therefore, based on the service provisioning of programs and widgets being respectively implemented in cloud system by Chawla and Bodin, it would have been obvious for one of ordinary skill in the art before the effective filing date of the invention to implement the widget-based mashup framework in Baird so that the service providing server (to accumulate programs) and the component providing server (to accumulate widgets) would cooperate with a plurality of external cloud systems such as native, third party, financial management and security subsystems – as in Wong - to implement completion of the respective service orchestrated with the pairing the provided programs and widgets, where the provided programs are basically cloud native programs – as shown in Wong – so they are to be executed within each the widget page rendering - through an application program interface - in the cloud-based system as in Wong – for orchestrating communication and exchange with other cloud subsystems to implement rendering of a financial application service; because
using cloud native module and native programs as supply to the widget framework for effect to develop a service to be rendered using collaboration of cloud subsystems for completion of a financial service as set forth above not only makes efficient use of native executables provided by the very cloud native (development) sources but also would put into effective use of cloud-provided management control services and security subsystems, all enlisted from internal subsystems or cooperative entities set within the cloud infrastructure to enforce transaction, communication rules and business policies without the costly recourse to external software to obtain support for an administrative, management type and protective functionality that can be otherwise fetched or executed from within the pertinent entities of the very cloud infrastructure.
Claims 14, 18, 21 is/are rejected under § 35 U.S.C. 103 as being unpatentable over Baird et al, USPubN: 2009/0313601 (herein Baird) in view of and Bodin et al, USPubN: 2020/0159502 (herein Bodin) and Mandyam et al, USPN: 8,595,186 (herein Mandyam), further in view of Chawla et al, USPubN: 2014/0052617 (herein Chawla) and Frohwein, USPubN: 2010/0023874 (herein Frohwein) and further of Maxwell et al, USPubN: 2011/0060994 (herein Maxwell)
As per claim 14, Baird does not explicitly disclose system of claim 2, wherein the operator terminal is configured, in creating the page, to construct a new service flow by arranging a plurality of selected widgets associated with a plurality of programs for providing respective services in component arrangement areas of the page as contiguous blocks, and causing program codes of the programs for providing the plurality of respective services to be automatically generated sequentially according to an arrangement order of the selected widgets in the component arrangement areas of the page, to thereby construct the new service flow in which services of the programs associated with the plurality of selected widgets are sequentially executed.
Maxwell discloses service provider (Fig. 9) in connection with framework use of widgets configured on a CHUMBY device (para 0073) where the widgets are presented as blocks or diagrams to represent a service implementation (Figs 13-14) with timeline and sequential operations (para 0021, 0075, 0084) where the blocks, in some instance, can be arranged on a UI in series for execution (each widget as a function) for executing a flow order or in sequence (claim 27, claim 42 - pg. 34). Hence, contiguous arrangement of diagrams representing widget being configured in series for carry out a execution following a sequence order as part of rendering a service is recognized
Therefore, based on use of programs to attach to each widget for configuring a widget code underlying a page service to render per obviousness rationale C in claim 1, it would have been obvious at the time of the invention for one skill in the art to implement widget-based service in Baird so that
in creating the page to construct a new service flow, operating a service implementation framework based on widgets, would include arranging a plurality of selected widgets associated with a plurality of programs for providing respective services in component arrangement areas of the page as contiguous blocks – as per Maxwell arrangement of diagrams;
program codes of the programs provided (from repositories) for the plurality of respective services can be automatically generated sequentially according to an arrangement order of the selected widgets in the component arrangement areas of the page – as set forth in Maxwell to represent a service flow - to thereby construct the new service flow in which services – as represented in Maxwell - of the programs associated with the plurality of selected widgets are sequentially executed; because
use of a graphical tool to pre-arrange and configure expected behavior of a service flow by representing widgets in series of executing functions set in contiguous blocks as required for fulfilling the service would facilitate the code translation phase of the widget and service framework in which programs identified from remote sources can be automatically mapped into each widget diagrams so that a widget code can be compiled for each of such diagrams in accordance to a execution sequence enforced by a developer in placing and connecting blocks of a target service in a specific sequence or ordered arrangement by way of graphically representing the widget functions on a UI – as shown in Maxwell.
As per claim 18, refer to rationale of claim 14.
As per claim 21, refer to rationale of claim 14.
Response to Arguments
Applicant's arguments filed 10/28/25 have been fully considered but they are moot in light of the new grounds of rejection which have been necessitated by the Amendments.
Conclusion
THIS ACTION IS MADE FINAL. Applicant is reminded of the extension of time policy as set forth in 37 CFR 1.136(a).
A shortened statutory period for reply to this final action is set to expire THREE MONTHS from the mailing date of this action. In the event a first reply is filed within TWO MONTHS of the mailing date of this final action and the advisory action is not mailed until after the end of the THREE-MONTH shortened statutory period, then the shortened statutory period will expire on the date the advisory action is mailed, and any extension fee pursuant to 37 CFR 1.136(a) will be calculated from the mailing date of the advisory action. In no event, however, will the statutory period for reply expire later than SIX MONTHS from the mailing date of this final action.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to Tuan A Vu whose telephone number is (571) 272-3735. The examiner can normally be reached on 8AM-4:30PM/Mon-Fri.
If attempts to reach the examiner by telephone are unsuccessful, the examiner's supervisor, Chat Do can be reached on (571)272-3721.
The fax phone number for the organization where this application or proceeding is assigned is (571) 273-3735 ( for non-official correspondence - please consult Examiner before using) or 571-273-8300 ( for official correspondence) or redirected to customer service at 571-272-3609.
Any inquiry of a general nature or relating to the status of this application should be directed to the TC 2100 Group receptionist: 571-272-2100.
Information regarding the status of an application may be obtained from the Patent Application Information Retrieval (PAIR) system. Status information for published applications may be obtained from either Private PAIR or Public PAIR. Status information for unpublished applications is available through Private PAIR only. For more information about the PAIR system, see http://pair-direct.uspto.gov. Should you have questions on access to the Private PAIR system, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free).
/Tuan A Vu/
Primary Examiner, Art Unit 2193
Decembre 4, 2025