US20210081563A1 - Multiuser information exchange management - Google Patents
Multiuser information exchange management Download PDFInfo
- Publication number
- US20210081563A1 US20210081563A1 US16/575,130 US201916575130A US2021081563A1 US 20210081563 A1 US20210081563 A1 US 20210081563A1 US 201916575130 A US201916575130 A US 201916575130A US 2021081563 A1 US2021081563 A1 US 2021081563A1
- Authority
- US
- United States
- Prior art keywords
- permission
- information
- receive
- permissions
- audio
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
- G06F21/6245—Protecting personal data, e.g. for financial or medical purposes
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/602—Providing cryptographic facilities or services
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
- G06F21/6272—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database by registering files or documents with a third party
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/16—Sound input; Sound output
- G06F3/167—Audio in a user interface, e.g. using voice commands for navigating, audio feedback
Definitions
- the subject matter disclosed herein relates to multiuser information exchange and more particularly relates to multiuser information exchange management.
- the apparatus includes a processor and a memory that stores code executable by the processor.
- the processor receives information permissions for a plurality of participants in an electronic forum.
- the information permissions include an audio permission, a video permission, a file share permission, a drawing permission, and/or a presentation permission for each participant.
- the processor provides forum information to each participant based on the information permissions.
- the audio permission is required to receive audio from the electronic forum.
- the video permission is required to receive video from the electronic forum.
- the file share permission is required to receive a file from the electronic forum.
- the drawing permission is required to receive a drawing from the electronic forum.
- the presentation permission is required to receive a presentation from the electronic forum.
- a method and program product also perform the functions of the apparatus.
- FIG. 1A is a schematic block diagram illustrating one embodiment of an electronic forum
- FIG. 1B is drawings of illustrating embodiments of electronic devices
- FIG. 2A is a schematic block diagram illustrating one embodiment of information permissions
- FIG. 2B is a schematic block diagram illustrating one embodiment of forum information
- FIG. 3 is drawing illustrating one embodiment of a user interface
- FIG. 4 is a schematic block diagram illustrating one embodiment of a computer
- FIG. 5 is a schematic flow chart diagram illustrating one embodiment of a forum information management method.
- embodiments may be embodied as a system, method or program product. Accordingly, embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, embodiments may take the form of a program product embodied in one or more computer readable storage devices storing machine readable code, computer readable code, and/or program code, referred hereafter as code. The storage devices may be tangible, non-transitory, and/or non-transmission. The storage devices may not embody signals. In a certain embodiment, the storage devices only employ signals for accessing code.
- modules may be implemented as a hardware circuit comprising custom VLSI circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components.
- a module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.
- Modules may also be implemented in code and/or software for execution by various types of processors.
- An identified module of code may, for instance, comprise one or more physical or logical blocks of executable code which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module need not be physically located together, but may comprise disparate instructions stored in different locations which, when joined logically together, comprise the module and achieve the stated purpose for the module.
- a module of code may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices.
- operational data may be identified and illustrated herein within modules, and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different computer readable storage devices.
- the software portions are stored on one or more computer readable storage devices.
- the computer readable medium may be a computer readable storage medium.
- the computer readable storage medium may be a storage device storing the code.
- the storage device may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.
- a storage device More specific examples (a non-exhaustive list) of the storage device would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
- a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
- Code for carrying out operations for embodiments may be written in any combination of one or more programming languages including an object oriented programming language such as Python, Ruby, R, Java, Java Script, Smalltalk, C++, C sharp, Lisp, Clojure, PHP, or the like, and conventional procedural programming languages, such as the “C” programming language, or the like, and/or machine languages such as assembly languages.
- the code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server.
- the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
- LAN local area network
- WAN wide area network
- Internet Service Provider an Internet Service Provider
- the code may also be stored in a storage device that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the storage device produce an article of manufacture including instructions which implement the function/act specified in the schematic flowchart diagrams and/or schematic block diagrams block or blocks.
- the code may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the code which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
- each block in the schematic flowchart diagrams and/or schematic block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions of the code for implementing the specified logical function(s).
- FIG. 1A is a schematic block diagram illustrating one embodiment of an electronic forum 100 .
- the electronic forum 100 allows one or more participants 120 to collaborate and share information online.
- the electronic forum 100 includes a server 105 , a network 115 , a plurality of electronic devices 110 , and a plurality of participants 120 .
- the electronic forum 100 may include one or more sets of information permissions 200 .
- the network 115 may be the Internet, a mobile telephone network, a Wi-Fi network, a wide-area network, a local area network, or combinations thereof.
- the electronic forum 100 may be an audio conference, a video conference, a virtual conference, and the like.
- the participants 120 collaborate and share forum information through the electronic devices 110 .
- the forum information may include audio, video, files, drawings, and/or presentations.
- the electronic devices 110 may communicate through the network 115 .
- the server 105 may manage the exchanges of forum information in the electronic forum 100 .
- each participant in the electronic forum 100 is able to access all forum information that is shared in the electronic forum 100 .
- the embodiments receive the information permissions 200 for the participants 120 and provide the forum information to each participant 120 based on the information permissions 200 .
- each participant 120 only receives forum information that the participant 120 should have access to.
- one or more participants 120 may be categorized in a group 125 .
- the participants 120 in the group 125 share a set of information permissions 200 .
- FIG. 1B is drawings of illustrating embodiments of electronic devices 110 .
- a virtual-reality electronic device 110 a a mobile telephone electronic device 110 b , and a laptop computer electronic device 110 c are shown.
- Other electronic devices 100 may be employed.
- the electronic devices 110 may exchange forum information including audio, video, files, drawings, and/or presentations.
- FIG. 2A is a schematic block diagram illustrating one embodiment of the information permissions 200 .
- the information permissions 200 specify the forum information 250 that each participant 120 may receive from the electronic forum 100 .
- the information permissions 200 maybe organized as a data structure in a memory.
- the information permissions 200 includes an audio permission 201 , a video permission 203 , a file share permission 205 , a drawing permission 207 , and a presentation permission 209 .
- the information permissions 200 may include an audio time stamp 221 , a video time stamp 223 , a file share timestamp 225 , a drawing timestamp 227 , and a presentation timestamp 229 .
- each permission 201 / 203 / 205 / 207 / 209 may have a corresponding timestamp 221 / 223 / 225 / 227 / 229 .
- the audio permission 201 may be required to receive audio from the electronic forum 100 .
- the video permission 203 may be required to receive video from the electronic forum 100 .
- the file share permission 205 may be required to receive a file from the electronic forum 100 .
- the drawing permission 207 may be required to receive a drawing from the electronic forum 100 .
- the presentation permission 209 may be required to receive a presentation from the electronic forum 100 .
- the server 105 and/or electronic device 110 may communicate the audio, the video, the file, the drawing, and/or the presentation in response to a corresponding permission 201 / 203 / 205 / 207 / 209 being set.
- server 105 and/or electronic device 110 may communicate the audio in response to the audio permission 201 being set.
- the server 105 and/or electronic device 110 communicates the audio, the video, the file, the drawing, and/or the presentation in response to the corresponding timestamp 221 / 223 / 225 / 227 / 229 preceding a current time.
- the server 105 and/or electronic device 110 may communicate the video in response to the video timestamp 223 preceding the current time.
- the server 105 and/or electronic device 110 may communicate the audio, the video, the file, the drawing, and/or the presentation in response to both a corresponding permission 201 / 203 / 205 / 207 / 209 being set and the corresponding timestamp 221 / 223 / 225 / 227 / 229 preceding the current time.
- server 105 and/or electronic device 110 may communicate the presentation in response to both the presentation permission 209 being set and the presentation timestamp 229 preceding the current time.
- FIG. 2B is a schematic block diagram illustrating one embodiment of forum information 250 .
- the forum information 250 may be communicated between the electronic devices 110 and/or server 105 over the network 115 .
- the forum information 250 maybe organized as data in one or more packets.
- the forum information 250 maybe organized as a data structure in a memory.
- the forum information 250 includes the audio 251 , the video 253 , a file 255 , the drawing 257 , and/or the presentation 259 .
- the forum information 250 may include a command 270 .
- the audio 251 may include audio data from one or more participants 120 .
- the video 253 may include video data from one or more participants 120 .
- the file 255 may comprise data organized in a file structure that is shared between participants 120 .
- the drawing 257 may include bitmapped, vector, and the like graphic information that is generated by a participant 120 and rendered for other participants 120 .
- the presentation 259 may be a presentation data structure that is presented by a first participant 120 to other participants 120 .
- the command 270 may be received by an electronic device 110 .
- the command 270 may be received as a voice command.
- the command 270 may be received through the user interface as will be described hereafter.
- the command 270 may specify and/or modify the information permissions 200 .
- the information permissions 200 may be received from a first participant 120 as a voice command 270 .
- the information permissions 200 may be received through the user interface.
- FIG. 3 is drawing illustrating one embodiment of a user interface 300 .
- the user interface 300 may be presented to a participant 120 on a display of the electronic device 110 .
- the participant 120 may interact with the user interface 300 using a keyboard, a pointing device, and the like.
- the user interface 300 displays information types 303 comprising the forum information 250 employed in a given electronic forum 100 .
- the user interface 300 may display the participants 120 and/or groups 125 participating in the electronic forum 100 .
- participants 120 that are part of a group 125 are only presented as part of the group 125 .
- participants 120 that are part of a group 125 are presented both individually and as part of the group.
- both the group 125 and the participants of the group 125 are presented in the user interface 300 .
- the user interface 300 may receive permission selections 305 for each combination of information type 303 and participant 120 and/or group 125 .
- the permissions selections 305 may specify which participant 120 and/or group 125 may receive which forum information 250 .
- the permission selections 305 may set the corresponding permissions 201 / 203 / 205 / 207 / 209 .
- the permission selections 305 may set the corresponding timestamps 221 / 223 / 225 / 227 / 229 to a current time.
- the permission selections 305 may set the corresponding timestamps 221 / 223 / 225 / 227 / 229 to a specified time.
- the user interface 300 receives a single set of information permissions 200 for each of the plurality of participants 120 .
- the user interface 300 may receive the single set of information permissions 200 from an administrator.
- the administrator may be a designated participant 120 .
- instances of the user interface 300 receive information permissions 200 for each of the plurality of participants 120 from each of the plurality of participants 120 .
- a first instance of the user interface 300 may receive first information permissions 200 from a first participant 120 and the second instance of the user interface 300 may receive second information permissions 200 from a second participant 120 .
- the information permission 200 received from a participant 120 applies only to the forum information 250 originating from that participant 120 .
- the information permission 200 received from a first participant 120 may apply only to the audio 251 , video 253 , file 255 , drawing 257 , and/or presentation 259 originating from the first participant 120 .
- the information permission 200 received from a participant 120 applies to all the forum information 250 originating from all participants 120 .
- the information permission 200 received from the participant 120 applies only to the participants 120 as specified in the user interface 300 by the permissions selections 305 .
- FIG. 4 is a schematic block diagram illustrating one embodiment of a computer 400 .
- the computer 400 may be embodied each of the electronic devices 110 and the server 105 .
- the computer 400 includes a processor 405 , a memory 410 , and communication hardware 415 .
- the memory 410 may include a semiconductor storage device, a hard disk drive, an optical storage device, or combinations thereof.
- the memory 410 may store code.
- the processor 405 may execute the code.
- the communication hardware 415 may communicate with other devices such as the network 115 .
- FIG. 5 is a schematic flow chart diagram illustrating one embodiment of a forum information management method 500 .
- the method 500 may receive information permissions 200 for the plurality of participants 120 in the electronic forum 100 and provide the forum information 250 to each participant 120 based on the information permissions 200 .
- the method 500 may be performed by the processor 405 .
- the method 500 starts, and in one embodiment, the processor 405 receives 501 the information permissions 200 for the plurality of participants 120 in the electronic forum 100 .
- the information permissions 200 may be received 501 from the user interface 300 .
- the user interface 300 generates the command 270 that is communicated to the server 105 .
- the information permissions 200 may be received 501 as a voice command 270 .
- the information permissions 200 are received 501 from an administrator.
- sets of information permissions 200 may be received 501 from each participant 120 .
- the information permissions 200 may comprise the audio permission 201 , the video permission 203 , the file share permission 205 , the drawing permission 207 , and/or the presentation permission 209 for each participant 120 .
- one or more participants 120 are organized in a group 125 .
- a first set of information permissions 200 may be assigned to the group 125 .
- the information permissions 200 for each participant 120 in the group 125 may be the information permissions 200 for the group 125 .
- the information permissions 200 may be received 501 at any time during the electronic forum 100 .
- a first participant 120 may communicate updated information permissions 200 to the processor 405 before sharing confidential forum information 200 with only specified participants 120 .
- Updating the information permissions 250 may comprise updating a corresponding timestamp 221 / 223 / 225 / 227 / 229 with the current time if permission is granted and updating the corresponding timestamp 221 / 223 / 225 / 227 / 229 with a null value if the permission is withdrawn.
- updating the information permissions 250 may comprise setting the corresponding permission 201 / 203 / 205 / 207 / 209 if permission is granted and clearing the permission 201 / 203 / 205 / 207 / 209 if the permission is withdrawn.
- the administrator may update the drawing permission 207 for a first participant 120 to withdraw the drawing permission 207 .
- the server 105 may record a null value to the drawing timestamp 227 for the first participant 120 .
- the server 105 may clear the drawing permission 207 .
- the first participant 120 will subsequently not receive a drawing 257 .
- the administrator may update the drawing permission 207 for the first participant 120 to grant the drawing permission 207 .
- the server 105 may record a current time to the drawing timestamp 227 for the first participant 120 . As a result, the first participant 120 will subsequently receive the drawing 257 .
- the processor 405 may provide 503 the forum information 250 to each participant 120 based on the information permissions 200 .
- the audio permission 201 may be required to receive audio 251 from the electronic forum 100 .
- the video permission 203 may be required to receive video 253 from the electronic forum 100 .
- the file share permission 205 may be required to receive a file 255 from the electronic forum 100 .
- the drawing permission 207 may be required to receive a drawing 257 from the electronic forum 100 .
- the presentation permission 209 may be required to receive a presentation 259 from the electronic forum 100 .
- the server 205 communicates the audio 251 , the video 253 , the file 255 , the drawing 257 , and/or the presentation 259 in response to the corresponding timestamp 221 / 223 / 225 / 227 / 229 preceding the current time.
- the server 205 communicates the audio 251 , the video 253 , the file 255 , the drawing 257 , and/or the presentation 259 in response to the corresponding permission 201 / 203 / 205 / 207 / 209 being set.
- the processor 405 may further loop to receive 501 subsequent information permissions 200 .
- the embodiments receive the information permissions 200 and provide the forum information 250 based on the information permissions 200 .
- an administrator and/or each participant 120 may grant or restrict specific forum information 250 for specific participants 120 .
- forum information 250 may be selectively withheld from participants 120 , facilitating the selective dissemination of information within the electronic forum 100 .
- a single electronic forum 100 may thus be used to selectively share the forum information 250 among a larger group of participants 120 than could participate in the electronic forum 100 if all participants 120 received the same forum information 250 .
- the efficiency of the electronic forum 100 and the computers 400 employed therein is improved using the information permissions 200 .
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Health & Medical Sciences (AREA)
- General Health & Medical Sciences (AREA)
- Bioethics (AREA)
- General Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- Software Systems (AREA)
- Computer Security & Cryptography (AREA)
- Computer Hardware Design (AREA)
- Databases & Information Systems (AREA)
- Medical Informatics (AREA)
- Multimedia (AREA)
- Audiology, Speech & Language Pathology (AREA)
- Human Computer Interaction (AREA)
- Information Transfer Between Computers (AREA)
- Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)
Abstract
Description
- The subject matter disclosed herein relates to multiuser information exchange and more particularly relates to multiuser information exchange management.
- Diverse participants share information in electronic forums.
- An apparatus for multiuser information exchange management is disclosed. The apparatus includes a processor and a memory that stores code executable by the processor. The processor receives information permissions for a plurality of participants in an electronic forum. The information permissions include an audio permission, a video permission, a file share permission, a drawing permission, and/or a presentation permission for each participant. The processor provides forum information to each participant based on the information permissions. The audio permission is required to receive audio from the electronic forum. The video permission is required to receive video from the electronic forum. The file share permission is required to receive a file from the electronic forum. The drawing permission is required to receive a drawing from the electronic forum. The presentation permission is required to receive a presentation from the electronic forum. A method and program product also perform the functions of the apparatus.
- A more particular description of the embodiments briefly described above will be rendered by reference to specific embodiments that are illustrated in the appended drawings. Understanding that these drawings depict only some embodiments and are not therefore to be considered to be limiting of scope, the embodiments will be described and explained with additional specificity and detail through the use of the accompanying drawings, in which:
-
FIG. 1A is a schematic block diagram illustrating one embodiment of an electronic forum; -
FIG. 1B is drawings of illustrating embodiments of electronic devices; -
FIG. 2A is a schematic block diagram illustrating one embodiment of information permissions; -
FIG. 2B is a schematic block diagram illustrating one embodiment of forum information; -
FIG. 3 is drawing illustrating one embodiment of a user interface; -
FIG. 4 is a schematic block diagram illustrating one embodiment of a computer; and -
FIG. 5 is a schematic flow chart diagram illustrating one embodiment of a forum information management method. - As will be appreciated by one skilled in the art, aspects of the embodiments may be embodied as a system, method or program product. Accordingly, embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, embodiments may take the form of a program product embodied in one or more computer readable storage devices storing machine readable code, computer readable code, and/or program code, referred hereafter as code. The storage devices may be tangible, non-transitory, and/or non-transmission. The storage devices may not embody signals. In a certain embodiment, the storage devices only employ signals for accessing code.
- Many of the functional units described in this specification have been labeled as modules, in order to more particularly emphasize their implementation independence. For example, a module may be implemented as a hardware circuit comprising custom VLSI circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.
- Modules may also be implemented in code and/or software for execution by various types of processors. An identified module of code may, for instance, comprise one or more physical or logical blocks of executable code which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module need not be physically located together, but may comprise disparate instructions stored in different locations which, when joined logically together, comprise the module and achieve the stated purpose for the module.
- Indeed, a module of code may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and illustrated herein within modules, and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different computer readable storage devices. Where a module or portions of a module are implemented in software, the software portions are stored on one or more computer readable storage devices.
- Any combination of one or more computer readable medium may be utilized. The computer readable medium may be a computer readable storage medium. The computer readable storage medium may be a storage device storing the code. The storage device may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.
- More specific examples (a non-exhaustive list) of the storage device would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
- Code for carrying out operations for embodiments may be written in any combination of one or more programming languages including an object oriented programming language such as Python, Ruby, R, Java, Java Script, Smalltalk, C++, C sharp, Lisp, Clojure, PHP, or the like, and conventional procedural programming languages, such as the “C” programming language, or the like, and/or machine languages such as assembly languages. The code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
- Reference throughout this specification to “one embodiment,” “an embodiment,” or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, appearances of the phrases “in one embodiment,” “in an embodiment,” and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment, but mean “one or more but not all embodiments” unless expressly specified otherwise. The terms “including,” “comprising,” “having,” and variations thereof mean “including but not limited to,” unless expressly specified otherwise. An enumerated listing of items does not imply that any or all of the items are mutually exclusive, unless expressly specified otherwise. The terms “a,” “an,” and “the” also refer to “one or more” unless expressly specified otherwise. The term “and/or” indicates embodiments of one or more of the listed elements, with “A and/or B” indicating embodiments of element A alone, element B alone, or elements A and B taken together.
- Furthermore, the described features, structures, or characteristics of the embodiments may be combined in any suitable manner. In the following description, numerous specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a thorough understanding of embodiments. One skilled in the relevant art will recognize, however, that embodiments may be practiced without one or more of the specific details, or with other methods, components, materials, and so forth. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of an embodiment.
- Aspects of the embodiments are described below with reference to schematic flowchart diagrams and/or schematic block diagrams of methods, apparatuses, systems, and program products according to embodiments. It will be understood that each block of the schematic flowchart diagrams and/or schematic block diagrams, and combinations of blocks in the schematic flowchart diagrams and/or schematic block diagrams, can be implemented by code. This code may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the schematic flowchart diagrams and/or schematic block diagrams block or blocks.
- The code may also be stored in a storage device that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the storage device produce an article of manufacture including instructions which implement the function/act specified in the schematic flowchart diagrams and/or schematic block diagrams block or blocks.
- The code may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the code which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
- The schematic flowchart diagrams and/or schematic block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of apparatuses, systems, methods and program products according to various embodiments. In this regard, each block in the schematic flowchart diagrams and/or schematic block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions of the code for implementing the specified logical function(s).
- It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the Figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more blocks, or portions thereof, of the illustrated Figures.
- Although various arrow types and line types may be employed in the flowchart and/or block diagrams, they are understood not to limit the scope of the corresponding embodiments. Indeed, some arrows or other connectors may be used to indicate only the logical flow of the depicted embodiment. For instance, an arrow may indicate a waiting or monitoring period of unspecified duration between enumerated steps of the depicted embodiment. It will also be noted that each block of the block diagrams and/or flowchart diagrams, and combinations of blocks in the block diagrams and/or flowchart diagrams, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and code.
- The description of elements in each figure may refer to elements of proceeding figures. Like numbers refer to like elements in all figures, including alternate embodiments of like elements.
-
FIG. 1A is a schematic block diagram illustrating one embodiment of anelectronic forum 100. Theelectronic forum 100 allows one ormore participants 120 to collaborate and share information online. In the depicted embodiment, theelectronic forum 100 includes aserver 105, anetwork 115, a plurality ofelectronic devices 110, and a plurality ofparticipants 120. In addition, theelectronic forum 100 may include one or more sets ofinformation permissions 200. Thenetwork 115 may be the Internet, a mobile telephone network, a Wi-Fi network, a wide-area network, a local area network, or combinations thereof. Theelectronic forum 100 may be an audio conference, a video conference, a virtual conference, and the like. - The
participants 120 collaborate and share forum information through theelectronic devices 110. The forum information may include audio, video, files, drawings, and/or presentations. Theelectronic devices 110 may communicate through thenetwork 115. In addition, theserver 105 may manage the exchanges of forum information in theelectronic forum 100. - Typically, each participant in the
electronic forum 100 is able to access all forum information that is shared in theelectronic forum 100. However, it may be advantageous to not share some forum information with someparticipants 120. For example, it may be critical to share confidential forum information with only a limited set ofparticipants 120 that are authorized to receive the confidential form information. The embodiments receive theinformation permissions 200 for theparticipants 120 and provide the forum information to eachparticipant 120 based on theinformation permissions 200. As result, eachparticipant 120 only receives forum information that theparticipant 120 should have access to. - In one embodiment, one or
more participants 120 may be categorized in agroup 125. In a certain embodiment, theparticipants 120 in thegroup 125 share a set ofinformation permissions 200. -
FIG. 1B is drawings of illustrating embodiments ofelectronic devices 110. In the depicted embodiment, a virtual-realityelectronic device 110 a, a mobile telephoneelectronic device 110 b, and a laptop computerelectronic device 110 c are shown. Otherelectronic devices 100 may be employed. Theelectronic devices 110 may exchange forum information including audio, video, files, drawings, and/or presentations. -
FIG. 2A is a schematic block diagram illustrating one embodiment of theinformation permissions 200. Theinformation permissions 200 specify theforum information 250 that eachparticipant 120 may receive from theelectronic forum 100. Theinformation permissions 200 maybe organized as a data structure in a memory. In the depicted embodiment, theinformation permissions 200 includes anaudio permission 201, avideo permission 203, afile share permission 205, adrawing permission 207, and apresentation permission 209. In addition, theinformation permissions 200 may include anaudio time stamp 221, avideo time stamp 223, afile share timestamp 225, a drawingtimestamp 227, and apresentation timestamp 229. In one embodiment, eachpermission 201/203/205/207/209 may have acorresponding timestamp 221/223/225/227/229. - The
audio permission 201 may be required to receive audio from theelectronic forum 100. Thevideo permission 203 may be required to receive video from theelectronic forum 100. Thefile share permission 205 may be required to receive a file from theelectronic forum 100. The drawingpermission 207 may be required to receive a drawing from theelectronic forum 100. Thepresentation permission 209 may be required to receive a presentation from theelectronic forum 100. - The
server 105 and/orelectronic device 110 may communicate the audio, the video, the file, the drawing, and/or the presentation in response to acorresponding permission 201/203/205/207/209 being set. For example,server 105 and/orelectronic device 110 may communicate the audio in response to theaudio permission 201 being set. - In one embodiment, the
server 105 and/orelectronic device 110 communicates the audio, the video, the file, the drawing, and/or the presentation in response to thecorresponding timestamp 221/223/225/227/229 preceding a current time. For example, theserver 105 and/orelectronic device 110 may communicate the video in response to thevideo timestamp 223 preceding the current time. - The
server 105 and/orelectronic device 110 may communicate the audio, the video, the file, the drawing, and/or the presentation in response to both acorresponding permission 201/203/205/207/209 being set and thecorresponding timestamp 221/223/225/227/229 preceding the current time. For example,server 105 and/orelectronic device 110 may communicate the presentation in response to both thepresentation permission 209 being set and thepresentation timestamp 229 preceding the current time. -
FIG. 2B is a schematic block diagram illustrating one embodiment offorum information 250. Theforum information 250 may be communicated between theelectronic devices 110 and/orserver 105 over thenetwork 115. Theforum information 250 maybe organized as data in one or more packets. In addition, theforum information 250 maybe organized as a data structure in a memory. In the depicted embodiment, theforum information 250 includes the audio 251, thevideo 253, afile 255, the drawing 257, and/or thepresentation 259. In addition, theforum information 250 may include acommand 270. - The audio 251 may include audio data from one or
more participants 120. Thevideo 253 may include video data from one ormore participants 120. Thefile 255 may comprise data organized in a file structure that is shared betweenparticipants 120. The drawing 257 may include bitmapped, vector, and the like graphic information that is generated by aparticipant 120 and rendered forother participants 120. Thepresentation 259 may be a presentation data structure that is presented by afirst participant 120 toother participants 120. - The
command 270 may be received by anelectronic device 110. Thecommand 270 may be received as a voice command. In addition, thecommand 270 may be received through the user interface as will be described hereafter. Thecommand 270 may specify and/or modify theinformation permissions 200. For example, theinformation permissions 200 may be received from afirst participant 120 as avoice command 270. In addition, theinformation permissions 200 may be received through the user interface. -
FIG. 3 is drawing illustrating one embodiment of auser interface 300. Theuser interface 300 may be presented to aparticipant 120 on a display of theelectronic device 110. In addition, theparticipant 120 may interact with theuser interface 300 using a keyboard, a pointing device, and the like. - In one embodiment, the
user interface 300 displaysinformation types 303 comprising theforum information 250 employed in a givenelectronic forum 100. In addition, theuser interface 300 may display theparticipants 120 and/orgroups 125 participating in theelectronic forum 100. In the depicted embodiment,participants 120 that are part of agroup 125 are only presented as part of thegroup 125. In an alternative embodiment,participants 120 that are part of agroup 125 are presented both individually and as part of the group. In a certain embodiment, both thegroup 125 and the participants of thegroup 125 are presented in theuser interface 300. - The
user interface 300 may receivepermission selections 305 for each combination ofinformation type 303 andparticipant 120 and/orgroup 125. Thepermissions selections 305 may specify whichparticipant 120 and/orgroup 125 may receive whichforum information 250. Thepermission selections 305 may set the correspondingpermissions 201/203/205/207/209. In addition, thepermission selections 305 may set the correspondingtimestamps 221/223/225/227/229 to a current time. In a certain embodiment, thepermission selections 305 may set the correspondingtimestamps 221/223/225/227/229 to a specified time. - In one embodiment, the
user interface 300 receives a single set ofinformation permissions 200 for each of the plurality ofparticipants 120. Theuser interface 300 may receive the single set ofinformation permissions 200 from an administrator. The administrator may be a designatedparticipant 120. - In a certain embodiment, instances of the
user interface 300 receiveinformation permissions 200 for each of the plurality ofparticipants 120 from each of the plurality ofparticipants 120. For example, a first instance of theuser interface 300 may receivefirst information permissions 200 from afirst participant 120 and the second instance of theuser interface 300 may receivesecond information permissions 200 from asecond participant 120. - In one embodiment, the
information permission 200 received from aparticipant 120 applies only to theforum information 250 originating from thatparticipant 120. For example, theinformation permission 200 received from afirst participant 120 may apply only to the audio 251,video 253, file 255, drawing 257, and/orpresentation 259 originating from thefirst participant 120. - In an alternative embodiment, the
information permission 200 received from aparticipant 120 applies to all theforum information 250 originating from allparticipants 120. In a certain embodiment, theinformation permission 200 received from theparticipant 120 applies only to theparticipants 120 as specified in theuser interface 300 by thepermissions selections 305. -
FIG. 4 is a schematic block diagram illustrating one embodiment of acomputer 400. Thecomputer 400 may be embodied each of theelectronic devices 110 and theserver 105. In the depicted embodiment, thecomputer 400 includes aprocessor 405, amemory 410, andcommunication hardware 415. Thememory 410 may include a semiconductor storage device, a hard disk drive, an optical storage device, or combinations thereof. Thememory 410 may store code. Theprocessor 405 may execute the code. Thecommunication hardware 415 may communicate with other devices such as thenetwork 115. -
FIG. 5 is a schematic flow chart diagram illustrating one embodiment of a foruminformation management method 500. Themethod 500 may receiveinformation permissions 200 for the plurality ofparticipants 120 in theelectronic forum 100 and provide theforum information 250 to eachparticipant 120 based on theinformation permissions 200. Themethod 500 may be performed by theprocessor 405. - The
method 500 starts, and in one embodiment, theprocessor 405 receives 501 theinformation permissions 200 for the plurality ofparticipants 120 in theelectronic forum 100. Theinformation permissions 200 may be received 501 from theuser interface 300. In one embodiment, theuser interface 300 generates thecommand 270 that is communicated to theserver 105. In addition, theinformation permissions 200 may be received 501 as avoice command 270. In one embodiment, theinformation permissions 200 are received 501 from an administrator. In addition, sets ofinformation permissions 200 may be received 501 from eachparticipant 120. - The
information permissions 200 may comprise theaudio permission 201, thevideo permission 203, thefile share permission 205, the drawingpermission 207, and/or thepresentation permission 209 for eachparticipant 120. In one embodiment, one ormore participants 120 are organized in agroup 125. A first set ofinformation permissions 200 may be assigned to thegroup 125. Theinformation permissions 200 for eachparticipant 120 in thegroup 125 may be theinformation permissions 200 for thegroup 125. - The
information permissions 200 may be received 501 at any time during theelectronic forum 100. For example, afirst participant 120 may communicate updatedinformation permissions 200 to theprocessor 405 before sharingconfidential forum information 200 with only specifiedparticipants 120. Updating theinformation permissions 250 may comprise updating acorresponding timestamp 221/223/225/227/229 with the current time if permission is granted and updating thecorresponding timestamp 221/223/225/227/229 with a null value if the permission is withdrawn. In addition, updating theinformation permissions 250 may comprise setting thecorresponding permission 201/203/205/207/209 if permission is granted and clearing thepermission 201/203/205/207/209 if the permission is withdrawn. - For example, the administrator may update the
drawing permission 207 for afirst participant 120 to withdraw thedrawing permission 207. Theserver 105 may record a null value to the drawingtimestamp 227 for thefirst participant 120. In addition, theserver 105 may clear thedrawing permission 207. As a result, thefirst participant 120 will subsequently not receive adrawing 257. Similarly, the administrator may update thedrawing permission 207 for thefirst participant 120 to grant thedrawing permission 207. Theserver 105 may record a current time to the drawingtimestamp 227 for thefirst participant 120. As a result, thefirst participant 120 will subsequently receive thedrawing 257. - The
processor 405 may provide 503 theforum information 250 to eachparticipant 120 based on theinformation permissions 200. Theaudio permission 201 may be required to receive audio 251 from theelectronic forum 100. Thevideo permission 203 may be required to receivevideo 253 from theelectronic forum 100. Thefile share permission 205 may be required to receive afile 255 from theelectronic forum 100. The drawingpermission 207 may be required to receive a drawing 257 from theelectronic forum 100. Thepresentation permission 209 may be required to receive apresentation 259 from theelectronic forum 100. - In one embodiment, the
server 205 communicates the audio 251, thevideo 253, thefile 255, the drawing 257, and/or thepresentation 259 in response to thecorresponding timestamp 221/223/225/227/229 preceding the current time. In addition, theserver 205 communicates the audio 251, thevideo 253, thefile 255, the drawing 257, and/or thepresentation 259 in response to thecorresponding permission 201/203/205/207/209 being set. Theprocessor 405 may further loop to receive 501subsequent information permissions 200. - The embodiments receive the
information permissions 200 and provide theforum information 250 based on theinformation permissions 200. As a result, an administrator and/or eachparticipant 120 may grant or restrictspecific forum information 250 forspecific participants 120. Thus,forum information 250 may be selectively withheld fromparticipants 120, facilitating the selective dissemination of information within theelectronic forum 100. A singleelectronic forum 100 may thus be used to selectively share theforum information 250 among a larger group ofparticipants 120 than could participate in theelectronic forum 100 if allparticipants 120 received thesame forum information 250. Thus the efficiency of theelectronic forum 100 and thecomputers 400 employed therein is improved using theinformation permissions 200. - Embodiments may be practiced in other specific forms. The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the invention is, therefore, indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.
Claims (20)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US16/575,130 US11238177B2 (en) | 2019-09-18 | 2019-09-18 | Multiuser information exchange management |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US16/575,130 US11238177B2 (en) | 2019-09-18 | 2019-09-18 | Multiuser information exchange management |
Publications (2)
Publication Number | Publication Date |
---|---|
US20210081563A1 true US20210081563A1 (en) | 2021-03-18 |
US11238177B2 US11238177B2 (en) | 2022-02-01 |
Family
ID=74869602
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/575,130 Active 2040-04-14 US11238177B2 (en) | 2019-09-18 | 2019-09-18 | Multiuser information exchange management |
Country Status (1)
Country | Link |
---|---|
US (1) | US11238177B2 (en) |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CA2515488C (en) * | 2003-02-10 | 2013-04-16 | Raindance Communications, Inc. | Methods and apparatus for providing egalitarian control in a multimedia collaboration session |
WO2017083980A1 (en) * | 2015-11-20 | 2017-05-26 | Genetec Inc. | Secure layered encryption of data streams |
US10992679B1 (en) * | 2016-07-01 | 2021-04-27 | Wells Fargo Bank, N.A. | Access control tower |
-
2019
- 2019-09-18 US US16/575,130 patent/US11238177B2/en active Active
Also Published As
Publication number | Publication date |
---|---|
US11238177B2 (en) | 2022-02-01 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP7351907B2 (en) | Online document sharing methods, devices, electronic devices and storage media | |
CN108173706B (en) | Service marking method, device and equipment under multi-service system | |
US9906756B2 (en) | Convergence of social enterprise and digital telephony | |
CN110413390A (en) | Thread task processing method, device, server and storage medium | |
CN111679990B (en) | Test data generation method and device, readable medium and electronic equipment | |
US10606688B2 (en) | Resolving conflicts between multiple software and hardware processes | |
US10992662B2 (en) | Enabling/disabling applications using face authentication | |
CN111931962A (en) | Information display method and device and electronic equipment | |
WO2016173303A1 (en) | Shared file processing method and device | |
US11902039B2 (en) | Interaction method and apparatus, and electronic device | |
US11934649B2 (en) | Scrollable real-time presentation document twin | |
CN109167819A (en) | Data synchronous system, method, apparatus and storage medium | |
GB2623225A (en) | Method, system, and apparatus for securely sharing video stream, and storage medium | |
US11238177B2 (en) | Multiuser information exchange management | |
US11848762B2 (en) | Live broadcast stream pushing method and apparatus, and electronic device | |
CN110990329B (en) | Federal computing high availability method, equipment and medium | |
US11277275B2 (en) | Device ranking for secure collaboration | |
US9910737B2 (en) | Implementing change data capture by interpreting published events as a database recovery log | |
US20150295964A1 (en) | Methods and systems for conducting an electronic device enhanced meeting | |
US20220050863A1 (en) | Capturing messages from a phone message exchange | |
US20220360463A1 (en) | Autonomous screenshare of dynamic magnification view without primary collaboration interruption | |
CN113885818A (en) | Display method and device and electronic equipment | |
CN113610525A (en) | Financial data processing method, device, equipment and medium based on block chain | |
US20160241657A1 (en) | Device delegation of push notification distribution | |
US11647098B2 (en) | System and method for providing real-time lockless parallel screen recording compliance enforcement to omni channel cloud systems |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: LENOVO (SINGAPORE) PTE. LTD., SINGAPORE Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:WANG, SONG;LI, JIAN;QIAN, MING;AND OTHERS;REEL/FRAME:050425/0042 Effective date: 20190916 |
|
FEPP | Fee payment procedure |
Free format text: ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: FINAL REJECTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE AFTER FINAL ACTION FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NOTICE OF ALLOWANCE MAILED -- APPLICATION RECEIVED IN OFFICE OF PUBLICATIONS |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: PUBLICATIONS -- ISSUE FEE PAYMENT VERIFIED |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |