AODP Automatic Ordering & Delivery Protocol
Technical Information
How the protocol works
AODP works according to the client/server principle with XML-formatted messages, that are exchanged via HTTP. (For details see Resources.)
When a retailer wants to sell a specific digital item to an end customer, its client software contacts the provider's server via the Internet and requests the desired article via AODP. If the retailer is activated by the provider, the server provides the article for download under an individual, not guessworkable link for this purchase process and returns this link to the retailer's AODP software. This completes the transaction. What happens next depends on the application. The retailer can forward the link to the end customer so that he can download the article directly from the provider's server. The retailer can also offer additional services, for instance in the case of sheet music the creation of a bound printout.
AODP is universally applicable, both in the shop, where the process is carried out by the dealer for the end customer, as well as, for example, in a web shop, where the customer places download items from the retailer's range in his shopping cart and after payment receives the download link on the completion page or in the confirmation e-mail. In the latter case, the process is fully automatic.
Of course, many other applications are also conceivable. AODP provides a universal technical "back end" for this purpose.
Securing data traffic
Two requirements belong to security: Mutual authentication of transaction partners and encryption of data traffic.
Authentication means that not everyone can easily access an AODP server over the Internet. Instead, an AODP client must "identify itself" to the server and vice versa the server to the client. This is done with the help of X.509 certificates, a technical standard, which is also used for secure websites.
Encryption is done by TLS (Transport Layer Security), which is also a common technical standard.