CN118276890A - Method and device for upgrading software system of internet of things (IoT) device - Google Patents

Abstract

A software system upgrading method and device of internet of things (IoT) equipment relate to the technical field of terminals, and can solve the problems that flow, time and the like are consumed more and the software system is not stably upgraded when the software system of the IoT equipment is upgraded in a front loading scene, so that the probability of successful upgrading of the software system of the IoT equipment is improved, the front loading cost is reduced, and the delivery efficiency is improved. The method comprises the following steps: the device receives a first operation, the first operation being an operation to trigger at least one IoT device software system upgrade; in response to the first operation, the device sending an upgrade installation file to the first IoT device, the upgrade installation file for a software system upgrade of the first IoT device, the first IoT device being one or more of the at least one IoT device; the device stores an upgrade installation file of the first IoT device in advance, and the device communicates with the first IoT device through a local area network.

Description

Method and device for upgrading software system of internet of things (IoT) device

Technical Field

The present application relates to the field of terminal technologies, and in particular, to a method and an apparatus for upgrading a software system of an IoT device.

Background

With the rapid development of smart home, more and more users install internet of things (Internet of Things, ioT) devices in places such as home or office, and even install IoT devices in a whole house, users can feel a convenient user experience brought by IoT devices.

However, in the full-house intelligent scenario, as the number and types of IoT devices increase, the upgrade management of the software systems of these IoT devices becomes more complex. For example, in a front-loading scenario (the front-loading scenario refers to a mode of first installing equipment according to equipment requirements before house decoration, such as a blank house), because the software system of the IoT equipment needs to consume more traffic and time due to poor network environment, the software system is not upgraded stably, and the situation that the software system of the IoT equipment fails to upgrade easily causes the increase of front-loading cost and affects the delivery schedule.

Disclosure of Invention

The application provides a method and equipment for upgrading a software system of an internet traffic (IoT) device, which can solve the problems that when the software system of the IoT device is upgraded, the flow, the time and the like are more consumed and the software system is not stably upgraded in a front loading scene, improve the success probability of upgrading the software system of the IoT device, reduce the front loading cost and improve the delivery efficiency.

In order to achieve the above purpose, the application adopts the following technical scheme:

In a first aspect, a method for upgrading a software system of an IoT device in an internet of things is provided, and the method is applied to the device and includes: the device receives a first operation, the first operation being an operation to trigger at least one IoT device software system upgrade; in response to the first operation, the device sending an upgrade installation file to the first IoT device, the upgrade installation file for a software system upgrade of the first IoT device, the first IoT device being one or more of the at least one IoT device; the device stores an upgrade installation file of the first IoT device in advance, and the device communicates with the first IoT device through a local area network.

Based on the above technical solution, after receiving the operation for triggering the IoT device upgrade, the device may send the pre-stored IoT device upgrade installation file to the IoT device to complete the software system upgrade of the IoT device. And the devices and the IoT devices can communicate through a local area network, which does not need Wi-Fi network or consume network traffic. In this way, in the scene without network or in the scene with poor network environment such as the front loading scene, the current saving, the quick and stable upgrading of the software system of the IoT device can be realized, the successful upgrading probability of the software system of the IoT device is improved, the front loading cost is reduced, and the delivery efficiency is improved. In addition, in the scene of upgrading the IoT device software system on a large scale, the scheme can save more traffic and improve the stability and efficiency of the IoT device software system upgrading.

In one possible design, the device may also pre-store a version profile of the first IoT device, where the version profile is used to determine a version matching relationship of the first IoT device with a version of the second IoT device. Based on the design, version profiles of IoT devices are pre-stored in the devices, and the version profiles indicate version corollary relationships of different IoT devices. In this way, when the device sends the upgrade installation file to the IoT device, the device can send the upgrade installation file with a proper version to the IoT device based on the version configuration file, so that collaborative upgrade between IoT device software systems can be realized, and the upgraded IoT device software systems can be matched with each other in version and can be used together.

In one possible design, before the device sends the upgrade installation file to the first IoT device, the method further comprises: the device determines that a second IoT device is present and that the version of the upgrade installation file satisfies a version matching relationship with the version of the second IoT device. Based on the design, the device sends the upgrade installation file meeting the version matching relation to the IoT device, so that collaborative upgrade between IoT device software systems can be realized, the version matching between the upgraded IoT device software systems can be realized, and the IoT device software systems can be matched for use.

In one possible design, before the device sends the upgrade installation file to the first IoT device, the method further comprises: the device satisfies a first condition according to a current version of the first IoT device and a version of the upgrade installation file, the first condition comprising: the version of the upgrade installation file is higher than the current version of the first IoT device. Based on the design, before the device sends the upgrade installation file to the IoT device, the device determines whether the current version of the IoT device and the version of the upgrade installation file meet the first condition, and only if the first condition is met, that is, the version of the upgrade installation file is higher than the current version of the IoT device, the upgrade installation file is sent to the IoT device, so that the situation that the software system of the IoT device is upgraded to an error version can be avoided, and meanwhile, the cost for sending the upgrade installation file which does not meet the first condition can be reduced.

In one possible design, before the device sends the upgrade installation file to the first IoT device, the method further comprises: the device sends a first message to the first IoT device via the relay device, the first message comprising an upgrade message and a storage address of an upgrade installation file; the device receives, by the relay device, a second message from the first IoT device, the second message for requesting an upgrade installation file; the relay device is used for providing a local area network. Based on the design, the local area network may be provided through the relay device, that is, the communication between the device and the IoT device may be forwarded through the relay device, so that the software system upgrade of the IoT device may be implemented without a Wi-Fi network or consuming network traffic. And the device can send the upgrade message and the storage address of the upgrade installation file to the IoT device, so that the IoT device can request the upgrade installation file corresponding to the storage address and complete the upgrade operation of the software system. The method can realize current saving, quick and stable upgrading of the IoT device software system and improve the success probability of upgrading the IoT device software system.

In one possible design, the gateway device includes one or more of a power bus communication PLC gateway device, a bluetooth gateway device.

In one possible design, the method further comprises, prior to the device receiving the first operation: the device obtains upgrade installation files and/or version configuration files from other devices in advance in an environment with or without a network. Based on the design, the device can obtain the upgrade installation file and/or version configuration file of the IoT device in advance under the condition of having a network or not having the network, so that the current-saving, rapid and stable upgrade of the IoT device software system can be realized in the subsequent scene of no network or worse network environment, the probability of successful upgrade of the IoT device software system is improved, the front loading cost is reduced, and the delivery efficiency is improved.

And when the IoT device of the same class is replaced or added, the IoT device can acquire the pre-stored upgrade installation file from the device under the condition of no network, and complete the upgrade operation according to the upgrade installation file. Offline upgrades of the IoT devices are implemented, which may reduce consumption of network traffic. Also, even if the upgrade installation files stored in advance in the device are acquired in an environment having a network in advance, the upgrade installation files for IoT devices of the same category are the same, so the device only needs to acquire the upgrade installation files once. That is, only the traffic of downloading the upgrade installation file once is consumed, and each IoT device in the IoT devices of the same class does not need to perform at least one operation of downloading the upgrade installation file, so that the consumption of network traffic can be further saved.

In a second aspect, a method for upgrading a software system of an IoT device is provided, and the method is applied to a first IoT device, and includes: the first IoT device receives an upgrade installation file from a device; the first IoT device performs a software system upgrade according to the upgrade installation file; the upgrade installation file is stored in the device in advance, and the first IoT device and the device are communicated through a local area network.

In one possible design, the version of the upgrade installation file satisfies a first condition, the first condition comprising: the version of the upgrade installation file is higher than the current version of the first IoT device.

In one possible design, before the first IoT device receives the upgrade installation file from the device, the method further comprises: the method comprises the steps that a first IoT device receives a first message from a device through a relay device, wherein the first message comprises an upgrade message and a storage address of an upgrade installation file; the first IoT device sends a second message to the device through the relay device according to the first message, the second message being for requesting an upgrade installation file; the relay device is used for providing a local area network.

In one possible design, the first IoT device is one or more of at least one IoT device that is an IoT device in a full-house smart scene.

In a third aspect, there is provided an apparatus having the functionality to implement the method as described in the first or second aspects and any one of the designs. The functions can be realized by hardware, and can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the functions described above.

In a fourth aspect, there is provided an apparatus comprising: comprising a processor and a memory coupled to the processor, the memory for storing program code comprising instructions, the processor reading the instructions from the memory to cause the apparatus to perform the method of the first or second aspect and any one of the designs described above. The memory may be coupled to the processor or may be separate from the processor.

In one possible design, the apparatus further includes a communication interface operable to communicate with other devices. By way of example, the communication interface may be a transceiver, an input/output interface, an interface circuit, an output circuit, an input circuit, a pin or related circuit, or the like.

In one possible design, the device further includes a display screen operable to perform a display operation with the device.

In a fifth aspect, there is provided a readable storage medium comprising a program or instructions which, when run on a device, cause the device to perform the method of the first or second aspects and any one of the designs described above.

In a sixth aspect, there is provided a program product for enabling a device to carry out the method of the first or second aspect and any one of the designs described above when the program product is run on the device.

In a seventh aspect, a system on a chip is provided, comprising at least one processor and at least one interface circuit, the at least one interface circuit being configured to perform a transceiving function and to send instructions to the at least one processor, the at least one processor performing the method according to the first aspect or the second aspect and any one of the designs described above when the at least one processor executes the instructions.

An eighth aspect provides a communication system comprising a device configured to perform the method of the first aspect and any of the designs described above, and a first IoT device configured to perform the method of the second aspect and any of the designs described above.

It should be noted that the technical effects caused by any one of the second to eighth aspects may be referred to the technical effects caused by the corresponding design in the first aspect, and will not be described herein.

Drawings

FIG. 1 is a schematic view of a full house intelligent scenario provided by an embodiment of the present application;

fig. 2 is a schematic diagram of a communication system according to an embodiment of the present application;

Fig. 3 is a schematic hardware structure of a device according to an embodiment of the present application;

FIG. 4 is a schematic structural diagram of still another apparatus according to an embodiment of the present application;

Fig. 5 is a flowchart of a method for upgrading a software system of an IoT device according to an embodiment of the present application;

FIG. 6 is a first schematic interface diagram according to an embodiment of the present application;

FIG. 7 is a second schematic interface diagram according to an embodiment of the present application;

FIG. 8 is a third schematic interface diagram according to an embodiment of the present application;

FIG. 9 is a fourth schematic interface diagram according to an embodiment of the present application;

FIG. 10 is a fifth interface diagram according to an embodiment of the present application;

Fig. 11 is a flowchart of a software system upgrade method of another IoT device according to an embodiment of the present application;

FIG. 12 is a diagram illustrating an interface according to an embodiment of the present application;

Fig. 13 is a flowchart of a software system upgrade method of another IoT device according to an embodiment of the present application;

FIG. 14 is a schematic view of a further apparatus according to an embodiment of the present application;

fig. 15 is a schematic structural diagram of a chip system according to an embodiment of the present application.

Detailed Description

The following describes the technical scheme provided by the embodiment of the application in detail by combining the drawings.

The terms "comprising" and "having" and any variations thereof, as referred to in the description of the application, are intended to cover non-exclusive inclusion. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those listed but may optionally include other steps or elements not listed or inherent to such process, method, article, or apparatus.

It should be noted that, in the embodiments of the present application, words such as "exemplary" or "such as" are used to mean serving as an example, instance, or illustration. Any embodiment or design described herein as "exemplary" or "e.g." in an embodiment should not be taken as preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "such as" is intended to present related concepts in a concrete fashion.

In the description of the present application, unless otherwise indicated, the meaning of "a plurality" means two or more. "and/or" herein is merely an association relationship describing an association object, and means that three relationships may exist, for example, a and/or B may mean: a exists alone, A and B exist together, and B exists alone.

Currently, a variety of IoT devices have entered people's lives, suggesting the concept of smart home for home use IoT device scenarios. With the increasing number of IoT devices installed in smart home, even the whole house installs IoT devices, the concept of whole house intelligence has developed. The whole house intelligence takes a house as a platform, integrates facilities related to household life by utilizing various technologies such as comprehensive wiring technology, network communication technology, security technology, automatic control technology, audio and video technology and the like, and improves the experiences of household safety, convenience, comfort and the like by constructing an efficient management system of household facilities and household schedule matters.

Exemplary, fig. 1 shows a schematic view of a full-house intelligent scenario provided by an embodiment of the present application. As shown in fig. 1, the whole house includes a house entrance aisle, a kitchen, a restaurant, a living room, a balcony, a main sleeping, a sub-sleeping, a bathroom, and the like. The whole house is provided with a plurality of IoT devices. Specifically, the kitchen is provided with an electric cooker or an electric pressure cooker, a gas device and the like; the living room is provided with a sound box (such as a smart sound box), a television (such as a smart television, also called a smart screen, a large screen and the like), a routing device and the like; the balcony is provided with a clothes hanger (such as an intelligent clothes hanger and the like); the restaurant is provided with a sweeping robot and the like; the main bed is provided with a television (such as an intelligent television), a sound box (such as an intelligent sound box), a floor lamp (such as an intelligent floor lamp), a routing device and the like; the secondary lying is provided with a desk lamp (such as an intelligent desk lamp), a sound box (such as an intelligent sound box) and the like; the toilet is provided with a body fat scale and the like.

The connection between IoT devices in the whole house intelligent scene can be established by adopting a wired communication mode or a wireless communication mode. By way of example, wired communication means may include, but is not limited to, power bus communication (power line communication, PLC) and the like. Wireless communication means may include, but are not limited to, near Field Communication (NFC), bluetooth (BT) (e.g., conventional bluetooth or low energy (bluetooth low energy, BLE) bluetooth), wireless local area network (wireless local area networks, WLAN) (e.g., wireless fidelity (WIRELESS FIDELITY, wi-Fi) network), zigbee (Zigbee), frequency modulation (frequency modulation, FM), infrared (IR), and the like.

In some scenarios, there is a need for upgrades to the software systems of the IoT devices in the full house intelligent scenario. Each IoT device may download a corresponding installation package from the cloud server over the network to complete the upgrade to the software system. Such as: with IoT devices employing Wi-Fi communication (hereinafter referred to as Wi-Fi devices), they may download installation packages from a cloud server over a Wi-Fi network to complete upgrades of software systems. For another example: with IoT devices (hereinafter abbreviated as PLC devices) that employ PLC communication, an installation package may be downloaded from a cloud server through a PLC gateway connected to a Wi-Fi network, and then the PLC gateway may send the downloaded installation package to a corresponding PLC device, and the PLC device may complete an upgrade of a software system according to the installation package. For another example: with IoT devices that use bluetooth communication (hereinafter referred to as bluetooth devices for short), the installation package may also be downloaded from the cloud server through a bluetooth gateway that connects to the Wi-Fi network, and then the bluetooth gateway may send the downloaded installation package to a corresponding bluetooth device, and the bluetooth device may complete the upgrade of the software system according to the installation package.

It will be appreciated that the gateway is also known as an intersystem connector, a protocol converter, etc. Which may enable interconnection of different networks. Such as: the PLC gateway can realize interconnection of Wi-Fi and PLC, and the Bluetooth gateway can realize interconnection of Wi-Fi and Bluetooth, etc.

In the above scheme, the cloud server needs to be connected to download the installation package through the Wi-Fi network. But in some scenarios Wi-Fi network environments are poor. Such as: the front-loading scene refers to a mode of firstly installing the IoT device according to the requirement of the IoT device before house decoration, such as a blank house and the like. Since the Wi-Fi network of the house is not installed in the front-loading scenario, the installer can only provide the Wi-Fi network to the IoT device by means of a mobile phone hotspot, a client device (customer premise equipment, CPE), etc. The CPE is a mobile signal access device that receives mobile signals and forwards them out as wireless Wi-Fi signals, also called a "mobile router". The flow can be converted into Wi-Fi signals by inserting a subscriber identity module (subscriber identification module, SIM) card provided by an operator, so that network support is provided for other devices.

However, the Wi-Fi network provided in the above manner is poor, and the download of the installation package of the IoT device is easy to fail. For the scenario of software system upgrade of large-scale IoT devices, more traffic and time are required to be consumed, and the software system upgrade is unstable, so that the front loading cost is increased, and the delivery schedule is affected.

Also, today IoT devices are numerous in variety, and matching usage may be required between the software system versions of the IoT devices. Such as: software system version matching between the scene panel and the PLC gateway is usable. For another example: in the screen-throwing scene, the screen-throwing function and the like can be realized only when the versions of the software systems among the IoT devices are matched. In the current IoT device upgrade scheme, the software systems of the IoT devices are upgraded individually, so that the problem that the IoT device software systems cannot be used in a matching manner after being upgraded may occur.

In addition, in the above scheme, when the IoT devices of the same class are added or replaced in the whole house intelligent scene, the software system upgrade of the IoT devices still needs to depend on the network, and the offline upgrade of the software system cannot be realized.

Based on this, the embodiment of the application provides a method for upgrading a software system of an IoT device, which can solve the problems of more consumption of flow, time and the like and unstable software system upgrade when upgrading the software system of the IoT device, including but not limited to the software system upgrade of a single IoT device, the software system upgrade of a large-scale IoT device and the like, in a pre-loading scene, improve the probability of successful software system upgrade of the IoT device, reduce the pre-loading cost and improve the delivery efficiency. Meanwhile, the version of the updated IoT device software system can be matched, and the IoT device software system can be matched for use. The method can also enable the software system of the IoT device to realize offline upgrade without depending on a network when the IoT device of the same class is added or replaced in the whole house intelligent scene, and reduce the consumption of network traffic.

The technical scheme provided by the embodiment of the application can be applied to the scenes of upgrading the software system of one or more IoT devices, including but not limited to the scenes of upgrading the software system of various IoT devices such as a front loading scene, a rear loading scene and the like under the whole house intelligence. The afterloading scene refers to a scene in which IoT equipment is installed after the house is finished.

Fig. 2 is a schematic diagram illustrating an architecture of a communication system 10 to which a software system upgrade method of an IoT device is applied according to an embodiment of the present application. As shown in fig. 2, the communication system 10 includes a device 100 and at least one IoT device 200 (only six are shown in fig. 2).

The device 100 may be a dedicated device that controls the IoT device 200, or may be a device that includes functionality that controls the IoT device 200. In some embodiments, the device 100 may control a software system upgrade of the IoT device 200, which may serve as an upgrade server, providing services for the IoT device 200 such as upgrade installation file download, version management, and the like. Alternatively, the device 100 may be a terminal device such as a mobile phone (this is exemplified in fig. 2), a Personal Digital Assistant (PDA), a personal computer (personal computer, PC), a Laptop computer (Laptop), a large screen display device, a wearable device, an artificial intelligence (ARTIFICIAL INTELLIGENCE, AI) device, or the like. And can also be various storage devices such as home storage, edge upgrade servers and the like.

Optionally, ioT devices 200 may be, for example, various IoT devices such as speakers 201, large screen devices 202, desk lamps 203, lights 204, cameras 205, air cleaners 206, smart curtains, smart air conditioners, smart door locks, and the like. In some embodiments, ioT device 200 may act as an upgrade client, retrieving an upgrade installation file (or upgrade installation package, etc.) from device 100 to enable a software system upgrade of IoT device 200.

Optionally, the operating systems installed by the device 100 and/or IoT device 200 include, but are not limited to Or other operating system. Of course, an operating system may not be installed in the device 100 and/or IoT device 200. In some embodiments, the device 100 and/or IoT device 200 may be a fixed device or a portable device. The application is not limited by the specific type of device 100 and/or IoT device 200, the presence or absence of an installed operating system, and the operating system installed with an installed operating system.

In some embodiments, ioT devices 200 may be smart home devices, and connections may be established between the various IoT devices 200. For example, the IoT devices 200 may establish a connection using wired or wireless communication. Reference is made to the description above for a specific description of wired or wireless communication.

In some examples, proximity discovery functionality is supported between IoT devices 200. Taking IoT device 200 as an example of sound box 201 and large screen device 202, after sound box 201 approaches large screen device 202, sound box 201 and large screen device 202 can discover each other, and then establish a wireless communication connection such as Wi-Fi end-to-peer (P2P) connection, bluetooth connection, etc. After establishing the wireless communication connection, the loudspeaker 201 and the large screen device 202 may implement signal interaction through the wireless communication connection.

In other examples, the IoT devices 200 may establish wireless communication connections over a local area network. Also take IoT device 200 as a speaker 201, and large screen device 202 as an example, speaker 201 and large screen device 202 are both connected to the same router.

In still other examples, wireless communication connections may be established between IoT devices 200 through a cellular network, the internet, or the like. Also take IoT device 200 as a sound box 201, a large screen device 202 as an example, such as: the loudspeaker 201 is connected to the Internet through a router, the large-screen device 202 is connected to the Internet through a cellular network, and then the loudspeaker 201 and the large-screen device 202 are connected in a wireless communication mode.

In some embodiments, a connection may also be established between the device 100 and one or more IoT devices 200, either by wire or wirelessly, to obtain device information for the IoT devices 200. The device 100 may provide a human-machine interaction interface through which device information of the IoT device 200 is displayed to a user and control instructions of the IoT device 200 are received by the user, such as including but not limited to upgrade instructions and the like.

Alternatively, the communication between the device 100 and the IoT device 200 may be direct, or may be forwarded by other devices. For example, one or more relay devices 300 may also be included in the communication system 10 as shown in fig. 2 in the case where the device 100 forwards communications with the IoT device 200 through other devices. In some embodiments, the relay device 300 may be used to provide a local area network to enable communication between the device 100 and the IoT device 200. It is appreciated that network traffic is not consumed in communicating between the device 100 and the IoT device 200 over the local area network. That is, the relay device 300 may not provide a Wi-Fi network, only provide a data forwarding function to enable communication between the device 100 and the IoT device 200. By way of example, the relay device 300 may be such as a router or the like. Likewise, the connection between the device 100 and the relay device 300, and/or between the relay device 300 and the IoT device 200 may also be established by a wired communication manner or a wireless communication manner, which is not limited in particular by the embodiment of the present application.

Illustratively, the speaker 201, the large-screen device 202, etc. shown in fig. 2 adopt a Wi-Fi communication mode (or support Wi-Fi communication), the desk lamp 203, etc. adopts a PLC communication mode (or support PLC communication), the electric lamp 204, etc. adopts a plc+wi-Fi communication mode (or support PLC and Wi-Fi communication mode, or support Wi-Fi communication and PLC communication simultaneously), and the camera 205, the air purifier 206, etc. adopt a bluetooth communication mode (or support bluetooth communication). In some embodiments, as shown in fig. 2, ioT devices employing Wi-Fi communication for soundbox 201, large screen device 202, etc. may request upgrade installation files directly from device 100. An IoT device using a PLC communication scheme for the desk lamp 203 and the like and a plc+wi-Fi communication scheme for the lamp 204 and the like can request an upgrade installation file from the device 100 through a PLC gateway. Likewise, for IoT devices employing bluetooth communication for cameras 205, air cleaners 206, etc., it may request upgrade installation files from device 100 through a bluetooth gateway.

Alternatively, in the process of requesting the upgrade installation file from the device 100 by the IoT device 200, the upgrade installation file may be directly requested from the device 100, or the upgrade installation file may be indirectly requested from the device 100 by the relay device 300.

In some embodiments, the device 100 may also obtain upgrade installation files of one or more IoT devices 200 and version management related files (e.g., version configuration files) from other devices, etc., before the device 100 provides the services of upgrade installation file download, version management, etc. for the IoT devices 200. By way of example, the other device may be, for example, a cell phone, personal Digital Assistant (PDA), personal computer (personal computer, PC), laptop (Laptop), large screen display device, wearable device, artificial intelligence (ARTIFICIAL INTELLIGENCE, AI) device, etc. The device may be a server 400 (fig. 2, for example). Alternatively, the device 100 may be the same type of device as the other devices, or may be a different type of device.

Alternatively, the server 400 may be a device or network device having a computing function, such as a cloud server or a network server. The server 400 may be a server, a server cluster formed by a plurality of servers, or a cloud computing service center.

Optionally, the device 100 may also establish a connection with other devices through a wired communication manner (such as a universal serial bus (universal serial bus, USB), etc.) or a wireless communication manner (such as bluetooth, wi-Fi, etc.), and reference is made to the above for a specific description of the wired communication manner and the wireless communication manner.

Optionally, fig. 2 may be a simplified schematic diagram for understanding, and in practical application, the system may further include other devices, which are not shown in the drawings.

Taking the device 100 as an example of a mobile phone, fig. 3 shows a schematic hardware structure of the device 100 according to an embodiment of the present application.

As shown in fig. 3, the device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (universal serial bus, USB) interface 130, a charge management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a sensor module 180, keys 190, a motor 191, an indicator 192, a camera 193, a display 194, and a subscriber identity module (subscriber identification module, SIM) card interface 195, etc.

The processor 110 may include one or more processing units, such as: the processor 110 may include an application processor (application processor, AP), a modem processor, a graphics processor (graphics processing unit, GPU), an image signal processor (IMAGE SIGNAL processor, ISP), a controller, a video codec, a digital signal processor (DIGITAL SIGNAL processor, DSP), a baseband processor, and/or a neural-Network Processor (NPU), etc. Wherein the different processing units may be separate devices or may be integrated in one or more processors.

The controller can generate operation control signals according to the instruction operation codes and the time sequence signals to finish the control of instruction fetching and instruction execution.

A memory may also be provided in the processor 110 for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory may hold instructions or data that the processor 110 has just used or recycled. If the processor 110 needs to reuse the instruction or data, it can be called directly from the memory. Repeated accesses are avoided and the latency of the processor 110 is reduced, thereby improving the efficiency of the system.

In some embodiments, the processor 110 may include one or more interfaces. The interfaces may include an integrated circuit (inter-INTEGRATED CIRCUIT, I2C) interface, an integrated circuit built-in audio (inter-INTEGRATED CIRCUIT SOUND, I2S) interface, a pulse code modulation (pulse code modulation, PCM) interface, a universal asynchronous receiver transmitter (universal asynchronous receiver/transmitter, UART) interface, a mobile industry processor interface (mobile industry processor interface, MIPI), a general-purpose input/output (GPIO) interface, a subscriber identity module (subscriber identity module, SIM) interface, and/or a universal serial bus (universal serial bus, USB) interface, among others.

The charge management module 140 is configured to receive a charge input from a charger. The charger can be a wireless charger or a wired charger.

The power management module 141 is used for connecting the battery 142, and the charge management module 140 and the processor 110. The power management module 141 receives input from the battery 142 and/or the charge management module 140 to power the processor 110, the internal memory 121, the display 194, the camera 193, the wireless communication module 160, and the like.

The wireless communication functions of the device 100 may be implemented by the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, a modem processor, a baseband processor, and the like.

The antennas 1 and 2 are used for transmitting and receiving electromagnetic wave signals. Each antenna in device 100 may be used to cover a single or multiple communication bands. Different antennas may also be multiplexed to improve the utilization of the antennas. For example: the antenna 1 may be multiplexed into a diversity antenna of a wireless local area network. In other embodiments, the antenna may be used in conjunction with a tuning switch.

The mobile communication module 150 may provide a solution for wireless communication, including 2G/3G/4G/5G, as applied to the device 100. The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (low noise amplifier, LNA), etc.

The wireless communication module 160 may provide solutions for wireless communication including wireless local area network (wireless local area networks, WLAN) (e.g., wireless fidelity (WIRELESS FIDELITY, wi-Fi) network), bluetooth (BT), global navigation satellite system (global navigation SATELLITE SYSTEM, GNSS), frequency modulation (frequency modulation, FM), near field communication (NEAR FIELD communication, NFC), infrared (IR), etc., as applied to the device 100.

In some embodiments, antenna 1 and mobile communication module 150 of device 100 are coupled, and antenna 2 and wireless communication module 160 are coupled, such that device 100 may communicate with a network and other devices via wireless communication techniques.

In some embodiments of the application, the mobile communication module 150 and/or the wireless communication module 160, etc. of the device 100 may be used to communicate with one or more devices, such as the server 400, relay device 300, ioT device 200, etc. shown in fig. 2.

The device 100 implements display functionality via a GPU, a display screen 194, and an application processor, etc. The GPU is a microprocessor for image processing, and is connected to the display 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs that execute program instructions to generate or change display information.

The display screen 194 is used to display images, videos, and the like. The display 194 includes a display panel. The display panel may employ a Liquid Crystal Display (LCD). In some embodiments, the device 100 may include 1 or N display screens 194, N being a positive integer greater than 1. In some embodiments of the application, the display screen 194 may be used to display device information for one or more IoT devices to enable upgrade operations for software systems of the one or more IoT devices.

The camera 193 is used to capture still images or video. In some embodiments, device 100 may include 1 or N cameras 193, N being a positive integer greater than 1.

The external memory interface 120 may be used to connect an external memory card, such as a Micro SD card, to enable the memory capabilities of the expansion device 100. The external memory card communicates with the processor 110 through an external memory interface 120 to implement data storage functions.

The internal memory 121 may be used to store computer executable program code including instructions. The internal memory 121 may include a storage program area and a storage data area. The storage program area may store an application program (such as a sound playing function) required for at least one function of the operating system, and the like. The storage data area may store data created during use of the device 100 (e.g., audio data), etc. In addition, the internal memory 121 may include a high-speed random access memory, and may also include a nonvolatile memory such as at least one magnetic disk storage device, a flash memory device, a general-purpose flash memory device, and the like. The processor 110 performs various functional applications of the device 100 and data processing by executing instructions stored in the internal memory 121 and/or instructions stored in a memory provided in the processor. In some embodiments of the application, the internal memory 121 may be used to store upgrade installation files, version configuration files, etc. for one or more IoT devices.

The audio module 170 is used to convert digital audio information into an analog audio signal output and also to convert an analog audio input into a digital audio signal. The audio module 170 may also be used to encode and decode audio signals. In some embodiments, the audio module 170 may be disposed in the processor 110, or a portion of the functional modules of the audio module 170 may be disposed in the processor 110. The device 100 may be capable of playing, recording, etc., via an audio module 170, such as music. The audio module 170 may include a speaker, a receiver, a microphone, a headphone interface, an application processor, etc. to implement audio functions.

The sensor module 180 may include a pressure sensor, a gyroscope sensor, a barometric sensor, a magnetic sensor, an acceleration sensor, a distance sensor, a proximity sensor, a fingerprint sensor, a temperature sensor, a touch sensor, an ambient light sensor, a bone conduction sensor, and the like.

The keys 190 include a power-on key, a volume key, etc. The keys 190 may be mechanical keys. Or may be a touch key. The device 100 may receive key inputs, generating key signal inputs related to user settings and function control of the device 100.

The motor 191 may generate a vibration cue. The indicator 192 may be an indicator light, may be used to indicate a state of charge, a change in charge, a message indicating a missed call, a notification, etc. The SIM card interface 195 is used to connect a SIM card.

The foregoing is merely illustrative of the structure of the device 100 in the embodiment of the present application, but is not meant to limit the structure and form of the device 100. The embodiment of the present application does not limit the structure and form of the apparatus 100. By way of example, fig. 4 illustrates another exemplary configuration of the device 100. As shown in fig. 4, the apparatus 100 includes: a processor 401, a memory 402, a transceiver 403. The processor 401 and the memory 402 may be implemented by the processor and the memory shown in fig. 3. A transceiver 403 for the device 100 to interact with other devices (such as one or more of the servers 400, relay devices 300, ioT devices 200, etc., including but not limited to those shown in fig. 2). The transceiver 403 may be a device based on a wireless communication protocol such as Wi-Fi, bluetooth or other communication protocol.

It should be understood that the illustrated structure of the embodiment of the present application does not constitute a specific limitation on the apparatus 100. In other embodiments of the application, the apparatus 100 may include more or fewer components than shown in fig. 3,4, or certain components may be combined, certain components may be split, or different arrangements of components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

The technical solutions related to the following embodiments may be implemented in the devices having the structures shown in fig. 3 and fig. 4, and the systems having the structures shown in fig. 2.

It will be appreciated that in the embodiments of the present application, the device 100 is a device, the IoT device 200 is an IoT device, the relay device 300 is a relay device, and/or the IoT device and/or the relay device may perform some or all of the steps in the embodiments of the present application, these steps or operations are merely examples, and the embodiments of the present application may also perform other operations or variations of the various operations. Furthermore, the various steps may be performed in a different order presented in accordance with embodiments of the application, and it is possible that not all of the operations in the embodiments of the application may be performed.

Fig. 5 is a schematic flow chart of a method for upgrading a software system of an IoT device according to an embodiment of the present application, where the method includes the following steps:

s501, the device receives a first operation.

In some embodiments, the first operation is an operation to upgrade one or more IoT device software systems. In some scenarios, the one or more IoT devices may be IoT devices included in the full-house intelligence, such as IoT devices in pre-load scenarios, post-load scenarios, and the like, including but not limited to.

Alternatively, the first operation may trigger an upgrade of one IoT device software system, or may trigger software system upgrades of multiple IoT devices simultaneously.

The first operation is described below taking an application managing IoT devices as an example of a smart life application.

In some embodiments, after a device accesses a local area network (such as a local area network provided by relay device 300 as shown in fig. 2, and the like), it is able to discover IoT devices that access the same local area network and/or log into the same account. Illustratively, an account is used to represent an account of an IoT device management system that devices log in during a server registration process, such as: the account may be an account number of a smart life application registered by the user.

Specifically, taking a mobile phone as an example, as shown in fig. 6 (1), the mobile phone displays a main interface 600 (or called desktop 600), and icons of one or more applications, such as an icon of a calendar application, an icon of a weather application, etc., are included in the main interface 600, which are not illustrated herein. Icons of different applications can be used for opening running interfaces of corresponding applications, and functions of the corresponding applications are achieved. The icons of the one or more applications include an icon 601 of the smart life application.

If the mobile phone detects a click operation such as the user's icon 601 of the smart life application, the mobile phone displays an operation interface 610 of the smart life application in response to the click operation as shown in (2) of fig. 6. Among other things, an add control (or button) 611 is included in the running interface 610 of the smart life application that can be used to add one or more IoT devices. Optionally, the add control 611 may also be used to implement one or more of creating a scene, sharing a device, connecting a three-way platform, sweeping, etc., which are not described in detail herein. And/or one or more add-on device cards 612 may also be displayed in the running interface 610 of the smart life application, which may also be used to add one or more IoT devices.

Taking the example of a user adding one or more IoT devices via the add control 611, the handset detects a click operation, such as the user clicking on the add control 611, in response to which the handset displays an interface 620, as shown in fig. 6 (3). Among other things, an add device control 621 is included in interface 620 that can be used to add one or more IoT devices. The handset detects a click operation, such as a user clicking on add device control 621, which determines that the user needs to add an IoT device to the smart life application, and in response to the click operation, such as add device interface 630 shown in fig. 6 (4), the handset displays one or more IoT devices located in proximity to the handset, such as including but not limited to projectors, speakers, televisions, dishwashers, steamers, ovens, and the like. In some examples, the handset may add the corresponding IoT device to the smart life application through the connect button 631 shown in fig. 6 (4). Of course, in other examples, the mobile phone may also add the searched one or IoT devices to the smart life application through other adding operations, and the type of the adding operation is not particularly limited in the embodiments of the present application.

Alternatively, in some examples, the handset may first display the search device interface 700 before displaying the add device interface 630, as shown in fig. 7 (1), upon detecting a click operation, such as by a user, on the add device control 621. Wherein a manual addition control 701 and/or a swipe code addition control 702 are included in the search device interface 700, a user may also add one or more IoT devices to the smart life application through the manual addition control 701 or the swipe code addition control 702.

Taking the example of adding one or more IoT devices via the manual add control 701, such as the search device interface 700 shown in fig. 7 (1), the handset detects a click operation, such as the user manually adding the control 701, and in response to the click operation, the handset displays the classification interface 710, as shown in fig. 7 (2). Wherein different IoT devices are classified into different categories according to classification criteria in the classification interface 710. As examples of classification criteria, the categories include, but are not limited to, routing, lighting, video, sports, and the like. If the route category includes IoT devices with route functions such as 5G-follower Wi-Fi and 5G CPE, the lighting category includes IoT devices with lighting functions such as an intelligent desk lamp, a read-write desk lamp and a full-color bulb, the audio-visual category includes IoT devices with audio-visual functions such as a sound box, an intelligent screen and a headset, and the sports category includes IoT devices with sports functions such as a running machine and an intelligent rope skipping.

It is to be understood that the above are merely illustrative of a few categories and IoT devices included in each category, which are not limiting of the present application. In practical applications, more or fewer categories may be included, or other types of category classification may be provided.

When a user determines to add an IoT device to a smart life application, the user may perform the adding operation according to the class of the IoT device. Taking IoT devices as smart screens, a user may want to add a smart screen to a smart life application, such as shown in fig. 7 (2), and the user may perform a click operation on an icon (or control, module, etc.) of the smart screen included in the audio-visual category. Alternatively, in response to the click operation, the handset may first display configuration wizard interface 720, as shown in fig. 7 (3). The configuration guide interface 720 includes a code scanning login control 721, and the user may trigger the code scanning function of the mobile phone through the code scanning login control 721. Optionally, a prompt 722 may be further included in the configuration guide interface 720, so that the user may call out the corresponding two-dimensional code on the smart screen according to the prompt 722.

If the mobile phone detects a click operation of the code scanning login control 721 by the user, the mobile phone displays a code scanning interface 730 in response to the operation, as shown in (4) in fig. 7. The smart screen may be added to the smart life application by scanning various types of identification codes such as corresponding two-dimensional codes (in the figure, this is an example) or bar codes on the smart screen through the code scanning interface 730.

Likewise, when one or more IoT devices are added via the swipe code addition control 702 shown in fig. 7 (1), the handset detects a user click operation (not shown) on the swipe code addition control 702, and in response to the click operation, the handset may also display a swipe code interface 730, such as that shown in fig. 7 (4). The IoT device may be added to the smart life application by scanning various types of identification codes, such as corresponding two-dimensional codes or bar codes, on the IoT device through the code scanning interface 730.

Optionally, the manual adding control 701 and/or the code scanning adding control 702 may also be displayed in the adding device interface 630 shown in (4) in fig. 6, and the display position of the manual adding control 701 and/or the code scanning adding control 702 is not limited in the present application.

It will be appreciated that the above illustrates just a few ways of adding one or more IoT devices to a smart life application. In actual applications, one or more IoT devices may also be added to the smart life application by other means. Such as: the present application is not particularly limited as to the manner in which one or more IoT devices are added to the smart life application by bump-and-bump, bluetooth pairing, etc.

For example, after adding one or more IoT devices to the smart life application, the handset may present an interface 800 such as shown in fig. 8 (1), wherein one or more IoT devices that have been added to the smart life application, such as televisions, projectors, speakers, ovens, dishwashers, ovens, vamps, etc., are displayed in the interface 800. The user may trigger a software system upgrade of one or more IoT devices as desired.

In some examples, a user may trigger a software system upgrade of an IoT device through a display control of the added IoT device.

Taking IoT devices as sound boxes for example, as shown in (1) in fig. 8, the mobile phone detects a click operation of a display control 801 of the sound box by a user, and in response to the operation, the mobile phone displays a detail interface 810 of the sound box as shown in (2) in fig. 8. A firmware update control 811 is included in the details interface 810 of the loudspeaker box, and a user can trigger a software system update of the loudspeaker box through the firmware update control 811. If the handset detects a click operation of the firmware update control 811 by the user, in response to the click operation, the handset displays a firmware update interface 820 as shown in fig. 8 (3). Among other things, a check update control 821 is included in firmware update interface 820, through which a user can trigger a software system upgrade of a loudspeaker enclosure. In this example, the first operation described above may be a trigger operation to check update control 821, including, but not limited to, a click operation, etc. Optionally, a system version of the speaker, such as "V1.0.0.186" or the like, may also be included in the firmware update interface 820.

In other examples, a user may trigger a software system upgrade of an IoT device through a setup interface.

Illustratively, the handset detects a clicking operation (not shown) of the my control shown in fig. 6 (2), and in response to the clicking operation, such as the interface 900 shown in fig. 9 (1), the handset may display one or more options, such as sharing management, my two-dimensional code, my mall, etc., whose functions are not described in detail herein. Among the plurality of options, the setting option 901 is included, the mobile phone detects a click operation of the setting option 901 by a user, and in response to the click operation, the mobile phone displays the setting interface 910. One or more functional options, such as a collar bean service, a sweep, etc., may also be included in the setup interface 910, which are not illustrated here. Included among the plurality of functional options is a firmware update option 911 that may be used to implement software system upgrades of one or more IoT devices.

If the handset detects a click operation of the firmware update option 911 by the user, the handset displays a firmware update interface 920 as shown in fig. 9 (3) in response to the click operation. The handset may detect a system version of one or more IoT devices, perform operations to upgrade a software system of the one or more IoT devices. In this example, the first operation described above may be a user trigger operation of the firmware update option 911, including, but not limited to, a click operation or the like.

In other examples, the handset may also present the results of the detection to the user first. Illustratively, as shown in interface 930 of fig. 9 (4), the handset may present the detected IoT device with a new version and/or a new version number that is specifically present, etc. to the user. As shown in interface 930, the television, dishwasher, oven, etc. does not detect the new version, the projector has the new version, the new version number is "1.1.8.2", etc., and will not be described here by way of example. Optionally, the IoT devices presented in interface 930 may be some or all IoT devices that have been added to the smart life application.

Among other things, an immediate upgrade control 931 is included in interface 930, and the handset detects a user click on the immediate upgrade control 931, and in response to the click, the handset performs an operation to upgrade the software system of one or more IoT devices (e.g., including, but not limited to, one or more IoT devices that detected a new version). In this example, the first operation may be a trigger operation to the upgrade control 931, including but not limited to a click operation or the like.

Of course, the user may also select the software system of some IoT devices in the interface 930 to upgrade according to actual needs, and the first operation may also be an upgrade operation of the software system of these IoT devices, etc.

It will be appreciated that the above embodiments merely illustrate the first operation and do not constitute a limitation of the present application, and that in practical applications, the first operation may be other types of operations, such as: the present application is not limited to this, and voice operation, key operation, gesture operation, or other control or button operation may be performed. The above embodiments are exemplified by the IoT device being added to the device and then the first operation being received by the device, i.e., the first operation acting on the device. Of course, the above-described operation of adding the IoT device to the device may not be performed, and the first operation may be received by the IoT device, that is, the first operation may also directly act on the IoT device.

It will also be appreciated that in the above embodiments, a software system upgrade is exemplified in which a user triggers one or more IoT devices through a device. In other embodiments, devices other than the device may be used, such as: other devices that have management functions for IoT devices, etc., trigger a software system upgrade of one or more IoT devices. Or the respective software system upgrades may also be triggered periodically or periodically by the IoT device itself. The application is not particularly limited as to the manner in which the software system upgrade of one or more IoT devices is triggered.

In some examples, the manner in which the IoT devices themselves periodically or periodically trigger the respective software system upgrades may also be set by the user. Illustratively, taking IoT devices as speakers, a setup button 822, which may be used to set up a software system upgrade of the speakers, may also be included in the firmware update interface 820 shown in fig. 8 (3). If the handset detects a click operation (not shown) of the setting button 822 by the user, the handset displays the setting interface 1000 as shown in fig. 10 in response to the click operation. Wherein, the setup interface 1000 includes an automatic upgrade option, and the user can start the automatic upgrade function of the sound box through the automatic upgrade option. If the mobile phone detects the opening operation of the button 1001 of the automatic upgrade option by the user, the mobile phone starts the automatic upgrade function of the sound box in response to the operation.

In other examples, the manner in which the IoT devices themselves periodically or periodically trigger respective software system upgrades may also be system automatically set. Optionally, the time or period for the IoT device to automatically trigger a software system upgrade may also be set by the user through the device.

It should be understood that the interfaces in the embodiments of the present application are only schematic, and do not constitute limitations of the present application. In practical applications, more or less content may be included in each interface, and more or less interfaces may be included.

S502, in response to a first operation, the device triggers a software system upgrade of the IoT device.

In some embodiments, the device may send the IoT device's upgrade installation file directly to the IoT device. That is, in response to the first operation, the device sends the upgrade installation file directly to the IoT device. Accordingly, after the IoT device receives the upgrade installation file, the software system upgrade is completed according to the upgrade installation file.

Optionally, the upgrade installation file in the embodiment of the present application may be a full-volume file (or called a full-volume installation package), or may be an incremental file (or called an incremental installation package, or called a patch installation package, etc.). It will be appreciated that a full volume file may refer to a complete software system installation file, and a delta file may refer to an upgrade file that is added with patches or modified based on the original software system.

It will be appreciated that in embodiments of the present application, an upgrade installation file for one or more IoT devices is pre-stored within (or local to) the device, which may be pre-obtained by the device from other devices. Such as devices may download upgrade installation files of one or more IoT devices from a server or the like in a network-enabled environment in advance. Or may also import (e.g., including but not limited to via USB, bluetooth, or other wired or wireless communication) upgrade installation files for one or more IoT devices from other devices. Optionally, the operation of obtaining the upgrade installation files of the one or more IoT devices by the device may be performed in an environment with a network or may be performed in an environment without a network, and the method of obtaining the upgrade installation files of the one or more IoT devices by the device according to the embodiments of the present application does not limit any way.

In this embodiment, as a possible implementation, before sending the upgrade installation file to the IoT device, the device may further determine whether to send the upgrade installation file to the IoT device according to the stored version of the upgrade installation file of the IoT device and the current version of the IoT device. Such as: in the event that the device determines that the version of the stored upgrade installation file of the IoT device is higher than the current version of the IoT device, the device then sends the upgrade installation file to the corresponding IoT device. In the event that it is determined that the version of the stored upgrade installation file of the IoT device is less than or equal to the current version of the IoT device, the device may determine not to send the upgrade installation file to the IoT device.

Alternatively, the device may store a current version of the IoT device, such as the IoT device that the device may obtain after being added to the smart life application. The current version of the IoT device may also be received from other devices, such as including but not limited to IoT devices, as well as other devices other than IoT devices.

As another possible implementation, the device may send the upgrade installation file directly to the IoT device, i.e., without performing the operations described above in which it is determined whether to send the upgrade installation file to the IoT device based on the version of the upgrade installation file stored by the IoT device. Optionally, the IoT device, after receiving the upgrade installation file from the device, may determine whether to upgrade the software system based on the current version and the version of the upgrade installation file. If the version of the upgrade installation file received by the IoT device is higher than the current version, the IoT device performs an upgrade operation of the software system. In the event that the received version of the upgrade installation file is determined to be less than or equal to the current version, then the IoT device does not perform an upgrade operation of the software system.

In some embodiments, matching (or mating) use may be required between versions of IoT devices. Thus, in the embodiment of the present application, the version configuration file of the IoT device may be stored in advance in the device, where the version configuration file is used to indicate (or determine) the version matching relationship between the IoT devices. If versions between the IoT devices only match, the IoT devices may be used in concert. Conversely, the plurality of IoT devices may not be usable in combination.

Taking the example of a screen-cast scenario, ioT device B may screen to IoT device a only if IoT device a has a higher version than a certain version. Conversely, when the IoT device a version is lower than or equal to the version, ioT device B cannot screen to IoT device a, i.e., cannot implement the screen-casting function.

Alternatively, the number of version profiles may be one or more, and each IoT device may correspond to a version profile that may be used to indicate (or determine) the version matching relationship of the corresponding IoT device with other IoT devices. Or all IoT devices may correspond to a version profile that may be used to indicate a version matching relationship between IoT devices.

Alternatively, the version configuration file may be obtained by the device from another device in advance. The method for acquiring the version configuration file can refer to the description of the method for acquiring the upgrade installation file. Optionally, the device may also send the version profile to one or more IoT devices after it has been obtained. Or the IoT device may also have a version profile pre-stored. Optionally, the version profile may be sent to the IoT device by the device and/or other devices, or the IoT device may be preset in the IoT device prior to shipment.

As a specific embodiment, the device may also determine, prior to sending the upgrade installation file to the IoT device, whether to send the upgrade installation file to the IoT device based on the version configuration file.

Such as: taking IoT device a as an example, the device determines, according to the version configuration file, that the version of IoT device a needs to be matched with the version of the other IoT device or IoT devices, for example, if the version of IoT device a is higher than version 1, the device may be matched with IoT device B higher than version 2. If there are one or more IoT devices currently in need of matching for use, and the version of the one or more IoT devices meets the requirement of the version profile with the version of the upgrade installation file of IoT device a, or the requirement of the version profile may also be described as a version matching relationship determined from the version profile. If IoT device 2 currently exists, ioT device 2 has a higher version than version 2, and IoT device a has a higher version of the upgrade installation file than version 1, the device sends the upgrade installation file to IoT device a. Or the device may also send an upgrade installation file to IoT device a when there is currently no IoT device a that needs to match one or more IoT devices in use.

Conversely, when there is currently IoT device a that needs to match one or more IoT devices in use, the version of the one or more IoT devices and the version of the IoT device a's upgrade installation file do not meet the requirements of the version profile, if there is currently IoT device 2, the version of IoT device 2 is less than or equal to version 2, and/or the version of the IoT device a's upgrade installation file is less than or equal to version 1, the device does not send the upgrade installation file to IoT device a.

As another specific embodiment, the device may also send the upgrade installation file directly to the IoT device, that is, the operation of determining whether to send the upgrade installation file to the IoT device according to the version configuration file in the above embodiment is not performed.

Optionally, after receiving the upgrade installation file from the device, the IoT device may determine, based on the version configuration file, whether to perform an upgrade operation of the software system based on the upgrade installation file.

Taking IoT device as IoT device a for example, ioT device a determines that it needs to be matched with one or more IoT device versions according to the version configuration file, if one or more IoT devices currently exist and the one or more IoT device versions and the version of the upgrade installation file of IoT device a meet the requirement of the version configuration file, ioT device a performs the upgrade operation of the software system according to the received upgrade installation file. Or when there are currently no one or more IoT devices that require IoT device a to match usage, ioT device a may also perform an upgrade operation of the software system according to the upgrade installation file.

Conversely, when there are one or more IoT devices currently in need of matching usage, the version of the one or more IoT devices and the upgrade installation file of IoT device a do not meet the requirement of the version configuration file, and IoT device a does not perform the operation of performing the software system upgrade according to the upgrade installation file.

Optionally, in the foregoing embodiment, the manner how the IoT device, such as the device and/or the IoT device a, knows whether there is an IoT device that needs to be used in matching with the IoT device a, and the version of the IoT device used in matching, and the present application is not limited in this regard. As after the IoT device is added to the device's smart life application, the device can learn whether there is currently an IoT device that needs to be used in match with IoT device a, and the version of the IoT device used in the match, etc. The device may also notify IoT device a of the previously learned information. Of course, ioT devices, such as device and/or IoT device a, may also learn the aforementioned information from other devices, and so on.

Based on the scheme, the software system of the IoT device is upgraded by combining the version configuration file, and only when the requirement of the version configuration file is met, the software system of the IoT device is upgraded, so that collaborative upgrade among the software systems of the IoT device can be realized under the scenes of full house intelligence and the like, the version of the upgraded IoT device can be matched, and the IoT device can be matched for use.

In some examples, a software system upgrade of which IoT device the device specifically triggers may be determined according to the first operation. As in the example shown in fig. 8, since the first operation is an operation for a software system upgrade of the sound box system, the device may determine that the software system upgrade of the sound box needs to be triggered according to the first operation.

In other examples, the software system upgrades of which IoT device the device specifically triggers may be determined by an upgrade installation file pre-stored by the device. As in the example shown in (3) of fig. 9, since the first operation is an operation of a software system upgrade for all IoT devices present in the current scenario (e.g., full house intelligence), the devices may determine which IoT devices to specifically upgrade from a pre-stored upgrade installation file, such as: if the device determines that an upgrade installation file of one IoT device is currently stored; or an upgrade installation file for an IoT device is stored, and the version of the upgrade installation file is higher than the current version of the IoT device, etc., then the device determines to trigger a software system upgrade for the IoT device. Otherwise, a software system upgrade of the IoT device is not triggered.

Optionally, in the above example, when the device determines that the upgrade installation file of the IoT device that triggers the upgrade is not stored in the device, the device may also output a reminder message to remind the user that the upgrade installation file of the IoT device is not currently stored in the device.

It may be appreciated that, in the embodiment of the present application, the number of IoT devices that the first operation triggers the software system upgrade may be the same as or different from the number of IoT devices that actually perform the software system upgrade operation.

It can be further understood that the technical solutions provided by the embodiments of the present application may be used alone, or in combination, where possible.

In other embodiments, step S502 shown in fig. 5 may be embodied as steps S503 to S506 shown in fig. 11.

S503, in response to the first operation, the device sends an upgrade instruction (or upgrade message) to the IoT device. Accordingly, the IoT device receives the upgrade instructions from the device.

In some embodiments, the upgrade instruction includes a storage address of an upgrade installation file corresponding to the IoT device in the device. The storage address may be used for the IoT device to obtain a corresponding upgrade installation file. Illustratively, the storage address may be identified by a uniform resource locator (uniform resource location, URL), or may take other forms, as embodiments of the application are not limited in this regard.

Optionally, other information may be included in the upgrade instruction. By way of example, this other information may include, but is not limited to, identification and/or address of IoT devices, and the like. The identification and/or address of the IoT device may be used to enable communication between the device and the IoT device, and the like.

It will be appreciated that the above embodiments are exemplified by the storage address of the upgrade installation file in the device, the identification and/or address of the IoT device, etc. being included in the upgrade instructions. Of course, in other embodiments, the storage address of the upgrade installation file in the device, the identification and/or address of the IoT device, etc. may also be sent through one or more other messages, and the present application does not limit the sending manner of the upgrade installation file.

In some embodiments, the device may also determine, prior to performing step S503, whether to send an upgrade instruction to the IoT device according to the version profile. For an introduction to the version profile, please refer to the description above.

Taking IoT device a as an example, the device determines, according to the version configuration file, that IoT device a needs to be matched with versions of other IoT device or devices, for example, if the version of IoT device a is higher than version 1, it can be matched with IoT device B that is higher than version 2. If there is currently IoT device a that needs to match the one or more IoT devices used and the version of the one or more IoT devices meets the requirement of the version profile with the version of the upgrade installation file of IoT device a, if there is currently IoT device 2, the version of IoT device 2 is higher than version 2 and the version of the upgrade installation file of IoT device a is higher than version 1, the device determines to send an upgrade instruction to IoT device a. Or the device may also send an upgrade instruction to IoT device a when there is currently no one or more IoT devices that require IoT device a to match usage.

Conversely, when there is currently IoT device a that needs to match one or more IoT devices in use, the version of the one or more IoT devices and the version of the IoT device a's upgrade installation file do not meet the requirements of the version profile, if there is currently IoT device 2, the version of IoT device 2 is not less than version 2, and/or the version of the IoT device a's upgrade installation file is not less than or equal to version 1, the device determines not to send an upgrade instruction to IoT device a.

In some embodiments, the device may also not perform step S503 if the first operation is received by other devices, such as including but not limited to IoT devices.

S504, the IoT device sends a request message to the device. Accordingly, the device receives a request message from the IoT device.

In some embodiments, the request message may be embodied as a request message for requesting an upgrade installation file from a device. Optionally, the request message may also include a current version of the IoT device, a version profile, etc. The current version, version profile, of the IoT device may be used by the device to determine whether to perform step S505.

In other embodiments, the request message may be embodied as a plurality of request messages for requesting the device for the version of the upgrade installation file, and the upgrade installation file, respectively. Such as: the IoT device requests the version of the upgrade installation file from the device through the request message 1, and then requests the upgrade installation file from the device through the request message 2 when determining that the version of the upgrade installation file meets the preset condition.

As one possible example, the preset condition may be higher than the current version of the IoT device.

As another possible example, the preset condition may be a requirement of a version profile. Taking IoT device as IoT device a for example, if IoT device a determines that it needs to be matched with one or more IoT device versions according to the version configuration file, if one or more IoT devices currently exist and the version number of the one or more IoT devices and the version number of the upgrade installation file requested by IoT device a through request message 1 meet the requirement of the version configuration file, ioT device a requests the upgrade installation file from the device through request message 2. Or IoT device a may request an upgrade installation file from device via request message 2 when there is currently no IoT device a that needs to match one or more IoT devices in use.

Alternatively, in other embodiments, the IoT device may not directly perform step S504.

S505, the device sends an upgrade installation file to the IoT device. Accordingly, the IoT device receives the upgrade installation file from the device.

In some embodiments, a connection may be established between the device and the IoT device through which the device may send the upgrade installation file to the IoT device. The connection may be, for example, a file transfer protocol (FILE TRANSFER protocol, FTP) connection, although other protocols may be used for the connection, which is not limited by the present application.

Alternatively, the connection may be automatically opened or may be actively opened by the user.

S506, the IoT device executes upgrading operation of the software system according to the upgrading installation file.

Based on the above technical scheme, in a scene without a network or in a scene with a poor network environment, such as a pre-installed scene, the IoT device can obtain an upgrade installation file stored in advance in the device under the condition without a network, and complete the upgrade operation of the software system according to the upgrade installation file. In the process, network traffic is not required to be consumed, so that the current-saving, rapid and stable upgrading of the IoT device software system can be realized, the success probability of upgrading the IoT device software system is improved, the front loading cost is reduced, and the delivery efficiency is improved. In addition, in the scene of upgrading the IoT device software system on a large scale, the above technical scheme can save more traffic and improve the stability and efficiency of the IoT device software system upgrade.

And when the IoT device of the same class is replaced or added, the IoT device can acquire the pre-stored upgrade installation file from the device under the condition of no network, and complete the upgrade operation of the software system according to the upgrade installation file. Offline upgrades of the IoT device software system are implemented, which may reduce consumption of network traffic. Also, even if the upgrade installation files stored in advance in the device are acquired in an environment having a network in advance, the upgrade installation files for IoT devices of the same category are the same, so the device only needs to acquire the upgrade installation files once. That is, only the traffic of downloading the upgrade installation file once is consumed, and each IoT device in the IoT devices of the same class does not need to perform at least one operation of downloading the upgrade installation file, so that the consumption of network traffic can be further saved.

In some embodiments, the IoT device may also output a reminder message to alert the user of the particular situation of the IoT device software system upgrade after the successful or failed software system upgrade. Optionally, in the event of an IoT device software system upgrade failure, the IoT device and/or the device may also output a cause of the software system upgrade failure, etc., such as the cause of the IoT device software system upgrade failure may include, but is not limited to, upgrade failure caused by not meeting the requirements of the version profile described above, etc.

By outputting a reminder message that the IoT device software system is successfully upgraded by the device, and upgrading the IoT device software system in a manner such as that shown in fig. 8, the IoT device is a speaker, and the device is a mobile phone, for example, as shown in fig. 12, after the upgrading of the speaker software system is successful, the mobile phone may display a firmware update interface 1200. The firmware update interface 1200 includes a reminder message 1201, where the reminder message 1201 can be used to remind the user that the software system of the speaker is successfully updated. Optionally, an upgraded version of the software system of the speaker may also be displayed in the firmware update interface 1200, such as "V1.0.0.200" or the like.

It may be appreciated that in the embodiments of the present application, the devices may communicate directly with the IoT device, or may forward the communication through a relay device or the like. The method for upgrading the software system of the IoT device provided by the embodiment of the application is described below by taking the example that the device forwards communication with the IoT device through a relay device, the relay device is a router, and the IoT device comprises a PLC device, a plc+wi-Fi device, a Wi-Fi device and a bluetooth device.

Fig. 13 is a schematic flow chart of a software system upgrade method of another IoT device according to an embodiment of the present application. As shown in fig. 13, the method includes the steps of:

s1301, the device receives a first operation.

S1302, in response to the first operation, the device sends an upgrade instruction to the PLC gateway, the Bluetooth gateway and the Wi-Fi device through the router. Correspondingly, the PLC gateway, the Bluetooth gateway and the Wi-Fi equipment receive upgrading instructions from the equipment through the router.

Optionally, the PLC gateway may also send upgrade instructions to one or more IoT devices among the PLC device, the plc+wi-Fi device, etc., and the bluetooth gateway may also send upgrade instructions to the bluetooth device, etc. (not shown in the figures).

S1303, the PLC gateway, the Bluetooth gateway and the Wi-Fi equipment send request messages to the equipment through the router. Correspondingly, the device receives the request message from the PLC gateway, the Bluetooth gateway and the Wi-Fi device through the router.

Optionally, the PLC gateway may also receive the request message from one or more IoT devices of the PLC device, the plc+wi-Fi device, and/or the like. The bluetooth gateway may also receive the request message or the like (not shown in the figure) from the bluetooth device.

And 1304, the device sends an upgrade installation file to the PLC gateway, the Bluetooth gateway and the Wi-Fi device through the router. Correspondingly, the PLC gateway, the Bluetooth gateway and the Wi-Fi equipment receive upgrade installation files from the equipment through the router.

In some embodiments, for a plc+wi-Fi device, the device may also send an upgrade installation file directly to the plc+wi-Fi device through the router. Correspondingly, the PLC+wi-Fi device can directly receive the upgrade installation file from the device through the router.

S1305, the PLC gateway sends an upgrade installation file to the PLC device, and the Bluetooth gateway sends the upgrade installation file to the Bluetooth device.

It will be appreciated that in this embodiment, a PLC device is exemplified as communicating with a device through a PLC gateway, and a bluetooth device is exemplified as communicating with a device through a bluetooth gateway.

S1306, the Wi-Fi equipment, the PLC equipment and the Bluetooth equipment execute upgrading operation of the software system according to the upgrading installation file respectively.

In some embodiments, the plc+wi-Fi device may also perform an upgrade operation of the software system according to the upgrade installation file.

Optionally, the method shown in fig. 13 may further include step S1307.

S1307, the PLC equipment sends an upgrading result to the PLC gateway, and the Bluetooth equipment sends the upgrading result to the Bluetooth gateway. Correspondingly, the PLC gateway and the Bluetooth gateway forward the received upgrading result to the equipment through the router. The Wi-Fi equipment sends an upgrading result to the equipment through the router. Correspondingly, the device receives the upgrade results from the PLC device, the Bluetooth device and the Wi-Fi device through the router.

For example, the upgrade results may refer to results of success or failure of software system upgrades of the IoT devices.

The description of each step shown in fig. 13 may refer to the description of the corresponding steps in fig. 5, 11, etc.

The foregoing description of the solution provided by the embodiments of the present application has been mainly presented in terms of a method. It will be appreciated that the apparatus, in order to achieve the above-described functions, comprises hardware structures and/or software modules corresponding to the execution of the respective functions. The various illustrative units and algorithm steps described in connection with the embodiments disclosed herein may be implemented as hardware or a combination of hardware and software. Whether a function is implemented as hardware or software-driven hardware depends upon the particular application and design constraints imposed on the solution. Those skilled in the art may implement the described functionality using different approaches for each particular application, but such implementation is not to be considered as beyond the scope of the embodiments of the present application.

The embodiment of the application can divide the functional modules of the device according to the method example, for example, each functional module can be divided corresponding to each function, or two or more functions can be integrated in one processing unit. The integrated units may be implemented in hardware or in software functional modules. It should be noted that, in the embodiment of the present application, the division of the units is schematic, which is merely a logic function division, and other division manners may be implemented in actual practice.

As shown in fig. 14, a schematic structural diagram of an apparatus according to an embodiment of the present application is provided, and the apparatus 1400 may be used to implement the methods described in the above method embodiments. By way of example, the apparatus 1400 may specifically include: a processing unit 1401, and a communication unit 1402.

In a possible example, taking the device 1400 as the device 100 shown in fig. 2 as an example, the processing unit 1401 is configured to support the device 1400 to perform steps S501 to S502 in fig. 2. And/or the processing unit 1401 is configured to support the apparatus 1400 to perform step S501 in fig. 11. And/or the processing unit 1401 is configured to support the apparatus 1400 to perform step S1301 in fig. 13. And/or the processing unit 1401 is further configured to support the device 1400 to perform other steps performed by the device 100 in the embodiment of the present application.

The communication unit 1402 is for supporting the apparatus 1400 to perform steps S503 to S505 in fig. 11. And/or the communication unit 1402 is for supporting the apparatus 1400 to perform steps S1302 to S1304, and S1307 in fig. 13. And/or the communication unit 1402 is further configured to support the device 1400 to perform other steps performed by the device 100 in embodiments of the present application.

In another possible example, taking the device 1400 as the IoT device 200 shown in fig. 2 as an example, the processing unit 1401 is configured to support the device 1400 to perform step S506 in fig. 11. And/or the processing unit 1401 is configured to support the apparatus 1400 to perform step S1306 in fig. 13. And/or the processing unit 1401 is further configured to support the device 1400 to perform other steps performed by the IoT device 200 in the embodiment of the present application.

The communication unit 1402 is for supporting the apparatus 1400 to perform steps S503 to S505 in fig. 11. And/or the communication unit 1402 is for supporting the device 1400 to perform steps S1302 to S1305, and S1307 in fig. 13. And/or the communication unit 1402 is further configured to support the device 1400 to perform other steps performed by the IoT device 200 in embodiments of the present application.

Optionally, the device 1400 shown in fig. 14 may further comprise a display unit 1403. The display unit 1403 may be used to display IoT device information and the like. And/or the display unit 1403 is further configured to support the device 1400 to perform other steps performed by the device in the embodiment of the present application.

Optionally, the apparatus 1400 shown in fig. 14 may further include a storage unit (not shown in fig. 14) storing a program or instructions. When the processing unit 1401 executes the program or instructions, the apparatus 1400 shown in fig. 14 is enabled to perform the method shown in fig. 2, 11, 13, etc.

The technical effects of the apparatus 1400 shown in fig. 14 may refer to the technical effects of the methods shown in fig. 2, 11, 13, etc., and will not be described herein. The processing unit 1401 referred to in the apparatus 1400 shown in fig. 14 may be implemented by a processor or a processor-related circuit component, and may be a processor or a processing module. The communication unit 1402 may be implemented by a transceiver or transceiver-related circuit component, which may be a transceiver or transceiver module. The display unit 1403 may be implemented by a display screen related component.

The embodiment of the present application also provides a chip system, as shown in fig. 15, which includes at least one processor 1501 and at least one interface circuit 1502. The processor 1501 and the interface circuit 1502 may be interconnected by wires. For example, interface circuit 1502 may be used to receive signals from other devices. For another example, interface circuit 1502 may be used to send signals to other devices (e.g., processor 1501). Illustratively, the interface circuit 1502 may read instructions stored in the memory and send the instructions to the processor 1501. The instructions, when executed by the processor 1501, may cause the apparatus to perform the various steps performed by the apparatus in the embodiments described above. Of course, the system-on-chip may also include other discrete devices, which are not particularly limited in accordance with embodiments of the present application.

Alternatively, the processor in the system-on-chip may be one or more. The processor may be implemented in hardware or in software. When implemented in hardware, the processor may be a logic circuit, an integrated circuit, or the like. When implemented in software, the processor may be a general purpose processor, implemented by reading software code stored in a memory.

Alternatively, the memory in the system-on-chip may be one or more. The memory may be integral with the processor or separate from the processor, and the application is not limited. The memory may be a non-transitory processor, such as a ROM, which may be integrated on the same chip as the processor, or may be separately provided on different chips, and the type of memory and the manner of providing the memory and the processor are not particularly limited in the present application.

The chip system may be a field programmable gate array (field programmable GATE ARRAY, FPGA), an Application Specific Integrated Chip (ASIC), a system on chip (SoC), a central processing unit (central processor unit, CPU), a network processor (network processor, NP), a digital signal processing circuit (DIGITAL SIGNAL processor, DSP), a microcontroller (micro controller unit, MCU), a programmable controller (programmable logic device, PLD) or other integrated chip, for example.

It should be understood that the steps in the above-described method embodiments may be accomplished by integrated logic circuitry in hardware in a processor or instructions in the form of software. The steps of the method disclosed in connection with the embodiments of the present application may be embodied directly in a hardware processor for execution, or in a combination of hardware and software modules in the processor for execution.

The embodiment of the application also provides a storage medium, wherein instructions are stored in the storage medium, and when the instructions run on the device, the instructions cause the device to execute the method described in the embodiment of the method.

An embodiment of the present application provides a program product comprising: a program or instructions which, when run on a device or computer, cause the device or computer to perform the method described in the method embodiments above.

The embodiment of the application provides a communication system, which comprises equipment and an IoT device, wherein the equipment and the IoT device are used for realizing the method in the embodiment through interaction.

In addition, the embodiment of the application also provides a device, which can be a chip, a component or a module, and can comprise a processor and a memory which are connected; the memory is configured to store execution instructions, and when the apparatus is running, the processor may execute the execution instructions stored in the memory, so that the apparatus performs the methods in the method embodiments.

The device, the storage medium, the program product or the chip provided in this embodiment are used to execute the corresponding methods provided above, so that the beneficial effects achieved by the device, the storage medium, the program product or the chip can refer to the beneficial effects in the corresponding methods provided above, and are not repeated herein.

It will be appreciated by those skilled in the art that, for convenience and brevity of description, only the above-described division of the functional modules is illustrated, and in practical application, the above-described functional allocation may be performed by different functional modules according to needs, i.e. the internal structure of the apparatus is divided into different functional modules to perform all or part of the functions described above.

In the several embodiments provided by the present application, it should be understood that the disclosed apparatus and method may be implemented in other manners. The embodiments may be combined or referenced to each other without conflict. The above-described apparatus embodiments are merely illustrative, e.g., the division of modules or units is merely a logical functional division, and there may be additional divisions in actual implementation, e.g., multiple units or components may be combined or integrated into another apparatus, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and the parts shown as units may be one physical unit or a plurality of physical units, may be located in one place, or may be distributed in a plurality of different places. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.

The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a readable storage medium. Based on such understanding, the technical solution of the embodiments of the present application may be essentially or a part contributing to the prior art or all or part of the technical solution may be embodied in the form of a software product stored in a storage medium, including several instructions for causing a device (may be a single-chip microcomputer, a chip or the like) or a processor (processor) to perform all or part of the steps of the methods of the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read Only Memory (ROM), a random access memory (random access memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

The foregoing is merely illustrative of the present application, and the present application is not limited thereto, and any person skilled in the art will readily recognize that variations or substitutions are within the scope of the present application. Therefore, the protection scope of the application is subject to the protection scope of the claims.

Claims (10)

1. A method of software system upgrade for an IoT device of the internet of things, applied to the device, the method comprising:

the device receives a first operation, the first operation being an operation to trigger at least one IoT device software system upgrade;

In response to the first operation, the device sends an upgrade installation file to a first IoT device, the upgrade installation file for a software system upgrade of the first IoT device, the first IoT device being one or more of the at least one IoT device;

The device stores an upgrade installation file of the first IoT device in advance, and the device and the first IoT device communicate through a local area network.

2. The method of claim 1, wherein the device further stores a version profile of the first IoT device in advance, the version profile being used to determine a version matching relationship of the first IoT device to a version of a second IoT device.

3. The method of claim 2, wherein before the device sends the upgrade installation file to the first IoT device, the method further comprises:

The device determines that the second IoT device is present and that a version of the upgrade installation file and a version of the second IoT device satisfy the version matching relationship.

4. The method of any of claims 1-3, wherein before the device sends an upgrade installation file to the first IoT device, the method further comprises:

The device sends a first message to the first IoT device via a relay device, the first message comprising an upgrade message and a storage address of the upgrade installation file;

The device receives, by the relay device, a second message from the first IoT device, the second message for requesting the upgrade installation file;

the relay device is configured to provide the local area network.

5. The method of any of claims 2-4, wherein prior to the device receiving the first operation, the method further comprises:

The device obtains the upgrade installation file and/or the version configuration file from other devices in advance in an environment with or without a network.

6. A method of upgrading a software system of an IoT device, applied to a first IoT device, the method comprising:

The first IoT device receives an upgrade installation file from a device;

the first IoT device performs a software system upgrade according to the upgrade installation file;

the upgrade installation file is pre-stored in the device, and the first IoT device and the device communicate through a local area network.

7. The method of claim 6, wherein prior to the first IoT device receiving an upgrade installation file from a device, the method further comprises:

the first IoT device receives a first message from the device via a relay device, the first message comprising an upgrade message and a storage address of the upgrade installation file;

The first IoT device sending a second message to the device through the relay device according to the first message, the second message being for requesting the upgrade installation file;

the relay device is configured to provide the local area network.

8. An apparatus, comprising: a processor and a memory coupled to the processor, the memory for storing program code, the program code comprising instructions, the processor reading the instructions from the memory to cause the apparatus to perform the method of any of claims 1-5 or to cause the apparatus to perform the method of any of claims 6-7.

9. A readable storage medium, characterized in that the readable storage medium comprises a program which, when run on a device, causes the device to perform the method of any one of claims 1-5 or causes the device to perform the method of any one of claims 6-7.

10. A program product, characterized in that the program product, when run on a device, causes the device to perform the method of any one of claims 1-5 or causes the device to perform the method of any one of claims 6-7.