GB2454583A

GB2454583A - Remote management of mobile devices

Info

Publication number: GB2454583A
Application number: GB0820431A
Authority: GB
Inventors: Lasse Koskela; Jukka Pirinen; Harri Salokorpi
Original assignee: Capricode Oy
Current assignee: Capricode Oy
Priority date: 2007-11-09
Filing date: 2008-11-07
Publication date: 2009-05-13
Anticipated expiration: 2028-11-07
Also published as: FI20075792A7; FI121618B; GB2454583B; GB0820431D0; FI20075792A0

Abstract

The invention relates to a device management method and system for wireless management of mobile devices. A database in a device management server belonging to the device management system includes a hierarchical data structure specifying the device profiles of all data processing devices belonging to the device management system. A single device profile includes data required in managing the data processing device. By means of the device profile, the device management sewer converts a macro-level device management instruction into a device-specific command sequence which it sends to the data processing device being managed for execution. The invention enables a device management action to be defined by a command at a general level, suitable for all devices of the system. The device profiles may include device properties and actions, and lower levels of the hierarchy may inherit device profile definitions from higher levels. The hierarchical data structure may be XML.

Description

Device management method and arrangement of a mobile device The invention relates to a device management method and device management system for implementing the device management of mobile devices. The invention also relates to a device profile which is used in the device management system.

Various mobile data processing and communication devices are gaining popularity over devices installed as stationary. Examples of such devices are portable computers, mobile phones and PDAs (Personal Digital Assistant). The above-mentioned small, mobile devices are expected to perform the same tasks as the alternative stationary devices do. In practice, this means that the devices have to be managed via a stationary device. Through management, the operation or operating properties of the device can be changed, complemented or removed.

The operation described above is commonly known as device management.

Device management has the following characteristics, among others: It enables one data processing device or server to remote control at least one other data processing device. By using it, e.g. a data processing device used for device management can disable, complement, remove or change the functional properties of some other data processing device.

The Open Mobile Alliance (OMA), an association promoting the use of mobile communication devices, has published specifications on the maintenance and updating of software in mobile devices wirelessly using the OTA (Over-The-Air) technique. The specifications OMA DM (Device Management) and OMA DS (Data Syncronization) describe some possible ways of implementing the management procedure of mobile devices and the wireless maintenance of files contained by them. Said specifications also describe the SyncML (Synchronization Mark up Language) protocol and how it is utilised in procedures conformable to the standards.

In device management systems based on the OMA OM standard, various types of devices can be managed in accordance with the client-server model described in the standard. A problem is that the device management implementations of data processing devices utilising the management system are different. Data processing devices belonging to the management arrangement can differ from each other e.g. in relation to the device operating system, functionality, data formats and data structures.

Also, the DMA DM standard is for some of its parts open to various interpretations, because of which the data processing devices of various manufacturers can include functionalities differing from each other even though working under the umbrella of one and the same OMA DM standard. In practice, such a situation impels the device management system to handle each device belonging to the device management system one at a time. Adding a new data processing device or changing the functionality of a data processing device already included in the device management has to be done device-specifically.

This can require changes in the device management system e.g. as device-specifically customised software changes.

A device management system of devices according to prior art can cover several different device types, device brands or device versions. With existing management methods, in the worst case, each device type differing from another has to be managed with a different management procedure or instructioning. This slows down managing devices and increases management costs.

The object of the invention is to introduce a device management method and arrangement to be used in the management of data processing devices, by using which the management of data processing devices different of their structure or functionality is simplified and rationalised in the device management system.

The objects of the invention are achieved by utilising in a device management server belonging to the device management system a hierarchically specifying device profile defined to each device belonging to the device management system. The device profile of a single device comprises device management measures and properties possible for the device as hierarchical structural definitions. By using the device profile, the device management server can realise an action related to the device management defined at the macro level by converting the macro- level action by means of the device profile to a command sequence suitable for the single device included in the device management.

An advantage of the invention is that, by means of hierarchical, gradually specifying device type specific profiles, it is possible to conform the interface used in managing the device for all devices included in the device management.

Furthermore, an advantage of the invention is that the user of the device management system will be able to use a uniform management window for alt devices of the management system from which the functional differences and incompatibilities of different devices have been omitted by means of the device profile according to the invention.

Additionally, an advantage of the invention is that, when defining a device management action for a device, the action can be defined by a command defined at a general level, suitable for all the devices of the device management system which, by using the profile according to the invention, is converted into a device-specific command sequence whereby the action defined at said high level can be implemented in the device being the target.

A further advantage of the invention is that, during the creation of management definitions of a new device using a profile according to the invention, only those actions which are both possible for the device in question and desired by the user can be selected for the device being the target of management.

An additional advantage of the invention is that customising the device management system for different device types and different client requirements can be done without software changes in the device management system.

A data structure included in a device management system saved in a data storage medium according to the invention is characterised in that the data structure comprises a device profile hierarchy which comprises at least two device profiles at different hierarchy levels, of which each device profile comprises the device profile definitions of a single data processing device type belonging to the device management system, which device profile definitions a device management server belonging to the device management system is configured to use in the management of said data processing device.

A method for managing a data processing device according to the invention is characterised in that in the device management server belonging to the device management system -a macro instruction executing a device management action of the data processing device is selected -a data processing device specific command sequence corresponding the defined macro instruction of the data processing device is selected, and -the selected command sequence is sent to the mobile data processing device for execution.

A wireless device management system of data processing devices according to the invention is characterised in that it comprises a device management server which compnses a database which compnses hierarchically specifying data processing device type specific device profiles of the data processing devices belonging to the device management system.

Some advantageous embodiments of the invention are described in the dependent claims.

The basic idea of the invention is the following: Hierarchically specifying device type specific device profiles are created in the device management system of devices. At the highest hierarchical level, the base profile, general functionalities or properties possible for the device are presented. Each functionality or property of the base profile is specifiable in the device profile according to the invention as a more detailed functionality or property defined by some low-level profile. A functionality defined by means of the low-level profile can describe e.g. actions possible for the device defined in more detail. If it is possible to execute these actions in the device in alternative ways, these alternatives are shown at the next lower level of the device profile according to the invention. The definitions of the lowest level of the device profile according to the invention include a reference to a device-specific command sequence which executes the defined action related to the device management.

The invention will now be described in detail. However, the detailed description with its examples will only be presented for depicting the invention and the invention will not be limited to the examples depicted. The description refers to the accompanying drawings in which Fig. 1 shows by way of example a device management system which can employ a device profile according to the invention, Fig. 2a shows by way of example a simplified block diagram of the hierarchical device profile according to the invention, Fig. 2b shows a simplified example of the hierarchical device profile applying to one data processing device according to the invention as a description in XML language, and Fig. 3 shows by way of example a flow chart of utilising the device profile according to the invention in performing a device management instruction.

Fig. 1 shows by way of example a mainly wireless device management system 10 implemented in connection with a data transfer network 100, advantageously following the OMA DM standard, For implementing device management, a device management server 110 is connected to the data transfer network 100 advantageously with a fixed connection 115. The device management server 110 advantageously comprises a processing unit according to prior art, volatile and non-volatile memory It also comprises connection means for connecting the device management server 110 via the fixed data transfer connection 115 to a backbone network of the data transfer network 100 and to a computer 120 used in controlling the device management via a connection 125 which can be either a fixed or wireless data transfer connection. The device management server 110 also comprises a database saved in its memory in which device profiles of the data processing devices according to the invention are saved. The device management server 110 also comprises software means which are utilised for using the device profiles according to the invention In the example of Fig. 1, the device management includes several different data processing devices mainly functioning wirelessly. They can be controlled either each device one at a time, in device groups suitably grouped or all devices at the same time. Through the data transfer network, it is possible to control e.g. two mobile phones 140 and 150 of different types which are connected to the data transfer network 100 by means of wireless connections 145 and 115. In the data transfer network shown as an example in Fig. 1, a data processing device 130, which can be e.g. a PDA device or a so-called communicator, has been connected to the data transfer network via a wireless connection 135. Reference 160 designates a portable computer which can connect to the data transfer network 100 either directly or via a connection 165 or through a local wireless computer network.

By means of the computer 120, new data processing device types can be connected to the device management system 10. Then, when connecting the data processing device in the device management system 10, its device profile is saved in the device profile database in the device management server 110. When saving the profile of a new data processing device, a device type specific profile already in the device profile database, created for a corresponding device type, can be advantageously utilised. The device type specific device profile advantageously comprises references to the operating system of the data processing device, all functionalities and data formats possible for the data processing device.

When a new data processing device is connected to the device management system 10, first it is explored if there already exists a device type specific device profile corresponding the data processing device being connected saved in the device profile database. If the device type specific device profile is found, it is selected as the device profile of the new data processing device. If required, the selected device profile can be further edited into a form desired by the client within the limits of options included by the existing device type specific device profile.

After this, the device profile of the new data processing device is saved in the database of the device management server 110. At the same time, the functionalities of the data processing device are set to correspond to the created device profile.

If no device type specific device profile yet exists in the device profile database for the data processing device being connected to the device management system, one is created and saved by the administrator of the device management system in the device profile database. After having created the device type specific device profile, the device profile of the new data processing device can be selected in a way described above.

Device profiles in the database of the device management server 110 can be utilised e.g. in the following ways. For example, a device management measure can be addressed to one certain data processing device, e.g. the device 150.

Then, a device profile of the data processing device according to the invention is searched from the database of the device management server 110 by means of an identifier of the data processing device 150 in question. If there is need to change the settings of the device profile in order to perform the device management measure, the change is made before performing the management measure. When the device profile includes an action required for the management measure being performed, a macro-level instruction describing the management measure is given. The device management server 110 changes this macro-level instruction by means of the selected device profile of the data processing device into a device-specific command sequence which is sent to the data processing device 150 via a wireless data transfer connection. After having received the management command sequence, the data processing device 150 performs the required management measure and reports it to the device management server 110.

Another example of a management measure can relate to either a certain group of data processing devices included in the management or to all data processing devices belonging to the device management system 10. Then, the management measure starts from a given macro-level instruction which applies to all data processing devices selected as the target of the management measure. After the given macro-level instruction, the device management server 110 retrieves the identification data and device profiles of the data processing device being the target of the management measure from the database in its use. By means of the device identification data, the device management server 110 can form, using the device profiles according to the invention, a command sequence exactly suitable for the data processing device being the target of the management measure for executing the defined management measure. Each device- specific command sequence is only sent to the data processing device by means of the device profile of which it has been created. Each data processing device having been the target of the management measure reports the performance of the command sequence to the device management server 110.

Fig. 2a shows an example of a device profile hierarchy 1 according to the invention. In the example of Fig. 2a, the highest level of the device profile hierarchy 1, a base profile, is P1 (Ref. 2). It is possible to specify the device profile included by the base profile P1 in the example of Fig. 2a with low-level device profiles P2 (Ref. 21) or P3 (Ref. 22) belonging to the same device profile hierarchy. In the example of Fig. 2a, the device profile P2 can be further specified with a device profile P4 (Ref. 210) belonging to the next lower level of the device profile hierarchy 1. Correspondingly, the device profile P3 can be further specified either with a device profile P5 (Ref. 220) or a device profile P6 (Ref. 221).

In the example of Fig. 2a, the device profile P1 is the base profile of the device profile hierarchy 1 shown as an example, which profile includes properties and functionalities common for devices belonging to the same device profile hierarchy 1. The base profile P1 according to the example of Fig. 2a comprises as an example a device property X (Ref. 2a) the value of which is A. Furthermore, the base profile P1 of Fig. 2a comprises as an example an action Y (Ref. 2b) and as an example a command sequence Z related to it the value of which is B. It is evident to those skilled in the art that the base profile P1 of Fig. 2a can also comprise other device properties, actions and instruction sequences than the

examples of Fig. 2a.

The highest level of the device profile hierarchy 1, the base profile P1, can be specified either with the device profile P2 or P3 which belong to a hierarchy level lower than the base profile P1 in the device profile hierarchy 1. If the low-level device profile includes a device profile definition which differs from the corresponding device profile definition of the high-level device profile, the low-level device profile definition substitutes the more general device profile definition inherited from the high level in the specified low-level device profile. If the low-level device profile includes a device profile definition which is not included in the device profile higher in the hierarchy, it will be added in the specified, low-level device profile.

If the high-level device profile is complemented with a device profile definition which is not included in one or more low-level profiles at the creation moment of the profile definition, then the change or addition made in the high-level device profile is inherited to the low-level device profiles at the change moment.

If specifying the base profile P1 in the example of Fig. 2a takes place using the device profile P2, then, as a result of this, the original value B of the command sequence Z belonging to the action Y originally defined in the base profile P1 is replaced by a new value C in the device profile P2. Advantageously, the new value C is a more detailed value from the viewpoint of the functionality of the data processing device than the original value B. The other device profile definitions of P1 remain unchanged.

If the device profile P2 is further specified to the device profile P4 at the next level of the device profile hierarchy, then the value A of the device property X belonging to the device profile P1 is replaced by a value H in the device profile P4.

Furthermore, in the device profile P4 is added a device property W not belonging to the high-level device profiles P1 and P2 which is given a value L in the device profile P4. The device profile P4 of the example of Fig. 2a thus comprises the device property X, the value of which is H, the device property W, the value of which is L, and the action Y, the value of the command sequence Z related to it is C. In the example of Fig. 2a, specifying the base profile P1 can also occur using the device profile P3 which is an alternative device profile for the device profile P2.

Then, in the specified device profile P3 the value A of the device property X originally defined in the base profile P1 is replaced by a new value D. No other changes in the settings of the base profile P1 are made, but they are included unchanged to the specified device profile P3 If the device profile P3 is further specified to the device profile P6 of the next lower level in the device profile hierarchy I then the value D of the device property X. included by the device profile P3 is replaced by a value K in the device profile P6.

After specifying, the device profile P6 thus comprises the device property X, the value of which is K, and the action Y, the value of the command sequence Z related to it is B. Alternatively, it is also possible to specify the device profile P3 to the device profile P5. Then, in the device profile P5, F is changed to the value of the command sequence Z related to the action Y and another action Y is added in which G is set as the value of the command sequence W related to it. The specified device profile P5 thus comprises the device property X, the value of which is D, and the action Y, the value of the command sequence Z related to it is F and another action V. the value of the command sequence W related to it is G. The example of Fig. 2a describes only three device profile levels belonging to the device profile hierarchy 1. However, the device profile hierarchy I according to the invention is not limited to the three device profile levels described in Fig. 2a, but the device profile hierarchy can include more device profile levels than shown in Fig. 2a.

The device profiles of the device profile hierarchy 1 of the example of Fig. 2a can comprise e.g. the following definitions. The base profile P1 belonging to the highest level of the device profile hierarchy can advantageously define the operating system of the data transfer device and other settings related to it, common for several data transfer devices. Some examples of possible operating systems of mobile devices, which can be presented as a technical definition at the highest device profile level of the device profile hierarchy, in the base profile, are Symbian OS, Windows Mobile, OS X and Linux.

If the operating system of the data transfer device is e.g. Symbian OS, then in the example of Fig. 2a in the base profile P1 belonging to the highest level of the device profile hierarchy is included a definition on the Symbian OS operating system. Then, the device profiles P2 and P3 of the next lower hierarchical level can advantageously comprise a definition on which Symbian OS based application platform of mobile devices to use in the data processing device. Some examples of possible Symbian OS based application platforms which different device manufacturers use are S60, S80, S90, UIQ and MOAP. A specific application platform can also be divided into different versions which are advantageously presented with their own device profile.

Utilising some suitable application platform or its specific version, device profiles can be formed in the example of Fig. 2a for different device models which belong to the same device management system 10 Such device profiles describing the actions and properties of the device models can be in the example of Fig. 2a e.g. the device profiles P4, P5 and P6 The device model having the device profile P4 has been implemented using the application platform defined in the device profile P2. The device models according to the device profiles P5 and P6 are implemented utilising another application platform defined in the device profile P3.

If one of the above device models has various corresponding model versions, it is possible to create in the hierarchical device profile system I according to the invention more specified device profiles describing the model versions which are related to the device profiles P4, P5 or P6 of the device models at the next lower level of the device profile hierarchy 1. No examples on the device profiles of a product version have been shown in the example of Fig. 2a.

The device profile according to the invention can at one or more levels include both actions and properties included by the original manufacturer of the data processing device in the data processing device during manufacturing and actions programmable in the data processing device by the operator of the device management. There is no need for a party utilising the device profile according to the invention to know the device-specific facilities or commands in detail, because the device profile according to the invention converts an action definition given at the macro level into a device-specific command sequence.

Fig. 2b shows a simplified example in XML language of the device profile hierarchy according to the invention of one data processing device. The description in XML language relates to the hierarchical device profile chain P1 + P2 + P4 shown in Fig. 2a by way of example. However, the invention is not limited to the implementation in XML language, but XML language has been used in Fig. 2b only to illustrate the hierarchical device profile according to the invention.

The data structure according to the invention, the device profile, shown in Fig. 2b is saved in the database in the memory of the device management server 110.

The example of Fig. 2b only shows by way of example the hierarchical structure of the device profile according to the invention by means of some elements in XML language belonging to the device profile. The complete device profile of one data processing device can comprise more actions and properties as elements in each presented device profile than the simplified example in XML language of Fig. 2b shows.

Reference 2 in Fig. 2b designates a description in XML language of the highest hierarchical device profile level of the data processing device belonging to the hierarchical device profile 1 of Fig. 2a, the base profile P1 (Ref. 2). The XML description includes information on the presented device profile hierarchy 1. On the second line of the description presented by way of example, there is the start tag of the device profile <device-profile-definition>. The third line includes the abbreviated name P1 of the base profile between the start and end tags. The fourth line of the description correspondingly includes the whole name of the device profile P1: Base profile'. The fifth line of the description includes the start tag of the action list <actions>. The sixth line presents the start tag of the action V <Y>. The seventh line of the description presents the command sequence named Z related to the action V. The value of the command sequence Z is B. The eighth line comprises the end tag of the action V <IY>. The ninth line comprises the end tag of the action list <factions>. The ninth line comprises the start tag of the device property list <properties>. The tenth line includes the description of the device property named X for which is set the value A. The eleventh line includes the end tag of the device property list </properties>. The twelfth line includes the end tag of the device profile </device-profile-definition>.

Reference 21 shows the device profile P2 as a description in XML language whereby the definitions included by the base profile P1 can be specified. In its principle, the description in XML language corresponds to the procedures presented in connection with the base profile P1. The description of the device profile P2 starts with the start tag <device-profile-definition>. The XML description proceeds as shown above in connection with the description of the device profile P1. However, on the fifth line of the XLM description of the device profile P2, there is a definition on the fact that the device profile P2 by default inherits the definitions comprised by the device profile P1: <inheritProfile>P1 </iriheritProfile>.

These definitions inherited from the device profile P1 can be changed, removed or complemented by means of the definitions included by the device profile P2. If the device profile P2 does not include a change definition for the part of a definition included by the device profile P1, then this definition of the device profile P1 is also included as such in the device profile P2.

An example of the specification included by the low device profile P2 is shown on line eight of the XML description, in which it is presented that the value B of the instruction sequence Z of one action inherited from the device profile P1 is changed in the device profile P2 to the value C. The definition of the device profile P2 ends, as in the device profile P1, to the end tag </device-profile-definitiofl>.

Reference 210 shows the device profile P4 of the next lower hierarchical device profile level as a description in XML language whereby the device profile definitions included by the device profile P2 can further be specified. Also, the description of the device profile P4 starts with the start tag <device-profile-definition> The XML description proceeds as shown above in connection with the description of the device profiles P1 and P2. However, on the seventh line of the XLM description of the device profile P4, there is the definition on the fact that in the device profile P4 the value A of the device property X inherited from the device profile P2 is changed to the value H. With the definition on the eighth line of the device profile P4, the new device property W is added to the device profile P4.

The new device property W is given the value L. The definition of the device profile P4 ends, as described above, to the end tag </device-profile-definition>.

Fig. 3 shows by way of example a flow chart on how to utilise the device profile according to the invention in the device management system 10. The description also utilises Figs. 1, 2a and 2b with their descriptions. The device management system 10 advantageously utilises the OMA DM standard.

In step 30, the device management action is activated for providing a change in one or more wireless data processing devices belonging to the device management system 10. In step 31, a device management action which is wished to be performed is defined. The device management action can be e.g. complementing, removing or changing one or more actions or device properties of the data processing device.

In step 32, those data processing devices in which the device management action is wished to be performed are advantageously defined.

In step 33, device profiles of single data processing devices according to the invention are searched from a database in the memory of the device management server 110 belonging to the device management system 10, e.g. the device profiles 2, 21 and 210 shown in Fig. 2b.

In step 34, a command sequence corresponding to the device management action defined in step 32 is selected by using the most specific existing device profile.

The command sequence advantageously consists of one or more separate commands. If no reference to a suitable command sequence is found in the most specific device profile, then in this situation a command sequence is selected from the high-level device profile which corresponds to the desired device management action.

The command sequence selected in step 35 is sent as a message to the data processing device or devices being the target of management. In step 36, the data processing device performs the action defined by the command sequence. By performing the command sequence, it is possible to advantageously complement, remove or change one or more actions or device properties of the data processing device.

In step 37, the data processing device sends the device management server 110 a message which contains information on performing or not performing the command sequence.

The device management process ends in step 38 in which the device management server 110 is set at stand-by to wait for the next device management action.

Above were described advantageous embodiments of a method and a device according to the invention. The invention is not limited to the above-described solutions, but it is possible to apply the inventive idea with several ways within the limitations set by the claims.

Claims

Claims 1. A data structure of a device management system (10) saved in a data storage medium, characterised in that the data structure comprises a device profile hierarchy (1) which comprises at least two device profiles (2, 21, 210) at different hierarchy levels, of which each device profile comprises device profile definitions (2a, 2b) of a single data processing device (130, 140, 150, 160) belonging to the device management system (10) which device profile definitions a device management server (110) belonging to the device management system (10) is configured to use in the management of said data processing device (130, 140, 150, 160).
2. The data structure according to claim 1, characterised in that the device profile (2, 21, 210) belonging to the data structure comprises -an individual device profile identifier (21) -an individual device profile identifier (2) of a device profile higher in the device profile hierarchy than the device profile identifier and -device profile definitions which comprise -at least one device property (2a) and -at least one action definition (2b).
3. The data structure according to claim 2, characterised in that the action definition (2b) comprises at least one management measure definition which comprises a reference to at least one command sequence.
4. The data structure according to claim 2, characterised in that the device profile (21) of a lower device profile hierarchy level is configured to inherit the device profile definitions (2a, 2b) of the device profile (2) of the high device profile hierarchy level.
5. The data structure according to claim 4, characterised in that a change made in the device profile definition (21b) of the device profile (21) of the lower device profile hierarchy level is configured to replace the device profile definition (2b) inherited from the previous higher device profile hierarchy level (2).
6. The data structure according to claim 4, characterised in that a new device profile definition (210a2) added to the device profile (210) of the lower device profile hierarchy level, which will not be inherited from the device profile (2, 21) higher in the device profile hierarchy, is configured to be added only to the device profile (210) of the lower device profile hierarchy level.
7. The data structure according to any one of claims 1-6, characterised in that the device profile is the device profile of a mobile device.
8. The data structure according to claim 1, characterised in that the data storage medium is the device management server (110) of the device management system (10).
9. A method for managing a data processing device (130, 140, 150, 160), in which method, in a device management server (110) of a device management system (10) -at least one executable device management action is defined (31) and -at least one data processing device being the target of device management action is defined (32), characterised in that in the method in the device management server -a macro instruction executing the device management action of the data processing device is selected (33) -a data processing device specific command sequence (21b) corresponding the defined macro instruction of the data processing device is selected (34) and -the selected command sequence is sent to the data processing device for execution (35, 36).
10. The method according to claim 9, characterised in that the macro instruction is selected from a device profile (2, 21, 210) of the data processing device saved in the device management server (110).
11. The method according to claim 10, characterised in that the macro instruction is executed by a reference to a command sequence related to the macro instruction in the device profile of the data processing device.
12. The method according to claim 9, characterised in that the method is used for managing mobile data processing devices (130, 140, 150, 160).
13. A wireless device management system (10) of data processing devices, which comprises -a device management server (110) and -data processing devices (130, 140, 150, 160), characterised in that the device management server (110) comprises a database which comprises hierarchically specifying data processing device specific device profiles (2, 21, 210) of the data processing devices belonging to the device management system (10).
14. The device management system according to claim 13, characterised in that the device profiles (2, 21, 210) are saved in the database data processing device type specifically.
15. The device management system according to claim 14, characterised in that the device profile comprises actions (2b) and device properties (2a) allowed for the data processing device.
16. The device management system according to claim 14, characterised in that, in it, the device profile (21) of a lower device profile hierarchy level of the single data processing device is configured to inherit the device profile definitions (2a, 2b) of the device profile (2) of a higher device profile hierarchy level.
17. The device management system according to claim 14, characterised in that, in it, a change made in the device profile definition (21b) of the device profile (21) of a lower device profile hierarchy level is configured to replace the device profile definition (2b) inherited from a previous higher device profile hierarchy level (2).
18. The device management system according to claim 17, characterised in that a new device profile definition (210a2) added to the device profile (210) of the lower device profile hierarchy level, which will not be inherited from the device profile (2, 21) higher in the device profile hierarchy, is configured to be added only to the device profile (210) of the lower device profile hierarchy level.
19. The device management system according to any one of claims 13-17, characterised in that the data processing devices (130, 140, 150, 160) are mobile devices.
20. A data structure of a device management system substantially as any one embodiment herein described with reference to the accompanying drawings.
21. A method for managing a data processing device substantially as any one embodiment herein described with reference to the accompanying drawings.
22. A wireless device management system substantially as any one embodiment herein described with reference to the accompanying drawings.