TWI492155B - Methods and systems for executing applications on mobile devices using cloud services - Google Patents

Description

Method and system for executing an application on a mobile device using a cloud service

The invention relates to the execution of an application by a mobile device. In other words, the system integration and computing technology of the information technology is used, and the application to be executed on the mobile device first calls the system function to generate an application description file and loads it into the mobile device, and then starts. The application execution agent in the mobile device executes the application service request in the service call mode through the cloud service execution agent during the application execution process, and the method and system are related to using the system integration operation technology in the application file generation and The service request is executed in the relevant application.

System integration computing technology is a technology that is constantly evolving in the information technology industry, from early mainframe (mainframe) to master-slave architecture (client-server), to multi-tier application server (application server), and cloud computing (cloud) Computing) service model. System integration computing technology allows the system to deploy applications, services, data, etc. on different hosts or servers as needed to increase the flexibility, availability and scalability of the system. Each host or server can use the mode of the application or service to call or integrate with each other for the purpose of computing. Using application re-orientation, service deployment, and flexible storage of data, system integration computing technology provides a systematic approach to managing a centralized information and accessing an open information system to reduce the cost of system operations. Secondly, the current application on mobile devices is mostly based on a fixed service model, which is not only inelastic, but also has limited application scope and cannot be used to perform complex commercial applications. The invention integrates the simple application mode of the prior mobile device with the system integration computing technology, the application description file generation method and the service request execution method, and extends the business service application mode that can satisfy the highly flexible design.

The present invention proposes a method and system for combining cloud services and executing them on a mobile device using system integration computing techniques. The mobile device application developer can combine the pre-defined services in the cloud service system and the self-defined services to generate an application description file. The mobile device's service request agent can be parsed into the application description file to parse the interface and receive input data, and communicate with the service execution agent on the system. The service execution agent on the system uses the service execution trigger module to complete the service request, and returns the execution result to the mobile device, and displays the returned result on the mobile device according to the content set by the application description file. The application description file referred to in the present invention is not a general text file, but is a combination of a pre-defined or self-defined cloud service project using an internet service description language. A script file for the mobile device service request agent parsing and dynamically generating the operation interface. The service requesting agent of the mobile device referred to in the present invention is not only generally performing a preset function, or simply calling and executing an agent of a specific cloud service; instead, it can analyze the use of the Internet service description language (web service) Description language) An application description file composed of pre-defined or self-defined cloud service items and dynamically generated an operation interface, and a cloud service execution agent after inputting data according to a dynamically set component category attribute format in a dynamically generated operation interface After the program communicates and receives the execution result returned by the cloud service execution agent, the service request agent that displays the return result is displayed on the mobile device according to the content format set in the application description file.

In the first embodiment, a cloud service system includes at least one data storage unit, at least one application description file generation processing unit, and at least one service request execution processing unit. The cloud service system can utilize configuration settings to provide at least one information service. The cloud service system can also include plural A third-party service provider system that uses configuration settings to log in and communicate with the cloud service system and perform specific services. The cloud service system has at least one processing unit, which can utilize a pre-defined service on the data storage unit, or generate an application description file in a service combination manner for a self-defined service; and at least one processing unit can receive the service of the mobile device Request, and according to the service request category, call the service provided by the cloud service system itself, or call the service of the third-party service provider, and transmit the execution result back to the mobile device.

In a specific embodiment, the service request processing unit of the cloud service system may set the configuration to dynamically generate the item according to the input parameter and according to the service request category of the mobile device, and supplement the item with the missing value by the preset parameter value. , to complete the service request format.

In other specific embodiments, the cloud service system has at least one data storage unit configured to dynamically generate information related to the cloud service, such as service items, service configurations, service execution rules, and service providers, according to the input parameters.

In still other embodiments, the service request processing unit of the cloud service system can set the configuration to dynamically generate an information service that is linked to a specific ERP application system according to the input parameter to provide a commercial application in a third-party service provider role.

The second embodiment is an environment for applying an application file generation, the environment comprising at least one processing unit of the application file generation module, and at least one data storage unit that can be configured to dynamically generate the service-related data according to the input parameters. The application description file is stored in the application description file staging area before being generated, and is generated after all application generation requests are completed.

A third embodiment is a service request execution environment of a mobile device, the environment comprising a processing unit of the at least one service request execution module, and at least one data storage unit configured to dynamically generate the service-related data dynamically generated according to the input parameters . Service request execution is divided into two types: system service and third-party service provider service. The result of service request execution will be returned to mobile equipment. Set.

The above is only a brief description of the present invention, and further description will be hereinafter described in detail. The description of the content and the embodiments of the present invention does not define the main technical features of the scope of the patent application, nor does it limit the scope of the patent application.

In order to further clarify the present invention, it will be helpful to review the review by the reviewer, the description of the drawings, and the detailed description of the invention.

The matters discussed in the following Figures 1 through 5, and the various embodiments, which are used to describe the principles of the invention described herein, are merely illustrative and should not be construed as limiting the scope of the invention. It will be appreciated by those of ordinary skill in the art that the principles of the invention can be practiced on any suitably arranged device or system.

Figure 1 depicts an exemplary system 100 of the present invention. 1 shows a device 102 connectable to the Internet, a mobile device 104, and a third party service provider system 106 coupled to a cloud service system 108. The cloud service system 108 includes an application profile generation processing unit 110. The application description file referred to herein is not a general text file, but a pre-defined one using a web service description language. Or a self-defining cloud service project is combined and can be used by the mobile device service requesting agent to parse and dynamically generate a script file of the operation interface; a service request execution processing unit 112 is configured to execute the cloud service execution agent, And a data storage unit 114. The application profile generation processing unit 110 can be accessed by the device 102, and the service request execution processing unit 112 can communicate with the processing unit 116 on the mobile device 104 or with the processing unit 118 on the third party service provider system 106. . The processing unit 116 on the mobile device 104 will execute a service requesting agent that does not generally only perform pre-set functions, or simply calls and executes an agent of a specific cloud service, but can analyze the use of the Internet. The web service description language is predefined or defined by itself. The application description file combined by the cloud service item dynamically generates an operation interface, and the cloud service agent executed on the service request execution processing unit 112 after inputting the data in the dynamically generated component category attribute format in the dynamically generated operation interface After communicating and receiving the execution result returned by the cloud service agent, the service request agent displaying the return result is displayed on the mobile device according to the content format set in the application description file. One of the innovations of the present invention is to design a flexible and stable cloud service system 108 to provide cloud services to mobile devices in various environments through innovative workflows and combined with third-party services. This multi-hybrid cloud service model will become an important part of the foundation of mobile commerce.

The cloud service system 108 is an information system having the ability to store information and perform data operations. The cloud service system includes at least one server that can be accessed by the remote end. The cloud service system 108 can include a plurality of storage devices, can be referenced by a collection of storage units 114, and a plurality of processing units, which can be referenced by a collection of processing units 110 or 112. The cloud services system 108 can also include hardware that communicates with third party service provider systems. Second, the cloud services system 108 can also include software that communicates with third party service provider systems. Therefore, the cloud service system 108 communicates with the third-party service provider system 106 through software and hardware and through secure or general connection to complete the combined cloud service electronic operation. Although there is only one cloud service system in FIG. 1, the present invention is also applicable to an integrated system of a plurality of cloud services.

The third party service provider system 106 can be a computer system of a plurality of different industry environments or units, and can also include a plurality of servers, personal computers, or any communication device for performing related electronic operations of the cloud service request.

The third party service provider system 106 can communicate through any secure or general method, including a secure hypertext transfer protocol, a secure telnet, or a secure file transfer protocol. (secure file transfer protocol) to communicate with the cloud service system 108. It is generally understood that the adoption of a secure method is superior to the general method, and the method chosen is based on the functional requirements of the access. The invention is not limited to the use of any particular protocol or method of data transmission.

The communication between the third party service provider system 106 and the cloud service system 108 must be bidirectional. The so-called two-way communication means that data is transmitted and received between two or more communication devices.

In some embodiments, the cloud service system 108 may employ a Service Oriented Architecture (SOA) that provides cloud services by the server in a service call mode. When the user of the mobile device calls a function, such as an inventory inquiry, the service request agent on the mobile device requests the cloud service system 108 to provide the information inquiry service. The system or method disclosed by the present invention can be designed as a multi-tenancy, which allows multiple units to share the same entity database resource, but still maintains the completeness and privacy of the respective data.

One of the innovative features of the present invention is that when performing cloud services, a mixed processing mode can be employed between the data storage and data processing units of the plurality of cloud service systems 108. If some characteristics of the mobile device 104 are performed by the cloud service system 108 to perform better, then the cloud service system 108 can be selected to perform; otherwise, the mobile device 104 can be maintained for execution, so that effective arrangements and comparisons of resources can be achieved. Good performance.

2 shows an embodiment 200 of an application description file generation case 208 and a simplified application profile generation execution environment. Figure 2 also describes the functional elements in the application documentation generation environment. In some embodiments, the functional component may be a hardware component 202, a software component 204, or a combination of hardware and software. Some components may be application level software, while some components may be operating system level components. In other embodiments, two or more closely coupled components can operate on a single hardware platform to generate an application documentation. In other embodiments, the components may be linked across a network. Every embodiment may use Different hardware, software, and connected network architectures to achieve the set functions.

The execution environment 206 can include an application description file generation module 210. The functions executable by the application specification file generation module 210 include: receiving an application generation request 212, generating a request instruction classification 214, generating a request instruction format verification 216, and generating a request instruction execution. 218, and the execution result is returned 224. The Receive Application Generation Request function 212 can perform initial processing of the request, such as converting the received request instruction format to a format that other instructions can process. In some embodiments, receiving application generation request function 212 also performs some inter-component communication work.

The execution environment 206 can also include an application generation request instruction execution engine 222 that can be used to process the write request request execution function 218 of the application specification file generation module 210 to the generation request request. In column 220, a request to generate is awaiting execution. The application generation request execution engine 222 executes the result backhaul 224, may be written into the application specification file temporary storage area 226 according to the instruction request, or generate an application specification file generation file 228 for later downloading to the mobile device.

The application description file generation module 210 and the application generation request instruction execution engine 222 included in the execution environment 206 may be executable code generated after being compiled and linked, or may be controlled under the control of the execution environment 206. Managed code or source code. The executed mode may be an immediate processing mode or a batch mode. For example, in the batch mode, components such as a request request queue 220, a description file temporary storage area 226, and an application specification file generation file 228 may be combined.

In some embodiments, the service execution rule setting file 234 can be used to indicate the mode of operation of the generated file generation module 210, such as starting a different number of various components at different time periods to achieve load balance. purpose. The generate request instruction classification function 214 can classify the request events. The Generate Request Instruction Format Verification 216 confirms the correctness of the instruction format. Classify the request event or verify the correctness of the instruction format, The service item archive 230, the service configuration file 232, the service execution rule file 234, and one or a combination of the service provider unit files 236 are used to determine how the request event should be handled.

In some embodiments, the application profile generation module 210 may be similar or similar to some of the file generation modules developed as applications. When the application profile generation module 210 is used as a platform for application development, it can be combined with any third-party application development platform and eventually become part of the application development platform. The developed application can be executed on a mobile device, allowing developers to test and adjust application documentation. Once the application documentation test is complete, it can be deployed to the cloud service platform for download by users of mobile devices.

FIG. 3 shows an embodiment 300 of a service request execution case 308 and a simplified service request execution environment. Figure 3 also describes the functional elements in the service request execution environment. In some embodiments, the functional element may be a hardware component 302, a software component 304, or a combination of hardware and software. Some components may be application level software, while some components may be operating system level components. In other embodiments, two or more closely coupled components can operate on a single hardware platform to perform service requests. In other embodiments, the components may be linked across a network. Each of the embodiments may use different hardware, software, and connected network architectures to achieve the set functions.

The execution environment 306 can include a service request execution module 310, and the functions executable by the service request execution module 310 include: receiving a mobile device service request 312, a service request classification 314, a service request format verification 316, a service request execution 318, and executing The result is 324. The receiving mobile device service request function 312 can perform initial processing of the service request, such as converting the received service request instruction format into a format that other instructions can process. In some embodiments, the receiving mobile device service request function 312 also performs some inter-component communication work.

Execution environment 306 can also include a service execution engine 322, the service The execution engine 322 can be used to process the service request written to the service request queue 320 by the service request execution function 318 of the service request execution module 310, waiting to be executed. The service execution engine 322 returns the executed result 324. If the service request is a service provided by the cloud service platform itself, the execution result may be directly replied to complete the service request execution; if the service request is a service provided by the third party server, Some embodiments adopt a direct call mode and reply the result to the requester; in other embodiments, the service request is first written into the call service provider service message queue 326, and the third party service provider will The result is passed back to the service provider and returned to the result message queue 328, and the result is returned to the requester by the execution result backhaul function 324.

The service request execution module 310 and the service execution engine 322 included in the execution environment 306 may be executable code generated after being compiled and linked, or may be a control code to be executed under the control of the execution environment 306. Code) or source code. The execution mode may be an immediate processing mode or a batch mode. For example, in the batch mode, the generation request request queue 320, the service provider service message queue 326, and the service provider may return a result message. Column 328 and other components.

In some embodiments, the service execution rule setting file 334 can be used to indicate the mode of operation of the service request execution module 310, such as starting a different number of various components at different time periods for load balancing purposes. . The service request classification function 314 can classify service request events. The service request format verification 316 confirms the correctness of the service request format. To classify the service request event or verify the correctness of the service request format, the service item archive 330, the service configuration file 332, the service execution rule file 334, and one of the service provider unit files 336 or a combination thereof are used to determine the service. How to handle the event.

In some embodiments, the service request execution module 310 may be similar or similar to a module executed by some applications. When the service request execution module 310 is used as an application execution platform, it can be associated with any third providing cloud service. The combination of the platform and the platform will eventually become part of the mobile device application platform. The application description file generated by the technology disclosed by the present invention can be executed on the mobile device, and can be seamlessly integrated with the service request execution module disclosed by the present invention and the third party provider providing the cloud service. To meet the needs of mobile device users.

FIG. 4 is an embodiment of one of the methods 400 of generating an application description file disclosed by the present invention. In this embodiment, after the application profile developer sends the application profile generation request 402 to the application profile generation module 210, the application profile generation module 210 completes the process of receiving the application generation request function 212 and generates a request instruction. After the classification function 214, the generation request instruction format verification function 216, and the generation request instruction execution function 218, the generation request is written into the instruction queue 220. When the application generation request instruction execution engine 222 performs the application specification file generation instruction processing 404, it is determined whether the generation instruction is the service item 406 provided by the system, and if it is the service item provided by the system, the service item 408 provided by the system is displayed. And the service item 410 provided by the system is selected by the application description file developer; if not the service item provided by the system, the application service file developer defines a new service item 412. After the service project definition is completed, the application profile developer defines the interface for the service project, including: (1) selecting/setting the input project; (2) specifying the set value of the unselected project; and (3) selecting/setting The output item; (4) specifies the component type of the input item; (5) specifies the component type of the output item; and generates an interface description instruction language 414 of the application specification file. The generated interface description instruction language may be written into the application description file temporary storage area 416 before all the description files have been completed. After all the description files are completed, the application description file developer, after specifying the order of the service items 420 An application description file 422 is generated.

FIG. 5 is an embodiment of one of the methods 500 of performing the application note disclosed herein. Embodiment 500 describes a process in which a mobile device 502 executes an application, with the cloud service system 504, and a third party service The order of interaction of the donor 506 part. Other embodiments may use different orders, additional or fewer steps, and different terminology to achieve the same function. In other embodiments, various jobs or sets of jobs may be executed in a parallel or non-synchronized parallel mode of operation. The steps disclosed herein are illustrated only by the simplest principles of operation.

The mobile device 502 can execute an application pre-loaded into the mobile device as needed. When executed, the mobile device needs to start the service requesting agent 508 to complete the connection to the cloud service system job 510. The service requesting agent then reads the application specification file 512 and performs a parsing 514 of the application specification file. The interface description command language 414 in the application description file dynamically generates the interface 516 according to the selected/specified input items and component categories. The relevant parameter 518 is then entered by the mobile device user and a service request 520 is issued to the cloud service system. The cloud service system 504 needs to start the service agent 522 before providing the service. The service request execution module 310 of the cloud service system will receive the service request 524 of the mobile device, that is, the function of the service request execution module 312, and complete the service request classification and verification service request content 526, which is the service request execution module. 314,316 function. The service request format and execution service request 528 are then completed, which is the function of the service request execution module 318. The service request execution function 318 determines whether the service request is a service 530 provided by the system, such as the service provided by the system, the service execution engine 322 will execute the service request 532, and generate a service request result 534; if not the system The service provided calls the service 546 provided by the third party service provider. The third party service provider 506 needs to start the service execution program 544 before the service is provided. After the cloud service system 504 calls the service 546 provided by the third party service provider, the third party service provider receives the service request 548 and executes the service request 550. The service request result 552 is generated, and then the service request result 554 is returned to the cloud service system 504. The cloud service system 504 replies the service request execution result 536 to the mobile device 502, and the service request agent of the mobile device 502 receives the service request result, and outputs the project component class according to the setting. Do not display the service request result 538. When the mobile device user ends the application 540, the mobile device's service requesting agent ends 542.

Certain words mentioned in this manual are specifically defined to help understand. "Service Configuration" means that the definition of the service can be done using the configured model. The configuration model means that the service category can be divided into a common module, an option module, and an attachment module; if the service combination is defined, the common service module can be utilized. Service modules and additional service modules are selected to configure their configuration to define the desired combination of services for the purpose of application.

It will be apparent that alternative embodiments and methods of the invention are apparent to those of ordinary skill in the art. Therefore, the above description of the embodiments does not define or limit the invention. The scope of the claims and the scope of the claims are not to be construed as limited.

100‧‧‧ system

102‧‧‧Devices connected to the Internet

104‧‧‧Mobile devices

106‧‧‧Third-party service provider system

108‧‧‧Devices connected to the cloud service system

110‧‧‧Application note generation processing unit

112‧‧‧Service Request Execution Processing Unit

114‧‧‧Data storage unit

116‧‧‧Processing unit

118‧‧‧Third-party service provider processing unit

200‧‧‧Application documentation generation environment

202‧‧‧ hardware components

204‧‧‧Software components

206‧‧‧Application note generation execution environment

210‧‧‧Application note generation module

212, 214, 216, 218, 224‧‧‧ application description file generation function

220‧‧‧ Generate request script queue

222‧‧‧Application generation request instruction execution engine

226‧‧‧ Application note file temporary storage area

228‧‧‧Application documentation file generation

230‧‧‧ service project files

232‧‧‧Service Configuration File

234‧‧‧Service Execution Rules File

236‧‧‧Service provider file

300‧‧‧Service Request Execution Environment

302‧‧‧ hardware components

304‧‧‧Software components

306‧‧‧Executive environment

310‧‧‧Service Request Execution Module

312, 314, 316, 318, 324‧‧‧ service request execution function

320‧‧‧Service request queue

322‧‧‧Service Execution Engine

326‧‧‧ Service Provider Service Messages

328‧‧‧Service providers return results messages

330‧‧‧Service Project Files

332‧‧‧Service Configuration File

334‧‧‧Service Execution Rules File

336‧‧‧Service provider file

400‧‧‧Application note generation method

500‧‧‧Service request execution method

Figure 1 depicts an exemplary cloud service system and its environment in accordance with the present invention.

Figure 2 depicts an environment in which an example application document generation of the present invention is generated.

Figure 3 depicts an environment in which an example service request execution of the present invention is performed.

Figure 4 depicts a method of generating an application specification file in one example of the present invention.

Figure 5 depicts a method of performing an application of an example of the present invention.

302‧‧‧ hardware architecture

304‧‧‧Soft organization

306‧‧‧Executive environment

310‧‧‧Service Request Execution Module

312,314,316,318,324‧‧‧Service request execution function

320‧‧‧Service request queue

322‧‧‧Service Execution Engine

326‧‧‧call service provider service message queue

328‧‧‧Service providers return results messages

330‧‧‧Service Project Files

332‧‧‧Service Configuration File

334‧‧‧Service Execution Rules File

336‧‧‧Service provider file

Claims (10)

A system comprising: at least one service request execution and application specification file generation system, the service request execution and application specification file generation system comprising at least one application specification file generation processing unit, at least one service request execution processing unit, and at least one data storage Various parameters of the unit storage element and definition thereof; in the service request execution and application specification file generation system, the configuration may be configured to dynamically generate at least one service callable by the mobile device according to the input parameter dynamic generation; and the application description file generation processing The unit may set the configuration mode to execute the application description file generation method according to the dynamic generation of the input parameter, so as to complete the application description file generated by the requester by any requesting device that can be connected to the system, and the execution application description file is generated. The method includes: the application description file generation requester issues a generation request, and the system application description file generation module completes the following functions, including: receiving an application description file generation request, generating a request instruction classification, generating a request instruction format verification, and generating After the instruction is executed, the application generation request execution engine executes the application specification file generation request processing by the generation request instruction queue; if the request is the service item provided by the system, the item provided by the system is displayed, and is selected by the requester. The service item provided by the system; if the request is not a service item provided by the system, the requester defines a new service item; when the service item is selected or defined, The following interface definitions are made by the requester for the service item, including: 1) selecting/setting the input item; 2) specifying the set value of the unselected item; 3) selecting/setting the output item; 4) specifying the component type of the input item; Specify the component category of the output item; to generate the interface of the application description file to describe the instruction language. If the service item setting has not been completed, the system will first write the result to the application description file temporary storage area, and when the requester completes the service item write After the entry, the requester may specify the order of the service items, and then the system will generate an instruction to execute the final result to generate an application description file; and the service request execution processing unit may set a configuration method to dynamically generate the application according to the input parameter, to Completing a service request of at least one processing unit in the mobile device, the method for executing the application includes: the mobile device first starts a service requesting agent, completes a connection to the cloud service system, and then the service requesting agent reads the application description file, and performs Anatomy of the application documentation, based on the interface in the application documentation The instruction language, the service requesting agent can dynamically generate an interface according to the selected/specified input items and component categories; the mobile device user inputs relevant parameters and sends a service request to the cloud service system; before the cloud service system provides the service The service agent program needs to be started first; the service request function of the service request execution module of the cloud service system will receive the service request of the mobile device, and the service request classification function and the service request format verification function of the service request execution module will complete the service. Requesting the classification and verification service request content; then executing the service request execution module service request, the execution function, after completing the service request format, determining whether the service request is a service provided by the system, such as the service provided by the system The service execution engine will execute the service request and generate the service request execution result; if it is not the service provided by the system, call the service provided by the third-party service provider; the third-party service provider needs to start before providing the service Service execution program, waiting for the cloud After the system service call service provided by a third party service provider, third-party service provider receives a service request, the service request is performed, generating a service request result, And then replying the service request result to the cloud service system; the cloud service system replies the service request result, and returns the service request execution result to the mobile device, and the mobile device service request agent receives the service request result, and displays the service according to the output item component category. The result of the request; when the mobile device user ends the application, the service request agent of the mobile device ends. The system of claim 1, wherein the service request execution and the application specification file generating system are further configured to dynamically configure at least one processing unit in the service system of the plurality of service providers dynamically according to the input parameters. Communicate with each other and provide information about the information service in a timely manner. The service provider can provide services to any type of cloud service provider or service provider. The system of claim 1, wherein the application specification file generation processing unit and the service request execution processing unit generate a configuration specification file or execute a service request mode by setting a configuration, which may be an application mode. Or one of the service-oriented architecture patterns, or a combination thereof. The system of claim 1, wherein the storage unit can be configured to dynamically generate at least one service-related information (230, 330) and service configuration according to input parameters. File (232, 332), service execution rule file (234, 334), service provider unit file (236, 336); the service item (230, 330) may be provided by the system or provided by the service unit that completed the registration, or A combination of the services provided by the system and the services provided by the service unit that completed the registration. The system of claim 1, wherein the application description file generation processing unit further includes an application description file generation module, and the application file processed by the module is a description language having program execution capability ( Script) file, and parsable and dynamic execution receive application generation request, generate request instruction classification, generate request instruction format verification, Generating request instruction execution and execution result return function, and is not limited to the order in which the instructions are executed; and further includes an application generation request instruction execution engine to dynamically process the application generation request instruction. The system of claim 5, wherein the application description file generation module and the application generation request instruction execution engine may be executed in an immediate mode or in a batch mode; If the mode is executed, the following components such as the generation request command queue, the description file temporary storage area, and the application description file generation file can be selected. The system of claim 1, wherein the service request execution processing unit further comprises a service request execution module, performing a receiving mobile device service request, a service request classification, a service request format verification, a service request execution, And the execution result backhaul function is not limited to the order in which the instructions are executed; and further includes a service execution engine to process the service request instruction. The system of claim 7, wherein the service request execution module and the service execution engine may be executed in an immediate mode or in a batch mode; if executed in a batch mode, The following service request queues, call service provider service message queues, and service provider return message queues can be selected. A method for generating an application description file, the method comprising: an application description file generation requester issues a generation request, and the system application specification file generation module performs the following functions, including: receiving an application description file generation request, generating a request instruction classification, and generating a request After the instruction format verification and the generation request instruction are executed, the application generation request execution engine executes the application specification file generation request processing by the generation request instruction queue; if the request is the service item provided by the system, the system provides the item provided. And the requester selects the service item provided by the system; if the request is not the service item provided by the system, the requester defines a new service item; when the service item is selected or defined, the requester performs the service item for the service item The following interface definitions include: 1) Select / Set Input Project; 2) specify the set value of the unselected item; 3) select/set the output item; 4) specify the component type of the input item; 5) specify the component category of the output item; to generate the interface of the application description file to describe the instruction language, such as If the service item setting has not been completed, the system will first write the result to the application description file staging area. When the requester completes the service item write, the requester can specify the order of the service item, and then the system will generate the instruction execution final. The result generates an application documentation. A method for executing an application on a mobile device, the method comprising: the mobile device first launching a service requesting agent to complete a connection to the cloud service system, and then the service requesting agent reads the application description file and parsing the application specification file, According to the interface description instruction language in the application description file, the service requesting agent can dynamically generate an interface according to the input/specified input items and component categories; the mobile device user inputs relevant parameters and issues a service request to the cloud service system; The cloud service system needs to start the service agent before providing the service; the service request function of the service request execution module of the cloud service system receives the service request of the mobile device, and performs the service request classification function and service of the service request execution module. The request format verification function will complete the service request classification and verification service request content; then execute the service request execution function of the service request execution module, and after completing the service request format, it will determine whether the service request is a service provided by the system, such as Oriented The service provided by the system, the service execution engine will execute the service request and generate the service request execution result; if it is not the service provided by the system, the service provided by the third party service provider is called; the third party service provider is providing The service execution program needs to be started before the service. After the cloud service system calls the service provided by the third-party service provider, the third-party service provider receives the service request, executes the service request, generates the service request result, and then returns the service request result to the cloud. Service system; the cloud service system replies to the service request result, and also returns the service request execution result to the mobile device, and the mobile device service request agent receives the service The result is requested, and the service request result is displayed according to the output item component category; when the mobile device user ends the application, the mobile device's service requesting agent ends.