Opposition · USPTO

Opposition 91247463

OtherUSPTO

Opposition 91247463 at USPTO between Energizer Brands, LLC and He Yongqing, over the mark LUMINTOP, filed Apr 2, 2019. Status in the office record: other.

Status
Other
Result
Other
Filed
Apr 2, 2019
Marks involved
18
Parties

Who is involved

The parties as named in the office record.

Opponent

Energizer Brands, LLC

Company trademarks
Respondent

He Yongqing

Timeline

How the case has moved

Dates from the USPTO record and the LUMINTOP filing.

  1. LUMINTOP filed

    Application 87639219 filed at the USPTO.
  2. Opposition filed

    Energizer Brands, LLC started opposition 91247463 at USPTO against LUMINTOP.
Marks

Marks involved

2 contested marks, 16 marks the challenger relies on.

MarkRoleApplicationOffice
LUMINTOPContested87639219USPTO
LUMINTOPContested87639246USPTO
ENERGIZERRelied on74708971USPTO
ENERGIZER BUNNYRelied on76367112USPTO
ENERGIZER BUNNYRelied on78200655USPTO
ENERGIZERRelied on85898597USPTO
ENERGIZERRelied on86078652USPTO
ENERGIZERRelied on86760047USPTO
ENERGIZERRelied on86760300USPTO
ENERGIZERRelied on86760872USPTO
ENERGIZERRelied on86872437USPTO
ENERGIZERRelied on86872444USPTO

+6 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_6dfc4b5b-4e24-4e80-8034-e4fa3abce1d7
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_6dfc4b5b-4e24-4e80-8034-e4fa3abce1d7",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91247463",
  "status": "other",
  "office_code": "US",
  "filed_date": "2019-04-02",
  "parties": [
    {
      "name": "Energizer Brands, LLC",
      "role": "opponent"
    },
    {
      "name": "He Yongqing",
      "role": "respondent"
    }
  ]
}