research agenda
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
379
On Slideshare
379
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
3
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • Another category in the system is the infrastructure component, which defines what routing mechanism to use: Chord, CAN, etc. What are Groove and Magi? Groove: P2P system for office collaboration. Not clear how the user is detected, perhaps statically added by peers. Every peer in the group sees the same user space. Synchronized across all peers. All communications are signed. Proprietary. Magi: goal was to make it standards based such as HTTP, XML, WebDAV to provide document sharing and communication mechanism on the Internet. It uses dynamic DNS to register the Magi nodes/instances. All communications are signed.

Transcript

  • 1. A Creative Environment for Mobile Knowledge Workers Anwitaman Datta (PI, NTU Singapore) Adam Wierzbicki (PI, PJIIT Poland) Sun Chengzheng (Co-PI, NTU Singapore) m T eam
  • 2. Collaborative Innovation Networks
    • Knowledge economy – the new reality
      • also called “ Collaborative Innovation Networks” – COINS
        • typically these are self-organizing, open systems
        • source: Peter Gloor (MIT Sloan), Competitive Advantage through Collaborative Innovation Networks, Oxford University Press, 2006; www.swarmcreativity.net
    • Examples of COINS:
        • Linux developers
        • Development of WWW in CERN
        • Wikipedia
        • Really, most innovative projects today – including business
  • 3. Types of COIN members
    • Creators
      • the core of the COIN
      • need to be: creative, collaborative, fair
      • example: Linux Creators
    • Collaborators
      • share common knowledge and experience
      • work together to realize, improve, test new ideas
      • example: Linux Maintainers
    • Communicators (Interested users)
      • last tier of the COIN
      • information seekers (readers)
      • communicate new ideas outside
      • example: Linux Users
  • 4. Properties of COINS
    • Swarm creativity
      • creativity seen as an emergent property of an open system
    • Social network
      • essential for finding required collaborators
    • Sharing and frequent communication
      • information is freely shared among trusted, cooperating persons
    • Virtual trust through ethical code
      • Trust is established through following an ethical code requiring recognition of other’s input, meritocracy
  • 5. mTeam agenda
    • E nabling the creation of applications that would use social networks and mobility to find new collaboration opportunities and tools to support collaboration
    • In other words: enable building a COIN in a nomadic environment, supporting mobility
      • a heterogenous environment: fixed/mobile
        • Supporting nomadic teams
      • needs:
        • social network
        • environment for sharing
        • trust, access control, security (in a decentralized setting)
        • resource discovery and communication primitives
  • 6. mTeam goals
    • 3D social network:
      • expresses tacit knowledge about environment of a user ( “ mental map”)
      • includes: familiarity, skills/experience, trust /reputation
    • Collaboration tools:
      • a middleware for typical collaboration activities/functions
    • Handling heterogenous mobile environment and the inherent distributed/decentralized setting using a P2P information systems infrastructure
  • 7. mTeam deliverables
    • TeamCreator
      • uses the social network to recommend and buld a team to solve a problem
        • build a team from a COIN
        • form a new COIN
        • restructure a team
        • negotiate rules of engagement in the team (who does what, when, etc.)
    • TeamEnvironment
      • uses collaboration middleware to enable a team to work on shared information
        • includes a distributed versioning system
        • gives users rich context awareness
        • allows co llaborator s to communicate
        • gathers social information required to build social network
  • 8. mTeam architecture (tentative) Social information TOP BOTTOM MIDDLE TEAM CREATOR TEAM ENVIRONMENT 3D SOCIAL NETWORK COLLABORATION MIDDLEWARE P2P Overlay Network Security Reliability Trust Management Network Management Publish-subscribe P2P-SIP Routing/Multicast
  • 9. Collaboration middleware functions
    • Session management
    • Conference management
    • Group management
    • Data synchronization
    • Data sharing
    • Presence
    • Workspace awareness
    • Event management
    • Access control
    • Trust management
  • 10. P2P information system
    • Share the resources of individual peers
      • CPU, disk, bandwidth, information, …
    C C C C C S P P P P P Computer systems Centralized Distributed Client-server Peer-to-peer Flat Hierarchical Pure Hybrid mainframes workstations DNS mount RPC HTTP Gnutella Chord Napster Groove Kazaa File sharing Communication and collaboration Distributed computing [email_address] [email_address] Napster Gnutella Kazaa Freenet Overnet Magi Groove Skype
  • 11. Basic P2P layer functions
    • Routing and information search
      • it can be constrained by other requirements, such as trust
    • Publish-subscribe
      • subscribe to a topic, publish, notify
      • in ad-hoc environments, needs to be delay-tolerant
    • Multicast
      • special case of publish-subscribe
    • etc …
  • 12. Research issues The project will investigate the full-spectrum of research topics and technologies to enable nomadic collaboration or collaboration on the go, including algorithmic foundations and basic research on Networked Distributed Systems which will support upper layer functionalities and ubiquity independent of device and location, Social Networking to facilitate new collaboration opportunities and finally the Collaboration Tools themselves to carry out the tasks and manage such collaborations.
  • 13. Research issues
    • Privacy issues (beyond the scope of mTeam’s requirements) as well as some common security issues
      • Informal collaboration between NTU Singapore & Deutsche Telekom Laboratories (Berlin)
  • 14. Research issues
  • 15. Research issues
  • 16. Technical issues: Open standards and open sources …
    • Whether and how much to use SIP ?
    • How standard will interfaces like P2PP be ?
    • Open source Android SDK or some other environments for mobile devices ?
      • Politics of hardware/cellular service providers, etc.
    • UMPCs
  • 17. Proof of concept: Driver Applications
    • Not part of the original deliverables …
      • An collaborative editing application for research papers, capable of sharing and reviewing academic literature and news, as well as finding relevant collaboration opportunities
        • Ongoing
      • An application geared specifically to facilitate collaboration among environment scientists
        • Tentative (pending a Swiss/Singapore joint project on cyber-infrastructure for environment monitoring and modeling )
  • 18. Status
    • Research work
      • Ongoing literature and technology survey on various themes
        • Tutorial on “SIP, IMS and P2P-SIP” at IFIP Networking 2008
        • Book chapter (proposal accepted): Vertically Integrated Collaboration Middleware in Mobile P2P Environments
      • Groundwork for first driver application well in progress
      • Study of dynamics in open collaboration systems (Wikipedia)
    • Hiring
      • Poland:
        • One Ph.D. student and one research assistant hired
      • Singapore
        • Hiring is ongoing
        • One PhD student is informally working on related security topics, as will some FYP students from next semester
    • Project webpage: http://mteam.pjwstk.edu.pl