|Número de publicación||US20060073820 A1|
|Tipo de publicación||Solicitud|
|Número de solicitud||US 10/538,794|
|Número de PCT||PCT/US2003/032284|
|Fecha de publicación||6 Abr 2006|
|Fecha de presentación||10 Oct 2003|
|Fecha de prioridad||10 Oct 2002|
|También publicado como||WO2004034687A1|
|Número de publicación||10538794, 538794, PCT/2003/32284, PCT/US/2003/032284, PCT/US/2003/32284, PCT/US/3/032284, PCT/US/3/32284, PCT/US2003/032284, PCT/US2003/32284, PCT/US2003032284, PCT/US200332284, PCT/US3/032284, PCT/US3/32284, PCT/US3032284, PCT/US332284, US 2006/0073820 A1, US 2006/073820 A1, US 20060073820 A1, US 20060073820A1, US 2006073820 A1, US 2006073820A1, US-A1-20060073820, US-A1-2006073820, US2006/0073820A1, US2006/073820A1, US20060073820 A1, US20060073820A1, US2006073820 A1, US2006073820A1|
|Inventores||Ronald Craswell, David Pratt, Paul Klassen|
|Cesionario original||Craswell Ronald J, Pratt David S Jr, Klassen Paul J H|
|Exportar cita||BiBTeX, EndNote, RefMan|
|Citas de patentes (5), Citada por (71), Clasificaciones (16), Eventos legales (6)|
|Enlaces externos: USPTO, Cesión de USPTO, Espacenet|
This application claims the benefit of U.S. Provisional Application No. 60/417,905, filed on Oct. 10, 2002, entitled UPDATE FOR WIRELESS MOBILE DEVICES, and U.S. Provisional Application No. 60/417,858, filed on Oct. 10, 2002, entitled REMOTE CONTROL FOR WIRELESS MOBILE DEVICES INCLUDING REMOTE LOCKING, the subject matter of which is incorporated herein by reference.
The present invention relates to the field of wireless communications. More specifically, the present invention relates to the provision of a remove control function from remotely controlling a wireless mobile device, including remotely locking the device; and additionally includes the provision of an update function for wireless devices.
Since their introduction, the capabilities and number of services and features of wireless mobile devices have steadily increased while the cost of ownership and operation has decreased. At first, wireless mobile devices operated on analog wireless networks that established voice communications and simple paging features. Later, digital wireless networks were introduced for cellular telephone communications to provide more advanced features for voice and data communications, such as encryption, caller identification and transmitting and receiving Short Message Service (“SMS”) text messages.
Some cellular telephones also incorporate many of the features originally provided for in the hand-held electronic devices, such as personal data assistants (“PDAs”). Relative simple PDA features such as keeping a list of contacts, a calendar, appointments and the like have been generally integrated into recent cellular telephone models.
Recently, some cellular telephones were enabled to allow the browsing of web pages on the Internet or other on-line services. More recently, Action Engine, Inc. of Redmond, Wash., assignee of the present invention, has developed and improved browserless approach to are consumed using wireless mobile devices, more user data, in particular, important, sensitive and/or critical data are being stored on the wireless mobile devices. In addition, as more and more types of software are implemented and/or installed on wireless mobile devices, the number of updates to the software has increased as well. Additionally, as wireless mobile devices become more sophisticated, users may not be able to keep track of the current state of development in their software and other data on their wireless mobile devices.
The present invention will be described by way of exemplary embodiments, but not limitations, illustrated in the accompanying drawings in which like references denotes similar elements, and in which:
The detailed description which follows is represented largely in terms of processes and symbolic representations of the of operations by conventional computing components, including processors, memory storage devices for these processors, connected display devices and input devices, all of which are well-known in the art. These processes and operations may utilize conventional computing components in a heterogeneous distributed computer environment, including remote storage servers, computer servers and memory storage devices. Such processes, devices and operations also being known to those skilled in the art and others. Each of these conventional computing components may be accessible by the processors via a communications network.
The present invention includes a remote control application for wireless mobile devices. The remove control application allows a wireless communication service provider to remotely control a subscriber's wireless mobile device. In particular, the remote control application allows a wireless communications service provider to remotely lock a subscriber's wireless mobile device. Further, in an exemplary embodiment of the present invention, by invoking the update application described below, a user's data (including programs and operating system data) on a wireless mobile device can be updated without the user needing to intervene.
The remote control software application resides on a wireless mobile device and can allow secure remote administration of the wireless mobile device to cause specific tasks to be performed on the device, to cause the user interface (“UI”) of the device to be locked from normal access, allow a remote administrator to cause files and data stored on the wireless mobile device to be erased, to allow a remote administrator to cause a backup to be performed on the wireless mobile device, and for a remote administrator to cause an update on data in the wireless mobile device.
The remote control application allows the remote administrator to seize control (either with or without a user's permission) of a wireless mobile device and in one exemplary embodiment, to do so with no visible indication as to the fact that control has been seized of the device.
The remote administrator will be able to use a unique device identifier (“ID”) to log in and select various options. Special messages or instructions for the remote control application on the wireless mobile device are then placed in a secure queue on a server. Next, a “ping” message is sent to the wireless mobile device. The ping message is in turn processed by the remote control application on the wireless mobile device. The remote control application on the wireless mobile device then retrieves the special messages or instructions from the remote server and processes these instructions. In the exemplary embodiment of the present invention where the instructions include updating the wireless mobile device, the updating process will allow programs installed on the wireless mobile device to be automatically updated in a manner that can be controlled by the user in some cases and is completely automatic (e.g., controlled by the wireless service provider as instructions) in other cases.
Briefly, the update application on the wireless mobile device can update itself, update applications from a remote server, monitor a catalogue of application updates and additions on the server, monitor user activity via a unique device ID and/or other unique identifiers, launch by stub applications asking to be replaced by full applications and may further stop or resume downloads that have been interrupted.
As noted above, the update application may be activated in a number of different ways: (1) It may be launched as a normal stand alone application as to any other application launched on the wireless mobile device. (2) It may be launched by a stub application, with a specific path, to replace the stub application with its intended application (after download and successful install). To the user, they would launch the stub application, see a download in progress screen, followed by the actual application starting up. (3) As already noted above, the update application may be invoked using the remote control application and having the update application invoked by a remote administrator.
There are different types of updates and in various embodiments, the server will send updates in priority order. It will first send mandatory updates, then critical updates, then all others. Within each category, it will download the files in order of appearance. Mandatory updates are those updates that the update application will automatically (and silently) download and update whenever the update application is invoked and such an update is located. Critical updates are those that have been singled out as particularly important as they relate to fixing “bugs” in existing applications and/or providing increased security to a wireless mobile device. Normal updates are all the remaining types of updates.
Application and updates and be further categorized into “exclusive” updates. If an exclusive update is selected, no other selections can be made until the exclusive update is downloaded and installed. This category is particularly useful when installing updates that require a device reset, or updates that change the operating system files. The update application does not sent personal information to a remote server. Rather, it downloads from the server the list of available updates from which is parses and analyzes against the local wireless mobile device's computing environment.
As previously explained, embodiments of the present invention operate in a wireless network to communicate between wireless mobile devices and remote servers. It will be appreciated by those of ordinary skill in the art that other networks may be used in addition to a wireless network, e.g., the “Internet” which refers to a collection of networks and routers that can communicate between each other on a global level using the Internet Protocol (“IP”) communications protocol.
The remote control/update system 100 functions in a distributed computer environment that includes a plurality of client devices, interconnected by a wireless network 110 via a gateway 120 to other networks 130 to a remote control/update server 150. In addition, an administrator device 140 is connected with the remote control/update server 150 to pass instructions to the remote control/update server 150. All these connections and communications are interconnected via suitable network connections using suitable network communications protocols. As will be appreciated by those of ordinary skill in the art, the remote control/update server 150 may reside on any device accessible by the client device 200 shown in
It will also be appreciated that while the remote control/update server 150 of the remote control/update system 100 is illustrated as a single device, the remote control/update server 150 may actually comprise more than a single device in an actual system practicing embodiments of the present invention. It will also be appreciated that the remote control/update server 150 may comprise file servers, database servers or a mixture of file servers and database servers.
The computing device 200 also includes a processing unit 210, a display 240 and a memory 250, all interconnected along with the communications interface 230 via a bus 220. Those of ordinary skill in the art and others will appreciate that the display 240 may not be necessary in all embodiments of the present invention and accordingly, is an optional component. The memory 250 generally comprises a random access memory (“RAM”), a read-only memory (“ROM”), and a permanent mass storage device, such as a disc drive, flash memory, or the like. The memory 250 stores and operating system 255, remote control software 260, and update software 265, formed in accordance with embodiments of the present invention. It will be appreciated that these software components may be loaded from a computer readable medium into memory 250 of the client device 200 using a drive mechanism (not shown) associated with the computer readable medium, such as a floppy, tape, DVD/CD ROM drive, flash memory or the communications interface 230.
Although an exemplary computing device 200 has been described, it general conforms to conventional computing devices, those of ordinary skill in the art and others will appreciate that a client device 200 may be any of a great number of computing devices capable of communicating remotely with other computing devices. In various embodiments of the present invention, the client device 200 may be a cellular phone, PDA, general purpose computing device and the like.
The operation of the remote control functionality of the remote control/update system 100 shown in
If, however, in decision block 410 it was determined that the message was a ping message, then processing proceeds to block 415 where the client device 200 sends a request for further instructions to a remote server (e.g., remote control/update server 150). Those of ordinary skill in the art and others will appreciate that while only a single remote control/update server 150 is illustrated in
If, however, in decision block 425 it was determined that the instructions are targeted for mobile services, then processing proceeds to block 445 where mobile services are performed. Such mobile services may be any conventional mobile services that would apply to a wireless mobile device. However, in one exemplary embodiment of the present invention, these mobile services may include service for locking the UI of the client device 200.
If in decision block 425 it was determined that the instruction was targeted to the backup service then processing proceeds to decision block 430 where a further determination is made whether the instructions are directed to erasing or backing up data on the client device 200. If the determination in decision block 430 indicated that data is to be erased, then processing proceeds to block 435 where the memory of the client device is partially or completely erased as directed in the received instructions. In the alternative, where a backup instruction was issued for backing up the data on the client device 200, then processing proceeds to block 440 where some or all of the memory of the client device is backed up depending on the received instructions.
Those of ordinary skill in the art and others will appreciate that more types of instruction may be included in still other embodiments of the present invention. The inclusion of the messaging service, backup and update instructions is meant to be illustrative and not limiting. To better appreciate one such embodiment,
The operation of an exemplary embodiment of the present invention having an update functionality implemented in the remote control/update system 100 shown in
The exemplary communication interactions shown in
The client device 200 next depicts 525 any relevant available updates on the client device 200 (e.g., via the display 240). The relevant available updates are those non-mandatory updates (i.e., critical updates and other updates) that have not already been installed on the client device 200 and for which the client device 200 has a use (e.g., that are applicable to the currently installed operating system and/or versions of software running on the client device 200).
One or more relevant available updates are selected 530 on the client device 200. Those of ordinary skill in the art and others will appreciate that the selection of relevant available updates may be accomplished in a variety of manners. In one exemplary embodiment of the present invention all relevant available critical updates are automatically selected while other updates may be selected by a user using any form of conventional user interface. Next the selected updates are requested 535 from the remote control/update server 150. The remote control/update server 150 retrieves 540 the selected update or updates and sends 545 the selected updates back to the client device 200. Once the client device 200 receives the selected updates, they are then installed 550 on the client device 200.
The remote control/update system 100 (described herein) includes a client device 200 whose software is to be updated via the remote control/update server 150.
The update routine 600 begins at block 605 where a update is requested from the remote control/update server 150. Next in block 610 a catalog of available updates is received along with any mandatory updates for the client device 200. In decision block 615 a determination is made whether any mandatory updates were received. If so then processing proceeds to block 620 where the mandatory updates are installed on the client device 200. Processing then proceeds to block 625. Also if in decision block 615 it was determined that no mandatory updates were received then processing continues to block 625. In block 625 the received catalog of available updates is compared to the currently installed software on the client device 200. Next in decision block 630 a determination is made whether any available updates in the catalog are still relevant to the client device 200. If in decision block 630 it is determined that no available updates are relevant to client device 200 then processing continues to block 660 where a message is depicted on the client device 600 that there are no relevant updates and routine 600 ends.
If, however, in decision block 630 it was determined that there are available updates that are still relevant to the client device 200, then in block 635 those relevant updates are depicted at the client device 200. Processing then proceeds to block 640 where any desired relevant updates are selected. As already noted, desired relevant updates may be selected in a variety of fashions according to any conventional selection mechanism. Next, in block 645 a request is sent to the remote control/update server 150 for the selected updates. The selected updates are received in block 650, and installed on the client device 200 in block 655.
The operations of the alternate update mechanism illustrated in
Alternate update routine 800 begins at block 805 with the execution of a stub application. Next in block 810 a placeholder for the full application is displayed. In block 815, the client device 200 sends a request to the remote control/update server 150 for the full application. In decision block 820 a determination is made whether the full application was received from the remote control/update server 150. If so, processing proceeds to block 830 where the full application is installed on the client device 200. After which, the full application can then be executed in block 835. If however in decision block 820 it was determined that the full application was not received then in block 825 an error is depicted indicating that the full application was not available.
Although various embodiments of the present invention have been illustrated and described, it will be appreciated that changes can be made therein without departing from the spirit and scope of the invention as defined by the appended claims. In particular it will be appreciated that while the processes and communication-interactions and the present interaction have been described in a particular order, those of ordinary skill in the art and other will appreciate that other orders of processes and/or communication interactions will also fall within the spirit and scope of the present invention.
|Patente citada||Fecha de presentación||Fecha de publicación||Solicitante||Título|
|US6928579 *||27 Jun 2001||9 Ago 2005||Nokia Corporation||Crash recovery system|
|US6941148 *||2 Mar 2001||6 Sep 2005||International Business Machines Corporation||Device registry for automatic connection and data exchange between pervasive devices and backend systems|
|US7096311 *||30 Sep 2002||22 Ago 2006||Innopath Software, Inc.||Updating electronic files using byte-level file differencing and updating algorithms|
|US7275243 *||21 Mar 2003||25 Sep 2007||Sun Microsystems, Inc.||Mobile download system|
|US7415707 *||18 Abr 2002||19 Ago 2008||Sony Corporation||Installation software using a setting file to automatically determine if a module is installable and the location of the installation|
|Patente citante||Fecha de presentación||Fecha de publicación||Solicitante||Título|
|US7409575 *||31 Dic 2004||5 Ago 2008||Intel Corporation||Recovery of computer systems|
|US7620392 *||27 Feb 2006||17 Nov 2009||Good Technology, Inc.||Method and system for distributing and updating software in wireless devices|
|US7702322||27 Feb 2006||20 Abr 2010||Good Technology, Llc||Method and system for distributing and updating software in wireless devices|
|US7853297||26 Abr 2008||14 Dic 2010||Iwao Fujisaki||Communication device|
|US7865216||4 Dic 2009||4 Ene 2011||Iwao Fujisaki||Communication device|
|US7890089||15 Feb 2011||Iwao Fujisaki||Communication device|
|US7904109||9 Oct 2010||8 Mar 2011||Iwao Fujisaki||Communication device|
|US7907942||23 Jul 2008||15 Mar 2011||Iwao Fujisaki||Communication device|
|US7907963||27 Abr 2008||15 Mar 2011||Iwao Fujisaki||Method to display three-dimensional map on communication device|
|US7917167 *||29 Mar 2011||Iwao Fujisaki||Communication device|
|US7945236||10 Abr 2010||17 May 2011||Iwao Fujisaki||Communication device|
|US7945256||10 Abr 2010||17 May 2011||Iwao Fujisaki||Communication device|
|US7945286||10 Abr 2010||17 May 2011||Iwao Fujisaki||Communication device|
|US7945287||10 Abr 2010||17 May 2011||Iwao Fujisaki||Communication device|
|US7949371||10 Abr 2010||24 May 2011||Iwao Fujisaki||Communication device|
|US7996038||18 Dic 2010||9 Ago 2011||Iwao Fujisaki||Communication device|
|US8010157||18 Dic 2010||30 Ago 2011||Iwao Fujisaki||Communication device|
|US8041371||12 Ago 2010||18 Oct 2011||Iwao Fujisaki||Communication device|
|US8064954||22 Nov 2011||Iwao Fujisaki||Communication device|
|US8078157||12 Oct 2009||13 Dic 2011||Good Technology, Inc.||Method and system for distributing and updating software in wireless devices|
|US8090402||23 Jul 2004||3 Ene 2012||Iwao Fujisaki||Communication device|
|US8121635||26 Dic 2008||21 Feb 2012||Iwao Fujisaki||Communication device|
|US8224376||12 Feb 2011||17 Jul 2012||Iwao Fujisaki||Communication device|
|US8233938||31 Jul 2012||Iwao Fujisaki||Communication device|
|US8238963||7 Ago 2012||Iwao Fujisaki||Communication device|
|US8260352||3 Ago 2011||4 Sep 2012||Iwao Fujisaki||Communication device|
|US8271608||7 Dic 2011||18 Sep 2012||Lookout, Inc.||System and method for a mobile cross-platform software system|
|US8295876||23 Oct 2012||Iwao Fujisaki||Communication device|
|US8295880||19 Oct 2011||23 Oct 2012||Iwao Fujisaki||Communication device|
|US8301194||30 Oct 2012||Iwao Fujisaki||Communication device|
|US8311578||13 Nov 2012||Iwao Fujisaki||Communication device|
|US8320899 *||20 Ene 2010||27 Nov 2012||Ntt Docomo, Inc.||Installation notification method, installation notification system, and installation notification server|
|US8320958||6 Sep 2011||27 Nov 2012||Iwao Fujisaki||Communication device|
|US8326355||4 Dic 2012||Iwao Fujisaki||Communication device|
|US8331983||11 Dic 2012||Iwao Fujisaki||Communication device|
|US8331984||14 Sep 2011||11 Dic 2012||Iwao Fujisaki||Communication device|
|US8335538||6 Sep 2011||18 Dic 2012||Iwao Fujisaki||Communication device|
|US8340720||6 Sep 2011||25 Dic 2012||Iwao Fujisaki||Communication device|
|US8340726||4 Oct 2008||25 Dic 2012||Iwao Fujisaki||Communication device|
|US8351984||3 Ago 2011||8 Ene 2013||Iwao Fujisaki||Communication device|
|US8364201||6 Sep 2011||29 Ene 2013||Iwao Fujisaki||Communication device|
|US8365252||7 Dic 2011||29 Ene 2013||Lookout, Inc.||Providing access levels to services based on mobile device security state|
|US8452307||28 May 2013||Iwao Fujisaki||Communication device|
|US8467768 *||18 Jun 2013||Lookout, Inc.||System and method for remotely securing or recovering a mobile device|
|US8572571||21 Jul 2010||29 Oct 2013||Shuv Gray Llc||Modification of terminal and service provider machines using an update server machine|
|US8583556||15 Ago 2011||12 Nov 2013||Content Technologies, Llc||Method of providing a digital asset for distribution|
|US8606856||15 Abr 2008||10 Dic 2013||Content Technologies, Llc||Digital media asset identification system and method|
|US8626838||4 Sep 2012||7 Ene 2014||Content Technologies, Llc||Digital media asset identification system and method|
|US8639214||26 Oct 2007||28 Ene 2014||Iwao Fujisaki||Communication device|
|US8655307||27 Nov 2012||18 Feb 2014||Lookout, Inc.||System and method for developing, updating, and using user device behavioral context models to modify user, device, and application state, settings and behavior for enhanced user security|
|US8774788||10 Oct 2013||8 Jul 2014||Lookout, Inc.||Systems and methods for transmitting a communication based on a device leaving or entering an area|
|US8825007||10 Oct 2013||2 Sep 2014||Lookout, Inc.||Systems and methods for applying a security policy to a device based on a comparison of locations|
|US8984657 *||21 Dic 2010||17 Mar 2015||Appcentral, Inc.||System and method for remote management of applications downloaded to a personal portable wireless appliance|
|US8997181||23 Sep 2013||31 Mar 2015||Lookout, Inc.||Assessing the security state of a mobile communications device|
|US9042876||15 Abr 2013||26 May 2015||Lookout, Inc.||System and method for uploading location information based on device movement|
|US9043919||30 May 2012||26 May 2015||Lookout, Inc.||Crawling multiple markets and correlating|
|US9065846||17 Jun 2013||23 Jun 2015||Lookout, Inc.||Analyzing data gathered through different protocols|
|US9081897||22 Oct 2013||14 Jul 2015||Shuv Gray Llc||Modification of terminal and service provider machines using an update server machine|
|US9100389||2 Ago 2013||4 Ago 2015||Lookout, Inc.||Assessing an application based on application data associated with the application|
|US9100925||10 Oct 2013||4 Ago 2015||Lookout, Inc.||Systems and methods for displaying location information of a device|
|US20050047414 *||23 Ago 2004||3 Mar 2005||Kabushiki Kaisha Toshiba||Communication control apparatus, communication system, and communication control method|
|US20060023738 *||28 Jun 2005||2 Feb 2006||Sanda Frank S||Application specific connection module|
|US20100076871 *||25 Mar 2010||Hands-On Mobile, Inc.||Software Application Framework for Network-Connected Devices|
|US20100190482 *||20 Ene 2010||29 Jul 2010||Ntt Docomo, Inc||Installation notification method, installation notification system, and installation notification server|
|US20100223677 *||2 Sep 2010||Altair Engineering, Inc.||Digital content licensing method|
|US20110093516 *||30 Dic 2006||21 Abr 2011||Zte Corporation||implementation method for updating the terminals in batches|
|US20110145932 *||21 Dic 2010||16 Jun 2011||Paul Shelton Nerger||System and Method for Remote Management of Applications Downloaded to a Personal Portable Wireless Appliance|
|US20110302636 *||8 Dic 2011||Bryan Dunkeld||Method of Providing a Digital Asset for Distribution|
|US20120188064 *||16 Mar 2012||26 Jul 2012||Lookout. Inc., a California Corporation||System and method for remotely initiating playing of sound on a mobile device|
|US20120239783 *||20 Sep 2012||Optim Corporation||Remote operation system and remote operation method for terminal|
|WO2011011534A1 *||21 Jul 2010||27 Ene 2011||Sourcetrace Systems, Inc.||Modification of terminal and service provider machines using an update server machine|
|Clasificación de EE.UU.||455/419|
|Clasificación internacional||G06F9/445, H04W8/22, H04M3/42, H04M1/725, H04M3/00|
|Clasificación cooperativa||H04W8/22, G06F8/65, H04M3/42144, H04M1/72525, H04M3/42178, H04W8/245|
|Clasificación europea||H04M1/725F1A, G06F8/65, H04M3/42E5, H04W8/24N|
|20 Mar 2006||AS||Assignment|
Owner name: ACTION ENGINE CORPORATION, WASHINGTON
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:CRASWELL, RONALD J.;PRATT, DAVID S., JR.;KLASSEN, PAUL J.H.;REEL/FRAME:017698/0339
Effective date: 20060303
|3 Jun 2008||AS||Assignment|
Owner name: PERLEGO SYSTEMS, INC., WASHINGTON
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:ACTION ENGINE CORPORATION;REEL/FRAME:021046/0430
Effective date: 20080523
|7 Abr 2010||AS||Assignment|
Owner name: SILICON VALLEY BANK,CALIFORNIA
Free format text: SECURITY AGREEMENT;ASSIGNOR:PERLEGO SYSTEMS, INC.;REEL/FRAME:024201/0781
Effective date: 20100330
Owner name: SILICON VALLEY BANK, CALIFORNIA
Free format text: SECURITY AGREEMENT;ASSIGNOR:PERLEGO SYSTEMS, INC.;REEL/FRAME:024201/0781
Effective date: 20100330
|15 Nov 2010||AS||Assignment|
Owner name: PERLEGO SYSTEMS INC., WASHINGTON
Free format text: RELEASE;ASSIGNOR:SILICON VALLEY BANK;REEL/FRAME:025321/0253
Effective date: 20101109
|20 Jul 2011||AS||Assignment|
Owner name: BOLLER CROSS DATA, L.L.C., DELAWARE
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:PERLEGO SYSTEMS, INC.;REEL/FRAME:026621/0940
Effective date: 20110707
|21 Jul 2011||AS||Assignment|
Owner name: PERLEGO SYSTEMS, INC., WASHINGTON
Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:SILICON VALLEY BANK;REEL/FRAME:026626/0389
Effective date: 20110630