Opposition · USPTO

Opposition 91239929

OtherUSPTO

Opposition 91239929 at USPTO between Medtronic, Inc. and Vivian Nguepi Dongmo, over the mark METATRONIC, filed Mar 2, 2018. Status in the office record: other.

Status
Other
Result
Other
Filed
Mar 2, 2018
Marks involved
28
Parties

Who is involved

The parties as named in the office record.

Opponent

Medtronic, Inc.

Company trademarks
Respondent

Vivian Nguepi Dongmo

Timeline

How the case has moved

Dates from the USPTO record and the METATRONIC filing.

  1. METATRONIC filed

    Application 87494144 filed at the USPTO.
  2. Opposition filed

    Medtronic, Inc. started opposition 91239929 at USPTO against METATRONIC.
Marks

Marks involved

1 contested mark, 27 marks the challenger relies on.

MarkRoleApplicationOffice
METATRONICContested87494144USPTO
MEDTRONICRelied on72461305USPTO
MEDTRONICRelied on72461407USPTO
MEDTRONICRelied on72461720USPTO
MEDTRONICRelied on73064410USPTO
MEDTRONICRelied on73824429USPTO
MEDTRONICRelied on73824921USPTO
MEDTRONICRelied on74138348USPTO
MEDTRONICRelied on74238654USPTO
MEDTRONICRelied on74405138USPTO
MEDTRONICRelied on75695704USPTO
MEDTRONICRelied on78069264USPTO

+16 more marks in this case

API

Get this data via the API

Every fact on this page comes from the Signa API. Track oppositions and cancellations on any mark with one request.

  • GET/v1/proceedings/{id}

    Parties, dates, outcome and every mark in the case

  • GET/v1/proceedings?trademark_id={trademark_id}

    Every proceeding on a mark

GET /v1/proceedings/{id}
ID=prc_04061a2f-b412-4a8d-943c-5343906ee11d
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_04061a2f-b412-4a8d-943c-5343906ee11d",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91239929",
  "status": "other",
  "office_code": "US",
  "filed_date": "2018-03-02",
  "parties": [
    {
      "name": "Medtronic, Inc.",
      "role": "opponent"
    },
    {
      "name": "Vivian Nguepi Dongmo",
      "role": "respondent"
    }
  ]
}