# US 10,484,324 B2 · Hero cards that display contextual information and actions for backend systems > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 10,484,324 B2 - Document ID: US10484324B2 - Status: Granted - Kind: B2 - Application number: 15/369,888 - Filed: 2016-12-06 - Published: 2018-04-05 - Granted: 2019-11-19 - Earliest claimed: 2016-10-02 - Assignees: VMware, Inc. - Applicants: VMware, Inc. - Inventors: Ian Ragsdale; Adam Cianfichi; Neal Foster; Marshall Anne Busbee; Dan Zeck; Rob Worsnop; Anthony Kueh; Andrew Eye - Web page: https://patentgrep.com/patent/US10484324B2 ## CPC - H04L 51/226: Delivery according to priorities - G06F 3/04883: for inputting data by handwriting, e.g. gesture or text - G06F 16/90335: {Query processing} - G06Q 10/103: {Workflow collaboration or project management} - H04L 51/046: Interoperability with other network applications or services - H04L 51/52: for supporting social networking services - H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP] - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) - G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR ## Abstract Systems herein supply hero cards that display contextual information and actions based on backend systems. The information and actions are related to a trigger content item in an application that does not have access to the backend systems. A hero agent running a user device can communicate the trigger content to a hero server. The hero server can determine which connectors to backend systems relate to the user device, and then can retrieve result information from one or more of the backend systems. The result information populates the hero card, which the hero agent displays within the application. Action buttons on the hero card cause the hero agent to contact one or more of the backend systems to cause an action to take place there. ## Claims ### Claim 1 A system for providing hero cards, the system comprising: a non-transitory, computer-readable medium that contains instructions; a processor that executes the instructions to perform stages including: enabling a hero agent on a user device, the hero agent causing the user device to communicate with a hero server; receiving, at the hero server, a service request sent by the hero agent in response to detection of trigger content within an application, wherein the trigger content is detected by the hero agent, the service request including one or more authentication tokens used to determine one or more backend systems associated with the user device; based on the one or more authentication tokens, determining at the hero server a subset of backend systems associated with the user device; applying a first recipe selected based on compatibility with the trigger content and causing a first backend system of the subset of backend systems to perform a search based on the trigger content; receiving result information from the first backend system based on the search; assembling a hero card that includes the result information from the first backend system; and sending the hero card to the hero agent, causing the user device to display the hero card within the application. ### Claim 2 (depends on 1) The system of claim 1, wherein the hero card includes a first action button for causing a first action in the first backend system, wherein the first action button causes the hero agent to send a first message to the first backend system. ### Claim 3 (depends on 2) The system of claim 2, the stages further comprising applying a second recipe based on to compatibility with the trigger content and causing a second backend system to perform a search based on the trigger content, wherein the hero card includes additional result information from the second backend system. ### Claim 4 (depends on 3) The system of claim 3, wherein the hero card includes a second action button for causing a second action in the second backend system, wherein the second action button causes the hero agent to send a second message to the second backend system. ### Claim 5 (depends on 1) The system of claim 1, wherein the hero card includes at least one of a header region, a body region, and an action region, wherein the hero server determines how many of the three regions to provide based on the result information. ### Claim 6 (depends on 5) The system of claim 5, wherein the header region includes an icon that indicates which of the backend systems the hero card relates to. ### Claim 7 (depends on 1) The system of claim 1, wherein the application is an email application and the service request is generated by the email application based on an email being the trigger content, wherein the hero card displays simultaneously with other emails in the email application. ### Claim 8 (depends on 1) The system of claim 1, wherein the hero card is one of a plurality of hero cards sent from the hero server to the hero agent, wherein the application cycles through the plurality of hero cards. ### Claim 9 (depends on 1) The system of claim 1, wherein the application is a social media platform and the service request is generated based on a posted message being the trigger content, wherein the hero card displays within the social media platform. ### Claim 10 (depends on 1) The system of claim 1, wherein the application is a hero application that displays the hero card amongst a plurality of hero cards. ### Claim 11 A non-transitory, computer-readable medium containing instructions executed by at least one processor to perform stages for generating hero cards, the stages comprising: sending a hero agent to a user device for installation, the hero agent causing the user device to communicate with a hero server; receiving, at the hero server, a service request from the hero agent, the service request being sent in response to detection of trigger content within an application, wherein the trigger content is detected by the hero agent, the service request including one or more authentication tokens used to determine one or more backend systems associated with the user device; based on the one or more authentication tokens, determining at the hero server a subset of backend systems associated with the user device; applying a first recipe that relates the trigger content to a first backend system of the subset of backend systems, the recipe being selected based on compatibility with the trigger content and causing the first backend system to perform a search and provide result information; assembling a hero card that includes the result information from the first backend system; and sending the hero card to the hero agent, causing the user device to display the hero card within the application. ### Claim 12 (depends on 11) The non-transitory, computer-readable medium of claim 11, wherein the hero card includes a first action button for causing a first action in the first backend system, wherein the first action button causes the hero agent to send a first message to the first backend system. ### Claim 13 (depends on 12) The non-transitory, computer-readable medium of claim 12, wherein the hero card includes a second action button for causing a second action in a second backend system based on the hero server applying a second recipe for the second backend system. ### Claim 14 (depends on 11) The non-transitory, computer-readable medium of claim 11, wherein the application is an email application and the service request is generated by the email application based on an email being the trigger content, wherein the hero card displays simultaneously with other emails in the email application. ### Claim 15 (depends on 11) The non-transitory, computer-readable medium of claim 11, wherein the hero card includes at least one of a header region, a body region, and an action region, wherein the hero server determines how many of the three regions to provide based on the result information. ### Claim 16 A method for presenting backend content within an application using hero cards, comprising: sending a hero agent to a user device for installation, the hero agent causing the user device to communicate with a hero server; receiving, at the hero server, a service request from the hero agent, the service request being sent in response to detection of trigger content within an application, wherein the trigger content is detected by the hero agent, the service request including one or more authentication tokens used to determine one or more backend systems associated with the user device; based on the one or more authentication tokens, determining at the hero server a subset of backend systems associated with the user device; applying a first recipe that relates the trigger content to a first backend system of the subset of backend systems, the recipe being selected based on compatibility with the trigger content and causing the first backend system to perform a search and provide result information; assembling a hero card that includes the result information from the first backend system; and sending the hero card to the hero agent, causing the user device to display the hero card within the application. ### Claim 17 (depends on 16) The method of claim 16, wherein the hero card includes a first action button for causing a first action in the first backend system, wherein the first action button causes the hero agent to send a first message to the first backend system. ### Claim 18 (depends on 17) The method of claim 17, wherein the hero card includes a second action button for causing a second action in a second backend system based on the hero server applying a second recipe for the second backend system. ### Claim 19 (depends on 16) The method of claim 16, wherein the application is an email application and the service request is generated by the email application based on an email being the trigger content, wherein the hero card displays simultaneously with other emails in the email application. ### Claim 20 (depends on 16) The method of claim 16, wherein the hero card includes at least one of a header region, a body region, and an action region, wherein the hero agent determines how many of the three regions to display based on the result information.