MANAGING SENSOR AND/OR ACTUATOR DEVICES

Abstract

A method is disclosed, performed by at least a first apparatus, for managing at least a second apparatus, the second apparatus being a sensor and/or actuator device or a part thereof, the method comprising: obtaining identifier information of the second apparatus and obtaining positioning information associated with the identifier information and indicative of a position of the second apparatus; determining updated positioning information of the second apparatus at least based on an obtained radio measurement taken by the second apparatus; and at least based on the updated positioning information of the second apparatus, determining whether the second apparatus has been relocated and/or updating the positioning information associated with the identifier information of the second apparatus.

Claims

1. A method, performed by at least a first apparatus, for managing at least a second apparatus, the second apparatus being a sensor and/or actuator device or a part thereof, the method comprising: obtaining identifier information of the second apparatus and obtaining positioning information indicative of a position of the second apparatus and associated with the identifier information; determining updated positioning information of the second apparatus at least based on an obtained radio measurement taken by the second apparatus; and at least based on the updated positioning information of the second apparatus, determining whether the second apparatus has been relocated and/or updating the positioning information associated with the identifier information of the second apparatus.

2. The method of claim 1, further comprising: obtaining sensor data from the second apparatus and/or providing actuator data to the second apparatus.

3. The method of claim 1, wherein the identifier information of the second apparatus is obtained from a third apparatus, the third apparatus having obtained the identifier information from the second apparatus.

4. The method of claim 3, wherein the identifier information is obtained at the third apparatus from the second apparatus based on radio-frequency identification technology.

5. The method of claim 1, wherein the obtained positioning information indicative of a position of the second apparatus is obtained from a third apparatus.

6. The method of claim 1, wherein the obtained positioning information indicative of a position of the second apparatus is determined by positioning a third apparatus.

7. The method of claim 6, wherein the positioning of the third apparatus is based on at least one of a cellular communication system; a non-cellular communication system; and/or a global satellite navigation system.

8. The method of claim 3, wherein the third device communicates with the first apparatus at least in part based on at least one of a cellular communication system; and/or a non-cellular communication system.

9. The method of claim 3, wherein the third apparatus is a mobile device or a part thereof.

10. The method of claim 1, further comprising: obtaining, from the second apparatus, identifier information of the second apparatus and a radio measurement taken by the second apparatus, associating the obtained positioning information with the obtained radio measurement.

11. The method of claim 1, wherein the second apparatus communicates with the first apparatus at least in part via a low power wide area network.

12. The method of claim 1, wherein the radio measurements taken by the second apparatus are based on signals of a low power wide area network.

13. The method of claim 11, wherein the low power wide area network is based on at least one of: a chirp spread spectrum based system; a LoRa based system; an ultra narrow band based system; a Sigfox system; a Telensa system; a NarrowBand-IoT system; an Nwave system; or a Weightless system.

14. The method of claim 1, wherein the first and the third apparatus communicate at least in part via a first communication system and wherein the first and the second apparatus communicate at least in part via a second communication system, wherein the second communication system utilizes a lower data rate and/or allows for a lower power consumption for communication than the first communication system.

15. The method of claim 1, wherein the first apparatus provides or triggers providing an alert, in case it is determined that the second apparatus has been relocated.

16. The method of claim 1, wherein the first apparatus is a server or a part thereof.

17. The method of claim 1, wherein the method is performed for a plurality of second apparatuses.

18. A method for supporting managing at least a second apparatus at a first apparatus, the second apparatus being a sensor and/or actuator device, the method performed by the second apparatus, the method comprising: providing identifier information of the second apparatus to a third apparatus; taking a radio measurement; providing identifier information of the second apparatus and the radio measurement to the first apparatus; providing sensor data to the first apparatus and/or obtaining actuator data from the first apparatus; and automatically and repeatedly taking further radio measurements and providing the further taken radio measurements to the first apparatus.

19. (canceled)

20. (canceled)

21. An apparatus configured to manage at least a second apparatus, the second apparatus being a sensor and/or actuator device or a part thereof, the apparatus comprising at least one processor and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus; obtain identifier information of the second apparatus and obtain positioning information indicative of a position of the second apparatus and associated with the identifier information; determine updated positioning information of the second apparatus at least based on an obtained radio measurement taken by the second apparatus; and at least based on the updated positioning information of the second apparatus, determine whether the second apparatus has been relocated and/or update the positioning information associated with the identifier information of the second apparatus.

22. (canceled)

23. (canceled)

24. (canceled)

25. The apparatus of claim 21, wherein the at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to: obtain sensor data from the second apparatus and/or provide actuator data to the second apparatus.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0108] FIG. 1 is a block diagram of a system of exemplary apparatuses according to the different aspects;

[0109] FIG. 2 is a block diagram of the server of FIG. 1;

[0110] FIG. 3 is a block diagram of the sensor and/actuator device of FIG. 1;

[0111] FIG. 4 is a block diagram of the mobile device of FIG. 1;

[0112] FIG. 5 is a flow chart illustrating the sending and receiving of information between the apparatuses when performing exemplary methods according to the different aspects;

[0113] FIG. 6 is a flow chart illustrating an exemplary embodiment of a (first) method according to the first aspect;

[0114] FIG. 7 is a flow chart illustrating an exemplary embodiment of a (second) method according to the second aspect;

[0115] FIG. 8 is a flow chart illustrating an exemplary embodiment of a (third) method according to the third aspect; and

[0116] FIG. 9 is a schematic illustration of examples of tangible storage media according to the invention.

DETAILED DESCRIPTION OF EXAMPLE EMBODIMENTS OF THE INVENTION

[0117] The following description serves to deepen the understanding of the present invention and shall be understood to complement and be read together with the description as provided in the above summary section of this specification.

[0118] FIG. 1 is a block diagram of a system 1 of a first apparatus 10, which is in this case a server, such as a computer cloud, a second apparatus 20, which is in this case an IoT sensor and/or actuator device and a third apparatus 30, which is in this case a mobile device such as a cellular phone, a personal digital assistant, a laptop computer, a tablet computer or a wearable. In the following, the apparatuses 10, 20 and 30 will be referred to as a server 10, sensor/actuator device 20 and mobile device 30 as examples apparatuses according to the invention. The apparatuses may separately or together perform exemplary embodiments of the different methods according to the invention. Further details of the server 10, the sensor/actuator device 20 and the mobile device 30 are described with respect to FIGS. 2, 3 and 4, respectively, which are exemplary block diagrams of the respective apparatuses.

[0119] Server 10 may be a server located remote from sensor/actuator device 20. Mobile device 30 may be at least for a certain time in the proximity (e.g. within a few meters or centimeters) of sensor/actuator device 30.

[0120] Turning now to FIG. 2, the server 10 comprises a processor 11. Processor 11 may represent a single processor or two or more processors, which are for instance at least partially coupled, for instance via a bus. Processor 11 executes a program code stored in program memory 12 (for instance program code causing the server to perform embodiments of the (first) method according to the first aspect of the invention, when executed on processor 11), and interfaces with a main memory 13. Some or all of memories 12 and 13 may also be included into processor 11. One of or both of memories 12 and 13 may be fixedly connected to processor 11 or at least partially removable from processor 11. Program memory 12 may for instance be a non-volatile memory. It may for instance be a FLASH memory (or a part thereof), any of a ROM, PROM, EPROM and EEPROM memory (or a part thereof) or a hard disc (or a part thereof), to name but a few examples. Program memory 12 may also comprise an operating system for processor 11. Main memory 13 may for instance be a volatile memory. It may for instance be a RAM or DRAM memory, to give but a few non-limiting examples. It may for instance be used as a working memory for processor 11 when executing an operating system and/or programs.

[0121] Processor 11 further interfaces with a mass storage 15, which may be part of the server 10 or remote from server 10, and which may for instance be used to store one or more databases.

[0122] For instance, server 10 may store, in a database, collected information from crowd sourcing processes. The database may store identification information of sensor/actuator devices 20 associated with respective geographical positions of the respective sensor/actuator device. The database may be updated with updated positioning information, which may be determined as described with respect to the different aspects of the invention.

[0123] Additionally or alternatively, mass storage 15 may be used to store, in a database (e.g. the same or a different database from the database described above) radio measurements of radio signals observed by respective sensor/actuator devices 20 in their environment. This information may be used to create or update a radio map, for instance. The database or the respective radio map can then be used to determine an updated geographical position of the sensor/actuator device 20, also based on radio measurements of radio signals observed by the sensor/actuator device 20.

[0124] Processor 11 further controls a communication interface 14 configured to receive and/or output information. For instance, communication interface 14 may be configured to communicate with (e.g. send and/or receive data to/from) sensor/actuator device 20 and/or mobile device 30. This may for instance comprise receiving identifier information, positioning information, radio measurements and/or sensor data. The communication may for instance be based on a (e.g. partly) wireless connection. The communication interface 14 may thus comprise circuitry such as modulators, filters, mixers, switches and/or one or more antennas to allow transmission and/or reception of signals. In embodiments of the invention, communication interface 14 is inter alia configured to allow communication according to a 2G/3G/4G/5G cellular communication system and/or a non-cellular communication system, such as for instance a WLAN network. Nevertheless, the communication route between server 10 and other apparatuses may equally well at least partially comprise wire-bound portions. For instance, server 10 may be connected to a back-bone of one or more wireless communication systems (associated with sensor/actuator device 20 or mobile device 30) via a wire-bound system such as for instance the internet.

[0125] The components 12-15 of server 10 may for instance be connected with processor 11 by means of one or more serial and/or parallel busses.

[0126] Turning now to FIG. 3, an exemplary block diagram of a sensor/actuator device 20 of FIG. 1 is shown. Similarly to FIG. 2, sensor/actuator device 20 comprises a processor 21. Processor 21 may represent a single processor or two or more processors, which are for instance at least partially coupled, for instance via a bus. Similar to FIG. 2, processor 21 may use program memory 22 and main memory 23 to execute a program code stored in program memory 22 (for instance program code causing sensor/actuator device 20 to perform embodiments of the (second) method according to the second aspect of the invention, when executed on processor 21).

[0127] Processor 21 further interfaces with a sensor 26 and an actuator 27. Processor 21 further controls a communication interface 24 configured to receive and/or send information. For instance, sensor/actuator device 20 may be configured to communicate with server 10 and/or mobile device 30 of system 1 of FIG. 1. This may for instance comprise sending identifier information, radio measurements and/or sensor data of sensor 26. Additionally, this may for instance comprise receiving actuator data for actuator 27. The communication may for instance be based on a (e.g. partly) wireless connection. The communication interface 24 may thus comprise circuitry such as modulators, filters, mixers, switches and/or one or more antennas to allow transmission and/or reception of signals. In embodiments of the invention, communication interface 24 is inter alia configured to allow communication according to a 2G/3G/4G/5G cellular communication system and/or a non-cellular communication system, such as for instance a WLAN network. Specifically, the communication interface 24 may configured for communication over a LPWAN.

[0128] Processor 21 may further control a user interface 25 configured to present information to a user of sensor/actuator device 20 and/or to receive information from such a user. However, it may also be the case, that the sensor/actuator device, in particular in case of e.g. an IoT device, does not comprise any user interface.

[0129] Turning now to FIG. 4, an exemplary block diagram of a mobile device 30 of FIG. 1 is shown. Similarly to FIGS. 2 and 3, mobile device 30 comprises a processor 31. Processor 31 may represent a single processor or two or more processors, which are for instance at least partially coupled, for instance via a bus. Similar to FIGS. 2 and 3 processor 31 may use program memory 32 and main memory 33 to execute a program code stored in program memory 32 (for instance program code causing mobile device 30 to perform embodiments of the (third) method according to the third aspect of the invention, when executed on processor 31).

[0130] Processor 31 further controls a communication interface 34 configured to receive and/or send information. For instance, mobile device 30 may be configured to communicate with server 10 and/or sensor/actuator device 20 of system 1 of FIG. 1. This may for instance comprise sending identifier information and/or positioning information. Additionally, this may for instance comprise receiving identifier information. The communication may for instance be based on a (e.g. partly) wireless connection. The communication interface 34 may thus comprise circuitry such as modulators, filters, mixers, switches and/or one or more antennas to allow transmission and/or reception of signals. In embodiments of the invention, communication interface 34 is inter alia configured to allow communication according to a 2G/3G/4G/5G cellular communication system and/or a non-cellular communication system, such as for instance a WLAN network. Specifically, the communication interface 34 may configured for communication over a LPWAN.

[0131] Processor 31 further controls a user interface 35 configured to present information to a user of mobile device 30 and/or to receive information from such a user, such as manually input position fixes or the like. User interface 34 may for instance be the standard user interface via which a user of mobile device 30 controls other functionality thereof, such as making phone calls, browsing the Internet, etc.

[0132] Processor 31 may further control a GNSS interface 36 configured to receive positioning information of an GNSS such as Global Positioning System (GPS), Galileo, Global Navigation Satellite System (i.e. “Globalnaja Nawigazionnaja Sputnikowaja Sistema”, GLONASS) and Quasi-Zenith Satellite System (QZSS). It should be noted that, even in case mobile device 30 has a GNSS interface 36, a position of the mobile device 30 may additionally or alternatively be determined with positioning technologies based on other approaches, such as the approach based on radio measurements of communication networks supported by the communication interface 34 or inertial sensors, since these technologies may provide a higher accuracy in challenging environments for GNSS-based technologies.

[0133] Exemplary embodiments of the different methods according to the different aspects will now be described together with reference to FIGS. 5-8. Therein, FIG. 5 is a flow chart 50 illustrating the sending and receiving of information between the different apparatuses 10, 20, 30 when performing exemplary methods according to the different aspects. FIG. 6 is flow chart 60 illustrating an exemplary embodiment of a (first) method according to the first aspect, FIG. 7 is flow chart 70 illustrating an exemplary embodiment of a (second) method according to the second aspect, and FIG. 8 is a flow chart 80 illustrating an exemplary embodiment of a (third) method according to the third aspect.

[0134] A procedure for registering a sensor/actuator device 20 with the server 10 may be started at the mobile device 30. In the described embodiment, the sensor/actuator device 20 may comprise an NFC tag storing identifier information (e.g. a unique identifier, e.g. sensor no. 123) of the sensor/actuator device 20. Thus, in action 51 the sensor/actuator device 20 may provide identifier information of the sensor/actuator device 20 to the mobile device 30 (action 71). The mobile device 30 may in turn receive the identifier information from the sensor/actuator device (action 81). For this, an app of the mobile device 30 may read the NFC tag of the sensor/actuator device 20.

[0135] The mobile device 30 determines positioning information by positioning itself (action 82). Since the mobile device 30 is at or close to the sensor/actuator device 20, the position information is indicative of a position of the sensor/actuator device 20. This may be done using the best positioning technology available at the mobile device 30, e.g. any indoor/outdoor, online/offline positioning method e.g. based on one or more of GNSS, WLAN, Bluetooth, a cellular communication system, etc.

[0136] The mobile device 30 then sends the identifier information of the sensor/actuator device 20 (e.g. sensor no. 123) and the determined positioning information indicative of a position of the sensor/actuator device 20 to server 10 (back-end) (actions 52, 53 and action 83). Server 10 obtains the identifier information (action 61) and the (initial) positioning information associated with the identifier information and indicative of a position of the sensor/actuator device 20 (action 62). Thus, server 10 is notified about the registering or installation of a new sensor/actuator device 20.

[0137] Server 10 stores the position information and waits for the respective sensor/actuator device 20 (i.e. sensor/actuator device no. 123) to register itself at the server.

[0138] When the sensor/actuator device 20 is turned on, it connects automatically to the server 10 using, e.g. an NB-IoT connection. Also, the sensor/actuator device 20 scans the radio environment (in this case the NB-IoT environment) and takes an (initial) radio measurement (action 72).

[0139] The sensor/actuator device 20 then provides the identifier information and the (initial) radio measurement to server 10 (actions 54, 55 and action 73). Accordingly, the server 10 obtains the identifier information of the sensor/actuator device 20 and the (initial) radio measurement taken (action 62). This process constitutes a crowd sourcing.

[0140] Server 10 then associates the obtained positioning information with the obtained radio measurement (action 64). In this way, accurate positioning information from the mobile device 30 and the radio environment measurement (e.g. NB-IoT scan information) from the sensor/actuator device 20 can be combined at the back-end. The server 10 can then create and/or update an (e.g. NB-IoT) positioning radio database.

[0141] The sensor/actuator device 20 now sends or reports sensor data from sensor 26 e.g. to server 10 and/or receives actuator data for actuator 27 e.g. from server 10 (actions 56, 57 and action 74). Accordingly, server 10 receives the sensor data from the sensor/actuator device 20 and/or provides actuator data to the sensor/actuator device 20 (action 65). This may be considered as the original or main task of sensor/actuator device 20.

[0142] Sensor/actuator device 20 now automatically and repeatedly takes further radio measurements of the environment and sends the further taken radio measurements to server 10 (action 58 and action 75).

[0143] Based on these obtained (further) radio measurements taken by the sensor/actuator device 20, server 10 determines updated positioning information of sensor/actuator device 20 (action 66).

[0144] Based on the updated positioning information, server 10 can now determine whether the sensor/actuator device 20 has been relocated (action 67) and e.g. provide an alert.

[0145] Additionally or alternatively, server can update the positioning information associated with the identifier information of sensor/actuator device 20 (action 67).

[0146] Thus, if the sensor is relocated (e.g. because the service crew changes the location of the sensor), the described system (in particular server 10) can automatically notice that the sensor/actuator device 20 has moved and can update the stored location of the sensor/actuator device 20 to the back-end system.

[0147] The described approach has in particular the following advantages: [0148] it allows for an easy installation of the sensor/actuator devices 20; [0149] it allows for tracking the location of the sensor/actuator devices 20 in real-time; [0150] it allows for an easy relocation of the sensor/actuator devices 20; and [0151] it allows for creating alerts if a sensor/actuator device 20 is moved.

[0152] FIG. 9 is a schematic illustration of examples of tangible storage media according to the present invention, that may for instance be used to implement program memory of FIGS. 2-4. To this end, FIG. 8 displays a flash memory 90, which may for instance be soldered or bonded to a printed circuit board, a solid-state drive 91 comprising a plurality of memory chips (e.g. Flash memory chips), a magnetic hard drive 92, a Secure Digital (SD) card 93, a Universal Serial Bus (USB) memory stick 94, an optical storage medium 95 (such as for instance a CD-ROM or DVD) and a magnetic storage medium 96.

[0153] The following embodiments shall also be considered disclosed:

[0154] 1. A method, performed by at least a first apparatus, for managing at least a second apparatus, the second apparatus being a sensor and/or actuator device or a part thereof, the method comprising: [0155] obtaining identifier information of the second apparatus and obtaining positioning information indicative of a position of the second apparatus and associated with the identifier information; [0156] determining updated positioning information of the second apparatus at least based on an obtained radio measurement taken by the second apparatus; and [0157] at least based on the updated positioning information of the second apparatus, determining whether the second apparatus has been relocated and/or updating the positioning information associated with the identifier information of the second apparatus.

[0158] 2. The method of embodiment 1, further comprising: [0159] obtaining sensor data from the second apparatus and/or providing actuator data to the second apparatus.

[0160] 3. The method of embodiment 1 or 2, wherein the identifier information of the second apparatus is obtained from a third apparatus, the third apparatus having obtained the identifier information from the second apparatus.

[0161] 4. The method of embodiment 3, wherein the identifier information is obtained at the third apparatus from the second apparatus based on radio-frequency identification technology.

[0162] 5. The method of any of the preceding embodiments, wherein the obtained positioning information indicative of a position of the second apparatus is obtained from a third apparatus.

[0163] 6. The method of any of the preceding embodiments, wherein the obtained positioning information indicative of a position of the second apparatus is determined by positioning a third apparatus.

[0164] 7. The method of embodiment 6, wherein the positioning of the third apparatus is based on at least one of [0165] a cellular communication system; [0166] a non-cellular communication system; and/or [0167] a global satellite navigation system.

[0168] 8. The method of any of embodiments 3 to 7, wherein the third device communicates with the first apparatus at least in part based on at least one of [0169] a cellular communication system; and/or [0170] a non-cellular communication system.

[0171] 9. The method of any of embodiments 3 to 8, wherein the third apparatus is a mobile device or a part thereof.

[0172] 10. The method of any of the preceding embodiments, further comprising: [0173] obtaining, from the second apparatus, identifier information of the second apparatus and a radio measurement taken by the second apparatus, [0174] associating the obtained positioning information with the obtained radio measurement.

[0175] 11. The method of any of the preceding embodiments, wherein the second apparatus communicates with the first apparatus at least in part via a low power wide area network.

[0176] 12. The method of any of the preceding embodiments, wherein the radio measurements taken by the second apparatus are based on signals of a low power wide area network.

[0177] 13. The method of embodiments 11 or 12, wherein the low power wide area network is based on at least one of: [0178] a chirp spread spectrum based system; [0179] a LoRa based system; [0180] an ultra narrow band based system; [0181] a Sigfox system; [0182] a Telensa system; [0183] a NarrowBand-IoT system; [0184] an Nwave system; [0185] a Weightless system.

[0186] 14. The method of any of the preceding embodiments, wherein the first and the third apparatus communicate at least in part via a first communication system and wherein the first and the second apparatus communicate at least in part via a second communication system, wherein the second communication system utilizes a lower data rate and/or allows for a lower power consumption for communication than the first communication system.

[0187] 15. The method of any of the preceding embodiments, wherein the first apparatus provides or triggers providing an alert, in case it is determined that the second apparatus has been relocated.

[0188] 16. The method of any of the preceding embodiments, wherein the first apparatus is a server or a part thereof.

[0189] 17. The method of any of the preceding embodiments, wherein the method is performed for a plurality of second apparatuses.

[0190] 18. A method for supporting managing at least a second apparatus at a first apparatus, the second apparatus being a sensor and/or actuator device, the method performed by the second apparatus, the method comprising: [0191] providing identifier information of the second device to a third apparatus; [0192] taking a radio measurement; [0193] providing identifier information of the second apparatus and the radio measurement to the first apparatus; [0194] providing sensor data to the first apparatus and/or obtaining actuator data from the first apparatus; [0195] automatically and repeatedly taking further radio measurements and providing the further taken radio measurements to the first apparatus.

[0196] 19. A method for registering at least a second apparatus at a first apparatus, the second device being a sensor and/or actuator device, the method performed by a least a third apparatus, the method comprising: [0197] receiving, from the second apparatus, identifier information of the second apparatus; [0198] determining positioning information indicative of a position of the second apparatus by positioning the third apparatus; and [0199] providing the identifier information of the second apparatus and the positioning information indicative of a position of the second apparatus to the first apparatus.

[0200] 20. An apparatus comprising means for performing a method according to any of embodiments 1 to 19.

[0201] 21. An apparatus comprising at least one processor and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus to at least perform the method of any of embodiments 1 to 19.

[0202] 22. A computer program code, the computer program code, when executed by a processor, causing an apparatus to perform the method of any of the embodiments 1 to 19.

[0203] 23. A non-transitory computer readable storage medium in which computer program code is stored, the computer program code when executed by a processor causing at least one apparatus to perform the method of any of embodiments 1 to 19.

[0204] 24. A system comprising: [0205] a first apparatus; [0206] a second apparatus; and [0207] optionally a third apparatus; [0208] the first apparatus, the second apparatus and the optionally third apparatus together being configured for performing a method according to any of embodiments 1 to 19.

[0209] Any presented connection in the described embodiments is to be understood in a way that the involved components are operationally coupled. Thus, the connections can be direct or indirect with any number or combination of intervening elements, and there may be merely a functional relationship between the components.

[0210] Further, as used in this text, the term ‘circuitry’ refers to any of the following:

[0211] (a) hardware-only circuit implementations (such as implementations in only analog and/or digital circuitry)

[0212] (b) combinations of circuits and software (and/or firmware), such as: (i) to a combination of processor(s) or (ii) to portions of processor(s)/software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone, to perform various functions) and

[0213] (c) to circuits, such as a microprocessor(s) or a portion of a microprocessor(s), that re-quire software or firmware for operation, even if the software or firmware is not physically present.

[0214] This definition of ‘circuitry’ applies to all uses of this term in this text, including in any claims. As a further example, as used in this text, the term ‘circuitry’ also covers an implementation of merely a processor (or multiple processors) or portion of a processor and its (or their) accompanying software and/or firmware. The term ‘circuitry’ also covers, for example, a baseband integrated circuit or applications processor integrated circuit for a mobile phone.

[0215] Any of the processors mentioned in this text, in particular but not limited to processors of FIGS. 2 and 3, could be a processor of any suitable type. Any processor may comprise but is not limited to one or more microprocessors, one or more processor(s) with accompanying digital signal processor(s), one or more processor(s) without accompanying digital signal processor(s), one or more special-purpose computer chips, one or more field-programmable gate arrays (FPGAS), one or more controllers, one or more application-specific integrated circuits (ASICS), or one or more computer(s). The relevant structure/hardware has been programmed in such a way to carry out the described function.

[0216] Moreover, any of the actions described or illustrated herein may be implemented using executable instructions in a general-purpose or special-purpose processor and stored on a computer-readable storage medium (e.g., disk, memory, or the like) to be executed by such a processor. References to ‘computer-readable storage medium’ should be understood to encompass specialized circuits such as FPGAs, ASICs, signal processing devices, and other devices.

[0217] It will be understood that all presented embodiments are only exemplary, and that any feature presented for a particular exemplary embodiment may be used with any aspect of the invention on its own or in combination with any feature presented for the same or another particular exemplary embodiment and/or in combination with any other feature not mentioned. It will further be understood that any feature presented for an example embodiment in a particular category may also be used in a corresponding manner in an example embodiment of any other category.