WO2024002222A1 - 应用管理方法及相关设备 - Google Patents

应用管理方法及相关设备 Download PDF

Info

Publication number
WO2024002222A1
WO2024002222A1 PCT/CN2023/103730 CN2023103730W WO2024002222A1 WO 2024002222 A1 WO2024002222 A1 WO 2024002222A1 CN 2023103730 W CN2023103730 W CN 2023103730W WO 2024002222 A1 WO2024002222 A1 WO 2024002222A1
Authority
WO
WIPO (PCT)
Prior art keywords
application
store
app
download
information
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2023/103730
Other languages
English (en)
French (fr)
Inventor
林伟
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Wellintech Co Ltd
Original Assignee
Beijing Wellintech Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Beijing Wellintech Co Ltd filed Critical Beijing Wellintech Co Ltd
Priority to US18/879,756 priority Critical patent/US20250390312A1/en
Priority to EP23830391.1A priority patent/EP4538869A4/en
Publication of WO2024002222A1 publication Critical patent/WO2024002222A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/70—Software maintenance or management
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/445—Program loading or initiating
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/61—Installation
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/70—Software maintenance or management
    • G06F8/71—Version control; Configuration management
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/445—Program loading or initiating
    • G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files

Definitions

  • This application relates to the field of software technology, and in particular, to an application management method and related equipment.
  • Application also called application, refers to a computer program that is used to complete one or more specific tasks. It can run in user mode and interact with users, and can have a visual user interface.
  • This application provides an application management method and related equipment, which can enable collaborative development between different application development organizations and improve development efficiency.
  • this application provides an application management method, the method is applied to an application store, and the application store at least includes a first application and a second application; the method includes: establishing an association relationship between the first application and the second application; The second application can call the first application to implement the functions of the first application.
  • the second application includes first information, and the first information is used to indicate the first application associated with the second application.
  • the first information includes the identification of the first application; the identifications of different applications in the application store are different.
  • the copyright owners of the first application and the second application are the same or different.
  • the developers of the first application and the second application are the same or different.
  • the present application provides an application management device, which is used in an application store.
  • the application store at least includes a first application and a second application.
  • the device can be used in an application store to implement the application management method described in the first aspect and any possible implementation manner of the first aspect.
  • the function of the device can be realized by hardware, or it can be realized by hardware executing corresponding software.
  • the hardware or software includes one or more of the components described in the first aspect and any possible implementation of the first aspect.
  • the module or unit corresponding to the steps in the application management method.
  • the device includes: an application management module, configured to establish an association between a first application and a second application; the second application can call the first application to implement the functions of the first application.
  • an application management module configured to establish an association between a first application and a second application
  • the second application can call the first application to implement the functions of the first application.
  • the second application includes first information, and the first information is used to indicate the first application associated with the second application.
  • the first information includes the identification of the first application; the identifications of different applications in the application store are different.
  • the copyright owners of the first application and the second application are the same or different.
  • the developers of the first application and the second application are the same or different.
  • the present application provides an electronic device.
  • the electronic device may be a hardware device corresponding to the application store described in the first aspect.
  • the electronic device includes: a processor, a memory used to store instructions executable by the processor; when the processor is configured to execute the instructions, the electronic device implements the first aspect and any possible implementation manner of the first aspect. method described.
  • the present application provides a computer-readable storage medium on which computer program instructions are stored; when the computer program instructions are executed by an electronic device, the electronic device enables the electronic device to implement any one of the first aspect and the first aspect. possible implementation methods.
  • the present application provides a computer program product, including computer readable code, or a non-volatile computer readable storage medium carrying the computer readable code, when the computer readable code is run in an electronic device , the processor in the electronic device implements the method described in the first aspect and any possible implementation manner of the first aspect.
  • the present application provides an application management method.
  • the method includes: obtaining a first application from an application store; generating a second application based on the first application; and the second application has an associated relationship with the first application and can call the second application.
  • One application is used to realize the functions of the first application; the second application is put on the application store.
  • the second application includes first information, and the first information is used to indicate the first application associated with the second application.
  • the first information includes an identifier of the first application.
  • the copyright owners of the first application and the second application are the same or different.
  • the developers of the first application and the second application are the same or different.
  • the present application provides an application management device, which can be used to implement the application management method described in the sixth aspect and any possible implementation manner of the sixth aspect.
  • the function of the device can be realized by hardware, or it can be realized by hardware executing corresponding software.
  • the hardware or software includes one or more applications described in the sixth aspect and any possible implementation manner of the sixth aspect. Use the modules or units corresponding to the steps in the management method.
  • the device includes: an acquisition module, used to obtain a first application from an application store; a generation module, used to generate a second application according to the first application; the second application has an associated relationship with the first application and can call the first application.
  • the application is used to realize the functions of the first application; the listing module is used to put the second application on the application store.
  • the second application includes first information, and the first information is used to indicate the first application associated with the second application.
  • the first information includes an identifier of the first application.
  • the copyright owners of the first application and the second application are the same or different.
  • the developers of the first application and the second application are the same or different.
  • the present application provides an electronic device, including: a processor, a memory used to store instructions executable by the processor; when the processor is configured to execute the instructions, the electronic device implements the sixth aspect and the sixth aspect. Any possible implementation of the method described in this aspect.
  • the present application provides a computer-readable storage medium on which computer program instructions are stored; when the computer program instructions are executed by an electronic device, the electronic device enables the electronic device to implement any one of the sixth aspect and the sixth aspect. possible implementation methods.
  • the present application provides a computer program product, including computer readable code, or a non-volatile computer readable storage medium carrying the computer readable code, when the computer readable code is run in an electronic device , the processor in the electronic device implements the method described in the sixth aspect and any possible implementation manner of the sixth aspect.
  • the present application provides an application management method, which method includes: receiving a first download request, the first download request being used to request to download a second application in the application store; the second application and the third application in the application store.
  • An application has an association relationship and can call the first application to realize the function of the first application; in response to the first download request, the second application and the first application are sent.
  • the second application includes first information, and the first information is used to indicate the first application associated with the second application.
  • the first information includes the identification of the first application; the identifications of different applications in the application store are different.
  • the method further includes: receiving a second download request, the second download request being used to request to download the first application in the application store; in response to the second download request, sending the first application, wherein the first application uses To generate the second application.
  • the method further includes: receiving a second application listed in the application store, where the second application is generated based on the first application downloaded from the application store.
  • the present application provides an application management device, which can be used to implement the application management method described in the eleventh aspect and any possible implementation manner of the eleventh aspect.
  • the function of the device can be realized by hardware, or it can be realized by hardware executing corresponding software.
  • the hardware or software includes one or more modules or units corresponding to the steps in the application management method described in the eleventh aspect and any possible implementation manner of the eleventh aspect.
  • the device includes: a receiving module, configured to receive a first download request, the first download request being used to request to download a second application in the application store; the second application has an association relationship with the first application in the application store, and can The first application is called to implement the function of the first application; the sending module is configured to send the second application and the first application in response to the first download request.
  • a receiving module configured to receive a first download request, the first download request being used to request to download a second application in the application store
  • the second application has an association relationship with the first application in the application store, and can
  • the first application is called to implement the function of the first application
  • the sending module is configured to send the second application and the first application in response to the first download request.
  • the second application includes first information, and the first information is used to indicate the first application associated with the second application.
  • the first information includes the identification of the first application; the identifications of different applications in the application store are different.
  • the receiving module is also configured to receive a second download request, and the second download request is used to request to download the first application in the application store; the sending module is also configured to respond to the second download request, sending the first application, Wherein, the first application is used to generate the second application.
  • the receiving module is also configured to receive a second application listed in the application store, where the second application is generated based on the first application downloaded from the application store.
  • the present application provides an electronic device, including: a processor, a memory used to store instructions executable by the processor; when the processor is configured to execute the instructions, the electronic device implements the following aspects as described in the eleventh aspect and The method described in any possible implementation manner of the eleventh aspect.
  • the present application provides a computer-readable storage medium on which computer program instructions are stored; when the computer program instructions are executed by an electronic device, the electronic device implements the eleventh aspect and the eleventh aspect any possible implementation method.
  • the present application provides a computer program product, including a computer readable code, or a non-volatile computer readable storage medium carrying the computer readable code, when the computer readable code is run in an electronic device At this time, the processor in the electronic device implements the method described in the eleventh aspect and any possible implementation manner of the eleventh aspect.
  • this application provides an application management method, which can be applied to user equipment.
  • the method includes: sending a first download request, the first download request being used to request to download a second application in the application store; the second application has an association relationship with the first application in the application store and can call the first application to implement the second application.
  • the function of one application receiving the second application and the first application.
  • the second application includes first information, and the first information is used to indicate the connection with the second application.
  • the first application associated with the application.
  • the first information includes an identifier of the first application.
  • the copyright owners of the first application and the second application are the same or different.
  • the developers of the first application and the second application are the same or different.
  • this application provides an application management device, which can be used to implement the application management method described in any of the sixteenth aspects and any possible implementation manner of the sixteenth aspect.
  • the function of the device can be realized by hardware, or it can be realized by hardware executing corresponding software.
  • the hardware or software includes one or more modules or units corresponding to the steps in the application management method described in the sixteenth aspect and any possible implementation manner of the sixteenth aspect.
  • the device includes: a sending module, used to send a first download request, the first download request is used to request to download a second application in the application store; the second application has an association relationship with the first application in the application store, and can The first application is called to realize the function of the first application; the receiving module is used to receive the second application and the first application.
  • the second application includes first information, and the first information is used to indicate the first application associated with the second application.
  • the first information includes an identifier of the first application.
  • the copyright owners of the first application and the second application are the same or different.
  • the developers of the first application and the second application are the same or different.
  • the present application provides an electronic device, including: a processor, a memory used to store instructions executable by the processor; when the processor is configured to execute the instructions, the electronic device implements the sixteenth aspect and The method described in any possible implementation manner of the sixteenth aspect.
  • the present application provides a computer-readable storage medium on which computer program instructions are stored; when the computer program instructions are executed by an electronic device, the electronic device implements the sixteenth aspect and the sixteenth aspect any possible implementation method.
  • the present application provides a computer program product, including computer readable code, or a non-volatile computer readable storage medium carrying the computer readable code, when the computer readable code is run in an electronic device At this time, the processor in the electronic device implements the method described in the sixteenth aspect and any possible implementation manner of the sixteenth aspect.
  • this application at least has the following beneficial effects:
  • the second application has an associated relationship with the first application in the application store, can call the first application to realize the functions of the first application, and can realize that the second application and the first application are stored separately and independently.
  • This decentralized and independent storage relationship can effectively save the storage space occupied by applications in the app store. Reserve resources.
  • the second application has an associated relationship with the first application in the application store and can call the first application to realize the functions of the first application. It also enables collaborative development between development organizations of different applications to improve development efficiency.
  • Figure 1 is a schematic flow chart of an application management method provided by an embodiment of the present application.
  • FIG. 2 is another schematic flowchart of an application management method provided by an embodiment of the present application.
  • Figure 3 is a schematic diagram of the model and predefined relationships provided by the embodiment of this application.
  • Figure 4 is a schematic diagram of the data model provided by the embodiment of the present application.
  • Figure 5 is a schematic diagram of the composition of the APP model of the second application provided by the embodiment of the present application.
  • Figure 6 is another schematic flow chart of the application management method provided by the embodiment of the present application.
  • Figure 7 is another schematic flow chart of the application management method provided by the embodiment of the present application.
  • Figure 8 is a schematic diagram of the composition of an application management system provided by an embodiment of the present application.
  • Figure 9 is a schematic structural diagram of an application management device provided by an embodiment of the present application.
  • Figure 10 is another schematic structural diagram of an application management device provided by an embodiment of the present application.
  • Figure 11 is another structural schematic diagram of an application management device provided by an embodiment of the present application.
  • Figure 12 is another schematic structural diagram of an application management device provided by an embodiment of the present application.
  • a and/or B can mean: A exists alone, A and B exist simultaneously, and B exists alone.
  • the character “/” generally indicates that the related objects are in an "or” relationship.
  • Application also called application, refers to a computer program that is used to complete one or more specific tasks. It can run in user mode and interact with users, and can have a visual user interface.
  • the application store can be implemented on hardware devices such as servers and computers, and can also provide users with an interactive application store interface for users to download the applications they need.
  • an industrial Internet platform can be built based on hardware devices such as servers and computers.
  • the industrial Internet platform is the aforementioned application store.
  • Application developers can put the developed applications on the Industrial Internet platform, and users who need to use the applications can download and use the applications from the Industrial Internet platform.
  • embodiments of the present application provide an application management method, which can be applied to application stores. Through this method, collaborative development can be achieved between development organizations of different applications, improve development efficiency, and effectively save the space occupied by applications.
  • the storage resources of the application store are used to store collaborative development.
  • the method may be implemented on a hardware device corresponding to the application store.
  • the hardware device may include a server, a computer, etc.
  • the server may be a single server, or it may be a server cluster composed of multiple servers. In some implementations, the server cluster may also be a distributed cluster.
  • This application does not limit the specific implementation of the hardware devices corresponding to the application store. It should be noted that the implementation steps on the application store side involved in the embodiments of this application can all be implemented by hardware devices corresponding to the application store.
  • FIG. 1 is a schematic flowchart of an application management method provided by an embodiment of the present application. As shown in Figure 1, the application management method may include:
  • the application store may include at least a first application and a second application.
  • the first application and the second application may be put on the application store by their respective developers or copyright holders.
  • the second application can call the first application to implement the functions of the first application.
  • the second application does not include the code for implementing the first function, and the first function can also be implemented by calling the first application.
  • the application store can deliver the second application and the first application together.
  • the user can use the user device (such as a mobile phone, computer, etc.) to send a request to download the second application to the application store.
  • the application store may respond to the request and deliver the second application to the user device.
  • the application store may deliver a third application to the user device based on the association relationship.
  • One application When the user device runs the downloaded second application, the second application can call the downloaded first application to implement the functions of the first application.
  • the first application can be considered as a sub-application of the second application, but the code of the first application is independent of the second application. That is, in the application store, the second application and the first application are stored separately and independently. This relationship of decentralized and independent storage can effectively save the storage resources of the app store occupied by the application.
  • development organization 1 wants to develop an application that can realize function 1 and function 2
  • development organization 2 wants to develop an application that can realize function 2.
  • development organization 1 needs to develop an independent application 1 to implement function 1 and function 2, and put application 1 on the app store
  • development organization 2 needs to develop an independent application 2 to implement function 2, and put application 2 on the shelves.
  • the storage resources of the app store occupied by Application 1 and Application 2 at least include: resources occupied by the code used to implement Function 1 in Application 1, resources occupied by the code used in Application 1 to implement Function 2, and The resources occupied by the code used to implement function 2 in application 2.
  • application 2 can be equivalent to the first application to implement function 2
  • application 1 can be equivalent to the second application to implement function 1
  • application 1 can call application 2 to implement function 2.
  • Application 2 can provide an interface that can call Application 1.
  • the storage resources of the application store occupied by Application 1 and Application 2 include: resources occupied by the code used to implement Function 1 in Application 1, and resources occupied by the code used in Application 2 to implement Function 2.
  • Application 1 calls Application 2 to implement Function 2, which saves resources occupied by the code used to implement Function 2 in Application 1.
  • the application store also includes application 3 that can call application 2 to implement function 2, the effect of saving the storage resources of the application store occupied by the application is more significant.
  • the application The store can deliver the second application and the first application together, so it will not affect the normal use of the application on the user's device side.
  • the application management method provided by the embodiment of the present application can also enable collaborative development between different application development organizations and improve development efficiency.
  • development organization 1 takes the above-mentioned development organization 1 to develop an application that can realize function 1 and function 2, and development organization 2 to develop an application that can realize function 2.
  • Development organization 2 can develop an application 2 that can realize function 2.
  • Development organization 1 can develop an application 1 that can implement function 1 and call application 2.
  • Collaborative development has been achieved between development organization 1 and development organization 2, and the development efficiency of development organization 1 can be higher.
  • development organization 2 can put application 2 on the application store, and development organization 1 can download application 2 from the application store and develop application 1 based on application 2.
  • the relevant interface that can call Application 2 can be implemented in Application 1 based on Application 2.
  • the following is an exemplary description of an implementation method for establishing an association relationship between the first application and the second application.
  • the second application may include first information, and the first information is used to indicate the first application associated with the second application.
  • the application store establishing an association relationship between the first application and the second application may include: establishing an association relationship between the first application and the second application based on the first information included in the second application; or, integrating the first application information included in the second application. One piece of information serves as the association relationship between the first application and the second application.
  • the developer of the second application can add the identification of the first application to the second application, or add some fields that can indicate the first application.
  • the identifier of the first application or a field that can indicate the first application is the above-mentioned first information. That is, the first information may include: an identifier of the first application or some fields that can indicate the first application.
  • the application store side may maintain a link between the second application and the first application based on the identification of the first application included in the second application or a field that can indicate the first application.
  • the association relationship table is used to establish the association relationship between the first application and the second application.
  • the association table may include an identifier of the second application, an identifier of the first application corresponding to the identifier of the second application, or a field that can indicate the first application.
  • the application store can determine which application is the first application by querying the association relationship between the first application and the second application (such as an association relationship table), and combine the second application with the first application. Deliver.
  • the application store side may directly use the identification of the first application included in the second application or a field that can indicate the first application as the first application. and the association relationship with the second application.
  • the application store can determine which application is the first application by querying the identifier of the first application included in the second application or a field that can indicate the first application, and combine the second application with the first application. The application is delivered together.
  • embodiments of the present application also provide an application management method, which can be used to develop and generate a second application that is associated with a first application.
  • the developers of the first application and the second application are the same.
  • the developer can develop the first application locally, generate the second application based on the development of the first application, and then put the first application and the second application on the shelves. to the app store.
  • the developers of the first application and the second application are different.
  • the application store may include the first application.
  • the developer may obtain the first application from the application store and develop and generate the second application based on the first application. , and then put the second application on the app store.
  • the following is an exemplary description in which a developer obtains a first application from an application store and develops and generates a second application based on the first application.
  • FIG 2 is another schematic flowchart of an application management method provided by an embodiment of the present application. As shown in Figure 2, the application management method includes:
  • the device on the development side sends a request to download the first application to the application store.
  • the equipment on the development side may include servers, computers, etc. used by developers.
  • the application store sends the first application to the device on the development side.
  • the request to download the first application may include an identifier of the first application, and the application store may find the stored first application based on the identifier of the first application and deliver it to the device on the development side.
  • the device on the development side can obtain the first application from the application store.
  • the second application has an associated relationship with the first application and can call the first application to realize the functions of the first application.
  • a developer can develop a second application and add an interface capable of calling the first application in the second application, so that the second application can call the first application to implement the functions of the first application.
  • the device on the development side puts the second application on the application store.
  • the copyright owners of the first application and the second application may be the same or different, and the developers of the first application and the second application may also be the same or different.
  • the developer of the first application is development organization 1, and the developer of the second application is development organization 2, but the copyright owners of the first application and the second application are both unit A.
  • the developer of the first application is the Development Organization 1
  • the copyright owner is Unit A
  • the developer of the second application is Development Organization 2
  • the copyright owners are both Unit B.
  • the copyright owner of the first application is unit A
  • the copyright owners of the second application are both unit B, but the developers of the first application and the second application are both development organization 1.
  • the first application and the second application may be put on the application store by their respective copyright owners, or may be put on the application store by their respective developers, which is not limited here.
  • the device on the side of the copyright owner of the second application may also put the second application on the application store.
  • the application store may include the developer information and copyright owner information corresponding to each application, such as: the developer's team name, the copyright owner's unit name, address, etc.
  • the process of generating the second application based on the first application may be as follows:
  • the data predefinition of the second application is predefined and assigned a unique identifier (such as a globally unique identifier); among them, the system warehouse of the second application is also the system warehouse used by the developer who develops the second application.
  • the system warehouse of the second application is the same as the second application.
  • the developer's development studio can be connected via the network.
  • a model is information that describes the structure of an object when modeling abstraction.
  • Predefinition is information that determines the model of the structure and is configured with parameters.
  • the predefinition records the model information, and the predefinition is used to instantiate the object.
  • the instantiated object constructs the structure of the object according to the structure of its model, and uses the parameter value as the initial value of the object.
  • Predefinitions can also be referenced by other models as subpredefinitions.
  • operations can include: creating a new model, assigning names and identifiers; adding members, specifying member types; deleting members; adding or deleting sub-predefined; setting the initial value of sub-predefined; updating the model version; publishing a certain Model version generation predefined, etc.
  • operations can include: specifying a model version to publish (create) the predefinition; assigning a name and identity; setting predefined parameter values (attributes and members), etc.
  • Figure 3 is a schematic diagram of the model and predefined relationships provided by the embodiment of the present application.
  • the model can include basic attributes and member lists; basic attributes can include name, description, globally unique identifier (GUID), version, etc. Information; the member list can include: "Member 1: Name + Type", “Member 2: Name + Type”, “Member 3: Name + Type” and other information.
  • Predefinition can include basic attributes and member lists; basic attributes can include name, description, GUID, model GUID+version and other information; member lists can include: “Member 1+value”, “Member 2+value”, “Member 3+value” " and other information.
  • the data model described in step 2) is a concept in the spatiotemporal database, which describes the structure of the data objects in the spatiotemporal database and is an abstract description of the objects in the objective world.
  • FIG. 4 is a schematic diagram of the data model provided by the embodiment of the present application.
  • the data model may include: basic attributes, member lists, and sub-model lists.
  • a data model with sub-models is a composite data model.
  • data model A in the figure is a composite data model
  • data model B and data model C are sub-models of data model A.
  • the submodel list records the predefined identification of the data that refers to the data model of the submodel, establishing the dependency relationship between the submodel and the data model.
  • the submodel list of data model A includes data model B and data model C.
  • the predefined identification of the data such as: "name B1+referenced model ID+parameter value”, "name B2+referenced model ID+parameter value”, "name C3+referenced model ID+parameter value”, etc.
  • motor equipment has parameters such as speed, temperature, and current.
  • Establish a data model of the motor equipment The data model of the motor equipment can include members of speed, temperature, and current.
  • the data model of the motor equipment can uniformly describe similar motors.
  • the compressor workshop has a fixed plate production line, a static plate production line, and a final assembly line, and establish a data model of the compressor workshop.
  • the data model of the compressor workshop can include sub-models: fixed plate production line, static plate production line, Assembly production line, etc.
  • the data model of a compressor shop can describe similar compressor shop models.
  • the resource object that the APP model of the second application depends on (referred to as the resource object of the second application) to the resource library, and assign a unique identifier (such as a globally unique identifier) to the resource object of the second application.
  • the resource object is a concept in the spatiotemporal database.
  • the binary file data is organized and managed in an object-oriented manner, and an identifier is assigned to each resource object.
  • the APP model of the second application can access the data of the resource object through the identifier of the resource object.
  • an icon is defined as a resource object and forms a dependency relationship with the APP model of the second application
  • the APP model of the second application can use this icon.
  • define a video file as a resource A dependency relationship is formed between the object and the APP model of the second application, and the APP model of the second application can read the video file for playback through the dependency relationship.
  • the predefined data in the system warehouse of the second application may be built by the developer itself, or may be purchased from an application store.
  • the resource objects in the resource library can be built by the developer or purchased from the application store.
  • Add the sub-APP list of the APP model of the second application select the pre-definition of the first application as a sub-APP from the system warehouse of the second application, and record the pre-defined identification of the first application in the APP of the second application on the model's sub-APP list.
  • the predefinition of the first application is the first application obtained from the application store in S201-S202.
  • the predefined identification of the first application is the identification of the first application described in the previous embodiment.
  • the predefinition of the first application may be uploaded to the application store by the copyright owner or developer of the first application.
  • the predefined identification of the second application is the identification of the second application.
  • predefined parameter values such as attributes and members.
  • FIG. 5 is a schematic diagram of the composition of the APP model of the second application provided by the embodiment of the present application.
  • the APP model of the second application may include: basic attributes, dependent data list, function function list, and sub-APP list.
  • Basic attributes may include: name, description, and GUID (ie, the unique identifier of the APP model of the second application).
  • the dependent data list records the data models or resource objects that the APP model of the second application needs to use, and establishes a relationship between the APP model of the second application and the dependent data models or resource objects.
  • Data 2: Data ID represent the predefined identification of the data of the dependent data model or the identification of the resource object.
  • the dependent data list may include the above-mentioned predefined list of dependent data and/or the above-mentioned dependent resource list.
  • the functional function list may include: Function 1, Function 2 and other functional functions of the APP model of the second application. These functional functions are the implementation of the program logic of the APP model of the second application.
  • the sub-APP list records the information of the first application and the association relationship established between the APP model of the second application and the first application.
  • the sub-APP list may include the identification and configuration parameters of the first applications such as sub-APP-B1, APP-C2, APP-D3, etc. That is, APP model B, APP model C, and APP model D, etc. may be the above-mentioned first application.
  • the second application can be generated according to the first application in S203.
  • the development process of the first application is similar to the development process of the second application.
  • the development process of the first application does not include steps similar to step 6) above. the process described.
  • the development process of the first application is consistent with the process described in steps 1) to 8) above. The development process of the first application will not be described in detail here.
  • the second application and the first application may depend on the same predefined data or resource object, because the dependency relationship is established when the second application and the first application are developed separately.
  • the second application The identifier of the same data predefinition or resource object may be recorded in the dependency data list of the first application.
  • the process of the copyright owner of the second application putting the second application on the app store is as follows:
  • the copyright owner of the second application creates an APP product for the second application in the app store.
  • the APP product for the second application includes a predefined identification of the second application.
  • APP products refer to the corresponding information established for the predefinition of APP in the application store, and mainly describe the predefined commercialization information of APP.
  • the APP product of the second application may also include the second application's pattern (logo), video, product pricing, product name, product description, etc.
  • the application store determines the predefined content of the second application corresponding to the APP product of the second application based on the registered account of the copyright owner of the second application in the application store (or the system product code of the copyright owner of the second application).
  • the system repository belonging to the secondary application That is, the application store can determine which system warehouse the predefinition of the second application corresponding to the APP product of the second application comes from based on the registered account of the copyright owner of the second application in the application store.
  • the application store requests the system warehouse of the second application to list the predefinition of the second application based on the predefined identification of the second application included in the APP product of the second application.
  • the system warehouse of the second application responds to the predefined request from the application store to list the second application, and executes the following steps (4.1) to step (4.2):
  • the system warehouse of the second application uploads the predefinition of the second application to the application store.
  • the predefinition of the second application may include the APP model and configuration parameters of the second application.
  • the system warehouse of the second application uploads the data predefinition and resource objects of the second application to the application store based on the dependent data predefined list and dependent resource list of the second application.
  • the second application can be put on the application store in S204.
  • the system warehouse of the second application can also upload the second application to the application store. Predefine the associated local sub-APP, and upload the local sub-APP's data predefinition and resource objects to the app store based on the local sub-APP's dependent data predefined list and dependent resource list.
  • the system warehouse of the second application since the data related to the first application already exists in the application store, the system warehouse of the second application does not need to upload the data related to the first application to the application store, such as: the predefined, An application's data predefinition and resource objects, etc. Therefore, only one copy of data related to the first application is included in the application store, achieving the effect of saving storage resources of the application store as described in the foregoing embodiments.
  • the above embodiments mainly introduce the application management method provided by the embodiments of the present application from the perspective of application store management and application development on the development side.
  • the application store can deliver the second application and the first application together.
  • embodiments of the present application also provide an application management method that can be applied on the app store side.
  • the method may include: receiving a first download request, the first download request being used to request to download a second application in the application store; the second application has an association relationship with the first application in the application store and can call the first application to implement the second application. Functions of an application; in response to the first download request, sending the second application and the first application.
  • the application management method will be described below by taking the user device sending the first download request to the application store as an example.
  • the user equipment can be a mobile phone, a computer, etc.
  • FIG. 6 is another schematic flowchart of an application management method provided by an embodiment of the present application.
  • the application management method includes:
  • the user device sends a first download request to the application store.
  • the first download request is used to request to download the second application in the application store.
  • the application store receives the first download request.
  • the application store sends the second application and the first application to the user device in response to the first download request.
  • the first download request may include an identifier of the second application, and the identifier of the second application is used to indicate downloading the second application.
  • the application store may determine the first application based on the association between the second application and the first application, and deliver the first application and the second application together to the user device. For example, the application store may determine which application is the first application based on the identification of the first application included in the second application, and deliver the second application and the first application together.
  • the application store can also receive a second download request, and the second download request is used to request to download the application store the first application in; and in response to the second download request, sending the first application, wherein the first application is used to generate the second application.
  • the application store may also receive a second application listed in the application store, and the second application is generated based on the first application downloaded from the application store.
  • the application management method will be described by taking the device on the development side of the second application (referred to as the device on the development side) sending a second download request to the application store as an example.
  • FIG. 7 is another schematic flowchart of an application management method provided by an embodiment of the present application.
  • the application management method includes:
  • the device on the development side sends a second download request to the application store.
  • the second download request is used to request to download the first application in the application store.
  • the application store receives the second download request.
  • the application store sends the first application to the device on the development side.
  • the first application is used to generate the second application.
  • the device on the development side can generate a second application based on the first application.
  • the device on the development side can generate a second application based on the first application.
  • the device on the development side puts the second application in the application store.
  • the user device sends a first download request to the application store.
  • the first download request is used to request to download the second application in the application store.
  • the application store receives the first download request.
  • the application store sends the second application and the first application to the user device in response to the first download request.
  • S704-S705 can refer to S601-S602 and will not be described again.
  • the second application may be called a finished APP
  • a sub-APP of the second application (such as The first application) can be called Parts APP.
  • the finished APP can be a program that can run independently.
  • the parts APP can be an APP program that can run independently, or it can be a program that does not run independently.
  • a parts APP can serve as a sub-APP of one or more finished products APPs and be called by the finished products APP to realize the functions of the parts APP.
  • parts APP and finished product APP are relative concepts, and applications that are sub-APPs can be considered part APPs.
  • the third application is the finished product APP and the second application is the parts APP.
  • FIG 8 is a schematic diagram of the composition of an application management system provided by an embodiment of the present application. As shown in Figure 8, development system warehouse 1, development system warehouse 2, application store, and consumer warehouse can form an application management system.
  • the development system warehouse 1 may be a system warehouse used to develop parts APP (such as the above-mentioned first application).
  • the developer of the parts APP can develop the parts APP in the development system warehouse 1 and put the parts APP on the application store.
  • the parts APP can include a predefined list of dependent data and a list of dependent resources.
  • the dependent data predefined list establishes the dependency relationship between the parts APP and data model 4 (predefined) and data model 5 (predefined).
  • the dependent resource list establishes the dependency relationship between the parts APP and resource data 4.
  • the development system warehouse 2 may be a system warehouse used to develop a finished APP (such as the above-mentioned second application).
  • the developer of the finished APP can download the part APP from the application store to the development system warehouse 2, develop the finished APP in the development system warehouse 2 based on the part APP, and put the finished APP on the application store.
  • the finished APP can include a predefined list of dependent data and a list of dependent resources.
  • the dependent data predefined list establishes the dependency relationship between the finished APP and data model 1 (predefined), data model 2 (predefined), and data model 3 (predefined).
  • the dependent resource list establishes the dependency relationship between the finished APP and resource data 1, resource data 2, and resource data 3.
  • the finished product APP and the parts APP have established an association, and can call the parts APP to realize the functions of the parts APP.
  • the consumer warehouse may be a warehouse on the consumer (user) side of the second application. Consumers can use the user device to download the finished APP from the app store to the consumer warehouse. When a consumer uses a user device to download a finished APP from the app store, the app store can deliver both the finished APP and the parts APP to the consumer warehouse.
  • the process of consumers downloading the finished APP from the application store may include: 1) The consumer executes the instruction to download the finished APP through the user device in the interactive interface provided by the application store, triggering the user device to send the instruction to download the finished APP to the application store.
  • Requests to download the finished APP can be Specify the name of the finished APP (for example, include the logo of the finished APP). 2)
  • the App Store delivers the predefined APP to the consumer warehouse based on the name of the finished APP specified in the request to download the finished APP. 3)
  • the application store finds the predefined data and resource data that the finished APP depends on based on the predefined dependency data predefined list and dependent resource list of the finished APP and delivers them to the consumer warehouse.
  • the application store delivers the predefined parts APP to the consumer warehouse based on the identification of the part APP included in the finished product APP (such as querying the sub-APP list of the finished product APP).
  • the application store finds the predefined data and resource data that the parts APP depends on based on the predefined dependency data predefined list and dependent resource list of the parts APP and delivers them to the consumer warehouse.
  • development system warehouse 1 and development system warehouse 2 may be part of the APP development system, and the APP development system may also include a developer studio.
  • Developer Studio refers to a system for developers to edit APP models, and can create, edit, publish and other APP model management operations.
  • the development system warehouse is a predefined system that stores APP models developed by developers and released into APPs.
  • the consumer warehouse can be part of the consumer application system, and the consumer application system can also include an APP running environment and an APP operation and maintenance system.
  • the consumer application system refers to the business application system of an independent manufacturing enterprise. The manufacturing enterprise completes business activities on the system and is responsible for maintaining the business application system.
  • the consumer warehouse is a system that stores predefined apps purchased by consumers.
  • the APP operation and maintenance system is a system for consumers to operate and maintain APPs.
  • the APP running environment is the environment system for running the APP.
  • the finished product APP predefinition can create an APP running instance, specify the running environment (computer node), and allocate computer resources (such as central processing unit (CPU), memory, network bandwidth, etc.).
  • the APP running instance has the predefined identification of the APP.
  • the APP operation and maintenance system can deploy the functional logic of the APP's predefined APP model (the predefined APP carries the APP model's identification) to the designated computer node based on the predefined identification of the APP on the APP running instance.
  • the APP operation and maintenance system, consumer warehouse, and APP operating environment complete the deployment process of APP program files through network communication. After completing the deployment, you can start the operation of the APP instance and start executing the functional function logic of the APP instance.
  • the application store may include a store system consisting of a store system and a transaction system.
  • This store system can serve as a commodity trading and circulation system operated by the operator of the application store.
  • APP software development companies i.e. developers
  • production companies i.e. consumers
  • the store system can include one or more stores, which are used to store APP products on the shelves and are responsible for the listing, downloading, and authorization key distribution of APPs.
  • the trading system can realize functions such as order management and payment management.
  • Parts APP can be called by one or more finished APPs to realize the functions of the parts APP, which enables the parts APP to be reused between different development organizations.
  • Parts APP can be adopted by more development organizations, the value of Parts APP is amplified, and the value of Parts APP developers is also amplified, which can increase the enthusiasm of APP developers.
  • finished APPs and parts APPs are stored decentrally in the app store, which can ensure that there is no redundant data and save the storage resources of the app store occupied by the APP.
  • the application store, development side equipment, user equipment, etc. described in the embodiments of the present application may include one or more hardware structures and/or software modules for implementing the corresponding application management methods mentioned above.
  • these execution hardware structures and/or software modules may constitute an electronic device.
  • the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is performed by hardware or computer software driving the hardware depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each specific application, but such implementations should not be considered beyond the scope of this application.
  • FIG. 9 is a schematic structural diagram of an application management device provided by an embodiment of the present application.
  • the application management device may include: an acquisition module 901, configured to acquire a first application and a second application.
  • the application management module 902 is used to establish an association between the first application and the second application.
  • the second application can call the first application to implement the functions of the first application.
  • FIG 10 is another schematic structural diagram of an application management device provided by an embodiment of the present application.
  • the application management device may include: an acquisition module 1001, configured to acquire a first application from an application store.
  • Generating module 1002 configured to generate a second application according to the first application.
  • the second application has an associated relationship with the first application and can call the first application to implement the functions of the first application.
  • the listing module 1003 is used to put the second application on the application store.
  • FIG 11 is another schematic structural diagram of an application management device provided by an embodiment of the present application.
  • the application management device may include: a receiving module 1101, configured to receive the first download request.
  • the download request is used to request to download a second application in the app store.
  • the second application has an associated relationship with the first application in the application store and can call the first application to realize the functions of the first application.
  • the sending module 1102 is configured to send the second application and the first application in response to the first download request.
  • the receiving module 1101 is also configured to receive a second download request, and the second download request is used to request to download the first application in the application store.
  • the sending module 1102 is also configured to send the first application in response to the second download request. Wherein, the first application is used to generate the second application.
  • the receiving module 1101 is also configured to receive a second application listed in the application store, where the second application is generated based on the first application downloaded from the application store.
  • FIG 12 is another schematic structural diagram of an application management device provided by an embodiment of the present application.
  • the application management device may include: a sending module 1201, used to send a first download request, and the first download request is used to request to download a second application in the application store.
  • the second application has an associated relationship with the first application in the application store and can call the first application to realize the functions of the first application.
  • the receiving module 1202 is used to receive the second application and the first application.
  • the embodiment of the present application can divide each execution subject involved in the application management method into functional modules according to the above method example.
  • the above integrated modules can be implemented in the form of hardware or software function modules.
  • the division of modules in the embodiment of the present application is schematic and is only a logical function division. In actual implementation, there may be other division methods.
  • each functional module can be divided corresponding to each function, or two or more functions can be integrated into one processing module.
  • An embodiment of the present application also provides an electronic device, which may be a hardware device corresponding to an application store, a device on the development side, or the above-mentioned user device.
  • the electronic device includes: a processor, a memory used to store instructions executable by the processor; when the processor is configured to execute the instructions, the electronic device implements the method as described in the previous embodiment.
  • embodiments of the present application also provide a computer-readable storage medium on which computer program instructions are stored; when the computer program instructions are executed by an electronic device, the electronic device implements the implementation as described in the foregoing embodiments. method described.
  • the above-mentioned computer-readable storage medium may be a non-transitory computer-readable storage medium.
  • the non-transitory computer-readable storage medium may be ROM, random access memory (RAM), CD-ROM, magnetic tape, Floppy disks and optical data storage devices, etc.
  • embodiments of the present application further provide a computer program product, including a computer readable code, or a non-volatile computer readable storage medium carrying the computer readable code, when the computer readable code
  • the processor in the electronic device implements the method described in the foregoing embodiments.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Security & Cryptography (AREA)
  • Stored Programmes (AREA)

Abstract

本申请关于一种应用管理方法及相关设备，涉及软件技术领域。本申请中，应用商店至少包括第一应用和第二应用，应用商店可以建立第一应用和第二应用的关联关系。第二应用能够调用第一应用以实现第一应用的功能。本申请可以使得不同应用的开发组织之间可以实现协作开发，提高开发效率，并有效节省应用所占据的应用商店的存储资源。

Description

应用管理方法及相关设备
本申请要求于2022年06月30日提交的、申请号为202210772348.7的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及软件技术领域，尤其涉及一种应用管理方法及相关设备。
背景技术
应用程序(application，APP)也称应用，是指为完成某项或多项特定工作的计算机程序，可以运行在用户模式和用户进行交互，可以具有可视的用户界面。
目前，应用的开发者可以将开发好的应用上架到应用商店中，需要使用APP的用户可以从应用商店中下载应用。
但是，目前不同的应用之间是独立运行的，不同应用的开发者之间协作不便。如：不同的开发组织之间很难对应用进行协作开发，协作开发应用的难度很高、效率很低。
发明内容
本申请提供一种应用管理方法及相关设备，可以使得不同应用的开发组织之间可以实现协作开发，提高开发效率。
本申请的技术方案如下：
第一方面，本申请提供一种应用管理方法，所述方法应用于应用商店，应用商店至少包括第一应用和第二应用；所述方法包括：建立第一应用和第二应用的关联关系；第二应用能够调用第一应用以实现第一应用的功能。
一些实现方式中，第二应用中包括第一信息，第一信息用于指示与第二应用关联的第一应用。
一些实现方式中，第一信息包括第一应用的标识；应用商店中的不同应用的标识不同。
可选地，第一应用和第二应用的版权所有者相同或不同。
可选地，第一应用和第二应用的开发者相同或不同。
第二方面，本申请提供一种应用管理装置，所述装置应用于应用商店，应用商店至少包括第一应用和第二应用。该装置可以用于应用商店实现如第一方面及第一方面的任意一种可能的实现方式所述的应用管理方法。该装置的功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。硬件或软件包括一个或多个与第一方面及第一方面的任意一种可能的实现方式所述的 应用管理方法中的步骤相对应的模块或单元。
例如，所述装置包括：应用管理模块，用于建立第一应用和第二应用的关联关系；第二应用能够调用第一应用以实现第一应用的功能。
一些实现方式中，第二应用中包括第一信息，第一信息用于指示与第二应用关联的第一应用。
一些实现方式中，第一信息包括第一应用的标识；应用商店中的不同应用的标识不同。
可选地，第一应用和第二应用的版权所有者相同或不同。
可选地，第一应用和第二应用的开发者相同或不同。
第三方面，本申请提供一种电子设备，如电子设备可以是上述第一方面中所述的应用商店对应的硬件设备。电子设备包括：处理器，用于存储处理器可执行指令的存储器；处理器被配置为执行所述指令时，使得电子设备实现如第一方面及第一方面的任意一种可能的实现方式所述的方法。
第四方面，本申请提供一种计算机可读存储介质，其上存储有计算机程序指令；当所述计算机程序指令被电子设备执行时，使得电子设备实现如第一方面及第一方面的任意一种可能的实现方式所述的方法。
第五方面，本申请提供一种计算机程序产品，包括计算机可读代码，或者承载有计算机可读代码的非易失性计算机可读存储介质，当所述计算机可读代码在电子设备中运行时，所述电子设备中的处理器实现如第一方面及第一方面的任意一种可能的实现方式所述的方法。
第六方面，本申请提供一种应用管理方法，所述方法包括：从应用商店中获取第一应用；根据第一应用生成第二应用；第二应用与第一应用具有关联关系，能够调用第一应用以实现第一应用的功能；将第二应用上架到应用商店中。
一些实现方式中，第二应用中包括第一信息，第一信息用于指示与第二应用关联的第一应用。
一些实现方式中，第一信息包括第一应用的标识。
可选地，第一应用和第二应用的版权所有者相同或不同。
可选地，第一应用和第二应用的开发者相同或不同。
第七方面，本申请提供一种应用管理装置，该装置可以用于实现如第六方面及第六方面的任意一种可能的实现方式所述的应用管理方法。该装置的功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。硬件或软件包括一个或多个与第六方面及第六方面的任意一种可能的实现方式所述的应 用管理方法中的步骤相对应的模块或单元。
例如，所述装置包括：获取模块，用于从应用商店中获取第一应用；生成模块，用于根据第一应用生成第二应用；第二应用与第一应用具有关联关系，能够调用第一应用以实现第一应用的功能；上架模块，用于将第二应用上架到应用商店中。
一些实现方式中，第二应用中包括第一信息，第一信息用于指示与第二应用关联的第一应用。
一些实现方式中，第一信息包括第一应用的标识。
可选地，第一应用和第二应用的版权所有者相同或不同。
可选地，第一应用和第二应用的开发者相同或不同。
第八方面，本申请提供一种电子设备，包括：处理器，用于存储处理器可执行指令的存储器；处理器被配置为执行所述指令时，使得电子设备实现如第六方面及第六方面的任意一种可能的实现方式所述的方法。
第九方面，本申请提供一种计算机可读存储介质，其上存储有计算机程序指令；当所述计算机程序指令被电子设备执行时，使得电子设备实现如第六方面及第六方面的任意一种可能的实现方式所述的方法。
第十方面，本申请提供一种计算机程序产品，包括计算机可读代码，或者承载有计算机可读代码的非易失性计算机可读存储介质，当所述计算机可读代码在电子设备中运行时，所述电子设备中的处理器实现如第六方面及第六方面的任意一种可能的实现方式所述的方法。
第十一方面，本申请提供一种应用管理方法，所述方法包括：接收第一下载请求，第一下载请求用于请求下载应用商店中的第二应用；第二应用与应用商店中的第一应用具有关联关系，能够调用第一应用以实现第一应用的功能；响应于第一下载请求，发送第二应用和第一应用。
一些实现方式中，第二应用中包括第一信息，第一信息用于指示与第二应用关联的第一应用。
一些实现方式中，第一信息包括第一应用的标识；应用商店中的不同应用的标识不同。
可选地，所述方法还包括：接收第二下载请求，第二下载请求用于请求下载应用商店中的第一应用；响应于第二下载请求，发送第一应用，其中，第一应用用于生成第二应用。
可选地，所述方法还包括：接收上架到应用商店的第二应用，第二应用是根据从应用商店中下载的第一应用生成的。
第十二方面，本申请提供一种应用管理装置，该装置可以用于实现如第十一方面及第十一方面的任意一种可能的实现方式所述的应用管理方法。该装置的功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。硬件或软件包括一个或多个与第十一方面及第十一方面的任意一种可能的实现方式所述的应用管理方法中的步骤相对应的模块或单元。
例如，所述装置包括：接收模块，用于接收第一下载请求，第一下载请求用于请求下载应用商店中的第二应用；第二应用与应用商店中的第一应用具有关联关系，能够调用第一应用以实现第一应用的功能；发送模块，用于响应于第一下载请求，发送第二应用和第一应用。
一些实现方式中，第二应用中包括第一信息，第一信息用于指示与第二应用关联的第一应用。
一些实现方式中，第一信息包括第一应用的标识；应用商店中的不同应用的标识不同。
可选地，接收模块，还用于接收第二下载请求，第二下载请求用于请求下载应用商店中的第一应用；发送模块，还用于响应于第二下载请求，发送第一应用，其中，第一应用用于生成第二应用。
可选地，接收模块，还用于接收上架到应用商店的第二应用，第二应用是根据从应用商店中下载的第一应用生成的。
第十三方面，本申请提供一种电子设备，包括：处理器，用于存储处理器可执行指令的存储器；处理器被配置为执行所述指令时，使得电子设备实现如第十一方面及第十一方面的任意一种可能的实现方式所述的方法。
第十四方面，本申请提供一种计算机可读存储介质，其上存储有计算机程序指令；当所述计算机程序指令被电子设备执行时，使得电子设备实现如第十一方面及第十一方面的任意一种可能的实现方式所述的方法。
第十五方面，本申请提供一种计算机程序产品，包括计算机可读代码，或者承载有计算机可读代码的非易失性计算机可读存储介质，当所述计算机可读代码在电子设备中运行时，所述电子设备中的处理器实现如第十一方面及第十一方面的任意一种可能的实现方式所述的方法。
第十六方面，本申请提供一种应用管理方法，可以应用于用户设备。所述方法包括：发送第一下载请求，第一下载请求用于请求下载应用商店中的第二应用；第二应用与应用商店中的第一应用具有关联关系，能够调用第一应用以实现第一应用的功能；接收第二应用和第一应用。
一些实现方式中，第二应用中包括第一信息，第一信息用于指示与第二 应用关联的第一应用。
一些实现方式中，第一信息包括第一应用的标识。
可选地，第一应用和第二应用的版权所有者相同或不同。
可选地，第一应用和第二应用的开发者相同或不同。
第十七方面，本申请提供一种应用管理装置，该装置可以用于实现如第十六方面及第十六方面的任意一种可能的实现方式所述的应用管理方法。该装置的功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。硬件或软件包括一个或多个与第十六方面及第十六方面的任意一种可能的实现方式所述的应用管理方法中的步骤相对应的模块或单元。
例如，所述装置包括：发送模块，用于发送第一下载请求，第一下载请求用于请求下载应用商店中的第二应用；第二应用与应用商店中的第一应用具有关联关系，能够调用第一应用以实现第一应用的功能；接收模块，用于接收第二应用和第一应用。
一些实现方式中，第二应用中包括第一信息，第一信息用于指示与第二应用关联的第一应用。
一些实现方式中，第一信息包括第一应用的标识。
可选地，第一应用和第二应用的版权所有者相同或不同。
可选地，第一应用和第二应用的开发者相同或不同。
第十八方面，本申请提供一种电子设备，包括：处理器，用于存储处理器可执行指令的存储器；处理器被配置为执行所述指令时，使得电子设备实现如第十六方面及第十六方面的任意一种可能的实现方式所述的方法。
第十九方面，本申请提供一种计算机可读存储介质，其上存储有计算机程序指令；当所述计算机程序指令被电子设备执行时，使得电子设备实现如第十六方面及第十六方面的任意一种可能的实现方式所述的方法。
第二十方面，本申请提供一种计算机程序产品，包括计算机可读代码，或者承载有计算机可读代码的非易失性计算机可读存储介质，当所述计算机可读代码在电子设备中运行时，所述电子设备中的处理器实现如第十六方面及第十六方面的任意一种可能的实现方式所述的方法。
基于上述第一方面至第二十方面中的任一方面，本申请至少具备如下有益效果：
本申请中，第二应用与应用商店中的第一应用具有关联关系，能够调用第一应用以实现第一应用的功能，可以实现第二应用和第一应用是分散独立存储的。这种分散独立存储的关系可以有效节省应用所占据的应用商店的存 储资源。另外，第二应用与应用商店中的第一应用具有关联关系，能够调用第一应用以实现第一应用的功能，还可以使得不同应用的开发组织之间可以实现协作开发，提高开发效率。
应当理解的是，以上的一般描述和后文的细节描述仅是示例性和解释性的，并不能限制本申请。
附图说明
此处的附图被并入说明书中并构成本说明书的一部分，示出了符合本申请的实施例，并与说明书一起用于解释本申请的原理，并不构成对本申请的不当限定。
图1为本申请实施例提供的应用管理方法的流程示意图；
图2为本申请实施例提供的应用管理方法的另一流程示意图；
图3为本申请实施例提供的模型和预定义的关系示意图；
图4为本申请实施例提供的数据模型的示意图；
图5为本申请实施例提供的第二应用的APP模型的组成示意图；
图6为本申请实施例提供的应用管理方法的又一流程示意图；
图7为本申请实施例提供的应用管理方法的又一流程示意图；
图8为本申请实施例提供的一种应用管理系统的组成示意图；
图9为本申请实施例提供的应用管理装置的结构示意图；
图10为本申请实施例提供的应用管理装置的另一结构示意图；
图11为本申请实施例提供的应用管理装置的又一结构示意图；
图12为本申请实施例提供的应用管理装置的又一结构示意图。
具体实施方式
为了使本领域普通人员更好地理解本申请的技术方案，下面将结合附图，对本申请实施例中的技术方案进行清楚、完整地描述。
需要说明的是，本申请的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便这里描述的本申请的实施例能够以除了在这里图示或描述的那些以外的顺序实施。以下示例性实施例中所描述的实施方式并不代表与本申请相一致的所有实施方式。相反，它们仅是与如所附权利要求书中所详述的、本申请的一些方面相一致的装置和方法的例子。
还应当理解的是，术语“包括”指示所描述特征、整体、步骤、操作、元素和/或组件的存在，但并不排除一个或多个其他特征、整体、步骤、操作、 元素和/或组件的存在或添加。
“和/或”用于描述关联对象的关联关系，表示可以存在三种关系。例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。字符“/”一般表示前后关联对象是一种“或”的关系。
应用程序(application，APP)也称应用，是指为完成某项或多项特定工作的计算机程序，可以运行在用户模式和用户进行交互，可以具有可视的用户界面。
目前，应用的开发者可以将开发好的应用上架到应用商店中，需要使用APP的用户可以从应用商店中下载应用。其中，应用商店可以在服务器、计算机等硬件设备上实现，也可以为用户提供一个可以交互的应用商店界面，供用户下载需要的应用。
例如，在工业相关场景中，可以基于服务器、计算机等硬件设备构建一个工业互联网平台，该工业互联网平台即前述应用商店。应用的开发者可以将开发好的应用上架到工业互联网平台中，需要使用应用的用户可以从工业互联网平台中下载使用应用。
但是，目前不同的应用之间是独立运行的，不同应用的开发者之间协作不便。如：不同的开发组织之间很难对应用进行协作开发，协作开发应用的难度很高、效率很低。
另外，目前的应用商店中，众多的应用会占用大量的存储资源。
基于此，本申请实施例提供了一种应用管理方法，该方法可以应用于应用商店，通过该方法可以使得不同应用的开发组织之间可以实现协作开发，提高开发效率，并有效节省应用所占据的应用商店的存储资源。
示例性地，该方法具体可以在应用商店对应的硬件设备上实现，如：硬件设备可以包括服务器、计算机等。其中，服务器可以是单独的一个服务器，或者，也可以是由多个服务器构成的服务器集群。部分实施方式中，服务器集群还可以是分布式集群。本申请对应用商店对应的硬件设备的具体实现方式不作限制。需要说明的是，本申请实施例中涉及到的应用商店侧实现步骤，均可以是由应用商店对应的硬件设备来实现。
图1为本申请实施例提供的应用管理方法的流程示意图。如图1所示，该应用管理方法可以包括：
S101、获取第一应用和第二应用。
可选地，应用商店至少可以包括第一应用和第二应用。第一应用和第二应用可以由各自的开发者或版权所有者上架到应用商店中。
S102、建立第一应用和第二应用的关联关系。
其中，第二应用能够调用第一应用以实现第一应用的功能。
例如，第一应用可以实现的功能为第一功能，则第二应用中不包括用于实现第一功能的代码，也可以通过调用第一应用的方式实现第一功能。
通过建立第一应用和第二应用的关联关系，可以使得当第二应用被下载时，应用商店能够将第二应用和第一应用一并进行下发。例如，用户可以使用用户设备(如手机、电脑等)向应用商店发送下载第二应用的请求。应用商店可以响应于该请求，向用户设备下发第二应用，同时，由于第二应用和第一应用之间建立了关联关系，所以应用商店可以基于该关联关系一并向用户设备下发第一应用。当用户设备运行下载后的第二应用时，第二应用可以调用下载的第一应用实现第一应用的功能。
在本申请中，第一应用可以认为是第二应用的子应用，但第一应用的代码又是独立在第二应用之外的。也即，在应用商店中，第二应用和第一应用是分散独立存储的。这种分散独立存储的关系可以有效节省应用所占据的应用商店的存储资源。
例如，假设存在开发组织1、开发组织2等两个开发组织，其中，开发组织1想要开发一个能够实现功能1和功能2的应用，开发组织2想要开发一个能够实现功能2的应用。目前，开发组织1需要开发一个独立的应用1来实现功能1和功能2，并将应用1上架到应用商店中；开发组织2需要开发一个独立的应用2来实现功能2，并将应用2上架到应用商店中。此时，应用1和应用2所占据的应用商店的存储资源至少包括：应用1中用于实现功能1的代码所占据的资源、应用1中用于实现功能2的代码所占据的资源、以及应用2中用于实现功能2的代码所占据的资源。
而本申请实施例提供的该应用管理方法中，应用2可以相当于第一应用来实现功能2，应用1可以相当于第二应用来实现功能1，且应用1可以调用应用2来实现功能2。例如，应用2中可以提供能够调用应用1的接口。此时，应用1和应用2所占据的应用商店的存储资源包括：应用1中用于实现功能1的代码所占据的资源、以及应用2中用于实现功能2的代码所占据的资源。相对于目前的方式而言，应用1调用应用2来实现功能2，节省了应用1中用于实现功能2的代码所占据的资源。
可以理解的，当第二应用包括多个，如：应用商店中还包括能够调用应用2来实现功能2的应用3时，节省了应用所占据的应用商店的存储资源的效果更为显著。
为了达到节省存储资源的目的，虽然本申请中第二应用和第一应用是分散存储的，但由于第二应用和第一应用之间建立了关联关系，使得当第二应用被下载时，应用商店能够将第二应用和第一应用一并进行下发，所以并不会影响用户设备侧对应用的正常使用。
另外，本申请实施例提供的应用管理方法还可以使得不同应用的开发组织之间可以实现协作开发，提高开发效率。例如，同样以上述开发组织1开发一个能够实现功能1和功能2的应用，开发组织2开发一个能够实现功能2的应用为例，开发组织2可以开发一个能够实现功能2的应用2，开发组织1可以开发一个能够实现功能1且能够调用应用2的应用1即可，开发组织1和开发组织2之间实现了协作开发，开发组织1的开发效率可以更高。例如，开发组织2可以将应用2上架到应用商店，开发组织1可以从应用商店中下载应用2，并根据应用2实现应用1的开发。如：可以根据应用2在应用1中实现能够调用应用2的相关接口。
下面对建立第一应用和第二应用的关联关系的实现方式进行示例性说明。
一些实现方式中，第二应用中可以包括第一信息，第一信息用于指示与第二应用关联的第一应用。应用商店建立第一应用和第二应用的关联关系，可以包括：基于第二应用中包括的第一信息，建立第一应用和第二应用的关联关系；或者，将第二应用中包括的第一信息作为第一应用和第二应用的关联关系。
可选地，第二应用的开发者在开发第二应用时，可以在第二应用中增加第一应用的标识，或者，增加能够指示第一应用的一些字段。第一应用的标识或者能够指示第一应用的字段即为上述第一信息。也即，第一信息可以包括：第一应用的标识或能够指示第一应用的一些字段。
例如，当第二应用被上架到应用商店后，应用商店侧可以根据第二应用中包括的第一应用的标识或者能够指示第一应用的字段，为第二应用和第一应用之间维护一个关联关系表，实现第一应用和第二应用的关联关系的建立。例如，关联关系表中可以包括第二应用的标识、以及与第二应用的标识对应的第一应用的标识或者能够指示第一应用的字段。当第二应用被下载时，应用商店可以通过查询第一应用和第二应用的关联关系(如关联关系表)，确定出哪个应用为第一应用，并将第二应用和第一应用一并进行下发。
又例如，当第二应用被上架到应用商店后，应用商店侧可以直接将第二应用中包括的第一应用的标识或者能够指示第一应用的字段，作为第一应用 和第二应用的关联关系。当第二应用被下载时，应用商店可以通过查询第二应用中包括的第一应用的标识或者能够指示第一应用的字段，确定出哪个应用为第一应用，并将第二应用和第一应用一并进行下发。
本申请中，应用商店中的不同应用的标识不同。也即，应用商店中的不同应用具有唯一标识。
基于前述实施例，本申请实施例还提供了一种应用管理方法，该方法可以用于开发生成和第一应用具有关联关系的第二应用。一种实现方式中，第一应用和第二应用的开发者相同，开发者可以在本地开发完成第一应用，并根据第一应用开发生成第二应用，然后将第一应用和第二应用上架到应用商店中。另一种实现方式中，第一应用和第二应用的开发者不同，应用商店可以包括第一应用，开发者可以在从应用商店中获取第一应用，并根据第一应用开发生成第二应用，然后将第二应用上架到应用商店中。下面以开发者从应用商店中获取第一应用，并根据第一应用开发生成第二应用的方式进行示例性说明。
图2为本申请实施例提供的应用管理方法的另一流程示意图。如图2所示，该应用管理方法包括：
S201、开发侧的设备向应用商店发送下载第一应用的请求。
其中，开发侧的设备可以包括开发者所使用的服务器、计算机等。
S202、应用商店响应于下载第一应用的请求，向开发侧的设备发送第一应用。
例如，下载第一应用的请求中可以包括第一应用的标识，应用商店可以基于第一应用的标识找到存储的第一应用下发给开发侧的设备。
通过上述S201-S202，开发侧的设备可以从应用商店中获取到第一应用。
S203、根据第一应用生成第二应用。
其中，第二应用与第一应用具有关联关系，能够调用第一应用以实现第一应用的功能。
例如，开发者可以开发第二应用，并在第二应用中添加能够调用第一应用的接口，以使得第二应用能够调用第一应用以实现第一应用的功能。
S204、开发侧的设备将第二应用上架到应用商店中。
可选地，本申请实施例中，第一应用和第二应用的版权所有者可以相同或不同，第一应用和第二应用的开发者也可以相同或不同。
例如，第一应用的开发者为开发组织1，第二应用的开发者为开发组织2，但第一应用和第二应用版权所有者均为单位A。或者，第一应用的开发者为开 发组织1、版权所有者为单位A，第二应用的开发者为开发组织2、版权所有者均为单位B。又或者，第一应用的版权所有者为单位A，第二应用的版权所有者均为单位B，但第一应用和第二应用开发者均为开发组织1。
可选地，本申请实施例中，第一应用和第二应用可以是由各自的版权所有者上架到应用商店的，也可以是由各自的开发者上架到应用商店的，在此不作限制。例如，上述S204中也可以是由第二应用的版权所有者侧的设备将第二应用上架到应用商店中。
可选地，应用商店中可以包括每个应用对应的开发者的信息和版权所有者的信息，如：开发者的团队名称，版权所有者的单位名称、地址等。
下面对S203中根据第一应用生成第二应用的具体实现方式进行示例性说明。
示例性地，根据第一应用生成第二应用的过程可以如下：
1)创建第二应用的APP模型，并为第二应用的APP模型分配唯一标识(如全球唯一标识)。例如，第二应用的开发者可以在开发工作室中创建第二应用的APP模型。
2)定义第二应用的APP模型依赖的数据模型，发布第二应用的APP模型依赖的数据模型的数据预定义(简称第二应用的数据预定义)到第二应用的系统仓库中，并为第二应用的数据预定义分配唯一标识(如全球唯一标识)；其中，第二应用的系统仓库也即开发第二应用的开发者所使用的系统仓库，第二应用的系统仓库与第二应用的开发者的开发工作室可以通过网络连接。
本申请中提到了模型和预定义的概念，模型是在建模抽象时描述对象结构的信息，预定义是确定了结构的模型并配置有参数的信息。预定义上记录了模型的信息，预定义用来实例化对象，实例化对象是按照其模型的结构构建对象的结构，并把参数值作为对象的初始值。预定义也能被其他模型引用为子预定义。
例如，创建数据模型时，操作可以包括：新建模型，分配名字和标识；添加成员，指定成员类型；删除成员；添加或删除子预定义；设置子预定义的初值；更新模型版本；发布某模型版本生成预定义等。创建预定义时，操作可以包括：指定某模型版本发布(创建)预定义；分配名称和标识；设置预定义的参数值(属性和成员)等。
图3为本申请实施例提供的模型和预定义的关系示意图。
如图3所示，模型可以包括基本属性和成员列表；基本属性可以包括名称、描述、全局唯一标识符(globally unique identifier,GUID)、版本等 信息；成员列表可以包括：“成员1：名称+类型”、“成员2：名称+类型”、“成员3：名称+类型”等信息。
预定义可以包括基本属性和成员列表；基本属性可以包括名称、描述、GUID、模型GUID+版本等信息；成员列表可以包括：“成员1+值”、“成员2+值”、“成员3+值”等信息。
步骤2)中所述的数据模型是时空数据库中的概念，描述了时空库中数据对象的结构，是客观世界对象的抽象描述。
示例性地，图4为本申请实施例提供的数据模型的示意图。如图4所示，数据模型可以包括：基本属性、成员列表、以及子模型列表。具有子模型的数据模型是复合的数据模型，如：图中的数据模型A为复合的数据模型，数据模型B和数据模型C是数据模型A的子模型。
数据模型中，基本属性描述了数据的固有属性，包括名称、描述、GUID、时间属性(如精度)、空间属性(如坐标系、几何形状)等；成员列表描述了自由定义的字段，每个成员描述其字段名称、数据类型，如：成员1、成员2等。子模型列表中记录了引用为子模型的数据模型的数据预定义的标识，建立了子模型和数据模型之间的依赖关系，例如，数据模型A的子模型列表包括数据模型B和数据模型C的数据预定义的标识，如：“名称B1+引用模型ID+参数值”、“名称B2+引用模型ID+参数值”、“名称C3+引用模型ID+参数值”等。
例如，电机设备都具有转速、温度、电流等参数，建立电机设备的数据模型，电机设备的数据模型可以包括转速、温度、电流的成员，通过电机设备的数据模型可以对同类的电机统一描述。
又例如，假设压缩机车间内部都有定盘生产线、静盘生产线、总装生产线，建立压缩机车间的数据模型，压缩机车间的数据模型的内部可以包括子模型：定盘生产线、静盘生产线、总装生产线等。压缩机车间的数据模型可以描述同类的压缩机车间模型。
3)定义第二应用的APP模型依赖的资源对象(简称第二应用的资源对象)到资源库，并为第二应用的资源对象分配唯一标识(如全球唯一标识)。
其中，资源对象是时空数据库中的概念。把二进制文件数据进行对象化组织和管理，为每个资源对象分配标识，第二应用的APP模型能够通过资源对象的标识访问资源对象的数据。
例如，把图标定义为资源对象和第二应用的APP模型之间形成依赖关系，则第二应用的APP模型可以使用这个图标。又例如，把视频文件定义为资源 对象和第二应用的APP模型之间形成依赖关系，则第二应用的APP模型可以通过依赖关系读取视频文件进行播放。
4)在第二应用的APP模型上建立第二应用的依赖数据预定义列表，从第二应用的系统仓库中选择第二应用的数据预定义，将第二应用的数据预定义的标识记录在第二应用的依赖数据预定义列表上。其中，第二应用的系统仓库中的数据预定义可以是开发者自建的，也可以是从应用商店上购买的。
5)在第二应用的APP模型上建立第二应用的依赖资源列表，从资源库中选择第二应用的资源对象，把第二应用的资源对象的标识记录在第二应用的依赖资源列表上。其中，资源库中的资源对象可以是开发者自建的，也可以是从应用商店上购买的。
6)添加第二应用的APP模型的子APP列表，从第二应用的系统仓库中选择作为子APP的第一应用的预定义，将第一应用的预定义的标识记录在第二应用的APP模型的子APP列表上。第一应用的预定义即S201-S202中从应用商店获取的第一应用。第一应用的预定义的标识即前述实施例中所述的第一应用的标识。第一应用的预定义可以由第一应用的版权所有者或者开发者上传到应用商店中。
7)编写第二应用的APP模型的功能函数的程序逻辑。
8)发布第二应用的APP模型的预定义(简称第二应用的预定义)到第二应用的系统仓库中，并为第二应用的预定义分配唯一标识(如全球唯一标识)。第二应用的预定义的标识即第二应用的标识。
其中，发布第二应用的预定义时，还可以设置预定义的参数值(如：属性和成员)。
示例性地，图5为本申请实施例提供的第二应用的APP模型的组成示意图。
如图5所示，第二应用的APP模型可以包括：基本属性、依赖数据列表、功能函数列表、以及子APP列表。
基本属性可以包括：名称、描述、以及GUID(即第二应用的APP模型的唯一标识)。
依赖数据列表记录了第二应用的APP模型需要使用的数据模型或资源对象，在第二应用的APP模型，以及依赖的数据模型或资源对象之间建立了关系。例如，“数据1：数据ID”、“数据2：数据ID”等表示依赖的数据模型的数据预定义的标识或资源对象的标识。依赖数据列表可以包括上述依赖数据预定义列表和/或上述依赖资源列表。
功能函数列表可以包括：函数1、函数2等第二应用的APP模型的功能函数，这些功能函数是第二应用的APP模型的程序逻辑的实现。
子APP列表中记录了第一应用的信息，在第二应用的APP模型和第一应用之间建立的关联关系。例如，子APP列表可以包括子APP-B1、APP-C2、APP-D3等第一应用的标识和配置参数。也即，APP模型B、APP模型C、以及APP模型D等可以是上述第一应用。
通过上述步骤1)-步骤8)所述的过程，即可实现S203中根据第一应用生成第二应用。
可以理解的，第一应用的开发过程与第二应用的开发过程类似。其区别仅仅在于，当第一应用不包括更深层级的子APP(即第一应用没有调用其他应用实现其他应用的功能)时，第一应用的开发过程中不包括类似于上述步骤6)中所述的过程。当第一应用还包括更深层级的子APP(即第一应用调用其他应用实现其他应用的功能)时，第一应用的开发过程中与上述步骤1)-步骤8)所述的过程一致。在此对第一应用的开发过程不再赘述。
需要说明的是，第二应用和第一应用可能存在依赖同一数据预定义或资源对象的情况，因为依赖关系是在第二应用和第一应用各自开发时建立的，也就是说，第二应用和第一应用的依赖数据列表中可能记录同一数据预定义或资源对象的标识。
下面对S204中将第二应用上架到应用商店的过程进行示例性说明。
示例性地，以第二应用是由第二应用的版权所有者上架到应用商店为例，第二应用的版权所有者将第二应用上架到应用商店的过程如下：
1)第二应用的版权所有者在应用商店中创建将第二应用的APP商品，第二应用的APP商品包括第二应用的预定义的标识。
其中，APP商品是指应用商店中为APP的预定义建立的对应的信息，主要描述APP的预定义的商品化信息。例如，第二应用的APP商品中还可以包括第二应用的图案(logo)、视频、商品定价、产品名称、产品说明等。
2)应用商店根据第二应用的版权所有者在应用商店中的注册账户(或者第二应用的版权所有者的系统产品码)，确定第二应用的APP商品对应的第二应用的预定义所归属的第二应用的系统仓库。也即，应用商店可以根据第二应用的版权所有者在应用商店中的注册账户，确定第二应用的APP商品对应的第二应用的预定义来自哪个系统仓库。
3)应用商店根据第二应用的APP商品中包括的第二应用的预定义的标识，向第二应用的系统仓库请求上架第二应用的预定义。
4)第二应用的系统仓库响应于来自应用商店的上架第二应用的预定义的请求，执行下述步骤(4.1)至步骤(4.2)：
(4.1)第二应用的系统仓库向应用商店上传第二应用的预定义，第二应用的预定义可以包括第二应用的APP模型和配置参数。
(4.2)第二应用的系统仓库根据第二应用的依赖数据预定义列表和依赖资源列表，向应用商店上传第二应用的数据预定义和资源对象。
通过上述步骤1)-步骤4)所述的过程，即可实现S204中将第二应用上架到应用商店。
需要说明的是，上述步骤4)中，当第二应用还关联了其他本地的子APP(不是从应用商店获取的子APP)时，第二应用的系统仓库还可以向应用商店上传第二应用关联的本地的子APP的预定义，以及根据本地的子APP的依赖数据预定义列表和依赖资源列表，向应用商店上传本地的子APP的数据预定义和资源对象。对于第一应用而言，由于应用商店中已经存在第一应用相关的数据，则第二应用的系统仓库无需再向应用商店上传第一应用相关的数据，如：第一应用的预定义、第一应用的数据预定义和资源对象等。从而，应用商店中仅包括一份第一应用相关的数据，实现了前述实施例中所述的节省应用商店的存储资源的效果。
以上实施例主要从应用商店管理应用的角度、以及开发侧开发应用的角度介绍了本申请实施例提供的应用管理方法。如前述实施例中所述，在本申请中，当第二应用被下载时，应用商店能够将第二应用和第一应用一并进行下发。
例如，基于应用商店接收下载第二应用的请求，并响应于下载第二应用的请求一并下发第二应用和第一应用的场景，本申请实施例还提供一种应用管理方法，可以应用于应用商店侧。该方法可以包括：接收第一下载请求，第一下载请求用于请求下载应用商店中的第二应用；第二应用与应用商店中的第一应用具有关联关系，能够调用第一应用以实现第一应用的功能；响应于第一下载请求，发送第二应用和第一应用。
下面以用户设备向应用商店发送第一下载请求为例，对该应用管理方法进行说明。其中，用户设备可以是手机、电脑等。
示例性地，图6为本申请实施例提供的应用管理方法的又一流程示意图。如图6所示，该应用管理方法包括：
S601、用户设备向应用商店发送第一下载请求，第一下载请求用于请求下载应用商店中的第二应用。
相应地，应用商店接收第一下载请求。
S602、应用商店响应于第一下载请求，向用户设备发送第二应用和第一应用。
示例性地，第一下载请求中可以包括第二应用的标识，第二应用的标识用于指示下载第二应用。应用商店可以通过第二应用与第一应用的关联关系确定第一应用，并将第一应用和第二应用一并下发给用户设备。例如，应用商店可以根据第二应用中包括的第一应用的标识确定出哪个应用为第一应用，并将第二应用和第一应用一并进行下发。
可选地，对于前述实施例中所述的第二应用是根据从应用商店中获取的第一应用生成的场景，应用商店还可以接收第二下载请求，第二下载请求用于请求下载应用商店中的第一应用；以及，响应于第二下载请求，发送第一应用，其中，第一应用用于生成第二应用。应用商店还可以接收上架到应用商店的第二应用，第二应用是根据从应用商店中下载的第一应用生成的。
例如，以第二应用的开发侧的设备(简称开发侧的设备)向应用商店发送第二下载请求为例，对该应用管理方法进行说明。
示例性地，图7为本申请实施例提供的应用管理方法的又一流程示意图。如图7所示，该应用管理方法包括：
S701、开发侧的设备向应用商店发送第二下载请求，第二下载请求用于请求下载应用商店中的第一应用。
相应地，应用商店接收第二下载请求。
S702、应用商店响应于第二下载请求，向开发侧的设备发送第一应用。
其中，第一应用用于生成第二应用。
例如，开发侧的设备可以根据第一应用生成第二应用，具体过程可以参考前述实施例中所述，不再赘述。
S703、开发侧的设备将第二应用上架到应用商店中。
S703中第二应用的上架过程可以参考前述实施例中所述，不再赘述。
S704、用户设备向应用商店发送第一下载请求，第一下载请求用于请求下载应用商店中的第二应用。
相应地，应用商店接收第一下载请求。
S705、应用商店响应于第一下载请求，向用户设备发送第二应用和第一应用。
S704-S705可以参考S601-S602所述，不再赘述。
可选地，在本申请中，第二应用可以称为成品APP，第二应用的子APP(如 第一应用)可以称为零件APP。成品APP可以是能够独立运行的程序。零件APP可以是能够独立运行的APP程序，也可以是不独立运行的程序。零件APP能够作为一个或多个成品APP的子APP，实现被成品APP调用以实现零件APP的功能。
可以理解的，零件APP和成品APP是个相对概念，作为子APP的应用都可以认称为零件APP。例如，存在一个第三应用可以调用第二应用实现第二应用的功能时，第三应用是成品APP，第二应用是零件APP。
下面以一个具体的示例，对本申请实施例提供的应用管理方法进行更进一步的说明。
图8为本申请实施例提供的一种应用管理系统的组成示意图。如图8所示，开发系统仓库1、开发系统仓库2、应用商店、以及消费者仓库可以组成应用管理系统。
开发系统仓库1可以是用于开发零件APP(如上述第一应用)的系统仓库。零件APP的开发者可以在开发系统仓库1中开发完成零件APP，并将零件APP上架到应用商店中。其中，零件APP可以包括依赖数据预定义列表和依赖资源列表。依赖数据预定义列表建立了零件APP与数据模型4(预定义)和数据模型5(预定义)的依赖关系。依赖资源列表建立了零件APP与资源数据4的依赖关系。
开发系统仓库2可以是用于开发成品APP(如上述第二应用)的系统仓库。成品APP的开发者可以从应用商店中下载零件APP到开发系统仓库2中，并根据零件APP在开发系统仓库2中开发完成成品APP，并将成品APP上架到应用商店中。其中，成品APP可以包括依赖数据预定义列表和依赖资源列表。依赖数据预定义列表建立了成品APP与数据模型1(预定义)、数据模型2(预定义)、以及数据模型3(预定义)的依赖关系。依赖资源列表建立了成品APP与资源数据1、资源数据2、以及资源数据3的依赖关系。成品APP和零件APP建立了关联关系，能够调用零件APP实现零件APP的功能。
消费者仓库可以是消费使用第二应用的消费者(用户)侧的仓库。消费者可以使用用户设备从应用商店中下载成品APP到消费者仓库。当消费者使用用户设备从应用商店中下载成品APP时，应用商店可以将成品APP和零件APP一并下发到消费者仓库。
示例性地，消费者从应用商店中下载成品APP的过程可以包括：1)消费者通过用户设备在应用商店提供的交互界面中执行下载成品APP的指令，触发用户设备向应用商店发送下载成品APP的请求，下载成品APP的请求可以 指定成品APP的名称(如包括成品APP的标识)。2)应用商店根据下载成品APP的请求指定的成品APP的名称，将成品APP的预定义下发到消费者仓库中。3)应用商店根据成品APP的预定义的依赖数据预定义列表和依赖资源列表找到成品APP依赖的数据预定义和资源数据下发到消费者仓库中。4)应用商店根据成品APP中包括的零件APP的标识(如查询成品APP的子APP列表)，将零件APP的预定义下发到消费者仓库中。5)应用商店根据零件APP的预定义的依赖数据预定义列表和依赖资源列表找到零件APP依赖的数据预定义和资源数据下发到消费者仓库中。
可选地，上述开发系统仓库(开发系统仓库1和开发系统仓库2)可以是APP开发系统的一部分，APP开发系统还可以包括开发者工作室。开发者工作室是指开发者编辑APP模型的系统，能够创建、编辑、发布等APP模型管理操作。开发系统仓库是存放开发者开发完成的APP模型发布成APP预定义的系统。
可选地，消费者仓库可以是消费者应用系统的一部分，消费者应用系统还可以包括APP运行环境和APP运维系统。消费者应用系统是指一个独立的生产企业的业务应用系统，生产企业在系统上完成业务活动，并负责维护业务应用系统。消费者仓库是存放消费者购买的APP预定义的系统。APP运维系统是消费者运维APP的系统。APP运行环境是运行APP的环境系统。
成品APP和零件APP下载到消费者仓库后，成品APP预定义可以创建APP运行实例，并指定运行环境(计算机节点)、分配计算机资源(如中央处理器(central processing unit，CPU)、内存、网络带宽等)。APP运行实例上面带有APP的预定义的标识。APP运维系统可以根据APP运行实例上的APP的预定义的标识，把APP的预定义的APP模型(APP的预定义上携带了APP模型的标识)的功能逻辑部署到指定的计算机节点。APP运维系统、消费者仓库、APP运行环境之间通过网络通信完成APP程序文件的部署过程。完成部署之后，可以启动APP实例的运行，开始执行APP实例的功能函数逻辑。
可选地，应用商店可以包括一个由店铺系统和交易系统组成的商店系统。该商店系统可以作为应用商店的运营商运营的商品交易流通系统。APP软件开发企业(即开发者)和生产企业(即消费者)可以通过商店系统完成APP的交易和共享。其中，店铺系统可以包括一个或多个店铺，用于存放上架的APP商品，负责APP的上架、下载、授权钥匙分发等。交易系统可以实现订单管理、支付管理等功能。
本申请中，成品APP的开发者和零件APP的开发者之间可以实现协同开 发，能够有效提升成品APP的开发效率。零件APP能够被一个或多个成品APP调用以实现零件APP的功能，可以实现零件APP能够在不同开发组织之间的复用。通过应用商店，零件APP能够被更多的开发组织采用，零件APP的价值被放大，零件APP开发者的价值也被放大，可以提升APP开发者的积极性。
以工业APP的场景为例，通过这种合作模式，众多的工业APP开发者能够分工协作，复杂的工业APP由单个开发者开发转变为众多开发者协作开发，工业APP的产出效率会提升。
另外，成品APP和零件APP在应用商店中分散存储，可以保证不出现冗余数据，节省APP所占据的应用商店的存储资源。
可以理解的，在实际实施时，本申请实施例所述的应用商店、开发侧的设备、用户设备等可以包含有用于实现前述对应的应用管理方法的一个或多个硬件结构和/或软件模块，这些执行硬件结构和/或软件模块可以构成一个电子设备。本领域技术人员应该很容易意识到，结合本文中所申请的实施例描述的各示例的算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
基于这样的理解，以应用商店包含的硬件结构和/或软件模块为例，本申请实施例还对应提供一种应用管理装置，可以应用于上述应用商店(如应用商店对应的硬件设备)。图9为本申请实施例提供的应用管理装置的结构示意图。如图9所示，该应用管理装置可以包括：获取模块901，用于获取第一应用和第二应用。应用管理模块902，用于建立第一应用和第二应用的关联关系。第二应用能够调用第一应用以实现第一应用的功能。
本申请实施例还对应提供一种应用管理装置，可以应用于上述开发侧的设备。图10为本申请实施例提供的应用管理装置的另一结构示意图。如图10所示，该应用管理装置可以包括：获取模块1001，用于从应用商店中获取第一应用。生成模块1002，用于根据第一应用生成第二应用。第二应用与第一应用具有关联关系，能够调用第一应用以实现第一应用的功能。上架模块1003，用于将第二应用上架到应用商店中。
本申请实施例还对应提供一种应用管理装置，可以应用于上述应用商店。图11为本申请实施例提供的应用管理装置的又一结构示意图。如图11所示，该应用管理装置可以包括：接收模块1101，用于接收第一下载请求，第一下 载请求用于请求下载应用商店中的第二应用。第二应用与应用商店中的第一应用具有关联关系，能够调用第一应用以实现第一应用的功能。发送模块1102，用于响应于第一下载请求，发送第二应用和第一应用。
可选地，接收模块1101，还用于接收第二下载请求，第二下载请求用于请求下载应用商店中的第一应用。发送模块1102，还用于响应于第二下载请求，发送第一应用。其中，第一应用用于生成第二应用。
可选地，接收模块1101，还用于接收上架到应用商店的第二应用，第二应用是根据从应用商店中下载的第一应用生成的。
本申请实施例还对应提供一种应用管理装置，可以应用于上述用户设备。图12为本申请实施例提供的应用管理装置的又一结构示意图。如图12所示，该应用管理装置可以包括：发送模块1201，用于发送第一下载请求，第一下载请求用于请求下载应用商店中的第二应用。第二应用与应用商店中的第一应用具有关联关系，能够调用第一应用以实现第一应用的功能。接收模块1202，用于接收第二应用和第一应用。
如上所述，本申请实施例可以根据上述方法示例对应用管理方法中涉及到的各执行主体进行功能模块的划分。其中，上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。另外，还需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。
关于上述实施例中的应用管理装置，其中各个模块执行操作的具体方式、以及具备的有益效果，均已经在前述方法实施例中进行了详细描述，此处不再赘述。
本申请实施例还提供一种电子设备，该电子设备可以是应用商店对应的硬件设备，或者开发侧的设备，又或者上述用户设备。电子设备包括：处理器，用于存储处理器可执行指令的存储器；处理器被配置为执行所述指令时，使得电子设备实现如前述实施例所述的方法。
在示例性实施例中，本申请实施例还提供一种计算机可读存储介质，其上存储有计算机程序指令；当所述计算机程序指令被电子设备执行时，使得电子设备实现如前述实施例所述的方法。
可选地，上述计算机可读存储介质可以是非临时性计算机可读存储介质，例如，所述非临时性计算机可读存储介质可以是ROM、随机存取存储器(RAM)、CD-ROM、磁带、软盘和光数据存储设备等。
在示例性实施例中，本申请实施例还提供一种计算机程序产品，包括计算机可读代码，或者承载有计算机可读代码的非易失性计算机可读存储介质，当所述计算机可读代码在电子设备中运行时，所述电子设备中的处理器实现如前述实施例所述的方法。
本领域技术人员在考虑说明书及实践这里申请的发明后，将容易想到本申请的其它实施方案。本申请旨在涵盖本申请的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本申请的一般性原理并包括本申请未申请的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示例性的，本申请的真正范围和精神由下面的权利要求指出。
应当理解的是，本申请并不局限于上面已经描述并在附图中示出的精确结构，并且可以在不脱离其范围进行各种修改和改变。本申请的范围仅由所附的权利要求来限制。

Claims (21)

  1. 一种应用管理方法，其特征在于，所述方法应用于应用商店，所述应用商店至少包括第一应用和第二应用；所述方法包括：
    建立所述第一应用和所述第二应用的关联关系；
    所述第二应用能够调用所述第一应用以实现所述第一应用的功能。
  2. 根据权利要求1所述的方法，其特征在于，所述第二应用中包括第一信息，所述第一信息用于指示与所述第二应用关联的所述第一应用。
  3. 根据权利要求2所述的方法，其特征在于，所述第一信息包括所述第一应用的标识；
    所述应用商店中的不同应用的标识不同。
  4. 根据权利要求1-3任一项所述的方法，其特征在于，所述第一应用和所述第二应用的版权所有者相同或不同。
  5. 根据权利要求1-3任一项所述的方法，其特征在于，所述第一应用和所述第二应用的开发者相同或不同。
  6. 一种应用管理方法，其特征在于，所述方法包括：
    从应用商店中获取第一应用；
    根据所述第一应用生成第二应用；所述第二应用与所述第一应用具有关联关系，能够调用所述第一应用以实现所述第一应用的功能；
    将所述第二应用上架到所述应用商店中。
  7. 根据权利要求6所述的方法，其特征在于，所述第二应用中包括第一信息，所述第一信息用于指示与所述第二应用关联的所述第一应用。
  8. 根据权利要求7所述的方法，其特征在于，所述第一信息包括所述第一应用的标识。
  9. 根据权利要求6-8任一项所述的方法，其特征在于，所述第一应用和所述第二应用的版权所有者相同或不同。
  10. 根据权利要求6-8任一项所述的方法，其特征在于，所述第一应用和所述第二应用的开发者相同或不同。
  11. 一种应用管理方法，其特征在于，所述方法包括：
    接收第一下载请求，所述第一下载请求用于请求下载应用商店中的第二应用；所述第二应用与所述应用商店中的第一应用具有关联关系，能够调用所述第一应用以实现所述第一应用的功能；
    响应于所述第一下载请求，发送所述第二应用和所述第一应用。
  12. 根据权利要求11所述的方法，其特征在于，所述第二应用中包括第一信息，所述第一信息用于指示与所述第二应用关联的所述第一应用。
  13. 根据权利要求12所述的方法，其特征在于，所述第一信息包括所述第一应用的标识；
    所述应用商店中的不同应用的标识不同。
  14. 根据权利要求11-13任一项所述的方法，其特征在于，所述方法还包括：
    接收第二下载请求，所述第二下载请求用于请求下载所述应用商店中的所述第一应用；
    响应于所述第二下载请求，发送所述第一应用，其中，所述第一应用用于生成所述第二应用。
  15. 根据权利要求14所述的方法，其特征在于，所述方法还包括：
    接收上架到所述应用商店的所述第二应用，所述第二应用是根据从所述应用商店中下载的所述第一应用生成的。
  16. 一种应用管理装置，其特征在于，所述装置应用于应用商店，所述应用商店至少包括第一应用和第二应用；所述装置包括：
    应用管理模块，用于建立所述第一应用和所述第二应用的关联关系；
    所述第二应用能够调用所述第一应用以实现所述第一应用的功能。
  17. 一种应用管理装置，其特征在于，所述装置包括：
    获取模块，用于从应用商店中获取第一应用；
    生成模块，用于根据所述第一应用生成第二应用；所述第二应用与所述第一应用具有关联关系，能够调用所述第一应用以实现所述第一应用的功能；
    上架模块，用于将所述第二应用上架到所述应用商店中。
  18. 一种应用管理装置，其特征在于，所述装置包括：
    接收模块，用于接收第一下载请求，所述第一下载请求用于请求下载应用商店中的第二应用；所述第二应用与所述应用商店中的第一应用具有关联关系，能够调用所述第一应用以实现所述第一应用的功能；
    发送模块，用于响应于所述第一下载请求，发送所述第二应用和所述第一应用。
  19. 一种电子设备，其特征在于，包括：处理器；存储器；以及计算机程序；其中，所述计算机程序存储在所述存储器上，当所述计算机程序被所述处理器执行时，使得所述电子设备实现如权利要求1-5任一项所述的方法，或者，如权利要求6-10任一项所述的方法，又或者，如权利要求11-15任一项所述的方法。
  20. 一种计算机可读存储介质，所述计算机可读存储介质包括计算机程 序，其特征在于，当所述计算机程序在电子设备上运行时，使得所述电子设备实现如权利要求1-5任一项所述的方法，或者，如权利要求6-10任一项所述的方法，又或者，如权利要求11-15任一项所述的方法。
  21. 一种计算机程序产品，包括计算机可读代码，或者承载有计算机可读代码的非易失性计算机可读存储介质，其特征在于，当所述计算机可读代码在电子设备中运行时，所述电子设备中的处理器实现如权利要求1-5任一项所述的方法，或者，如权利要求6-10任一项所述的方法，又或者，如权利要求11-15任一项所述的方法。
PCT/CN2023/103730 2022-06-30 2023-06-29 应用管理方法及相关设备 Ceased WO2024002222A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US18/879,756 US20250390312A1 (en) 2022-06-30 2023-06-29 Application management method and related device
EP23830391.1A EP4538869A4 (en) 2022-06-30 2023-06-29 APPLICATION MANAGEMENT METHOD AND ASSOCIATED DEVICE

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210772348.7 2022-06-30
CN202210772348.7A CN115080102A (zh) 2022-06-30 2022-06-30 应用管理方法及相关设备

Publications (1)

Publication Number Publication Date
WO2024002222A1 true WO2024002222A1 (zh) 2024-01-04

Family

ID=83258089

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/103730 Ceased WO2024002222A1 (zh) 2022-06-30 2023-06-29 应用管理方法及相关设备

Country Status (4)

Country Link
US (1) US20250390312A1 (zh)
EP (1) EP4538869A4 (zh)
CN (1) CN115080102A (zh)
WO (1) WO2024002222A1 (zh)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115080102A (zh) * 2022-06-30 2022-09-20 北京亚控科技发展有限公司 应用管理方法及相关设备
CN115695412B (zh) * 2022-09-28 2024-08-30 北京亚控科技发展有限公司 工业应用系统、开发方法、装置及存储介质
CN115421780A (zh) * 2022-09-29 2022-12-02 北京亚控科技发展有限公司 应用程序的开发方法及相关设备
CN119179500A (zh) * 2023-06-21 2024-12-24 华为技术有限公司 一种免安装应用的下载方法与相关设备

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160227343A1 (en) * 2013-06-04 2016-08-04 Qiongmao SHEN System and method for creating mobile application store
CN110060134A (zh) * 2019-04-26 2019-07-26 天津店主助手科技有限公司 App关联方法与系统、分享方法与系统、终端及介质
CN111539775A (zh) * 2020-05-07 2020-08-14 网易（杭州）网络有限公司 应用程序的管理方法及设备
CN113485722A (zh) * 2021-06-30 2021-10-08 北京鲸鲮信息系统技术有限公司 应用商店的应用程序的上架方法、处理方法及计算机设备
CN115080102A (zh) * 2022-06-30 2022-09-20 北京亚控科技发展有限公司 应用管理方法及相关设备

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104854561B (zh) * 2012-10-16 2018-05-11 思杰系统有限公司 用于应用程序管理框架的应用程序封装
CN111475170B (zh) * 2012-12-12 2024-02-02 华为技术有限公司 多屏应用启用和分发服务
US20140359606A1 (en) * 2013-05-30 2014-12-04 Microsoft Corporation Bundle package retrieving
CN107329742B (zh) * 2017-06-14 2021-01-29 北京小米移动软件有限公司 软件开发工具包调用方法及装置
CN113486361B (zh) * 2021-07-27 2024-04-16 中国银行股份有限公司 基于区块链的app管理系统及方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160227343A1 (en) * 2013-06-04 2016-08-04 Qiongmao SHEN System and method for creating mobile application store
CN110060134A (zh) * 2019-04-26 2019-07-26 天津店主助手科技有限公司 App关联方法与系统、分享方法与系统、终端及介质
CN111539775A (zh) * 2020-05-07 2020-08-14 网易（杭州）网络有限公司 应用程序的管理方法及设备
CN113485722A (zh) * 2021-06-30 2021-10-08 北京鲸鲮信息系统技术有限公司 应用商店的应用程序的上架方法、处理方法及计算机设备
CN115080102A (zh) * 2022-06-30 2022-09-20 北京亚控科技发展有限公司 应用管理方法及相关设备

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
LIPAN: "Starting of Windows Phone 8 Study Notes (4) Application", CNBLOGS, 6 April 2008 (2008-04-06), pages 1 - 24, XP093122699, Retrieved from the Internet <URL:https://www.cnblogs.com/lipan/archive/2013/06/04/3080275.html> [retrieved on 20240123] *
See also references of EP4538869A4

Also Published As

Publication number Publication date
CN115080102A (zh) 2022-09-20
EP4538869A4 (en) 2025-10-01
US20250390312A1 (en) 2025-12-25
EP4538869A1 (en) 2025-04-16

Similar Documents

Publication Publication Date Title
WO2024002222A1 (zh) 应用管理方法及相关设备
CN111258773B (zh) 服务调用流程信息处理方法、装置及电子设备
CN112114894B (zh) 基于Activiti流程引擎的流程处理方法、装置及电子设备
CN108334387A (zh) 动态界面渲染方法及装置
CN110888736A (zh) 一种基于容器云平台的应用管理方法、系统及相关组件
CN106548261A (zh) 一种业务流程控制方法、装置及电子设备
CN111258567A (zh) 服务代码开发处理方法及装置
CN111258772A (zh) 服务调用信息处理方法、装置及系统
US20250390561A1 (en) Application authorization management method and related device
CN112785248A (zh) 人力资源数据跨组织交互方法、装置、设备和存储介质
CN111262897A (zh) 服务调用路由处理方法、装置及系统
CN110532493B (zh) 数据的处理方法及装置、存储介质和电子装置
CN118228978A (zh) 算力标识管理方法、装置、终端设备、存储介质及产品
CN116360918A (zh) 建模数据处理方法、装置、计算机设备和存储介质
EP4538881A1 (en) Virtual resource allocation method and related device
CN108696559B (zh) 流处理方法及装置
WO2024002217A1 (zh) 应用管理方法及相关设备
CN106961453A (zh) 基于tosca的服务调用方法及装置
CN113342461A (zh) 一种设备挂载方法、装置、计算机设备及可读存储介质
CN118672599A (zh) 应用部署系统、应用部署方法及装置
WO2024002302A1 (zh) 应用管理方法、应用订阅方法及相关设备
CN106559454B (zh) 资源访问方法、装置及系统
CN117114613A (zh) 一种业务流程控制的流程引擎、方法、设备及程序产品
CN109918147B (zh) OpenStack下驱动的扩展方法、装置、电子设备
CN116661767A (zh) 文件生成方法、装置、设备以及存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23830391

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 18879756

Country of ref document: US

WWE Wipo information: entry into national phase

Ref document number: 2023830391

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2023830391

Country of ref document: EP

Effective date: 20250107

NENP Non-entry into the national phase

Ref country code: DE

WWP Wipo information: published in national office

Ref document number: 2023830391

Country of ref document: EP