DETAILED ACTION
Applicant’s Application filed on July 31, 2024 has been reviewed.
Claims 1-20 have been examined.
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 .
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 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.
Priority
Acknowledgment is made of applicant's claim for foreign priority under 35 U.S.C. 119(a)-(d). The certified copy has been filed in Application No. INDIA 202411042331, filed on May 31, 2024.
The effective priority date for the subject matter in the pending claims in this application is May 31, 2024.
Information Disclosure Statement
The information disclosure statements (IDSs) submitted on August 28, 2024, April 29, 2025, August 19, 2025, October 6, 2025, November 12, 2025, February 18, 2026 and March 13, 2026 were filed. The submission is in compliance with the provisions of 37 CFR 1.97. Accordingly, the information disclosure statements are being considered by the examiner.
Claim Objections
Claim 9 is objected to because of the following informalities:
In claim 9, at line 1, “The computer-implemented method of Claim 1” should be changed to “The system of Claim 8”.
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 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.
The factual inquiries set forth in Graham v. John Deere Co., 383 U.S. 1, 148 USPQ 459 (1966), that are applied for establishing a background for determining obviousness under 35 U.S.C. 103 are summarized as follows:
1. Determining the scope and contents of the prior art.
2. Ascertaining the differences between the prior art and the claims at issue.
3. Resolving the level of ordinary skill in the pertinent art.
4. Considering objective evidence present in the application indicating obviousness or nonobviousness.
This application currently names joint inventors. In considering patentability of the claims the examiner presumes that the subject matter of the various claims was commonly owned as of the effective filing date of the claimed invention(s) absent any evidence to the contrary. Applicant is advised of the obligation under 37 CFR 1.56 to point out the inventor and effective filing dates of each claim that was not commonly owned as of the effective filing date of the later invention in order for the examiner to consider the applicability of 35 U.S.C. 102(b)(2)(C) for any potential 35 U.S.C. 102(a)(2) prior art against the later invention.
Claims 1-20 are rejected under 35 U.S.C. 103 as being unpatentable over DeGennaro et al. (US 2020/0137041 A1), hereinafter referred to as DeGennaro, in view of Wells (US 2017/0364369 A1), hereinafter referred to as Wells, and further in view of Bienkowski et al. (US 2024/0419817 A1), hereinafter referred to as Bienkowski.
With respect to claim 1, DeGennaro teaches A computer-implemented method comprising:
receiving, from a vendor layer via a web based portal running on an extensibility layer, an integration with a server (partners 210 access partner integration server 206 using partner protocol 214 via network 224, partner integration server 206 incorporate protocol translation 216 that enabled to translate or map various information provided using partner protocol 214 into information that is used or standardized by partner integration server 206, para. 0049), the integration including a plurality of data fields (partner integration server 206 enabled to support partner3 210-3 without performing authentication of user 106 with partner3 210-3, partner3 210-3 identified for user 106 based on user input of an identifier associated with partner3 210-3 (the offer code) or explicit user selection of partner3 210-3, , from a list of potential partner options, para. 0048), and an authentication mechanism (partner integration server 206 perform authentication of users 106 who operate media access client 202 by authenticating user 106 using internal user information, such as stored in admin repository 220, or by using the internal user information to authenticate user 106 at partner 210 on behalf of user 106 (also referred to as “proxy authentication” where partner integration server 206 is a proxy for user 106), partner integration server 206 enable authentication of users 106 directly with partner 210, without partner integration server 206 first authenticating user 106, para. 0053);
sending the integration to a data integration layer (the configuration data be stored in admin repository 220 and provided to media access client 202 from partner integration server 206;such a customization of media access client 202 desirable for branding media access client 202 according to a market identity of partner 210; because the configuration data stored with at least one of partner integration server 206 and admin repository 220, the customized display elements for partner 210 updated during operation of media access client 202, including without delay when a change is made with at least one of partner integration server 206 and admin repository 220, para. 0066);
receiving, in response to sending the integration to the data integration layer, configuration data having the integration data, and an address of a data store (the configuration data be stored in admin repository 220 and provided to media access client 202 from partner integration server 206;such a customization of media access client 202 desirable for branding media access client 202 according to a market identity of partner 210; because the configuration data stored with at least one of partner integration server 206 and admin repository 220, the customized display elements for partner 210 updated during operation of media access client 202, including without delay when a change is made with at least one of partner integration server 206 and admin repository 220, para. 0066; providing address to access to media objects stored in a media repository, para.0012).
DeGennaro does not explicitly teach the integration including an endpoint schema of the server,
However, Wells teaches the integration including an endpoint schema of the server (API service 132 can obtain the schema definition for the associated node in the API graph to determine if received query includes any parameters that are required for the subquery to successfully execute. If the schema definition indicates any specific parameters required to execute the subquery, API service 132 can count the number of parameters provided in the request to determine if the required parameters were included in the request, para. 0036) in order to allow a user to select data that the user wishes to view as taught by Wells (para. 0028),
Therefore, based on DeGennaro in view of Wells, it would have been obvious to one having ordinary skill in the art before the effective filing date of the claimed invention to utilize the teaching of Wells to the method of DeGennaro in order to allow a user to select data that the user wishes to view as taught by Wells (para. 0028).
DeGennaro in view of Wells does not explicitly teach the integration including one of data refresh intervals;
However, Bienkowski teaches the integration including one of data refresh intervals (API integrations, and the like created by the application 420 on behalf of the consumer; configuring properties of the application 420 such as refresh interval of tasks for ingestion, para. 0074) in order to providing dimensions for slicing and dicing data for visualizations as taught by Bienkowski (para. 0074);
Therefore, based on DeGennaro in view of Wells, and further in view of Bienkowski, it would have been obvious to one having ordinary skill in the art before the effective filing date of the claimed invention to utilize the teaching of Bienkowski to the method of DeGennaro in view of Wells in order to providing dimensions for slicing and dicing data for visualizations as taught by Bienkowski (para. 0074).
With respect to claim 2, DeGennaro teaches The computer-implemented method of Claim 1, further comprising:
sending, to an integration review interface running on the extensibility layer, the integration data of the integration (partner integration server 206 perform authentication of users 106 who operate media access client 202 by authenticating user 106 using internal user information, such as stored in admin repository 220, or by using the internal user information to authenticate user 106 at partner 210 on behalf of user 106 (also referred to as “proxy authentication” where partner integration server 206 is a proxy for user 106), partner integration server 206 enable authentication of users 106 directly with partner 210, without partner integration server 206 first authenticating user 106, para. 0053);
receiving approval, at the extensibility layer, of the integration (partner integration server 206 perform authentication of users 106 who operate media access client 202 by authenticating user 106 using internal user information, such as stored in admin repository 220, or by using the internal user information to authenticate user 106 at partner 210 on behalf of user 106 (also referred to as “proxy authentication” where partner integration server 206 is a proxy for user 106), partner integration server 206 enable authentication of users 106 directly with partner 210, without partner integration server 206 first authenticating user 106, para. 0053);
in response to the approval, authorizing the integration to be sent to the data broker layer for configuration (partner integration server 206 perform authentication of users 106 who operate media access client 202 by authenticating user 106 using internal user information, such as stored in admin repository 220, or by using the internal user information to authenticate user 106 at partner 210 on behalf of user 106 (also referred to as “proxy authentication” where partner integration server 206 is a proxy for user 106), partner integration server 206 enable authentication of users 106 directly with partner 210, without partner integration server 206 first authenticating user 106, para. 0053).
With respect to claim 3, DeGennaro teaches The computer-implemented method of Claim 1, further comprising:
sending, to a partner server, a plurality of integrations from the extensibility layer, the plurality of integrations including the integration (the configuration data be stored in admin repository 220 and provided to media access client 202 from partner integration server 206;such a customization of media access client 202 desirable for branding media access client 202 according to a market identity of partner 210; because the configuration data stored with at least one of partner integration server 206 and admin repository 220, the customized display elements for partner 210 updated during operation of media access client 202, including without delay when a change is made with at least one of partner integration server 206 and admin repository 220, para. 0066; providing address to access to media objects stored in a media repository, para.0012);
receiving, from the partner server, an integration of the plurality of integrations selected in a web interface of the partner server and authentication information for the integration (the configuration data be stored in admin repository 220 and provided to media access client 202 from partner integration server 206;such a customization of media access client 202 desirable for branding media access client 202 according to a market identity of partner 210; because the configuration data stored with at least one of partner integration server 206 and admin repository 220, the customized display elements for partner 210 updated during operation of media access client 202, including without delay when a change is made with at least one of partner integration server 206 and admin repository 220, para. 0066);
saving the authentication information for the integration at the extensibility layer (the configuration data be stored in admin repository 220 and provided to media access client 202 from partner integration server 206;such a customization of media access client 202 desirable for branding media access client 202 according to a market identity of partner 210; because the configuration data stored with at least one of partner integration server 206 and admin repository 220, the customized display elements for partner 210 updated during operation of media access client 202, including without delay when a change is made with at least one of partner integration server 206 and admin repository 220, para. 0066; providing address to access to media objects stored in a media repository, para.0012);
sending, to the data streaming service, an event indicating the integration is enabled (the configuration data be stored in admin repository 220 and provided to media access client 202 from partner integration server 206;such a customization of media access client 202 desirable for branding media access client 202 according to a market identity of partner 210; because the configuration data stored with at least one of partner integration server 206 and admin repository 220, the customized display elements for partner 210 updated during operation of media access client 202, including without delay when a change is made with at least one of partner integration server 206 and admin repository 220, para. 0066);
creating a stream for each data field of the given integration (the configuration data be stored in admin repository 220 and provided to media access client 202 from partner integration server 206;such a customization of media access client 202 desirable for branding media access client 202 according to a market identity of partner 210; because the configuration data stored with at least one of partner integration server 206 and admin repository 220, the customized display elements for partner 210 updated during operation of media access client 202, including without delay when a change is made with at least one of partner integration server 206 and admin repository 220, para. 0066); and
sending, to the partner server, data retrieved from the stream for each data field at the web interface of the partner server (the configuration data be stored in admin repository 220 and provided to media access client 202 from partner integration server 206;such a customization of media access client 202 desirable for branding media access client 202 according to a market identity of partner 210; because the configuration data stored with at least one of partner integration server 206 and admin repository 220, the customized display elements for partner 210 updated during operation of media access client 202, including without delay when a change is made with at least one of partner integration server 206 and admin repository 220, para. 0066; providing address to access to media objects stored in a media repository, para.0012).
With respect to claim 4, DeGennaro teaches The computer-implemented method of Claim 1, further comprising:
storing data received from the stream in a data store (the configuration data be stored in admin repository 220 and provided to media access client 202 from partner integration server 206;such a customization of media access client 202 desirable for branding media access client 202 according to a market identity of partner 210; because the configuration data stored with at least one of partner integration server 206 and admin repository 220, the customized display elements for partner 210 updated during operation of media access client 202, including without delay when a change is made with at least one of partner integration server 206 and admin repository 220, para. 0066; providing address to access to media objects stored in a media repository, para.0012).
With respect to claim 5, DeGennaro teaches The computer-implemented method of Claim 4, further comprising:
receiving, from the vendor layer via the web based portal, a first workspace configured to access the plurality of data fields of the integration (partners 210 access partner integration server 206 using partner protocol 214 via network 224, partner integration server 206 incorporate protocol translation 216 that enabled to translate or map various information provided using partner protocol 214 into information that is used or standardized by partner integration server 206, para. 0049);
receiving, from the vendor layer via the web based portal, a second workspace configured to access the plurality of data fields of the integration (partners 210 access partner integration server 206 using partner protocol 214 via network 224, partner integration server 206 incorporate protocol translation 216 that enabled to translate or map various information provided using partner protocol 214 into information that is used or standardized by partner integration server 206, para. 0049);
wherein the first workplace and the second workspace are configured to access the plurality of data fields via the data store (the configuration data be stored in admin repository 220 and provided to media access client 202 from partner integration server 206;such a customization of media access client 202 desirable for branding media access client 202 according to a market identity of partner 210; because the configuration data stored with at least one of partner integration server 206 and admin repository 220, the customized display elements for partner 210 updated during operation of media access client 202, including without delay when a change is made with at least one of partner integration server 206 and admin repository 220, para. 0066; providing address to access to media objects stored in a media repository, para.0012).
With respect to claim 6, DeGennaro teaches The computer-implemented method of Claim 4, further comprising:
receiving, from the vendor layer via the web based portal, a first gauge configured to access the plurality of data fields of the integration (partners 210 access partner integration server 206 using partner protocol 214 via network 224, partner integration server 206 incorporate protocol translation 216 that enabled to translate or map various information provided using partner protocol 214 into information that is used or standardized by partner integration server 206, para. 0049);
receiving, from the vendor layer via the web based portal, a second gauge configured to access the plurality of data fields of the integration (partners 210 access partner integration server 206 using partner protocol 214 via network 224, partner integration server 206 incorporate protocol translation 216 that enabled to translate or map various information provided using partner protocol 214 into information that is used or standardized by partner integration server 206, para. 0049);
wherein the first gauge and the second gauge are configured to access the plurality of data fields via the data store (the configuration data be stored in admin repository 220 and provided to media access client 202 from partner integration server 206;such a customization of media access client 202 desirable for branding media access client 202 according to a market identity of partner 210; because the configuration data stored with at least one of partner integration server 206 and admin repository 220, the customized display elements for partner 210 updated during operation of media access client 202, including without delay when a change is made with at least one of partner integration server 206 and admin repository 220, para. 0066; providing address to access to media objects stored in a media repository, para.0012).
With respect to claim 7, DeGennaro teaches The computer-implemented method of Claim 1, further comprising:
extracting raw data from the server at the data integration layer using the endpoint schema of the integration (partner integration server 206 perform authentication of users 106 who operate media access client 202 by authenticating user 106 using internal user information, such as stored in admin repository 220, or by using the internal user information to authenticate user 106 at partner 210 on behalf of user 106 (also referred to as “proxy authentication” where partner integration server 206 is a proxy for user 106), partner integration server 206 enable authentication of users 106 directly with partner 210, without partner integration server 206 first authenticating user 106, para. 0053);
transforming the data at a data transformation layer (partner integration server 206 perform authentication of users 106 who operate media access client 202 by authenticating user 106 using internal user information, such as stored in admin repository 220, or by using the internal user information to authenticate user 106 at partner 210 on behalf of user 106 (also referred to as “proxy authentication” where partner integration server 206 is a proxy for user 106), partner integration server 206 enable authentication of users 106 directly with partner 210, without partner integration server 206 first authenticating user 106, para. 0053).
With respect to claim 8, DeGennaro teaches A system comprising:
a computing node comprising a computer readable storage medium having program instructions embodied therewith, the program instructions executable by a processor of the computing node to cause the processor to perform a method (a processor and memory media accessible to the processor storing instructions executable by the processor, para. 0012) comprising:
receiving, from a vendor layer via a web based portal running on an extensibility layer, an integration with a server (partners 210 access partner integration server 206 using partner protocol 214 via network 224, partner integration server 206 incorporate protocol translation 216 that enabled to translate or map various information provided using partner protocol 214 into information that is used or standardized by partner integration server 206, para. 0049), the integration including a plurality of data fields (partner integration server 206 enabled to support partner3 210-3 without performing authentication of user 106 with partner3 210-3, partner3 210-3 identified for user 106 based on user input of an identifier associated with partner3 210-3 (the offer code) or explicit user selection of partner3 210-3, , from a list of potential partner options, para. 0048), and an authentication mechanism (partner integration server 206 perform authentication of users 106 who operate media access client 202 by authenticating user 106 using internal user information, such as stored in admin repository 220, or by using the internal user information to authenticate user 106 at partner 210 on behalf of user 106 (also referred to as “proxy authentication” where partner integration server 206 is a proxy for user 106), partner integration server 206 enable authentication of users 106 directly with partner 210, without partner integration server 206 first authenticating user 106, para. 0053);
sending the integration to a data integration layer (the configuration data be stored in admin repository 220 and provided to media access client 202 from partner integration server 206;such a customization of media access client 202 desirable for branding media access client 202 according to a market identity of partner 210; because the configuration data stored with at least one of partner integration server 206 and admin repository 220, the customized display elements for partner 210 updated during operation of media access client 202, including without delay when a change is made with at least one of partner integration server 206 and admin repository 220, para. 0066);
receiving, in response to sending the integration to the data integration layer, configuration data having the integration data, and an address of a data store (the configuration data be stored in admin repository 220 and provided to media access client 202 from partner integration server 206;such a customization of media access client 202 desirable for branding media access client 202 according to a market identity of partner 210; because the configuration data stored with at least one of partner integration server 206 and admin repository 220, the customized display elements for partner 210 updated during operation of media access client 202, including without delay when a change is made with at least one of partner integration server 206 and admin repository 220, para. 0066; providing address to access to media objects stored in a media repository, para.0012).
DeGennaro does not explicitly teach the integration including an endpoint schema of the server,
However, Wells teaches the integration including an endpoint schema of the server (API service 132 can obtain the schema definition for the associated node in the API graph to determine if received query includes any parameters that are required for the subquery to successfully execute. If the schema definition indicates any specific parameters required to execute the subquery, API service 132 can count the number of parameters provided in the request to determine if the required parameters were included in the request, para. 0036) in order to allow a user to select data that the user wishes to view as taught by Wells (para. 0028),
Therefore, based on DeGennaro in view of Wells, it would have been obvious to one having ordinary skill in the art before the effective filing date of the claimed invention to utilize the teaching of Wells to the method of DeGennaro in order to allow a user to select data that the user wishes to view as taught by Wells (para. 0028).
DeGennaro in view of Wells does not explicitly teach the integration including one of data refresh intervals;
However, Bienkowski teaches the integration including one of data refresh intervals (API integrations, and the like created by the application 420 on behalf of the consumer; configuring properties of the application 420 such as refresh interval of tasks for ingestion, para. 0074) in order to providing dimensions for slicing and dicing data for visualizations as taught by Bienkowski (para. 0074);
Therefore, based on DeGennaro in view of Wells, and further in view of Bienkowski, it would have been obvious to one having ordinary skill in the art before the effective filing date of the claimed invention to utilize the teaching of Bienkowski to the method of DeGennaro in view of Wells in order to providing dimensions for slicing and dicing data for visualizations as taught by Bienkowski (para. 0074).
With respect to claim 9, DeGennaro teaches The computer-implemented method of Claim 1, further comprising:
sending, to an integration review interface running on the extensibility layer, the integration data of the integration (partner integration server 206 perform authentication of users 106 who operate media access client 202 by authenticating user 106 using internal user information, such as stored in admin repository 220, or by using the internal user information to authenticate user 106 at partner 210 on behalf of user 106 (also referred to as “proxy authentication” where partner integration server 206 is a proxy for user 106), partner integration server 206 enable authentication of users 106 directly with partner 210, without partner integration server 206 first authenticating user 106, para. 0053);
receiving approval, at the extensibility layer, of the integration (partner integration server 206 perform authentication of users 106 who operate media access client 202 by authenticating user 106 using internal user information, such as stored in admin repository 220, or by using the internal user information to authenticate user 106 at partner 210 on behalf of user 106 (also referred to as “proxy authentication” where partner integration server 206 is a proxy for user 106), partner integration server 206 enable authentication of users 106 directly with partner 210, without partner integration server 206 first authenticating user 106, para. 0053);
in response to the approval, authorizing the integration to be sent to the data broker layer for configuration (partner integration server 206 perform authentication of users 106 who operate media access client 202 by authenticating user 106 using internal user information, such as stored in admin repository 220, or by using the internal user information to authenticate user 106 at partner 210 on behalf of user 106 (also referred to as “proxy authentication” where partner integration server 206 is a proxy for user 106), partner integration server 206 enable authentication of users 106 directly with partner 210, without partner integration server 206 first authenticating user 106, para. 0053).
With respect to claim 10, DeGennaro teaches The system of Claim 9, further comprising:
sending, to a partner server, a plurality of integrations from the extensibility layer, the plurality of integrations including the integration (the configuration data be stored in admin repository 220 and provided to media access client 202 from partner integration server 206;such a customization of media access client 202 desirable for branding media access client 202 according to a market identity of partner 210; because the configuration data stored with at least one of partner integration server 206 and admin repository 220, the customized display elements for partner 210 updated during operation of media access client 202, including without delay when a change is made with at least one of partner integration server 206 and admin repository 220, para. 0066; providing address to access to media objects stored in a media repository, para.0012);
receiving, from the partner server, an integration of the plurality of integrations selected in a web interface of the partner server and authentication information for the integration (the configuration data be stored in admin repository 220 and provided to media access client 202 from partner integration server 206;such a customization of media access client 202 desirable for branding media access client 202 according to a market identity of partner 210; because the configuration data stored with at least one of partner integration server 206 and admin repository 220, the customized display elements for partner 210 updated during operation of media access client 202, including without delay when a change is made with at least one of partner integration server 206 and admin repository 220, para. 0066);
saving the authentication information for the integration at the extensibility layer (the configuration data be stored in admin repository 220 and provided to media access client 202 from partner integration server 206;such a customization of media access client 202 desirable for branding media access client 202 according to a market identity of partner 210; because the configuration data stored with at least one of partner integration server 206 and admin repository 220, the customized display elements for partner 210 updated during operation of media access client 202, including without delay when a change is made with at least one of partner integration server 206 and admin repository 220, para. 0066; providing address to access to media objects stored in a media repository, para.0012);
sending, to the data streaming service, an event indicating the integration is enabled (the configuration data be stored in admin repository 220 and provided to media access client 202 from partner integration server 206;such a customization of media access client 202 desirable for branding media access client 202 according to a market identity of partner 210; because the configuration data stored with at least one of partner integration server 206 and admin repository 220, the customized display elements for partner 210 updated during operation of media access client 202, including without delay when a change is made with at least one of partner integration server 206 and admin repository 220, para. 0066; providing address to access to media objects stored in a media repository, para.0012);
creating a stream for each data field of the given integration (the configuration data be stored in admin repository 220 and provided to media access client 202 from partner integration server 206;such a customization of media access client 202 desirable for branding media access client 202 according to a market identity of partner 210; because the configuration data stored with at least one of partner integration server 206 and admin repository 220, the customized display elements for partner 210 updated during operation of media access client 202, including without delay when a change is made with at least one of partner integration server 206 and admin repository 220, para. 0066; providing address to access to media objects stored in a media repository, para.0012); and
sending, to the partner server, data retrieved from the stream for each data field at the web interface of the partner server (the configuration data be stored in admin repository 220 and provided to media access client 202 from partner integration server 206;such a customization of media access client 202 desirable for branding media access client 202 according to a market identity of partner 210; because the configuration data stored with at least one of partner integration server 206 and admin repository 220, the customized display elements for partner 210 updated during operation of media access client 202, including without delay when a change is made with at least one of partner integration server 206 and admin repository 220, para. 0066; providing address to access to media objects stored in a media repository, para.0012).
With respect to claim 11, DeGennaro teaches The system of Claim 9, further comprising:
storing data received from the stream in a data store (the configuration data be stored in admin repository 220 and provided to media access client 202 from partner integration server 206;such a customization of media access client 202 desirable for branding media access client 202 according to a market identity of partner 210; because the configuration data stored with at least one of partner integration server 206 and admin repository 220, the customized display elements for partner 210 updated during operation of media access client 202, including without delay when a change is made with at least one of partner integration server 206 and admin repository 220, para. 0066; providing address to access to media objects stored in a media repository, para.0012).
With respect to claim 12, DeGennaro teaches The system of Claim 9, further comprising:
receiving, from the vendor layer via the web based portal, a first workspace configured to access the plurality of data fields of the integration (partners 210 access partner integration server 206 using partner protocol 214 via network 224, partner integration server 206 incorporate protocol translation 216 that enabled to translate or map various information provided using partner protocol 214 into information that is used or standardized by partner integration server 206, para. 0049);
receiving, from the vendor layer via the web based portal, a second workspace configured to access the plurality of data fields of the integration (partners 210 access partner integration server 206 using partner protocol 214 via network 224, partner integration server 206 incorporate protocol translation 216 that enabled to translate or map various information provided using partner protocol 214 into information that is used or standardized by partner integration server 206, para. 0049);
wherein the first workplace and the second workspace are configured to access the plurality of data fields via the data store (the configuration data be stored in admin repository 220 and provided to media access client 202 from partner integration server 206;such a customization of media access client 202 desirable for branding media access client 202 according to a market identity of partner 210; because the configuration data stored with at least one of partner integration server 206 and admin repository 220, the customized display elements for partner 210 updated during operation of media access client 202, including without delay when a change is made with at least one of partner integration server 206 and admin repository 220, para. 0066; providing address to access to media objects stored in a media repository, para.0012).
With respect to claim 13, DeGennaro teaches The system of Claim 12, further comprising:
receiving, from the vendor layer via the web based portal, a first gauge configured to access the plurality of data fields of the integration (partners 210 access partner integration server 206 using partner protocol 214 via network 224, partner integration server 206 incorporate protocol translation 216 that enabled to translate or map various information provided using partner protocol 214 into information that is used or standardized by partner integration server 206, para. 0049);
receiving, from the vendor layer via the web based portal, a second gauge configured to access the plurality of data fields of the integration (partners 210 access partner integration server 206 using partner protocol 214 via network 224, partner integration server 206 incorporate protocol translation 216 that enabled to translate or map various information provided using partner protocol 214 into information that is used or standardized by partner integration server 206, para. 0049);
wherein the first gauge and the second gauge are configured to access the plurality of data fields via the data store (the configuration data be stored in admin repository 220 and provided to media access client 202 from partner integration server 206;such a customization of media access client 202 desirable for branding media access client 202 according to a market identity of partner 210; because the configuration data stored with at least one of partner integration server 206 and admin repository 220, the customized display elements for partner 210 updated during operation of media access client 202, including without delay when a change is made with at least one of partner integration server 206 and admin repository 220, para. 0066; providing address to access to media objects stored in a media repository, para.0012).
With respect to claim 14, DeGennaro teaches The system of Claim 9, further comprising:
extracting raw data from the server at the data integration layer using the endpoint schema of the integration (partner integration server 206 perform authentication of users 106 who operate media access client 202 by authenticating user 106 using internal user information, such as stored in admin repository 220, or by using the internal user information to authenticate user 106 at partner 210 on behalf of user 106 (also referred to as “proxy authentication” where partner integration server 206 is a proxy for user 106), partner integration server 206 enable authentication of users 106 directly with partner 210, without partner integration server 206 first authenticating user 106, para. 0053);
transforming the data at a data transformation layer (partner integration server 206 perform authentication of users 106 who operate media access client 202 by authenticating user 106 using internal user information, such as stored in admin repository 220, or by using the internal user information to authenticate user 106 at partner 210 on behalf of user 106 (also referred to as “proxy authentication” where partner integration server 206 is a proxy for user 106), partner integration server 206 enable authentication of users 106 directly with partner 210, without partner integration server 206 first authenticating user 106, para. 0053).
With respect to claim 15, DeGennaro teaches A computer program product for generating an integration, the computer program product comprising a computer readable storage medium having program instructions embodied therewith, the program instructions executable by a processor to cause the processor to perform a method (a processor and memory media accessible to the processor storing instructions executable by the processor, para. 0012) comprising:
receiving, from a vendor layer via a web based portal running on an extensibility layer, an integration with a server (partners 210 access partner integration server 206 using partner protocol 214 via network 224, partner integration server 206 incorporate protocol translation 216 that enabled to translate or map various information provided using partner protocol 214 into information that is used or standardized by partner integration server 206, para. 0049), the integration including a plurality of data fields (partner integration server 206 enabled to support partner3 210-3 without performing authentication of user 106 with partner3 210-3, partner3 210-3 identified for user 106 based on user input of an identifier associated with partner3 210-3 (the offer code) or explicit user selection of partner3 210-3, , from a list of potential partner options, para. 0048), and an authentication mechanism (partner integration server 206 perform authentication of users 106 who operate media access client 202 by authenticating user 106 using internal user information, such as stored in admin repository 220, or by using the internal user information to authenticate user 106 at partner 210 on behalf of user 106 (also referred to as “proxy authentication” where partner integration server 206 is a proxy for user 106), partner integration server 206 enable authentication of users 106 directly with partner 210, without partner integration server 206 first authenticating user 106, para. 0053);
sending the integration to a data integration layer (the configuration data be stored in admin repository 220 and provided to media access client 202 from partner integration server 206;such a customization of media access client 202 desirable for branding media access client 202 according to a market identity of partner 210; because the configuration data stored with at least one of partner integration server 206 and admin repository 220, the customized display elements for partner 210 updated during operation of media access client 202, including without delay when a change is made with at least one of partner integration server 206 and admin repository 220, para. 0066);
receiving, in response to sending the integration to the data integration layer, configuration data having the integration data, and an address of a data store (the configuration data be stored in admin repository 220 and provided to media access client 202 from partner integration server 206;such a customization of media access client 202 desirable for branding media access client 202 according to a market identity of partner 210; because the configuration data stored with at least one of partner integration server 206 and admin repository 220, the customized display elements for partner 210 updated during operation of media access client 202, including without delay when a change is made with at least one of partner integration server 206 and admin repository 220, para. 0066; providing address to access to media objects stored in a media repository, para.0012).
DeGennaro does not explicitly teach the integration including an endpoint schema of the server,
However, Wells teaches the integration including an endpoint schema of the server (API service 132 can obtain the schema definition for the associated node in the API graph to determine if received query includes any parameters that are required for the subquery to successfully execute. If the schema definition indicates any specific parameters required to execute the subquery, API service 132 can count the number of parameters provided in the request to determine if the required parameters were included in the request, para. 0036) in order to allow a user to select data that the user wishes to view as taught by Wells (para. 0028),
Therefore, based on DeGennaro in view of Wells, it would have been obvious to one having ordinary skill in the art before the effective filing date of the claimed invention to utilize the teaching of Wells to the product of DeGennaro in order to allow a user to select data that the user wishes to view as taught by Wells (para. 0028).
DeGennaro in view of Wells does not explicitly teach the integration including one of data refresh intervals;
However, Bienkowski teaches the integration including one of data refresh intervals (API integrations, and the like created by the application 420 on behalf of the consumer; configuring properties of the application 420 such as refresh interval of tasks for ingestion, para. 0074) in order to providing dimensions for slicing and dicing data for visualizations as taught by Bienkowski (para. 0074);
Therefore, based on DeGennaro in view of Wells, and further in view of Bienkowski, it would have been obvious to one having ordinary skill in the art before the effective filing date of the claimed invention to utilize the teaching of Bienkowski to the product of DeGennaro in view of Wells in order to providing dimensions for slicing and dicing data for visualizations as taught by Bienkowski (para. 0074).
With respect to claim 16, DeGennaro teaches The computer program product of Claim 15, further comprising:
sending, to an integration review interface running on the extensibility layer, the integration data of the integration (partner integration server 206 perform authentication of users 106 who operate media access client 202 by authenticating user 106 using internal user information, such as stored in admin repository 220, or by using the internal user information to authenticate user 106 at partner 210 on behalf of user 106 (also referred to as “proxy authentication” where partner integration server 206 is a proxy for user 106), partner integration server 206 enable authentication of users 106 directly with partner 210, without partner integration server 206 first authenticating user 106, para. 0053);
receiving approval, at the extensibility layer, of the integration (partner integration server 206 perform authentication of users 106 who operate media access client 202 by authenticating user 106 using internal user information, such as stored in admin repository 220, or by using the internal user information to authenticate user 106 at partner 210 on behalf of user 106 (also referred to as “proxy authentication” where partner integration server 206 is a proxy for user 106), partner integration server 206 enable authentication of users 106 directly with partner 210, without partner integration server 206 first authenticating user 106, para. 0053);
in response to the approval, authorizing the integration to be sent to the data broker layer for configuration (partner integration server 206 perform authentication of users 106 who operate media access client 202 by authenticating user 106 using internal user information, such as stored in admin repository 220, or by using the internal user information to authenticate user 106 at partner 210 on behalf of user 106 (also referred to as “proxy authentication” where partner integration server 206 is a proxy for user 106), partner integration server 206 enable authentication of users 106 directly with partner 210, without partner integration server 206 first authenticating user 106, para. 0053).
With respect to claim 17, DeGennaro teaches The computer program product of Claim 15, further comprising:
sending, to a partner server, a plurality of integrations from the extensibility layer, the plurality of integrations including the integration (the configuration data be stored in admin repository 220 and provided to media access client 202 from partner integration server 206;such a customization of media access client 202 desirable for branding media access client 202 according to a market identity of partner 210; because the configuration data stored with at least one of partner integration server 206 and admin repository 220, the customized display elements for partner 210 updated during operation of media access client 202, including without delay when a change is made with at least one of partner integration server 206 and admin repository 220, para. 0066; providing address to access to media objects stored in a media repository, para.0012);
receiving, from the partner server, an integration of the plurality of integrations selected in a web interface of the partner server and authentication information for the integration (the configuration data be stored in admin repository 220 and provided to media access client 202 from partner integration server 206;such a customization of media access client 202 desirable for branding media access client 202 according to a market identity of partner 210; because the configuration data stored with at least one of partner integration server 206 and admin repository 220, the customized display elements for partner 210 updated during operation of media access client 202, including without delay when a change is made with at least one of partner integration server 206 and admin repository 220, para. 0066; providing address to access to media objects stored in a media repository, para.0012);
saving the authentication information for the integration at the extensibility layer (the configuration data be stored in admin repository 220 and provided to media access client 202 from partner integration server 206;such a customization of media access client 202 desirable for branding media access client 202 according to a market identity of partner 210; because the configuration data stored with at least one of partner integration server 206 and admin repository 220, the customized display elements for partner 210 updated during operation of media access client 202, including without delay when a change is made with at least one of partner integration server 206 and admin repository 220, para. 0066; providing address to access to media objects stored in a media repository, para.0012);
sending, to the data streaming service, an event indicating the integration is enabled (the configuration data be stored in admin repository 220 and provided to media access client 202 from partner integration server 206;such a customization of media access client 202 desirable for branding media access client 202 according to a market identity of partner 210; because the configuration data stored with at least one of partner integration server 206 and admin repository 220, the customized display elements for partner 210 updated during operation of media access client 202, including without delay when a change is made with at least one of partner integration server 206 and admin repository 220, para. 0066; providing address to access to media objects stored in a media repository, para.0012);
creating a stream for each data field of the given integration (the configuration data be stored in admin repository 220 and provided to media access client 202 from partner integration server 206;such a customization of media access client 202 desirable for branding media access client 202 according to a market identity of partner 210; because the configuration data stored with at least one of partner integration server 206 and admin repository 220, the customized display elements for partner 210 updated during operation of media access client 202, including without delay when a change is made with at least one of partner integration server 206 and admin repository 220, para. 0066; providing address to access to media objects stored in a media repository, para.0012); and
sending, to the partner server, data retrieved from the stream for each data field at the web interface of the partner server (the configuration data be stored in admin repository 220 and provided to media access client 202 from partner integration server 206;such a customization of media access client 202 desirable for branding media access client 202 according to a market identity of partner 210; because the configuration data stored with at least one of partner integration server 206 and admin repository 220, the customized display elements for partner 210 updated during operation of media access client 202, including without delay when a change is made with at least one of partner integration server 206 and admin repository 220, para. 0066; providing address to access to media objects stored in a media repository, para.0012).
With respect to claim 18, DeGennaro teaches The computer program product of Claim 15, further comprising:
storing data received from the stream in a data store (the configuration data be stored in admin repository 220 and provided to media access client 202 from partner integration server 206;such a customization of media access client 202 desirable for branding media access client 202 according to a market identity of partner 210; because the configuration data stored with at least one of partner integration server 206 and admin repository 220, the customized display elements for partner 210 updated during operation of media access client 202, including without delay when a change is made with at least one of partner integration server 206 and admin repository 220, para. 0066; providing address to access to media objects stored in a media repository, para.0012).
With respect to claim 19, DeGennaro teaches The computer program product of Claim 18, further comprising:
receiving, from the vendor layer via the web based portal, a first workspace configured to access the plurality of data fields of the integration (partner integration server 206 perform authentication of users 106 who operate media access client 202 by authenticating user 106 using internal user information, such as stored in admin repository 220, or by using the internal user information to authenticate user 106 at partner 210 on behalf of user 106 (also referred to as “proxy authentication” where partner integration server 206 is a proxy for user 106), partner integration server 206 enable authentication of users 106 directly with partner 210, without partner integration server 206 first authenticating user 106, para. 0053);
receiving, from the vendor layer via the web based portal, a second workspace configured to access the plurality of data fields of the integration (partner integration server 206 perform authentication of users 106 who operate media access client 202 by authenticating user 106 using internal user information, such as stored in admin repository 220, or by using the internal user information to authenticate user 106 at partner 210 on behalf of user 106 (also referred to as “proxy authentication” where partner integration server 206 is a proxy for user 106), partner integration server 206 enable authentication of users 106 directly with partner 210, without partner integration server 206 first authenticating user 106, para. 0053);
wherein the first workplace and the second workspace are configured to access the plurality of data fields via the data store (the configuration data be stored in admin repository 220 and provided to media access client 202 from partner integration server 206;such a customization of media access client 202 desirable for branding media access client 202 according to a market identity of partner 210; because the configuration data stored with at least one of partner integration server 206 and admin repository 220, the customized display elements for partner 210 updated during operation of media access client 202, including without delay when a change is made with at least one of partner integration server 206 and admin repository 220, para. 0066; providing address to access to media objects stored in a media repository, para.0012).
With respect to claim 20, DeGennaro teaches The computer program product of Claim 18, further comprising:
receiving, from the vendor layer via the web based portal, a first gauge configured to access the plurality of data fields of the integration (partner integration server 206 perform authentication of users 106 who operate media access client 202 by authenticating user 106 using internal user information, such as stored in admin repository 220, or by using the internal user information to authenticate user 106 at partner 210 on behalf of user 106 (also referred to as “proxy authentication” where partner integration server 206 is a proxy for user 106), partner integration server 206 enable authentication of users 106 directly with partner 210, without partner integration server 206 first authenticating user 106, para. 0053);
receiving, from the vendor layer via the web based portal, a second gauge configured to access the plurality of data fields of the integration (partner integration server 206 perform authentication of users 106 who operate media access client 202 by authenticating user 106 using internal user information, such as stored in admin repository 220, or by using the internal user information to authenticate user 106 at partner 210 on behalf of user 106 (also referred to as “proxy authentication” where partner integration server 206 is a proxy for user 106), partner integration server 206 enable authentication of users 106 directly with partner 210, without partner integration server 206 first authenticating user 106, para. 0053);
wherein the first gauge and the second gauge are configured to access the plurality of data fields via the data store (the configuration data be stored in admin repository 220 and provided to media access client 202 from partner integration server 206;such a customization of media access client 202 desirable for branding media access client 202 according to a market identity of partner 210; because the configuration data stored with at least one of partner integration server 206 and admin repository 220, the customized display elements for partner 210 updated during operation of media access client 202, including without delay when a change is made with at least one of partner integration server 206 and admin repository 220, para. 0066; providing address to access to media objects stored in a media repository, para.0012).
Contact Information
Any inquiry concerning this communication or earlier communications from the examiner should be directed to HAO NGUYEN whose telephone number is (571)272-2666. The examiner can normally be reached on Monday through Friday from 7:30 A.M. to 4:00 P.M. (EST).
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Joon H. Hwang can be reached on 571-272-4036. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300.
Information regarding the status of an application may be obtained from the Patent Application Information Retrieval (PAIR) system. Status information for published applications may be obtained from either Private PAIR or Public PAIR. Status information for unpublished applications is available through Private PAIR only. For more information about the PAIR system, see http://pair-direct.uspto.gov. Should you have questions on access to the Private PAIR system, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative or access to the automated information system, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000.
/H.H.N/Examiner, Art Unit 2447
May 2, 2026
/JOON H HWANG/Supervisory Patent Examiner, Art Unit 2447
Prosecution Insights