Operation method of electronic device for providing information, and electronic device supporting same

Abstract

According to the present disclosure, the disclosed method by which an electronic device provides information comprises the steps of: acquiring information about the number of times code exception processing for an application of a service provided by the electronic device occurs during a preset first time interval; if the number of times is greater than or equal to a threshold number of times, determining the proportion of user terminals in which code exception processing has occurred, during a preset second time interval, from among all user terminals in which the service is activated; and providing code exception processing notification information about the service if the proportion is greater than or equal to a first threshold proportion.

Description

Method of operation of an electronic device providing information and an electronic device supporting the same

[0001] The present invention relates to a method and device for providing information, and more particularly, to a method and an electronic device for providing notification information related to code exception handling for a service.

[0002] With the advancement of electronic technology, e-commerce has become a prominent part of the shopping experience. Customers can purchase items online without having to visit a physical shopping mall or market, and items purchased online are delivered to the customer's requested delivery address.

[0003] In the case of e-commerce, providing detailed and accurate product information significantly impacts customer satisfaction, so various methods for providing more detailed and accurate information are being discussed.

[0004] In this regard, reference may be made to prior literature such as KR101756594B1 or KR101500849B1.

[0005] According to the method of the present invention, an electronic device can provide notification information related to code exception handling for a service.

[0006] The technical problems to be achieved in the present invention are not limited to the technical problems mentioned above, and other technical problems not mentioned can be clearly understood by a person having ordinary skill in the technical field to which the present invention belongs from the description below.

[0007] Various embodiments may provide a method of operating an electronic device for providing information and an electronic device supporting the same.

[0008] A method for an electronic device to provide information according to various embodiments may include: obtaining information on the number of times code exception processing has occurred for an app of a service provided by the electronic device during a first preset time period; determining a ratio of user terminals in which code exception processing has occurred among all user terminals in which the service has been activated during a second preset time period when the number of times is equal to or greater than a threshold number; and providing code exception processing notification information for the service when the ratio is equal to or greater than a first threshold ratio.

[0009] In an exemplary embodiment, the step of obtaining information about the number of times may include: a step of checking a first cumulative number of times that code exception processing has occurred for the app until the start time of the first preset time interval; a step of checking a second cumulative number of times that code exception processing has occurred for the app until the end time of the first preset time interval; and a step of obtaining information about the number of times that code exception processing has occurred for the app during the first preset time interval based on the first cumulative number and the second cumulative number.

[0010] In an exemplary embodiment, information about the number of times may be obtained based on a query that monitors code exception handling for the app.

[0011] In an exemplary embodiment, the information providing method may further include a step of setting to call an API (Application Programming Interface) to check information about user terminals for which the service is activated during the preset second time period and information about user terminals for which code exception processing occurs for the service during the preset second time period, when the number of times is greater than or equal to the threshold number of times.

[0012] In an exemplary embodiment, the method for providing information further includes a step of providing information on one or more notification setting options for providing the code exception handling notification information, wherein the code exception handling notification information may be provided based on an input of an administrator selecting one notification setting option from among the one or more notification setting options.

[0013] In an exemplary embodiment, the one or more notification setting options may include a first setting option that sets the code exception handling notification information to always be provided, a second setting option that sets the code exception handling notification information to be omitted for the current version of the service and to be provided for a new version of the service, a third setting option that sets the code exception handling notification information to be omitted for the current version and to be provided for the new version, but to be omitted for the code exception handling notification information if a code exception handling issue related to the code exception handling notification information corresponds to a code exception handling issue that does not occur in the new version, and a fourth setting option that sets the code exception handling notification information to be omitted.

[0014] In an exemplary embodiment, the code exception handling notification information may include information about the domain of the app in which the code exception handling occurred, terminal identification information about the user terminal in which the code exception handling occurred, and code line identification information about at least one code among the codes for the domain in which the code exception handling by the user terminal is confirmed.

[0015] In an exemplary embodiment, the code exception handling notification information may further include information about a page provided on the service through the domain, and user identification information about a user of the user terminal.

[0016] In an exemplary embodiment, the method for providing information further comprises the step of providing a call notification related to code exception processing for the service when the ratio is greater than or equal to a second threshold ratio, wherein the second threshold ratio may be greater than the first threshold ratio.

[0017] In an exemplary embodiment, the method for providing information may further include a step of providing code exception handling statistical information for the service.

[0018] In an exemplary embodiment, the code exception processing statistical information may include information on the ratio of normal user terminals that did not experience code exception processing among user terminals that used the service for a certain period of time.

[0019] In an exemplary embodiment, information about the ratio of the normal user terminals may be provided in the form of graph information for the period of time.

[0020] In an exemplary embodiment, the code exception handling statistics information may be updated at regular intervals.

[0021] An electronic device providing information according to various embodiments comprises: a processor; and one or more memories storing one or more instructions, wherein the one or more instructions, when executed, cause the processor to perform: obtaining information on the number of times code exception processing has occurred for an app of a service provided by the electronic device during a first preset time period; determining a ratio of user terminals in which code exception processing has occurred among all user terminals in which the service has been activated during a second preset time period when the number of times is greater than or equal to a threshold number; and providing code exception processing notification information for the service when the ratio is greater than or equal to a first threshold ratio.

[0022] The various embodiments of the present disclosure described above are only some of the preferred embodiments of the present disclosure, and various embodiments reflecting the technical features of the various embodiments of the present disclosure can be derived and understood by a person having ordinary skill in the art based on the detailed description to be described below.

[0023] The present invention has a technical effect in that it can improve the convenience of monitoring and management of code exception handling by suggesting a method for an electronic device to provide notification information related to code exception handling for a service.

[0024] The effects that can be obtained from the present invention are not limited to the effects mentioned above, and other effects not mentioned can be clearly understood by a person having ordinary skill in the art to which the present invention belongs from the description below.

[0025] FIG. 1 is a drawing for explaining an information providing system in which an operating method of an electronic device for providing information according to various embodiments can be implemented.

[0026] FIG. 2 is a diagram illustrating the configuration of a server device (100) and a user device (200) according to various embodiments.

[0027] FIG. 3 is a diagram illustrating an operation method of a server device (100) for providing information according to various embodiments.

[0028] FIG. 4 is a flowchart illustrating a process of providing code exception processing notification information based on an operation of a server device (100) calling an API (Application Programming Interface) that checks information about a user terminal where a service is activated and a user terminal where code exception processing occurs.

[0029] FIG. 5 is a diagram illustrating an example of code exception handling notification information provided by a server device (100).

[0030] FIG. 6 is a diagram illustrating an example of code exception processing statistical information provided by a server device (100).

[0031] The following embodiments combine components and features of various embodiments in a predetermined form. Each component or feature may be considered optional unless explicitly stated otherwise. Each component or feature may be implemented without being combined with other components or features. Furthermore, various embodiments may be formed by combining some components and features. The order of operations described in various embodiments may be changed. Some components or features of one embodiment may be included in another embodiment or may be replaced with corresponding components or features of another embodiment.

[0032] In the description of the drawings, procedures or steps that may obscure the gist of various embodiments are not described, and procedures or steps that can be understood by a person with ordinary skill in the art are also not described.

[0033] Throughout the specification, when a part is said to "comprising" (or including) a certain component, this does not mean that other components are excluded, but rather that other components can be included, unless specifically stated otherwise. In addition, terms such as "...part," "...unit," and "module" described in the specification mean a unit that processes at least one function or operation, which may be implemented by hardware, software, or a combination of hardware and software. In addition, the words "a" or "an," "one," "the," and similar related words may be used in the singular and plural sense in the context of describing various embodiments (especially in the context of the claims below) unless otherwise indicated herein or clearly contradicted by context.

[0034] Hereinafter, preferred embodiments according to various embodiments will be described in detail with reference to the attached drawings. The detailed description set forth below, together with the attached drawings, is intended to explain exemplary embodiments of various embodiments and is not intended to represent the only embodiments.

[0035] Additionally, specific terms used in various embodiments are provided to aid understanding of the various embodiments, and the use of such specific terms may be changed in other forms without departing from the technical spirit of the various embodiments.

[0036] FIG. 1 is a drawing for explaining an information providing system in which an operating method of an electronic device for providing information according to various embodiments can be implemented.

[0037] Referring to FIG. 1, the information providing system according to various embodiments may be implemented in various types of electronic devices. For example, the information providing system may be implemented in a server device (100) and a user device (200). In other words, the server device (100) and the user device (200) may perform operations according to various embodiments of the present disclosure based on the information providing system implemented in each device. For example, in various embodiments according to the present disclosure, the server device (100) may provide notification information related to code exception processing occurring in relation to a service app to a user device (200) corresponding to an administrator. Meanwhile, the information providing system according to various embodiments is not limited to that illustrated in FIG. 1, and may be implemented in a wider variety of electronic devices and servers.

[0038] According to various embodiments, a server device (100) may be a device that performs wireless and wired communication with a plurality of user devices (200) and includes storage with a large storage capacity. For example, the server device (100) may be a cloud device that is linked with a plurality of user devices (200).

[0039] The user device (200) according to various embodiments may be a device that can be used by individual users, such as a desktop PC, tablet PC, or mobile terminal. In addition, other electronic devices that perform similar functions may be used as the user device (200).

[0040] An information providing system according to various embodiments may include various modules for operation. The modules included in the information providing system may be computer codes or one or more instructions implemented so that a physical device (e.g., a server device (100) and a user device (200)) in which the information providing system is implemented (or included in a physical device) can perform a specified operation. In other words, a physical device in which the information providing system is implemented stores a plurality of modules in a memory in the form of computer codes, and when the plurality of modules stored in the memory are executed, the plurality of modules can cause the physical device to perform specified operations corresponding to the plurality of modules.

[0041] FIG. 2 is a diagram illustrating the configuration of a server device (100) and a user device (200) according to various embodiments.

[0042] Referring to FIG. 2, the server device (100) and the user device (200) may include an input / output unit (210), a transceiver (or communication unit) (220), storage (230), and a processor (240).

[0043] The input / output unit (210) may be various interfaces or connection ports that receive user input or output information to the user. The input / output unit (210) may include an input module and an output module, and the input module receives user input from the user. The user input may be in various forms, including key input, touch input, and voice input. Examples of input modules that can receive such user input include not only a traditional keypad, keyboard, or mouse, but also a touch sensor that detects the user's touch, a microphone that receives a voice signal, a camera that recognizes gestures through image recognition, a proximity sensor including at least one of an illuminance sensor or an infrared sensor that detects the user's approach, a motion sensor that recognizes the user's movement through an acceleration sensor or a gyro sensor, and various other forms of input means that detect or receive various forms of user input, and the input module according to an embodiment of the present disclosure may include at least one of the devices listed above. Here, the touch sensor can be implemented as a piezoelectric or electrostatic touch sensor that detects touch through a touch panel or touch film attached to the display panel, an optical touch sensor that detects touch by an optical method, etc. In addition, the input module can be implemented in the form of an input interface (USB port, PS / 2 port, etc.) that connects an external input device that receives user input instead of a device that detects user input on its own. In addition, the output module can output various types of information. The output module can include at least one of a display that outputs an image, a speaker that outputs a sound, a haptic device that generates vibration, and various other forms of output means. In addition, the output module can be implemented in the form of a port-type output interface that connects the individual output means described above.

[0044] For example, an output module in the form of a display can display text, still images, and moving images. The display can include at least one of a liquid crystal display (LCD), a light emitting diode (LED) display, an organic light emitting diode (OLED) display, a flat panel display (FPD), a transparent display, a curved display, a flexible display, a 3D display, a holographic display, a projector, and various other devices capable of performing an image output function. Such a display can also be in the form of a touch display that is integrated with a touch sensor of the input module.

[0045] The transceiver (220) can communicate with other devices. Accordingly, the server device (100) and the user device (200) can transmit and receive information with other devices via the transceiver (220). For example, the server device (100) and the user device (200) can communicate with each other or with other devices using the transceiver (220).

[0046] Here, communication, i.e., transmission and reception of data, can be performed wired or wirelessly. To this end, the transceiver (220) may include a wired communication module that connects to the Internet, etc., via a LAN (Local Area Network), a mobile communication module that connects to a mobile communication network via a mobile communication base station and transmits and receives data, a short-range communication module that uses a WLAN (Wireless Local Area Network) series communication method such as Wi-Fi or a WPAN (Wireless Personal Area Network) series communication method such as Bluetooth or Zigbee, a satellite communication module that uses a GNSS (Global Navigation Satellite System) such as a GPS (Global Positioning System), or a combination thereof.

[0047] Storage (230) can store various types of information. Storage (230) can store data temporarily or semi-permanently. For example, the storage (230) of the server device (100) can store an operating program (OS: Operating System) for operating the server device (100), data for hosting a website, a program for generating Braille, or data related to an application (e.g., a web application). In addition, the storage (230) can store modules in the form of computer code, as described above.

[0048] Examples of storage (230) may include a hard disk drive (HDD), a solid state drive (SSD), flash memory, read-only memory (ROM), random access memory (RAM), etc. This storage (230) may be provided as a built-in type or a detachable type.

[0049] The processor (240) controls the overall operation of the server device (100) and the user device (200). To this end, the processor (240) may perform calculations and processing of various types of information and control the operation of components of the server device (100). For example, the processor (240) may execute a program or application for providing information. The processor (240) may be implemented as a computer or a similar device according to hardware, software, or a combination thereof. In terms of hardware, the processor (240) may be implemented in the form of an electronic circuit that processes electrical signals to perform control functions, and in terms of software, it may be implemented in the form of a program that drives the hardware processor (240). Meanwhile, unless otherwise specified in the following description, the operations of the server device (100) and the user device (200) may be interpreted as being performed under the control of the processor (240). That is, when the modules implemented in the above-described information provision system are executed, the modules can be interpreted as controlling the processor (240) to perform the following operations on the server device (100) and the user device (200).

[0050] In summary, the various embodiments may be implemented through various means. For example, the various embodiments may be implemented through hardware, firmware, software, or a combination thereof.

[0051] In the case of hardware implementation, the methods according to various embodiments may be implemented by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, etc.

[0052] When implemented via firmware or software, the methods according to various embodiments may be implemented in the form of modules, procedures, or functions that perform the functions or operations described below. For example, software code may be stored in memory and executed by a processor. The memory may be located within or external to the processor and may exchange data with the processor via various known means.

[0053] Below, various embodiments are described in more detail based on the above technical concepts. The previously described concepts may be applied to the various embodiments described below. For example, operations, functions, terms, etc. not defined in the various embodiments described below may be performed and explained based on the previously described concepts.

[0054] The following description describes various embodiments assuming that the server device (100) performs an operation of providing code exception handling notification information for a service, and according to various embodiments, a user device (200) for a service manager can output and provide code exception handling notification information received from the server device (100).

[0055] FIG. 3 is a diagram illustrating an operation method of a server device (100) for providing information according to various embodiments.

[0056] According to FIG. 3, the server device (100) obtains information on the number of times code exception processing has occurred for an app of a service during a first preset time period (301), and if the number is greater than or equal to a threshold number, determines the ratio of user terminals in which code exception processing has occurred among all user terminals for which the service is activated during a second preset time period (303), and if the ratio is greater than or equal to the first threshold ratio, code exception processing notification information for the service can be provided (305).

[0057] According to FIG. 3, the operation of the server device (100) providing code exception processing notification information for a service may be performed for a service provided by the server device (100) or a service related to the server device (100), and the service may correspond to a service in which multiple users using the service can order and purchase multiple items sold in the service. The multiple items sold in the service are not limited to the type or type of the items, and may include various types or types of items registered by sellers to sell the items.

[0058] According to various embodiments, in operation 301, the server device (100) may obtain information about the number of times a code exception processing occurred for an app of a service during a preset first time interval.

[0059] For example, in operation 301, the server device (100) may obtain information on the number of times code exception handling has occurred for the app of the service during the first preset time interval by checking the first cumulative number of times code exception handling has occurred for the app until the start time of the first preset time interval and the second cumulative number of times code exception handling has occurred for the app until the end time of the first preset time interval, thereby obtaining information on the number of times code exception handling has occurred for the app during the first preset time interval. That is, the server device (100) continuously monitors the cumulative number of times code exception handling has occurred for the app, and when a time interval for which it is desired to obtain information on the number of times code exception handling has occurred for the app is determined, the server device (100) checks the cumulative number of times code exception handling has occurred for the app at the start time and the end time of the corresponding time interval, respectively, and calculates the difference between the cumulative numbers, thereby obtaining information on the number of times code exception handling has occurred for the app during the corresponding time interval.

[0060] For example, the cumulative number of times code exception handling occurs for an app can be monitored based on a query that monitors code exception handling for the app in conjunction with a server device (100). That is, the server device (100) can be equipped with a query that performs an operation of monitoring code exception handling for an app of a service, and can continuously track the occurrence of code exception handling for the app through the query.

[0061] For example, the information about the number of times code exception handling has occurred for the app of the service that the server device (100) confirms in operation 301 may include information about the number of times code exception handling has occurred in the entire app of the service, or may include information about the number of times code exception handling has occurred in a certain domain for the app of the service. The server device (100) may check the number of times code exception handling has occurred based on the app of the service, and compare the number of times code exception handling has occurred in the entire app of the service with the threshold number in operation 303, or may designate a specific domain among the app of the service and check the number of times code exception handling has occurred based on the designated specific domain, and compare the number of times code exception handling has occurred in the specific domain with the threshold number in operation 303. In this case, the threshold number in operation 303 may have a different value depending on whether it is based on the app of the service or on a specific domain included in the app of the service.

[0062] For example, when the server device (100) checks the number of times code exception processing has occurred based on a specific domain among the apps of the service, the server device (100) can manage the value of the first time interval for obtaining the number of times code exception processing has occurred to be set differently depending on which domain is specified, taking into account the characteristics of the specified domain.

[0063] Specifically, in operation 301, when the server device (100) designates a specific domain among the apps of the service and checks the number of times code exception handling has occurred based on the designated specific domain, thereby setting the number of times code exception handling has occurred in the specific domain to be compared with the threshold number of times in operation 303, the server device (100) may reflect the service usage characteristics of users for the designated specific domain when setting the first time interval in operation 301. For example, the server device (100) may determine how much the code written for each domain is used by multiple users using the service, targeting multiple domains included in the app of the service, and may set a smaller value of the first time interval for obtaining the number of times code exception handling has occurred in a domain with a high usage rate by multiple users, and may set a larger value of the first time interval for obtaining the number of times code exception handling has occurred in a domain with a low usage rate by multiple users.

[0064] In the case of a domain with a high usage rate by multiple users, by setting the value of the first time interval for obtaining the number of occurrences of code exception handling to a relatively small value, the problem that the number of occurrences of code exception handling frequently exceeds a threshold number due to a large number of users for the domain and thus API calls for providing code exception handling notification information are unnecessarily activated can be prevented. Conversely, in the case of a domain with a low usage rate by multiple users, by setting the value of the first time interval for obtaining the number of occurrences of code exception handling to a relatively large value, the problem that the number of occurrences of code exception handling rarely exceeds a threshold number due to a small number of users for the domain and thus API calls for providing code exception handling notification information are effectively deactivated can be prevented.

[0065] According to various embodiments, in operation 303, if the number of times code exception processing has occurred for an app of the service is greater than or equal to a threshold number, the server device (100) may determine the ratio of user terminals in which code exception processing has occurred among all user terminals in which the service has been activated during a preset second time period.

[0066] For example, the server device (100) may operate to call an API (Application Programming Interface) that can check information about user terminals on which the service is activated and user terminals on which code exception processing occurs in order to determine the ratio of user terminals on which code exception processing occurs among all user terminals on which the service is activated during the preset second time interval according to operation 303. That is, in operation 303, the server device (100) may be configured to call an API for checking information about user terminals on which the service is activated during the preset second time interval and information about user terminals on which code exception processing occurs for the service during the preset second time interval when the number of times code exception processing occurs for the app of the service is greater than or equal to a threshold number.

[0067] FIG. 4 is a flowchart illustrating a process of providing code exception processing notification information based on an operation of a server device (100) calling an API (Application Programming Interface) that checks information about a user terminal where a service is activated and a user terminal where code exception processing occurs.

[0068] In FIG. 4, the server device (100) can check the occurrence of code exception processing for the app through a query that monitors code exception processing for the app in connection with the server device (100) (401). If the number of times that code exception processing for the app of the service is confirmed to have occurred through the query during a first preset time interval exceeds a threshold number, the server device (100) can call an API that checks information about the user terminals where the service is activated and the user terminals where code exception processing occurs (403). Based on the called API, the server device (100) can check the user terminals where the service is activated and the user terminals where code exception processing occurs for the service during a second preset time interval, and if the ratio between them is calculated and exceeds the threshold ratio, code exception processing notification information can be provided to the administrator of the app or the app's domain as in operation 305 described below (405).

[0069] For example, when the server device (100) checks the number of times code exception handling has occurred based on a specific domain among the apps of the service, the server device (100) can manage to set a different value for the threshold number of times for comparison of the number of times code exception handling has occurred depending on which domain is specified, taking into account the characteristics of the specified domain.

[0070] Specifically, in operation 301, when the server device (100) designates a specific domain among the apps of the service and checks the number of times code exception handling has occurred based on the designated specific domain, thereby setting the number of times code exception handling has occurred in the specific domain to be compared with the threshold number in operation 303, the server device (100) may reflect the service usage characteristics of users for the designated specific domain when setting the threshold number in operation 303. For example, the server device (100) may determine how much the code written for each domain is used by multiple users using the service, targeting multiple domains included in the apps of the service, and may set the value of the threshold number for obtaining the number of times code exception handling has occurred to be larger for a domain with a high usage rate by multiple users, and may set the value of the threshold number for obtaining the number of times code exception handling has occurred to be smaller for a domain with a low usage rate by multiple users.

[0071] In the case of a domain with a high usage rate by multiple users, by setting the value of the threshold number for comparison to a relatively large value, the problem that the number of times code exception handling occurs frequently exceeds the threshold number due to the large number of users for the domain, resulting in unnecessary activation of API calls for providing code exception handling notification information can be prevented. Conversely, in the case of a domain with a low usage rate by multiple users, by setting the value of the threshold number for comparison to a relatively small value, the problem that the number of times code exception handling occurs rarely exceeds the threshold number due to the small number of users for the domain, resulting in virtual inactivation of API calls for providing code exception handling notification information can be prevented.

[0072] According to various embodiments, in operation 305, the server device (100) may provide code exception processing notification information for the service when the ratio of user terminals in which code exception processing occurs among all user terminals in which the service is activated during the preset second time period is equal to or greater than a first threshold ratio.

[0073] For example, the code exception handling notification information for the service provided by the server device (100) according to operation 305 may correspond to information provided to an administrator who manages the service or the service's app.

[0074] For example, in operation 305, the server device (100) may provide code exception handling notification information for a service to an administrator in a different manner depending on a notification setting option selected by the administrator. That is, in the process of providing code exception handling notification information to an administrator, the administrator may select one notification setting option from among various notification setting options, and operation 305 of the server device (100) may be performed in accordance with one notification setting option selected by the administrator. The server device (100) may provide information on one or more notification setting options for providing code exception handling notification information, and the code exception handling notification information of operation 305 may be provided based on an input of an administrator who selects one notification setting option from among one or more notification setting options.

[0075] At this time, examples of the above notification setting options may include 1) a first setting option that sets the code exception handling notification information to always be provided, 2) a second setting option that sets the code exception handling notification information to be omitted for the current version of the service but to be provided for a new version of the service, 3) a third setting option that sets the code exception handling notification information to be omitted for the current version of the service but to be provided for a new version of the service but to be omitted if the code exception handling notification information related to the code exception handling notification information corresponds to a code exception handling issue that does not occur in the new version of the service, and 4) a fourth setting option that sets the code exception handling notification information to be omitted altogether.

[0076] For example, the code exception handling notification information provided by the server device (100) according to operation 305 may include 1) information on the domain of the app where the code exception handling occurred, 2) terminal identification information on the user terminal where the code exception handling occurred, 3) code line identification information on at least one code for which code exception handling by the user terminal is confirmed among the codes for the domain of the app where the code exception handling occurred, 4) information on a page provided on the service through the domain of the app where the code exception handling occurred, and / or 5) user identification information on the user of the user terminal.

[0077] For example, the server device (100) may set a second threshold ratio that is greater than the first threshold ratio in operation 305, and if the ratio of user terminals in which code exception processing occurs among all user terminals in which the service is activated during the second preset time period is greater than the second threshold ratio, a more specific and direct notification may be provided to the administrator beyond providing code exception processing notification information. For example, if the ratio of user terminals in which code exception processing occurs among all user terminals in which the service is activated during the second preset time period is greater than or equal to the second threshold ratio that is greater than the first threshold ratio, the server device (100) may provide the administrator with a call notification related to code exception processing for the service.

[0078] FIG. 5 is a diagram illustrating an example of code exception handling notification information provided by a server device (100).

[0079] In FIG. 5, the code exception handling notification information provided by the server device (100) may include code line identification information for at least one code for which code exception handling by the user terminal has been confirmed among the codes for the domain of the app in which code exception handling has occurred (501). That is, identification information for indicating a code line for which code exception handling has been confirmed among the codes written for the domain may be included in the code exception handling notification information in a format such as 501, and such code line identification information may identify the #th code line for which exception handling has been confirmed in the code of the domain by displaying it in a format such as dart: #.

[0080] In addition, in the code exception handling notification information provided by the server device (100) in FIG. 5, in addition to the code exception handling notification information as described above, information indicating the domain of the app where the code exception handling occurred, the user terminal where the code exception handling occurred, the page provided on the service through the domain of the app where the code exception handling occurred, and / or the user of the user terminal, etc. may also be included (503).

[0081] Meanwhile, when the server device (100) performs an operation of providing code exception handling notification information according to FIG. 3, it may also perform an operation of providing statistical information related to code exception handling. That is, the server device (100) may operate to provide code exception handling statistical information for a service based on the status of code exception handling occurrence for the service confirmed in the process of performing the operation of providing code exception handling notification information.

[0082] For example, the code exception processing statistical information provided by the server device (100) may include information on the ratio of abnormal user terminals in which code exception processing occurred among user terminals that used the service during a specific period, or the ratio of normal user terminals in which code exception processing did not occur among user terminals that used the service during a specific period. In this case, the information on the ratio of abnormal user terminals or normal user terminals may be provided in the form of a graph for a certain period so that the rate of change over a certain period can be confirmed, and the information on the ratio of abnormal user terminals or normal user terminals may be set to be updated at a certain cycle.

[0083] FIG. 6 is a diagram illustrating an example of code exception processing statistical information provided by a server device (100).

[0084] The code exception handling statistics information of FIG. 6 may correspond to information that represents the code exception handling statistics information, which is continuously updated on a daily basis, in the form of a graph for a two-week period. In this case, the value of the code exception handling statistics corresponding to each date may correspond to a value representing the ratio of normal user terminals that did not experience code exception handling among user terminals that used the service during a specific period prior to each date (600). For example, in FIG. 6, the value of the code exception handling statistics corresponding to each date may be a value representing the ratio of normal user terminals that did not experience code exception handling among user terminals that used the service during the three days or one week prior to each date.

[0085] Through code exception handling statistics in the form of Figure 6, an administrator can check changes in the ratio of normal user terminals where code exception handling did not occur on the service.

[0086] It is obvious that each piece of information can be combined in various forms during the process of performing the operation method in which the server device (100) provides code exception processing notification information according to FIGS. 3 to 6.

[0087] The embodiments of the present invention disclosed in this specification and drawings are merely specific examples to easily explain the technical content of the present invention and to facilitate understanding of the present invention, and are not intended to limit the scope of the present invention. In other words, it will be apparent to those skilled in the art that other modifications based on the technical concept of the present invention are possible. Furthermore, the above-described embodiments can be combined and operated as needed. For example, all embodiments of the present invention can be implemented as a system by combining parts with each other.

[0088] In addition, the method according to the system or the like according to the present invention may be implemented in the form of program commands that can be executed through various computer means and recorded on a computer-readable medium.

[0089] As such, various embodiments of the present invention can be implemented as computer-readable code on a computer-readable recording medium in certain aspects. A computer-readable recording medium is any data storage device capable of storing data that can be read by a computer system. Examples of computer-readable recording media can include read-only memories (ROMs), random access memories (RAMs), compact disk-read-only memories (CD-ROMs), magnetic tapes, floppy disks, optical data storage devices, and carrier waves (such as data transmission over the Internet). A computer-readable recording medium can also be distributed across network-connected computer systems, so that the computer-readable code is stored and executed in a distributed manner. Additionally, functional programs, codes, and code segments for achieving various embodiments of the present invention can be easily interpreted by programmers skilled in the field to which the present invention is applied.

[0090] It will also be appreciated that devices and methods according to various embodiments of the present invention can be implemented in the form of hardware, software, or a combination of hardware and software. Such software may be stored in a volatile or non-volatile storage device, such as a ROM, for example, regardless of whether it is erasable or rewritable, or in a memory, such as a RAM, a memory chip, a device, or an integrated circuit, or in a storage medium that is optically or magnetically recordable and simultaneously machine-readable (e.g., a computer), such as a compact disk (CD), a DVD, a magnetic disk, or a magnetic tape. It will be appreciated that methods according to various embodiments of the present invention can be implemented by a computer including a control unit and a memory, or a vehicle including such a memory or a computer, and such a memory is an example of a machine-readable storage medium suitable for storing a program or programs including commands for implementing embodiments of the present invention.

[0091] Accordingly, the present invention encompasses a program containing code for implementing the devices or methods described in the claims of this specification, and a machine-readable storage medium (e.g., a computer) storing such a program. Furthermore, such a program may be transmitted electronically via any medium, such as a communication signal transmitted via a wired or wireless connection, and the present invention appropriately encompasses equivalents thereof.

[0092] Although the present invention has been described above with reference to embodiments, the embodiments of the present invention disclosed in this specification and drawings are merely specific examples to easily explain the technical content of the present invention and assist in understanding the present invention, and are not intended to limit the scope of the present invention. Furthermore, the embodiments of the present invention described above are merely exemplary, and those skilled in the art will understand that various modifications and equivalent embodiments are possible. Therefore, the true technical protection scope of the present invention should be defined by the following claims.

Claims

1. In the method of providing information by an electronic device, A step of obtaining information on the number of times a code exception processing occurred for an app of a service provided by the electronic device during a preset first time period; If the above number of times is greater than or equal to the threshold number, a step of determining the ratio of user terminals in which code exception processing occurred among all user terminals in which the service was activated during the preset second time period; and If the ratio is greater than or equal to the first threshold ratio, a step of providing code exception processing notification information for the service is included. How to provide information.

2. In paragraph 1, The step of obtaining information about the above number of times is: A step of checking the first cumulative number of times that a code exception handling has occurred for the app up to the start time of the first preset time interval; A step of checking the second cumulative number of times that a code exception handling has occurred for the app until the end of the first preset time interval; A step of obtaining information on the number of times that code exception processing for the app occurred during the first preset time interval, based on the first accumulated number of times and the second accumulated number of times. How to provide information.

3. In paragraph 1, Information about the above number of times is obtained based on a query that monitors code exception handling for the above app. How to provide information.

4. In paragraph 1, The method of providing the above information is: If the number of times is greater than or equal to the threshold number, the step of setting to call an API (Application Programming Interface) for checking information about user terminals for which the service is activated during the preset second time period and information about user terminals for which code exception processing occurs for the service during the preset second time period is further included. How to provide information 5. In paragraph 1, The method of providing the above information is: Further comprising a step of providing information about one or more notification setting options for providing the above code exception handling notification information, The above code exception handling notification information is provided based on the administrator's input of selecting one notification setting option from among the one or more notification setting options. How to provide information.

6. In paragraph 5, One or more of the above notification settings options: A first configuration option that sets the above code exception handling notification information to always be provided; A second setting option that sets the provision of the above code exception handling notification information to be omitted for the current version of the above service and to be provided for the new version of the above service; A third setting option that sets the provision of the code exception handling notification information to be omitted for the current version and to be provided for the new version, but to omit the provision of the code exception handling notification information if the code exception handling issue related to the code exception handling notification information corresponds to a code exception handling issue that does not occur in the new version, and Including a fourth setting option that sets to omit the provision of the above code exception handling notification information, How to provide information.

7. In paragraph 1, The above code exception handling notification information is: Information about the domain of the app where the code exception occurred; Terminal identification information for the user terminal where the code exception handling occurred, and Among the codes for the above domain, including code line identification information for at least one code for which code exception handling by the user terminal has been confirmed, How to provide information.

8. In paragraph 7, The above code exception handling notification information is: Information about the pages provided on the above service through the above domain, and Further including user identification information for the user of the user terminal, How to provide information.

9. In paragraph 1, The method of providing the above information is: If the above ratio is greater than or equal to the second threshold ratio, further comprising a step of providing a call notification related to code exception processing for the service; The second critical ratio is greater than the first critical ratio, How to provide information.

10. In paragraph 1, The method of providing the above information is: Further comprising the step of providing code exception handling statistics information for the above service, How to provide information.

11. In paragraph 10, The above code exception processing statistics information includes information on the ratio of normal user terminals that did not experience code exception processing among user terminals that used the service for a certain period of time. How to provide information.

12. In paragraph 11, Information on the ratio of the above normal user terminals is provided in the form of graph information for the above period of time. How to provide information.

13. In paragraph 10, The above code exception handling statistics are updated at regular intervals. How to provide information.

14. In an electronic device that provides information, processor; and Contains one or more memories that store one or more instructions, The one or more instructions, when executed, cause the processor to: A step of obtaining information on the number of times a code exception processing occurred for an app of a service provided by the electronic device during a preset first time period; If the above number of times is greater than or equal to the threshold number, a step of determining the ratio of user terminals in which code exception processing occurred among all user terminals in which the service was activated during the preset second time period; and If the above ratio is greater than or equal to the first threshold ratio, controlling the processor to perform a step of providing code exception processing notification information for the service. Electronic devices.

Images