Things : EPC and beyond. Wolf Rüdiger Hansen / AIM Germany, Dr. Alexander Pflaum / Fraunhofer Institute for

Transcription

1 Architectures for Realization of the Vision Internet of Things : EPC and beyond Wolf Rüdiger Hansen / AIM Germany, Dr. Alexander Pflaum / Fraunhofer Institute for Integrated Circuits IIS and Center for Intelligent Objects ZIO, Brussels, 30. June 20

2 Content. IoT: Uncertainness of Definitions - Where are we today? 2. New Dimensions beyond the EPC Network Architecture 3. A preliminary Definition for the Internet of Things 4. Smart Objects, smart Things, Technologies 5. A Functional Perspective on the basic Technologies of IoT 6. Examples for Solutions and Specialties of corresponding Architectures 7. Conclusion and Challenges 2

3 Recent Milestones in the IT World 8. June 20 Introduction of the internet protocol IPv6 340 sextillions (036) internet addresses > This address space allows unique internet addresses for all things Apple introduces the icloud goals Disempowerment of the PC as synchronization instrument. Automatic connection of iphones, ipads etc. with the Apple icloud -> and thus with the IoT RFID readers communicate increasingly with the cloud as AIM member companies confirm Assumption: The cloud will be the platform for the IoT Side aspect: All these developments are boosting the issues of reliable autoid procedures data protection and privacy -> see PIA Framework 3

4 Dimensions of the Future IoT Why this Presentation? In order to foster awareness for current shortcomings like:. Comprehensive approach: We always need to be aware of the whole picture of the future IoT when while discussing special details 2. Broad technology scope: RFID plays only a selective role in the future IoT. Other autoid technologies will also be there like data matrix 3. Smart objects revolution: Need new ways of bi-directional communications 4. Overcome the point-to-point to style of EDI communications : Towards any-to-any-communication 5. Performance: We must also discuss the future IoT of the performance capabilities of its components 4

5 Uncertainness regarding the Definition of IoT It s a metaphor, Dr. Peter Friess, European Commission There is no accepted definition., Prof. Dr. Wolfgang Kleinwächter, University of Aarhus It s a vision, Prof. Dr. Friedemann Mattern, Technical University of Zurich It comprises intelligent houses, networked clothes controlling body functions, cars, all the things we are carrying with us, office equipment, Vint Cerf, Google, inventor of the Internet Protocol (IP) Today, the IoT is a foundation for connecting things, sensors, actuators, and other smart technologies, thus enabling person-to-person and object-to-object communications., Prof. Dr. Bernd Scholz-Reiter, University of Bremen (Foreword of the book: Dieter Uckelmann et al. (Eds.): Architecting the Internet of Things, Springer, Germany, 20) We would add: and person-to-object communications 5

6 Internet of Things: Where are we today? Only preliminary stages reached so far: Building access and smart card ticketing: RFID is daily live Manufacturing: controlling production lines and internal asset management: RFID dissemination in progress. Retail/EPC sector: Predicted -cent RFID tag Not available, realistic price: > 5 Cent RFID tags on items Attached only on RFID-friendly items like apparel and expensive products or on RTIs / assets. Non-RFID data carriers Integrated like bare code, data matrix Cross enterprise communication Still with EDI in a point-to-point style - including EPCIS Internet of Things, central component: F-ONS under test at Orange, France; DS not available Military sector / DoD: Central repository & workflow system in place (A proprietarily controlled system) Item marking with data matrix in place RTI marking with RFID in place A variety of numbering schemes supported Other sectors: Initial projects on the way 6

7 Basic EPC Architecture Elements The original approach of the EPC architecture: Traditional data flow from bottom (item) via EPCIS to top (ERP business application / ONS) Data capture oriented collecting GS data formats Interesting news: bar code and other ID symbologies supported Filtering & Collection covered by software today s RFID readers Further requirements to be implemented: Reverse data flow from top to bottom e.g. to communicate with sensors, actuators, t smart objects Enrichment of business functions on the distributed level - richer than just capturing applications > towards real-time business monitoring and control ONS, DS, ERP Business application (RFID-independent) Data capture (RFID-specific) Bar code or other inputs Filtering & collection is covered by today s reader software Figure from The EPCglobal Architecture Framework, Version.4 Approved 5 Dec

8 Extended EPCglobal Architecture reaching for more The traditional vertical dimension: mainframe and ERP oriented. 2 The new horizontal dimension i offering new interfaces to sensors, actuators, smart objects. Interesting new terms: dynamic data federated systems negotiations with other agents non IP interface 3 Gateway to non-epc worlds? The EPC numbering scheme is no more a prerequisite for using this architecture. (Dieter Uckelmann*) Core architecture 3 Question: This approach tries to integrate completely new elements into a traditional concept. Is this leading to a reliable future solution? Edge architecture * Source: Uckelmann et al. (Eds.): Architecting the Internet of Things, Springer Verlag Berlin Heidelberg 8 20: 2

9 Systems Landscape supporting the future IoT Virtual world the cloud Enterprise systems ERP Other enterprises Proprietory ONS DS Other enterprises Other EPCIS EDI Communication interfaces Future look-up and negotiation services Data capturing local business applications software agents ID Sensor Actuator numbers data commands Real world?? Bi-directional communication AutoID readers other communication units Smart objects, product memories Basic Actuators autoid Sensors ID numbers: EPC and others Real world objects / items The future internet will provide:. New services for not pre-defined cross enterprise communications 2. Enrichment of the operational power of local systems towards business monitoring and control 3. New communication services to all kinds of real world objects particularly l to smart objects. 9

10 The Internet of Things fulfills User Needs along the Life Cycle Process using Technologies of smart Objects Internet of Things A preliminary Definition End of life Birth Thing Life cycle of the smart thing smart User Needs along the life cycle process Solutions delivered by different types of solution providers based on internet and basic technologies of smart things The Internet of things IoT could be understood as the continuum of smart object based useroriented solutions which are incorporating internet technologies Solution provider 0

11 Things come from every Area of Life and need different Types and Degree of Smartness Smart Objects and Things Things to be taken into account: Artificial products like FMCG, food, apparel Complex things like machines, parts, vehicles Items like packages, pallets, containers Natural products like trees, bushes, reefs, corn as well as animals and human beings Smartness realized ed by embedding microelectronic modules into the thing in order to connect it to the internet using wire or wireless communication and to move business logic and intelligence from the IT backend to the thing itself to integrate the physical world and the world on physical goods

12 Different Types of microelectronic Tags can be attached to or integrated into different Types of Things Different Types of smart Object Technologies Wireless tags are attached to things without connecting them: UHF-RFID on mechanical spare parts HF-RFID on product carriers WSN on expensive clinical assets Sensor tags accompanying pharmaceutical products Telematics modules on sea containers Smart object functions integrated into products with Internet t connection UHF-RFID for Retail & Logistics Wireless sensor networks Electronic tags with sensors Telematics modules Coffee maker Refrigerator with display Cars and other vehicles HF-RFID for production Real-time locating tags References: Siemens, KSW microtec, Ekahau, Fraunhofer IIS, OnAsset 2

13 Six Functions of the microelectronic Modules support Integration of material and virtual World Internet of Things Integration gets better in case that Logic Data Storage 0 Networking Barcode Identification single products can be identified & Paper unambiguously (identification), Locating Solutions based on smart things / objects Sensors * According to Pflaum, A., Hupp, J. (2007) their current position is lodged in the information system (location), the current state of the products is well known to the system (sensors), the products are always within reach for relevant players (networking), the history of the goods is directly attached to themselves (data storage), the single products are able to detect critical situations (logic). 3

14 The functional Profile of the microelectronic Module determines the Architecture of the Solution Integration Capability of different wireless Technologies Logic Identification Logic Identification Logic Identification Logic Identification Logic Identification Logic Identification Data Storage 0 Locating Data Storage 0 Locating Data Storage 0 Locating Data Storage 0 Locating Data Storage 0 Locating Data Storage 0 Locating Networking Sensors Networking Sensors Networking Sensors Networking Sensors Networking Sensors Networking Sensors HF-RFID for production Electronic tags with sensors UHF-RFID for retail/logistics Real-time locating tags Wireless sensor networks Telematics modules Increasing integration capabilities and potential benefits Higher degree of complementary innovations Increasing system and implementation costs Internet of Things Solutions are based on different Architectures! The EPC architecture is one of many! 4

15 Supply Chains for Food and other FMCGs need EPC based Information Services in order to create Transparency Example Tracking and Tracing of Goods in the FMCG Sector Functionality of tag is limited to identification Standard architecture with mobile and fixed readers, middleware, tracking & tracing software Perfect fit between requirements and EPC based Internet of Things architecture: No numbering scheme for unambiguous and global product identification Open logistics systems do not allow pooling of electronic tags Supply Chain structures and distribution of power support services from third parties EPC architecture has a good chance in case that business cases are positive for customers 5

16 Lufthansa Technik is using UHF-RFID and internal Service Providers in order to track and trace Parts worldwide Example Focus on identification based on RFID tags Standard architecture with mobile and fixed readers, middleware, tracking & tracing software Striking similarity with existing RFID installations in the retail sector, but: Industry is using its own complex numbering schemes and license plates Spare parts are running in a closed pool system where third party information providers are not really needed Global companies like LHT are therefore e e building up their on systems based on already existing IT infrastructures 6

17 Hospitals will use wireless Sensor Networks in order to manage Blood Products in the Future Example Monitoring of Blood Products in Hospitals Wireless sensor nodes monitor environmental conditions, determine their own position, create events and communicate with users Decentralized architecture with smart things acting on the user s behalf as agents Basic and generic services for identification, locating, sensing, communication on the node Application software modules can be downloaded onto the node via the internet ( business logic ) Nodes can gather context specific information from the infrastructure (gateways, anchor nodes etc.) Special middleware features are needed d which h are not yet defined by the EPC architecture 7

18 Logistics Research Organizations develop an autonomous smart Container for global Transport Example Realtime T&T with Aletheia and SemProM Smart containers monitor cargo (WSN), determine position (GPS), create events and communicate Highly decentralized and semantic architecture: WSN communication based on proprietary protocols Service oriented middleware on the nodes Web Services based on OGC offered by the container Semantic product memory on smart things Direct link between smart phone and container User integration via internet Today service providers like Agheera handle data and realize link between smart container and user The Future: Energy autonomous containers organizing themselves over their own web page? 8

19 Smart Metering becomes more Important due to Energy and Sustainability Discussions Example Smart Metering Focus of smart metering is on measurement, storage and communication of consumption data Meters are made smart using wireless sensor nodes which are embedded into the meter itself Dynamic system architecture: Multi hopping communication between measuring nodes and gateway into IT backend Central anchor node in the building for collection and fusion of raw data Mobile gateways installed to a measurement vehicle moving through streets No information service provider needed in order to set up the system 9

20 Development of a Reference Architecture for the Internet of Things needs further Research Conclusions IoT could be understood as the continuum of smart object based user- oriented solutions which h are incorporating internet technologies Depending on the basic technology used the solution architectures are different and sometimes unique Special features: Established application specific numbering schemes (e.g. aviation) Decentralization of application systems ( inverted systems ) Things talking to things ( multi hopping ) Dynamic and temporary architectures ( moving nodes ) EPC architecture is one very important one amongst a lot of other architectures representing the Internet of things Generic reference architecture does not exist and has to be developed combining bottom up and top down approaches 20

21 IoT Components and Challenges Components Challenges Status. RFID 2. ID numbers 3. Data capture and download Variety of autoid technologies Variety of numbering schemes Bi-directional communication with sensors, actuators, smart objects Available Available Under research 4. Point-to-point communication Any-to-any communication also based in the EPCIS/EDI style on service providers as middlemen??? 5. Structured data like numbering formats 6. Traditional IT systems Unstructured data from object memories based on ontology (representation of knowledge) Cross-enterprise workflow systems Under research Under research 7. Performance Available? 8. IoT discussion groups Needing additional experts for the mentioned topics?????? 2