Opposition · USPTO

Opposition 91242666

OtherUSPTO

Opposition 91242666 at USPTO between Philips Lighting Holding B.V. and Shenzhen Peba Technology Co., Ltd, over the mark SAMHUE, filed Jul 24, 2018. Status in the office record: other.

Status
Other
Result
Other
Filed
Jul 24, 2018
Marks involved
9
Parties

Who is involved

The parties as named in the office record.

Opponent

Philips Lighting Holding B.V.

Respondent

Shenzhen Peba Technology Co., Ltd

Company trademarks
Timeline

How the case has moved

Dates from the USPTO record and the SAMHUE filing.

  1. SAMHUE filed

    Application 87675828 filed at the USPTO.
  2. Opposition filed

    Philips Lighting Holding B.V. started opposition 91242666 at USPTO against SAMHUE.
Marks

Marks involved

1 contested mark, 8 marks the challenger relies on.

MarkRoleApplicationOffice
SAMHUEContested87675828USPTO
FRIENDS OF HUERelied on79200265USPTO
HUE PERSONAL WIRELESS LIGHTINGRelied on79200414USPTO
HUERelied on79207468USPTO
FRIENDS OF HUERelied on79213423USPTO
HUE WHITE AND COLOR AMBIANCERelied on79213792USPTO
HUE WHITE AMBIANCERelied on79213793USPTO
HUE AMBIANCERelied on79213816USPTO
INTELLIHUERelied on85455430USPTO
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_5a78974d-0ce7-461f-bad2-165121055331
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_5a78974d-0ce7-461f-bad2-165121055331",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91242666",
  "status": "other",
  "office_code": "US",
  "filed_date": "2018-07-24",
  "parties": [
    {
      "name": "Philips Lighting Holding B.V.",
      "role": "opponent"
    },
    {
      "name": "Shenzhen Peba Technology Co., Ltd",
      "role": "respondent"
    }
  ]
}