CN113364826B

CN113364826B - Enhancement method of system characteristics of terminal equipment, terminal equipment and server

Info

Publication number: CN113364826B
Application number: CN202010152913.0A
Authority: CN
Inventors: 倪照军
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2020-03-06
Filing date: 2020-03-06
Publication date: 2023-10-03
Anticipated expiration: 2040-03-06
Also published as: CN113364826A

Abstract

The application provides a method for enhancing system characteristics of terminal equipment, the terminal equipment and a server. The terminal device may send a first request message including a first identification of the first system characteristic to the server in response to a request operation of the user for the first system characteristic that it does not have. Then, the terminal device receives a first response message containing a first download path from the server, and downloads a first data packet containing a function enhancement module and a description file according to the first download path, wherein the description file describes the identification of at least one interface class included in the function enhancement module. The terminal device may then invoke the functionality enhancement module based on the identification of the at least one interface class such that the terminal device has the first system characteristic. By the technical scheme provided by the application, the occupation of the software system to various resources of the terminal equipment can be reduced.

Description

Enhancement method of system characteristics of terminal equipment, terminal equipment and server

Technical Field

The present application relates to the field of terminal devices, and in particular, to a method for enhancing system characteristics of a terminal device, and a server.

Background

In order to increase the use scenarios of various types of terminal devices, the user experience is improved as much as possible or other purposes are achieved, and the system characteristics of the various types of terminal devices are more and more complex.

Accordingly, the more complex the system characteristics of the terminal device is, the number of functional modules included in the software system employed by the terminal device will also be greatly increased. If the functional modules in the software system adopted by the terminal equipment are greatly increased, the software system adopted by the terminal equipment can occupy various resources of the terminal equipment more, such as more operation memory and body memory of the terminal equipment, and the performance of the terminal equipment is easily affected. For example, the terminal device cannot respond to the operation of the user on the terminal device in time.

In view of this, improved solutions are desired in order to reduce the occupation of the resources of the terminal device by the software system.

Disclosure of Invention

The embodiment of the application provides a method for enhancing the system characteristics of terminal equipment, the terminal equipment and a server, which can dynamically enhance the system characteristics of the terminal equipment according to the use requirement of a user on the terminal equipment, thereby reducing the occupation of various resources of the terminal equipment by a software system adopted by the terminal equipment.

In a first aspect, a method for enhancing system characteristics of a terminal device is provided, where the method may be performed by the terminal device, or may be performed by a module or a chip system deployed in the terminal device. The terminal device may send a first request message containing a first identification of a first system characteristic to the server in response to a request operation of the user for the first system characteristic that it does not have. Then, the terminal device receives a first response message including a first download path from the server, and downloads a first data packet including a function enhancement module and a description file describing an identification of at least one interface class included in the function enhancement module according to the first download path. The terminal device may then invoke the functionality enhancement module based on the identification of the at least one interface class such that the terminal device has the first system characteristic. Therefore, the system characteristic of the terminal equipment can be dynamically enhanced according to the use requirement of the user on the terminal equipment, so that the occupation of the software system on various resources of the terminal equipment is reduced.

In one possible implementation, the terminal device may further determine, before invoking the function enhancement module according to the identification of the at least one interface class, whether an identification associated with the first identification is included in the identification of the at least one interface class. If the identifier of the at least one interface class does not include the identifier associated with the first identifier, it is indicated that the function enhancement module included in the first data packet may not support the terminal device to have the first system characteristic, and the terminal device does not need to make further calls to the function enhancement module, so that the first data packet is prevented from largely occupying the running memory and computing resources of the terminal device.

In one possible implementation manner, before the terminal device downloads the first data packet according to the first download path, the terminal device may further display a feature management interface, through which a first system feature that the terminal device does not have is indicated, so that a user performs a request operation on the first system feature through the feature management interface; correspondingly, the terminal equipment can receive the request operation of the user on the first system characteristic through the characteristic management interface.

In one possible implementation manner, the terminal device may load the function enhancement module into a memory of the terminal device, and call at least one interface class to implement calling the function enhancement module. More specifically, the terminal device may trigger the corresponding caller such that the caller invokes at least one interface class included in the function enhancing module that has been loaded into the memory.

In one possible implementation, after the terminal device loads the function enhancement module into the memory of the terminal device and invokes at least one interface class, the terminal device may further delete the function enhancement module from the memory of the terminal device in response to a release operation of the first system characteristic by the user. In this way, in the case that the user does not have a use requirement for a certain system characteristic, the function enhancement module for supporting the terminal device to have the system characteristic is prevented from occupying extra running memory of the terminal device.

In one possible implementation, after the terminal device deletes the function enhancement module from its memory in response to the user's release operation of the first system characteristic, the terminal device may further delete the first data packet from the nonvolatile memory of the terminal device in response to the user's delete operation of the first system characteristic. In this way, in the case that the user does not have a use requirement for a certain system characteristic, the data packet for supporting the terminal device to have the system characteristic is prevented from occupying extra memory of the body of the terminal device.

In one possible implementation manner, after the terminal device deletes the function enhancement module from its memory in response to the user's release operation of the first system characteristic, the terminal device may further record an accumulated time after the function enhancement module is deleted from its memory by the terminal device, and delete the first data packet from the nonvolatile memory of the terminal device if the accumulated time reaches a preset duration. In this way, in the case that the user does not have a use requirement for a certain system characteristic, the data packet for supporting the terminal device to have the system characteristic is prevented from occupying extra memory of the body of the terminal device.

In one possible implementation, the first request message may further include: a preset version number associated with the first identification, wherein the preset version number is not greater than a current version number of the first data packet. In this way, it is ensured that the first data packet downloaded by the terminal device for supporting the first system characteristic thereof does not have compatibility problems with the software system employed by the terminal device.

In one possible implementation, the first response message further includes: the data size of the first data packet. Correspondingly, the terminal device can also display the data volume of the first data packet to the user so as to be convenient for the user to confirm; and downloading the first data packet according to the first downloading path under the condition that the confirmation operation of the user is received.

In one possible implementation, the first request message further includes: any one or more of a system version number of a software system employed by the terminal device and a model number of the terminal device.

In a possible implementation manner, the terminal device may further receive a second response message sent by the server, and provide the second response message to the user, where the second response message is used to indicate a reason that the terminal device does not support the first system characteristic. Thus, the targeted processing of the terminal equipment by the user is facilitated, and the problem that the terminal equipment does not support the first system characteristic is solved.

In one possible embodiment, the first response message further includes a second download path for providing a download of a characteristic dependency indicating a dependency between at least two system characteristics. The terminal equipment can also download characteristic dependency relations according to the second download path; in case the at least one depended feature comprises a second system feature not possessed by the terminal device, a second request message is sent to the server, wherein the feature dependence indicates that the first system feature depends on the respective depended feature, the second request message comprising a second identification of the second system feature. In this way, the terminal device is enabled to have the first system characteristic on the basis of having the dependent characteristics of the items on which the first system characteristic depends.

In a second aspect, a method for enhancing system characteristics of a terminal device is provided, where the method may be performed by a server, or may be performed by a module or a chip system deployed in the server. The server may receive a first request message from the terminal device, the first request message comprising a first identification of a first system characteristic. The server may then determine a first download path associated with the first identification, the first download path for providing for downloading of a first data packet, the first data packet including a functional enhancement module and a description file, the functional enhancement module including at least one interface class, the description file describing the identification of the at least one interface class.

In a possible embodiment, the first request message further comprises a preset version number. Accordingly, the server may determine at least one candidate download path associated with the first identifier, and then determine a first download path from among the candidate download paths, where the first download path is associated with a current version number of the first data packet, and the current version number of the first data packet is not less than the preset version number.

In a possible embodiment, the first download address and the data volume of the first data packet are associated with each other in the server, and the corresponding first response message further includes the data volume of the first data packet.

In one possible implementation, the first request message further includes: any one or more of a system version number of a software system adopted by the terminal equipment and a model number of the terminal equipment.

In one possible implementation manner, the server may determine whether the terminal device supports the first system characteristic according to one or more of a system version number and a model number of the terminal device included in the first request message; if the terminal device does not support the first system characteristic, the server may send a second response message to the terminal device, where the second response message is used to indicate a reason why the terminal device does not support the first system characteristic.

In one possible embodiment, the first response message further includes a second download path for providing a download of a characteristic dependency indicating an interdependence between at least two system characteristics, the first system characteristic being one of the at least two system characteristics.

In a third aspect, a communication device is provided for implementing the method of any one of the first aspects.

In a fourth aspect, there is provided a communication device for implementing the method of any of the second aspects. In a fifth aspect, there is provided a terminal device comprising: a transceiver configured to send a first request message to a server in response to a request operation of a user for a first system characteristic that the terminal device does not have, wherein the first request message includes a first identification of the first system characteristic; a first response message is received from the server, wherein the first response message includes a first download path. A processor configured to download a first data packet according to the first download path, where the first data packet includes a function enhancement module and a description file, the function enhancement module includes at least one interface class, and the description file describes an identifier of the at least one interface class; and calling the function enhancement module according to the identification of the at least one interface class to enable the terminal equipment to have the first system characteristic.

In a possible implementation manner, the processor is further configured to determine whether the identifier of the at least one first interface includes an identifier associated with the first identifier.

In a possible implementation manner, the processor is further configured to display a feature management interface, where the feature management interface indicates the first system feature; and receiving a request operation of a user on the first system characteristic through the characteristic management interface.

In a possible implementation manner, the processor is specifically configured to load the function enhancement module into a memory of the terminal device and call the at least one interface class.

In a possible implementation manner, the processor is further configured to delete the function enhancement module from the memory of the terminal device in response to a release operation of the first system characteristic by a user.

In a possible implementation manner, the processor is further configured to delete the first data packet from the nonvolatile memory of the terminal device in response to a deletion operation of the first system characteristic by a user.

In a possible implementation manner, the processor is further configured to delete the first data packet from the nonvolatile memory of the terminal device if the accumulated time after deleting the function enhancing module from the memory of the terminal device reaches a preset duration.

In one possible implementation, the first request message further includes: at least one of a system version number of a software system adopted by the terminal device, a model number of the terminal device and a preset version number associated with the first identifier, wherein the preset version number is not greater than a current version number of the first data packet.

In a possible implementation manner, the first response message further includes a data amount of the first data packet. The processor is further configured to display the data amount of the first data packet to a user for confirmation by the user.

In one possible implementation, the first request message further includes: and any one or more of the system version number of the software system adopted by the terminal equipment and the model number of the terminal equipment.

In a possible embodiment, the transceiver is further configured to receive a second response message from the server, where the second response message is used to indicate a reason why the first system characteristic is not supported by the terminal device. The processor is further configured to provide a second response message to the user.

In a possible implementation, the first response message further includes a second download path for providing a download of a characteristic dependency, the characteristic dependency being indicative of a dependency between at least two system characteristics, the first system characteristic being one of the at least two system characteristics. The processor is further configured to download the characteristic dependency relationship according to the second download path. The transceiver is further configured to send a second request message to a server in case the at least one dependent characteristic includes a second system characteristic not possessed by the terminal device, wherein the characteristic dependency indicates that the first system characteristic depends on the at least one dependent characteristic, and the second request message includes a second identification of the second system characteristic.

In a sixth aspect, there is provided a server comprising: a transceiver for receiving a first request message from a terminal device, wherein the first request message comprises a first identification of a first system characteristic; and sending a first response message to the terminal equipment, wherein the first response message comprises a first downloading path, the first downloading path is associated with the first identifier, the first downloading path is used for providing downloading of a first data packet, the first data packet comprises a function enhancement module and a description file, the function enhancement module comprises at least one interface class, and the description file describes the identifier of the at least one interface class.

In one possible implementation, the first request message further includes: a preset version number associated with the first identification. The first identifier is associated with at least one candidate download path, the at least one candidate download path including the first download path, the first download path being associated with a current version number of the first data packet, the current version number of the first data packet being not less than the preset version number.

In a possible embodiment, the first download address is associated with a data volume of the first data packet. The first response message also includes a data amount of the first data packet.

In one possible implementation, the first request message further includes: and any one or more of a system version number of a software system adopted by the terminal equipment and a model number of the terminal equipment. The apparatus further comprises a processor configured to determine whether the terminal device supports the first system characteristic according to the system version number and/or the model of the terminal device. The transceiver is further configured to send a second response message to the terminal device if the terminal device does not support the first system characteristic, where the second response message is used to indicate a reason why the terminal device does not support the first system characteristic.

In a possible implementation, the first response message further includes a second download path for providing a download of a characteristic dependency, the characteristic dependency being indicative of a dependency between at least two system characteristics, the first system characteristic being one of the at least two system characteristics.

In a seventh aspect, a computer readable storage medium is provided for storing instructions/executable code which, when executed by a processor of an electronic device, cause the electronic device to implement the method of any one of the first or second aspects.

In an eighth aspect, a chip system is provided, the chip system comprising a processor for implementing the method of any of the first or second aspects.

In a ninth aspect, there is provided a computer program product comprising instructions/code which, when run on an electronic device, implements the method of any one of the first or second aspects.

Drawings

The drawings that accompany the detailed description can be briefly described as follows.

Fig. 1 is a schematic diagram of a hardware structure of an exemplary mobile phone according to an embodiment of the present application.

Fig. 2 is a schematic structural diagram of a software system adopted by an exemplary mobile phone according to an embodiment of the present application.

Fig. 3 is a schematic diagram of a system frame to which an embodiment of the present application is applicable.

Fig. 4 is a flowchart of a method for enhancing system characteristics of a terminal device according to an embodiment of the present application.

Fig. 5 is a flowchart of another method for enhancing system characteristics of a terminal device according to an embodiment of the present application.

Fig. 6a is a schematic diagram of an exemplary feature management interface displayed by a terminal device according to an embodiment of the present application.

Fig. 6b is a schematic diagram of an exemplary request management interface displayed by a terminal device according to an embodiment of the present application.

Fig. 6c is a schematic diagram of an exemplary download confirmation interface displayed by the terminal device according to an embodiment of the present application.

Fig. 6d is a schematic diagram of an exemplary status display interface displayed by the terminal device according to an embodiment of the present application.

FIG. 7 is a diagram illustrating exemplary dependencies between multiple system characteristics in an embodiment of the application.

Fig. 8 is a schematic structural diagram of a terminal device according to an embodiment of the present application.

Fig. 9 is a schematic structural diagram of another server according to an embodiment of the present application.

Detailed Description

In the embodiment of the application, the terminal equipment comprises, but is not limited to, a tablet personal computer, a smart phone, a smart sound box and a smart refrigerator. For example, terminal devices and automation control devices that are independently developed for each specific business scenario may also be included.

In terms of hardware structure, at least the memory and the processor may be included in the terminal device.

Taking the example that the terminal device is a mobile phone, as shown in fig. 1, the mobile phone 100 may include a processor 110 and an internal memory 120. Also included may be a display 130, antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, audio module 170, speaker 170A, receiver 170B, microphone 170C, earphone interface 170D, sensor module 180, keys 190, motor 191, pointing device 192, camera 193, and subscriber identity module (subscriber identification module, SIM) card interface 194, among others. Among them, the sensor module 180 may include a gyro sensor 180A, an acceleration sensor 180B, a proximity light sensor 180C, a fingerprint sensor 180D, a touch sensor 180E, and the like.

The internal memory 120 may store a software system adopted by the mobile phone 100 and an application program deployed on the software system, and may also store various data created during the use of the mobile phone 100. In addition, the internal memory 120 may include high-speed random access memory and nonvolatile memory, such as disk memory, flash memory, and universal flash memory (universal flash storage, UFS), among others.

The processor 110 implements various functions and data processing procedures of the handset 100 by executing executable program code/instructions stored in the internal memory 120.

Accordingly, in an embodiment of the present application, there is further provided a computer readable storage medium storing executable codes/instructions, which when executed by a processor of a terminal device, cause the terminal device to implement the method performed by the terminal device provided in any one of the embodiments of the present application. The computer readable storage medium may be an internal memory of the terminal device, or may be an external memory connected to the terminal device through an external memory interface.

The embodiment of the application also provides a terminal device, which comprises a memory and a processor, wherein executable codes/instructions are stored in the memory, and when the processor executes the executable codes/instructions, the terminal device realizes the method executed by the terminal device provided by any embodiment of the application.

The embodiment of the application also provides a chip system which comprises a processor and is used for realizing the functions of the terminal equipment provided in any embodiment of the application. For example, corresponding data and/or information is received or processed. In one possible design, the chip system may be composed of chips, or may include chips and other discrete devices.

There is also provided in an embodiment of the present application a computer program product comprising instructions/code which, when run on a terminal device, implements the method performed by the terminal device provided in any of the embodiments of the present application.

As for the software architecture, a software system deployed in the terminal device may employ a layered architecture, an event-driven architecture, a micro-core architecture, or a cloud architecture. In the embodiment of the application, taking an Android (Android) system with a layered architecture as an example of a software system deployed in terminal equipment, a software structure of the terminal equipment is illustrated.

Fig. 2 is a schematic diagram of a software system used in the mobile phone 100. As shown in fig. 2, the Android system can be generally divided into four layers, namely an application program layer, an application program framework layer, a system library and an Android runtime (Android run) kernel layer from top to bottom, each layer has a clear role and division, and the layers are communicated through software interfaces.

The application layer includes a series of applications deployed on the handset 100. Exemplary application layers include, but are not limited to, desktop Launcher (desktop), settings module, calendar module, camera module, talk module, and text message module.

The application framework layer may provide an application programming interface (application programming interface, API) and programming framework for applications in the application layer, and may also include some predefined functional modules/services. Exemplary application framework layers include, but are not limited to, window manager (Window manager), activity manager (Activity manager), package manager (Package manager), resource manager (Resource manager), and Power manager (Power manager).

The activity manager is used for managing the life cycle of the application programs and realizing the navigation rollback function of each application program. For example, an Activity manager may be responsible for the creation of an Activity (Activity) process and the maintenance of the lifecycle of an already created Activity process.

Wherein the window manager is used for managing window programs. It will be appreciated that the graphical user interface of an application is typically composed of one or more activities, which in turn are composed of one or more views; the window manager may add views included in the graphical user interface to be displayed to the display 130 or may be used to remove views from the graphical user interface displayed on the display 130.

The packet manager may manage data packets corresponding to each application program, for example, for decompressing, verifying, installing, and upgrading each data packet.

In the embodiment of the present application, a new functional module may be embedded in the packet manager, and/or a functional module independent of the packet manager may be embedded in the application framework layer, so that the mobile phone 100 implements the method executed by the terminal device provided in any one of the embodiments of the present application.

Wherein the resource manager is used to provide access to various non-code resources to the application.

The power manager is a core service of power management of the Android system and is mainly used for executing computing tasks related to power management in the Android system. And the downward decision controls the underlying system of the Android system to turn on or off a display screen, start or stop a distance sensor, and approach hardware equipment such as a light sensor. And providing corresponding operation interfaces upwards, so that each application program of the application program layer can call the operation interfaces, and the specific business purpose is realized.

In the embodiment of the application, the application framework layer may further include a functional module for supporting the terminal device to have one or more system characteristics (or referred to as system functions and system capabilities). As described above, the function modules of the application framework layer may be managed by the packet manager, such as downloading, installing, and deleting the data packets including the corresponding function modules.

The system characteristics of the terminal device refer to characteristics/functions/capabilities of the terminal device under the support of the function modules located in the application framework layer. The system characteristics of the terminal device are not dependent on the application of the application layer.

It will be appreciated that the functional module/functional enhancement module, which is used to support the terminal device as having certain system characteristics, is a file/instruction set formed by compiling and packaging computer program code and capable of being executed by a computer.

The system libraries and An Zhuoyun lines below the application framework layer, the kernel layer, etc. may be referred to as an underlying system that includes an underlying display system for providing display services, which may include, but is not limited to, surface managers (surface manager) at the system libraries and display drivers at the kernel layer.

The runtime is responsible for the scheduling and management of the entire software system, including the core libraries and virtual machines. The computer programs of the application layer and the application framework layer run in virtual machines. More specifically, the virtual machine may execute java files of the application layer and the application framework layer as binary files.

The system library may also include a plurality of functional modules other than the surface manager. Such as status monitoring services, media Libraries, three-dimensional graphics engines (e.g., openGL for Embedded Systems), two-dimensional graphics engines, and the like.

Wherein the surface manager may provide a fusion of two-dimensional graphics and three-dimensional graphics for each application.

The state monitoring service may receive data reported by each driver at the kernel layer.

Wherein the media library may support playback and acquisition of images/audio/video in a variety of commonly used formats.

The three-dimensional graphic engine is used for drawing, rendering and synthesizing the three-dimensional images.

The two-dimensional graphic engine is used for drawing and rendering the two-dimensional image.

The kernel layer is a layer between hardware and software, and includes a plurality of hardware drivers. Illustratively, the kernel layer may include a display driver, a camera driver, an audio driver, and a touch driver. Each driver can collect information collected by corresponding hardware and report corresponding monitoring data to a state monitoring service or other functional modules in a system library.

For a terminal device, the user may not have a need for use of one or more of the numerous system features that the terminal device may have. If the software system adopted by the terminal equipment comprises a functional module for supporting the system characteristics that the user does not have the use requirement, the functional module can waste various resources such as the memory of the body of the terminal equipment, the running memory, the computing resources and the like, and even the performance of the terminal equipment can be influenced by occupying various resources of the terminal equipment excessively.

Illustratively, a tablet computer may have one system characteristic: when the leather sheath sleeved on the tablet personal computer is covered on the display screen of the tablet personal computer, the tablet personal computer automatically locks the display screen; when the leather sheath is opened and is not covered on the display screen of the tablet personal computer any more, the tablet personal computer automatically unlocks the display screen. The item of system characteristics that a tablet computer has is often referred to as a "holster mode," i.e., a "holster mode" is often used as an indicator for indicating the item of system characteristics. It will be appreciated that the software system layer employed by the tablet computer includes functional modules for supporting the system features indicated by the tablet computer having "holster mode".

Functional modules for supporting the system features indicated by the "holster mode" of a tablet computer are typically built into the system framework layer of the software system employed by the tablet computer. Even if the user does not have a use requirement for the system characteristic indicated by the "holster mode" (for example, the user is not sleeving the holster on the tablet computer), the functional module for supporting the system characteristic indicated by the "holster mode" is still loaded into the memory of the tablet computer when the tablet computer is used by the user, so that the waste is caused to the body memory and the running memory of the tablet computer.

In the embodiment of the application, the system characteristics of the terminal equipment are enhanced according to the requirements of the user on the use of various system characteristics which the terminal equipment can have. Accordingly, the number of functional modules and the total data amount in the software system adopted by the terminal equipment can be reduced, so that the occupation of the software system to various resources of the terminal equipment is reduced.

It can be appreciated that by reducing the occupation of various resources of the terminal device by the software system, it is beneficial to reduce the minimum specification of the software system adopted by various types or models of terminal devices, and to further improve the performance of the terminal device.

It can be understood that the system characteristics of the terminal device can be enhanced according to the use requirements of the user on the system characteristics of the terminal device, and the user experience can be further improved.

It can be understood that the system characteristics indicated by the "holster mode" above are only used to assist in describing the technical solution of the embodiments of the present application. In practice, the system characteristics indicated by the "holster mode" should not be understood as the system characteristics that the terminal device must have or should have. The terminal device may also have, for example, system characteristics indicated by the identifiers of "glove mode" and "hover button", respectively.

The system framework of an embodiment of the present application will be described first with reference to fig. 3. As shown in fig. 3, a worker may issue a packet for supporting the terminal device 10 to have various system characteristics to the packet management server 30 through the server 20 or other devices. Wherein the data packet at least comprises a functional module for supporting the terminal device 10 to have corresponding system characteristics. The worker may also maintain in the server 20 package information for the data packages that have been published to the package administration server 30. The packet information of each data packet maintained in the server 20 may be applied to the information interaction process between the terminal device 10 and the server 20, and finally, the terminal device 10 may download the corresponding data packet from the packet management server 30.

It should be noted that, in the system framework shown in fig. 3, the server 20 and the packet management server 30 may be separate computing devices, or may be integrated into the same computing device.

To improve the security of the terminal device 10, to avoid that the data packets downloaded by the terminal device 10 from the packet management server 30 are maliciously altered by an intruder, and to avoid that the terminal device 10 loads data packets that have been maliciously altered by an intruder, the packet management server 30 and the terminal device 10 may also be connected to an authentication server 40 of a certificate authority (CA, certificate authority). The CA authentication server 40 may assign a digital certificate to the packet management server 30 so that the terminal device 10 performs integrity and security check on the data packet downloaded by the packet management server 30 according to the digital certificate. The terminal device 10 performs subsequent service processing on the data packet downloaded by the terminal device after the data packet downloaded by the terminal device passes the security and integrity check.

The technical solution of the embodiment of the present application is described in more detail below with further reference to the system framework shown in fig. 4.

In step 41, the terminal device sends a first request message to the server in response to a request operation of a first system characteristic that the terminal device does not have by the user.

Wherein the first request message includes at least a first identification of a first system characteristic.

In step 43, the server may determine a first download path associated with the first identification.

The first download path is used for providing downloading of the first data packet.

In step 45, the server sends a first response message to the terminal device.

Wherein the first response message includes a first download path.

In step 47, the terminal device downloads the first data packet from the packet management server according to the first download path.

The first data packet comprises a function enhancement module and a description file, wherein the function enhancement module comprises at least one interface class, and the description file describes the identification of the at least one interface class.

In step 49, the terminal device invokes the functionality enhancement module based on the identity of the at least one interface class.

After the terminal device invokes at least one interface class, the terminal device may have a first system characteristic.

First, in step 501, the terminal device displays a characteristics management interface to a user.

Wherein the characteristics management interface indicates at least one or more system characteristics not possessed by the terminal device, and the user can execute a request operation for the system characteristics not possessed by the terminal device in the characteristics management interface.

In a more specific example, the characteristics management interface may include an identification of one or more system characteristics, and may further include a pattern or a combination of patterns for indicating whether the terminal device already has the corresponding system characteristics. FIG. 6a is a schematic diagram of an exemplary property management interface. As shown in fig. 6a, words such as "leather sheath mode", "X1", "X2", "X3", "X4" in the characteristic management interface are identifiers for indicating corresponding system characteristics. The combination of patterns in the characteristics management interface to the right of the respective identifications may indicate whether the terminal device already has the corresponding system characteristics. Wherein, in the same pattern combination, when the circular pattern is positioned at the left side of the oblong pattern, the terminal device can be indicated not to have the system characteristic indicated by the mark positioned at the left side of the pattern combination; when the circular pattern is located on the right side of the oblong pattern, it may be indicated that the terminal device already has the system characteristics indicated by the identification located on the left side of the pattern combination.

It can be understood that the "holster mode", "X1", "X2", "X3", and "X4" are only used to assist in describing the technical solutions of the embodiments of the present application, and in an actual service scenario, the identification of various system characteristics may be used to replace the same.

Accordingly, the feature management interface shown in fig. 6a may indicate that the terminal device displaying the feature management interface already has the system features indicated by "X1", "X2" and "X4", respectively, and the terminal device may also have the system features indicated by "holster mode" and "X3", respectively, but the terminal device does not have the system features indicated by "holster mode" and "X3", respectively.

Next, in step 502, the terminal device receives a request operation of the user for the first system feature through the feature management interface.

Wherein the first system characteristic is a system characteristic not possessed by the terminal device. For example, in the feature management interface shown in fig. 6a, the user may drag a circular pattern included in a pattern combination on the right side of a first mark (e.g., a "holster mode") to the right side of an oblong pattern included in the pattern combination, to form a request operation for the system feature indicated by the first mark.

In one possible embodiment, for a system feature that the terminal device does not have, there may already be a functional module in the terminal device for supporting the terminal device to have the system feature, but the functional module is not loaded into the memory of the terminal device, resulting in the terminal device not having the system feature. At this time, if the user drags the circular pattern included in the corresponding pattern combination to the right side of the oblong pattern included in the pattern combination in the feature management interface, the terminal device can be triggered to load the function module into the memory of the terminal device and call the function module, so that the terminal device has the system feature.

In one possible implementation manner, for a system characteristic that the terminal device does not have, the user may trigger (e.g., click/touch) an area where a first identifier for indicating the system characteristic is located in the characteristic management interface, or trigger an area where a pattern combination on the right side of the first identifier is located, so that the terminal device displays a request management interface for the system characteristic, and then performs a request operation for the system characteristic in the request management interface.

For example, the user may trigger the region where the "holster mode" word is located in the feature management interface shown in fig. 6a, or trigger the region where the pattern combination on the right side of the "holster mode" word is located, so that the terminal device displays the request management interface shown in fig. 6 b. Then, in the request management interface shown in fig. 6b, the user drags the circular pattern included in the pattern combination on the right side of the "holster mode" word to the right side of the oblong pattern included in the pattern combination, so as to form a request operation on the system characteristic indicated by the "holster mode".

In step 503, the terminal device sends a first request message to the server in response to a request operation of the user for the first system characteristic.

As previously described, at least a first identification of a first system characteristic is included in the first request message.

In one possible implementation, the first request message may further include: any one or more of a system version number of a software system employed by the terminal device, a model number of the terminal device, and a preset version number associated with the first identification. Any one or more of a system version number of the software system and a model number of the terminal device may be used to determine whether the terminal device supports the first system characteristic.

It will be appreciated that for different models of terminal devices, there may be differences in hardware configuration or other reasons, resulting in different models of terminal devices requiring different versions of software systems to be employed. Moreover, for terminal devices employing different versions of the software system, it may be necessary to use different functional modules to support the same system characteristics. The staff may issue a plurality of different versions of data packages to the package management server for one system characteristic, each version of data package may be adapted to one or more versions of the software system, i.e. each version of data package only has the system characteristic for supporting terminal devices employing the particular version of the software system.

In a more specific example, for each version of software system, an association relationship between an identifier corresponding to each system characteristic and a version number of each data packet may be set in the software system of the current version. Illustratively, among a plurality of data packets of the software system with the adaptation Version number of version_3, there are a plurality of target data packets, and each target data packet includes a functional module for supporting the terminal device to have the system characteristic indicated by "holster mode"; however, each target packet includes a different functional module, and the version number of each target packet is different. At this time, the minimum Version number of the Version numbers corresponding to the target data packets respectively can be determined as the preset Version number, and the association relationship between the leather sheath mode and the preset Version number is set in the software system with Version number of version_3.

Correspondingly, the terminal device may determine a preset version number associated with the first identifier, and carry the preset version number in the first request message. Therefore, the situation that the subsequently downloaded data packet cannot adapt to the software system adopted by the terminal equipment due to too low version is avoided, and the terminal equipment is ensured to acquire the data packet for supporting the first system characteristic indicated by the first identifier.

In step 504, the server may determine whether the terminal device supports the first system characteristic.

In a possible embodiment, the server may also maintain device information of the respective terminal devices allowing downloading of the data packets from the packet management server. The device information includes, but is not limited to, the model number of the terminal device and the minimum system version number of the software system that the terminal device of each model can employ.

It will be appreciated that the same model of terminal equipment typically has the same hardware configuration, but that different models of terminal equipment may have differences in hardware configuration or other reasons, resulting in different versions of the software system being required for different models of terminal equipment. After the model of the terminal device is determined, the hardware configuration of the terminal device can be determined, and the system version number of the software system that the terminal device can employ can also be determined.

By way of example, device information of the terminal device that allows downloading of the data packet from the packet management server may be maintained by the following table 1.

TABLE 1

Model number	System version number
		Mate10	Version_2
Mate20	Version_2
		Mate30	Version_3
P9	Version_1
		P30Pro	Version_3

In the above table 1, the model numbers and system version numbers of the terminal devices located in the same row may be regarded as one piece of device information defining the minimum system version number of the software system that the terminal devices of the corresponding model can employ. For example, in table 1, the model "Mate10" and Version number "version_2" located in the same row define that the minimum system Version number of each software system that can be used by the terminal device having the model "Mate10" is version_2; in other words, assuming that the system Version number version_3 is greater than version_2 and version_2 is greater than version_1, it is explained that the terminal device of the model "Mate10" cannot install the software system of the system Version number version_1.

Accordingly, in the case that the first request message includes the system version number of the software system adopted by the terminal device and the model number of the terminal device, the server may query whether the device information including the model number of the terminal device and the version number of the software system adopted by the terminal device is included in the pieces of device information included in the table 1. If not, the server may determine that the terminal device may not have the first system characteristic. The server may then send a second response message to the terminal device, the reason why the terminal device indicated by the second response message may not have the first system characteristic may be that the terminal device is not authorized/allowed to download the data packet from the packet management server.

In a possible implementation manner, the server may also maintain an association relationship between the terminal devices of each model and the identifiers of each system characteristic that the terminal devices may have. By way of example, the association between the identities of the various models of terminal devices and the various system characteristics that they may have may be maintained by table 2 below.

TABLE 2

Model number	Identification mark
		Mate10	Leather sheath mode, X3, X4
Mate20	Leather sheath mode, X2, X3, X4
		Mate30	Leather sheath mode, X1, X2, X3, X4
P9	Leather sheath mode, X1, X2
		P30Pro	X1、X2、X3、X4

Accordingly, in the case that the first request message further includes the model of the terminal device, the server may determine whether the first identifier included in the first request message and the model of the terminal device are associated with each other according to an association relationship between the terminal devices of the respective models and identifiers of various system characteristics that the terminal devices may have. If not, the server may determine that the terminal device may not have the first system characteristic. Then, the server may send a second response message to the terminal device, where the reason that the terminal device indicated by the second response message may not have the first system characteristic may be that the hardware configuration of the terminal device may not support the terminal device to have the first system characteristic.

As described above, the server can maintain packet information of individual data packets that have been issued to the packet management server.

In one possible implementation, the packet information of the data packet includes, but is not limited to, a download address corresponding to the data packet in the packet management server, a version number of the data packet, a data amount of the data packet, and an identification of a system characteristic that the data packet may support for the terminal device.

By way of example, packet information of individual data packets that have been issued to the packet management server may be maintained by the following table 3.

TABLE 3 Table 3

Identification mark	Version number	Download address	Data volume
				Leather sheath mode	V1	URL_1	Data_1
Leather sheath mode	V2	URL_2	Data_2
				Leather sheath mode	V3	URL_3	Data_3
X1	/	URL_4	Data_4
				X2	/	URL_5	Data_5
X3	/	URL_6	Data_6
				X4	/	URL_7	Data_7

Referring to table 3 above, when a worker develops a Data packet for a system characteristic of a terminal device, the Data packet may be issued to the packet management server, and then the identifier (e.g., holster mode) for indicating the system characteristic, the version number (e.g., V1) of the Data packet, the download address (e.g., url_1) of the Data packet in the packet management server, the Data amount (e.g., data_1) of the Data packet may be correspondingly stored in the "identifier" field, "version" field, "download address" field, "and" Data amount "field shown in table 1 above. Also, for packet information of the same packet, the identification, version number, download address, and data amount for indicating the system characteristics are contained in the same row in table 1. Accordingly, any two field values among the plurality of field values located in the same row in table 1 can be understood as being interrelated therebetween.

It should be noted that "/" in table 3 indicates that the corresponding packet does not have a version number. The field values under the respective fields in the above table 3 are merely examples and do not represent actual values, and the respective field values in the above table 3 may be replaced with the actual values in an actual business scenario.

In one possible implementation, if the packet information of each data packet maintained by the server does not include the first identifier carried in the first request message, the server may determine that the terminal device may not have the first system characteristic. The terminal device may then send a second response message to the terminal device, where the reason why the second response message indicates that the terminal device does not support the first system characteristic may be that there is no data packet in the packet management server for supporting the terminal device to have the first system characteristic.

Correspondingly, the terminal device may also provide the user with the second response message it receives, so that the user knows the reason why the terminal device does not support the first system characteristic. Thus, the method is beneficial to the targeted processing of the terminal equipment by the user so as to solve the problem that the terminal equipment does not support the first system characteristic. For example, the second response message indicates that the first system characteristic and the version of the software system adopted by the terminal device have compatibility problems, so that the user can overcome the problem that the terminal device does not support the first system characteristic by updating the software system adopted by the terminal device.

In the embodiment of the present application, if the server does not determine that the terminal device does not support the first system characteristic, i.e., in the case that the terminal device supports the first system characteristic, the server may perform the following step 505.

Specifically, in step 505, the server may determine a first download path of the first data packet and a data amount of the first data packet.

In a possible implementation manner, in the case that the first request message includes the preset version number, the server may first determine at least one candidate download path associated with the first identifier according to each packet information maintained by the server, and then determine the first download path of the first data packet from each candidate download path. The first downloading path is correlated with the current version number of the first data packet, and the current version number of the first data packet is not smaller than the preset version number.

For example, still referring to table 3 above, if the first request message includes a first identification "holster mode" and a preset version number "V2", the server may determine candidate download addresses "url_1", "url_2", and "url_3" associated with "holster mode" from table 3 above. Further looking up the above table 1, it can be seen that the version numbers associated with "url_1", "url_2" and "url_3" are "V1", "V2" and "V3", respectively. If version number V3 is greater than V2, V2 is greater than V1; then the server may determine url_2 or url_3 as the first download path.

Correspondingly, the server can determine the data volume of the first data packet from the packet information containing the first download path according to the determined first download path of the first data packet.

Next, in step 506, the server sends a first response message to the terminal device.

As described above, the first response message may include the first download path of the first data packet, and may further include the data amount of the first data packet and the second download path. The second download path is for providing a download of a characteristic dependency, the characteristic dependency being for indicating a dependency between at least two system characteristics. More specifically, the second download path may indicate a resource location of the characteristic dependency in the package administration server.

Next, in step 507, the terminal device downloads the characteristic dependency relationship from the package management server according to the second download path.

Next, in step 508, the terminal device determines, according to the characteristic dependency relationship and the first identifier, whether at least one dependent characteristic on which the first system characteristic depends includes a second system characteristic that the terminal device does not have.

It will be appreciated that the function enhancement module for supporting the terminal device having the first system characteristic may need to cooperate with, e.g. be invoked by, at least one other function module in order to provide the terminal device with the first system characteristic. Wherein at least one other functional module is a functional module located in a system framework layer of a software system employed by the terminal device. In other words, there may be a dependency between functional modules for supporting that the terminal device has various system characteristics, i.e. there may be a dependency between various system characteristics that the terminal device may have. That is, for the first system characteristic that the terminal device does not have, the terminal device needs to have the first system characteristic in a case where it already has at least one relied characteristic on which the first system characteristic depends.

In the case that the at least one dependent characteristic includes a second system characteristic that the terminal device does not have, there may already exist a functional module for supporting the terminal device to have the second system characteristic in a system frame layer of the terminal device, and the functional module corresponding to the second system characteristic may be loaded into a memory of the terminal device and called.

In case the at least one dependent characteristic comprises a second system characteristic not possessed by the terminal device, there may not be a functional module in the system framework layer of the terminal device for supporting the terminal device to possess the second system characteristic. At this time, the terminal device may send a second request message to the server, where the second request message includes the second identifier of the second system characteristic, and finally the terminal device is enabled to have the second system characteristic.

Taking the system characteristics indicated by the labels of "holster mode", "X1", "X2", "X3", etc. as an example, the dependency relationship shown in fig. 7 is satisfied. In the dependency relationship between the various system characteristics as shown in fig. 7, the system characteristic indicated by the "holster mode" depends on the system characteristic indicated by the "X1", the system characteristic indicated by the "X1" depends on the system characteristics indicated by the "X2" and the "X3", respectively, and the system characteristic indicated by the "X3" depends on the system characteristic indicated by the "X4". Assuming that the first system characteristic is the system characteristic indicated by the "holster mode", the terminal device may query the dependency relationship between the various system characteristics as shown in fig. 7 according to the "holster mode", determine the system characteristic indicated by the dependency characteristic "X1" on which the first system characteristic depends, then determine whether the terminal device already has the system characteristic indicated by "X1", and if the terminal device does not have the system characteristic indicated by "X1", the terminal device may send a second request message including "X1" to the server.

In summary, for each of the dependent characteristics on which the first system characteristic depends, the terminal device may perform the following step 509 in case the terminal device already has each of the dependent characteristics.

Specifically, in step 509, the terminal device displays the data amount of the first data packet to the user.

In one possible implementation manner, the terminal device may display the data amount of the first data packet to the user through the corresponding download confirmation interface, so that the user performs a corresponding operation in the download confirmation interface displayed by the terminal device, to confirm whether the terminal device can continue to download the first data packet. For example, the running memory load of the terminal device is higher, and the data volume of the first data packet is relatively larger, so that the user can execute corresponding operation in the download confirmation interface to confirm that the terminal device does not continue to download the first data packet; for another example, the load of the running memory and the body memory of the terminal device is smaller, the data volume of the first data packet is also relatively smaller, even if the terminal device downloads the first data packet and the first system characteristic of the terminal device is enhanced by utilizing the function enhancing module included in the first data packet, the performance of the terminal device is not affected by too much occupying various resources such as the running memory and the body memory of the terminal device, and the user can execute corresponding operation in the download confirmation interface to confirm that the terminal device can continue to download the first data packet.

For example, when the user drags the circular pattern included in the pattern combination to the right side of the oblong pattern included in the pattern combination in the request management interface shown in fig. 6b, a request operation for the "holster mode" is implemented, so that after the terminal device receives the first response message from the server, the interface displayed by the terminal device may be changed from the request management interface shown in fig. 6b to the download confirmation interface shown in fig. 6 c. Wherein "(size: 25K)" in the download confirmation interface, as shown in fig. 6c, indicates that the data amount of the first data packet for supporting the terminal device to have the first system characteristic is 25K. The user can trigger the area where the "cancel" word is located in the download confirmation interface as shown in fig. 6c, and confirm that the terminal device does not continue downloading the first data packet any more; the user may trigger the download confirmation interface shown in fig. 6c to download the area where the "continue" word is located, and the confirmation terminal device may continue to download the first data packet.

In summary, in case the terminal device confirms that the first data packet can continue to be downloaded, the following step 510 may be performed.

In step 510, a first data packet is downloaded from a packet management server according to a first download path.

In the embodiment of the application, the first data packet comprises a function enhancement module and a description file. Wherein, at least one interface class is encapsulated in the function enhancement module, and the second identification of the at least one interface class is described in the description file. An interface class may be an abstract class or an entity class for implementing an interface.

In step 511, the terminal device determines whether the identifier of the at least one interface class includes an identifier associated with the first identifier.

It will be appreciated that, if the terminal device is to be provided with a first system characteristic, it may be necessary for the caller to call at least one interface class, wherein the caller refers to a functional module for supporting the terminal device with at least one relied characteristic, the first system characteristic being dependent on the at least one relied characteristic. For at least one interface class that needs to be called by the calling party, the association relationship between the identifier of the at least one interface class and the first identifier of the first system characteristic may be stored in the terminal device in advance.

Still referring to fig. 7, assume that the first system characteristic is a system characteristic indicated by "holster mode", which is dependent on a system characteristic indicated by "X1". The caller then comprises a functional module for supporting the terminal device to have the system characteristics indicated by "X1".

In other words, if the terminal device is required to have the first system characteristic indicated by "holster mode", the functional module for supporting the terminal device to have the system characteristic indicated by "X1" needs to be called as a calling party to at least one interface class. For at least one interface class that the caller needs to call, it should be integrated in a function enhancement module for supporting the terminal device to have the first system characteristic. For any interface class that needs to be called by the calling party, if the terminal device queries that the description file included in the first data packet does not describe the identifier of the interface class, it is indicated that the interface class is not integrated in the function enhancement module included in the first data packet, and the function enhancement module may not support that the terminal device has the first system characteristic.

Correspondingly, in the case that the identifier associated with the first identifier is not included in the identifier of the at least one interface class, that is, in the case that the first data packet cannot support the terminal device to have the first system characteristic, the terminal device may delete the first data packet downloaded by the terminal device and perform a corresponding alarm indication. Conversely, in case the identification associated with the first identification is included in the identification of the at least one interface class, the terminal device may further perform the following step 512.

In step 512, the terminal device loads the function enhancement module into the memory of the terminal device, and triggers the caller to call the function enhancement module loaded into the memory.

Still taking the Android system as an example of the terminal device, the functional modules located in the system framework layer of the Android system can be generally written based on the JAVA language. The technical scheme is not limited to the Android system, can be used for other operating systems, and can correspondingly write the functional modules by adopting other programming languages.

First, a function enhancement module for supporting a terminal device to have a certain system characteristic may be written in JAVA language, for example, source codes respectively corresponding to one or more classes included in the function enhancement module are written. Wherein, the one or more classes included in the function enhancement module may include at least one class for implementing an interface. The class used for realizing the interface can be an abstract class or an entity class, and the class used for realizing the interface is described as an interface class in the embodiment of the application.

And compiling source codes corresponding to the one or more classes respectively to obtain files in the ". Class" format corresponding to the one or more classes respectively.

Then, the files in the ". Class" format are further packaged to form a function enhancement module for supporting the terminal device to have a certain system characteristic, wherein the function enhancement module can be a file in the ". Jar" format, and can be a file in the ". Lib" or other formats.

And then constructing a corresponding description file aiming at the function enhancement module, and generating a data packet containing the function enhancement module and the description file. More specifically, the identification of at least one interface class included in the function enhancement module may be utilized to construct a description file for describing the identification of at least one interface class.

Further, the data packet is issued to a packet management server, and packet information of the data packet is maintained in the server.

Correspondingly, after the terminal equipment downloads the data packet from the packet management server, the terminal equipment can load the function enhancement module in the data packet into the memory of the terminal equipment through the JAVA class loader.

As described above, after the function enhancing module for supporting the terminal device having the first system characteristic is loaded into the memory, it may be further required to perform corresponding linking, initialization processing, and other related processing for each class included in the function enhancing module loaded into the memory, so that the terminal device has the first system characteristic.

In a more specific example, the terminal device may send a corresponding prompt message to the caller, thereby triggering the caller to call the interface class included in the function enhancement module already loaded into the memory.

In summary, by the methods shown in the foregoing steps 501 to 512, the system characteristics of the terminal device can be enhanced as required according to the use requirements of the user on the various system characteristics that the terminal device may have.

Based on the foregoing embodiments, the terminal device may further display a corresponding status prompt interface, through which whether the terminal device already has the first system characteristic is displayed to the user. Illustratively, the first system characteristic is a system characteristic indicated by "holster mode", and the terminal device may display a status display interface as shown in fig. 6 d.

On the basis of the foregoing embodiments, in the case where there is no need for use of a certain system characteristic already possessed by the terminal device by the user, in order to avoid that the function enhancement module for supporting the terminal device having the certain system characteristic additionally occupies the running memory of the terminal device, the terminal device may further delete the function enhancement module for supporting the terminal device having the certain system characteristic from the memory in response to the release operation of the user on the certain system characteristic.

For example, the user may form a release operation of the system characteristic indicated by "X1" by dragging a circular pattern included in a pattern combination on the right side of the "X1" character to the left side of an oblong pattern included in the pattern combination in the characteristic management interface shown in fig. 6 a. So that the memory of the terminal device is no longer loaded with the function enhancing module for supporting the terminal device to have the system characteristics indicated by "X1".

It will be appreciated that after the function enhancing module for supporting the terminal device to have a certain system characteristic is released, the data packet including the function enhancing module still occupies the body memory of the terminal device, i.e. occupies the storage space of the non-volatile memory of the terminal device. Therefore, in order to save the body memory of the terminal device, the terminal device may delete the data packet to which the function enhancing module that is not loaded into the memory belongs from the nonvolatile memory of the terminal device.

In a more specific example, after the function enhancement module for supporting the terminal device to have a certain system characteristic is released, that is, after the function enhancement module is deleted from its memory by the terminal device, the terminal device may delete the data packet to which the function enhancement module belongs from the nonvolatile memory of the terminal device in response to a deletion operation of the system characteristic by the user.

In a more specific example, after the function enhancing module for supporting the terminal device to have a certain system characteristic is released, that is, after the function enhancing module is deleted from its memory by the terminal device, the terminal device may record the accumulated time after the function enhancing module is released, and in the case that the accumulated time reaches a preset duration, delete the data packet to which the function enhancing module belongs from the nonvolatile memory of the terminal device.

In the embodiment of the application, the terminal equipment can adopt any one of a plurality of communication protocols such as file transfer protocol (FTP, file transfer protocol), hypertext transfer protocol (HTTP, hyper text transfer protocol) and the like to interact with the server.

Based on the same conception as the foregoing method embodiments, a communication device is also provided in the embodiments of the present application, where the communication device may be a terminal device, or may be a module or a chip system disposed in the terminal device, and is configured to implement a method performed by the terminal device provided in any one of the embodiments of the present application.

Based on the same conception as the foregoing method embodiments, a communication device is also provided in the embodiments of the present application, where the communication device may be a server, or may be a module or a chip system disposed in a terminal device, and is configured to implement a method performed by the server provided in any one of the embodiments of the present application.

The embodiment of the application also provides terminal equipment. As shown in fig. 8, the terminal device includes: a transceiver 801 for transmitting a first request message to a server in response to a request operation of a user for a first system characteristic that the terminal device does not have, wherein the first request message includes a first identification of the first system characteristic; a first response message is received from the server, wherein the first response message includes a first download path. A processor 802, configured to download a first data packet according to the first download path, where the first data packet includes a function enhancement module and a description file, the function enhancement module includes at least one interface class, and the description file describes an identification of the at least one interface class; and calling the function enhancement module according to the identification of the at least one interface class to enable the terminal equipment to have the first system characteristic.

In a possible implementation, the processing processor 802 is further configured to determine whether the identifier of the at least one interface class includes an identifier associated with the first identifier.

In a possible implementation, the processor 802 is further configured to display a feature management interface, where the feature management interface indicates the first system feature. The processor 802 is further configured to receive, through the feature management interface, a request operation of the user for the first system feature.

In a possible implementation manner, the processor 802 is specifically configured to load the function enhancement module into a memory of the terminal device and make a call to the at least one interface class.

In a possible implementation manner, the processor 802 is further configured to delete the function enhancement module from the memory of the terminal device in response to a release operation of the first system characteristic by a user.

In a possible implementation manner, the processor 802 is further configured to delete the first data packet from the nonvolatile memory of the terminal device in response to a deletion operation of the first system characteristic by a user.

In a possible implementation manner, the processor 802 is further configured to delete the first data packet from the nonvolatile memory of the terminal device if the accumulated time after deleting the function enhancing module from the memory of the terminal device reaches a preset duration.

In a possible implementation manner, the first response message further includes a data amount of the first data packet. The processor 802 is further configured to display the data amount of the first data packet to a user for confirmation by the user.

In a possible implementation, the transceiver 801 is further configured to receive a second response message from the server, where the second response message is used to indicate a reason that the terminal device does not support the first system characteristic. The processor 802 is further configured to provide a second response message to the user.

In a possible implementation, the first response message further includes a second download path for providing a download of a characteristic dependency, the characteristic dependency being indicative of a dependency between at least two system characteristics, the first system characteristic being one of the at least two system characteristics. The processor 802 is further configured to download the characteristic dependency relationship according to the second download path. The transceiver 801 is further configured to send a second request message to a server in case the at least one dependent characteristic comprises a second system characteristic not possessed by the terminal device, wherein the characteristic dependency indicates that the first system characteristic depends on the at least one dependent characteristic, and the second request message comprises a second identification of the second system characteristic.

The embodiment of the application also provides a server. As shown in fig. 9, the server includes: a transceiver 901 for receiving a first request message from a terminal device, wherein the first request message comprises a first identification of a first system characteristic. The transceiver 802 is further configured to send a first response message to the terminal device, where the first response message includes a first download path, the first download path being associated with the first identifier, the first download path being configured to provide downloading of a first data packet, the first data packet including a function enhancement module and a description file, the function enhancement module including at least one interface class, the description file describing an identifier of the at least one interface class, the function enhancement module being configured to enhance the first system characteristic of the terminal device.

In one possible implementation, the first request message further includes: and any one or more of a system version number of a software system adopted by the terminal equipment and a model number of the terminal equipment. The server may include: and a processor 902, configured to determine whether the terminal device supports the first system characteristic according to the system version number and/or the model of the terminal device. The transceiver 901 is further configured to send a second response message to the terminal device in case the terminal device does not support the first system characteristic, where the second response message is used to indicate a reason why the terminal device does not support the first system characteristic.

The embodiment of the application also provides a server which comprises a memory and a processor, wherein executable codes are stored in the memory, and when the processor executes the executable codes, the server can realize the method executed by the server provided by any embodiment of the application.

The embodiment of the application also provides a computer readable storage medium for storing instructions/executable code, which when executed by a processor of a server, enable the server to implement the method executed by the server provided in any one of the embodiments of the application.

The embodiment of the application also provides a chip system which comprises a plurality of processors and is used for realizing the functions of the server provided in any embodiment of the application. For example, corresponding data and/or information is received or processed. In one possible design, the chip system may be composed of chips, or may include chips and other discrete devices.

There is also provided in an embodiment of the present application a computer program product comprising instructions/code which, when run on a server, enables the method provided in any one embodiment of the present application to be performed by the server.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the embodiments of the present application.

It should be understood that, in various embodiments of the present application, the sequence numbers of the foregoing processes do not mean the order of execution, and the order of execution of the processes should be determined by the functions and internal logic of the processes, and should not constitute any limitation on the implementation process of the embodiments of the present application.

Finally, it should be noted that the above embodiments are only for illustrating the technical solution of the present application, and are not limited thereto. Although the application has been described in detail with reference to the foregoing embodiments, those skilled in the art will understand that modifications may be made to the technical solutions provided in the foregoing embodiments, or equivalents may be substituted for some of the technical features thereof, without departing from the spirit and scope of the technical solutions provided in the embodiments of the application.

Claims

1. A method of enhancing system characteristics of a terminal device, the method comprising:

responding to a request operation of a user for a first system characteristic which is not possessed by the terminal equipment, and sending a first request message to a server, wherein the first request message comprises a first identification of the first system characteristic;

receiving a first response message from a server, wherein the first response message includes a first download path;

downloading a first data packet according to the first downloading path, wherein the first data packet comprises a function enhancement module and a description file, the function enhancement module comprises at least one interface class, and the description file describes the identification of the at least one interface class;

according to the identification of the at least one interface class, the function enhancement module is called to enable the terminal equipment to have the first system characteristic;

wherein the first data packet has at least one version, and the first download path is associated with a current version number of the first data packet.

2. The method of claim 1, wherein the step of determining the position of the substrate comprises,

before the calling the function enhancing module according to the identification of the at least one interface class to enable the terminal device to have the first system characteristic, the method further comprises: determining whether an identification associated with the first identification is included in the identification of the at least one interface class.

3. A method according to claim 1 or 2, characterized in that,

before the first request message is sent to the server in response to the request operation of the user for the first system characteristic which the terminal device does not have, the method further comprises:

displaying a characteristic management interface, wherein the characteristic management interface indicates the first system characteristic;

and receiving a request operation of a user on the first system characteristic through the characteristic management interface.

4. The method according to any one of claim 1 to 2, wherein,

the calling the function enhancement module comprises the following steps: and loading the function enhancement module into the memory of the terminal equipment and calling the at least one interface class.

5. The method of claim 4, wherein the step of determining the position of the first electrode is performed,

after loading the function enhancement module into the memory of the terminal device and invoking the at least one interface class, the method further comprises: and deleting the function enhancement module from the memory of the terminal equipment in response to the release operation of the user on the first system characteristic.

6. The method of claim 5, wherein the step of determining the position of the probe is performed,

After deleting the function enhancement module from the memory of the terminal device in response to the user releasing operation of the first system characteristic, the method further includes: and deleting the first data packet from the nonvolatile memory of the terminal equipment in response to a deleting operation of the first system characteristic by a user.

7. The method of claim 5, wherein the step of determining the position of the probe is performed,

after deleting the function enhancement module from the memory of the terminal device in response to the user releasing operation of the first system characteristic, the method further includes: and deleting the first data packet from the nonvolatile memory of the terminal equipment under the condition that the accumulated time after deleting the function enhancement module from the memory of the terminal equipment reaches the preset duration.

8. The method according to any one of claims 1 to 2, wherein,

the first request message further includes: at least one of a system version number of a software system adopted by the terminal device, a model number of the terminal device and a preset version number associated with the first identifier, wherein the preset version number is not greater than a current version number of the first data packet.

9. The method according to any one of claims 1 to 2, wherein,

the first response message further includes: the data amount of the first data packet;

before said downloading of the first data packet according to said first download path, said method further comprises: and displaying the data quantity of the first data packet to a user so as to confirm the user.

10. The method according to any one of claims 1 to 2, wherein,

the method further comprises the steps of:

receiving a second response message from the server, wherein the second response message is used for indicating a reason that the terminal equipment does not support the first system characteristic;

and providing the second response message to the user.

11. The method according to any one of claim 1 to 2, wherein,

the first response message further includes a second download path for providing a download of a characteristic dependency, the characteristic dependency being indicative of a dependency between at least two system characteristics, the first system characteristic being one of the at least two system characteristics;

before said downloading of the first data packet according to said first download path, said method further comprises:

Downloading the characteristic dependency relationship according to the second downloading path;

in case the at least one depended feature comprises a second system feature not possessed by the terminal device, a second request message is sent to the server, wherein the feature dependency indicates that the first system feature depends on the at least one depended feature, the second request message comprising a second identification of the second system feature.

12. A method for enhancing system characteristics of a terminal device, the method comprising:

receiving a first request message from a terminal device, wherein the first request message comprises a first identification of a first system characteristic;

and sending a first response message to the terminal equipment, wherein the first response message comprises a first downloading path, the first downloading path is associated with the first identifier, the first downloading path is used for providing downloading of a first data packet, the first data packet comprises a function enhancement module and a description file, the function enhancement module comprises at least one interface class, and the description file describes the identifier of the at least one interface class.

13. The method of claim 12, wherein the step of determining the position of the probe is performed,

The first request message further includes: a preset version number associated with the first identification;

the first identifier is associated with at least one candidate download path, the at least one candidate download path including the first download path, the first download path being associated with a current version number of the first data packet, the current version number of the first data packet being not less than the preset version number.

14. The method according to claim 12 or 13, wherein,

the first download path is associated with a data volume of the first data packet;

the first response message also includes a data amount of the first data packet.

15. The method according to any one of claims 12 to 13, wherein,

the first request message further includes: at least one of a system version number of a software system adopted by the terminal equipment and a model number of the terminal equipment;

before the sending of the first response message to the terminal device, the method further comprises:

determining whether the terminal equipment supports the first system characteristic according to the system version number and/or the model of the terminal equipment;

and sending a second response message to the terminal equipment under the condition that the terminal equipment does not support the first system characteristic, wherein the second response message is used for indicating the reason that the terminal equipment does not support the first system characteristic.

16. The method according to any one of claims 12 to 13, wherein,

the first response message further includes a second download path for providing a download of a characteristic dependency, the characteristic dependency being indicative of a dependency between at least two system characteristics, the first system characteristic being one of the at least two system characteristics.

17. A communication device for implementing the method of any one of claims 1 to 11.

18. A communication device for implementing the method of any one of claims 12 to 16.

19. A terminal device, comprising:

a transceiver configured to send a first request message to a server in response to a request operation of a user for a first system characteristic that the terminal device does not have, wherein the first request message includes a first identification of the first system characteristic; receiving a first response message from a server, wherein the first response message includes a first download path;

a processor configured to download a first data packet according to the first download path, where the first data packet includes a function enhancement module and a description file, the function enhancement module includes at least one interface class, and the description file describes an identifier of the at least one interface class; according to the identification of the at least one interface class, the function enhancement module is called to enable the terminal equipment to have the first system characteristic;

20. The terminal device of claim 19, wherein the terminal device,

the processor is further configured to determine whether an identifier associated with the first identifier is included in the identifier of the at least one interface class.

21. Terminal device according to claim 19 or 20, characterized in that,

the processor is further configured to display a feature management interface, where the feature management interface indicates the first system feature; and receiving a request operation of a user on the first system characteristic through the characteristic management interface.

22. Terminal device according to any of the claims 19-20, characterized in that,

the processor is specifically configured to load the function enhancing module into a memory of the terminal device, and call the at least one interface class.

23. The terminal device of claim 22, wherein the terminal device,

and the processor is further used for responding to the releasing operation of the user on the first system characteristic and deleting the function enhancement module from the memory of the terminal equipment.

24. The terminal device of claim 23, wherein the terminal device,

the processor is further configured to delete the first data packet from the nonvolatile memory of the terminal device in response to a user deleting operation of the first system characteristic.

25. The terminal device of claim 23, wherein the terminal device,

the processor is further configured to delete the first data packet from the nonvolatile memory of the terminal device when the accumulated time after deleting the function enhancing module from the memory of the terminal device reaches a preset duration.

26. Terminal device according to any of the claims 19 to 20, characterized in that,

27. Terminal device according to any of the claims 19-20, characterized in that,

The processor is further configured to display the data amount of the first data packet to a user for confirmation by the user.

28. Terminal device according to any of the claims 19-20, characterized in that,

the transceiver is further configured to receive a second response message from the server, where the second response message is used to indicate a reason why the first system characteristic is not supported by the terminal device; and providing the second response message to the user.

29. Terminal device according to any of the claims 19-20, characterized in that,

the processor is further configured to download the characteristic dependency relationship according to the second download path; in case the at least one depended feature comprises a second system feature not possessed by the terminal device, a second request message is sent to the server, wherein the feature dependency indicates that the first system feature depends on the at least one depended feature, the second request message comprising a second identification of the second system feature.

30. A server comprising a memory and a processor, the memory having instructions stored therein, which when executed by the processor, implement the method of any of claims 12 to 16.

31. A computer readable storage medium storing instructions which, when executed by a processor of an electronic device, cause the electronic device to implement the method of any one of claims 1-11 or 12-16.