US20050232175A1 - System and method for provisioning device management tree parameters over a client provisioning protocol - Google Patents
System and method for provisioning device management tree parameters over a client provisioning protocol Download PDFInfo
- Publication number
- US20050232175A1 US20050232175A1 US10/826,833 US82683304A US2005232175A1 US 20050232175 A1 US20050232175 A1 US 20050232175A1 US 82683304 A US82683304 A US 82683304A US 2005232175 A1 US2005232175 A1 US 2005232175A1
- Authority
- US
- United States
- Prior art keywords
- client
- provisioning
- parameter
- device management
- characteristic
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
- 238000000034 method Methods 0.000 title claims description 12
- 238000004891 communication Methods 0.000 claims abstract description 38
- 238000007726 management method Methods 0.000 description 38
- 239000003795 chemical substances by application Substances 0.000 description 9
- 230000006870 function Effects 0.000 description 8
- 239000013256 coordination polymer Substances 0.000 description 7
- 238000010586 diagram Methods 0.000 description 6
- 230000008901 benefit Effects 0.000 description 3
- 230000001413 cellular effect Effects 0.000 description 3
- 230000007246 mechanism Effects 0.000 description 3
- 230000000007 visual effect Effects 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 1
- 238000012937 correction Methods 0.000 description 1
- 238000013499 data model Methods 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/04—Network management architectures or arrangements
- H04L41/046—Network management architectures or arrangements comprising network management agents or mobile agents therefor
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/04—Protocols specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99941—Database schema or data structure
- Y10S707/99944—Object-oriented database structure
- Y10S707/99945—Object-oriented database structure processing
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99941—Database schema or data structure
- Y10S707/99948—Application of database or data structure, e.g. distributed, multimedia, or image
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
- Information Transfer Between Computers (AREA)
Abstract
A client device (102) of a communication system (100) comprising a provisioning and management framework (206). The framework (206) receives (404) a client provisioning document from a source (110), and the client provisioning document includes a device management characteristic. The client device (102) then identifies (408) a device management characteristic from the client provisioning document. Thereafter, the client device (102) provides (424) data based on the device management characteristic of the client provisioning document to a device management tree (226, 426).
Description
- 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.
-
FIG. 1 is a schematic view illustrating an embodiment of a communication system in accordance with the present invention. -
FIG. 2 is a schematic view illustrating another embodiment of the communication system in accordance with the present invention. -
FIG. 3 is a block diagram illustrating exemplary internal components of various servers, controllers and devices that may utilize the present invention. -
FIG. 4 is a flow diagram representing an exemplary operation of a client device in accordance with the present invention. -
FIG. 5 is a code diagram illustrating an exemplary data format that may be processed by the client device in accordance with the present invention. - 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.
- Referring to
FIG. 1 , there is provided a schematic view illustrating afirst embodiment 100 of a communication system. Thefirst embodiment 100 includes aclient device 102 communicating with awireless communication network 104 through awireless link 106. Any type ofwireless link 106 may be utilized for the present invention, but it is to be understood that a high speed wireless data connection is preferred. For example, thewireless communication network 104 may communicate with a plurality of client devices, including theclient device 102, via a cellular-based communication infrastructure that utilizes a cellular-based communication protocols such as Advanced Mobile Phone System (AMPS), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Global System For Mobile Communications (GSM), Integrated Digital Enhanced Network (iDEN), General Packet Radio Service (GPRS), Enhanced Data for GSM Evolution (EDGE), Universal Mobile Telecommunications System (UMTS), Wideband Code Division Multiple Access (WCDMA) and their variants. Thewireless communication network 104 may also communicate with the plurality of client devices via a peer-to-peer or ad hoc system utilizing appropriate communication protocols such as Bluetooth, IEEE 802.11, IEEE 802.16, and the like. - The
wireless communication network 104 may include a variety of components for proper operation and communication with theclient device 102. For example, for the cellular-based communication infrastructure shown inFIG. 1 , thewireless communication network 104 includes at least onebase station 108 and aserver 110. Although a variety of components may be coupled between one ormore base stations 108 and theserver 110, the base station and server shown inFIG. 1 is connected by a singlewired line 112 to simplify this example. - The
server 110 is capable of providing services requested by theclient device 102. For example, a user of thedevice 102 may send a request for assistance, in the form of a data signal (such as text messaging), to thewireless communication network 104, which directs the data signal to theserver 110. In response, theserver 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 thedevice 102, theserver 110 may send update data to the device via thewireless link 106 so that the programmable module may be updated to fulfill the request. If multiple solutions are available, then theserver 110 may send these options to thedevice 102 and await a response from the device before proceeding. - The
first embodiment 100 may also include an operator terminal 114, managed by aservice person 116, which controls theserver 110 and communicates with thedevice 102 through the server. When theserver 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. Theservice person 116 may also correspond with thedevice 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 avoice client device 118 connected to the rest of thewireless communication network 104 via a wired or wireless connection, such aswired line 118, and is available for use by theservice person 116. Thevoice client device 118 may also connect to the network via theserver 110 or the operator terminal 114. Thus, in reference to the above examples, a user of thedevice 102 may send a request for assistance, in the form of a voice signal, to thewireless communication network 106, which directs the data signal to theserver 110. While theserver 110 and or theservice 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 thedevice 102 via voice signals to explain any issues, solutions and/or other issues that may be of interest the user of the device. - Referring to
FIG. 2 , there is provided a schematic view illustrating asecond embodiment 200 of the communication system. For this system, client provisioning and device management are converged. An example of client provisioning is OMA CP, and an example of device management is SyncML DM. As application data protocols, they are similarly generic, though device management tends to have a meta-data model that is missing from client provisioning. - The major difference comes at the level of transport protocols. For the example shown in
FIG. 2 , the OMA CP is confined to Wireless Application Protocol Push (WAP Push), which may limit the amount and complexity of data that may be provisioned. On the other hand, the ability to perform provisioning while in-call, and without opening a data connection, may be a significant benefit for the communication service provider. The present invention is not limited to the embodiments shown. For example, SyncML DM binding over short message service (SMS) may be implemented. Preferably, to minimize additional cost, the device management may be implemented on existing infrastructure commonly used by communication service providers, such as OMA CP. - 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
FIG. 2 , thesecond embodiment 200 includes components at thenetwork 104 and components at one ormore client devices 102. Each component may be a separate device, controller or server, or two or more components may be combined within the same device, controller or server. The components at thenetwork 104 include adevice management server 202, such as a SyncML DM server, and aclient provisioning server 204, such as an OMA CP server. The components at theclient device 102 include a provisioning andmanagement framework 206, which includes adevice management agent 208 and aclient provisioning agent 210. For one embodiment, thedevice management agent 208 and theclient provisioning agent 210 are managed by a parameter management frame of the provisioning andmanagement framework 206. - The
device management server 202 of thenetwork 104 communicates with thedevice management agent 208 of the client device viacommunication link 212. For one embodiment, the signal protocol between theservers agents management framework 206 also receives sync signals, in the form of WAP Push, from thedevice management server 202 viaconnection link 214 and provides the incoming device management signals to thedevice management agent 208 viaconnection link 218. Likewise, the provisioning andmanagement framework 206 further receives provisioning signals, in the form of WAP Push, from theclient provisioning server 204 viaconnection link 216 and provide the incoming provisioning signals to theclient provisioning agent 210 viaconnection link 220. - The client device further includes a
device management engine 222 communicating with thedevice management agent 208 viaconnection link 224 and adevice management tree 226 communicating with the device management engine viacommunication link 228. - Referring to
FIG. 3 , there is provided a block diagram illustrating exemplary internal components of various servers, controllers and devices that may utilize the present invention, such as theclient device 102 and theserver 110 ofFIG. 1 . The exemplary embodiment includes one ormore transceivers 302, aprocessor 304, amemory portion 306, one or more output devices 308, and one or more input devices 310. Each embodiment may include a user interface that comprises at least one input device 310 and may include one or more output devices 308. Eachtransceiver 302 may be a wired transceiver, such as an Ethernet connection, or a wireless connection such as an RF transceiver. Theinternal components 300 may further include acomponent interface 312 to provide a direct connection to auxiliary components or accessories for additional or enhanced functionality. Theinternal components 300 preferably include apower supply 314, such as a battery, for providing power to the other internal components while enabling the server, controller and/or device to be portable. - Referring to the
client device 102 and theserver 110 ofFIG. 1 , each machine may have a different set of internal components. Eachserver 110 may include atransceiver 302, aprocessor 304, amemory 306 and apower supply 314 but may optionally include the otherinternal components 300 shown inFIG. 2 . Thememory 306 of theservers 110 should include high capacity storage in order to handle large volumes of media content. Eachclient device 102 must include atransceiver 302, aprocessor 304, amemory 306, one or more output devices 308, one or more input devices 310 and apower supply 314. Due to the mobile nature of theclient device 102, thetransceiver 302 should be wireless and the power supply should be portable, such as a battery. Thecomponent interface 312 is an optional component of theclient device 102. - 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 alocation circuit 328. Examples of thelocation 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 theinternal components 300 may be used by theprocessor 304 to store and retrieve data. The data that may be stored by thememory 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 theinternal components 300, communication with external devices via thetransceiver 302 and/or thecomponent interface 312, and storage and retrieval of applications and data to and from thememory 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 thememory 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 thememory portion 306. Each component of theinternal 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 theinternal components 300 may be combined or integrated so long as the functions of these components may be performed by the client device. - Referring to
FIG. 4 , there is provided a flow diagram representing anexemplary operation 400 of a client device. Theexemplary operation 400 begins atstep 402. Next, the client device receives a client provisioning document, such as an OMA CP document, from asource 406, such as theOMA CP server 204, and reads the client provisioning document atstep 404. The client device then identifies a characteristic from the client provisioning document atstep 408. - 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 atstep 410. If the characteristic only includes a URI parameter, then the client device appends the URI parameter atstep 412, stores the URI parameter by pushing it down on a URI stack atstep 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 atstep 416. If not, then the client device sets the OP parameter to “REPLACE” atstep 418 and thereafter determines whether the characteristic includes aDATA 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 atstep 422 and sets device management tree (DMT) data atstep 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 atstep 424, the client device provides the data to the device management tree 226 (shown inFIG. 2 ). Thereafter, the client device returns to step 408 where the client device identifies the next characteristic from the client provisioning document. The exemplary operation continues until all characteristics of the client provisioning document have been reviewed. - Referring to
FIG. 5 , there is provided a code diagram illustrating anexemplary data format 500 that may be processed by the client device. It is to be understood thatFIG. 5 merely represents an example of the type of data format that may be utilized by the embodiments shown and described herein, and the type of data format is not limited to the one shown inFIG. 5 .FIG. 5 shows an example of package setting log parameters which may be encoded in accordance with the present invention. Thefirst line 502 of theexemplary data format 500 identifies the characteristic type of a first node to be SYNCML-DM. The second line 504 of theexemplary data format 500 sets the URI parameter of the first node to be “./DevDetail/Ext/Conf/Log”. - 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, thethirteenth line 526 refers back toline 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.
Claims (13)
1. A method for a client device of a communication system comprising:
receiving a client provisioning document from a source;
identifying a device management characteristic from the client provisioning document; and
storing data based on the device management characteristic of the client provisioning document to a device management tree.
2. The method of claim 1 , wherein receiving a client provisioning document from a source includes receiving the client provisioning document from a remote server over a wireless communication link.
3. The method of claim 1 , wherein identifying a device management characteristic from the client provisioning document includes identifying at least one of a URI parameter, an OP parameter and a DATA parameter corresponding to the device management characteristic.
4. The method of claim 3 , further comprising appending the URI parameter if the client provisioning document only includes the URI parameter.
5. The method of claim 3 , further comprising setting the OP parameter to a REPLACE status if the device management characteristic does not include the OP parameter.
6. The method of claim 3 , further comprising resetting the DATA parameter to a default value if the device management characteristic does not include the DATA parameter.
7. A client device of a communication system comprising:
a provisioning and management framework configured to receive a client provisioning document, the client provisioning document includes a device management characteristic.
8. The client device of claim 7 , wherein the provisioning and management framework receives the client provisioning device from a remote server over a wireless communication link.
9. The client device of claim 7 , wherein the device management characteristic corresponds to at least one of a URI parameter, an OP parameter and a DATA parameter.
10. The client device of claim 9 , wherein the provisioning and management framework appends the URI parameter if the client provisioning document only includes the URI parameter.
11. The client device of claim 9 , wherein the provisioning and management framework sets the OP parameter to a REPLACE status if the device management characteristic does not include the OP parameter.
12. The client device of claim 9 , wherein the provisioning and management framework resets the DATA parameter to a default value if the device management characteristic does not include the DATA parameter.
13. The client device of claim 7 , further comprising a device management engine communicating with the provisioning and management framework, the device management engine being configured to update a device management tree based on the device management characteristic of the client provisioning document.
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/826,833 US20050232175A1 (en) | 2004-04-16 | 2004-04-16 | System and method for provisioning device management tree parameters over a client provisioning protocol |
US11/024,895 US7499950B2 (en) | 2004-04-16 | 2004-12-29 | System and method for providing data storage through a device management tree using non-device management agents |
PCT/US2005/009264 WO2005107217A1 (en) | 2004-04-16 | 2005-03-21 | System and method for provisioning device management tree parameters over a client provisioning protocol |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/826,833 US20050232175A1 (en) | 2004-04-16 | 2004-04-16 | System and method for provisioning device management tree parameters over a client provisioning protocol |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/024,895 Continuation-In-Part US7499950B2 (en) | 2004-04-16 | 2004-12-29 | System and method for providing data storage through a device management tree using non-device management agents |
Publications (1)
Publication Number | Publication Date |
---|---|
US20050232175A1 true US20050232175A1 (en) | 2005-10-20 |
Family
ID=34963302
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/826,833 Abandoned US20050232175A1 (en) | 2004-04-16 | 2004-04-16 | System and method for provisioning device management tree parameters over a client provisioning protocol |
US11/024,895 Active 2025-12-14 US7499950B2 (en) | 2004-04-16 | 2004-12-29 | System and method for providing data storage through a device management tree using non-device management agents |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/024,895 Active 2025-12-14 US7499950B2 (en) | 2004-04-16 | 2004-12-29 | System and method for providing data storage through a device management tree using non-device management agents |
Country Status (2)
Country | Link |
---|---|
US (2) | US20050232175A1 (en) |
WO (1) | WO2005107217A1 (en) |
Cited By (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20060020947A1 (en) * | 2004-07-01 | 2006-01-26 | Mika Hallamaa | Arranging management operations in management system |
US20060031449A1 (en) * | 2004-07-01 | 2006-02-09 | Mika Hallamaa | Selection of management method |
US20060203722A1 (en) * | 2005-03-14 | 2006-09-14 | Nokia Corporation | System and method for managing performance of mobile terminals via remote diagnostics |
US20070043692A1 (en) * | 2005-08-19 | 2007-02-22 | Samsung Electronics Co., Ltd. | System and method for managing XDM service information |
CN100391168C (en) * | 2006-03-08 | 2008-05-28 | 华为技术有限公司 | Method, system and terminal for synchronously marking language terminal equipment of terminal management |
US20080271023A1 (en) * | 2006-10-20 | 2008-10-30 | Vodafone Group Plc | Device management |
WO2008150145A2 (en) | 2007-06-08 | 2008-12-11 | Samsung Electronics Co., Ltd. | System and method for controlling wireless network access information in using removable external modem |
WO2009005203A1 (en) * | 2007-07-03 | 2009-01-08 | Lg Electronics Inc. | Mobile e-mail management objects |
US20090094363A1 (en) * | 2006-08-07 | 2009-04-09 | Huawei Technologies Co., Ltd. | Method, system, client and server for locating operation nodes in communication system |
US20090280794A1 (en) * | 2006-04-20 | 2009-11-12 | Frederic Desruelle | Device management system for remotely accessing terminal equipments |
US20100325740A1 (en) * | 2008-02-13 | 2010-12-23 | Osvaldo Diaz | Managing electronic devices using an electronic device as a root of trust |
US20100332639A1 (en) * | 2008-02-13 | 2010-12-30 | Osvaldo Diaz | Providing Manageability To An Electronic Device That Supports Location Limited Manageability Functionality |
EP2429225A1 (en) * | 2009-05-06 | 2012-03-14 | ZTE Corporation | Method for provisioning parameters of terminal, system thereof, and terminal management device |
US8392545B2 (en) | 2004-07-01 | 2013-03-05 | Nokia Corporation | Device management system |
Families Citing this family (33)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8479189B2 (en) | 2000-11-17 | 2013-07-02 | Hewlett-Packard Development Company, L.P. | Pattern detection preprocessor in an electronic device update generation system |
US7409685B2 (en) | 2002-04-12 | 2008-08-05 | Hewlett-Packard Development Company, L.P. | Initialization and update of software and/or firmware in electronic devices |
US7974613B1 (en) * | 2003-06-16 | 2011-07-05 | Hewlett-Packard Development Company, L.P. | Device capability determination for a mobile device |
US8555273B1 (en) | 2003-09-17 | 2013-10-08 | Palm. Inc. | Network for updating electronic devices |
US20070180127A1 (en) * | 2003-11-11 | 2007-08-02 | Nokia Corporation | Preconfigured syncml profile categories |
US7756968B1 (en) | 2003-12-30 | 2010-07-13 | Sap Ag | Method and system for employing a hierarchical monitor tree for monitoring system resources in a data processing environment |
US7822826B1 (en) | 2003-12-30 | 2010-10-26 | Sap Ag | Deployment of a web service |
US7725572B1 (en) | 2003-12-30 | 2010-05-25 | Sap Ag | Notification architecture and method employed within a clustered node configuration |
US7526550B2 (en) * | 2004-03-26 | 2009-04-28 | Sap Ag | Unified logging service with a log viewer |
US20050216585A1 (en) * | 2004-03-26 | 2005-09-29 | Tsvetelina Todorova | Monitor viewer for an enterprise network monitoring system |
US7721266B2 (en) | 2004-03-26 | 2010-05-18 | Sap Ag | Unified logging service with a logging formatter |
US7904895B1 (en) | 2004-04-21 | 2011-03-08 | Hewlett-Packard Develpment Company, L.P. | Firmware update in electronic devices employing update agent in a flash memory card |
US8526940B1 (en) | 2004-08-17 | 2013-09-03 | Palm, Inc. | Centralized rules repository for smart phone customer care |
US7788226B2 (en) * | 2004-12-30 | 2010-08-31 | Sap Ag | Monitoring availability of applications |
US7734737B2 (en) * | 2005-05-26 | 2010-06-08 | Nokia Corporation | Device management with configuration information |
CN100479575C (en) * | 2005-06-30 | 2009-04-15 | 华为技术有限公司 | Method and apparatus for realizing scheduled operation in equipment management |
US20070067384A1 (en) * | 2005-09-21 | 2007-03-22 | Angelov Dimitar V | System and method for web services configuration creation and validation |
US20070100968A1 (en) * | 2005-10-27 | 2007-05-03 | Nokia Corporation | Proprietary configuration setting for server to add custom client identity |
US7870490B2 (en) * | 2005-11-15 | 2011-01-11 | Microsoft Corporation | On-the-fly device configuration and management |
KR20070108425A (en) | 2006-02-06 | 2007-11-12 | 엘지전자 주식회사 | Method for placing a call in voice call continuity and terminal and vcc application server thereof |
CN101080077B (en) * | 2006-05-23 | 2011-07-13 | 华为技术有限公司 | Maintenance method of device management tree and terminal device |
EP2025095A2 (en) | 2006-06-08 | 2009-02-18 | Hewlett-Packard Development Company, L.P. | Device management in a network |
EP2047420A4 (en) | 2006-07-27 | 2009-11-18 | Hewlett Packard Development Co | User experience and dependency management in a mobile device |
KR101401799B1 (en) * | 2007-07-19 | 2014-05-29 | 삼성전자주식회사 | System and method for providing device management service to electrical devices having no broadband communication module |
EP2188734A4 (en) * | 2007-08-08 | 2014-09-24 | Innopath Software Inc | Push and clone configuration management for mobile devices |
CN101505549B (en) * | 2008-02-04 | 2012-08-08 | 华为技术有限公司 | Configuration method and apparatus for terminal equipment |
US20090204578A1 (en) * | 2008-02-12 | 2009-08-13 | Microsoft Corporation | Targeted queries using an oma dm protocol |
US8447332B2 (en) * | 2008-05-02 | 2013-05-21 | Xtify, Inc. | Location-based services platform |
US8819447B2 (en) * | 2010-03-10 | 2014-08-26 | Sprint Communications Company L.P. | Secure storage of protected data in a wireless communication device |
US9467338B2 (en) * | 2010-04-01 | 2016-10-11 | Blackberry Limited | Method for communicating device management data changes |
TWI455520B (en) * | 2010-08-12 | 2014-10-01 | Hon Hai Prec Ind Co Ltd | Customer premises equipment and method for updating equipment parameters of the customer premises equipment |
DE102012000454B4 (en) * | 2012-01-12 | 2015-04-02 | Vodafone Gmbh | Method for self-learning expansion of a configuration computer device and configuration computer device |
US10587551B1 (en) * | 2017-07-13 | 2020-03-10 | Whatsapp Inc. | Techniques for multi-agent messaging |
Citations (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030103484A1 (en) * | 2001-12-03 | 2003-06-05 | Paul Oommen | Apparatus, and associated method, for retrieving mobile-node logic tree information |
US20030204640A1 (en) * | 2002-04-30 | 2003-10-30 | Nokia Corporation | Method and device for management of tree data exchange |
US20040043788A1 (en) * | 2002-08-28 | 2004-03-04 | Guarav Mittal | Management of parameters in a removable user identity module |
US20040123241A1 (en) * | 2002-11-21 | 2004-06-24 | Nokia Corporation | Priorization of management objects |
US20040158619A1 (en) * | 2003-02-10 | 2004-08-12 | Claus Pedersen | Method and apparatus for provisioning content |
US20040261116A1 (en) * | 2001-07-03 | 2004-12-23 | Mckeown Jean Christophe | Broadband communications |
US20050027851A1 (en) * | 2001-05-22 | 2005-02-03 | Mckeown Jean Christophe | Broadband communications |
US20050055453A1 (en) * | 2003-09-08 | 2005-03-10 | Microsoft Corporation | System and method for automatic conversion from WAP client provisioning XML represented objects to OMA DM tree structure represented objects |
US20050166140A1 (en) * | 2004-01-27 | 2005-07-28 | International Business Machines Corporation | Eliminating superfluous namespace declarations and undeclaring default namespaces in XML serialization processing |
Family Cites Families (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020123335A1 (en) * | 1999-04-09 | 2002-09-05 | Luna Michael E.S. | Method and apparatus for provisioning a mobile station over a wireless network |
US6594666B1 (en) | 2000-09-25 | 2003-07-15 | Oracle International Corp. | Location aware application development framework |
US6941560B1 (en) | 2000-12-19 | 2005-09-06 | Novell, Inc. | XML-based integrated services event system |
EP1315330A1 (en) * | 2001-11-21 | 2003-05-28 | Markport Limited | A mobile device provisioning system |
US20040098715A1 (en) * | 2002-08-30 | 2004-05-20 | Parixit Aghera | Over the air mobile device software management |
FI116958B (en) * | 2003-07-01 | 2006-04-13 | Nokia Corp | Determination of management nodes in a device management system |
US20050114504A1 (en) * | 2003-07-09 | 2005-05-26 | Sunil Marolia | Carrier network capable of conducting remote diagnostics in a mobile handset |
US8694620B2 (en) * | 2003-09-08 | 2014-04-08 | Microsoft Corporation | System and method for an OMA DM extension to manage mobile device configuration settings |
-
2004
- 2004-04-16 US US10/826,833 patent/US20050232175A1/en not_active Abandoned
- 2004-12-29 US US11/024,895 patent/US7499950B2/en active Active
-
2005
- 2005-03-21 WO PCT/US2005/009264 patent/WO2005107217A1/en active Application Filing
Patent Citations (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050027851A1 (en) * | 2001-05-22 | 2005-02-03 | Mckeown Jean Christophe | Broadband communications |
US20040261116A1 (en) * | 2001-07-03 | 2004-12-23 | Mckeown Jean Christophe | Broadband communications |
US20030103484A1 (en) * | 2001-12-03 | 2003-06-05 | Paul Oommen | Apparatus, and associated method, for retrieving mobile-node logic tree information |
US20030204640A1 (en) * | 2002-04-30 | 2003-10-30 | Nokia Corporation | Method and device for management of tree data exchange |
US20040043788A1 (en) * | 2002-08-28 | 2004-03-04 | Guarav Mittal | Management of parameters in a removable user identity module |
US20040123241A1 (en) * | 2002-11-21 | 2004-06-24 | Nokia Corporation | Priorization of management objects |
US20040158619A1 (en) * | 2003-02-10 | 2004-08-12 | Claus Pedersen | Method and apparatus for provisioning content |
US20050055453A1 (en) * | 2003-09-08 | 2005-03-10 | Microsoft Corporation | System and method for automatic conversion from WAP client provisioning XML represented objects to OMA DM tree structure represented objects |
US20050166140A1 (en) * | 2004-01-27 | 2005-07-28 | International Business Machines Corporation | Eliminating superfluous namespace declarations and undeclaring default namespaces in XML serialization processing |
Cited By (27)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20060020947A1 (en) * | 2004-07-01 | 2006-01-26 | Mika Hallamaa | Arranging management operations in management system |
US20060031449A1 (en) * | 2004-07-01 | 2006-02-09 | Mika Hallamaa | Selection of management method |
US8073960B2 (en) | 2004-07-01 | 2011-12-06 | Nokia Corporation | Arranging management operations in management system |
US8392545B2 (en) | 2004-07-01 | 2013-03-05 | Nokia Corporation | Device management system |
US20060203722A1 (en) * | 2005-03-14 | 2006-09-14 | Nokia Corporation | System and method for managing performance of mobile terminals via remote diagnostics |
US20070043692A1 (en) * | 2005-08-19 | 2007-02-22 | Samsung Electronics Co., Ltd. | System and method for managing XDM service information |
US8543719B2 (en) * | 2005-08-19 | 2013-09-24 | Samsung Electronics Co., Ltd | System and method for managing XDM service information |
CN100391168C (en) * | 2006-03-08 | 2008-05-28 | 华为技术有限公司 | Method, system and terminal for synchronously marking language terminal equipment of terminal management |
US20090280794A1 (en) * | 2006-04-20 | 2009-11-12 | Frederic Desruelle | Device management system for remotely accessing terminal equipments |
US8095128B2 (en) * | 2006-04-20 | 2012-01-10 | International Business Machines Corporation | Device management system for remotely accessing terminal equipments |
US9009306B2 (en) | 2006-08-07 | 2015-04-14 | Huawei Technologies Co., Ltd. | Method, system, client and server for locating operation nodes in communication system |
US20090094363A1 (en) * | 2006-08-07 | 2009-04-09 | Huawei Technologies Co., Ltd. | Method, system, client and server for locating operation nodes in communication system |
US8356094B2 (en) * | 2006-08-07 | 2013-01-15 | Huawei Technologies Co., Ltd. | Method, system, client and server for locating operation nodes in communication system |
US20080271023A1 (en) * | 2006-10-20 | 2008-10-30 | Vodafone Group Plc | Device management |
US8321864B2 (en) * | 2006-10-20 | 2012-11-27 | Vodafone Group Plc | Device management |
WO2008150145A2 (en) | 2007-06-08 | 2008-12-11 | Samsung Electronics Co., Ltd. | System and method for controlling wireless network access information in using removable external modem |
EP2156609A4 (en) * | 2007-06-08 | 2011-08-17 | Samsung Electronics Ltd | System and method for controlling wireless network access information in using removable external modem |
US20100238988A1 (en) * | 2007-06-08 | 2010-09-23 | Samsung Electronics Co., Ltd. | System and method for controlling wireless network access information in using removable external modem |
US8396138B2 (en) | 2007-06-08 | 2013-03-12 | Samsung Electronics Co., Ltd | System and method for controlling wireless network access information in using removable external modem |
EP2156609A2 (en) * | 2007-06-08 | 2010-02-24 | Samsung Electronics Co., Ltd. | System and method for controlling wireless network access information in using removable external modem |
EP3079306A1 (en) * | 2007-06-08 | 2016-10-12 | Samsung Electronics Co., Ltd. | System and method for controlling wireless network access information in using removable external modem |
WO2009005203A1 (en) * | 2007-07-03 | 2009-01-08 | Lg Electronics Inc. | Mobile e-mail management objects |
US20100332639A1 (en) * | 2008-02-13 | 2010-12-30 | Osvaldo Diaz | Providing Manageability To An Electronic Device That Supports Location Limited Manageability Functionality |
US20100325740A1 (en) * | 2008-02-13 | 2010-12-23 | Osvaldo Diaz | Managing electronic devices using an electronic device as a root of trust |
US8479262B2 (en) | 2008-02-13 | 2013-07-02 | Hewlett-Packard Development Company, L.P. | Managing electronic devices using an electronic device as a root of trust |
EP2429225A1 (en) * | 2009-05-06 | 2012-03-14 | ZTE Corporation | Method for provisioning parameters of terminal, system thereof, and terminal management device |
EP2429225A4 (en) * | 2009-05-06 | 2012-12-05 | Zte Corp | Method for provisioning parameters of terminal, system thereof, and terminal management device |
Also Published As
Publication number | Publication date |
---|---|
US7499950B2 (en) | 2009-03-03 |
US20050234967A1 (en) | 2005-10-20 |
WO2005107217A1 (en) | 2005-11-10 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20050232175A1 (en) | System and method for provisioning device management tree parameters over a client provisioning protocol | |
US7194503B2 (en) | System and method to query settings on a mobile device | |
US8170536B2 (en) | Provisioning content formatting in a mobile device management system | |
US20060143179A1 (en) | Apparatus and method for managing security policy information using a device management tree | |
US7716276B1 (en) | Network that supports user-initiated device management | |
US20060242248A1 (en) | Shortcut generator for services accessible via a messaging service system | |
US8433301B2 (en) | Method and system for automatically providing contents from a service provider to a mobile telephonic terminal | |
WO2006036323A1 (en) | System and method for wireless download capability of media objects from multiple sources | |
CN103002156B (en) | For the technology of dynamicvoice menu | |
US20030065738A1 (en) | Wireless information systems and methods | |
US20160373553A1 (en) | Mobile dialogue system and mobile content delivery solutions | |
CN101480075A (en) | System, apparatus, and method for dynamically configuring application access point settings | |
CN102075539A (en) | Data delivery system and method | |
KR100738040B1 (en) | Method for providing application Program Interface in open mobile business supporting system | |
US8185090B2 (en) | Method and system for provisioning content in a mobile device management system | |
WO2007022676A1 (en) | A system for reporting and obtaining device information and the method therefor | |
US20040040022A1 (en) | Method and apparatus for just-in-time provisioning application-related information at a communication device | |
EP1872525A1 (en) | System and method for discovering wireless mobile applications | |
EP2323311B1 (en) | User interface for SIM card based applications | |
KR100654541B1 (en) | Wireless contents management system and method thereof | |
TWI450571B (en) | Structural data transmission method and system for interactive voice response system | |
lC | _IU/....:: Ie~ _t_ec_h_n_is_ch_e_u_n_iv_e_rs_it_ei_t_ei_nd_h_O_Ve_n _ |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
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 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |