Opposition · USPTO

Opposition 91270357

OtherUSPTO

Opposition 91270357 at USPTO between Bayerische Motoren Werke Aktiengesellschaft and Di Liang, over the mark CJIBMWI, filed Jul 8, 2021. Status in the office record: other.

View CJIBMWIGet this data via the API
Status
Other
Result
Other
Filed
Jul 8, 2021
Marks involved
11
Parties

Who is involved

The parties as named in the office record.

Opponent

Bayerische Motoren Werke Aktiengesellschaft

Company trademarks
Respondent

Di Liang

Timeline

How the case has moved

Dates from the USPTO record and the CJIBMWI filing.

  1. CJIBMWI filed

    Application 90367755 filed at the USPTO.

  2. Opposition filed

    Bayerische Motoren Werke Aktiengesellschaft started opposition 91270357 at USPTO against CJIBMWI.
Marks

Marks involved

1 contested mark, 10 marks the challenger relies on.

MarkRoleApplicationOffice
CJIBMWIContested90367755USPTO
BMWRelied on71662350USPTO
BMWRelied on71662351USPTO
BMWRelied on73487543USPTO
BMWRelied on76410763USPTO
BMWRelied on76410806USPTO
BMW IRelied on79098410USPTO
BMW IRelied on79171111USPTO
BMWRelied on87378824USPTO
BMWRelied on87379075USPTO
BMWRelied on87383973USPTO
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 API keyView docs
GET /v1/proceedings/{id}
ID=prc_903aef81-8e88-4ed6-b5f2-39611c31c8da
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_903aef81-8e88-4ed6-b5f2-39611c31c8da",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91270357",
  "status": "other",
  "office_code": "US",
  "filed_date": "2021-07-08",
  "parties": [
    {
      "name": "Bayerische Motoren Werke Aktiengesellschaft",
      "role": "opponent"
    },
    {
      "name": "Di Liang",
      "role": "respondent"
    }
  ]
}