CN111625283A

CN111625283A - Hardware updating method, device, system and computer readable storage medium

Info

Publication number: CN111625283A
Application number: CN202010450393.1A
Authority: CN
Inventors: 彭天成
Original assignee: Xian Wingtech Electronic Technology Co Ltd
Current assignee: Xian Wingtech Electronic Technology Co Ltd
Priority date: 2020-05-25
Filing date: 2020-05-25
Publication date: 2020-09-04

Abstract

The application relates to the technical field of communication, and provides a hardware updating method, device and system and a computer readable storage medium. The method comprises the following steps: acquiring information of target hardware; comparing the information of the target hardware with the locally stored hardware information; if the information of the target hardware does not exist in the locally stored hardware information, sending a target driver program acquisition request of the target hardware to a network data center through a pre-established wireless network access with the network data center, wherein the target driver program acquisition request comprises the information of the target hardware; receiving a target driver of the target hardware, which is requested to be fed back by the network data center according to the target driver acquisition request; and running the target driver. By adopting the method, resource waste can be avoided.

Description

Hardware updating method, device, system and computer readable storage medium

Technical Field

The present application relates to the field of communications technologies, and in particular, to a method, an apparatus, a system, and a computer-readable storage medium for updating hardware.

Background

With the development of communication technology and computer technology, smart handheld devices such as mobile phones and tablets are applied more and more widely, and the smart handheld devices are updated very frequently. The product just replaced may be under a crisis of elimination for half a year, resulting in the need to replace the product again with a new one.

At present, when the hardware of the intelligent handheld device is updated, due to the tight binding of the hardware and the software and the private customization of a manufacturer system, a new intelligent handheld device needs to be purchased, that is, the entire intelligent handheld device is updated.

However, in practice, not all modules in the smart handheld device need to be updated. The whole machine updating mode causes that modules which do not need to be updated in the intelligent handheld equipment are discarded, and resource waste is caused.

Disclosure of Invention

In view of the foregoing, it is desirable to provide a hardware updating method, apparatus, system and computer readable storage medium capable of avoiding resource waste.

The embodiment of the application provides a hardware updating method, which comprises the following steps:

acquiring information of target hardware;

comparing the information of the target hardware with the locally stored hardware information;

if the information of the target hardware does not exist in the locally stored hardware information, sending a target driver acquiring request of the target hardware to a network data center through a pre-established wireless network access with the network data center; the target driver acquiring request comprises information of the target hardware;

receiving a target driver of the target hardware, which is requested to be fed back by the network data center according to the target driver acquisition request;

and running the target driver.

In one embodiment, the method further comprises:

executing preset codes in a processor;

loading a bootstrap program in a read-only memory;

and loading a manufacturer system in the radio frequency baseband module to establish a wireless network access with the network data center.

In one embodiment, the method further comprises:

after the target driver program is successfully operated, storing the information of the target hardware;

and taking the stored information of the target hardware and the locally stored hardware information as new locally stored hardware information, and comparing the new information of the target hardware with the new locally stored hardware information after acquiring the new information of the target hardware.

In one embodiment, the method further comprises:

after power-on, determining to execute the step of acquiring the information of the target hardware; alternatively, the first and second electrodes may be,

and determining to execute the step of acquiring the information of the target hardware after receiving a target hardware information acquisition request triggered by a user.

In one embodiment, the method further comprises:

sending a data acquisition request to the network data center;

receiving data fed back by the network data center according to the data acquisition request;

displaying and/or playing the data.

In one embodiment, the target hardware is at least one of: the device comprises a touch display module, a camera, a sensor, a battery module, an audio module and an input/output interface.

An embodiment of the present application provides a hardware updating apparatus, the apparatus includes:

the acquisition module is used for acquiring the information of the target hardware;

the comparison module is used for comparing the information of the target hardware with the locally stored hardware information;

the sending module is used for sending a target driver acquiring request of the target hardware to a network data center through a pre-established wireless network access with the network data center if the information of the target hardware does not exist in the locally stored hardware information; the target driver acquiring request comprises information of the target hardware;

the receiving module is used for receiving a target driver of the target hardware, which is fed back by the network data center according to the target driver acquisition request;

and the running module is used for running the target driver.

An embodiment of the present application provides a hardware update system, including: a network data center and a peripheral hardware entity; the network data center is connected with the peripheral hardware entity through a wireless network access; the peripheral hardware entity comprises a processor and a communication module;

the peripheral hardware entity acquires information of target hardware through the processor, compares the information of the target hardware with locally stored hardware information through the processor, and sends a target driver acquisition request of the target hardware to the network data center through the communication module if the processor determines that the locally stored hardware information does not contain the information of the target hardware; the target driver acquiring request comprises information of the target hardware;

the network data center receives the target driver acquiring request, determines a target driver of the target hardware according to the target driver acquiring request, and sends the target driver to the peripheral hardware entity;

and the peripheral hardware entity receives the target driver through the communication module and runs the target driver through the processor.

In one embodiment, the peripheral hardware entity further comprises an operating system for maintaining communication with the network data center and controlling local hardware;

the peripheral hardware entity is used for interacting with a user, generating a data acquisition request according to the operation of the user, sending the data acquisition request to the network data center, receiving data fed back by the network data center according to the data acquisition request, and displaying and/or playing the data;

and the network data center is used for receiving the data acquisition request, determining the data after processing the data according to the data acquisition request, and sending the data to the peripheral hardware entity.

In one embodiment, the peripheral hardware entity executes a preset code in the processor through the processor, loads a bootstrap program in the read-only memory, and loads a vendor system in the radio frequency baseband module to establish a wireless network access with the network data center.

In an embodiment, after the target driver successfully operates, the peripheral hardware entity stores information of the target hardware through a processor, and uses the stored information of the target hardware and the locally stored hardware information as new locally stored hardware information through the processor, so that after the new information of the target hardware is obtained, the new information of the target hardware is compared with the new locally stored hardware information.

In one embodiment, after the peripheral hardware entity is powered on, the processor determines to execute the step of acquiring the information of the target hardware; or after receiving a target hardware information acquisition request triggered by a user through the display touch module or the audio module, determining and executing the step of acquiring the information of the target hardware through the processor.

The embodiment of the present application provides a handheld device, which includes a memory and a processor, where the memory stores a computer program, and the processor implements the steps of the hardware updating method provided in any embodiment of the present application when executing the computer program.

The embodiments of the present application provide a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the steps of the hardware updating method provided in any embodiment of the present application.

According to the hardware updating method, the device, the system and the computer readable storage medium provided by the embodiment of the application, when it is determined that the acquired information of the target hardware does not exist in the locally stored hardware information, a target driver acquiring request of the target hardware is sent to a network data center through a pre-established wireless network access with a network data center, and then the target driver of the target hardware fed back by the network data center according to the target driver acquiring request is received, and the target driver is operated to realize normal work of the target hardware, so that the target hardware is successfully updated. The hardware is updated in a modularization mode by acquiring the target driving program from the network data center, and compared with the conventional complete machine updating mode, on one hand, resource waste is avoided, and on the other hand, information safety problems such as loss and leakage of user information caused by complete machine updating are avoided.

Drawings

FIG. 1 is a diagram illustrating an exemplary implementation of a hardware update method;

FIG. 2 is a flowchart illustrating a hardware update method according to an embodiment;

FIG. 3 is a diagram illustrating the structure of peripheral hardware entities in one embodiment;

FIG. 4 is a schematic diagram of a network data center in one embodiment;

FIG. 5A is a diagram of a user interface for a hardware update method in one embodiment;

FIG. 5B is a diagram of another user interface for a hardware update method in one embodiment;

FIG. 6 is a flowchart illustrating a hardware update method according to another embodiment;

FIG. 7 is a schematic flow chart of user, peripheral hardware entity and network data center interaction in another embodiment;

FIG. 8 is a diagram showing a variation of a user interface diagram of a hardware update method according to another embodiment;

FIG. 9 is a block diagram showing the structure of a hardware update apparatus according to an embodiment;

FIG. 10 is a block diagram of a hardware update system in one embodiment;

FIG. 11 is a diagram of the internal structure of a handheld device in one embodiment.

Detailed Description

The purpose, technical solutions and advantages of the present application will become more apparent from the following detailed description of the present application with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.

Fig. 1 is a diagram illustrating an application scenario of the hardware update method according to an embodiment. The hardware updating method provided by the application can be applied to the application environment shown in fig. 1. The hardware updating method is applied to a hardware updating system. The hardware updating system comprises a peripheral hardware entity 11 and a network data center 12. Wherein, the peripheral hardware entity 11 communicates with the network data center 12 through a wireless network. The network data center 12 stores application data of users and drivers of each hardware in the peripheral hardware entities 11. When the peripheral hardware entity 11 needs to update the hardware, the information of the target hardware may be compared with the locally stored hardware information by acquiring the information of the target hardware, when it is determined that the locally stored hardware information does not include the information of the target hardware, a target driver acquisition request of the target hardware is sent to the network data center through a pre-established wireless network access with the network data center, and then the target driver of the target hardware fed back by the network data center according to the target driver acquisition request is received and operated, thereby successfully updating the target hardware. Compared with the conventional complete machine updating mode, the hardware updating method provided by the embodiment can realize modularized hardware updating, on one hand, resource waste is avoided, and on the other hand, information safety problems such as loss and leakage of user information caused by complete machine updating are avoided. The peripheral hardware entity 11 may be, but not limited to, various personal computers, notebook computers, smart phones, tablet computers, and portable wearable devices, and the network data center 12 may be implemented by an independent server or a server cluster formed by a plurality of servers.

FIG. 2 is a flowchart illustrating a hardware update method according to an embodiment. In one embodiment, as shown in FIG. 2, a hardware update method is provided. The embodiment is mainly illustrated by applying the method to the peripheral hardware entity 11 in fig. 1.

Step 201: and acquiring information of the target hardware.

Fig. 3 is a schematic structural diagram of a peripheral hardware entity in an embodiment. As shown in fig. 3, the peripheral hardware entity 11 in this embodiment includes: a processor 111, and a communication module 112, a Read-Only Memory (ROM) 113, a touch display module 114, a camera 115, a sensor module 116, a battery module 117, an audio module 118, and an input/output interface 119, all of which are connected to the processor 111. The processor 111 of the peripheral hardware entity 11 stores preset codes, the ROM113 stores a boot program, and the communication module 112 stores a system customized by a manufacturer.

The communication module 112 in this embodiment may specifically be a radio frequency baseband module. The communication module 112 may access a wireless network based on a communication standard.

Illustratively, the communication module 112 may include at least one of the following: the wireless local area network based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11b standard, a bluetooth unit, an infrared unit, a Zigbee (Zigbee) unit, a mobile Communication unit, a Radio Frequency Identification (RFID) unit, and a Near Field Communication (NFC) unit. The Mobile communication unit may use any communication standard or protocol, including but not limited to Global System for Mobile communication (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), and Long Term Evolution (LTE).

The touch display module 114 may include a display screen and a touch panel. The touch panel may include one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensor may not only sense the boundary of a touch or slide action, but also detect the duration and pressure associated with the touch or slide operation.

The cameras 115 may include front and rear cameras. The camera 115 may receive external multimedia data in a photographing mode or a video mode.

Sensor module 116 includes one or more sensors for providing various aspects of status assessment for peripheral hardware entities 11. Alternatively, the sensor module 116 may include a light sensor, a proximity sensor, an acceleration sensor, a gyro sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

The battery module 117 provides power to the various modules of the peripheral hardware entity 11. The battery module 117 may include a battery management system and a battery.

The audio module 118 may input and/or output audio signals. Alternatively, the audio module 118 may include a microphone, an earpiece, and a speaker.

The input/output interface 119 may be an interface for providing input/output functions on the peripheral hardware entity 11, such as a volume button, a start button, a charging interface, a headphone interface, and the like.

The target hardware may be hardware that needs to obtain a driver from the network data center 12 after being updated. For example, the target hardware may specifically be at least one of the touch display module 114, the camera 115, the sensor in the sensor module 116, the battery module 117, the audio module 118, and the input/output interface 119 in the peripheral hardware entity 11.

Specifically, the target hardware in this embodiment has corresponding information, where the information may be information that can uniquely identify the target hardware, such as a serial number of the target hardware.

After the peripheral hardware entity 11 is powered on, the processor 111 first executes the preset code, and loads the boot program in the ROM113, and then the processor 111 runs the kernel to obtain the information of the target hardware from the local.

In one implementation, the target hardware in this embodiment may be all the hardware in the peripheral hardware entity that needs to obtain the driver from the network data center 12 after updating. In this implementation, after the peripheral hardware entity is powered on, step 201 is determined to be performed. In this implementation, information of a plurality of target hardware may be acquired.

FIG. 5A is a diagram of a user interface for a hardware update method in one embodiment. As shown in fig. 5A, in this implementation, after the peripheral hardware entity is powered on, on the premise that the touch display module 114 can work normally, the user interface 501 is displayed on the touch display module 114 to prompt the user that the information of the target hardware is currently acquired.

In another implementation manner, the target hardware in this embodiment may be hardware that needs to obtain the driver from the network data center 12 after the update specified by the user in the peripheral hardware entity 11. In this implementation, after the peripheral hardware entity 11 is powered on, the user may trigger the target hardware information acquisition request. The target hardware information acquisition request may include a name of the target hardware.

For example, in a case that the audio module 118 can work normally, the user may trigger the target hardware information obtaining request through the audio module 118, for example, the user inputs a voice "please obtain information of a camera" to the audio module 118 of the peripheral hardware entity 11, where the "camera" is a name of the target hardware.

FIG. 5B is a diagram of another user interface for a method for updating hardware in an embodiment. For example, on the premise that the touch display module 114 can work normally, the user interface 502 is displayed on the touch display module 114, and the user can trigger the target hardware information acquisition request by clicking an icon of the corresponding hardware. The icon clicked by the user is the name of the target hardware.

In this implementation, a user may trigger multiple target hardware information acquisition requests.

Step 202: and comparing the information of the target hardware with the locally stored hardware information.

Specifically, the locally stored hardware information is the information of the hardware locally stored by the peripheral hardware entity 11 after the hardware can normally work. In other words, the hardware that can normally work in the peripheral hardware entity 11 stores the hardware information locally.

After the information of the target hardware is acquired, the information of the target hardware is compared with the locally stored hardware information to determine whether the target hardware is updated hardware.

Step 203: and if the information of the target hardware does not exist in the locally stored hardware information, sending a target driver acquiring request of the target hardware to the network data center through a pre-established wireless network access with the network data center.

The target driver acquiring request comprises information of target hardware.

Specifically, before step 203, a wireless network path between the peripheral hardware entity 11 and the network data center 12 needs to be established in advance. More specifically, the processor 111 may load a vendor-customized system stored in the communication module 112, for example, a vendor system in the rf baseband module, to implement establishing a wireless network access with the network data center 12.

The information of the target hardware does not exist in the locally stored hardware information, and the target hardware is indicated to be updated hardware. In this embodiment, the network data center 12 stores a driver of the target hardware. In order for the target hardware to work properly, the target driver of the target hardware needs to be acquired from the network data center 12.

Fig. 4 is a schematic structural diagram of a network data center in one embodiment. As shown in fig. 4, the network data center 12 provided in this embodiment includes drivers for each hardware. The vendor may upload the driver updates for the hardware to the network data center 12 in advance.

In step 203, the peripheral hardware entity 11 sends a target driver obtaining request of the target hardware to the network data center 12 through the wireless network.

After receiving the target driver acquisition request, the network data center 12 searches the target driver of the target hardware from the driver library according to the information of the target hardware in the target driver acquisition request. Then, the network data center 12 feeds back the target driver to the external hardware entity 11 through the wireless network path.

Step 204: and receiving the target driving program of the target hardware, which is requested to be fed back by the network data center according to the target driving program.

Step 205: and running the target driver.

In step 204, the peripheral hardware entity 11 receives the target driver of the target hardware fed back by the network data center 12 through the wireless network path. And then, running the target driver to realize the control of the target hardware. The control target hardware in this embodiment works to mean that the control target hardware realizes its own functions, for example, control the camera to successfully take a picture, control the touch display module to successfully display and successfully receive a touch operation.

Further, after the target driver is successfully operated, the information of the target hardware is stored; and taking the stored information of the target hardware and the locally stored hardware information as new locally stored hardware information, and comparing the new information of the target hardware with the new locally stored hardware information after acquiring the new information of the target hardware. Therefore, after the information of the target hardware is acquired next time, the information of the target hardware can be searched in the new locally stored hardware information, and the waste of network resources caused by acquiring the target driver of the target hardware again is avoided.

Optionally, after the target driver is successfully run, the peripheral hardware entity 11 may obtain, from the network data center 12, screen data preset by a user or configured by the network data center 12 by default, and display the screen data on the touch display module.

In the hardware updating method provided in this embodiment, when it is determined that there is no acquired information of the target hardware in the locally stored hardware information, a target driver acquisition request of the target hardware is sent to the network data center through a pre-established wireless network path with the network data center, and then the target driver of the target hardware fed back by the network data center according to the target driver acquisition request is received and the target driver is run to realize normal operation of the target hardware, so that the target hardware is successfully updated. The hardware is updated in a modularization mode by acquiring the target driving program from the network data center, and compared with the conventional complete machine updating mode, on one hand, resource waste is avoided, and on the other hand, information safety problems such as loss and leakage of user information caused by complete machine updating are avoided.

FIG. 6 is a flowchart illustrating a hardware update method according to another embodiment. As shown in fig. 6, the hardware updating method provided in this embodiment will be described in detail with respect to the subsequent steps based on the embodiment shown in fig. 2 and various alternatives. As shown in fig. 6, the hardware updating method provided in this embodiment further includes:

step 601: and sending a data acquisition request to a network data center.

Alternatively, step 601 may be performed after step 204. The peripheral hardware entity 11 in this embodiment is used to implement operations such as data display, user interaction, and sending a data acquisition request to the network data center 12. The network data center 12 processes the data obtaining request sent by the peripheral hardware entity 11, and feeds back data to the peripheral hardware entity 11 according to the data obtaining request.

With continued reference to fig. 4, the network data center 12 also includes application data for the user. Such as the user's account number, password, phone book, installed applications, etc.

In one implementation, the peripheral hardware entity 11 may generate the data obtaining request according to a user operation. For example, the user clicks an icon of a certain game by touching the display module. The peripheral hardware entity 11 generates a data acquisition request according to the operation of the user, where the data acquisition request is specifically to run the game.

After receiving the data acquisition request, the network data center 12 acquires the game-related information of the user, such as an account number, a game level, a game role, and the like, from the application data of the user, and executes the game according to the game-related information. And feeding back the picture after the game is run to the peripheral hardware entity 11.

In another implementation, the peripheral hardware entity 11 may generate the data acquisition request according to the data collected by the sensor module 116 or a preset program execution rule. For example, when the peripheral hardware entity 11 displays an image, it determines that the image is in the landscape display mode at this time according to the sensor module 116, and generates a landscape mode data acquisition request, and sends the request to the network data center 12.

After receiving the horizontal screen mode data acquisition request, the network data center 12 generates image display data in the horizontal screen mode, and sends the image display data to the external hardware entity 11.

Step 602: and receiving data fed back by the network data center according to the data acquisition request.

Step 603: the data is displayed and/or played.

Specifically, in step 602, the peripheral hardware entity 11 receives data fed back by the network data center 12. In step 603, when the data is text information or image information, the peripheral hardware entity 11 displays the data on the touch display module. When the data further includes audio information, the peripheral hardware entity 11 displays the data through the touch display module and plays the data through the audio module. When the data includes only audio information, the peripheral hardware entity 11 plays the data through the audio module.

Optionally, in step 603, when the peripheral hardware entity 11 displays and/or plays the data, the data may be verified and analyzed, and then displayed and/or played.

Fig. 7 is a schematic flow chart illustrating interaction among a user, a peripheral hardware entity, and a network data center according to another embodiment. As shown in fig. 7, the peripheral hardware entity 11 generates a data acquisition request by interacting with a user. And sends the data acquisition request to the network data center 12. The network data center 12 feeds back data to the external hardware entity 11 according to the data acquisition request. After receiving the data, the peripheral hardware entity 11 displays and/or plays the data.

The above process is described below as a specific example. Fig. 8 is a schematic diagram illustrating a change process of a user interface diagram of a hardware updating method according to another embodiment. As shown in fig. 8, a illustrates a user interface 801 displayed after the peripheral hardware entity 11 performs steps 201-204. Icons of respective programs installed by the user are shown in the user interface 801. When the user needs to run the application 2, the user clicks the icon of the application 2. After the user clicks the icon of the application 2, the peripheral hardware entity 11 generates an operation request of the application 2. Then, step 601 is executed to send an operation request of the application 1 to the network data center. After receiving the operation request of the application 2, the network data center operates the application 2 and feeds back the operated picture of the application 2 to the external hardware entity 11. The peripheral hardware entity 11 performs step 602 and step 603. b illustrates the user interface 802 after the peripheral hardware entity performs steps 601-603. Suppose the application 2 is a navigation program, and the b diagram shows a map screen after the navigation program is opened.

In the hardware updating method provided in this embodiment, the peripheral hardware entity 11 is a terminal for data acquisition, display and interaction, and is equivalent to a remote desktop. The operations of running, installing and the like of the application are all executed in the network data center 12. There is no large operating system, e.g., android, in the peripheral hardware entity 11, but only a small system maintains network data transmission and local hardware control. Thus, the requirement for the local hardware of the external hardware entity 11 is low, and the use cost of the user can be reduced.

In the hardware updating method provided by this embodiment, the peripheral hardware entity is configured to send a data acquisition request to the network data center, and receive data fed back by the network data center according to the data acquisition request, and display and/or play the data, so that the following technical effects are achieved: on one hand, the peripheral hardware entity is used for sending a data acquisition request, receiving data and presenting the data, the requirement on local hardware of the peripheral hardware entity is low, and the use cost of a user can be reduced; on the other hand, when the two peripheral hardware entities transmit data, the data are transmitted between the corresponding network data centers substantially, the data do not need to be transmitted between the two peripheral hardware entities, the network flow expenditure is saved, and meanwhile, the data transmission rate is improved.

It should be understood that, although the steps in the flowcharts of fig. 2 and 6 are shown in sequence as indicated by the arrows, the steps are not necessarily performed in sequence as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least some of the steps in fig. 2 and 6 may include multiple sub-steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, and the order of performing the sub-steps or stages is not necessarily sequential, but may be performed alternately or alternately with other steps or at least some of the sub-steps or stages of other steps.

FIG. 9 is a block diagram of a hardware update apparatus according to an embodiment. In one embodiment, as shown in fig. 9, there is provided a hardware update apparatus including: an obtaining module 91, a comparing module 95, a sending module 92, a receiving module 93 and an operating module 94, wherein:

the obtaining module 91 is configured to obtain information of the target hardware.

The comparison module 95 is configured to compare the information of the target hardware with the locally stored hardware information.

The sending module 92 is configured to send a target driver acquisition request of the target hardware to the network data center through a pre-established wireless network access with the network data center if it is determined that the information of the target hardware does not exist in the locally stored hardware information.

The target driver acquiring request comprises information of target hardware.

And the receiving module 93 is configured to receive a target driver of the target hardware, which is requested to be fed back by the network data center according to the target driver acquisition request.

And the running module 94 is used for running the target driver.

Optionally, the apparatus further comprises: the establishing module is used for executing a preset code in the processor, loading a bootstrap program in the read-only memory and loading a manufacturer system in the radio frequency baseband module so as to establish a wireless network access with the network data center.

Optionally, the apparatus further comprises: the storage module is used for storing the information of the target hardware after the target driver program is successfully operated; and taking the stored information of the target hardware and the locally stored hardware information as new locally stored hardware information, and comparing the new information of the target hardware with the new locally stored hardware information after acquiring the new information of the target hardware.

Optionally, the apparatus further includes a determining module, configured to determine to execute the step of obtaining information of the target hardware after the power is turned on; or, after receiving a target hardware information acquisition request triggered by a user, determining to execute a step of acquiring information of the target hardware.

Further, in an embodiment, the sending module 92 is further configured to send a data obtaining request to the network data center. The receiving module 93 is configured to receive data fed back by the network data center according to the data obtaining request. The device also comprises a display module and/or a playing module. The display module is used for displaying the data. The playing module is used for playing the data.

Optionally, the apparatus further includes a generating module, configured to generate a data obtaining request according to a user operation.

Optionally, the target hardware is at least one of: the device comprises a touch display module, a camera, a sensor, a battery module, an audio module and an input/output interface.

The hardware updating device provided by the embodiment realizes modularized hardware updating by acquiring the target driver from the network data center, and compared with the conventional complete machine updating mode, on one hand, resource waste is avoided, and on the other hand, information safety problems such as loss and leakage of user information caused by complete machine updating are avoided.

For the specific limitation of the hardware updating apparatus, reference may be made to the above limitation of the hardware updating method, which is not described herein again. The various modules in the hardware upgrade apparatus described above may be implemented in whole or in part by software, hardware, and combinations thereof. The modules can be embedded in a hardware form or independent of a processor in the handheld device, and can also be stored in a memory in the handheld device in a software form, so that the processor can call and execute operations corresponding to the modules.

FIG. 10 is a block diagram illustrating the architecture of a hardware update system in one embodiment. In one embodiment, a hardware update system is provided. The system comprises a network data center and peripheral hardware entities. The network data center and the peripheral hardware entities are connected through a wireless network access. The peripheral hardware entity includes a processor and a communication module.

The peripheral hardware entity obtains the information of the target hardware through the processor, compares the information of the target hardware with the locally stored hardware information through the processor, and sends a target driver obtaining request of the target hardware to the network data center through the communication module if the processor determines that the locally stored hardware information does not contain the information of the target hardware. The target driver acquiring request comprises information of target hardware.

And the network data center receives the target driver acquiring request, determines a target driver of the target hardware according to the target driver acquiring request, and sends the target driver to the external hardware entity.

The peripheral hardware entity receives the target driver through the communication module and runs the target driver through the processor.

In one embodiment, the peripheral hardware entity further includes an operating system for maintaining communication with the network data center and controlling the local hardware.

The peripheral hardware entity is used for interacting with a user, generating a data acquisition request according to the operation of the user, sending the data acquisition request to the network data center, receiving data fed back by the network data center according to the data acquisition request, and displaying and/or playing the data.

The network data center is used for receiving the data acquisition request, determining data after processing the data according to the data acquisition request, and sending the data to the external hardware entity.

In one embodiment, after the target driver is successfully operated, the peripheral hardware entity stores information of the target hardware through the processor, and uses the stored information of the target hardware and the locally stored hardware information as new locally stored hardware information through the processor, so that after the new information of the target hardware is obtained, the new information of the target hardware is compared with the new locally stored hardware information.

The hardware updating system provided by this embodiment realizes modularized hardware updating by obtaining the target driver from the network data center, and compared with the existing whole machine updating method, on one hand, resource waste is avoided, and on the other hand, information security problems such as loss and leakage of user information caused by whole machine updating are avoided.

FIG. 11 is a diagram of the internal structure of a handheld device in one embodiment. In one embodiment, a handheld device is provided, which may be a terminal, and the internal structure thereof may be as shown in fig. 11. The handheld device comprises a processor, a memory, a communication interface, a display screen and an input device which are connected through a system bus. Wherein the processor of the handheld device is configured to provide computing and control capabilities. The memory of the handheld device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The communication interface of the handheld device is used for carrying out wired or wireless communication with an external terminal, and the wireless communication can be realized through WIFI, an operator network, Near Field Communication (NFC) or other technologies. The computer program is executed by a processor to implement a hardware update method. The display screen of the handheld device can be a liquid crystal display screen or an electronic ink display screen, and the input device of the handheld device can be a touch layer covered on the display screen, a key, a track ball or a touch pad arranged on a shell of the handheld device, an external keyboard, a touch pad or a mouse and the like.

Those skilled in the art will appreciate that the configuration shown in fig. 11 is a block diagram of only a portion of the configuration associated with the present application and does not constitute a limitation on the handheld device to which the present application is applied, and that a particular handheld device may include more or less components than those shown, or combine certain components, or have a different arrangement of components.

In one embodiment, the hardware updating apparatus provided in the present application may be implemented in a form of a computer program, and the computer program may be run on a handheld device as shown in fig. 11. The memory of the handheld device may store various program modules constituting the hardware updating apparatus, such as an obtaining module 91, a sending module 92, a receiving module 93 and an operating module 94 shown in fig. 9. The computer program constituted by the respective program modules causes the processor to execute the steps in the hardware updating method of the respective embodiments of the present application described in the present specification.

For example, the handheld device shown in fig. 11 may perform the step of acquiring information of the target hardware by the acquisition module 91 in the hardware upgrade apparatus shown in fig. 9. The handheld device may perform the step of comparing the information of the target hardware with the locally stored hardware information via the comparison module 95. The handheld device may execute, through the sending module 92, the step of sending the target driver acquisition request of the target hardware to the network data center through a pre-established wireless network access with the network data center if it is determined that the information of the target hardware does not exist in the locally stored hardware information. The handheld device may execute the step of receiving the target driver of the target hardware requested to be fed back by the network data center according to the target driver through the receiving module 93. The handheld device may perform the step of running the target driver via the run module 94.

In one embodiment, there is provided a handheld device comprising a memory storing a computer program and a processor implementing the following steps when the computer program is executed by the processor: acquiring information of target hardware; comparing the information of the target hardware with the locally stored hardware information; if the information of the target hardware does not exist in the locally stored hardware information, sending a target driver program acquisition request of the target hardware to a network data center through a pre-established wireless network access with the network data center, wherein the target driver program acquisition request comprises the information of the target hardware; receiving a target driver of the target hardware, which is requested to be fed back by the network data center according to the target driver acquisition request; and running the target driver.

In one embodiment, the processor, when executing the computer program, further performs the steps of: executing preset codes in a processor; loading a bootstrap program in a read-only memory; and loading a manufacturer system in the radio frequency baseband module to establish a wireless network access with the network data center.

In one embodiment, the processor, when executing the computer program, further performs the steps of: after the target driver program is successfully operated, storing the information of the target hardware; and taking the stored information of the target hardware and the locally stored hardware information as new locally stored hardware information, and comparing the new information of the target hardware with the new locally stored hardware information after acquiring the new information of the target hardware.

In one embodiment, the processor, when executing the computer program, further performs the steps of: after power-on, determining to execute the step of acquiring the information of the target hardware; or after receiving a target hardware information acquisition request triggered by a user, determining to execute the step of acquiring the information of the target hardware.

In one embodiment, the processor, when executing the computer program, further performs the steps of: sending a data acquisition request to the network data center; receiving data fed back by the network data center according to the data acquisition request; displaying and/or playing the data.

In one embodiment, the processor, when executing the computer program, further performs the steps of: and generating the data acquisition request according to user operation.

When it is determined that the locally stored hardware information does not contain the acquired information of the target hardware, the handheld device sends a target driver acquisition request of the target hardware to the network data center through a pre-established wireless network access with the network data center, and then receives a target driver of the target hardware fed back by the network data center according to the target driver acquisition request, and runs the target driver to realize normal operation of the target hardware, thereby successfully updating the target hardware. The hardware is updated in a modularization mode by acquiring the target driving program from the network data center, and compared with the conventional complete machine updating mode, on one hand, resource waste is avoided, and on the other hand, information safety problems such as loss and leakage of user information caused by complete machine updating are avoided.

In one embodiment, a computer-readable storage medium is provided, having a computer program stored thereon, which when executed by a processor, performs the steps of: acquiring information of target hardware; comparing the information of the target hardware with the locally stored hardware information; if the information of the target hardware does not exist in the locally stored hardware information, sending a target driver program acquisition request of the target hardware to a network data center through a pre-established wireless network access with the network data center, wherein the target driver program acquisition request comprises the information of the target hardware; receiving a target driver of the target hardware, which is requested to be fed back by the network data center according to the target driver acquisition request; and running the target driver.

In one embodiment, the computer program when executed by the processor further performs the steps of: executing preset codes in a processor; loading a bootstrap program in a read-only memory; and loading a manufacturer system in the radio frequency baseband module to establish a wireless network access with the network data center.

In one embodiment, the computer program when executed by the processor further performs the steps of: after the target driver program is successfully operated, storing the information of the target hardware; and taking the stored information of the target hardware and the locally stored hardware information as new locally stored hardware information, and comparing the new information of the target hardware with the new locally stored hardware information after acquiring the new information of the target hardware.

In one embodiment, the computer program when executed by the processor further performs the steps of: after power-on, determining to execute the step of acquiring the information of the target hardware; or after receiving a target hardware information acquisition request triggered by a user, determining to execute the step of acquiring the information of the target hardware.

In one embodiment, the computer program when executed by the processor further performs the steps of: sending a data acquisition request to the network data center; receiving data fed back by the network data center according to the data acquisition request; displaying and/or playing the data.

In one embodiment, the computer program when executed by the processor further performs the steps of: and generating the data acquisition request according to user operation.

In the computer-readable storage medium provided in this embodiment, when it is determined that there is no acquired information of the target hardware in the locally stored hardware information, a target driver acquisition request of the target hardware is sent to the network data center through a pre-established wireless network access with the network data center, and then the target driver of the target hardware fed back by the network data center according to the target driver acquisition request is received and the target driver is run to realize normal operation of the target hardware, so that the target hardware is successfully updated. The hardware is updated in a modularization mode by acquiring the target driving program from the network data center, and compared with the conventional complete machine updating mode, on one hand, resource waste is avoided, and on the other hand, information safety problems such as loss and leakage of user information caused by complete machine updating are avoided.

It will be understood by those skilled in the art that all or part of the processes of the methods of the above embodiments may be implemented by hardware related to instructions of a computer program, which may be stored in a non-volatile computer readable storage medium, and when executed, may include the processes of the above embodiments of the methods. Any reference to memory, database, or other medium used in the embodiments provided herein may include at least one of non-volatile and volatile memory. Non-volatile memory may include Read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical storage, or the like. Volatile Memory can include Random Access Memory (RAM) or external cache Memory. By way of illustration and not limitation, RAM is available in many forms, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), and the like.

The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.

The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent should be subject to the appended claims.

It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present invention and the technical principles employed. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.

Claims

1. A method for updating hardware, comprising:

acquiring information of target hardware;

and running the target driver.

2. The method of claim 1, further comprising:

executing preset codes in a processor;

loading a bootstrap program in a read-only memory;

3. The method of claim 1, further comprising:

4. The method of claim 1, further comprising:

5. The method according to any one of claims 1 to 4, further comprising:

sending a data acquisition request to the network data center;

displaying and/or playing the data.

6. The method of any one of claims 1 to 4, wherein the target hardware is at least one of: the device comprises a touch display module, a camera, a sensor, a battery module, an audio module and an input/output interface.

7. A hardware update apparatus, comprising:

and the running module is used for running the target driver.

8. A hardware update system, comprising: a network data center and a peripheral hardware entity; the network data center is connected with the peripheral hardware entity through a wireless network access; the peripheral hardware entity comprises a processor and a communication module;

9. The system of claim 8, wherein the peripheral hardware entity further comprises an operating system for maintaining communication with the network data center and controlling local hardware;

10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the hardware updating method of one of claims 1 to 7.