WO2020140105A1 - System and method of digital product onboarding and distribution using the cloud service brokerage infrastructure - Google Patents
System and method of digital product onboarding and distribution using the cloud service brokerage infrastructure Download PDFInfo
- Publication number
- WO2020140105A1 WO2020140105A1 PCT/US2019/068844 US2019068844W WO2020140105A1 WO 2020140105 A1 WO2020140105 A1 WO 2020140105A1 US 2019068844 W US2019068844 W US 2019068844W WO 2020140105 A1 WO2020140105 A1 WO 2020140105A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- product
- request
- present disclosure
- product model
- csb
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/06—Buying, selling or leasing transactions
- G06Q30/0601—Electronic shopping [e-shopping]
- G06Q30/0603—Catalogue ordering
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/547—Remote procedure calls [RPC]; Web services
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/06—Buying, selling or leasing transactions
- G06Q30/0601—Electronic shopping [e-shopping]
- G06Q30/0633—Lists, e.g. purchase orders, compilation or processing
- G06Q30/0635—Processing of requisition or of purchase orders
Definitions
- the present disclosure relates to a system and method of software delivery in a cloud service broker (CSB) platform, and specifically, for a system and method for Of Digital Product Onboarding And Distribution Using The Cloud Service Brokerage Infrastructure.
- CSB cloud service broker
- CSB cloud service broker
- the CSB would be configured to provide a unique user interface (UI) that integrated offers from different IS Vs, an operating system for performing different control actions on the services (provisioning, deleting, changing etc.), a billing system for performing calculations of consumption/licensing fees, and generating invoices for their sub-resellers and customers.
- UI user interface
- CSB platform may also be integrated with a plurality of different service vendors (e.g. Microsoft®, Dropbox®, Kaspersky Lab®) interfaces or special connectors.
- resellers may already offer other services unrelated to cloud services.
- a reseller in the hardware distribution business may have already implanted a solution for billing their sub-resellers and customers, they have tuned working CRM and many other custom system or IT business systems from any popular vendors of such systems (Oracle, QuickBooks, SalesForce, SAP etc.).
- launching a new platform with built-in IT solutions that enable selling products (it may be cloud services but also anything that is being handled by ISV) become too costly and ineffective.
- FIG. 1 a schematic drawing of a system for digital product onboarding and distribution using the cloud service brokerage infrastructure.
- the system includes and ISV device, an ordering system, a vendor portal computing device, a marketplace computing device, and third-party computing device.
- a developer for an ISV that wants to integrate its service with the CSB platform may use a vendor UI portal in the vendor portal computing device.
- the developer of the ISV may use the vendor portal computing device to fill in the general attributes of a product for sale, where such attributes may include, for example, product name, logo, product ID that will be further used in API calls, name of the account that owns this product from the ISV side, product fulfillment mode that define whether how provisioning/change/deletion will happen, short product overview for CSBs and the detailed overview of the product for CSBs.
- the vendor portal computing device and the product catalog are configured to generate the product model for a particular product.
- the product definition may operate by way of API calls.
- API calls are relative to requests for a purchase order; and the purchase order is relative to a single asset with multiple product items from the ISV.
- the system is configured to allow an asset defined as a recurring or one-time service or a product and a workflow of requesting these assets.
- all such requests get into a queue and then are processed either by an operator using the fulfillment UI or automatically via the integration through the fulfillment API.
- FIG. 1 displays a schematic drawing of a system for digital product onboarding and distribution using the cloud service brokerage infrastructure, according to at least one embodiment of the present disclosure.
- FIG. 2 displays an exemplary catalog of a system and method for digital product onboarding and distribution using the cloud service brokerage infrastructure, according to at least one embodiment of the present disclosure.
- FIG. 3 displays a workflow of a method for digital product onboarding and distribution using the cloud service brokerage infrastructure, according to at least one embodiment of the present disclosure.
- FIG. 4 displays a workflow a method for digital product onboarding and distribution using the cloud service brokerage infrastructure, according to at least one embodiment of the present disclosure.
- FIG. 1 there is shown a schematic drawing of a system for digital product onboarding and distribution using the cloud service brokerage infrastructure, generally indicated at 100.
- the system 100 includes and ISV device 102, an ordering system 104, a vendor portal computing device 106, a marketplace computing device 110, and third-party computing device 130.
- a developer for an ISV that wants to integrate its service with the CSB platform may use a vendor UI portal in the vendor portal computing device 106. It will be appreciated that in order for the ISV to integrate with the CSB platform, the ISV may need to create a product model via the vendor portal computing device 106, as further disclosed herein. It will be further appreciated that the approach of creating product models is product-agnostic as there is no application packaging standard (APS) specific requirement in the format of the product model.
- APS application packaging standard
- the developer of the ISV may use the vendor portal computing device 106 to fill in the general attributes of a product for sale, where such attributes may include, for example, product name, logo, product ID that will be further used in API calls, name of the account that owns this product from the ISV side, product fulfillment mode that define whether how provisioning/change/deletion will happen, short product overview for CSBs and the detailed overview of the product for CSBs.
- attributes may include, for example, product name, logo, product ID that will be further used in API calls, name of the account that owns this product from the ISV side, product fulfillment mode that define whether how provisioning/change/deletion will happen, short product overview for CSBs and the detailed overview of the product for CSBs.
- the developer of the ISV may also set a product definition and related business model in the product catalog 114.
- the product catalog 114 may include a user interface. It will be appreciated that the product catalog 114 is configured to accommodate a plurality of possible product definitions and business models so that various products can be orchestrated within the product catalog 114, thereby making the marketplace computing device 110, product agnostic.
- an ISV may have a very complex structure for its product models.
- ISVs may have very complex rules for how a product may be sold. For example, products may have dependencies- a first product item can only be if a second product item was previously used by the user; or a first reseller can only sell one group of product items but cannot sell another group of product items.
- a first quantity of a first product item may depend on a first quantity number of second product item via a specific functional dependency.
- IS Vs keep this business logic internally in unstructured data stores.
- ISVs may encounter challenges to integrate and automate their product model(s) and business rule(s), especially if the ISV needs to make it fast and efficient.
- the ISV defines the product model which will be stored and processed in the product catalog 114.
- a product is configured as something that can be sold (standalone, or otherwise).
- a product is the minimum sellable (and conversely, purchasable) commodity/item.
- a product item is part of a product which is reflected and accounted as its own line item in financial documents.
- at least one product item must be purchased when the product is purchased, whereas all others may be optional. It will be appreciated that product items may have a price.
- a product offer is a particular business offer related to the product.
- a customer or reseller
- purchases a product - a particular offer may be selected with fixed product pricing, currency, discounts, and other details, to name a few, non limiting examples.
- product attributes are also defined, including, but not limited to: product item IDs, a measure of units of the product items; internal ID from the vendor system; and the like. It will be further appreciated that every product item is assigned to a stock keeping unit (SKU), which is an identifier of the product item in the CSB platform.
- SKU stock keeping unit
- a product item may have a hierarchical complex structure.
- the structure might be defined by at least one of a plurality of rules as further disclosed herein.
- each product item is unique at each level.
- such a product may only be ordered at the assigned level of the hierarchy.
- a buyer may buy as many telephone numbers as desired and also can buy a data/minutes package that will be shared by all associated telephone numbers.
- it may be that a telephone number is first purchased and then a data/minutes package is subsequently purchased.
- the structure may be such that it can only be ordered once (with quantity assigned); or, following the initial order, only quantity changes could be requested.
- each product item may also define if there are any child product items and whether they are unique or are configured as a collection.
- a child product items defines incompatibility rules with other product items at the same level; a child product item defines compatibility rules with the parent product item(s); and each product item at any level may define compatibility to transition to another product item at the same level.
- each of the contract dates can be set on a certain level of the hierarchy and are inherited by items in lower levels.
- the contract date is set at level 0 all underlying levels will follow; similarly, if the contract date is set at level 1, different dates for product items at level 1 may differ, but lower levels follow parents.
- product items of each level might have additional attributes assigned to them (which are also visible by their children), whereby these attributes can be defined by the product owner, and then passed to provisioning level.
- FIG. 2 there is shown an exemplary embodiment of a product model construction tool interface, generally indicated at 200.
- the interface 200 includes eight (8) product items at level-1 (i.e. 202, 204, 206, 212, 218, 220 - 224); and where two level-1 product items (i.e. 206 and 212) have their own child product items: 206 has child product items 208 and 210; and 212 has child product items 214 and 216.
- the ISV is able to build any product structure in accordance with the ISV’s business model.
- the product model construction tool may be provided via an API.
- the product model construction tool generates a computer readable file, for example, in JavaScript Object Notation (JSON), based on this representation of the product model.
- JSON JavaScript Object Notation
- the computer readable file i.e. in JSON format
- the vendor portal computing device 106 and the product catalog 114 are configured to generate the product model (as exemplarily shown via interface 200) for a particular product. It will be appreciated that the product model may also be transmitted to a third-party CSB 130 e-commerce platform which third -party CSB e-commerce platform may use the data from the product model for displaying the offer of this product in the e-commerce system. It will be further appreciated that the ordering system 100 also stores the product model, whereby the product catalog 114 operably communicates with a fulfillment manager 122 and allowing the system 100 to process the requests from any third-party CSB 130 that refers to this particular product according to the product definition set by the ISV.
- the product definition may operate by way of API calls.
- a third-party CSB 130 may want to create a contract with CSB marketplace 112.
- the CSB marketplace 112 is configured to add the new connection in a connection database 116A, and create a set of credentials for accessing the ordering system for the third- party CSB 130.
- the system 100 is configured to receive posting API calls from the third-party CSB 130.
- the third-party CSB 130 may optionally display the data from the product model for displaying the product offer.
- the third-party CSB 130 may incorporate the product model for further integrating it with internal e-commerce system(s) for automatic tracking of actions with the product in internal systems (e.g. QuickBooks, SalesForce, Oracle and so on).
- the integration layer is optional and is aimed to translate third-party CSB 130 APIs into the standard posting API of the ordering system 100.
- FIG. 3 there is shown a standard fulfillment API workflow, generally indicated at 300.
- API calls are relative to requests for a purchase order; and the purchase order is relative to a single asset with multiple product items from the ISV.
- the system 100 is configured to allow an asset defined as a recurring or one-time service or a product and a workflow of requesting these assets.
- all such requests get into a queue and then are processed either by an operator using the fulfillment UI 126 or automatically via the integration through the fulfillment API 124.
- an asset is characterized by the following: (i) Every asset reflects some purchase (somebody purchases either a service or a good); (ii) Purchase requests can be reverted (canceled) or terminated when terms of purchase are expired; (iii) An asset can be subscription-based (when customer pays for usage in some time terms) or one-time based; (iv) Matter of asset is defined as a list of purchased SKUs with purchased quantities (asset items); (v) Item in the asset may be either reservation-based when a customer decides how much items of SKU to be purchased or‘pay-per-user’ basis when actual use of the SKU defines the quantity for asset item; (vi) the asset may be modified using change requests: either set of items may be changed or quantities of reservation-based items may be changed; (vii) Some assets can be put into suspend state when service is not actually provided and no charges happened; and (viii) Assets also may be parametrized by one or more parameters which differentiate one asset from another.
- the fulfillment manager 122 keeps track of assets, check the validity of requests, by the information from the request check it against the product model set in the product catalog 114.
- each ISV independently of the third-party CSB 130 platform logic, is able to interact with the ordering system using a product agnostic API (i.e. fulfillment API 124).
- This fulfillment API 124 delivers basic endpoint to operate with the different requests generated by the third-party CSB 130 platform in a consistent manner independently of operation (e.g. purchase, change, delete) or product owned by ISV.
- the available operations for the API are: (i) Get Requests List - GET /requests; (ii) Get Request Details - GET /requests/ ⁇ id ⁇ ; (iii) Modify Request Data - PUT /requests/ ⁇ id ⁇ and PATCH /requests/ ⁇ id ⁇ ; and (iv) Change Request Status - POST /requests/ ⁇ id ⁇ / ⁇ status ⁇ .
- GET request methods provide the collection of requests objects available to the vendor
- additional filtering is possible to limit the request returned by fulfillment system.
- Available filters include: (i) request status is pending, inquiring, approved or failed; (ii) created after a certain date; (iii) for a concrete asset, obtaining with that all orders relative to a concrete asset; and (iv) For a concrete product, in case that ISV provides multiple products at the same time.
- each of the returned objects represents a unique request, each of them provides: (i) Unique identifier of the request (ID); (ii) Type of the request, possible values are: (a) purchase: initial request for a new asset; (b) change: a modification on existing asset relative to the items purchased, one asset may have multiple change requests on its life cycle; (c) cancel: relative to the request to terminate a concrete asset suspension: to put temporally on the suspended asset on ISV platform; (d) resume: request to return to normal state a previously suspended asset; (iii) status: any of the possible status based on the workflow/lifecycle of a request; (iv) asset structure contains information about: (a) unique identifier of the asset from the ordering system; (b) unique product information to identify for what concrete product request is; (c) connection information to identify the exact contract between ISV and CSB marketplace 112 to which the asset is bound to; (d) concrete information relative to the different companies involved in the request, being
- connection DB "CT-9861-7949-8492”, //Unique identifier of the connection of a given third-party CSB 130, stored in the connection DB
- tiers ⁇ //Full information of the different actors involved in the purchase, that will be end customer (buyer), there can be as many tiers as the number of resellers in the chain under the third-party CSB 130 "customer”: ⁇ "id”: "CS-9861-7949-8492",
- the ISV is able to modify the parameters of the request only and move the request over the workflow.
- data on the body may contain a new value or a reason why the value provided by the customer is wrong via the modification of the value error.
- updating parameters allows the ISV to: (i) Interact with the buyer in order to request additional data or correct provided one; and (ii) Store information on the ordering system for future use on new requests for the same asset.
- the posting API allows the creation of a request object, whereby one matches the fulfillment API with the add-on that allows external commerce to also pass extemal attributes that will not be disclosed to vendor; and where such attributes are solely used by commerce system (e.g. CSB platform) to use the reporting or even on the retrieval of a request to match / reconcile the requests it created with its own internals. This extends request object as mentioned with an array like this:
- the assets, defined by one or multiple requests have a complete lifecycle controlled by the third-party CSB 130 platform that generates multiple requests over time.
- the complete asset life cycle may be covered by the workflow shown in FIG. 4.
- an asset represents an instance of a product acquired by a customer with a limited amount of items.
- FIG. 4 there is shown a lifecycle modified by the multiple requests that points to it, according to at least one embodiment of the present disclosure.
- Each type of request will modify the status of the asset accordingly.
- an asset in“NEW” status means a purchase request has been issued but not all parameters had been filled yet by responsible party, and the ISV is still not aware of the asset.
- an asset in“PROCESSING” status means the ISV is still performing processing the purchase request or a change request, and the asset is not delivered to buyer yet but he is informed that work is in progress;
- an asset in status “REJECTED” means the ISV failed the purchase request (for various possible reasons) and the object receives a final non-recoverable status;
- an asset in“ACTIVE” status means the ISV completed the change / purchase / resume request and asset is operative and usable by buyer;
- an asset is“SUSPENDED” status occurs when an administrative hold notification is sent over a suspend request;
- an asset in“TERMINATED” status means a final not recoverable status result of completing a cancelation request, and the asset object is not destroyed and remains on the system for tracking / reporting purposes.
Landscapes
- Business, Economics & Management (AREA)
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Finance (AREA)
- Accounting & Taxation (AREA)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- Software Systems (AREA)
- Development Economics (AREA)
- Economics (AREA)
- Marketing (AREA)
- Strategic Management (AREA)
- General Business, Economics & Management (AREA)
- General Engineering & Computer Science (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Stored Programmes (AREA)
Abstract
Description
Claims
Priority Applications (6)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2021532239A JP7314273B2 (en) | 2018-12-28 | 2019-12-28 | Systems and methods for onboarding and distributing digital products using cloud service broker infrastructure |
MX2021007727A MX2021007727A (en) | 2018-12-28 | 2019-12-28 | System and method of digital product onboarding and distribution using the cloud service brokerage infrastructure. |
CA3123883A CA3123883A1 (en) | 2018-12-28 | 2019-12-28 | Method of digital product onboarding and distribution using t he cloud service brokerage infrastructure |
EP19905892.6A EP3903272A4 (en) | 2018-12-28 | 2019-12-28 | System and method of digital product onboarding and distribution using the cloud service brokerage infrastructure |
AU2019413433A AU2019413433A1 (en) | 2018-12-28 | 2019-12-28 | System and method of digital product onboarding and distribution using the cloud service brokerage infrastructure |
CN201980086387.8A CN113228080B (en) | 2018-12-28 | 2019-12-28 | System and method for digital product loading and distribution using cloud service proxy infrastructure |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US16/235,855 | 2018-12-28 | ||
US16/235,855 US11538091B2 (en) | 2018-12-28 | 2018-12-28 | Method of digital product onboarding and distribution using the cloud service brokerage infrastructure |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2020140105A1 true WO2020140105A1 (en) | 2020-07-02 |
Family
ID=71122992
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2019/068844 WO2020140105A1 (en) | 2018-12-28 | 2019-12-28 | System and method of digital product onboarding and distribution using the cloud service brokerage infrastructure |
Country Status (8)
Country | Link |
---|---|
US (1) | US11538091B2 (en) |
EP (1) | EP3903272A4 (en) |
JP (1) | JP7314273B2 (en) |
CN (1) | CN113228080B (en) |
AU (1) | AU2019413433A1 (en) |
CA (1) | CA3123883A1 (en) |
MX (1) | MX2021007727A (en) |
WO (1) | WO2020140105A1 (en) |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2023240163A1 (en) * | 2022-06-07 | 2023-12-14 | Madipadaga Venkat | Multi-vendor api marketplace with targeted content and customized rate plan monetization capabilities |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20110314082A1 (en) * | 2010-06-16 | 2011-12-22 | Computer Associates Think, Inc. | System and method for selecting cloud services |
US20150161681A1 (en) * | 2013-12-09 | 2015-06-11 | Hewlett-Packard Development Company, L.P. | Fulfilling a request based on catalog aggregation and orchestrated execution of an end-to-end process |
US20160065417A1 (en) * | 2013-03-15 | 2016-03-03 | Gravitant, Inc | Fulfillment of cloud service orders |
US20160125489A1 (en) * | 2014-11-03 | 2016-05-05 | Hewlett Packard Enterprise Development Lp | Fulfillment of cloud service using marketplace system |
US20180316772A1 (en) * | 2017-04-28 | 2018-11-01 | Sap Se | Brokering services from partner cloud platforms |
Family Cites Families (17)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CA2373511C (en) * | 1999-05-19 | 2014-07-08 | Digimarc Corporation | Methods and systems for controlling computers or linking to internet resources from physical and electronic objects |
US20050027610A1 (en) * | 1999-08-26 | 2005-02-03 | Wharton Brian K. | Electronic commerce systems and methods providing unified checkout steps |
US7475123B2 (en) * | 2002-11-18 | 2009-01-06 | Sap Ag | Web service integration |
GB0518416D0 (en) * | 2005-09-09 | 2005-10-19 | Standard Life Assurance Compan | Improvements in and relating to service orientated architecture |
US7996488B1 (en) * | 2006-11-27 | 2011-08-09 | Disney Enterprises, Inc. | Systems and methods for interconnecting media applications and services with automated workflow orchestration |
US9069599B2 (en) * | 2008-06-19 | 2015-06-30 | Servicemesh, Inc. | System and method for a cloud computing abstraction layer with security zone facilities |
CN101296243B (en) * | 2008-06-26 | 2013-02-20 | 阿里巴巴集团控股有限公司 | Service integration platform system and method for providing internet service |
US8924559B2 (en) | 2009-12-03 | 2014-12-30 | International Business Machines Corporation | Provisioning services using a cloud services catalog |
US8700777B2 (en) * | 2010-05-28 | 2014-04-15 | International Business Machines Corporation | Extensible support system for service offerings |
US9489243B2 (en) * | 2012-01-26 | 2016-11-08 | Computenext Inc. | Federating computing resources across the web |
US8997038B2 (en) * | 2012-03-30 | 2015-03-31 | Anypresence, Inc. | Systems and methods for building and deploying mobile applications |
US11714685B2 (en) * | 2015-07-31 | 2023-08-01 | The Conundrum Ip Llc | Discovering and publishing API information |
US11361355B2 (en) * | 2015-09-08 | 2022-06-14 | Kyndryl, Inc. | Marketplace suggestions for cloud service providers |
US10395293B1 (en) * | 2016-08-25 | 2019-08-27 | PredictSpring, Inc. | Canonical order management system |
US10528995B2 (en) * | 2016-11-04 | 2020-01-07 | Micro Focus Llc | Use of marketplace platform instances for reselling |
CN108121533A (en) * | 2016-11-28 | 2018-06-05 | 宁波有哒云商务服务有限公司 | A kind of online electronic commerce integrated service system based on cloud computing |
GB2564165B (en) * | 2017-02-02 | 2021-11-24 | Google Llc | Custom digital components |
-
2018
- 2018-12-28 US US16/235,855 patent/US11538091B2/en active Active
-
2019
- 2019-12-28 WO PCT/US2019/068844 patent/WO2020140105A1/en unknown
- 2019-12-28 MX MX2021007727A patent/MX2021007727A/en unknown
- 2019-12-28 CN CN201980086387.8A patent/CN113228080B/en active Active
- 2019-12-28 CA CA3123883A patent/CA3123883A1/en active Pending
- 2019-12-28 JP JP2021532239A patent/JP7314273B2/en active Active
- 2019-12-28 EP EP19905892.6A patent/EP3903272A4/en active Pending
- 2019-12-28 AU AU2019413433A patent/AU2019413433A1/en active Pending
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20110314082A1 (en) * | 2010-06-16 | 2011-12-22 | Computer Associates Think, Inc. | System and method for selecting cloud services |
US20160065417A1 (en) * | 2013-03-15 | 2016-03-03 | Gravitant, Inc | Fulfillment of cloud service orders |
US20150161681A1 (en) * | 2013-12-09 | 2015-06-11 | Hewlett-Packard Development Company, L.P. | Fulfilling a request based on catalog aggregation and orchestrated execution of an end-to-end process |
US20160125489A1 (en) * | 2014-11-03 | 2016-05-05 | Hewlett Packard Enterprise Development Lp | Fulfillment of cloud service using marketplace system |
US20180316772A1 (en) * | 2017-04-28 | 2018-11-01 | Sap Se | Brokering services from partner cloud platforms |
Non-Patent Citations (1)
Title |
---|
See also references of EP3903272A4 * |
Also Published As
Publication number | Publication date |
---|---|
EP3903272A4 (en) | 2022-09-28 |
US20200211089A1 (en) | 2020-07-02 |
JP2022517509A (en) | 2022-03-09 |
MX2021007727A (en) | 2021-08-05 |
EP3903272A1 (en) | 2021-11-03 |
CN113228080B (en) | 2024-03-12 |
CN113228080A (en) | 2021-08-06 |
CA3123883A1 (en) | 2020-07-02 |
JP7314273B2 (en) | 2023-07-25 |
US11538091B2 (en) | 2022-12-27 |
AU2019413433A1 (en) | 2021-06-24 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
Smith et al. | Analysis & Design | |
KR100340774B1 (en) | Object oriented technology flamework for order processing | |
US8326702B2 (en) | Providing supplier relationship management software application as enterprise services | |
US8401928B2 (en) | Providing supplier relationship management software application as enterprise services | |
CA2744629C (en) | Systems and methods for providing a multi-channel retail layaway service | |
US8396749B2 (en) | Providing customer relationship management application as enterprise services | |
US20100070336A1 (en) | Providing Customer Relationship Management Application as Enterprise Services | |
US20150039457A1 (en) | System for syndicating subscriptions with retailers | |
US11657444B2 (en) | Methods and systems for generating a customized return policy | |
CN102262761A (en) | Service delivery management for brokered service delivery | |
CN102262767A (en) | Service delivery management for brokered service delivery of service groups | |
US11544642B2 (en) | Supplier recommendation engine | |
US20150154687A1 (en) | Reseller sales force | |
US20230344912A1 (en) | Methods and systems for automatic installation of software applications for online stores | |
US11538091B2 (en) | Method of digital product onboarding and distribution using the cloud service brokerage infrastructure | |
US10719590B1 (en) | Computer software product grant management system | |
US20210272172A1 (en) | Systems and methods to regulate sales of a product in an online store | |
US20030163385A1 (en) | Commodity order acceptance and transportation system, method, and recording medium | |
US20120179583A1 (en) | Electronic Commerce Platform with Staging to Production and Bundles | |
US20230359984A1 (en) | Methods and systems for inventory management for blockchain-based transactions | |
US11816713B2 (en) | Systems and methods for automating tasks across multiple online stores | |
US11170120B1 (en) | Runtime computer software product management system | |
US20140006303A1 (en) | Consistent Interface for Customer Contract and Customer Contract Template - Message Set 1 | |
US12008628B2 (en) | Systems and methods for obscuring content in electronic messages | |
US20240062142A1 (en) | Systems and methods for computer memory optimization for the storage of delivery time information for a product sold online |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 19905892 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2021532239 Country of ref document: JP Kind code of ref document: A |
|
ENP | Entry into the national phase |
Ref document number: 3123883 Country of ref document: CA |
|
ENP | Entry into the national phase |
Ref document number: 2019413433 Country of ref document: AU Date of ref document: 20191228 Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 2019905892 Country of ref document: EP Effective date: 20210728 |