CN111078199A - Implementation scheme for Android middleware customized component platform - Google Patents

Abstract

The invention relates to the technical field of Android system middleware component customization, in particular to a platform implementation scheme of an Android middleware customization component, which comprises the following specific implementation modes: s1: stripping the middleware related to the product service characteristics in the Android system frame into independent component units, so that the middleware and the Android system frame are kept relatively independent; the set of stripped product service component units forms a middleware service platform; s2: establishing a corresponding compiling dependency relationship between a service component unit independent from an Android system frame and the Android system according to product development integration compiling requirements; the method is beneficial to realizing the platform of the core service component, is convenient to realize the integration and the customized development of the product on a multi-chip platform and different system versions, flexibly customizes the content based on the service characteristics of the middleware, and can meet the development requirements of various products.

Description

Implementation scheme for Android middleware customized component platform

Technical Field

The invention relates to the technical field of Android system middleware customization, in particular to a platform implementation scheme of an Android middleware customization component.

Background

The open source and open property and good application ecology of the Android system make the Android system become the most popular mobile operating system at present. Due to different application fields, Android-based intelligent terminal research and development generally needs to customize middleware components of a system to meet business requirements.

Meanwhile, market demands are various and constantly changing, so that product research and development, particularly development of middleware components related to business scenes, can quickly and flexibly meet various different demands.

At present, many middleware components of Android intelligent terminals are developed and directly customized based on a native system framework layer, and the middleware components comprise an application API (application programming interface) facing a service scene, a middleware service adaptation layer, a service support layer and the like. These custom business components are deeply tied to the system, resulting in a product that lacks flexibility in terms of subsequent maintenance, expansion, upgrades, etc.

When the diversified service requirements or requirements of the product are frequently changed and the service components are deeply bound with the system, the service requirements are difficult to meet by a single product project. And a product project is established for each service requirement change, and the maintenance cost and complexity are increased along with the upgrading of subsequent products or the change of service requirements, so that the product competitiveness is reduced.

The present application proposes a feasible solution to the above-mentioned problem.

Disclosure of Invention

The invention provides a platform implementation scheme for an Android middleware customized component, which can effectively solve the problems.

In order to achieve the purpose, the invention is realized by the following technical scheme:

an implementation scheme for Android middleware customization component platformization is specifically implemented as follows:

s1: stripping the middleware related to the product service characteristics in the Android system frame into independent component units, so that the middleware and the Android system frame are kept relatively independent;

the set of stripped product service component units forms a middleware service platform;

s2: and establishing a corresponding compiling dependency relationship between the service component unit independent from the Android system frame and the Android system according to the product development and integration compiling requirements.

Further, the assembly units peeled off in S1 may be combined according to the requirements of the product.

Further, the compiling dependency relationship in S2 is mainly realized by the following method:

and embedding corresponding hooks in the Android compiling system aiming at the compiling characteristic of the middleware, and dynamically searching corresponding business layer compiling files or objects based on the embedded hooks when the system is actually compiled.

Further, the compiling dependency relationship in S2 is mainly realized by the following method:

on product engineering compilation, establishing association between a middleware service component and a system for unified compilation, stripping the service middleware into independent component units and maintaining the independent component units independently, and dynamically establishing soft links for the middleware component engineering and the Android system dependent directory when downloading or executing compilation of product engineering source codes according to the compilation dependency relationship of the middleware component; and when the system is compiled, traversing to the middleware component based on the soft link, thereby realizing the complete system compilation of the product engineering.

Compared with the prior art, the invention has the beneficial effects that:

1. the invention strips the middleware component engineering related to the product service from the system frame for independent maintenance, is beneficial to realizing the platform of the core service component, and is convenient to realize the integration and the customized development of the product on a multi-chip platform and different system versions;

2. according to the invention, a corresponding compiling hook is established for the middleware service component in the Android system, and the content is flexibly customized based on the service characteristics of the middleware, so that the development requirements of various types of products can be met;

3. the invention also provides a method for performing association integration compilation on the middleware service component unit and the Android compilation system in a soft link mode, so that the middleware component keeps relatively independent in development and maintenance, flexible integration of the middleware component and different system platforms can be realized, and the requirements of multi-platform development products are met.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.

FIG. 1 is a schematic diagram of a middleware services component being stripped away;

FIG. 2 is a diagram of middleware compilation "hooks";

FIG. 3 is a schematic diagram of middleware services component and system "soft link" integration.

Detailed Description

In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

Example 1

Referring to the attached drawings 1 and 2, an implementation scheme for Android middleware customization component platformization specifically comprises the following implementation modes:

s1: stripping the middleware related to the product service characteristics in the Android system frame into independent component units, so that the middleware and the Android system frame are kept relatively independent; each component unit corresponds to an independent service function, including but not limited to: a service application layer, a service API interface layer, a service adaptation layer, a service supporting layer and the like;

the set of stripped product service component units forms a middleware service platform, wherein the platform can be continuously expanded and perfected according to the change of product requirements; the stripped assembly units can be correspondingly combined according to the requirements of products.

S2: for a service component unit independent from an Android system frame, aiming at the compiling characteristics of a service application layer, a service API interface layer, a service adaptation layer, a service supporting layer and the like to middleware, a corresponding hook is embedded in the Android compiling system, and when the system is actually compiled, a corresponding service layer compiling file or target is dynamically searched based on the embedded hook.

In the above steps, compiling a "hook" is a colloquial description, which can be understood as a mark or reference in Makefile, based on which the compile-time system will expand to find its true definition. The compiling hook needs to be correspondingly embedded in the compiling system based on the compiling of the business components, and the content can be customized based on the business requirements or characteristics of specific products.

Example 2

Referring to the attached drawings 1 and 3, an implementation scheme for Android middleware customization component platformization specifically comprises the following implementation modes:

s1: stripping the middleware related to the product service characteristics in the Android system frame into independent component units, so that the middleware and the Android system frame are kept relatively independent; each component unit corresponds to an independent service function, including but not limited to: a service application layer, a service API interface layer, a service adaptation layer, a service supporting layer and the like;

the set of stripped product service component units forms a middleware service platform, wherein the platform can be continuously expanded and perfected according to the change of product requirements; the stripped assembly units can be correspondingly combined according to the requirements of products.

S2: on product engineering compilation, a middleware service component independent from an Android system frame is associated with the system to be compiled in a unified way, a service middleware is stripped into an independent component unit and maintained independently, after the service middleware is kept relatively independent from the Android system, according to the compiling dependency relationship of the middleware component, when a product engineering source code is downloaded or compiling is executed, a soft link is dynamically established for a dependent directory of the middleware component engineering and the Android system, and therefore the service component unit and the Android system are kept relatively independent physically; and when the system is compiled, traversing to the middleware component based on the soft link, thereby realizing the complete system compilation of the product engineering.

It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.

The above examples are only intended to illustrate the technical solution of the present invention, but not to limit it; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present invention.

Claims (4)

1. An implementation scheme for Android middleware customized component platformization is characterized by comprising the following specific implementation modes:

s1: stripping the middleware related to the product service characteristics in the Android system frame into independent component units, so that the middleware and the Android system frame are kept relatively independent;

the set of stripped product service component units forms a middleware service platform;

s2: and establishing a corresponding compiling dependency relationship between the service component unit independent from the Android system frame and the Android system according to the product development and integration compiling requirements.

2. The implementation scheme of the Android middleware customized component platform as claimed in claim 1, wherein the component units stripped in S1 can be combined correspondingly according to product requirements.

3. The Android middleware customization component platform implementation scheme of claim 1 or 2, wherein the compiling dependency relationship in the S2 is mainly implemented by:

and embedding corresponding hooks in the Android compiling system aiming at the compiling characteristic of the middleware, and dynamically searching corresponding business layer compiling files or objects based on the embedded hooks when the system is actually compiled.

4. The Android middleware customization component platform implementation scheme of claim 1 or 2, wherein the compiling dependency relationship in the S2 is mainly implemented by:

on product engineering compilation, establishing association between a middleware service component and a system for unified compilation, stripping the service middleware into independent component units and maintaining the independent component units independently, and dynamically establishing soft links for the middleware component engineering and the Android system dependent directory when downloading or executing compilation of product engineering source codes according to the compilation dependency relationship of the middleware component; and when the system is compiled, traversing to the middleware component based on the soft link, thereby realizing the complete system compilation of the product engineering.

Images