Patent Application
20240176801
Static content such as audio/video files or email messages can be synced between a cloud server and a portable media player, or between a portable media player and a computer, for example. The syncing occurs when a new content arrives at the server, or when a user makes a request. Syncing can result in new content, updated content and/or deleted content.
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 systems and methods for folder synchronization and/or offline synchronization via a mobile platform of a web-based collaboration environment.
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 and/or a network 108. 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
In one embodiment, the host server 100 of the online or web-based collaboration environment provides platform and application independent methods and features for networked file access and editing by a remote device (e.g., by user devices 102). Specifically, the host server 100 and components residing on a client side (e.g., on a user device 102) enables a user to edit files or other work items on the host server 100 using their own choice of applications, or any application that is available on the device 102 they are using to access/edit the file, and regardless of the device 102 platform (e.g., mobile, or desktop or operating system).
Furthermore, the user can edit the file accessed from the host server 100 without the additional process of manually downloading and storing the file locally on the device 102. For example, the file may be ready for the user to edit locally without informing that the file is stored or prompting the user for a directory in which to store the file, to streamline the access/edit process to enhance user experience.
Functions and techniques disclosed for platform and/or application independent file access/editing are further described with reference to the components illustrated in the example of
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.
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 a organizational setting, multiple workspaces (e.g., workspace A, B C) can be created to support different projects or a variety of work flows. Each workspace can have its own associate work items. For example, work space A 205 may be associated with work items 215, work space B 225 can be associated with work items 235, and work space N can 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 can 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 can be associated with departments 212 and 216 and users shown as example user B 214.
Each user associated with a work space can generally access the work items associated with the work space. The level of access will depend on permissions associated with the specific work space, and/or with a specific work item. Permissions can 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) can 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.
Each of users 316, 318, and 320 can 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 can 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 can 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 can be accessed from the workspace 302 in accordance with the platform and/or application independent mechanisms disclosed herein, as further described with references to the examples of
For example, a notification of a download, access, read, write, edit, or uploaded related activities can 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.
For example, any given file initially stored on the host server 400 (e.g., in the repository 430) can be edited using any of the devices 402A-N, despite the differing platforms and operating systems. Furthermore, any given file stored on the host 400 can be edited or accessed using any device 402A-N, as long as each individual device has an application which can open/edit the file type of the requested file.
In general, the process of identifying a local application suitable for accessing a file requested from the host server 400 is streamlined and automatic, and can be performed without prompting the user. Since the local components on a local device is able to query or monitor the operating system of any of the devices 402A-N to identify one or more suitable applications (e.g., default application or preferred application) for the file type of the requested file. By communicating with the operating system, (e.g., by monitoring the OS through the API, registry, or other methods), the process for detecting a suitable application for each device is operating system (platform)-independent and application-independent, thus working with any of the devices 402A-N and any other types of devices running different operating systems, platforms, and/or having installed thereon different applications.
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 502, a synchronization request processor 505 having a permission manager 510 and a synchronization engine 515 having a change detector 520, a synchronization status manager 525, an offline synchronization engine 530, a synchronization conflict manager 535, a synchronization folder manager 540 and a synchronization device manager 545, for example. The host server 100 may also include an offline manager 550 having an offline content meta data updator 555 and an offline content modification module 560. One embodiment of the host server 100 further optionally includes a notification engine 565 having, for example, a feed stream updator 570, a recipient selector 575 and/or a notification preference module 580. Additional or less components/modules/engines can be included in the host server 100 and each illustrated component.
The network interface 502 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 400, through any known and/or convenient communications protocol supported by the host and the external entity. The network interface 502 can include one or more of a network adaptor card, a wireless network interface card (e.g., SMS interface, WiFi interface, interfaces for various generations of mobile communication standards including but not limited to 1G, 2G, 3G, 3.5G, 4G, LTE, etc.,), Bluetooth, a router, an access point, a wireless router, a switch, a multilayer switch, a protocol converter, a gateway, a bridge, bridge router, a hub, a digital media receiver, and/or a repeater.
As used herein, a “module,” “a manager,” a “handler,” a “detector,” an “interface,” a “processor,” a “tracker,” a “detector,” a “generator,” a “launcher,” a “selector,” an “updator,” or an “engine” includes a general purpose, dedicated or shared processor and, typically, firmware or software modules that are executed by the processor. Depending upon implementation-specific or other considerations, the module, manager, hander, or engine can be centralized or its functionality distributed. The module, manager, hander, or engine can include general or special purpose hardware, firmware, or software embodied in a computer-readable (storage) medium for execution by the processor. As used herein, a computer-readable medium or computer-readable storage medium is intended to include all mediums that are statutory (e.g., in the United States, under 35 U.S.C. 101), and to specifically exclude all mediums that are non-statutory in nature to the extent that the exclusion is necessary for a claim that includes the computer-readable (storage) medium to be valid. Known statutory computer-readable mediums include hardware (e.g., registers, random access memory (RAM), non-volatile (NV) storage, to name a few), but may or may not be limited to hardware.
The host server 100 can track a user's folders and its subfolders in a given work space and across work spaces. Through the web or mobile application, the user can specify which folders or subfolders to synchronize for access using a mobile device (e.g., via a mobile platform), for example, when the mobile device or the mobile application enabled by the mobile platform is offline. The host server 100 of the collaboration platform can track the user's selections (e.g., the user can select ‘favorite’ folders or sub-folders, or otherwise indicate one or more sub-folders and the content that are to be made available offline) and stores the preferences (e.g., managed by the offline synchronization engine 530 and/or the synchronization folder manager 540). The host server 100 can track folder-level and/or sub-folder level synchronization preferences across multiple users and multiple workspace, and/or across multiple work spaces for a given user.
When a request to synchronize with a mobile device is received (e.g., via the mobile platform deployed on the mobile device 600), the synchronization request processor 505 checks with the permission manager 510 to see whether the requesting device has the proper permission to access or synchronize a given folder/sub-folder, or to access a given work space having the content or folders to be synchronized. The request can be generated automatically by the mobile platform, at periodic intervals, or automatically whenever the mobile application is online. The request to synchronize can also be triggered by user request from the mobile device 600. The permission information may be embedded in the folder/sub-folder meta data in one embodiment. The permission manager 510 can examine the meta data of the selected folder/sub-folder and determine from the meta data whether the user of the mobile device has adequate privileges to access or synchronize the selected folder/sub-folder.
In one embodiment, the permission manager may allow an admin or a creator of a workspace, that includes folders or sub-folders that are collaborated on by a number of users, to specify the type of synchronization that is allowed. For example, some users can have bi-directional synchronization privileges that allow the users to download updated folders or sub-folders from the host server to their client devices, and upload updated folders or sub-folders from their client devices to the host server. Since bi-directional synchronization of collaborated folders or sub-folders can create conflicts, limiting the bi-directional synchronization privileges to select users can be advantageous. Alternately, the synchronization may be unidirectional, from the server to the client devices. In one implementation, a collaborated folder or sub-folder that is updated on the client device can be sent to the admin of the workspace for synchronization approval.
The offline manager 550 keeps track of the folders, sub-folders and the content therein that have been selected or provided for offline access via the offline content meta data updator 555 and the offline content modification module 560. The offline content meta data updator 555, for example, updates the meta data of the selected folder/sub-folder and/or the content therein to include an offline status, indicator or tag. The offline status, indicator or tag may be provided by the synchronization status manager 525 of the synchronization engine 515 in one embodiment. In one implementation, the offline content meta data updator 555 may also add to the folder/sub-folder meta data a time stamp indicating the date and time the folder/sub-folder was synchronized and provided for offline access.
The offline content modification module 560 includes one or more rules to determine whether a folder/sub-folder and content therein can be accessed or modified by other users or collaborators of the cloud-based collaboration platform. For example, in one implementation, the offline content modification module 560 may be configured to restrict other users of the collaboration platform from accessing or modifying the folder/sub-folder selected for offline access. In another implementation, one or more rules may be implemented by the offline content modification module 560 to manage folders/sub-folders that are provided for offline access. For example, a rule that allows a selected user or a group of users to modify the server copy of the folder/sub-folder provided for offline access may be implemented by the offline content modification module 560. Similarly, another rule that allows some users or collaborators only read/download access may be implemented by the offline content modification module 560. The implementation of one or more of the rules for allowing or restricting access, modification, and/or other actions on the folder/sub-folder selected for offline access can be customized by the user according to the user's preference. In one implementation, the user's preference for managing at the server folder/sub-folder selected for offline access may be stored in a preference setting database. The offline content modification module 560 may access the preference setting database to retrieve applicable rules configured by the user to manage the given folder/sub-folder at the server side.
The synchronization engine 530 performs the synchronization of the selected workspace or selected folder/sub-folder and all of the sub-folders within the selected folder. In one embodiment, the content in the selected folder and/or sub-folder are synchronized by detected changed content, for example, via the change detector 520. For example, in synchronization, the selected folder and its child/subfolders can be scanned by the synchronization engine 530 to detect changed content since the last synchronization. In one implementation, the change detector 520 examines the time stamp on the selected folder/sub-folder and/or content therein to determine if the folder/sub-folder has changed since it was last synchronized. The changed content can then be provided to the mobile device 600. The change detector 520 can also identify any new sub-folders within the selected folder and/or new content within the selected folder/sub-folder on the host server 100 based on the date and time of the last synchronization operation. If there is new content on the host server in a folder selected to be synchronized, or in a sub-folder, the new content may be synchronized with the user device/mobile device in its entirety. In one embodiment, synchronization of the selected folders/sub-folders may occur automatically whenever the user device/mobile device 600 goes online to enable offline access of the content in the selected folder. Alternately, the synchronization may occur upon user request, and/or when a new content is available for synchronization.
In one embodiment, the synchronization engine 515 includes a synchronization status manager 525 to keep track of the synchronization status of workspaces, folders, sub-folders and content therein. The synchronization status manager functions may be particularly important if the user has configured synchronization to occur on demand and not automatically whenever there is a new or updated content or when the mobile device 600 is online. When a request to provide selected folder/sub-folder for offline access is received by the host server 100, the synchronization engine 530 checks with the synchronization status manager 525 to determine whether the selected folder/sub-folder should be synchronized before marking the selected folder/sub-folder as being available for offline access. The synchronization status manager 525 compares the time stamp on a local copy of a folder/sub-folder in a mobile device and the time stamp on the copy of the folder/sub-folder in the host server. If the time stamp on the local copy and the host server copy are the same, the folder/sub-folder can be assigned a synchronization status such as “current” or “synced.” The selected folder/sub-folder can then be marked as being available for offline access, without having to perform a synchronization. If the synchronization status is “out of date,” i.e., either the host server or the mobile device has an updated copy of the folder/sub-folder, the offline synchronization engine 530 performs a synchronization operation such that both the host server and the mobile device can both have the most current folder/sub-folder.
When a mobile device 600 is online after being offline, offline folders/sub-folders may have been updated at the mobile device or the host server. In one implementation, an offline folder/sub-folder can be updated both at the host server and the mobile device by different users or collaborators, resulting in a conflict. The synchronization conflict manager 535 is responsible for determining, prior to performing a sync, whether the synchronization generates a conflict. The synchronization conflict manager 535 may, in one implementation, generate a notification regarding the conflict for the client device. In a further implementation, the synchronization conflict manager 535 may postpone synchronization of the folder/sub-folder in the event of conflict. In another implementation, the synchronization conflict manager 535 may assign the folder/sub-folder that generates a conflict when synchronized, a conflict status. The synchronization conflict manager 535 may further store the folder/sub-folder originating from the client device as a new version, and notify the client device of the conflict. In yet another implementation, the synchronization conflict manager 535 can evaluate the reason for conflict, and take an action accordingly. For example, if the reason for the conflict is addition of a comment, the synchronization conflict manager 535 can waive the conflict and synchronize the folder/sub-folder, while retaining the comment. By way of another example, the synchronization conflict manager 535 can also synchronize the folder/sub-folder with conflict status by merging the folders/sub-folders from the host server and the client device.
The synchronization folder manager 540 manages folder-level and/or sub-folder level synchronization preferences across multiple users and multiple workspaces, and/or across multiple work spaces for a given user. In one implementation, the synchronization preferences may be stored in a database accessible by the host server 100. Based on the synchronization preferences, the synchronization folder manager 540 can identify folders/sub-folders for synchronization. For example, in one implementation, a synchronization preference may indicate synchronization of folders/sub-folders one level up and one level below a selected folder/sub-folder. Based on the synchronization preference, the synchronization folder manager 540 examines the selected folder/sub-folder hierarchy and identifies folders/sub-folders for syncing by the offline synchronization engine 530. In another implementation, a synchronization preference may indicate syncing of all folders/sub-folders related to the selected folder/sub-folder. The synchronization folder manager 540 can then identify the related folders/sub-folders, screen the identified folders/sub-folders for changed content (e.g., via the change detector 520) and provide any of the identified folders/sub-folders having changed content to the offline synchronization engine 530 for synchronization with the client device. Various other synchronization preferences for identifying folders/sub-folders for syncing are contemplated.
In one embodiment, the synchronization engine 515 includes the synchronization device manager 545 for managing syncing of folders/sub-folders and/or content therein across multiple client devices running the web-based collaboration platform application. The synchronization device manager 545 manages device synchronization preferences set by the user. For example, the synchronization device manager 545 can register for synchronization one or more client devices specified by the user and coordinate syncing between the host server and the registered client devices. The synchronization device manager 545 may assist the synchronization request processor 505 having the permission manager 510 to accept requests for synchronization from any of the registered client devices. The synchronization device manager 545 may also assist the offline synchronization engine 530 to send synchronization packages (e.g., folders/sub-folders for syncing and/or offline access) to some or all of the registered client devices according to the synchronization preferences set up by the user.
One embodiment of the host server 100 includes the notification engine 565. The notification engine 565, can for example, update a feed stream to include an updated feed indicating that one or more folders/sub-folders have been uploaded, for example, via the feed stream updator 570. The users that are notified can be selected, for example, by the recipient selector 575, 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 folders/sub-folders is completed. For real-time updating, the notification engine 565 can utilize another server, or another engine in the same server which provides push functionality.
The notification engine 565 of the host server 100 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 the aforementioned application 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 565 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
The notification engine 565 includes a notification preference manager 580 that can determine the channel through which to notify selected users or recipients of an access request, a synchronization request, a synchronization completion, synchronization in progress, synchronization error, a download, a file edit/modification, a file save or upload (e.g., an upload request, completion of upload of a single item, multiple items, and/or a full upload request), and the like. The channels that are used can include, indicators via a user interface to the online collaboration environment, SMS, audio message, text-based messages, email, desktop application, RSS, and the like.
The user device 600 (e.g., the user device 102, 402A-N) shown in the examples of
The network interface 605 can be a networking module that enables the user device 600 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 605 can include one or more of a network adaptor card, a wireless network interface card (e.g., SMS interface, WiFi interface, interfaces for various generations of mobile communication standards including but not limited to 1G, 2G, 3G, 3.5G, 4G, LTE, etc.,), Bluetooth, a router, an access point, a wireless router, a switch, a multilayer switch, a protocol converter, a gateway, a bridge, bridge router, a hub, a digital media receiver, and/or a repeater.
As used herein, a “module,” “a manager,” a “handler,” a “detector,” an “interface,” a “processor,” a “tracker,” a “detector,” a “generator,” a “launcher,” a “selector,” an “updator,” or an “engine” includes a general purpose, dedicated or shared processor and, typically, firmware or software modules that are executed by the processor. Depending upon implementation-specific or other considerations, the module, manager, hander, or engine can be centralized or its functionality distributed. The module, manager, hander, or engine can include general or special purpose hardware, firmware, or software embodied in a computer-readable (storage) medium for execution by the processor. As used herein, a computer-readable medium or computer-readable storage medium is intended to include all mediums that are statutory (e.g., in the United States, under 35 U.S.C. 101), and to specifically exclude all mediums that are non-statutory in nature to the extent that the exclusion is necessary for a claim that includes the computer-readable (storage) medium to be valid. Known statutory computer-readable mediums include hardware (e.g., registers, random access memory (RAM), non-volatile (NV) storage, to name a few), but may or may not be limited to hardware.
The synchronization request manager 610 can generate, time, trigger automatic requests or process a user request to synchronize content accessible via the mobile platform on the user device 600 with content stored on the host server 100. In one embodiment, the synchronization request manager 610 sends periodic requests to synchronize some or all folders/sub-folders selected for syncing. These folders may be selected by the user of the user device 600, or other users of a given work space in which the folders reside. For example, an owner or admin of a given work space may specify or assign certain folders/subfolders to certain users to be accessible offline via the mobile platform. In one implementation, the syncing may be triggered when a user selects one or more folders/sub-folders or other content for offline access via the offline manager 615.
In one embodiment, the synchronization request manager 610 can also receive and process synchronization requests or notification from the host server 100. For example, the host server 100 determines whether any folders/sub-folders have changed or if any of the folders/sub-folders for synchronization include new or updated content. If so, the user device 600 (e.g., the synchronization request manager 610) is notified. The synchronization request manager 610 receiving the notification can display an indication of availability of an update and additionally, may prompt the user for confirmation prior to performing the synchronization via the folder synchronization module 620.
In one embodiment, the offline manager 615 can allow or facilitate selection of certain folders, sub-folders or other content for offline access. In one implementation, one or more of the selected folders, sub-folders or other content can be modified while the user device 600 is offline. A user of the user device 600 can make this selection by selecting the content or folders to be synced or otherwise available offline through the mobile platform/application on the mobile device 600, or via the web-based application accessed via a web-portal.
A synchronization event, when triggered at the user device 600, can include a request to synchronize a given folder, a given sub-folder, or all folders selected for synchronization or offline access. To synchronize a folder in this request, the folder synchronization module 620 automatically identifies all sub-folders of any folder included in the request. The identification of sub-folders and folders can then be sent to the host server 100 such that the request can be satisfied. In one implementation, along with the identification of sub-folders and folders, other folder/sub-folder meta data such as time stamp on the folder/sub-folder may also be sent to the host server 100. For example, when the selected folders/sub-folders are locally stored in the user device, the host server 100 can use the time stamp information to determine whether the locally stored folders/sub-folders the out of date or not.
In one embodiment, the application identifier 625 also facilitates identification of folders and sub-folders. In some instances or certain mobile operating systems, each application is associated with its own folders/sub-folders for content generated using the application or other supporting files. In the cases where one application does not have access to files/folders of other applications, the application identifier 625 can be used to identify the relevant or related folders/subfolders/child-folders for synchronization purposes. For example, by identifying the application used to open or modify content or a given file, the related folder/folders can be identified for synchronization.
The offline status manager 630 accords an offline status to the folders and sub-folders selected for offline access or modification. The offline status can be provided by, for example, modifying meta data associated with the selected folders/sub-folders. In one implementation, the offline status manager 630 can confer offline status to other folders, sub-folders or content items that are not directly selected by the user, but are identified by, for example, the folder synchronization module 620 for synchronization. In one implementation, the offline status of the folders and sub-folders may be used to select and display all folders/sub-folders available for offline access and/or modification in a separate folder or display area of a user interface provided by the user device 600.
The offline change detector module 635 detects change or modification to any of the folders, sub-folders or other content items selected for offline access or modification. The change that is detected includes, for example, changes to folder hierarchy, addition of sub-folders, or other content, change in the folder/sub-folder content, and the like. The change may be detected based on screening of the selected folders, sub-folders or other content items in one implementation. Alternately, the time stamp on the selected folders, sub-folders or other content items may be examined to detect change. The offline change detector module 635 can also detect change to the folders and sub-folders identified by the folder synchronization module 620. In one embodiment, some or all of the functions of the offline change detector module 635 can be performed by, for example, the change detector module 520 in the synchronization engine 515 in the host server 100.
The access monitoring module 640 monitors access history associated with folders and sub-folders selected for offline access. The access reporting module 645 can report the access history aggregated by the access monitoring module 640 to the host server 100. In one implementation, the access history may be reported as a part of the meta data associated with the selected folders and sub-folders that is provided to the host server 100, at the time of synchronization. Access history can include a record of actions such as access, preview, modify, email, print, comment, annotate, and the like, and in some implementations, date/time an action is performed, the length of time for each action, and the like.
The user preference module 650 includes user interfaces for obtaining from the user of the user device 600 preferences relating to various synchronization processes. The user preference module 650 further manages and communicates to the host server 100 the preferences for various synchronization processes. For example, the user preference module 650 allows the user to customize the synchronization request manager 610 to generate requests for syncing on demand, automatically upon receiving a trigger from the offline change detector module 635, periodically or whenever the user device 600 is online. The user preference module 650 may also allow the user to define criteria for identifying folders, sub-folders or other content items related to folders and sub-folders selected for offline access. The user preference module 650 may also allow the user to create and/or select one or more rules for allowing or restricting access, modification, and/or other actions on the selected folder/sub-folder at the host server. The user preference module 650 further allows the user to specify synchronization preferences for various components of the host server 100 such as, the synchronization folder manager 540, notification preference for the notification preference manager 580, synchronization device preferences for the synchronization device manager 545, and the like.
Although not discussed, the user device may also include other components. Furthermore, some or all of the processes described above with respect to the user device components can, in part or in whole, implemented on the host server (e.g., the host server 100). Some of the processes implemented by the host server may be in lieu of or in duplicate with those able to be performed by the components described herein with respect to the user device 600.
Alternately, the mobile device may have no local copy of the selected folder or sub-folder, or based on the time stamp comparison, the selected folder or sub-folder on the mobile device may not match the one on the host server. If so, at decision block 715, the host server determines that a synchronization should be performed. At decision block 720, the host server determines whether the selected folder or sub-folder on the mobile device or the host server is out of date based on the time stamp. For example, if the time stamp on the selected folder or sub-folder at the host server is more recent, then the mobile device is out of sync. At block 735, the host server sends the selected folder or sub-folder to the mobile device.
If, on the other hand, the time stamp on the selected folder or sub-folder at the mobile device is more recent, then the host server is out of sync. At block 725, the host server requests the mobile device to upload the selected folder or sub-folder to the host server. The upload may be performed automatically in the background in one implementation. In another implementation, the user of the mobile device may be requested to allow syncing with the host server. At block 730, the host server receives the selected folder or sub-folder from the mobile device and replaces the out of date folder or sub-folder on the server with the one obtained from the mobile device.
At block 830, the host server identifies folders and/or sub-folders marked for offline access or having an offline access status. At block 835, the host server examines the identified folders and/or sub-folders for changed content or new content. The host server also examines any child or sub-folders in the hierarchy of the identified folders and/or sub-folders for changed content or new content. In one implementation, the child or sub-folders in the hierarchy may be identified at the time of assigning offline access status to user selected folders and/or sub-folders, such that the child or sub-folders can also be marked as having offline status.
At decision block 840, the host server determines if there is any changed content or new content in the folders and/or sub-folders marked for offline access and any child or sub-folders thereof. In one implementation, any change in the folders, sub-folders and/or child folders are determined based on the current time stamp and last synchronization date and time. For example, a folder and/or a sub-folder includes changed content if the time stamp on the folder and/or the sub-folder is more recent than the last synchronization date. If there is a changed content, the host server can send an update available notification to the mobile device at block 845. In one implementation, the host server can send identification of the folders and/or sub-folders and content therein that have changed content. The host server then waits for a synchronization request from the user to download the changed folders and/or sub-folders. Alternately, the host server can select and download changed folders and/or sub-folders to the mobile device at block 850, and provide a synchronization completed notification to the mobile device. The block 850 option may be implemented based on user preference.
At decision block 840, if the host server determines that there is a new content in any of the folders and/or sub-folders having offline access status, the host server sends a new content available notification to the mobile device at block 855. In one implementation, the notification can include identification of folders and/or sub-folders having the new content. The host server downloads the folder and/or sub-folder with the new content upon receiving a synchronization request from the user. Alternately, the host server can download the folder/sub-folder having the new content to the mobile device at block 860. The block 860 option may be implemented based on user preference.
In one embodiment, the host server may not differentiate between new content and changed content, in which case, blocks 845 and 855 and blocks 850 and 860 may be consolidated. At decision block 840, if the host server determines that there is no changed or new content, the host server skips the synchronization operation at block 865.
For example, user interface 900 of
When files or folders are selected (e.g., ‘favorited’) for offline access, the mobile application can automatically synchronize the file or contents of the selected folders with or without prompting the user when in the presence of a network connection (e.g., cellular or Wifi). This process can be performed automatically such that the file/folder is available and is updated when the user next accesses them.
For example, user interface 1300 of
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 disk drives, 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 2800 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, 16, 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, 16 will begin with the words “means for”.) Accordingly, the applicant reserves the right to add additional claims after filing the application to pursue such additional claim forms for other aspects of the disclosure.
The present application is a continuation of U.S. application Ser. No. 18/058,511, filed Nov. 23, 2022, which is a continuation of U.S. patent application Ser. No. 17/163,909, filed Feb. 1, 2021, now U.S. Pat. No. 11,537,630, which is a continuation of U.S. patent application Ser. No. 15/685,111, filed Aug. 24, 2017, now U.S. Pat. No. 10,909,141, which is a continuation of U.S. patent application Ser. No. 13/689,544, filed Nov. 29, 2012, now U.S. Pat. No. 9,773,051, which claims priority and the benefit of U.S. Provisional Patent Application Ser. No. 61/564,425 titled “Mobile Platform Folder Synchronization And Offline Synchronization”, filed on Nov. 29, 2011; and U.S. Provisional Patent Application Ser. No. 61/568,430 titled “Mobile Platform File and Folder Selection Functionalities For Offline Access and Synchronization”, filed on Dec. 8, 2011. The entire content of the aforementioned applications are expressly incorporated by reference herein.
| Number | Date | Country | |
|---|---|---|---|
| 61564425 | Nov 2011 | US | |
| 61568430 | Dec 2011 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 18058511 | Nov 2022 | US |
| Child | 18499005 | US | |
| Parent | 17163909 | Feb 2021 | US |
| Child | 18058511 | US | |
| Parent | 15685111 | Aug 2017 | US |
| Child | 17163909 | US | |
| Parent | 13689544 | Nov 2012 | US |
| Child | 15685111 | US |
