Source: https://patents.justia.com/patent/10162983
Timestamp: 2019-06-17 04:52:10
Document Index: 30832979

Matched Legal Cases: ['Application No. 60', 'Application No. 12190992', 'Application No. 12190992', 'Application No. 08706234', 'Application No. 08706234', 'Application No. 8706234', 'application No. 12190992']

US Patent for Selectively wiping a remote device Patent (Patent # 10,162,983 issued December 25, 2018) - Justia Patents Search
Justia Patents Remote Programming ControlUS Patent for Selectively wiping a remote device Patent (Patent # 10,162,983)
Mar 31, 2017 - BLACKBERRY LIMITED
This application is a continuation of U.S. application Ser. No. 14/816,271, filed Aug. 3, 2015, which is a continuation of U.S. application Ser. No. 13/245,061, filed Sep. 26, 2011, which is a continuation of U.S. application Ser. No. 12/016,723, filed Jan. 18, 2008, which claims priority from U.S. Application No. 60/885,796, filed Jan. 19, 2007, the entireties of which are incorporated herein by reference.
In the example of FIG. 4b, further rules are provided for the user/administration authorization levels 1, 2, and 4 (DataWipeAuthLevel1=00000000111100, DataWipeAuthLevel2=0000001111110, and DataWipeAuthLevel4=00111111111111, respectively); in this embodiment, the client device 10, 100 is configured to implement the IT policy 361 such that if a rule for a given authorization level is missing from the IT policy 361, then the rule in effect for the next available lower authorization level is enforced for that missing authorization level. Thus, in this example, a wipe command issued by a user/administrator with an authorization level of 3 would be governed by the DataWipeAuthLevel2=00000011111100 rule. It can be seen that in this particular example, which is not intended to be limiting concerning the formatting of rules or flag values, only those users/administrators with an authorization level of 3 are capable of issuing a wipe command that will wipe the IT policy data 315 and the key data 302. It will be appreciated that the execution of the wipe command will generally follow the same process as that described in respect of FIG. 4a. When the user device 10, 100 sets the flag at step 520 of FIG. 6, it will locate the appropriate rule in the IT policy 361 according to the authorization level indicator detected in the received wipe command; then, if the value provided in the rule is in the appropriate format, the client device 10, 100 may utilize that value directly as the flag value in the subsequent execution of the wipe command in step 530.
1. A method of securing data on a client device, the client device storing data of a plurality of data types, the method comprising:
creating, at the server, a securing command for securing at least one data type based on the determined authorization level associated with the command issuer by: determining that a subset of data types in the plurality of data types is available to be secured based on the determined authorization level associated with the command issuer; receiving a selection of the at least one data type from the determined subset of data types; and generating the securing command for securing the at least one data type from the subset of data types; and
sending the securing command from the server to the client device.
2. The method of claim 1, wherein the selection includes selecting the at least one data type based on received command issuer input.
3. The method of claim 1, wherein the securing includes deleting the at least one data type.
4. The method of claim 1, wherein the securing includes encrypting the at least one data type.
5. The method of claim 1, wherein the command issuer is a user, and wherein the at least one data type is personal data associated with the user.
6. The method of claim 5, wherein a second data type is not a data type in a subset of data types available to be secured, and wherein the second data type is not associated with the created securing command.
7. The method of claim 1, wherein the command issuer is an administrator, and wherein the at least one data type is not personal data.
9. The method of claim 1, wherein the at least one data type includes message data.
10. The method of claim 1, wherein the at least one data type includes applications, or data files created at the client device or received at the client device that are personal to a user.
11. The method of claim 1, wherein the at least one data type is not user-created data, and wherein creating the securing command for securing the at least one data type includes:
determining that the determined authorization level associated with the command issuer is an administrator authorization level to secure data that is not user-created data but preventing the command issuer from securing user-created data.
create a securing command for securing at least one data type based on the determined authorization level associated with the command issuer by: determining that a subset of data types in the plurality of data types is available to be secured based on the determined authorization level associated with the command issuer; receiving a selection of the at least one data type from the determined subset of data types; and generating the securing command for securing the at least one data type from the subset of data types; and
send the securing command from the server to a client device.
13. The server of claim 12, wherein the selection includes the processor being configured to select the at least one data type based on a received selection from the command issuer.
14. The server of claim 12, wherein the securing includes deleting the at least one data type.
15. The server of claim 12, wherein the securing includes encrypting the at least one data type.
16. The server of claim 12, wherein the command issuer is a user, and wherein the at least one data type is personal data associated with the user.
17. The server of claim 16, wherein a second data type is not a data type in a subset of data types available to be secured, and wherein the second data type is not associated with the created securing command.
18. The server of claim 12, wherein the command issuer is an administrator, and wherein the at least one data type is not personal data.
19. The server of claim 18, wherein a second data type is personal data, and wherein the second data type is not associated with the created securing command.
creating a securing command for securing at least one data type based on the determined authorization level associated with the command issuer by: determining that a subset of data types in the plurality of data types is available to be secured based on the determined authorization level associated with the command issuer; receiving a selection of the at least one data type from the determined subset of data types; and generating the securing command for securing the at least one data type from the subset of data types; and
sending the securing command from the server to a client device.
5150407 September 22, 1992 Chan
5901285 May 4, 1999 Labatte et al.
6160873 December 12, 2000 Troung et al.
6167519 December 26, 2000 Sonobe
6292898 September 18, 2001 Sutherland
7113912 September 26, 2006 Stefik et al.
7159120 January 2, 2007 Muratov et al.
7216110 May 8, 2007 Ogg et al.
7543160 June 2, 2009 Adams et al.
7788487 August 31, 2010 Ito et al.
8012219 September 6, 2011 Mendez et al.
8042189 October 18, 2011 Little et al.
8056143 November 8, 2011 Brown et al.
8676273 March 18, 2014 Fujisaki
8696765 April 15, 2014 Mendez et al.
9083707 July 14, 2015 Mendez et al.
9672371 June 6, 2017 Mendez et al.
9965643 May 8, 2018 Mendez et al.
20010045884 November 29, 2001 Barrus et al.
20020002685 January 3, 2002 Shim
20020143961 October 3, 2002 Siegel et al.
20030023561 January 30, 2003 Stefik et al.
20030139175 July 24, 2003 Kim
20030191955 October 9, 2003 Wagner et al.
20040025053 February 5, 2004 Hayward
20040124975 July 1, 2004 Fujiwara et al.
20040181673 September 16, 2004 Lin et al.
20050039001 February 17, 2005 Hudis et al.
20050138109 June 23, 2005 Redlich
20050227729 October 13, 2005 Nakayama
20050278793 December 15, 2005 Raley et al.
20060125112 June 15, 2006 Ikeya et al.
20060236126 October 19, 2006 Adams et al.
20060265328 November 23, 2006 Yasukura
20070015490 January 18, 2007 Munje
20070035390 February 15, 2007 Thomas et al.
20070056043 March 8, 2007 Onyon
20070094463 April 26, 2007 Brown et al.
20070094471 April 26, 2007 Shaath et al.
20070199075 August 23, 2007 Skoric et al.
20080113649 May 15, 2008 Ibacache
20080141337 June 12, 2008 Yeung
20080148042 June 19, 2008 Brown
20090036157 February 5, 2009 Mackie
20130031595 January 31, 2013 Nevstruev et al.
20130091564 April 11, 2013 Fitzgerald et al.
2388117 December 2002 CA
2495083 January 2008 CA
0899647 March 1999 EP
1320010 June 2003 EP
1535159 January 2005 EP
1585007 October 2005 EP
1633155 March 2006 EP
2375336 June 2013 EP
2955896 October 2017 EP
2004001619 December 2003 WO
2004015576 February 2004 WO
2006044746 April 2006 WO
2006125112 November 2006 WO
WO2006/125112 November 2006 WO
EPO, Extended European Search Report relating to Application No. 12190992.3, dated Feb. 13, 2013.
EPO, Replacement Extended European Search Report relating to Application No. 12190992.3, dated Mar. 4, 2013.
International Search Report dated Jun. 14, 2006 in WO2006/044746.
Brown et al.: “Mastering Lotus Notes”, Lotus Books, Lotus Development Corporation.
Menezes A.J. et al.: “Hash Functions and Data Integrity”, Jan. 1, 1997, Handbook of Applied Cryptography; [CRC Press Series on Discrete Mathematics and its Applications], pp. 321-383, XP002275660.
EPO, Supplementary European Search Report relating to Application No. 08706234, dated Mar. 12, 2010.
EPO, Examination Report relating to Application No. 08706234.5, dated Oct. 28, 2010.
USPTO, U.S. Office Action relating to U.S. Appl. No. 13/245,061, dated Jan. 22, 2015.
EPO, EP Examination Report relating to Application No. 8706234.5, dated Aug. 8, 2012.
USPTO, U.S. Final Office Action relating to U.S. Appl. No. 13/245,061, dated Jan. 22, 2015.
USPTO, U.S. Final Office Action relating to U.S. Appl. No. 14/816,271, dated Sep. 28, 2016.
EP Office Action dated May 8, 2018.
EPO, EP application No. 12190992.3, Communication pursuant to Article 94(3) EPC dated May 8, 2018.
Patent Publication Number: 20170206378
Primary Examiner: Shin-Hon (Eric) Chen
Application Number: 15/475,901
International Classification: H04L 29/06 (20060101); G06F 21/62 (20130101); H04W 12/02 (20090101); G06F 21/60 (20130101); G06F 21/88 (20130101); H04W 12/08 (20090101); G06F 7/04 (20060101); G06F 17/30 (20060101); G06F 11/00 (20060101); G06F 17/00 (20060101); H04N 7/16 (20110101);