CN115357280A - Software version management method, device, server and storage medium - Google Patents
Software version management method, device, server and storage medium Download PDFInfo
- Publication number
- CN115357280A CN115357280A CN202210952686.9A CN202210952686A CN115357280A CN 115357280 A CN115357280 A CN 115357280A CN 202210952686 A CN202210952686 A CN 202210952686A CN 115357280 A CN115357280 A CN 115357280A
- Authority
- CN
- China
- Prior art keywords
- version
- software version
- client
- target
- software
- 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
Links
- 238000007726 management method Methods 0.000 title claims abstract description 43
- 238000000034 method Methods 0.000 claims description 24
- 238000004590 computer program Methods 0.000 claims description 16
- 238000012360 testing method Methods 0.000 claims description 16
- 238000012545 processing Methods 0.000 claims description 4
- 238000012423 maintenance Methods 0.000 abstract description 7
- 230000006870 function Effects 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 230000008569 process Effects 0.000 description 3
- 238000004891 communication Methods 0.000 description 2
- 238000013507 mapping Methods 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Images
Classifications
-
- 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
-
- 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/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters
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)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Stored Programmes (AREA)
Abstract
The embodiment of the application provides a software version management method, a software version management device, a server and a storage medium. The software version management method comprises the following steps: acquiring target identity information and software version setting information of a client, wherein the target identity information is at least one of IP address information and a preset identifier; establishing an identity version corresponding relation between target identity information and software version setting information; and managing the software version of the client based on the identity version corresponding relation. According to the embodiment of the application, the version of the client software is managed based on at least one item of the IP address information and the preset identification, so that the management and maintenance cost can be effectively reduced.
Description
Technical Field
The present application relates to the field of internet technologies, and in particular, to a software version management method, apparatus, server, and storage medium.
Background
In Software-as-a-Service (SAAS), a Software Service provider usually faces the needs of different clients for different Software versions. For example, some customers may require that the software remain constantly in the latest test or stable version, while other customers may adapt relatively to a fixed use of a historical version.
In the related art, in order to meet the requirement of the customer on the differentiated use of the software version, the software service provider generally configures a separate domain name for the customer to control the version. However, version control based on domain names often has the problem of high management and maintenance costs.
Disclosure of Invention
The embodiment of the application provides a software version management method, a software version management device, a server and a storage medium, and aims to solve the problem of high management and maintenance cost caused by domain name-based version control in the related art.
In order to solve the technical problem, the present application is implemented as follows:
in a first aspect, an embodiment of the present application provides a software version management method, including:
acquiring target identity information and software version setting information of a client, wherein the target identity information is at least one of IP address information and a preset identifier;
establishing an identity version corresponding relation between target identity information and software version setting information;
and managing the software version of the client based on the identity version corresponding relation.
In a second aspect, an embodiment of the present application further provides a software version management apparatus, including:
the system comprises an acquisition module, a storage module and a processing module, wherein the acquisition module is used for acquiring target identity information and software version setting information of a client, and the target identity information is at least one of IP address information and a preset identifier;
the establishing module is used for establishing the identity version corresponding relation between the target identity information and the software version setting information;
and the management module is used for managing the software version of the client based on the identity version corresponding relation.
In a third aspect, an embodiment of the present application further provides a server, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and the processor implements the above method when executing the computer program.
In a fourth aspect, an embodiment of the present application further provides a computer-readable storage medium, where a computer program is stored, and when the computer program is executed by a processor, the computer program implements the foregoing method.
The software version management method provided by the embodiment of the application acquires target identity information and software version setting information of a client, wherein the target identity information is at least one of IP address information and a preset identifier; establishing an identity version corresponding relation between target identity information and software version setting information; and managing the software version of the client based on the identity version corresponding relation. Compared with the mode of managing the client software version based on the domain name in the prior art, the method and the device for managing the client software version based on at least one of the IP address information and the preset identification can effectively reduce the management and maintenance cost.
Drawings
Fig. 1 is a schematic flowchart of a software version management method according to an embodiment of the present application;
FIG. 2 is a flowchart illustrating a software version management method in an exemplary application;
fig. 3 is a schematic structural diagram of a software version management apparatus according to an embodiment of the present application.
Detailed Description
To make the technical problems, technical solutions and advantages to be solved by the present application clearer, the following detailed description is made with reference to the accompanying drawings and specific embodiments. In the following description, specific details such as specific configurations and components are provided only to help the embodiments of the present application be fully understood. Accordingly, it will be apparent to those skilled in the art that various changes and modifications may be made to the embodiments described herein without departing from the scope and spirit of the present application. In addition, descriptions of well-known functions and constructions are omitted for clarity and conciseness.
Unless otherwise defined, technical or scientific terms used herein shall have the ordinary meaning as understood by one of ordinary skill in the art to which this application belongs. As used in this application, the terms "first," "second," and the like do not denote any order, quantity, or importance, but rather are used to distinguish one element from another. Also, the use of the terms "a" or "an" and the like do not denote a limitation of quantity, but rather denote the presence of at least one.
As shown in fig. 1, a software version management method provided in an embodiment of the present application includes:
102, establishing an identity version corresponding relation between target identity information and software version setting information;
and 103, managing the software version of the client based on the identity version corresponding relation.
The Software version management method provided by the embodiment of the application can be applied to a server or an electronic device, for example, can be applied to a server providing Software-as-a-Service (SAAS). In connection with some application scenarios, the server may include a gateway controller, such as an APISIX gateway or an lstio gateway, which are not illustrated here. For simplicity of description, the embodiments of the present application will be described below mainly with a server as an execution subject of the method.
In step 101, the server may obtain target identity information and software version setting information of the client.
The client may be a terminal that receives a software service, and may be an electronic device such as a mobile terminal, a personal computer, or a wearable device, which is not limited in this respect. The client can be used to install the software provided by the server.
The number of the clients can be one or more, the software released by the server can generate different versions along with the update, and the requirements of different clients on the software versions can be inconsistent.
In this embodiment, the client may specifically correspond to the target identity information, and the target identity information may be at least one of IP address information and a preset identifier.
Generally, the geographic location of the client corresponds to the IP address information. Of course, in practical applications, the client and the server may communicate through a private network, and accordingly, the client may also have corresponding IP address information in the private network. In some examples, the IP address information may include one IP address, or may also include an IP address field composed of a plurality of IP addresses.
The preset identifier may be an identifier agreed by the server and the client, for example, the preset identifier may be an enterprise number identifier (hereinafter referred to as a "corp _ id identifier") of the client, or a personal number identifier, and the preset identifier may be set as needed.
The software version setting information may then be used to indicate the usage requirements of the client for the software version. In combination with some examples, some clients may need to keep the software version as the latest version, other clients may need to fix the software version as the preset version, and the software version setting information may indicate these requirements.
In some examples, the client may send its own target identity information and software version setting information to the server to enable the server to obtain the information. In other examples, the target identity information and the software version setting information of the client may also be obtained by the server in response to an information entry operation of an associated administrator.
In step 102, the server may establish an identity version correspondence between the target identity information and the software version setting information.
For example, the server obtains target identity information of three groups of clients, where the target identity information of two groups of clients is IP address information and is respectively recorded as IP1 and IP2, and the target identity information of the other group of clients is a preset identifier and is recorded as corp _ id1. The software version setting information of the IP1 client is a v1.0 version, namely, an IP1 user needs to fix the version of the software installed on the user as the v1.0 version; the software version setting information of the IP2 client is a v2.0 version, namely, an IP2 user needs to fix the version of the software installed on the user as the v2.0 version; the software version setting information of the corrp _ id1 client is the latest version, that is, the corrp _ id1 client needs to be updated when an updatable software version exists, and the software version is further kept as the latest version.
The identity version corresponding relationship may be a corresponding relationship between the target identity information and the software version setting information, and in combination with the above example, the IP1 and the v1.0 version have a corresponding relationship, the IP2 and the v2.0 version have a corresponding relationship, and the corp _ id1 and the latest version have a corresponding relationship.
In practical applications, the server may store the identity version correspondence, for example, in a table form or other formats.
In step 103, the server may manage the software version of the client based on the identity version correspondence.
Continuing with the above example, when the server receives the uploaded latest software version v3.0 base version, based on the identity version correspondence, it may be determined that software version upgrade is not required for the IP1 client and the IP2 client, and a v3.0 base version software upgrade packet may be sent to the corp _ id1 client, so that the corp _ id1 client can upgrade the software to the latest version.
The software version management method provided by the embodiment of the application acquires target identity information and software version setting information of a client, wherein the target identity information is at least one of IP address information and a preset identifier; establishing an identity version corresponding relation between target identity information and software version setting information; and managing the software version of the client based on the identity version corresponding relation. Compared with the mode of managing the client software version based on the domain name in the prior art, the method and the device for managing the client software version based on at least one of the IP address information and the preset identification can effectively reduce the management and maintenance cost.
In some application scenarios, the identity version corresponding relationship in the embodiment of the present application may set a modification permission, and the requirement that a client temporarily wants to use other versions of software may be met by modifying the identity version corresponding relationship. Compared with the prior art, the method and the device have the advantages that management or operation and maintenance personnel do not need to manually adjust the domain name to be bound to other codes, so that the error rate can be effectively reduced, and the software version management efficiency is improved.
In addition, generally, encrypted transmission such as Secure Socket Layer (SSL) is used between the server and the client, and the management of the client based on the domain name in the prior art results in that the cost of the SSL certificate increases as the number of domain names of the client increases. The software version management method provided by the embodiment of the application can effectively reduce the cost of the SSL certificate.
Optionally, the IP address information includes an IP address field to which the client belongs;
correspondingly, in step 102, establishing an identity version corresponding relationship between the target identity information and the software version setting information includes:
and establishing an identity version corresponding relation between the IP address field and the software version setting information.
In connection with some application scenarios, such as a school, a business, or other organization, there may be multiple clients at the same time, and the IP addresses of the clients may be located in the corresponding IP address fields. Alternatively, as exemplified above, the geographic location of the client may be attributed to the corresponding IP address segment.
In this embodiment, the IP address information may include an IP address field to which the client belongs, and when the resume identity version correspondence is made, the IP address field and the software version setting information may be corresponded. Therefore, the software versions of the clients belonging to the IP address field can be managed in a unified mode, and management efficiency is improved.
In some embodiment modes, the target identity information may include IP address information and a preset identifier, and the established identity version correspondence may include a correspondence between software version setting information and the preset identifier and IP address information. When the server manages the software version, the server can determine the special software version setting information corresponding to the IP address information on the basis of determining the conventional software version setting information corresponding to the preset identification according to the identity version corresponding relation.
For example, the identity version correspondence relationship includes a correspondence relationship between software version setting information-corp _ id-IP addresses. Multiple clients with different IP addresses under the same corr _ id, and conventional software version setting information corresponding to the corr _ id may indicate that the software is configured to be v2.0 version. However, among the multiple clients in the corp _ id, several of the clients need to configure the software into the v1.0 version which is relatively familiar to the user, and at this time, the IP addresses of the several clients may be included in the identity version correspondence relationship, so that the server performs special management on the software versions of the several clients subsequently when performing software version management.
Therefore, in the embodiment, the server can conveniently manage the software versions of the plurality of clients through the preset identification, and can meet the special requirements of part of the clients on the software versions according to the IP address information.
Optionally, in step 103, managing the software version of the client based on the identity version correspondence relationship includes:
under the condition of acquiring the version of the software to be released, determining a first target client based on the corresponding relation between the version of the software to be released and the identity version, wherein the software version setting information of the first target client indicates that the first target client can be configured as the version of the software to be released;
and sending the version of the software to be released to the first target client according to the target identity information of the first target client.
In connection with some application scenarios, the software version to be released may be the latest version of the software. From the perspective of the server, the server may receive the software version to be released uploaded by other terminals, or may copy the software version to be released from, for example, a mobile storage medium in response to an operation of an associated administrator.
Under the condition of acquiring the to-be-released software version, the server can determine the first target client by combining the identity version corresponding relation.
The software version setting information of the first target client indicates that the first target client can be configured as the software version to be released. In general, the first target client may be considered a client having a need to upgrade software to a software version to be released. The requirement of the client for upgrading the software version can be embodied in the software version setting information of the client.
The client, the target identity information and the software version setting information can be in corresponding relation, and under the condition that the first target client is determined, the server can send the software version to be released to the first target client according to the target identity information of the first target client, so that the software version of the client can be conveniently managed.
With reference to some specific embodiments, the server may directly send the to-be-released software version to the first target client when the to-be-released software version is obtained. In other embodiments, the server may send a prompt message indicating that the software is upgradable to the first target client, and send the version of the software to be released to the first target client after receiving the instruction for agreeing to upgrade sent by the first target client.
Optionally, sending the to-be-released software version to the first target client includes:
under the condition that the software version to be released is the test version, sending the software version to be released to part of the first target clients;
and under the condition that the software version to be released is a stable version, sending the software version to be released to all the first target clients.
In general, the software version can be divided into a test version and a formal version, and the stable version can correspond to the formal version.
For simplicity of illustration, the version with the ate field in the examples below may be considered a test version, while the version without the ate field may be considered a stable version. Of course, in practical applications, the test version may be not only the regular base version, but also the alpha version, etc., which are not illustrated here
In combination with some examples, when the version of the software to be released is the v2.0 version, that is, the stable version, the server may send the version of the software to be released to all the first target clients. Here, the manner of sending the v2.0 version by the server may be directly sending the v2.0 version, or sending a prompt message that is upgradable to the v2.0 version to all the first target clients, and sending the v2.0 version to the first target clients and the like when receiving an instruction for agreeing to upgrade sent by the first target clients, which is not specifically limited herein.
In other examples, when the to-be-released software version is a v3.0-base version, i.e., a test version, the server may send the v3.0-base version to a part of the first target clients for gray scale testing.
The server may select a random selection or a directional selection when selecting the first target client for performing the gray scale test. The selection may be based on the IP address of the client, or the IP address field to which the client belongs, or a preset identifier, and the like, which is not limited herein.
In some application cases, a server issues an alpha version configuration small part area to distribute to the version, a base version code is established in the same way after testing, and the strategy is adjusted to distribute the alpha small part area to a rear-end base version until a formal stable version is achieved, so that the problems of gray level testing and public testing of software are effectively solved.
Optionally, managing the software version of the client based on the identity version correspondence includes:
under the condition that the software version to be released is received, determining a second target client based on the corresponding relation between the software version to be released and the identity version, wherein the software version setting information of the second target client indicates that the second target client cannot be configured into the software version to be released;
and sending a prompt message to the second target client, wherein the prompt message is used for prompting the existence of the software version to be released.
In connection with the above example, some users may be more appropriate to use a certain version of software, and need to keep the version of software in the client at that version all the time without updating to the latest version of software. These clients, here, may correspond to the second target client.
The second target client is opposite to the first target client, namely the second target client does not need to be upgraded to the software version to be released. The second target client does not upgrade to the setting of the software version to be released, and can also reflect the software version setting information, which is not described herein again.
In this embodiment, the server may send a prompt message to the second target client, where the prompt message is used to prompt that the software version to be released exists.
As shown above, the server may obtain the target identity information of the client, so as to send the prompt message to the second target client according to the target identity information.
From the perspective of the second target client, the prompting mode of the prompt message may be various, for example, when the software is started and the prompt message corresponding to the software version to be released is received for the first time, the prompt is performed in a pop-up mode; alternatively, it may also be that, when the software is started, a prompt message or the like is displayed in a bubble manner, which is not illustrated here.
Of course, it is worth mentioning that the client that needs to keep the software version as a specific version may be an example of the second target client, and the second target client may also be other types of clients.
For example, in some embodiments, based on the identity version correspondence, the software version setting information of some clients may indicate that only the stable version is upgraded, and when the software version to be released is the test version, these clients may also be determined as the second target clients.
In this embodiment, the server determines the second target client and sends the prompt message to the second target client, so that the requirement of the second target client for maintaining the software version can be met, the second target client can be prompted for the upgradable version, and the software use experience of the user is effectively improved.
Optionally, in step 101, the obtaining target identity information and software version setting information of the client includes:
and receiving configuration information sent by the client, wherein the configuration information comprises target identity information and software version setting information of the client.
In this embodiment, the client may embody a requirement for upgrading or maintaining the software version by sending the configuration information to the server.
The configuration information may include target identity information and software version setting information of the client, for example, the configuration information sent by the client to the server may carry its own IP address information or corp _ id, etc.
The server receives the configuration information, and can acquire the target identity information and the software version setting information of the client. Accordingly, the server may further establish an identity version correspondence between the target identity information and the software version setting information.
Of course, when the server establishes the identity version corresponding relationship corresponding to a certain client, if the server receives the configuration information sent by the client again, the server may update the identity version corresponding relationship.
Based on the application of the embodiment, the client can realize the upgrade setting of the subsequent software version in the server by sending the configuration information, the setting mode is efficient and flexible, and different client requirements can be met at any time.
Optionally, the obtaining target identity information and software version setting information of the client further includes:
and under the condition that the configuration information sent by the client is not received, determining the software version setting information as default setting information, wherein the default setting information indicates that the client is configured to be the latest software version.
In practical applications, some clients may not have a fixed requirement for software version upgrade or maintenance, and accordingly, the clients may not send the above configuration information to the server.
In this embodiment, the server may perform default setting for the clients that do not send the configuration information, that is, determine the software version setting information of the clients as default setting information, where the default setting information indicates that the clients are configured to the latest software version. In this manner, the server can provide these clients with the latest software versions, constantly optimizing the services to the clients.
In some application scenarios, although the server does not obtain the target identity information of the client by receiving the configuration information, the server may obtain and store the target identity information of the client at other stages when the client performs software registration. When the software version setting information is determined as default setting information, the server may implement establishment of the identity version correspondence relationship in combination with the stored target identity information.
The software version management method provided by the embodiment of the present application is described below with reference to a specific application example.
In the application example, the server can establish an IP address library and an APISIX micro-service official network, accurately position a user area, determine a corresponding IP address field, and set a corp _ id identifier for enterprise users. The server can be provided with a visual web setting interface, different version codes distributed to the server can be accurately set for different areas based on the setting interface, and different software versions can be accurately set according to enterprises.
As shown in fig. 2, fig. 2 is a flowchart of an implementation process of this specific application case. With reference to fig. 2, the specific steps of the server performing multi-version management may be as follows.
1. Different versions are configured according to regions.
1. Configuring versions corresponding to an APISIX gateway and a server;
2. mapping the zone tables for different pairs of IP segments;
3. configuring all client distribution strategies by default, and distributing all clients to the latest stable version by default;
4. different software versions of the mapping are configured according to the requirements of customers or enterprises.
2. Different versions are configured according to the corr _ id.
1. When a new enterprise opens the system, the system allocates a unique cord _ id to a client, and the cord _ id of the enterprise is taken by the client of the enterprise each time the client of the enterprise uses the system to access the server;
2. configuring different versions of the corresponding period of the distribution strategy by using the corp _ id according to the client requirement;
3. or different versions can be accurately configured for employees in different areas under each enterprise flag by combining the enterprise corp _ id and the area IP.
Based on the specific application examples, the method and the system can be combined with the requirements that the region and the unique enterprise chirp _ id can accurately manage different enterprises and different versions of clients in colleges and universities. The configuration strategy is simple, and only regional or enterprise configuration is needed to be installed generally. The different versions are accurate in use range, and different versions can be configured according to regions or enterprises. The efficiency is high, the flexibility is strong, different customer demands can be met at any time, different versions are timely responded to the customer needs to be upgraded, and multiple versions coexist. In addition, the method can also solve the problems of customer gray scale and public testing, a small part of area configured by an alpha version is published on line and distributed to the version, a base version code is established in the same way after testing, and the small part of area configured by the alpha version is distributed to a rear-end base version until a formal stable version is obtained by adjusting a strategy.
As shown in fig. 3, an embodiment of the present application further provides a software version management apparatus, including:
an obtaining module 301, configured to obtain target identity information and software version setting information of a client, where the target identity information is at least one of IP address information and a preset identifier;
an establishing module 302, configured to establish an identity version correspondence between the target identity information and the software version setting information;
and the management module 303 is configured to manage the software version of the client based on the identity version correspondence.
Optionally, the IP address information includes an IP address field to which the client belongs;
accordingly, the establishing module 302 may be specifically configured to:
and establishing an identity version corresponding relation between the IP address field and the software version setting information.
Optionally, the management module 303 may include:
the first determining unit is used for determining a first target client based on the corresponding relation between the software version to be released and the identity version under the condition of acquiring the software version to be released, and the software version setting information of the first target client indicates that the first target client can be configured as the software version to be released;
and the first sending unit is used for sending the software version to be released to the first target client according to the target identity information of the first target client.
Optionally, the first sending unit may include:
the first sending subunit is used for sending the software version to be released to a part of the first target clients under the condition that the software version to be released is the test version;
and the second sending subunit is used for sending the software version to be released to all the first target clients under the condition that the software version to be released is a stable version.
Optionally, the management module 303 may include:
the second determining unit is used for determining a second target client based on the corresponding relation between the software version to be released and the identity version under the condition that the software version to be released is received, wherein the software version setting information of the second target client indicates that the second target client cannot be configured as the software version to be released;
and the second sending unit is used for sending a prompt message to the second target client, wherein the prompt message is used for prompting that the software version to be released exists.
Optionally, the obtaining module 301 may include:
and the receiving unit is used for receiving the configuration information sent by the client, and the configuration information comprises target identity information and software version setting information of the client.
Optionally, the obtaining module 301 may further include:
the determining module is used for determining the software version setting information as default setting information under the condition that the configuration information sent by the client is not received, wherein the default setting information indicates that the client is configured to be the latest software version.
It should be noted that the software version management apparatus is an apparatus corresponding to the software version management method, and all implementation manners in the method embodiments are applicable to the embodiment of the apparatus, and the same technical effect can be achieved.
Optionally, an embodiment of the present application further provides a server, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and when the processor executes the computer program, the software version management method described above is implemented.
Optionally, an embodiment of the present application further provides a computer-readable storage medium, where a computer program is stored, and when the computer program is executed by a processor, the software version management method is implemented.
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-mentioned division of the functional units and modules is illustrated, and in practical applications, the above-mentioned function distribution may be performed by different functional units and modules according to needs, that is, the internal structure of the apparatus is divided into different functional units or modules, so as to perform all or part of the functions described above. Each functional unit and module in the embodiments may be integrated in one processing unit, or each unit may exist alone physically, or two or more units are integrated in one unit, and the integrated unit may be implemented in a form of hardware, or in a form of software functional unit. In addition, specific names of the functional units and modules are only used for distinguishing one functional unit from another, and are not used for limiting the protection scope of the present application. The specific working processes of the units and modules in the system may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the above embodiments, the description of each embodiment has its own emphasis, and reference may be made to the related description of other embodiments for parts that are not described or recited in any embodiment.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus/terminal device and method may be implemented in other ways. For example, the above-described embodiments of the apparatus/terminal device are merely illustrative, and for example, a module or a unit may be divided into only one logical function, and may be implemented in other ways, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
Units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit may be implemented in the form of hardware, or may also be implemented in the form of a software functional unit.
The integrated modules/units, if implemented in the form of software functional units and sold or used as separate products, may be stored in a computer readable storage medium. Based on such understanding, all or part of the flow in the method according to the embodiments described above may be implemented by a computer program, which is stored in a computer readable storage medium and used by a processor to implement the steps of the embodiments of the methods described above. . Wherein the computer program comprises computer program code, which may be in the form of source code, object code, an executable file or some intermediate form, etc. The computer readable medium may include: any entity or device capable of carrying computer program code, recording medium, U.S. disk, removable hard disk, magnetic diskette, optical disk, computer Memory, read-Only Memory (ROM), random Access Memory (RAM), electrical carrier wave signal, telecommunications signal, software distribution medium, etc.
The above embodiments are only used to illustrate the technical solutions of the present application, and not to limit the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not depart from the spirit and scope of the embodiments of the present application, and they should be construed as being included in the present application.
Claims (10)
1. A software version management method, comprising:
acquiring target identity information and software version setting information of a client, wherein the target identity information is at least one of IP address information and a preset identifier;
establishing an identity version corresponding relation between the target identity information and the software version setting information;
and managing the software version of the client based on the identity version corresponding relation.
2. The method of claim 1, wherein the IP address information comprises an IP address field to which the client belongs;
the establishing of the identity version corresponding relationship between the target identity information and the software version setting information includes:
and establishing the identity version corresponding relation between the IP address field and the software version setting information.
3. The method of claim 1, wherein managing the software version of the client based on the identity version correspondence comprises:
under the condition of acquiring a software version to be released, determining a first target client based on the corresponding relation between the software version to be released and the identity version, wherein software version setting information of the first target client indicates that the first target client can be configured as the software version to be released;
and sending the software version to be released to the first target client according to the target identity information of the first target client.
4. The method of claim 3, wherein sending the to-be-released software version to the first target client comprises:
sending the software version to be released to a part of the first target clients under the condition that the software version to be released is a test version;
and sending the software version to be released to all the first target clients under the condition that the software version to be released is a stable version.
5. The method of claim 1, wherein managing the software version of the client based on the identity version correspondence comprises:
under the condition that a software version to be released is received, determining a second target client based on the corresponding relation between the software version to be released and the identity version, wherein the software version setting information of the second target client indicates that the second target client cannot be configured as the software version to be released;
and sending a prompt message to the second target client, wherein the prompt message is used for prompting that the software version to be released exists.
6. The method of claim 1, wherein the obtaining target identity information and software version setting information of the client comprises:
and receiving configuration information sent by the client, wherein the configuration information comprises target identity information of the client and the software version setting information.
7. The method of claim 6, wherein the obtaining target identity information and software version setting information of the client further comprises:
and under the condition that the configuration information sent by the client is not received, determining the software version setting information as default setting information, wherein the default setting information indicates that the client is configured to be the latest software version.
8. A software version management apparatus, comprising:
the system comprises an acquisition module, a storage module and a processing module, wherein the acquisition module is used for acquiring target identity information and software version setting information of a client, and the target identity information is at least one of IP address information and a preset identifier;
the establishing module is used for establishing the identity version corresponding relation between the target identity information and the software version setting information;
and the management module is used for managing the software version of the client based on the identity version corresponding relation.
9. A server comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that the processor implements the method according to any of claims 1 to 7 when executing the computer program.
10. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210952686.9A CN115357280A (en) | 2022-08-09 | 2022-08-09 | Software version management method, device, server and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210952686.9A CN115357280A (en) | 2022-08-09 | 2022-08-09 | Software version management method, device, server and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115357280A true CN115357280A (en) | 2022-11-18 |
Family
ID=84001618
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210952686.9A Pending CN115357280A (en) | 2022-08-09 | 2022-08-09 | Software version management method, device, server and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115357280A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117407049A (en) * | 2023-12-15 | 2024-01-16 | 广州嘉为科技有限公司 | Application release arrangement method, device, equipment and storage medium |
Citations (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040064812A1 (en) * | 2002-09-30 | 2004-04-01 | Toshiba Tec Kabushiki Kaisha | System and method for updating software versions |
| CN101179425A (en) * | 2006-12-11 | 2008-05-14 | 腾讯科技（深圳）有限公司 | Client terminal software updating control method and system |
| CN101699399A (en) * | 2009-11-03 | 2010-04-28 | 中兴通讯股份有限公司 | Software update system and method |
| US20140157249A1 (en) * | 2011-05-27 | 2014-06-05 | Liberty Global Europe Holding B.V. | Method and system for updating software in a media content delivery system |
| US20140317174A1 (en) * | 2013-04-22 | 2014-10-23 | Alibaba Group Holding Limited | Method and device for updating client |
| CN104579768A (en) * | 2014-12-29 | 2015-04-29 | 广州酷狗计算机科技有限公司 | Client upgrading method and device |
| US20150128122A1 (en) * | 2013-07-05 | 2015-05-07 | Tencent Technology (Shenzhen) Company Limited | Systems and Methods for Updating Software |
| CN105224373A (en) * | 2015-11-03 | 2016-01-06 | 中体彩科技发展有限公司 | The method and system of different editions application program parallel running |
| WO2017016210A1 (en) * | 2015-07-27 | 2017-02-02 | 中兴通讯股份有限公司 | Software version management method and apparatus |
| CN107360010A (en) * | 2016-05-09 | 2017-11-17 | 阿里巴巴集团控股有限公司 | A kind of website gray scale dissemination method and device |
| CN108632374A (en) * | 2018-05-09 | 2018-10-09 | 星络科技有限公司 | Software gray scale dissemination method and device |
| CN109725928A (en) * | 2018-06-15 | 2019-05-07 | 平安普惠企业管理有限公司 | Gray scale dissemination method, device, equipment and readable storage medium storing program for executing |
| CN111277633A (en) * | 2020-01-13 | 2020-06-12 | 北京奇艺世纪科技有限公司 | Request processing method, server, electronic equipment and storage medium |
| CN112667262A (en) * | 2020-12-31 | 2021-04-16 | 努比亚技术有限公司 | FOTA upgrading method, terminal and storage medium |
| CN114090047A (en) * | 2021-11-27 | 2022-02-25 | 深圳市元征科技股份有限公司 | Software upgrading method and device |
| CN114625410A (en) * | 2022-03-11 | 2022-06-14 | 蚂蚁区块链科技(上海)有限公司 | Request message processing method, device and equipment |
-
2022
- 2022-08-09 CN CN202210952686.9A patent/CN115357280A/en active Pending
Patent Citations (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040064812A1 (en) * | 2002-09-30 | 2004-04-01 | Toshiba Tec Kabushiki Kaisha | System and method for updating software versions |
| CN101179425A (en) * | 2006-12-11 | 2008-05-14 | 腾讯科技（深圳）有限公司 | Client terminal software updating control method and system |
| CN101699399A (en) * | 2009-11-03 | 2010-04-28 | 中兴通讯股份有限公司 | Software update system and method |
| US20140157249A1 (en) * | 2011-05-27 | 2014-06-05 | Liberty Global Europe Holding B.V. | Method and system for updating software in a media content delivery system |
| US20140317174A1 (en) * | 2013-04-22 | 2014-10-23 | Alibaba Group Holding Limited | Method and device for updating client |
| US20150128122A1 (en) * | 2013-07-05 | 2015-05-07 | Tencent Technology (Shenzhen) Company Limited | Systems and Methods for Updating Software |
| CN104579768A (en) * | 2014-12-29 | 2015-04-29 | 广州酷狗计算机科技有限公司 | Client upgrading method and device |
| WO2017016210A1 (en) * | 2015-07-27 | 2017-02-02 | 中兴通讯股份有限公司 | Software version management method and apparatus |
| CN105224373A (en) * | 2015-11-03 | 2016-01-06 | 中体彩科技发展有限公司 | The method and system of different editions application program parallel running |
| CN107360010A (en) * | 2016-05-09 | 2017-11-17 | 阿里巴巴集团控股有限公司 | A kind of website gray scale dissemination method and device |
| CN108632374A (en) * | 2018-05-09 | 2018-10-09 | 星络科技有限公司 | Software gray scale dissemination method and device |
| CN109725928A (en) * | 2018-06-15 | 2019-05-07 | 平安普惠企业管理有限公司 | Gray scale dissemination method, device, equipment and readable storage medium storing program for executing |
| CN111277633A (en) * | 2020-01-13 | 2020-06-12 | 北京奇艺世纪科技有限公司 | Request processing method, server, electronic equipment and storage medium |
| CN112667262A (en) * | 2020-12-31 | 2021-04-16 | 努比亚技术有限公司 | FOTA upgrading method, terminal and storage medium |
| CN114090047A (en) * | 2021-11-27 | 2022-02-25 | 深圳市元征科技股份有限公司 | Software upgrading method and device |
| CN114625410A (en) * | 2022-03-11 | 2022-06-14 | 蚂蚁区块链科技(上海)有限公司 | Request message processing method, device and equipment |
Non-Patent Citations (1)
| Title |
|---|
| 邓仲华等: "信息系统分析与设计", 武汉大学出版社, pages: 342 - 344 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117407049A (en) * | 2023-12-15 | 2024-01-16 | 广州嘉为科技有限公司 | Application release arrangement method, device, equipment and storage medium |
| CN117407049B (en) * | 2023-12-15 | 2024-03-26 | 广州嘉为科技有限公司 | Application release arrangement method, device, equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20040064480A1 (en) | System and method for utilizing profile information | |
| JP4916432B2 (en) | Application programming interface for managing the distribution of software updates in an update distribution system | |
| US8458658B2 (en) | Methods and systems for dynamically building a software appliance | |
| US8935687B2 (en) | Incrementally updating a software appliance | |
| US8019725B1 (en) | Software update management | |
| CN114025004A (en) | Method, device and equipment for processing cloud service in cloud system | |
| US20070244930A1 (en) | System and method for utilizing profile information | |
| CN109889621A (en) | The configuration method and device of virtual private cloud service | |
| CN101217368A (en) | A network logging on system and the corresponding configuration method and methods for logging on the application system | |
| JP2009534882A (en) | Device management system for remotely accessing a terminal device | |
| US10848533B2 (en) | Remotely configurable wireless broadcast device | |
| EP2681942A2 (en) | System and method to provide remote device management for mobile virtualized platforms | |
| CN102196009A (en) | Method for logging on network, server and client | |
| CN109246201B (en) | Cloud resource delivery method, processor and storage medium | |
| CN101360127A (en) | File updating method and transmission system | |
| US10897468B1 (en) | Region management for distirbuted services in provider networks | |
| US9690676B2 (en) | Assigning network device subnets to perform network activities using network device information | |
| CN115357280A (en) | Software version management method, device, server and storage medium | |
| CN105528205A (en) | Update control method and update control system | |
| CN115562757B (en) | Data processing method, configuration center system, electronic device and storage medium | |
| JP2004005437A (en) | Setting management system for network connection | |
| CN102611762B (en) | uniform domain name service system and method | |
| CN112035396B (en) | Processor-implemented method, system, and storage medium for provisioning a set of solutions | |
| CN116562888A (en) | Advisor information distribution method, advisor information distribution device, electronic device and readable storage medium | |
| CN105117278B (en) | A kind of application management method and application management platform |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20221118 |
|
| RJ01 | Rejection of invention patent application after publication |