Notification response method and apparatus, electronic device, and computer-readable storage medium

Abstract

The present disclosure provides a notification response method and device, electronic equipment and computer readable storage medium, relating to the technical field of computer. The notification response method comprises: receiving a notification service request; determining a target plug-in based on the notification service request; and executing a notification task corresponding to the notification service request through the target plug-in. The present disclosure determines a target plug-in based on a notification service request, and executes a corresponding notification task based on the target plug-in. The notification service is separated from the business system through the target plug-in. Developers only need to focus on how to implement the notification task through the plug-in, without needing to focus on additional logic, thereby improving the convenience and universality of notification service development and invocation.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of computer, and in particular, to a notification response method and device, electronic equipment and computer readable storage medium. BACKGROUND

[0002] Various existing business systems have the function of sending notifications to users. For example, in the field of intelligent operation and maintenance, when a system anomaly is detected, the function of sending an alarm notification to the user is provided; or the function of sending information notifications such as telephone, short message, email, instant messaging software, etc. to the user is provided by the business system.

[0003] In related technologies, the above notification function is usually realized by writing the logic code of the notification into the business code, or by calling a script. However, the above method is highly invasive and the technical languages implemented by the business code are inconsistent, which can cause high development and implementation costs, complex function debugging, the need to restart the business system after implementation, and other problems. SUMMARY

[0004] Therefore, the present application provides a notification response method and device, electronic equipment and computer readable storage medium to solve the problems of high development and implementation costs, complex function debugging, and the need to restart the business system after implementation caused by the inconsistency of the technical languages implemented by the business code in related technologies.

[0005] According to a first aspect of the present application, a notification response method is provided, comprising: receiving a notification business request; determining a target plug-in based on the notification business request; and executing a notification task corresponding to the notification business request through the target plug-in.

[0006] According to a second aspect of the present application, a notification response device is provided, comprising: a service calling module configured to receive a notification business request; a plug-in determining module configured to determine a target plug-in based on the notification business request; and a message notification module configured to execute a notification task corresponding to the notification business request through the target plug-in.

[0007] According to a third aspect of the present application, an electronic device is provided, comprising: a processor; and a memory storing a program, wherein the program includes instructions that, when executed by the processor, cause the processor to perform the above notification response method.

[0008] According to a fourth aspect of the present application, a non-transitory computer readable storage medium storing computer instructions is provided, wherein the computer instructions are used to cause the computer to perform the above notification response method.

[0009] The exemplary embodiments of the present application can have the following partial or all beneficial effects:

[0010] In the notification response method provided by the example embodiments of the present disclosure, a notification service request is received; a target plug-in is determined based on the notification service request; and a notification task corresponding to the notification service request is executed through the target plug-in. The notification response method of the embodiments of the present disclosure determines a target plug-in based on a notification service request, and executes a corresponding notification task based on the target plug-in. The notification service is separated from the business system through the target plug-in. The developer only needs to focus on how to implement the notification task through the plug-in, without needing to focus on additional logic, thereby improving the convenience and universality of notification service development and invocation.

[0011] It should be understood that the foregoing general description and the following detailed description are only exemplary and explanatory, and are not limiting to the present disclosure. BRIEF DESCRIPTION OF DRAWINGS

[0012] In the following description of the example embodiments in conjunction with the accompanying drawings, more details, features and advantages of the present disclosure are disclosed, in which:

[0013] Figure 1 A flowchart of a notification response method according to an example embodiment of the present disclosure is shown;

[0014] Figure 2 A class diagram of notification plug-in development of a notification response method according to an example embodiment of the present disclosure is shown;

[0015] Figure 3 A class diagram of callback plug-in development of a notification response method according to an example embodiment of the present disclosure is shown;

[0016] Figure 4 A system architecture diagram of a notification service system of a notification response method according to an example embodiment of the present disclosure is shown;

[0017] Figure 5 A notification flow diagram of a notification response method according to an example embodiment of the present disclosure is shown;

[0018] Figure 6 A callback flow diagram of a notification response method according to an example embodiment of the present disclosure is shown;

[0019] Figure 7 A schematic block diagram of a notification response apparatus according to an example embodiment of the present disclosure is shown;

[0020] Figure 8 A structural block diagram of an example electronic device that can be used to implement the embodiments of the present disclosure is shown. DETAILED DESCRIPTION

[0021] Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While certain embodiments of the present disclosure are shown in the drawings, it is understood that the present disclosure can be embodied in various forms and should not be interpreted in a limited sense as set forth in the embodiments set forth herein, but rather, these embodiments are provided to more thoroughly and completely understand the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are only for illustrative purposes and are not intended to limit the scope of protection of the present disclosure.

[0022] It should be understood that each of the steps described in the method embodiments of the present disclosure can be performed in different orders and / or in parallel. In addition, the method embodiments can include additional steps and / or omit the steps shown. The scope of the present disclosure is not limited in this respect.

[0023] The term "comprising" and variations thereof as used herein are open-ended, that is "including but not limited to". The term "based on" is "based, at least in part, on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". Related terms are defined as follows. It should be noted that the concepts mentioned in the present disclosure are only used to distinguish different devices, modules or units, and are not intended to limit the functions performed by these devices, modules or units in order or interdependence.

[0024] It should be noted that the modification of "one" or "multiple" mentioned in the present disclosure is illustrative and not limiting, and those skilled in the art should understand that unless otherwise explicitly indicated in the context, it should be understood as "one or more".

[0025] The names of the messages or information exchanged between the devices in the embodiments of the present disclosure are only for illustrative purposes and are not intended to limit the scope of the messages or information.

[0026] The embodiments of the present disclosure provide a notification response method, device, electronic equipment and computer readable storage medium. The scheme of the present disclosure is described below with reference to the accompanying drawings.

[0027] The embodiments of the present disclosure first provide a notification response method. Referring to Figure 1 The notification response method specifically includes the following steps:

[0028] S110: receiving a notification service request;

[0029] S120: determining a target plug-in based on the notification service request;

[0030] S130: executing a notification task corresponding to the notification service request through the target plug-in.

[0031] In the notification response method provided in the embodiments of the present disclosure, the target plug-in is determined based on the notification service request, and the corresponding notification task is executed based on the target plug-in, the notification service is separated from the business system through the target plug-in, the developer only needs to focus on how to implement the notification task through the plug-in, and does not need to focus on additional logic, thereby improving the convenience and universality of the notification service development and calling.

[0032] In another embodiment, the above steps are described in more detail as follows.

[0033] In step S110, a notification service request is received.

[0034] The notification response method provided in the embodiments of the present disclosure separates the notification service from the business system as an independently existing system, the notification service system provides a unified business calling interface to the outside, and the business system can obtain each notification service in the notification service system by calling the business calling interface, thereby realizing more efficient, lower cost, lower invasiveness, and rapid satisfaction of user function scenarios and other needs without integrating the notification functions developed for different users into the business system and restarting and debugging the system.

[0035] In the embodiments of the present disclosure, the notification service request is a request initiated by a request initiator to the notification service system, and is used to execute a corresponding notification service.

[0036] In the embodiments of the present disclosure, the notification service request can be a notification sending request, for example, the notification sending request can be a request of the business system to send a notification to a user; the notification service request can also be a notification callback request, for example, the notification callback request can be a callback request initiated by a third-party system to a callback address provided by the notification service system after the business system sends a notification to the third-party system; the notification service request can also be a notification query request, for example, the user can send the notification query request to the notification service system to query a notification log in a database of the notification service system.

[0037] In the embodiments of the present disclosure, for example, the request initiator initiates a request to execute a corresponding notification service to the notification service system by calling a business calling interface of the notification service system, and the notification service system can execute a corresponding notification service based on subsequent step S120 and step S130 after receiving the notification service request.

[0038] In step S120, a target plug-in is determined based on the notification service request.

[0039] In the embodiments of the present disclosure, the target plug-in is used to execute the notification service corresponding to the notification service request.

[0040] In the embodiments of the present application, the target plug-in can be a plug-in for implementing a notification service or a plug-in for implementing a notification callback service.

[0041] In the embodiments of the present application, when the target plug-in is a plug-in for implementing a notification service, the development process of the target plug-in can be implemented as follows: a first general component dependency package corresponding to the notification service is acquired; a target method in the first general component dependency package is inherited to obtain a notification plug-in.

[0042] Specifically, the development process of the target plug-in for implementing a notification service can be implemented as follows:

[0043] As shown in Figure 2 The notification response method provided in the embodiments of the present application defines a notification media service (NotificationMediaService) and two default implemented abstract classes: an abstract notification service (AbstractNotificationService) and a hypertext transfer protocol (HTTP) based subclass implementation (AbstractHttpNotificationService) of the abstract notification service. The NotificationMediaService is a top-level interface. The corresponding application scenarios gradually become specific from the NotificationMediaService to the AbstractHttpNotificationService. For example, in the http implementation scenario, when developing a target plug-in, the AbstractHttpNotificationService can be inherited; if the http implementation scenario is not met, the AbstractNotificationService can be directly inherited. The AbstractNotificationService is at a higher level than the AbstractHttpNotificationService. That is, the AbstractHttpNotificationService is a subclass defined for the specific scenario of http, and the AbstractNotificationService is applicable to a wider range of scenarios.

[0044] Specifically, the above development process can be implemented as follows: the embodiment of the present application provides a general service component notification-core-xyz.jar dependency package, when developing a plug-in, only needs to download the dependency package, rewrite the setConfig, createRequest, sendNotification, doExecuted method.

[0045] In the embodiment of the present application, when the notification service request is a notification sending request, the notification service request includes a requested notification type, which can be a short message notification, a voice notification or an email notification, etc.

[0046] In the embodiment of the present application, when the notification service request is a notification sending request, the above determining the target plug-in based on the notification service request can be implemented as follows: analyzing the notification sending request; determining the notification service type requested by the notification sending request based on the analysis result; determining the target plug-in from the pre-designed notification plug-in based on the notification service type. That is, different notification types need to load different target plug-ins, and different plug-in types can be loaded and used at the same time to implement the function of sending notifications.

[0047] In the embodiment of the present application, when the target plug-in is a plug-in for implementing a notification callback service, the development process of the target plug-in can be implemented as follows: obtaining a second general component dependency package corresponding to the notification callback service; inheriting the target method in the second general component dependency package to obtain a notification callback plug-in.

[0048] Specifically, taking the IT service management (IT Service Management, ITSM) scenario as an example, the development process of the above target plug-in for implementing a notification callback service is described in detail:

[0049] For example, Figure 3As shown, since in actual scenarios, the notification callback mode of ITSM is mostly asynchronous callback, the notification response method provided in the embodiments of the present application defines a callback service interface (CallbackService), an interface based on an ITSM work order plug-in (ItsmCallbackService), and an abstract class: an ITSM-based callback service (AbstractItsmCallbackService). The CallbackService is a top-level interface. In the ITSM scenario, when developing a target plug-in, only AbstractItsmCallbackService needs to be inherited. Specifically, the embodiments of the present application provide a general service component notification-core-xyz.jar dependency package. When developing a plug-in, only this dependency package needs to be downloaded, and the methods in the dependency package can be inherited.

[0050] In the embodiments of the present application, when the notification service request is a notification callback request, the notification service request includes a requested callback service type. Exemplarily, the callback service type can be an ITSM type.

[0051] In the embodiments of the present application, when the notification service request is a notification callback request, the determination of the target plug-in based on the notification service request can be implemented as follows: parsing the notification sending request; parsing the notification callback request; determining the callback service type requested by the notification callback request based on the parsing result; and determining the target plug-in from the pre-designed callback plug-in based on the callback service type.

[0052] In step S130, the target plug-in is used to execute the notification task corresponding to the notification service request.

[0053] In the embodiment of the present application, after the target plug-in is determined through steps S110 and S120, the target plug-in can be loaded to execute the notification task corresponding to the notification service request through the target plug-in. Specifically, the plug-in loading process can be implemented as follows: the development process of the target plug-in is implemented based on a micro-service framework (springboot), and therefore a command line -Dloader.path=lib,plugins can be added in the jvm start parameter, which indicates that when the plug-in starts, the position of the loaded jar package is the lib directory and the plugins directory of the current directory. The lib directory is used to store the basic jar package dependency, and the plugins / *.jar is used to store the notification plug-in (i.e., the target plug-in) to be developed. The plug-in package parameters of the target plug-in are configured, which can include the type of the plug-in, the complete class name of the plug-in, and other configuration parameters such as the required retransmission frequency and the retransmission number of the plug-in, and the plug-in dependency package is registered as a spring bean. The retransmission frequency refers to the time interval of re-sending the notification when the notification sending fails, and the retransmission number refers to the number of re-sending the notification when the notification sending fails. When the number of sending the notification reaches the retransmission number, the notification is no longer sent to the user even if the notification is not successfully sent. The embodiment of the present application unifies the notification frequency, the retry number, and the retry interval limit by configuring the parameters of the target plug-in.

[0054] In the embodiment of the present application, when the notification service request is a notification sending request, the target plug-in is called to send the notification message corresponding to the notification sending request, and the notification message is re-sent based on the parameter setting of the target plug-in if the notification message sending fails.

[0055] Specifically, the target plug-in used to implement the notification sending can be loaded, and the service notification is sent to the user by calling the target plug-in. For example, when the notification service type to be sent is determined to be the short message type based on the notification sending request, the short message notification can be sent to the user by calling the corresponding target plug-in. Further, if it is detected that the notification sending is successful, the process is ended; if it is detected that the notification sending fails, the notification message is re-sent to the user based on the parameter setting of the target plug-in. For example, when the parameter setting of the target plug-in includes a retransmission interval of 5 minutes and a retransmission number of 3 times, the process can be implemented as follows: it is determined whether the time interval from the last time of sending the notification message reaches 5 minutes, if yes, it is further determined whether the current retransmission number reaches three times, if not, the message notification is sent to the user again, and it is determined whether the sending is successful, if yes, the process is ended; if not, the retransmission process is repeated until the sending is successful or the retransmission number reaches three times.

[0056] In the embodiments of the present application, when the notification service request is a notification callback request, the notification task corresponding to the notification service request is executed by the target plug-in, and the callback content corresponding to the notification callback request is obtained by calling the target plug-in, and the callback content is stored in the database.

[0057] Specifically, the target plug-in for implementing the notification callback can be loaded, and the callback party obtains the callback notification by calling the target plug-in. For example, when it is determined based on the notification callback request that the notification service type to be called back is an ITSM type, the notification callback can be implemented by calling the target plug-in corresponding to the callback service type. Further, the notification service system can return the callback content to the callback party after obtaining the callback notification, and store the callback content in the database for subsequent query.

[0058] In the embodiments of the present application, the notification service request can also be a notification query request. For example, the user can obtain the notification log by sending the notification query request to the notification service system.

[0059] The notification response method of the embodiments of the present application determines the target plug-in based on the notification service request, and executes the corresponding notification task based on the target plug-in. The notification service is separated from the business system through the target plug-in, and the developer only needs to focus on how to implement the notification task through the plug-in, without needing to focus on additional logic, thereby improving the convenience and universality of the notification service development and calling.

[0060] In the following, in a specific embodiment, the notification response method is described in detail in combination with Figure 4 to Figure 6 The notification response method is described in detail as follows:

[0061] Figure 4 The architecture diagram for implementing the notification response method based on the notification service system is shown in FIG. 1. As shown in FIG. 1, the notification service system includes a service layer, a business layer and a query storage engine layer. Specifically: Figure 4 The service layer is used for processing the notification request, the notification callback request and the request for querying the notification log, and distributing them to the corresponding business layer. That is, the notification service system provides an interface for calling the plug-in through the service layer, and the user can send the notification request, the notification callback request or the request for querying the notification log to the notification service system through the calling interface. The service layer distributes the received request to the corresponding business layer.

[0062] The business layer is used for implementing the notification business and the callback business.

[0063]

[0064] ​The notification service is implemented as follows: receiving a notification request, analyzing notification content, and calling a corresponding notification plug-in based on the analysis result to implement notification calling through the notification plug-in. For example, a service of a three-party system shown in FIG. 7 can be called, or a local three-party package can be called to perform a sending task. The calling can be synchronous calling or asynchronous calling. Figure 4

[0065] The callback service is implemented as follows: in an asynchronous calling scenario (for example, voice notification and ITSM notification), a system callback address needs to be provided to a third-party system. When a callback request is initiated by the notification service, if the scenario is asynchronous calling, the system callback address is called, the notification callback request is analyzed by the service layer, a corresponding callback plug-in is called based on the analysis result to implement notification calling, and the callback result is stored in a database.

[0066] The query storage engine layer includes a query engine and a storage engine. The query engine is configured to provide a query notification log function, and the storage engine is configured to store notification-related content, notification results, and related process parameters in a database. The database can be a distributed database or a relational database. After the service layer completes the notification service or the notification callback service, the service layer can generate a notification log based on data generated during the execution and store the notification log in the database, so that a user can query the notification log in the database through the query engine.

[0067] In the embodiments of the present application, the notification plug-in and the callback plug-in correspond to the target plug-in described above. The development and loading process of the plug-in have been described in detail above, and thus will not be described here.

[0068] In the embodiments of the present application, the process of implementing notification sending is shown in FIG. 7 and includes the following steps. Figure 5

[0069] S510: receiving a notification request.

[0070] In the embodiments of the present application, a calling party calls a notification service through a calling interface of a service layer to initiate a notification request. After receiving the notification request, the service layer distributes the notification request to a service layer.

[0071] S520: analyzing the notification request.

[0072] In the embodiments of the present application, the service layer analyzes the notification request and identifies a requested notification service type based on the analysis result. For example, it is determined that the requested service type is short message notification, email notification, or other notification.

[0073] S530: calling a corresponding notification plug-in based on the requested notification service type. ​​

[0074] S540: executing the notification by the notification plug-in.

[0075] S550: judging whether the notification is successful.

[0076] In the embodiment of the present application, it is judged whether the notification is successful. If the notification is successful, the notification is stored in the database and the process is ended; if the notification is not successful, step S560 is executed.

[0077] S560: judging whether the number of retransmissions exceeds a set value.

[0078] In the embodiment of the present application, when the notification fails, it is judged whether the current number of retransmissions exceeds the set value in the notification plug-in parameter setting. If the set value is not exceeded, step S570 is continuously executed. If the set value is exceeded, the process is ended.

[0079] S570: retransmitting the notification.

[0080] S580: judging whether the retransmission is successful.

[0081] In the embodiment of the present application, it is judged whether the retransmission is successful. If the retransmission is successful, the notification is stored in the database and the process is ended. If the retransmission fails, step S560 is returned.

[0082] S590: ending the process.

[0083] In the embodiment of the present application, the process of implementing the notification callback as described above, as shown in FIG. 6, specifically includes the following steps: Figure 6

[0084] S610: receiving a notification callback request.

[0085] In the embodiment of the present application, the callback party calls the notification service through the calling interface of the service layer to initiate the notification callback request. After receiving the notification callback request, the service layer distributes the notification callback request to the business layer.

[0086] S620: analyzing the notification callback request.

[0087] In the embodiment of the present application, the business layer analyzes the notification callback request and identifies the callback service type based on the analysis result. For example, it is identified whether the callback notification is of the ITSM type or other types.

[0088] S630: calling the corresponding callback plug-in based on the callback service type.

[0089] S640: executing the callback by the callback plug-in.

[0090] In the embodiment of the present application, after the callback is executed, the callback content is stored in the database.

[0091] ​In the notification response method provided in this application embodiment, developers only need to focus on how various notification plugins or callback plugins are implemented, without needing to focus on the development language of the caller. It has the following advantages: (1) It provides a unified interface to provide services to the outside world, and business callers can easily call the notification service; (2) Developers only need to focus on how to implement the notification service function through plugins, without needing to focus on other logic; (3) Debugging is convenient after the plugin is developed; (4) It unifies the notification frequency, number of retries and retry interval limits; (5) It summarizes and statistically analyzes the notification history through the query storage engine layer and provides query function; (6) It supports synchronous and asynchronous calls.

[0092] The foregoing primarily describes the solutions provided by the embodiments of the present invention from a methodological perspective. To achieve the aforementioned functions, it includes corresponding hardware structures and / or software modules for executing each function. Those skilled in the art should readily recognize that, in conjunction with the units and algorithm steps of the various examples described in the embodiments disclosed herein, the present invention can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the present invention.

[0093] In this embodiment of the invention, the notification response device can be divided into functional modules according to the above method example. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into one processing module. The integrated modules can be implemented in hardware or as software functional modules. It should be noted that the module division in this embodiment is illustrative and only represents one logical functional division; other division methods may be used in actual implementation.

[0094] This disclosure provides a notification response device. (See also...) Figure 7 As shown, the notification response device 700 may include a service invocation module 710, a plug-in determination module 720, and a message notification module 730, wherein:

[0095] Service call module 710 is used to receive notification service requests;

[0096] The plugin determination module 720 is used to determine the target plugin based on the notification business request.

[0097] The message notification module 730 is used to execute the notification task corresponding to the notification business request through the target plugin.

[0098] In this embodiment of the application, the notification service request includes a notification sending request, and the plugin determination module is specifically used to: parse the notification sending request; determine the notification service type requested by the notification sending request based on the parsing result; and determine the target plugin from the pre-designed notification plugins based on the notification service type.

[0099] In this embodiment of the application, the notification service request includes a notification callback request, and the plugin determination module is specifically used to: parse the notification callback request; determine the callback service type requested by the notification callback request based on the parsing result; and determine the target plugin from the pre-designed callback plugins based on the callback service type.

[0100] In this embodiment, the message notification module is specifically used to: send a notification message corresponding to the notification sending request by calling the target plugin; if the notification message fails to be sent, resend the notification message based on the parameter settings of the target plugin. In this embodiment, the message notification module is specifically used to: obtain the callback content corresponding to the notification callback request by calling the target plugin, and store the callback content in the database.

[0101] In this embodiment of the application, the message notification module is specifically used to: query the notification log based on the notification query request.

[0102] In this embodiment, the notification response device further includes a plugin development module, which is specifically used to develop a notification plugin. Specifically, the development process can be implemented as follows: obtaining a general component dependency package; inheriting the target methods in the general component dependency package to obtain the notification plugin.

[0103] Furthermore, the specific implementation details of the aforementioned notification response device have been described in detail in the corresponding section of the notification response method, and therefore will not be repeated here.

[0104] Figure 8 This is a schematic diagram of the structure of an electronic device according to an embodiment of this disclosure. See below for details. Figure 8 It shows a schematic diagram of a structure suitable for implementing the electronic device 800 in the embodiments of this disclosure. Figure 8 The electronic device shown is merely an example and should not be construed as limiting the functionality and scope of the embodiments disclosed herein.

[0105] like Figure 8As shown, the electronic device 800 can include a processing device (e.g., a central processor, a graphics processor, etc.) 801 that can perform various appropriate actions and processes to implement the notification response method of embodiments as described in the present disclosure according to programs stored in a read-only memory (ROM) 802 or loaded into a random access memory (RAM) 803 from a storage device 808. Various programs and data required by the electronic device 800 to operate are also stored in the RAM 803. The processing device 801, the ROM 802, and the RAM 803 are connected to each other through a bus 804. An input / output (I / O) interface 805 is also connected to the bus 804.

[0106] Generally, the following devices can be connected to the I / O interface 805: input devices 806 including, for example, a touch screen, a touch pad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; output devices 807 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; storage devices 808 including, for example, a magnetic tape, a hard disk, etc.; and communication devices 809. The communication devices 809 can allow the electronic device 800 to communicate wirelessly or wired with other devices to exchange data. Although Figure 8 The electronic device 800 is shown with various devices, but it should be understood that not all of the shown devices are required to be implemented or present. More or fewer devices can alternatively be implemented or present.

[0107] In particular, the processes described above with reference to the flowcharts can be implemented as a computer software program according to embodiments of the present disclosure. For example, embodiments of the present disclosure include a computer program product comprising a computer program carried on a non-transitory computer-readable medium, the computer program containing program code for performing the methods illustrated by the flowcharts, thereby implementing the notification response method as described above. In such embodiments, the computer program can be downloaded and installed from a network through the communication devices 809, or installed from the storage devices 808, or installed from the ROM 802. When the computer program is executed by the processing device 801, the above-described functions defined in the methods of embodiments of the present disclosure are performed.

[0108] It should be noted that the computer-readable medium in the present disclosure can be a computer-readable signal medium or a computer-readable storage medium or any combination of the two. The computer-readable storage medium may, for example, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or apparatus, or any combination thereof. More specific examples of the computer-readable storage medium can include, but are not limited to, an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present disclosure, the computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, device or apparatus. In the present disclosure, the computer-readable signal medium can include a data signal carried in a baseband or as a part of a carrier wave, which carries computer-readable program code. Such a propagated data signal can take various forms, including but not limited to an electromagnetic signal, an optical signal, or any suitable combination thereof. The computer-readable signal medium can also be any computer-readable medium other than the computer-readable storage medium, which can send, propagate or transmit a program for use by or in conjunction with an instruction execution system, device or apparatus. The program code contained in the computer-readable medium can be transmitted by any suitable medium, including but not limited to a wire, a cable, a RF (radio frequency), or the like, or any suitable combination thereof.

[0109] In some embodiments, the client, server, or both can communicate using any current known or future developed network protocol, such as HTTP (Hyper Text Transfer Protocol), and can be interconnected with any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include local area networks ("LAN"), wide area networks ("WAN"), the Internet, and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any current known or future developed networks.

[0110] The computer-readable medium described above can be included in the electronic device described above; or can exist separately from the electronic device and not be assembled into the electronic device.

[0111] The computer-readable medium described above carries one or more programs, when the one or more programs are executed by the electronic device, the electronic device:

[0112] Receive a notification service request;

[0113] determine the target plug-in based on the notification service request;

[0114] execute the notification task corresponding to the notification service request by the target plug-in.

[0115] Optionally, when the one or more programs are executed by the electronic device, the electronic device can further execute other steps described in the above embodiments.

[0116] Computer program code for carrying out operations of the present disclosure can be written in one or more programming languages or combinations of languages including object oriented programming languages such as Java, Smalltalk, C++ as well as conventional procedural programming languages such as the "C" programming language or similar programming languages. The program code can execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection can be made to an external computer (for example, through the Internet using an Internet Service Provider).

[0117] The flow diagrams and the block diagrams in the drawings are illustrations of architectures, functionalities, and operations of possible implementations of systems, methods, and computer program products according to various embodiments of present disclosure. In this regard, each block in the flow diagrams or block diagrams can represent a module, a procedure, or a part of code, which comprises one or more executable instructions for implementing the specified logical functions. It should also be noted that in some alternative implementations, the functions noted in the blocks can occur in a different order than that noted in the figures. For example, two blocks noted in succession can in fact be executed substantially concurrently or in the opposite order, depending on the functionality involved. It should also be noted that each block in the block diagrams and / or flow diagrams, and combinations of blocks in the block diagrams and / or flow diagrams, can be implemented by dedicated hardware-based systems that perform the specified functions or operations, or can be implemented by a combination of dedicated hardware-based systems and computer instructions.

[0118] The units described in the embodiments of the present disclosure can be implemented by software, or by hardware. In some cases, the name of the unit does not constitute a limitation on the unit itself.

[0119] The functionality described above can be performed, at least in part, by one or more hardware logic components. For example, and without limitation, an example type of hardware logic components that can be used include Field-programmable Gate Arrays (FPGAs), Application-specific Integrated Circuits (ASICs), Application-specific Standard Products (ASSPs), System-on-a-chip (SOCs), Complex Programmable Logic Devices (CPLDs), etc.

[0120] In the context of the present disclosure, a machine-readable medium can be a tangible medium that contains or stores a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of the machine-readable storage medium will include one or more lines of electrical connections, portable computer disks, hard disk drives, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or Flash memory), optical fibers, portable compact disc read-only memories (CD-ROMs), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0121] The foregoing description merely exemplifies the preferred embodiments of the disclosure and the principles of the technology applied. It is understood by those skilled in the art that the disclosed scope of the present disclosure is not limited to the technical solutions formed by the specific combinations of the above technical features, and also covers other technical solutions formed by any combinations of the above technical features or equivalent features without departing from the above disclosed concept. For example, the technical solutions formed by the mutual replacement of the above features and the technical features disclosed in the present disclosure (but not limited to) having similar functions.

[0122] Further, while operations are depicted in a particular order, this should not be understood as requiring the operations to be performed in the particular order shown or in sequential order, and that certain operations can be performed in parallel or in any suitably ordered order under certain circumstances. Also, while several specific implementation details are included herein, they should not be construed as limitations on the scope of the disclosure, as such specific implementation details can not be included in other implementations. Certain features that are described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable sub-combination.

[0123] Although the subject matter has been described in language specific to structural features and / or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims

1. A notification response method characterized by, The method comprises the following steps: receiving a notification service request based on a calling interface, wherein the notification service request comprises a notification callback request, and the notification callback request comprises a callback service type, and the callback service type comprises an ITSM type; the calling interface is a unified business calling entrance provided by a notification service system to the outside; the notification callback request is a callback request initiated by a third-party system based on a callback address provided by the notification service system to the business system after the business system sends a notification to the third-party system; determining a target plug-in based on the notification service request, which comprises the following steps: analyzing the notification callback request, determining the callback service type requested by the notification callback request based on the analysis result, and determining the target plug-in from the pre-designed callback plug-in based on the callback service type; the notification callback mode corresponding to the ITSM type comprises asynchronous callback; executing a notification task corresponding to the notification service request through the target plug-in, which comprises the following steps:

2. The notification response method of claim 1, wherein, obtaining callback content corresponding to the notification callback request through the target plug-in, and analyzing and storing the callback content into a database. The callback plug-in comprises a callback service interface, an ITSM single plug-in interface and an abstract class, and the callback plug-in is developed by inheriting AbstractItsmCallbackService. The notification service request comprises a notification sending request; the method of determining the target plug-in based on the notification service request comprises the following steps: analyzing the notification sending request; 3. The notification response method of claim 2, wherein, determining the notification service type requested by the notification sending request based on the analysis result; determining the target plug-in from the pre-designed notification plug-in based on the notification service type. The method of executing the notification task corresponding to the notification service request through the target plug-in comprises the following steps:

4. The notification response method of claim 2, wherein, sending a notification message corresponding to the notification sending request by calling the target plug-in; if the notification message fails to be sent, resending the notification message based on the parameter setting of the target plug-in. The method further comprises the following steps: developing the notification plug-in; The method of developing the notification plug-in comprises the following steps:

5. The notification response method of claim 1, wherein, obtaining a general component dependency package; inheriting a target method in the general component dependency package to obtain the notification plug-in.

6. A notification response apparatus characterized by comprising: The notification service request comprises a notification query request; the method further comprises the following steps: querying a notification log based on the notification query request. The method comprises the following steps: a service calling module is configured to receive a notification service request based on a calling interface, wherein the notification service request comprises a notification callback request, and the notification callback request comprises a callback service type, and the callback service type comprises an ITSM type; the calling interface is a unified business calling entrance provided by a notification service system to the outside; the notification callback request is a callback request initiated by a third-party system based on a callback address provided by the notification service system to the business system after the business system sends a notification to the third-party system. The plug-in determining module is configured to determine a target plug-in based on the notification service request, including: parsing the notification callback request, determining a callback service type requested by the notification callback request based on a parsing result, and determining the target plug-in from pre-designed callback plug-ins based on the callback service type, wherein the notification callback mode corresponding to the ITSM type includes asynchronous callback. The message notification module is configured to execute a notification task corresponding to the notification service request through the target plug-in, including: obtaining callback content corresponding to the notification callback request through the target plug-in, and storing the callback content in a database. The callback plug-in includes a callback service interface, an ITSM single plug-in interface, and an abstract class, and the callback plug-in is developed by inheriting AbstractItsmCallbackService.

7. An electronic device, comprising: a processor; and a memory storing a program, wherein the program includes instructions that, when executed by the processor, cause the processor to perform the method according to any one of claims 1-5.

8. A non-transitory computer readable storage medium having stored thereon computer instructions, wherein, The computer instructions are used to cause the computer to perform the method according to any one of claims 1-5.

Images