Opposition · USPTO

Opposition 91293895

OtherUSPTO

Opposition 91293895 at USPTO between Signify Holding B.V. and Ningbo Heyme Information Technology Co.,Ltd, over the mark DOMIHUE, filed Sep 11, 2024. Status in the office record: other.

Status
Other
Result
Other
Filed
Sep 11, 2024
Marks involved
9
Parties

Who is involved

The parties as named in the office record.

Opponent

Signify Holding B.V.

Company trademarks
Respondent

Ningbo Heyme Information Technology Co.,Ltd

Company trademarks
Timeline

How the case has moved

Dates from the USPTO record and the DOMIHUE filing.

  1. DOMIHUE filed

    Application 98341225 filed at the USPTO.
  2. Opposition filed

    Signify Holding B.V. started opposition 91293895 at USPTO against DOMIHUE.
Marks

Marks involved

1 contested mark, 8 marks the challenger relies on.

MarkRoleApplicationOffice
DOMIHUEContested98341225USPTO
HUE PERSONAL WIRELESS LIGHTINGRelied on79200414USPTO
HUERelied on79207468USPTO
HUE WHITERelied on79212166USPTO
HUE WHITE AND COLOR AMBIANCERelied on79213792USPTO
HUE WHITE AMBIANCERelied on79213793USPTO
HUE AMBIANCERelied on79213816USPTO
HUERelied on87513273USPTO
HUERelied on87648189USPTO
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_e5382b83-cbaa-46b3-a70d-81b8dfdf5f91
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_e5382b83-cbaa-46b3-a70d-81b8dfdf5f91",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91293895",
  "status": "other",
  "office_code": "US",
  "filed_date": "2024-09-11",
  "parties": [
    {
      "name": "Signify Holding B.V.",
      "role": "opponent"
    },
    {
      "name": "Ningbo Heyme Information Technology Co.,Ltd",
      "role": "respondent"
    }
  ]
}