System and method of a manipulative handle in an interactive mobile user interface

Description

BACKGROUND

A mobile device generally has a limited display area. An application running on the mobile device can display limited information at a time. Some applications minimize fonts, button sizes, etc., in order to fit more information on a display screen. Others cramp the display area by making more information visible at a time. Yet other applications allow users to access information in a way that requires users to leave the screen that they are currently on, or obstructs the information already on the screen. All of these options for displaying information in a mobile device application do not optimize the use of the limited display area available to mobile device applications to display information.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example diagram of a system having a host server of a cloud service and/or cloud storage accounts accessible via an interactive mobile user interface utilizing a manipulative handle.

FIG. 2 depicts a diagram of a web-based or online collaboration platform deployed in an enterprise or other organizational setting for organizing work items and workspaces, as one example of a hosted cloud service and/or cloud storage accounts accessible via an interactive mobile user interface utilizing a manipulative handle.

FIG. 3 depicts an example diagram of a workspace in a cloud-based, online or web-based collaboration environment accessible by multiple collaborators through various devices authorized to access the work space.

FIG. 4A depicts a block diagram illustrating an example of components in a mobile device with an interactive mobile user interface utilizing a manipulative handle for displaying activity status and associated information.

FIG. 4B depicts a block diagram illustrating an example of components in a host server for cloud-based services (e.g., collaborative and/or file sharing) and storage services accessible via an interactive mobile user interface utilizing a manipulative handle.

FIG. 5 illustrates a logic flow diagram of an example method for revealing additional detail using an animated user interface element.

FIG. 6A-E are screenshots showing example user interfaces with animated user interface elements that act as manipulative handles for revealing additional detail.

FIG. 7 shows a diagrammatic representation of a machine in the example form of a computer system within which a set of instructions, for causing the machine to perform any one or more of the methodologies discussed herein, may be executed.

DETAILED DESCRIPTION

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.

Embodiments of the present disclosure include system and method of a manipulative handle in an interactive mobile user interface of a cloud-based collaboration platform. The embodiments facilitate generating, displaying, providing and/or using user interface elements such as a manipulative handle for revealing detail or additional information relating to collaboration platform activities such as uploading, downloading, syncing, streaming, emailing, printing, deleting, copying, and/or the like that are supported by the collaboration platform.

It is generally convenient and efficient to have user interface elements such as transfer status user interface element remain visible on screen at all times. However, mobile device user interfaces have limited screen real estate, which makes the task of finding a place for user interface elements such as transfer status difficult. The manipulative handle described herein provides a solution that balances subtlety (keeping the transfer status minimal) while still allowing the user to get to more detailed information if desired. The manipulative handle described herein strikes the balance by keeping some information (e.g., preferred information) visible on the screen, and some information concealed, either partially or wholly, from the screen, but yet easily accessible from the displayed information should the user desire to see it. Furthermore, the manipulative handle is animated, and responds to user interaction by expanding and contracting, such that the screen real estate is not cramped.

In one example embodiment, the user interface element doubles as a traditional status or progress bar. It shows total status of an action in an animated bar, but can also be used as a manipulative handle to expand a hidden drawer of further details. In doing so, the animated bar keeps status information on the screen in a manner that is subtle, while also providing the user an option to get more details. Furthermore, the user does not need to leave the screen to view the details, and the information displayed on the screen is not completely obstructed by the expansion of the status bar.

In one implementation, the user interface element may include a status bar that has transparent, hidden touch or grab points. Users may engage one or more of such grab points by touching and/or sliding the grab points along with the motion of their finger tip, stylus, mouse or any other input device, giving the suggestion that the status bar is movable. Sliding the grab points a long enough way reveals a hidden drawer of more advanced details. The solution is space efficient and utilizes the screen real estate taken by the status bar in novel ways.

In another example embodiment, the user interface element may have an intelligent and/or customizable component that determines and displays additional information that is likely to be more useful to the user. The intelligence for providing customized additional or detail information for display on the user interface element may be based on user-specific or aggregate application usage data and/or behavior.

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 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 (e.g., 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 FIG. 2. A diagrammatic illustration of a workspace having multiple work items with which collaborators can access through multiple devices is illustrated with further reference to the example of FIG. 3.

In one embodiment, the host server 100 of cloud-based services and/or cloud storage such as an online or web-based collaboration environment is able to track or monitor the devices used by users to access content or activities. In one implementation, such tracking or monitoring may be performed upon receiving explicit permission or authorization from users.

In one embodiment, client devices 102 communicate with the host server 100 and/or notification server 150 over network 106. In general, network 106, over which the client devices 102, the host server 100, and/or notification server 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, 1×RTT, 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 (IMPP), instant messaging, USSD, IRC, or any other wireless data networks or messaging protocols.

FIG. 2 depicts a diagram of a web-based or online collaboration platform deployed in an enterprise or other organizational setting 250 for organizing work items 215, 235, 255 and workspaces 205, 225, 245, as one example of a hosted cloud file sharing, collaboration service and/or cloud storage service accessible via an interactive mobile user interface utilizing a manipulative handle.

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 A-N) 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 for 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 downloaded or edited in accordance with the techniques described in the present disclosure can be 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 to the web-based collaboration platform where notifications are presented, users can, via the same 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.

FIG. 3 depicts an example diagram of a workspace 302 in an online or web-based collaboration environment accessible by multiple collaborators 322 through various devices authorized to access the work space.

Each of users 316, 318, and 320 may individually use multiple different devices to access and/or manipulate work items 324 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.

FIG. 4A depicts a block diagram illustrating an example of components in a mobile device 400 with an interactive mobile user interface utilizing a manipulative handle for displaying activity status and additionally detail information, when the manipulative handle is engaged. The mobile device 400 can be any of the client devices 102 described above. The mobile device 400 can include, for example, a bus 402, and a memory 404 among other components. The memory 404 may include a user interface module 406, an activity status manager 416 and a manipulative handle detail information generator 428. The memory 404 may also include a communication module 424 that facilitates communication between the mobile device 400 and the host server 100 using any of the communication protocols supported by the mobile device 400 and the host server 100. The memory 404 may also include other device modules 426 such as a GPS module for determining and providing location information, text input module for accepting and processing inputs provided using different input mechanisms of the mobile device, and the like for handling various functions of the mobile device 400. Additional or less components/modules/engines can be included in the mobile device 400 and each illustrated component.

The bus 402 is a subsystem for transferring data between the components of the mobile device 400. For example, the bus 402 facilitates the transfer of data between the memory 404 and other components of the mobile device such as the processor and/or the input/output components that utilize the data.

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, handler, 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 media that are statutory (e.g., in the United States, under 35 U.S.C. § 101), and to specifically exclude all media 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.

In one embodiment, the user interface module 406 may include a user interface rendering engine 408, a manipulative handle generator module 410, a manipulative handle contact detector module 412 and a manipulative handle state tracking module 414. The user interface rendering engine 408 includes program codes that accept data in Extensible Markup Language (XML), JavaScript Object Notation (JSON) or other forms and formatting or style information (e.g., Cascading Style Sheets (CSS)) to display the formatted content on the screen of the mobile device. An example of the rendering engine 408 is the webkit layout engine used in the Android platform. The rendering engine 408 may utilize C/C++ libraries such as SQL lite and graphics libraries such as OpenGL ES to render user interface graphics.

The manipulative handle generator module 410 generates the manipulative handle (e.g., user interface elements 610, 680, 690) illustrated in FIGS. 6A-D. The module 410 may generate the manipulative handle by modifying an existing widget provided by the mobile device platform (e.g., the Android Platform or other mobile operating systems or platforms). For example, the module 410 may modify a progress bar widget to generate a modified progress bar widget that has transparent or hidden grab points that can be engaged by a user. When engaged, the module 410 may further provide an expanded progress bar widget that displays detail information. Alternately, the module 410 can use custom program modules (e.g., new View class in the Android platform) to generate a manipulative handle that can respond to an event, such as an engagement event detected by the manipulative handle contact detector module 412. The module 410 leverages data from other modules such as the manipulative handle state tracking module 414 to determine whether to generate an expanded or minimized manipulative handle, the activity status manager module 416 to obtain data regarding the activity status for display on the manipulative handle, and the manipulative handle detail information generator module 428 to obtain detail information for display on the expanded manipulative handle. Alternately, or in addition to the data provided by the mobile device modules 412, 414, 416 and 428, the manipulative handle generator module 410 may obtain data such as status information, formatted in JSON, XML, or the like, from the host server using the facilities of the communication module 424. The communication module 424 establishes a communication channel such as the Transmission Control Protocol (TCP) connection with the host server.

The manipulative handle contact detector module 412 detects user interaction with the manipulative handle of the user interface. The user interaction may be detected by listening in on a callback made by the mobile device framework. For example, a callback may be made when a touch event occurs. The touch event may be caused when a user taps, slides, releases, or applies another gesture to an engagement area of the touch sensitive screen of the mobile device. The contact detector module 412 may be configured to detect contacts made in a predefined engagement area. The contact detector module 412 may provide information (e.g., Boolean data) regarding the detection event to the manipulative handle generator module 410, which responds by modulating (i.e., expanding or minimizing) the manipulative handle based on the current state (i.e., expanded or minimized state), and providing corresponding data and attributes to the rendering engine 408 for rendering the manipulative handle along with other user interface components on the mobile device.

The manipulative handle state tracking module 414 keeps tracks of the minimized or expanded state of the manipulative handle. The state tracking facilitates the manipulative handle generator module 410 to determine whether to generate an expanded or minimized manipulative handle, when the manipulative handle contact detector module 412 registers a touch event.

The activity status manager 416 provides initial information for display on the manipulative handle in its initial state. The activity status manager 416 further handles activity requests from the user, tracks the processing status of the activity, and generates and/or aggregates information relating to the status for display on the manipulative handle. The activity status manager 416 may include an activity request processor module 418, an activity status tracking module 420 and an activity status information generator module 422. The activity request processor module 418 can receive, detect, process, translate, determine and/or package an activity request into a request message (e.g., an HTTP(S) POST message) that is then sent to the host server 100. The activity request processor module 418 may also receive, process, translate, determine and/or parse activity response from the host server.

By way of a non-limiting example, an activity request can include a transfer request such as an upload or download request. In some instances, upon completion of an upload or download via a mobile device, users or collaborators can be notified in real time or near real time (e.g., via the notification server 150 shown in the example of FIG. 1). An upload request, for example, can be submitted by a user through a user interface of the collaboration platform to upload an item or multiple items individually or in batch; similarly, real time or near real time notification of collaborators or other users can occur from a desktop application, web application and/or on another mobile device upon completion or of other types of status updates.

The activity status tracking module 420 can track the status of an activity by periodically querying the host server or local storage areas of the mobile device 400 to obtain a status of an activity such as a transfer of a file to or from the host server 100. For example, if the activity is an upload/download of a work item to or from the host server of the cloud-based platform, then the activity status tracking module 420 tracks the status of the upload/download by determining the size of the file uploaded or periodically checking storage areas in the mobile device to determine the size of the file downloaded. Other parameters including time and number of files uploaded or downloaded can also be tracked by the activity status information tracking module 420. Example of upload/download status information detected by the activity status tracking module 420 include, but is not limited to: in progress, completed, paused, queued or not started, buffering, and the like.

The activity status information generator module 422 can aggregate, derive and/or generate initial information for display on the manipulative handle in its minimized form. For example, the generator module 422 can obtain upload/download status information from the activity status tracking module 420 and provide such status information to the manipulative handle generator module 410 for display on the manipulative handle. In another example, the generator module 422 can obtain information relating to the size of the file uploaded/downloaded from the host server from the activity status tracking module 420 to determine progress (e.g., percentage complete information) and provide such information to the manipulative handle generator module 410 for display on the manipulative handle (e.g., a status or progress bar).

The manipulative handle detail information manager module 428 aggregates, analyses, generates and/or provides additional or detail information relating to the activity for display on the manipulative handle, when the manipulative handle is activated or engaged by a user. The detail information manager 428 may include an activity status detail information generator module 430, a historical usage data aggregator module 432 and a historical usage data analysis module 434. The detail information manager 428 provides the detail information to the manipulative handle generator module 410 when a detection event is registered by the manipulative handle contact detector module 412.

The activity status detail information generator module 430 can obtain, process and/or generate details relating to the status of the activity. The module 430 may obtain, from the host server, detail activity related information that is generated at the host server. Alternatively, or in addition to obtaining detail information from the host server, the module 430 may obtain activity related information from the activity status tracking module 420. In some instances, the module 430 may process such information locally on the mobile device.

For example, the module 430 may obtain from the activity status tracking module 420, information relating to the status of the upload such as size of the file uploaded to the host server, the total file size, download/upload speed, number of files being downloaded/uploaded, percentage completed, estimated time remaining, and the like. The module 430, in one implementation, may directly query the host server for detail information relating to the activity. For example, the module 430 may request the host server to provide contextual information relating to the file or the upload activity such as location where the file is being saved or can be accessed from in future, information relating to collaborators, and the like. The additional detail query to the host server may include one or more parameters such as activity type, storage location (e.g., folder name), and/or the like. The host server, based on the parameters, can determine and provide detail information for display on the manipulative handle. For example, if the activity is related to an upload of a file to a collaboration folder, the detail information may include information such as collaboration history, names of collaborators, options to add collaborators, and/or the like. In one implementation, when a batch upload or batch download is being performed, the module 430 may obtain and/or generate detail information for each file in the batch upload or batch download. In a further implementation, the detail information may include status information for each file in the batch, options to modify (e.g., cancel, pause, email, print, and the like) each file in the batch, and/or options to modify all the files in the batch.

Historical usage data aggregator module 432 tracks application usage and aggregates the application usage data for further analysis by the historical usage data analysis module 434. Types of application usage data aggregated by module 432 include, but are not limited to: use of options such as print, email, preview, share, comment, annotate, etc., use of features such as collaboration (e.g., user actively collaborates, passively collaborates, or never collaborates), interaction with other collaborators, and/or the like. The historical usage data analysis module 434 can reside at the host server or in the mobile device. When the analysis module 434 is residing at the host server, the historical usage data aggregator module 432 sends the aggregated usage data to the host server for further analysis. The host server may then utilize the results of the analysis (e.g., correlation data) to determine and provide detail information appropriate for the user.

The historical usage data analysis module 434, regardless of where it resides, analyses the aggregated usage data from module 432 to determine additional detail information for display on the manipulative handle when it is engaged by the user. For example, the analysis module 434 may determine, based on the usage data, an option (e.g., print, email, share, preview, and the like) that is most frequently used by the user when performing a given activity, and provide the option for display on the manipulative handle. In another example, the analysis module 434 may determine, based on frequency of collaboration, whether further information on collaboration should be displayed, and if so, provide the further information on collaboration for display on the manipulative handle. Similarly, the analysis module 434 may anticipate based on, for example, frequency of email exchanges with other collaborators, that the user is likely to email a file being downloaded to another collaborator, and provide an option (e.g., a link or a button) to send an email to the collaborator for display on the manipulative handle (e.g., “send email to John Doe” button).

FIG. 4B depicts a block diagram illustrating an example of components in a host server 100 for cloud-based services and storage accounts accessible via an interactive mobile user interface utilizing a manipulative handle.

The host server 100 of the web-based or online collaboration environment can generally be a cloud-based service. The host server 100 can include, for example, a network interface 442, an activity request processor 444 having a drag-drop manager 446 and an upload/download engine 454 having a multi-file upload/download manager 456 and/or a folder upload/download manager 458. The host server 100 can also include, for example, an activity status manager 448 having an activity status detector module 450 and an activity status information generator/provider module 452, and a user interface information generator module 466 which may include a manipulative handle detail information generator and/or provider module 468, a historical usage data aggregator module 470, and/or a historical usage data analysis module 472. One embodiment of the host server 100 further includes a notification engine 460 having, for example, a feed stream updator 462 and/or a recipient selector 464. Additional or less components/modules/engines can be included in the host server 100 and each illustrated component.

The network interface 442 can be a networking module that enables the host server 100 to mediate data in a network with an entity that is external to the host server 100, through any known and/or convenient communications protocol supported by the host and the external entity. The network interface 442 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.

One embodiment of the host server 100 includes the activity request processor 444 which can receive, detect, process, identify, parse, translate, and/or determine an activity request. By way of a non-limiting example, an activity request includes a transfer request such as an upload or download request. An upload/download request can be submitted by a user through a user interface of the collaboration platform to upload/download one or multiple items.

The user can identify the files, content, or work items to be uploaded to the host server 100 one-by-one and queue up multiple items (e.g., including but not limited to files, folders, documents, images, audio, etc.) to be uploaded in a single request. The user can also select all of the items to be uploaded in a single action (e.g., via highlighting or otherwise selecting of icons corresponding to each of the items). In one embodiment, the upload request is generated via a drag-and-drop action of the multiple work items to be uploaded to the host server into a portion of a user interface. Drag-and-drop activated uploaded requests can be detected, handled, received, processed, and/or otherwise managed by the drag-drop manager 446.

In one embodiment, the upload request is generated via a drag-and-drop action of a single folder which includes the multiple work items to be uploaded to the host server 100. For example, the upload request can be generated when a folder having the multiple items on a client device that is to be uploaded is identified through the user interface. In some instances, the folder can include additional folders in a folder hierarchy of multiple items.

In some instances, the user can generate an upload request by activating the upload feature in a tab on a user interface and initiate uploading by selecting (e.g., clicking on or otherwise activating) a button/tab. Once selected, another user interface or a pop-up window may appear allowing the user to navigate through files or folders to select the items to be uploaded.

Once upload requests have been detected and processed, the upload engine 454 can upload the requested item or multiple requested items. The upload engine 454 can, in one embodiment, upload a single item or multiple items (e.g., sequentially or simultaneously) to the host server 100. A multiple item upload may be initiated via a single-step or multi-step user request. A multi-file upload request can be handled, processed, and executed, for example, through the multi-file upload manager 456.

In one embodiment, the multi-file upload manager 456 receives an identification of each of the multiple files to be uploaded (e.g., from the upload request processor 444) and sequentially prepares each individual file for uploading and uploads each file independently. For example, the upload manager 456 can compress one of the multiple files individually, upload it to the host server 100 and decompress the file when uploaded and proceed to perform the same steps with the next file. Preprocessing a file can include, for example, analyzing the file size and type to determine if it is acceptable/valid and/or to identify how best to compress the file. Post-processing can include, for example, performing one or more of, decompressing the file, validating the file size and name, checking permissions, potentially scanning for malicious software, and/or moving to permanent storage. The step of moving to storage can further include, one or more of, adding the file metadata to the database, creating thumbnails, creating previews, indexing for search, encrypting the file, and/or storing in multiple locations for redundancy. Note that the above processes can occur in any order or synchronously in any combination with one another. The process continues until all items in the request have been uploaded to the host server 100. The upload may automatically progress from one file when completed to the next one in sequence when the user initiates a multi-file upload request.

In one embodiment, the upload engine 454 uploads multiple items in a folder hierarchy based on a single request to upload a folder which has a hierarchy of folders inside, for example, via the folder upload manager 458. In one embodiment, the folder upload manager compresses the multiple items in the folder hierarchy in a single process into a single item and uploads the single item in a single upload process (rather than one by one) to the host server 100. After the merged file of multiple items has been uploaded, the folder upload manager 458 can decompress and subsequently parse the single upload of the single item into the original individual files that were stored as multiple items in the folders in the hierarchy. By merging multiple files into one and performing a single compression, and decompression step, the uploading process can be expedited since the overhead in time to compress and decompress multiple files is mostly eliminated. Some additional benefits of bulk uploading allow the following overhead to be partially or wholly eliminated: repeatedly creating TCP connections for each upload, repeatedly checking the same permissions and storage quotas when processing the files on the server.

In one embodiment, the activity status manager 448 detects, tracks and manages status of an activity being processed by the activity request processor 444 and the upload/download engine 454. The activity status manager 448 may also respond to request for information from the corresponding activity status manager 416 of the mobile device 400. The activity status detector module 450 can detect the status of, for example, a request for a single or batch upload of files. By way of non-limiting example only, the detector module 450 detects status such as, but not limited to: upload complete, upload in progress, waiting to upload, file in preprocessing, file in post-processing, file in buffer, file in permanent storage, and the like. The activity status detector module 450 can further detect and track status such as, but not limited to: total size of files(s) to upload, time elapsed, total size of file(s) uploaded, time remaining, average speed of upload, and the like.

The activity status information generator module 452 obtains, processes, generates and/or packages status information on an activity and provides such information to the mobile device. In one implementation, the providing is triggered by events detected by the activity status detector module 450. For example, when the upload of a file is complete as detected by the detector module 450, the module 452 may process and package the status information and send it to the mobile device for display. In another implementation, the providing is triggered by a request for status information from the mobile device. In yet another implementation, the module 452 periodically checks the status information from the detector module 450 and provides such information to the mobile device.

In one embodiment, the host server 100 may include the manipulative handle detail information manager module 466 having the manipulative handle detail information generator module 468, the historical usage data aggregator module 470 and historical usage data analysis module 472. The detail information generator module 468 performs the function of receiving and parsing requests for detail information, gathering and/or generating the requested detail information, and providing such information to the corresponding manager module 428 of the mobile device. The detail information generator module 468 usually obtains detail relating to the activity status from the activity status detector manager 448. In some embodiments, the detail information generator module 468 can obtain detail information from the historical usage data aggregator module 470 and the historical usage data analysis module 472.

Similar to the historical usage data aggregator module 432, module 470 aggregates user-specific application usage data such as, but not limited to: use of options such as print, email, preview, share, comment, annotate, use of features such as collaboration, interaction with other collaborators, and the like. Furthermore, the server-side implementation of the module 470 may aggregate application usage data collected from some or all users, such that the aggregate application usage data represents aggregate application usage behavior of a representative sample of users or all users of the collaboration platform. Module 472, like the historical usage data analysis module 434, analyses aggregated application usage data (e.g., user specific and otherwise) to determine information, options, functions and/or features that are likely to be useful to a user. The analysis module 434 can, in some implementations, establish correlations, such as a correlation between an activity type and information, options, functions or features most frequently used by users performing the activity. The detail information generator module 468 can provide the information, options, functions and/or features determined by the historical usage data analysis module 434 to be the most relevant, applicable, useful or correlated to the mobile device for display on the expanded manipulative handle.

One embodiment of the host server 100 includes a notification engine 460. The notification engine 460, can for example, update a feed stream to include an updated feed indicate that an item or multiple items have been uploaded, for example, via the feed stream updator 462. The users that are notified can be selected, for example, by the recipient selector 464, and can include collaborators or the user, or other users meeting a criterion. In some instances, the feed stream is updated in real time or near real time relative to when the upload of the item completed. For real-time updating, the notification engine 460 can utilize another server, or another engine in the same server which provides push functionality.

The notification engine 460 can generally notify users, which can be collaborators of the user who performed the activity in the work space via one or more of many mechanisms, including but not limited to, email, SMS, voice-message, text-based message, RSS, feed, etc., as described in detail with further reference to related co-pending U.S. patent application Ser. No. 13/152,982 filed on Jun. 3, 2011. The contents of which are incorporated herein by reference in its entirety.

In one embodiment, the notification is depicted through a web-browser used by the other user to access the web-based collaboration environment, for access in real time or near real time to when the activity was performed by the user. When notifying a user in real time through a web-browser, the notification engine 460 can utilize a push-enabled service to ensure real time notification. In one embodiment, the notification is sent by a component or another server which implements push technology (e.g., the notification server 150 shown in the example of FIG. 1). The push-enabled service can be implemented via long poll or HTTP streaming, for example, by the notification server 150 or another component, device which may be internal to or external to the host server 100. In addition, the host server 100 could utilize other push servers including third party push servers to implement push technology including but not limited to mobile platform push systems and services (e.g., via smart phones or tablets or other portable devices such as iPhone, Android phones, Blackberry, iPad, Galaxy or other tablets, etc.).

One embodiment of the host server 100 includes the user interface module 476, which preserves or enhances user experience before, during, or after an upload request. For example, the user interface module 476 can allow the user to engage in other activities in the collaboration platform while an upload is in progress so as to prevent the user from having to wait for the completion to work in the platform.

In one embodiment, during the upload of a single file (before completion), the user can generally navigate away from the user interface through which the upload request was submitted, for example, via the navigation manager 478 in the user interface module 476. In other words, while a file or item upload is in progress, the user can navigate to other pages to perform other actions or initiate additional actions on the current page without interrupting (stopping or pausing) the in-progress upload.

Similarly, when a multi-file or multi-item upload request is in progress, the user can also navigate away from the user interface which the upload request was submitted prior to completion of the uploading of each of the multiple items to the host server 100. Navigation between pages during an upload of multiple files can also be managed by the navigation manager 478. For example, the upload of the multiple items can continue to proceed and is not interrupted if the user accesses a link on the user interface causing another user interface to launch in a browser. To enable bulk uploading, a new browser window is opened so it operates independently of user navigation. In addition, the web application for uploading and access of the collaboration environment is “pageless,” meaning it can be updated asynchronously without a browser page refresh. This allows navigation and to start new uploads in other folders, which can be added to the upload queue.

In addition, during a multi-file upload, an item of the multiple items that has been uploaded to the host server 100 available for access through the user interface, even when some of the multiple items have not yet been uploaded to the host server, via the upload content access module 480, for example. Thus, during an active upload, individual files which have completed uploading can be accessed or interacted with by the user in the collaborative environment without having to wait for the full upload to complete.

In some instances, the item which has been uploaded to the host server is manipulatable by the user through the user interface, without a need for browser refresh. This enhances the user experience by allowing the user to work on the file or otherwise interact with it once it has been uploaded without waiting for other files to finish uploading. For example, the user can view, edit, preview, or comment on the item that has been uploaded, prior to completion of uploading all of the multiple items in an upload request. In one embodiment, buffer space in memory for storage of the individual work items are created in response to the upload request such that when individual items have been uploaded, they can be moved into the created buffer space, and subsequently permanent storage. When the file is in permanent storage, the user can then access and work on the individual item, while others are still being uploaded. In one embodiment, metadata for the file can be created before it is fully uploaded or processed, allowing faster user interaction. However, to actually interact with the file content (full content search, download or preview) the file generally needs to be processed as usual and be stored in permanent storage.

FIG. 5 illustrates a logic flow diagram of an example method for revealing additional detail using a user interface element. Example method 500 includes initiating a collaboration platform activity from the mobile device, tracking the status of the activity and displaying the status using a user interface element. Example method 500 further includes detecting activation of hidden grab points on or near the user interface element and expanding the user interface element to reveal additional detail. If the user interface element is already in an expanded state, detecting activation of hidden grab points on the user interface element may cause minimization of the user interface element, thereby concealing the additional detail revealed earlier.

A user may initiate a collaboration platform activity at block 510 by, for example, activating an application feature. An application feature includes any functions provided by the collaboration platform. By way of example only, an application feature includes upload, download, sync, transfer, stream, email, print, comment, post, copy, move, open, close, delete, and/or the like of a work item or multiple work items. Associated with each activity is a status. For example, if the user initiated upload of a file, the status would provide information on the progress of the activity. At block 520, the status of the activity may be tracked. The status may track, for example, any of the previously discussed activity related information such as the percentage or size of the file that has been uploaded and/or is still to be uploaded at any given time, the amount of time passed and/or time remaining to complete the activity, and/or the like.

At block 530, the status may be displayed in an animated user interface element. Referring to user interface 605 shown in FIG. 6A, an animated user interface element may be depicted by a status bar 610. As shown, a download activity is being performed, and status bar 610 shows the status of the download (e.g., download of 672.7 KB of 123.6 KB complete).

Status bar 610 may be an animated status bar. In other words, the status bar is not static, but is responsive to user interaction. In one implementation, status bar 610 and/or an area proximate to the status bar may be responsive to user interaction. The responsiveness to user interaction may be provided by hidden contact, touch or grab points, which may be contacted, touched, or otherwise engaged. Referring to FIG. 5, at block 540, an activation or engagement of such hidden contact points at or near the user interface element (e.g., status bar 610) may be detected. As previously discussed, the manipulative handle contact detector module 414 may detect the engagement in one embodiment.

In one implementation, the contact points may be engaged in one or more ways. For example, referring to FIG. 6B, user interface 615 depicts example mechanics for engaging hidden contact points. In one implementation, contact points may be distributed over an engagement area, such as an area defined by perimeter 620 around status bar 610. Although a rectangular engagement area is shown, areas of other regular (square, circle, oval, hexagonal, etc.) or irregular shapes, and having different measurements (length, width, radii, etc.) are contemplated. Within the engagement area, the client application may be responsive to various gestures to engage the contact points. For example, in one implementation, the user may apply an upwards motion, represented by gesture 625a, on the display screen. In another implementation, a tap or touch represented by 625b may be sufficient. In yet another implementation, a leftward or a rightward slide represented by 625c may be applied. In other implementations, a downward slide represented by 625d may be applied. One or more of these gestures may be combined in a single implementation.

Referring to FIG. 5, upon detection of engagement of the contact points, at block 540, the user interface element may be expanded to display additional detail of the activity. In one embodiment, the expanded user interface element may be generated by the manipulative handle generator module 410, which can leverage data from other mobile device modules and/or the host server 100. Referring to FIG. 6C, user interface 650 shows the expanded user interface element 665. Expanded user interface element 665 includes status bar 610, as well as additional details such as detailed status information represented by 655 and button options represented by cancel button 660. In the example user interface 650, the activity is related to download of a work item and thus, expanded user interface element 665 reveals previously hidden details concerning the status of the download activity, such as the number of files being saved and size of the file downloaded so far, and an option to cancel the activity. In the case of other activities, the expanded user interface element may reveal other previously hidden details. For example, if the activity is upload of a work item, the expanded user interface element may reveal details such as the size of the work item uploaded so far, time remaining to complete the upload, name of the collaboration folder to which the work item is being uploaded, names of users A, B and C who are designated as collaborators, size of the user account used/free, and/or the like. The detail information may be generated and/or provided by the manipulative handle detail information manager 428 and/or the user interface information generator module 466. Referring to FIG. 6E, an example user interface 685 shows an activity relating to playing of a movie file. As shown, the client application may have buffering requirement, where it waits until a certain portion of the file is downloaded in the client device cache memory before playing the file. The user may engage the status bar 690 or an area around the status bar to expand to view details 695 concerning the “buffering” status.

In one implementation, options for modifying the activity or initiating another activity (e.g., email, print, share, etc.) may be available. For example, as previously discussed, the expanded status bar may include an option to modify the download activity by canceling it. Other types of modifications include pause, resume, and/or the like.

In various implementations, the additional detail that may be revealed by the expanded user interface element may vary. In various embodiments, the additional detail information can be generated and/or provided by the manipulative handle detail information manager 428 of the mobile device, the user interface information generator module 466 of the host server, or a combination thereof. In one implementation, the additional detail may include information that may be useful to the user or is likely to be used based on the user's historical usage data and/or a user profile. For example, if the user is an active collaborator, the additional detail may include collaboration information corresponding to the specific activity. Similarly, if the user regularly prints or emails documents, the additional detail may include options to perform print or email action. Such historical usage data may be saved locally or remotely in one or more servers and/or associated data stores.

In another implementation, the additional detail may include information based on predefined criteria such as activity type. For example, if the activity is associated with a file transfer, the additional detail may include file size information, file transfer location, size of file transferred or remaining to be transferred, and/or the like. Similarly, if the activity is associated with an upload to a collaboration folder, the additional detail may include information such as collaboration history, names of collaborators, options to add collaborators, and/or the like. Thus, in some implementations, the expanded drawer of additional details may be used as a pivot point to perform other actions relating to a specific item without having to leave the current screen, and without having the additional information obstruct the original activity (e.g., status of the file download).

Similar to the way the user interface element is used as a handle to expand and reveal additional detail, the expanded user interface element may also be used as a handle to conceal the additional detail and display the user interface element in its minimized original form. Alternately, the expanded user interface element may be modified by removing a portion, but not all of the additional detail, such that a modified user interface element, and not the original form of the user interface element, is displayed. Referring to FIG. 5, the minimization may be initiated when, at block 560, engagement of hidden contact points on or near the expanded user interface element is detected. As previously described, the engagement area may be defined by a perimeter, and one or more gestures may be applied. In response to the detection of engagement of the hidden contact points, the expanded user interface element may be minimized at block 570, thereby again concealing the additional detail.

In one implementation, the minimization of the expanded user interface element may not require engagement of the hidden contact points. The expanded user interface element may be automatically minimized after a predefined amount of time (e.g., 15 seconds) has lapsed. In a further implementation, the timer may be reset when the user engages one or more options on the expanded user interface element.

In one implementation, it should be noted that the engagement of any area outside of the engagement area may have no effect on the state (e.g., expanded or minimized state) of the user interface element. For example, referring to FIG. 6C, when the user selects the scroll option 662 on user interface 650, next user interface 670 of FIG. 6D is displayed. As shown, the state of the status bar user interface element in user interface 670 remains the same (i.e., expanded state). However, the content of the expanded user interface element is changed to reflect the current item being displayed on the display panel (e.g., WP_001096.jpg of user interface 570 instead of WP_001095.jpg of user interface 550).

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.

Claims

1. A method of an interactive user interface for accessing a cloud-based platform via a mobile device, comprising: displaying, to a user, first information concerning a multi-file cloud-based platform supported activity on a user interface element of an application on the mobile device, the application providing access to one or more content items in the cloud-based platform and allowing interaction with one or more users of the cloud-based platform, the user interface element configured to provide customized user-specific options selectable by the user based on analyzing data relating to usage of the application on the mobile device, the usage of the application comprising access to the one or more content items or interaction with the one or more users, wherein the multi-file cloud-based platform supported activity includes at least two files;detecting engagement of the user interface element or a region defined by a perimeter relative to the user interface element for generating the data relating to the usage of the application on the mobile device, wherein the engagement includes engagement of multiple contact points on the user interface element or the region defined by the perimeter relative to the user interface element;upon detecting the engagement of the user interface element or the region defined by the perimeter relative to the user interface element, determining a state of the user interface element, wherein the state of the user interface element includes a fully expanded state or a partially minimized state;in response to determining that the user interface element is in a partially minimized state and the cloud-based platform supported activity is associated with an upload of a file or a file transfer session including the at least two files, changing the partially minimized user interface element to a fully expanded user interface element to reveal information that is concealed in the partially minimized state and is supplemental to the first information;upon identifying that the cloud-based platform supported activity is associated with an upload of a file, displaying second information within the fully expanded user interface element, the second information including a size information corresponding to a portion of the file being uploaded, a remaining time to complete the upload of the file, a name of a collaboration folder where the file is being uploaded, and a consumed size of the collaboration folder where the file is being uploaded, wherein the display of the second information is asynchronously updated during the upload of the file; andupon identifying that the cloud-based platform supported activity is associated with a file transfer session, displaying second information within the fully expanded user interface element, the second information including a size of the file being transferred, a location for the transfer of the file, a size information corresponding to a portion of the file being transferred, wherein the display of the second information is asynchronously updated during the file transfer session.
2. The method of claim 1, wherein, the cloud-based platform provides a collaboration or a file sharing service.
3. The method of claim 1, wherein the engagement includes tapping or sliding of one or more of the multiple contact points via touch screen action on a screen of the mobile device.
4. The method of claim 1, wherein the cloud-based platform supported activity includes a single file and corresponds to download of the file from a host server of the cloud-based platform and the first information includes status information concerning the status of the download.
5. The method of claim 4, wherein the second information includes additional detail relating to the status information concerning the status of the download.
6. The method of claim 5, wherein the second information includes additional detail relating to one or more options to make modifications to the download of the file or initiate a collaboration or a file sharing activity.
7. The method of claim 5, wherein the data relating to usage of the application on the mobile device is specific to a user.
8. The method of claim 1, further comprising: detecting engagement of the expanded user interface element or a region defined by a perimeter relative to the expanded user interface element; andin response to determining that the user interface element is in an expanded state, minimizing the expanded user interface element such that the second information is not displayed.
9. The method of claim 2, wherein the cloud-based platform supported activity includes collaboration activity with other users in the cloud-based platform.
10. The method of claim 9, wherein, the cloud-based platform supported activity includes at least one of: downloading, syncing, transferring, buffering, copying, deleting, emailing, generating a preview, or commenting on the file.
11. A mobile device having an interactive mobile user interface for accessing a cloud-based service to interact with a work item, comprising: a processor configured to: detect the engagement of the user interface element or a region defined by the perimeter relative to the user interface element; andupon detecting the engagement of the user interface element or the region defined by the perimeter relative to the user interface element, determine a state of a user interface element or the region defined by the perimeter relative to the user interface element, wherein the state of the user interface element includes a fully expanded state or a partially minimized state;a memory unit having instructions stored thereon which when executed by the processor, causes the processor to generate the interactive mobile user interface having the user interface element configured to: display, to a user, status information concerning a multi-item cloud-based platform supported activity that includes at least two work items, the user interface element including multiple contact points responsive to user engagement;changing the partially minimized state user interface element to a fully expanded user interface element to reveal information that is concealed in the partially minimized state and is supplemental to the status information, in response to determining that the user interface element is in the partially minimized state, upon detecting engagement of the user interface element;upon identifying that the cloud-based platform supported activity is associated with an upload of the work item included in the at least two work items, displaying additional information within the fully expanded user interface element, the additional information including a size information corresponding to a portion of the work item being uploaded, a remaining time to complete the upload of the work item, a name of a collaboration workspace where the work item is being uploaded, and a consumed size of the collaboration workspace where the work item is being uploaded, wherein the display of the additional information is asynchronously updated during the upload of the work item;upon identifying that the cloud-based platform supported activity is associated with a work item transfer session including the at least two work items, displaying additional information within the fully expanded user interface element, the additional information including a size of the work item being transferred, a location for the transfer of the work item, a size information corresponding to a portion of the work item being transferred, wherein the display of the additional information is asynchronously updated during the work item transfer session; andprovide customized user-specific options selectable by the user based on analyzing the data relating to the usage of an application associated with the mobile user interface, the application providing access to one or more content items in the cloud-based platform and allowing interaction with one or more users of the cloud-based platform and the usage of the application comprising access to the one or more content items or interaction with the one or more users.
12. The mobile device of claim 11 wherein, the cloud-based service includes a cloud-based collaboration service, wherein, the at least two work items are transferred to or from the cloud-based service via the mobile device for collaboration on the at least two work items with other users of the cloud-based service.
13. The mobile device of claim 11, wherein the engagement of the user interface element includes tapping or sliding of one or more of the multiple contact points via touch screen action on a screen of the mobile device.
14. The mobile device of claim 11, wherein the additional information includes one or more options to modify the transfer of the at least two work items.
15. The mobile device of claim 11, wherein the additional information is determined based on historical usage data.
16. The mobile device of claim 11, wherein the status information is provided by a host server associated with the cloud-based service and at least some of the additional information is obtained locally from the mobile device.
17. The mobile device of claim 11, wherein the user interface element is further configured to: decrease in size in response to detecting a subsequent engagement of the user interface element such that the additional information is not displayed by the user interface element.
18. A non-transitory computer-readable storage medium storing a set of instructions which when executed by a computing system on a mobile device causes the computing system to perform a method for generating an interactive user interface on a mobile display region for providing information related to processing information of a work item of a cloud-based environment, comprising: displaying, to a user, status information relating to a multi-item cloud-based environment supported activity associated with at least two work items;providing a user interface element for user interaction, wherein the user interface element includes multiple contact points responsive to user interaction, the user interface element configured to provide customized user-specific options selectable by the user based on analyzing data relating to usage of an application on the mobile device, the application providing access to one or more content items in the cloud-based platform and allowing interaction with one or more users of the cloud-based platform and the usage of the application comprising access to the one or more content items or interaction with the one or more users;detecting the user interaction with the user interface element for generating the data relating to the usage of the application on the mobile device;upon detecting the user interaction, determining a state of the user interface element, wherein the state of the user interface element includes a fully expanded state or a partially minimized state;in response to determining that the user interface element is in a partially minimized state and the cloud-based environment supported activity associated with an upload of a work item or a work item transfer session, changing the partially minimized user interface element to a fully expanded user interface element to reveal information that is concealed in the partially minimized state and is supplemental to the status information;upon identifying that the cloud-based environment supported activity is associated with an upload of the work item, displaying additional information within the fully expanded user interface element, the additional information including a size information corresponding to a portion of the work item being uploaded, a remaining time to complete the upload of the work item, a name of a collaboration workspace where the work item is being uploaded, and a consumed size of the collaboration workspace where the work item is being uploaded, wherein the display of the additional information is asynchronously updated during the upload of the work item; andupon identifying that the cloud-based environment supported activity is associated with a work item transfer session, displaying additional information within the fully expanded user interface element, the additional information including a size of the work item being transferred, a location for the transfer of the work item, a size information corresponding to a portion of the work item being transferred, wherein the display of the additional information is asynchronously updated during the work item transfer session.
19. The computer-readable storage medium of claim 18, wherein the cloud-based environment supported activity includes performing a batch processing function of work items, including one or more of batch upload, batch download function, to or from the cloud-based collaboration environment.
20. The computer-readable storage medium of claim 19, wherein the batch processing function of the work items is related to collaboration activities with other users of the cloud-based environment such that other users of the cloud-based environment are able to perform collaborative functions on the batch uploaded or the batch downloaded work items.
21. The computer-readable storage medium of claim 18, wherein the user interaction includes tapping or sliding of one or more of the multiple contact points via touch screen action.
22. The computer-readable storage medium of claim 18, wherein the additional information includes an option to cancel processing of one or more of the work items or cancel the batch processing.
23. The computer-readable storage medium of claim 18, further comprising: detecting a subsequent user interaction with the user interface element;concealing the additional information relating to the cloud-based environment supported activity in response to the detecting.
24. The computer-readable storage medium of claim 18, further comprising: receiving the status information from a host and at least some of the additional information from the mobile device.
25. The method of claim 1, wherein the analyzing the data relating to the usage of the application on the mobile device is performed at a server associated with the cloud-based perform.
26. The method of claim 1, wherein the analyzing the data relating to the usage of the application on the mobile device is performed at the mobile device.
27. The method of claim 1, wherein the customized user-specific options include most frequently-done activities by the user.
28. The method of claim 27, wherein the frequently-done activities by the user is based on at least one of: a frequency of the collaboration with other collaborators and a frequency of email exchanges with other collaborators.
29. The method of claim 1, wherein the analyzing the data relating to the usage of the application is based at least in part on a correlation between (i) data relating to the cloud-based platform supported activity and (ii) data relating to settings or features frequently used by the user for performing the cloud-based platform supported activity.
30. The method of claim 1, wherein the in response to further includes: upon identifying that the cloud-based platform supported activity is associated with downloading a digital media file, the second information includes buffering status information corresponding to a portion of the digital media file being downloaded.
31. The mobile device of claim 11, wherein the expand in response to further includes: upon identifying that the cloud-based platform supported activity is associated with downloading a digital media work item, the additional information includes buffering status information corresponding to a portion of the digital media work item being downloaded.
32. The computer-readable storage medium of claim 18, wherein the in response to further includes: upon identifying that the cloud-based environment supported activity is associated with downloading a digital media work item, the additional information includes buffering status information corresponding to a portion of the digital media work item being downloaded.

CROSS-REFERENCE TO RELATED APPLICATION(S)

The present application claims priority to and benefit from U.S. Provisional Patent Application Ser. No. 61/701,823 titled “Use of a Status Bar Interface Element as a Handle for Revealing Additional Details”, filed on Sep. 17, 2012, the entire content of which is expressly incorporated by reference herein.

US Referenced Citations (487)

Number	Name	Date	Kind
858619	O'Farrell	Jul 1907	A
5787175	Carter	Jul 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
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	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
7886295	Burger et al.	Feb 2011	B2
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
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
8918387	Sokolov	Dec 2014	B1
8949939	Peddada	Feb 2015	B2
8959579	Barton et al.	Feb 2015	B2
8990955	Hymel et al.	Mar 2015	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
20020116544	Barnard et al.	Aug 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
20040098361	Peng	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
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
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
20050210412	Matthews	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	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
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
20080059656	Saliba 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
20080114844	Sanchez	May 2008	A1
20080133674	Knauerhase et al.	Jun 2008	A1
20080140732	Wilson et al.	Jun 2008	A1
20080151817	Fitchett et al.	Jun 2008	A1
20080154873	Redlich et al.	Jun 2008	A1
20080168401	Boule	Jul 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
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	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
20090282483	Bennett	Nov 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
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
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
20100248787	Smuga	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
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
20110145744	Haynes et al.	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
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
20110277027	Hayton et al.	Nov 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
20120092055	Peschke et al.	Apr 2012	A1
20120096521	Peddada	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
20120173612	Vegesna-Venkata et al.	Jul 2012	A1
20120173625	Berger	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
20120259964	Lin et al.	Oct 2012	A1
20120263166	Cho et al.	Oct 2012	A1
20120266203	Elhadad et al.	Oct 2012	A1
20120284638	Cutler	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
20120331394	Trombley-Shapiro	Dec 2012	A1
20120331441	Adamson	Dec 2012	A1
20130007245	Malik 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
20130061259	Raman	Mar 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
20130124638	Barreto et al.	May 2013	A1
20130138608	Smith	May 2013	A1
20130138615	Gupta et al.	May 2013	A1
20130152003	Ricci	Jun 2013	A1
20130159411	Bowen	Jun 2013	A1
20130163289	Kim et al.	Jun 2013	A1
20130167253	Seleznev et al.	Jun 2013	A1
20130185347	Romano	Jul 2013	A1
20130185558	Seibert 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
20130262210	Savage et al.	Oct 2013	A1
20130262862	Hartley	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
20130332886	Cranfill	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
20140150023	Gudorf et al.	May 2014	A1
20140156373	Roberts et al.	Jun 2014	A1
20140172595	Beddow et al.	Jun 2014	A1
20140344456	Buzbee et al.	Nov 2014	A1
20140359286	Wen et al.	Dec 2014	A1
20150019723	Kweon et al.	Jan 2015	A1

Foreign Referenced Citations (43)

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
152874	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-2002019128	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-2013166520	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

Non-Patent Literature Citations (260)

Entry
http://web.archive.org/web/20100207220834/http://www.motobit.com/help/scptutl/pure-asp-upload.htm, Feb. 7, 2010, www.archive.org.
https://web.archive.org/web/20120128234726/http://www.codeproject.com/Articles/113418/ASP-NET-File-Upload-with-Progress-Bar, Jan. 28, 2012, www.archive.org.
“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. dated Nov. 21, 2013, 7 pages.
Exam Report for GB1309209.3, Applicant: Box, Inc. dated Oct. 30, 2013, 11 pages.
Exam Report for GB1310666.1, Applicant: Box, Inc. dated Aug. 30, 2013, 10 pages.
Exam Report for GB1311417.8, Applicant: Box, Inc. dated Dec. 20, 2013, 5 pages.
Exam Report for GB1312095.1, Applicant: Box, Inc. dated Dec. 12, 2013, 7 pages.
Exam Report for GB1312874.9, Applicant: Box, Inc. dated Dec. 20, 2013, 11 pages.
Exam Report for GB1313559.5, Applicant: Box, Inc., dated Aug. 22, 2013, 19 pages.
Exam Report for GB1316532.9, Applicant: Box, Inc. dated Oct. 31, 2013, 10 pages.
Exam Report for GB1316533.7, Applicant: Box, Inc. dated Oct. 8, 2013, 9 pages.
Exam Report for GB1316971.9, Applicant: Box, Inc. dated Nov. 26, 2013, 10 pages.
Exam Report for GB1317600.3, Applicant: Box, Inc. dated Nov. 21, 2013, 8 pages.
Exam Report for GB1318373.6, Applicant: Box, Inc. dated Dec. 17, 2013, 4 pages.
Exam Report for GB1320902.8, Applicant: Box, Inc. dated Dec. 20, 2013, 4 pages.
Gedymin, “Cloud computing with an emphasis on Google App Engine,” Master Final Project, Sep. 2011, 146 pages.
Google Docs, http://web.Archive.org/web/20100413105758/http://en.wikipedia.org/wiki/Google_docs, Apr. 13, 2010, 6 pages.
International Search Report and Written Opinion for PCT/US2013/039782, Applicant: Box, Inc., dated Aug. 28, 2013, 15 pages.
Patent Court Document of Approved Judgment for GB0602349.3 and GB0623571.7; Mar. 3, 2009, 17 pages.
International Search Report and Written Opinion for PCT/US2013/034765, Applicant: Box, Inc., dated Jan. 20, 2014, 15 pages.
Exam Report for EP13185269.1, Applicant: Box, Inc. dated Jan. 28, 7 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/039126 dated Oct. 6, 2011, pp. 1-13.
International Search Report and Written Opinion for PCT/US2011/041308 dated Jul. 2, 2012, pp. 1-16.
International Search Report and Written Opinion for PCT/US2011/056472 dated Jun. 22, 2012, pp. 1-12.
International Search Report and Written Opinion for PCT/US2011/060875 dated Oct. 30, 2012, pp. 1-10.
Internet Forums, http://web.archive.org/web/20100528195550/http://en.wikipedia.org/wiki/Internet_forums, Wikipedia, May 30, 2010, pp. 1-20.
Langfeld L. et al., “Microsoft SharePoint 2003 Unleashed,” Chapters 11 and 15, Jun. 2004, pp. 403-404, 557-561, 578-581.
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. 20, 2011 pp. 1-5.
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, Wikipedia, Mar. 20, 2009, pp. 1-6.
Conner, “Google Apps: The Missing Manual,” published by O'Reilly Media, May 27, 2008, 24 pages.
Cisco, “FTP Load Balancing on ACE in Routed Mode Configuration Example,” DocWiki, Jun. 2011, 7 pages.
Palmer, “Load Balancing FTP Servers,” BlogNav, Oct. 2008, 2 pages.
Wayback, “Wayback machine,” Wayback, Jun. 1, 2011, 1 page.
Extended Search Report for EP131832800, Applicant: Box, Inc. dated Aug. 25, 2014, 7 pages.
Extended Search Report for EP141509422, Applicant: Box, Inc. dated Aug. 26, 2014, 12pages.
Search Report for EP 13189144.2 Applicant: Box, Inc. dated Sep. 1, 2014, 9 pages.
Exam Report for GB1312874.9 Applicant: Box, Inc. dated Sep. 26, 2014, 2 pages.
Exam Report for GB1415126.0 Applicant: Box, Inc. dated Oct. 2, 2014, 8 pages.
Exam Report for GB1415314.2 Applicant: Box, Inc. dated Oct. 7, 2014, 6 pages.
Exam Report for GB1309209.3 Applicant: Box, Inc. dated Oct. 7, 2014, 3 pages.
Exam Report for GB1315232.7 Applicant: Box, Inc. dated Oct. 9, 2014, 5 pages.
Exam Report for GB1318789.3 Applicant: Box, Inc. dated Oct. 30, 2014, 6 pages.
Exam Report for GB1317393.5 Applicant: Box, Inc. dated Nov. 7, 2014, 6 pages.
Exam Report for GB1311417.8 Applicant: Box, Inc. dated Nov. 7, 2014, 2 pages.
Exam Report for GB1311421.0 Applicant: Box, Inc. dated Nov. 7, 2014, 4 pages.
Exam Report for GB1316682.2 Applicant: Box, Inc. dated Nov. 19, 2014, 6 pages.
Exam Report for GB1312095.1 Applicant: Box, Inc. dated Nov. 19, 2014, 5 pages.
Exam Report for GB1313559.5 Applicant: Box, Inc. dated 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. dated 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. dated Feb. 17, 2015, 6 pages.
Exam Report for GB1312264.3 Applicant: Box, Inc. dated Jan. 30, 2015, 5 pages.
Exam Report for GB1312874.9 Applicant: Box, Inc. dated Feb. 10, 2015, 7 pages.
Exam Report for GB1316685.5 Applicant: Box, Inc. dated Feb. 17, 2015, 5 pages.
Exam Report for EP 13185269.1, Applicant: Box, Inc. dated Feb. 13, 2015, 8 pages.
Exam Report for GB1316532.9 Applicant: Box, Inc. dated Mar. 27, 2015, 6 pages.
Burney, “How to Move Document from Your Computer to Your iPad and Back Again,” May 31, 2011, 3 pages.
“Understanding Metadata,” National Information Standards Organization, NISO Press, 2004, 20 pages.
International Search Report and Written Opinion for PCT/US2012/056955, Applicant: Box, Inc., dated Mar. 27, 2013, pp. 1-11.
International Search Report and Written Opinion for PCT/US2011/047530, Applicant: Box, Inc., dated Mar. 22, 2013, pp. 1-10.
International Search Report and Written Opinion for PCT/US2012/065617, Applicant: Box, Inc., dated Mar. 29, 2013, 9 pages.
International Search Report and Written Opinion for PCT/US2012/067126, Applicant: Box, Inc., dated Mar. 29, 2013, 10 pages.
International Search Report and Written Opinion for PCT/US2012/063041, Applicant: Box, Inc., dated Mar. 29, 2013, 12 pages.
International Search Report and Written Opinion for PCT/US2011/057938, Applicant: Box, Inc., dated Mar. 29, 2013, 10 pages.
Parr, “Google Docs Improves Commenting, Adds E-mail Notifications,” Apr. 16, 2011, mashable.com, pp. 1-6.
“Microsoft Office SharePoint 2007 User Guide,” Feb. 16, 2010, pp. 1-48.
Lars, “35 Very Useful Online Tools for Improving your project Management and Team Collaboration,” Apr. 31, 2010, tripwiremagazine.com, pp. 1-32.
International Search Report and Written Opinion for PCT/US2010/070366, Applicant: Box, Inc., dated Mar. 24, 2013, 10 pages.
“How-to Geek, How to Sync Specific Folders With Dropbox,” downloaded from the internet http://www.howtogeek.com, Apr. 23, 2013, 5 pages.
International Search Report and Written Opinion for PCT/US2013/020267, Applicant: Box, Inc., dated May 7, 2013, 10 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. dated May 26, 2014, 6 pages.
Exam Report for GB1308842.2, Applicant: Box, Inc. dated Mar. 10, 2014, 4 pages.
Exam Report for GB1312264.3, Applicant: Box, Inc. dated Mar. 24, 2014, 7 pages.
Exam Report for GB1314771.5, Applicant: Box, Inc. dated Feb. 17, 2014, 7 pages.
Exam Report for GB1318792.7, Applicant: Box, Inc. dated May 22, 2014, 2 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. dated 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. dated Feb. 7, 2014, 9 pages.
Search Report for EP13187217.8, Applicant: Box, Inc. dated Apr. 15, 2014, 12 pages.
Search Report for EP141509422, Applicant: Box, Inc. dated May 8, 2014, 7 pages.
Search Report for EP14151588.2, Applicant: Box, Inc. dated Apr. 15, 2014, 12 pages.
Search Report for EP14153783.7, Applicant: Box, Inc. dated Mar. 24, 2014, 7 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.
International Search Report and Written Opinion for PCT/US2013/034662, Applicant: Box, Inc., dated May 31, 2013, 10 pages.
Exam Report for GB1306011.6, Applicant: Box, Inc. dated Apr. 18, 2013, 8 pages.
Exam Report for GB1300188.8, Applicant: Box, Inc. dated May 31, 2013, 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.
Exam Report for EP13158415.3, Applicant: Box, Inc. dated Jun. 4, 2013, 8 pages.
International Search Report and Written Opinion for PCT/US2013/029520, Applicant: Box, Inc., dated Jun. 26, 2013, 10 pages.
International Search Report and Written Opinion for PCT/US2013/023889, Applicant: Box, Inc., dated Jun. 24, 2013, 13 pages.
International Search Report and Written Opinion for PCT/US2013/035404, Applicant: Box, Inc., dated Jun. 26, 2013, 13 pages.
U.S. Appl. No. 60/922,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. 12/260,533 (U.S. Pat. No. 8,326,814) Oct. 29, 2008 (Dec. 4, 2012) Methods and Systems for Open Source Integration.
U.S. Appl. No. 13/030,090 (U.S. Pat. No. 8,140,513) Feb. 17, 2011 (Mar. 20, 2012) Methods and Systems for Open Source Collaboration in an Application Service Provider Environment.
U.S. Appl. No. 13/412,549 (U.S. Pat. No. 9,583,619) Mar. 5, 2012 Methods and Systems for Open Source Collaboration in an Application Service Provider Environment.
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 On 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/274,268, filed Oct. 14, 2011 (Aug. 20, 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. 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 Updated 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 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 Metedata 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/656,136, filed Aug. 2, 2012 Load Balancing Secure Ftp Connections Among Multiple Ftp Servers.
U.S. Appl. No. 13/649,784, filed Oct. 11, 2012 Highly Available Ftp Servers for a Cloud-Based Service.
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. 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. 13/969,474 (U.S. Pat. No. 8,745,267) Aug. 16, 2013 (Jun. 3, 2014) Client-Server Fast Upload And Download Feedback Optimizers.
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. 14/056,899, filed Oct. 17, 2013 Remote Key Management In A Cloud-Based Environment.
U.S. Appl. No. 61/709,086, filed Oct. 2, 2012 Visibility, Access Control, Advanced 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, 2013 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,474, 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 Building, 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/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 ln Cloud-Based Collaboration Platforms.
U.S. Appl. No. 14/075,849, filed Nov. 8, 2013 Systems And Methods For Configuring Event-Based Automation ln 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/474,507, filed Sep. 2, 2014 High Availability Architecture For A Cloud-Based Concurrent-Access 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. dated 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.

Related Publications (1)

	Number	Date	Country
	20140082503 A1	Mar 2014	US

Provisional Applications (1)

	Number	Date	Country
	61701823	Sep 2012	US

System and method of a manipulative handle in an interactive mobile user interface

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

Agents

CPC

Field of Search

US

CPC

International Classifications

Term Extension

Abstract