TWI900978B - Operating method for electronic apparatus for providing information and electronic apparatus supporting thereof - Google Patents

Abstract

According to the present invention, a method is disclosed, which is for providing information by an electronic device, and includes the following steps: obtaining API class analysis information for analyzing the API field that will provide log information in the API class of the API action used in the service provided by the above-mentioned electronic device; based on the above-mentioned API class analysis information, confirming the first log field indication information including one or more API fields indicating that the API field provides log information, and the one or more API fields correspond to the first API class of the first API action used in the above-mentioned service; and when confirming that the above-mentioned first API class is set to the API class that will provide log information, providing the first log information corresponding to the above-mentioned first API class based on the above-mentioned first log field indication information.

Description

Method for operating an electronic device for providing information and electronic device supporting the method

The present invention relates to a method and apparatus for providing information. More specifically, the present invention relates to a method and apparatus for an electronic device to provide log information corresponding to one or more API fields selected from among API fields, wherein the one or more API fields correspond to API classes related to API (Application Programming Interface) actions in a service.

With the development of electronic technology, e-commerce has become a major player in the shopping world. Customers can purchase items online without having to visit a shopping mall or market in person, and the items purchased online will be delivered to the customer's desired delivery location.

For e-commerce, detailed and accurate processing of product information has a significant impact on service satisfaction, so various solutions for more detailed and accurate information processing are being discussed.

For related information, please refer to previous literature such as KR101756594B1 or KR101500849B1.

[Identify the problem you want to solve]

According to the method of the present invention, the electronic device can provide log information corresponding to an API field selected from one or more API fields, wherein the one or more API fields correspond to an API class related to an API (Application Programming Interface) action in a service.

The technical issues to be achieved by this invention are not limited to those mentioned above. Those skilled in the art to which this invention relates will clearly understand other technical issues not mentioned based on the following description. [Technical Means for Solving the Problem]

Various embodiments may provide an operating method of an electronic device for providing information and an electronic device supporting the method.

The method for an electronic device to provide information in various embodiments may include the following steps: obtaining API class analysis information for analyzing an API field for providing log information in an API class of an API (Application Programming Interface) action used in a service provided by the electronic device; based on the API class analysis information, confirming first log field indication information including one or more API fields indicating an API field for providing log information, wherein the one or more API fields correspond to a first API class for a first API action used in the service; and upon confirming that the first API class is set as the API class for providing log information, providing first log information corresponding to the first API class based on the first log field indication information.

In an exemplary embodiment, the above-mentioned API class analysis information can be set based on a code scan analysis of the API field corresponding to the API class.

In an exemplary embodiment, the information providing method may further include the following step: confirming the second log field indication information of the following API field among the one or more API fields, that is, the API field indicating that log information is not provided because the log information generated by the API field includes redundant information.

In an exemplary embodiment, the redundant information may include personal information of users of the services.

In an exemplary embodiment, the above-mentioned information providing method may further include the following steps: confirming the third log field indication information of the following API fields among the above-mentioned one or more API fields, that is, the API field indicated as providing log information or not providing log information according to the administrator's API field selection input data.

In an exemplary embodiment, the API field selection input information may be configured as follows: API fields are selected or excluded based on characteristic information of the API class.

In an exemplary embodiment, for a second API class having the same characteristic information as the first API class, the API field selection input information may be applied identically to the second API class.

In an exemplary embodiment, when no API field for providing log information is identified in the first API class based on the API class analysis information, the first log field indication information may indicate that all of the one or more API fields provide log information.

In an exemplary embodiment, the step of providing the above-mentioned first log information may include the following steps: providing the above-mentioned first log information based on the above-mentioned first log field indication information, the second log field indication information and the third log field indication information, the second log field indication information includes the following API fields among the above-mentioned one or more API fields, that is, the API field that indicates not to provide log information because the log information generated by the API field includes redundant information, and the third log field indication information includes the following API fields, that is, the API field that indicates to provide log information or to indicate not to provide log information based on the administrator's API field selection input information.

In an exemplary embodiment, the first log field indication information, the second log field indication information, and the third log field indication information may be applied in sequence according to their priorities.

In an exemplary embodiment, the priority of the second log field indication information may be set higher than the priority of the third log field indication information, and the priority of the third log field indication information may be set higher than the priority of the first log field indication information.

In an exemplary embodiment, the first log information may include log information generated by each API field, which is identified as providing log information in the first API category based on the first log field indication information, the second log field indication information, and the third log field indication information.

In an exemplary embodiment, the information providing method may further include the following steps: setting registration information, which registers multiple API classes including the first API class as API classes that will provide log information; and based on the registration information, confirming that the first API class is set as the API class that will provide log information.

In an exemplary embodiment, the information providing method may further include the following step: based on the log field indication information for the API class, setting an adapter for providing log information corresponding to the API class.

In an exemplary embodiment, the step of providing the first log information may include the following steps: providing the first log information based on the adapter.

The electronic device for providing information in various embodiments may include: a processor; and one or more memories storing one or more instructions; when executing the one or more instructions, controlling the processor to enable the processor to perform the following steps: in an API (Application Programming Interface) used in the service provided by the electronic device; API class (class) for an API interface action ("Service Interface") is obtained, API class analysis information for analyzing an API field (field) that will provide log information is obtained; based on the above API class analysis information, first log field indication information including one or more API fields indicating an API field that will provide log information is confirmed, and the one or more API fields correspond to a first API class for a first API action used in the above service; and when it is confirmed that the above first API class is set as the API class that will provide log information, first log information corresponding to the above first API class is provided based on the above first log field indication information.

The various embodiments of the present invention described above are merely some of the preferred embodiments of the present invention. Those skilled in the art can derive various embodiments reflecting the technical features of the various embodiments of the present invention based on the detailed description below. [Effects of the Invention]

The present invention discloses a method for an electronic device to provide log information corresponding to selected API fields from one or more API fields. The one or more API fields correspond to API classes related to API (Application Programming Interface) actions in a service. An administrator can selectively receive log information only for required API fields, which has the technical effect of reducing the load brought about by providing log information.

The effects that can be achieved by the present invention are not limited to the effects mentioned above. Those skilled in the art can clearly understand other effects not mentioned based on the following description.

The following embodiments combine the components and features of various embodiments into specific configurations. Unless explicitly stated otherwise, each component or feature is considered optional. Each component or feature may be implemented without being combined with other components or features. Furthermore, various embodiments may be constructed by combining some components and features. The order of actions described in the various embodiments may be varied. Some components or features of one embodiment may be included in other embodiments, or may be interchanged with corresponding components or features of other embodiments.

In the description of the accompanying drawings, no procedures or steps are described that would obscure the gist of the various embodiments, nor are any procedures or steps described that are understandable to a person having ordinary skill in the art.

Throughout this specification, when it is stated that a certain part "comprising or including" a certain component, unless otherwise stated, it means that other components may be further included, and does not exclude other components. In addition, terms such as "...part", "...device", and "module" described in the specification refer to a unit that processes at least one function or action, which can be implemented by hardware, software, or a combination of hardware and software. In addition, in the text describing various embodiments (especially in the scope of the invention application below), unless otherwise indicated in this specification or not explicitly contradicted in the text, "a (or an)", "one (one)", "the (the)" and similar conjunctions can be used to include both the singular and the plural meaning.

Hereinafter, with reference to the accompanying drawings, preferred embodiments of the present invention will be described in detail. The detailed description disclosed below together with the accompanying drawings is intended to illustrate exemplary embodiments of the present invention and is not intended to represent the only embodiment.

Furthermore, specific terms used in various embodiments are provided to facilitate understanding of the various embodiments, and the use of such specific terms may be changed into other forms without departing from the technical concepts of the various embodiments.

FIG. 1 is a diagram illustrating an information providing system that can implement an operation method of an electronic device for providing information according to various embodiments.

Referring to Figure 1 , the information provision systems of various embodiments can be implemented in various types of electronic devices. For example, the information provision system can be implemented in server device 100 and user device 200 . In other words, server device 100 and user device 200 can perform the operations of the various embodiments of the present invention based on the information provision systems implemented in each device. Furthermore, the information provision systems of various embodiments are not limited to those shown in Figure 1 and can be implemented in a wider variety of electronic devices and servers.

The server device 100 of various embodiments may be a device that performs wireless and wired communication with a plurality of user devices 200 and includes a storage device with a large unit of storage capacity. For example, the server device 100 may be a cloud device connected to a plurality of user devices 200.

The user equipment 200 of various embodiments can be a device that can be used by a personal user, such as a desktop computer, a tablet computer, a mobile terminal, etc. In addition, other electronic devices that perform similar functions can also be used as the user equipment 200.

The information provision system of various embodiments may include various modules for performing actions. The modules included in the information provision system may be computer code and one or more instructions implemented in such a manner that a physical device (e.g., server device 100 and user device 200) that implements the information provision system (or included in the physical device) can perform a specified action. In other words, the physical device that implements the information provision system may store multiple modules in the form of computer code in memory. When the multiple modules stored in the memory are executed, the multiple modules cause the physical device to perform the specified actions corresponding to the multiple modules.

FIG2 is a diagram showing the configuration of a server device 100 and a user device 200 according to various embodiments.

2 , the server device 100 and the user device 200 may include an input/output unit 210 , a communication unit 220 , a storage 230 , and a processor 240 .

The input/output unit 210 can be any interface or port for receiving user input or outputting information to the user. The input/output unit 210 can include an input module and an output module. The input module receives user input. User input can be implemented in various forms, including keystroke input, touch input, and voice input. Examples of input modules that can receive such user input include, in addition to traditional keypads or keyboards, and mice, touch sensors that sense user touch, microphones that receive voice signals, cameras that recognize gestures through image recognition, proximity sensors that include at least one of an illumination sensor or an infrared sensor that senses the user's approach, motion sensors that recognize user movements through acceleration sensors or gyroscope sensors, and various other input mechanisms that sense or receive various forms of user input. The input module of an embodiment of the present invention 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 senses touch via a touch panel or touch film attached to a display panel, or an optical touch sensor that senses touch optically. Furthermore, the input module can also be implemented as an input interface (USB (Universal Serial Bus) port, PS/2 (Personal System 2) port, etc.) that connects to an external input device that receives user input instead of a device that senses user input itself. Furthermore, the output module can output various types of information. The output module can include at least one of a display that outputs images, a speaker that outputs sound, a tactile device that generates vibrations, and various other types of output mechanisms. In addition, the output module can also be implemented as a port-type output interface connected to the above-mentioned individual output mechanisms.

For example, an output module in the form of a display can display text, still images, or video. Displays may 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 other devices capable of outputting images. Such a display may also be in the form of a touch display integrated with the touch sensor of the input module.

The communication unit 220 can communicate with other devices. Therefore, the server device 100 and the user device 200 can send and receive information with other devices via the communication unit. For example, the server device 100 and the user device 200 can use the communication unit to communicate with each other or with other devices.

Here, communication, i.e., the transmission and reception of data, can be achieved either wired or wirelessly. For this purpose, the communication unit may include: a wired communication module connected to the Internet via a LAN (Local Area Network), a mobile communication module connected to a mobile communication network via a mobile communication base station to transmit and receive data, a short-range communication module utilizing WLAN (Wireless Local Area Network) communication methods such as Wi-Fi or WPAN (Wireless Personal Area Network) communication methods such as Bluetooth and Zigbee, a satellite communication module utilizing GNSS (Global Navigation Satellite System) such as GPS (Global Positioning System), or a combination thereof.

The memory 230 can store various types of information. The memory 230 can store data temporarily or semi-permanently. For example, the memory 230 of the server device 100 can store the operating system (OS) used to drive the server device 100, data used to host a website, or data of a program or application used to generate Braille (e.g., a website application). Furthermore, the memory 230 can store modules in the form of computer code, as described above.

Examples of the memory 230 include a hard disk drive (HDD), a solid state drive (SSD), a flash memory, a read-only memory (ROM), a random access memory (RAM), etc. The memory 230 can be provided in a built-in or removable form.

The processor 240 can control the overall operation of the server device 100 and the user device 200. To this end, the processor 240 can perform various calculations and processing of information and control the operation of the components of the server device 100. For example, the processor 240 can execute a program or application for providing information. The processor 240 can be implemented by a computer or similar device based on hardware, software, or a combination thereof. In terms of hardware, the processor 240 can be implemented in the form of a circuit that uses electrical signals to perform processing and perform control functions. In terms of software, it can be implemented in the form of a program that drives the hardware processor 240. On the other hand, unless otherwise specified in the following description, the actions of the server device 100 and the user device 200 can be interpreted as being performed under the control of the processor 240. That is, when executing the modules implemented in the above-mentioned information provision system, the modules can be interpreted as the processor 240 controlling the server device 100 and the user device 200 by performing the following actions.

In short, various embodiments can be implemented by various mechanisms. For example, various embodiments can be implemented by hardware, firmware, software, or a combination thereof.

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

When implemented via firmware or software, the methods of various embodiments can be implemented in the form of modules, procedures, or functions that perform the functions or actions described below. For example, the software code can be stored in memory and driven by a processor. The memory can be located internally or externally to the processor and can transmit and receive data with the processor using various well-known mechanisms.

The following describes various embodiments in more detail based on the above-described technical concepts. The above-described contents can be applied to the various embodiments described below. For example, actions, functions, and terms not defined in the various embodiments described below can be implemented and described based on the above-described contents.

In the following description, various embodiments are described based on the premise that the server device 100 performs information providing operations.

FIG3 is a diagram showing an operation method of the server device 100 for providing information according to various embodiments.

3 , in order to provide log information corresponding to an API class and to implement the action of providing log information, the server device 100 may obtain API class analysis information (301) for analyzing an API field for providing log information in an API class of an API (Application Programming Interface) action used in a service. Based on the API class analysis information, the server device 100 may confirm the first log field indication information including one or more API fields indicating an API field for providing log information, wherein the one or more API fields correspond to the first API class of the first API action used in the service (303). When it is confirmed that the first API class is set as the API class for providing log information, the server device 100 may provide the first log information (305) corresponding to the first API class based on the first log field indication information.

As shown in FIG3 , the action of server device 100 providing log information may be performed for the service provided by server device 100 or for services related to server device 100. Such services may be equivalent to a service in which multiple users utilizing the service can order and purchase multiple items sold in the service. The multiple items sold in the service may include various types or categories of items registered by the seller for sale, and are not limited to the types or categories of items.

In Figure 3, an API action within a service can refer to software/application actions related to corresponding lower-level services or functions, processed through a series of programming interfaces (APIs), thereby serving specific lower-level services or functions within the service. The APIs used to process API actions can be implemented using API classes. To handle the various API actions generated by the service, corresponding API classes can be configured. Each API class can include one or more API fields, which are configured to implement the processing items of each API class. The API fields included in each API class can vary.

When providing log information generated by API actions, the log information is typically provided on an API class basis. However, this can lead to the following issues: depending on the number of API fields included in the API class, the processing load for providing the log information may increase, or log information generated by the remaining API fields included in the API class may be redundantly provided, in addition to the portion of API fields for which the administrator desires to receive log information. Referring to FIG. 3 , the action of server device 100 providing log information can be understood as: to resolve the above-mentioned issue, only log information for a portion of the API fields included in the API class, which is set according to a fixed standard, is provided, corresponding to the API class. In this way, only log information corresponding to the portion of API fields desired by the administrator can be selectively received within the API class.

According to various embodiments, in action 301, the server device 100 may obtain API class analysis information for analyzing an API field that will provide log information in an API class of an API action used in a service.

For example, according to action 301, the API class analysis information obtained by the server device 100 can be performed based on code scanning analysis of the API fields corresponding to the API class. The API class and the API fields included in the API class are configured using code. Therefore, by performing code unit scanning analysis, it is possible to determine which API field in the API class is designated as the object for providing log information.

For example, according to action 301, the API class analysis information obtained by the server device 100 may be a combination of information analyzed for each API class corresponding to each API action. Specifically, code scanning analysis is performed on the API fields included in each API class corresponding to each API action included in the various API actions generated in the service. For each API class, the server device 100 may determine which API field is designated as the target for providing log information and configure it to be included in the API class analysis information.

FIG. 4 is a diagram showing an example of API-type analysis information obtained by configuring the server device 100.

In FIG4 , with the API class as the object ( 401 ), a code scan ( 403 ) can be performed on the API fields included in the API class, and fixed filters ( 405 , 407 ) can be applied to the scanned code as the object. In this way, the API fields ( 409 ) that will become the objects providing log information in the API class can be determined.

As shown in Figure 4, various API classes in the service can be used as targets to determine the API fields within the API class that will provide log information. Based on this, the API fields determined to provide log information within each API class can be analyzed and compiled into comprehensive API class analysis information. The configured API class analysis information can be obtained from the server device 100 through administrator input, etc. The example in Figure 4 can also be implemented using the process in Figure 5.

FIG. 5 is a diagram showing an example of a process for configuring the API-type analysis information obtained by the server device 100.

In Figure 5, the code corresponding to the API class can be read according to a fixed standard (501). The API class can be analyzed by a series of filter processing and method processing (503). The results of the procedures 501 and 503 are combined to confirm the API fields that become the objects of log information provision in the API class (505). When the information of the API fields confirmed as described above is sorted and integrated for each API class, the API class analysis information can be set.

According to various embodiments, in action 303, the server device 100 may confirm, based on the API class analysis information, first log field indication information including an indication that one or more API fields corresponding to the first API class used in the first API action in the service are API fields providing log information.

For example, the first log field indication information confirmed by server device 100 in action 303 may be information indicating the API fields determined to be the subject of log information provision in the first API class based on the results of code scanning and analysis of one or more API fields included in the first API class used in the first API action in the service. In other words, the first log field indication information may be information indicating the API fields determined to be the subject of log information provision in the first API class based on the API class analysis information. An example of a code indicating an API field using the first log field indication information is shown in Table 1.

[Table 1] com.apigateway.services.search_api.model.Agreement =agreementTime,agreementType,agreementVersion,deadtineDate,effectiveDate,status com.apigateway.services.checkout_front_api.model.LandingRequest =

In the code shown in Table 1, the code corresponding to the first part is in the API class related to Agreement in the search_api, indicating multiple API fields (agreementTime, agreementType, agreementVersion, deadlineDate, effectiveDate, status) that are the targets of log information. On the other hand, in the code shown in Table 1, the code corresponding to the second part is in the API class related to LandingRequest in the checkout_front_api, indicating API fields that are the targets of log information. In this case, all API fields included in the corresponding API class can be designated as the targets of log information as described below.

For example, according to action 303, the API field in the first API class indicated by the first log field indication information confirmed by the server device 100 may be: according to action 305 described below, the API field becomes the object of log information provision corresponding to the first API class.

For example, according to action 301, in the API class analysis information obtained by the server device 100, when the API field for which log information will be provided is not separately specified in the first API class, that is, when matters related to the API field identified as the object of log information in the first API class are not confirmed in the API class analysis information, according to action 303, in the first log field indication information confirmed by the server device 100, it can be indicated that one or more API fields in the first API class are all objects for providing log information. If the API field for which log information is to be provided is not confirmed in the first API class by analyzing the information through the API class, the server device 100 determines to provide log information for all API fields included in the first API class. In this case, the action 305 of the server device 100 that provides the first log information corresponding to the first API class can provide log information for all API fields included in the first API class.

For example, in addition to the first log field indication information set based on the API class analysis information, the server device 100 can also determine the API field in the first API class that is the target of log information provision based on different log field indication information set based on other criteria.

For example, if the log information generated by one or more API fields included in the first API category contains redundant information, server device 100 may identify the second log field indication information, including an indication that the API field does not provide log information, and may reflect the second log field indication information to determine the API fields in the first API category that are subject to log information provision. Log information generated by API fields may not only record information related to API actions, but also include personal information such as the name, address, and age of service users that is unrelated to the API actions themselves. Therefore, for the sake of personal information protection, API fields that record such personal information may be determined to be excluded from log information provision in the first API category. That is, the API field in the first API class indicated in the second log field indication information can be set in such a way that it does not become an object of log information provision.

As another example, the server device 100 can confirm the third log field indication information of the following API fields among one or more API fields included in the first API class, that is, the API field that is indicated as providing log information or not providing log information based on the administrator's API field selection input information can reflect the third log field indication information and determine the API field in the first API class to be the object of log information provision.

For API classes, regardless of the first and second log field indication information, if there is a separate API field for the administrator to receive log information, or if there is a separate API field that the administrator wishes to omit from the recipients of log information, it is necessary to reflect the administrator's intention as described above. Therefore, the server device 100 manages by adding a specific API field as an object of log information provision in the API class, or by obtaining API field selection input information from an administrator who excludes a specific API field from the object of log information provision. If an API field indicating provision of log information or indication of non-provision of log information is confirmed based on the obtained API field selection input information, it can be reflected in the process of finally determining the API field as an object of log information provision in the API class.

When using the third log field indicator information when determining the API fields within an API class that are the subject of log information provision, the third log field indicator information can be configured for each API class not only by allowing the administrator to select specific API fields and include or exclude those specific API fields from the subject of log information provision, but also by obtaining API field selection input from the administrator and selecting specific API fields based on the characteristics of the API class, and then including or excluding those selected specific API fields from the subject of log information provision.

Administrators can select specific API fields for each API class and add or exclude them from log information provision. This is because the characteristic information including the characteristics of each API class may lead to different judgments about the API fields required for log information. Administrators can conveniently add or exclude API fields. If API classes with the same characteristic information exist, the administrator's method for selecting and inputting API fields can be applied to the corresponding API classes in the same manner. That is, if there are a first API class and a second API class with the same characteristic information, if the administrator has applied API field selection and input information to the first API class, the server device 100 can also apply the same method for selecting and inputting API fields to the second API class.

For example, the API class used to process credit card settlement actions within a service and the API class used to process transfer settlement actions within a service are both APIs used for settlement processing actions. They may include some common settlement characteristic information of the settlement processing actions and some common API fields. Therefore, if the administrator's API field selection input information confirmed for a certain API class is related to the common API fields based on the same settlement characteristic information, the administrator's API field selection input information can also be configured for the remaining API class in the same manner.

An example of a code indicating an API field by using the second log field indication information and the third log field indication information is shown in Table 2.

[Table 2] common.excludes =registration,passport # includes demo com.apigateway.services.search_api.model.MemberV3.includes =shippingPolicies,serviceTypesByMemberStatus

In the codes shown in Table 2, the codes corresponding to the first section include the second log field indication information, indicating that the API field does not provide log information due to the inclusion of redundant log information. This indicates that API fields containing registration- and passport-related information are generally excluded from log information provision within the API class. In the codes shown in Table 2, the codes corresponding to the second section include the third log field indication information, indicating that the API field provides log information or does not provide log information, based on the administrator's API field selection input. This indicates that in the MemberV3 API class related to the search_api, fixed API fields (shippingPolicies and serviceTypesByMemberStatus) are designated as targets for log information provision.

If the server device 100 confirms the above-mentioned second log field indication information and/or third log field indication information, the server device 100 is confirmed as the API field of the object of log information provision in the first API class based on the first log field indication information. Then, in order to apply all of the above-mentioned first to third log field indication information, the server device 100 can set the priority of each log field indication information, and apply each log field indication information in sequence according to the set priority, and finally determine the API field of the object of log information provision in the first API class.

For example, the server device 100 1) focuses on the personal information of users who omit the service, and can give the highest priority to the second log field indication information that is determined not to be the object of log information provision. 2) In order to reflect the log information of the API field selected based on the administrator's API field selection input as the next priority, the third log field indication information that is determined to be the object of log information provision can be given an intermediate priority. This API field corresponds to the API field selection input information. Furthermore, 3) the first log field indication information may be determined to be information preset for each API class. This first log field indication information specifies the API field preset for each API class as the target for log information provision. Therefore, the first log field indication information may be assigned the lowest priority. In this case, the second log field indication information may be given a higher priority than the third log field indication information, and the third log field indication information may be given a higher priority than the first log field indication information.

By setting a priority for each log field indication information and applying each log field indication information in order according to the set priority, the priority of each API field included in the API class can also be determined. If the server device 100 is configured to provide log information for only a portion of the API fields included in the API class, if the number of API fields for which log information is provided is to be limited, the server device 100 can also manage the API fields for which log information is to be provided in the order of the highest priority set for each API field as described above.

According to various embodiments, in action 305, when the server device 100 confirms that the first API class is set as the API class for providing log information, the server device 100 may provide first log information corresponding to the first API class based on the first log field indication information.

For example, according to action 305, based on the first log field indication information in one or more API fields included in the first API class, the first log information provided by the server device 100 may include the following information: including each log information generated by each API field in the first API class that is confirmed to provide log information.

If the server device 100 confirms not only the first log field indication information but also the second log field indication information and the third log field indication information, then according to action 305, based on the first to third log field indication information in one or more API fields included in the first API class, the first log information provided by the server device 100 may include the following information: each log information generated by finally confirming that each API field provides log information in the first API class.

For example, in action 305, server device 100 confirms that the first API class is set as the API class for which log information will be provided by confirming whether the first API class associated with the service has been previously registered as the API class for which log information will be provided. Specifically, server device 100 may configure registration information for the aforementioned multiple API classes to separately categorize the multiple API classes for which log information will be provided among the various API classes associated with the service. If, based on the aforementioned registration information, the first API class is confirmed as the API class for which log information will be provided, first log information corresponding to the first API class may be provided according to action 305.

For example, the server device 100's action 305 of providing the first log information corresponding to the first API class may be performed by configuring an adapter for providing the log information. The server device 100 may configure the adapter for providing the log information corresponding to the API class based on the log field indication information for the API class, and may provide the first log information corresponding to the first API class based on the configured adapter. At this time, the adapter described above can be equivalent to an adapter set up in the following manner: it is connected to the registration information and log field indication information of multiple API classes that will be the objects of log information provision, and outputs the log information of the API class and API field determined to provide log information based on the above registration information and the above log field indication information.

FIG. 6 is a diagram showing an example of a flow chart for providing log information corresponding to an API class based on log field indication information.

In FIG. 6 , the first log field indication information (Domain dependency Model fields, 601), the second log field indication information (PII Classification Table, 603), and the third log field indication information (Model Custom includes/excludes fields, 605) can be confirmed by the server device 100. At this time, the first log field indication information 601 can be set as in one of the examples in FIG. 4 to FIG. 5 above.

The 1st to 3rd log field indication information can be applied to determine the API field that has been selected as the object of log information provision for the API class. At this time, if it is confirmed through registration information 607 that the corresponding API class is set as the API class that will provide log information, then based on the adapter 609, log information including various log information generated by the API field can be provided to the administrator, and the API field is selected for the corresponding API class.

FIG. 7 is a diagram showing an example of an API class being determined as one of the objects to which log information is provided.

In Figure 7, for each of the seven API classes, you can see that the API fields that are identified as providing log information have been organized. You can use the format "API class" = "API field identified as providing log information" to confirm that each piece of information is displayed.

For example, in Figure 7, the API class "com.Apigateway.services.search_api.model.BalanceAccount," shown in item 7, is related to the API action for handling balance amounts. Within this API class, you can confirm that the API fields "balanceAmountEx" and "depositAmountEx" are selected as the targets for log information provision. If an administrator wishes to receive log information for the API class shown in item 7, the provided log information will include logs generated by both the API fields "balanceAmountEx" and "depositAmountEx."

On the other hand, in FIG7 , for each API class displayed as items 3, 4, 6, and 9 without displaying a specific API field, all API fields included in the corresponding API class can be the objects of log information provision. When the administrator wishes to receive log information of the corresponding API class, the log information provided can include logs generated by all API fields included in the corresponding API class.

3 to 7 , it is apparent that when the server device 100 implements the method for providing information, the information used can be combined into various forms.

The embodiments of the present invention disclosed in this specification and drawings are provided merely as specific examples to facilitate explanation of the technical content of the present invention and aid understanding of the present invention. They are not intended to limit the scope of the present invention. In other words, it is apparent that those skilled in the art will be able to implement other variations based on the technical principles of the present invention. Furthermore, the above-mentioned embodiments may be combined as needed. For example, some embodiments may be combined to implement all embodiments of the present invention as a system.

Furthermore, the system and methods of the present invention can be implemented in the form of program commands that can be executed by various computer mechanisms and recorded in a computer-readable medium.

As described above, in certain aspects, various embodiments of the present invention may be implemented as computer-readable code in a computer-readable recording medium. A computer-readable recording medium is any data storage device capable of storing data that can be accessed by a computer system. Examples of computer-readable recording media include read-only memory (ROM), random access memory (RAM), compact disk-read-only memory (CD-ROM), magnetic tape, floppy disk, optical data storage devices, and carrier waves (for transmitting data over the Internet, etc.). The computer-readable recording medium can also be distributed through network-connected computer systems, so that the computer-readable code can be stored and executed in a distributed manner. In addition, programmers skilled in the application field of the present invention can easily interpret the functional programs, codes, and code segments used to implement various embodiments of the present invention.

Furthermore, it is understood that the devices and methods of various embodiments of the present invention can be implemented in the form of hardware, software, or a combination of hardware and software. Such software can be stored, for example, regardless of whether it is rewritable or not, in a volatile or non-volatile storage device such as a ROM, or a RAM, memory chip, device, or integrated circuit memory, or an optically or magnetically recordable storage medium such as a compact disk (CD), DVD (Digital Versatile Disc), magnetic disk, or magnetic tape that can be read by a machine (e.g., a computer). It is understood that the methods of various embodiments of the present invention can be implemented by a computer including a control unit and a memory, or a vehicle including the memory or computer as described above. Such a memory is an example of a program including commands for implementing the embodiments of the present invention or a storage medium suitable for storing the program and readable by a machine.

Therefore, the present invention includes: a program as code for implementing the apparatus or method described in the scope of the invention application of this specification, and a storage medium storing such a program and readable by a machine (such as a computer). Furthermore, such a program can be electronically transferred via any medium that transmits communication signals, such as via a wired or wireless connection, and the present invention appropriately includes their equivalents.

The above description has been made with reference to the embodiments of the present invention. However, the embodiments of the present invention disclosed in this specification and drawings are merely specific examples provided to facilitate explanation of the technical content of the present invention and to aid understanding of the present invention, and are not intended to limit the scope of the present invention. Furthermore, it should be understood that the embodiments of the present invention described above are merely illustrative, and that persons skilled in the art will be able to implement various modifications and equivalent embodiments based thereon. Therefore, the true scope of technical protection for the present invention should be defined in accordance with the scope of the invention application set forth below.

100: Server Device 200: User Device 210: Input/Output Unit 220: Communication Unit 230: Storage 240: Processor 301: Action 303: Action 305: Action 401: Action 403: Action 405: Action 407: Action 409: Action 501: Program 503: Program 505: Program 601: Log Field Indication Information 603: Log Field Indication Information 605: Log Field Indication Information 607: Registration Information 609: Adapter

Figure 1 illustrates an information provision system that can implement an operating method of an electronic device for providing information, according to various embodiments. Figure 2 illustrates the configuration of a server device 100 and a user device 200, according to various embodiments. Figure 3 illustrates the operating method of the server device 100 for providing information, according to various embodiments. Figure 4 illustrates an example of configuring API class analysis information obtained by the server device 100. Figure 5 illustrates an example of a procedure for configuring API class analysis information obtained by the server device 100. Figure 6 illustrates an example of a flowchart for providing log information corresponding to an API class based on log field indication information. Figure 7 illustrates an example of organizing API fields that identify an API class as the target of log information provision.

301: Action 303: Action 305: Action

Claims (16)

An information provision method, performed by an electronic device, comprises the following steps: Acquiring API class analysis information analyzing an API field for providing log information in an API class used in an API action in a service provided by the electronic device; Based on the API class analysis information, confirming first log field indication information including one or more API fields indicating an API field for providing log information, wherein the one or more API fields correspond to a first API class for a first API action in the service; and If it is confirmed that the first API class is set as the API class for providing log information, providing first log information corresponding to the first API class based on the first log field indication information. The information providing method of claim 1, wherein the API class analysis information is set based on a code scan analysis of an API field corresponding to the API class. The information providing method of claim 1 further includes the following step: Confirming the second log field indication information of the one or more API fields, including the following API fields, i.e., an API field indicating that log information is not provided because the log information generated by the API field includes redundant information. The information provision method of claim 3, wherein the redundant information includes personal information of users of the service. The information provision method of claim 1 further includes the following step: Confirming the third log field indication information of the one or more API fields, including the following API fields, i.e., the API fields indicating whether to provide log information or not to provide log information based on the administrator's API field selection input information. The information providing method of claim 5, wherein the API field selection input information is set in the following manner: selecting or excluding API fields based on characteristic information of the API class. The information providing method of claim 6, wherein for a second API class having the same characteristic information as the first API class, the API field selection input information applies identically to the second API class. In the information providing method of claim 1, when no API field for which log information will be provided is confirmed in the first API class based on the API class analysis information, the first log field indication information indicates that all of the one or more API fields provide log information. The information providing method of claim 1, wherein the step of providing the first log information comprises the following steps: Providing the first log information based on the first log field indication information, the second log field indication information, and the third log field indication information, wherein the second log field indication information includes the following API field among the one or more API fields: an API field indicating that log information is not provided because log information generated by the API field includes redundant information; and the third log field indication information includes the following API field indicating that log information is provided or not provided based on information input by an administrator through the API field selection. The information providing method of claim 9, wherein the first log field indication information, the second log field indication information, and the third log field indication information are applied in sequence according to their priorities. The information providing method of claim 10, wherein the priority of the information indicated in the second log field is set higher than the priority of the information indicated in the third log field, and the priority of the information indicated in the third log field is set higher than the priority of the information indicated in the first log field. An information providing method as claimed in claim 9, wherein the first log information includes log information generated by each API field, and the API field is confirmed as providing log information in the first API category based on the first log field indication information, the second log field indication information and the third log field indication information. The information provision method of claim 1 further comprises the following steps: Setting registration information, wherein the registration information registers multiple API classes including the first API class as API classes that will provide log information; and Based on the registration information, confirming that the first API class is set as the API class that will provide log information. The information providing method of claim 1 further comprises the following steps: Based on the log field indication information for the API class, setting an adapter for providing log information corresponding to the API class. The information providing method of claim 14, wherein the step of providing the first log information comprises the following steps: Providing the first log information based on the adapter. An electronic device that provides information, comprising: a processor; and one or more memories storing one or more instructions; when executing the one or more instructions, controlling the processor so that the processor performs the following steps: obtaining API class analysis information for analyzing an API field that will provide log information in an API class used for an API action in a service provided by the electronic device; based on the API class analysis information, confirming that first log field indication information including one or more API fields indicating an API field that provides log information corresponds to a first API class for the first API action used in the service; and When it is confirmed that the first API class is set as the API class for which log information will be provided, the first log information corresponding to the first API class will be provided based on the first log field indication information.