Cloud oriented stream scheduling method based on android platform

Patent metadata

Field	Value
Publication number	US-2018338013-A1
Application number	US-201715674535-A
Country	US
Kind code	A1
Filing date	Aug 11, 2017
Priority date	May 19, 2017
Publication date	Nov 22, 2018
Grant date	—

Abstract

The present invention discloses a cloud-oriented stream scheduling method based on Android platform, which aims to solve the problem that the calculation and storage capability of the mobile terminal device are limited and the application has a low expandability. The technical solution of the present invention is to build a core scheduling routine and an App management routine in a mobile terminal device based on Android operation system, and build a cloud management service subsystem in cloud server to construct a cloud-oriented stream scheduling system based on the Android platform to make the mobile terminal device enabled to dynamically install or uninstall the applications according to security attribute, user behavior habit, network status and transmission quality, processing capability of current mobile terminal device, and timed task of the application and achieve the consistent application view on the level of the mobile terminal device.

First claim

What is claimed is:

1 . A cloud-oriented stream scheduling method based on an Android platform, comprising the following steps:
a first step of building a cloud-oriented stream scheduling system based on an Android platform,
wherein the system comprises two layers, one of the two layers is a cloud management service subsystem operated on a cloud server, an other of the two layers is a core scheduling routine and an App management routine operated in a mobile terminal device; the cloud management service subsystem provides services of application download, scheduling strategy access, user configuration access, and user App status access for all mobile terminal devices connected to the cloud management service subsystem in a parallel manner, and a data center database is installed on the cloud management service subsystem; the cloud management service subsystem obtains access information needed in a mobile terminal device access operation by querying the data center database;
wherein the data center database further comprises four data tables corresponding to four services of the cloud management service subsystem, the four data tables includes: an application data table, wherein each table item of the application data table is entitled an App classification identifier, an App identifier, and an App installation package; a scheduling strategy data table, wherein each table item of the scheduling strategy data table is entitled a user type identifier, and a scheduling strategy information; a user configuration data table, wherein each table item of the user configuration data table is entitled a user identifier, and a user configuration information; an user App status data table, wherein each table item of the user App status data table is entitled the user identifier, the App identifier, and a user App status information;
wherein the App classification identifier indicates a class an App belongs to; the App identifier is a unique identifier to indicate a kind of the App; an App package file is stored in the App installation package; the user type identifier indicates a type of a user, wherein users of the same type have the same scheduling strategy; the user identifier is a unique identifier indicating the user of the mobile terminal device;
wherein the scheduling strategy information comprises a display strategy, a timed task strategy, an operation mode strategy, and a status saving strategy of the App; the display strategy is a list of N1 records, the content of each of the N1 records includes the App identifier, and a display manner; the display manner indicates an App display order corresponding to the App identifier and the display manner is one selected from the group consisting of “fixed”, “dynamically adjusted” and “preferential”; and N1 is equal to the number of applications controlled by the display strategy; the timed task strategy is a list of M records, the content of each of the M records includes the App identifier, and an operation time; the App corresponding to the App identifier will operate automatically within a time specified by the operation time, and M is equal to the number of applications controlled by the timed task strategy; the operation mode strategy is a list of K records, the contents of each of the K records include the App identifier, and an operation mode; the operation mode indicates that the App corresponding to the App identifier is one-off “stream execution”, “uninstallation prohibited” resident in system, or “dynamically uninstallation” determined by the core scheduling routine, and K is equal to the number of the applications controlled by the operation mode strategy; the status saving strategy is a list with L records, the content of each of the L records include the App identifier, and a whether to save indicator; the whether to save indicator indicates whether the status information of the App corresponding to the App identifier needs to be uploaded to the cloud management service subsystem before uninstallation and whether the status information of the App corresponding to the App identifier is needed to be downloaded and restored to a mobile smart terminal currently used by a user after installation, and L is equal to the number of the applications controlled by the status saving strategy;
wherein the user configuration information is a data list with N2 records, the content of each of the N2 records includes the App identifier, an application usage frequency, and an application display order; the application usage frequency records an average daily usage frequency of the application corresponding to the App identifier after the App is installed, and the application display order indicates the order and the location that the App is displayed in the display list, N2 is equal to the number of applications that have been installed in the mobile terminal device used by the user;
wherein the user App status information is a file that stores the content related to status and configuration of the App corresponding to the App identifier used by the user corresponding to the user identifier;
wherein the core scheduling routine and the App management routine is running on each of the mobile terminal devices, wherein the core scheduling routine provides a plurality of functions including a scheduling strategy processing, a silent installation or an App uninstallation, and a dynamic App adjustment, and performs a specific scheduling task of stream computing; the App management routine provides a plurality of functions including a user configuration processing, an App integration and display, and an App pre-processing before the installation and the uninstallation, including a plurality of functions such as an apk installation file downloading, a user App status information downloading, and a user App status information uploading;
wherein an HTTP protocol is used between the cloud management service subsystem and each of the core scheduling routine and the App management routine for allowing a communication, and an Android internal broadcast mechanism is used between the core scheduling routine and the App management routine for allowing the communication to asynchronously implement a plurality of internal functions in a message-driven manner;
wherein the cloud management service subsystem further comprises a global application management module, a scheduling strategy management module, a user configuration management module, and a user App status management module; the core scheduling routine further comprises a terminal strategy processing module, an App silent operation module, and an application dynamic scheduling module; the App management routine further comprises a terminal configuration processing module, an application preprocessing module, and an App integration display module;
wherein, the global application management module is connected to the application preprocessing module, the App integration display module, and the data center database; the global application management module receives a request for downloading an application installation package with the App identifier as a parameter sent by the application preprocessing module, finds an App installation package URL corresponding to the App identifier from the Application data table, and sends an App installation package corresponding to the App installation package URL to the Application preprocessing module; the global application management module also receives the request for downloading an App list with the App classification identifier as a parameter sent by the App integration display module, and finds all Apps belonging to the App classification identifier from the application data table to form the App list, and sends the App list to the App integration display module, wherein the App list includes two pieces of information, the two pieces of information includes the App identifier in the application data

Assignees

• Univ Central South

Inventors

• Liu Yaping
• Li Shaoyong
• Zhang Yaoxue
• Zhang Shuo
• Liao Haining

Classifications

• H04L67/26

  Electricity · mapped topic

• H04W24/02

  Arrangements for optimising operational condition · CPC title

• H04L69/04 Primary

  Protocols for data compression, e.g. ROHC · CPC title

• H04M3/42161

  via computer interface · CPC title

• H04L67/2828 Primary

  Electricity · mapped topic