Opposition · USPTO

Opposition 91239847

OtherUSPTO

Opposition 91239847 at USPTO between Sony Corporation and GuangDong Roman Technology Co., Ltd., over the mark SONICOOL, filed Feb 26, 2018. Status in the office record: other.

Status
Other
Result
Other
Filed
Feb 26, 2018
Marks involved
27
Parties

Who is involved

The parties as named in the office record.

Opponent

Sony Corporation

Respondent

GuangDong Roman Technology Co., Ltd.

Company trademarks
Timeline

How the case has moved

Dates from the USPTO record and the SONICOOL filing.

  1. SONICOOL filed

    Application 87439285 filed at the USPTO.
  2. Opposition filed

    Sony Corporation started opposition 91239847 at USPTO against SONICOOL.
Marks

Marks involved

4 contested marks, 23 marks the challenger relies on.

MarkRoleApplicationOffice
SONICOOLContested87439285USPTO
SONICOOLContested87439289USPTO
SONICOOLContested87439290USPTO
SONICOOLContested87589229USPTO
SONYRelied on72171393USPTO
SONYRelied on72171578USPTO
SONYRelied on72171579USPTO
SONYRelied on72204017USPTO
SONYRelied on72304825USPTO
SONYRelied on72304827USPTO
SONYRelied on72304828USPTO
SONYRelied on72304830USPTO

+15 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_bf7c144a-d058-4144-a650-9a94ddc03e05
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_bf7c144a-d058-4144-a650-9a94ddc03e05",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91239847",
  "status": "other",
  "office_code": "US",
  "filed_date": "2018-02-26",
  "parties": [
    {
      "name": "Sony Corporation",
      "role": "opponent"
    },
    {
      "name": "GuangDong Roman Technology Co., Ltd.",
      "role": "respondent"
    }
  ]
}