Opposition · USPTO

Opposition 91288839

OtherUSPTO

Opposition 91288839 at USPTO between General Electric Company and Ge William Wei, over the mark GEDEFENSE V GEDEFENSE, filed Dec 19, 2023. Status in the office record: other.

Status
Other
Result
Other
Filed
Dec 19, 2023
Marks involved
50
Parties

Who is involved

The parties as named in the office record.

Opponent

General Electric Company

Company trademarks
Respondent

Ge William Wei

Timeline

How the case has moved

Dates from the USPTO record and the GEDEFENSE V GEDEFENSE filing.

  1. GEDEFENSE V GEDEFENSE filed

    Application 97567749 filed at the USPTO.
  2. Opposition filed

    General Electric Company started opposition 91288839 at USPTO against GEDEFENSE V GEDEFENSE.
Marks

Marks involved

1 contested mark, 49 marks the challenger relies on.

MarkRoleApplicationOffice
GEDEFENSE V GEDEFENSEContested97567749USPTO
GERelied on70035089USPTO
GERelied on72396531USPTO
GERelied on72404063USPTO
GERelied on72455729USPTO
GERelied on72455733USPTO
GERelied on73036924USPTO
GERelied on73071173USPTO
GERelied on73082141USPTO
GERelied on73102821USPTO
GERelied on73162520USPTO
GERelied on73392934USPTO

+38 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_4a9bd10a-5723-4f3b-b9e9-ccf2e6873b51
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_4a9bd10a-5723-4f3b-b9e9-ccf2e6873b51",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91288839",
  "status": "other",
  "office_code": "US",
  "filed_date": "2023-12-19",
  "parties": [
    {
      "name": "General Electric Company",
      "role": "opponent"
    },
    {
      "name": "Ge William Wei",
      "role": "respondent"
    }
  ]
}