PROVIDING RECOMMENDED RESOLUTIONS FOR EVENTS

BACKGROUND

The present invention relates generally to the field of computing, and more specifically, to event resolution.

Generally, data centers and networks may include fault management protocols to receive event notifications indicating that events, such as network errors, may have occurred. In such cases, typical event resolving methods may include fault analysis and root cause analysis. For example, when an event occurs in a data center, a notification, such as simple network management protocol, is sent to an event manager. The received event may often be enriched with data, be handled by a rules engine, and/or create a ticket for a help desk administrator.

SUMMARY

A method for enabling at least one user interface display field to perform at least one action is provided. The method may include receiving a plurality of first events. The method may further include generating a plurality of tickets based on the plurality of first events. Additionally, the method may include routing the received plurality of first events and the generated plurality of tickets to at least one service department. The method may also include associating a plurality of resolutions codes with the received plurality of first events and the generated plurality of tickets. The method may further include receiving at least one second event associated with the received plurality of first events and the generated plurality of tickets. The method may also include determining the plurality of resolution codes to the at least one second event based on the association of the at least one second event to the received plurality of first events and the generated plurality of tickets. The method may further include ranking the determined plurality of resolution codes to the at least one second event. The method may also include presenting the ranked plurality of resolution codes to the at least one second event to users.

A computer system for enabling at least one user interface display field to perform at least one action is provided. The computer system may include one or more processors, one or more computer-readable memories, one or more computer-readable tangible storage devices, and program instructions stored on at least one of the one or more storage devices for execution by at least one of the one or more processors via at least one of the one or more memories, whereby the computer system is capable of performing a method. The method may include receiving a plurality of first events. The method may further include generating a plurality of tickets based on the plurality of first events. Additionally, the method may include routing the received plurality of first events and the generated plurality of tickets to at least one service department. The method may also include associating a plurality of resolutions codes with the received plurality of first events and the generated plurality of tickets. The method may further include receiving at least one second event associated with the received plurality of first events and the generated plurality of tickets. The method may also include determining the plurality of resolution codes to the at least one second event based on the association of the at least one second event to the received plurality of first events and the generated plurality of tickets. The method may further include ranking the determined plurality of resolution codes to the at least one second event. The method may also include presenting the ranked plurality of resolution codes to the at least one second event to users.

A computer program product for enabling at least one user interface display field to perform at least one action is provided. The computer program product may include one or more computer-readable storage devices and program instructions stored on at least one of the one or more tangible storage devices, the program instructions executable by a processor. The computer program product may include program instructions to receive a plurality of first events. The computer program product may also include program instructions to generate a plurality of tickets based on the plurality of first events. Additionally, the computer program product may include program instructions to route the received plurality of first events and the generated plurality of tickets to at least one service department. The computer program product may further include program instructions to associate a plurality of resolutions codes with the received plurality of first events and the generated plurality of tickets. The computer program product may also include program instructions to receive at least one second event associated with the received plurality of first events and the generated plurality of tickets. The computer program product may further include program instructions to determine the plurality of resolution codes to the at least one second event based on the association of the at least one second event to the received plurality of first events and the generated plurality of tickets. The computer program product may also include program instructions to rank the determined plurality of resolution codes to the at least one second event. The computer program product may further include program instructions to present the ranked plurality of resolution codes to the at least one second event to users.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

These and other objects, features and advantages of the present invention will become apparent from the following detailed description of illustrative embodiments thereof, which is to be read in connection with the accompanying drawings. The various features of the drawings are not to scale as the illustrations are for clarity in facilitating one skilled in the art in understanding the invention in conjunction with the detailed description. In the drawings:

FIG. 1 illustrates a networked computer environment according to one embodiment;

FIG. 2 is an operational flowchart illustrating the steps carried out by a program for providing recommended resolutions to events according to one embodiment;

FIG. 3 is a block diagram of the system architecture of a program for providing recommended resolutions to events according to one embodiment;

FIG. 4 is a block diagram of an illustrative cloud computing environment including the computer system depicted in FIG. 1, in accordance with an embodiment of the present disclosure; and

FIG. 5 is a block diagram of functional layers of the illustrative cloud computing environment of FIG. 4, in accordance with an embodiment of the present disclosure.

DETAILED DESCRIPTION

Detailed embodiments of the claimed structures and methods are disclosed herein; however, it can be understood that the disclosed embodiments are merely illustrative of the claimed structures and methods that may be embodied in various forms. This invention may, however, be embodied in many different forms and should not be construed as limited to the exemplary embodiments set forth herein. Rather, these exemplary embodiments are provided so that this disclosure will be thorough and complete and will fully convey the scope of this invention to those skilled in the art. In the description, details of well-known features and techniques may be omitted to avoid unnecessarily obscuring the presented embodiments.

Embodiments of the present invention relate generally to the field of computing, and more particularly, to event management and resolution. The following described exemplary embodiments provide a system, method and program product for providing resolutions to events. Therefore, the present embodiment has the capacity to improve the technical field associated with event resolution by leveraging resolutions to events and tickets to recommend resolutions for received events. Specifically, the present embodiment may analyze archived events and tickets to provide resolutions to received events based on the resolutions to the archived event and tickets.

As previously described with respect to fault management, event notifications indicating that events, such as network errors and/or access lost to host servers, may be received. Typically, the received event notifications create tickets, often time-stamped in the time ordered received, for a help desk attendant to resolve the event. However, tickets generated by a number of received events affect the time and resources it takes to resolve the received events. Specifically, the performance and availability of help desk services may be reduced due to the volume of received events. As such, it may be advantageous, among other things, to provide a system, method and program product for providing recommended resolutions for events to improve performance, reduce cost and mean time to repair (MTTR), and increase return on investment (ROI). Specifically, archived events and tickets may be analyzed to provide resolutions to received events based on the resolutions to the archived event and tickets.

According to at least one implementation of the present embodiment, first events may be received. Next, tickets may be generated based on the first events. Then, resolution codes may be associated with the first events and the tickets. Next, the first events and tickets may be routed to service departments. Then, resolution codes may be associated with the first events and the tickets. Next, at least one second event may be received. Then, resolutions to the at least one second event may be determined. Next, the resolutions to the at least one second event may be ranked based on the associated resolution codes. Then, the resolutions to the at least one second event may be presented.

The present invention may be a system, a method, and/or a computer program product. The computer program product may include a computer readable storage medium (or media) having computer readable program instructions thereon for causing a processor to carry out aspects of the present invention.

The computer readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device. The computer readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of the computer readable storage medium includes the following: 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), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing. A computer readable storage medium, as used herein, is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire.

Computer readable program instructions described herein can be downloaded to respective computing/processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and/or a wireless network. The network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. A network adapter card or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing/processing device.

Computer readable program instructions for carrying out operations of the present invention may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like, and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The computer readable program instructions may 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 may 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 may be made to an external computer (for example, through the Internet using an Internet Service Provider). In some embodiments, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer readable program instructions.

These computer readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, a programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function/act specified in the flowchart and/or block diagram block or blocks.

The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions/acts specified in the flowchart and/or block diagram block or blocks.

The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts or carry out combinations of special purpose hardware and computer instructions.

The following described exemplary embodiments provide a system, method and program product for providing recommended resolutions to events.

According to at least one implementation, first events may be received. Next, tickets may be generated based on the first events. Then, resolution codes may be associated with the first events and the tickets. Next, the first events and tickets may be routed to service departments. Then, resolution codes may be associated with the first events and the tickets. Next, at least one second event may be received. Then, resolutions to the at least one second event may be determined. Next, the resolutions to the at least one second event may be ranked based on the associated resolution codes. Then, the resolutions to the at least one second event may be presented.

Referring now to FIG. 1, an exemplary networked computer environment 100 in accordance with one embodiment is depicted. The networked computer environment 100 may include a computer 102 with a processor 104 and a data storage device 106 that is enabled to run an event management and resolution program 108A and a software program 114. The software program 114 may be an application program such as an internet browser and an email program. The event management and resolution program 108A may communicate with the software program 114. The networked computer environment 100 may also include a server 112 that is enabled to run an event management and resolution program 108B and a communication network 110. The networked computer environment 100 may include a plurality of computers 102 and servers 112, only one of which is shown for illustrative brevity.

According to at least one implementation, the present embodiment may also include a database 116, which may be running on server 112. The communication network may include various types of communication networks, such as a wide area network (WAN), local area network (LAN), a telecommunication network, a wireless network, a public switched network and/or a satellite network. It may be appreciated that FIG. 1 provides only an illustration of one implementation and does not imply any limitations with regard to the environments in which different embodiments may be implemented. Many modifications to the depicted environments may be made based on design and implementation requirements.

The client computer 102 may communicate with server computer 112 via the communications network 110. The communications network 110 may include connections, such as wire, wireless communication links, or fiber optic cables. As will be discussed with reference to FIG. 3, server computer 112 may include internal components 800a and external components 900a, respectively and client computer 102 may include internal components 800b and external components 900b, respectively. Server computer 112 may also operate in a cloud computing service model, such as Software as a Service (SaaS), Platform as a Service (PaaS), or Infrastructure as a Service (IaaS). Server 112 may also be located in a cloud computing deployment model, such as a private cloud, community cloud, public cloud, or hybrid cloud. Client computer 102 may be, for example, a mobile device, a telephone, a personal digital assistant, a netbook, a laptop computer, a tablet computer, a desktop computer, or any type of computing device capable of running a program and accessing a network. According to various implementations of the present embodiment, the event management and resolution program 108A, 108B may interact with a database 116 that may be embedded in various storage devices, such as, but not limited to a mobile device 102, a networked server 112, or a cloud storage service.

According to the present embodiment, a program, such as an event management and resolution program 108A and 108B may run on the client computer 102 or on the server computer 112 via a communications network 110. The event management and resolution program 108A, 108B may provide recommended resolutions to events. Specifically, a user using a computer, such as computer 102, may run an event management and resolution program 108A, 108B, that interacts with a software program 114, to provide resolutions to events based on resolutions associated with archived tickets and events.

Referring now to FIG. 2, an operational flowchart 200 illustrating the steps carried out by a program for providing recommended resolutions to events is depicted. At 202, the event management and resolution program 108A, 108B (FIG. 1) may receive first events. For example, the event management and resolution program 108A, 108B (FIG. 1) may receive first events such as network errors, switch router failures, and access lost to host servers that may be events occurring in a system. Furthermore, the event management and resolution program 108A, 108B (FIG. 1) may receive the first events as simple network management protocol (SNMP) traps via SNMP probes, log scraping, and gateways. Additionally, the event management and resolution program 108A, 108B (FIG. 1) may receive information associated with the first events, such as, the time of the first event, the frequency of the first event, the system nodes affected by the first event, and the service department designated to resolve the first event.

Next, at 204, the event management and resolution program 108A, 108B (FIG. 1) may generate tickets based on the received first events. Specifically, when first events are received, the event management and resolution program 108A, 108B (FIG. 1) may generate tickets using event management systems, such as IBM Netcool OMNIbus® and IBM Netcool Operations® (IBM and all IBM-based trademarks and logos are trademarks or registered trademarks of IBM and/or its affiliates), and include information in the tickets based on data associated with the first events. For example, the event management and resolution program 108A, 108B (FIG. 1) may receive a first event, such as a switch router failure. Thereafter, the event management and resolution program 108A, 108B (FIG. 1) may generate a ticket that includes data based on the first event, such as the type of first event (i.e. switch router failure), the time of the first event, the frequency of the first event, the system nodes affected by the first event, and the service department designated to resolve the first event.

Then, at 206, the event management and resolution program 108A, 108B (FIG. 1) may route the first events and the tickets to service departments. Specifically, according to one embodiment, the event management and resolution program 108A, 108B (FIG. 1) may route the first events and tickets to the designated service desk/department based on the type of the first event, the time of the first event, and the frequency of the first event, to resolve the first events. For example, the event management and resolution program 108A, 108B (FIG. 1) may receive first events such as network errors. Furthermore, the event management and resolution program 108A, 108B (FIG. 1) may generate tickets based on the network errors, and may include in the tickets the times of the network errors along with the service departments that resolve network errors, such as subject matter experts in networks, application developers, and database specialists. Thereafter, the event management and resolution program 108A, 108B (FIG. 1) may route the first events and the tickets to the service departments based on the time received to resolve the network errors.

Then, at 208, the event management and resolution program 108A, 108B (FIG. 1) may associate resolution codes with the generated tickets and the first events. As previously described at steps 202-206, the event management and resolution program 108A, 108B (FIG. 1) may receive first events, generate tickets that include information based on the received first events, and route the tickets to the designated service desk/department to resolve the first events. As such, when the first events are resolved by the designated service desk/department, the event management and resolution program 108A, 108B (FIG. 1) may associate resolution codes with the tickets and the corresponding first events to indicate the action taken to resolve the tickets and the first events. Specifically, according to one embodiment, the event management and resolution program 108A, 108B (FIG. 1) may associate resolution codes, using a coding system and/or texts, with the tickets and the first events. For example, for a first event, such as a network error, the event management and resolution program 108A, 108B (FIG. 1) may associate a coding system using letters and numbers, such as RC27, with the tickets and the first events to indicate that a resolution code 27 was used to resolve the network error. Furthermore, the event management and resolution program 108A, 108B (FIG. 1) may associate a resolution code using text, such as “system reboot,” with the tickets and the first events to indicate that a “system reboot” was used to resolve the network error. Additionally, the event management and resolution program 108A, 108B (FIG. 1) may archive the first events along with the information, tickets, and resolution codes associated with the first events.

Next, at 210, the event management and resolution program 108A, 108B (FIG. 1) may receive at least one second event. As previously described at step 202, the event management and resolution program 108A, 108B (FIG. 1) may receive first events such as network errors, switch router failures, and access lost to host servers that are new events that occur in systems. Furthermore, the event management and resolution program 108A, 108B (FIG. 1) may generate tickets based on the first events. Additionally, the event management and resolution program 108A, 108B (FIG. 1) may receive at least one second event that may include network errors, switch router failures, and access lost to host servers that are events that are similar to the first events. Furthermore, the event management and resolution program 108A, 108B (FIG. 1) may generate tickets associated with the at least one second event that are similar to the tickets associated with the first events. Therefore, the event management and resolution program 108A, 108B (FIG. 1) may receive first events that are new events occurring in systems, generate tickets based on the new events, as well as receive at least one second event similar to the first events, and generate tickets based on the at least one second event that are similar to the tickets associated with the first events.

Then, at 212, the event management and resolution program 108A, 108B (FIG. 1) may determine resolutions to the at least one second event using the resolution codes. As previously described in step 208, the event management and resolution program 108A, 108B (FIG. 1) may associate resolution codes to the first events and the tickets associated with the first events to indicate the actions taken to resolve the first events. Also, as previously described in step 210, the event management and resolution program 108A, 108B (FIG. 1) may receive at least one second event similar to the first events. As such, based on the similarity of the at least one second event to the first events, the event management and resolution program 108A, 108B (FIG. 1) may determine resolutions to the at least one second event using the resolutions codes associated with the first events and the tickets.

For example, the event management and resolution program 108A, 108B (FIG. 1) may receive first events, that may include access lost to different host servers, as well as receive information associated with the first events (i.e. the time of the first events, the frequency of the first events, the system nodes affected by the first events, and the service departments designated to resolve the first events). Furthermore, the event management and resolution program 108A, 108B (FIG. 1) may generate tickets based on the first events, route the first events to service departments, and associate resolution codes to the first events and the tickets to indicate the actions taken to resolve the first events. Thereafter, the event management and resolution program 108A, 108B (FIG. 1) may receive at least one second event, that may include access lost to a host server, receive the information associated with the at least one second event, and generate a ticket based on the at least one second event. Therefore, the event management and resolution program 108A, 108B (FIG. 1) may determine that there is a similarity between the first events and tickets to the at least one second event and ticket (i.e. access lost to a host server), as well as similarities between the information associated with the first events to the information associated with the at least one second event. As such, the event management and resolution program 108A, 108B (FIG. 1) may determine that the resolution codes associated with the first events and tickets may be resolutions to the at least one second event. For example, the event management and resolution program 108A, 108B (FIG. 1) may determine that the resolution codes with the first events and tickets, such as “system reboot” and/or “tech sent on site”, may be resolutions to the at least one second event.

Next, at 214, the event management and resolution program 108A, 108B (FIG. 1) may rank the resolutions to the at least one second event. As previously described at step 212, the event management and resolution program 108A, 108B (FIG. 1) may determine resolution codes to the at least one second event based on information associated with the first events and the at least one second event. Furthermore, the event management and resolution program 108A, 108B (FIG. 1) may rank the resolution codes based on the information associated with the first events and the at least one second event. For example, the event management and resolution program 108A, 108B (FIG. 1) may determine that the resolution codes “system reboot”, “cable plugged back in”, and “tech sent on site”, may be resolutions to the at least one second event. Thereafter, the event management and resolution program 108A, 108B (FIG. 1) may rank the resolution codes based on information, such as, the frequency of the at least one second event and the system nodes affected by the at least one second event compared to the frequency of the received first events and the system nodes affected by the received first events. As such, based on the compared information, the event management and resolution program 108A, 108B (FIG. 1) may rank the resolutions codes in the following order: 1) “cable plugged back in, 2) “system reboot,” and 3) “tech sent on site.”

Then, at 216, the event management and resolution program 108A, 108B (FIG. 1) may present the ranked resolution codes to users. Specifically, based on the ranking of the resolution codes, the event management and resolution program 108A, 108B (FIG. 1) may recommend resolutions to the at least one second event using the resolutions codes, and present the resolutions to users in ranking order.

It may be appreciated that FIG. 2 provide only illustrations of one implementation and does not imply any limitations with regard to how different embodiments may be implemented. Many modifications to the depicted environments may be made based on design and implementation requirements. For example, in step 214, the event management and resolution program 108A, 108B (FIG. 1) may use a multi-label classifier model to rank the resolutions by a class scoring method, whereby a cut-off may be implemented so that a class score below a certain threshold (such as, a score of “no known remediation”) may not be presented to users.

FIG. 3 is a block diagram 300 of internal and external components of computers depicted in FIG. 1 in accordance with an illustrative embodiment of the present invention. It should be appreciated that FIG. 3 provides only an illustration of one implementation and does not imply any limitations with regard to the environments in which different embodiments may be implemented. Many modifications to the depicted environments may be made based on design and implementation requirements.

Data processing system 800, 900 is representative of any electronic device capable of executing machine-readable program instructions. Data processing system 800, 900 may be representative of a smart phone, a computer system, PDA, or other electronic devices. Examples of computing systems, environments, and/or configurations that may represented by data processing system 800, 900 include, but are not limited to, personal computer systems, server computer systems, thin clients, thick clients, hand-held or laptop devices, multiprocessor systems, microprocessor-based systems, network PCs, minicomputer systems, and distributed cloud computing environments that include any of the above systems or devices.

User client computer 102 (FIG. 1), and network server 112 (FIG. 1) include respective sets of internal components 800a, b and external components 900a, b illustrated in FIG. 3. Each of the sets of internal components 800a, b includes one or more processors 820, one or more computer-readable RAMs 822, and one or more computer-readable ROMs 824 on one or more buses 826, and one or more operating systems 828 and one or more computer-readable tangible storage devices 830. The one or more operating systems 828, the software program 114 (FIG. 1), the event management and resolution program 108A (FIG. 1) in client computer 102 (FIG. 1), and the event management and resolution program 108B (FIG. 1) in network server computer 112 (FIG. 1) are stored on one or more of the respective computer-readable tangible storage devices 830 for execution by one or more of the respective processors 820 via one or more of the respective RAMs 822 (which typically include cache memory). In the embodiment illustrated in FIG. 3, each of the computer-readable tangible storage devices 830 is a magnetic disk storage device of an internal hard drive. Alternatively, each of the computer-readable tangible storage devices 830 is a semiconductor storage device such as ROM 824, EPROM, flash memory or any other computer-readable tangible storage device that can store a computer program and digital information.

Each set of internal components 800a, b, also includes a R/W drive or interface 832 to read from and write to one or more portable computer-readable tangible storage devices 936 such as a CD-ROM, DVD, memory stick, magnetic tape, magnetic disk, optical disk or semiconductor storage device. A software program, such as an event management and resolution program 108A and 108B (FIG. 1), can be stored on one or more of the respective portable computer-readable tangible storage devices 936, read via the respective R/W drive or interface 832 and loaded into the respective hard drive 830.

Each set of internal components 800a, b also includes network adapters or interfaces 836 such as a TCP/IP adapter cards, wireless Wi-Fi interface cards, or 3G or 4G wireless interface cards or other wired or wireless communication links. The event management and resolution program 108A (FIG. 1) and software program 114 (FIG. 1) in client computer 102 (FIG. 1), and the event management and resolution program 108B (FIG. 1) in network server 112 (FIG. 1) can be downloaded to client computer 102 (FIG. 1) from an external computer via a network (for example, the Internet, a local area network or other, wide area network) and respective network adapters or interfaces 836. From the network adapters or interfaces 836, the event management and resolution program 108A (FIG. 1) and software program 114 (FIG. 1) in client computer 102 (FIG. 1) and the event management and resolution program 108B (FIG. 1) in network server computer 112 (FIG. 1) are loaded into the respective hard drive 830. The network may comprise copper wires, optical fibers, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers.

Each of the sets of external components 900a, b can include a computer display monitor 920, a keyboard 930, and a computer mouse 934. External components 900a, b can also include touch screens, virtual keyboards, touch pads, pointing devices, and other human interface devices. Each of the sets of internal components 800a, b also includes device drivers 840 to interface to computer display monitor 920, keyboard 930, and computer mouse 934. The device drivers 840, R/W drive or interface 832 and network adapter or interface 836 comprise hardware and software (stored in storage device 830 and/or ROM 824).

It is understood in advance that although this disclosure includes a detailed description on cloud computing, implementation of the teachings recited herein are not limited to a cloud computing environment. Rather, embodiments of the present invention are capable of being implemented in conjunction with any other type of computing environment now known or later developed.

Cloud computing is a model of service delivery for enabling convenient, on-demand network access to a shared pool of configurable computing resources (e.g. networks, network bandwidth, servers, processing, memory, storage, applications, virtual machines, and services) that can be rapidly provisioned and released with minimal management effort or interaction with a provider of the service. This cloud model may include at least five characteristics, at least three service models, and at least four deployment models.

Characteristics are as follows:

On-demand self-service: a cloud consumer can unilaterally provision computing capabilities, such as server time and network storage, as needed automatically without requiring human interaction with the service's provider.

Broad network access: capabilities are available over a network and accessed through standard mechanisms that promote use by heterogeneous thin or thick client platforms (e.g., mobile phones, laptops, and PDAs).

Resource pooling: the provider's computing resources are pooled to serve multiple consumers using a multi-tenant model, with different physical and virtual resources dynamically assigned and reassigned according to demand. There is a sense of location independence in that the consumer generally has no control or knowledge over the exact location of the provided resources but may be able to specify location at a higher level of abstraction (e.g., country, state, or datacenter).

Rapid elasticity: capabilities can be rapidly and elastically provisioned, in some cases automatically, to quickly scale out and rapidly released to quickly scale in. To the consumer, the capabilities available for provisioning often appear to be unlimited and can be purchased in any quantity at any time.

Measured service: cloud systems automatically control and optimize resource use by leveraging a metering capability at some level of abstraction appropriate to the type of service (e.g., storage, processing, bandwidth, and active user accounts). Resource usage can be monitored, controlled, and reported providing transparency for both the provider and consumer of the utilized service.

Service Models are as follows:

Software as a Service (SaaS): the capability provided to the consumer is to use the provider's applications running on a cloud infrastructure. The applications are accessible from various client devices through a thin client interface such as a web browser (e.g., web-based e-mail). The consumer does not manage or control the underlying cloud infrastructure including network, servers, operating systems, storage, or even individual application capabilities, with the possible exception of limited user-specific application configuration settings.

Platform as a Service (PaaS): the capability provided to the consumer is to deploy onto the cloud infrastructure consumer-created or acquired applications created using programming languages and tools supported by the provider. The consumer does not manage or control the underlying cloud infrastructure including networks, servers, operating systems, or storage, but has control over the deployed applications and possibly application hosting environment configurations.

Infrastructure as a Service (IaaS): the capability provided to the consumer is to provision processing, storage, networks, and other fundamental computing resources where the consumer is able to deploy and run arbitrary software, which can include operating systems and applications. The consumer does not manage or control the underlying cloud infrastructure but has control over operating systems, storage, deployed applications, and possibly limited control of select networking components (e.g., host firewalls).

Deployment Models are as follows:

Private cloud: the cloud infrastructure is operated solely for an organization. It may be managed by the organization or a third party and may exist on-premises or off-premises.

Community cloud: the cloud infrastructure is shared by several organizations and supports a specific community that has shared concerns (e.g., mission, security requirements, policy, and compliance considerations). It may be managed by the organizations or a third party and may exist on-premises or off-premises.

Public cloud: the cloud infrastructure is made available to the general public or a large industry group and is owned by an organization selling cloud services.

Hybrid cloud: the cloud infrastructure is a composition of two or more clouds (private, community, or public) that remain unique entities but are bound together by standardized or proprietary technology that enables data and application portability (e.g., cloud bursting for load-balancing between clouds).

A cloud computing environment is service oriented with a focus on statelessness, low coupling, modularity, and semantic interoperability. At the heart of cloud computing is an infrastructure comprising a network of interconnected nodes.

Referring now to FIG. 4, illustrative cloud computing environment 400 is depicted. As shown, cloud computing environment 400 comprises one or more cloud computing nodes 100 with which local computing devices used by cloud consumers, such as, for example, personal digital assistant (PDA) or cellular telephone 400A, desktop computer 400B, laptop computer 400C, and/or automobile computer system 400N may communicate. Nodes 100 may communicate with one another. They may be grouped (not shown) physically or virtually, in one or more networks, such as Private, Community, Public, or Hybrid clouds as described hereinabove, or a combination thereof. This allows cloud computing environment 400 to offer infrastructure, platforms and/or software as services for which a cloud consumer does not need to maintain resources on a local computing device. It is understood that the types of computing devices 400A-N shown in FIG. 4 are intended to be illustrative only and that computing nodes 100 and cloud computing environment 400 can communicate with any type of computerized device over any type of network and/or network addressable connection (e.g., using a web browser).

Referring now to FIG. 5, a set of functional abstraction layers 500 provided by cloud computing environment 400 (FIG. 4) is shown. It should be understood in advance that the components, layers, and functions shown in FIG. 5 are intended to be illustrative only and embodiments of the invention are not limited thereto. As depicted, the following layers and corresponding functions are provided:

Hardware and software layer 60 includes hardware and software components. Examples of hardware components include: mainframes 61; RISC (Reduced Instruction Set Computer) architecture based servers 62; servers 63; blade servers 64; storage devices 65; and networks and networking components 66. In some embodiments, software components include network application server software 67 and database software 68.

Virtualization layer 70 provides an abstraction layer from which the following examples of virtual entities may be provided: virtual servers 71; virtual storage 72; virtual networks 73, including virtual private networks; virtual applications and operating systems 74; and virtual clients 75.

In one example, management layer 80 may provide the functions described below. Resource provisioning 81 provides dynamic procurement of computing resources and other resources that are utilized to perform tasks within the cloud computing environment. Metering and Pricing 82 provide cost tracking as resources are utilized within the cloud computing environment, and billing or invoicing for consumption of these resources. In one example, these resources may comprise application software licenses. Security provides identity verification for cloud consumers and tasks, as well as protection for data and other resources. User portal 83 provides access to the cloud computing environment for consumers and system administrators. Service level management 84 provides cloud computing resource allocation and management such that required service levels are met. Service Level Agreement (SLA) planning and fulfillment 85 provide pre-arrangement for, and procurement of, cloud computing resources for which a future requirement is anticipated in accordance with an SLA.

Workloads layer 90 provides examples of functionality for which the cloud computing environment may be utilized. Examples of workloads and functions which may be provided from this layer include: mapping and navigation 91; software development and lifecycle management 92; virtual classroom education delivery 93; data analytics processing 94; transaction processing 95; and Event Management and Resolution 96. An Event Management and Resolution Program 108A, 108B (FIG. 1) may be offered “as a service in the cloud” (i.e., Software as a Service (SaaS)) for applications running on mobile devices 102 (FIG. 1) and may provide recommended resolutions to events.

The descriptions of the various embodiments of the present invention have been presented for purposes of illustration, but are not intended to be exhaustive or limited to the embodiments disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope of the described embodiments. The terminology used herein was chosen to best explain the principles of the embodiments, the practical application or technical improvement over technologies found in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein.

	Number	Date	Country
Parent	14926642	Oct 2015	US
Child	15095447		US

PROVIDING RECOMMENDED RESOLUTIONS FOR EVENTS

Information

Publication Number

Date Filed

Date Published

Inventors

Original Assignees

CPC

International Classifications

Abstract

Description

Claims

Continuations (1)