US20140280955A1 - Controlling Electronically Communicated Resources - Google Patents
Controlling Electronically Communicated Resources Download PDFInfo
- Publication number
- US20140280955A1 US20140280955A1 US13/828,922 US201313828922A US2014280955A1 US 20140280955 A1 US20140280955 A1 US 20140280955A1 US 201313828922 A US201313828922 A US 201313828922A US 2014280955 A1 US2014280955 A1 US 2014280955A1
- Authority
- US
- United States
- Prior art keywords
- entities
- computing device
- entity
- communication
- management application
- 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.)
- Abandoned
Links
- 238000004891 communication Methods 0.000 claims abstract description 132
- 238000000034 method Methods 0.000 claims abstract description 44
- 230000004044 response Effects 0.000 claims abstract description 20
- 238000013475 authorization Methods 0.000 claims description 20
- 230000000246 remedial effect Effects 0.000 claims description 20
- 238000007726 management method Methods 0.000 description 225
- 230000015654 memory Effects 0.000 description 31
- 230000006870 function Effects 0.000 description 18
- 238000010586 diagram Methods 0.000 description 9
- 230000008569 process Effects 0.000 description 7
- 238000012986 modification Methods 0.000 description 6
- 230000004048 modification Effects 0.000 description 6
- 230000003287 optical effect Effects 0.000 description 6
- 238000005192 partition Methods 0.000 description 6
- 238000012545 processing Methods 0.000 description 5
- 238000009877 rendering Methods 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 3
- 238000012423 maintenance Methods 0.000 description 3
- 241000700605 Viruses Species 0.000 description 2
- 230000009471 action Effects 0.000 description 2
- 238000013459 approach Methods 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 2
- 230000001413 cellular effect Effects 0.000 description 2
- 238000013500 data storage Methods 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 230000008520 organization Effects 0.000 description 2
- 230000002093 peripheral effect Effects 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 230000002155 anti-virotic effect Effects 0.000 description 1
- 230000001143 conditioned effect Effects 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 230000001815 facial effect Effects 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 238000005259 measurement Methods 0.000 description 1
- 210000001525 retina Anatomy 0.000 description 1
- 230000002207 retinal effect Effects 0.000 description 1
- 238000012552 review Methods 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 238000013024 troubleshooting Methods 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
- H04L63/104—Grouping of entities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
- H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
- H04L63/0435—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload wherein the sending and receiving network entities apply symmetric encryption, i.e. same key used for encryption and decryption
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
- H04L63/102—Entity profiles
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
- H04L63/107—Network architectures or network communication protocols for network security for controlling access to devices or network resources wherein the security policies are location-dependent, e.g. entities privileges depend on current location or allowing specific operations only from locally connected terminals
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/20—Network architectures or network communication protocols for network security for managing network security; network security policies in general
-
- 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/10—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM]
- G06F21/101—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM] by binding digital rights to specific entities
- G06F21/1015—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM] by binding digital rights to specific entities to users
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/2143—Clearing memory, e.g. to prevent the data from being stolen
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/06—Network architectures or network communication protocols for network security for supporting key management in a packet data network
- H04L63/061—Network architectures or network communication protocols for network security for supporting key management in a packet data network for key exchange, e.g. in peer-to-peer networks
Definitions
- Electronic content provided via a network may be used to enhance collaborative projects between multiple users or to provide electronic content to a widespread audience.
- video content and other multimedia presentations can be used to provide instructions, augment lectures, and otherwise enhance projects involving multiple participants.
- Controlling access to and distribution of electronic content and other enterprise resources in a networked environment may ensure that only authorized users and network-connected devices may gain access to sensitive information.
- Systems and methods are desirable for temporarily controlling independently operated computing devices to provide electronic content to users of the computing devices.
- a management application identifies multiple entities for communicating electronic content.
- the management application determines that at least a subset of entities required for communicating the electronic content is available for electronic communication.
- the management application authorizes communication of at least some of the electronic content among the entities in response to determining that the required subset of entities is available for electronic communication.
- a management application prevents unauthorized access to an electronic meeting.
- the management application identifies multiple entities authorized for electronic communication among one another.
- the management application detects an additional entity that lacks an authorization for electronic communication among the entities.
- the management application restricts a communication of at least some electronic content among at least some of the entities based on detecting the additional entity that lacks the authorization.
- a system identifies multiple entities required for authorizing at least one of multiple communication features for communicating electronic content. At least one additional communication feature is available in an absence of at least one of the required entities. The system determines that each required entity is available for electronic communication. The system authorizes performance of the at least one communication feature based on determining that each entity is available for electronic communication.
- FIG. 1 is a block diagram of a networked environment according to some embodiments.
- FIG. 2 is a modeling diagram depicting resources accessed by a client application and a management application for authorizing the use of resources by a computing device, according to some embodiments.
- FIG. 3 is a modeling diagram depicting an example flow of communications among a management application and multiple computing devices accessing an electronic meeting, according to some embodiments.
- FIG. 4 is a modeling diagram depicting an example flow of communications among a management application, multiple computing devices accessing an electronic meeting, and an unauthorized entity or device according to some embodiments.
- FIG. 5 is a flow chart illustrating an example method for controlling resources communicated among computing devices according to some embodiments.
- FIG. 6 is a flow chart illustrating an example method for restricting access to resources communicated among computing devices based on the presence of an unauthorized entity according to some embodiments.
- Computer-implemented systems and methods are disclosed for a management application controlling applications, files, and other resources being accessed, executed, and/or otherwise used at computing devices via an electronic meeting and/or other forum for electronic communication.
- the board meeting may be scheduled for a given conference room within a building during a given time period. Individuals may participate in the board meeting in person or remotely. Individuals participating in the board meeting may use mobile computing devices, such as tablet computers and/or smart phones, to access board related documents that may be needed for the meeting.
- the board related documents may be shared to the mobile computing devices via an electronic meeting session. It may be desirable to prevent sharing of the board related documents until a quorum of board members and/or specific members of the board, such as an executive committee, join the meeting, either in person or remotely.
- a management application can determine the number of the board members and/or the specific board members present in the meeting room and/or accessing the electronic meeting for sharing the board related documents.
- the management application can determine that a quorum is available and/or the specific members of the board are present based on those members accessing the electronic meeting.
- the management application can authorize the sharing of the board related documents via the electronic conference based on the quorum being available and/or the specific members of the board being present, thereby ensuring that no less than the required meeting participants are available at a certain time and place to receive the content.
- the management application can also detect the either the physical presence of unauthorized computing devices and/or attempts to access the electronic meeting by unauthorized users (e.g., non-board members).
- the management application can restrict sharing of the board related documents via the electronic meeting to prevent the unauthorized computing devices and/or unauthorized users from obtaining the documents via the electronic meeting.
- a management application can control the use of resources by computing devices via an electronic meeting and/or other forms of electronic communication.
- the management application can identify multiple entities required for communicating electronic content.
- An entity can include a logical representation of any participant in a meeting.
- the management application may identify a given entity based on any suitable criteria.
- suitable criteria include (but are not limited to) credentials associated with a particular user (such as, but not limited to, a user name and/or other identifier), one or more identifiers associated with a computing device used to access the electronic meeting (such as, but not limited to, a hardware identifier or network address of the computing device), and/or based on a pairing of a user credential and a device identifier.
- the required entities may be a subset of all entities authorized to access the electronic meeting. In the absence of all of the required entities, communication of electronic content via the electronic meeting may be restricted and/or disallowed.
- the management application can determine that each required entity is physically present in the meeting room (assuming an in-person meeting is being held) and/or accessing the electronic meeting (either from within the meeting room and/or a remote location).
- the management application can authorize communication of the electronic content among the required entities and other authorized entities via the electronic meeting based on determining that each required entity is present in the meeting room and/or accessing the electronic meeting. It should be understood that in some cases, the management application can authorize communication of the electronic content among the required entities and other authorized users even if one of the required users is not accessing the electronic meeting, as long as that required user is physically present in the meeting room.
- an electronic meeting is used to refer to an exchange of information between at least two entities executed via a telecommunication system.
- An electronic meeting may include at least one entity, such as (but not limited to) moderator entities, that are authorized to perform at least one function during the electronic meeting that are unavailable to other entities accessing the meeting.
- An electronic meeting may permit the exchange of electronic content, such as documents, multimedia presentations, text messages, and the like.
- at least one restriction can be placed on the exchange of electronic content during the meeting.
- Non-limiting examples of an electronic meeting include telephone conferences, internet telephone conferences, videoconferences, web conferences, and the like.
- Electronic content is used to refer to any type of resources that can accessed, be rendered for display, and/or otherwise used at a computing system and/or other electronic device.
- Electronic content can include text and/or multimedia files, such as images, video, audio, and/or any combination thereof.
- Electronic content can also include application software that is designed to perform at least one specific task at a computing system.
- each entity can correspond to and/or otherwise be associated with a respective computing device.
- the management application can determine whether each computing device corresponding to a required entity is authorized to access the electronic meeting. Determining that each computing device is authorized to access the electronic meeting can include determining that the computing device is compliant with at least one rule that controls access to the electronic content by computing devices. For example, a rule may require that software such as a mobile device management module and/or up-to-date antivirus software be installed on the computing device as a prerequisite to granting access to resources shared via the electronic meeting.
- determining that each entity is authorized for accessing the electronic meeting may include determining that at least some of the computing devices corresponding to the required entities are positioned in a specific geographical location.
- the management application may require that wireless devices corresponding to required entities be positioned in a particular conference room of an office building and/or that the wireless devices be positioned within a given proximity to one another and/or a given distance from non-authorized wireless devices.
- the management application can determine that the computing devices are positioned in a specific geographical location by communicating with a computing device and/or system configured for detecting the computing devices, such as (but not limited to) a sensor system, a global positioning system, a telecommunication system, etc.
- the management application may be able to determine locations of the computing devices by communicating with the computing devices themselves (e.g., but requiring the computing devices to transmit its geospatial coordinates and/or other positioning information to the management application).
- the management application may restrict communication of electronic content based on at least one triggering condition.
- the triggering conditions may include a required entity leaving a meeting, a computing device corresponding to a required entity leaving a common geographical location, an unauthorized entity accessing and/or attempting to access the electronic meeting, and/or an unauthorized computing device being positioned within a given proximity to one and/or more of the computing devices corresponding to authorized entities.
- restricting the communication of electronic content can include restricting the participating entities to communication of a subset of electronic content. For example, an electronic meeting that involves sharing both publicly available documents and secret and/or otherwise sensitive documents may be restricted to sharing only the publicly available documents in the absence of all required entities and/or upon detecting the presence of an unauthorized entity.
- the presence of an unauthorized entity can include, for example, the unauthorized entity accessing and/or attempting to access the electronic meeting and/or a computing device corresponding to the unauthorized entity being positioned in proximity to computing devices corresponding to authorized entities.
- restricting the communication of electronic content can include barring any communication of electronic content in the absence of all required entities and/or the presence of an unauthorized entity.
- the management application may authenticate each entity accessing the electronic meeting based on authentication data provided by a client application executed at a computing device corresponding to the entity.
- authentication data is used to refer to any data used by an application to verify the identity of an entity and/or approve access to a resource provided via the application.
- authentication data can include information provided by the entity. Non-limiting examples of authentication data provided by an entity include a password, a personal identification number, at least one answer to at least one secret question, a token, and the like.
- authentication data can include biometric information associated with the entity. Non-limiting examples of biometric information associated with the entity can include the entity's voice, DNA, handprint, iris and/or retinal scan, and the like.
- the management application can authorize communication of the electronic content based on secondary authentication data generated from authentication data provided by each of the required entities.
- generating secondary authentication data can include combining the authentication data received from the required entities.
- the management application may concatenate and/or otherwise join a group of passwords received from the required entities to form a combined password. The combined password may be used to verify that the communication of electronic content during the electronic meeting is authorized.
- generating secondary authentication data from authentication data provided by required entities can include generating authentication data that is different from the separate authentication data received from the required entities.
- the management application may receive a personal identification number from each of the required entities.
- the management application can perform at least one mathematical operation and/or other algorithms on the received personal identification numbers.
- the output of the mathematical operation(s) and/or other algorithm can be a new identification number.
- the new identification number may be used to verify that the electronic content can be communicated during the electronic meeting.
- the management application can authorize communication of electronic content by decrypting the electronic content with an encryption key collectively provided by the required entities.
- the management application can receive a respective portion of the encryption key from each required entity and/or from a computing device corresponding to the required entity.
- the management application can combine the portions to obtain the encryption key.
- the management application can decrypt the electronic content with the encryption key.
- the management application can restrict communication of electronic content via an electronic meeting in response to detecting an unauthorized entity.
- detecting the unauthorized entity can include determining that a computing device corresponding to the unauthorized entity (e.g., a user that is not authorized to access the meeting) is positioned in the same geographical location as other computing devices authorized to access the meeting.
- the management application can determine that a computing device is not authorized to access the electronic meeting, regardless of whether the operator of the computing device is authorized to access the meeting. For example, the management application can determine that a computing device is not authorized to access the electronic meeting based on the computing device being non-compliant with at least one rule governing access to the electronic content by computing devices.
- the management application can perform at least one remedial action in response to detecting an unauthorized computing device accessing an electronic meeting, attempting to access the electronic meeting, and/or being positioned in the vicinity of other computing devices authorized to access the electronic meeting.
- the remedial action includes transmitting a software update to the computing device.
- the software update is configured to bring the computing device into compliance with at least one rule governing access to resources shared via the electronic meeting.
- the remedial action includes transmitting a command to a client application executing on the computing device.
- the command directs the client application to erase some or all content and/or applications from the computing device (i.e., perform a partial or total “device wipe”) and/or to disable certain functions of the computing device and/or its applications.
- the remedial action includes transmitting a command directing the client application to lock the computing device.
- the management application can detect the unauthorized entity based on the unauthorized entity unsuccessfully attempting to access the electronic meeting. In one non-limiting example, the management application can determine that authentication data provided by the entity is invalid. The management application may execute at least one remedial action in response to a threshold number of failed attempts by an entity to access the meeting using invalid authentication data. In another non-limiting example, the management application can determine that the entity is not included on a listing of the entities authorized to access the electronic meeting. In another non-limiting example, the management application can determine that a request from the entity to access the electronic meeting has a timestamp outside a designated time period for the electronic meeting.
- a computing device can include any suitable arrangement of components that provide a result conditioned on at least one input.
- Suitable computing devices include multipurpose microprocessor-based computer systems accessing stored software that programs and/or configures the computing system from a general-purpose computing apparatus to a specialized computing apparatus implementing one or more aspects of the present subject matter.
- Any suitable programming, scripting, and/or other type of language and/or combinations of languages may be used to implement the teachings contained herein in software to be used in programming and/or configuring a computing device. Aspects and features from each embodiment disclosed can be combined with any other embodiment.
- FIG. 1 is a block diagram depicting example computing systems for implementing certain embodiments.
- the example computing systems include a server system 102 and at least one example computing device 104 in communication via a network 106 .
- a general discussion of the components of the server system 102 and the computing device 104 is provided below.
- the server system 102 may include at least one server computer and/or any other system providing capabilities for managing access to resources and/or distributing resources to computing device(s) 104 .
- multiple server systems 102 may be employed that are configured in at least one server bank, computer banks, and/or other arrangements.
- multiple server systems 102 may be configured to provide a cloud computing resource, a grid computing resource, and/or any other distributed computing arrangement.
- Such server systems 102 may be located in a single installation or may be distributed among many different geographic locations.
- the server system 102 is referred to herein in the singular. Even though the server system 102 is referred to in the singular, it is understood that multiple server systems 102 may be employed in the arrangements as descried herein.
- the computing device 104 can include any suitable computing device and/or system for communicating via the network 106 and executing at least one application.
- a computing device 104 include a desktop computer, a laptop computer, a personal digital assistant, a cellular telephone, a set-top box, a music player, a web pad, a tablet computer system, a game console, and/or another device with like capability.
- the computing device 104 may be configured to execute various applications.
- the computing device 104 may be configured to execute applications such as web browsing applications, email applications, instant messaging applications, and/or other applications capable of receiving and/or rendering resources 202 on a display 136 associated with the computing device 104 .
- the server system 102 includes a processor 108 and the computing device 104 includes a processor 118 .
- Each of the processors 108 , 118 may be a microprocessor, an application-specific integrated circuit (“ASIC”), a state machine, and/or other suitable processing device.
- the processors 108 , 118 may be of electrical and/or of some other available construction.
- Each of the processors 108 , 118 can include any number of computer processing devices, including one.
- Each of the processors 108 , 118 can be communicatively coupled to a computer-readable medium, such as the memories 110 , 120 , respectively.
- Each of the processors 108 , 118 can execute computer-executable program instructions and/or accesses information respectively stored in the memory 110 of the server system 102 and in the memory 120 of the computing device 104 .
- Each of the memories 110 , 120 can include a computer-readable medium and/or other memory device.
- a computer-readable medium and/or other memory device can include both volatile and nonvolatile memory and data storage components. Volatile components are those that do not retain data values upon loss of power. Nonvolatile components include memory components that retain data upon a loss of power.
- a computer-readable medium may include (but is not limited to) an electronic, optical, magnetic, and/or other storage device capable of providing a processor with computer-readable instructions.
- RAM may include, for example, static random access memory (“SRAM”), dynamic random access memory (“DRAM”), or magnetic random access memory (“MRAM”) and other such devices.
- ROM may comprise, for example, a programmable read-only memory (“PROM”), an erasable programmable read-only memory (“EPROM”), an electrically erasable programmable read-only memory (“EEPROM”), or other like memory device.
- PROM programmable read-only memory
- EPROM erasable programmable read-only memory
- EEPROM electrically erasable programmable read-only memory
- the processor 108 and the memory 110 of the server system 102 may be communicatively coupled to a local interface 112 .
- the processor 118 and the memory 120 of the computing device 104 may be communicatively coupled to a local interface 122 .
- a local interface can include, for example, a data bus with an accompanying address/control bus or other bus structure.
- One or more of the processors 108 , 118 may represent multiple processing devices and one or more of the memories 110 , 120 may represent multiple memory devices that operate in parallel processing circuits, respectively.
- one or more of the local interfaces 112 , 122 may include an appropriate network that facilitates communication between any two of the multiple processors and/or between any two of the multiple memory devices.
- the local interfaces 112 , 122 may comprise additional systems designed to coordinate this communication, including, for example, performing load balancing.
- the computing device 104 may also include a number of external and/or internal devices such as a mouse, a keyboard, a display, audio speakers, one or more microphones, and/or any other input and/or output devices 130 .
- the computing device 104 may include and/or be in data communication with a display device 128 .
- a non-limiting example of a display device 128 is a computer monitor or computer screen, such as a touch screen.
- FIG. 1 depicts the display device 128 as a separate device coupled to the computing device 104 , the display device 128 can be integrated into the computing device 104 .
- the computing device 104 can also include at least one communication component (not shown in FIG. 1 ).
- One of the communication components can include a wired network connectivity component such as, for example, an Ethernet network adapter, a modem, and/or the like.
- the computing device 104 may further include a wireless network connectivity interface, for example, a Peripheral Component Interconnect (“PCI”) card, a Universal Serial Bus (“USB”) interface, a Personal Computer Memory Card International Association (“PCMCIA”) card, Secure Digital Input-Output (“SDIO”) card, NewCard, Cardbus, a modem, a wireless radio transceiver, and/or the like.
- PCI Peripheral Component Interconnect
- USB Universal Serial Bus
- PCMCIA Personal Computer Memory Card International Association
- SDIO Secure Digital Input-Output
- NewCard NewCard, Cardbus
- modem a wireless radio transceiver, and/or the like.
- the computing device 104 may be operable to communicate via wired connection with the server system
- Instructions stored in the memory 110 of the server system 102 and executable by its processor 108 can include a management application 114 and/or other applications.
- the management application 114 can include at least one function for controlling resources executed at computing devices such as computing device 104 , as described in detail below.
- Certain data may be stored in a data store 116 of the memory 110 that is part of and/or otherwise accessible to the server system 102 .
- the illustrated data store 116 may be representative of a multiple data stores, as can be appreciated.
- the data stored in the data store 116 for example, is associated with the operation of certain applications and/or functional entities described herein.
- the data store 116 may utilize strong encryption standards to protect the resources 202 from unauthorized access.
- the data store 116 may utilize Standard Hash Algorithm (“SHA-1”) and/or a similar strong encryption standard that may be utilized for server-side data storage.
- SHA-1 Standard Hash Algorithm
- Instructions stored in the memory 120 of the computing device 104 and executable by its processor 118 can include a client application 124 and/or other applications.
- An application capable of receiving and/or rendering resources on a display device 128 is generally referred to herein as a “client application” 124 .
- Certain data may be stored in a data store 126 of the memory 120 that is part of and/or otherwise accessible to the computing device 104 .
- the illustrated data store 126 may be representative of multiple data stores.
- the data stored in the data store 126 may be associated with the operation of certain applications and/or functional entities described herein.
- computer-executable program instructions is used to refer to a program file that is in a form that can ultimately be run by a processor.
- Examples of computer-executable program instructions may be, for example, a compiled program that can be translated into machine code in a format that can be loaded into a random access portion of a memory and executed by a processor, source code that may be expressed in proper format such as object code that can be loaded into a random access portion of a memory and executed by a processor, source code that may be interpreted by another executable program to generate instructions in a random access portion of a memory and executed by a processor, and the like.
- the instructions may comprise processor-specific instructions generated by a compiler and/or an interpreter from code written in any suitable computer-programming language, including, for example, C, C++, C#, Visual Basic, Java, Python, Perl, JavaScript, and ActionScript.
- An executable program may be stored in any portion and/or component of a memory device such as, for example, RAM, ROM, a hard drive, solid-state drive, USB flash drive, memory card, optical disc such as compact disc (“CD”) and/or digital versatile disc (“DVD”), floppy disk, magnetic tape, and/or other memory components.
- the network 106 facilitates communication between a server system 102 and at least one computing device 104 .
- the network 106 can include any suitable architecture for providing communication channels between the computing device 104 and the server system 102 .
- a communication channel can include any suitable means capable of communicating signals between the computing device 104 and a server system 102 .
- Non-limiting examples of the network 106 include any type of wired network, wireless network, and/or a combination of wired and wireless networks.
- a wireless network may be a wireless local area network (“WLAN”), a wireless wide area network (“WWAN”), and/or any other type of wireless network now known and/or later developed.
- WLAN wireless local area network
- WWAN wireless wide area network
- the network 106 may be and/or include the Internet, intranets, extranets, microwave networks, satellite communications, cellular systems, personal communication services (“PCS”), infrared communications, global area networks, and/or other suitable networks, etc., and/or any combination of two or more such networks.
- the Internet intranets, extranets, microwave networks, satellite communications, cellular systems, personal communication services (“PCS”), infrared communications, global area networks, and/or other suitable networks, etc., and/or any combination of two or more such networks.
- FIG. 2 is a modeling diagram depicting resources accessed by the client application 124 and/or the management application 114 for authorizing the use of resources 202 by the computing device 104 , according to some embodiments.
- the client application 124 can include any software configured for communicating with the management application 114 and/or remotely managing the computing device 104 .
- the client application 124 may access information from its associated data store 126 such as a device profile 212 , at least one of the credentials 214 , a device identifier 216 , and other data.
- the device profile 212 may include hardware, software, and security attributes that describe and/or otherwise identify the computing device 104 .
- the device profile 212 may represent hardware specifications of the computing device 104 , version and configuration information of various software programs and hardware components installed on the computing device 104 , transport protocols enabled on the computing device 104 , version and usage information of various other resources stored on the computing device 104 , and/or any other attributes associated with the state of the computing device 104 . Additionally, the device profile 212 may include data indicating a date of a last virus scan of the computing device 104 , a date of a last access by an administrator entity, a date of a last access by the server system 102 , a date of a last service by an administrator entity, and/or any other data indicating a date of last maintenance.
- the credentials 214 may uniquely identify the user and/or other entity authorized to operate the computing device 104 .
- the credentials 214 may include a username, a password, and/or biometric data related to facial recognition, retina recognition, fingerprint recognition, and the like.
- the device identifier 216 may uniquely identify the computing device 104 .
- the device identifier 216 may include a software identifier, a hardware identifier, and/or a combination of software and hardware identifiers.
- the device identifier 216 may be a unique hardware identifier such as a Globally Unique Identifier (“GUID”), Universally Unique Identifier (“UUID”), Unique Device Identifier (“UDID”), serial number, Internationally Mobile Equipment Identity (“IMEI”), Wi-Fi Media Access Control (“MAC”) address, Bluetooth MAC address, a processing device identifier, and/or the like, and/or any combination of two or more such hardware identifiers.
- the device identifier 216 may additionally or alternatively be represented by a unique software identifier such a token and/or certificate, based at least in part on the aforementioned unique hardware identifiers.
- the client application 124 may be executed to transmit requests to access resources 202 stored at and/or accessible via the server system 102 .
- the client application 124 may be a secure container program that may be authorized to receive and render selected resources 202 , as described herein.
- the client application 124 may be a plug-in and/or additional software module for a browser and/or other application configured to be executed as described herein.
- the client application 124 and/or another application on a computing device 104 managed by the client application 124 may access the resources 202 via a graphical interface 210 or other suitable interface rendered on the display device 128 .
- the resources 202 may be presented in a graphical interface 210 by decompressing compressed files and presenting the uncompressed files, by mounting disk image files and presenting the mounted image files, by running executable files and presenting the executed files, by enabling a data search of the resources 202 and presenting the featured output in a user interface, by calling on another application on the computing device 104 to respond to data links contained within the resources 202 , and/or by transmitting a part and/or the whole of the resources 202 to another application on the computing device 104 .
- a client application 124 may be executed to present a single resource 202 .
- a client application 124 may be executed to present a series of resources 202 in a comprehensive manner.
- a non-limiting example of presenting a series of resources 202 in a comprehensive manner is presenting photograph files in a slideshow presentation.
- the client application 124 may be executed to render an environment that presents multiple resources 202 in a single view, such as a category-based tree and/or outline format, based at least in part on a resource qualifier associated with the resources 202 .
- the client application 124 may also facilitate the modification of resources 202 provided by the management application 114 and the modification of data associated with the provided resources 202 , if the computing device 104 and/or its user are authorized to perform such actions.
- the client application 124 may include functionality for adding content to the existing resources 202 , removing content from the existing resources 202 , altering the content of existing resources 202 , and/or the like, and/or any combination of manipulations of the resources 202 .
- the client application 124 may further be executed to add new resources 202 to be hosted by the server system 102 , if authorized.
- a user having administrator-level credentials 214 may interact with an I/O device 130 to manipulate the graphical interface 210 and thereby generate instructions to transfer copies of resources 202 locally stored on the computing device 104 to the server system 102 to be included in the data store 116 .
- the user of the computing device 104 may initiate upload of at least one of the resources 202 via the graphical interface 210 rendered by the client application 124 , as can be appreciated.
- the user may indicate approved resource-grouping identifiers 206 for identifying groups of entities and/or devices that are permitted to access the uploaded resource 202 and specify rules 207 that may require compliance by a requesting entity in order to grant access to the uploaded resource 202 by the requesting entity, as will be described.
- a user without administrator-level credentials 214 may manipulate the graphical interface 210 to transfer local copies of personal resources 202 to the server system 102 .
- resources qualifiers associated with the personal resources 202 may be configured by default to restrict access by any other user.
- a management function of the client application 124 can include optionally restricting access to the resources 202 by other applications executed by the computing device 104 , thereby preventing access to the resources 202 from an application other than the client application 124 .
- the client application 124 may monitor network traffic between the computing device 104 and the server system 102 .
- the client application 124 may identify from the network traffic any data being transmitted between an application executed by the computing device 104 other than the client application 124 and the server system 102 .
- the client application 124 may determine whether a resource 202 is being provided to an application other than the client application 124 executed by the computing device 104 .
- the client application 124 may intercept and/or block the incoming resource 202 .
- the client application 124 may allow the intercepted resource 202 to be accessible to the user via a graphical interface 210 rendered by the client application 124 . In some embodiments, the client application 124 may deny access to the intercepted resource 202 by any other application on the computing device 104 . Additionally, the client application 124 may be executed to call on other services associated with the resources 202 that are executed on the server system 102 and/or another server and/or device accessible to the client application 124 , for instance, a technical support service that may be executed on the server system 102 .
- Certain applications and/or other functionality may be executed in the server system 102 according to some embodiments.
- the components executed on the server system 102 include the management application 114 and other applications, services, processes, systems, engines, and/or functionality not disclosed in detail herein.
- the management application 114 is executed to provide resources 202 stored in the data store 116 and/or provide access to resources accessible by the server system 102 .
- the management application 114 may also accept new resources 202 provided by the user of the computing device 104 , and previously provided resources 202 modified by the user of the computing device 104 , as will be described.
- the management application 114 can also be executed to communicate at least one command to the client application 124 for managing the computing device 104 .
- the data store 116 may include resources 202 , resource-grouping identifiers 203 , and/or other data.
- the resource-grouping identifiers 203 may represent unique identifiers for previously determined resource groupings and are used to determine which resources 202 are served up to the user of the computing device 104 , as will be described.
- a resource grouping may relate to organizational groups, organizational roles, geographic locations, and/or any other type(s) of grouping(s) that require access to a type of resource.
- Each resource grouping identifier 203 may be associated with a pairing of at least one of multiple approved credentials 204 and at least one of multiple approved device identifiers 205 .
- each combination of approved credentials 204 and approved device identifiers 205 may be associated with more than one of the resource-grouping identifiers 203 . Additionally, the pairing of approved credentials 204 and approved device identifiers 205 may be associated with a user's organizational role and/or capacity. For instance, the pairing of approved credentials 204 and the approved device identifiers 205 may be predetermined by a technical services administrator and/or other administrative entity. In some embodiments, the pairing of approved credentials 204 and the approved device identifiers 205 may be automatically associated with the resource-grouping identifiers 203 based at least upon a user's pay grade, organizational level, status within the organization, and/or any other organizational factor.
- Each resource 202 may be associated with a listing of approved resource-grouping identifiers 206 and at least one of the rules 207 .
- the listing of approved resource-grouping identifiers 206 includes at least some of the resource-grouping identifiers 203 that regulate access to the respective resource 202 .
- the listing of approved resource-grouping identifiers 206 may be predetermined by an administrator entity. For instance, the administrator entity may specify which of the resource-grouping identifiers 203 are permitted access to a respective at least one of the resources 202 .
- rules 207 may regulate how an entity having a combination of the appropriate credentials 214 and device identifier 216 may access the respective resource 202 .
- the rules 207 may describe a required and/or a permitted state that an accessing computing device 104 may satisfy in order for the computing device 104 to be permitted access to the resource 202 .
- rules 207 may include (but are not) limited to hardware requirements, software requirements, configuration requirements, maintenance requirements of a computing device, and/or requirements related to the resource 202 .
- hardware requirements may include requirements associated with a processor of the computing device 104 , memory, power supply, external storage, peripherals, and/or the like.
- Software requirements may include requirements associated with the operating system type and version, operating system authenticity and jailbreak/rooted status, installed application types and versions, and/or the like.
- Configuration requirements may include requirements associated with the configuration of the hardware, software, data encryption methods, transport protocols, and/or the like.
- Maintenance requirements may include requirements associated with the date of last virus scan for the computing device 104 , the date of the last access of the computing device 104 by an administrative entity, the date of last communication between the computing device 104 and the server system 102 , the date of last tune-up of the computing device 104 , and/or the like.
- Requirements related to the resource 202 may include whether the resources 202 may be rendered while the computing device 104 is offline and/or not in communication with the management application 114 , whether to permit synchronization of the resources 202 with a remote data store, whether to restrict the resources 202 from being forwarded, whether to permit storing resources 202 locally on the computing device 104 , and/or the like.
- the resources 202 and rules 207 may be stored on another data store accessible to the computing device 104 and/or other storage facility in data communication with the server system 102 , such as an internal email server, a web-based email server, an internal file server, a third-party hosted file server, a cloud-based server, and/or a cached local data store on the computing device 104 .
- Each resource 202 may be associated with at least one of the resource qualifiers 208 .
- a resource qualifier 208 may be and/or include metadata that describes and/or regulates the use of a respective at least one of the resources 202 .
- a resource qualifier 208 may include categories/sub-categories to which at least one of the resources 202 belong, an indication that at least one of the resources 202 are considered favorites, an indication of whether at least one of the resources 202 are privately owned, publicly owned, and/or enterprise-owned, an indication of whether at least one of the resources 202 are confidential, an indication of whether at least one of the resources 202 are password protected, an indication of the historical version of at least one of the resources 202 , a description of at least one of the resources 202 , at least one comment regarding at least one of the resources 202 , an indication of the size and format of at least one of the resources 202 , an indication of the download priority associated with at least one of the resources 202 , an indication of the expiration date associated
- a user and/or other entity operating a computing device 104 may wish to access resources 202 stored on the server system 102 .
- the user may manipulate a graphical interface 210 rendered by the client application 124 to transmit a request 218 for accessing at least one of the resources 202 on the server system 102 .
- the user may provide credentials 214 , such as, a unique user name, a password, biometric data, and/or other types of credentials 214 to request access to the server system 102 .
- the client application 124 may transmit the request 218 to the management application 114 .
- the request 218 may include the credentials 214 provided by the user, the device identifier 216 that uniquely identifies the computing device 104 , and/or any other relevant information.
- the management application 114 and/or another service provided by the server system 102 receives the request 218 and determines whether the user is authorized to access the resources 202 from the computing device 104 .
- the management application 114 may determine that the user is authorized to access the resources 202 from the computing device 104 based on the credentials 214 and the device identifier 216 provided with the request 218 .
- the server system 102 determines which of the resources 202 to provide to the computing device 104 .
- the management application 114 determines which resources 202 to provide based on resource-grouping identifiers 203 associated with each resource 202 . For instance, the management application 114 may determine which resource-grouping identifiers 203 are associated with the pairing of credentials 214 and the device identifier 216 included in the request 218 .
- the management application 114 parses the listing of approved credentials 204 and the listing of approved device identifiers 205 of each resource grouping identifier to determine whether the respective resource grouping identifier is associated with both the credentials 214 and the device identifier 216 .
- the management application 114 may identify a resource 202 to provide to the computing device 104 based on the determined resource-grouping identifiers 203 .
- the management application 114 identifies at least one of the resources 202 associated with each one of the determined resource-grouping identifiers 203 .
- the management application 114 identifies a resource 202 that is associated with the determined resource-grouping identifiers 203 .
- the management application 114 identifies the resource 202 if it is associated with a threshold number of the resource-grouping identifiers 203 .
- the management application 114 may provide the identified resources 202 to the user of the computing device 104 .
- the management application 114 may additionally determine whether the computing device 104 from which the user requested access to the resources 202 complies with the rules 207 associated with each one of the identified resources 202 . For example, the management application 114 may determine whether the device profile 212 describing the state of the computing device 104 complies with the rules 207 of each identified resource 202 . As discussed above, the device profile 212 may include hardware specifications of the computing device 104 , software specifications of the computing device 104 , version information of various other components of the computing device 104 , and/or any other information profiling the computing device 104 .
- the management application 114 may provide each identified resource 202 to the user if the computing device 104 complies with all of, or at least a portion of, the rules 207 associated with each of the identified resources 202 . Additionally, in some embodiments, the management application 114 may provide the identified resource(s) 165 to the user if the computing device 104 complies with at least a threshold number of the rules 207 associated with each of the identified resources 202 .
- the management application 114 may be further executed to transmit the identified resources 202 to the computing device 104 .
- the management application 114 may automatically transmit the identified resources 202 to the computing device 104 .
- the management application 114 may make the identified resources 202 available for download by the computing device 104 based on a resource qualifier associated with the respective resource 202 .
- the resource qualifier may indicate the respective resource 202 be made available for download to the computing device 104 .
- the user may transmit a request to the management application 114 to download the respective resource 202 .
- the state of the computing device 104 may have been modified between the time the management application 114 makes the identified resource 202 available for download and the time the management application 114 receives the request to download the identified resource 202 .
- the computing device 104 may have switched connectivity from a secured network 106 to an unsecured network 106 .
- the management application 114 may determine for a second time whether the computing device 104 complies with the rules 207 .
- the request to download transmitted from the computing device 104 may include an updated device profile 212 .
- the management application 114 may make the second determination of whether the computing device 104 complies with the rules 207 based on the updated device profile 212 .
- the rules 207 may require that the computing device 104 be connected to a secured network 106 to gain access to the resource and the second determination of compliance may reveal that the computing device 104 is connected to an unsecured network 106 .
- the management application 114 Responsive to the second determination that the computing device 104 complies with the rules 207 , the management application 114 provides the requested resource 202 .
- the client application 124 may manage computing device 104 on behalf of the management application 114 by periodically transmitting the device profile 212 to the server system 102 .
- the management application 114 may determine whether the updated computing device 104 complies with the rules 207 using the updated device profile 212 .
- the management application 114 may transmit rules 207 associated with each one of the identified resources 202 to the computing device 104 .
- the management application 114 may transmit the rules 207 to the client application 124 involved in managing the computing device 104 for determining whether the computing device 104 complies with the rules 207 .
- the management application 114 may not determine whether the computing device 104 complies with the rules 207 of each of the identified resources 202 and instead permits the client application 124 to make this determination.
- the client application 124 may determine whether the computing device 104 complies with the rules 207 associated with the received resource 202 prior to rendering the received resource 202 on the display device 128 .
- the management application 114 may transmit the rules 207 to the computing device 104 prior to transmitting the identified resources 202 .
- the client application 124 may determine whether the computing device 104 complies with the rules 207 , as described above.
- the client application 124 may transmit an indication back to the management application 114 of the compliance status. Responsive to receiving an indication from the computing device 104 that the computing device 104 complies with all and/or a sufficient portion of the rules 207 associated with each respective resource 202 , the management application 114 may transmit the appropriate identified resources 202 to the computing device 104 . Additionally, the client application 124 may store the rules 207 in a memory associated with the computing device 104 , such as the data store 126 .
- the management application 114 may wait to receive an indication from the client application 124 that the computing device 104 complies with the rules 207 associated with the requested resource 202 to determine whether to transmit the requested resource 202 .
- the client application 124 may use the stored rules 207 received from a previous request to make the determination and transmit the request 218 .
- the management application 114 may be further executed to log activity related to the resources 202 for asset tracking purposes.
- the management application 114 may log activities such as transmission of resources, historical data related to the transmission of the resource, data related to the rendering of the resources 202 by the computing device 104 , data related to a storage location of the resources 202 , data related to communication with the computing device 104 , data related to resource qualifiers associated with the resources 202 , data related to computing device 104 compliance with rules 207 , data related to usage and availability of bandwidth, and/or any other data related to the resources 202 .
- the management application 114 may periodically determine whether the transmitted resources 202 have been modified on the computing device 104 .
- the management application 114 may synchronize the modified resource 202 on the computing device 104 with the unmodified resource 202 on the server system 102 .
- the management application 114 may determine whether the resource 202 has been modified based on an edit date, modified date, and/or an access date associated with the resource 202 .
- the management application 114 may periodically request to receive the relevant date from the client application 124 .
- the management application 114 compares the relevant date from the computing device 104 with the corresponding date on the server system 102 and determines to synchronize the respective resources 202 if the two relevant dates do not match.
- the management application 114 may employ a synchronization approach as is known in the art. In some embodiments, the management application 114 may employ the synchronization approach based on determining whether the user is permitted to modify the resource 202 on the computing device 104 . In some embodiments, the management application 114 may remove the resource 202 on the computing device 104 upon synchronizing with the server system 102 . In some embodiments, the management application 114 stores the modified resource 202 in the data store 116 as one of multiple versions of the respective resource 202 .
- the client application 124 may be pre-authorized to access at least some of the resources 202 hosted by the server system 102 .
- the management application 114 may be configured to provide to the client application 124 a listing of resources 202 available for download by the computing device 104 based only on certain embedded authorization data (e.g., device identifier 216 , and/or device profile 212 , etc.) and without requiring the client application 124 to provide additional authorization data (e.g., user name and password).
- the management application 114 may identify resources 202 to include in the listing by determining which of the resources 202 are associated with rules 207 that correspond with the device profile 212 of the computing device 104 .
- the management application 114 may allow the client application 124 to download at least some of the available resources 202 .
- at least one of the available resources 202 may be associated with a distribution rule that requires additional authorization.
- the resource 202 may be a document containing sensitive information that requires authorization of a username and password and/or other additional authorization data.
- the management application 114 may prompt the client application 124 to provide additional authorization data.
- the client application 124 may prompt the user to provide credentials 214 .
- the client application 124 may transmit the credentials 214 and/or the device identifier 216 of the computing device 104 to the management application 114 .
- the management application 114 may allow the client application 124 to download the sensitive resource 202 .
- management application 114 may be embodied in software and/or code executed by general purpose hardware as discussed above, as an alternative the same may also be embodied in dedicated hardware and/or a combination of software/general purpose hardware and dedicated hardware. If embodied in dedicated hardware, each can be implemented as a circuit and/or state machine that employs any one of or a combination of a number of technologies. These technologies may include, but are not limited to, discrete logic circuits having logic gates for implementing various logic functions upon an application of at least one of data signals, application specific integrated circuits having appropriate logic gates, and/or other components, etc. Such technologies are generally well known by those skilled in the art and, consequently, are not described in detail herein.
- the management application 114 executed at the server system 102 can control the use of resources 202 and other electronic content accessed via an electronic meeting between multiple computing devices 104 , as described in detail with respect to FIGS. 3-6 .
- FIG. 3 is a modeling diagram depicting an example flow of communications among a management application 114 and multiple computing devices 104 a - c accessing an electronic meeting 302 .
- the electronic meeting 302 can include at least one function for sharing resources 202 provided by the server system 102 and/or other electronic content.
- entities accessing the electronic meeting 302 may transmit copies of resources 202 among the computing devices 104 a - c , render the resources 202 for display at the computing devices 104 a - c , and/or making the resources 202 available for use at least one of the computing devices 104 a - c.
- the electronic meeting 302 may be hosted via the server system 102 and/or another server system with which the management application 114 can communicate.
- a communication application 303 configured to access the resources 202 may host the electronic meeting 302 , as depicted in FIG. 3 .
- the management application 114 can moderate requests for access to resources 202 transmitted by the communication application 303 . Moderating requests for access to the resources 202 can include ensuring that resources 202 are provided via the electronic meeting 302 to computing devices 104 a - c according to any applicable rules 207 , as described above with respect to FIG. 2 .
- the communication application 303 can retrieve and/or otherwise access the resources 202 on behalf of the participating entities 304 a - c and/or provide the resources to the computing devices 104 a - c via the electronic meeting 302 . Additionally or alternatively, the communication application 303 can receive requests 218 for resources 202 from the computing devices 104 a - c via the electronic meeting 302 and transmit the requests to the management application 114 , which can transmit the requested resources 202 to the requesting devices. In some embodiments, the management application 114 may host the electronic meeting 302 .
- Computing devices 104 a - c accessing resources 202 via an electronic meeting may be authenticated, managed, and/or otherwise determined to be compliant with rules 207 via any suitable manner.
- the client applications 124 a - c may include at least one electronic meeting function via which the computing devices 104 a - c may respectively access and/or establish an electronic meeting 302 .
- the client applications 124 a - c may be installed on the respective computing devices 104 a - c prior to the electronic meeting 302 being established. If an instance of the client application 124 is not installed to a computing device, the computing device may be unable to access the electronic meeting 302 and/or communicate resources 202 and/or other electronic content via the electronic meeting 302 .
- a dedicated electronic meeting application other than the client application 124 can be used to establish and/or access the electronic meeting 302 .
- the dedicated electronic meeting application may be required to communicate with the management application 114 via the electronic meeting 302 via the client application 124 .
- the client application 124 may be a plug-in module added to the dedicated electronic meeting application and/or a separate application used for accessing and/or communicating resources 202 via the electronic meeting 302 .
- a computing device 104 may be able to access the electronic meeting 302 the dedicated electronic meeting application without the client application 124 if the computing device 104 does not access the resources 202 provided by the server system 102 .
- the management application 114 may push and/or otherwise provide the client application 124 to computing devices on which the client application 124 is not installed in response to the computing device requesting access to the resources 202 via the electronic meeting 302 .
- the instance of the client application 124 may automatically be installed to the computing device 104 without intervention by an operator of the computing device 104 . Additionally or alternatively, the computing device 104 may provide a prompt to the operator requesting authorization to install the instance of the client application 124 . Upon the operator affirming that the client application 124 may be installed, the computing device 104 can install the instance of the client application 124 .
- the management application 114 can automatically establish the electronic meeting 302 based on the presence of computing devices 104 a - c corresponding to entities permitted to access the electronic meeting 302 .
- the management application 114 can search for a beacon and/or other identification signal broadcasted and/or otherwise transmitted by each of the computing devices 104 a - c .
- the beacon and/or other identification signal can identify the computing device as being available for the electronic meeting 302 .
- the management application 114 can search for the beacon at predetermined times during a time period in which the electronic meeting 302 is scheduled to occur and/or continuously search for the beacon during the time period.
- the management application 114 can broadcast a discovery signal.
- the discovery signal can be received by the computing devices 104 a - c at which the client applications 124 a - c are respectively executing. Each of the client applications 124 a - c can transmit a response to the discovery signal. The response can notify the management application 114 that the computing devices 104 a - c are available to join the electronic meeting 302 . At least one of the client applications 124 a - c may automatically transmit a response to the management application 114 without intervention by respective operators of the computing devices 104 a - c . Additionally or alternatively, at least one of the client applications 124 a - c may provide a prompt to the respective operator and transmit a response to the management application 114 based on the respective operator affirming that he and/or she wishes to join the electronic meeting 302
- the client applications 124 a - c may transmit data via the electronic meeting 302 identifying the entities 304 a - c accessing and/or requesting access to the electronic meeting 302 .
- the entities 304 a - c can be identified by any suitable identifier, such as a device profile 212 , at least one of credentials 214 , a device identifier 216 , and/or a combination thereof.
- an identifier for an entity can identify the operator of a computing device.
- the identifier can include a user name for the operator.
- an identifier for an entity can identify the computing device accessing requesting access to the electronic meeting.
- Non-limiting examples of identifiers for computing devices 104 a - c include an internet protocol (“IP”) address and/or a MAC address.
- IP internet protocol
- an entity may identified by a pairing of an operator identifier and a device identifier.
- the management application 114 may obtain data 306 from the electronic meeting 302 identifying the entities 304 a - c , such as the device profile 212 , at least one of credentials 214 , a device identifier 216 , and/or a combination thereof provided by each of the client applications 124 a - c .
- the communication application 303 can push the data 306 to the management application 114 .
- the management application 114 can pull and/or otherwise retrieve the data 306 from the communication application 303 .
- the management application 114 may authenticate and/or otherwise identify each of the entities 304 a - c accessing and/or requesting access to the electronic meeting 302 from the data 306 .
- the management application can access a listing 308 stored in the data store 116 .
- the listing 308 can include a list of entities that are required to participate in the electronic meeting 302 in order for the management application 114 to authorize the communication of at least one of the resources 202 and/or other electronic content.
- the entities 304 a , 304 b are listed as required participants for the electronic meeting 302 .
- the listing 308 can also include a list of other entities that are authorized to access the electronic meeting 302 . For example, as depicted in FIG.
- the entity 304 c is listed as an authorized participant.
- the management application 114 may not require the participation of the entity 304 c (i.e., an authorized but not required entity) in the electronic meeting 302 as a prerequisite to communication of at least one of the resources 202 and/or other electronic content among the entities 304 a - c .
- authorized but not required entities e.g., entity 304 c
- Any suitable mechanism and/or process can be used for authorizing communication of the at least one of the resources 202 and/or other electronic content among the entities 304 a - c via the electronic meeting 302 .
- the management application 114 can authorize the communication of the resources 202 and/or other electronic content by respectively providing tokens 310 a - c to the client applications 124 a - c , as depicted in FIG. 3 .
- the tokens 310 a - c can include an authorization to access the resources 202 and/or other electronic content from the data store 116 of the server system 102 and/or another server system in communication with the management application 114 .
- the tokens 310 a - c can respectively identify that requests for the resources 202 from the entities 304 a - c , the client applications 124 a - c , and/or the computing device 104 a - c are to be granted.
- the tokens 310 a - c can specify permissions (e.g., read, write, copy, etc.) for using the resources 202 and/or other electronic content.
- the tokens 310 a - c can additionally or alternatively include data specifying that the use of the resources 202 and/or other electronic content is authorized during a scheduled time period for the electronic meeting.
- the management application 114 can perform at least one action enforcing the conditions specified in the tokens 310 a - c as described above with respect to FIG. 2 .
- the management application 114 can add the tokens 310 a - c to the approved credentials 204 in the data store 116 .
- Each of the computing devices 104 a - c can add a respective one of the tokens 310 a - c to the credentials 214 .
- the management application 114 may determine resource-grouping identifiers 203 based on the credentials 214 of the requesting entity and/or the device identifier 216 of the computing device 104 corresponding to the entity. For example, each resource grouping identifier 203 may be associated with a pairing of credentials 214 (including at least one of the tokens 310 a - c ) and a device identifier 216 . The management application 114 may determine at least one of resource-grouping identifiers 203 associated with the pairing of credentials 214 and the device identifier 216 .
- the management application 114 can identify the resources 202 that are associated with the determined resource-grouping identifiers 203 .
- the management application 114 can determine whether a computing device 104 from which the request 218 originated complies with the rules 207 associated with each one of the identified resources 202 . If the management application 114 determines that the computing device 104 complies with the rules 207 , the management application 114 can transmit the identified resources 202 associated with the rules 207 via the electronic meeting 302 . In some embodiments, the management application 114 automatically transmits the identified resources 202 that the computing device 104 is authorized to receive. In some embodiments, the management application 114 may make the identified resources 202 available for download.
- a computing device 104 may receive an indication that the resource 202 is available for download.
- the computing device 104 may transmit a request to the management application 114 for downloading the applicable resource 202 .
- the management application 114 may transmit the resource 202 to the computing device 104 .
- the client applications 124 a - c can manage the computing devices 104 a - c based on the conditions specified in the tokens 310 a - c .
- a client applications 124 may block attempts to access resources 202 in violation of the conditions specified in the tokens 310 a - c .
- the client application 124 may receive at least one of the rules 207 from the server system 102 along with the token. Each of the received rules 207 may be associated with at least one of the resources 202 identified in the token.
- the client application 124 can determine compliance with the at least one of the rules 207 received by the client application (e.g., based on the device profile 212 for the requesting computing device).
- the client application 124 determines a request to access resources 202 via the electronic meeting 302 is not compliant with some and/or all of the received rules 207 , the client application 124 can render a notice of non-compliance on a display device 216 of the computing device 104 .
- the client application 124 may additionally or alternatively transmit a notification to the management application 114 indicating that the computing device 104 is non-compliant. If the client application 124 determines that the request to access resources 202 via the electronic meeting 302 is compliant with all and/or a portion of the sets of rules 207 , the client application 124 can transmit a notification of compliance to the management application 114 .
- the client application 124 can obtain the resources 202 associated with the rules 207 with which the requesting computing device 104 complies. The resources 202 may be obtained via the electronic meeting 302 .
- the management application 114 can authorize the communication of electronic content by granting access to the resources 202 and/or other electronic content by the communication application 303 .
- the management application 114 may provide a token to the communication application 303 and/or add a temporary credential for the communication application 303 to the approved credentials 204 stored in the data store 116 .
- the token and/or temporary credential may be valid for a particular period of time corresponding to a scheduled start time and/or end time for the electronic meeting 302 .
- the management application 114 can implement at least one security measure to prevent unauthorized entities from accessing electronic content communicated via the electronic meeting 302 .
- FIG. 4 is a modeling diagram depicting an example flow of communications among the management application 114 , the computing devices 104 a - c , and an unauthorized entity.
- Each of the computing devices 104 a - c can respectively access the electronic meeting 302 via the connections 404 a - c .
- Another computing device 402 can attempt to access the meeting and/or be otherwise detected by the management application 114 .
- This other computing device 402 can correspond to an unauthorized entity 406 .
- the management application 114 can detect an unauthorized entity 406 accessing and/or attempting to access the electronic meeting 302 , as depicted in FIG. 4 by the computing device 402 identifying the entity 406 to the electronic meeting 302 .
- the management application can receive data 408 identifying the entity 406 .
- the management application 114 can detect the unauthorized entity 406 based on data received via a communication channel other than the electronic meeting 302 , as depicted in FIG. 4 by the computing device 402 communicating the data 406 ′ identifying the unauthorized entity 406 .
- the data 406 ′ may be received via a router and/or other network communication device providing network connectivity to the computing devices 104 a - c and the computing device 402 .
- the management application 114 may receive the data 406 ′ from a router and/or other network communication device via a direct connection between the router and the server system 102 and/or a connection with another server system in communication with the router.
- the management application 114 can determine that the entity 406 and/or the computing device 402 are not authorized to access the electronic meeting 302 via any suitable process. In one non-limiting example, management application 114 can determine that the entity 406 is not included in the listing 308 . In another non-limiting example, the management application 114 can determine that authentication data for the entity 406 (e.g., a user name and/or password) is invalid. In another non-limiting example, the management application 114 can determine that the computing device 402 corresponding to the unauthorized entity 406 fails to comply with at least one of the rules 207 and/or another rule governing access to the resources 202 .
- authentication data for the entity 406 e.g., a user name and/or password
- the management application 114 can restrict communication of at least one of the resources 202 and/or other electronic content based on determining that the entity 406 is not authorized to access the electronic meeting 302 .
- restricting the communication of electronic content can include restricting the computing devices 104 a - c and/or the entities 304 a - c to communicating a subset of electronic content.
- an electronic meeting 302 that involves sharing both publicly available resources 202 and secret and/or otherwise sensitive resources 202 may be restricted to sharing only the publicly available resources 202 in the presence of the unauthorized entity 406 .
- restricting the communication of electronic content can include barring any communication of electronic content in the presence of the unauthorized entity 406 .
- any suitable mechanism and/or process can be used for restricting communication of the at least one of the resources 202 and/or other electronic content among the entities 304 a - c .
- the management application 114 can restrict the communication of the resources 202 and/or other electronic content by respectively providing updated tokens 410 a - c to the client applications 124 a - c to replace tokens 310 a - c , as depicted in FIG. 4 .
- the tokens 410 a - c can include an authorization to access fewer of the resources 202 as compared to the tokens 310 a - c .
- the tokens 410 a - c can specify permissions (e.g., read, write, copy, etc.) for using the resources 202 and/or other electronic content that are more restrictive as compared to permissions specified by the tokens 310 a - c .
- the conditions specified in the tokens 410 a - c can be enforced by the client applications 124 a - c , the management application 114 , and/or some combination thereof as described above with respect to FIG. 3 .
- the management application 114 can restrict the communication of the resources 202 and/or other electronic content by restricting access to the resources 202 and/or other electronic content by the communication application 303 .
- the management application 114 may invalidate any tokens previously provided to the communication application 303 and provide a new token to the communication application 303 that specifies a more restrictive permission level and/or subset of resources 202 that the communication application 303 may access.
- the management application 114 can restrict communication of the resources 202 and/or other electronic content based on a required entity leaving the electronic meeting 302 and/or a computing device corresponding to a required entity leaving the electronic meeting 302 and/or a specified geographic area.
- the management application 114 can direct the communication application to terminate the electronic meeting 302 based on a required entity leaving the meeting, a computing device corresponding to a required entity leaving a specified geographic area in which the computing device 104 a - c are positioned, an unauthorized entity 406 accessing and/or attempting to access the electronic meeting, and/or an unauthorized computing device 402 entering a specified geographic area in which the computing device 104 a - c are positioned.
- the management application 114 can perform a remedial action in response to detecting an unauthorized entity 406 and/or an unauthorized computing device 402 for a computing device 402 that can be managed by the management application 114 .
- a remedial action can include at least one security measure for preventing the unauthorized entity 406 from accessing the resources 202 .
- a remedial action can be specified at least one rule stored in the data store 116 and governing access to the resources 202 .
- An instance of the client application 124 may be installed on the computing device 402 .
- the application 124 may include at least one management function for managing the computing device 402 in response to commands received from the management application 114 .
- the client application 124 can perform the remedial actions at the computing device 402 in response to commands from the management application 114 .
- the remedial action can include transmitting data 412 to the computing device 402 .
- the data 412 can include command to a client application 124 executing on the computing device 402 .
- the command can direct the client application to erase some or all content from the computing device 402 (i.e., perform a “device wipe”).
- the data 412 can include a software update to be installed on the computing device 402 .
- the software update can update the computing device 402 such that the computing device 402 is compliant with at least one rule governing access to the resources 202 .
- the remedial action can involve notifying an administrative entity of the presence of the unauthorized entity 406 and/or the unauthorized computing device 402 .
- the presence of an unauthorized computing device 402 detected in the vicinity of the computing devices 104 a - c may trigger an alert to an administrator and/or security personnel.
- the administrator and/or security personnel may respond by escorting the user of the unauthorized computing device 402 from the premises.
- each of the computing devices 104 a - c may be positioned in a geographical location in which network connectivity is provided by at least one network communication device that can be controlled by the management application 114 .
- network device(s) such as routers and/or computing systems in communication with routers, may provide network connectivity to the computing devices 104 a - c accessing the electronic meeting 302 .
- the management application 114 may communicate with the network communication device(s) via another computing system configured to control the network communication device(s), such as a server system providing network connectivity between the computing devices 104 a - c and the server system 102 .
- the management application 114 may be able to restrict the operations of the unauthorized computing device 402 by communicating a command to the network communication device(s).
- the command communicated to the network communication device(s) can identify the computing device(s) 402 via any suitable identifier, such as an IP address and/or a MAC address.
- the command can direct the network communication device(s) to restrict and/or deny network access by the computing device(s) 402 .
- FIG. 5 is a flow chart illustrating an example method 500 for controlling resources 202 and/or other electronic content communicated among computing devices 104 a - c .
- the method 500 is described with reference to the system implementations depicted in FIGS. 1-2 and the flows of communication depicted in FIGS. 3-4 . Other implementations, however, are possible.
- the method 500 involves identifying multiple entities available for communicating electronic content via an electronic meeting and/or other form of electronic communication, as shown in block 510 .
- the processor 108 of the server system 102 can execute the management application 114 to identify that entities 304 a , 304 b are required for communicating electronic content via an electronic meeting.
- the management application 114 can identify the required entities 304 a , 304 b in any suitable manner, such as accessing a listing 308 .
- the method 500 further involves determining that determining that each of a required subset entities is available for communication via the electronic meeting and/or other form of electronic communication, as shown in block 520 .
- the management application 114 can determine that the required entities 304 a , 304 b are accessing the electronic meeting 302 .
- the required subset of entities can include multiple entities whose availability is mandatory.
- the required subset of entities can include a required number of entities (such as, but not limited to, a quorum) without requiring any specific entity be available.
- the required subset of entities can include at least one mandatory entity and at least one additional entity selected from a group of required entities.
- authorizing electronic communication may require the participation and/or availability of an entity 304 a as well the participation and/or availability of either an entity 304 b or an entity 304 c .
- the participation and/or availability of entities 304 a , 304 b may be sufficient to authorize electronic communication.
- the participation and/or availability of entities 304 a , 304 c may also be sufficient to authorize electronic communication.
- the required subset of entities can include a required entity and required number of additional entities (such as, but not limited to, a quorum) without requiring any specific entity of the additional entities be available.
- Determining that the required entities 304 a , 304 b are accessing the electronic meeting 302 can include authenticating the required entities 304 a , 304 b based on respective authentication data provided by the respective client applications 124 a , 124 b .
- the client applications 124 a , 124 b may authenticate the entities required 304 a , 304 b by verifying the authentication data.
- the client applications 124 a , 124 b can communicate successful verifications of the authentication data to the management application 114 .
- the client applications 124 a , 124 b may transmit the authentication data to the management application 114 .
- the management application 114 can verify the authentication data provided by the client applications 124 a , 124 b.
- authentication data can include information provided by the required entities 304 a , 304 b to the client applications 124 a , 124 b .
- Non-limiting examples of authentication data provided by the required entities 304 a , 304 b include a password, a personal identification number, at least one answer to at least one secret question, a token, and the like.
- the authentication data can include biometric information associated with each of the required entities 304 a , 304 b .
- a required entity 304 a using a computing device 104 a may access fingerprint scanning function provided by the client application 124 a and/or another application.
- the required entity 304 a may scan at least one of his and/or her fingerprints.
- determining that the required entities 304 a , 304 b are accessing the electronic meeting 302 can include determining that the respective client applications 124 a , 124 b at the computing devices 104 a , 104 b is accessing a common collaborative session via the network 106 .
- each of the computing devices 104 a , 104 b may be executing a respective application for accessing a web meeting and/or other media conference.
- the management application 114 can identify the computing devices 104 a , 104 b corresponding to the required entities 304 a , 304 b based on at least one identifier provided for accessing the collaborative session, such as an IP address and/or MAC address associated with each of the computing devices 104 a - c.
- determining that each of the required entities 304 a , 304 b is accessing the electronic meeting 302 comprises determining that each of the computing devices 104 a , 104 b is positioned in a common geographical location.
- the management application 114 may identify the common geographical location by reference to a file and/or other data stored in a data store 116 .
- the common geographical location can be defined in any suitable manner.
- a common geographical location may be delineated by fixed boundaries.
- a common geographical location may be defined by a proximity to at least one reference location, such as (but not limited to) a distance from at least one base station in a telecommunication system and/or access points in a wireless data network.
- the management application 114 can determine that the computing devices 104 a , 104 b corresponding to required entities 304 a , 304 b are positioned in a common geographic location via any suitable process. In some embodiments, the management application 114 can detect and/or otherwise determine that each computing device is registered with the management application via a sensing device positioned in the common geographic location. For example, one or more radio-frequency identification (“RFID”) scanners may be positioned at one or more respective locations in a geographic location. Each of the computing devices 104 a , 104 b may display an RFID identifier and/or have an RFID identifier affixed to it. The RFID identifier can be scanned by an RFID scanner.
- RFID radio-frequency identification
- a control device can be configured to detect that the computing devices 104 a - c are positioned in the common geographic location by establishing radio communication with the computing devices 104 a , 104 b via at least one field communication (“NFC”) process.
- NFC processes include touching each of the computing devices 104 a , 104 b to the control device and/or another sensor device and/or bring each of the computing devices 104 a , 104 b into close proximity with the control device.
- the management application 114 can detect and/or otherwise determine that the computing devices 104 a , 104 b are positioned in a common geographic location by accessing the global positioning system (“GPS”) coordinates for each of the computing devices 104 a , 104 b . In some embodiments, the management application 114 can determine that computing devices 104 a , 104 b such as smart phones are positioned in a common geographic location by triangulating the position of each computing device based on the distance of the computing device from each of multiple base stations in a telecommunication system.
- GPS global positioning system
- the management application 114 can determine that a required entity 304 a , 304 b has left the common geographical location.
- the management application 114 can restrict the communication of at least one of the resources 202 and/or other electronic content based on the participating required entity leaving the common geographical location. For example, the management application 114 may periodically update a stored list of the respective locations of the computing devices 104 a - c .
- the management application 114 may determine during a first time period that a computing device 104 a corresponding to a required entity 304 a is positioned within the common geographical location.
- the management application 114 may authorize communication of at least one of the resources 202 and/or other electronic content via the electronic meeting 302 during the first time period.
- the management application 114 may determine during a second time period that the computing device 104 a is positioned outside the common geographical location. The management application 114 may restrict communication of at least one of the resources 202 and/or other electronic content via the electronic meeting 302 during the second time period.
- the method 500 further involves authorizing a communication of the electronic content among the required entities 304 a , 304 b and, optionally, any other authorized entities 304 c via the electronic meeting and/or other form of electronic communication based on determining that each of the entities is available for communication, as shown in block 530 .
- the management application 114 can authorize the client applications 124 a - c accessing the electronic meeting 302 to communicate at least one of the resources 202 provided by the server system 102 and/or other electronic content, as described above with respect to FIG. 3 .
- the management application 114 can authorize the client applications 124 a - c to communicate at least one of the resources 202 and/or other electronic content by decrypting the electronic content for use during the electronic meeting 302 .
- the electronic content may be encrypted using an encryption key provided by the required entities 304 a , 304 b .
- the encryption key may be divided among the required entities 304 a , 304 b such that each entity has access to a respective portion of the encryption key.
- Each of the required entities 304 a , 304 b can provide a respective portion of the encryption key upon accessing the electronic meeting 302 .
- the portions of the encryption key may be stored on the computing devices 104 a , 104 b .
- the client applications 124 a , 124 b can retrieve the portions of the encryption key in response to the entities 304 a , 304 b accessing and/or requesting access to the electronic meeting 302 .
- the client applications 124 a , 124 b can provide the portions of the encryption key to the management application 114 .
- the management application 114 can combine and/or perform other operations on the portions of the encryption key into the encryption key and decrypt content to be shared via the electronic meeting 302 .
- a 256-bit key or other key can be partitioned. Each partition can be provided to a respective entity.
- the management application 114 can receive each partition and parse or otherwise combine the partitions to obtain an operable 256-bit key.
- a 256-bit key or other key can be partitioned. Each partition can be provided to a respective entity.
- the management application 114 can receive each partition and execute an algorithm using the partitions to obtain an operable 256-bit key.
- the management application 114 can authorize the client applications 124 a - c to communicate at least one of the resources 202 and/or other electronic content based on secondary authentication information generated from authentication data provided by the required entities 304 a , 304 b .
- generating secondary authentication data can include combining the authentication data received from the required entities 304 a , 304 b .
- the management application may concatenate and/or otherwise join a group of passwords to form a combined password. The combined password may be used to verify that the electronic content can be communicated during the electronic meeting 302 .
- generating secondary authentication data can include generating authentication data that is different from the separate authentication data received from the required entities 304 a , 304 b .
- the management application may receive a personal identification number from each of the required entities 304 a , 304 b .
- the management application can perform mathematical operations (e.g., addition and/or multiplication) on the received personal identification numbers.
- the output of the mathematical operation(s) can be a new identification number.
- the new identification number may be used to verify that the electronic content can be communicated during the electronic meeting 302 .
- the management application 114 can detect an additional entity 406 that lacks an authorization for accessing the electronic meeting 302 .
- the management application 114 can restrict the communication of at least some of the electronic content among at least some of the entities 304 a - c based on detecting the additional entity 406 , as described above with respect to FIG. 4 .
- the management application 114 can determine that the entities 304 a , 304 b are respectively accessing the electronic meeting 302 via authorized computing devices 104 a , 104 b .
- the management application 114 can permit communication of the resources 202 and/or other electronic content based on determining that each of the computing devices 104 a , 104 b is authorized to access the electronic meeting 302 . Determining that each of the computing device 104 a , 104 b is authorized to access the electronic meeting 302 can include, for example, determining that each computing device 104 a , 104 b is compliant with at least one of the rules 207 .
- FIG. 6 is a flow chart illustrating an example method 600 for restricting access to resources 202 and/or other electronic content communicated among computing devices 104 a - c based on the presence of an unauthorized entity 406 .
- the method 600 is described with reference to the system implementations depicted in FIGS. 1-2 and the flows of communication depicted in FIGS. 3-4 . Other implementations, however, are possible.
- the method 600 involves identifying multiple entities authorized to electronically communicate with one another, as shown in block 610 .
- the processor 108 of the server system 102 can execute the management application 114 to identify that the entities 304 a - c are authorized to access the electronic meeting 302 .
- the management application 114 can identify that the entities 304 a - c are authorized to access the electronic meeting 302 by, for example, referencing a listing 308 and/or by verifying that the entities 304 a - c have provided valid authentication data.
- the method 600 further involves detecting an additional entity that lacks an authorization for communicating with the entities, as shown in block 620 .
- the processor 108 of the server system 102 can detect an additional entity 406 that lacks an authorization for accessing the electronic meeting 302 , as described above with respect to FIG. 4 .
- detecting the unauthorized entity 406 can include determining that a computing device 402 corresponding to the unauthorized entity 406 (e.g., a user that is not authorized to access the meeting) is positioned in the same geographical location as other computing devices 104 a - c authorized to access the meeting.
- the geographical location can be a defined by reference to a specific area, such as a boardroom, and/or a proximity to the other computing devices 104 a - c (e.g., within 200 feet of the other computing devices 104 a - c ).
- the management application 114 can detect the unauthorized entity 406 based on the unauthorized entity 406 unsuccessfully attempting to access the electronic meeting 302 . In one non-limiting example, the management application 114 can determine that authentication data provided by the entity 406 is invalid. The management application 114 may execute at least one remedial action for a managed computing device 402 in response to a threshold number of failed attempts by an entity to access the meeting using invalid authentication data. In another non-limiting example, the management application 114 can determine that the entity 406 is not included on a listing 308 of the entities authorized to access the electronic meeting 302 . In another non-limiting example, the management application 114 can determine that a request from the entity to access the electronic meeting 302 has a timestamp outside a designated time period for the electronic meeting 302 .
- the management application 114 can determine that the computing device 402 is not authorized to access the electronic meeting, regardless of whether the operator of the computing device 402 is authorized to access the meeting. For example, the management application 114 can determine that a computing device 402 is not authorized to access the electronic meeting based on the computing device 402 being non-compliant with at least one rule governing access to the resources 202 and/or other electronic content used for the electronic meeting.
- the method 600 involves restricting a communication of at least some electronic content among at least some of entities 304 a - c based on detecting the additional entity that lacks authorization, as shown in block 630 .
- the processor 108 of the server system 102 can restrict communication among the entities 304 a - c in an electronic meeting 302 and/or other form of electronic communication, as described above with respect to FIG. 4 .
- the management application 114 can perform at least one remedial action in response to detecting an unauthorized computing device 402 accessing the electronic meeting 302 , attempting to access the electronic meeting 302 , and/or being positioned in the vicinity of other computing devices 104 a - c authorized to access the electronic meeting 302 .
- the remedial action includes transmitting a software update to the computing device 402 .
- the software update can bring the computing device 402 into compliance with at least one rule governing access to resources shared via the electronic meeting 302 , such as the rules 207 .
- the remedial action includes transmitting a command to an instance of the client application 124 executing on the computing device 402 .
- the command directs the client application 124 to erase some or all content and/or applications from the computing device 402 (i.e., perform a partial or total “device wipe”).
- the remedial action includes transmitting a command directing the client application 124 to lock the computing device 402 .
- Locking the computing device 402 can include preventing an operator of the computing device from accessing at least one application on the computing device 402 .
- FIGS. 1-6 involves the server system 102 providing at least one of the resources 202 , other implementations are possible.
- an additional enterprise level computing device may store and provide at least one of the resources 202 based on commands from the management application 114 .
- the server system 102 can include multiple servers performing multiple functions.
- the server system 102 can include a proxy server function and/or a compliance server function.
- the proxy server function may include providing a proxy service.
- the term “proxy service” is used to refer to computer-executable instructions for performing the at least one function for authenticating access credentials and device identifiers.
- the proxy service may be executed to receive an access request from a computing device for accessing resources 202 and to determine whether to grant or deny the access request. Based on determining that the access request is granted, the proxy service may associate a computing device with access credentials to access resources 202 provided by and/or accessible via the server system 102 .
- a proxy server function may communicate with a compliance server function, such as a compliance service, to authorize a computing device 104 by determining whether the computing device 104 complies with hardware, software, device management restrictions, and the like, as defined in a set of rules 207 .
- a compliance server function such as a compliance service
- the term “compliance service” is used to refer to computer-executable instructions for performing the functionality described herein for authorizing the device characteristics of the requesting device.
- the compliance service may identify the device characteristics from a device profile listing of hardware restrictions, software restrictions, and/or computing device management restrictions for a given computing device.
- each box may represent a module, segment, or portion of code that comprises program instructions to implement the specified logical function(s).
- the program instructions may be embodied in the form of source code that comprises human-readable statements written in a programming language or machine code that comprises numerical instructions recognizable by a suitable execution system such as a processor 108 and 118 in a computer system or other system.
- the machine code may be converted from the source code, etc.
- each block may represent a circuit or a number of interconnected circuits to implement the specified logical function(s).
- any logic or application described herein that comprises software or code can be embodied in any non-transitory computer-readable medium for use by or in connection with a computing system such as, for example, a processor in a computer system or other system.
- the logic may comprise, for example, statements including instructions and declarations that can be fetched from the computer-readable medium and executed by a computing system.
- a “computer-readable medium” can include any medium that can contain, store, maintain, or otherwise include the logic or application described herein for use by or in connection with a computing system.
- the computer-readable medium can comprise any one of many physical media such as, for example, magnetic, optical, or semiconductor media. More specific examples of a suitable computer-readable medium can include, but are not limited to, magnetic tapes, magnetic floppy diskettes, magnetic hard drives, memory cards, solid-state drives, USB flash drives, optical discs, etc.
- the computer readable medium may be a random access memory (“RAM”). Examples of a RAM can include (but are not limited to) static random access memory (“SRAM”), dynamic random access memory (“DRAM”), magnetic random access memory (“MRAM”), etc.
- the computer-readable medium may be a read-only memory (“ROM”), a programmable read-only memory (“PROM”), an erasable programmable read-only memory (“EPROM”), an electrically erasable programmable read-only memory (“EEPROM”), or other type of memory device.
- ROM read-only memory
- PROM programmable read-only memory
- EPROM erasable programmable read-only memory
- EEPROM electrically erasable programmable read-only memory
Abstract
Methods, systems, and devices provide control over resources electronically communicated among computing devices. In some embodiments, a management application identifies multiple entities for communicating electronic content. The management application determines that at least a subset of the entities required for communicating the electronic content is available for electronic communication. The management application authorizes communication of at least some of the electronic content among the entities in response to determining that the required subset of entities is available for electronic communication.
Description
- Electronic content provided via a network, such as documents or applications, may be used to enhance collaborative projects between multiple users or to provide electronic content to a widespread audience. For example, video content and other multimedia presentations can be used to provide instructions, augment lectures, and otherwise enhance projects involving multiple participants. Controlling access to and distribution of electronic content and other enterprise resources in a networked environment may ensure that only authorized users and network-connected devices may gain access to sensitive information.
- Systems and methods are desirable for temporarily controlling independently operated computing devices to provide electronic content to users of the computing devices.
- Systems, devices, and methods for controlling resources that are electronically communicated among computing devices are described.
- In some embodiments, a management application identifies multiple entities for communicating electronic content. The management application determines that at least a subset of entities required for communicating the electronic content is available for electronic communication. The management application authorizes communication of at least some of the electronic content among the entities in response to determining that the required subset of entities is available for electronic communication.
- In some embodiments, a management application prevents unauthorized access to an electronic meeting. The management application identifies multiple entities authorized for electronic communication among one another. The management application detects an additional entity that lacks an authorization for electronic communication among the entities. The management application restricts a communication of at least some electronic content among at least some of the entities based on detecting the additional entity that lacks the authorization.
- In some embodiments, a system is provided. The system identifies multiple entities required for authorizing at least one of multiple communication features for communicating electronic content. At least one additional communication feature is available in an absence of at least one of the required entities. The system determines that each required entity is available for electronic communication. The system authorizes performance of the at least one communication feature based on determining that each entity is available for electronic communication.
- These illustrative aspects and embodiments are mentioned not for purposes of limitation or definition, but to provide examples to aid understanding of the concepts described and disclosed herein. Other aspects, advantages, and features will become apparent after review of the entire disclosure, including the accompanying figures and claims.
- Many aspects of the present disclosure can be better understood with reference to the following diagrams. The drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating certain features of the disclosure. Moreover, in the drawings, like reference numerals designate corresponding parts throughout the several views.
-
FIG. 1 is a block diagram of a networked environment according to some embodiments. -
FIG. 2 is a modeling diagram depicting resources accessed by a client application and a management application for authorizing the use of resources by a computing device, according to some embodiments. -
FIG. 3 is a modeling diagram depicting an example flow of communications among a management application and multiple computing devices accessing an electronic meeting, according to some embodiments. -
FIG. 4 is a modeling diagram depicting an example flow of communications among a management application, multiple computing devices accessing an electronic meeting, and an unauthorized entity or device according to some embodiments. -
FIG. 5 is a flow chart illustrating an example method for controlling resources communicated among computing devices according to some embodiments. -
FIG. 6 is a flow chart illustrating an example method for restricting access to resources communicated among computing devices based on the presence of an unauthorized entity according to some embodiments. - Computer-implemented systems and methods are disclosed for a management application controlling applications, files, and other resources being accessed, executed, and/or otherwise used at computing devices via an electronic meeting and/or other forum for electronic communication.
- The following non-limiting example is provided to help introduce the general subject matter of certain embodiments. Multiple individuals may participate in a board meeting for an organization. The board meeting may be scheduled for a given conference room within a building during a given time period. Individuals may participate in the board meeting in person or remotely. Individuals participating in the board meeting may use mobile computing devices, such as tablet computers and/or smart phones, to access board related documents that may be needed for the meeting. The board related documents may be shared to the mobile computing devices via an electronic meeting session. It may be desirable to prevent sharing of the board related documents until a quorum of board members and/or specific members of the board, such as an executive committee, join the meeting, either in person or remotely. A management application can determine the number of the board members and/or the specific board members present in the meeting room and/or accessing the electronic meeting for sharing the board related documents. The management application can determine that a quorum is available and/or the specific members of the board are present based on those members accessing the electronic meeting. The management application can authorize the sharing of the board related documents via the electronic conference based on the quorum being available and/or the specific members of the board being present, thereby ensuring that no less than the required meeting participants are available at a certain time and place to receive the content. The management application can also detect the either the physical presence of unauthorized computing devices and/or attempts to access the electronic meeting by unauthorized users (e.g., non-board members). The management application can restrict sharing of the board related documents via the electronic meeting to prevent the unauthorized computing devices and/or unauthorized users from obtaining the documents via the electronic meeting.
- In accordance with some embodiments, a management application can control the use of resources by computing devices via an electronic meeting and/or other forms of electronic communication. The management application can identify multiple entities required for communicating electronic content. An entity can include a logical representation of any participant in a meeting. The management application may identify a given entity based on any suitable criteria. Non-limiting examples of suitable criteria include (but are not limited to) credentials associated with a particular user (such as, but not limited to, a user name and/or other identifier), one or more identifiers associated with a computing device used to access the electronic meeting (such as, but not limited to, a hardware identifier or network address of the computing device), and/or based on a pairing of a user credential and a device identifier. The required entities may be a subset of all entities authorized to access the electronic meeting. In the absence of all of the required entities, communication of electronic content via the electronic meeting may be restricted and/or disallowed. The management application can determine that each required entity is physically present in the meeting room (assuming an in-person meeting is being held) and/or accessing the electronic meeting (either from within the meeting room and/or a remote location). The management application can authorize communication of the electronic content among the required entities and other authorized entities via the electronic meeting based on determining that each required entity is present in the meeting room and/or accessing the electronic meeting. It should be understood that in some cases, the management application can authorize communication of the electronic content among the required entities and other authorized users even if one of the required users is not accessing the electronic meeting, as long as that required user is physically present in the meeting room.
- As used herein, the term “electronic meeting” is used to refer to an exchange of information between at least two entities executed via a telecommunication system. An electronic meeting may include at least one entity, such as (but not limited to) moderator entities, that are authorized to perform at least one function during the electronic meeting that are unavailable to other entities accessing the meeting. An electronic meeting may permit the exchange of electronic content, such as documents, multimedia presentations, text messages, and the like. In some embodiments, at least one restriction can be placed on the exchange of electronic content during the meeting. Non-limiting examples of an electronic meeting include telephone conferences, internet telephone conferences, videoconferences, web conferences, and the like.
- As used herein, the term “electronic content” is used to refer to any type of resources that can accessed, be rendered for display, and/or otherwise used at a computing system and/or other electronic device. Electronic content can include text and/or multimedia files, such as images, video, audio, and/or any combination thereof. Electronic content can also include application software that is designed to perform at least one specific task at a computing system.
- In some embodiments, each entity can correspond to and/or otherwise be associated with a respective computing device. The management application can determine whether each computing device corresponding to a required entity is authorized to access the electronic meeting. Determining that each computing device is authorized to access the electronic meeting can include determining that the computing device is compliant with at least one rule that controls access to the electronic content by computing devices. For example, a rule may require that software such as a mobile device management module and/or up-to-date antivirus software be installed on the computing device as a prerequisite to granting access to resources shared via the electronic meeting.
- In some embodiments, determining that each entity is authorized for accessing the electronic meeting may include determining that at least some of the computing devices corresponding to the required entities are positioned in a specific geographical location. For example, the management application may require that wireless devices corresponding to required entities be positioned in a particular conference room of an office building and/or that the wireless devices be positioned within a given proximity to one another and/or a given distance from non-authorized wireless devices. The management application can determine that the computing devices are positioned in a specific geographical location by communicating with a computing device and/or system configured for detecting the computing devices, such as (but not limited to) a sensor system, a global positioning system, a telecommunication system, etc. In some cases, the management application may be able to determine locations of the computing devices by communicating with the computing devices themselves (e.g., but requiring the computing devices to transmit its geospatial coordinates and/or other positioning information to the management application).
- In some embodiments, the management application may restrict communication of electronic content based on at least one triggering condition. The triggering conditions may include a required entity leaving a meeting, a computing device corresponding to a required entity leaving a common geographical location, an unauthorized entity accessing and/or attempting to access the electronic meeting, and/or an unauthorized computing device being positioned within a given proximity to one and/or more of the computing devices corresponding to authorized entities. In some embodiments, restricting the communication of electronic content can include restricting the participating entities to communication of a subset of electronic content. For example, an electronic meeting that involves sharing both publicly available documents and secret and/or otherwise sensitive documents may be restricted to sharing only the publicly available documents in the absence of all required entities and/or upon detecting the presence of an unauthorized entity. The presence of an unauthorized entity can include, for example, the unauthorized entity accessing and/or attempting to access the electronic meeting and/or a computing device corresponding to the unauthorized entity being positioned in proximity to computing devices corresponding to authorized entities. In some embodiments, restricting the communication of electronic content can include barring any communication of electronic content in the absence of all required entities and/or the presence of an unauthorized entity.
- In some embodiments, the management application may authenticate each entity accessing the electronic meeting based on authentication data provided by a client application executed at a computing device corresponding to the entity. As used herein, the term “authentication data” is used to refer to any data used by an application to verify the identity of an entity and/or approve access to a resource provided via the application. In some embodiments, authentication data can include information provided by the entity. Non-limiting examples of authentication data provided by an entity include a password, a personal identification number, at least one answer to at least one secret question, a token, and the like. In some embodiments, authentication data can include biometric information associated with the entity. Non-limiting examples of biometric information associated with the entity can include the entity's voice, DNA, handprint, iris and/or retinal scan, and the like.
- In some embodiments, the management application can authorize communication of the electronic content based on secondary authentication data generated from authentication data provided by each of the required entities. In some embodiments, generating secondary authentication data can include combining the authentication data received from the required entities. For example, the management application may concatenate and/or otherwise join a group of passwords received from the required entities to form a combined password. The combined password may be used to verify that the communication of electronic content during the electronic meeting is authorized. In some embodiments, generating secondary authentication data from authentication data provided by required entities can include generating authentication data that is different from the separate authentication data received from the required entities. For example, the management application may receive a personal identification number from each of the required entities. The management application can perform at least one mathematical operation and/or other algorithms on the received personal identification numbers. The output of the mathematical operation(s) and/or other algorithm can be a new identification number. The new identification number may be used to verify that the electronic content can be communicated during the electronic meeting.
- In some embodiments, the management application can authorize communication of electronic content by decrypting the electronic content with an encryption key collectively provided by the required entities. The management application can receive a respective portion of the encryption key from each required entity and/or from a computing device corresponding to the required entity. The management application can combine the portions to obtain the encryption key. The management application can decrypt the electronic content with the encryption key.
- In some embodiments, the management application can restrict communication of electronic content via an electronic meeting in response to detecting an unauthorized entity. In some embodiments, detecting the unauthorized entity can include determining that a computing device corresponding to the unauthorized entity (e.g., a user that is not authorized to access the meeting) is positioned in the same geographical location as other computing devices authorized to access the meeting. In some embodiments, the management application can determine that a computing device is not authorized to access the electronic meeting, regardless of whether the operator of the computing device is authorized to access the meeting. For example, the management application can determine that a computing device is not authorized to access the electronic meeting based on the computing device being non-compliant with at least one rule governing access to the electronic content by computing devices.
- In some embodiments, the management application can perform at least one remedial action in response to detecting an unauthorized computing device accessing an electronic meeting, attempting to access the electronic meeting, and/or being positioned in the vicinity of other computing devices authorized to access the electronic meeting. In one non-limiting example, the remedial action includes transmitting a software update to the computing device. The software update is configured to bring the computing device into compliance with at least one rule governing access to resources shared via the electronic meeting. In another non-limiting example, the remedial action includes transmitting a command to a client application executing on the computing device. The command directs the client application to erase some or all content and/or applications from the computing device (i.e., perform a partial or total “device wipe”) and/or to disable certain functions of the computing device and/or its applications. In another non-limiting example, the remedial action includes transmitting a command directing the client application to lock the computing device.
- In some embodiments, the management application can detect the unauthorized entity based on the unauthorized entity unsuccessfully attempting to access the electronic meeting. In one non-limiting example, the management application can determine that authentication data provided by the entity is invalid. The management application may execute at least one remedial action in response to a threshold number of failed attempts by an entity to access the meeting using invalid authentication data. In another non-limiting example, the management application can determine that the entity is not included on a listing of the entities authorized to access the electronic meeting. In another non-limiting example, the management application can determine that a request from the entity to access the electronic meeting has a timestamp outside a designated time period for the electronic meeting.
- The foregoing illustrative examples are given to introduce the general subject matter discussed herein and are not intended to limit the scope of the disclosed concepts. The following sections describe various additional aspects and examples with reference to the drawings in which like numerals indicate like elements. The features discussed herein are not limited to any particular hardware architecture and/or configuration. A computing device can include any suitable arrangement of components that provide a result conditioned on at least one input. Suitable computing devices include multipurpose microprocessor-based computer systems accessing stored software that programs and/or configures the computing system from a general-purpose computing apparatus to a specialized computing apparatus implementing one or more aspects of the present subject matter. Any suitable programming, scripting, and/or other type of language and/or combinations of languages may be used to implement the teachings contained herein in software to be used in programming and/or configuring a computing device. Aspects and features from each embodiment disclosed can be combined with any other embodiment.
- Referring now to the drawings,
FIG. 1 is a block diagram depicting example computing systems for implementing certain embodiments. The example computing systems include aserver system 102 and at least oneexample computing device 104 in communication via anetwork 106. A general discussion of the components of theserver system 102 and thecomputing device 104 is provided below. - The
server system 102 may include at least one server computer and/or any other system providing capabilities for managing access to resources and/or distributing resources to computing device(s) 104. In some embodiments,multiple server systems 102 may be employed that are configured in at least one server bank, computer banks, and/or other arrangements. For example,multiple server systems 102 may be configured to provide a cloud computing resource, a grid computing resource, and/or any other distributed computing arrangement.Such server systems 102 may be located in a single installation or may be distributed among many different geographic locations. For purposes of convenience, theserver system 102 is referred to herein in the singular. Even though theserver system 102 is referred to in the singular, it is understood thatmultiple server systems 102 may be employed in the arrangements as descried herein. - The
computing device 104 can include any suitable computing device and/or system for communicating via thenetwork 106 and executing at least one application. Non-limiting examples of acomputing device 104 include a desktop computer, a laptop computer, a personal digital assistant, a cellular telephone, a set-top box, a music player, a web pad, a tablet computer system, a game console, and/or another device with like capability. Thecomputing device 104 may be configured to execute various applications. For example, thecomputing device 104 may be configured to execute applications such as web browsing applications, email applications, instant messaging applications, and/or other applications capable of receiving and/orrendering resources 202 on a display 136 associated with thecomputing device 104. - The
server system 102 includes aprocessor 108 and thecomputing device 104 includes aprocessor 118. Each of theprocessors processors processors processors memories processors memory 110 of theserver system 102 and in thememory 120 of thecomputing device 104. - Each of the
memories - The
processor 108 and thememory 110 of theserver system 102 may be communicatively coupled to alocal interface 112. Theprocessor 118 and thememory 120 of thecomputing device 104 may be communicatively coupled to alocal interface 122. A local interface can include, for example, a data bus with an accompanying address/control bus or other bus structure. One or more of theprocessors memories local interfaces local interfaces - The
computing device 104 may also include a number of external and/or internal devices such as a mouse, a keyboard, a display, audio speakers, one or more microphones, and/or any other input and/oroutput devices 130. For example, thecomputing device 104 may include and/or be in data communication with adisplay device 128. A non-limiting example of adisplay device 128 is a computer monitor or computer screen, such as a touch screen. AlthoughFIG. 1 depicts thedisplay device 128 as a separate device coupled to thecomputing device 104, thedisplay device 128 can be integrated into thecomputing device 104. - The
computing device 104 can also include at least one communication component (not shown inFIG. 1 ). One of the communication components can include a wired network connectivity component such as, for example, an Ethernet network adapter, a modem, and/or the like. Thecomputing device 104 may further include a wireless network connectivity interface, for example, a Peripheral Component Interconnect (“PCI”) card, a Universal Serial Bus (“USB”) interface, a Personal Computer Memory Card International Association (“PCMCIA”) card, Secure Digital Input-Output (“SDIO”) card, NewCard, Cardbus, a modem, a wireless radio transceiver, and/or the like. Thecomputing device 104 may be operable to communicate via wired connection with theserver system 102 with the aid of the wired network connectivity component. Thecomputing device 104 may be further operable to communicate wirelessly with theserver system 102 with the aid of the wireless network connectivity component. - Instructions stored in the
memory 110 of theserver system 102 and executable by itsprocessor 108 can include amanagement application 114 and/or other applications. Themanagement application 114 can include at least one function for controlling resources executed at computing devices such ascomputing device 104, as described in detail below. Certain data may be stored in adata store 116 of thememory 110 that is part of and/or otherwise accessible to theserver system 102. The illustrateddata store 116 may be representative of a multiple data stores, as can be appreciated. The data stored in thedata store 116, for example, is associated with the operation of certain applications and/or functional entities described herein. Thedata store 116 may utilize strong encryption standards to protect theresources 202 from unauthorized access. For example, thedata store 116 may utilize Standard Hash Algorithm (“SHA-1”) and/or a similar strong encryption standard that may be utilized for server-side data storage. - Instructions stored in the
memory 120 of thecomputing device 104 and executable by itsprocessor 118 can include aclient application 124 and/or other applications. An application capable of receiving and/or rendering resources on adisplay device 128 is generally referred to herein as a “client application” 124. Certain data may be stored in adata store 126 of thememory 120 that is part of and/or otherwise accessible to thecomputing device 104. The illustrateddata store 126 may be representative of multiple data stores. The data stored in thedata store 126 may be associated with the operation of certain applications and/or functional entities described herein. - As used herein, the term “computer-executable program instructions” is used to refer to a program file that is in a form that can ultimately be run by a processor. Examples of computer-executable program instructions may be, for example, a compiled program that can be translated into machine code in a format that can be loaded into a random access portion of a memory and executed by a processor, source code that may be expressed in proper format such as object code that can be loaded into a random access portion of a memory and executed by a processor, source code that may be interpreted by another executable program to generate instructions in a random access portion of a memory and executed by a processor, and the like. The instructions may comprise processor-specific instructions generated by a compiler and/or an interpreter from code written in any suitable computer-programming language, including, for example, C, C++, C#, Visual Basic, Java, Python, Perl, JavaScript, and ActionScript. An executable program may be stored in any portion and/or component of a memory device such as, for example, RAM, ROM, a hard drive, solid-state drive, USB flash drive, memory card, optical disc such as compact disc (“CD”) and/or digital versatile disc (“DVD”), floppy disk, magnetic tape, and/or other memory components.
- The
network 106 facilitates communication between aserver system 102 and at least onecomputing device 104. Thenetwork 106 can include any suitable architecture for providing communication channels between thecomputing device 104 and theserver system 102. A communication channel can include any suitable means capable of communicating signals between thecomputing device 104 and aserver system 102. Non-limiting examples of thenetwork 106 include any type of wired network, wireless network, and/or a combination of wired and wireless networks. A wireless network may be a wireless local area network (“WLAN”), a wireless wide area network (“WWAN”), and/or any other type of wireless network now known and/or later developed. Additionally, thenetwork 106 may be and/or include the Internet, intranets, extranets, microwave networks, satellite communications, cellular systems, personal communication services (“PCS”), infrared communications, global area networks, and/or other suitable networks, etc., and/or any combination of two or more such networks. -
FIG. 2 is a modeling diagram depicting resources accessed by theclient application 124 and/or themanagement application 114 for authorizing the use ofresources 202 by thecomputing device 104, according to some embodiments. - The
client application 124 can include any software configured for communicating with themanagement application 114 and/or remotely managing thecomputing device 104. Theclient application 124 may access information from its associateddata store 126 such as adevice profile 212, at least one of thecredentials 214, adevice identifier 216, and other data. In some embodiments, thedevice profile 212 may include hardware, software, and security attributes that describe and/or otherwise identify thecomputing device 104. For instance, thedevice profile 212 may represent hardware specifications of thecomputing device 104, version and configuration information of various software programs and hardware components installed on thecomputing device 104, transport protocols enabled on thecomputing device 104, version and usage information of various other resources stored on thecomputing device 104, and/or any other attributes associated with the state of thecomputing device 104. Additionally, thedevice profile 212 may include data indicating a date of a last virus scan of thecomputing device 104, a date of a last access by an administrator entity, a date of a last access by theserver system 102, a date of a last service by an administrator entity, and/or any other data indicating a date of last maintenance. - The
credentials 214 may uniquely identify the user and/or other entity authorized to operate thecomputing device 104. For example, thecredentials 214 may include a username, a password, and/or biometric data related to facial recognition, retina recognition, fingerprint recognition, and the like. - The
device identifier 216 may uniquely identify thecomputing device 104. Thedevice identifier 216 may include a software identifier, a hardware identifier, and/or a combination of software and hardware identifiers. For example, thedevice identifier 216 may be a unique hardware identifier such as a Globally Unique Identifier (“GUID”), Universally Unique Identifier (“UUID”), Unique Device Identifier (“UDID”), serial number, Internationally Mobile Equipment Identity (“IMEI”), Wi-Fi Media Access Control (“MAC”) address, Bluetooth MAC address, a processing device identifier, and/or the like, and/or any combination of two or more such hardware identifiers. Thedevice identifier 216 may additionally or alternatively be represented by a unique software identifier such a token and/or certificate, based at least in part on the aforementioned unique hardware identifiers. - The
client application 124 may be executed to transmit requests to accessresources 202 stored at and/or accessible via theserver system 102. In some embodiments, theclient application 124 may be a secure container program that may be authorized to receive and render selectedresources 202, as described herein. In some embodiments, theclient application 124 may be a plug-in and/or additional software module for a browser and/or other application configured to be executed as described herein. - The
client application 124 and/or another application on acomputing device 104 managed by theclient application 124 may access theresources 202 via agraphical interface 210 or other suitable interface rendered on thedisplay device 128. Theresources 202 may be presented in agraphical interface 210 by decompressing compressed files and presenting the uncompressed files, by mounting disk image files and presenting the mounted image files, by running executable files and presenting the executed files, by enabling a data search of theresources 202 and presenting the featured output in a user interface, by calling on another application on thecomputing device 104 to respond to data links contained within theresources 202, and/or by transmitting a part and/or the whole of theresources 202 to another application on thecomputing device 104. - In some embodiments, a
client application 124 may be executed to present asingle resource 202. In some embodiments, aclient application 124 may be executed to present a series ofresources 202 in a comprehensive manner. A non-limiting example of presenting a series ofresources 202 in a comprehensive manner is presenting photograph files in a slideshow presentation. In some embodiments, theclient application 124 may be executed to render an environment that presentsmultiple resources 202 in a single view, such as a category-based tree and/or outline format, based at least in part on a resource qualifier associated with theresources 202. - The
client application 124 may also facilitate the modification ofresources 202 provided by themanagement application 114 and the modification of data associated with the providedresources 202, if thecomputing device 104 and/or its user are authorized to perform such actions. For example, theclient application 124 may include functionality for adding content to the existingresources 202, removing content from the existingresources 202, altering the content of existingresources 202, and/or the like, and/or any combination of manipulations of theresources 202. - The
client application 124 may further be executed to addnew resources 202 to be hosted by theserver system 102, if authorized. For example, a user having administrator-level credentials 214 may interact with an I/O device 130 to manipulate thegraphical interface 210 and thereby generate instructions to transfer copies ofresources 202 locally stored on thecomputing device 104 to theserver system 102 to be included in thedata store 116. In some embodiments, the user of thecomputing device 104 may initiate upload of at least one of theresources 202 via thegraphical interface 210 rendered by theclient application 124, as can be appreciated. In addition, the user may indicate approved resource-grouping identifiers 206 for identifying groups of entities and/or devices that are permitted to access the uploadedresource 202 and specifyrules 207 that may require compliance by a requesting entity in order to grant access to the uploadedresource 202 by the requesting entity, as will be described. In some embodiments, a user without administrator-level credentials 214 may manipulate thegraphical interface 210 to transfer local copies ofpersonal resources 202 to theserver system 102. In this example, resources qualifiers associated with thepersonal resources 202 may be configured by default to restrict access by any other user. - A management function of the
client application 124 can include optionally restricting access to theresources 202 by other applications executed by thecomputing device 104, thereby preventing access to theresources 202 from an application other than theclient application 124. In some embodiments, theclient application 124 may monitor network traffic between thecomputing device 104 and theserver system 102. Theclient application 124 may identify from the network traffic any data being transmitted between an application executed by thecomputing device 104 other than theclient application 124 and theserver system 102. Theclient application 124 may determine whether aresource 202 is being provided to an application other than theclient application 124 executed by thecomputing device 104. Theclient application 124 may intercept and/or block theincoming resource 202. In some embodiments, theclient application 124 may allow the interceptedresource 202 to be accessible to the user via agraphical interface 210 rendered by theclient application 124. In some embodiments, theclient application 124 may deny access to the interceptedresource 202 by any other application on thecomputing device 104. Additionally, theclient application 124 may be executed to call on other services associated with theresources 202 that are executed on theserver system 102 and/or another server and/or device accessible to theclient application 124, for instance, a technical support service that may be executed on theserver system 102. - Certain applications and/or other functionality may be executed in the
server system 102 according to some embodiments. The components executed on theserver system 102, for example, include themanagement application 114 and other applications, services, processes, systems, engines, and/or functionality not disclosed in detail herein. Themanagement application 114 is executed to provideresources 202 stored in thedata store 116 and/or provide access to resources accessible by theserver system 102. In addition, themanagement application 114 may also acceptnew resources 202 provided by the user of thecomputing device 104, and previously providedresources 202 modified by the user of thecomputing device 104, as will be described. Themanagement application 114 can also be executed to communicate at least one command to theclient application 124 for managing thecomputing device 104. - The
data store 116 may includeresources 202, resource-grouping identifiers 203, and/or other data. The resource-grouping identifiers 203 may represent unique identifiers for previously determined resource groupings and are used to determine whichresources 202 are served up to the user of thecomputing device 104, as will be described. For example, a resource grouping may relate to organizational groups, organizational roles, geographic locations, and/or any other type(s) of grouping(s) that require access to a type of resource. Eachresource grouping identifier 203 may be associated with a pairing of at least one of multiple approved credentials 204 and at least one of multiple approved device identifiers 205. In some embodiments, each combination of approved credentials 204 and approved device identifiers 205 may be associated with more than one of the resource-grouping identifiers 203. Additionally, the pairing of approved credentials 204 and approved device identifiers 205 may be associated with a user's organizational role and/or capacity. For instance, the pairing of approved credentials 204 and the approved device identifiers 205 may be predetermined by a technical services administrator and/or other administrative entity. In some embodiments, the pairing of approved credentials 204 and the approved device identifiers 205 may be automatically associated with the resource-grouping identifiers 203 based at least upon a user's pay grade, organizational level, status within the organization, and/or any other organizational factor. - Each
resource 202 may be associated with a listing of approved resource-grouping identifiers 206 and at least one of therules 207. In some embodiments, the listing of approved resource-grouping identifiers 206 includes at least some of the resource-grouping identifiers 203 that regulate access to therespective resource 202. In some embodiments, the listing of approved resource-grouping identifiers 206 may be predetermined by an administrator entity. For instance, the administrator entity may specify which of the resource-grouping identifiers 203 are permitted access to a respective at least one of theresources 202. Additionally or alternatively, rules 207 may regulate how an entity having a combination of theappropriate credentials 214 anddevice identifier 216 may access therespective resource 202. For example, in some embodiments, therules 207 may describe a required and/or a permitted state that an accessingcomputing device 104 may satisfy in order for thecomputing device 104 to be permitted access to theresource 202. Non-limiting examples ofrules 207 may include (but are not) limited to hardware requirements, software requirements, configuration requirements, maintenance requirements of a computing device, and/or requirements related to theresource 202. - In some embodiments, hardware requirements may include requirements associated with a processor of the
computing device 104, memory, power supply, external storage, peripherals, and/or the like. Software requirements may include requirements associated with the operating system type and version, operating system authenticity and jailbreak/rooted status, installed application types and versions, and/or the like. Configuration requirements may include requirements associated with the configuration of the hardware, software, data encryption methods, transport protocols, and/or the like. Maintenance requirements may include requirements associated with the date of last virus scan for thecomputing device 104, the date of the last access of thecomputing device 104 by an administrative entity, the date of last communication between thecomputing device 104 and theserver system 102, the date of last tune-up of thecomputing device 104, and/or the like. Requirements related to theresource 202 may include whether theresources 202 may be rendered while thecomputing device 104 is offline and/or not in communication with themanagement application 114, whether to permit synchronization of theresources 202 with a remote data store, whether to restrict theresources 202 from being forwarded, whether to permit storingresources 202 locally on thecomputing device 104, and/or the like. Alternatively, theresources 202 andrules 207 may be stored on another data store accessible to thecomputing device 104 and/or other storage facility in data communication with theserver system 102, such as an internal email server, a web-based email server, an internal file server, a third-party hosted file server, a cloud-based server, and/or a cached local data store on thecomputing device 104. - Each
resource 202 may be associated with at least one of theresource qualifiers 208. In some embodiments, aresource qualifier 208 may be and/or include metadata that describes and/or regulates the use of a respective at least one of theresources 202. For example, aresource qualifier 208 may include categories/sub-categories to which at least one of theresources 202 belong, an indication that at least one of theresources 202 are considered favorites, an indication of whether at least one of theresources 202 are privately owned, publicly owned, and/or enterprise-owned, an indication of whether at least one of theresources 202 are confidential, an indication of whether at least one of theresources 202 are password protected, an indication of the historical version of at least one of theresources 202, a description of at least one of theresources 202, at least one comment regarding at least one of theresources 202, an indication of the size and format of at least one of theresources 202, an indication of the download priority associated with at least one of theresources 202, an indication of the expiration date associated with at least one of theresources 202, an indication of the effective date associated with at least one of theresources 202, an indication of the ownership of at least one of theresources 202, an indication of the managing party of at least one of theresources 202, and/or the like, and/or any combination of resource qualifiers. - A user and/or other entity operating a
computing device 104 may wish to accessresources 202 stored on theserver system 102. In some embodiments, the user may manipulate agraphical interface 210 rendered by theclient application 124 to transmit arequest 218 for accessing at least one of theresources 202 on theserver system 102. For instance, the user may providecredentials 214, such as, a unique user name, a password, biometric data, and/or other types ofcredentials 214 to request access to theserver system 102. Theclient application 124 may transmit therequest 218 to themanagement application 114. In some embodiments, therequest 218 may include thecredentials 214 provided by the user, thedevice identifier 216 that uniquely identifies thecomputing device 104, and/or any other relevant information. - The
management application 114 and/or another service provided by theserver system 102 receives therequest 218 and determines whether the user is authorized to access theresources 202 from thecomputing device 104. For example, themanagement application 114 may determine that the user is authorized to access theresources 202 from thecomputing device 104 based on thecredentials 214 and thedevice identifier 216 provided with therequest 218. - Upon determining that the user is authorized to access the
resources 202 from thecomputing device 104, theserver system 102 determines which of theresources 202 to provide to thecomputing device 104. In some embodiments, themanagement application 114 determines whichresources 202 to provide based on resource-grouping identifiers 203 associated with eachresource 202. For instance, themanagement application 114 may determine which resource-grouping identifiers 203 are associated with the pairing ofcredentials 214 and thedevice identifier 216 included in therequest 218. In some embodiments, themanagement application 114 parses the listing of approved credentials 204 and the listing of approved device identifiers 205 of each resource grouping identifier to determine whether the respective resource grouping identifier is associated with both thecredentials 214 and thedevice identifier 216. Themanagement application 114 may identify aresource 202 to provide to thecomputing device 104 based on the determined resource-grouping identifiers 203. In some embodiments, themanagement application 114 identifies at least one of theresources 202 associated with each one of the determined resource-grouping identifiers 203. In some embodiments, themanagement application 114 identifies aresource 202 that is associated with the determined resource-grouping identifiers 203. Additionally, in some embodiments, themanagement application 114 identifies theresource 202 if it is associated with a threshold number of the resource-grouping identifiers 203. Themanagement application 114 may provide the identifiedresources 202 to the user of thecomputing device 104. - In some embodiments, the
management application 114 may additionally determine whether thecomputing device 104 from which the user requested access to theresources 202 complies with therules 207 associated with each one of the identifiedresources 202. For example, themanagement application 114 may determine whether thedevice profile 212 describing the state of thecomputing device 104 complies with therules 207 of each identifiedresource 202. As discussed above, thedevice profile 212 may include hardware specifications of thecomputing device 104, software specifications of thecomputing device 104, version information of various other components of thecomputing device 104, and/or any other information profiling thecomputing device 104. In some embodiments, themanagement application 114 may provide each identifiedresource 202 to the user if thecomputing device 104 complies with all of, or at least a portion of, therules 207 associated with each of the identifiedresources 202. Additionally, in some embodiments, themanagement application 114 may provide the identified resource(s) 165 to the user if thecomputing device 104 complies with at least a threshold number of therules 207 associated with each of the identifiedresources 202. - Responsive to a determination that the
computing device 104 is in a state of compliance with therules 207, themanagement application 114 may be further executed to transmit the identifiedresources 202 to thecomputing device 104. In some embodiments, themanagement application 114 may automatically transmit the identifiedresources 202 to thecomputing device 104. In some embodiments, themanagement application 114 may make the identifiedresources 202 available for download by thecomputing device 104 based on a resource qualifier associated with therespective resource 202. For instance, the resource qualifier may indicate therespective resource 202 be made available for download to thecomputing device 104. In this example, the user may transmit a request to themanagement application 114 to download therespective resource 202. - In some embodiments, the state of the
computing device 104 may have been modified between the time themanagement application 114 makes the identifiedresource 202 available for download and the time themanagement application 114 receives the request to download the identifiedresource 202. For example, thecomputing device 104 may have switched connectivity from asecured network 106 to anunsecured network 106. In this embodiment, themanagement application 114 may determine for a second time whether thecomputing device 104 complies with therules 207. For example, the request to download transmitted from thecomputing device 104 may include an updateddevice profile 212. Themanagement application 114 may make the second determination of whether thecomputing device 104 complies with therules 207 based on the updateddevice profile 212. For instance, therules 207 may require that thecomputing device 104 be connected to asecured network 106 to gain access to the resource and the second determination of compliance may reveal that thecomputing device 104 is connected to anunsecured network 106. Responsive to the second determination that thecomputing device 104 complies with therules 207, themanagement application 114 provides the requestedresource 202. In some embodiments, theclient application 124 may managecomputing device 104 on behalf of themanagement application 114 by periodically transmitting thedevice profile 212 to theserver system 102. In this embodiment, each time thedevice profile 212 is transmitted to theserver system 102, themanagement application 114 may determine whether the updatedcomputing device 104 complies with therules 207 using the updateddevice profile 212. - In some embodiments, the
management application 114 may transmitrules 207 associated with each one of the identifiedresources 202 to thecomputing device 104. For example, themanagement application 114 may transmit therules 207 to theclient application 124 involved in managing thecomputing device 104 for determining whether thecomputing device 104 complies with therules 207. In some embodiments, themanagement application 114 may not determine whether thecomputing device 104 complies with therules 207 of each of the identifiedresources 202 and instead permits theclient application 124 to make this determination. For instance, theclient application 124 may determine whether thecomputing device 104 complies with therules 207 associated with the receivedresource 202 prior to rendering the receivedresource 202 on thedisplay device 128. - In some embodiments, the
management application 114 may transmit therules 207 to thecomputing device 104 prior to transmitting the identifiedresources 202. Theclient application 124 may determine whether thecomputing device 104 complies with therules 207, as described above. Theclient application 124 may transmit an indication back to themanagement application 114 of the compliance status. Responsive to receiving an indication from thecomputing device 104 that thecomputing device 104 complies with all and/or a sufficient portion of therules 207 associated with eachrespective resource 202, themanagement application 114 may transmit the appropriate identifiedresources 202 to thecomputing device 104. Additionally, theclient application 124 may store therules 207 in a memory associated with thecomputing device 104, such as thedata store 126. Uponsubsequent requests 218 to access the identifiedresource 202, themanagement application 114 may wait to receive an indication from theclient application 124 that thecomputing device 104 complies with therules 207 associated with the requestedresource 202 to determine whether to transmit the requestedresource 202. For example, theclient application 124 may use the storedrules 207 received from a previous request to make the determination and transmit therequest 218. - The
management application 114 may be further executed to log activity related to theresources 202 for asset tracking purposes. For example, themanagement application 114 may log activities such as transmission of resources, historical data related to the transmission of the resource, data related to the rendering of theresources 202 by thecomputing device 104, data related to a storage location of theresources 202, data related to communication with thecomputing device 104, data related to resource qualifiers associated with theresources 202, data related tocomputing device 104 compliance withrules 207, data related to usage and availability of bandwidth, and/or any other data related to theresources 202. - In an additional embodiment, the
management application 114 may periodically determine whether the transmittedresources 202 have been modified on thecomputing device 104. Themanagement application 114 may synchronize the modifiedresource 202 on thecomputing device 104 with theunmodified resource 202 on theserver system 102. For instance, themanagement application 114 may determine whether theresource 202 has been modified based on an edit date, modified date, and/or an access date associated with theresource 202. In this embodiment, themanagement application 114 may periodically request to receive the relevant date from theclient application 124. Upon receiving the relevant date, themanagement application 114 compares the relevant date from thecomputing device 104 with the corresponding date on theserver system 102 and determines to synchronize therespective resources 202 if the two relevant dates do not match. For instance, themanagement application 114 may employ a synchronization approach as is known in the art. In some embodiments, themanagement application 114 may employ the synchronization approach based on determining whether the user is permitted to modify theresource 202 on thecomputing device 104. In some embodiments, themanagement application 114 may remove theresource 202 on thecomputing device 104 upon synchronizing with theserver system 102. In some embodiments, themanagement application 114 stores the modifiedresource 202 in thedata store 116 as one of multiple versions of therespective resource 202. - In some embodiments, the
client application 124 may be pre-authorized to access at least some of theresources 202 hosted by theserver system 102. In such embodiments, themanagement application 114 may be configured to provide to theclient application 124 a listing ofresources 202 available for download by thecomputing device 104 based only on certain embedded authorization data (e.g.,device identifier 216, and/ordevice profile 212, etc.) and without requiring theclient application 124 to provide additional authorization data (e.g., user name and password). For example, themanagement application 114 may identifyresources 202 to include in the listing by determining which of theresources 202 are associated withrules 207 that correspond with thedevice profile 212 of thecomputing device 104. Themanagement application 114 may allow theclient application 124 to download at least some of theavailable resources 202. However, at least one of theavailable resources 202 may be associated with a distribution rule that requires additional authorization. For instance, theresource 202 may be a document containing sensitive information that requires authorization of a username and password and/or other additional authorization data. Thus, if theclient application 124 submits a request to download such aresource 202, themanagement application 114 may prompt theclient application 124 to provide additional authorization data. In response, theclient application 124 may prompt the user to providecredentials 214. In some embodiments, theclient application 124 may transmit thecredentials 214 and/or thedevice identifier 216 of thecomputing device 104 to themanagement application 114. Upon determining that the user is authorized to access thesensitive resource 202 from thecomputing device 104, themanagement application 114 may allow theclient application 124 to download thesensitive resource 202. - Although the
management application 114,client application 124, and other various systems described herein may be embodied in software and/or code executed by general purpose hardware as discussed above, as an alternative the same may also be embodied in dedicated hardware and/or a combination of software/general purpose hardware and dedicated hardware. If embodied in dedicated hardware, each can be implemented as a circuit and/or state machine that employs any one of or a combination of a number of technologies. These technologies may include, but are not limited to, discrete logic circuits having logic gates for implementing various logic functions upon an application of at least one of data signals, application specific integrated circuits having appropriate logic gates, and/or other components, etc. Such technologies are generally well known by those skilled in the art and, consequently, are not described in detail herein. - The
management application 114 executed at theserver system 102 can control the use ofresources 202 and other electronic content accessed via an electronic meeting betweenmultiple computing devices 104, as described in detail with respect toFIGS. 3-6 . -
FIG. 3 is a modeling diagram depicting an example flow of communications among amanagement application 114 andmultiple computing devices 104 a-c accessing anelectronic meeting 302. - The
electronic meeting 302 can include at least one function for sharingresources 202 provided by theserver system 102 and/or other electronic content. For example, entities accessing theelectronic meeting 302 may transmit copies ofresources 202 among thecomputing devices 104 a-c, render theresources 202 for display at thecomputing devices 104 a-c, and/or making theresources 202 available for use at least one of thecomputing devices 104 a-c. - The
electronic meeting 302 may be hosted via theserver system 102 and/or another server system with which themanagement application 114 can communicate. In some embodiments, acommunication application 303 configured to access theresources 202 may host theelectronic meeting 302, as depicted inFIG. 3 . Themanagement application 114 can moderate requests for access toresources 202 transmitted by thecommunication application 303. Moderating requests for access to theresources 202 can include ensuring thatresources 202 are provided via theelectronic meeting 302 to computingdevices 104 a-c according to anyapplicable rules 207, as described above with respect toFIG. 2 . Thecommunication application 303 can retrieve and/or otherwise access theresources 202 on behalf of the participating entities 304 a-c and/or provide the resources to thecomputing devices 104 a-c via theelectronic meeting 302. Additionally or alternatively, thecommunication application 303 can receiverequests 218 forresources 202 from thecomputing devices 104 a-c via theelectronic meeting 302 and transmit the requests to themanagement application 114, which can transmit the requestedresources 202 to the requesting devices. In some embodiments, themanagement application 114 may host theelectronic meeting 302. -
Computing devices 104a -c accessing resources 202 via an electronic meeting may be authenticated, managed, and/or otherwise determined to be compliant withrules 207 via any suitable manner. - In some embodiments, the
client applications 124 a-c may include at least one electronic meeting function via which thecomputing devices 104 a-c may respectively access and/or establish anelectronic meeting 302. Theclient applications 124 a-c may be installed on therespective computing devices 104 a-c prior to theelectronic meeting 302 being established. If an instance of theclient application 124 is not installed to a computing device, the computing device may be unable to access theelectronic meeting 302 and/or communicateresources 202 and/or other electronic content via theelectronic meeting 302. - In some embodiments, a dedicated electronic meeting application other than the
client application 124 can be used to establish and/or access theelectronic meeting 302. The dedicated electronic meeting application may be required to communicate with themanagement application 114 via theelectronic meeting 302 via theclient application 124. Theclient application 124 may be a plug-in module added to the dedicated electronic meeting application and/or a separate application used for accessing and/or communicatingresources 202 via theelectronic meeting 302. Acomputing device 104 may be able to access theelectronic meeting 302 the dedicated electronic meeting application without theclient application 124 if thecomputing device 104 does not access theresources 202 provided by theserver system 102. Themanagement application 114 may push and/or otherwise provide theclient application 124 to computing devices on which theclient application 124 is not installed in response to the computing device requesting access to theresources 202 via theelectronic meeting 302. The instance of theclient application 124 may automatically be installed to thecomputing device 104 without intervention by an operator of thecomputing device 104. Additionally or alternatively, thecomputing device 104 may provide a prompt to the operator requesting authorization to install the instance of theclient application 124. Upon the operator affirming that theclient application 124 may be installed, thecomputing device 104 can install the instance of theclient application 124. - In some embodiments, the
management application 114 can automatically establish theelectronic meeting 302 based on the presence ofcomputing devices 104 a-c corresponding to entities permitted to access theelectronic meeting 302. Themanagement application 114 can search for a beacon and/or other identification signal broadcasted and/or otherwise transmitted by each of thecomputing devices 104 a-c. The beacon and/or other identification signal can identify the computing device as being available for theelectronic meeting 302. Themanagement application 114 can search for the beacon at predetermined times during a time period in which theelectronic meeting 302 is scheduled to occur and/or continuously search for the beacon during the time period. In some embodiments, themanagement application 114 can broadcast a discovery signal. The discovery signal can be received by thecomputing devices 104 a-c at which theclient applications 124 a-c are respectively executing. Each of theclient applications 124 a-c can transmit a response to the discovery signal. The response can notify themanagement application 114 that thecomputing devices 104 a-c are available to join theelectronic meeting 302. At least one of theclient applications 124 a-c may automatically transmit a response to themanagement application 114 without intervention by respective operators of thecomputing devices 104 a-c. Additionally or alternatively, at least one of theclient applications 124 a-c may provide a prompt to the respective operator and transmit a response to themanagement application 114 based on the respective operator affirming that he and/or she wishes to join theelectronic meeting 302 - The
client applications 124 a-c may transmit data via theelectronic meeting 302 identifying the entities 304 a-c accessing and/or requesting access to theelectronic meeting 302. The entities 304 a-c can be identified by any suitable identifier, such as adevice profile 212, at least one ofcredentials 214, adevice identifier 216, and/or a combination thereof. In some embodiments, an identifier for an entity can identify the operator of a computing device. The identifier can include a user name for the operator. In some embodiments, an identifier for an entity can identify the computing device accessing requesting access to the electronic meeting. Non-limiting examples of identifiers for computingdevices 104 a-c include an internet protocol (“IP”) address and/or a MAC address. In some embodiments, an entity may identified by a pairing of an operator identifier and a device identifier. - The
management application 114 may obtaindata 306 from theelectronic meeting 302 identifying the entities 304 a-c, such as thedevice profile 212, at least one ofcredentials 214, adevice identifier 216, and/or a combination thereof provided by each of theclient applications 124 a-c. In some embodiments, thecommunication application 303 can push thedata 306 to themanagement application 114. In some embodiments, themanagement application 114 can pull and/or otherwise retrieve thedata 306 from thecommunication application 303. - The
management application 114 may authenticate and/or otherwise identify each of the entities 304 a-c accessing and/or requesting access to theelectronic meeting 302 from thedata 306. The management application can access alisting 308 stored in thedata store 116. The listing 308 can include a list of entities that are required to participate in theelectronic meeting 302 in order for themanagement application 114 to authorize the communication of at least one of theresources 202 and/or other electronic content. For example, as depicted inFIG. 3 , theentities electronic meeting 302. The listing 308 can also include a list of other entities that are authorized to access theelectronic meeting 302. For example, as depicted inFIG. 3 , theentity 304 c is listed as an authorized participant. Themanagement application 114 may not require the participation of theentity 304 c (i.e., an authorized but not required entity) in theelectronic meeting 302 as a prerequisite to communication of at least one of theresources 202 and/or other electronic content among the entities 304 a-c. In some embodiments, authorized but not required entities (e.g.,entity 304 c) may not have access to some or all of theresources 202 and/or other electronic content made available to required entities (e.g.,entities - Any suitable mechanism and/or process can be used for authorizing communication of the at least one of the
resources 202 and/or other electronic content among the entities 304 a-c via theelectronic meeting 302. For example, themanagement application 114 can authorize the communication of theresources 202 and/or other electronic content by respectively providing tokens 310 a-c to theclient applications 124 a-c, as depicted inFIG. 3 . The tokens 310 a-c can include an authorization to access theresources 202 and/or other electronic content from thedata store 116 of theserver system 102 and/or another server system in communication with themanagement application 114. The tokens 310 a-c can respectively identify that requests for theresources 202 from the entities 304 a-c, theclient applications 124 a-c, and/or thecomputing device 104 a-c are to be granted. In some embodiments, the tokens 310 a-c can specify permissions (e.g., read, write, copy, etc.) for using theresources 202 and/or other electronic content. The tokens 310 a-c can additionally or alternatively include data specifying that the use of theresources 202 and/or other electronic content is authorized during a scheduled time period for the electronic meeting. - In some embodiments, the
management application 114 can perform at least one action enforcing the conditions specified in the tokens 310 a-c as described above with respect toFIG. 2 . For example, themanagement application 114 can add the tokens 310 a-c to the approved credentials 204 in thedata store 116. Each of thecomputing devices 104 a-c can add a respective one of the tokens 310 a-c to thecredentials 214. In response to arequest 218 that includes one of the tokens 310 a-c withcredentials 214, themanagement application 114 may determine resource-grouping identifiers 203 based on thecredentials 214 of the requesting entity and/or thedevice identifier 216 of thecomputing device 104 corresponding to the entity. For example, eachresource grouping identifier 203 may be associated with a pairing of credentials 214 (including at least one of the tokens 310 a-c) and adevice identifier 216. Themanagement application 114 may determine at least one of resource-grouping identifiers 203 associated with the pairing ofcredentials 214 and thedevice identifier 216. Themanagement application 114 can identify theresources 202 that are associated with the determined resource-grouping identifiers 203. Themanagement application 114 can determine whether acomputing device 104 from which therequest 218 originated complies with therules 207 associated with each one of the identifiedresources 202. If themanagement application 114 determines that thecomputing device 104 complies with therules 207, themanagement application 114 can transmit the identifiedresources 202 associated with therules 207 via theelectronic meeting 302. In some embodiments, themanagement application 114 automatically transmits the identifiedresources 202 that thecomputing device 104 is authorized to receive. In some embodiments, themanagement application 114 may make the identifiedresources 202 available for download. For example, acomputing device 104 may receive an indication that theresource 202 is available for download. Thecomputing device 104 may transmit a request to themanagement application 114 for downloading theapplicable resource 202. Upon receiving the request, themanagement application 114 may transmit theresource 202 to thecomputing device 104. - In some embodiments, the
client applications 124 a-c can manage thecomputing devices 104 a-c based on the conditions specified in the tokens 310 a-c. For example, aclient applications 124 may block attempts to accessresources 202 in violation of the conditions specified in the tokens 310 a-c. Theclient application 124 may receive at least one of therules 207 from theserver system 102 along with the token. Each of the receivedrules 207 may be associated with at least one of theresources 202 identified in the token. Theclient application 124 can determine compliance with the at least one of therules 207 received by the client application (e.g., based on thedevice profile 212 for the requesting computing device). If theclient application 124 determines a request to accessresources 202 via theelectronic meeting 302 is not compliant with some and/or all of the receivedrules 207, theclient application 124 can render a notice of non-compliance on adisplay device 216 of thecomputing device 104. Theclient application 124 may additionally or alternatively transmit a notification to themanagement application 114 indicating that thecomputing device 104 is non-compliant. If theclient application 124 determines that the request to accessresources 202 via theelectronic meeting 302 is compliant with all and/or a portion of the sets ofrules 207, theclient application 124 can transmit a notification of compliance to themanagement application 114. Theclient application 124 can obtain theresources 202 associated with therules 207 with which the requestingcomputing device 104 complies. Theresources 202 may be obtained via theelectronic meeting 302. - In some embodiments, the
management application 114 can authorize the communication of electronic content by granting access to theresources 202 and/or other electronic content by thecommunication application 303. For example, themanagement application 114 may provide a token to thecommunication application 303 and/or add a temporary credential for thecommunication application 303 to the approved credentials 204 stored in thedata store 116. In some embodiments, the token and/or temporary credential may be valid for a particular period of time corresponding to a scheduled start time and/or end time for theelectronic meeting 302. - In some embodiments, the
management application 114 can implement at least one security measure to prevent unauthorized entities from accessing electronic content communicated via theelectronic meeting 302.FIG. 4 is a modeling diagram depicting an example flow of communications among themanagement application 114, thecomputing devices 104 a-c, and an unauthorized entity. - Each of the
computing devices 104 a-c can respectively access theelectronic meeting 302 via the connections 404 a-c. Anothercomputing device 402 can attempt to access the meeting and/or be otherwise detected by themanagement application 114. Thisother computing device 402 can correspond to anunauthorized entity 406. In some embodiments, themanagement application 114 can detect anunauthorized entity 406 accessing and/or attempting to access theelectronic meeting 302, as depicted inFIG. 4 by thecomputing device 402 identifying theentity 406 to theelectronic meeting 302. The management application can receivedata 408 identifying theentity 406. In some embodiments, themanagement application 114 can detect theunauthorized entity 406 based on data received via a communication channel other than theelectronic meeting 302, as depicted inFIG. 4 by thecomputing device 402 communicating thedata 406′ identifying theunauthorized entity 406. Thedata 406′ may be received via a router and/or other network communication device providing network connectivity to thecomputing devices 104 a-c and thecomputing device 402. For example, themanagement application 114 may receive thedata 406′ from a router and/or other network communication device via a direct connection between the router and theserver system 102 and/or a connection with another server system in communication with the router. - The
management application 114 can determine that theentity 406 and/or thecomputing device 402 are not authorized to access theelectronic meeting 302 via any suitable process. In one non-limiting example,management application 114 can determine that theentity 406 is not included in thelisting 308. In another non-limiting example, themanagement application 114 can determine that authentication data for the entity 406 (e.g., a user name and/or password) is invalid. In another non-limiting example, themanagement application 114 can determine that thecomputing device 402 corresponding to theunauthorized entity 406 fails to comply with at least one of therules 207 and/or another rule governing access to theresources 202. - The
management application 114 can restrict communication of at least one of theresources 202 and/or other electronic content based on determining that theentity 406 is not authorized to access theelectronic meeting 302. In some embodiments, restricting the communication of electronic content can include restricting thecomputing devices 104 a-c and/or the entities 304 a-c to communicating a subset of electronic content. For example, anelectronic meeting 302 that involves sharing both publiclyavailable resources 202 and secret and/or otherwisesensitive resources 202 may be restricted to sharing only the publiclyavailable resources 202 in the presence of theunauthorized entity 406. In some embodiments, restricting the communication of electronic content can include barring any communication of electronic content in the presence of theunauthorized entity 406. - Any suitable mechanism and/or process can be used for restricting communication of the at least one of the
resources 202 and/or other electronic content among the entities 304 a-c. In some embodiments, themanagement application 114 can restrict the communication of theresources 202 and/or other electronic content by respectively providing updated tokens 410 a-c to theclient applications 124 a-c to replace tokens 310 a-c, as depicted inFIG. 4 . In one non-limiting example, the tokens 410 a-c can include an authorization to access fewer of theresources 202 as compared to the tokens 310 a-c. In another non-limiting example, the tokens 410 a-c can specify permissions (e.g., read, write, copy, etc.) for using theresources 202 and/or other electronic content that are more restrictive as compared to permissions specified by the tokens 310 a-c. The conditions specified in the tokens 410 a-c can be enforced by theclient applications 124 a-c, themanagement application 114, and/or some combination thereof as described above with respect toFIG. 3 . - In some embodiments, the
management application 114 can restrict the communication of theresources 202 and/or other electronic content by restricting access to theresources 202 and/or other electronic content by thecommunication application 303. For example, themanagement application 114 may invalidate any tokens previously provided to thecommunication application 303 and provide a new token to thecommunication application 303 that specifies a more restrictive permission level and/or subset ofresources 202 that thecommunication application 303 may access. - In some embodiments, the
management application 114 can restrict communication of theresources 202 and/or other electronic content based on a required entity leaving theelectronic meeting 302 and/or a computing device corresponding to a required entity leaving theelectronic meeting 302 and/or a specified geographic area. - In some embodiments, the
management application 114 can direct the communication application to terminate theelectronic meeting 302 based on a required entity leaving the meeting, a computing device corresponding to a required entity leaving a specified geographic area in which thecomputing device 104 a-c are positioned, anunauthorized entity 406 accessing and/or attempting to access the electronic meeting, and/or anunauthorized computing device 402 entering a specified geographic area in which thecomputing device 104 a-c are positioned. - In some embodiments, the
management application 114 can perform a remedial action in response to detecting anunauthorized entity 406 and/or anunauthorized computing device 402 for acomputing device 402 that can be managed by themanagement application 114. A remedial action can include at least one security measure for preventing theunauthorized entity 406 from accessing theresources 202. A remedial action can be specified at least one rule stored in thedata store 116 and governing access to theresources 202. An instance of theclient application 124 may be installed on thecomputing device 402. Theapplication 124 may include at least one management function for managing thecomputing device 402 in response to commands received from themanagement application 114. Theclient application 124 can perform the remedial actions at thecomputing device 402 in response to commands from themanagement application 114. - The remedial action can include transmitting
data 412 to thecomputing device 402. In some embodiments, thedata 412 can include command to aclient application 124 executing on thecomputing device 402. The command can direct the client application to erase some or all content from the computing device 402 (i.e., perform a “device wipe”). In some embodiments, thedata 412 can include a software update to be installed on thecomputing device 402. The software update can update thecomputing device 402 such that thecomputing device 402 is compliant with at least one rule governing access to theresources 202. - In some embodiments, the remedial action can involve notifying an administrative entity of the presence of the
unauthorized entity 406 and/or theunauthorized computing device 402. For example, the presence of anunauthorized computing device 402 detected in the vicinity of thecomputing devices 104 a-c may trigger an alert to an administrator and/or security personnel. The administrator and/or security personnel may respond by escorting the user of theunauthorized computing device 402 from the premises. - In some embodiments, each of the
computing devices 104 a-c may be positioned in a geographical location in which network connectivity is provided by at least one network communication device that can be controlled by themanagement application 114. For example, network device(s), such as routers and/or computing systems in communication with routers, may provide network connectivity to thecomputing devices 104 a-c accessing theelectronic meeting 302. Themanagement application 114 may communicate with the network communication device(s) via another computing system configured to control the network communication device(s), such as a server system providing network connectivity between thecomputing devices 104 a-c and theserver system 102. Themanagement application 114 may be able to restrict the operations of theunauthorized computing device 402 by communicating a command to the network communication device(s). The command communicated to the network communication device(s) can identify the computing device(s) 402 via any suitable identifier, such as an IP address and/or a MAC address. The command can direct the network communication device(s) to restrict and/or deny network access by the computing device(s) 402. -
FIG. 5 is a flow chart illustrating anexample method 500 for controllingresources 202 and/or other electronic content communicated among computingdevices 104 a-c. For illustrative purposes, themethod 500 is described with reference to the system implementations depicted inFIGS. 1-2 and the flows of communication depicted inFIGS. 3-4 . Other implementations, however, are possible. - The
method 500 involves identifying multiple entities available for communicating electronic content via an electronic meeting and/or other form of electronic communication, as shown inblock 510. For example, theprocessor 108 of theserver system 102 can execute themanagement application 114 to identify thatentities management application 114 can identify the requiredentities listing 308. - The
method 500 further involves determining that determining that each of a required subset entities is available for communication via the electronic meeting and/or other form of electronic communication, as shown inblock 520. For example, themanagement application 114 can determine that the requiredentities electronic meeting 302. In some embodiments, the required subset of entities can include multiple entities whose availability is mandatory. In some embodiments, the required subset of entities can include a required number of entities (such as, but not limited to, a quorum) without requiring any specific entity be available. In some embodiments, the required subset of entities can include at least one mandatory entity and at least one additional entity selected from a group of required entities. For example, authorizing electronic communication may require the participation and/or availability of anentity 304 a as well the participation and/or availability of either anentity 304 b or anentity 304 c. The participation and/or availability ofentities entities - Determining that the required
entities electronic meeting 302 can include authenticating the requiredentities respective client applications client applications client applications management application 114. In some embodiments, theclient applications management application 114. Themanagement application 114 can verify the authentication data provided by theclient applications - In some embodiments, authentication data can include information provided by the required
entities client applications entities - In some embodiments, the authentication data can include biometric information associated with each of the required
entities entity 304 a using acomputing device 104 a may access fingerprint scanning function provided by theclient application 124 a and/or another application. The requiredentity 304 a may scan at least one of his and/or her fingerprints. - In some embodiments, determining that the required
entities electronic meeting 302 can include determining that therespective client applications computing devices network 106. For example, each of thecomputing devices management application 114 can identify thecomputing devices entities computing devices 104 a-c. - In some embodiments, determining that each of the required
entities electronic meeting 302 comprises determining that each of thecomputing devices management application 114 may identify the common geographical location by reference to a file and/or other data stored in adata store 116. The common geographical location can be defined in any suitable manner. In some embodiments, a common geographical location may be delineated by fixed boundaries. In some embodiments, a common geographical location may be defined by a proximity to at least one reference location, such as (but not limited to) a distance from at least one base station in a telecommunication system and/or access points in a wireless data network. - The
management application 114 can determine that thecomputing devices entities management application 114 can detect and/or otherwise determine that each computing device is registered with the management application via a sensing device positioned in the common geographic location. For example, one or more radio-frequency identification (“RFID”) scanners may be positioned at one or more respective locations in a geographic location. Each of thecomputing devices management application 114, thereby allowing themanagement application 114 to identify the scannedcomputing device 104. In some embodiments, a control device can be configured to detect that thecomputing devices 104 a-c are positioned in the common geographic location by establishing radio communication with thecomputing devices computing devices computing devices management application 114 can detect and/or otherwise determine that thecomputing devices computing devices management application 114 can determine thatcomputing devices - In some embodiments, the
management application 114 can determine that a requiredentity management application 114 can restrict the communication of at least one of theresources 202 and/or other electronic content based on the participating required entity leaving the common geographical location. For example, themanagement application 114 may periodically update a stored list of the respective locations of thecomputing devices 104 a-c. Themanagement application 114 may determine during a first time period that acomputing device 104 a corresponding to a requiredentity 304 a is positioned within the common geographical location. Themanagement application 114 may authorize communication of at least one of theresources 202 and/or other electronic content via theelectronic meeting 302 during the first time period. Themanagement application 114 may determine during a second time period that thecomputing device 104 a is positioned outside the common geographical location. Themanagement application 114 may restrict communication of at least one of theresources 202 and/or other electronic content via theelectronic meeting 302 during the second time period. - The
method 500 further involves authorizing a communication of the electronic content among the requiredentities entities 304 c via the electronic meeting and/or other form of electronic communication based on determining that each of the entities is available for communication, as shown inblock 530. For example, themanagement application 114 can authorize theclient applications 124 a-c accessing theelectronic meeting 302 to communicate at least one of theresources 202 provided by theserver system 102 and/or other electronic content, as described above with respect toFIG. 3 . - In some embodiments, the
management application 114 can authorize theclient applications 124 a-c to communicate at least one of theresources 202 and/or other electronic content by decrypting the electronic content for use during theelectronic meeting 302. The electronic content may be encrypted using an encryption key provided by the requiredentities entities entities electronic meeting 302. For example, the portions of the encryption key may be stored on thecomputing devices client applications entities electronic meeting 302. Theclient applications management application 114. Themanagement application 114 can combine and/or perform other operations on the portions of the encryption key into the encryption key and decrypt content to be shared via theelectronic meeting 302. In one non-limiting example, a 256-bit key or other key can be partitioned. Each partition can be provided to a respective entity. Themanagement application 114 can receive each partition and parse or otherwise combine the partitions to obtain an operable 256-bit key. In another non-limiting example, a 256-bit key or other key can be partitioned. Each partition can be provided to a respective entity. Themanagement application 114 can receive each partition and execute an algorithm using the partitions to obtain an operable 256-bit key. - In some embodiments, the
management application 114 can authorize theclient applications 124 a-c to communicate at least one of theresources 202 and/or other electronic content based on secondary authentication information generated from authentication data provided by the requiredentities entities electronic meeting 302. In some embodiments, generating secondary authentication data can include generating authentication data that is different from the separate authentication data received from the requiredentities entities electronic meeting 302. - In some embodiments, the
management application 114 can detect anadditional entity 406 that lacks an authorization for accessing theelectronic meeting 302. Themanagement application 114 can restrict the communication of at least some of the electronic content among at least some of the entities 304 a-c based on detecting theadditional entity 406, as described above with respect toFIG. 4 . - In some embodiments, the
management application 114 can determine that theentities electronic meeting 302 via authorizedcomputing devices management application 114 can permit communication of theresources 202 and/or other electronic content based on determining that each of thecomputing devices electronic meeting 302. Determining that each of thecomputing device electronic meeting 302 can include, for example, determining that eachcomputing device rules 207. -
FIG. 6 is a flow chart illustrating anexample method 600 for restricting access toresources 202 and/or other electronic content communicated among computingdevices 104 a-c based on the presence of anunauthorized entity 406. For illustrative purposes, themethod 600 is described with reference to the system implementations depicted inFIGS. 1-2 and the flows of communication depicted inFIGS. 3-4 . Other implementations, however, are possible. - The
method 600 involves identifying multiple entities authorized to electronically communicate with one another, as shown inblock 610. For example, theprocessor 108 of theserver system 102 can execute themanagement application 114 to identify that the entities 304 a-c are authorized to access theelectronic meeting 302. Themanagement application 114 can identify that the entities 304 a-c are authorized to access theelectronic meeting 302 by, for example, referencing alisting 308 and/or by verifying that the entities 304 a-c have provided valid authentication data. - The
method 600 further involves detecting an additional entity that lacks an authorization for communicating with the entities, as shown inblock 620. For example, theprocessor 108 of theserver system 102 can detect anadditional entity 406 that lacks an authorization for accessing theelectronic meeting 302, as described above with respect toFIG. 4 . - In some embodiments, detecting the
unauthorized entity 406 can include determining that acomputing device 402 corresponding to the unauthorized entity 406 (e.g., a user that is not authorized to access the meeting) is positioned in the same geographical location asother computing devices 104 a-c authorized to access the meeting. The geographical location can be a defined by reference to a specific area, such as a boardroom, and/or a proximity to theother computing devices 104 a-c (e.g., within 200 feet of theother computing devices 104 a-c). - In some embodiments, the
management application 114 can detect theunauthorized entity 406 based on theunauthorized entity 406 unsuccessfully attempting to access theelectronic meeting 302. In one non-limiting example, themanagement application 114 can determine that authentication data provided by theentity 406 is invalid. Themanagement application 114 may execute at least one remedial action for a managedcomputing device 402 in response to a threshold number of failed attempts by an entity to access the meeting using invalid authentication data. In another non-limiting example, themanagement application 114 can determine that theentity 406 is not included on alisting 308 of the entities authorized to access theelectronic meeting 302. In another non-limiting example, themanagement application 114 can determine that a request from the entity to access theelectronic meeting 302 has a timestamp outside a designated time period for theelectronic meeting 302. - In some embodiments, the
management application 114 can determine that thecomputing device 402 is not authorized to access the electronic meeting, regardless of whether the operator of thecomputing device 402 is authorized to access the meeting. For example, themanagement application 114 can determine that acomputing device 402 is not authorized to access the electronic meeting based on thecomputing device 402 being non-compliant with at least one rule governing access to theresources 202 and/or other electronic content used for the electronic meeting. - The
method 600 involves restricting a communication of at least some electronic content among at least some of entities 304 a-c based on detecting the additional entity that lacks authorization, as shown inblock 630. For example, theprocessor 108 of theserver system 102 can restrict communication among the entities 304 a-c in anelectronic meeting 302 and/or other form of electronic communication, as described above with respect toFIG. 4 . - In some embodiments, the
management application 114 can perform at least one remedial action in response to detecting anunauthorized computing device 402 accessing theelectronic meeting 302, attempting to access theelectronic meeting 302, and/or being positioned in the vicinity ofother computing devices 104 a-c authorized to access theelectronic meeting 302. In one non-limiting example, the remedial action includes transmitting a software update to thecomputing device 402. The software update can bring thecomputing device 402 into compliance with at least one rule governing access to resources shared via theelectronic meeting 302, such as therules 207. In another non-limiting example, the remedial action includes transmitting a command to an instance of theclient application 124 executing on thecomputing device 402. The command directs theclient application 124 to erase some or all content and/or applications from the computing device 402 (i.e., perform a partial or total “device wipe”). In another non-limiting example, the remedial action includes transmitting a command directing theclient application 124 to lock thecomputing device 402. Locking thecomputing device 402 can include preventing an operator of the computing device from accessing at least one application on thecomputing device 402. - Although the description of
FIGS. 1-6 involves theserver system 102 providing at least one of theresources 202, other implementations are possible. For example, an additional enterprise level computing device may store and provide at least one of theresources 202 based on commands from themanagement application 114. - Although the
server system 102 is depicted as a single server inFIGS. 1-2 for purposes of simplicity, theserver system 102 can include multiple servers performing multiple functions. In some embodiments, theserver system 102 can include a proxy server function and/or a compliance server function. The proxy server function may include providing a proxy service. As used herein, the term “proxy service” is used to refer to computer-executable instructions for performing the at least one function for authenticating access credentials and device identifiers. The proxy service may be executed to receive an access request from a computing device for accessingresources 202 and to determine whether to grant or deny the access request. Based on determining that the access request is granted, the proxy service may associate a computing device with access credentials to accessresources 202 provided by and/or accessible via theserver system 102. - In some embodiments, a proxy server function may communicate with a compliance server function, such as a compliance service, to authorize a
computing device 104 by determining whether thecomputing device 104 complies with hardware, software, device management restrictions, and the like, as defined in a set ofrules 207. As used herein, the term “compliance service” is used to refer to computer-executable instructions for performing the functionality described herein for authorizing the device characteristics of the requesting device. For instance, the compliance service may identify the device characteristics from a device profile listing of hardware restrictions, software restrictions, and/or computing device management restrictions for a given computing device. - The foregoing description of the aspects, including illustrated examples, has been presented only for the purpose of illustration and description and is not intended to be exhaustive or limiting to the precise forms disclosed. Many variations and modifications may be made to the above-described examples without departing substantially from the spirit and principles of the disclosure. All such modifications and variations are intended to be included herein within the scope of this disclosure and protected by the following claims.
- The flowcharts described herein show certain functionality and operations performed by the
management application 114 and theclient application 124, respectively. If embodied in software, each box may represent a module, segment, or portion of code that comprises program instructions to implement the specified logical function(s). The program instructions may be embodied in the form of source code that comprises human-readable statements written in a programming language or machine code that comprises numerical instructions recognizable by a suitable execution system such as aprocessor - Although the flowcharts described herein show a specific order of execution, it is understood that the order of execution may differ from that which is depicted. For example, the order of execution of two or more steps may be scrambled relative to the order shown. Also, two or more blocks shown in succession in the flow charts may be executed concurrently or with partial concurrence. Further, in some embodiments, one or more of the steps shown in the flow charts may be skipped or omitted. In addition, any number of counters, state variables, warning semaphores, or messages might be added to the logical flow described herein, for purposes of enhanced utility, accounting, performance measurement, or providing troubleshooting aids, etc. It is understood that all such variations are within the scope of the present disclosure.
- Any logic or application described herein that comprises software or code can be embodied in any non-transitory computer-readable medium for use by or in connection with a computing system such as, for example, a processor in a computer system or other system. In this sense, the logic may comprise, for example, statements including instructions and declarations that can be fetched from the computer-readable medium and executed by a computing system.
- In the context of the present disclosure, a “computer-readable medium” can include any medium that can contain, store, maintain, or otherwise include the logic or application described herein for use by or in connection with a computing system. The computer-readable medium can comprise any one of many physical media such as, for example, magnetic, optical, or semiconductor media. More specific examples of a suitable computer-readable medium can include, but are not limited to, magnetic tapes, magnetic floppy diskettes, magnetic hard drives, memory cards, solid-state drives, USB flash drives, optical discs, etc. The computer readable medium may be a random access memory (“RAM”). Examples of a RAM can include (but are not limited to) static random access memory (“SRAM”), dynamic random access memory (“DRAM”), magnetic random access memory (“MRAM”), etc. The computer-readable medium may be a read-only memory (“ROM”), a programmable read-only memory (“PROM”), an erasable programmable read-only memory (“EPROM”), an electrically erasable programmable read-only memory (“EEPROM”), or other type of memory device.
- It should be emphasized that the above-described embodiments of the present disclosure are merely possible examples of implementations set forth for a clear understanding of the principles of the disclosure. Many variations and modifications may be made to the above-described embodiment(s) without departing substantially from the spirit and principles of the disclosure. All such modifications and variations are intended to be included herein within the scope of this disclosure and the following claims.
Claims (20)
1. A method comprising:
identifying, by a management application executed by a processor, a plurality of entities for communicating electronic content;
determining, by the management application, that at least a required subset of entities of the plurality of entities required for communicating the electronic content is available for electronic communication; and
in response to determining that the required subset of entities is available for electronic communication, authorizing, by the management application, communication of at least some of the electronic content among the plurality of entities.
2. The method of claim 1 , wherein the required subset of entities comprises a configurable threshold number of entities available for electronic communication.
3. The method of claim 1 , wherein determining that at least the required subset of entities is available comprises determining, for each required entity of the required subset of entities, that a respective computing device corresponding to the required entity is authorized for electronic communication.
4. The method of claim 1 , wherein determining that at least the required subset of entities is available comprises determining, for each required entity of the required subset of entities, that a respective computing device corresponding to the required entity is compliant with at least one rule configured for controlling access to the electronic content by computing devices.
5. The method of claim 1 , wherein determining that at least the required subset of entities is available comprises determining, for each required entity of the required subset of entities, that a respective computing device corresponding to the required entity is positioned in a common geographical location.
6. The method of claim 1 , wherein determining that at least the required subset of entities is available comprises authenticating each required entity based on respective authentication data provided by a respective client application executed at a respective computing device corresponding to the required entity.
7. The method of claim 6 , wherein authenticating the required entity based on respective authentication data comprises authenticating the required entity based on at least one of:
respective information corresponding to the required entity and detected by the respective client application; and
at least one respective user input to a respective computing device corresponding to the required entity.
8. The method of claim 1 , wherein authorizing the communication comprises decrypting the electronic content with an encryption key formed by performing at least one operation on each of a plurality of portions of the encryption key received from the required subset of entities.
9. The method of claim 1 , wherein authorizing the communication comprises verifying secondary authentication data generated from authentication data provided by the required subset of entities.
10. The method of claim 1 , wherein the communication of electronic content is performed via an electronic meeting accessed by the plurality of entities.
11. The method of claim 1 , further comprising restricting the communication of the electronic content based on determining that fewer than all required entities of the required subset of entities are available for electronic communication.
12. The method of claim 1 , further comprising restricting the communication of the electronic content based on detecting an additional entity that lacks an authorization for electronic communication.
13. A method performed by a management application executed by a processor, the method comprising:
identifying a plurality of entities authorized for electronic communication among one another;
detecting an additional entity that lacks an authorization for electronic communication among the plurality of entities; and
restricting a communication of at least some electronic content among at least some of the plurality of entities based on detecting the additional entity that lacks the authorization.
14. The method of claim 13 , wherein detecting the additional entity that lacks the authorization comprises determining that an unauthorized computing device corresponding to the additional entity is positioned in a geographical location in which a respective computing device corresponding each entity of the plurality of entities is positioned.
15. The method of claim 14 , further comprising performing a remedial action specified by at least one rule configured for controlling access to the electronic content in response to determining that the unauthorized computing device is non-compliant with the at least one rule.
16. The method of claim 15 , wherein the remedial action comprises transmitting to the unauthorized computing device a software update that is configured to bring the unauthorized computing device into compliance with the at least one rule.
17. The method of claim 15 , wherein the remedial action comprises transmitting a command to a client application executing on the unauthorized computing device directing the client application to erase at least some content from the unauthorized computing device.
18. The method of claim 15 , wherein the remedial action comprises transmitting a command to a client application executing on the computing device, wherein the command directs the client application to lock the computing device.
19. The method of claim 13 , further comprising terminating an electronic meeting accessed by the plurality of entities for the electronic communication among the plurality of entities based on detecting the additional entity that lacks the authorization.
20. A system comprising:
at least one processor; and
a computer-readable medium in communication with the at least one processor;
wherein the at least one processor is configured to execute instructions embodied in the computer-readable medium to perform operations comprising:
identifying a plurality of entities required for authorizing at least one communication feature of a plurality of communication features for communicating electronic content,
determining that each required entity of the plurality of required entities is available for electronic communication, and
authorizing performance of the at least one communication feature based on determining that each entity is available for electronic communication, wherein at least one additional communication feature of the plurality of communication features is available in an absence of at least one of the plurality of required entities.
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/828,922 US20140280955A1 (en) | 2013-03-14 | 2013-03-14 | Controlling Electronically Communicated Resources |
US15/430,184 US11824644B2 (en) | 2013-03-14 | 2017-02-10 | Controlling electronically communicated resources |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/828,922 US20140280955A1 (en) | 2013-03-14 | 2013-03-14 | Controlling Electronically Communicated Resources |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/430,184 Continuation US11824644B2 (en) | 2013-03-14 | 2017-02-10 | Controlling electronically communicated resources |
Publications (1)
Publication Number | Publication Date |
---|---|
US20140280955A1 true US20140280955A1 (en) | 2014-09-18 |
Family
ID=51533704
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/828,922 Abandoned US20140280955A1 (en) | 2013-03-14 | 2013-03-14 | Controlling Electronically Communicated Resources |
US15/430,184 Active 2034-10-24 US11824644B2 (en) | 2013-03-14 | 2017-02-10 | Controlling electronically communicated resources |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/430,184 Active 2034-10-24 US11824644B2 (en) | 2013-03-14 | 2017-02-10 | Controlling electronically communicated resources |
Country Status (1)
Country | Link |
---|---|
US (2) | US20140280955A1 (en) |
Cited By (44)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20130274940A1 (en) * | 2012-03-05 | 2013-10-17 | Siemens Corporation | Cloud enabled building automation system |
US20140201816A1 (en) * | 2013-09-23 | 2014-07-17 | Sky Socket, Llc | Securely Authorizing Access to Remote Resources |
US20150074813A1 (en) * | 2013-09-06 | 2015-03-12 | Oracle International Corporation | Protection of resources downloaded to portable devices from enterprise systems |
US20150120930A1 (en) * | 2013-10-31 | 2015-04-30 | Aruba Networks.Com | Provisioning access point bandwidth based on predetermined events |
US9100390B1 (en) | 2014-09-05 | 2015-08-04 | Openpeak Inc. | Method and system for enrolling and authenticating computing devices for data usage accounting |
US9106538B1 (en) | 2014-09-05 | 2015-08-11 | Openpeak Inc. | Method and system for enabling data usage accounting through a relay |
US9124493B2 (en) | 2008-12-19 | 2015-09-01 | Openpeak Inc. | System and method for ensuring compliance with organizational polices |
US9135418B2 (en) | 2011-10-10 | 2015-09-15 | Openpeak Inc. | System and method for creating secure applications |
US20150312260A1 (en) * | 2014-04-25 | 2015-10-29 | Samsung Electronics Co., Ltd. | Methods of providing social network service and server performing the same |
US9232013B1 (en) | 2014-09-05 | 2016-01-05 | Openpeak Inc. | Method and system for enabling data usage accounting |
US9232078B1 (en) | 2015-03-16 | 2016-01-05 | Openpeak Inc. | Method and system for data usage accounting across multiple communication networks |
US9232012B1 (en) | 2014-09-05 | 2016-01-05 | Openpeak Inc. | Method and system for data usage accounting in a computing device |
US9350818B2 (en) | 2014-09-05 | 2016-05-24 | Openpeak Inc. | Method and system for enabling data usage accounting for unreliable transport communication |
US20160239489A1 (en) * | 2015-02-17 | 2016-08-18 | International Business Machines Corporation | Electronic meeting question management |
US20160285991A1 (en) * | 2015-03-26 | 2016-09-29 | International Business Machines Corporation | Collaborative based caching |
US20170054674A1 (en) * | 2010-10-08 | 2017-02-23 | Brian Lee Moffat | Data sharing system method |
US20170068793A1 (en) * | 2015-09-04 | 2017-03-09 | Cisco Technology, Inc. | Time and motion data fusion for determining and remedying issues based on physical presence |
US9723003B1 (en) * | 2014-06-06 | 2017-08-01 | Amazon Technologies, Inc. | Network beacon based credential store |
US20180014295A1 (en) * | 2016-07-05 | 2018-01-11 | Fujitsu Limited | Information processing system, server, and terminal device |
US20180183810A1 (en) * | 2015-08-21 | 2018-06-28 | PushPull Technology Limited | Data Collaboration |
US10063592B1 (en) * | 2014-06-06 | 2018-08-28 | Amazon Technologies, Inc. | Network authentication beacon |
US10129299B1 (en) * | 2014-06-06 | 2018-11-13 | Amazon Technologies, Inc. | Network beacon management of security policies |
US10298577B1 (en) * | 2016-03-31 | 2019-05-21 | Amazon Technologies, Inc. | Credential vending to processes |
US10326671B2 (en) * | 2016-10-18 | 2019-06-18 | Airwatch Llc | Federated mobile device management |
US10684736B2 (en) * | 2007-02-13 | 2020-06-16 | Visual Targeting Corporation | Method for defining a presentation format targetable to a demographic |
US10699201B2 (en) * | 2013-06-04 | 2020-06-30 | Ent. Services Development Corporation Lp | Presenting relevant content for conversational data gathered from real time communications at a meeting based on contextual data associated with meeting participants |
US11038886B1 (en) * | 2018-02-08 | 2021-06-15 | Wells Fargo Bank, N.A. | Compliance management system |
US11190512B2 (en) | 2019-04-17 | 2021-11-30 | Microsoft Technology Licensing, Llc | Integrity attestation of attestation component |
US11222137B2 (en) | 2019-05-03 | 2022-01-11 | Microsoft Technology Licensing, Llc | Storing and executing an application in a user's personal storage with user granted permission |
US11240316B1 (en) * | 2017-04-11 | 2022-02-01 | Wells Fargo Bank, N.A. | Systems and methods for optimizing information collaboration |
US11310008B2 (en) * | 2017-10-23 | 2022-04-19 | Kyocera Corporation | Data transmission with multiple numerologies for multiple devices with common geographical location dependent control information |
US11381567B2 (en) | 2019-04-29 | 2022-07-05 | Microsoft Technology Licensing, Llc | Execution of an application within a scope of user-granted permission |
US11388245B1 (en) | 2017-04-11 | 2022-07-12 | Wells Fargo Bank, N.A. | Systems and methods for content delivery |
US11392467B2 (en) | 2019-04-17 | 2022-07-19 | Microsoft Technology Licensing, Llc | Failover between decentralized identity stores |
US11411959B2 (en) * | 2019-05-03 | 2022-08-09 | Microsoft Technology Licensing, Llc | Execution of application in a container within a scope of user-granted permission |
US11429743B2 (en) | 2019-04-29 | 2022-08-30 | Microsoft Technology Licensing, Llc | Localization of DID-related claims and data |
US11528233B2 (en) * | 2013-03-15 | 2022-12-13 | Advanced Elemental Technologies, Inc. | Systems and methods for establishing a user purpose fulfillment computing platform |
US20220405412A1 (en) * | 2021-06-21 | 2022-12-22 | Microsoft Technology Licensing, Llc | Configuration of default sensitivity labels for network file storage locations |
US11652823B1 (en) * | 2022-12-19 | 2023-05-16 | Uab 360 It | Systems and methods for controlling access |
US11722491B1 (en) * | 2020-06-30 | 2023-08-08 | Amazon Technologies, Inc. | Cumulative risk-based scoring for quorum authorization |
US11822662B2 (en) | 2013-03-15 | 2023-11-21 | Advanced Elemental Technologies, Inc. | Methods and systems for secure and reliable identity-based computing |
US11847495B2 (en) | 2013-03-15 | 2023-12-19 | Advanced Elemental Technologies, Inc. | Systems and methods configured to enable an operating system for connected computing that supports user use of suitable to user purpose resources sourced from one or more resource ecospheres |
US11886605B2 (en) * | 2019-09-30 | 2024-01-30 | Red Hat, Inc. | Differentiated file permissions for container users |
US11914696B1 (en) | 2020-09-30 | 2024-02-27 | Amazon Technologies, Inc. | Quorum-based access control management |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10715343B1 (en) * | 2017-09-06 | 2020-07-14 | Amazon Technologies, Inc. | Device monitoring for conference reservation cancellation |
Citations (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030164853A1 (en) * | 2000-12-29 | 2003-09-04 | Min Zhu | Distributed document sharing |
US20060067250A1 (en) * | 2004-09-30 | 2006-03-30 | Boyer David G | Method and apparatus for launching a conference based on presence of invitees |
US20070162417A1 (en) * | 2006-01-10 | 2007-07-12 | Kabushiki Kaisha Toshiba | System and method for selective access to restricted electronic documents |
US20080065727A1 (en) * | 2006-09-13 | 2008-03-13 | Majors Kenneth D | Conferencing system with improved access |
US20100100972A1 (en) * | 2008-08-08 | 2010-04-22 | Jacques Lemieux | Approaches for a location aware client |
US20110135083A1 (en) * | 2009-12-04 | 2011-06-09 | Charles Steven Lingafelt | Methods to Improve Fraud Detection on Conference Calling Systems Based on Observation of Participants' Call Time Durations |
US20110141276A1 (en) * | 2009-12-14 | 2011-06-16 | Apple Inc. | Proactive Security for Mobile Devices |
US20140237041A1 (en) * | 2013-02-19 | 2014-08-21 | Cisco Technology, Inc. | Automatic future meeting scheduler based upon locations of meeting participants |
Family Cites Families (390)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4679226A (en) | 1985-06-17 | 1987-07-07 | Alltel Corporation | Computer security guard circuit |
AU1550992A (en) | 1991-03-04 | 1992-10-06 | Megatrend Telecommunications | Mobile telephone, system and method |
US5237614A (en) | 1991-06-07 | 1993-08-17 | Security Dynamics Technologies, Inc. | Integrated network security system |
US5799068A (en) | 1992-06-29 | 1998-08-25 | Elonex I.P. Holdings Ltd. | Smart phone integration with computer systems |
US5740395A (en) | 1992-10-30 | 1998-04-14 | Intel Corporation | Method and apparatus for cleaning up a solid state memory disk storing floating sector data |
US5666530A (en) | 1992-12-02 | 1997-09-09 | Compaq Computer Corporation | System for automatic synchronization of common file between portable computer and host computer via communication channel selected from a plurality of usable channels there between |
JP2757243B2 (en) | 1993-03-26 | 1998-05-25 | 松下電器産業株式会社 | How to prevent unauthorized use in microcellular systems |
US6748318B1 (en) | 1993-05-18 | 2004-06-08 | Arrivalstar, Inc. | Advanced notification systems and methods utilizing a computer network |
US6618668B1 (en) | 2000-04-26 | 2003-09-09 | Arrivalstar, Inc. | System and method for obtaining vehicle schedule information in an advance notification system |
US6278936B1 (en) | 1993-05-18 | 2001-08-21 | Global Research Systems, Inc. | System and method for an advance notification system for monitoring and reporting proximity of a vehicle |
JP3124664B2 (en) | 1993-11-12 | 2001-01-15 | 松下電器産業株式会社 | Remote file lock system |
US5446888A (en) | 1994-01-14 | 1995-08-29 | Pyne; Charles F. | Remote file transfer method and apparatus |
US5668876A (en) | 1994-06-24 | 1997-09-16 | Telefonaktiebolaget Lm Ericsson | User authentication method and apparatus |
US5864683A (en) | 1994-10-12 | 1999-01-26 | Secure Computing Corporartion | System for providing secure internetwork by connecting type enforcing secure computers to external network for limiting access to data based on user and process access rights |
US6167253A (en) | 1995-01-12 | 2000-12-26 | Bell Atlantic Network Services, Inc. | Mobile data/message/electronic mail download system utilizing network-centric protocol such as Java |
US5574786A (en) | 1995-02-06 | 1996-11-12 | International Business Machines Corporation | Securing trusted personal computer system against unauthorized movement |
JP2661582B2 (en) | 1995-03-13 | 1997-10-08 | 日本電気株式会社 | Subsystem for preventing unauthorized use of wireless mobile terminal in wireless mobile terminal system |
CA2227432C (en) | 1995-07-20 | 2001-05-22 | Novell, Inc. | Transaction synchronization in a disconnectable computer and network |
US7553234B2 (en) | 1995-11-22 | 2009-06-30 | Walker Digital, Llc | Method and apparatus for outputting a result of a game via a container |
US6226622B1 (en) | 1995-11-27 | 2001-05-01 | Alan James Dabbiere | Methods and devices utilizing a GPS tracking system |
US5815807A (en) | 1996-01-31 | 1998-09-29 | Motorola, Inc. | Disposable wireless communication device adapted to prevent fraud |
US5974238A (en) | 1996-08-07 | 1999-10-26 | Compaq Computer Corporation | Automatic data synchronization between a handheld and a host computer using pseudo cache including tags and logical data elements |
JPH10111727A (en) | 1996-10-03 | 1998-04-28 | Toshiba Corp | Information equipment having telephone function and security rearising method therefor |
US6021492A (en) | 1996-10-09 | 2000-02-01 | Hewlett-Packard Company | Software metering management of remote computing devices |
US5870459A (en) | 1996-11-01 | 1999-02-09 | Ericsson Inc. | Recyclable cellular telephone and method and apparatus for supporting the use of a recyclable cellular telephone within a cellular telephone network |
US5826265A (en) | 1996-12-06 | 1998-10-20 | International Business Machines Corporation | Data management system having shared libraries |
US6085192A (en) | 1997-04-11 | 2000-07-04 | Roampage, Inc. | System and method for securely synchronizing multiple copies of a workspace element in a network |
US6023708A (en) | 1997-05-29 | 2000-02-08 | Visto Corporation | System and method for using a global translator to synchronize workspace elements across a network |
US6708221B1 (en) | 1996-12-13 | 2004-03-16 | Visto Corporation | System and method for globally and securely accessing unified information in a computer network |
US7287271B1 (en) | 1997-04-08 | 2007-10-23 | Visto Corporation | System and method for enabling secure access to services in a computer network |
US6131116A (en) | 1996-12-13 | 2000-10-10 | Visto Corporation | System and method for globally accessing computer services |
US20060195595A1 (en) | 2003-12-19 | 2006-08-31 | Mendez Daniel J | System and method for globally and securely accessing unified information in a computer network |
US6766454B1 (en) | 1997-04-08 | 2004-07-20 | Visto Corporation | System and method for using an authentication applet to identify and authenticate a user in a computer network |
US5961590A (en) | 1997-04-11 | 1999-10-05 | Roampage, Inc. | System and method for synchronizing electronic mail between a client site and a central site |
DE19722424C5 (en) | 1997-05-28 | 2006-09-14 | Telefonaktiebolaget Lm Ericsson (Publ) | Method of securing access to a remote system |
GB2361558B (en) | 1997-05-28 | 2003-07-23 | Ericsson Telefon Ab L M | A method for securing access to a remote system |
US6606662B2 (en) | 1997-06-11 | 2003-08-12 | Canon Kabushiki Kaisha | Portable terminal apparatus and communication method thereof |
JPH1196099A (en) * | 1997-09-19 | 1999-04-09 | Hitachi Ltd | Service providing system |
US5966081A (en) | 1997-09-24 | 1999-10-12 | Chesnutt; R. Van | Paging activated electronic security system |
US6052735A (en) | 1997-10-24 | 2000-04-18 | Microsoft Corporation | Electronic mail object synchronization between a desktop computer and mobile device |
US6269369B1 (en) | 1997-11-02 | 2001-07-31 | Amazon.Com Holdings, Inc. | Networked personal contact manager |
US6636489B1 (en) | 1997-11-03 | 2003-10-21 | Bell South Wireless Data. L.P. | Wireless management system and a method for an automated over-the-air managing process for wireless communication device |
US6151606A (en) | 1998-01-16 | 2000-11-21 | Visto Corporation | System and method for using a workspace data manager to access, manipulate and synchronize network data |
JPH11224288A (en) | 1998-02-06 | 1999-08-17 | Hitachi Ltd | Use condition sale type digital contents sale electronic mall system |
US20030110084A1 (en) | 1998-03-04 | 2003-06-12 | Martin Forest Eberhard | Secure content distribution system |
US7792297B1 (en) | 1998-03-31 | 2010-09-07 | Piccionelli Greg A | System and process for limiting distribution of information on a communication network based on geographic location |
US6779118B1 (en) | 1998-05-04 | 2004-08-17 | Auriq Systems, Inc. | User specific automatic data redirection system |
US6233341B1 (en) | 1998-05-19 | 2001-05-15 | Visto Corporation | System and method for installing and using a temporary certificate at a remote site |
US6480096B1 (en) | 1998-07-08 | 2002-11-12 | Motorola, Inc. | Method and apparatus for theft deterrence and secure data retrieval in a communication device |
US6286098B1 (en) * | 1998-08-28 | 2001-09-04 | Sap Aktiengesellschaft | System and method for encrypting audit information in network applications |
US8332478B2 (en) | 1998-10-01 | 2012-12-11 | Digimarc Corporation | Context sensitive connected content |
US6131096A (en) | 1998-10-05 | 2000-10-10 | Visto Corporation | System and method for updating a remote database in a network |
US7136645B2 (en) | 1998-10-09 | 2006-11-14 | Netmotion Wireless, Inc. | Method and apparatus for providing mobile and other intermittent connectivity in a computing environment |
US6463470B1 (en) | 1998-10-26 | 2002-10-08 | Cisco Technology, Inc. | Method and apparatus of storing policies for policy-based management of quality of service treatments of network data traffic flows |
US6370629B1 (en) | 1998-10-29 | 2002-04-09 | Datum, Inc. | Controlling access to stored information based on geographical location and date and time |
US6553375B1 (en) | 1998-11-25 | 2003-04-22 | International Business Machines Corporation | Method and apparatus for server based handheld application and database management |
US6078260A (en) | 1998-12-21 | 2000-06-20 | Sony Corporation | Method and apparatus for keeping track of children |
US7430757B1 (en) | 1999-01-08 | 2008-09-30 | International Business Machines Corporation | Oblivious proxying using a secure coprocessor |
US6529949B1 (en) | 2000-02-07 | 2003-03-04 | Interactual Technologies, Inc. | System, method and article of manufacture for remote unlocking of local content located on a client device |
US6668322B1 (en) | 1999-08-05 | 2003-12-23 | Sun Microsystems, Inc. | Access management system and method employing secure credentials |
US7373517B1 (en) | 1999-08-19 | 2008-05-13 | Visto Corporation | System and method for encrypting and decrypting files |
US6578069B1 (en) | 1999-10-04 | 2003-06-10 | Microsoft Corporation | Method, data structure, and computer program product for identifying a network resource |
US6578054B1 (en) | 1999-10-04 | 2003-06-10 | Microsoft Corporation | Method and system for supporting off-line mode of operation and synchronization using resource state information |
US6694335B1 (en) | 1999-10-04 | 2004-02-17 | Microsoft Corporation | Method, computer readable medium, and system for monitoring the state of a collection of resources |
KR100348249B1 (en) | 1999-10-08 | 2002-08-09 | 엘지전자 주식회사 | Data architecture of VCT and method for transmit/receiving service information |
US6560772B1 (en) | 1999-10-15 | 2003-05-06 | International Business Machines Corporation | Method, system, and program for accessing data in different environments |
US7363361B2 (en) | 2000-08-18 | 2008-04-22 | Akamai Technologies, Inc. | Secure content delivery system |
WO2001046833A2 (en) | 1999-12-23 | 2001-06-28 | Logistics.Com, Inc. | Bid positioning system |
US7739334B1 (en) | 2000-03-17 | 2010-06-15 | Visto Corporation | System and method for automatically forwarding email and email events via a computer network to a server computer |
US10552583B2 (en) | 2000-03-21 | 2020-02-04 | Gregory A. Piccionelli | Secure portable computer and security method |
US20010047335A1 (en) | 2000-04-28 | 2001-11-29 | Martin Arndt | Secure payment method and apparatus |
US7216361B1 (en) | 2000-05-19 | 2007-05-08 | Aol Llc, A Delaware Limited Liability Company | Adaptive multi-tier authentication system |
AU2001261784B2 (en) | 2000-05-22 | 2006-12-14 | Manhattan Associates | System, method and apparatus for integrated supply chain management |
US10684350B2 (en) | 2000-06-02 | 2020-06-16 | Tracbeam Llc | Services and applications for a communications network |
US7991697B2 (en) | 2002-12-16 | 2011-08-02 | Irdeto Usa, Inc. | Method and system to digitally sign and deliver content in a geographically controlled manner via a network |
JP2002082917A (en) | 2000-07-04 | 2002-03-22 | Sony Computer Entertainment Inc | Contents distribution method, contents distribution server, and client terminal in contents distribution infrastructure |
US7225231B2 (en) | 2000-09-20 | 2007-05-29 | Visto Corporation | System and method for transmitting workspace elements across a network |
US20020055967A1 (en) | 2000-11-08 | 2002-05-09 | Coussement Stefaan Valere Albert | System for reporting client status information to communications-center agents |
US7660902B2 (en) | 2000-11-20 | 2010-02-09 | Rsa Security, Inc. | Dynamic file access control and management |
US7512806B2 (en) | 2000-11-30 | 2009-03-31 | Palmsource, Inc. | Security technique for controlling access to a network by a wireless device |
US7428411B2 (en) | 2000-12-19 | 2008-09-23 | At&T Delaware Intellectual Property, Inc. | Location-based security rules |
US7702785B2 (en) | 2001-01-31 | 2010-04-20 | International Business Machines Corporation | Methods, systems and computer program products for selectively allowing users of a multi-user system access to network resources |
US7017105B2 (en) | 2001-02-02 | 2006-03-21 | Microsoft Corporation | Deleting objects from a store of a device |
US7330717B2 (en) * | 2001-02-23 | 2008-02-12 | Lucent Technologies Inc. | Rule-based system and method for managing the provisioning of user applications on limited-resource and/or wireless devices |
US6529136B2 (en) | 2001-02-28 | 2003-03-04 | International Business Machines Corporation | Group notification system and method for implementing and indicating the proximity of individuals or groups to other individuals or groups |
US7350229B1 (en) | 2001-03-07 | 2008-03-25 | Netegrity, Inc. | Authentication and authorization mapping for a computer network |
US7107339B1 (en) | 2001-04-07 | 2006-09-12 | Webmethods, Inc. | Predictive monitoring and problem identification in an information technology (IT) infrastructure |
US7603703B2 (en) | 2001-04-12 | 2009-10-13 | International Business Machines Corporation | Method and system for controlled distribution of application code and content data within a computer network |
US6996841B2 (en) | 2001-04-19 | 2006-02-07 | Microsoft Corporation | Negotiating secure connections through a proxy server |
US7228383B2 (en) | 2001-06-01 | 2007-06-05 | Visto Corporation | System and method for progressive and hierarchical caching |
US7284045B1 (en) | 2001-06-01 | 2007-10-16 | Visto Corporation | Method and system for determining information to access an electronic mail account |
US7444375B2 (en) | 2001-06-19 | 2008-10-28 | Visto Corporation | Interactive voice and text message system |
US7562112B2 (en) | 2001-07-06 | 2009-07-14 | Intel Corporation | Method and apparatus for peer-to-peer services for efficient transfer of information between networks |
US7590684B2 (en) * | 2001-07-06 | 2009-09-15 | Check Point Software Technologies, Inc. | System providing methodology for access control with cooperative enforcement |
US20030009595A1 (en) | 2001-07-09 | 2003-01-09 | Roger Collins | System and method for compressing data using field-based code word generation |
US7064688B2 (en) | 2001-07-09 | 2006-06-20 | Good Technology, Inc. | System and method for compressing data on a bandwidth-limited network |
US20030186689A1 (en) | 2001-08-06 | 2003-10-02 | Samsung Electronics Co., Ltd | System and method for IOTA software download notification for wireless communication devices |
US20030065934A1 (en) | 2001-09-28 | 2003-04-03 | Angelo Michael F. | After the fact protection of data in remote personal and wireless devices |
US7308710B2 (en) | 2001-09-28 | 2007-12-11 | Jp Morgan Chase Bank | Secured FTP architecture |
EP1451718B1 (en) | 2001-10-23 | 2012-08-08 | Beechwood Limited Partnership | System and method for merging remote and local data in a single user interface |
CA2467404A1 (en) | 2001-11-15 | 2003-05-30 | Visto Corporation | System and methods for asychronous synchronization |
US8108687B2 (en) | 2001-12-12 | 2012-01-31 | Valve Corporation | Method and system for granting access to system and content |
US7496957B2 (en) | 2002-01-02 | 2009-02-24 | Hewlett-Packard Development Company, L.P. | System and method for preventing use of a wireless device |
US6741232B1 (en) | 2002-01-23 | 2004-05-25 | Good Technology, Inc. | User interface for a data processing apparatus |
US7606938B2 (en) | 2002-03-01 | 2009-10-20 | Enterasys Networks, Inc. | Verified device locations in a data network |
US7458098B2 (en) | 2002-03-08 | 2008-11-25 | Secure Computing Corporation | Systems and methods for enhancing electronic communication security |
US8094591B1 (en) | 2002-03-19 | 2012-01-10 | Good Technology, Inc. | Data carrier detector for a packet-switched communication network |
US7788382B1 (en) | 2002-03-26 | 2010-08-31 | Good Technology, Inc. | Server initiated synchronization |
US7447506B1 (en) | 2002-03-29 | 2008-11-04 | Good Technology, Inc. | Apparatus and method for reducing network congestion |
US7310535B1 (en) | 2002-03-29 | 2007-12-18 | Good Technology, Inc. | Apparatus and method for reducing power consumption in a wireless device |
US6726106B1 (en) | 2002-04-02 | 2004-04-27 | Good Technology, Inc. | Power management and device illumination mechanisms for a personal digital assistant |
US20030204716A1 (en) | 2002-04-24 | 2003-10-30 | Rockwood Troy Dean | System and methods for digital content distribution |
US7447799B2 (en) | 2002-04-24 | 2008-11-04 | Good Technology, Inc. | System and method for automatically updating a wireless device |
US6727856B1 (en) | 2002-06-06 | 2004-04-27 | Good Technology, Inc. | Antenna system for a wireless device |
JP3707449B2 (en) | 2002-06-10 | 2005-10-19 | ソニー株式会社 | COMMUNICATION METHOD, COMMUNICATION SYSTEM, AND COMMUNICATION DEVICE |
US7032181B1 (en) | 2002-06-18 | 2006-04-18 | Good Technology, Inc. | Optimized user interface for small screen devices |
CA2391717A1 (en) | 2002-06-26 | 2003-12-26 | Ibm Canada Limited-Ibm Canada Limitee | Transferring data and storing metadata across a network |
US7339484B2 (en) | 2002-06-27 | 2008-03-04 | Hewlett-Packard Development Company, L.P. | Event-driven discovery method and apparatus |
US9357013B2 (en) | 2002-07-26 | 2016-05-31 | International Business Machines Corporation | Client-side script to application communication system |
TW588243B (en) | 2002-07-31 | 2004-05-21 | Trek 2000 Int Ltd | System and method for authentication |
AU2003259893B2 (en) | 2002-08-09 | 2009-03-12 | Blackberry Limited | System and method for preventing access to data on a compromised remote device |
US20040098715A1 (en) | 2002-08-30 | 2004-05-20 | Parixit Aghera | Over the air mobile device software management |
US7665125B2 (en) | 2002-09-23 | 2010-02-16 | Heard Robert W | System and method for distribution of security policies for mobile devices |
US7665118B2 (en) | 2002-09-23 | 2010-02-16 | Credant Technologies, Inc. | Server, computer memory, and method to support security policy maintenance and distribution |
US7437752B2 (en) | 2002-09-23 | 2008-10-14 | Credant Technologies, Inc. | Client architecture for portable device with security policies |
US20060190984A1 (en) | 2002-09-23 | 2006-08-24 | Credant Technologies, Inc. | Gatekeeper architecture/features to support security policy maintenance and distribution |
US7343488B2 (en) * | 2002-09-30 | 2008-03-11 | Intel Corporation | Method and apparatus for providing discrete data storage security |
EP1408391A1 (en) | 2002-10-11 | 2004-04-14 | Telefonaktiebolaget LM Ericsson (publ) | Method of associating authentication information of a trusted device to an identifier of a non-trusted device |
US7827607B2 (en) | 2002-11-27 | 2010-11-02 | Symantec Corporation | Enhanced client compliancy using database of security sensor data |
US7353533B2 (en) | 2002-12-18 | 2008-04-01 | Novell, Inc. | Administration of protection of data accessible by a mobile device |
US7308703B2 (en) | 2002-12-18 | 2007-12-11 | Novell, Inc. | Protection of data accessible by a mobile device |
US7480907B1 (en) | 2003-01-09 | 2009-01-20 | Hewlett-Packard Development Company, L.P. | Mobile services network for update of firmware/software in mobile handsets |
GB2398712B (en) | 2003-01-31 | 2006-06-28 | Hewlett Packard Development Co | Privacy management of personal data |
EP1634162B1 (en) | 2003-01-31 | 2010-07-14 | Visto Corporation | Asynchronous real-time retrieval of data |
EP1618478A4 (en) | 2003-03-13 | 2007-10-03 | Drm Technologies L L C | Secure streaming container |
US7203959B2 (en) | 2003-03-14 | 2007-04-10 | Symantec Corporation | Stream scanning through network proxy servers |
US6995749B2 (en) | 2003-03-28 | 2006-02-07 | Good Technology, Inc. | Auto font magnification mechanism |
US7603112B2 (en) | 2003-04-03 | 2009-10-13 | Nokia Corporation | System, mobile station, method and computer program product for managing context-related information |
GB0308991D0 (en) | 2003-04-17 | 2003-05-28 | Psion Digital Ltd | A data access replication or communication system comprising a distributed software application |
GB2400931B (en) | 2003-04-25 | 2006-09-27 | Messagelabs Ltd | A method of, and system for, replacing external links in electronic documents |
US7275073B2 (en) | 2003-05-07 | 2007-09-25 | Good Technology, Inc. | System and method for notifying mobile devices based on device type and network capabilities |
US7890091B2 (en) | 2003-05-08 | 2011-02-15 | Good Technology, Inc. | Collaborative data and intelligent synchronization for mobile devices |
US7840631B2 (en) | 2003-05-09 | 2010-11-23 | Good Technology, Inc. | Multimedia control with one-click device selection |
US20040224703A1 (en) | 2003-05-09 | 2004-11-11 | Takaki Steven M. | Method and system for enhancing venue participation by venue participants |
US7184801B2 (en) | 2003-05-12 | 2007-02-27 | Good Technology, Inc. | Mobile application builder |
US20040243428A1 (en) | 2003-05-29 | 2004-12-02 | Black Steven C. | Automated compliance for human resource management |
US7676681B2 (en) | 2003-06-17 | 2010-03-09 | Veratad Technologies, Llc | Method, system, and apparatus for identification number authentication |
US20140143852A1 (en) | 2008-08-21 | 2014-05-22 | Ntrepid Corporation | Secure network privacy system |
US6977587B2 (en) | 2003-07-09 | 2005-12-20 | Hewlett-Packard Development Company, L.P. | Location aware device |
US7515717B2 (en) | 2003-07-31 | 2009-04-07 | International Business Machines Corporation | Security containers for document components |
US7735122B1 (en) | 2003-08-29 | 2010-06-08 | Novell, Inc. | Credential mapping |
EP1513040B1 (en) | 2003-09-03 | 2006-12-20 | France Telecom | System and method for distributing content access data |
US7594224B2 (en) | 2003-10-10 | 2009-09-22 | Bea Systems, Inc. | Distributed enterprise security system |
US7421741B2 (en) | 2003-10-20 | 2008-09-02 | Phillips Ii Eugene B | Securing digital content system and method |
US20050097032A1 (en) | 2003-10-29 | 2005-05-05 | Lucent Technologies Inc. | Network support for automatic credit for dropped calls |
US7039394B2 (en) | 2003-11-25 | 2006-05-02 | Good Technology, Inc. | Communication system and method for compressing information sent by a communication device to a target portable communication device |
US8639819B2 (en) | 2004-02-05 | 2014-01-28 | Nokia Corporation | Ad-hoc connection between electronic devices |
US7194273B2 (en) | 2004-02-12 | 2007-03-20 | Lucent Technologies Inc. | Location based service restrictions for mobile applications |
US8843413B2 (en) | 2004-02-13 | 2014-09-23 | Microsoft Corporation | Binding content to a domain |
EP1564944B1 (en) | 2004-02-13 | 2006-12-20 | Sony Ericsson Mobile Communications AB | Method and device for message delivery |
BRPI0508991A (en) | 2004-03-18 | 2007-08-28 | Manhattan Associates Inc | shipping management system and method for shipping planning optimization |
RU2344557C2 (en) | 2004-04-14 | 2009-01-20 | Диджитал Ривер, Инк. | Licensing system based on geographical location |
US7496847B2 (en) | 2004-04-29 | 2009-02-24 | International Business Machines Corporation | Displaying a computer resource through a preferred browser |
US7454623B2 (en) | 2004-06-16 | 2008-11-18 | Blame Canada Holdings Inc | Distributed hierarchical identity management system authentication mechanisms |
US7543146B1 (en) | 2004-06-18 | 2009-06-02 | Blue Coat Systems, Inc. | Using digital certificates to request client consent prior to decrypting SSL communications |
AU2005273532B2 (en) | 2004-06-28 | 2011-04-07 | Acano (Uk) Limited | System for proximity determination |
JP4552540B2 (en) | 2004-07-09 | 2010-09-29 | ソニー株式会社 | Content recording apparatus, content reproducing apparatus, content recording method, content reproducing method, and program |
GB0420409D0 (en) | 2004-09-14 | 2004-10-20 | Waterleaf Ltd | Online commercial transaction system and method of operation thereof |
EP1792469A1 (en) | 2004-09-17 | 2007-06-06 | Koninklijke Philips Electronics N.V. | Proximity check server |
US7475152B2 (en) | 2004-09-20 | 2009-01-06 | International Business Machines Corporation | Approach to provide self-protection function to web content at client side |
US7620001B2 (en) | 2004-10-13 | 2009-11-17 | Good Technology, Inc. | Communication system and method with mobile devices |
US8001082B1 (en) | 2004-10-28 | 2011-08-16 | Good Technology, Inc. | System and method of data security in synchronizing data with a wireless device |
GB0427643D0 (en) | 2004-12-17 | 2005-01-19 | Carnall Murat | Method and apparatus for recording events |
US7873959B2 (en) | 2005-02-01 | 2011-01-18 | Microsoft Corporation | Publishing the status of and updating firmware components |
US7448023B2 (en) | 2005-02-25 | 2008-11-04 | Microsoft Corporation | Method and system for verifying rule compliance of an application object |
JP2006260201A (en) | 2005-03-17 | 2006-09-28 | Hitachi Ltd | Distributed authentication system and communication controller |
US7657746B2 (en) | 2005-04-22 | 2010-02-02 | Microsoft Corporation | Supporting statements for credential based access control |
US20060253474A1 (en) | 2005-05-09 | 2006-11-09 | Hotchkiss Lynette I | System and method for compliance profile configuration and application |
US7970386B2 (en) | 2005-06-03 | 2011-06-28 | Good Technology, Inc. | System and method for monitoring and maintaining a wireless device |
US7590403B1 (en) | 2005-06-07 | 2009-09-15 | Good Technology, Inc. | Wireless device dormancy override |
US9418040B2 (en) | 2005-07-07 | 2016-08-16 | Sciencelogic, Inc. | Dynamically deployable self configuring distributed network management system |
US7991764B2 (en) | 2005-07-22 | 2011-08-02 | Yogesh Chunilal Rathod | Method and system for communication, publishing, searching, sharing and dynamically providing a journal feed |
US7697942B2 (en) | 2005-09-02 | 2010-04-13 | Stevens Gilman R | Location based rules architecture systems and methods |
US20070093243A1 (en) | 2005-10-25 | 2007-04-26 | Vivek Kapadekar | Device management system |
IL171722A (en) | 2005-11-01 | 2011-12-29 | Eci Telecom Ltd | Access system for the provisioning of different communication services and method for using same |
US20070130473A1 (en) | 2005-12-02 | 2007-06-07 | Mazotas James S | System and method for access control |
US20070136492A1 (en) | 2005-12-08 | 2007-06-14 | Good Technology, Inc. | Method and system for compressing/decompressing data for communication with wireless devices |
US7836303B2 (en) | 2005-12-09 | 2010-11-16 | University Of Washington | Web browser operating system |
US8321947B2 (en) | 2005-12-15 | 2012-11-27 | Emc Corporation | Method and system for dynamically generating a watermarked document during a printing or display operation |
US8006289B2 (en) | 2005-12-16 | 2011-08-23 | International Business Machines Corporation | Method and system for extending authentication methods |
US20070143851A1 (en) | 2005-12-21 | 2007-06-21 | Fiberlink | Method and systems for controlling access to computing resources based on known security vulnerabilities |
US8621549B2 (en) | 2005-12-29 | 2013-12-31 | Nextlabs, Inc. | Enforcing control policies in an information management system |
US9942271B2 (en) | 2005-12-29 | 2018-04-10 | Nextlabs, Inc. | Information management system with two or more interactive enforcement points |
US9081981B2 (en) * | 2005-12-29 | 2015-07-14 | Nextlabs, Inc. | Techniques and system to manage access of information using policies |
JP2007213397A (en) * | 2006-02-10 | 2007-08-23 | Fuji Xerox Co Ltd | Data management program, data management device and switching method of protocol |
US7702322B1 (en) | 2006-02-27 | 2010-04-20 | Good Technology, Llc | Method and system for distributing and updating software in wireless devices |
US7620392B1 (en) | 2006-02-27 | 2009-11-17 | Good Technology, Inc. | Method and system for distributing and updating software in wireless devices |
US7917641B2 (en) | 2006-03-14 | 2011-03-29 | Tangoe, Inc. | Apparatus and method for provisioning wireless data communication devices |
CN101449272A (en) | 2006-03-31 | 2009-06-03 | 维斯托公司 | System and method for searching disparate datastores via a remote device |
US20070261099A1 (en) | 2006-05-02 | 2007-11-08 | Broussard Scott J | Confidential content reporting system and method with electronic mail verification functionality |
US7904718B2 (en) | 2006-05-05 | 2011-03-08 | Proxense, Llc | Personal digital key differentiation for secure transactions |
US9002018B2 (en) | 2006-05-09 | 2015-04-07 | Sync Up Technologies Corporation | Encryption key exchange system and method |
JP4825050B2 (en) | 2006-05-12 | 2011-11-30 | ヤフー株式会社 | Method and system for obtaining moving means from position information |
US8601102B1 (en) | 2006-05-31 | 2013-12-03 | Juniper Networks, Inc. | Dynamic access management for network security |
US8989778B2 (en) | 2006-06-01 | 2015-03-24 | Green Dot Corporation | Secure and private location sharing for location-aware mobile communication devices |
US8745227B2 (en) | 2006-06-07 | 2014-06-03 | Apple Inc. | Distributed secure content delivery |
US7917963B2 (en) | 2006-08-09 | 2011-03-29 | Antenna Vaultus, Inc. | System for providing mobile data security |
US8611928B1 (en) | 2006-08-23 | 2013-12-17 | Aol Inc. | Location-based parental controls |
US7823186B2 (en) | 2006-08-24 | 2010-10-26 | Novell, Inc. | System and method for applying security policies on multiple assembly caches |
US8201216B2 (en) | 2006-09-11 | 2012-06-12 | Interdigital Technology Corporation | Techniques for database structure and management |
US20090298514A1 (en) | 2006-09-14 | 2009-12-03 | Shah Ullah | Real world behavior measurement using identifiers specific to mobile devices |
US8000692B2 (en) | 2006-09-19 | 2011-08-16 | Microsoft Corporation | Mobile device manners propagation and compliance |
US8046823B1 (en) | 2006-10-03 | 2011-10-25 | Stamps.Com Inc. | Secure application bridge server |
US7769394B1 (en) | 2006-10-06 | 2010-08-03 | Sprint Communications Company L.P. | System and method for location-based device control |
US8095124B2 (en) * | 2006-10-20 | 2012-01-10 | Verizon Patent And Licensing Inc. | Systems and methods for managing and monitoring mobile data, content, access, and usage |
US8538028B2 (en) | 2006-11-20 | 2013-09-17 | Toposis Corporation | System and method for secure electronic communication services |
US20080134296A1 (en) | 2006-11-30 | 2008-06-05 | Ofer Amitai | System and method of network authorization by scoring |
GB2446199A (en) | 2006-12-01 | 2008-08-06 | David Irvine | Secure, decentralised and anonymous peer-to-peer network |
US9411976B2 (en) | 2006-12-01 | 2016-08-09 | Maidsafe Foundation | Communication system and method |
US7895296B1 (en) | 2006-12-29 | 2011-02-22 | Google, Inc. | Local storage for web based native applications |
US20080160984A1 (en) | 2006-12-30 | 2008-07-03 | Motorola, Inc. | Method and apparatus for altering mobile device behavior based on rfid tag discovery |
US20080168030A1 (en) * | 2007-01-05 | 2008-07-10 | Stonestreet One, Inc. | Method and system for identifying and selecting a wireless device or network for connection |
US9324074B2 (en) | 2007-01-17 | 2016-04-26 | Eagency, Inc. | Mobile communication device monitoring systems and methods |
US8127133B2 (en) | 2007-01-25 | 2012-02-28 | Microsoft Corporation | Labeling of data objects to apply and enforce policies |
EP2126713A2 (en) | 2007-02-19 | 2009-12-02 | Ondeego, Inc. | Methods and system to create applications and distribute applications to a remote device |
US8687536B2 (en) | 2007-02-23 | 2014-04-01 | Qualcomm Incorporated | Method and apparatus to create multicast groups based on proximity |
US8181206B2 (en) | 2007-02-28 | 2012-05-15 | Time Warner Cable Inc. | Personal content server apparatus and methods |
US20080228504A1 (en) | 2007-03-13 | 2008-09-18 | Nguyen Binh Q | Technique to Deflect Incident Ticket Submission in Real-Time |
US8472874B2 (en) | 2007-03-14 | 2013-06-25 | Apple Inc. | Method and system for pairing of wireless devices using physical presence |
US8225085B2 (en) | 2007-06-05 | 2012-07-17 | Blue Coat Systems, Inc. | System and method for distributed SSL processing between co-operating nodes |
US20080318548A1 (en) | 2007-06-19 | 2008-12-25 | Jose Bravo | Method of and system for strong authentication and defense against man-in-the-middle attacks |
US8561148B2 (en) * | 2008-06-26 | 2013-10-15 | Citrix Systems, Inc. | Methods and systems for interactive evaluation using dynamically generated, interactive resultant sets of policies |
US8060074B2 (en) | 2007-07-30 | 2011-11-15 | Mobile Iron, Inc. | Virtual instance architecture for mobile device management systems |
US9417934B2 (en) * | 2007-08-31 | 2016-08-16 | Core Wireless Licensing S.A.R.L. | Information distribution in a dynamic multi-device environment |
US9225823B2 (en) | 2007-08-31 | 2015-12-29 | Sony Corporation | Portable electronic devices and methods for downloading applications based on presence of the portable electronic device in a defined geographical region |
US8379867B2 (en) | 2007-09-24 | 2013-02-19 | Mymail Technology, Llc | Secure email communication system |
US8160247B2 (en) | 2007-09-27 | 2012-04-17 | Adobe Systems Incorporated | Providing local storage service to applications that run in an application execution environment |
US7890743B2 (en) | 2007-09-28 | 2011-02-15 | Avaya Inc. | Method and apparatus for configuring a device based on proximity to another device |
US8456293B1 (en) | 2007-10-22 | 2013-06-04 | Alarm.Com Incorporated | Providing electronic content based on sensor data |
EP2218015A4 (en) | 2007-11-05 | 2012-08-08 | Visto Corp | Service management system for providing service related message prioritization in a mobile client |
JP5172405B2 (en) | 2007-11-15 | 2013-03-27 | ソニー株式会社 | Wireless communication apparatus, wireless communication system, program, and wireless communication method |
US8677141B2 (en) | 2007-11-23 | 2014-03-18 | Microsoft Corporation | Enhanced security and performance of web applications |
US8051491B1 (en) * | 2007-12-10 | 2011-11-01 | Amazon Technologies, Inc. | Controlling use of computing-related resources by multiple independent parties |
US20090186633A1 (en) | 2008-01-17 | 2009-07-23 | Garmin Ltd. | Location-based profile-adjusting system and method for electronic device |
US11159909B2 (en) | 2008-02-05 | 2021-10-26 | Victor Thomas Anderson | Wireless location establishing device |
US8447303B2 (en) | 2008-02-07 | 2013-05-21 | Research In Motion Limited | Method and system for automatic seamless mobility |
US9185554B2 (en) | 2008-02-15 | 2015-11-10 | Appcentral, Inc. | System and methods to store, retrieve, manage, augment and monitor applications on appliances |
US20090222880A1 (en) | 2008-03-03 | 2009-09-03 | Tresys Technology, Llc | Configurable access control security for virtualization |
GB2458568B (en) | 2008-03-27 | 2012-09-19 | Covertix Ltd | System and method for dynamically enforcing security policies on electronic files |
US8990911B2 (en) | 2008-03-30 | 2015-03-24 | Emc Corporation | System and method for single sign-on to resources across a network |
US20090260064A1 (en) | 2008-04-15 | 2009-10-15 | Problem Resolution Enterprise, Llc | Method and process for registering a device to verify transactions |
US8209744B2 (en) | 2008-05-16 | 2012-06-26 | Microsoft Corporation | Mobile device assisted secure computer network communication |
US8910255B2 (en) | 2008-05-27 | 2014-12-09 | Microsoft Corporation | Authentication for distributed secure content management system |
US8353044B1 (en) * | 2008-06-27 | 2013-01-08 | Symantec Corporation | Methods and systems for computing device remediation |
JP5383335B2 (en) | 2008-07-03 | 2014-01-08 | キヤノン株式会社 | Data transmission apparatus, transmission control method, and program |
US8763071B2 (en) | 2008-07-24 | 2014-06-24 | Zscaler, Inc. | Systems and methods for mobile application security classification and enforcement |
EP2342652A4 (en) | 2008-09-05 | 2012-05-30 | Visto Corp | System, apparatus and associated methodology for enriching contact of a remote client |
US8555351B2 (en) | 2008-09-29 | 2013-10-08 | International Business Machines Corporation | Trusted database authentication through an untrusted intermediary |
US20100087144A1 (en) | 2008-10-02 | 2010-04-08 | Roni Korenshtein | Short Range Exchange of Information |
JP4730421B2 (en) | 2008-10-10 | 2011-07-20 | ソニー株式会社 | Wireless communication method |
US8863268B2 (en) | 2008-10-29 | 2014-10-14 | Dell Products, Lp | Security module and method within an information handling system |
BRPI0823115A2 (en) | 2008-11-04 | 2015-06-16 | Nokia Siemens Networks Oy | Service Access Control |
US8346234B2 (en) | 2008-11-08 | 2013-01-01 | Absolute Software Corporation | Secure platform management with power savings capacity |
US8260320B2 (en) | 2008-11-13 | 2012-09-04 | Apple Inc. | Location specific content |
US8909925B2 (en) | 2008-11-17 | 2014-12-09 | Prakash Baskaran | System to secure electronic content, enforce usage policies and provide configurable functionalities |
US8219536B2 (en) | 2008-11-25 | 2012-07-10 | At&T Intellectual Property I, L.P. | Systems and methods to select media content |
US8156435B2 (en) | 2008-11-25 | 2012-04-10 | At&T Intellectual Property I, L.P. | Systems and methods to select media content |
US20100138667A1 (en) | 2008-12-01 | 2010-06-03 | Neil Patrick Adams | Authentication using stored biometric data |
US8972496B2 (en) * | 2008-12-10 | 2015-03-03 | Amazon Technologies, Inc. | Content sharing |
US8412957B2 (en) | 2008-12-16 | 2013-04-02 | SAP France S.A. | Encryption and decryption of records in accordance with group access vectors |
WO2010088199A2 (en) | 2009-01-27 | 2010-08-05 | Watchguard Technologies, Inc. | Location-aware configuration |
US9557889B2 (en) | 2009-01-28 | 2017-01-31 | Headwater Partners I Llc | Service plan design, user interfaces, application programming interfaces, and device management |
US8392972B2 (en) | 2009-02-11 | 2013-03-05 | Sophos Plc | Protected access control method for shared computer resources |
US20100212016A1 (en) | 2009-02-18 | 2010-08-19 | Microsoft Corporation | Content protection interoperrability |
US20100222645A1 (en) | 2009-02-27 | 2010-09-02 | Verizon Patent And Licensing Inc. | Health and wellness monitoring system |
US8688078B2 (en) | 2009-03-05 | 2014-04-01 | Centurylink Intellectual Property Llc | System and method for mobile service geochronous validation |
JPWO2010106772A1 (en) | 2009-03-17 | 2012-09-20 | 日本電気株式会社 | Distributed processing system and distributed processing method |
US8332350B2 (en) | 2009-04-08 | 2012-12-11 | Titus Inc. | Method and system for automated security access policy for a document management system |
US8214645B2 (en) | 2009-04-08 | 2012-07-03 | Research In Motion Limited | Systems, devices, and methods for securely transmitting a security parameter to a computing device |
US8171292B2 (en) | 2009-04-08 | 2012-05-01 | Research In Motion Limited | Systems, devices, and methods for securely transmitting a security parameter to a computing device |
US8380170B2 (en) | 2009-04-12 | 2013-02-19 | Kristine A. Wilson | Cellular device identification and location with emergency number selectivity enforcement (CILENSE) |
US9197417B2 (en) | 2009-04-24 | 2015-11-24 | Microsoft Technology Licensing, Llc | Hosted application sandbox model |
US8695058B2 (en) | 2009-05-20 | 2014-04-08 | Mobile Iron, Inc. | Selective management of mobile device data in an enterprise environment |
US20100299152A1 (en) | 2009-05-20 | 2010-11-25 | Mobile Iron, Inc. | Selective Management of Mobile Devices in an Enterprise Environment |
US8898748B2 (en) | 2009-05-21 | 2014-11-25 | Mobile Iron, Inc. | Remote verification for configuration updates |
US20100299362A1 (en) | 2009-05-24 | 2010-11-25 | Roger Frederick Osmond | Method for controlling access to data containers in a computer system |
US20100317371A1 (en) | 2009-06-12 | 2010-12-16 | Westerinen William J | Context-based interaction model for mobile devices |
US8032666B2 (en) | 2009-06-12 | 2011-10-04 | Microsoft Corporation | Location enabled bookmark and profile |
US9047458B2 (en) | 2009-06-19 | 2015-06-02 | Deviceauthority, Inc. | Network access protection |
US8214862B1 (en) | 2009-07-13 | 2012-07-03 | Sprint Communications Company L.P. | Conserving bandwidth by restricting videos communicated in a wireless telecommunications network |
US8706272B2 (en) | 2009-08-14 | 2014-04-22 | Apple Inc. | Adaptive encoding and compression of audio broadcast data |
WO2011022053A1 (en) | 2009-08-18 | 2011-02-24 | Errol David Naiman | System and methods for device management |
US20110055891A1 (en) | 2009-08-26 | 2011-03-03 | Rice Christopher T | Device security |
US8984657B2 (en) | 2009-09-08 | 2015-03-17 | Appcentral, Inc. | System and method for remote management of applications downloaded to a personal portable wireless appliance |
US8744490B2 (en) | 2009-12-03 | 2014-06-03 | Osocad Remote Limited Liability Company | System and method for migrating agents between mobile devices |
RU2012130005A (en) | 2009-12-14 | 2014-01-27 | Сумитомо Электрик Нетуоркс, Инк. | CONTENT RECEPTION DEVICE, CONTENT PLAYBACK DEVICE, CONTENT RECEPTION AND PLAYBACK DEVICE, CONTENT RECEPTION METHOD AND PROGRAM |
JP5370131B2 (en) | 2009-12-22 | 2013-12-18 | セイコーエプソン株式会社 | Image display apparatus and control method |
CN102111759A (en) | 2009-12-28 | 2011-06-29 | 中国移动通信集团公司 | Authentication method, system and device |
EP2537102A4 (en) | 2010-02-15 | 2017-08-23 | Unwired Planet International Limited | Scripting/proxy systems, methods and circuit arrangements |
US8166106B2 (en) | 2010-04-15 | 2012-04-24 | Microsoft Corporation | Targeting applications based on mobile operator |
US9135434B2 (en) | 2010-04-19 | 2015-09-15 | Appcentral, Inc. | System and method for third party creation of applications for mobile appliances |
US8411834B2 (en) | 2010-04-27 | 2013-04-02 | Cox Communications, Inc. | Device-to-device call disposition |
JP5483569B2 (en) | 2010-04-27 | 2014-05-07 | Kddi株式会社 | Terminal control system, terminal control method and program |
CN103262024B (en) | 2010-05-09 | 2015-05-13 | 思杰系统有限公司 | Methods and systems for forcing an application to store data in a secure storage location |
US8560151B2 (en) | 2010-05-11 | 2013-10-15 | Cartasite, Inc. | Dynamic monitoring of mobile railway car undercarriage |
US9350708B2 (en) | 2010-06-01 | 2016-05-24 | Good Technology Corporation | System and method for providing secured access to services |
US8447986B2 (en) | 2010-06-23 | 2013-05-21 | Microsoft Corporation | Accessing restricted content based on proximity |
US9558476B2 (en) | 2010-07-01 | 2017-01-31 | Good Technology Holdings Limited | Method and device for editing workspace data objects |
US20120011007A1 (en) | 2010-07-07 | 2012-01-12 | At&T Intellectual Property I, L.P. | Mobile Payment Using DTMF Signaling |
KR101763747B1 (en) | 2010-08-19 | 2017-08-01 | 삼성전자 주식회사 | Method and system for bluetooth communication |
KR101814600B1 (en) | 2010-08-26 | 2018-01-30 | 삼성전자주식회사 | Method and apparatus for connecting communication |
US20120094639A1 (en) | 2010-10-15 | 2012-04-19 | Mark Carlson | Heat maps applying location-based information to transaction processing data |
US9576068B2 (en) | 2010-10-26 | 2017-02-21 | Good Technology Holdings Limited | Displaying selected portions of data sets on display devices |
US9071580B2 (en) | 2010-11-01 | 2015-06-30 | Blackberry Limited | Method and system for securing data of a mobile communications device |
US20120203620A1 (en) | 2010-11-08 | 2012-08-09 | Douglas Howard Dobyns | Techniques For Wireless Communication Of Proximity Based Marketing |
US8560648B2 (en) | 2010-11-10 | 2013-10-15 | Microsoft Corporation | Location control service |
EP2453631B1 (en) * | 2010-11-15 | 2016-06-22 | BlackBerry Limited | Data source based application sandboxing |
US8504831B2 (en) | 2010-12-07 | 2013-08-06 | At&T Intellectual Property I, L.P. | Systems, methods, and computer program products for user authentication |
US20120150577A1 (en) | 2010-12-14 | 2012-06-14 | Microsoft Corporation | Meeting lifecycle management |
EP2656007B1 (en) | 2010-12-20 | 2016-03-16 | TomTom International B.V. | Mobile device that operates differently in different regions |
ES2630014T3 (en) | 2011-01-20 | 2017-08-17 | Nec Corporation | Communication system, control device, policy management device, communication method, and program |
US8898742B2 (en) * | 2011-10-11 | 2014-11-25 | Paramount Pictures Corporation | Systems and methods for controlling access to content distributed over a network |
US8566923B2 (en) | 2011-02-01 | 2013-10-22 | Rockwell Automation Technologies, Inc. | Enhanced organization and automatic navigation of display screens facilitating automation control |
US20120246719A1 (en) | 2011-03-21 | 2012-09-27 | International Business Machines Corporation | Systems and methods for automatic detection of non-compliant content in user actions |
US8577391B2 (en) | 2011-03-31 | 2013-11-05 | Verizon Patent And Licensing Inc. | Providing a location-based service using real-time radio access network (RAN) modeling |
CN103548374A (en) | 2011-04-12 | 2014-01-29 | 西里克斯系统公司 | Server remotely executing an application using geographic location data of a mobile device |
GB2490310A (en) | 2011-04-18 | 2012-10-31 | Nearfield Comm Ltd | Method and system for controlling access to a service. |
US8789133B2 (en) | 2011-04-20 | 2014-07-22 | Cisco Technology, Inc. | Location based content filtering and dynamic policy |
US20120290544A1 (en) | 2011-05-09 | 2012-11-15 | International Business Machines Corporation | Data compliance management |
US9119067B2 (en) | 2011-06-03 | 2015-08-25 | Apple Inc. | Embodiments of a system and method for securely managing multiple user handles across multiple data processing devices |
US8958559B2 (en) | 2011-06-03 | 2015-02-17 | Apple Inc. | System and method for secure instant messaging |
US9078128B2 (en) | 2011-06-03 | 2015-07-07 | Apple Inc. | System and method for secure identity service |
US20120331527A1 (en) | 2011-06-22 | 2012-12-27 | TerraWi, Inc. | Multi-layer, geolocation-based network resource access and permissions |
US8875222B1 (en) | 2011-06-30 | 2014-10-28 | Emc Corporation | Efficient XACML access control processing |
WO2013006553A1 (en) | 2011-07-01 | 2013-01-10 | Fiberlink Communications Corporation | Rules based actions for mobile device management |
US8423511B1 (en) | 2011-07-07 | 2013-04-16 | Symantec Corporation | Systems and methods for securing data on mobile devices |
US9396345B2 (en) | 2011-07-10 | 2016-07-19 | Blendology Limited | Electronic data sharing device and method of use |
WO2013007675A2 (en) | 2011-07-10 | 2013-01-17 | Blendology Limited | An electronic data sharing device and method of use |
AU2012282577B2 (en) | 2011-07-10 | 2017-09-07 | Blendology Limited | An electronic data sharing device and method of use |
WO2013007683A1 (en) | 2011-07-10 | 2013-01-17 | Blendology Limited | An electronic data sharing device and method of use |
IL214209A0 (en) | 2011-07-20 | 2012-01-31 | Israel Aerospace Ind Ltd | System and method for location based control of elements of a mobile communication device |
US8850536B2 (en) | 2011-08-05 | 2014-09-30 | Safefaces LLC | Methods and systems for identity verification in a social network using ratings |
US8571538B2 (en) | 2011-08-10 | 2013-10-29 | Qualcomm Incorporated | Web-based parental controls for wireless devices |
US8699998B2 (en) | 2011-08-10 | 2014-04-15 | Qualcomm Incorporated | Controlling text messages on a mobile device |
US20130045729A1 (en) | 2011-08-17 | 2013-02-21 | Microsoft Corporation | Location-based promotion of applications |
US8898750B2 (en) | 2011-08-23 | 2014-11-25 | Cisco Technology, Inc. | Connecting remote and local networks using an identification device associated with the remote network |
US9659165B2 (en) | 2011-09-06 | 2017-05-23 | Crimson Corporation | Method and apparatus for accessing corporate data from a mobile device |
US8756348B2 (en) * | 2011-09-14 | 2014-06-17 | Barco N.V. | Electronic tool and methods for meetings |
MY183320A (en) | 2011-09-19 | 2021-02-18 | E Lock Corp Sdn Bhd | Method of controlling access to an internet-based application |
US8756651B2 (en) | 2011-09-27 | 2014-06-17 | Amazon Technologies, Inc. | Policy compliance-based secure data access |
US8799994B2 (en) * | 2011-10-11 | 2014-08-05 | Citrix Systems, Inc. | Policy-based application management |
US9529996B2 (en) * | 2011-10-11 | 2016-12-27 | Citrix Systems, Inc. | Controlling mobile device access to enterprise resources |
US8959572B2 (en) * | 2011-10-28 | 2015-02-17 | Google Inc. | Policy enforcement of client devices |
US8689281B2 (en) | 2011-10-31 | 2014-04-01 | Hewlett-Packard Development Company, L.P. | Management of context-aware policies |
US8713646B2 (en) | 2011-12-09 | 2014-04-29 | Erich Stuntebeck | Controlling access to resources on a network |
US9171146B2 (en) | 2011-12-14 | 2015-10-27 | Intel Corporation | Method and system for monitoring calls to an application program interface (API) function |
US8622836B2 (en) | 2011-12-22 | 2014-01-07 | Igt | Use of wireless signal strength to determine connection |
US9009794B2 (en) | 2011-12-30 | 2015-04-14 | Rovi Guides, Inc. | Systems and methods for temporary assignment and exchange of digital access rights |
KR101595431B1 (en) | 2012-01-16 | 2016-02-18 | 엘지전자 주식회사 | Method and apparatus for providing proximity service in wireless communication system |
US20140053250A1 (en) * | 2012-02-10 | 2014-02-20 | University Of Utah Research Foundation | Access to Web Application via a Mobile Computing Device |
US9680763B2 (en) | 2012-02-14 | 2017-06-13 | Airwatch, Llc | Controlling distribution of resources in a network |
US9705813B2 (en) | 2012-02-14 | 2017-07-11 | Airwatch, Llc | Controlling distribution of resources on a network |
US20130226696A1 (en) | 2012-02-24 | 2013-08-29 | Meetme, Inc. | Social discovery system using computing device proximity |
US8774041B2 (en) | 2012-03-02 | 2014-07-08 | Qualcomm Incorporated | Proximity-based wireless handshaking for connection establishment |
US8769003B2 (en) | 2012-05-09 | 2014-07-01 | Qualcomm Innovation Center, Inc. | Method for proximity determination between mobile peers while maintaining privacy |
BR102012010913A2 (en) | 2012-05-09 | 2014-05-13 | Hangar 4 Projetos Ltda | METHOD FOR DATA COMMUNICATION BETWEEN DEVICES THROUGH SOUND WAVES |
US8577392B1 (en) | 2012-06-13 | 2013-11-05 | Apple Inc. | System and method of determining location of wireless communication devices/persons for controlling/adjusting operation of devices based on the location |
US8732792B2 (en) * | 2012-06-20 | 2014-05-20 | Ricoh Company, Ltd. | Approach for managing access to data on client devices |
US20140053229A1 (en) * | 2012-08-15 | 2014-02-20 | Appsense Limited | Systems and Methods for Policy Propagation and Enforcement |
CN103947151A (en) | 2012-08-24 | 2014-07-23 | 索尼公司 | Information processing device, information storage device, server, information processing system, information processing method, and program |
US8862155B2 (en) | 2012-08-30 | 2014-10-14 | Time Warner Cable Enterprises Llc | Apparatus and methods for enabling location-based services within a premises |
KR101974820B1 (en) | 2012-09-10 | 2019-08-23 | 삼성전자주식회사 | Method for controlling a device and device performing the same |
US10042603B2 (en) | 2012-09-20 | 2018-08-07 | Samsung Electronics Co., Ltd. | Context aware service provision method and apparatus of user device |
US8770484B2 (en) | 2012-09-21 | 2014-07-08 | Alcatel Lucent | Data exchange using streamed barcodes |
US8990895B2 (en) | 2012-09-23 | 2015-03-24 | Farhad David Nosrati | Method and apparatus for a portable wireless security device |
US8933778B2 (en) | 2012-09-28 | 2015-01-13 | Intel Corporation | Mobile device and key fob pairing for multi-factor security |
US8904186B2 (en) | 2012-09-28 | 2014-12-02 | Intel Corporation | Multi-factor authentication process |
US20140096180A1 (en) | 2012-09-28 | 2014-04-03 | Ansuya Negi | System, devices, and methods for proximity-based parental controls |
US9253811B2 (en) | 2012-10-19 | 2016-02-02 | Verizon Patent And Licensing Inc. | Network-assisted device-to-device communication |
US9276684B2 (en) | 2012-12-10 | 2016-03-01 | Qualcomm Incorporated | Efficient means of broadcast and relaying information between wireless terminals |
US9451551B2 (en) | 2012-12-21 | 2016-09-20 | Apple Inc. | Controlling a power state of a cellular packet data subsystem in a portable electronic device |
US9910499B2 (en) | 2013-01-11 | 2018-03-06 | Samsung Electronics Co., Ltd. | System and method for detecting three dimensional gestures to initiate and complete the transfer of application data between networked devices |
US20140213179A1 (en) | 2013-01-29 | 2014-07-31 | Einar Rosenberg | System and Method for Establishing Communications between Two Devices |
US9848276B2 (en) | 2013-03-11 | 2017-12-19 | Rovi Guides, Inc. | Systems and methods for auto-configuring a user equipment device with content consumption material |
US9432361B2 (en) | 2013-03-13 | 2016-08-30 | Lookout, Inc. | System and method for changing security behavior of a device based on proximity to another device |
US9247014B1 (en) | 2013-03-13 | 2016-01-26 | Intellectual Ventures Fund 79 Llc | Methods, devices, and mediums associated with recommending user applications |
US10754966B2 (en) | 2013-04-13 | 2020-08-25 | Airwatch Llc | Time-based functionality restrictions |
US9058495B2 (en) | 2013-05-16 | 2015-06-16 | Airwatch Llc | Rights management services integration with mobile device management |
US10251059B2 (en) | 2014-01-21 | 2019-04-02 | Everykey Inc. | Authentication device and method |
US10025612B2 (en) | 2016-03-18 | 2018-07-17 | Airwatch Llc | Enforcing compliance rules against hypervisor and host device using guest management components |
-
2013
- 2013-03-14 US US13/828,922 patent/US20140280955A1/en not_active Abandoned
-
2017
- 2017-02-10 US US15/430,184 patent/US11824644B2/en active Active
Patent Citations (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030164853A1 (en) * | 2000-12-29 | 2003-09-04 | Min Zhu | Distributed document sharing |
US20060067250A1 (en) * | 2004-09-30 | 2006-03-30 | Boyer David G | Method and apparatus for launching a conference based on presence of invitees |
US20070162417A1 (en) * | 2006-01-10 | 2007-07-12 | Kabushiki Kaisha Toshiba | System and method for selective access to restricted electronic documents |
US20080065727A1 (en) * | 2006-09-13 | 2008-03-13 | Majors Kenneth D | Conferencing system with improved access |
US20100100972A1 (en) * | 2008-08-08 | 2010-04-22 | Jacques Lemieux | Approaches for a location aware client |
US20110135083A1 (en) * | 2009-12-04 | 2011-06-09 | Charles Steven Lingafelt | Methods to Improve Fraud Detection on Conference Calling Systems Based on Observation of Participants' Call Time Durations |
US20110141276A1 (en) * | 2009-12-14 | 2011-06-16 | Apple Inc. | Proactive Security for Mobile Devices |
US20140237041A1 (en) * | 2013-02-19 | 2014-08-21 | Cisco Technology, Inc. | Automatic future meeting scheduler based upon locations of meeting participants |
Non-Patent Citations (1)
Title |
---|
"Secret Sharing" by Wikipedia, January 10, 2012. * |
Cited By (73)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10684736B2 (en) * | 2007-02-13 | 2020-06-16 | Visual Targeting Corporation | Method for defining a presentation format targetable to a demographic |
US9124493B2 (en) | 2008-12-19 | 2015-09-01 | Openpeak Inc. | System and method for ensuring compliance with organizational polices |
US10726126B2 (en) | 2008-12-19 | 2020-07-28 | Samsung Electronics Co., Ltd. | System and method for ensuring compliance with organizational policies |
US10187347B2 (en) * | 2010-10-08 | 2019-01-22 | Brian Lee Moffat | Data sharing system method |
US10587563B2 (en) * | 2010-10-08 | 2020-03-10 | Brian Lee Moffat | Private data sharing system |
US20170054674A1 (en) * | 2010-10-08 | 2017-02-23 | Brian Lee Moffat | Data sharing system method |
US9135418B2 (en) | 2011-10-10 | 2015-09-15 | Openpeak Inc. | System and method for creating secure applications |
US9165139B2 (en) | 2011-10-10 | 2015-10-20 | Openpeak Inc. | System and method for creating secure applications |
US9535411B2 (en) * | 2012-03-05 | 2017-01-03 | Siemens Aktiengesellschaft | Cloud enabled building automation system |
US20130274940A1 (en) * | 2012-03-05 | 2013-10-17 | Siemens Corporation | Cloud enabled building automation system |
US11847495B2 (en) | 2013-03-15 | 2023-12-19 | Advanced Elemental Technologies, Inc. | Systems and methods configured to enable an operating system for connected computing that supports user use of suitable to user purpose resources sourced from one or more resource ecospheres |
US11822662B2 (en) | 2013-03-15 | 2023-11-21 | Advanced Elemental Technologies, Inc. | Methods and systems for secure and reliable identity-based computing |
US11528233B2 (en) * | 2013-03-15 | 2022-12-13 | Advanced Elemental Technologies, Inc. | Systems and methods for establishing a user purpose fulfillment computing platform |
US10699201B2 (en) * | 2013-06-04 | 2020-06-30 | Ent. Services Development Corporation Lp | Presenting relevant content for conversational data gathered from real time communications at a meeting based on contextual data associated with meeting participants |
US20150074813A1 (en) * | 2013-09-06 | 2015-03-12 | Oracle International Corporation | Protection of resources downloaded to portable devices from enterprise systems |
US9497194B2 (en) * | 2013-09-06 | 2016-11-15 | Oracle International Corporation | Protection of resources downloaded to portable devices from enterprise systems |
US11570160B2 (en) | 2013-09-23 | 2023-01-31 | Airwatch, Llc | Securely authorizing access to remote resources |
US10798076B2 (en) * | 2013-09-23 | 2020-10-06 | Airwatch, Llc | Securely authorizing access to remote resources |
US10257180B2 (en) | 2013-09-23 | 2019-04-09 | Airwatch Llc | Securely authorizing access to remote resources |
US9185099B2 (en) * | 2013-09-23 | 2015-11-10 | Airwatch Llc | Securely authorizing access to remote resources |
US20190238526A1 (en) * | 2013-09-23 | 2019-08-01 | Airwatch, Llc | Securely authorizing access to remote resources |
US20140201816A1 (en) * | 2013-09-23 | 2014-07-17 | Sky Socket, Llc | Securely Authorizing Access to Remote Resources |
US9769141B2 (en) | 2013-09-23 | 2017-09-19 | Airwatch Llc | Securely authorizing access to remote resources |
US9591562B2 (en) * | 2013-10-31 | 2017-03-07 | Aruba Networks, Inc. | Provisioning access point bandwidth based on predetermined events |
US20150120930A1 (en) * | 2013-10-31 | 2015-04-30 | Aruba Networks.Com | Provisioning access point bandwidth based on predetermined events |
US20150312260A1 (en) * | 2014-04-25 | 2015-10-29 | Samsung Electronics Co., Ltd. | Methods of providing social network service and server performing the same |
US9781123B2 (en) * | 2014-04-25 | 2017-10-03 | Samsung Electronics Co., Ltd. | Methods of providing social network service and server performing the same |
US9723003B1 (en) * | 2014-06-06 | 2017-08-01 | Amazon Technologies, Inc. | Network beacon based credential store |
US10063592B1 (en) * | 2014-06-06 | 2018-08-28 | Amazon Technologies, Inc. | Network authentication beacon |
US10129299B1 (en) * | 2014-06-06 | 2018-11-13 | Amazon Technologies, Inc. | Network beacon management of security policies |
US9350818B2 (en) | 2014-09-05 | 2016-05-24 | Openpeak Inc. | Method and system for enabling data usage accounting for unreliable transport communication |
US9232012B1 (en) | 2014-09-05 | 2016-01-05 | Openpeak Inc. | Method and system for data usage accounting in a computing device |
US10410154B2 (en) | 2014-09-05 | 2019-09-10 | Vmware, Inc. | Method and system for enabling data usage accounting through a relay |
US10943198B2 (en) | 2014-09-05 | 2021-03-09 | Vmware, Inc. | Method and system for enabling data usage accounting through a relay |
US9232013B1 (en) | 2014-09-05 | 2016-01-05 | Openpeak Inc. | Method and system for enabling data usage accounting |
US9106538B1 (en) | 2014-09-05 | 2015-08-11 | Openpeak Inc. | Method and system for enabling data usage accounting through a relay |
US9100390B1 (en) | 2014-09-05 | 2015-08-04 | Openpeak Inc. | Method and system for enrolling and authenticating computing devices for data usage accounting |
US9720917B2 (en) * | 2015-02-17 | 2017-08-01 | International Business Machines Corporation | Electronic meeting question management |
US9753927B2 (en) * | 2015-02-17 | 2017-09-05 | International Business Machines Corporation | Electronic meeting question management |
US10599703B2 (en) * | 2015-02-17 | 2020-03-24 | International Business Machines Corporation | Electronic meeting question management |
US20160239537A1 (en) * | 2015-02-17 | 2016-08-18 | International Business Machines Corporation | Electronic meeting question management |
US20160239489A1 (en) * | 2015-02-17 | 2016-08-18 | International Business Machines Corporation | Electronic meeting question management |
US9232078B1 (en) | 2015-03-16 | 2016-01-05 | Openpeak Inc. | Method and system for data usage accounting across multiple communication networks |
US9967358B2 (en) * | 2015-03-26 | 2018-05-08 | International Business Machines Corporation | Collaborative based caching |
US20160285991A1 (en) * | 2015-03-26 | 2016-09-29 | International Business Machines Corporation | Collaborative based caching |
US20180183810A1 (en) * | 2015-08-21 | 2018-06-28 | PushPull Technology Limited | Data Collaboration |
US11038687B2 (en) * | 2015-08-21 | 2021-06-15 | PushPull Technology Limited | Data collaboration |
US10558784B2 (en) * | 2015-09-04 | 2020-02-11 | Cisco Technology, Inc. | Time and motion data fusion for determining and remedying issues based on physical presence |
US20170068793A1 (en) * | 2015-09-04 | 2017-03-09 | Cisco Technology, Inc. | Time and motion data fusion for determining and remedying issues based on physical presence |
US10298577B1 (en) * | 2016-03-31 | 2019-05-21 | Amazon Technologies, Inc. | Credential vending to processes |
US20180014295A1 (en) * | 2016-07-05 | 2018-01-11 | Fujitsu Limited | Information processing system, server, and terminal device |
US10477558B2 (en) * | 2016-07-05 | 2019-11-12 | Fujitsu Limited | Information processing system, server, and terminal device |
US10587485B2 (en) | 2016-10-18 | 2020-03-10 | Airwatch Llc | Federated mobile device management |
US10326671B2 (en) * | 2016-10-18 | 2019-06-18 | Airwatch Llc | Federated mobile device management |
US11477096B2 (en) | 2016-10-18 | 2022-10-18 | Airwatch Llc | Federated mobile device management |
US11240316B1 (en) * | 2017-04-11 | 2022-02-01 | Wells Fargo Bank, N.A. | Systems and methods for optimizing information collaboration |
US11388245B1 (en) | 2017-04-11 | 2022-07-12 | Wells Fargo Bank, N.A. | Systems and methods for content delivery |
US11310008B2 (en) * | 2017-10-23 | 2022-04-19 | Kyocera Corporation | Data transmission with multiple numerologies for multiple devices with common geographical location dependent control information |
US11038886B1 (en) * | 2018-02-08 | 2021-06-15 | Wells Fargo Bank, N.A. | Compliance management system |
US11190512B2 (en) | 2019-04-17 | 2021-11-30 | Microsoft Technology Licensing, Llc | Integrity attestation of attestation component |
US11392467B2 (en) | 2019-04-17 | 2022-07-19 | Microsoft Technology Licensing, Llc | Failover between decentralized identity stores |
US11381567B2 (en) | 2019-04-29 | 2022-07-05 | Microsoft Technology Licensing, Llc | Execution of an application within a scope of user-granted permission |
US11429743B2 (en) | 2019-04-29 | 2022-08-30 | Microsoft Technology Licensing, Llc | Localization of DID-related claims and data |
US11411959B2 (en) * | 2019-05-03 | 2022-08-09 | Microsoft Technology Licensing, Llc | Execution of application in a container within a scope of user-granted permission |
US11222137B2 (en) | 2019-05-03 | 2022-01-11 | Microsoft Technology Licensing, Llc | Storing and executing an application in a user's personal storage with user granted permission |
US11886605B2 (en) * | 2019-09-30 | 2024-01-30 | Red Hat, Inc. | Differentiated file permissions for container users |
US11722491B1 (en) * | 2020-06-30 | 2023-08-08 | Amazon Technologies, Inc. | Cumulative risk-based scoring for quorum authorization |
US11914696B1 (en) | 2020-09-30 | 2024-02-27 | Amazon Technologies, Inc. | Quorum-based access control management |
US20220405412A1 (en) * | 2021-06-21 | 2022-12-22 | Microsoft Technology Licensing, Llc | Configuration of default sensitivity labels for network file storage locations |
US11783073B2 (en) * | 2021-06-21 | 2023-10-10 | Microsoft Technology Licensing, Llc | Configuration of default sensitivity labels for network file storage locations |
US11652823B1 (en) * | 2022-12-19 | 2023-05-16 | Uab 360 It | Systems and methods for controlling access |
US11855996B1 (en) | 2022-12-19 | 2023-12-26 | Uab 360 It | Systems and methods for controlling access |
US11855999B1 (en) | 2022-12-19 | 2023-12-26 | Uab 360 It | Systems and methods for controlling access |
Also Published As
Publication number | Publication date |
---|---|
US20170155660A1 (en) | 2017-06-01 |
US11824644B2 (en) | 2023-11-21 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11824644B2 (en) | Controlling electronically communicated resources | |
US10116583B2 (en) | Controlling resources used by computing devices | |
US10075849B2 (en) | Secure distribution of electronic content | |
US9401915B2 (en) | Secondary device as key for authorizing access to resources | |
AU2016238935B2 (en) | Secondary device as key for authorizing access to resources | |
US10084789B2 (en) | Peer to peer enterprise file sharing | |
US10257194B2 (en) | Distribution of variably secure resources in a networked environment | |
US10986095B2 (en) | Systems and methods for controlling network access | |
US20130212278A1 (en) | Controlling distribution of resources in a network | |
CN107534664B (en) | Multi-factor authorization for IEEE802.1X enabled networks | |
CN112840339A (en) | Progressive access to data and device functionality | |
US9584508B2 (en) | Peer to peer enterprise file sharing | |
US9571288B2 (en) | Peer to peer enterprise file sharing | |
US11038687B2 (en) | Data collaboration | |
US20210097023A1 (en) | Decentralized Data System | |
WO2023141864A1 (en) | Conference data transmission method, apparatus and system, electronic device and readable medium |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: SKY SOCKET LLC, GEORGIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:STUNTEBECK, ERICH;DIRICO, JOHN;REEL/FRAME:030003/0005 Effective date: 20130314 |
|
AS | Assignment |
Owner name: AIRWATCH LLC, GEORGIA Free format text: MERGER;ASSIGNOR:SKY SOCKET, LLC;REEL/FRAME:033369/0291 Effective date: 20140623 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |