CN108632375B - Online upgrading method for distributed deployment service software program - Google Patents
Online upgrading method for distributed deployment service software program Download PDFInfo
- Publication number
- CN108632375B CN108632375B CN201810439466.XA CN201810439466A CN108632375B CN 108632375 B CN108632375 B CN 108632375B CN 201810439466 A CN201810439466 A CN 201810439466A CN 108632375 B CN108632375 B CN 108632375B
- Authority
- CN
- China
- Prior art keywords
- program
- server
- upgrading
- software program
- application
- 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
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L67/025—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
-
- 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
- G06F8/656—Updates while running
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/08—Protocols specially adapted for terminal emulation, e.g. Telnet
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/55—Push-based network services
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (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)
Abstract
The invention relates to the field of online software service, and discloses an online upgrading method for a distributed deployment service software program. By the invention, a solution capable of reducing the deployment complexity of the server and the upgrading difficulty of a subsequent server can be provided, on one hand, by using a Docker application container technology and distributively operating each application subprogram of the service software program, the resource occupancy rate can be reduced, the transverse expansion of a hardware system is convenient to carry out, the deployment difficulty of the server is reduced, the stability of an online service system can be greatly improved, and all-weather uninterrupted operation is realized; on the other hand, by utilizing the Jenkins server and the program version management server, automatic delivery and gray scale upgrading of upgrading program codes can be realized, and the upgrading difficulty of the server side is greatly reduced. In addition, each application subprogram is restarted and upgraded in a polling mode, so that the service is not interrupted in the upgrading process, and the method is convenient for practical application and popularization.
Description
Technical Field
The invention belongs to the field of online software services, and particularly relates to an online upgrading method for a distributed deployment service software program.
Background
At present, the traditional online service software is installed and deployed in a single point, namely, the whole software is installed and operated by directly using a single physical machine or virtual machine, and the problems of high investment cost and difficult maintenance and installation are solved. Specifically, the software installation and deployment tend to release an installation package, and then online debugging is performed, so that the upgrade of the server is far more difficult than that of the client, and in addition, the service interruption may occur.
Disclosure of Invention
In order to solve the above problems in the prior art, the present invention aims to provide an online upgrade method for a distributed deployment service software program.
The technical scheme adopted by the invention is as follows:
an online upgrade method for a distributed deployment service software program, comprising the steps of:
s101, splitting a service software program into a plurality of application subprograms, and operating the application subprograms in a target server in a one-to-one correspondence manner in the form of a Docker application container, wherein a Docker application container engine and a Jenkins terminal software program are pre-installed on the target server;
s102, logging in a Jenkins server, newly building an online monitoring project, and configuring a first parameter for pulling an upgrading program code from a program version management server in the online monitoring project;
s103, logging in a program version management server, and setting a second parameter associated with the Jenkins server;
s104, after receiving a service software program upgrading package from a software development end, a program version management server sends a program upgrading operation request message to a Jenkins server, wherein the service software program upgrading package is provided with upgrading program codes named by application subprogram names, and the program upgrading operation request message comprises all the application subprogram names in the service software program upgrading package;
s105, after receiving the program upgrading operation request message, the Jenkins server triggers a remote construction task for a target server corresponding to the application subprogram name, and transmits an upgrading program code which is pulled from a program version management server and corresponds to the application subprogram name to the target server through a Jenkins terminal software program running on the target server;
s106, after receiving the complete upgrading program code, the target server starts a Maven program package, and the upgrading program code is packaged into a Maven container;
s107, the target server pushes the mirror image of the Maven container to a local Docker private library to complete updating of the Docker application container mirror image corresponding to the application subprogram name;
s108, shutting down and restarting the target server, starting a Docker application container engine, obtaining a Docker application container mirror image corresponding to the application subprogram name from the Docker private library, and then running the application subprogram in the form of the Docker application container again to complete online upgrade.
Specifically, in step S102, the first parameter includes a URL address of the program version management server and an authentication token for triggering remote construction.
Specifically, the program version management server is an SVN server or a Git server. More specifically, when the program version management server is a Git server, in step S103, the second parameter includes a hook address and/or a URL request password for opening a hook function.
Optimally, if the service software program upgrading package is provided with a plurality of upgrading program codes named by different application subprogram names, the steps S105 to S108 are executed one by one according to a polling mode for each upgrading program code and target server corresponding to different application subprogram names.
And optimally, the Jenkins terminal software program and the Docker private library are respectively operated in a target server in a Docker application container mode.
Specifically, the target server is a physical machine or a virtual machine.
The invention has the beneficial effects that:
(1) the invention provides a solution which can reduce the deployment complexity of the server and the upgrading difficulty of the subsequent server, on one hand, by using the Docker application container technology and operating each application subprogram of the service software program in a distributed manner, the resource occupancy rate can be reduced, the transverse expansion of a hardware system is convenient to carry out, the deployment difficulty of the server is reduced, the stability of an online service system can be greatly improved, and all-weather uninterrupted operation is realized; on the other hand, by utilizing the Jenkins server and the program version management server, automatic delivery and gray scale upgrading of upgrading program codes can be realized, and the upgrading difficulty of a server side is greatly reduced;
(2) and each application subprogram is restarted and upgraded in a polling mode, so that the service is not interrupted in the upgrading process, and the method is convenient for practical application and popularization.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
FIG. 1 is a flow chart of the online upgrade method for a distributed deployment service software program according to the present invention.
FIG. 2 is a schematic structural diagram of an online upgrade system provided by the present invention.
Detailed Description
The invention is further described with reference to the following figures and specific embodiments. It should be noted that the description of the embodiments is provided to help understanding of the present invention, but the present invention is not limited thereto.
The term "and/or" herein is merely an association describing an associated object, meaning that three relationships may exist, e.g., a and/or B, may mean: a exists alone, B exists alone, and A and B exist at the same time, and the term "/and" is used herein to describe another association object relationship, which means that two relationships may exist, for example, A/and B, may mean: a alone, and both a and B alone, and further, the character "/" in this document generally means that the former and latter associated objects are in an "or" relationship.
Example one
As shown in fig. 1 and 2, the online upgrade method for a distributed deployment service software program provided in this embodiment includes the following steps.
S101, splitting a service software program into a plurality of application subprograms, and operating the application subprograms in a target server in a one-to-one correspondence mode in the form of a Docker application container, wherein a Docker application container engine and a Jenkins terminal software program are installed in the target server in advance.
In step S101, the Docker application container engine is an open-source application container engine, so that developers can package their application programs and dependency packages into a portable container, and then distribute the portable container to any popular Linux machine, and virtualization can also be implemented. The Docker application container is a fully-used sandbox mechanism, has no interfaces (like APP program of iPhone) with each other, has almost no performance overhead, can easily run in machines and data centers, and most importantly, can be independent of any language, framework and system, and has the following characteristics: (1) the container can be arranged, namely the container can be configured and arranged according to actual conditions, such as planning tasks, sharing files and sharing networks and the like; (2) the resource occupation is lower, the performance approaches to that of a native system, and the resource overhead of a virtual hardware layer can be saved compared with a virtual machine technology; (3) the running is started more quickly, and the starting in millisecond level can be realized. Therefore, by using the Docker application container technology, each application subprogram of the service software program is operated in a distributed mode, the resource occupancy rate can be reduced, the transverse expansion of a hardware system is facilitated, the deployment difficulty of the server is reduced, the stability of an online service system can be greatly improved, and all-weather uninterrupted operation is realized. Optimized, the Jenkins (Jenkins is an easy-to-use continuous integration system, which can be released from a complicated integration process by developers and is focused on more important business logic implementation, moreover, Jenkins can implement monitoring of errors existing in integration, provide detailed log files and reminding functions, and can also vividly show the trend and stability of project construction in the form of charts) terminal software programs also run in a target server in the form of a Docker application container. In addition, specifically, the target server may be, but is not limited to, a physical machine or a virtual machine.
S102, logging in a Jenkins server, newly building an online monitoring project, and configuring a first parameter for pulling an upgrading program code from a program version management server in the online monitoring project.
In step S102, specifically, the first parameter may include, but is not limited to, a URL address of the program version management server and an authentication token for triggering remote construction. The program version management server may be, but is not limited to, an SVN (version management tool, which is a rising version management tool in recent years, and most open source software uses an SVN as code version management software) server or a Git (Git is the currently most advanced distributed version control system) server. For example, as shown in fig. 2, the program version management server in the present embodiment employs a Git server.
And S103, logging in the program version management server, and setting a second parameter associated with the Jenkins server.
In the step S103, since the program version management server adopts a Git server, specifically, the second parameter may include, but is not limited to, a hook address and/or a URL (Uniform Resource Locator, which is a compact representation of a location and an access method of a Resource available from the internet and is an address of a standard Resource on the internet) request password for opening a hook function. Therefore, the fact that the Git server can transmit related messages and tasks to the Jenkins server after receiving the uploaded upgrading program codes can be guaranteed.
S104, after receiving a service software program upgrading package from a software development end, the program version management server sends a program upgrading operation request message to the Jenkins server, wherein the service software program upgrading package is filled with upgrading program codes named by application subprogram names, and the program upgrading operation request message contains all the application subprogram names in the service software program upgrading package.
And S105, after receiving the program upgrading operation request message, the Jenkins server triggers a remote construction task for the target server corresponding to the application subprogram name, and transmits the upgrading program code which is pulled from the program version management server and corresponds to the application subprogram name to the target server through the Jenkins terminal software program running on the target server.
And S106, after the target server receives the complete upgrading program code, starting a Maven program package, and packaging the upgrading program code into a Maven container.
In step S106, the Maven (an open source project management tool written in pure Java) package is used to call and compile upgrade program codes, which may be temporarily downloaded from a website or pre-stored in a target server.
S107, the target server pushes the mirror image of the Maven container to a local Docker private library to finish updating the Docker application container mirror image corresponding to the application subprogram name.
In step S107, the optimized Docker private library is also run in the target server in the form of a Docker application container.
S108, shutting down and restarting the target server, starting a Docker application container engine, obtaining a Docker application container mirror image corresponding to the application subprogram name from the Docker private library, and then running the application subprogram in the form of the Docker application container again to complete online upgrade.
Through the steps S104-S108, automatic delivery and gray scale upgrading of the upgrading program codes can be realized (namely if the upgrading of the current version fails, the version before rollback can be selected, and the upgrading is carried out after the new version is completed), so that the upgrading difficulty of the server is greatly reduced. If the service software program upgrading package is provided with a plurality of upgrading program codes named by different application subprogram names, the steps S105 to S108 are executed one by one according to a polling mode aiming at the upgrading program codes and the target servers corresponding to the different application subprogram names. Therefore, each application subprogram is restarted and upgraded in a polling mode, so that the service is not interrupted in the upgrading process, and the method is convenient for practical application and popularization.
In summary, the online upgrade method for the distributed deployment service software program provided by the embodiment has the following technical effects:
(1) the invention provides a solution which can reduce the deployment complexity of the server and the upgrading difficulty of the subsequent server, on one hand, by using the Docker application container technology and operating each application subprogram of the service software program in a distributed manner, the resource occupancy rate can be reduced, the transverse expansion of a hardware system is convenient to carry out, the deployment difficulty of the server is reduced, the stability of an online service system can be greatly improved, and all-weather uninterrupted operation is realized; on the other hand, by utilizing the Jenkins server and the program version management server, automatic delivery and gray scale upgrading of upgrading program codes can be realized, and the upgrading difficulty of a server side is greatly reduced;
(2) and each application subprogram is restarted and upgraded in a polling mode, so that the service is not interrupted in the upgrading process, and the method is convenient for practical application and popularization.
The present invention is not limited to the above-described alternative embodiments, and various other forms of products can be obtained by anyone in light of the present invention. The above detailed description should not be taken as limiting the scope of the invention, which is defined in the claims, and which the description is intended to be interpreted accordingly.
Claims (7)
1. An online upgrading method for a distributed deployment service software program is characterized by comprising the following steps:
s101, splitting a service software program into a plurality of application subprograms, and operating the application subprograms in a target server in a one-to-one correspondence manner in the form of a Docker application container, wherein a Docker application container engine and a Jenkins terminal software program are pre-installed on the target server;
s102, logging in a Jenkins server, newly building an online monitoring project, and configuring a first parameter for pulling an upgrading program code from a program version management server in the online monitoring project;
s103, logging in a program version management server, and setting a second parameter associated with the Jenkins server;
s104, after receiving a service software program upgrading package from a software development end, a program version management server sends a program upgrading operation request message to a Jenkins server, wherein the service software program upgrading package is provided with upgrading program codes named by application subprogram names, and the program upgrading operation request message comprises all the application subprogram names in the service software program upgrading package;
s105, after receiving the program upgrading operation request message, the Jenkins server triggers a remote construction task for a target server corresponding to the application subprogram name, and transmits an upgrading program code which is pulled from a program version management server and corresponds to the application subprogram name to the target server through a Jenkins terminal software program running on the target server;
s106, after receiving the complete upgrading program code, the target server starts a Maven program package, and the upgrading program code is packaged into a Maven container;
s107, the target server pushes the mirror image of the Maven container to a local Docker private library to complete updating of the Docker application container mirror image corresponding to the application subprogram name;
s108, shutting down and restarting the target server, starting a Docker application container engine, obtaining a Docker application container mirror image corresponding to the application subprogram name from the Docker private library, and then running the application subprogram in the form of the Docker application container again to complete online upgrade.
2. The method for online upgrade of a distributed deployment service software program of claim 1, wherein: in step S102, the first parameter includes a URL address of the program version management server and an authentication token for triggering remote construction.
3. The method for online upgrade of a distributed deployment service software program of claim 1, wherein: the program version management server is an SVN server or a Git server.
4. A method for online upgrade of a distributed deployment service software program, according to claim 3, characterized in that: when the program version management server is a Git server, in step S103, the second parameter includes a hook address and/or a URL request password for opening a hook function.
5. The method for online upgrade of a distributed deployment service software program of claim 1, wherein: if the service software program upgrading package is provided with a plurality of upgrading program codes named by different application subprogram names, the steps S105 to S108 are executed one by one according to a polling mode aiming at the upgrading program codes and the target servers corresponding to the different application subprogram names.
6. The method for online upgrade of a distributed deployment service software program of claim 1, wherein: the Jenkins terminal software program and the Docker private library are respectively operated in a target server in a Docker application container mode.
7. The method for online upgrade of a distributed deployment service software program of claim 1, wherein: the target server is a physical machine or a virtual machine.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201810439466.XA CN108632375B (en) | 2018-05-09 | 2018-05-09 | Online upgrading method for distributed deployment service software program |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201810439466.XA CN108632375B (en) | 2018-05-09 | 2018-05-09 | Online upgrading method for distributed deployment service software program |
Publications (2)
Publication Number | Publication Date |
---|---|
CN108632375A CN108632375A (en) | 2018-10-09 |
CN108632375B true CN108632375B (en) | 2021-04-27 |
Family
ID=63692233
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN201810439466.XA Active CN108632375B (en) | 2018-05-09 | 2018-05-09 | Online upgrading method for distributed deployment service software program |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN108632375B (en) |
Families Citing this family (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN109542677B (en) * | 2018-11-05 | 2021-08-13 | 北京炎黄盈动科技发展有限责任公司 | Method and device for upgrading application medium in high-reliability container and storage medium |
CN109725931A (en) * | 2018-12-17 | 2019-05-07 | 中国联合网络通信集团有限公司 | A kind of jenkins construction method and device |
CN109800006A (en) * | 2018-12-28 | 2019-05-24 | 易票联支付有限公司 | A kind of dissemination method, system and storage medium customizing script |
CN110597531B (en) * | 2019-08-05 | 2022-11-08 | 平安科技(深圳)有限公司 | Distributed module upgrading method and device and storage medium |
CN110730135B (en) * | 2019-09-06 | 2022-12-09 | 平安普惠企业管理有限公司 | Method and device for improving performance of server, storage medium and server |
CN110837383B (en) * | 2019-09-30 | 2023-10-31 | 奇安信科技集团股份有限公司 | Application installation-free upgrading method and device |
US20210117859A1 (en) * | 2019-10-20 | 2021-04-22 | Nvidia Corporation | Live updating of machine learning models |
CN110990035B (en) * | 2019-11-01 | 2023-03-14 | 中国人民解放军63811部队 | Chain type software upgrading method based on Git |
CN111273926A (en) * | 2020-01-14 | 2020-06-12 | 一飞智控(天津)科技有限公司 | Airport client remote upgrade management method, system, storage medium and unmanned aerial vehicle |
CN112698855B (en) * | 2020-12-30 | 2023-03-14 | 浙江惠瀜网络科技有限公司 | Method for upgrading on-line automatic deployment server |
CN112612513A (en) * | 2020-12-31 | 2021-04-06 | 平安养老保险股份有限公司 | Message middleware upgrading method and device, computer equipment and storage medium |
CN113312152A (en) * | 2021-06-25 | 2021-08-27 | 上海华瑞银行股份有限公司 | Method and device for automatically creating private cloud release task and electronic equipment |
CN113849487B (en) * | 2021-12-02 | 2022-03-11 | 中关村科学城城市大脑股份有限公司 | Database management method, device, equipment and medium |
Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN105760167A (en) * | 2016-02-23 | 2016-07-13 | 浪潮软件集团有限公司 | Docker-based continuous integration method |
CN106598681A (en) * | 2016-12-21 | 2017-04-26 | 北京恒华伟业科技股份有限公司 | Construction method and device for development environment |
CN106873975A (en) * | 2016-12-30 | 2017-06-20 | 武汉默联股份有限公司 | Devops based on Docker persistently pays and automated system and method |
CN106991035A (en) * | 2017-04-06 | 2017-07-28 | 北京计算机技术及应用研究所 | A kind of Host Supervision System based on micro services framework |
CN107562472A (en) * | 2017-08-24 | 2018-01-09 | 四川长虹电器股份有限公司 | Micro services system and method based on docker containers |
CN107729034A (en) * | 2017-10-24 | 2018-02-23 | 郑州云海信息技术有限公司 | A kind of software continuous integrated approach and its device |
CN107797767A (en) * | 2017-09-30 | 2018-03-13 | 南京卓盛云信息科技有限公司 | One kind is based on container technique deployment distributed memory system and its storage method |
-
2018
- 2018-05-09 CN CN201810439466.XA patent/CN108632375B/en active Active
Patent Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN105760167A (en) * | 2016-02-23 | 2016-07-13 | 浪潮软件集团有限公司 | Docker-based continuous integration method |
CN106598681A (en) * | 2016-12-21 | 2017-04-26 | 北京恒华伟业科技股份有限公司 | Construction method and device for development environment |
CN106873975A (en) * | 2016-12-30 | 2017-06-20 | 武汉默联股份有限公司 | Devops based on Docker persistently pays and automated system and method |
CN106991035A (en) * | 2017-04-06 | 2017-07-28 | 北京计算机技术及应用研究所 | A kind of Host Supervision System based on micro services framework |
CN107562472A (en) * | 2017-08-24 | 2018-01-09 | 四川长虹电器股份有限公司 | Micro services system and method based on docker containers |
CN107797767A (en) * | 2017-09-30 | 2018-03-13 | 南京卓盛云信息科技有限公司 | One kind is based on container technique deployment distributed memory system and its storage method |
CN107729034A (en) * | 2017-10-24 | 2018-02-23 | 郑州云海信息技术有限公司 | A kind of software continuous integrated approach and its device |
Also Published As
Publication number | Publication date |
---|---|
CN108632375A (en) | 2018-10-09 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN108632375B (en) | Online upgrading method for distributed deployment service software program | |
CN110572436B (en) | Multi-place cross-cluster server deployment method and system | |
CN105955782B (en) | Application program operation control method and device | |
US9485134B2 (en) | Managing configurations of system management agents in a distributed environment | |
US10613853B2 (en) | Updating software components through online stores | |
CN108170448B (en) | System for automatically and efficiently releasing software update version | |
CN102523268A (en) | Client side upgrading method and system | |
CN108574702A (en) | A cloud application deployment method and system | |
CN108737463A (en) | A kind of software deployment method, server and system | |
CN112860282B (en) | Cluster plug-in upgrading method, device and server | |
CN106557347B (en) | Software updating method and device | |
CN105260209A (en) | Hot-update solution of program | |
CN112104501A (en) | Remote software upgrading method for agricultural machinery subsoiling Internet of things terminal equipment | |
CN110753088A (en) | System deployment method and device | |
CN112860251A (en) | Method and system for constructing website front end | |
CN111984440A (en) | Method, system and storage medium for Celery online management and automatic task execution | |
CN112256989A (en) | Page loading method and device based on offline package, terminal equipment and storage medium | |
CN100421072C (en) | Method for realizing software updating | |
CN114840243A (en) | Operating system upgrading system of distributed edge node | |
CN104348646A (en) | Configuration data processing method, device and system | |
CN104077168A (en) | Method and device for updating operation systems for terminal | |
CN117215818A (en) | Cloud edge collaboration-based lightweight application collaboration method for Internet of things | |
CN111679850A (en) | Application program hot update processing method, device and system | |
CN109697080B (en) | Online upgrading method for operating system of Internet of things | |
CN105282180B (en) | Method and device for processing service authentication |
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 | ||
TR01 | Transfer of patent right | ||
TR01 | Transfer of patent right |
Effective date of registration: 20220928 Address after: Unit 02-04, Floor 14, Unit 1, Building 2, No. 11, Middle Spectra Road, Lianhe Street, Huangpu District, Guangzhou, Guangdong 510000 Patentee after: Guangzhou Jianxin Technology Co.,Ltd. Address before: 610000 First Floor, 219 Tianshun Road, Chengdu High-tech Zone, Sichuan Province Patentee before: SICHUAN HUACHUANG SHIJI TECHNOLOGY Co.,Ltd. |