A software listing method, system, device, and medium based on an app store

Abstract

This application is applicable to the technical field of software distribution, and provides a software listing method based on an application store, including: obtaining configuration information of the application store, authenticating the application store based on the configuration information to obtain authorization information; splitting a plurality of the application stores according to functions to obtain a plurality of function interfaces; calling the function interfaces, and encapsulating the plurality of function interfaces into a listing interface; creating a store instance object based on the listing interface, and calling the store instance object based on the authorization information to list the software to the application store. This application can uniformly manage the software listing process of different application stores, thereby simplifying the development process and improving the development efficiency.

Description

Technical Field

[0001] This application belongs to the technical field of software distribution, and particularly relates to a software listing method, system, device, and medium based on an application store. Background Art

[0002] In the current increasingly competitive and diversified software distribution market, in order to effectively expand the user base of software products and increase market penetration, software developers usually list software products on multiple third-party application stores, so that software products can reach a wider range of potential user groups, and at the same time, attract different types of user groups through the features and advantages of different store channels.

[0003] In the prior art, the process of listing software usually requires manual operations, including steps such as docking with various third-party application stores, submitting review materials, waiting for review results, handling review feedback, and finally uploading the package body. This is not only inefficient but also error-prone. In addition, with the continuous increase in the number of third-party application stores in the market, software developers need to face more cumbersome submission and review processes, and each third-party application store has its own review criteria and processes, which requires software developers to spend a lot of time and effort to understand and adapt. At the same time, software version updates are also a frequent and important task. Developers need to ensure that the game versions in each third-party application store channel are the latest to provide a good user experience. Therefore, the workload in the software listing process is cumbersome and complex, which seriously affects the software distribution efficiency. Summary of the Invention

[0004] The embodiments of this application provide a software listing method, system, device, and medium based on an application store, which can solve one of the above-mentioned prior art problems.

[0005] In a first aspect, the embodiments of this application provide a software listing method based on an application store, including:

[0006] Obtain the configuration information of the application store, and based on the configuration information, authenticate the application store to obtain authorization information;

[0007] Split multiple application stores according to functions to obtain multiple function interfaces;

[0008] Call the function interfaces and encapsulate multiple function interfaces into a listing interface;

[0009] Based on the listing interface, create a store instance object, and based on the authorization information, call the store instance object to list the software on the application store.

[0010] Further, the obtaining of the configuration information of the application store includes:

[0011] Search for a match in the preset store configuration management module according to the name of the application store to obtain the target application store. The store configuration management module includes configuration information of different application stores.

[0012] Furthermore, the configuration information includes authentication interface information and identity authentication information;

[0013] Authenticate the application store based on the configuration information to obtain authorization information, including:

[0014] Based on the authentication interface information, establish a connection relationship between the application store and a predefined authentication abstract interface to obtain authentication interface parameters;

[0015] Package the authentication interface parameters and the identity authentication information to obtain authentication request parameters;

[0016] Pass the authentication request parameters to the authentication interface of the application store and initiate an authentication request to the authentication interface;

[0017] Receive the response information of the authentication interface, parse and verify the response information to obtain an authentication result. The response information includes authorization information;

[0018] When the authentication result is successful, store the authorization information in the cache system.

[0019] Furthermore, splitting the multiple application stores according to functions to obtain multiple function interfaces includes:

[0020] Construct a domain model according to the business logic of software application listing;

[0021] Based on the domain model, divide the application store into different business domains, and conduct business division for each business domain to form multiple sub-domains. Among them, the business domains include software application domain, application store domain, submission and release domain, and data domain, and each sub-domain corresponds to a function interface.

[0022] Furthermore, after splitting the application store according to functions to obtain multiple function interfaces, it includes:

[0023] Abstractly describe each function interface and determine the name of each function interface;

[0024] Set the call data when calling the function interface. The call data includes input parameters, output response information, interface protocol, and request path;

[0025] Package the call data into an interface document.

[0026] Further, the calling of the function interfaces and encapsulating multiple function interfaces into a listing interface includes:

[0027] When listing a software on an application store, according to the business requirements of software listing, analyze and determine one or more function interfaces to be called, obtain the call data required for calling all the function interfaces, and form a call list;

[0028] Analyze the call list, determine the dependency relationships and call sequences among the function interfaces, and form a call logic flowchart;

[0029] Based on the call logic flowchart and the call data of each function interface, encapsulate multiple function interfaces into one listing interface.

[0030] Further, the creating of a store instance object based on the listing interface includes:

[0031] According to the listing interface, obtain listing data, where the listing data is the data required for listing the software on the application store;

[0032] Based on the listing data, create a store instance object for the application store, where the store instance object is the software to be listed.

[0033] In a second aspect, an embodiment of the present application provides a software listing system based on an application store, including:

[0034] A store authentication module: used to obtain the configuration information of the application store, authenticate the application store based on the configuration information, and obtain authorization information;

[0035] A store abstraction module: used to split multiple application stores by function to obtain multiple function interfaces;

[0036] A listing interface encapsulation module: used to call the function interfaces and encapsulate multiple function interfaces into a listing interface;

[0037] A software listing module: used to create a store instance object based on the listing interface, and call the store instance object based on the authorization information to list the software on the application store.

[0038] In a third aspect, an embodiment of the present application provides a terminal device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the above-mentioned software listing method based on an application store is implemented.

[0039] Fourthly, an embodiment of the present application provides a computer-readable storage medium. The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the software listing method based on the application store described above is implemented.

[0040] The beneficial effects of the embodiments of the present application compared with the prior art are as follows:

[0041] For a software listing method based on an application store of the present application, by uniformly configuring authentication interface information, identity authentication information and other configuration information for each application store, the configurations of different application stores can be uniformly managed, which is convenient for management and effectively avoids the disadvantages that in the traditional mode, software developers need to log in to the web backends of multiple application stores one by one for cumbersome configuration, significantly reducing the workload. At the same time, different application stores are uniformly split into multiple functional modules independent of specific application stores, thereby eliminating the functional differences between different application stores. Each functional module is designed to focus on solving problems in a specific field, improving the compatibility and interoperability of different application stores, thus simplifying the development process and improving the development efficiency. Description of the Drawings

[0042] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following will briefly introduce the drawings required for use in the embodiments or the description of the prior art. Obviously, the following drawings are only some embodiments of the present application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0043] Figure 1 is a schematic flowchart of a software listing method based on an application store provided by an embodiment of the present invention;

[0044] Figure 2 is a schematic structural diagram of a software listing system based on an application store provided by an embodiment of the present invention;

[0045] Figure 3 is a schematic structural diagram of a terminal device provided by an embodiment of the present application. Detailed Embodiments

[0046] In the following description, specific details such as specific system structures and technologies are proposed for the purpose of illustration rather than limitation, so as to thoroughly understand the embodiments of the present application. However, those skilled in the art should clearly understand that the present application can also be implemented in other embodiments without these specific details. In other cases, the detailed descriptions of well-known systems, devices, circuits and methods are omitted to avoid unnecessary details from interfering with the description of the present application.

[0047] It should be understood that when used in the specification and the appended claims of this application, the term "comprising" indicates the presence of the described features, wholes, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, wholes, steps, operations, elements, components and / or their combinations.

[0048] It should also be understood that the term "and / or" used in the specification and the appended claims of this application refers to any combination and all possible combinations of one or more of the associated listed items, and includes these combinations.

[0049] As used in the specification and the appended claims of this application, the term "if" can be interpreted as "when", "once", "in response to determining", or "in response to detecting" depending on the context. Similarly, the phrases "if determined" or "if [the described condition or event] is detected" can be interpreted as meaning "once determined", "in response to determining", "once [the described condition or event] is detected", or "in response to detecting [the described condition or event]" depending on the context.

[0050] In addition, in the description of the specification and the appended claims of this application, the terms "first", "second", "third", etc. are only used for differentiating descriptions and cannot be understood as indicating or implying relative importance.

[0051] Reference to "one embodiment" or "some embodiments" or the like described in the specification of this application means that a specific feature, structure or characteristic described in connection with that embodiment is included in one or more embodiments of this application. Thus, statements such as "in one embodiment", "in some embodiments", "in other some embodiments", "in still other embodiments", etc. that appear in different places in this specification do not necessarily all refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in another way. The terms "comprising", "including", "having" and their variants all mean "including but not limited to", unless otherwise specifically emphasized in another way.

[0052] Please refer to Figure 1 As shown, the present invention is a software listing method based on an application store, including the following steps:

[0053] S100. Obtain the configuration information of the application store, and based on the configuration information, authenticate the application store to obtain authorization information;

[0054] In this embodiment, the software is equipped with a store configuration management module, which uniformly configures configuration information such as authentication interface information and identity authentication information for each application store, thereby uniformly managing the configuration of different application stores, facilitating management, and effectively avoiding the disadvantages of the traditional mode where software developers need to log in to the web backends of multiple application stores one by one to perform tedious configurations, significantly reducing the workload and reducing the risk of information leakage caused by human operational errors. Specifically, before putting the software on the application store, the application store needs to be authenticated to obtain authorization information, without having to log in to the web backend of the corresponding application store to perform the listing operation.

[0055] In some embodiments, obtaining configuration information of the application store includes:

[0056] According to the name of the application store, a matching search is performed in a preset store configuration management module to obtain a target application store, wherein the store configuration management module includes configuration information of different application stores.

[0057] In this embodiment, a centralized management interface is provided in the preset store configuration management module. The user can enter the keyword of the application store name in the centralized management interface, thereby matching and searching the corresponding target application store in the store configuration module, and then obtaining the corresponding configuration information of the application store.

[0058] In this embodiment, the matching search process adopts a fuzzy matching algorithm to calculate the similarity between the keywords of the application store name entered by the user and the application store name preset in the store configuration management module, and the application store with the highest similarity is used as the target application store, and its corresponding configuration information is returned.

[0059] In one embodiment, by entering the keywords of the corresponding software name in the centralized management interface, the application store corresponding to the software name can be obtained, so that the corresponding application store can perform review operations on the software. The review operation is used to perform content review, version review, and technical review on the software to ensure that the software content is healthy and uplifting and conforms to the mainstream values ​​of society. At the same time, it verifies whether the software has legal copyright and authorization, ensures that the software does not infringe on the intellectual property rights of others, and ensures that the software can operate normally on various devices and network environments.

[0060] In some of these embodiments, the configuration information includes authentication interface information and identity authentication information;

[0061] The authenticating the application store based on the configuration information to obtain authorization information includes:

[0062] Based on the authentication interface information, a connection relationship between the application store and a predefined authentication abstract interface is established to obtain authentication interface parameters;

[0063] Encapsulate the authentication interface parameters and the identity authentication information to obtain authentication request parameters;

[0064] Pass the authentication request parameters to the authentication interface of the application store and initiate an authentication request to the authentication interface;

[0065] Receive the response information from the authentication interface, parse and verify the response information to obtain an authentication result, where the response information includes authorization information;

[0066] When the authentication result is successful, store the authorization information in the cache system.

[0067] In this embodiment, the authentication interface information includes the interface address and the protocol type, and an efficient and flexible security protection framework is constructed for the application store. According to the authentication interface information, a connection relationship is established between the application store and the authentication abstract interface, enabling the application store to perform authentication operations and obtain authentication interface parameters for initiating an authentication request to the authentication interface to implement the authentication operation.

[0068] In this embodiment, the identity authentication information includes the application store identifier and the authentication key. Through the encapsulation process of the authentication interface parameters and the identity authentication information, the authentication interface parameters and the identity authentication information are integrated into a request packet with authentication request parameters, which can prevent the identity authentication information from being intercepted or tampered with separately during the transmission process, thereby improving the security of the entire authentication process. In addition, the encapsulated authentication request parameters are directly used to initiate a request to the authentication interface, eliminating the need for software developers to manually splice authentication-related parameters in the code, reducing the possibility of errors, simplifying the writing of the authentication logic, making the authentication process clearer and more efficient. At the same time, by encapsulating the authentication request parameters, it can promote the standardization of the interface between the application store and the application store authentication service. The standardized authentication request parameters help to reduce compatibility issues between different application stores and promote the sharing and interoperability of cross-platform and cross-service authentication capabilities.

[0069] The encapsulation mechanism of the authentication interface parameters and the identity authentication information in this embodiment allows for flexible adjustment of the format and content of the authentication request parameters without changing the authentication interface parameters and the identity authentication information themselves. That is, when the authentication interface parameters and the identity authentication information change, only the encapsulation logic needs to be modified, without the need for large-scale reconstruction of the entire authentication process.

[0070] In this embodiment, during the authentication process, the response information returned by the authentication interface is received, parsed, and verified to determine whether the authentication is successful. Specifically, the response information includes authentication success information and authentication failure information. When the authentication is successful, while returning the authentication success information, authorization information such as an authorization token and an authorization scope is synchronously returned and stored in the cache system. When the user initiates a software listing request, the above authorization information is called to provide support for software listing. When the authentication fails, the authentication failure information returned contains an error code, and software developers can perform corresponding exception handling and retry mechanisms based on the above error code to obtain authorization information.

[0071] S200. Split the multiple application stores according to their functions to obtain multiple function interfaces.

[0072] In some embodiments, the above step S200 includes:

[0073] Construct a domain model according to the business logic of software listing.

[0074] Based on the domain model, divide the application stores into different business domains, and perform business division on each business domain to form multiple sub-domains. Among them, the business domains include the software application domain, the application store domain, the submission and release domain, and the data domain, and each sub-domain corresponds to a function interface.

[0075] In this embodiment, constructing a domain model according to the business logic of software listing includes the following steps: obtaining the business basic information, business process information, and business domain information of the software listing business according to the business logic of software listing; performing architecture division according to the business basic information to form multiple business domains; dividing the multiple business domains according to the business process information to form sub-domains; extracting domain keywords from the business domain information, and through correlation analysis, classifying the domain keywords in an orderly manner to ensure that each category of domain keywords is closely associated with the corresponding sub-domain function, and at the same time defining the corresponding bounded context for each sub-domain, thereby clarifying the scope and boundary of the role of the sub-domain within the business domain, and thus determining the correlation between the domain vocabulary and the functions of the sub-domains. After that, perform domain modeling based on the sub-domains and the bounded context to obtain the domain model.

[0076] In this embodiment, according to the above domain model, different application stores can be uniformly split into multiple functional modules independent of specific application stores, thereby eliminating functional differences between different application stores. Each functional module is designed to focus on solving problems in a specific domain, improving the compatibility and interoperability of different application stores, enabling software developers to more easily publish applications to the application stores of multiple platforms without the need for separate adaptation for each application store, simplifying the management and maintenance of application stores, and greatly improving work efficiency. In addition, it also promotes resource sharing and knowledge transfer between application stores, accelerating the introduction and application of new technologies and new functions.

[0077] In some of these embodiments, after splitting the application store by function to obtain multiple functional interfaces, it includes:

[0078] Abstractly describe each of the functional interfaces to determine the name of each functional interface;

[0079] Set the call data when calling the functional interface, where the call data includes input parameters, output response information, interface protocol, and request path;

[0080] Encapsulate the call data into an interface document.

[0081] In this embodiment, for each functional interface, according to the functional description of the functional interface, a separate name is determined for each functional interface to facilitate the call between different functional interfaces. At the same time, a unified interface specification is designed for different functional interfaces, that is, an interface document is encapsulated for each functional interface. The call data such as input parameters, output response information, interface protocol, and request path of the functional interface are clearly defined in the interface document to ensure that standardized interaction can occur between different functional interfaces.

[0082] In this embodiment, the interface document builds a standardized communication bridge between the development team, the testing team, the operation and maintenance team, and possible third-party developers, ensuring that all relevant personnel can accurately understand the function and purpose of the interface, reducing misunderstandings and errors caused by poor communication, and thus promoting collaboration and cooperation among team members. In addition, the interface document provides detailed test basis for testers, and they can write test cases according to the description in the interface document to verify whether the function of the interface meets the expectations. At the same time, when the interface changes or needs to be maintained, the interface document is also an important reference material to help developers quickly locate problems and take corresponding solutions.

[0083] In a preferred embodiment, after abstractly describing each of the function interfaces, the business domain includes the application software domain, the app store domain, the submission and release domain, and the data domain. Among them, the application software domain includes a software information module, a software modification module, a software pull module, and a software addition module. The software information module includes the software information of all software in the app store. The software information includes the installation package hash value, software name, and software version number. By centrally managing the software information of all software in the app store, the accuracy and integrity of the software information are ensured. The software modification module is used to quickly and securely modify the information of the software in the app store, such as updating the software description, fixing the incorrect version number, etc., thereby enhancing the flexibility and response speed of the app store and being able to promptly reflect the latest status of the software. The software pull module is used to ensure the synchronization of local and remote data in software version control. Through an automated pulling mechanism, the errors and delays in manual synchronization are reduced, and the work efficiency is improved. The software addition module is used to add the software information of newly listed software in the app store, enabling new software to quickly and smoothly enter the app store. In addition, the app store domain includes a store information module, a store modification module, and a store pull module. The store information module is used to manage the store information of the app store itself, such as store name, LOGO, introduction, etc., enhancing the brand image and recognition of the app store. The store modification module is used to flexibly adjust the information of the app store to adapt to market changes or operational requirements. The submission and release domain includes a gray release module, a full release module, a pull module, an upload module, a submission module, and a release module. The gray release module tests newly listed software on a small scale, collects user feedback and evaluates the effects, reducing the risk of direct full release. The full release module is used to perform a full release after confirming that the new software or new function is stable and reliable, thereby enhancing the user experience and satisfaction. The pull sub-domain is used to synchronize the latest software version or configuration information during the release process to ensure that the released software is the latest version and the configuration is correct. The upload module is used to upload the software installation package to the app store. The submission module is used to conduct content review, version review, and technical review on the uploaded software installation package, thereby ensuring software quality, safeguarding user rights and interests, and promoting the healthy development of software. The release module is used to manage the release process of software, including review, packaging, deployment, etc. Through an automated release process, human errors and delays are reduced, and the release efficiency is improved. The data domain includes a financial data module and a quality data module. The financial data module is used to centrally manage the financial-related data in the app store, such as income, expenditure, cost, etc. The quality data module is used to collect and analyze data related to software quality, such as crash rate, user feedback, performance indicators, etc., which helps to discover problems existing in the software and repair them in a timely manner, improving software quality and user satisfaction.

[0084] S300. Invoke the function interface and encapsulate multiple function interfaces into a listing interface;

[0085] In some of these embodiments, the above step S300 includes:

[0086] When putting a software on an application store, according to the business requirements of software listing, analyze and determine one or more function interfaces to be called, obtain the call data required for calling all the function interfaces, and form a call list;

[0087] Analyze the call list, determine the dependency relationships and call sequences among the function interfaces, and form a call logic flowchart;

[0088] Based on the call logic flowchart and the call data of each of the function interfaces, encapsulate multiple function interfaces into one listing interface.

[0089] In this embodiment, according to the business requirements of software listing, analyze and determine the function interfaces to be called, store all the function interfaces in an interface list, traverse the interface list, for each function interface, obtain the call data when calling this function interface, and store the call data in a data dictionary, where the call data includes input parameters, output response information, interface protocol, and request path; generate a call list for software listing according to the interface list and the data dictionary.

[0090] In this embodiment, according to the business process of software listing, analyze the call list to determine the dependency relationships among the function interfaces. Specifically, traverse each function interface in the call list, for each function interface, analyze the source of its input parameters. If the input parameters come from the output of other function interfaces, establish a dependency relationship between the two interfaces and record the dependency direction. According to the established interface dependency relationships, use the topological sorting algorithm to generate a call sequence of the interfaces. The interfaces earlier in the sequence are called first, and the interfaces later in the sequence are called later. Obtain the business process description, through natural language processing technology, extract the key steps and judgment conditions in the business process, and map them to the corresponding interface calls. Combine the interface call sequence with the business process to generate a complete interface call logic flowchart. The above call logic flowchart includes interface nodes, judgment nodes, data flows, etc.

[0091] In this embodiment, by encapsulating the call logic flowchart and call information of multiple function interfaces related to software listing into one listing interface, software developers do not need to call these function interfaces one by one when implementing the listing function, but only need to call the encapsulated listing interface, thus simplifying the development process, reducing the amount of code, and improving the development efficiency.

[0092] In this embodiment, when encapsulating the on-shelf interface, mechanisms such as error handling and data verification can be built in to ensure that each functional interface can correctly handle abnormal situations during invocation, avoid error propagation and system crashes, thereby enhancing the stability and reliability of the system.

[0093] S400. Based on the on-shelf interface, create a store instance object, and based on the authorization information, call the store instance object to put the software on the application store.

[0094] In some of these embodiments, the creating a store instance object based on the on-shelf interface includes:

[0095] Obtain on-shelf data according to the on-shelf interface, where the on-shelf data is the data required to put the software on the application store;

[0096] Based on the on-shelf data, create a store instance object for the application store, where the store instance object is the software to be put on the shelf.

[0097] In this embodiment, when the application store obtains the authorization information, it calls the on-shelf interface, inputs the installation package and application information of the software to be put on the shelf, obtains the on-shelf data when the software to be put on the shelf, creates a store instance object, calls the initialization method of the store instance object, establishes a connection with the store system, completes the initialization process, and at the same time calls the store instance object to put the software on the corresponding application store.

[0098] In this embodiment, when receiving the installation package and software information of the software to be put on the shelf, the legality of the format and content of the received data is verified to ensure the integrity and correctness of the data. For the integrity verification of the installation package, the hash algorithm is used to calculate the hash value of the installation package, and the calculated hash value is compared with the hash value in the software information to determine whether the installation package is complete and not tampered with. For the software information, mandatory item verification is performed. According to the preset mandatory fields, such as the installation package hash value, software name, software version number, etc., it is judged one by one whether each mandatory field has a value. If there is a mandatory field that is empty, an error message is returned, prompting the user to complete the mandatory information and then submit. After the legality verification of the software installation package and software information, key information such as the software name and software version number is extracted from the software information, and a unique software identification code is generated in combination with the current timestamp. According to the software identification code, a storage directory for the software is created, and the software installation package is stored in this directory. At the same time, the storage path of the software is recorded and mapped to the software identification code. The basic information of the software, software identification code, storage path and other information are stored in the software information library corresponding to the software field, and the software is associated through the software identification code, which is convenient for subsequent software management and query. If the verification result is qualified, a response result of successful software upload is returned. Among them, the response result includes information such as the software identification code and access path, which is convenient for software developers to confirm the software upload result and perform subsequent software management and distribution operations.

[0099] In this embodiment, through this software shelf-listing method, the software to be put on the shelf can be listed on multiple application stores, thereby significantly improving the software release efficiency, reducing human errors, and lowering the operation cost.

[0100] Specifically, the above software shelf-listing method is applied to the game field. Among them, the application stores of games usually include Google Play, Samsung Galaxy Store, etc. The game software is listed on the corresponding application stores in sequence through the above method. The game software needs to be submitted for review regularly during use to ensure the game quality and protect the rights and interests of players. Therefore, in this embodiment, when it is necessary to submit the game software for review, the authorization information can be obtained through the above step S100 without logging in to the web background of the corresponding application store. In addition, by inputting the keyword of the name of the corresponding game software in the store configuration management module, the corresponding application store is obtained, and through the review submission module encapsulated in the application store, the upload and review of the game software are realized.

[0101] Please refer to Figure 2 As shown in the figure, the present invention also provides a software shelf-listing system based on an application store. The system includes:

[0102] A store authentication module 201: used to obtain the configuration information of the application store, and based on the configuration information, authenticate the application store to obtain authorization information;

[0103] Store abstraction module 202: used to split multiple said application stores according to functions to obtain multiple function interfaces;

[0104] Shelf interface encapsulation module 203: used to call the said function interfaces and encapsulate multiple said function interfaces into a shelf interface;

[0105] Software shelving module 204: used to create a store instance object based on the said shelf interface, and based on the said authorization information, call the said store instance object to shelve software to the said application store.

[0106] It can be understood that the content in the embodiment of the software shelving method based on the application store as Figure 1 shown is applicable to the embodiment of the software shelving system based on the application store. The functions specifically implemented by the embodiment of the software shelving system based on the application store are the same as those in the embodiment of the software shelving method based on the application store as Figure 1 shown, and the beneficial effects achieved are also the same as those in the embodiment of the software shelving method based on the application store as Figure 1 shown.

[0107] It should be noted that the content such as information interaction and execution process between the above systems, because it is based on the same concept as the method embodiment of the present invention, for its specific functions and the technical effects brought, please refer to the method embodiment part specifically, and will not be elaborated here.

[0108] Those skilled in the art can clearly understand that for the convenience and conciseness of description, only the above division of each functional unit and module is used as an example. In actual applications, the above functions can be allocated to different functional units and modules according to needs, that is, the internal structure of the said system is divided into different functional units or modules to complete all or part of the functions described above. Each functional unit and module in the embodiment can be integrated in a processing unit, or each unit can exist physically alone, or two or more units can be integrated in one unit. The above integrated unit can be implemented in the form of hardware or in the form of a software functional unit. In addition, the specific names of each functional unit and module are only for the convenience of mutual distinction and do not limit the protection scope of this application. The specific working process of the units and modules in the above system can refer to the corresponding process in the foregoing method embodiment and will not be elaborated here.

[0109] Please refer to Figure 3As shown in the figure, an embodiment of the present invention further provides a computer device 3, including: a memory 302, a processor 301, and a computer program 303 stored on the memory 302. When the computer program 303 is executed on the processor 301, it implements the software listing method based on the application store as described in any one of the above methods.

[0110] The computer device 3 may be a computing device such as a desktop computer, a notebook, a palm computer, and a cloud server. The computer device 3 may include, but is not limited to, a processor 301 and a memory 302. Those skilled in the art can understand that Figure 3 This is only an example of the computer device 3 and does not constitute a limitation on the computer device 3. It may include more or fewer components than shown in the figure, or combine some components, or different components. For example, it may also include input / output devices, network access devices, etc.

[0111] The so-called processor 301 may be a central processing unit (CPU). The processor 301 may also be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor, or the processor may also be any conventional processor, etc.

[0112] In some embodiments, the memory 302 may be an internal storage unit of the computer device 3, such as the hard disk or memory of the computer device 3. In other embodiments, the memory 302 may also be an external storage device of the computer device 3, such as a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card, etc. equipped on the computer device 3. Further, the memory 302 may also include both the internal storage unit and the external storage device of the computer device 3. The memory 302 is used to store an operating system, application programs, a boot loader, data, and other programs, such as the program code of the computer program. The memory 302 may also be used to temporarily store data that has been output or will be output.

[0113] An embodiment of the present invention also provides a computer-readable storage medium, on which a computer program is stored. When the computer program is run by a processor, it implements the software listing method based on an application store as described in any one of the above methods.

[0114] In this embodiment, if the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on such an understanding, to implement all or part of the processes in the above embodiment methods of the present application, a computer program can be used to instruct relevant hardware to complete. The computer program can be stored in a computer-readable storage medium. When the computer program is executed by a processor, it can implement the steps of the above various method embodiments. Among them, the computer program includes computer program code, and the computer program code can be in the form of source code, object code, executable file or some intermediate form, etc. The computer-readable medium can at least include: any entity or device that can carry the computer program code to the photographing device / terminal device, recording medium, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signal, telecommunication signal, and software distribution medium. For example, a USB flash drive, a mobile hard disk, a magnetic disk or an optical disc, etc. In some jurisdictions, according to legislation and patent practice, the computer-readable medium cannot be an electrical carrier signal and a telecommunication signal.

[0115] The above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit it; although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: they can still modify the technical solutions recorded in the foregoing embodiments, or perform equivalent replacements on some of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the various embodiments of the present application, and should all be included in the protection scope of the present application.

Claims

1. A method for putting software on shelves based on an application store, characterized in that: include: Obtaining configuration information of the application store, and authenticating the application store based on the configuration information to obtain authorization information; Splitting the multiple application stores according to their functions to obtain multiple functional interfaces; Calling the functional interface, and encapsulating a plurality of the functional interfaces into a shelf interface; Based on the listing interface, a store instance object is created, and based on the authorization information, the store instance object is called to list the software on the application store; The multiple application stores are split according to their functions to obtain multiple functional interfaces, including: Build a domain model based on the business logic of the application software; Based on the domain model, the application store is divided into different business domains, and each business domain is divided into business to form multiple subdomains, wherein the business domain includes the application software domain, the application store domain, the review and release domain, and the data domain, and each subdomain corresponds to a functional interface; The calling of the functional interface and encapsulating a plurality of the functional interfaces into a shelf interface include: When a software is put on an application store, one or more functional interfaces that need to be called are analyzed and determined according to the business requirements of the software, and the call data required for calling all the functional interfaces are obtained to form a call list; Analyze the call list, determine the dependency relationship and call sequence between the functional interfaces, and form a call logic flow chart; Based on the calling logic flow chart and the calling data of each of the functional interfaces, a plurality of the functional interfaces are encapsulated into a shelf interface.

2. The method according to claim 1, characterized in that The obtaining of configuration information of the application store includes: According to the name of the application store, a matching search is performed in a preset store configuration management module to obtain a target application store, wherein the store configuration management module includes configuration information of different application stores.

3. The method according to claim 1, characterized in that The configuration information includes authentication interface information and identity authentication information; The authenticating the application store based on the configuration information to obtain authorization information includes: Based on the authentication interface information, a connection relationship between the application store and a predefined authentication abstract interface is established to obtain authentication interface parameters; Encapsulate the authentication interface parameters and the identity authentication information to obtain authentication request parameters; Passing the authentication request parameters to the authentication interface of the application store, and initiating an authentication request to the authentication interface; Receiving response information from the authentication interface, parsing and verifying the response information, and obtaining an authentication result, wherein the response information includes authorization information; When the authentication result is successful, the authorization information is stored in a cache system.

4. The method according to claim 1, characterized in that After the application store is split according to functions and multiple functional interfaces are obtained, the following are included: Performing an abstract description on each of the functional interfaces and determining a name for each of the functional interfaces; Setting calling data when calling the functional interface, the calling data including input parameters, output response information, interface protocol and request path; The call data is encapsulated as an interface document.

5. The method according to claim 1, characterized in that The step of creating a store instance object based on the shelf interface includes: According to the shelf interface, obtain shelf data, the shelf data is the data required when the software is put on the shelf to the application store; Based on the listing data, a store instance object is created for the application store, where the store instance object is the software to be listed.

6. A software listing system based on an application store, characterized in that: include: Store authentication module: used to obtain configuration information of the application store, authenticate the application store based on the configuration information, and obtain authorization information; Store abstraction module: used to split the multiple application stores according to their functions and obtain multiple functional interfaces; The shelf interface encapsulation module is used to call the functional interface and encapsulate multiple functional interfaces into a shelf interface; Software listing module: used to create a store instance object based on the listing interface, and call the store instance object based on the authorization information to list the software on the application store; The multiple application stores are split according to their functions to obtain multiple functional interfaces, including: Build a domain model based on the business logic of the application software; Based on the domain model, the application store is divided into different business domains, and each business domain is divided into business to form multiple subdomains, wherein the business domain includes the application software domain, the application store domain, the review and release domain, and the data domain, and each subdomain corresponds to a functional interface; The calling of the functional interface and encapsulating a plurality of the functional interfaces into a shelf interface include: When a software is put on an application store, one or more functional interfaces that need to be called are analyzed and determined according to the business requirements of the software, and the call data required for calling all the functional interfaces are obtained to form a call list; Analyze the call list, determine the dependency relationship and call sequence between the functional interfaces, and form a call logic flow chart; Based on the calling logic flow chart and the calling data of each of the functional interfaces, a plurality of the functional interfaces are encapsulated into a shelf interface.

7. A terminal device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the method according to any one of claims 1 to 5 is implemented.

8. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the method according to any one of claims 1 to 5 is implemented.

Images