WO2012062063A1

WO2012062063A1 - Method and apparatus for generating and uninstalling software installation package

Info

Publication number: WO2012062063A1
Application number: PCT/CN2011/071141
Authority: WO
Inventors: 王宁; 杜龙姣; 刘帅; 段方红
Original assignee: 中兴通讯股份有限公司
Priority date: 2010-11-12
Filing date: 2011-02-21
Publication date: 2012-05-18
Also published as: CN101984410B; CN101984410A

Abstract

The present invention discloses a method and an apparatus for generating and uninstalling a software installation package. The method for generating the software installation package includes: obtaining the version information of service software, files to be packaged and information about the files to be packaged; generating a configuration file according to the version information of the service software and the files to be packaged, and recording the information corresponding to the configuration file (S102); creating a software installation package and writing an installation unit of the service software into the header of the software installation package (SI 04); writing the information corresponding to the configuration file, the configuration file, the information about the files to be packaged, the files to be packaged and tail structure information in sequence behind the installation unit of the software installation package, and generating the software installation package for the service software (SI 06). With the technical solutions of the present invention, the entire installation process can be automatically treated by the installation unit, and normal usages of all the installed service software can be ensured. The match between platform software and service software can be satisfied, and compatibility of all the installed service software and flexibility of switching between each version of the service software can be ensured.

Description

TECHNICAL FIELD The present invention relates to the field of communications, and in particular to a method and apparatus for generating and uninstalling a software installation package. BACKGROUND With the rapid development of the mobile communication industry, the standards and platforms of mobile phones are increasing, and the corresponding businesses are also increasing. Therefore, there are more and more related tests to be carried out on mobile phone production lines, and corresponding mobile phone production test softwares are also numerous. The same business software of each system and platform generally has some commonalities, and different services of the same standard platform have similarities for the operation of mobile phones, in order to facilitate the uniformity of software operation style and the convenience of development and maintenance of software teams. As well as the expansion of new features, more and more enterprises are beginning to use plug-in software architecture, the entire system is divided into a number of functionally independent small modules, each module is independently developed and maintained. For the production line software, based on the development method of the plug-in class, when the software version is released, the startup program and the public plug-in are generally released as separate versions of the platform software, and the business software plug-ins are separately released. The platform software version can be packaged with some mainstream packaging tools, but for business software, traditional packaging tools cannot meet the requirements. First, the business software needs to be installed in the installation directory where the platform software is located. Secondly, different business softwares have certain requirements on the version of the platform software. For a certain service software, the platform version may be too low to support its related functions, resulting in software. Cannot run normally; Again, you need to support the business software version to upgrade to the high version, and sometimes the high version needs to fall back to the lower version due to instability; finally, different business software may contain the same file, but the file version Not necessarily the same, it is necessary to ensure the compatibility of different business software installed, and the business software can be uninstalled without affecting the normal use of other business software. The traditional packaging method is to collect all the files that need to be packaged and then merge them, and then release all the files directly to the user-specified installation directory when the user installs. In this way, the business software packaged by the user needs to judge the platform software directory by itself, and then set the business software installation directory, which increases the complexity of the operation and is prone to errors. Once the installation directory is set incorrectly, the main program will be caused. The plugin could not be found, and the plugin could not be loaded properly. In addition, when the traditional package software is installed, all the files corresponding to the post-installation version directly overwrite the files of the first-installed version, and the compatibility of the plug-in business software cannot be guaranteed. And the business software packaged by the traditional packaging method will be uninstalled. Delete all the files included in the business software. This may result in the deletion of files of the same name in other business software in the same directory, which may affect the use of other business software. SUMMARY OF THE INVENTION A primary object of the present invention is to provide a method and apparatus for generating and uninstalling a software installation package to solve at least one of the above problems. According to an aspect of the present invention, a method for generating a software installation package is provided, including: obtaining version information of a service software, a file to be packaged, and file information to be packaged, a version information of the service software, and a configuration file to be packaged. Record the information corresponding to the configuration file; create a software installation package, write the installation unit of the business software at the head of the software installation package; write the information corresponding to the configuration file, the configuration file, and the package to be packaged after the installation unit of the software installation package File information, files to be packaged, tail structure information, software installation packages for generating business software. Preferably, the version information of the service software includes at least one of the following information corresponding to the service software: a mobile phone system, a platform, a service type, a service software version number, and a platform version number; the file information to be packaged includes at least one of the following: a current file path, The file name, the file size, the installed platform main program path, and the file version number; the configuration file information includes at least one of the following: a configuration file size, a configuration file name, and a path where the configuration file is located; the tail structure information includes at least one of the following : The file size of the installation unit, the total number of files to be packed, and the constant information of the positioning tail structure. Preferably, the method further comprises: executing the software installation package of the business software according to the following steps: reading the installation information of the local platform software from the registry; reading the information corresponding to the configuration file and the configuration file from the software installation package of the business software Determine whether the currently installed business software can run on the local platform software. If not, it prompts the user that the local platform software version is too low, and needs to install a higher version of the platform software to exit the installation; if the currently installed business software can be localized If the platform software is running, it continues to determine whether a higher version of the currently installed service software has been installed locally. If yes, it prompts whether it is necessary to install a lower version of the business software than the current version. If necessary, the business software to be installed this time. And the service software conflicting with the service software is recorded in the service software uninstall configuration file, if not, exit the installation; if there is no higher version of the business software than the currently installed business software, continue to judge the local installation directory Whether there is this business The piece contains a later version of the file, and if not, The service software is installed and the information corresponding to the service software is written into the service software installation configuration file. If a higher version file of the file included in the service software exists in the local installation directory, it is prompted whether to uninstall all the files containing the high version. The business software, if yes, writes the business software installed and the business software that conflicts with the business software into the business software uninstallation configuration file, and if not, installs the business software and the information corresponding to the business software Write to the business software installation configuration file. Preferably, after reading the installation information of the platform software from the registry, before reading the configuration file information and the configuration file, the method further includes: reading the tail structure information of the currently running service software; determining whether the tail structure information is complete Correct, if no, the prompt file format is incorrect, the installation is finished, and if so, the step of reading the configuration file information and the configuration file is determined. Preferably, after the configuration file information and the configuration file are read, before determining whether the currently installed service software can be run on the local platform software, the method further includes: naming the version information of the read service software according to the predetermined service software. The rule generates the service software name and compares it with the name of the service software currently being installed. If it is inconsistent, it prompts that the currently used service software version information is incorrect and exits the installation; if it is consistent, reads the currently installed business software information and displays Give the user to confirm whether to install, if not, exit the installation; if it is installed, judge whether the local platform software is running, if yes, prompt to close the platform software, then loop to determine whether the platform software is running, if the platform software is not After running, it is determined to perform the step of judging whether the currently installed business software can run on the local platform software. According to another aspect of the present invention, a software uninstallation method is provided, including: loading a service software installation configuration file, reading current installed service software information from a service software installation configuration file; and determining the current service software uninstallation configuration file according to the service software Whether the secondary uninstallation is to install new business software, if not, all the currently installed business software is displayed, so that the user selects the business software to be uninstalled from all the business software, and responds to the operation of the user to select the business software to be uninstalled. The selected service software is uninstalled one by one. If the user selects cancel, the uninstallation is exited. If the uninstallation configuration file is determined according to the service software uninstallation configuration file, the user is prompted to confirm whether the uninstallation is to install a new one. The service software, if not, displays all the currently installed business software, so that the user selects the business software to be uninstalled from all the business software, and uninstalls the selected business software one by one in response to the user selecting the operation of the business software to be uninstalled.If the user selects Cancel to exit the uninstall; if to confirm this is to uninstall the installation of a new business software, and will be All the business software conflicting with the new business software is displayed, so that the user selects the business software that needs to be uninstalled from all the business softwares that conflict with the new business software, and responds to the operation of the business software that the user needs to uninstall, one by one. Uninstall the selected business software, and if the user chooses to cancel, exit the uninstallation. According to still another aspect of the present invention, a device for generating a software installation package includes: an obtaining module, configured to obtain version information of a service software, a file to be packaged, and information about a file to be packaged, according to version information of the service software. And the file to be packaged generates a configuration file and records information corresponding to the configuration file; a module for creating a software installation package, writing the installation unit at the head of the software installation package; and writing a module for installing the software installation package After the unit, the information corresponding to the configuration file, the configuration file, the information to be packaged, the file to be packaged, and the information about the tail structure are written. Preferably, the version information of the service software includes at least one of the following information corresponding to the service software: a mobile phone system, a platform, a service type, a service software version number, and a platform version number; the file information to be packaged includes at least one of the following: a current file path, File name, file size, installed platform main program path, file version number; configuration file information includes at least one of the following: the size of the configuration file, the configuration file name, the path where the configuration file is located; the tail structure information includes at least the following —: The file size of the installation unit, the total number of files to be packed, and the constant information of the positioning tail structure. Preferably, the installation unit includes: a first installation subunit, configured to read installation information of the platform software from the registry; a second installation subunit, configured to read information corresponding to the configuration file and a configuration file; The subunit is configured to determine whether the currently installed service software can run on the local platform software, and if not, prompt the user that the local platform software version is too low, and need to install a high version of the platform software to exit the installation; the fourth installation subunit , when the currently installed business software can run on the local platform software, determine whether a higher version of the currently installed business software is installed locally, and if so, whether it is necessary to install a business software lower than the current version, If necessary, the business software to be installed and the business software conflicting with the business software are recorded in the business software uninstall configuration file, and if not, the installation is exited; The fifth installation subunit is configured to determine whether a higher version file of the file included in the service software exists in the local installation directory when there is no local version of the service software than the currently installed service software, if not, install The service software writes the information corresponding to the service software into the service software installation configuration file; the sixth installation subunit is configured to prompt the user whether a higher version file of the file included in the service software exists in the local installation directory Uninstall all the business software that contains the high-level version file. If yes, write the business software installed and the business software that conflicts with the business software into the service software uninstall configuration file. If not, install the business software and The information corresponding to the service software is written into the service software installation configuration file. Preferably, the installation unit further includes: a seventh installation subunit, configured to read tail structure information of the currently running service software; and an eighth installation subunit, configured to determine whether the tail structure information is complete and correct, if no , the file format is incorrect, and the installation is finished. Preferably, the installation unit further includes: a ninth installation subunit, configured to generate the service software name according to the predetermined service software naming rule according to the version information of the read service software, and compare with the service software name currently being installed, If they are inconsistent, the current service software version information is incorrect and the installation is exited. The tenth installation subunit is used to read the currently installed service software information and display it to the user to confirm whether to install. If not, exit the installation. The eleventh installation subunit is configured to determine whether the local platform software is running, and if so, prompts to close the platform software and loop to determine whether the platform software is running. According to still another aspect of the present invention, a software uninstalling apparatus is provided, including: a reading module, configured to read a service software installation configuration file, and obtain current installed service software information; and a first determining module, configured to determine the present Whether the secondary uninstallation installation is to install new business software; the second judgment module is used to prompt the user to confirm whether the uninstallation is to install new business software; the first uninstallation module is configured to display all the currently installed business software. In order to enable the user to select the business software to be uninstalled from all the business software, in response to the user selecting the operation of the business software to be uninstalled, uninstalling the selected business software one by one, and exiting the uninstallation if the user selects canceling; the second uninstalling module, Displaying all business software that conflicts with the new business software to enable users to interact with the new business The business software that needs to be uninstalled is selected among all the business softwares that conflict with the software, and the selected business software is uninstalled one by one in response to the operation of the business software that the user selects to uninstall, and the uninstallation is exited if the user selects cancel. Through the invention, the utility model puts the relevant complex logic judgment of the installation into the installation unit, and packages the installation unit to the head of the file at the time of packaging, and adds corresponding information to let the program automatically process the solution, and solves the operation of installing the service software. Complex, error-prone issues that increase the flexibility of switching between versions of business software and ensure compatibility of all installed business software. BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings, which are set to illustrate,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, 1 is a schematic flowchart of a method for generating a software installation package according to an embodiment of the present invention; FIG. 2 is a schematic structural diagram of a software installation package according to an embodiment of the present invention; FIG. 3 is a software installation of an example of the present invention. FIG. 4 is a schematic flowchart of a method for installing a software installation package according to an example of the present invention; FIG. 5 is a schematic flowchart of a method for uninstalling a software installation package according to an example of the present invention; FIG. 7 is a schematic structural diagram of an apparatus for unloading a software installation package according to an embodiment of the present invention. FIG. BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, the present invention will be described in detail with reference to the accompanying drawings. It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict. FIG. 1 is a schematic flow chart of a method for generating a software installation package according to an embodiment of the present invention. As shown in FIG. 1, a method for generating a software installation package according to an embodiment of the present invention includes: In step S102, the version information of the service software, the file to be packaged, and the file to be packaged are obtained, and the configuration file is generated according to the version information of the service software and the file to be packaged, and the information corresponding to the configuration file is recorded. Step S104, creating a software installation package, and writing an installation unit (or an installer, an installation unit program) of the business software at the head of the software installation package. Step S106: After the installation unit of the software installation package, the information corresponding to the configuration file, the configuration file, the information to be packaged, the file to be packaged, and the structure of the tail structure are sequentially written to generate a software installation package of the service software. Through the above method, the installation unit is packaged into the head of the file at the time of packaging, the installation unit contains the relevant complex logic judgment of the installation, and corresponding information is written in the subsequent part of the software installation package, and the software is installed. When the package is installed, the entire installation process can be automatically processed by the installation unit to ensure the normal use of all installed business software, which can not only match the platform software and business software, but also ensure the compatibility and service of all installed business software. Flexibility to switch between versions of the software. The above method will be described in detail below with reference to FIG. Preferably, in the above method, the version information of the service software may further include at least one of the following information corresponding to the service software: a mobile phone system, a platform, a service type, a service software version number, and a platform version number; the file information to be packaged may further include At least one of the following: a current file path, a file name, a file size, a platform main program path after installation, and a file version number; the configuration file information may further include at least one of the following: a configuration file size, a configuration file name, and a configuration file The trailing structure information may further include at least one of the following: a file size of the mounting unit, a total number of files to be packed, and constant information of the positioning tail structure. The above information is the information that the installation unit needs when installing the software installation package. You can select one or more of them according to the actual situation, or you can add more information. After the packaging is completed, the structure of the generated software installation package is as shown in Figure 2. Preferably, the step of performing the software installation package for generating the service software by the installation unit may further include, but is not limited to: Step 1: reading the installation information of the local platform software from the registry; Step 2, reading from the software installation package Take the information corresponding to the configuration file and the configuration file; Step 3: Determine whether the currently installed service software can run on the local platform software. If not, prompt the user that the local platform software version is too low, and install a high version of the platform software to exit the installation; Step 4, if the currently installed service The software can run on the local platform software, and then continue to determine whether the local version of the currently installed business software is installed. If the user is prompted to install a lower version of the business software than the current version, if the user selects the required software, the user will The secondary installation business software and the business software conflicting with the business software are recorded in the business software uninstallation configuration file, and if not, the installation is exited; Step 5, if there is no local version of the service than the currently installed business software The software continues to determine whether there is a higher version file of the file included in the service software in the local installation directory. If not, the service software is installed and the information corresponding to the service software is written into the service software installation configuration file; Step 6 If the local installation If there is a higher version file of the file included in the service software, the user is prompted to uninstall all the business software containing the high version file. If the user selects yes, the business software installed this time and the business software conflict with the service software. The service software is written in the service software uninstall configuration file. If no, the service software is installed and the corresponding information of the service software is written into the service software installation configuration file. By performing the above steps, the above installation unit can install the generated software installation package on the corresponding platform. During the installation process, multiple judgments and selections have been made to ensure the normal use of all installed business software, to match the platform software and business software, and to ensure the compatibility of all installed business software and business software. Flexibility to switch between versions. Preferably, step 4 is gathered between 1 and 2, and the following processing may be further included: Step 7: reading the tail structure information of the currently running service software; Step 8: determining whether the tail structure information is complete and correct If no, the prompt file format is incorrect, the installation is finished, and if yes, it is determined to proceed to step 2. Preferably, between step 4 and step 4, the following processing may be further included: Step 9, the version information of the read service software is generated according to a predetermined service software naming rule, and the current service software name is generated. If the business software names being installed are compared, if they are inconsistent, the current service software version information is incorrect and the installation is exited. Step 10: If they are consistent, read the currently installed service software information and display it to the user to confirm whether to install, if not, exit the installation; Step 11, if installed, determine whether the local platform software is running, and if so, Then the user is prompted to close the platform software, and then the loop determines whether the platform software is running. If the platform software is not running, it is determined to perform step 3. By adding the above steps throughout the installation process, the entire process can be made more rigorous and complete, ensuring that the software installation package is properly and completely installed. The above software installation package installation method will be described in detail below with reference to FIG. The method for uninstalling the software installation package according to the embodiment of the present invention includes (hereinafter, the following software installation package uninstallation method will be described in detail with reference to FIG. 5): Step 1: Load the service software installation configuration file, and install and configure the service software from the service software. The currently installed business software information is read in the file. Step 2: According to the service software uninstallation configuration file, determine whether the uninstallation is to install new business software. If not, display all the currently installed business software, so that the user selects the business software to be uninstalled from all the business software. The selected business software is then uninstalled one by one in response to the user selecting the operation of the business software to be uninstalled, and if the user selects the cancellation, the uninstallation is exited. Step 3: If it is determined according to the service software uninstallation configuration file that the uninstallation is to install a new service software, the user is prompted again to confirm whether the uninstallation is to install a new service software. If the user selects No, the currently installed version is displayed. All the business software, so that the user selects the business software to be uninstalled from all the business software, and then uninstalls the selected business software one by one in response to the operation of the user selecting the business software to be uninstalled, and if the user selects cancel, exits the uninstallation. Step 4: If it is confirmed that the uninstallation is to install a certain business software, all the business softwares that conflict with the new business software are all displayed, so that the user selects from all the business softwares that conflict with the new business software. The business software that needs to be uninstalled is then uninstalled one by one in response to the user selecting the operation of the business software to be uninstalled, and if the user selects cancel, the uninstallation is exited. Through the above uninstallation method, intelligent uninstallation of each service software can be realized, and ensuring that the uninstallation of each service software does not affect the normal use of other business software. The above preferred embodiments will be described in detail below with reference to the examples and Figs. 3, 4, and 5. It should be noted that since the normal software development high version is a further extension of the function on the basis of the low version, it satisfies the compatibility of the high version to the low version. Therefore, in the embodiment of the present invention, the high version of the platform software must meet the compatibility version. For example, the platform version applicable to a certain service software is V1.0, and the platform version above V1.0 must satisfy the normal use of the business software; The same is true for plugins or file versions, and higher versions must be compatible with lower versions. However, the lower version is not necessarily compatible with the high version. FIG. 3 is a schematic flow chart of a method for generating a software installation package according to an example of the present invention. As shown in Figure 3, the packaging process of the software installation package includes the following steps: Step S302: Collect relevant version information of the packaged service software, including the format, platform, service type, service software version number, and applicable platform version number of the service software. Step S304: Collect the file to be packaged, including the file name, the corresponding file path, and the path of the file relative to the platform main program. Step S306: Generate a configuration file according to the information collected in the previous two steps, and record the name of the currently generated configuration file and the path where it is located. The configuration file name is generated according to the information collected in step S302 according to a certain rule, and the content of the configuration file includes all the contents collected in step S302 and step S304. Step S308: Obtain the version number of each collected file to be packaged. For the plug-in, the version number is set in the program, and for the text configuration file, the version number is recorded in the text. Step S310: Create an installation package program in a preset directory, where the installation package name is generated according to a certain rule according to the information collected in step S302. Step S312: Write the installation unit to the head of the installation package. Step S314: The configuration file information and the configuration file are sequentially written in the back of the installation unit. The configuration file information mainly records the size of the configuration file, and is convenient for positioning the location and size of the file when the configuration file is read. Step S316: The collected file information to be packaged and the file to be packaged are sequentially written to the configuration file, and the file information to be packaged includes the corresponding file name, size, relative platform main program path, and file version number. Step S318: Write the tail structure information at the end of the package file, mainly including the file size of the installation unit, the total number of packaged files, and a constant information for positioning the tail structure itself. After the above packaging step is completed, a software installation package is generated. As shown in Figure 2, the installation unit is packaged in the head of the business software, which contains all the logical processing of the installation process. After the packaged business software is started, the installation unit is triggered to run, as shown in Figure 4, the operation steps are as follows: Step S402: Read the installation information of the platform software from the registry, determine whether the platform software has been installed, and if not installed, prompt the user to install the platform software first, and exit the business software installation; if the platform software is installed, obtain the current platform software. installation path. Step S404: Read the tail structure information of the currently running service software, obtain the size of the installation unit in the service software, the total number of packaged files, and the constant information for locating the tail structure. Step S406: Step S404 is read to determine whether the information of the tail structure is complete and correct (mainly, whether the constant information of the read tail structure is correct), and if the related information is incorrect, the service software is considered to be incompletely packaged. Step S408: If the related information is completely met, the service software is considered to be completely packaged, and the process proceeds to step S410. Step S408: The service software package is incomplete, prompting the user that the file format is incorrect, returning an error, and ending the installation. Step S410: The service software is packaged completely, and the configuration file information is started to be read, because the file is attached to the installation unit, and the configuration file information is found by moving the installation unit corresponding to the size byte from the beginning of the service software. Get the relevant information and get the size of the configuration file. Step 4: S412: The content of the corresponding configuration file size byte is read as a configuration file, and the relevant version information of the service software can be obtained from the configuration file, including the mobile phone standard, platform, and service corresponding to the service software. Type, business software version number, and platform software version to which the business software is applicable. Step S414: The service software version information read in step S412 is generated according to the business software naming rule, and then compared with the service software name currently being installed. If not, the version number information in the software name is modified. If the software description is incorrect, go to step S416; otherwise, go to step S418. Step S416: The version information recorded by the software is inconsistent with the version information described by the software name itself, prompting the user that the currently used service software version information is incorrect, and the error is returned. This step mainly prevents the software name from being modified, and the user software installed by the user is caused. Or the version is not what you expected. Step S418: Read the currently installed service software information from the service software installation configuration file in the platform software installation directory, including the installed service software name, the corresponding version number, all files included in the business software, and relative to the platform. The relative path of the main program (each time a business software is installed, the corresponding installation information will be written into the service soft installation configuration file, so that the current business software installation information can be found during installation and uninstallation). Step S420: Display the installation information of the current service software to the user for confirmation, including the mobile phone system, platform, service type, version number, and applicable platform version number corresponding to the service software. If the user selects to install, proceed to step S422, otherwise the user selects Cancel to exit the installation. Step S422: determining whether the platform software is running, if it is running, proceeding to step S424, otherwise proceeding to step S426. Step S424: The user is prompted to close the platform software, and then proceeds to step S422. Step S426: determining whether the currently installed service software can be run on the local platform software, by reading the version of the locally installed platform software from the registry, and then comparing with the platform version applicable to the business software, if the local platform software version If the service software is not running on the local platform software, go to step S428. Otherwise, if the local platform software version is higher than or equal to the platform version applicable to the service software, the service software can be run on the local platform. On the version, go to step 4 to gather S430. Step S428: Prompt the user to the local platform software version, the user needs to install the high version of the platform software, and the error returns. Step S430: Determine whether a higher version of the currently installed service software is installed in the local area, and the current service software installation information has been read in step S418, and it can be checked whether the same service software has been installed, if the same business software is installed. Then, the version number is compared. If the same service software is installed locally and the local version is higher than the currently installed service software version, go to step S432; otherwise, if the service software is not installed locally, or the locally installed service software and current The business software version is the same or 4氐 is the service software version, and the process proceeds to step S436; Step S432: Ask the user whether to continue to install the current low-level service software. If the user selects "Yes", go to step S434, and select "No" to exit the installation of the service software. Step S434: Record the service software to be installed and the service software that conflicts with the service software (that is, the service software that is installed locally and has a higher version than the service software) in the service software uninstall configuration file, so that the next uninstallation is convenient. Smart recognition, exit this installation. Step S436: If there is no higher version of the currently installed service software, the method further determines whether there is a higher version of the file included in the service software in the local installation directory. For example, another locally installed business software contains an X file, and The currently installed business software also contains X files, and the local X file version is higher than the currently installed X file version. If not, the process goes to step S438, otherwise to step S442. Step S438: Install the business software, and read the first file information from the configuration file in the business software. The file information records the name, relative path, file size, and version number of the corresponding file, from the first file information. The file that reads the corresponding file length and size is the first file, and is released to the corresponding directory (the file is calculated by the platform software installation path obtained in step S402 and the relative path recorded in the file information here). Release directory). Then read the second file information from the end of the first file... and so on, read all the files and release them to the corresponding directory. Here, by counting the accumulation, when the number of files read is the same as the number of files recorded in the tail file structure information, the file reading release is completed, and the flow proceeds to step S440. Step S440: Write the installed service software related information into the service software installation configuration file, including the business software name, the version number, each file included in the business software, and the relative path of each file relative to the platform main program. To prevent the installation configuration file from being arbitrarily tampered with, the configuration file is encrypted. At this point, the business software installation is successful and ends. Step S442: Ask the user whether to uninstall all the business software containing the high version file, for example, the local file X is the same as the current business software, and the local X version is relatively high, and ask the user whether to delete all the business software containing X. If yes, go to step S446, and go to step S444. Step S444: Install the business software, the basic processing is the same as step S438, the difference is that when the file is released, it is judged if the local existence is higher than the file version. If the file with the same name is skipped, the file is not released, and then the next file is read. After the installation is completed, the process proceeds to step S440. Step S446: Write the business software that is installed this time and the business software that conflicts with the service software (that is, all the business software that contains the same high-version file as the service software) into the service software uninstall configuration file, so as to facilitate Intelligent identification when uninstalling, exit this installation. It should be noted that only the business software that failed the last installation and the business software that conflicts with it are recorded in the business software uninstallation configuration file, that is, the last record is cleared every time a new record is written, so as to prevent multiple software installations continuously. Recording multiple records causes logical confusion, so each time you uninstall, you can only intelligently identify the business software that failed to install last time. The corresponding unloading method is as shown in FIG. 5. The uninstalling method mainly includes: Step S502: Loading a service software installation configuration file from the platform installation directory, and reading and parsing the currently installed business software information, including the service software name and version number. , all files included in the business software, the corresponding version number, and the relative path of the file. Step S504: Determine whether the uninstallation is to install a certain service software. By loading the uninstallation configuration file of the business software, read and parse the related information, and check whether the business software A that failed the last installation is recorded in the file. If yes, it indicates that the last service software A is not successfully installed due to a version conflict, and all service software conflicting with the service software A is read, and the process goes to step S506; otherwise, if the content of the uninstall configuration file is empty, the description is The last time there was no installation failure of a business software, go to 4 S510. Step S506: The prompt information and the user confirm whether the uninstallation is to install the business software A. If the user selects "Yes", go to step S508, select "No", and then go to step S510. Step S508: All the business softwares that conflict with the business software A are displayed, and all are selected by default. After the user further selects the determination, the process goes to step S512. Step S510: Display all the currently installed service software, and wait for the user to select the service software to be uninstalled, and go to step S512. Step S512: If the user selects the service software that needs to be uninstalled and determines to go to step S514, otherwise if the user cancels, go to step S516. Step S514: Unloading the software that the user selects to uninstall one by one. When uninstalling each service software, it is judged one by one whether the file included in the service software exists in other installed business software, and if not, the file is not deleted, if not If it exists, delete the corresponding file in the corresponding directory. Per uninstall After completing a business software, update the business software installation configuration table, delete the records corresponding to the uninstalled software, and update the current business software information. Step S516: Exit this uninstallation. FIG. 6 is a schematic structural diagram of a device for generating a software installation package according to an embodiment of the present invention. As shown in FIG. 6, the device for generating a software installation package according to an embodiment of the present invention includes: an obtaining module 62, configured to obtain version information of a service software, a file to be packaged, and information to be packaged, and version information of the service software and The package file generates a configuration file and records the information corresponding to the configuration file. Create module 64, set to create a software installation package, write the installation unit at the head of the software installation package. The writing module 66 is configured to sequentially write the information corresponding to the configuration file, the configuration file, the information to be packaged, the file to be packaged, and the information of the tail structure after the installation unit of the software installation package. The software installation package generated by the above device has a special structure, and the packaged complex logic is installed to determine the installation unit to be packaged to the head of the file for automatic processing, and correspondingly written in the subsequent part of the software installation package. Information. When the software installation package is installed, the entire installation process can be automatically processed by the installation unit to ensure the normal use of all installed business software, which can not only match the platform software and the business software, but also ensure that all the installation software is installed. Compatibility and flexibility to switch between versions of business software. Preferably, the version information of the service software may further include at least one of the following information corresponding to the service software: a mobile phone system, a platform, a service type, a service software version number, and a platform version number; the file information to be packaged may further include at least one of the following : current file path, file name, file size, platform main program path after installation, file version number; configuration file information may further include at least one of the following: configuration file size, configuration file name, path where the configuration file is located; tail structure The volume information may further include at least one of the following: a file size of the installation unit, a total number of files to be packed, and constant information of the positioning tail structure. The above information is the information that the installation unit needs when installing the software installation package. You can select one or more of them according to the actual situation, and you can add more information. Preferably, the above-described mounting unit may further include (not shown in the following sub-unit drawings): The first installation subunit is configured to read installation information of the platform software from the registry; the second installation subunit is configured to read information corresponding to the configuration file and the configuration file; and the third installation subunit is set to determine the current installation. Whether the business software can run on the local platform software, if not, it prompts the user that the local platform software version is too low, and needs to install a high version of the platform software to exit the installation; the fourth installation subunit is set to the currently installed business software. When running on the local platform software, it is determined whether a higher version of the currently installed business software is installed locally, and if so, whether it is necessary to install a business software lower than the current version, and if necessary, the current installation is required. The business software and the business software that conflicts with the business software are recorded in the business software uninstall configuration file. If not, the installation is exited; the fifth installation subunit is set to have no higher version locally than the currently installed business software. When the business software is used, determine whether the local installation directory is The higher version file of the file included in the service software, if not, the service software is installed and the corresponding information of the business software is written into the service software installation configuration file; the sixth installation subunit is set to the local installation directory. When there is a higher version file of the file included in the service software, the user is prompted to uninstall all the business software containing the high version file, and if so, the business software installed this time and the business software that conflicts with the business software. The service software uninstallation configuration file is written. If no, the service software is installed and the corresponding information of the service software is written into the service software installation configuration file. Preferably, the above-mentioned mounting unit may further include (not shown in the following sub-unit drawings): a seventh installation sub-unit, configured to read the tail structure information of the currently running service software; the eighth installation sub-unit, Set to determine whether the tail structure information is complete and correct. If not, the file format is incorrect and the installation ends. Preferably, the above-mentioned installation unit may further include (not shown in the following sub-unit diagram): the ninth installation sub-unit is configured to generate the service according to the predetermined service software naming rules according to the version information of the read service software. The software name is compared with the name of the business software currently being installed. If they are inconsistent, the current service software version information is incorrect and the installation is exited. The tenth installation subunit is configured to read the currently installed business software information and display it to the user to confirm whether the installation is performed. If not, the installation is exited; the eleventh installation subunit is set to determine whether the local platform software is running, If yes, it prompts to close the platform software and loop to determine if the platform software is running. In the specific implementation process, the installation unit can complete the entire installation process of the software installation package through the above subunits. FIG. 7 is a schematic structural diagram of an unloading apparatus of a software installation package according to an embodiment of the present invention. As shown in FIG. 7, the uninstalling apparatus of the software installation package includes: a reading module 702, configured to read a service software installation configuration file, and obtain information about currently installed business software; and a first determining module 704, configured to determine the current time Whether the uninstallation installation is to install a certain business software; the first determining module 706 is configured to prompt the user to confirm whether the uninstallation is to install new business software; the first uninstalling module 708 is configured to display all the services currently installed. Software, so that the user selects the business software that needs to be uninstalled from all the business softwares, and in response to the user selecting the operation of the business software that needs to be uninstalled, uninstalls the selected business software one by one, and exits the uninstallation if the user selects canceling; the second uninstalling module 710 And setting, to display, all the business software conflicting with the new business software, so that the user selects the business software that needs to be uninstalled from all the business software that conflicts with the new business software, and responds to the operation of the business software that the user needs to uninstall, Uninstall the selected business software one by one, if the user chooses If you choose to cancel, exit the uninstall. The unloading device is relatively independent, and the user can independently operate the device. To facilitate management, the device is preferably packaged and distributed together in the platform software. In the specific implementation process, the modules, units, and sub-units of the present invention described above may be implemented by a general-purpose computing device, which may be centralized on a single computing device or distributed on a network composed of multiple computing devices. Alternatively, they may also be implemented by program code executable by a computing device, and thus the division of the above modules, units, subunits is only a preferred example. As a whole, the device for generating the software installation package is mainly used for: (A) collecting packaged software version information and file information to be packaged, wherein the service software version information includes the service name and version number of the service software. And the platform version to which the business software is applicable, the file information to be packaged includes the name and relative path of the file; (B) generating a corresponding configuration file according to the collected information, recording the path and name of the corresponding configuration file; (C) creating the packaged software, the header Write to the installation unit program, and then write the configuration file and each file to be packaged in turn, wherein the configuration file and each file to be packaged are written to the file content after the file information is first written, and the package software writes the mark structure at the end Information, records the size and number of related files, and is used to indicate that the file is fully packaged. The installation unit is the installation program written by the package software header, mainly for: (A) reading the installation information of the platform software from the registry, obtaining the installation path of the platform software; (B) reading the package software tail structure Body information, determine the integrity of the packaged software; (C) read the configuration file to determine the correctness of the packaged software version information; (D) read the locally installed business software information from the business software installation configuration file; (E) Determine whether the platform software is running. If the platform software is running, prompt the user to close the platform software, and confirm the service software installation information with the user after confirming that the platform software is not running; (F) After the user confirms the information and starts the installation, determine the current Whether the platform software version meets the requirements of the business software. If the platform software version is lower than the service software requirement, the user is prompted to install the high version platform software; (G) determine whether the business software to be installed has a higher version locally, if it is already installed. For later versions of the business software, if the user needs to fall back to the version, this will be installed this time. The software and the conflicting local high-level software are recorded in the uninstall configuration file for the intelligent judgment of the program when the user subsequently uninstalls, and prompt the user to uninstall the corresponding high version software first, if the user does not need to roll back the lower version, Stop the installation of the software; (H) Determine whether there is a higher version of each file included in the business software to be installed. If it does not exist, install it directly. If it exists, you need to confirm whether you need to uninstall each file containing the high version file. If the business software needs to be uninstalled, the business software to be installed and all the business software that conflicts with it are recorded in the uninstall configuration file. If the uninstallation is not required, the local software version is encountered when the business software is installed. When the file version is high, the corresponding file skips and is not released. (I) After installing all the business software and releasing the files to the corresponding directory, record the business software name, version number, all files included in the business software and their corresponding files in the installation configuration file. path. The above-mentioned unloading device is used for implementing intelligent and flexible uninstallation of service software, and is mainly used for: (A) reading a service software installation configuration file, and acquiring current installed service software information; (B) reading a service software uninstallation configuration file, and determining Whether the uninstallation installation is to install a certain business software, and if so, all the business software that conflicts with the business software is displayed for the user to select and confirm. If the uninstallation is not for installing a business software, all the locally installed services are displayed. Business software for users to choose to confirm (C) uninstalling one by one according to the business software selected by the user to be uninstalled. When uninstalling each business software, it is judged one by one whether the files included in the business software are also present in other locally installed business software, if If it exists, the file will not be deleted. If it does not exist, delete the corresponding file in the corresponding directory. Update the business software installation configuration file and uninstall the configuration file after the uninstallation is completed. From the above description, it can be seen that, compared with the prior art, the method and device provided by the present invention can enable the service software to be automatically installed in the directory where the platform software is located, without requiring the user to select settings, and can ensure all installed business software. The normal use can not only match the platform software and the business software, but also ensure the compatibility of all installed business software and the flexibility of switching between versions of the business software, and can realize the intelligent uninstallation of each business software to ensure each business. Software uninstallation does not affect the normal use of other business software. In summary, the present invention is mainly directed to the special requirements of the business software installation based on the secondary development of the plug-in technology, putting all the installation logic judgment and processing into the installation unit program, and packaging the installation unit program at the head of the file. The files required for other packaging are attached, so that the installation unit program is automatically started after the business software is started, and the software is automatically installed according to the user's requirements. The intelligent processing for installing and uninstalling multiple business software is solved by the method of configuration file recording. In order to prevent the configuration file from being maliciously changed, the configuration file is encrypted accordingly. Obviously, those skilled in the art should understand that the above modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device, such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein. The steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps are fabricated as a single integrated circuit module. Thus, the invention is not limited to any particular combination of hardware and software. The above description is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the scope of the present invention are intended to be included within the scope of the present invention.

Claims

Claim

1. A method for generating a software installation package, comprising:

Obtaining the version information of the service software, the file to be packaged, and the information to be packaged, generating a configuration file according to the version information of the service software and the file to be packaged, and recording information corresponding to the configuration file;

Creating a software installation package, and writing an installation unit of the business software at a header of the software installation package;

After the installation unit of the software installation package, the information corresponding to the configuration file, the configuration file, the to-be-packaged file information, the to-be-packaged file, and the tail structure information are sequentially written to generate the service. Software installation package for the software.

2. The method according to claim 1, wherein

The version information of the service software includes at least one of the following information corresponding to the service software: a mobile phone system, a platform, a service type, a service software version number, and a platform version number; and the file information to be packaged includes at least one of the following: File path, file name, file size, platform main program path after installation, file version number;

The configuration file information includes at least one of the following: a configuration file size, a configuration file name, and a path where the configuration file is located;

The tail structure information includes at least one of: a file size of the installation unit, a total number of files to be packed, and constant information for positioning the tail structure.

The method according to claim 2, wherein the method further comprises: performing a software installation package of the service software according to the following steps:

Read the installation information of the local platform software from the registry;

Reading information corresponding to the configuration file and the configuration file from a software installation package of the service software;

Determining whether the currently installed service software can run on the local platform software; if not, prompting the user that the local platform software version is too low, and installing a higher version of the platform software, and exiting the installation; If the currently installed service software can run on the local platform software, continue to determine whether a higher version of the currently installed service software is installed locally, and if so, whether it is required to install a service software lower than the current version. If necessary, the business software to be installed and the business software conflicting with the business software are recorded in the business software uninstall configuration file, and if not, the installation is exited;

If there is no higher version of the business software than the currently installed service software, it is determined whether there is a higher version file of the file included in the service software in the local installation directory, and if not, the service software is installed and the service is installed. The information corresponding to the software is written into the service software installation configuration file;

If there is a higher version file of the file included in the service software in the local installation directory, it is prompted whether to uninstall all the business software containing the high version file, and if so, the business software installed this time and the business software conflict with the service software. The service software is written into the service software uninstall configuration file. If no, the service software is installed and the corresponding information of the service software is written into the service software installation configuration file.

The method according to claim 3, wherein, after the reading the installation information of the platform software from the registry, the reading the configuration file information and the configuration file, the method further includes:

Reading the tail structure information of the currently running business software;

It is determined whether the information of the tail structure is complete and correct. If not, the file format is incorrect, and the installation is terminated. If yes, it is determined to perform the step of reading the configuration file information and the configuration file.

The method according to claim 3, wherein, after the reading the profile information and the configuration file, before determining whether the currently installed service software can be run on the local platform software , Also includes:

The version information of the service software that is read is generated according to a predetermined business software naming rule, and is compared with the service software name currently being installed. If the information is inconsistent, the current service software version information is incorrect. Exit the installation;

If they are consistent, the currently installed business software information is read and displayed to the user to confirm whether the installation is performed. If not, the installation is exited;

If installed, it is determined whether the local platform software is running, and if so, prompting to close the platform software, and then periodically determining whether the platform software is running, if the level is If the software is not running, it is determined to perform the step of determining whether the currently installed service software can run on the local platform software.

6. A software uninstallation method for a software installation package according to any one of claims 1 to 5, comprising:

Loading a business software installation configuration file, and reading the currently installed business software information from the business software installation configuration file;

According to the service software uninstallation configuration file, it is determined whether the uninstallation is to install new business software. If not, all the currently installed business softwares are displayed, so that the user selects the business software to be uninstalled from all the business softwares, and responds. When the user selects the operation of the business software that needs to be uninstalled, the selected business software is uninstalled one by one, and if the user selects the cancellation, the uninstallation is exited;

If the uninstallation is based on the service software uninstallation configuration file, the user is prompted to confirm whether the uninstallation is to install new business software. If not, all the currently installed business software is displayed. Having the user select the service software that needs to be uninstalled from all the service softwares, and in response to the user selecting the operation of the service software that needs to be uninstalled, uninstalling the selected service software one by one, and exiting the uninstallation if the user selects cancellation;

If it is confirmed that the uninstallation is to install new business software, all the business softwares that conflict with the new business software are all displayed, so that the user selects from all the business softwares that conflict with the new business software. The uninstalled business software, in response to the user selecting an operation of the business software to be uninstalled, uninstalls the selected business software one by one, and exits the uninstallation if the user selects cancel.

7. A device for generating a software installation package, comprising:

The obtaining module is configured to obtain the version information of the service software, the file to be packaged, and the information to be packaged, the version information of the service software and the configuration file to be packaged, and record the corresponding information of the configuration file; Creating a software installation package, and writing the installation unit at the head of the software installation package;

a writing module, configured to sequentially write information corresponding to the configuration file, the configuration file, the to-be-packaged file information, the to-be-packaged file, and the tail structure after the installation unit of the software installation package Information, a software installation package that generates the business software.

8. The apparatus according to claim 7, wherein

The version information of the service software includes at least one of the following information corresponding to the service software: a mobile phone system, a platform, a service type, a service software version number, and a platform version number;

The file information to be packaged includes at least one of the following: a current file path, a file name, a file size, a platform main program path after installation, and a file version number;

The configuration file information includes at least one of the following: a size of the configuration file, a configuration file name, and a path where the configuration file is located;

9. The device according to claim 8, wherein the installation unit comprises:

a first installation subunit, configured to read installation information of the platform software from the registry; a second installation subunit, configured to read information corresponding to the configuration file and the configuration file;

The third installation subunit is configured to determine whether the currently installed service software can run on the local platform software. If not, the user is prompted that the local platform software version is too low, and a high version of the platform software needs to be installed to exit the installation;

a fourth installation subunit, configured to determine whether a higher version of the currently installed service software is installed locally when the currently installed service software is executable on the local platform software, and if yes, whether the installation ratio is required If the service software of the current version is low, the service software to be installed and the service software conflicting with the service software are recorded in the service software uninstall configuration file, and if not, the installation is exited;

The fifth installation subunit is configured to determine whether a higher version file of the file included in the service software exists in the local installation directory when there is no higher version of the business software than the currently installed service software, and if not, install The business software writes information corresponding to the business software into the business software installation configuration file;

The sixth installation subunit is configured to prompt the user to uninstall all the business software containing the high version file when the higher version file of the file included in the service software exists in the local installation directory, and if yes, the installation is performed. The service software and the business software that conflicts with the service software are written into the service software uninstall configuration file. If not, the service software is installed and the corresponding information of the service software is written into the service software installation configuration file.

23 P41331

The device according to claim 9, wherein the installation unit further comprises: a seventh installation subunit, configured to read tail structure information of the currently running service software;

The eighth installation subunit is set to determine whether the information of the tail structure is complete and correct. If not, the file format is incorrect, and the installation is ended.

The device according to claim 9, wherein the installation unit further comprises:

The ninth installation subunit is configured to generate the service software name according to the predetermined service software naming rule according to the version information of the read service software, and compare with the service software name currently being installed, if not, prompt the current use The business software version information is incorrect, and the installation is exited;

The tenth installation subunit is configured to read the currently installed business software information and display it to the user to confirm whether the installation is performed, and if not, exit the installation;

The eleventh installation subunit is configured to determine whether the local platform software is running, and if so, prompt to close the platform software, and cyclically determine whether the platform software is running.

12. A software uninstallation apparatus for uninstalling the installation package program of any one of claims 1 to 5, comprising:

The reading module is configured to read the business software installation configuration file to obtain the currently installed business software information; the first determining module is configured to determine whether the uninstalling installation is to install new business software;

The second determining module is configured to prompt the user to confirm whether the uninstalling is to install new business software; the first uninstalling module is configured to display all the currently installed business software, so that the user selects from all the business software. The business software that needs to be uninstalled, in response to the user selecting the operation of the business software that needs to be uninstalled, uninstalling the selected business software one by one, and exiting the uninstallation if the user selects canceling;

a second uninstalling module, configured to be in contact with all the business software that displays the new business software conflict, so that the user selects the business software that needs to be uninstalled from all the business software that conflicts with the new business software, in response to the user's selection The operation of the uninstalled business software, uninstalling the selected business software one by one, and exiting the uninstallation if the user selects cancel.

24 P41331