System and method for dashboard software maintained by an end user
US-2015153918-A1 · Jun 4, 2015 · US
US10178001B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10178001-B2 |
| Application number | US-201514933281-A |
| Country | US |
| Kind code | B2 |
| Filing date | Nov 5, 2015 |
| Priority date | Nov 5, 2015 |
| Publication date | Jan 8, 2019 |
| Grant date | Jan 8, 2019 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
In some examples, a method includes receiving a data packet through a datapath configured by a data source. The datapath may specify a data dimension of data communicated through the data packet. The method may also include identifying, from the data packet, a particular dimension value for the data dimension specified in the datapath and dispatching the data of the data packet to a virtual data channel specific to the particular dimension value to support presentation of the data through a dashboard.
Opening claim text (preview).
The invention claimed is: 1. A system comprising: a processor; a non-transitory machine-readable storage medium to store instructions that, when executed by the processor, cause the processor to: receive a first data packet from a data source through a first datapath configured by the data source; identify, from the first datapath, a data dimension of data communicated through the first data packet; identify a particular dimension value from the first data packet for the data dimension identified from the first datapath; differentiate the first data packet from a second data packet that also includes the particular dimension value according to a parameter tag specified in the first datapath that is not specified in a second datapath used to communicate the second data packet; dispatch the data of the first data packet to a first virtual data channel specific to both the particular dimension value and the parameter tag for presentation through a dashboard; and dispatch data of the second data packet to a second virtual data channel specific to the particular dimension value, but not the parameter tag. 2. The system of claim 1 , wherein the first datapath comprises a universal resource locator (URL) link; and wherein the instructions, when executed by the processor, cause the processor to identify the data dimension as a URL parameter specified within the URL link itself. 3. The system of claim 1 , wherein the parameter tag includes an additional parameter for the first data packet that is not specified in the first data packet itself. 4. The system of claim 3 , wherein the instructions, when executed by the processor, cause the processor to dispatch the data of the first data packet to the first virtual data channel specific to the additional parameter. 5. The system of claim 1 , wherein the instructions, when executed by the processor, cause the processor to identify the parameter tag by identifying a universal resource locator (URL) parameter in the first datapath indicated as a tag, and not a data dimension, for the first data packet. 6. The system of claim 1 , wherein the instructions, when executed by the processor, cause the processor to bind the first virtual data channel to a widget of the dashboard. 7. The system of claim 6 , wherein the instructions, when executed by the processor, cause the processor to bind the first virtual data channel to the widget in response to a user selection for presenting the first data packet through the widget. 8. A method comprising: receiving a data packet through a datapath configured by a data source, wherein the datapath specifies a data dimension of data communicated through the data packet; identifying, from the data packet, a particular dimension value for the data dimension specified in the datapath; identifying a parameter tag specified in the datapath that specifies an additional parameter for the data packet that is not specified in the data packet itself, wherein identifying the parameter tag comprises identifying a universal resource locator (URL) parameter in the datapath indicated as a tag, and not a data dimension, for the data packet; and dispatching the data of the data packet to a virtual data channel specific to the particular dimension value and to the additional parameter to support presentation of the data through a dashboard. 9. The method of claim 8 , wherein the URL parameter is part of a URL link of the datapath. 10. The method of claim 9 , further comprising parsing the URL link to identify the data dimension. 11. The method of claim 8 , further comprising differentiating the data packet from a different data packet that also includes the particular dimension value according to the parameter. 12. The method of claim 8 , further comprising binding the virtual data channel to a widget of the dashboard. 13. The method of claim 8 , further comprising: dispatching data of a different data packet to a different virtual data channel according to a different data dimension specified in a datapath through which the different data packet is communicated. 14. A method comprising: receiving a first data packet through a datapath configured by a data source, wherein the datapath specifies a first data dimension of data communicated through the first data packet; identifying, from the first data packet, a first dimension value for the first data dimension specified by the datapath; dispatching the data of the first data packet to a first virtual data channel specific to the first dimension value to support presentation of the data through a dashboard; receiving a second data packet through the datapath configured by the data source; identifying, from the second data packet, a second dimension value for the first data dimension specified by the datapath; and dispatching data of the second data packet to a second virtual data channel specific to the second dimension value. 15. The method of claim 14 , wherein the datapath comprises a universal resource locator (URL) link, the method further comprising: identifying multiple data dimensions of the data of the first data packet, including the first data dimension, by identifying multiple URL parameters from the URL link; and parsing the first data packet to identify a dimension value for each of the multiple data dimensions, respectively, including the first dimension value, wherein dispatching the data of the first data packet comprises dispatching the data of the first data packet to a virtual data channel specific to all of the identified dimension values, including the first dimension value. 16. The method of claim 14 , wherein the datapath comprises a universal resource locator (URL) link, the method further comprising: identifying a URL parameter tag in the URL link, wherein the URL parameter tag identifies an additional parameter for the first data packet, and the additional parameter is not specified in the first data packet itself, wherein dispatching the data of the first data packet comprises dispatching the data of the first data packet to a virtual data channel specific to both the additional parameter and to the first dimension value. 17. The method of claim 16 , further comprising: identifying a URL parameter indicative of the first data dimension at a first portion of the URL link, wherein identifying the URL parameter tag comprises identifying the URL parameter tag at a second portion of the URL link, and the first portion of the URL link is delineated from the second portion of the URL link. 18. The method of claim 14 , further comprising: binding the first virtual data channel to a widget of the dashboard.
for graphical visualisation of monitoring data · CPC title
Parsing or analysis of headers · CPC title
Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements · CPC title
Network arrangements or protocols for supporting network services or applications (user-to-user messaging H04L51/00; network arrangements, protocols or services for supporting real-time applications in data packet communications networks H04L65/00) · CPC title
Arrangements for monitoring or testing data switching networks · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.