TW202524314A - Apparatus for monitoring whether a function is implemented normally and method thereof - Google Patents

Abstract

According to the present invention, a method for processing information in an electronic device is disclosed, which includes the following steps: determining whether a function is normally implemented in a customer's terminal; and when it is determined that the function is not normally implemented in the customer's terminal, determining whether an abnormal screen is output in the customer's terminal.

Description

Device and method for monitoring whether functions are normally realized

The present invention relates to a device and method for monitoring whether a function is normally implemented. More specifically, the present invention relates to an electronic device and method for determining whether a function is normally implemented in a customer's terminal, and when determining that the function is not normally implemented in the customer's terminal, determining whether an abnormal screen is output in the customer's terminal.

With the development of electronic technology, services using electronic technology have occupied a place in the whole life. Services using electronic technology can be provided based on various codes (programs written in machine language and interpreted and executed by CPU). As a specific form of the method of providing services based on codes, there is a method of applying various functions (for example, scripts including codes) to services.

As services become more sophisticated, various functions are applied to the same service, and the complexity of implementing them is gradually increasing, errors may occur for various reasons. For example, in the case of hybrid applications that are all related to native apps and web-based apps, errors may occur during the communication and compatibility process between native apps and web-based apps. In addition, errors may occur for the following reasons: compatibility issues of the terminal receiving the service, JavaScript syntax issues (e.g. JavaScript syntax compatibility issues), system version inconsistency issues, spontaneous rendering issues of web views (WebView), etc.

As described above, as errors may occur for a variety of reasons, methods for detecting specific types of errors are less useful than general error detection methods. Furthermore, even in the case of general error detection methods, ensuring the cost efficiency of resources and time consumed for their detection (i.e., preventing excessive waste of costs) becomes an important issue.

In this regard, please refer to previous literature such as KR101944874B1 or KR100618319B1.

[The problem the invention is trying to solve]

The problem to be solved by this embodiment is to provide an electronic device and a method thereof. To solve the above problem, the electronic device determines whether a function is normally implemented in a customer's terminal. When it is determined that the function is not normally implemented in the customer's terminal, it determines whether an abnormal screen is output in the customer's terminal.

The technical issues to be realized by this embodiment are not limited to the technical issues described above, and other technical issues can be introduced based on the following embodiments. [Technical means to solve the problem]

An embodiment of a method for processing information in an electronic device includes the following steps: determining whether a function is normally implemented in a customer's terminal; and if it is determined that the function is not normally implemented in the customer's terminal, determining whether an abnormal screen is output in the customer's terminal.

According to one embodiment, the abnormal screen may include a screen having a fixed ratio or more of the screen filled with a single color.

According to one embodiment, the step of determining whether the above function is normally implemented in the above customer's terminal may include the following steps: confirming whether information notifying that the above function is normally implemented is received from the above customer's terminal within a set time.

According to one embodiment, the information notifying that the above function is normally implemented may include information indicating that a screen rendering process associated with the above function is successful.

According to one embodiment, the step of determining whether an abnormal screen is output in the customer's terminal may include the following steps: obtaining a screenshot of the screen output in the customer's terminal; down-scaling the screenshot to obtain a converted image; and determining whether the converted image is an abnormal screen.

According to one embodiment, the step of determining whether the above-mentioned converted image belongs to an abnormal screen may include the following steps: obtaining information on colors corresponding to each of the above-mentioned multiple unit constituent elements in relation to the multiple unit constituent elements included in the above-mentioned converted image; and based on the colors corresponding to each of the above-mentioned multiple unit constituent elements, determining whether the ratio of unit constituent elements that meet the set conditions exceeds the set critical ratio.

According to one embodiment, the unit constituent elements satisfying the above-mentioned setting conditions may include unit constituent elements corresponding to colors in a set of more than one set of colors.

According to one embodiment, the unit components that meet the above-set conditions may include unit components that are not assigned any color.

According to one embodiment, the unit constituent element may belong to a pixel.

According to an embodiment, the method may further include the following steps: verifying whether the judgment result of whether an abnormal screen is output in the customer's terminal is accurate.

According to one embodiment, the verification step may include the following steps: after providing the function, obtaining information about the interaction between the customer and the customer's terminal; and based on the interaction information, predicting whether an abnormal screen is output in the customer's terminal.

According to one embodiment, the method may further include the following steps: based on the verification, obtaining feedback information related to the process of determining whether an abnormal screen is output in the customer's terminal.

According to an embodiment, the method may further include the following step: when it is determined that an abnormal screen is output in the customer's terminal, disabling the function.

According to one embodiment, the electronic device may detect in advance whether there are defects related to the execution of the function. If no defects are detected, it is determined whether the function is normally implemented in the customer's terminal.

An electronic device for processing information in one embodiment may include a transceiver, a memory for storing commands, and a processor, wherein the processor is as follows: connected to the transceiver and the memory to determine whether a function is normally implemented in a customer's terminal; when it is determined that the function is not normally implemented in the customer's terminal, it determines whether an abnormal screen is output in the customer's terminal.

Specific matters of other embodiments are included in the detailed description and drawings. [Effects of the invention]

According to the present invention, an electronic device and method for monitoring whether a function is normally implemented discloses a general error detection method applicable to various types of errors related to the execution of functions, and can also ensure cost economy by preventing excessive waste of resources and time consumed in its detection.

The effects of the invention are not limited to the effects mentioned above, and a person skilled in the art can clearly understand other effects not mentioned based on the description of the invention patent application scope.

The terms used in the embodiments are currently widely used general terms as much as possible in consideration of the functions of the present invention, but they may differ due to the intentions of technical personnel in the field, precedents, the emergence of new technologies, etc. In addition, in specific cases, there are also terms that the applicant arbitrarily selects. In such cases, their meanings are described in detail in the corresponding description section. Therefore, the terms used in the present invention should be defined based on the meanings of the terms and the overall content of the present invention, rather than simply defined by the names of the terms.

Throughout the specification, when a certain part is described as "including" a certain component, unless otherwise stated, it means that other components may be further included, and other components are not excluded. In addition, the terms "...part" and "...module" described in the specification represent a unit that processes at least one function or action, and the unit can be implemented by hardware or software, or by a combination of hardware and software.

The expression "at least one of a, b, and c" recorded throughout the specification may include "a alone", "b alone", "c alone", "a and b", "a and c", "b and c", or "a, b, and c".

The "terminal" mentioned below can be realized by a computer or a portable terminal, which can be connected to a server or other terminals via a network. Here, the computer includes, for example, a notebook computer, a desktop computer, a laptop computer, etc. equipped with a web browser, and the portable terminal is a wireless communication device that ensures portability and mobility, and can include, for example, IMT (International Mobile Telecommunication), CDMA (Code Division Multiple Access), W-CDMA (W-Code Division Multiple Access), LTE (Long Term Evolution) and other communication terminals, such as smartphones, tablet computers, and all types of handheld wireless communication devices.

Hereinafter, the embodiments of the present invention will be described in detail with reference to the attached drawings so that those skilled in the art can easily implement the present invention. However, the present invention can be implemented in various forms and is not limited to the embodiments described herein.

Hereinafter, referring to the accompanying drawings, embodiments of the present invention will be described in detail.

When describing the embodiments, the description of the technical contents that are well known in the technical field to which the present invention belongs and are not directly related to the present invention is omitted. The reason is that the main purpose of the present invention can be conveyed more clearly by omitting redundant descriptions to avoid confusion of the main purpose of the present invention.

For the same reason, some components are exaggerated, omitted or shown schematically in the attached drawings. In addition, the size of each component does not completely reflect the actual size. In each figure, the same reference number is given to the same or corresponding components.

The advantages and features of the present invention, as well as the methods for achieving the advantages and features, will become clear as long as reference is made to the accompanying drawings and the embodiments described in detail below. However, the present invention is not limited to the embodiments disclosed below, but can be implemented in various different forms. The embodiments are provided only to fully disclose the present invention and enable those with common sense in the technical field to which the present invention belongs to fully understand the scope of the present invention. The present invention is defined only by the scope of the invention application. Throughout the specification, the same reference symbols represent the same constituent elements.

At this point, it is understood that the combination of each block of the process flow chart and the flow chart can be implemented by computer program instructions. Such computer program instructions can be loaded on a processor of a general-purpose computer, a special-purpose computer or other programmable data processing device, so that such instructions implemented by the processor of the computer or other programmable data processing device will produce a method for implementing the functions described in the blocks of the flow chart. In order to implement the functions in a specific manner, such computer program instructions can be stored in a computer-usable or computer-readable memory that can be directed to a computer or other programmable data processing device, so that the instructions stored in the computer-usable or computer-readable memory can also produce a manufactured item that includes an instruction method for implementing the functions described in the blocks of the flow chart. Computer program instructions can also be loaded on a computer or other programmable data processing device, so that a series of action steps are executed on the computer or other programmable data processing device to generate a process executed by the computer, so that the instructions executed by the computer or other programmable data processing device can also provide steps for executing the functions described in the blocks of the flowchart.

Furthermore, each block may represent a module, a segment, or a portion of code that includes one or more executable instructions for performing a specific logical function. Furthermore, in some alternative implementations, the functions mentioned in the blocks may not be performed in order. For example, two blocks shown in succession may be executed simultaneously, or may occasionally be executed in the opposite order according to the corresponding functions.

FIG. 1 is a schematic diagram showing a system 100 for monitoring whether a function is normally implemented according to an embodiment.

According to various embodiments, the system 100 for monitoring whether a function is normally implemented includes an electronic device 110 and a customer terminal 120. The system 100 for monitoring whether a function is normally implemented in one embodiment may further include a network that supports information transmission and reception between the electronic device 110, the customer terminal 120, and at least a portion of the external device.

The electronic device 110 and the customer's terminal 120 may include a transceiver, a memory, and a processor. In addition, the electronic device 110 and the customer's terminal 120 respectively refer to a unit that processes at least one function or action, which may be implemented by hardware or software, or by a combination of hardware and software.

On the other hand, in the entire embodiment, the electronic device 110 and the customer's terminal 120 are respectively mentioned as separate devices or servers, but they can be logically separated structures, and at least a part of them can be realized by functions separated from one device or server. For example, in the entire present invention, the electronic device 110 and the customer's terminal 120 can be realized by one device. In this case, it can be understood as follows: to achieve the judgment whether the function is normally realized in the terminal used by the customer and to judge whether an abnormal screen is output, etc., the process of sending and receiving information between the electronic device 110 and the customer's terminal 120 can be understood as the process of actually exchanging data in one device.

According to one embodiment, the electronic device 110 and the customer's terminal 120 may include a plurality of computer systems or computer software implemented by a network server. For example, at least a portion of the electronic device 110 and the customer's terminal 120 may refer to the following computer systems and computer software: connected to a lower device to accept a request for an operation, perform the operation on the request and provide an execution result, and the lower device can communicate with other network servers through a computer network such as an intranet or the Internet. In addition, at least a portion of the electronic device 110 and the customer's terminal 120 can also be understood as the following broad concept: including a series of applications that can perform actions on a network server, and various databases built on the internal or connected nodes. For example, at least a portion of the electronic device 110 and the customer's terminal 120 may be implemented using a network server program provided in various forms based on operating systems such as DOS, Windows, Linux, UNIX, or MacOS.

On the other hand, for the sake of convenience, although the various action subjects are referred to as electronic devices 110 and customer terminals 120, they should be understood as the following general types of devices: capable of corresponding to various types of devices, such as computer devices and mobile communication terminals, etc., or including various types of devices, or included in various types of devices.

The electronic device 110 is a device for processing various information. The electronic device 110 can perform various operations for processing information. Specifically, the electronic device 110 determines whether a function is normally implemented in the customer's terminal. When it is determined that the function is not normally implemented in the customer's terminal, it determines whether an abnormal screen is output in the customer's terminal. In this regard, "function" as a function implemented for providing services to the customer's terminal 120 can be understood as a broad concept including various forms such as a collection of objects/actions/programs/routines/subroutines/collections of execution statements, and specific forms do not limit the scope of the present invention.

Customers may include various entities that wish to use the services provided. The "services" that customers wish to use may be provided by the electronic device 110, but the scope of the present invention is not limited thereto. For example, there may be various embodiments as follows: the main device that provides the service exists alone, and the electronic device 110 of the present invention may be a separate sub-device used to monitor whether the function is normally implemented.

The customer terminal 120 may be a device operated and managed by the customer as its user. The customer terminal 120 may receive input from the customer or information from the electronic device 110 or other devices, and perform corresponding actions. For example, the customer terminal 120 may receive information about a function from the electronic device 110, and based on this, display a corresponding screen (according to an embodiment, the customer terminal 120 may also constitute a screen corresponding to the function). In addition, the customer terminal 120 may provide information about the displayed screen (e.g., a screenshot of the screen) to the electronic device 110. In addition, there may be various examples related to the actions of the customer's terminal 120. For example, the customer's terminal 120 may also receive information notifying the deactivation of the function from the electronic device 110, and display a screen reflecting the deactivation of the function in response thereto.

More details about the operation of the electronic device 110 and the customer's terminal 120 will be described in FIGS. 2 to 8 .

The electronic device 110 and the customer's terminal 120 may include a computer device, a mobile communication terminal, a server, etc. The electronic device 110 may include an input device such as a touch panel, a mouse, a keyboard, etc. for receiving input, or be connected to the input device. According to an embodiment, the customer's terminal 120 may also be the same. In addition, the electronic device 110 may include an output device such as a screen, a speaker, an interface device, etc. for providing information to the user, or be connected to the output device. According to an embodiment, the customer's terminal 120 may also be the same. Furthermore, the input device and the output device of the electronic device 110 and the customer's terminal 120 may be integrally formed or associated with each other. For example, at least one of the electronic device 110 and the customer's terminal 120 may display an interface for receiving input.

The actions related to a series of information providing methods of various embodiments may be implemented by a single physical device or by a plurality of physical devices in an organic combination. For example, a portion of the components included in the system 100 for monitoring whether the function is normally implemented may be implemented by a certain physical device, and the remaining portion may be implemented by other physical devices. For example, a certain physical device may be implemented by a portion of the electronic device 110, and other physical devices may also be implemented by a portion of the customer's terminal 120 or a portion of other external devices. Depending on the situation, the components included in the system 100 for monitoring whether the function is normally implemented can also be implemented in the following manner: they are respectively distributed in different physical devices and configured, and the distributed components are organically combined to implement the functions and actions of the system 100 for monitoring whether the function is normally implemented. For example, the electronic device 110 in this specification includes at least one sub-device, and it is recorded that a part of the actions implemented by the electronic device 110 can be implemented by the first sub-device, and the remaining part of the actions can also be implemented by the second sub-device.

FIG. 2 is a flowchart for illustrating an operation of a hybrid application according to an embodiment.

2 , at least a portion of the services provided to the customer's terminal 120 of an embodiment can be implemented in the form of a hybrid application 200. The hybrid application 200 may refer to an application that, when implemented, is implemented in a manner that includes all native applications 210 and web-based applications 220. In addition, the hybrid application 200 may further implement functions for processing communication and interaction between the native application 210 and the web-based application 220. For example, according to one example, the JavaScript Bridge (JsBridge) 230 may process the communication and interaction between the native application 210 and the web-based application 220.

With the development of electronic technology, services have become increasingly sophisticated, and many services have the form of hybrid applications 200. In the communication and compatibility process between the native application 210 and the web-based application 220, hybrid applications 200 are prone to errors, and the types of errors that may occur are also diverse, so there is a problem that the detection thereof is relatively difficult. Therefore, in the case of hybrid applications 200, the monitoring method proposed by the present invention may be particularly useful.

However, the description of the hybrid application 200 is intended to emphasize the effect of the method of the present invention, and should not be understood as the method of the present invention being applicable only to the hybrid application 200. On the contrary, the method of the present invention is a general error detection method that is not restricted by the type of error and the type of application, and can be applied.

FIG. 3 is a flow chart for illustrating a method for monitoring whether a function is normally implemented in an electronic device according to an embodiment.

Referring to FIG. 3 , the electronic device 110 of one embodiment can determine whether a function is normally implemented in the customer's terminal 120 (310). When the function is normally implemented in the customer's terminal 120 (310, YES), monitoring can be terminated without any problem. However, "termination" here should be understood to mean that it has been determined that the function has been normally implemented in the current step (furthermore, it is intended that there is no need to proceed to the step numbered 320 because it has been normally implemented), and should not be understood to mean that it is determined that the function will no longer be monitored next, or that monitoring of other functions will be interrupted.

On the other hand, when it is determined that the function is not normally implemented in the customer's terminal 120 (310, NO), the electronic device 110 determines whether to output an abnormal screen in the customer's terminal 120 (320).

FIG. 4 shows a more detailed embodiment related to the action of icon number 310 for determining whether a function is normally implemented in the customer's terminal 120. Referring further to FIG. 4, the electronic device 110 of one embodiment may wait for receiving information notifying normal implementation of the function from the customer's terminal 120 within a set time (410). Thereafter, the electronic device 110 may confirm whether the information notifying normal implementation of the function has been received (420). The situation of receiving the information notifying normal implementation of the function (420, YES) may be understood as belonging to one embodiment of the above-mentioned "situation that the function is normally implemented in the customer's terminal 120 (310, YES)". The situation where the information notifying the normal implementation of the function is not received (420, NO) can be understood as an example of the above-mentioned situation where it is determined that the function is not normally implemented in the customer's terminal 120 (310, NO).

On the other hand, the embodiment of FIG. 4 is only an example of confirming whether the information notifying the normal function implementation is received from the customer's terminal 120 within the set time, and the scope of the present invention is not limited to the embodiment of FIG. 4. For example, the example of FIG. 4 is to wait for the information notifying the normal function implementation within the set time, and then perform the action of determining whether the information is received. On the contrary, according to other examples, as the information notifying the normal function implementation is repeatedly determined within the set time, if it is confirmed that the information is received (even if it is before the set time), it can immediately proceed to the next step.

In addition, according to the embodiments, there may be various embodiments related to the present invention as follows: even when receiving the situation of "information that the notification function is not implemented normally", the electronic device 110 can also implement the action of icon number 320 (immediately before the set time).

In the present invention, "information notifying that a function is normally implemented" may include information indicating that a screen rendering process is successful, and "information notifying that a function is not normally implemented" may include information indicating that a screen rendering process fails. In other words, "whether a function is normally implemented" may be understood to include whether a screen is displayed in the customer's terminal 120 (and whether a screen is constituted according to the embodiment) in order to meet the purpose of the function.

Returning to FIG. 3 , as described above, when it is determined that the function is not normally implemented in the customer's terminal 120 (310, NO), the electronic device 110 determines whether to output an abnormal screen in the customer's terminal 120 (320). The abnormal screen may include a screen with a fixed ratio or more of a single color filling the screen, but the scope of the present invention is not limited thereto.

FIG5 shows a more detailed embodiment of the action of icon number 320 for determining whether an abnormal screen is output in the customer's terminal. Referring to FIG5, the electronic device 110 of one embodiment can obtain a screenshot (510) of the screen output in the customer's terminal. Thereafter, the electronic device 110 can zoom out the screenshot to obtain a converted image (520) to determine whether the converted image is an abnormal screen.

On the other hand, according to the embodiment, the action of icon number 520 of converting the image may not be performed by zooming out the screen and taking a screenshot. In the case of such an embodiment, it can be understood that the electronic device 110 can determine whether the screenshot of the screen output to the customer's terminal is an abnormal screen. In the following, for the convenience of explanation, although the situation of performing the action of icon number 520 is described, the following description can also be applied to the situation of performing the action of icon number 520 of converting the image by zooming out the screen and taking a screenshot. In the applicable situation shown above, the description related to "converting the image" can be interpreted and understood as the description related to "screenshot".

According to an embodiment related to the action of determining whether the converted image is an abnormal screen, the electronic device 110 can determine the ratio of the unit components that meet the set conditions in relation to the plurality of unit components included in the converted image (530). As a more specific example, the electronic device 110 can obtain information on the colors corresponding to each of the plurality of unit components in relation to the plurality of unit components included in the converted image, and determine whether the ratio of the unit components that meet the set conditions exceeds a set critical ratio based on the colors corresponding to each of the plurality of unit components. For example, the electronic device 110 checks the colors corresponding to the plurality of unit components included in the converted image and determines whether the ratio of the unit components having white or black colors exceeds 90%. If it exceeds 90%, it can be determined that the screen is abnormal.

As shown in the above example, "unit components that meet the set conditions" may include unit components that correspond to colors in one or more set color sets (in the case of the above example, the one or more color sets include white and black). Of course, "unit components that meet the set conditions" may also include (not a plurality of color sets) unit components that correspond to a single color. In this regard, in the case where "unit components that meet the set conditions" are unit components that correspond to a single color, the abnormal screen may be a screen with a fixed ratio or more of the screen filled with a single color.

According to the embodiment, "unit components that meet the set conditions" may also include unit components that do not specify any color. For example, the electronic device 110 confirms the color corresponding to each of the plurality of unit components included in the converted image, and determines whether the ratio of unit components that do not specify any color exceeds 90%. If it exceeds 90%, it can also be determined that it belongs to an abnormal screen. As described above, an example of a unit component that does not specify any color may include a blank pixel.

The unit components described in the present invention may belong to any pixel. However, in addition, the unit components may also include components of various shapes and sizes that fill the screen according to a preset standard, and the scope of the present invention is not limited by a specific type of unit components.

As described above, an abnormal screen of an embodiment may include a screen that is filled with a single color at a fixed ratio or more. In this regard, referring to an example of FIG. 6 , an example (a) of a screen that is filled with white at a fixed ratio or more, and an example (b) of a screen that is filled with black at a fixed ratio or more may be examples of abnormal screens. Of course, this is only an example to help understanding, and does not limit the scope of the present invention.

Returning to FIG. 3 again, when it is determined that an abnormal screen has been output (330, YES), the electronic device 110 of one embodiment may disable the function (340). In this regard, there may be various embodiments associated with the deactivation of the function as follows: the function may be disabled only in the customer's terminal 120, the function may be disabled in other terminals that meet the conditions set in the relationship with the customer's terminal 120 (for example, terminals of the same model as the customer's terminal 120), and the function may be disabled in all terminals.

Furthermore, according to one embodiment, the specific reason for outputting the abnormal screen or the specific judgment result of whether the abnormal screen is output in other terminals can be considered to determine the scope of the terminal deactivation. For example, if the reason for outputting the abnormal screen is a compatibility problem with the customer's terminal 120, the function can be deactivated for other terminals of the same model as the customer's terminal 120. As another example, if the abnormal screen is not output in other terminals, the function can also be deactivated only in the customer's terminal 120.

According to the embodiment, in addition to the electronic device 110 directly disabling the function, the function may be disabled or determined to be disabled by other subjects. For example, the electronic device 110 may transmit information notifying the output of an abnormal screen to an external device, or provide it to an administrator (which may include a user of the electronic device 110, but is not limited thereto), and the function may be disabled by the external device or the administrator. As another example, the electronic device 110 transmits information notifying the output of an abnormal screen to an external device, or provides it to the administrator. If a deactivation instruction is received from the external device or the administrator, the electronic device 110 may deactivate the function based on the instruction.

As described above, when the information notifying the abnormal screen output is transmitted to an external device or provided to a management personnel, the information can be provided in the form of notification via a dashboard. However, the scope of the present invention is not limited thereto.

Furthermore, even when it is determined that an abnormal screen is outputted in the customer's terminal, it is not necessary to immediately disable the function. For example, the electronic device 110 can wait within a fixed time after determining that an abnormal screen is outputted, and can more clearly determine whether it is a situation suitable for disabling the function. In this regard, when waiting within a fixed time, the electronic device 110 can observe the customer's actions and can also determine again whether an abnormal screen is outputted, etc., and can perform various operations, but whether to perform what kind of operation does not limit the scope of the present invention.

According to an embodiment, the electronic device 110 can also detect in advance whether there is a defect related to the execution of the function. In this case, if no defect is detected, the electronic device 110 can determine that the function is normally implemented in the customer's terminal (the action of the diagram number 310). In other words, the electronic device 110 of an embodiment can detect in advance whether there is a defect related to the execution of the function, and when the defect is detected in advance, the action of the diagram number 310 is not performed. In the case of the embodiment described above, when the defect has been confirmed, the action of Figure 3 is not performed, thereby preventing unnecessary waste of resources and time.

On the other hand, the operation of detecting whether there are defects in advance may include one or more of the operation of determining whether there is information related to the implementation of the function, and the operation of determining whether the function is implemented without any problems (for example, in a test environment), but the specific content of these operations does not limit the scope of the present invention.

According to an embodiment, the electronic device 110 may verify the accuracy of the judgment result of whether an abnormal screen is output in the customer's terminal 120. The action of verifying the accuracy may not only include the action of verifying the accuracy of a single judgment result, but also include the action of determining one or more of the accuracy, precision and recall of a plurality of accumulated judgment results.

According to one embodiment, after providing the function, the electronic device 110 may obtain information about the interaction between the customer and the customer's terminal 120, and based on the obtained information about the interaction, predict whether an abnormal screen has been output in the customer's terminal 120, thereby verifying whether the judgment result is accurate. For example, if after providing the function, the interaction between the customer and the customer's terminal 120 includes a scroll input and a selection input (click, touch, etc.) by the customer, the electronic device 110 may judge that an abnormal screen has been output.

On the other hand, according to the embodiment, considering that the customer may also provide scrolling or selection input to the abnormal screen, the "information of the interaction used as a basis for predicting that a normal screen has been output" may be set more finely. For example, the electronic device 110 may obtain historical information related to one or more users including the customer, and may further predict whether an abnormal screen has been output in the customer's terminal 120 based on the historical information, the historical information including the activities of one or more users when a normal screen has been output and the activities of one or more users when an abnormal screen has been output.

According to one embodiment, based on the above verification, the electronic device 110 can obtain feedback information related to the process of determining whether an abnormal screen is output in the customer's terminal 120. The feedback information of one embodiment may include information for adjusting one or more parameters, and the one or more parameters are used to determine whether an abnormal screen is output in the customer's terminal 120. For example, when the verification result shows that the judgment of the electronic device 110 is inaccurate and the normal screen is judged as an abnormal screen, the feedback information may include one or more of the following information: information about resetting the "set time" of the action of icon number 410 to a larger value, information about reducing the degree of "zooming out" of the action of icon number 520 (i.e., reducing the screenshot compression), and information about resetting the "critical ratio" related to the ratio of unit components that meet the set conditions to a larger value. By resetting in the above manner, the possibility of judging a normal screen as an abnormal screen can be reduced.

On the other hand, the specific examples of the above feedback information are only used to help understanding and do not limit the scope of the present invention. For example, when the electronic device 110 determines that the normal screen is an abnormal screen, the feedback information may include information about the degree of "zooming out" of the action of increasing icon number 520 (i.e., further compressing the screenshot), and may also include information about changing the specific implementation method of "zooming out". Alternatively, when the electronic device 110 determines that the normal screen is an abnormal screen, the feedback information may also set the "set condition" to a different condition again, and the "set condition" is the object for judging whether the unit constituent element meets its requirements.

In addition, there may be various embodiments related to the present invention. For example, when the electronic device 110 determines that an abnormal screen is a normal screen, feedback information may also be obtained.

FIG. 7 is a diagram for illustrating an embodiment in which a function is not normally implemented in a customer's terminal.

7 , an example 700 of a Document Object Model tree (DOM tree) representing objects of a web page corresponding to (or including) controls and functions according to an embodiment is shown.

There may be various types of functions that are not normally implemented in the customer's terminal, but one type may include a situation where at least a portion of the body portion of the document object model tree structure is missing or deleted. For example, deleting the object included in icon number 710 may output an abnormal screen (e.g., a white screen).

As described above, when at least a portion of the main part of the document object model tree structure is missing or deleted, even if the electronic device 110 detects in advance whether there are defects related to the execution of the function, it is difficult to predict in advance the output of the abnormal screen, only by judging the existence of information related to the realization of the function, or judging whether the load level is normal. Therefore, the method proposed in the present invention may be very useful.

FIG. 8 is a diagram for illustrating a specific example of a method for monitoring whether a function is normally implemented in an electronic device according to an embodiment.

Referring to FIG8 , an electronic device 110 of an embodiment may open a web view (WebView) (801), complete loading of the web view (802), and wait for a rendering success callback (803). When the action of icon number 801 of opening the web view and the action of icon number 802 of completing loading of the web view cannot be achieved, the actions of icon number 803 to icon number 810 may not be performed. The action of icon number 801 of opening the web view and the action of icon number 802 of completing loading of the web view can be understood as an example of the action of "preliminarily detecting whether there is a defect related to the execution of the function" described in FIG3 above.

The action of icon number 803 of waiting for rendering success callback can be understood as an example of the action of "waiting to receive information notifying the normal implementation of the function from the customer's terminal 120 within the set time" (action of icon number 410) in Figure 4. In this case, the set time can be 200ms.

In the case of receiving a rendering success callback (804, YES), monitoring can be terminated without any problem. On the contrary, in the case of not receiving a rendering success callback (804, NO), the electronic device 110 can start detecting an abnormal screen on the customer's terminal 120 (805). The action of icon number 804 for confirming whether to receive a rendering success callback can be understood as an example of the action of "confirming whether the information notifying the normal implementation of the function has been received" in Figure 4 (action of icon number 420).

The combined action of icon number 803 and the action of icon number 804 can be understood as an example of the action of "determining whether the function is normally implemented in the customer's terminal 120" (action of icon number 310) described in FIG. 3 above.

The actions of the combined icon numbers 805 to 809 can be understood as an example of the action of "determining whether an abnormal screen is output in the customer's terminal 120" (the action of icon number 320) described in FIG. 3 above. Specifically, the electronic device 110 that starts detecting the abnormal screen (805) can obtain a screen shot (806) of the web page view, and zoom out the screen shot to obtain a conversion image (807), which can be understood by referring to the actions of icon number 510 and icon number 520 in FIG. 5 above.

The electronic device 110 can determine the ratio of empty pixels included in the converted image (808). The action of the icon number 808 can be understood as an example of the action of "determining the ratio of unit components that meet the set conditions in relation to the plurality of unit components included in the converted image" (action of the icon number 530) in FIG. 5.

When the judgment result is that the converted image does not belong to the abnormal screen situation (809, NO), the monitoring can be terminated. On the contrary, when the judgment result is that the converted image belongs to the abnormal screen situation (809, YES), the electronic device 110 can disable the function and transmit the relevant log (810). The actions of icon number 809 and icon number 810 can be understood by referring to the actions of icon number 330 and icon number 340 in Figure 3 above.

On the other hand, the "related log" may include information that enables the subject reading the log to recognize that an abnormal screen has been output. However, there may be various embodiments regarding whether to transmit the log, the specific content of the log, and the recipient of the log, and a specific embodiment does not limit the scope of the present invention.

FIG. 9 is a diagram showing an example of the structure of an electronic device according to an embodiment.

9 , the electronic device 110 includes a transceiver 910, a processor 920, and a memory 930. The electronic device 110 can be connected to a customer's terminal 120 and an external device via the transceiver 910 to exchange data.

The processor 920 may include at least one of the devices described in Figures 1 to 8, or implement at least one of the methods described in Figures 1 to 8. The memory 930 may store information for implementing at least one of the methods described in Figures 1 to 8. The memory 930 may be a volatile memory or a non-volatile memory.

The processor 920 may execute a program to control the electronic device 110 for providing information. The code of the program executed by the processor 920 may be stored in the memory 930.

In addition, the electronic device 110 of the embodiment may further include an interface capable of providing information to users, etc.

On the other hand, the preferred embodiments of the present invention are disclosed in this specification and the accompanying drawings. Although specific terms are used, these terms are used in a general sense to easily explain the technical content of the present invention and help understand the invention, and are not intended to limit the scope of the present invention. In addition to the embodiments disclosed herein, those with common sense in the technical field to which the present invention belongs should understand that other variations can also be implemented based on the technical ideas of the present invention.

The server or terminal of the above embodiment may include a processor, a memory for storing and executing program data, a permanent storage such as a disk drive, a communication port for communicating with external devices, a user interface device such as a touch panel, a key, a button, etc. The method implemented by the software module or algorithm can be stored in a computer-readable recording medium as a computer-readable code or program command that can be executed on the above processor. Here, as computer-readable recording media, there are magnetic storage media (e.g., ROM (read-only memory), RAM (random-Access memory), floppy disk, hard disk, etc.) and optical readable media (e.g., CD-ROM, DVD: Digital Versatile Disc)). Computer-readable recording media are distributed in computer systems connected to the network, so that computer-readable codes can be stored and executed in a distributed manner. The media can be read by the computer, stored in the memory, and executed in the processor.

The present embodiment may be represented by a functional block structure and various processing steps. Such functional blocks may be implemented by different numbers of hardware and/or software structures that perform specific functions. For example, the embodiment may be implemented by an integrated circuit structure that can perform various functions such as memory, processing, logic, look-up tables, etc. through the control of one or more microprocessors or other control devices. The components may be executed by software programming or software components. Similarly, the present embodiment includes algorithms implemented by a combination of data structures, programs, routines, or other programming structures, and can therefore be implemented by programming or scripting languages such as C, C++, Java, assembler, Python, etc. In terms of functions, it can be implemented by algorithms executed in one or more processors. In addition, the present embodiment can use prior art to perform electronic environment settings, signal processing and/or data processing. Terms such as "mechanism", "component", "mechanism", and "structure" can be used widely and are not limited to mechanical and physical. The above terms can be associated with processors and include the meaning of a series of processes (routines) of software.

The above embodiment is only an example, and other embodiments may be implemented within the scope of the invention application described below.

100: System 110: Electronic device 120: Customer terminal 200: Hybrid application 210: Native application 220: Web-based application 230: JavaScript Bridge 310: Action 320: Action 330: Action 340: Action 410: Action 420: Action 510: Action 520: Action 530: Action 700: Example 710: Icon number 801: Action 802: Action 803: Action 804: Action 805: Action 806: Action 807: Action 808: Action 809: Action 810: Action 910: Transceiver 920: Processor 930: Memory

FIG. 1 is a schematic diagram showing a system 100 for monitoring whether a function is normally implemented in an embodiment. FIG. 2 is a flowchart for illustrating an operation of a hybrid application in an embodiment. FIG. 3 is a flowchart for illustrating an operation of a method for monitoring whether a function is normally implemented in an electronic device in an embodiment. FIG. 4 is a diagram for illustrating an operation of judging whether a function is normally implemented in a customer's terminal in an embodiment. FIG. 5 is a diagram for illustrating an operation of judging whether an abnormal screen is output in a customer's terminal in an embodiment. FIG. 6 is a diagram for illustrating an abnormal screen in an embodiment. FIG. 7 is a diagram for illustrating a situation where a function of an embodiment is not normally implemented in a customer's terminal. FIG. 8 is a diagram for illustrating a specific example of a method for monitoring whether a function is normally implemented in an electronic device in an embodiment. FIG. 9 is an example diagram of the structure of an electronic device in an embodiment.

310:Action

320:Action

330:Action

340:Action

Claims (16)

A method for processing information, which is performed in an electronic device, includes the following steps: Determining whether a function is normally implemented in a customer's terminal; and When it is determined that the function is not normally implemented in the customer's terminal, determining whether an abnormal screen is output in the customer's terminal. A method for processing information as claimed in claim 1, wherein the abnormal screen includes a screen having a fixed ratio or more of the screen filled with a single color. The method for processing information as in claim 1, wherein the step of determining whether the above function is normally implemented in the above customer's terminal includes the following steps: Confirming whether information notifying the above function is normally implemented is received from the above customer's terminal within a set time. A method for processing information as claimed in claim 3, wherein the information notifying that the above-mentioned function is implemented normally includes information indicating that the screen rendering process associated with the above-mentioned function is successful. The method for processing information as in claim 1, wherein the step of determining whether an abnormal screen is output in the above-mentioned customer's terminal includes the following steps: Obtaining a screenshot of the screen output in the above-mentioned customer's terminal; Reducing the above-mentioned screenshot to obtain a converted image; and Determining whether the above-mentioned converted image is an abnormal screen. The method for processing information as in claim 5, wherein the step of determining whether the converted image is an abnormal screen includes the following steps: Obtaining information on the colors corresponding to each of the plurality of unit components included in the converted image; and Based on the colors corresponding to each of the plurality of unit components, determining whether the ratio of unit components that meet the set conditions exceeds the set critical ratio. A method for processing information as claimed in claim 6, wherein the unit components satisfying the above-mentioned set conditions include unit components corresponding to colors in a set of one or more set colors. A method for processing information as claimed in claim 6, wherein the unit components that satisfy the above-mentioned conditions include unit components that do not specify any color. A method for processing information as claimed in claim 6, wherein the unit component belongs to a pixel. The method for processing information as in claim 1 further includes the following steps: Verifying whether the judgment result of whether an abnormal screen is output in the above-mentioned customer's terminal is accurate. A method for processing information as in claim 10, wherein the verification step includes the following steps: After providing the above function, obtaining information about the interaction between the above customer and the above customer's terminal; and Based on the above interaction information, predicting whether an abnormal screen has been output in the above customer's terminal. The method for processing information as in claim 10 further comprises the following steps: Based on the above verification, feedback information related to the process of determining whether an abnormal screen is output in the above customer's terminal is obtained. The method for processing information as in claim 1 further includes the following steps: When it is determined that an abnormal screen is output in the terminal of the above customer, the above function is disabled. A method for processing information as claimed in claim 1, wherein the electronic device detects in advance whether there is a defect related to the execution of the function, and if the defect is not detected, determines whether the function is normally implemented in the customer's terminal. A non-transitory computer-readable recording medium records a program for executing the method of claim 1 in a computer. An electronic device that processes information includes a transceiver, a memory for storing commands, and a processor. The processor is as follows: connected to the transceiver and the memory to determine whether a function is normally implemented in a customer's terminal; when it is determined that the function is not normally implemented in the customer's terminal, it determines whether an abnormal screen is output in the customer's terminal.