KR101260773B1 - Apparatus and method for communicating interstitial applications - Google Patents

Apparatus and method for communicating interstitial applications Download PDF

Info

Publication number
KR101260773B1
KR101260773B1 KR1020120095572A KR20120095572A KR101260773B1 KR 101260773 B1 KR101260773 B1 KR 101260773B1 KR 1020120095572 A KR1020120095572 A KR 1020120095572A KR 20120095572 A KR20120095572 A KR 20120095572A KR 101260773 B1 KR101260773 B1 KR 101260773B1
Authority
KR
South Korea
Prior art keywords
application
touch
touch event
information
event information
Prior art date
Application number
KR1020120095572A
Other languages
Korean (ko)
Inventor
남진하
Original Assignee
주식회사 안랩
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 주식회사 안랩 filed Critical 주식회사 안랩
Priority to KR1020120095572A priority Critical patent/KR101260773B1/en
Application granted granted Critical
Publication of KR101260773B1 publication Critical patent/KR101260773B1/en

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
    • G06F11/3006—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/03—Arrangements for converting the position or the displacement of a member into a coded form
    • G06F3/041—Digitisers, e.g. for touch screens or touch pads, characterised by the transducing means
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Software Systems (AREA)
  • Computing Systems (AREA)
  • Quality & Reliability (AREA)
  • Human Computer Interaction (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mathematical Physics (AREA)
  • Telephone Function (AREA)

Abstract

PURPOSE: An apparatus for communicating between applications and a method thereof are provided to check a state of an application which is called in connecting between different applications through a touch event. CONSTITUTION: An apparatus for communicating between applications includes a main communication device(100) installed in a main application and a calling communication device(150) installed in a calling application. The main communication device includes a first interface unit(102) performing communications with the calling application, a generating unit(104) generating touch event information provided in calling and executing the calling application, a touch information reading unit(106) reading touch information corresponding to the touch event information, and a comparing and analyzing unit(108) checking a state of the calling application by comparing read touch information with the touch event information. The calling communication device installed in the calling application includes a second interface unit(152) performing communication with the first interface unit of the main application, an execution checking unit(154) checking an operation according to a received command, and a touch event generating unit(156) generating a touch event corresponding to the touch event information according to an execution result of the execution checking unit. [Reference numerals] (102) First interface unit; (104) Generating unit; (106) Touch information reading unit; (108) Comparing and analyzing unit; (152) Second interface unit; (154) Execution checking unit; (156) Touch event generating unit; (AA) Touch action occurs

Description

APPARATUS AND METHOD FOR COMMUNICATING INTERSTITIAL APPLICATIONS

The present invention relates to an application-to-application communication, and more particularly, by providing touch event information and instructions when calling and executing an application, the execution state of the called application can be grasped through monitoring of the touch action, and the called application The present invention relates to an inter-application communication apparatus and a method capable of communicating with a service provider.

Recently, with the widespread use of smart phones, personal digital assistants (PDAs), and WiBro terminals, these portable terminals are becoming a necessity for modern life. Many people use mobile devices to talk about each other, exchange information, and exchange business-critical information through voice and data communication.

However, as the hardware functions of the portable terminal have been expanded and advanced, various applications (applications) performed in the portable terminal have been made. In addition, in order to provide convenience to the user, it supports interworking between applications.

Interworking between applications can be divided into two types. The first method is to communicate with a specific protocol between applications, and the second method is to use a web browser page.

On the other hand, with the recent development of applications, research on various communication methods between applications is in progress.

In "LG U + (Patent No. 10-2010-0115194)" Mobile communication terminal providing an application service with a browsing function and a service providing method thereof ", the user interface is displayed on the user interface display area of the display unit. A technique for displaying a web page in a browser display area of a display unit by executing a browser on a web platform according to a call of the execution unit is described.

As a result of the above research, it is an object of the present invention to provide an inter-application communication apparatus and method that can check the state of an application called when interworking between different applications through a touch event.

In addition, the present invention provides an apparatus and method for communication between applications that can control the execution of an application that is exchanged and called through a touch event when interworking between applications.

The objects of the present invention are not limited to the above-mentioned objects, and other objects not mentioned can be clearly understood by those skilled in the art from the following description.

According to an aspect of the present invention, an inter-application communication method according to an embodiment of the present invention is a communication method between at least two or more applications that are executed in a device operated by a touch, and in one application, at least one or more other applications. At least one touch event information is transmitted when an execution request is performed, and communication between the at least one application and the at least one other application is performed using touch information generated according to the touch event information.

The inter-application communication method according to an embodiment of the present invention is characterized by transmitting a command corresponding to each of the touch event information to the at least one other application when the execution request is made.

In the application-to-application communication method according to an embodiment of the present invention, the command is characterized in that the value of the malicious code scan result when the application that is requested to execute in any one application is a malicious code monitoring application.

In the application-to-application communication method according to an embodiment of the present invention, the one application reads a touch operation at a preset time interval and controls the operation by comparing the read touch operation with the touch event information. It is done.

According to another aspect of the present invention, an inter-application communication device according to an embodiment of the present invention is at least two or more application-to-application communication devices installed in a device operated by a touch, and the touch event when the execution request of the second application is executed in the first application. A generation unit for generating information and providing the generated information to the second application, a touch event generation unit generating a touch event corresponding to the touch event information according to an execution state of the second application, and reading the touch information in the device. The touch information reader may include a comparison analyzer configured to determine an execution state of the calling application by comparing the read touch information with the touch event information.

In the inter-application communication apparatus according to an exemplary embodiment of the present disclosure, if the touch information is not read from the touch information reader for a preset time, the comparison analyzer stops providing a service by the first application.

In the inter-application communication apparatus according to an embodiment of the present disclosure, the comparison analyzer may retransmit the touch event information to the second application when the touch information is not read from the touch information reader for a preset time. .

In the inter-application communication apparatus according to an embodiment of the present invention, the generation unit may include touch event information in each of a command for executing the second application and a result value according to an execution result of the command, and provide the second application to the second application. It is characterized by.

An execution check unit for extracting a result value by executing the second application in accordance with the command in the inter-application communication device according to an embodiment of the present invention, wherein the touch event generating unit, the touch event corresponding to the extracted result value The touch event may be generated using the information.

According to another aspect of the invention, the inter-application communication device according to an embodiment of the present invention generates the touch event information when there is a request for execution of the second application from the first application and the touch event information to the second application A generation unit provided to the; a touch information reading unit reading the touch information; and when the touch information is read, a comparison of determining an execution state of the second application through comparison between the read touch information and the touch event information. It may include an analysis unit.

In the inter-application communication apparatus according to an embodiment of the present invention, the comparison analyzer stops providing a service by the first application when the touch information is not read from the touch information reader for a preset time.

In the inter-application communication apparatus according to an embodiment of the present disclosure, the comparison analyzer may retransmit the touch event information to the second application when the touch information is not read from the touch information reader for a preset time. .

In the inter-application communication apparatus according to an embodiment of the present invention, the generation unit may include touch event information in each of a command for executing the second application and a result value according to an execution result of the command, and provide the second application to the second application. It is characterized by.

According to another aspect of the invention, the inter-application communication apparatus according to an embodiment of the present invention is the interface unit for receiving the touch event information when the execution request of the first application, and the execution state of the second application received the execution request And a touch event generator for generating a touch event corresponding to the touch event information, wherein the first application determines an execution state of the second application through comparison between the touch information and the touch event information according to the touch event. It is characterized by judging.

In the inter-application communication apparatus according to an embodiment of the present disclosure, the interface unit may include data including touch event information in each of a command for executing the second application from the first application and a result value according to an execution result of the command. In this case, the inter-application communication apparatus according to the embodiment of the present invention includes an execution check unit for extracting a result value by executing the second application according to the command, wherein the touch event generation unit, the extracted result value After selecting the touch event information corresponding to the characterized in that to generate a touch event based on the selected touch event information.

According to another aspect of the present invention, an inter-application communication method according to an embodiment of the present invention is a communication method between at least one or more applications executed in a device capable of performing a touch operation, wherein the second application is executed by the first application. Generating and transmitting touch event information to the second application when called, reading the touch information in the device, and comparing the read touch information with the touch event information. And determining an execution state.

The inter-application communication method according to an embodiment of the present invention may further include retransmitting the touch event information to the second application when the touch information is not read for the preset time.

The inter-application communication method according to an embodiment of the present invention may further include terminating the first application when the touch information is not read for the preset time.

According to another aspect of the invention, the inter-application communication method according to an embodiment of the present invention is a communication method between the first and second applications in the device capable of performing a touch operation, the first application to the second application; Generating a command to execute and touch event information for each result value according to the execution of the command, transmitting the command and touch event information for each result value to the second application, and using the command Executing a second application; extracting an execution result value of the second application; selecting touch event information according to the execution result value to generate a touch event; and touch information according to the touch event. Read the second apple based on the read touch information It may comprise determining the status of execution of indications.

In the application-to-application communication method according to an embodiment of the present invention, the first application is a web browser providing a financial transaction service, and the second application is a system monitoring service application executed by a request of the web browser. do.

The inter-application communication method according to an embodiment of the present invention may include retransmitting the command and touch event information for each result value to the second application when the touch information is not read for a preset time.

An inter-application communication method according to an embodiment of the present invention may include terminating the first application when the touch information is not read for a preset time.

According to the present invention, communication between applications can be performed through a touch event, so that not only the execution state of the called application can be confirmed, but also various information can be exchanged between applications.

1 is a block diagram illustrating an inter-application communication apparatus according to an embodiment of the present invention;
2 is a flowchart illustrating an inter-application communication process according to an embodiment of the present invention;
3 is a flowchart illustrating an inter-application communication process according to another exemplary embodiment of the present invention.

Objects and effects of the present invention, and technical configurations for achieving them will be apparent with reference to the embodiments described below in detail with the accompanying drawings. In the following description of the present invention, a detailed description of known functions and configurations incorporated herein will be omitted when it may make the subject matter of the present invention rather unclear. The following terms are defined in consideration of the functions of the present invention, and may be changed according to the intentions or customs of the user, the operator, and the like.

The present invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. The present embodiments are merely provided to complete the disclosure of the present invention and to fully inform the scope of the invention to those skilled in the art, and the present invention is defined by the scope of the claims. It will be. Therefore, the definition should be based on the contents throughout this specification.

The technical gist of the present invention relates to an inter-application communication apparatus and method capable of checking an execution state of an application called when inter-application interworking. Hereinafter, with reference to the accompanying drawings will be described for this technical gist.

1 is a block diagram illustrating an inter-application communication apparatus according to an exemplary embodiment of the present invention.

Prior to the description, an application calling an arbitrary application is defined as a main application, and any application is defined as a calling application.

In addition, the terminal on which such an application is installed means a device operated by a touch, and examples thereof include a smart phone, a tablet PC, a smart TV, but are not limited thereto.

As shown in FIG. 1, the inter-application communication device may be largely composed of a main communication device 100 installed in a main application and a call communication device 150 installed in a calling application.

The main communication device 100 includes a first interface unit 102 for performing communication with a calling application, a generation unit 104 for generating touch event information provided when calling and executing a calling application, and touch event information. The touch information reading unit 106 reading out the corresponding touch information and the comparison analyzing unit 108 checking the state of the calling application through the comparison between the read touch information and the touch event information may be included.

The main communication device 100 may be separately installed and interworked with the main application, or may be installed when the main application is installed.

The generation unit 104 of the main communication device 100 may generate at least one touch event information for allowing a predetermined location to be touched. Here, the touch event information may include touch coordinate information to which at least one location is touched.

In addition, the generation unit 104 may generate a command for each touch event information when generating the touch event information. Here, the command is a command executed in the calling application, and examples thereof include but are not limited to checking version information of the calling application, executing status check, and malicious code checking.

On the other hand, the generation unit 104 may generate different touch event information for each result value according to the execution of the command. That is, when there are a plurality of result values when the command is executed, different touch event information may be generated for each result value.

The touch event information generated by the generation unit 104 and the result value according to the command may be transmitted to the calling application through the first interface unit 102.

Meanwhile, the call application receiving the command and the touch event information may generate a touch event corresponding to the touch event information by using the call communication device 150 when execution of the command is completed. Accordingly, the terminal performs a touch operation based on a touch event, and touch information can be generated according to the touch operation.

The touch information reading unit 106 reads the touch information generated according to the touch event occurrence of the calling application and provides it to the comparison analyzing unit 108. That is, the touch information reading unit 106 reads the touch information when a preset time interval or touch operation occurs and provides it to the comparison analyzing unit 108.

If the touch information is not read for a preset time after providing the touch event information, the touch information reader 106 may inform the comparison analyzer 108 of this. Accordingly, the comparison analyzer 108 may control the execution of the main application or provide the call communication device 150 with the result value according to the touch event information and the command.

The comparison analysis unit 108 may check an execution state of a corresponding command by comparing the touch information with the touch event information, and determine the subsequent execution of the main application according to the execution state. That is, the comparison analyzer 108 may stop using the service using the main application, stop execution of the main application, or retransmit the touch event information and the command if there is a mismatch between the touch information and the touch event information.

The call communication device 150 in the call application includes a second interface unit 152 for performing communication with the first interface unit 102 of the main application, and checking an operation according to a command received from the main communication device 100. The execution check unit 154 and the touch event generator 156 for generating a touch event corresponding to the touch event information according to the execution result of the execution unit check unit 154 may be included.

The second interface unit 152 may communicate with the first interface unit 102 to receive the result value and the touch event information according to the command from the main application.

The execution checker 154 may check whether the received command is completed based on the execution result of the calling application according to the request of the main application.

In addition, the execution checker 154 may provide an execution result value for the command to the touch event generator 156. For example, if the command received from the main application checks the version of the calling application, the execution checker 154 checks the version information of the calling application and outputs a value of "1" if it is the latest version. In this case, a value of "0" can be output. Here, the generation unit 104 in the main communication device 100 generates different touch event information for each execution result value and provides it to the call communication device 150 of the calling application.

The touch event generator 156 may generate a touch event using touch event information corresponding to an execution result value provided from the execution checker 154. Such a touch event means generating a touch at at least one location.

As described above, in the exemplary embodiment of the present invention, for example, the touch event information and the execution result value of the command are provided to the calling application. However, when checking the execution completion state of the calling application, only the touch event information is called. Can be provided to

In addition, in the exemplary embodiment of the present invention, the main application communicates with one calling application. For example, the same may be applied when the main application calls one or more applications. That is, the main application transmits at least one touch event information when the execution request for at least two other applications is executed, and after the touch event information is transmitted, communication between the main application and at least one other application is performed through monitoring of the touch information. Can be.

In addition, when the main application requests execution of at least two or more applications, the touch event information for each result value according to the execution of the command may be transmitted.

The operation of the communication device having the above configuration will be described with reference to FIG.

2 is a flowchart illustrating an inter-application communication process according to an exemplary embodiment of the present invention.

As shown in FIG. 2, when a web browser application requests execution by calling another application, that is, a calling application, the main communication device 100 generates touch event information using the generation unit 104 (S200). Then, the execution of the calling application is requested using the touch event information (S202). The execution request and the touch event information in the web browser application are provided through the first interface unit 102.

The calling application is executed according to the execution request of the web browser application (S204), and the execution checker 154 determines whether execution of the calling application is completed (S206).

As a result of the determination in S206, when execution is completed, the execution check unit 154 generates information (S208) indicating the completion of execution and provides it to the touch event generation unit 156. Accordingly, the touch event generator 156 generates a touch event corresponding to the touch event information (S210). That is, the touch event generation unit 156 generates a touch event such that a touch occurs at a position corresponding to the touch event information, and thus touch information is generated in a device that executes an application.

Thereafter, the touch information reading unit 106 of the main communication device 100 interworking with the web browser application reads the touch information (S212) and then provides it to the comparison analyzing unit 108.

The comparison analysis unit 108 determines whether the correspondence is made by comparing the touch event information with the read touch information (S214).

As a result of the determination in S214, if it matches, the web browser application keeps running and provides a service according to the user's input (S216). Otherwise, the web browser application stops executing (S218).

On the other hand, as a result of the determination in S206, if execution is not completed, the execution checker 154 checks the execution state of the calling application for a preset time.

In an embodiment of the present invention, a state in which execution of a calling application is completed for a preset time is described as an example. However, when the execution of the calling application is not completed for a preset time, the comparison analyzer 108 of the main communication device 100 is performed. Since the execution of the calling application is not completed, the execution of the web browser application may be stopped or the touch event information generated through the generation unit 104 may be retransmitted to the calling application. The number of retransmissions may be set in the main communication device 100, and the time for checking whether execution of the calling application is completed may be set by the call communication device 150.

In addition, in the embodiment of the present invention, the web browser application may include a payment service, and the calling application may include a vaccine and a monitoring service that monitor the system during the payment service, but are not limited thereto.

In the above description, for example, the touch event information is provided to check an execution state of the calling application. However, the touch event information and the command may be transmitted together. This will be described with reference to FIG.

3 is a flowchart illustrating an inter-application communication process according to another exemplary embodiment of the present invention.

As shown in FIG. 3, when there is a request for execution of another application (hereinafter referred to as a calling application) after an application (hereinafter, referred to as a main application) is executed (S300), the main communication device interworking with the main application The generation unit 104 of 100 generates a command and corresponding touch event information (S302). That is, the generator 104 may generate different touch event information according to the execution result value of the command, or may generate different touch event information for each of the plurality of commands.

Subsequently, the generation unit 104 of the main communication device 100 requests execution of the calling application through the first interface unit 102, and provides touch event information for each execution result value according to the command to the calling application. S304).

Accordingly, the calling application is executed (S306), the execution check unit 154 of the call communication device 150 extracts the execution result value according to the command (S308).

The execution checker 154 provides an execution result value to the touch event generator 156, and the touch event generator 156 selects touch event information according to the execution result value (S310) and corresponds to the selected touch event information. A touch event is generated (S312). That is, the touch event generator 156 causes a touch to occur at a position corresponding to the touch event information.

Accordingly, the touch information reading unit 106 of the main communication device 100 reads the touch information (S314) and provides the read touch information to the comparison analyzing unit 108.

The comparison analysis unit 108 extracts the state of the calling application according to the execution result of the command by using the touch event information and the read touch information (S316).

Then, the comparison analyzer 108 controls the operation of the main application according to the state of the calling application (S318).

An example of applying the operation process of the communication device as described above will be described below.

First, the main application is a web browser application that provides a payment service, the calling application is a monitoring application for monitoring the system when the payment service is in progress, and when the monitoring application is called according to the execution of the web browser application, it is linked with the web browser application. For example, the main device 150 transmits a command for checking version information of the monitoring application and touch event information to the monitoring application.

For example, the A touch event information is generated when the version information is the latest version, and the B touch event information is generated when the version information is not the latest version.

When the web browser application is executed to provide a payment service, the A and B touch event information is transmitted to the monitoring application according to the command for checking the version information of the monitoring application and the execution result of the command.

Accordingly, the execution check unit 154 of the call communication device 150 interoperating with the monitoring application receives a result value according to the command from the monitoring application and touches the A or B touch event information based on the received execution result value. The event generator 156 is provided. That is, when the result value according to the command is the latest version, the A touch event information is provided to the touch event generator 156, and when the result value is not the latest version, the B touch event information is provided to the touch event generator 156. .

Accordingly, the touch event generating unit 156 generates an A touch event corresponding to the A touch event information, and the touch information reading unit 106 of the main communication device 100 reads the touch information corresponding to the A touch event. After providing it to the comparison analysis unit 108. The comparison analyzing unit 108 recognizes that the monitoring application is the latest version based on the touch information according to the A touch event, and thus provides a payment service.

Meanwhile, the touch event generating unit 156 generates a B touch event corresponding to the B touch event information, and the touch information reading unit 106 of the main communication device 100 reads the touch information corresponding to the B touch event. It is then provided to the comparison analysis unit 108. The comparison analyzer 108 recognizes that the monitoring application is not the latest version based on the touch information according to the B touch event, and thus stops the payment service or informs the user that the information of the monitoring application is not the latest version.

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. For example, those skilled in the art can change each component according to the field of application, or combine or substitute the disclosed embodiments in a form that is not clearly disclosed in the embodiments of the present invention, but this is also within the scope of the present invention. It is not. Therefore, the above-described embodiments are to be considered in all respects as illustrative and not restrictive, and such modified embodiments should be included in the technical spirit described in the claims of the present invention.

100: main communication device 102: first interface unit
104: generating unit 106: touch information reading unit
108: comparison analysis unit 150: call communication device
152: second interface unit 154: execution check unit
156: touch event generator

Claims (22)

A communication method between at least two applications executed in a device operated by a touch,
At least one touch event information is transmitted when a request for execution of at least one other application is executed in any one application, and communication between the at least one application and the at least one other application through monitoring of a touch operation generated in the device Characterized in that
How to communicate between applications.
The method of claim 1,
The command corresponding to each of the touch event information is transmitted to the at least one other application when the execution request is made.
How to communicate between applications.
The method of claim 2,
The command may be a result of malicious code inspection when the application that is requested to execute in any one application is a malicious code monitoring application.
How to communicate between applications.
The method of claim 1,
The one application reads a touch operation at a predetermined time interval and controls the operation by comparing the read touch operation with the touch event information.
How to communicate between applications.
A communication device between at least two applications installed in a device operated by a touch,
A generation unit configured to generate touch event information and provide the second application with the second application when a first application executes the execution of the second application;
A touch event generator for generating a touch event corresponding to the touch event information according to an execution state of the second application;
A touch information reader for reading touch information in the device;
And a comparison analyzer configured to determine an execution state of the second application by comparing the read touch information with the touch event information.
Inter-application communication device.
The method of claim 5, wherein
The comparative analysis unit,
If the touch information is not read from the touch information reading unit for a preset time, the service provision by the first application is stopped.
Inter-application communication device.
The method of claim 5, wherein
The comparative analysis unit,
The touch event information is retransmitted to the second application when the touch information is not read from the touch information reader for a preset time.
Inter-application communication device.
The method of claim 5, wherein
The generation unit may include the touch event information in each of a command for executing the second application and a result value according to an execution result of the command, and provide the touch event information to the second application.
Inter-application communication device.
The method of claim 8,
An execution check unit for extracting a result value by executing the second application according to the command;
The touch event generating unit may generate a touch event by using touch event information corresponding to the extracted result value.
Inter-application communication device.
A generation unit generating touch event information and providing the touch event information to the second application when a request for execution of the second application is received from a first application;
A touch information reader for reading touch information;
When the touch information is read, a comparison analyzer configured to determine an execution state of the second application through comparison between the read touch information and the touch event information.
Inter-application communication device.
11. The method of claim 10,
The comparative analysis unit,
If the touch information is not read from the touch information reading unit for a preset time, the service provision by the first application is stopped.
Inter-application communication device.
11. The method of claim 10,
The comparative analysis unit,
The touch event information is retransmitted to the second application when the touch information is not read from the touch information reader for a preset time.
Inter-application communication device.
11. The method of claim 10,
The generation unit may include the touch event information in each of a command for executing the second application and a result value according to an execution result of the command, and provide the touch event information to the second application.
Inter-application communication device.
An interface unit configured to receive touch event information when the execution request of the first application is performed;
And a touch event generator for generating a touch event corresponding to the touch event information according to the execution state of the second application that has received the execution request.
The first application may determine an execution state of the second application through comparison between the touch information according to the touch event and the touch event information.
Inter-application communication device.
15. The method of claim 14,
The interface unit receives data including touch event information in each of a command for executing the second application and a result value according to an execution result of the command from the first application,
The communication device comprising:
An execution check unit for extracting a result value by executing the second application according to the command;
The touch event generator,
Selecting touch event information corresponding to the extracted result value and generating a touch event based on the selected touch event information
Inter-application communication device.
A communication method between at least one or more applications executed in a device capable of performing a touch operation,
Generating touch event information when the second application is called by the first application and then transmitting the touch event information to the second application;
Reading touch information in the device;
Determining an execution state of the second application through comparison between the read touch information and the touch event information.
How to communicate between applications.
17. The method of claim 16,
Retransmitting the touch event information to the second application when the touch information is not read for the preset time.
How to communicate between applications.
17. The method of claim 16,
Terminating the first application if the touch information is not read for the preset time.
How to communicate between applications.
A communication method between first and second applications in a device capable of performing a touch operation,
Generating a command for executing the second application in the first application and touch event information for each result value according to the execution of the command;
Transmitting the touch event information for each of the command and the result value to the second application;
Running the second application using the command;
Extracting an execution result value of the second application;
Generating touch events by selecting touch event information according to the execution result value;
Reading touch information according to the touch event and determining an execution state of the second application based on the read touch information;
How to communicate between applications.
The method of claim 19,
The first application is a web browser providing a financial transaction service, and the second application is a system monitoring service application executed by a request of the web browser.
How to communicate between applications.
The method of claim 19,
Retransmitting the command and touch event information for each result value to the second application when the touch information is not read for a preset time.
How to communicate between applications.
The method of claim 19,
Terminating the first application if the touch information is not read for a preset time;
How to communicate between applications.
KR1020120095572A 2012-08-30 2012-08-30 Apparatus and method for communicating interstitial applications KR101260773B1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
KR1020120095572A KR101260773B1 (en) 2012-08-30 2012-08-30 Apparatus and method for communicating interstitial applications

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
KR1020120095572A KR101260773B1 (en) 2012-08-30 2012-08-30 Apparatus and method for communicating interstitial applications

Publications (1)

Publication Number Publication Date
KR101260773B1 true KR101260773B1 (en) 2013-05-06

Family

ID=48665499

Family Applications (1)

Application Number Title Priority Date Filing Date
KR1020120095572A KR101260773B1 (en) 2012-08-30 2012-08-30 Apparatus and method for communicating interstitial applications

Country Status (1)

Country Link
KR (1) KR101260773B1 (en)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2010519663A (en) 2008-03-04 2010-06-03 アップル インコーポレイテッド Touch event model for web pages

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2010519663A (en) 2008-03-04 2010-06-03 アップル インコーポレイテッド Touch event model for web pages

Similar Documents

Publication Publication Date Title
KR101251439B1 (en) Automatical test system and method performance of smart phone using android debug bridge interface
CN111427803B (en) Automated random test method, apparatus, computer device and medium
CN104636924B (en) Secure payment method, server and system
US9459937B2 (en) Method for using shared device in apparatus capable of operating two operating systems
EP2784672A1 (en) Method for processing information, browsing device and storage medium
CN105354118B (en) Automatic test approach, the apparatus and system of intelligent terminal
CN108305065B (en) Data processing method, terminal equipment and data processing system
CN112631910A (en) Front-end testing method and device, computer equipment and storage medium
CN111866885A (en) Verification information sharing method and device and electronic equipment
KR20130066901A (en) Apparatus and method for analyzing malware in data analysis system
CN111723002A (en) Code debugging method and device, electronic equipment and storage medium
CN103200325A (en) Peripheral device for mobile terminal and communication method for mobile terminal and peripheral device
CN104660814A (en) Communication information display method and terminal
KR102203130B1 (en) Method for controlling an use of sim card and an electronic device thereof
CN106856474A (en) A kind of processing method and processing device of checking information
CN114968023A (en) Terminal control method, terminal control device, electronic equipment and storage medium
CN107346197B (en) Information display method and device
CN110399131B (en) Method, device and computer equipment for improving stability of application program
CN105812543A (en) Information integration system and method
KR101260773B1 (en) Apparatus and method for communicating interstitial applications
EP3499399A1 (en) Electronic apparatus and information reading control method
CN111741453A (en) Bluetooth data encapsulation communication method and device
CN111212439A (en) Mobile terminal testing device, mobile terminal testing system and NSA testing method
CN108009084B (en) Testing method, device and system for hybrid mobile application
CN106934616A (en) A kind of service implementation method and device based on NFC technique

Legal Events

Date Code Title Description
A201 Request for examination
A302 Request for accelerated examination
E902 Notification of reason for refusal
E701 Decision to grant or registration of patent right
GRNT Written decision to grant
FPAY Annual fee payment

Payment date: 20170501

Year of fee payment: 5

FPAY Annual fee payment

Payment date: 20190429

Year of fee payment: 7