CN110531961B - Intelligent service crust breaking system and method thereof - Google Patents
Intelligent service crust breaking system and method thereof Download PDFInfo
- Publication number
- CN110531961B CN110531961B CN201910675891.3A CN201910675891A CN110531961B CN 110531961 B CN110531961 B CN 110531961B CN 201910675891 A CN201910675891 A CN 201910675891A CN 110531961 B CN110531961 B CN 110531961B
- Authority
- CN
- China
- Prior art keywords
- service
- data
- sub
- layer
- application data
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/20—Software design
- G06F8/24—Object-oriented
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/34—Graphical or visual programming
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/40—Transformation of program code
- G06F8/41—Compilation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Telephonic Communication Services (AREA)
- Stored Programmes (AREA)
Abstract
The invention provides an intelligent service crust breaking system and a method thereof, belonging to the technical field of application program development. The system comprises: incubator and service layer; the incubator is used for acquiring a first object interaction command; the incubator is used for selectively acquiring first application data of a first service through the service layer according to the first object interaction command; the incubator is used for selecting a processing mode and a packaging type according to second application data of a second service; the incubator is used for processing and packaging the first application data according to the processing mode and the packaging type and also generating a deployment piece for forming a sub-service corresponding to the first application data in the second service. The invention has the characteristics of low equipment coupling, low service dependence, multi-system form compatibility, multi-interaction form support, high expansibility, high flexibility and the like.
Description
Technical Field
The invention relates to the technical field of application program development, in particular to a method for constructing an intelligent service crust breaking framework, a method for intelligent service crust breaking, a system for intelligent service crust breaking, equipment for intelligent service crust breaking and a computer readable storage medium.
Background
With the rapid popularization of intelligent terminal equipment, the rapid promotion of mobile network speed and the continuous enrichment of content resources, the content services of various industries cover more and more aspects of life; content services (such as voice and video) in different forms can depend on respective development frameworks to carry out online experiments and delivery, but often the content services and the development frameworks have high coupling, dynamic application scene expansion cannot be effectively carried out, and new function realization and operation cooperation can be limited; lack of preset, on-demand deployed machine programs; a certain function service cannot be realized through the object interaction command; if the content services in different forms are required to be delivered and pushed out at various terminals, a large amount of architecture adaptation and debugging work is required to be performed due to the compatibility problem, so that the cost of the content services of different terminals in the stages of research and development, testing, transportation, popularization and the like is increased; if new content services need to be integrated in the application service, the framework of the application service has expansibility and flexibility problems.
Disclosure of Invention
The invention aims to provide an intelligent service crust breaking system and a method thereof, and the technical problems of high coupling, high cost, poor compatibility, poor expansibility and the like of various terminals in the prior art are solved.
In order to achieve the above object, an embodiment of the present invention provides a method for constructing an intelligent service crust breaking architecture, the method including:
s1) forming a service layer, wherein the service layer is configured to have a function of acquiring first application data of a first service;
s2) determining a second service and forming an incubator from second application data of the second service, wherein the incubator includes a data processing program and is configured to have a function of acquiring output data output by the service layer corresponding to the first application data and a function of forming a sub-service of the second service using the output data corresponding to the first application data,
the incubator can comprise a data processing program for realizing data operations such as request, response, scheduling, coding and decoding calculation, interaction processing, logic judgment, processing, compiling, integration and/or encapsulation, and the like, and particularly the data processing program comprises a plurality of sub-modules, wherein the plurality of sub-modules comprise a request module, a response module, a scheduling module, a coding and decoding calculation module, an interaction processing module, a logic judgment module, a processing module, a compiling module, an integration module and/or encapsulation module, and the like;
Breaking the shell, namely, the process that the incubator processes data through the data produced by the source service (the first service at the moment) sent by the service layer to form sub-service in the target service (the second service at the moment);
s3) integrating the service layer and the incubator into an intelligent service crust breaking framework.
Specifically, in step S1), the service layer is configured to have a function of acquiring first application data of the first service according to the first object interaction command.
Specifically, step S1) includes:
s101) forming a development suite and a machine program suite, wherein the development suite comprises a user interface library, a developer platform module, a plug-in library and a component library, the user interface library is at least provided with a user interface template of a Slice framework, and the machine program suite is at least provided with an intelligent voice interaction Bot library and a small program library;
s102) forming a service layer, wherein the service layer is configured to have a function of acquiring first application data of a first service through the development suite, and the service layer is configured to have a function of acquiring application data of a machine program through the machine program suite, wherein the application data of the machine program is used for forming a sub-service corresponding to the machine program.
Specifically, in step S102), the service layer is configured to have a function of acquiring application data of N services through the development suite, where N is a positive integer.
Specifically, in step S2), an incubator is formed according to the second application data of the second service, including:
s201) forming a management layer having a module plug-in integration function and a dependent component acquisition function corresponding to the data feature of the second application data according to the data feature of the second application data, wherein the management layer is configured to have a communication scheduling function for data transfer configured to acquire output data output by the service layer corresponding to the first application data, and the management layer is further configured to perform processing of the output data corresponding to the first application data by the module plug-in integration function and the dependent component acquisition function and to acquire processing data after the processing is completed;
s202) forming a functional layer with a function of acquiring processing data output by the management layer corresponding to the first application data and a function of encapsulating the processing data to form a deployment piece for forming sub-services in the second service according to the production environment characteristics, the functional characteristics and the operation characteristics of the second service;
S203) forming an interface layer having a function of delivering the deployment element for deployment in the second service;
s204) integrating the management layer, the functional layer and the interface layer into an incubator.
Specifically, in step S2), the incubator is configured to have a function of acquiring a second object interaction command through the interface layer and a function of generating deployment request data for forming a new sub-service corresponding to the second object interaction command, wherein the new sub-service is a new sub-service with respect to a deployed sub-service within the second service.
Specifically, in step S2), the interface layer is configured to have a function of acquiring the second object interaction command;
the function layer is configured to have a function of acquiring interaction data regarding the second object interaction command delivered by the interface layer;
the management layer is configured to have a function of acquiring the interaction data distributed by the function layer and to have deployment request data or sub-service execution data selectively generated from the interaction data according to sub-services within the second service.
Specifically, in step S2), the functional layer is configured to have a function of forming a current deployment piece by the sub-service execution data, where the current deployment piece is configured to perform an operation on a sub-service corresponding to the sub-service execution data after deployment in the second service;
The service layer is configured to have a function of acquiring third application data of a third service according to the deployment request data, wherein the third application data of the third service is used for forming a new sub-service.
Specifically, in step S2), the incubator has a function of forming a sub-service of the second service by using output data corresponding to the first application data in combination with a user interface template.
The embodiment of the invention provides a method for intelligent service crust breaking, which comprises the following steps:
s1) acquiring a first object interaction command and selectively acquiring first application data of a first service according to the first object interaction command;
s2) selecting a processing mode and a packaging type according to second application data of a second service, processing and packaging the first application data according to the processing mode and the packaging type, and generating a deployment piece for forming sub-services corresponding to the first application data in the second service after packaging is completed.
Specifically, in step S1), first application data of a first service is selectively obtained according to the first object interaction command, including:
and identifying first sub-service metadata corresponding to the first object interaction command, and selectively acquiring first application data of a first service according to the first sub-service metadata.
Specifically, the method further comprises the steps of:
s3) acquiring a second object interaction command, identifying second sub-service metadata corresponding to the second object interaction command, determining a current sub-service of the second service according to the second sub-service metadata, and generating an uninstaller for deleting the current sub-service in the second service or an update for changing the current sub-service in the second service by combining a processing mode and a packaging type of the current sub-service.
The embodiment of the invention provides a system for intelligent service crust breaking, which comprises:
incubator and service layer;
the incubator is used for acquiring a first object interaction command;
the incubator is used for selectively acquiring first application data of a first service through the service layer according to the first object interaction command;
the incubator is used for selecting a processing mode and a packaging type according to second application data of a second service;
the incubator is used for processing and packaging the first application data according to the processing mode and the packaging type and also generating a deployment piece for forming a sub-service corresponding to the first application data in the second service.
Optionally, the incubator includes: an interface layer, a functional layer and a management layer;
the management layer is used for processing the first application data and obtaining processing data after processing is completed;
the function layer is used for packaging the processing data and generating a deployment piece for forming a sub-service corresponding to the first application data in the second service after the packaging is completed;
the interface layer is to obtain the first object interaction command and to output the deployment to the second service.
Optionally, the module for supporting processing in the management layer includes: the system comprises a plug-in downloading module, a component management module, a communication scheduling module and a voice interaction module, wherein the plug-in downloading module has a module plug-in integration function corresponding to the data characteristics of the second application data, the component management module has a dependent component acquisition function corresponding to the data characteristics of the second application data, the communication scheduling module is used for transmitting data to the service layer and/or the functional layer, and the voice interaction module is used for identifying the first object interaction command.
Optionally, the module for supporting encapsulation in the functional layer includes: the system comprises a plug-in module, an additional component module and a user interface template configuration module, wherein the plug-in module is used for configuring the progress of the deployment piece, the additional component module is used for adding the function of the deployment piece, and the user interface template configuration module is used for pre-configuring a user interface or functional policy processing logic of a sub-service corresponding to the deployment piece.
Optionally, the interface layer includes an input module and an output module, where the input module is configured to obtain the first object interaction command, the output module is configured to send the deployment to the second service and/or form a morphological package of the deployment, and the morphological package is configured to present the deployment to the second service.
Optionally, the service layer includes a development suite and/or a machine program suite, wherein the development suite includes a user interface template library, a plug-in library, and a component library, and the machine program suite has different types of machine programs;
the machine program suite comprises an intelligent voice interaction Bot library and a applet library;
the user interface template library comprises user interface templates with a Slice frame, wherein each user interface template is provided with a plurality of Slice units;
the development suite is used for acquiring and integrating the data of the first service into the first application data through combining the user interface template library, the plug-in library and the component library, or the machine program suite is used for acquiring and integrating the data of the first service into the first application data through combining the machine program.
Optionally, the incubator is further configured to obtain a second object interaction command, identify sub-service metadata corresponding to the second object interaction command, determine a current sub-service of the second service according to the sub-service metadata, and combine a processing mode and an encapsulation type of the current sub-service to generate an uninstaller for deleting the current sub-service in the second service or generate an update for changing the current sub-service in the second service, where the update may be used for upgrading, forcedly upgrading, disabling and repairing a plug-in (for example, a faulty plug-in with a problem), the uninstaller may be used for uninstalling and forcedly uninstalling the plug-in, and the uninstaller provide security and guarantee functions.
In yet another aspect, an embodiment of the present invention provides an apparatus for intelligent service crust breaking, comprising:
at least one processor;
a memory coupled to the at least one processor;
wherein the memory stores instructions executable by the at least one processor, the at least one processor implementing the aforementioned methods by executing the memory-stored instructions.
In yet another aspect, embodiments of the present invention provide a computer-readable storage medium storing computer instructions that, when executed on a computer, cause the computer to perform the foregoing method.
Corresponding to the above, the service layer may implement obtaining data from different content service vendors, machine program (Bot) services (e.g., bot intelligent voice service) and developer platform modules, and implement sub-services within a second service (e.g., deployed service of a terminal) through the hatcher, while the implemented sub-services may obtain data from different content service vendors, provide Bot service predefined source domain services (the predefined source domain service is an instance of a source service, the first service is also an instance of a source service, the second service is an instance of a target service) or pre-define source domain service data in the developer platform modules as needed; the formation sub-service in the target service does not depend on the service layer to perform various processing, packaging and other operations, the incubator can automatically complete the crust breaking processing operation required by the formation sub-service of the target service, and the incubator and the service layer have decoupling characteristics;
according to the object interaction command, the incubator forwards or processes the object interaction command and then starts the driving service layer to acquire first application data;
The plug-in library and the component library of the development kit support the data interaction infrastructure required by realizing the first service, and the development kit with the capability of supporting the data interaction of the multi-type service is also preferred according to a specific example, and some common content services can be preset, preferably, for example, a machine program kit is formed, so that the time required by forming the sub-service can be saved and the unnecessary data flow can be reduced;
the construction of the incubator considers the characteristics of application data in the second service, processes and encapsulates output data of a compatible service layer and forms sub-services suitable for the second service;
the realization of the deployment part at the user side only needs the user to express the content service requirement through object interaction, the service layer and the incubator can realize the deployment part which has the content service function, provides the content service data and is used for forming (executing entity) sub-service according to the requirement, if the deployment part is an installation package, the installation can be rapidly completed in the production environment where the second service is located, and the data interaction of executing the content service in the second service is realized, so that the process that the user obtains a certain content service through the terminal is simplified, and on the other hand, the equipment storage space of the user terminal is saved because the user does not need to install a special application program of the certain content service;
The management layer and the functional layer are rich in various plug-ins and various components, so that the data of the first service are fused into the second service in a sub-service mode, and the data has localization characteristics relative to the second service;
the interface layer can be used for supporting a unified input/output layer and has the capability of realizing the form packaging of a corresponding user interface template library, so that the dynamic flexible expansion of sub-services is realized;
the invention has the characteristics of low equipment coupling, low service dependence, multi-system form compatibility, multi-interaction form support, high expansibility, high flexibility and the like.
Additional features and advantages of embodiments of the invention will be set forth in the detailed description which follows.
Drawings
The accompanying drawings are included to provide a further understanding of embodiments of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description serve to explain, without limitation, the embodiments of the invention. In the drawings:
FIG. 1 is a schematic diagram of a system according to an embodiment of the present invention;
FIG. 2 is a schematic flow chart of generating a multi-state output according to an embodiment of the present invention;
fig. 3 is a flowchart illustrating a process of forming a voice memo sub-service in combination with a display area according to an embodiment of the present invention.
Detailed Description
The following describes the detailed implementation of the embodiments of the present invention with reference to the drawings. It should be understood that the detailed description and specific examples, while indicating and illustrating the invention, are not intended to limit the invention.
Example 1
The embodiment provides a method for constructing an intelligent service crust breaking framework, which comprises the following steps:
s1) forming a service layer, wherein the service layer is configured to have a function of acquiring first application data of a first service;
s2) determining a second service and forming an incubator according to second application data of the second service, wherein the incubator comprises a data processing program and is configured to have a function of acquiring output data output by the service layer corresponding to the first application data and a function of forming a sub-service of the second service using the output data corresponding to the first application data, the sub-service being configured to have a function of data interaction with the first service;
s3) integrating the service layer and the incubator into an intelligent service shell breaking framework;
the first service is a service having demand data and belonging to an application service that is not deployed at the user terminal, such as a news content service; the first application data may be code data, interaction data, configuration data, content data, application data, or the like; the second service is a deployed service, such as an application service running on the user terminal, and the second application data may be code data, interaction data, configuration data, content data, application data, or the like, which meets the running requirements of the second service.
Specifically, in step S1), the service layer is configured to have a function of acquiring first application data of a first service according to a first object interaction command;
the object interaction command can be acquired by a user terminal in a mode of acquiring voice, touch behaviors, user images, videos and the like of a user.
Specifically, step S1) includes:
s101) forming a development suite and a machine program suite, wherein the development suite comprises a user interface library, a developer platform module, a plug-in library and a component library, the user interface library is at least provided with a user interface template of a Slice framework, and the machine program suite is at least provided with an intelligent voice interaction Bot library and a small program library;
s102) forming a service layer, wherein the service layer is configured to have a function of acquiring first application data of a first service through the development suite, and the service layer is configured to have a function of acquiring application data of a machine program through the machine program suite;
the development kit further comprises a developer platform module, wherein the developer platform module can be used for various content providers to access (an access process can set an authorization condition and a judgment strategy), and requests and receives data through an application program interface provided by a first service source domain (the data interaction process can be in an encryption environment, for example, a communication tunnel using an encryption certificate is used as an encryption environment), so that first application data of a first service can be obtained, and the developer platform module can be an integrated software development kit; the user interface library can be selected from a user interface UI (User Interface) library with a Slice frame in the production environment of the android terminal, wherein the Slice frame is a user interface template frame with rich elements and dynamic interaction content, and the UI library can provide a user interface template based on hypertext markup language (concrete, HTML 5) so as to improve the cross-terminal compatibility; the plug-in library can form a plurality of functions for processing the first application data, for example, the first application data is weather data, special effect plug-ins with different weather animations can be selected from the plug-in library, and for example, the first application data is application program data, time plug-ins with the current time acquisition function can be selected from the plug-in library, so that the flexibility and the expansibility are improved; each component can be a dependent module for supporting a plug-in function, first application data acquisition, output data generation and the like, so that compatibility, flexibility and expansibility are improved;
For example, the application data of the machine program is music Bot service data, the service layer provides the music Bot service data, and the sub-service, namely, the music Bot service, is formed in the second service through the incubator.
Specifically, in step S102), the service layer is configured to have a function of acquiring application data of N services through the development suite, where N is a positive integer;
for example, M sub-services are deployed in the second service of the user terminal device, and application data of a service corresponding to the M sub-services in the N services is to be used for updating current data of the corresponding sub-services; the service without corresponding sub-service in the N services is used for forming a new sub-service and presenting initial data in the new sub-service, M is a positive integer and is less than or equal to N.
Specifically, in step S2), an incubator is formed according to the second application data of the second service, including:
s201) forming a management layer having a module package integration function and a dependent component acquisition function corresponding to the data characteristics of the second application data according to the data characteristics of the second application data of the second service (for example, the second application data requires a specific type of shared object file support, etc.), wherein the management layer is configured to have a communication scheduling function for data transfer configured to acquire output data output by the service layer corresponding to the first application data, the management layer is further configured to perform processing of the output data corresponding to the first application data by the module package integration function and the dependent component acquisition function and to acquire processing data after the processing is completed;
S202) forming a functional layer with a function of acquiring processing data output by the management layer corresponding to the first application data and a function of encapsulating the processing data to form a deployment piece for forming sub-services in the second service according to the production environment characteristics, the functional characteristics and the operation characteristics of the second service;
s203) forming an interface layer having a function of delivering the deployment element for deployment in the second service;
s204) integrating the management layer, the functional layer, and the interface layer into an incubator;
a dispatching management module can be arranged in the management layer, and the dispatching management module can have the functions of calculation, judgment, dispatching, processing (such as assembly, integration and compiling) and the like; the data characteristics of the second application data may be a data storage type, a data processing rule, etc., for example, the data storage type is a Json data format storage type, and the data processing rule may be a deployment rule, an update rule, a permission rule, etc.; the production environment characteristic of the second service can be an android system environment, the functional characteristic can be an application program function of the second service, the functional characteristic is used for judging whether a sub-service of a required function exists or not by the scheduling management module, and the operation characteristic can be a requirement of the second service on a system process; the interface layer may further set an output module with a form packaging function (the output module in fig. 2 has rich output capability, which is called polymorphic Skill; the polymorphism is a plurality of forms, each form is a dimension form or a content data form, the dimension form may be a deployment piece, an update piece, a deletion piece, etc., the content data form is text, voice, an image, a video, etc., the input object interaction command may be polymorphic, the output may also be polymorphic, the polymorphism is realized through code packaging of the service layer and form packaging of the interface layer), the output module is used for performing form packaging adapted to the current production environment or adapted to the required presentation mode for elements or pre-packaging provided by the UI library, for example, providing weather forecast sub-service with a voice broadcasting function in an android user terminal device, the form packaging may be an integrated voice broadcasting plug-in; the deployment piece may install a package (or execution code) or update a repair package (or execution code), or may be just a data file with a storage format for presentation in a sub-service, or may be a configuration file for modifying the sub-service, for example, the deployment piece is update repair execution code (e.g., view service command in fig. 2), the deployment piece includes an execution command line and a configuration file, the execution command line may be an adb installation command, and the configuration file may be a Json format file and includes information such as a repair package name, a type, a signature, and a download address in the deployment piece.
Specifically, in step S2),
the incubator is configured to have a function of acquiring a second object interaction command through the interface layer and a function of generating deployment request data for forming a new sub-service corresponding to the second object interaction command;
the interface layer is configured to have a function of acquiring a second object interaction command;
the function layer is configured to have a function of acquiring interaction data regarding the second object interaction command delivered by the interface layer;
the management layer is configured to have a function of acquiring the interaction data distributed by the function layer and to have a function of selectively generating deployment request data or sub-service execution data according to the interaction data in accordance with sub-services within the second service;
the function layer is configured to have a function of forming a current deployment piece by the sub-service execution data, wherein the current deployment piece is used for executing an operation on a sub-service corresponding to the sub-service execution data after deployment in the second service;
the service layer is configured to have a function of acquiring third application data of a third service according to the deployment request data, wherein the third application data of the third service is used for forming a new sub-service;
Specifically, in step S2), the incubator has a function of forming a sub-service of the second service by using output data corresponding to the first application data in combination with a user interface template;
according to the second object interaction command, sub-service deployment corresponding to the third service is realized, and if the sub-service corresponding to the third service exists in the second service, the operation of the sub-service can be executed; the interface layer acquires a second object interaction command, the scheduling management module can identify the second object interaction command, match the identification result with preset sub-service metadata, and then use the matching result to determine whether the second service has the sub-service or not, if not, deployment request data can be generated, the deployment request data is used for delivering the sub-service to the second service through the service layer and the incubator, if so, sub-service execution data can be generated, and the sub-service execution data can be used for executing operations such as updating data of the sub-service, adding and deleting the sub-service, and the like.
Example 2
The intelligent service crust breaking architecture constructed in embodiment 1 can be used according to this embodiment, and this embodiment provides a method for intelligent service crust breaking, which includes:
S1) acquiring a first object interaction command and selectively acquiring first application data of a first service according to the first object interaction command;
s2) selecting a processing mode and a packaging type according to second application data of a second service, processing and packaging the first application data according to the processing mode and the packaging type, and generating a deployment piece for forming sub-services corresponding to the first application data in the second service after packaging is completed;
specifically, in step S1), first application data of a first service is selectively obtained according to the first object interaction command, including:
identifying first sub-service metadata corresponding to the first object interaction command, and selectively acquiring first application data of a first service according to the first sub-service metadata;
specifically, the method further comprises the steps of:
s3) acquiring a second object interaction command, identifying second sub-service metadata corresponding to the second object interaction command, determining a current sub-service of the second service according to the second sub-service metadata, and generating an uninstaller for deleting the current sub-service in the second service or an update for changing the current sub-service in the second service by combining a processing mode and a packaging type of the current sub-service;
As shown in fig. 3, the first object interaction command may be in various forms, such as voice, an augmented reality screen, a virtual reality screen, or the like; the reason why the first application data is selectively acquired is that there may be a sub-service corresponding to the function required in the first object interaction command in the second service, then a preset response may be presented in the second service on the user terminal through the interface layer by using the scheduling management module, for example, the first object interaction command is a voice "i need a voice memo", the voice memo sub-service already exists, and the preset response may be to adjust the display priority of the voice memo sub-service in the second service to be higher than the display priority of the other sub-services, so that the voice memo sub-service is presented in the sub-service display area of the second service on the user terminal; but even if the corresponding sub-service already exists, step S2) may be performed, for example, according to the second object interaction command, a deployment piece is obtained, where the deployment piece is a deployment piece with an updating or repairing function; if the corresponding sub-service does not exist, a deployment piece for installing the sub-service can be obtained, the sub-service is generated and arranged in the second service according to the priority order, a second service display area is updated on the user terminal equipment, and the voice memo sub-service is displayed.
Example 3
Based on embodiments 1 and 2, the present embodiment provides a system for intelligent service crust breaking, the system comprising:
incubator and service layer;
the incubator is used for acquiring a first object interaction command;
the incubator is used for selectively acquiring first application data of a first service through the service layer according to the first object interaction command;
the incubator is used for selecting a processing mode and a packaging type according to second application data of a second service;
the incubator is used for processing and packaging the first application data according to the processing mode and the packaging type and also generating a deployment piece for forming a sub-service corresponding to the first application data in the second service;
for example, after the incubator inquires the sub-service metadata, the component and the execution code required by the voice memo are formed in the service layer, so that output data is formed, the output data is first application data, the incubator processes and packages the first application data according to the characteristics of second application data, and then a deployment piece of the sub-service is formed, and the deployment piece can be installed on user terminal equipment running the second service, so that the voice memo sub-service is formed in the second service; preferably, the voice memo sub-service and the remaining sub-services occupy the same display area size and have the same display style, respectively, and each sub-service has a display priority, and for sub-services beyond the display area, a sub-service outside the current display area may be found by searching within the second service or operating a hardware device carrying the display area (e.g., operating a display screen of the user terminal to slide a scroll bar within the display area).
Optionally, the incubator includes: an interface layer, a functional layer and a management layer;
the management layer is used for processing the first application data and obtaining processing data after processing is completed;
the function layer is used for packaging the processing data and generating a deployment piece for forming a sub-service corresponding to the first application data in the second service after the packaging is completed;
the interface layer is used for acquiring the first object interaction command and outputting the deployment piece to the second service;
optionally, the module for supporting processing in the management layer includes: the system comprises a plug-in downloading module, a component management module, a communication scheduling module and a voice interaction module, wherein the plug-in downloading module has a module plug-in integration function corresponding to the data characteristics of the second application data, the component management module has a dependent component acquisition function corresponding to the data characteristics of the second application data, the communication scheduling module is used for transmitting data to the service layer and/or the functional layer, and the voice interaction module is used for identifying the first object interaction command;
optionally, the module for supporting encapsulation in the functional layer includes: the system comprises a plug-in module, an additional component module and a user interface template configuration module, wherein the plug-in module is used for configuring the progress of the deployment piece, the additional component module is used for increasing the function of the deployment piece, and the user interface template configuration module is used for pre-configuring a user interface or a functional policy processing logic of a sub-service corresponding to the deployment piece;
Functional policy processing logic such as loading logic of internal elements of a sub-service or processing logic corresponding to a system trigger event, etc.;
optionally, the interface layer includes an input module and an output module, where the input module is configured to obtain the first object interaction command, the output module is configured to send the deployment to the second service and/or form a morphological package of the deployment, and the morphological package is configured to present the deployment to the second service;
optionally, the service layer includes a development suite and/or a machine program suite, wherein the development suite includes a user interface template library, a plug-in library, and a component library, and the machine program suite has different types of machine programs;
the machine program suite comprises an intelligent voice interaction Bot library and a applet library;
the user interface template library comprises user interface templates with a Slice frame, wherein each user interface template is provided with a plurality of Slice units;
each intelligent voice interaction Bot in the intelligent voice interaction Bot library can be preset in a service layer according to the Bot intelligent voice service (a server side for providing content) so as to conveniently and quickly form sub-services in real time according to object interaction commands;
Each applet in the applet library can be pre-placed in a service layer according to the applet service so as to facilitate the instant and rapid formation of sub-services according to the object interaction command;
the Slice unit can be a scroll bar, a typesetting form for displaying small blocks, fonts, buttons and the like;
the development suite is used for acquiring and integrating the data of the first service into the first application data through combining the user interface template library, the plug-in library and the component library, or the machine program suite is used for acquiring and integrating the data of the first service into the first application data through combining the machine program;
optionally, the incubator is further configured to obtain a second object interaction command, identify sub-service metadata corresponding to the second object interaction command, determine a current sub-service of the second service according to the sub-service metadata, and generate an uninstaller for deleting the current sub-service in the second service or generate an updater for performing modification on the current sub-service in the second service in combination with a processing mode and an encapsulation type of the current sub-service;
optionally, the incubator and the service layer are both integrated in the same software development kit;
Referring to fig. 1 and fig. 2, for example, the first object interaction command is "i need weather forecast with weather animation and voice broadcast", the scheduling management module identifies the sub-service corresponding to the object interaction command and the required additional function, after the service layer forms the weather forecast machine program, the scheduling management module drives the plug-in downloading module and the component management module (if the sub-service of the web page version is provided, the second service can be browser application, the component should use style sheets and script components), and the special effect plug-in with weather animation, the voice plug-in and the support component are integrated into the weather forecast machine program; the plug-in module may be a GPT (GreedyPorter) plug-in module, and may be used to determine a sub-service process, for example, a same process or a cross process, where the additional component module is used to determine whether a dependency relationship of the sub-service has met a production environment where the second service is located or provide additional new functions (for example, implement a shopping function through a glutinous rice component), and the user interface template configuration module (Slice Action) may determine whether the second service has a support component required by the sub-service and set a data presentation manner of the sub-service; the machine program suite comprises a Bot service central control, wherein the Bot service central control and the scheduling management module conduct data interaction; the machine programs can be custom download programs, music programs, weather forecast programs and the like, and a voice interaction module can be preset in each machine program so that each machine program can directly and quickly respond to an object interaction command after forming a sub-service; the communication scheduling module can be used for transmitting various data, such as update data or repair data; the functional layer further comprises: the system comprises a safety management and control module, an instruction distribution module and a task scheduling module, wherein the safety management and control module can set functions of sub-service authentication, authority distribution and the like, the instruction distribution module can set and distribute a second service or trigger events of a system environment where the second service is located to certain sub-services, and task scheduling can realize transfer of a current task of a functional layer or current execution tasks for configuring the sub-services.
The invention constructs a service layer and an interface layer with universality and expansibility, and the service layer can effectively acquire service data of different content service manufacturers through the developer platform module and acquire data of different Bot intelligent services through the Bot service central control; the invention uses the user interface frame with high performance and high universality, realizes the cross-terminal capability and reduces the cost; the invention constructs sub-services in the locally deployed services through various plug-ins, components, applets (machine programs Bot) and user interface templates with a Slice framework, thereby obviously reducing the coupling and the dependence between application services and system equipment; the invention has flexible and rich command input and data presentation modes; the service layer constructed by the invention presets a plurality of machine programs and can quickly respond to generate corresponding sub-services; the invention has dynamic scene expansibility, provides convenience for service provider access, can simultaneously present a plurality of sub-services, and is easy to realize the data required to be presented by the service provider through the development kit.
The foregoing details of the optional implementation of the embodiment of the present invention have been described in detail with reference to the accompanying drawings, but the embodiment of the present invention is not limited to the specific details of the foregoing implementation, and various simple modifications may be made to the technical solution of the embodiment of the present invention within the scope of the technical concept of the embodiment of the present invention, and these simple modifications all fall within the protection scope of the embodiment of the present invention.
In addition, the specific features described in the above embodiments may be combined in any suitable manner without contradiction. In order to avoid unnecessary repetition, various possible combinations of embodiments of the present invention are not described in detail.
Those skilled in the art will appreciate that all or part of the steps in implementing the methods of the embodiments described above may be implemented by a program stored in a storage medium, including instructions for causing a single-chip microcomputer, chip or processor (processor) to perform all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
In addition, any combination of various embodiments of the present invention may be performed, so long as the concept of the embodiments of the present invention is not violated, and the disclosure of the embodiments of the present invention should also be considered.
Claims (16)
1. A method of constructing an intelligent service crust breaking architecture, the method comprising:
S1) forming a service layer, wherein the service layer is configured to have a function of acquiring first application data of a first service;
s2) determining a second service and forming an incubator according to second application data of the second service, wherein the incubator includes a data processing program and is configured to have a function of acquiring output data output by the service layer corresponding to the first application data and a function of forming a sub-service of the second service using the output data corresponding to the first application data;
s3) integrating the service layer and the incubator into an intelligent service shell breaking framework;
wherein, in step S2), an incubator is formed according to the second application data of the second service, including:
s201) forming a management layer having a module plug-in integration function and a dependent component acquisition function corresponding to the data feature of the second application data according to the data feature of the second application data, wherein the management layer is configured to have a communication scheduling function for data transfer configured to acquire output data output by the service layer corresponding to the first application data, and the management layer is further configured to perform processing of the output data corresponding to the first application data by the module plug-in integration function and the dependent component acquisition function and to acquire processing data after the processing is completed;
S202) forming a functional layer with a function of acquiring processing data output by the management layer corresponding to the first application data and a function of encapsulating the processing data to form a deployment piece for forming sub-services in the second service according to the production environment characteristics, the functional characteristics and the operation characteristics of the second service;
s203) forming an interface layer having a function of delivering the deployment element for deployment in the second service;
s204) integrating the management layer, the functional layer, and the interface layer into an incubator;
in step S2), the incubator is configured to have a function of acquiring a second object interaction command through the interface layer and a function of generating deployment request data for forming a new sub-service, which is a new sub-service with respect to a deployed sub-service within the second service, corresponding to the second object interaction command.
2. The method of claim 1, wherein in step S1), the service layer is configured to have a function of acquiring first application data of a first service according to a first object interaction command.
3. The method for constructing intelligent service crust breaking architecture as recited in claim 1, wherein in the step S2),
The interface layer is configured to have a function of acquiring a second object interaction command;
the function layer is configured to have a function of acquiring interaction data regarding the second object interaction command delivered by the interface layer;
the management layer is configured to have a function of acquiring the interaction data distributed by the function layer and to have deployment request data or sub-service execution data selectively generated from the interaction data according to sub-services within the second service.
4. The method for constructing intelligent service crust breaking architecture as recited in claim 3, wherein in the step S2),
the function layer is configured to have a function of forming a current deployment piece by the sub-service execution data, wherein the current deployment piece is used for executing an operation on a sub-service corresponding to the sub-service execution data after deployment in the second service;
the service layer is configured to have a function of acquiring third application data of a third service according to the deployment request data.
5. The method of building an intelligent service crust breaking architecture according to claim 1, wherein step S1) comprises:
s101) forming a development suite and a machine program suite, wherein the development suite comprises a user interface library, a developer platform module, a plug-in library and a component library, the user interface library is at least provided with a user interface template of a Slice framework, and the machine program suite is at least provided with an intelligent voice interaction Bot library and a small program library;
S102) forming a service layer, wherein the service layer is configured to have a function of acquiring first application data of a first service through the development suite, and the service layer is configured to have a function of acquiring application data of a machine program through the machine program suite.
6. The method of claim 1, wherein in step S2), the incubator has a function of forming sub-services of the second service by using output data corresponding to the first application data in combination with a user interface template.
7. A method for intelligent service crust breaking, the method comprising:
s1) acquiring a first object interaction command and selectively acquiring first application data of a first service according to the first object interaction command;
s2) selecting a processing mode and a packaging type according to second application data of a second service, processing and packaging the first application data according to the processing mode and the packaging type, and generating a deployment piece for forming sub-services corresponding to the first application data in the second service after packaging is completed;
the method further comprises the steps of:
s3) acquiring a second object interaction command, identifying second sub-service metadata corresponding to the second object interaction command, determining a current sub-service of the second service according to the second sub-service metadata, and generating an uninstaller for deleting the current sub-service in the second service or an update for changing the current sub-service in the second service by combining a processing mode and a packaging type of the current sub-service.
8. The method for intelligent service crust breaking according to claim 7, wherein the selectively obtaining the first application data of the first service according to the first object interaction command in step S1) comprises:
and identifying first sub-service metadata corresponding to the first object interaction command, and selectively acquiring first application data of a first service according to the first sub-service metadata.
9. A system for intelligent service crust breaking, the system comprising:
incubator and service layer;
the incubator is used for acquiring a first object interaction command;
the incubator is used for selectively acquiring first application data of a first service through the service layer according to the first object interaction command;
the incubator is used for selecting a processing mode and a packaging type according to second application data of a second service;
the incubator is used for processing and packaging the first application data according to the processing mode and the packaging type and also generating a deployment piece for forming a sub-service corresponding to the first application data in the second service; the incubator is further configured to obtain a second object interaction command, identify sub-service metadata corresponding to the second object interaction command, determine a current sub-service of the second service according to the sub-service metadata, and combine a processing mode and a packaging type of the current sub-service to generate an uninstaller for deleting the current sub-service in the second service or generate an updater for changing the current sub-service in the second service.
10. The system for intelligent service crust breaking of claim 9, wherein the system comprises a plurality of intelligent service devices,
the incubator comprises: an interface layer, a functional layer and a management layer;
the management layer is used for processing the first application data and obtaining processing data after processing is completed;
the function layer is used for packaging the processing data and generating a deployment piece for forming a sub-service corresponding to the first application data in the second service after the packaging is completed;
the interface layer is to obtain the first object interaction command and to output the deployment to the second service.
11. The system for intelligent service crust breaking of claim 10, wherein,
the module for supporting processing in the management layer comprises: the system comprises a plug-in downloading module, a component management module, a communication scheduling module and a voice interaction module, wherein the plug-in downloading module has a module plug-in integration function corresponding to the data characteristics of the second application data, the component management module has a dependent component acquisition function corresponding to the data characteristics of the second application data, the communication scheduling module is used for transmitting data to the service layer and/or the functional layer, and the voice interaction module is used for identifying the first object interaction command.
12. The system for intelligent service crust breaking of claim 10, wherein,
the module for supporting encapsulation in the functional layer comprises: the system comprises a plug-in module, an additional component module and a user interface template configuration module, wherein the plug-in module is used for configuring the progress of the deployment piece, the additional component module is used for adding the function of the deployment piece, and the user interface template configuration module is used for pre-configuring a user interface or functional policy processing logic of a sub-service corresponding to the deployment piece.
13. The system for intelligent service crust breaking of claim 10, wherein,
the interface layer comprises an input module and an output module, wherein the input module is used for acquiring the first object interaction command, the output module is used for sending the deployment piece to the second service and/or forming a form package of the deployment piece, and the form package is configured to be used for presenting the deployment piece to the second service.
14. The system for intelligent service crust breaking of claim 10, wherein,
the service layer comprises a development kit and/or a machine program kit, wherein the development kit comprises a user interface template library, a plug-in library and a component library, and the machine program kit comprises machine programs of different types;
The machine program suite comprises an intelligent voice interaction Bot library and a applet library;
the user interface template library comprises user interface templates with a Slice frame, wherein each user interface template is provided with a plurality of Slice units;
the development suite is used for acquiring and integrating the data of the first service into the first application data through combining the user interface template library, the plug-in library and the component library, or the machine program suite is used for acquiring and integrating the data of the first service into the first application data through combining the machine program.
15. An apparatus for intelligent service crust breaking, comprising:
at least one processor;
a memory coupled to the at least one processor;
wherein the memory stores instructions executable by the at least one processor, the at least one processor implementing the method of any one of claims 1 to 8 by executing the instructions stored by the memory.
16. A computer readable storage medium storing computer instructions which, when run on a computer, cause the computer to perform the method of any one of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910675891.3A CN110531961B (en) | 2019-07-24 | 2019-07-24 | Intelligent service crust breaking system and method thereof |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910675891.3A CN110531961B (en) | 2019-07-24 | 2019-07-24 | Intelligent service crust breaking system and method thereof |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110531961A CN110531961A (en) | 2019-12-03 |
| CN110531961B true CN110531961B (en) | 2023-05-23 |
Family
ID=68660970
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910675891.3A Active CN110531961B (en) | 2019-07-24 | 2019-07-24 | Intelligent service crust breaking system and method thereof |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110531961B (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104714828B (en) * | 2015-03-31 | 2017-06-09 | 北京奇虎科技有限公司 | Using installation, operation method and device |
| CN107295077A (en) * | 2017-06-16 | 2017-10-24 | 深圳易嘉恩科技有限公司 | Distributed cloud platform system based on micro services framework |
| US10007501B1 (en) * | 2017-05-19 | 2018-06-26 | Central South University | Method of deploying applications rapidly based on customized android platform |
Family Cites Families (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102170439B (en) * | 2011-04-20 | 2014-04-02 | 深圳创维－Rgb电子有限公司 | Application service expansion system |
| CN104376256B (en) * | 2014-12-02 | 2017-04-05 | 北京奇虎科技有限公司 | Program process hatching control and device |
| WO2017004391A1 (en) * | 2015-07-02 | 2017-01-05 | Convida Wireless, Llc | Content security at service layer |
| CN105657053A (en) * | 2016-03-04 | 2016-06-08 | 浪潮软件集团有限公司 | SOA architecture-based data integration exchange platform |
| US10409589B2 (en) * | 2016-07-12 | 2019-09-10 | Accenture Global Solutions Limited | Application centric continuous integration and delivery with automated service assurance |
| CN107193546B (en) * | 2017-04-11 | 2021-05-04 | 国网天津市电力公司信息通信公司 | Micro-service business application system |
| CN109086409B (en) * | 2018-08-02 | 2021-10-08 | 泰康保险集团股份有限公司 | Microservice data processing method and device, electronic equipment and computer readable medium |
-
2019
- 2019-07-24 CN CN201910675891.3A patent/CN110531961B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104714828B (en) * | 2015-03-31 | 2017-06-09 | 北京奇虎科技有限公司 | Using installation, operation method and device |
| US10007501B1 (en) * | 2017-05-19 | 2018-06-26 | Central South University | Method of deploying applications rapidly based on customized android platform |
| CN107295077A (en) * | 2017-06-16 | 2017-10-24 | 深圳易嘉恩科技有限公司 | Distributed cloud platform system based on micro services framework |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110531961A (en) | 2019-12-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10127057B2 (en) | Method and apparatus for dynamically implementing application function | |
| US9178948B2 (en) | Methods and apparatus for subscribing to multimedia delivery services in a data network | |
| CN102801755B (en) | A kind of management method of application and a kind of application platform | |
| US7603109B2 (en) | Methods and apparatus for over-the-air subscriptions | |
| CN102622241B (en) | A kind of method for upgrading software and device | |
| US20160227276A1 (en) | Intelligent television operation system | |
| EP2673723A1 (en) | Method and system for providing content | |
| CN106686200B (en) | Mobile application program updating method, mobile terminal and updating system | |
| CN104834541B (en) | Function module hanging method, carry system and the method for updating carry system | |
| US20150113533A1 (en) | Cloud system for managing creation and distribution of templates of virtual machines and method thereof | |
| CN104715309A (en) | Service control method and device | |
| US9286054B2 (en) | Deployment of mobile enterprise application platform | |
| CN111144878B (en) | Instruction generation method and instruction generation device | |
| CN105744341A (en) | Offline information releasing method and device | |
| CN110531961B (en) | Intelligent service crust breaking system and method thereof | |
| CN110493644B (en) | Television application upgrading method, television terminal and server | |
| CN112882733B (en) | Application updating method and device, electronic equipment and storage medium | |
| CN106484374B (en) | Method for controlling APK online and transfer server | |
| CN115002548A (en) | Method and device for calling application interface of television platform, terminal equipment and storage medium | |
| CN113268272A (en) | Application delivery method, device and system based on private cloud | |
| CN111831566A (en) | Test method, test device, electronic equipment and computer readable storage medium | |
| CN108134683B (en) | Terminal and bus architecture implementation method | |
| US10755321B1 (en) | Techniques for dynamic utilization of advertising capabilities by applications on user devices | |
| KR20110103888A (en) | System for accessing and sharing user defined contents and method of the same | |
| CN114153472A (en) | Bare metal server deployment method and device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |