WO2016033126A1 - Sharing content - Google Patents
Sharing content Download PDFInfo
- Publication number
- WO2016033126A1 WO2016033126A1 PCT/US2015/046835 US2015046835W WO2016033126A1 WO 2016033126 A1 WO2016033126 A1 WO 2016033126A1 US 2015046835 W US2015046835 W US 2015046835W WO 2016033126 A1 WO2016033126 A1 WO 2016033126A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- conversation
- users
- permission
- user
- content item
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/16—Arrangements for providing special services to substations
- H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
- H04L12/1813—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast for computer conferences, e.g. chat rooms
- H04L12/1822—Conducting the conference, e.g. admission, detection, selection or grouping of participants, correlating users to one or more conference sessions, prioritising transmission
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/04—Real-time or near real-time messaging, e.g. instant messaging [IM]
- H04L51/046—Interoperability with other network applications or services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/07—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail characterised by the inclusion of specific contents
- H04L51/10—Multimedia information
Definitions
- IM chat services which enable users to establish private conversations between them, over a network such as the Internet.
- Examples include IM (instant messaging) chat services, VoIP (Voice over Internet Protocol) services, picture messaging services, video messaging services and/or voice messaging services.
- IM chat conversation for example, a user can send a textual message to the one or more other users involved in the conversation.
- VoIP conversation a call
- a user can stream live voice and/or video to the other users in the conversation.
- a user can send a still image to the other users in the
- each of multiple users installs a respective instance of a communication client application on his or her respective user device (e.g. smartphone, tablet, or laptop or desktop computer).
- the communication client application may be implemented in any suitable executable or interpreted code, whether in the form of a stand-alone application running on an operating system, or a plug-in application to another application, or an applet running in a browser (e.g. purely in script, or using an API such as WebRTC).
- a communication client provided by a given communication service provider (potentially including different compatible releases of the application) defines a given communication service, with different service providers producing different applications and therefore providing separate services.
- the IM application produced by a first service provider would provide a first IM service, while a second IM application produced by a second service provider would provide a second IM service; or the VoIP application produced by a first service provider would provide a first VoIP service, while a second VoIP application produced by a second service provider would provide a second VoIP service; and similarly for picture messaging or video messaging applications, etc.
- different conversation media can optionally be combined into the service provided by a given service provider, e.g. the application provided by a first service provider my enable a combination of IM chat messages, voice calling, video calling, picture messaging, video messaging and/or voice messaging to be included in the same conversation.
- the different services are characterised by different systems of usernames.
- a given user is identified within the first communication service (for the purpose of being contacted by other users of the first service) by a first username that is unique amongst the usernames of the first service but not necessarily the second service, and is identified within the second service (for the purpose of being contacted by other users of the second service) by a second username that is unique within the second communication service but not necessarily the first service.
- Private conversations are distinct from other, more public forms of communication such as social media feeds, in that a conversation is an exchange of communications between only a selected group of users who have been selected to take part in the conversation, with the exchange (i.e. both sent and received messages) being self-contained within that group.
- the exchange i.e. both sent and received messages
- the messages posted by any given user are only distributed to selected contacts, but the receiving user's feed will also collect together messages from other user's feeds, and those messages are not necessarily contained within the same group of users.
- Conversations also typically are conducted between smaller groups of users, e.g. less than ten users, less than five users or even just two or three users. Furthermore, usually each participant in a conversation knows who each of the other participants are, and the participants list may be displayed in the presentation of the conversation. Messages sent within a conversation are therefore directed towards specific and known participants and not accessible outside of that group or outside of the conversational context.
- Communication systems that support conversations may also store unique identifiers for conversations. For example, each conversation may have its own ID and records of who the participants are, when the conversation was created and sometimes if there is an administrator with special permissions to add or delete participants to a conversation and change the name of the conversation.
- Conversations allow items of content to be shared within the conversation, and nowadays may include multimedia content items such as still images, video images and/or audio clips.
- multimedia content items such as still images, video images and/or audio clips.
- a picture messaging application allows users to share still images amongst one another
- an IM application may allow a user to insert a picture or video into the conversation to be shared with the other users (e.g. by dragging and dropping the image into the a conversation window of the application).
- any receiving user of a conversation can only view (or play out) the content through the particular client application through which that conversation was conducted, within the context of that conversation, and is blocked from saving the content or sharing it onwards to any other conversations or any other communications services - i.e. confining the content to the particular service and conversation through which it was initially shared by the source user.
- a picture is only viewable through the corresponding picture messaging application through which it was received, and only in the context of the same
- a method for controlling permissions in relation to a private conversation conducted over a network between a selected group of two or more users.
- a private conversation e.g. IM chat conversation, VoIP call or picture messaging conversation
- Each of said group of users participates in the conversation from a respective instance of a communication client (e.g. IM, VoIPor picture messaging application) run on a respective user device (e.g. smartphone, tablet, or laptop or desktop computer).
- the private conversation comprises one or more content items (e.g. text message, still image, video image or audio clip), each of said content items being shared by a respective source user of said group with one or more other users of said group. When shared by the source user, the content item is just shared internally within the private conversation.
- the method comprises associating a respective permissions model with each respective one of the content items.
- the permission model may be attached to the content item by the client of the source user, or by an intermediary server, and in embodiments is attached automatically. Either way, the permission model is configured to act on the communication client (at the devices of the other users) to control permission for the one or more other users to use the respective content item outside of said conversation, e.g. to control permission for the one or more other users to make the respective content item available outside of said conversation.
- permission model which controls (e.g. blocks, grants or inhibits the extent of) the use and/or onwards distribution of the content beyond the conversation. Whether the content is blocked or inhibited is not just a fixed, intrinsic property of the communication client (and therefore the service provided by that client), but rather can be controlled on a per-item basis by a small, settable data structure tagged on to each item of content.
- the permission model may control the permission individually for each of a plurality of the other users of the group, thus specifying which of the other users can share the content item onwards, and/or in what manner each of the other users is permitted to share the item.
- the permission model may control: (a) whether or not the respective content item is permitted to be shared onwards with one or more third-party users who are not users of said group and so not party to the private conversation, and/or which third-party users the respective content item is permitted to be shared with; (b) whether or not the respective content item is permitted to be shared outside the
- communication client application i.e. outside the communication service provided by that application
- other communication services e.g. social media services
- the respective content item is permitted to be shared with
- the permission may be selectably granted by the source user in response to a request from a requesting one of the other users.
- a permission messaging mechanism may be incorporated into the communication client application, enabling a requesting one of the other users to request permission from the respective source user to make one of the content items available outside of the private conversation within which the item was initially shared.
- the respective permission model is then set to grant the requested permission to the requesting user.
- the messaging mechanism may comprise a user interface element, such as a drop down permission menu, which is attached to the content item as presented to the requesting user by the client application on the requesting user's device.
- the client application When the requesting user actuates this user-interface element, the client application then sends the request to the client application on the source user's device.
- the messaging mechanism may comprise a user-interface element, such as a pair of buttons, which is presented to the source user by the communication client application on the source user's device upon receipt of the request, and which provides the source user with an option to either accept or decline the request.
- content shared in a conversation acquires a permission model which can be modified through message based requests and approvals communicated through the same conversation platform.
- a communication system may have existing message types (e.g. text message, photo message, video message) and implement one or more additional message types for requesting and for granting permissions for content shared within the conversation.
- Figure 1 is a schematic diagram of a communication network
- Figure 2 is a schematic illustration of the user interface of a communication client application
- Figure 3 is another schematic illustration of the user interface of a communication client application.
- Figure 1 illustrates a communication system comprising a network 101, e.g. a public wide area internetwork such as the Internet, or a private wide area network such as a company intranet.
- a network 101 e.g. a public wide area internetwork such as the Internet, or a private wide area network such as a company intranet.
- a network 101 Connected to the network 101 is a plurality of user devices in the form of user terminals 102, such as desktop computers, laptop computers, tablets and/or smartphones.
- Each of the user terminals 102 is installed with a respective instance of a communication client application 103 provided by a particular communication service provider.
- the client application 103 takes the form of a computer program comprising any form of code embodied on one or more computer-readable storage media (e.g.
- the communication client application 103 may take any suitable form such as a stand-alone application for running on an operating system, or a plug-in application to run in conjunction with another application, or an applet or other browser-based application for running in a browser such as a web-browser (e.g. purely in script, or using an API such as WebRTC).
- the communication client application 103 may take any suitable form such as a stand-alone application for running on an operating system, or a plug-in application to run in conjunction with another application, or an applet or other browser-based application for running in a browser such as a web-browser (e.g. purely in script, or using an API such as WebRTC).
- the communication client application 103 may take any suitable form such as a stand-alone application for running on an operating system, or a plug-in application to run in conjunction with another application, or an applet or other browser-based application for running in a browser such as a web-browser (e.g. purely in script
- communication client 103 may be an IM application for conducting IM chat conversations over the network 101; a voice and/or video calling client such as a VoIP client for conducting live voice and/or video calls between user terminals 102 over the network 101; and/or a picture, video and/or voice messaging application for sending pictures, video clips and/or audio clips over the network.
- a voice and/or video calling client such as a VoIP client for conducting live voice and/or video calls between user terminals 102 over the network 101
- a picture, video and/or voice messaging application for sending pictures, video clips and/or audio clips over the network.
- four user terminals 102a, 102b, 102c, 102d of four respective users Annabelle, Beatrice, Clive and Donald are shown for illustrative purposes. However, it will be appreciated that may more such user terminals
- the multiple instances of the client application 103 running on the different user terminals 102 act to provide a communication service, with each of the users being identified by a different respective username that is unique amongst all users of the communication service in question.
- a first one of the users e.g. Annabelle
- the client 103 on the first user's terminal 102a sends an invitation to the instance of the client
- conversation is identified by a conversation ID, which is unique at least amongst the IDs of any other conversations currently ongoing within the communication service in question.
- the client application 103 is configured to present each user with at least a region of the client's user interface dedicated to the conversation, e.g. a conversation window, through which he or she can input outgoing content items and view received content items as part of that conversation.
- a user the "source” user
- inputs a content item e.g. a picture of him or herself
- the client 103 then sends that content item over the network 101 to the instance on the client 103 on the user terminal(s) 102b of the one or more other, receiving participants of the conversation.
- the receiving instance 103 then presents the content item (e.g.
- the instance of the client application 103 running on Beatrice's terminal 102 is displaying a user- interface 200 of the client 103 comprising a region 201 representing the conversation with Annabelle, e.g. a conversation window specific to that conversation.
- Annabelle shares a picture of herself (e.g. a "selfie") 202 via a corresponding user interface at Annabelle 's end.
- the client 103 on Annabelle 's terminal 102a sends the picture to the client 103 on Beatrice's terminal 102b as part of the conversation established between them ( identified by the conversation ID of that conversation), and in response, the client 103 on Beatrice's terminal 102b presents the picture within the conversation user-interface region 201 (e.g. conversation window) of the client interface 200.
- the conversation user-interface region 201 e.g. conversation window
- Annabelle or her terminal 102a may apply to any source user sharing content into a conversation, and any statements made herein in relation to Beatrice or her terminal 102b may apply to any one or more other participants of a conversation receiving content shared by a source user within that private conversation. Similarly any statements made in relation to Clive or Donald or their terminals 102c, 102d may more generally apply to any users that are not participants of the conversation in question.
- a server 104 running a serving application 105.
- This server 104 may be implemented as a single server unit, or more generally may be a logical server comprising one or more server units over one or more geographical sites.
- the serving application 105 takes the form of a computer program comprising code embodied on one or more computer-readable storage media (e.g. a magnetic medium such as a hard drive, an electronic medium such as EEPROM of
- this (logical) server 104 also defines the communication service together with the client application 103 - i.e. the communication service through which the conversation is conducted is that provided by the service provider operating the server 104 and providing the client application 103, being distinct from other communication services which are those provided by other providers from other (logical) servers.
- the serving application 105 may have any one or more of a number of roles in the conversation. For instance, the invitation and acceptance messages involved when starting a conversation or adding a new user to a conversation may be sent between the client 103 on the inviting user's terminal 102a and the client 103 on the invited user's terminal 102b via the serving application 105 on the server 104, such that the server 104 mediates the establishment (set-up) of the conversation.
- the serving application 105 may also perform related functions such as authenticating users for joining conversations, and providing address look-up for determining the network address of the users' terminals 102 based on their usernames. And/or the actual content of the conversations may be transmitted between the clients 103 on the users' terminals 102 via the serving application 105 on the server 104.
- the server 104 acts as a relay or host of the
- conversation being an intermediary of the actual user communications (content) involved in the conversation.
- client does not necessarily mean a client to a server, but may also cover a P2P client or more generally may refer to a client of any centralised and/or distributed communication infrastructure.
- the permission model is attached automatically to shared content whenever a user (the source user) shares a content item into a conversation (e.g. whenever he or she shares a picture, video clip or audio clip).
- a user the source user
- shares a content item into a conversation e.g. whenever he or she shares a picture, video clip or audio clip.
- the adding of the permissions model to the content item may be performed by the client application 103 on the source user's terminal 102a, or by the serving application 105 on the server 104.
- the permissions model is a data structure that is electronically attached to the shared content item. It may specify sharing permissions on a per "sharee" user basis (per user with whom the content item is initially shared within the conversation), i.e. it provides the ability to specify permissions individually for different participants of the conversation in question. Alternatively or additionally, the permission model may specify the sharing permissions on a per third-party user basis (per user outside the conversation), i.e. it provides the ability to individually specify which non-participating users the content item can be shared with. Alternatively or additionally, the permission model may specify the permissions on a per third-party service basis (i.e. per communication service other than that provided by the communication client 103 through which the conversation is conducted). E.g.
- the permission model could even specify different third party users and/or services for different participants of the conversation, i.e. individually specifying which third party users and/or services each of the participants is permitted to share the item with.
- Other alternative or additional permissions that may be specified by the permissions model include whether the content item is allowed to be shared with one or more other conversations conducted through the same communication client 103 as the conversation in which the item was originally shared (i.e. into other conversations within the same communication service), and/or whether the receiving participant is permitted to save the content item to local storage on his or her own user terminal 102b (i.e. as a file that can be used outside the client 103 through which the conversation was conducted, e.g. to be accessed via a file system).
- the permissions model may comprise a table specifying a respective permission for each of the participants by mapping permissions to usernames (or other suitable identifiers), i.e. the permission model has a "slot" for specifying the permission granted to each of the other users. For instance:
- the client application 103 and/or serving application 105 is/are configured to respect the permissions specified by the permissions model.
- a conversation conducted through the communication service provided by the client application 103 and any associated server 104 cannot be shared out to other services or destinations (such as social media sites) without conforming to the permissions for that content item.
- the person adding the content to the conversation chat is made the "owner” and has control over permissions to share his or her content out to other services or destinations as he or she wishes.
- the person sharing the content may, as the "owner", retain full rights by default so that they may take any action at any later time on any content which they have shared into the conversation.
- the permission model is automatically set by default (by the source user's client 103 or serving application 105) to block any sharing or other making available of the content item outside of the conversation (or at least is set to the most restricted level).
- a participant who receives the item within the conversation (the "sharee") must request the desired permission from the source user.
- content inside the communication service provided by the client 103 and any associated server 104 is "sandboxed" to remain within that service by default.
- Other participants in the conversation have to request permissions from the owner before they can copy the content out of the particular client application 103 and send it to another service or destination.
- a permissions messaging mechanism is incorporated into the client application 103.
- the permission messaging mechanism includes a user interface element 204, 206 that is presented to the receiving participant of the conversation (the "sharee") as being attached to or at least in some way associated with the received content item, e.g. overlaid on or placed alongside a shared picture.
- this user interface element may comprise a button 204 which when activated (e.g. clicked or tapped) summons a drop-down menu 206, the menu 206 presenting the receiving participant (the "sharee") with a plurality of permissions which he or she may select to request from the source user (the "sharer").
- the permission messaging mechanism also comprises a message type of the client application's messaging scheme, being an additional message type defined for requesting and granting (or denying) permissions in relation to content shared within a conversation.
- a message type of the client application's messaging scheme being an additional message type defined for requesting and granting (or denying) permissions in relation to content shared within a conversation.
- the client application supports a set of message types such as IM, video call, voicemail, etc., then an additional permissions message type may be added to this set.
- the client 103 When the requesting participant of the conversation (the "sharee") actuates the user interface element 204, 206 to request permission, the client 103 at the respective terminal 102b generates a request message of the permissions message type, which it sends over the network 101 to the client 103 on the source user's terminal 102a (in embodiments via the serving application 105 on the server 104, though not in all possible implementations). In response, at the source user's terminal 102a, the client 103 presents another user interface element 302, 304, 306 of the permissions messaging mechanism, allowing the source user to select whether to grant permission.
- this may comprise a box 302 or other such on-screen message comprising a pair of buttons 304, 206, presenting the source user with the option to either accept or decline the request respectively.
- the permissions requesting message and the permissions granting message could either appear in the same conversation as all the other messages, or could be exchanged one-on-one between the requester and the owner but still through the same communication application 103.
- the client 103 on the source user's terminal 102a If the source user accepts, then in response, the client 103 on the source user's terminal 102a generates an acceptance message of the permissions message type which it returns over the network 101 to the client 103 on the requesting user's terminal 102b (in embodiments via the serving application 105 on the server 104, though not in all possible implementations). The client 103 on the requesting user's terminal 102b then grants the relevant permission in accordance with the acceptance message. If the request is declined on the other hand, the client 103 on the source user's terminal 102a could respond with an explicit decline message of the permissions message type, or alternatively could just not respond so that the permission is left ungranted by default.
- each content item has a share menu 204, 206 attached to it.
- the options on the share menu 206 vary by participant and their current permissions.
- the menu displays the destination options available to them (e.g. Social Media Service X, Social Media Service Y, save to disc, etc.).
- the menu becomes a way to construct a request message to the owner to request such permission.
- the menu displays the name of the owner and options for the desired destination: "Ask [owner of the content item] if this content can be shared to destination [Social Media Service X, Social Media Service Y, Save to disc]".
- a request message is created by selecting the desired destination and is automatically sent to the owner as a message of the messaging mechanism of the client application 103, e.g. by sending the message in a one-to-one chat with the owner.
- permissions are granted by the owner to one person at a time for each content item as a response to a request from that person.
- the request messages are one-to-one messages between the requester and the owner and approving the request is only for the one requesting individual.
- the owner receives a request message which contains options to approve or decline: "[Requester's name] wants to share this content item [photo, video, etc] to destination [Social Media Service X, Social Media Service Y, Save to disc, etc]. Do you [Approve] or [Decline]. Send [option to add personal message]”.
- permissions to share content from one conversation to another conversation conducted using the same communication service could be required in the same way as permissions are required for sharing out from the client application 103 to a third- party destination such as a social media service.
- the source user's client 103 or serving application 105 may apply a watermark of the communication service in question, branding the content shared from that service into other services, so as to drive brand awareness.
- the messaging mechanism of the client 103 may support the option for the owner to revoke the permissions they have previously granted to another person for a particular item of content.
- the messaging mechanism is used to send a message of the permissions message type from the client 103 on the source user's terminal 102a to the client 103 on the other's terminal 103b. This message acts on the client 103 at the other user's terminal 102b to set the permission model back to blocking the other user from making the content available outside of the conversation, or at least set the permission model back to a lesser degree of permission.
- the permission model may control permissions for other classes of actions that recipient users can take in relation to received content.
- other examples of such actions may include editing, remixing, and/or other forms of modification, or potentially any actions that are usually restricted by digital rights management (copying, printing, etc).
Abstract
Description
Claims
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201580046691.1A CN106605386B (en) | 2014-08-29 | 2015-08-26 | Method and device for sharing content |
EP15760341.6A EP3167570B1 (en) | 2014-08-29 | 2015-08-26 | Sharing content |
KR1020177007643A KR102378954B1 (en) | 2014-08-29 | 2015-08-26 | Sharing content |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
GB1415357.1 | 2014-08-29 | ||
GBGB1415357.1A GB201415357D0 (en) | 2014-08-29 | 2014-08-29 | Sharing content |
US14/538,680 US10002260B2 (en) | 2014-08-29 | 2014-11-11 | Sharing content |
US14/538,680 | 2014-11-11 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2016033126A1 true WO2016033126A1 (en) | 2016-03-03 |
Family
ID=54065471
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2015/046835 WO2016033126A1 (en) | 2014-08-29 | 2015-08-26 | Sharing content |
Country Status (1)
Country | Link |
---|---|
WO (1) | WO2016033126A1 (en) |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20100242091A1 (en) * | 2009-03-23 | 2010-09-23 | Microsoft Corporation | Network video messaging |
WO2011094028A1 (en) * | 2010-02-01 | 2011-08-04 | Orbach David M | System for distribution permissions for network communications |
-
2015
- 2015-08-26 WO PCT/US2015/046835 patent/WO2016033126A1/en active Application Filing
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20100242091A1 (en) * | 2009-03-23 | 2010-09-23 | Microsoft Corporation | Network video messaging |
WO2011094028A1 (en) * | 2010-02-01 | 2011-08-04 | Orbach David M | System for distribution permissions for network communications |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP3167570B1 (en) | Sharing content | |
JP6558430B2 (en) | An approach for accessing third-party content collaboration services on interactive whiteboard devices using the wrapper application program interface | |
US10298635B2 (en) | Approach for accessing third-party content collaboration services on interactive whiteboard appliances using a wrapper application program interface | |
US10250592B2 (en) | Approach for accessing third-party content collaboration services on interactive whiteboard appliances using cross-license authentication | |
US10382501B2 (en) | Multifunction collaboration within an electronic meeting | |
US9246917B2 (en) | Live representation of users within online systems | |
CA2977035C (en) | System and method for video communication | |
US20170366784A1 (en) | Displaying Concurrently Presented Versions in Web Conferences | |
US8751572B1 (en) | Multi-user chat search and access to chat archive | |
US20130179491A1 (en) | Access controls for communication sessions | |
US10284609B2 (en) | Multifunction collaboration within an electronic meeting | |
US10528211B2 (en) | Computing systems and processes for simultaneous co-development of dashboard interfaces | |
JP2013232819A (en) | Electronic conference system | |
US11553011B1 (en) | Methods and systems for facilitating a collaborative work environment | |
US11677908B2 (en) | Methods and systems for facilitating a collaborative work environment | |
WO2016033126A1 (en) | Sharing content | |
KR101898546B1 (en) | Terminal and system for providing chatting service, and computer readable recorder medium storing a program for providing chatting service | |
US11863335B1 (en) | Chat channel highlights | |
US20230156154A1 (en) | Methods and systems for facilitating a collaborative work environment | |
US20230156051A1 (en) | Methods and systems for facilitating a collaborative work environment | |
JP2014053820A (en) | System and electronic apparatus | |
WO2023086021A2 (en) | Methods and systems for facilitating a collaborative work environment | |
TR2021018363A2 (en) | INFORMATION SHARING SYSTEM THROUGH VIDEO CONFERENCE | |
CN118044171A (en) | Method and system for facilitating a collaborative work environment |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
DPE2 | Request for preliminary examination filed before expiration of 19th month from priority date (pct application filed from 20040101) | ||
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 15760341 Country of ref document: EP Kind code of ref document: A1 |
|
REEP | Request for entry into the european phase |
Ref document number: 2015760341 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2015760341 Country of ref document: EP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 20177007643 Country of ref document: KR Kind code of ref document: A |