Conversation access rights management

FIELD: physics, computer engineering.

SUBSTANCE: invention relates to computer engineering. The method of managing conversation access rights comprises steps of: receiving a request for creating a conversation access rights based restriction for a communication session at a rights management server; providing a license to a requesting first client application; receiving another request from a second client application for the license, the second client application being invited to participate in the communication session with the first client application; providing the license to the second client application in response to confirming communication session access rights. The communication system implements said method and a machine-readable medium contains instructions for implementing the method.

EFFECT: safer communication session owing to verification of access rights of a client.

15 cl, 7 dwg

Prior art

Modern communication systems have a large number of capabilities, including the integration of different ways of communication (modalities) with different services. For example, instant messaging, voice/video calls, sharing of data/applications, electronic whiteboard, and other types of communication can be combined with the availability of information about subscribers. Such systems can provide subscribers with advanced features, such as commands for callers to different categories of status, alternative contacts, calendar information, and similar signs.

Many of these modern means of communication is multimodal, which means that in one session can be used several communication modes such as voice communication mode, the data transmission mode, transmission mode, video data and other similar modes to complement each other. All or part of the various communication modes used in the session, can operate in real-time. For example, if the group call with the use of electronic "whiteboard" voice and video calls can operate in real time while sharing data with the use of electronic boards can bytecodestream in real time or may be based on stored data. Another feature of modern systems is that the chat sessions can be saved and made available to partially or fully. For example, along with a conference record documents shared in a video conference can be saved in a way that provides the ability to search. This leads to the problem relating to user access rights to the records of the sessions multimodal communication.

The essence

This is a brief summary of the invention presents for the introduction of a selection of concepts in a simplified form, which will be described below in the detailed description. This presentation of the invention is not intended nor to directly identify key or essential features of the claimed invention or to aid in determining the scope of the claimed invention.

Embodiments of focused on ensuring rights in multimodal communication. Through the use of physical and/or software components of multimodal communication sessions may be partially or wholly stored based on the properties of the access rights that have been taken by default or specified by the user. Access to conserving the actual records of various modes of communication session, as well as related documents/data may be limited is icen on the basis of the assigned property rights.

These and other features and advantages will become apparent after reading the following detailed description and upon consideration of the attached drawings. It should be understood that both the foregoing General description and the following detailed description are illustrative and do not limit the claimed aspects.

Brief description of drawings

Figure 1 depicts a graphical representation illustrating an example unified communications, in which to control access rights to the conversation can be implemented options for implementation;

Figure 2 depicts a conceptual graphical representation illustrating an example of the basic system for managing access rights to the components of the communication session;

Figure 3 depicts a functional graphical representation illustrating the interaction between various components of the communication system in accordance with the variants of implementation;

Figure 4 depicts screen shots of illustrative user interfaces for managing access rights to the conversation in a communications application;

Figure 5 depicts a network environment that may be implemented in accordance with the variants of implementation;

6 depicts a block diagram illustrative of a computing operating environment, which can be implemented options ASU is estline; and

Fig.7 depicts the logical sequence of operations for managing access rights to the conversation in the communication system in accordance with the variants of the implementation.

Detailed description

As was briefly described above, access rights to the conversation can control the components of the communication system, limiting access to stored components session conversation. In the following detailed description presented with reference to the accompanying drawings, which are part of it, through which the figures illustrate specific embodiments of, or examples. These aspects can be combined, can also be used in other aspects and in addition can be performed structural changes, not beyond the essence or scope of the present disclosure. Therefore, the following detailed description should not be construed in a limiting sense, and the scope of the present invention is defined by the attached claims and their equivalents.

Although variants of implementation will be described in the General context of program modules that execute in conjunction with an application that runs on the operating system on a personal computer, specialists in the art will understand that aspects that the same can be implemented in combination with other program modules.

In General, program modules include standard routines, programs, components, data structures, and other types of structures that perform particular tasks or implement particular abstract data types. In addition, specialists in the art will appreciate that embodiments of may be practiced with other configurations of computing platforms, including handheld devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, mini-computers, General-purpose computing machines and similar computing devices. Options exercise can also be practiced in distributed computing environments where tasks are performed by remote processing devices data that are linked through a communications network. In a distributed computing environment, program modules may be located in both the local and remote storage devices.

Options for implementation may be implemented as implemented in the computer process (method), a computing system or as an industrial product, such as a computer program product or computer readable media. The computer software product may be a computer storage medium, which is considered one of th the receiving computer system and on which is encoded a computer program, which includes commands for prescriptions computer or computing system to perform an illustrative process(es). Machine-readable data carrier may, for example, be implemented using one or more units, volatile memory, nonvolatile memory, hard disk drives, flash memory, floppy disks, or CDs and similar media. The computer program product may also be a propagated signal on a carrier (for example, a signal with frequency or phase modulation) or medium that is read by the computing system and in which is encoded a computer program in the form of commands for executing a computer process.

Throughout this description, the term "platform" may be a combination of software and hardware that controls access rights to the conversation. Examples of platforms include autsorsingovuju service running on multiple servers, an application executing on a single server, and similar systems, but are not limited to. The term "server"generally refers to a computing device executing one or more system programs, typically in a networked environment. However, the server may also be implemented as a virtual server (system programs), executable on the bottom or more computing devices, visible on the network as a server. More detail on these techniques and illustrative of the operation is provided below.

As shown in figure 1, is depicted a graphical representation 100 of the illustrative system of unified communications, which can be implemented options implemented. Unified communications is an illustrative communication system with a wide range of capabilities and services that can be provided to subscribers. Unified communication is a communication system in real time, facilitating instant messaging, presence, voice and video conferencing, the functionality of network conferencing and similar functionality.

In the unified communications ("UC"), such as depicted in the graphical representation 100, users can communicate through a variety of target devices (102 and 104), which are client devices of the UC system. Each client device may be capable of executing one or more communications applications for voice, video, instant messaging, application sharing, data sharing, etc. In addition to their advanced functionality, the target device can also simplify a traditional phone call who you via an external connection, such as through the PBX 124 (private telephone station with access to the shared network to the public switched telephone public network ("PSTN"). The target device may include any type of smartphone, cell phone, any computing device executing a communication application, an intelligent dashboard of the car and advanced telephony device with additional functionality.

Network(s) 110 UC includes multiple servers that perform different tasks. For example, the server 114 UC provide registration, availability and functionality of routing. Functional routing capabilities allow the system to direct the user targeted calls to any of the client devices assigned to the user based on the policies adopted by default and/or user-defined. For example, if the user is not available through the ordinary telephone, the call may be sent to a cell phone user, and if he does not respond, it can be used many options voice mail. Because the target device can work with additional communication modes, servers 114 UC can provide access to these additional modes of communication (e.g. instant messaging, video, etc) via the server 112 access. Behold the ver 112 access is located in the perimeter network and makes it possible to connect via the network(s) 110 UC to other users in one of the additional modes of communication. Servers 114 UC may include servers that perform a combination of the above described functionality, or specialized servers that only provide specific functionality. For example, mail servers, providing the functionality of a presence, routing servers, provide the functionality of the routing servers control access rights and so on. Similarly, the server 112 may provide several features, such as firewall protection and connectivity, or only specified functionality.

The server 118 audio/video (A/V) conferencing provides voice and/or video conference communication by simplifying their work through an internal or external network. Mediation server 116 serves as a link between signaling and media data to other types of networks such as the PSTN or a cellular communication network (for example, calls through the PBX 124 or cell phone 122), or from them. Mediation server 116 may also act as a custom software agent Protocol session (SIP).

In the UC system users can have one or more identifiers, which are not necessarily limited to telefonn the m number. The identifier can take any form depending on networks with integrated services, such as telephone number, universal indicator information resource identifier (URI) of the Protocol session initiation (SIP), or any other identifier. Despite the fact that the UC system can be used by any Protocol, SIP is the preferred method.

SIP is a control Protocol (communication) application level to create, modify, and end sessions with one or more participants. This can be used to create a bilateral, multilateral or group sessions, which include phone calls via the Internet, dissemination of multimedia data and the conference using multimedia tools. SIP is designed to be independent from the underlying transport layer.

SIP clients can use the transmission control Protocol ("TCP") to connect to SIP servers and other target devices SIP. First of all, SIP is used to establish and break a voice or video call. However, it can be used in any application where session initiation is a prerequisite. They include a subscription or event notification, the mobility of the terminal and so on. Voice and/or videoswe the ü, usually performed under a separate Protocol session, as a rule, a transport Protocol real-time ("RTP").

The concept of "conversation", as used herein, refers to multimodal communication session, in which subscribers can communicate through a variety of devices, applications, and communication modes simultaneously or sequentially. For example, two subscriber can initiate a conversation through instant messaging through their personal computers. Then, the communication can be improved to voice and instant messages using one subscriber personal computer for both modes, while the other uses a personal computer for instant messaging and smartphone for voice mode. Other subscribers can join the session or out of it, other modes and devices can be added or removed. The commonality between these types of communication is maintained by means of a designation of all these types of communication as belonging to the same conversation. Conversations can be assigned a unique identifier that allows subscribers to view, record, edit, share, and generally to manage aspects of the conversation, including documents and other data associated with the call (for example, documents the s, exchanged as attachments in a single call or write in other modes of conversation).

Assigned or selected access rights to the conversation for a particular communication session or one or more modes of communication session can be managed and put into action by one of the servers 114 UC UC system, as mentioned above. In accordance with some options exercise of the right of access to the conversation can be managed through a server digital rights management. The server digital rights management can coordinate the encryption information exchange which occurs during a call (communication as such, as well as any associated data, such as nested or generated documents). Participants may be given the keys to the decryption on the basis of their tolerance levels to protect aspects of the conversation in its process or after he was saved. SIP can be used to simplify encryption-based access control to the conversation or otherwise.

As discussed above, the component server rights management servers 114 UC and the encryption mechanism for scrambling links in real time can be used to assign and the introduction of restrictions on the rights of access to communication and its components. For example, the secure key and the RTP server rights management can be used for encryption, the trusted component can ensure that confidential conversations or conversations with the management of access rights are held exclusively between the client terminal devices, which correspond to rights management technologies access to multimedia data. The solution also may have a new use SIP for transportation of various information about the management of access rights for the session and allows the use of SIP or before a session, or in the middle of the session. Various artificial means of identification (artifacts) user interface (UI)that provides end-to-end interaction, can be associated with the management of access rights, such as the limitation of copy/paste, or use information rights management of documents, if they are part of the session sharing the document.

Although illustrative system in figure 1 has been described with specific components such as mediation server, A/V server, and similar devices, ways of implementation are not limited to this illustrative system components and configurations. Service (service) for managing access rights in a conversation can be implemented in other systems and configurations that use fewer components or additional is sustained fashion components. In addition, such systems should not be advanced communication systems, combining different modes of communication. Options for implementation can also be implemented in systems that simplify various communication modes, separately by coordinating options for the implementation of the rules through various modes connection with the use described in this document of principles.

Figure 2 is a conceptual graphical representation 200, illustrating the main illustrative system for managing access rights to the components of the communication session. Despite the fact that the system in accordance with the variants of implementation, likely includes many servers, client devices and services, such as discussed illustratively in figure 1, are related to the modalities for the implementation shown in figure 2.

As discussed earlier, the ability of modern communication systems is that the chat sessions can be saved and made available to partially or fully. For example, shared in a video conference documents can be saved in a searchable way, as well as the conference record. This is a complex problem, related to user's access rights to records multimodal communication sessions. Another aspect of such multimodal communication sessions I have is that that some or all of the modes can be personal or confidential and you or your organization may wish to save the attribute constraints associated with a particular regime or the whole conversation, if the session is saved/archived.

In accordance with some of the options for the implementation of the Protocol session initiation (SIP) can be used to configure complex solutions for managing access rights to the conversation through guarantees that multimedia content multimodal conversation is encrypted using the services control access rights; multimodal conversation in real time is determined by the service management access rights for the introduction of the limitations of the recording and playback based on user selection or configuration policies of the organization; and multimodal conversation in real time may not be recorded if any of the callers decides to activate the function "confidential" conversation.

Multimodal conversations in real time, which can be implemented in the management of rights in accordance with the variants of implementation, include instant messaging, electronic mail, voice telephone, video sharing, application sharing, joint use of the Finance data the electronic boards and the like, but are not limited to. Such multimodal conversation in real time may involve multiple parties, multiple target devices of the same user, as well as several components that can be stored in various ways.

The main components of the system in accordance with options for implementation include the client device 238, executing a communication application user 236, the client device 242 for execution of the application due to user 244 and server 234 the management of access rights. Application of communication for users 236 and 244 provide multimodal communication sessions 240 (within one or more networks between users 236 and 244 (and other users) on the basis of the organizational, system, and user-selectable options related to the quality, quantity and other aspects of communication. For example, the parameters may include the resolution, the quality of speech restrictions puts documents and similar factors. Modes of communication session can also be defined at the beginning of or during an existing communication session on the basis of the organizational, system or custom election.

In accordance with one embodiment of the client application provides the essence of the management solution p is the AV access. The client application allows the user to access the functions of managing access rights before talking or during them. During the initial boot process of the client application receive information regarding registration/rights management from a server, such as server UC). If activated, the function access rights to the conversation, the client applications communicate with the server 234 the management of access rights to generate the corresponding keys control access rights to the conversation and ensure that sent real-time messages (for example, transport Protocol real-time "RTP" or secure transport Protocol real-time "SRTP") encrypted with the license. The client application receiving the protected content, are in communication with the server 234 the management of access rights in order to assist in the decryption of incoming messages with managed access rights. Server 234 rights issues licenses to publish for client applications and enforces usage rights. If the client application to accept incoming INVITE message with SDP that indicates that the session is secure, the client may enter into communication with the server 234 the management of access rights and to obtain a license to use. The servo is 234 the management of access rights can be checked, authorized if the customer has access to the content, and to provide a license to use. If the license cannot be obtained, the client may reject the INVITE message with the appropriate error code.

In an illustrative scenario, the users 236 and 244 can initiate a voice call, which can be improved to video conference with the function of electronic boards based on the capabilities of their client devices (and applications communication) after the accession of the third user who wants to add a video, and whiteboard. Based on this change, the chat session may be changed to a multi-mode version automatically or by user selection. Firstly, you may be given the opportunity of joining the third user based on the assigned/selected by the user attributes access rights of the initial conversation. If one or both users 236 and 244 declared a private conversation, a third user may be given the opportunity to join if it's not specifically allowed users 236 and 244 (a third user may be provided the signal busy/unavailable, or it can be placed on hold, while users 236 and 244 are notified of the request for connection). Second, different aspects of the communication session could the t to be recorded for later retrieval (video, a voice recording, image capture electronic whiteboard, and so on), which can be assigned attributes based permissions assigned by default or by the user's access rights to the conversation. For example, "private" Declaration on the establishment of a voice communication can be extended to additional modes, as well as any records (and attachments), created to save the conversation.

Restrictions control access rights can also be applied based on the Association of different communication modes with specific people, groups or organizations. As discussed above, the rights can be adapted for each communication mode to be applied to different aspects of each communication mode (for example, recording video, attachments, emails, and similar aspects).

In accordance with some of the options for the implementation of the content (e.g. multimedia data) and the shared files in the shared autsorsingovoy the service can be improved to a conference or similar communication that implements access rights to the conversation. For example, if the conversation apply limited access rights, the shared files are associated with this session can also be applied with similar restrictions arising from the call to the saved files.

Despite the fact that some of the rights on the mortar can be applied statically (for example, as defined before the conversation by organizational policies or user) as mentioned previously, other types may vary on the basis of assumptions (for example, user selection during a call, use the access rights for one mode to the newly added mode based on the type of communication mode, etc). In addition, the applicability of the restrictions of the access rights management is not just limited to communications applications. In the advanced modes of communication, such as e-mail, Bulletin boards, data sharing, and so forth, can be used connectivity components, such as nested data, records, etc. by other applications, such as calendar applications, planning applications, word processing applications, compiling spreadsheets, database applications, and other Such applications can be local applications or distributed services that are performed by a Central server and accessed through a browser or similar application. Any rights-based access restrictions assigned to documents (including records)generated through conversation or associated with it, can be saved, if such documents are used by applications not related to communication.

Essential system components, implements the management of access rights to the conversation, are the terminal equipment, which is able to understand and execute permissions set for conversation. If the terminal equipment (physical or software) is unable to understand or execute permissions to the conversation, then this terminal equipment may be denied participation in conversation or control function access rights can be disabled with a notice requesting the access rights of the subscriber.

Figure 3 is a functional graphical representation illustrating the interaction between various components of the communication system in accordance with the variants of implementation. In accordance with an illustrative scenario, the client application 352 for user 1 starts with obtaining a license or certificate for the requested status of the access rights from the server 356 rights management for the initiated session (358). Then the client application 352 generates a SIP INVITE that contains usage information related to access rights to the conversation (e.g., encryption keys) for the client application 354 from user 2 (360). These stages can be included as a component part of the session description Protocol. The receiving client application 354 can guarantee that the INVITE is accepted only when the availability of the appropriate mechanisms to guarantee the introduction of the restriction(s) access rights to the conversation, requested by the user 1. If these mechanisms are available, the client application 354 receives information about access rights/decoding of the server 356 managing access rights (362). Then the client application 354 sends an ACCEPT message to the client application 352 (364). This is followed by the exchange of encrypted messages between a client application 352 and 354, providing the requested communication, subject to restrictions of the access rights to the conversation.

Although this is not shown in the functional graph, restrict access to the conversation can be created/changed also during the call, after stages, such action 358, 360, 362 and 364. Restrictions can be applied to records all or part of this conversation, any documents associated with the session (e.g., created during the session or exchanged as attachments during the session), and records the conversation. For example, copy and paste functionality of the conversation and related documents can be disabled if the session should not be recorded. Constraints can be defined separately for individual components (modes, related documents) session or logically derived from one component to the other (for example, using the scheme). Background or similar recording of the conversation is the thief can be limited to authorized users or to not be supported. In addition, there may be used a special key to establishing trust between a client application in the sense that they are able to handle access rights to the conversation. If one of them is not capable of handling the requested access rights limitations to the conversation, the client application is the initiator may reject the client application is unable or change the aspect of the conversation (for example, to return only to speech from a combination of speech-sharing applications).

Despite the fact that various communication modes and associated communication documents can be defined a number of restrictions on the rights of access to the conversation and rules, some examples may include "confidential", "private", "limited distribution", "preserving a limited time" and similar.

In addition to conference facilities-based UC systems control access rights to the conversation can also be applied to peer-to-peer communication. For example, in the session using CCCP (link control Protocol conferencing) is a Protocol can be modified for a focused message that access rights to the conversation are applied. In this illustrative system, only the leaders can apply access rights to the conversation; once access rights note the tive, they can be applied directly to the members in the list; and some access rights can be rejected if people join the conference anonymously or through the system is not able to match the requested access rights (e.g., PSTN).

In addition, in a typical scenario, digital rights management access permissions are applied and enforced for documents individually or in groups. In the system in accordance with the variants of implementation there are several physical target devices and modalities of communication. Consequently, it can be used the pattern of Association rights of access to the conversation with these different aspects of the session. For example, each applied the right of a session can be defined statement that introduces the applicable modes of communication, the physical target device, the duration of the call, the associated data, and so forth.

Discussed above scenario, the illustrative system, restrict access to the conversation and configurations are intended to illustrate. Options for implementation are not limited to these examples. Other forms of restrictions, configuration, communication modes and scenarios can be used to implement the control of access rights to the conversation in a similar way to the use described in this document of principles.

IG illustrates screen shots (400) illustrative user interfaces for managing access rights to the conversation in a communications application. The elements and configuration of the user interface in the screenshot 470 are solely for illustration and are not limiting to the embodiments. In a communications application, capable of handling access rights to the conversation, you can use any user interface with other elements and configurations.

The user interface of screenshot 470 includes graphical representations of available communication modes in the form of icons (icons, such as icon 472 voice communication and other next to it. Applications that can be related to records and other associated documents can be presented in the form of icons, such as icon 474. Commands and configuration settings associated with the current conversation (for example, disconnection of the connection, conference call with another user, the audio settings and so on), can also be displayed as icons (e.g., icons 476) or in other forms. Text (478) and/or graphic (480) warning relating to the status of access rights to the conversation (for example, "confidential"), can be represented, as well as the list of participants and their status (button 482, 486 radio and icons 484, 488). For illustrative screen shot icon 488 indicates that the user "John Doe" Zap achive "confidential" conversation.

The user interface shown in the screenshot 490 is a menu to select from pre-defined permissions aspect of the conversation. After selecting a command for setting permissions (492) the user can choose from several levels of permissions 494, such as, without limitation, restrictions on forwarding or reply, confidentiality within the company, confidentiality within the company with the restriction read only (for example, 496), restrictions on branches or offices and similar. Other illustrative levels of resolution may include "do not extend to the conference call," "do not record", "allow only personal conversations" (without rooms for conference calls), "limit to workers employed full-time" and so the Conversation can also be created without the participants in accordance with some of the options for implementation, and the respective members can be added after the establishment of permissions.

The user interface for the application connection that can handle access rights to the conversation, may include additional or fewer text and graphic elements and may use different graphics, color and other circuit configurations to display the various features and related the restrictions based on the management of access rights.

Figure 5 is an illustrative network environment in which it can be implemented options implemented. Platform that provides services related to the management of access rights to the conversation, may be implemented via software executed by one or more servers 518, such as autsorsingova service. The platform may communicate with client applications on individual computing devices such as cell phone 513, laptop 512 and desktop computer 511 (client device) via the network(s) 510.

As discussed above, modern communication technologies such as UC services that allow subscribers to use a wide range of computing devices and application functionality in conjunction with the communication services. This means that the subscriber can use one or more devices (e.g., regular phone, smartphone, computer, smart car dashboard etc) for communication. Depending on the capabilities of each device and is available on every device applications may be allowed additional services and communication modes.

Client devices 511-513 used for communications through a variety of modes between subscribers of a communication system. One or more servers 518 can manage the rights of the mi access to the conversation based on the default definitions or the user's selections for the currently used modes of communication. Information associated with subscribers and required for communication with the enactment of the access rights to the conversation, can be stored in one or more storage devices (e.g., device 516 data storage)that can be operated by any of the servers 518 or through a server 514 databases.

Network(s) 510 can contain any topology of servers, clients, service providers, Internet and media transmission. The system in accordance with the variants of the implementation may have a static or dynamic topology. Network(s) 510 may include a secure network such as an enterprise network, an unprotected network, such as an open wireless network, or the Internet. Network(s) 510 may also coordinate communication between other networks such as the PSTN or a cellular network. Network(s) 510 provides communication between the nodes described herein. As an example, and not limitation, the network(s) 510 may include wireless transmission medium, such as acoustic, RF (radio frequency), infrared and other wireless data transmission medium.

Can be used in many other configurations of computing devices, applications, data sources, and data distribution for the implementation of systems related to the management of access rights R is govoru. In addition, the network environment, discussed in Figure 5, mentioned solely for the purpose of illustration. Options for implementation are not limited to the examples, applications, modules, or processes.

6 and the associated discussion are intended to provide a brief General description of a suitable computing environment that can be implemented options implemented. Figure 6 depicts a block diagram of an illustrative computing environment for application in compliance with the variants of the implementation, such as computing device 600. In the basic configuration, computing device 600 may be a server managing access rights as part of the communication system and includes at least one block 602, data processing and system memory 604. Computing device 600 can also include multiple blocks of data that provide the performance of programs. Depending on the exact configuration and type of computing device, system memory 604 may be volatile (such as RAM)), non-volatile (such as ROM (permanent memory), flash memory, etc. or any combination thereof. System memory 604 typically includes an operating system 605, the right to control the operation of the platform, such as operation the e WINDOWS® of Microsoft Corporation, Redmond, Washington. The system memory 604 may also include one or more software applications such as program modules 606, application 622 communication and module 624 management of access rights.

Application 622 may be part of a service that provides communication through a variety of modalities between client applications, servers, and other devices. Module 624 rights management can manage and enforce access rights to the conversation associated with the different communication modes and related documents, as discussed earlier. Module 624 management of access rights and the application 622 connection may be separate applications or integral modules autsorsingovoy services, which provides advanced communication services to client applications/devices. This basic configuration is illustrated in Fig.6 through the components within the dotted line 608.

Computing device 600 may have additional features or functionality. For example, computing device 600 may also include additional data storage devices (removable and/or replaceable), such as, for example, magnetic disks, optical disks or tape. Such additional storage device illustrated in Fig.6 what exploits removable storage device 609 and non-replaceable storage device 610. The computer-readable storage media may include volatile and nonvolatile, removable and non-replaceable media implemented in any method or technology for storage of information such as machine-readable commands, data structures, program modules or other data. System memory 604, a removable storage device 609 and non-replaceable storage device 610, all are examples of machine-readable data carriers. The computer-readable storage media include RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage device or other magnetic storage devices, or any other medium that can be used to store the desired information and which can be accessed by computing device 600, but not confined by them. Any such computer-readable storage media may be part of computing device 600. Computing device 600 can also have the device(s) 612 input, such as keyboard, mouse, pen, audio input device, touch input device, and similar input devices. Can also be enabled device(s) output 614, such as a device from the images, speaker system, printer, and other types of output devices. These devices are well known in the prior art, and in this document do not require detailed discussion.

Computing device 600 may also contain communication connection 616, which allow the device to communicate with other devices 618, such as over a wireless network in a distributed computing environment, satellite communications, cellular communications and other similar mechanisms. Other devices 618 may include computer device(s), which performs application communication, other directory servers, and policies, and similar devices. Communication connection(s) 616 is one example of media data. The transmission medium may include a machine-readable commands, data structures, program modules or other data in a modulated data signal such as a carrier or other data transfer mechanism, and includes any medium of information delivery. The term "modulated data signal" means a signal that has one or more of its parameters set or changed in such a way to encode information in the signal. As an example, but not limitation, the transmission medium include wired media is, such as a wired network or direct-wired connection, and wireless environments, such as acoustic, RF, infrared and other wireless environments.

Illustrative embodiments of also include methods. These methods can be implemented any number of ways, including the structure described in this document. One of such ways is through machine operations of the devices described in this document type.

Another way is for one or more individual operations of ways, which will be undertaken jointly with one or more human operators performing some of them. It is not necessary that these people-the operators were located next to each other, but each of them can only be with the machine, which performs part of the program.

Fig.7 illustrates the logical precedence diagram for process 700 of managing access rights to the conversation in the communication system in accordance with the variants of implementation. Process 700 may be implemented as part of a communication system which provides multiple communication modes.

Process 700 begins with operation 710, in which the client application is accepted the request to create or modify access rights to the call for a new conversation or an existing razgovor the and. The request may relate to the whole conversation, or part (for example, certain modes, the selected components or determinable time part). In operation 720 identifies the associated communication modes and/or components, especially if the request is for a part of the conversation. The determination in operation 720 may include the decision whether to apply the same requested restrictions related to the modes/components and how to use them, if they should be applied (for example, restrictions can be applied in different ways to voice conversations and email exchanges).

In operation 730 for performing the query, the client application may be granted a license/certificate (e.g., encryption keys), confirming the acceptance of the request for access rights management and software making the request the client application tool for the introduction of these restrictions. In operation 740 may be accepted the request for a license/certificate (for example, a decryption key) is a part of the same conversation that could accept the invitation message from the original client application. In accordance with some of the options for the implementation of the management server access rights can confirm that the client application participant is able to enforce access rights to the conversation and/or who is a trusted application, before securing a license/certificate, which allows the client application of a party to communicate with the source client application and to simplify the conversation, using the access rights requested by the original client application.

The operations included in the process 700, provided for purposes of illustration. Communication service for managing access rights to the conversation may be implemented by similar processes with fewer steps or additional steps, as well as with a different order of operations using described herein principles.

The above description, examples and data provide a complete description of the manufacture and use of combinations of embodiments. Although the invention has been described in language characteristic structural features and/or methodological acts, it should be understood that the scope of the invention defined by the attached claims is not necessarily limited to such characteristic features or actions described above. Rather, the features and steps described above are disclosed as illustrative forms of implementing the claims and embodiments.

1. The method, performed at least partially in computing mouth is oiste for control of access rights to the conversation, containing phases in which:
receive a request to create a rights-based access to the conversation limitations for session management server access rights (710);
provide a license to the requesting first client application (730);
receive another request from the second client application for license, and the second client application is invited for participation in the communication session with the first client application (740); and
provide the license to the second client application in response to confirmation that the second client application is a trusted application and adapted to give effect to rights-based access to the call restriction for a communication session (740).

2. The method according to claim 1, in which the license is at least one encryption key for use the first or second client application to encrypt and decrypt messages (360, 362, 364)exchanged during the communication session.

3. The method according to claim 1, wherein the request to create a rights-based access to the call limit is taken in time, which is one of: before initiation of the session 240 connection and during the session 240, this rights-based access to the conversation limitation applies to at least one of the number of the item is in: the recording of the communication session, the record associated with the communication session, and the document associated with the communication session.

4. The method according to claim 1, further comprising stages, which are:
take an additional request from either the first application or the second application to change based on the access rights to the conversation limitations; and
provide a modified license to the requesting application.

5. The method according to claim 1, in which the session 240 connection extends from one of the stored content and the shared data, and based on the access rights to the conversation limitation associated with the communication session 240, applies to this one of the stored content and the shared data, from which extends the session 240 connection.

6. The method according to claim 1, in which rights-based access to the call restriction is used to determine at least one of a number of elements: whether the users are allowed to join the session 240 connection whether the recording of the communication session, the access permissions for at least one of: recording a communication session, the record associated with the communication session, and the document associated with the communication session.

7. The method according to claim 1, in which rights-based access to the conversation limit applies to the document associated with the session 240 connection so that the restriction is saved when the document is not used with the Rel shall provide to the communication application, includes one of a number of elements: application for text processing, the application for compiling spreadsheets, presentation application, a calendar application, a scheduling application, and the application of image processing.

8. The method according to claim 1, in which the session 240 communication is multimodal communication session comprising at least one of a number of elements: voice communication, video communication session using the electronic whiteboard, session sharing data, session-sharing application, session, instant messaging and e-mail exchanges, while rights-based access to the call restriction is determined for a single mode communication session and applies to all modes.

9. The method according to claim 1, in which rights-based access to the conversation limitation includes one of a number of limitations: "confidential", "private", "limited distribution", "do not forward", "no answer", "confidential within the company, confidential within the company with the constraint readonly", "with limited distribution within business units, with limited distribution within the Department, not to extend to the conference call," "do not record", "allow only personal talk", "limit to the worker is in, working full-time" and "c preservation for a limited period of time."

10. Communication system for control of access rights to the conversation that contains:
server connection configured to provide multimodal communication between terminal devices of the system;
the rights management server access configured:
to provide the encryption key to the first terminal equipment in response to a request from the first terminal equipment 730;
to accept the request from the second terminal equipment caused by invitation, sent the first CPE to the second terminal equipment 740;
to determine whether the second terminal equipment trusted terminal equipment and adapted if it is to enforce access rights to the conversation requested by the first terminal equipment; and
if so, provide information decryption to the second terminal equipment so that is the exchange of encrypted messages between the first and second terminal equipments to ensure multimodal communication session 740; otherwise,
to issue an error message to the second terminal equipment, preventing connection of the second terminal equipment to the multimodal communication session.

11. The system of claim 10, in which PR is taken off, the exchange of information about access rights to the conversation between the first terminal equipment, the second terminal equipment and the management server access rights using the components of the session description Protocol (SDP), at the same time refuses access terminal equipment, attempting joining multimodal communication 240, but is unable to comply with applicable access rights to the conversation.

12. The system of claim 10, in which it is determined that the second terminal equipment is a trusted terminal equipment, through the authentication through a trusted server 518 communications systems.

13. Machine-readable data carrier with the stored commands for managing access rights to the conversation through the application multimodal communication, and commands are implemented in stages, which are:
provide a user interface 470 to provide the user an option to initiate a communication session by selecting at least one communication mode, and the user is provided the opportunity to ask the status of access rights to the conversation for a communication session;
receive at least one encryption key from the management server access rights that should be used to operationalize a given status of access rights to the conversation in the session 730;
send an invitation message to another communication app that includes the KJV is anuty at least one encryption key 740; and
on receiving the message about the successful adoption from another application communication provide the communication session by exchanging messages encrypted mentioned at least one encryption key 740.

14. A machine-readable medium of clause 13, in which the session 240 connection 240 is held in the system peer-to-peer communication, in this part apply access rights to the conversation rejected based on the capabilities of the participating terminal equipment.

15. A machine-readable medium of clause 13, in which each applicable right of access to the conversation is determined by the scheme, introducing the applicable modes of communication, physical terminal equipment, the duration of the session 240 communication and associated data.