Created: | 12.01.2018 11:20:07 |
Modified: | 08.02.2018 10:14:44 |
![]() |
|
![]() |
Element | Source Role | Target Role |
«block» Service Provider Exchange System Block |
Name: |
Name: |
![]() |
Element | Message |
«block» SD Lookup Client | |
![]()
Type: Sequence Synchronous Call
|
|
«block» SD Entry Client | |
![]()
Type: Sequence Synchronous Call
|
|
«block» SD Entry Client | |
![]()
Type: Sequence Synchronous Call
|
|
«block» SD Entry Client | |
![]()
Type: Sequence Synchronous Call
|
|
«block» SD Lookup Client | |
![]()
Type: Sequence Synchronous Call
|
Element | Message |
«block» SD Entry Client | update(String, ServiceEntry) |
![]()
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» SD Entry Client | create(ServiceEntry) |
![]()
Type: Sequence Synchronous Call
The SD-EC create an initial entry once he comes to life. |
|
«block» SD Lookup Client | queryServices(String) |
![]()
Type: Sequence Synchronous Call
The SD-LC might query the SD for services with a specific property. E.g. to get services which are available for the current region in which the vehicle is present. |
|
«block» SD Entry Client | update(String, ServiceEntry) |
![]()
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 Lookup Client | getService(String) |
![]()
Type: Sequence Synchronous Call
The SD-LC might also request the entry for a specific service, e.g. based on serviceID. This is mostly used by services, to check if their own entry is up-to-date. |
Property | Value |
_defaultDiagramType: | SysML1.4::InternalBlock |
Object | Type | Connection | Direction | Notes |
«block» Personal Information Devices | Block | Information Flow | To | The Personal Information Device (PID) queries the Service Directory on demand to obtain information of services, geo-messaging entities, data provider, etc. PID's themselves are not managed in the SD. |