Method for Configuring an Electronic Device

• US 20070226749A1
• Filed: 02/14/2004
• Published: 09/27/2007
• Est. Priority Date: 02/14/2004
• Status: Active Grant

• Current Assignee: Nokia Technologies Oy (Nokia Corporation)
• Original Assignee: Nokia Corporation
• Inventors: Pedersen, Claus, Hansen, Jacob
• Granted Patent: US 8,341,302 B2
• Time in Patent Office: Days
• US Class Current: 719/313
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04W 8/22 Processing or transfer of terminal data, e.g. status or physical capabilities
• CPC Class Codes: H04W 8/245 from a network towards a terminal
• CPC Class Codes: H04W 80/00 Wireless network protocols or protocol adaptations to wireless operation

Abstract

A method for automatically configuring an electronic device Including receiving at an electronic device a command identifying first data; automatically determining a property of the identified first data; automatically identifying an executable from the determined property; and operating on the identified first data using the identified executable.

Claims

1. A method comprising:

receiving at an electronic device a command identifying first data;

automatically determining a property of the identified first data;

automatically identifying an executable from the determined property; and

operating on the identified first data using the identified executable.

2. A method as claimed in claim 1, wherein the determined property of the identified data indicates a content type.

3. A method as claimed in claim 1, wherein the command contains an identifier of the first data.

4. A method as claimed in claim 3, wherein the identifier identifies a node of a hierarchical nodular data structure.

5. A method as claimed in claim 4, wherein the command is an exec command and the identifier is a URI contained within a source element, which is contained within the exec command.

6. A method as claimed in claim 1, wherein the command is received as XML code.

7. A method as claimed in claim 6, wherein the command is a SyncML command.

8. A method as claimed in claim 1, wherein the identified first data is stored at the mobile device.

9. A method as claimed in claim 6, wherein the identified first data is stored as a first leaf node of a hierarchical nodular data structure.

10. A method as claimed in claim 9, wherein each leaf node of the hierarchical nodular data structure has properties and the step of determining the content type uses the properties of the first leaf node.

11. A method as claimed in claim 9, wherein each leaf node of the hierarchical nodular data structure has metadata and the step of determining the content type uses the first leaf node'"'"'s metadata.

12. A method as claimed in claim 1, wherein the step of determining the content type uses the value of a Format element and/or the value of a Type element associated with the first data.

13. A method as claimed in claim 1 further comprising associating a plurality of different executables with each of a plurality of different properties.

14. A method as claimed in claim 11, wherein the step of automatically identifying an executable from the determined property comprises identifying the executable associated with the determined property.

15. A method as claimed in claim 13, wherein the plurality of different executables are stored in the electronic device.

16. A method as claimed in claim 1, further comprising, before receiving the command identifying the first data, receiving commands for creating a hierarchical nodular data structure including the first data at the electronic device.

17. A method comprising:

transferring code comprising a command to an electronic device, wherein the command identifies a first leaf node of a hierarchical nodular data structure;

determining a property of the identified first leaf node;

identifying an executable from the determined property; and

operating on data stored at the identified first leaf node using the identified executable.

18. A method, comprising:

receiving re-usable code at an electronic device wherein the code comprises;

commands for creating at the electronic device a hierarchical nodular data structure, having leaf nodes and interior nodes, that comprises first data stored at a first leaf node; and

a first command identifying the first leaf node;

determining a property of the identified first leaf node;

identifying an executable from the determined property; and

operating on the first data stored at the first leaf node using the identified executable.

19. An electronic device, comprising:

a memory for storing first data;

a receiver for receiving a command identifying the first data; and

a processor, operable to determine a property of the identified first data;

identify an executable from the determined property,

and to operate on the identified data using the identified executable.

20. A mobile cellular telephone as claimed in claim 19, wherein the receiver is for receiving set-up code, and the processor is operable to interpret the received set-up code to create a hierarchical nodular data structure, having leaf nodes and interior nodes, that comprises a first leaf node storing the first data.

21. A mobile cellular telephone as claimed in claim 20, further wherein the processor is operable to interpret a first command within the received set-up code to determine a property of the leaf node identified by the first command.

22. A data structure, comprising:

code identifying first data and specifying execution of an unidentified executable on the first data.

23. A data structure as claimed in claim 22, wherein the code further specifies the transfer of the first data to an electronic device.

25. A method, comprising:

using a data structure as claimed in claim 22.

26. A method comprising:

setting-up an electronic device using a data structure as claimed in claim 22.

27. A method comprising:

re-using the data structure as claimed in claim 22, to set-up different electronic devices.

28. A server for storing and transmitting the data structure as claimed in claim 22.

24. A data structure, comprising:

commands for creating at an electronic device a hierarchical nodular data structure, having leaf nodes and interior nodes, that comprises first data stored at a first leaf node; and

a first command identifying the first leaf node that specifies execution of an unidentified executable on the first data stored at the first node.

29. A system, comprising:

means for creating a data structure for re-use in setting up different electronic devices by associating each one of a plurality of user friendly commands with different code portions, each of which includes one or more commands.

31. A system as claimed in claim 29, wherein a first user friendly command is associated with XML code comprising only a SyncML Add command.

32. A system as claimed in claim 29, wherein a second user friendly command is associated with XML code comprising a SyncML Add command followed by a SyncML Exec command.

33. A system as claimed in claim 29, wherein a third user friendly command is associated with XML code comprising a SyncML Add command followed by a SyncML exec command followed by SyncML Delete command.

30. (canceled)

34. An electronic device, comprising:

means for storing first data;

means for receiving a command identifying the first data;

means for determining a property of the identified first data;

means for identifying an executable from the determined property; and

means for operating on the identified data using the identified executable.

35. A method, comprising:

transmitting code identifying first data and specifying execution of an unidentified executable on the first data.

36. A method, comprising:

transmitting commands for creating a hierarchical nodular data structure, having leaf nodes and interior nodes, that comprises first data stored at a first leaf node; and

transmitting a first command identifying the first leaf node that specifies execution of an unidentified executable on the first data stored at the first node.

37. A server, comprising:

a memory for storing a code identifying first data and specifying execution of an unidentified executable on the first data.

38. A server as claimed in claim 37, wherein the code is for setting up an electronic device.

39. A server as claimed in claim 37, wherein the code is for re-use in setting up different electronic devices.

40. A server, comprising:

a memory for storing commands for creating at an electronic device a hierarchical nodular data structure, having leaf nodes and interior nodes, that comprises first data stored at a first leaf node, and for storing a first command identifying the first leaf node that specifies execution of an unidentified executable on the first data stored at the first node.

41. Software, comprising:

means for automatically determining a property of a received command identifying first data;

means for automatically identifying an executable from the determined property; and

means for enabling the identified first data to be operated on using the identified executable.

42. A computer program, comprising:

means for creating a data structure for re-use in setting-up different electronic devices by associating each one of a plurality of user friendly commands with different code portions, each of which includes one or more commands.