CN113741925B - Software upgrading method and device - Google Patents

Abstract

The embodiment of the application provides a software upgrading method and device, relates to the field of terminals, and aims to enable a first device (for example, a mobile phone) to assist a second device (for example, a sound box or an earphone) in software upgrading. The method is applied to a system comprising first equipment, second equipment and a server, wherein the first equipment comprises a first module set, the first module set comprises a first module and a second module, the second equipment comprises a second module set and first configuration information, and the second module set is a subset of the first module set, and the method comprises the following steps: the second device may determine to schedule the first module of the first device to search for the second version information of the first software from the server according to the first configuration information; the second equipment determines to schedule a second module of the first equipment to download an upgrade package corresponding to the second version information from the server according to the first configuration information; the second equipment receives the upgrade package corresponding to the second version information from the first equipment; and the second equipment installs the upgrade package corresponding to the second version information.

Description

A software upgrade method and device

technical field

The present application relates to the communication field, in particular to a software upgrading method and device.

Background technique

At present, when equipment manufacturers/manufacturers (for example, Internet of Things (internet of things, IOT) equipment manufacturers) upgrade the IOT equipment, they usually adopt a mobile phone-assisted IOT equipment upgrade strategy. IOT devices can be divided into multiple types. IOT device manufacturers can provide a set of integrated binary components for each type of IOT device, which are integrated on the IOT device side and the mobile phone side respectively to ensure the stability of the interface between the mobile phone and the IOT device.

The above solution has the following disadvantages: the function realization of the mobile phone side and the IOT device side is fixed, and in the case of different types of IOT devices, the interaction interfaces between the mobile phone and the IOT device are also different. With the continuous increase of IOT devices, if the mobile phone side wants to uniformly control multiple different types of IOT devices, the mobile phone side needs to integrate many different binary components, resulting in a large consumption of storage space on the mobile phone side. Moreover, when a new type of IOT device appears, it is necessary to redesign and integrate the corresponding binary components for the new type of IOT device, making it difficult for the mobile phone to effectively expand the assisted upgrade of various types of IOT devices.

Contents of the invention

Embodiments of the present application provide a software upgrading method and apparatus, which are used to assist in upgrading software of a device (for example, an IOT device).

In the first aspect, the embodiment of the present application provides a software upgrade method, which is applied to a system including a first device, a second device, and a server. The first device includes a first module set, and the first module set includes the first module and the second module. module, the second device includes a second module set and first configuration information, the second module set is a subset of the first module set, the method includes: the second device determines that the first software of the second device is to be upgraded, and the first software is currently The version information is the first version information; the second device determines to schedule the first module of the first device to search for the second version information of the first software from the server according to the first configuration information, and the second version information is different from the first version information; The first module of a device searches the second version information of the first software from the server; the second device determines and schedules the second module of the first device to download the upgrade package corresponding to the second version information from the server according to the first configuration information; the first device The second module downloads the upgrade package corresponding to the second version information from the server; the first device sends the upgrade package corresponding to the second version information to the second device; the second device receives the upgrade package corresponding to the second version information from the first device; The second device installs an upgrade package corresponding to the second version information.

Based on the method provided in the embodiment of the present application, the first device (for example, a mobile phone) can assist the second device (for example, a speaker) to search for and download an upgrade package corresponding to the second version information. In this way, if the second device does not have the networking capability or if the second device cannot be connected to the Internet, the second device can use the networking capability of the first device to search and download the upgrade package corresponding to the second version information, which can realize the upgrade of the second device. software upgrade.

In a possible implementation manner, the system further includes a third device, the third device includes a third module set and second configuration information, the third module set is a subset of the first module set, and the third module set and the first The two module sets are different, and the method further includes: the third device determines that the second software of the third device is to be upgraded, and the current version information of the second software is the third version information; the third device determines and schedules the first device according to the second configuration information The first module searches the fourth version information of the second software from the server, and the fourth version information is different from the first version information; the first module of the first device searches the fourth version information of the second software from the server; the third device searches according to the fourth version information of the second software. Two configuration information determines and schedules the second module of the first device to download the upgrade package corresponding to the fourth version information from the server; the second module of the first device downloads the upgrade package corresponding to the fourth version information from the server; the first device downloads the upgrade package corresponding to the fourth version information from the server; An upgrade package corresponding to the fourth version information is sent; the third device receives the upgrade package corresponding to the fourth version information from the first device; and the third device installs the upgrade package corresponding to the fourth version information.

Based on the method provided in the embodiment of the present application, the first device (for example, a mobile phone) can assist a third device (for example, a speaker) to search for and download an upgrade package corresponding to the fourth version information. In this way, if the third device does not have networking capabilities or the third device cannot be connected to the Internet, the third device can use the networking capabilities of the first device to search and download the upgrade package corresponding to the fourth version information, which can realize the third device's software upgrade.

Moreover, the method provided in the embodiment of the present application can enable the first device to assist different devices (the second device and the third device) to upgrade through the modules in the first module set (for example, the first module and the second module).

In a possible implementation manner, the first module set further includes a third module, and the method further includes: the second device determines and schedules the third module of the first device to check the upgrade package corresponding to the second version information according to the first configuration information ; The third module of the first device verifies the upgrade package corresponding to the second version information.

In this way, if the second device does not have the upgrade package checking capability or the second device cannot check the upgrade package, the second device can check the upgrade package corresponding to the second version information by means of the upgrade package checking capability of the first device.

In a possible implementation manner, the first module set further includes a fourth module, and the method further includes: the second device determines and schedules the fourth module of the first device to upgrade the upgrade package corresponding to the second version information according to the first configuration information. Differential restoration and/or compression restoration; the fourth module of the first device performs differential restoration and/or compression restoration on the upgrade package corresponding to the second version information.

In this way, if the second device does not have the capability of differential restoration and/or compression restoration of the upgrade package or if the second device cannot perform differential restoration and/or compression restoration, the second device can rely on the differential restoration and/or compression restoration of the first device. The compression restoration capability performs differential restoration and/or compression restoration on the upgrade package corresponding to the second version information.

In a possible implementation manner, the searching by the first module of the first device for the second version information of the first software from the server includes: inputting the identification information of the second device and the type information of the first software to the first module, and the first The module outputs search results for the second version information.

That is, the first module may search for the second version information according to the identification information of the second device and the type information of the first software.

In a possible implementation manner, the first module further outputs at least one of the second version information, URL address information of the upgrade package corresponding to the second version information, upgrade package size information, or update log information.

In a possible implementation manner, the second module of the first device downloading the upgrade package corresponding to the second version information from the server includes: inputting the identification information of the second device, the second version information, and the second version information to the second module. Corresponding to at least one of the URL address information of the upgrade package or the type information of the first software, the second module outputs the download result of the upgrade package corresponding to the second version information.

That is, the second module may download the second version information corresponding to at least one of the identification information of the second device, the second version information, the URL address information of the upgrade package corresponding to the second version information, or the type information of the first software. upgrade package.

In a possible implementation manner, the second module further outputs at least one of a cache address of the upgrade package corresponding to the second version information or a download progress of the upgrade package corresponding to the second version information.

In a possible implementation manner, the first module set or the second module set is integrated in a software development kit (software development kit, SDK). The first module set can be integrated in the SDK of the first device, and the second module set can be integrated in the SDK of the second device. Wherein, the SDK may be uniformly provided by a software manufacturer (for example, Huawei).

In a possible implementation manner, before the second device determines that the first software of the second device is to be upgraded, the method further includes: the first device displays prompt information on the first interface of the application program, and the prompt information is used to prompt the second device The first software of the user is to be upgraded; the first device receives the first operation of the user, and the first operation is used to upgrade the first software of the second device; the first device sends a notification message to the second device, and the notification message is used to indicate that the first software pending upgrade. That is, the user can perform corresponding operations on the first device to upgrade the software of the second device, without requiring the user to operate on the second device, which can improve the user's operation convenience.

In a possible implementation manner, the first device sending the upgrade package corresponding to the second version information to the second device includes: the first device sending the upgrade package corresponding to the second version information to the second device based on a near-field device communication protocol; Wherein, the near field device communication protocol includes at least one of a Wi-Fi protocol, a Bluetooth protocol, or a near field communication protocol (near field communication, NFC).

In a possible implementation manner, the method further includes: the first device sends a download progress of the upgrade package corresponding to the second version information to the second device. If the second device has a display screen, the download progress can be displayed to the user.

In a possible implementation manner, the method further includes: the second device sends an installation progress of the upgrade package corresponding to the second version information to the first device. In this way, the first device can display the installation progress to the user through the display screen.

In a possible implementation manner, the type of the first software includes at least one of firmware, patch, software development kit, plug-in, or device parameter. That is, the first device can assist the second device to upgrade various upgrade services.

In a possible implementation manner, the first configuration information is provided by a manufacturer of the second device. In this way, it can be ensured that the upgrade process of the speaker has been effectively verified and tested by the speaker manufacturer to ensure the reliability of the upgrade.

In a possible implementation manner, the first configuration information is determined by the second device according to the capability information of the second device and the capability information of the first device; wherein, the capability information of the second device includes the communication capability of the second device, At least one of processing capability and display capability, the capability information of the first device includes at least one of communication capability, processing capability, and display capability of the first device. In this way, the upgrade process can be made more flexible.

In the second aspect, the embodiment of the present application provides a method for upgrading software, which is applied to a first device. The first device includes a first module set, and the first module set includes a first module and a second module. The method includes: the first device determines The first software of the second device is to be upgraded, and the current version information of the first software is the first version information; the first module of the first device searches the second version information of the first software from the server; the second module of the first device searches for the second version information of the first software from the server; The server downloads the upgrade package corresponding to the second version information; the first device sends the upgrade package corresponding to the second version information to the second device.

Based on the method provided in the embodiment of the present application, the first device (for example, a mobile phone) can assist the second device (for example, a speaker) to search for and download an upgrade package corresponding to the second version information. In this way, if the second device does not have the networking capability or if the second device cannot be connected to the Internet, the second device can use the networking capability of the first device to search and download the upgrade package corresponding to the second version information, which can realize the upgrade of the second device. software upgrade.

In the third aspect, the embodiment of the present application provides a method for upgrading software, including: the second device determines that the first software of the second device is to be upgraded, and the current version information of the first software is the first version information; The configuration information determines to schedule the first module of the first device to search the second version information of the first software from the server, and the second version information is different from the first version information; the second device determines to schedule the second version of the first device according to the first configuration information The module downloads the upgrade package corresponding to the second version information from the server; the second device receives the upgrade package corresponding to the second version information from the first device; the second device installs the upgrade package corresponding to the second version information.

Based on the method provided by the embodiment of the present application, if the second device does not have the networking capability or the second device cannot connect to the Internet, the second device can use the networking capability of the first device to search for and download the upgrade package corresponding to the second version information , the software upgrade of the second device can be realized.

In a fourth aspect, the embodiment of the present application provides a first device, the first device includes: a wireless communication module, a memory, and one or more processors; the wireless communication module, the memory is coupled to the processor; wherein the memory is used to store Computer program code, the computer program code includes computer instructions; when the computer instructions are executed by the processor, the first device is made to execute the method described in the first aspect or the second aspect and any possible implementation thereof.

In the fifth aspect, the embodiment of the present application provides a first device, which has the function of implementing the method described in the first aspect or the second aspect and any possible implementation manner thereof. The functions described above may be implemented by hardware, or may be implemented by executing corresponding software on the hardware. The hardware or software includes one or more modules corresponding to the above functions.

In a sixth aspect, the embodiment of the present application provides a second device, the second device includes: a wireless communication module, a memory, and one or more processors; the wireless communication module, the memory is coupled to the processor; wherein the memory is used to store Computer program code, where the computer program code includes computer instructions; when the computer instructions are executed by the processor, the second device is made to execute the method described in the first aspect or the third aspect and any possible implementation thereof.

In a seventh aspect, the embodiment of the present application provides a second device, which has the function of implementing the method described in the first aspect or the third aspect and any possible implementation manner thereof. The functions described above may be implemented by hardware, or may be implemented by executing corresponding software on the hardware. The hardware or software includes one or more modules corresponding to the above functions.

In an eighth aspect, the embodiment of the present application provides a chip system, where the chip system includes one or more interface circuits and one or more processors. The interface circuit and the processor are interconnected by wires.

The system-on-a-chip described above can be applied to a first device including a communication module and a memory. The interface circuit is for receiving signals from the memory and sending the received signals to the processor, the signals comprising computer instructions stored in the memory. When the processor executes the computer instruction, the first device may execute the method described in the first aspect and any possible implementation manner thereof.

Alternatively, the above system-on-a-chip may be applied to a second device including a communication module and a memory. The interface circuit is adapted to receive signals from the memory of the second device and to send the received signals to the processor, the signals comprising computer instructions stored in the memory. When the processor executes the computer instruction, the second device may execute the method described in the second aspect and any possible implementation manner thereof.

In a ninth aspect, the embodiment of the present application provides a computer-readable storage medium, where the computer-readable storage medium includes computer instructions. When the computer instructions are run on the first device, the first device is made to execute the method described in the first aspect and any possible implementation manner thereof. When the computer instructions are run on the second device, the second device is made to execute the method described in the second aspect and any possible implementation manner thereof.

In a tenth aspect, the embodiment of the present application provides a computer program product, which, when the computer program product is run on a computer, enables the computer to execute the first aspect, the second aspect, or the third aspect and any possible one thereof. The method described in the implementation.

In the eleventh aspect, the embodiment of the present application provides a software upgrade system, including a first device, a second device, and a server, wherein the first device can implement the first aspect or the second aspect and any possible implementation thereof For the method described in the first aspect or the third aspect and any possible implementation thereof, the second device may execute the method described in the first aspect or the third aspect and any possible implementation manner thereof.

Optionally, the above software upgrade system may further include a third device, and the third device may execute a method similar to that involved in the second device in the first aspect or the third aspect and any possible implementation thereof.

Description of drawings

FIG. 1A is a schematic diagram of a system architecture provided by an embodiment of the present application;

FIG. 1B is a schematic diagram of a first device provided in an embodiment of the present application;

FIG. 2A is a schematic display diagram of a mobile phone provided by an embodiment of the present application;

FIG. 2B is a schematic display diagram of another mobile phone provided by the embodiment of the present application;

FIG. 2C is a schematic display diagram of another mobile phone provided by the embodiment of the present application;

FIG. 2D is a schematic display diagram of another mobile phone provided by the embodiment of the present application;

FIG. 2E is a schematic display diagram of another mobile phone provided by the embodiment of the present application;

FIG. 2F is a schematic display diagram of another mobile phone provided by the embodiment of the present application;

FIG. 2G is a schematic display diagram of another mobile phone provided by the embodiment of the present application;

FIG. 2H is a schematic display diagram of another mobile phone provided by the embodiment of the present application;

FIG. 2I is a schematic display diagram of another mobile phone provided by the embodiment of the present application;

FIG. 2J is a schematic display diagram of another mobile phone provided by the embodiment of the present application;

FIG. 2K is a schematic display diagram of another mobile phone provided by the embodiment of the present application;

FIG. 2L is a schematic display diagram of another mobile phone provided by the embodiment of the present application;

FIG. 3A is a schematic diagram of an upgrade module set provided by an embodiment of the present application;

FIG. 3B is a schematic diagram of another upgrade module set provided by the embodiment of the present application;

FIG. 4A is a schematic diagram of different upgrade modules corresponding to different upgrade services provided in the embodiment of the present application;

FIG. 4B is a schematic diagram of another upgrade module set provided by the embodiment of the present application;

FIG. 5A is a schematic structural diagram of a speaker and a mobile phone provided by an embodiment of the present application;

FIG. 5B is a schematic diagram of interaction between an upgrade management module of a speaker and a mobile phone and each upgrade module provided by the embodiment of the present application;

FIG. 6A is a schematic structural diagram of a speaker, a mobile phone, and a server provided in an embodiment of the present application;

FIG. 6B is a schematic structural diagram of yet another speaker, mobile phone and server provided by the embodiment of the present application;

FIG. 6C is a schematic structural diagram of another speaker and a mobile phone provided by the embodiment of the present application;

FIG. 7A is a schematic diagram of module interaction between a speaker and a mobile phone provided by the embodiment of the present application;

FIG. 7B is a schematic diagram of interaction between another upgrade management module of speakers and mobile phones and each upgrade module provided by the embodiment of the present application;

FIG. 8A is a schematic diagram of another module interaction between a speaker and a mobile phone provided by the embodiment of the present application;

FIG. 8B is a schematic diagram of interaction between another upgrade management module of speakers and mobile phones and each upgrade module provided by the embodiment of the present application;

FIG. 9A is a schematic diagram of signal interaction between a speaker and a mobile phone according to an embodiment of the present application;

FIG. 9B is another schematic diagram of signal interaction between a speaker and a mobile phone according to an embodiment of the present application;

FIG. 9C is another schematic diagram of signal interaction between a speaker and a mobile phone provided by the embodiment of the present application;

FIG. 10A is a schematic diagram of signal interaction between an earphone and a mobile phone according to an embodiment of the present application;

FIG. 10B is another schematic diagram of signal interaction between an earphone and a mobile phone according to an embodiment of the present application;

FIG. 11 is a schematic diagram of signal interaction of a first device, a second device, and a third device provided in an embodiment of the present application;

FIG. 12 is a schematic structural diagram of a chip system provided by an embodiment of the present application;

FIG. 13 is a schematic structural diagram of a second device provided by an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application. Wherein, in the description of the present application, unless otherwise specified, "at least one" refers to one or more, and "multiple" refers to two or more than two. In addition, in order to clearly describe the technical solutions of the embodiments of the present application, in the embodiments of the present application, words such as "first" and "second" are used to distinguish the same or similar items with basically the same function and effect. Those skilled in the art can understand that words such as "first" and "second" do not limit the number and execution order, and words such as "first" and "second" do not necessarily limit the difference.

In order to make the description of the following embodiments clear and concise, a brief introduction of related concepts or technologies is given first:

Firmware: refers to a (software) program that implements the basic functions of a device (for example, an IOT device), and can be installed in a chip of the device. The firmware can be upgraded through an over the air (OTA) technology, so the firmware upgrade can also be called an OTA upgrade, and the firmware upgrade service can also be called an OTA upgrade service.

Patch: refers to the program code released for the problems existing in the firmware, and is used to solve the problems existing in the firmware.

SDK: In a broad sense, it refers to a collection of related documents, examples and tools that assist in the development of a certain type of software.

KIT (service): It is an SDK used to provide basic services to the application layer (applications), for example, location services, "pass by one touch" services, etc.

Plug-in: is a program written for a specific application programming interface. A plug-in is also called a plug-in, addin, add-in, addon, or add-on. The plug-in can be used to add the function of a specific application, for example, a plug-in of "night scene mode" can be installed in the camera application, so that the function of the night scene mode can be added in the camera application.

Device parameters: can include device protocol parameters, power consumption parameters, time zone parameters, performance parameters, custom parameters, and so on. In this embodiment of the present application, the device parameters may be simply referred to as parameters.

At present, when IOT device manufacturers upgrade IOT devices, they usually adopt a mobile phone-assisted IOT device upgrade strategy. IOT devices can be divided into multiple types. IOT device manufacturers can provide a set of integrated binary components for each type of IOT device, which are integrated on the IOT device side and the mobile phone side respectively to ensure the stability of the interface between the mobile phone and the IOT device.

The above solution has the following characteristics: the function implementations on the mobile phone side and the IOT device side are fixed. In the case of different types of IOT devices, the implementation on the mobile phone side and the interaction interface between the mobile phone and the IOT device are different. With the continuous increase of IOT devices, if the mobile phone side wants to uniformly control multiple different types of IOT devices, the mobile phone side needs to integrate many different binary components, resulting in a large consumption of storage space on the mobile phone side. And when a new type of IOT device appears, it is necessary to redesign and integrate the corresponding binary components for the new type of IOT device, making it difficult for mobile phones to effectively expand the auxiliary upgrade of various types of IOT devices.

The embodiment of this application adopts a common upgrade framework (upgrade management mechanism) to realize the upgrade of devices (for example, IOT devices), and various types of IOT devices (for example, speakers and earphones) can be upgraded through electronic devices (for example, mobile phones) To upgrade, various types of IOT devices are upgraded using the same set of upgrade framework, which consumes less storage space and can effectively expand the auxiliary upgrade of IOT devices.

As shown in FIG. 1A , it is a schematic diagram of a system architecture provided by an embodiment of the present application. The system may include a first device, a second device and a server. Wherein, an application program (application, APP) is installed in the first device. The server may be an administration server for the application. Wherein, the application program may be, for example, a smart life APP, a sports health APP, and the like. Alternatively, the application program may be a local setting APP of the first device.

Wherein, the communication between the second device and the first device may be performed through wireless fidelity (wireless fidelity, WIFI), bluetooth, NFC and other communication methods.

Exemplarily, the first device in the embodiment of the present application may be a mobile phone, a tablet computer, a desktop computer (desktop computer), a handheld computer, a notebook computer (laptop computer), an ultra-mobile personal computer (ultra-mobilepersonal computer, UMPC), netbook, personal digital assistant (personal digital assistant, PDA), augmented reality (augmented reality, AR)\virtual reality (virtual reality, VR) equipment, etc. can install the above-mentioned target application equipment, the embodiment of the present application is for the first The specific form of the device is not particularly limited.

Wherein, the operating system of the first device may be Android (Android). Optionally, the EMUI system can be installed on the Android platform. Optionally, a Huawei mobile service (huawei mobile service, HMS) engine (engine) or a Google mobile service (google mobile service, GMS) module may also be integrated on the Android platform. Alternatively, the first device may be a Hongmeng system, an IOS system, or another operating system, and the embodiment of the present application does not limit the type of operating system of the first device.

The second device provided in the embodiment of the present application may refer to a device with communication capabilities such as WIFI, Bluetooth or NFC, such as a router, a TV, a stereo, a camera, an air conditioner, a refrigerator, a smart curtain, a desk lamp, a chandelier, a rice cooker, Security devices (such as smart electronic locks), personal computers (personal computers, PCs) and other devices that can access the home wireless local area network. Alternatively, the second device in the embodiment of the present application may be a wearable device such as a smart watch, a smart bracelet, a wireless locator, a tracker (Tracker), and an electronic collar, and the second device in the embodiment of the present application may also be a car stereo , a vehicle air conditioner and other equipment, the embodiment of the present application does not specifically limit the specific form of the second equipment.

Wherein, the operating system of the second device may be the Hongmeng system, the lightweight Hongmeng system, the lightweight Internet of Things operating system (lite OS) of the Android system, the linux system, the dual-framework system, or other operating systems. Do limited.

In the embodiment of the present application, the structure of the first device provided in the embodiment of the present application is illustrated by taking the electronic device 200 (such as a mobile phone) as an example in which the first device shown in FIG. 1A is taken as an example. As shown in Figure 1B, the electronic device 200 (such as a mobile phone) may include: a processor 210, an external memory interface 220, an internal memory 221, a universal serial bus (universal serialbus, USB) interface 230, a charging management module 240, and a power management module 241, battery 242, antenna 1, antenna 2, mobile communication module 250, wireless communication module 260, audio module 270, speaker 270A, receiver 270B, microphone 270C, earphone jack 270D, sensor module 280, button 290, motor 291, indicator 292, a camera 293, a display screen 294, a subscriber identification module (subscriber identification module, SIM) card interface 295, and the like.

Wherein, the above-mentioned sensor module 280 may include sensors such as pressure sensor, gyroscope sensor, air pressure sensor, magnetic sensor, acceleration sensor, distance sensor, proximity light sensor, fingerprint sensor, temperature sensor, touch sensor, ambient light sensor and bone conduction sensor.

It can be understood that the structure shown in this embodiment does not constitute a specific limitation on the electronic device 200 . In other embodiments, the electronic device 200 may include more or fewer components than shown, or combine certain components, or separate certain components, or arrange different components. The illustrated components can be realized in hardware, software or a combination of software and hardware.

The processor 210 may include one or more processing units, for example: the processor 210 may include an application processor (application processor, AP), a modem processor, a graphics processing unit (graphics processing unit, GPU), an image signal processor ( image signal processor, ISP), controller, memory, video codec, digital signal processor (digital signal processor, DSP), baseband processor, and/or neural network processor (neural-network processing unit, NPU), etc. . Wherein, different processing units may be independent devices, or may be integrated in one or more processors.

The controller may be the nerve center and command center of the electronic device 200 . The controller can generate an operation control signal according to the instruction opcode and timing signal, and complete the control of fetching and executing the instruction.

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

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

It can be understood that, the interface connection relationship among the modules shown in this embodiment is only a schematic illustration, and does not constitute a structural limitation of the electronic device 200 . In other embodiments, the electronic device 200 may also adopt different interface connection methods in the above embodiments, or a combination of multiple interface connection methods.

The charging management module 240 is configured to receive charging input from the charger. Wherein, the charger may be a wireless charger or a wired charger. While the charging management module 240 is charging the battery 242 , it can also supply power to the electronic device through the power management module 241 .

The power management module 241 is used for connecting the battery 242 , the charging management module 240 and the processor 210 . The power management module 241 receives the input from the battery 242 and/or the charging management module 240 to provide power for the processor 210 , internal memory 221 , external memory, display screen 294 , camera 293 , and wireless communication module 260 . In some embodiments, the power management module 241 and the charging management module 240 can also be set in the same device.

The wireless communication function of the electronic device 200 can be realized by the antenna 1, the antenna 2, the mobile communication module 250, the wireless communication module 260, the modem processor and the baseband processor. In some embodiments, the antenna 1 of the electronic device 200 is coupled to the mobile communication module 250, and the antenna 2 is coupled to the wireless communication module 260, so that the electronic device 200 can communicate with the network and other devices through wireless communication technology.

Antenna 1 and Antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in electronic device 200 may be used to cover single or multiple communication frequency bands. Different antennas can also be multiplexed to improve the utilization of the antennas. For example: Antenna 1 can be multiplexed as 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 250 can provide wireless communication solutions including 2G/3G/4G/5G applied on the electronic device 200 . The mobile communication module 250 may include at least one filter, switch, power amplifier, low noise amplifier (low noise amplifier, LNA) and the like. The mobile communication module 250 can receive electromagnetic waves through the antenna 1, filter and amplify the received electromagnetic waves, and send them to the modem processor for demodulation.

The mobile communication module 250 can also amplify the signal modulated by the modem processor, convert it into electromagnetic wave and radiate it through the antenna 1 . In some embodiments, at least part of the functional modules of the mobile communication module 250 may be set in the processor 210 . In some embodiments, at least part of the functional modules of the mobile communication module 250 and at least part of the modules of the processor 210 may be set in the same device.

The wireless communication module 260 can provide WLAN (such as (wireless fidelity, Wi-Fi) network), Bluetooth (bluetooth, BT), global navigation satellite system (global navigation satellite system, GNSS), frequency modulation (frequency modulation) applied on the electronic device 200. , FM), nearfield communication technology (nearfield communication, NFC), infrared technology (infrared, IR) and other wireless communication solutions. For example, in this embodiment of the application, the electronic device 200 (such as the first device 110 ) can access the temporary network (such as the Wi-Fi network) provided by the home device 130 through the wireless communication module 260 .

The wireless communication module 260 may be one or more devices integrating at least one communication processing module. The wireless communication module 260 receives electromagnetic waves via the antenna 2 , frequency-modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 210 . The wireless communication module 260 can also receive the signal to be sent from the processor 210 , frequency-modulate it, amplify it, and convert it into electromagnetic waves through the antenna 2 to radiate out.

The electronic device 200 realizes the display function through the GPU, the display screen 294 , and the application processor. The GPU is a microprocessor for image processing, and is connected to the display screen 294 and the application processor. GPUs are used to perform mathematical and geometric calculations for graphics rendering. Processor 210 may include one or more GPUs that execute program instructions to generate or change display information.

The display screen 294 is used to display images, videos and the like. The display screen 294 includes a display panel. For example, in this embodiment of the present application, the display screen 294 may be used to display the application interface of the above-mentioned first APP, such as a device sharing interface, a device search interface, and a QR code scanning interface.

The electronic device 200 can realize the shooting function through the ISP, the camera 293 , the video codec, the GPU, the display screen 294 and the application processor. The ISP is used for processing the data fed back by the camera 293 . Camera 293 is used to capture still images or video. In some embodiments, the electronic device 200 may include 1 or N cameras 293, where N is a positive integer greater than 1.

The external memory interface 220 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 200 . The external memory card communicates with the processor 210 through the external memory interface 220 to implement a data storage function. Such as saving music, video and other files in the external memory card.

The internal memory 221 may be used to store computer-executable program codes including instructions. The processor 210 executes various functional applications and data processing of the electronic device 200 by executing instructions stored in the internal memory 221 . For example, in the embodiment of the present application, the processor 210 may execute instructions stored in the internal memory 221, and the internal memory 221 may include a program storage area and a data storage area.

Wherein, the stored program area can store an operating system, at least one application program required by a function (such as a sound playing function, an image playing function, etc.) and the like. The storage data area can store data created during the use of the electronic device 200 (such as audio data, phonebook, etc.) and the like. In addition, the internal memory 221 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, flash memory device, universal flash storage (universal flash storage, UFS) and the like.

The electronic device 200 can realize the audio function through the audio module 270 , the speaker 270A, the receiver 270B, the microphone 270C, the earphone interface 270D, and the application processor. Such as music playback, recording, etc.

The keys 290 include a power key, a volume key and the like. The key 290 may be a mechanical key. It can also be a touch button. The motor 291 can generate a vibrating reminder. The motor 291 can be used for incoming call vibration prompts, and can also be used for touch vibration feedback. The indicator 292 can be an indicator light, which can be used to indicate the charging status, the change of the battery capacity, and also can be used to indicate messages, missed calls, notifications and so on. The SIM card interface 295 is used for connecting a SIM card. The SIM card can be connected and separated from the electronic device 200 by inserting it into the SIM card interface 295 or pulling it out from the SIM card interface 295 . The electronic device 200 may support 1 or N SIM card interfaces, where N is a positive integer greater than 1. SIM card interface 295 can support Nano SIM card, Micro SIM card, SIM card and so on.

Taking the target application as a smart life APP and the first device as a mobile phone as an example, the operation process in which the first device assists the second device (for example, an IOT device) to upgrade will be described below.

As shown in Figure 2A, the main interface (i.e. desktop) 201 of the mobile phone includes an icon 202 of the smart life application, and the mobile phone can receive the user's click operation on the icon 202 of the smart life application, and in response to the click operation, the mobile phone can open the smart life application icon 202. application. In response to the user's operation of opening the "Settings" option in the interface of the smart life application, the mobile phone may display an interface 203 as shown in FIG. 2B . In the interface 203, a plurality of configurable options may be included, for example, an IOT device upgrade option 204 may be included. Optionally, the interface 203 may also include options such as smart button sound effect, smart button vibration, message notification, and personalized content recommendation, which are not limited in this application. In response to the user's operation of selecting the IOT device upgrade option 204 on the interface 203, as shown in FIG. 2C, the mobile phone can display an interface 205, which can include a plurality of IOT device identifiers, such as rice cookers, refrigerators, desk lamps, and speakers. and many more. The user can manually trigger an IOT device to upgrade in the interface 205 . Exemplarily, in response to the user's operation of selecting the upgrade button 206 of the speaker on the interface 205 , as shown in FIG. 2D , the upgrade button 206 of the speaker may prompt the user that it is loading (searching for a new version). Further, as shown in FIG. 2E , the mobile phone can display an interface 209, and in the interface 209, a prompt text 210 can be displayed, and the prompt text 210 is used to prompt the user to check a new version of the firmware of the speaker, and the new version is 11.1.01A. In the interface 209, a prompt box 211 may also be included, and the prompt box 211 may include options such as immediate upgrade, nightly upgrade, and WLAN automatic upgrade for the user to choose. In response to the user's operation of selecting the immediate upgrade option 2111 in the prompt box 211 , as shown in (a) in FIG. 2F , the mobile phone may display an interface 212 . In the interface 212, a prompt bar 213 may be included, and the prompt bar 213 is used to remind the user of the progress of the firmware download (for example, 58% has been downloaded). After the firmware download is completed, as shown in (b) in FIG. 2F , the mobile phone can display prompt text 214, which is used to remind the user that version 11.1.01A has been downloaded and whether to install it. In response to the user clicking the "Yes" button 215, the mobile phone may display a progress bar 216 as shown in (a) in FIG. 2G , the progress bar 216 is used to remind the user of the installation progress (for example, 90% has been installed). After the installation is completed, as shown in (b) in FIG. 2G , the mobile phone may display prompt text 217, which is used to remind the user that the firmware has been upgraded to version 11.1.01A.

Optionally, as shown in FIG. 2E , if the user selects the nightly upgrade or WLAN automatic upgrade option in the prompt box 211, the mobile phone can download the upgrade package of the target version to the local at night or when connected to the WLAN. When the user wants to upgrade the IOT device, he does not need to download the upgrade package, but can directly install the upgrade package, which shortens the user's waiting time, improves the user experience, and increases the upgrade rate.

In a possible design, the mobile phone can directly prompt the user of one or more IOT devices currently to be upgraded. Exemplarily, as shown in (a) in FIG. 2H, when the user opens the smart life APP and enters the home page 220 of the smart life APP, the mobile phone can display the prompt text "2 The firmware of the device has been updated, go and upgrade it." In response to the operation of the user clicking the prompt box 221, as shown in (b) in FIG. Use prompt dots (for example, small black dots or small red dots) to indicate that the firmware of the device is about to be upgraded. In response to the operation of the user clicking on the firmware upgrade option 223, as shown in (a) in FIG. ) TV and a router in a fourth room (eg, living room). Each device to be upgraded corresponds to an upgrade button. Exemplarily, in response to the user's operation of clicking the upgrade button 225 of the TV in the first room, as shown in (b) in FIG. TVs are being upgraded. Wherein, "upgrading" may indicate that the firmware is being downloaded and installed. After the TV in the first room is upgraded successfully, as shown in (c) in FIG. For the upgrade, refer to the upgrade process of the TV in the first room for the specific process, so I won’t repeat it here.

In another possible design, as shown in (a) in FIG. 2I , the mobile phone can display an interface 224. In the interface 224, there are two devices to be upgraded, which are respectively the first room (for example, the bedroom) The TV and the router in the fourth room (e.g., the living room). Each device to be upgraded corresponds to an upgrade button. Exemplarily, in response to the user's operation of clicking the upgrade button 225 of the TV in the first room, as shown in (a) in FIG. The TV's firmware is being downloaded. After the download is completed, as shown in (b) in FIG. 2J , the prompt text on the button 225 may change to "Installing", indicating that the firmware of the TV in the first room is being installed. After the installation is completed, as shown in (c) in Figure 2I, the TV in the first room may no longer be displayed on the interface 224, and only the router in the fourth room may be displayed. The user can upgrade the router in the fourth room. For details, refer to The upgrade process of the TV in the first room will not be repeated here.

In yet another possible design, as shown in (a) in FIG. 2K , the mobile phone can display an interface 224. In the interface 224, there are two devices to be upgraded, which are respectively the first room (for example, the bedroom) The TV and the router in the fourth room (e.g., the living room). Each device to be upgraded corresponds to an upgrade button. Moreover, a one-key upgrade button 230 for all devices to be upgraded in the upgrade interface 224 may also be included. Exemplarily, in response to the user's operation of clicking the one-key upgrade button 230, as shown in (b) in FIG. The prompt text on the upgrade button 225 corresponding to the TV and the upgrade button 231 corresponding to the router in the fourth room can be "upgrading", indicating that the software of the TV in the first room and the software of the router in the fourth room are being upgraded (download and install ). After the upgrade is completed, as shown in (c) in FIG. 2K, the TV in the first room and the router in the fourth room may no longer be displayed on the interface 224, indicating that the TV in the first room and the router in the fourth room have been successfully upgraded. There are currently no devices to upgrade.

For another example, as shown in FIG. 2L , when the user opens the Smart Life APP, a bullet box 215 may pop up on the interface of the Smart Life APP, prompting the user whether to upgrade the IOT devices such as TVs, speakers, and routers to detect new versions. The user may choose to upgrade one or more of the IOT devices, or the user may choose to upgrade all the IOT devices that have detected a new version. For example, in response to the user's operation of selecting the all upgrade option 216 in the prompt box 215, the mobile phone can upgrade all IOT devices that detect a new version.

The procedure of the upgrade method provided by the embodiment of the present application is described below. The method provided by the embodiment of the present application may include the following procedures: (1) establishing a set of upgrade modules; (2) scheduling and executing the upgrade process.

The process (1) (that is, the establishment of an upgrade module set) will be described below.

As shown in FIG. 3A , upgrade module sets that can be supported by the respective devices can be respectively established on the second device (for example, a sound box) and the first device (for example, a mobile phone). Wherein, the upgrading module represents the program code used for upgrading. An upgrade module may also be called an upgrade capability, an upgrade sub-capability, or an upgrade unit, etc., which is not limited in this application. Multiple upgrade modules can form a collection, and a collection can be regarded as a resource pool.

Since the software and hardware functions of the mobile phone are relatively comprehensive, a relatively complete set of upgrade modules can be established on the mobile phone side. As shown in (a) in Figure 3B, the upgrade module set of the mobile phone may include a user experience design (UX) module, an upgrade package search module (which may be referred to as a search module for short), an upgrade package download module (which may be referred to as a download module for short). module), an upgrade package execution module (or called an upgrade package upgrade execution module). Optionally, the set of upgrade modules on the mobile phone side may also include an upgrade package security verification module (which may be referred to as a security verification module for short), an upgrade package differential/compression restoration module (which may be referred to as a differential/compression restoration module) and the like. Wherein, the upgrade package may refer to a firmware upgrade package (or OTA package), a patch upgrade package, an SDK upgrade package (for example, a KIT upgrade package (KIT package for short)), a plug-in upgrade package or a parameter upgrade package, etc.

Since the second device includes multiple types, different types of second devices have different software and hardware functions, therefore, at the second device side, different sets of upgrade modules can be established on different types of second devices. Generally, the second device can be classified according to factors such as the communication module (Bluetooth module, WIFI module or NFC module) of the second device, the computing power of the processor, and the size of the memory. For example, according to the different communication modules of the second device, the second device can be classified into WIFI-type devices, Bluetooth-type devices, NFC-type devices, and so on. Wherein, the WIFI type device may be, for example, a sound box, and the Bluetooth type device may be, for example, an earphone.

Exemplarily, as shown in (b) in FIG. 3B, if the second device is a speaker, the speaker may be a WIFI type device. Since the WIFI type device has the function of connecting to the Internet, the upgrade module set of the speaker may include an upgrade package search Modules and upgrade packages Download modules. Optionally, if the speaker has a device for user interaction such as a display screen or a touch screen, the speaker can also establish a UI module. Optionally, if the processor of the speaker has a stronger function, the speaker can also establish a safety verification module. Optionally, if the ROM of the speaker is large, the speaker can also establish a differential/compression restoration module and the like.

As shown in (c) in Figure 3B, the second device can be an earphone, and the earphone can be a Bluetooth device. Since the Bluetooth device does not have the function of connecting to the Internet, the upgrade package search module and the upgrade package download module may not be established. Optionally, if the headset has a device for user interaction such as a display screen or a touch screen, the headset may also establish a UI module. Optionally, if the processor of the earphone has a strong function, the earphone can also establish a security verification module. Optionally, if the ROM of the earphone is large, the earphone can also establish a differential/compression restoration module and the like.

It should be noted that all types of second devices need to have an upgrade execution module. The upgrade execution capability may refer to the capability of writing the upgrade package into ROM, which is a basic module that the second device should have. Optionally, the upgrade package security verification module and the upgrade package differential/compression restoration module may be integrated in the upgrade package execution module. That is, the upgrade execution capability not only refers to the ability to write the upgrade package into ROM, but also includes the security verification module, differential/compression restoration module.

In a possible design, each upgrade module can be further distinguished according to different types of upgrade services. Wherein, the types of upgrade services may include firmware upgrade services (OTA upgrade services), patch upgrade services, SDK upgrade services (KIT upgrade services), plug-in upgrade services, parameter upgrade services, and the like.

Exemplarily, as shown in FIG. 4A , the firmware upgrade service may correspond to a firmware search module, a firmware download module, a firmware upgrade execution module, and the like. The parameter upgrade service may correspond to a parameter search module, a parameter download module, a parameter upgrade execution module, and the like. The patch upgrade service may correspond to a patch search module, a patch download module, a patch upgrade execution module, and the like.

For the second device, if the second device needs to support different types of upgrade services, the second device needs to include upgrade modules corresponding to the different types of upgrade services. For example, as shown in Figure 4B, for the speaker, if it is necessary to support firmware upgrade service and parameter upgrade service, the upgrade package search module in the upgrade module set of the speaker can include a firmware search module and a parameter search module, an upgrade package download module It can include a firmware download module and a parameter download module. The upgrade package security check module can include a firmware security check module and a parameter security check module. The upgrade package differential/compression restoration module can include a firmware differential/compression restoration module and a parameter differential/compression module. The restore module, the upgrade package upgrade execution module may include a firmware upgrade execution module and a parameter upgrade execution module. Among them, the firmware upgrade service may correspond to a firmware upgrade search module, a firmware upgrade download module, a firmware security verification module, a firmware difference/compression restore module, and a firmware upgrade execution module. The parameter upgrade service can correspond to a parameter upgrade search module, a parameter upgrade download module, a parameter safety verification module, a parameter difference/compression restoration module, and a parameter upgrade execution module.

In a possible design, some upgrade modules of different upgrade services can be shared. For example, different upgrade services using the same upgrade package structure, same upgrade package signature, and same security verification mechanism can share the upgrade package security verification module and the upgrade package differential/compression recovery module. For example, the OTA package upgrade service (firmware upgrade service) and the patch upgrade service may share the upgrade package security verification module and the upgrade package differential/compression restoration module.

It should be noted that, no matter on the first device side or the second device side, each upgrade module has a fixed input interface and output interface, the input interface can receive specific input parameters, and the output interface can output specific return information to Ensure that the upgrade modules of different upgrade module sets can be seamlessly connected.

Exemplarily, the definition format of the upgrade package search module may include functions, input parameters and return information, where:

Function description: Initiate the search (detection) of the target version (new version) upgrade package.

Input parameters: identification information of the second device, new version upgrade package type (for example, firmware, patch, parameter, plug-in or SDK (for example, KIT), etc.).

Return information: search results for new version upgrade packages (no new version upgrade package/new version upgrade package available). If there is a new version upgrade package, the returned information may also include version number information, URL address information, upgrade package size information and update log (changelog) information of the new version upgrade package.

The definition format of the upgrade package download module can include functions, input parameters and return information, where:

Function description: Initiate the download of the new version upgrade package, or cancel the download of the new version upgrade package.

Input parameters: the identification information of the second device, the URL address of the new version upgrade package, and the type of the new version upgrade package.

Return information: can include the download progress of the new version upgrade package, the download result of the new version upgrade package (download success/download failure). The returned information may also include the address of the local cache after the download of the upgrade package of the new version is completed, the version number information of the upgrade package of the new version, and the like. Alternatively, the returned information may include a result of canceling the download of the new version upgrade package (cancellation succeeds, cancellation fails).

The definition format of the security verification module can include functions, input parameters and return information, among which:

Function description: Initiate the security verification of the upgrade package.

Input parameters: the identification information of the second device, the storage address of the new version upgrade package, the type of the new version upgrade package, etc.

Return information: The verification result of the new version upgrade package (verification successful/verification failed).

The definition format of the differential/compression restoration module can include functions, input parameters and return information, where:

Function description: Initiate the difference/compression restore of the upgrade package.

Input parameters: the identification information of the second device, the storage address of the new version upgrade package, and the type of the new version upgrade package.

Return information: upgrade package differential/compression restoration result (differential/compression restoration successful or differential/compression restoration failed).

The definition format of an upgrade execution module can include functions, input parameters and return information, where:

Function description: Initiate the upgrade execution of the upgrade package (that is, install the upgrade package), or cancel the upgrade execution of the upgrade package.

Input parameters: the identification information of the second device, the storage address of the new version upgrade package, and the type of the new version upgrade package.

Return information: It can include the progress of the upgrade execution of the new version upgrade package (that is, the progress of the installation), the result of the upgrade execution (successful installation/failure of the upgrade), or the result of canceling the installation (successful cancellation of the installation/failure of the upgrade).

The definition format of a UI module can include functions, input parameters and return information, where:

Function description: It is for the user to choose whether to initiate the search, download and installation of the new version upgrade package (that is, upgrade execution), or cancel the download and installation process, and report the corresponding progress (for example, download progress, installation progress, etc.) and results ( For example, download results, cancel download results, install results, cancel install results, etc.) are displayed to the user.

Input parameters: identification information of the second device, new version upgrade package type, version number information of the new version upgrade package (including ROM version, patch version) and the upgrade status of the second device (including initialization, detection, downloading, installation medium.

Return information: user UX setting information, such as determining to initiate a new version upgrade package search, download and installation, canceling downloading, canceling installation, etc.

In order to aggregate the upgrade modules in the upgrade module sets of different devices into a complete upgrade process, a set of upgrade modules can be established for unified coordination and scheduling between the first device (for example, a mobile phone) and the second device (for example, a speaker) The management mechanism (that is, the upgrade framework/upgrade management mechanism).

As shown in Figure 5A, taking the first device as a mobile phone and the second device as a speaker, an upgrade management module (or an upgrade process scheduling execution module) can be established on the speaker, and the upgrade management module on the speaker can be scheduled Each upgrade module in the speaker's upgrade module collection. An upgrade management module can also be established on the mobile phone, and the upgrade management module on the mobile phone can schedule each upgrade module in the upgrade module set on the mobile phone. The upgrade management module on the speaker and the upgrade management module of the mobile phone can perform signaling interaction.

Exemplarily, as shown in FIG. 5B , on the mobile phone side, the UI module can store user UX setting information (for example, information about the upgrade setting operation performed by the user on the touch screen of the mobile phone, for example, the upgrade setting operation can be for the firmware of the desk lamp upgrade) is sent to the upgrade management module, and the upgrade management module determines that the upgrade package needs to be upgraded according to the user UX setting information (for example, the firmware of the desk lamp is upgraded). Then, the upgrade management module can schedule corresponding upgrade modules, such as an upgrade package search module, an upgrade package download module, and an upgrade package upgrade execution module. The upgrade management module can input corresponding input parameters to the input interface of the upgrade package search module, and the upgrade package search module output interface can output corresponding search information (such as the URL address of the upgrade package), and the upgrade management module is when scheduling the upgrade package download module, The search information (such as the URL address of the upgrade package) output by the upgrade package search module output interface can be used as the input parameter of the input interface of the upgrade package download module, that is, the output interface of the upgrade package search module can be docked with the input interface of the upgrade package download module . The upgrade package download module output interface can output corresponding download information (such as the storage address of the upgrade package). storage address) as the input parameter of the input interface of the upgrade package upgrade execution module, that is, the output interface of the upgrade package upgrade execution module can be connected with the input interface of the upgrade package upgrade execution module.

Similarly, on the speaker side, the UI module can send user UX setting information (for example, information about the upgrade setting operation performed by the user on the touch screen of the speaker, for example, the upgrade setting operation can be to upgrade the firmware of the desk lamp) to the upgrade management module, the upgrade management module can determine that an upgrade package needs to be upgraded according to the user UX setting information (for example, upgrade the firmware of the desk lamp). Then, the upgrade management module can schedule corresponding upgrade modules, such as an upgrade package search module, an upgrade package download module, and an upgrade package upgrade execution module. The upgrade management module can input corresponding input parameters to the input interface of the upgrade package search module, and the upgrade package search module output interface can output corresponding search information (such as the URL address of the upgrade package), and the upgrade management module is when scheduling the upgrade package download module, The search information (such as the URL address of the upgrade package) output by the upgrade package search module output interface can be used as the input parameter of the input interface of the upgrade package download module, that is, the output interface of the upgrade package search module can be docked with the input interface of the upgrade package download module . The upgrade package download module output interface can output corresponding download information (such as the storage address of the upgrade package). storage address) as the input parameter of the input interface of the upgrade package upgrade execution module, that is, the output interface of the upgrade package upgrade execution module can be connected with the input interface of the upgrade package upgrade execution module.

In summary, no matter on the mobile phone side or on the speaker side, the input interface and output interface of each upgrade module (such as the upgrade package search module, the upgrade package download module and the upgrade package upgrade execution module) are fixed. Whether the module, the upgrade package download module, and the upgrade package upgrade execution module are integrated on the speaker or on the mobile phone side, seamless connection can be realized.

It can be understood that, since the upgrade modules in the upgrade module sets of speakers and mobile phones may be repeated (for example, both speakers (for example, WIFI type equipment) and mobile phones can have upgrade package search modules and upgrade package download modules), it is necessary to A module selection mechanism to clearly select which modules from which device's upgrade module set to complete the upgrade process.

In a possible design, as shown in FIG. 5A , configuration information may be integrated on the speaker, and the configuration information may be specified by the speaker manufacturer. The upgrade management module of the speaker can determine which modules to select from the upgrade module set of which device to complete the upgrade process according to the configuration information.

Exemplarily, if the second device is a speaker, the configuration information may be as shown in Table 1:

Table 1

upgrade module speaker side mobile phone side UI module ● ● Upgrade package search module ● Upgrade package download module ● Upgrade package security verification module ● Upgrade package differential/compression restore module ● Upgrade package upgrade execution module ●

Exemplarily, if the second device is a headset, the configuration information (list) may be as shown in Table 2:

Table 2

upgrade module earphone side mobile phone side UI module ● Upgrade package search module ● Upgrade package download module ● Upgrade package security verification module ● Upgrade package differential/compression restore module ● Upgrade package upgrade execution module ●

It should be noted that in the configuration information, the UI modules can be parallelized, that is, UX interaction can be performed on both the first device side (for example, a mobile phone) and the second device side (for example, a speaker or earphone). The UX interaction on different devices has the same effect, that is, there can be multiple user interaction interfaces for the upgrade, and each interface can be operated independently by the user for upgrade control, and the operation results are shared on different interactive interfaces. Moreover, it can be understood that when upgrading the second device, the upgrade execution module can only select the upgrade execution module on the side of the second device. For other modules except the UI module and the upgrade execution module (for example, the upgrade package search module, the upgrade package download module, etc.), only the upgrade module of one side/one end device can be selected.

In another possible design, the upgrade management module may automatically compile upgrade modules for completing the upgrade process according to the upgrade module information on the second device side and the first device side. The automatic arrangement strategy may be: priority scheduling of the upgrade module on the second device side, when the second device lacks a necessary upgrade module (for example, an upgrade package download module), schedule the corresponding upgrade module from the first device side.

Exemplarily, as shown in FIG. 6A , it is a schematic diagram of a system architecture provided by an embodiment of the present application, including a speaker, a mobile phone, and a server. Wherein, the mobile phone includes application program and SDK collection. The SDK set may be, for example, an HMS module (or called an HMS engine)) or a GMS module. Wherein, the application program may be, for example, a smart life APP, and the application program includes an upgrade management interface. The SDK set includes a first SDK, a second SDK and a near-field device communication protocol module. Wherein, the first SDK may be, for example, a KIT framework (framework), and the second SDK may, for example, be a smart home toolkit (smarthome KIT). The first SDK includes an upgrade function module, and the upgrade function module includes an upgrade management module on the mobile phone side as shown in FIG. 5A and an upgrade module in the upgrade module set except the UI module.

Wherein, the upgrade management interface of the application program can receive the user's operation, and based on the user's operation, the application program can call the application programming interface (application programming interface, API) interface provided by the first SDK to interact with the upgrade function module. On the mobile phone, the first SDK can exist independently in APP mode, or the first SDK can be integrated in the application program, or the SDK collection can be used as an independent APP, and the application program and the independent APP can be downloaded and installed together. The operation of the software depends on the independent APP.

Among them, the speaker includes an upgrade-related user interaction application (that is, an application for upgrading, such as a speaker setting application), an SDK set, an upgrade adaptation layer, and the manufacturer's own code. The SDK set can be, for example, an HMS module or a GMS module. Wherein, the SDK set includes the first SDK, the second SDK and the near-field device communication protocol module. The first SDK may be, for example, the first SDK, and the second SDK may be, for example, smarthome KIT. The first SDK includes an upgrade function module, and the upgrade function module includes an upgrade management module on the speaker side as shown in FIG. 5A and an upgrade module in the upgrade module set except the UI module.

Wherein, the SDK set on the speaker side may be uniformly delivered by a software manufacturer (for example, Huawei). The SDK set can be upgraded independently from the speaker, that is, the SDK set is decoupled from the code of the speaker manufacturer. The rest of the software code of the speaker is adapted and developed by the speaker manufacturer according to the characteristics of the current speaker.

The speaker manufacturer's own code can carry the speaker's own upgrade capability. The speaker's own upgrade capability can be associated with the SDK set by upgrading the adaptation layer. As shown in FIG. 6B , the speaker can communicate with the server (for example, the OTA server of the manufacturer) through the manufacturer's own code, for example, the OTA upgrade package can be obtained from the server. You can refer to the related description below for the self-upgrading ability of the speaker, which is temporarily omitted here.

The soft bus in speakers or mobile phones is used to provide communication capabilities between devices. For example, the soft bus may provide inter-device communication capabilities of near-field devices, which may include devices connected through a near-field protocol such as Bluetooth, or devices connected through a home router.

A second SDK in the speaker or phone can provide far-field device communication capabilities. Wherein, the far-field device refers to a device that completes information exchange between devices through a cloud server (cloud server). It should be noted that the near-field device and the far-field device are not fixed and can be switched dynamically. For example, when a user controls the air conditioner at home through a mobile phone in the company, the mobile phone and the air conditioner are far-field devices, and the far-field device communication protocol is adopted. If the user returns home, the mobile phone and the air conditioner are connected to the home router network. At this time, the mobile phone and the air conditioner are near-field devices and adopt the near-field device communication protocol. The first SDK can call the far-field device communication capability interface provided by the second SDK to complete the information exchange between the far-field devices.

Wherein, the server may include an OTA server and an application market server. Wherein, the OTA server may store an OTA upgrade package (for example, an OTA upgrade package provided by a software manufacturer (for example, Huawei)) and a patch upgrade package. The SDK, for example (KIT upgrade package), can be stored in the application market server.

Wherein, the operating system of the mobile phone may be an Android system, a Hongmeng system, an IOS system or other operating systems. The operating system of the speaker can be Hongmeng system, lightweight Hongmeng system, lite OS, linux system, dual-frame system, or other operating systems.

Wherein, the second SDK of the mobile phone may include a far-field device communication module, and the first SDK of the mobile phone may further include a far-field upgrade control interface and a near-field upgrade control interface. The first SDK can call the far-field device communication capability interface of the far-field device communication module through the far-field upgrade control interface, so that the first SDK can communicate with the far-field device. The first SDK can call the near-field device communication capability interface of the soft bus through the near-field upgrade control interface, so that the first SDK can communicate with the near-field device.

Similarly, the second SDK of the speaker may include a far-field device communication module, and the first SDK of the speaker may further include a far-field upgrade control interface and a near-field upgrade control interface. The first SDK can call the far-field device communication capability interface of the far-field device communication module through the far-field upgrade control interface, so that the first SDK can communicate with the far-field device. The first SDK can call the near-field device communication capability interface of the soft bus through the near-field upgrade control interface, so that the first SDK can communicate with the near-field device.

Exemplarily, as shown in FIG. 6C , on the speaker side, the first SDK in the SDK set may include an upgrade function module, and the upgrade function module may include an upgrade management module and an upgrade module in the upgrade module set except the UI module. On the mobile phone side, the first SDK may include an upgrade function module, and the upgrade function module may include an upgrade management module and upgrade modules other than the UI module in the upgrade module set.

The UI module of the speaker can be integrated in an upgrade-related user interaction application, and the upgrade-related user interaction application can perform information interaction with the upgrade management module through an upgrade API interface. The UI module of the mobile phone can be integrated in the application program, and the user can perform corresponding upgrade settings through the upgrade management interface of the application program, that is, the mobile phone can receive the corresponding operation of the user's upgrade settings through the upgrade management interface, and the upgrade management interface can be updated through the upgrade API interface Interact information with the upgrade management module. The upgrade management module of the mobile phone and the upgrade management module of the speaker can interact through the upgrade control interface.

Among them, the upgrade configuration information specified by the speaker manufacturer is determined by the speaker manufacturer in the process of integrating the SDK set, according to the current situation of the speaker and the auxiliary upgrade capability (module) that the mobile phone can provide. The configuration information can be solidified in the speaker after being effectively verified and tested by the speaker manufacturer. Subsequent upgrade module scheduling execution process will be executed in accordance with the fixed scheduling sequence and process. In this way, it can be ensured that the upgrade process of the speaker has been effectively verified and tested by the speaker manufacturer to ensure the reliability of the upgrade.

In a possible design, the speaker upgrade module may not be integrated in the first SDK of the SDK set, and the speaker may have its own upgrade capability. Among them, the speaker's own upgrade capability can be carried in the speaker manufacturer's own code, and the association is established by upgrading the adaptation layer and the SDK set. Among them, the self-upgrading ability of speakers refers to the content that speaker manufacturers are responsible for integrated development. In the following two cases, the speaker can have its own upgrade capability.

1. Some modules need to be developed by speaker manufacturers themselves. For example, the upgrade execution module is optionally developed by the speaker manufacturer itself. For example, the upgrade execution module may support modes such as AB upgrade mode and independent module upgrade.

2. Some speaker manufacturers have strong capabilities and can design and upgrade functions by themselves. For example, some speaker manufacturers have OTA servers, which can make and release OTA upgrade packages by themselves. In this way, both the search module and the download module of the upgrade package can be implemented by the speaker manufacturer. That is, speaker manufacturers can build upgrade package search modules and download modules by themselves.

It should be noted that the scheduling of the self-upgrading capability of the speaker still depends on the upgrade management module of the speaker, so as to ensure that the target application (for example, an application program) can effectively manage the upgrade of the speaker.

Moreover, no matter whether the upgrade module of the speaker is built in the first SDK of the SDK collection or built by the speaker manufacturer itself, its input interface and output interface are fixed, so as to ensure that the upgrade module of the speaker and the upgrade module of the mobile phone can be seamlessly connected .

The process (2) (that is, the scheduling and execution of the upgrade process) will be described below.

Exemplarily, the user may initiate an upgrade (for example, firmware upgrade) on the second device (for example, a speaker) on an application program on the first device (for example, a mobile phone). The mobile phone can send user UX setting information to the speaker, and the upgrade management module on the speaker can read the configuration information integrated on the speaker, and schedule each upgrade module according to the arrangement result in the configuration information. Alternatively, the upgrade management module on the speaker may determine (that is, automatically arrange) the upgrade modules used to complete the upgrade process according to the upgrade module information on the speaker side and the mobile phone side, and schedule corresponding upgrade modules.

As shown in Figure 7A, the user can upgrade settings through the upgrade management interface of the application program (for example, as shown in Figure 2C, the user can upgrade the speaker through the upgrade button 206 on the interface 205), and the upgrade management interface can be upgraded through the API interface. Pass the user UX setting information (that is, information related to the upgrade settings performed by the user on the upgrade management interface) to the upgrade management module. The upgrade management module of the mobile phone can send user UX setting information to the upgrade management module of the speaker through the upgrade control interface, and the upgrade management module of the speaker can receive the user UX setting information through the upgrade control interface. According to the user UX setting information, the upgrade management module of the speaker determines that an upgrade package (for example, an OTA package) needs to be upgraded. The upgrade management module of the speaker can read the configuration information, and the configuration information can specify the OTA package search module, the OTA package download module and the OTA package upgrade execution module on the speaker. In this way, the upgrade management module of the speaker can determine that the upgrade execution process is: (1) calling the OTA package search module on the speaker; (2) calling the OTA package download module on the speaker; (3) calling the OTA package upgrade execution module on the speaker .

As shown in Figure 7B, on the mobile phone side, the UI module (which can be integrated in the application program in Figure 7A) can send the user UX setting information to the upgrade management module, and the upgrade management module can send the user UX setting information to the upgrade on the speaker side management module. The upgrade management module on the speaker side determines that the OTA package upgrade needs to be performed according to the user UX setting information. The upgrade management module on the speaker side can determine to call the local (ie speaker) upgrade package search module, upgrade package download module and upgrade package upgrade execution module according to the configuration information. For the specific calling process, reference may be made to the relevant description in FIG. 5B , and details are not repeated here.

Optionally, the upgrade management module on the speaker side can also send corresponding search information, download information, and upgrade execution information to the upgrade management module on the mobile phone side, and the upgrade management module on the mobile phone side forwards it to the UI module on the mobile phone side, so that through The application presents to the user corresponding search information (for example, the version number of the new version as shown in Figure 2E), download information (for example, the download progress as shown in (a) in Figure 2F or ( The download progress shown in a), the download completion result shown in (b) in Figure 2F), the upgrade execution information (for example, the installation progress shown in Figure 2G (a) or the ( The installation progress shown in b), the installation completion result shown in (b) in FIG. 2G, etc.).

For another example, as shown in FIG. 8A , the user can perform upgrade settings through the upgrade management interface of the application program, and the upgrade management interface can pass the user UX setting information to the upgrade management module through the upgrade API interface. The upgrade management module of the mobile phone can send upgrade setting information through the upgrade control interface, and the upgrade management module of the speaker can receive the upgrade setting information through the upgrade control interface. According to the upgrade setting information, the upgrade management module of the speaker determines that an OTA package upgrade is required. The upgrade management module of the speaker can read the configuration information, and the configuration information can specify to use the search module and the download module on the mobile phone, and the upgrade execution module on the speaker. In this way, the upgrade management module of the speaker can determine that the upgrade execution process is: (1) calling the OTA package search module on the mobile phone; (2) calling the OTA package download module on the phone; (3) calling the OTA package upgrade execution module on the speaker .

As shown in Figure 8B, on the mobile phone side, the UI module (which can be integrated into the application program in Figure 8A) can send the user UX setting information to the upgrade management module, and the upgrade management module can send the user UX setting information to the upgrade on the speaker side management module. The upgrade management module on the speaker side determines that an upgrade package (for example, an OTA package) needs to be upgraded according to the user UX setting information. The upgrade management module on the speaker side can determine to call the upgrade package search module, the upgrade package download module and the local (ie speaker side) upgrade package upgrade execution module on the mobile phone side according to the configuration information. The upgrade management module on the speaker side can send the configuration information to the upgrade management module on the mobile phone side, so that the upgrade management module on the mobile phone side calls the upgrade package search module and the upgrade package download module on the mobile phone side in turn. The upgrade management module on the mobile phone side can send the return information from the upgrade package search module and the upgrade package download module on the mobile phone side to the upgrade management module on the speaker side, and the upgrade management module on the speaker side can analyze the above returned information, and the speaker calls the upgrade Package upgrade execution module. For the specific calling process, reference may be made to the relevant description in FIG. 5B , and details are not repeated here.

Optionally, the upgrade management module on the speaker side can also send the upgrade execution information and the parsed search information and download information to the upgrade management module on the mobile phone side, and the upgrade management module on the mobile phone side will update the upgrade execution information, search information and download information. The information is forwarded to the UI module on the mobile phone side, so that the corresponding search information (for example, the version number of the new version as shown in Figure 2E), download information (for example, as shown in (a) in Figure 2F) is presented to the user through the application program. The download progress shown in Figure 2J or the download progress shown in (a) in Figure 2J, the download result shown in Figure 2F in (b)), upgrade execution information (for example, as shown in Figure 2G in (a) The installation progress or the installation progress shown in (b) in FIG. 2J , the installation result shown in (b) in FIG. 2G , etc.).

It should be noted that, in the process shown in FIG. 7A and FIG. 7B , the mobile phone and the sound box may use far-field device communication or near-field device communication. In the process shown in FIG. 8A and FIG. 8B , the mobile phone and the sound box can communicate using a near-field device. This is because far-field device communication usually cannot transfer files (that is, the mobile phone cannot send the upgrade package downloaded by the mobile phone to the speaker).

The upgrade management module of the first device (for example, a mobile phone) can determine whether the second device (for example, a speaker) to be upgraded is a far-field device or a near-field device, and then decide to use the near-field device communication interface or the far-field device communication interface to complete the upgrade. Communication between devices. The judgment mode of the far-field device and the near-field device is: the soft bus provides the information of all the near-field devices currently connected to the first device, so the first device can determine all the near-field devices, if the second device to be upgraded currently is Non-near-field devices are considered far-field devices. Of course, the second device also needs to determine whether the current communication mode is near-field device communication or far-field device communication, and then decide which communication interface needs to be used currently. The second device may also determine the information of all near-field devices currently connected to the second device through the soft bus interface, and if the current first device is not a near-field device, it is regarded as a far-field device.

Exemplarily, the following assumes that the first device is a mobile phone, the second device is a speaker, and the configuration information specifies the search module, download module and upgrade execution module on the speaker as an example. The upgrade package search process, upgrade package download process and upgrade The package execution process is described.

Taking the upgrade service type as an OTA service as an example, the upgrade package (OTA package) search process is shown in Figure 9A, including:

901. The UI module of the mobile phone notifies the upgrade management module of the mobile phone that a user initiates an OTA upgrade package search.

Exemplarily, the UI module of the mobile phone can be integrated in the application program, the user can perform corresponding upgrade settings through the application program, and the mobile phone can receive corresponding operations of the user's upgrade settings through the upgrade management interface of the application program. Wherein, the version of the OTA upgrade package is different from (for example, higher than) the version of the OTA package on the current speaker.

902. The upgrade management module of the mobile phone notifies the user of the upgrade management module of the speaker to initiate an OTA upgrade package search.

The upgrade management module of the mobile phone and the upgrade management module of the sound box can use near-field device communication or far-field device communication.

903. The upgrade management module of the speaker starts a version search process.

904. The upgrade management module of the sound box reads the module scheduling configuration information configured by the device manufacturer.

Wherein, the module scheduling configuration information configured by the device manufacturer may be the configuration information solidified in the speaker by the speaker manufacturer.

905. The upgrade management module of the sound box confirms that the search module of the device is used.

That is, the configuration information in the speaker specifies to use the search module of the speaker itself.

906. The upgrade management module of the sound box calls the search module of the device.

907. The search module of the speaker initiates an OTA new version search.

The search module of the speaker can search the OTA package of the new version from the OTA server or the OTA server owned by the speaker manufacturer.

908. The search module of the sound box sends the new version information of the OTA package to the upgrade management module of the sound box.

909. The upgrade management module of the sound box saves the new version information of the OTA package locally.

910. The upgrade management module of the sound box sends the new version information of the OTA package to the upgrade management module of the mobile phone.

911. The upgrade management module of the mobile phone sends the new version information of the OTA package to the UI module of the mobile phone.

912. The UI module of the mobile phone displays the new version information of the OTA package.

Exemplarily, as shown in FIG. 2E , the mobile phone may display prompt text 210 to prompt the user to check the new version 11.1.01A.

The upgrade package search process for other types of upgrade services is similar to that shown in FIG. 9A , and will not be repeated in this application.

The upgrade package download process of the OTA service is shown in Figure 9B, including:

920. The UI module of the mobile phone notifies the upgrade management module of the mobile phone that the user initiates an OTA upgrade package download.

Exemplarily, as shown in FIG. 2E , the mobile phone may receive an operation in which the user clicks the upgrade immediately item 2111, and in response to the operation, the upgrade management interface (that is, the interface 209) may notify the upgrade management module of the mobile phone through the corresponding upgrade API interface that the user initiates an upgrade. Speaker OTA upgrade package download. Or, as shown in (a) in Fig. 2I, the mobile phone can receive the operation that the user clicks the upgrade button 225 corresponding to the TV in the first room, and in response to this operation, the upgrade management interface (ie interface 224) can pass the corresponding upgrade API The interface notifies the upgrade management module of the mobile phone that the user initiates the download of the OTA upgrade package of the TV in the first room.

921. The upgrade management module of the mobile phone notifies the user of the upgrade management module of the speaker to initiate an OTA upgrade package download.

922. The upgrade management module of the speaker starts an OTA upgrade package download process.

923. The upgrade management module of the sound box reads the configuration information configured by the device manufacturer.

924. The upgrade management module of the sound box confirms that the download module of the device (that is, the sound box) is used.

925. The upgrade management module of the sound box calls the download module of the device.

926. The download module of the sound box downloads the OTA upgrade package.

927. The download module of the sound box sends the local cache address of the OTA upgrade package to the upgrade management module of the sound box.

928. The upgrade management module of the sound box saves the OTA upgrade package locally.

The upgrade management module of the speaker saves the OTA upgrade package locally according to the local cache address of the OTA upgrade package.

929. The download module of the sound box feeds back the progress of downloading the upgrade package (also referred to as the download progress) to the upgrade management module of the sound box.

930. The upgrade management module of the speaker feeds back the download progress to the upgrade management module of the mobile phone.

931. The upgrade management module of the mobile phone feeds back the download progress to the UI module of the mobile phone.

931a. The UI module of the mobile phone performs a download progress display.

Exemplarily, as shown in (a) in FIG. 2F , the current download progress may be 58%. For another example, as shown in (a) in FIG. 2J , the mobile phone can display "downloading" through the button 225 without displaying the specific downloading progress.

932. The download module of the sound box notifies the upgrade management module of the sound box that the download of the OTA upgrade package is completed.

933. The upgrade management module of the speaker notifies the upgrade management module of the mobile phone that the download of the OTA upgrade package is completed.

934. The upgrade management module of the mobile phone notifies the UI module of the mobile phone that the download of the OTA upgrade package is completed.

935 . The UI module of the mobile phone completes the download of the OTA upgrade package and displays a result.

Exemplarily, as shown in (b) in FIG. 2F , after the download of the OTA upgrade package is completed, the mobile phone can prompt the user through the prompt text 214 that version 11.1.01A has been downloaded, and can prompt the user whether to install it.

The upgrade package execution process of the OTA service is shown in Figure 9C, including:

940. The UI module of the mobile phone notifies the upgrade management module of the mobile phone that the user initiates the installation of the OTA upgrade package.

Exemplarily, as shown in (b) in FIG. 2F , the mobile phone may prompt the user through the prompt text 214 that the version 11.1.01A has been downloaded, and may prompt the user whether to install it. In response to the user's operation of clicking the button 215, the upgrade management interface (that is, the interface 212) can notify the upgrade management module of the mobile phone through the corresponding upgrade API interface that the user initiates the installation of the OTA upgrade package of the speaker.

Alternatively, after the upgrade management module of the mobile phone determines that the OTA upgrade package has been downloaded, it may automatically initiate the installation of the OTA upgrade package.

941. The upgrade management module of the mobile phone notifies the user of the upgrade management module of the speaker to initiate OTA upgrade package installation.

942. The upgrade management module of the speaker starts an OTA upgrade package installation process.

943. The upgrade management module of the sound box reads the configuration information configured by the device manufacturer.

944. The upgrade management module of the sound box confirms that the upgrade execution module of the device is used.

945. The upgrade management module of the sound box calls the upgrade execution module of the device.

946. Install an OTA upgrade package in the upgrade execution module of the sound box.

947. The upgrade execution module of the sound box feeds back the installation progress (also called the download progress) to the upgrade management module of the sound box.

948. The upgrade management module of the speaker feeds back the installation progress to the upgrade management module of the mobile phone.

949. The upgrade management module of the mobile phone feeds back the installation progress to the UI module of the mobile phone.

950. Displaying progress of the UI module of the mobile phone being installed.

Exemplarily, as shown in (a) in FIG. 2G , the current installation progress may be 90%. Or, as shown in (b) in FIG. 2J , the mobile phone can display "Installing" through the button 225 without displaying the specific installation progress.

951. The upgrade execution module of the sound box feeds back to the upgrade management module of the sound box that the installation is completed.

952 . Record the installation completion information of the upgrade management module of the sound box.

953. The upgrade management module of the speaker feeds back that the installation is completed to the upgrade management module of the mobile phone.

954. The upgrade management module of the mobile phone reports to the UI module of the mobile phone that the installation is completed.

955. The UI module of the mobile phone is installed and a result is displayed.

Exemplarily, as shown in (b) in FIG. 2G , the mobile phone may prompt the user through prompt text 217 that the firmware (OTA package) of the speaker has been upgraded to version 11.1.01A. Or, as shown in (c) in FIG. 2I , the TV in the first room may no longer be displayed on the interface 224 to indicate that the OTA upgrade package installation in the first room is completed.

In the following, the first device is a mobile phone, the second device is a headset, and the configuration information specifies the search module and download module on the mobile phone, and the upgrade execution module on the headset as an example. The upgrade package search process, upgrade package download process and upgrade The package execution process is described.

Taking the upgrade service type as an OTA service as an example, the upgrade package (OTA package) search process is shown in Figure 10A, including:

1001. The UI module of the mobile phone notifies the upgrade management module of the mobile phone that the user initiates an OTA upgrade package search.

1002. The upgrade management module of the mobile phone notifies the user to initiate an OTA upgrade package search to the upgrade management module of the earphone.

The upgrade management module of the mobile phone and the upgrade management module of the headset can use near-field device communication or far-field device communication.

1003. The upgrade management module of the headset starts an OTA upgrade package search process.

1004. The upgrade management module of the headset reads the configuration information configured by the device manufacturer.

1005. The upgrade management module of the earphone confirms that the search module of the mobile phone is used.

1006. The upgrade management module of the earphone calls the search module of the mobile phone through the upgrade management module of the mobile phone.

1007. The upgrade management module of the mobile phone calls the search module of the mobile phone.

1008. The search module of the mobile phone initiates an OTA upgrade package search.

The search module of the earphone can search the OTA package of the new version from the OTA server or the OTA server owned by the earphone manufacturer.

1009. The search module of the mobile phone feeds back the version information of the OTA upgrade package to the upgrade management module of the mobile phone.

1010. The upgrade management module of the mobile phone feeds back the version information of the OTA upgrade package to the upgrade management module of the earphone.

1011. The upgrade management module of the headset saves the version information of the OTA upgrade package locally.

That is, the upgrade management module of the headset saves the OTA package version information on the headset.

1012. The upgrade management module of the earphone sends the upgrade package description file information to the upgrade management module of the mobile phone.

It should be noted that after the search module of the mobile phone completes the search for the OTA upgrade package, it will not process the version information of the OTA upgrade package, and the upgrade management module of the mobile phone will directly pass it to the upgrade management module of the earphone. The upgrade package description file information is analyzed from the upgrade package version information, and then the upgrade package description file information is passed to the upgrade management module of the mobile phone.

1013. The upgrade management module of the mobile phone sends the upgrade package description file information to the UI module of the mobile phone.

1014. The UI module of the mobile phone displays the version information of the OTA upgrade package.

The UI module of the mobile phone displays the version information of the OTA upgrade package based on the upgrade package description file information. Exemplarily, as shown in FIG. 2E , the mobile phone may display prompt text 210 to prompt the user to check the new version 11.1.01A.

The upgrade package download process of the OTA service is shown in Figure 10B, including:

1021. The UI module of the mobile phone notifies the user to initiate an OTA upgrade package download to the upgrade management module of the mobile phone.

Exemplarily, as shown in FIG. 2E , the mobile phone may receive an operation in which the user clicks the upgrade immediately item 2111, and in response to the operation, the upgrade management interface (that is, the interface 209) may notify the upgrade management module of the mobile phone through the corresponding upgrade API interface that the user initiates an upgrade. Speaker OTA upgrade package download. Or, as shown in (a) in Fig. 2I, the mobile phone can receive the operation that the user clicks the upgrade button 225 corresponding to the TV in the first room, and in response to this operation, the upgrade management interface (ie interface 224) can pass the corresponding upgrade API The interface notifies the upgrade management module of the mobile phone that the user initiates the download of the OTA upgrade package of the TV in the first room.

1022. The upgrade management module of the mobile phone notifies the user to initiate an OTA upgrade package download to the upgrade management module of the headset.

1023. The upgrade management module of the headset starts an OTA upgrade package search process.

1024. The upgrade management module of the headset reads the configuration information configured by the device manufacturer.

1025. The upgrade management module of the earphone confirms that the download module of the mobile phone is used.

1026. The upgrade management module of the earphone calls the download module of the mobile phone through the upgrade management module of the mobile phone.

1027. The upgrade management module of the mobile phone calls the download module of the mobile phone.

1028. The download module of the mobile phone downloads the OTA upgrade package.

1029. The download module of the mobile phone sends the cache address of the OTA upgrade package to the upgrade management module of the mobile phone.

1030. The upgrade management module of the mobile phone stores the OTA upgrade package locally.

1031. The download module of the mobile phone feeds back the download progress to the upgrade management module of the mobile phone.

1032. The upgrade management module of the mobile phone feeds back the download progress to the upgrade management module of the earphone.

1032a. The upgrade management module of the headset feeds back the download progress to the upgrade management module of the mobile phone.

1033. The upgrade management module of the mobile phone feeds back the download progress to the UI module of the mobile phone.

1034. The UI module of the mobile phone displays the download progress.

Exemplarily, as shown in (a) in FIG. 2F , the current download progress may be 58%. For another example, as shown in (a) in FIG. 2J , the mobile phone can display "downloading" through the button 225 without displaying the specific downloading progress.

1035. The download module of the mobile phone feeds back that the download is completed to the upgrade management module of the mobile phone.

1036. The upgrade management module of the mobile phone sends an OTA upgrade package to the upgrade management module of the headset.

1037. The upgrade management module of the headset saves the OTA upgrade package locally.

1037a. The upgrade management module of the earphone feeds back to the upgrade management module of the mobile phone that the download of the OTA upgrade package is completed.

It should be noted that after the download module of the mobile phone completes the download of the OTA upgrade package, it will not process the OTA upgrade package, and the upgrade management module of the mobile phone will directly pass the OTA upgrade package to the upgrade management It is finally determined that the download of the OTA upgrade package is completed, and then, the upgrade management module of the earphone feeds back the download completion of the OTA upgrade package to the upgrade management module of the mobile phone.

1038. The upgrade management module of the mobile phone feeds back to the UI module of the mobile phone that the download of the OTA upgrade package is completed.

1039. The UI module of the mobile phone completes the downloading of the OTA upgrade package and displays the result.

Exemplarily, as shown in (b) in FIG. 2F , after the download of the OTA upgrade package is completed, the mobile phone may prompt the user through a prompt text 214 that version 11.1.01A has been downloaded.

For the execution process of the upgrade package of the Bluetooth device, reference may be made to the flow shown in FIG. 9C , which will not be repeated here.

Based on the method provided in the embodiment of the present application, the first device (for example, a mobile phone) can use the same set of upgrade frameworks to upgrade different types of second devices (for example, speakers or earphones), the storage space consumption of the mobile phone is small, and the mobile phone can Different capability assistance is provided for different types of second devices through the upgrade framework. For example, for a headset that only has communication capabilities such as Bluetooth and NFC, the mobile phone can assist the headset to search for and download an upgrade package. For another example, for a device without a touch screen or a device with cumbersome user interaction operations (for example, the process of operating a TV through a remote control is cumbersome), the mobile phone can provide the TV with user interaction capabilities. For another example, for a second device that cannot support differential restoration and security verification capabilities, the mobile phone can provide security verification capabilities for the second device, for example, the mobile phone can assist the second device to perform HTTPS security protocol and PKI authentication on the upgrade package. In this way, the effective extension of the first device to assist the upgrade of the second device can be realized.

As shown in Figure 11, the embodiment of the present application provides a software upgrade method, which is applied to a system including a first device, a second device, and a server. The first device includes a first module set, and the first module set includes a first module and a The second module, the second device includes a second module set and first configuration information, the second module set is a subset of the first module set, including:

1101. The second device determines that the first software of the second device is to be upgraded, and the current version information of the first software is the first version information.

Before step 1101, the following steps may also be included: the first device displays prompt information on the first interface of the application program, and the prompt information is used to prompt the first software of the second device to be upgraded; the first device receives the user's first operation, The first operation is used to upgrade the first software of the second device; the first device sends a notification message to the second device, and the notification message is used to indicate that the first software is to be upgraded.

Wherein, the type of the first software includes at least one of firmware, patch, software development kit, plug-in or device parameter. The first configuration information is provided by the manufacturer of the second device. Alternatively, the first configuration information is determined by the second device according to the capability information of the second device and the capability information of the first device; wherein, the capability information of the second device includes communication capability, processing capability, and display capability of the second device. At least one, the capability information of the first device includes at least one of communication capability, processing capability, and display capability of the first device.

1102. The second device determines and schedules the first module of the first device to search for second version information of the first software from the server according to the first configuration information, where the second version information is different from the first version information.

Wherein, the first module may be the upgrade package search module mentioned above.

1103. The first module of the first device searches for the second version information of the first software from the server.

Exemplarily, the identification information of the second device and the type information of the first software may be input to the first module, and the first module outputs the search result of the second version information.

Optionally, the first module further outputs at least one of the second version information, URL address information of the upgrade package corresponding to the second version information, size information of the upgrade package, or update log information.

1104. The second device determines and schedules the second module of the first device to download the upgrade package corresponding to the second version information from the server according to the first configuration information.

Wherein, the second module may be the above-mentioned upgrade package download module.

1105. The second module of the first device downloads an upgrade package corresponding to the second version information from the server.

Exemplarily, at least one of the identification information of the second device, the second version information, the Uniform Resource Locator address information of the upgrade package corresponding to the second version information, or the type information of the first software may be input to the second module. The second module outputs the download result of the upgrade package corresponding to the second version information.

Optionally, the second module further outputs at least one of the cache address of the upgrade package corresponding to the second version information or the download progress of the upgrade package corresponding to the second version information.

Optionally, the first device may send the download progress of the upgrade package corresponding to the second version information to the second device.

Further, the first module set further includes a third module, and the third module may be the aforementioned upgrade package security verification module. The second device may determine and schedule the third module to check the upgrade package corresponding to the second version information according to the first configuration information; the third module of the first device checks the upgrade package corresponding to the second version information.

Further, the first module set further includes a fourth module, which may be the upgrade package difference/compression restoration module mentioned above. The second device may determine and schedule the fourth module to perform differential restoration and/or compression restoration on the upgrade package corresponding to the second version information according to the first configuration information; the fourth module of the first device performs differential restoration on the upgrade package corresponding to the second version information Restore and/or Compress Restore.

1106. The first device sends an upgrade package corresponding to the second version information to the second device.

The first device sends an upgrade package corresponding to the second version information to the second device based on a near-field device communication protocol; wherein the near-field device communication protocol includes at least one of a Wi-Fi protocol, a Bluetooth protocol, or a near-field communication protocol.

1107. The second device receives an upgrade package corresponding to the second version information from the first device.

The second device may receive an upgrade package corresponding to the second version information from the first device based on the near-field device communication protocol.

1108. The second device installs an upgrade package corresponding to the second version information.

Optionally, the second device may send the installation progress of the upgrade package corresponding to the second version information to the first device.

In a possible design, the above system further includes a third device, the third device includes a third module set and second configuration information, the third module set is a subset of the first module set, and the third module set and the first The two module sets are different, and the above method also includes:

1109. The third device determines that the second software of the third device is to be upgraded, and the current version information of the second software is the third version information.

1110. The third device determines and schedules the first module of the first device to search for fourth version information of the second software from the server according to the second configuration information, where the fourth version information is different from the first version information.

1111. The first module of the first device searches for fourth version information of the second software from the server.

1112. The third device determines and schedules the second module of the first device to download the upgrade package corresponding to the fourth version information from the server according to the second configuration information;

1113. The second module of the first device downloads an upgrade package corresponding to the fourth version information from the server.

1114. The first device sends an upgrade package corresponding to the fourth version information to the third device.

1115. The third device receives an upgrade package corresponding to the fourth version information from the first device.

1116. The third device installs an upgrade package corresponding to the fourth version information.

Wherein, for the process of step 1109-step 1116, reference may be made to the relevant description of step 1101-step 1118, which will not be repeated here.

It should be noted that the first device in the embodiment described in FIG. 11 may be the mobile phone in the foregoing embodiments, the second device may be a sound box, and the third device may be an earphone, which is not detailed in the embodiment described in FIG. 11 For the above-mentioned part, reference may be made to the foregoing embodiments, and details are not repeated here.

Based on the method provided in the embodiment of the present application, the first device (for example, a mobile phone) can use the same set of upgrade frameworks to upgrade different types of second devices (for example, speakers or earphones), the storage space consumption of the mobile phone is small, and the mobile phone can Different capability assistance is provided for different types of second devices through the upgrade framework. For example, for a headset that only has communication capabilities such as Bluetooth and NFC, the mobile phone can assist the headset to search for and download an upgrade package. For another example, for a device without a touch screen or a device with cumbersome user interaction operations (for example, the process of operating a TV through a remote control is cumbersome), the mobile phone can provide the TV with user interaction capabilities. For another example, for a second device that cannot support differential restoration capability and security verification capability, the mobile phone can provide the security verification capability for the second device. transfer protocol over secure socket (HTTPS) security protocol and public key infrastructure (public key infrastructure, PKI) authentication. In this way, the effective extension of the first device to assist the upgrade of the second device can be realized.

Another embodiment of the present application provides a chip system. As shown in FIG. 12 , the chip system includes at least one processor 1201 and at least one interface circuit 1202 . The processor 1201 and the interface circuit 1202 may be interconnected through wires. For example, the interface circuit 1202 may be used to receive signals from other means (eg, a memory of a first device, a memory of a second device, or a memory of a third device). As another example, the interface circuit 1202 may be used to send signals to other devices (such as the processor 1201).

For example, the interface circuit 1202 may read instructions stored in a memory in the device and send the instructions to the processor 1201 . When the instructions are executed by the processor 1201, the first device or the second device (such as the electronic device 200 shown in FIG. 1B ) may be made to execute various steps in the foregoing embodiments.

Of course, the chip system may also include other discrete devices, which is not specifically limited in this embodiment of the present application.

Other embodiments of the present application provide a first device (such as the electronic device 200 shown in FIG. 1B ), where the first device may include: a communication module, a memory, and one or more processors. The communication module, memory and processor are coupled. The memory is used to store computer program code comprising computer instructions.

Another embodiment of the present application provides a second device. As shown in FIG. 13 , the second device 1300 includes a communication module 1303 , a memory 1302 and one or more processors 1301 . The communication module 1303 , the memory 1302 are coupled with the processor 1201 . Wherein, the memory 1302 is used for storing computer program codes, and the computer program codes include computer instructions. When the computer instructions are executed by the processor 1301, the second device 1300 is made to perform various functions or steps performed by the second device in the foregoing method embodiments.

The embodiment of the present application also provides a computer-readable storage medium. The computer-readable storage medium includes computer instructions. When the computer instructions are run on the first device (such as the electronic device 200 shown in FIG. 1B ), the electronic The device 200 executes various functions or steps performed by the first device (for example, a mobile phone) in the foregoing method embodiments. When the computer instructions are run on the second device (such as the second device 1300 shown in FIG. 13 ), the second device 1300 is made to execute the various functions performed by the second device (for example, speaker or earphone) in the above method embodiments. or steps.

The embodiment of the present application also provides a computer program product. When the computer program product is run on a computer, the computer is made to execute the first device (for example, a mobile phone) or the second device (for example, a speaker) in the above method embodiment. or earphones) perform various functions or steps.

Through the description of the above embodiments, those skilled in the art can clearly understand that for the convenience and brevity of the description, only the division of the above functional modules is used as an example for illustration. In practical applications, the above functions can be assigned by Completion of different functional modules means that the internal structure of the device is divided into different functional modules to complete all or part of the functions described above.

In the several embodiments provided in this application, it should be understood that the disclosed devices and methods may be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the modules or units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be Incorporation or may be integrated into another device, or some features may be omitted, or not implemented. In another point, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical, mechanical or other forms.

The unit described as a separate component may or may not be physically separated, and the component displayed as a unit may be one physical unit or multiple physical units, that is, it may be located in one place, or may be distributed to multiple different places . Part or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit. The above-mentioned integrated units can be implemented in the form of hardware or in the form of software functional units.

If the integrated unit is realized in the form of a software function unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application is essentially or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, and the software product is stored in a storage medium Among them, several instructions are included to make a device (which may be a single-chip microcomputer, a chip, etc.) or a processor (processor) execute all or part of the steps of the methods described in the various embodiments of the present application. The above-mentioned storage medium includes: U disk, mobile hard disk, read only memory (read only memory, ROM), random access memory (random access memory, RAM), magnetic disk or optical disk, and other various media that can store program codes.

The above content is only the specific implementation of the application, but the protection scope of the application is not limited thereto, and any changes or replacements within the technical scope disclosed in the application shall be covered within the protection scope of the application. Therefore, the protection scope of the present application should be determined by the protection scope of the claims.

Claims (19)

1. A software upgrade method applied to a system including a first device, a second device and a server, wherein the first device includes a first module set including a first module and a second module, the second device includes a second module set and first configuration information, and the second module set is a subset of the first module set, the method comprising:

the second equipment determines that first software of the second equipment is to be upgraded, wherein the current version information of the first software is first version information;

the second device determines to schedule the first module of the first device to search the server for second version information of the first software according to the first configuration information, wherein the second version information is different from the first version information; wherein the first configuration information is determined by the second device according to the capability information of the second device and the capability information of the first device; the capability information of the second device comprises at least one of communication capability, processing capability and display capability of the second device, and the capability information of the first device comprises at least one of communication capability, processing capability and display capability of the first device;

the first module of the first device searching the server for the second version information of the first software;

the second equipment determines to schedule the second module of the first equipment to download the upgrade package corresponding to the second version information from the server according to the first configuration information;

the second module of the first device downloads the upgrade package corresponding to the second version information from the server;

the first equipment sends an upgrade package corresponding to the second version information to the second equipment;

the second equipment receives the upgrade package corresponding to the second version information from the first equipment;

and the second equipment installs the upgrade package corresponding to the second version information.

2. The method of claim 1, wherein the system further comprises a third device comprising a third set of modules and second configuration information, wherein the third set of modules is a subset of the first set of modules, and wherein the third set of modules is different from the second set of modules, the method further comprising:

the third equipment determines that second software of the third equipment is to be upgraded, wherein the current version information of the second software is third version information;

the third device determines to schedule the first module of the first device to search for fourth version information of the second software from the server according to the second configuration information, wherein the fourth version information is different from the first version information;

the first module of the first device searching the server for the fourth version information of the second software;

the third equipment determines to schedule the second module of the first equipment to download the upgrade package corresponding to the fourth version information from the server according to the second configuration information;

the second module of the first device downloads the upgrade package corresponding to the fourth version information from the server;

the first equipment sends an upgrade package corresponding to the fourth version information to the third equipment;

the third equipment receives the upgrade package corresponding to the fourth version information from the first equipment;

and the third equipment installs the upgrade package corresponding to the fourth version information.

3. The method of claim 1 or 2, wherein the first set of modules further comprises a third module, the method further comprising:

the second equipment determines to schedule the third module of the first equipment to check the upgrade package corresponding to the second version information according to the first configuration information;

and the third module of the first equipment verifies the upgrade package corresponding to the second version information.

4. The method of claim 3, wherein the first set of modules further comprises a fourth module, the method further comprising:

the second device determines to schedule the fourth module of the first device to perform differential restoration and/or compression restoration on the upgrade package corresponding to the second version information according to the first configuration information;

and the fourth module of the first device performs differential restoration and/or compression restoration on the upgrade package corresponding to the second version information.

5. The method of any of claims 1, 2, and 4, wherein the first module of the first device searching for second version information of the first software from the server comprises:

and inputting the identification information of the second device and the type information of the first software to the first module, and outputting the search result of the second version information by the first module.

6. The method of claim 5,

the first module further outputs at least one of the second version information, uniform resource locator address information of an upgrade package corresponding to the second version information, upgrade package size information, or update log information.

7. The method according to any one of claims 1, 2, 4 and 6, wherein the downloading, by the second module of the first device, the upgrade package corresponding to the second version information from the server includes:

inputting at least one of identification information of the second device, the second version information, uniform resource locator address information of an upgrade package corresponding to the second version information, or type information of the first software to the second module, and outputting a download result of the upgrade package corresponding to the second version information by the second module.

8. The method of claim 7,

the second module further outputs at least one of a cache address of the upgrade package corresponding to the second version information or a download progress of the upgrade package corresponding to the second version information.

9. The method of any one of claims 1, 2, 4, 6, 8,

the first set of modules or the second set of modules are integrated in an SDK.

10. The method of any one of claims 1, 2, 4, 6, and 8, wherein before the second device determines that the first software of the second device is to be upgraded, the method further comprises:

the first equipment displays prompt information on a first interface of an application program, wherein the prompt information is used for prompting that first software of the second equipment is to be upgraded;

the first device receives a first operation of a user, wherein the first operation is used for upgrading the first software of the second device;

and the first equipment sends a notification message to the second equipment, wherein the notification message is used for indicating that the first software is to be upgraded.

11. The method according to any one of claims 1, 2, 4, 6, and 8, wherein the sending, by the first device, the upgrade package corresponding to the second version information to the second device includes:

the first equipment sends an upgrade packet corresponding to the second version information to the second equipment based on a near field equipment communication protocol; wherein the near field device communication protocol comprises at least one of a wireless fidelity protocol, a Bluetooth protocol, or a near field communication protocol.

12. The method of any one of claims 1, 2, 4, 6, 8, further comprising:

and the first equipment sends the download progress of the upgrade package corresponding to the second version information to the second equipment.

13. The method of any one of claims 1, 2, 4, 6, 8, further comprising:

and the second equipment sends the installation progress of the upgrade package corresponding to the second version information to the first equipment.

14. The method according to any one of claims 1, 2, 4, 6, 8,

the type of the first software includes at least one of firmware, a patch, a software development kit, a plug-in, or a device parameter.

15. The method according to any one of claims 1, 2, 4, 6, 8,

the first configuration information is provided by a manufacturer of the second device.

16. A software upgrading method applied to a first device, wherein the first device comprises a first module set, the first module set comprises a first module and a second module, and the method comprises the following steps:

the first equipment determines that first software of second equipment is to be upgraded, wherein the current version information of the first software is first version information; wherein the second device comprises a second set of modules and first configuration information, the second set of modules being a subset of the first set of modules, the first configuration information being determined by the second device from capability information of the second device and capability information of the first device; the capability information of the second device comprises at least one of communication capability, processing capability and display capability of the second device, and the capability information of the first device comprises at least one of communication capability, processing capability and display capability of the first device;

the first module of the first device searches for second version information of the first software from a server;

the second module of the first device downloads the upgrade package corresponding to the second version information from the server;

and the first equipment sends the upgrade package corresponding to the second version information to the second equipment.

17. A method of upgrading software, comprising:

the method comprises the steps that a second device determines that first software of the second device is to be upgraded, wherein current version information of the first software is first version information;

the second equipment determines to schedule a first module of the first equipment to search second version information of the first software from a server according to first configuration information, wherein the second version information is different from the first version information; wherein the first configuration information is determined by the second device according to the capability information of the second device and the capability information of the first device; the capability information of the second device comprises at least one of communication capability, processing capability and display capability of the second device, and the capability information of the first device comprises at least one of communication capability, processing capability and display capability of the first device;

the second equipment determines to schedule a second module of the first equipment to download the upgrade package corresponding to the second version information from the server according to the first configuration information;

the second equipment receives the upgrade package corresponding to the second version information from the first equipment;

and the second equipment installs the upgrade package corresponding to the second version information.

18. A software upgrade system, comprising a first device performing the method of any one of claims 1-16, a second device performing the method of any one of claims 1-15 or 17, and a server.

19. A computer-readable storage medium comprising computer instructions;

when the computer instructions are run on a first device, cause the first device to perform the method of any one of claims 1-16;

alternatively, the computer instructions, when executed on a second device, cause the second device to perform the method of any of claims 1-15 or 17.

Images