The CHOReOS project aims to develop choreographies for ultra-large scale service coordination in the future internet. It introduces a dynamic development process and middleware to implement and coordinate decentralized services through choreographies. The project is an FP7 initiative with 15 partners and a budget of 8.6 million euros. It seeks to address challenges of heterogeneity, scalability, and distribution in future internet architectures through a choreography-centric approach.

1. The CHOReOS FP7 project
and the Future Internet OW2 initiative
Pierre CHÂTEL – Thales Communications
OW2 Annual Conference
Template v1
November 25th, 2010

2. What is CHOReOS ?
“Large Scale Choreographies for the Future Internet”
 Main goal: sustaining decentralized service choreographies
 Specific context: Future Internet (FI), Ultra Large Scale (ULS)
 Abstract: “It revisits choreography-centric SOAs by introducing a
dynamic development process and middleware for the
implementation and coordination of services through choreographies”
Ultra
Future
CHOReOS Large
Internet
Scale
In this presentation…
 main tenets behind Future Internet and Choreography of Services
2

3. CHOReOS at a glance
Duration: European programme:
 October 2010 –  Call FP7-ICT-2009-5
September 2013  Grant n°257178
Consortium of 15
partners:
 7 industrials Further information:
 8 academics
 http://www.choreos.eu
Total budget:
 8.665.785 €
3

4. Consortium
7 industrials 8 academics
4

5. From Context…
Help with the next big step in
system architectures
Future Internet
Ultra-Large
Internet Scale
revolution
Interconnected Highly
Interconnected computers Distributed
mainframes around the globe Systems
through dedicated
channels Web Services
Individual High
“disconnected” Local networks of Heterogeneity
… computers small computers
Cloud Computing
1980 Today
5

6. …to Framework
The CHOReOS Integrated Dev. & Runtime Environment (IDRE)
Formally grounded Choreography-centric
abstractions and models development process
and runtime
Handle Ultra- Handle high
Large Scale service
distributivity
Service-oriented Governance and V&V
middleware for the support
Future Internet
Handle high
heterogeneity
6

7. Table of Content
CHOReOS
 European FP7
 OW2 implication
Main concepts
 Future Internet
 Service Choreography
 Cloud
Use Cases
 Air Travel Logistics
 Others
7

8. Positioning inside FP7
“7th Framework Programme for Research and
Technological Development”
 Bundles all research-related EU initiatives
together under a common roof
 from 2007 to 2013, € 50 billion budget
 Objectives grouped into
Specific Programmes:
Cooperation, Ideas, People, Capacities.
 CHOReOS: Cooperation / ICT Programme
 Theme: Information and Communication Technologies
 Challenge 1: Pervasive &Trusted Network & Service Infrastructures
 Objective 1.2: Internet of Services, Software and Virtualization
 Outcome: Service Architectures and Platforms for the Future Internet
8

9. OW2 Implication
Community building
 Collaborative services to project teams
 Forge to centralize all developments: including models, UML profiles and code
Dissemination
 Through OW2 activities (marketing services, organizing conferences, …)
 CHOReOS artifacts published as Open Source Software (LGPL)
OW2 “Future Internet” initiative
 “(…) joint efforts by OW2 Members to develop technical integration between
projects and business synergies in order to address specific market needs”
 grouping of scope-bound projects, CHOReOS is the first in this initiative
 will help broaden the spectrum of CHOReOS and facilitate dissemination to a
wider community of users and developers
9

10. OW2 Related projects
Identifying synergies with existing projects
 Orchestra
 “...solution to handle long-running, Service Oriented
Processes”
 JORAM
 “…distributed MOM… designed with an OSGiTMbased
services architecture to provide a dynamically adaptable
messaging server”
 Fractal
 “…a modular, extensible and programming language
agnostic component model that can be used to design,
implement, deploy and reconfigure systems and applications”
 SOFA
 “...used for dynamic reconfiguration of component
architecture and for accessing components under the SOA
concepts”
10

11. Table of Content
CHOReOS
 European FP7
 OW2 implication
Main concepts
 Future Internet
 Service Choreography
 Cloud
Use Cases
 Air Travel Logistics
 Others
11

12. Table of Content
CHOReOS
 European FP7
 OW2 implication
Main concepts
 Future Internet
 Service Choreography
 Cloud
Use Cases
 Air Travel Logistics
 Others
12

13. Future Internet Overview
FP7 / Cross-ETP (European Technology Platforms) vision
http://www.future-internet.eu
Future Networked Society
Accomodation of Interactive Context aware Permanent
all users multimedia content autonomic seamless
requirements everywhere objects services
Internet Internet
of Internet Internet
by and
Contents of of
for and Things Services
People Knowl.
Future Network Infrastructure
Scalable & dynamic routing and addressing Security, privacy, trust
Efficient data & traffic management Availability, ubiquity, simplicity
Adaptability to heterogeneous environments Energetic and economic sustainability
13

14. Future Internet The Four Pillars
Internet by and for People
 Goal: to break the digital divide, by interconnecting growing
populations of new users over time; to meet their needs and
expectations
Internet of Contents and Knowledge
 Goal: to support mechanisms for knowledge dissemination both at
local and global level. Knowledge & culture should be distributed
worldwide
Internet of Things (IoT)
 Goal: to create an universally addressable continuum, with objects as
“living beings”. They will have defined behaviors, actions and unique
way of individual identification
Internet of Services (IoS)
 Goal: to enable internet-scale service oriented computing as the next
evolutionary step after components. “Loose coupling” between service
consumers and producers (instantiated by the “Cloud” paradigm)
14

15. Future Internet FI & CHOReOS
A full-fledged choreography framework should help deal
with specific FI characteristics
CHOReOS manages:
 Major characteristics of “Internet of Things”
 High heterogeneity: totally different objects in terms of functionality,
technology and application fields
 Ultra Large Scale: a unique identifier for every object (Pervasive
technologies) that need to communicate with each-other in a meaningful
way
 Major characteristic of “Internet of Services”
 Distributivity: numerous service orchestrations, dispatched over the
Internet, that need to communicate through message exchanges, but
without a single point of control
15

16. Table of Content
CHOReOS
 European FP7
 OW2 implication
Main concepts
 Future Internet
 Service Choreography
 Cloud
Use Cases
 Air Travel Logistics
 Others
16

17. Choreography In the “real world”
Orchestration: Choreography:
 Local / centralized perspective  Global / distributed perspective
 "Each player in the orchestra  “Dancers dance following a
strictly follows instructions from global scenario, without a single
the conductor" point of control"
17

18. Choreography In SOAs
Service orchestration: Service choreography:
 Refers to an executable  Describes a non-executable
business process, with a protocol for peer-to-peer
specific (business) goal interactions
 Represents control from one  Legal sequences of exchanged
messages between peers
party’s perspective (the
orchestrator)  Tracks the message exchange
among multiple parties
 Interactions occur at the
 More collaborative: allows each
message level
party involved in the interaction to
 Between orchestrator and services describe its part
 Message sequence controlled by  Guarantees interoperability by
orchestrator reflecting obligations and constraints
 Allows recursive combination between parties
 Orchestrated processes accessible  Interactions still occur at the
through WS interfaces message level
 Orchestration of composite WS  But directly between services
18

19. Choreography Why ?
Future Internet context:
 More and more distributed architectures and systems
 Large number of to-be-coordinated services,
 Heterogeneity in services, providers
Choreographies to organize services, plan processes
when centralized approaches are inapplicable,
deprecated
Avoid single points of failure
19

20. Choreography Overview in SOA
Choreography
Composite WS Composite WS
Orchestration Orchestration
Message exchange
WS WS WS WS
Message exchange
(..)
WS WS
Complex conversations
beetween orchestrations
Orchestrator Orchestrator
20

21. Choreography Specifications
 Two paradigms [Decker, 2008]:
I. Interconnected Interfaces Modeling: choreography logic split across its
participants through the roles they play, as specified by their interfaces.
II. Interaction Modeling: choreography logic as a workflow, elementary interactions
represent message exchanges between participants
Independent
BPMN 2
BPMN1.x BPSS
Let’s Dance
Dependent
WSCI
WSFL WS-CDL
BPEL4Chor
Interface (type I) Interaction (type II)
21

22. Choreography BPMN specification
 BPMN (Business Process Modeling Notation)
 “De-facto standard for process modeling on the implementation independent
level” [Decker, 2008], maintained by the OMG
 v1.x (2004) follows type I paradigm (Interconnected Interfaces) :
 participants = swim lanes (pools), interconnected by message flow, in a
collaboration model
 v2.0 (2010) introduces type II paradigm (Interaction):
 each step (Choreography Task) involves at least two participants
Order
Customer Customer Customer
Order
Order request Deliver product
confirmation
Seller Seller Seller
Confirmation Product
22

23. Table of Content
CHOReOS
 European FP7
 OW2 implication
Main concepts
 Future Internet
 Service Choreography
 Cloud
Use Cases
 Air Travel Logistics
 Others
23

24. CHOReOS in the Cloud…
Goal : enable scalable service provisioning based
on Cloud computing
 Well recognized technology for sustaining very large load
 ULS  we need to support computationally-intensive processes that serve
millions of users issuing thousands of simultaneous service requests
to thousands of services
 General idea: Cloud as “another” deployment target
 A Choreography is not directly executable
 Translation/compilation process  multiple corresponding orchestrations
 Part of these orchestrations deployed on the Cloud
 Implementation: Apache Hadoop
 … combined with InteGrade Grid Computing technology
 To enable scalability in terms of users, requests, services, choreographies,
and computing nodes
24

25. Table of Content
CHOReOS
 European FP7
 OW2 implication
Main concepts
 Future Internet
 Service Choreography
 Cloud
Use Cases
 Air Travel Logistics
 Others
25

26. UC1 Air Travel Logistics
Description
 Air transportation / service to passengers
 actual coordination proven inefficient during unexpected events
 Bad weather at destination  flight rerouted to another airport
 passengers p.o.v.: stress, lack of information, delays everywhere
 service providers differ between airports, flights  flexibility need
 Choreographies are introduced as part of a global solution
 already existing business processes (orchestrations) for specific/local parts
of the scenario, with well-known orchestrators (e.g. air traffic control, airport
authorities, airlines)
 lack of broad-spectrum/global choreographies…
 between these areas of responsibility
 between first and second-level actors (e.g. luggage handling company,
airport information desk, hotels, travel agencies, ground transportation,
passengers, …)
26

27. UC1 Global choreography
Passenger (…)
New info from
ATC Air traffic control (…)
Passenger
Inform Inform passengers
Pilot
Pilot
In-flight
information
Plane will land only when
Air traffic control logistics has been set-up at
Pilot destination
Air traffic control Dest. Airport
Confirm approach Check gatevand transit
on info. displays
Pilot
(…)
Passenger
Airport Bus Company
Luggage Handling Company
Air traffic control Air traffic control Air traffic control Ground staff
Inform
Confirm new Prepare for unexpected Inform about local
Reroute request Destination
destination arrival modalities
airport
Pilot Pilot Dest. Airport
New
Dest. Airport
Security Company
(…)
Passenger
arrival
Air traffic control
Ground staff
(…)
Travel agency
Prepare for unexpected
Inform about journey
arrival
alterations
Inform
Airline
Airline
Airline
(…)
Passenger
Travel agency
Delay (…)
27

28. UC1 A sub-choreography
Ground staff
Synchronize with travel
agencies
Available
Passenger hotel list
informations
Ground transportation
Travel agency Hotels
Airline
Inform of
Obtain hotels list and
unexpected Book Make reservation
update information
arrival
Ground staff
Ground staff Ground staff Ground staff
Current Passenger
Destinations
information informations
Passenger
informations
Airline
Inform of unexpected
arrival
Travel agency
Airline
Travel agency
28

29. UC1 Expected impact
Before CHOReOS After CHOReOS
 At alternate airport  At alternate airport
 Delays everywhere (plane  Less delays in rerouting-
logistics, handling passengers consequences
luggage, …)
 At airline level
 At airline level  Efficient coordinated logistics
 impervious dedicated logistics  Costs reduction
for each situation
 Improved flight rescheduling
 For passengers process
 Poor indications  For passengers
 Extra costs  Better information
 Waste of time  Less waste of time and money
 … extra stress !  Improved airline/brand image
29

30. UC2 - 3 Other use cases
Citizen journalism
 Collection, report and dissemination of news and information by
the public
 interaction among millions of (smart-phone) users who share information
 lack of coordination and verification of provided contents and contributions
 Dynamically composed large-scale choreographies introduced
 for run-time integration of services provided by different users
 Mobile-enabled coordination of people requires ULS and QoS-
aware systems in terms of concurrent users
DynaRoute
 Mobile-enabled coordination of people
30

31. Conclusion
Future internet is multifaceted, as are the associated
issues and challenges
CHOReOS provides solutions at the conceptual and
technical level
 Is focused on certain aspects of the FI !
 Highlights a coordination paradigm that is both distributed and of
higher granularity that orchestrations  Choreographies
Choreographies as a core of these solutions, in order to
deal with…
 Ultra-Large Scale problems
 High distributivity of systems & architectures based on services
 Heterogeneity of these services
31

32. Contact
 Address :
Pierre CHATEL
Thales Communications France
DSC/R&T/CEA/SC2
Campus de Polytechnique
1, avenue Augustin Fresnel
91767 Palaiseau Cedex - France
 Mail :
pierre.chatel@thalesgroup.com
 Phone:
+33 (0)1 69 41 55 65
32