CN112130872B - Hot replacement method and system for radio frequency reader driver - Google Patents

Abstract

The application provides a hot replacement method and a hot replacement system driven by a radio frequency reader, wherein when the radio frequency application detects that an external radio frequency reader is replaced, and acquiring the identification information of the replaced external radio frequency reader, and acquiring the target driving file based on the identification information of the replaced external radio frequency reader. The target driving file is installed in a thermal installation mode, so that the thermal replacement of the external radio frequency reader driver in the running process of the radio frequency application is realized, and after the thermal replacement of the external radio frequency reader driver is completed, the replaced external radio frequency reader can be directly used without reinstalling the radio frequency application or restarting the radio frequency application.

Description

Hot replacement method and system for radio frequency reader driver

Technical Field

The present application belongs to the technical field of radio frequency readers, and in particular, relates to a hot replacement method and system for a radio frequency reader driver.

Background Art

In order to effectively manage fixed assets and conduct statistical analysis, local power companies are vigorously carrying out the construction of physical "ID". Scanning the radio frequency tags that identify fixed assets is an important part of the construction of physical "ID". However, since the physical "ID" mobile operation terminal contains a variety of radio frequency readers, involving multiple radio frequency reader manufacturers, and the original driver files provided by different radio frequency reader manufacturers are different.

When the external RF reader is replaced, the corresponding RF application needs to be reinstalled and the newly installed RF application needs to be restarted to scan the RF tag using the replaced RF reader.

Summary of the invention

In view of this, the purpose of the present application is to provide a hot replacement method and system for a radio frequency reader driver, which is used to solve the problem in the prior art that when an external radio frequency reader is replaced, the corresponding radio frequency application needs to be reinstalled and the newly installed radio frequency application needs to be restarted before the replaced radio frequency reader can be used.

The technical solution is as follows:

The present application provides a hot replacement method for a radio frequency reader driver, comprising:

If the radio frequency application detects that the external radio frequency reader is replaced, the identification information of the replaced radio frequency reader is obtained;

Based on the identification information of the replaced radio frequency reader, a target driver file is obtained;

Use hot installation to install the target driver file to complete the driver installation of the RF reader.

Preferably, the target driver file is a driver file obtained by preprocessing the original driver file;

Among them, the following method is used to preprocess the original driver file:

The original driver files are unified into a so library with the same interface function, and the driver is packaged in the form of a patch package to obtain the target driver file.

Preferably, it also includes:

Upload the target driver file obtained after preprocessing to the RF reader driver management platform;

Accordingly, the step of acquiring the target driver file based on the identification information of the replaced radio frequency reader includes:

If the target driver file is not obtained from the local driver file library, the target driver file is downloaded from the RF reader driver management platform.

Preferably, the method of installing the target driver file by hot installation to complete the driver installation of the radio frequency reader includes:

Use aspect-oriented programming technology to insert the path of the so library in the form of a patch package into the front of the native Library Directories array at the native layer;

Load the so library in the form of a patch package and install it.

Preferably, it also includes:

The target driver file is cached locally to update the local driver file library.

Preferably, the radio frequency reader drive management platform has a visual interface;

The radio frequency reader driving management platform can receive and respond to input operations on the visual interface.

The present application also provides a hot replacement system driven by a radio frequency reader, comprising:

The RF reader driver middleware is used to obtain the identification information of the replaced RF reader if it is detected that the external RF reader is replaced after the RF application is started; obtain the target driver file based on the identification information of the replaced RF reader; install the target driver file using hot installation to complete the driver installation of the RF reader.

Preferably, it also includes:

The driver unification module is used to unify the original driver files into a so library with the same interface function, and package the driver in the form of a patch package to obtain the target driver file.

Preferably, it also includes:

The radio frequency reader driver management platform is used to receive and store the target driver file uploaded by the driver unified format module.

Preferably, the radio frequency reader driver middleware is further used to cache the target driver file locally.

Compared with the prior art, the above technical solution provided by this application has the following advantages:

As can be seen from the above technical solution, in this application, when the RF application detects that the external RF reader has been replaced, the identification information of the replaced external RF reader is obtained, and based on the identification information of the replaced external RF reader, the target driver file is obtained. The target driver file is installed by hot installation to achieve hot replacement of the external RF reader driver during the operation of the RF application. After the hot replacement of the external RF reader driver is completed, the replaced external RF reader can be directly used without reinstalling the RF application or restarting the RF application.

At the same time, in a scenario where compatibility with multiple RF readers is required, if a new RF reader is added, the target driver file corresponding to the newly added RF reader can be obtained, and the target driver file can be installed using hot installation. The newly added RF reader can be used without having to re-update the installation package of the RF application corresponding to the newly added RF reader, re-download the installation package of the RF application, and reinstall the RF application.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

FIG1 is a schematic structural diagram of a radio frequency reader driven hot swap system disclosed in the present application.

FIG2 is a flow chart of a hot replacement method driven by a radio frequency reader disclosed in the present application;

FIG. 3 is a flow chart of another radio frequency reader driven hot replacement method disclosed in the present application.

DETAILED DESCRIPTION

The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

RFID is widely used in the existing technology to manage fixed assets and conduct statistical analysis, such as animal chips, car chip anti-theft devices, access control, parking lot control, production line automation, and material management. Radio Frequency Identification (RFID) is called inductive electronic chips or proximity cards, induction cards, contactless cards, electronic tags, electronic barcodes, etc. A complete RFID system consists of radio frequency tags, radio frequency readers, and antennas. The antenna is generally built into the radio frequency reader. Radio frequency tags are divided into active tags and passive tags, and radio frequency readers are divided into handheld and fixed types.

However, when the external RF reader is replaced, the corresponding RF application needs to be reinstalled and the newly installed RF application needs to be restarted in order to scan the RF tag using the replaced RF reader.

To this end, an embodiment of the present application provides a hot replacement method for a radio frequency reader driver, which is applied to a radio frequency reader driver hot replacement system. As shown in FIG1 , the system includes a radio frequency reader, a radio frequency application, and a radio frequency reader driver management platform.

When the method detects that an external RF reader has been replaced during the operation of a RF application, the driver file corresponding to the replaced RF reader can be directly loaded and installed, and the replaced RF reader can be used to scan RF tags immediately without reinstalling the RF application integrated with the corresponding driver file and restarting the RF application.

As shown in FIG2 , the hot replacement method driven by the radio frequency reader may include the following steps:

S201: If the radio frequency application detects that the external radio frequency reader is replaced, then obtain identification information of the replaced radio frequency reader.

After the RF application is installed and started on the terminal, the RF application can detect the replacement of the external RF reader.

Referring to the system shown in FIG1 , a radio frequency reader driver middleware is integrated in the radio frequency application. The radio frequency reader driver middleware has an internal sensing function, an external sensing function, and a driver discrimination function.

The built-in sensing function is used to detect the built-in RF reader, the external sensing function is used to detect the external RF reader, and the driver identification function is used to determine whether the driver corresponding to the detected RF reader is installed.

Specifically, when the RF application is started, the built-in RF reader is detected and the driver identification function is used to determine whether the driver of the built-in RF reader is installed; if not installed, the corresponding driver file is loaded and the driver installation is completed. Usually, the driver installation of the built-in RF reader is completed when the RF application is installed.

When the RF application detects that the external RF reader has been replaced, it determines whether the driver of the external RF reader is installed through the driver identification function; if not, it obtains the identification information of the replaced RF reader to perform driver hot replacement according to the identification information.

The identification information is used to uniquely identify the external RF reader, such as a manufacturer identification, etc. Different RF readers have different drivers, and thus different RF readers have different corresponding target driver files.

There is a corresponding relationship between the identification information and the target driver file, so that the target driver file corresponding to the identification information is searched based on the corresponding relationship.

S202: Acquire a target driver file based on the identification information of the replaced radio frequency reader.

The target driver file refers to the driver file corresponding to the replaced external radio frequency reader. After obtaining the identification information of the replaced radio frequency reader, the driver file corresponding to the identification information is searched to obtain the target driver file.

S203: Install the target driver file by hot installation to complete the driver installation of the radio frequency reader.

The hot installation method is used to complete the hot replacement of the replaced RF reader driver. After the driver installation of the replaced RF reader is completed, the replaced RF reader can be used directly without reinstalling the RF application or restarting the RF application.

It should be noted that during the driver installation process, if the installation is not completed due to network or other reasons, the driver installation will be automatically completed when the RF application is started next time and the driver identification function determines that the corresponding driver is not installed. The driver here includes the driver of the built-in RF reader and the driver of the external RF reader.

Through the above technical solution, in this embodiment, when the radio frequency application detects that the external radio frequency reader has been replaced, the identification information of the replaced external radio frequency reader is obtained, and based on the identification information of the replaced external radio frequency reader, the target driver file is obtained. The target driver file is installed by hot installation to achieve hot replacement of the external radio frequency reader driver during the operation of the radio frequency application. After the hot replacement of the external radio frequency reader driver is completed, the replaced external radio frequency reader can be directly used without reinstalling the radio frequency application or restarting the radio frequency application.

At the same time, in a scenario where compatibility with multiple RF readers is required, if a new RF reader is added, the target driver file corresponding to the newly added RF reader can be obtained, and the target driver file can be installed using hot installation. The newly added RF reader can be used without having to re-update the installation package of the RF application corresponding to the newly added RF reader, re-download the installation package of the RF application, and reinstall the RF application.

As shown in FIG3 , the embodiment of the present application provides another hot replacement method for a radio frequency reader driver, comprising the following steps:

S301. After preprocessing the original driver file, a target driver file is obtained, and the target driver file is uploaded to the radio frequency reader driver management platform.

The target driving file is different from the original driving file provided by each RF reader manufacturer in the prior art. The target driving file is a driving file obtained by preprocessing the original driving file.

Preprocessing refers to unifying the original driver files into a so library with the same interface function, and packaging the driver in the form of a patch package to obtain the target driver file.

Referring to the system architecture shown in Figure 1, the developers repackaged the original driver files provided by various RF reader manufacturers and unified the original driver files into a so library with the same interface functions. The interface functions include protocol selection, reading data, clearing read data, reading/writing data stop, etc., and the parameters of the same interface functions in different so libraries are consistent.

Use the unified interface template and each so library obtained after secondary packaging to package the driver in the form of a patch package to obtain the target driver file, complete the driver unified format, and solve the problem of driver interface diversity.

After obtaining the target driver file, the obtained target driver file is uploaded to the radio frequency reader driver management platform.

Referring to the system architecture shown in FIG1 , the RF reader driver management platform includes a driver management Web terminal and a driver management server terminal.

The driver management Web terminal provides a visual interface, and provides visual human-computer interaction through the visual interface. The RF reader driver management platform can receive and respond to input operations on the visual interface.

Input operations include driver upload, driver download, driver view, driver deletion and driver usage statistics.

In this way, visual human-computer interaction is provided for functions such as driver upload, driver download, driver view, driver deletion, and driver usage statistics through a visual interface.

The driver management server provides driver management interfaces such as driver addition, driver deletion, driver reading, driver list and driver details, and implements driver indexing to manage the driver file library.

S302: If the radio frequency application detects that the external radio frequency reader is replaced, then obtain identification information of the replaced radio frequency reader.

The implementation of step S302 in this embodiment is similar to the implementation of step S201 in the previous embodiment, and will not be repeated here.

S303, obtaining a target driver file from a local driver file library, and determining whether the target driver file is obtained from the local driver file library;

If it is determined that the target driver file cannot be obtained from the local driver file library, step S304 is executed;

If it is determined that the target driver file is obtained from the local driver file library, step S305 is executed.

After the developer uploads the target driver file to the driver management platform, the corresponding target driver file can be downloaded from the driver management platform based on the identification information of the replaced RF reader. After the target driver file is downloaded from the driver management platform, the target driver file is cached locally and the local driver file library is updated. In this way, in the subsequent process of obtaining the target driver file according to the identification information, the target driver file is first obtained from the local driver file library. Only when the target driver file cannot be obtained from the local driver file library, the driver management platform is remotely called to download the target driver file.

As shown in FIG1 , the RF reader driver middleware has a driver storage function, which caches the target driver files of all external RF readers that have been used in the past. In this way, in the subsequent use process, if the external RF reader is replaced with an external RF reader that has been used in the past, the target driver file is first obtained from the local driver file library, and the local driver file library has already cached the corresponding target driver file, so the corresponding target driver file can be obtained from the local driver file library, thereby eliminating the need to download the target driver file from the RF reader driver management platform again.

In this way, by adopting a dual storage method of driver management platform storage combined with local driver cache, the problem of repeated downloading of driver files when the external radio frequency reader is replaced is solved.

Optionally, the RF reader driver middleware also includes functions such as driver addition, driver deletion, driver reading, driver indexing and driver file library, etc. The driver indexing is completed by the built-in database SQLite of the Android application.

S304: Download the target driver file from the radio frequency reader driver management platform.

Remotely call the driver management platform and download the target driver file.

S305: Install the target driver file by hot installation to complete the driver installation of the radio frequency reader.

In the embodiment of the present application, the aspect-oriented programming (AOP) technology is used to insert the path of the so library in the form of a patch package obtained at the native layer into the front of the native Library Directories array, so that when the so library is loaded, the so library in the form of a patch package is loaded instead of the directory of the original so library, thereby achieving the purpose of hot replacement of the radio frequency reader driver.

Aspect Oriented Programming (AOP) is a technology that achieves unified maintenance of program functions through pre-compilation and dynamic proxy during runtime. AOP is an important part of the Spring framework and a derivative paradigm of functional programming. AOP can be used to isolate various parts of business logic, thereby reducing the coupling between the various parts of business logic, improving the reusability of the program, and improving development efficiency.

Through the above technical scheme, the plug-in and hot repair technology based on Android application development in the embodiment of the present application adopts the form of a patch to complete the driver unification format. The core of the patch is the patch so library, which is the original driver file provided by the RF reader manufacturer and is repackaged and unified into a so library with the same interface function. Using AOP programming technology, the path of the patch so library is inserted to the front of the nativeLibraryDirectories array at the native layer, so that when loading the so library, it is the patch so library instead of the directory of the original so library, thereby achieving the purpose of hot installation of the RF driver. It is possible to directly use the replaced external RF reader without reinstalling and restarting the RF application.

Moreover, in a scenario where compatibility with multiple RF readers is required, if a new RF reader is added, the target driver file corresponding to the newly added RF reader can be downloaded from the RF reader driver management platform, and the target driver file can be installed using hot installation. The newly added RF reader can be used without having to re-update the installation package of the RF application corresponding to the newly added RF reader, re-download the installation package of the RF application, and re-install the RF application.

Corresponding to the hot replacement method driven by the radio frequency reader disclosed in the above embodiment, this embodiment further provides a hot replacement system driven by the radio frequency reader, as shown in FIG1 , the system includes:

The RF reader driver middleware is used to obtain the identification information of the replaced RF reader if it is detected that the external RF reader is replaced after the RF application is started; obtain the target driver file based on the identification information of the replaced RF reader; install the target driver file using hot installation to complete the driver installation of the RF reader.

Through the above technical solution, in this embodiment, after the RF application is started, when the RF reader driver middleware detects that the external RF reader has been replaced, the identification information of the replaced external RF reader is obtained, and the target driver file is obtained based on the identification information of the replaced external RF reader. The target driver file is installed by hot installation to realize the hot replacement of the external RF reader driver during the operation of the RF application. After the hot replacement of the external RF reader driver is completed, the replaced external RF reader can be directly used without reinstalling the RF application or restarting the RF application. At the same time, in the scenario where multiple RF readers need to be compatible, if a new RF reader is added, the target driver file corresponding to the newly added RF reader can be obtained, and the target driver file can be installed by hot installation, so that the newly added RF reader can be used without re-updating the installation package of the RF application corresponding to the newly added RF reader, re-downloading the installation package of the RF application and reinstalling the RF application.

Optionally, in other embodiments, the hot replacement system driven by the radio frequency reader further includes:

The driver unification module is used to unify the original driver files into a so library with the same interface function, and package the driver in the form of a patch package to obtain the target driver file.

Among them, the interface functions include protocol selection, reading data, clearing read data, reading/writing data stop, etc.

The unified drive standard is achieved through the unified drive standard module, solving the problem of diversified drive interfaces.

Optionally, a method of installing the target driver file by hot installation to complete the driver installation of the radio frequency reader is as follows:

By using the Aspect Oriented Programming (AOP) technology, the path of the so library in the form of a patch package is inserted into the front of the native Library Directories array at the native layer, so that when the so library is loaded, the so library in the form of a patch package is loaded instead of the directory of the original so library, thereby achieving the purpose of hot replacement of the RF reader driver.

Through the above technical scheme, the plug-in and hot repair technology based on Android application development in the embodiment of the present application adopts the form of a patch to complete the driver unification format. The core of the patch is the patch so library, which is the original driver file provided by the RF reader manufacturer and is repackaged and unified into a so library with the same interface function. Using AOP programming technology, the path of the patch so library is inserted to the front of the nativeLibraryDirectories array at the native layer, so that when loading the so library, it is the patch so library instead of the directory of the original so library, thereby achieving the purpose of hot installation of the RF driver. It is possible to directly use the replaced external RF reader without reinstalling and restarting the RF application.

Moreover, in a scenario where compatibility with multiple RF readers is required, if a new RF reader is added, the target driver file corresponding to the newly added RF reader can be downloaded from the RF reader driver management platform, and the target driver file can be installed using hot installation. The newly added RF reader can be used without having to re-update the installation package of the RF application corresponding to the newly added RF reader, re-download the installation package of the RF application, and re-install the RF application.

Optionally, in other embodiments, the hot replacement system driven by the radio frequency reader further includes:

The radio frequency reader driver management platform is used to receive and store the target driver file uploaded by the driver unified format module.

The RF reader driver management platform includes a driver management Web terminal and a driver management server terminal.

The driver management web terminal provides a visual interface, which provides visual human-computer interaction. The visual interface can receive the operator's input operation and respond to the input operation.

Input operations include driver upload, driver download, driver view, driver deletion and driver usage statistics.

In this way, visual human-computer interaction is provided for functions such as driver upload, driver download, driver view, driver deletion, and driver usage statistics through a visual interface.

The driver management server provides driver management interfaces such as driver addition, driver deletion, driver reading, driver list and driver details, and implements driver indexing to manage the driver file library.

Optionally, in other embodiments, the radio frequency reader driver middleware is further used to cache the target driver file locally.

As shown in FIG1 , the RF reader driver middleware has a driver storage function, which caches the target driver files of all external RF readers that have been used in the past. In this way, in the subsequent use process, if the external RF reader is replaced with an external RF reader that has been used in the past, the target driver file is first obtained from the local driver file library, and the local driver file library has already cached the corresponding target driver file, so the corresponding target driver file can be obtained from the local driver file library, thereby eliminating the need to download the target driver file from the RF reader driver management platform again.

By adopting a dual storage method of driver management platform storage combined with local driver cache, the problem of repeated downloading of driver files when the external RF reader is replaced is solved.

Optionally, in other embodiments, the RF reader driver middleware further includes functions such as driver addition, driver deletion, driver reading, driver indexing and driver file library, etc. The driver indexing is completed by the built-in database SQLite of the Android application.

For the above-mentioned method embodiments, for the sake of simplicity, they are all described as a series of action combinations, but those skilled in the art should know that the present invention is not limited by the order of the actions described, because according to the present invention, some steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the present invention.

It should be noted that each embodiment in this specification is described in a progressive manner, and each embodiment focuses on the differences from other embodiments, and the same or similar parts between the embodiments can be referred to each other. For the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

Finally, it should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the presence of other identical elements in the process, method, article or device including the elements.

The above description of the disclosed embodiments enables those skilled in the art to implement or use the present invention. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention will not be limited to the embodiments shown herein, but rather to the widest scope consistent with the principles and novel features disclosed herein.

The above is only a preferred embodiment of the present invention. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principle of the present invention. These improvements and modifications should also be regarded as the scope of protection of the present invention.

Claims (7)

1. A method of rf reader driven thermal replacement comprising:

If the radio frequency application detects that the external radio frequency reader is replaced, acquiring the identification information of the replaced radio frequency reader; the radio frequency application integrates a radio frequency reader driving middleware which has an internal sensing function, an external sensing function and a driving judging function; the internal sensing function is used for detecting the internal radio frequency reader, the external sensing function is used for detecting the external radio frequency reader, and the drive judging function is used for determining whether a drive corresponding to the detected radio frequency reader is installed or not; if the radio frequency application detects that the external radio frequency reader is replaced, the method for acquiring the identification information of the replaced radio frequency reader comprises the following steps: if the radio frequency application detects that the external radio frequency reader is replaced, determining whether a driver of the external radio frequency reader is installed or not through a driver judging function, and if the driver is not installed, acquiring identification information of the replaced radio frequency reader;

Acquiring a target driving file based on the identification information of the replaced radio frequency reader;

installing a target driving file in a thermal installation mode to finish the driving installation of the radio frequency reader;

The target driving file is a driving file obtained by preprocessing an original driving file;

the method comprises the following steps of:

Unifying the original driving files into a so library with the same interface function, and driving and packaging the so library in the form of a patch package to obtain a target driving file;

The method for installing the target driving file by using the thermal installation mode, which completes the driving installation of the radio frequency reader, comprises the following steps:

Inserting the obtained path of the so library in the form of the patch package into the forefront of native Library Directories arrays at the native layer by using a technique facing to the tangent plane programming;

and loading and installing a so library in the form of a patch package.

2. The thermal replacement method according to claim 1, further comprising:

uploading the target driving file obtained after pretreatment to a radio frequency reader driving management platform;

correspondingly, the acquiring the target driving file based on the identification information of the replaced radio frequency reader comprises the following steps:

and if the target driving file is not obtained from the local driving file library, downloading the target driving file from the radio frequency reader driving management platform.

3. The thermal replacement method according to claim 2, further comprising:

And locally caching the target drive file to update the local drive file library.

4. The thermal replacement method of claim 2, wherein the rf reader driver management platform has a visual interface;

the RF reader driver management platform is capable of receiving and responding to input operations on the visual interface.

5. A radio frequency reader driven thermal replacement system comprising:

The radio frequency reader driving middleware is used for acquiring the identification information of the replaced radio frequency reader if the replacement of the external radio frequency reader is detected after the radio frequency application is started; acquiring a target driving file based on the identification information of the replaced radio frequency reader; installing a target driving file in a thermal installation mode to finish the driving installation of the radio frequency reader; the radio frequency reader driving middleware is integrated in the radio frequency application and has an internal sensing function, an external sensing function and a driving judging function; the internal sensing function is used for detecting the internal radio frequency reader, the external sensing function is used for detecting the external radio frequency reader, and the drive judging function is used for determining whether a drive corresponding to the detected radio frequency reader is installed or not; if the external radio frequency reader is detected to be replaced, the method for acquiring the identification information of the replaced radio frequency reader comprises the following steps: if the external radio frequency reader is detected to be replaced, determining whether a driver of the external radio frequency reader is installed or not through a driver judging function, and if the driver is not installed, acquiring identification information of the replaced radio frequency reader;

Further comprises:

The drive unified system module is used for unifying the original drive files into a so library with the same interface function, and carrying out drive packaging in the form of a patch package to obtain target drive files;

The method for installing the target driving file by using the thermal installation mode, which completes the driving installation of the radio frequency reader, comprises the following steps:

Inserting the obtained path of the so library in the form of the patch package into the forefront of native Library Directories arrays at the native layer by using a technique facing to the tangent plane programming;

and loading and installing a so library in the form of a patch package.

6. The system of claim 5, further comprising:

And the radio frequency reader drive management platform is used for receiving and storing the target drive file uploaded by the drive unified system module.

7. The system of any of claims 5-6, wherein the rf reader driver middleware is further configured to locally cache the target driver file.