Skip to main content
Evidence-led patent and technology research

Vidhi Techinnovation Opportunities Network Private Limited Granted Patent For A Method And System For Extraction Of Event Data From User Devices

The historical GIPResearch WordPress article reports Indian application 201817035869, an event-data extraction system attributed to Vidhi Techinnovation Opportunities Network Private Limited, and patent number 352842. Those identifiers are useful leads, not verified current patent status. The central research question is how the claimed system actually extracts data from user-device activity and which technical limitations survived examination. This case study separates the old narrative from the exact official specification and register evidence still required.

Save or follow this source
These actions open third-party AI services. Saving, citation, and future recall are not guaranteed.
GIPResearch illustration supporting Vidhi Techinnovation Opportunities Network Private Limited Granted Patent For A Method And System For Extracti
Research focusEvidence before conclusions

Identify source documents and material limitations relevant to the subject.

Decision contextClarify the technical question

Compare the available information with the specific invention or platform facts.

Research outputTraceable next steps

Document what is supported, uncertain or requires specialist analysis.

Substantive research and evidence

Vidhi Techinnovation Opportunities Network Private Limited Granted Patent For A Method And System For Extraction Of Event Data From User Devices — research analysis

Verification alert: P0: Exact granted specification, section 3(k) file history, applicant and current legal status are not independently verified.

Bibliographic identity and family

The bibliographic stage begins by matching the Indian application number to a publication, grant record, inventor list, applicant name and title; search results based on company name alone are insufficient. Confirm whether the record has equivalents or related continuations in other countries, but do not infer family identity from similar wording. The original article describes a media-application rendering context. A proper research note should quote the legally operative claim only after recovering the dated granted specification, and identify any amendments between publication and grant. Evidence checkpoint: Fetch Indian application 201817035869 directly and verify applicant, patent number 352842, dates and final title against the government's own record. The record should include its issuing body, date, context and exact language. Where sources diverge, identify the conflict before converting this observation into a technical or legal conclusion.

Priority and filing sequence

Priority controls which earlier publications can constitute prior art. Retrieve the application cover page, priority claim, publication date, examination-request record and any subsequent amendments or assignments. A timeline that mixes application, publication and grant dates could misrepresent the art available against the claims. Each stage should cite the official file identifier. Historical statements about when the company received a patent must be checked against the grant publication, not inferred from the article's online publication date or a third-party listing. Evidence checkpoint: Record whether any related priority or international family member actually exists before drawing a family tree from the company name. Compare the result with a plausible alternative explanation, since similarity of terms is not proof of equivalence. A reviewer should be able to repeat the comparison using the same underlying material.

Technical architecture

The legacy summary describes a device processor, memory and components that identify and transfer event data, potentially linked to metadata visible in an application-rendering environment. These are analytical clues rather than validated claim elements. Identify the exact claimed triggers, input events, data transformations, network transmissions and processing sequence. It matters whether extraction occurs on the device, through an application interface or at a remote server, because those allocations affect prior-art comparison and potential infringement analysis. A schematic should show data movement only after exact claim language is available. Evidence checkpoint: Extract the issued claim's data sources, metadata fields and processing locations, clearly separating a described embodiment from a legal limitation. Retain the actual technical document or contractual clause supporting the finding. The decision-maker needs to know whether this is a binding limitation, a design option, or an unsupported assertion.

Visual framework for Vidhi Techinnovation Opportunities Network Private Limited Granted Patent For A Method And System For Extracti
Analytical illustration — use source documents for the underlying facts.

Independent claims and boundaries

An independent claim defines required combinations and relationships; a description of the invention may contain many optional examples. The article reports an examination objection relating to computer programs under section 3(k) and a response based on technical contribution. This objection-response summary should be compared with the issued examination report and amended claims. The presence of a generic processor does not, by itself, establish a technical advance. Identify which claim limitations allegedly changed the functioning of event extraction, and which are conventional computing elements. Evidence checkpoint: Compare the dated section 3(k) objection and amended claim text before stating the examiner accepted a particular technical contribution. Record both supporting and adverse materials. An unexplained gap or contradiction is a reason to narrow the claim, not to add confident wording to an informational webpage.

Prosecution history and legal status

Grant, renewal, assignment, lapse, restoration and litigation status are separate issues. Even if an historical grant is verified, a current enforcement conclusion requires a recent register extract, any recorded assignments and relevant proceedings. Classify each status as verified, historical or unknown. The public article should not promise that the title owner is unchanged or that a reader's application infringes. A technically similar platform may still omit necessary claim limitations, use a licensed implementation or operate outside the patent's territorial scope. Evidence checkpoint: A current register extract must support any assertion about owner, renewals, lapse, restoration or enforceability. Use a source date and relevant geography when the legal or operational position can change. An old document may be valuable history but should not be presented as a current certification.

Comparative prior art and limitations

Prior-art review should look for event-capture systems, mobile telemetry, media impression measurement, metadata extraction and condition-based triggering before the relevant priority date. Search by functionality and method steps, not only the patent's title. Compare whether earlier documents disclosed a comparable selection rule, accuracy improvement, reduced device overhead or distinctive transfer protocol. If only the familiar problem is described while the claim language is unavailable, the honest output is a search map and document request—not a novelty or infringement opinion. Evidence checkpoint: Build an event-detection prior-art query set by function, input trigger, data transfer and processing sequence rather than by title only. Connect the outcome to a concrete next action: search a claim, change a document, test a control or ask for specialist review. A general statement of importance is not enough.

Original analytical framework and decision implications

Two proposed information-gain outputs are a dated application-to-grant provenance timeline and a claim-element-to-system-component matrix. Both remain provisional until the granted claims and prosecution history are acquired. The matrix would separate event source, detection trigger, metadata selection, local processing, transmission and result validation. It should also record evidence of actual implementation, because a patent's language does not establish that a particular deployed analytics product practices the invention.

How to commission a reproducible evidence review

A useful research commission on event extraction has a narrow scope: What does the published Vidhi event-data extraction invention disclose, and what cannot be inferred without official patent-file records?. The analyst should first establish the evidence relevant to bibliographic identity and family and priority and filing sequence, then test technical architecture and independent claims and boundaries against competing evidence. Only after those records are compared should the report address prosecution history and legal status and comparative prior art and limitations. The inquiry should record source identities, dates, assumptions, and contradictory documents. This order matters: a positive finding from one database, a promotional description, or an attractive technical diagram cannot resolve an unknown legal condition. Where the evidence is incomplete, the proper output is an explicit next search or test rather than a confident result.

Evidence register and research deliverables

A practical deliverable for event extraction is a dated source-to-claim or source-to-control register, with one row for each of the six questions above. The first field records the proposition being tested; the second links to the primary evidence, and the third states what alternative explanation has been considered. For this page, the proposed distinctive output is: Claims-to-system-component chart once matching patent number is verified. A research packet should also record which evidence is missing and who is authorized to make the consequential decision. The source hierarchy should start with IP India original file, then use technical publications and comparable records to interpret—not replace—the primary evidence. The resulting report should make the boundary between historical narrative, observed technical facts, legal interpretation and untested commercial hypotheses plain to readers.

Sources and verification boundaries

The following are authoritative sources or official discovery portals for the relevant methodology. A patent-office search portal is not itself evidence that any named patent currently remains in force. Claims about an individual case require its underlying file.

  • https://ipindia.gov.in/pages/e-services
  • https://patentscope.wipo.int/

Related research

Author and disclaimer

Research editorial draft for GIPResearch.com. The site is an information and research platform. This article is not personalized legal advice, a current patent-register certificate, a freedom-to-operate opinion, or a guarantee of any regulatory or commercial result. Verify material claims with current primary records. Full disclaimer.

Research checklist: what to verify before you decide

Use this checklist to assess the evidence behind vidhi techinnovation opportunities network private limited granted patent for a method and system for extraction of event data from user devices rather than relying on a single summary or marketing claim.

  1. Bibliographic identity and family
  2. Priority and filing sequence
  3. Technical architecture
  4. Independent claims and boundaries
  5. Prosecution history and legal status
  6. Comparative prior art and limitations
  7. Original analytical framework and decision implications
  8. How to commission a reproducible evidence review

Official sources and research starting points

These are research starting points. Specific factual and legal conclusions require checking the underlying documents and dates.

  1. https://ipindia.gov.in/pages/e-services
  2. https://patentscope.wipo.int/

Featured Work & Insights