CN112035134B - Container software upgrading method, cloud server, container and device - Google Patents
Container software upgrading method, cloud server, container and device Download PDFInfo
- Publication number
- CN112035134B CN112035134B CN202010652139.XA CN202010652139A CN112035134B CN 112035134 B CN112035134 B CN 112035134B CN 202010652139 A CN202010652139 A CN 202010652139A CN 112035134 B CN112035134 B CN 112035134B
- Authority
- CN
- China
- Prior art keywords
- upgrade
- upgrade package
- client
- package information
- information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/30—Computing systems specially adapted for manufacturing
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention provides a container software upgrading method, a cloud server, a container and a container device. The method comprises the steps that a server receives upgrade request information sent by a client, wherein the upgrade request information comprises a device mode identifier of the client; if the equipment mode identifier is a self-camping mode, inquiring an operation main body of the client and selecting corresponding first upgrade package information according to the operation main body; if the equipment mode identifier is a foundry mode, querying a foundry manufacturer of the client and selecting corresponding second upgrade package information according to the foundry manufacturer; and returning the first upgrade package information or the second upgrade package information to the client so that the client upgrades according to the first upgrade package information or the second upgrade package information. Therefore, not only is the self-operating mode container of different operating main bodies upgraded, but also the substitute mode container of different substitute manufacturers is upgraded, the problem of singleization of the container software upgrading mode in the prior art is solved, and the operating safety risk brought by upgrading is reduced.
Description
Technical Field
The invention relates to the technical field of intelligent control, in particular to a container software upgrading method, a cloud server, a container and a device.
Background
Along with the development of informatization and networking technologies, intelligent containers are gradually widely applied, and the dependence of users on the intelligent containers is higher and higher. As the user demands and user experiences change, the demands for intelligence are also increasing, so that the software of the container is necessary to be upgraded regularly. However, the software upgrading of the current container is only aimed at a single mode, and brings a plurality of barriers to the business development of the company.
Therefore, to solve the above-mentioned problems, a new container software upgrading method, cloud server, container and device must be provided.
Disclosure of Invention
In order to achieve the above object, the present invention provides a method for upgrading container software, comprising: the method comprises the steps that a server receives upgrade request information sent by a client, wherein the upgrade request information comprises equipment mode identification of the client; if the equipment mode identifier is a self-operating mode, inquiring an operation main body of the client and selecting corresponding first upgrade package information according to the operation main body; if the equipment mode identifier is a foundry mode, querying a foundry manufacturer of the client and selecting corresponding second upgrade package information according to the foundry manufacturer; and returning the first upgrade package information or the second upgrade package information to the client so that the client upgrades according to the first upgrade package information or the second upgrade package information.
As a further improvement of the present invention, the upgrade request information includes a device unique identifier of the client; the querying the operation main body of the client comprises: determining that the unique equipment identifier exists in the prestored self-operating data information, and inquiring the operation main body according to the unique equipment identifier; the querying the foundry of the client includes: determining that the unique equipment identifier exists in the pre-stored substitution data information, and inquiring the substitution manufacturer according to the unique equipment identifier.
As a further improvement of the present invention, the querying the operator of the client further includes: if the fact that the unique equipment identifier does not exist in the prestored self-operating data information is determined, informing the client of ending the upgrade; the agent manufacturer querying the client further comprises: and if the fact that the unique equipment identifier does not exist in the pre-stored substitution data information is determined, informing the client of ending the upgrading.
As a further improvement of the present invention, the upgrade request information further includes current version information of the client; the querying the operation subject according to the equipment unique identification further comprises: inquiring whether a first configuration record of the latest upgrade version exists or not based on the upgrade request information; if the first configuration record does not exist, notifying the client to end upgrading; if the first configuration record exists, judging whether the first configuration record exists a designated operation main body or not, and returning the first upgrade package information based on a judging result; the querying the surrogate vendor according to the unique identifier of the device further comprises: inquiring whether a second configuration record of the latest upgrade version exists or not based on the upgrade request information; if the second configuration record does not exist, notifying the client to end upgrading; if the second configuration record exists, judging whether the second configuration record designates a manufacturer, and returning the second upgrade package information based on a judging result.
As a further improvement of the present invention, the determining whether the first configuration record has a designated operator, and returning the first upgrade package information based on a determination result includes: if the appointed operation main body does not exist, returning the first upgrade package information; if the appointed operation main body exists, returning the first upgrade package information according to a matching result of the appointed operation main body and the operation main body; the determining whether the second configuration record designates a manufacturer, and returning the second upgrade package information based on the determination result includes: if the designated manufacturer does not exist, returning the second upgrade package information; and if the designated substitution manufacturer exists, returning the second upgrade package information according to the matching result of the designated substitution manufacturer and the substitution manufacturer.
As a further improvement of the present invention, the returning the first upgrade package information according to the matching result between the designated operator and the operator includes: if the appointed operation main body is not matched with the operation main body, notifying the client end of upgrading; if the appointed operation main body is matched with the operation main body, returning the first upgrade package information; and returning the second upgrade package information according to the matching result of the designated foundry manufacturer and the foundry manufacturer, wherein the second upgrade package information comprises the following steps: if the designated forwarder manufacturer is not matched with the forwarder manufacturer, notifying the client of ending the upgrade; and if the designated foundry manufacturer is matched with the foundry manufacturer, returning the second upgrade package information.
As a further improvement of the present invention, the first upgrade package information and the second upgrade package information both include a download link address and a version number of the software to be upgraded.
The invention also provides an upgrading method of the container software, which comprises the following steps: the method comprises the steps that a client sends upgrading request information to a server, wherein the upgrading request information comprises equipment mode identification of the client; receiving the first upgrade package information or the second upgrade package information returned by the server according to the equipment mode identifier; the first upgrade package information determines that the equipment mode identifier is a self-operating mode for the server, inquires an operation main body and selects according to the operation main body, and the second upgrade package information determines that the equipment mode identifier is a labor-substituting mode for the server, inquires a labor-substituting manufacturer and selects according to the labor-substituting manufacturer; and receiving the first upgrade package information or the second upgrade package information, and upgrading according to the first upgrade package information or the second upgrade package information.
As a further improvement of the present invention, the first upgrade package information and the second upgrade package information both include a download link address and a version number of the software to be upgraded; the receiving the first upgrade package information or the second upgrade package information, and upgrading according to the first upgrade package information or the second upgrade package information, includes: receiving the download link address, and downloading a first upgrade package or a second upgrade package according to the download link address; updating the current version information according to the version number of the software to be upgraded; based on the first upgrade package or the second upgrade package, the upgrade is completed within a predetermined time range.
The invention also provides a cloud server, which comprises: a processor, a memory, and a communication network, the processor being coupled to the memory and the communication network, respectively; the processor, the memory and the communication network may be operable to implement the upgrade method described above.
The invention also provides a container comprising: a processor, a memory, and a communication network, the processor being coupled to the memory and the communication network, respectively; the processor, the memory and the communication network may be operable to implement the upgrade method described above.
The invention also provides a device with a storage function, which stores program instructions capable of being executed by a processor, and the program instructions are used for realizing the upgrading method.
Compared with the prior art, the invention has the beneficial effects that:
according to the container software upgrading method, the equipment mode of the client is identified to be the self-operating mode or the substitution mode, the operation main body or the substitution manufacturer is inquired according to the equipment mode identification, and corresponding upgrading package information is selected according to different operation main bodies or substitution manufacturers to return to the client, so that the container software upgrading method not only realizes the upgrading of the container in the self-operating mode of different operation main bodies, but also realizes the upgrading of the container in the substitution mode of different substitution manufacturers, solves the problem of singleness of the container software upgrading mode in the prior art, and reduces the operation safety risk brought by upgrading.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art. Wherein:
FIG. 1 is a flow chart of an embodiment of a method for upgrading container software according to the present invention;
FIG. 2 is a flow chart of another embodiment of the method for upgrading container software according to the present invention;
FIG. 3 is a flow chart of an embodiment of a method for upgrading container software according to the present invention;
FIG. 4 is a schematic diagram of a cloud server according to an embodiment of the present invention;
fig. 5 is a schematic structural diagram of a memory device according to an embodiment of the invention.
Detailed Description
The following describes the embodiments of the present application in detail with reference to the drawings.
In the following description, for purposes of explanation and not limitation, specific details are set forth such as the particular system architecture, interfaces, techniques, etc., in order to provide a thorough understanding of the present application.
The terms "system" and "network" are often used interchangeably herein. The term "and/or" is herein merely an association relationship describing an associated object, meaning that there may be three relationships, e.g., a and/or B, may represent: a exists alone, A and B exist together, and B exists alone. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship. Further, "a plurality" herein means two or more than two.
Referring to FIG. 1, the invention provides a method for upgrading container software, which specifically comprises the following steps:
s11: the server receives upgrade request information sent by the client, wherein the upgrade request information comprises a device mode identifier of the client.
In one embodiment, the server receives upgrade request information sent by the client, indicating that the client needs to upgrade at least one file in the installed software. The equipment mode identifier in the upgrade request information indicates whether the corresponding container equipment is in a self-operating mode or a substitution mode.
In addition, it should be noted that the equipment mode identifier is written into the client software configuration file when the container is checked.
Specifically, the upgrade request information further includes a device unique identifier of the client, current version information, and the like. The current version information comprises a current software version number, a current upgrade package type, a current upgrade version identifier and the like.
S12: if the equipment mode identifier is a self-camping mode, inquiring an operation main body of the client and selecting corresponding first upgrade package information according to the operation main body.
In this embodiment, after receiving the upgrade request information sent by the client, the server needs to determine whether the device mode identifier in the upgrade request information is a self-owned mode or a proxy mode. In one case, if the device mode identifier determines that the device mode is the self-camping mode, the operation main body of the client needs to be further queried, and corresponding first upgrade package information is selected according to the operation main body.
Specifically, the operation body of the query client in the step S12 further includes: and determining that the unique equipment identifier exists in the prestored self-operating data information, and inquiring an operation main body according to the unique equipment identifier. In this embodiment, for convenience of query, the self-owned data information is a self-owned data table. Thus, the operation subject can be inquired in the corresponding data information through the unique identification of the equipment.
Conversely, the operation body of the query client in the step S12 may further include: and if the fact that the unique equipment identifier does not exist in the prestored self-operating data information is determined, informing the client of ending the upgrading.
In this embodiment, first, whether the unique identifier of the device exists in the self-operating data information is determined; if the unique equipment identifier exists, inquiring an operation main body according to the unique equipment identifier; if the unique identification of the equipment does not exist, the method directly returns that the unique identification of the client equipment does not exist so as to inform the client of ending the upgrade.
Of course, in other embodiments of the present invention, the notification of the end upgrade of the client may be other manners, for example, the server does not return the response information of the client within a certain time range, which is also within the scope of the present invention.
Further, the querying the operation subject according to the device unique identifier includes: based on the upgrade request information, whether a first configuration record of the latest upgrade version exists is queried. In one case, if the first configuration record does not exist, notifying the client to end the upgrade; in another case, if the first configuration record exists, whether the first configuration record exists a designated operation main body is continuously judged, and the first upgrade package information is returned based on the judging result.
Specifically, in this embodiment, according to the unique identifier of the device and the current version information, the server queries whether the first configuration record of the latest upgrade version exists, and if not, returns to the upgrade configuration of the client which does not meet the condition, so that the upgrade is not required.
Therefore, the invention realizes the effect of upgrading the software aiming at the appointed operation main body, and reduces the safety risk brought by online upgrading deployment.
In an embodiment, the determining whether the first configuration record has the designated operation body and returning the first upgrade package information based on the determination result specifically includes two cases: if the designated operation main body does not exist, the first upgrade package corresponding to the latest upgrade version at the moment is a system-wide upgrade package, namely the upgrade package is not specific to a certain operation main body, is a general upgrade package, and directly returns the first upgrade package information of the client; and if the designated operation main body exists, returning the first upgrade package information according to the matching result of the designated operation main body and the operation main body inquired in the previous step.
The step of returning the first upgrade package information according to the matching result of the designated operation main body and the operation main body inquired in the previous step comprises the following steps: if the appointed operation main body is not matched with the operation main body, informing the client end of upgrading; and if the appointed operation main body is matched with the operation main body, returning the first upgrade package information.
Specifically, if the designated operation main body is not matched with the operation main body, the upgrading requirement is not met, and the upgrading configuration which is not met by the client side is returned, so that the upgrading is not needed. If the appointed operation main body is matched with the operation main body, returning to a downloading link address of the first upgrade package of the client and a version number of the software to be upgraded.
S13: if the equipment mode is identified as the foundry mode, querying a foundry manufacturer of the client and selecting corresponding second upgrade package information according to the foundry manufacturer.
In another case, if the equipment mode identifier determines that the equipment mode is the substitution mode, the substitution manufacturer of the client needs to be further queried, and corresponding second upgrade package information is selected according to the substitution manufacturer. Therefore, the server can further inquire out the corresponding operation main body or the foundry according to different equipment mode identifiers, and then select the corresponding upgrade package information according to different operation main bodies or the foundry, so that the operation safety risk brought by upgrade is reduced.
Specifically, the foundry manufacturer of the query client in the step S13 further includes: determining that the unique equipment identifier exists in the pre-stored substitution data information, and inquiring the substitution manufacturer according to the unique equipment identifier.
In this embodiment, the proxy data information is a proxy data table for convenience of query. Therefore, the manufacturer can be queried in the corresponding data information through the unique identifier of the equipment.
Of course, in other embodiments of the present invention, the self-owned data information and the proxy data information may be other associated information types, and the purpose of the present invention may be achieved as long as the operation main body or the proxy manufacturer in the associated information corresponds to the unique identifier of the device one by one.
Conversely, the manufacturer substitute of the query client in the step S13 may further include: and if the fact that the unique equipment identifier does not exist in the pre-stored substitution data information is determined, informing the client to finish upgrading.
Likewise, in the present embodiment, it is first determined whether or not the unique identifier of the device exists in the substitute data information; if the unique equipment identifier exists, inquiring a manufacturer substitute according to the unique equipment identifier; if the unique identification of the equipment does not exist, the method directly returns that the unique identification of the client equipment does not exist so as to inform the client of ending the upgrade.
Of course, in other embodiments of the present invention, the two steps of notifying the client of the end of the update may be other manners, for example, the server does not return the response information of the client within a certain time range, which is also within the scope of the present invention.
Further, the querying the foundry business according to the device unique identification includes: and inquiring whether a second configuration record of the latest upgrade version exists or not based on the upgrade request information. In one case, if the second configuration record does not exist, notifying the client to end the upgrade; in another case, if the second configuration record exists, whether the second configuration record exists a designated manufacturer or not is continuously judged, and the second upgrade package information is returned based on the judgment result.
Specifically, in this embodiment, according to the unique identifier of the device and the current version information, the server queries whether the second configuration record of the latest upgrade version exists. If not, returning to the upgrade configuration which is not in accordance with the conditions of the client, so that the upgrade is not needed.
In an embodiment, the determining whether the second configuration record designates the manufacturer, and returning the second upgrade package information based on the determination result specifically includes two cases: similar to the above, if the first case is that no designated manufacturer exists, it indicates that the second upgrade package corresponding to the latest upgrade version is a full-system upgrade package, that is, the upgrade package is not specific to a certain operation main body, but is a general upgrade package, and the second upgrade package information of the client is directly returned; and if the designated forwarder exists, returning second upgrade package information according to the matching result of the designated forwarder and the forwarder queried in the previous step.
And returning second upgrade package information according to a matching result of the designated substitution manufacturer and the substitution manufacturer queried in the previous step, wherein the second upgrade package information comprises the following steps: if the designated foundry manufacturer is not matched with the foundry manufacturer, informing the client to finish upgrading; and if the designated foundry manufacturer is matched with the foundry manufacturer, returning second upgrade package information.
Specifically, if the designated foundry manufacturer is not matched with the foundry manufacturer, the upgrading requirement is not met, and the upgrading configuration which is not met by the client side is returned without upgrading. If the designated foundry manufacturer is matched with the foundry manufacturer, the download link address of the second upgrade package of the client and the version number of the software to be upgraded are returned.
S14: and returning the first upgrade package information or the second upgrade package information to the client so that the client upgrades according to the first upgrade package information or the second upgrade package information.
In an embodiment, if the device mode identifier is a self-operating mode, the first upgrade package information is selected according to the operation subject, and then the first upgrade package information is returned to the client in this step, so that the client upgrades according to the first upgrade package information. In another embodiment, if the equipment mode is identified as the foundry mode, the second upgrade package information is selected according to the foundry, and then the second upgrade package information is returned to the client in this step, so that the client upgrades according to the second upgrade package information.
According to the container software upgrading method, the equipment mode of the client is identified to be the self-operating mode or the substitution mode, the operation main body or the substitution manufacturer is inquired according to the equipment mode identification, and corresponding upgrading package information is selected according to different operation main bodies or substitution manufacturers to return to the client, so that the container software upgrading method not only realizes the upgrading of the container in the self-operating mode of different operation main bodies, but also realizes the upgrading of the container in the substitution mode of different substitution manufacturers, solves the problem of singleness of the container software upgrading mode in the prior art, and reduces the operation safety risk brought by upgrading.
The foregoing describes an embodiment of the method for upgrading container software of the present invention from the perspective of the server side, and an embodiment of the method for upgrading container software of the present invention from the perspective of the client side will be described below with reference to fig. 2.
Referring to FIG. 2, the method for upgrading container software of the present embodiment includes:
s21: the client sends upgrade request information to the server, wherein the upgrade request information comprises a device mode identifier of the client.
Specifically, the client requests the server software upgrade interface with upgrade request information, and specifically, the upgrade request information includes a device mode identifier, a device unique identifier of the client, current version information, and the like. The equipment mode identifier is written into the software configuration file when the container is checked, and the current version information comprises a current software version number, a current upgrade package type, a current upgrade version identifier and the like.
S22: receiving first upgrade package information or second upgrade package information returned by the server according to the equipment mode identification; the first upgrade package information determines that the equipment mode identifier is a self-operating mode for the server, inquires an operation main body and selects according to the operation main body, and the second upgrade package information determines that the equipment mode identifier is a substitution mode for the server, inquires a substitution manufacturer and selects according to the substitution manufacturer.
S23: and receiving the first upgrade package information or the second upgrade package information, and upgrading according to the first upgrade package information or the second upgrade package information.
Specifically, the first upgrade package information and the second upgrade package information both include a download link address and a version number of the software to be upgraded, and the step S23 includes: receiving a download link address, and downloading a first upgrade package or a second upgrade package according to the download link address; updating the current version information according to the version number of the software to be upgraded; based on the first upgrade package or the second upgrade package, the upgrade is completed within a predetermined time range. Specifically, the current software version number in the current version information is the version number of the software to be updated, and the software is updated within a specific predetermined time range, so that the current version information in the update request information is the updated latest version information when the next software is updated.
It should be noted that, in this embodiment, the same as the previous embodiment, the related content may refer to the previous embodiment, and the description thereof is omitted herein.
An embodiment of the method for upgrading container software according to the present invention will be described with reference to FIG. 3: firstly, writing a device mode identification into a client software configuration file when a container is subjected to business inspection, wherein a container client is attached with upgrade request information to request a server software upgrade interface; the method comprises the steps that a server side obtains a device mode identifier of a client side in upgrading request information and inquires a unique identifier of a device; if the self-operating mode is the self-operating mode, the unique equipment identifier is inquired in the self-operating data information, and if the self-operating mode is the substitute operating mode, the unique equipment identifier is inquired in the substitute operating data information so as to judge whether the unique equipment identifier exists or not; if the equipment unique identifier does not exist, returning to the client, stopping upgrading, and if the equipment unique identifier does not exist, continuously inquiring an operation main body or a substitute manufacturer; then, the server side inquires a first configuration record or a second configuration record of the latest upgrade version according to the unique equipment identifier and the current version information so as to judge whether the first configuration record or the second configuration record exists or not; if the first configuration record does not exist, returning to the upgrade configuration of the client which does not meet the conditions, and if the first configuration record does not exist, continuing to judge whether the first configuration record designates an operation main body, and if the second configuration record does not exist, returning to the upgrade configuration of the client which does not meet the conditions, without upgrading, otherwise, continuing to judge whether the first configuration record designates a substitute manufacturer; if the appointed operation main body or the appointed substitution manufacturer does not exist, the method indicates that the upgrade package is a full system upgrade package, and returns a download link address of the corresponding upgrade package of the client and a version number of the software to be upgraded, so that the client downloads the link address of the corresponding upgrade package and updates the current version information; if the appointed operation main body or the appointed foundry manufacturer exists, whether the appointed operation main body is matched with the inquired operation main body or not is further judged, if not, the appointed foundry manufacturer is matched with the inquired foundry manufacturer or not, if not, the client is returned, the upgrading configuration which does not meet the conditions is not needed, if yes, the download link address of the corresponding upgrading package of the client and the version number of the software to be upgraded are returned, so that the client downloads the link address of the corresponding upgrading package and updates the current version information.
In summary, the method for upgrading container software provided by the invention identifies whether the equipment mode of the client is the self-operating mode or the substitution mode, inquires the operation main body or the substitution manufacturer according to the equipment mode identification, and further selects corresponding upgrade package information according to different operation main bodies or substitution manufacturers to return to the client, thereby realizing the upgrade of the self-operating mode containers of different operation main bodies, realizing the upgrade of the substitution mode containers of different substitution manufacturers, solving the problem of singleness of the container software upgrade mode in the prior art, and reducing the operation safety risk brought by the upgrade.
The invention also provides upgrading equipment which comprises a receiving module, a query module and an upgrading module. Specifically, the receiving module is used for receiving upgrade request information sent by the client, and the upgrade request information comprises a device mode identifier of the client; the query module is used for querying an operation main body of the client and selecting corresponding first upgrade package information according to the operation main body when the equipment mode identifier is a self-operating mode; when the equipment mode is identified as a foundry mode, querying a foundry manufacturer of the client and selecting corresponding second upgrade package information according to the foundry manufacturer; the upgrade module is used for returning the first upgrade package information or the second upgrade package information to the client so that the client upgrades according to the first upgrade package information or the second upgrade package information.
Referring to fig. 4, the present invention further provides a cloud server, which includes a processor 41, a memory 42 and a communication circuit 43, wherein the processor 41 is respectively coupled to the memory 42 and the communication circuit 43, and the processor 41, the memory 42 and the communication circuit 43 can implement the upgrade method in any of the above embodiments when working.
In particular, the processor 41 is adapted to control itself and the memory 42 to implement the steps of any of the calibration method embodiments described above. The processor 41 may also be referred to as a CPU (Central Processing Unit ). The processor 41 may be an integrated circuit chip with signal processing capabilities. The processor 41 may also be a general purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), a Field programmable gate array (Field-Programmable Gate Array, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. In addition, the processor 41 may be commonly implemented by a plurality of integrated circuit chips.
The invention also provides a container, which comprises a processor, a memory and a communication network, wherein the processor is respectively coupled with the memory and the communication network; the processor, memory and communication network may be operable to implement the upgrade method of any of the embodiments described above. It should be noted that, the container provided by the present invention has a similar structure to the cloud server described above, and specific contents may refer to the above and will not be described herein.
In addition, referring to fig. 5, the present invention further provides a storage device, where the storage device 60 stores a program instruction 600 that can be executed by a processor, and the program instruction 600 is used to implement the calibration method in any of the foregoing embodiments. That is, when the calibration method is implemented in software and sold or used as a separate product, the calibration method may be stored in a storage device 60 readable by an electronic device, where the storage device 60 may be a usb disk, an optical disk, a server, or the like.
In the several embodiments provided in the present application, it should be understood that the disclosed methods and apparatus may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of modules or units is merely a logical functional division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical, or other forms.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed over a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the embodiment.
In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.
The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be embodied essentially or in part or all or part of the technical solution contributing to the prior art or in the form of a software product stored in a storage medium, including several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor (processor) to perform all or part of the steps of the methods of the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
The foregoing description is only of embodiments of the present application, and is not intended to limit the scope of the patent application, and all equivalent structures or equivalent processes using the descriptions and the contents of the present application or other related technical fields are included in the scope of the patent application.
Claims (11)
1. An upgrade method of container software is characterized in that the upgrade method comprises the following steps:
the method comprises the steps that a server receives upgrade request information sent by a client, wherein the upgrade request information comprises a device mode identifier, a device unique identifier and current version information of the client;
if the device mode identifier is a self-operating mode, querying an operating main body of the client and selecting corresponding first upgrade package information according to the operating main body, wherein querying the operating main body of the client comprises: determining that the unique equipment identifier exists in prestored self-operating data information, inquiring the operation main body according to the unique equipment identifier, determining a first configuration record with the latest upgrading version based on the upgrading request information, judging whether the first configuration record has a designated operation main body or not, and returning the first upgrading packet information based on a judging result;
if the equipment mode is identified as a proxy mode, querying a proxy manufacturer of the client and selecting corresponding second upgrade package information according to the proxy manufacturer, wherein querying the proxy manufacturer of the client comprises: determining that the unique equipment identifier exists in pre-stored substitution data information, inquiring the substitution manufacturer according to the unique equipment identifier, determining a second configuration record with the latest upgrade version based on the upgrade request information, judging whether the second configuration record designates the substitution manufacturer or not, and returning the second upgrade package information based on a judgment result;
and returning the first upgrade package information or the second upgrade package information to the client so that the client upgrades according to the first upgrade package information or the second upgrade package information.
2. The upgrade method according to claim 1, wherein said querying the operator of the client further comprises: if the fact that the unique equipment identifier does not exist in the prestored self-operating data information is determined, informing the client of ending the upgrade;
the agent manufacturer querying the client further comprises: and if the fact that the unique equipment identifier does not exist in the pre-stored substitution data information is determined, informing the client of ending the upgrading.
3. The upgrade method according to claim 1, wherein said querying the operator according to the device unique identification further comprises:
based on the upgrade request information, if the first configuration record does not exist, informing the client of ending the upgrade;
the querying the surrogate vendor according to the unique identifier of the device further comprises:
and based on the upgrade request information, if the second configuration record does not exist, informing the client to end the upgrade.
4. The method for upgrading according to claim 3, wherein,
the step of judging whether the first configuration record has a designated operation main body or not and returning the first upgrade package information based on a judgment result comprises the following steps:
if the appointed operation main body does not exist, returning the first upgrade package information;
if the appointed operation main body exists, returning the first upgrade package information according to a matching result of the appointed operation main body and the operation main body;
the determining whether the second configuration record designates a manufacturer, and returning the second upgrade package information based on the determination result includes:
if the designated manufacturer does not exist, returning the second upgrade package information;
and if the designated substitution manufacturer exists, returning the second upgrade package information according to the matching result of the designated substitution manufacturer and the substitution manufacturer.
5. The upgrade method according to claim 4, wherein,
the step of returning the first upgrade package information according to the matching result of the designated operation main body and the operation main body, including:
if the appointed operation main body is not matched with the operation main body, notifying the client end of upgrading;
if the appointed operation main body is matched with the operation main body, returning the first upgrade package information;
and returning the second upgrade package information according to the matching result of the designated foundry manufacturer and the foundry manufacturer, wherein the second upgrade package information comprises the following steps:
if the designated forwarder manufacturer is not matched with the forwarder manufacturer, notifying the client of ending the upgrade;
and if the designated foundry manufacturer is matched with the foundry manufacturer, returning the second upgrade package information.
6. The upgrade method according to claim 1, wherein the first upgrade package information and the second upgrade package information each include a download link address and a software version number to be upgraded.
7. An upgrade method of container software is characterized in that the upgrade method comprises the following steps:
the method comprises the steps that a client sends upgrading request information to a server, wherein the upgrading request information comprises a device mode identifier, a device unique identifier and current version information of the client;
receiving first upgrade package information or second upgrade package information returned by the server according to the equipment mode identification; the first upgrade package information determines that the equipment mode identifier is a self-operating mode for the server, the operation main body is queried through the existence of the equipment unique identifier in the pre-stored self-operating data information, a first configuration record with the latest upgrade version is determined, and the first configuration record is selected by the appointed operation main body; the second upgrade package information determines that the equipment mode identifier is a substitution mode for the server, the substitution manufacturer is queried through the unique equipment identifier in the pre-stored substitution data information, a second configuration record of the latest upgrade version is determined, and the second configuration record is selected by the appointed substitution manufacturer;
and receiving the first upgrade package information or the second upgrade package information, and upgrading according to the first upgrade package information or the second upgrade package information.
8. The upgrade method according to claim 7, wherein the first upgrade package information and the second upgrade package information each include a download link address and a software version number to be upgraded; the receiving the first upgrade package information or the second upgrade package information, and upgrading according to the first upgrade package information or the second upgrade package information, includes:
receiving the download link address, and downloading a first upgrade package or a second upgrade package according to the download link address;
updating the current version information according to the version number of the software to be upgraded;
based on the first upgrade package or the second upgrade package, the upgrade is completed within a predetermined time range.
9. A cloud server, comprising: a processor, a memory, and a communication network, the processor being coupled to the memory and the communication network, respectively; the processor, the memory and the communication network being operable to implement the upgrade method of any one of claims 1-6.
10. A container, comprising: a processor, a memory, and a communication network, the processor being coupled to the memory and the communication network, respectively; the processor, the memory and the communication network being operable to implement the upgrade method of any one of claims 7-8.
11. An apparatus having a memory function, characterized in that program instructions executable by a processor for implementing the upgrade method according to any one of claims 1-6 or claims 7-8 are stored.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010652139.XA CN112035134B (en) | 2020-07-08 | 2020-07-08 | Container software upgrading method, cloud server, container and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010652139.XA CN112035134B (en) | 2020-07-08 | 2020-07-08 | Container software upgrading method, cloud server, container and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112035134A CN112035134A (en) | 2020-12-04 |
| CN112035134B true CN112035134B (en) | 2023-08-04 |
Family
ID=73578980
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010652139.XA Active CN112035134B (en) | 2020-07-08 | 2020-07-08 | Container software upgrading method, cloud server, container and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112035134B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114973502A (en) * | 2022-05-12 | 2022-08-30 | 深圳市乐科智控科技有限公司 | Method and system for supporting multi-manufacturer access to dynamic cabinet |
Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1763713A (en) * | 2004-10-22 | 2006-04-26 | 华为技术有限公司 | Mobile terminal software edition updating method |
| CN102695194A (en) * | 2012-05-17 | 2012-09-26 | 中国联合网络通信集团有限公司 | Element management system and method and system for self-configuration of eNodeBs |
| CN104065753A (en) * | 2014-07-11 | 2014-09-24 | 北京领通科技有限公司 | Pushing method, device and system of intelligent terminal file |
| CN104125558A (en) * | 2013-04-26 | 2014-10-29 | 中国移动通信集团上海有限公司 | Client-based service processing method, equipment and system |
| CN106412696A (en) * | 2016-09-20 | 2017-02-15 | 深圳Tcl数字技术有限公司 | System upgrading method and device for smart television |
| CN106411540A (en) * | 2015-07-27 | 2017-02-15 | 中兴通讯股份有限公司 | Software version management method and device |
| CN106775841A (en) * | 2016-11-29 | 2017-05-31 | 广州广电运通金融电子股份有限公司 | The method, system and device of plug-in unit upgrading |
| CN109271184A (en) * | 2018-08-28 | 2019-01-25 | 苏州浪潮智能软件有限公司 | A method of based on remote upgrade version security protection |
| CN109298878A (en) * | 2018-09-28 | 2019-02-01 | 冼汉生 | Law-enforcing recorder upgrade-system and law-enforcing recorder upgrade method based on Internet of Things |
| CN109408091A (en) * | 2018-10-15 | 2019-03-01 | 珠海格力电器股份有限公司 | A kind of method and apparatus of application upgrade |
| CN109600401A (en) * | 2017-09-30 | 2019-04-09 | 美的智慧家居科技有限公司 | Household electrical appliances upgrade method, client and server |
| CN111324363A (en) * | 2019-11-14 | 2020-06-23 | 杭州海康威视系统技术有限公司 | Equipment upgrading method, upgrading terminal, equipment and storage medium |
| CN111367545A (en) * | 2020-02-13 | 2020-07-03 | 北京三快在线科技有限公司 | Terminal upgrading method and device, server, terminal equipment and readable storage medium |
-
2020
- 2020-07-08 CN CN202010652139.XA patent/CN112035134B/en active Active
Patent Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1763713A (en) * | 2004-10-22 | 2006-04-26 | 华为技术有限公司 | Mobile terminal software edition updating method |
| CN102695194A (en) * | 2012-05-17 | 2012-09-26 | 中国联合网络通信集团有限公司 | Element management system and method and system for self-configuration of eNodeBs |
| CN104125558A (en) * | 2013-04-26 | 2014-10-29 | 中国移动通信集团上海有限公司 | Client-based service processing method, equipment and system |
| CN104065753A (en) * | 2014-07-11 | 2014-09-24 | 北京领通科技有限公司 | Pushing method, device and system of intelligent terminal file |
| CN106411540A (en) * | 2015-07-27 | 2017-02-15 | 中兴通讯股份有限公司 | Software version management method and device |
| CN106412696A (en) * | 2016-09-20 | 2017-02-15 | 深圳Tcl数字技术有限公司 | System upgrading method and device for smart television |
| CN106775841A (en) * | 2016-11-29 | 2017-05-31 | 广州广电运通金融电子股份有限公司 | The method, system and device of plug-in unit upgrading |
| CN109600401A (en) * | 2017-09-30 | 2019-04-09 | 美的智慧家居科技有限公司 | Household electrical appliances upgrade method, client and server |
| CN109271184A (en) * | 2018-08-28 | 2019-01-25 | 苏州浪潮智能软件有限公司 | A method of based on remote upgrade version security protection |
| CN109298878A (en) * | 2018-09-28 | 2019-02-01 | 冼汉生 | Law-enforcing recorder upgrade-system and law-enforcing recorder upgrade method based on Internet of Things |
| CN109408091A (en) * | 2018-10-15 | 2019-03-01 | 珠海格力电器股份有限公司 | A kind of method and apparatus of application upgrade |
| CN111324363A (en) * | 2019-11-14 | 2020-06-23 | 杭州海康威视系统技术有限公司 | Equipment upgrading method, upgrading terminal, equipment and storage medium |
| CN111367545A (en) * | 2020-02-13 | 2020-07-03 | 北京三快在线科技有限公司 | Terminal upgrading method and device, server, terminal equipment and readable storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112035134A (en) | 2020-12-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP1225744B1 (en) | Method and system to access software pertinent to an electronic peripheral device at an address based on a peripheral device identifier | |
| US7376944B2 (en) | Hardware ROM upgrade through an internet or intranet service | |
| US8055496B2 (en) | Ensuring product correctness in a multilingual environment | |
| US20170228230A1 (en) | Provisioning a device with multiple bit-size versions of a software component | |
| CN107632846B (en) | Firmware upgrade method and device, Shelf management module | |
| CN106775841B (en) | Method, system and device for upgrading plug-in | |
| US20070118507A1 (en) | Managing software configuration of a wireless device | |
| CN110706071B (en) | Exception handling method, device, server and system for order payment request | |
| EP3800538A1 (en) | Method and apparatus for data migration | |
| CN106027644B (en) | Service verification method and system | |
| US11288054B2 (en) | Vehicular communication system | |
| CN109445902B (en) | Data operation method and system | |
| CN112035134B (en) | Container software upgrading method, cloud server, container and device | |
| CN105704241A (en) | Client terminal program updating method and system and a service platform | |
| US20230359454A1 (en) | Software update device, update control method, and non-transitory storage medium | |
| WO2020233351A1 (en) | Blockchain-oriented data management method, apparatus and device, and storage medium | |
| CN113448756A (en) | Inter-process communication system and method and computing device | |
| CN114201197A (en) | Firmware upgrading method and device, electronic equipment and readable storage medium | |
| CN114995860A (en) | Method for upgrading firmware of graphic processor and graphic processor | |
| US20170345082A1 (en) | Systems and methods for staging customer premise equipment of a telecommunications network | |
| JP2001051810A (en) | Method for printer driver, update management, printer, and computer network system | |
| CN113986852A (en) | Driving program calibration parameter matching method and device, electronic equipment and storage medium | |
| US11075925B2 (en) | System and method to enable component inventory and compliance in the platform | |
| US20140316943A1 (en) | Method and apparatus for integrating an e-commerce provider with third-party vendors | |
| KR101461319B1 (en) | Methods and device for upgrading firmware of set-top box |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |