Source: http://patents.com/us-9838985.html
Timestamp: 2017-12-15 12:26:29
Document Index: 469321470

Matched Legal Cases: ['art 1', 'art 2', 'art 1', 'art 2', 'art 3', 'Application No. 60']

US Patent # 9,838,985. User-input scheduling of synchronization operation on a mobile device based on user activity - Patents.com
United States Patent 9,838,985
Vargas , et al. December 5, 2017
Vargas; Sandra I (Sammamish, WA), Williamson; David R (Duvall, WA), Hall; Gary W (Redmond, WA), Foster; Michael A (Redmond, WA), Balducci; Juan V. Esteve (Issaquah, WA)
Family ID: 1000002992748
14/691,059
US 20150230192 A1 Aug 13, 2015
13930525 Jun 28, 2013 9037173
13369725 Aug 13, 2013 8509830
13173242 Mar 20, 2012 8140099
12872579 Aug 9, 2011 7996028
10641380 Oct 5, 2010 7809384
60424177 Nov 5, 2002
Current CPC Class: H04W 56/00 (20130101); G06F 17/30575 (20130101); H04L 67/1095 (20130101); H04N 21/4126 (20130101); H04L 29/06 (20130101); H04L 69/329 (20130101)
Current International Class: H04W 56/00 (20090101); H04L 29/06 (20060101); H04L 29/08 (20060101); G06F 17/30 (20060101); H04N 21/41 (20110101)
6553409 April 2003 Cohen et al.
6874037 March 2005 Beckwitt et al.
7016710 March 2006 Carmeli et al.
7032003 April 2006 Shi et al.
7194551 March 2007 Moll et al.
7571194 August 2009 Mettala et al.
7809384 October 2010 Vargas et al.
7996028 August 2011 Vargas et al.
8140099 March 2012 Vargas et al.
8509830 August 2013 Vargas et al.
2002/0159416 October 2002 Kazmi et al.
2002/0177442 November 2002 Nagashima
2003/0084108 May 2003 Syed
2003/0220966 November 2003 Hepper et al.
Matrianni, Steven J., "A Location Management and Data Synhcronization Application for Mobile Computing", A Thesis Presented to the Faculty of the School of Computer Science, Kennedy-Western University, Sep. 2000, 212 pages. cited by applicant .
Prosecution History from U.S. Appl. No. 13/369,725 including: Issue Notification dated Jul. 24, 2013, Response to Amendment dated Jul. 15, 2013, Amendment dated Jun. 26, 2013, Office Communication dated Jun. 5, 2013, Interview Summary dated Jun. 3, 2013, Notice of Allowance dated Apr. 3, 2013, Terminal Disclaimer Review Decision dated Feb. 8, 2013, Amendment dated Feb. 4, 2013, Non-Final Office Action dated Nov. 20, 2012, Response to Notice to File Corrected Application Papers dated Jun. 5, 2012, Part 1 of 2. cited by applicant .
Prosecution History from U.S. Appl. No. 13/369,725 including: Notice of Incomplete Reply dated May 14, 2012, Response to Notice to File Corrected Application Papers dated May 3, 2012, Notice to File Corrected Application Papers dated Mar. 6, 2012, and Application and Drawings filed Feb. 9, 2012, Part 2 of 2. 98 pages. cited by applicant .
Prosecution History from U.S. Appl. No. 13/173,242 including: Issue Notification dated Feb. 29, 2012, Notice of Allowance dated Dec. 30, 2011, Terminal Disclaimer Review Decision dated Dec. 6, 2011, Amendment dated Nov. 8, 2011, Non-Final Office Action dated Sep. 30, 2011, and Application and Drawings filed Jun. 30, 2011, 69 pages. cited by applicant .
Prosecution History from U.S. Appl. No. 12/872,579 including: Issue Notification dated Jul. 20, 2011, Notice of Allowance dated May 19, 2011, Terminal Disclaimer Review Decision dated May 13, 2011, Amendment dated Mar. 25, 2011, Non-Final Office Action dated Jan. 6, 2011, Response to Notice to File Corrected Application Papers dated Nov. 8, 2010, Notice to File Corrected Application Papers dated Sep. 15, 2010, and Application and Drawings filed Aug. 31, 2010. 88 pages. cited by applicant .
Prosecution History from U.S. Appl. No. 10/641,380 including: Issue Notification dated Sep. 16, 2010, Notice of Allowance dated Jun. 3, 2010, Supplemental Amendment dated May 25, 2010, Supplemental Amendment dated May 17, 2010, Amendment dated Mar. 9, 2010, Non-Final Office Action dated Jan. 4, 2010, Amendment dated Oct. 29, 2009, Non-Final Office Action dated Aug. 6, 2009, Amendment dated May 1, 2009, Office Action dated Feb. 3, 2009, Amendment dated Nov. 7, 2008, Part 1 of 3. cited by applicant .
Prosecution History from U.S. Appl. No. 10/641,380 including: Advisory Action dated Oct. 8, 2008, Response After Final dated Aug. 8, 2008, Final Office Action dated May 8, 2008, Amendment dated Feb. 15, 2008, Notice of Non-Compliant Amendment dated Feb. 11, 2008, Amendment dated Jan. 29, 2008, Non-Final Office Action dated Nov. 8, 2007, Response After Final dated Oct. 18, 2007, Notice of Appeal dated Oct. 19, 2007, Final Office Action dated Jul. 26, 2007, Amendment dated Apr. 16, 2007, Part 2 of 3. cited by applicant .
Prosecution History from U.S. Appl. No. 10/641,380 including: Non-Final Office Action dated Jan. 16, 2007, Notice to File Corrected Application Papers dated Nov. 12, 2003, and Application and Drawings filed Aug. 14, 2003, Part 3 of 3. 317 pages. cited by applicant .
Prosecution History from U.S. Appl. No. 13/930,525 including: Notice of Allowance dated Feb. 20, 2015, Response to Informational Notice to Applicant dated Oct. 23, 2014, Notice of Allowance dated Oct. 14, 2014, Response to Informational Notice to Applicant dated Oct. 10, 2014, Terminal Disclaimer Review Decision dated Sep. 8, 2014, Amendment dated Sep. 5, 2014, Non-Final Office Action dated Jun. 10, 2014, Informational Notice to Applicant dated Jul. 25, 2013, Application and Drawings filed Jun. 28, 2013, 86 pages. cited by applicant.
The present application is a continuation of U.S. patent application Ser. No. 13/930,525, filed Jun. 28, 2013, which is a continuation of U.S. patent application Ser. No. 13/369,725, filed Feb. 9, 2012, now U.S. Pat. No. 8,509,830, issued Aug. 13, 2013, which is a continuation of U.S. patent application Ser. No. 13/173,242, filed Jun. 30, 2011, now U.S. Pat. No. 8,140,099, issued Mar. 20, 2012, which is a continuation of U.S. patent application Ser. No. 12/872,579, filed Aug. 31, 2010, now U.S. Pat. No. 7,996,028, issued Aug. 9, 2011 which is a continuation of U.S. patent application Ser. No. 10/641,380, filed Aug. 14, 2003, now U.S. Pat. No. 7,809,384, issued Oct. 5, 2010, which is based on and claims the benefit of U.S. Provisional Patent Application No. 60/424,177, filed Nov. 5, 2002, the contents of each of which are hereby incorporated by reference in their entireties.
1. A mobile device, comprising: a processing unit; and a memory coupled to the processing unit and storing instructions that, when executed by the processing unit, perform a method, comprising: determining a status of the mobile device; and perform a synchronization operation based on the determined status of the mobile device and a previous synchronization performed by the mobile device.
2. The mobile device of claim 1, wherein the status of the mobile device is based, at least in part, on a determination that the mobile device is in a roaming state.
3. The mobile device of claim 1, wherein the synchronization operation synchronizes data between the mobile device and a computing device using a wireless communication interface.
4. The mobile device of claim 3, wherein the status of the mobile device is based, at least in part, on a state of the wireless communication interface.
5. The mobile device of claim 1, further comprising instructions for accessing scheduling information that defines when the synchronization operations is to be performed.
6. The mobile device of claim 5, further comprising instructions for performing the synchronization operation based on the status of the mobile device relative to the scheduling information.
7. The mobile device of claim 1, further comprising instructions for generating a user interface display having at least one input mechanism that receives input that defines at least one synchronization parameter associated with the synchronization operation.
8. The mobile device of claim 7, wherein the synchronization parameter defines when synchronization operations are to be performed based, at least in part, on the status of the mobile device.
9. The mobile device of claim 8, wherein the synchronization parameter defines a synchronization frequency.
10. The mobile device of claim 7, wherein the synchronization parameter defines when synchronization operations are to be performed for a plurality of different mobile device statuses.
11. The mobile device of claim 10, wherein the synchronization parameter defines a synchronization frequency for each different mobile device status.
12. The mobile device of claim 1, further comprising instructions for performing the synchronization operation according to an override criterion.
13. The mobile device of claim 1, further comprising instructions for: determining whether the synchronization operation has been interrupted or has failed; and in response to the determination, implementing a retry procedure for retrying the synchronization operation.
14. A mobile device, comprising: a processing unit; and a memory coupled to the processing unit and storing instructions that, when executed by the processing unit, perform a method, comprising: obtaining a first time value indicative of a time for performing a next synchronization operation and a second time value indicative of an end of a previous synchronization operation; scheduling the next synchronization operation based on the first and second time values; and performing the next synchronization operation when the first time value is satisfied.
15. The mobile device of claim 14, wherein the first time value indicates a prescribed time period between synchronization operations.
16. The mobile device of claim 15, further comprising instructions for scheduling the next synchronization operation such that the next synchronization operation occurs at the prescribed time period after the end of the previous synchronization operation.
17. A mobile device, comprising: a processing unit; and a memory coupled to the processing unit and storing instructions that, when executed by the processing unit, perform a method, comprising: generating a user interface display that receives an input defining a set of operations on the mobile device for which synchronization operations are to be performed; identifying an occurrence of an operation in the set of operations; and performing a synchronization operation based the occurrence of the operation.
18. The mobile device of claim 17, further comprising instructions for: displaying a plurality of available operations; and receiving input that selects the set of operations from the displayed plurality of operations.
19. The mobile device of claim 17, further comprising instructions for: identifying a time delay; and performing the synchronization operation based on the time delay.
20. The mobile device of claim 17, further comprising instructions for displaying at least one synchronization parameter associated with the synchronization operation.
While a wide variety of computing tasks and applications can be performed by such mobile devices, personal information managers (PIMs) are particularly well suited to mobile devices. PIMs typically comprise applications which enable the user of the mobile device to better manage scheduling and communications, and other such tasks. Some commonly available PIMs include scheduling and calendar programs, task lists, address books, and electronic mail (e-mail) programs. Some commonly commercially available PIMs are sold under the trademarks "MICROSOFT SCHEDULE+" and "MICROSOFT OUTLOOK" and are commercially available from Microsoft Corporation of Redmond, Wash. In addition to PIMs, however, such mobile devices may also run different types of applications, such as word processors, spread sheets, etc.
Object stores 20 and 32 are implemented in memory configured to store a plurality of individual records or objects, each comprising a plurality of fields or properties related to PIMs 16 and 28. In one illustrative embodiment, PIMs 16 and 28 are programs, such as that available under the commercial designation "MICROSOFT OUTLOOK", and object stores 20 and 23 are configured to store objects, each of which having a plurality of attributes or properties associated with electronic mail messaging, such as a sender's name, the recipient's name, text messages, etc. Computing device 14 executes PIM 28 to maintain objects stored in store 32, and mobile device 12 executes program 16 to maintain objects stored in object store 20. In one illustrative embodiment, each object in object store 20 comprises the same set of properties or attributes stored in object store 32, or a subset of those properties or attributes.
Similarly, application programs 18 and 30 maintain objects on associated object stores 22 and 34, respectively. In one illustrative embodiment, application programs 18 and 30 are file system applications, such as those available under the commercial designation "MICROSOFT WORD". It should also be noted that any suitable number of other application programs, and associated object stores, can be provided on mobile device 12 and computing device 14. However, for the sake of simplicity, only programs 16, 18, 28 and 30, and their associated object stores, are described herein.
Dynamically linked libraries (DLLs), comprising a plurality of executable functions are associated with PIM 28 and application 30 for execution by processor 62. Interprocessor and intercomponent calls are facilitated preferably using the component object model (COM) as is common in programs written for Microsoft "WINDOWS" brand operating systems. Briefly, when using COM, a software component such as a DLL has a number of interfaces. Each interface exposes a plurality of methods, which can be called individually to utilize different services offered by the software component. In addition, interfaces are provided such that methods or functions can be called from other software components which optionally receive and return one or more parameter arguments.
Wireless network port 608 and wireless network driver 618 provide communication to a network over a radio channel. Wireless network port 608 and driver 618 can use any number of wireless network protocols including General Packet Radio Service (GPRS) and 1Xrtt, which are wireless services used to provide cellular access to a network, as well as 802.11 and 802.11b (Wi-Fi) protocols, and Bluetooth.TM. protocol, which provide local wireless connections to networks. Of course, others can be used as well.
(a) Each handle may contain data that uniquely identifies an object-such as an object identifier, an ID number, a full pathname for a file system object, etc. This data may be persistent (in that it does not change for a particular object) and should not be reused for subsequently created objects. This data can be compared to determine whether two handles actually correspond to the same object. As is discussed below, this can be problematic for file system information, because the object identifier is typically the pathname, and can be changed simply by renaming the file.
FIGS. 11-12C illustrate an embodiment of the present invention in which these actions can be used to initiate a synchronization operation. First, the user takes an action which triggers a synchronization operation. This is indicated by block 1000. As mentioned, these actions will likely be a preselected subset of actions which the user can take on the mobile device, and may be those actions which generate an outgoing electronic mail message, or identify information to be downloaded.
It is next determined whether the real time response feature that automatically initiates a synchronization operation based on these actions (rather than waiting for the next scheduled sync operation) is active. This is indicated by block 1002. FIGS. 12A-12C illustrate different user interfaces which allow the user to select the real time response feature. FIG. 12A is similar to FIG. 9, except that it also includes a box labeled "Sync outgoing items as they are sent". This is designated by number 1100 in FIG. 12A. If the user checks this box, then synchronization operations are initiated when the user takes any of the predetermined subset of actions that trigger a real time response synchronization operation. FIG. 12B is simply a different embodiment of a user interface but also contains the check box 1100, as does the user interface indicated in FIG. 12C.
Previous Patent US 9,838,984 | Next Patent US 9,838,986