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

Abstract

According to the present disclosure, a method for providing information by an electronic device includes the steps of checking error type information including a plurality of error types corresponding to a backend service of a service provided by the electronic device; Setting error occurrence information to implement an error situation corresponding to a specific error type among the plurality of error types on a first backend server included in one or more backend servers corresponding to the backend service; and providing error implementation result information for the error situation implemented based on the error occurrence information.

Description

Method of operating an electronic device that provides information and an electronic device supporting the same {OPERATING METHOD FOR ELECTRONIC APPARATUS FOR PROVIDING INFORMATION AND ELECTRONIC APPARATUS SUPPORTING THEREOF}

The present invention relates to a method and device for providing information, and more specifically, to a method and electronic device for enabling an electronic device to implement an error situation and provide result information corresponding to the error situation.

With the development of electronic technology, e-commerce has become a field of shopping. Customers can purchase items online without having to go to a shopping mall or market in person, and items purchased online are delivered to the delivery address requested by the customer.

In the case of e-commerce, the processing of detailed and accurate information about products has a significant impact on service satisfaction, so discussions are taking place on various methods to process information in more detail and accurately.

In relation to this, prior literature such as KR101756594B1 or KR101500849B1 may be referred to.

According to the method of the present invention, an electronic device can implement an error situation and provide result information corresponding to the error situation.

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 will be clearly understood by those skilled in the art from the description below. You will be able to.

Various embodiments may provide a method of operating an electronic device to provide information and an electronic device that supports the same.

A method of providing information by an electronic device according to various embodiments, comprising: checking error type information including a plurality of error types corresponding to a backend service of a service provided by the electronic device; Setting error occurrence information to implement an error situation corresponding to a specific error type among the plurality of error types on a first backend server included in one or more backend servers corresponding to the backend service; And it may include providing error implementation result information for the error situation implemented based on the error occurrence information.

In an exemplary embodiment, the checking the error type information includes collecting information about a plurality of error situations that occur in relation to the backend service on the service; and classifying the plurality of error situations into the plurality of error types.

In an exemplary embodiment, the plurality of error types include: a first error type in which a data call of the backend server to a counterpart backend server is missed, and a time required for a data call to the counterpart backend server of the backend server exceeds a threshold time. A second error type may include a second error type, and a third error type in which incorrect response data is called in response to a data call from a backend server to a counterpart backend server.

In an exemplary embodiment, setting the error occurrence information may include setting a message notifying missing data call when the specific error type corresponds to the first error type.

In an exemplary embodiment, setting the error occurrence information may include setting the threshold time when the specific error type corresponds to the second error type.

In an exemplary embodiment, setting the error occurrence information may include setting information to be included as the incorrect response data when the specific error type corresponds to the third error type.

In an exemplary embodiment, the error occurrence information includes information about the first backend server, the first backend to implement the error situation among one or more frontend servers corresponding to the frontend service of the service. Information about a first front-end server set as a counterpart front-end server of the server, and information about a second back-end server set as a counterpart back-end server of the first back-end server to implement the error situation among the one or more back-end servers. May contain information.

In an exemplary embodiment, the error occurrence information may include information about a period managed to implement the error situation.

In an exemplary embodiment, the error occurrence information may include information about a manager who manages implementation of the error situation.

In an exemplary embodiment, the error occurrence information includes condition information for limiting user terminals that are set to enable implementation of the error situation, and implementation of the error situation is limited to user terminals that meet the condition information. It can be set to enable.

In an exemplary embodiment, the information providing method further includes setting a message to be displayed through the error implementation result information, and when the message is displayed as a result of the implementation of the error situation, the error situation The implementation can be managed as having been performed successfully.

In an exemplary embodiment, the information provision method further includes the step of building a test server corresponding to the service, and the implementation of the error situation and provision of the error implementation result information are performed by using the error occurrence information in the test server. It can be performed by applying .

In an exemplary embodiment, the information providing method includes setting an adapter to be used to apply the error occurrence information to the test server; and registering the adapter with the test server.

In an exemplary embodiment, the test server may be configured to enable implementation of the error situation based on the fact that the registered adapter is activated.

In an exemplary embodiment, if attempts to activate the adapter fail a certain number of times, the adapter may be deactivated.

In an exemplary embodiment, the information providing method includes: a first front-end configured as a counterpart front-end server of the first back-end server to implement the error situation among one or more front-end servers corresponding to the front-end service of the service; Checking information about the server; And based on the error implementation result information, it may further include setting an error information message to be provided in relation to the error situation to the user of the service through the first front-end server.

An electronic device that provides information according to various embodiments includes: a processor; and one or more memories storing one or more instructions, wherein the one or more instructions, when executed, cause the processor to: correspond to a backend service of a service provided by the electronic device. Checking error type information including a plurality of error types; Setting error occurrence information to implement an error situation corresponding to a specific error type among the plurality of error types on a first backend server included in one or more backend servers corresponding to the backend service; And the processor may be controlled to perform a step of providing error implementation result information for the error situation implemented based on the error occurrence information.

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 understood by those skilled in the art. It can be derived and understood based on the detailed description described below.

The present invention has a technical effect in that it provides a method for an electronic device to implement an error situation and provide result information in response to the error situation, allowing an effective way to respond to the error situation.

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 those skilled in the art from the description below. will be.

FIG. 1 is a diagram illustrating an information provision system in which a method of operating an electronic device for providing information according to various embodiments can be implemented.
FIG. 2 is a diagram illustrating the configuration of a server device 100 and a user device 200 according to various embodiments.
FIG. 3 is a diagram illustrating a method of operating the server device 100 for providing information according to various embodiments.
Figure 4 is a diagram showing an outline of front-end services and back-end services.
FIG. 5 is a diagram illustrating an example of error occurrence information for implementing an error situation corresponding to the first error type.
FIG. 6 is a diagram illustrating an example of error occurrence information for implementing an error situation corresponding to the second error type.
FIG. 7 is a diagram illustrating an example of error occurrence information for implementing an error situation corresponding to a third error type.
FIG. 8 is a diagram illustrating a method by which the server device 100 executes an adapter for applying error occurrence information according to various embodiments.
Figure 9 is a diagram illustrating a flow chart in which an adapter for applying error occurrence information is registered and activated.
FIG. 10 is a flowchart showing how an error situation is implemented by applying error occurrence information based on an adapter.
Figure 11 is a diagram showing how various error occurrence information is applied to the test server.

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 in a form that is not combined with other components or features. Additionally, various embodiments may be configured by combining some components and features. The order of operations described in various embodiments may change. Some features or features of one embodiment may be included in other embodiments or may be replaced with corresponding features or features of other embodiments.

In the description of the drawings, procedures or steps that may obscure the gist of the various embodiments are not described, and procedures or steps that can be understood at the level of a person with ordinary knowledge in the relevant technical field are not described. did.

Throughout the specification, when a part is said to “comprise or include” a certain element, this means that it does not exclude other elements but may further include other elements, unless specifically stated to the contrary. do. In addition, terms such as "... unit", "... unit", and "module" used in the specification refer to a unit that processes at least one function or operation, which refers to hardware, software, or a combination of hardware and software. It can be implemented as: Additionally, the terms “a or an,” “one,” “the,” and similar related terms are used herein in the context of describing various embodiments (particularly in the context of the claims below). Unless otherwise indicated or clearly contradicted by context, it may be used in both singular and plural terms.

Hereinafter, preferred embodiments according to various embodiments will be described in detail with reference to the attached drawings. The detailed description set forth below in conjunction with the accompanying drawings is intended to illustrate exemplary embodiments of various embodiments and is not intended to represent the only embodiment.

In addition, 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 to other forms without departing from the technical spirit of the various embodiments. .

FIG. 1 is a diagram illustrating an information provision system in which a method of operating an electronic device for providing information according to various embodiments can be implemented.

Referring to FIG. 1, information providing systems according to various embodiments may be implemented in various types of electronic devices. For example, the information provision system may be implemented in the server device 100 and the 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 provision system implemented in each device. Meanwhile, the information provision system according to various embodiments is not limited to what is shown in FIG. 1, and may be implemented in a wider variety of electronic devices and servers.

The server device 100 according to various embodiments 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 works with a plurality of user devices 200. In addition to functioning as a server, the server device 100, which will be described later in this disclosure, may function to manage and control various front-end servers on the front-end service for the service and various back-end servers on the back-end service for the service.

The user device 200 according to various embodiments may be a device that can be used by an individual user, 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.

An information provision system according to various embodiments may include various modules for operation. Modules included in the information provision system are implemented so that the physical device (e.g., server device 100 and user device 200) on which the information provision system is implemented (or included in the physical device) can perform specified operations. It may be computer code or one or more instructions. In other words, the physical device in which the information provision system is implemented stores a plurality of modules in the memory in the form of computer code, and when the plurality of modules stored in the memory are executed, the plurality of modules are designated by the physical device corresponding to the plurality of modules. Actions can be performed.

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

Referring to FIG. 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 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. User input can take various forms, including key input, touch input, and voice input. Examples of input modules that can receive such user input include traditional keypads, keyboards, and mice, as well as touch sensors that detect the user's touch, microphones that receive voice signals, cameras that recognize gestures through image recognition, etc. A proximity sensor including at least one of an illumination sensor or an infrared sensor that detects user approach, a motion sensor that recognizes user movement through an acceleration sensor or gyro sensor, and various other types of sensors that detect or receive user input. There is an input means, 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 may be implemented as a piezoelectric or capacitive touch sensor that detects touch through a touch panel or touch film attached to the display panel, or an optical touch sensor that detects touch by an optical method. In addition, the input module may 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 itself. Additionally, the output module can output various information. The output module may include at least one of a display that outputs an image, a speaker that outputs sound, a haptic device that generates vibration, and various other types of output means. In addition, the output module may be implemented in the form of a port-type output interface that connects the individual output means described above.

As an example, a display-type output module can display text, still images, and moving images. Displays include liquid crystal display (LCD), light emitting diode (LED) display, organic light emitting diode (OLED) display, flat panel display (FPD), and transparent display. Among various types of devices that can perform image output functions such as display, curved display, flexible display, 3D display, holographic display, projector, and other It can contain at least one. This display may 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. Accordingly, the server device 100 and the user device 200 can transmit and receive information with other devices through the communication unit. For example, the server device 100 and the user device 200 may communicate with each other or with other devices using a communication unit.

Here, communication, that is, transmission and reception of data, can be accomplished wired or wirelessly. To this end, the communication department includes a wired communication module that connects to the Internet, etc. through a LAN (Local Area Network), a mobile communication module that transmits and receives data by connecting to a mobile communication network through a mobile communication base station, and a WLAN (Wireless Local Area Network) such as Wi-Fi. A short-distance communication module using an Area Network-type communication method or a WPAN (Wireless Personal Area Network)-type communication method such as Bluetooth or Zigbee, and a GNSS (Global Navigation Satellite System) such as a GPS (Global Positioning System) ) may include a satellite communication module using a satellite communication module or a combination thereof.

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

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

The processor 240 controls the overall operation of the server device 100 and the user device 200. To this end, the processor 240 can perform calculations and processing of various information and control the operation of components of the server device 100. For example, the processor 240 may execute a program or application to provide information. The processor 240 may be implemented as a computer or similar device using hardware, software, or a combination thereof. In hardware, the processor 240 may be implemented in the form of an electronic circuit that processes electrical signals to perform a control function, and in 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 modules implemented in the above-described information provision system are executed, the modules may be interpreted as the processor 240 controlling the server device 100 and the user device 200 to perform the following operations.

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

In the case of hardware implementation, methods according to various embodiments include one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), and FPGAs. It can be implemented by (field programmable gate arrays), processor, controller, microcontroller, microprocessor, etc.

In the case of implementation by firmware or software, 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 can be stored in memory and run by a processor. The memory may be located inside or outside the processor, and may exchange data with the processor through various known means.

Below, various embodiments will be described in more detail based on the above technical idea. The contents described above may be applied to various embodiments described below. For example, operations, functions, terms, etc. that are not defined in various embodiments described below may be performed and explained based on the contents described above.

In the following description, various embodiments will be described on the premise that the electronic device performs an information provision operation.

FIG. 3 is a diagram illustrating a method of operating the server device 100 for providing information according to various embodiments.

According to FIG. 3, the server device 100 provides error implementation result information for an error situation, and in order to perform an operation of providing error implementation result information, a plurality of error types corresponding to the backend service of the service Confirm error type information including (301), and implement an error situation corresponding to a specific error type among a plurality of error types for the first backend server included in one or more backend servers corresponding to the backend service. Error occurrence information can be set (303), and error implementation result information for the error situation implemented based on the error occurrence information can be provided (305).

According to FIG. 3, the operation of the server device 100 providing error implementation result information may be performed for a service provided by the server device 100 or a service related to the server device 100, and the service is sold in the service. It may correspond to a service that allows multiple users using the service to order and purchase multiple items. The plurality of items sold in the service are not limited to the type or type of the item and may include various types or types of items registered by the seller to sell the item. At this time, services provided by the server device 100 or services related to the server device 100 may be divided into frontend services and backend services, as shown in FIG. 4.

Figure 4 is a diagram showing an outline of front-end services and back-end services.

Referring to identification number 401, the front-end service may include various customer domains for services provided by the server device 100, and various front-end servers corresponding to the various customer domains provide the front-end service. can respond. Here, the customer domain may refer to a domain corresponding to various service pages that users can access on the UI/UX (user interface/user experience) of the service provided by the server device 100. The front-end service can be understood as a user-side management unit that is set up to manage data requested from each customer domain according to the user's UI/UX access and use.

Referring to identification number 403, the back-end service may include various database domains related to databases for services provided by the server device 100, and various back-end servers corresponding to the various database domains may provide the back-end service. can respond. Here, the database domain may refer to a domain corresponding to a database set to store and manage each data stored and managed by the server device 100 based on the type or type of the data. The backend service can be understood as a database-side management stage that is set up to store, check, and/or call data obtained in relation to the service provided by the server device 100.

In response to a user's data request through UI/UX, data that the server device 100 wants to call may be served from a back-end service to a front-end service. For example, a first customer domain corresponding to a specific customer domain used by the user may be provided. The front-end server may serve data that the server device 100 wants to call from a first back-end server corresponding to a specific database related to the specific customer domain. Additionally, if necessary, the first back-end server may call data from another second back-end server and operate to serve the called data to the first front-end server.

According to various embodiments, in operation 301, the server device 100 may check error type information including a plurality of error types corresponding to the backend service of the service.

For example, operation 301 in which the server device 100 checks error type information is based on collecting various error situations that occur or are recognized in relation to the backend service and classifying the collected error situations according to certain standards. This may be carried out. That is, on the service provided by the server device 100, the server device 100 collects information about a plurality of error situations that occur in relation to the backend service and classifies the collected error situations into a plurality of error types. Operation 301 may correspond to an operation of checking information about a plurality of error types classified as such.

For example, the plurality of error types included in the error type information that the server device 100 checks in accordance with operation 301 are error types corresponding to various error situations that occur when the backend server attempts to call data from the other backend server. may include. Specifically, the plurality of error types include: 1) a first error type in which a data call from a backend server to a counterpart backend server is missed; 2) the time required for a data call to a counterpart backend server from a backend server exceeds a threshold time; a second error type, and 3) a third error type in which incorrect response data is called in response to a data call from the backend server to a counterpart backend server.

According to various embodiments, in operation 303, the server device 100 generates an error situation corresponding to a specific error type among a plurality of error types to the first backend server included in one or more backend servers corresponding to the backend service. You can set error occurrence information for implementation.

For example, the error occurrence information that the server device 100 sets according to operation 303 includes information for implementing and simulating an error situation corresponding to a specific error type among the various error types described above in operation 301 in the test server. can do.

Specifically, if the specific error type corresponding to the error situation that the server device 100 wants to implement corresponds to the first error type in which a data call to the counterpart backend server of the backend server is missed, the server device 100 You can simulate the error by implementing an error situation where a data call is missed and setting a message to display that a data call is missed. In this case, the server device 100 may separately set a message notifying the omission of a data call when setting the error occurrence information in operation 303 in order to implement the error situation and simulate the error as desired.

If the specific error type corresponding to the error situation that the server device 100 wants to implement corresponds to a second error type in which the time required for the backend server to call data to the counterpart backend server exceeds the threshold time, the server device 100 100 may simulate an error by implementing an error situation in which a data call is delayed by exceeding a threshold time or response data corresponding to a data call is not received within the threshold time. In this case, in order to implement the error situation and simulate the error as desired, the server device 100 may separately set a threshold time that will be the standard for the data call delay when setting the error occurrence information according to operation 303.

In addition, if the specific error type corresponding to the error situation that the server device 100 wants to implement corresponds to a third error type in which incorrect response data is called in response to a data call from the backend server to the counterpart backend server, the server The device 100 may simulate an error by implementing an error situation in which incorrect data unrelated to the data call is called, rather than appropriate data corresponding to the data call. In this case, the server device 100 may separately set information to be included as incorrect response data when setting error occurrence information according to operation 303 in order to implement the error situation and simulate the error as desired.

For example, the error occurrence information that the server device 100 sets according to operation 303 includes information about the first back-end server designated to implement the error situation and one or more front-end servers corresponding to the front-end service. Information about the first front-end server that is set as a counterpart front-end server of the first back-end server to implement the error situation, and the first back-end among one or more back-end servers corresponding to the back-end service to implement the error situation It may include information about a second back-end server that is set as the server's counterpart back-end server. That is, information about the front-end server and/or back-end server corresponding to the data calling path or data serving path where the error situation is to be implemented may be included in the error occurrence information.

For example, error occurrence information that the server device 100 sets according to operation 303 may include information about a period managed to implement an error situation. In other words, in order to manage and supervise the error situation that the server device 100 wants to implement in the test server and prevent the problem of such error situation continuing regardless of the error simulation intention, the period during which the error situation is managed to be implemented is determined. The information may be included in error occurrence information.

For example, the error occurrence information that the server device 100 sets according to operation 303 may include information about the manager who manages the implementation of the error situation. In other words, information about the manager who manages the implementation of the error situation is provided so that the test server can manage and supervise the error situation by indicating which manager wants to simulate the error situation that the server device 100 wants to implement. It may be included in error occurrence information.

For example, the error occurrence information that the server device 100 sets according to operation 303 may include condition information for limiting user terminals that are set to enable implementation of an error situation. If it is set to enable the implementation of error situations without any restrictions for all user terminals connecting to the test server, users who are unrelated to the implementation of error situations in the test server or who do not know that a certain error situation is being simulated to be implemented on the test server Problems may occur when users connect to the test server and perform other tasks. Accordingly, the error occurrence information that the server device 100 sets according to operation 303 may include condition information that limits the implementation of the error situation to only be possible in certain user terminals, and only user terminals that meet the condition information may be used in the test server. It can be set to enable implementation of an error situation. Such condition information may include conditions determined according to the administrator's input. For example, the administrator may input a condition that restricts the implementation of the error situation to only user terminals with certain identification information.

FIG. 5 is a diagram illustrating an example of error occurrence information for implementing an error situation corresponding to the first error type.

The error occurrence information shown in FIG. 5 includes 1) information about the first backend server to implement an error situation corresponding to the first error type on the backend service (501), 2) the first backend server to implement the error situation. Information about the first front-end server that is set as the counterpart front-end server of the server (503), and 3) information about the period managed to implement the error situation and information about the manager who manages the implementation of the error situation (505) may include.

In addition, the error occurrence information is 4) first error type information 507, 5) to a second backend server that is set as a counterpart backend server of the first backend server to implement an error situation corresponding to the first error type. It may also include information 509 such as name, host, and path, and 6) information 511 about a message set to notify omission of a data call in response to the first error type.

Lastly, the error occurrence information may include condition information 513 for limiting the user terminals that can be set to implement the error situation, and through this, the error occurrence information of FIG. 5 is applied only to the limited terminals, thereby preventing the error situation from occurring. It can be implemented.

FIG. 6 is a diagram illustrating an example of error occurrence information for implementing an error situation corresponding to the second error type.

The error occurrence information shown in FIG. 6 includes 1) information 601 about the first backend server to implement an error situation corresponding to the second error type on the backend service, 2) the first backend server to implement the error situation. Information about the first front-end server that is set as the counterpart front-end server of the server (603), and 3) information about the period managed to implement the error situation and information about the manager who manages the implementation of the error situation (605) may include.

In addition, the error occurrence information is 4) second error type information 607, 5) to a second back-end server that is set as a counterpart back-end server of the first back-end server to implement an error situation corresponding to the second error type. Information 609, such as a path, and 6) information 611, such as a threshold time set in response to the second error type, may also be included.

Lastly, the error occurrence information may include condition information 613 for limiting the user terminals that can be set to implement the error situation, and through this, the error occurrence information of FIG. 6 is applied only to the limited terminals, thereby preventing the error situation from occurring. It can be implemented.

FIG. 7 is a diagram illustrating an example of error occurrence information for implementing an error situation corresponding to a third error type.

The error occurrence information shown in FIG. 7 includes 1) information about the first backend server to implement an error situation corresponding to the third error type on the backend service (701), 2) the first backend server to implement the error situation. Information about the first front-end server that is set as the counterpart front-end server of the server (703), and 3) information about the period managed to implement the error situation and information about the manager who manages the implementation of the error situation (705) may include.

In addition, the error occurrence information is 4) third error type information 707, 5) to the second backend server that is set as the counterpart backend server of the first backend server to implement an error situation corresponding to the third error type. Information 709 such as name, host, path, etc., and 6) information 711 about the contents of data to be included as incorrect response data in response to the third error type.

Lastly, the error occurrence information may include condition information 713 for limiting the user terminals that can be set to implement the error situation, and through this, the error occurrence information of FIG. 7 is applied only to the limited terminals, thereby preventing the error situation from occurring. It can be implemented.

According to various embodiments, in operation 305, the server device 100 may provide error implementation result information for an error situation implemented based on error occurrence information.

For example, the error implementation result information provided by the server device 100 according to operation 305 may include information about the results shown on the front-end service and back-end service when the error situation is implemented and the error is simulated. In other words, information about what situation appeared as a result of the error simulation, what message was displayed, what reaction appeared on the front-end service and back-end service, etc. may be included in the error implementation result information of operation 305.

For example, the error implementation result information provided by the server device 100 in accordance with operation 305 may correspond to information for an administrator who manages the service, and the server device 100 may provide information for the administrator based on such error implementation result information. A message to be provided to users of the provided service may be set. At this time, in order for an error-related message to be provided to the user of the service provided by the server device 100, the customer domain used by the user must be confirmed, so the server device 100 is equipped with one or more front-ends corresponding to the front-end service. In order to implement an error situation among servers, information about the first front-end server set as the counterpart front-end server of the first back-end server is checked, and based on the error implementation result information, an error situation is sent to the user through the first front-end server. You can set an error message to be provided in relation to .

For example, the error implementation result information provided by the server device 100 according to operation 305 may include a message displayed or provided to the administrator as a result when an error situation is implemented and an error is simulated. . At this time, the server device 100 can set a message to be displayed through error implementation result information, and when the message set in this way is displayed as a result of a simulation of an error situation implemented based on the error occurrence information, the error situation It can be managed that the implementation has been performed successfully.

For example, as described above, the implementation of an error situation of the server device 100 may be performed on a test server corresponding to the service provided by the server device 100. The server device 100 may build a specific test server in response to a specific service provided by the server device 100, and apply the error occurrence information set according to operation 303 to the specific test server to resolve the error situation. Operation 305 may be performed to provide implementation and error implementation result information.

If the server device 100 provides a plurality of services, the server device 100 can build each test server for each service included in the plurality of services, and can implement a specific error situation to simulate an error. By checking the service, the error occurrence information set in operation 303 can be applied to the specific test server corresponding to the specific service, and operation 305 can be performed to implement the error situation and provide error implementation result information.

In order to apply error occurrence information to the plurality of services provided by the server device 100, compatible adapters may be separately set for each of the plurality of test servers corresponding to the plurality of services. That is, the error occurrence information set by the server device 100 according to operation 303 can be directly applied to each test server corresponding to each service included in the plurality of services provided by the server device 100 without going through additional compatibility procedures. The server device 100 may set an adapter to be used to apply error occurrence information. The adapter set in this way can be used by registering with each test server corresponding to each service included in the plurality of services provided by the server device 100. As an example, for a specific test server corresponding to a specific service included in the plurality of services provided by the server device 100, the server device 100 may register an adapter set to apply error occurrence information. And, by applying error occurrence information to a specific test server registered through an adapter, an error situation can be implemented in the specific test server.

For example, an adapter registered on a test server can be managed to be activated or deactivated, and when the adapter is activated, it can be set to enable the implementation of an error situation on the test server. That is, even if the adapter is registered on the test server, the server device 100 can manage the adapter to be activated and operate only when an error situation is desired.

For example, if attempts to activate an adapter registered on a test server fail more than a certain number of times, the adapter may be set to be automatically deactivated. In other words, even if an attempt is made to implement an error situation, if the adapter is not activated despite a certain number of activation attempts, it is necessary to prevent unnecessary activation attempt overload. Therefore, if a certain number of attempts to activate the adapter fail, the registered adapter is not activated. It can be set to be disabled.

FIG. 8 is a diagram illustrating a method by which the server device 100 executes an adapter for applying error occurrence information according to various embodiments.

In FIG. 8, the server device 100 sets the adapter to be used to apply error occurrence information to the test server (801), registers the set adapter with the test server corresponding to the service that will implement the error situation (803), and registers (803) By executing the adapter (805), an error situation can be implemented on a test server corresponding to the service. At this time, a flowchart showing registration and execution of the adapter according to FIG. 8 and implementation of the resulting error situation may be the same as FIGS. 9 and 10.

Figure 9 is a diagram illustrating a flow chart in which an adapter for applying error occurrence information is registered and activated.

When an adapter (drill_adapter) for application of error occurrence information is set, the service (service_role) provided by the server device 100 is executed and the adapter can be registered in the test server (service_assists) corresponding to the service (service_role). There is (901). The adapter (drill_adapter) registered on the test server (service_assists) goes through a periodic health check process and can be activated when the administrator attempts to apply error information. If an attempt is made to activate the adapter (drill_adapter), If the adapter fails up to a preset maximum threshold number of attempts, the adapter may be automatically deactivated (903).

FIG. 10 is a flowchart showing how an error situation is implemented by applying error occurrence information based on an adapter.

In FIG. 10, an administrator (user) who can access the service (service_role) provided by the server device 100 and the test server (service_assists) corresponding to the service (service_role) has a certain error situation that will cause an error situation corresponding to a specific error type. Based on the error implementation plan and strategy, desired error occurrence information can be applied to the test server through the adapter (1001).

The administrator (user) generally uses the service (service_role) provided by the server device 100 to obtain results corresponding to specific traffic, or to implement an error situation based on artificially injected traffic to the test server (service_assists). Thus, a result corresponding to artificial injection traffic can be obtained using the service (service_role) (1003). Additionally, the manager can stop the implementation of the error situation for the test server (service_assists). In this case, the data created according to the implementation of the error situation is deleted (1005), but the log according to the implementation and suspension of the error situation is deleted. It can be set to leave a record (1007).

Figure 11 is a diagram showing how various error occurrence information is applied to the test server.

In Figure 11, various error implementation plans and strategies (Drill Plan & Strategy) for applying various error occurrence information by various managers to the test server can be confirmed (1101), and each error implementation plan and strategy can be confirmed. Each corresponding error occurrence information can be applied to the test server through an adapter under the management of each manager (1103). As an example, for a test server corresponding to one service, the first manager may register a first adapter with the test server so that an error situation corresponding to the first error type is implemented in the first user terminal, and the second The administrator may register the second adapter with the test server so that an error situation corresponding to the second error type is implemented in the second user terminal, and each administrator's actions may be performed individually.

At this time, in order to simulate an error in the test server, artificially injected traffic can be used in the test server to implement an error situation that can be distinguished from normal traffic (1105).

It is obvious that each piece of information used in the process of the server device 100 performing an operation method for providing information according to FIGS. 3 to 11 can be combined in various forms.

The embodiments of the present invention disclosed in the specification and drawings are merely provided as 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 is obvious to those skilled in the art that other modifications based on the technical idea of the present invention can be implemented. Additionally, each of the above embodiments can be operated in combination with each other as needed. For example, all embodiments of the present invention can be implemented by a system by combining parts with each other.

Additionally, the method according to the system according to the present invention may be implemented in the form of program instructions that can be executed through various computer means and recorded on a computer-readable medium.

As such, various embodiments of the present invention may be implemented as computer readable code on a computer readable recording medium in certain respects. 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 include read only memory (ROM), random access memory (RAM), and compact disk-read only memory (CD-ROM). ), magnetic tapes, floppy disks, optical data storage devices, and carrier waves (data transmission over the Internet, etc.). Computer-readable recording media may also be distributed across networked computer systems, such that 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.

Additionally, it will be appreciated that the 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, for example, use any storage device, volatile or non-volatile, such as ROM, whether erasable or rewritable, or memory such as, for example, RAM, memory chips, devices or integrated circuits; Alternatively, it may be stored on a storage medium that is optically or magnetically recordable and readable by a machine (e.g., a computer), for example, a compact disk (CD), DVD, magnetic disk, or magnetic tape. . Methods according to various embodiments of the present invention may be implemented by a computer including a control unit and a memory, or a vehicle including such memory or a computer, and such memory is a program containing instructions that implement the embodiments of the present invention. Alternatively, you can see that it is an example of a machine-readable storage medium suitable for storing programs.

Accordingly, the present invention includes a program containing code for implementing the device or method described in the claims of this specification and a machine-readable storage medium (such as a computer) storing such a program. Additionally, such programs may be transmitted electronically through any medium, such as communication signals transmitted over a wired or wireless connection, and the present invention includes equivalents thereof as appropriate.

Although the present invention has been described above with reference to embodiments of the present invention, the embodiments of the present invention disclosed in the specification and drawings are merely presented as specific examples to easily explain the technical content of the present invention and to aid understanding of the present invention. It is not intended to limit the scope. In addition, the embodiments according to the present invention described above are merely illustrative, and those skilled in the art will understand that various modifications and equivalent scope of embodiments are possible therefrom. Therefore, the true technical protection scope of the present invention should be determined by the following patent claims.

Claims (17)

In a method for an electronic device to provide information,
Confirming error type information including a plurality of error types corresponding to a backend service of the service provided by the electronic device;
Setting error occurrence information to implement an error situation corresponding to a specific error type among the plurality of error types on a first backend server included in one or more backend servers corresponding to the backend service; and
Comprising the step of providing error implementation result information for the error situation implemented based on the error occurrence information,
The error occurrence information is,
Information about the first backend server,
Information about a first front-end server that is set as a counterpart front-end server of the first back-end server to implement the error situation among one or more front-end servers corresponding to the front-end service of the service, and
Containing information about a second back-end server among the one or more back-end servers that is set as a counterpart back-end server of the first back-end server to implement the error situation,
How to provide information. According to claim 1,
The step of checking the error type information is,
collecting information about a plurality of error situations occurring in relation to the backend service on the service; and
Comprising classifying the plurality of error situations into the plurality of error types,
How to provide information. According to claim 1,
The plurality of error types are:
The first type of error is missing data calls from a backend server to a counterpart backend server,
A second error type in which the time taken for a data call of a backend server to a counterpart backend server exceeds a threshold time, and
Including a third error type in which incorrect response data is called in response to a data call from a backend server to a counterpart backend server,
How to provide information. According to claim 3,
The step of setting the error occurrence information is,
When the specific error type corresponds to the first error type, setting a message notifying missing data call,
How to provide information. According to claim 3,
The step of setting the error occurrence information is,
If the specific error type corresponds to the second error type, setting the threshold time,
How to provide information. According to claim 3,
The step of setting the error occurrence information is,
When the specific error type corresponds to the third error type, setting information to be included as the incorrect response data,
How to provide information. delete According to claim 1,
The error occurrence information includes information about a period managed to implement the error situation,
How to provide information. According to claim 1,
The error occurrence information includes information about the manager who manages the implementation of the error situation,
How to provide information. According to claim 1,
The error occurrence information includes condition information for limiting user terminals that are set to enable implementation of the error situation,
Set to enable implementation of the error situation only in user terminals that meet the condition information,
How to provide information. According to claim 1,
The method of providing the above information is:
Further comprising setting a message to be displayed through the error implementation result information,
If the message is displayed as a result of the implementation of the error situation, the implementation of the error situation is managed as successfully performed,
How to provide information. According to claim 1,
The method of providing the above information is:
Further comprising the step of building a test server corresponding to the service,
Implementation of the error situation and provision of the error implementation result information are performed by applying the error occurrence information in the test server,
How to provide information. According to claim 12,
The method of providing the above information is:
Setting up an adapter to be used to apply the error occurrence information to the test server; and
Further comprising registering the adapter with the test server,
How to provide information. According to claim 13,
Set to enable implementation of the error situation in the test server based on the fact that the registered adapter is activated,
How to provide information. According to claim 14,
If attempts to activate the adapter fail a certain number of times, the adapter is deactivated.
How to provide information. In a method for an electronic device to provide information,
Confirming error type information including a plurality of error types corresponding to a backend service of the service provided by the electronic device;
Setting error occurrence information to implement an error situation corresponding to a specific error type among the plurality of error types on a first backend server included in one or more backend servers corresponding to the backend service; and
Comprising the step of providing error implementation result information for the error situation implemented based on the error occurrence information,
The method of providing the above information is:
Confirming information about a first front-end server among one or more front-end servers corresponding to the front-end service of the service that is set as a counterpart front-end server of the first back-end server to implement the error situation; and
Based on the error implementation result information, further comprising setting an error information message to be provided in relation to the error situation to the user of the service through the first front-end server,
How to provide information. 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:
Confirming error type information including a plurality of error types corresponding to a backend service of the service provided by the electronic device;
Setting error occurrence information to implement an error situation corresponding to a specific error type among the plurality of error types on a first backend server included in one or more backend servers corresponding to the backend service; and
Controlling the processor to perform the step of providing error implementation result information for the error situation implemented based on the error occurrence information,
The error occurrence information is,
Information about the first backend server,
Information about a first front-end server that is set as a counterpart front-end server of the first back-end server to implement the error situation among one or more front-end servers corresponding to the front-end service of the service, and
Containing information about a second back-end server among the one or more back-end servers that is set as a counterpart back-end server of the first back-end server to implement the error situation,
Electronic devices.

Images