TWI898359B - Apparatus for providing alarm information and method thereof and non-transitory computerreadable recording medium - Google Patents

Abstract

According to the present invention, a method for providing information in an electronic device including a repository for storing data is disclosed, comprising the following steps: identifying one or more service departments; obtaining one or more conditional information associated with each of the one or more service departments; storing the one or more conditional information in the repository; and, when a service-related event occurs, determining whether to provide a service-related notification based on the one or more conditional information stored in the repository.

Description

Device and method for providing notification information and non-temporary computer-readable recording medium

The present invention relates to a device and method for providing notification information. More specifically, the present invention relates to an electronic device and method that obtains and stores one or more conditional information associated with each of one or more service departments in a repository. When a service-related event occurs, the device determines whether to provide a service-related notification based on the one or more conditional information.

A proxy server is a server that allows clients to indirectly connect to other upstream services. The proxy server transfers data between the client and the server, effectively processing messages sent across a computer network.

In one embodiment, a proxy server can further implement the function of detecting and notifying errors that occur during data communication (e.g., a request failure transmitted by a client). For example, whenever a request is generated, the proxy server can emit one or more metric events that track the request. However, when the proxy server implements the error notification function as described above, the scalability and flexibility of the notification must be limited to avoid excessive burden on the proxy server. Consequently, there are limitations such as the inability to flexibly adjust the criteria for determining whether an error is significant enough to require notification, and the inability to flexibly adjust the recipients of the error notification.

For related information, please refer to previous documents such as KR20180124299A and KR20090000734A.

The present embodiment aims to solve the aforementioned problem by providing an electronic device and method thereof: identifying one or more service departments; obtaining one or more conditional information associated with each of the one or more service departments; storing the one or more conditional information in a repository; and, when a service-related event occurs, determining whether to provide a service-related notification based on the one or more conditional information stored in the repository.

The technical issues to be achieved by this embodiment are not limited to the technical issues described above. Other technical issues can be derived based on the following embodiments.

One embodiment of a method for providing information in an electronic device including a repository for storing data includes the following steps: identifying one or more service departments; obtaining one or more conditional information associated with each of the one or more service departments; storing the one or more conditional information in the repository; and, when an event related to a service occurs, determining whether to provide a notification related to the service based on the one or more conditional information stored in the repository.

According to one embodiment, determining whether to provide the notification may include the following steps: confirming one or more of the event type information and information about the service associated with the event; and, based on the event type information and information about the service associated with the event, confirming whether at least a portion of the one or more conditional information is satisfied.

According to one embodiment, the event type information may include error code information corresponding to the event.

According to one embodiment, the electronic device may be a device different from the device that implements the agent function for providing the above-mentioned service.

According to one embodiment, the step of determining whether to provide a notification related to the service includes the step of determining the object that will receive the notification. The object may include a device that implements the agent function and at least a portion of the one or more service departments.

According to one embodiment, the step of confirming the one or more service departments may include one or more of the following steps: obtaining a register request from the one or more service departments; and obtaining register information notifying the one or more service departments.

According to one embodiment, one or more of the register request and the information notified to the register may include one or more of the conditional information.

According to one embodiment, the one or more conditional information may include the following condition: providing the above notification when the number of events related to a specific service department generated within a set time range exceeds a set threshold.

According to one embodiment, the step of obtaining the one or more conditional information may include the following steps: obtaining one or more feature information associated with each of the one or more service departments; and determining the conditions for providing the notification for each of the one or more service departments based on the one or more feature information.

According to one embodiment, the one or more characteristic information may include one or more of the following: the size of the one or more service departments, the functions of the one or more service departments, and the history of providing the notifications to the one or more service departments.

An electronic device for providing information in one embodiment includes a transceiver, a data storage repository, and a processor. The processor is configured to: connect to the transceiver and the data storage repository to identify one or more service departments; obtain one or more condition information associated with each of the one or more service departments; store the one or more condition information in the data storage repository; and, when a service-related event occurs, determine whether to provide a notification related to the service based on the one or more condition information stored in the data storage repository.

Specific details of other embodiments are included in the detailed description and drawings.

According to the present invention, an electronic device and method for providing notification information can ensure scalability and flexibility when determining whether to provide service-related notifications and determining the recipients of the notifications.

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

110: Electronic devices

111: Storage

112: Transceiver

113: Processor

120: Customer Service Department

210:Action

220:Action

230:Action

240:Action

301: Domain Registration Request

310: Proxy Function

311: Streaming request

320:Agency Service Group

321: Manually set notifications

330: Notification rule repository

331: Notification Rules

340: Metrics and Analysis Services

341: Generate notification

401: Domain Registration Request

410: Routing & Notification Repository

411: Routing rules

412: Notification generated

420: Proxy function

421: Measurement Event

430: Notification system

431: Trigger

510: Partial

520: Partial

521: Partial

522: Partial

Figure 1 is a schematic diagram showing the structure of a system for providing notification information according to one embodiment.

Figure 2 is a flowchart illustrating a method for providing notification information in an electronic device according to one embodiment.

FIG3 is a diagram used to exemplarily illustrate a previous notification providing method according to an embodiment.

FIG4 is a diagram illustrating a notification providing method according to an embodiment of the present invention.

FIG5 is a diagram illustrating an interface for obtaining one or more conditional information according to an embodiment.

The terms used in the embodiments are selected to the greatest extent possible from commonly used terms, taking into account the functions of the present invention. However, these terms may vary depending on the intentions of those skilled in the art, precedents, the emergence of new technologies, and so on. Furthermore, in certain cases, the applicant may arbitrarily select terms. In such cases, their meanings will be detailed in the corresponding description. Therefore, the terms used in this invention should be defined based on their meanings and the overall content of the invention, rather than simply based on their names.

Throughout this manual, when a section is described as "including" a certain component, unless otherwise stated, it implies that other components may be included, not excluded. Furthermore, terms such as "unit" and "module" used in this manual refer to a unit that processes at least one function or action and may be implemented by hardware or software, or a combination of hardware and software.

The phrase "at least one of a, b, and c" throughout this specification may include "a alone," "b alone," "c alone," "a and b," "a and c," "b and c," or "all three of a, b, and c."

The term "terminal" mentioned below can be implemented as a computer or portable terminal, which can connect to a server or other terminals via a network. Computers include, for example, laptops, desktops, and the like equipped with web browsers. Portable terminals, as wireless communication devices that ensure portability and mobility, include, for example, IMT (International Mobile Telecommunication), CDMA (Code Division Multiple Access), W-CDMA (W-Code Division Multiple Access), LTE (Long Term Evolution), and all types of handheld wireless communication devices, including smartphones and tablets.

The following describes an embodiment of the present invention in detail with reference to the accompanying drawings so that those skilled in the art can easily implement the present invention. However, the present invention can be implemented in various forms and is not limited to the embodiment described here.

Below, with reference to the accompanying drawings, an embodiment of the present invention is described in detail.

When describing the embodiments, descriptions of technical contents that are well-known in the art and not directly related to the present invention are omitted. This is done to more clearly convey the main points of the present invention and avoid confusion.

For similar reasons, some components may be exaggerated, omitted, or shown schematically in the accompanying drawings. Furthermore, the dimensions of each component do not necessarily reflect the actual dimensions. In the drawings, identical or corresponding components are given the same reference numbers.

The advantages and features of the present invention, as well as methods for achieving such advantages and features, will become apparent with reference to the accompanying drawings and the embodiments described in detail below. However, the present invention is not limited to the embodiments disclosed below and can be implemented in a variety of different forms. These embodiments are provided solely to fully disclose the present invention and enable those skilled in the art to fully understand the scope of the invention. The present invention is defined solely by the scope of the patent application. Throughout this specification, the same reference numerals may represent the same components.

At this point, it should be understood that the combination of each block of the process flow chart and the flowchart can be implemented by computer program instructions. These computer program instructions can be loaded into a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device. Therefore, when these instructions are executed by the processor of the computer or other programmable data processing device, they produce a method for performing the functions described in the blocks of the flow chart. To perform the functions in a specific manner, these computer program instructions can also be stored in a computer-usable or computer-readable memory that is readable by the computer or other programmable data processing device. Therefore, the instructions stored in the computer-usable or computer-readable memory can also produce an article of manufacture that includes the instruction method for performing the functions described in the blocks of the flow chart. Computer program instructions can also be loaded onto a computer or other programmable data processing device, thereby executing a series of action steps on the computer or other programmable data processing device to generate a process executed by the computer. The instructions executed by the computer or other programmable data processing device can also provide steps for performing the functions described in the blocks of the flowchart.

Furthermore, each block may represent a module, segment, or portion of code that includes one or more executable instructions for performing a specific logical function. Furthermore, it should be noted that in some alternative implementations, the functions described in the blocks may not occur in the order in which they are described. For example, two blocks shown in succession may be executed simultaneously, or may occasionally be executed in the reverse order depending on the corresponding functions.

Figure 1 is a schematic diagram showing the structure of a system for providing notification information according to one embodiment.

According to various embodiments, a system for providing notification information includes an electronic device 110 and one or more service units 120. The system for providing notification information of one embodiment may further include a network that supports information transmission and reception between the electronic device 110, one or more service units 120, and at least a portion of external devices.

According to one embodiment, actions associated with a series of information provision methods in various embodiments can be implemented by a single physical device. In this case, throughout this disclosure, actions described as being performed by one or more service units 120 can be understood as actions performed by the electronic device 110 as a single physical device. Data transmission and reception between one or more service units 120 and the electronic device 110 can be understood as data flow within the electronic device 110 and/or interaction between the electronic device 110 and the first user. For example, the action of "obtaining one or more conditional information" described below may include the action of receiving one or more conditional information from one or more service departments 120. If the system providing notification information includes one or more service departments 120, the action can be understood as the action of sending and receiving data associated with one or more conditional information within the electronic device 110.

For ease of explanation, the following description is based on an embodiment in which a system for providing notification information includes an electronic device 110 and one or more service departments 120. The description below is applicable to various embodiments within the scope of the present invention.

Electronic device 110 of a system for providing notification information may include a storage 111, a transceiver 112, and a processor 113. Storage 111 stores one or more conditional information associated with each of one or more service departments. Furthermore, storage 111 may store information used to implement at least one of the methods described below with reference to Figures 2 to 5. Storage 111 may be a volatile memory or a non-volatile memory.

The electronic device 110 can connect to and exchange data with external devices via the transceiver 112. For example, the electronic device 110 can receive one or more conditional information via the transceiver 112 and can also provide notifications related to services.

Processor 113 may include at least one of the devices described below with reference to Figures 2 through 5 , or implement at least one of the methods described below with reference to Figures 2 through 5 . Processor 113 may execute programs and control electronic device 110 for generating signals. The code of the programs executed by processor 113 may be stored in repository 111 .

According to one embodiment, electronic device 110 may be a different device from the device that implements the proxy function for providing services. This is described in more detail below with reference to Figures 2 through 5 .

The electronic device 110 and one or more service units 120 each refer to a unit that processes at least one function or action, which may be implemented through hardware or software, or a combination of hardware and software. Furthermore, as described above, throughout the embodiments, the electronic device 110 and one or more service units 120 are referred to as separate devices and servers. However, they may be logically separate structures, at least part of which may be implemented through functions separated from a single device or server.

According to one embodiment, the electronic device 110 and one or more service departments 120 may include multiple computer systems or computer software implemented via a network server. For example, the electronic device 110 and at least a portion of the one or more service departments 120 may refer to the following computer systems and computer software: connecting to a lower-level device to accept operation execution requests, executing the operations in response to the requests and providing execution results. The lower-level device can communicate with other network servers via a computer network such as an intranet or the Internet. In addition, the electronic device 110 and at least a portion of the one or more service departments 120 can also be understood as a broad concept: including a series of applications that can operate on the network server and various databases that can be built internally. For example, the electronic device 110 and at least a portion of the one or more service units 120 may be implemented using a network server program provided in various forms based on an operating system such as DOS, Windows, Linux, UNIX, or MacOS.

On the other hand, for ease of explanation, each action subject refers to the electronic device 110 and one or more service units 120. However, these action subjects should be understood as devices of the following comprehensive forms: corresponding to various types of devices such as computer devices and mobile communication terminals; or including various types of devices; or being included in various types of devices.

Electronic device 110 can provide various information, including notification information, and can perform various operations to this end. Specifically, electronic device 110 identifies one or more service departments 120, obtains one or more condition information associated with each of the one or more service departments 120, and stores the one or more condition information in storage 111. When a service-related event occurs, electronic device 110 determines whether to provide a service-related notification based on the one or more condition information stored in storage 111. In this regard, the one or more condition information may include, but is not limited to, information regarding the conditions for providing the notification.

The following describes more detailed matters related to the operation of the electronic device 110 based on Figures 2 to 5.

One or more service departments 120 may perform more than one function to provide a service. For example, to provide item delivery services, Service Department A may perform sorting management, Service Department B may perform the function of assigning responsible delivery personnel, and Service Department C may perform the function of monitoring delivery processing status. However, this is merely an example, and various embodiments are possible, such as the following: multiple functions may be performed in a single service department, and the functions performed by each service department may overlap (for example, Service Department A and Service Department B may both perform sorting management). This specific embodiment does not limit the scope of the present invention.

One or more service units 120 can exchange information with external devices such as electronic device 110 and perform actions associated therewith. For example, if a notification is received from electronic device 110, one or more service units 120 can limit at least a portion of the functions related to providing the service in response to the notification.

On the other hand, as described above, each of the one or more service units 120 refers to a unit that processes at least one function or action. Therefore, each of the one or more service units 120 does not necessarily need to be implemented by different devices; at least a portion of them can be implemented by different functions within a single device.

The actions associated with the series of information provision methods in various embodiments may be implemented by a single physical device or by an organic combination of multiple physical devices. For example, a portion of the components of the system for providing notification information may be implemented by any one physical device, while the remaining portion may be implemented by another physical device. For example, any one physical device may be implemented by a portion of electronic device 110, while the other physical devices may be implemented by a portion of one or more service units 120 or a portion of another external device.

Depending on the circumstances, the various components included in the system for providing notification information can also be implemented by being separately configured in different physical devices, with the distributed components being organically combined to perform the functions and operations of the system for providing notification information. For example, the electronic device 110 in this specification may include at least one sub-device, with descriptions stating that a portion of the operations performed by the electronic device 110 are performed by a first sub-unit, while another portion of the operations are performed by a second sub-unit.

Figure 2 is a flowchart illustrating a method for providing notification information in an electronic device according to one embodiment.

2 , an electronic device 110 according to one embodiment confirms one or more service departments 120 (210). According to one embodiment, the electronic device 110 may obtain register requests from one or more service departments 120 and confirm one or more service departments 120 based on the obtained requests. According to other embodiments, the electronic device 110 may obtain register information notifying one or more service departments 120 and confirm one or more service departments 120 based on the obtained information. There are various embodiments for the transmission subject of "register information notifying one or more service departments 120".

When confirming one or more service departments 120, it is not necessary to confirm each service department using the same method. For example, if one or more service departments 120 include service department A, service department B, and service department C, service department A can be confirmed by obtaining a register request from service department A, service department B can be confirmed by obtaining register information notifying service department B, and service department C can be confirmed by another method (e.g., loading service department directory information pre-stored in repository 111).

The electronic device 110 obtains one or more conditional information 220 associated with each of one or more service departments. The one or more conditional information may include information regarding conditions for providing notifications. According to one example, the one or more conditional information may include a condition for providing a notification when the number of events associated with a specific service department within a set time range exceeds a set threshold. In the present invention, a notification may include one or more of an alarm message and a pop-up message, but is not limited thereto.

By obtaining more than one conditional information, more than one service department can be associated with different conditional information, eliminating the need to apply the same conditional information uniformly to all service departments. Therefore, notification provision can be determined based on the specific characteristics of each service department, ensuring scalability and flexibility. Furthermore, specific service department characteristics that can be considered may include the size of the service department and the functions within the service department. For example, if the service department is relatively small, the conditions for providing notifications can be more stringent; if the functions within the service department are more important, the conditions for providing notifications can be more stringent.

In addition, various embodiments exist for determining whether to provide a notification based on a factor, such as the following: specific characteristics of a service department may include a history of providing notifications to the service department, or include current special circumstances related to the service department (for example, whether the server responsible for the service department has malfunctioned).

According to one embodiment, the information used as a basis for confirming one or more service departments may include one or more conditional information. For example, one or more of the aforementioned "register request" and the aforementioned "register notification information" may include one or more conditional information.

In addition, various embodiments are possible for obtaining one or more pieces of condition information. For example, the electronic device 110 may provide an interface for obtaining one or more pieces of condition information and receive the one or more pieces of condition information by receiving corresponding input. The interface may be provided to at least a portion of one or more service departments, or to at least a portion of one or more administrators who manage one or more service departments, but is not limited thereto.

On the other hand, in one embodiment, the electronic device 110 may provide an interface when a specific condition is met. The specific condition may include, for example, a condition such as "a register request is obtained." However, this is merely an example, and the scope of the present invention is not limited thereto.

Below, more details regarding the interface for obtaining one or more condition information are described with reference to FIG5.

The action of "obtaining one or more conditional information" in diagram 220 is not limited to the action of receiving information including one or more conditional information. For example, the electronic device 110 may generate (or determine) at least a portion of the one or more conditional information. As a specific example, the electronic device 110 may obtain one or more feature information associated with each of one or more service departments and, based on the obtained one or more feature information, determine the conditions for providing notifications to each of the one or more service departments. In this case, the one or more feature information in one embodiment may include one or more of the scale of the one or more service departments, the functions of the one or more service departments, and the history of providing notifications to the one or more service departments, but the scope of the present invention is not limited to this.

The electronic device 110 stores the obtained one or more condition information in the storage 111 (230). By storing the one or more condition information in the storage 111, when the electronic device 110 needs to use the condition information associated with each service department, it can use the stored condition information without receiving the condition information again from the external device.

When a service-related event occurs, the electronic device 110 determines whether to provide a service-related notification (240) based on one or more condition information stored in the storage 111. The "service" in the "service-related event" may include a service performed by one or more functions provided by one or more service units 120. The "event" in the "service-related event" can be understood as a broad concept including a series of events generated in connection with the service, however, a series of events does not necessarily include all events. By confirming whether to provide a notification when an event occurs, the real-time nature of providing notifications can be maintained and the efficiency of monitoring costs can be expected (in the case where no event occurs, monitoring can be minimized or disabled).

According to one embodiment, electronic device 110 can confirm one or more of event type information and information about the service associated with the event. Event types may include, but are not limited to, error types such as server failure, request failure, and response failure corresponding to a request. For example, event types (besides situations that can be clearly identified as errors) may include situations with a high probability of abnormal activity, such as when the number of customer requests within a period exceeds a certain threshold. In addition, various embodiments may exist, such as the following: the event type may include error code information corresponding to the event (e.g., error code 404, error code 503, etc.).

Information about services associated with an event may include information about the service departments associated with the event from one or more service departments 120, and may also include information about functions associated with the event from one or more functions managed by one or more service departments 120. For example, when an event occurs in which a request with a prefix of "service-hub" fails, the electronic device 110 may identify the function corresponding to the service-hub as the service associated with the event.

Depending on the embodiment, "services associated with an event" may include information about devices other than one or more service units 120, or may include information about functions associated with the event among functions associated with devices other than one or more service units 120. For example, "services associated with an event" may include information about an agent function or information about a device that implements the agent function.

The electronic device 110 can confirm whether at least a portion of one or more conditional information is satisfied based on one or more of the event type information and information about the service associated with the event. For example, for an event with error code 503, the electronic device 110 determines that one or more conditional information is not satisfied, and therefore, may determine not to provide a notification related to the service. As another example, the electronic device 110 may further confirm information about the service associated with the event in the event of error code 503; and in the event of an error caused by deployment in a specific service department, determine that the conditional information associated with the service department is satisfied, and therefore, may determine to provide a notification to the service department. In addition, various embodiments may exist, such as determining whether at least a portion of one or more conditional information is satisfied.

On the other hand, as mentioned above, it is not necessary to determine whether all or more conditional information is satisfied. There are many possible implementations where some conditional information is satisfied, but some is not. In this case, it can be understood that a notification is transmitted to the service department that satisfies the associated conditional information, but not to the service department that does not. In other words, the action in diagram number 240 can be understood as including the action of determining the recipient of the notification. More specifically, it can be understood as including the action of determining which candidate recipient, among multiple candidate recipients, to whom the notification is to be provided.

Furthermore, according to an embodiment, the aforementioned "plurality of candidate objects" may also include devices other than one or more service departments 120. That is, the action of diagram number 240 may further include the following action: determining whether to provide a notification to devices other than one or more service departments 120. For example, the action of diagram number 240 in one embodiment may include the following action: determining whether to provide a notification to a device that implements the proxy function.

On the other hand, in one embodiment, the electronic device 110 may be a separate device from the device implementing the proxy function (part of the above explanation is based on this premise, but it is explained again to avoid confusion). By separating the device implementing the proxy function from the electronic device 110, not only can the speed and accuracy of the "action of determining whether to provide a notification" performed by the electronic device 110 be ensured, but it can also more smoothly perform actions that require more resources (compared to the case of fully determining whether to provide a notification), such as determining whether to provide a notification to a specific candidate among multiple candidates.

As described above, the electronic device 110 is different from the device that implements the proxy function. Therefore, the previous description can be more clearly understood, that is, the object receiving the notification may include the device that implements the proxy function.

According to one embodiment, the action of determining whether to provide a service-related notification (diagram number 240) may also include determining what type of notification to provide. For example, the notifications that may be provided may include a first type of "error" notification and a second type of "warning" notification. A specific example is as follows: if a specific parameter related to the service exceeds a first threshold, an error notification is provided; if the parameter does not exceed the first threshold but exceeds a second threshold that is set to be lower than the first threshold, a warning notification is provided.

FIG3 is a diagram used to exemplarily illustrate a previous notification providing method according to an embodiment.

Referring to FIG. 3 , the provision of notifications in one embodiment is implemented in the agent function 310 . Specifically, the agent service group 320 associated with the agent function 310 can manually configure notifications ( 321 ) and transfer them to the notification rule repository 330 . The notification rule repository 330 can transfer the notification rules 331 to the metric analysis service 340 . The metric analysis service 340 can generate notifications 341 and provide notification services ( 341 ) when necessary.

However, the proxy function 310 must implement the function of transmitting the request stream 311 (the actual proxy function), making it difficult to devote significant resources to providing notifications or ensuring the scalability and flexibility of notifications. For example, if a domain registration request 301 received from a service department does not include conditional information related to the service department, the notification manually configured in the proxy service group 320 will apply to all service departments.

FIG4 is a diagram illustrating a notification providing method according to an embodiment of the present invention.

Referring to FIG. 4 , this can be implemented in a routing & notification repository 410 that is separate from the proxy function 420 in one embodiment of the present invention. The routing & notification repository 410 can be an example of the repository 111 described above.

The domain registration request 401 received by the routing & notification repository 410 from the service department may include notification rule information as a type of conditional information associated with the service department. The routing & notification repository 410 may store the conditional information associated with the service department, generate notifications (412) based on the conditional information when necessary, and provide the notifications to the notification system 430, which may trigger the notifications (431).

According to one embodiment, the routing & notification repository 410 may also provide routing rules 411 to the proxy function 420. In turn, the proxy function 420 may transmit metric events 421 to the matrix repository (according to one embodiment, the routing & notification repository 410 may also provide logging rules to the proxy function 420). Furthermore, according to one embodiment, the metric events generated by the matrix repository may also be provided to the notification system 430.

Compared to Figure 3 , the present invention's method provides notifications through the additional functionality of the routing & notification repository 410. This allows for greater utilization of resources for providing notifications and more easily ensures scalability and flexibility. For example, the routing & notification repository 410 receives notification rules from various service departments and can flexibly determine whether to provide notifications to various candidate recipients.

FIG5 is a diagram illustrating an interface for obtaining one or more condition information according to an embodiment.

Referring to Figure 5 , an electronic device 110 in one embodiment provides an interface for obtaining one or more conditional information and receives corresponding input, thereby receiving one or more conditional information. An exemplary interface may include one or more of a portion 510 for setting the notification service type and a portion 520 for setting notification conditions. The notification service type may refer to the type of service (not the type of notification) that determines whether to provide a notification. For example, the notification service type may be set to "retail." In this case, events generated in the retail section may be determined to determine whether one or more conditions are met.

The portion 520 for setting notification conditions may include a portion for setting one or more parameters and a portion for setting an associated comparator. In the example shown, the one or more parameters may include a threshold parameter related to the number of times and a parameter related to time.

According to an embodiment, section 520 for setting notification conditions may provide an interface for setting different conditions depending on the notification type. For example, according to the example shown, section 521 for setting "error" type notifications and section 522 for setting "warning" type notifications may be provided.

The diagram and description in Figure 5 should be understood as an example and are not intended to limit the scope of the present invention.

On the other hand, this specification and drawings disclose preferred embodiments of the present invention. Although specific terms are used, these terms are used in their ordinary sense to facilitate understanding of the present invention and are not intended to limit the scope of the present invention. Those skilled in the art will appreciate that, in addition to the embodiments disclosed herein, other variations based on the technical concepts of the present invention are possible.

The recommended server, electronic device, or terminal of the above embodiments may include a processor, memory for storing and executing program data, permanent storage such as a disk drive, communication ports for communicating with external devices, and user interface devices such as a touch panel, keys, or buttons. Methods implemented by software modules or algorithms may be stored on a computer-readable recording medium as computer-readable code or program commands that can be executed on the processor. Here, computer-readable recording media include magnetic storage media (e.g., ROM (Read-only memory), RAM (Random-access memory), floppy disks, hard disks, etc.) and optical readable media (e.g., Compact Disc Read-Only Memory (CD-ROM) and Digital Versatile Disc (DVD)). Computer-readable recording media are distributed across computer systems connected to a network, enabling the storage and execution of computer-readable code in a distributed manner. The media can be read by the computer, stored in memory, and executed by the processor.

The present embodiment may be represented by a functional block structure and various processing steps. These functional blocks may be implemented by different numbers of hardware and/or software components that perform specific functions. For example, the embodiment may be implemented using an integrated circuit structure that can perform various functions, such as memory, processing, logic, look-up tables, etc., under the control of one or more microprocessors or other control devices. The components may be implemented by software programming or software components. Similarly, the present embodiment includes algorithms implemented by a combination of data structures, procedures, routines, or other programming structures, and thus may be implemented by programming or scripting languages such as C, C++, Java, assemblers, Python, etc. Functionally, this can be achieved through algorithms executed on one or more processors. Furthermore, this embodiment can utilize existing technologies for electronic environment configuration, signal processing, and/or data processing. Terms such as "mechanism," "element," "mechanism," and "configuration" are used broadly and are not limited to mechanical or physical configurations. These terms can be associated with processors and other devices and include software routines.

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

210:Action220:Action230:Action240:Action

Claims (11)

A method for providing information in an electronic device including a storage repository configured to store data, comprising the steps of: identifying one or more service departments; obtaining one or more conditional information associated with each of the one or more service departments; storing the one or more conditional information in the storage repository; and determining whether to provide information related to the one or more service departments based on the one or more conditional information stored in the storage repository when an event related to the service occurs. Service-related notifications, wherein the step of obtaining the above-mentioned one or more conditional information includes the following steps: obtaining one or more characteristic information associated with each of the above-mentioned one or more service departments; and based on the above-mentioned one or more characteristic information, determining the conditions for providing the above-mentioned notification for each of the above-mentioned one or more service departments, wherein the above-mentioned one or more characteristic information includes: the scale of the above-mentioned one or more service departments; and the history of providing the above-mentioned notification to the above-mentioned one or more service departments. A method for providing information as claimed in claim 1, wherein the step of determining whether to provide the above-mentioned notification includes the following steps: confirming one or more of the type information of the above-mentioned event and the information of the service associated with the above-mentioned event; and based on the type information of the above-mentioned event and the information of the service associated with the above-mentioned event, confirming whether at least a portion of the above-mentioned one or more conditional information is satisfied. The method for providing information as claimed in claim 2, wherein the type information of the event includes error code information corresponding to the event. The method for providing information as claimed in claim 1, wherein the electronic device is a device different from a proxy server used to provide the service. The method for providing information as claimed in claim 4, wherein the step of determining whether to provide a notification related to the above-mentioned service includes the step of determining an object to receive the above-mentioned notification, and the above-mentioned object includes the above-mentioned proxy server and at least a part of the above-mentioned one or more service departments. The method for providing information as claimed in claim 1, wherein the step of confirming the one or more service departments comprises one or more of the following steps: obtaining a register request from the one or more service departments; and obtaining register information notifying the one or more service departments. The method for providing information as claimed in claim 6, wherein one or more of the register request and the information notified to the register includes the one or more conditional information. The method for providing information as claimed in claim 1, wherein the one or more conditional information includes the following condition: providing the above notification when the number of events related to a specific service department occurring within a set time range exceeds a set threshold. The method for providing information as recited in claim 1, wherein the one or more characteristic information further includes the functions of the one or more service departments. A non-transitory computer-readable recording medium records a program for executing the method of claim 1 on a computer. An electronic device that provides information includes a transceiver, a storage configured to store data, and a processor, wherein the processor is configured to: connect to the transceiver and the storage to identify one or more service departments; obtain one or more condition information associated with each of the one or more service departments; store the one or more condition information in the storage; and when an event related to a service occurs, determine whether the event is a service related event based on the one or more condition information stored in the storage. Whether to provide notifications related to the above-mentioned services, wherein the above-mentioned processor is configured to obtain the above-mentioned one or more conditional information through the following steps: obtaining one or more characteristic information associated with each of the above-mentioned one or more service departments; and based on the above-mentioned one or more characteristic information, determining the conditions for providing the above-mentioned notifications for each of the above-mentioned one or more service departments, wherein the above-mentioned one or more characteristic information includes: the scale of the above-mentioned one or more service departments; and the history of providing the above-mentioned notifications to the above-mentioned one or more service departments.