Opposition · USPTO

Opposition 91265901

OtherUSPTO

Opposition 91265901 at USPTO between J.D. Power and Shenzhen Jianyan Technology Co., Ltd, over the mark JIPOWER, filed Nov 11, 2020. Status in the office record: other.

Status
Other
Result
Other
Filed
Nov 11, 2020
Marks involved
7
Parties

Who is involved

The parties as named in the office record.

Opponent

J.D. Power

Company trademarks
Respondent

Shenzhen Jianyan Technology Co., Ltd

Timeline

How the case has moved

Dates from the USPTO record and the JIPOWER filing.

  1. JIPOWER filed

    Application 88954946 filed at the USPTO.
  2. Opposition filed

    J.D. Power started opposition 91265901 at USPTO against JIPOWER.
Marks

Marks involved

1 contested mark, 6 marks the challenger relies on.

MarkRoleApplicationOffice
JIPOWERContested88954946USPTO
J.D. POWER AND ASSOCIATESRelied on73829921USPTO
JDPOWER.COMRelied on75660523USPTO
J.D. POWERRelied on75841233USPTO
J.D. POWER AND ASSOCIATES CUSTOMER SATISFACTION SINCE 1968 THE VOICE OF THE CUSTOMERRelied on77117553USPTO
J.D. POWER AND ASSOCIATES 1 CUSTOMER SATISFACTION SINCE 1968 THE VOICE OF THE CUSTOMERRelied on77117608USPTO
J.D. POWER VOXRelied on86564747USPTO
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_4de40c13-b07f-492b-aefa-6f81e80531ca
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_4de40c13-b07f-492b-aefa-6f81e80531ca",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91265901",
  "status": "other",
  "office_code": "US",
  "filed_date": "2020-11-11",
  "parties": [
    {
      "name": "J.D. POWER",
      "role": "opponent"
    },
    {
      "name": "Shenzhen Jianyan Technology Co., Ltd",
      "role": "respondent"
    }
  ]
}