WO2015105293A1

WO2015105293A1 - Method, system and computer-readable storage medium for handling log regarding application

Info

Publication number: WO2015105293A1
Application number: PCT/KR2014/013000
Authority: WO
Inventors: 박남욱; 이태규
Original assignee: 주식회사 프로브테크놀로지
Priority date: 2014-01-07
Filing date: 2014-12-29
Publication date: 2015-07-16
Also published as: KR101668713B1; KR20150082106A

Abstract

Provided is a method for handling a log regarding an application according to an aspect of the present invention, the method comprising the steps of: when an event regarding an application of a user terminal device occurs, acquiring a log regarding the event by an SDK embedded in the application; and analyzing the log and classifying the log with a predetermined category.

Description

Method, system and computer readable recording medium for handling logs relating to an application

The present invention relates to a method, system and computer readable recording medium for handling logs relating to an application.

The mobile application market is growing rapidly with the increase in the population using smartphones or tablet PCs. As of June 2013, Apple's App Store has more than 900,000 applications, and Google's Google Play is about 70 It is reported to provide 10,000 applications. Meanwhile, the number of mobile application users is expected to reach about 4.4 billion by 2017, from 1.2 billion in 2012. However, despite the continued growth of the mobile application market, the profitability of mobile application developers and developers is polarizing, and global competition is expected to intensify.

In this race, there is a growing need for developers to develop mobile applications more easily and at higher productivity while appropriately handling data associated with mobile applications.

In order to assist the developer in developing and analyzing the usability of a mobile application, a conventional technique such as the technique disclosed by Korean Patent Publication No. 10-2013-0058336 has been proposed. According to the technique of the above publication, it is possible to analyze the usability of the mobile application by analyzing the behavior log of the user who uses the mobile application centered on the controversy. However, this prior art attitude has been to require the developer of a mobile application to do coding to allow a log of user activity to it to be analyzed.

That is, from the developer's point of view, it is true that log data of user behavior or data of events occurring in accordance with user behavior (hereinafter, collectively referred to as "log") is important, but not much effort is required to make it analyzed. It is a reality. This is true even if the developer develops and uses a mobile application that incorporates a Software Development Kit (SDK), so that logs about the mobile application can be analyzed. This is because a developer must perform coding that classifies the log or sets the relationship between specific events even when the log of the SDK embedded mobile application is analyzed by in-app usage analytics. to be. Worse still, if this coding changes, the developer also has to change the mobile application itself.

Accordingly, the present inventor (s) will propose a novel technique for handling logs related to mobile applications, while eliminating all of the above problems of the prior art.

The present invention aims to solve all of the above-mentioned problems of the prior art.

Another object of the present invention is to allow logs to be properly handled even when a developer does not perform coding to classify logs or determine a relationship between specific events.

Another object of the present invention is to allow the log to be properly handled even if the mobile application is not changed.

The present invention further provides that a system for communicating with a mobile application centrally handles a plurality of log packages received from a plurality of mobile applications, so that the category of the corresponding logs may be difficult to determine. The purpose.

Representative configuration of the present invention for achieving the above object is as follows.

According to an aspect of the present invention, there is provided a method for handling a log of an application, the method comprising: acquiring a log of the event by an SDK embedded in the application when an event regarding an application of a user terminal device occurs; And analyzing the log and classifying the log into a predetermined category.

According to another aspect of the present invention, there is provided a system for handling logs relating to an application, wherein when an event relating to an application of a user terminal device occurs, the log relating to the event is acquired by an SDK built in the application. A system including a log acquisition unit and a log management unit for analyzing the log and classifying the log into a predetermined category is provided.

In addition, there is further provided a computer readable recording medium for recording another method for implementing the present invention, another system, and a computer program for executing the method.

According to the present invention, the effect that the log can be properly handled is achieved even if the developer does not perform coding that classifies the log or defines the relationship between specific events.

In addition, according to the present invention, the effect that the log can be properly handled even if the mobile application does not necessarily change.

In addition, according to the present invention, as a system for communicating with a mobile application centrally handles a plurality of log packages received from a plurality of mobile applications, it is difficult to determine the category among the corresponding logs. Effect is achieved.

1 is a diagram illustrating a schematic configuration of an entire system for handling logs relating to an application according to an embodiment of the present invention.

2 is a diagram illustrating in detail the internal configuration of the log handling system 200 according to an embodiment of the present invention.

3 and 4 are diagrams for exemplarily describing a log obtaining unit obtaining a log from a user terminal device according to an exemplary embodiment of the present invention.

FIG. 5 is a diagram for exemplarily describing classification of a log obtained according to an exemplary embodiment according to a preset condition.

210: log acquisition unit

220: log management unit

230: database

240: communication unit

250: control unit

DETAILED DESCRIPTION The following detailed description of the invention refers to the accompanying drawings that show, by way of illustration, specific embodiments in which the invention may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the invention. It should be understood that the various embodiments of the present invention are different but need not be mutually exclusive. For example, certain shapes, structures, and characteristics described herein may be implemented with changes from one embodiment to another without departing from the spirit and scope of the invention. In addition, it is to be understood that the location or arrangement of individual components within each embodiment may be changed without departing from the spirit and scope of the invention. Accordingly, the following detailed description is not to be taken in a limiting sense, and the scope of the present invention should be taken as encompassing the scope of the claims of the claims and all equivalents thereto. Like reference numerals in the drawings indicate the same or similar elements throughout the several aspects.

Hereinafter, various preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings so that those skilled in the art can easily implement the present invention.

[Preferred Embodiments of the Invention]

Configuration of the entire system

As shown in FIG. 1, the entire system according to an embodiment of the present invention may include a communication network 100, a log handling system 200, and a user terminal device 300.

First, the communication network 100 according to an embodiment of the present invention may be configured regardless of a communication mode such as wired communication or wireless communication, and includes a local area network (LAN) and a metropolitan area network (MAN). ), And various communication networks such as a wide area network (WAN). Preferably, the communication network 100 as used herein may be a known Internet or World Wide Web (WWW). However, the communication network 100 may include, at least in part, a known wired / wireless data communication network, a known telephone network, or a known wired / wireless television communication network without being limited thereto. Apparently, the communication network 100 is implemented by techniques such as IEEE 802.11, Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Global System for Mobile communications (GSM), Long Term Evolution (LTE), and the like. A wireless communication network may be included at least in part.

Next, the log handling system 200 according to an embodiment of the present invention is an event occurring in the terminal device 300 of the user through the communication network 100 (mainly generated by the user's action, but the user's specific A function of receiving and handling logs from the user terminal device 300 that are not actions, for example, may be caused by the movement of the user terminal device 300 according to the movement of the vehicle in which the user is riding. Can be performed.

The configuration and function of the log handling system 200 according to the present invention will be described in more detail below.

Lastly, the user terminal device 300 according to an embodiment of the present invention is a digital device including a function of communicating after connecting to the log handling system 200, and includes a smart phone, a tablet PC, and other smart devices ( For example, a mobile device such as a smart watch or a smart glass) or a mobile device having a memory means such as a desktop computer, a notebook computer, a workstation, a PDA, a web pad, a mobile phone, or the like, can be operated by mounting a microprocessor. Any digital device having the capability can be adopted as the user terminal device 300 according to the present invention.

In particular, the user terminal device 300 may include an application program that the user can appropriately use according to the corresponding purpose. This will typically be a mobile application that can generate certain events or generate other events depending on the user's actions. On the other hand, the application program may be an SDK embedded program (in this case, the SDK may be designed for a predetermined operating system and provided commercially or non-commercially for the public). The SDK may provide a log or log package as described below to the log handling system 200 without coding a developer's application.

Configuring the Log Handling System

Hereinafter, the internal structure of the log handling system 200 and the function of each component will be described.

The log handling system 200 according to an exemplary embodiment of the present invention may be a digital device having a computing capability with a memory means and a microprocessor. This log handling system 200 may be a server system. As illustrated in FIG. 2, the log handling system 200 may include a log acquirer 210, a log manager 220, a database 230, a communicator 240, and a controller 250. According to an embodiment of the present invention, the log acquisition unit 210, the log management unit 220, the database 230, the communication unit 240 and the control unit 250 at least a part of the communication with the user terminal device 300 It may be a program module. Such program modules may be included in the log handling system 200 in the form of operating systems, application modules, or other program modules, and may be physically stored in various known storage devices. Such program modules may also be stored in a remote storage device capable of communicating with the log handling system 200. On the other hand, such program modules include, but are not limited to, routines, subroutines, programs, objects, components, data structures, etc. that perform particular tasks or execute particular abstract data types, described below, in accordance with the present invention.

First, when a predetermined event occurs with respect to an application of the user terminal device 300, the log acquisition unit 210 according to an embodiment of the present invention may log a log of the event to an action of an SDK embedded in the application. It can perform a function obtained by. The log acquisition unit 210 may acquire a log immediately, periodically or intermittently. Alternatively, the log may be obtained by directly requesting the user terminal device 300 (such a request may be particularly performed when real time analysis of the log is not necessary or when the user terminal device 300 is relatively idle. This can be useful if it is better to obtain the log while in the process. Such logs may preferably be logs that are packaged as long and short of the time interval between two adjacent logs. That is, a package of logs may be a package of two or more consecutive logs in which a time interval between two adjacent logs is shorter than a predetermined reference time.

As shown in FIG. 3, a predetermined application (for example, a Facebook (which is a service mark of a US famous SNS) application) may be used in the user terminal device 300. When the user selects a predetermined object 310 displayed to the user by the application, the embedded SDK of the application may transmit a log about an event occurring according to the user's selection action to the log acquisition unit 210. In this case, the SDK may send log data packaged with respect to the plurality of events, as shown in FIG. 4. As shown, this log package may include an ID 410 that enables the SDK to identify the embedded application and its user, and a plurality of

logs

420 and 425 for a plurality of events. The log may include information on the type of the corresponding event, the location of the scroll or click, the target object, and the like. A log corresponding to reference number 425 may correspond to an event illustrated with reference to FIG. 3. Meanwhile, each of the plurality of logs in one log package may be arranged according to a corresponding logging time.

Next, the log management unit 220 according to an embodiment of the present invention may perform a function of analyzing the log obtained by the log acquisition unit 210 and classifying or processing the log according to a predetermined condition. In this case, the condition may be a preset condition or a condition that is adaptively changed. On the other hand, the log management unit 220 may analyze the log to select only the log of the event of interest, and then may perform classification or processing.

As shown in FIG. 5, the log manager 220 analyzes the types of applications and information on each

log

420 and 425 from the log package, and then logs the

logs

420 and 425 according to a predetermined condition. It may be classified into one of the

categories

510, 520, and 530. In particular, when the log is generated by the user selecting a predetermined object displayed by the application, the category to which the log should be classified may be determined by analyzing the type of the object. For example, when a predetermined SNS application (eg, a Facebook application) is used, a 'Like' object among 'Like', 'Comment' and 'Share' objects included in each posting by the user. Is selected, a corresponding event occurs and a log 425 is generated, and the log manager 220 identifies a 'like' object which is the corresponding object in the log 425, so that the log 425 is relatively simply 'posted'. May be classified into categories 510. If necessary, the log manager 220 may perform a process of providing the sorted log 425 to an application usability analysis device (or module) inside or outside the log handling system 200.

Meanwhile, the log manager 220 determines that a log belongs to a log package indicating a specific log category arrangement pattern, and then logs the log package to another log package having a similar pattern (for example, all logs already associated with the log package). The log may be classified by comparison with a log package in which analysis is completed.

For example, five logs in one package can be arranged in the order of A, B, C, D and E, where each alphabetic symbol is a identified category of each log, When there are a plurality of log packages of the log category arrangement pattern, the above log category arrangement pattern may be one comparison criterion.

In this case, if a log package shows a log category arrangement pattern of A, B, X, D, and E (where X is an unknown log category), the log manager 220 sorts the categories according to a set filtering principle. It is possible to determine that a log that has not been identified belongs to the category of C.

Next, in the database 230 according to an embodiment of the present invention, information such as logs, log packages, classified logs, and the like may be stored. Although the database 230 is illustrated as being included in the log handling system 200 in FIG. 2, the database 230 is separate from the log handling system 200, as required by those skilled in the art to implement the invention. It may be configured. On the other hand, the database 230 in the present invention is a concept that includes a computer-readable recording medium, and may be a broad database including not only a negotiated database but also a file system based on a file system. If the set can be retrieved to extract data, it can be the database 230 of the present invention.

Next, the communication unit 240 according to an embodiment of the present invention may perform a function to enable data transmission / reception from / to the log acquisition unit 210, the log management unit 220, and the database 230.

Finally, the control unit 250 according to an embodiment of the present invention may perform a function of controlling the flow of data between the log acquisition unit 210, the log management unit 220, the database 230 and the communication unit 240. have. That is, the controller 250 according to the present invention controls the data flow from / to the outside of the log handling system 200 or the data flow between each component of the log handling system 200, thereby obtaining the log acquisition unit 210. The log manager 220, the database 230, and the communicator 240 may control to perform unique functions, respectively.

Embodiments according to the present invention described above can be implemented in the form of program instructions that can be executed by various computer components and recorded in a computer-readable recording medium. The computer-readable recording medium may include program instructions, data files, data structures, etc. alone or in combination. Program instructions recorded on the computer-readable recording medium may be specially designed and configured for the present invention, or may be known and available to those skilled in the computer software arts. Examples of computer-readable recording media include magnetic media such as hard disks, floppy disks and magnetic tape, optical recording media such as CD-ROMs and DVDs, and magneto-optical media such as floptical disks. medium) and hardware devices specifically configured to store and execute program instructions, such as ROM, RAM, flash memory, and the like. Examples of program instructions include not only machine code generated by a compiler, but also high-level language code that can be executed by a computer using an interpreter or the like. The hardware device may be modified with one or more software modules to perform the processing according to the present invention, and vice versa.

Although the present invention has been described by specific matters such as specific components and limited embodiments and drawings, it is provided only to help a more general understanding of the present invention, and the present invention is not limited to the above embodiments. Those skilled in the art may make various modifications and changes from this description.

Therefore, the spirit of the present invention should not be limited to the above-described embodiments, and the scope of the spirit of the present invention is defined not only in the claims below, but also in the ranges equivalent to or equivalent to the claims. Will belong to.

Claims

As a method for handling logs about an application,

When an event relating to an application of the user terminal device is generated, acquiring a log of the event by an SDK built in the application; and

Classifying the log into a predetermined category

How to include.
The method of claim 1,

The log obtaining step includes the step of obtaining the log in the form of a package.
The method of claim 2,

And wherein the log package is packaged together with two or more consecutive logs whose time interval between two adjacent logs is less than a predetermined reference time.
The method of claim 1,

The log obtaining step is executed according to a request issued while the user terminal device is in a lazy state.
The method of claim 2,

The analyzing and classifying the log comprises analyzing the log package based on a specific log category arrangement pattern.
A system for handling logs about an application,

A log acquisition unit for acquiring a log of the event by an SDK built in the application when an event regarding an application of the user terminal device occurs;

Log management unit to analyze the log and classify it into a predetermined category

System comprising.
A computer-readable recording medium for recording a computer program for executing the method according to any one of claims 1 to 5.