User-space emulation framework for heterogeneous soc design
US-2024004776-A1 · Jan 4, 2024 · US
US9298588B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9298588-B2 |
| Application number | US-201414455170-A |
| Country | US |
| Kind code | B2 |
| Filing date | Aug 8, 2014 |
| Priority date | Sep 4, 2013 |
| Publication date | Mar 29, 2016 |
| Grant date | Mar 29, 2016 |
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.
A tracing system may trace applications and their modules, and may make module-specific data available through various interfaces. The tracing system may collect tracer data while an application executes, and may preprocess the data into application-specific and module-specific databases. An analysis engine may further analyze and process these databases to create application-specific views and module-specific views into the data. The application-specific views may be intended for a developer of the application, while the module-specific views may have a public version accessible to everybody and a module developer version that may contain additional details that may be useful to the module developer.
Opening claim text (preview).
What is claimed is: 1. A method performed by at least one computer processor, said method comprising: receiving tracing data gathered from an application, said application comprising application specific code and reusable module code; identifying reusable module trace data and storing said reusable module trace data in a reusable module trace database; identifying application trace data and storing said application trace data in an application trace database; receiving a first request for said tracing data; determining that said first request is not authenticated; creating an application-specific view of said application trace data in response to determining that said first request is not authenticated; receiving a second request for said tracing data; determining that said second request is authenticated; and creating a reusable module-specific view of said reusable module trace data in response to determining that said second request is authenticated. 2. The method of claim 1 further comprising: anonymizing said reusable module trace data prior to storing said reusable module trace data. 3. The method of claim 2 , said anonymizing being performed by obfuscating at least a portion of said reusable module trace data. 4. The method of claim 1 , said first request being an authenticated request from an application developer.
by tracing the execution of the program · CPC title
User authentication · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.