1 / 8

A ‘Connect’ Protocol for B2B

The 'Connect' Protocol simplifies B2B interactions by mirroring social network dynamics, making connections as easy as “friending” someone. Unlike traditional B2B exchanges that require complex partner setups, this protocol uses an open, SMTP-like model for easy adoption, especially by SMBs. It features semi-automated email invitations and fully automated system communication, allowing businesses to connect, authorize, and exchange essential documents such as POs and invoices with ease and low overhead. It aims to establish trust and streamline collaboration across different governance domains.

neola
Télécharger la présentation

A ‘Connect’ Protocol for B2B

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. A ‘Connect’ Protocol for B2B Making B2B Connections as easy as ‘friending’ someone… or easier

  2. Problem • B2B exchanges are typically privileged, requiring an initial partner validation/setup • Analog to social networks: “friending” / “connecting” • PEPPOL has adopted an open, SMTP-like model… but this is the exception, not the rule • Maximizing adoption (especially by SMBs) requires a B2B setup with social-network-like ease and low cost • B2B requirements are, however, more complex, e.g. • Four-corner model (different agents for each party)

  3. Problem, contd. • Two models, variants of the same problem • Three-corner: identity federation/setup across networks • Four-corner: getting beyond “trusted peering” • “Chain of Trust” issues with multiple governance domains

  4. Use Cases • Semi-automated: email invitation • Similar to the “social network” invitation scenario • Recipient of invitation clicks to accept/authorize connection • May need to first create/provision an account to do so • BUT, process includes authorization of BOTH parties’ systems to connect on their respective users’ behalf • Fully-automated: system to system dialog • Two systems each pre-authorized to manage collaboration • Fully automated relationship discovery and setup

  5. Semi-AutomatedBuyer-Driven Process (Email PO or Invitation) Supplier Gateway SMB Acct’g ERP A/P Buyer Network/ Gateway Cloud Platform 4 Invoice ERP POs Data/ Process Data/ Process Identities / Trust 1 Identities / Trust POs pre-populate Supplier Identities Get all emailed invoices Link triggers Auth handshake 3 Send email invitations with ‘SMB Accounting’ links 2 Get Connected • Buyer issues POs via Buyer Network, triggering pre-configured, pre-authorized supplier account creation. • On Buyer’s behalf, Buyer Network sends invitation emails for suppliers to get connected (i.e. to complete activation of a pre-configured account) for exchange of POs, invoices and other business documents. • For an supported Buyer, these emails include a "Connect to SMB Accounting" link, enabling a Supplier to: • Authorize Buyer (B2B Network) to activate their account, with Supplier Gateway access permissions • Enroll with Supplier Gateway (i.e. authorize Supplier’s SMB Accounting (Cloud) to connect) • Authorize the Supplier’s Gateway to connect with the Buyer’s Gateway (invoicing, payment) • Supplier Gateway retrieves all emailed invoices from the Supplier's connected SMB Accounting Cloud account, and matches recipient email addresses against enrolled Buyer domains/email addresses. If matched, it: • Retrieves Supplier Identity Attributes, and syncs as needed to the Buyer Gateway; • Transforms the retrieved invoice content in accordance with Buyer Profile Specification; • Posts invoice to Buyer Network

  6. Fully Automated Big / Buyer / Receiver Small / Seller / Sender Available Identities Available Identities 1 6 Enrolled Identities Enrolled Identities 2 Populated by “listening” to sent document flow: POs 3 7 Invoices Matched? 4 Send Request 5 Target Partner Identities Target Partner Identities Matched? 8 Accept Request 9 • Notes: • This shows the Buyer-initiated process. Seller-initiated process can also occur, if Buyer supports • Skip step 5 if small/seller party is already enrolled

  7. Related Issues • Discovery (SML) • Email/domain based? • Chain of trust issues • Service Profile (CPPA / SMP) • Trust Frameworks (Inter-Cloud)

  8. References • OASIS Id-Cloud Use Cases v1.0 Committee Note 01 Use Case 25:  Inter-cloud Document Exchange & Collaboration http://docs.oasis-open.org/id-cloud/IDCloud-usecases/v1.0/cn01/IDCloud-usecases-v1.0-cn01.html#_Toc324801970

More Related