WO2017128964A1 - 一种应用融合方法及装置 - Google Patents

一种应用融合方法及装置 Download PDF

Info

Publication number
WO2017128964A1
WO2017128964A1 PCT/CN2017/071121 CN2017071121W WO2017128964A1 WO 2017128964 A1 WO2017128964 A1 WO 2017128964A1 CN 2017071121 W CN2017071121 W CN 2017071121W WO 2017128964 A1 WO2017128964 A1 WO 2017128964A1
Authority
WO
WIPO (PCT)
Prior art keywords
application
data
fusion
merged
fused
Prior art date
Application number
PCT/CN2017/071121
Other languages
English (en)
French (fr)
Inventor
陈善席
董明杰
Original Assignee
华为技术有限公司
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 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP17743579.9A priority Critical patent/EP3404536A4/en
Priority to BR112018015451-2A priority patent/BR112018015451A2/zh
Publication of WO2017128964A1 publication Critical patent/WO2017128964A1/zh
Priority to US16/047,629 priority patent/US10552233B2/en

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/61—Installation
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • 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/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • G06F9/541—Interprogram communication via adapters, e.g. between incompatible applications
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/28—Databases characterised by their database models, e.g. relational or object models
    • G06F16/284—Relational databases
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/70—Software maintenance or management
    • G06F8/72—Code refactoring
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR 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
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR 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/451—Execution arrangements for user interfaces
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR 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/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/70—Software maintenance or management
    • G06F8/74—Reverse engineering; Extracting design information from source code

Definitions

  • the present invention relates to the field of intelligent terminal technologies, and in particular, to an application fusion method and apparatus.
  • the colorful application (Application, APP for short) on the smart terminal has changed the entertainment, life or working style of the user to a large extent.
  • the installation of a large number of APPs has caused a lot of inconvenience to users. So many APPs are installed on the terminals, which are complicated and complicated, and there are many APPs that have the same functions, which brings a lot of inconvenience to users.
  • Apple's Siri voice digital assistant which uses the Siri voice tool software as an entry point to analyze the voice semantics and call other APPs to complete the required actions.
  • the results of the execution are displayed to the user.
  • Such a voice digital assistant can implement the call of the APP, such a voice digital assistant is solidified inside the operating system, and not any one of the APPs can be used as a digital assistant, and the user cannot decide which APP to call.
  • the embodiment of the invention provides an application fusion method and device, so as to implement fusion of any multiple applications according to an application fusion operation request.
  • an application convergence method including: registering, by using a plurality of fusion parameter interfaces, a plurality of fusion parameters of each application, where the multiple fusion parameters include: a format of data of each application, and each application a logical relationship between the data; when receiving the fusion operation request, acquiring, by the multiple fusion parameter interfaces, multiple fusion parameters of the multiple applications, and multiple fusion parameters of the acquired multiple applications The fusion is performed separately to obtain the logical relationship of the merged application and the format of the data.
  • the operating system provides multiple fusion parameter interfaces to the application, and the application registers a plurality of fusion parameters through the fusion parameter interface during installation, and some of the fusion parameters may be used to indicate the application. Whether the fusion parameter can be used, and another part of the fusion parameter can be used to indicate the required information such as the data format or the interface display format after the application is merged. Of course, the above fusion parameter type can also have one of them. In this way, the operating system can obtain the fusion parameters of multiple applications, and when the fusion requirements are received, the application fusion is performed according to the fusion parameters of the applications that need to be merged.
  • the fused application may be a stand-alone application having its own unique application interface.
  • the application icon may be a newly generated one different from the multiple applications before the merging.
  • the application after the icon may be a brand new interface; in other embodiments of the present invention, the merged application may also be one of a plurality of applications that need to be merged, and the data information of other applications passes through the application and the The interface of the application is displayed, for example, after the mapping application and the social application are merged, the geographic location information of the social application is integrated on the map of the map application, etc.
  • when the merged application is not used It does not show that the data processed by the application is displayed only when the user or other application uses the function of the merged application.
  • the installation of the application may not be performed in the operating system, and the icon of the application is not displayed on the user interface, but the fusion of the application may be completed by registering multiple fusion parameters through the fusion parameter interface;
  • the installation of the application in the operating system displays the icon of the application on the user interface.
  • the Fusion parameter interface is used to register multiple fusion parameters, and the user receives the fusion operation request from the user to perform the application fusion operation.
  • the method further includes: determining a presentation interface of the merged application.
  • the application is installed in the operating system, and the icon of the application is displayed on the user interface, and after the application is merged, the merged application also has a corresponding display interface.
  • the step of performing the fusion to obtain the logical relationship of the merged application, the format of the data, and the order of the two steps are not sequential.
  • the multiple convergence parameters further include information about the convergence of the data of each application;
  • the method further includes: acquiring data of the merged application according to the fusibility definition information of the data of each application; and displaying, according to the data of the merged application, on the display interface of the merged application The logical relationship and the format of the data output the data of the merged application.
  • the data format of each application uses multiple two-dimensional tables to describe data of each application
  • the logical relationship between the data of each application includes a relationship between the plurality of two-dimensional tables, a basic data table and a top-level data table in the plurality of two-dimensional tables, and data of each of the applications may be
  • the fusion-qualified information includes information in each application's data that supports fusion and/or does not support fused data.
  • the method further includes:
  • the receiving, by the user, the fused operation request for the multiple applications includes: receiving an operation request that the user drags the multiple applications to the target application, where the fused application is the a target application, the target application being one of the plurality of applications; or receiving an operation request by the user to drag the plurality of applications to an empty location to create a new application, wherein the merged Apply the new app created as described.
  • the receiving, by the user, a fusion operation request for multiple applications includes: receiving, by the user, a request for selecting the multiple applications and the merged application in an application list, the merged application An application for the one of the plurality of applications, or an application other than the plurality of applications in the application list.
  • the operation is simple and convenient by selecting an application in the application list for fusion.
  • the method further includes: checking whether the multiple fused parameter interfaces meet the fused specification; if the result of the checking is that the fused specification is not met, requesting, by the application center, the multiple fused parameter interfaces that meet the fused specification An application installation package; if the application installation package exists in the application center, downloading the application installation package; if the application installation package does not exist in the application center, proceeding in the application center Decoding the multiple fusion parameter interfaces, compiling the application source code, and after generating the application installation package, downloading the application installation package; Downloading the application installation package.
  • the fusion parameter interface is adapted to conform to the fusion specification, and the fusion parameter in the fusion parameter interface can be invoked to perform application fusion.
  • the method further
  • the plurality of fused parameter interfaces respectively register a logical relationship between the data of the fused application, a format of the data of the fused application, and/or a condensability of the data of the fused application.
  • an application fusion device having a function of implementing the behavior of the application fusion device in the above method.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • an application convergence device including: a registration unit, configured to register multiple fusion parameters of each application through multiple fusion parameter interfaces, where the multiple fusion parameters include: each application a format of the data, a logical relationship between the data of each application; a merging unit, configured to acquire, by the plurality of fused parameter interfaces, multiple fused parameters of the multiple applications, respectively, when receiving the fused operation request And acquiring the plurality of fusion parameters of the plurality of applications respectively, and obtaining a logical relationship of the merged application and a format of the data.
  • an application fusion device including: an input device, an input device, a memory, and a processor; and the processor is configured to: through multiple fusion parameter interfaces through a program or instruction in a memory Registering a plurality of fusion parameters of each application, the plurality of fusion parameters including: a format of data of each application, a logical relationship between data of each application; and when receiving the fusion operation request, by the plurality of The fused parameter interface obtains multiple fused parameters of the multiple applications, and respectively fuses the obtained multiple fused parameters of the multiple applications to obtain a logical relationship and a data format of the fused application.
  • 1 is a schematic structural diagram of a terminal device
  • FIG. 2 is a schematic flowchart of an application convergence method according to an embodiment of the present invention.
  • FIG. 3 is a schematic flowchart of another application convergence method according to an embodiment of the present disclosure.
  • FIG. 4 is a schematic diagram of compatibility adaptation of an application interface after an application center is implemented according to an embodiment of the present disclosure
  • FIG. 5 is a schematic structural diagram of an application fusion device according to an embodiment of the present disclosure.
  • FIG. 6 is a schematic structural diagram of another application fusion device according to an embodiment of the present disclosure.
  • FIG. 7 is a schematic structural diagram of another terminal device according to an embodiment of the present disclosure.
  • FIG. 8 is a schematic structural diagram of still another terminal device according to an embodiment of the present invention.
  • FIG. 1 is a schematic structural diagram of a terminal device.
  • the computing node may be a terminal device, and the terminal device may specifically be a smart phone.
  • the hardware layer of the terminal device includes a CPU, an input device, and the like, and may further include a memory, an output device, a memory, a memory controller, a network interface, and the like.
  • the input device may include a keyboard, a mouse, a touch screen, and the like, and the output may be Devices may include display devices such as LCDs, CRTs, Holographics, Projectors, and the like. Above the hardware layer you can run an operating system (such as Android) and some applications.
  • an operating system such as Android
  • the core library is the core part of the operating system, including input/output services, core services, fusion parameter interfaces, and application convergence services.
  • the terminal further includes a driving layer, a frame layer, and an application layer.
  • the driver layer may include a CPU driver, a display controller driver, and the like.
  • the framework layer may include a fusion parameter registration service or the like.
  • the application layer may include a Graphical User Interface (GUI), an application list, a browser, and the like. It should be understood that the logical structure of the execution body of the method of the embodiment of the present invention can be referred to FIG.
  • GUI Graphical User Interface
  • FIG. 2 is a schematic flowchart of an application convergence method according to an embodiment of the present disclosure, where the method includes the following steps:
  • the operating system enhances and refines the application installation process, and provides a plurality of fusion parameter interface provisioning programs to be invoked during installation to receive registration of multiple fusion parameters of each application.
  • the various fusion parameters here include the format of the data for each application and the logical relationship between the data for each application.
  • the application can register the format of the data of each application through the data format registration interface, and can register the logical relationship between the data of each application through the data logical relationship registration interface.
  • the format of the data of each application describes data of each application by using a plurality of two-dimensional tables, and the logical relationship between the data of each application includes a relationship between the plurality of two-dimensional tables, the plurality of Basic data table in a two-dimensional table And top-level data tables.
  • the fusion parameter may further include: a data generation rule and a data reading rule, and the data generation rule refers to an execution body or a program segment that generates data in a registration format in the data generation process.
  • the data reading rule refers to reading the data content saved in the form of a two-dimensional data table in the registration format during the data extraction/reading process.
  • the user may choose to merge any of the installed applications on the terminal to receive the user's request for the fusion operation of the selected application.
  • multiple fusion parameters of multiple applications to be merged can be obtained through multiple fusion parameter interfaces.
  • a format of data of multiple applications is acquired through a data format registration interface
  • a logical relationship between data of multiple applications is acquired through a data logical relationship registration interface.
  • the multiple fusion parameters of the acquired multiple applications are respectively fused to obtain the logical relationship and data format of the merged application.
  • the data format registration interface is used to obtain data formats of multiple applications, check the convergence of data formats of multiple applications, obtain a fused data format, and use the data format of the fused application; register the interface through the data logical relationship. Obtain a logical relationship between data of multiple applications to determine a logical relationship between data of the merged application.
  • the installation of the application may not be performed in the operating system, and the icon of the application may not be displayed in the user interface, but the fusion of the application may be completed by registering multiple fusion parameters through the fusion parameter interface;
  • the application is installed, and the icon of the application is displayed on the user interface.
  • a plurality of fusion parameters are registered through the fusion parameter interface, and the user's fusion operation request to the application is received, and the application fusion operation is performed.
  • An application convergence method provides a plurality of fusion parameters registered by the application through the fusion parameter interface, thereby receiving the fusion of multiple applications within the user or the device.
  • multiple fusion parameters of multiple applications are obtained from multiple fusion parameter interfaces, and multiple fusion parameters of multiple applications are respectively fused, thereby realizing fusion of any multiple applications.
  • FIG. 3 is a schematic flowchart of another application convergence method according to an embodiment of the present disclosure, where the method includes the following steps:
  • the operating system enhances and refines the application installation process, and provides a plurality of fusion parameter interface provisioning programs to be invoked during installation to receive registration of multiple fusion parameters of each application.
  • the various fusion parameters here include: the format of the data of each application, the logical relationship between the data of each application, and the fusion of the data of each application.
  • the application can register the format of the data of each application through the data format registration interface, and can register the logical relationship between the data of each application through the data logical relationship registration interface, and can register the data of each application through the convergence-limited registration interface.
  • the fusion can be used to define information.
  • the above multiple fusion parameters can also be registered through the same interface.
  • the format of the data of each application describes data of each application by using a plurality of two-dimensional tables, and the logical relationship between the data of each application includes a relationship between the plurality of two-dimensional tables, the plurality of The basic data table and the top-level data table in the two-dimensional table, the fusibility definition information of the data of each application includes information of data of each application that supports fusion and/or does not support fusion.
  • the fusion parameter may further include: a data generation rule and a data reading rule, and the data generation rule refers to the data generation In the process of generating data, the executable or program fragment of the data is generated in the registration format.
  • the data reading rule refers to reading the data content saved in the form of a two-dimensional data table in the registration format during the data extraction/reading process.
  • the plurality of fusion parameters received through the respective fusion parameter interfaces are respectively stored in a plurality of storage spaces of the operating system for being invoked when the operating system performs application fusion.
  • S203 Receive an operation request for creating a new application by the user dragging the multiple applications to an empty location.
  • the merged application is the created new application.
  • the user may choose to merge any of the installed applications on the terminal, and the device receives the user's request for the fusion operation of the selected application.
  • Dragging the app icon directly causes the fusion trigger.
  • the dragging includes dragging multiple applications to an empty location, creating a new application at the empty location, and the merged application is the new application created.
  • the S203 may be an operation request for receiving the user to drag the multiple applications to the target application, where the merged application is the target application, and the target application is One of the plurality of applications.
  • the above drag mode is based on the terminal desktop providing, for example, a graphical user interface, so that the user can drag the application icon directly on the desktop.
  • the application fusion is realized by dragging the application, and the operation is simple and convenient.
  • the S203 may be configured to receive, by the user, a request for selecting the multiple applications and the merged application in an application list, where the merged application is in the multiple applications.
  • An application or an application other than the plurality of applications in the application list. You can select an application to be merged in the application list.
  • the application list only lists the identifiers of multiple applications for selection. The user can select the merged application as one of the multiple applications, or the application list is excluded.
  • the operation is simple and convenient by selecting an application in the application list for fusion.
  • FIG. 4 is a schematic diagram of the application interface compatibility adaptation of the application center after the convergence of the application center according to the embodiment of the present invention.
  • multiple fusion parameter interfaces need to be checked. Whether it meets the integration specification.
  • the operating system's convergence specification is not met, stop the convergence, and then request the application installation package that meets the convergence specification from the application center (such as App store or App market); if the application market does not have the application installation package that meets the convergence specification, then Recompile the application source code through the corresponding interface adaptation, generate a new application installation package; then receive notifications of application installations that meet the specifications and requirements, obtain the corresponding application installation package, and reinstall the downloaded application Install the package; if the application installation package exists in the application center, download the installation directly Describe the application installation package and install it.
  • the application center such as App store or App market
  • the attributes of the application include: a social relationship attribute, a time relationship attribute, a transaction arrangement type attribute, an exchange determined type attribute, etc., according to the attribute of the application, the interface display parameter of the merged application can be determined, thereby generating a corresponding according to the interface display parameter.
  • Display interface the device may save an interface template generated according to the attributes of the different applications, and corresponding to the application attributes of the application to be merged, and selecting the corresponding interface template.
  • the user may choose to merge any of the installed applications on the terminal to receive the user's request for the fusion operation of the selected application.
  • multiple fusion parameters of multiple applications to be merged can be obtained through multiple fusion parameter interfaces.
  • a format of data of multiple applications is acquired through a data format registration interface
  • a logical relationship between data of multiple applications is acquired through a data logical relationship registration interface.
  • the multiple fusion parameters of the acquired multiple applications are respectively fused to obtain the logical relationship and data format of the merged application.
  • the data format registration interface is used to obtain data formats of multiple applications, check the convergence of data formats of multiple applications, obtain a fused data format, and use the data format of the fused application; register the interface through the data logical relationship. Obtain a logical relationship between data of multiple applications to determine a logical relationship between data of the merged application.
  • the data of the merged application is obtained according to the fusibility definition information acquired from the fusion parameter interface. That is, get the data that is available in each application.
  • the acquired data is processed according to the logical relationship between the format of the generated merged application data and the data, and is output on the display interface of the merged application.
  • a new data format may be generated, with a new logical relationship between the data, a new data generation rule and a data reading rule. Therefore, it is necessary to register the fusion in multiple fusion parameter interfaces.
  • An application convergence method provides a plurality of fusion parameters registered by the application through the fusion parameter interface, thereby receiving the fusion of multiple applications within the user or the device.
  • multiple fusion parameters of multiple applications are obtained from multiple fusion parameter interfaces, and multiple fusion parameters of multiple applications are respectively fused, thereby realizing integration of any multiple applications; and implementing multiple applications
  • the interworking of the data; and the application fusion by dragging the application, the operation is simple and convenient.
  • the application fusion of the first application and the second application is taken as an example for illustration.
  • the operating system enhances and refines the application installation process, especially the format of the data registered in the storage area of the operating system, the logical relationship of the data, and the conformability limiting information, and may also include data generation rules. , data reading rules.
  • the registration of this information was not available in previous operating systems.
  • the operational forms and requirements on the graphical interface are not considered.
  • the operating system enables application fusion
  • the operating system provides a registration interface and storage space during the installation phase of the application to receive the initialization of the application, that is, the operating system provides multiple fusion parameter interfaces, and the application program is called during installation to associate the application's own data with other related Information is registered to the operating system's storage space.
  • These interfaces include:
  • A.genInitialData() The installation process generates initial data, that is, generates metadata about the application (Metadata), which is a preview summary table, including basic information of the fusion parameters of multiple applications.
  • Metadata a preview summary table, including basic information of the fusion parameters of multiple applications.
  • the column form requirements for these Metadata are as follows:
  • B.regDataEncoder() Registration of the data generation interface. Calling this interface during the installation process, you can register the executable or program fragment that generates data in the registered format during the data generation process.
  • C.regDateDecoder() Registration of the data read interface. This interface is called during the installation process, and it is possible to register the data content saved in the form of a two-dimensional data table in the registration format during the data extraction/reading process.
  • D.regDataFormat() The registration interface for the format of the data. This interface is called during the installation process to register the format of the data generated by the application.
  • One approach is that the data format uses a series of two-dimensional tables. Each table has a table name, and the table defines a set of key names to form a column. Each table and key name here, correspondingly, has an array (tuple) consisting of a set of key names during the initial data filling phase (when genInitialData is called) and during the application data generation phase during normal use. A tuple's data sheet.
  • E.regDataBusinessLogic The registration of the business logic embodied in the data. Calling this interface during the installation process, you can register the business logic of the application data, that is, the relationship between the tables of each two-dimensional data table, the basic hierarchical relationship of the data, the presentation level when providing the service to the user, etc., indicating the data application and the business relationship.
  • the "logical" information The column form requirements for these business logic tables are as follows:
  • F.regDataTranferRight() specifies the registration of the fusion-qualified information of the relevant data. Calling this interface during the installation process will specify the fusibility of this application data.
  • This "data fusion" can be that all data of the entire application does not support convergence, or some data support can be fused, or some data does not support fusion, or other fusion limitations and requirements.
  • the difference between the first application and the second application in the installation process compared to the previous operating system reflects the final support for the integration.
  • the first application is, for example, a friend application.
  • the details of invoking the corresponding device interface registration fusion parameter are as follows:
  • the first application has a total of 5 data tables, ⁇ 1, 2, 3, 4, 5 ⁇ / table name of the first application of the application, ⁇ 1, 2, 3 ⁇ / data is prioritized by server data, ⁇ 4, 5 ⁇ / data is only used in the local table ⁇ .
  • the data area I of the device saves multiple parsing interfaces and interface usage rules of the first application application, and the two key interfaces are the first application DataFromTables. () with set first application DataIntoTables().
  • the former is used to provide data from a data table, and the latter is used to write certain data to a data table for permanent storage as a record.
  • the first application installer calls regDataFormat to generate and save the data Metadata of the first application application in the data area II of the operating system:
  • Table ⁇ goodfriendid/friend ID, friendname/friend name, friendnickyname/friend nickname ⁇ is used to record the basic information of the first application user;
  • D.4 table ⁇ goodfriendid/friend ID, Settings / number of settings for friend permissions, lstRights / permission setting type ⁇ is used to record the user's viewing permission settings for "friends";
  • D.5 table ⁇ sortInGUI/interface display order, goodfriendid/friend ID ⁇ is used to record the user's settings for the running interface.
  • the first application installer generates and saves a set of records of the "business logic space" in the data area III of the operating system.
  • E.1 ⁇ 12321 / device assigned to the first application's application ID, 2 / application first application has two basic data tables, ⁇ 1, 2 ⁇ / application first application's underlying data table table name ⁇ ;
  • the first application installer calls regDataTranferRight, and generates and saves the record in the data area IV of the operating system: ⁇ 12321/application ID assigned to the first application, 2/installer restricts the second application to the first application
  • the second application is a map application
  • the application second application is in the installation process
  • the details of invoking the corresponding device interface registration fusion parameter are as follows:
  • the second application installer calls the genInitialData interface to generate and save the application metadata in the data area II of the operating system:
  • the second application has a total of 2 data tables, ⁇ 1, 2, 3 ⁇ / application table name of the second application, ⁇ 1, 2 ⁇ /Data is prioritized by server data, ⁇ 3 ⁇ /data only uses ⁇ saved in local table.
  • the second application installer calls regDataEncoder and regDateDecoder respectively, and generates and saves multiple parsing interfaces and interface usage rules of the second application application in the data area I of the operating system, wherein the two key interfaces are getAMPDataFromTables() With setAMPDataIntoTables().
  • the former is used to display the user's path record results, and the latter is used to write the user's path record to the history.
  • D.0 Record the data record of how many data tables the second application will use, ⁇ 32123/application ID assigned to the second application, 123456789/random ID assigned to the user by the device, 3/application will use three data tables , ⁇ , ⁇ , ⁇ /record the addresses in three data table formats, ⁇ , ⁇ , ⁇ /record the address of three table data ⁇ used as a basic description of the following table;
  • the following data table definitions and formats are generated and saved in the data area II of the operating system:
  • D.1 Table ⁇ pointSerial/path point number, datetime/time, longitude/longitude, latitude/latitude ⁇ is used to record the user's path point information based on time + location;
  • D.2 Table ⁇ pointSerial/path point number, longPOI/item number on the path point ⁇ is used to record the user's "association" of the item of interest based on the path point;
  • D.3 table ⁇ pointSerial/path point serial number, typePresent/path point map interface display type ⁇ is used to record the location and method of the last time the user used the map;
  • the second application installer generates and saves a set of records of the "business logic space" in the data area III of the operating system.
  • E.1 ⁇ 32123/device assigned to the application ID of the second application, 2/application second application has two basic data tables, ⁇ 1, 2 ⁇ / application second application base data table table name ⁇ ;
  • E.2 ⁇ 32123 / device assigned to the second application's application ID, 1 / application second application has a top-level data table, ⁇ 3 ⁇ / application second application's top-level data table table name ⁇ ;
  • E.3 ⁇ 32123/Application ID assigned to the second application by the device 2/Application second application data usage layer number is 2, ⁇ 1, 2 ⁇ , ⁇ 3 ⁇ / application second application data table Relationship matrix ⁇ .
  • the second application installer calls regDataTranferRight, and generates and saves the record in the data area IV of the operating system: ⁇ 32123/ the application ID assigned by the device to the second application, and the NULL/installer defines the application data table as a fusion. The number is 0 ⁇ .
  • the "friend information" of the first application of the application has a limitation that is not transferable in the fusion, that is, the fusion of the first application includes:
  • the G.2 merged new application can read the "friend" relationship using the data interface inherited from the application first application (including the use of the original application's digital certificate);
  • the G.3 merged new application can modify the "friend" relationship using the data interface inherited from the application first application (including the use of the original application's digital certificate);
  • the G.4 fused new application can use the data interface inherited from the application first application (including the use of the original application's digital certificate) data interface to increase the "friend" relationship.
  • the device gives the basic data item options for the new application "Friends Map” and the top-level data item options for the application "Friends Map", which are determined by the user.
  • the device gives the business logic and content options and suggestions reflected by the data table relationship of the new application "buddy map";
  • the interface displays parameters.
  • the user selects and confirms a map as a basic interface, and the user (differs depending on the constraint G.2-G.5, and the user selects the inherited content) and the history and even the current location information of the friend as A new application that presents content and results, for example, the second application is a map application.
  • N N.
  • obtaining a data generation rule of the third application registering a data generation rule of the third application by using a regDataEncoder() interface, and reading data according to the first application and the second application Take the rule, obtain the data reading rule of the third application, and register the data reading rule of the third application through the regDateDecoder() interface.
  • this third application allows the user to show "when", “where” and “who” have a “what way” and
  • the interaction of "what content" for example, the second application is a map application; or
  • the third application can also aggregate interaction with friends based on a geographical scope, Or aggregate interactions with friends based on a time range, or show interactions with friends by geographic location, or show interactions with friends based on timeline relationships.
  • FIG. 5 is a schematic structural diagram of an application fusion device according to an embodiment of the present disclosure, where the device 1000 includes:
  • the registration unit 11 is configured to register multiple fusion parameters of each application through multiple fusion parameter interfaces when multiple applications are installed.
  • the operating system enhances and refines the application installation process, and provides a plurality of fusion parameter interface provisioning programs to be invoked during installation to receive registration of multiple fusion parameters of each application.
  • the various fusion parameters here include the format of the data for each application and the logical relationship between the data for each application.
  • the application can register the format of the data of each application through the data format registration interface, and can register the logical relationship between the data of each application through the data logical relationship registration interface.
  • the format of the data of each application describes data of each application by using a plurality of two-dimensional tables, each application
  • the logical relationship between the data includes a relationship between the plurality of two-dimensional tables, an underlying data table and a top-level data table in the plurality of two-dimensional tables.
  • the fusion parameter may further include: a data generation rule and a data reading rule, and the data generation rule refers to an execution body or a program segment that generates data in a registration format in the data generation process.
  • the data reading rule refers to reading the data content saved in the form of a two-dimensional data table in the registration format during the data extraction/reading process.
  • the merging unit 12 is configured to: when receiving a fusion operation request of the user for multiple applications, determine a display interface of the merged application, and obtain multiple fusion parameters of the multiple applications by using the multiple fusion parameter interfaces And acquiring the plurality of fusion parameters of the plurality of applications respectively, and obtaining a logical relationship of the merged application and a format of the data.
  • the user may choose to merge any of the installed applications on the terminal to receive the user's request for the fusion operation of the selected application.
  • multiple fusion parameters of multiple applications to be merged can be obtained through multiple fusion parameter interfaces.
  • a format of data of multiple applications is acquired through a data format registration interface
  • a logical relationship between data of multiple applications is acquired through a data logical relationship registration interface.
  • the multiple fusion parameters of the acquired multiple applications are respectively fused to obtain the logical relationship and data format of the merged application.
  • the data format registration interface is used to obtain data formats of multiple applications, check the convergence of data formats of multiple applications, obtain a fused data format, and use the data format of the fused application; register the interface through the data logical relationship. Obtain a logical relationship between data of multiple applications to determine a logical relationship between data of the merged application.
  • the installation of the application may not be performed in the operating system, and the icon of the application may not be displayed in the user interface, but the fusion of the application may be completed by registering multiple fusion parameters through the fusion parameter interface;
  • the application is installed, and the icon of the application is displayed on the user interface.
  • a plurality of fusion parameters are registered through the fusion parameter interface, and the user's fusion operation request to the application is received, and the application fusion operation is performed.
  • An application convergence device provides a plurality of fusion parameters registered by the application through the fusion parameter interface, thereby receiving a fusion of multiple applications within the user or the device.
  • multiple fusion parameters of multiple applications are obtained from multiple fusion parameter interfaces, and multiple fusion parameters of multiple applications are respectively fused, thereby realizing fusion of any multiple applications.
  • FIG. 6 is a schematic structural diagram of another application fusion device according to an embodiment of the present disclosure, where the device 2000 includes:
  • the registration unit 20 is configured to register multiple fusion parameters of each application through multiple fusion parameter interfaces when multiple applications are installed.
  • the operating system enhances and refines the application installation process, and provides a plurality of fusion parameter interface provisioning programs to be invoked during installation to receive registration of multiple fusion parameters of each application.
  • the various fusion parameters here include: the format of the data of each application, the logical relationship between the data of each application, and the fusion of the data of each application.
  • the application can register the format of the data of each application through the data format registration interface, and can register the logical relationship between the data of each application through the data logical relationship registration interface, and can register the data of each application through the convergence-limited registration interface.
  • the fusion can be used to define information.
  • the above multiple fusion parameters can also be registered through the same interface.
  • the format of the data of each application describes data of each application by using a plurality of two-dimensional tables, and the logical relationship between the data of each application includes a relationship between the plurality of two-dimensional tables, the plurality of The basic data table and the top-level data table in the two-dimensional table, the fusibility definition information of the data of each application includes information of data of each application that supports fusion and/or does not support fusion.
  • the fusion parameter may further include: a data generation rule and a data reading rule, and the data generation rule refers to an execution body or a program segment that generates data in a registration format in the data generation process.
  • the data reading rule refers to reading the data content saved in the form of a two-dimensional data table in the registration format during the data extraction/reading process.
  • the storage unit 21 is configured to separately store multiple fusion parameters of each application into one storage space of the operating system.
  • the plurality of fusion parameters received through the respective fusion parameter interfaces are respectively stored in a plurality of storage spaces of the operating system for being invoked when the operating system performs application fusion.
  • the first receiving unit 22 is configured to receive an operation request for creating a new application by the user dragging the multiple applications to an empty location.
  • the merged application is the created new application.
  • the user may choose to merge any of the installed applications on the terminal, and the device receives the user's request for the fusion operation of the selected application.
  • Dragging the app icon directly causes the fusion trigger.
  • the dragging includes dragging multiple applications to an empty location, creating a new application at the empty location, and the merged application is the new application created.
  • the first receiving unit 22 is further configured to receive an operation request that the user drags the multiple applications to the target application, where the merged application is the target application, where The target application is one of the plurality of applications.
  • the above drag mode is based on the terminal desktop providing, for example, a graphical user interface, so that the user can drag the application icon directly on the desktop.
  • the application fusion is realized by dragging the application, and the operation is simple and convenient.
  • the second receiving unit is further configured to receive, by the user, a request for the user to select the multiple applications and the merged application in an application list, where
  • the merged application is one of the plurality of applications, or is one of the application list except the plurality of applications. You can select an application to be merged in the application list.
  • the application list only lists the identifiers of multiple applications for selection. The user can select the merged application as one of the multiple applications, or the application list is excluded.
  • the operation is simple and convenient by selecting an application in the application list for fusion.
  • the checking unit 23 is configured to check whether the multiple fusion parameter interfaces meet the fusion specification.
  • the requesting unit 24 is configured to request, from the application center, an application installation package that includes multiple fusion parameter interfaces that meet the fusion specification.
  • the downloading unit 25 is configured to download the application installation package if the application installation package exists in the application center; or
  • the downloading unit 25 is configured to: if the application installation package does not exist in the application center, compile the application source code by using the adaptation of the multiple fusion parameter interfaces in the application center, and generate the application program After installing the package, download the application installation package.
  • the installation unit 26 is configured to install the downloaded application installation package.
  • FIG. 4 is a schematic diagram of application interface compatibility adaptation after an application center is implemented by an application center according to an embodiment of the present invention.
  • it is also necessary to check whether multiple fusion parameter interfaces meet the fusion specification.
  • the operating system's convergence specification is not met, stop the convergence, and then request the application installation package that meets the convergence specification from the application center (such as App store or App market); if the application market does not have the application installation package that meets the convergence specification, then Recompile the application source code through the corresponding interface adaptation, generate a new application installation package; then receive notifications of application installations that meet the specifications and requirements, obtain the corresponding application installation package, and reinstall the downloaded application Install the package; if the application installation package exists in the application center, directly download the application installation package and install it.
  • the application installation package that meets the convergence specification from the application center (such as App store or App market)
  • the application market does not have the application installation package that meets the convergence specification
  • Recompile the application source code through the corresponding interface adaptation, generate a new application installation package; then receive notifications of application installations that meet the specifications and requirements, obtain the corresponding application installation package, and reinstall the downloaded application Install the package; if the application installation package exists in the application center, directly download the application installation package and install it.
  • the merging unit 27 is configured to: when receiving a fusion operation request of the user for multiple applications, determine a display interface of the merged application, and obtain multiple fusion parameters of the multiple applications by using the multiple fusion parameter interfaces And acquiring the plurality of fusion parameters of the plurality of applications respectively, and obtaining a logical relationship of the merged application and a format of the data.
  • the attributes of the application include: a social relationship attribute, a time relationship attribute, a transaction arrangement type attribute, an exchange determined type attribute, etc., according to the attribute of the application, the interface display parameter of the merged application can be determined, thereby generating a corresponding according to the interface display parameter.
  • Display interface the device may save an interface template generated according to the attributes of the different applications, and corresponding to the application attributes of the application to be merged, and selecting the corresponding interface template.
  • the user may choose to merge any of the installed applications on the terminal to receive the user's request for the fusion operation of the selected application.
  • multiple fusion parameters of multiple applications to be merged can be obtained through multiple fusion parameter interfaces.
  • a format of data of multiple applications is acquired through a data format registration interface
  • a logical relationship between data of multiple applications is acquired through a data logical relationship registration interface.
  • the multiple fusion parameters of the acquired multiple applications are respectively fused to obtain the logical relationship and data format of the merged application.
  • the data format registration interface is used to obtain data formats of multiple applications, check the convergence of data formats of multiple applications, obtain a fused data format, and use the data format of the fused application; register the interface through the data logical relationship. Obtain a logical relationship between data of multiple applications to determine a logical relationship between data of the merged application.
  • the obtaining unit 28 is configured to acquire data of the merged application according to the fusibility definition information of the data of each application.
  • the data of the merged application is obtained according to the fusibility definition information acquired from the fusion parameter interface. That is, get the data that is available in each application.
  • the output unit 29 is configured to output data of the merged application according to a format of the data of the merged application and a logical relationship between the data on the display interface of the merged application.
  • the acquired data is processed according to the logical relationship between the format of the generated merged application data and the data, and is output on the display interface of the merged application.
  • the registration unit 20 is further configured to separately register, by using the multiple fusion parameter interfaces, a logical relationship between the data of the merged application, a format of the data of the merged application, and/or the merged application.
  • the fusion of data can define information.
  • a new data format may be generated, with a new logical relationship between the data, a new data generation rule and a data reading rule. Therefore, it is necessary to register the fusion in multiple fusion parameter interfaces.
  • the combined application can also be merged with other applications as a raw application.
  • An application convergence device provides a plurality of fusion parameters registered by the application through the fusion parameter interface, thereby receiving a fusion of multiple applications within the user or the device.
  • multiple fusion parameters of multiple applications are obtained from multiple fusion parameter interfaces, and multiple fusion parameters of multiple applications are respectively fused, thereby realizing integration of any multiple applications; and implementing multiple applications
  • the interworking of the data; and the application fusion by dragging the application, the operation is simple and convenient.
  • FIG. 7 illustrates a structure of another terminal device 3000 according to an embodiment of the present invention.
  • the terminal device 3000 includes: at least one processor 31, at least one network interface 34 or other user interface 33, a memory 35, and at least one communication bus 32. .
  • Communication bus 32 is used to implement connection communication between these components.
  • the terminal device 30 optionally includes a user interface 33, including a display (eg, a touch screen, LCD, CRT, Holographic or Projector, etc.), a keyboard or a pointing device (eg, a mouse, a trackball) , touch panel or touch screen, etc.).
  • a display eg, a touch screen, LCD, CRT, Holographic or Projector, etc.
  • a keyboard or a pointing device eg, a mouse, a trackball
  • the memory 35 can include read only memory and random access memory and provides instructions and data to the processor 31. A portion of the memory 35 may also include non-volatile random access memory (NVRAM).
  • NVRAM non-volatile random access memory
  • memory 35 stores elements, executable modules or data structures, or a subset thereof, or their extension set:
  • the operating system 351 includes various device programs and multiple fusion parameter interfaces in the embodiment, such as the framework layer, the core library layer, the driver layer, and the like shown in FIG. 1 for implementing various basic services and processing hardware-based task;
  • the application module 352 includes various application programs, such as a graphical user interface, an application list, a browser, and the like shown in FIG. 1 for implementing various application services.
  • the processor 31 by calling a program or instruction stored in the memory 35, the processor 31 is configured to: when multiple applications are installed, register multiple fusion parameters of each application through multiple fusion parameter interfaces, the multiple The fusion parameter includes: a format of data of each application, a logical relationship between data of each application; and when receiving a fusion operation request of the user for multiple applications, determining a display interface of the merged application, by using the multiple And a plurality of fusion parameters of the plurality of applications are respectively obtained by the fusion parameter interface, and the plurality of fusion parameters of the plurality of applications are respectively merged to obtain a logical relationship and a data format of the merged application.
  • the multiple convergence parameters further include fusibility definition information of data of each application; the processor 31 is further configured to: combine, according to data of each application Defining the information, and acquiring the data of the merged application; and displaying the data of the merged application according to the logical relationship of the merged application and the format of the data on the display interface of the merged application.
  • the format of the data of each application describes data of each application by using a plurality of two-dimensional tables, and the logical relationship between the data of each application includes a relationship between the plurality of two-dimensional tables,
  • the base data table and the top-level data table of the plurality of two-dimensional tables, the fusibility-defining information of the data of each application includes information of data of each application that supports fusion and/or does not support fusion.
  • processor 31 is further configured to separately store multiple fusion parameters of each application into one storage space of the operating system.
  • the processor 31 is further configured to: receive, by the user, the operation of dragging the multiple applications to the target application Making a request, wherein the merged application is the target application, the target application is one of the plurality of applications; or receiving the user to drag the plurality of applications to an empty location An operation request for creating a new application, wherein the merged application is the created new application.
  • the processor 31 is further configured to: receive, by the user, a request for selecting the multiple applications and the merged application in an application list, where the merged application is in the multiple applications An application, or an application other than the plurality of applications in the application list.
  • processor 31 is further configured to: check whether the multiple fusion parameter interfaces meet the fusion specification;
  • the application center is requested to request an application installation package that includes multiple fusion parameter interfaces that meet the fusion specification;
  • the processor 31 is further configured to separately register, by using the multiple fusion parameter interfaces, a logical relationship between data of the fused application, a format of the data of the fused application, and/or The fusibility of the data of the merged application defines information.
  • terminal device 30 can also perform the method and the embodiment of FIG. 2 to FIG. 3, and details are not described herein again.
  • the embodiment of the invention relates to a terminal device 4000 and a method for application convergence.
  • the terminal device 4000 can be a mobile phone, a tablet computer, a PDA (Personal Digital Assistant), a POS (Point of Sales), or Car computer, etc.
  • FIG. 8 is a schematic structural diagram of a terminal device 4000 according to an embodiment of the present invention.
  • another terminal device 4000 includes a first memory 421, a processor 45, and an input unit 43.
  • the first memory 421 stores multiple fusion parameters of multiple applications of the terminal;
  • the unit 43 is configured to receive a fusion operation request of the user for multiple applications.
  • the processor 45 is configured to register multiple fusion parameters of each application through multiple fusion parameter interfaces when multiple applications are installed, and combine multiple fusion parameters.
  • the display interface of the merged application is determined, and the plurality of fusion parameter interfaces respectively acquire the plurality of The plurality of fusion parameters of the plurality of applications are respectively fused, and the logical relationship of the merged application and the format of the data are obtained.
  • the first memory 421 may further store the fusibility defining information of the data of each application
  • the terminal device 4000 may further include a second memory 422, where the second memory 422 may be used to store the terminal device 4000.
  • the processor 45 may further acquire data of the fused application from the second memory 422 according to the fusibility defining information of the data of each application; on the display interface of the fused application, And outputting data of the merged application according to the logical relationship of the merged application and the format of the data.
  • the second memory 422 can be an external storage of the terminal device 4000, and the first memory 421 can be a memory of the terminal device 4000.
  • the processor 45 can load data of a plurality of applications from the second memory 422 into the first memory 421.
  • Each of the fusion parameters corresponds to one storage space in the first memory 421. Alternatively, each storage space may be the same.
  • the first memory 421 may be one of an NVRAM nonvolatile memory, a DRAM dynamic random access memory, an SRAM static random access memory, a flash flash memory, and the like; the second memory 422 may be a hard disk, an optical disk, a USB disk, a floppy disk, or a tape drive.
  • data of all applications of the terminal may be stored in a cloud server, and the cloud server may be a second memory 422.
  • the processor 45 obtains the data of the merged application into the first memory 421. Specifically, the processor 45 acquires data of the merged application in the cloud server through the network channel, and loads the data of the merged application. Go to the first memory 421.
  • the input unit 43 can be configured to receive input digital or character information and to generate signal inputs related to user settings and function control of the terminal device 4000.
  • the input unit 43 may include a touch panel 431.
  • the touch panel 431 also referred to as a touch screen, can collect touch operations on or near the user (such as the user's operation on the touch panel 431 or on the touch panel 431 using any suitable object or accessory such as a finger, a stylus, or the like. ), and drive the corresponding connection device according to a preset program.
  • the touch panel 431 may include two parts: a touch detection device and a touch controller.
  • the touch detection device detects the touch orientation of the user, and detects a signal brought by the touch operation, and transmits the signal to the touch controller; the touch controller receives the touch information from the touch detection device, converts the touch information into contact coordinates, and sends the touch information.
  • the processor 45 is provided and can receive commands from the processor 45 and execute them.
  • the touch panel 431 can be implemented in various types such as resistive, capacitive, infrared, and surface acoustic waves.
  • the input unit 43 may further include other input devices 432, which may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, switch buttons, etc.), trackballs, mice, joysticks, and the like. One or more of them.
  • the terminal device 4000 can also include a display unit 44 that can be used to output data of the fused application.
  • the display unit 44 can include a display panel 441.
  • the display panel 441 can be configured in the form of an LCD (Liquid Crystal Display) or an OLED (Organic Light-Emitting Diode).
  • the touch panel 431 covers the display panel 441 to form a touch display screen.
  • the touch display screen detects a touch operation on or near the touch display screen, the touch display screen transmits to the processor 45 to determine the type of the touch event.
  • the processor 45 then provides a corresponding visual output on the touch display depending on the type of touch event.
  • the touch display screen includes an application interface display area and a common control display area.
  • the arrangement manner of the application interface display area and the display area of the common control is not limited, and the arrangement manner of the two display areas can be distinguished by up-and-down arrangement, left-right arrangement, and the like.
  • the application interface display area can be used to display the interface of the application. Each interface can contain interface elements such as at least one application's icon and/or widget desktop control.
  • the application interface display area can also be an empty interface that does not contain any content.
  • the common control display area is used to display controls with high usage, such as setting buttons, interface numbers, scroll bars, phone book icons, and the like.
  • the processor 45 is a control center of the terminal device 4000, which connects various parts of the entire mobile phone using various interfaces and lines, by running or executing software programs and/or modules stored in the first memory 421, and calling the storage in The data in the second memory 422 performs various functions and processing data of the terminal device 4000, thereby performing overall monitoring of the terminal device 4000.
  • the processor 45 can include one or more processing units.
  • Computer readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one location to another.
  • a storage medium may be any available media that can be accessed by a computer.
  • the computer readable medium may include a random access memory (RAM), a read-only memory (ROM), and an electrically erasable programmable read-only memory (Electrically Erasable Programmable).
  • EEPROM Electrically Error Read-Only Memory
  • CD-ROM Compact Disc Read-Only Memory
  • Any connection may suitably be a computer readable medium.
  • the software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL), or wireless technologies such as infrared, radio, and microwave, Then coaxial cable, fiber optic cable, twisted pair, DSL or wireless technologies such as infrared, wireless and microwave are included in the fixing of the associated medium.
  • DSL Digital Subscriber Line
  • a disk and a disc include a compact disc (CD), a laser disc, a compact disc, a digital versatile disc (DVD), a floppy disk, and a Blu-ray disc, wherein the disc is usually magnetically copied, and the disc is The laser is used to optically replicate the data. Combinations of the above should also be included within the scope of the computer readable media.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Databases & Information Systems (AREA)
  • Human Computer Interaction (AREA)
  • Data Mining & Analysis (AREA)
  • Stored Programmes (AREA)
  • Communication Control (AREA)
  • User Interface Of Digital Computer (AREA)

Abstract

一种应用融合方法及装置，通过提供多个融合参数接口，接收应用通过该融合参数接口注册的多种融合参数(S101)，从而在接收到用户或装置内部的对多个应用的融合操作请求时，从多个融合参数接口获取多个应用的多种融合参数，对多个应用的多种融合参数分别进行融合(S102)，从而实现了对任意多个应用进行融合。

Description

一种应用融合方法及装置 技术领域
本发明涉及智能终端技术领域，尤其涉及一种应用融合方法及装置。
背景技术
智能终端上丰富多彩的应用(Application，简称APP)在很大程度上改变了用户的娱乐、生活或工作方式。然而，大量的APP的安装也给用户造成了很多不便利，这么多的APP安装在终端上，纷繁复杂，还有很多是同样的功能的APP，这给用户带来了很多使用上的不便。
为了应用使用的方便，现有的一种方式是苹果公司的Siri语音数字助手，是以Siri语音工具软件为入口，通过解析语音语义，对其他APP进行调用来完成所需执行的动作，并将执行的结果显示给用户。
这类语音数字助手虽然可以实现APP的调用，但是这类语音数字助手是操作系统内部固化好的，并非任一一个APP均可作为数字助手，且用户无法决定对哪些APP调用。
发明内容
本发明实施例提供一种应用融合方法及装置，以实现根据应用融合操作请求，对任意多个应用进行融合。
第一方面，提供了一种应用融合方法，包括：通过多个融合参数接口注册每个应用的多种融合参数，所述多种融合参数包括：每个应用的数据的格式，每个应用的数据之间的逻辑关系；当接收到融合操作请求时，通过所述多个融合参数接口，分别获取所述多个应用的多种融合参数，对获取的所述多个应用的多种融合参数分别进行融合，获得所述融合后的应用的逻辑关系，数据的格式。
在本发明实施例提供设备中，操作系统对应用提供多个融合参数接口，而应用在安装的时候通过该融合参数接口注册多种融合参数，这些融合参数中的部分融合参数可以用来指示应用之间是否可融合，另外一部分融合参数可以用来指示应用之间融合后的数据格式或界面展示格式等需要的信息，当然以上融合参数类型也可以具备其中的一种。这样，操作系统可以获得多个应用的融合参数，并在接收到融合需求时根据需要融合的应用的融合参数进行应用融合。
在本发明的某些实施例中，融合后的应用可以是一个独立的应用，具有自己独特的应用界面，例如应用程序图标可以是个不同于融合前的多个应用的新生成的一个，打开该图标后的应用可以是一个全新的界面；在本发明的另一些实施例中，融合后的应用也可以是需要融合的多个应用中的其中一个应用，其他应用的数据信息通过该应用以及该应用的界面展示出来，例如地图应用和社交应用进行融合后，在地图应用的地图上融合社交应用的好友地理位置信息等；在本发明的再一些实施例中，融合后的应用不使用的时候并不显示，仅在用户或其他应用使用该融合后的应用的功能时显示该应用处理后的数据。
在该实现方式中，也可以不在操作系统中进行应用的安装，不在用户界面显示应用的图标，但只需通过融合参数接口注册多种融合参数，即可完成应用的融合；当然也可以在 操作系统中进行应用的安装，在用户界面显示应用的图标，在应用安装时，通过融合参数接口注册多种融合参数，接收用户在用户对应用的融合操作请求，进行应用的融合操作。
结合第一方面，在第一方面的第一种可能的实现方式中，所述方法还包括：确定融合后的应用的展示界面。
在实现方式中，在操作系统中进行了应用的安装，在用户界面显示了应用的图标，则进行应用融合后，融合后的应用也具有相应的展示界面。
且对于“确定融合后的应用的展示界面”和“通过所述多个融合参数接口，分别获取所述多个应用的多种融合参数，对获取的所述多个应用的多种融合参数分别进行融合，获得所述融合后的应用的逻辑关系，数据的格式”的步骤，两个步骤之间没有先后顺序关系。
结合第一方面的第一种可能的实现方式，在第一方面的第二种可能的实现方式中，所述多种融合参数还包括每个应用的数据的可融合性限定信息；所述方法还包括：根据所述每个应用的数据的可融合性限定信息，获取所述融合后的应用的数据；在所述融合后的应用的展示界面上，根据所述融合后的应用的数据之间的逻辑关系和数据的格式输出所述融合后的应用的数据。
在该实现方式中，不仅进行了应用的融合，还在融合后的应用的展示界面上，根据融合后的应用的逻辑关系和数据的格式输出融合后的应用的数据，实现了多个应用的数据的互通。
结合第一方面的第二种可能的实现方式，在第一方面的第三种可能的实现方式中，所述每个应用的数据的格式采用多个二维表描述每个应用的数据，所述每个应用的数据之间的逻辑关系包括所述多个二维表之间的关系、所述多个二维表中的基础数据表和顶层数据表，所述每个应用的数据的可融合性限定信息包括每个应用的数据中支持融合和/或不支持融合的数据的信息。
结合第一方面或第一方面的第一种可能的实现方式或第一方面的第二种可能的实现方式，在第一方面的第三种可能的实现方式中，所述方法还包括：
将每个应用的多种融合参数分别存储至操作系统的一个存储空间。
结合第一方面或第一方面的第一种可能的实现方式或第一方面的第二种可能的实现方式或第一方面的第三种可能的实现方式，在第一方面的第四种可能的实现方式中，所述接收用户对多个应用的融合操作请求，包括：接收所述用户将所述多个应用拖动到目标应用的操作请求，其中，所述融合后的应用为所述目标应用，所述目标应用为所述多个应用中的一个应用；或接收所述用户将所述多个应用拖动到一个空位置的创建新应用的操作请求，其中，所述融合后的应用为所述创建的新应用。
在该实现方式中，通过对应用进行拖动操作来实现应用融合，操作简单方便。
结合第一方面或第一方面的第一种可能的实现方式或第一方面的第二种可能的实现方式或第一方面的第三种可能的实现方式，在第一方面的第五种可能的实现方式中，所述接收用户对多个应用的融合操作请求，包括：接收所述用户在应用列表中选择所述多个应用以及所述融合后的应用的请求，所述融合后的应用为所述多个应用中的一个应用，或为所述应用列表中除所述多个应用外的一个应用。
在该实现方式中，通过在应用列表中选择应用进行融合，操作简单方便。
结合第一方面或第一方面的第一种可能的实现方式或第一方面的第二种可能的实现方式或第一方面的第三种可能的实现方式或第一方面的第四种可能的实现方式或第一方面的第五种可能的实现方式，在第一方面的第六种可能的实现方式中，所述通过所述多个融合参数注册接口，分别获取所述多个应用的多种融合参数之前，所述方法还包括：检查所述多个融合参数接口是否符合融合规范；若检查的结果为不符合融合规范，则向应用中心请求包含满足融合规范的多个融合参数接口的应用程序安装包；若所述应用中心存在所述应用程序安装包，则下载所述应用程序安装包；若所述应用中心不存在所述应用程序安装包，则在所述应用中心通过进行所述多个融合参数接口的适配，编译应用程序源码，生成所述应用程序安装包后，下载所述应用程序安装包；安装下载的所述应用程序安装包。
在该实现方式中，进行了融合参数接口的适配，使其符合融合规范，能够调用该融合参数接口中的融合参数进行应用的融合。
结合第一方面或第一方面的第一种可能的实现方式或第一方面的第二种可能的实现方式或第一方面的第三种可能的实现方式或第一方面的第四种可能的实现方式或第一方面的第五种可能的实现方式或第一方面的第六种可能的实现方式，在第一方面的第七种可能的实现方式中，所述方法还包括：通过所述多个融合参数接口分别注册所述融合后的应用的数据之间的逻辑关系，所述融合后的应用的数据的格式，和/或所述融合后的应用的数据的可融合性限定信息。
第二方面，提供了一种应用融合装置，该应用融合装置具有实现上述方法中应用融合装置行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
一种可能的实现方式中，提供了一种应用融合装置，包括：注册单元，用于通过多个融合参数接口注册每个应用的多种融合参数，所述多种融合参数包括：每个应用的数据的格式，每个应用的数据之间的逻辑关系；融合单元，用于当接收到融合操作请求时，通过所述多个融合参数接口，分别获取所述多个应用的多种融合参数，对获取的所述多个应用的多种融合参数分别进行融合，获得所述融合后的应用的逻辑关系，数据的格式。
另一种可能的实现方式中，提供了一种应用融合装置，包括：输入装置、输入装置、存储器和处理器；通过存储器中的程序或指令，所述处理器用于：通过多个融合参数接口注册每个应用的多种融合参数，所述多种融合参数包括：每个应用的数据的格式，每个应用的数据之间的逻辑关系；当接收到融合操作请求时，通过所述多个融合参数接口，分别获取所述多个应用的多种融合参数，对获取的所述多个应用的多种融合参数分别进行融合，获得所述融合后的应用的逻辑关系，数据的格式。
实施本发明实施例提供的一种应用融合方法及装置，具有如下有益效果：
通过提供多个融合参数接口，接收应用通过该融合参数接口注册的多种融合参数，从而在接收到用户或装置内部的对多个应用的融合操作请求时，从多个融合参数接口获取多个应用的多种融合参数，对多个应用的多种融合参数分别进行融合，从而实现了对任意多 个应用进行融合。
附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1是一种终端设备的结构示意图；
图2为本发明实施例提供的一种应用融合方法的流程示意图；
图3为本发明实施例提供的另一种应用融合方法的流程示意图；
图4为本发明实施例提供的应用中心实现融合后的应用接口兼容性适配示意图；
图5为本发明实施例提供的一种应用融合装置的结构示意图；
图6为本发明实施例提供的另一种应用融合装置的结构示意图；
图7为本发明实施例提供的另一种终端设备的结构示意图；
图8为本发明实施例提供的又一种终端设备的结构示意图。
具体实施方式
图1是一种终端设备的结构示意图。
以图1为例介绍本发明实施例提供的应用融合方法应用的计算节点的逻辑结构。该计算节点可以是终端设备，该终端设备具体可以为一智能手机。如图1所示，该终端设备的硬件层包括CPU、输入设备等，当然还可以包括存储器、输出设备、内存、内存控制器、网络接口等，输入设备可包括键盘、鼠标、触摸屏等，输出设备可包括显示设备如LCD、CRT、全息成像(Holographic)、投影(Projector)等。在硬件层之上可运行有操作系统(如Android等)以及一些应用程序。核心库是操作系统的核心部分，包括输入/输出服务、核心服务、融合参数接口以及应用融合服务等。除此之外，该终端还包括驱动层、框架层和应用层。驱动层可包括CPU驱动、显示控制器驱动等。框架层可包括融合参数注册服务等。应用层可包括图形用户界面(Graphical User Interface，简称GUI)、应用列表、浏览器(Browser)等。应当理解的是，本发明实施例方法的执行主体的逻辑结构可参考图1。
图2为本发明实施例提供的一种应用融合方法的流程示意图，该方法包括以下步骤：
S101，当多个应用安装时，通过多个融合参数接口注册每个应用的多种融合参数。
本实施例中，操作系统对应用程序安装过程进行了增强与细化，提供多个融合参数接口供应用程序在安装时作调用，以接收每个应用的多种融合参数的注册。
这里的多种融合参数包括：每个应用的数据的格式，每个应用的数据之间的逻辑关系。应用可以通过数据格式注册接口注册每个应用的数据的格式，可以通过数据逻辑关系注册接口注册每个应用的数据之间的逻辑关系，当然，也可以通过同一个接口注册以上多种融合参数。所述每个应用的数据的格式采用多个二维表描述每个应用的数据，所述每个应用的数据之间的逻辑关系包括所述多个二维表之间的关系、所述多个二维表中的基础数据表 和顶层数据表。
该融合参数还可以包括：数据生成规则和数据读取规则，数据生成规则是指在数据生成过程中将数据按注册格式生成数据的执行体或者程序片段。数据读取规则是指在数据提取/读取过程中按注册格式读取以二维数据表形式保存的数据内容。
S102，当接收到用户对多个应用的融合操作请求时，确定融合后的应用的展示界面，通过所述多个融合参数接口，分别获取所述多个应用的多种融合参数，对获取的所述多个应用的多种融合参数分别进行融合，获得所述融合后的应用的逻辑关系，数据的格式。
用户可以选择对终端上已安装的任意多个应用进行融合，接收用户对所选择的应用的融合操作请求。在进行应用融合时，则可以通过多个融合参数接口，获取待进行融合的多个应用的多种融合参数。具体地，例如，通过数据格式注册接口获取多个应用的数据的格式，通过数据逻辑关系注册接口获取多个应用的数据之间的逻辑关系。
获取融合操作请求所请求融合的应用的多种融合参数后，对获取的多个应用的多种融合参数分别进行融合，获得融合后的应用的逻辑关系，数据的格式。具体地，通过数据格式注册接口获取多个应用的数据格式，检查多个应用的数据格式的可融合性，获得融合的数据格式，作为融合后的应用的数据的格式；通过数据逻辑关系注册接口获取多个应用的数据之间的逻辑关系，确定融合后的应用的数据之间的逻辑关系。
需要说明的是，也可以不在操作系统中进行应用的安装，不在用户界面显示应用的图标，但只需通过融合参数接口注册多种融合参数，即可完成应用的融合；当然也可以在操作系统中进行应用的安装，在用户界面显示应用的图标，在应用安装时，通过融合参数接口注册多种融合参数，接收用户在用户对应用的融合操作请求，进行应用的融合操作。
根据本发明实施例提供的一种应用融合方法，通过提供多个融合参数接口，接收应用通过该融合参数接口注册的多种融合参数，从而在接收到用户或装置内部的对多个应用的融合操作请求时，从多个融合参数接口获取多个应用的多种融合参数，对多个应用的多种融合参数分别进行融合，从而实现了对任意多个应用进行融合。
图3为本发明实施例提供的另一种应用融合方法的流程示意图，该方法包括以下步骤：
S201，当多个应用安装时，通过多个融合参数接口注册每个应用的多种融合参数。
本实施例中，操作系统对应用程序安装过程进行了增强与细化，提供多个融合参数接口供应用程序在安装时作调用，以接收每个应用的多种融合参数的注册。
这里的多种融合参数包括：每个应用的数据的格式，每个应用的数据之间的逻辑关系，每个应用的数据的可融合性限定信息。应用可以通过数据格式注册接口注册每个应用的数据的格式，可以通过数据逻辑关系注册接口注册每个应用的数据之间的逻辑关系，可以通过可融合性限定注册接口注册每个应用的数据的可融合性限定信息，当然，也可以通过同一个接口注册以上多种融合参数。所述每个应用的数据的格式采用多个二维表描述每个应用的数据，所述每个应用的数据之间的逻辑关系包括所述多个二维表之间的关系、所述多个二维表中的基础数据表和顶层数据表，所述每个应用的数据的可融合性限定信息包括每个应用的数据中支持融合和/或不支持融合的数据的信息。
该融合参数还可以包括：数据生成规则和数据读取规则，数据生成规则是指在数据生 成过程中将数据按注册格式生成数据的执行体或者程序片段。数据读取规则是指在数据提取/读取过程中按注册格式读取以二维数据表形式保存的数据内容。
S202，将每个应用的多种融合参数分别存储至操作系统的一个存储空间。
将通过各个融合参数接口接收到的多种融合参数分别存储至操作系统的多个存储空间，以供操作系统进行应用融合时调用。
S203，接收所述用户将所述多个应用拖动到一个空位置的创建新应用的操作请求。
所述融合后的应用为所述创建的新应用。用户可以选择对终端上已安装的任意多个应用进行融合，装置接收用户对所选择的应用的融合操作请求。可对应用图标直接作拖动导致融合触发。该拖动包括将多个应用拖动到一个空位置，在该空位置创建一个新应用，融合后的应用即为该创建的新应用。
作为一种替代的实现方式，S203也可以是接收所述用户将所述多个应用拖动到目标应用的操作请求，其中，所述融合后的应用为所述目标应用，所述目标应用为所述多个应用中的一个应用。
以上拖动方式是基于终端桌面提供了例如图形用户界面，使得用户可以在桌面直接对应用图标进行拖动。通过对应用进行拖动操作来实现应用融合，操作简单方便。
作为另一种替代的实现方式，S203也可以是接收所述用户在应用列表中选择所述多个应用以及所述融合后的应用的请求，所述融合后的应用为所述多个应用中的一个应用，或为所述应用列表中除所述多个应用外的一个应用。即可在应用列表中选择应用进行融合，该应用列表中仅列出了多个应用的标识供选择，用户可选择融合后的应用为多个应用中的一个应用，或为应用列表中除待融合的多个应用外的一个应用。
通过在应用列表中选择应用进行融合，操作简单方便。
S204，检查所述多个融合参数接口是否符合融合规范，若是，则进行到S209；否则，进行到S205。
S205，向应用中心请求包含满足融合规范的多个融合参数接口的应用程序安装包。
S206，所述应用中心是否存在所述应用程序安装包，若是，则进行到S208；否则，进行到S207。
S207，在所述应用中心通过进行所述多个融合参数接口的适配，编译应用程序源码，生成所述应用程序安装包。
S208，下载所述应用程序安装包并安装下载的所述应用程序安装包。
S204-S208为检查融合参数接口是否符合融合规范，进行融合参数接口的适配，使其符合融合规范，使操作系统能够调用该融合参数接口中的融合参数进行应用的融合。图4为本发明实施例提供的应用中心实现融合后的应用接口兼容性适配示意图，在本实施例中，在获取多个应用的融合参数进行应用融合之前，还需检查多个融合参数接口是否符合融合规范。如果不符合操作系统的融合规范，则停止融合，然后向应用中心(例如App store或者App market)请求满足融合规范的应用程序安装包；如果应用市场尚无满足融合规范的应用程序安装包，则通过相应的接口适配，重新编译应用程序源码，生成新的应用程序安装包；然后接收存在已满足规范与要求的应用程序安装的通知，获取相应的应用程序安装包，重新安装下载的应用程序安装包；如果应用中心存在所述应用程序安装包，则直接下载所 述应用程序安装包并安装。
S209，确定融合后的应用的展示界面。
应用的属性包括：社交关系属性、时间关系属性、事务安排型属性、交流确定型属性等，根据应用的属性，即可确定融合后的应用的界面展示参数，从而根据该界面展示参数生成对应的展示界面。具体地，装置可保存一些根据不同应用的属性融合生成的界面模板，对应待融合应用的应用属性，选择对应的界面模板即可。
S210，通过所述多个融合参数接口，分别获取所述多个应用的多种融合参数，对获取的所述多个应用的多种融合参数分别进行融合，获得所述融合后的应用的逻辑关系，数据的格式，根据所述每个应用的数据的可融合性限定信息，获取所述融合后的应用的数据。
用户可以选择对终端上已安装的任意多个应用进行融合，接收用户对所选择的应用的融合操作请求。在进行应用融合时，则可以通过多个融合参数接口，获取待进行融合的多个应用的多种融合参数。具体地，例如，通过数据格式注册接口获取多个应用的数据的格式，通过数据逻辑关系注册接口获取多个应用的数据之间的逻辑关系。
获取融合操作请求所请求融合的应用的多种融合参数后，对获取的多个应用的多种融合参数分别进行融合，获得融合后的应用的逻辑关系，数据的格式。具体地，通过数据格式注册接口获取多个应用的数据格式，检查多个应用的数据格式的可融合性，获得融合的数据格式，作为融合后的应用的数据的格式；通过数据逻辑关系注册接口获取多个应用的数据之间的逻辑关系，确定融合后的应用的数据之间的逻辑关系。
在确定融合后的应用的数据格式和数据之间的逻辑关系后，根据从融合参数接口获取的可融合性限定信息获取融合后的应用的数据。即获取每个应用中可获取的数据。
需要说明的是，S209和S210的执行没有先后顺序关系。
S211，在所述融合后的应用的展示界面上，根据所述融合后的应用的数据的格式和数据之间的逻辑关系输出所述融合后的应用的数据。
在获取了每个应用中可获取的数据后，根据生成的融合后的应用的数据的格式和数据之间的逻辑关系对获取的数据进行处理，输出在融合后的应用的展示界面上。
S212，通过所述多个融合参数接口分别注册所述融合后的应用的数据之间的逻辑关系，所述融合后的应用的数据的格式，和/或所述融合后的应用的数据的可融合性限定信息。
针对融合后的应用，可能生成新的数据格式，具有新的数据之间的逻辑关系，具有新的数据的数据生成规则和数据读取规则，因此，需要在多个融合参数接口中注册融合后的应用的数据的格式、数据之间的逻辑关系、数据生成规则和数据读取规则。注册后，该融合后的应用还可以作为一个原始应用与其它应用进行融合。
根据本发明实施例提供的一种应用融合方法，通过提供多个融合参数接口，接收应用通过该融合参数接口注册的多种融合参数，从而在接收到用户或装置内部的对多个应用的融合操作请求时，从多个融合参数接口获取多个应用的多种融合参数，对多个应用的多种融合参数分别进行融合，从而实现了对任意多个应用进行融合；且实现了多个应用的数据的互通；且通过对应用进行拖动操作来实现应用融合，操作简单方便。
下面以一个具体的示例对基于用户对多个应用的融合操作请求进行应用融合的方法进 行详细描述：
以第一应用与第二应用的应用融合为例来说明。在这里，操作系统对应用程序安装过程进行了增强与细化，尤其是在注册到操作系统的存储区域中的数据的格式、数据的逻辑关系以及可融合性限定信息，还可以包括数据生成规则、数据读取规则。这些信息的注册，是以前各种操作系统所没有的。在下述的举例说明中，不考虑图形界面上的操作形式与要求。
一、操作系统使能应用融合
操作系统在应用程序的安装阶段提供注册接口及存储空间以接收应用程序的初始化，即操作系统提供多个融合参数接口，供应用程序在安装时作调用，以将应用程序自己的数据及其它相关信息注册到操作系统的存储空间中。这些接口包括：
A.genInitialData()：即安装过程生成初始数据，即生成关于应用程序的元数据(Metadata)，该元数据为一个预览总表，包括多个应用的融合参数的基本信息。这些Metadata的列形式要求如下：
{appID/应用ID,counTables/应用总表个数，lstTables/应用各表列表,tblFromNetwork/网络服务器优先的数据，tblLocally/仅在本地保存的数据}。
B.regDataEncoder()：即数据生成接口的注册。在安装过程中调用这个接口，可以注册在数据生成过程中将数据按注册格式生成数据的执行体或者程序片段。
C.regDateDecoder()：即数据读取接口的注册。在安装过程中调用这个接口，可以注册在数据提取/读取过程中按注册格式读取以二维数据表形式保存的数据内容。
D.regDataFormat()：即数据的格式的注册接口。在安装过程中调用这个接口，可以注册应用所生成数据的格式。一种方法是数据格式采用一系列二维表(table)的方式。每个table有表名(table name)，table中限定一组关键名称(key name)组成一栏(column)。这里的每个table及key name，相对应的，在初始数据填写阶段(调用genInitialData时)以及正常使用过程中的应用数据生成阶段就有由一组key name组成的数组(tuple)，并有多个tuple的数据表。
E.regDataBusinessLogic()：即数据所体现业务逻辑的注册。在安装过程中调用这个接口，可以注册应用数据的业务逻辑，即各二维数据表的各表间的关系、数据的基本层次关系、为用户提供服务时的展示层次等表示数据应用与业务关系之“逻辑”的信息。这些业务逻辑表的列形式要求如下：
1.{appID/应用ID,countBaseTables/应用基础数据表个数,lstBaseTables/应用基础数据表列表}；
2.{appID/应用ID,countTopTables/应用顶层数据表个数,lstTopTables/应用顶层数据表列表}；
3.{appID/应用ID,countTableLevels/应用数据表层数,arrayTableLevels/应用数据表关系矩阵}。
F.regDataTranferRight()：即指定相关数据的可融合性限定信息的注册。在安装过程中调用这个接口，将指定本应用数据的可融合性。这种“数据的可融合性”，可以是整个应用的所有数据均不支持融合，或者某些数据支持可融合，或者某些数据不支持融合，或者其它可融合性的限制与要求。
二、应用安装过程的融合准备
第一应用与第二应用在安装过程中相比以前操作系统所体现出来的差异些细节，这些细节体现对融合的最终支持。
(一)第一应用安装过程
在本实施例中，该第一应用例如为好友应用，第一应用在安装过程中，调用相应的装置接口注册融合参数的细节如下：
A:调用genInitialData接口生成应用程序Metadata：
{12321/装置分配给第一应用的应用ID，5/应用程序第一应用总共有5个数据表，{1,2,3,4,5}/应用程序第一应用的各表表名，{1,2,3}/数据以服务器数据优先的，{4,5}/数据只使用保存在本地表的}。
B/C:第一应用安装程序分别调用regDataEncoder与regDateDecoder后，在装置的数据区I保存了第一应用应用的多个解析接口以及接口使用规则，其中两条关键的接口为get第一应用DataFromTables()与set第一应用DataIntoTables()。前者用于从数据表中提供数据，后者用于将某些数据写入数据表中永久作为记录保存。
D:第一应用安装程序调用regDataFormat，从而在操作系统的数据区II生成并保存了第一应用应用程序的数据Metadata:
D.0:具有记录内容的表{1/第一应用的表1，5/应用程序将使用五个数据表，{{},{},{},{},{}}/记录五个数据表格式的地址，{{},{},{},{},{}}/记录五个表数据的地址}用来作为下面表的基本描述；并在操作系统的数据区II生成并保存了下述为具体的数据表定义与格式：
D.1:表{goodfriendid/好友ID，friendname/好友名，friendnickyname/好友昵称}用来记录第一应用用户的基本信息；
D.2:表{goodfriendid/好友ID，relationbegintime/联系起始时间，chartcount/互动次数}用来记录跟好友的互动统计信息；
D.3表{goodfriendid/好友ID,activetype/互动类型，activetime/互动时间，activecountaddr/互动内容记录所在}用来记录同好友的互动内容；
D.4表{goodfriendid/好友ID，Settings/针对好友权限设置的条数，lstRights/权限设置类型}用来记录用户的针对“好友”的查看权限设置；
D.5表{sortInGUI/界面展示顺序，goodfriendid/好友ID}用来记录用户对运行界面的设置。
E:第一应用安装程序在操作系统的数据区III生成并保存了“业务逻辑空间”的一组记录。
E.1{12321/装置分配给第一应用的应用ID，2/应用程序第一应用有两个基础的数据表,{1,2}/应用程序第一应用的基础数据表表名}；
E.2{12321/装置分配给第一应用的应用ID，1/应用程序第一应用有一个顶层的数据表,{5}/应用程序第一应用的顶层数据表表名}；
E.3{12321/装置分配给第一应用的应用ID，2/应用程序第一应用数据使用层数为3，{{1,2,3},{4,5}}/应用程序第一应用的数据表关系矩阵}。
F:第一应用安装程序调用regDataTranferRight，在操作系统的数据区IV生成并保存了记录：{12321/装置分配给第一应用的应用ID，2/安装程序限制对第一应用应用的2号表的融合传递，{}/对2号表中具体限制融合传递的字段列举}。
(二)第二应用安装过程
在本实施例中，例如，该第二应用为地图应用，应用程序第二应用在安装过程中，调用相应的装置接口注册融合参数的细节如下：
A:第二应用安装程序调用genInitialData接口，在操作系统的数据区II生成并保存了应用程序Metadata：
{32123/装置分配给第二应用的应用ID，2/应用程序第二应用总共有2个数据表，{1,2,3}/应用程序第二应用的各表表名，{1,2}/数据以服务器数据优先的，{3}/数据只使用保存在本地表的}。
B/C:第二应用安装程序分别调用regDataEncoder与regDateDecoder，在操作系统的数据区I生成并保存了第二应用应用的多个解析接口以及接口使用规则，其中两条关键的接口为getAMPDataFromTables()与setAMPDataIntoTables()。前者用于用于展示用户的路径记录结果，后者用于将用户的路径记录写入历史记录。
D:第二应用的安装程序调用regDataFormat，在操作系统的数据区I中生成并保存了第二应用应用程序的数据Metadata:
D.0:记录第二应用将使用多少数据表的数据记录，{32123/装置分配给第二应用的应用ID，123456789/装置分配给用户的随机ID，3/应用程序将使用三个数据表，{{},{},{}}/记录三个数据表格式的地址，{{},{},{}}/记录三个表数据的地址}用来作为下面表的基本描述；并在操作系统的数据区II生成并保存了下述为具体的数据表定义与格式：
D.1:表{pointSerial/路径点序号，datetime/时间，longitude/经度，latitude/纬度}用来记录用户基于时间+地点的路径点信息；
D.2:表{pointSerial/路径点序号，longPOI/路径点上的兴趣物编号}用来记录用户基于路径点对感兴趣物品的“关联”；
D.3表{pointSerial/路径点序号，typePresent/路径点的地图界面展示类型}用来记录最后一次用户使用地图时的地点与方式；
E:第二应用安装程序在操作系统的数据区III生成并保存了“业务逻辑空间”的一组记录。
E.1{32123/装置分配给第二应用的应用ID，2/应用程序第二应用有两个基础的数据表，{1,2}/应用程序第二应用的基础数据表表名}；
E.2{32123/装置分配给第二应用的应用ID，1/应用程序第二应用有一个顶层的数据表，{3}/应用程序第二应用的顶层数据表表名}；
E.3{32123/装置分配给第二应用的应用ID，2/应用程序第二应用数据使用层数为2，{{1,2},{3}}/应用程序第二应用的数据表关系矩阵}。
F:第二应用安装程序调用regDataTranferRight，在操作系统的数据区IV生成并保存了记录：{32123/装置分配给第二应用的应用ID，NULL/安装程序对应用数据表作可融合性限定的个数为0}。
三、融合过程的数据融合与新应用生成：
A.触发对第一应用与第二应用的融合，根据用户的融合操作请求将生成新的应用程序第三应用。
B.检查第一应用与第二应用所注册的接口是否符合融合规范。如果不符合操作系统的融合规范，则停止融合，然后：
B.1向应用市场(App store或者App market)请求满足融合规范的应用程序安装包；
B.1.1如果应用市场尚无满足融合规范的应用程序安装包，则通过相应的接口适配，重新编译应用程序源码，生成新的应用程序安装包；
B.1.2发送已存在满足规范与要求的应用程序安装的通知；
B.2获取相应的应用程序安装包；
B.3将应用程序的数据从前(不满足融合规范)格式转换成新的格式(满足融合规范)，完成应用程序的执行条件更新。
C.获取第一应用与第二应用注册到操作系统各数据区I/II/III/IV/V的融合参数和应用数据表。
D.检查第一应用与第二应用的数据格式的可融合性，获得融合的数据格式，作为所述融合后的应用即第三应用的数据格式。
E.检查用户ID的冲突性(实际情况为应用程序第一应用呈现给用户的ID为特定值，而第二应用并未给用户呈现一个特定的ID，故它们间并不存在明确的冲突)。
F.提示并让用户确认在新的应用程序第三应用中将使用应用程序第一应用中的ID代替应用程序第二应用的随机ID。
G.应用程序第一应用的“好友信息”具有在融合中不可传递的限制，即第一应用的可融合性限定信息包括：
G.1融合后的新应用将不可获取任何关于原“好友”的信息以及原ID同“好友”的互动内容；
G.2融合后的新应用可以使用从应用程序第一应用继承(包括允许使用原应用的数字证书)数据接口来读取“好友”关系；
G.3融合后的新应用可以使用从应用程序第一应用继承(包括允许使用原应用的数字证书)数据接口来修改“好友”关系；
G.4融合后的新应用可以使用从应用程序第一应用继承(包括允许使用原应用的数字证书)数据接口来增加“好友”关系。
H.根据融合的数据格式，和获得的第一应用与第二应用的应用数据内容的可融合性限定信息，确定第三应用的融合数据。
I.装置给出新应用程序“好友地图”的基础数据项选项，以及给出应用程序“好友地图”的顶层数据项选项，由用户选择确定。
J.装置给出新应用程序“好友地图”的由数据表关系反映的业务逻辑及呈现内容选项与建议；
K.装置分析后，根据应用程序第一应用的社交关系属性、第二应用的时间关系属性(应用程序其它类型包括：如会议/日程类为事务安排型、如email为交流确定型，等等)，确定 界面展示参数。
从而用户选择与确认了一个以地图作为基础界面、以用户(基于限制条件G.2-G.5的不同而不同，以及用户选择继承内容的不同而不同)及好友的历史甚至当前位置信息作为呈现内容与结果的新应用，例如，该第二应用为一个地图应用程序。
L.通过regDataFormat()接口注册第三应用的数据格式。
M.通过regDataBusinessLogic()注册第三应用的业务逻辑关系。
N.根据第一应用和第二应用的数据生成规则，获得第三应用的数据生成规则，通过regDataEncoder()接口注册第三应用的数据生成规则；以及根据第一应用和第二应用的数据读取规则，获得第三应用的数据读取规则，通过regDateDecoder()接口注册第三应用的数据读取规则。
O.为第三应用生成应用程序Metadata。
P.保存上述注册内容到相应的各数据区。
Q.根据原生应用程序与新应用程序的数据传递关系，从原生应用程序的数据空间中拷贝数据到新应用程序的数据空间。
R.确认数据校验无误提示用户融合新应用成功。
S.如果基于一个极大化的可传递许可与数据融合，这个第三应用在一个地图界面允许用户展示“在何时”“在何地”“与谁”发生过一个以“什么方式”及“什么内容”所作的互动，例如，该第二应用为地图应用程序；或者
T.在可能的情况(操作融合使用特性的支持、以及应用程序第一应用新版本和第二应用新版本的支持下)下，第三应用还可以基于一个地理范围聚合同各好友的互动、或者基于一个时间范围聚合同各好友的互动，或者按地理位置来展示同好友的互动、或者基于时间轴关系来展示同好友的互动。
需要说明的是，对于前述的各方法实施例，为了简单描述，故将其都表述为一系列的动作组合，但是本领域技术人员应该知悉，本发明并不受所描述的动作顺序的限制，因为根据本发明，某些步骤可以采用其他顺序或者同时进行。其次，本领域技术人员也应该知悉，说明书中所描述的实施例均属于优选实施例，所涉及的动作和模块并不一定是本发明所必须的。
图5为本发明实施例提供的一种应用融合装置的结构示意图，该装置1000包括：
注册单元11，用于当多个应用安装时，通过多个融合参数接口注册每个应用的多种融合参数。
本实施例中，操作系统对应用程序安装过程进行了增强与细化，提供多个融合参数接口供应用程序在安装时作调用，以接收每个应用的多种融合参数的注册。
这里的多种融合参数包括：每个应用的数据的格式，每个应用的数据之间的逻辑关系。应用可以通过数据格式注册接口注册每个应用的数据的格式，可以通过数据逻辑关系注册接口注册每个应用的数据之间的逻辑关系，当然，也可以通过同一个接口注册以上多种融合参数。所述每个应用的数据的格式采用多个二维表描述每个应用的数据，所述每个应用 的数据之间的逻辑关系包括所述多个二维表之间的关系、所述多个二维表中的基础数据表和顶层数据表。
该融合参数还可以包括：数据生成规则和数据读取规则，数据生成规则是指在数据生成过程中将数据按注册格式生成数据的执行体或者程序片段。数据读取规则是指在数据提取/读取过程中按注册格式读取以二维数据表形式保存的数据内容。
融合单元12，用于当接收到用户对多个应用的融合操作请求时，确定融合后的应用的展示界面，通过所述多个融合参数接口，分别获取所述多个应用的多种融合参数，对获取的所述多个应用的多种融合参数分别进行融合，获得所述融合后的应用的逻辑关系，数据的格式。
用户可以选择对终端上已安装的任意多个应用进行融合，接收用户对所选择的应用的融合操作请求。在进行应用融合时，则可以通过多个融合参数接口，获取待进行融合的多个应用的多种融合参数。具体地，例如，通过数据格式注册接口获取多个应用的数据的格式，通过数据逻辑关系注册接口获取多个应用的数据之间的逻辑关系。
获取融合操作请求所请求融合的应用的多种融合参数后，对获取的多个应用的多种融合参数分别进行融合，获得融合后的应用的逻辑关系，数据的格式。具体地，通过数据格式注册接口获取多个应用的数据格式，检查多个应用的数据格式的可融合性，获得融合的数据格式，作为融合后的应用的数据的格式；通过数据逻辑关系注册接口获取多个应用的数据之间的逻辑关系，确定融合后的应用的数据之间的逻辑关系。
需要说明的是，也可以不在操作系统中进行应用的安装，不在用户界面显示应用的图标，但只需通过融合参数接口注册多种融合参数，即可完成应用的融合；当然也可以在操作系统中进行应用的安装，在用户界面显示应用的图标，在应用安装时，通过融合参数接口注册多种融合参数，接收用户在用户对应用的融合操作请求，进行应用的融合操作。
根据本发明实施例提供的一种应用融合装置，通过提供多个融合参数接口，接收应用通过该融合参数接口注册的多种融合参数，从而在接收到用户或装置内部的对多个应用的融合操作请求时，从多个融合参数接口获取多个应用的多种融合参数，对多个应用的多种融合参数分别进行融合，从而实现了对任意多个应用进行融合。
图6为本发明实施例提供的另一种应用融合装置的结构示意图，该装置2000包括：
注册单元20，用于当多个应用安装时，通过多个融合参数接口注册每个应用的多种融合参数。
本实施例中，操作系统对应用程序安装过程进行了增强与细化，提供多个融合参数接口供应用程序在安装时作调用，以接收每个应用的多种融合参数的注册。
这里的多种融合参数包括：每个应用的数据的格式，每个应用的数据之间的逻辑关系，每个应用的数据的可融合性限定信息。应用可以通过数据格式注册接口注册每个应用的数据的格式，可以通过数据逻辑关系注册接口注册每个应用的数据之间的逻辑关系，可以通过可融合性限定注册接口注册每个应用的数据的可融合性限定信息，当然，也可以通过同一个接口注册以上多种融合参数。所述每个应用的数据的格式采用多个二维表描述每个应用的数据，所述每个应用的数据之间的逻辑关系包括所述多个二维表之间的关系、所述多 个二维表中的基础数据表和顶层数据表，所述每个应用的数据的可融合性限定信息包括每个应用的数据中支持融合和/或不支持融合的数据的信息。
该融合参数还可以包括：数据生成规则和数据读取规则，数据生成规则是指在数据生成过程中将数据按注册格式生成数据的执行体或者程序片段。数据读取规则是指在数据提取/读取过程中按注册格式读取以二维数据表形式保存的数据内容。
存储单元21，用于将每个应用的多种融合参数分别存储至操作系统的一个存储空间。
将通过各个融合参数接口接收到的多种融合参数分别存储至操作系统的多个存储空间，以供操作系统进行应用融合时调用。
第一接收单元22，用于接收所述用户将所述多个应用拖动到一个空位置的创建新应用的操作请求。
所述融合后的应用为所述创建的新应用。用户可以选择对终端上已安装的任意多个应用进行融合，装置接收用户对所选择的应用的融合操作请求。可对应用图标直接作拖动导致融合触发。该拖动包括将多个应用拖动到一个空位置，在该空位置创建一个新应用，融合后的应用即为该创建的新应用。
作为一种替代的实现方式，第一接收单元22还可用于接收所述用户将所述多个应用拖动到目标应用的操作请求，其中，所述融合后的应用为所述目标应用，所述目标应用为所述多个应用中的一个应用。
以上拖动方式是基于终端桌面提供了例如图形用户界面，使得用户可以在桌面直接对应用图标进行拖动。通过对应用进行拖动操作来实现应用融合，操作简单方便。
作为另一种替代的实现方式，还可以包括第二接收单元，所述第二接收单元用于接收所述用户在应用列表中选择所述多个应用以及所述融合后的应用的请求，所述融合后的应用为所述多个应用中的一个应用，或为所述应用列表中除所述多个应用外的一个应用。即可在应用列表中选择应用进行融合，该应用列表中仅列出了多个应用的标识供选择，用户可选择融合后的应用为多个应用中的一个应用，或为应用列表中除待融合的多个应用外的一个应用。
通过在应用列表中选择应用进行融合，操作简单方便。
检查单元23，用于检查所述多个融合参数接口是否符合融合规范。
请求单元24，用于向应用中心请求包含满足融合规范的多个融合参数接口的应用程序安装包。
下载单元25，用于若所述应用中心存在所述应用程序安装包，则下载所述应用程序安装包；或
所述下载单元25用于若所述应用中心不存在所述应用程序安装包，则在所述应用中心通过进行所述多个融合参数接口的适配，编译应用程序源码，生成所述应用程序安装包后，下载所述应用程序安装包。
安装单元26，用于安装下载的所述应用程序安装包。
以上为检查融合参数接口是否符合融合规范，进行融合参数接口的适配，使其符合融合规范，使操作系统能够调用该融合参数接口中的融合参数进行应用的融合。图4为本发明实施例提供的应用中心实现融合后的应用接口兼容性适配示意图，在本实施例中，在获 取多个应用的融合参数进行应用融合之前，还需检查多个融合参数接口是否符合融合规范。如果不符合操作系统的融合规范，则停止融合，然后向应用中心(例如App store或者App market)请求满足融合规范的应用程序安装包；如果应用市场尚无满足融合规范的应用程序安装包，则通过相应的接口适配，重新编译应用程序源码，生成新的应用程序安装包；然后接收存在已满足规范与要求的应用程序安装的通知，获取相应的应用程序安装包，重新安装下载的应用程序安装包；如果应用中心存在所述应用程序安装包，则直接下载所述应用程序安装包并安装。
融合单元27，用于当接收到用户对多个应用的融合操作请求时，确定融合后的应用的展示界面，通过所述多个融合参数接口，分别获取所述多个应用的多种融合参数，对获取的所述多个应用的多种融合参数分别进行融合，获得所述融合后的应用的逻辑关系，数据的格式。
应用的属性包括：社交关系属性、时间关系属性、事务安排型属性、交流确定型属性等，根据应用的属性，即可确定融合后的应用的界面展示参数，从而根据该界面展示参数生成对应的展示界面。具体地，装置可保存一些根据不同应用的属性融合生成的界面模板，对应待融合应用的应用属性，选择对应的界面模板即可。
用户可以选择对终端上已安装的任意多个应用进行融合，接收用户对所选择的应用的融合操作请求。在进行应用融合时，则可以通过多个融合参数接口，获取待进行融合的多个应用的多种融合参数。具体地，例如，通过数据格式注册接口获取多个应用的数据的格式，通过数据逻辑关系注册接口获取多个应用的数据之间的逻辑关系。
获取融合操作请求所请求融合的应用的多种融合参数后，对获取的多个应用的多种融合参数分别进行融合，获得融合后的应用的逻辑关系，数据的格式。具体地，通过数据格式注册接口获取多个应用的数据格式，检查多个应用的数据格式的可融合性，获得融合的数据格式，作为融合后的应用的数据的格式；通过数据逻辑关系注册接口获取多个应用的数据之间的逻辑关系，确定融合后的应用的数据之间的逻辑关系。
获取单元28，用于根据所述每个应用的数据的可融合性限定信息，获取所述融合后的应用的数据。
在确定融合后的应用的数据格式和数据之间的逻辑关系后，根据从融合参数接口获取的可融合性限定信息获取融合后的应用的数据。即获取每个应用中可获取的数据。
输出单元29，用于在所述融合后的应用的展示界面上，根据所述融合后的应用的数据的格式和数据之间的逻辑关系输出所述融合后的应用的数据。
在获取了每个应用中可获取的数据后，根据生成的融合后的应用的数据的格式和数据之间的逻辑关系对获取的数据进行处理，输出在融合后的应用的展示界面上。
注册单元20还用于通过所述多个融合参数接口分别注册所述融合后的应用的数据之间的逻辑关系，所述融合后的应用的数据的格式，和/或所述融合后的应用的数据的可融合性限定信息。
针对融合后的应用，可能生成新的数据格式，具有新的数据之间的逻辑关系，具有新的数据的数据生成规则和数据读取规则，因此，需要在多个融合参数接口中注册融合后的应用的数据的格式、数据之间的逻辑关系、数据生成规则和数据读取规则。注册后，该融 合后的应用还可以作为一个原始应用与其它应用进行融合。
根据本发明实施例提供的一种应用融合装置，通过提供多个融合参数接口，接收应用通过该融合参数接口注册的多种融合参数，从而在接收到用户或装置内部的对多个应用的融合操作请求时，从多个融合参数接口获取多个应用的多种融合参数，对多个应用的多种融合参数分别进行融合，从而实现了对任意多个应用进行融合；且实现了多个应用的数据的互通；且通过对应用进行拖动操作来实现应用融合，操作简单方便。
图7描述了本发明实施例提供的另一种终端设备3000的结构，该终端设备3000包括：至少一个处理器31，至少一个网络接口34或者其他用户接口33，存储器35，至少一个通信总线32。通信总线32用于实现这些组件之间的连接通信。该终端设备30可选的包含用户接口33，包括显示器(例如，触摸屏、LCD、CRT、全息成像(Holographic)或者投影(Projector)等)，键盘或者点击设备(例如，鼠标，轨迹球(trackball),触感板或者触摸屏等)。
存储器35可以包括只读存储器和随机存取存储器，并向处理器31提供指令和数据。存储器35的一部分还可以包括非易失性随机存取存储器(NVRAM)。
在一些实施方式中，存储器35存储了如下的元素，可执行模块或者数据结构，或者他们的子集，或者他们的扩展集:
操作系统351，包含各种装置程序和本实施例中的多个融合参数接口，例如图1所示的框架层、核心库层、驱动层等，用于实现各种基础业务以及处理基于硬件的任务；
应用程序模块352，包含各种应用程序，例如图1所示的图形用户界面、应用列表、浏览器(Browser)等，用于实现各种应用业务。
在本发明实施例中，通过调用存储器35存储的程序或指令，处理器31用于：当多个应用安装时，通过多个融合参数接口注册每个应用的多种融合参数，所述多种融合参数包括：每个应用的数据的格式，每个应用的数据之间的逻辑关系；当接收到用户对多个应用的融合操作请求时，确定融合后的应用的展示界面，通过所述多个融合参数接口，分别获取所述多个应用的多种融合参数，对获取的所述多个应用的多种融合参数分别进行融合，获得所述融合后的应用的逻辑关系，数据的格式。
可选地，作为一个实施例，所述多种融合参数还包括每个应用的数据的可融合性限定信息；所述处理器31还用于：根据所述每个应用的数据的可融合性限定信息，获取所述融合后的应用的数据；在所述融合后的应用的展示界面上，根据所述融合后的应用的逻辑关系和数据的格式输出所述融合后的应用的数据。
进一步地，所述每个应用的数据的格式采用多个二维表描述每个应用的数据，所述每个应用的数据之间的逻辑关系包括所述多个二维表之间的关系、所述多个二维表中的基础数据表和顶层数据表，所述每个应用的数据的可融合性限定信息包括每个应用的数据中支持融合和/或不支持融合的数据的信息。
进一步地，所述处理器31还用于：将每个应用的多种融合参数分别存储至操作系统的一个存储空间。
进一步地，所述处理器31还用于：接收所述用户将所述多个应用拖动到目标应用的操 作请求，其中，所述融合后的应用为所述目标应用，所述目标应用为所述多个应用中的一个应用；或接收所述用户将所述多个应用拖动到一个空位置的创建新应用的操作请求，其中，所述融合后的应用为所述创建的新应用。
进一步地，所述处理器31还用于：接收所述用户在应用列表中选择所述多个应用以及所述融合后的应用的请求，所述融合后的应用为所述多个应用中的一个应用，或为所述应用列表中除所述多个应用外的一个应用。
进一步地，所述处理器31还用于：检查所述多个融合参数接口是否符合融合规范；
若检查的结果为不符合融合规范，则向应用中心请求包含满足融合规范的多个融合参数接口的应用程序安装包；
若所述应用中心存在所述应用程序安装包，则下载所述应用程序安装包；
若所述应用中心不存在所述应用程序安装包，则在所述应用中心通过进行所述多个融合参数接口的适配，编译应用程序源码，生成所述应用程序安装包后，下载所述应用程序安装包；
安装下载的所述应用程序安装包。
进一步地，所述处理器31还用于：通过所述多个融合参数接口分别注册所述融合后的应用的数据之间的逻辑关系，所述融合后的应用的数据的格式，和/或所述融合后的应用的数据的可融合性限定信息。
另外，终端设备30还可执行图2至图3的方法及实施例，本发明实施例在此不再赘述。
可见，采用上述方案后，在接收到用户或装置内部的对多个应用的融合操作请求时，从多个融合参数接口获取多个应用的多种融合参数，对多个应用的多种融合参数分别进行融合，从而实现了对任意多个应用进行融合。
本发明实施例涉及又一种终端设备4000及应用融合的方法，该终端设备4000可以为手机、平板电脑、PDA(Personal Digital Assistant，个人数字助理)、POS(Point of Sales，销售终端)、或车载电脑等。
图8示出的是本发明实施例终端设备4000的结构示意图。
参考图8，本发明实施例的又一种终端设备4000，包括，第一存储器421、处理器45及输入单元43，该第一存储器421存储该终端多个应用的多种融合参数；该输入单元43用于接收用户对多个应用的融合操作请求；该处理器45用于当多个应用安装时，通过多个融合参数接口注册每个应用的多种融合参数，并将多种融合参数存储在第一存储器421，并当接收到输入单元43输入的用户对多个应用的融合操作请求时，确定融合后的应用的展示界面，通过所述多个融合参数接口，分别获取所述多个应用的多种融合参数，对获取的所述多个应用的多种融合参数分别进行融合，获得所述融合后的应用的逻辑关系，数据的格式。
本发明实施例中，第一存储器421还可以存储每个应用的数据的可融合性限定信息，该终端设备4000还可以包括第二存储器422，该第二存储器422可以用于存储终端设备4000的所有应用的数据。该处理器45还可以根据所述每个应用的数据的可融合性限定信息，从第二存储器422获取所述融合后的应用的数据；在所述融合后的应用的展示界面上， 根据所述融合后的应用的逻辑关系和数据的格式输出所述融合后的应用的数据。
可以理解的，该第二存储器422可以为该终端设备4000的外存，该第一存储器421可以为该终端设备4000的内存。该处理器45可以从该第二存储器422中加载多个应用的数据到该第一存储器421中。每种融合参数在该第一存储器421中对应一个存储空间，可选的，每个存储空间可以相同。该第一存储器421可以为NVRAM非易失存储器、DRAM动态随机存储器、SRAM静态随机存储器、Flash闪存等其中之一；该第二存储器422可以为硬盘、光盘、USB盘、软盘或磁带机等。
本发明实施例中，终端的所有应用的数据可以存储在云服务器，该云服务器可以为第二存储器422。该处理器45获取融合后的应用的数据到该第一存储器421中，具体为：该处理器45通过网络通道获取该云服务器中融合后的应用的数据，将该融合后的应用的数据加载到该第一存储器421中。
该输入单元43可用于接收输入的数字或字符信息，以及产生与终端设备4000的用户设置以及功能控制有关的信号输入。具体地，本发明实施例中，该输入单元43可以包括触控面板431。触控面板431，也称为触摸屏，可收集用户在其上或附近的触摸操作(比如用户使用手指、触笔等任何适合的物体或附件在触控面板431上或在触控面板431的操作)，并根据预先设定的程式驱动相应的连接装置。可选的，触控面板431可包括触摸检测装置和触摸控制器两个部分。其中，触摸检测装置检测用户的触摸方位，并检测触摸操作带来的信号，将信号传送给触摸控制器；触摸控制器从触摸检测装置上接收触摸信息，并将它转换成触点坐标，再送给该处理器45，并能接收处理器45发来的命令并加以执行。此外，可以采用电阻式、电容式、红外线以及表面声波等多种类型实现触控面板431。除了触控面板431，输入单元43还可以包括其他输入设备432，其他输入设备432可以包括但不限于物理键盘、功能键(比如音量控制按键、开关按键等)、轨迹球、鼠标、操作杆等中的一种或多种。
该终端设备4000还可以包括显示单元44，该显示单元44可用于输出融合后的应用的数据。该显示单元44可包括显示面板441，可选的，可以采用LCD(Liquid Crystal Display，液晶显示器)或OLED(Organic Light-Emitting Diode,有机发光二极管)等形式来配置显示面板441。
本发明实施例中，该触控面板431覆盖该显示面板441，形成触摸显示屏，当该触摸显示屏检测到在其上或附近的触摸操作后，传送给处理器45以确定触摸事件的类型，随后处理器45根据触摸事件的类型在触摸显示屏上提供相应的视觉输出。
本发明实施例中，该触摸显示屏包括应用程序界面显示区及常用控件显示区。该应用程序界面显示区及该常用控件显示区的排列方式并不限定，可以为上下排列、左右排列等可以区分两个显示区的排列方式。该应用程序界面显示区可以用于显示应用程序的界面。每一个界面可以包含至少一个应用程序的图标和/或widget桌面控件等界面元素。该应用程序界面显示区也可以为不包含任何内容的空界面。该常用控件显示区用于显示使用率较高的控件，例如，设置按钮、界面编号、滚动条、电话本图标等应用程序图标等。
该处理器45是终端设备4000的控制中心，利用各种接口和线路连接整个手机的各个部分，通过运行或执行存储在该第一存储器421内的软件程序和/或模块，以及调用存储在 该第二存储器422内的数据，执行终端设备4000的各种功能和处理数据，从而对终端设备4000进行整体监控。可选的，该处理器45可包括一个或多个处理单元。
在上述实施例中，对各个实施例的描述都各有侧重，某个实施例中没有详述的部分，可以参见其他实施例的相关描述。
通过以上的实施方式的描述，所属领域的技术人员可以清楚地了解到本发明可以用硬件实现，或固件实现，或它们的组合方式来实现。当使用软件实现时，可以将上述功能存储在计算机可读介质中或作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是计算机能够存取的任何可用介质。以此为例但不限于：计算机可读介质可以包括随机存取存储器(Random Access Memory，RAM)、只读存储器(Read-Only Memory，ROM)、电可擦可编程只读存储器(Electrically Erasable Programmable Read-Only Memory，EEPROM)、只读光盘(Compact Disc Read-Only Memory，CD-ROM)或其他光盘存储、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质。此外。任何连接可以适当的成为计算机可读介质。例如，如果软件是使用同轴电缆、光纤光缆、双绞线、数字用户线(Digital Subscriber Line，DSL)或者诸如红外线、无线电和微波之类的无线技术从网站、服务器或者其他远程源传输的，那么同轴电缆、光纤光缆、双绞线、DSL或者诸如红外线、无线和微波之类的无线技术包括在所属介质的定影中。如本发明所使用的，盘(Disk)和碟(disc)包括压缩光碟(CD)、激光碟、光碟、数字通用光碟(DVD)、软盘和蓝光光碟，其中盘通常磁性的复制数据，而碟则用激光来光学的复制数据。上面的组合也应当包括在计算机可读介质的保护范围之内。
总之，以上所述仅为本发明技术方案的较佳实施例而已，并非用于限定本发明的保护范围。凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。

Claims (16)

  1. 一种应用融合方法，其特征在于，包括：
    当多个应用安装时，通过多个融合参数接口注册每个应用的多种融合参数，所述多种融合参数包括：每个应用的数据的格式，每个应用的数据之间的逻辑关系；
    当接收到用户对多个应用的融合操作请求时，确定融合后的应用的展示界面，通过所述多个融合参数接口，分别获取所述多个应用的多种融合参数，对获取的所述多个应用的多种融合参数分别进行融合，获得所述融合后的应用的逻辑关系，数据的格式。
  2. 如权利要求1所述的方法，其特征在于，所述多种融合参数还包括每个应用的数据的可融合性限定信息；
    所述方法还包括：
    根据所述每个应用的数据的可融合性限定信息，获取所述融合后的应用的数据；
    在所述融合后的应用的展示界面上，根据所述融合后的应用的数据之间的逻辑关系和数据的格式输出所述融合后的应用的数据。
  3. 如权利要求2所述的方法，其特征在于，所述每个应用的数据的格式采用多个二维表描述每个应用的数据，所述每个应用的数据之间的逻辑关系包括所述多个二维表之间的关系、所述多个二维表中的基础数据表和顶层数据表，所述每个应用的数据的可融合性限定信息包括每个应用的数据中支持融合和/或不支持融合的数据的信息。
  4. 如权利要求1-3任意一项所述的方法，其特征在于，所述方法还包括：
    将每个应用的多种融合参数分别存储至操作系统的一个存储空间。
  5. 如权利要求1所述的方法，其特征在于，所述接收用户对多个应用的融合操作请求，包括：
    接收所述用户将所述多个应用拖动到目标应用的操作请求，其中，所述融合后的应用为所述目标应用，所述目标应用为所述多个应用中的一个应用；或
    接收所述用户将所述多个应用拖动到一个空位置的创建新应用的操作请求，其中，所述融合后的应用为所述创建的新应用。
  6. 如权利要求1所述的方法，其特征在于，所述接收用户对多个应用的融合操作请求，包括：
    接收所述用户在应用列表中选择所述多个应用以及所述融合后的应用的请求，所述融合后的应用为所述多个应用中的一个应用，或为所述应用列表中除所述多个应用外的一个应用。
  7. 如权利要求1所述的方法，其特征在于，所述通过所述多个融合参数注册接口，分别获取所述多个应用的多种融合参数之前，所述方法还包括：
    检查所述多个融合参数接口是否符合融合规范；
    若检查的结果为不符合融合规范，则向应用中心请求包含满足融合规范的多个融合参数接口的应用程序安装包；
    若所述应用中心存在所述应用程序安装包，则下载所述应用程序安装包；
    若所述应用中心不存在所述应用程序安装包，则在所述应用中心通过进行所述多个融合参数接口的适配，编译应用程序源码，生成所述应用程序安装包后，下载所述应用程序安装包；
    安装下载的所述应用程序安装包。
  8. 如权利要求1-7任意一项所述的方法，其特征在于，所述方法还包括：
    通过所述多个融合参数接口分别注册所述融合后的应用的数据之间的逻辑关系，所述融合后的应用的数据的格式，和/或所述融合后的应用的数据的可融合性限定信息。
  9. 一种应用融合装置，其特征在于，包括：
    注册单元，用于当多个应用安装时，通过多个融合参数接口注册每个应用的多种融合参数，所述多种融合参数包括：每个应用的数据的格式，每个应用的数据之间的逻辑关系；
    融合单元，用于当接收到用户对多个应用的融合操作请求时，确定融合后的应用的展示界面，通过所述多个融合参数接口，分别获取所述多个应用的多种融合参数，对获取的所述多个应用的多种融合参数分别进行融合，获得所述融合后的应用的逻辑关系，数据的格式。
  10. 如权利要求9所述的装置，其特征在于，所述多种融合参数还包括每个应用的数据的可融合性限定信息；
    所述装置还包括：
    获取单元，用于根据所述每个应用的数据的可融合性限定信息，获取所述融合后的应用的数据；
    输出单元，用于在所述融合后的应用的展示界面上，根据所述融合后的应用的数据之间的逻辑关系和数据的格式输出所述融合后的应用的数据。
  11. 如权利要求10所述的装置，其特征在于，所述每个应用的数据的格式采用多个二维表描述每个应用的数据，所述每个应用的数据之间的逻辑关系包括所述多个二维表之间的关系、所述多个二维表中的基础数据表和顶层数据表，所述每个应用的数据的可融合性限定信息包括每个应用的数据中支持融合和/或不支持融合的数据的信息。
  12. 如权利要求9-11任意一项所述的装置，其特征在于，所述装置还包括：
    存储单元，用于将每个应用的多种融合参数分别存储至操作系统的一个存储空间。
  13. 如权利要求9所述的装置，其特征在于，所述装置还包括：第一接收单元；
    所述第一接收单元用于接收所述用户将所述多个应用拖动到目标应用的操作请求，其中，所述融合后的应用为所述目标应用，所述目标应用为所述多个应用中的一个应用；或
    所述第一接收单元用于接收所述用户将所述多个应用拖动到一个空位置的创建新应用的操作请求，其中，所述融合后的应用为所述创建的新应用。
  14. 如权利要求9所述的装置，其特征在于，所述装置还包括：第二接收单元；
    所述第二接收单元用于接收所述用户在应用列表中选择所述多个应用以及所述融合后的应用的请求，所述融合后的应用为所述多个应用中的一个应用，或为所述应用列表中除所述多个应用外的一个应用。
  15. 如权利要求9所述的装置，其特征在于，所述装置还包括：
    检查单元，用于检查所述多个融合参数接口是否符合融合规范；
    请求单元，用于若检查的结果为不符合融合规范，则向应用中心请求包含满足融合规范的多个融合参数接口的应用程序安装包；
    下载单元，用于若所述应用中心存在所述应用程序安装包，则下载所述应用程序安装包；或
    所述下载单元用于若所述应用中心不存在所述应用程序安装包，则在所述应用中心通过进行所述多个融合参数接口的适配，编译应用程序源码，生成所述应用程序安装包后，下载所述应用程序安装包；
    安装单元，用于安装下载的所述应用程序安装包。
  16. 如权利要求9-15任意一项所述的装置，其特征在于，所述注册单元还用于：
    通过所述多个融合参数接口分别注册所述融合后的应用的数据之间的逻辑关系，所述融合后的应用的数据的格式，和/或所述融合后的应用的数据的可融合性限定信息。
PCT/CN2017/071121 2016-01-29 2017-01-13 一种应用融合方法及装置 WO2017128964A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP17743579.9A EP3404536A4 (en) 2016-01-29 2017-01-13 METHOD AND DEVICE FOR MERGING APPLICATIONS
BR112018015451-2A BR112018015451A2 (zh) 2016-01-29 2017-01-13 An application fusion method and apparatus
US16/047,629 US10552233B2 (en) 2016-01-29 2018-07-27 Application convergence method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610070659.3A CN105786484B (zh) 2016-01-29 2016-01-29 一种应用融合方法及装置
CN201610070659.3 2016-01-29

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/047,629 Continuation US10552233B2 (en) 2016-01-29 2018-07-27 Application convergence method and apparatus

Publications (1)

Publication Number Publication Date
WO2017128964A1 true WO2017128964A1 (zh) 2017-08-03

Family

ID=56403284

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/071121 WO2017128964A1 (zh) 2016-01-29 2017-01-13 一种应用融合方法及装置

Country Status (5)

Country Link
US (1) US10552233B2 (zh)
EP (1) EP3404536A4 (zh)
CN (1) CN105786484B (zh)
BR (1) BR112018015451A2 (zh)
WO (1) WO2017128964A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105786484B (zh) 2016-01-29 2019-05-10 华为技术有限公司 一种应用融合方法及装置
CN107065011B (zh) * 2017-06-22 2018-11-02 东北石油大学 一种应用于陆相盆地储层反演的曲线频率融合方法
EP3844700A4 (en) 2018-08-27 2021-08-25 Box, Inc. ACTIVITY-BASED APPLICATION RECOMMENDATIONS

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102360377A (zh) * 2011-10-12 2012-02-22 中国测绘科学研究院 一种空间聚类挖掘pse系统及其构建方法
CN104008135A (zh) * 2014-05-07 2014-08-27 南京邮电大学 一种多源异构数据库融合系统及其数据查询方法
CN104657371A (zh) * 2013-11-20 2015-05-27 腾讯科技（深圳）有限公司 一种数据展示方法和装置
CN105786484A (zh) * 2016-01-29 2016-07-20 华为技术有限公司 一种应用融合方法及装置

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2008511935A (ja) * 2004-08-31 2008-04-17 インターナショナル・ビジネス・マシーンズ・コーポレーション データ統合システムのためのユーザ・インターフェース
GB2428834A (en) * 2005-08-04 2007-02-07 Ibm Linking objects with graphical user interface items
EP2199908A1 (de) * 2008-12-22 2010-06-23 ControlExpert GmbH Zugriffsverfahren auf ein Übertragungsmedium
US10241752B2 (en) 2011-09-30 2019-03-26 Apple Inc. Interface for a virtual digital assistant
US9038177B1 (en) * 2010-11-30 2015-05-19 Jpmorgan Chase Bank, N.A. Method and system for implementing multi-level data fusion
US10417037B2 (en) 2012-05-15 2019-09-17 Apple Inc. Systems and methods for integrating third party services with a digital assistant
US9400647B2 (en) * 2013-03-15 2016-07-26 Sap Se Application discovery and integration using semantic metamodels
CN103440303A (zh) * 2013-08-21 2013-12-11 曙光信息产业股份有限公司 一种异构云存储系统及其数据处理方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102360377A (zh) * 2011-10-12 2012-02-22 中国测绘科学研究院 一种空间聚类挖掘pse系统及其构建方法
CN104657371A (zh) * 2013-11-20 2015-05-27 腾讯科技（深圳）有限公司 一种数据展示方法和装置
CN104008135A (zh) * 2014-05-07 2014-08-27 南京邮电大学 一种多源异构数据库融合系统及其数据查询方法
CN105786484A (zh) * 2016-01-29 2016-07-20 华为技术有限公司 一种应用融合方法及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3404536A4 *

Also Published As

Publication number Publication date
BR112018015451A2 (zh) 2018-12-18
EP3404536A4 (en) 2019-06-19
CN105786484A (zh) 2016-07-20
US20180373575A1 (en) 2018-12-27
EP3404536A1 (en) 2018-11-21
US10552233B2 (en) 2020-02-04
CN105786484B (zh) 2019-05-10

Similar Documents

Publication Publication Date Title
US20240155312A1 (en) Layers in Messaging Applications
US10194288B2 (en) Sticker distribution system for messaging apps
JP6088520B2 (ja) 狭小ディスプレイ・デバイスのためのロール・ユーザー・インターフェース
US10331463B2 (en) Dynamic role-based view definitions in a repository system
US9948700B2 (en) ADFDI support for custom attribute properties
US10379819B2 (en) Generic editor layout using intrinsic persistence metadata
CN101866299B (zh) 修改便携式电子设备上本地应用的执行的方法和系统
JP6263199B2 (ja) アプリケーション間通信によるタスク完了
JP6426732B2 (ja) 自動的に生成された仮想環境を用いたユーザサポートエクスペリエンス
US20160092048A1 (en) Display of hierarchical datasets using high-water mark scrolling
TW201814510A (zh) 介面移動方法、裝置、智慧型終端機、伺服器和操作系統
US9176726B2 (en) Method and apparatus for developing, distributing and executing applications
US11797273B2 (en) System and method for enhancing component based development models with auto-wiring
US20150161547A1 (en) Methods and systems to define and execute customer declarative business rules to extend business applications
US20170300319A1 (en) Automatic submission of applications to applications stores
KR20150004817A (ko) 사용자 인터페이스 웹 서비스
US10552233B2 (en) Application convergence method and apparatus
JP2015509243A (ja) スターター・アプリケーションにおけるコンテキスト関連勧誘
US20180335909A1 (en) Using sections for customization of applications across platforms
US20230139886A1 (en) Device control method and device
US10303462B2 (en) Windows support of a pluggable ecosystem for universal windows application stores
KR20120123210A (ko) 애플리케이션의 저장 공간을 제공하기 위한 제어 방법과 그를 위한 단말 및 서버
US9418071B2 (en) Method and system for automatically initiating a file aggregation process between communicatively coupled devices
TW201606547A (zh) 用戶定義的動態事件
US9706013B2 (en) Mobile runtime conditional sections for surveys

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: 17743579

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112018015451

Country of ref document: BR

WWE Wipo information: entry into national phase

Ref document number: 2017743579

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2017743579

Country of ref document: EP

Effective date: 20180813

ENP Entry into the national phase

Ref document number: 112018015451

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20180727