SD-EC : Public <<block>> Block
Created: 08.02.2018 16:15:34
Modified: 08.02.2018 17:23:43
Project:
Advanced:
The SD-EC is a client of the Service Directory, who provides information of services to the SD. Typical SD-EC's are Service Provider Engines, GeoMessaging Servers, etc. <br/><br/>
Element Source Role Target Role
«block» Service Provider Service Directory Client
Block  
Name:  
 
Name:  
 
Details:
A SPE writes itself into the Service Directory, so it can be found by other entities. <br/><br/>SPE's might query the Service Directory to find other services, GeoMessaging-Server or similar entities.<br/><br/>
«block» Billing System
Block  
Name:  
 
Name:  
 
Details:
 
«block» Communication Provider BO
Block  
Name:  
 
Name:  
 
Details:
 
«block» Data Provider Service Directory Client
Block  
Name:  
 
Name:  
 
Details:
Specific instances of data provider inscribe themselves in the Service Directory, so they can be found by other entities.<br/><br/>Data provider may query the Service directory to receive information of other entities listed in the directory, e.g. to obtain data from other data providers.<br/><br/>
Element Message
«block» Service Directory update(String, ServiceEntry)
Details:
Type: Sequence Synchronous Call
If the service is discontinued, the SD-EC updates its entry a last time so it expires at the time the service is shut down.
«block» Service Directory create(ServiceEntry)
Details:
Type: Sequence Synchronous Call
The SD-EC create an initial entry once he comes to life.
«block» SD Entry Client createEnrtry
Details:
Type: Sequence Synchronous Call
The SD-EC creates an initial version of the ServiceEntry
«block» SD Entry Client updateEntry
Details:
Type: Sequence Synchronous Call
The SD-EC updates the information in its ServiceEntry before sending it to the ServiceDirectory.
«block» SD Entry Client sign
Details:
Type: Sequence Synchronous Call
Each ServiceEntry contains a signature, to proof that it has been created by the corresponding SD-EC.
«block» SD Entry Client sign
Details:
Type: Sequence Synchronous Call
Each ServiceEntry contains a signature, to proof that it has been created by the corresponding SD-EC.
«block» SD Entry Client updateEntry
Details:
Type: Sequence Synchronous Call
The SD-EC updates the information in its ServiceEntry before sending it to the ServiceDirectory.
«block» Service Directory update(String, ServiceEntry)
Details:
Type: Sequence Synchronous Call
When one of the informations present in the service entry change or the service entry is about to expire, the SD-EC will update his information in the SD.
«block» SD Entry Client sign
Details:
Type: Sequence Synchronous Call
Each ServiceEntry contains a signature, to proof that it has been created by the corresponding SD-EC.
Element Message
«block» SD Entry Client createEnrtry
Details:
Type: Sequence Synchronous Call
The SD-EC creates an initial version of the ServiceEntry
«block» SD Entry Client updateEntry
Details:
Type: Sequence Synchronous Call
The SD-EC updates the information in its ServiceEntry before sending it to the ServiceDirectory.
«block» Service Directory  
Details:
Type: Sequence Synchronous Call
 
«block» SD Entry Client sign
Details:
Type: Sequence Synchronous Call
Each ServiceEntry contains a signature, to proof that it has been created by the corresponding SD-EC.
«block» Service Directory  
Details:
Type: Sequence Synchronous Call
 
«block» SD Entry Client sign
Details:
Type: Sequence Synchronous Call
Each ServiceEntry contains a signature, to proof that it has been created by the corresponding SD-EC.
«block» Service Directory  
Details:
Type: Sequence Synchronous Call
 
«block» SD Entry Client updateEntry
Details:
Type: Sequence Synchronous Call
The SD-EC updates the information in its ServiceEntry before sending it to the ServiceDirectory.
«block» SD Entry Client sign
Details:
Type: Sequence Synchronous Call
Each ServiceEntry contains a signature, to proof that it has been created by the corresponding SD-EC.
Property Value
_defaultDiagramType: SysML1.4::InternalBlock
Object Type Connection Direction Notes
«block» SD Lookup Client Block Generalization To Each SD-EC is also an SD-LC. All SD-EC can also use the lookup interfaces, e.g. to verify that their entries have been updated correctly. Thus, each SD-EC is also an SD-LC in principle. However, not all implementations of SD-EC might provide the read functionality to their using entities.
«block» Geomessaging Server Service Directory Client Block Generalization From  
«block» Billing System Block Weak To  
«block» Communication Provider BO Block Weak To