CN116474375A - Game application version control method, device, equipment and medium - Google Patents

Game application version control method, device, equipment and medium Download PDF

Info

Publication number
CN116474375A
CN116474375A CN202310571731.0A CN202310571731A CN116474375A CN 116474375 A CN116474375 A CN 116474375A CN 202310571731 A CN202310571731 A CN 202310571731A CN 116474375 A CN116474375 A CN 116474375A
Authority
CN
China
Prior art keywords
version
game
expected
game 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.)
Pending
Application number
CN202310571731.0A
Other languages
Chinese (zh)
Inventor
尹红光
万磊
何子豪
蒲家坤
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Shenzhen Yunwang Wulian Technology Co ltd
Original Assignee
Shenzhen Yunwang Wulian Technology Co ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Shenzhen Yunwang Wulian Technology Co ltd filed Critical Shenzhen Yunwang Wulian Technology Co ltd
Priority to CN202310571731.0A priority Critical patent/CN116474375A/en
Publication of CN116474375A publication Critical patent/CN116474375A/en
Pending legal-status Critical Current

Links

Classifications

    • A—HUMAN NECESSITIES
    • A63—SPORTS; GAMES; AMUSEMENTS
    • A63F—CARD, BOARD, OR ROULETTE GAMES; INDOOR GAMES USING SMALL MOVING PLAYING BODIES; VIDEO GAMES; GAMES NOT OTHERWISE PROVIDED FOR
    • A63F13/00—Video games, i.e. games using an electronically generated display having two or more dimensions
    • A63F13/70—Game security or game management aspects
    • A63F13/77—Game security or game management aspects involving data related to game devices or game servers, e.g. configuration data, software version or amount of memory
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/61—Installation
    • 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

Abstract

The application discloses a game application version control method, a device, equipment and a medium, comprising the following steps: sending a request to a central server so that the central server returns the game information of the expected version corresponding to the user node; comparing the expected version game information with the locally stored current version game information to judge whether the node meets the expected version game installation conditions or not; and if the node meets the installation condition of the expected version game, installing an expected version game application based on the expected version game information. Therefore, the central server is not required to send the notification at regular time, the resource waste of the central server can be avoided, and the situation that the game application of the expected version can be immediately installed after the node is online is ensured.

Description

Game application version control method, device, equipment and medium
Technical Field
The present disclosure relates to the field of game application version control technologies, and in particular, to a method, an apparatus, a device, and a medium for controlling a game application version.
Background
Currently, in the existing game application control version scheme, when a game application version expected to be installed by a node appears, a notification is usually sent to each node by a central server to notify each node to perform game application installation, but the central server does not know whether the node is online or not, so that the notification is usually sent once every a certain period of time, which causes resource waste of the central server, and the node needs to wait for the notification sent by the central server after being online again, so that the installation of the expected version cannot be performed immediately.
Disclosure of Invention
In view of the above, an object of the present application is to provide a method, apparatus, device, and medium for controlling a version of a game application, which can avoid resource waste of a central server and ensure that a game application of a desired version can be installed immediately after a node is online. The specific scheme is as follows:
in a first aspect, the present application discloses a game application version control method, applied to a user node, including:
sending a request to a central server so that the central server returns the game information of the expected version corresponding to the user node;
comparing the expected version game information with the locally stored current version game information to judge whether the node meets the expected version game installation conditions or not;
and if the node meets the installation condition of the expected version game, installing an expected version game application based on the expected version game information.
Optionally, the comparing the expected version game information with the locally stored current version game information to determine whether the node meets the expected version game installation condition includes:
comparing the expected version game information with the locally stored current version game information to obtain a game version comparison result;
and if the version comparison result is that the local game version is the old version, judging that the node meets the expected version game installation condition.
Optionally, the method further comprises:
and if the version comparison result is that the local game version and the expected version are the same version, judging that the node does not meet the game installation conditions of the expected version.
Optionally, the method further comprises:
if the version comparison result is that the local game version is an updated version, judging that the node does not meet the expected version game installation condition, or judging that the node meets the expected version game installation condition, and installing a lower version game application based on the expected version game information.
Optionally, the method further comprises:
if the version comparison result is that the local game version and the expected version are the same version, comparing the information abstract in the game information of the expected version with the information abstract in the game information of the current version;
if the information abstract in the expected version game information is inconsistent with the information abstract in the current version game information, judging that the node meets the installation condition of the expected version game.
Optionally, after the installation of the desired version game application based on the desired version game information, the method further includes:
updating the locally stored current version of the game information based on the desired version of the game information;
or reading application information of the installed game application, and updating the locally stored current version game information based on the application information.
Optionally, after the installation of the desired version game application based on the desired version game information, the method further includes:
and reporting the updated current version game information to a central server so that the central server judges whether the game application is installed or not based on the updated current version game information and the expected version game information.
Optionally, the method further comprises:
if the current version game information does not exist locally, installing the expected version game application based on the expected version game information.
Optionally, the sending the request to the central server includes:
the request is sent to the central server at regular time.
In a second aspect, the present application discloses a game application version control device, applied to a user node, comprising:
the request sending module is used for sending a request to the central server so that the central server returns the game information of the expected version corresponding to the user node;
the installation condition judging module is used for comparing the expected version game information with the locally stored current version game information so as to judge whether the node meets the installation condition of the expected version game;
and the game application installation module is used for installing the expected version game application based on the expected version game information if the installation condition judgment module judges that the node meets the expected version game installation condition.
In a third aspect, the present application discloses an electronic device comprising a memory and a processor, wherein:
the memory is used for storing a computer program;
the processor is configured to execute the computer program to implement the foregoing game application version control method.
In a fourth aspect, the present application discloses a computer readable storage medium storing a computer program, wherein the computer program when executed by a processor implements the aforementioned game application version control method.
It can be seen that, the present application sends a request to a central server, so that the central server returns the expected version game information corresponding to the user node, and then compares the expected version game information with the locally stored current version game information to determine whether the present node meets the expected version game installation condition, and if the present node meets the expected version game installation condition, the present node installs the expected version game application based on the expected version game information. In other words, in the application, the user node actively sends a request to the central server, acquires the expected version game information returned by the central server, compares the expected version game information with the locally stored current version game information to judge whether the expected version game application needs to be installed, and installs the expected version game application based on the expected version game information if the expected version game application needs to be installed, so that the central server does not need to send a notification at regular time, resource waste of the central server can be avoided, and the fact that the expected version game application can be installed immediately after the node is online is ensured.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings that are required to be used in the embodiments or the description of the prior art will be briefly described below, and it is obvious that the drawings in the following description are only embodiments of the present application, and that other drawings may be obtained according to the provided drawings without inventive effort to a person skilled in the art.
FIG. 1 is a flow chart of a method for controlling version of a game application according to an embodiment of the present application;
FIG. 2 is a schematic diagram of a particular game application version control disclosed in an embodiment of the present application;
FIG. 3 is a schematic diagram of a game application version control device according to an embodiment of the present disclosure;
fig. 4 is a block diagram of an electronic device according to an embodiment of the present application.
Detailed Description
The following description of the embodiments of the present application will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are only some, but not all, of the embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.
Currently, in the existing game application control version scheme, when a game application version expected to be installed by a node appears, a notification is usually sent to each node by a central server to notify each node to perform game application installation, but the central server does not know whether the node is online or not, so that the notification is usually sent once every a certain period of time, which causes resource waste of the central server, and the node needs to wait for the notification sent by the central server after being online again, so that the installation of the expected version cannot be performed immediately. Therefore, the game application version control scheme can avoid resource waste of the central server, and can ensure that the game application of the expected version can be installed immediately after the node is online.
Referring to fig. 1, an embodiment of the present application discloses a game application version control method, including:
step S11: and sending a request to a central server so that the central server returns the game information of the expected version corresponding to the user node.
In one implementation, embodiments of the present application may send requests to a central server at regular intervals. That is, the user node polls the central server for the desired version of game information for the node. The expected version game information is game information set by the central server, and can be directly set after the expected version game information is acquired when the game information is set for the first time, and can be compared with the expected version game information set last time after the expected version game information is acquired when the game information is not set for the first time, so as to judge whether updating is needed, and if so, the expected version game information is set. For example, if the version number is greater than the version number in the last set expected version game information, it is determined that update is required; if the version numbers are the same and the Md5 value is different from the Md5 value in the last set expected version game information, the update is judged to be needed.
Step S12: and comparing the expected version game information with the locally stored current version game information to judge whether the node meets the installation condition of the expected version game.
The embodiment of the application can compare the expected version game information with the locally stored current version game information to obtain a game version comparison result. The desired version information may include, among other things, a version number, a game name, a time at which version control was initiated, and the like. And comparing the version number in the expected version game information with the version number in the locally stored current version game information to obtain a game version comparison result.
Further, if the version comparison result is that the local game version is the old version, the node is judged to meet the expected version game installation condition. Specifically, the version number of the local game application may be lower, and the node needs to upgrade the game application.
In one embodiment, if the version comparison result indicates that the local game version and the desired version are the same, it is determined that the current node does not satisfy the desired version game installation condition. In another embodiment, the expected version game information may further include an information abstract, and if the version comparison result is that the local game version and the expected version are the same, the information abstract in the expected version game information is compared with the information abstract in the current version game information; if the information abstract in the expected version game information is inconsistent with the information abstract in the current version game information, judging that the node meets the installation condition of the expected version game. Wherein the message digest may be an Md5 value.
Further, in one embodiment, if the version comparison result is that the local game version is an updated version, it is determined that the current node does not satisfy the expected version game installation condition. That is, if the local game version is an updated version, the current game version is maintained. In another embodiment, if the version comparison result is that the local game version is an updated version, it may be determined that the current node satisfies a desired version game installation condition, and a lower version game application is installed based on the desired version game information. That is, embodiments of the present application may perform version rollback as desired.
In addition, in the embodiment of the application, if the current version game information does not exist locally, the expected version game application is installed based on the expected version game information. According to the embodiment of the application, before comparing the expected version game information with the locally stored current version game information, whether the current version game information exists locally or not can be judged, if so, the step of comparing the expected version game information with the locally stored current version game information is triggered, and if not, the expected version game application is installed based on the expected version game information. That is, when the game application is installed for the first time, the node directly installs the desired version game application based on the desired version game information, stores the desired version game information locally as current version game information, and when the game application is not installed for the first time, compares the current version game information with the newly acquired desired version game information to judge whether to install the desired version game application.
Step S13: and if the node meets the installation condition of the expected version game, installing an expected version game application based on the expected version game information.
In a specific embodiment, the installation of the desired version of the game application may be performed by downloading a corresponding installation package from a remote server based on the desired version of the game information.
Additionally, in one embodiment, the locally stored current version of the game information may be updated based on the desired version of the game information. In another embodiment, application information of the installed game application may be read, and updating the locally stored current version game information based on the application information.
Further, the updated current version game information is reported to the central server, so that the central server judges whether the game application is installed or not based on the updated current version game information and the expected version game information. The updated current version game information and the expected version game information can be compared, if the updated current version game information is consistent with the expected version game information, the installation is judged to be completed, and otherwise, the installation is judged to be not completed.
For example, referring to fig. 2, fig. 2 is a schematic diagram illustrating a specific game application version control according to an embodiment of the present application. The desired version of game information is game information for which the node expects to install a game version, including a game package name, a game version number, a game package md5 value, and a time to initiate game version control. The set granularity is that each node corresponds to one expected version of game information. The node refers to a server operated by a game, each server is identified by its own server ID, and the architecture of the server is not limited in this embodiment of the present application, for example, an X86 architecture may be used. That is, the desired version of game information is set for each node based on the server ID. When the first setting is performed, the expected version game information is directly set, when the second and later setting are performed, after the expected version game information is obtained, the expected version game information can be compared with the expected version game information set last time, whether updating is needed or not is judged, and if the updating is needed, the expected version game information is set. For example, if the version number is greater than the version number in the last set expected version game information, it is determined that update is required; if the version numbers are the same and the Md5 value is different from the Md5 value in the last set expected version game information, the update is judged to be needed. In addition, each node runs a client software, the client software polls the center server for the game information of the expected version of the node through the server ID, when the game information of the expected version is obtained, the corresponding installation package is downloaded from the remote server when the game application is installed for the first time, and the game application installation is executed. And when the game is installed for the second time and later, comparing the game information with the locally stored current version game information based on preset comparison logic, if the game is required to be installed, downloading a corresponding installation package from a remote server, executing game application installation, and updating the local current version game information. The installation success information is reported after the installation is successful no matter the first installation or the subsequent installation, and after the upgrade is successful, the center server stores the current version game information of the node, and the round of installation is completed.
The current version game information stored locally by the node also comprises a game package name, a game version number, a game package Md5 value and the like. If the game is not installed in the node, the game package on the storage server is directly downloaded according to the game package name, the game version number and the Md5 value of the game package, the game package is installed after the downloading is completed, and after the installation is successful, the game package name, the game version number and the Md5 value of the game package are recorded as current version game information to a local table. And if the two types of the game package names are equal, comparing Md5 and Md5 to be different, then downloading the game package on the storage server, installing the game package after the downloading is completed, and recording the game package name, the game version number and the Md5 value of the game package on the storage server to the local table after the downloading is completed. The desired version of game information may be polled by the client software, information comparison performed, game packages downloaded, installed, and successfully reported. In this way, the node is offline in any case, and the game installation and upgrading operation can be realized only after the node is online.
As can be seen, in the embodiment of the present application, a request is sent to a central server, so that the central server returns the expected version game information corresponding to the user node, and then the expected version game information is compared with the locally stored current version game information, so as to determine whether the node meets the expected version game installation condition, and if the node meets the expected version game installation condition, the expected version game application is installed based on the expected version game information. That is, in the embodiment of the present application, the user node actively sends a request to the central server, acquires the expected version game information returned by the central server, compares the expected version game information with the locally stored current version game information to determine whether the expected version game application needs to be installed, and if so, installs the expected version game application based on the expected version game information, so that the central server does not need to send a notification at regular time, resource waste of the central server can be avoided, and it is ensured that the expected version game application can be installed immediately after the node is online.
Referring to fig. 3, an embodiment of the present application discloses a game application version control device, which is applied to a user node, and includes:
a request sending module 11, configured to send a polling request to a central server, so that the central server returns the game information of the desired version corresponding to the user node;
the installation condition judging module 12 is configured to compare the expected version game information with the locally stored current version game information, so as to judge whether the node meets the installation condition of the expected version game;
the game application installation module 13 installs a desired version of the game application based on the desired version of the game information if the installation condition judgment module judges that the present node satisfies the desired version of the game installation condition.
As can be seen, in the embodiment of the present application, a request is sent to a central server, so that the central server returns the expected version game information corresponding to the user node, and then the expected version game information is compared with the locally stored current version game information, so as to determine whether the node meets the expected version game installation condition, and if the node meets the expected version game installation condition, the expected version game application is installed based on the expected version game information. That is, in the embodiment of the application, the user node actively sends a request to the central server, obtains the expected version game information returned by the central server, compares the expected version game information with the locally stored current version game information to determine whether the expected version game application needs to be installed, if so, installs the expected version game application based on the expected version game information,
the installation condition judging module 12 is specifically configured to compare the expected version game information with the locally stored current version game information, so as to obtain a game version comparison result; and if the version comparison result is that the local game version is the old version, judging that the node meets the expected version game installation condition.
In one embodiment, the installation condition determining module 12 is further configured to determine that the current node does not meet the installation condition of the desired version of the game if the version comparison result indicates that the local game version and the desired version are the same. In another embodiment, the installation condition determining module 12 is further configured to compare the information summary in the game information of the expected version with the information summary in the game information of the current version if the version comparison result indicates that the local game version is the same as the expected version; if the information abstract in the expected version game information is inconsistent with the information abstract in the current version game information, judging that the node meets the installation condition of the expected version game.
Further, in one embodiment, the installation condition determining module 12 is further configured to determine that the current node does not meet the installation condition of the desired version game if the version comparison result is that the local game version is an updated version. In another embodiment, the installation condition determining module 12 is further configured to determine that the node meets a desired version of game installation condition, and the corresponding game application installation module 13 is configured to install a lower version of game application based on the desired version of game information.
And, the apparatus further comprises: and the current version game information updating module.
In one embodiment, the current version game information updating module is specifically configured to update the locally stored current version game information based on the desired version game information after the desired version game application is installed based on the desired version game information.
In another embodiment, the current version game information updating module is specifically configured to, after the installation of the desired version game application based on the desired version game information, read application information of the installed game application, and update the locally stored current version game information based on the application information.
Further, the device further comprises a current version game information reporting module for reporting the updated current version game information to the central server, so that the central server judges whether the game application is installed or not based on the updated current version game information and the expected version game information.
And the device also comprises a first installation judging module for judging whether the current version game information exists locally or not, and a corresponding game application installation module 13 for installing the expected version game application based on the expected version game information if the first installation judging module judges that the current version game information does not exist locally.
In one embodiment, the request sending module 11 is specifically configured to send the request to the central server at a timing.
Referring to fig. 4, an embodiment of the present application discloses an electronic device 20 comprising a processor 21 and a memory 22; wherein the memory 22 is used for storing a computer program; the processor 21 is configured to execute the computer program and implement the game application version control method disclosed in the foregoing embodiment.
For the specific process of the above game application version control method, reference may be made to the corresponding content disclosed in the foregoing embodiment, and no further description is given here.
The memory 22 may be a carrier for storing resources, such as a read-only memory, a random access memory, a magnetic disk or an optical disk, and the storage mode may be transient storage or permanent storage.
In addition, the electronic device 20 further includes a power supply 23, a communication interface 24, an input-output interface 25, and a communication bus 26; wherein the power supply 23 is configured to provide an operating voltage for each hardware device on the electronic device 20; the communication interface 24 can create a data transmission channel between the electronic device 20 and an external device, and the communication protocol to be followed is any communication protocol applicable to the technical solution of the present application, which is not specifically limited herein; the input/output interface 25 is used for acquiring external input data or outputting external output data, and the specific interface type thereof may be selected according to the specific application requirement, which is not limited herein.
Further, the embodiment of the application also discloses a computer readable storage medium for storing a computer program, wherein the computer program realizes the game application version control method disclosed in the previous embodiment when being executed by a processor.
For the specific process of the above game application version control method, reference may be made to the corresponding content disclosed in the foregoing embodiment, and no further description is given here.
In this specification, each embodiment is described in a progressive manner, and each embodiment is mainly described in a different point from other embodiments, so that the same or similar parts between the embodiments are referred to each other. For the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant points refer to the description of the method section.
The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. The software modules may be disposed in Random Access Memory (RAM), memory, read Only Memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
The above describes in detail a method, apparatus, device and medium for controlling version of game application provided in the present application, and specific examples are applied herein to illustrate the principles and embodiments of the present application, where the above examples are only used to help understand the method and core ideas of the present application; meanwhile, as those skilled in the art will have modifications in the specific embodiments and application scope in accordance with the ideas of the present application, the present description should not be construed as limiting the present application in view of the above.

Claims (12)

1. A method of game application version control, applied to a user node, comprising:
sending a request to a central server so that the central server returns the game information of the expected version corresponding to the user node;
comparing the expected version game information with the locally stored current version game information to judge whether the node meets the expected version game installation conditions or not;
and if the node meets the installation condition of the expected version game, installing an expected version game application based on the expected version game information.
2. The game application version control method according to claim 1, wherein the comparing the desired version game information with the locally stored current version game information to determine whether the present node satisfies a desired version game installation condition comprises:
comparing the expected version game information with the locally stored current version game information to obtain a game version comparison result;
and if the version comparison result is that the local game version is the old version, judging that the node meets the expected version game installation condition.
3. The game application version control method according to claim 2, further comprising:
and if the version comparison result is that the local game version and the expected version are the same version, judging that the node does not meet the game installation conditions of the expected version.
4. The game application version control method according to claim 2, further comprising:
if the version comparison result is that the local game version is an updated version, judging that the node does not meet the expected version game installation condition, or judging that the node meets the expected version game installation condition, and installing a lower version game application based on the expected version game information.
5. The game application version control method according to claim 2, further comprising:
if the version comparison result is that the local game version and the expected version are the same version, comparing the information abstract in the game information of the expected version with the information abstract in the game information of the current version;
if the information abstract in the expected version game information is inconsistent with the information abstract in the current version game information, judging that the node meets the installation condition of the expected version game.
6. The game application version control method according to claim 1, further comprising, after the installation of the desired version game application based on the desired version game information:
updating the locally stored current version of the game information based on the desired version of the game information;
or reading application information of the installed game application, and updating the locally stored current version game information based on the application information.
7. The game application version control method according to claim 6, further comprising, after the installation of the desired version game application based on the desired version game information:
and reporting the updated current version game information to a central server so that the central server judges whether the game application is installed or not based on the updated current version game information and the expected version game information.
8. The game application version control method according to any one of claims 1 to 7, characterized by further comprising:
if the current version game information does not exist locally, installing the expected version game application based on the expected version game information.
9. The game application version control method according to claim 1, wherein the sending a request to the center server includes:
the request is sent to the central server at regular time.
10. A game application version control device, for use with a user node, comprising:
the request sending module is used for sending a request to the central server so that the central server returns the game information of the expected version corresponding to the user node;
the installation condition judging module is used for comparing the expected version game information with the locally stored current version game information so as to judge whether the node meets the installation condition of the expected version game;
and the game application installation module is used for installing the expected version game application based on the expected version game information if the installation condition judgment module judges that the node meets the expected version game installation condition.
11. An electronic device comprising a memory and a processor, wherein:
the memory is used for storing a computer program;
the processor for executing the computer program to implement the game application version control method according to any one of claims 1 to 9.
12. A computer readable storage medium for storing a computer program, wherein the computer program when executed by a processor implements the game application version control method of any one of claims 1 to 9.
CN202310571731.0A 2023-05-19 2023-05-19 Game application version control method, device, equipment and medium Pending CN116474375A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202310571731.0A CN116474375A (en) 2023-05-19 2023-05-19 Game application version control method, device, equipment and medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202310571731.0A CN116474375A (en) 2023-05-19 2023-05-19 Game application version control method, device, equipment and medium

Publications (1)

Publication Number Publication Date
CN116474375A true CN116474375A (en) 2023-07-25

Family

ID=87221501

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202310571731.0A Pending CN116474375A (en) 2023-05-19 2023-05-19 Game application version control method, device, equipment and medium

Country Status (1)

Country Link
CN (1) CN116474375A (en)

Similar Documents

Publication Publication Date Title
US8245225B2 (en) Method, system, terminal and device management server for installing software components
US7003767B2 (en) System and method for remotely updating software applications
US7360208B2 (en) Rolling upgrade of distributed software with automatic completion
US9253265B2 (en) Hot pluggable extensions for access management system
CN110730090B (en) Batch updating method, device, medium and electronic equipment for agent terminals in cloud environment
CN111273924B (en) Software updating method and device
JP2009521746A (en) Program execution service window
CN110865819B (en) OS installation method, server and system
CN110855746A (en) Middleware management method, electronic device and storage medium
CN110716734A (en) Software upgrading method and device, electronic equipment and medium
EP2104274B1 (en) Method, system, dm client and dm server for installing software component
CN112702195A (en) Gateway configuration method, electronic device and computer readable storage medium
CN112688794A (en) YANG model management method, device, system, equipment and storage medium
CN111625264B (en) Method, device, equipment and medium for upgrading multi-level management system
CN112748949A (en) Software package management method, device, equipment and storage medium of operating system
CN116474375A (en) Game application version control method, device, equipment and medium
CN111367740B (en) BMC debugging system and method and computer readable storage medium
JP4882291B2 (en) Module update program
CN111610991A (en) Version upgrading method and device
CN114936043B (en) Method, device, equipment and storage medium for starting pooled heterogeneous resources
CN117453641A (en) File uploading method, device, equipment and storage medium
CN113765971A (en) Method, device, equipment and computer readable medium for controlling interface
US20140325270A1 (en) Method and a device for managing an application referenced by a device
CN117421022A (en) Application updating method and device, electronic equipment and storage medium
CN116360885A (en) Start control method, start control device, substrate management controller, management equipment and medium

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