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

Abstract

According to the present invention, a method for an electronic device to provide information is disclosed, which includes the following steps: confirming error type information, the error type information includes a plurality of error types corresponding to a backend service of a service provided by the above-mentioned electronic device; setting error generation information for a first backend server included in one or more backend servers corresponding to the above-mentioned backend service, the error generation information is used to realize an error situation corresponding to a specific error type among the above-mentioned plurality of error types; and providing error realization result information of the above-mentioned error situation, the error situation being realized based on the above-mentioned error generation information.

Description

Operation method of electronic device for providing information and electronic device supporting the operation method

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

With the development of electronic technology, e-commerce has taken a place in the shopping field. Customers can buy items online without going directly to shopping malls or markets. Items purchased online will be delivered to the delivery location requested by the customer.

In the case of e-commerce, processing detailed and accurate product information has a significant impact on service satisfaction, so the industry is discussing various solutions to process information in more detail and accuracy.

In this regard, please refer to previous literature such as KR101756594B1 or KR101500849B1.

[Problem to be solved by the invention] According to the method of the present invention, an electronic device can realize an error situation and provide result information corresponding to the error situation.

The technical issues to be realized by this invention are not limited to the technical issues mentioned above. People with common sense in the technical field to which this invention belongs can clearly understand other technical issues not mentioned based on the following description. [Technical means to solve the problem]

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

The method of providing information by an electronic device in various embodiments may include the following steps: confirming error type information, the error type information includes a plurality of error types corresponding to the backend service of the service provided by the above-mentioned electronic device; setting error generation information for a first backend server included in one or more backend servers corresponding to the above-mentioned backend service, the error generation information is used to realize an error situation corresponding to a specific error type among the above-mentioned plurality of error types; and providing error realization result information of the above-mentioned error situation, the error situation being realized based on the above-mentioned error generation information.

In an exemplary embodiment, the step of confirming the error type information may include the following steps: collecting information of a plurality of error situations occurring in association with the backend service on the service; and classifying the plurality of error situations into the plurality of error types.

In an exemplary embodiment, the above-mentioned multiple error types may include: a first error type, which is a missing data call made to a backend server relative to a backend server; a second error type, which is a time required for calling the data of the backend server relative to the backend server exceeding a critical time; and a third error type, which corresponds to a call error response data of the data call made to the backend server relative to the backend server.

In an exemplary embodiment, the step of setting the error generation information may include the following steps: when the specific error type corresponds to the first error type, setting a message notifying the missing of the data call.

In an exemplary embodiment, the step of setting the error generation information may include the following steps: when the specific error type corresponds to the second error type, setting the critical time.

In an exemplary embodiment, the step of setting the error generation information may include the following step: when the specific error type corresponds to the third error type, setting the information included in the response data as an error.

In an exemplary embodiment, the error generating information may include: information of the first back-end server; information of the first front-end server, the first front-end server being one of the one or more front-end servers corresponding to the front-end service of the service and being configured as a relative front-end server of the first back-end server in order to realize the error situation; and information of the second back-end server, the second back-end server being one of the one or more back-end servers configured as a relative back-end server of the first back-end server in order to realize the error situation.

In an exemplary embodiment, the error generating information may include information about the period of management in a manner to achieve the error condition.

In an exemplary embodiment, the error generation information may include information of a manager who manages the realization of the error situation.

In an exemplary embodiment, the error generating information may include condition information, which is used to limit user terminals that are configured in a manner that enables the error condition, and is configured so that only user terminals that satisfy the condition information can achieve the error condition.

In an exemplary embodiment, the information providing method may further include the following steps: setting a message to be displayed by the error realization result information; and when the message is displayed as a result of realizing the error situation, managing the successful realization of the error situation.

In an exemplary embodiment, the information providing method may further include the following steps: constructing a test server corresponding to the service; and realizing the error situation and providing the error realization result information are implemented in the test server by applying the error generation information.

In an exemplary embodiment, the information providing method may further include the following steps: setting an adapter, which is used to apply the error generating information in the test server; and registering the adapter with the test server.

In an exemplary embodiment, it can be configured as follows: based on activating the registered adapter, the error condition can be realized in the test server.

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

In an exemplary embodiment, the above-mentioned information providing method may further include the following steps: confirming the information of the first front-end server, which is one of the one or more front-end servers corresponding to the front-end service of the above-mentioned service and is set as the relative front-end server of the above-mentioned first back-end server in order to realize the above-mentioned error situation; and based on the above-mentioned error realization result information, setting an error guidance message, which is provided to the users of the above-mentioned service by the above-mentioned first front-end server and is related to the above-mentioned error situation.

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, the processor is controlled to perform the following steps: confirming error type information, the error type information including backend information related to the service provided by the electronic device; end) service; for a first back-end server included in one or more back-end servers corresponding to the above-mentioned back-end service, error generation information is set, and the error generation information is used to realize an error situation corresponding to a specific error type among the above-mentioned multiple error types; and error realization result information of the above-mentioned error situation is provided, and the error situation is realized based on the above-mentioned error generation information.

The various embodiments of the present invention described above are only part of the preferred embodiments of the present invention. People with common sense in the technical field can derive and understand various embodiments reflecting the technical features of the various embodiments of the present invention based on the detailed description described below. [Effects of the invention]

The present invention proposes a method for realizing an error condition in an electronic device and providing result information corresponding to the error condition, which has a technical effect in being able to effectively explore solutions to deal with the error condition.

The effects obtained by the present invention are not limited to the effects mentioned above, and those having common sense in the technical field to which the present invention belongs can clearly understand other effects not mentioned according to the following description.

The following embodiments are combinations of the constituent elements and features of various embodiments in a specified form. Unless otherwise explicitly mentioned, each constituent element or feature is considered to be optional. Each constituent element or feature can be implemented in a form that is not combined with other constituent elements or features. In addition, some constituent elements and features can be combined to form various embodiments. The order of the actions described in various embodiments can be changed. A part of the constituent elements or features of a certain embodiment can be included in other embodiments, or can replace the corresponding constituent elements or features of other embodiments.

In the description of the drawings, procedures or steps that may confuse the subject matter of various embodiments are not described, nor are procedures or steps that can be understood at the level of a person having ordinary knowledge in the technical field.

Throughout the specification, when it is stated that a certain part "comprising or including" a certain constituent element, it means that other constituent elements may be further included unless there is any specific content to the contrary, and other constituent elements are not excluded. In addition, the terms "...part", "...device", "module" and the like recorded 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 related words can be used in a meaning including both the singular and the plural.

The following detailed description in conjunction with the accompanying drawings is intended to illustrate exemplary implementations of various embodiments, but is not intended to represent the only implementation.

In addition, the specific terms used in the various embodiments are provided to help understand the various embodiments, and the use of such specific terms can be changed into other forms without departing from the technical ideas of the various embodiments.

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

Referring to FIG. 1 , the information providing system of various embodiments can be implemented in various types of electronic devices. For example, the information providing system can be implemented in a server device 100 and a user device 200. In other words, the server device 100 and the user device 200 can implement the actions of various embodiments of the present invention based on the information providing system implemented in each device. On the other hand, the information providing system of various embodiments is not limited to that shown in FIG. 1 above, and can also be implemented in more electronic devices and servers.

The server device 100 of various embodiments may be a device that implements 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. In the present invention, in addition to being used as a server, the server device 100 described below can also play a role in the following manner: managing and controlling various front-end servers used for the front-end services of the service and various back-end servers used for the back-end services of the service.

The user device 200 of various embodiments may 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 may be used as the user device 200.

The information providing system of various embodiments may include various modules for performing actions. The modules included in the information providing system may be computer codes and one or more instructions implemented in the following manner, which refers to enabling a physical device (e.g., server device 100 and user device 200) that implements the information providing system (or included in the physical device) to perform a specified action. In other words, the physical device that implements the information providing system stores a plurality of modules in the form of computer codes in a memory, and when executing the plurality of modules stored in the memory, the plurality of modules can enable the physical device to perform the specified actions corresponding to the plurality of modules.

FIG. 2 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 may be various interfaces or ports for receiving user input or outputting 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 be implemented in various forms including key input, touch input, and voice input. As examples of input modules that can receive such user input, in addition to traditional numeric keypads, keyboards or mice, they also include 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 approach of a user, motion sensors that recognize user movements through acceleration sensors or gyroscope sensors, and various forms of input mechanisms that sense or receive other various forms of user input. The input module of the embodiments 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 capacitive touch sensor that senses touch by a touch panel or touch film attached to a display panel, an optical touch sensor that senses touch by an optical method, etc. In addition, the input module can also be implemented in the form of an input interface (USB (Universal Serial Bus) port, PS/2 (Personal System 2) port, etc.) that is connected to an external input device that receives user input instead of the device that senses user input itself. In addition, the output module can output various information. The output module may include a display for outputting images, a speaker for outputting sounds, a tactile device for generating vibrations, and at least one of the output mechanisms of various forms other than these. In addition, the output module may also be implemented in the form of a port-type output interface connected to the above-mentioned individual output mechanisms.

For example, the output module in the form of a display can display text, static images, and videos. The display may include 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 at least one of various devices that can implement image output functions. Such a display may be in the form of a touch display that is integrated with a 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 through 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 means the sending and receiving of data which can be realized by wired or wireless. 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 send and receive data, a short-range communication module using a communication method of the WLAN (Wireless Local Area Network) series such as Wi-Fi or a communication method of the WPAN (Wireless Personal Area Network) series such as Bluetooth and Zigbee, a satellite communication module using a GNSS (Global Navigation Satellite System) such as GPS (Global Positioning System), or a combination thereof.

The memory 230 can store various 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) for driving the server device 100, the data for hosting the website, or the program for generating braille and the data related to the application (e.g., the website application). In addition, the memory 230 can store the module 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. Such a memory 230 can be provided in a built-in type or a removable 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 the components of the server device 100. For example, the processor 240 can execute programs and applications for providing information. The processor 240 can be implemented by a computer or a similar device based on hardware, software, or a combination thereof. In terms of hardware, the processor 240 can be implemented in the form of an electronic circuit that performs control functions by processing electrical signals, and in terms of software, it can be implemented in the form of a program that drives the hardware processor 240. On the other hand, in the case where no particular mention is made 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 module implemented in the above-mentioned information providing system, the module can be interpreted as the processor 240 controlling the server device 100 and the user device 200 to perform 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.

When implemented by hardware, the methods of various embodiments can 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 by firmware or software, the methods of various embodiments can be implemented in the form of modules, programs or functions that implement the functions or actions described below. For example, the software code can be stored in a memory and driven by a processor. The memory can be located inside or outside the processor and can exchange data with the processor through various well-known mechanisms.

Based on the above technical ideas, various embodiments are described in more detail below. For the various embodiments described below, the contents described previously can be applied. For example, actions, functions, terms, etc. that are not defined in the various embodiments described below can be implemented and described based on the contents described previously.

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

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

3, the server device 100 can provide error realization result information of the error situation, and in order to implement the action of providing the error realization result information, confirm the error type information, the error type information includes a plurality of error types (301) corresponding to the backend service of the service; for one or more corresponding to the backend service The first backend server included in the backend server sets error generation information, which is used to realize an error situation corresponding to a specific error type among a plurality of error types (303); and provides error realization result information of the error situation, which is realized based on the error generation information (305).

According to FIG. 3 , the action of the server device 100 providing the error realization result information can be implemented for the service provided by the server device 100 or the service related to the server device 100. The above service can be equivalent to a service in which a plurality of users utilizing the service can order and purchase a plurality of items sold in the service. The types or categories of the plurality of items sold in the service are not limited and can include various types or categories of items registered by the seller for selling items. At this time, the service provided by the server device 100 or the service related to the server device 100 can be divided into a front-end service and a back-end service as shown in FIG. 4 .

FIG. 4 is a diagram showing an overview of front-end services and back-end services.

Referring to identification number 401, the front-end service may include various customer domains for the services provided by the server device 100, and various front-end servers corresponding to the various customer domains may correspond to the front-end services. Here, the customer domain may refer to a domain corresponding to various service pages accessible to users on the UI/UX (user interface/user experience) of the services provided by the server device 100. The front-end service may be understood as a user-side management terminal configured in the following manner: data requested in each customer domain may be managed according to the user's UI/UX connection and utilization.

Referring to identification number 403, the backend service may include various database domains related to the database used for the service provided by the server device 100, and various backend servers corresponding to the above-mentioned various database domains may correspond to the above-mentioned backend services. Here, the database domain may refer to a domain corresponding to a database configured in the following manner: storing and managing each data based on the type or type of data, and the above-mentioned each data is stored and managed by the server device 100. The backend service can be understood as a database-side management terminal configured in the following manner: it can store, confirm and/or call the data obtained in connection with the service provided by the server device 100.

The data that the server device 100 wants to call in response to the data request made by the user through the UI/UX can be served from the backend service to the frontend service. For example, the first frontend server corresponding to the specific client domain used by the user can receive the service (serving) of the data that the server device 100 wants to call from the first backend server, and the first backend server corresponds to the specific database related to the above-mentioned specific client domain. In addition, if necessary, the first backend server can also act in the following manner: it can call data from another second backend server, and serve the data called as described above to the first frontend server.

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

For example, the action 301 of the server device 100 confirming the error type information may be an action of collecting various error conditions that occur or are recognized in relation to the backend service, and classifying the collected error conditions based on a fixed standard. That is, in the service provided by the server device 100, the server device 100 may collect information on a plurality of error conditions that occur in relation to the backend service, and classify the collected plurality of error conditions into a plurality of error types. The action 301 may be equivalent to the action of confirming the information on the plurality of error types classified as described above.

For example, the plurality of error types included in the error type information confirmed by the server device 100 according to the action 301 may include error types corresponding to various error situations that occur when the backend server wants to call data from the relative backend server. Specifically, the plurality of error types may include: 1) the first error type, which is missing the data call made to the relative backend server of the backend server; 2) the second error type, which is the time required for calling the data of the relative backend server of the backend server exceeds the critical time; and 3) the third error type, which corresponds to the response data of the call made to the relative backend server of the backend server.

According to various embodiments, in action 303, the server device 100 may set error generation information for a first backend server included in one or more backend servers corresponding to the backend service, wherein the error generation information is used to implement an error situation corresponding to a specific error type among a plurality of error types.

For example, the error generation information set by the server device 100 according to action 303 may include information for implementing and simulating an error situation corresponding to a specific error type among the various error types described in action 301 in the test server.

Specifically, when the above-mentioned specific error type corresponding to the error situation to be realized by the server device 100 corresponds to the first error type, the first error type misses a data call made to the backend server of the backend server, and the server device 100 can realize the error situation of missing the data call, and set it in a manner of displaying a message notifying the missing of the data call, thereby simulating the error. In this case, in order to realize the error situation as desired and simulate the error, the server device 100 can set the message notifying the missing of the data call separately when setting the error generation information according to action 303.

When the above-mentioned specific error type corresponding to the error situation that the server device 100 intends to realize corresponds to the situation of the second error type, the second error type is used for calling the back-end server and the time required for the data of the back-end server exceeds the critical time. The server device 100 can simulate the error by realizing the error situation, and the error situation includes that the time of the data call is delayed due to exceeding the critical time, or the response data corresponding to the data call is not received within the above-mentioned critical time. In this case, in order to realize the error situation and simulate the error as desired, the server device 100 can set the critical time that will become the benchmark of the data call delay when setting the error generation information according to action 303.

Furthermore, when the above-mentioned specific error type corresponding to the error situation that the server device 100 intends to realize corresponds to the situation of the third error type, the third error type corresponds to a data call made to a back-end server relative to the back-end server and calls for erroneous response data, the server device 100 can simulate the error by realizing the error situation, which calls erroneous data that is irrelevant to it instead of calling appropriate data corresponding to the data call. In this case, in order to realize the error situation and simulate the error as desired, the server device 100 can set the information included as the error response data separately when setting the error generation information according to action 303.

For example, the error generation information set by the server device 100 according to action 303 may include: information of the first back-end server, which is designated to realize the error situation; information of the first front-end server, which is one of the one or more front-end servers corresponding to the front-end service and is set as the relative front-end server of the above-mentioned first back-end server to realize the error situation; and information of the second back-end server, which is one of the one or more back-end servers corresponding to the back-end service and is set as the relative back-end server of the above-mentioned first back-end server to realize the above-mentioned error situation. That is, information of the data call path that will cause the error or the front-end server and/or back-end server belonging to the data service path may be included in the error generation information.

For example, the error generation information set by the server device 100 according to the action 303 may include information about the period of management in a manner to achieve the error situation. That is, in the test server, the error situation to be achieved by the server device 100 is managed and supervised. In order to prevent the error situation from continuing to occur regardless of the error simulation intention as described above, the information about the period of management in a manner to achieve the error situation may be included in the error generation information.

For example, the error generation information set by the server device 100 according to action 303 may include information of an administrator who manages the realization of the error situation. That is, the information of the administrator who manages the realization of the error situation in the following manner may be included in the error generation information: information indicating which administrator wants to simulate the error situation that the server device 100 wants to realize in the test server to manage and supervise the error situation.

For example, the error generation information set by the server device 100 according to the action 303 may include condition information for limiting the user terminals that are set in a manner that can achieve the error situation. If all user terminals connected to the test server are set in a manner that can achieve the error situation without restriction, users who are not related to the realization of the error situation in the test server or users who are unaware of the fact that the simulation is being performed in the test server in a manner that realizes a fixed error situation may encounter problems when connecting to the test server to perform other services. Therefore, the error generation information set by the server device 100 according to action 303 may include condition information that is restricted in a manner that the error situation can only be realized in a fixed user terminal, and may be set so that only a user terminal that satisfies the condition information can realize the error situation in the test server. The condition information as described above may include conditions determined according to the input of an administrator. As an example, the administrator may input conditions that are restricted in a manner that only a user terminal with fixed identification information can realize the error situation.

FIG. 5 is a diagram showing an example of error generation information for realizing an error situation corresponding to the first error type.

The error generation information shown in Figure 5 may include: 1) information 501 of the first back-end server, which is used to implement the error situation corresponding to the first error type on the back-end service; 2) information 503 of the first front-end server, which is set as the relative front-end server of the first back-end server in order to implement the error situation; and 3) information 505 of the administrator, who manages the information during the period of management in a manner to implement the error situation and the implementation of the error situation.

In addition, the above-mentioned error generation information may also include: 4) information 507 of the first error type; 5) information 509 such as the name, host, path, etc. of the second back-end server, which is set as the relative back-end server of the first back-end server in order to realize the error situation corresponding to the first error type; and 6) information 511 such as messages, which is set in a manner corresponding to the first error type to inform the omission of the data call.

Finally, the error generation information may include condition information 513, which is used to limit the user terminals that are configured in a manner that can achieve the error situation, so that the error generation information of FIG. 5 can be applied only in the restricted terminals to achieve the error situation.

FIG. 6 is a diagram showing an example of error generation information for realizing an error situation corresponding to the second error type.

The error generation information shown in Figure 6 may include: 1) information 601 of the first back-end server, which is used to implement the error situation corresponding to the second error type on the back-end service; 2) information 603 of the first front-end server, which is set as the relative front-end server of the first back-end server in order to implement the error situation; and 3) information 605 of the administrator, who manages the information during the period of management in a manner to implement the error situation and the implementation of the error situation.

Furthermore, the error generation information may also include: 4) information 607 of the second error type; 5) information 609 of the path of the second back-end server, etc. The second back-end server is set as the relative back-end server of the first back-end server in order to realize the error situation corresponding to the second error type; and 6) information 611 of the critical time, etc. The critical time is set corresponding to the second error type.

Finally, the error generation information may include condition information 613, which is used to limit the user terminals that are configured in a manner that can achieve the error situation, so that the error generation information of FIG. 6 can be applied only in the restricted terminals to achieve the error situation.

FIG. 7 is a diagram showing an example of error generation information for realizing an error situation corresponding to the third error type.

The error generation information shown in Figure 7 may include: 1) information 701 of the first back-end server, which is used to implement the error situation corresponding to the third error type on the back-end service; 2) information 703 of the first front-end server, which is set as the relative front-end server of the first back-end server in order to implement the error situation; and 3) information 705 of the administrator, who manages the information during the period of management in a manner to implement the error situation and the implementation of the error situation.

Furthermore, the error generation information may also include: 4) information 707 of the third error type; 5) information 709 of the name, host, path, etc. of the second back-end server, which is set as the relative back-end server of the first back-end server in order to realize the error situation corresponding to the third error type; and 6) information 711 of content, etc., which corresponds to the third error type and is included as error response data.

Finally, the error generation information may include condition information 713, which is used to limit the user terminals that are configured in a manner that can achieve the error situation, so that the error generation information of FIG. 7 can be applied only in the restricted terminals to achieve the error situation.

According to various embodiments, in action 305, the server device 100 may provide error realization result information of the error situation realized based on the error generation information.

For example, according to action 305, the error realization result information provided by the server device 100 may include information of the results displayed on the front-end service and the back-end service when the error situation is realized and the error situation is simulated. That is, information such as a certain situation occurring as a result of the error simulation, a certain message being displayed, a certain reaction occurring on the front-end service and the back-end service, etc. may be included in the error realization result information of action 305.

For example, according to action 305, the error realization result information provided by the server device 100 may be information for an administrator who manages services, and based on the error realization result information as described above, a message to be provided to users of the service provided by the server device 100 may be set. At this time, in order to provide error-related information to users of the service provided by the server device 100, it is necessary to be able to confirm the client domain used by the user. Therefore, the server device 100 can confirm the information of the first front-end server. The first front-end server is one or more front-end servers corresponding to the front-end service, which is set as the relative front-end server of the first back-end server in order to realize the error situation. Based on the error realization result information, the error guidance message is set. The first front-end server is the one related to the error situation that is to be provided to the user by the above-mentioned first front-end server.

For example, according to action 305, the error realization result information provided by the server device 100 may include the following message: when simulating in a manner that an error occurs by realizing an error situation, it is displayed or provided to the administrator as a result. At this time, the server device 100 can set the message displayed by the error realization result information, and when the message set as described above is displayed as a result of the simulation of the error situation realized based on the error generation information, the realization of the error situation can be managed as successfully realized.

For example, as described above, the realization of the error situation of the server device 100 can be realized in the test server corresponding to the service provided by the server device 100. The server device 100 can construct a specific test server corresponding to the specific service provided by the server device 100, and apply the error generation information set according to the action 303 in the specific test server, thereby implementing the action 305 for realizing the error situation and providing the error realization result information.

When the server device 100 provides multiple services, the server device 100 can construct test servers for each service included in the multiple services, and can confirm the specific service to be simulated by realizing the error situation, thereby applying the error generation information set according to action 303 in the specific test server corresponding to the above-mentioned specific service, and implementing action 305 for realizing the error situation and providing error realization result information.

In order to apply the error generation information in the plurality of services provided by the server device 100, an adapter may be separately set, and the adapter may be compatible with each of the plurality of test servers corresponding to the plurality of services. That is, the server device 100 may set an adapter for applying the error generation information so that the error generation information set by the server device 100 according to the action 303 may 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 an additional compatibility procedure. The adapter set as described above may be registered and used in 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 a plurality of services provided by the server device 100, the server device 100 may register an adapter configured for error application generation information. If error generation information is applied in the specific test server registered through the adapter, the error situation may be realized in the above-mentioned specific test server.

For example, the adapter registered on the test server can be managed in an activated or deactivated manner, and can be configured in a manner that an error condition can be realized in the test server when the adapter is activated. That is, even if the adapter is registered with the test server, the server device 100 can manage it in a manner that the adapter is activated only when an error condition is desired to be realized.

For example, it is possible to configure the adapter to be automatically deactivated when attempts to activate the adapter registered on the test server have failed more than a fixed number of times. That is, if the adapter is not activated despite more than a fixed number of activation attempts, even if an error condition is attempted, it is necessary to prevent overload with unnecessary activation attempts, so it is possible to configure the adapter to be deactivated when attempts to activate the adapter have failed more than a fixed number of times.

FIG. 8 is a diagram showing a method for implementing an adapter for applying error generating information by a server device 100 according to various embodiments.

In FIG8 , the server device 100 may configure an adapter for use in applying error generation information in a test server ( 801 ), register the configured adapter in a test server corresponding to a service for which an error condition is to be realized ( 803 ), and realize the error condition in the test server corresponding to the service by executing the registered adapter ( 805 ). At this time, the flow chart showing the registration and execution of the adapter in FIG8 , and the realization of the error condition caused thereby, may be the same as FIG9 to FIG10 .

FIG. 9 is a flow chart showing the process of registering and activating an adapter for applying error generating information.

In the case of setting an adapter (drill_adapter) for applying error-generating information, the service (service_role) provided by the server device 100 may be executed, and the adapter may be registered with the test server (service_assists) corresponding to the service (service_role) (901). The adapter (drill_adapter) registered with the test server (service_assists) may undergo a periodic status confirmation (healthy check) procedure and be activated in the process of the administrator intending to apply the error-generating information, but in the case of a preset maximum critical number of attempts to activate the adapter (drill_adapter) being failed, the adapter may be automatically deactivated (903).

FIG. 10 is a flow chart showing the implementation of an error condition based on applying error generating information to an adapter.

In FIG. 10 , an administrator (user) who has access to the service (service_role) provided by the server device 100 and the test server (service_assists) corresponding to the service (service_role) can apply the expected error generation information (1001) in the test server through an adapter based on a fixed error implementation plan and strategy for generating error conditions corresponding to specific error types.

The manager (user) can usually use the service (service_role) provided by the server device 100 to obtain the result corresponding to the specific traffic, or in association with the realization of the error situation of the artificially injected traffic based on the test server (service_assists), use the service (service_role) to obtain the result corresponding to the artificially injected traffic (1003). In addition, the manager (manager) can interrupt the realization of the error situation of the test server (service_assists). In this case, the data generated by the realization of the error situation can be deleted (1005), and it is set to leave the log record of the realization and interruption of the error situation (1007).

FIG. 11 is a diagram showing the state of applying various error generation information to a test server.

In FIG. 11 , for a test server, multiple administrators may confirm various error realization plans and strategies (Drill Plan & Strategy) (1101) for applying various error generation information, and each error generation information corresponding to each error realization plan and strategy may be applied in the test server through an adapter under the management of each administrator (1103). For example, for a test server corresponding to a service, the first administrator can register the first adapter in the test server so that the error situation corresponding to the first error type is realized in the first user terminal. The second administrator can register the second adapter in the test server so that the error situation corresponding to the second error type is realized in the second user terminal. The actions of each administrator can be implemented independently.

At this time, in order to simulate the error in the test server, artificially injected traffic (Injected Traffic) (1105) which can be distinguished from normal traffic to achieve the error situation can be used in the test server.

Needless to say, according to FIG. 3 to FIG. 11 , each information used in the process of the server device 100 implementing the method for providing information can be combined in various forms.

The embodiments of the present invention disclosed in this specification and drawings are only specific examples provided to easily explain the technical content of the present invention and help understand the present invention, and are not intended to limit the scope of the present invention. That is, it goes without saying that for those with common sense in the technical field to which the present invention belongs, other variations can be implemented based on the technical ideas of the present invention. In addition, the above-mentioned embodiments can be combined with each other as needed. For example, a part of all the embodiments of the present invention can be combined with each other and implemented by the system.

Furthermore, the system and methods of the present invention can be implemented in the form of program commands that can be implemented by various computer methods 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 read by a computer system. Examples of computer readable recording media may include: read only memory (ROM), random access memory (RAM), compact disk-read only memory (CD-ROM), magnetic tape, floppy disk, optical data storage device, and carrier wave (sending data via the Internet, etc.). The computer-readable recording medium can also be distributed through a computer system connected by a network, so that the computer-readable code is stored and executed in a distributed manner. In addition, the functional programs, codes and code segments used to implement various embodiments of the present invention can be easily interpreted by a skilled programmer in the field of application of the present invention.

Furthermore, it is known that the apparatus 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, in a volatile or non-volatile storage device such as a ROM, or a RAM, a memory chip, a device or an integrated circuit, or a storage medium such as a compact disk (CD), a DVD (Digital Versatile Disc), a disk or a tape that can be recorded optically or magnetically and can be read by a machine (e.g., a computer), regardless of whether it can be deleted or recorded again. It can be known 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 storage medium that includes a program that includes commands for implementing the embodiments of the present invention or can be read by a machine suitable for storing programs.

Therefore, the present invention includes a program of code for realizing the device or method described in the scope of the invention application of this specification and a storage medium readable by a machine (computer, etc.) storing such a program. In addition, such a program can be electronically transferred by any medium such as a communication signal transmitted by a wired or wireless connection, and the present invention appropriately includes its equivalents.

The above description is made with reference to the embodiments of the present invention, but the embodiments of the present invention disclosed in this specification and drawings are only specific examples provided to easily explain the technical content of the present invention and help understand the present invention, and are not intended to limit the scope of the present invention. In addition, it can be understood that the embodiments of the present invention described above are only examples, and those with common sense in the field can realize various variations and equivalent embodiments based on them. Therefore, the true technical protection scope of the present invention should be defined according to the following invention patent application scope.

100: Server device 200: User device 210: Input/output unit 220: Communication unit 230: Memory 240: Processor 301: Action 303: Action 305: Action 401: Identification number 403: Identification number 501: Information 503: Information 505: Information 507: Information 509: Information 511: Information 513: Conditional information 601: Information 603: Information 605: Information 607: Information 609: Information 611: Information 613: Conditional information 701: Information 703: Information 705: Information 707: Information 709: Information 711: Information 713: Condition Information 801: Set up the adapter for use in applying error generation information in the test server 803: Register the adapter to the test server corresponding to the service to achieve the error condition 805: Execute the adapter 901: Action 903: Action 1001: Action 1003: Action 1005: Action 1007: Action 1101: Action 1103: Action 1105: Action

FIG. 1 is a diagram for explaining an information providing system that can implement various embodiments of an operation method of an electronic device for providing information. FIG. 2 is a diagram showing the configuration of a server device 100 and a user device 200 of various embodiments. FIG. 3 is a diagram showing the operation method of a server device 100 for providing information of various embodiments. FIG. 4 is a diagram showing an overview of a front-end service and a back-end service. FIG. 5 is a diagram showing an example of error generation information for implementing an error situation corresponding to the first error type. FIG. 6 is a diagram showing an example of error generation information for implementing an error situation corresponding to the second error type. FIG. 7 is a diagram showing an example of error generating information for realizing an error situation corresponding to the third error type. FIG. 8 is a diagram showing a method in which the server device 100 of various embodiments executes an adapter for applying error generating information. FIG. 9 is a flowchart showing registration and activation of an adapter for applying error generating information. FIG. 10 is a flowchart showing an error situation realized by applying error generating information based on an adapter. FIG. 11 is a diagram showing a state in which various error generating information is applied to a test server.

301:Action

303:Action

305:Action

Claims (15)

A method for providing information, which is an electronic device providing information, comprising the following steps: For a first backend server included in one or more backend servers corresponding to a backend service, error generation information is set, the error generation information is used to realize an error situation corresponding to a specific error type among a plurality of error types of the above-mentioned backend service included in the error type information; and providing error realization result information of the above-mentioned error situation, the error situation is realized based on the above-mentioned error generation information, wherein the error generation information includes: Information of the above-mentioned first backend server, Information of the first front-end server, which is one of the one or more front-end servers corresponding to the front-end service and is set as the relative front-end server of the first back-end server in order to achieve the above-mentioned error situation, Information of the second back-end server, which is one of the one or more back-end servers and is set as the relative back-end server of the first back-end server in order to achieve the above-mentioned error situation, and Information for specifying a user terminal, which is connected through the first front-end server to achieve the above-mentioned error situation. The information providing method of claim 1 further comprises the following steps: Collecting information about a plurality of error situations occurring in connection with the above-mentioned backend service; and Classifying the above-mentioned plurality of error situations into the above-mentioned plurality of error types. The information providing method of claim 1, wherein the plurality of error types include: The first error type is a data call made to a backend server relative to a backend server is missed; The second error type is a time required to call the data of the backend server relative to the backend server exceeds a critical time; and The third error type is a response data corresponding to a data call made to a backend server relative to the backend server and a call error. As in the information providing method of claim 3, the step of setting the error-generating information includes the following steps: When the specific error type corresponds to the first error type, setting a message notifying the missing data call. In the information providing method of claim 3, the step of setting the error-generating information includes the following steps: When the specific error type corresponds to the second error type, the critical time is set. In the information providing method of claim 3, the step of setting the error-generating information includes the following steps: In the case where the specific error type corresponds to the third error type, setting the information included in the response data as an error. An information providing method as claimed in claim 1, wherein the error-generating information includes information about a period of management in a manner that realizes the error situation. The information providing method of claim 1, wherein the error-generating information includes information of a manager who manages the realization of the error. The information providing method of claim 1 further comprises the following steps: Setting a message to be displayed by the above-mentioned error realization result information; and When the above-mentioned message is displayed as a result of realizing the above-mentioned error situation, the management successfully realizes the above-mentioned error situation. The information providing method of claim 1 further comprises the following steps: Constructing a test server corresponding to the service provided by the electronic device; and The realization of the error situation and the provision of the error realization result information are implemented by applying the error generation information in the test server. The information providing method of claim 10 further comprises the following steps: Setting an adapter, which is used to apply the error-generating information in the test server; and Registering the adapter with the test server. The information providing method of claim 11 is configured as follows: Based on the activation of the registered adapter, the error can be realized in the test server. An information providing method as claimed in claim 12, wherein the adapter is deactivated when attempts to activate the adapter fail more than a fixed number of times. The information providing method of claim 1 further comprises the following steps: Confirming the information of the first front-end server; and Based on the error realization result information, setting an error guidance message, wherein the error guidance message is provided to the user by the first front-end server and is related to the error situation. 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: for a first backend server included in one or more backend servers corresponding to a backend service, setting error generation information, the error generation information being used to realize an error situation corresponding to a specific error type among a plurality of error types of the backend service included in error type information; and providing error realization result information of the error situation, the error situation being realized based on the error generation information, The error generating information includes: Information of the first backend server, Information of the first frontend server, the first frontend server is one of the one or more frontend servers corresponding to the frontend service and is set as the relative frontend server of the first backend server in order to realize the above error situation, Information of the second backend server, the second backend server is one of the one or more backend servers and is set as the relative backend server of the first backend server in order to realize the above error situation, and Information for specifying a user terminal, the user terminal is connected through the first frontend server to realize the above error situation.