Slide 1Slide 2Slide 3Slide 4Slide 5Slide 6Slide 7Slide 8Slide 9Slide 10Slide 11Slide 12Slide 13Slide 14Slide 15Slide 16Slide 17Slide 18Slide 19Slide 20Slide 21Slide 22Slide 23Slide 24Slide 25Slide 26Slide 27Slide 28Slide 29Slide 30Slide 31Slide 32Slide 33Slide 34Slide 35Slide 36Slide 37Slide 38Slide 39Slide 40Slide 41Slide 42Slide 43Slide 4419/1/1819/1/1811A Web Services Framework for Collaboration and VideoconferencingPTLIU Laboratory for Community GridsGeoffrey Fox, Wenjun WuAhmet Uyar, Hasan BulutIndiana University, Bloomington IN [email protected] 22 June 200319/1/1819/1/1822AbstractWe define such a common, interoperable framework called XGSP (XML based General Session Protocol) based on Web services technology for creating and controlling videoconferencesWe developed a common dynamic messaging environment (NaradaBrokering) for the collaboration applicationsBased on the web-services framework and NaradaBrokering messaging environment, we are developing Global Multimedia Collaboration System (Global-MMCS) Integrates various services including videoconference, instant messaging and streaming, and supports multiple videoconferencing technologies and heterogeneous collaboration environment.19/1/1819/1/1833Collaboration and Web ServicesCollaboration hasa) Mechanism to set up members (people, devices) of a “collaborative sessions”b) Shared generic tools such as text chat, white boards, audio-video conferencingc) Shared applications such as Web Pages, PowerPoint, Visualization, maps, (medical) instruments ….b) and c) are “just shared objects” where objects could be Web Services but rarely are at moment•We can port objects to Web Services and build a general approach for making Web services collaborativea) is a “Service” which is set up in many different ways (H323 SIP JXTA are standards supported by multiple implementations) – we should make it a WS19/1/1819/1/1844Shared Event CollaborationCollaboration involves sharing resources and synchronous collaboration involves coordinating a common view of a resource between multiple clientsAll collaboration is about sharing some sort of event•Audio/Video conferencing shares events specifying in compressed form audio or video•Shared display shares events corresponding to change in pixels of a frame buffer•Instant Messengers share updates to text message streams•Microsoft events for shared PowerPoint (file replicated between clients)Using Web services makes universal as exposes updates of all kinds as messagesGroup communication service is needed for the delivery of the update events•Using Event Messaging middleware makes messaging universal19/1/1819/1/1855Peer to Peer GridDatabaseDatabasePeersPeersPeer to Peer GridA democratic organizationUser FacingWeb Service InterfacesService FacingWeb Service InterfacesEvent/MessageBrokersEvent/MessageBrokersEvent/MessageBrokers19/1/1819/1/1866Solutions to Problems from current collaboration systemsNetworks were unreliable and firewalls are a problem•Not a lot of progress with QoS at network level•Some QoS problems are due to different collaboration streams interfering•Use application level QoS with highly robust managed messagingMany different standards H323, SIP, Access Grid, T120 …•Unify as single XML standard•Make the conference control services into Web ServicesVery hard to customize each application in “shared state event model”•Offer shared display•Convert Applications to Web ServicesInconvenient to customize user interfaces•Use portlet technology supporting desktop and PDA clients19/1/1819/1/1877Portals and Web ServicesWeb Services allow us to build a component model for resources.Each resource naturally has a user interface (which might be customized for user)Web Service <--> PortletNatural to use a component model for portal building displayed web page from collection of portlets•So can customize each portlet and customize which portlets you want19/1/1819/1/1888WSRP Structure of a PortletEach Web Service naturally has a user interface specified as “just another port” This gives each Web Service a Portlet view specified (in XML as always) by WSRP (Web services for Remote Portals)So component model for resources “automatically” gives a component model for user interfaces•When you build your application, you define portlet at same timeApplication orContent sourceWSDLWeb ServiceSRWPApplication as a WSGeneral Application Ports Interface with other Web ServicesUser Face ofWeb ServiceWSRP Ports define WS as a PortletPortalUser ProfileAggregateUI FragmentsClientWSRP isWeb Services for Remote Portals1st Meeting OASIS March 18 200219/1/1819/1/1899 XGSP Framework To integrate heterogeneous systems into one collaboration system, we need to reach the following goals: (1) Different kinds of application endpoints should join leave in the same collaboration session.(2) Different providers for multipoint A/V and data collaboration should be connected together to build unified A/V and data multipoint channels.(3) A common user interface should be present for all the collaboration participants using different A/V and data application endpoints.19/1/1819/1/181010XGSP Conference Control Framework19/1/1819/1/181111XGSP Conference Control Framework ComponentsUser session management •User session management supports user sign-in, user create/terminate/join/leave/invite-into XGSP sessions. Application Session Management•XGSP application session management provides the services to A/V and data application endpoints and communities, controlling multipoint A/V RTP and data channels. Floor Control •Floor control manages the access to shared collaboration resources.19/1/1819/1/181212XGSP Application Session ManagementXGSP signaling protocol for •H.323 signaling protocols (H.225, H.245) •SIP signaling protocol ( Invite, Bye Message )•Access Grid ( Unicast VIC & RAT ) Join XGSP Session, Leave XGSP Session, Invite into XGSP Session, Expel from XGSP SessionActivate the XGSP session•the XGSP session server will link all the “rooms” in the session together by connecting multipoint A/V and data channels from different communities to the XGSP A/V Media and Data Channel Services. Link/Disconnect XGSP SubSession19/1/1819/1/181313XGSP Floor ControlXGSP should provide: •Floor control primitives, including: request floor, release floor,