Your SlideShare is downloading. ×
Dr. Rahul Banerjee Computer Science Group
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.

Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Dr. Rahul Banerjee Computer Science Group


Published on

  • Be the first to comment

  • Be the first to like this

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide
  • 07/13/10 For copyrights and credits, please see the Acknowledgement page! NOT for redistribution. Meant for academic purpose only.
  • Transcript

    • 1. Dr. Rahul Banerjee Computer Science Group Birla Institute of Technology & Science, Pilani, India Email: [email_address] , [email_address] Fundamentals of Pervasive Computing : Communication & Connectivity Aspects Lecture-2 August-6, 2007 (c) Dr. Rahul Banerjee, BITS-Pilani, India
    • 2. Interaction Points
      • Introduction to Communication & Connectivity Needs
      • Select Fundamentals specific to:
        • Pervasive Communication Architecture
        • Device Connectivity for Pervasive Computing
      • Connectivity & Service Discovery in Pervasive Computing
        • Importance of Self-configuration
        • Protocols and Mechanisms For Self-Configuration
      • Importance of Self-Healing
      • Summary
      (c) Dr. Rahul Banerjee, BITS-Pilani, India
    • 3.
      • The pervasive computing system needs at least two basic elements to be pervading everywhere they are required to pervade:
        • Computing elements to take care of computational needs; and,
        • Communication elements to interconnect these computing elements either through wires or wirelessly (with / without mobility) .
      • From the end user’s perspective and in many a practical situations, the wireless communication based mobile computing is becoming increasingly important .
      • From the back-end systems’ viewpoint, however, due to its sheer traffic volume, low error rates, better noise immunity and low cost, the wireline communication based computing still remains an attractive option.
      • Therefore, hybrid architectures will possibly continue to exist even though end users may not be even aware of it.
      (c) Rahul Banerjee, BITS, Pilani, India
    • 4.
      • First Generation Global Mobile Radio standard : 1G
        • Only voice, No data
      • Second Generation Global Mobile Radio standard : 2G
        • GSM: 9.6 Kbps <circuit switched voice / data>
        • Enhanced Second Generation Global Mobile Radio standard : 2.5G
          • GSM-GPRS <combination of circuit and packet switched voice / data>
          • GPRS-136: <100Kbps <packet switched>
      • Third Generation Global Mobile Radio standard: 3G
        • CDMA2000, =< 2Mbps <packet switched voice / data>
      • Fourth Generation Global Mobile Radio standard : 4G (near future)
        • ? 20-40 Mbps <packet switched voice / data>
      (c) Rahul Banerjee, BITS, Pilani, India
    • 5.
      • What is 3G?
        • Stands for the Third Generation,
        • Used in the context of new wireless mobile communication systems / services,
        • Leverages the progress made in cellular technologies with the advances made in the Internet-based communication / services and the fixed wireline communication technologies,
        • Is a general-purpose communication network / service architecture,
        • Allows freedom to end users from being aware of location of request / provision of services,
        • Puts more emphasis on the services than on the underlying delivery technologies,
        • Aims to play a key role in aiding the On-Demand service paradigm.
        • Is not a single-technology architecture; instead allows a multi-technology solution.
      (c) Rahul Banerjee, BITS, Pilani, India
    • 6.
      • Summary:
        • Several generations
        • Gradual enhancements
          • Security
          • Speed
          • Discovery
        • Coexistence & transition
        • Transition form ‘ No IP ’ to IPv4 to IPv6
      (c) Rahul Banerjee, BITS, Pilani, India 2G GSM GSM / GPRS GSM/EGPRS/EDGE 3G UMTS / CDMA 2K /IMT 2K
    • 7. Any questions?
      • Let’s move to the next point of discussion!
    • 8. Self-Configuration & its Importance
      • In order too achieve the pervasive computing system design goals (simplicity, versatility and pleasurability) the appliances and the networks comprising of these appliance nodes must be able to:
          • automatically discover other
              • Devices,
              • Services and
              • Parameters
          • In addition, they should be able to carry out unattended negotiation amongst themselves if needed.
      • Systems that can self-configure help bridge the gap among early users and the normal consumers.
    • 9. Discovery Protocols & Mechanisms
      • Discovery is a term used to describe the protocols and mechanisms by which a network connected device or software service becomes aware of the network to which it is connected and discovers which network services are available.
      • Service discovery can be all pre-configured (as in DHCP, DNS and LDAP)
      • For a relatively static system with infrequent addition of new devices or software services, this may be a viable approach. For relatively static networks where central administration is needed or desirable, this sort of pre-configured service discovery may be appropriate.
      • Mobile devices can enter and leave a home network quite frequently.
      • Closed systems violate the axiom of versatility, as they are not amenable to easily adding new functionality. In these situations, it is difficult to rely on manual configuration of the network services without violating the axioms of simplicity, versatility and pleasurability.
      • Therefore, we need service discovery in the home, mobile, and similar environments to be self-configuring.
    • 10. Common Features of SDP
      • The discovery protocols discussed above share some common attributes, which could form the basis for a high degree of interoperability.
      • Let's examine a set of common characteristics of self-configuring service discovery protocols:
        • Client agent : The client agent is a software component that runs in a device and searches the network to find services needed by applications running in the device. Note that services themselves can be clients of other services.
        • Service agent : For devices that provide services to other devices, the service agent is a software component that advertises the services provided by the device. In the case where a service provider implementation does not require hardware, a service agent can be based entirely in software.
        • Registry : In order to provide efficiency and scalability, some of these protocols provide for a (perhaps optional) registry where information about available services is maintained. Typically a registry contains an entry for each service advertised by a service provider. The registry can be centralized or decentralized (distributed).
        • Registry update mechanism : This pertains to the protocols the service agents use to update their entries in a registry.
    • 11. Common Features of S D P …
      • Registry cleanup : This topic addresses how obsolete or incorrect information is purged from the registry.
      • Discovery mechanism : The discovery mechanism is that part of a service discovery protocol that specifies how a client locates the service discovery infrastructure such as a registry.
      • Client lookup mechanism : The client lookup mechanism defines how a client queries the registry (if there is one) to locate a service it needs, and how it locates the service in the absence of a registry.
      • Client access to service : This topic addresses how a client, once it has located the service that it needs, negotiates access to the service, including &quot;quality of service&quot; issues and security issues.
      • Client use of services : Once a client has located a service, and has successfully negotiated access to the service, it must determine (and perhaps acquire) the protocols to actually interact with the service (for instance: IPP, LPR, HTTP, FTP, Java RMI).
    • 12. Select Protocols at Different Levels with Service Discovery Features
      • UPnP
      • Salutation
      • SLP
      • JINI
      • HAVi
      • Bluetooth
      • IPv6
      (c) Dr. Rahul Banerjee, BITS-Pilani© Rahul Banerjee, BITS-Pilani, India, 2003-2005
    • 13. Salutation Service Discovery Architecture
      • Salutation
        • Salutation is an architecture for looking up, discovering, and accessing services and information.
        • The Salutation architecture defines abstractions for
          • devices,
          • applications ,
          • services;
          • a capabilities exchange protocol ;
          • a service request protocol;
          • &quot; personalities &quot; (standardized protocols for common services); and
          • APIs for information access and session management.
      • Its heritage has been (and most implementations to date have focused on) enabling access to office equipment (FAX, printers, scanners, and so on).
      • However, the architecture also supports other information appliances such as telephones and PDAs through definitions for telephony, scheduling, and address book.
      • Details on Salutation can be found at
    • 14. Service Location Protocol & JINI
      • SLP
        • Service Location Protocol (SLP)3 is a standard developed by a working group of the Internet Engineering Task Force (IETF).
        • SLP addresses the problem of self-configuring service discovery by applying existing Internet standards to the problem.
        • SLP is designed to be a lightweight, decentralized protocol with minimal administration requirements.
      • Jini
        • Sun Microsystems developed its Jini technology to address service discovery needs for networks of Java-enabled devices.
        • Jini addresses the axioms of simplicity and versatility directly.
        • Leveraging the Java platform, Jini uses very simple techniques to solve the hard problem of distributed service discovery.
        • Jini is described at
    • 15. Home Audio Video Interoperability & Bluetooth Schemes
      • HAVi
        • Home Audio/Video Interoperability (HAVi) is a consortium of consumer electronics companies organized to define
          • the interoperability standards among next generation network-connected &
          • digital home entertainment products.
        • HAVi has its own proprietary service discovery protocol.
        • HAVi is described at .
      • Bluetooth
        • Bluetooth is a a short-range wireless communication protocol.
        • As part of this effort, the Bluetooth Software Special Interest Group is defining several layers of a software stack - one of these layers is Service Discovery.
        • It is optimized for the highly dynamic nature of Bluetooth networks, and is a simple, efficient protocol that allows Bluetooth devices to discover services offered by or through other Bluetooth devices.
        • Details on Bluetooth can be found at
    • 16. Which one to dominate?
      • None of these discovery protocols is likely to dominate. Some of these protocols (SLP, Salutation) are deployed primarily within the enterprise or office environment, reducing the likelihood of penetrating the home networking market.
      • Other technologies like Jini, UPnP and Bluetooth were conceived for a more informal, casually connected environment, which could include networked vehicles and small offices as well as home networks. Each has its strengths, and none has a dominant position in the marketplace.
      • Consequently, good consumer networking solutions should be able to accommodate heterogeneity, both in terms of underlying connectivity, and in terms of the discovery infrastructure that is supported .
    • 17. Any questions?
      • Let’s move to the next point of discussion!
    • 18. Interfacing technologies
      • Navigation technologies
      • Haptic interfacing technologies
      • On-screen / Touch-panel technologies
      • Voice interfacing technologies
      • Video-interfacing technologies
      • Handwriting-based interfacing technologies
      • Hybrid interfacing technologies
      © Rahul Banerjee, BITS-Pilani, India, 2003-2006
    • 19. Any questions?
      • Let’s move to the next point of discussion!