1. WP4 – Deployment of “smart”
services toolkit
WP4 leader: MOSS Tasks: T4.1 - T4.9
Presented by: Daniel Holweg

2. WP4 – Deployment of “smart” services toolkit
• Agenda
• WP 4 challenge
• WP 4 realization plan
• WP 4 current achievements
• WP 4 next steps

3. • Agenda
• WP 4 challenge
• WP 4 realization plan
• WP 4 current achievements
• WP 4 next steps
WP4 – Deployment of “smart” services toolkit

4. WP 4 summary
Goals:
-Development of smart services
- Platform and basic services
- Thematic smart-city services
-Development of clients
- Web client
- Mobile client
-Delivery of an integrated and functional client-server solution
Start: 15.07.2012.
End: 15.01.2014.
Deliverables:
Prototypes: D4.1, D4.2, D4.4
Reports: D4.3, D4.5
Deliverable deadline: 15.01.2014.

5. WP organisation
i-SCOPE timetable
Resouces:
- existing results from other
projects / existing solutions
- 178 PM

6. Partners involved and their role
T 4.1 MOSS 3D Service Technology Platform
T 4.2 EPS Designed-for-all personal routing service
T 4.3 VUB Real-time environmental noise mapping service
T 4.4 MOSS Environmental noise simulation
T 4.5 MOSS Solar energy potential assessment service
T 4.6 FG Web client
T 4.7 REG Mobile client for citizens
T 4.8 CL3 Security and privacy enforcement
T 4.9 REG
Integration of new smart services with existing service
infrastructures

7. WP 4 challenge and status
• Challenge:
• largest WP
• main technical results
• Status & main activities
• formal start of WP July 2012
• evaluating main concepts for the platform and the services
• Deployment of core platform Infrastructure (Datamanagement /
CityGML generation)
• development of core service functions
• ToDos
• Integration

8. • Agenda
• WP 4 challenge
• WP 4 realization plan
• WP 4 current achievements
• WP 4 next steps
WP4 – Deployment of “smart” services toolkit

9. System overview
Security and privacy (T4.8 C3L)
Building generation
service (MOSS)
Data management
service (MOSS)
3D Technology Plattform
(T4.1 MOSS)
Smart services - Integration (T4.9 REG)
WEB Client (T4.6 FG) Mobile Client (T4.7 REG)
Routing service
(T 4.2 EPS)
Noise mapping
(T4.3 VUB)
Solar assessment
(T4.5 MOSS)
noise simulation
(T4.4 MOSS)

10. • Approach to implementation
• Distributed development of service
• Implementation workshops on task level
• Approach to integration
• Interface definitions
• Concept for synchronous / asynchronous services
• Ongoing integration based on agreed testbeds
• Regulary telcos and integration Workshops on WP level
WP4 – organisation

11. • Agenda
• WP 4 challenge
• WP 4 realization plan
• WP 4 current achievements
• WP 4 next steps
WP4 – Deployment of “smart” services toolkit

12. WP start 07.2012
Exampels
• 3D Technology platform (Task T4.1 )
• service definition
• processing test data
• Solar potential assessment (Task T4.5 )
• Draft of evaluation report
• Application prototype
WP4 – Current achievements

13. 3D Technology platform (Task T4.1 )
• Service definition technology platform
• Import surveying data (test data Trento)
• Data adjustment
• Building generation
• Export CityGML
Service examples - Processing test data (Trento)

14. 3D City
Database
CityGML
novaFACTORY novaFACTORY
Export3D CityDB
Imp/Exp
CityGMLCityGML
DSMDTM Floor plan
3D Technology Platform
Import
Service examples - Processing test data

15. Service exampels - Processing test data (Trento)
database (distribution)
DTM, LIDAR, footprints
raw data
database (production)
clearing data

16. Data example - Trento

17. Data example - Trento

18. Solar potential assessment (Task T4.5 )
• Analysis of user requirements
• Elaboration of user scenario
• Data definition (WP3)
• Draft of WEB Interface
• Draft of evaluation report
• Style for data transformation
• Prototype for WEB application
Service examples - Prototype Solar potential assessment

19. Service examples - Prototyp Solar potential assessment
Draft of report
Map of building and
surrounding
Evaluation settings
Evaluation period
Coverage with panels
Panel efficiency
aquisition costs

20. Service examples - Prototype Solar potential assessment
Draft of evaluation report
• Evaluation settings
• Evaluation results (per
building / roof)
Electrical yield
Reduction of costs
Aquisition costs
Return of investment
CO2 savings
Total line
• Roof texturing

21. • Agenda
• WP 4 challenge
• WP 4 realization plan
• WP 4 current achievements
• WP 4 next steps
WP4 – Deployment of “smart” services toolkit

22. Next Steps
• WP just begun
• smart services
• Implementation based on WP 1 / WP 2 outcomes
• Common data-structure (CityGML) based on WP 3
outcomes
• Integration
• Basic platform installation (Sep. 2012)
• Specification of interfaces including integration of
security and privacy aspects
• Initial training in technology platform and existing
interfaces (Oct. 12)

23. Data example - Trento

24. Thank you for your attention
Contact details
Daniel Holweg
M.O.S.S. - dholweg@moss.de

25. Privacy and Security Enforcement
Update on status of T.4.8

26. How we approach security
2

27. Security Reference Model
i-Scope
user
i-Scope
System
Authorization
Authority
Identification
Authority
Ref S1
Ref S4
Ref S3
Ref S2
Consent
Authority
Ref S5

28. Initial enforcement of identity and authenticity
1. Provision of identity token and symmetric key
pair by i-SCOPE security manager
– Using “off the shelf” token manager for hardware
and platform – TBD which package
2. Identity brokering for SSO with software
platform based on JOSSO or similar
– This links into SAML for assertions (and XACML and
hopefully ExTRA)

29. Standardisation as enforcement
• Development of ExTRA
– ETSI TC MTS workplan
• Development of PbD and DfA paradigms
– In ETSI EP E2NA in TC NTECH
• SSO and Identity Management in Networks
– Probably in ETSI EP E2NA in TC NTECH
– Some work in ETSI M2M and 3GPP SA3
31

30. SAML, XACML and ExTRA as assertion platforms
• The general language of security assertions is as
follows:
– Assertion A was issued at time t by issuer R
regarding subject S provided conditions C are valid.
• This is what the receiving and relying entity is
provided with and the security model requires
the each of t, R, S and C are validated to ensure
that any action dependent on A is provably
allowed.

31. ExTRA – the extension of TPLan to security
• ExTRA is a stimulus-response notation that
operates at a high level of design
ensure that {
when { ... } -- stimuli
then { ... } -- responses and other behaviour
}
• This is our target meta-language with
SAML/XACML as target implementations