CN111190649B

CN111190649B - Client building method, device and system

Info

Publication number: CN111190649B
Application number: CN201811261732.0A
Authority: CN
Inventors: 李彪; 尹帆; 曹桂荣
Original assignee: Alibaba Group Holding Ltd
Current assignee: Taobao China Software Co Ltd
Priority date: 2018-10-26
Filing date: 2018-10-26
Publication date: 2023-07-25
Anticipated expiration: 2038-10-26
Also published as: WO2020083059A1; CN111190649A

Abstract

The application discloses a client side building method which is applied to a server, wherein the method comprises the following steps: providing a plurality of components, the components corresponding to a plurality of operating systems; providing at least one of driving information, calling interface and data information required by the component to build a client running on the terminal device; wherein the driving information corresponds to an operating system, and the calling interface corresponds to the operating system. By adopting the scheme provided by the application, the client can be efficiently constructed, and the terminal equipment is configured and expanded, so that the terminal equipment is suitable for various application scenes and requirements, and the intelligent level of the terminal equipment is improved.

Description

Client building method, device and system

Technical Field

The present disclosure relates to the field of computer technologies, and in particular, to a method, an apparatus, and a system for client side construction.

Background

With the rapid development of computer technology and internet related technology, the intelligent level of various off-line application scenes is also higher and higher.

Taking the off-line retail industry as an example, more and more retail terminal devices with different functions and different use scenes are layered endlessly. For example, POS (Point Of sales) for cashing, barcode scale for weighing and printing labels, hand-held inventory device for inventory checking, in-out management, unattended vending device, unattended sample dispatch device, etc.

Therefore, a method for constructing a client is needed to efficiently construct the client, and configure and expand the terminal device, so that the method is suitable for various application scenes and requirements, and the intelligent level of the terminal device is improved.

Disclosure of Invention

The embodiment of the application provides a client construction method, device and system, so that a client can be constructed efficiently, terminal equipment is configured and expanded, the method, device and system are suitable for various different application scenes and requirements, and the intelligent level of the terminal equipment is improved.

The embodiment of the application adopts the following technical scheme:

in a first aspect, an embodiment of the present application provides a method for constructing a client, which is applied to a server, where the method includes:

providing a plurality of components, the components corresponding to a plurality of operating systems;

providing at least one of driving information, calling interface and data information required by the component to build a client running on the terminal device;

wherein the driving information corresponds to an operating system, and the calling interface corresponds to the operating system.

Optionally, in the method provided in the first aspect of the embodiment of the present application, the method further includes:

Determining information of a target operating system of the terminal equipment and information of a target component required by the client;

pushing at least one item of target driving information, a target calling interface and target data information required by the target component to the terminal equipment so as to construct a client running on the terminal equipment;

the target driving information corresponds to the target operating system, and the target calling interface corresponds to the target operating system.

and pushing the drive update information of the target drive information to the terminal equipment, wherein the drive update information corresponds to the target operating system.

receiving a drive acquisition request sent by the terminal equipment, wherein the drive acquisition request comprises information of a target operating system of the terminal equipment and information of target drive information required by a target component;

and returning target driving information corresponding to the target operating system to the terminal equipment based on the driving acquisition request.

receiving an interface acquisition request sent by the terminal equipment, wherein the interface acquisition request comprises information of a target operating system of the terminal equipment and information of a target calling interface required by a target component;

and returning a target calling interface corresponding to the target operating system to the terminal equipment based on the interface acquisition request.

receiving a data acquisition request sent by the terminal equipment, wherein the data acquisition request comprises information of a database to be configured required by the target component;

and returning target data information corresponding to the database to be configured to the terminal equipment based on the data acquisition request.

Optionally, in the method provided in the first aspect of the embodiment of the present application, the method further includes at least one of the following:

receiving a component acquisition request sent by the terminal equipment, and returning the target component to the terminal equipment, wherein the component acquisition request contains information of the target component required by the client;

And determining information of target components required by the client and pushing the target components to the terminal equipment.

In a second aspect, an embodiment of the present application provides a method for constructing a client, which is applied to a terminal device, where the method includes:

acquiring a target component required by a client, wherein the target component corresponds to various operating systems;

based on the target component, acquiring at least one of target driving information, a target calling interface and target data information required by the target component, wherein the target driving information corresponds to a target operating system of the terminal equipment, and the target calling interface corresponds to the target operating system;

and constructing the client running on the terminal equipment based on at least one of the target driving information, the target calling interface and the target data information.

Optionally, in the method provided in the second aspect of the embodiment of the present application, based on the target component, at least one of target driving information, a target calling interface and target data information required by the target component is acquired, including:

receiving at least one of the target driving information, the target calling interface and the target data information pushed to the terminal equipment by a server;

And the server determines at least one of the target driving information, the target calling interface and the target data information according to the information of the target operating system and the information of the target component.

Optionally, in the method provided in the second aspect of the embodiment of the present application, based on the target component, obtaining target driving information required by the target component includes:

determining a functional module required by the target component based on the target component;

and acquiring the target driving information corresponding to the target operating system for driving the functional module.

Optionally, in the method provided in the second aspect of the embodiment of the present application, the obtaining the target driving information corresponding to the target operating system for driving the functional module includes at least one of the following:

sending a drive acquisition request to a server, and receiving target drive information returned by the server based on the drive acquisition request, wherein the drive acquisition request comprises information of the target operating system and information of the target drive information;

and pulling the target driving information stored on the server.

Optionally, in the method provided in the second aspect of the embodiment of the present application, based on the target driving information, the constructing the client running on the terminal device includes:

and encapsulating the target driving information in the client to obtain a target calling interface of the functional module, so that the target component can call the functional module.

Optionally, in the method provided in the second aspect of the embodiment of the present application, the method further includes:

receiving drive update information of the target drive information pushed by the server, wherein the drive update information corresponds to the target operating system;

updating a target call interface of the function module in the client based on the drive update information;

and providing a new calling interface for the target component to call the functional module.

Optionally, in the method provided in the second aspect of the embodiment of the present application, based on the target component, acquiring a target call interface required by the target component includes:

and acquiring the target calling interface which is used for calling the functional module and corresponds to the target operating system.

Optionally, in the method provided in the second aspect of the embodiment of the present application, the obtaining the target call interface corresponding to the target operating system for calling the functional module includes at least one of the following:

an interface acquisition request is sent to a server, and the target calling interface returned by the server based on the interface acquisition request is received, wherein the interface acquisition request comprises information of the target operating system and information of the target calling interface;

and pulling the target call interface stored on the server.

Optionally, in the method provided in the second aspect of the embodiment of the present application, based on the target component, obtaining target data information required by the target component includes:

determining a database to be configured based on the target component;

and acquiring target data information corresponding to the database to be configured based on the database to be configured.

Optionally, in the method provided in the second aspect of the embodiment of the present application, based on the target data information, the constructing the client running on the terminal device includes:

and storing the target data information in the client, and providing a calling interface for the target data information for calling by the target component.

Optionally, in the method provided in the second aspect of the embodiment of the present application, based on the database to be configured, acquiring data information corresponding to the database to be configured includes at least one of the following:

sending a data acquisition request to a server, and receiving the target data information returned by the server based on the data acquisition request, wherein the data acquisition request comprises the information of the database to be configured;

and pulling the target data information stored on the server.

Optionally, in the method provided in the second aspect of the embodiment of the present application, obtaining a target component required by a client includes:

the target component is obtained from a server.

Optionally, in the method provided in the second aspect of the embodiment of the present application, the obtaining, from a server, the target component includes at least one of:

sending a component acquisition request to a server, and receiving the target component returned by the server, wherein the component acquisition request contains information of the target component;

receiving the target component pushed by the server, wherein the target component is determined by the server based on information of the target component required by the client;

Pulling the target component stored at the server.

the client receives a service processing request;

based on the target component, the client determines a function module to be called corresponding to the service processing request;

based on the calling interface of the function module to be called, the client calls the driving information corresponding to the function module to be called so as to process the service corresponding to the service processing request.

the client receives a service processing request;

based on the target component, the client determines data to be called corresponding to the service processing request;

based on the calling interface of the data to be called, the client calls the data to be called;

and the client returns the data to be called.

In a third aspect, an embodiment of the present application provides a client building system, where the system includes:

a server for providing a plurality of components, the components corresponding to a plurality of operating systems; the system is also used for providing at least one of driving information, calling interfaces and data information required by the components so as to construct a client running on the terminal equipment; wherein, the driving information corresponds to an operating system, and the calling interface corresponds to the operating system;

The terminal equipment is used for acquiring target components required by the client, and the target components correspond to various operating systems; the target component is further used for acquiring at least one of target driving information, a target calling interface and target data information required by the target component, wherein the target driving information corresponds to a target operating system of the terminal equipment, and the target calling interface corresponds to the target operating system; and the client is further configured to construct the client running on the terminal device based on at least one of the target driving information, the target calling interface and the target data information.

In a fourth aspect, an embodiment of the present application provides a client building apparatus, applied to a server, where the apparatus is configured to implement the client building method provided in the first aspect.

In a fifth aspect, an embodiment of the present application provides a client building apparatus, which is applied to a terminal device, where the apparatus is configured to implement the client building method provided in the second aspect.

In a sixth aspect, an embodiment of the present application provides an electronic device, applied to a server, where the electronic device includes:

a processor; and

A memory arranged to store computer executable instructions which, when executed, cause the processor to perform the client building method provided in the first aspect.

In a seventh aspect, embodiments of the present application provide a computer-readable storage medium storing one or more programs, which when executed by an electronic device comprising a plurality of application programs, cause the electronic device to perform the client building method provided in the first aspect.

In an eighth aspect, an embodiment of the present application provides an electronic device, which is applied to a terminal device, and includes:

a processor; and

a memory arranged to store computer executable instructions that, when executed, cause the processor to perform the client building method provided in the second aspect.

In a ninth aspect, embodiments of the present application provide a computer-readable storage medium storing one or more programs that, when executed by an electronic device comprising a plurality of application programs, cause the electronic device to perform the client building method provided in the second aspect.

The above-mentioned at least one technical scheme that this application embodiment adopted can reach following beneficial effect:

in the embodiment of the application, the server provides a plurality of components which can correspond to various operating systems, and provides at least one of driving information, a calling interface and data information required by the components, wherein the driving information corresponds to the operating systems, and the calling interface also corresponds to the operating systems. Therefore, the terminal equipment is convenient to construct the client.

Correspondingly, when the terminal equipment builds the client, the terminal equipment can acquire target components required by the client, and the target components correspond to various operating systems. On the basis, the terminal equipment can acquire target driving information, target calling interfaces and the like which are required by the target component and correspond to a target operating system of the terminal equipment based on the target component, so that the client can be efficiently built on the terminal equipment. On the basis, by adopting the scheme provided by the embodiment of the application, the terminal equipment can be efficiently configured and expanded, so that the terminal equipment is suitable for various different application scenes and requirements, and the intelligent level of the terminal equipment is improved.

Drawings

The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiments of the application and together with the description serve to explain the application and do not constitute an undue limitation to the application. In the drawings:

fig. 1 is a schematic structural diagram of a client building system according to an embodiment of the present application;

fig. 2 is a flow chart of a method for constructing a client according to an embodiment of the present application;

FIG. 3 is a schematic diagram of a logical architecture of a client in an embodiment of the present application;

fig. 4 is a schematic diagram of a logic architecture of a service system according to an embodiment of the present application;

fig. 5 is a schematic structural diagram of a client building device according to an embodiment of the present application;

fig. 6 is a schematic structural diagram of an electronic device in an embodiment of the present application.

Detailed Description

For the purposes, technical solutions and advantages of the present application, the technical solutions of the present application will be clearly and completely described below with reference to specific embodiments of the present application and corresponding drawings. It will be apparent that the described embodiments are only some, but not all, of the embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.

The embodiment of the application provides a client side constructing method which is respectively applied to a server and terminal equipment, so that a client side running on the terminal equipment can be efficiently constructed, and further, the service requirement of a service system can be met.

It should be noted that, under different application scenarios, the application requirements of the service system are different, and the specific meanings of the terminal device are also different.

Taking the off-line retail industry as an example, retail terminals such as physical shops, vending machine sites, etc. can use a variety of different types of terminal devices with different functions. For example, a hardware device for checkout at a retail terminal, a POS. For another example, when the retail terminal packages and sells the goods, the hardware equipment used for weighing the weight of the goods, adding the bar code and printing out the label is a bar code scale. For another example, the retail terminal may be a handheld device that performs inventory, warehouse entry, etc. Also for example, vending machines are machines that are deployed in vending sites, such as unattended vending equipment, unattended sample dispatch equipment, and the like. Etc.

Taking logistics management as an example, logistics terminals such as collecting stations, transfer stations and the like can also use a plurality of terminal devices with different types and different functions. For example, a bar code scale is a hardware device for packing and weighing articles at a collecting station. For another example, the handheld device is used for identifying, reading and writing labels such as bar codes, two-dimensional codes, electronic tags, RFID and the like attached to the articles at the transit station so as to track and trace the articles. Etc.

In the related art, a corresponding client needs to be installed on various terminal devices used in a service system. Because the hardware platforms on different terminal devices are different and the underlying operating systems are different, clients running on different terminal devices often need to be independently developed based on the hardware platforms and the operating systems, so that the labor cost is high and the development efficiency is low. In addition, when a terminal device needs to be updated, for example, when a configuration is updated or a function is extended, the terminal device often needs to be redeveloped, and therefore, later operation and maintenance are difficult.

Therefore, the embodiment of the application provides a cross-platform universal client construction method, which aims to efficiently construct a client, can flexibly configure and expand terminal equipment, is suitable for various different application scenes and requirements, and improves the intelligent level of the terminal equipment.

To build a client, an embodiment of the present application provides a client building system, referring to fig. 1, the system may include:

a server 200 for providing a plurality of components, the components corresponding to a plurality of operating systems; the system is also used for providing at least one of driving information, calling interfaces and data information required by the components so as to build a client running on the terminal equipment; the driving information corresponds to the operating system, and the calling interface corresponds to the operating system;

The terminal device 100 is configured to obtain a target component required by the client, where the target component corresponds to multiple operating systems; the target device is also used for acquiring at least one of target driving information, a target calling interface and target data information required by the target component based on the target component, wherein the target driving information corresponds to a target operating system of the terminal device, and the target calling interface corresponds to the target operating system; and the client is also used for constructing a client running on the terminal equipment based on at least one of the target driving information, the target calling interface and the target data information.

The technical schemes provided by the embodiments of the present application are further described in detail below with reference to the accompanying drawings.

Referring to fig. 2, an embodiment of the present application provides a method for constructing a client, which is applied to a client. Wherein the method may comprise:

s101: and acquiring a target component required by the client, wherein the target component corresponds to various operating systems.

It will be appreciated that a client may include a plurality of different components for executing different service logic of the client (which may be understood as different service functions of the client or different functions required by the terminal device), and thus each component corresponds to the service logic of the function to be implemented by the component.

For example, the login component is used for realizing the function of a user logging in a client, the cashing component is used for realizing the cashing and checkout functions of a merchant, the weighing component is used for realizing the weighing function of commodities, the printing component is used for printing bar codes, printing shopping tickets, printing cashing vouchers and the like, the member component is used for realizing the verification of member identities, the consumption of member points, the pushing of member exclusive information and the like, the shift component is used for realizing the shift function of staff, the preferential component is used for realizing the settlement of preferential orders and the like.

It should be noted that, in the embodiment of the present application, the target component of the client corresponds to multiple operating systems, and can be applied to multiple operating systems. Therefore, when a user builds the client on the terminal equipment, the user does not need to consider the bottom information such as the operating system of the terminal equipment where the client is located, but only needs to pay attention to the requirement of the client, and the target component required by the client can be determined.

Alternatively, when the target component required by the client is acquired, the user may determine the target component to be developed based on the component development environment (for example, tool kit, etc.) provided by the client according to the application requirement of the client, and autonomously perform the development of the target component.

Alternatively, the terminal device may obtain the target component required by the client from the server. Correspondingly, the server will provide a plurality of components, and these components correspond to a variety of operating systems, and thus are suitable for use with a variety of operating systems.

There are several ways in which the terminal device obtains the target component from the server:

alternatively, the terminal device may send a component acquisition request to the server, where the component acquisition request includes information about the service system, so as to inform the server of the primary use of the client built by the terminal device. On the basis, the server can return the components (comprising the target components) automatically recommended based on the information of the service system to the terminal equipment, and can also return a component list to the terminal equipment for the user to select the target components. Correspondingly, the terminal equipment receives the components returned by the server, so that the target components required for creating the client are obtained.

Alternatively, the server may push the component (including the target component) directly to the terminal device; correspondingly, the terminal equipment can directly receive the components pushed by the server. For example, in an application scenario, to improve the security performance of a client, a server may actively push a security verification component to a terminal device, so that the re-created client can implement a security verification function. For another application scenario, for example, to monitor the running data of the client, the server may actively push the information reporting component to the terminal device, so that the re-created client can implement the function of information reporting.

Alternatively, the terminal device may pull the component stored on the server from the server as the target component directly according to the creation needs of the client. It will be appreciated that the components acquired by the terminal device from the server may be alternative components provided by the user to the terminal device based on the server, with the terminal device selecting the customizations.

Because the components in the embodiment of the application correspond to various operating systems and can be suitable for various operating systems, whether the POS machine is based on Windows or Android operating systems, the bar code scale is based on Linux operating systems, the handheld device is based on Android operating systems, or the vending machine is based on Android or Linux operating systems, the step S101 can be adopted, and target components required by the client can be obtained according to the actual requirements of the service system.

For example, for a POS, a settlement component and a ticket printing component can be included, and if the POS requires electronic signing, a signing component can also be included. For another example, for a barcode scale, a weighing assembly, a price tag printing assembly, and the like may be included. For another example, for a handheld device, a code scanning component, a barcode printing component, a shift-shift component, and the like can be included. Also for example, for vending machines, a login component, a cashier component, a settlement component, a membership component, a coupon component, and the like may be included.

It will be appreciated that, when the client is initialized, step S101 may be performed to determine and obtain the target component required by the client. When a client that has been built is updated, for example, it is desired to add, delete, or modify components of the client, it can be understood that the client is being reconstructed. Thus, step S101 may be performed again to determine and acquire components that need to be added, deleted or modified, or to determine components that are required by the updated client in order to perform subsequent steps to complete the reconstruction of the client.

S103: and acquiring at least one of target driving information, a target calling interface and target data information required by the target component based on the target component.

It should be noted that, the target driving information corresponds to a target operating system of the terminal device, and the target calling interface corresponds to the target operating system, so that the client can normally operate on the target operating system.

S105: and constructing a client running on the terminal equipment based on at least one of the target driving information, the target calling interface and the target data information.

The specific procedure of the terminal device to acquire the target driving information, the target calling interface, and the target data information based on the target component, and the procedure of constructing the client based on these will be described below, respectively.

It will be understood that the driving information is used to drive the hardware module built in or external to the terminal device to operate, for example, a printer driver for driving the printer to print, a camera driver for driving the camera to collect images, and so on.

Because the target component is used for realizing a certain business logic of the client, the target component may need to be used for a part of built-in or external hardware functional modules on the terminal equipment. Therefore, when the target driving information required by the target component is acquired based on the target component, the functional module required by the target component can be determined based on the target component. It should be noted that, if some of all the functional modules required for the normal operation of the target component have been configured in the terminal device, only another part of the functional modules that have not been configured in all the functional modules may be determined as the functional modules required for the target component.

For example, for a POS, the settlement component may employ a hardware module such as a keyboard and display, and the receipt printing component may employ a printer module. Thus, the functional modules required for the target assembly may include a keyboard module, a display screen module, a printer module, and the like. It should be noted that, if a portion of the functional modules (e.g., the keyboard module) are already configured in the POS machine, the functional modules required by the target component may be determined as those portions of the functional modules (e.g., the display screen module and the printer module) that are not yet configured.

For another example, if it is desired to add a signature component to the POS machine so that the POS machine has an electronic signature function, based on the newly added component, i.e., the signature component, the handwriting board module may be determined as a functional module required by the target component (specifically, the signature component at this time), so that the signature component invokes the handwriting board module to implement the electronic signature function.

For another example, if a face payment component is desired to be added to the POS machine, so that the POS machine can support the function of face payment, based on the newly added component, namely the face payment component, the camera module can be determined to be a functional module required by the target component (specifically, the face payment component at this time), so that the face payment component invokes the camera, and the acquisition of the face image is realized, and the function of face payment is further realized.

Also for example, on the above basis, if it is desired to replace the black-and-white printer module with a color printer module, the color printer module may also be determined as a function module required for the target component (in this case, specifically, the ticket printing component) so that the ticket printing component invokes the color printer to realize the function of printing color tickets.

On the basis of determining the functional module required by the target component, the terminal equipment can further acquire target driving information which is used for driving the functional module and corresponds to the target operating system, so that the target component can call the hardware function corresponding to the functional module, further realize the business logic corresponding to the component and complete the construction of the client. In the case where the server is capable of providing the driving information required by the target component and corresponding to the operating system, the client may acquire the target driving information in various ways.

Alternatively, when acquiring the target driving information corresponding to the target operating system for driving the functional module, the terminal device may send a driving acquisition request to the server, where the driving acquisition request includes information of the target operating system and information of the target driving information. Correspondingly, the server receives a drive acquisition request sent by the terminal equipment, and returns target drive information corresponding to the target operating system to the terminal equipment based on the drive acquisition request. On the basis, the terminal equipment receives target driving information returned by the server based on the driving acquisition request, and completes configuration of a functional module required by the target component, so that the target component can call the functional module to realize required business logic.

Optionally, after determining the information of the target operating system of the terminal device and the information of the target component required by the client, the server may directly push the target driving information required by the target component and corresponding to the target operating system to the terminal device. Correspondingly, the terminal equipment can receive target driving information pushed to the terminal equipment by the server so as to complete the configuration of the functional modules required by the target assembly.

Optionally, the terminal device may actively pull the target driving information stored on the server, and configure a function module required by the target component, so that the target component may call the function module to implement the required service logic.

In the embodiment of the present application, the driving information of the (hardware) function module is applicable to the operating system corresponding to the terminal device, so that the target driving information obtained by the terminal device from the server can drive the bottom hardware function of the terminal device, so that the bottom hardware function can be invoked by the target component, and the service logic corresponding to the target component is implemented.

It should be further noted that, on terminal devices loaded with different operating systems, the specific content of the driving information of the same hardware functional module may be different (it is understood that the driving of the hardware functional module is implemented in a code form adapted to the operating system), but the implemented hardware functions are the same. Therefore, the target component can call the functional module in the same call mode to realize business logic.

Optionally, when the terminal device performs step S105 and constructs a client running on the terminal device based on the target driving information, the target driving information may be encapsulated in the client to obtain a target call interface of the function module, so that the target component may call the function module. By adopting the mode, the driving information in different code realization forms is packaged into a unified calling interface, and the hardware capability of the terminal equipment is exposed to the target component, so that the calling of the target component to the hardware function is facilitated.

In addition, when the drive information of a certain functional module needs to be updated, the server may push the drive update information corresponding to the target operating system to the terminal device. Correspondingly, the terminal equipment directly receives the drive update information of the target drive information pushed by the server; based on the drive update information, the terminal equipment updates the target call interface of the functional module in the client, for example, repackages the updated drive information, and further provides a new call interface for the target component to call the functional module.

In addition, in order to provide the call interface to the function module for the target component, the terminal device may package the target driving information after receiving the target driving information of the function module in the above manner, or may directly provide the call interface to the function module for the terminal device by the server. In this case, the client may obtain, from the server, a target call interface required for the target component to call after determining the target component required for the client. It can be understood that the target call interface corresponds to a target operating system, and is applicable to the target operating system of the terminal device.

Optionally, when the terminal device obtains the target call interface required by the target component based on the target component, the functional module required by the target component may be determined based on the target component, and the target call interface corresponding to the target operating system for calling the functional module may be further obtained based on the functional module. In the case where the server is capable of providing a call interface required by the target component and corresponding to the operating system, the client may acquire the target call interface in a variety of ways.

Optionally, when acquiring the target call interface corresponding to the target operating system for calling the functional module, the terminal device may send an interface acquisition request to the server, where the interface acquisition request includes information of the target operating system and information of the target call interface. Correspondingly, the server receives an interface acquisition request sent by the terminal equipment, and returns a target calling interface corresponding to the target operating system to the terminal equipment based on the interface acquisition request. On the basis, the terminal equipment receives a target calling interface returned by the server based on the interface acquisition request, so that the target component can call the functional module by using the target calling interface, and the required business logic is realized.

Optionally, after determining the information of the target operating system of the terminal device and the information of the target component required by the client, the server may directly push the target call interface required by the target component and corresponding to the target operating system to the terminal device. Correspondingly, the terminal equipment can receive a target calling interface pushed to the terminal equipment by the server, so that the target component can call the functional module by utilizing the target calling interface, and the required business logic is realized.

Optionally, the terminal device may also actively pull the target call interface stored on the server, so that the target component may call the functional module by using the target call interface, to implement the required service logic.

It should be noted that, under the circumstance that the driving information of a certain functional module needs to be updated, the server may push, to the terminal device, the driving update information corresponding to the target operating system, so that the terminal device may be repackaged in the client as a new call interface, and the server may also push the new call interface at the same time, so that the client may provide the new call interface for the target component, so that the target component may call the functional module.

On the basis of acquiring the target call interface, the terminal device may expose the target call interface to the target component when the terminal device performs step S105 and builds the client based on the target call interface, so that the target component may call the corresponding functional module by using the target call interface, so as to implement the corresponding service logic.

When the hardware function module needs to be called in the business logic to be realized by the target component, the terminal equipment acquires the target driving information and/or the target calling interface required by the target component so that the target component can call the main process of the function module. It will be appreciated that the target component may also be running with partial data information. Therefore, when the client is built, the terminal device also needs to acquire target data information required by the target component based on the target component. Specifically, the terminal device may determine the database to be configured based on the target component, and further obtain, based on the database to be configured, target data information corresponding to the database to be configured. On this basis, the terminal device executes step S105, and when the client is built based on the target data information, the target data information may be stored in the client, and a call interface for the target data information may be provided for the target component to call.

It can be appreciated that the requirements of the business logic implemented by the target component may be different, the meaning of the database to be configured may be different, and the data information stored in the database to be configured will be different.

For example, the barcode scale may need to use the name/type/identifier of the item, the unit price of the item, etc. in order to calculate the actual price of the item for printing by the price tag printing component when executing the business logic corresponding to the weighing component. In this case, the database to be configured may be specifically an item unit price database in which correspondence relation between names/kinds/identifications of items and item unit prices is stored.

For another example, assuming that the weighing assembly of the bar code scale only needs to provide the actual weight of the item, and not the price of the item, in accordance with the business logic of the business system, the weighing assembly is implemented without using the item unit price database described previously. Meanwhile, the execution of the business logic corresponding to the price tag printing component needs to use the item unit price database, so that the price tag printing component calculates the actual price of the item and prints the price tag by combining the item unit price under the condition that the actual weight of the item is obtained.

For another example, when the handheld device executes business logic corresponding to the shift-exchange component, information about legal accounts, information about shift arrangement, and the like may be needed. In this case, the database to be configured may specifically include a legal account database, where identity verification information such as an identification of a legal account and a login password is stored. The database to be configured may further include a shift arrangement database, where a correspondence between an identification of an account and a shift time period or order may be stored.

Also, for example, vending machines may require account information for legitimate users, etc. when executing business logic corresponding to the login component. In this case, the database to be configured may be a legal account database, where identification of a legal account, login password, fingerprint and other identity verification information are stored. The vending machine may need information such as membership grade, point value, etc. of the membership account when executing business logic corresponding to the membership component. In this case, the database to be configured may be specifically a member management database in which correspondence between information such as identification of a member account, a member level, a member point, and the like is stored.

Optionally, when acquiring data information corresponding to the database to be configured based on the database to be configured, the terminal device may send a data acquisition request to the server, where the data acquisition request includes information of the database to be configured. Correspondingly, the server receives a data acquisition request sent by the terminal equipment, and returns target data information to the terminal equipment based on the data acquisition request. On the basis, the terminal equipment receives target data information which is returned by the server based on the data acquisition request and corresponds to the database to be configured, so that the client can call the target data information to realize the required business logic.

Optionally, the server may actively push the target data information corresponding to the database to be configured to the terminal device. Correspondingly, the terminal equipment can receive the target data information pushed by the server so as to support the execution requirement of the business logic corresponding to the target component.

Optionally, the terminal device may actively pull, after determining the database to be configured, the target data information stored on the server from the server, so as to support the execution requirement of the service logic corresponding to the target component.

It should be noted that, after obtaining the target data information corresponding to the database to be configured, the terminal device may further store the target data information in the local database module. It will be appreciated that the local database module may be constructed using a database (e.g., apache CouchDB) common to various operating systems (e.g., windows operating system, android operating system, etc.), so that the client may provide a call interface to the target data information for the target component to call, regardless of the type of operating system underlying the terminal device.

Fig. 3 is a schematic diagram of a logical architecture of a client configured by a terminal device executing the above-mentioned client configuration method. The logical architecture of the terminal device and the client, and the specific implementation of each logical architecture in the client building process will be illustrated layer by layer.

In this embodiment of the present application, the hardware modules included in the terminal device and the external hardware modules are all divided into hardware layers, which may include physical hardware, for example, a memory, a processor, a printer, a camera, a keyboard, a screen, a speaker, and the like, and may further include hardware drivers and/or a singlechip system corresponding to these hardware, so as to drive or control the physical hardware devices to work.

In the terminal device, an Operating System OS layer (collectively referred to as Operating System) is provided above the hardware layer, and the OS layer is formed by an Operating System installed on the terminal device. For example, a Windows or Android operating system may be installed on the OS layer of the POS device, an Android operating system may be installed on the OS layer of the handheld device, and an Android or Linux operating system may be installed on the OS layer of the vending device.

Above the OS layer is a software development tool SDK layer, which can be understood as part of the client. In the embodiment of the present application, a development tool (specifically, a hardware SDK) required for client development based on an OS layer and a hardware layer, and a hardware management module for managing hardware of the hardware layer, a hardware driver, and a hardware SDK of the SDK layer are integrated in the SDK layer. The hardware management module is used for providing updated information receiving, information processing, local monitoring and data uploading for the whole client and each layer of modules in the client. As shown in fig. 4, the hardware SDK may include a Read-Only Memory ROM (fully called Read-Only Memory), which provides hardware capabilities related to an operating system, such as security protection capability, power-on management capability, cloud control capability, exclusive operation capability, upgrade service capability, location service capability, encryption capability, and so on. Hardware capabilities for supporting stability and client development, such as storage capabilities, background services, automated testing capabilities, generating crash reports, and the like, may also be included in the hardware SDK.

In the embodiment of the present application, a general database suitable for different operating systems, for example, apache CouchDB, is also integrated in the SDK layer, and is used for providing user data, commodity category data, payment order data, member data, and the like. The universal database can provide a unified data storage model and a data read-write scheme, and a consistent database operation mode is provided for the components.

In order to realize communication between the server and the client, the SDK layer is also integrated with a data communication module, specifically, the data communication module can define a unified data communication protocol of the server and the client based on XML, and the protocol can include an interface protocol of RESTFul style, an ISO8583 data international message protocol, a custom protocol related to client update and the like. The above server may include a service server for implementing a service system, or may include a client building server for supporting client building, where the two servers may be the same or different in entity, and the embodiment of the present application is not limited to this.

In the embodiment of the application, the SDK layer is further integrated with a general gateway, and the general gateway can include encapsulation of protocols such as HTTP, TCP/IP, UDP, etc., so that a unified communication call mode is provided for the outside, so as to support the terminal device to perform internet and local area network communication. For example, the universal gateway is implemented by adopting JS/Weex Bridge, URL routing and the like.

Above the SDK layer, a rendering layer and a presentation layer are also included in the client. The rendering kernel in the rendering layer can integrate and encapsulate the chromoum kernel applicable to different operating systems so as to support terminal equipment provided with the operating systems such as Linux, windows, android and the like. It can be understood that in the embodiment of the present application, the rendering layer interfaces with the general gateway and the data communication module of the SDK layer, and can support the data request and the hardware capability call request of the presentation layer. And the rendering layer also adopts a general hybrid interface scheme, and the capability (comprising data capability and hardware capability) provided by the hardware SDK layer is injected into the encapsulated chromoum kernel for calling by components in the presentation layer so as to support the operation of different service logics.

The presentation layer comprises a renderer constructed by rendering logic which generates JavaScript based on a web scheme, and the renderer is used for providing a component applicable to a business system. Taking the off-line retail industry as an example, components can be created to respectively support the business logic of terminal equipment operated by buttons, such as a large screen of a POS machine, a small screen of a handheld device, a bar code scale, a vending machine and the like. It can be appreciated that under the renderer and components, a unified build, compile, publish tool is also provided in the presentation layer.

It should be noted that, in the case where the operating systems in the operating system layer are different, the logical architecture of the SDK layer is the same, so as to provide the rendering layer and the presentation layer with the same hardware capability and data capability calling manner. Meanwhile, in the case where operating systems in the operating system layer are different, the code implementation of the SDK layer is also different so as to be applicable to different operating systems.

Taking the logic architecture schematic diagram of the business system shown in fig. 4 as an example, the presentation layer may include a login component, a cashing component, a settlement component, a member component, a preferential component, and other components for implementing each business logic. Each component may correspond to an operations/presentation interface (e.g., related to screen presentation), may correspond to business logic and data to be invoked, and may correspond to hardware capabilities to be invoked.

In the embodiment of the application, on the basis of building the service system, the client can also receive the service processing request. It can be appreciated that the service processing request can be issued by a user operating on an operation interface corresponding to the component. After receiving the service processing request, the client (i.e. the client installed on the terminal device) may further determine, based on the target component, a function module to be invoked corresponding to the service processing request, and further invoke, based on an invocation interface of the function module to be invoked, driving information corresponding to the function module to be invoked, and execute service processing corresponding to the service processing request. Further, after executing the service processing corresponding to the service processing request, the client may also return a result of the service processing based on the component.

In addition, after receiving the service processing request, the client (i.e. the client installed on the terminal device) may further determine, based on the target component, data to be invoked corresponding to the service processing request, and further invoke and return the data to be invoked based on the invocation interface of the data to be invoked, so as to execute an operation corresponding to the service processing request.

For example, according to the business logic corresponding to the login component, first, the client may present the login interface to the user (at this point, the renderer will render the login interface). Secondly, the client can call the keyboard to receive login information (user name, password and the like) input by the user, and at the moment, the client needs to call the hardware capability of the keyboard; or, the client may call the fingerprint recognition module to receive the fingerprint input by the user, and at this time, the client needs to call the hardware capability of the fingerprint collection module.

Based on this, the client can further call the user data (which can be a user name and a password, or reserved fingerprint information of the user, etc.) reserved in the database, and verify the identity verification information input by the user to determine whether to allow login. The business logic of the login component is completed.

For another example, according to the business logic corresponding to the cashing component, first, the client may display the purchase interface to the user (at this time, the renderer will render the purchase interface) so that the user adds the item to be purchased. Second, the client may invoke the commodity price data reserved in the database in order to calculate the amount of money to be collected.

On the basis, the client can display a code scanning payment interface so that a user can conveniently conduct code scanning payment. Or the client side can also display a face payment interface and call a face acquisition module so as to acquire face information of the user to realize face payment. At this time, the client needs to adjust the hardware capability of the face acquisition module to acquire the face information of the user; the user face information reserved in the database is also required to be called so as to authenticate the user identity.

If the business logic of the cashing component further comprises a shopping receipt printing link, the client can further call the hardware capability of the printer module to realize the function of printing the shopping receipt.

It will be appreciated that the process of using the terminal device (essentially the terminal device in which the client is installed) and the process of processing the service request are a continuation of the client building method. In the use process of the terminal device, if the hardware capability or data of the terminal device needs to be updated or reconfigured, the client side can be updated or reconfigured by adopting the client side constructing method provided by the embodiment of the application.

The above mainly describes the procedure of the terminal device for client side construction. Correspondingly, the embodiment of the application also provides a client side constructing method applied to the server. Wherein the method may comprise:

providing at least one of driving information, calling interface and data information required by the component to construct a client running on the terminal device; the driving information corresponds to the operating system, and the calling interface corresponds to the operating system.

On the basis, optionally, the server can also determine the information of a target operating system of the terminal equipment and the information of target components required by the client; further pushing at least one item of target driving information, target calling interface and target data information required by the target component to the terminal equipment so as to construct a client running on the terminal equipment; the target driving information corresponds to the target operating system, and the target calling interface corresponds to the target operating system.

Optionally, the server may further push drive update information of the target drive information to the terminal device, where the drive update information corresponds to the target operating system.

Optionally, the server may further receive a drive acquisition request sent by the terminal device, where the drive acquisition request includes information of a target operating system of the terminal device and information of target drive information required by the target component; and returning target drive information corresponding to the target operating system to the terminal device based on the drive acquisition request.

Optionally, the server may further receive an interface acquisition request sent by the terminal device, where the interface acquisition request includes information of a target operating system of the terminal device and information of a target calling interface required by the target component; and returning a target calling interface corresponding to the target operating system to the terminal equipment based on the interface acquisition request.

Optionally, the server may further receive a data acquisition request sent by the terminal device, where the data acquisition request includes information of a database to be configured required by the target component; and returning target data information corresponding to the database to be configured to the terminal equipment based on the data acquisition request.

Optionally, the server may further receive a component acquisition request sent by the terminal device, and return a target component to the terminal device, where the component acquisition request includes information of a target component required in the client; and determining information of target components required by the client and pushing the target components to the terminal equipment.

It can be understood that the client building method executed by the server corresponds to the client building method executed by the terminal device in the foregoing embodiment, and the relevant descriptions in the foregoing embodiment are applicable to the present embodiment, which is not repeated herein.

It should be specifically noted that, the server capable of implementing the client side building method, providing the components required by the client side and the driving information required by the components and the like provided in the embodiments of the present application may be the same or different in entity, and the comparison of the present application is not limited.

Referring to fig. 5, the embodiment of the present application further provides a client building apparatus, which is applied to a terminal device, and the apparatus can implement the foregoing client building method executed by the terminal device. Specifically, the device may include:

the component acquisition module 101 is configured to acquire a target component required by the client, where the target component corresponds to multiple operating systems;

the information obtaining module 103 is configured to obtain, based on the target component, at least one of target driving information, a target calling interface, and target data information required by the target component, where the target driving information corresponds to a target operating system of the terminal device, and the target calling interface corresponds to the target operating system;

The client building module 105 is configured to build a client running on the terminal device based on at least one of the target driving information, the target call interface, and the target data information.

It can be understood that the above-mentioned client building apparatus can implement each step of the client building method executed by the terminal device provided in the foregoing embodiment, and the relevant explanation about the client building method is applicable to the client building apparatus, which is not repeated herein.

The embodiment of the application also provides a client building device which is applied to the server and can realize the client building method executed by the server. Specifically, the device may include:

the first providing module is used for providing a plurality of components, and the components correspond to various operating systems;

the second providing module is used for providing at least one of driving information, calling interfaces and data information required by the component so as to construct a client running on the terminal equipment; the driving information corresponds to the operating system, and the calling interface corresponds to the operating system.

It can be understood that the above-mentioned client building apparatus can implement each step of the client building method executed by the server provided in the foregoing embodiment, and the relevant explanation about the client building method is applicable to the client building apparatus, which is not repeated herein.

Fig. 6 is a schematic structural diagram of an electronic device according to an embodiment of the present application. Referring to fig. 6, at the hardware level, the electronic device includes a processor, and optionally an internal bus, a network interface, and a memory. The Memory may include a Memory, such as a Random-Access Memory (RAM), and may further include a non-volatile Memory (non-volatile Memory), such as at least 1 disk Memory. Of course, the electronic device may also include hardware required for other services.

The processor, network interface, and memory may be interconnected by an internal bus, which may be an ISA (Industry Standard Architecture ) bus, a PCI (Peripheral Component Interconnect, peripheral component interconnect standard) bus, or EISA (Extended Industry Standard Architecture ) bus, among others. The buses may be classified as address buses, data buses, control buses, etc. For ease of illustration, only one bi-directional arrow is shown in FIG. 6, but not only one bus or type of bus.

And the memory is used for storing programs. In particular, the program may include program code including computer-operating instructions. The memory may include memory and non-volatile storage and provide instructions and data to the processor.

The processor reads the corresponding computer program from the nonvolatile memory into the memory and then runs to form the client building device on a logic level.

When the processor is applied to the client, the processor executes the program stored in the memory and is specifically configured to perform the following operations:

based on the target component, acquiring at least one item of target driving information, a target calling interface and target data information required by the target component, wherein the target driving information corresponds to a target operating system of the terminal equipment, and the target calling interface corresponds to the target operating system;

and constructing a client running on the terminal equipment based on at least one of the target driving information, the target calling interface and the target data information.

When the processor is applied to the server, the processor executes the program stored in the memory and is specifically configured to perform the following operations:

providing at least one of driving information, calling interface and data information required by the component to construct a client running on the terminal device;

The driving information corresponds to the operating system, and the calling interface corresponds to the operating system.

The method performed by the client building device disclosed in the embodiment of the present application may be applied to a processor or implemented by a processor. The processor may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be performed by integrated logic circuits of hardware in a processor or by instructions in the form of software. The processor may be a general-purpose processor, including a central processing unit (Central Processing Unit, CPU), a network processor (Network Processor, NP), etc.; but also digital signal processors (Digital Signal Processor, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), field programmable gate arrays (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components. The disclosed methods, steps, and logic blocks in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with the embodiments of the present application may be embodied directly in hardware, in a decoded processor, or in a combination of hardware and software modules in a decoded processor. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in a memory, and the processor reads the information in the memory and, in combination with its hardware, performs the steps of the above method.

The electronic device may further execute the method executed by the client building device and implement the functions of the client building device in the foregoing embodiments, which are not described herein.

The present application also proposes a computer-readable storage medium storing one or more programs, the one or more programs including instructions, which when executed by an electronic device comprising a plurality of application programs, enable the electronic device to perform the method performed by the client building apparatus in the foregoing embodiment, and specifically configured to perform:

It will be appreciated by those skilled in the art that embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

In one typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include volatile memory in a computer-readable medium, random Access Memory (RAM) and/or nonvolatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of computer-readable media.

Computer readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by a computing device. Computer-readable media, as defined herein, does not include transitory computer-readable media (transmission media), such as modulated data signals and carrier waves.

It should also be noted that 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 one … …" does not exclude the presence of other like elements in a process, method, article or apparatus that comprises the element.

It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The foregoing is merely exemplary of the present application and is not intended to limit the present application. Various modifications and changes may be made to the present application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc. which are within the spirit and principles of the present application are intended to be included within the scope of the claims of the present application.

Claims

1. A client side building method applied to a server, wherein the method comprises the following steps:

Wherein, the driving information corresponds to an operating system, and the calling interface corresponds to the operating system;

the method further comprises the steps of:

receiving a drive acquisition request sent by the terminal equipment, wherein the drive acquisition request comprises information of a target operating system of the terminal equipment and information of target drive information required by a target component; the target driving information is used for driving a functional module required by the target assembly; the functional module is a hardware module;

and returning target driving information corresponding to the target operating system to the terminal equipment based on the driving acquisition request so as to construct a client running on the terminal equipment.

2. The method of claim 1, wherein the method further comprises:

3. The method of claim 1, wherein the method further comprises:

4. The method of claim 1, wherein the method further comprises:

5. The method of any of claims 1-4, wherein the method further comprises at least one of:

6. A client side building method applied to a terminal device, wherein the method comprises the following steps:

determining a functional module required by the target component based on the target component; the functional module is a hardware module;

Acquiring target driving information corresponding to the target operating system for driving the functional module;

acquiring a target calling interface and/or target data information required by the target component based on the target component, wherein the target calling interface corresponds to the target operating system;

constructing the client running on the terminal equipment based on at least one of the target driving information, the target calling interface and the target data information;

based on the target driving information, constructing the client running on the terminal device, including:

7. The method of claim 6, wherein obtaining the target drive information corresponding to the target operating system for driving the functional module comprises at least one of:

And pulling the target driving information stored on the server.

8. The method of claim 6, wherein the method further comprises:

receiving drive update information of the target drive information pushed by a server, wherein the drive update information corresponds to the target operating system;

9. The method of claim 6, wherein obtaining a target call interface required by the target component based on the target component comprises:

10. The method of claim 9, wherein obtaining the target call interface corresponding to the target operating system for calling the functional module comprises at least one of:

And pulling the target call interface stored on the server.

11. The method of claim 6, wherein obtaining target data information required by the target component based on the target component comprises:

determining a database to be configured based on the target component;

12. The method of claim 11, wherein constructing the client running on the terminal device based on the target data information comprises:

13. The method of claim 11, wherein based on the database to be configured, obtaining data information corresponding to the database to be configured comprises at least one of:

and pulling the target data information stored on the server.

14. The method of any of claims 6-13, wherein obtaining the target component required by the client comprises:

the target component is obtained from a server.

15. The method of claim 14, wherein obtaining the target component from a server comprises at least one of:

pulling the target component stored at the server.

16. The method according to any one of claims 6-13, wherein the method further comprises:

the client receives a service processing request;

17. The method according to any one of claims 6-13, wherein the method further comprises:

the client receives a service processing request;

and the client returns the data to be called.

18. A client building system, wherein the system comprises:

the server is further configured to receive a drive acquisition request sent by the terminal device, where the drive acquisition request includes information of a target operating system of the terminal device and information of target drive information required by a target component; the target driving information is used for driving a functional module required by the target assembly; the functional module is a hardware module; returning target driving information corresponding to the target operating system to the terminal equipment based on the driving acquisition request;

The terminal equipment is used for acquiring target components required by the client, and the target components correspond to various operating systems; the function module is also used for determining a function module required by the target component based on the target component; the functional module is a hardware module; acquiring the target driving information corresponding to the target operating system for driving the functional module; the target calling interface and/or target data information required by the target component are/is acquired based on the target component, and the target calling interface corresponds to the target operating system; the method is also used for constructing the client running on the terminal equipment based on at least one of the target driving information, the target calling interface and the target data information;

the terminal device is specifically configured to encapsulate the target driving information in the client when the client running on the terminal device is configured based on the target driving information, so as to obtain a target calling interface of the function module, and the target calling interface is used for the target component to call the function module.

19. A client building apparatus for use in a server, wherein the apparatus is configured to implement the client building method of any of claims 1-5.

20. A client building apparatus for application to a terminal device, wherein the apparatus is adapted to implement the client building method of any of claims 6-17.

21. An electronic device, applied to a server, comprising:

a processor; and

a memory arranged to store computer executable instructions which, when executed, cause the processor to perform the client building method of any of claims 1-5.

22. A computer readable storage medium storing one or more programs, which when executed by an electronic device comprising a plurality of application programs, cause the electronic device to perform the client building method of any of claims 1-5.

23. An electronic device, applied to a terminal device, comprising:

a processor; and

a memory arranged to store computer executable instructions which, when executed, cause the processor to perform the client building method of any of claims 6-17.

24. A computer readable storage medium storing one or more programs, which when executed by an electronic device comprising a plurality of application programs, cause the electronic device to perform the client building method of any of claims 6-17.