Method and system for providing a common collaboration framework accessible from within multiple applications

[0001] 1. Field of the Invention

[0002] The present invention generally relates to collaboration between network users and more particularly to an improved system and methodology that allows network users to seamlessly collaborate with each other using multiple unrelated applications.

[0003] 2. Description of the Related Art

[0004] Collaboration is the process of interaction amongst one or more users. Collaboration technologies allow users to collaborate with each other. User collaboration technologies have existed for some time in various forms such as telephone, fax, e-mail, bulletin boards, etc. Today, many enterprise portals, web sites, and also software applications provide their users with advanced collaboration capabilities such as online presence awareness (aka: buddy lists) of other users, instant messaging between users, discussion threads, and team rooms.

[0005] The invention provides a system adapted to enable contextual collaboration within a computer network. In the invention, a collaboration manager supports manipulation of collaboration spaces. The collaboration spaces contain one or more collaboration elements that have potentially different collaboration modalities. The context manager maintains resources and resource interrelationships within contexts. The resources can include collaboration elements, processes, tasks, business objects, users, and/or roles. A view generator selects a set of the resources to be displayed to a user of the computer network. The invention also may include an interface adapted to allow applications to specify commands to manipulate collaboration spaces, commands to maintain resources and resource interrelationships within contexts, and queries for context-sensitive views.

[0006] In the invention, commands to manipulate collaboration spaces include managing lifecycles of the collaboration spaces, maintaining membership lists, user profiles, and role associations in the collaboration spaces. The invention adds and removes the collaboration elements, and performs modality-specific operations on the collaboration elements. The commands to maintain resources and resource interrelationships may include: creating, deleting, opening, and closing of the contexts. The invention may add resources and associations between the resources in the contexts, and then, may remove the resources and the associations from the contexts. The queries for context-sensitive views may include retrieving resources related to a given context, retrieving resources related to a given resource within a context, and retrieving resources related to a given resource across contexts.

[0007] The collaboration manager may store information on collaboration spaces, and may be coupled to adapters for plugging in external collaboration capabilities. The adapters each implement a standardized and modality-specific interface. The context manager may describe associated resources and resource interrelationships. The view generator may specify policies for view generation.

[0008] The invention provides collaboration between different applications used by multiple users in a computerized network. At least one collaboration space supports different modes of collaboration, wherein the users collaborate through the different applications using the different modes of collaboration maintained in the collaboration space. The application program interfaces connect the collaboration space to the applications, thereby making collaboration content available to all the applications. All the collaboration content is transparently accessible by the users natively from within each application.

[0009] The contextual view generator may select a limited set of resources maintained within the collaboration space to be displayed to a user of the computerized network based on user needs. The collaboration manager may maintain the collaboration space. The collaboration manager also preferably creates, deletes, archives, searches, and queries the collaboration spaces. The collaboration manager may interact with collaboration technology servers. The application program interfaces may create instances of collaborative interaction within the collaboration space.

[0010] The invention also includes a method for enabling contextual collaboration within a computer network. The method creates collaboration spaces containing one or more collaboration elements of potentially different collaboration modalities. The method maintains resources and resource interrelationships within contexts. The resources include collaboration elements, processes, tasks, business objects, users, and/or roles. The method selects a set of the resources to be displayed to a user.

[0011] The invention further provides a service for enabling contextual collaboration within a computer network. The service creates collaboration spaces containing one or more collaboration elements of potentially different collaboration modalities, maintains resources and resource interrelationships within contexts, the resources including at least one of collaboration elements, processes, tasks, business objects, users, and roles, and selects a set of the resources to be displayed to a user.

[0012] The service may also manages lifecycles of the collaboration spaces, maintain membership lists, user profiles, and role associations in the collaboration spaces, add and removes the collaboration elements, and perform modality-specific operations on the collaboration elements. If the service maintains the membership lists, the service creates, deletes, opens, and closes the contexts; adds resources and associations between the resources in the contexts; and removes the resources and the associations from the contexts. If the service selects a set of resources to be displayed, the service retrieves resources related to a given context, retrieves resources related to a given resource within a context, and retrieves resources related to a given resource across contexts.

[0013] The service may also store information on collaboration spaces, redirect operations on the collaboration elements to external collaboration capabilities, use a context model to describe resource associations and resource interrelationships, and maintain a set of view rules adapted to specify policies for view generation.

[0014] These, and other, aspects and objects of the present invention will be better appreciated and understood when considered in conjunction with the following description and the accompanying drawings. It should be understood, however, that the following description, while indicating preferred embodiments of the present invention and numerous specific details thereof, is given by way of illustration and not of limitation. Many changes and modifications may be made within the scope of the present invention without departing from the spirit thereof, and the invention includes all such modifications.

[0021] The present invention and the various features and advantageous details thereof are explained more fully with reference to the nonlimiting embodiments that are illustrated in the drawings and detailed in the following description. It should be noted that the features illustrated in the drawings are not necessarily drawn to scale. Descriptions of well-known components and processing techniques are omitted so as to not unnecessarily obscure the present invention in detail.

[0022] In most cases, collaboration capabilities can be considered to be general and not specific to any business context. The invention defines contextual collaboration as the capability for multiple role players to interact with each other within a specific context. Contextual collaboration differs from general-purpose collaboration in that it can be initiated within a specific context such as a software application, business process, business object, or some business artifact and thereby allowing only a relevant set of participants within a larger universe of users to collaborate. Additionally, for contextual collaboration to be most effective, the user should be able to access the collaboration technology from within the user's environment, such as a software application. For example, a product designer should be able to collaborate with others from within the familiar user interface of the design application software.

[0023] The problem addressed by this invention is that the contextual collaboration data accessible natively from within one application is not carried over for access from within the next application. One way to get around this problem is to utilize a separate collaboration application that is outside of the other applications and that has its own user interface for access. However, with such a separate collaboration application, the user is forced to leave the application environment to access the collaboration application user interface. To illustrate this problem, consider the new product design process, which uses multiple applications for various tasks. Many of these applications provide a contextual collaboration environment to their users to interact with other process participants such as designers, product manager, parts procurement manager, etc. However, as the user moves from using the product design application to the parts catalog management application, all collaborative interaction data associated with the design decision-making would no longer be available to the user within the parts catalog management software.

[0024] As shown in FIG. 1, the invention includes a system and methodology that addresses this problem by creating a collaboration infrastructure 5 that provides collaboration capability to any business applications 20. This infrastructure makes collaboration spaces “CollabSpaces” 10 available across multiple applications 20 that can be accessed from within the application's native user interface. Additionally, the infrastructure also has features to address the issues of organizing and managing multiple such collaboration spaces 10.

[0025] A CollabSpace 10 represents an aggregation of various collaboration modality instances (different modes of collaboration) associated with a business context. The collaboration modality refers to a distinct collaboration capability provided by a specific technology such as e-meeting, discussion threads, instant messaging chat transcripts, online presence awareness (buddy lists), annotations, team rooms, etc. Additionally, the business artifact refers to the interrelated aspects of a business process within which a collaboration may occur. A CollabSpace 10 can be requested by any business application 20 and once created it is available to other authorized business applications 20.

[0026] As shown in FIG. 2, the collaboration infrastructure 5 includes the following components: a collaboration manager “CollabManager” 21; Context Manager 72; and View Generator 42. The CollabManager 21 handles requests for CollabSpaces 10 from various business applications 20 and manages the lifecycle functions of these CollabSpaces 10 including, creation, deletion, and archival. It also provides search and query function on its set of CollabSpaces 10 to locate CollabSpaces 10 by various criteria as well as find the attribute name and value information for each CollabSpace 10.

[0027] The CollabManager 21 interacts with various Collaboration technology servers 33 such as Lotus QuickPlace® server (for team rooms), Lotus Sametime® server (for online awareness and instant messaging) both available from International Business Machines Corp., Armonk, N.Y., USA , and others through adapters 32. The adapters 32 implement standard interfaces for creating an instance of collaborative interaction (such as a team room, buddy list, threaded discussion) as well as other management functions. In case the adapters 32 are implemented as web services, the adapter interfaces can be represented in Web Services Definition Language (WSDL).

[0028] The CollabManager 21 itself provides interfaces for lifecycle management functions, search and query functions, and update functions for CollabSpaces 10. The various business applications 20 interact with the CollabManager 21 through this interface. Some representative function calls are as follows:

[0029] Lifecycle Management commands:

• • [0030] CreateCollabSpace (Name, Description, ContextID)
  • [0031] DeleteCollabSpace (CollabSpaceID)
  • [0032] ModifyMembersOfACLGroup (CollabSpaceID, ACLGroup, MemberList)

[0033] Search and Query functions:

• • [0034] GetCollabSpaceDetails (CollabSpaceID)
  • [0035] ListCollabSpacesByUser (UserDN)
  • [0036] ListCollabSpacesByContextID (ContextID)

[0037] The CollabManager 21 stores the details of the collaboration spaces 10 within a CollabSpace Directory 31. Such a directory 31 can be implemented using a relational database or by using LDAP (lightweight directory access protocol) services.

[0038] A CollabSpace 10 can contain pointers to several collaboration modalities and also contain various attributes associated with these modalities. However, a user may not need access to all this information for the task at hand. For example, the universe of people participating within a particular contract negotiation process may contain several role players including contract initiator (sales person), counter party (customer), contract administrator, department manager (sales manager), financial analyst, legal expert, etc. However, the buddy list when displayed to the customer may contain references only to the salesperson and the sales manager and no references to the other role players (i.e., financial analyst, contract administrator, legal expert). On the other hand, the salesperson initiating the contract will see the entire set of participants in order to initiate any collaborative interaction with them in the context of the contract being negotiated.

[0039] Therefore, the invention provides a View Generator 42 within the middleware infrastructure 5. The View Generator 42 receives requests from the business applications 20 being collaboration enabled. The output of the View Generator 42 is a set of collaboration modalities that should be included in the presentation to the user of the business application 20. The View Generator 42 also returns the context-specific collaboration content to be displayed to a user based on specific business rules.

[0040] The View Generator 42 accesses a library of context rules 41 and executes those that are relevant to the current business context. The View Generator 42 depends on querying the Context Manager 72 and the CollabManager 21 to access the business environment details and collaboration space details respectively. The context rules 41 can be modeled using industry standard process ontologies or proprietary schemes and implemented using XML technology.

[0041] FIG. 3 outlines the sequence of activities that takes place between various sub-systems during a request for a collaboration space by a business application 20, and FIG. 4 shows the request for context specific collaboration content to be presented to the end user via an application user interface. More specifically, in item 501, a request from the requesting business application 20 is made to the collaboration manager 21. Then, in item 502, the collaboration manager verifies the existence of the collaboration space 10 from the collaboration space directory 31. Then, the collaboration manager 21 issues a collaboration space URL 503 if item 502 indicates that one previously exists. Alternatively, the processing shown in items 504-512 is undertaken. In item 504, the collaboration manager constructs a new model for the collaboration space if one does not exist for the context specified. In item 505, the collaboration manager 21 creates a collaboration element request to the collaboration application adapter 32. In item 506, the collaboration application adapter 32 translates the collaboration model to application parameters. In item 507, the collaboration application adapter 32 creates the collaboration elements using the collaboration technology 33, which in turn returns the collaboration element URL 508. The URL is forwarded back to the collaboration manager 21 in item 509. In item 510, the collaboration manager updates the collaboration space directory, which returns acknowledgment 511. Then, item 512 represents the collaboration manager 21 returning the newly created collaboration space URL to the requesting business application 20.

[0042] In FIG. 4, the process of determining a contextual view of the collaboration space begins in item 61 where the business application 20 produces a request to get a contextual view. In item 62, the view generator 42 sends a query to the view rules library 41, which in turn returns the relevant rules 63. A query is also sent from the contextual view generator 42 to the context manager 72 in item 64. The context manager 72 returns details of the current business context in item 65. The view generator 42 then sends a query 66 to the collaboration manager 21 which returns the elements of the CollabSpace in item 67. With such information, the view generator 42 executes the rule in item 68 and provides the viewing details to the business application 20 in item 69.

[0043] As illustrated in FIG. 5, the Context Manager 72 maintains a Context Store 73 that represents an aggregation of the contextual relations that exists between the different resources 77. These relations can be modeled using a non-cyclical graph or a tree 76. For all intended purposes, the Context Store 73 does not have to deal with the semantic nature of the relation, nor does it have to deal with how and where the resource is physically stored, because the context store 73 simply maintains the structure of the relationship and provides linkage between the different resources.

[0044] The contextual information that is encoded by each node consists of the primary resource that a context deals with, and all the resources that are directly related to primary resource. The primary resource is encoded using a Resource Descriptor block 75 that allows the system to uniquely identify the resource. URI is a well-known mechanism in the art that can be used in lieu of, or part of the Resource Descriptor block. It might be however desired to store additional information such as a CLASS attribute (i.e., person, process, document, discussion, etc.) or MIME type (although most standard protocols can return this information based on its URI) or type of relation to parent node (if so desired to be used in the application semantic), etc. An application 20 can access a specific context by referring to the corresponding node unique identifier, which is generated by the Context Manager 72. Alternatively the application can specify a path, or part of a path, that identifies the resources that the application deals with to locate the corresponding context. A fully qualified path specifies all the nodes that are visited to reach the desire context. For example, the path “/project:STB/design document: physical layout v1/discussion:heat dissipation” refers to the context that is part of the discussion about heat dissipation in version 1 of the design document of the Set Top Box project. A partially qualified path allows for ambiguity and may identify more than one context. For example, “/project:contract negotiation/ . . . /discussion: terms and conditions” refers to all the contexts for all the discussions that are in the database that relate to the terms and conditions of any contract negotiation project. The Context Manager 72 provides the necessary API for creating, retrieving and/or modifying a context requested by the business application 20.

[0045] The tree organization 76 of the Context Store 73 allows the system to implement a hierarchical view of the contextual relationship and navigate the contextual space from the most general context (root node) to the more specific contexts (leaf nodes). It is also possible to provide direct access to a specific node of the tree. An index table or other optimization techniques that are well known in the art is used to accomplish this.

[0046] Resources that are already defined as part of the parent context do not have to be repeated for a child context and can be easily derived by inheritance. Furthermore, the hierarchical organization of the Context Store 73 allows the system to use the context encoded by a parent node to access all the resources that are encoded by a child or grandchild nodes. For example, if B is a child node of node A, than all the contextual information that is encoded by node B should also be accessible to node A. In this case, the resource that is attached to node B is said to be directly related to the resource attached to node A, while the resources that are attached to a child node of B are said to be indirectly related to the resource attached to node A but are still accessible from the context encoded by child node B.

[0047] The above drawings also illustrate a service for enabling contextual collaboration within a computer network. The service creates collaboration spaces containing one or more collaboration elements of potentially different collaboration modalities, maintains resources and resource interrelationships within contexts, the resources including at least one of collaboration elements, processes, tasks, business objects, users, and roles, and selects a set of the resources to be displayed to a user.

[0048] The service also manages lifecycles of the collaboration spaces, maintains membership lists, user profiles, and role associations in the collaboration spaces, adds and removes the collaboration elements, and performs modality-specific operations on the collaboration elements. When the service maintains the membership lists, the service creates, deletes, opens, and closes the contexts; adds resources and associations between the resources in the contexts; and removes the resources and the associations from the contexts. When the service selects a set of resources to be displayed, the service retrieves resources related to a given context, retrieves resources related to a given resource within a context, and retrieves resources related to a given resource across contexts.

[0049] The service also stores information on collaboration spaces, redirects operations on the collaboration elements to external collaboration capabilities, uses a context model to describe resource associations and resource interrelationships, and maintains a set of view rules adapted to specify policies for view generation.

[0050] Thus, as shown above, the invention provides a system or a service adapted to enable contextual collaboration within a computer network. In the invention, a collaboration manager supports manipulation of collaboration spaces. The collaboration spaces contain one or more collaboration elements that have potentially different collaboration modalities. The context manager is adapted to maintain resources and resource interrelationships within contexts. The resources can include collaboration elements, processes, tasks, business objects, users, and/or roles. A view generator selects a set of the resources to be displayed to a user of the computer network. The invention also includes an interface adapted to allow applications to specify commands to manipulate collaboration spaces, commands to maintain resources and resource interrelationships within contexts, and queries for context-sensitive views.

[0051] In the invention, commands to manipulate collaboration spaces include managing lifecycles of the collaboration spaces, maintaining membership lists, user profiles, and role associations in the collaboration spaces. The invention adds and removes the collaboration elements, and performs modality-specific operations on the collaboration elements. The commands to maintain resources and resource interrelationships include: creating, deleting, opening, and closing of the contexts. The invention adds resources and associations between the resources in the contexts, and then, removes the resources and the associations from the contexts. The queries for context-sensitive views include retrieving resources related to a given context, retrieving resources related to a given resource within a context, and retrieving resources related to a given resource across contexts.

[0052] The collaboration manager stores information on collaboration spaces. The collaboration manager plugs in external collaboration capabilities. The adapters each implement a standardized and modality-specific interface. The context manager describes associated resources and resource interrelationships. The view generator specifies policies for view generation.

[0053] The invention provides collaboration between different applications used by multiple users in a computerized network. At least one collaboration space supports different modes of collaboration, wherein the users collaborate through the different applications using the different modes of collaboration maintained in the collaboration space. The application program interfaces connect the collaboration space to the applications, thereby making collaboration content available to all the applications. All the collaboration content is transparently accessible by the users natively from within each application.

[0054] The contextual view generator selects a limited set of resources maintained within the collaboration space to be displayed to a user of the computerized network based on user needs. The collaboration manager maintains the collaboration space. The collaboration manager also creates, deletes, archives, searches, and queries the collaboration spaces. The collaboration manager interacts with collaboration technology servers. The application program interfaces create instances of collaborative interaction within the collaboration space.

[0055] The invention also includes a method for enabling contextual collaboration within a computer network. The network creates collaboration spaces containing one or more collaboration elements of potentially different collaboration modalities. The method maintains resources and resource interrelationships within contexts. The resources include collaboration elements, processes, tasks, business objects, users, and/or roles. The method selects a set of the resources to be displayed to a user.

[0056] This invention can be used to enable capability for collaborative user interaction within applications in all industrial sectors. It can be offered as collaboration middleware to software vendors for building inter-operable collaboration capability into their applications. The invention can also be offered by a service provider as a service for enabling contextual collaboration within a computer network. The collaboration is an integral part of a familiar business application, so it is easy to use, and a common set of collaboration technologies that are used across multiple applications is easier to learn. Further, software application vendors do not have to develop their own collaboration software and the cross-application collaboration context improves marketability of Independent Software Vendor (ISV) software that is built using this infrastructure. Infrastructure based on adapters for various collaboration technologies allows plug-n-play of different collaboration technologies and improves flexibility. The common collaboration context across several applications, business processes, and business objects is appealing to customer specific embodiments.

[0057] The examples used herein are intended merely to facilitate an understanding of ways in which the invention may be practiced and to further enable those of skill in the art to practice the invention. Accordingly, the examples should not be construed as limiting the scope of the invention.

[0058] While the invention has been described in terms of preferred embodiments, those skilled in the art will recognize that the invention can be practiced with modification within the spirit and scope of the appended claims.