Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Design Principles For Smart Space Management


Published on

Design Principles For Smart Space Management

Published in: Business
  • Be the first to comment

  • Be the first to like this

Design Principles For Smart Space Management

  1. 1. Introduction Design principles recognise many areas • Design Principles for Smart Space Management – Provision of service logic – Business to network translation – Impacts and dimensions of engineering – Service life cycle – A conceptual model Dr. Sven van der Meer et. al. – Components – Service Centric Environment Well will look at the areas and discuss their influence • to Smart Space Management December 2003 2 Where do we go to? What are our Research Challenges? IP Technology Software Services & TCP/IP SGML The Mobile Internet Distributed Systems Telecommunications Usage Patterns & IP Technology & Software Service & Management Hypercard smtp, ftp, telnet Ambient Intelligence The Mobile Internet Distributed Systems Internet gopher, WAIS, http HTML munication Infrast earing Com ructure D isapp DiffServ, IntServ XML, XML Schema Ipv6 SOAP UDDI, WSDL SIP Network Web IN Application Enterprise Element .NET EJB CORBA COM RPC Services Services Services Services Services CPL Business Usage GIF P2P Models Patterns Telecommunication Software Applications Software DECT Ipv6 IPSec PHP CC/PP Services CDN RSVP Mobile IP DEN COPS Portals SNMP NGOSS Appl. Appl. Appl. Program Batch SMTP Echolon DPE TINA CMIP Parlay/OSA SMIng SLA WBEM RMI Services Suite GUI run Bluetooth WAP BER ASN.1 IPTelSAP IN N - G SSL RSA GSM Policy SOAP XSLT MIB OCR Powerline UMTS Mobile- WiFi, 3G/4G Pervasive- Device/PDA MOF Jini VHE ATM EPOC IrDA X.200 UDDI DES GDMO Communication Platforms HTTP Solaris NRIM CIM Mobile- GSM Mobile- Laptop WSI GPRS Environments IVR XML ASR Linux DIM FTP CORBA H.323 Mobile Agents XDSL PC / Workstation Fixed- B ISDN - 802.x ISDN AN DCOM MGCP KQML X.700 X.400 ASP UPnP IN ACL Java SNMP Telecommunications Usage Patterns Mini IDL TTS ISDN TMN TINA X.500 EIB Management Ambient Intelligence Basic Technologies 3GB Mainframe PSTN December 2003 December 2003 3 4
  2. 2. Provision of Service Logic Business to Network Translation End User End User Customer 2 Network Today Today Network Provider-A Provider-C service logic is outside the switches, service logic is outside the switches, • • but with limited flexibility but with limited flexibility Customer 1 Customer 3 centralized: Intelligent Network at the end systems: Internet • • Service Broker Network Provider-B Service Provider A Service Provider B 2 2 5 5 8 8 7 7 P P 0 0 Telecommunication Today Tomorrow Services service logic is outside the switches, • service dynamically activated • but with limited flexibility anywhere distributed: OSA/DPE Regulatory Body • centralized, distributed, at end • systems, at switches, at special nodes Network Provider c Network Provider a Network Provider b Access Provider Subscriber End User 2 2 5 5 8 8 7 7 P P 0 0 December 2003 December 2003 5 6 Complete Service Lifecycle Impacts and Dimensions of Software Engineering Dimensions Different independent actors must co- Leisure & • Supporting eLogistics Ontology Entertainment operate Services Functional Areas Financial – support of autonomy & co- Services operation Networks Applications & Service Fault Business eHealth IN Engineering Large amount of involved components • Configuration Models VPN – scalability of services Accounting Quality Corporate Management Life Cycle Performance MAN Methodology Huge variety of employed systems and eGovernment eScience • Security Changes components Service WAN Operation – vendor independence => standard LAN Installation Life Cycle Planning Quality of based service development Filtering & Architecture Service Adaptivity Network Management Data Services Tools Systems / components will change • System Management Speech frequently Application Management Video Basic Service-aware – reusability of software concepts Technologies Framework Multimedia Service Management AAA – support of the whole lifecycle of services (design, installation, etc.) Enterprise Management Performance Platform Interoperability Communication Services Ubiquitous Management Grid Access Computing Classes of Management December 2003 December 2003 7 8
  3. 3. Conceptual Model Components Home Fantasy WWW Control Soccer Editing Application Services Applications & Business Meta Schema WWW Messaging, Specification, Instant Models WWW API Alert Messaging Client Client Monitoring Visualisation, Database Core Model Configuration Core Services Console Service Repository Naming, Directory, Monitoring, DomainB Engineering API DomainC Lifecycle, Config, Notification Performance DomainA Formal Monitoring Notation Communication Services Administration Service aware Compiler Control Services Framework Tools Mappings Protocol Services API Tools Protocols and Formats UA F&A AAA AAA Basic Development Execution Environment Deployment Technologies UA QoS GC UA PM December 2003 December 2003 9 10 Service Characteristics Service-centric Environment Smart Services will Two main perspectives • – Business to network translation Learn from previous events and adapt behaviour – Service modelling • Be aware of other services, applications and resources Abstraction from the technical environment, network • • – Service-centric network Advertise functionality to other services – End-environment to end-environment connectivity • – Complexity becomes transparent Interact with other services, applications and resources • Covering the complete life cycle of services • Allow service composition to provide value-added services – Business models, interoperability, product line management, • domain engineering Provide a common terminology • December 2003 December 2003 11 12
  4. 4. Conclusion Converged networks and Smart Spaces challenge • established design principles Business to network translation is one key issue • Service-centric approach might dominate software • engineering User-centric approach will define requirements • December 2003 13