Patent Grant
9628268
As electronic and digital content use in enterprise. settings and/or other organizational settings has become the preferred mechanism for project, task, and work flow management, so has the need for streamlined collaboration and sharing of digital content and documents. In such collaboration environments, multiple users share, access, and otherwise perform actions or tasks on content and files in shared workspaces. This shared access and collaboration requires high availability of the data (e.g., an unfettered ability to download and upload files) as any number of users may have access to a file at any given time.
The collaboration environments can include features or mechanisms that add security mechanisms to the access of content and files in the shared workspaces. Unfortunately, these mechanisms do not provide variable client-level control of the security mechanism and thus a need exists for a system that overcomes the above problems, as well as one that provides additional benefits.
Overall, the examples herein of some prior or related systems and their associated limitations are intended to be illustrative and not exclusive. Other limitations of existing or prior systems will become apparent to those of skill in the art upon reading the following.
The following description and drawings are illustrative and are not to be construed as limiting. Numerous specific details are described to provide a thorough understanding of the disclosure. However, in certain instances, well-known or conventional details are not described in order to avoid obscuring the description. References to one or an embodiment in the present disclosure can be, but not necessarily are, references to the same embodiment; and, such references mean at least one of the embodiments.
Reference in this specification to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the disclosure. The appearances of the phrase “in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. Moreover, various features are described which may be exhibited by some embodiments and not by others. Similarly, various requirements are described which may be requirements for some embodiments but not other embodiments.
The terms used in this specification generally have their ordinary meanings in the art, within the context of the disclosure, and in the specific context where each term is used. Certain terms that are used to describe the disclosure are discussed below, or elsewhere in the specification, to provide additional guidance to the practitioner regarding the description of the disclosure. For convenience, certain terms may be highlighted, for example using italics and/or quotation marks. The use of highlighting has no influence on the scope and meaning of a term; the scope and meaning of a term is the same, in the same context, whether or not it is highlighted. It will be appreciated that same thing can be said in more than one way.
Consequently, alternative language and synonyms may be used for any one or more of the terms discussed herein, nor is any special significance to be placed upon whether or not a term is elaborated or discussed herein. Synonyms for certain terms are provided. A recital of one or more synonyms does not exclude the use of other synonyms. The use of examples anywhere in this specification including examples of any terms discussed herein is illustrative only, and is not intended to further limit the scope and meaning of the disclosure or of any exemplified term. Likewise, the disclosure is not limited to various embodiments given in this specification.
Without intent to limit the scope of the disclosure, examples of instruments, apparatus, methods and their related results according to the embodiments of the present disclosure are given below. Note that titles or subtitles may be used in the examples for convenience of a reader, which in no way should limit the scope of the disclosure. Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains. In the case of conflict, the present document, including definitions will control.
Collaboration environments can include features or mechanisms that provide security through the use of data item (or file) encryption. The file encryption features can, for example, include encrypting an encryption key used that is used to encrypt a data or content item (e.g., a file). However, the current mechanisms that provide security through data encryption do not provide for client-side (e.g., enterprise-side) control and configurability.
Embodiments of the present disclosure include systems and methods for facilitating remote key management services in a collaborative cloud-based environment. More specifically, the remote key management architecture and techniques described herein provide for local key encryption and automatic generation of a reason code associated with content access, The reason code is used by a remote client device (e.g., an enterprise client) to control a second (remote) layer of key encryption. The remote client device provides client-side control and configurability of the second layer of key encryption.
In various embodiments, the remote key management engine provides the client-side control and configurability through the use of a rule engine that can process a generated access reason to determine whether or not to encrypt or decrypt a corresponding encryption key based, at least in part, on a set of pre-defined client configurable rules. Additionally, in various embodiments a kill switch is provided to the client for facilitating remote kill capabilities.
The client devices 102 can be any system and/or device, and/or any combination of devices/systems that is able to establish a connection, including wired, wireless, cellular connections with another device, a server and/or other systems such as host server 100 and/or notification server 150. Client devices 102 will typically include a display and/or other output functionalities to present information and data exchanged between among the devices 102 and/or the host server 100 and/or notification server 150.
For example, the client devices 102 can include mobile, hand held or portable devices or non-portable devices and can be any of but not limited to, a server desktop, a desktop computer, a computer cluster, or portable devices including, a notebook, a laptop computer, a handheld computer, a palmtop computer, a mobile phone, a cell phone, a smart phone, a PDA, a Blackberry device, a Treo, a handheld tablet (e.g. an iPad, a Galaxy, Xoom Tablet, etc.), a tablet PC, a thin-client, a hand held console, a hand held gaming device or console, an iPhone, and/or any other portable, mobile, hand held devices, etc. running on any platform or any operating system (e.g., Mac-based OS (OS X, iOS, etc,), Windows-based OS (Windows Mobile, Windows 7, etc.), Android, Blackberry OS, Embedded Linux platforms, Palm OS, Symbian platform). In one embodiment, the client devices 102, host server 100, and app server 110 are coupled via a network 106. In some embodiments, the devices 102 and host server 100 may be directly connected to one another.
The input mechanism on client devices 102 can include touch screen keypad (including single touch, multi-touch, gesture sensing in 2D or 3D, etc.), a physical keypad, a mouse, a pointer, a track pad, motion detector (e.g., including 1-axis, 2-axis, 3-axis accelerometer, etc.), a light sensor, capacitance sensor, resistance sensor, temperature sensor, proximity sensor, a piezoelectric device, device orientation detector (e.g., electronic compass, tilt sensor, rotation sensor, gyroscope, accelerometer), or a combination or variation of the above.
Signals received or detected indicating user activity at client devices 102 through one or more of the above input mechanism, or others, can be used in the disclosed technology by various users or collaborators collaborators 108) for accessing, through network 106, a web-based collaboration environment or online collaboration platform (e.g., hosted by the host server 100).
The collaboration platform or environment hosts workspaces with work items that one or more users can access (e.g., view, edit, update, revise, comment, download, preview, tag, or otherwise manipulate, etc.). A work item can generally include any type of digital or electronic content that can be viewed or accessed via an electronic device (e.g., device 102). The digital content can include .pdf files, .doc, slides (e.g., Powerpoint slides), images, audio files, multimedia content, web pages, blogs, etc. A workspace can generally refer to any grouping of a set of digital content in the collaboration platform. The grouping can be created, identified, or specified by a user or through other means. This user may be a creator user or administrative user, for example.
In general, a workspace can be associated with a set of users or collaborators (e.g., collaborators 108) which have access to the content included therein. The levels of access (e.g., based on permissions or rules) of each user or collaborator to access the content in a given workspace may be the same or may vary among the users. Each user may have their own set of access rights to every piece of content in the workspace, or each user may be different access rights to different pieces of content. Access rights may be specified by a user associated with a work space and/or a user who created/uploaded a particular piece of content to the workspace, or any other designated user or collaborator.
In general, the collaboration platform allows multiple users or collaborators to access or collaborate efforts on work items such each user can see, remotely, edits, revisions, comments, or annotations being made to specific work items through their own user devices. For example, a user can upload a document to a work space for other users to access (e.g., for viewing, editing, commenting, signing-off, or otherwise manipulating). The user can login to the online platform and upload the document (or any other type of work item) to an existing work space or to a new work space. The document can be shared with existing users or collaborators in a work space.
A diagrammatic illustration of the online collaboration environment and the relationships between workspaces and users/collaborators are illustrated with further reference to the example of
In one embodiment, client devices 102 communicate with the host server 100 and/or people search engine 150 over network 106. In general, network 106, over which the client devices 102, the host server 100, and/or people search engine 150 communicate, may be a cellular network, a telephonic network, an open network, such as the Internet, or a private network, such as an intranet and/or the extranet, or any combination thereof, For example, the Internet can provide file transfer, remote log in, email, news, RSS, cloud-based services, instant messaging, visual voicemail, push mail, VoIP, and other services through any known or convenient protocol, such as, but is not limited to the TCP/IP protocol, Open System Interconnections (OSI), FTP, UPnP, iSCSI, NSF, ISDN, PDH, RS-232, SDH, SONET, etc.
The network 106 can be any collection of distinct networks operating wholly or partially in conjunction to provide connectivity to the client devices 102 and the host server 100 and may appear as one or more networks to the serviced systems and devices. In one embodiment, communications to and from the client devices 102 can be achieved by, an open network, such as the Internet, or a private network, such as an intranet and/or the extranet. In one embodiment, communications can be achieved by a secure communications protocol, such as secure sockets layer (SSL), or transport layer security (TLS).
In addition, communications can be achieved via one or more networks, such as, but are not limited to, one or more of WiMax, a Local Area Network (LAN), Wireless Local Area Network (WLAN), a Personal area network (PAN), a Campus area network (CAN), a Metropolitan area network (MAN), a Wide area network. (WAN), a Wireless wide area network (WWAN), enabled with technologies such as, by way of example, Global System for Mobile Communications (GSM), Personal Communications Service (PCS), Digital Advanced Mobile Phone Service (D-Amps), Bluetooth, Wi-Fi, Fixed Wireless Data, 2G, 2.5G, 3G, 4G, IMT-Advanced, pre-4G, 3G LTE, 3GPP LTE, LTE Advanced, mobile WiMax, WiMax 2, WirelessMAN-Advanced networks, enhanced data rates for GSM evolution (EDGE), General packet radio service (GPRS), enhanced GPRS, iBurst, UMTS, HSPDA, HSUPA, HSPA, UMTS-TDD, 1xRTT, EV-DO, messaging protocols such as, TCP/IP, SMS, MMS, extensible messaging and presence protocol (XMPP), real time messaging protocol (RTMP), instant messaging and presence protocol (1MPP), instant messaging, USSD, IRC, or any other wireless data networks or messaging protocols.
In one embodiment, actions performed on work items or other activities that occur in a workspace can be detected in real time or in near real time. The host server can generate notifications or notification events for one or more of the plurality of activities and select one or more recipients for each notification. Various mechanisms or external messaging applications can then be used to notify users or collaborators, including through the web interface to access the collaboration platform, via email, and/or SMS, for example.
The web-based platform for collaborating on projects or jointly working on documents can be used by individual users and shared among collaborators. In addition, the collaboration platform can be deployed in an organized setting including but not limited to, a company (e.g., an enterprise setting), a department in a company, an academic institution, a department in an academic institution, a class or course setting, or any other types of organizations or organized setting.
When deployed in an organizational setting, multiple workspaces (e.g., workspace AN) may be created to support different projects or a variety of work flows. Each workspace may have its own associate work items. For example, work space A 205 may be associated with work items 215, work space B 225 may be associated with work items 235, and work space N may be associated with work items 255. The work items 215, 235, and 255 may be unique to each work space but need not be. For example, a particular word document may be associated with only one work space (e.g., work space A 205) or it may be associated with multiple work spaces (e.g., Work space A 205 and work space B 225, etc.).
In general, each work space has a set of users or collaborators associated with it. For example, work space A 205 is associated with multiple users or collaborators 206. In some instances, work spaces deployed in an enterprise may be department specific. For example, work space B may be associated with department 210 and some users shown as example user A 208 and workspace N 245 may be associated with departments 212 and 216 and users shown as example user B 214.
Each user associated with a work space may generally access the work items associated with the work space. The level of access may depend on permissions associated with the specific work space, and/or with a specific work item. Permissions may be set for the work space or set individually on a per work item basis. For example, the creator of a work space (e.g., one of user A 208 who creates work space B) may set one permission setting applicable to all work items 235 for other associated users and/or users associated with the affiliate department 210, for example. Creator user A 208 may also set different permission settings fir each work item, which may be the same for different users, or varying for different users.
In each work space A, B, . . . , N, when an action is performed on a work item by a given user or any other activity is detected in the work space, other users in the same work space may be notified (e.g., in real time or in near real time, or not in real time). Activities which trigger real time notifications can include, by way of example but not limitation, adding, deleting, or modifying collaborators in the work space, uploading, downloading, adding, deleting a work item in the work space, creating a discussion topic in the work space.
Specifically, items or content (content items) downloaded or edited in accordance with the techniques described in the present disclosure can cause notifications to be generated. Such notifications can be sent to relevant users to notify them of actions surrounding a download, an edit, a change, a modification, a new file, a conflicting version, an upload of an edited or modified file.
In one embodiment, in a user interface of the web-based collaboration platform where notifications are presented, users can, via the user interface, create action items (e.g., tasks) and delegate the action items to other users including collaborators pertaining to a work item 215, for example. The collaborators 206 may be in the same workspace A 205 or the user may include a newly invited collaborator. Similarly, in the same user interface where discussion topics can be created in a work space (e.g., work space A, B or N, etc.), actionable events on work items can be created and/or delegated/assigned to other users such as collaborators of a given work space 206 or other users. Through the same user interface, task status and updates from multiple users or collaborators can be indicated and reflected. In some instances, the users can perform the tasks (e.g., review or approve or reject, etc.) via the same user interface,
Each of users 316, 318, and 320 may individually use multiple different devices to access and/or manipulate work items 324 (e.g., content items) in the work space 302 with which they are associated with. For example users 316, 318, 320 may be collaborators on a project to which work items 324 are relevant. Since the work items 324 are hosted by the collaboration environment (e.g., a cloud-based environment), each user may access the work items 324 anytime, and from any physical location using any device (e.g., including devices they own or any shared/public/loaner device).
Work items to be edited or viewed may be accessed from the workspace 302 in accordance with the platform and/or application independent mechanisms. Users may also be notified of access, edit, modification, and/or upload related-actions performed on work items 324 by other users or any other types of activities detected in the work space 302. For example, if user 316 modifies a document, one or both of the other collaborators 318 and 320 can be notified of the modification. in real time, or near real-time, or not in real time. The notifications can be sent through any of all of the devices associated with a given user, in various formats including, one or more of, email, SMS, or via a pop-up window in a user interface in which the user uses to access the collaboration platform. In the event of multiple notifications, each notification may be depicted preferentially (e.g., ordering in the user interface) based on. user preferences and/or relevance to the user (e.g., implicit or explicit).
For example, a notification of a download, access, read, write, edit, or upload related activities may be presented in a feed stream among other notifications through a user interface on the user device according to relevancy to the user determined based on current or recent activity of the user in the web-based collaboration environment.
In one embodiment, a notification feed stream includes updates when an invited user accepts an invitation and/or successfully creates a new account through receipt of an invitation from an existing user. The invited user, upon creation of the new account, receives the account having enhanced features. The new user can automatically be connected to the existing user who sent the invitation. The system can also automatically prompt both users to query they wish to be collaborators in a common work space.
Work items hosted by a collaboration environment (e.g., a cloud-based collaboration environment) can be accessed by users (e.g., users 316, 318, and 320) via multiple different devices (e.g., devices 304-314) for viewing, editing, processing or performing other manipulations on work items. The devices can include applications for accessing a server hosting a cloud-based platform or service or other backend web services (hereinafter “cloud-based collaboration platform application”) and applications for viewing, editing, processing, or performing other manipulations on work items. The communication between such applications are generally facilitated by a communication mechanism of the OS. For example, in Android OS, the communication mechanism is based on “Intents”. As previously described, the underlying communication mechanism are generally insecure, and any data passed between applications are visible to all other application on a device.
As shown in the examples of
Referring first to
The content encryption/decryption engine 414 then passes the encryption key to the key service engine 416. The encryption/decryption engine 414 can also pass the encrypted data item 403 to the data store 415. Alternatively or additionally, the encrypted data item 403 (or a handle thereto or indicator thereof) can be passed to the key service engine 416. The key service engine 416 can use the encrypted data item 403 (or handle or indicator thereof) to associate one or more key encryption keys with the encrypted data item 403. The one or more key encryption keys can be later associated with and/or otherwise stored with the encrypted data 403 in the data store 415.
Continuing with the example of
The key service engine 416 also processes the content (upload) request 401 to identify metadata and a reason for the content request and generate a code associated with the reason. By way of example and not limitation, the metadata can include: an Internet Protocol (IP) address initiating the request, a user identifier (ID) associated with the request, a file identifier (ID) associated with the request, etc. Other metadata is also possible. By way of example and not limitation, reasons can include: to fulfill an upload data item request, to fulfill a download or access data item request, to fulfill a maintenance request, to perform another action (e.g., to perform a. text extraction request), to fulfill backend services, etc. Other reasons are also possible. Each reason can be coded with reason code.
The key service engine 416 also generates a remote key request 406 and sends the request to the enterprise client, As shown in the example of
The remote key service engine 420 includes a configurable rules processing engine that receives the remote key request including the encrypted encryption key, the generated reason code, and/or identified or generated metadata associated with the content request and processes the reason code and/or the metadata to determines whether to accept or reject the request based on one or more pre-configured rules. For example, rules can be generated to reject requests with particular reason codes, reject requests from particular IP addresses, reject particular users based on user ID, etc. The contents of an example remote key service engine 420 are shown and discussed in greater detail with reference to
If the remote key service engine 420 accepts the request, then the remote key service engine 420 selects a remote KEK and uses the remote KEK to encrypt the encrypted encryption key resulting in a twice encrypted key 408. The remote key service engine 420 then responds to the remote key request 406 with the twice encrypted key 408 and the remote KEK. Alternatively, the remote KEK and/or the twice encrypted key 408 can be stored at a remote data store associated with the enterprise client.
Lastly, the key service engine 416 directs the data store to store the twice encrypted key 408, the remote KEK, and the local KEK in data store 415. The twice encrypted key 408, the remote KEK, and the local KEK can be stored and/or otherwise associated with the corresponding encrypted data item 403 in the data store 415. Alternatively, if the remote KEK and/or twice encrypted key are stored remotely, information (e.g., IDs) with respect to the KEK and/or twice encrypted key may be associated with and/or stored with encrypted data item 403.
Referring next to
The key service engine 416 first determines whether the requested data item 445 is associated with remote key management functionality. For example, each data item can be associated with an enterprise and the key service engine 416 can identify the enterprise associated with the data item and determine if the enterprise has key management functionality. Alternatively or additionally, an enterprise or client can handle and/or otherwise manage keys on a case-by-case (or item-by-item) basis. In the example of
The key service engine 416 then determines and/or otherwise identifies information associated with data item 445 and accesses and/or otherwise receives or retrieves the information from the data store 415. In the example of
As discussed above, the remote key service engine 420 includes a configurable rules processing engine that receives the remote key request including the twice encrypted encryption key, the generated reason code, identified or generated metadata associated with the content request, and/or the remote KEK. The remote key service engine 420 processes the reason code and/or the metadata to determine whether to accept or reject the request based on one or more pre-configured rules. As discussed above, rules can be generated to reject requests with particular reason codes, reject requests from particular IP addresses, reject particular users based on user ID, etc. The contents of an example remote key service engine 420 are shown and discussed in greater detail with reference to
If the remote key service engine 420 accepts the request, then the remote key service engine 420 decrypts the twice encrypted key using the remote KEK and provides the once encrypted key 439 back to the key service engine 416. The key service engine 416 receives the once encrypted key 439 and decrypts the once encrypted key 439 using the local KEK. resulting in the encryption key 441. The key service engine 416 then provides the encryption key 441 to the content encryption/decryption engine 414 to decrypt the encrypted data item 443 resulting in the data item 445. The content encryption/decryption engine 414 provides the data item 445 to the content interface 412 which, in turn, responds to the content request 431 with the data item 445.
The key service engine 500 can be part of a web-based or online collaboration environment which can generally be a cloud-based service. The key service engine 500 can include, for example, a request interface 505, a key service proxy 510, a key encryption/decryption engine 515, a reason generation engine 520, a metadata engine 525, and an enterprise client interface 530. Additional or fewer components/modules/engines can be included in the key service engine 500 and/or each illustrated component. Further, although illustrated as included as part of the key service engine 500, the components/modules/engines can be physically and/or functionally distributed.
The request interface 505 can be configured to communicate with other components of the cloud-based platform. Similarly, the enterprise client interface 530 can be configured to communicate with components of a remote client device (e.g., enterprise client computers or devices).
The request interface 505 and/or the enterprise client interface 530 can be networking modules that enables key service engine 500 to mediate data in a network with entities that are external to key service engine 500, through any known and/or convenient communications protocol supported by the host and the external entity. For example, the request interface 505 and/or the enterprise client interface 530 can be a network interface that can include one or more of a network adaptor card, a wireless network interface card (e.g., SMS interface, Win interface, interfaces for various generations of mobile communication standards including but not limited to 1G, 2G, 3G, 3.5G, 4G, LTE, etc.,), Bluetooth, a router, an access point, a wireless router, a switch, a multilayer switch, a protocol converter, a gateway, a bridge, bridge router, a hub, a digital media receiver, and/or a repeater.
As used herein, a “module,” “a manager,” a “handler,” a “detector,” an “interface,” or an “engine” includes a general purpose, dedicated or shared processor and, typically, firmware or software modules that are executed by the processor. Depending upon implementation-specific or other considerations, the module, manager, hander, or engine can be centralized or its functionality distributed. The module, manager, hander, or engine can include general or special purpose hardware, firmware, or software embodied in a computer-readable (storage) medium for execution by the processor. As used herein, a computer-readable medium or computer-readable storage medium is intended to include all mediums that are statutory (e.g., in the United States, under 35 U.S.C. 101), and to specifically exclude all mediums that are non-statutory in nature to the extent that the exclusion is necessary for a claim that includes the computer-readable (storage) medium to be valid. Known statutory computer-readable mediums include hardware (e.g., registers, random access memory (RAM), non-volatile (NV) storage, to name a few), but may or may not be limited to hardware.
One embodiment of the key service engine 500 includes the key service proxy 510 which can comprise any device configured to initiate a remote key request responsive to a determination that a data item indicated by a content request is associated with remote key management functionality.
One embodiment of the key service engine 500 includes the key encryption/decryption engine 515 which can provide a first layer of encryption and decryption for an encryption key. During upload requests, as described in
During access (or download) requests, as described in
One embodiment of the key service engine 500 includes the reason generation engine 520 which can process the content request to identify the reason associated with the content request and responsively generate the corresponding reason code.
One embodiment of the key service engine 500 includes the metadata engine 525 which can process the received content request to identify metadata associated with the content request. In one embodiment, the remote key request can include the metadata.
The remote key service engine 600 can be part of a web-based or online collaboration environment which can generally be a cloud-based service. The remote key service engine 600 can include, for example, a platform interface 605, a key encryption/decryption engine 610, a rule configuration engine 615, a rule processing engine 620, a kill switch 625, and a client configuration interface 630. Additional or fewer components/modules/engines can be included in the remote key service engine 600 and/or each illustrated component. Moreover, although illustrated as included as part of the remote key service engine 600, the components/modules/engines can be physically and/or functionally distributed. Furthermore, in some embodiments, the remote key service engine 600 can be a key service engine 500 with each having one or more of the same components.
The platform interface 605 can be configured to communicate with components of the cloud-based platform such as, tier example, the key service engine 500 of
The platform interface 605 and/or the client configuration interface 630 can be networking modules that enables the remote key service engine 600 to mediate data in a network with entities that are external to remote key service engine 600, through any known and/or convenient communications protocol supported by the host and the external entity. For example, the platform interface 605 and/or the client configuration interface 630 can be a network interface that can include one or more of a network adaptor card, a wireless network interface card (e.g., SMS interface, WiFi interface, interfaces for various generations of mobile communication standards including but not limited to 1G, 2G, 3G, 3.5G, 4G, LTE, etc.,), Bluetooth, a router, an access point, a wireless router, a switch, a multilayer switch, a protocol converter, a gateway, a bridge, bridge router, a hub, a digital media receiver, and/or a repeater.
As used herein, a “module,” “a manager,” a “handler,” a “detector,” an “interface,” or an “engine” includes a general purpose, dedicated or shared processor and, typically, firmware or software modules that are executed by the processor. Depending upon implementation-specific or other considerations, the module, manager, hander, or engine can be centralized or its functionality distributed. The module, manager, hander, or engine can include general or special purpose hardware, firmware, or software embodied in a computer-readable (storage) medium for execution by the processor. As used herein, a computer-readable medium or computer-readable storage medium is intended to include all mediums that are statutory (e.g., in the United States, under 35 U.S.C. 101), and to specifically exclude all mediums that are non-statutory in nature to the extent that the exclusion is necessary for a claim that includes the computer-readable (storage) medium to be valid. Known statutory computer-readable mediums include hardware (e.g., registers, random access memory (RAM), non-volatile (NV) storage, to name a few), but may or may not be limited to hardware.
One embodiment of the remote key service engine 600 includes the key encryption/decryption engine 610 which can provide a second layer of encryption and decryption for an encryption key at a remote client device. During remote encryption requests, as described in
One embodiment of the remote key service engine 600 includes the rule configuration engine 615 which can facilitate client configuration of rules. For example, rules can be generated to reject requests with particular reason codes, reject requests from particular IP addresses, reject particular users based on user ID, etc.
One embodiment of the remote key service engine 600 includes the rule processing engine 620 which can receive the remote key request including the encrypted encryption key, the generated reason code, and/or identified or generated metadata associated with the content request and processes the reason code and/or the metadata to determines whether to accept or reject the request based on one or more pre-configured rules. For example, rules can be generated to reject requests with particular reason codes, reject requests from particular IP addresses, reject particular users based on user ID, etc. The contents of an example remote key service engine 420 are shown and discussed in greater detail with reference to
One embodiment of the remote key service engine 600 includes a kill switch which can be set regardless of the pre-configured rules and reasons. Once set, the kill switch rejects the remote key requests regardless of the pre-configured rules and the reasons.
To begin, at process 710, the cloud-based platform receives a request for upload of a raw file (e.g., content or data item). The request for upload can be received from another machine internal to the collaborative cloud-based environment, a web application server, an external user (collaborator) machine, etc. In one embodiment, a content interface such as, for example, the content interface 412 of
At process 714, the cloud-based platform encrypts the encryption key using a local key encryption key (KEK). In one embodiment, a key service engine such as, for example, the key service engine 416 of
At decision process 716, the cloud-based platform determines if the content (upload) request and/or the particular content item is associated with remote key management functionality, in one embodiment, a key service engine such as, for example, the key service engine 416 of
If the content (upload) request and/or the particular content item is not associated with remote key management functionality then, at process 718, the cloud-based platform stores the encrypted content or data item and associated once encrypted encryption key and local KEK in a data store. However, if the content (upload) request and/or the particular content item is associated with remote key management functionality then, at process 720, the cloud-based platform identifies metadata associated with the content request and, at process 722, determines a reason code associated with the content request. In one embodiment, a key service engine such as, for example, the key service engine 416 of
In one embodiment, identifying the metadata associated with the content request includes identifying and/or otherwise determining ancillary information associated with the content request. For example, the metadata can include, but is not limited to, an Internet Protocol (IP) address initiating the request, a user identifier (ID) associated with the request, a file identifier (ID) associated with the request, etc. Other metadata is also possible.
In one embodiment, determining the reason code includes first identifying a reason for the content request and subsequently generating a code associated with the reason. By way of example and not limitation, reasons can include: to fulfill an upload data item request, to fulfill a download or access data item request, to fulfill a maintenance request, to perform another action (e.g., to perform a text extraction request), to fulfill backend services, etc. Other reasons are also possible. Each reason can be coded with reason code.
At process 724, the cloud-based platform initiates a remote key request to encrypt the encrypted encryption key. As discussed herein the remote key request includes the encrypted encryption key (also referred to as the once encrypted encryption key herein), identified or generated metadata associated with the content request, and the generated reason code. A key service engine such as, for example, the key service engine 416 of
At a decision process 726, a remote enterprise client system determines if the reason is ok. For example, a remote key service engine such as, for example, the remote key service engine 420 of
At process 732, the cloud-based platform receives a twice encrypted encryption key and a remote KEK and, at process 734, stores the encrypted file with the associated twice encrypted encryption key, the local KEK, and the remote KEK. Lastly, at process 736, the cloud-based platform optionally provides a confirmation response to the content item requestor. In one embodiment, the confirmation could occur at any time subsequent to the reception of the content request.
To begin, at process 810, the cloud-based platform receives an access request to download a file (e.g., content or data item). The request for access can be received from another machine internal to the collaborative cloud-based environment, a web application server, an external user (collaborator) machine, etc. In one embodiment, a content interface such as, for example, the content interface 412 of
At decision process 812, the cloud-based platform determines if the content (access) request and/or the particular content item is associated with remote key management functionality. In one embodiment, a key service engine such as, for example, the key service engine 416 of
If the content (access) request and/or the particular content item is not associated with remote key management functionality then the process continues at process 832 below. However, if the content (access) request and/or the particular content item is associated with remote key management functionality then, at process 814, the cloud-based platform identifies metadata associated with the content request and, at process 816, determines a reason code associated with the content request. In one embodiment, a key service engine such as, for example, the key service engine 416 of
In one embodiment, identifying the metadata associated with the content request includes identifying and/or otherwise determining ancillary information associated with the content request. For example, the metadata can include, but is not limited to, an Internet Protocol (IP) address initiating the request, a user identifier (ID) associated with the request, a file identifier (ID) associated with the request, etc. Other metadata is also possible.
In one embodiment, determining the reason code includes first identifying a reason for the content request and subsequently generating a code associated with the reason. By way of example and not limitation, reasons can include: to fulfill an upload data item request, to fulfill a download or access data item request, to fulfill a maintenance request, to perform another action (e.g., to perform a text extraction request), to fulfill backend services, etc. Other reasons are also possible. Each reason can be coded with reason code.
At process 822, the cloud-based platform accesses a twice encrypted encryption key, a local KEK, and a remote KEK from a data store. At process 824, the cloud-based platform initiates a remote key request to decrypt the encrypted encryption key. As discussed herein the remote key request includes the twice encrypted encryption key, identified or generated metadata associated with the content request, the generated reason code, and the remote KEK. A key service engine such as, for example, the key service engine 416 of
At a decision process 824, a remote enterprise client system determines if the reason is ok. For example, a remote key service engine such as, for example, the remote key service engine 420 of
At process 830, the cloud-based platform receives a once encrypted encryption key and, at process 832, accesses the encrypted data item associated with the content request from the data store. In various embodiments, the cloud-based platform can also access a local KEK from the data store if the local KEK was not previously accessed at process 818.
At process 834, the cloud-based platform decrypts the encrypted data encryption key using the local KEK.
At process 836, the cloud-based platform decrypts the encrypted data item using the unencrypted encryption key. Lastly, the cloud-based platform provides the decrypted file content item requestor responsive to the content request.
In alternative embodiments, the machine operates as a standalone device or may be connected (e.g., networked) to other machines. In a networked deployment, the machine may operate in the capacity of a server or a client machine in a client-server network environment, or as a peer machine in a peer-to-peer (or distributed) network environment.
The machine may be a server computer, a client computer, a personal computer (PC), a user device, a tablet PC, a laptop computer, a set-top box (STB), a personal digital assistant (PDA), a cellular telephone, an iPhone, an iPad, a Blackberry, a processor, a telephone, a web appliance, a network router, switch or bridge, a console, a hand-held console, a (hand-held) gaming device, a music player, any portable, mobile, hand-held device, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine.
While the machine-readable medium or machine-readable storage medium is shown in an exemplary embodiment to be a single medium, the term “machine-readable medium” and “machine-readable storage medium” should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of instructions. The term “machine-readable medium” and “machine-readable storage medium” shall also be taken to include any medium that is capable of storing, encoding or carrying a set of instructions for execution by the machine and that cause the machine to perform any one or more of the methodologies of the presently disclosed technique and innovation.
In general, the routines executed to implement the embodiments of the disclosure, may be implemented as part of an operating system or a specific application, component, program, object, module or sequence of instructions referred to as “computer programs.” The computer programs typically comprise one or more instructions set at various times in various memory and storage devices in a computer, and that, when read and executed by one or more processing units or processors in a computer, cause the computer to perform operations to execute elements involving the various aspects of the disclosure.
Moreover, while embodiments have been described in the context of fully functioning computers and computer systems, those skilled in the art will appreciate that the various embodiments are capable of being distributed as a program product in a variety of forms, and that the disclosure applies equally regardless of the particular type of machine or computer-readable media used to actually effect the distribution.
Further examples of machine-readable storage media, machine-readable media, or computer-readable (storage) media include, but are not limited to, recordable type media such as volatile and non-volatile memory devices, floppy and other removable disks, hard disks, optical disks (e.g., Compact Disk Read-Only Memory (CD ROMS), Digital Versatile Disks, (DVDs), etc.), among others, and transmission type media such as digital and analog communication links.
The network interface device enables the machine 700 to mediate data in a network with an entity that is external to the host server, through any known and/or convenient communications protocol supported by the host and the external entity. The network interface device can include one or more of a network adaptor card, a wireless network interface card, a router, an access point, a wireless router, a switch, a multilayer switch, a protocol converter, a gateway, a bridge, bridge router, a hub, a digital media receiver, and/or a repeater.
The network interface device can include a firewall which can, in some embodiments, govern and/or manage permission to access/proxy data in a computer network, and track varying levels of trust between different machines and/or applications. The firewall can be any number of modules having any combination of hardware and/or software components able to enforce a predetermined set of access rights between a particular set of machines and applications, machines and machines, and/or applications and applications, for example, to regulate the flow of traffic and resource sharing between these varying entities. The firewall may additionally manage and/or have access to an access control list which details permissions including for example, the access and operation rights of an Object by an individual, a machine, and/or an application, and the circumstances under which the permission rights stand.
Other network security functions can be performed or included in the functions of the firewall, can be, for example, but are not limited to, intrusion-prevention, intrusion detection, next-generation firewall, personal firewall, etc. without deviating from the novel art of this disclosure.
Unless the context clearly requires otherwise, throughout the description and the claims, the words “comprise,” “comprising,” and the like are to be construed in an inclusive sense, as opposed to an exclusive or exhaustive sense; that is to say, in the sense of “including, but not limited to.” As used herein, the terms “connected,” “coupled,” or any variant thereof, means any connection or coupling, either direct or indirect, between two or more elements; the coupling of connection between the elements can be physical, logical, or a combination thereof. Additionally, the words “herein,” “above,” “below,” and words of similar import, when used in this application, shall refer to this application as a whole and not to any particular portions of this application. Where the context permits, words in the above Detailed Description using the singular or plural number may also include the plural or singular number respectively. The word “or,” in reference to a list of two or more items, covers all of the following interpretations of the word: any of the items in the list, all of the items in the list, and any combination of the items in the list.
The above detailed description of embodiments of the disclosure is not intended to be exhaustive or to limit the teachings to the precise form disclosed above. While specific embodiments of, and examples for, the disclosure are described above for illustrative purposes, various equivalent modifications are possible within the scope of the disclosure, as those skilled in the relevant art will recognize. For example, while processes or blocks are presented in a given order, alternative embodiments may perform routines having steps, or employ systems having blocks, in a different order, and some processes or blocks may be deleted, moved, added, subdivided, combined, and/or modified to provide alternative or subcombinations. Each of these processes or blocks may be implemented in a variety of different ways. Also, while processes or blocks are at times shown as being performed in series, these processes or blocks may instead be performed in parallel, or may be performed at different times. Further, any specific numbers noted herein are only examples: alternative implementations may employ differing values or ranges.
The teachings of the disclosure provided herein can be applied to other systems, not necessarily the system described above. The elements and acts of the various embodiments described above can be combined to provide further embodiments.
Any patents and applications and other references noted above, including any that may be listed in accompanying filing papers, are incorporated herein by reference. Aspects of the disclosure can be modified, if necessary, to employ the systems, functions, and concepts of the various references described above to provide yet further embodiments of the disclosure.
These and other changes can be made to the disclosure in light of the above Detailed Description. While the above description describes certain embodiments of the disclosure, and describes the best mode contemplated, no matter how detailed the above appears in text, the teachings can be practiced in many ways. Details of the system may vary considerably in its implementation details, while still being encompassed by the subject matter disclosed herein. As noted above, particular terminology used when describing certain features or aspects of the disclosure should not be taken to imply that the terminology is being redefined herein to be restricted to any specific characteristics, features, or aspects of the disclosure with which that terminology is associated. In general, the terms used in the following claims should not be construed to limit the disclosure to the specific embodiments disclosed in the specification, unless the above Detailed Description section explicitly defines such terms. Accordingly, the actual scope of the disclosure encompasses not only the disclosed embodiments, but also all equivalent ways of practicing or implementing the disclosure under the claims.
While certain aspects of the disclosure are presented below in certain claim forms, the inventors contemplate the various aspects of the disclosure in any number of claim forms. For example, while only one aspect of the disclosure is recited as a means-plus-function claim under 35 U.S.C. §112, ¶6, other aspects may likewise be embodied as a means-plus-function claim, or in other forms, such as being embodied in a computer-readable medium. (Any claims intended to be treated under 35 U.S.C. §112, ¶6 will begin with the words “means for”.) Accordingly, the applicant reserves the right to add additional claims after filing the application to pursue such additional claim forms for other aspects of the disclosure.
The present application claims priority to and benefit from U.S. Provisional Patent Application Ser. No. 61/715,208 titled “ADAPTIVE ARCHITECTURES FOR ENCRYPTION KEY MANAGEMENT IN A CLOUD-BASED ENVIRONMENT”, filed on Oct. 17, 2012, the content of which is incorporated by reference herein.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5787803 | Ohmura et al. | Aug 1998 | A |
| 5799320 | Klug | Aug 1998 | A |
| 5848415 | Guck | Dec 1998 | A |
| 5864870 | Guck | Jan 1999 | A |
| 5999908 | Abelow | Dec 1999 | A |
| 6016467 | Newsted et al. | Jan 2000 | A |
| 6034621 | Kaufman | Mar 2000 | A |
| 6055543 | Christensen et al. | Apr 2000 | A |
| 6073161 | DeBoskey et al. | Jun 2000 | A |
| 6098078 | Gehani et al. | Aug 2000 | A |
| 6233600 | Salas et al. | May 2001 | B1 |
| 6260040 | Kauffman et al. | Jul 2001 | B1 |
| 6289345 | Yasue | Sep 2001 | B1 |
| 6292803 | Richardson et al. | Sep 2001 | B1 |
| 6336124 | Alam et al. | Jan 2002 | B1 |
| 6342906 | Kumar et al. | Jan 2002 | B1 |
| 6345386 | Delo et al. | Feb 2002 | B1 |
| 6370543 | Hoffert et al. | Apr 2002 | B2 |
| 6374260 | Hoffert et al. | Apr 2002 | B1 |
| 6385606 | Inohara et al. | May 2002 | B2 |
| 6396593 | Laverty et al. | May 2002 | B1 |
| 6515681 | Knight | Feb 2003 | B1 |
| 6539381 | Prasad et al. | Mar 2003 | B1 |
| 6549626 | Al-Salqan | Apr 2003 | B1 |
| 6584466 | Serbinis et al. | Jun 2003 | B1 |
| 6636872 | Heath et al. | Oct 2003 | B1 |
| 6654737 | Nunez | Nov 2003 | B1 |
| 6662186 | Esquibel et al. | Dec 2003 | B1 |
| 6687878 | Eintracht et al. | Feb 2004 | B1 |
| 6714968 | Prust | Mar 2004 | B1 |
| 6735623 | Prust | May 2004 | B1 |
| 6742181 | Koike et al. | May 2004 | B1 |
| 6760721 | Chasen et al. | Jul 2004 | B1 |
| 6947162 | Rosenberg et al. | Sep 2005 | B2 |
| 6952724 | Prust | Oct 2005 | B2 |
| 6996768 | Elo et al. | Feb 2006 | B1 |
| 7010752 | Ly | Mar 2006 | B2 |
| 7020697 | Goodman et al. | Mar 2006 | B1 |
| 7039806 | Friedman et al. | May 2006 | B1 |
| 7069393 | Miyata et al. | Jun 2006 | B2 |
| 7130831 | Howard et al. | Oct 2006 | B2 |
| 7133834 | Abelow | Nov 2006 | B1 |
| 7149787 | Mutalik et al. | Dec 2006 | B1 |
| 7152182 | Ji et al. | Dec 2006 | B2 |
| 7155483 | Friend et al. | Dec 2006 | B1 |
| 7165107 | Pouyoul et al. | Jan 2007 | B2 |
| 7222078 | Abelow | May 2007 | B2 |
| 7275244 | Charles Bell et al. | Sep 2007 | B1 |
| 7296025 | Kung et al. | Nov 2007 | B2 |
| 7346778 | Guiter et al. | Mar 2008 | B1 |
| 7353252 | Yang et al. | Apr 2008 | B1 |
| 7370269 | Prabhu et al. | May 2008 | B1 |
| 7386535 | Kalucha et al. | Jun 2008 | B1 |
| 7401117 | Dan et al. | Jul 2008 | B2 |
| 7543000 | Castro et al. | Jun 2009 | B2 |
| 7581221 | Lai et al. | Aug 2009 | B2 |
| 7620565 | Abelow | Nov 2009 | B2 |
| 7647559 | Yozell-Epstein et al. | Jan 2010 | B2 |
| 7650367 | Arruza | Jan 2010 | B2 |
| 7661088 | Burke | Feb 2010 | B2 |
| 7665093 | Maybee et al. | Feb 2010 | B2 |
| 7676542 | Moser et al. | Mar 2010 | B2 |
| 7698363 | Dan et al. | Apr 2010 | B2 |
| 7734600 | Wise et al. | Jun 2010 | B1 |
| 7756843 | Palmer | Jul 2010 | B1 |
| 7774412 | Schnepel | Aug 2010 | B1 |
| 7814426 | Huesken et al. | Oct 2010 | B2 |
| 7886287 | Davda | Feb 2011 | B1 |
| 7890964 | Vogler-Ivashchanka et al. | Feb 2011 | B2 |
| 7937663 | Parker et al. | May 2011 | B2 |
| 7958453 | Taing | Jun 2011 | B1 |
| 7979296 | Kruse et al. | Jul 2011 | B2 |
| 7996374 | Jones et al. | Aug 2011 | B1 |
| 8027976 | Ding et al. | Sep 2011 | B1 |
| RE42904 | Stephens, Jr. | Nov 2011 | E |
| 8065739 | Bruening et al. | Nov 2011 | B1 |
| 8090361 | Hagan | Jan 2012 | B2 |
| 8103662 | Eagan et al. | Jan 2012 | B2 |
| 8117261 | Briere et al. | Feb 2012 | B2 |
| 8140513 | Ghods et al. | Mar 2012 | B2 |
| 8151183 | Chen et al. | Apr 2012 | B2 |
| 8179445 | Hao | May 2012 | B2 |
| 8185830 | Saha et al. | May 2012 | B2 |
| 8214747 | Yankovich et al. | Jul 2012 | B1 |
| 8230348 | Peters et al. | Jul 2012 | B2 |
| 8326814 | Ghods et al. | Dec 2012 | B2 |
| 8347276 | Schadow | Jan 2013 | B2 |
| 8358701 | Chou et al. | Jan 2013 | B2 |
| 8370803 | Holler et al. | Feb 2013 | B1 |
| 8429540 | Yankovich et al. | Apr 2013 | B1 |
| 8464161 | Giles et al. | Jun 2013 | B2 |
| 8515902 | Savage | Aug 2013 | B2 |
| 8527549 | Cidon | Sep 2013 | B2 |
| 8549066 | Donahue et al. | Oct 2013 | B1 |
| 8549511 | Seki et al. | Oct 2013 | B2 |
| 8583619 | Ghods et al. | Nov 2013 | B2 |
| 8607306 | Bridge et al. | Dec 2013 | B1 |
| 8719445 | Ko | May 2014 | B2 |
| 8745267 | Luecke et al. | Jun 2014 | B2 |
| 8849955 | Prahlad et al. | Sep 2014 | B2 |
| 8868574 | Kiang et al. | Oct 2014 | B2 |
| 8892679 | Destagnol et al. | Nov 2014 | B1 |
| 8914900 | Smith et al. | Dec 2014 | B2 |
| 20010027492 | Gupta | Oct 2001 | A1 |
| 20020029218 | Bentley et al. | Mar 2002 | A1 |
| 20020091738 | Rohrabaugh et al. | Jul 2002 | A1 |
| 20020099772 | Deshpande et al. | Jul 2002 | A1 |
| 20020133509 | Johnston et al. | Sep 2002 | A1 |
| 20020147770 | Tang | Oct 2002 | A1 |
| 20020194177 | Sherman et al. | Dec 2002 | A1 |
| 20030041095 | Konda et al. | Feb 2003 | A1 |
| 20030084306 | Abburi et al. | May 2003 | A1 |
| 20030093404 | Bader et al. | May 2003 | A1 |
| 20030108052 | Inoue et al. | Jun 2003 | A1 |
| 20030110264 | Whidby et al. | Jun 2003 | A1 |
| 20030115326 | Verma et al. | Jun 2003 | A1 |
| 20030135536 | Lyons | Jul 2003 | A1 |
| 20030135565 | Estrada | Jul 2003 | A1 |
| 20030154306 | Perry | Aug 2003 | A1 |
| 20030204490 | Kasriel | Oct 2003 | A1 |
| 20030217171 | Von Stuermer et al. | Nov 2003 | A1 |
| 20040021686 | Barberis | Feb 2004 | A1 |
| 20040088647 | Miller et al. | May 2004 | A1 |
| 20040103147 | Flesher et al. | May 2004 | A1 |
| 20040111415 | Scardino et al. | Jun 2004 | A1 |
| 20040117438 | Considine et al. | Jun 2004 | A1 |
| 20040122949 | Zmudzinski et al. | Jun 2004 | A1 |
| 20040128359 | Horvitz et al. | Jul 2004 | A1 |
| 20040177138 | Salle et al. | Sep 2004 | A1 |
| 20040181579 | Huck et al. | Sep 2004 | A1 |
| 20040196307 | Zak et al. | Oct 2004 | A1 |
| 20040201604 | Kraenzel et al. | Oct 2004 | A1 |
| 20040230624 | Frolund et al. | Nov 2004 | A1 |
| 20040246532 | Inada | Dec 2004 | A1 |
| 20040267836 | Armangau et al. | Dec 2004 | A1 |
| 20050005276 | Morgan | Jan 2005 | A1 |
| 20050010860 | Weiss et al. | Jan 2005 | A1 |
| 20050022229 | Gabriel et al. | Jan 2005 | A1 |
| 20050028006 | Leser | Feb 2005 | A1 |
| 20050050228 | Perham et al. | Mar 2005 | A1 |
| 20050063083 | Dart et al. | Mar 2005 | A1 |
| 20050097225 | Glatt et al. | May 2005 | A1 |
| 20050102328 | Ring et al. | May 2005 | A1 |
| 20050108406 | Lee et al. | May 2005 | A1 |
| 20050114205 | Nelson et al. | May 2005 | A1 |
| 20050114305 | Haynes et al. | May 2005 | A1 |
| 20050114378 | Elien et al. | May 2005 | A1 |
| 20050138118 | Banatwala et al. | Jun 2005 | A1 |
| 20050182966 | Pham et al. | Aug 2005 | A1 |
| 20050198299 | Beck et al. | Sep 2005 | A1 |
| 20050198452 | Watanabe | Sep 2005 | A1 |
| 20050234864 | Shapiro | Oct 2005 | A1 |
| 20050234943 | Clarke | Oct 2005 | A1 |
| 20050261933 | Magnuson | Nov 2005 | A1 |
| 20060005163 | Huesken et al. | Jan 2006 | A1 |
| 20060026502 | Dutta | Feb 2006 | A1 |
| 20060026535 | Hotelling et al. | Feb 2006 | A1 |
| 20060036568 | Moore et al. | Feb 2006 | A1 |
| 20060041603 | Paterson et al. | Feb 2006 | A1 |
| 20060047804 | Fredricksen et al. | Mar 2006 | A1 |
| 20060053088 | Ali et al. | Mar 2006 | A1 |
| 20060053380 | Spataro et al. | Mar 2006 | A1 |
| 20060066902 | Matsui et al. | Mar 2006 | A1 |
| 20060070083 | Brunswig et al. | Mar 2006 | A1 |
| 20060075071 | Gillette | Apr 2006 | A1 |
| 20060117247 | Fite et al. | Jun 2006 | A1 |
| 20060123062 | Bobbitt et al. | Jun 2006 | A1 |
| 20060133340 | Rybak et al. | Jun 2006 | A1 |
| 20060168550 | Muller et al. | Jul 2006 | A1 |
| 20060174051 | Lordi et al. | Aug 2006 | A1 |
| 20060174054 | Matsuki | Aug 2006 | A1 |
| 20060179070 | George et al. | Aug 2006 | A1 |
| 20060242204 | Karas et al. | Oct 2006 | A1 |
| 20060259524 | Horton | Nov 2006 | A1 |
| 20060265719 | Astl et al. | Nov 2006 | A1 |
| 20060271510 | Harward et al. | Nov 2006 | A1 |
| 20070016680 | Burd et al. | Jan 2007 | A1 |
| 20070038934 | Fellman | Feb 2007 | A1 |
| 20070079242 | Jolley et al. | Apr 2007 | A1 |
| 20070100830 | Beedubail et al. | May 2007 | A1 |
| 20070115845 | Hochwarth et al. | May 2007 | A1 |
| 20070118598 | Bedi et al. | May 2007 | A1 |
| 20070124460 | McMullen et al. | May 2007 | A1 |
| 20070124737 | Wensley et al. | May 2007 | A1 |
| 20070124781 | Casey et al. | May 2007 | A1 |
| 20070126635 | Houri | Jun 2007 | A1 |
| 20070130143 | Zhang et al. | Jun 2007 | A1 |
| 20070130163 | Perez et al. | Jun 2007 | A1 |
| 20070198609 | Black et al. | Aug 2007 | A1 |
| 20070208878 | Barnes-Leon et al. | Sep 2007 | A1 |
| 20070214180 | Crawford | Sep 2007 | A1 |
| 20070220016 | Estrada et al. | Sep 2007 | A1 |
| 20070220590 | Rasmussen et al. | Sep 2007 | A1 |
| 20070240057 | Satterfield et al. | Oct 2007 | A1 |
| 20070250762 | Mansfield | Oct 2007 | A1 |
| 20070256065 | Heishi et al. | Nov 2007 | A1 |
| 20070266304 | Fletcher et al. | Nov 2007 | A1 |
| 20070282848 | Kiilerich et al. | Dec 2007 | A1 |
| 20070283443 | McPherson et al. | Dec 2007 | A1 |
| 20070288290 | Motoyama et al. | Dec 2007 | A1 |
| 20080005135 | Muthukrishnan et al. | Jan 2008 | A1 |
| 20080005195 | Li | Jan 2008 | A1 |
| 20080016146 | Gan et al. | Jan 2008 | A1 |
| 20080021959 | Naghi et al. | Jan 2008 | A1 |
| 20080028323 | Rosen et al. | Jan 2008 | A1 |
| 20080040173 | Aleong et al. | Feb 2008 | A1 |
| 20080040503 | Kleks et al. | Feb 2008 | A1 |
| 20080046828 | Bibliowicz et al. | Feb 2008 | A1 |
| 20080049942 | Sprunk et al. | Feb 2008 | A1 |
| 20080059656 | Saliba et al. | Mar 2008 | A1 |
| 20080063210 | Goodman et al. | Mar 2008 | A1 |
| 20080065881 | Dawson et al. | Mar 2008 | A1 |
| 20080077631 | Petri | Mar 2008 | A1 |
| 20080091763 | Devonshire et al. | Apr 2008 | A1 |
| 20080091790 | Beck | Apr 2008 | A1 |
| 20080104277 | Tian | May 2008 | A1 |
| 20080114720 | Smith et al. | May 2008 | A1 |
| 20080133674 | Knauerhase et al. | Jun 2008 | A1 |
| 20080140732 | Wilson et al. | Jun 2008 | A1 |
| 20080147790 | Malaney et al. | Jun 2008 | A1 |
| 20080151817 | Fitchett et al. | Jun 2008 | A1 |
| 20080154873 | Redlich et al. | Jun 2008 | A1 |
| 20080182628 | Lee et al. | Jul 2008 | A1 |
| 20080183467 | Yuan et al. | Jul 2008 | A1 |
| 20080184130 | Tien et al. | Jul 2008 | A1 |
| 20080194239 | Hagan | Aug 2008 | A1 |
| 20080215883 | Fok et al. | Sep 2008 | A1 |
| 20080222654 | Xu et al. | Sep 2008 | A1 |
| 20080243855 | Prahlad et al. | Oct 2008 | A1 |
| 20080250333 | Reeves et al. | Oct 2008 | A1 |
| 20080250348 | Alimpich et al. | Oct 2008 | A1 |
| 20080263099 | Brady-Kalnay et al. | Oct 2008 | A1 |
| 20080271095 | Shafton | Oct 2008 | A1 |
| 20080276158 | Lim et al. | Nov 2008 | A1 |
| 20080279533 | Buttars | Nov 2008 | A1 |
| 20080294899 | Gazzetta et al. | Nov 2008 | A1 |
| 20090015864 | Hasegawa | Jan 2009 | A1 |
| 20090019093 | Brodersen et al. | Jan 2009 | A1 |
| 20090019426 | Baeumer et al. | Jan 2009 | A1 |
| 20090030710 | Levine | Jan 2009 | A1 |
| 20090044128 | Baumgarten et al. | Feb 2009 | A1 |
| 20090049131 | Lyle et al. | Feb 2009 | A1 |
| 20090119322 | Mills et al. | May 2009 | A1 |
| 20090125469 | McDonald et al. | May 2009 | A1 |
| 20090132651 | Roger et al. | May 2009 | A1 |
| 20090138808 | Moromisato et al. | May 2009 | A1 |
| 20090150417 | Ghods et al. | Jun 2009 | A1 |
| 20090150627 | Benhase et al. | Jun 2009 | A1 |
| 20090158142 | Arthursson et al. | Jun 2009 | A1 |
| 20090164438 | Delacruz | Jun 2009 | A1 |
| 20090171983 | Samji et al. | Jul 2009 | A1 |
| 20090193107 | Srinivasan et al. | Jul 2009 | A1 |
| 20090193345 | Wensley et al. | Jul 2009 | A1 |
| 20090198772 | Kim et al. | Aug 2009 | A1 |
| 20090210459 | Nair et al. | Aug 2009 | A1 |
| 20090214115 | Kimura et al. | Aug 2009 | A1 |
| 20090235167 | Boyer et al. | Sep 2009 | A1 |
| 20090235181 | Saliba et al. | Sep 2009 | A1 |
| 20090235189 | Aybes et al. | Sep 2009 | A1 |
| 20090249224 | Davis et al. | Oct 2009 | A1 |
| 20090254589 | Nair et al. | Oct 2009 | A1 |
| 20090260060 | Smith et al. | Oct 2009 | A1 |
| 20090265430 | Bechtel et al. | Oct 2009 | A1 |
| 20090271708 | Peters et al. | Oct 2009 | A1 |
| 20090276771 | Nickolov et al. | Nov 2009 | A1 |
| 20090282212 | Peterson | Nov 2009 | A1 |
| 20090300356 | Crandell | Dec 2009 | A1 |
| 20090300527 | Malcolm et al. | Dec 2009 | A1 |
| 20090327358 | Lukiyanov et al. | Dec 2009 | A1 |
| 20090327961 | De Vorchik et al. | Dec 2009 | A1 |
| 20100011292 | Marinkovich et al. | Jan 2010 | A1 |
| 20100011447 | Jothimani | Jan 2010 | A1 |
| 20100017262 | Iyer et al. | Jan 2010 | A1 |
| 20100023776 | Fedronic et al. | Jan 2010 | A1 |
| 20100036929 | Scherpa et al. | Feb 2010 | A1 |
| 20100042720 | Stienhans et al. | Feb 2010 | A1 |
| 20100057560 | Skudlark et al. | Mar 2010 | A1 |
| 20100057785 | Khosravy et al. | Mar 2010 | A1 |
| 20100070769 | Shima et al. | Mar 2010 | A1 |
| 20100076946 | Barker et al. | Mar 2010 | A1 |
| 20100082634 | Leban | Apr 2010 | A1 |
| 20100083136 | Komine et al. | Apr 2010 | A1 |
| 20100088150 | Mazhar et al. | Apr 2010 | A1 |
| 20100092126 | Kaliszek et al. | Apr 2010 | A1 |
| 20100093310 | Gbadegesin et al. | Apr 2010 | A1 |
| 20100107225 | Spencer et al. | Apr 2010 | A1 |
| 20100131868 | Chawla et al. | May 2010 | A1 |
| 20100151431 | Miller | Jun 2010 | A1 |
| 20100153835 | Xiong et al. | Jun 2010 | A1 |
| 20100162365 | Del Real | Jun 2010 | A1 |
| 20100162374 | Nair | Jun 2010 | A1 |
| 20100179940 | Gilder et al. | Jul 2010 | A1 |
| 20100185463 | Noland et al. | Jul 2010 | A1 |
| 20100185932 | Coffman et al. | Jul 2010 | A1 |
| 20100191689 | Cortes et al. | Jul 2010 | A1 |
| 20100198783 | Wang et al. | Aug 2010 | A1 |
| 20100198871 | Stiegler et al. | Aug 2010 | A1 |
| 20100198944 | Ho et al. | Aug 2010 | A1 |
| 20100205537 | Knighton et al. | Aug 2010 | A1 |
| 20100218237 | Ferris et al. | Aug 2010 | A1 |
| 20100223378 | Wei | Sep 2010 | A1 |
| 20100229085 | Nelson et al. | Sep 2010 | A1 |
| 20100235526 | Carter et al. | Sep 2010 | A1 |
| 20100235539 | Carter et al. | Sep 2010 | A1 |
| 20100241611 | Zuber | Sep 2010 | A1 |
| 20100241972 | Spataro et al. | Sep 2010 | A1 |
| 20100250120 | Waupotitsch et al. | Sep 2010 | A1 |
| 20100251340 | Martin et al. | Sep 2010 | A1 |
| 20100257457 | De Goes | Oct 2010 | A1 |
| 20100262582 | Garcia-Ascanio et al. | Oct 2010 | A1 |
| 20100267588 | Nelson et al. | Oct 2010 | A1 |
| 20100274765 | Murphy et al. | Oct 2010 | A1 |
| 20100274772 | Samuels | Oct 2010 | A1 |
| 20100281118 | Donahue et al. | Nov 2010 | A1 |
| 20100290623 | Banks | Nov 2010 | A1 |
| 20100306379 | Ferris | Dec 2010 | A1 |
| 20100322252 | Suganthi et al. | Dec 2010 | A1 |
| 20100325155 | Skinner et al. | Dec 2010 | A1 |
| 20100325527 | Estrada et al. | Dec 2010 | A1 |
| 20100325559 | Westerinen et al. | Dec 2010 | A1 |
| 20100325655 | Perez | Dec 2010 | A1 |
| 20100332401 | Prahlad et al. | Dec 2010 | A1 |
| 20100332962 | Hammer et al. | Dec 2010 | A1 |
| 20100333116 | Prahlad et al. | Dec 2010 | A1 |
| 20101318893 | Matthews et al. | Dec 2010 | |
| 20110001763 | Murakami | Jan 2011 | A1 |
| 20110016409 | Grosz et al. | Jan 2011 | A1 |
| 20110022559 | Andersen et al. | Jan 2011 | A1 |
| 20110022812 | van der Linden et al. | Jan 2011 | A1 |
| 20110029883 | Lussier et al. | Feb 2011 | A1 |
| 20110040812 | Phillips | Feb 2011 | A1 |
| 20110041083 | Gabai et al. | Feb 2011 | A1 |
| 20110047413 | McGill et al. | Feb 2011 | A1 |
| 20110047484 | Mount et al. | Feb 2011 | A1 |
| 20110052155 | Desmarais et al. | Mar 2011 | A1 |
| 20110054968 | Galaviz | Mar 2011 | A1 |
| 20110055299 | Phillips | Mar 2011 | A1 |
| 20110055721 | Jain et al. | Mar 2011 | A1 |
| 20110061045 | Phillips | Mar 2011 | A1 |
| 20110061046 | Phillips | Mar 2011 | A1 |
| 20110065082 | Gal et al. | Mar 2011 | A1 |
| 20110066951 | Ward-Karet et al. | Mar 2011 | A1 |
| 20110083167 | Carpenter et al. | Apr 2011 | A1 |
| 20110093567 | Jeon et al. | Apr 2011 | A1 |
| 20110099006 | Sundararaman et al. | Apr 2011 | A1 |
| 20110107205 | Chow et al. | May 2011 | A1 |
| 20110113320 | Neff et al. | May 2011 | A1 |
| 20110119313 | Sung et al. | May 2011 | A1 |
| 20110137991 | Russell | Jun 2011 | A1 |
| 20110142410 | Ishii | Jun 2011 | A1 |
| 20110161289 | Pei et al. | Jun 2011 | A1 |
| 20110167125 | Achlioptas | Jul 2011 | A1 |
| 20110167353 | Grosz et al. | Jul 2011 | A1 |
| 20110167435 | Fang | Jul 2011 | A1 |
| 20110185292 | Chawla et al. | Jul 2011 | A1 |
| 20110202424 | Chun et al. | Aug 2011 | A1 |
| 20110202599 | Yuan et al. | Aug 2011 | A1 |
| 20110208958 | Stuedi et al. | Aug 2011 | A1 |
| 20110209064 | Jorgensen et al. | Aug 2011 | A1 |
| 20110213765 | Cui et al. | Sep 2011 | A1 |
| 20110219419 | Reisman | Sep 2011 | A1 |
| 20110225417 | Maharajh et al. | Sep 2011 | A1 |
| 20110238458 | Purcell et al. | Sep 2011 | A1 |
| 20110238621 | Agrawal | Sep 2011 | A1 |
| 20110238759 | Spataro et al. | Sep 2011 | A1 |
| 20110239135 | Spataro et al. | Sep 2011 | A1 |
| 20110246294 | Robb et al. | Oct 2011 | A1 |
| 20110246950 | Luna et al. | Oct 2011 | A1 |
| 20110252071 | Cidon | Oct 2011 | A1 |
| 20110252320 | Arrasvuori et al. | Oct 2011 | A1 |
| 20110252339 | Lemonik et al. | Oct 2011 | A1 |
| 20110258461 | Bates | Oct 2011 | A1 |
| 20110258561 | Ladouceur et al. | Oct 2011 | A1 |
| 20110282710 | Akkiraju et al. | Nov 2011 | A1 |
| 20110289433 | Whalin et al. | Nov 2011 | A1 |
| 20110296022 | Ferris et al. | Dec 2011 | A1 |
| 20110313803 | Friend et al. | Dec 2011 | A1 |
| 20110320197 | Conejero et al. | Dec 2011 | A1 |
| 20120036370 | Lim et al. | Feb 2012 | A1 |
| 20120064879 | Panei | Mar 2012 | A1 |
| 20120072436 | Pierre et al. | Mar 2012 | A1 |
| 20120079095 | Evans et al. | Mar 2012 | A1 |
| 20120089659 | Halevi et al. | Apr 2012 | A1 |
| 20120110005 | Kuo et al. | May 2012 | A1 |
| 20120110436 | Adler, III et al. | May 2012 | A1 |
| 20120110443 | Lemonik et al. | May 2012 | A1 |
| 20120117626 | Yates et al. | May 2012 | A1 |
| 20120124306 | Abercrombie et al. | May 2012 | A1 |
| 20120124547 | Halbedel | May 2012 | A1 |
| 20120130900 | Tang et al. | May 2012 | A1 |
| 20120134491 | Liu | May 2012 | A1 |
| 20120136936 | Quintuna | May 2012 | A1 |
| 20120144283 | Hill et al. | Jun 2012 | A1 |
| 20120150888 | Hyatt et al. | Jun 2012 | A1 |
| 20120151551 | Readshaw et al. | Jun 2012 | A1 |
| 20120158908 | Luna et al. | Jun 2012 | A1 |
| 20120159178 | Lin et al. | Jun 2012 | A1 |
| 20120159310 | Chang et al. | Jun 2012 | A1 |
| 20120173625 | Berger | Jul 2012 | A1 |
| 20120179909 | Sagi et al. | Jul 2012 | A1 |
| 20120179981 | Whalin et al. | Jul 2012 | A1 |
| 20120185355 | Kilroy | Jul 2012 | A1 |
| 20120185913 | Martinez et al. | Jul 2012 | A1 |
| 20120192055 | Antebi et al. | Jul 2012 | A1 |
| 20120192086 | Ghods et al. | Jul 2012 | A1 |
| 20120203908 | Beaty et al. | Aug 2012 | A1 |
| 20120204032 | Wilkins et al. | Aug 2012 | A1 |
| 20120214444 | McBride et al. | Aug 2012 | A1 |
| 20120218885 | Abel et al. | Aug 2012 | A1 |
| 20120221789 | Felter | Aug 2012 | A1 |
| 20120226767 | Luna et al. | Sep 2012 | A1 |
| 20120233155 | Gallmeier et al. | Sep 2012 | A1 |
| 20120233205 | McDermott | Sep 2012 | A1 |
| 20120233543 | Vagell et al. | Sep 2012 | A1 |
| 20120240061 | Hillenius et al. | Sep 2012 | A1 |
| 20120257249 | Natarajan | Oct 2012 | A1 |
| 20120263166 | Cho et al. | Oct 2012 | A1 |
| 20120266203 | Elhadad et al. | Oct 2012 | A1 |
| 20120284638 | Cutler et al. | Nov 2012 | A1 |
| 20120284664 | Zhao | Nov 2012 | A1 |
| 20120291011 | Quine | Nov 2012 | A1 |
| 20120296790 | Robb | Nov 2012 | A1 |
| 20120309540 | Holme et al. | Dec 2012 | A1 |
| 20120311157 | Erickson et al. | Dec 2012 | A1 |
| 20120317239 | Mulder et al. | Dec 2012 | A1 |
| 20120317487 | Lieb et al. | Dec 2012 | A1 |
| 20120328259 | Seibert, Jr. et al. | Dec 2012 | A1 |
| 20120331177 | Jensen | Dec 2012 | A1 |
| 20120331441 | Adamson | Dec 2012 | A1 |
| 20130007245 | Malik et al. | Jan 2013 | A1 |
| 20130007450 | Janyavula et al. | Jan 2013 | A1 |
| 20130007471 | Grab et al. | Jan 2013 | A1 |
| 20130007894 | Dang et al. | Jan 2013 | A1 |
| 20130013560 | Goldberg et al. | Jan 2013 | A1 |
| 20130014023 | Lee et al. | Jan 2013 | A1 |
| 20130042106 | Persaud et al. | Feb 2013 | A1 |
| 20130055127 | Saito et al. | Feb 2013 | A1 |
| 20130067232 | Cheung et al. | Mar 2013 | A1 |
| 20130073403 | Tuchman et al. | Mar 2013 | A1 |
| 20130080919 | Kiang et al. | Mar 2013 | A1 |
| 20130117337 | Dunham | May 2013 | A1 |
| 20130117376 | Filman et al. | May 2013 | A1 |
| 20130124371 | Mehta et al. | May 2013 | A1 |
| 20130124638 | Barreto et al. | May 2013 | A1 |
| 20130138608 | Smith | May 2013 | A1 |
| 20130138615 | Gupta et al. | May 2013 | A1 |
| 20130159411 | Bowen | Jun 2013 | A1 |
| 20130163289 | Kim et al. | Jun 2013 | A1 |
| 20130167253 | Seleznev et al. | Jun 2013 | A1 |
| 20130179676 | Hamid | Jul 2013 | A1 |
| 20130185347 | Romano | Jul 2013 | A1 |
| 20130185558 | Seibert et al. | Jul 2013 | A1 |
| 20130191233 | Atkinson et al. | Jul 2013 | A1 |
| 20130191339 | Haden et al. | Jul 2013 | A1 |
| 20130198600 | Lockhart et al. | Aug 2013 | A1 |
| 20130212486 | Joshi et al. | Aug 2013 | A1 |
| 20130218978 | Weinstein et al. | Aug 2013 | A1 |
| 20130239049 | Perrodin et al. | Sep 2013 | A1 |
| 20130246932 | Zaveri et al. | Sep 2013 | A1 |
| 20130251146 | Roelse | Sep 2013 | A1 |
| 20130262210 | Savage et al. | Oct 2013 | A1 |
| 20130262862 | Hartley | Oct 2013 | A1 |
| 20130266138 | Mantri et al. | Oct 2013 | A1 |
| 20130268480 | Dorman | Oct 2013 | A1 |
| 20130268491 | Chung et al. | Oct 2013 | A1 |
| 20130275398 | Dorman et al. | Oct 2013 | A1 |
| 20130275429 | York et al. | Oct 2013 | A1 |
| 20130275509 | Micucci et al. | Oct 2013 | A1 |
| 20130282830 | Besen et al. | Oct 2013 | A1 |
| 20130305039 | Gauda | Nov 2013 | A1 |
| 20130326344 | Masselle et al. | Dec 2013 | A1 |
| 20140013112 | Cidon et al. | Jan 2014 | A1 |
| 20140019497 | Cidon et al. | Jan 2014 | A1 |
| 20140019498 | Cidon et al. | Jan 2014 | A1 |
| 20140032489 | Hebbar et al. | Jan 2014 | A1 |
| 20140032616 | Nack | Jan 2014 | A1 |
| 20140033277 | Xiao et al. | Jan 2014 | A1 |
| 20140033291 | Liu | Jan 2014 | A1 |
| 20140052939 | Tseng et al. | Feb 2014 | A1 |
| 20140068589 | Barak | Mar 2014 | A1 |
| 20140075198 | Peirce et al. | Mar 2014 | A1 |
| 20140150023 | Gudorf et al. | May 2014 | A1 |
| 20140156373 | Roberts et al. | Jun 2014 | A1 |
| 20140164776 | Hook et al. | Jun 2014 | A1 |
| 20140172595 | Beddow et al. | Jun 2014 | A1 |
| 20140195807 | Bar-El et al. | Jul 2014 | A1 |
| 20140229729 | Roth et al. | Aug 2014 | A1 |
| 20140270178 | Kiang et al. | Sep 2014 | A1 |
| 20140304167 | Atkinson et al. | Oct 2014 | A1 |
| 20150082041 | Gaspar Cuevas | Mar 2015 | A1 |
| Number | Date | Country |
|---|---|---|
| 2724521 | Nov 2009 | CA |
| 101997924 | Mar 2011 | CN |
| 102264063 | Nov 2011 | CN |
| 0348614 | Jan 1990 | EP |
| 0921661 | Jun 1999 | EP |
| 1349088 | Oct 2003 | EP |
| 1528746 | May 2005 | EP |
| 1933242 | Jun 2008 | EP |
| 2372574 | Oct 2011 | EP |
| 2610776 | Jul 2013 | EP |
| 2453924 | Apr 2009 | GB |
| 2471282 | Dec 2010 | GB |
| 09-101937 | Apr 1997 | JP |
| 11-025059 | Jan 1999 | JP |
| 2003273912 | Sep 2003 | JP |
| 2004310272 | Nov 2004 | JP |
| 09-269925 | Oct 2007 | JP |
| 2008250944 | Oct 2008 | JP |
| 20020017444 | Mar 2002 | KR |
| 20040028036 | Apr 2004 | KR |
| 20050017674 | Feb 2005 | KR |
| 20060070306 | Jun 2006 | KR |
| 20060114871 | Nov 2006 | KR |
| 20070043353 | Apr 2007 | KR |
| 20070100477 | Oct 2007 | KR |
| 20100118836 | Nov 2010 | KR |
| 20110074096 | Jun 2011 | KR |
| 20110076831 | Jul 2011 | KR |
| WO-0007104 | Feb 2000 | WO |
| WO-0219128 | Mar 2002 | WO |
| WO-2004097681 | Nov 2004 | WO |
| WO-2006028850 | Mar 2006 | WO |
| WO-2007024438 | Mar 2007 | WO |
| WO-2007035637 | Mar 2007 | WO |
| WO-2007113573 | Oct 2007 | WO |
| WO-2008011142 | Jan 2008 | WO |
| WO-2008076520 | Jun 2008 | WO |
| WO-2011109416 | Sep 2011 | WO |
| WO-2012167272 | Dec 2012 | WO |
| WO-2013009328 | Jan 2013 | WO |
| WO-2013013217 | Jan 2013 | WO |
| WO-2013041763 | Mar 2013 | WO |
| WO-2013166520 | Nov 2013 | WO |
| Entry |
|---|
| Final Office Action dated Oct. 13, 2015 for U.S. Appl. No. 14/670,312. |
| U.S. Appl. No. 60/992,656, filed Dec. 5, 2007, Methods and Systems for Open Source Collaboration in an Application Service Provider Environment. |
| U.S. Appl. No. 61/055,901, filed May 23, 2008, Methods and Systems for Open Source Integration. |
| U.S. Appl. No. 13/646,339, filed Oct. 5, 2012, File Management System and Collaboration Service and Integration Capabilities With Third Party Applications. |
| U.S. Appl. No. 14/073,502, filed Nov. 6, 2013, Methods and Systems for Open Source Collaboration in an Application Service Provider Environment. |
| U.S. Appl. No. 61/434,810, filed Jan. 20, 2011, Real Time Notifications of Activity and Real-Time Collaboration in a Cloud-Based Environment With Applications in Enterprise Settings. |
| U.S. Appl. No. 13/152,982, filed Jun. 3, 2011, Real Time Notification of Activities that Occur in a Web-Based Collaboration Environment. |
| U.S. Appl. No. 13/166,733, filed Jun. 22, 2011, Multimedia Content Preview Rendering in a Cloud Content Management System. |
| U.S. Appl. No. 61/551,894, filed Oct. 26, 2011, Enhanced Multimedia Content Preview Rendering in a Cloud Content Management System. |
| U.S. Appl. No. 13/590,012, filed Aug. 20, 2012, Preview Pre-Generation Based Heuristics and Algorithmic Prediction/Assessment of Predicted User Behavior for Enhancement of User Experience. |
| U.S. Appl. No. 13/297,230, filed Nov. 15, 2011, Enhanced Multimedia Content Preview Rendering in a Cloud Content Management. |
| U.S. Appl. No. 61/592,567, filed Jan. 30, 2012, Preview Pre-Generation Based on Heuristics and Algorithmic Prediction/Assessment of Predicted User Behavior for Enhancement of User Experience. |
| U.S. Appl. No. 61/506,013, filed Jul. 8, 2011, Collaboration Sessions in a Workspace on a Cloud-Based Content Management System. |
| U.S. Appl. No. 13/208,615, filed Aug. 12, 2011, Collaboration Sessions in a Workspace on a Cloud-Based Content Management System. |
| U.S. Appl. No. 61/592,394, filed Jan. 30, 2012, Extended Applications of Multimedia Content Previews in the Cloud Based Content Management System. |
| U.S. Appl. No. 13/588,356, filed Aug. 17, 2012, Extended Applications of Multimedia Content Previews in the Cloud-Based Content Management System. |
| U.S. Appl. No. 13/968,357, filed Aug. 15, 2013, Automatic and Semi-Automatic Tagging Features of Work Items in a Shared Workspace for Metadata Tracking in a Cloud-Based Content Management System With Selective or Optional User Contribution. |
| U.S. Appl. No. 61/538,782, filed Sep. 23, 2011, Central Management and Control of User-Contributed Content in a Web-Based Collaboration Environment and Management Console Thereof. |
| U.S. Appl. No. 13/547,264, filed Jul. 12, 2012, Central Management and Control of User-Contributed Content in a Web-Based Collaboration Environment and Management Console Thereof. |
| U.S. Appl. No. 13/165,725, filed Jun. 21, 2011, Batch Uploading of Content to a Web-Based Collaboration Environment. |
| U.S. Appl. No. 61/505,999, filed Jul. 11, 2011, Desktop Application for Access and Interaction with Workspaces in a Cloud-Based Content Management System and Synchronization Mechanisms Thereof. |
| U.S. Appl. No. 13/282,427, filed Oct. 26, 2011, Desktop Application for Access and Interaction with Workspaces in a Cloud-Based Content Management System and Synchronization Mechanisms Thereof. |
| U.S. Appl. No. 61/554,450, filed Nov. 1, 2011, Platform and Application Independent Method for Document Editing and Version Tracking Via a Web Browser. |
| U.S. Appl. No. 13/332,319, filed Dec. 20, 2011, Platform and Application Independent System and Method for Networked File Access and Editing. |
| U.S. Appl. No. 13/414,480, filed Mar. 7, 2012, Universal File Type Preview for Mobile Devices. |
| U.S. Appl. No. 61/564,425, filed Nov. 29, 2011, Mobile Platform Folder Synchronization and Offline Synchronization. |
| U.S. Appl. No. 61/568,430, filed Dec. 8, 2011, Mobile Platform File and Folder Selection Functionalities for Offline Access and Synchronization. |
| U.S. Appl. No. 13/689,544, filed Nov. 29, 2012, Mobile Platform File and Folder Selection Functionalities for Offline Access and Synchronization. |
| U.S. Appl. No. 13/345,502, filed Jan. 6, 2012, System and Method for Actionable Event Generation for Task Delegation and Management Via a Discussion Forum in a Web-Based Collaboration Environment. |
| U.S. Appl. No. 13/619,439, filed Sep. 14, 2012, Batching Notifications of Activities That Occur in a Web-Based Collaboration Environment. |
| U.S. Appl. No. 61/560,685, filed Nov. 16, 2011, Temporal and Spatial Processing and Tracking of Events in a Web-Based Collaboration Environment for Asynchronous Delivery in an Ordered Fashion. |
| U.S. Appl. No. 13/524,501, filed Jun. 15, 2012, Resource Effective Incremental Updating of a Remote Client With Events Which Occurred Via a Cloud-Enabled Platform. |
| U.S. Appl. No. 13/526,437, filed Jun. 18, 2012, Managing Updates at Clients Used by a User to Access a Cloud-Based Collaboration Service. |
| U.S. Appl. No. 61/579,551, filed Dec. 22, 2011, System Status Monitoring and Data Health Checking in a Collaborative Environment. |
| U.S. Appl. No. 13/464,813, filed Apr. 4, 2012, Health Check Services for Web-Based Collaboration Environments. |
| U.S. Appl. No. 13/405,164, filed Feb. 24, 2012, System and Method for Promoting Enterprise Adoption of a Web-Based Collaboration Environment. |
| U.S. Appl. No. 13/431,645, filed Mar. 27, 2012, Cloud Service or Storage Use Promotion Via Partnership Driven Automatic Account Upgrades. |
| U.S. Appl. No. 61/620,554, filed Apr. 5, 2012, Device Pinning Capability for Enterprise Cloud Service and Storage Accounts. |
| U.S. Appl. No. 13/493,922, filed Jun. 11, 2012, Device Pinning Capability for Enterprise Cloud Service and Storage Accounts. |
| U.S. Appl. No. 61/649,869, filed Mar. 21, 2012, Selective Application Access Control Via a Cloud-Based Service for Security Enhancement. |
| U.S. Appl. No. 13/493,783, filed Jun. 11, 2012, Security Enhancement Through Application Access Control. |
| U.S. Appl. No. 61/702,948, filed Sep. 19, 2012, Cloud-Based Platform Enabled With Media Content Indexed for Text-Based Searches and/or Metadata Extraction. |
| U.S. Appl. No. 13/829,663, filed Mar. 14, 2013, Cloud-Based Platform Enabled With Media Content Indexed for Text-Based Searches and/or Metadata Extraction. |
| U.S. Appl. No. 61/702,662, filed Sep. 18, 2012, Sandboxing Individual Applications to Specific User Folders in a Cloud-Based Service. |
| U.S. Appl. No. 13/830,016, filed Mar. 14, 2013, Sandboxing Individual Applications to Specific User Folders in a Cloud-Based Service. |
| U.S. Appl. No. 61/620,568, filed Apr. 5, 2012, Synchronization Client Selective Subfolder Syncing in a Cloud-Based Environment. |
| U.S. Appl. No. 13/856,607, filed Apr. 4, 2013, Method and Apparatus for Selective Subfolder Synchronization in a Cloud-Based Environment. |
| U.S. Appl. No. 61/622,868, filed Apr. 11, 2012, Web and Desktop Client Synchronization of Mac Packages With a Cloud-Based Platform. |
| U.S. Appl. No. 13/618,993, filed Sep. 14, 2012, Cloud Service Enabled to Handle a Set of Files Depicted to a User as a Single File in a Native Operating System. |
| U.S. Appl. No. 61/643,116, filed May 4, 2012, Hbase Redundancy Implementation for Action Log Framework. |
| U.S. Appl. No. 13/890,172, filed May 8, 2013, Repository Redundancy Implementation of a System Which Incrementally Updates Clients With Events That Occurred Via a Cloud-Enabled Platform. |
| U.S. Appl. No. 13/888,308, filed May 6, 2013, Repository Redundancy Implementation of a System Which Incrementally Updates Clients With Events That Occurred Via a Cloud-Enabled Platform. |
| U.S. Appl. No. 61/693,521, filed Aug. 27, 2012, Backend Implementation of Synchronization Client Selective Subfolder Syncing in a Cloud-Based Environment. |
| U.S. Appl. No. 14/010,851, filed Aug. 27, 2013, Server Side Techniques for Reducing Database Workload in Implementing Selective Subfolder Synchronization in a Cloud-Based Environment. |
| U.S. Appl. No. 61/641,824, filed May 2, 2012, Platform and Application Agnostic Method for Seamless File Access in a Mobile Environment. |
| U.S. Appl. No. 61/650,840, filed May 23, 2012, Platform and Application Agnostic Method for Seamless File Access in a Mobile Environment. |
| U.S. Appl. No. 61/653,876, filed May 31, 2012, Platform and Application Agnostic Method for Seamless File Access in a Mobile Environment. |
| U.S. Appl. No. 13/886,147, filed May 2, 2013, System and Method for a Third-Party Application to Access Content Within a Cloud-Based Platform. |
| U.S. Appl. No. 13/897,421, filed May 19, 2013, Methods, Architectures and Security Mechanisms for a Third-Party Application to Access Content in a Cloud-Based Platform. |
| U.S. Appl. No. 13/898,200, filed May 20, 2013, Metadata Enabled Third-Party Application Access of Content at a Cloud-Based Platform Via a Native Client to the Cloud-Based Platform. |
| U.S. Appl. No. 13/898,242, filed May 20, 2013, Identification Verification Mechanisms for a Third-Party Application to Access Content in a Cloud-Based Platform. |
| U.S. Appl. No. 61/667,909, filed Jul. 3, 2012, Highly Available Ftp Servers for a Cloud-Based Service. |
| U.S. Appl. No. 13/565,136, filed Aug. 2, 2012, Load Balancing Secure Ftp Connections Among Multiple Ftp Servers. |
| U.S. Appl. No. 61/668,626, filed Jul. 6, 2012, Online Shard Migration. |
| U.S. Appl. No. 13/937,060, filed Jul. 8, 2013, System and Method for Performing Shard Migration to Support Functions of a Cloud-Based Service. |
| U.S. Appl. No. 61/668,698, filed Jul. 6, 2012, Identification of People as Search Results From Key-Word Based Searches of Content. |
| U.S. Appl. No. 13/937,101, filed Jul. 8, 2013, Identification of People as Search Results From Key-Word Based Searches of Content in a Cloud-Based Environment. |
| U.S. Appl. No. 61/668,791, filed Jul. 6, 2012, Systems and Methods for Specifying User and Item Identifiers Within an Email Address for Securely Submitting Comments Via Email. |
| U.S. Appl. No. 13/937,124, filed Jul. 8, 2013, Systems and Methods for Securely Submitting Comments Among Users Via External Messaging Applications in a Cloud-Based Platform. |
| U.S. Appl. No. 61/673,671, filed Jul. 19, 2012, Data Loss Prevention Methods and Architectures in a Cloud Service. |
| U.S. Appl. No. 13/944,184, filed Jul. 17, 2013, Data Loss Prevention (Dlp) Methods and Architectures by a Cloud Service. |
| U.S. Appl. No. 13/944,241, filed Jul. 17, 2013, Data Loss Prevention (Dlp) Methods by a Cloud Service Including Third Party Integration Architectures. |
| U.S. Appl. No. 61/694,492, filed Aug. 29, 2012, Method of Streaming File Encryption and Decryption to/From a Collaborative Cloud. |
| U.S. Appl. No. 13/975,827, filed Aug. 26, 2013, Method of Streaming File Encryption and Decryption to/From a Collaborative Cloud. |
| U.S. Appl. No. 61/701,823, filed Sep. 17, 2012, Use of a Status Bar Interface Element As a Handle for Revealing Additional Details. |
| U.S. Appl. No. 13/737,577, filed Jan. 9, 2013, System and Method of a Manipulative Handle in an Interactive Mobile User Interface. |
| U.S. Appl. No. 61/697,437, filed Sep. 6, 2012, Secure File Portability Between Mobile Applications Using a Server-Based Key Generation Service. |
| U.S. Appl. No. 13/776,358, filed Feb. 25, 2013, Secure File Portability Between Mobile Applications Using a Server-Based Key Generation Service. |
| U.S. Appl. No. 61/697,469, filed Sep. 6, 2012, Force Upgrade of a Mobile Application Via Server Side Configuration Files. |
| U.S. Appl. No. 13/776,467, filed Feb. 25, 2013, Force Upgrade of a Mobile Application Via Server Side Configuration File. |
| U.S. Appl. No. 61/697,477, filed Sep. 6, 2012, Disabling the Self-Referential Appearance of a Mobile Application in an Intent Via a Background Registration. |
| U.S. Appl. No. 13/794,401, filed Mar. 11, 2013, Disabling the Self-Referential Appearance of a Mobile Application in an Intent Via a Background Registration. |
| U.S. Appl. No. 61/697,511, filed Sep. 6, 2012, Channel for Opening and Editing Files From a Cloud Service Provider Based on Intents. |
| U.S. Appl. No. 13/776,535, filed Feb. 25, 2013, System and Method for Creating a Secure Channel for Inter-Application Communication Based on Intents. |
| U.S. Appl. No. 61/694,466, filed Aug. 12, 2012, Optimizations for Client and/or Server Feedback Information Enabled Real Time or Near Real Time Enhancement of Upload/Download Performance. |
| U.S. Appl. No. 61/702,154, filed Sep. 17, 2012, Optimizations for Client and/or Server Feedback Information Enabled Real Time or Near Real Time Enhancement of Upload/Download Performance. |
| U.S. Appl. No. 61/703,699, filed Sep. 20, 2012, Optimizations for Client and/or Server Feedback Information Enabled Real Time or Near Real Time Enhancement of Upload/Download Performance. |
| U.S. Appl. No. 14/293,685, filed Jun. 2, 2014, Enhancement of Upload and/or Download Performance Based on Client and/or Server Feedback Information. |
| U.S. Appl. No. 61/751,578, filed Jan. 11, 2013, Functionalities, Features, and User Interface of a Synchronization Client to a Cloud-Based Environment. |
| U.S. Appl. No. 14/153,726, filed Jan. 13, 2014, Functionalities, Features, and User Interface of a Synchronization Client to a Cloud-Based Environment. |
| U.S. Appl. No. 61/715,208, filed Oct. 17, 2012, Adaptive Architectures for Encryption Key Management in a Cloud-Based Environment. |
| U.S. Appl. No. 61/709,086, filed Oct. 2, 2012, Visibility, Access Control, Advancement Reporting Api, and Enhanced Data Protection and Security Mechanisms for Administrators in an Enterprise. |
| U.S. Appl. No. 14/044,261, filed Oct. 2, 2013, System and Method for Enhanced Security and Management Mechanisms for Enterprise Administrators in a Cloud-Based Environment. |
| U.S. Appl. No. 61/709,653, filed Oct. 4, 2012, Corporate User Discovery and Identification of Recommended Collaborators in a Cloud Platform. |
| U.S. Appl. No. 14/046,294, filed Oct. 4, 2013, Corporate User Discovery and Identification of Recommended Collaborators in a Cloud Platform. |
| U.S. Appl. No. 61/709,866, filed Oct. 4, 2012, Enhanced Quick Search Features, Low-Barrier Commenting/Interactive Features in a Collaboration Platform. |
| U.S. Appl. No. 14/046,523, filed Oct. 4, 2012, Enhanced Quick Search Features, Low-Barrier Commenting/Interactive Features in a Collaboration Platform. |
| U.S. Appl. No. 61/709,407, filed Oct. 4, 2012, Seamless Access, Editing, and Creation of Files in a Web Interface or Mobile Interface to a Cloud Platform. |
| U.S. Appl. No. 14/046,726, filed Oct. 4, 2013, Seamless Access, Editing, and Creation of Files in a Web Interface or Mobile Interface to a Collaborative Cloud Platform. |
| U.S. Appl. No. 61/710,182, filed Oct. 5, 2012, Embedded Html Folder Widget for Accessing a Cloud Collaboration Platform and Content From Any Site. |
| U.S. Appl. No. 14/047,223, filed Oct. 7, 2013, System and Method for Generating Embeddable Widgets Which Enable Access to a Cloud-Based Collaboration Platform. |
| U.S. Appl. No. 61/750,747, filed Jan. 9, 2013, File System Event Monitor and Event Filter Pipeline for a Cloud-Based Platform. |
| U.S. Appl. No. 14/149,586, filed Jan. 7, 2014, File System Monitoring in a System Which Incrementally Updates Clients With Events That Occurred in a Cloud-Based Collaboration Platform. |
| U.S. Appl. No. 61/753,761, Conflict Resolution, Retry Condition Management, and Handling of Problem Files for the Synchronization Client to a Cloud-Based Platform. |
| U.S. Appl. No. 14/158,626, Conflict Resolution, Retry Condition Management, and Handling of Problem Files for the Synchronization Client to a Cloud-Based Platform. |
| U.S. Appl. No. 61/739,296, filed Dec. 19, 2012, Synchronization of Read-Only Files/Folders by a Synchronization Client With a Cloud-Based Platform. |
| U.S. Appl. No. 14/135,311, filed Dec. 19, 2013, Method and Apparatus for Synchronization of Items With Read-Only Permissions in a Cloud-Based Environment. |
| U.S. Appl. No. 61/748,399, filed Jan. 2, 2013, Handling Action Log Framework Race Conditions for a Synchronization Client to a Cloud-Based Environment. |
| U.S. Appl. No. 14/146,658, filed Jan. 2, 2014, Race Condition Handling in a System Which Incrementally Updates Clients With Events That Occurred in a Cloud-Based Collaboration Platform. |
| U.S. Appl. No. 61/822,170, filed May 10, 2013, Identification and Handling of Items to Be Ignored for Synchronization With a Cloud-Based Platform by a Synchronization Client. |
| U.S. Appl. No. 14/275,890, filed May 13, 2014, Identification and Handling of Items to Be Ignored for Synchronization With a Cloud-Based Platform by a Synchronization Client. |
| U.S. Appl. No. 61/822,191, filed May 10, 2013, Systems and Methods for Depicting Item Synchronization With a Cloud-Based Platform by a Synchronization Client. |
| U.S. Appl. No. 14/275,401, filed May 12, 2014, Top Down Delete or Unsynchronization on Delete of and Depiction of Item Synchronization With a Synchronization Client to a Cloud-Based Platform. |
| U.S. Appl. No. 61/834,756, filed Jun. 13, 2013, Systems and Methods for Event Budding, Collapsing, or Monitoring by a Synchronization Client of a Cloud-Based Platform. |
| U.S. Appl. No. 14/304,038, filed Jun. 13, 2014, Systems and Methods for Synchronization Event Building and/or Collapsing by a Synchronization Component of a Cloud-Based Platform. |
| U.S. Appl. No. 61/838,176, filed Jun. 21, 2013, Maintaining and Updating File System Shadows on a Local Device by a Synchronization Client of a Cloud- Based Platform. |
| U.S. Appl. No. 14/312,482, filed Jun. 23, 2014, Maintaining and Updating File System Shadows on a Local Device by a Synchronization Client of a Cloud-Based Platform. |
| U.S. Appl. No. 61/839,325, filed Jun. 23, 2013, Systems and Methods for Improving Performance of a Cloud-Based Platform. |
| U.S. Appl. No. 14/314,887, filed Jun. 25, 2014, Systems and Methods for Managing Upgrades, Migration of User Data and Improving Performance of a Cloud-Based Platform. |
| U.S. Appl. No. 61/839,331, filed Jun. 25, 2013, Systems and Methods for Providing Shell Communication in a Cloud-Based Platform. |
| U.S. Appl. No. 14/314,677, filed Jun. 25, 2014, Systems and Methods for Providing Shell Communication in a Cloud-Based Platform. |
| U.S. Appl. No. 13/954,680, filed Jul. 30, 2013, System and Method for Advanced Control Tools for Administrators in a Cloud-Based Service. |
| U.S. Appl. No. 61/860,050, filed Jul. 30, 2013, Scalability Improvement in a System Which Incrementally Updates Clients With Events That Occurred in a Cloud-Based Collaboration Platform. |
| U.S. Appl. No. 14/194,091, filed Feb. 28, 2014, Scalability Improvement in a System Which Incrementally Updates Clients With Events That Occurred in a Cloud-Based Collaboration Platform. |
| U.S. Appl. No. 13/953,668, filed Jul. 29, 2013, System and Method for Advanced Search and Filtering Mechanisms for Enterprise Administrators in a Cloud-Based Environment. |
| U.S. Appl. No. 14/531,035, filed Jul. 3, 2014, System and Method for Advanced Search and Filtering Mechanisms for Enterprise Administrators in a Cloud-Based Environment. |
| U.S. Appl. No. 14/026,674, filed Sep. 13, 2013, Configurable Event-Based Automation Architecture for Cloud-Based Collaboration Platforms. |
| U.S. Appl. No. 61/877,917, filed Sep. 13, 2013, Systems and Methods for Configuring Event-Based Automation in Cloud-Based Collaboration Platforms. |
| U.S. Appl. No. 14/075,849, filed Nov. 8, 2013, Systems and Methods for Configuring Event-Based Automation in Cloud-Based Collaboration Platforms. |
| U.S. Appl. No. 14/027,149, filed Sep. 13, 2013, Simultaneous Editing/Accessing of Content by Collaborator Invitation Through a Web-Based or Mobile Application to a Cloud-Based Collaboration Platform. |
| U.S. Appl. No. 14/042,473, filed Sep. 30, 2013, Simultaneous Editing/Accessing of Content by Collaborator Invitation Through a Web-Based or Mobile Application to a Cloud-Based Collaboration Platform. |
| U.S. Appl. No. 14/026,837, filed Sep. 13, 2013, Mobile Device, Methods and User Interfaces Thereof in a Mobile Device Platform Featuring Multifunctional Access and Engagement in a Collaborative Environment Provided by a Cloud-Based Platform. |
| U.S. Appl. No. 14/166,414, filed Jan. 28, 2014, System and Method of a Multi-Functional Managing User Interface for Accessing a Cloud-Based Platform Via Mobile Devices. |
| U.S. Appl. No. 14/027,147, filed Sep. 13, 2013, System and Method for Rendering Document in Web Browser or Mobile Device Regardless of Third-Party Plug-In Software. |
| U.S. Appl. No. 61/877,938, filed Sep. 13, 2013, High Availability Architecture for a Cloud-Based Concurrent-Access Collaboration Platform. |
| U.S. Appl. No. 14/477,507, filed Sep. 2, 2014, High Availability Architecture for a Cloud-Based Concurrent-Access Collaboration Platform. |
| U.S. Appl. No. 61/894,340, filed Oct. 22, 2013, Desktop Application for Accessing a Cloud Collaboration Platform. |
| U.S. Appl. No. 14/521,134, filed Oct. 22, 2014, Desktop Application for Accessing a Cloud Collaboration Platform. |
| U.S. Appl. No. 14/472,540, filed Aug. 29, 2014, Enhanced Remote Key Management for an Enterprise in a Cloud-Based Environment. |
| U.S. Appl. No. 14/474,008, filed Aug. 28, 2014, Configurable Metadata-Based Automation and Content Classification Architecture for Cloud-Based Collaboration Platforms. |
| Exam Report for GB1410569.6 Applicant: Box, Inc. Mailed Jul. 11, 2014, 9 pages. |
| Sommerer, “Presentable Document Format: Improved On-demand PDF to HTML Conversion,” retrieved from the internet, http://research.microsoft.com, Nov. 2004, 8 pages. |
| “PaperPort Professional 14,” PC Mag. Com review, published Feb. 2012, Ziff Davis, Inc., 8 pages. |
| “PaperPort,” Wikipedia article (old revision), published May 19, 2012, Wikipedia Foundation, 2 pages. |
| “Quickoffice Enhances Android Mobile office Application for Improved Productivity on latest Smartphone and Table Devices,” QuickOffice Press Release, Nov. 21, 2011, QuickOffice Inc., 2 pages. |
| “QuickOffice,” Wikipedia Article (old revision), published May 9, 2012, Wikipedia Foundation, 2 pages. |
| Exam Report for EP13168784.0, Applicant: Box, Inc. Mailed Nov. 21, 2013, 7 pages. |
| Exam Report for GB1309209.3, Applicant: Box, Inc. Mailed Oct. 30, 2013, 11 pages. |
| Exam Report for GB1311417.8, Applicant: Box, Inc. Mailed Dec. 20, 2013, 5 pages. |
| Exam Report for GB1312095.1, Applicant: Box, Inc. Mailed Dec. 12, 2013, 7 pages. |
| Exam Report for GB1312874.9, Applicant: Box, Inc. Mailed Dec. 20, 2013, 11 pages. |
| Exam Report for GB1316532.9, Applicant: Box, Inc. Mailed Oct. 31, 2013, 10 pages. |
| Exam Report for GB1316533.7, Applicant: Box, Inc. Mailed Oct. 8, 2013, 9 pages. |
| Exam Report for GB1316971.9, Applicant: Box, Inc. Mailed Nov. 26, 2013, 10 pages. |
| Exam Report for GB1317600.3, Applicant: Box, Inc. Mailed Nov. 21, 2013, 8 pages. |
| Exam Report for GB1318373.6, Applicant: Box, Inc. Mailed Dec. 17, 2013, 4 pages. |
| Exam Report for GB1320902.8, Applicant: Box, Inc. Mailed Dec. 20, 2013, 4 pages. |
| Gedymin, “Cloud computing with an emphasis on Google App Engine,” Master Final Project, Sep. 2011, 146 pages. |
| Patent Court Document of Approved Judgment for GB0602349.3 and GB0623571.7; Mar. 3, 2009, 17 pages. |
| “Average Conversion Time for a D60 RAW file?” http://www.dpreview.com, Jul. 22, 2002, 4 pages. |
| “Revolving sync conflicts; frequently asked questions,” Microsoft Tech Support, Jul. 16, 2012, retrieved from the Internet: http://web.archive.org/web, 2 pages. |
| “Troubleshoot sync problems,” Microsoft Tech Support: May 2, 2012, retrieved from the internet, http://web. Archive.org/web, 3 pages. |
| “Tulsa TechFest 2012—Agenda,” retrieved from the website, http://web.archive.org, Oct. 2, 2012, 2 pages. |
| Burns, “Developing Secure Mobile Applications for Android,” Oct. 2008, Version 1.0, 1-28 pages. |
| Cohen, “Debating the Definition of Cloud Computing Platforms,” retrieved from the internet, http://forbes.com, Feb. 3, 2014, 7 pages. |
| Comes, “MediaXchange User's Manual,” Version 1.15.15, Feb. 1, 2009, pp. 1-90. |
| Delendik, “Evolving with Web Standards—The Story of PDF.JS,” retrieved from the internet, http://people.mozilla.org, Oct. 12, 2012, 36 pages. |
| Delendik, “My PDF.js talk slides from Tulsa TechFest,” retrieved from the internet, http://twitter.com, Oct. 12, 2012, 2 pages. |
| Duffy, “The Best File-Syncing Services,” pcmag.com, retrieved from the internet: http://www.pcmag.com, Sep. 28, 2012, 7 pages. |
| Exam Report for EP13177108.1, Applicant: Box, Inc. Mailed May 26, 2014, 6 pages. |
| Exam Report for EP13185269.1, Applicant: Box, Inc. Mailed Jan. 28, 7 pages. |
| Exam Report for GB1308842.2, Applicant: Box, Inc. Mailed Mar. 10, 2014, 4 pages. |
| Exam Report for GB1312264.3, Applicant: Box, Inc. Mailed Mar. 24, 2014, 7 pages. |
| Exam Report for GB1314771.5, Applicant: Box, Inc. Mailed Feb. 17, 2014, 7 pages. |
| Exam Report for GB1318792.7, Applicant: Box, Inc. Mailed May 22, 2014, 2 pages. |
| International Search Report and Written Opinion for PCT/US2013/034765, Applicant: Box, Inc., Mailed Jan. 20, 2014, 15 pages. |
| John et al., “Always Sync Support Forums—View topic—Allway sync funny behavior,” Allway Sync Support Forum at http://sync-center.com, Mar. 28, 2011, XP055109680, 2 pages. |
| Partial Search Report for EP131832800, Applicant: Box, Inc. Mailed May 8, 2014, 5 pages. |
| Pyle et al., “How to enable Event logging for Offline Files (Client Side Caching) in Windows Vista,” Feb. 18, 2009, retrieved from the internet: http://blogs.technet.com, 3 pages. |
| Rao, “Box Acquires Crocodoc to Add HTML5 Document Converter and Sleek Content Viewing Experience to Cloud Storage Platform,” retrieved from the internet, http://techcrunch.com, May 9, 2013, 8 pages. |
| Search Report for EP 11729851.3, Applicant: Box, Inc. Mailed Feb. 7, 2014, 9 pages. |
| Search Report for EP13187217.8, Applicant: Box, Inc. Mailed Apr. 15, 2014, 12 pages. |
| Search Report for EP141509422, Applicant: Box, Inc. Mailed May 8, 2014, 7 pages. |
| Search Report for EP14151588.2, Applicant: Box, Inc. Mailed Apr. 15, 2014, 12 pages. |
| Sommerer, “Presentable Document Format: Improved On-demand PDF to HTML Conversion,” retrieved from the internet, http://research.microsoft.com, 8 pages. |
| Tulloch et al., “Windows Vista Resource Kit,” Apr. 8, 2007, Microsoft Press, XP055113067, 6 pages. |
| Walker, “PDF.js project meeting notes,” retrieved from the internet, http://groups.google.com, May 15, 2014, 1 page. |
| Extended Search Report for EP131832800, Applicant: Box, Inc. Mailed Aug. 25, 2014, 7 pages. |
| Extended Search Report for EP141509422, Applicant: Box, Inc. Mailed Aug. 26, 2014, 12pages. |
| Search Report for EP 13189144.2 Applicant: Box, Inc. Mailed Sep. 1, 2014, 9 pages. |
| Exam Report for GB1312874.9 Applicant: Box, Inc. Mailed Sep. 26, 2014, 2 pages. |
| Exam Report for GB1415126.0 Applicant: Box, Inc, Mailed Oct. 2, 2014, 8 pages. |
| Exam Report for GB1415314.2 Applicant: Box, Inc. Mailed Oct. 7, 2014, 6 pages. |
| Exam Report for GB1309209.3 Applicant: Box, Inc. Mailed Oct. 7, 2014, 3 pages. |
| Exam Report for GB1315232.7 Applicant: Box, Inc. Mailed Oct. 9, 2014, 5 pages. |
| Exam Report for GB1318789.3 Applicant: Box, Inc. Mailed Oct. 30, 2014, 6 pages. |
| Microsoft Windows XP Professional Product Documentation: How Inheritance Affects File and Folder Permissions, Apr. 11, 2014, 2 pages. |
| Exam Report for GB1317393..5 Applicant: Box, Inc, Mailed Nov. 7, 2014, 6 pages. |
| Exam Report for GB1311417.8 Applicant: Box, Inc, Mailed Nov. 7, 2014, 2 pages. |
| Exam Report for GB1316682.2 Applicant: Box, Inc. Mailed Nov. 19, 2014, 6 pages. |
| Exam Report for GB1312095.1 Applicant: Box, Inc. Mailed Nov. 19, 2014, 5 pages. |
| Exam Report for GB1313559.5 Applicant: Box, Inc. Mailed Nov. 4, 2014, 2 pages. |
| User's Guide for SMART Board Software for Windows, published Dec. 2004, 90 pages. |
| Zambonini et al., “Automated Measuring of Interaction with User Interfaces,” Published as WO2007113573 Oct. 2007, 19 pages. |
| Exam Report for GB1309209.3 Applicant: Box, Inc. Mailed Jan. 19, 2015, 6 pages. |
| “Agilewords—How to Request Approval,” YouTube, http://www.youtube.com/watch?v=3-Ov3DYNN3Q, Jan. 31, 2011, 2 pages. |
| “Agilewords—Features, Powerful Features Yet Simple,” Jun. 1, 2011, http://web.archive.org/web/20110601223756/http://agilewords.com/product/features, 3 pages. |
| Conner, “Google Apps: The Missing Manual,” published by O'Reilly Media, May 27, 2008, 42 pages. |
| Exam Report for EP 13177108.1, Applicant: Box, Inc. Mailed Feb. 17, 2015, 6 pages. |
| Exam Report for GB1312264.3 Applicant: Box, Inc. Mailed Jan. 30, 2015, 5 pages. |
| Exam Report for GB1312874.9 Applicant: Box, Inc. Mailed Feb. 10, 2015, 7 pages. |
| Exam Report for GB1316685.5 Applicant: Box, Inc, Mailed Feb. 17, 2015, 5 pages. |
| Exam Report for EP 13185269.1, Applicant: Box, Inc. Mailed Feb. 13, 2015, 8 pages. |
| “Conceptboard”, One-Step Solution for Online Collaboration, retrieved from websites http://conceptboard.com and https://www.youtube.com/user/ConceptboardApp?feature=watch, printed on Jun. 13, 2013. 9 pages. |
| “How-to Geek, How to Sync Specific Folders With Dropbox,” downloaded from the internet http://www.howtogeek.com, Apr. 23, 2013, 5 pages. |
| “Microsoft Office SharePoint 2007 User Guide,” Feb. 16, 2010, pp. 1-48. |
| “Understanding Metadata,” National Information Standards Organization, NISO Press, 2004, 20 pages. |
| Cisco, “FTP Load Balancing on ACE in Routed Mode Configuration Example,” DocWiki, Jun. 2011, 7 pages. |
| Conner, “Google Apps: The Missing Manual,” published by O'Reilly Media, May 27, 2008, 24 pages. |
| Exam Report for EP13158415.3, Applicant: Box, Inc. Mailed Jun. 4, 2013, 8 pages. |
| Exam Report for GB1300188.8, Applicant: Box, Inc. Mailed May 31, 2013, 8 pages. |
| Exam Report for GB1306011.6, Applicant: Box, Inc. Mailed Apr. 18, 2013, 8 pages. |
| Exam Report for GB1310666.1, Applicant: Box, Inc. Mailed Aug. 30, 2013, 10 pages. |
| Exam Report for GB1313559.5, Applicant: Box, Inc., Mailed Aug. 22, 2013, 19 pages. |
| Googie Docs, http://web.Archive.org/web/20100413105758/http://en.wikipedia.org/wiki/Googie—docs, Apr. 13, 2010, 6 pages. |
| International Search Report and Written Opinion for PCT/US2008/012973 dated Apr. 30, 2009, pp. 1-11. |
| International Search Report and Written Opinion for PCT/US2011/041308 Mailed Jul. 2, 2012, pp. 1-16. |
| International Search Report and Written Opinion for PCT/US2011/047530, Applicant: Box, Inc., Mailed Mar. 22, 2013, pp. 1-10. |
| International Search Report and Written Opinion for PCT/US2011/056472 mailed on Jun. 22, 2012, pp. 1-12. |
| International Search Report and Written Opinion for PCT/US2011/057938, Applicant: Box, Inc., Mailed Mar. 29, 2013, 10 pages. |
| International Search Report and Written Opinion for PCT/US2011/060875 Mailed Oct. 30, 2012, pp. 1-10. |
| International Search Report and Written Opinion for PCT/US2012/056955, Applicant: Box, Inc., Mailed Mar. 27, 2013, pp. 1-11. |
| International Search Report and Written Opinion for PCT/US2012/063041, Applicant: Box, Inc., Mailed Mar. 29, 2013, 12 pages. |
| International Search Report and Written Opinion for PCT/US2012/065617, Applicant: Box, Inc., Mailed Mar. 29, 2013, 9 pages. |
| International Search Report and Written Opinion for PCT/US2012/067126, Applicant: Box, Inc., Mailed Mar. 29, 2013, 10 pages. |
| International Search Report and Written Opinion for PCT/US2012/070366, Applicant: Box, Inc., Mailed Apr. 24, 2013, 10 pages. |
| International Search Report and Written Opinion for PCT/US2013/020267, Applicant: Box, Inc., Mailed May 7, 2013, 10 pages. |
| International Search Report and Written Opinion for PCT/US2013/029520, Applicant: Box, Inc., Mailed Jun. 26, 2013, 10 pages. |
| International Search Report and Written Opinion for PCT/US2013/034662, Applicant: Box, Inc., Mailed May 31, 2013, 10 pages. |
| International Search Report and Written Opinion for PCT/US2013/035404, Applicant: Box, Inc., Mailed Jun. 26, 2013, 13 pages. |
| International Search Report and Written Opinion for PCT/US2013/039782, Applicant: Box, Inc., Mailed Aug. 28, 2013, 15 pages. |
| Internet Forums, http://web.archive.org/web/20100528195550/http://en.wikipedia.org/wiki/Internet—forums, Wikipedia, May 30, 2010, pp. 1-20. |
| Langfeid L. et al., “Microsoft SharePoint 2003 Unleashed,” Chapters 11 and 15, Jun. 2004, pp. 403-404, 557-561, 578-581. |
| Lars, “35 Very Useful Online Tools for Improving your project Management and Team Collaboration,” Apr. 31, 2010, tripwiremagazine.com, pp. 1-32. |
| Palmer, “Load Balancing FTP Servers,” BlogNav, Oct. 2008, 2 pages. |
| Parr, “Google Docs improves Commenting, Adds E-mail Notifications,” Apr. 16, 2011, mashable.com, pp. 1-6. |
| Partial International Search Report for PCT/US2011/041308 dated Feb. 27, 2012, pp. 1-2. |
| Supplementary European Search Report European Application No. EP 08 85 8563 dated Jun. 28, 2011 pp. 1-5. |
| Wayback, “Wayback machine,” Wayback, Jun. 1, 2011, 1 page. |
| Wiki, http://web.archive.org/web/20100213004936/http://en.wikipedia.org/wiki/Wiki, Feb. 13, 2010, pp. 1-16. |
| Yahoo! Groups, http://web.archive.org/web/20090320101529/http://en.wikipedia.org/wiki/Yahoo!—Groups, Wkipedia, Mar. 20, 2009, pp. 1-6. |
| Number | Date | Country | |
|---|---|---|---|
| 20140270178 A1 | Sep 2014 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61715208 | Oct 2012 | US |
