Main Use Case Sample Clauses

Main Use Case. 5.3.1 Current State-of-the-Art 1. The Key Generator creates and provisions a private/public key pair. 2. The DER Client stores the key pair and provides controlled access to the private key. 3. The Manufacturer manufactures the DER Client. 4. The certificate authority issues a certificate based on the information provided in the certificate request. 5. The DER Server receives the issued certificate as part of the TLS handshake and establishes a connection to the DER Client if it validates the TLS session setup.

Main Use Case. The main use case consists of the following actors and their interaction: 1. An Authorized Assessor conducts a security audit of (a) the key generation process, (b) the private key’s storage and control access mechanisms within the DER Client and (c) the exposure of the private key through the DER Client’s manufacturing supply chain. Audit results are stored on the Blockchain. 2. The Key Generator creates and provisions a private/public key pair into the DER Client. The Key Generator processes were previously audited. 3. The DER Client stores the key pair and provides controlled access to the private key. Storage and access mechanisms were previously audited. 4. The Manufacturer manufactures the DER Client. The manufacturing process was previously audited. 5. The Manufacturer will register the key of a manufactured DER Client on the Blockchain. The registration will link the generated key pair to (a) the audited process used to create and provision the keys in step 2,

Main Use Case. 1. A user can send a message that may be beforehand encrypted, and may contain some attachments. 2. Each message sent is in a first step set in a temporary spool in order to be stored directly in the receiver eHealthbox. At the moment, the mail is in the receiver eHealthbox, the sender may receive a notification2. 3. If the inbox of the receiver is less than its authorised capacity, the receiver can from that moment see the mail otherwise, he has to clean his inbox. 4. From that moment, the receiver can consult the list of messages (with a limit of 100 messages per call). In addition, once a day, the receiver may obtain a notification if he had subscribed to the eHealth update info service. 5. The receiver can select and consult a specific message. The sender can obtain a notification related to this act. 6. The receiver can then download the attachment.

Main Use Case a. A user can send a message that may be encrypted beforehand and may contain some attachments. b. Each message sent, is first set in a temporary spool in order to be stored directly in the receiver’s eHBox. As soon as the mail is in the receiver’s eHBox, the sender may receive a notification3. c. If content of the receiver’s inbox is less than its authorised capacity, the receiver can see the mail, and otherwise he has to clean his inbox.