SelfCon Foil no 1 Dynamic component systems 2. SelfCon Foil no 2 Fire and burglar alarms Climate control: heating and cooling Power control: minimize.

Slides:



Advertisements
Similar presentations
Virtual Trunk Protocol
Advertisements

The Replica Location Service In wide area computing systems, it is often desirable to create copies (replicas) of data objects. Replication can be used.
When Applications can Roam Freely OSGi Service Platform R4 Peter Kriens Technical Director OSGi
SelfCon Foil no 1 Dynamic component systems 1. SelfCon Foil no 2 Pre-structured systems vs. dynamic component systems Pre-structured – emphasis on content.
LACP Project Proposal.
UCAIug HAN SRS v2.0 Summary August 12, Scope of HAN SRS in the NIST conceptual model.
TCP-IP Primer David Cozens. Targets Have a basic understanding of Ethernet network technology Be aware of how this technology is applied on the 5000 series.
Copyright © IBM Corp., All rights reserved. The presentation is licensed under Creative Commons Att. Nc Nd 2.5 license. RESTful Service Oriented.
CSCI 465 D ata Communications and Networks Lecture 20 Martin van Bommel CSCI 465 Data Communications & Networks 1.
G O B E Y O N D C O N V E N T I O N WORF: Developing DB2 UDB based Web Services on a Websphere Application Server Kris Van Thillo, ABIS Training & Consulting.
Network Management Overview IACT 918 July 2004 Gene Awyzio SITACS University of Wollongong.
Notes to the presenter. I would like to thank Jim Waldo, Jon Bostrom, and Dennis Govoni. They helped me put this presentation together for the field.
1 Internet Networking Spring 2004 Tutorial 13 LSNAT - Load Sharing NAT (RFC 2391)
William Stallings Data and Computer Communications 7 th Edition (Selected slides used for lectures at Bina Nusantara University) Internetworking.
CS 501: Software Engineering Fall 2000 Lecture 16 System Architecture III Distributed Objects.
SensIT PI Meeting, April 17-20, Distributed Services for Self-Organizing Sensor Networks Alvin S. Lim Computer Science and Software Engineering.
CS-3013 & CS-502, Summer 2006 Network Input & Output1 CS-3013 & CS-502, Summer 2006.
Systems Architecture, Fourth Edition1 Internet and Distributed Application Services Chapter 13.
2 Systems Architecture, Fifth Edition Chapter Goals Describe client/server and multi-tier application architecture and discuss their advantages compared.
Institute of Technology, Sligo Dept of Computing Semester 3, version Semester 3 Chapter 3 VLANs.
1 Spring Semester 2007, Dept. of Computer Science, Technion Internet Networking recitation #12 LSNAT - Load Sharing NAT (RFC 2391)
 The Open Systems Interconnection model (OSI model) is a product of the Open Systems Interconnection effort at the International Organization for Standardization.
1 CSCI 233 Internet Protocols Class 3 Dave Roberts.
Understanding Networks Charles Zangla. Network Models Before I can explain how connections are made from across the country, I would like to provide you.
OSPF To route, a router needs to do the following: Know the destination address Identify the sources it can learn from Discover possible.
Introduction to the Atlas Platform Mobile & Pervasive Computing Laboratory Department of Computer and Information Sciences and Engineering University of.
NetworkProtocols. Objectives Identify characteristics of TCP/IP, IPX/SPX, NetBIOS, and AppleTalk Understand position of network protocols in OSI Model.
Institute of Computer and Communication Network Engineering OFC/NFOEC, 6-10 March 2011, Los Angeles, CA Lessons Learned From Implementing a Path Computation.
Common Devices Used In Computer Networks
1 IP Forwarding Relates to Lab 3. Covers the principles of end-to-end datagram delivery in IP networks.
Enterprise Java Bean Matt. 2 J2EE 3 J2EE Overview.
Microcontroller-Based Wireless Sensor Networks
ANSTO E-Science workshop Romain Quilici University of Sydney CIMA CIMA Instrument Remote Control Instrument Remote Control Integration with GridSphere.
05 October 2015 Peter Mendham The SpaceWire-PnP Protocol: Status and Relationship with SOIS.
Chapter Three Network Protocols By JD McGuire ARP Address Resolution Protocol Address Resolution Protocol The core protocol in the TCP/IP suite that.
SelfCon Foil no 1 Self configurating systems - a starter Rolv Bræk, Item.
NETWORKING COMPONENTS AN OVERVIEW OF COMMONLY USED HARDWARE Christopher Johnson LTEC 4550.
PERVASIVE COMPUTING MIDDLEWARE BY SCHIELE, HANDTE, AND BECKER A Presentation by Nancy Shah.
Cisco 3 - LAN Perrine. J Page 110/20/2015 Chapter 8 VLAN VLAN: is a logical grouping grouped by: function department application VLAN configuration is.
Webservice versioning using osgi Allard Buijze, Jettro Coenradie.
CCNA 2 Week 1 Routers and WANs. Copyright © 2005 University of Bolton Welcome Back! CCNA 2 deals with routed networks You will learn how to configure.
Open Service Gateway Initiative (OSGi) Reporter : 林學灝 侯承育 1.
Chapter 15 – Part 2 Networks The Internal Operating System The Architecture of Computer Hardware and Systems Software: An Information Technology Approach.
7400 Samsung Confidential & Proprietary Information Copyright 2006, All Rights Reserved. -0/17- OfficeServ 7400 Enterprise IP Solutions Quick Install Guide.
JEMMA: an open platform for a connected Smart Grid Gateway GRUPPO TELECOM ITALIA MAS2TERING Smart Grid Workshop Brussels, September Strategy &
Discovering object interaction. Use case realisation The USE CASE diagram presents an outside view of the system. The functionality of the use case is.
CS 501: Software Engineering Fall 1999 Lecture 12 System Architecture III Distributed Objects.
SelfCon Foil no 1 Self configuring systems - introduction I.
Chapter 3 - VLANs. VLANs Logical grouping of devices or users Configuration done at switch via software Not standardized – proprietary software from vendor.
Outline The key findings What the SGA Summit did Smart City Amsterdam Some more detail on the disrupters – Ecosystem of the Grid – Distributed Generation.
12 Chapter 12: Advanced Topics in Object-Oriented Design Systems Analysis and Design in a Changing World, 3 rd Edition.
Networking Material taken mainly from HowStuffWorks.com.
Alex Leifheit NETWORKS. NETWORK A number of interconnected computers, machines, or operations. Key Components Network components, Network Architecture,
SelfCon Foil no 1 Variability in Self-Adaptive Systems.
Voice Over Internet Protocol (VoIP) Copyright © 2006 Heathkit Company, Inc. All Rights Reserved Presentation 5 – VoIP and the OSI Model.
目录 8 in 1 Sensor ◆ 8 in 1 Sensor Unique Features ● Built in PIR motion sensor and light intensity sensor ● Built in 2 Dry Input Ports ● Built in 32 Logics.
Object and Class Structuring Chapter 9 Part of Analysis Modeling Designing Concurrent, Distributed, and Real-Time Applications with UML Hassan Gomaa (2001)
Copyright 2007, Information Builders. Slide 1 iWay Web Services and WebFOCUS Consumption Michael Florkowski Information Builders.
Introduction.
COMPUTER NETWORKS Hwajung Lee. Image Source:
What problems are we trying to solve? Hannes Tschofenig.
Orion Contextbroker PROF. DR. SERGIO TAKEO KOFUJI PROF. MS. FÁBIO H. CABRINI PSI – 5120 – TÓPICOS EM COMPUTAÇÃO EM NUVEM
Real-Time Systems Lab. OSGi overview January 23, 2002 Sung-ho Park.
SelfCon Foil no 1 Pre-structured Systems. SelfCon Foil no 2 Pre-structured systems (e.g. SDL systems) Stable (cannot be added or changed dynamically)
SDN controllers App Network elements has two components: OpenFlow client, forwarding hardware with flow tables. The SDN controller must implement the network.
Internet and Distributed Application Services
ROLL Home Automation: draft-ietf-roll-home-routing-reqs
Layered Architectures
Chapter 3: Windows7 Part 4.
JINI ICS 243F- Distributed Systems Middleware, Spring 2001
Presentation transcript:

SelfCon Foil no 1 Dynamic component systems 2

SelfCon Foil no 2 Fire and burglar alarms Climate control: heating and cooling Power control: minimize power costs Smart metering (AMS) Access control Assisted living (well-fare technology) Entertainment Cooking Lighting Etc. Fire and burglar alarms Climate control: heating and cooling Power control: minimize power costs Smart metering (AMS) Access control Assisted living (well-fare technology) Entertainment Cooking Lighting Etc. Now let us look at the HNS system again

SelfCon Foil no 3 We want as much self adaptation as possible – how? Every device is networked! We want to plug in and out devices: heaters, alarm sensors, panels, power meters, appliances, weather stations,... We want to connect devices with service providing applications We want to (buy and) install applications We want to access external resources and to have remote access Every device is networked! We want to plug in and out devices: heaters, alarm sensors, panels, power meters, appliances, weather stations,... We want to connect devices with service providing applications We want to (buy and) install applications We want to access external resources and to have remote access

SelfCon Foil no 4 How simple can it get? The bare necessities: A component model for device and application components: Cpt A network with dynamic registration, routing and registry discovery: Rtr Registry functionality to register, lookup, subscribe-notify: Reg Life cycle support to install, update, remove components The bare necessities: A component model for device and application components: Cpt A network with dynamic registration, routing and registry discovery: Rtr Registry functionality to register, lookup, subscribe-notify: Reg Life cycle support to install, update, remove components

SelfCon Foil no 5 Basic component model Application specific services Generic support services Application specific services Generic support services C3 support s1 s2 s4 Reg Rtr Lcs C3 app

SelfCon Foil no 6 Using OSGi The component is a bundle with a manifest Provided as a Service object The component is a bundle with a manifest Provided as a Service object C3 support s1 s2 s4 OSG reg rtr OSGi LCS C3 app Provided and required Java interfaces Direct method calls on Service objects OSGi Registry API OSGi LSC API

SelfCon Foil no 7 Distributed support Asynchronous messaging for real-time, distribution and flexibility Global Rtr for distribution transparency Global Reg for remote find-bind Asynchronous messaging for real-time, distribution and flexibility Global Rtr for distribution transparency Global Reg for remote find-bind C3 global S1’ S2’ S4’ Global Reg OSGi LCS C3’ app’ C3 local Global Rtr OSGi reg Message interfaces over Rtr Message interface over Rtr Java interfaces Java interface

SelfCon Foil no 8 A distributed system using OSGi OSGi Reg Global RTR OSGi LCS Global COM App CPT 1 App CPT 2 App CPT n Global Reg Network OSGi Bundle

SelfCon Foil no 9 Important issues to consider The nature of components: Just Java classes? State machines? Other? Dealing with concurrency: Just Java Threads? Concurrency and real-time support? How to communicate: Just Java method calls? Web services, JSON, HTTP,....? Asynchronous messaging? Devices and network issues: Device drivers; I/O Timing constraints The nature of components: Just Java classes? State machines? Other? Dealing with concurrency: Just Java Threads? Concurrency and real-time support? How to communicate: Just Java method calls? Web services, JSON, HTTP,....? Asynchronous messaging? Devices and network issues: Device drivers; I/O Timing constraints

SelfCon Foil no 10 Global Component Model Identity: unique ID generated for each Cpt and session Rtr interface: Registering in Rtr Discover Reg: getting the Reg address (or use well-known ID) Reg interface: Register Cpt services (i.e. collaborations) in Reg Look up other Cpt services according to application Application services (i.e. collaborations): Dynamically link service roles according to application and ctx Identity: unique ID generated for each Cpt and session Rtr interface: Registering in Rtr Discover Reg: getting the Reg address (or use well-known ID) Reg interface: Register Cpt services (i.e. collaborations) in Reg Look up other Cpt services according to application Application services (i.e. collaborations): Dynamically link service roles according to application and ctx

SelfCon Foil no 11 Case 1: Access Control System The structure of components is to be “magically” created by the components themselves when plugged in... with a little help from the router and the registry using the Acs Point name as association key The structure of components is to be “magically” created by the components themselves when plugged in... with a little help from the router and the registry using the Acs Point name as association key Logical structure “Physical” structure

SelfCon Foil no 12 Creating links The seeker uses Lookup while the responder uses Register The seeking direction can be determined for each collaboration/interface Here we have chosen the many-to-one direction An Association Key is needed to select instances – here the ACS Point Name A component may be both seeker and responder, but in different collaborations Lookup and Register must deal with collaborations and roles, not just CPT The seeker uses Lookup while the responder uses Register The seeking direction can be determined for each collaboration/interface Here we have chosen the many-to-one direction An Association Key is needed to select instances – here the ACS Point Name A component may be both seeker and responder, but in different collaborations Lookup and Register must deal with collaborations and roles, not just CPT

SelfCon Foil no 13 Access Control System with link creation Rtr and Reg omitted for simplicity below Each component have: one or more static collaboration sessions with other components, maintained locally by roles Responder or Seeker roles(to perform Register or Lookup) for each link application behaviour using the roles. basic component management behaviour, e.g. OSGi Rtr and Reg omitted for simplicity below Each component have: one or more static collaboration sessions with other components, maintained locally by roles Responder or Seeker roles(to perform Register or Lookup) for each link application behaviour using the roles. basic component management behaviour, e.g. OSGi

SelfCon Foil no 14 Component model illustrated A Cpt can have any number of collaborations with different seeking directions Each is established by a seeker-responder pair interacting with the Registry Collaboration behaviour is application dependent There is a port at each end of a link The ports register in the Rtr and the portID is used as message addresses A Cpt can have any number of collaborations with different seeking directions Each is established by a seeker-responder pair interacting with the Registry Collaboration behaviour is application dependent There is a port at each end of a link The ports register in the Rtr and the portID is used as message addresses

SelfCon Foil no 15 A possible Plug-In sequence Assumptions: The ports generates their own PortID The PortID is registered in the Rtr tables The Reg has a well-known identity provided as parameter Assumptions: The ports generates their own PortID The PortID is registered in the Rtr tables The Reg has a well-known identity provided as parameter

SelfCon Foil no 16 Generic Seeker and Responder as blocks Manages collaboration session establishment Provides session messaging Manages collaboration session establishment Provides session messaging

SelfCon Foil no 17 Global Registry A Responder registers: Register(Cpt ID, Ass Key, Collaboration Name, Responder Port ID) A Seeker Looks up: Lookup(Ass Key, Collaboration Name) The registry is stateless A Responder registers: Register(Cpt ID, Ass Key, Collaboration Name, Responder Port ID) A Seeker Looks up: Lookup(Ass Key, Collaboration Name) The registry is stateless

SelfCon Foil no 18 Addressing and Routing Routing is based on Ports and Port ID Each (stateful) session has a Port at each end with its own Port ID and a reference to the remote Port Session ID Each port registers in the Rtr table with its own Port ID The Rtr table maps from Port ID to Java message listeners Routing is based on Ports and Port ID Each (stateful) session has a Port at each end with its own Port ID and a reference to the remote Port Session ID Each port registers in the Rtr table with its own Port ID The Rtr table maps from Port ID to Java message listeners Message SignalID: String Sender: PortSessionId Receiver: PortSesssionId Payload: Object

SelfCon Foil no 19 Distributed routing A router in each node NodeID part of address Routing tables dynamically updated as cpt come and go (self adapting) A router in each node NodeID part of address Routing tables dynamically updated as cpt come and go (self adapting)

SelfCon Foil no 20 Developing the Access Control Application 1.Develop the component types 2.Create the objects needed, provide Ass Key information to each object 3.Start the objects and let the system self configure: 1.responding roles dynamically Register 2.seeking roles dynamically Lookup and link to responding roles 4.The validation database has to be entered by other means 1.Develop the component types 2.Create the objects needed, provide Ass Key information to each object 3.Start the objects and let the system self configure: 1.responding roles dynamically Register 2.seeking roles dynamically Lookup and link to responding roles 4.The validation database has to be entered by other means

SelfCon Foil no 21 Simple Home Heating App Any number of rooms, any number of heaters in each Temperatures and programs set for each room, either locally or centrally Everything plugged in and linked dynamically... but there is a problem... Any number of rooms, any number of heaters in each Temperatures and programs set for each room, either locally or centrally Everything plugged in and linked dynamically... but there is a problem...

SelfCon Foil no how to Input a room plan if desired? Associate components with rooms? 1.By network segment 2.By manual identification Input a room plan if desired? Associate components with rooms? 1.By network segment 2.By manual identification

SelfCon Foil no 23 Smart Home Heating Takes power price and weather into account and uses shades/curtains to collect and conserve energy when possible Now there is a choice between Simple- and Smart-H-Heat Takes power price and weather into account and uses shades/curtains to collect and conserve energy when possible Now there is a choice between Simple- and Smart-H-Heat

SelfCon Foil no 24 How to deal with variability in types? Type selection in seeking Direction of seeking Ensuring compatibility across interfaces – interoperability Type selection in seeking Direction of seeking Ensuring compatibility across interfaces – interoperability

SelfCon Foil no 25 Discussion items Physical networking Network protocols How to really plug-in and plug out devices How to select among alternatives How to discover the configuration at startup and restart? Associate devices with rooms? Input the overall room plan? Load new services and device types? Using existing protocols like UPnP Physical networking Network protocols How to really plug-in and plug out devices How to select among alternatives How to discover the configuration at startup and restart? Associate devices with rooms? Input the overall room plan? Load new services and device types? Using existing protocols like UPnP