SPE : Public <<block>> Block
Created: 19.12.2017 15:18:40
Modified: 23.02.2018 16:36:40
Project:
Advanced:
A generic back-office system of a<br/>service provider used for the specific services of the SP to connected<br/>drivers or end-users to inform end users or other SP BO systems from<br/>providers. A SP BO can be used to support personal information services<br/>for, e.g. navigation or traffic information applications on OBU/PID. A SP BO<br/>can also be used to gather floating car data from OBU/PID;<br/><br/>[Towards an Architecture for Cooperative-Intelligent TransportSystem (C-ITS) Applications in the Netherlands]<br/>
Element Source Role Target Role
«block» Central System
Block  
Name:  
 
Name:  
 
Details:
 
«block» Central System
Block  
Name:  
 
Name:  
 
Details:
 
Element Source Role Target Role
«block» BO Traveler Information Distribution
Block  
Name:  
 
Name:  
 
Details:
 
«block» Service Provider Geomessaging Client
Block  
Name:  
 
Name:  
 
Details:
 
«block» BO Traffic Information Distribution
Block  
Name:  
 
Name:  
 
Details:
 
«block» BO Application Specific Support
Block  
Name:  
 
Name:  
 
Details:
 
«block» BO Traffic Data Collection
Block  
Name:  
 
Name:  
 
Details:
 
Element Message
«block» Generic Application Specific Support  
Details:
Type: Sequence Synchronous Call
 
«block» Service Provider BO verify
Details:
Type: Sequence Synchronous Call
The Service Provider verifies the validity of the given signedServiceCertificate, by a) checking that its has been signed by a Registration Server which is part of the Certificate Chain of a known Root-CA. A Service Provider will refuse to serve a client, whose signedServiceCertificate has been issued by an unknown CA.
«block» x.509 Root Certification Authority obtainRootCertificate
Details:
Type: Sequence Synchronous Call
Each ServiceProvider installes the Root Certificate for each Root CA, so he as the same trust anchor(s) as all other entities.
Element Message
«block» x.509 Root Certification Authority  
Details:
Type: Sequence Synchronous Call
 
«block» Generic Application Specific Support register
Details:
Type: Sequence Synchronous Call
 
«block» Service Provider BO verify
Details:
Type: Sequence Synchronous Call
The Service Provider verifies the validity of the given signedServiceCertificate, by a) checking that its has been signed by a Registration Server which is part of the Certificate Chain of a known Root-CA. A Service Provider will refuse to serve a client, whose signedServiceCertificate has been issued by an unknown CA.
«block» Generic Application Specific Support use
Details:
Type: Sequence Synchronous Call
 
Property Value
_defaultDiagramType: SysML1.4::InternalBlock
Object Type Connection Direction Notes
«block» Central System Block Strong To  
«block» Service Provider Back-Office (SP-BO) Block Generalization To  
1 Port Dependency From .
«block» x.509 Root Certification Authority Block Dependency To Each SP needs to hold a certificate for all x.509 Root-CA's which he trusts, as long as they do not share a common trust anchor.
Service Providers Boundary Realization From  
«block» Service Provider BO Block Generalization To  
«block» Service Provider, Data Provider, Traffic Information Systems Block Generalization To