|Publication number||US20050232175 A1|
|Application number||US 10/826,833|
|Publication date||Oct 20, 2005|
|Filing date||Apr 16, 2004|
|Priority date||Apr 16, 2004|
|Also published as||US7499950, US20050234967, WO2005107217A1|
|Publication number||10826833, 826833, US 2005/0232175 A1, US 2005/232175 A1, US 20050232175 A1, US 20050232175A1, US 2005232175 A1, US 2005232175A1, US-A1-20050232175, US-A1-2005232175, US2005/0232175A1, US2005/232175A1, US20050232175 A1, US20050232175A1, US2005232175 A1, US2005232175A1|
|Inventors||Vadim Draluk, Boris Klots, Dmitri Latypov|
|Original Assignee||Vadim Draluk, Boris Klots, Latypov Dmitri R|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (9), Referenced by (17), Classifications (16), Legal Events (1)|
|External Links: USPTO, USPTO Assignment, Espacenet|
The present invention relates generally to the field of systems and methods for managing mobile electronic devices from a remote location. More particularly, the present invention relates to a system and method for updating applications and files of a client device via a wireless communication network.
Computing devices may have different capabilities and features based on the applications installed in their memory. The applications may be pre-installed to a computing device before purchase by a customer or installed after purchase by a customer or service technician via a storage media, such as a magnetic or optical disk. For computing devices that communicate with a computer network, applications may be installed after a customer or service technician downloads the applications to the computing device.
Installations of applications and updates on client devices present other issues that are not a concern for wired devices. Users of client devices frequently need access to a variety of information, but such information is not as readily available as wired connections due to the limited bandwidth of wireless connections. Also, the traffic experienced by a client device should be minimized in order to minimize power drain on the device's power source. Thus, communications are challenged to maximize the quality of information provided to client devices while minimizing the traffic imposed on the wireless connections to the devices.
A communication that utilizes a large number of applications must have the capability of managing the applications efficiently and proficiently. Two of the more important functions of these systems are client provisioning and device management. Generally, these functions operate independently (with the exception of the WAP profile used in SyncML device management bootstrapping). On the other hand, there are advantages for client provisioning and device management to converge. As application data protocols, both functions are typically generic and, thus, they are quite similar. The major difference between client provisioning and device management is at the level of transport protocols, where client provisioning is confined to a certain type. Thus, the amount and complexity of data that can be provisioned is limited. Accordingly, there is need for a system and method for converging and managing client provisioning and device management to provide significant benefit to communication service providers. There is further need for a system and method that would provide communication service providers with the ability to perform provisioning while in-call and without opening a data connection.
Client provisioning and device management functions may be combined by defining client provisioning characteristics and parameters that would operate over a device management tree (DMT). For example, Open Mobile Alliance Client Provisioning (OMA CP) characteristics and parameters may be mapped to a DMT to create a new characteristic, namely synchronized markup language-device management (SYNCML-DM), which is recursive. Thus, communication service providers may have a generic and simple parameter provisioning mechanism using existing communication infrastructure. The mechanism would enable the communication service provider to perform provisioning while a user of a client device is communicating with a customer care representative of the communication service provider. The customer care representative would be able to address the user's problems efficiently and provide maximum satisfaction of user experience to the user.
One aspect of the present invention is a method for a client device of a communication system. The client device receives a client provisioning document from a source. The client device then identifies a device management characteristic from the client provisioning document. Thereafter, the client device stores data based on the device management characteristic of the client provisioning document to a device management tree.
Another aspect of the present invention is a client device of a communication system comprising a provisioning and management framework. The framework receives a client provisioning document from a source, and the client provisioning document includes a device management characteristic.
The wireless communication network 104 may include a variety of components for proper operation and communication with the client device 102. For example, for the cellular-based communication infrastructure shown in
The server 110 is capable of providing services requested by the client device 102. For example, a user of the device 102 may send a request for assistance, in the form of a data signal (such as text messaging), to the wireless communication network 104, which directs the data signal to the server 110. In response, the server 110 may interrogate the device and/or network state and identify one or more solutions. For those solutions that require change or correction of a programmable module of the device 102, the server 110 may send update data to the device via the wireless link 106 so that the programmable module may be updated to fulfill the request. If multiple solutions are available, then the server 110 may send these options to the device 102 and await a response from the device before proceeding.
The first embodiment 100 may also include an operator terminal 114, managed by a service person 116, which controls the server 110 and communicates with the device 102 through the server. When the server 110 receives the request for assistance, the service person may interrogate the device and/or network state to identify solution(s) and/or select the best solution if multiple solutions are available. The service person 116 may also correspond with the device 102 via data signals (such as text messaging) to explain any issues, solutions and/or other issues that may be of interest the user of the device.
The first embodiment 100 may further include a voice client device 118 connected to the rest of the wireless communication network 104 via a wired or wireless connection, such as wired line 118, and is available for use by the service person 116. The voice client device 118 may also connect to the network via the server 110 or the operator terminal 114. Thus, in reference to the above examples, a user of the device 102 may send a request for assistance, in the form of a voice signal, to the wireless communication network 106, which directs the data signal to the server 110. While the server 110 and or the service person 116 is interrogating the device and/or network state, identifying one or more solutions, and/or selecting an appropriate solution, the service person may correspond with the device 102 via voice signals to explain any issues, solutions and/or other issues that may be of interest the user of the device.
The major difference comes at the level of transport protocols. For the example shown in
The client provisioning characteristics and parameters may be defined so that they may operate over the device management tree. A single new characteristic which is recursive may be utilized and is referenced herein as SYNCML-DM. The parameter names include, but are not limited to, a uniform resource identifier (URI) parameter, an operational (OP) parameter and a DATA parameter. The URI parameter is a sync node device management URI. An actual URI may be calculated as concatenation of URI's of nested characteristics and is the only parameter appearing in non-inner-most characteristics. The OP parameter is a node operation, with possible values such as ADD, REPLACE, DELETE and EXECUTE. The DATA parameter is data that may be applied by the operation, if any.
As shown in
The device management server 202 of the network 104 communicates with the device management agent 208 of the client device via communication link 212. For one embodiment, the signal protocol between the servers 202, 204 and the agents 208, 210 is a Hyper Text Transfer Protocol/Open Business Engine (HTTP/OBE). The Open Business Engine is an open source workflow engine written in JAVA, and OBE workflow definitions are written in XML and are typically executed by a J2EE container. The provisioning and management framework 206 also receives sync signals, in the form of WAP Push, from the device management server 202 via connection link 214 and provides the incoming device management signals to the device management agent 208 via connection link 218. Likewise, the provisioning and management framework 206 further receives provisioning signals, in the form of WAP Push, from the client provisioning server 204 via connection link 216 and provide the incoming provisioning signals to the client provisioning agent 210 via connection link 220.
The client device further includes a device management engine 222 communicating with the device management agent 208 via connection link 224 and a device management tree 226 communicating with the device management engine via communication link 228.
Referring to the client device 102 and the server 110 of
The input and output devices 308, 310 of the internal components 300 may include a variety of visual, audio and/or mechanical outputs. For example, the output device(s) 308 may include a visual output device 316 such as a liquid crystal display and light emitting diode indicator, an audio output device 318 such as a speaker, alarm and/or buzzer, and/or a mechanical output device 320 such as a vibrating mechanism. Likewise, by example, the input devices 310 may include a visual input device 322 such as an optical sensor (for example, a camera), an audio input device 324 such as a microphone, and a mechanical input device 326 such as a flip sensor, keyboard, keypad, selection button, touch pad, touch screen, capacitive sensor, motion sensor, and switch.
The internal components 300 may include a location circuit 328. Examples of the location circuit 328 include, but are not limited to, a Global Positioning System (GPS) receiver, a triangulation receiver, an accelerometer, a gyroscope, or any other information collecting device that may identify a current location of the device.
The memory portion 306 of the internal components 300 may be used by the processor 304 to store and retrieve data. The data that may be stored by the memory portion 306 include, but is not limited to, operating systems, applications, and data. Each operating system includes executable code that controls basic functions of the client device, such as interaction among the components of the internal components 300, communication with external devices via the transceiver 302 and/or the component interface 312, and storage and retrieval of applications and data to and from the memory portion 306. Each application includes executable code utilizes an operating system to provide more specific functionality for the client device, such as file system service and handling of protected and unprotected data stored in the memory portion 306. Data is non-executable code or information that may be referenced and/or manipulated by an operating system or application for performing functions of the client device.
The processor 304 may perform various operations to store, manipulate and retrieve information in the memory portion 306. Each component of the internal components 300 is not limited to a single component but represents functions that may be performed by a single component or multiple cooperative components, such as a central processing unit operating in conjunction with a digital signal processor and one or more input/output processors. Likewise, two or more components of the internal components 300 may be combined or integrated so long as the functions of these components may be performed by the client device.
After identifying a characteristic at step 408, the client device determines whether the characteristic includes a URI parameter but does not include an OP parameter or a DATA parameter at step 410. If the characteristic only includes a URI parameter, then the client device appends the URI parameter at step 412, stores the URI parameter by pushing it down on a URI stack at step 414, and returns to step 408 where the client device identifies the next characteristic from the client provisioning document.
If the client device determines that the characteristic does not only include a URI parameter at step 410, then the client device determines whether the characteristic includes an OP parameter at step 416. If not, then the client device sets the OP parameter to “REPLACE” at step 418 and thereafter determines whether the characteristic includes a DATA parameter step 420. If the characteristic does include an OP parameter, then the client device proceeds directly to step 420 without updating the OP parameter.
The client device determines whether the characteristic includes a DATA parameter at step 420. If not, then the client device sets the DATA parameter to a NULL value at step 422 and sets device management tree (DMT) data at step 424. If the characteristic does include a DATA parameter, then the client device proceeds directly to step 424 to set the DMT data. To set the DMT data at step 424, the client device provides the data to the device management tree 226 (shown in
The third line 506 of the exemplary data format 500 identifies a second node, nested within the first node, having a characteristic type of SYNCML-DM. The fourth line 508 sets the URI parameter of the second node to be “FileName”, the fifth line 510 sets the OP parameter of the second node to be “REPLACE”, and the sixth line 512 sets the DATA parameter of the second node to be “log.txt”. The seventh line 514 refers back to line 506 and indicates the end of all descriptions of the second node.
The eighth line 516 of the exemplary data format 500 identifies a third node, nested within the first node along with the second node, having a characteristic type of SYNCML-DM. The ninth line 518 sets the URI parameter of the third node to be “Level”, the tenth line 520 sets the OP parameter of the third node to be “REPLACE”, and the eleventh line 522 sets the DATA parameter of the second node to be “3”. The twelfth line 524 refers back to line 516 and indicates the end of all descriptions of the third node. Likewise, the thirteenth line 526 refers back to line 502 and indicates the end of all descriptions of the first node and its nested sub-nodes.
While the preferred embodiments of the invention have been illustrated and described, it is to be understood that the invention is not so limited. Numerous modifications, changes, variations, substitutions and equivalents will occur to those skilled in the art without departing from the spirit and scope of the present invention as defined by the appended claims.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US20030103484 *||Dec 3, 2002||Jun 5, 2003||Paul Oommen||Apparatus, and associated method, for retrieving mobile-node logic tree information|
|US20030204640 *||Apr 22, 2003||Oct 30, 2003||Nokia Corporation||Method and device for management of tree data exchange|
|US20040043788 *||Aug 28, 2002||Mar 4, 2004||Guarav Mittal||Management of parameters in a removable user identity module|
|US20040123241 *||Nov 20, 2003||Jun 24, 2004||Nokia Corporation||Priorization of management objects|
|US20040158619 *||Feb 10, 2003||Aug 12, 2004||Claus Pedersen||Method and apparatus for provisioning content|
|US20040261116 *||Jul 3, 2002||Dec 23, 2004||Mckeown Jean Christophe||Broadband communications|
|US20050027851 *||May 22, 2002||Feb 3, 2005||Mckeown Jean Christophe||Broadband communications|
|US20050055453 *||May 27, 2004||Mar 10, 2005||Microsoft Corporation||System and method for automatic conversion from WAP client provisioning XML represented objects to OMA DM tree structure represented objects|
|US20050166140 *||Jan 27, 2004||Jul 28, 2005||International Business Machines Corporation||Eliminating superfluous namespace declarations and undeclaring default namespaces in XML serialization processing|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US8073960||Oct 15, 2004||Dec 6, 2011||Nokia Corporation||Arranging management operations in management system|
|US8095128 *||Mar 13, 2007||Jan 10, 2012||International Business Machines Corporation||Device management system for remotely accessing terminal equipments|
|US8321864 *||Oct 22, 2007||Nov 27, 2012||Vodafone Group Plc||Device management|
|US8356094 *||Dec 11, 2008||Jan 15, 2013||Huawei Technologies Co., Ltd.||Method, system, client and server for locating operation nodes in communication system|
|US8392545||Oct 15, 2004||Mar 5, 2013||Nokia Corporation||Device management system|
|US8396138||Jun 9, 2008||Mar 12, 2013||Samsung Electronics Co., Ltd||System and method for controlling wireless network access information in using removable external modem|
|US8479262||Oct 31, 2008||Jul 2, 2013||Hewlett-Packard Development Company, L.P.||Managing electronic devices using an electronic device as a root of trust|
|US8543719 *||Aug 1, 2006||Sep 24, 2013||Samsung Electronics Co., Ltd||System and method for managing XDM service information|
|US9009306||Dec 3, 2012||Apr 14, 2015||Huawei Technologies Co., Ltd.||Method, system, client and server for locating operation nodes in communication system|
|US20060020947 *||Oct 15, 2004||Jan 26, 2006||Mika Hallamaa||Arranging management operations in management system|
|US20060031449 *||Oct 15, 2004||Feb 9, 2006||Mika Hallamaa||Selection of management method|
|US20100332639 *||Oct 31, 2008||Dec 30, 2010||Osvaldo Diaz||Providing Manageability To An Electronic Device That Supports Location Limited Manageability Functionality|
|EP2156609A2 *||Jun 9, 2008||Feb 24, 2010||Samsung Electronics Co., Ltd.||System and method for controlling wireless network access information in using removable external modem|
|EP2156609A4 *||Jun 9, 2008||Aug 17, 2011||Samsung Electronics Ltd||System and method for controlling wireless network access information in using removable external modem|
|EP2429225A1 *||Apr 30, 2010||Mar 14, 2012||ZTE Corporation||Method for provisioning parameters of terminal, system thereof, and terminal management device|
|WO2008150145A2||Jun 9, 2008||Dec 11, 2008||Samsung Electronics Co Ltd|
|WO2009005203A1 *||Feb 4, 2008||Jan 8, 2009||Lg Electronics Inc||Mobile e-mail management objects|
|U.S. Classification||370/310, 709/222, 709/223|
|International Classification||H04L29/08, H04L29/06, H04L12/24|
|Cooperative Classification||Y10S707/99948, Y10S707/99945, H04L67/04, H04L67/34, H04L41/0806, H04L41/046|
|European Classification||H04L41/08A1, H04L41/04C, H04L29/08N33, H04L29/08N3|
|Apr 16, 2004||AS||Assignment|
Owner name: MOTOROLA, INC., ILLINOIS
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:DRALUK, VADIM;KLOTS, BORIS;LAYTPOV, DIMITRI R.;REEL/FRAME:015245/0718;SIGNING DATES FROM 20040406 TO 20040414