Field(s)	WIFI connection attribute information
		ssid	WIFI name
bssid	Router MAC address
		rssi	WIFI Strength
networkid	Id of network operator of WIFI connection
		ip	IP address of terminal equipment connected with WIFI
is_hidden_ssid	Whether to hide WIFI names of wireless networks

Considering that in an android simulator, a WIFI on-off state value is generally unknown in a WIFI state, in a specific implementation manner, a monitoring table is registered first, the WIFI on-off state value of the android system running the to-be-detected android program is monitored, if the monitored on-off state value is any one of the WIFI on, the WIFI off and the WIFI off, it is determined that the android system has WIFI configuration information, if the monitored on-off state value is unknown in the WIFI state, whether WIFI connection attribute information of the android system can be acquired is detected, if the WIFI connection attribute information of the android system is acquired, it is determined that the android system has the WIFI configuration information, and if the WIFI connection attribute information of the android system is not acquired, it is determined that the android system does not have the WIFI configuration information.

In this embodiment, whether the android system running the android program to be detected has short message function configuration information is detected, specifically: and simulating and executing a short message sending process in the android system running the android program to be detected, if the simulated and executed short message sending is successful, determining that the android system has short message function configuration information, and if the simulated and executed short message sending is failed, determining that the android system does not have short message function configuration information.

The simulation execution short message sending process specifically comprises the following steps: whether the terminal equipment has short message sending configuration is tested according to a short message sending mode of android, short message sending authority is registered at first, then a PendingIntent object is built and broadcasted by using getBacladcast (), and finally PendingIntent, short message content, telephone number (preset telephone number regular) and other contents are transmitted into a sendTextMessage () method of SmsManager. If the simulation process is abnormal because a certain component does not exist, determining that the simulation execution short message is failed to be sent, otherwise, determining that the simulation execution short message is successfully sent.

In this embodiment, whether an android system running an android program to be detected has memory card configuration information is detected, which specifically includes: detecting whether an android system running an android program to be detected has one or more of the following information: memory card memory information, memory card storage directory information, memory card directory authority information, and memory card plugging state values; and if so, determining that the android system has the memory card configuration information, otherwise, determining that the android system does not have the memory card configuration information.

In a specific embodiment, fopen is used to open a function open path "/proc/meminfo" in an android system running an android program to be detected, if a returned result is not null, it is determined that memory card memory information of the android system is obtained, and it is determined that the android system has the memory card memory information; and a register listener can also monitor the plug-pull state value of the memory card, and if the monitoring result is not null, the android system is confirmed to have the plug-pull state value of the memory card. For a terminal device running an android simulator, a memory card plug state value is not provided, and for an android system-based android device, a memory card plug state value is provided. The memory Card in this embodiment may be an SD (Secure Digital Card).

It should be noted that the unmodified customized simulator does not have the above specific configuration information (WIFI configuration information, sms function configuration information, and memory card configuration information), and the modified customized simulator may have the above specific configuration information, and the modification customization refers to modifying the system information for the purpose of evasion detection.

Considering that a terminal device running an android simulator is generally different from a sensor installed in an android device based on an android System, for example, a notebook computer running the android simulator is generally installed with only a GPS (Global Positioning System) sensor, while an android device such as an android mobile phone is generally installed with various sensors such as GPS, acceleration, speed, gravity, and the like, for example, the android device such as the android mobile phone is generally installed with the following sensors:

LTR55X ALSPRX, -Non Wakeup Secondary (without Secondary wake-up)

Rotation Vector, -Wakeup Secondary Wakeup

Step Counter, -Wakeup Secondary Consequence (with Secondary Wake-Up)

LTR55X ALSPRX, -Wakeup Secondary (with Secondary Wakeup)

Organization, -Wakeup Secondary Wakeup

BMI160Gyroscope, -Wakeup Secondary (with Secondary Wakeup)

BMI160Accelerometer, -Wakeup Secondary System (with Secondary Wakeup)

And 20 types of sensors such as a Game Rotation Vector, Wakeup Secondary (with Secondary wake-up) sensor and the like.

Therefore, in this embodiment, a sensor installation list is preset, the preset sensor installation list records the types and the number of sensors that are usually installed in android devices based on an android system, and table 2 is one schematic of the preset sensor installation list.

TABLE 2

Kind of sensor	Number/number
		Image pickup sensor	4
Gravity sensor	2
		Speed sensor	1
Acceleration sensor	1
		Position sensor	2
Total of	10

Based on the preset sensor installation list, in step S102, it is determined whether the terminal device meets a preset sensor installation requirement, specifically: acquiring sensor installation information of terminal equipment; detecting whether the number of the sensors missing from the terminal equipment is smaller than a preset number threshold value and whether the type of the sensors missing from the terminal equipment is smaller than a preset type threshold value according to the sensor installation information and a preset sensor installation list; and if the number of the terminal equipment is less than the preset number, determining that the terminal equipment meets the sensor installation requirement, otherwise, determining that the terminal equipment does not meet the sensor installation requirement.

In a specific embodiment, a weight may be assigned to each sensor type in the preset sensor installation list, and in particular, a weight may be assigned to each sensor type according to the importance degree or the use frequency of each sensor, the sensor installation information is compared with the content in the preset sensor installation list, the sensor type installed by the terminal device and the weight corresponding to each sensor type are determined, the weights corresponding to each sensor type installed by the terminal device are summed to obtain a weight value corresponding to the sensor type installed by the terminal device, the magnitude relationship between the weight value and a preset weight threshold is compared, if the weight value is greater than the preset weight threshold, it is determined that the terminal device meets the sensor installation requirement, otherwise, it is determined that the terminal device does not meet the sensor installation requirement. The preset weight threshold may be a weight value predetermined empirically.

In another specific implementation manner, it is predicted that the android program to be detected may run in a certain android simulator, and if it is predicted that the android program to be detected may run in the VM virtual machine, then at least one sensor related to the android simulator which may run is selected from the preset sensor installation list, whether the selected various sensors are installed in the terminal device is detected, if the terminal device is installed with the selected various sensors, it is determined that the terminal device meets the sensor installation requirements, and otherwise, it is determined that the terminal device does not meet the sensor installation requirements.

In the step S104, if the android system running the android program to be detected does not have the specific configuration information, and/or the terminal device does not meet the sensor installation requirement, it is determined that the android program to be detected runs in the android simulator.

It can be seen that, in the android simulator detection method in fig. 1, based on the configuration information of the android system in the terminal device and the sensor installation condition of the terminal device, it is determined from two aspects of the configuration information and the hardware characteristics whether the android program to be detected runs in the android simulator, if it is determined that the android program to be detected runs in the android simulator, it is described that the terminal device is a device running with the android simulator, and if it is determined that the android program to be detected does not run in the android simulator, it is described that the terminal device is the android device based on the android system.

The sensor installation condition of the terminal device is one of the hardware characteristics of the terminal device, and the hardware characteristics of the terminal device can also be reflected in some specific fields, such as an operator information field, a fingerprint collection fingerprint field, a product name product field, a version model field, a hardware name hardware field, and the like, and based on this, in this embodiment of the present application, before determining that the android program to be detected does not run in the android simulator, the method further includes:

detecting whether information related to the android simulator is contained in the specific field;

determining that the android program to be detected does not run in the android simulator, specifically:

and if the specific field does not contain the information related to the android simulator, determining that the android program to be detected does not run in the android simulator.

The specific field includes one or more of an operator information field (such as an operator name field), a fingerprinting fingerprint field, a product name field, a version model field, and a hardware name hardware field, and the information related to the android simulator may be simulator identification and the like. Taking specific fields including an operator information field, a fingerprint collection fingerprint field, a product name product field, a version model field and a hardware name hardware field as an example, if the android program to be detected is not operated in the android simulator, any one of the operator information field, the fingerprint collection fingerprint field, the product name product field, the version model field and the hardware name hardware field of the terminal device does not contain information related to the android simulator, so in this embodiment, before determining that the android program to be detected is not operated in the android simulator, whether the operator information field, the fingerprint collection fingerprint field, the product name product field, the version model field and the hardware name hardware field of the terminal device contain information related to the android simulator or not can be detected, if each field does not contain information related to the android simulator, determining that the android program to be detected is not operated in the android simulator, and if any field contains information related to the android simulator, determining that the android program to be detected runs in the android simulator. In the embodiment, the accuracy of simulator detection can be improved by detecting whether the specific field contains information related to the android simulator.

In a specific embodiment, an execution main body of the application is an android program to be detected, after the android program to be detected runs, an operator information field, a fingerprint acquisition fingerprint field, a product name product field, a version model field and a hardware name hardware field are acquired under a running system of the android program to be detected, whether information related to an android simulator is contained in each field is detected according to the above mode, and whether the android program runs in the android simulator is determined.

Based on the above, an embodiment of the present application further provides a flow of an android simulator detection method combining configuration information and hardware characteristics, and fig. 2 is a second schematic flow diagram of the android simulator detection method combining configuration information and hardware characteristics provided in the embodiment of the present application, as shown in fig. 2, the flow is executed after a terminal device runs an android program to be detected, and includes the following steps:

step S202, judging whether the android system running the android program to be detected has specific configuration information for identifying the non-android simulator.

The android system running the android program to be detected is the android system in the terminal device, if the android system running the android program to be detected has specific configuration information, step S204 is executed, and otherwise, step S210 is executed. This step may refer to the description of step S102, which is not described herein again.

And step S204, judging whether the terminal equipment meets the preset sensor installation requirement.

If yes, go to step S206, otherwise, go to step S210. This step may refer to the description of step S102, which is not described herein again.

Step S206, detecting whether the specific field contains information related to the android simulator.

If not, go to step S208, otherwise go to step S210. This step may be referred to the previous description and will not be repeated here.

And S208, determining that the android program to be detected does not run in the android simulator.

And step S210, determining that the android program to be detected runs in the android simulator.

In fig. 2, the execution sequence of step S202, step S204, and step S206 is not limited, and may be executed in the order of step S202, step S204, step S206, or in other orders such as step S204, step S206, step S202, and the like, which are not listed here.

By the method in fig. 2, whether the android program to be detected runs in the android simulator can be determined based on the configuration information of the terminal device and the hardware characteristics of the terminal device, and the accuracy of the determination result can be ensured by adopting a mode of combining the configuration information and the hardware characteristics.

The hardware characteristics of the terminal device can also be reflected in aspects such as a memory card slot and a Subscriber Identity Module (SIM) card slot, so that in this embodiment, it can also be detected whether the terminal device has the memory card slot and the SIM card slot, and if the terminal device does not have the memory card slot and/or the SIM card slot, it is determined that the android program to be detected runs in the android simulator.

Based on this, an embodiment of the present application further provides a flow of an android simulator detection method combining configuration information and hardware characteristics, and fig. 3 is a third flow schematic diagram of the android simulator detection method combining configuration information and hardware characteristics provided by the embodiment of the present application, as shown in fig. 3, the flow is executed after the terminal device runs an android program to be detected, and the method includes the following steps:

step S302, judging whether the android system running the android program to be detected has specific configuration information for identifying the non-android simulator.

If the specific configuration information exists, step S304 is executed, otherwise step S320 is executed.

And step S304, judging whether the terminal equipment meets the preset sensor installation requirement.

If yes, go to step S306, otherwise go to step S320.

Step S306, detecting whether the specific field contains information related to the android simulator.

If not, go to step S308, otherwise, go to step S320.

And step S308, detecting whether the terminal equipment has a process communication channel specific to the android simulator.

The process communication channels specific to android simulators include "/dev/socket/qemud" and "/dev/qemu _ pipe". And opening the functions of "/dev/socket/qemud" and "/dev/qemu _ pipe", if the two return values are null, the terminal device does not have a process communication channel specific to the android simulator, and executing the step S310, otherwise, executing the step S320.

Step S310, determining whether the terminal device has an ID (identity) unique to the android simulator.

The simulator-specific ID is { "000000000000000" }. Judging whether the ID of the terminal equipment is { "000000000000000" }, if not, determining that the terminal equipment does not have the ID specific to the android simulator, and executing step S312, otherwise, executing step S320.

Step S312, determine whether the terminal device has a unique phone number of the android emulator.

If not, go to step S314, otherwise go to step S320.

The unique phone numbers of android simulators include:

{"15555215554","15555215556","15555215582","15555215584"

"15555215558","15555215560","15555215562","15555215564",

"15555215566","15555215568","15555215570","15555215572",

"15555215574","15555215576","15555215578","15555215580"}。

and step S314, judging whether the terminal equipment has a simulator file specific to the android simulator.

If not, go to step S316, otherwise, go to step S320.

The simulator files specific to android simulators include:

{"/system/lib/libc_malloc_debug_qemu.so"；

"/sys/qemu_trace"；

"/system/bin/qemu-props"；}。

step S316, determining whether the terminal device has IMSI (international mobile Subscriber identity Number) information specific to the android emulator.

The IMSI ID unique to android simulator is 310260000000000. And judging whether the IMSI ID of the terminal equipment is 310260000000000, if not, determining that the terminal equipment does not have the IMSI information specific to the android simulator, and executing step S318, otherwise, executing step S320.

And step S318, determining that the android program to be detected does not run in the android simulator.

And step S320, determining that the android program to be detected runs in the android simulator.

In fig. 3, the sequence from step S302 to step S316 is not limited, and may be executed as shown in fig. 3, or the execution sequence from step S302 to step S316 may be adjusted as needed. By the method in fig. 3, whether the android program to be detected runs in the android simulator can be determined based on the configuration information of the terminal device and various hardware characteristics of the terminal device, and the accuracy of the determination result can be ensured by adopting a mode of combining the configuration information and the hardware characteristics.

Based on the above android simulator detection method, an embodiment of the present invention further provides an android simulator detection apparatus combining configuration information and hardware characteristics, the apparatus can execute the above android simulator detection method, fig. 4 is a schematic diagram of a first module composition of the android simulator detection apparatus combining configuration information and hardware characteristics provided in the embodiment of the present application, and as shown in fig. 4, the apparatus includes:

the information detection module 41 is configured to determine, after the terminal device runs the to-be-detected android program, whether an android system running the to-be-detected android program has specific configuration information for identifying a non-android simulator, and determine whether the terminal device meets a preset sensor installation requirement;

and a result determining module 42, configured to determine that the android program to be detected does not run in the android simulator if the android system has the specific configuration information and the terminal device meets the sensor installation requirement, and otherwise, determine that the android program to be detected runs in the android simulator.

Optionally, the information detecting module 41 is specifically configured to:

detecting whether the android system running the android program to be detected has wireless fidelity (WIFI) configuration information, short message function configuration information and memory card configuration information;

and if so, determining that the android system has the specific configuration information.

Optionally, the information detecting module 41 is specifically configured to:

acquiring sensor installation information of the terminal equipment;

detecting whether the number of the sensors missing from the terminal equipment is smaller than a preset number threshold value and whether the type of the sensors missing from the terminal equipment is smaller than a preset type threshold value according to the sensor installation information and a preset sensor installation list;

and if the number of the terminal equipment is less than the preset value, determining that the terminal equipment meets the installation requirement of the sensor.

Optionally, the information detecting module 41 is further specifically configured to:

detecting whether the android system running the android program to be detected has a WIFI switch state value, and if so, determining that the android system has the WIFI configuration information;

or,

and detecting whether the android system running the android program to be detected has WIFI connection attribute information, and if so, determining that the android system has the WIFI configuration information.

simulating and executing a short message sending process in the android system running the android program to be detected;

and if the simulation execution short message is successfully sent, determining that the android system has the short message function configuration information.

detecting whether the android system running the android program to be detected has one or more of the following information:

memory card memory information, memory card storage directory information, memory card directory authority information, and memory card plugging state values;

and if so, determining that the android system has the memory card configuration information.

The android simulator detection device in the embodiment of the application, it is the android application program to detect the android program, after the android program is detected in the operation of the terminal equipment, whether the android system of the android program to be detected in the operation has the specific configuration information used for identifying the non-android simulator, and whether the terminal equipment meets the preset sensor installation requirement is determined, if the android system has the specific configuration information, and the terminal equipment meets the sensor installation requirement, the android program to be detected is determined not to operate in the android simulator, otherwise, the android program to be detected is determined to operate in the android simulator. Because specific configuration information can mark a non-android simulator, and a terminal device running the android simulator is usually different from a sensor installed on an android device based on an android system, through the android simulator detection device in the embodiment of the application, whether an android program to be detected runs in the android simulator can be determined based on the specific configuration information marking the non-android simulator and the installation condition of the sensor, so that the use safety of the android program to be detected is ensured.

Fig. 5 is a schematic diagram of a second module composition of the android simulator detection apparatus combining configuration information and hardware characteristics according to the embodiment of the present application, and as shown in fig. 5, the apparatus further includes:

a field detection module 51, configured to detect whether a specific field includes information related to an android simulator before determining that the android program to be detected is not run in the android simulator;

the result determining module 42 is specifically configured to determine that the android program to be detected is not run in the android simulator if the specific field does not contain information related to the android simulator.

In the embodiment, the accuracy of simulator detection can be improved by detecting whether the specific field contains information related to the android simulator.

Further, based on the above android simulator detection method, an embodiment of the present application further provides an android simulator detection device that combines configuration information and hardware characteristics, and fig. 6 is a schematic structural diagram of the android simulator detection device that combines configuration information and hardware characteristics and is provided by the embodiment of the present application.

As shown in fig. 6, the android simulator detection device may have a relatively large difference due to different configurations or performances, and may include one or more processors 601 and a memory 602, where one or more stored applications or data may be stored in the memory 602. Wherein the memory 602 may be transient or persistent storage. The application program stored in memory 602 may include one or more modules (not shown), each of which may include a series of computer-executable instructions in an android simulator detection device. Still further, the processor 601 may be configured to communicate with the memory 602 to execute a series of computer-executable instructions in the memory 602 on an android simulator detection device. The android simulator detection apparatus may also include one or more power supplies 603, one or more wired or wireless network interfaces 604, one or more input-output interfaces 605, one or more keyboards 606, and the like.

In one particular embodiment, an android simulator detection apparatus includes a memory, and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions for the android simulator detection apparatus, and configured for execution by one or more processors the one or more programs including computer-executable instructions for:

Optionally, when executed, the computer executable instructions determine whether an android system running the to-be-detected android program has specific configuration information for identifying a non-android simulator, including:

Optionally, the computer executable instructions, when executed, determine whether the terminal device meets a preset sensor installation requirement, comprising:

acquiring sensor installation information of the terminal equipment;

Optionally, when executed, the computer-executable instruction detects whether the android system running the to-be-detected android program has WIFI configuration information, including:

or,

Optionally, when executed, the computer executable instruction detects whether the android system running the android program to be detected has short message function configuration information, including:

Optionally, when executed, the computer-executable instruction detects whether an android system running the to-be-detected android program has memory card configuration information, including:

Optionally, before determining that the to-be-detected android program is not run in the android simulator, the computer-executable instructions, when executed, further include:

determining that the android program to be detected does not run in an android simulator, including:

Because specific configuration information can identify a non-android simulator, and a terminal device for operating the android simulator is usually different from a sensor installed on an android device based on an android system, whether an android program to be detected operates in the android simulator can be determined based on the specific configuration information for identifying the non-android simulator and the installation condition of the sensor through the android simulator detection device in the embodiment of the application, so that the use safety of the android program to be detected is ensured.

Further, based on the above method for detecting an android simulator, an embodiment of the present application further provides a storage medium for storing computer executable instructions, in a specific embodiment, the storage medium may be a usb disk, an optical disk, a hard disk, and the like, and when the computer executable instructions stored in the storage medium are executed by a processor, the following process can be implemented:

Optionally, the storage medium stores computer-executable instructions that, when executed, determine whether an android system running the to-be-detected android program has specific configuration information for identifying a non-android simulator, including:

Optionally, the storage medium stores computer-executable instructions that, when executed, determine whether the terminal device meets a preset sensor installation requirement, including:

acquiring sensor installation information of the terminal equipment;

Optionally, when executed, the computer-executable instructions stored in the storage medium detect whether the android system running the android program to be detected has WIFI configuration information, including:

or,

Optionally, when executed, the computer executable instructions stored in the storage medium detect whether the android system running the to-be-detected android program has short message function configuration information, including:

Optionally, when executed, the computer-executable instructions stored in the storage medium detect whether the android system running the to-be-detected android program has memory card configuration information, including:

Optionally, the storage medium stores computer-executable instructions that, when executed, further comprise, before determining that the android program to be detected is not running in the android simulator:

Because the specific configuration information can identify the non-android simulator, and the sensor for installing the terminal device running the android simulator is usually different from the sensor for installing the android device based on the android system, whether the android program to be detected runs in the android simulator can be determined based on the specific configuration information identifying the non-android simulator and the installation condition of the sensor through the storage medium in the embodiment of the application, so that the use safety of the android program to be detected is ensured.

In the 90 s of the 20 th century, improvements in a technology could clearly distinguish between improvements in hardware (e.g., improvements in circuit structures such as diodes, transistors, switches, etc.) and improvements in software (improvements in process flow). However, as technology advances, many of today's process flow improvements have been seen as direct improvements in hardware circuit architecture. Designers almost always obtain the corresponding hardware circuit structure by programming an improved method flow into the hardware circuit. Thus, it cannot be said that an improvement in the process flow cannot be realized by hardware physical modules. For example, a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), is an integrated circuit whose Logic functions are determined by programming the Device by a user. A digital system is "integrated" on a PLD by the designer's own programming without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Furthermore, nowadays, instead of manually making an integrated Circuit chip, such Programming is often implemented by "logic compiler" software, which is similar to a software compiler used in program development and writing, but the original code before compiling is also written by a specific Programming Language, which is called Hardware Description Language (HDL), and HDL is not only one but many, such as abel (advanced Boolean Expression Language), ahdl (alternate Language Description Language), traffic, pl (core unified Programming Language), HDCal, JHDL (Java Hardware Description Language), langue, Lola, HDL, laspam, hardsradware (Hardware Description Language), vhjhd (Hardware Description Language), and vhigh-Language, which are currently used in most common. It will also be apparent to those skilled in the art that hardware circuitry that implements the logical method flows can be readily obtained by merely slightly programming the method flows into an integrated circuit using the hardware description languages described above.

The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, an Application Specific Integrated Circuit (ASIC), a programmable logic controller, and an embedded microcontroller, examples of which include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic for the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller as pure computer readable program code, the same functionality can be implemented by logically programming method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Such a controller may thus be considered a hardware component, and the means included therein for performing the various functions may also be considered as a structure within the hardware component. Or even means for performing the functions may be regarded as being both a software module for performing the method and a structure within a hardware component.

The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functionality of the units may be implemented in one or more software and/or hardware when implementing the present application.

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

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

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

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

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

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

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

It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

The application may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The application may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.

The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.

The above description is only an example of the present application and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.