KR101781527B1 - Method for verifying mobile application and terminal using the same - Google Patents

Abstract

A mobile application verification method and a terminal to which the method is applied are disclosed.
The terminal is equipped with an application layer and a mobile open platform. In the application layer, a target application created based on a mobile open platform and an API function group and a system callback function group exchanged between the application and the platform are hooked And a verification agent for verifying whether or not the normal operation of the apparatus is performed. At the start of the target application, the terminal's verification agent requests the handle of the application to obtain the process information, registers the hooking process information, and then uses the hooking process information to access API functions Group and system callback function groups are hooked up to collect and monitor the results.
According to this configuration, it is possible to verify whether the application is normally installed and operated for an application created based on the mobile open platform, and to easily debug the application, thereby providing convenience in development, error detection and correction of the application.

Description

METHOD FOR VERIFYING MOBILE APPLICATION AND TERMINAL USING THE SAME,

The present invention relates to a method of verifying a mobile application and a terminal to which the method is applied. More particularly, the present invention relates to a method for verifying whether an application is normally installed and operated on an application built on a mobile open platform such as WIPI, To a mobile application verification method that can provide convenience in development, error identification, and correction of an application and shorten an application development period accordingly, and a terminal to which the method is applied.

Recently, as devices such as smart phones have become widespread, many application markets (app stores, etc.) provided by manufacturers and mobile communication providers are emerging. Also, in this environment, when a content developer commercially creates an application and uploads it to an application market, a service pattern is changed in a way that individual users download and use the application from the terminal.

Meanwhile, in the past, an application has been provided in a form in which a manufacturer manufactures an application according to the policy of a mobile communication provider and basically mounts the application in a terminal or a mobile communication company dedicated to testing and management. Accordingly, I was able to participate.

However, as the terminal equipped with a mobile open platform such as WIPI is commercialized, the environment for creating an application is opened, and even for an individual user, an environment in which an application can be easily produced and sold through an application market such as an app store As a result, numerous applications are being produced. Here, the mobile open platform is a platform that is installed in a terminal such as a smart phone and provides an environment in which an application can be executed, and is developed in a form embedded with an operating system (OS) in a terminal. The application can be executed on the terminal only if it is developed based on the standard of the mobile open platform which is a unique execution environment built in the terminal.

As the application production environment is open, the mobile telecom operators are running the application test personnel to provide high quality applications among a large number of large-scale applications. However, there is a limit to the error detection in the manual test performed by the employed personnel there was. In addition, there is no objectified criterion for the error detection standard, and even when an error is detected, there is a problem in that it is difficult to cope with and solve the problem because accurate cause analysis is not performed.

The present invention has been proposed in order to solve the problems of the related art as described above, and it is an object of the present invention to verify whether an application is normally installed and operated for an application created based on a mobile open platform such as WIPI, The present invention has been made in view of the above problems, and it is an object of the present invention to provide a mobile application verification method capable of shortening an application development period by providing convenience for development, error grasping and correction of an application.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory and are not to be construed as limiting the invention as defined by the appended art. It will be possible.

A method for verifying a mobile application according to the present invention is a method for verifying an application of a terminal equipped with an application layer and a mobile open platform for providing an execution environment of the application layer, Acquiring process information of a target application; The terminal registering hooking process information based on the process information; And checking whether the target application is operating normally by hooking up the API function group and the system callback function group that the terminal sends and receive to the target application based on the hooking process information during the operation of the target application.

Preferably, the verification step may include a step in which, when a call for an API function is requested during operation of the target application, the terminal first calls a hooking API function based on a hooking API table address included in the hooking process information; Collecting resource usage information related to the hooking API function by the terminal; And allocating a resource by calling the API function by the terminal.

Preferably, when the return of the memory ID is requested after execution of the API function, the terminal collects resource release information related to the memory ID. And releasing resources by the terminal returning the memory ID.

Preferably, in the verification step, when a call of a system callback function is requested by an event occurrence during operation of the target application, the terminal transmits a hooking system callback function based on a hooking system callback registration address included in the hooking process information Calling first; Collecting event log information related to the hooking system callback function by the terminal; And the terminal may call the system callback function.

A computer-readable recording medium according to the present invention includes: instructions for requesting execution of a target application on a mobile open platform to obtain process information of the target application managed by the mobile open platform; Instructions for registering hooking process information based on the process information; And hooking an API function group and a system callback function group exchanged between the target application and the mobile open platform based on the hooking process information during operation of the target application to verify whether the target application is operating normally .

A terminal according to the present invention includes an application layer and a mobile open platform for providing an execution environment of the application layer, the application layer including: a target application developed based on the mobile open platform; And a verification agent that verifies whether the target application is operating normally by hooking API function groups and system callback function groups exchanged between the target application and the mobile open platform during operation of the target application.

Preferably, the verification agent registers a hooking API table address when the target application is activated. When the target application calls the API function from the target application during the operation of the target application, the verification agent registers a hooking API Function, an API operation verifying unit for collecting and monitoring resource usage information related to the hooking API function, and then calling the API function to the mobile open platform to allocate resources.

Preferably, the verification agent stores a hooking system callback registration address when the target application is operated, and when a call of the system callback function is requested from the mobile open platform by an event occurrence during the operation of the target application, And a system callback verification unit for calling the hooking system callback function on the basis of the system callback registration address, collecting and monitoring the event log information related to the hooking system callback function, and then calling the system callback function to the target application have.

A method of verifying a mobile application according to the present invention is a method of verifying an application of a terminal equipped with an application layer and a mobile open platform for providing an execution environment of the application layer, ; If the calling of the API function is requested from the target application, collecting and monitoring resource usage information related to the hooking API function by first calling the hooking API function based on the pre-registered hooking API table address; And, after the monitoring, invoking the API function requested by the API based on the API table address included in the process information of the mobile open platform to allocate the resource to the target application.
Preferably, when the return of the memory ID is requested after execution of the API function, collecting resource release information related to the memory ID is performed. And releasing the resource by returning the memory ID.
Preferably, when a call to the system callback function is requested by an event occurrence from the target application, the hooking system callback function is firstly called based on the registered hooking system callback registration address to obtain event log information related to the hooking system callback function Collecting and monitoring; And after the monitoring, calling the system callback function requested based on the system callback registration address included in the process information of the mobile open platform so that the system callback function is called to the target application and the event is processed Step < / RTI >
A method of verifying an application of a terminal equipped with an application layer of the present invention and a mobile open platform providing an execution environment of the application layer includes the steps of: driving a target application developed based on the mobile open platform; If a call to the system callback function is requested by the target application, the hooking system callback function is first called based on the pre-registered hooking system callback registration address to collect and monitor event log information related to the hooking system callback function step; And after the monitoring, calling the system callback function requested based on the system callback registration address included in the process information of the mobile open platform so that the system callback function is called to the target application and the event is processed .
A terminal device equipped with an application layer of the present invention and a mobile open platform providing an execution environment of the application layer includes a target application developed based on the mobile open platform; And a verification agent for activating the target application in cooperation with the mobile open platform, and for hooking up a group of API functions and a system callback function group exchanged between the target application and the mobile open platform to verify whether the target application operates normally .
Preferably, when the calling of the API function is requested from the target application, the verification agent first calls the hooking API function based on the address of the pre-registered hooking API table to collect and monitor resource usage information related to the hooking API function After the monitoring, the API function requested by the call may be called based on the API table address included in the process information of the mobile open platform to allocate the resource to the target application.
Preferably, when the system callback function call is requested by the target application from the target application, the verification agent first calls the hooking system callback function based on the registered hooking system callback registration address, The system callback function is called and the system callback function is called based on the system callback registration address included in the process information of the mobile open platform, May be invoked and cause the event to be processed.
The verification agent may collect resource release information related to the memory ID and release the resource after returning the memory ID if the memory ID is requested to be returned after execution of the API function.

According to the mobile application verification method of the present invention and the terminal to which the present invention is applied, it is possible to easily verify whether the application is normally installed and operated for an application created based on a mobile open platform such as WIPI.

In addition, it is possible to easily debug an application in the development process, thereby providing convenience in development, error detection and correction of the application, thereby shortening the application development period.

In addition, by accurately collecting resources such as a memory allocation amount, a number of file handles, and a number of timers used in an application executed in a terminal through API (Application Platform Interface) hooking, It is possible to prevent an abnormal operation that occurs due to not releasing resources at the time.

In addition, a log of an event operation of an application can be recorded by hooking a system callback function registered in an application.

1 is a configuration diagram of a terminal according to an embodiment of the present invention.
2 is a flowchart of a mobile application verification method according to an embodiment of the present invention.
Figures 3 and 4 are detailed flow charts illustrating some steps of Figure 2.
5 is a table illustrating process information used by a mobile application in an embodiment of the present invention.

Hereinafter, a mobile application verification method according to a preferred embodiment of the present invention and a terminal using the same will be described in detail with reference to the accompanying drawings.

1 is a configuration diagram of a terminal according to an embodiment of the present invention.

Referring to FIG. 1, a terminal according to an embodiment includes a terminal operating system 110, a mobile open platform 120, and an application layer 130 on which one or more applications are installed.

The terminal operating system 110 is system software for driving a terminal, and controls hardware such as an input unit, a display unit, a memory unit, and a microprocessor that constitute a physical configuration of the terminal.

The mobile open platform 120 is located between the hardware of the terminal and the application layer 130 and provides an environment in which various applications located in the application layer 130 can be executed on the terminal. The mobile open platform 120 provides application platform interface (API) functions for creating applications to content developers, such as WIPI, Android, and the like. Each application produced by a content developer performs a desired function through an API function group provided by the mobile open platform 120. According to the embodiment of the terminal, in particular, when the terminal is a smart phone type mobile device, the terminal operating system 110 and the mobile open platform 120 may be integrated into one layer.

The application layer 130 is a space where various applications implemented in an environment provided by the mobile open platform 120 are located. Each application installed in the application layer 130 is implemented under an execution environment provided by the mobile open platform 120. In particular, the application layer 130 includes a verification agent 131 for verifying the operation of the target application 134 and the target application 134 developed by the content developer based on the mobile open platform 120.

The verification agent 131 is driven together with the target application 134 to verify whether the installation, operation, and the like of the target application 134 are normally performed or not. The content developer creates the target application 134 based on a specific type of mobile open platform 120 and verifies the operation of the target application 134 using the verification agent 131 prior to release and corrects the error The target application 134 that has been verified after the process is uploaded can be uploaded to an application market such as an app store and sold.

The verification agent 131 performs hooking of API function groups and system callback function groups exchanged between the target application 134 and the mobile open platform 120 to verify whether the target application 134 operates normally. To this end, the verification agent 131 registers the hooking process information including the hooking API table address and the hooking system callback registration address at the start of the operation of the target application 134.

The verification agent 131 may include an API operation verifier 132 and a system callback verifier 133. The API operation verifying unit 132 first calls the hooking API function based on the address of the previously registered hooking API table when the API function calling from the target application 134 is requested during the operation of the target application 134, (E.g., information related to memory allocation) related to the application program, and then calls the original API function to the mobile open platform 120 to allocate resources to the target application 134. [ After the API function is executed, when the mobile open platform 120 requests return of the memory ID to release the resource, the API operation verification unit 132 of the verification agent 131 collects the resource release information related to the memory ID, And returns the pre-allocated memory ID to the target application 134 to release the resource.

The system callback verifying unit 133 checks the hooking system callback function based on the hooking system callback registration address when a call of the system callback function is requested from the mobile open platform 120 by the occurrence of the event during the operation of the target application 134 Collects and monitors the event log information related to the hooking system callback function, and calls the original system callback function to the target application 134.

According to one embodiment of the present invention, a content developer can know all events transmitted to the target application 134, and can identify items related to memory allocation, file resources, device resources, and timer resources used in the target application 134 have. Therefore, the content developer can easily debug the problem of the target application 134, thereby providing convenience in grasping and correcting problems, shortening the development period, and the like.

FIG. 2 is a flowchart of a mobile application verification method according to an embodiment of the present invention. As shown in FIG. 1, an application layer 130 and a mobile open platform 120 providing an execution environment of an application layer 130 are mounted And a method of verifying an application of a terminal having the same function.

The verification agent 131 installed in the terminal controls the target application 134 to be normally installed and operated and collects the result. In order to verify the target application 134 to be verified It implements hooking of system callback function group and application platform interface (API) function group.

The verification agent 131 requests the execution of the target application 134 to be verified at step S110 and the mobile open platform 120 activates the target application 134 at step S120, A handle of the target application 134 is requested and acquired (S130). Here, the handle is for the process information managed by the mobile open platform 120, and the process information includes the system callback registration address of the target application 134 and the API table address of the mobile open platform 120.

The verification agent 131 registers the hooking process information, that is, the hooking API table address and the system callback registration address, based on the process information obtained in step S130 (S140).

The verification agent 131 then determines whether the target application 134 and the mobile open platform 120 (or both), based on the hooking process information registered by the verification agent 131, (Step S150). In step S150, the API function group and the system callback function group are hooked to verify whether the target application 134 operates normally. In this case, when the API function is called from the target application 134 or the system callback function is systematically called from the mobile open platform 120 during the operation of the target application 134, the API information is included in the process information of the mobile open platform 120 The hooking API table address and the system callback registration address registered by the verification agent 131 are called instead of calling the API table address and the system callback registration address at step S150.

As described above, when the mobile application is verified, an API hooking technique and a system callback hooking technique that can easily find an error in the process operation of an application can be applied.

Through API hooking, it collects precise information about resources such as memory allocation, file handle count, and timer count used by mobile application executed in terminal, thereby preventing abnormal operation caused by not releasing resources at the end of the application have. In addition, by hooking a system callback function registered in an application, a log of an event operation of the application can be recorded.

Figures 3 and 4 are detailed flow charts illustrating some steps of Figure 2.

FIG. 3 illustrates an API function calling method in the verification step of S150 shown in FIG.

When the target application 134 starts to operate, when the terminal calls the API function related to the resource through the API table hooked by the verification agent 131, the actual API function intended by the target application 134 is called The hooking API function registered by the verification agent 131 is called. The verification agent 131 collects the resource usage information required for the verification and then calls the original API function to the mobile open platform 120 so that the memory allocation, file resource, device resource, Resource usage information on resource usage, and the like can be collected. The collection of relevant information is valid unless the resources used during the life cycle of the target application 134 are released.

Referring to FIG. 3, when a call of the API function is requested (S210) during the operation of the target application 134, the verification agent 131 first calls the hooking API function based on the registered hooking API table address (S220) The resource usage information related to the API function is collected, stored, and monitored by the user (S230). After the information collection is completed, the verification agent 131 calls the native API function to the mobile open platform 120 to allocate resources to the target application 134 (S240).

After the execution of the corresponding API function, the mobile open platform 120 requests the memory ID to be returned (S250). The validation agent 131 hooks the resource request and collects resource release information related to the memory ID (S260) And returns the memory ID to the resource manager 134 so that the previously allocated resource can be released (S270).

FIG. 4 illustrates a system callback invocation method in the verification step of S150 shown in FIG.

If the user generates an event in hardware through an input unit such as a touch panel or a keypad, if the verification agent 131 does not operate, the mobile open platform 120 calls an appropriate system callback function to process the event . However, in one embodiment, since the verification agent 131 changes the process information of the target application 134 at the start of the target application 134, the hooking system callback function registered in the verification agent 131 at the time of the event Is called. At this time, the verification agent 131 records log information about the event, and calls the system callback function (event handler) originally registered in the target application 134.

4, when an event is generated during operation of the target application 134 (S310) and a call of the system callback function is requested (S320) from the mobile open platform 120, the verification agent 131 registers the registered hooking system The hooking system callback function is first called (S330) on the basis of the callback registration address, and event log information related to the hooking system callback function is collected and recorded (S340). When logging is completed, the verification agent 131 calls the original system callback function to the target application 134 so that the event can be processed (S350).

The method of the present invention as described above may be embodied as a program and stored in a computer-readable recording medium (such as a CD-ROM, a RAM, a ROM, a floppy disk, a hard disk, or a magneto-optical disk). Such a process can be easily carried out by those skilled in the art and will not be described in detail.

A computer readable recording medium according to an exemplary embodiment of the present invention requests the execution of a target application 134 by a mobile open platform 120 to acquire process information of a target application 134 managed by the mobile open platform 120 A command for registering the hooking process information based on the process information and an API function to be exchanged between the target application 134 and the mobile open platform 120 based on the hooking process information during operation of the target application 134, Group and system callback function groups to verify whether the target application 134 is operating normally.

5 is a table illustrating process information used by a mobile application in an embodiment of the present invention.

When the applications (application A, application B, and application C) are activated, the mobile open platform 120 generates a process information structure of the applications as shown in FIG. At this time, the generated process information includes the API table address T110, the system callback registration addresses T120 and T130, and the binary region information T140.

In the mobile open platform 120, a data type of the API table is defined as follows.

"typedef struct {

TKnlApiLinkTable * pKnlApiLinkTable;

       // kernel API function set

TGrpApiLinkTable * pGrpApiLinkTable;

      // Graphics API function set

... ...

} TApiLinkTable; "

At this time, the API table address (T110) used in the application is an address value of a variable defined globally in the mobile open platform (120).

"TApiLinkTable * g_ppApiLinkTable = (TApiLinkTable *) & g_ApiLinkTable_TopLevel"

When an application is to be built in the terminal, a global variable of the API table address is generated in a certain region of the binary specified by the binary region information T 140 of the installed application.

An API table implemented by the verification agent 131 and a hooking method of the system callback after the process information structure of the application is generated in the mobile open platform 120 will be described below.

When the validation agent 131 obtains the handle of the application in the mobile open platform 120, it declares the matching structure matching the process information as follows.

"/ * platform TPress information * /

typedef struct tag_AGENTTPROCESS {

char * apitableaddr;

    int systemA;

    int systemB;

} * PAGENTTPROCESS; "

In order to copy the address of the API table used in the mobile open platform 120, the validation agent 131 declares an API table data type variable used in the mobile open platform 120 as follows.

"TApiLinkTable g_HookApiLinkTable_TopLevel = {

(TKnlApiLinkTable *) & g_HookKnlApiLinkTable_GrLevel,

// kernel API function set dummy structure variable

(TGrpApiLinkTable *) & g_HookGrpApiLinkTable_GrLevel,

// Graphics API function set dummy structure variable

...

}; "

The verification agent 131 also "TYPECAST" the handle of the application acquired from the mobile open platform 120 to the "tag_AGENTTPROCESS" variable as follows.

"PAGENTTPROCESS pProc = (PAGENTTPROCESS) appHandleId;"

Then, the verification agent 131 copies the API table address provided by the mobile open platform 120 to the variable "g_HookApiLinkTable_TopLevel ".

"memcpy (& g_HookApiLinkTable_TopLevel, pProc-> apitableaddr, sizeof (TApiLinkTable));"

When copying is performed in this manner, the API function of the mobile open platform 120 stores in "g_HookApiLinkTable_TopLevel". Although there are many API functions in the mobile open platform 120, the verification agent 131 only hooks API functions required for verification, and therefore only the API functions required are modified as follows.

"g_HookApiLinkTable_TopLevel. pfnMC_knlAlloc = &HOOK_MC_knlAlloc;"

For example, the function "HOOK_MC_knlAlloc" is a hooking API function defined by the verification agent 131.

When API functions to be hooked are assigned as described above, API hooking is completed when "g_HookApiLinkTable_TopLevel" is substituted into the API table address of the process information and the hooking API table address is registered as follows.

"* (pProc-> apitableaddr) = &g_HookApiLinkTable_TopLevel;"

On the other hand, the system callback hooking method is completed when the hooking system callback registration address defined by the verification agent 131 is substituted into the system callback registration address of the process information as follows.

"pProc-> systemA = (M_Uint32) Hook systemA;

pProc-> systemB = (M_Uint32) Hook systemB;

The verification agent 131 operates according to the life cycle of the process after the target application 134 is executed in the terminal and the verification agent 131 is activated during the operation of the verification agent 131, It is possible to prevent an application error that occurs due to the failure of the target application 134 to release the resource normally.

In addition, it is possible to inform the developer about the application error through the recording of the event log information, and by recreating the error precisely, the recall rate for the error operation is increased, thereby making it possible for the developer to correct errors and to make good quality contents.

While the present invention has been described in connection with what is presently considered to be practical exemplary embodiments, it is to be understood that the invention is not limited to the disclosed embodiments, but, on the contrary, You will understand.

Therefore, it should be understood that the above-described embodiments are provided so that those skilled in the art can fully understand the scope of the present invention. Therefore, it should be understood that the embodiments are to be considered in all respects as illustrative and not restrictive, The invention is only defined by the scope of the claims.

The mobile application verification method according to the present invention and the terminal using the same can easily debug the mobile application, so that the individual user can analyze the exact cause of the error in the process of developing the mobile application as a developer, Thereby reducing the cost, effort, and time required for application development. In addition, since the mobile application can be easily verified by objective criteria before uploading it to the open application market and releasing the mobile application, a high-quality mobile application can be created in a short time at a low cost .

110: terminal operating system
120: Mobile Open Platform
130: Application layer
131: Verification Agent
132: API operation verification unit
133: system callback verification unit
134: Target Application

Claims (8)

1. An application verification method for a terminal equipped with an application layer and a mobile open platform for providing an execution environment of the application layer,
Driving a target application developed based on the mobile open platform;
If the calling of the API function is requested from the target application, collecting and monitoring resource usage information related to the hooking API function by first calling the hooking API function based on the pre-registered hooking API table address;
After the monitoring, calling the API function requested to be called based on the API table address included in the process information of the mobile open platform to allocate resources to the target application;
When a call of a system callback function for the target application is requested from the mobile open platform according to an event from the hardware of the terminal, the hooking system callback registration address is registered for each event generated from the hardware of the terminal, Collecting and monitoring event log information related to a hooking system callback function by first calling a system callback function; And
After the monitoring, invoking the system callback function requested based on the system callback registration address included in the process information of the mobile open platform so that the system callback function is called to the target application and the event is processed / RTI >
Collecting resource release information related to the memory ID if the memory ID is requested to be returned after execution of the API function, and returning the memory ID and releasing the resource. delete delete 1. An application verification method for a terminal equipped with an application layer and a mobile open platform for providing an execution environment of the application layer,
Driving a target application developed based on the mobile open platform;
When a call of a system callback function for the target application is requested from the mobile open platform according to an event from the hardware of the terminal, the hooking system callback registration address is registered for each event generated from the hardware of the terminal, Collecting and monitoring event log information related to a hooking system callback function by first calling a system callback function; And
After the monitoring, invoking the system callback function requested based on the system callback registration address included in the process information of the mobile open platform so that the system callback function is called to the target application and the event is processed / RTI >
Further comprising collecting resource release information related to the memory ID when the return of the memory ID is requested after execution of the API function, and returning the memory ID and releasing the resource. [Claim 5 is abandoned upon payment of registration fee.] 1. A terminal device equipped with an application layer and a mobile open platform for providing an execution environment of the application layer,
The application layer comprises:
A target application developed based on the mobile open platform; And
And a verification agent for activating the target application in cooperation with the mobile open platform and for verifying whether the target application is operating normally by hooking an API function group and a system callback function group exchanged between the target application and the mobile open platform In addition,
The verification agent comprising:
When a call of a system callback function for the target application is requested from the mobile open platform according to an event from the hardware of the terminal, the hooking system callback registration address is registered for each event generated from the hardware of the terminal, The system callback function is first called to collect and monitor the event log information related to the hooking system callback function, and after the monitoring, the system callback function registered in the system callback registration address included in the process information of the mobile open platform To invoke the system callback function in the target application to cause the event to be processed,
The verification agent comprising:
If the memory ID is requested to be returned after execution of the API function, collects resource release information related to the memory ID, returns the memory ID, and releases the resource. delete delete delete

Images