WO2013148470A1 - Requesting and displaying a business service context from a virtual database - Google Patents

Requesting and displaying a business service context from a virtual database Download PDF

Info

Publication number
WO2013148470A1
WO2013148470A1 PCT/US2013/033355 US2013033355W WO2013148470A1 WO 2013148470 A1 WO2013148470 A1 WO 2013148470A1 US 2013033355 W US2013033355 W US 2013033355W WO 2013148470 A1 WO2013148470 A1 WO 2013148470A1
Authority
WO
WIPO (PCT)
Prior art keywords
business service
computing device
business
service context
user
Prior art date
Application number
PCT/US2013/033355
Other languages
English (en)
French (fr)
Inventor
Vincent Joseph Kowalski
Simon Jeremy KING
Tamar Shor
Original Assignee
Bmc Software, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US13/432,888 external-priority patent/US8818994B2/en
Application filed by Bmc Software, Inc. filed Critical Bmc Software, Inc.
Priority to JP2015503402A priority Critical patent/JP6228968B2/ja
Priority to EP13716557.7A priority patent/EP2842058A1/en
Priority to CA2868804A priority patent/CA2868804C/en
Priority to AU2013240062A priority patent/AU2013240062B2/en
Publication of WO2013148470A1 publication Critical patent/WO2013148470A1/en

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/25—Integrating or interfacing systems involving database management systems
    • G06F16/256—Integrating or interfacing systems involving database management systems in federated or virtual databases

Definitions

  • This description relates to business computing, specifically the collection and display of information related to a business service.
  • BSM Business service management
  • IT information technology
  • BSM tools are generally designed to help IT organizations view and manage technology environments, in order to better support and maintain the main services they provide to the business.
  • an email system may include an email server application which is executed by one or more physical computers or servers.
  • a Help-Desk application may collect or access data referring to various user's experiences and troubles with an email system.
  • the email server application itself my collect or access data regarding how the email system processes emails (e.g., user not found errors, failure to deliver errors, number of emails sent, etc.).
  • a third business application may monitor the system resources (e.g., processor load, memory utilization, network bandwidth, etc.) used by the physical computer or computes executing the email server application.
  • a method may include requesting, from a database and by a program executing on a mobile computing device, at least a portion of a business service context regarding a business service.
  • the method may also include receiving, from the database, an aggregated database result regarding the business service.
  • the aggregated database result may include the requested business service context and wherein the business service context includes information from a plurality of applications.
  • the method may also include displaying, via the mobile computing device, at least a portion of the information included by the business service context.
  • a mobile computing device may include a microprocessor, a network interface, and a monitor.
  • the microprocessor may be configured to execute a software application.
  • the network interface may be configured to request, at the instruction of the software application executing via the microprocessor, at least a portion of a business service context regarding a business service, and receive, from the database, an aggregated database result regarding the business service, wherein the aggregated database result includes the requested business service context and wherein the business service context includes information from a plurality of applications.
  • the monitor may be configured to display at least a portion of the information included by the business service context.
  • a computer program product for the collection and display of information related to a business service may be tangibly and non-transitorily embodied on a computer-readable medium.
  • the computer program may include executable code that, when executed, is configured to cause a mobile computing apparatus to: request, from a database, at least a portion of a business service context regarding a business service; receive, from the database, an aggregated database result regarding the business service, wherein the aggregated database result includes the requested business service context and wherein the business service context includes information from a plurality of applications; and display, via the mobile computing device, at least a portion of the information included by the business service context.
  • FIG. 1 is a block diagram of an example embodiment of a system in accordance with the disclosed subject matter.
  • FIG. 2 is a diagram of an example embodiment of a user interface in accordance with the disclosed subject matter.
  • FIG. 3 is a block diagram of an example embodiment of a system in accordance with the disclosed subject matter.
  • FIG. 4a is a diagram of an example embodiment of a user interface in accordance with the disclosed subject matter.
  • FIG. 4b is a diagram of an example embodiment of a user interface in accordance with the disclosed subject matter.
  • FIG. 4c is a diagram of an example embodiment of a user interface in accordance with the disclosed subject matter.
  • FIG. 5 a is a block diagram of an example embodiment of a system in accordance with the disclosed subject matter.
  • FIG. 5b is a block diagram of an example embodiment of a user interface in accordance with the disclosed subject matter.
  • FIG. 6 is a flow chart of an example embodiment of a technique in accordance with the disclosed subject matter.
  • FIG. 7 is a flow chart of an example embodiment of a technique in accordance with the disclosed subject matter.
  • FIG. 8 is a block diagram of an example embodiment of a system in accordance with the disclosed subject matter.
  • FIG. 9 is a flow chart of an example embodiment of a technique in accordance with the disclosed subject matter.
  • FIG. 10a is a diagram of an example embodiment of a user interface in accordance with the disclosed subject matter.
  • FIG. 10b is a diagram of an example embodiment of a user interface in accordance with the disclosed subject matter.
  • FIG. 10c is a diagram of an example embodiment of a user interface in accordance with the disclosed subject matter.
  • FIG. 1 Od is a diagram of an example embodiment of a user interface in accordance with the disclosed subject matter.
  • FIG. lOe is a diagram of an example embodiment of a user interface in accordance with the disclosed subject matter.
  • FIG. 1 Of is a diagram of an example embodiment of a user interface in accordance with the disclosed subject matter.
  • FIG. lOg is a diagram of an example embodiment of a user interface in accordance with the disclosed subject matter.
  • FIG. 1 Oh is a diagram of an example embodiment of a user interface in accordance with the disclosed subject matter.
  • FIG. 11 is a flow chart of an example embodiment of a technique in accordance with the disclosed subject matter.
  • FIG. 1 is a block diagram of an example embodiment of a system 100 in accordance with the disclosed subject matter.
  • the system 100 may include an apparatus 102 that is used or operated by a user 190, a database (DB) server or system 104, and one or more business application servers 106.
  • the apparatus 102 may include a traditional computer (e.g., a desktop, laptop, netbook, etc.) or a non-traditional computing device (e.g., smartphone, tablet, thin client, computer terminal, etc.).
  • DB database
  • the apparatus 102 may include a traditional computer (e.g., a desktop, laptop, netbook, etc.) or a non-traditional computing device (e.g., smartphone, tablet, thin client, computer terminal, etc.).
  • three business application servers 106 are illustrated, the disclosed subject matter is not limited to any number of such devices.
  • the devices 102, 104, and 106 may include instantiations of such devices included in a virtual or modular environment (e.g., a blade server
  • the term "business service” refers to a software application or a computing device operated within an Information Technology (IT) environment.
  • the a business service may include software applications, such as, for example, an email server, a file server, a Help-Desk application, a customer relationship management (CRM) application, an automation application, etc.
  • a business service may include computing devices, such as for example, a business application server 106, a blade server executing a plurality of business applications, a server pool executing one or more instances of a business application ⁇ e.g. , a web server, etc.), computing devices issued to employees or users 190, etc. It is understood that the above are merely a few illustrative examples to which the disclosed subject matter is not limited.
  • business application refers to a business service that is a software application or, more colloquially, an application ⁇ e.g. , a Help-Desk application, a sales automation application, etc.).
  • business server or “business application server” refers to a computing device that executes a business application ⁇ e.g., a server pool, a blade server, etc.).
  • a user 190 may operate, use or control an apparatus or computing device 102.
  • the computing device 102 may include a processor 112 configured to execute a stream or machine executable instructions (e.g., operating system 118, application 120, etc.).
  • the computing device 102 may include a memory 114 configured to store data and/or instructions.
  • the memory 114 may include volatile memory, non- volatile memory, or a combination thereof.
  • the memory 114 or portions thereof may be configured to store data in a temporary fashion (e.g., Random Access Memory (RAM), etc.) as part of the execution of instructions by the processor 112.
  • the memory 114 or portions thereof may be configured to store data in a semi-permanent or long-term fashion (e.g., a hard drive, solid-state memory, flash memory, optical storage, etc.).
  • the computing device 102 may include one or more network interfaces 116 configured to communicate with other devices (e.g., server 104, etc.) via a communications network.
  • this communications network may employ wired (e.g., Ethernet, Fibre Channel, etc.) or wireless (e.g., Wi-Fi, cellular, etc.) protocols or standards or a combination thereof.
  • the computing device 102 may include an operating system (OS) 118 that may be executed by the processor 112.
  • OS operating system
  • the OS 118 may be configured to act as an intermediary between application programs (e.g., application 120, etc.) and the computer hardware (processor 112, network interface 116, etc.).
  • application programs e.g., application 120, etc.
  • the computer hardware processor 112, network interface 116, etc.
  • the application may be executed directly by the hardware and may frequently call the OS 118 or be interrupted by it.
  • the computing device 102 may include or execute an application 120.
  • the application 120 may include a BMC software application and may be executed by the processor 112 in conjunction with the OS 118.
  • the computing device 102 may also include other applications (not shown).
  • the user 190 may desire to view or access information regarding a particular business service (e.g., one of the business application server 106, one of the business applications 180, etc.). In such an embodiment, the user 190 may request the display of a business service context user interface element 122.
  • a business service context e.g., one of the business application server 106, one of the business applications 180, etc.
  • service context e.g., one of the business applications 180, etc.
  • FIG. 2 is a diagram of an example embodiment of a user interface (UI) 200 in accordance with the disclosed subject matter.
  • the UI 200 may be the main or a portion of the UI for an application executing on a computing device (e.g., application 120 of Fig. 1).
  • the application may be an IT Service Management (ITSM) application.
  • ITSM IT Service Management
  • the service context may be launched or displayed within any tool or application (e.g., ITSM, BMC ProactiveNet Performance Management (BPPM), etc.).
  • ITSM ITSM
  • BMC ProactiveNet Performance Management BPPM
  • the above are merely a few illustrative examples to which the disclosed subject matter is not limited.
  • the user may desire to see or access information regarding a particular business service.
  • the user has selected to display a service context for business service 202.
  • the user may right-click on the UI element 202 associated with the desired business service (e.g. , an Electronic Product Distribution (EPD) business service, etc.). This may bring up a context menu, from which the user may select to display a service context associated with the selected business service.
  • EPD Electronic Product Distribution
  • an icon or button may bring up the service context.
  • other UI means or forms of interaction e.g., gestures, hyperlinks, etc.
  • the application may display the service context UI element 204 to display the service context or a portion thereof.
  • the business service context may include a means by which applications can reach into data they do not normally provide themselves or have access to in order to give users a thumbnail sketch or condensed version or view of what a given business service is and how it is performing.
  • the business service context and the UI element 204 displaying the business service context may be likened to a packing label (as used on shipping packages, e.g., FedEx, etc.) for business services.
  • a packing label as used on shipping packages, e.g., FedEx, etc.
  • the application may be able to make available a visual UI component 204 that a user may bring up or request in the context of some application they are running (e.g., IT Service Management, etc.) for a given business service (e.g., business service 202, EPD, etc.) that is viewable in the UI 200 of the launching application.
  • a visual UI component 204 that a user may bring up or request in the context of some application they are running (e.g., IT Service Management, etc.) for a given business service (e.g., business service 202, EPD, etc.) that is viewable in the UI 200 of the launching application.
  • this UI element 204 may be referred to as the Service Context Summary View and is discussed in more detail below in regards to Fig. 4a.
  • further UI elements may also be displayed or, in one embodiment, replace the UI element 204.
  • These subsequent UI elements may be referred to as sub-views and may include, in various embodiments, a list view configured to display additional inform regarding the service in a less condensed or alternate format.
  • various UI elements or views may focus on various aspects of the selected business service. It is understood that the above are merely a few illustrative examples to which the disclosed subject matter is not limited.
  • data from Service Context may be integrated in the User Interface 200 of the application the consumes or makes use of the Service Context (as opposed to being displayed in a separate UI element, e.g., UI element 204, etc.).
  • the set of data available to such applications may be enriched and may, in one embodiment, make the user experience more productive.
  • the integration of Service Context Data into the UI 200 of the launching application may be referred to as the Native View of Service Context.
  • various applications may access and use data from the Service Context without ever needing to display the visual UI element 204. It is understood that the above are merely a few illustrative examples to which the disclosed subject matter is not limited.
  • a user may desire the display of a business service context for a variety of reasons. Below, a few example usages cases of the service context are described. It is understood that the below are merely a few illustrative examples to which the disclosed subject matter is not limited.
  • help desks or service desks one of the most inefficient processes is getting an incident or support ticket assigned to the correct personnel. Once an incident is entered into the system, it may be handed off several times before the correct assignment is made.
  • a service context and the display of the service context (at least in part) may aid in the identification of the correct assignee of an incident by providing richer, more relevant data that is related to a given business service.
  • the flow of information across management disciplines is often not as fluid as it often should be. Problems that are encountered in one discipline may simply stay with the personnel associated with that business group or silo or if the problem does get communicated outward, the communication is often done in a less than optimal fashion.
  • the service context may be discipline agnostic. As such the data values and their respective visual representations in the summary view or other UI element may be shared across disciplines or business groups with little risk that they will be misunderstood or misinterpreted.
  • a user may be given enough information regarding what could be wrong with a given business service. However, if the user needs or desires better, more detailed information they can obtain it by launching another business application.
  • the service context and the UI element displaying it may provide the user with a starting point to help them get started on solving a problem regarding the business service without the user having to start or execute each of the various (and often more intensive) business applications.
  • the service context and/or the UI element 204 that displays the service context may be consistent in one or more ways.
  • the look and feel of the UI element 204 may be consistent across applications.
  • a user may display the service context in help-desk application or in an IT service management application and the UI element 204 may be substantially identical. In various embodiments, this may be beneficial as users in various business groups or of various business applications may be conditioned to know what to expect from the business context and how to process the information contained within.
  • the service context may be consistent in terms of the data, information, or attributes displayed.
  • the UI element may include the same fields (e.g. , business service description, business service owner, business service state, etc.) and the same values for those fields. Again, such consistency may aid user efficiency.
  • the service context and/or the UI element 204 that displays the service context may be configured to display the information regarding the business service in a simple and speedy manner.
  • the service context may include or display only information that is deemed (e.g., by a system administrator, etc.) critical and no more (unless a subsequent view or UI element is displayed), such that the information contained therein is easily understandable by a user.
  • a second user and a second computing device executing a second application may also request a service context for the same business service as the user 190.
  • the second user and the user 190 may see an identical or substantially equivalent service context or the UI element 122 displaying the service context.
  • a user at a help-desk application and a user at a device provisioning application may see substantially the same service context with a consistent look and feel, and data values (e.g. , business service status, etc.) regardless of their host application (e.g., application 120, etc.).
  • the user 190 may request to display the service context 168 of a given business service 188.
  • the business service 188 may include one of the business servers 106, one of the business applications 180, or another business service. It is understood that the above are merely a few illustrative examples to which the disclosed subject matter is not limited.
  • the application 120 may transmit or send a business service context request 162 to a federated database 150.
  • a business service context request 162 may be transmitted or send to a federated database 150.
  • the business service context request 162 may include an attribute or field indicating which business service the service context request pertains.
  • the federated DB 150 may include a configuration management DB (CMDB).
  • CMDB configuration management DB
  • general storage components e.g., a relational database, etc.
  • the federated DB 150 may be executed or included by the DB server 104.
  • the DB server 104 may include a processor 152, a memory 154, and at least one network interface 156, as described above.
  • the memory 154 may include volatile storage (e.g., random access memory etc.), non- volatile storage (e.g., a hard drive, a solid-state drive, etc.), or a combination thereof.
  • the federated DB 150 may be stored, at least in part, by a portion of the memory 154.
  • the federated DB 150 may include a virtual or at least partially virtual DB. In such an embodiment, the federated DB 150 may not include the service context 168 or the information included in the service context 168. However, the federated DB 150 may provide a single point of query for the service context information or virtualize a database that appears (to the application 120) to include the information included in the service context 168.
  • the federated DB 150 may retrieve information from a plurality of other business applications 180.
  • the federated DB 50 may then in turn query one or more business applications 180 regarding the business service 188.
  • the queried business applications 180 may retrieve information (if such exists) regarding the business service 188 from their respective business application data repositories 182. This information 164 may then be transmitted to the federated DB 150.
  • the federated DB 150 may then generated an aggregated database result 166 based, at least in part, upon the various pieces of information 164 regarding the business service 188 retrieved from the plurality of business applications 180.
  • the federated DB 150 may aggregate the information 164 in such a way that the aggregated DB result 166 appears as if the federated DB 150 was not virtual but actually included the desired information in a physical storage location.
  • the aggregated database result 166 may provide the application 120 with the information for the service context 168 or the service context 168 itself in a single database transaction. In such an embodiment, the application 120 may not have to ask repeatedly for data or be constantly updated as new information 164 arrives from the various business applications 180.
  • the application 120 may receive the aggregated database query result 166. As described above, in various embodiments, this aggregated database query result 166 may include the service context 168. In various embodiments, the application 120 may the filter or condense the information included by the service context 168 into a predetermined format (e.g., a series of predefined fields to be displayed, etc.). This portion of the service context 168 may then be displayed to the user 190 via the service context UI element 122.
  • a predetermined format e.g., a series of predefined fields to be displayed, etc.
  • new UI elements or views may be generated and displayed based upon predefined rules detailing the contents of such UI elements.
  • Various embodiments of such views are described in reference to Figs. 4a, 4b, and 4c, below. It is understood that the above are merely a few illustrative examples to which the disclosed subject matter is not limited.
  • FIG. 3 is a block diagram of an example embodiment of a system 300 in accordance with the disclosed subject matter.
  • the system 300 may be a more detailed embodiment of portions of the system 100 of Fig. 1.
  • the system 300 may include a service context consumer 302 that may be an application as described in reference to Fig. 1.
  • the system 300 may also include, in one embodiment, a federated of at least partially virtual database (DB) 304.
  • DB virtual database
  • the system 300 may also include one or more provider applications 306 that each provide information or data regarding a particular business service which is the focus of the current business service context.
  • the service context consumer or consumer application 302 may request 312 a service context for a given business service. This request 312 may be made to the federated database 304. The service context consumer 302 may expect to receive, in return, an aggregated database query result 314, which may include the requested service context. In such an embodiment, the service context consumer 302 may request 312 and receive 314 the service context (or information from which the service context may be derived) in a single atomic database transaction, as described above.
  • the federated or partially virtual database 304 may include a federated DB 304 may include a federated DB interface 358 that is configured to receive database requests (e.g., request 312, etc.) and provide database query results (e.g., query result 314, etc.) as if the DB 304 was a non-virtualized database.
  • the federated DB interface 358 may be referred to as a Service Context Abstraction Layer (SCAL) that presents a virtual view of all the attributes gathered from the various Application Data APIs 394 by this architecture.
  • SCAL Service Context Abstraction Layer
  • a consumer application 302 e.g., the Service Context View or Native Views
  • the federated DB interface 358 may be alternatively exposed as a Web Service for those consumer applications 302 that prefer this protocol.
  • the federated DB 304 may include Federated DB storage portion 350. configured to "store" various database entries or information regarding one or more business services. As described above, in various embodiments, this storage may occur virtually, at least in part, in that the federated DB 304 not actually store, at least in a long term sense, the information included in the storage portion 350, but may instead access the data dynamically from the one or more provider applications 306. [0069] However, in some embodiments, the federated DB 304 may include one or more non-virtual fields or database entries and their respective values 352. These nonvirtual fields 352 may include fundamental or default values for the various business services referenced by the federated DB 304. Such fields may include: the business service's name, the business service's description, the owner of the business service, etc. It is understood that the above are merely a few illustrative examples to which the disclosed subject matter is not limited.
  • the federated DB 304 may include one or more virtual fields or database entries and their respective values 354.
  • These virtual fields 354 may include any database fields and values that are retrieved from a provider application 306 and only nominally stored in the federated DB 304.
  • Example virtual fields may include: business service status, number of incidents or other performance metrics associated with the business service, business service location, etc. It is understood that the above are merely a few illustrative examples to which the disclosed subject matter is not limited.
  • the federated DB 304 may be referred to as merely partially virtual as the federated DB 350 may include both non-virtual fields 352 and virtual fields 354 that are aggregated to provide the illusion that the federated DB 304 includes a larger more informative DB than actually exists.
  • the non- virtual fields 352 and virtual fields 354 may be aggregated to provide the illusion that the federated DB 304 is a single monolithic database.
  • the federated DB 304 may be fully virtual and may not include the non-virtualized fields 352.
  • the federated DB 304 may be non- virtual and the information illustrated as being stored in the virtual fields 354 may be actually stored in non-virtual fields 352 of a non-virtualized federated DB. It is understood that the above are merely a few illustrative examples to which the disclosed subject matter is not limited.
  • the federated DB 304 may include a cache 360 to temporarily store the virtual fields 354 retrieved from the provider applications 306. By temporarily storing results of retrievals from the provider applications 306, the system 300 may avoid having to re-retrieve such data each time it is requested by the consumer application 302.
  • the federated DB 304 may include a service context adapter 356.
  • the service context adapter 356 may be configured to access data that is delivered from the provider applications 306. A described below, this information may be provided by the provider application 306 via a standardized format regardless of the specific provider application 306 accessed. For example, a help- desk provider application and a system resources provider application may produce information in the same format or according to a predefined protocol.
  • the service context adapter 356 may be configured to adapt or convert this information received in a standardized format into the database fields 354 or even fields 352 employed by the federated DB 304.
  • the provider applications 306 may be accessed as web services and may provide their respective data in a predefined format (e.g., Simple Object Access Protocol (SOAP), Extensible Markup Language (XML), etc.). In various embodiments, this format may be described or defined via a Web Services Description Language (WSDL) or other manner. It is understood that the above are merely a few illustrative examples to which the disclosed subject matter is not limited.
  • SOAP Simple Object Access Protocol
  • XML Extensible Markup Language
  • WSDL Web Services Description Language
  • the federated DB 304 may know or be aware of which provider applications 306 may exist and how to access them by relying or making use of an application or web service registry 308.
  • each provider application 306 may register with or inform the registry 308 of the provider application 306's existence, the location or means by which a consumer (e.g., the federated DB 304) may access the provider application 306 (e.g., network address, port number, protocol, etc.), the services or information the provider application 306 may provide and, in various embodiments, other relevant details regarding the provider service 306.
  • the registry 308 may include a Universal Description, Discovery and Integration (UDDI) compliant or substantially compliant registry. It is understood that the above is merely one illustrative example to which the disclosed subject matter is not limited.
  • UDDI Universal Description, Discovery and Integration
  • the system 300 may include one or more provider applications 306.
  • Each of these provider applications 306 may include various pieces of data or information 392 that are stored in whatever format or manner the application 306 makes use of. This data 392 may be accessed via the provider application 306's normal data application programmatic interface (API) 394.
  • API application programmatic interface
  • each provider application 306 may include, implement, or make use of a standard attribute interface (SAI) 396.
  • SAI standard attribute interface
  • Each implementation of the SAI 396 may be configured to allow a consumer (e.g., the federated DB 304) external to the provider application 306 to access the application data 392 in a standardized, uniform and predefined format and protocol.
  • the SAI 396 may allow the provider application 306 to function as a web service and be accessed by the federated DB 304 via a database query 316.
  • the federated DB 304 may be configured to read or access information a given business service from the provider applications 306 but may not be configured to edit or write new information back to the provider applications 306.
  • the service context may be an informative tool not an ameliorative or control tool.
  • the service context consumer 302 may be configured to specify edits or alterations in the retrieved data.
  • the federated DB 304 may be configured to write such change in the information back to the respective provider applications 306.
  • the writing between the consumer application 302 and the federated DB 304 may occur as a single database transaction, similarly to the read transaction (e.g., request 312 and response 314).
  • the consumer application 302 may be configured write data or communicate commands directly to the provider applications 306. It is understood that the above are merely a few illustrative examples to which the disclosed subject matter is not limited.
  • the issue of security may be considered in retrieving the service context.
  • the user or the consumer application 302 may be associated with one or more security credentials that dictate what data may be accessed and/or displayed.
  • the federated DB 304 may be configured to filter the data received from the provider applications 306, and eventually provided to the consumer application 302 via the aggregated database query result 314 based upon the security credentials associated with the consumer application 302.
  • the security credentials may be provided via the request for service context 312.
  • the presentation of the security credentials may be implicit (e.g., derivable via a username, etc.) or explicit (e.g., an authentication certificate or password included in the request 312, etc.).
  • the user of consumer application 302 may be provided with an authentication or security check (e.g. , login prompt, key code request, etc.) to access data securely stored on a provider application 306.
  • an authentication or security check e.g. , login prompt, key code request, etc.
  • the authentication requests and responses may be forwarded between the consumer application 302 and the provider application 306 via the federated DB 304.
  • the consumer application 302 and the provider application 306 may communicate directly or via another intermediary (e.g., an authentication server (not shown), etc.).
  • the service context may be initially displayed without the un-authorized data and the user may then be able to actively request that the unauthorized data be displayed. In such an embodiment, this may cause the authentication UI (e.g., login screen, etc.), as described above, for the authorization of the requested data. In one embodiment, this may allow the service context to be displayed (at least partly) in a quick and unobtrusive manner, but may allow the display of the full or most complete service context if a user wishes or desires that initially un-authorized information.
  • the new authorization may cause a new request for the updated service context or may simple cause the consumer application 302 or the federated DB 304 to unlock or cease to filter out the previously unauthorized data.
  • the system 300 may support having different security models for the provider applications 306 such that the system 300 is security model heterogeneous.
  • one or more of the provider applications 306 may include a multi-tenancy architecture.
  • multi-tenancy refers to a principle in software architecture where a single instance of the software (e.g., application 306) runs or executes on a server, serving multiple client organizations (tenants). Multi- tenancy may be contrasted with a multi-instance architecture where separate software instances (or hardware systems) are set up for different client organizations.
  • a multi- tenant architecture a software application is designed to virtually partition its data and configuration, and each client organization works with a customized virtual application instance.
  • the information provided by or available to a multi-tenancy provider application 306 may include data for a number of tenants.
  • the provider application 306 or the federated DB 304 may be configured to filter the provided data by tenant, such that the consumer application 302 only receives information it the service context that is associated with the same tenant as the consumer application 302.
  • the tenants of a provider application 306 may include Exxon, Sunoco, Shell, Chevron.
  • the consumer application 302 may be associated with the Shell tenant. Therefore, in such an embodiment, the service context may be filtered to only include data about the business service that would be accessible or authorized for the Shell tenant. It is understood that the above is merely one illustrative example to which the disclosed subject matter is not limited.
  • the service context may include both tenant- common data and tenant-specific data.
  • tenant-common data may include data that is the same regardless of what tenant is associated with the consumer application 302 or which tenant accesses the data.
  • tenant-common data may include, for example: the system resource load of business service, the computing device name, business service uptime, etc.
  • tenant-specific data may include data that differs for each tenant.
  • tenants-specific data may include, for example: the number of failed email transmission attempt an email business service may experience, the number of failed login attempts to a business service, the number of help-desk requests, support tickets, or incidents for a business service, etc.
  • the system 300 may not filter the results of the service context request such that the tenant-common data is included in the service context. But, the system 300 may also filter tenant-specific data such that only tenant- specific data associated with the consumer application 302's tenant are included in the service context. For example, every tenant may be able to see or view, within their respective service contexts, the common-tenant data (e.g., business service status, etc.), but each tenant may only see or view their own tenant-specific data (e.g., a Mobile tenant may only view the number of business service incidents for the Shell tenant, likewise for other tenants, etc.).
  • tenant-specific data such that only tenant-specific data associated with the consumer application 302's tenant are included in the service context. For example, every tenant may be able to see or view, within their respective service contexts, the common-tenant data (e.g., business service status, etc.), but each tenant may only see or view their own tenant-specific data (e.g., a Mobile tenant may only view the number of business service incidents
  • tenant-common and tenant-specific may be employed.
  • data may be associated with or have multiple or overlapping tenants.
  • tenant-common data may not exist per se, but tenant-common data may effectively exist as all tenants are associated or authorized to access that data.
  • an overlapping security scheme e.g. , non-tenant based or considering tenants
  • FIG. 4a is a diagram of an example embodiment of a user interface (UI) or UI element 401 in accordance with the disclosed subject matter.
  • the UI 401 may be included as part of or the service context user interface element (e.g., the service context user interface element 122 of Fig. 1).
  • the UI 401 may be displayed within or as part of a pop-up window or portion of a larger UI (e.g., in a Native View, as described above).
  • the UI 401 may include an Attribute View of a Service Context Summary View.
  • the UI 401 may provide a user with a "thumbnail sketch" or condensed version or view of what a given business service is and how it is performing.
  • the information displayed in the UI 401 may have been received in an aggregated database query result.
  • This aggregated database query result may have been produced or generated by a federated or at least partially virtual database based upon information regarding the business service that was, in turn, provided by a plurality of producer applications.
  • the UI 401 may include a UI element (e.g., a label, etc.) that displays the name 410 of the business service that the service context pertains.
  • the UI 401 may also include a status indicator 418 UI element (e.g., a icon, a particular color, etc.).
  • the business service "Sales Automation” may be in a critical or imperfect state. Therefore, the status indicator 418 is illustrated as an orange "X" icon giving a user a quick indicator that the business service is in a "warning" state. It is understood that the above is merely one illustrative example to which the disclosed subject matter is not limited.
  • an administrator, privileged user, or software developer may determine which database fields or pieces of information regarding the business service are to be displayed in this "thumbnail sketch" or condensed version or view of what a given business service is and how it is performing.
  • the user may define what attributes or information they would like to see displayed.
  • the UI 401 may display one or more predefined attributes or fields.
  • these predefined fields may fall into two or more categories. In an example embodiment, three categories will be used. However, it is understood that various categories or partitions of business service fields or attributes may be employed and that the disclosed subject matter is not limited to any one example embodiment.
  • the first category are mandatory or fixed fields which may have been determined or defined by a software developer to be displayed in all service contexts and service context UI elements, (e.g., UI 401, etc.).
  • mandatory or fixed fields or attributes may include: the business service's status, any other business services or configuration items that are related to the service context's business service, etc. It is understood that the above are merely a few illustrative examples to which the disclosed subject matter is not limited.
  • the second category of fields or attributes may include default fields which are predefined by a software developer as included within the service context, but may be removed by an administrator, privileged user, or another user as deemed by the embodiment.
  • examples of such default fields or attributes may include, but are not limited to: the owner or user primarily associated with the business service, a description of the business service, an indicator of the level of business impact of the business service, a number of events or activities performed or experienced by the business service (e.g., completed change request, changes deployed, incidents, etc.), etc.
  • the various fields which include numbers e.g., a number of events, etc.
  • the third category of fields or attributes may include optional fields that are by default omitted from a service context but may be added by an administrator, privileged user, or another user as deemed by the embodiment.
  • optional fields may include, but are not limited to: the number of maintenance hours experienced by the business service, the owner of the business service's contact information, the location of the business service, the priority level of the business service, the compliance status (e.g., to a standard or contractual compliment, such as uptime, etc.) of the business service, a number of outage records associated with the business service, a number of work orders or service tickets associated with the business service, a number of changes detecting the relation to the business service, a number of predictive events associated with the business service, etc.
  • the various fields which include numbers may also include a listing or a pointer to those enumerated items. It is understood that the above are merely a few illustrative examples to which the disclosed subject matter is not limited.
  • a number of attributes or fields of the service context may be displayed by UI element groups 412 and 414. As described above, some of these attributes or fields may be displayed or included as mandatory. Other attributes or fields may be included or displayed based upon a predefined scheme or set of rules established by an administrator or privileged user.
  • UI element group 412 illustrates a set of attributes that are relatively static or do not allow for further interaction with a user.
  • fields or attributes may include, but are not limited to: a description of the business service, the owner of the business service, the status of the business service, and the impact priority of the business service. It is understood that the above are merely a few illustrative examples to which the disclosed subject matter is not limited.
  • the Ul element group 414 illustrates a set of attributes that are relatively dynamic and/or allow for further interaction with a user.
  • these attributes may include a number or a list of events or objects (e.g., service tickets, other business services, etc.) that may be condensed into a single numerical value.
  • the attributes of 414 may include list attributes, having several tuples (or rows) of values that are associated with each attribute.
  • the user may be allowed or the Ul may provide a means for to progressively disclosing such lists (e.g., via Ul element 416, Ul 402 of Fig. 4b, etc.).
  • these attributes may be governed or filtered based upon a set of rules that have been predefined by an administrator or privileged user. For example, one attribute shows that 25 incidents have occurred in the last hour.
  • the set of rules may dictate the time frame (e.g. , 1 hour, etc.) that will be considered with non-conforming or older incidents being filtered out.
  • the numerical value of indicates within 1 hour is highlighted (e.g., in red, etc.) to indicate to a user that the value is of some importance.
  • the set of rules may dictate a threshold value or series of threshold values for the attribute or field. If the value of the field or items in the field (for fields containing a list of items), an indicator may be displayed to a user.
  • the Ul element 416 may be colored (e.g., red, etc.). It is understood that the above is merely one illustrative example to which the disclosed subject matter is not limited.
  • the Ul 401 may include a Ul element (e.g., Ul element 416, etc.) that allows a user to display or view these additional, initially hidden data.
  • these Ul elements 412 may include buttons, hyperlinks, context menus, etc. It is understood that the above are merely a few illustrative examples to which the disclosed subject matter is not limited.
  • FIG. 4b is a diagram of an example embodiment of a user interface 402 in accordance with the disclosed subject matter.
  • the UI 402 may illustrate a List View of a Service Context View.
  • the UI 402 may be displayed once a user has selected on of the expanding or list UI elements of the Attribute View of the Service Context (e.g., UI element 416 of Fig. 4a, etc.).
  • the UI element 420 may display a list of all the items associated with the parent attribute or field.
  • the attribute "Related incidents in the last 1 hour" may be the parent attribute or field, and the various incidents (e.g., incident 422 "INC000000042156") may be the associated items.
  • the associated items themselves may include various fields or attributes.
  • the list of associated items may be displayed in a table format. It is understood that the above is merely one illustrative example to which the disclosed subject matter is not limited.
  • the UI 402 may include a UI element 422 for returning to the previous Service Context view (e.g., UI 401 of Fig. 4a, etc.).
  • the UI 402 may include a group of UI elements 419 configured to facilitate navigation between various Service Context views.
  • the UI element group 419 may include a button or icon for navigating back to the previous Service Context view, a button or icon for returning to a "Home" view (e.g., the Attribute View of Fig. 4a, etc.).
  • the group of UI elements 419 may include a button or icon to refresh the service context.
  • the process for acquiring a service context may be repeated and the new version of the service context may be displayed directly into the current view (e.g., UI 402).
  • the group of UI elements 419 may be displayed across a plurality or all views. It is understood that the above are merely a few illustrative examples to which the disclosed subject matter is not limited.
  • FIG. 4c is a diagram of an example embodiment of a user interface 403 in accordance with the disclosed subject matter.
  • the UI 403 may include a Related Configuration Items View of the Service Context.
  • a user may view a list of business services or, in the illustrated embodiment, configuration items (e.g., Business Services, Applications, or Computer Systems, etc.) related to or associated with the business service that is the subject of the service context.
  • configuration items e.g., Business Services, Applications, or Computer Systems, etc.
  • the UI element group 430 may display a list of related configuration items 432 or business services, much as the list of incidents was displayed by UI element group 420 of Fig. 4b.
  • items included within a dependent or subordinate list, such as the related configuration items may be selectable by a user.
  • the selection may display additional information regarding the item.
  • the name of a related configuration item may include a link UI element 434 that the user may select.
  • this new service context may associated with the selected item (e.g., CLT133), as opposed to the business service of the parent service context (e.g., Sales Automation, etc.). It is understood that the above is merely one illustrative example to which the disclosed subject matter is not limited.
  • FIG. 5a is a block diagram of an example embodiment of a system 500 in accordance with the disclosed subject matter.
  • the system 500 may be similar in many ways to the system 100 of Fig. 1.
  • System 500 illustrates two variations that may occur separately or together in various embodiments o the disclosed subject matter.
  • the apparatus or computing device 102 may include the federated DB 150.
  • the federated DB 150 may be included in one of the business server 106.
  • the application 120 may include a service context administration UI 522.
  • the administration UI 522 may facilitate the creation and definition of the fields and attributes that make up a service context, and any sets of rules that govern the way the fields or attributes are filtered or displayed.
  • the administration UI 522 may allow an administrator to select which optional or non-mandatory attributes or fields are included in a service context.
  • these service context definitions may apply regardless of the business service associated with the service context.
  • each business service or class or group of business services may be associated with their respective definitions of their service contexts.
  • the administration UI 522 may allow an administrator to define or create a set of rules for filtering the attributes of the service context or dictating how the attribute is to be displayed to the user. For example, the administration UI 522 may allow an administrator to dictate that only incidents occurring within the last 1 hour may be included in the service context (as illustrated by Fig. 4a). Also, the administration UI 522 may allow an administrator to define threshold values or other conditional values that when met or exceeded cause the service context UI 122 to display a predefined indication to the user (e.g., the red UI element 416 of Fig. 4a). It is understood that the above is merely one illustrative example to which the disclosed subject matter is not limited.
  • FIG. 5b is a block diagram of an example embodiment of a user interface 501 in accordance with the disclosed subject matter.
  • the UI 501 includes a service context administration UI 522 that may be used by an administrator to define the attributes and fields included within a service context, and any sets or rules that filter the attributes or dictate how they are displayed to a user.
  • the UI 501 may include a series of UI elements 550 that may allow an administrator to define various service context settings for various categories or groups of business services (e.g., web services, applications, or server, etc.).
  • the UI 501 may include UI element groups 552 and 554 that are configured to allow an administrator to set or define which of a group of possible business service attributes or fields to include in the service context.
  • UI element group 552 may allow the definition or inclusion of the relatively simple or single valued attributes or fields.
  • UI element group 554 may allow the definition or inclusion of the relatively complex, list, or multi-valued attributes or fields.
  • the UI element 556 may allow an administrator to define various one or more sets of rules to filter which values are included in the service context (e.g., incidents occurring within the last hour, etc.), how the respective values are displayed to the user (e.g., highlighting values above a threshold, etc.), or other rules. It is understood that the above are merely a few illustrative examples to which the disclosed subject matter is not limited.
  • FIG. 6 is a flow chart of an example embodiment of a technique in accordance with the disclosed subject matter. In various embodiments, the technique 600 may be used or produced by the systems such as those of Figs. 1, 3, or 5a.
  • technique 600 may be used with or may produce user interfaces such as those of Figs. 2, 4a, 4b, 4c, or 5b.
  • user interfaces such as those of Figs. 2, 4a, 4b, 4c, or 5b.
  • Block 602 illustrates that, in one embodiment, an application may receive a request, from a user, to display at least a portion of a business service context regarding a business service, as described above.
  • requesting may include selecting, from within the application, a user interface element associated with the business service, as described above.
  • one or more of the action(s) illustrated by this Block may be performed by the apparatuses or systems of Figs. 1, 3, or 5a, the application 120 of Figs. 1 or 5a, or the via the user interface 200 of Fig. 2, as described above.
  • Block 604 illustrates that, in one embodiment, an application may receive, from a database, an aggregated database result regarding the business service, as described above.
  • the aggregated database result may include the requested business service context, as described above.
  • the business service context may, in turn, include information from a plurality of other applications, as described above.
  • receiving the aggregated database result may include receiving the aggregated database result as part of a single database query transaction, as described above.
  • the aggregated database result may be provided by an at least partially virtual database that virtualizes database fields whose field values are provided by the plurality of other applications, as described above.
  • one or more of the action(s) illustrated by this Block may be performed by the apparatuses or systems of Figs. 1, 3, or 5a, the application 120 or database server 104 of Figs. 1 or 5a, as described above.
  • Block 606 illustrates that, in one embodiment, an application may display a graphical user interface element that displays at least a portion of the information included by the business service context, as described above.
  • display may include distilling the information included by the aggregated database result into an a condensed set of information regarding the performance of the business service; and displaying a summary view graphical user interface element that displays at least a portion of the condensed set of information regarding the performance of the business service, as described above.
  • displaying may include displaying a first graphical user interface element that displays a first portion of information regarding the attributes of the business service, and in response to a user indicating they wish to view more information regarding at least one aspect of the business service, displaying a second graphical user interface element that displays a second portion of information regarding the attributes of the business service, as described above.
  • the first graphical user interface element may include a window that displays a Summary View of the business service context
  • the second graphical user interface element may include a window that displays a List View of items included in the second portion of the information, as described above.
  • displaying may include displaying a set of required information regarding the business service, and displaying a set of optional information regarding the business service, wherein the set of optional information has been previously predefined by an administrative user, as described above.
  • displaying may include evaluating at least one of the displayed information to determine if a value of the information exceeds a predefined threshold, and if so, indicating to the user that the respective information has exceeded the threshold value, as described above.
  • displaying may include displaying a business service linking user interface element that when selected causes a second business service context to be created and displayed, wherein the second business service context is associated with a second business service indicated by the business service linking user interface element, as described above.
  • a second user e.g., an administrator, etc.
  • displaying may include filtering the information to be displayed based upon the predefined set of rules, as described above.
  • one or more of the action(s) illustrated by this Block may be performed by the apparatuses or systems of Figs. 1, 3, or 5a, the application 110 of Figs. 1 or 5a, or the via the user interfaces 401, 402, and 403 of Figs. 4a, 4b, and 4c, as described above.
  • FIG. 7 is a flow chart of an example embodiment of a technique in accordance with the disclosed subject matter.
  • the technique 700 may be used or produced by the systems such as those of Figs. 1, 3, or 5a.
  • portions of technique 700 may be used with or may produce user interfaces such as those of Figs. 2, 4a, 4b, 4c, or 5b.
  • the above are merely a few illustrative examples to which the disclosed subject matter is not limited. It is understood that the disclosed subject matter is not limited to the ordering of or number of actions illustrated by technique 700.
  • Block 702 illustrates that, in one embodiment, an application may receive a request, from a user, to display at least a portion of a business service context regarding a business service, as described above.
  • one or more of the action(s) illustrated by this Block may be performed by the apparatuses or systems of Figs. 1, 3, or 5a, the application 120 of Figs. 1 or 5a, or the via the user interface 200 of Fig. 2, as described above.
  • Block 704 illustrates that, in one embodiment, an application may access a partially virtual database to retrieve a database result that includes the business service context, as described above.
  • one or more of the action(s) illustrated by this Block may be performed by the apparatuses or systems of Figs. 1, 3, or 5a, the application 120 or federated database 150 of Figs. 1 or 5a, or the via the user interface 200 of Fig. 2, as described above.
  • Block 706 illustrates that, in one embodiment, the partially virtual database may query at least one other application for information regarding the business service, as described above.
  • querying may include accessing the at least one other application via a web services interface that produces formatted query results that are standardized to a single predetermined formatting scheme regardless of the other application queried, and adapting the information, included in the query result from the respective other application, to the partial virtual database fields of the partially virtual database, as described above.
  • querying may include retrieving a list of other applications to query from a provider application registry in which the other applications have previously registered, as described above.
  • the partially virtual database may be configured to read information regarding the business service from at least one other application, but may not write information regarding the business service from the at least one other application, as described above.
  • the partially virtual database may include at least one non- virtual field associated with the business services that are stored within the partially virtual database, and at least one virtual field associated with the business service whose field value is provided by the at least one application as a result of querying the at least one application, as described above.
  • one or more of the action(s) illustrated by this Block may be performed by the apparatuses or systems of Figs. 1, 3, or 5a, the applications 180 or federated database 150 of Figs. 1 or 5a, as described above.
  • Block 708 illustrates that, in one embodiment, the partially virtual database may generate an aggregated database result associated with the business service, as described above.
  • the aggregated database result may include information provided by the at least one other application, as described above.
  • generating may include providing a database result that includes at least one of both a non- virtual field and a virtual field in a single database retrieval operation, as described above.
  • the user of Block 702 may be associated with a security credential, as described above.
  • generating an aggregated database result may include filtering the information provided by the at least one other application based upon the user's security credentials, as described above.
  • the filtering based upon the security credentials may occur at the consumer application or, in yet another embodiment, each of the other provider applications, as described above.
  • the user's security credential may be associated with a tenant, and at least one of the at least one other applications may provide a multi- tenant business service, as described above.
  • filtering information based upon the user's security credential may include not filtering a first set of information, provided by the at least one other application, that is common to all tenants of the multi-tenant business service, and filtering, based on the user's associated tenant, a second set of information, provided by the at least one other application, that is specific to individual tenants of the multi-tenant business service, as described above.
  • one or more of the action(s) illustrated by this Block may be performed by the apparatuses or systems of Figs. 1, 3, or 5a, the applications 180 or federated database 150 of Figs. 1 or 5a, as described above.
  • Block 710 illustrates that, in one embodiment, an application may display at least a portion of the business service context regarding the business service based upon the aggregated database result, as described above.
  • one or more of the action(s) illustrated by this Block may be performed by the apparatuses or systems of Figs. 1, 3, or 5a, the application 120 of Figs. 1 or 5a, or the via the user interfaces 401, 402, and 403 of Figs. 4a, 4b, and 4c, as described above.
  • FIG. 8 is a block diagram of an example embodiment of a system 800 in accordance with the disclosed subject matter.
  • a mobile computing device or mobile device e.g., a smartphone, a tablet, etc.
  • system 100 of Fig. 1 may be configured to generate a "widget" that provides a consistent, high performing summary of a Service given the user's current context in some application. Further, the system 100 may be configured to provide data access mechanisms for multiple applications to incorporate Service summary data into their own native user interfaces.
  • the system 800 of Fig. 8 may be configured to provide the same or similar data but via a user experience that is appropriate from a mobile user. For example, in one such embodiment, launching a service context UI may not be done from within another UI of an application.
  • the system 800 may be configured to provide features suitable for a mobile device such as receiving notifications and collaboration, etc. It is understood that the above is merely one illustrative example to which the disclosed subject matter is not limited.
  • the system 800 may be configured to provide a constant look-and-feel to the service context UI 122 in that it looks substantially the same no matter where or how the UI 122 is launched.
  • the service context within a mobile device context may include single or limited purpose interaction with the user 190, provide a quick means for the user to view the service context (e.g., a 1-2 second response time, etc.).
  • the application 120 may be substantially independent or a stand-alone application that merely provides the UI 122 and no other functions.
  • the generation and display of the UI 122 may occur similarly to that of the system 100 of Fig. 1, as described above.
  • the system 800 may be configured to take advantage of
  • the system 100 may be configured to launch or display the UI 122 as derivative of the native UI of the application or as pop-up or tooltip element on-top of the native the application.
  • the system 800 may be configured to display the UI 122 as the main or sole UI of the application, as described above.
  • the system 100 may be configured to get the business service identifier (ID) or other context identifiers or names from the UI context of the launching application.
  • the system 800 may be configured to get the business service ID or name from a list of business services presented to the user.
  • system 100 may constrain the user to only the services presented or associated with the launching application.
  • the user 190 may be able to alter the query to generate a different list of business services or otherwise manipulate the list of business services, as described below. It is understood that the above are merely a few illustrative examples to which the disclosed subject matter is not limited.
  • a user may be able to communicate or transmit a service context using various capabilities of the mobile device or communication protocols (e.g., Bluetooth, email, short messaging service, etc.).
  • the user may be able to register for or receive various push notifications about changes to certain services or attributes of various business services, as described below.
  • a user may be able to join communities or groups of users who are interested in a particular business service or other system resources, as described below.
  • the system 100 within a desktop or non-mobile context may not be configured to provide these abilities or services. It is understood that the above are merely a few illustrative examples to which the disclosed subject matter is not limited.
  • the mobile device 802 may be similar to or include the computing device 102 of Fig. 1.
  • the mobile device 802 may include at least one display or monitor 817 configured to visually display information to the user 190.
  • the monitor 817 may include a touch screen, a liquid crystal display (LCD), or other form of display technology.
  • other hardware components such as, for example, an input device, keyboard, mouse, touchpad, loud speakers, a camera, a sensor, etc. It is understood that the above are merely a few illustrative examples to which the disclosed subject matter is not limited.
  • the computing device 102 of Fig. 1 may also include these hardware devices.
  • the application 120 includes a mobile application executing on the mobile device 802.
  • the application 120 may be a special purpose application 120 configured simply to request, retrieve and display a service context 168.
  • Such an application 120 is illustrated in Figs. 10a - lOh. It is understood that the above is merely one illustrative example to which the disclosed subject matter is not limited.
  • the application 120 may be configured to provide additional services or functionality (e.g., an IT management application, etc.)
  • the application 120 may be configured to request, receive, and display a service context 168, similarly to that as described above.
  • the technique may be more complex than that described above.
  • the application 120 may not be directly associated with a business service 188, as the application 120 might be if the application 120 was generally configured to interact with or provide a front-end to a business service, as described above.
  • user 190 or application 120 may be configured to select a business service 188 from a plurality of possible business services 188.
  • the application 120 may request an associated business service context 168, as described above.
  • the user 190 may be required to manually enter the desired business service 188 into the application 120.
  • a list 814 of possible business services may be provided by a service manager 804 included by the Service Context Data Server 804 or other computing entity.
  • the business service list 814 may be maintained by the Service Context Data server 804.
  • the Service Context Data Server 804 may be similar to the DB Server 104 of Fig. 1.
  • Service Context Data Server 804 may include various hardware components, such as, a processor, memory, network interface, etc. similarly to those of DB server 104 of Fig. 1 which are not illustrated in this figure.
  • one or all of the components, such as, the notification manager 822, service manager 824, or the group manager 826 may be included in other computing devices or entities and may not be integrated or co-located with the Service Context Data Server 804. It is understood that the illustrated is merely one example to which the disclosed subject matter is not limited.
  • the service manager 824 may transmit the service list 814 to the mobile device 802 in response to a request by the mobile device 802. In various embodiments, the service manager 824 may periodically push or transmits a service list 814 to the mobile device 802. In some such embodiments, the service list 814 may only be pushed to the mobile deice 802 if there is a change in the service list 814 (e.g., an addition or removal of a business service 188 from the list 814, etc.). In another embodiment, predefined criteria or a set of rules may dictate when the service manager 814 communicates the service list 814 to the mobile device 802.
  • the service manager 824 may associate one or more service lists 814 with a particular user 190 or a group of users. For example, in one embodiment, a plurality of service lists 814 may be maintained and when the mobile device 802 requests a service list 814, the service manager 824 may determine which of the plurality of service lists 814 to send the mobile device 802. In such an embodiment, the user 190 may be included with a user group that includes, for example, administrators located in Houston, Texas. The service manager 824 may then select a service list 814 associated with that Houston administrator group and not provide other service lists 814 that are associated with other user groups (e.g., salesmen located in Houston, Texas; administrators located in San Francisco, California; etc.).
  • other user groups e.g., salesmen located in Houston, Texas; administrators located in San Francisco, California; etc.
  • the user 190 may be able to update the service list 814 via the application 120.
  • the application 120 may be configured to transmit the modified service list 814 (or a portion thereof) back to the service manager 824 for storage and later retrieval.
  • the application 120 may transmit messages 832 (e.g., write requests, request to delete a particular business service, etc.) to the service manager 824.
  • the service manager 824 may then be configured to alter or edit the associated service list 814 and/or provide appropriate success or failure messages back to the mobile device 802.
  • the service manager 824 may be configured to store cascading or overlapping service lists 814.
  • a user 190 may be associated with a number of user groups (e.g., administrators in Houston, Texas, all employees in Houston, Texas, employees that Boss Bob manages, etc.).
  • the user 190 may have a personalized list of business services 188 that the user 190 has added (or deleted or blacklisted, etc.).
  • the service manager 824 may be configured to transmit each service list 814 to the application 120.
  • the service manager 824 may be configured to dynamically generate a composite service list 814 based upon the various service lists 814 that are associated with the user 190.
  • this generation may be based upon a set of predefined priority rules. For example, the existence of a business service 188 on the list 814 associated with "employees that Boss Bob manages" may override the blacklisting or removal of the business service 188 from the user 190's personal service list 814.
  • the user 190 may actively select the business service from the list 814.
  • the application 120 may automatically select the most recently used or selected business service 188.
  • the user 190 may be able to manually select another business service 188 or override the application 120's automatic selection.
  • the business service 188 may be automatically selected based upon a message from the Service Context Data Server 804 or another user/mobile device (not illustrated).
  • the message may include an update message 812 or a group message 816, as described below.
  • this service list 814 may be stored and/or transmitted as a text or a binary file.
  • the service list 814 may include a file that includes data formatted in an Extensible Markup Language (XML) format or a similar format.
  • the service list 814 may include a file stored in a variation of Property List (plist) format (e.g., an iOS plist format, a GNUstep plist format, etc.). It is understood that the above are merely a few illustrative examples to which the disclosed subject matter is not limited.
  • the application may request a business service context 168 from the Service Context Data Server 804, as described above.
  • the business service context 168 may be displayed via a service context UI 122, as described above.
  • Fig. lOe is a diagram of an example embodiment of a user interface (UI) 1094 in accordance with the disclosed subject matter.
  • the UI 1095 may display a business service context within or on a mobile computing device 802.
  • this UI 1095 may be referred to as the Service Context Summary View.
  • further UI elements may also be displayed
  • the UI 1095 may display via a UI element 1054 (e.g., a tile bar or header) which business service 804 the business service context is associated with. Further the UI 1095 may include an element 1052 to display the service context or a portion thereof.
  • a UI element 1054 e.g., a tile bar or header
  • the UI 1095 may include an element 1052 to display the service context or a portion thereof.
  • various UI elements 1058 may be configured to cause the mobile device 802 to display other portions of the service context or retrieve and display other service contexts. Examples of such displays are discussed below in reference to Figs. lOa-lOh. These UI elements 1058 may effectively cause the mobile device 802 to display the sub-views, as described above, and may result in the displaying various embodiments, such as, a list view configured to display additional inform regarding the service in an alternate format. In various embodiments, various UI elements or views may focus on various aspects of the selected business service. It is understood that the above are merely a few illustrative examples to which the disclosed subject matter is not limited. In another embodiment, the UI elements 1058 may include business service linking UI elements 1058 that cause the retrieval and display other service contexts, as described above.
  • Service Context Data Server 804 may include notification manager 822.
  • the notification manager 824 may be configured to push or transmit an update message 812 to the application 120, OS 118, or mobile device 802 when a predefined event occurs (e.g., a business service 188 generates an event, such as, an incident ticket; a message has been sent to the user 190 by another user; etc.).
  • a predefined event e.g., a business service 188 generates an event, such as, an incident ticket; a message has been sent to the user 190 by another user; etc.
  • the update message 812 may cause the application 120 to automatically retrieve a service context 168 for a business service 188 (typically a business service 188 associated with or indicated by the update message 812).
  • the update message 812 may cause application 120 or OS 118 to indicate, to the user 190, that a notification message has arrived. In various embodiments, this may occur via a UI element overlaid upon the application 120's icon (as shown in Fig. 10a). In another embodiment, this may occur via a pop-up windows or other UI element. It is understood that the above are merely a few illustrative examples to which the disclosed subject matter is not limited.
  • the user 190 or application 120 may transmit update configuration messages 834 to the notification manager 822 indicating rules or criteria for which the notification manager 822 is to generate or transmit subsequent update messages 812.
  • rules may include "any changes in information for the business service associate current service context 168", "if information (e.g., incidents, service tickets, sales values, etc.) associated with a particular business service 188 exceed or falls below a certain threshold value", etc. It is understood that the above are merely a few illustrative examples to which the disclosed subject matter is not limited.
  • the notification manager 822 may receive notification rules from an administrator logged into or having direct or remote access to the Service Context Data Server. In yet another embodiment, the notification manager 822 may receive notification rules from update configuration messages 834 sent by other users (not illustrated). For example, a manager may update the notification rules associated with their employees. It is understood that the above are merely a few illustrative examples to which the disclosed subject matter is not limited.
  • the notification manager 822 may base the generation of its notification or update messages 812 on, at least in part, values or messages received from a group manager 826 that is included by the Service Context Data Server 804.
  • the group manager 826 may be configured to group a plurality of users 190 together for processes of notifications, messaging, access rights, or other processing tasks.
  • the group of users 190 may include a community that has a common interest in some system resource(s) (e.g., business service 188, etc.). It is understood that the above is merely one illustrative example to which the disclosed subject matter is not limited.
  • the multiple users 190 may be associated for purposes of access to a service list 814.
  • the service manager 824 may determine which users 190 are part of those associations by asking a group manager 826. Likewise, with the notification manager 822.
  • the group manager 826 may also be configured to distribute or transmit messages 816 to all the members or users 190 associated with one or more groups of users 190. In another embodiment, the group manager 826 may ask or make use of the notification manager 822 to perform the actual transmission of the information via the update message 812.
  • a user 190 may wish to send a business service context 168 to another user 190, as described above.
  • the user 190 may not just wish to send the business service context 168 to a single other user, but to a group of users (e.g., the user 190's team at work, etc.). Instead of sending individual messages to each user, the user 190 or application 120 may send a single group update message 836 to the group manager 826.
  • the group manager 826 may then forward and/or re-format and re-send the information of the message to the various users associated with the group of users for whom the group update message 836 was destined.
  • the group manager 826 may instead inform the notification manager 822 that a notification event has occurred for users associated with the group update message 836 was destined.
  • the group manager 826 may provide the notification manager 822 with the information (e.g., business service context 168, etc.) included in the group update message 836.
  • the notification manager 822 may then send out an update message 812 to the various users.
  • a business service 188 may generate a notification event (e.g., a critical hardware failure, etc.) that the notification manager 822 deems to be warrant the transmission of an update message 812.
  • the notification manager 822 may check its internal business service-to-user associations and determine that a group of administrative users (e.g., administrators working for Boss Bob, etc.) should receive the update message 812.
  • the update message 812 may include a business service context 168 or a DB query result 166 the associated business service 188.
  • the notification manager 822 may maintain a list of the affected users. In another embodiment, the notification manager 822 may simply know that the group should receive the update message 812 and may ask the group manager 826 for the specific users 190 included in the group. In yet another
  • the notification manager 822 may transmit an update message 812 to the group manager 826 (e.g., as a group update message 836, etc.).
  • the group manager 826 may then essentially forward the update message 812 as a group message 816 to the affected users 190 of the targeted group of users.
  • the user for example, Jane (as a member of the target group) or Jane's mobile device may receive the update message 812 or group message 816 (depending upon the embodiment).
  • the OS 118 or application 120 may provide a GUI element that indicates that Jane has received a notification or message. Jane may then check this message and view the business service context 168 that informs her that a piece of hardware has failed (in this example).
  • Other users of the group who also receive the update message 812 may include, for purposes of this example, Boss Bob, Dick, and Sally.
  • Jane may be the "on-call" administrator during this event. Jane may then replace or repair the piece of hardware and restore the business service 188. Jane may then send a group update message 836 (targeted to the group of administrators working for Boss Bob) that says that "Jane has fixed everything and everything is OK”.
  • the group manager 826 may receive this group update message 836 and either forward it as a group message 816 or ask the notification manager to send the information the message 836 includes as an update message 812 (depending upon the embodiment) to the targeted group.
  • Boss Bob may receive the message 836 similarly to that described above and may rest easy knowing Jane has fixed everything. It is understood that the above is merely one illustrative example to which the disclosed subject matter is not limited.
  • the group update message 836, group message 816, and/or update message 812 may include text messages and/or binary messages (e.g., pictures, service contexts 168, etc.). In various embodiments, these messages may adhere to predefined protocol (e.g., notification message related to the mobile device's OS 118, email format, text messaging format, etc.). It is understood that the above are merely a few illustrative examples to which the disclosed subject matter is not limited.
  • the group update message 836 may allow a user 190 to add or remove themself or other users from various groups and/or perform various other management functions (e.g., set permissions, set business service associations, etc.).
  • the notification manager 822, service manager 824, and/or the group manager 826 may make use of a publish-subscribe model of distribution of their respective messages.
  • the managers 822, 824, and/or 826 may broadcast their respective messages and the application 120 or OS 118 may be configured to filter out messages as needed. It is understood that the above are merely a few illustrative examples to which the disclosed subject matter is not limited.
  • FIG. 9 is a flow chart of an example embodiment of a technique 900 in accordance with the disclosed subject matter.
  • the technique 900 may be used or produced by the systems such as those of Figs. 1, 3, or 8.
  • the above are merely a few illustrative examples to which the disclosed subject matter is not limited. It is understood that the disclosed subject matter is not limited to the ordering of or number of actions illustrated by technique 900.
  • Fig. 9 illustrates one possible form of a user's interaction with an application executed by a mobile device that is configured to display a business context service, as described above. It is understood that other interactions with the application and operations performed by the application are possible. Some of the user interfaces which support these operations and interactions are described in more detail below.
  • Block 902 illustrates that, in one embodiment, a business service context application may be executed on or by a mobile device, as described above.
  • the application may be configured to have a single purpose, retrieving and displaying business service contexts.
  • the application may provide a richer functionality (e.g., an IT management application) that also supports the retrieval and display of a business service context, as described above.
  • one or more of the action(s) illustrated by this Block may be performed by the apparatuses or systems of Figs. 1, 3, or 8, the application of Figs. 1, 3, or 8, as described above.
  • FIG. 10a is a diagram of an example embodiment of a user interface (UI) 1091 in accordance with the disclosed subject matter.
  • the UI element 652 may cause the application to be launched (or executed by the mobile device) or brought to the foreground of the mobile device's UI (in embodiments that include a multi-tasking operating system). It is understood that the above is merely one illustrative example to which the disclosed subject matter is not limited.
  • Block 904 illustrates that, in one embodiment, the application may be configured to display a list of business services, as described above. In some
  • the application may automatically retrieve the list of business services, or, in another embodiment, the user may manually enter one or more business services, as described above.
  • one or more of the action(s) illustrated by this Block may be performed by the apparatuses or systems of Figs. 1, 3, or 8, the application of Figs. 1, 3, or 8, as described above.
  • FIG. 1 Ob is a diagram of an example embodiment of a user interface (UI)
  • the UI 1092 may display a list 1022 of business services about which the user may request a business service context.
  • the UI 1092 may include a UI element 1024 (e.g., a button, etc.) via which the user may start another UI (e.g., UI 1094 of Fig. lOd) that allows a user to manually enter or add another business service.
  • the UI 1092 may include a UI element 1026 (e.g., a button, etc.) via which the user may start another UI (e.g., UI 1093 of Fig. 10c) that allows a user to edit the list of business services.
  • the user may wish to edit or manipulate the list of business services.
  • the user may select an UI element 1026 and be provided with a UI (e.g., UI 1093 of Fig. 10c) that allows a user to edit the list of business services.
  • UI e.g., UI 1093 of Fig. 10c
  • FIG. 10c is a diagram of an example embodiment of a user interface (UI)
  • the UI 1093 may provide a user with a way to edit the list of business services.
  • this editing may include adding a business service, deleting a business service, altering the order or hierarchy of the list of business services, etc.
  • the UI 1093 may include one or more UI elements 1032 (e.g., buttons, a touch-n-drag region, etc.) by which the user may re-order the business services within the list.
  • the list of business services may include a hierarchical organization (e.g., folders, etc.). In such an embodiment, the user may re-order or re-arrange the business services within such a hierarchy.
  • the UI 1032 may include a UI element 1034 that, when selected, allow a user to delete or remove a business service from the list of business services.
  • the UI 1032 may include a UI element 1036 that allows a user to add or manually enter one or more business services.
  • this may cause the UI 1094 of Fig. lOd to be displayed.
  • this may allow a user to select a list of business services from a plurality of lists, for example, that are available on the Service Context Data server of Fig. 8, another remote computing device, or are stored within the mobile device.
  • the UI 1093 may include a UI element 1034 (e.g., button, pull down menu, etc.) that indicates that the user wishes to save the entered business service to the list of business services.
  • a UI element 1034 e.g., button, pull down menu, etc.
  • the list may be transmitted back to the Service Context Data server or a remote server for storage and/or future synchronization. It is understood that the above are merely a few illustrative examples to which the disclosed subject matter is not limited.
  • the user may wish to r to manually enter or add another business service.
  • the user may select the UI element 1024 of Fig. 10b or the UI element 1036 of Fig. 10c.
  • FIG. 1 Od is a diagram of an example embodiment of a user interface (UI) 1094 in accordance with the disclosed subject matter.
  • the UI 1094 may provide a user with a way to manually add a business service to the list of business services.
  • a UI 1094 may be used in order for the user to manually enter a desired business service.
  • the UI 1094 may be used to enter or accept a business service that is communicated to the user (e.g., via a message from a another user, etc.) or if the user becomes aware of a business service by some out-of-bounds means.
  • the UI 1094 may include one or more UI elements 1042 (e.g., text fields, buttons, virtual keyboard, etc.) by which the user may enter or select a business service.
  • fields to be entered may include, but are not limited to, the name of the business service, an identifier associated with the business service, a network address of the business service, any identification or authentication credentials (e.g., username, password, etc.) that are associated with the user or would give the user access to the business service, etc.
  • the UI 1094 may include a UI element 1044 (e.g., button, pull down menu, etc.) that indicates that the user wishes to save the entered business service to the list of business services.
  • the UI element 1044 or other UI elements may allow a user to clear the fields of UI elements 1042, place predefined values (e.g., authentication credentials, domain information, etc.) within the fields of UI elements 1042, etc.
  • predefined values e.g., authentication credentials, domain information, etc.
  • other UI elements may be included by UI 1094.
  • Block 906 illustrates that, in one embodiment, a user may cause a mobile computing device to select a business service from a plurality or list of possible business services, as described above.
  • a user may cause a mobile computing device to select a business service from a plurality or list of possible business services, as described above.
  • one or more of the action(s) illustrated by this Block may be performed by the apparatuses or systems of Figs. 1, 3, or 8, the application of Figs. 1, 3, or 8, as described above.
  • the application may display a list of business services from which the user may select a particular business service. Using that selected business service, the application may then automatically request from a database a business service context associated with the selected business service, as described above.
  • Block 908 illustrates that, in one embodiment, the mobile computing device may receive a request from a user to display at least a portion of a business service context regarding a business service, as described above. In some embodiments, this may include launching the application. In various embodiments, one or more of the action(s) illustrated by this Block may be performed by the apparatuses or systems of Figs. 1, 3, or 8, the application of Figs. 1, 3, or 8, as described above.
  • Block 910 illustrates that, in one embodiment, that the mobile device may query a database for a business service context of the select business service, and receiving in response an aggregated database result regarding the business service that include the requested business service context, as described above.
  • one or more of the action(s) illustrated by this Block may be performed by the apparatuses or systems of Figs. 1, 3, or 8, the application of Figs. 1, 3, or 8, as described above.
  • Block 912 illustrates that, in one embodiment, the mobile device may display a graphical user interface (GUI) on the mobile device that displays at least a portion of the information included by the business service context, as described above.
  • GUI graphical user interface
  • one or more of the action(s) illustrated by this Block may be performed by the apparatuses or systems of Figs. 1, 3, or 8, the application of Figs. 1, 3, or 8, as described above.
  • the GUI may be similar to the UI 1095 of Fig. lOe, as described above.
  • the GUI may be similar to the UI 1096 of Fig. lOf, as described below.
  • FIG. lOe is a diagram of an example embodiment of a user interface (UI) 1095 in accordance with the disclosed subject matter.
  • the UI 1095 may provide a user with a summary view of the business service context. It is understood that the above is merely one illustrative example to which the disclosed subject matter is not limited.
  • the UI 1095 may include a UI element 1054 (e.g., a label, a title bar, etc.) that displays the business service associated with the current business service context (e.g., "BusinessServicel", etc.).
  • a UI element 1054 e.g., a label, a title bar, etc.
  • the business service associated with the current business service context e.g., "BusinessServicel", etc.
  • the UI 1095 may include one or more UI elements 1052 that provide detailed information about a portion of the business service context.
  • a user can see that the business service "BusinessServicel” has an attribute called “Incidents” and that there are 4 "Incidents”.
  • the user may cause the UI 1096 of Fig. lOf to be displayed. It is understood that the above is merely one illustrative example to which the disclosed subject matter is not limited.
  • the UI 1095 and other UIs may include a UI element 1056 that facilitates the user sending or transmitting the business service context or a portion thereof to another user or group of users.
  • this UI element 1056 may execute an email or other messaging program to which the business service context (or portion thereof) is automatically attached or entered into.
  • the UI element 1056 may cause another UI to be shown that allows a user to select one or more users or devices to transmit the message to.
  • the message may include a group update message, as described above. It is understood that the above are merely a few illustrative examples to which the disclosed subject matter is not limited.
  • a user may be able to move or switch from the UI 1095 of Fig. lOe to the UI 1096 of Fig. 1 Of via the UI element 1058 of Fig. lOe. It is understood that the above are merely a few illustrative examples to which the disclosed subject matter is not limited.
  • FIG. 1 Of is a diagram of an example embodiment of a user interface (UI)
  • the UI 1096 may display a detailed view of business service context within or on a mobile computing device. In some embodiments, this UI 1096 may be referred to as the Service Context List View. In such an embodiment, further UI elements may also be displayed
  • the UI 1096 may display via UI element 1064 (e.g., a tile bar or header, etc.) which business service the business service context is associated with (e.g., "BusinessServicel", etc.). Further the UI 1095 may include an element 1066 to display the service context or a portion thereof.
  • UI element 1064 e.g., a tile bar or header, etc.
  • business service the business service context e.g., "BusinessServicel", etc.
  • the UI 1095 may include an element 1066 to display the service context or a portion thereof.
  • various UI elements 1062 may be configured to cause the mobile device to display other portions of the service context or retrieve and display other service contexts. These UI elements 1062 may effectively cause the mobile device to display the sub-views, as described above, and may result in the displaying various embodiments, such as, a detail view configured to display additional inform regarding the service in an alternate format. In various embodiments, various UI elements or views may focus on various aspects of the selected business service. It is understood that the above are merely a few illustrative examples to which the disclosed subject matter is not limited. In another embodiment, the UI elements 1062 may include business service linking UI elements 1062 that cause the retrieval and display other service contexts, as described above.
  • the UI elements 1062 may cause the mobile device to display another UI that provides or displays further detail regarding the business context information.
  • the information included in the business context may be hierarchical in nature.
  • the UI element 1062 may cause an UI such as UI 1097 of Fig. lOg to be displayed.
  • FIG. lOg is a diagram of an example embodiment of a user interface (UI)
  • the UI 1097 may provide a user with a very detailed view of a portion of the information included by business service context (e.g., the "Incidentl" portion of the
  • the UI 1097 may include one or more UI elements 1072 to display detailed information regarding the service context or a portion thereof, displayed by UI 1076.
  • the UI element 1064 may be configured to display current portion of the business service context (now "Incidentl") being displayed.
  • the UI 1097 may include a UI element 1076 that allows or facilitates the return or retrieval of the prior portion of hierarchical level of the business service context (e.g., "BusinessServicel").
  • the user may navigate between multiple portions of the business service context. In the illustrated embodiment, the navigation may be simply "up or down", but in other embodiments lateral or sideways or even more complex navigation between interrelated business service context portions may be possible.
  • Block 914 illustrates that, in one embodiment, that the mobile device may display a GUI on the mobile device that shows a list of additional business service contexts that are associated with the current business service context.
  • this GUI may be included as a GUI similar to UIs 1095 of Fig. lOe, 1096 of Fig. lOf or 1097 of Fig. lOg; however, it is understood that the above are merely a few illustrative examples to which the disclosed subject matter is not limited.
  • one or more of the action(s) illustrated by this Block may be performed by the apparatuses or systems of Figs. 1, 3, or 8, the application of Figs. 1, 3, or 8, as described above.
  • notifications or messages may be pushed or sent to a user or a mobile device.
  • the receipt of such a message may be indicated to the user. In various embodiments, this may be done via the operating system of the mobile device.
  • FIG. 1 Oh is a diagram of an example embodiment of a user interface (UI) 1098 in accordance with the disclosed subject matter.
  • the UI 1084 may provide a user with an indication of any new messages or notifications that have been pushed or transmitted to the mobile device, as described above. It is understood that the above is merely one illustrative example to which the disclosed subject matter is not limited.
  • the business service context application may include or be associated with an icon or UI element 1012.
  • the UI element 1012 may cause the application to be launched (or executed by the mobile device) or brought to the foreground of the mobile device's UI (in embodiments that include a multi-tasking operating system). It is understood that the above is merely one illustrative example to which the disclosed subject matter is not limited.
  • the application or operating system of the mobile device may cause a UI element 1084 to be shown or available to the user.
  • the UI element 1084 may indicate that an update message or notification has been received.
  • the UI element 1084 may include a graphic (e.g., a number indicating the number of messages received, etc.) included with or overlaid upon the UI element or icon 1012.
  • another form or UI element 1084 may be employed (e.g., pop-up window, transient panel, sound, etc.).
  • a UI may be presented or displayed to the user that shows the pending or current notifications.
  • a UI may be displayed that immediately shows the user the pending notification.
  • the notification includes a text (or other) message
  • the UI may display the message.
  • the UI may display the business service context.
  • FIG. 11 is a flow chart of an example embodiment of a technique 1100 in accordance with the disclosed subject matter.
  • the technique 1100 may be used or produced by the systems such as those of Figs. 1, 3, 5a, or 8.
  • Block 1102 illustrates that, in one embodiment, at least a portion of a business service context regarding a business service may be requested by a mobile device, as described above.
  • requesting may include retrieving and/or displaying a list of business services, as described above.
  • the user may select one of these business services.
  • the mobile device may then request the respective business service context, as described above.
  • the user may manually add a business service to the list, as described above.
  • the user may manually edit the list of business services, as described above.
  • one or more of the action(s) illustrated by this Block may be performed by the apparatuses or systems of Figs. 1, 3, 5a, or 8, or the mobile computing device or the network interface of Fig. 8, as described above.
  • Block 1104 illustrates that, in one embodiment, an aggregated database result regarding the business service may be received from a database, as described above.
  • the aggregated database result may include the requested business service context, as described above.
  • the business service context may include information from a plurality of applications, as described above.
  • receiving may include receiving the aggregated database result as part of a single database query transaction, as described above.
  • the aggregated database result may be provided by an at least partially virtual database that virtualizes database fields whose field values are provided by the plurality of other applications, as described above.
  • one or more of the action(s) illustrated by this Block may be performed by the apparatuses or systems of Figs. 1, 3, 5a, or 8, or the mobile computing device or the network interface of Fig. 8, as described above.
  • Block 1106 illustrates that, in one embodiment, a graphical user interface element may be displayed that displays at least a portion of the information included by the business service context, as described above.
  • displaying may include displaying a first portion of the information included by the business service context, as described above.
  • displaying may include displaying a business service linking user interface element that when selected causes a second business service context to be created and displayed, wherein the second business service context is associated with a second business service indicated by the business service linking user interface element, as described above.
  • one or more of the action(s) illustrated by this Block may be performed by the apparatuses or systems of Figs. 1, 3, 5a, or 8, or the mobile computing device or the monitor of Fig. 8, or the user interfaces of Figs. lOa-lOh, as described above.
  • Block 1108 illustrates that, in one embodiment, in response to a user indicating that the user wishes to view more information regarding at least one aspect of the business service context, displaying a second portion of information included by the business service context, as described above.
  • one or more of the action(s) illustrated by this Block may be performed by the apparatuses or systems of Figs. 1, 3, 5a, or 8, or the mobile computing device or the monitor of Fig. 8, or the user interfaces of Figs. lOa-lOh, as described above.
  • Block 1122 illustrates that, in one embodiment, a message may be transmitted to a remote computing device that causes a user of the mobile computing device to be associated with a business service, as described above.
  • the message may instead cause the user to be associated with a group of users, as described above.
  • transmitting may include transmitting a message to the remote computing device that causes the user to be associated with a group of users, wherein the group of users is associated with at least one business service, as described above.
  • one or more of the action(s) illustrated by this Block may be performed by the apparatuses or systems of Figs. 1, 3, 5a, or 8, or the mobile computing device or the network interface of Fig. 8, as described above.
  • Block 1124 illustrates that, in one embodiment, a notification from the remote computing device may be received when or in response to at least one predefined event regarding the associated business service has occurred, as described above.
  • receiving may include receiving, from a database, an aggregated database result regarding the business service, wherein the aggregated database result includes a second business service context, as described above.
  • one or more of the action(s) illustrated by this Block may be performed by the
  • Block 1142 illustrates that, in one embodiment, at a user's request, at least a portion of the information included by the business service context may be transmitted from the mobile computing device to a second computing device, as described above.
  • the second computing device may include a mobile computing device, as described above.
  • transmitting may include instructing a remote computing device to provide the portion of the information included by the business service context to a second user, as described above.
  • the second user may be associated with the second computing device, as described above.
  • one or more of the action(s) illustrated by this Block may be performed by the apparatuses or systems of Figs. 1, 3, 5a, or 8, or the mobile computing device or the network interface of Fig. 8, as described above.
  • Implementations of the various techniques described herein may be implemented in digital electronic circuitry, or in computer hardware, firmware, software, or in combinations of them. Implementations may be implemented as a computer program product, i.e., a computer program tangibly embodied in an information carrier, e.g., in a machine-readable storage device or in a propagated signal, for execution by, or to control the operation of, data processing apparatus, e.g., a programmable processor, a computer, or multiple computers.
  • data processing apparatus e.g., a programmable processor, a computer, or multiple computers.
  • a computer program such as the computer program(s) described above, can be written in any form of programming language, including compiled or interpreted languages, and can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment.
  • a computer program can be deployed to be executed on one computer or on multiple computers at one site or distributed across multiple sites and interconnected by a communication network.
  • Method steps may be performed by one or more programmable processors executing a computer program to perform functions by operating on input data and generating output. Method steps also may be performed by, and an apparatus may be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application- specific integrated circuit).
  • FPGA field programmable gate array
  • ASIC application- specific integrated circuit
  • processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer.
  • a processor will receive instructions and data from a read-only memory or a random access memory or both.
  • Elements of a computer may include at least one processor for executing instructions and one or more memory devices for storing instructions and data.
  • a computer also may include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks.
  • Information carriers suitable for embodying computer program instructions and data include all forms of non-volatile memory, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks.
  • semiconductor memory devices e.g., EPROM, EEPROM, and flash memory devices
  • magnetic disks e.g., internal hard disks or removable disks
  • magneto-optical disks e.g., CD-ROM and DVD-ROM disks.
  • the processor and the memory may be supplemented by, or incorporated in special purpose logic circuitry.
  • implementations may be
  • a computer having a display device, e.g. , a capacitive touchscreen, a restive touchscreen, or a liquid crystal display (LCD) monitor, for displaying information to the user and a keyboard and/or a pointing device (e.g., a mouse, a trackball, a touchscreen, etc.), by which the user can provide input to the computer.
  • a display device e.g. , a capacitive touchscreen, a restive touchscreen, or a liquid crystal display (LCD) monitor
  • LCD liquid crystal display
  • keyboard and/or a pointing device e.g., a mouse, a trackball, a touchscreen, etc.
  • Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback, e.g., visual feedback, auditory feedback, or tactile feedback; and input from the user can be received in any form, including acoustic, speech, or tactile input.
  • Implementations may be implemented in a computing system that includes a back-end component, e.g. , as a data server, or that includes a middleware component, e.g., an application server, or that includes a front-end component, e.g., a client computer having a graphical user interface or a Web browser through which a user can interact with an implementation, or any combination of such back-end, middleware, or front-end components.
  • Components may be interconnected by any form or medium of digital data communication, e.g., a communication network. Examples of communication networks include a wired or wireless local area network (LAN), a wide area network (WAN), e.g., the Internet, or a cellular network.
  • LAN local area network
  • WAN wide area network
  • cellular network e.g., cellular network.

Landscapes

  • Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • User Interface Of Digital Computer (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
PCT/US2013/033355 2012-03-28 2013-03-21 Requesting and displaying a business service context from a virtual database WO2013148470A1 (en)

Priority Applications (4)

Application Number Priority Date Filing Date Title
JP2015503402A JP6228968B2 (ja) 2012-03-28 2013-03-21 仮想的なデータベースに対するビジネスサービスコンテキストの要求、及び表示
EP13716557.7A EP2842058A1 (en) 2012-03-28 2013-03-21 Requesting and displaying a business service context from a virtual database
CA2868804A CA2868804C (en) 2012-03-28 2013-03-21 Requesting and displaying a business service context from a virtual database
AU2013240062A AU2013240062B2 (en) 2012-03-28 2013-03-21 Requesting and displaying a business service context from a virtual database

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US13/432,888 2012-03-28
US13/432,888 US8818994B2 (en) 2011-06-27 2012-03-28 Mobile service context

Publications (1)

Publication Number Publication Date
WO2013148470A1 true WO2013148470A1 (en) 2013-10-03

Family

ID=48096231

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2013/033355 WO2013148470A1 (en) 2012-03-28 2013-03-21 Requesting and displaying a business service context from a virtual database

Country Status (5)

Country Link
EP (1) EP2842058A1 (ja)
JP (1) JP6228968B2 (ja)
AU (1) AU2013240062B2 (ja)
CA (1) CA2868804C (ja)
WO (1) WO2013148470A1 (ja)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9412084B2 (en) 2011-06-27 2016-08-09 Bmc Software, Inc. Service context
US10366416B2 (en) 2015-04-30 2019-07-30 Kellogg Company Beacon based campaign management
EP3745278A1 (en) * 2019-05-29 2020-12-02 Amadeus S.A.S. System and method for integrating heterogeneous data objects
EP3745279A1 (en) * 2019-05-29 2020-12-02 Amadeus S.A.S. System and method of generating aggregated functional data objects
FR3096802A1 (fr) * 2019-05-29 2020-12-04 Amadeus Système et procédé de génération d’objets de données fonctionnelles agrégées

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220237097A1 (en) * 2021-01-22 2022-07-28 Vmware, Inc. Providing user experience data to tenants

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2002259384A (ja) * 2001-03-02 2002-09-13 Mitsubishi Electric Corp 仮想レコード使用データベース統合装置
US7246159B2 (en) * 2002-11-01 2007-07-17 Fidelia Technology, Inc Distributed data gathering and storage for use in a fault and performance monitoring system
WO2009122527A1 (ja) * 2008-03-31 2009-10-08 富士通株式会社 装置構成情報管理装置へ情報の更新系処理を行なう仮想統合管理装置
US20100017314A1 (en) * 2008-07-16 2010-01-21 Microsoft Corporation Travel expense management system
JP2010146165A (ja) * 2008-12-17 2010-07-01 Fujitsu Ltd 性能トラブル切り分け支援プログラム及び性能トラブル切り分け支援装置
JP5402066B2 (ja) * 2009-02-19 2014-01-29 富士通株式会社 情報検索システム、情報検索装置、情報検索プログラム及び情報検索方法
EP2224358A1 (en) * 2009-02-27 2010-09-01 AMADEUS sas Graphical user interface for search request management

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
DENNIS MCLOED ET AL: "A federated architecture for database systems", AFIPS '80 PROCEEDINGS OF THE NATIONAL COMPUTER CONFERENCE, 1980, pages 283 - 289, XP055072273, Retrieved from the Internet <URL:http://delivery.acm.org/10.1145/1510000/1500561/p283-mcleod.pdf?ip=145.64.134.247&id=1500561&acc=ACTIVE SERVICE&key=986B26D8D17D60C88D75A192E3112143&CFID=235162788&CFTOKEN=13218470&__acm__=1374493739_d570997bd9f04d68ec770f9887e64d4d> [retrieved on 20130722] *

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9412084B2 (en) 2011-06-27 2016-08-09 Bmc Software, Inc. Service context
US10366416B2 (en) 2015-04-30 2019-07-30 Kellogg Company Beacon based campaign management
US10991006B2 (en) 2015-04-30 2021-04-27 Kellogg Company Beacon based campaign management
EP3745278A1 (en) * 2019-05-29 2020-12-02 Amadeus S.A.S. System and method for integrating heterogeneous data objects
EP3745279A1 (en) * 2019-05-29 2020-12-02 Amadeus S.A.S. System and method of generating aggregated functional data objects
FR3096802A1 (fr) * 2019-05-29 2020-12-04 Amadeus Système et procédé de génération d’objets de données fonctionnelles agrégées
FR3096800A1 (fr) * 2019-05-29 2020-12-04 Amadeus Système et procédé pour intégrer des objets de données hétérogènes
US11087244B2 (en) 2019-05-29 2021-08-10 Amadeus S.A.S. System and method for aggregating and updating heterogeneous data objects
US11494709B2 (en) 2019-05-29 2022-11-08 Amadeus S.A.S. System and method for integrating heterogeneous data objects

Also Published As

Publication number Publication date
JP6228968B2 (ja) 2017-11-08
CA2868804A1 (en) 2013-10-03
AU2013240062B2 (en) 2018-04-19
AU2013240062A1 (en) 2014-10-16
CA2868804C (en) 2019-09-10
JP2015518601A (ja) 2015-07-02
EP2842058A1 (en) 2015-03-04

Similar Documents

Publication Publication Date Title
US9412084B2 (en) Service context
US8745040B2 (en) Service context
US11496460B2 (en) Dynamic, customizable, controlled-access child outcome planning and administration resource
CA2868804C (en) Requesting and displaying a business service context from a virtual database
US9674227B2 (en) Communicating status regarding application of compliance policy updates
US8577960B2 (en) Providing status information for components in a distributed landscape
CN105229678B (zh) 进程建模和界面
US20180278563A1 (en) Systems and methods for messaging and collaboration
US20140164893A1 (en) Assisted portal navigation and crowd-based feedback
US9361139B1 (en) System and method for visualizing virtual system components
TW200849076A (en) Tailored system management interface
US9389934B1 (en) Centralized and distributed notification handling system for software applications
US10026132B2 (en) Chronological information mapping
US11556225B1 (en) Displaying queue information in a graphical user interface of an issue tracking system
US8713152B2 (en) Managing distributed applications using structural diagrams
US20150134706A1 (en) Integrating Collaboration Systems with Other Systems
WO2017152231A1 (en) &#34;incident reporting&#34;
CN109450874B (zh) 用户账号监控方法及装置
US20150262128A1 (en) Assimilating business rules
US11017412B2 (en) Contextual information monitoring
US20220414565A1 (en) Methods and systems for service request management
US20230103896A1 (en) Configuring dynamic interactions between application elements
US10097622B1 (en) Method and system for communication using published events
JP2016035681A (ja) メニュー構造

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 13716557

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2015503402

Country of ref document: JP

Kind code of ref document: A

Ref document number: 2868804

Country of ref document: CA

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2013240062

Country of ref document: AU

Date of ref document: 20130321

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 2013716557

Country of ref document: EP